Feature/translate json functions #29306 #30010

…ty type as keyless. (dotnet#32032) Fixes dotnet#24722

[main] Update dependencies from dotnet/arcade - React to xunit breaking changes

…to parent table. (dotnet#32031) Similar to JSON entities, owned entities that are mapped to the same table as their owner should be treated as scalars for the purpose of temporal query validation - they are always in sync with the parent entity, so all operations should be allowed for them, not only AsOf. Fixes dotnet#29156

…1012.7 (dotnet#32044) [main] Update dependencies from dotnet/runtime

…1013.17 (dotnet#32049) [release/8.0] Update dependencies from dotnet/runtime

…1014.1 (dotnet#32050) [main] Update dependencies from dotnet/runtime

…1014.5 (dotnet#32054) [main] Update dependencies from dotnet/runtime

…010.4 (dotnet#32057) [main] Update dependencies from dotnet/arcade

…005.1 (dotnet#32061) [release/8.0] Update dependencies from dotnet/arcade

…1015.3 (dotnet#32060) [main] Update dependencies from dotnet/runtime

…n the base. (dotnet#32041) Fixes dotnet#26218 Fixes dotnet#27404

…1016.9 (dotnet#32067) [release/8.0] Update dependencies from dotnet/runtime

…1016.15 (dotnet#32068) [release/8.0] Update dependencies from dotnet/runtime

)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

… 7.0.12 (dotnet#32063) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…1017.2 (dotnet#32074) [main] Update dependencies from dotnet/runtime

Fixes dotnet#32052

…1017.12 (dotnet#32079) [release/8.0] Update dependencies from dotnet/runtime

…1017.16 (dotnet#32080) [release/8.0] Update dependencies from dotnet/runtime

…017.7 (dotnet#32081) [main] Update dependencies from dotnet/arcade

…1018.7 (dotnet#32089) [release/8.0] Update dependencies from dotnet/runtime

…could not be translated (dotnet#31996) Problem was that optimizing visitor was looking for a very specific pattern (member access over conditional), but in this scenario conditional is wrapped around Convert node. Fix is to recognize this case also, strip convert around the conditional and apply it around non-null portion instead, before applying the member access over it. Fixes dotnet#31961

…1018.12 (dotnet#32091) [release/8.0] Update dependencies from dotnet/runtime

…1018.26 (dotnet#32095) [release/8.0] Update dependencies from dotnet/runtime

…1019.1 (dotnet#32096) [main] Update dependencies from dotnet/runtime

…1020.1 (dotnet#32106) [main] Update dependencies from dotnet/runtime

…1019.13 (dotnet#32112) [release/8.0] Update dependencies from dotnet/runtime

…1020.9 (dotnet#32114) [release/8.0] Update dependencies from dotnet/runtime

…1020.16 (dotnet#32115) [release/8.0] Update dependencies from dotnet/runtime

…1021.1 (dotnet#32118) [main] Update dependencies from dotnet/runtime

…1021.5 (dotnet#32125) [main] Update dependencies from dotnet/runtime

…018.2 (dotnet#32132) [main] Update dependencies from dotnet/arcade

…1023.1 (dotnet#32133) [main] Update dependencies from dotnet/runtime

…016.4 (dotnet#32134) [release/8.0] Update dependencies from dotnet/arcade

…1023.3 (dotnet#32138) [release/8.0] Update dependencies from dotnet/runtime

…1023.10 (dotnet#32146) [release/8.0] Update dependencies from dotnet/runtime

… when using SplitQuery() or ToList() inside projection. (dotnet#32094) Problem was that our SqlExpression simplifying visitor, when visiting ShapedQuery would only look into QueryExpression part. This makes sense in general as QueryExpression is where the SqlExpression is stored. However, for split query scenarios, we also have SqlExpression in the ShaperExpression (wrapped by RelationalSplitCollectionShaperExpression), and all the optimizations were not run on that SqlExpression piece, which in that case caused too deep CASE WHEN ELSE structure (that we normally optimize into flat CASE with multiple WHENs. Fix is to also visit ShaperExpression when performing post processing. Fixes dotnet#32023

…s invalid SQL commands for migration (dotnet#32102) Problem was that alter column from nullable to non-nullable on a temporal table requires us to disable versioning, so that null values could be properly updated to the new defaults. Fixes dotnet#32062

…1023.12 (dotnet#32148) [release/8.0] Update dependencies from dotnet/runtime

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…1023.13 (dotnet#32153) [main] Update dependencies from dotnet/runtime

…of ValueBuffer (dotnet#32099) Fixes dotnet#31117 Part of dotnet#26544

…ntimeModel (dotnet#32124) Fixes dotnet#31142 Fixes dotnet#19361

…1024.7 (dotnet#32158) [release/8.0] Update dependencies from dotnet/runtime

…t-runtime

Fixes dotnet#31583

* Fix failing tests * fixup! Fix failing tests Hmm, is there some non-determinism here?

Fixes dotnet#32105

[main] Update dependencies from dotnet/runtime

…1027.14 (dotnet#32175) [main] Update dependencies from dotnet/runtime

…1028.2 (dotnet#32177) [main] Update dependencies from dotnet/runtime

…028.2 (dotnet#32182) [main] Update dependencies from dotnet/arcade

…025.4 (dotnet#32184) [release/8.0] Update dependencies from dotnet/arcade

…1029.4 (dotnet#32183) [main] Update dependencies from dotnet/runtime

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

… 7.0.13 (dotnet#32189) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…t-runtime

…1030.14 (dotnet#32195) [main] Update dependencies from dotnet/runtime

…ng/internal/dotnet-runtime This pull request updates the following dependencies [marker]: <> (Begin:922981e1-18b6-46aa-2468-08dbd53ba9ce) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime - **Subscription**: 922981e1-18b6-46aa-2468-08dbd53ba9ce - **Build**: 20231031.3 - **Date Produced**: October 31, 2023 9:19:19 PM UTC - **Commit**: 5535e31a712343a63f5d7d796cd874e563e5ac14 - **Branch**: refs/heads/internal/release/8.0 [DependencyUpdate]: <> (Begin) - **Updates**: - **Microsoft.Extensions.Caching.Memory**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.Configuration**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.Configuration.Abstractions**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.Configuration.EnvironmentVariables**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.Configuration.Json**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.DependencyInjection**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.DependencyModel**: [from 8.0.0 to 8.0.0][1] - **Microsoft.Extensions.HostFactoryResolver.Sources**: [from 8.0.0-rtm.23530.12 to 8.0.0-rtm.23531.3][1] - **Microsoft.Extensions.Logging**: [from 8.0.0 to 8.0.0][1] - **Microsoft.NETCore.App.Ref**: [from 8.0.0 to 8.0.0][1] - **Microsoft.NETCore.App.Runtime.win-x64**: [from 8.0.0 to 8.0.0][1] - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 8.0.0-rtm.23530.12 to 8.0.0-rtm.23531.3][1] - **System.Text.Json**: [from 8.0.0 to 8.0.0][1] [1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GC0395649aa1&targetVersion=GC5535e31a71&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:922981e1-18b6-46aa-2468-08dbd53ba9ce)

…1101.2 (dotnet#32200) [main] Update dependencies from dotnet/runtime

…1101.9 (dotnet#32211) [main] Update dependencies from dotnet/runtime

…otnet#32196)

Make existing model building conventions more extensible Fixes dotnet#11124 Fixes dotnet#28866

…1103.1 (dotnet#32226) [main] Update dependencies from dotnet/runtime

…dotnet#32214) Fixes dotnet#32208

…converting List.Contains (dotnet#32219) Fixes dotnet#32215 Fixes dotnet#32218

…1103.8 (dotnet#32232) [main] Update dependencies from dotnet/runtime

…1104.5 (dotnet#32236) [main] Update dependencies from dotnet/runtime

…103.1 (dotnet#32240) [main] Update dependencies from dotnet/arcade

…1106.1 (dotnet#32241) [main] Update dependencies from dotnet/runtime

…hnav.yml (dotnet#32082)

We <3 contributors

…net#32251) Fixes dotnet#32179

…1107.1 (dotnet#32247) [main] Update dependencies from dotnet/runtime

…1108.1 (dotnet#32254) [main] Update dependencies from dotnet/runtime

* Update branding to 8.0.1 * Update Versions.props --------- Co-authored-by: Matt Mitchell <mmitche@microsoft.com>

…108.3 (dotnet#32262) [main] Update dependencies from dotnet/arcade

…1109.1 (dotnet#32268) [main] Update dependencies from dotnet/runtime

…dotnet#32214) (dotnet#32265) Fixes dotnet#32208 (cherry picked from commit 338b76a)

…110.1 (dotnet#32281) [main] Update dependencies from dotnet/arcade

…converting List.Contains (dotnet#32219) (dotnet#32266) Fixes dotnet#32215 Fixes dotnet#32218 (cherry picked from commit 08ee676)

…1113.1 (dotnet#32282) [main] Update dependencies from dotnet/runtime

…106.5 (dotnet#32283) [release/8.0] Update dependencies from dotnet/arcade

Before we used to put temporal annotations on temporal tables and all their columns, so that it's easier to process. Problem was that this would generate very noisy migrations when converting from regular table to temporal and vice versa. Every column would have an AlterColumn operation (which we would ignore during processing, but they were nonetheless generated in migration files). Also, we were using relatively simple logic to track state of our temporal tables. Some operations require temporary disabling of the versioning/period, and we need to keep track of that so that we don't try to disable period twice, or forget to enable it later. The way we did it could lead to invalid SQL in some non-trivial scenarios (e.g. converting table to temporal and adding a new column at the same time) The new approach is to only put temporal annotations on the table itself, and the period columns. Regular columns of the temporal table don't have any temporal annotations on them anymore and we reason about temporal information based on other table-based migration operation in the batch and, if need be, on the relational model. We also keep track of the actual temporal information for every operation (rather than keeping global dictionaries of period/version), so that complex migrations, involving multiple operations are more robust. To achieve that we compute the initial (temporal) state of all the tables involved in the migration. We scan all the table operations, and if some info is missing we get it from relational model. Then we do the proper processing of the migration operations - when we encounter table operation, we update the temporal information for that table (since table operations contain relevant temporal annotations). For all other operations we extract the current temporal state for the table involved, and reason based on that info. Fixes dotnet#27459 - SQL Server Migrations: Review temporal table annotations Fixes dotnet#29536 - EF Core IsTemporal() creates huge migration Fixes dotnet#29799 - EF7 SqlServer Migration is trying to update columns on History table before creating the History table if any new columns are added in the same migration

Fixes dotnet#28852 Fixes dotnet#27705 Fixes dotnet#25346

…zation with junk data (dotnet#32253) Co-authored-by: Arthur Vickers <ajcvickers@hotmail.com> Fix to dotnet#32235 - Buffering error in JSON deserialization with junk data Fixes dotnet#32235

…e data logging is on (dotnet#32285) Fixes dotnet#32198

…-merge-7.0-2023-11-14-1021

…-merge-6.0-2023-11-14-1026

…-merge-8.0-2023-11-14-1115

)

….0-2023-11-14-1026 Merging internal commits for release/6.0

….0-2023-11-14-1115 Merging internal commits for release/8.0

….0-2023-11-14-1021 Merging internal commits for release/7.0

Fixes dotnet#29037

…114.4 (dotnet#32309) [release/8.0] Update dependencies from dotnet/arcade

…114.5 (dotnet#32311) [release/7.0] Update dependencies from dotnet/arcade

…sit the Contains item argument (and possibly other non-lambda arguments) (dotnet#32317) This was always a problem but was uncovered by change in how we process Contains. We were going through the full process of nav expansion on the argument (only on the source), which could lead to untranslatable expression tree in some cases. Fixes dotnet#32217 Fixes dotnet#32312

… temporal table causes them to be swapped (dotnet#32328) Problem was that migration model differ was too lax with pairing up columns. Fix is to add more predicates - one that matches annotations+values and one that just matches annotations, ignoring the values, before we fallback to simple column definition. Now that we reworked temporal annotations, this actually gives clean match for the period start and period end column. Moreover, this change could improve matching in other, non-temporal scenarios. Fixes dotnet#29902

Fixes dotnet#32310

Fixes dotnet#32267 The problem here is that ILazyLoader is a transient IDisposable service, which means that the service scope will keep track of instances created in the scope. However, when using context pooling, the service scope is not disposed because it is instead re-used. This means that the scope keeps getting more and more instances added, and never clears them out. The fix is to make the service not IDisposable. Instead, we create instances from our own internal factory where we keep track of the instances created. These can then be disposed and freed when the context is places back in the pool, or when the scope is disposed thus disposing the factory.

…117.1 (dotnet#32356) [main] Update dependencies from dotnet/arcade

…1120.1 (dotnet#32357) [main] Update dependencies from dotnet/runtime

… 8.0.0 (dotnet#32362) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…known FK values (dotnet#32343)

Fixes dotnet#32353

…dotnet#32355) Fixes dotnet#32310

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Part of dotnet#32315

…entity with unknown FK values (dotnet#32368)

…rse failing (dotnet#32370) On some versions of Sql Server, temporal table's history table is by default setup with compression. If that's the case, we need to disable versioning and de-compress the history table before adding a sparse column or converting non-sparse column to sparse. Fixes dotnet#32154

…otnet#31449) (dotnet#32334) Fixes dotnet#31448 (cherry picked from commit d2f824a) Co-authored-by: Gordeev Dmitry <dmitrii.gordeev@redlab.dev>

… Castle interceptor (dotnet#32388)

Fixes dotnet#32392

Fixes dotnet#32375

…122.2 (dotnet#32420) [main] Update dependencies from dotnet/arcade

…1126.6 (dotnet#32421) [main] Update dependencies from dotnet/runtime

Closes dotnet#31552

Closes dotnet#27794 Closes dotnet#31681 Closes dotnet#32332

Closes dotnet#28151

…Contains (dotnet#32433) Fixes dotnet#32432

…ing computed column not generating correct script (dotnet#32398) Working with computed column on a temporal table requires special processing - we need to disable the versioning, add the computed column to regular table and a column with the same name/type/position to the history table, but as a regular column. After all is done we re-enable versioning. Historical information on the computed column will be copied to the counterpart column in history table without issue. One thing that we can't do is modifying computed column SQL when table is temporal. What happens in case of CCSQL modification, we drop the column and create a new one with new CCSQL. This is not an issue for regular table, because the value is computed anyway, so old value is useless. But when we drop-create column, that column gets created at the last position in the table, and so the table no longer matches it's history table exactly (positions of columns may differ). We would have to drop+recreate column on a history table, but that results in losing historical data of that column. And that is valuable data, unlike for regular table. We could enable that scenario once/if we support table rebuilds. Fixes dotnet#27844

…dotnet#32444)

Fixes dotnet#32449

)

Fixes dotnet#32331

…ly (dotnet#32483) Fixes dotnet#32481

…e persisted. (dotnet#32469) Fixes dotnet#32363 Fixes dotnet#32410

… tracked (dotnet#32480)

…ildren (dotnet#32456) Fixes dotnet#32234

…otnet#32501)

…201.1 (dotnet#32508) [main] Update dependencies from dotnet/arcade

…1203.1 (dotnet#32511) [main] Update dependencies from dotnet/runtime

* Work on type mapping inference for string concatenation Fixes dotnet#32325, see also dotnet#32333 * Tweaks, update baselines add more tests and cleanup * Update baselines, add more tests, some cleanup. --------- Co-authored-by: Shay Rojansky <roji@roji.org>

Fixes dotnet#32374

…lternate key property (dotnet#32492) Fixes dotnet#28961 Reverts dotnet#30213 for dotnet#32385 In dotnet#32385, an unconstrained alternate key was added to the model purely to make a non-identifying relationship artificially identifying. dotnet#30213 attempted to fix this by throwing that the key was being modified. However, this scenario is very similar to the case for a many-to-many join type, where the composite primary key is also not the end of any relationship, but forces the two many-to-one relationships to be identifying. I prepared a PR that would only throw if the key involved is alternate, but on reflection that doesn't seem like an appropriate distinction to make. So overall, I think we should just revert this change, which is what this PR does.

* Update Grpc.AspNetCore Needed for Windows ARM64. * Remove Mac build because OS is too old to work with latest GRPC * Adding back MacOS * Disable Grpc tests on Mac Per discussion with James * Try again * Update test/EFCore.AspNet.Specification.Tests/EFCore.AspNet.Specification.Tests.csproj Co-authored-by: Andriy Svyryd <AndriySvyryd@users.noreply.github.com> * Getting there... --------- Co-authored-by: Andriy Svyryd <AndriySvyryd@users.noreply.github.com>

…2522) Fixes dotnet#32390 Since the DbContext is not thread-safe, lazy-loading proxies cannot be used from multiple threads _when loading is happening_. However, it is a common pattern to pass proxies to other parts of the application after the navigations have been loaded. At this time, accesses should be thread-safe. We broke this in 8.

- Allow to specify a migrations assembly using an Assembly type apart from an assemlyName Fixes dotnet#32461

Fix found issues Part of dotnet#32315

Fixes dotnet#32457

* Test new sqlite3mc SQLitePCLRaw bundle * Disable test. --------- Co-authored-by: Brice Lambson <brice@bricelam.net>

…otnet#32569) This is important for Identity

- Moving tests from QueryBugsTests to other more appropriate places (either AssertQuery - enabled or proper AdHoc suites) - Adding a bunch of AdHoc suites (navigations, splitting, filters, weird mappings) - Unified format of AdHoc tests Resolves dotnet#1015

…t type as principal properties (dotnet#32560) * Ensure that, by convention, dependent properties have the same element type as principal properties Fixes dotnet#32411 The issue here is that when a value converter is applied to a principal property, then that converter is used by the dependent properties unless something else is explicitly configured. However, this meant that when the PK has a converter but the FK does not, then the FK can get configured as a primitive collection, since it doesn't have a converter preventing this. The fix is to add a convention that sets the element type for dependent properties to match that for principal properties. * Update based on review

…y set (dotnet#32497) * Don't consider a generated value stable just because it was explicitly set Fixes dotnet#32084 * Updated based on feedback

…el (dotnet#32580)

…t#32581) Fixes dotnet#22921 Note that the reports here seem to be caused by incorrect use by the same connection concurrently. This is invalid. However, made the code a bit more robust here anyway.

…207.2 (dotnet#32585) [main] Update dependencies from dotnet/arcade

…1211.1 (dotnet#32586) [main] Update dependencies from dotnet/runtime

…hen not starting on one. (dotnet#32573) Additionally, detect multiple relationship chains that end with incompatible conversions. Fixes dotnet#32422

…n types (dotnet#32577) And allow non-public parameterless constructors. Fixes dotnet#24748 Fixes dotnet#19691

* Validate scaffolding migration file names Fixes dotnet#24024 * Use TempDirectory class * Skip negative cases on non-Windows. * Exclude more tests from non-Windows platforms

…tor. (dotnet#32593) Don't allocate Queue unless necessary. Fix an issue with configuration of an FK to the base type. Part of dotnet#32422

…32599) Fixes dotnet#24175 See https://learn.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-rename-transact-sql?view=sql-server-ver16

…otnet#32600) Fixes dotnet#32430

…32606) This has been broken form 6 onwards. It's possible the tools will revert their break, but there doesn't seem much value in keeping -d at this point. -m stands for "mapping attributes" ¯\_(``)_/¯ Fixes dotnet#26687

Fixes dotnet#25797 Fixes dotnet#26016 I identified two race conditions, both caused by splitting state across multiple data structures. In particular, the Semaphore and the two ConcurrentStacks must stay in sync--that is, the Semaphore can let someone get a collection if and only if there is a connection available in the one of the stacks. The fix is to wrap all these things in a single lock. It's possible that we don't need a full lock, but we already have one to protect _collections which can easily be expanded to cover the right areas. Once this lock is used, the semaphore is no longer needed, and the stacks don't need to be concurrent because they are protected by the lock.

… config (dotnet#32597) Fixes dotnet#25278 Fixes dotnet#19814 Fixes dotnet#27527

…et#32613) * Microsoft.Data.Sqlite: Check error code when binding parameters Fixes dotnet#27597 * Use reflection to call into PCLraw * Call into PCLraw directly.

…verter (dotnet#32619) Fixes dotnet#32552

…net#32620) Ensure that configuring connection details again overrides previous configuration.

…in table (dotnet#32627) Fixes dotnet#28905

…1217.5 (dotnet#32635) [main] Update dependencies from dotnet/runtime

… to reference it. Instead, remove it and reattach the configuration. (dotnet#32640) Also, reuse the FKs that already were configured instead of creating new ones. Fixes dotnet#27990 Fixes dotnet#26555

…ved types (dotnet#32628)

…when casing differs (dotnet#32629) Fixes dotnet#30237

… will then be used for scaffolding (dotnet#32631) Covers dotnet#32571

Fixes dotnet#31121

…cted columns (dotnet#32648) Fixes dotnet#29744 Fixes dotnet#30765

…otnet#32506) Also fixing exception ordering issue. Fixes dotnet#32505

…1224.2 (dotnet#32670) [main] Update dependencies from dotnet/runtime

Closes dotnet#31083 Fixes dotnet#31407

Instead of on a private list on SelectExpression. Part of dotnet#31049

Closes dotnet#32668

Fixes dotnet#30982 Fixes dotnet#32664

…r only because hardcoded column types etc can be moved from provider to relational/core (dotnet#32706) Also removed some tests from InMemory QBT - those tests were duplicated from SqlServer QBT but have been moved to AdHoc test suites and run for all providers.

…slator.cs Co-authored-by: Shay Rojansky <roji@roji.org>

Co-authored-by: Shay Rojansky <roji@roji.org>

…/joelmandell/efcore into feature/translate_json_functions

Feature/translate json functions #29306 #30010

Are you sure you want to change the base?

Feature/translate json functions #29306 #30010

Commits on Oct 12, 2023

Commits on Oct 13, 2023

Commits on Oct 14, 2023

Commits on Oct 15, 2023

Commits on Oct 16, 2023

Commits on Oct 17, 2023

Commits on Oct 18, 2023

Commits on Oct 19, 2023

Commits on Oct 20, 2023

Commits on Oct 21, 2023

Commits on Oct 22, 2023

Commits on Oct 23, 2023

Commits on Oct 24, 2023

Commits on Oct 25, 2023

Commits on Oct 26, 2023

Commits on Oct 27, 2023

Commits on Oct 28, 2023

Commits on Oct 29, 2023

Commits on Oct 30, 2023

Commits on Oct 31, 2023

Commits on Nov 1, 2023

Commits on Nov 2, 2023

Commits on Nov 3, 2023

Commits on Nov 4, 2023

Commits on Nov 5, 2023

Commits on Nov 6, 2023

Commits on Nov 8, 2023

Commits on Nov 9, 2023

Commits on Nov 13, 2023

Commits on Nov 14, 2023

Commits on Nov 15, 2023

Commits on Nov 17, 2023

Commits on Nov 20, 2023

Commits on Nov 21, 2023

Commits on Nov 22, 2023

Commits on Nov 23, 2023

Commits on Nov 27, 2023

Commits on Nov 28, 2023

Commits on Nov 29, 2023

Commits on Nov 30, 2023

Commits on Dec 1, 2023

Commits on Dec 2, 2023

Commits on Dec 3, 2023

Commits on Dec 4, 2023

Commits on Dec 5, 2023

Commits on Dec 7, 2023

Commits on Dec 8, 2023

Commits on Dec 9, 2023

Commits on Dec 10, 2023

Commits on Dec 11, 2023

Commits on Dec 12, 2023

Commits on Dec 13, 2023

Commits on Dec 14, 2023

Commits on Dec 15, 2023

Commits on Dec 16, 2023

Commits on Dec 18, 2023

Commits on Dec 19, 2023

Commits on Dec 20, 2023

Commits on Dec 23, 2023

Commits on Dec 25, 2023

Commits on Dec 29, 2023

Commits on Dec 30, 2023

Commits on Jan 2, 2024

Commits on Jan 3, 2024