fix(angular-query-devtools) non optional devtools property in devtool…

Moved things around in order to remove optionality and unnecessary optional chaining.
Devtools testes, example is working.

That's odd, 30 tests failing in the Nx Cloud build all relate to solid query. @arnoud-dv do you get similar errors?

Just to make sure I didn't introduce any regression I ran npm run test:ci on feature/angular-query without above changes and I get this:

 >  NX   Ran targets test:format, test:eslint, test:lib, test:types, test:build, test:bundle, build for 33 projects (19s)

    ✔    107/114 succeeded [103 read from cache]

    ✖    7/114 targets failed, including the following:
         - nx run @tanstack/angular-query-experimental:test:types
         - nx run @tanstack/svelte-query-devtools:test:types
         - nx run @tanstack/angular-query-devtools-experimental:test:lib
         - nx run @tanstack/angular-query-experimental:test:eslint
         - nx run angular-vite:test:bundle
         ...and 2 more...

When it comes to tests, I hope npm/pnpm doesn't make a difference...
Anyway, I'm curious @arnaud-dv if you tried to run those when trying to merge into tanstack repo.

Triage

@tanstack/angular-query-devtools-experimental:"test:lib" - it's basically missing test files.
@tanstack/angular-query-experimental:"test:types" - (single?) compilation error, Type 'void' is not assignable to type 'Promise<unknown>'.
nx run @tanstack/angular-query-experimental:"test:eslint" - linter: 5 problems (5 errors, 0 warnings) / 4 errors and 0 warnings potentially fixable with the --fix option.
nx run angular-vite:"test:bundle" - [vite]: Rollup failed to resolve import "rxjs" from<EMAIL_ADDRESS>/ This is most likely unintended because it can break your application at runtime. - this looks rather important 🔥

arnoud-dv I can take care of first 3 straight ahead, if you haven't done that locally

@tanstack/angular-query-devtools-experimental:"test:lib"
> nx run @tanstack/angular-query-devtools-experimental:"test:lib"

><EMAIL_ADDRESS>test:lib /Users/tomaszducin/Development/contrib/query/packages/angular-query-devtools-experimental
> vitest run --coverage
 RUN  v0.34.6 /Users/tomaszducin/Development/contrib/query/packages/angular-query-devtools-experimental
      Coverage enabled with istanbul
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |       0 |
----------|---------|----------|---------|---------|-------------------
include: **/*.{test,spec}.?(c|m)[jt]s?(x)
exclude:  **/node_modules/**, **/dist/**, **/cypress/**, **/.{idea,git,cache,output,temp}/**, **/{karma,rollup,webpack,vite,vitest,jest,ava,babel,nyc,cypress,tsup,build}.config.*
watch exclude:  **/node_modules/**, **/dist/**

No test files found, exiting with code 1
 ELIFECYCLE  Command failed with exit code 1.

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test:lib for project @tanstack/angular-query-devtools-experimental and 3 task(s) they depend on (7s)

    ✖    1/4 failed
    ✔    3/4 succeeded [2 read from cache]

   View structured, searchable error logs at https://nx.app/runs/z2FDmYZ6zA

@tanstack/angular-query-experimental:"test:types"
> nx run @tanstack/angular-query-experimental:"test:types"

><EMAIL_ADDRESS>test:types /Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental
> tsc

src/tests/injectMutation.test.ts(40,9): error TS2322: Type '() => void' is not assignable to type 'MutationFunction<unknown, void>'.
  Type 'void' is not assignable to type 'Promise<unknown>'.
src/tests/injectMutation.test.ts(46,23): error TS2345: Argument of type '{ par1: string; }' is not assignable to parameter of type 'void'.
 ELIFECYCLE  Command failed with exit code 2.

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test:types for project @tanstack/angular-query-experimental and 1 task(s) they depend on (2s)

    ✖    1/2 failed
    ✔    1/2 succeeded [1 read from cache]

   View structured, searchable error logs at https://nx.app/runs/RuOyF5BKvy

@tanstack/angular-query-experimental:"test:eslint"
> nx run @tanstack/angular-query-experimental:"test:eslint"

><EMAIL_ADDRESS>test:eslint /Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental
> eslint --ext .ts,.tsx ./src
DeprecationWarning: 'originalKeywordKind' has been deprecated since v5.0.0 and will no longer be usable after v5.2.0. Use 'identifierToKeywordKind(identifier)' instead.

/Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental/src/injectQueryClient.ts
  2:1  error  `ngxtension/create-injection-token` import should occur before type import of `@tanstack/query-core`  import/order

/Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental/src/query-proxy.ts
   1:20  error  Member 'Signal' of the import declaration should be sorted alphabetically   sort-imports
   3:1   error  All imports in the declaration are only used as types. Use `import type`    @typescript-eslint/consistent-type-imports
   3:1   error  `./types` import should occur before type import of `@tanstack/query-core`  import/order
  19:11  error  Unnecessary conditional, value is always truthy                             @typescript-eslint/no-unnecessary-condition

✖ 5 problems (5 errors, 0 warnings)
  4 errors and 0 warnings potentially fixable with the `--fix` option.

 ELIFECYCLE  Command failed with exit code 1.

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test:eslint for project @tanstack/angular-query-experimental and 1 task(s) they depend on (4s)

    ✖    1/2 failed
    ✔    1/2 succeeded [1 read from cache]

   View structured, searchable error logs at https://nx.app/runs/sGVhzi99Jp

@tanstack/angular-query-experimental:"test:eslint"
> nx run @tanstack/angular-query-experimental:"test:eslint"

><EMAIL_ADDRESS>test:eslint /Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental
> eslint --ext .ts,.tsx ./src
DeprecationWarning: 'originalKeywordKind' has been deprecated since v5.0.0 and will no longer be usable after v5.2.0. Use 'identifierToKeywordKind(identifier)' instead.

/Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental/src/injectQueryClient.ts
  2:1  error  `ngxtension/create-injection-token` import should occur before type import of `@tanstack/query-core`  import/order

/Users/tomaszducin/Development/contrib/query/packages/angular-query-experimental/src/query-proxy.ts
   1:20  error  Member 'Signal' of the import declaration should be sorted alphabetically   sort-imports
   3:1   error  All imports in the declaration are only used as types. Use `import type`    @typescript-eslint/consistent-type-imports
   3:1   error  `./types` import should occur before type import of `@tanstack/query-core`  import/order
  19:11  error  Unnecessary conditional, value is always truthy                             @typescript-eslint/no-unnecessary-condition

✖ 5 problems (5 errors, 0 warnings)
  4 errors and 0 warnings potentially fixable with the `--fix` option.

 ELIFECYCLE  Command failed with exit code 1.

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test:eslint for project @tanstack/angular-query-experimental and 1 task(s) they depend on (4s)

    ✖    1/2 failed
    ✔    1/2 succeeded [1 read from cache]

   View structured, searchable error logs at https://nx.app/runs/sGVhzi99Jp

angular-vite:test:bundle
Mac-Mini-Tomaszku~/Development/contrib/query[feature/angular-query|⚑1] % nx run angular-vite:test:bundle

   ✔    4/4 dependent project tasks succeeded [1 read from cache]

   Hint: you can run the command with --verbose to see the full dependent project outputs

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

> nx run angular-vite:"test:bundle"

> angular-vite@ test:bundle /Users/tomaszducin/Development/contrib/query/integrations/angular-vite
> vite build
vite v4.5.0 building for production...
transforming...
✓ 14 modules transformed.
✓ built in 858ms
[vite]: Rollup failed to resolve import "rxjs" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "rxjs" from<EMAIL_ADDRESS>This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at viteWarn (file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/vite@4.5.0_@types+node@18.18.0_less@4.2.0_sass@1.69.5_terser@5.24.0/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:48216:27)
    at onRollupWarning (file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/vite@4.5.0_@types+node@18.18.0_less@4.2.0_sass@1.69.5_terser@5.24.0/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:48248:9)
    at onwarn (file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/vite@4.5.0_@types+node@18.18.0_less@4.2.0_sass@1.69.5_terser@5.24.0/node_modules/vite/dist/node/chunks/dep-bb8a8339.js:47976:13)
    at file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:24276:13
    at Object.logger [as onLog] (file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:25950:9)
    at ModuleLoader.handleInvalidResolvedId (file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:24862:26)
    at file:///Users/tomaszducin/Development/contrib/query/node_modules/.pnpm/rollup@3.29.4/node_modules/rollup/dist/es/shared/node-entry.js:24822:26
 ELIFECYCLE  Command failed with exit code 1.

 —————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Ran target test:bundle for project angular-vite and 4 task(s) they depend on (11s)

    ✖    1/5 failed
    ✔    4/5 succeeded [1 read from cache]

   View structured, searchable error logs at https://nx.app/runs/8BF5ipPUcV

Pushed some eslint and other small fixes. Also downgraded vitest, Solid tests don't succeed on newer vitest.

Rebased to your update. I'll take care of prettier.
But now we've got a svelte fail. Is there a possibility to merge it to feature/angular-query and take care of other things there @arnoud-dv as they're unrelated to this PR?
I guess if you're directly pushing to the feature/angular-query branch without CI checks (npm run test:ci) the code doesn't go through all the checks... at least it looks like this.

Aligned some versions, updated Vite to 4.5.0 as vite-plugin-solid depends on 4.5.0 and Svelte was using types from both 4.5.0 and 4.4.11, giving the error there. Also removed the Angular Vite application in /integrations as I don't want another Vite version appearing from a plugin. Solid tests are failing inconsistently. Sometimes when re-running after failure they'll succeed. It looks like actual timers are used, not mocked.

@arnoud-dv finally passing 😍! could you take a look?


Merge changes of database model  of the last few weeks

why not just making the build work for JDKs > 9?


bug: Panic when selecting from non-materialized source

Describe the bug
With rust frontend, select from non-materialized source cause frontend node to crash.
To Reproduce
patrick=> CREATE SOURCE kafka1 (v1 int, v2 varchar) with ('connector'='kafka', 'kafka.topic'='kafka_1_partition_mv_topic', 'kafka.broker'='<IP_ADDRESS>:29092', 'kafka.scan.startup.mode'='earliest', 'kafka.consumer.group'='kafka1-c1') ROW FORMAT JSON;
CREATE_SOURCE

patrick=> SELECT * FROM kafka1;
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

Expected behavior
Return an error instead of panic
Additional context
frontend log:
thread 'tokio-runtime-worker' panicked at 'there is no batch source operator', src/frontend/src/optimizer/plan_node/logical_source.rs:94:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/f4a7ce997a1d7546d2b737f8b87d36907bcea2ad/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/f4a7ce997a1d7546d2b737f8b87d36907bcea2ad/library/core/src/panicking.rs:142:14
   2: <risingwave_frontend::optimizer::plan_node::logical_source::LogicalSource as risingwave_frontend::optimizer::plan_node::convert::ToBatch>::to_batch
             at ./src/frontend/src/optimizer/plan_node/logical_source.rs:94:9
   3: <risingwave_frontend::optimizer::plan_node::logical_project::LogicalProject as risingwave_frontend::optimizer::plan_node::convert::ToBatch>::to_batch
             at ./src/frontend/src/optimizer/plan_node/logical_project.rs:272:25
   4: risingwave_frontend::optimizer::plan_node::convert::ToBatch::to_batch_with_order_required
             at ./src/frontend/src/optimizer/plan_node/convert.rs:66:19
   5: risingwave_frontend::optimizer::PlanRoot::gen_batch_query_plan
             at ./src/frontend/src/optimizer/mod.rs:149:16
   6: risingwave_frontend::handler::query_single::handle_query_single::{{closure}}
             at ./src/frontend/src/handler/query_single.rs:41:20
   7: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/f4a7ce997a1d7546d2b737f8b87d36907bcea2ad/library/core/src/future/mod.rs:91:19
   8: risingwave_frontend::handler::handle::{{closure}}
             at ./src/frontend/src/handler/mod.rs:79:65
   9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/f4a7ce997a1d7546d2b737f8b87d36907bcea2ad/library/core/src/future/mod.rs:91:19
  10: <risingwave_frontend::session::SessionImpl as pgwire::pg_server::Session>::run_statement::{{closure}}
             at ./src/frontend/src/session.rs:382:37

We don't support select from source for now. We should create materialized source.

We don't support select from source for now. We should create materialized source.

Right. But we should return an error instead of panic.

I want to try this issue and new to rust. The panic is thrown in to_batch(&self) -> PlanRef in logical_source.rs, but the return value of this method is Rc, how can we return an error?

I want to try this issue and new to rust. The panic is thrown in to_batch(&self) -> PlanRef in logical_source.rs, but the return value of this method is Rc, how can we return an error?

I think the correct way to resolve this is to deny such statement in binder, rather in planner.

I want to try this issue and new to rust. The panic is thrown in to_batch(&self) -> PlanRef in logical_source.rs, but the return value of this method is Rc, how can we return an error?

I think the correct way to resolve this is to deny such statement in binder, rather in planner.

Do you mean we should check whether the source of the Query can be batched in bind_query?

Yes.

This bug has been fixed.


Mat.T() and Mat * operator errors

Summary of your issue
Either I am doing something wrong or the .T() transpose method for Mat is not working correctly.
I tried to transpose a 3x1 Mat to a 1x3 Mat and received garbage instead.
A similar effect was observed when using the * multiplication operator.
Environment
C# Visual Studio 2019, OpenCvSharp<IP_ADDRESS>.20191110
What did you do when you faced the problem?
            Mat mat = new Mat(3, 1, MatType.CV_32F);
            mat.Set<float>(0, 1.0f);
            mat.Set<float>(1, 2.0f);
            mat.Set<float>(2, 3.0f);

            Mat trans = mat.T().Clone();
            Console.WriteLine($"{trans.Get<float>(0)},  {trans.Get<float>(1)} ,{trans.Get<float>(2)}");

Output:
1 , 0 , 0

Expected
1, 2 , 3

Hi @claudeHasler . I think you misunderstood the Get-method. The integer parameter represents "the index along the 0 dimension" which means the rows. After transposing the matrix the 0 dimension just has an entry at the first position, leading to the result you pasted.
Use an array instead to get the full 2D output:
float[,] testmatout = new float[mat.Height, mat.Width];
mat.GetArray(0, 0, testmatout);
If you have that full information, you should also be able to use the multiplication operator correctly.
Give it a try


Document Usage and Configuration

See Usage documentation in original plugin repo.
Currently configuration only partially shown in the example of build.gradle.

Thanks, I'll update this repo as soon as possible

@AlexTrotsenko I updated the documentation in #74
Please, review it and any further help is welcome


build pkged.go directly from make target

Changes

:bug:  Fixes bash error running make on a stock OS X

By removing the unnecessary script intermediary for packaging ./templates as pkged.go, and instead relying on only
Go code run directly from make, the incompatibility with the old bash which ships with OSX is bypassed.
/kind bug
Fixes #834  (...probably)

/lgtm


Container support for Windows 10 IoT Enterprise LTSC 2021

Is your feature request related to a problem? Please describe.
We need base container images  for Windows 10 IoT Enterprise LTSC 2021 !
Currently we use 20H2 where we still can develop windows containers , this is ticking bomb which will hit our company (>1000 developers).
We cannot jump to Windows 11 and we cannot upgrade the systems with Windows Server licenses due to higher costs.
We need images for 21H2, the strategy described in:
https://techcommunity.microsoft.com/t5/containers/windows-server-2022-and-beyond-for-containers/ba-p/2712487
is a huge problem for us. In my eyes that's a breaking behavior, it was always stated from Microsoft side that it is allowed not only to develop and test container workloads on Windows 10 IoT, actually also production workloads are supported on Windows 10 IoT.
Hyper-V isolation is not an solution, it's extremely slow and is not supported for example by containerd.
Describe the solution you'd like
Base Images which allow process isolation on 21H2 for Windows 10 IoT Enterprise LTSC 2021,
basically the ability to host .NET Framework services as well as windows apps in containers.
Describe alternatives you've considered
Moving all our services from Windows containers to Linux containers.
This is a very costly operation since we have millions of line of code to adapt and rewrite.
Additional context
Medical Industry Systems available at customer site

Hey @SyngoPredevelopment thank you for writing to us. Can you clarify what is the issue with 21H2?

The problem is that in Windows 10 21H2, 21H1 you don't have base images for windows containers whic supports process isolation.
Also here it is stated:
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility?tabs=windows-server-2022%2Cwindows-10-21H1
that the images don't support process isolation. For mcr.microsoft.com/windows/servercore images you don't have base images for 21H2 for example, you jumped directly to Windows 11. We have a major problem in that, we cannot use Windows 21H2 at all in that case.

To be more concrete, we need to run containers with dotnet framework apps in process isolation on Windows 21H2, the LTSC version for windows 10 does not support process isolation for OS build 19044.1826 which is the latest Win 10 LTSC version. The are no base images for mcr.microsoft.com/dotnet/framework/runtime:4.8 (which is actually based on the server core images, there 21H2 where omitted) which can give us the needed functionality. This is very much needed in our case !

Many thanks

Wanted to let you know that we're still looking into this but I don't have an update to share at the moment.

We have found an workaround how to use the Windows 10 20H2 containers also on 21H2 and 22H2.

We have found an workaround how to use the Windows 10 20H2 containers also on 21H2 and 22H2.

Can you please share the workaround with the community


Jenkins is not building plugin with plugin.yml or config.yml.

Missing resource folder to include files in compile?

Hmmm I see that, I think I know what's going on......

Ok fixed it. For some reason I believe @gvlfm78 moved the plugin.yml and config.yml out of the resources folder. I put them back, you can get the fixed version here:
https://jenkins-bukkitocm.rhcloud.com/job/OldCombatMechanics/19/


Frontend work- install nextui

we've got the start of a frontend up!

merging so I can push up a preview for everyone to see


Running heapster-controller gives error : invalid character '%' looking for beginning of object key string. Why?

Running heapster-controller gives error :
"invalid character '%' looking for beginning of object key string". Why?

what was the cause of this??


Development: Refactor course score CSV export

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[x] I documented the TypeScript code using JSDoc style.

Motivation and Context
The course scores component had huge methods and was not very understandable.
Description
Splits up the large methods into smaller ones where it makes sense to make the code more readable. Also reduces duplication by extracting some common functionality when putting values into the rows into their own class.
Steps for Testing
Prerequisites:

1 Instructor
Some course with a few exercises and some student submissions.

Export and download the course scores CSV file (reachable via the Course Management → turquoise ‘Scores’ button) before deploying this PR to a test server.
After deployment, download the CSV file again for the same course. It should be identical (or no longer be broken as for example for Georg Willer’s test course on TS1).

Review Progress
Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

File
Branch
Statement

course-scores.component.ts
94.2%
73.6%

course-scores-csv-row-builder.ts
100%
100%

Screenshots
n/a

I've got a line containing "undefined" in my export. Is that somehow expected or normal?

I've got a line containing "undefined" in my export. Is that somehow expected or normal?

Thanks, that was a bug that should now be fixed with 2830744.

@willergeorg @dveljacic Thanks for testing!
The component determined the exercises which should be included before some additional data was fetched from the server. Therefore, depending on how quick the server responded they were indeed missing from the output. This has now been fixed in c0a01c1.

I think now you are including every single exercise as well.

@willergeorg That is the intended behaviour. It works like that on our production system as well. There is a column for each exercise, and then for each exercise type there are two columns (points, score) with some aggregated data.

@Strohgelaender @VinnavanSembian @mallgaier @lBruchmann Good catch!
In commit 608c8fb4cd0678453dc3cc82a4e51787ea97acc0 I switched to the correct rounding function and improved the tests to test the changed value.
In commit a09f05a0396315ebafbf57f92196276f89684da2 I then renamed the rounding utility function to a name that actually reflects how it should be used to make it less likely to use the wrong one in the future.


Handle dvc init when git repository is not initialized

When running dvc init before git init, the following error is shown:
Unexpected error: 'Base' object has no attribute 'GITIGNORE'
The .dvc folder is created but no .gitignore file is added. Running dvc init again fails.
I guess best solution would be to exit without creating any files when the git repository is not initialized?

Hi @prihoda !
dvc actually supposed to run even without git. The only difference for dvc init would be that it would not create .gitignore and will not add the changes to git. Other than that, dvc should be operational even without git. I think that we should add --bare or --no-scm option for dvc init so that we can be sure that user actually wants to initiate dvc repo in a plain directory. Created #662 for that.
The error you are experiencing here is definitely a bug. Will prepare a patch ASAP.
Thank you for the feedback!


Fixed possible resource leak

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #287 into dev will decrease coverage by 0.15%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##                dev    #287      +/-   ##
===========================================
- Coverage     37.36%   37.2%   -0.16%
+ Complexity     1671    1666       -5
===========================================
  Files           103     103
  Lines         23671   23673       +2
  Branches       3882    3882
===========================================
- Hits           8844    8808      -36
- Misses        13234   13272      +38
  Partials       1593    1593

Flag
Coverage Δ
Complexity Δ

#JDBC41
37.08% <0%> (-0.08%)
1659 <0> (-5)

#JDBC42
37.07% <0%> (-0.18%)
1658 <0> (-6)

Impacted Files
Coverage Δ
Complexity Δ

...com/microsoft/sqlserver/jdbc/dns/DNSUtilities.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
41.57% <0%> (-3.38%)
14% <0%> (-2%)

src/main/java/microsoft/sql/DateTimeOffset.java
37.14% <0%> (-2.86%)
8% <0%> (-2%)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
45.94% <0%> (-0.92%)
0% <0%> (ø)

...c/main/java/com/microsoft/sqlserver/jdbc/Util.java
45.15% <0%> (-0.71%)
60% <0%> (-1%)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
29.68% <0%> (-0.45%)
56% <0%> (-1%)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
49.11% <0%> (+0.07%)
213% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c706d55...8cebdd4. Read the comment docs.

Thanks for the fix @pierresouchay and quick response!


Sometimes occures 'invalid_grant' error

Hi, I 'am 'qkrgksqkr'
I implementing OIDC protocol by using this package.
It's very nice and good,
but, somtimes I have a error message 'invalid_grant' error message, while processing 'authrozation_code" flow,
Not always, just sometimes,
Detail step is like below.
step 1. Client did /authoize,, and redirect with 'authroizatio_code'
step 2  Client request /token with 'authorization_code'
If success, Client get access/ refresh / id token,
but sometimes Client get 'invalid_grant'
so, I retry step 2, with same 'authorization_code' then, it is always success
I can't understand why this is success.
In real system, the moment between step1 and step2 is very short. no extra time.
So I test with your sampe code. and added log message

I'll try postman runner..
Your sample code with mongo deafult option, localhost:27017 , stand alone
There are no error,
but mongo db is replaset (primary - second -second), similiar to my system
It occures error sometimes
So, the difference is mongo DB environment,  standAlone and ReplicaSet.
Is is some additional config element that I need to set to use this package?..
I want to solve this problem.
thank you.

My mongodb is replicast structure
So, I think it is beacuse 'write concern'?..

I did some test
I set this options, SetReadPreference / SetWriteConcern /SetReadConcern
Some cases, threr is no 'invalid_grant' error
would you added feautre these 3 options??

I have some addtinal question.
Why this value is "SecondaryPreferred()" ??
The default is Primary

Hello!
Thank you for your wonderful debugging! That's fantastic!
Yes, we've seen this error crop up as well and I was wondering if it was down to replication lag since the redirects are very quick, just never had the capacity to investigate.
The main reason we go with secondary preferred is to try to distribute as many reads away from the primary. As soon as a write is needed to be performed the mongo driver should perform the write and any subsequent queries on the primary.
If you remove the read preference and remove the write concern does it also solve the issue? (Read preference: primary)
Personally, I've been pretty unwell this week, so I won't be able to jump on a machine for a week, but can respond as needed to questions via my phone/GH app

I tested 3 case, I try 20 times below url using 'postam runner', and count error case.
-> [POST] http://localhost:3846/oauth2/auth?client_id=my-client&redirect_uri=http%3A%2F%2Flocalhost%3A3846%2Fcallback&response_type=code&scope=photos+openid+offline+email&state=some-random-state-foobar&nonce=some-random-nonce
-> This url execute /authorize and /token in a row from example source
a) ReadPrefrenece - secondary ( default)
error count / total count
5/20
3/20
0/20
8/20
0/20
3/20
2/20
5/20
2/20
5/20
b) ReadPrefrenece - primary
error count / total count
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
c) ReadPrefrenece - secondary and WriteConcern(Wmajority())
error count / total count
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
0/20
teso case b)  and case c) , no error.

I need to solve this problem,
so I add some feature in your source temparory
I hope you will be well!
thanky for your reply

Sorry about the delay on this, version v0.31.0 has been released with the fix!
Thank you! :+1:


Shift is not displayed in capital letters unlike all other keys like CTRL and ESC

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the Staging dot on Chrome
Press CTRL + I to open up the dialog box
See that the shift is not displayed in caps unlike other keys like CTRL and ESC

Expected Result:
Shift should also be displayed in caps like other keys
Actual Result:
Shift is not displayed in caps
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.86-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1678948248802089
View all open jobs on GitHub

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

https://expensify.slack.com/archives/C01SKUP7QR0/p1679012932980229?thread_ts=1678993219.761179&cid=C01SKUP7QR0

We're going to keep this as is


switches with no break?

Dear MELA developers,
While checking compilation warnings, I noticed this switch() where some of the case do not include a break:
https://github.com/JHUGen/JHUGenMELA/blob/master/MELA/src/MELANCSplineCore.cc#L94-L101
Is this really intended?
The effect here is that eg if bcBegin==bcApproximatedSecondDerivative then both the case bcApproximatedSecondDerivative and the following one case bcApproximatedSlope are executed, which loosk suspect.
Same for case bcClamped and case bcQuadratic (both will be executed if  bcBegin==bcClamped).
HTH,
N.

@namapane:
The behavior is intended: bcval is initialized to 0, so cases bcNaturalSpline and bcClamped use this initial condition. Cases bcApproximatedSecondDerivative and bcApproximatedSlope differ from bcNaturalSpline and bcClamped, respectively, with only a change in the value of bcval in the formula. You might get verbose warnings depending on compiler flags, but it should be harmless. Nevertheless, if you tell me the warnings, those could be investigated.
I also see a bug on L139. The left-hand side should be ecval, not bcval. I will fix that with a PR at the same time I investigate the warnings if you mention them.

Thanks @usarica for the quick reply. The warning is the one documented here:
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wimplicit-fallthrough
essentially, it warns aboout all case statements with no break , as these are often unintended.
As documented in the link above, when the behaviour is intended It is possible to suppress the warning in gcc adding a statement:
__attribute__ ((fallthrough));
which has also the side effect of making it apparent to the reader of the code.
BTW in case you make a bugfix PR, may I suggest to also add new architectures/compilers in setup.sh?
In the 12X series the default arch is el8_amd64_gcc10, while for 13X it is el8_amd64_gcc11. In these cases the script sets  slc7_amd64_gcc920 as arch, which is probably still fine, but you may consider updating it nevertheless.
BTW SLC7 will arrive at end-of-life mid next year.

I am not sure whether the issue is still being considered - in case it is still ongoing, @namapane would you please let us know? Otherwise, I will close this issue.

As far as I can tell, the code would still produce a warning. My suggestion is still to follow the gcc prescription adding:
__attribute__ ((fallthrough));
which suppresses the warning, and also makes it clear to the casual reader that the lack of "break" is intended.
I can make a PR for that, if you wish.


When will the _layers directory be deleted ?

Detail
I will push the image first.
# docker push reg.domain.com/library/alpine
The push refers to a repository [reg.domain.com/library/alpine]
5bef08742407: Layer already exists
latest: digest: sha256:1072e499f3f655a032e88542330cf75b02e7bdf673278f701d7ba61629ee3ebe size: 528

And if you check inside the harbor there are tags and _layers.
root@devreghar001:~/harbor# du -k -x /data/registry/docker/registry/v2/repositories/library/alpine
2       /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags/latest/current
2       /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags/latest/index/sha256/1072e499f3f655a032e88542330cf75b02e7bdf673278f701d7ba61629ee3ebe
11      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags/latest/index/sha256
12      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags/latest/index
14      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags/latest
14      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags
2       /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions/sha256/1072e499f3f655a032e88542330cf75b02e7bdf673278f701d7ba61629ee3ebe
11      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions/sha256
12      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions
26      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests
1       /data/registry/docker/registry/v2/repositories/library/alpine/_uploads
2       /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256/88286f41530e93dffd4b964e1db22ce4939fffa4a4c665dab8591fbab03d4926
2       /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256/7328f6f8b41890597575cbaadc884e7386ae0acc53b747401ebce5cf0d624560
13      /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256
13      /data/registry/docker/registry/v2/repositories/library/alpine/_layers
40      /data/registry/docker/registry/v2/repositories/library/alpine

Next I deleted tags and repositories pushed from the UI.
When you check the harbor again, the _layer directory is left.
The tags directory has been deleted.
# du -k -x /data/registry/docker/registry/v2/repositories/library/alpine
1       /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/tags
1       /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions/sha256/1072e499f3f655a032e88542330cf75b02e7bdf673278f701d7ba61629ee3ebe
10      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions/sha256
11      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests/revisions
12      /data/registry/docker/registry/v2/repositories/library/alpine/_manifests
1       /data/registry/docker/registry/v2/repositories/library/alpine/_uploads
2       /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4
2       /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256/88286f41530e93dffd4b964e1db22ce4939fffa4a4c665dab8591fbab03d4926
2       /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256/7328f6f8b41890597575cbaadc884e7386ae0acc53b747401ebce5cf0d624560
14      /data/registry/docker/registry/v2/repositories/library/alpine/_layers/sha256
15      /data/registry/docker/registry/v2/repositories/library/alpine/_layers
27      /data/registry/docker/registry/v2/repositories/library/alpine

I have questions.

Will not delete the _layers directory ?
If the _layers directory is deleted, when will it be deleted ?

If the _layers directory will remain forever, I think that you will waste storage space.
Thanks.
Versions

Docker version 17.03.0-ce, build 60ccb22

harbor.cfg
## Configuration file of Harbor

#The IP address or hostname to access admin UI and registry service.
#DO NOT use localhost or <IP_ADDRESS>, because Harbor needs to be accessed by external clients.
hostname = reg.domain.com

#The protocol for accessing the UI and token/notification service, by default it is http.
#It can be set to https if ssl is enabled on nginx.
ui_url_protocol = https

#The password for the root user of mysql db, change this before any production use.
db_password = root123

#Maximum number of job workers in job service
max_job_workers = 3

#Determine whether or not to generate certificate for the registry's token.
#If the value is on, the prepare script creates new root cert and private key
#for generating token to access the registry. If the value is off the default key/cert will be used.
#This flag also controls the creation of the notary signer's cert.
customize_crt = on

#The path of cert and key files for nginx, they are applied only the protocol is set to https
ssl_cert = /root/harbor/certs/reg.domain.com_2017.crt.pem
ssl_cert_key = /root/harbor/certs/reg.domain.com_2017.key.pem.signed

#The path of secretkey storage
secretkey_path = /data

#Admiral's url, comment this attribute, or set its value to NA when Harbor is standalone
admiral_url = NA

#NOTES: The properties between BEGIN INITIAL PROPERTIES and END INITIAL PROPERTIES
#only take effect in the first boot, the subsequent changes of these properties
#should be performed on web ui

#************************BEGIN INITIAL PROPERTIES************************

#Email account settings for sending out password resetting emails.

#Email server uses the given username and password to authenticate on TLS connections to host and act as identity.
#Identity left blank to act as username.
email_identity =

email_server = smtp.mydomain.com
email_server_port = 25
email_username =<EMAIL_ADDRESS>email_password = abc
email_from = admin<EMAIL_ADDRESS>email_ssl = false

##The initial password of Harbor admin, only works for the first time when Harbor starts.
#It has no effect after the first launch of Harbor.
#Change the admin password from UI after launching Harbor.
harbor_admin_password = Harbor12345

##By default the auth mode is db_auth, i.e. the credentials are stored in a local database.
#Set it to ldap_auth if you want to verify a user's credentials against an LDAP server.
auth_mode = db_auth

#The url for an ldap endpoint.
ldap_url = ldaps://ldap.mydomain.com

#A user's DN who has the permission to search the LDAP/AD server.
#If your LDAP/AD server does not support anonymous search, you should configure this DN and ldap_search_pwd.
#ldap_searchdn = uid=searchuser,ou=people,dc=mydomain,dc=com

#the password of the ldap_searchdn
#ldap_search_pwd = password

#The base DN from which to look up a user in LDAP/AD
ldap_basedn = ou=people,dc=mydomain,dc=com

#Search filter for LDAP/AD, make sure the syntax of the filter is correct.
#ldap_filter = (objectClass=person)

# The attribute used in a search to match a user, it could be uid, cn, email, sAMAccountName or other attributes depending on your LDAP/AD
ldap_uid = uid

#the scope to search for users, 1-LDAP_SCOPE_BASE, 2-LDAP_SCOPE_ONELEVEL, 3-LDAP_SCOPE_SUBTREE
ldap_scope = 3

#Timeout (in seconds)  when connecting to an LDAP Server. The default value (and most reasonable) is 5 seconds.
ldap_timeout = 5

#Turn on or off the self-registration feature
self_registration = on

#The expiration time (in minute) of token created by token service, default is 30 minutes
token_expiration = 30

#The flag to control what users have permission to create projects
#The default value "everyone" allows everyone to creates a project.
#Set to "adminonly" so that only admin user can create project.
project_creation_restriction = everyone

#Determine whether the job service should verify the ssl cert when it connects to a remote registry.
#Set this flag to off when the remote registry uses a self-signed or untrusted certificate.
verify_remote_cert = on
#************************END INITIAL PROPERTIES************************
#############

The layers will be deleted by garbage collection of the registry, please refer to the docs of docker for the detail.

Is this https://docs.docker.com/registry/garbage-collection/ ?

Yes.

Thanks !


Mechanism to build pre-computed testing state

Several parts:
A "Test State" description file
We will place to put test state files somewhere in our repo. They will have a something like the following format (this is a major work in progress):
@TestStateGenerator("Filename?")
class SomeTestState {
 @GenerateState('stateNameKey')
 async baseState() {
   const baseProvider = await makeProvider(seed, ACCOUNTS);
   const addresses = baseProvider.getContractAddresses();

   const john = await ContractAPI.userWrapper(ACCOUNTS[0], baseProvider, addresses);
   const mary = await ContractAPI.userWrapper(ACCOUNTS[1], baseProvider, addresses);
   const bob = await ContractAPI.userWrapper(ACCOUNTS[2], baseProvider, addresses);

   await john.approveCentralAuthority();
   await mary.approveCentralAuthority();
   await bob.approveCentralAuthority();

   return {
     bob,
     john,
     mary,
   };
 }

 @GenerateState('derived state name', 'baseState');
 state2(constractAPI:ReturnType<SomeTestState.baseState>) {
   const yesNoMarket1 = john.augur.contracts.marketFromAddress(markets['yesNoMarket1']);
   const yesNoMarket2 = john.augur.contracts.marketFromAddress(markets['yesNoMarket2']);

   return {
     yesNoMarket1,
     yesNoMarket2,
   }
 }
}

what's this


wit, wit/bindgen: generate Go type aliases for WIT type aliases

Go type aliases are now generated for each WIT type alias (type foo = bar). Deep chains of type aliases (type b = a; type c = b;) are fully supported. Generated documentation now reflects whether a type is an alias.
For example, given the following WIT:
package example:aliases;

interface i {
	resource r {
		m: func() -> u32;
	}

	type a = r;
	type b = a;
	type c = b;

	fa: func(v: a);
	fb: func(v: b);
	fc: func(v: c);
}

world w {
	import i;
	export i;
}

Generates the following Go:
// R represents the imported resource "example:aliases/i#r".
//
//	resource r
type R cm.Resource

// A represents the imported type alias "example:aliases/i#a".
//
// See [R] for more information.
type A = R

// B represents the imported type alias "example:aliases/i#b".
//
// See [A] for more information.
type B = A

// C represents the imported type alias "example:aliases/i#c".
//
// See [B] for more information.
type C = B

Fixes #204.

Just verified that this PR does what it says it does. Thank you very much for such a quick response @ydnar


[$250] [HOLD for payment 2024-05-05] Payment issue for Add Split expense to Global Create

This issue is a summary payment issue for @getusha and @shubham1206agra for their work on the Add Split Expense to Global create. They have done:

Cleanup all instances of "request" and "send money" in App by Shubham
Implement route changes in NewDot for updated Global Create by Shubham
Refactor Participant Selector by Me
Writing the detailed section of the Add Split Expense to Global create

The last PR has also been merged and deployed to staging on Monday 22nd April and that was well before the deadline of 1st May. There were no major regressions and it seems like we are in a good spot now. I have offered the team a bonus of $1000 for completing this project urgently once week before the official deadline which would be Tuesday 23rd April and they have met this deadline so they deserver the bonus too.
The total rewards for each are $3500 where $2500 was a base and $1000 bonus for completion. There were also basically no regressions.
I believe that is a reasonable reward given the urgency, proactive approach, starting discussions in the vip-split room, writing the design doc, helping to resolve the threads from the doc so we could start the implementation, implementing all the frontend changes, cross testing and reviewing the PRs.
$3500 to @shubham1206agra and $3500 to @getusha for the completion of this entire project
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a5df74a98073dc25
Upwork Job ID:<PHONE_NUMBER>242520064
Last Price Increase: 2024-04-30

done


[WIP] Amazon Linux 2023 proof-of-concept

Description of changes:
This is an initial PoC for an AL2023-based EKS worker AMI.
Changelog:

rsa SSH keys not supported by default on AL2023, switched to ed25519.
Removed Docker from template variables.
Removed upgrade_kernel.sh provisioner -- AL2023 is on kernel 6.1 by default.
Removed curl in favor of curl-minimal.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

What protocol do you need that is not provided by curl-minimal ?

Thanks for combing through this, @stewartsmith! This is a very rough draft I threw together to see how far the existing template was from a successful build with an AL2023 base. I'll follow up on the items one-by-one, but I expect to remove many oddities that have accumulated over time.

@cartermckinnon would it be better if the AL2023 version was a new repo? Given the new AL release cadence it seems likely that multiple AL versions will be relevant at a given time. By changing repos it'd also allow for tooling changes without impacting the previous version.

Note: For installing curl (or gnupg) on top of the -minimal variant, the best approach is to use dnf swap, for example:
sudo dnf swap curl-minimal curl

@cartermckinnon
Have you tried this and had it work?  I had to add iptables-legacy to get bootstrap.sh to run.  However coredns  continually errors out and restarts.  There is no pod-to-pod networking that works - and I can't seem to figure out why.
[INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [INFO] plugin/kubernetes: waiting for Kubernetes API before starting server                                                                                │
│ [WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API                                                                                │
│ .:53                                                                                │
│ [INFO] plugin/reload: Running configuration SHA512 = 74129e6fb7c506b394c384adbdec8b507dec173739e054b346299b79b229f2ce2342b444c4298b2d6c85b6d7302ee317ae1fd6ea3eff84c03129413ddcdda3ba                                                                                │
│ CoreDNS-1.9.3                                                                                │
│ linux/amd64, go1.19.5, b8f104d1                                                                                │
│ [INFO] <IP_ADDRESS>:35475 - 57502 "HINFO IN<PHONE_NUMBER>292060063.1664824736373062434. udp 57 false 512" - - 0 6.001588443s                                                                                │
│ [ERROR] plugin/errors: 2<PHONE_NUMBER>292060063.1664824736373062434. HINFO: read udp <IP_ADDRESS>:38767-><IP_ADDRESS>:53: i/o timeout                                                                                │
│ [INFO] <IP_ADDRESS>:35034 - 21288 "HINFO IN<PHONE_NUMBER>292060063.1664824736373062434. udp 57 false 512" - - 0 6.001696281s                                                                                │
│ [ERROR] plugin/errors: 2<PHONE_NUMBER>292060063.1664824736373062434. HINFO: read udp <IP_ADDRESS>:37140-><IP_ADDRESS>:53: i/o timeout                                                                                │
│ [INFO] <IP_ADDRESS>:50233 - 61768 "HINFO IN<PHONE_NUMBER>292060063.1664824736373062434. udp 57 false 512" - - 0 2.000631216s                                                                                │
│ [ERROR] plugin/errors: 2<PHONE_NUMBER>292060063.1664824736373062434. HINFO: read udp <IP_ADDRESS>:48565-><IP_ADDRESS>:53: i/o timeout

The related errors seem to be a CNI problem.
May 17 19:10:22 ip-192-168-20-231.us-east-2.compute.internal kubelet[2326]: E0517 19:10:22.972813    2326 kubelet.go:2376] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
May 17 19:10:28 ip-192-168-20-231.us-east-2.compute.internal kubelet[2326]: E0517 19:10:28.226863    2326 kubelet.go:2376] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
May 17 19:10:33 ip-192-168-20-231.us-east-2.compute.internal kubelet[2326]: E0517 19:10:33.227694    2326 kubelet.go:2376] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
May 17 19:10:38 ip-192-168-20-231.us-east-2.compute.internal kubelet[2326]: E0517 19:10:38.228454    2326 kubelet.go:2376] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
May 17 19:10:43 ip-192-168-20-231.us-east-2.compute.internal kubelet[2326]: E0517 19:10:43.228781    2326 kubelet.go:2376] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"

@cartermckinnon a few more things here:
https://github.com/awslabs/amazon-eks-ami/compare/master...dims:amazon-eks-ami:al2023-poc-dims
(also rebased to master!)
Only thing i had to do was to add the role to the configmap as it was not getting added for some reason:
https://karpenter.sh/v0.26/troubleshooting/#:~:text=CSINode publishing%3A Unauthorized-,Check the ConfigMap,-to check whether
snippet from kubectl get nodes -o yaml shows:
    nodeInfo:
      architecture: amd64
      bootID: 1d95ba81-e95c-4073-8a77-a2351489ee07
      containerRuntimeVersion: containerd://1.6.19
      kernelVersion: 6.1.29-47.49.amzn2023.x86_64
      kubeProxyVersion: v1.27.1-eks-2f008fe
      kubeletVersion: v1.27.1-eks-2f008fe
      machineID: ec220096a17ae2fd59153f731a6b9346
      operatingSystem: linux
      osImage: Amazon Linux 2023
      systemUUID: ec220096-a17a-e2fd-5915-3f731a6b9346

Closing this PR in favor of #1340.


Create a tool to get images that are referenced by MLFlow charm

Description
To be able to deploy the mlflow bundle in an airgapped environment, there needs to be a script available to retrieve a complete list of images that can be deployed by mlflow-operator.
This script will then be used by the airgapped environment script in https://github.com/canonical/bundle-kubeflow/pull/682.
Discussed in https://github.com/canonical/bundle-kubeflow/issues/705#issuecomment-1738860909.

closed by #211


Highlight non-breaking spaces in editor

Hi,
It could be a good idea to highlight non-breaking spaces when you edit a post. It's very useful in french, especially for angle quotes and numbers (we write 35 000 and not 35.000).
I may have found a solution on stackoverflow.
Thanks for all

Hi @toblerone1963,
We're going to be overhauling the editor soon, so I recommend adding this over on our wishlist. We use this list to help determine what goes into the roadmap and how to prioritise features. This is not something we would fix in the existing editor as it would likely be lost in the overhaul.
Note: You can also access the wishlist any time from inside the Ghost admin:


⚠ ClamAV has degraded performance

In 316c7bc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 226 ms

Resolved: ClamAV performance has improved in 5bfae8c.


breaks on RN version 0.30 rc0

I'm new to this library so haven't much background yet, but I've used programmatic SVG for React in the web-browser for years.
I'm able to get the red outline mentioned in issue number #73 .
I've sucessfully migrated to 30; I have a View and Text working.  The Svg is only showing the red outline.

I`m closing this.
This is duplicated with #73


Rubygems / Bundler updates are moving dependencies from global to secondary source

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Bundler
Package manager version
Bundler 2.5.4
Language version
Ruby 3.3.3
Manifest location and content before the Dependabot update

Gemfile
Gemfile.lock

dependabot.yml content
version: 2

registries:
  bundler-github:
    type: rubygems-server
    url: https://rubygems.pkg.github.com/[redacted]
    token: [redacted]

  bundler-graphql-pro:
    type: rubygems-server
    url: https://gems.graphql.pro/
    token: [redacted]

updates:
  - package-ecosystem: 'bundler'
    registries:
      - bundler-github
      - bundler-graphql-pro
    vendor: true
    directory: '/'
    schedule:
      interval: 'daily'
      time: '10:00'
      timezone: 'America/New_York'
    versioning-strategy: 'increase-if-necessary'
    groups:
      google:
        patterns:
          - 'google*'
      graphql:
        patterns:
          - 'graphql*'
      packwerk:
        patterns:
          - 'packs*'
          - 'packwerk*'
      pry:
        patterns:
          - 'pry*'
      rubocop:
        patterns:
          - 'rubocop*'
      sentry:
        patterns:
          - 'sentry*'

  - package-ecosystem: 'github-actions'
    directory: '/'
    schedule:
      interval: 'daily'
      time: '10:00'
      timezone: 'America/New_York'

Updated dependency
We've seen this with a couple of dependencies, but the most recent culprit is shoulda-matchers going from v6.1.0 to v6.2.0.
What you expected to see, versus what you actually saw
Dependabot is moving a bunch of dependencies from our primary source (https://rubygems.org/) within Gemfile.lock to a secondary source, when there is an overlap of sub-dependencies between sources. That secondary source includes a gem that has the same sub-dependencies as the dependencies that were moved, which I think is the likely cause.
Native package manager behavior
Bundler will, AFAIK, only list dependencies in a secondary source that are only available within that source. Sub-dependencies that are available in the global source are only listed in the global source within Gemfile.lock.
Images of the diff or a link to the PR, issue, or logs

I hope this diff screenshot is helpful! The removals are within the https://rubygems.org/ source, while the additions are within a private source (in our case, a GItHub Packages RubyGems registry).
Smallest manifest that reproduces the issue
source 'https://rubygems.pkg.github.com/[redacted]' do
  gem 'foo' # <= some private dependency that includes `activesupport` as a dependency, which shoulda-matchers also depends on
end

group :test do
  gem 'shoulda-matchers'
end

I am going to close this, as I've managed to track down that this is a subtle bug with Bundler itself (rubygems/rubygems#7540) when multiple sources and vendoring of gems are used. Sorry for the confusion!

Thanks for circling back to let us know!
You're in good hands with @deivid-rodriguez  :smile:

@jeffwidman so while this was fixed upstream in Bundler v2.5.9, it seems like Dependabot may not be using that version when doing its Gemfile.lock updates? Is it possible to confirm what version of Bundler is being used?

Closing again, as it looks like this has now been resolved in Dependabot as well!


Update Provenance.hs

small typo corrections.

Thanks for the contribution! Monad, state and transformer don't require capitalisation, but the other changes look good. Looks like one thing is failing in CI due to a probabilistic failure, I'll restart.


#13 0.616 Err:6 http://debian-archive.trafficmanager.net/debian buster-backports Release #13 0.616   404  Not Found [IP: <IP_ADDRESS> 80]

I used Sonic-VPP two weeks ago, and I was able to build the image without any problem. I cloned the repo this week in a new server, and when I tried to run the make sonic command. I am getting the following error:
sonic-net/sonic-buildimage#13 0.616 Err:6 http://debian-archive.trafficmanager.net/debian buster-backports Release
sonic-net/sonic-buildimage#13 0.616   404  Not Found [IP: <IP_ADDRESS> 80]
The repository 'http://debian-archive.trafficmanager.net/debian buster-backports Release' does not have a Release file.
I guess it could be something on the /sonic-platform-vpp/build/sonic-buildimage/sonic-slave-buster/Dockerfile.j2, but I am not really sure. Do you guys have any idea of it?

Hi @neethajohn I partially fixed it by changing the NOBUSTER from 0 to 1 on the sonic-buildimage Make file:
/sonic-buildimage$ cat Makefile
SONiC make file
NOJESSIE ?= 1
NOSTRETCH ?= 1
NOBUSTER ?= 1
NOBULLSEYE ?= 0
It seems there is no trafficmanager support anymore for Debian's Buster version. So maybe we have to change the 'http://debian-archive.trafficmanager.net/debian repository if we want to keep building buster images

Using the env flag "MIRROR_SNAPSHOT=y" may also help partly, since it this tells the build system to use a different mirror repository.


Use urlparse to generate websocket url

Fixes #246

I will wait for @foklepoint to test this before merging. If you didn't change anything else in this PR, ignore "nit" comments.

@dims I think you added the original code. Can you answer the question?

I am fine with the new code doesn't have the logic to replacing "//api" with "/api". I would say we can merge this (after rebase) and if @dims has objection we can always patch it.

I've fixed the comment and rebased it.
Thank you all for your time.


Add invite URL paramter to user invite function

Related Issues
Fixes https://github.com/descope/etc/issues/4090
Description

add invite options (which includes invite URL)
also changed replaceUserPassword to return authentication info (instead https://github.com/descope/descope-java/pull/61)

Are you planning to bump the version? If so, please update the pom in both the main and examples

Are you planning to bump the version? If so, please update the pom in both the main and examples

Not at the moment, I will wait for next releases as this is not urgent


[v2.5.10] Backport: Warnings "will not create impersonation account on cluster" seen on rancher startup

Issue: https://github.com/rancher/rancher/issues/34076

Moving it to Review as the linked PR is not merged yet

My checks PASSED
Reproduction Steps:

Not required.

Validation Environment:

Rancher version: v2.5-head b2f17e430 pulled 9/9/21 11:20am Pacific
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: RKE1 Digital Ocean (rancher node driver)
Downstream K8s version: v1.20.10-racher1-1
Validation steps:

Deploy rancher. Log in and set password.
Deploy a 1-node DigitalOcean cluster as Admin.
No errors are seen in the rancher server logs like indicated in the original issue.


Unable to deploy within existing resource groups

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

If you have existing resource groups you are using for testing and experimentation this application fails to deploy and use
existing resource groups.   It fails with:
A resource with the same name cannot be created in location 'eastus2'. Please select a new resource name. (Code: InvalidResourceLocation)
Follow the readme and set each resource group to my common resource group as follows:
azd env set AZURE_SUBSCRIPTION_ID <
azd env set AZURE_RESOURCE_GROUP rg-ParsonsSearch
azd env set AZURE_FORMRECOGNIZER_RESOURCE_GROUP rg-ParsonsSearch
azd env set AZURE_FORMRECOGNIZER_SERVICE cog-fr-parsonssearch
azd env set AZURE_SEARCH_SERVICE_RESOURCE_GROUP rg-ParsonsSearch
azd env set AZURE_SEARCH_SERVICE search-parsons
azd env set AZURE_SEARCH_INDEX idx-oaicsharp
azd env set AZURE_STORAGE_RESOURCE_GROUP rg-ParsonsSearch
azd env set AZURE_STORAGE_ACCOUNT parsonssearch
azd env set AZURE_STORAGE_CONTAINER oaicsharp
azd env set AZURE_OPENAI_RESOURCE_GROUP GPT4
azd env set AZURE_OPENAI_SERVICE GPT4-Preview
azd env set AZURE_OPENAI_CHATGPT_DEPLOYMENT GPT4-32K
azd env set AZURE_OPENAI_GPT_DEPLOYMENT GPT4-32K-unfiltered
azd env set AZURE_OPENAI_EMB_DEPLOYMENT Embedding
azd env set BACKEND_URI https://oaicsharp.azurewebsites.net
Any log messages given by the failure

Expected/desired behavior

Ideally the deployment code would identify and reuse the existing resrouces.
This is specifically important for the OpenAI resources which will not allow deployments
beyond certain token limits.
OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10

Versions

Mention any other details that might be useful
This problem does not exist in the Python version of this example.   I assume it is somewhere down in the
bicep files.

Thanks! We'll be in touch soon.

Related to #127


ConnectAsync fails when many Tasks are active

Describe the bug
For load tests we created an application that contains of a lot of Tasks (via Task.Run) which publish MQTT messages. Unfortunately ConnectAsync does not succeed to have a stable connection when a lot of Tasks are active. Note that the CPU load was very low since the Tasks didn't do very much.
This may seem like a "toy code" problem. But our production application has the same problems, too. As soon as a few dozen Tasks are running an MQTT connection is not possible anymore.
Which project is your bug related to?

Client (<IP_ADDRESS> .NET 4.5.2)

To Reproduce
Steps to reproduce the behavior:

Create 100 Tasks
Connect to an MQTT broker
Connect won't succeed

Expected behavior
ConnectAsync would be successful
### Code example
 Please provide full code examples below where possible to make it easier for the developers to check your issues.

```csharp
            // LOGGING
            MqttNetGlobalLogger.LogMessagePublished += (s, e) =>
            {
                var trace = $">> [{e.TraceMessage.Timestamp:O}] [{e.TraceMessage.ThreadId}] [{e.TraceMessage.Source}] [{e.TraceMessage.Level}]: {e.TraceMessage.Message}";
                if (e.TraceMessage.Exception != null)
                {
                    trace += Environment.NewLine + e.TraceMessage.Exception.ToString();
                }

                Console.WriteLine(trace);
            };

            // CREATE TASKS (which do almost nothing)
            bool run = true;

            for (int i = 0; i < 100; i++)
            {
                Task.Run(() =>
                {
                    while (run)
                    {
                        Thread.Sleep(100);
                    }
                });
            }

            Thread.Sleep(10000);

            // CONNECTING
            var options = new MqttClientOptionsBuilder()
                .WithClientId(Guid.NewGuid().ToString())
                .WithTcpServer("localhost",1883)
                .WithCleanSession()
                .Build();

            var result = mqttClient.ConnectAsync(options).Result;  // THIS WILL NOT SUCCEED

            Thread.Sleep(10000);
            run = false;

As far as I see, you are simulating 100 long running Tasks. Because of the Thread.Sleep(...) they will block a thread on the thread pool of the TPL. Which is the same as a long running Task will do.
If the code reaches ConnectAsync(...), the TPL will reach a point, where it needs a thread of the thread pool, but they are very busy with other tasks (tasks, which will not finish in this example, as long as the ConnectAsync(...) hasn't finished, maybe kind of deadlock).
As far as I know, the TPL will create more threads in the thread pool, if there is a lot of work to do, but I don't know if there is an upper limit on how much threads will be created.
Did you test it with less concurrent tasks? Maybe 10 or 20?

I found your issue very interesting, so I did a little research and found the following, maybe this helps you: The managed thread pool
If you have short tasks that require background processing, the managed thread pool is an easy way to take advantage of multiple threads.
and
You can control the maximum number of threads by using the ThreadPool.GetMaxThreads and ThreadPool.SetMaxThreads methods.

Ok, thank you very much for the detailed answers and your investigations. And yes, I tried it with 10-20 threads and then it worked. That means the connect (with 100 tasks) really didn't just work because the thread pool was exhausted.
So it's not a problem in the MQTTnet library (which means this issue can be closed) but it's a problem in my understanding of things.

Task.Run(...) shall only be used for short-running stuff
Long running processes shall always have their own threads
Thread.Sleep(...) does return computing resources to the CPU (so that another thread can be processed), but it does NOT return a thread to the thread pool (which is quite clear... in hindsight).

I'm glad I could help.

Good to know that this is solved. Thank you @OidaTiftla. By the way, cool user name 😅


UI Plugin: Build components for AWS management cluster workflow

Feature Request
Based on most recent mockups for AWS management cluster creation simplified workflow, build out the required components/steps for deploying management cluster.
Note: this does not include wiring up underlying REST APIs (separate issue)
Describe alternatives you've considered
None

Duplicate


feat: version bump to 1.8.0

Adds historical availability types.

:tada: This PR is included in version 1.8.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Transform jumps on .then call

I have a randomly generated transform, after which I call .then() and chain a stroke tween. The resulting shape animation seems to jump:
http://codepen.io/sdras/pen/2b9e7b16fb55afe2b45442716da9a814
I think this is spec behavior but might come up as a problem because the expected behavior is much different

Hi Sarah!
I'm sorry about that, seems a bug, will try to fix it shortly.
Thanks!

Thank you!

Hi, oddly it doesn't display the jump behaviour when you run the example using the player... I guess this is the intended
// --
.then({
strokeWidth:    0,
easing: 'sin.in'
});//.play();
new MojsPlayer({ add: shape });

Hi Phil!
Could you make an example? What versions of mojs and mojs-player are you using?
// @philmon4

Phill, I see, it doesn't jump on subsequent runs.

Yep, sorry about not giving more detail.   I basically played around with
Sarah's codepen in the editor so it's the same environment as hers.  The
cut and paste in my email was straight from codepen.  I can only offer it
just in case it sparked off an idea because of the different behavior.
I was playing around with similar .then constructs but all mine end and
carry on from known static points so I never noticed it before and just
played around. I did have a quick peek at the code to see why the value
gets dropped but I'm under a lot of time pressure right now and failed to
get a handle on it quickly enough.
It's a great library, and when I start to get a better grip on it I hope I
can contribute something a little more helpful, maybe to the docs ....
Thank you
Phil
On 10 December 2016 at 17:46, Oleg Solomka<EMAIL_ADDRESS>wrote:

Phill, I see, it doesn't jump on subsequent runs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/legomushroom/mojs/issues/68#issuecomment-266225517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFFkh8fgnboLlDpdBGv8sdWlkKpVjhQoks5rGuVmgaJpZM4KfMXh
.

@philmon4 awesome! Would love to get a contribution from you one day!

Seems the .then method is not 100% reliable. Have a similiar bug when setting different origins in the shape tween object and in the .then method. Can work around it by setting the origin to a tweenable object instead of a static one. Like this:
new mojs.Shape({
  shape: 'rect',
  scaleY: {0: 1},
  origin: {"0% 0%": "0% 0%"}, // instead of just origin: "0% 0%"
}).then({
  scaleY: {1: 0},
  origin: "0% 100%",
});

Will take a closer look at the bug later.


Mypy annotation zserver.lib.html_diff

Automated message from Dropbox CLA bot
@medullaskyline, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@medullaskyline, thanks for signing the CLA!

@medullaskyline thanks for working on this!  It looks pretty good; I posted one comments, also while you're fixing that can you squash the commits together and give the resullt a nice commit message (the description of the pull request isn't merged, just the commit message(s) for the individual commit(s))

Merged after changing the commit message title to the present tense, thanks @medullaskyline!


Disallow CRI socket mounts

I'd recommend adding both of these as, without them, the rule can easily be bypassed by mounting any of the following:

/var
/var/run

Probably makes more sense to just add this as a sentence in the description and for users to select an additional policy such as this to complement the disallow CRI sockets policy.

Ideally, users would use an "allow list" and should use the "Limit hostPath Volumes to Specific Directories" and should never use the "Disallow CRI socket mounts" . However, not all users are at that stage and many may still want to use a "deny list". For users who select to do so, I think it makes more sense to actually make this policy do what it claims to do (block CRI socket mounts) instead of going half-way and just blocking some of the paths.


WIP: improve coverage

@tiaguinho  have you updated this pull request?

@avelino you can merge this.
I'll do more in another PR.


Web -Using CMD + V doesn’t focus the input and insert the text unlike slack

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open any chat
Unfocused the text input
and use CMD + V or Ctrl + V

Expected Result:
The compose box will be focused and the text is pasted
Actual Result:
The compose box is not focused and nothing happens
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/231866503-13bd4950-fab7-4622-9074-48d1e9e56a2a.mov
https://user-images.githubusercontent.com/93399543/231866567-e201f121-bab4-467c-b999-7161a3bd230a.mp4
Expensify/Expensify Issue URL:
Issue reported by: @getusha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681361141142909
View all open jobs on GitHub

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

About to go offline for the week

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

This actually isn't a bug. We discussed this in this slack thread, and decided this is a new feature that we intentionally do not support today.
So we should use the new feature label here instead.

Current assignee @joekaufmanexpensify is eligible for the NewFeature assigner, not assigning anyone new.

I verified that this behavior doesn't currently exist in NewDot, but does in Slack. IMO, it makes sense to do this eventually, but it doesn't feel like a high priority change.
Going to un-assign per the new feature process. This is ready to be worked on whenever we want to pick it up.

Keyboard short cut bugs are not in scope. Closing the bug as per this comment


Port to new native REST API

Per announcement from Gerv below we should consider porting bztools to the new native REST API in the future but perhaps this would be a good first bug for a contributor.
"This service is due to be decommissioned. Fortunately, Bugzilla has a new native REST API which works somewhat similarly that you could use instead:
https://wiki.mozilla.org/Bugzilla:REST_API
Moving to that new API would require some porting work. If that seems like too much effort, fear not, because there is also a BzAPI compatibility layer built on top of the new API. Because it's compatible, using that should simply require a change of API endpoint.
Change:
https://api-dev.bugzilla.mozilla.org/latest/
(or https://api-dev.bugzilla.mozilla.org/1.3/)
to
https://bugzilla.mozilla.org/bzapi/"

@bkerensa are you still planning to work on this?

We should leave this as a Good First Bug to on ramp new contributors

@sylvestre As a beginner, can I work on this if not already done?

Note: I'd recommend doing this sooner rather than later, since BzAPI is 2-10x slower in many cases. See:
https://bugzilla.mozilla.org/show_bug.cgi?id=1301541
https://bugzilla.mozilla.org/show_bug.cgi?id=1035804


Breaking: Revert "[WIN/LINUX] Implement vtable dummies (virtual dtors) through extra trait"

This reverts commit c37cb037be072cac43f2706b89f1388b9deee19a. This commit is squashed in the merge of PR #5, and does not exist in-tree.
https://github.com/microsoft/DirectXShaderCompiler/pull/3793 has finally been merged on October 13th 2022 and now allows us to drop the vtable dummies for virtual destructors again, as those are not part of the ABI and shouldn't have been in the vtable in the first place.

Note that releasing hassle-rs with this change relies on a DXC built with at least that PR, which was meged on October 13th.

I have unfortunately not found a clear way to detect the version of libdxcompiler.so at runtime or some other way to inform the user about this discrepancy... We'll have to release this as a breaking change and clearly document since what commit / version DXC is becoming incompatible I think.

We've previously done this by stating all the many commits that we landed upstream, together with DXC release tags.
I've converted those overly verbose and hard-to-scan-through paragraphs to a simple table, describing exactly what DXC version is going to be needed for a given hassle-rs release: the only breaks happened with 0.5.1 (when using intellisense intellisense) and are going to happen with 0.10.0 where this PR is supposed to land. Besides that it's just been flaky/broken IID support on MacOS+clang and gcc compilers before a given DXC commit/release.

CC @cwfitzgerald, such breaking changes in DXC releases and hassle-rs may be extra relevant for you now that you're using DXC in wgpu :)

Thanks for the heads up! What are the consequences of loading an old version?

@cwfitzgerald It'll segfault, because the COM vtables changed (for the better, mind you!).

It only segfaults on linux? If so, that's spooky but tolerable as we will only use DXC on windows.

It's spooky but only because we previously worked around clearly-wrong vtable layouts, and it quite frankly took well over a year to fix upstream :/

DXC v1.7.2212 just released, seems like a great moment to merge this and make a new release to crates.io :tada:


Fails to cast timestamp when $dateFormat is set

When $dateFormat property is set in a model (e.g. to ISO8601) and $casts property has timestamp
    /**@inheritdoc */
    protected $dateFormat = Carbon::ISO8601;

    /**@inheritdoc */
    protected $casts = [
        'created_at' => 'date',
    ];

Laravel fails on reading this attribute.
Internally Laravel got a string from database such as '2016-02-07 22:03:19' and from stack getAttributeValue -> castAttribute -> asDateTime it goes to Carbon::createFromFormat($this->getDateFormat(), $value) where fails on invalid data.
The problem IMHO is that Laravel tries to use same format for input data (from database) and for output (in format requested by user).

Sorry, another IMHO
function fromDateTime accepts not only DateTime or int but string as well as it is called from setAttribute as well. In fact it translates from user <-> model format to model <-> database one.

    /**
     * Convert a DateTime to a storable string.
     *
     * @param  \DateTime|int  $value
     * @return string
     */
    public function fromDateTime($value)
    {
        ...
    }

I've found a workaround. It doesn't support auto convert to JSON but solves the problems

data can be read (as Carbon) and written (Carbon or ISO8601 string) to model
model can read dates from/write to database in format appropriate for database

class MyModel extends Model
{
    ...
    /**
     * @inheritdoc
     */
    public function setAttribute($key, $value)
    {
        if (is_string($value) && (in_array($key, $this->getDates()) || $this->isDateCastable($key))) {
            $value = Carbon::createFromFormat(Carbon::ISO8601, $value);
        }

        return parent::setAttribute($key, $value);
    }
}

Ping @taylorotwell for advice.

@neomerx thank you for the workaround, did you stick to this solution?

@dschniepp I was using it without changes. However I've been working mostly on non-Laravel projects recently so you'd better to check it on the latest version on your own.


[Feature request] Add an option to resize the advancements window

Kinda like in the better advancements mod (some tabs at least with BlazeandCave's Advancements Pack are not centered, maybe it can be done better here)
Here are some screenshots showing how it looks like in better advancements mod:

.

there we go. Looks like this is already resolved, I just did never close the issue :)


LND crashes on startup can't access funds

I was setting up my LND node and installed RTL (ride the lightning)
As I was using it to create new channels I noticed an option to use unconfirmed transactions, since my stuff was currently still unconfirmed I thought, sure!
However, my balance stopped showing up, so I restart.
Now, LND won't start anymore and I don't know how to access the channels in order to close them and get them back.
This is the error it gives me when I try to unlock my wallet. It seems to work okay before that.
2019-09-04 04:16:26.513 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2019-09-04 04:16:26.513 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2019-09-04 04:16:26.514 [INF] LTND: Waiting for chain backend to finish sync, start_height=593152
2019-09-04 04:16:27.123 [DBG] LNWL: Chain backend synced to tip!
panic: Unable to synchronize wallet to chain: t: short read (expected 8 bytes, read 0)
goroutine 114 [running]:
github.com/btcsuite/btcwallet/wallet.(*Wallet).handleChainNotifications(0xc000254500)
/home/opti/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190712034938-7a3a3e82cbb6/wallet/chainntfns.go:117 +0x149d
created by github.com/btcsuite/btcwallet/wallet.(*Wallet).SynchronizeRPC
/home/opti/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190712034938-7a3a3e82cbb6/wallet/wallet.go:191 +0x153
opti@ubuntu:~/lnd$
Using Ubuntu 18.08
LND Version: 0.7.1-beta commit=v0.7.1-beta-155-g06206f09b5c0c29654110b5cb95a85a9c0e75e14
bitcoind
Latest version of RTL

@Rabbit7744  You need to report to RTL folks on their Github repo. The LND dev team has nothing to do with RTL.

@molxyz I understand that the LND has nothing to do with RTL, I don't really want to use RTL anymore though. Just looking for a way at the moment to start LND back up so I can get to my stuff.

@Rabbit7744
If you have the seed words and channel.backup file, you should be able to recover your funds by starting a new lnd instance and follow the SCB guides. Your channel.backup should be in the default location ~/.lnd/data/chain/bitcoin/mainnet/channel.backup
And here are the guides:  https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md
You can also ask on the LND slack for help if needed.

Are you seeing this error reliably upon unlocking the wallet? Any other logs available?

@wpaulino It does happen upon unlocking the wallet, I don't think I have any other logs.
I doesn't even save the error to the .log file, it's just throwing it in my console.

Yeah recovering is probably your best bet here, though I'm still interested in how you arrived at this state. Do you have the logs before running into the issue?

I doesn't even save the error to the .log file, it's just throwing it in my console.

That's because the program crashed and it can't write the output to the log file.

Recovery went okay. I tried digging through the logs but can't discover anything out of order.
My guess is that it had to do with the RTL option of spending unconfirmed transactions, however I'm not willing to try and recreate the issue.
Thank you for your assistance!


Set flag to prompt for sudo password on setup.yml

The setup playbook requires privilege escalation.
If the user runs the playbook with an account that requires
password to be entered when sudo'ing, then ansible should
prompt the user for the password.

Continuous integration will be setup as a part of future work.


embedly "card" embeds render empty

With a valid EMBEDLY_KEY, when I embed a URL for which Embedly doesn't have specific support, such as http://pointnineseven.com/
I expect to see an Embedly Card summarizing the URL on the live page, but nothing is rendered. The output markup is:
`
`
Other embeds (Vimeo, Youtube) work.

@edrex been a while - any chance you have the markup still? it is showing as blank in your comment.
This might need to be revisited with the upcoming Draftail editor.

@lb- you can edit the comment to show the markup, please see above.

@thibaudcolas thanks :)


New build does not contain latest changes from github

Last MSLab build does not contain latest changes.
Looks like build process is broken. @machv

Is this one still valid?
@jaromirk


Clarify documentation around DNs in MTRCertificates and MTRCertificateInfo.

Fixes https://github.com/project-chip/connectedhomeip/issues/24908

Fast-tracking platform-specific change with platform owner review.


"Removed" Standards Still Showing In Compliance "Dashboard".

Hi, my name is klawrawkz. I am fine. How are you?
According to this documentation, we can "remove a standard from [our] dashboard."

Remove a standard from your dashboard
You can continue to customize the regulatory compliance dashboard, to focus only on the standards that are applicable to you, by removing any of the supplied regulatory standards that aren't relevant to your organization.
To remove a standard:

From Defender for Cloud's menu, select Security policy.
Select the relevant subscription from which you want to remove a standard.
Note
You can remove a standard from a subscription, but not from a management group.
The security policy page opens. For the selected subscription, it shows the default policy, the industry and regulatory standards, and any custom initiatives you've created.

This does not appear to be the case in my implementation.
E.G. I follow these steps and all (each and every one) of the standards I have "removed" continue to defy me and are visible in the "dashboard."
Step 1: Remove unwanted.

Step 2: Navigate to "Regulatory Compliance 'blade'" and view the awe-inspiring results of "removal" procedure.

What's the story here? Why do these unwanted standards still show up in our UI? How do I "remove" them for real?
Thanks for the help, and I hope you are doing well.
klaw

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a9fbe6ca-1f70-657b-fc1a-c488335bdef6
Version Independent ID: 4962534a-ec5a-bc9a-f0ec-2074cf446807
Content: The regulatory compliance dashboard in Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/update-regulatory-compliance-packages.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: elkrieger

@klawrawkz
Thanks for your feedback! We will investigate and update as appropriate.

@ElazarK
Can you please check and add your comments on this doc update request as applicable.

@klawrawkz Thank you for reaching out. I am looking in to this.

@klawrawkz
I'm going to assign this to the document author so they can take a look at it accordingly.

@klawrawkz I apologize for the delay. I am checking with the relevant stakeholders and hope to have an answer for you soon.

@ElazarK
Thanks for the update and the help.

@klawrawkz I've heard back from the team and this is indeed a bug. They are working on this hope to have it resolved in just a few days. I will keep this GitHub issue open so that I can let you know as soon as they have it fixed.

@klawrawkz I've been informed that this issue has now been resolved. If you are having any further issues please feel free to open another GitHub issue and we'll be happy to assist.

#please-close


RDS MigrationResource CREATE_FAILED

Deploying a new stack with RDS fails when creating the MigrationResource:
no identity-based policy allows the cloudformation:DescribeStacks action

Logs:
|  Database db/MigrationHandler/ServiceRole/DefaultPolicy AWS::IAM::Policy CREATE_COMPLETE
|  Database db/MigrationHandler AWS::Lambda::Function CREATE_COMPLETE
|  Database db/MigrationResource Custom::SSTScript CREATE_FAILED Received response status [FAILED] from custom resource. Message returned: User: arn:aws:sts::******:assumed-role/mike-rpm-Database-dbMigrationHandlerServiceRole-******/mike-rpm-Database-dbMigrationHandler****** is not authorized to perform: cloudformation:DescribeStacks on resource: arn:aws:cloudformation:ca-central-1:******:stack/mike-rpm-Database/****** because no identity-based policy allows the cloudformation:DescribeStacks action

My stack:
import { RDS, StackContext } from "sst/constructs";

export function Database({  stack }: StackContext) {
  return new RDS(stack, "db", {
    engine: "postgresql13.9",
    defaultDatabaseName: "main",
    migrations: "packages/core/migrations",
    types: "packages/core/src/sql.generated.ts",
  });
}

I believe this issue was introduced in sst 2.13.3. The deploy works fine on 2.13.2.
I also tested a few postgres/mysql engines and the results were the same.

https://discord.com/channels/983865673656705025/1119328118952435712

I had the same issue. Rolled back to 2.12.0 and everything worked again.

I also had the same issue and was able to get it working with version 2.13.2.

I am using 2.13.6 and I have this issue, looks like the bug is ongoing

Also experiencing this on a deployment and needed to downgrade to 2.13.2

Released in v2.16.0
Thanks @iloewensen.


Adding requirejs bookmarklet

RequireJS needs to be included on a tested page.

Hey folks. The Marmelab team is attempting to clean up the Issues backlog. With that, we're closing issues that have been open for an one or more years.
We really appreciate the folks have taken the time to open and comment on this issue. Please don't confuse this closure with us not caring or dismissing your issue, feature request, discussion, or report. If the issue pertains to a bug, please re-test for the bug on the latest version of gremlins.js.
The best way to report problems with gremlins.js 2.0 is to file new issues.


Bug: publishing on RabbitBroker hangs forever when connection lost

Describe the bug
If an application uses a RabbitBroker broker to publish messages, the application establishes the connection correctly but after the fact the connection is lost (e.g., broker goes offline) the publishing logic hangs for as long as the broker is offline and then attempts to publish all stuck messages at once.
How to reproduce
Follow the instructions in the code snippet.
# example.py
"""
How to reproduce the issue:
1. Start the FastAPI app (`uvicorn example:fastapi_app --host <IP_ADDRESS> --port 8181`)
2. Stop the broker
3. Send a POST request to http://localhost:8181/run-job (`curl -X 'POST' 'http://localhost:8181/run-job'`) and watch it hang
"""
from contextlib import asynccontextmanager

from fastapi import FastAPI
from faststream import FastStream
from faststream.rabbit import RabbitBroker

broker = RabbitBroker(
    f"amqp://guest:guest@localhost:5672",
    max_consumers=1,
)

@asynccontextmanager
async def lifespan(app):
    await broker.start()
    yield
    await broker.close()

fastapi_app = FastAPI(
    lifespan=lifespan
)
faststream_app = FastStream(
    broker=broker
)

async def run_job(message):
    print(f"Message processed: {message}")

broker.subscriber("run_job")(run_job)

async def run_job_http_endpoint():
    await broker.publish(queue="run_job", message={"job": "run"})
    return {"message": "Job processed successfully"}

fastapi_app.post("/run-job")(run_job_http_endpoint)

Expected behavior
When publishing, if the connection is in an invalid state, the operation fails fast raising some sort of exception.
Observed behavior
When publishing, if the connections is lost after its established correctly, the operation hangs forever.
Environment
$ faststream -v
Running FastStream 0.5.11 with CPython 3.10.12 on Darwin

Additional context
This looks like its linked to an open issue with aio-pika that could be the source of this one, because a check to the connection's state prior to publishing mitigates the issue, i.e., if broker._connection.connected.is_set() is False.

@sfran96 thx for such detail report! Indeed, seems like the problem on aio-pika side: I reported Issue and pinged Mosquito already. Also I am planning to help him with a fix, when we discuss, how the problem should be fixed. Wait a bit for it, please

Should be closed with tomorrow aio-pika release

AioPika fix was released today c9.4.3


attempt to compare number with nil

This occurs when trying to set the Chat CoreGUI to disabled. I am using SetCoreGuiEnabled("All"), in this screenshot, you can see that no CoreGUI is hidden.
This seems to only happen to me while using the ROBLOX Developer app for iOS.

Which version of Roblox Developer are you using? Since we don't force update Roblox Developer app as much you could be using an older version of the chat script.

This issue was moved to GitBlox/Core-Scripts#3

heY Mind IF ME Cum Cum IN UR assHawl?

tHAT me cUM in u LOL.


Regression : Link "Created with Visualize"

On PROD, the ‘Created with Visualize’ link leads directly to visualisation. On INT this link leads to the Visualize home page.
If it has not been expressly decided to modify this way for a good reason, please correct the link so that the user lands directly on the graph.
Please check and adapt the link in embeded URLs as well (AEM + iFrame).

Oh thanks for the explanation @bprusinowski . I wouldn't have looked for this feature under Button "share" but the main thing is that we can edit the graphic from the publication.
You can close the issue.
Thank you very much.

Thanks @ortnever! If it turns out to be confusing, we might need to revisit this with @KerstinFaye. But for now I will close the issue 👍


Update README.md for Kotlin Multiplatform Mobile client-side Twirp integration.

Issue #, if available:
Description of changes:
Add link to https://github.com/collectiveidea/twirp-kmm for Kotlin Multiplatform Mobile client-side Twirp integration.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks for your contribution.


(maint) Acceptance Rake - give CONFIG priority

This commit changes the logic in the beaker_test rake task for
acceptance giving BEAKER_HOSTS priority over TEST_TARGET.
It also changes the name of the ENV variable from CONFIG to
BEAKER_HOSTS
In the case that a static beaker host config file is needed for
running acceptance testing, the file path to this config should
be assigned to the ENV variable BEAKER_HOSTS. This value
will take precedence over any value set for TEST_TARGET.
TEST_TARGET is still used to supply a string for dynamically
generating beaker host configs.
skip:ci

:+1: