Support automatic language identification when transcribing

Currently transcription requires specifying a language code:
https://github.com/amazon-connect/amazon-connect-salesforce-lambda/blob/master/sam-app/lambda_functions/sfSubmitTranscribeJob.py#L49
If no code is specified, pass IdentifyLanguage=True to automatically identify the language:
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/transcribe.html#TranscribeService.Client.start_transcription_job

Hello, I just wanted to let you know that have received this feature request and are looking into it. Thank you!


Annotation errors in QuasiStatic library

Reported by otter on 21 Jun 2014 15:03 UTC
Performing Check with Dymola on trunk/Modelica gives the following errors:
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceVoltageSource annotation the annotation 'Icon' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceVoltageSource annotation the annotation 'Documentation' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceCurrentSource annotation the annotation 'Icon' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceCurrentSource annotation the annotation 'Documentation' appeared multiple times.
Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave.Components annotation the annotation 'DymolaStoredErrors' is not standardized.
Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave.Utilities.VfController annotation the annotation 'Diagram' appeared multiple times.
Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave annotation the annotation 'versionDate, versionBuild' is unknown.
Please, before you submit models to the trunk, perform check and check with simulation.
I marked this as ElectricalQuasiStationary, because MagneticQuasiStationsary is not yet in the Component trac menu.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1524

Comment by dietmarw on 21 Jun 2014 15:28 UTC
This ought to be for 3.2.2 since Modelica.Magnetic.QuasiStatic.FundamentalWave seems to have been introduced for 3.2.2 and not in 3.2.1

Comment by christiankral on 23 Jun 2014 10:36 UTC
Fixed the issues of Modelica.Magnetic.QuasiStatic.FundamentalWave in 45217cb78cc32f1bf6af0f4f4eb8df0092c4db7f:

Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave.Components annotation the annotation 'DymolaStoredErrors' is not standardized.

Removed 'DymolaStoredErrors'

Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave.Utilities.VfController annotation the annotation 'Diagram' appeared multiple times.

Removed obsolete annotation 'Diagram'

Error: In class Modelica.Magnetic.QuasiStatic.FundamentalWave annotation the annotation 'versionDate, versionBuild' is unknown.

Removed 'versionDate' and 'versionBuild' since these annotations are not needed

Comment by christiankral on 23 Jun 2014 11:54 UTC
Fixed the issues of Modelica.Electrical.QuasiStationary.MultiPhase in 597a8bb86e73a2718e9f6ea87ab603917acbba33:

Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceVoltageSource annotation the annotation 'Icon' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceVoltageSource annotation the annotation 'Documentation' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceCurrentSource annotation the annotation 'Icon' appeared multiple times.
Error: In class Modelica.Electrical.QuasiStationary.MultiPhase.Sources.ReferenceCurrentSource annotation the annotation 'Documentation' appeared multiple times.

Removed additional annotations 'Icon' and 'Documentation'

Comment by ahaumer on 8 Jan 2015 09:55 UTC
inspected trunk, already fixed

Comment by beutlich on 29 Oct 2015 15:19 UTC
Do no longer hide development tickets. Instead leave the Release Notes empty.


Add a new StackedBar chart

This change adds a separate StackedBar type of chart.
I did consider modifying the main Bar chart to just take multiple data arrays as input, but decided that it was better create a separate chart type, as it seems likely that you might want to have some sort of "side-by-side" bar chart in the future.
I also updated the example for the bar chart so that the title and axes made sense.
Screenshot before and after this change

@matt3play Firstly, thanks for your work!
For stacked bar chart, I am thinking, it might be better if legend and color are also added as how the pie chart behaves.
Because if no legend is provided, the stacked bar might look a little confusing before the mouse hovers on the bars

Good point!
I've got a PR up with tooltips, but adding a legend makes sense too.  Maybe
as an optional add-on
On Fri, Nov 29, 2019, 12:00 AM Tim Qian<EMAIL_ADDRESS>wrote:

@matt3play https://github.com/matt3play Firstly, thanks for your work!
For stacked bar chart, I am thinking, it might be better if legend and
color are also added as how the pie chart behaves.
Because if no legend is provided, the stacked bar might look a little
confusing before the mouse hovers on the bars
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/timqian/chart.xkcd/pull/54?email_source=notifications&email_token=ALZIRUWLKNMQSXZOZ3IMH2TQWCOVRA5CNFSM4JSYOYBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFN3YFQ#issuecomment-559660054,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALZIRUTJEKDWNL4MNNYDXL3QWCOVRANCNFSM4JSYOYBA
.

Add a legend, and changed the chart to always be colored (instead of just coloring on mouseover).  Now it looks like this:

Also for clarity, here's a screenshot with the mouse over a bar to show that label:

Looks great! Will play with it a bit, add some doc and then push to npm soon. Thanks for your work!

I did some updates https://github.com/timqian/chart.xkcd/commit/abe5d809506612d74e2afab2c3a9d4f27464788e and have published this new chart type to npm and website.


Unable to burn flash encryption key (IDFGH-5617)

idf 4.3, esp devkit v1 with universal serial bus connection and windows

no modification on any secure configuration (all disabled as default)
run this command to generate key: espsecure.py generate_flash_encryption_key abc/key.bin
burn the key: espefuse.py --port port burn_key flash_encryption abc/key.bin

error:
Connecting........_
Detecting chip type... ESP32
espefuse.py v3.1-dev
Burn keys to blocks:
 - BLOCK1 -> [8e . .. . . .. 5f]
        Reversing the byte order
A fatal error occurred:         BLOCK1 is read-protected. The written value can not be read, the efuse/block looks as all 0.
        Burn in this case may damage an already written value.(use '--force-write-always' option to ignore it)

why? saw others done this command with flying colors...
thanks!

What is the output of espefuse.py --port port summary

Detecting chip type... ESP32
espefuse.py v3.1-dev
EFUSE_NAME (Block)                       Description  = [Meaningful Value] [Readable/Writeable] (Hex Value)
Calibration fuses:
BLK3_PART_RESERVE (BLOCK0):              BLOCK3 partially served for ADC calibration data   = False R/W (0b0)
ADC_VREF (BLOCK0):                       Voltage reference calibration                      = 1072 R/W (0b10100)
Config fuses:
XPD_SDIO_FORCE (BLOCK0):                 Ignore MTDI pin (GPIO12) for VDD_SDIO on reset     = False R/W (0b0)
XPD_SDIO_REG (BLOCK0):                   If XPD_SDIO_FORCE, enable VDD_SDIO reg on reset    = False R/W (0b0)
XPD_SDIO_TIEH (BLOCK0):                  If XPD_SDIO_FORCE & XPD_SDIO_REG                   = 1.8V R/W (0b0)
CLK8M_FREQ (BLOCK0):                     8MHz clock freq override                           = 55 R/W (0x37)
SPI_PAD_CONFIG_CLK (BLOCK0):             Override SD_CLK pad (GPIO6/SPICLK)                 = 0 R/W (0b00000)
SPI_PAD_CONFIG_Q (BLOCK0):               Override SD_DATA_0 pad (GPIO7/SPIQ)                = 0 R/W (0b00000)
SPI_PAD_CONFIG_D (BLOCK0):               Override SD_DATA_1 pad (GPIO8/SPID)                = 0 R/W (0b00000)
SPI_PAD_CONFIG_HD (BLOCK0):              Override SD_DATA_2 pad (GPIO9/SPIHD)               = 0 R/W (0b00000)
SPI_PAD_CONFIG_CS0 (BLOCK0):             Override SD_CMD pad (GPIO11/SPICS0)                = 0 R/W (0b00000)
DISABLE_SDIO_HOST (BLOCK0):              Disable SDIO host                                  = False R/W (0b0)
Efuse fuses:
WR_DIS (BLOCK0):                         Efuse write disable mask                           = 128 R/W (0x0080)
RD_DIS (BLOCK0):                         Efuse read disable mask                            = 1 R/W (0x1)
CODING_SCHEME (BLOCK0):                  Efuse variable block length scheme
= NONE (BLK1-3 len=256 bits) R/W (0b00)
KEY_STATUS (BLOCK0):                     Usage of efuse block 3 (reserved)                  = False R/W (0b0)
Identity fuses:
MAC (BLOCK0):                            Factory MAC Address
= ..... R/W
MAC_CRC (BLOCK0):                        CRC8 for factory MAC address                       = 48 R/W (0x30)
CHIP_VER_REV1 (BLOCK0):                  Silicon Revision 1                                 = True R/W (0b1)
CHIP_VER_REV2 (BLOCK0):                  Silicon Revision 2                                 = False R/W (0b0)
CHIP_VERSION (BLOCK0):                   Reserved for future chip versions                  = 2 R/W (0b10)
CHIP_PACKAGE (BLOCK0):                   Chip package identifier                            = 0 R/W (0b000)
MAC_VERSION (BLOCK3):                    Version of the MAC field                           = 0 R/W (0x00)
Security fuses:
FLASH_CRYPT_CNT (BLOCK0):                Flash encryption mode counter                      = 0 R/W (0b0000000)
UART_DOWNLOAD_DIS (BLOCK0):              Disable UART download mode (ESP32 rev3 only)       = False R/W (0b0)
FLASH_CRYPT_CONFIG (BLOCK0):             Flash encryption config (key tweak bits)           = 0 R/W (0x0)
CONSOLE_DEBUG_DISABLE (BLOCK0):          Disable ROM BASIC interpreter fallback             = True R/W (0b1)
ABS_DONE_0 (BLOCK0):                     Secure boot V1 is enabled for bootloader image     = False R/W (0b0)
ABS_DONE_1 (BLOCK0):                     Secure boot V2 is enabled for bootloader image     = False R/W (0b0)
JTAG_DISABLE (BLOCK0):                   Disable JTAG                                       = False R/W (0b0)
DISABLE_DL_ENCRYPT (BLOCK0):             Disable flash encryption in UART bootloader        = False R/W (0b0)
DISABLE_DL_DECRYPT (BLOCK0):             Disable flash decryption in UART bootloader        = False R/W (0b0)
DISABLE_DL_CACHE (BLOCK0):               Disable flash cache in UART bootloader             = False R/W (0b0)
BLOCK1 (BLOCK1):                         Flash encryption key
= ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? -/-
BLOCK2 (BLOCK2):                         Secure boot key
= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
BLOCK3 (BLOCK3):                         Variable Block 3
= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W
Flash voltage (VDD_SDIO) determined by GPIO12 on reset (High for 1.8V, Low/NC for 3.3V).

It looks like you already successfully burned the key however you would have to enable encryption to verify whether it matches the key you wanted to burn.

ya, look like. but i never get successful burn message before.

@tsctrl I see that it was like this: the first run espefuse.py --port port burn_key flash_encryption abc/key.bin sets the key and protection bits; the second run the same command gives the error as you show.
if you have the log from the first attempt please share it.

cant recall if i have done it before. i guess i exidentally burn it somehow. is it possible to override the key with new key? any impact?

if the key is write-protected then it is not possible to burn a new key https://github.com/espressif/esptool/wiki/espefuse#read--and-write--protecting-efuses, the tool will show the error like above. (hardware blocks this operation anyway).

ok, tried the same with my other kits and it burn successfully,
i guess, i got too excited, burn the keys and forgotten doing it, lesson learned.
closing this, thanks!


Added Template Validation

Added DropDown Input  component in formComponent folder
Error handling while creating template

@ashwaniMaddheshiya please resolve conflicts!


Mark kins in KS test result output

A new column ksgrp is added to the Kinship sum test, which groups affected individuals by kinship. Solves issue #15.

[x]  R CMD check runs successfully.

Was more work than I assumed. shareKinship exists in multiple locations. Documentation had to be updated. R-4.1.0 was just released with Bioconductor 3.13, also tested it there. Overall, see my commit 7f2a396 for a full list of changes. I decided to call the new parameter rmKinship, as minKinship was misleading: it removes all kins with kinship ≤ rmKinship, whereas minKinship would indicate that the value itself would still be included.


feat: support search by vote with .lens

@j0hnfl0w I don't think we need apollo for that.

@bonustrack @samuveth where we can find votes from .lens? Do we even resolve .lens profiles in search results?

@bonustrack @samuveth where we can find votes from .lens? Do we even resolve .lens profiles in search results?

No we don't, we will do a single API call like when resolving the .eth, if you can't find it in the lens protocol docs we can ask them on their discord.

I mean we want to search with .lens, but we don't show .lens, only 'eth', 'xyz', 'com', 'org', 'io', 'app', 'art'

.lense is not ENS related

I already found how to resolve in lens docs


Bumped glutin version to 0.19

Transitively brings numerous fixes from newer winit version. https://github.com/tomaka/winit/blob/v0.18.0/CHANGELOG.md#version-0180-2018-11-07
PR checklist:

[ ] make succeeds (on *nix): I don't have an environment with make available
[ ] make reftests succeeds: I don't have an environment with make available
[x] tested examples with the following backends: ran cargo test --features gl-headless in src/warden and cargo test in src/backend/gl
[x] rustfmt run on changed code

Looks like another dependency is pulling in a different version of winit.

@agersant Update winit to 0.18, too.

diff --git a/examples/Cargo.toml b/examples/Cargo.toml
index ff03e16a7..59601814c 100644
--- a/examples/Cargo.toml
+++ b/examples/Cargo.toml
@@ -28,7 +28,7 @@ path = "compute/main.rs"
 env_logger = "0.5"
 image = "0.19"
 log = "0.4"
-winit = "0.17"
+winit = "0.18"
 glsl-to-spirv = "0.1.4"
 gfx-hal = { path = "../src/hal", version = "0.1" }
 gfx-backend-empty = { path = "../src/backend/empty", version = "0.1" }
diff --git a/src/backend/dx11/Cargo.toml b/src/backend/dx11/Cargo.toml
index 417aa74cb..5d7514c7f 100644
--- a/src/backend/dx11/Cargo.toml
+++ b/src/backend/dx11/Cargo.toml
@@ -26,5 +26,5 @@ smallvec = "0.6"
 spirv_cross = "0.11.2"
 parking_lot = "0.6.3"
 winapi = { version = "0.3", features = ["basetsd","d3d11", "d3d11sdklayers", "d3dcommon","d3dcompiler","dxgi1_2","dxgi1_3","dxgi1_4", "dxgi1_5", "dxgiformat","dxgitype","handleapi","minwindef","synchapi","unknwnbase","winbase","windef","winerror","winnt","winuser"] }
-winit = { version = "0.17", optional = true }
+winit = { version = "0.18", optional = true }
 wio = "0.2"
diff --git a/src/backend/dx12/Cargo.toml b/src/backend/dx12/Cargo.toml
index d64773e44..4934d14c0 100644
--- a/src/backend/dx12/Cargo.toml
+++ b/src/backend/dx12/Cargo.toml
@@ -26,4 +26,4 @@ log = { version = "0.4", features = ["release_max_level_error"] }
 smallvec = "0.6"
 spirv_cross = "0.11.2"
 winapi = { version = "0.3", features = ["basetsd","d3d12","d3d12sdklayers","d3d12shader","d3dcommon","d3dcompiler","dxgi1_2","dxgi1_3","dxgi1_4","dxgiformat","dxgitype","handleapi","minwindef","synchapi","unknwnbase","winbase","windef","winerror","winnt","winuser"] }
-winit = { version = "0.17", optional = true }
+winit = { version = "0.18", optional = true }
diff --git a/src/backend/gl/Cargo.toml b/src/backend/gl/Cargo.toml
index 587f3da5c..40408cc61 100644
--- a/src/backend/gl/Cargo.toml
+++ b/src/backend/gl/Cargo.toml
@@ -23,5 +23,5 @@ log = { version = "0.4", features = ["release_max_level_error"] }
 gfx_gl = "0.5"
 gfx-hal = { path = "../../hal", version = "0.1" }
 smallvec = "0.6"
-glutin = { version = "0.18", optional = true }
+glutin = { version = "0.19", optional = true }
 spirv_cross = "0.11.2"
diff --git a/src/backend/metal/Cargo.toml b/src/backend/metal/Cargo.toml
index 29982bffd..9c0f3e05d 100644
--- a/src/backend/metal/Cargo.toml
+++ b/src/backend/metal/Cargo.toml
@@ -22,7 +22,7 @@ name = "gfx_backend_metal"
 gfx-hal = { path = "../../hal", version = "0.1" }
 bitflags = "1.0"
 log = { version = "0.4", features = ["release_max_level_error"] }
-winit = { version = "0.17", optional = true }
+winit = { version = "0.18", optional = true }
 dispatch = { version = "0.1", optional = true }
 metal = { version = "0.13.0", features = ["private"] }
 foreign-types = "0.3"
diff --git a/src/backend/vulkan/Cargo.toml b/src/backend/vulkan/Cargo.toml
index 06c74c58a..260b86a38 100644
--- a/src/backend/vulkan/Cargo.toml
+++ b/src/backend/vulkan/Cargo.toml
@@ -26,7 +26,7 @@ shared_library = { version = "0.1.9", optional = true }
 ash = "0.24.4"
 gfx-hal = { path = "../../hal", version = "0.1" }
 smallvec = "0.6"
-winit = { version = "0.17", optional = true }
+winit = { version = "0.18", optional = true }
 glsl-to-spirv = { version = "0.1", optional = true }

 [target.'cfg(windows)'.dependencies]

bors r+


Feature/apichard/thumbnail max size

Purpose
Display an error message before aws validation on large file upload
Proposal

[x] Check size in serialization
[x] Display the error message in the front

The last commit title is not relevant. You should specify you are working on a thumbnail resource.


A "tight layout" mode that reduces vertical spacing

A design with generous vertical spacing looks nice on big screens.
However, on a small Laptop screen, it's in my opinion better to have a tighter layout to fit more lines of code on the screen.
Therefore, it would be nice to have a "tight layout" mode, that reduces vertical spacing in a notebook.
I've made 4 screenshots from the same notebook to show how vertical spacing is varying from platform to platform (and VSCode wins the contest of largest white space areas):

from JupyterLab
from a Gist
from VS Code
from VS Code diff

All screenshots are made with default zoom setting and used this notebook https://gist.github.com/kolibril13/cdecff2da4f12dcbc5ffae449a5e9572
My machine is a MacBoc Air M1, Retina display, 13.3-inch (diagonal).
It would be amazing if vertical spacing was customizable in VS Code Jupyter!

JupyterLab

Gist on GitHub

VSCode (note how the last cell output is not on the screen anymore)

VSCode diff

related, but for IW: https://github.com/microsoft/vscode/issues/156803

@kolibril13 thanks for your feedback. This has been brought up multiple times and we can see the value of having a more compact view for notebook editor.
The main reason VS Code's default notebook view has more spacing is it renders more components than the Jupyter Notebook, including

A toolbar to insert between cells
A breadcrumb to show the TOC of the notebook file and cell
Cell toolbar which allows you to run operations against the target cell
Cell status bar for execution state and cell language

If we disable these components (the functionalities are still available through commands, or through other components) with following settings
    "notebook.insertToolbarLocation": "notebookToolbar",
    "breadcrumbs.enabled": false,
    "notebook.showCellStatusBar": "hidden",
    "notebook.cellToolbarLocation": {
        "jupyter-notebook": "hidden"
    }

VS Code

Chrome/Jupyter Notebook

@kolibril13 do you wanna give the settings a try and see how they work for you?

Thanks @rebornix for your quick response and so many great suggestions!
And congrats for winning the "more content rendered than in Jupyter Lab" challenge with VSCode! ;)
I think it's really situation dependent when one prefers more functions, and when one prefers more space.
Maybe there can be a switch command that toggles all these settings at once?
Regarding from your comment above:

A toolbar to insert between cells
A breadcrumb to show the TOC of the notebook file and cell
Cell toolbar which allows you to run operations against the target cell

I totally agree with this, these are nice to have, but also dispensable as there are good alternatives.

Cell status bar for execution state and cell language

In my opinion, the execution state is an important feature.
Maybe this can be shifted up in "tight layout" mode, so that it does not occupy extra vertical space?
In JupyterLab, there is the [*] that indicates cell execution.
And the cell language: How about shifting this to the right button corner of the last code line in "tight layout" mode?
But cell language is also not very important to have in a "tight layout" mode, I think.
I've tested your parameters, and it's a huge difference! Thanks a lot for providing these settings! :)
Here is a before/after image comparison:
https://user-images.githubusercontent.com/44469195/221275922-9f5ddb1e-a9d3-492f-96ae-28c3766c3c30.mov

Do we want to take this challenge even further and once test out the tightest vertical spacing that does not harm the readability?
I just took your reduced spaced layout and drew some red lines where I can see potential to further reduce the size:

A few pixels less at the beginning of a cell.
A few pixels less at the ending of a cell.
A few pixel less between the outputs.

Maybe it might look cluttered then, but it would be interesting to see if this was possible.

@kolibril13 I like the screenshot you posted above very much. You did figure out the padding we added around those components, great work!

A few pixels less at the beginning of a cell.
A few pixels less at the ending of a cell.

We always add a few pixels around the cell editor. The text editor has settings to control the top/bottom padding, so we might consider adding the same set of settings for notebook.

A few pixel less between the outputs.

We might want to check the default padding we use for outputs cc @amunger

I find switching this setting to hidden helps the most.

Historically related: #101366


fix: pss subscribe in browsers

Exactly. The reason is that the type of the message data in browser for WebSocket can be any type [docs] (and seem like it is Blob in this case) so it was failing to convert and we don't have tests for this (and never tried).
We use the isomorhpic-ws to have compatibility between browser and nodejs but it seems it's not 100% at least when it comes to types (and unclear what types are really allowed in the nodejs case)

In that case let's write browser tests for this use case 😄


[SPARK-17328][SQL] Fix NPE with EXPLAIN DESCRIBE TABLE

What changes were proposed in this pull request?
This PR fixes the following NPE scenario.
Reported Error Scenario
scala> sql("EXPLAIN DESCRIBE TABLE x").show(truncate = false)
INFO SparkSqlParser: Parsing command: EXPLAIN DESCRIBE TABLE x
java.lang.NullPointerException

How was this patch tested?
Pass the Jenkins test with a new test case.

Test build #66368 has started for PR 15357 at commit 4b60195.

Test build #66371 has started for PR 15357 at commit 45e46a9.

Test build #66368 has finished for PR 15357 at commit 4b60195.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66368/
Test PASSed.

Merged build finished. Test PASSed.

Test build #66371 has finished for PR 15357 at commit 45e46a9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66371/
Test PASSed.

LGTM - merging to master

Thank you, @hvanhovell !


Watcher workspace flow

Look at the Readme changes and see if the approach seems reasonable.
So far, it seems to address most of my concerns, with two lingering annoyances:

The asset viewer/ModelDoc/etc default to looking at addons/* apparently, so they ignore my sbox/workspace/my-gamemode/wirebox/models/ folder. Its still possible to manually browse to and open those files, but they don't show in Recent/etc. This may be for the best, since if it did see two versions, it'd likely confuse them anyway, but it does mean developing assets practically needs a backwards sync back into the git workspace folder. Which is totally doable...
When you load new models in-game, they compile .vmdl's to .vmdl_c's, which of course get written to addons/my-gamemode/models/, thus you need to manually copy those back over the "source files" in ./workspace to commit them to git. I'm not actually sure yet if I even want to commit those, since they're kinda big to store in git, and I may have seen them vary between game versions - so might not be a con, but I do get a lagspike when I first generate them, so I could imagine a gamemode with 100's of models would likely want to include those for distribution (if not git, in release.zip's or something)

Oh, and I also dropped the sandbox assets, sorry that muddies the PR diff, but I kept them in an isolated commit.

I think this is ready enough to merge.


chore(master): release 1.2.15

:robot: I have created a release beep boop
1.2.15 (2023-06-18)
Bug Fixes

deps: update dependency friendsofphp/php-cs-fixer to v3.18.0 (0c14f37)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/php-cs-fixer-config/releases/tag/v1.2.15 :sunflower:


Expand Exported Distribution Data

Hi, awesome volunteers!
I received a request from another DiaperBase user to expand the data exported regarding distributions. Currently, the export sheet only says the total items distributed to partner agencies, which isn't as helpful as it could be. Also adding a breakdown of what items/quantities were distributed is ideal.

Thanks,
Rachel

Sounds like we should add extra columns of each item + quantity beneath them.
Whoever takes this, please see if you can include the columns with the quantity of each.

Ohh I just noticed we have another PR that might be able to address this - https://github.com/rubyforgood/diaper/pull/2005
I'll do a dive in to see if that addresses this

Addressed this by merging in https://github.com/rubyforgood/diaper/pull/2005 ; Should have this released in production soon, perhaps this weekend :)


easy way to add dependencies which aren't in a public maven repo

Whenever I want to write a function which depends on a jar that isn't in a public maven repo it's a pain.  I end up creating a custom Dockerfile with something like:
COPY deps  /usr/share/maven/ref/repository
to pre-seed the in-image maven repo cache with stuff I am working on right now. This could actually be in the boilerplate, no?

@mjg123 why not use maven install-file plugin ?
http://www.baeldung.com/install-local-jar-with-maven/


Update Composer dependencies (2021-03-05-00-11)

Visual regression test passed!
View the visual regression test report


Release Prep: Core

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Suggested detail to add to the considerations & limitations section

It's not crystal clear whether the dataset scale-out setting is altered or removed when a .pbix file is re-deployed from PBI desktop, overwriting an existing scale-out enabled dataset.
After testing, scale-out does not appear to be altered in any way when re-publishing, however stating this in the docs could save the audience a lot of time :)

Thanks for your comment, @alan-at-microsoft. This issue has been assigned to the doc author for review.

When my comment was originally made, I didn't see this information in any of the PBI scale-out docs. For example:
https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-scale-out#considerations-and-limitations

Hi @alan-at-microsoft,
Thank you for your suggestion and for explaining which document you're referring to. As you stated, a republished PBIX doesn't break scale-out, therefore, I see no need to document an expected behavior that doesn't break the anything.
Thanks,
Kesem


InternLM2.5 - 7 billion parameter with 1M context length

Link to the collection
Introduction
InternLM2.5 has open-sourced a 7 billion parameter base model and a chat model tailored for practical scenarios. The model has the following characteristics:
Outstanding reasoning capability: State-of-the-art performance on Math reasoning, surpassing models like Llama3 and Gemma2-9B.
1M Context window: Nearly perfect at finding needles in the haystack with 1M-long context, with leading performance on long-context tasks like LongBench. Try it with LMDeploy for 1M-context inference.
Stronger tool use: InternLM2.5 supports gathering information from more than 100 web pages, corresponding implementation will be released in Lagent soon. InternLM2.5 has better tool utilization-related capabilities in instruction following, tool selection and reflection. See examples.

1m token length 👀

Seconded, this would be a fantastic addition.

Online


feat(core): :sparkles: in corelist new varient props has been added

Description
a new varient props has been added to verify the listType will work or not.
Ref: #93

Merging since stale over 24hrs.


Urgent issue with the Camera trigger.

I have an urgent issue with one camera - Mapir https://www.mapir.camera/ camera.
Our regular PWM trigger stays at 1500us then it triggers at 1700us. (not the seagulMap)
For this Mapir camera it is no go because at 1500us it switches to USB file transfer mode.
The trigger should stay at 1000us passive and then receive 2000us on trigger events.
Is there any quick fix or workaround I can apply to make it work until 14th of Nov.
Asking for help on this one. Really don't have any clue how to do the survey in a demo mission with this camera.
Any help will be greatly appreciated.

Two line change : https://github.com/PX4/Firmware/blob/master/src/drivers/camera_trigger/interfaces/src/pwm.cpp#L9-L11

Hi @mhkabir Is it very hard to make parameters for these two? We are willing to pay somebody to do it for the open source branch. Will you be able to do it? We can discuss in private<EMAIL_ADDRESS>


The Lepiter database registry does not update the list of databases when the database folder is deleted

If you delete a folder containing a lepiter database, then the list of databases is not updated.
LeDatabasesRegistry uniqueInstance defaultLogicalDatabase databases

This can be an issue, for example, when deleting a git repo and the underlying files from the git interface.
The git Setup dialog for example is confused after deleting and cloning again a repo because it thinks the lepiter database is still there, though it is not.

Something like this should clean up the registry:
registry := LeDatabasesRegistry uniqueInstance defaultLogicalDatabase.
registry
	databasesDo: [ :each | each localStoreRootDirectory exists ifFalse: [ registry removeDB: each ] ]

As a first step, Lepiter databases are now removed when their Git repository is deleted from the image (whether it exists on disk still or not).


Autocomplete dropdown opens and cannot be closed

💻 Environment

Platform:  MacOS
OS Version:  OS X 10.14
Toggl Version:  7.4.1023
🐞 Actual behavior
The autocomplete dropdown opens and does not close, hiding user time entries.
💯 Expected behavior
The autocomplete should close when you click enter?
🔨 Steps to reproduce
User Video here
📦 Additional info
User  Report

When the user has selected a project from autocomplete and the timer now has 2 fields then when the user opens autocomplete the ESC won't close it and only clicking outside the autocomplete will close it. Also when you remove focus from timer it (SHIFT+DOWN) to focus listing it should also still trigger autocomplete close when pressing ESC.

user report

Case Reference

Closes by #3507


Clarify the semantics of Time_zone_info in documentation

Right now the semantics is roughly: a possibly valid pairing of time zone offset and time zone

Fixed by 3f22c7da4ff8acdfd943858729c1f6acaba10891


Development documentation

It would be nice to have some development documentation, for example:

how to setup a local development environment
how to run the tests
things to keep in mind when submitting a PR, if any

The docs can probably still use some improvement, e.g. we might want to tell people to rebase / squash their commits?
Not sure if you prefer to keep this issue open or not, please feel free to close it if you want to :)

If you want to catalog your ideas for enhancements, I personally don't have an issue leaving this open for a bit.


Nested packageProp path

Allows targeting of nested package.json values using dot notation

Closes #164

@davidtheclark is there anything else needed for this?

@iamogbz - please update the readme with a small blurb on allowing nested package properties
other than that it looks good to me.  At first I was weary of pulling in lodash.get because lodash utils are bigger than most people think - but its functionality is ubiquitous and thus expected, and the size isn't that big.

@iamogbz - please update the readme with a small blurb on allowing nested package properties

@olsonpm updated, thanks!

Thanks @iamogbz. It's looking good. I think there may be a bunch of additional tests worth writing for cases other than successfully loading a named file. Do you mind if I add a commit to this PR?


"module": ""  -- "All good!" from publint

Another thing to report.
I tried a package.json (below) with:
"module": "",
Results in
$ npx publint
whip-whep lint results:
All good!

I found this by accident.

Thanks for the report! This is somewhat strange but I think bundlers could still work with this if it resolves to the packages root index.js file. Does it exists in your package?

These are the files:
$ ls
LICENSE       README.md     index.mjs     package.json  types.d.ts    whep.js       whip.js

No index.js file

I can't seem to reproduce this with the given directory. I'm getting this correct (although could be worded better) error:
publint-invalid-field-types lint results:
Errors:
1. pkg.module is  but the file does not exist.
 ELIFECYCLE  Command failed with exit code 1.

Can you share the setup through a github repo or https://stackblitz.com ?

Closing this for now.


A couple of issues when parsing

I was trying to add all the examples from the Teal Tutorial to the examples folder (#32) and came across a couple parsing issues.
Generics
The S is has an error on it:
local interface Shape
   x: number
   y: number
end

local function largest_shape<S is Shape>(shapes: {S}): S
   --- ...
end

Functions
All of the following throw errors on the ?:
local f: function(function(? string):(number, number), number) -- from tutorial
local f: function(function(thing?: string):(number, number), number) -- slight modification

These ones don't:
local type Comparator = function<T>(T, T): boolean
local function mysort<A>(arr: {A}, cmp?: Comparator<A>)
   -- ...
end
local f: function(function(thing: string):(number, number), number) -- also works as expected

Globals
global types seems to error out on global type [WHITESPACE]* global
-- person.tl
local person = {}

global type Building

global record Person
   residence: Building
end

return person

I might try my hand at updating the grammar, but if it's a quick fix for you, don't wait on me!
We should probably determine what to do with #31 before getting too far on this.
This currently blocks #32 from being merged (without causing failures during the build).

I got the functions and globals working! Normally I'd put in a PR, but I'll just mention them here for now (and can PR it in later)
Functions
Update partype to:
_partype: $ => seq(optional(
  choice(
    optional(field("optional_marker", $.optional_marker)),
    seq(field("name", $.identifier), optional(field("optional_marker", $.optional_marker)), ":")),
  ),
  field("type", $._type)
),

Globals
I felt like this was a special global case, so created a new global forward declaration:
global_type_forward_decleration: $ => seq(
  "global",
  "type",
  field("name", $.identifier),
),

and then added it to _statement.
Generics...
I don't have this one figured out. I tried updating typeargs to.
typeargs: $ => seq("<", list(
  seq(
    $.identifier,
    optional(seq(field("is_types", seq("is", list($._type))))),
  )),
">"),

I felt like all the places it was referenced can be extended, but should probably double check with Teal itself.
regardless, I got some fun type resolution errors to work through:
Unresolved conflict for symbol sequence:

  'return'  'function'  '<'  identifier  ','  identifier  'is'  _type  type_tuple_repeat1  •  ','  …

Possible interpretations:

  1:  'return'  'function'  '<'  identifier  ','  identifier  'is'  _type  (type_tuple_repeat1  type_tuple_repeat1  •  type_tuple_repeat1)
  2:  'return'  'function'  '<'  identifier  (typeargs_repeat1  ','  identifier  'is'  _type  type_tuple_repeat1)  •  ','  …

Possible resolutions:

  1:  Specify a left or right associativity in `typeargs_repeat1`
  2:  Add a conflict for these rules: `typeargs`

I feel like after reading a lot of source code, I think left associativity is the way to go, but it also seems to work if you just throw typeargs into conflicts, but that does not feel good.


With multisite enabled in 21.1-canary, the GRAPH_QL_ENDPOINT is required

Description
In previous versions before adding the new multisite functionality, it was enough to provide the SITECORE_API_HOST and SITECORE_API_KEY environment variables, and with multisite enabled, the GRAPH_QL_ENDPOINT variable must be filled in, according to the file here:
https://github.com/Sitecore/jss/blob/dev/packages/create-sitecore-jss/src/templates/nextjs-multisite/scripts/config/plugins/multisite.ts
If omitted, the build fails, as the config.graphQLEndpoint is only containing a path.
Expected behavior
It should be enough to provide SITECORE_API_HOST and SITECORE_API_KEY

@larserhardsen Thanks for reporting, I've added this to our backlog for further investigation. You are correct, we lost previous dynamic aspects of the config graphQLEndpoint prop.

@larserhardsen This issue is resolved with #1296. Please try with latest canary build.

@ambrauer It works! Thanks!


Added turn_based_game to list of packages.

The library turn_based_game is a rules engine that assists in writing games that are...well...turn-based. (The meaning of that is well documented in the wiki.) One of my next projects is porting my Negamax AI algorithms to nim, and they will require this framework to predictably operate.

Nice! You can use Nim syntax highlighting in your readme btw :)


Quote keys

Need to figure out a good regex for when it is required.
Might be able to borrow something from the work done by @mathiasbynens
http://mathiasbynens.be/notes/javascript-properties

Seems like the library still don't quote some keys and that causes nodejs to output error about syntax error...


Undefined behavior for GenericStringArray::from_iter_values if reported iterator upper bound is incorrect

Describe the bug
While reviewing #197 I was able to create a reproducer that indeed caused undefined behavior
To Reproduce
use arrow::array::StringArray;

// Make an iterator that is untruthful about its actual length (say it is shorter than it really is):
#[derive(Debug, Clone)]
struct BadIterator<T> {
    /// where the iterator currently is
    cur: u64,
    /// How many items will this iterator *actually* make
    limit: u64,
    /// How many items this iterator claims it will make
    claimed: u64,
    /// What type of item to return
    pub item: T,
}

impl<T> BadIterator<T> {
    /// Create a new iterator for <limit> items, but that reports to
    /// produce <claimed> items
    fn new(limit: u64, claimed: u64, item: T) -> Self {
        Self{
            cur: 0,
            limit,
            claimed,
            item
        }
    }
}

impl <T:Clone> Iterator for BadIterator<T> {
    type Item = T;

    fn next(&mut self) -> Option<Self::Item> {
        if self.cur < self.limit {
            self.cur += 1;
            Some(self.item.clone())
        } else {
            None
        }
    }

    /// report whatever the iterator says to
    fn size_hint(&self) -> (usize, Option<usize>) {
        (0, Some(self.claimed as usize))
    }
}

fn from_vec(v: Vec<&str>) -> StringArray {
    v.into_iter()
        .map(Some)
        .collect()
}

// This definitely causes a problem
fn use_iter_values() {
    // correctly report size:
    let array = StringArray::from_iter_values(BadIterator::new(3, 3, "foo"));
    assert_eq!(array, from_vec(vec!["foo", "foo", "foo"]));

    // incorrectly correctly report size to be 10
    let array = StringArray::from_iter_values(BadIterator::new(3, 10, "foo"));
    assert_eq!(array, from_vec(vec!["foo", "foo", "foo"]));

    // incorrectly correctly report size to be 1 (too small)
    let array = StringArray::from_iter_values(BadIterator::new(3, 1, "foo"));
    assert_eq!(array, from_vec(vec!["foo", "foo", "foo"]));
}

fn main() {
    println!("Starting...");
    use_iter_values();
    println!("Done...");
}

Results in
Starting...
Use collect
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /Users/alamb/Software/arrow-rs/arrow/src/array/array_string.rs:101:40
stack backtrace:

And undefined behavior in MIRI
Expected behavior
Success and no undefined behavior
Additional context
Add any other context about the problem here.

Strangely, I don't understand the usecase of from_iter_values compared to FromIter -- I'll add a PR to remove the API

It looks like DataFusion uses from_iter_values in several places (both for StringArrays and primitive arrays)
https://github.com/apache/arrow-datafusion/search?q=from_iter_values
However, when I was looking at the implementations of FromIterator and from_iter_values I didn't see the need for both.

Strangely, I don't understand the usecase of from_iter_values compared to FromIterator

I think that from_iter_values leverages the invariant that there are no nulls in the iterator (AsRef<str>), while FromIterator accepts nulls / None. The two APIs are motivated by a significant performance penalty in creating the bitmap from an iterator of options (compared to the cost of an iterator of non-nullable values)


Missing Files annotations in feed api

90% sure that FeedItems that are Files are coming back with empty likes and comments. It seems that the comments (and probably likes too) are coming back fine in the normal files api.

Will take a look ASAP

Looking...

@asutula what FeedMode are you requesting?

CHRONO

CHRONO doesn't nest the annotations. They appear in pure chronological order. ANNOTATED will nest them, and STACKS nests them unless there's a break in continuity, in which case they would appear as in CHRONO with the target nested (flipped).

:face_palm::skin-tone-2:


Revert "Store exception to local object for easier debugging." that warns

This reverts commit 332fd1db337db905bf4b17191f3d7ca76f629cd0.
Because this causes "assigned but unused variable" warning when libxml-ruby 3.2.4 is being required with -W.
$ ruby -we "require'libxml-ruby'"
.../libxml-ruby-3.2.4/lib/libxml-ruby.rb:7: warning: assigned but unused variable - e

Thanks


Open/Close transition on mobile

The datepicker pops up and closes very abruptly in the mobile layout.
Could you consider adding some nice transitions for open/close?

Definitely have considered that already – just not as a high priority for 1.0.
On top of the popup open/close, we should consider some sort of visual feedback when the user selects a date (a ripple is a natural choice for Material Design).
There’s a similar task for the combo box: https://github.com/vaadin/vaadin-combo-box/issues/65

moving this feature to vaadin-overlay https://github.com/vaadin/vaadin-overlay/issues/36

We can’t implement these in the generic overlay, as the transition/animation is probably custom for the date picker.

The new Lumo theme (in v3) has an opening animation currently.
There’s a PR pending for vaadin-overlay that allows us to defined closing animations as well: https://github.com/vaadin/vaadin-overlay/pull/60
We will probably add some closing animation for date picker once that is released. I’ll keep this issue open until we do that.

Seems to be working fine with the latest version. Closing.


Save the image  layer group

I have a PSD with layer groups. Is it possible to save each layer group as an image?
For Example:
Layer group 01: {
layer logo
layer text
to be continued....
}
Layer group 02: {
layer logo
layer text
to be continued....
}
I need to download each layer group as a separate image.

Have you found a solution?

I couldn't find a solution. I'm using the separate layers. Joining the single layers until they form a group of complete layers.

me to

I couldn't find a solution. I'm using the separate layers. Joining the single layers until they form a group of complete layers.

Hi, can you tell me how you join these layers? Thanks!

You will need to recursively go over the layers of the top node of the group you want to save and save each one of them over the parent node's image.


[FEATURE] : Add Template Engines

Pull Request
Description
[FEATURE] : Add Template Engines
Closes #1515
Type of change

[ ] Adding a new Resource
[ ] Adding a new Category
[x] Documentation enhancement or fixes
[ ] Website enhancement or fixes

Checklist:

[x] I read carefully CONTRIBUTING.md
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Screenshots (if appropriate):

Additional

@jfmartinz please merge it...


Enhanced label positioning at limit lines (enum ChartLimitLabelPosition)

Added new enums for ChartLimitLabelPosition for a more flexible label positioning.


WIP: Llfc change issue 31

pytest result:
              Starting test_llfc_susceptibility_check
... [Check  1/5] Link Level Flow Control Check...                                                                       MANUAL CHECK REQUIRED
  Current version                                                         Target Version                                                          Warning
  ---------------                                                         --------------                                                          -------
  <aci-preupgrade-validation-script.AciVersion object at 0x7f2667f16ee0>  <aci-preupgrade-validation-script.AciVersion object at 0x7f2667f16f10>  Affected Path Found, Check Bug RNE

  Recommended Action: Manually change Peer devices Transmit(send) Flow Control to off prior to switch Upgrade
  Reference Document: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo27498

[Check  2/5] Link Level Flow Control Check...                                                                       MANUAL CHECK REQUIRED
  Current version                                                         Target Version                                                          Warning
  ---------------                                                         --------------                                                          -------
  <aci-preupgrade-validation-script.AciVersion object at 0x7f2667f16f10>  <aci-preupgrade-validation-script.AciVersion object at 0x7f2667f16ee0>  Affected Path Found, Check Bug RNE

  Recommended Action: Manually change Peer devices Transmit(send) Flow Control to off prior to switch Upgrade
  Reference Document: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo27498

[Check  3/5] Link Level Flow Control Check...                                                                                PASS
[Check  4/5] Link Level Flow Control Check...                                                                                PASS
              Starting Positive stale_nir_object_check
... [Check  1/5] NIR App Stale Object Check...                                                                        FAIL - OUTAGE WARNING!!
  Current version  Target Version  Warning
  ---------------  --------------  -------
  4.2(1a)          5.2(4d)         telemetryStatsServerP Found

  Recommended Action: Manually delete the telemetryStatsServerP object prior to switch upgrade
  Reference Document: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt47850

[Check  2/5] NIR App Stale Object Check...                                                                                PASS
[Check  3/5] NIR App Stale Object Check...                                                                        FAIL - OUTAGE WARNING!!
  Current version  Target Version  Warning
  ---------------  --------------  -------
  3.2(1a)          5.2(6a)         telemetryStatsServerP Found

  Recommended Action: Manually delete the telemetryStatsServerP object prior to switch upgrade
  Reference Document: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt47850

#31

issue:
hit error when no FW in fwrepo:
    ==== 2022-10-19T15-24-55-0700 ====

Enter username for APIC login          : admin
Enter password for corresponding User  :

Checking current APIC version (switch nodes are assumed to be on the same version)...5.2(6e)

Gathering APIC Versions from Firmware Repository...

No Firmware Detected!  Please Upload APIC Firmware and re-run the script.
......
......
[Check 39/39] Link Level Flow Control Check...
              Error: expected string or buffer...                                                                                ERROR !!

Issue:
flags MANUAL if tver selected is same as cver:
    ==== 2022-10-19T18-13-06-0400 ====

Enter username for APIC login          : admin
Enter password for corresponding User  :

Checking current APIC version (switch nodes are assumed to be on the same version)...4.1(2g)

Gathering APIC Versions from Firmware Repository...

[1]: aci-apic-dk<IP_ADDRESS>g.bin
[2]: aci-apic-dk<IP_ADDRESS>o.bin
[3]: aci-apic-dk<IP_ADDRESS>d.bin

What is the Target Version?     : 1

You have chosen version "aci-apic-dk<IP_ADDRESS>g.bin"
....
.....
[Check 39/39] Link Level Flow Control Check...                                                                       MANUAL CHECK REQUIRED
  Current version  Target Version           Warning
  ---------------  --------------           -------
  4.1(2g)          aci-apic-dk<IP_ADDRESS>g.bin  Affected Path Found, Check Bug RNE

  Recommended Action: Manually change Peer devices Transmit(send) Flow Control to off prior to switch Upgrade
  Reference Document: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo27498


Frames argument in transform

Added frames argument in BaSiCPy.transform so that the users can select the frames for the baseline.

ml-dtypes version should be fixed for windows, see https://github.com/google/jax/issues/17693 .


"Sync your viewers from GitHub" icon

currently it's a plus sign - it should be a sync sign of some sort - doesn't have to be fancy.

How about a GitHub logo?
--

mdz

I don't think I can make a github logo look like a github logo in < 25 pixels

The current icon is 74x74, no?
--

mdz

It's browser resized to 28x28, which includes borders

http://imageshar.es/4e9cc6fb059ef06c3200067d was what I went with, if you don't like it, we can try something else

Works for me.
--

mdz


Load_weights not working

It looks like there may be a problem with the load_weights method when trying to re-load the bi-directional model after a previous training session.
  File "D:/Final project/TimeNLPTest/KerasVec2Vec.py", line 130, in buildBiLSTM
    model.load_weights(dir + "StackedLSTM E-D 13 epochs 50 512 20 relu mse adam 2015-08-23 <IP_ADDRESS>1000 .wt")
  File "C:\Anaconda\lib\site-packages\keras\models.py", line 492, in load_weights
    for k in range(f.attrs['nb_layers']):
  File "h5py\_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (D:\Build\h5py\h5py-2.5.x\h5py\_objects.c:2475)
  File "h5py\_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (D:\Build\h5py\h5py-2.5.x\h5py\_objects.c:2432)
  File "C:\Anaconda\lib\site-packages\h5py\_hl\attrs.py", line 52, in __getitem__
    attr = h5a.open(self._id, self._e(name))
  File "h5py\_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (D:\Build\h5py\h5py-2.5.x\h5py\_objects.c:2475)
  File "h5py\_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (D:\Build\h5py\h5py-2.5.x\h5py\_objects.c:2432)
  File "h5py\h5a.pyx", line 77, in h5py.h5a.open (D:\Build\h5py\h5py-2.5.x\h5py\h5a.c:2079)
KeyError: "Can't open attribute (Can't locate attribute: 'nb_layers')"

I can try and work with you to sort this out, what do you think the problem could be?

To be clear the model I used when saving those weights was identitical to the one I used when loading them:
model = Sequential()
model.add(BiDirectionLSTM(embedding_size, hidden_size, init=initialize))
model.add(Dense(hidden_size, hidden_size, init=initialize))
model.add(Activation('relu'))
model.add(RepeatVector(maxlen))
model.add(LSTM(hidden_size, hidden_size, return_sequences=True, init=initialize))
model.add(TimeDistributedDense(hidden_size, output_size, activation='softmax', init=initialize))

Ignore this, I found the problem.

@cjmcmurtrie Could you clarify what the issue was?  I'm having a similar problem.

I have this same problem, and I'd like to know what the solution was.

@TELSER1 Non-Existant and/or 0 byte h5 file.

I also have this problem @cjmcmurtrie @bryan-lunt can you tell me the solution?

Maybe you can post your code up here, otherwise you may also wish to try out mozi bilstm
https://github.com/hycis/Mozi/blob/master/example/imdb_bilstm.py

I think it was that my h5 file was bad.

@erlizhou I was definitely a non-existant file.

I guess it needs a separate issue on the master branch, but it seems that load_weights will create the .h5 file if it doesn't exist.
I don't like that behavior.

I fixed this in my own keras repo.
https://github.com/bryan-lunt/keras/tree/fix_load_weights
You can comment on my pull-request on the main keras repo.
https://github.com/fchollet/keras/pull/1736

@erlizhou I am also face this problem, do you solve it?

@bryan-lunt  Hello, I can't find the solution from the link that you give, can you say it again, thank you.

@south-ocean You can clone my forked git repo and see the difference between that branch and the master it was based off of. I haven't delt with Keras for quite a while. The problem I was facing (judging by my comments) was that I was trying to load an h5 file that did not exist.

@cjmcmurtrie can you please give me brief about the error how to solve it.

@cjmcmurtrie  Hi, I also have the same problem, can you tell me how you fix it?

The fix to the problem I was having is right here:
https://github.com/bryan-lunt/keras/commit/c23579e059c9cd88a956b7eac9a69f7d7e276fc8
I believe that it's already been merged into the main branch of keras.
The problem ( my problem) was that if you asked for an hdf5 file that did not already exist, an empty one would be created automatically.
This change prevents that. If you don't want to change keras for that, you can write your own code that will check for the existence of the file before trying to load it with keras.

who solve the problem? who  can tell me ?


Login is broken

Program gets stuck on homepage of Duolingo.

Fixed the login issue, although Duolingo removed the extra modules for flirting and idioms so the script will not work now. :(


Update imagery

Solves #4
Instead of using Open Sans, I used the gdg logo generator :)

Do we need jpg and png?

uhmmm, it's a good question, maybe we can do with the png and leave the jpg out, right?


Implement a new wait parameter when creating a droplet.

Solves #177

I am updating the master branch on my fork so I created a separate branch and a new pull request


Filtering for Scalar List Fields

Hi, in prisma/prisma2#169 you have implemented the support for Array of primitives.
Do you have a plan for supporting filtering by such array?
For example:
model Person {
   titles: String[]
}

person.findMany({ where: { titles: { contains: 'Dr' } } })
person.findMany({ where: { titles: { in: ['Dr', 'Ing'] } } })

Hm, this is quite an important feature for me. Are you able to ship this with Q1 Production release? Otherwise, I'll probably need to rethink how I deal with this problem, as it's pretty much a requirement that I'm able to query/filter based on arrays. Is there an alternative/workaround?

For me is very important feauture!!!

Our prisma based ecommerce product currently has a couple of features blocked by this issue and we would really like to avoid reverting to the queryRaw route. Is there any ETA?
(This is a "+1 comment", I don't usually do this but I've been instructed on Slack to do so).

Also leaving a comment here to notify I'm currently blocked by the lack of having this feature. Like @esistgut I'd love to not fall back to using queryRaw.
It would be lovely if the Prisma product team could prioritize and give us an ETA so we set expectations for our team and clients.

During the last planning we were unsure whether this is already partially implemented or not. I found some corresponding data structures in our internal filter API. But those are not implemented in any way.
So the following is still needed:

Define what the API should look like in the client.
Define an implementation for each operation in the API. As only Postgres supports scalar lists right now here is the link to the docs for their array functions.

Internally we have the following filters defined for scalar lists right now. Are these already enough? Do we want more?
pub enum ScalarListCondition {
    /// List contains the given value
    Contains(PrismaValue),

    /// List contains all the given values
    ContainsEvery(Vec<PrismaValue>),

    /// List contains some of the given values
    ContainsSome(Vec<PrismaValue>),

    /// List is empty
    ContainsNone,
}

Thanks @mavilein! These looks like definitely enough for now.
I would let @timsuchanek chime in for the client API piece

@do4gr mentioned that we might want an equality condition additionally.

@thebiglabasky This is still tagged 2.2.0 but is not implemented as far as I am aware, it is actually missing. Is it possible to put it back in the roadmap somewhere? Thanks

Hi,
This is still in the "Planned" state right now so coming in the next months. We're busy going after native types and atomic operations first.

@mavilein we also need the inverse operation too: ContainedIn: Vec<PrismaValue> where the input vec contains the stored vec.

@MJGTwo what you describe is currently supported.
String fields are capable of taking in, notIn etc.
So in your example
const emails =<EMAIL_ADDRESS><EMAIL_ADDRESS>user.findMany({ where: { emails: { in: emails } } });
//
const titles = ['dr', 'rev', 'capt'];
user.findMany({ where: { titles: { not: titles } } });

Will work as expected.
The current limitation applies to String[] or any other field for which the exact database type is an array of scalar. The latter is only supported by Postgres though.
I created an issue in the prisma/prisma repo to summarize the problem and suggested solutions: https://github.com/prisma/prisma/issues/3475
I would suggest people to track this one instead

Additional context/request in https://github.com/prisma/prisma-client-js/issues/334.

any update on when we can expect this feature? thanks!

We're wrapping up group by this sprint, so this is something that we'll have to look at after the holidays, early next year.

Hey folks, here's the current plan for supporting filtering scalar list fields.
Please let me know if you have any thoughts, concerns or suggestions!
You can also schedule time with me to discuss privately: https://calendly.com/matthewmueller/prisma

Functionality
Databases

Postgres

Supported Operations

findFirst
findMany
groupBy
aggregate

Capabilities
We add the following has, hasEvery, hasSome and isEmpty as filters for scalar lists. These capabilities can be combined with our NOT, OR, and AND operations.

has: a value is contained within a list

[1, 2, 3] has 1 is true
[1, 2, 3] has 4 is false

hasEvery: all values are contained within the list

[1, 2, 3] hasEvery [1, 2] is true
[1, 2, 3] hasEvery [1, 2, 4] is false

hasSome: at least one values is contained in the list

[1, 2, 3] hasSome [1, 2] is true
[1, 2, 3] hasSome [1, 2, 4] is true
[1, 2, 3] hasSome [4, 5] is false

isEmpty: the list is empty

[] is empty is true
[1] is empty is false

Supported Types
We'll start by trying to add all the types, see how the tests react and adjust our expectations accordingly.
Must Haves

String[]
Enum[]

Nice to Haves

Int[]
Float[]
Boolean[]
DateTime[]

Icing on the Cake

BigInt[]
Decimal[]

Out of Scope

Json[]
Bytes[]
Postgres native types and extensions (e.g. uuid, citext, postgis)

Example
Given the following Schema:
model User {
  id     Int      @id
  active Boolean
  roles  String[]
  titles Title[]
  level  Int[]
}

enum Title {
  Dr
  Ing
  Esq
}

You should be able to query:
*// Read: Find first user who has a "Dr" title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains the given value
      has: "Dr"
    }
  }
})

// *Read: Find first user who has both a "Dr" and "Ing" Title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains all the given values.
      // In this case both "Dr" and "Ing"
      hasEvery: ["Dr", "Ing"]
    }
  }
})

// *Read: Find first user who either a "Dr" or a "Ing" Title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains at least one of the given values.
      // In this case "Dr" or "Ing"
      hasSome: ["Dr", "Ing"]
    }
  }
})

// *Read: Find first user who has no titles.*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" is empty
      isEmpty: true // or hasNone
    }
  }
})

// These filter clauses (contains, some, every, none) should work for
// findFirst, findMany & findUnique. (TODO: aggregate, groupBy too?)
//
// They should also work with other where clauses. The operations are
// ANDed.
//
// Read: find all active users that have either a Dr or Ing title.
await prisma.user.findMany({
  where: {
    active: true
    titles: {
      hasSome: ["Dr", "Ing"]
    }
  }
})

// Works with explicit OR clauses too.
//
// Read: find all active users that have either a Dr. or Ing. title
// OR don't have any titles.
await prisma.user.findMany({
  where: {
    active: true,
    OR: [
      titles: {
        hasSome: ["Dr", "Ing"]
      },
      titles: {
        isEmpty: true
      },
    ]
  }
})

// Lastly, everything above should also work for Enum and Int types.
await prisma.user.findMany({
  where: {
    active: true,
    OR: [
      roles: {
        hasSome: ["email:read", "user:write"]
      },
      roles: {
        hasNone: true
      },
    ]
  }
})

Hey folks, here's the current plan for supporting filtering scalar list fields.
Please let me know if you have any thoughts, concerns or suggestions!
You can also schedule time with me to discuss privately: https://calendly.com/matthewmueller/prisma

Functionality
Databases

Postgres

Supported Operations

findFirst
findMany
groupBy
aggregate

Capabilities
We add the following has, hasEvery, hasSome and isEmpty as filters for scalar lists. These capabilities can be combined with our NOT, OR, and AND operations.

has: a value is contained within a list

[1, 2, 3] has 1 is true
[1, 2, 3] has 4 is false

hasEvery: all values are contained within the list

[1, 2, 3] hasEvery [1, 2] is true
[1, 2, 3] hasEvery [1, 2, 4] is false

hasSome: at least one values is contained in the list

[1, 2, 3] hasSome [1, 2] is true
[1, 2, 3] hasSome [1, 2, 4] is true
[1, 2, 3] hasSome [4, 5] is false

isEmpty: the list is empty

[] is empty is true
[1] is empty is false

Supported Types
We'll start by trying to add all the types, see how the tests react and adjust our expectations accordingly.
Must Haves

String[]
Enum[]

Nice to Haves

Int[]
Float[]
Boolean[]
DateTime[]

Icing on the Cake

BigInt[]
Decimal[]

Out of Scope

Json[]
Bytes[]
Postgres native types and extensions (e.g. uuid, citext, postgis)

Example
Given the following Schema:
model User {
  id     Int      @id
  active Boolean
  roles  String[]
  titles Title[]
  level  Int[]
}

enum Title {
  Dr
  Ing
  Esq
}

You should be able to query:
*// Read: Find first user who has a "Dr" title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains the given value
      has: "Dr"
    }
  }
})

// *Read: Find first user who has both a "Dr" and "Ing" Title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains all the given values.
      // In this case both "Dr" and "Ing"
      hasEvery: ["Dr", "Ing"]
    }
  }
})

// *Read: Find first user who either a "Dr" or a "Ing" Title*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" contains at least one of the given values.
      // In this case "Dr" or "Ing"
      hasSome: ["Dr", "Ing"]
    }
  }
})

// *Read: Find first user who has no titles.*
await prisma.user.findFirst({
  where: {
    titles: {
      // "title" is empty
      isEmpty: true // or hasNone
    }
  }
})

// These filter clauses (contains, some, every, none) should work for
// findFirst, findMany & findUnique. (TODO: aggregate, groupBy too?)
//
// They should also work with other where clauses. The operations are
// ANDed.
//
// Read: find all active users that have either a Dr or Ing title.
await prisma.user.findMany({
  where: {
    active: true
    titles: {
      hasSome: ["Dr", "Ing"]
    }
  }
})

// Works with explicit OR clauses too.
//
// Read: find all active users that have either a Dr. or Ing. title
// OR don't have any titles.
await prisma.user.findMany({
  where: {
    active: true,
    OR: [
      titles: {
        hasSome: ["Dr", "Ing"]
      },
      titles: {
        isEmpty: true
      },
    ]
  }
})

// Lastly, everything above should also work for Enum and Int types.
await prisma.user.findMany({
  where: {
    active: true,
    OR: [
      roles: {
        hasSome: ["email:read", "user:write"]
      },
      roles: {
        hasNone: true
      },
    ]
  }
})

Couple of observations:

Json[] might be out of scope, but we still have to think how we will be able to compare elements inside the array when its going to be objects so it won't be necessary to do a breaking change later on.
Will it work if we have ids String[] where the underlining storage type is UUID[]?
One nice to have would be hasNone which is basically a NOT: { field: hasSome(...) }, but easier to read.

Couple of observations:

Json[] might be out of scope, but we still have to think how we will be able to compare elements inside the array when its going to be objects so it won't be necessary to do a breaking change later on.
Will it work if we have ids String[] where the underlining storage type is UUID[]?
One nice to have would be hasNone which is basically a NOT: { field: hasSome(...) }, but easier to read.

With the proposal above, how would one check if two arrays are equal?
hasEvery allows for the array in the DB to have more values than the array in the filter. In my use case equality check of two arrays is what I need.

With the proposal above, how would one check if two arrays are equal?
hasEvery allows for the array in the DB to have more values than the array in the filter. In my use case equality check of two arrays is what I need.

I think the default behaviour that already exists is strict equality @nrxus

I think the default behaviour that already exists is strict equality @nrxus

Oh I could have swore that wasn't there a few versions ago. Thanks!

Oh I could have swore that wasn't there a few versions ago. Thanks!


Fix the 'ssh failed to start error' on every chef run.

This change pulls out the first commit of #1271 and just applies a simple diff to fix the error.
The default service provider now works fine for ssh on ubuntu 14.04, so we can use it instead of a manual execution resource.
Tested under the following scenarios:

ssh is disabled, not yet running.
ssh is disabled, already running.
ssh is enabled, not yet running.
ssh is enabled, already running.

Tested using the following methods:
Disable the service with:
$ sudo chef-shell
chef (12.19.36)> recipe_mode
chef:recipe (12.19.36)> service 'ssh' do
chef:recipe > action :disable
chef:recipe ?> end
chef:recipe (12.19.36)> run_chef

Modify and check the status of ssh with:
$ sudo service ssh stop
$ sudo service ssh status
$ sudo service ssh start

Run this recipe with chef:
$ sudo chef-client -o 'bcpc::ssh'

The specifics of the tests are quite important; this code runs under at least a few different scenarios:
• SSH service not enabled
• SSH service running but disabled
• SSH service enabled and running
• SSH service not running seems unlikely since we ssh in
Please confirm if you've tried these three (or anyone comment if you can think of more)

The specifics of the tests are quite important; this code runs under at least a few different scenarios:
• SSH service not enabled
• SSH service running but disabled
• SSH service enabled and running
• SSH service not running seems unlikely since we ssh in
Please confirm if you've tried these three (or anyone comment if you can think of more)

Now tested under the following circumstances:

ssh is disabled, not yet running.
ssh is disabled, already running.
ssh is enabled, not yet running.
ssh is enabled, already running.

Thanks for the verification!


Thread-safe (lock-free) maps

We want to get rid from using mutex when working with maps.
We need to fix concurrent read/write in maps.
To do that we need to remove throws about concurrent write/read-write, fix growWork and evacuate() and write as many as possible tests for maps.

[x] basic implementation
[ ] tests

See also https://github.com/golang/go/issues/18177.

@bcmills thanks. glad to see that Golang team is working on this.
notice, that this issue is about replacing maps to its thread-safe and lock-free implementation, so it's not about adding something, it's about fixing original implementation while saving backward compatibility.
but, as you can see here, Go will not support thread-safe lock-free map implementation. but I'll do.

also, about the status of this issue. now I'm testing it in my stage and production environments, there's no data corruptions, no panics etc, so I think it's ready.


Can't print status

I'm trying to print the https://core.telegram.org/bots/api#chatmember -> status object but I don't see any way...

Would you mind sharing the code part that does not print as expected?

status = msg['reply_to_message']['from']['user']['status']
This is my code

You mixed User with ChatMember. There is an additional api-request needed to get the data you want:

a User is part of every Message sent into groups/supergroups/private chats
a ChatMember can be received via the method getChatMember

So:
status = msg['reply_to_message']['from']['chat_member']['status']
Should work?

No. As mentioned in my last comment, you have to do an additional api-request to get a ChatMember.
user = msg['reply_to_message']['from']
try:
    chat_member = <bot>.getChatMember(user_id=user['id'], chat_id=msg['chat']['id'])
except telepot.TelegramError as err:
    print(repr(err))
    status = None
else:
    status = chat_member['status']

Thank you! U're awesome :)


There is no service_provider default when used on Puppet 7

Describe the Bug
When the module is used with Puppet 7 clients, catalog compilation fails unless parameter postgresql::globals::service_provideris explicitly set in Hiera data or a resource-like class declaration.
This is a regression: the module used to choose a suitable provider without help.
Expected Behavior
The module should choose the target system's default service provider automatically.  The manifest set and site data should not need to specify one explicitly unless something different from the default is required.
Steps to Reproduce
Steps to reproduce the behavior:

Install puppetlabs-postgresql 9.2.0
Attempt to compile a catalog containing this declaration:include postgresql::server

with facts from a Puppet 7 client.

Catalog compilation then fails with an error such as this spec test output shows:
  1) demo on redhat-8-x86_64 is expected to compile into a catalogue without dependency cycles
     Failure/Error: it { is_expected.to compile.with_all_deps }
       error during compilation: Evaluation Error: Error while evaluating a Function Call, pick(): must receive at least one non empty value (file: /.../environments/production/modules/demo/spec/fixtures/modules/postgresql/manifests/params.pp, line: 88, column: 10) on node x.y.z
     # ./spec/classes/demo_spec.rb:10:in `block (4 levels) in <top (required)>'

Environment

Puppet 7.26.0
puppetlabs-posgresql 9.2.0
RHEL 7 server, RHEL 7-8, CentOS 7-8, Rocky 8-9 clients

Additional Context
The module seems to be trying to use $facts['service_provider']to identify the default provider, but this fact is not served by the version of facter bundled with Puppet 7.
The issue can be worked around by providing a suitable value for class parameter postgresql::globals::service_provider.

The service_provider fact is provided by stdlib since version 4.10.0: https://github.com/puppetlabs/puppetlabs-stdlib/pull/506 (released in 2015).
The module currently require version 9.0.0 or newer of stdlib:
https://github.com/puppetlabs/puppetlabs-postgresql/blob/476734001c9aade2c9731d32ce4446d7e21142bf/metadata.json#L13
Please check your module dependencies:
root@puppet ~ # puppet module list

You need to use a custom fact in your test environment. In Vox Pupuli we have a helper that automatically adds it: https://github.com/voxpupuli/voxpupuli-test/blob/8014068e5fb0c84ba61dd9abc1bf4bcc79db1470/lib/voxpupuli/test/facts.rb#L71-L96
The PDK maintainers could implement a similar workaround, but it's a problem that all modules relying on custom facts will face.
https://github.com/puppetlabs/puppetlabs-postgresql/pull/1518 will lessen the impact, but the root cause is still there.
Closing this as it can't be solved without dropping the use of the custom fact.


refactor: remove meta command

Current dependencies on/for this PR:

main

PR #31   👈

This stack of pull requests is managed by Graphite.


Recursive Render Target Renaming Makes Shaders Confusing

Like so https://github.com/Aeva/dream_machine/commit/9f7b4417614def5f5d51b5bd4930ba55b89dd875#diff-437ae06c45e54d9da008390640588351R146.
Probably just want to add a template substitution type thing for inserting the actual handles for accessing input/output targets.  So like instead of Accumulator and AccumulatorTarget for accessing Accumulator as a texture for sampling or an output target, probably just do something goofy like 「in Accumulator」 and 「out Accumulator」.  The handles could then just have "__in" and "__out" appended to them in the actual generated shader (or whatever).
This also solves the problems of not being able to rename the output target for WebGL and it not being clear when a handle is defined by the shader or generated.

This probably should just be handled in the compiler frontend.

It occurred to me that another way to simplify the backends.  In https://github.com/Aeva/dream_machine/blob/excelsior/dream_machine/opengl/solver.py#L185, the bits about SwitchTextureHandles and RebuildFrameBuffer can probably just be promoted to another sort of "Render*" event.  The frontend would handle populating these into the renderer event lists, and the backends just handle routing them to expanders.
I think in the future, things like memory barriers and residency events would work the same way for applicable backends.


tools/jxlinfo: improve CLI option parsing

Calling "jxlinfo --help" should provide the default help
message rather than failing with "failed to read file --help."
This fixes that behavior to work as expected.
This patch adds --help, --verbose, and other convenience
features, such as the ability to read multiple files with
jxlinfo.

Maybe allow -h too then?

-h and -? could both be added, if we desired

-h and -? could both be added, if we desired

Personally, I think that -h and --help would be enough, but if you think -? would also be used, then feel free to add that as well!

Aight, ready for review again, after a bunch of forcepushing


Icons everywhere

Ingredients and recipes should have icons for their respective type.

One last thing is the icons sometimes take up too much space because the table is automatically laid out. I might be able to use a fixed table layout.


upstream main merge 2021 11 29

Update SDK to 6.0 RC2 (#60256)
JIT: limited version of forward substitution for some relops (#61023)
Make System.Security.Cryptography.X509Certificates compliant with interop guidelines - part 2
lock protect nullability cache of symbolic regex node (#60942)
[DllImportGenerator] Fix stub generation for char array marshalling (#61188)
[arm64] JIT: Recognize sbfiz/ubfiz idioms (#61045)
Set IL offsets for calls created during devirtualization (#61189)
Fix Assertion failed 'ins == INS_add' for madd/msub (#61171)
Applied @marek-safar review to exit the loop once the condition is fulfilled. (#61165)
[mono][interp] Fix GetType called on ptr constrained to Nullable` (#61020)
improved BDD Unicode table representation in NonBacktracking engine (#61142)
Use constant ids for RoArrayType GetMethodsCore (#61177)
[DllImportGenerator] Use ElementMarshallingGeneratorFactory to create the marshalling generator for collection elements (#61219)
Fold S.S.C.Encoding into new System.Security.Cryptography library
Fix bug in iterator test, modify attempt count, make more robust (#61242)
JIT: Fold "shift-by-zero" in lower (#61222)
Fix comment typo (#61246)
[wasm] Revert back  to eval in wasm InvokeJS with modularization support . (#61212)
Fix UnobservedTaskException from SemaphoreSlim.WaitAsync (#60890)
JIT: don't bother with GDV for an abstract class (#61191)
Fix build options for native test lib to not enable avx-512 (#61229)
1388 xml serializer assembly load context awareness (#58932)
fix unexpected TimeSeriesLimitReached after HistogramLimitReached(#60752) (#61199)
[wasm] Add test for blazor/sdk fix for lazy loaded assemblies (#60673)
Simplify minterm generation in Regex NonBacktracking engine (#61232)
Convert to OleDb assembly and last Cryptography DllImport to GeneratedDllImport (#61184)
Update area-owners.md (#61269)
Implement GT_AND_NOT for ARM/ARM64 (#59881)
Remove BestFitMapping, CallingConvention, and ThrowOnUnmappableChar from GeneratedDllImportAttribute (#61182)
use GenTreeFlags for better debugging (#61272)
Make JitPrintInlinedMethods less verbose (#61208)
ensure the AcceptSocket is cleared when AcceptAsync completes (#61258)
Don't create a COM weak reference if the object is an aggregated COMWrappers RCW. (#61267)
Use the Xunit assert library instead of CoreCLRTestLibrary for most asserts (#61226)
Fix build failure due to conflicting PR merge (#61286)
[mono][interp] Implement tailcalls (#59799)
[wasm] Add console version of browser-bench sample (#60733)
Clean up the documentation for the library testing (#59401)
Enable global constant propagation for GT_LCL_FLD (#61209)
[main] Update dependencies from 10 repositories (#61087)
[main] Update dependencies from dotnet/runtime dotnet/xharness (#61309)
Fix value numbering of field assignments (#61113)
Removing m_hostAssemblyMap and ceremony around it (#61292)
Type key hash tweaks. (#61234)
Fix incorrect CCW decoding in GetObjectForCCW (#61193)
Remove sorting requirement for interface lists (#60541)
Fix: add missed open curly (#61320)
Fix format.py to use jit-format.exe, not jit-format.bat (#61334)
JIT: extend redundant relop to handle side effects (#61275)
Add instructions for using Codespaces (#60996)
Adding Regex source generator to Microsoft.netcore.app.ref pack (#61329)
Use UTC throughout certificate request tests
Fix binplacing for (impl) System.Security.Cryptography.Encoding.dll
Provide PEM implementations for AsymmetricAlgorithm.
[wasm][aot] Disable (again) Microsoft.Extensions.Logging.Generators.Roslyn3.11.Tests failing due to OOM (#61323)
Convert concatenation string to interpolation for System.Private.Xml (#60057)
[wasm] Remove WasmBuildTemplate (#61315)
Add additional steps in gcc validation leg (#61241)
Ensure MaxBy/MinBy return first element if all keys are null. (#61364)
Add System.Diagnostics.StackFrame.GetMethodFromNativeIP API for VS4Mac (#61289)
SPMI: Use diffed bytes for jit-analyze and print more info (#61254)
Proper VNs for zeroed structs (#61285)
Start tracking debug info for inlined statements (#61220)
Implement WebRequest CachePolicy (#60913)
Add unit test for variable length encoding HTTP/3 (#60766)
Remove unnecessary DLLIMPORTGENERATOR_ENABLED ifdefs (#61345)
Delete unused test projects (#61348)
InstallWorkload: Use the repo's nuget.config as the base for installing manifests (#60699)
[wasm] Allow enums in unmanaged callbacks. (#61377)
[arm64] JIT: Enable CSE/hoisting for "arrayBase + elementOffset" (#61293)
Change WASM direct heap access to use helper functions (#61355)
[wasm] Add task marshaling tests. (#61324)
[wasm][debugger] Correct the endian swapping and string implementation (#61386)
[wasm] Build improvements (#61276)
Delete unused mono_unbox_int (#61384)
fix lint issue (#61433)
Fix common workflow issues (#61027)
Update timeout for sourcebuild (#61436)
Baseline two failing tests to make outerloop green again (#61280)
Fix inconsistency in p/invoke arguments introduced when switching some to be blittable (#61071)
Create superpmi-asmdiffs pipeline (#61194)
[main] Update dependencies from dotnet/arcade dotnet/icu dotnet/emsdk dotnet/hotreload-utils dotnet/llvm-project (#61365)
[DllImportGenerator] Initialize by-value out array to default (#61431)
Remove dead code (#61427)
Explicitly mark tests with CLRTestKind=SharedLibrary (#61235)
Fix Array ctor integer widening and add Reflection tests (#61347)
Fix CI trigger of superpmi-asmdiffs pipeline (#61444)
JIT: slightly more aggressive tail duplication (#61179)
Clean up tests under Interop/PInvoke/BestFitMapping (#61390)
Include the "TargetingPack" folder in the mobile apps. (#61432)
Some more precise debug info improvements (#61419)
[Mono] Skip flaky android tests (#61460)
Fix bug where we reference the entry #0 in the pinned plug queue (#60966)
[main] Update dependencies from 5 repositories (#61463)
Use DllImportGenerator in System.Diagnostics.PerformanceCounter (#61389)
Refine superpmi-replay trigger (#61469)
Enable sourcelink in source-build for '.version' file (#60944)
Add tests for metricseventsource HistogramLimitReached(#60752, #61199) (#61449)
Add PEM PKCS#8 and SPKI exports for AsymmetricAlgorithm
Updating src/tests/Interop/PInvoke/Generics/GenericsNative.Vector* to annotate individual methods as requiring AVX (#61259)
XARCH: Remove redudant tests for GT_LT/GT_GE relops. (#61152)
Implement Narrow and Widen using SIMDAsHWIntrinsic (#60094)
[wasm] Add AppStart task to the bench Sample (#61481)
System.IO files cleanup (#61413)
Remove explicit '.exe' extension from assembly names in ilproj tests (#61479)
Lock non localizable strings on regex resources (#61489)
Remove all DLLIMPORTGENERATOR_ENABLED usage. (#61476)
[mono][jit] Optimize constrained calls to object.GetHashCode () where the receiver is a gshared type constrained to a primitive type/enum. (#61513)
[mono][jit] Optimize calls to Type:get_IsValueType () on gshared constrained types. (#61514)
Fix optIsLoopEntry to skip removed loops (#61527)
Update exception docs (#61278)
[DllImportGenerator] Treat pointer fields in structs as blittable regardless of what they point at (#61538)
[mini] Allow MONO_VERBOSE_METHOD=':' (#61520)
Update how OSR and PGO interact (#61453)
[mono] Add a 'inline_method' profiler event. (#61454)
[mono] Disable partial generic sharing for gparams with non-enum constraints. (#59437)
Enable new analyzers in global configs (#60914)
Add [Fact] attributes on TypeGeneratorTests (#61534)
Completely lock-free ClassLoader::LookupTypeKey (#61346)
Add [Fact] attributes to methodical JIT tests (#61536)
Add [Fact] attributes to JIT regression tests (#61540)
Enable 54910 tests (#61564)
Alternative fix of #60182 (#60298)
[main] Update dependencies from dotnet/linker (#61094)
Add JsonSerializerOptions.Default (#61434)
Delete __DoCrossgen2 (#61582)
[main] Update dependencies from 3 repositories (#61568)
Rewrite selection for fields (#61370)
Disable poisoning for large structs (#61589)
SortedList<TKey, TValue> added GetKeyAtIndex, GetValueAtIndex, and SetValueAtIndex (#60520)
Remove the "anything + null => null" optimization (#61518)
Use Span.Fill in String(Char, Int32) constructor  (#60269)
Use GeneratedDllImport for blittable p/invokes in System.Diagnostics.Process, System.Diagnostics.Process, System.Diagnostics.FileVersionInfo, System.Runtime.InteropServices.RuntimeInformation (#61532)
Update workflow docs to indicate ARM64 macOS works (#61575)
FileSystem.Unix: improve CopyFile. (#59695)
Exclude the managed code around libproc on iOS/tvOS (#61590)
Fix CharInClass reference in regex emitter (#61559)
Fix LastWriteTime and LastAccessTime of a symlink on Windows and Unix (#52639)
Improve System.Speech trimmability (#61566)
Delete dead code (#61533)
There shouldn't be a 'lib' prefix on Windows .lib files (#61618)
Loop refactoring and commenting improvements (#61496)
Give write access to backport action explicitly (#61626)
Create runtime staging clone to manually kick off full test runs (#61443)
Adding support for X86Base.Pause() and ArmBase.Yield() (#61065)
[wasm] parallel asset loading (#61610)
Delete impCheckForNullPointer (#61576)
Enable SymbolicRegexNode.IsNullableFor fast path to inline (#61605)
Use GeneratedDllImport in Microsoft.Win32.SystemEvents (#61609)
Restrict GITHUB_TOKEN in markdownlint action (#61622)
Allow for backport to report progress to PR (#61637)
Only run JIT formatting job if there are JIT changes (#61632)
Obsolete thumbtacked AssemblyName properties (#59522)
Add tests for CNG symmetric key algorithm mismatches
XArch: Trim the code block to match the actual code length (#61523)
Provide locations for src-gen diagnostic output (#61430)
Fix SuperPMI Python script Azure usage (#61650)
Give create codespaces prebuild action right permissions (#61651)
[arm64] JIT: Make 0.0 containable for fcmp (#61617)
Disable fgMorphCastedBitwiseOp opt for floats (#61657)
Fix poisoning for very large structs (#61521)
[wasm] Rework fetch (#61639)
[wasm][debugger] Improvement of memory consumption while Evaluating Expressions (#61470)
[wasm][debugger] View multidimensional array when debugging (#60983)
Update WASM README.md (#61681)
Use GeneratedDllImport for blittable p/invokes in System.IO.Compression, System.IO.Compression.Brotli, System.Net.Http, System.Net.NameResolution (#61638)
Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 1472678 (#61680)
[DllImportGenerator] Stop ignoring QCalls when looking for methods to convert to GeneratedDllImport (#61678)
Add .runsettings file to be able to run and debug tests on vscode in codespace with prebuilt (#61684)
Add [Fact] attributes to all remaining ilproj tests (#61625)
JIT: don't import IL for partial compilation blocks (#61572)
Update SPCL to use GeneratedDllImport where possible. (#61640)
[wasm] renames and cleanup before modularization (#61596)
[mono][aot] Fix the inclusion of generic instances when doing profiled AOT. (#61627)
[wasm][debugger] Fix evaluation of a static class attribute; using current namespace for evaluation (#61252)
Minor File.ReadAllBytes* improvements (#61519)
Extend RegexCharClass.Canonicalize range inversion optimization (#61562)
Remove some unnecessary slicing from generated Regex code (#61701)
Ignore missing data result from superpmi-replay run (#61699)
refactoring (#60074)
Remove XUnit reference metadata from tests I switched over last week (#61691)
[DllImportGenerator] Enable on projects without System.Memory and System.Runtime.CompilerServices.Unsafe (#61704)
Factor out and improve the vectorization of RegexInterpreter.FindFirstChar (#61490)
A few follow up changes to LookupTypeKey change (#61718)
HostFactoryResolver - Increase default timeout to thirty seconds (#61621)
Merge System.Security.Cryptography.Algorithms to System.Security.Cryptography
Skip HardwareIntrinsics/x86base/Pause tests on Mono (#61743)
Update docker image (#61217)
src/tests tree test xunit-based source generated runner (#60846)
Remove DisableImplicitNamespaceImports_DotNet (#61656)
Upload dasm files as artifacts for "asmdiffs pipeline" (#61700)
[wasm][debugger] Tie sdb agent lifetime to the ExecutionContext and simplify the api (#61392)
Remove race condition from DllImportGenerator build (#61695)
Hide 'align' instruction behind jmp (#60787)
Create runtime clone to manually kick off full test runs (#61641)
Update DNNE version (#61738)
Convert Crypto P/Invokes to GeneratedDllImport. (#61742)
Use GeneratedDllImport in System.Data.Odbc, System.IO.Ports, System.ServiceProcess.ServiceController (#61741)
Reduce the output from tests. (#61593)
CreateDirectory: eliminate some syscalls. (#58799)
FileSystemEntry.Unix: ensure properties are available when file is deleted. (#60214)
FileStatus.Unix/Process.Unix: align caching of user identity. (#60160)
Add support for dumping and using precise debug info (#61735)
Add single char lazy loop support to simplified Regex code gen (#61698)
Update Area Owners for System.Data (#61748)
Remove duplicate checks (#61766)
[iOS] Follow up changes for 61590 (#61670)
[Group 4] Enable nullable annotations for Microsoft.Extensions.Configuration.Binder (#57418)
Actually use TargetOS=AnyOS in the build-test-job. (#61745)
Add ThrowIfNull overload for pointers (#61633)
Add tests verifying fast-path semantics for nullable structs (#61711)
Revert "Actually use TargetOS=AnyOS in the build-test-job. (#61745)" (#61799)
Fix the only ilproj test that uses multiple command-line variants (#61750)
Fix building DllImportGeneratorSample (#61806)
Convert System.Net.* over to GeneratedDllImport (#61765)
JIT: support OSR for synchronized methods (#61712)
Apply BuiltInComInterop feature switch to managed code (#54056)
[Group 4] Enable nullable annotations for Microsoft.Extensions.Configuration.EnvironmentVariables (#57433)
Add JitDisasmWithDebugInfo (#61780)
[DllImportGenerator] Don't flag methods with known unsupported UnmanagedType (#61808)
Improve superpmi-asmdiffs AzDO pipeline robustness (#61819)
Skip System.Diagnostics.TextWriterTraceListenerTests.XmlWriterTraceListenerTests on iOS/tvOS (#61807)
Try to skip pause_* tests again (#61793)
Include arch specific headers in standalone JITs (#61800)
Disable several failing tests on iOSSimulator arm64 (#61826)
Reduce allocations for CreateDirectory (#61777)
Expand One/Notone/Setlazy support to Lazy (#61784)
Switch IP mapping lists to use jitstd::list (#61822)
Integration of changes in shared files from runtimelab/NativeAOT (#61655)
Enable DD117522 test (#61585)
Allow runtimeconfig StartupHooks and Environment StartupHooks to both be present (#61461)
Create empty zip files (#61828)
[Group 4] Enable nullable annotations for Microsoft.Extensions.Configuration.CommandLine (#57432)
Update area-owners to reflect Libraries Area Pod changes (#61642)
[wasm] Disable System.Text.RegularExpressions.Tests for AOT (#61803)
[wasm] Run AOT, and Wasm.Build.Tests on windows (#59479)
Make intrinsic nodes multi op (aka delete GT_LIST) (#59912)
Update GetPinnableReference() usage in multi-step custom type marshalling (#61539)
Use reflection or a compile-time only shim assembly to reference unexposed corelib types. (#61802)
Do not devirtualize if optimizations disabled (#61868)
Actually use TargetOS=AnyOS in the build-test-job (Try 2) (#61801)
Fix a few special cases of projects with command line arguments (#61758)
Mark PLINQ as enabled in WASM and make browser compat changes (#58227)
Fix XXHash for stripe size (#61881)
[HTTP] Scavange fix (#61530)
Rename CORINFO_FLG_CONTAINS_STACK_PTR to CORINFO_FLG_BYREF_LIKE (#61907)
Make System.DirectoryServices.AccountManagement use GeneratedDllImport (#61805)
Default BuildTargetFramework to NetCoreAppCurrent so that the ref is (#61760)
JIT: refactor to allow OSR to switch to optimized (#61851)
Skip eventpipe_readevents for arm32 (#58545)
Revert "[Mono] Skip flaky android tests (#61460)" (#61771)
Make S.S.C.X509Certificates compliant with interop guidelines - part 3
Do not explicitly pass type to VNForMapStore (#61882)
Vectorize SpanHelpers.IndexOf (#60974)
Delete Regex timeout tests with RegexOptions.Debug (#61888)
Use correct VN relation kind for redundant relop opts (#61912)
Don't special case "Experimental" projects (#60641)
Add a JsonWriterOptions.MaxDepth property (#61608)
Extract ECAlgorithm from ECDsa and ECDiffieHellman
Update list of analyzer diagnostics with JSON entries (#61809)
Adding support for the X86Base.Pause intrinsic on Mono (#61707)
Fix regression in IsPrefix / IsSuffix benchmarks (#61935)
Add backtracking loops, backreferences, and if-then-else constructs to Regex "simplified" code gen (#61906)
Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 1482158 (#61858)
Disable changing align nop padding to breakpoints for arm64 under jit stress (#61951)
Use GeneratedDllImport in Microsoft.Extensions.Hosting.WindowsServices, System.Drawing.Primitives, System.Management, System.Security.Cryptography.ProtectedData, System.Speech, System.Windows.Extensions (#61949)
Add Clear() to MemoryCache (#57631)
Added AsReadOnly extension methods for IDictionary<T, U> and IList (#61172)
Update Proxy-Support check to be case insensitive (#61446)
[wasm] workaround test results corruption (#61841)
[System.Text.Json] Move inline throw statements to ThrowHelper (#61746)
FileSystem.Unix: Directory.Delete: remove per item syscall. (#59520)
Environment variable should override property for gcServer. (#61950)
Disable several GenericMath tests on iOS/tvOS (#61922)
[mono] Don't use recursion in mono_ssa_rename_vars (#61677)
removed argument requestId from loopbackserver.cs (#58678)
Stabilize host's UpgradeCode and ProviderKey (#61810)
Check for time-sensitive work when worker thread starvation is ongoing (#61930)
Delete dead code from InferStructOpSizeAlign (#61880)
[mono] Remove support for Classic Xamarin for the Selector.GetHandle optimization, and add newer platforms. (#61989)
[wasm] Misc CI/test run improvements (#61937)
prevent concurrent access to IO buffers on macOS (#61723)
Make more extensive use of lvaGetDesc() (#61494)
Clean up test intermediates when clean test rebuild is requested (#62001)
Use separate partials for iOS&tvOS instead of UnknowUnix in System.Diagnostics.Process (#61871)
Fix Android crypto asserts (#61827)
Add RequiresDynamicCodeAttribute to runtime (#61956)
Add some tests that validate debug info through ETW events (#61962)
[wasm] [debugger] Eval fixes for static class eval (#61660)
Nullable annotation for System.Windows.Extensions (#57896)
Added null checks to prevent null pointer exception (#62013)
Unify ARRAY_SIZE/STRING_LENGTH-like macros (#61537)
Fix calling NLS with Cultures has alternative sort names (#61992)
The DestroyStructure API passes null to the IL marshaller for (#61985)
Use GeneratedDllImport in System.Diagnostics.EventLog (#61990)
Splitting the hardware intrinsic tests into more test groupings (#61973)
Remove SupportedOSPlatformAttribute("windows") from LdapSessionOption (#61388)
Handle empty string parameter value in MetadataLoadContext (#61457)
Use GeneratedDllImport for blittable p/invokes in System.Console, System.IO.FileSystem.Watcher, System.IO.Pipes (#61996)
Reorganize libs.native (#61958)
Update path of disabled test that was moved (#62051)
[wasm] debug with modularized runtime(s) (#61848)
[mono][interp] Fix handing of native types (#61612)
Add a github action to sync shared source from aspnetcore (#61999)
Integration of changes in shared files from runtimelab/NativeAOT (#62039)
Re-enable Windows test that verifies DriveInfo.VolumeLabel setter fails on SUBST'd drive (#59850)
Add endHeader flag to QPACK decode (#62059)
[wasm][debugger] Stepping into hidden function. (#61312)
Exclude a newly added test on Mono (#62056)
Suppress trim warning caused by recent attribute removal changes (#62023)
Fix setting pipe as nonblocking (#61126)
Avoid switching GC mode in COM's HasValidTarget (#62066)
Refactor writing QPACK status (#62069)
fix for excessive gen0 in high memory load situation (#61884)
[main] Update dependencies from 8 repositories (#61668)
Fix miscellaneous typos (#62062)
Flip IL offset check (#62049)
[mono]mono_runtime_delegate_invoke change to gc unsafe state (#62003)
Update hash of the new CSE when resizing (#61984)
Fix optComputeLoopSideEffects to account for HWI stores (#61911)
CI matrix change: add Windows.Server.Core.20H2 - Second attempt (#60054)
[wasm] Use cross origin policy headers (#62016)
[main] Update dependencies from 3 repositories (#62098)

I'm leaving this PR open so that we can review it as part of https://github.com/Unity-Technologies/runtime/pull/8. I don't plan to merge it though.

Closing to test a new PR.


Kubeflow does not handle evicted Pods correctly

When you leave Charmed Kubeflow (CKF) running for some time - Pods eviction happens. The evicted Pods stay in the system until the GC of evicted Pods is invoked. Based on the default value of vanilla Kubernetes it happens when 12.500 Pods Evicted Pods are in the system.
On the running CKF when Eviction happens Pods are left in juju which means that the leadership is not transferred from Evicted Pod to the newly created one.
Reproduce:

Deploy Charmed Kubeflow on Kubernetes with 2 Nodes (make sure that Kubeflow Pods are placed on both Nodes)
Drain one of the Nodes
Wait for Pods to be moved to another Node.
Check juju status

Workaround:
Manually remove all Evicted Pods

@Barteus you're talking about eviction of the charm operator pods, right?  Not the underlying kubeflow workload pods (like the actual kfp-api workload, etc)?
I wonder whether we're missing some logic in our charms, or if Juju is mishandling something

Needs investigration.

This issue requires us to go through the charms and see which ones are affected.


QA - Opacity

This issue is for testing the Opacity functionality. Below are steps intended to aid with testing. These are the features covered in this issue:
Product Spec Doc
QA Steps

Add a background image
Add text to the page and reduce the opacity
Add a shape to the page and reduce the opacity
Add an image to the page and reduce the opacity

closing this as CUJ testing will cover any required tests