[Bug] Invalid Time value

Had this error when stream went live:

2022-09-02 17:28:20.992 | hook  Hook called
2022-09-02 17:28:21.029 | automator.handle  Automator channel.update event for royalphunk
/usr/local/share/twitchautomator/server/node_modules/date-fns/format/index.js:392
throw new RangeError('Invalid time value');
^
RangeError: Invalid time value
at format11 (/usr/local/share/twitchautomator/server/node_modules/date-fns/format/index.js:392:11)
at Automator.vodBasenameTemplate (/usr/local/share/twitchautomator/server/src/Core/Automator.ts:99:26)
at Automator.updateGame (/usr/local/share/twitchautomator/server/src/Core/Automator.ts:288:31)
at Automator.handle (/usr/local/share/twitchautomator/server/src/Core/Automator.ts:213:24)
at Hook (/usr/local/share/twitchautomator/server/src/Controllers/Hook.ts:189:32)
at Layer.handle (/usr/local/share/twitchautomator/server/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/share/twitchautomator/server/node_modules/express/lib/router/route.js:144:13)
at AuthCore (/usr/local/share/twitchautomator/server/src/Helpers/Auth.ts:80:5)
at Layer.handle (/usr/local/share/twitchautomator/server/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/local/share/twitchautomator/server/node_modules/express/lib/router/route.js:144:13)
Node.js v18.8.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

hmm, can't immediately see why the date is broken via tests, gonna have to update my own server

added a valid check, but the date definitely shouldn't be empty to begin with.
i think i just realised what happened. i'm guessing this is a new channel that hasn't streamed before and did a channel update, therefore never setting the start date?
also it's using the basename to update chapters, that's not good

added a valid check, but the date definitely shouldn't be empty to begin with.
i think i just realised what happened. i'm guessing this is a new channel that hasn't streamed before and did a channel update, therefore never setting the start date? also it's using the basename to update chapters, that's not good

Newly added yes and changed the title before stream I think an then started streaming.

made it use the capture id instead, on a bigger project to replace using the vod basename for everything :/

Not sure if this is related, but stream went offline twice and it captured the first two streams fine but the third stream has an incorrect duration: https://i.tony.pm/c5RI9Sx.png

yeah any interruptions would start the stream again with a new name, hopefully fixed when using the capture id now


Introduce url query account manager.

URLQueryAccountManager gets the account username from a URL query parameter: ?user=<username>.

Tests:

curl -k -d '{}' --request POST http://localhost:8080/v1/zones/local/hosts?user=<username>
curl -k --request GET http://localhost:8080/v1/zones/local/hosts?user=<username>
curl -k -d '{}' --request DELETE http://localhost:8080/v1/zones/local/hosts/<host_name>?user=<username>

What's the purpose for introducing a new AM, despite of existence of HttpBasicAccountManager?

What's the purpose for introducing a new AM, despite of existence of HttpBasicAccountManager?

The motivation is to prevent from overengineering on top of http basic auth, so we are trying to replace HttpBasicAccountManager by this new URLQueryAccountManager. More details at b/340969490#comment1.

I think it's okay to submit.

Closing this PR according to the discussion at b/340969490. Using url query may not be suitable for interacting with CO via a web page.


Swiper completely bugs out when (loop && numberOfSlides > 1 && numberOfSlides > slidesPerView && numberOfSlides < slidesPerView*2)

Check that this is really a bug

[X] I confirm

Reproduction link
https://stackblitz.com/edit/js-2amhdw?file=index.html
Bug description
If you have loop enabled, and the number of slides is greater than the number of slidesPerView but less than slidesPerView*2, nothing will work properly. You will only be able to slide right until the last slide is visible; Swiping left will always skip 1 slide; After swiping left, you can only swipe right 1 time.
Steps to reproduce:
slidesPerView: 4
slidesPerGroup: 1
loop: true
numberOfSlides: >4 && <8
You can also reproduce the bug using the Swiper Studio
Expected Behavior
Swiping in any direction should only slide 1 slide at a time and infinitely loop.
Actual Behavior

You can only swipe right until the last slide (no looping).
Swiping left will skip every other slide, and afterwards you will only be able to swipe right 1 time before it stops.

Swiper version
10.3.1
Platform/Target and Browser Versions
Chrome, Firefox
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

If you have loop enabled, and the number of slides is greater than the number of slidesPerView but less than slidesPerView*2, nothing will work properly

This requirement is stated in docs


feat: install dev dependencies only in DEBUG mode

Connects to: https://github.com/bucharest-gold/centos7-s2i-nodejs/issues/34
This change also ensures that symlinks in node_modules/.bin are preserved

LGTM. tested build (make) , s2i build, and docker run on fedora 27 locally.
✔ ~/Desktop/centos7-s2i-nodejs [34-dev-dependencies-in-debug-only|✔]
17:42 $ docker run --rm  -p 8080:8080 -e DEV_MODE=true bucharestgold/centos7-s2i-nodejs-testapp
Environment:
	DEV_MODE=true
	NODE_ENV=development
	DEBUG_PORT=5858
Installing dev dependencies...
added 34 packages in 5.666s
Launching via nodemon...
[nodemon] 1.15.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --inspect=5858 server.js`
Debugger listening on ws://<IP_ADDRESS>:5858/f2bef849-4659-4140-8b99-97e8815c9595
For help see https://nodejs.org/en/docs/inspector
Server running on <IP_ADDRESS>:8080

@danbev good point. I had a test for it in a stripped down, simplified builder I was using to figure out what exactly was going on. I will incorporate that test into this PR.


Update dependency for repo-infra

...to pull in a change that makes 2017 a valid copyright year.

LGTM

confirmed and tested. 2017 date does not work before the change. 2017 does not work after the change. 2018 does not work before or after the change.
I think this is one of those 'skip the queue' type PRs.

executive decision


XFA - Avoid to have containers not pushed in the html

it aims to fix issue #13668.

/botio test

/botio makeref

Hmm; given that both browsers timed-out on both of the bots during the tests above, see https://github.com/mozilla/pdf.js/pull/13716#issuecomment-877836304 and https://github.com/mozilla/pdf.js/pull/13716#issuecomment-877836572, how do we know that this doesn't cause a bunch of breakage/regressions!?

My bad, I missed that... I checked locally that everything was good and it was.
Anyway, do you prefer I revert and then push again, test, ... ?

Hmm; given that both browsers timed-out on both of the bots during the tests above, see #13716 (comment) and #13716 (comment), how do we know that this doesn't cause a bunch of breakage/regressions!?

Where can I see an indication that they timed out?

I checked locally that everything was good and it was.

Strange, for me this patch actually times-out locally as well.

Where can I see an indication that they timed out?

There's a errors: 1238 respectively errors: 1226 printed in https://github.com/mozilla/pdf.js/pull/13716#issuecomment-877836304 respectively https://github.com/mozilla/pdf.js/pull/13716#issuecomment-877836572, and those kind of (general) errors should never appear when testing a working patch. After that, following the "Full output at..." links, the reference tests end with:
TEST-UNEXPECTED-FAIL | test failed firefox has not responded in 120s
TEST-UNEXPECTED-FAIL | test failed chrome has not responded in 120s

There's errors: 1238 respectively errors: 1226 printed in #13716 (comment) respectively #13716 (comment), and those kind of (general) errors should never appear when testing a working patch. After that, following the "Full output at..." links, the reference tests end with:

Could the bot surface the "has not responded" errors in the comment or the HTML output?

@calixteman I've tested this patch locally, in the viewer (with enableXfa = true set), and xfa_bug1717668_2 causes the browser (or tab rather) to hang (with full CPU utilization of one core) and the document doesn't render.

Could the bot surface the "has not responded" errors in the comment or the HTML output?

But as mentioned this is already indirectly visible, via the errors: {number here} lines, since those should never appear and that's thus a clear indication to look at the full logs.

The same for me locally... I was sure I tested (and I'm still sure) but obviously I didn't.


Mentors/Mentor Managers List Screen-Admin-App - Sprint 3

Description:

Build the Screen using the style guide.
Integrate Screen with the Backend

I will be working on this

I will be working on this


Provision delivery format in contract

Fixes #3970

Proposed Changes

Add the format field to the egress config

/test upgrade-tests

@matzew I've rebased this to only have the relevant changes, can you recheck?

/retest-required

/retest

/retest-required

/retest-required

/test upgrade-tests

/cc @matzew
While going through the data plane changes I realized I needed to essentially re-do the changes in this PR so since the data plane changes are isolated I added them here as well instead
I'll add unit tests and an e2e test later, would you mind taking a look at the data plane code and letting me know if the approach I'm taking makes sense?

/cc @pierDipi

/retest

/retest-required


[QUERY] Getting InvalidOperationException("The current instance does not have data, you must call Get first.") on PostgreSqlServerAdministratorResource.Data when calling PostgreSqlServerResource.GetPostgreSqlServerAdministrator()

Library name and version
Azure.ResourceManager.PostgreSql <IP_ADDRESS>
Query/Question
Hi,
I am getting exception error when calling PostgreSqlServerResource.GetPostgreSqlServerAdministrator() below.
Upon checking, this seems like a bug? Can someone verify please.

GetPostgreSqlServerAdministrator() in the library calls the code below within the library.

And the highlighted internal constructor below that is used does not set the HasData and _data unlike the other internal constructor.

Thus causing this exception to trigger when getting Data, which makes sense.

So it seems like I need to use the Get/GetAsync() to get the Data basing from the error, but this is giving me exceptions too about missing ResourceType.

Any thoughts? How should I get the Data?
Regards,
Alwyn
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @alwynjohnlim , Thank you for using Azure SDK for .NET.
For the first question, yes, you will need another get to get the actual data, it's by design.
For the second question, we believe this is a service issue, the return type value is not a proper rsource type: PostgreSQL.Server.PAL, add service attention.

Hey @alwynjohnlim, thank you for reaching out to us about the Azure SDK for .NET. Unfortunately, this issue is related to the service side and not the SDK side, so we are not able to help you with it. Therefore, we are closing this issue for now. If you need more assistance, please open an Azure support request. We apologize for any inconvenience this may cause you.
We value your feedback and we want to make sure that your problem is solved. If you think that we have misunderstood your issue or closed it incorrectly, please feel free to comment on this thread and reopen the issue. We will be happy to assist you further. Thank you for your understanding and cooperation.


Space out the weights of PHP pages

Originally posted by @chalin in https://github.com/open-telemetry/opentelemetry.io/pull/2415#discussion_r1120900286

Note to self and @cartermp @svrnm : after this lands we should "space out" the weights so that more pages can fit in between them.

As a rule of thumb, use tenths for individual pages so, e.g., 10, 20, etc.

this is fixed


fix: Fix summarizer for Anthropic and add integration tests

Fix summarizer for Anthropic and add integration tests. Also rename several testing files for accuracy.

Did not wait for checks to pass bc previous PR finished all tests successfully except for one that was misconfigured, so should be safe to merge.


Rename 'Deposit compliance' to 'REF 2021'

I still need to work on the warnings and the description.


rewards(order_by: {address: ?

Is it possible to order the rewards(order_by ...) query by address?
currently I only see  StakeAddress_comparison_exp (_eq, _in) and not order_by (asc, desc).

Yeah, this looks like a bug. Here in the schema it has 'StakeAddress_comparison_exp' when I think it should be 'order_by'.
input Reward_order_by {
  address: StakeAddress_comparison_exp
  amount: text_comparison_exp
  earnedIn: Epoch_order_by
  stakePool: StakePool_order_by
}

Like how ActiveStake has:
input ActiveStake_order_by {
  address: order_by
  amount: order_by
  epoch: Epoch_order_by
  epochNo: order_by
  registeredWith: StakePool_order_by
}

If that's it then it should be simple for the devs to fix.

yes, that's exactly it.
Thanks

Thanks for the leg work, I'll patch this shortly


Super simple fronts

updated to account for anas major arcana stuff

Ohh... this is nice.
Easy to update if we choose to change either definitions or images.
Ana
On Thu, Dec 26, 2019 at 5:15 PM Andrew McNutt<EMAIL_ADDRESS>wrote:

[image: Screen Shot 2019-12-26 at 5 15 00 PM]
https://user-images.githubusercontent.com/6854312/71495551-496b4080-2803-11ea-9e7b-2b185ff8306b.png
updated to account for anas major arcana stuff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mcorrell/vis-tarot/pull/12?email_source=notifications&email_token=ABJFLHRSHQCEZBHHUM54NV3Q2VJLXA5CNFSM4J6EI6NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHWLEQY#issuecomment-569160259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJFLHS6IDYLJHSUXGD6QRLQ2VJLXANCNFSM4J6EI6NA
.


JOSS Feedback

Re: JOSS Review
A few notes while reviewing the JOSS guidelines:

Would be helpful to have a link to the documentation on the GH repo page (to the right and within the readme) (https://mongibellili.github.io/QuantizedSystemSolver.jl/dev/)

Installation functional, but could be described better for the Julia novices

State of the field could be clearer: contrasting what is currently done, especially within the paper: maybe an example of a stiff system and compare approaches

RE: the v.1.01 notes: use version control so that these are not shown until it is released then just show it and note those functions in the release changelog

Documentation:

Landing page with description (statement of need) and installation would be good
The examples do a good job of showing how the qwuantized approach adds vaue with the number of dots: leverage this and maybe explain the differences between approaches
Tutorial: would be good to have a general simple example / just show the syntax and setup of the problem before solving the first one
Developer Guide:

Implementation page is a huge plock of text and daunting
Implementation: Distinguish between syntax and placeholders in the example

Implementation/Dependencies hide the valuable API reference information

First of all, I am grateful for your time spent to provide these comments and suggestions.

Direction to documentation is now clearer.
Installation is explained in a step by step approach.
Explanation of some limitations of the classic methods is added, and a comparison via two examples is also added.
mentioning the capabilities of the different versions is removed from the readme.

Documentation:

the landing page contains the statement of need and a detailed installation steps.
The difference between QSS and classic methods is stated, and a comparison is added in the examples.
The syntax to setup the problem and solve it is added before the first exmple in the tutorial section.
The different subject are split into multiple subpages for an easier navigation, and the user API is separate.
implementation and dependencies are minimized and kept under the developer guide.

LGTM


debug: tests

Mirror branch of main to debug failing unit tests on snapshots that are passing locally.

Picking up strange behaviour where the snapshots passing for @bonzzy locally as well as on CI are failing for me locally. Will investigate as a separate track. Linked issue on Linear here


nixos rpi bootloader: install files for raspberry pi 4 (rpi4)

Motivation for this change
NixOS currently has a few bootloader "builders":

generations-dir
generic-extlinux-compatible
grub
init-script
raspberrypi
systemd-boot

The raspberrypi option, itself, has multiple different bootloader builders that you choose from:

raspberry-pi-builder

just drops a config.txt, kernel, initrd and an old dir with old generation kernel/initrd

u-boot

drops the version-appropriate u-boot binary to /boot
drops the rpi firmware files to /boot
calls the generic-extlinux-compatible bootloader builder which in turn drops extlinux-compatible files and dir structures.

The u-boot scenario is more ideal because the user has a chance to choose a different generation to boot, including kernel and initrd. Without u-boot, the user must manually intervene and edit the sd card to switch to an old generation.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

One other note, my firmware is a bit ahead of what we have in nixpkgs, but the note on it requests that I update the rpi foundation kernel do, which I'm not trying to do right now. I'm hoping this doesn't matter...

Alright, I've now tested this by:

removing all other pi-related commits from my nixpkgs
cherry-picking this commit (27b6d45)
re-deploying my rpi4 system
sshing in, cd /boot; rm -rf *
sudo /run/current-system/bin/switch-to-configuration switch
sudo reboot

And the system came back correctly. This rpi4 system boot config looks like this:
    boot = }
      loader.grub.enable = false;
      loader.raspberryPi.enable = true;
      loader.raspberryPi.version = 4;
      loader.raspberryPi.uboot.enable = true;
      loader.raspberryPi.uboot.configurationLimit = 5;
      # ...
    };

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/493

I have tested this on my pi4 and it does indeed boot and work nicely via the uboot loader

I can also confirm this boots mainline kernel. Get the serial up and running by adding
{
  boot.kernelParams = [
    "console=ttyS1,115200n8"
  ];
}

Unfortunately the serial is a bit messy.
PM_RSTS: 0x00001000
RPi: BOOTLOADER release VERSION:23a9f59b DATE: May 15 2020 TIME: 11:05:55 BOOTMODE: 0x00000006 part: 0 BUILD_TIMESTAMP=1589537152 0x1ca63f53 0x00c03111
uSD voltage 3.3V
Initialising SDRAM 'Micron' 16Gb x2 total-size: 32 Gbit 3200
Boot mode: SD (01) order f4
SD HOST: 250000000 CTL0: 0x00000000 BUS: 100000 Hz actual: 100000 HZ div: 2500 (1250) status: 0x1fff0000 delay: 1080
SD HOST: 250000000 CTL0: 0x00000f00 BUS: 100000 Hz actual: 100000 HZ div: 2500 (1250) status: 0x1fff0000 delay: 1080
CID: 001b534d45433251543021a6552e0141
CSD: 400e00325b590001dcff7f800a404000
SD: bus-width: 4 spec: 2 SCR: 0x02858483 0x00000000
SD HOST: 250000000 CTL0: 0x00000f04 BUS: 50000000 Hz actual: 41666666 HZ div: 6 (3) status: 0x1fff0000 delay: 2
MBR: 0x00004000, 2097152 type: 0x0b
MBR: 0x00000000,       0 type: 0x00
MBR: 0x00000000,       0 type: 0x00
MBR: 0x00000000,       0 type: 0x00
lba: 16384 oem: 'mkfs.fat' volume: ' FIRMWARE   '
rsc 32 fat-sectors 2048 c-count 261628 c-size 8 r-dir 2 r-sec 0
PM_RSTS: 0x00001000
Partition: 0
lba: 16384 oem: 'mkfs.fat' volume: ' FIRMWARE   '
rsc 32 fat-sectors 2048 c-count 261628 c-size 8 r-dir 2 r-sec 0
Read config.txt bytes      503 hnd 0x0000e567 hash '19c7f64fb7ca570a'
recover4.elf not found (6)
recovery.elf not found (6)
Read start4cd.elf bytes   793116 hnd 0x0000e820 hash '07c5561caf7563d6'
Read fixup4cd.dat bytes     3187 hnd 0x0000e5f8 hash 'b4d9d35bf0b62011'
0x00c03111 0x00000000 0x000000ff
MEM GPU: 16 ARM: 998 TOTAL: 1014
Starting start4cd.elf @ 0xff000200 partition 0

U-Boot 2021.01 (Jan 11 2021 - 18:11:43 +0000)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
MMC:   emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 4 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
2939 bytes read in 21 ms (135.7 KiB/s)
------------------------------------------------------------
1:	NixOS - Default
2:	NixOS - Configuration 471 (2021-04-12 01:41 - 21.05pre-git)
3:	NixOS - Configuration 470 (2021-04-12 01:23 - 21.05pre-git)
4:	NixOS - Configuration 469 (2021-04-08 18:43 - 21.05pre-git)
5:	NixOS - Configuration 468 (2021-04-08 18:23 - 21.05pre-git)
6:	NixOS - Configuration 467 (2021-04-06 23:40 - 21.05pre-git)
Enter choice: 1:	NixOS - Default
Retrieving file: /extlinux/../nixos/ljsv9m9mkh6py0ksxnrgd7l96ph1mng3-initrd-linux-5.11.11-initrd
8799381 bytes read in 408 ms (20.6 MiB/s)
Retrieving file: /extlinux/../nixos/7ybggvzp8p6xw8zc7q68szgmbmj0pvl1-linux-5.11.11-Image
43803136 bytes read in 1909 ms (21.9 MiB/s)
append: init=/nix/store/ryxhx9rs4zzfh9p2wq4r66fs6zrpfr0z-nixos-system-dione-21.05pre-git/init console=ttyS1,115200n8 loglevel=4
Retrieving file: /extlinux/../nixos/7ybggvzp8p6xw8zc7q68szgmbmj0pvl1-linux-5.11.11-dtbs/broadcom/bcm2711-rpi-4-b.dtb
25741 bytes read in 41 ms (612.3 KiB/s)
Moving Image from 0x80000 to 0x200000, end=2c70000
## Flattened Device Tree blob at 02e00000
   Booting using the fdt blob at 0x2e00000
   Using Device Tree in place at<PHONE_NUMBER>e00000, end<PHONE_NUMBER>e0948c

Starting kernel ...

<<< NixOS Stage 1 >>>

loading module btrfs...
loading module crc32c...
modprobe: FATAL: Module crc32c not found in directory /lib/modules/5.11.11
loading module dm_mod...
running udev...
Starting version 247
[    4.044699] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
kbd_mode: KDSKBMODE: Inappropriate ioctl for device
starting device mapper and LVM...
Scanning for Btrfs filesystems
waiting for device /dev/disk/by-label/NIXOS to appear...[    4.481506] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[    4.621070] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[    4.643324] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[    4.715873] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[    4.878142] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock

mounting /dev/disk/by-label/NIXOS on /...

<<< NixOS Stage 2 >>>

running activation script...
setting up /etc...
starting systemd...

Welcome to NixOS 21.05 (Okapi)!

[   11.595257] systemd[1]: postgresqlBackup-hass.timer: Timer unit lacks value setting. Refusing.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Created slice system-modprobe.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Containers.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Swap.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Starting Create list of st…odes for the current kernel...
         Starting Load Kernel Module configfs...
         Starting Load Kernel Module drm...
         Starting Load Kernel Module fuse...
         Starting Journal Service...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting Coldplug All udev Devices...
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Finished Create list of st… nodes for the current kernel.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Remount Root and Kernel File Systems.
[  OK  ] Started Journal Service.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting Flush Journal to Persistent Storage...
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Starting Rule-based Manage…for Device Events and Files...
[  OK  ] Finished Load Kernel Modules.
         Starting Apply Kernel Variables...
[  OK  ] Finished Flush Journal to Persistent Storage.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Started Rule-based Manager for Device Events and Files.
[  OK  ] Finished Coldplug All udev Devices.
[   13.843007] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[  OK  ] Found device /dev/ttyS1.
[   13.872850] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[   13.917454] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[  OK  ] Found device /dev/disk/by-label/FIRMWARE.
        [   14.014862] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
 Starting File System Check…/dev/disk/by-label/FIRMWARE...
[   14.063568] [drm:vc5_hdmi_init_resources [vc4]] *ERROR* Failed to get HDMI state machine clock
[   14.142417] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present!
[   14.157730] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present!
��`�:�i+73�i�.
�[�۽��-@�i���(�SKI1��min+��E`�:�J�ӭ�H7+���`�:�Kb��i!I��F�ԴTR��Z�@�����7K��E`���+l���7+���`�:�IA*a����Z���I2����z�Aj
�iZ���i�:�IxXl]�B�Zj�I�@FU4@�O� i�KI7K���`�:I%�ZZr� i4�DU���`�:�J�ӭ
                              ��%�eo�i��i�:�IxXl]z��ȵ�Zj�1v���eo+�HKb��(�S
�┬Z�E◆�:I%�Z�X��V����◆�Z�─$[�)�⎺+���◆�:�J�ӭ]��"B.��┴Z�@�␋▒��I≥��]7K��E◆�:I%�Z��◆�#��7+��E◆�:I%�Z�R�������◆�:�K␉����+�����Z���◆�:�K␉���≠%��I���Z���◆���S┌���I◆IM����◆�:I%�Z���▒
                                                                                �����◆��@IA*▒���P���◆�:�J"I3�␋3"+␊
                                                                                �Z%�@�␋▒���␋�Z
                                                                                ��◆��D��␋�Z�@I]�Z�I֮њ�Z*@I]�Z:�B�P����I�@I]�ZZ�\��⎺K���◆�:�K␉��$���њ�Z���◆�:I%�ZZ�\��⎺���E◆��@IA*▒����Z���◆�:�J�ӭ��␤A��@I]�Z�A���I�@�␋▒���%�	�⎺K�@I]�ZZ5�$��I�@I]�Z��R�␋Z*�E◆��D*┌�␋·�>����[���◆�:I%�Z�·IU├�R2��␋�Z�@I]�Z���I�@I]�Z��T␍�7K�@I]�ZZ�Z��7K��E◆��D�␉���⎺+���◆�:�K␉���E�[�Z���◆�:I%�Z:7*��E◆��$*┌��)#7�└+���◆�:�J�ӭ�5�����◆�:I%�Z�A�����◆�:�J�ӭ�A�����◆�:I%�ZZI␋	�����◆�:I%�Z���·	H�Z���◆�:I%�ZZ␋$DM�Z���◆�Z�^␋B␋┼+��┌+����H���U �A°����

@colemickens Can you rebase please? https://github.com/mohe2015/nixpkgs/tree/rpi4-uboot should be a correct rebase. Also applying the one suggestion would be great!

Also is it possible to create an iso/sd image from this? And is this useful?

The infra in nixpkgs for building an rpi4-capable SD Card already prepare uboot in their own way. I don't think it's a super-wise investment to try to unify the uboot setup between the two right now, for a few different reasons.

Is there anything preventing this from being merged?

As the author of this PR, I'm personally more interested in making Tow-Boot and a traditional UEFI installation the preferred way to install. This is messy business, I'd love to let Tow-Boot handle it all. I think @samueldr has done a lot of thinking to arrive at a good model with some fun paths to take things in if it goes well.
I don't really have any opinion one way or the other about this being merged as is.

As the author of this PR, I'm personally more interested in making Tow-Boot and a traditional UEFI installation the preferred way to install. This is messy business, I'd love to let Tow-Boot handle it all. I think @samueldr has done a lot of thinking to arrive at a good model with some fun paths to take things in if it goes well.

While Tow-Boot may be the better solution long term, it is a fundamentally different approach. Unless there is a plan is to completely remove this approach, it would be good to have support for all Pi versions.
@samueldr Thoughts?

This PR only affects installing U-Boot files to a boot partition. This is not how the generic image was conceived to be used.
NixOS should not manage the firmware used to boot itself on ARM. This is because it's unknown exactly how it was installed at the first place, and will work differently depending on the system. Supporting it for a specific class of hardware (Raspberry Pi) is only going to cause some more confusion.
I believe NixOS should not manage the firmware for many reasons. The first is that the firmware should stay neutral to the operating system it intends to boot.
The second, and more important, is that it is impossible to handle the firmware through generations. So a firmware update can break currently working generations, maybe even prevent the system from booting anything at all. Handling firmware updates through a different mechanism (which doesn't exist at this point) ensures a routine NixOS upgrade won't prevent the system from booting at all.
In many ways, the current "FIRMWARE partition" approach is a proto Tow-Boot. It is a distinct firmware blob installed on the same storage media as the OS is. It is not managed by NixOS.
On thing to realize is that right now we produce a NixOS SD image which coincidentally ships with the Raspberry Pi firmware pre-installed because it is prohibitively difficult to install it after the fact. If it wasn't, it would be like other ARM systems, "bring your own firmware".

The boot.loader.raspberryPi is not expected to be used with any the generic SD images produced since adding support for the "FIRMWARE" partition approach. That is, the U-Boot installed on it is not handled by the installed operating system.
Using any boot.loader.raspberryPi option with those images will break assumptions, either in the options themselves or in the behaviour of the images.
If it was just me, the boot.loader.raspberryPi options would have been marked as deprecated already as they do cause confusion (rightfully so!).

The current recommendation is:
If the image you are using was originally built with the boot.loader.raspberryPi approach in mind, continuing to use it should be fine. It should already be working, no? If it does not, it's another problem not fixed by this PR.
If the image you are using was originally built with an unmanaged FIRMWARE partition for a U-Boot install, do not use any boot.loader.raspberryPi options.
Is there anything I'm missing here?

If anyone finds this issue. I've moved to https://github.com/pftf/RPi4 and the aarch64 installer ISO. Best decision ever.

What's the status on this PR? I've been using on my Raspberry Pi 4 for a long time already, and it never broke since I've started using it.

From a few posts back, this is still my take on this PR: https://github.com/NixOS/nixpkgs/pull/112677#issuecomment-850874950
I'll have an update on the more ideal solution using tow-boot in a week or two (waiting on a rpi3b to be able to test across all aarch64 rpi devices)

Tested on a Pi4 and without this PR it is not rebooting properly.

PR works well for me. I think it should even be merged into 22.05.

As the author I still think that we are better off not merging this. I do
feel guilty about not having published more of my rpi/tow-boot work but my
life got turned upside down and will be hectic for a few more weeks before
I can start writing some blog posts and pushing new PRs.
On Wed, Jun 29, 2022, 11:50 AM Astro @.***> wrote:

PR works well for me. I think it should even be merged into 22.05.
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/112677#issuecomment-1170300498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACP25EHMZ6I3LJHP3BHNUDVRSEHRANCNFSM4XNVD4JQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

We need this for our network booted Pi 4s. Tow boot/UEFI is not done by tomorrow and I don't see a reason to block this PR on that.

I guess I just don't want to merge stuff and then wind up ripping it back
out after the next release given Samuel's hopes and my agreement.
But also, I've been trying to push this through for a while and life
complications keep arising, so I understand wanting it merged (or carrying
it but again, I get it).
So slight "ehhh" from me but not in a "you shouldn't merge this" way.
On Thu, Jun 30, 2022, 7:50 AM Sandro @.***> wrote:

We need this for our network booted Pi 4s. Tow boot/UEFI is not done by
tomorrow and I don't see a reason to block this PR on that.
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/112677#issuecomment-1171244934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACP25BDWS2NDWRD3HC3SEDVRWQZLANCNFSM4XNVD4JQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

We need this for our network booted Pi 4s.

The boot.loader.raspberrypi options have never been needed, and are more harmful than beneficial. Since way before the introduction of the Raspberry Pi 4 those options have not actually been working as expected. They are present for legacy use of really old NixOS installs. The main change that matters here was done in by mid 2019.
Anyway, if they're network booted, then the boot.loader options shouldn't apply, no?

The boot.loader.raspberrypi options have never been needed, and are more harmful than beneficial. Since way before the introduction of the Raspberry Pi 4 those options have not actually been working as expected. They are present for legacy use of really old NixOS installs. The main change that matters here was done in by mid 2019

How else should you boot then?

Anyway, if they're network booted, then the boot.loader options shouldn't apply, no?

yeah, slight misunderstanding. We are using it for the one Pi we have that is not networking booting. All others are networking booting and don't require this.

When I installed the RPi4 with a NixOS 21.05 image and subsequently updated the kernel, I was in need of a new U-boot (#139865 iirc) which that configuration would have brought. I am afraid that this could happen again.

I agree that a solution has to be provided for that issue, but this is not it.
The boot.loader.raspberrypi gives the illusion of working correctly, but is easy to accidentally misuse, and could just as well break systems rather than fix them.
I do not know what the proper solution for handling platform firmware (U-Boot) updates is. It should not be tied to the NixOS generations lifecycle, as it cannot fulfill the guarantees from it.

abandoning, I've given on SBCs for now.


fixes #1120: support ES3 static member access restriction

Fixes #1120.

LGTM

Unfortunately, this will be blocked by https://github.com/eslint/eslint/issues/2075.

Should be good to go now with latest eslint release.

Why was this blocked by an ESLint issue? ESLint doesn't use Esprima.

ESPrima uses eslint.


feat: allow to set hostAliases for traefik pod

What does this PR do?
Allows to set host aliases in the traefik pod.
More

[x] Yes, I ran make test and all the tests passed

@youkoulayley could you please review this one?

@youkoulayley, please merge it if there are no other remarks/improvements that need to be implemented.

@mloiseleur @darkweaver87,  no pressure, but when can this PR be expected to be merged(I'm relying on this change due to migration to traefik v3)?

Thanks :+1: .
I think we are good to go. See my last minor suggestion.

@mloiseleur fixed

@mloiseleur, I didn't find any information about releasing new versions with chart improvements, only updates related to the latest version of Traefik (#625 ). How frequently are you delivering new artifacts to the registry with minor improvements/fixes, like this one and #1093, for example?


B.1.1.529 / Omicron

I didn't see an open thread for the variant yet so here one is. Apologies if this is not how you want to track a developing situation and how it might impact the models. Please let me know and I'll try to do stuff that way.
Why we might care
The new variant looks to already have dramatically increased transmission rates. It may also have some degree of immune evasion, though this is yet to be determined.
Rapid Strain Dominance
One clear fact is that this strain has has dramatically displaced Delta in regions of South Africa. Rates vary seem to be over 70% of new sequenced infections for November, though they are clear that the number of sequenced samples is quite low.
So, there is probably some reason why this strain is so successful, and that means we probably need to research it. It wouldn't be unreasonable for this to become the new dominant strain in the next few weeks.
Nature estimates the R in impacted areas of South Africa to be above 2.
Potential Causes
Transmissibility
Estimates vary wildly.  I have attempted to request these models and will update this if I get them.
There are a number of weird outbreaks that indicate increased transmissibility.

At a holiday party in Norway, half of attendees are confirmed positive. 30 of them were infected after the infection sources left the party.

There are a number of weird outbreaks which should not count as proof of increased transmissibility, only of terrible policy

On the unfortunate Netherlands KLM Flight the passengers were left inside an airplane with no mask enforcement for 5 hours. It is unclear that this situation would have ended much better with previous variants.
Another flight to the Netherlands where people were packed in a waiting room

Immune Evasion
A lot of people are tremendously excited about the number of mutations on this variant and how this might theoretically impact immunity evasion. I have no found any evidence of real-world data to make decisions on at this time.
The public health department of South Africa expects this to be an issue.
This preprint thinks natural immunity might work less well against this variance, especially from an initial Delta infection.
Another preprint discusses how it is possible that the virus sampled in other genetic material, which might give it better immune evasion.
A third preprint indicates "extensive immune escape" in cell experiments. Since the document is distributed in a 7z, and since I was delayed in getting an official copy by site uptime, I am going to also attach the paper in a follow-up comment.
History
Though the variant has been sourced from other places, most of the data and science comes from South Africa.
South Africa has had an uptick. Estimates of this are confusing and vary wildly. Worldometers has a compartively modest uptick over the past two weeks going from about 300 infections a day to 3000 infections a day.
Whereas, unless I am reading this wrong or have the wrong source for the local department of health, the impact in Gautang alone has included numbers that say there were well over 10K new infections on one of these days.
A reminder: whatever the cause of this is, it is likely not seasonal. It is the beginning of summer in the Southern Hemisphere.

Thanks for opening this ticket. I agree that the preliminary data on Omicron is concerning but, as you stated, data is still fairly scarce. Your help in tracking research as it comes out is very much appreciated.

Given that we are seeing an R above 2 in some areas, how far Omicron has already spread, and the number of people who check the calculator often, it might make sense to add a disclaimer that these models are not updated for Omicron and that caution is advised as the situation develops.
By the end of next week, people in many major cities will be operating in a different and unknown risk regime, and I think we should be clear about that even if we can't fully update the models immediately.

So glad this issue already exists, and I agree with the last comment—people at least need to know to beware that Omicron is not yet covered for their holiday planning.

We have a preprint indicating "extensive immune escape" for vaccinated individuals in a cell experiment. I think it is critical that we approve this pull request to update the header. We need to warn people that this model is likely out of date so they can adjust their holiday plans. Due to previous uptime issues with the signallab site, I am uploading a copy of the paper here as a backup.
Preprint of a Sigallab paper that concluded there is "extensive immune escape" for vaccinated individuals Official copy (normally) available at https://sigallab.net/

Merged.
On Thu, Dec 9, 2021 at 11:37 AM bluehat @.***> wrote:

We have a preprint indicating "extensive immune escape" for vaccinated
individuals in a cell experiment. I think it is critical that we approve
this pull request to update the header. We need to warn people that this
model is likely out of date so they can adjust their holiday plans. Due to
previous uptime issues with the signallab site, I am uploading a copy of
the paper here as a backup.
Preprint of a Sigallab paper that concluded there is "extensive immune
escape" for vaccinated individuals
https://github.com/microCOVID/microCOVID/files/7687934/MEDRXIV-2021-267417v1-Sigal.pdf
Official copy (normally) available at https://sigallab.net/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microCOVID/microCOVID/issues/1226#issuecomment-990170901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM25LOE3QSCMRBAOH4FES3UQEAPJANCNFSM5I4635RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

We have a plausible first guess for vaccine evasion. People are firming up Christmas and New Year's plans, and so I think integrating these early findings into the model makes sense.
The UK Health Agency survey study has relatively few AZ samples, but guesses that it has the same immunity as Pfizer: 30% - 40% immunity for unboosted and 70%-80% for boosted.
I think we should update all full-dose vaccines to 35%. We do need a more nuanced way to input boosters long-term. However, short term, we can add an additional dosage number field labeled "any booster" that brings immunity to 75%.
Because this is a pretty big change in the model, I'm posting this here for comment before coding up a pull request.

Thanks for finding this. Could you include research links? We'll need to
update the whitepaper at the same time as the model.
On Mon, Dec 13, 2021 at 7:55 PM bluehat @.***> wrote:

We have a plausible first guess for vaccine evasion. People are firming up
Christmas and New Year's plans, and so I think integrating these early
findings into the model makes sense.
The UK Health Agency survey study has relatively few AZ samples, but
guesses that it has the same immunity as Pfizer: 30% - 40% immunity for
unboosted and 70%-80% for boosted.
I think we should update all full-dose vaccines to 35%. We do need a more
nuanced way to input boosters long-term. However, short term, we can add an
additional dosage number field labeled "any booster" that brings immunity
to 75%.
Because this is a pretty big change in the model, I'm posting this here
for comment before coding up a pull request.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microCOVID/microCOVID/issues/1226#issuecomment-993132684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM25LPCGMJRZT6F2V4NYQLUQ253NANCNFSM5I4635RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

https://www.imperial.ac.uk/media/imperial-college/medicine/mrc-gida/2021-12-16-COVID19-Report-49.pdf as reported on in the FT.

Thanks.
Am I reading this correctly - the chart on page 7 lists negative Vaccine
effectiveness for 2 doses of AZ and 1 or 2 doses of Pfizer?
On Sat, Dec 18, 2021 at 3:18 AM Sumana Harihareswara <
@.***> wrote:

https://www.imperial.ac.uk/media/imperial-college/medicine/mrc-gida/2021-12-16-COVID19-Report-49.pdf
as reported on in the FT https://archive.md/0QjvI.
—
Reply to this email directly, view it on GitHub
https://github.com/microCOVID/microCOVID/issues/1226#issuecomment-997187753,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM25LKHS5JB6XVKXQ6NI2TURRUYBANCNFSM5I4635RA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

In case it helps, Technical Brief 32 is now out from the UK, pub date December 17th.
Starting on page 20 there's a summary of household and non-household attack rates for Omicron vs Delta is presented, based on 777 Omicron cases and UK contact tracing data. Confidence intervals are in there. The paper cautions against conclusions due to the small sample size so far.
The preliminary conclusion is ~2.9x odds ratio of household transmission for Omicron vs Delta, with similar ratios for non-household transmission. The paper says this number is "adjusted for ... vaccination status" but it didn't provide any other details of the adjustment that I could find.


added filter example

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/7989

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 7062ac7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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

@tseward

@Kateyanne Please merge this PR. Thanks

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 3977eac:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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 59a74ad:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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 59a74ad:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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

closing/re-opening PR. Build failed on exceptions twice within a 30 minute period.

Docs Build status updates of commit 59a74ad:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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

@Kateyanne

Docs Build status updates of commit 522213c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

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


Unhandled Stream error in pipe

trying to apply a test swagger.json gives me Unhandled stream error in pipe. I tested it as valid json so I'm not sure?
github doesn't support json or i'd upload it. lol

Hey!
Can you mail me that<EMAIL_ADDRESS>

Yeah, I imagine it may be a bad file, sorry if it is.. I didn’t make it. So, sorry if it’s our fault. Thanks! Cool project

On Nov 16, 2017, at 3:41 AM, Valentin Roudge<EMAIL_ADDRESS>wrote:
Hey!
Can you mail me that<EMAIL_ADDRESS><EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/leboncoin/morphlingjs/issues/6#issuecomment-344868627, or mute the thread https://github.com/notifications/unsubscribe-auth/ABY06WXbcQ8EzNKrNARX3JLfrCCWFpXEks5s3ANLgaJpZM4Qcg2c.

Don't worry. It's still at an early phase project, so we're looking at swaggers to improve it.


core(docs): adding ionic to command name

@perrygovier We shouldn't even need to commit the docs to this repo, right?

no, the change to scripts/createMarkdownDocs.ts is still necessary, but the entire docs directory should be safe to ignore

merged--not sure why github can't detect this


sink/(ticdc): Restructure codec files

What problem does this PR solve?

Issue Number: ref #6797
What is changed and how it works?

Move source files for each codec format into individual packages.
Move out codec directory from mq package because cloud storage sink also needs this codec package.

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/check-issue-triage-complete

/check-issue-triage-complete

/cc @hi-rustin
/cc @asddongmen
/cc @3AceShowHand

Codecov Report

Merging #6796 (1500b89) into master (2ea67ba) will increase coverage by 0.8219%.
The diff coverage is 70.6211%.

Flag
Coverage Δ

cdc
67.5529% <70.6015%> (+1.6848%)
:arrow_up:

dm
51.9986% <72.0000%> (-0.0431%)
:arrow_down:

engine
63.0539% <ø> (+0.5178%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6796        +/-   ##
================================================
+ Coverage   59.2138%   60.0357%   +0.8219%
================================================
  Files           780        783         +3
  Lines         88405      89445      +1040
================================================
+ Hits          52348      53699      +1351
+ Misses        31415      31015       -400
- Partials       4642       4731        +89

/run-all-tests

What is the difference between common and internal?

They are created for different purpose:

The reason why internal package is created is that some structs and functions are used in codec package internally.
The reason why common package is created is that: if we put move the files in common dir to sink/codec dir, there will be an import cycle.

/merge

Thanks for working on this.

/run-leak-test

/run-leak-test


Why decodable mapping without closure?

First of all thanks to this repository. I've been using mine for several months in my application. Not so long ago, you updated the code to the 4th version of the language. Adding support for the new protocol Decodable:
func map<D: Decodable>(_ type: D.Type, atKeyPath keyPath: String? = nil, using decoder: JSONDecoder = JSONDecoder()) throws -> D {
//...
        do {
            return try decoder.decode(D.self, from: jsonData)
        } catch let error {
            throw MoyaError.objectMapping(error, self)
        }
}

In my opinion, this function will be more convenient if the decoder is a closure:
func map<D: Decodable>(_ type: D.Type, atKeyPath keyPath: String? = nil, using: ((JSONDecoder) -> ())? = nil) throws -> D {
//...
        let decoder = JSONDecoder()
        using?(decoder)

        do {
            return try decoder.decode(D.self, from: jsonData)
        } catch let error {
            throw MoyaError.objectMapping(error, self)
        }
}

Although, you can create another method, because there is one drawback: there is no way to return a new object in the closure. But this can also be corrected by making a closure:
func map<D: Decodable>(_ type: D.Type, atKeyPath keyPath: String? = nil, using: ((JSONDecoder) -> (JSONDecoder))? = nil) -> Self? {

        //..
        var decoder = JSONDecoder()
        if let closure = using {
            decoder = closure(decoder)
        }
        do {
            return try decoder.decode(D.self, from: jsonData)
        } catch let error {
            throw MoyaError.objectMapping(error, self)
        }
}

Hey @SeRG1k17, thanks for opening this issue. Why do you believe that this parameter needs to be a closure, (JSONDecoder) -> (JSONDecoder)? I'm not sure I see what you're trying to accomplish


Import users script

Do you have even a bullet-point idea of how to approach this?
Is it purely using Admin SDK APIs, or do you foresee needing to massage the data in some way?

@gregfenton The users can be imported via the Admin SDK. There isn't a need to do any kind of data manipulation for it.

What about handling of the hashed passwords?  How does that work?  What parameters would I need to specify in order to import the password hashes correctly to the new location?

Excellent! So we've already begun the work for this issue! 😄

Import script is available in a separate repo


Query should validate that the aggregate function works on the field data type

For instance, if the user tries to compute a mean against a field that is a string, the query should return an error that says they can't do this.
We also need to implement all numerical aggregates for int64 in addition to floats. It would probably be best to keep a map of which data types each aggregate function is able to process.

It might be cool to have an option to SKIP_INVALID_TYPES so that if I write a point with string when all other values are ints/floats I'll still be able to get a meaningful result that skips the string without any error message.

You can't write with different types. Once you've written the first value
for a given field on a measurement, all future values for that field on
that measurement must be the same type.
On Wed, Mar 4, 2015 at 8:49 AM, Władysław Bodzek<EMAIL_ADDRESS>wrote:

It might be cool to have an option to SKIP_INVALID_TYPES so that if I
write a point with string when all other values are ints/floats I'll still
be able to get a meaningful result that skips the string without any error
message.
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/1845#issuecomment-77195631.

What about nans? IOW, how are missing values marked/handled? Some applications may want to record missing values to keep track of time itself.

@pauldix
[OT]

so is this change introduced in 0.9? I'm using 0.7 and it doesn't have this check.
What is the type granularity? If I push something that looks like int and then float will this get rejected?

closing in favor of #3818


Include rewired nodes when calculating Modified Flows stop list

Fixes #4752
This adds 'rewired' nodes to the list that get stopped on Modified Flows type deploys.
When testing locally, I found some other odd behaviours caused by not including this list of nodes. For example:
Starting with:
[A] -> [B] -> [C]

then deleting the wire between B/C:
[A] -> [B]    [C]

Caused the runtime to restart nodes A and C, but not B (as B was considered 'rewired' whereas A and C were considered 'linked'). That's just wrong.
Makes sense to restart anything and everything that has been touched by a modification.

Another question from the author that also bothers me is why this mode doesn't restart all nodes in that flow? I mean that's the description of this mode. Because it's the same as Modified Nodes mode (not from a code point of view). Unless the description is not correct?

Depends what you mean by 'flow'. Modified Flow means any nodes that have changed and any nodes that are connected to them. It does not mean Flow as in the entire tab in the editor.

Thanks, and for Modified Nodes? I'll have to find a more appropriate translation 🤔


integration tests for /api/studyplans + configure pipeline to run during pr

This PR:

implements integration tests for /api/study_plans endpoint - this will serve as a template for future tasks relating to API testing
configure CI Pipeline to run tests during pull requests

closes https://github.com/stamford-syntax-club/stamfordcenter-backend/issues/13

FFTM

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

Feel free to merge @chinathaip XD

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

Feel free to merge @chinathaip XD

555555555555555555555555555555 aight aight


SIGINT (Exiting RootWindow's Run Method)

Conventionally, console applications respond to CTRL+C as a SIGINT signal and not as keyboard input.
SIGINT can be intercepted by an application so that it can perform a clean exit.
Windows doesn't have many examples of interactive console applications, but one example is the text editor Vim. Upon intercepting a SIGINT Vim prompts the user to exit the program by using its quit syntax:

On Linux, there are many examples of console applications which respond to SIGINT, such as:

htop (interactive process viewer)
Mutt (email client)
Lynx (text web browser)
GoAccess (web log analyzer)

Ideally NSCI would give the programmer the option to simply ignore SIGINT or to take some action.

I have added an options parameter to the RootWindow constructor that controls this.

@LokiMidgard Using the latest commit, I get the following error on the Run method of RootWindow:
Exception calling "Run" with "0" argument(s): "This property has already been set and cannot be modified."

I've added this line
https://github.com/LokiMidgard/NSCI/blob/9361d5fc777a4bd82880b3e6180e9f65ed969346/NSCI/UI/RootWindow.cs#L179
In my tests this runs without problems, are you setting a Thread name somewhere explicit?

Hm...
in PowerShell the thread is already named Pipeline Execution Thread. Hope that this does make more problems.

That has fixed the error, but I cannot get ctrl + c to work in PowerShell.
I have implemented the following, but when pressing ctrl + c nothing happens:
$NsciOptions = [NSCI.UI.NsciOptions]::new()
$NsciOptions.TreatControlCAsInput = $False
$Root = [NSCI.UI.RootWindow]::new($NsciOptions)

It works fine for me in C# though:
var NsciOptions = new NSCI.UI.NsciOptions
{
    TreatControlCAsInput = false
};

var root = new NSCI.UI.RootWindow(NsciOptions);
var grid = new Grid();

Any ideas? Does it work in PowerShell for you?

Unfrotunatly I have no idea. The CanleKeyPress call back is used, but it does not matter if ConsloeCancelEventArgs.Cancel is false or true. the console application does not stop.
I'm not sure whit the scripting stuff, maybe ctrl-c would terminate the process, but there was no process started. So only the executed function is terminated, but not additional threads that were spawned like UI and input thread.  If that would be the case, then you would need to handle OnCancelPressed yourself and call Detach on the RootWindow.

I've noticed wired behavior when the application was terminated via esc input behaves strage after that.
Most likely the input thread was still running. It was actually an endless loop, that was intended to live as long as the process. And when the process was killed it should vanish. But this did not happen in PowerShell.
I no explicitly stop the Thread if the app was stoped like the UI thread before. However The thread is most likely currently blocking in Console.ReadKey() when the app is stoped. And thus the first key pressed after termination will be consumed.
So, for PowerShell you must handle the Ctrl+C command with a Detach yourself.

@LokiMidgard OK, I have handled ctrl + c by assigning a ScriptBlock to OnCancelPressed which calls the Detach method of the RootWindow:
$NsciOptions = [NSCI.UI.NsciOptions]::new()
$NsciOptions.TreatControlCAsInput = $False
$NsciOptions.OnCancelPressed = {$Root.Detach()}
$Root = [NSCI.UI.RootWindow]::new($NsciOptions)

ctrl + c now exits the script but there are two problems...
Problem 1:
After exiting, you must now press a key twice before it is displayed on the console window. EG, if you want to type the letter A, you must press the A key twice.
Problem 2:
When NSCI exits it clears the console buffer. This is not the expected behaviour for a console application. When a console application exits, any output present on the console prior to it starting should be preserved when it exits. Try any console application on Linux and you will see this is the standard behaviour (EG. vim, htop, Mutt, etc).
Possible solution:
There are two types of screen buffer - the Normal Screen Buffer and the Alternate Screen Buffer. This is a standard found in almost all consoles/terminals, so it should work in almost any console on any operating system. When a full screen console application is invoked, it should use the Alternate Screen Buffer. When the application exits the console will return to the Normal Screen Buffer. So NSCI should be using the Alternate Screen Buffer.
Here is some information on the Alternate Screen Buffer:

Thomas Dickey - The Alternate Screen Buffer
Microsoft - Console Virtual Terminal Sequences

If NSCI used the Alternate Screen Buffer it should fix problem 2 and it might also fix problem 1.
I can do some more research into implementing Alternate Screen Buffer in a C# application. I would be interested in your thoughts...

@LokiMidgard Your commit to terminate input thread when application stops (https://github.com/LokiMidgard/NSCI/commit/48336a47a430eea6ee6feea4b7c361143adccea6) has fixed problem 1 in my last comment.

If this would work, it would be nice. But as far as I know the C# Console class is quite limited. I haven't found any method to switch to an alternative screen buffer. Also escape sequences to manipulate the console don't work. (e.g. "\x1b[31mThis text has a red foreground using SGR.31.\r\n")
I have disabled Console.Clear() as you suggested.

@LokiMidgard Your commit to terminate input thread when application stops (48336a4) has fixed problem 1 in my last comment.

I still have this problem for the first charakter I type after termination. Maybe I need to operate on the inputstream directly instead of using the Console.ReadKey() method. I need to check this out another time.

Sorry, I don't think the changes in https://github.com/LokiMidgard/NSCI/commit/f62db0e6f8bd3d3daefd244a73c4fb55e7b540ad are a good idea.
I think its better to revert those changes and implement Alternate Screen Buffer instead.
VT escape sequence support has existed in *nix forever. In Windows, it was introduced into conhost in the Windows 10 Anniversary Update: https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences
The reason the VT escape sequence was not working for you is because you have to explicitly enable Virtual Terminal Processing for the Windows console.
Please see this example: https://github.com/thecliguy/NSCI/commit/d21d3924082460312c993b584d7406294a7aa08b, where I have

Added support for Virtual Terminal Processing.
Enable Alternate Screen Buffer when RootWindow is run.
Enable Normal Screen Buffer when RootWindow is exited.

It is not the best code because I am not a C# developer.
There is one problem with the code, colours do not work:


STM32F0xxGxUx and QFN-28-ST

Adds a library part for the STM32F0xxGxUx and an associated footprint for the QFN-28-ST. Footprint was initially generated using build-mod-ic, but was then hand edited to account for the chamfered corner pads required by the data sheet. These are currently implemented as a set of identically numbered pads as shown in the third image below. Kicad seems to accept this and the footprint seems to operate correctly. It does not violate DRC with a 0.2mm clearance as standard. It does identify the extra pads as unconnected sadly. I'm looking to see if anything can be done about this, but I suspect not until Kicad supports polygon pads.
Datasheet

Have worked out a new arraignment of overlapping pads which does not produce the same unconnected warnings, will update the PR later today with a new footprint.

Done

Thanks!


Reuse CountDown in SkipLast

I renamed CountDown to Countdown.

Something more before merge?

By implementing SkipLast in terms of CountDown, this PR also adds all the optimisations built into CountDown.


Update Ubuntu package repo versions

Was required to fix container image builds: before and after

CI isn't looking great. I think SMS is near capacity


Restructuring of $DE00 area, gaps, labels.

Hi Claus!
From the log: Added comments for cartridge handling, ROM callouts, partially for some commands.
I hope this might be helpful and acceptable as a contribution to your work. I've also changed the header slightly to reflect the progress.
Best,
Johann

BTW, I've checked to source with ACME to produce the image which successfully matches the original ROM image.

Hi Johann,
I have merged your pull request into my code. Thanks for your support.
Claus


Update playsuisse.py

Improve PlaySuisse extractor: enhance episode naming and error handling

Modified episode naming to include series name: "Series Name - Episode Name"
Added robust error handling to prevent NoneType errors
Improved playlist handling for series with multiple episodes
Enhanced data validation in _extract_single method
Updated _real_extract to handle potential None returns from _extract_single

These changes improve the reliability of the extractor and provide more informative file names for series episodes, making content easier to identify and organize.
IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

ADD DESCRIPTION HERE
Fixes #
Template

Before submitting a pull request make sure you have:

[ ] At least skimmed through contributing guidelines including yt-dlp coding conventions
[ ] Searched the bugtracker for similar pull requests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

please review & complete the PR checklist and fix the ruff errors


[Ferature request] add examples.

Ahoj,
thanks for this software.
I did not really work out how this exactly works.
I suggest a feature request for the documentation to add examples:

One directory /usr/share/doc/genmonify/examples/ which contains ready-made example configuration,
in the usage section of the README.md one example with a concrete module showing step by step what do to.

For me it is not clear what holds as a valid "module" for genmon; xfce4-genmon-plugin is a plugin which just shows stdout of a command one can specify manually so I can enter any complex command I want in the preferences dialogue of the plugin.
Regards!

there is a guide (2 steps) and an example in the readme.
One thing I use this for is to display the window title of the active window. Sure i could do this by just adding a command in genmon which would output the active window title. But the problem is that genmon works on a set interval, and i don't want to check for and print the window title every second, that would be wasteful, and also get weird if the title changes faster than than the interval. Instead I have a script that watches for window title/focus change and when that occurs it triggers genmonify -o windowtitle "$title".


Adding an on_update method to the WindowHandler

I didn't found any solution to execute a function each tick of the  the WindowEventLoop.
Is that possible to add an on_update() method to the WindowHandler trait. Or is it a more simple solution.
For now, the only solution I have found is to call the update function from the on_draw() method but this solution is not optimal because the window have to be redrawn each tick.

Thanks for the request. The Speedy2D event loop only wakes up when something happens (e.g. a mouse movement or a redraw request), so it doesn't tick in the background (it just remains idle).
If you'd like to perform a regular action in your app, one solution would be to spawn a new thread, which periodically sends a user event to the main thread. For example:
fn on_start(&mut self, helper: &mut WindowHelper<String>, _info: WindowStartupInfo)
{
    let event_sender = helper.create_user_event_sender();
    thread::spawn(move || {
        loop {
            // Send an event every 10ms
            event_sender.send_event(MyEvent{}).unwrap();
            thread::sleep(Duration::from_millis(10));
        }
    });
}

The WindowHandler::on_user_event() callback will be invoked every time send_event() is called. See the user_events.rs sample code for an example of this :)

Thanks, it works well.


Current master does not work

The current master is kind of broken.
Since the update to lodash it does not run git commands on my system anymore and the 'file container' crashes. (Haven't inspected further right now).

This is at least based on the fact that the language server implemented is not compiled and therefore could not be started. How to compile the server?


Access the package's component using ref

Hi, I want to get the leaves by clusterId. I saw the code and it seems the only way to access the leaves is by onClusterPress method. I want to access the leaves without having to click on the cluster marker. Is there any way to do so?
I tried adding ref prop to the component but it didn't work.
The clusterEngine should be accessible as it is in the 'react-native-maps-super-cluster' package. It can either by by ref or by exposing a function that would return the cluster engine variable. It will help to access and get the properties directly in case it's not exposed by the package.
Request the contributor to add the functionality.

Hi @nikhilkumar6
In version 3.3.3 I added support for superClusterRef prop that gives you easy access to supercluster instance.
This is example how to use it:

import React, { useRef } from "react";
import MapView from "react-native-map-clustering";

const App = () => {
  const superCluster = useRef();

  return <MapView superClusterRef={superCluster}>
    {/* markers */}
  </MapView>;
};

export default App;

If you want to get all markers inside cluster you can call a function like this:
  const markers = superCluster.current.getLeaves(cluster.id, Infinity);

Thank you for contributing 💖


WebKitBrowser json and md file Updated as per code

Documentation Enhancement For WebKitBrowser Plugin
jira : https://ccp.sys.comcast.net/browse/RDK-35061

Change looks good to me. @HaseenaSainul @MFransen69  could you please take a look a well?
On a side note, WebKitBrowser.json gets overridden on every configuration. Not sure when it was added. Maybe it could be moved to a doc folder. @jruzzi is this something you could work on?

@svenka471 please create PR to 2201 sprint first. The change would have to be cherry-picked to main after RM approval

I see all the rdkservces plugins contain .json in the plugin folder, which is overridden on configuration time

@emutavchi , it seems fine for me. But would like to add Ozgur also in the review list. Currently I am not able to select.

@svenka471 please create PR to 2201 sprint first. The change would have to be cherry-picked to main after RM approval

PR created to 2201 sprint : https://github.com/rdkcentral/rdkservices/pull/2127

@svenka471 - Is this good to be merged to main?

Changes already merged to main. Closing PR.


Image on GHCR is private and image on Docker Hub is not up-to-date

The GHCR image is private and the last  update to the publicly available image on Docker Hub was last year which contains odc-stats version 1.0.35.

I think @alexgleith is looking into this.

Made it public now :-)


add a report-allocation sub command

This lets you send slave allocation metrics to graphite!

The last commit fixes the failing travis build here
The failure is due to upstream go-marathon library changes specifically, this pull request


The problem of generating SExpr expression

Hi,
After running python parse_sparql_webqsp.py program, SExpr expression will be generated, but there is null in the reproduced result. Is this reasonable?
Thank you for your assistance.
Best regards.

It's reasonable. Because the annotation data of sparql in this sample is manually written, an error will occur when converting to sexpr. However, chatkbqa can cover the conversion of this natural language problem according to the generalization ability generated by the learning of other samples.

Thank you for your timely answer.


Add socat to builds

The build images don't seem to have socat installed, which is incredibly handy for doing network routing between containers.  I propose that socat be added to the images.

From https://registry.hub.docker.com/_/buildpack-deps/:

In spirit, buildpack-deps is similar to Heroku's stack images. It includes a large number of “development header” packages needed by various things like Ruby Gems, PyPI modules, etc. For example, buildpack-deps would let you do a bundle install in an arbitrary application directory without knowing beforehand that ssl.h is required to build a dependent module.

So, while socat is useful, it isn't a common requirement of language-specific package management systems.

Closing old issue, if you feel this was closed in error please let us know.


$select inside $expand example

unit test examples for $expand with $select on collection and 1:1 as discussed in #578 and #136
$expand=Photo($select=Name)
$expand=Friends($select=UserName)
also fixes the invalid Person.Photos reference

Sorry for the long delay. Merged now.


⚠ Bofrost.fr has degraded performance

In 7587111, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2628 ms

Resolved: Bofrost.fr performance has improved in 684ed5c after 6 minutes.


Unchecking "viz" for an anchor doesn't remove it from ipyanchorviz

Unchecking "viz" does not appear to have any effect
Likely connected to https://github.com/ORNL/ipyanchorviz/issues/6

Fixing the linked ipyanchorviz issue successfully resolved this issue as well


[WIP] droplets: Update snapshot id

The new snapshot is created after upgrading the base droplet from the legacy 20$ a month plan to newer $10 a month plan. RAM is the same 2GB as in old plan but SSD capacity is 50GB instead of the 40GB.

Okay. This does not seem to be working. New droplets are still being created from the older plan. I think I need to create a new base droplet in newer plan to make this work.

That makes sense; let me know once this is ready.

@hackerkid this is obsolete, right, since we just rebuilt the snapshot on Bionic?


[WIP] [DO NOT MERGE] Adding tests for ZF3 Zend\EventManager

Stuff Todo

[x] \Zend\EventManager\Exception\RuntimeException
[x] \Zend\EventManager\Factory\ListenerPluginManagerFactory (ignore)
[x] \Zend\EventManager\Event
[ ] \Zend\EventManager\EventManager
[x] \Zend\EventManager\ResponseCollection

@bakura10 I have a query on how to be lazy...
<?php

// ... blah

class EventManagerTest extends \PHPUnit_Framework_TestCase
{
    // ... snip ...

    public function testLazyInstantiator()
    {
        $hasBeenTriggered = false;

        $myEventListener = function (Event $event) {
            $hasBeenTriggered = true;
        };

        $eventManager = new EventManager(function ($requestedListener) use ($myEventListener) {
            $this->assertSame('MyEventListener', $requestedListener);
            return $myEventListener;
        });

        $eventManager->attach('MyEvent', /* what is this supposed to be to be lazy??? */);

        // I tried:
        //  - ['classname', 'function']
        //  - [this, 'function']
        //  - ['something', function (..) {.. blah ..}]
        // etc. with various errors, e.g. when trigger() is called it complains about $listener...

        $event = new Event();
        $eventManager->trigger('MyEvent', $event);

        $this->assertTrue($hasBeenTriggered);
    }
}

https://gist.github.com/asgrim/60c73a0fffab11c60528

@asgrim I guess ['classname', 'function'] is the desired way. What error do you get when trying this?

Yes - sorted now, I chatted with @bakura10 last night - I'm working on it later, but basically if it's ['classname', 'function'] it gets classed as lazy, so the lazy instantiation kicks in... if it is [$alreadyAnInstance, 'function'] it does not need to. :D (see the gist in my last comment btw for a working test)

:+1: ok cool

ping @bakura10 - ready for review/merge/feedback :tada:

I've rebased to your refactor branch also

Looks nice!
Some tests are missing:

Test wildcard listeners
Make sure that wild card listeners of same priority are always triggered AFTER the named event (so if one listener is attached to event "my.event" with priority 1 and one listener is attached to event "*" with priority 1, listener attached to "my.event" must be exeucted before, even if it was attached after the wildcard.

yes I can add these (possibly not tonight as going to a UG meetup, depends how late I get back)

I'm going to merge that, you'll can add the missing tests in another PR :D.

np


media keeps original file open.

when I send a video and job will done "media" will not release original file and can not remove it.
I sent a video and after that try to remove original video but exception acquired and tells me that the file is in use with another process.

the unit tests are passing successfully, so I suspect the problem is on your side and not the client itself
can you show your code ?

yes of course:
try                                     {                                         var client = new BaleClient(token);                                         _ = client.Attachments.SendVideoAsync(id,Media.FromDisk("wwwroot/test/video.mp4"), message.Caption ?? string.Empty).Result;                                     }                                     catch (Exception ex)                                     {                                         System.IO.File.AppendAllText("wwwroot/test.txt", DateTime.Now + " error has been equired from sending bale! error = " + ex.Message + '\n');                                         _ = botClient.SendTextMessageAsync(meid, "Failed!\n" + "Error from sending bale! error = " + ex.Message + "(/cancel)" + '\n').Result;                                         if (message.Chat.Id != meid)                                             _ = botClient.SendTextMessageAsync(message.Chat.Id, "Failed error has been equired from sending bale! error = " + ex.Message + "(/cancel)" + "\n").Result;                                         return;                                     }                                     if (System.IO.File.Exists("wwwroot/test/video.mp4"))                                         System.IO.File.Delete("wwwroot/test/video.mp4");

calling the .Result is potentially the problem here, try using await instead
let me know if the problem still persists

method send the video correctly. the issue is that i can't remove the original file after that.

"System.IO.File.Delete("wwwroot/test/video.mp4");"
this line get a exception and tells me the file is in use by another process.

try again and let me know if the issue was solved

thanks. yes the problem solved. and i am surprised that doesn't need to use "using()" for media and Send method disposes media automatically.does it effect all send methods like "SendVideoAsync" , "SendPhotoAsync" and "SendDocumentAsync"?
and I would be very grateful if you update package on nuget too.

yes, every Send method in (IAttachments)[https://github.com/MrAliSalehi/Bale.Net/blob/master/Bale.Net/Interfaces/IAttachments.cs] API now will dispose its content automatically, except for SendContact & SendLocation because they are just raw query parameters and doesn't have any actual "body"
and nuget updated to version 1.0.3


kube 1.16 support - no matches for kind "StatefulSet" in version "apps/v1beta2"

I tried installing v0.4.2-dirty+85.gc6d71da5 on kube 1.16.2 via helm2/tiller and it failed with:
2019/10/31 00:03:34 cf-operator command failed. Failed to create new manager.: failed to add controllers to manager: Watching Statefulset failed in Statefulset cleanup controller.: no matches for kind "StatefulSet" in version "apps/v1beta2"

@drnic we're not planning to support 1.16 before 1.0 (December).
Is this a high priority for you?

Not a priority. Just a discovery when I was hand crafting a 1.16 cluster.
Dr Nic Williams
Stark & Wayne LLC
http://starkandwayne.com
+61 437 276 076
twitter @drnic

@viovanov Did you know Ephemeral Containers are alpha in 1.16.
Should we re-prioritize supporting 1.16 for pre-1.0 to get debug containers for problem analysis?

I believe this was fixed by 57bec03f and 1adb2cd4

I believe this was fixed by #728 and maybe 1adb2cd

Can confirm. We have been using 1.16 for a while now.


trouble with running the example

Hi,
I was just trying to play a little with causal graphical models so I started with the provided example.
I ran:
sprinkler = CausalGraphicalModel(
nodes=["season", "rain", "sprinkler", "wet", "slippery"],
edges=[
("season", "rain"),
("season", "sprinkler"),
("rain", "wet"),
("sprinkler", "wet"),
("wet", "slippery")
]
)
draw return a graphviz dot object, which jupyter can render
sprinkler.draw()
and get a long error message:
FileNotFoundError Traceback (most recent call last)
~\AppData\Local\Continuum\anaconda3\lib\site-packages\graphviz\backend.py in run(cmd, input, capture_output, check, encoding, quiet, **kwargs)
163 try:
--> 164 proc = subprocess.Popen(cmd, startupinfo=get_startupinfo(), **kwargs)
165 except OSError as e:
~\AppData\Local\Continuum\anaconda3\lib\subprocess.py in init(self, args, bufsize, executable, stdin, stdout, stderr, preexec_fn, close_fds, shell, cwd, env, universal_newlines, startupinfo, creationflags, restore_signals, start_new_session, pass_fds, encoding, errors, text)
774 errread, errwrite,
--> 775 restore_signals, start_new_session)
776 except:
~\AppData\Local\Continuum\anaconda3\lib\subprocess.py in _execute_child(self, args, executable, preexec_fn, close_fds, pass_fds, cwd, env, startupinfo, creationflags, shell, p2cread, p2cwrite, c2pread, c2pwrite, errread, errwrite, unused_restore_signals, unused_start_new_session)
1177 os.fspath(cwd) if cwd is not None else None,
-> 1178 startupinfo)
1179 finally:
FileNotFoundError: [WinError 2] The system cannot find the file specified
During handling of the above exception, another exception occurred:
ExecutableNotFound Traceback (most recent call last)
~\AppData\Local\Continuum\anaconda3\lib\site-packages\IPython\core\formatters.py in call(self, obj)
343 method = get_real_method(obj, self.print_method)
344 if method is not None:
--> 345 return method()
346 return None
347 else:
~\AppData\Local\Continuum\anaconda3\lib\site-packages\graphviz\files.py in repr_svg(self)
111
112 def repr_svg(self):
--> 113 return self.pipe(format='svg').decode(self._encoding)
114
115 def pipe(self, format=None, renderer=None, formatter=None, quiet=False):
~\AppData\Local\Continuum\anaconda3\lib\site-packages\graphviz\files.py in pipe(self, format, renderer, formatter, quiet)
136 out = backend.pipe(self._engine, format, data,
137 renderer=renderer, formatter=formatter,
--> 138 quiet=quiet)
139
140 return out
~\AppData\Local\Continuum\anaconda3\lib\site-packages\graphviz\backend.py in pipe(engine, format, data, renderer, formatter, quiet)
242 """
243 cmd, _ = command(engine, format, None, renderer, formatter)
--> 244 out, _ = run(cmd, input=data, capture_output=True, check=True, quiet=quiet)
245 return out
246
~\AppData\Local\Continuum\anaconda3\lib\site-packages\graphviz\backend.py in run(cmd, input, capture_output, check, encoding, quiet, **kwargs)
165 except OSError as e:
166 if e.errno == errno.ENOENT:
--> 167 raise ExecutableNotFound(cmd)
168 else:
169 raise
ExecutableNotFound: failed to execute ['dot', '-Tsvg'], make sure the Graphviz executables are on your systems' PATH
I restarted the kernel a few times and even the computer. Also as suggested in the error message, I added Graphviz to system path but it did not change anything.
Any hint on how I can resolve the issue?
Best regards

I finally installed Graphviz separately and this resolved the issue.
I am using windows 10 and apparently Graphviz has some issues on windows:
https://github.com/dask/dask-tutorial/issues/86


Fix replacement option in loss and gradnorm downsampling

There was an unused replacement option which defaulted to True, which caused multiple keys to be chosen, which caused the storage to crash since it cannot deal with multiple keys in its current implementation. However, it should not have happened in the first place.

let's just merge this I don't think any problem will be caused


porting: Add log for Puya PY32F0xx

Hi. Here is a porting report for Puya PY32F003 :)

Thank you @Zepan for quick review and merge! :)


https://reasonml.github.io/guide/language/function says below but variant already described earlier

The doc on functions claims variant isn't described yet but it was already.

Thanks! Really appreciate these attentions to details


Review AWS STRA with ISB Management

Describe the issue
A clear and concise description of what you want to happen.
Which Sprint Priority is this issue related to?
The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?
Additional context
Add any other context, attachments or screenshots
Definition of done
Identify what will need to happen/be delivered for this to be completely done

Reviewed and signed off by ISB members
-- incorporated feedback
closed as complete


suggestion: make outgoing particle packets async

morphan1 knows what im talking about

@Morphan1 how what

Async command! :D ?

From what mophan told me, the outgoing packets do not get handled async, and can still lock up the server even if it comes from an async queue, he told me he could change this

@mcmonkey4eva I talked to you at some point about it I think. particle packets are added to a queue that sends them per tick

@Morphan1 and the code is where?

@mcmonkey4eva somewhere around here http://git.mcmonkey.org/mcmonkey/mc-dev/blob/master/net/minecraft/server/NetworkManager.java#L129

Not sure what if anything can be done about this...
@Morphan1 do you have any idea?
To my knowledge queuing is unavoidable, except if there's multiple separate queues, in which case a few of the queues can be skipped.

Disregarding due to lack of explanation.
Also rather unnecessary.


Data about evaluation

Hi, thanks for your excellent work. As I am downloading the evaluation data, I have two questions.

The "testdev_balanced_predictions.json" in the GQA dataset looks like it should be the predictions?
What is the coco dataset in the MME? Since you only mention "Downloaded images to MME_Benchmark_release_version", I'm not sure if I need to download the coco dataset additionally? If so, what version of the coco dataset and can you provide a link to it?
Thanks again.

Thank you for your reminder. Regarding the first issue, the "testdev_balanced_predictions.json" file is the output file of the model and does not exist before evaluation. For the second issue, there is no COCO dataset under MME. Both issues were due to errors in our documentation, and we have now completed the corrections.

Thanks! And there are 900 gif data in ocr_vqa data, which will cause file corruption if converted directly, may I ask how you handle this?

Thank you for your reminder. Regarding the first issue, the "testdev_balanced_predictions.json" file is the output file of the model and does not exist before evaluation. For the second issue, there is no COCO dataset under MME. Both issues were due to errors in our documentation, and we have now completed the corrections.

Thanks! And there are 900 gif data in ocr_vqa data, which will cause file corruption if converted directly (like img.save(new_file_path, 'JPEG')). May I ask how you handle this?

Thank you for your response.


refactor: rename EntityListContent to EntityView

Changes

Rename EntityListContent to EntityView as we will support both grid and table views for tests/test suites
Add slots for the entity view component and also for the switch

Fixes

How to test it

screenshots

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Something is wrong with "Status" size on preview:


warning: attributes at the beginning of statement are ignored

/home/runner/work/osp-magnum/osp-magnum/3rdparty/longeronpp/src/longeron/id_management/registry_stl.hpp: In member function ‘IT_T lgrn::IdRegistryStl<ID_T, NO_AUTO_RESIZE, BITVIEW_T>::create(IT_T, ITB_T)’:
/home/runner/work/osp-magnum/osp-magnum/3rdparty/longeronpp/src/longeron/id_management/registry_stl.hpp:91:32: warning: attributes at the beginning of statement are ignored [-Wattributes]
   91 |             if (first != last) [[unlikely]]
      |                                ^~~~~~~~~~~~
/home/runner/work/osp-magnum/osp-magnum/3rdparty/longeronpp/src/longeron/id_management/registry_stl.hpp:101:18: warning: attributes at the beginning of statement are ignored [-Wattributes]
  101 |             else [[likely]]
      |                  ^~~~~~~~~~

Removed in c386ee6


server listening, client returns website

New to reactPHP and trying to set up on AWS EC2...
The PHP server side is listening... can telnet connect on the same server.
When I try the PHP client side, however, it receives the default HTTPS web page for the domain AND is not "seen" in the console on the server side. I'm obviously missing something.
EDIT:  using a javascript client, I get this:
WebSocket connection to 'wss://xxxxx.xxxxx.com/' failed: Error during WebSocket handshake: Unexpected response code: 200
Seems the requests are not being filtered on the server side, though both start connections on port 8000.  I still need to do something on the server... but what?
pointers (please)?

another edit...
been able to connect with PHP client but is horribly slow (one minute waiting) with this...
<VirtualHost...
ProxyPass / https://<IP_ADDRESS>:8000/
ProxyPassReverse / https://<IP_ADDRESS>:8000/
Still not a solution but getting closer, it seems.

Thank you for your reaching out, but unfortunately this question is somewhat beyond the scope of this project and I don't see how this could be answered without an in-depth understanding of your particular code.
As a first step, I would suggest making yourself familiar with the examples, the documentation and/or ReactPHP in general.
It looks like you may be looking for a WebSocket server? In this case, you may want to check out the excellent WebSocket server Ratchet which builds on top of ReactPHP. For additional help, you may want to check out the common community channels (such as IRC, StackOverflow etc.).
I hope this helps and you understand I'm closing this ticket for now. If your problem persists and you feel this is an issue that targets a broader audience, please comment back and we can re-open this. :+1: