Feature/#35 secure with spring security

Adding a Spring Security secured endpoint was not enough: We also needed to keep the existing REST resources running and we need to take the CSRF-related HTTP 403 for resource-changing HTTP verbs into account. Also rest-assured has to be used to test this new secured resource.
The user credential configuration should also be implemented in a super simple way: we should be able to configure them as secret environment variables inside our cloud environment (e.g. Heroku).
And as this project is a backend PLUS frontend application, we also need to implement the simplest possible protected frontend. Therefore, a Login component is needed to test whether a user is authenticated or not. The resulting state has to be stored in a frontend store, where we should use vuex as we're Vue users.

Pull Request Test Coverage Report for Build 164

24 of 28 (85.71%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.9%) to 88.235%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

backend/src/main/java/de/jonashackt/springbootvuejs/exception/UserNotFoundException.java
2
6
33.33%

Totals

Change from base Build 150:
-4.9%

Covered Lines:
45

Relevant Lines:
51

💛  - Coveralls


docs: Bring RELEASE.md up to date with current process

yarn-semantic-release was removed in #278. The commit message format also seems to have been long-abandoned and no longer relevant. This is an attempt to bring the documentation up to date with the current release and publishing process. It's intended as a combination of user manual and requirements.
I have introduced some new requirements that I hope are welcome:

Releases go through PRs (but are still merged and pushed locally)
Release commits and PR descriptions contain a list of changes
Explicit link to SemVer spec
Publishes are always made from a commit on LavaMoat/main

Ensuring that the gitHead field on the npm version can be mapped to a know source state. Critical for audits.

included shell snips should be useful for publishers who don't already have their own flow and tooling.

@weizman

https://github.com/LavaMoat/LavaMoat/pull/434#discussion_r1057038284
https://github.com/LavaMoat/LavaMoat/pull/434#discussion_r1057040656

Many sentences don't end with a ..

Should be all individual single-sentence bullet list, for consistency with existing style in README.md. I'm agnostic here and happy to change style, but if so we should change it in docs across the repository and address that in a separate PR?


Remove parameters in run method

Summary
Remove parameters in run method to align with https://github.com/Qiskit/qiskit-terra/pull/8684
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 64.598%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
3268

Relevant Lines:
5059

💛  - Coveralls

The CI failure looks related to this PR https://github.com/Qiskit/qiskit-terra/pull/8795


Bump identity governance version

Bump identity governance version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1023853693

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1023853693
Status: success


City Addition menu

Current Behavior:
There is no pre-selected city buttons to quickly chose frequent cities. Only history is shown once clicking in input.
Expected Behavior:
Create a code for user to select a searched city to be added as a city 'button' to quickly find data again, and also to remove the button.
Additionally, allow user to clear history (but not buttons)

Expected behavior completed.


Gift sats:While creating the gift, the Lightning account is also visible in the Account drop down.

While creating the gift, the Lightning account is also visible in the Account drop down.

And when I select Lightning account from drop down and try to send from it then it is giving me "Insufficient balance" error even though it has sufficient balance.

Verified this issue on dev app v2.0.70(441)


Datagrid theme makes the datagrid not visible

Hi I am using the latest nuget version 3.0.0-avalonia11-preview6.13-nightly (both the base package and the datagrid package)
I have a simple PCSC cardreader that pushes an card onto a datagrid, this datagrid sadly is invisible in this theme (dark or light)
Here is my app.axaml:

Here is the window:

Is this a known issue or do I need to do something in the app.axaml?

Hello, @HeadhunterXamd
If you add <StyleInclude Source="avares://Material.Avalonia.DataGrid/DataGrid.xaml" /> to your App.axaml, does this fix a problem?

@HeadhunterXamd does it works with 3.0.0-avalonia11-preview6.15-nightly?

I just had the same issue and upgraded to Material.Avalonia 3.0.0-avalonia11-preview6.17-nightly + Material.Avalonia.DataGrid 3.0.0-avalonia11-preview6.17-nightly.
That solved it for me and I don't have Fluent Theme installed anymore.


[BUG] Getting error on the latest commit

Im getting the following error on the latest commit: e3b0ace51db01e6fbecae489645b911a8f4b3441
packer.nvim: Error running config for nvim-lspconfig: ...packer/start/rust
-tools.nvim/lua/rust-tools/commands.lua:12: attempt to index field 'comman
ds' (a nil value)

Tried restoring rust-tools to ec6028323cc9cd37187eccb7ffdc5bab8c249d08 and it works

The same happens for me.

Should be fixed now lol

Let me know if its not because I don't want to switch back to 0.5.1 again for such  a small fix

Fixed for me as well. Thanks!


Fix TSQL upgrade script

Description

There were duplicate functions in TSQL upgrade script, fixed that
Added output verify file for upper-lower function in japanese collation

Authored-by: Anikait Agrawal<EMAIL_ADDRESS>Signed-off-by: Anikait Agrawal<EMAIL_ADDRESS>Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Memory tests -

Client tests -

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.503%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
42360

Relevant Lines:
57630

💛  - Coveralls


Small updates to thermal ir tutorial

These are some small changes to the thermal ir tutorial, not urgent. I can make a pr for these changes after the hackweek if that's preferred.

thanks @spestana - haven't forgotten about this, need to update some things related to caching to fix the CI checks and will plan to merge this in by the end of the week

@spestana could you please fetch the most recent 'main' branch and merge those updates in?
Also a few other requested fixes that I see from log output:
/home/jovyan/book/tutorials/thermal-ir/index.md:17: WARNING: 'myst' reference target not found: ./earthdata_api.py
/home/jovyan/book/tutorials/thermal-ir/thermal-ir-data-download.ipynb:30004: WARNING: 'myst' reference target not found: nsidc.org/

earthdata_api.py --> {download}`earthdata_api.py <./earthdata_api.py>`  Or [earthdata_api.py](https://github.com/snowex-hackweek/website/blob/main/book/tutorials/thermal-ir/earthdata_api.py)

In thermal-ir-data-download.ipynb [NSIDC](nsidc.org/) -->   https://nsidc.org

@spestana could you please fetch the most recent 'main' branch and merge those updates in?
Also a few other requested fixes that I see from log output:
/home/jovyan/book/tutorials/thermal-ir/index.md:17: WARNING: 'myst' reference target not found: ./earthdata_api.py
/home/jovyan/book/tutorials/thermal-ir/thermal-ir-data-download.ipynb:30004: WARNING: 'myst' reference target not found: nsidc.org/

1. In index.md

* [earthdata_api.py](./earthdata_api.py) --> `` {download}`earthdata_api.py <./earthdata_api.py>`  `` Or `[earthdata_api.py](https://github.com/snowex-hackweek/website/blob/main/book/tutorials/thermal-ir/earthdata_api.py)`

1. In thermal-ir-data-download.ipynb `[NSIDC](nsidc.org/) -->   https://nsidc.org`

Thanks! I think these markdown links are fixed now too.


For python add fmt off and format python comment

Pull requests:

https://github.com/senzing-garage/sdk-errors/pull/10
https://github.com/senzing-garage/sdk-errors/pull/11


feat(apps/prod/tekton/configs): implement step to wait for image delivery

Changes makes:

implement task wait-delivery-images
update the pipeline pingcap-release-ga

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Why is that some testing is doubled up?

See here
https://github.com/aivillage/llm_router/blob/1ec1051c546a5104f2040fb82b1688a45ca6caa4/tests/test_chat/test_mock.py#L63-L69
or here
https://github.com/aivillage/llm_router/blob/1ec1051c546a5104f2040fb82b1688a45ca6caa4/tests/test_chat/test_mock.py#L78-L85

Tests caching


Added a switch variable which allows it to disable dropout

When converting a model that has dropout it gets either ignored (when choosing test as a phase) or added constantly. However in many cases the user want to add/remove dropout on the fly, e.g. use dropout when training but then switch it off for validation/predictions.
With this PR I introduce a switch which gives the user the ability to explicitly switch on and off dropout even after the model is loaded. For that I use a placeholder which can be feed when running the model, e.g.
sess.run(prob, feed_dict={input: images, net.use_dropout: 0.0})
for switching off dropout (or 1.0 for using dropout). The placeholder has a default value of 1.0 which means that dropout is turned on, so the default behavior is not changing. I hope you also find this a useful addition to the network.

Thanks!


Support for SVG in CSS files

This is a great loader, but it shouldn't break when the svg file is loaded by an scss file. As in this example:
.foo {
   background-image: url(images/icon.svg);
}

Currently, these images are loaded as [object Object] strings.

I faced the same with image-size-loader and I solved it with a small hack
Would appreciate a PR if the same hack works for this.

Could also be fixed by separating SVG files used in JS and CSS into two different folders, and adjust the webpack config to only use react-svg-loader on SVG files in one of the folders...
test: /.svg-js(.*)\.svg$/,

@andersaloof  can you show more code about this implement? Then how can I only use file-laoder
for svg in scss, I tried /.svg-scss(.*)\.svg$/ but it doesn't work out.
Please help me out. I already spent over three days struggling with using svg in both jsx and scss

Why was this not fixed in 2.0.0... It's a huge issue.

This issued can be solved by using Webpacks Rule.oneOf and resourceQuery: https://webpack.js.org/configuration/module/#rule-oneof
By using this option in your webpack config, you can use react-svg-loader for JSX files, and another loader, say url-loader, in your CSS, Sass etc... files.

@P0lip I tried this.
I get:
ERROR in ./wwwroot/assets/arrow-down.svg
    Module parse failed: Unexpected token (1:0)
    You may need an appropriate loader to handle this file type.

css:
  .howItWorksItem:after {
    content: '';
    background: url(../../wwwroot/assets/arrow-down.svg);
  }

Is issuer only available in webpack 4?


Make sudo as an option

The commands in the code are now prefixed with sudo by default, which may introduce

security problems
users actually have permission to follow commands, but not a sudoer, causing tasks to fail. (For example, the user is in the docker group, but not a sudoer)

I feel that sudo should be included as an optional parameter -sudo or --root ? and only add sudo in front of the command after enabling the parameter.

CurveAdm v1.0 has support the sudo option, like curveadm deploy --sudo


[core] replace anonymous structs in netdiag.h

My proposition on #4758

I forget about the "types cannot be declared in anonymous unions" warning. I pushed commit with named union.


Admin user should be able to revoke authorized applications of other users

Simply admin user should be able to revoke access tokens issued for other users

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


API call fails in Vue + Node App

Describe the bug
Hi, I'm trying to create an app for Mac OS with Vue on frontend and Node on backend. I created a binary of my Node app using pkg npm package and have added it in externalBin also configured it in sidecar but the issue is that when I make an API call it gives below error.
"Failed to load resource: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection."
Platform and Versions (required):

Operating System - Mac OS, version 10.15.7 X64

Node.js environment
  Node.js - 12.22.2
  @tauri-apps/cli - 1.0.0-beta.3
  @tauri-apps/api - Not installed

Global packages
  npm - 6.14.13
  yarn - 1.22.10

Rust environment
  rustc - 1.53.0
  cargo - 1.53.0

App directory structure
/test
/dist
/.metadata
/target
/src-tauri-org
/node_modules
/server
/static
/scripts
/src-tauri
/dist_electron
/build
/.git
/.vscode
/electron
/src

App
  tauri.rs - 1.0.0-beta.4
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../dist/
  devPath - https://localhost:8080
  framework - React

Additional context
Add any other context about the problem here.
Stack Trace

You don't need to file an issue and start a discussion.

Adding plist to the project solves the issue.

Hi @NitinRamnani, I am new to Tauri and trying to convert the MERN stack web app to a desktop app. But I couldn't connect front end to backend in tauri.  Can you provide any resources to solve the problem?

@jayanthsaikiran - please visit our Discord and ask your question there in #help-triage. Without more insight into your exact situation, we can't help you. Also, please don't comment on closed issues - there is no guarantee you will get a response.


gf: Actions in templates ~ failing.

Hi,
I am doing a gf on the line
 <button class="btn btn-success icon-button ellipsis" {{action "newRisk"}}>

and getting an error:  can't find action 'newRisk'.
The template location: app/pods/home/route1/route1.1/template.hbs and the controller is in the same folder.
Experiencing the same with components. Component templates location: `app/pods/components/component-x/template.hbs1
BTW, gf: Components in templates ~ works perfectly fine.
Would appreciate if someone could debug this.

I'm sorry it took me so long to get around to debugging this.
I've pushed a commit that might fix your issue. It looks for the action in a file called controller.js or component.js, or route.js in the same directory as the template.hbs file. Could you try it out and let me know if it works?

No worries, took me quite a while to respond myself. Glad I could help in the end :).


gemma.cc:1322: Failed to load model weight

Hello, just fresh running the program after building for 8bit
./gemma \
--tokenizer tokenizer.spm \
--compressed_weights 2b-it-sfp.sbs \
--model 2b-it

and it output
Cached compressed weights does not exist yet (code 227), compressing weights and creating file: 2b-it-sfp.sbs.
Abort at ~/gemma.cpp/gemma.cc:1322: Failed to load model weights.
[1]    6581 abort      ./gemma --tokenizer tokenizer.spm --compressed_weights 2b-it-sfp.sbs --model

any idea what is wrong?

This appears to be an older version of the code :) Does it help to update to git HEAD? FYI we have just merged dev branch into main, so either is fine.

I have the same issue running from HEAD.
./gemma  --tokenizer /tmp/gemma_cpp_weights/tokenizer.spm --weights /tmp/gemma_cpp_weights/2b-pt-mqa.sbs --model 2b-pt
Cached compressed weights does not exist yet (code 104), compressing weights and creating file: /tmp/gemma_cpp_weights/2b-pt-mqa.sbs.
Abort at /usr/local/google/home/alankelly/dev/gemma.cpp/./gemma/gemma.cc:1394: Failed to load model weights.
Aborted

Hi @alankelly , the 'code' in the error message is a line number. Looks like the .sbs file has a size that does not match the size in the header. Might it be an incomplete download? Did you get the latest version of the weights from Kaggle?
A while back, there was an incompatible change to the tokenizer vocab, and weights had to be updated. I am not 100% sure all downloads on Kaggle were successfully updated. Maybe also try the IT instruction tuned version?

Nice, thanks for following up :)

Hi @alankelly Thank you for the confirmation on the resolved issues, Hence closing the issue.


Namespace not specified

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':android_x_storage'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file: /Users/john.doe/.pub-cache/hosted/pub.dev/android_x_storage-1.0.0/android/build.gradle. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

I think this is caused by the new android studio update (ladybug),
I will try to fix it ☺

the problem was fixed now, if it's still not working consider to reopen the issue.


[Bug] Cannot autoresize after atom.config.set("file-icons.revealTreeView", false);

@lexcast  Here's how to reproduce:

Install file-icons
Open dev console and run

atom.config.set("file-icons.revealTreeView", false);

Close tree-view, and restart atom
Open tree-view and you will see the :bug:

@ooJerryLeeoo It's safe to close this now. I'm still not sure what caused the error, but it doesn't really matter. =)
@lexcast No importa; lo siento. Todo bien.

@ooJerryLeeoo @Alhadis Thank you.


Lost Identity right after top up

Today i bought your services but your app stopped working immediately after that so i uninstalled it. So, I download that again and i want able to login into my account because i didn't have my back up key. The transaction was made today from my card I didnt make my backup code and delete the app, because the app bugged out.

Please help me restore my account

It's not something to help after topup the user will be warned to download the identity backup but the user just ignored and lost the funds.

Not in this case. The app was freezing after payment and the user restarted app. After doing so his identity automatically changed.
I understand if the user was already using the app and accidentally deleted his identity. However, he never even had the chance to download backup files..

"I bought your product but when i bought that i got black screen the app was crashing, so i was not able to make the backup. Then i reinstall that and when i open that again i had to buy that again. So i want refund, because i made nothing wrong your app just bugged me."


Add support for custom tags

Add a new --tag option to encrypt-ami and update-encrypted-ami.  This
allows the user to specify a custom tag that is set on every resource
created by encryption.  --tag may be specified multiple times, in order
to set multiple tags.
Get rid of ImageNameError.  Update the validation code to throw
ValidationError when validation of command-line options fails.  Move
ValidationError into a new validation module, to avoid circular
dependencies between aws_service and brkt_cli.

Nice, lgtm


Custom Operator Random Number Generator Support

Description
Add random number generator support for custom operator libraries.
Design
We pass from MXNet the initialized and seeded states, located on CPU and GPU, to custom library. So user could use those seeds to generate deterministic values from a given seed passed to MXNet. Basically this workflow:
mx.random.seed(128)
r1 = mx.nd.some_custom_random_op(data)
mx.random.seed(128)
r2 = mx.nd.some_custom_random_op(data)
assert (r1 == r2)
This PR is not
Let custom library generate exactly the same sequence of random numbers comparing to MXNet
Comments
This is a continuation of the custom operator project #15921 and #17270

Thanks for this @rondogency! this is going to be a great addition for customOps.
A couple suggestions on the PR description:
Add random number generator support for custom operators ~libraries~.
Custom ~library~ operators now can call MXNet random number generator to get random numbers through OpResource class in forward/backward computation.

Great. how are we testing this feature?

I think @rondogency's plan is to write a dropout operator

in the cmake, the line "target_compile_options(subgraph_lib PUBLIC -shared)" can be removed, as we added the library as shared already

@samskalicky resolved your comments, please take another look

@wkcn @eric-haibin-lin this PR is ready for review. I have to reimplement the workflow to get rid of some segfault error so the code is different from last time you reviewed

@sxjscience @yzhliu  I will appreciate if you can take a look at this PR and point out if any random number related use cases that need to be covered or tested

@samskalicky resolved all your comments

@mxnet-label-bot add [pr-awaiting-merge]

@mxnet-bot run ci [unix-gpu, centos-cpu]

@mxnet-bot run ci [unix-gpu]

@mxnet-bot run ci [unix-gpu]

@mxnet-bot run ci [unix-gpu]

@mxnet-bot run ci [unix-gpu, windows-gpu]


News141: additions

Per feedback from https://github.com/bitcoinops/bitcoinops.github.io/pull/533#pullrequestreview-619682192

Looks good. Thanks Mike!


[BUG_FIX] Watch for changes in the configsource implementations

Before, the WatchForChanges was not called, now we pass the same WatcherFunc down to the ConfigSources.
Signed-off-by: Bogdan Drutu<EMAIL_ADDRESS>

We've not moved the vault config source integration tests to our separate suite yet but it looks like fcb259b05302534ce6c58b8cb5cfda2c56187bac introduced a breaking change in its provider adoption:
internal/configsource/vaultconfigsource$ RUN_VAULT_DOCKER_TESTS=t go test -v -run TestVaultSessionForKV
=== RUN   TestVaultSessionForKV
    source_test.go:93:
        	Error Trace:	/home/rmfitzpatrick/work/splunk-otel-collector/internal/configsource/vaultconfigsource/source_test.go:93
        	Error:      	Received unexpected error:
        	            	unsupported type=json.Number for retrieved config
        	Test:       	TestVaultSessionForKV
--- FAIL: TestVaultSessionForKV (2.54s)


ISPN-15169 SIFS PMEM logs exception every file opening in dev

https://issues.redhat.com/browse/ISPN-15169

Replaying CI. I think it stopped because of yesterday's storage issue.


compile: optimize code in the encoding/binary package

The encoding/binary package uses portable bit operations to read and write integers.
Using the program:
package test

func readUint64BigEndian(b []byte) uint64 {
	_ = b[7] // bounds check hint to compiler; see golang.org/issue/14808

	return uint64(b[7]) | uint64(b[6])<<8 | uint64(b[5])<<16 | uint64(b[4])<<24 |
		uint64(b[3])<<32 | uint64(b[2])<<40 | uint64(b[1])<<48 | uint64(b[0])<<56
}

and building with:
GOAMD64=v3 go1.18 build -o test.o test.go

the resulting assembly is:
SUBQ $0x18, SP
MOVQ BP, 0x10(SP)
LEAQ 0x10(SP), BP
MOVQ AX, 0x20(SP)
CMPQ $0x7, BX
JBE 0x9ac
MOVBE 0(AX), AX
MOVQ 0x10(SP), BP
ADDQ $0x18, SP
RET
MOVL $0x7, AX
MOVQ BX, CX
CALL 0x9b9		[1:5]R_CALL:runtime.panicIndex
NOPL

The Zig compiler, with the same code and ReleaseSafe build mode, is able to generate the assembly:
movbe   rax, qword ptr [rdi]
ret

See https://godbolt.org/z/MPbE3P9j8.
Note that the movbe instruction was added in AMD64 v3 (https://en.wikipedia.org/wiki/X86-64).
Zig currently uses the LLVM backend, so I don't know if the cost/complexity of this optimization is high.

That zig code is not equivalent because you're passing a [8]u8, while the Go snippet uses a slice. This Go Function:
func readUint64BigEndian(b [8]byte) uint64 {
	return uint64(b[7]) | uint64(b[6])<<8 | uint64(b[5])<<16 | uint64(b[4])<<24 |
		uint64(b[3])<<32 | uint64(b[2])<<40 | uint64(b[1])<<48 | uint64(b[0])<<56
}

generates with GOAMD64=v3 go tool compile -S test.go:
	0x0000 00000 (test.go:5)	MOVBEQ	"".b+8(SP), AX
	0x0007 00007 (test.go:5)	RET

Which is the same as the LLVM output.

@ALTree, thank you for the clarification.
I did not notice the problem, since in Zig it is possible to convert a slice to an array; as an example:
var start: usize = 2;
var buf = [_]u8{ 0, 0, 0, 1, 2, 3, 4, 5, 6, 7, 8 };
var b = buf[start..]; // A slice since start is not a constant
var bytes = b[0..8]; // An array since the indices are constants

It should be possible(?) to implement this in Go, but it will break compatibility.

In the Go version that takes a slice we have to boundcheck it, but if you remove the instructions related to that, it's just a single MOVBEQ	(AX), AX again (but I could be missing something). Is there anything else the compiler should do?

I wrote this test code:
package test

import "encoding/binary"

func Parse(b []byte) uint64 {
	v := binary.BigEndian.Uint64(b[0:8])

	return v
}

func ParseUint64(b []byte, start, end int) uint64 {
	v := binary.BigEndian.Uint64(b[start:end])

	return v
}

func ParseUint64_2(b []byte, start, end int) uint64 {
	v := binary.BigEndian.Uint64(b[start:end][0:8])

	return v
}

The first and last functions (where slicing is done using constants), generate a single MOVBEQ  instruction for the  binary.BigEndian.Uint64 function, while the second function generates additional instructions.
I searched for real examples and found:
https://cs.opensource.google/go/x/net/+/27dd8689:http2/frame.go;l=764
The code can probably be improved with (not tested):
binary.BigEndian.Uint16(buf[i*6:][:2])

Zig, as a counter example, will report a compiler error so it is more easy to detect the problem.
NOTE:
The actual instruction I see is MOVBE, not MOVBEQ.
Also, for binary.BigEndian.UInt16, the Go compiler generates two instructions:
MOVZX 0(AX), AX
ROLW $0x8, AX

while the Zig compiler generates
movbe  ax,WORD PTR [rdi]

Is there a reason for not using MOVBE?

Is there a reason for not using MOVBE?

No particular reason, 16-bit versions just hasn't been implemented yet.


Added two additonal functions for Xml Writer

Hi Microsoft team,
Can you please add these two new functions for Xml Writer, for both BC16 and BC17?

Work for 16 and 17 pending, but in progress.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for submitting this issue. We will publish a fix for it in the next minor update for release 17.

Thanks for submitting this issue. We will publish a fix for it in the next minor update for release 16.


Virtual Box Setup gives "We're Sorry!"

Expected behavior
stops with errors after seconds
Actual behavior
Says needet to use VirtualBox - Setup. Then it runs to 99% says ""We're Sorry!" and stops with the erros bolow
Information about the Issue
Command failed: C:\Program Files\Docker Toolbox\docker-machine.exe -D create -d virtualbox --virtualbox-memory 2048 default,Docker Machine Version: 0.13.0, build 9ba6da9,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address <IP_ADDRESS>:52453,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(flag-lookup) Calling .GetMachineName,(flag-lookup) Calling .DriverName,(flag-lookup) Calling .GetCreateFlags,Found binary path at C:\Program Files\Docker Toolbox\docker-machine.exe,Launching plugin server for driver virtualbox,Plugin server listening at address <IP_ADDRESS>:52457,() Calling .GetVersion,Using API Version 1,() Calling .SetConfigRaw,() Calling .GetMachineName,(default) Calling .GetMachineName,(default) Calling .DriverName,(default) Calling .GetCreateFlags,(default) Calling .SetConfigFromFlags,(default) Calling .PreCreateCheck,(default) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | 5.2.6r120293,(default) DBG | },(default) DBG | STDERR:,(default) DBG | {,(default) DBG | },(default) DBG | COMMAND: wmic computersystem get hypervisorpresent,(default) DBG | STDOUT:,(default) DBG | {,(default) DBG | HypervisorPresent ,(default) DBG | TRUE ,(default) DBG | ,(default) DBG | },Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)",open C:\Users\Administrator.docker\machine\machines\default\default\Logs\VBox.log: Das System kann den angegebenen Pfad nicht finden.,notifying bugsnag: [Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)"],

I had a similar error. This error page should be improved:

The error messages are logically organized in lines; still, they are displayed as an unreadable blob.
To make them display nicer, replace ,(?! ) with ,\n.

Since this is an "unexpected error", there should be a "report this error" button.

The last line tells you exactly what the error is:
This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)


[#cleanup] remove unnecessary code in Interceptor

Codecov Report

Merging #6289 into master will increase coverage by 0.05%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #6289      +/-   ##
==========================================
+ Coverage   39.55%   39.61%   +0.05%
==========================================
  Files        3061     3061
  Lines       91415    91301     -114
  Branches    11845    11814      -31
==========================================
+ Hits        36163    36168       +5
+ Misses      52269    52148     -121
- Partials     2983     2985       +2

Impacted Files
Coverage Δ

...tor/SpanEventSimpleAroundInterceptorForPlugin.java
61.9% <ø> (ø)
:arrow_up:

...plate/interceptor/AsyncHttpRequestInterceptor.java
0% <0%> (ø)
:arrow_up:

...boss/interceptor/ContextInvocationInterceptor.java
0% <0%> (ø)
:arrow_up:

...son/interceptor/WriteValueAsStringInterceptor.java
0% <0%> (ø)
:arrow_up:

...sttemplate/interceptor/HttpRequestInterceptor.java
0% <0%> (ø)
:arrow_up:

...ugin/jackson/interceptor/ReadValueInterceptor.java
0% <0%> (ø)
:arrow_up:

...ptor/PreparedStatementExecuteQueryInterceptor.java
0% <0%> (ø)
:arrow_up:

...interceptor/FrontCacheGetFutureGetInterceptor.java
0% <0%> (ø)
:arrow_up:

...p/pinpoint/rpc/client/WriteFailFutureListener.java
56.25% <0%> (-18.75%)
:arrow_down:

...pc/server/LoggingServerMessageListenerFactory.java
90% <0%> (-10%)
:arrow_down:

... and 11 more

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 625a48d...866ef99. Read the comment docs.


Kiran_python_code

Kindly send a pull request after implementing all 31 algorithms on or before January 15th.
Thank you.


How can I grab the HTTP request/response between client and registry with Wireshark?

Hi~
I'm trying using the wireshark to grab the HTTP request/response between the client and registry, but it  looks a little strange.
My private registry runs in localhost:5000 without tls, and I try to push a images to it.
When I use wireshark, I try to listen to 'docker0' interface or the 'lo' with 'tcp.port eq 5000', the captured packets appear in protocol only tcp and ipa, but without http. In some ipa packets, there are some data looks like http protocol but it's partical.
This makes me confused, because according to my understanding, the data exchange between should be all using http protocol.
I want to ask why, and if it does't work, how can I analyze the data flow between the client and registry? Thank you!

@AngryHacker I think this was suggested to you earlier already: please use either the mailing list or the irc channel for general questions.
Please do NOT use the bugtracker for random questions.
Furthermore, this is way unrelated to the registry, or even to Docker.
Before trying to use a tool like WireShark, please start with:

reading the API documentation
looking at the logs (both docker and registry)

I fail to see why you would want wireshark here.
I'm closing this for these reasons.

Sorry. I will follow it next time. I didn't make clearly before.


DioError (DioError [DioErrorType.DEFAULT]: HttpException: , uri = http://xxxx.xxxx.xxx/xx/xx )

simulator will throw it.
the device is ok

same error for me ... Was founded a solution?


Documentation for building frameworks

If we don't provide this functionality through the Flutter tool, we might still want to add to the website the concrete steps to build a framework.
@jmagman has a guide on https://github.com/flutter/flutter/issues/36968#issuecomment-533357802.

Since we built flutter build ios-framework, we don't need this anymore


function neomake#Sh's second argument callback not work

ubuntu 16.04 vim 8.0 1-300
I tried to use function neomake#Sh to run external command
here is the example
function! AfterExit(job_status)
    echom "callback"
endfunction

 autocmd User NeomakeJobFinished call OnNeomakeFinished()

call neomake#Sh('touch test_file', function('AfterExit'))

test_file have been created successfully, but string "callback" not showing in :message

@tracyone
So it worked after all?

No.
I try to make a plugin base on neomake.
I found another way...
neomake-multiprocess

I fixed it anyway.. ;)
https://github.com/neomake/neomake/pull/1018


unnecessary error messages when deleting account

In HEDA, navigate to Contacts.
Create a new Contact "foo", leaving Account blank in order to have the system create a "foo Administrative account" for the Contact.
Navigate to "foo Administrative Account" and delete the account.  See this error:
Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here and any other related details.Something has gone wrong. Cannot read property 'childNodes' of null. Please try again.
Navigate to Contacts, see this error:
Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here and any other related details.Something has gone wrong. Cannot read property 'updateColumns' of undefined. Please try again.
Navigate to Accounts. Tab is empty as expected
Navigate to Contacts. Tab is empty as expected.

This only happens in Lightning Experience, and it's an error coming from the platform, not from the package.


Bootstrap RBAC Info into control plane

User story
As an admin, I want to be able to bootstrap my RBAC configuration so that on initial load I can manage my service.
Acceptance criteria

[ ] Configuration has a section for entering initial bootstrap of RBAC configuration
[ ] Identity provider, role, and role membership can be bootstrapped
[ ] Bootstrapping only occurs once
[ ] Changes to the bootstrap configuration is not persisted to the datastore

Moving work item tracking to Azure DevOps.


removed arbitrary player sample and player list text

player list may cause conflict when used behind a proxy like velocity

screw github
this was merged imma call it a day.


Mechanism to load JS projections into postgres at bootstrapping time

This is somewhat done already. IEventStore.Administration.LoadProjections()
Not sure how we want to do administration later. I'm leaving this open until the documentation effort flushes this out.

Replaced by #321


[BUG] Login Submittion routes to wrong url

Describe the bug
I have my cibisafe running on https://chibisafe.vbucksgenerator.zip and the API Server on https://chibiserver.vbucksgenerator.zip
When i try to login while specting network traffic (Browser Dev Tools) i see that a post request with the provided credentials is being made to https://chibisafe.vbucksgenerator.zip/api/auth/login instead of chibiserver.
the logs of the api server show following:
[11:32:48.513] INFO (143): Running Chibisafe v6.4.2
[11:32:48.966] WARN (143): Found route without URL or METHOD - dist/routes/admin            /files/Unzip.js
[11:32:49.267] WARN (143): Found route without URL or METHOD - dist/routes/album            /ZipAlbum.js
[11:32:49.665] INFO (143): Server listening at http://<IP_ADDRESS>:8000
[11:32:50.590] INFO (143): No updates available

Compose file:
version: '3.0'

services:
  chibisafe:
    container_name: chibisafe
    image: chibisafe/chibisafe:latest
    environment:
      - BASE_API_URL=https://chibiserver.vbucksgenerator.zip
    expose:
      - 8001
    networks:
      - revproxy
    restart: unless-stopped

  chibisafe_server:
    container_name: chibisafe_server
    image: chibisafe/chibisafe-server:latest
    volumes:
      - chibisafe_database:/app/database:rw
      - chibisafe_uploads:/app/uploads:rw
      - chibisafe_logs:/app/logs:rw
    expose:
      - 8000
    networks:
      - revproxy
    restart: unless-stopped

  caddy-chibsafe:
    container_name: caddy-chibisafe
    image: caddy:2-alpine
    volumes:
      - /docker/chibisafe_caddyfile/Caddyfile:/etc/caddy/Caddyfile:ro
      - chibisafe_uploads:/app/uploads:ro
    networks:
      - revproxy
    ports:
      - 24424:80
    environment:
      - BASE_URL=":80"
    restart: unless-stopped

volumes:
  chibisafe_database:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /docker/chibisafe_database
  chibisafe_uploads:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /docker/chibisafe_uploads
  chibisafe_logs:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /docker/chibisafe_logs

networks:
  revproxy:
    external: true

To Reproduce
Steps to reproduce the behavior:

Setup chbisafe with the docker compose file provided above
Point the VPS IP to a proxied cloudflare subdomain
In Nginx Proxy Manager, add the cloudflare letsencrypt ssl certificates and proxyhosts
Configure the enviroment variable baseurl of chibisafe to use chibiserver (as shown in the composefile above)
try to login while having devtools open.
see typerror: r is not defined and 404 as api response statuscode

Expected behavior
I expected everything to work flawlessly
Screenshots

Additional context
nothing

As I mentioned in the previous issue you opened (https://github.com/chibisafe/chibisafe/issues/673#issuecomment-2202312926), do not modify the docker compose file.
chibisafe doesn't support a different domain/subdomain for the api, so the whole point on the Caddyfile we supply you with, is to consolidate both services under the port 24424.
What you need to do, is reverse proxy port 24424 from another container, or from your host, and point it to your domain.

As I mentioned in the previous issue you opened (#673 (comment)), do not modify the docker compose file. chibisafe doesn't support a different domain/subdomain for the api, so the whole point on the Caddyfile we supply you with, is to consolidate both services under the port 24424.
What you need to do, is reverse proxy port 24424 from another container, or from your host, and point it to your domain.

It is generally a good practice to not expose ports on the public vps ip, which is the reason that i run all my containers inside a docker network and then use nginx proxy manager to connect those services to my domain.
I tried binding caddy-chibsafe with port 24424 to the chibsafe.vbucksgenerator.zip domain as well which caused the error DNS record point to a prohibited IP

It is generally a good practice to not expose ports on the public vps ip,
For this you could change the caddy port in the docker-compose.yml file so that it's only accesible from the host itself and not exposed, without using a network. Change

ports:
  - 24424:80

to
ports:
  - <IP_ADDRESS>:24424:80

Now for the 2nd problem, it remains. You cannot have the chibisafe frontend and backend in a separate domain. They need to be consolidated with caddy, which is exactly the purpose of our docker compose stack.

It is generally a good practice to not expose ports on the public vps ip,
For this you could change the caddy port in the docker-compose.yml file so that it's only accesible from the host itself and not exposed, without using a network. Change

ports:
  - 24424:80

to
ports:
  - <IP_ADDRESS>:24424:80

Now for the 2nd problem, it remains. You cannot have the chibisafe frontend and backend in a separate domain. They need to be consolidated with caddy, which is exactly the purpose of our docker compose stack.

This updated port configuration now causes following error:

Error response from daemon: driver failed programming external connectivity on e                             ndpoint caddy-chibisafe (a4b1bd8810117f39a2884afb0faf46d4554e8846dfe92924f15f256                             11a014b51): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:24424: bind: ca                             nnot assign requested address

You have an issue here that is most likely outside of chibisafe. Something is going on with your host or docker installation, or maybe all the other stuff you added to the docker-compose.yml file.
So, I'll ask you one last time if you can try with the default file we provide and see if it works first, and if it does, then start modifying it.
I can't help you if we don't debug properly.

It is generally a good practice to not expose ports on the public vps ip,
For this you could change the caddy port in the docker-compose.yml file so that it's only accesible from the host itself and not exposed, without using a network. Change

ports:
  - 24424:80

to
ports:
  - <IP_ADDRESS>:24424:80

Now for the 2nd problem, it remains. You cannot have the chibisafe frontend and backend in a separate domain. They need to be consolidated with caddy, which is exactly the purpose of our docker compose stack.

This updated port configuration now causes following error:
Error response from daemon: driver failed programming external connectivity on endpoint caddy-chibisafe (a4b1bd8810117f39a2884afb0faf46d4554e8846dfe92924f15f25611a014b51): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:24424: bind: cannot assign requested address

It's <IP_ADDRESS>, not <IP_ADDRESS>

<IP_ADDRESS>

Ok that makes sense. i could start the container now without any error.
It may be useful to provide my caddyfile:
# chibisafe/Caddyfile
{$BASE_URL} {
	route {
		file_server * {
				root /app/uploads
				pass_thru
		}

		@api path /api/*
		reverse_proxy @api http://chibisafe_server {
				header_up Host {http.reverse_proxy.upstream.hostport}
				header_up X-Real-IP {http.request.header.X-Real-IP}
		}

		@docs path /docs*
		reverse_proxy @docs http://chibisafe_server {
				header_up Host {http.reverse_proxy.upstream.hostport}
				header_up X-Real-IP {http.request.header.X-Real-IP}
		}

		reverse_proxy http://chibisafe {
				header_up Host {http.reverse_proxy.upstream.hostport}
				header_up X-Real-IP {http.request.header.X-Real-IP}
		}
	}
}

I removed the ports behind it because when doing curl with port, connection would timeout while doing curl without the port i get the response: error code: 1003 which is an error indicating that the request need to be done though a domain name.
Now i understand that you said it's not possible to use external domains, other docker containers i have in my compose file worked fine with my modifications so maybe it's possible to provide an option to make it work for my usecase?
thanks in advance.
Regards,
FuckingToasters

Don't remove the ports. What args are you using with curl? For testing, it should be curl <IP_ADDRESS>:24424 and curl <IP_ADDRESS>:24424/api/health

curl <IP_ADDRESS>:24424/api/health

The healthcheck seem to work internally now but once i try to login on the website, i still see the 404 error and the typeerror.
I've also tried to connect <IP_ADDRESS> to the domain which caused a Bad Gateway Error, additionally i tried <IP_ADDRESS> for testing purposes which resulted in the same Bad Gateway error.


Host info through client API

Is there a way to retrieve system details such as hostname and GPU type through the wandb.Api for a Run object? I couldn't find it on the docs.

Hi Carlo, thanks for asking about this. We have these metrics in the backend but they're not exposed via the API right now. This will be made available as part of our CLI roadmap, but will be a month or so out.

Quick "fix" or workaround while the official feature is still not here yet: set wandb.run.tags = ["<HOSTNAME_HERE>"] in your script (in my case I used os.environ["SLURM_JOB_NODELIST"] for that placeholder) and then get it with run.tags[0] when getting runs data through wandb API :)

In the past year we've majorly reworked the CLI and UI for Weights & Biases. We're closing issues older than 6 months. Please comment to reopen.


Add AES( Advanced Encryption Standard ) and DES ( Data Encryption Standard )

Kindly add AES( Advanced Encryption Standard ) and DES ( Data Encryption Standard )

Hi! Could you please provide a simple spec or a code example for the API you need?

Sorry, I have no idea about this. I just thought it should use cryptography concept like AES or DES


Helm Chart for easier installation

What problem are you facing?
When installing and configuring the provider you have to apply 3 yaml files:

runtime-config.yaml
provider.yaml
provider-config.yaml

There are few specifics that are not straight forward:

There are not enough examples how to configure deploymentruntimeconfig, api documentation is too brief and hence insufficient
One has to know that the Provider should reference the deploymentruntimeconfig name
You cannot apply all 3 yaml files at once because providerconfig.aws.upbound.io/v1beta1 API is set by the Provider, hence the providerconfig has to to be applied only after the provider status is health
For installing the families, you have parametrize the files and use a tool to loop trough the list of families

Uninstalling (kubectl delete) all the yaml files that were applied leaves the upbound-provider-family-aws Provider and pod behind.
It would be useful to be able to generate configurations for each family separately - provide different number of pods, set different resources and limits.
And providing IRSA or podidentity recommended aws policies per family.

How could Official AWS Provider help solve your problem?

Create a helm chart for the provider, with elaborate documentation in a values.yaml file.

There are not enough examples how to configure deploymentruntimeconfig, api documentation is too brief and hence insufficient

It might be worth raising a specific documentation PR at https://github.com/crossplane/docs for this - or better yet, opening a PR to improve the documentation.

As we deploy providers using a custom helm chart I'd really rather see something provided by the official team rather than pushing this off on the user to try and figure out. @negz Fixing the documentation doesn't fix the fundamental flaw of the runtimeConfig, I just wanted to add a nodeSelector, so I start off just adding
    spec:
      deploymentTemplate:
        spec:
          template:
            spec:
              nodeSelector:
                kubernetes.io/os: linux
                kubernetes.io/arch: amd64

NOPE. That won't work, it errors out saying I need to have the selector, ok cool, I can do that.
    spec:
     deploymentTemplate:
       spec:
         selector:
           matchLabels:
             pkg.crossplane.io/provider: provider-aws-ec2
         template:
           spec:
             nodeSelector:
               kubernetes.io/os: linux
               kubernetes.io/arch: amd64

NOPE. That won't work either. It errors out saying I need spec.deploymentTemplate.spec.template.spec.containers and at this point I've just given up because I've wasted too much time on this and just will find something else that works better. Why would I want to do all this instead of having it do a merge against the defaults. So obviously this isn't ready for anyone to use or it was just designed to fail. I looked at the design doc and the bugs, arguing against sane defaults is like arguing we should give every baby a bowie knife, just crazy.
I'm sure you've seen other CRDs like the alert manager or prometheus ones which allow you to easily define almost all aspects of the deployment without having to copy the entire deployment and repeat the code multiple times. Anyone who has worked with CRDs in literally every other open source tool is going to expect that field to just be a merge of the options set, and the defaults for the provider.
I genuinely like Crossplane, (I've implemented it at the last 4 places I've worked because I like it so much) but this is driving me crazy and I can't believe the team said "hey here's how everyone else does it so it's easy and intuitive to the users  but let's not do that", the limitation of making this useful and intuitive to the users isn't a concern to you?
What's worse is that you did this correctly in the serviceAccountTemplate.
      serviceAccountTemplate:
        metadata:
          annotations:
            well-designed: "true"

I don't have to completely spell out every section of the service account, just add the annotation. So please fix this with sane defaults.

We are using Crossplane for all our AWS deployment and the cluster where crossplane is deployed is having resource crunch. We would like to implement HPA on the deployment for upbound provider. To implement HPA, I would need to implement requests and limit for the upbound pod. The problem is, as mentioned above, there is no way to change the deployment configuration. Even if I want to edit the deployment, crossplane reverts the change back to the original configuration.
I think the users should have the flexibility to change the configs of the standard k8s resources created by crossplane as a part of Proider's child resources.

@achalk14 You can already do that - https://docs.crossplane.io/v1.16/concepts/providers/#runtime-configuration


Documentation request - AMQP permissions & setup required

Hi folks,
Can we get the permissions and setup for AMQP documented please? AMQP can have specific roles, ACLs and RBAC set for users to access queues, and a central/shared AMQP instance used by more than just one iRODS system/account/zone abd or other non-iRODS things will want to lock down the access to least privilege.
cheers
John

AMQP is just the protocol - I think the authentication/configuration will be slightly different per broker (ActiveMQ or RabbitMQ).

Sure, but the sample only has an anonymous account, and no documentation about how to setup access to a remote server.
I have been doing;
        {
            "instance_name": "irods_rule_engine_plugin-audit_amqp-instance",
            "plugin_name": "irods_rule_engine_plugin-audit_amqp",
            "plugin_specific_configuration" : {
                 "amqp_location" : "<user>:<password>@<host>:<port>",
                 "amqp_options" : "",
                 "amqp_topic" : "audit_messages_<zone>",
                 "pep_regex_to_match" : ""
                 }
            },

I see the queue being created;
$ sudo rabbitmqctl list_queues
Timeout: 60.0 seconds ...
Listing queues for vhost / ...
name    messages
audit_messages  0
audit_messages_sanger1_dev      0

Also, its worth noting that with RabbitMQ it needs
sudo rabbitmq-plugins enable rabbitmq_amqp1_0
We have a /etc/logstash/conf.d/rabbitmq.conf configured;
tee /etc/logstash/conf.d/rabbitmq.conf << EOFinput {
  rabbitmq {
    queue => "audit_messages"
    host => "localhost"
    codec => "plain"
  }
}

filter {
  mutate {
    gsub => [ "message", ".*__BEGIN_JSON__", "" ]
    gsub => [ "message", "__END_JSON__.*", "" ]
    gsub => [ "message", '\\"', '"' ]
  }
  json {
    source => "message"
  }
}

output {
  elasticsearch {
    hosts => ["elasticsearch:19200"]
    index => "irods-audit-plugin-test"
    user => "irods"
    password => "<password>"
  }
}

It would be good to know if we can use the same queue and/or elasticsearch index for multiple zones/servers or if different ones should be used (and if so per zone, per server etc)? - basically are there any hard coded assumptions in the plugin on how many servers/queues etc it will use


Combine "Pull" and "Reset local (forced pull)"

Current issues:

"pull" automatically imports all objects that are changed only remotely (but not locally). There is no option to select which objects should be pulled.
"pull" ignores all objects that exist only locally (but not remotely). There is no option to delete the local objects. However, "reset local" allows you to select if objects should be deleted.
"pull" and "reset local" let you select objects if they are changed on both sides or have been deleted locally.
"reset local" has a user confirmation popup, "pull" does not

Proposal:
Combine both features into "pull" and show one selection popup that lists all objects with a diff. The popup shall contain the following columns:

checkbox
object type
object name
current local state (same as in repo view)
current remote state (same as in repo view)
comment

The comment shall describe what happens if the object is selected and imported (plus a corresponding icon):

"update local object" (selected by default)
"delete local object" (not selected)

If the user selects objects to be deleted that exist only locally (so there's no remote backup), then the user shall confirm the deletion in an additional popup.

Tagging #413.
I like the proposal very much, if for no other reason than because it provides rationale for doing the fairly extensive changes needed IMO to enable "selective pull" :)
By "show one selection popup that lists all objects with a diff", did you mean that the popup should by displayed always, @mbtools? Another possibility were to let the "Pull" proceed with the default selection, and leave the selection popup to "Selective Pull", which could replace "force Pull" in the Advanced menu. The main reason I'm asking is: "selective Pull" would also need to include objects in the status "XA" (objects not existing locally) in the popup...
To enable optional deletion during pull were IMO fairly straightforward: starting point would be "moving" the deletion logic from ZCL_ABAPGIT_SERVICES_GIT->RESET( ) into  ZCL_ABAPGIT_SERVICES_REPO->GUI_DESERIALISE( ). There the popup could be merged with the two already there (overwrite and package overwrite). Because of "package overwrite" the local package would also need to appear on the popup.
Side question: is there any particular reason ZCL_ABAPGIT_POPUPS->POPUP_TO_SELECT_FROM_LIST( ) does not enable user to search and filter the list contents..? Asking because those would seem like obvious things to have, SALV has the functionality, but its not available on the UI (simply because of the choice of PF-STATUS, I suspect)...
It would IMO be nice to have two additional functions on the popup: select/deselect dependencies, but that may be taking it too far...

I like the idea of keeping "pull" as is but replacing "force pull" with "selective pull". I'm thinking now that it's should not be a popup but a page like "staging" where we list all objects with diffs and let the user select what to do. Similar to "stage commit", the "selective pull" could be followed by a confirmation page that shows the selected actions for the user to confirm.
We could build this apart from existing features and later decide if the old "reset local" is still required (probably not). It would be easier to add new features like "select/deselect dependencies" as well.
PS: Feel free to do a PR for the popup.

ref #3705


WIP - Revise and expand key performance indicators metrics beyond requests counter and meter

Overview
A key performance indicator (KPI) can be useful not only for measuring the performance of a server but also for building application-specific health checks using the KPI.
Existing ("basic") KPI metrics and implementation
Previously, in any app including metrics/metrics, Helidon has published two KPI metrics whenever the app includes the module metrics/metrics:

counter - Counter of the total number of requests received by the server
meter - Meter (rate) for above count.

The full metric names are the routing name for the routing (if any) plus request. so typically users see requests.count and requests.meter.
Recall that a Meter reports  an overall count, mean rate, and rates over the previous 1, 5, and 15-minute intervals.
These were created in MetricsSupport#configureVendorMetrics and a handler lambda declared in that same method would update the metrics before invoking request.next().
New ("extended") KPI metrics
The extended metrics are disabled by default, enabled by configuration or builder methods.

inFlight - ConcurrentGauge of requests actively being processed at a given moment
load - Meter of inFlight
longRunning -Meter -  requests which take longer than a configurable threshold to complete their processing
deferred - Meter - received requests were not processed immediately

Some requests (for example but not limited to Jersey) might be deferred--received by Helidon but then delayed for some reason (e.g, queued due to a shortage of available threads) before actually being processed. This means there can be a difference between when Helidon receives a request and when it starts processing the request.
Similarly, some requests (again, for example but not limited to Jersey) might complete their work asynchronously, after the user code has invoked request.next() and, therefore, separate from when the MetricsSupport handler's call to request.next() returns.
Some of the new KPI metrics require action after as well as before each request is handled and processed.
These complexities in behavior affect how Helidon should manage the KPI metrics, with the result that the code changes are a little more more extensive and complicated than might be expected at first glance.
Design
Introduce two abstractions:

A KPI metrics-related Context which tracks the key events in a request's life cycle that are relevant to KPI metrics
A KPI Metrics interface which encapsulates whether the basic or extended KPI metrics are set up

Make some small changes in the current request workflow:

The existing microprofile/server ServerCdiExtension class places an instance of the KPI Context into the request's context store.
The existing webserver/jersey JerseySupport class,  just before it submits the request to Jersey for processing, retrieves the KPI Context and, if found, reports to it that request processing is starting.
The existing MetricsSupport class, in its existing KPI-related handler:

retrieves the KPI Context, or, if there is none present, creates one;
obtains the correct impl of the Metrics abstraction mentioned above;
conveys the Metrics object to the KPI Context;
invokes methods on the KPI Context to report the handling and processing of the request.

The basic or extended KPI metrics are registered in the vendor registry when MetricsSupport instantiates the Metrics abstraction.
Changed components
webserver/webserver

New interface KeyPerformanceIndicatorSupport - defines the KPI behavior through nested interfaces

Metrics- abstracts the creation and collection of original (simple) and new (extended) KPI metrics
Context - abstracts the stages in a request's life cycle that are relevant to KPI metrics

Methods invoked when a request is received, work started, work completed
Static factory method

DeferrableRequestContext - sub-interface of Context

Adds a method invoked when processing actually begins on a deferrable request
Static factory method

New package-private class KeyPerformanceIndicatorContextImpls - impls for the above Context interfaces.

The specific type of Context needed for a request varies from request to request.
Callers of the Context factory methods always know which type they need.
webserver/jersey

Existing JerseySupport class now, just before starting the processing of the request, retrieves the KPI DeferrableRequestContext from the request Context and invokes requestProcessingStarted.

JerseySupport always invokes the DeferrableRequestContext if it's present. If metrics/metrics is not on the class or module path, the DeferrableRequestContext#requestProcessingStarted invocation done here acts as a no-op.
metrics/metrics

New interface KeyPerformanceIndicatorMetricsSettings
A POJO which holds all the configurable settings related to KPI metrics, currently:

whether the extended KPI metrics should be used, and
what threshold defines a "long-running" request

A buildable object which encapsulates the KPI metrics settings (whether extended metrics are enabled and the threshold for long-running requests). The builder is used as a "sub-builder" for MetricsSupport.

KeyPerformanceIndicatorMetricsSettingsImpl - impl for above

KeyPerformanceIndicatorMetricsImpls

Basic and extended implementations of the KPI Metrics abstraction
A factory method for the above

MetricsSupport

Enhance Builder and constructor to incorporate KPI metrics config settings
In configureVendorMetrics

Gets the correct instance of Metrics via the KeyPerformanceIndicatorMetricsImpls factory method
In the existing metrics-updating handler in configureVendorMetrics:

Retrieves the KPI Context from the request Context or creates a suitable one
Invokes requestHandlingStarted, requestProcessingCompleted, and requestHandlingCompleted from appropriate points. This handler cannot invoke requestProcessingStarted because the request's processing might be deferred by a handler later in the chain.

microprofile/metrics
Revise and add tests to check the extended KPI metrics.
microprofile/server
ServerCdiExtension now adds a new handler to the handler chain. The handler adds a new DeferrableRequestContext to each app's handler chain in a position earlier than the handler added by MetricsSupport.
This means:

The handler added by MetricsSupport will find that Context and use it, rather than creating and using a non-extended one.
JerseySupport will also find that DeferrableRequestContext and use it to track when the processing of the request begins.

examples/metrics/kpi
New example app showing config and explicit set-up of extended KPI metrics.
docs
Updates to the SE and MP metrics guides, involving refactoring duplicated text into a new common file.
Other notes
Non-Jersey apps with deferred requests
Users can write their own non-Jersey apps which defer processing of requests. To work correctly with the enhanced KPI support, such apps would need to build the handler chains for the relevant routes as JerseySupport does:

Inserting an early handler which adds a DeferrableRequestContext to the request's Context (so MetricsSupport will use that KPI Context when it updates the KPI metrics), and
During request processing, retrieving that context and invoking its requestProcessingStarted() method at the appropriate moment.

Note that if such an app does not take these steps, nothing fails. The KPI metrics will not accurately reflect deferred requests; it will seem as if all requests are processed immediately upon receipt.
SE apps using Jersey
Although we do not promote it (and coming changes in other technologies might invalidate this use case), developers can currently use JerseySupport in SE apps. Such apps can benefit from the KPI metrics improvements.
To do so, such apps, like ServerCdiExtension, must add a handler to each routing that should participate in extended KPI metrics. That handler must add a new DeferrableRequestContext to the request's context store. The application must add that handler earlier in the handler chain than it registers the MetricsSupport instance as a service.

Closed because another PR supersedes this one.


Grid Filters - Workplan Filters on all Grids

we need the same functionality from the Workplan grid on ALL grids across the System.

(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

@jadmsaadaot to estimate


Display bug in date range

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/wowchemy/wowchemy-hugo-themes/issues?q=is%3Aissue
[X] This issue is not a question, feature request, or anything other than a bug report directly related to Wowchemy. Please post those things on Discord: https://discord.gg/z8wNYzb

Description
Recently, I saw that when I update my website (Hugo + wowchemy-latest, hosted on gitlab) date ranges are not displayed correctly, as if the hugo parser was working twice on the produced html. Here is the description of the bug.
If for a specific "event/" page, I write
date: '2023-10-22'
date_end: '2023-11-04'

in the header of index.md, then, instead of displaying
 Oct 22, 2023 — Nov 4, 2023

in the compiled html page (automatically compiled with CI/CD in gitlab), it instead renders
 Oct 22, 2023 — Nov 4, 2023

The html source explains this since it is
 Oct 22, 2023 &mdash; Nov 4, 2023

as if Hugo/Wowchemy decided that "&" had to be displayed as it.
My website is not new, and previously I hadn't that bug.
Reproduction Link
https://laurentjacques.gitlab.io/event/visiting-professor-in-ens-lyon-france/
Steps to Reproduce
see above
Expected Result
see above
Actual Result
see above
What Hugo Module versions does your site use?
no available in gitlab
What operating system(s) are you seeing the problem on?
Linux
What browser(s) are you seeing the problem on?
Firefox
Which Wowchemy template are you using?
Academic
What version of Hugo are you using?
hugo v0.120.3+extended

v0.120 is a brand new version of Hugo with breaking changes. Have you tried the compatible version of Hugo, v0.119.0?


[NetAppFiles] Update azure-mgmt-netapp version to 2.0.0

Description

Update azure-mgmt-netapp dependency to version 2.0.0 and additions from that version added.
Migration of Python SDK from Track1 to Track2 changes.

Version 2.0.0 of Python SDK includes track 1 to track 2 migration along with additions from netapp API version 2020-12-01. User experience is not affected from the migration changes.
Migration changes are:

LRO operations are renamed to begin_xxx_xxx, for example in track1, the name is create_or_update; while in track2, the name is begin_create_or_update. This is only method name, not operation name.
In track2, SDK parameters are not flattened, so we need pass object parameter instead of flattened parameters to SDK. So more custom commands have been added instead of generic.
In track2, use ClientAuthenticationError, HttpResponseError, ResourceExistsError and ResourceNotFoundError instead of CloudError.
Fix some tests due to changes in track2.

Other changes:

Tests added and updated and new recordings made for all the tests.
Help was updated according to API changes.
Backup operations set to preview since it is only in private preview.
Backup tests marked to be skipped due to instability in CBS

Testing Guide

History Notes

[NetAppFiles] az netappfiles account ad add: Optional parameter added named allow-local-ldap-users
[NetAppFiles] az netappfiles volume create: Optional parameter added named ldap-enabled
[NetAppFiles] az netappfiles volume backup status show: Operation added

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

NetAppFiles


Win/lose

Updated joystick
Added win and lose dialog boxes that currently display based on points variable
When you click finish, it will bring you back to the main menu
When you click play again, the activity is reloaded

Resolves #78

I have nothing to add. Looks great! 💪🏻

One thing though. I think you forgot to initialize setupJoystick() :)

I have nothing to add. Looks great! 💪🏻

One thing though. I think you forgot to initialize setupJoystick() :)

I think you're right. Should be fixed now!


Most big & small fixes since June.

Sorry to batch this all up in one, but this is a gathering of most/all of the tweaks to TermKit since June. It's mostly minor bug fixes, along with merged additions by floby, albertz, kbrock, Fabian Brockmann and outbounder.

There's no way I'm pulling in a bunch of random commits from all over the place. This needs cleanly described issues, clean code, and isolated changes.

Fair enough, and my apologies; I've been pulling stuff together to make it easier to keep up with people's contributions, but I haven't been particularly critical of the code.


[Question] Error building clock example over the web runtime

I have copied&pasted the clock example into a binary crate with the following Cargo manifest.
[package]
name = "clock"
version = "0.1.0"
edition = "2021"

[dependencies]
iced = { git = "https://github.com/iced-rs/iced.git", features = ["canvas", "tokio", "debug"] }
iced_web = { git = "https://github.com/iced-rs/iced.git" }
chrono = "0.4"

I built with cargo build --bin clock --target wasm32-unknown-unknown following the guide. However the compiler gave an error:
error[E0432]: unresolved imports `iced::canvas`, `iced::canvas`, `iced::time`
 --> clock/src/main.rs:3:5
  |
3 |     canvas::{self, Cache, Canvas, Cursor, Geometry, LineCap, Path, Stroke},
  |     ^^^^^^   ^^^^ no `canvas` in the root
  |     |
  |     could not find `canvas` in `iced`
4 |     executor, time, Application, Color, Command, Container, Element, Length,
  |               ^^^^ no `time` in the root

For more information about this error, try `rustc --explain E0432`.
error: could not compile `clock` due to previous error

Am I doing something wrong? Or is canvas not supported over wasm yet?

Or is canvas not supported over wasm yet?

That is correct. Canvas is not supported on Wasm yet!


feat: upgrade k8s to v.1.29

Description of the Change
Update k8s to ver. 1.29 in aws&azure hosting_provider modules, update kubectl version to 1.29.4, increase disk size for aws managed nodes

Please generate updated tf docs as they still contain 1.27 as default version for the cluster.

updated docs for cloud_azure&cloud_aws modules


findOne failing in a particular scenario

I have a scenario where I'm dynamically trying to create and update documents while looping through an array of objects.
In this scenario, findOne is working fine the first time it is called but next it will always return the document from the previous call.
I've tried to make a very simple example available here: http://plnkr.co/edit/fD6vnv
I did not investigate much but it seems that the issue is within the calculateRange method.
Thanks

I'm sorry if this sounds stupid but i would have thought you would do this:
var result = brandCollection.findOne({'brand':car.brand}); instead of
var result = brandCollection.findOne({'id':car.brand});, as far as i can see ids are completely different from brands.
Again sorry if i misunderstood the issue.

I'm sorry, I agree that 'id' could be misleading (it was just meant for the example).
I've updated the plunker and replaced 'id' by 'brand' as you suggested.
Now, as you can see in the log, after we successfully retrieve a document with findOne, the next calls will not always return the objects we were looking for.

Ok I'll look into this
/cc @obeliskos

I think its a bug he found.
loki.js, line 1583 should be :
return t[index.values[seg[0]];
I will update later today or you can try updating and see if that fixes it for you.  If that's not it let me know.
Problem exists in edge case where doing findOne on indexed column.
Thanks for reporting.

Thanks for your prompt reply.
This seems to have fix both the issue in the plunker and in my personal use case.
Again thanks for your hard work to both of you !

@obeliskos thanks a lot for squashing that bug. And thanks @Badisi for the kind words. Closing this.


Error when trying to update sensors when device isn't testing

My replacement cartridge is late due to some shipping issues on Sutro's end, so my device has stopped testing.
I can manually reload the integration and get the latest temp, but the other sensors are failing because they're getting back null.
I'd like to at least keep the temp going in these cases. Can some safety null checks be put in place to allow things to update when others are having issues?
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:600
integration: Sensor (documentation, issues)
First occurred: June 10, 2024 at 2:59:19 PM (2 occurrences)
Last logged: 7:28:44 AM

Error adding entity sensor.sutro_alkalinity_sensor for domain sensor with platform sutro
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 600, in _async_add_entities
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 914, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1355, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
    state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1061, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 543, in state
    value = self.native_value
            ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/sutro/sensor.py", line 112, in native_value
    return float(self.coordinator.data["me"]["pool"]["latestReading"]["alkalinity"])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: float() argument must be a string or a real number, not 'NoneType'

Another very similar one
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/sutro/sensor.py:112
integration: Sutro (documentation, issues)
First occurred: June 10, 2024 at 3:29:19 PM (33 occurrences)
Last logged: 7:58:44 AM

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 255, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 411, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 165, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 491, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1000, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
    state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1061, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 543, in state
    value = self.native_value
            ^^^^^^^^^^^^^^^^^
  File "/config/custom_components/sutro/sensor.py", line 112, in native_value
    return float(self.coordinator.data["me"]["pool"]["latestReading"]["alkalinity"])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: float() argument must be a string or a real number, not 'NoneType'

Addressed in v1.0.0-beta.0:
https://github.com/ydogandjiev/hass-sutro/releases/tag/v1.0.0-beta.0
@Intecpsp, please consider updating to v1.0.0-beta.0 and confirming that you no longer see the issue and everyhing works as expected.


Custom icon.jpg is not being used

When I have a custom icon.jpg present in the root, It will show the default homebrew icon with the exclamation point.
The log states it is using the custom icon.jpg. I used an icon from a different homebrew of mine to make sure it has the proper dimensions.

I tried your icon at it works. turns out I used 255x255 instead of 256x256

Working on an archive org browser to download roms. Yeah will join soon :) first release will be soon


formatting x-enum-varnames in an array

Describe the bug
Is it possible for x-enum-varnames to be formatted so that they are contained within the items object?
To Reproduce
Steps to reproduce the behavior:
  type Frequency struct {
  Frequency    string    `json:"frequency" swaggertype:"array,integer" enums:"0,1,2" x-enum-varnames="Daily,Weekly,Monthly"`
  }

Expected behavior
                "frequency": {
                    "type": "array",
                    "items": {
                        "type": "integer",
                        "enum": [
                            0,
                            1,
                            2
                        ],
                        "x-enum-varname": [
                            "Daily",
                            "Weekly",
                            "Monthly"
                        ]
                    },
                }

Actual behavior
                "frequency": {
                    "type": "array",
                    "items": {
                        "type": "integer",
                        "enum": [
                            0,
                            1,
                            2
                        ],
                    },
                    "x-enum-varname": [
                        "Daily",
                        "Weekly",
                        "Monthly"
                    ]
                }

I guess this is actually more of a question about how to define the location of an extension. In this case possibly changing the varnames tag so that it reflects where they should sit? But that would be a pretty breaking change.

Or possible a solution similar to this https://github.com/swaggo/swag/pull/927 ?

Closing as resolved in https://github.com/swaggo/swag/pull/927


When selecting NDT and OOKLA results, each should have a different color

Clicking on both types of test just layer on points of the same color. We should use different colors for the different tests, or only enable one at a time.
With just NDT selected:

With NDT and OOKLA selected:

After adding a second test device labelled "wifi", we should also differentiate the colors for wired/wireless devices.
When viewing these charts, it would also be helpful to show the device name or metadata in the hover information, or provide a way to filter to select only one device for a location.

Plan for MVP:

@critzo will provide colors
will update color for ndt & ookla tests so they're different in the graph

NDT: red
Ookla: orange


[Macros] Update executable plugin sandbox profile to prohibit file-read

Except for dylibs.

@swift-ci Please smoke test


Gracefully close server on SIGTERM

I always find myself adding the following snippet to close the server when the process receives a request to close:
process.on('SIGTERM', function() {
    server.close(function() {
        process.exit();
    });
});

Thoughts on adding this by default? :thought_balloon:

Looks like if you're using bin/micro this is already done for you https://github.com/zeit/micro/blob/8.0.4/bin/micro.js#L96-L98

Thanks for pointing that out however I'm using this module programmatically, wonder why it's in the CLI code though.

I am not sure if it's a behaviour which would be okay for library to cause. What if you catch sigterm in your app that uses it and do something else like respawn? Signals are process global. And libraries are not. So I think it belongs in the CLI
Zeit team, thoughts?


[1.22.0] [FEAT] Make sealant production easier

Is your feature request related to a problem? Please describe.
The production of super sealant to be able to use the rocket silo is very convoluted. Since the mod forbids unbarreling heavy oil (which there are seas of on Fulgora), you need to do coal synthesis->simple coal liquefaction with sulfuric acid to get a bit of heavy oil->advanced coal liquefaction and then get some steam somewhere in space which means only one thing: nuclear.
We use fusion ships, so that is a bit jarring. Any way to make that a little less convoluted? This means a dedicated platform just to do this.
Describe the solution you'd like
Allow us to make sealant anywhere.

I think the intention is add another reason to use space platforms as a factory as the only other use case for a factory in space is space science. (I get that there are other things you can do with platforms but for progression in the game, they can be ignored. i.e. legendary coal production in space is not needed to complete the game)
Maraxsis is unlockable at the same time as aquilo but not after aquilo, meaning that for a fresh playthrough a typical player may not have fusion power yet.
Maraxsis is also on the same level as aquilo, meaning it already requires planetary logistics to complete. so bringing over some nuclear fuel cells doesn't seem to be out of the question.
Some things that were discussed on discord:

Unbanning heat towers in space -> would break the meta for power generation in space, why use anything other than a heat tower?
Add uranium to Maraxsis/Trench -> would remove the uniqueness of Nauvis (biolabs have already been unbanned for other planets on this mod)

I guess what we need to ask is: Is this additional puzzle fun and is it difficult enough to justify the rewards of maraxsis? How does it compare to the fun and difficulty of aquilo? (i.e. why should i choose to go to maraxsis first instead of aquilo?)

We managed to hack one of our workhorses to produce some sealant. Was it fun? Hrm.
I think I would rather see some unique materials from Maraxsis to produce the sealant locally, instead of modifying or limiting vanilla recipes.

The heavy oil embargo has been lifted!
You can now unbarrel in space.
Additionally I have added a new recipe that allows to recycle extra petrol. So if you decide to make it in space anyway, you are rewarded a bit.

Getting around the heavy oil restriction was a little annoying, but not too bad since you can jumpstart it with simple coal liquefaction and imported calcite and sulfuric acid.
The real thing that's annoying with sealant is how it forces you into a nuclear fission reactor. I was honestly considering using one of the mods that adds a steam recipe in space just so that I could use other power sources, most notably the new salt reactor, which looks really cool and interesting, but I'm having trouble finding a niche for it beyond ships going between Nauvis and Maraxsis anyways due to heating towers being as OP as they are. (Infinite free energy anywhere except space, for comparable space as nuclear, with fusion's main benefit being the much smaller footprint at the cost of more complex interplanetary logistics).
Unbanning the heating tower in space would be a terrible decision if you ask me because it's already so OP as it is that it needs to leave some niche open to other power sources. I'd much rather have a new way to make steam in space that's usable for coal liquefaction and sealant, but is too cool to realistically use for power.

Or have a separate recipe that doesn't use steam, but requires something from Maraxsis, like brine or something. So the first time you have the trouble of making sealant with a reactor, but then afterwards you are rewarded with a better recipe once you can launch the rocket.


Links to FAQ articles from CWA app no longer work

Where to find the issue

https://www.coronawarn.app/en/faq/
https://www.coronawarn.app/de/faq/

Describe the issue
A regression has been introduced with the new FAQ layout.
FAQ articles accessed from links within the CWA Android app no longer show the FAQ article.
Steps to reproduce
Device: Pixel 3a Emulator
Android version: API 31 / Android 12
CWA Version: 2.19.2
Default apps: Browser app: Chrome

Open CWA
Scroll down to "7-Day Incidence" statistics tile
Tap "i" icon
In "Key Figures" / "Explanation of Statistics" scroll down to "You'll find answers to frequently asked questions on our FAQ page:

Tap on FAQ in the above sentence
The address bar shows "coronawarn.app/en/faq/results/#further_details" however the browser is scrolled down to the footer

Scroll back up and note that the requested article is not visible

This is reproducible also with other FAQ links from the app.
It is reproducible with browsers:

Google Chrome
Mozilla Firefox
Samsung Internet

Additional information
The expected result of tapping a link to an FAQ article in the CWA is that the article should be displayed in a browser window on the mobile device, expanded and scrollable so that it is immediately available for reading.
Different links produce different error conditions different from the expected result:

Footer shown
Article not expanded (see also https://github.com/corona-warn-app/cwa-website/issues/2584)
No article shown (only the section headers are shown)

The following table contains a list of anchors which are always accessible in CWA Android. There are other links which are only shown based on certain conditions like red card or in combination with an error.

Link
Access through
Result

#where_can_i_get_tested
Manage Your Tests > Find Testing Center
Article not expanded

#notification_settings
Settings > Notifications
Footer shown

#eu_dcc
Scan a certificate which is already stored
No article shown

#eu_dcc_check
Certificates > "i" with stored certificate
Article not expanded

#error_log
App Information > Error Reports
Article not expanded

#further_details
Statistic tile > "I"
Footer shown

#interoperability_countries
App Information > Data Privacy, Section 7 (end)
Article not expanded

#android_location
Android 6 - 10, disable location > LOCATION SERVICES DEACTIVATED
Article not expanded

Confirm same issue for iOS:

@Ein-Tim
Thank you very much for checking on iOS as well! I am finding even more problems as I start using the new FAQ!

I am finding even more problems as I start using the new FAQ!

So do I, I'm currently checking whether other links also cause problems (e.g. if I shared them on Twitter).

I identified another problem: https://github.com/corona-warn-app/cwa-website/issues/2582

This seems to be a CSS Bug. I can reproduce the error with an iPhone XR, but with an iPad Air all FAQ entries in this section are displayed and so the link brings me to the expected anchor.
So far i was not able to find the cause. Maybe its a @media rule problem, but my CSS is rusty, so i'm not sure.

@Crystalskulls
It's linked to the width of the browser window. It fails in narrow browsers windows.
On an Android device if I turn the device on its side (so it's in landscape orientation) before tapping on the FAQ link, then the FAQ article appears correctly.

In the meantime I've logged #2579 and #2580 which may be related.

Additional information
The expected result of tapping a link to an FAQ article in the CWA is that the article should be displayed in a browser window on the mobile device, expanded and scrollable so that it is immediately available for reading.
Different links produce different error conditions different from the expected result:

Footer shown
Article not expanded (see also https://github.com/corona-warn-app/cwa-website/issues/2584)
No article shown (only the section headers are shown)

The following table contains a list of anchors which are always accessible in CWA Android. There are other links which are only shown based on certain conditions like red card or in combination with an error. (These are not listed here.)

Link
Access through
Result

#where_can_i_get_tested
Manage Your Tests > Find Testing Center
Article not expanded

#notification_settings
Settings > Notifications
Footer shown

#eu_dcc
Scan a certificate which is already stored
No article shown

#eu_dcc_check
Certificates > "i" with stored certificate
Article not expanded

#error_log
App Information > Error Reports
Article not expanded

#further_details
Statistic tile > "I"
Footer shown

#interoperability_countries
App Information > Data Privacy, Section 7 (end)
Article not expanded

#android_location
Android 6 - 10, disable location > LOCATION SERVICES DEACTIVATED
Article not expanded

See also enhancement request https://github.com/corona-warn-app/cwa-website/issues/2585.

I wonder if it would make sense to revert the FAQ redesign until these problems are addressed. I'm uncertain if a step that drastically needs to be taken, but I would say yes as nearly all links from the CWA app itself to the FAQs are broken.
Any options on this?

@Ein-Tim

I wonder if it would make sense to revert the FAQ redesign until these problems are addressed.

I think it is a significant problem for the app.
Whether the PR should be reverted depends on how long it is expected to take to fix it. It may be a simple fix. We don't know until the web developers take a look at it.

More bugs spotted:

#2591
#2592
#2593

If the team does not resolve most of the issues in the next week, I suggest to revert to the first version of the FAQs.

The missing #eu_dcc on the website is also listed in https://github.com/corona-warn-app/cwa-website/issues/2582.

Thanks for your input, the developers will start working on the faq issues starting today.
Internal Tracking ID: EXPOSUREAPP-12448

#eu_dcc is fixed through PR https://github.com/corona-warn-app/cwa-website/pull/2598.

I'm not seeing the problem with only the footer being displayed any more.
The remaining problem seems to be only that the articles are not opened expanded and ready for reading.

@MikeMcC399 Articles not opened/expanded was a CSP issue that was fixed with a recent PR https://github.com/corona-warn-app/cwa-website/pull/2606. Should be working now.

@svengabr

Articles not opened/expanded was a CSP issue that was fixed with a recent PR https://github.com/corona-warn-app/cwa-website/pull/2606. Should be working now.

This isn't fixed for a mobile device which is what this issue is all about.
Open https://www.coronawarn.app/en/faq/#where_can_i_get_tested in Google Chrome Desktop in full-screen, then the article is displayed.
Open Google Chrome Desktop, Press F12 and select mobile device then open  https://www.coronawarn.app/en/faq/#where_can_i_get_tested shows "Where can I get tested?" not expanded:

I confirmed also using the Corona-Warn-App (2.19.2) to access the article and it is not opened there either.


improve kubectl config handling and UX

Previously to
https://github.com/aws-controllers-k8s/test-infra/pull/222, when running make kind-test, there was some helpful output that set up the kubectl config so that developers could easily connect to the KinD cluster housing test pods. In addition, prior to the mentioned PR222, when scripts would run commands in a single shell as opposed to individual Bash functions, calling things like export KUBECONFIG would set the environment variable into the calling script's shell context. Calling export KUBECONFIG from within a Bash function does not do this, at least not on Linux, which means that in order to kubectl to the KinD cluster now, I need to actually execute export KUBECONFIG after running make kind-test, which is annoying.
This patch modifies the scripts/kind.sh:setup_kind_cluster Bash function to create a kubecontext file inside the KinD cluster's build directory ($ROOTDIR/build/clusters/$clustername/kubecontext). This file contains exports for the KUBECONFIG environment variable, properly set to the KinD cluster's configuration. It also calls kubectl config use-context to set the current shell's kubectl context and use the ack-system namespace by default. Finally, the kubecontext file has a helper function called controller_pod that accepts the name of the service and returns the Pod name for that controller.
This kubecontext file is shown in a block when we run make kind-test now:
2022-12-22T15:06:20-05:00 [INFO] Creating kubecontext file /home/jaypipes/go/src/github.com/aws-controllers-k8s/test-infra/scripts/../build/clusters/ack-test-7e1553e1/kubecontext ...

*******************************************
* To execute kubectl in the test context: *
*******************************************

source /home/jaypipes/go/src/github.com/aws-controllers-k8s/test-infra/scripts/../build/clusters/ack-test-7e1553e1/kubecontext

And sourcing the file in question sets the kubectl context appropriately and allows the developer to quickly access the controller pods and logs under test:
[jaypipes@thelio test-infra]$ source /home/jaypipes/go/src/github.com/aws-controllers-k8s/test-infra/scripts/../build/clusters/ack-test-7e1553e1/kubecontext
Switched to context "kind-ack-test-7e1553e1".
Context "kind-ack-test-7e1553e1" modified.
[jaypipes@thelio test-infra]$ k logs $(controller_pod s3) --tail 1
2022-12-22T20:10:55.733Z	DEBUG	ackrt	< r.deleteResource	{"account": "586748657421", "role": "", "region": "us-east-1", "kind": "Bucket", "namespace": "default", "name": "s3-bucket-vv97pk7q2imrxi", "generation": 16}
[jaypipes@thelio test-infra]$ k describe pods/$(controller_pod)
Name:         ack-s3-controller-dc744f569-74nz2
Namespace:    ack-system
Priority:     0
Node:         ack-test-7e1553e1-worker/<IP_ADDRESS>
Start Time:   Thu, 22 Dec 2022 15:07:13 -0500
Labels:       control-plane=controller
              pod-template-hash=dc744f569
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/ack-s3-controller-dc744f569
Containers:
  controller:
    Container ID:  containerd://e026ab4d9d9203e99fafba7702ad5067b011761272bae7784e7ea61fc49b0bd6
    Image:         aws-controllers-k8s:s3-v0.1.5-2-g2bbd673-dirty
    Image ID:      sha256:6a3e07cf23dac5a2755a1dd2ebfa57ccd29fe2147460205b666dc8604048b75a
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      ./bin/controller
    Args:
      --aws-region
      $(AWS_REGION)
      --aws-endpoint-url
      $(AWS_ENDPOINT_URL)
      --enable-development-logging
      $(ACK_ENABLE_DEVELOPMENT_LOGGING)
      --log-level
      $(ACK_LOG_LEVEL)
      --resource-tags
      $(ACK_RESOURCE_TAGS)
      --watch-namespace
      $(ACK_WATCH_NAMESPACE)
    State:          Running
      Started:      Thu, 22 Dec 2022 15:07:14 -0500
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     100m
      memory:  300Mi
    Requests:
      cpu:     100m
      memory:  200Mi
    Environment:
      ACK_SYSTEM_NAMESPACE:            ack-system (v1:metadata.namespace)
      AWS_REGION:                      us-east-1
      AWS_ENDPOINT_URL:
      ACK_WATCH_NAMESPACE:
      ACK_ENABLE_DEVELOPMENT_LOGGING:  true
      ACK_LOG_LEVEL:                   debug
      ACK_RESOURCE_TAGS:               services.k8s.aws/controller-version=%CONTROLLER_SERVICE%-%CONTROLLER_VERSION%,services.k8s.aws/namespace=%K8S_NAMESPACE%
...
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p7pn5 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  kube-api-access-p7pn5:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  25m   default-scheduler  Successfully assigned ack-system/ack-s3-controller-dc744f569-74nz2 to ack-test-7e1553e1-worker
  Normal  Pulled     25m   kubelet            Container image "aws-controllers-k8s:s3-v0.1.5-2-g2bbd673-dirty" already present on machine
  Normal  Created    25m   kubelet            Created container controller
  Normal  Started    25m   kubelet            Started container controller

Signed-off-by: Jay Pipes<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

The jsonpath expression that @RedbackThomson suggested isn't working.. need to figure out something else.

The jsonpath expression that @RedbackThomson suggested isn't working.. need to figure out something else.

We don't have labels on controller deployment manifests, yet

@RedbackThomson OK, fixed. Now uses a jq query to handle the metadata name regex/lookup. Works a charm.