Christopher

Provide credentials for base image different from the image to be built

2

Hi, i have the following setup: Dockerfile of "child" image ``` FROM quay.io/team/base ...do something... ``` quay.io need authentication and the following would work as expected. ``` - name: docker-image-tools...

Changelog for slices inconsistent when using pointer values

1

We want to compare slices of strings. Following example code: ``` type TestStruct struct { Slice []string `json:"slice"` } type TestData struct { TS *TestStruct } func main() { s1...

add throwable information to xml layout if present

1

Include the throwable information, that are present in the LoggerLoggingEvent, into the xml layout if present

before hook only executed once in open mode with `experimentalRunAllSpecs`

4

### Current behavior When adding a `before` hook in the support file, it is only executed once at the beginning of the first test that gets executed. ### Desired behavior...

[material-ui][Filled Input] Undocumented non-themeable values

5

### Steps to reproduce Link to live example: https://github.com/mui/material-ui/blob/0b38955227cf4fc879fea5c8d23e167a5b9c4936/packages/mui-material/src/FilledInput/FilledInput.js#L45-L49 and e.g. https://github.com/mui/material-ui/blob/0b38955227cf4fc879fea5c8d23e167a5b9c4936/packages/mui-material/src/FilledInput/FilledInput.js#L52 Nothing to reproduce. ### Current behavior After searching for hours where the background colors for the FilledInput come...

Broken SQL generation after v.1.25.6/7 (nested Where?)

3

## GORM Playground Link https://github.com/go-gorm/playground/pull/689 ## Description It looks like something in v.1.25.6 changed / broke, how SQL (at least for Postgres) is generated. Especially in the case of nested...

Hi, I got into a problem when ActiveMQ is not reachable when I try to read a frame. Function nesting level 100 reached, is the fatal error that is thrown....

## Explain your user case and expected results After gorm `v.1.25.5` (so `1.25.6` upwards) nested `Where`'s lead to different SQL output with Postgres (did not check other engines) and ultimately...

**Updates** - Affected products - Summary **Comments** Missing version constraint for the CVE. Source: https://go-review.googlesource.com/c/go/+/591255 (merged into 1.21 and 1.22 release branch)

Update docs to reflect db.Save behavior

1

## Description Please update the docs at https://gorm.io/docs/update.html#Save-All-Fields to reflect the correct behavior. It looks like `db.Save` does only `INSERT` but never `UPDATE` different then mentioned in that section.