[Deploy Blocker Fix] Scan - "Unhold" option appears in report details page of scanning expense

Details

Corrects the conditional for displaying the Hold PromotedActionsBar action when a receipt is still scanning.
Fixed Issues

$ https://github.com/Expensify/App/issues/44195
PROPOSAL:
Tests

Go to workspace chat
Submit two scan expenses
Go to transaction thread of either one of the scan expenses
Click on the chat header
Make sure the hold action does not appear before it finishes scanning the receipt

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/88325488/5df04d52-a815-4ed9-98aa-054932fe71bc

MacOS: Desktop
https://github.com/Expensify/App/assets/88325488/2e134a8f-0ee5-4bad-8c5d-320b818907c5

@hoangzinh do you have time to review & test this PR soon? (since it fixes a deploy blocker)

Thanks y'all! I'll get this CP'd 👍  (i fixed the title too)

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Looks like this should have made it to staging, since the following CP deployed successfully - https://github.com/Expensify/App/actions/runs/9646233943

Looking good in staging!!

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.0.1-19 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Is this lib still necessary?

... now that chai has deep.contain()

I believe it is, since deepInclude only works from the first level (see https://www.chaijs.com/api/assert/#method_deepinclude):
const subset = {
	a: 'b',
	e: {
                // missing "foo": "bar"
		baz: {qux: 'quux'},
	}
};
const obj = {
	a: 'b',
	c: 'd',
	e: {
		foo: "bar",
		baz: {qux: "quux"},
	}
};

// PASSES
expect(obj).to.containSubset(subset);

// FAILS, as obj.e does not contain "foo": "bar".
expect(obj).deep.contain(subset);

Another feature not offered by chai, AFAIK, is the ability to provide an asserting function at any level.
Test that an empty string key is present, do not care about the value:
    assert.containSubset(control.BBCI, {
      axes: { distro: { '': () => true } }
    });

Or even a more complex scenario with a nested assertion:
    assert.containSubset(control.BBCI.stages, {
      gcb_stage: {
        gcb: (x: unknown[]) => {
          assert.strictEqual(2, x.length);
          return true; } } });


HTTPS not working in Linux AppImage

While the Handshake Latest AppImage (v0.0.3) on Zorin 16 (Ubuntu 20.04) the proxy works to resolve domains, but even with the certificate installed in firefox and my PC's trust store, TLS doesn't work

An addition:
TLS works on https://proofofconcept/, but not https://home.johnnywu/

johnnywu is not a signed zone, has no DS record in the root zone and therefore can not be secure. Likely his web server isn't even configured for https


Fix no namespace issue

CtmsContext class is not declared in a namespace. Please fix that.

Fixed with issue#5


implement char handling

fixes #30

@oli-obk Actually, did you put the char stuff on top of another PR? Where are the overflow commits from?

yea I did, they are from #28

@oli-obk Can you rebase this so only the relevant commits show up?

rebased and addressed comments

Thanks!


[SUPPORT] Hudi partitions not dropped by Hive sync after insert_overwrite_table operation

Describe the problem you faced
After running an insert to overwrite a Hudi table inplace using insert_overwrite_table, partitions which no longer exist in the new input data are not removed by the Hive Sync. This causes some query engines to fail until the old partitions are manually removed (e.g. AWS Athena).
This is on Hudi 0.12.1, but I'm fairly sure this issue still exists on 0.13.0 - this change: https://github.com/apache/hudi/pull/6662 fixes this behaviour for delete_partition operations, but doesn't add any handling for insert_overwrite_table.
I'd be happy to be proven otherwise if this is fixed in 0.13.0 - I don't have an environment to easily test this without working out how to upgrade on EMR without a release.
To Reproduce
Steps to reproduce the behavior:

Create a new Hudi table using input data with two partitions, e.g. partition_col=1, partition_col=2
Insert into the table using the operation hoodie.datasource.write.operation=insert_overwrite_table with input data containing 1/2 of the original partitions, e.g. only partition_col=2
Run HiveSyncTool or similar (doesn't work with Spark writer sync or HiveSyncTool)
Check the Hive partitions. Both partitions still exist

Expected behavior
I'd expect the partition which was not inserted to be removed, e.g. only partition_col=2 exists, partition_col=1 is deleted.
Environment Description

Hudi version : 0.12.1

Spark version : 3.3.1

Hive version : AWS Glue

Hadoop version :

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

Additional context
Running on EMR 0.6.9

Thanks for the feedback, guess you are right, this should be supported

Is there no further text on this question? Do you have any plans to fix it in which version? Thanks!

Has this problem been solved? @Limess

cc @codope guess this should have been fixed? https://github.com/apache/hudi/pull/6662

Yes this was fixed in 0.13.0

@codope ：hello,this issue still exists in version 0.14, why was it closed?

@codope :As stated by the Issue, the problem is a necessary occurrence. The version we are currently using is 0.14.
@Limess :Have you not encountered this problem again? May I ask how was it avoided?Thanks!

@zhaobangcai The full context is that the issue was fixed but in order to fix, the archived timeline was also being read. This caused too high sync latency. Hence, the fix was reverted. Generally, reading archived timeline is an anti-pattern in Hudi, and we are optimizing this by implemeting LSM timeline in 1.0.0. That said, I think we did fix the timeline loading in https://github.com/apache/hudi/commit/ab61f61df9686793406300c0018924a119b02855 which I believe is in 0.14. Can you please share a script/test case to reproduce the issue with all configs that you used in your env? I am going to reopen the issue based on your comment and debug further once you provide the script/test case. Thanks.

@codope :As stated by the Issue, the problem is a necessary occurrence. The version we are currently using is 0.14. @Limess :Have you not encountered this problem again? May I ask how was it avoided?Thanks!

We never pursued this and are still on 0.13.0 for now, so I can't verify either way, sorry!


Add documentation with some examples for the MultiBrowser feature

Please use the attached image as screenshot.

/rebase

/rebase


Set default time

I currently using wickedpicker. I need to set the default time to two wickedpicker control when a user perform the button click operation. The timepickers.wickedpicker('time', 1) returns the time, but it wont provide any method to set the time.
Could you please tell me, how I can achieve the same?

There's is no simple way to set the time after initialisation.   I've altered the latest version to provide this functionality.
var myPicker = $('.timepicker').wickedpicker(options);

// set time to 2pm
myPicker.wickedpicker('setTime', 0, "14:00"); // 0 is the index of the timepicker. Use 0 if only one is present

Code can be found here: https://stackoverflow.com/a/45367908/1544886


报错

Traceback (most recent call last):
File "run.py", line 3, in
from init import select_ticket_info
File "/root/12306/init/select_ticket_info.py", line 13, in
from config.AutoSynchroTime import autoSynchroTime
ImportError: No module named AutoSynchroTime

拉今天的代码，昨天的代码漏提交了


TLI 101.b -- Link up API for ml_model for multiple models to Dashboard 2

Description:
This pull request introduces functionality to allow users to upload machine learning models via the Dashboard 2 interface. The backend will analyze the uploaded models and return the corresponding output for further visualization.
Additionally, error handling has been implemented to ensure that users are informed if they upload unsupported or incorrect file formats.
Key Changes:
Model Upload: Users can now upload machine learning models through the Dashboard 2 interface.
Model Analysis: Once the model is uploaded, the backend will analyze the model and return the relevant output.
Error Handling: Proper error handling is in place to notify the user if an unsupported or incorrect model file is uploaded.
Acceptance Criteria:
[] Dashboard 2 should be fully functional with proper integration of graph displays showing model analysis.
[] Error handling should be implemented to guide the user when they upload incorrect files.
Testing Notes:
Upload valid model files to ensure that the backend performs the correct analysis and returns the expected results.
Try uploading invalid or incorrect files to verify that appropriate error messages are displayed.

Looks good! @tvirat 's implementation of the background for dashboard2 isnt here though? did you not pull?

Looks good! @tvirat 's implementation of the background for dashboard2 isnt here though? did you not pull?

He hasn't pushed it yet as there are some changes to be made in Dashboard 1


Split NuGet CLI reference into multiple pages, one each for respective commands

This page: https://github.com/NuGet/docs.microsoft.com-nuget/blob/live/docs/Tools/nuget-exe-CLI-Reference.md
seems too long and difficult to navigate. We should have a getting started flow with nuget commands and then cover each command to its own page.

Completed, see https://docs.microsoft.com/en-us/nuget/tools/nuget-exe-cli-reference


add support for map nested in struct

Mappings nested in structs are not generated with additional properties. If a field is of a MapType, add the field with additional properties. If needed add the key and value type to the scheme.
Relation issue
https://github.com/swaggo/swag/issues/517

Codecov Report

Merging #521 into master will decrease coverage by 2.26%.
The diff coverage is 36.11%.

@@            Coverage Diff             @@
##           master     #521      +/-   ##
==========================================
- Coverage   86.78%   84.51%   -2.27%
==========================================
  Files           7        7
  Lines        1536     1608      +72
==========================================
+ Hits         1333     1359      +26
- Misses        119      161      +42
- Partials       84       88       +4

Impacted Files
Coverage Δ

parser.go
78.57% <36.11%> (-3.54%)
:arrow_down:

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 b09d3f5...d60d4f0. Read the comment docs.

I added a FooBarMap struct to the api in composition test. With view-covered I see that the tests the covers the added code. Except for when the map is required or the parsing of the value fails.
If that doesn't suffice, can you indicate which part should further tested and where to add it?


Typographical error on OLS landing page

Weekly emails
[ ] Send email to mentees
[ ] Send email to speakers
Cohort call video preparation
[ ] Download from Zoom cloud recordings
[ ] Upload to Otter.ai (will need a few minutes to process)
[ ] Upload to the OLS YouTube account
[ ] Create a front page slide for the video - templates are available in Google Drive
[ ] Make sure the YouTube video is added to the current cohort playlist
[ ] Correct Otter.ai transcripts (make sure to use uploaded video, not the original transcript, as the timings won't match the video)
[ ] Download corrected transcript as a .srt file from Otter
[ ] Upload it to the YouTube video
[ ] Post a link to the recording in the OLS Slack! 🙌
Website (in schedule in _data folder)
[ ] Add link to recording
Add talks

[ ] Add link to slide deck
[ ] Add person detail to people.yaml if needed

I do not understand what is the error here

And what is the error?

"Applications for OLS-7 will open in end 2022". I think we can modify the sentence ma'am. "Sign up to our low traffic news list to hear when the next cohort applications open". I also think we should modify the second sentence ma'am.  I think it should be "to get update on the next cohort application" I'm sorry for stressing you

"OLS-7 will open in end 2022". I think we should modify the sentence ma'am.
Secondly, "sign up to our low-traffic news list to hear when next cohort
applications open". I think we should modify the second sentence too
ma'am.
On Wed, Oct 12, 2022, 1:43 PM Bérénice Batut @.***>
wrote:

And what is the error?
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/issues/454#issuecomment-1276112330,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2WVJWEAKOPZTZIZWRLUGQDWC2W6LANCNFSM6AAAAAARDFJ6SU
.
You are receiving this because you authored the thread.Message ID:
<open-life-science/open-life-science.github.io/issues/454/1276112330@
github.com>

"OLS-7 will open in end 2022". I think we should modify the sentence ma'am.

How should it be modified do you think?

"Sign up to our low traffic news list to hear when the next cohort applications open". I also think we should modify the second sentence ma'am. I think it should be "to get update on the next cohort application"

Sounds good. Please make the change :)

Got it, thanks!
On Wed, Oct 12, 2022, 1:51 PM Bérénice Batut @.***>
wrote:

Assigned #454
https://github.com/open-life-science/open-life-science.github.io/issues/454
to @Esyteck https://github.com/Esyteck.
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/issues/454#event-7571581707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2WVJWA6B7G4OTA64WZNIYLWC2X5JANCNFSM6AAAAAARDFJ6SU
.
You are receiving this because you were assigned.Message ID:
<open-life-science/open-life-science.github.
@.***>

Hi ma'am. Greetings from this end. After thoroughly going through the repo,
I discovered that the content to that paragraph is hidden and I do not have
access to it.
On Wed, Oct 12, 2022, 1:52 PM Esther Okoli @.***> wrote:

Got it, thanks!
On Wed, Oct 12, 2022, 1:51 PM Bérénice Batut @.***>
wrote:

Assigned #454
https://github.com/open-life-science/open-life-science.github.io/issues/454
to @Esyteck https://github.com/Esyteck.
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/issues/454#event-7571581707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2WVJWA6B7G4OTA64WZNIYLWC2X5JANCNFSM6AAAAAARDFJ6SU
.
You are receiving this because you were assigned.Message ID:
<open-life-science/open-life-science.github.
@.***>

The content is here: https://github.com/open-life-science/open-life-science.github.io/blob/main/index.md#applications

Hi ma'am please I humbly request for the source code so that I can have
access. Thanks
On Thu, Oct 13, 2022, 6:26 AM Esther Okoli @.***> wrote:

Hi ma'am. Greetings from this end. After thoroughly going through the
repo, I discovered that the content to that paragraph is hidden and I do
not have access to it.
On Wed, Oct 12, 2022, 1:52 PM Esther Okoli @.***>
wrote:

Got it, thanks!
On Wed, Oct 12, 2022, 1:51 PM Bérénice Batut @.***>
wrote:

Assigned #454
https://github.com/open-life-science/open-life-science.github.io/issues/454
to @Esyteck https://github.com/Esyteck.
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/issues/454#event-7571581707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2WVJWA6B7G4OTA64WZNIYLWC2X5JANCNFSM6AAAAAARDFJ6SU
.
You are receiving this because you were assigned.Message ID:
<open-life-science/open-life-science.github.
@.***>

I gave the link to it in my previous comment

I've fixed it. Waiting for the review. Thanks.
I hope I'm not bothering you too much?  Please Forgive my disturbance.
Hahahahaha
On Thu, Oct 13, 2022, 8:04 AM Bérénice Batut @.***>
wrote:

I gave the link to it in my previous comment
—
Reply to this email directly, view it on GitHub
https://github.com/open-life-science/open-life-science.github.io/issues/454#issuecomment-1277125306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2WVJWAJQ5HIFBAMXX6ZD7DWC6X7RANCNFSM6AAAAAARDFJ6SU
.
You are receiving this because you were mentioned.Message ID:
<open-life-science/open-life-science.github.io/issues/454/1277125306@
github.com>

I will close this as completed.


[modify][voice] bot protection

Coverage increased (+2.8%) to 77.281% when pulling 2d222da9f77c0902e1b0e9e8e989e98b7e1411b0 on feature/voice-bot-prevention into f4fe64859e26db3103e09098556d103d8e85f2a9 on master.


🐛 Failed to lint json from stdin.

Environment information
CLI:
  Version:                      1.9.2
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-kitty"
  JS_RUNTIME_VERSION:           "v22.9.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.8.3" (In fact, i use pnpm 9.11.0)

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?

open your terminal.

mkdir demo && cd demo
pnpm init
pnpm i -D @biomejs/biome

# no error
npx biome lint package.json

# get "The contents aren't fixed. Use the `--fix` flag to fix them."
# note that we have already set "--fix"
cat package.json | npx biome lint --stdin-file-path=package.json --fix

Expected result
When using stdin mode, it shouldn't return an error. (Shouldn't it behave the same as normal usage?)
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

@dyc3, this issue exists for formatting as well. The fix included in #4109 only handles this for the lint and check command, and not for the format. You can see this issue on 1.9.4 by running the following:
echo | biome format --write --stdin-file-path=foo.js
Should this issue be reopened, or would you like me to open another issue for this?


Fix qdr auth one_time_upgrade label check

Bug is here: https://github.com/infrawatch/service-telemetry-operator/blob/master/roles/servicetelemetry/tasks/component_qdr.yml#L152
We need to upgrade the default password that is generated by the Interconnect Operator because it is extremely weak. The logic on L177 is supposed to pair with the label on L173 to make this a "one time" operation. However, you can see on L158 it's querying and registering the Interconnect object itself to _qdr_basicauth_object, not the Secret, so _qdr_basicauth_object[0].metadata.labels.stf_one_time_upgrade will never be defined (also it should be _qdr_basicauth_object.resources[0], so a double-bug)

I'm in the middle of testing this right now.

Testing
I noticed this while working on adding auth into the infrared and smoketest scripts. The password changed when I redeployed the operator pod for unrelated reasons.
Before
With the current 1.5.3 code, the original password was in place and unchanged overnight in a quiesced environment; but changes when I patch the STF object.
$ oc get secret default-interconnect-users -o json | jq -r .data.guest | base64 -d; echo
NCewFQQFHWl_osYfL87U

$ oc patch stf default --patch '{"spec":{"alerting":{"alertmanager":{"receivers":{"snmpTraps":{"community": "test1"}}}}}}' --type=merge; sleep 60

$ oc get secret default-interconnect-users -o json | jq -r .data.guest | base64 -d; echo
SzRlEeD6Ap,t:UyGgmLU

With the fixed code, the password remains unchanged in the face of both multiple STF changes and the passage of time.
$ git log --decorate=short | head -1
commit 5798487aff329b460125877b90f8fd33128f2f9d (HEAD -> csibbitt/fix-qdr-auth-creds-upgrade, origin/csibbitt/fix-qdr-auth-creds-upgrade)

$ oc delete project service-telemetry
project.project.openshift.io "service-telemetry" deleted

$ oc new-project service-telemetry
[...]

$ ansible-playbook --extra-vars __local_build_enabled=true --extra-vars working_branch="$(git rev-parse --abbrev-ref HEAD)" --extra-vars __service_telemetry_snmptraps_enabled=true --extra-vars __service_telemetry_storage_ephemeral_enabled=true --extra-vars __service_telemetry_observability_strategy=use_redhat ./run-ci.yaml
[...]

$ ./validate_deployment.sh
[...]
* [info] CI Build complete. You can now run tests.

$ oc get secret default-interconnect-users -o json | jq -r .data.guest | base64 -d; echo
548ymk-p,NT0Fd:Mhv-w

$ oc patch stf default --patch '{"spec":{"alerting":{"alertmanager":{"receivers":{"snmpTraps":{"community": "test1"}}}}}}' --type=merge; sleep 60
servicetelemetry.infra.watch/default patched

$ oc get secret default-interconnect-users -o json | jq -r .data.guest | base64 -d; echo
548ymk-p,NT0Fd:Mhv-w

$ oc patch stf default --patch '{"spec":{"alerting":{"alertmanager":{"receivers":{"snmpTraps":{"community": "test2"}}}}}}' --type=merge; sleep 600
servicetelemetry.infra.watch/default patched

$ oc get secret default-interconnect-users -o json | jq -r .data.guest | base64 -d; echo
548ymk-p,NT0Fd:Mhv-w

Just a heads up that based on some additional testing and discussion (only related here to help with verification) that we found the parsing for the plaintext password in the qdrouterd.conf can result in certain generated passwords not working. I ran into this when connecting my OSP to an STF for other reasons, but using the authentication method, still failing.
Our hunch was the : in the password causing issues. I changed the password to be significantly simpler, and that resulted in connections being authenticated and setup without issue.
Chris did some investigation (and continues to investigate as of the time I posted this comment) about a comment in the qpid-dispatch code in qd_dispatch_validate_config() // TODO Add real validation code.
Our expectation is that we'll need to make sure the passwords being generated don't use any special characters, which is unfortunate, but likely required for this iteration.


paste multiple addresses problem

The address does not seem to be able to paste multiple addresses, there is an error:” isotope a part following ‘@’ should not contain the symbol”
Even this format is the same error<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>How should I solve this problem?

Hi, this certainly seems an issue. We'll try to take care of it.

Looking forward to this bug can be fixed, this will be a major breakthrough.

Hi, this certainly seems an issue. We'll try to take care of it. Thx for reporting ;)

hi Manusa,
Is this problem solved?

Hi, sorry, this issue is still active.
I'm currently spending most of my free time working on another project. I will probably complete that work in a couple of weeks. Since Isotope is gaining traction lately, I'm planning on resuming the work on this project when I'm finished with the other thing :crossed_fingers: .


chore: create Button Textarea story

Fixes #556
Proposed Changes

Add Textarea story (component already existed)

@tmastrom

The fullWidth prop doesn't appear to be working. Also, can we document the 'rounded' prop in this story.

The base Button theme component doesn't have the same 'rounded' prop that the BCGov theme has. Looking into the fullWidth issue now.


change default implicit Reader[Map] to use ListMap (keeps order)

Default implementation of Reader[Map[K,V]] don't keep order of fields in objects. This is information that  we can keep without trouble (probably). I used similar implementation in my code (mostly scripts).
i used this code to validate this pull request:
import upickle.default._
import scala.collection.immutable.ListMap
val rest:Map[String, String] = (1 to 100).map {
  r => ("r:" + r.toString, "l:" + r.toString)
}(collection.breakOut):ListMap[String, String]

read[Map[String,String]](write(rest))

Bug bankruptcy


Install CMake in Merlin base image (instead of copying from build)

Since the CMake install is a bit more involved than just copying the executable, let's just install it in the base container directly.

rerun tests

rerun tests


GCP audit events Plugin

A new Plugin Request
A plugin to read GCP audit events via pubsub topic.
I have noticed inside the slack community that there was some work regarding this. Is it still planned in roadmap?

Hi! I think the thread you're referring to is https://kubernetes.slack.com/archives/CMWH3EH32/p1665830293867959.
From my understanding, preliminary work was ongoing but there has not been any updates for quite a while. Is this something you'd be interested to work on?

Seems like the plugin now have been made public https://github.com/ahmedameenaim/falco-plugin <3

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

The GCP plugin has been contributed to our org by @ahmedameenaim (thanks ❤ ), and is now available at https://github.com/falcosecurity/plugins/tree/master/plugins/gcpaudit.
/close

@jasondellaluce: Closing this issue.

In response to this:

The GCP plugin has been contributed to our org by @ahmedameenaim (thanks ❤ ), and is now available at https://github.com/falcosecurity/plugins/tree/master/plugins/gcpaudit.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.