Match Report Header and LHN Avatars

Details

As part of https://github.com/Expensify/App/issues/20486, we want to ensure that the avatars match between report headers and LHN. This PR uses the logic from the LHN Options List to display the header avatars.
Fixed Issues

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

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

Step 1. Create one of each of the following reports:

[ ] IOU Report
[ ] IOU Request
[ ] Workspace Expense Report
[ ] Workspace Expense Request

Step 2.

[ ] Open each report and ensure that the avatar style in the header matches the style in the LHN

IOUs

Start a DM between userA and userB.
Click on the plus actions icon next to "write something.." in the compose message box and select "request money".
Click on the expense request preview.
In the expense report, confirm the subheader says From <userA full name>

IOUs children  (IOU Requests)

Continuing from previous. Click on the specific expense in the expense report.
Confirm you see the single expense request view. Confirm the subheader says From <parent IOU report name>
The parent IOU report can be seen in the LHN. In the below screenshot the parent IOU report name is "Marc Glasser owes $20.00" and so the child has that as its subheader.

Click on the subheader and confirm you are navigated up one level to parent.
Create another thread in the expense report, Or a few nested thread. Confirm all thread subheaders show From <parent IOU report name>.

Expense Reports

Create a workspace. As admin userA, invite userB to the workspace.
You should see a workspace chat between the two like so (view for the admin is below, for a member it will look slightly different),

As userB, click on the plus actions button in the compose message and select "request money"
Once requested have userA and userB click on the expense preview to view the expense report.
Confirm userA, the admin sees the subheader, From <userB full name> in <workspace name>

Confirm userB, the member sees the subheader From <workspace name>

Click on the subheader and confirm you are navigated up one level to parent.

Expense Reports children (Expense Requests)

Continuation from the previous section, click on a specific expense request.
Confirm both admin and member sees From <Expense parent report name> in <workspace name>. The Expense parent report name can be seen in the LHN of the expense report.
Create any number of threads or nested threads under the expense report and confirm the subheader for them all is From <Expense parent report name> in <workspace name>.

Click on the subheader and confirm you are always navigated up one level to parent.

For Example,

PR Author Checklist

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

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

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

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

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

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

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

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

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

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/38015950/a6d89463-7630-412f-8455-4d0dbcf664d3

Mobile Web - Chrome

Mobile Web - Safari

https://github.com/Expensify/App/assets/38015950/81a33598-4b02-4a41-9ac1-0e0e3996cd98

Desktop

iOS

Android

https://github.com/Expensify/App/assets/38015950/bde488f7-6b06-4df8-9642-f31e5471f642

I am confused with the number of components that have similiar kind of logic.
HeaderView.
HeaderWithbackButton.
MoneyRequestHeader

I agree with you and thought the same while looking into this. We could refactor here, but I don't think it's a priority.

I checked that mainly HeaderView is used for report headers. Why does the change was made to AvatarWithDisplayName?
Are there only a few types of reports where the header was wrong from the list in the test steps?

AvatarWithDisplayName is only used in the headers, it was using incorrect logic and did not match the LHN.

Can you please also clarify the changed features? for example, which report-related header is changed.

as you can see in this photo, many of the multiple avatars/subscript avatar styles were incorrect and did not match
specifically expense reports, requests, and IOUs are affected

Expense Requests and Expense Reports (IOUs) @parasharrajat

@parasharrajat here's the example case that this PR fixes - https://github.com/Expensify/App/pull/22562#issuecomment-1638665301

@parasharrajat next time you log in and focus on /App issues, it would be great to get back to reviewing this issue.

@parasharrajat for expense reports, requests, and iou report and requests, I will be adding the the following test steps (will add to description too:
IOUs

Start a DM between userA and userB.
Click on the plus actions icon next to "write something.." in the compose message box and select "request money".
Click on the expense request preview.
In the expense report, confirm the subheader says From <userA full name>

IOUs children  (IOU Requests)

Continuing from previous. Click on the specific expense in the expense report.
Confirm you see the single expense request view. Confirm the subheader says From <parent IOU report name>
The parent IOU report can be seen in the LHN. In the below screenshot the parent IOU report name is "Marc Glasser owes $20.00" and so the child has that as its subheader.

Click on the subheader and confirm you are navigated up one level to parent.
Create another thread in the expense report, Or a few nested thread. Confirm all thread subheaders show From <parent IOU report name>.

Expense Reports

Create a workspace. As admin userA, invite userB to the workspace.
You should see a workspace chat between the two like so (view for the admin is below, for a member it will look slightly different),

As userB, click on the plus actions button in the compose message and select "request money"
Once requested have userA and userB click on the expense preview to view the expense report.
Confirm userA, the admin sees the subheader, From <userB full name> in <workspace name>

Confirm userB, the member sees the subheader From <workspace name>

Click on the subheader and confirm you are navigated up one level to parent.

Expense Reports children (Expense Requests)

Continuation from the previous section, click on a specific expense request.
Confirm both admin and member sees From <Expense parent report name> in <workspace name>. The Expense parent report name can be seen in the LHN of the expense report.
Create any number of threads or nested threads under the expense report and confirm the subheader for them all is From <Expense parent report name> in <workspace name>.

Click on the subheader and confirm you are always navigated up one level to parent.

@parasharrajat could you explain what you're referring to as wrong in the screenshot

@parasharrajat ah yes, the UI you sent is correct. In those screenshots, I am only referring to blue text as "header subtitle"

@parasharrajat changes applied

@parasharrajat pushed a fix

@parasharrajat what do you suggest? I can make any updates in this PR

@parasharrajat updated with just height and width

@parasharrajat are you able to help get this review to the finish line today?

@PauloGasparSv Can you treat this PRs as one of your top priorities? It's one of the initiatives that is required before we can close wave3. Thank you!

@PauloGasparSv Can you treat this PRs as one of your top priorities? It's one of the initiatives that is required before we can close wave3. Thank you!

Sure @JmillsExpensify, I'm almost done with reviewing+testing https://github.com/Expensify/App/pull/23860 then I'll review this

Hey, changes look good but I'm getting an error when I try to create a Money Request locally that is blocking me from testing this. I couldn't figure out why this error is happening so I'll try to finish this review and ask for help if the error persists first thing tomorrow.
cc @JmillsExpensify in case we need to reassign this to someone else.

Thanks @PauloGasparSv! Let us know how things go tomorrow. If this still isn't resolved for you, then let's get another reviewer in the mix.

The error is still happening here, I can't create Money Requests. Pretty sure it is unrelated to these changes though.
I think this is happening because the login (and therefore debtorEmail) is missing in personalDetailsList. I'll investigate this a little bit and then point newDot to staging if I can't figure out what's happening so we can merge this.

Sorry for the delay on this, I'm still stuck on that error.
I tried pointing newDot to staging but after the SigninUser request is successful nothing happens. Now the same is happening when I'm pointing locally.
Btw, I also managed to reproduce the error in staging by requesting money from<EMAIL_ADDRESS>specifically (I noticed it didn't have a login in personalDetailsList either).
@JmillsExpensify @grgia I've assigned puller bear here so another engineer can review while I figure this errors out.

Had to step out after I assigned another engineer but now I'm back.
Since this is blocking me from doing other stuff I'll give an update here if I fix my local environment and finish the review.

@PauloGasparSv Can you review the code first? C+ has tested, so I think the review is more important right now.

I managed to test Web now that I'm aware of https://github.com/Expensify/Expensify/issues/301703 and how to bypass it.

Web test
https://github.com/Expensify/App/assets/6564265/e001a4e2-4779-4dfd-856a-888a803e31f7

Merging this right now (won't test other platforms to focus on other issues)

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

🚀 Deployed to staging by https://github.com/PauloGasparSv in version: 1.3.49-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Thanks!

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


🐛 Bug: Textarea Autosuggestions Not Fetching Suggestions When Typing

♻ Reproduction Steps

Go to the feature/page where the textarea with autosuggestions is located.
Begin typing into the textarea.
Observe that no network requests or function calls are made to retrieve suggestions.

✅ Expected Behavior
As the user types in the textarea, there should be calls to retrieve relevant suggestions based on the input, which should then be displayed in the textarea.
❌ Actual Behavior
No network requests or API calls are made, and no suggestions are provided as the user types.
𝌚 CopilotKit Version
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
📄 Logs (Optional)
No response

Hi @ramonmalcolm10, thank you for flagging this. We are looking into this and will get back to you when I hear back from engineering.

@NathanTarbert I did some checks and it's working on Next.js 14 and not working on version 15 with React 19rc.

Ok, that makes sense. We don't officially support Next.js 15 yet because it is bundled with React 19, which is not GA yet.
When React 19 is generally available, we will support Next.js 15


Should unquirck Error 1306. Another application has exclusive access to the file 'C:\salt\var\log\salt\minion

Error 1306. Another application has exclusive access to the file 'C:\salt\var\log\salt\minion'.  Please shut down all other applications, then click Retry.

maybe only with /x /qb!
Stop salt-minion service first

probably needs solution for https://github.com/markuskramerIgitt/salt-windows-msi/issues/32

Quirk fix  https://github.com/markuskramerIgitt/salt-windows-msi/commit/9ec89293b270725ae2fff04c396843e91753ec19
Fix after issue https://github.com/markuskramerIgitt/salt-windows-msi/issues/32

several python.exe processes lingering without the salt-minion service prevented deletion of the file above

I assume we need to stop all minion processes

Fxied by https://github.com/markuskramerIgitt/salt-windows-msi/commit/c9be74be43fb7a86f0d69637c3734d3b7506a29b


EKS Registry is not accessible causing build failure

Using the following inventory:
https://gist.github.com/nadenf/73d7cc843c8887c8b5309268fed64c84

I get the following error:
TASK [../../roles/kubeinit_registry : Check if the registry is up and running] ***************************************************************************************************************************************************************
fatal: [localhost -> <IP_ADDRESS>]: FAILED! =>
{
	"changed": false,
	"cmd": "set -o pipefail\nset -e\ncurl -v --silent --user registryusername:registrypassword https://eks-service1.eks.kubeinit.local:5000/v2/_catalog --stderr - | grep '\\{\"repositories\":'\n# curl -v --silent --user registryusername:registrypassword https://eks-service1.eks.kubeinit.local:5000/v2/openshift/tags/list\n",
	"delta": "0:00:00.060488",
	"end": "2021-05-29 12:49:41.650796",
	"msg": "non-zero return code",
	"rc": 1,
	"start": "2021-05-29 12:49:41.590308",
	"stderr": "",
	"stderr_lines": [],
	"stdout": "",
	"stdout_lines": []
}

And nslookup on eks-service1.eks.kubeinit.local indicates that the domain can't be found.

I'll need to check why it failed for you, I just triggered the end job and it works as it should. https://storage.googleapis.com/kubeinit-ci/jobs/periodic/periodic-eks-libvirt-3-1-periodic-weekly-go/index.html Can you explain here what you changed in the inventory + a description of your environment so I can resproduce it?

From LSB_Release:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=21.04
DISTRIB_CODENAME=hirsute
DISTRIB_DESCRIPTION="Ubuntu 21.04"

And two key changes: (1) Changed from 10.0 -> 11.0 because of a conflict with my network and (2) Added additional nodes e.g. service.

Actually it was caused by me incorrectly setting the bridge mode. Looks good now !

Say we have two nodes (serviceA, serviceB) this will be the process:

Registry is installed on serviceA
Check if registry is running at URL: serviceA.kubeinit.local
Registry is running.
Registry is installed on serviceB
Check if registry is running at URL: serviceA.kubeinit.local
Registry is not running.

Now for some reason serviceB node can not access the registry on serviceA.

So far there is only one services node with the required services to run the cluster, it will have Bind, Apache, a container registry, and HAProxy. This is not a valid configuration.


Agent Kontena::Workers::NodeInfoWorker: publish_node_info: Address not available

On a DigitalOcean instance without private networking, the default /etc/kontena-agent.env KONTENA_PEER_INTERFACE=eth1 fails if the eth1 interface exists, but does not have any address configured:
grep KONTENA_PEER_INTERFACE /etc/kontena-agent.env
KONTENA_PEER_INTERFACE=eth1

ip addr show dev eth1
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 1e:4f:db:dd:5d:bf brd ff:ff:ff:ff:ff:ff

I guess Kontena::Helpers::IfaceHelper#interface_ip does not rescue on Errno::EADDRNOTAVAIL, and that causes Kontena::Workers::NodeInfoWorker private_ip and publish_node_info to fail completely, and not fallback to interface_ip('eth0').
Workaround is to configure explicit KONTENA_PEER_INTERFACE=eth0 or KONTENA_PRIVATE_IP=... to use the node's public IP address.

Symptom of this is that the host node agent does not publish the node_info, leaving weird node info on the master:
 kontena node ls
Name                                                                   Status     Initial    Labels
                                                                       online     yes


FormSelect values can be object

It would be nice is FormSelect values could be objects and not just strings (i.e. instead of this { label: 'Cooking', value: 'cooking' }, be able to { label: 'Cooking', value: {name: 'cooking', id: 3 }}. You are able to do this for the dropdown menu

This is because the underlying DOM is using <select> elements and just returning the element value. <Dropdown> is using <li>'s with values bound to the callback.
This desired effect should be able to be achieved using the same technique, without breaking the existing API.

@annarichardson thanks for contributing
This API is by design. You can derive the id via another method


fix(tui): stop the event handler on quit

Description of change
I realized we are not stopping the event handling loop when the restart command is send.
fixes #13
How has this been tested? (if applicable)
Locally.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 3.67%. Comparing base (236d19e) to head (c3f4a0d).

Files with missing lines
Patch %
Lines

src/lib.rs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #24      +/-   ##
========================================
- Coverage   3.67%   3.67%   -0.00%
========================================
  Files         18      18
  Lines       2212    2213       +1
========================================
  Hits          81      81
- Misses      2131    2132       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Infinite recursion when adding MaxParents(1) constraint

@tlambert03 I assume there is something wrong with my candidate graph that is causing this issue. I tried to add "hyperedges" to model specific division costs. Any tips?
  File "/Users/malinmayorc/code/darts_experiments/src/darts_utils/tracking/solve_with_motile.py", line 17, in solve_with_motile
    solver.add_constraint(motile.constraints.MaxParents(1))
  File "/Users/malinmayorc/code/motile/motile/solver.py", line 110, in add_constraint
    self.constraints.add(constraint)
  File "ilpy/wrapper.pyx", line 234, in ilpy.wrapper.Constraints.add
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 27, in as_constraint
    l_coeffs, q_coeffs, value = _get_coeff_indices(self)
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 268, in _get_coeff_indices
    for var, coefficient in _get_coefficients(expr).items():
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 342, in _get_coefficients
    _get_coefficients(expr.left, coeffs, scale, var_scale)
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 350, in _get_coefficients
    _get_coefficients(expr.left, coeffs, scale, var_scale)
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 350, in _get_coefficients
    _get_coefficients(expr.left, coeffs, scale, var_scale)
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 350, in _get_coefficients
    _get_coefficients(expr.left, coeffs, scale, var_scale)
  [Previous line repeated 988 more times]
  File "/Users/malinmayorc/miniconda3/envs/darts/lib/python3.10/site-packages/ilpy/expressions.py", line 347, in _get_coefficients
    if isinstance(expr.op, (ast.Mult, ast.Div)):
RecursionError: maximum recursion depth exceeded in __instancecheck__

Update: Actually, one of the nodes has 1002 previous edges (from my prints: Node 868 has 1002 prev_edges). This is larger than the max recursion depth set for the ilpy expressions. Is there an easy way to fix this?

(other than reduce my number of edges... which I have now done 😄 )


Corrupted stack - re-push from client

I had a problem with a Cognito resource and somehow my local code got out of sync with the pushed version. I ended up deleting the stack on the AWS account and cleared out the resources. Is there a way to re-push from the local? I fear that an 'amplify init' reset what I've already configured locally.
Any recommendations on best way to recover?

Could you clarify the following

What version of amplify are you using
Did you manage to remove all the resources (like s3, Cognito and IAM resources). Sometimes if your bucket has some content, deleting stack does not remove the bucket

v0.1.27
Yep, removed everything via AWS console by deleting the stack, then manually cleaning up what the stack(s) couldn't do (were out of sync with). For example, I had set the domain on my user pool and the stack couldn't delete it with that set.
Maybe another way to describe what I want to do is: if I start with a clean AWS account and a clone of my git repo that has the amplify backend and my app code (React), how can I run it? amplify init wants to recreate most of what exists in the paramters/api-params files...

You could try these steps manually to recover. ymmv based on how cleanly the stack was deleted.

Create a new project by running amplify init in a new folder
Once the init succeeds, copy everything in the amplify/#current-cloud-backend of your corrupted project to backend of the new project you just created.
Open amplify/backend/amplify-meta.json of the newly created project
copy the json data under the key providers from amplify/#current-cloud-backend/amplify-meta.json from the newly created project and paste it on to amplify/backend/amplify-meta.jsons providers section
Do an amplify push

Closing the issue. Re-open if the recovery step didn't work

This isn't resolved. Still getting Project stack doesn't exist

Chiming in here in case anyone else runs into this: the CloudFormation details are scattered in a lot of places, it's best to just rename your ./amplify folder (maybe ./amplify-old) and run amplify init again within your project and walk through the prompts to set up a new stack. Then amplify add <service> again for the various services. If you are using API/GraphQL, re-add your schemas when prompted. amplify push when you're done to rebuild the stack.

I follow the below steps to tear down my environment on AWS, whilst keeping my local code intact. Basically, we just delete the current environment I'm on, and recreate it.

We need create & switch to the temporary environment (called temp) before we can delete the current one. We can do this by running the below command:
amplify init

Answer the following for the prompt:
? Do you want to use an existing environment? (Y/n) ---> n
? Enter a name for the environment ---> temp
# ... The rest can be left as default

(Optional) After running amplify init, it'd switch you to the new environment. You can check your list of environments, and the currently checked out environment via the amplify env list command.

Remove the existing environment with the below command. This would remove the associated cloud resources as well.
amplify env remove <YourEnvironmentName>

<YourEnvironmentName> should be replaced by whatever your environment is. By default, it's dev.

Now that the environment is deleted, run the below command to re-create it.
amplify init

Answer the following for the prompt:
? Do you want to use an existing environment? (Y/n) ---> n
? Enter a name for the environment ---> dev
# ... The rest can be left as default

Now that we're switched back to our original environment & deleted the cloud resources, we can remove the temporary environment.
amplify env remove temp

Finally, we push the cloud resources for our environment so our AWS resources is re-created.
amplify push

Hit this today, my mental model of what is safe to do and what isn't just isn't solid enough in my head yet and its frustrating that I only seem to find out the boundaries when I hit them. A warning site or a helping hand to pull be back from the brink would be nice.
In my case I deleted some tables from DynamoDB which I'd removed from my schema but hadn't yet pushed those changes.
Misunderstanding #1: I thought that if I removed (or renamed) a table from the schema it wouldn't delete it in DynamoDB as that would be a destructive action, I could be losing data. I understood it that I would have to go in and clean up by hand. Is that not the case anymore? In this case I didn't care about losing data so deleted the table manually.
Misunderstanding #2: That if Amplify can't find a table when pushing (that it doesn't need anymore so shouldn't really care) it could just skip it (with a warning "Hey, I wanted to delete this for you but it appears to already be gone!"). Instead it just blows up and cancels the whole push and leaves me in an unknown state.
This is frustrating when developing but also adds to the terror in your belly about when this stuff goes live. Sure we fly a bit fast and loose in dev mode but I would like to think I can get it back up and running easily if something went wrong in production but having to do the "config/init shuffle!" described by @deltoss above doesn't really fill me with the warm fuzzies in my belly...more likely to bring me out in a cold sweat.
Currently when I've messed up my schema and get the dreaded red lines of doom when I push its difficult to know how to even begin to get back to known state. Need a way to safely "put it right" without having to resort to the "init shuffle".

Old thread, but FWIW, I made the mistake of changing the custom name of a resource and compounded it by deleting stacks. I found a simple solution to restoring the stacks - I created a new environment 'amplify env add ' which allowed me to do a full push and restore a working environment with all necessary stacks. I'm not even sure the push was even necessary - just needed a new environment from which to delete the old one and recreated using 'env add' again. Everything fixed. Of course, you do delete all of your resources, but way easier than going the full 'init', 'add', 'add' route to recreate the app.

Old thread, but FWIW, I made the mistake of changing the custom name of a resource and compounded it by deleting stacks. I found a simple solution to restoring the stacks - I created a new environment 'amplify env add ' which allowed me to do a full push and restore a working environment with all necessary stacks. I'm not even sure the push was even necessary - just needed a new environment from which to delete the old one and recreated using 'env add' again. Everything fixed. Of course, you do delete all of your resources, but way easier than going the full 'init', 'add', 'add' route to recreate the app.


Is there a way to download all domains from https://chaos.projectdiscovery.io/#/

Is there a way to download all domains from https://chaos.projectdiscovery.io/#/ ?
Is there a way to download all domains from https://chaos.projectdiscovery.io/#/

@wesamlibya source information is here - https://github.com/projectdiscovery/public-bugbounty-programs


Clarification regarding new-responder message

What happens if the client receives a new-responder message with an id that is already known? Protocol error?
When does the server start re-assigning already used responder ids? Once the old ones are used up?

I'd have to look into the server code but the server does reassign ids, yes. new-responder with the same ID means that the previous one has disconnected, so it's not an error.

Ok, so new-responder with the same ID will replace the previous responder.

Do we need to update the spec (if it isn't crystal clear)?

Would probably be good, yes. I wanted to do it this morning, but didn't find time do do so yet.

Implemented in https://github.com/saltyrtc/saltyrtc-client-java/pull/32. Protocol PR is at #95.


chore: Update to babel 7 + Typescript

#3 Replaced Flow w/ Typescript and as a result removed Babel because TypeScript both transpiles and type checks. However this makes us miss out on a lot of the plugins that are a part of the Babel community. Babel 7 adds support for Typescript.
Use babel 7 to build assets instead of tsc. The tsc command is still used for static type checking. Note that the babel typescript plugin will transpile code regardless of its typecheck correctyness.
tsc is also still used to generate the declaration files, since it looks as though the babel-typescript-plugin does not support creating those at this time. However there's a "create declaration only" flag that is convenient for this.
I've excluded the .spec files from the babel build, so now they won't appear in lib. I didn't move the ignore declaration into the .babelrc because I can imagine a situation where we might want to use a cool feature in our test suite that babel can transpile for is (even though node 8 gets us there at the moment). However there's never a need to have the transpiled versions in our lib.
Lastly, we can now support async await etc with the additions of lib -- es2015 and dom which I think will be especially useful in our tests because most of our exports will likely be functions that return promises.
PS: i'm not tied to the tests, i just want to prove that they work! I'm happy to remove them, as we definitely should in the future, thought it might be nice while we're building the foundation though.
Fixes #4

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can I keep a database table data in memory？

Not always in disk

you can use Caching. By default it uses a SimpleMapCache which will greedily load all objects from the DB. But there doesnt appear to be a SQLite in-memory equivalent unless you want https://www.sqlite.org/inmemorydb.html


Debugging MediaElement with custom browsers

We have several custom browsers that we built on IE, Chrome, or Safari based upon the operating system. We would like to debug MediaElement issues and would like something that indicates which logic path is being triggered by a certain browser. We would like to see which version of a browser is being detected and whether it is prioritizing HTML5 or Flash media.
Thanks,

@jeffreyspranza Closing old issues. If you'd like to reopen this, let us know. Thanks!


ctx.meta.$responseType not working

I need to return 'Content-Type' as xml and I used the following
ctx.meta.$responseType = "text/csv" as per documentation given in http://moleculer.services/docs/0.13/moleculer-web.html#Response-type-amp-status-code
Sadly it does not work and response goes with Content-Type of application/json ... Could you please get this corrected asap...

I think I found the problem... The code
// Custom responseType from ctx.meta
			if (ctx.meta.$responseType) {
				responseType = ctx.meta.$responseType;
			}

			// Custom headers from ctx.meta
			if (ctx.meta.$responseHeaders) {
				Object.keys(ctx.meta.$responseHeaders).forEach(key => {
					if (key == "Content-Type" && !responseType)
						responseType = ctx.meta.$responseHeaders[key];
					else
						res.setHeader(key, ctx.meta.$responseHeaders[key]);
				});
			}

which is found in the github page is missing in the node_modules folder file.... So $responseHeaders and $responseType are both ignored ... could you please update the npm version to github version to resolve this issue....

My apologies... I  was on older version ... It works like a charm now...


Tidy up

Asana Issue URL: N/A
Description
Tidy up:
• update to latest libs
• remove unused images
• switch to kotlin short formats
• clean up compiler warnings
Steps to Test this PR:
Run the app and ensure it is stable

Thanks for the review :)


AssetBundle is linking scss files in the HTML head

Additional info

Q
A

Yii version
2.0.34

PHP version
7.4.5

Operating system
N/A

I'm following this guide to convert scss files to css files.
In the css array from my AppAsset I have to add scss/myFile.scss to yii runs the converter command, but with this, the AssetBundle renders into the HTML head section the link to the scss file, so I have to add into the same array, the css file css/myFile.css.

Would you please put together a simple test case to reproduce it starting with basic app template and making minimal amount of changes? Thanks.

Frontend App Advanced main config:
<?php

$params = array_merge(
        require __DIR__ . '/../../common/config/params.php', require __DIR__ . '/../../common/config/params-local.php', require __DIR__ . '/params.php', require __DIR__ . '/params-local.php'
);

$from = dirname(__DIR__) . '/themes/grayscale/scss/grayscale.scss';
$to = filter_input(INPUT_SERVER, 'DOCUMENT_ROOT') . "/web/themes/grayscale/css/grayscale.css";

return [
    'id' => 'app-frontend',
    'basePath' => dirname(__DIR__),
    'bootstrap' => ['log'],
    'controllerNamespace' => 'frontend\controllers',
    'components' => [
        'assetManager' => [
            'bundles' => [
                #'yii\web\JqueryAsset' => [
                #    'sourcePath' => null, 'js' => [],
                #],
                'yii\bootstrap\BootstrapAsset' => [
                    'sourcePath' => null, 'css' => [],
                ],
                'yii\bootstrap\BootstrapPluginAsset' => [
                    'sourcePath' => null, 'js' => [],
                ],
                'yii\jui\JuiAsset' => [
                    'sourcePath' => null, 'css' => [], 'js' => [],
                ],
                '\rmrevin\yii\fontawesome\AssetBundle' => [
                    'sourcePath' => null, 'css' => [],
                ],
            ],
            'converter' => [
                'class' => 'yii\web\AssetConverter',
                'commands' => [
                    'scss' => ['scss', "sass $from $to --source-map"]
                ],
                'forceConvert' => true
            ],
            'appendTimestamp' => true,
        ],
        'view' => [
            'theme' => [
                #'class' => yii\base\Theme::class,
                'basePath' => '@app/themes/grayscale',
                'pathMap' => ['@app/views' => '@app/themes/grayscale'],
                'baseUrl' => '@web/themes/grayscale',
            ]
        ],
        'request' => [
            'csrfParam' => '_csrf-frontend',
            'baseUrl' => '/web',
        ],
        'user' => [
            'identityClass' => 'common\models\User',
            'enableAutoLogin' => true,
            'identityCookie' => ['name' => '_identity-frontend', 'httpOnly' => true],
        ],
        'session' => [
// this is the name of the session cookie used for login on the frontend
            'name' => 'advanced-frontend',
        ],
        'log' => [
            'traceLevel' => YII_DEBUG ? 3 : 0,
            'targets' => [
                [
                    'class' => 'yii\log\FileTarget',
                    'levels' => ['error', 'warning'],
                ],
                [
                    'class' => yii\log\SyslogTarget::class,
                    'levels' => ['error', 'warning']
                ]
            ],
        ],
        'errorHandler' => [
            'errorAction' => 'site/error',
        ],
        'urlManager' => [
            'class' => 'yii\web\UrlManager',
            'enablePrettyUrl' => true,
            'showScriptName' => false,
            #'suffix' => '.html',
            'rules' => [
                // tecnorecicla
                'requirement/<action:\w+>' => '/web/requirement/<action>',
            ],
        ],
    ],
    'params' => $params,
];

Frontend App Asset:
<?php

/**
 * @link http://www.yiiframework.com/
 * @copyright Copyright (c) 2008 Yii Software LLC
 * @license http://www.yiiframework.com/license/
 */

namespace frontend\assets;

use Yii;
use yii\web\AssetBundle;
use yii\helpers\FileHelper;

/**
 * @author Qiang Xue<EMAIL_ADDRESS> * @since 2.0
 */
class ThemeAsset extends AssetBundle
{

    /**
     * {@inheritdoc}
     */
    public $sourcePath = '@app/themes/grayscale'; //maybe set also as maybe unset

    /**
     * {@inheritdoc}
     */
    public $basePath = "@webroot/themes/grayscale";

    /**
     * {@inheritdoc}
     */
    public $baseUrl = '@web/themes/grayscale';

    /**
     * {@inheritdoc}
     */
    public $css = [
        'vendor/bootstrap/css/bootstrap.min.css',
        'vendor/fontawesome-free/css/all.min.css',
        "scss/grayscale.scss", // this is the scss inside @frontend/themes/grayscale/scss. This is rendered as <link href="/web/themes/grayscale/scss/grayscale.scss" rel="stylesheet">
        'css/grayscale.css', // this is the compiled scss inside @webroot/themes/grayscale/css
        [
            'href' => "favicon.ico",
            'rel' => 'icon',
            'sizes' => '16x16',
        ],
    ];

    /**
     * {@inheritdoc}
     */
    public $js = [
        #'vendor/jquery/jquery.min.js',
        'vendor/bootstrap/js/bootstrap.bundle.min.js',
        'js/grayscale.min.js',
        "vendor/jquery-easing/jquery.easing.min.js"
    ];

    /**
     * {@inheritdoc}
     */
    public $depends = [
        'yii\web\YiiAsset',
        #'yii\bootstrap\BootstrapAsset',
        #'yii\bootstrap\BootstrapPluginAsset',
    ];

}

Anything in AssetBundle::$css will be treated as CSS you want included on the page.
If you remove "scss/grayscale.scss" it should work as expected.


Weird resolution bug

I have added nanovg into sdl2 and everything works great...
http://i.imgur.com/OrTd448.png
except one thing, as soon as I set non-square resolution:
http://i.imgur.com/szSZTcF.png
or
http://i.imgur.com/PVD1Uuy.png
it breaks anti aliasing or makes it really blurred.
GLfloat ratio = (GLfloat)width / (GLfloat)height;

glClearColor(0, 0, 0, 0);
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT | GL_STENCIL_BUFFER_BIT);

glViewport(0, 0, width, height);

nvgBeginFrame(nanovg_context, width, height, ratio);
...

I've just noticed the same problem.

Hi,
Ratio is is not aspect ratio, but how big a pixel is. For example when you
render on retina screen, you may want to use larger value.
For example in GLFW, you have "window size" and "render buffer size", and
you can use those to derive the pixel ratio:
https://github.com/memononen/nanovg/blob/master/example/example_gl2.c#L129
--mikko
On Thu, Oct 8, 2015 at 12:30 PM, Anton Sazonov<EMAIL_ADDRESS>wrote:

I've just noticed the same problem.
—
Reply to this email directly or view it on GitHub
https://github.com/memononen/nanovg/issues/247#issuecomment-146471358.

Hmm.. I've set devicePixelRatio into 1 and the problem is gone in my case.
nvgBeginFrame( m_vg, width, height, 1 );

Thank you a lot guys! 1.0 also fixed everything in my case.


Cut New Release That Includes OpenSearch

Is your feature request related to a problem? Please describe.
it appears that opensearch has been merged. Can we get v1.0.3 cut?
Describe the solution you'd like
n/a
Describe alternatives you've considered
n/a
Additional context
No response

Although we are currently using fluentbit 1.8.11, users can manually upgrade fluentbit's version. Is there any reason why it must be removed?

I meant an new operator version that includes the k8s control plane changes for this plugin

And cut as in "create a new release" not remove it. Sorry for the lingo

That's a new feature added, so the new release could be v1.1.0

That works too 🙂

@benjaminhuo when would you be able to create the new tag/release/assets?

@frankgreco Hopefully in a week

v1.1.0 has been released, close this issue.


Runs but stops suddenly

I was running https://colab.research.google.com/drive/15_sd1tymWK-HPK88iWb12AP8j0U8hZXG
By adding the torchmetrics part in step 2.
But since this week I have not been able to use it because it immediately stops after step 3 shows "startup complete". Sometimes I am able to generate 1 single image and then step 3 stops running and turns red. Any idea what is happening?

another colab paid restriction...


Create clean example for using Dask with the Instacart dataset

We currently have two scripts in the dask-entity branch for running the Instacart dataset with Dask. One script requires a separate preprocessing script to be run and contains unused machine learning code. The second script does not use compose and has not been tested recently with recent dask related code updates.
These examples should be cleaned up to have either a single script or a notebook that explains how to use Dask to generate a feature matrix from this dataset.

Closed by #956


Error: EISDIR: illegal operation on a directory, read     at Object.readSync

Fresh Expo install of Ignite, when I run the app in Expo on my Android phone, I see the error below. This was happening on Node V14, I upgraded to the latest Node v15 (as the metro server seemed to keep crashing too), this has solved the crashing but I'm still getting the debug error.
Finished building JavaScript bundle in 1293ms.

Running application on ONEPLUS A6003.

Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (node:fs:617:3)
    at tryReadSync (node:fs:382:20)
    at Object.readFileSync (node:fs:419:19)
    at UnableToResolveError.buildCodeFrameMessage (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)
    at new UnableToResolveError (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)
    at ModuleResolver.resolveDependency (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)
    at DependencyGraph.resolveDependency (/Users/user/Sites/sitename/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)
    at /Users/user/Sites/sitename/node_modules/metro/src/lib/transformHelpers.js:271:42
    at /Users/user/Sites/sitename/node_modules/metro/src/Server.js:1097:37
    at Generator.next (<anonymous>)

Here's Ignite Doctor:
System
  platform           darwin
  arch               arm64
  cpu                8 cores      Apple M1
  directory          name        ~/Sites/name

JavaScript (and globally-installed packages)
  node               15.9.0       ~/.nvm/versions/node/v15.9.0/bin/node
  npm                7.6.1        ~/.nvm/versions/node/v15.9.0/bin/npm
    npm              7.6.1
    yarn             1.22.10
  yarn               1.22.10      ~/.nvm/versions/node/v15.9.0/bin/yarn

Ignite
  ignite-cli         6.2.0        ~/.npm-packages/bin/ignite
  ignite src         build        ~/.npm-packages/lib/node_modules/ignite-cli/build

Android
  java               1.8.0_282    /usr/bin/java
  android home       -            undefined

iOS
  xcode              12.4
  cocoapods          1.10.1       /usr/local/bin/pod

Not sure if this is a related issue or separate - I'm also getting really weird flashing screen transitions when I move pages. This doesn't happen on my IOS simulator (connected to the same metro instance), but is happening on Android.
https://user-images.githubusercontent.com/2121331/110394884-49322a80-80c1-11eb-8054-d82e64878db7.mp4

@jascination do you use "react-native-reanimated"? removing it seems to help

Still happening for me on the latest CLI (6.4) using expo in the IOS simulator; react-native-reanimated isn't a dependancy so no help there.

Are all of you folks on Apple M1 architecture?

@jamonholmgren Yep, I'm on the M1

not on M1, but i think "Error: EISDIR" might be connected to mobx-state-tree, for example i encountered it again when i wrote types.boolean instead of types.maybeNull(types.boolean) and it   couldn't assign undefined to boolean. Also got it when i accidentally created store model with the same name of existing one

i have sometimes same issue , someone told on github that is known metro issue , what helps me to do is the next :
watchman watch-del-all; rm -rf ./ios/build;  rm -rf ./ios/Pods; rm -rf $TMPDIR/react-*;rm -rf $TMPDIR/haste-*; rm -rf $TMPDIR/metro-*; rm -rf node_modules/; npm cache verify; yarn; npm start --reset-cache

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.


MarkdownEditor should allow lazy-loading suggestions

In order to reduce API load and improve time-to-render, we want to lazy-load suggestions in Projects by waiting until the suggestions are actually needed before making the API request (see https://github.com/github/memex/issues/12396). The MarkdownEditor doesn't support this at the moment, so it would like require changing the props to accept functions instead of (or in addition to) the suggestion arrays.
I am already working on this; just opening an issue to track over here.

cc @anleac as we discussed this topic today while working on https://github.com/github/issues/issues/3377


Field TabIndex incorrect after enum field refresh

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

What is the current behavior?
The TabIndex of a field type enum isn´t correct after the field was refreshed.

If the current behavior is a bug, please provide the steps to reproduce and if possible a screenshots.

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Link to jsFiddle that demonstrates the problem:

Other information
Problem is tabIndex at function "addMulti"  is being checked as number but it is a string.
So the check against -1 will always return true.

Closing issue: fixed


v1.2.3

Coverage remained the same at 100.0% when pulling 86016000dec2c139ee7411d32bb156d2957e00ab on staging into 700574c2035ed53fec7921a1f7f7c7994bac7055 on master.


Support for Soundcore Liberty Air 2 Pro

Hey, no rush on this because I respect any free tweak dev greatly, but support for these earbuds would be great. I've tried them and while the settings show up they do not work.

Completed, now available on Chariz


Enable noImplicitAny in the tsconfig

We're at a point where the types are pretty good in the source files, it's mostly the tests that are still messed up.  Lets close this TypeScript thing out :)

@joecervino this one's for you!

@JustinBeckwith Never got the ping - I'll do it asap


Add CircleCI

Does linting for now and package build (automatically on npm install).
Better then nothing =)

See build results for this PR: https://circleci.com/gh/nkbt/elemental/2
Shows lint warnings (but does not break the build). if there are lint errors - will break.

Needs project owner to allow access, so it can hook up with all PRs and commits

Good call @nkbt, thanks. Not sure why you don't already have access, I'm setting it up now.

Hmm, for some reason I still can't add elemental project to circleci


Prometheus scrape endpoint

It also fixes the OTEL metrics units from milliseconds to seconds, to be consistent with the latest OpenTelemetry specification.
Most of the PR files are just vendored dependencies

Codecov Report

Merging #110 (9b51b0b) into main (94bcce3) will decrease coverage by 30.60%.
The diff coverage is 19.33%.

@@             Coverage Diff             @@
##             main     #110       +/-   ##
===========================================
- Coverage   75.38%   44.78%   -30.60%
===========================================
  Files          21       22        +1
  Lines        1503     1601       +98
===========================================
- Hits         1133      717      -416
- Misses        276      833      +557
+ Partials       94       51       -43

Flag
Coverage Δ

integration-test
?

unittests
44.78% <19.33%> (-3.28%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/ebpf/tracer.go
0.00% <0.00%> (-63.22%)
:arrow_down:

pkg/pipe/config.go
53.33% <ø> (ø)

pkg/export/prom/prom.go
1.40% <1.40%> (ø)

pkg/export/otel/traces.go
78.85% <57.14%> (-0.88%)
:arrow_down:

pkg/export/otel/metrics.go
70.88% <100.00%> (-8.45%)
:arrow_down:

pkg/pipe/global/context.go
100.00% <100.00%> (ø)

pkg/pipe/instrumenter.go
82.14% <100.00%> (-8.49%)
:arrow_down:

pkg/transform/spanner.go
80.95% <100.00%> (-2.39%)
:arrow_down:

... and 12 files with indirect coverage changes


soc: arm: nordic: Remove enabling of temperature sensor

nrf51 and nrf52 by default was enabling temperature sensor if sensor
API was enabled. It was causing code size increase even when
temperature sensor was not touched by anyone. Removed default enabling
of temperature sensor for both series.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

Isn't the die temperature used for clock calibration?

Isn't the die temperature used for clock calibration?

It might be if RC is a source for 32k clock but then clock driver is enabling it.


Support more atomic_rmw ops

Feature
Support the following operations:

(u){min,max}
nand

Benefit
This is required for implementing certain rust intrinsics.
Implementation

Alternatives

Use a global lock instead of atomic instructions in cg_clif (bad perf)
Don't implement these stable operations in cg_clif

Looks like LLVM uses cmpxchg for these. I guess I could lower to that manually in cg_clif.


Bugfix/panic with invalid fillers

Fixed a panic when a struct was being filled with an incomplete filler i.e. there is a missing or misspelled setting.

Coverage decreased (-2.9%) to 97.122% when pulling d61e4b75cff6db5fbf31a5a70a05b5f6961d4480 on bugfix/panic_with_invalid_fillers into a3fdbf5d885c8555963a30c0dcd0891788e39d6c on master.

I'd like to point out that if the bit of code that coveralls believes is not tested was not executed as part of the added test, the test would fail...

Coverage decreased (-2.9%) to 97.122% when pulling 45f8060095d61e4b99b7721f5b86c52d39cbf12e on bugfix/panic_with_invalid_fillers into a3fdbf5d885c8555963a30c0dcd0891788e39d6c on master.

Removed the else block and Stalin.

Coverage decreased (-1.09%) to 98.905% when pulling cb63a6c3b1e7b495a92a4b1c9915a02498617508 on bugfix/panic_with_invalid_fillers into a3fdbf5d885c8555963a30c0dcd0891788e39d6c on master.

Coverage remained the same at 100.0% when pulling eac34e4753e6380918b4f8e1c1874aac40eab743 on bugfix/panic_with_invalid_fillers into a3fdbf5d885c8555963a30c0dcd0891788e39d6c on master.


Explanation of Extra Embeddings after generation from Dict

What is your question?
Hi! I am trying to extract word embeddings and do some analysis on a transformer model I trained. Compared to the srcdict used to generate the emeddings the 'encoder.embed_tokens.weight' seems to have 4 more tokens. Can someone confirm if these extra or special tokens are at the end, beginning or somewhere else. Also, is the order of the srcdict maintained when initializing the embedding matrix.
Thanks!

Hello, the source dict models special tokens in the dictionary, such as unk and start of sentence. The order is maintained and they are always appended at the beginning. You can see the tokens added if you check the dictionary.py file.

Thanks I got my thing to work :)

fantastic!


Selenium module updates

create page models
use page models instead of having the elements in unit test class
separated UIWaitUnitTest into UIWaitForUnitTest and UIWaitUntilUnitTest

closing this PR as it is no longer needed


I cant mining gravilite block with v20.1.20 in Better MC

I've tried using a diamond pickaxe with silk touch, and a netherite pickaxe with silk touch, but not working.
I can not get the gravilite block.
And the same as gravity compressor.

Will be Fixed in 21.0.0


Dapr ServiceBus component requests messages it has no capacity to process

In what area(s)?
/area runtime
What version of Dapr?
0.6.0
Description
numConcurrentHandlers setting of ServiceBus component allows to configure how many concurrent calls Dapr can make to the subscriber backend. However, it looks like the setting does not limit how many messages Dapr requests from ServiceBus and so Dapr can receive too many messages (it tries to read all available messages). All these messages are sitting in Dapr waiting to be processed and after their lock duration expires they will be redelivered again, causing duplicate deliveries and increasing delivery counts. After "Max Delivery Count" deliveries ServiceBus moves the message(s) into dead-letters queue.
Steps to Reproduce the Problem
My testing setup:
Max Delivery Count = 10
Message Lock Duration = 60 sec
numConcurrentHandlers  = 1
My application takes 45 sec to process a message (I added 45 sec sleep to make reproduction easier)
I deployed my subscriber app when there were 20 messages in the queue. In my app's logs I started seeing that the messages are being delivered one by one (exactly as expected with numConcurrentHandlers = 1). After ~10 minutes a few messages are processed and most of the messages are in dead-letters queue but my subscriber app continues to receive calls from Dapr for the messages that are already in the dead-letters queue (and each message is delivered multiple times even though my app responded with 200).
Expected Behavior
Dapr should only try to receive a message from ServiceBus if it can immediately send it to the backend for processing.

@programaka thanks for reporting this. Do you have any other concurrency controls on dapr i.e. https://github.com/dapr/docs/tree/master/howto/control-concurrency? Do you know if your app is dropping any requests? Could you increase the handlerTimeoutInSec to 120 and report back please.

@jjcollinge No, I don't have any concurrency control enabled on dapr and I see no indications of my app dropping requests. What I see in my logs is in line with what I would expect with "numConcurrentHandlers = 1" setting. How increasing handlerTimeoutInSec from 60 to 120 would change anything when my handler takes 45 seconds to respond? I did try to use a smaller delay in my app (15 sec instead of 45 sec) with same results.
Please note that the concern is how Dapr reads from Service Bus, not how it calls my backend (which works as expected).

Ok understood, thanks. My hunch is that because the underlying sdk we use (https://github.com/Azure/azure-service-bus-go) has 2 control loops, 1 to receive the messages and 1 to handle the messages, the first is receiving the messages as fast as possible and pushing them onto an in memory channel and becasue numConcurrentHandlers is throttling the handler this is causing back pressure on the channel, your default lock duration is set to 60, therefore, if these messages don't get processed in this time the subscriber will be able to fetch them again and you'd end up with multiple copies in the channel waiting to be processed. If this gets to the point where each message has been fetched more than 10 times (MaxDeliveryCount) then they'll get deadlettered on Service Bus but there will still be some left on the in memory channel waiting to be processed. We may have to change from calling Receive to calling ReceiveOne so we have more control over the receive loop. I don't see any mechanism in the sdk to throttle the receive loop but I will raise an issue to discuss it.

We should move this issue to the component-contrib repo.

I've opened a PR with a potential fix for this: https://github.com/dapr/components-contrib/pull/329.
I've done the following smoke test;
2 apps, both have a different topic handler that waits 10 seconds.
app A has numConcurrentHandlers=1 set. app B does not have it set.
The ASB has a lock duration of 30 seconds and max delivery count of 1.
I publish 100 messages to both topics.
For app B - dapr fetches the messages as fast as possible and invokes the apps handler 100 times in quick succession and waits for the responses.
For app A - dapr fetches 1 message at a time and invokes the app handler once per message.
In neither case did any messages get dead lettered.
@programaka are you able to build dapr with this change and test if it fixes your issue?

Hmm trying this out with your parameters still seems to result in some dead lettering - I'll investigate later.

I've added a general lock renewal mechanim now - however, I'm still seeing deadlettering occur on long running processes. I think it might be the prefetch buffer in the SDK (defaults to 1). If you set prefetchCount to 0 you receive no messages. I'll have to look at this more tomorrow.

I think my PR should now resolve this, @programaka are you able to test it?

@jjcollinge Thanks for looking into this Joni. I will look at your changes and test it.

@jjcollinge There are a number of new configuration settings added in the PR. Would you recommend to use the default values for my scenario or some custom ones?
I am also a bit concerned that renewing the lock might affect the scaling since locked messages will be waiting in the instance that locked them instead of being sent to newly added instances (as the number of instances scales up). What do you think?

@programaka I think the default lock renewal should be ok for your scenario - you might be able to increase lockRenewalInSec if per is an issue. You can use maxActiveMessages to control how many messages you are currently refreshing locks for - it defaults to 10000 which is effectively unbounded (i.e. pull as many as possible) but hopefuly stop before OOM error. In your case if you have lots of messages on the subscription and slow processing I'd throttle this down, maybe even to 1 if latency isn't your primary concern. That would mean you are pulling messages 1 at a time. It's been behaving as expected in my testing but I'm keen to get more evidence.

@jjcollinge
Ran a couple of tests on your branch of components-contrib and release-0.7 branch of dapr runtime. Same setup as in the issue description, but different pubsub configurations.

  - name: numConcurrentHandlers
    value: 1
  - name: maxActiveMessages
    value: 1
  - name: lockRenewalInSec
    value: 0

From my app logs it looks like numConcurrentHandlers was not respected. All messages came at the same time (was 5 messages in service bus queue).
my subscriber app logs:
Batch Processor listening on port 3000!
5/11/2020, 14:27:30.837<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2322
5/11/2020, 14:27:30.863<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2400
5/11/2020, 14:27:30.870<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2500
5/11/2020, 14:27:30.878<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2600
5/11/2020, 14:27:30.885<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2700
5/11/2020, 14:28:12.452<PHONE_NUMBER>0000000000000000000000 received batch:<PHONE_NUMBER>2800
5/11/2020, 14:28:15.858<PHONE_NUMBER>0000000000000000000000 getting an array of orders from batch:<PHONE_NUMBER>2322
5/11/2020, 14:28:15.938<PHONE_NUMBER>0000000000000000000000 getting an array of orders from batch:<PHONE_NUMBER>2400
5/11/2020, 14:28:15.942<PHONE_NUMBER>0000000000000000000000 getting an array of orders from batch:<PHONE_NUMBER>2500
5/11/2020, 14:28:15.946<PHONE_NUMBER>0000000000000000000000 getting an array of orders from batch:<PHONE_NUMBER>2600
5/11/2020, 14:28:15.951<PHONE_NUMBER>0000000000000000000000 getting an array of orders from batch:

  - name: numConcurrentHandlers
    value: 1
  - name: maxActiveMessages
    value: 1

In this test I see that I do have only one concurrent handler. There was about 20 messages in service bus queue. The first 5 messages are handled successfully and 200 is returned to dapr. And then I am seeing dapr tries to redeliver the last 2 messages over and over again (no new messages are delivered). On those retries I am responding with 200 as well.
I am also getting some errors in dapr runtime:

@programaka thanks for testing. In test 1 - numConcurrentHandlers is not respected as it has been renamed to maxConcurrentHandlers - sorry about the subtle change, it was to make it consistent with the new properties.
For test 2 - This will suffer the same issue and not be throttling handlers but will be throttling the subscriber. However, there is still an issue here with the lock expiration I need to investigate.

@jjcollinge Thanks for all the details, it was really helpful!
I tried these 2 test cases and everything is running smoothly, no more duplicate messages and no errors in dapr logs. I would like to run a couple more tests tomorrow and will let you know if I see any issues.
Test 1
  - name: maxActiveMessages
    value: 1
  - name: lockRenewalInSec
    value: 10

Test 2
  - name: maxActiveMessages
    value: 1
  - name: lockRenewalInSec
    value: 0
  - name: maxDeliveryCount
    value: 2

(instead of increasing lockDurationInSec I reduced sleep from 45 to 25 sec)

@programaka hey, just checking if you managed to run the additional testing you mentioned yet?

@jjcollinge hey Joni, I have run a couple of more tests, including in AKS. I ran it with 10 active messages and also tried scaling number of pods up and down. There were no dead letters.
The set of settings became pretty complex now so I would recommend to extend documentation with extra details on how to use them.


mkdocs init

As long as the extensions and plugins are within the same set as the main lagoon repo - https://github.com/uselagoon/lagoon/blob/main/mkdocs.yml
You can just reuse the github action there here https://github.com/uselagoon/lagoon/blob/main/.github/workflows/mkdocs.yml

@tobybellwood just noticed this PR is here - is this still good to go?

@tobybellwood just noticed this PR is here - is this still good to go?

I'd say it might be worth checking locally again first... it's been a while :D


mWeb/Chrome - Workspace - Invite button hidden behind keypad

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: 9.0.43-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Launch both mweb and Android
Go to workspace -- invite members
Go offline and note no internet connection above
Select a member and tap next

Expected Result:
In mweb and Android, in offline inviting members, invite button should display in same way
Actual Result:
In mweb, invite button hidden behind keypad but in Android above keypad
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/250bd971-ef81-4694-8012-d676e6cf96b1
View all open jobs on GitHub

@twisterdotcom  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Ahh @Nodebrute are you on iOS there? I didn't test that, it wasn't included in the report. Let me double check then.

https://github.com/user-attachments/assets/1cfab2bb-a2a8-4190-b93d-58fe3d00010a

Okay agreed. This has nothing to do with being offline/online either though. It just occurs regardless. Not sure what all the bottom padding is for either when you scroll with the keyboard in view. Can we fix that too @Nodebrute?

@Krishna2323 Thanks for your proposal!

The privacy link is render as footerContent which is rendered below the submit button.

Does this cause the Invite button hidden issue? Or it's another issue found when investigating the issue?

I think we should go with @Nodebrute 's proposal as they're the first to point out the root cause and suggested a fix.
Setting shouldEnableMaxHeight property for ScreenWrapper fixes the issue.
🎀👀🎀 C+ reviewed

Payment Summary:

@Nodebrute paid $250 here (Contributor)
@eh2077 paid $250 via NewDot Manual Request

Checklist

[x] [@eh2077] The PR that introduced the bug has been identified. Link to the PR: After searching the commit histories, I don't think this is a bug introduced by a recent PR. It's more likely an edge case that was uncovered
[x] [@eh2077] 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: N/A
[x] [@eh2077] 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] [@eh2077] Determine if we should create a regression test for this bug. No, because it's a minor change of style and won't impact the main user flow.

Requested payment in NewDot

$250 approved for @eh2077


Approval avatars

Add avatars of pending users on the admin panel

Add contributor avatars of pending items on the admin panel

👀


[lab] Reflect draft pattern of picker value in implementation

Based on https://github.com/mui-org/material-ui/pull/24366 (diff)
I originally misidentified that usePickerState needs getDerivedStateFromProps. I believe now that usePickerState implements the draft pattern but the previous implementation used useEffect. However, that pattern can be implemented without needing to commit twice. The React docs go over this in more detail: https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html#recap (look for usage of "draft").
We still have cascading updates (https://mui-dashboard.netlify.app/test-profile/212342/details/<DatePicker %2F> render proper month).
Latest test_profile on next: https://mui-dashboard.netlify.app/test-profile/212357
Latest test_profile on this PR: https://mui-dashboard.netlify.app/test-profile/212342

@eps1lon How about we only include this label when impacting all the picker components?

It seems good enough, it solves the need for a long list of distracting labels.

@eps1lon How about we only include this label when impacting all the picker components?

It seems good enough, it solves the need for a long list of distracting labels.

How about we only include this label when impacting all the picker components?

but the label is named after a single component prefixed with Date?

It seems good enough, it solves the need for a long list of distracting labels:

What is "the need for a long list of distracting labels"? Why do you find labels distracting?

We use a similar tradeoff with the DataGrid vs. XGrid:

Why is this an argument?

How about we only include this label when impacting all the picker components?

but the label is named after a single component prefixed with Date?

It seems good enough, it solves the need for a long list of distracting labels:

What is "the need for a long list of distracting labels"? Why do you find labels distracting?

We use a similar tradeoff with the DataGrid vs. XGrid:

Why is this an argument?

Anyway, please open this discussion in another issue if you have identified an issue that you think needs solving. Until then please don't spam the repo with things only you need.

Anyway, please open this discussion in another issue if you have identified an issue that you think needs solving. Until then please don't spam the repo with things only you need.

Went over this again and again. Worst case scenario is that it will reveal some code that relies on cascading updates.

Went over this again and again. Worst case scenario is that it will reveal some code that relies on cascading updates.


Backend documentation & API documentation

Task Description
Add backend code documentation and API documentation
Technical Considerations
Swagger and Compodoc can be used to automatically generate docs using NestJs builtin modules
Additional Considerations

Hi @Kerosz are you proposing using postman or maybe a proper documentation using maybe gitbook??

Hello @LuluNwenyi this has already been addressed, currently using swagger for the API documentation, and compodoc for the  BE code, being live here docs.dekoo.tk
Reason for the issue not being closed yet, it's because it's an epic spanning across sprints with the purpose of the team continuously adding the documentation and comments in the code for these tools to be able to extract it,


Update LICENSE

Codecov Report

Merging #158 (e541b50) into main (af1ba5a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #158   +/-   ##
=======================================
  Coverage   67.21%   67.21%
=======================================
  Files          14       14
  Lines        1449     1449
=======================================
  Hits          974      974
  Misses        371      371
  Partials      104      104

Continue to review full report at Codecov.

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


Display hostname in confirmation message when sharing eval to promptfoo server

Using the promptfoo CLI, if I'm sharing the latest eval to a self-hosted server (following these instructions), it would be nice if the confirmation message included the hostname it was sharing to.
That is, change this message:
Create a private shareable URL of your most recent eval?

To proceed, please confirm [Y/n]

to something like:
Create a private shareable URL of your most recent eval on promptfoo.example.com?

To proceed, please confirm [Y/n]

Since the hostname is set via an environment variable, having this confirmation would re-assure someone that they are indeed sending it to their instance, and not the public one.

Good suggestion!  Done in #1183

Thanks so much for this suggestion, @efung, and for all your other helpful suggestions. We released a fix for this in 0.72.1.


Refactor CoAP adapter

REFACTOR
Simplify CoAP adapter. Remove adapter logic from the transport layer and move it to the service implementation. Test for data race and optimize (currently, 4 goroutines are started on a single connection). Make session handling transparent so that it can be replaced with a scalable solution such as storing it in the Redis.

@dusanb94 is this one fixed?

Related to, and blocked by: https://github.com/absmach/coap-cli/pull/8, https://github.com/absmach/coap-cli/pull/7, https://github.com/absmach/mproxy/pull/60, https://github.com/absmach/mproxy/pull/43, #1963, #2206, #2183.


Add date support

This is the first step to adding date and time support, and we want to start by the simplest case: a date without a timezone like 12/23/2016. Since this is timezoneless, it doesn't represent a period in time, it's literally just a convenience for data entry.
Ideally, we would be able to reuse some of the work around Text value to simplify type handling in JSON marshalling, StructScan, and other things like that.
(Future work is to add types for date_with_tz as well as time. Other future work will be to support operations on these types such as now() + 5 days.)

Research

https://github.com/markets/jekyll-timeago
https://github.com/moment/moment/blob/497f918515ae6ab900f008f19523b1e4ae5e2450/src/locale/en-ie.js
https://github.com/scrapinghub/dateparser
https://github.com/wanasit/chrono


Minor tidy ups with flake8

Current coverage is 51.27%

Merging #489 into master will decrease coverage by -0.02% as of f867fcb

@@            master    #489   diff @@
======================================
  Files           89      89
  Stmts         3967    3965     -2
  Branches       405     405
  Methods          0       0
======================================
- Hit           2035    2033     -2
  Partial         52      52
  Missed        1880    1880

Review entire Coverage Diff as of f867fcb

Powered by Codecov. Updated on successful CI builds.

Thanks for your work, I've merged this with minor tweaks.


Login: Wrong username causes 500 error

Gogs version (or commit ref): v0.9.97
Operating system: Debian
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[x] No (I assume it does not run behind a reverse proxy)
[ ] Not relevant

Log gist: (Nothing special)

Description
When I try to login with a non-existent username I always get a 500 error. When I however just use an existent username with a wrong password, the usual error message is shown.
Note: Gogs runs behind nginx as a reverse proxy in my configuration.
Possibly related to https://github.com/gogits/gogs/issues/3605

I'm running Gogs 491407ddf89fb4182c5401c47d2af38f0a30adca behind Nginx 1.10.1 with a location ^~ /gogspath/ { proxy_pass http://<IP_ADDRESS>:3000/; } config and I cannot reproduce your problem.

Yeah, I have a similar setup...
However I always get this error.

Is is a 500 error from nginx or gogs?
Can you try running gogs from the command line with ./gogs web and see what shows in the log when you encounter this? Maybe supply your nginx gogs location part + [server] part of custom/conf/app.ini?

The error is from nginx, but it must be caused by Gogs somehow as the site requests with a valid name and an invalid password

Can you try running gogs from the command line with ./gogs web and see what shows in the log when you encounter this?

I did this already. The result is nothing is logged there...

Maybe supply your nginx gogs location part + [server] part of custom/conf/app.ini?

There is nothing special:
[server]
ROOT_URL      = https:/mysite.example/subdir/
HTTP_ADDR     = <IP_ADDRESS>
HTTP_PORT     = 12345
OFFLINE_MODE  = true

So now I tested it without nginx as a reverse proxy by sending request to Gogs directly and I could confirm my assumptions:
Correct user name: HTTP/1.1 200 OK and HTML document is returned
Wrong user name: HTTP/1.1 500 Internal Server Error and nothing (0 bytes) is returned

Can't reproduce this issue on Gogs <IP_ADDRESS>3. Maybe try to upgrade to newest version.

I'll test it again when a new stable is released.

I posted on #3605 . It appears that there are some problem on user validation logic.
Using v0.9.91 and SMTP external authentication I always get error 500 both on clone or pull commands from git.
If I rollback to v0.9.71 the problem disappears.
The following log is generated.
[Macaron] 2016-09-09 08:27:47: Started GET /gti/fenix.git/info/refs?service=git-uplo
[Macaron] PANIC: runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:458 (0x434743)
/usr/local/go/src/runtime/panic.go:62 (0x43329d)
/usr/local/go/src/runtime/sigpanic_unix.go:24 (0x449644)
/home/vagrant/gopath/src/github.com/gogits/gogs/models/login_source.go:491 (0x5609a9
/home/vagrant/gopath/src/github.com/gogits/gogs/models/login_source.go:549 (0x560fbd
/home/vagrant/gopath/src/github.com/gogits/gogs/modules/auth/auth.go:129 (0x803531)
/home/vagrant/gopath/src/github.com/gogits/gogs/modules/context/context.go:165 (0x84
/usr/local/go/src/runtime/asm_amd64.s:481 (0x4646b6)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/github.com/go-macaron/session/session.go:186 (0x74d665)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/recovery.go:161 (0x7f642b)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/logger.go:43 (0x7f55fe)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/router.go:184 (0x7f77bc)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/router.go:286 (0x7ef98e)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/macaron.go:177 (0x7e7cab)
/usr/local/go/src/net/http/server.go:2202 (0x70144d)
/usr/local/go/src/net/http/server.go:1579 (0x6fde57)
/usr/local/go/src/runtime/asm_amd64.s:2086 (0x4670a1)

fixed by a recent commit.

应该是同样问题，nginx反向代理后，无法登陆
v<IP_ADDRESS>1
2016/11/18 16:26:38 [T] Custom path: /data/gogs/custom
2016/11/18 16:26:38 [T] Log path: /data/gogs/log
2016/11/18 16:26:38 [I] Git Server <IP_ADDRESS>1
2016/11/18 16:26:38 [I] Log Mode: File(Info)
2016/11/18 16:26:38 [I] Cache Service Enabled
2016/11/18 16:26:38 [I] Session Service Enabled
2016/11/18 16:26:38 [I] Mail Service Enabled
2016/11/18 16:26:38 [I] Notify Mail Service Enabled
2016/11/18 16:26:38 [I] Git Version: <IP_ADDRESS>
2016/11/18 16:26:38 [I] SQLite3 Supported
2016/11/18 16:26:38 [I] Run Mode: Production
2016/11/18 16:26:38 [T] Doing: CheckRepoStats
2016/11/18 16:26:38 [I] Listen: http://<IP_ADDRESS>:3000
[Macaron] 2016-11-18 16:26:43: Started GET /user/login for <IP_ADDRESS>
2016/11/18 16:26:43 [D] Session ID: 220f5622222ae932
2016/11/18 16:26:43 [D] CSRF Token: thn45jMlioVl----------------DMwNQ==
[Macaron] 2016-11-18 16:26:43: Completed /user/login 200 OK in 2.21451ms
2016/11/18 16:26:43 [D] Template: user/auth/signin
[Macaron] 2016-11-18 16:26:43: Started GET /img/favicon.png for <IP_ADDRESS>
[Macaron] [Static] Serving /img/favicon.png
[Macaron] 2016-11-18 16:26:43: Completed /img/favicon.png 200 OK in 5.747248ms
[Macaron] 2016-11-18 16:26:50: Started POST /user/login for <IP_ADDRESS>
2016/11/18 16:26:50 [D] Session ID: 220f5622222ae932
2016/11/18 16:26:50 [D] CSRF Token: thn45jMlioVl----------------DMwNQ==
[Macaron] PANIC: runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:458 (0x434743)
/usr/local/go/src/runtime/panic.go:62 (0x43329d)
/usr/local/go/src/runtime/sigpanic_unix.go:24 (0x449644)
/home/vagrant/gopath/src/github.com/gogits/gogs/models/login_source.go:491 (0x5609a9)
/home/vagrant/gopath/src/github.com/gogits/gogs/models/login_source.go:549 (0x560fbd)
/home/vagrant/gopath/src/github.com/gogits/gogs/routers/user/auth.go:107 (0x8cc303)
/usr/local/go/src/runtime/asm_amd64.s:480 (0x4645ec)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/github.com/go-macaron/session/session.go:186 (0x74d665)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/recovery.go:161 (0x7f642b)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:104 (0x7e3316)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/logger.go:43 (0x7f55fe)
/usr/local/go/src/runtime/asm_amd64.s:479 (0x46453c)
/usr/local/go/src/reflect/value.go:434 (0x4f6148)
/usr/local/go/src/reflect/value.go:302 (0x4f5a64)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:177 (0xb1a2f3)
/home/vagrant/gopath/src/github.com/go-macaron/inject/inject.go:137 (0xb19cb2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/context.go:113 (0x7e33f2)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/router.go:184 (0x7f77bc)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/router.go:286 (0x7ef98e)
/home/vagrant/gopath/src/gopkg.in/macaron.v1/macaron.go:177 (0x7e7cab)
/usr/local/go/src/net/http/server.go:2202 (0x70144d)
/usr/local/go/src/net/http/server.go:1579 (0x6fde57)
/usr/local/go/src/runtime/asm_amd64.s:2086 (0x4670a1)
[Macaron] 2016-11-18 16:26:50: Completed /user/login 500 Internal Server Error in 3.070465ms

I am currently experiencing a similar problem when trying to login with ldap.

I believe this was fixed in https://github.com/gogits/gogs/commit/7c1fbed05764ff27c0684df92961a030e2e3344b which is right after 0.9.97 release.


Build failure: yubioath-flutter

Steps To Reproduce
Steps to reproduce the behavior:

build yubioath-flutter

Build log
error: builder for '/nix/store/jalgglf19k4zfh6c5yv18kmkxw6xlw6q-yubioath-flutter-helper-6.1.0.drv' failed with exit code 1;
       last 10 log lines:
       > installing
       > Executing pipInstallPhase
       > /build/source/helper/dist /build/source/helper
       > Processing ./authenticator_helper-0.1.0-py3-none-any.whl
       > Requirement already satisfied: zxing-cpp in /nix/store/dxnln5rmjs87qw1sd34vgjj8b5iqc7mg-python3.10-zxing_cpp-1.4.0/lib/python3.10/site-packages (from authenticator-helper==0.1.0) (1.4.0)
       > Requirement already satisfied: Pillow<10.0.0,>=9.1.1 in /nix/store/49y0gryvz22pfjhwq6x0gbawp2h7vsaa-python3.10-pillow-9.4.0/lib/python3.10/site-packages (from authenticator-helper==0.1.0) (9.4.0)
       > Requirement already satisfied: mss in /nix/store/xq1nygacq8mc5rg53qp6ccs0pcgm8pid-python3.10-mss-7.0.1/lib/python3.10/site-packages (from authenticator-helper==0.1.0) (7.0.1)
       > ERROR: Could not find a version that satisfies the requirement yubikey-manager==5.0.1 (from authenticator-helper) (from versions: none)
       > ERROR: No matching distribution found for yubikey-manager==5.0.1
       >
       For full logs, run 'nix log /nix/store/jalgglf19k4zfh6c5yv18kmkxw6xlw6q-yubioath-flutter-helper-6.1.0.drv'.

Additional context
I got this issue after upgrading my system from 897876e4c484f1e8f92009fd11b7d988a121a4e7 to 0470f36b02ef01d4f43c641bbf07020bcab71bf1, it seems ff9c88829755b38c3d44cd3b7446e389ce669697 broke yubioath-flutter somehow.
Notify maintainers
@lukegb @hacker1024
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[elnu@elnu:~/nix-config]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.1, NixOS, 23.05 (Stoat), 23.05.20230506.897876e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Closed by #230674.

❯ nix run nixpkgs#nix-info -- -m
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.1-zen1, NixOS, 23.05 (Stoat), 23.05.20230522.7084250`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/store/hc2y6044ksiz4vs1cyhy6qzd6szxvm4c-source`

Builds and runs correctly for me.


Tooltip's arrow is separated from the tooltip's body on Windows

Bug report
Current Behavior
The following screenshot comes directly from the Radix UI docs first example while visiting the page with Firefox on Windows.
the same problem has been reported internally (in Preply) also for Edge but always on Windows machines and this does not happen every time.

It seems quite related to #2458.
Expected behavior
No space between the arrow and the body.
Reproducible example
I don't have clues to reproduce it systematically, unfortunately. Like #2458, it's something random (I just tried using Browserstack to help you but I'm out of luck, I can't reproduce it there).
Suggested solution
I don't have one, I also think it's a matter of transform like maybe happens for #2458 but I'm not sure.
Additional context

Your environment

Software
Name(s)
Version

Radix Package(s)
Tooltip
1.0.6 (currently used in the docs)

React
n/a
18.2.0 (currently used in the docs)

Browser
Firefox
118.0.2

Assistive tech

Node
n/a

npm/yarn

Operating System
Windows
10.0.22621 build 22621

Praise
Thank you for the hard work, we love Radix UI ❤

This is probably due to some sub-pixel alignment or similar. It isn't an issue with the primitive per-se, but rather with the styling. If you want to make sure this really doesn't happen, you can probably move that arrow a tiny bit backwards so it's hidden behind by 1px.

Got it, thanks for the feedback ❤


Improve User Settings Page Design and Structure

The current design of the User Settings page can be enhanced for better user experience and content clarity. The following issues have been identified:
1.Redundant Headings:
The page includes two headings: "User Settings" and "My Profile". This redundancy can confuse users.
2.Header Content:
The user's name is included in the main content header. Instead, it could be better positioned within the body or as a     replacement for the "My Profile" heading.
3.Body Content Structure:
The body content currently includes personal information like email and phone number but lacks clarity. It needs restructuring for improved readability and hierarchy.

Design updated in - Design handoff


Error when using the config

Hi there,
I really like your theme and the possibilities it provides. However, I am unsure on how to use it.
When I add the settings to my typedoc.json I only get
Error: Tried to set an option (removePrimaryNavigation) that was not declared. Error: Tried to set an option (removeSecondaryNavigation) that was not declared. Error: Tried to set an option (customNavigations) that was not declared.
Where and how do i tell typedoc to use it? What am I doing wrong :(

Okay, got it running. I just needed to add
"plugin": [ "./node_modules/@wearerunes/typedoc-plugin/" ]
However, now I receive the following error
Error: Unknown option 'visibilityFilters'


Convert samples

Hello, i have some samples for piano in wav, how to configure a covert in mp3/ogg - that would get the best sound? I tried to cbr and every note breaks off a second after the start, in the vbr the note breaks off later, but there is no effect of finishing(release) it like in the acoustic grand piano

Are you asking how to convert wav files to mp3? There are probably a bunch of answers to that on StackOverflow.
I have always gone from wavefonts to midi-js readable format so now exactly sure how to do that by hand

@gleitz I will try to rephrase the question. Is it possible to use any library of samples using this library? As for the format of mp3, everything is clear. For example - I load my piano samples library (not FluidR3_GM' or 'MusyngKite) with several layers of volume and without changing a line of code the result is erroneous. The notes are played back with the counters and the piano pedal function stops working


8752 Added CA receiver transforms to truncate fields needed for CA

This PR adds CA receiver transforms to truncate the HL7 fields needed for CA. Based on the fields listed on this ticket #8752. The following fields listed on the ticket are not being truncated:

MSH-3-1: value is hardcoded and does not exceed max length
MSH-4-1: value is hardcoded and does not exceed max length
OBR-2-2: not sending this to CA at the moment
ORC-4-2: not sending this to CA at the moment
PID-3-6-1: we don't have a mapping for this field

If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

Send the attached FHIR bundle to the Reports API:
Simple Report.postman_collection.txt
This sample contains all the fields that should be truncated and you can search for them by looking for "truncatethis"

Verify that the request was accepted

Open the generated HL7 file in the local sftp folder.

Verify all the fields were truncated by making sure the HL7 message doesn't include the text "truncatethis"

Run integration tests and make sure they pass

Changes

Added CA receiver transforms to truncate HL7 fields
Added integration test for truncating fields

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[x] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

#8752

To Be Done
Create GitHub issues to track the work remaining, if any

#8876

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

https://github.com/CDCgov/prime-reportstream/pull/9012#pullrequestreview-1375409986
@arnejduranovic My concern about this approach is that if we do that truncation at the beginning of the pipeline by performing the FHIR truncate function, STLTs that accept un-truncated HL7 messages will experience a loss of data.
I think to make this decision we should make ourselves. Ideally I would have @jsutantio or @jakefishbein-navapbc asking STLTs that don't truncate how important that is to them . Alternatively, @brick-green or @LaFreda1 could weigh in on the STLT impact of this decision.

@victor-chaparro can you add a comment above each truncation about why its being truncated to that number of characters? I think this is something that will become confusing really quickly and I'd like it to be as easy as possible to read through the config and understand what's going on.


Performance issue when opening the editor

When open in a new page, sometimes takes a long time to open an editor.
the version I use is  flutter_summernote: ^0.2.2, flutter stable version 1.22.5.

If you'd like you can try out the html library I created here. It doesn't have this issue and also has support for Flutter Web & dark mode, among other features.

Ok, will try the package. Thanks!


Feature: add coinbase receiver info to mina client status

At the moment, there is no way to display the current coinbase receiver through the CLI.
It could be useful to see it by typing mina client status. It would allow to double check if it's set properly in the daemon and is active. e.g. under the "block producers running" field:
Block producers running:                       1 (<block_producer_pubkey>)
Coinbase receiver:                             <coinbase_receiver_pubkey>
Best tip consensus time:                       epoch=0, slot=2633

This was done in #8127. Closing.