- Sort Score
- Num 10 results
- Language All
Results 51 - 60 of 1,346 for happened (0.06 seconds)
-
docs/changelogs/changelog_3x.md
`Cache.urls()` would prevent in-flight entries from being written. ## Version 3.14.3 _2019-09-10_ * Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this happened enough then eventually the connection would stall. * Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
Created: Fri Apr 03 11:42:14 GMT 2026 - Last Modified: Sun Feb 06 14:55:54 GMT 2022 - 50.8K bytes - Click Count (0) -
src/archive/tar/reader.go
// of treating these fields as the USTAR prefix field. // // Note that this will not use the fallback logic for all possible // files generated by a pre-Go1.8 toolchain. If the generated file // happened to have a prefix field that parses as valid // atime and ctime fields (e.g., when they are valid octal strings), // then it is impossible to distinguish between a valid GNU file // and an invalid pre-Go1.8 file.
Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Tue Oct 07 19:46:36 GMT 2025 - 26.9K bytes - Click Count (0) -
cmd/bucket-replication.go
TaggingTimestamp = "tagging-timestamp" // ObjectLockRetentionTimestamp - the last time a object lock metadata modification happened on this cluster for this object version ObjectLockRetentionTimestamp = "objectlock-retention-timestamp" // ObjectLockLegalHoldTimestamp - the last time a legal hold metadata modification happened on this cluster for this object version
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 118.2K bytes - Click Count (0) -
doc/go_mem.html
which are unordered by happens before (that is, neither <i>r</i> happens before <i>w</i> nor <i>w</i> happens before <i>r</i>). </p> <p> A <i>write-write data race</i> on memory location <i>x</i> consists of two write-like memory operations <i>w</i> and <i>w'</i> on <i>x</i>, at least one of which is non-synchronizing, which are unordered by happens before. </p> <p>
Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Tue Aug 05 15:41:37 GMT 2025 - 26.6K bytes - Click Count (0) -
tests/generics_test.go
db := gorm.G[User](DB) for idx, pet := range user.Pets { pet.Toy = Toy{Name: "toy_nested_preload_" + strconv.Itoa(idx+1)} } if err := db.Create(ctx, &user); err != nil { t.Fatalf("errors happened when create: %v", err) } user2, err := db.Preload("Pets.Toy", nil).Preload("Friends.Pets", func(db gorm.PreloadBuilder) error { return nil }).Where(user.ID).Take(ctx) if err != nil {Created: Sun Apr 05 09:35:12 GMT 2026 - Last Modified: Tue Dec 30 08:11:14 GMT 2025 - 34.9K bytes - Click Count (0) -
tests/migrate_test.go
} if err := DB.Table("column_structs").Migrator().AlterColumn(&ColumnStruct{}, "Name"); err != nil { t.Fatalf("no error should happened when alter column, but got %v", err) } if err := DB.Table("column_structs").AutoMigrate(&ColumnStruct2{}); err != nil { t.Fatalf("no error should happened when auto migrate column, but got %v", err) } if columnTypes, err := DB.Migrator().ColumnTypes(&ColumnStruct{}); err != nil {
Created: Sun Apr 05 09:35:12 GMT 2026 - Last Modified: Sat Mar 21 11:49:01 GMT 2026 - 66.3K bytes - Click Count (0) -
docs/bucket/notifications/README.md
The steps below show how to use this notification target in `namespace` and `access` format. ### Step 1: Add Redis endpoint to MinIO
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Tue Aug 12 18:20:36 GMT 2025 - 84.2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.27.md
- Fixed data race in `kube-scheduler` when preemption races with a Pod update. ([#116395](https://github.com/kubernetes/kubernetes/pull/116395), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Jul 17 07:48:22 GMT 2024 - 466.3K bytes - Click Count (2) -
CHANGELOG/CHANGELOG-1.15.md
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu May 05 13:44:43 GMT 2022 - 278.9K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.29.md
- Fixed a situation when, sometimes, the scheduler incorrectly placed a pod in the `unschedulable` queue instead of the `backoff` queue. This happened when some plugin previously declared the pod as `unschedulable` and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the `active`...
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Mar 12 00:36:01 GMT 2025 - 429.6K bytes - Click Count (1)