[HOLD for payment 2024-07-24] [$250] Login – Expensify changes to Hidden in LHN if login with new Gmail account and reload page

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

Version Number: v9.0.4-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4694015
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to https://staging.new.expensify.com/
Log in with a new Gmail account
Choose Track and Budget Expenses
Enter your name in Onboarding modal
Verify Expensify and Concierge chats present in LHN
Reload page

Expected Result:
Expensify and Concierge chats present in LHN
Actual Result:
Hidden is name of Expensify and user name/Hidden as a Concierge in LHN, when login with new Gmail account and reload page
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/74ca5199-e979-475a-a19d-e2f642d5340d
https://github.com/Expensify/App/assets/51066321/218fb752-8f9d-4649-997c-b784d9257d57

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ac469d1b3213174d
Upwork Job ID:<PHONE_NUMBER>506651244
Last Price Increase: 2024-07-08
Automatic offers:

ahmedGaber93 | Reviewer | 103078265
dominictb | Contributor | 103078266

Issue OwnerCurrent Issue Owner: @Christinadobrzyn

I'm not sure if this can be external - we'll start there.

Reviewing today

@dominictb Thanks for the proposal.
Your proposal works well, but can you please mention the code follow that display 'Hidden' based on participants with explanation if needed in your root cause?

@dominictb's proposal LGTM!
🎀 👀 🎀 C+ reviewed

working on the PR - https://github.com/Expensify/App/pull/45369

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] [@ahmedGaber93] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/40254
[x] [@ahmedGaber93] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/40254/files#r1686288563
[x] [@ahmedGaber93] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] [@ahmedGaber93] Determine if we should create a regression test for this bug. Yes
[x] [@ahmedGaber93] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Go to NewDot
Log in with a new Gmail account
Choose Track and Budget Expenses
Enter your name in Onboarding modal
Verify Expensify and Concierge chats present in LHN
Reload page
Verify that: Expensify and Concierge chats present in LHN with correct name instead of Hidden

Do we agree 👍 or 👎

Regression test - https://github.com/Expensify/Expensify/issues/414726
Payouts due on payment day:

[ ] Contributor: $250 @dominictb (Upwork offer - https://www.upwork.com/nx/wm/workroom/37820150/overview)
[ ] Contributor+: $250 @ahmedGaber93 (Upwork offer - https://www.upwork.com/nx/wm/workroom/37789064/overview)

Payment day - payment summary here - https://github.com/Expensify/App/issues/44833#issuecomment-2246105763
Closing this as complete!


PSA updates to simplify options for cloning packets

@hanw please take a look at this to see if it matches your expectations.

Can we merge this?


Fixed crash caused by state persisting across a transition from one d…

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
SpatialGameInstance now creates GSM (GlobalStateManager) and SpatialStaticComponentView (SSCV) each time we create a Spatial connection, and destroys them when we destroy a Spatial connection.  This avoids state "leaking" from one deployment to another when the client transitions, which ultimately led to crashes.
Release note
Release note added.
Tests
This was tested on Spatial + PIE as well as cloud deploys.  This affects games where clients transition from one deployment to another (rather than using server travel).  Transitioning back and forth repeatedly from one deployment to another no longer causes crashes.  Additionally, I setup the GDKTestGyms and tested ServerTravelGym in Spatial + PIE and verified that server travel is still working correctly.
STRONGLY SUGGESTED: How can this be verified by QA?
Both the original case and the ServerTravel case can be tested as described above.
Documentation
Release note.
Primary reviewers
@m-samiec @MatthewSandfordImprobable @aleximprobable

Very cool.


Issue : Unauthorized Access Handling

Issue : Unauthorized Access Handling
Description
The response message for unauthorized access should be corrected for better user experience.
Steps to Reproduce

Try to access the POST method without a valid session.
Observe the response message.

Expected Result
The response message should be clear and correctly spelled.

Closing Remarks for Issue #26
Issue: Enhance Error Handling in Stripe Session Creation
Resolution:
Error handling mechanisms were improved to provide more descriptive and helpful error messages during the Stripe session creation process. This aids in better debugging and user experience.
Related Pull Request: #28


Make sure SVGs are scalable

Add a build step to make the SVG files scalable (remove width and height).

resolved via this commit (yep wrong commit name).


Compile to ES5 and publish to NPM

I'm trying to compile a project using this module, but upon running npm run build I get:

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/react-native-link-preview/index.js:7

Read more here: http://bit.ly/2tRViJ9

from: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-run-build-fails-to-minify
Some third-party packages don't compile their code to ES5 before publishing to npm. This often causes problems in the ecosystem because neither browsers (except for most modern versions) nor some tools currently support all ES6 features. We recommend to publish code on npm as ES5 at least for a few more years.

To resolve this:
Open an issue on the dependency's issue tracker and ask that the package be published pre-compiled.```

Please pre-compile and publish

thanks nicolas, published under version 1.3.4


Support i18n in Subscribe Input Change section in Home

I supported i18n in SubScribe Input Change section.
And I translated to jp.

awesome! thank you! i completely miss that part.


[chip-test,sival] chip_sw_usbdev_aon_wake_resume

Test point name
chip_sw_usbdev_aon_wake_resume
Host side component
Rust
OpenTitanTool infrastructure implemented
Unknown
Silicon Validation (SiVal)
Yes
Emulation Targets

[ ] None
[X] CW310
[X] Hyperdebug + CW310

Contact person
alees24
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[x] Device-side (C) component developed
[x] Bazel build rules developed
[x] Host-side component developed
[x] HJSON test plan updated with test name (so it shows up in the dashboard)
[x] Test added to dvsim nightly regression (and passing at time of checking)
[x] For SiVal test cases, test is running relevant FPGA or silicon regression

estimate 2

Clarify whether this test can actually be implemented, also it's not listed in the testplan.

estimate 0


Bump of-watchdog to version 0.4.1

Signed-off-by: Radoslav Dimitrov<EMAIL_ADDRESS>
Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)

Which issue(s) this PR fixes

Closing also #76
How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Tested via CI and approved.


Allow unauthenticated install of mongodb-org

Fixes https://travis-ci.org/doctrine/mongodb-odm/jobs/287745628#L501
Also removes the tests against MongoDB 3.0 since travis-ci comes with 3.2 installed and we can't downgrade. It's not optimal, but I don't have a better solution at this time.

If you're resigned to testing on 3.2+, would it be worth switching over to container builds (https://github.com/mongodb/mongo-php-library/pull/411)?

@jmikola that's a good idea, sadly I remember needing sudo to install mongo-orchestration. It's a long time ago, so it might be worth another shot.


Provider spec should be available in JSON

It will allow to specify $schema in provider.json to get completion and validation in VSCode and other IDEs.

Bonus points for submission to https://www.schemastore.org/json/

That we didn't want to do yet. Especially now when integration parameters will probably lead to schema change.


sqlfluff: 2.0.5 -> 2.0.7

Diff: https://github.com/sqlfluff/sqlfluff/compare/refs/tags/2.0.5...2.0.7
Changelog: https://github.com/sqlfluff/sqlfluff/blob/2.0.7/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 227507 run on x86_64-linux 1

1 package built:

sqlfluff


Error message: link pdf from storage

Poorly worded. The meaning can be found below.

We released the Pagekit Beta today. I close this issue because the code base completely changed. Please open a new issue if it still exists.


Provide support for .github repos

Provide support for .github repos that have the community health resources, such as code of conduct.
Example of KEDA: https://github.com/kedacore/.github/blob/main/CODE_OF_CONDUCT.md

🙌


Make dnn_trainer print the minibatch size to ostream

So, maybe this a bit controversial...
When I train networks, I like to fill all the fields of the dnn_trainer so that they all appear in my training log, and then access them from the trainer (get_min_learning_rate(), get_mini_batch_size(), etc...)
I found myself logging the minibatch-size manually many times, so finally I decided to make the dnn_trainer print it.
I was hesitating to submit this PR because, when you build your minibatches manually, and print the trainer to the screen, users might be surprised to see a 128 for the minibatch size (default value). But then I thought that it is already the case with the minimum learning rate, if you train with your own custom loop.
Anyway, feel free to reject it if you think it's not a good idea :)

Na, it's cool :)


Improve AccountHeaderView

The AccountHeaderView will get a new set of additional features (see checklist below). If you have any additional requests for this component, please bring them forward in this issue. Thanks!
Checklist for Release 0.4.0:

[x] Ability to make accounts selectable (via checkboxes)
[x] Ability to show extra info on accounts (icon and text) to e.g. display unread message counts

Implemented and coming with Release 0.4.0!


chore: render app on local host with an sdk shim

Description
This PR shims the Contentful SDK when running on a development ENV so that you can render the React application for local development on localhost.

Before
All testing had to run on contentful itself

After
The app can run on localhost and be tested on cypress

Steps to test

checkout the branch, run npm install
set the REACT_APP_CTFL_API_KEY environment variable to be your API key
run npm run start
run npm run cypress OR, if not testing just go open http://localhost:3000
click on e2e tests
click to run tests

🖼 Screenshots
https://user-images.githubusercontent.com/16711614/200433915-f09dd3c8-09d8-4315-9e42-854c6a6c53ca.mov
Checklist

[ ] Read the contributing guidelines.
[ ] Each commit follows the Conventional Commit spec format.
[ ] Update the readme (if applicable).
[ ] Update or add any necessary API documentation (if applicable)
[ ] All existing unit tests are still passing (if applicable).

[ ] Add some steps so we can test your bug fix or feature (if applicable).
[ ] Add new passing unit tests to cover the code introduced by your PR (if applicable).
[ ] Any breaking changes are specified on the commit on which they are introduced with BREAKING CHANGE in the body of the commit.
[ ] If this is a big feature with breaking changes, consider opening an issue to discuss first. This is completely up to you, but please keep in mind that your PR might not be accepted.

Current dependencies on/for this PR:

next

PR #140

PR #139

PR #141

PR #142

PR #143

PR #144

PR #145

PR #146

Current dependencies on/for this PR:

next

PR #140

PR #139

PR #141

PR #142

PR #143

PR #144

PR #145

PR #146

Current dependencies on/for this PR:

next

PR #140

PR #139

PR #141

PR #142

PR #143

PR #144

PR #145

PR #146

Current dependencies on/for this PR:

next

PR #140

PR #139

PR #141

PR #142

PR #143

PR #144

PR #145

PR #146

@sherwinski merging his in but tagging you one more time just in case you want to see it once more after the force push.


always crash when set anchor

evrytime seting an anchor the game crash

Im playing with the mod for sometime now, I have the same issue, but I manage to debug the mod sometime by making a realy small blueprint just before setting anchor to a big blueprint
For example, I put two floor, select them set anchor on them, save, go back to my big blueprint, set the anchor, should be good to go

By the way always save your game before anchor, blueprint are stored in the game save, so even if you crash you still have the selection ready to go to try again


hub-spoke network topology with shared services in Azure -contoso.com not found

Hi,
DSC installation part on VM extension install errors out as following complaining about "contoso.com" domain does not exist.
Deployment failed. Correlation ID: a7b453c9-081d-4a06-8789-c9a4e2d5e1b3. {
"status": "Failed",
"error": {
  "code": "ResourceDeploymentFailure",
  "message": "The resource operation completed with terminal provisioning state 'Failed'.",
  "details": [
    {
      "code": "DeploymentFailed",
      "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
      "details": [
        {
          "code": "Conflict",
          "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"VM has reported a failure when processing extension 'install-adds'. Error message: \\\"DSC Configuration 'CreateForest' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xWaitForADDomain  failed to execute Set-TargetResource functionality with error message: Domain 'contoso.com' NOT found after 5 Reboot attempts.  The SendConfigurationApply function did not succeed. LCM failed to start desired state configuration manually.\\\".\"\r\n      }\r\n    ]\r\n  }\r\n}"          }
      ]
    }
  ]
}
}

Hi @myaesubi Thank you for your feedback! Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team.

Hi @DixitArora-MSFT ,
Please find below:
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/shared-services.
Thanks,
Mohammad

We've taken this item to our internal backlog for further research and will update as necessary!


Chicken save & exit mouse conflict

Botty Version
An older version of my require_merc branch of my fork, core is botty 2.2. chicken subroutine was unchanged
Describe the bug
Unusual rare behavior on chicken when trying to click save & exit. Could it be due to the bot continuing to try to move or perform attack sequence simultaneously when the chicken occurs and causes a conflict in mouse movement?
To Reproduce
Steps to reproduce the behavior:
-Force a chicken during an attack sequence or movement sequence, then observe mouse attempt to save&exit.
Expected behavior
-Save&exit should be clicked
Screenshots / Video
https://user-images.githubusercontent.com/9866239/142743819-c3a2376b-3465-454d-b4c0-f5db118dc425.mp4
Logs

I would hope that two changes make this 1) less likely to occur 2) if it occurs have another go to click save&exit:
retry save and exit until loading screen is reached
https://github.com/aeon0/botty/commit/c22f133
43daf7c862c021ddaa20b4b1001d2c15d
https://github.com/aeon0/botty/pull/44/files

Sry, didnt want to close @mgleed, if you think that is enough (both changes are post v0.2.2), close it. If not you can bug me more with it : )

Sry, didnt want to close @mgleed, if you think that is enough (both changes are post v0.2.2), close it. If not you can bug me more with it : )

Sounds good, must have missed that change in #44 . Like I mentioned before, my character attempted to grab corpse every run after a single death after I movrd the kill thread line up, but seems like it probably works otherwise. If there are any other issues I run into I'll reopen.


Pseudo feedback framework

adds:
feedback base class, feedback factory
rocchio feedback implementation
ide-dec-hi feedback implementation
document vector class for VSM representations of queries / documents
modified:
ranker base class to work with VSM queries
Looks like some feedback features were snuck into the develop branch while I was working on this so there are some conflicts..

@skystrife I'm wondering if there's much value in this PR given what you've written for feedback

Sorry for the extended delay in getting back to you on this.
I think there is still value here, particularly in how you've separated out the feedback method from the rankers. I think it might be beneficial to be able to, for example, investigate which query terms were added by feedback, which in my current implementation is completely hidden away inside the ranker.
I would be open to a refactoring of the existing feedback code that extracts the feedback mechanism out into a separate class hierarchy like you have here, which will give users the option to either apply it manually (to see what exactly about a query is being modified) or use it as a "black box" ranker (which is what the current implementation does).

Closing for inactivity.


(GH-278) Support both yaml and yml files

Fixes #278

@akordowski what are your thoughts on this one?

This method should IMO return a .yml file, accordingly to GitVersion. The other changes looks good.
https://github.com/GitTools/GitReleaseManager/blob/4010dc57ff673bb7147c2c45339b889ad65f87ed/src/GitReleaseManager.Core/Configuration/ConfigurationProvider.cs#L100-L103

@akordowski getting a failing build... going to have to re-think this one a little bit...

A unit test is failing

@akordowski yip.  I know what is causing it, but need to re-think how this is working a little bit before continuing.

@AdmiringWorm @akordowski this should now be working.  There was a codecov error which was failing the build, but I have just run it again, hoping that it was a transient error.  Would appreciate another review.  Thanks

LGTM too

@gep13 yeah, I have seen quite a few transient errors regarding codecov lately, usually worked for me when running the build again.
I do believe they are looking into the issue.

@AdmiringWorm said...
I do believe they are looking into the issue.

Looks like it failed again.  Would you be happy to merge without a successful build?

This part is the first time I have seen though in the error response from codecov

Build already finished, unable to accept new reports.

Could be there was too short of a time between the runs 😕
I think it can be safely ignored for now.

@gep13 yeah, I think that would be fine.
When I think more about the error from codecov, I think it is due to several rebases in a very short amount of time (I could be wrong of course), so it basically became confused over which build it was supposed to use.

Should we wait for the LGTM analysis first?

@AdmiringWorm said...
When I think more about the error from codecov, I think it is due to several rebases in a very short amount of time (I could be wrong of course), so it basically became confused over which build it was supposed to use.

That could well be it.

@gep13  your changes have been merged, thanks for your contribution 👍


activation: allow to update poet server during runtime

Motivation
Allows updating the poet server that is used during ATX building process.
depends on: https://github.com/spacemeshos/go-spacemesh/pull/2532
Changes

safe interface for activation.Builder that can be used concurrently with PublishActivationTx. The new server will be used only after current build finishes
unsafe interface for activation.NiPSTBuilder (that type should not be exported at all, but it requires more refactoring)
API change. NodeServer.UpdatePoetClient (https://github.com/spacemeshos/api/pull/154)

Test Plan
Unit tests
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge

failed in systemtest-mining
bors merge

bors merge


Expand error message to explain that a string was found

With opt-level = "3" this previously said:
must be an integer, `z`, or `s`, but found: 3 for ...

The error message doesn't make that super clear.
This should now be a bit more clear.
Fixes #8234

We could even include a bit more saying that "3" should become 3 (either unconditionally or after trying to parse "3" into an integer?
cc @steveklabnik

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

may be we should write quotes also \"3\"

I would agree yeah it probably makes the most sense to also include the surrounding quotes, but otherwise looks great to me!

Adjusted and also fixed the tests.

Now they fail in apt install gcc-multilib

@bors: r+

:pushpin: Commit 09084a365f612192fa026754b448f5b0be231890 has been approved by alexcrichton

:hourglass: Testing commit 09084a365f612192fa026754b448f5b0be231890 with merge db702d3d09de4c1c1284e159090f49b793a7fe4d...

:broken_heart: Test failed - checks-azure

@bors retry
#7858 😦

:hourglass: Testing commit 09084a365f612192fa026754b448f5b0be231890 with merge 55869de80ab8b7bd20cbb9a909e303fc03cf0125...

:sunny: Test successful - checks-azure
Approved by: alexcrichton
Pushing 55869de80ab8b7bd20cbb9a909e303fc03cf0125 to master...


Previous not populated when using --latest and skip_tags are set but don't match

Describe the bug
If skip_tags is defined with a regex that correctly generates the changelog (by skipping the correct/defined ones), there is a regression when setting previous and using --latest which was supposed to be fixed here: https://github.com/orhun/git-cliff/issues/3
But it looks like if you use --latest in combination with skip_tags, even if the pattern should not match the tag at all, it will simply not populate the previous field. This might have been introduced here(?): https://github.com/orhun/git-cliff/commit/7f867ae647ff30f54aae314596cbc7c7ce4f50c1
If I remove the skip_tags from the config while generating with --latest, previous is populated as expected.
To Reproduce
Steps to reproduce the behavior:
[changelog]
header = """
# Changelog
All notable changes to this project will be documented in this file.\n
"""
body = """
{% if version %}\
    # [{{ version | trim_start_matches(pat="v") }}]\
    {% if previous %}\
        {% if previous.version %}\
            (https://github.com/discordjs/discord.js/compare/{{ previous.version }}...{{ version }})\
        {% else %}
            (https://github.com/discordjs/discord.js/tree/{{ version }}\
        {% endif %}\
    {% endif %} \
    - ({{ timestamp | date(format="%Y-%m-%d") }})
{% else %}\
    # [unreleased]
{% endif %}\
{% for group, commits in commits | group_by(attribute="group") %}
    ## {{ group | upper_first }}
    {% for commit in commits %}
        - {% if commit.breaking %}\
            [**breaking**] \
          {% endif %}\
            {% if commit.scope %}\
                **{{commit.scope}}:** \
            {% endif %}\
            {{ commit.message | upper_first }} ([{{ commit.id | truncate(length=7, end="") }}](https://github.com/discordjs/discord.js/commit/{{ commit.id }}))\
    {% endfor %}
{% endfor %}\n
"""
trim = true
footer = ""

[git]
conventional_commits = true
filter_unconventional = true
tag_pattern = "[0-9]*"
skip_tags = "v[0-9]*|11|12"
ignore_tags = ""

All tags on the repo in question:
10.0.0
10.0.1
11.0.0
11.1.0
11.2.0
11.3.0
11.3.1
11.3.2
11.4.0
11.4.1
11.4.2
11.5.0
11.5.1
11.6.0
11.6.1
11.6.2
11.6.3
11.6.4
12.0.0
12.0.1
12.0.2
12.1.0
12.1.1
12.2.0
12.3.0
12.3.1
12.4.0
12.4.1
12.5.0
12.5.1
12.5.2
12.5.3
13.0.0
13.0.1
13.1.0
13.2.0
13.3.0
13.3.1
13.4.0
13.5.0
5.2.0
5.3.2
6.0.0
6.1.0
7.0.0
7.0.1
8.0.0
8.1.0
8.2.0
9.0.2
9.1.0
9.1.1
9.2.0
9.3.0
9.3.1
v5.0.0
v5.0.1
v5.1.0
v5.3.0
v5.3.1

Expected behavior
Expect skip_tags to not drop unrelated tags from the previous field.
System (please complete the following information):

OS Information: [Windows 11 Pro / 10.0.22000 Build 22000]
Project Version: [0.5.0]

Hello, good catch!
This should be fixed in 943c23f, can you try it out and let me know if it works as expected?

Yes, that did indeed solve it, I do have another question about this, it might be semi-related? Please do tell if you want a separate issue about this but:
Let's presume I want to run something like this:
git cliff --prepend CHANGELOG.md -l which works with the changes/fixes you made now properly and populated previous and everything to correctly give me all the info I need.
But with this approach I need to manually git tag a release, then run the command with the --latest flag to get the diff between the 2 tags and such the commit.
But ideally, I would want to run something like this:
git cliff --prepend CHANGELOG.md --unreleased --tag 14.0.0
Is this somehow possible or not at all? Since previous does not seem to get applied if I do it this way, without manually creating the tag before.

Yes, that did indeed solve it, I do have another question about this, it might be semi-related? Please do tell if you want a separate issue about this but:
Let's presume I want to run something like this:
git cliff --prepend CHANGELOG.md -l which works with the changes/fixes you made now properly and populated previous and everything to correctly give me all the info I need.
But with this approach I need to manually git tag a release, then run the command with the --latest flag to get the diff between the 2 tags and such the commit.
But ideally, I would want to run something like this:
git cliff --prepend CHANGELOG.md --unreleased --tag 14.0.0
Is this somehow possible or not at all? Since previous does not seem to get applied if I do it this way, without manually creating the tag before.

Yes, that did indeed solve it,

Thanks for testing this out!

Please do tell if you want a separate issue about this

Yes, that would be nice 👍🏼

Let's presume I want to run something like this: git cliff --prepend CHANGELOG.md -l which works with the changes/fixes you made now properly and populated previous and everything to correctly give me all the info I need. But with this approach I need to manually git tag a release, then run the command with the --latest flag to get the diff between the two tags and such the commits.
But ideally, I would want to run something like this: git cliff --prepend CHANGELOG.md --unreleased --tag 14.0.0
Is this somehow possible or not at all? Since previous does not seem to get populated if I do it this way, without manually creating the tag before.

This is supposed to be possible. Actually, there is an example command (which is similar to what you gave as an example) in README.md:
# 1- changelog header is removed from CHANGELOG.md
# 2- new entries are prepended to CHANGELOG.md without footer part
git cliff --unreleased --tag 1.0.0 --prepend CHANGELOG.md

So I'm not sure if there is a problem here. Maybe you have a different use-case for --prepend? Feel free to submit another issue about this and I'd be more than happy to work on it 🙂
P.S. Sorry for the late reply.


⚠ Roblox Site has degraded performance

In 66d40c9, Roblox Site (https://roblox.com/) experienced degraded performance:

HTTP code: 200
Response time: 3227 ms

Resolved: Roblox Site performance has improved in 62dc855 after 17 minutes.


Update documentation to make it easier for users to find the right content for them

This is a result of some previous discussions in https://github.com/usds/justice40-tool/issues/949#issuecomment-988091659. It's not really touching the idea of the wiki yet, since we will discuss that in a follow up conversation. I just wanted to get something up there that we can all react to.
Changes:

Added a "Datasets" section to the top level readme, so we can add download links there for people who only want the data.
Added a "Local Quickstart" section to the top level readme that links to some docker compose setup steps, for people who just want to try running the app locally.
Added an "Advanced Guides" section for everyone else looking to go deeper.
Updated INSTALLATION.md to only itself document installation of more generic things like git, docker, and homebrew, and delegate more specific installation guides to the sub components where it's relevant (e.g. don't document node setup there, because someone working with the data pipeline doesn't need that).
Added a readme in the github actions directory just to give some context, and link that from INSTALLATION.md (it's not really something requiring an install, but I guess if you wanted to "install" our github actions deployment scripts in your own repo I guess you can stretch it. It seems like the most logical place for it for now).

I'd recommend going to the README on this branch and starting there to review this: https://github.com/usds/justice40-tool/blob/sverchdotgov/new-user-docs-updates/README.md

@switzersc-usds @esfoobar-usds @saran-ahluwalia I think I addressed the main comments from this and our discussion. Seems like there are two follow up tickets, for the Spanish translations and the github action to update the dataset links.
Some notes that we didn't already talk about.

Made a "For Developers and Data Scientists" section in the top level readme.
The datasets section probably needs some work to make it comprehensible/useful, but that can be part of the follow up.
The geojson got access denied so there may be some permissions to figure out.

Which datasets are useful might be a conversation on its own.


Content font-size on website is very small

Not sure why, the content font-size is computing to 9px on Chrome on macOs.
Haven't checked other browsers/OSes yet.
Screenshot attached:

I just checked in safari and firefox as well, the font is showing 9px, also I inspected the page, have attached the screenshot maybe be helpful


First immediate api call has no result callback

What's going on?
First api call in the first screen has no result callback
Steps to reproduce

switch the stack screen order in 'main-navigator.tsx' to be
 <Stack.Screen name="demoList" component={DemoListScreen} />    <Stack.Screen name="welcome" component={WelcomeScreen} />

then start the program, you will find out it will never get the result
     const result = await characterApi.getCharacters() in character-store.ts file
It only happen in the initial screen.

npx ignite-cli doctor results:
System
platform           darwin
arch               x64
cpu                12 cores       Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
directory          canbeDeleted   /Users/maci/Documents/git/canbeDeleted
JavaScript (and globally-installed packages)
node               16.3.0       /usr/local/bin/node
npm                7.17.0       /usr/local/bin/npm
npm              7.17.0
yarn             1.22.10
yarn               1.22.10      /usr/local/bin/yarn
code-push-cli    2.1.9
ignite-cli       7.0.3
Ignite
ignite-cli         7.0.3        /usr/local/bin/ignite
ignite src         build        /Users/maci/.config/yarn/global/node_modules/ignite-cli/build
Android
java               1.8.0_261    /usr/bin/java
android home       -            /Users/maci/Library/Android/sdk
iOS
xcode              12.5.1
cocoapods          1.10.1       /usr/local/bin/pod

I have to add a delay to solve it. I have no idea why.

Hi @Magrider! We have noticed this issue in other cases and what you did by adding a delay does solve the issue. This is a workaround that we are currently recommending. We are trying to figure out why this is happening and we would like to solve it as quickly as possible. Thanks 😃

I had the same issue,
I called the store action in useEffect but it wasn't working
after adding a delay to the actions it worked fine
but after checking the useEffect I found that I had an infinite loop
so, after I fixed it everything works normally now

Me too i got the same issue, add i fixed it by adding a delay of 1ms. i know that's not the best solution, but it's the only one i found. Hope this bug will be fixed soon.

Don't know how but removing the ToggleStoryBook from app.tsx solves the issue. And works smoothly

Hi @abhisekz,
I just tested the Ignite with your suggestion and it didn’t seem to work for me. Is there anything you might have changed that I’m missing here? We are excited to find out what is causing this issue so we really appreciate you for trying different workarounds. 😃

hi @kateinkim ,
If i remove the ToggleStoryBook from app.tsx it works for me. I don't know why it doesn't for you.
Thanks @abhisekz

Hey @momolafrooo! It's great to know that it worked for you and it seems like we are getting close to figuring out the issue. When I was trying to reproduce I noticed that it would appear to work if I just reloaded the app but it would fail again if I did a fresh install of the app. Not sure why that would be the case other than maybe some cache getting cleared by removing and reinstalling the app.

I can confirm, this issue persists in my project with ignite, first I thought it's because of the MST problem then I changed to Mobx, the problem is still there. 😞
all of my api call getting stuck because of this problem, hopefully, soon someone could find the solution
Thanks for the removing ToggleStorybook solution I'll do this instead whenever I'm not going to use storybook
    // <ToggleStorybook>
      <StoreProvider store={rootStore}>
        <SafeAreaProvider initialMetrics={initialWindowMetrics}>
          <ErrorBoundary catchErrors={"always"}>
            <AppNavigator
              initialState={initialNavigationState}
              onStateChange={onNavigationStateChange}
            />
          </ErrorBoundary>
        </SafeAreaProvider>
      </StoreProvider>
    // </ToggleStorybook>

I had a similar issue with another async/await call never returning. Removing ToggleStorybook also worked for me in a completely different context. I don't claim to understand why, just giving feedback here.

I have spent days until I find this issue through discussions. Deleting toggle storybook also resulted in resolving all my problems that I thought coming from MST, or MST-QGL and now everything works, waaaaaah!
I believe it is better to configure the base app without toggle story book until this issue is resolved, just to give people a nice setup without any issues to start developing their apps.

@kateinkim can you verify that #1906 resolved the issue and close it if has?

Just tested this again and it seems like it is resolved by #1906. Closing this.


[Bug]: zitadel ready command does not override default config parameters, causing the health check to fail.

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Environment
Self-hosted
Version
v2.54.1
Database
PostgreSQL
Database Version
16-alpine
Describe the problem caused by this bug
zitadel config sets following parameters
ExternalPort: 9080
ExternalSecure: false

docker compose healthcheck is used as
healthcheck:
  test: ["CMD", "/app/zitadel", "ready", "--config", "/zitadel.yaml" ]
  interval: '10s'
  timeout: '5s'
  retries: 5
  start_period: '10s'

this healthcheck fails as default port 8080 and proto https are used (values are not overwritten)
Get \"https://localhost:8080/debug/ready\": http: server gave HTTP response to HTTPS client

To reproduce
config zitadel.yaml
Log:
  Level: 'info'

ExternalPort: 9080
ExternalSecure: false

docker compose
services:
  zitadel:
    restart: always
    container_name: zitadel
    image: "ghcr.io/zitadel/zitadel:v2.54.1"
    command: 'start-from-init --config /zitadel.yaml --steps /zitadel.yaml --masterkey "MasterkeyNeedsToHave32Characters" --tlsMode disabled'
    ports:
      - "9080:8080"
    volumes:
      - ./zitadel.yaml:/zitadel.yaml:ro
    healthcheck:
      test: ["CMD", "/app/zitadel", "ready", "--config", "/zitadel.yaml" ]
      interval: '10s'
      timeout: '5s'
      retries: 5
      start_period: '10s'
    depends_on:
      db:
        condition: 'service_healthy'
  db:
    image: postgres:16-alpine
    restart: always
    container_name: zitadel-postgres
    environment:
      - POSTGRES_USER=root
      - POSTGRES_PASSWORD=postgres
    ports:
      - '5432:5432'
    healthcheck:
      test: ["CMD-SHELL", "pg_isready", "-d", "db_prod"]
      interval: 10s
      timeout: 60s
      retries: 5
      start_period: 10s

after started
docker inspect --format "{{json .State.Health }}" zitadel | jq '.Log[].Output'
docker exec -it zitadel /app/zitadel ready --config /zitadel.yaml

Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

Hi @everesio, this issue is tricky. I'd say it's not a bug imho but this deserves a discussion which has been introduced in the past: https://github.com/zitadel/zitadel/issues/6863
The ready command may indeed get a config, but it ignores ExternalPort and ExternalSecure as those settings are related with configuring Zitadel behind a reverse proxy and does not affect the ready command which deals with Zitadel readiness no matter if a reverse proxy is set. So it's expected that your 9080 port is ignored. Here's the code that shows that the ready command ignores external settings as expected:
scheme := "https"
if !config.TLS.Enabled {
	scheme = "http"
}
// Checking the TLS cert is not in the scope of the readiness check
httpClient := http.Client{Transport: &http.Transport{TLSClientConfig: &tls.Config{InsecureSkipVerify: true}}}
res, err := httpClient.Get(scheme + "://" + net.JoinHostPort("localhost", strconv.Itoa(int(config.Port))) + "/debug/ready")

One thing it's the ready command and another one is the ready endpoint which is affected by the ExternalPort and ExternalSecure settings and the endpoint do indeed listen according to those settings.
For the TLS issue, if you use your custom zitadel.yaml the ready command will asume that the TLS config is enabled because that it's the default config for Zitadel and it doesn't know that you've set tlsMode disabled for your Zitadel instance. Therefore the ready command uses TLS for the client while the Zitadel instance is not and you get: server gave HTTP response to HTTPS client
If you add the following lines to your zitadel.yaml the ready command will work fine for your docker compose file
TLS:
  Enabled: false

In https://github.com/zitadel/zitadel/tree/main/e2e/config/localhost you can check an example where that TLS setting is added to zitadel.yaml and --tlsMode disabled is also used.
In summary I think this is not a bug but some clarification should be added to docs as @mffap proposed in https://github.com/zitadel/zitadel/issues/6863
Maybe @eliobischof, @adlerhurst or @hifabienne can confirm if this should be treated as a bug or a docs issue that can be treated instead as a docs improvement
Thanks!

@doncicuto  thank you. I see the problem.
If you want please close the ticket or use it to improve your documentation.

The compose health checks will be obsolete with #8684


example don't work

hi, how can I run the example properly?

I added another example here: https://github.com/digitaltom/leaflet-indoor/blob/master/examples/captions.html
This should also run locally after checkout.


Are Babel packages still used?

Got a question about babel in this repo.
Reading from there would be an babel.config.js for @babel/plugin-transform-runtime, babel-plugin-glsl. But there isn't one in this repoe, is babel packages not used anymore? or there is some tricks of next.js I am not aware of?
https://nextjs.org/docs/advanced-features/customizing-babel-config

@kayden1940 Ah, thanks for the issue after moving to SWC I forgot to remove some babel dependencies. Indeed since Nextjs v11 we moved from babel to SWC so these dependencies are not necessary anymore


Compiler Errors

I am receiving many compiler errors when integrating into a basic Swift 3 application with cocoa pods.
pod 'SwiftyOAuth', '~> 0.3' // the pod

Hi @gtokman, you have to install 1.1 (I just updated the README). Thanks!


the status of expired order is still "Accepted" in living trading

Hello!
I find that the status of order is still "Accepted" when the order is expired.
I want to know when the status order will change to "Cancel" or "Expired"?
Thx!!
this is a simple snippet to reproduce
self.buy(
                data=self.data0,
                price=self.data0.close[0]-0.01,
                exectype=bt.Order.Limit,
                valid=self.data0.datetime.datetime(0) + datetime.timedelta(minutes=3),
                # transmit=False,
                size=1000,
            )

the notification from store shows that the order is expired
{
   "id":"968",
   "time":"1615515720.000000000",

   "batchID":"968",
   "type":"ORDER_CANCEL",
   "orderID":"967",

   "reason":"TIME_IN_FORCE_EXPIRED"
}

but the notify_order shows that the status of order is still accepted
--------------------------------------------------, ORDER BEGIN,
, 2021-03-12T02:22:04,
, Ref: 1
OrdType: 0
OrdType: Buy
Status: 2
Status: Accepted
Size: 1050
Price: 1.1877
Price Limit: None
TrailAmount: None
TrailPercent: None
ExecType: 2
ExecType: Limit
CommInfo: <btoandav20.brokers.oandav20broker.OandaV20CommInfo object at 0x7f7e0a5d3f40>
End of Session:<PHONE_NUMBER>999999
Info: AutoOrderedDict()
Broker: None
Alive: True,
, --------------------------------------------------, ORDER END

After doing some survey, I find this is cause by value of self.data.datetime[0] is nan.
So the expire function of broker returns false.
Therefore, the status of order won't be set to expired.


Android: VTM 0.13.0 OpenGL vector map library

VTM 0.13.0 OpenGL vector map library.

Loading graphs does not work with GraphHopper snapshot.
Probably the downloaded graphs need to be updated?

Thanks. The graph loading for snapshot should be fixed now.


[Artist] Initial selected tab should be ‘WORKS’

Open artist view, land on about tab, we should adjust this so that the work tab is the default selection when the view is opened.

This one is deceptively challenging; @alloy  should I try it?

If it's easier to make works the first position in the left then feel free to make that change
Sent with thumbs,
Katarina Batina
Product Designer
Artsy.net

On May 26, 2016, at 4:23 PM, Sarah Scott<EMAIL_ADDRESS>wrote:
This one is deceptively challenging; @alloy should I try it?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


Error starting the server: couldn't retrieve the server's process ID

Apparently this issue is tied to using an older Java version than 16 for Minecraft version 1.17+. However, I'm still having this while I have AdoptOpenJDK 16.0.1.
console.out:
cat /opt/mscs/worlds/shny/console.out
Error: LinkageError occurred while loading main class net.minecraft.bundler.Main
        java.lang.UnsupportedClassVersionError: net/minecraft/bundler/Main has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 60.0

java -version:
openjdk version "16.0.1" 2021-04-20
OpenJDK Runtime Environment AdoptOpenJDK-16.0.1+9 (build 16.0.1+9)
OpenJDK Server VM AdoptOpenJDK-16.0.1+9 (build 16.0.1+9, mixed mode)

Running on Raspberry Pi 4:
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Hi @mbacalan. Class file version 61.0 means you need to be running Java 17 at a minimum.

Hi @mbacalan. Class file version 61.0 means you need to be running Java 17 at a minimum.

Just realized this mistake! Thanks and sorry for wasting your time 🤦♂


Enhancing User Experience: Add Homepage Style and Animations/Effects

The only thing in our website to attract the user is the home page so I think it would be great to enhance the home page's style and add some animation or visual effects to make it more engaging and dynamic.
Here are some of the proposed changes:
Current home page looks like:-

Use parallax scrolling to create a sense of depth and motion as the user scrolls down the page.
Add some interactive elements, such as hover animations on images or buttons.
Use CSS animations to create a smooth transition between sections on the page.
I believe these changes will improve the user experience and attract more visitors to the resume genrator project.

hi i would like to do this assign me

@PURUSHOTHAM-REDDY-N  sure go a head.

too late


[help wanted] Code Documentation

I can help..provide me with a description of what's needs to be done

There are no comments on the variables, files, classes and functions explaining what the code does.
Using this file from url_launcher as a sample:
https://github.com/flutter/packages/blob/main/packages/url_launcher/url_launcher/lib/src/types.dart

You can look at another big flutter packages (or files from this one) to see what we're talking about.
unfortunately I won't have the time to solve this issue on the next weeks, If you're able to fix this problem, that will help a lot the package!

@erickNjuki we started documenting the code.
The single dropdown is almost finished, but we need help on the multiple one


Add automated documentation for metrics

Description of the change:
Add automated documentation for metrics.
The document path is docs/monitoring/metrics.md,
and the document content is created with monitoring/metricsdocs tool.
Motivation for the change:
See up-to-date documentation of all the metrics in one place (name, description, and type).
Note
Maybe we should consider adding the doc under: operator-framework/operator-sdk/tree/master/website/content/en/docs
jira-Ticket: https://issues.redhat.com/browse/CNV-21334
Signed-off-by: Aviv Litman<EMAIL_ADDRESS>

/hold

/hold

Hi @varshaprasad96,
We decided to separate the creation of the documentation file for metrics from the effort to produce a general plug-in for Observability, In order to add metrics documentation in the next version.
This PR is ready for review.

/assign @varshaprasad96

Added Copyrights to metrics.go as well.

/hold

/hold

@avlitman Since the testdata can be regenerated, the existing changes would be overwritten. I think we may still need a plugin to make changes on scaffolding especially the Makefile. Reason being, the testdata/ projects are primarily for users to refer how a sample scaffolding looks like after using the operator-sdk commands. If we make custom changes in Makefile (on top of existing scaffolding, which does not come from a plugin or any commands) then for a new user it maybe confusing to infer the sample project.

Hi @varshaprasad96, thank you so much for reviewing.
I updated the code to be only under the monitoring operator, and is ready for review.
Since the Makefile custom changes are now at monitoring/memcached-operator, I think it's not confusing now because the operator is specific for monitoring. Do you agree, or still think it's better to create a new plugin?
*Note: I followed the way we create the metrics documentation on hco

following the discussion on https://github.com/operator-framework/operator-sdk/pull/6135 we agreed it does not make sense to update the testdata generator, but to first create a plugin in kubebuilder instead.

@avlitman This is yet to be converted into the generator code like #6135, right?

So, this is still incorrect - you don't edit the the testdata samples directly, because they'll be overwritten, you need to edit the generators in https://github.com/operator-framework/operator-sdk/tree/master/hack/generate/samples

@avlitman This is yet to be converted into the generator code like #6135, right?

So, this is still incorrect - you don't edit the the testdata samples directly, because they'll be overwritten, you need to edit the generators in https://github.com/operator-framework/operator-sdk/tree/master/hack/generate/samples

Hi @varshaprasad96 @jberkhahn, thanks!
My steps:

I updated hack/generate/samples/internal/go/memcached-with-webhooks/memcached_with_webhooks.go
run make generate testdata
for v3 and v4-alpha:
cd testdata/go/v3/monitoring/memcached-operator/
make generate metricsdocs (it created the testdata/go/v3/monitoring/memcached-operator/docs/monitoring/metrics.md file
pushed the changes to the pr

I missed adding the metrics.md file to the generators, I will fix that.
Except that is there anything I'm missing?

@avlitman This is yet to be converted into the generator code like #6135, right?

So, this is still incorrect - you don't edit the the testdata samples directly, because they'll be overwritten, you need to edit the generators in https://github.com/operator-framework/operator-sdk/tree/master/hack/generate/samples

Hi @varshaprasad96 @jberkhahn, thanks!
My steps:

I updated hack/generate/samples/internal/go/memcached-with-webhooks/memcached_with_webhooks.go
ran make generate testdata
for v3 and v4-alpha:
make generate metricsdocs (it created the testdata/go/v3/monitoring/memcached-operator/docs/monitoring/metrics.md file
pushed the changes to the pr

I missed adding the metrics.md file to the generators, I will fix that. Except that is there anything I'm missing?

Done.
Now the testdata folder changes all generated using make generate testdata.
Note: if a metric will be added in the future we will need to run  make generate metricsdocs and paste the output in the generator.

/ok-to-test

@varshaprasad96 Updated the name to memcached_with_customization

LGTM.

LGTM

The PR looks good overall, except for two things:

(nit): The log lines and comments which have been modified to with customizations. I would prefer them to be more specific, like "webhook and metrics" where apt, or just "with webhooks".

As for now I changed all to "with webhooks and metrics documentation". regarding the condition I need more guidance.

The question of moving the common generator code to a library. I'm still curious on whether it would be useful to scaffold those out for every project. I agree that the generator should live in the operator project, but its helpers can still be moved to a common place. We can create an issue and fix that in a follow up.

I will make sure to add this in a follow up.

Rest of it is good to go from my end. Thanks for working on this PR! /lgtm @everettraven @jberkhahn could you all take a look at this too before we go ahead and merge this.

Hi @sradco @varshaprasad96 @everettraven @jberkhahn.
I created an issue for all the follow up implementations needed:https://github.com/operator-framework/operator-sdk/issues/6256.
@jberkhahn can you review and (if approved) merge this pr?
Thanks all!

/lgtm

/hold cancel
/lgtm

@avlitman Once all the tests pass I will merge. Thanks!

/lgtm

/lgtm


List of existing pastes

Hi,
Is there a way to have all existing pastes listed on the home page, or have a separate page with such list?
This would be very helpful for managing the pastes.
Thank you

I guess a REST call is not enough?

I think that having pastes listed on a web page would be easier to use than API.
REST call could work in the absence of a web list, but please include an example of such call in the readme.
I have no idea how to request the list...

Okay, I have some PoC but I am not sure how this is really that useful. At the end of the day it's just a list of links. Is it really all you need?

The main points behind this idea are to:

find and remove old entries,
find entries for which links were lost.
A chronological list of pastes would be sufficient for this.

Ideally, it would be great to have a table with:

paste creation date,
expiration date, if set,
something to act as a title for each paste - e.g. first line up to 32 characters,
encryption info (true / false).

Thank you

Unfortunately, creation date is not stored (anymore). Title would be possible but depending on the size of the database, I am not sure we are coming into denial-of-service area. In fact, I am already a bit worried dumping the entire list each time. On the other hand, I am also a bit too lazy to implement pagination now. So this is what I could offer:

I actually think it's a feature that none of the visitors is able to see what other people posted, unless you have the exact link. If anything i would argue to make the random link larger and even more hard to guess.

+1 this idea, besides, can be related with #54 to keep trace of the usage for the server and force the expiration specific files.

I personally like this idea for it's (probably) low efforts to implement, and this can probably recycle a lot of existing functions/code.

Thanks for the suggestion (and sorry for the late reply). I like the idea as well but I think we should flesh out a reasonable design in a separate issue.

I personally like this idea for it's (probably) low efforts to implement, and this can probably recycle a lot of existing functions/code.

Thanks for the suggestion (and sorry for the late reply). I like the idea as well but I think we should flesh out a reasonable design in a separate issue.

Thank you! anyway... don't understand what you mean... sorry.

I mean outlining what the tool(s) should be capable of doing, what the UI
should look like etc. should not be discussed here but in a separate GitHub
issue.
jichef @.***> schrieb am Fr., 8. Nov. 2024, 23:54:

I personally like this idea for it's (probably) low efforts to implement,
and this can probably recycle a lot of existing functions/code.
Thanks for the suggestion (and sorry for the late reply). I like the idea
as well but I think we should flesh out a reasonable design in a separate
issue.
Thank you! anyway... don't understand what you mean... sorry.
—
Reply to this email directly, view it on GitHub
https://github.com/matze/wastebin/issues/59#issuecomment-2465871242, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA4ERRBWG2OBGCEWNWZGRLZ7U6LDAVCNFSM6AAAAABJXEWBTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVHA3TCMRUGI
.
You are receiving this because you commented.Message ID:
@.***>


[Bug]: Saving Payment Method (Stripe) returns error

What happened?
Getting an error when saving the stripe payment method in the admin side after placing my stripe keys (or even if it is left empty), same with other payment gateways too.
BadMethodCallException: Call to undefined method Admin\Models\Payments_model::getConfigAttributes()
in /home/username/domains/domain.com/public_html/order/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php:71
Appreciate your help on this. Thanks 🙂
What did you expect to happen?
To be able to save without error, and enable stripe
Version
3.2.x
What browser are you seeing the problem on?
Chrome
Relevant log output
BadMethodCallException: Call to undefined method Admin\Models\Payments_model::getConfigAttributes()
in /home/username/domains/domain.com/public_html/order/vendor/laravel/framework/src/Illuminate/Support/Traits/ForwardsCalls.php:71

Fixed https://github.com/tastyigniter/TastyIgniter/commit/1da4091b58b8fef9104dda02fe33c19a087de004


Do not issue  Left side of comma operator is unused and has no side effects error on (0, expr) this-removing pattern

Both our and babel's output emits (0, expr) in many places to unbind the this from the call that's about to be done. Ergo, the 0, expr pattern is not without side-effects, and is, in fact, a very highly used pattern that we probably shouldn't issue an error on. It's probably OK to special-case the literal-zero LHS as a signal to silence the error.

Damn, any workaround for this? I am in a NX Workspace, and we are trying to compile a custom executor.
 >  NX   ⨯ Unable to compile TypeScript:

   apps/entergon/webpack.config.ts:9:19 - error TS2695: Left side of comma operator is unused and has no side effects.

   9 const _default = (0, _webpack.createConfig)("entergon", (config)=>{

This is a duplicate of #35866

This should be able to be closed now that #51989 is merged.

Thanks!


Directory Assistance db with a space in filename is no longer recognized by DLAU V1.2.1

If the Directory Assistance Catalog db filename contains a space (e.g. "Directory Assist.nsf"), DLAU V1.2.1 no longer recognizes the Directory Assistance and states that "Directory Assistance is not configured".
This is not an issue with the same Domino environment using DLAU V1.2.0

This cannot be reproduced so closing


Improves TradingEconomics Downloaders

Description

Add rategate to all requests so that we don't run over rate limits
Improve logging across all TradingEconomics Downloaders
Add retries to HTTP requests due to occassional failure
Added skipping of duplicates
Added skipping of fields with no actual value
Added temp file writing, temp file moving
Write to proper output directory
Update data directory structure
Update GetSource in BaseData implementation for TradingEconomics
Parallelize data processing and writing to disk

Related Issue

#3401
Motivation and Context

Alternative data efforts
Requires Documentation Change

Maybe - Directory structure has changed, but functionally everything else is the same
How Has This Been Tested?

Ran TradingEconomics algorithm locally and tested downloaders locally.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

@Jay-Jay-D In order to maintain directory structure for Github, we must have those files (i.e. if those files are missing, they won't show up on here).


Multiple parallel loads (even of the exact same image) can easily overwhelm available disk space

Wanted to open a discussion on this from a Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1162742
Description of problem:
Loading a single docker image requires double (1.3.0) or triple (1.2.0) it's size to load. Therefore multiple parallel loads (even of the exact same image) can easily overwhelm available disk space.  If docker's storage is located on the "/" filesystem, unpredictable failures are possible.  This is possibly made worse by bugzilla #1132388 (or similar), where temporary load data is not cleaned up until minutes later.
Steps to Reproduce:

docker save registry.access.redhat.com/rhel7:0-23 > img.tar
for i in $(seq 1 10); do docker load < img.tar & done
watch -i 1 -d df

Actual results:
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda2       8.3G  7.9G     0 100% /
Expected results:
Disk doesn't fill up.  When possible, loads that would exceed storage capacity should return an error status/message rather than blindly filling up the disk.
Additional info:
Suggest some kind of queuing/scheduling system where only a fixed number of loads proceed in parallel, the remaining block until the first batch are finished, then proceed only if there is sufficient space (when checking is possible).
Should we only allow 1? 5? X? number of pulls/loads at a time to make sure we don't run out of space and then queue the rest?

https://github.com/docker/docker/pull/9970

This has been merged for 1.5


feature/ome-tiff-suggestion

Description
The purpose of this PR was to resolve https://github.com/bioio-devs/bioio/issues/38 and unify the metadata that was being produced by bioio-tifffile and bioio-ome-tiff. In resolving this there were three vectors we pursued

That bioio-tifffile is the default for .ome.tiff with both bioio-tifffile and bioio-ome-tiff installed. This is now resolved by https://github.com/bioio-devs/bioio/commit/3d1671314a65185dbe003a1943a4c9c4a0d69021
That the channel names do not match up
That the metadata is different for both images

This led to an exploration into the feasibility of accessing channel names, unfortunately all information about specific channels are locked within the ome-metadata block. This means that in order to align the channel names we need to go about some level of parsing of the metadata block. This would be the first instance of parsing the ome metadata in the tifffile reader and would blur the responsibilities of each reader.
From this there are two avenues.

Acknowledge that the readers are different and keep them separate. Include no handling of the ome format within tifffile and specify that it is not intended for ome-tiff. Informing users that they should use bioio-ome-tiff
Combine the readers into one super reader for all tiff files. This would mean pulling bioio-tifffile and bioio-ome-tiff in favor of bioio-tiff

There are benefits to both. If we keep the readers separate we keep our development simple and easy to iterate on, we allow the possibility of other formatted tiff files to be created in the future. On the otherhand combining them reduces possibility of user confusion, giving them more tools/ support.

I think I am of the opinion of combining the readers into one reader
In regards to the third vector from the top of this post : That the metadata is different for both images. In tifffile we append the ome metadata whereas in bioio-ome-tiff we parse the metadata. This raises some additional issues, we use metadata as a catch all and with readers being moved to plugins the specifics of each readers metadata is undocumented. I do not have a good solution to this.
What this PR does do as a half measure is provide a warning to any user trying to use the tifffile reader on an ome-tiff that better metadata handling will be present if they install bioio-ome-tiff. It does not resolve the separation of metadata which for the time being is "intended function" until we decide on our path.

Hmmmm is there a method to check that bioio-ome-tiff isn't already installed before sending this log.warning?
I feel like it's entirely possible that someone will do a simple read of BioImage("some-file.ome.tiff") that attempts to use bioio-ome-tiff first (due to the new longest suffix wins change), but it fails for some reason, so it goes to bioio-tifffile next and then the user ends up confused because they already have bioio-ome-tiff installed.

Hypothetically if bioio-ome-tiff is installed than this logic would not be raised unless the user specifies bioio-tifffile. In this case we still want to warn them. If bioio-ome-tiff fails silently and we go to bioio-tifffile then that is even more dangerous becasue the user assumes they are using bioio-ome-tiff. This error would at least tell them something is wrong rather than just trying. We could include another message like "if you already have bioio-ome-tiff installed try the feasability report".

Hmmmm is there a method to check that bioio-ome-tiff isn't already installed before sending this log.warning?
I feel like it's entirely possible that someone will do a simple read of BioImage("some-file.ome.tiff") that attempts to use bioio-ome-tiff first (due to the new longest suffix wins change), but it fails for some reason, so it goes to bioio-tifffile next and then the user ends up confused because they already have bioio-ome-tiff installed.

Hypothetically if bioio-ome-tiff is installed than this logic would not be raised unless the user specifies bioio-tifffile. In this case we still want to warn them. If bioio-ome-tiff fails silently and we go to bioio-tifffile then that is even more dangerous becasue the user assumes they are using bioio-ome-tiff. This error would at least tell them something is wrong rather than just trying. We could include another message like "if you already have bioio-ome-tiff installed try the feasability report".

Thanks for the info! In that case I would simply update it to include the "feasability report" part. Nice work!


Support multiple tags for exporter (lifecycle)

Seems like this is a duplicate of #138

Duplicate. Closed.


[For discussion] Bindalias updates

This PR is being created as a stub for bindalias updates to improve the default bindalias settings in order to prompt some discussion / consensus building on what these should be before they are coded.
This has been prompted by issues with mappings for e.g. alt-f/alt-h which conflict on windows (and randomly override) menu shortcuts.
Reserved keys
Regardless of the platform used by individual developers, IMO bindalias needs to conform to BOTH of the following:

Mac - common shortcuts defined in https://support.apple.com/en-us/HT201236
should be followed where appropriate and avoided if not. This is important
for MK to be accepted into the Apple app store.
Where keys defined in other sections on this page make sense for this application,
these should also be used by preference.
Windows - alt-single letter should be avoided as these correspond to menu
shortcuts (e.g. in english locale, alt-f should activate the file menu).
Common Windows shortcuts can be found at
https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec
Graphics apps - where it does not conflict with the above, any synergy with
keys commonly used in popular SVG / image editors may be beneficial.

Opening list for discussion...

alt-c/e/f/h/p/r/s/t need to be removed or mapped elsewhere.
control-z should be reserved for future Undo
(though reset is a close equivalent right now unless we mapped it to file reload).
control-y should be reserved for future Redo
escape should probably NOT be used for pause as this is not common usage
it should perhaps close some open windows (like op properties perhaps)
control-f4 should be made to close a sub-window if it has focus
this might be the same function as for escape above
control-o below is overriden by menu Ctrl-O - delete or use a different mapping
we should consider adding new console commands if it helps us define
common Mac or Windows shortcuts
f1 should be help - but what help?? and should it be a menu shortcut rather than a bindalias
should zoom in/out use the numeric +/- rather than standard +/-?

Also, should we use special aliases to allow menu keys to be remapped by the user
e.g. File/Open calls an alias FileOpen which is mapped to dialog_open
user can change the alias to something else so that Ctrol-O does something else
and map e.g. control-shift-o to dialog_open

(though reset is a close equivalent right now unless we mapped it to file reload).```

This should actually call a command called undo currently. And just map that command (currently) to calling whatever we need. The redo command is `shift+control+z` rather than y.

I think the Undo/Redo test went fairly well. I needed a method of copying the entire operation tree. But, beyond that the main part of the idea worked fairly well and it stacked somewhat nicely.

I don't have strong opinions on the structure or what the keybinding keys are, but I do think that we should take a hard look at the defaults and see if there are improvements that can be made.
For instance:

The shapes in 0.8.0 need new bindings that reflect units, otherwise they are tiny in nano units. Also, I think adding 'stroke red classify' is a good idea.
Dunno if my "Go" keybind is implemented as a default? Doesn't seem like it. Less important now because of Laser Panel for the public, but still handy.
There are a million things I don't know about meerk40t and a lot of these can be exposed as example commands.  Wish I had seen that before!  We really ought to come up with some serious command documentation, "recipes", if you will.
escape should be estop NOT pause, pause (or p) should be pause.

I don't have strong opinions on the structure or what the keybinding keys are, but I do think that we should take a hard look at the defaults and see if there are improvements that can be made.
For instance:

The shapes in 0.8.0 need new bindings that reflect units, otherwise they are tiny in nano units. Also, I think adding 'stroke red classify' is a good idea.

I agree. I guess it probably is useful to do a circle / square etc. because you can then resize these using the Position pane.

Dunno if my "Go" keybind is implemented as a default? Doesn't seem like it. Less important now because of Laser Panel for the public, but still handy.

Yes - I would like this!!!! I'll take a look.

There are a million things I don't know about meerk40t and a lot of these can be exposed as example commands.  Wish I had seen that before!  We really ought to come up with some serious command documentation, "recipes", if you will.

Go for it!! The Wiki is waiting with baited breath for your text...

escape should be estop NOT pause, pause (or p) should be pause.

The pause key is already pause. However, IMO the escape key is too frequently used to e.g. cancel typing text etc. to abort something like a burn outright - if you are preparing the next job whilst the current one is executing, then the escape key is all too easy to hit by accident.

The command run for LaserPanel Start.
planz clear copy preprocess validate blob preopt optimize spool0
(for the Go binding)

inpain's rant today about key mappings is relevant to this pull request.  Do we already have some structure in place for platform-specific keybinding defaults? If not, there probably should be. His example of Ctrl being right-click is especially troubling for mac/win compatibility. I know it's been discussed forever by inpain and Tat, but a lot of that gets internalized and not documented in a way that helps out issues like this that happen in the future. So mac needs to be considered here in this remapping work.

wx already converts command into ctrl on macs. there is a rawctrl you can test which should work like menu.

Ok - mac code is now tested and working. This is (I hope) good to go,

@tatarize, @tiger12506 @joerlane  - Ready for review again.

I have requested @joerlane 's review some time back and he has not done so. I can't see this making Mac stuff worse, so if he doesn't review it soon, I suggest we merge it and we can iterate when he does use it if it needs further work.

I likely need to take a look at the differences in modifiers between the #825 and #801 here and see if they can be less of a broken-home when both of these are merged.

IMO there is not a conflict between modifiers between these two PRs which are addressing different things.
The concern I have is that there is (generally - not just in #825) a confusion about how we handle events - should we use the wx model of events whereby MK code hooks into mouse and keyboard events as they require and wx handles the hierarchy of event processing to ensure that the correct piece of code (frame, tree, scene, scenewidget etc.) handles a specific event, or for genuine reasons of correlating events which need to be stateful should we centralise the handling of mouse and keyboard events and have MK parse these and call relevant modules to process them. (Note: I have no view on which is correct, only a hunch that it may not be a good idea to mix and match).
If I felt that this PR (#801) was contributing to this confusion I would be the first to put it on hold, but since it only makes existing code more comprehensive and does not change how events are handled, I would suggest that this one should be approved and merged.
Similarly, although #825 does contain material new wx event handling, I still recommend that it is approved and merged, and  that subsequent to both these merges, we take a look at event handling and see if it needs to be rationalised.

WxPython handling of such things is fine. It comes down to how much code could/should be reused. And here we could imagine writing something that could maybe use some of bind/alias in a different gui system. We could also see maybe using scene stuff only in a wx context. So really neither of these is that useful in a CLI or different GUI system. Centralizing things is sometimes useful but sometimes less useful depending on whether doing that creates large amounts of coupling between the different systems. We could maybe merge bind/alias stuff a bit deeper into scene so we deal with binds as a keybind widget within the scene. Or we could try to remove all the specific wx parts from the keybinds so that it's plausible to use keybinds in a CLI context. Though neither of these seems to be logically right.
If I had to guess I would say keybinds should be available to widgets, and our main keybinds should catch whatever our various keystrokes and if not caught it should pass it down the chain. This isn't substantively different than allowing keybinds to caught at the wx layer and then propagate down into scene if they aren't otherwise dealt with, and the way this happens depends a bit on the current system and how scene should deal with hotkeys.
I'd think we'd be best to integrate #825 keystroke stuff to be a generalized set of modifiers that would catch whatever sorts of binds we might want. Then if the keybinds get consumed at the outermost level by something like bind-alias code it should rather defer to scene in this situation. Same for other things like joystick values which could, like mouse and keyboard, matter for some particular widgets and should be there for the scene operations. It depends a bit on how it currently works and what's the best method of generalizing these interactions.
If we have a hotkey binds qua bindalias and we have a scene. We need to have a hotkey matter to both, and the chief method for this to deal with the bindalias first and then the scene, depending on how possible that is within the current system that would inform the changes we make in the system itself.

Before considering this, we need to note that Mouse and Scene events are slightly different in scope. A keyboard event can apply anywhere in the Frame - but unless you are e.g. allowing drag of elements from scene to tree (I am not recommending this but dragging elements from scene to an Opnode might make some sense) or from tree to scene (makes no sense whatsoever) then mouse events are going to be limited to the scene.
My gut reaction is that we should handle both Keyboard and Mouse events in Frame, Panes and Scene and not in SceneWidgets - and that this would create the correct balance of centralisation. I think that this is essentially the current approach, so any cleanup would not require wholesale rework. We need to ensure that there is consistency over handling of Keyboard events - I note that if there is e.g. an alt-f keybind, then (on Windows) this prevents using the accelerator to open the File menu if you last clicked in Scene, but doesn't disable it if you last clicked in Tree - this is inconsistent and I think the Tree has it wrong.

On another note: the wxutils.get_key_name routine may need some more lines to acknowledge KeyUp for Shift and Ctrl:
    if keyvalue == "":
       if key == wx.WXK_SHIFT:
            keyvalue = "shift+"
        elif key == wx.WXK_CONTROL:
            keyvalue = "ctrl+"
        elif key == wx.WXK_ALT:
            keyvalue = "alt+"

these are currently not recognized

On another note: the wxutils.get_key_name routine may need some more lines to acknowledge KeyUp for Shift and Ctrl:
...
these are currently not recognized

There has not previously been a use case for recognising these keyup cases, which is why no one has spotted that they are not reported until now. But you are right that on key-up we should report these too, though there may need to be extra code (particularly in keymap) to deal with this situation.
Since we have not heard from @joerlane I am going to merge this and put this on my to-do list (unless you would like to pick it up Jens).

I think it's getting rather messy with the treatment of multi-modifier-keypresses:
a) Scenario 1: Try ctrl-shift-o for outline of an object, works like a charm. Now press Shift-O, keep them pressed and add the ctrl-key - nothing happens
b) In the keybind-window press Ctrl-Shift and release the Shift-Key: nothing
c) In the keybind-window press Ctrl-Shift-O and release the Shift-Key, add or remove other modifiers as you want but keep the O-pressed
Not sure whether this is the right approach, but I think we need to distinguish a couple of things:

key-down: one solution could be to keep track which keys are still pressed and then compose the get_key_name event appropriately
key-up: if you release i.e. in the above example (ctrl-shift-o) the o-key then you get back what you expected: ctrl-shift-o. If you release the ctrl key only then what: imho you should you get at least a key-up event for ctrl and what about the still pressed shift-o (sometimes an immediate follow-up event for keydown gets raised, sometimes not).
...

I think this depends on whether you trigger things on a non-modifier keydown or keyup.
Either way you are going to use the modifiers in place when the non-modifer key goes down or up and AFAIK the current get_key_name handles this correctly in both situations. But the Keymap window might not i.e. if you do Ctrl then P then shift it may not show the correct thing. I would need to check.

#853 seems to do it.
Non-modifier should be processed on keydown. So Ctrl-P-Alt should correctly show Ctrl-P whereas Ctrl-P-Alt-P should show Ctrl-Alt-P.


Wrong Compliance protocol url on compliance server github page

What version are you using?
https://github.com/stellar/go/tree/master/services/compliance

What did you do?
I clicked on the Compliance protocol link from the compliance-server section.

What did you expect to see?
I expected to see the page describing the compliance protocol used by the compliance service.
What did you see instead?
I see a 404 not found page and here is the link of it :https://www.stellar.org/developers/learn/integration-guides/compliance-protocol.html

@gaclaudiu Thank you for reporting the broken link. The link will be fixed in #2020. You can access the compliance protocol documentation here.


GI deprecation

NCBI has deprecated using GI numbers for anything in the future.  Here we must also do this.
In order to begin this process I have commented out code and created todos:
# TODO: GI deprecation.

The following commits were made on individual files for deprecating the GI functionality:

DatabaseManagement:  9713e87d1ebf29451ae91781a645029f3c91abe3
get_gi_list.py: f9c595600aaae25ea71567203ce9a1384b535e91
CompGenBlastn

92db4ac7563a0b9b8549600355fce8887c305103
8a20c32cbacfdfb0ddf10bf889fe51a7360cf4d4

Blast README: 6a5ac79538546409f2d31d280469ed2bd1fc4dc3
Blast\utils.py: 2f94c21e51b8fd4645cb404fceb0f154de332405

@sdhutchins GI list paths weren't integrated with the Manager module, and all of it's functionality.  So it's not necessary for anything to change at the moment.  Whenever the Window Masker stuff get's going, we can add an attribute into the management.py file and add the appropriate directories to cookiecutter templates.  It should go under /users//databases/NCBI//WindowMasker or something like that.
If you add some basic links here that would be awesome.

#113 to speed up BLAST we will deprecate GI numbers and use seqIDs or Windowmasker.

I added this to the CompGenBLASTn class (now named OrthoBlastN) in the the __init__
self.environment_vars = dict(os.environ)
if 'BLASTDB' not in self.environment_vars.keys():
    msg = "BLASTDB is not set in your path."
    raise EnvironmentError(msg)
elif 'WINDOW_MASKER_PATH' not in self.environment_vars.keys():
    msg = "WINDOW_MASKER_PATH is not set in your path."
    raise EnvironmentError(msg)

PR #116

Addressed by #120


⚠ Bofrost.at has degraded performance

In f188061, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1599 ms

Resolved: Bofrost.at performance has improved in 4be5377 after 25 minutes.


Enhancement Request: Customizable Normalization Range in wavfile_reader Function

Issue:
The current implementation of the wavfile_reader function automatically normalizes each loaded signal in the range (0, 1) by default. While this behavior might be suitable for many use cases, it would be beneficial to provide the option to control the normalization process.
Enhancement Proposal:
I suggest introducing a user-selectable option to control normalization in the wavfile_reader function. Specifically, this can be achieved by introducing a flag for normalization and allowing users to pass a tuple specifying the desired range. In case of the normalization flag set to False, the wavfile_reader function will load the raw amplitude signals.
# Default behavior (current implementation)
wavfile_reader(filename):

# Custom normalization range (e.g., normalize to the range -1 to 1)
wavfile_reader(filename, normalize=True, n_range=(-1, 1))

@gkontogiannhs  @tzamalisp  ready to use: https://github.com/AIoT-Group-UoP/crossai/blob/8a067ebb78181353c0c17a8a393b7ff913216939/crossai/loader/_audio.py#L35C1-L36C61


Add minimal Clerk example

Instead of adding a new example, it would be better to use the existing chat example and remove the chat stuff. Also, this is for React right?

Ok, so we can remove the chat-clerk app (agree since the only difference with the chat is the auth).

Also, this is for React right?
Do you think we should make one also for VueJS?

Yes that would be niceThough I think we should finish doing this in React for all the different features to nail the DX, before moving on to Vue.


added @skip-constraint to policies which cannot be deployed against gatekeeper

What is this PR About?
konstraint supports an annotation to skip generating a constraint. have added this to the ones which are not gatekeeper compatible
Check list

[x] Have you created a test case in _test/conftest-unittests.sh
[x] Have you created a test case in _test/opa-profile.sh
[x] Have you created a test case in _test/gatekeeper-integrationtests.sh
[x] Have you followed the TESTING.md doc? If not, please provide commands/steps to test this PR.
[x] Have you re-generated POLICIES.md

cc: @redhat-cop/rego-policies

/approve

/lgtm


Test better exports package

Test Pedro's package that adds server-side exports, in order to merge it / release it in Backpack 5.2 - https://github.com/DigitallyHappy/better-exports

@tabacitu did the server-side export ever get released? I never did see any kind of announcement about it. We really need it!

@tabacitu @promatik Any update on this? We really need the functionality and I can't find any way to get it to work even though it says this is merged?


[proj] Update to 9.0.1

What does your PR fix?
Update to today's release.

Which triplets are supported/not supported?


Optimize build images trigger github action rules

What type of PR is this?
What this PR does / why we need it:
Optimize build images trigger github action rules
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

see:
https://github.com/lbbniu/crane/pull/11
https://github.com/lbbniu/crane/pull/14


Integate Eclipse Backend-Function-Bindings client

Source project: https://projects.eclipse.org/projects/automotive.bfb

Source project has been archived.


[Bulk] Validation Fixes AM 5-16 (resolved comments)

This PR fixes ~50 issues across 6 articles.

Global effort to fix build validation errors
@Rick-Anderson
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


Closes #71: Edit tasks (Works for both current and completed tasks)

Implemented edit functionality on the single task scenes, with their corresponding task scene having a save task button rather than the add task button when adding tasks. Tasks are now able to have their attributes edited and for these edits to be saved.

I have reviewed your changes and everything functions correctly so good job! However, The .metadata folder is not relevant to the project and it should not be in your commits. Please remove this folder and it's contents before merging (I suggest you add it to .gitignore).

I have added .metadata to the gitignore file so that those files are now removed from being committed.


Feature/unit tests

There's not too much we can unit test (since it's basically just a series of redirects), but added tests for the methods that we can actually test right now.

The Snyk vulnerabilities are caused by the .NET runtime itself - I can't fix those.

I've manually approved the Snyk checks, given we can't resolve them without updating the .NET Framework.


Interpolate environment variables in config

As a general solution to the type of problem which #7 deals with, it would be nice to be able to reference environment variables in some or all config. For example, if we were to use golang templates, it might look like:
target:
  data_source_name: 'sqlserver://prom_user:{{.PROM_PASSWORD}}@dbserver1.example.com:1433'

This could be done either for the entire file or for specific keys. I think it would be straightforward enough and I'd be happy to do it if you think it would be useful.

Here's a simple implementation:
https://github.com/free/sql_exporter/compare/master...treatwell:master


Replace componentWillMount() and componentWillReceiveProps()

The following warnings are displayed in the console when using a SideNav component:
Warning: componentWillMount has been renamed, and is not recommended for use. See
https://fb.me/react-async-component-lifecycle-hooks for details.

* Move code with side effects to componentDidMount, and set initial state in the
constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress
this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work.
To rename all deprecated lifecycles to their new names, you can run `npx
react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Uncontrolled(SideNav)

Warning: componentWillReceiveProps has been renamed, and is not
recommended for use. See https://fb.me/react-async-component-lifecycle-hooks
for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use
memoization techniques or move it to static getDerivedStateFromProps. Learn
more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps
to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name
will work. To rename all deprecated lifecycles to their new names, you can run `npx
react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Uncontrolled(SideNav)

Isn't this resolved already?

Any update on this?

Is this repo dead?

Do you have any ideas to resolve this issue? I just think we just need update the uncontrollable dependency in package.json? I'm so new with js.

Resolved in 0.5.0.


The problem with interfaces that extends the interface

I want classes that implement the Observer interface to also implement the Comparable interface, how can I do this?
interface Comparable<T> {
    equals: (item: T) => boolean;
}

interface Observer extends Comparable<Observer> {
    notify: () => void
}

class TestA implements Observer {
    private name = '';

    equals = (item: TestA) => {
        return this.name === item.name
    }

    notify = () => {}
}

class TestB implements Observer {
    private name = '';

    equals = (item: TestB) => {
        return this.name === item.name
    }

    notify = () => {}
}

Error:

TS2416: Property 'equals' in type 'TestA' is not assignable to the same property in base type 'Observer'.   Type '(item: TestA) => boolean' is not assignable to type '(item: Observer) => boolean'.     Types of parameters 'item' and 'item' are incompatible.       Property 'name' is missing in type 'Observer' but required in type 'TestA'.

But, TestA implements the Observer interface why are they not compatible?
Of course, I can write like this:
class TestA implements Observer {
    private name = '';

    equals = (item: Observer) => {
        return this.name === item.name
    }

    notify = () => {}
}

But then I get such an error, and besides, this is not entirely correct, because I want to compare only objects of this class:

Property 'name' does not exist on type 'Observer'.

How to do it right?
"typescript": "^3.9.2"

It looks like this is a question rather than a bug report. This issue tracker is for tracking bugs and active work on TypeScript itself, rather than a general forum for programmers using TypeScript to get help or ask questions.
You can ask questions on sites like Stack Overflow. We are not able to provide one-on-one support on the issue tracker. Please read the issue template carefully - it has important information on what kinds of reports can be acted on here, as well as links to useful TypeScript resources. Thanks!

Need to use polymorphic this - https://stackoverflow.com/a/61922374/8963706


Document cilium internal IP address assignments

Cilium assigns IP addresses from the pod CIDR for internal use - e.g., cilium-health-ep, cilium-host, etc. Users need to account for these assignments as this can affect the maximum number of pods that can be deployed on a kubernetes node. This is particularly useful for EKS like environments that have resource limits based on instance types.

Hi, I think the details for the doc should go here.
https://docs.cilium.io/en/v1.9/concepts/networking/ipam/#address-management
Is it possible to point to the location [Code or any Doc] where I can see the details of the internally used IPs list? I will try to document this.
Thanks

Hey, I am new to this cilium project. I would love to start contribution from Documentation issue. It would be great if someone provide a reference to start with this issue.

@chowmean Sorry, I missed your message. Are you still interested in working on this documentation related PR?
AFAIK, we currently don't have a central place in the code that lists all the internal allocations. But this would be a good place to document the requirement as smaller instance types can limit the IP allocations - https://docs.cilium.io/en/v1.10/concepts/networking/ipam/eni/#ec2-instance-types-eni-limits.


TypeError: Cannot read property 'url' of null

https://sentry.io/artsynet/force-production/issues/271269109/
TypeError: Cannot read property 'url' of null
  File "/app/desktop/apps/artist/view_helpers.coffee", line 94, in Object.toJSONLD
    url: artwork.partner.url
  File "/app/desktop/apps/artist/routes.coffee", line 76, in null.<anonymous>
    variables:
...
(10 additional frame(s) were not displayed)

TypeError: Cannot read property 'url' of null

Interested to see if this auto-closes the Sentry issue.

Aww, bummer, had to manually close the issue on Sentry.

This repo isn't linked to sentry yet, only Eigen is atm

Oops, I must have configured the wrong one then :D


Restore fileName to anonymous function names

Anonymous functions used to be named just (anonymous), but as of DataDog/pprof-nodejs#141 they are named things like (anonymous:L#42:C#16) which triggers the : detection here. That logic dates from commit dcca5749da3f82706500403f9a52493e120fa809 which predates the anonymous function name change, and so pretty clearly wasn't intended to cover it.
This change means that instead of anonymous functions being reported in pyroscope as just (anonymous:L#42:C#16), they are instead reported as ./dist/example.js:(anonymous:L#42:C#16):42 which is a lot more pleasant to work with.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Sorry for delay, had to get permission from the CTO in order to sign, doing things by-the-book :) Signed now!

The CLA has been signed for a while now -- any chance this could be merged soon? Thanks!


controls row groups and empty tables

Description
See commit list and docs

@willi-mueller I fixed most of the suggested code changes and some docs changes... I think we are good for now. thanks, good review :)


Update schedule for 2024

[x] decide on schedule
[x] update schedule.html for website

https://github.com/ioos/bio_mobilization_workshop/blob/a821ee3b8936ce8ff385ccf29f28a6c73ff1a504/_includes/custom-schedule.html#L1

Everyone alright with the schedule for this year?

Breakout room slide would be good!

Suggested a few edits to the schedule: https://github.com/ioos/bio_mobilization_workshop/pull/121

I'm thinking that hyperlinking Animal Telemetry might be confusing to people, they might think it directs them to the specific breakout room? Should we remove the hyperlink?

last year we didn't hyperlink to the eDNA page from the workshop agenda.
I vote for removing the hyperlink but keeping the text.

[ ] TODO: Add 16:30 timeslot on both days to get people back into the main room: Day 1 - Recap of the day, looking forward to day 2, and OBIS Node Managers can do a quick hello and describe their role. Day 2 - recap of day 2, continuining the conversation, get show of hands to see who will participate on day 3.