Leave explicit file extensions in module import paths

Do you want to request a feature or report a bug?
Kind of both
What is the current behavior?
The current source code uses ES Modules without explicit file extensions. This is breaking my build process because my build process assumes anything without an extension is a .ts file.
What is the expected behavior?
I think it is more appropriate to explicitly put file extensions on import paths in the source code and the generated ES Modules distribution code. Since the source code is JavaScript, leaving out the extension has no purpose as far as I can tell. I don't believe my build system (https://github.com/lastmjs/zwitterion) is treating paths without extensions much differently than other popular build systems, by that I mean this is probably a common expected behavior outside of my use case

By the way, if the maintainers would accept it, I would be happy to do a PR to add these changes in

It looks like the bundling format used in v4.0.0-beta.2 fixes my issues, though my opinion still stands that explicit file extensions should be used.

The ECMA spec doesn't specify a file extension. In addition, most other tooling does not require this. This is based on the Node module resolution algorithm, which will attempt to find the file with a few different possible extensions. I would mimic this behavior, as you'll run into this same issue in many other libraries.


NavigationManager not encoding url

Normally when I navigate to a URL inside my app I would use something like UriHelper to encode the URL. But this has been replaced by the NavigationManager.
I am wondering if the NavigationManager.NavigateTo should do a UrlEncode?
The following example code works fine:
NavigationManager.NavigateTo("/?search=some criteria | other criteria");

This will let the application navigate properly. The URL that comes out in the browser will look like this:
/?search=some%20criteria%20|%20other%20criteria

But, when I copy that URL from the browser and when I paste it into a new window, I then get the following error:
[2019-09-24T09:32:14.420Z] Error: The uris provided are invalid.
e.log @ blazor.server.js:15
blazor.server.js:1 [2019-09-24T09:32:14.421Z] Information: Connection disconnected.
blazor.server.js:1 Uncaught (in promise) Error: Invocation canceled due to the underlying connection being closed.
    at e.connectionClosed (blazor.server.js:1)
    at e.connection.onclose (blazor.server.js:1)
    at e.stopConnection (blazor.server.js:1)
    at e.transport.onclose (blazor.server.js:1)
    at e.close (blazor.server.js:1)
    at e.stop (blazor.server.js:1)
    at e.<anonymous> (blazor.server.js:1)
    at blazor.server.js:1
    at Object.next (blazor.server.js:1)
    at s (blazor.server.js:1)

This is because the piped character is in the URL. This only fails when pasting the URL directly into the browser.
The same thing happends for a few other characters like curly brackets.
I am not sure if this is a bug? Or am I responsible to do a url encoding before passing the URL to the NavigateTo  method?
If so, what should I use, siince the UriHelper has been replaced?
Right now the behaviour is not very consistent when navigation through codes works fine, untill you copy paste the URL in the browser.

@chinookproject Thanks for contacting us.
Navigation manager's responsibility is to perform browser navigation. If you have urls with characters that require encoding you should be responsible for encoding those characters. Navigation manager can't know if the url you gave it was already encoded or not, so if we were to do this, we could cause double-encoding issues.
What I'm trying to say is that NavigationManager can't know in the general case whether it needs to encode or not a given url, so it is up to the developer to do so.
That said, maybe this is something we can provide an overload for. @danroth27 @rynowak thoughts?

Thanks for contacting us, @chinookproject.
This is not something we plan to expose additional API for. You can use WebUtility.UrlDecode method you can use to decode it yourself.


Default docmapper with dynamic mode.

Makes the dynamic mode the default, and allow unspecified doc mapping
Accepting sort by score even if one of the default field does not have fieldnorm.
Minor code cleanup
Closes #2910

@fulmicoton note that an index config like this one:
version: 0.4
index_id: my-dynamic-index

will not be created. The returned error message from the API is
"message": "Invalid config: Failed to read YAML file.: missing field `doc_mapping`."

@fmassot yes it used to be possible in my previous PR, but I removed that.
Should I readd it?


[BUG]- My Bloxtrap crashes every time I open it

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?

I know it says Roblox Crash but I promise you it isn't roblox, its bloxtrap

anyone help? Its been 4 hrs

Have you confirmed that this only happens with Bloxstrap? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

Have you confirmed that this only happens with Bloxstrap? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

Yes

What settings have you configured in the Bloxstrap Menu?

What settings have you configured in the Bloxstrap Menu?

is there a way to copy the settings?

activity tracking=On
see server location=Off
show game activity=On
allow activity joining=On
multi-instance launching=Off
old death sound=On
cursor=Default
OG editor background=Off
emulate OG character sounds=Off
disable desktop app=Off
emoji type=Default
disable fullscreen optimizations=Off
frame limit=9999 (I tried 0 and it didnt work)
lighting tech=Future
escape menu ver=Default
enable hide GUI=Off
OG textures=Off
preserver render quality with display scaling=Off
alt graphics quality selector=On
(appearance options are default)
auto update bloxstrap=On

activity tracking=On see server location=Off show game activity=On allow activity joining=On multi-instance launching=Off old death sound=On cursor=Default OG editor background=Off emulate OG character sounds=Off disable desktop app=Off emoji type=Default disable fullscreen optimizations=Off frame limit=9999 (I tried 0 and it didnt work) lighting tech=Future escape menu ver=Default enable hide GUI=Off OG textures=Off preserver render quality with display scaling=Off alt graphics quality selector=On (appearance options are default) auto update bloxstrap=On

couldnt copy them but hopefully this works

What did you do?


Add ability to define entire query manually

It would be nice to have some sort of mechanism to allow consumers to pass in a full query object. This would allow users to have full control over search queries and provide an escape hatch for those situations where a complex query is needed. Here are some suggestions to start the conversation:

A special $bool or $query property which signifies the the user has built a query themselves.
{
  $bool: { must: { match: 'query' } }
}

Allow params.elasticsearch to hold data which is merged onto the object passed to the underlying ES client. This would be the "top level" object passed to the ES client:
 (context) => {
   context.params.elasticsearch = { waitForActiveShards: '2' };
 }

The feathers-sequelize and feathers-knex adapters (and I'm sure others) allow users to set params[adapter-name] which is merged with the options generated by the adapter. This gives users 100% control of the options passed to the underlying sequelize/knex client.

Hey @DesignByOnyx,
I really like the second idea. In fact it's been on my to-do list for a while :)
With regards to the first one, I'm not quite sure. Elasticsearch lets the user create very heavy queries, which can bring the system down to its knees. That could provide an easy way to DOS the ES cluster for potential attacker. To sweeten it up a bit, we currently have raw method on the service, which should take care of that use case, if you wanted to have some complex queries. I hope it makes sense?

I think the second option that @DesignByOnyx suggested would be the best of the both worlds. Using "raw" removes a lot of the goodies we get with the cross adapter queries and standard feathers service apis. It seems like checking params.elasticsearch before each function call would be fairly straightforward.


[CT-2636] TestVersionedModels::test_pp_versioned_models is flaky

Example failing test run: https://github.com/dbt-labs/dbt-core/actions/runs/5178505585/jobs/9330058721?pr=7768
Relevant Logs:
        # update versions schema.yml block - latest_version from 2 to 1
        write_file(
            models_versions_updated_schema_yml, project.project_root, "models", "schema.yml"
        )
>       results, log_output = run_dbt_and_capture(
            ["--partial-parse", "--log-format", "json", "run"]
        )

D:\a\dbt-core\dbt-core\tests\functional\partial_parsing\test_partial_parsing.py:341:

        if expect_pass is not None:
>           assert res.success == expect_pass, "dbt exit state did not match expected"
E           AssertionError: dbt exit state did not match expected

d:\a\dbt-core\dbt-core\core\dbt\tests\util.py:105: AssertionError

stdout_log: {"data": {"msg": "  relation \"test16859771223328142563_test_partial_parsing.model_one_downstream\" does not exist"}, "info": {"category": "", "code": "Z029", "extra": {}, "invocation_id": "9e30ed11-b91f-4609-8dd0-a82ab93b96ba", "level": "error", "msg": "  relation \"test16859771223328142563_test_partial_parsing.model_one_downstream\" does not exist", "name": "AfterFirstRunResultError", "pid": 6128, "thread": "MainThread", "ts": "2023-06-05T14:58:50.611377Z"}}

Another example:
https://github.com/dbt-labs/dbt-core/actions/runs/5293127534/jobs/9580850631?pr=7892#step:8:3783

An another example:
https://github.com/dbt-labs/dbt-core/actions/runs/5324997604/jobs/9645095748

Tested with Flaky Tester and failed 3/100 runs on Python 3.8/windows

The test fails in the middle.  This happens when run as part of the suite or when run by itself.

In the test run that I looked at the sequence of events is:

create view ...model_one_downstream__dbt_tmp
rename model_one_downstream to model_one_downstream__dbt_backup
fails with "model_one_downstream" does not exist

Looks like this is flaking again: https://github.com/dbt-labs/dbt-core/actions/runs/8341943731/job/22829077630?pr=9769


icons are sticking together

Hey Community!
I got a toolbar with 1 icon to close the browser
2 icons for back & forward
and 1 custom btn.
The problem I got is, that the icons are sticked together so it is pretty hard to hit the right one.
Is there a recommended size or is there a trick or something else? I can't achieve the wanted look.
Here is the screenshot of the toolbar:

Hi,
see:
https://github.com/initialxy/cordova-plugin-themeablebrowser#how-do-i-add-margings-and-paddings

How do I add margings and paddings?
There is no margins or paddings. However notice that you can assign images to each of the buttons. So take advantage of PNG's transparency to create margins/paddings around your buttons.

The height of the toolbar is "44px", the close button in the toolbar has a dimension of "104x88px" and image density setting "2". Add transparent space around the icon.
cordova.ThemeableBrowser.open(url, '_blank', {
        toolbar: {
        height: 44,
        color: '#000000'
    },
    title: {
        color: '#ffffff',
        staticText: title,
        showPageTitle: false
    },
    closeButton: {
       wwwImage: 'assets/images/iab-close-button.png',
       wwwImageDensity: 2,
       align: 'left',
        event: 'closePressed'
    },
    backButtonCanClose: true,
    hidden: true
});


[BUG] websocket will continue to push resources that have been deleted

Describe the bug
The image object has been deleted, but the websocket will still push the deleted resource to the frontend.

To Reproduce
Steps to reproduce the behavior:

create a image
delete image
Do not refresh the page, after a while back to the image page, you may see the list of previously deleted images in the page again

Expected behavior

deleted resources should not continue to be displayed in the page
Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

@guangbochen   This is a backend issue. I deleted the ui label and added the backend label. However, I haven't encountered this problem recently. I will observe this problem in this period of time. If it doesn't recur, I will close this issue.


Queueing a music playlist using a link is broken

It's as the title says, the '!m pl' command still works with keywords, just not links.

weird, thanks for the report, ill take a look a bit later

Fixed itself. I changed nothing, but it works now.


fix bad babel relative test

Looks like the test itself was wrong, this fixes both the code and the test.

This change was incorrect, it breaks my use-case. The problem is that the way the tests are structured, it was impossible to actually use a path that made sense because when the tests run, it has a different current working directory than the actual source code.

I noted that in the original description in #191

I'm not too happy with the tests here, since we're dealing with relative paths, it gets a bit funky. I just put the path that actually gets output, but it's not actually a correct output for the tree structure of __tests__. This is because for some reason, file.opts.filename and file.opts.root have different roots. file.opts.root has cwd in it, but the file isn't actually within cwd so we end up with an extra .. in the output where we shouldn't.

We need the path relative to the file in question, not the path relative to the directory of that file. Adding path.dirname() is incorrect.

I don't think that's correct. I just tested master locally and it works as written:
# .babelrc
"plugins": [["snowpack/assets/babel-plugin.js",  { "importType": "relative" }]]

# src/index.js
import React from "react";

# lib/index.js
import React from "../web_modules/react.js";

I should have also linked to the original discussion in the PR, where someone originally reported the need for this fix: https://www.pika.dev/npm/snowpack/discuss/105

Okay, well it definitely doesn't work with:
    ["./plugins/snowpack-babel-plugin.js", {
      "webModulesUrlPath": "/web_modules",
      "webModulesDir": "../web_modules",
      "importType": "relative",
      "moduleResolution": "node"
    }],

It removes a ../ from the web_modules paths for my setup that is required.

You can replicate it by setting up a tree like this:
.
├── Component
│   ├── .babelrc
│   ├── common.scss
│   ├── package.json
│   ├── plugins
│   │   └── snowpack-babel-plugin.js
│   ├── src
│   │   ├── Common
│   │   │   ├── Button.tsx
│   │   ├── index.ts
│   │   └── types.ts
│   ├── tsconfig.json
│   └── yarn.lock
├── dist
│   ├── Common
│   │   ├── Button.js
│   ├── index.js
│   └── types.js
└── web_modules
    ├── import-map.json
    ├── react-dom.js
    └── react.js

Yea, I bet ""webModulesDir": "../web_modules"," is what's causing you trouble.
We'd originally wanted to avoid tackling this more complex use-case, but given the feedback here from you + discussion 105 I think we should tackle this as well, before releasing support. I think I have an idea, going to play around with something and then create a PR if it works. Will ping you with an update either way.

Thanks!


Bump libgit2 image and disable cosign verification for CI

The libgit2 libraries are downloaded and verified before
some of the make targets are executed. This assures the
provenance of such files before using them and is very
important specially for end users running such tests on
their machines.
Note that has been disabled specially due to recent issues
we experienced at CI which can be seen in:
https://github.com/fluxcd/source-controller/issues/899

When running the verification locally for the latest libgit2 image it is failing with:
+ COSIGN_EXPERIMENTAL=1
+ cosign verify-blob --cert /tmp/tmp.HOAXg9EIvk/checksums.txt.pem --signature /tmp/tmp.HOAXg9EIvk/checksums.txt.sig /tmp/tmp.HOAXg9EIvk/checksums.txt
Error: verifying blob [/tmp/tmp.HOAXg9EIvk/checksums.txt]: computed leaf hash did not match entry UUID
main.go:52: error during command execution: verifying blob [/tmp/tmp.HOAXg9EIvk/checksums.txt]: computed leaf hash did not match entry UUID

@pjbgf are you using Cosign v1.12.1?

@stefanprodan thanks for that, I deleted the cached cosign for IAC but forgot to do the same for SC. Which meant I was using an earlier version, it is now working as expected. :+1:


Add Harvo GT-004 on MacOS

Is this Marvo perhaps ? https://www.google.com/search?q=Marvo+GT-004&tbm=isch

Woops, their logo on the controller really makes it look like Harvo to me. Editing now.

Done!


Add a way to access Sprint modes from the overworld

The overworld should have a marketing consultant who has his own office, and lets you access the sprint modes.
Thematically, this sprint mode could correspond to a flyer that advertises "Delivery in 2 minutes or less!" but, he wants you to prove you can actually deliver that quickly.
Also see #91 and #93.

Closing due to removal of freeroam mode (#1257)


update that how to judge the same weight

update that weights and how to judge the index depend on offset
What is the purpose of the change
1.update that how to judge the same weight
2.update that weights and how to judge the index depend on offset
Brief changelog
1.enhance performance
2.code is clear
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

it is very clear. The totalWeight != weight * (i + 1) is very clever. very nice


Examples

@webus Please merge into the master branch..

can cama:develop be merged in to master without impact?


Feature - Item filter

Is your feature request related to a problem? Please describe.
I would like to filter items in the watchlists to be able to more easily select an item that I feel like watching
Describe the solution you'd like
Users can filter their view of watchlists by combination of tags and/or status
Requires #58 or #56 #57 to be done to begin

The Issue be implemented in pull request #75


54 beta indicator

adds testing warning/feedback request component.
also removes a couple extra ts props I missed in a previous pr.

Commits are now a subset of 54 beta indicator - alt


perf: reduce APK size with ProGuard enabled

Details

This PR enables minification and resource shrinking for android using ProGuard. This gives us 10.4 MB reduction in Download Size.
Before:
| APK Size MB | Download Size MB
-- | -- | --
All architectures | 127 | 123.3
  |   |
After:
| APK Size MB | Download Size MB
-- | -- | --
All architectures | 116.5 | 112.9
  |   |
Fixed Issues

$ https://github.com/Expensify/App/issues/34222
PROPOSAL: https://github.com/Expensify/App/issues/33070#issuecomment-1875099319
Tests

Install the APK

Launch the app and use normally

The app shouldn't crash and shouldn't miss any functionality

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

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

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

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

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

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

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

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

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

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 any new file was added I verified that:

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

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

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

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

[X] I verified that all the inputs inside a form are aligned with each other.
[X] I added Design label so the design team can review the changes.

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

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/47336142/8b320a4e-8159-487e-9555-8061187625de

Android: mWeb Chrome

N/A

iOS: Native

N/A

iOS: mWeb Safari

N/A

MacOS: Chrome / Safari

N/A

MacOS: Desktop

N/A

It would be ideal to NOT MERGE this PR until the QA completes their testing and confirms that no crashes or loss of functionality is noticed.
We can move forward with creating the builds for this PR and kick off the QA testing.
cc: @roryabraham @mountiny

Running a build here https://github.com/Expensify/App/actions/runs/7474984009

One super minor thing I noticed is that the AdHoc badge doesn't display, but I haven't checked previous AdHoc builds in a while...

@shubham1206agra will do some initial testing and we would probably ask QA to do a full regression on the android build before merging too

@shubham1206agra will do some initial testing and we would probably ask QA to do a full regression on the android build before merging too

Please check notification here

Is it the logo? that might be case for other adhoc builds too, that would be good to check

I think the App is working fine. Except the logo, crossed check with other adhoc build where it works fine.
Note - Please check the permissions area as I got a phantom permission while doing distance request in confirmation page.
cc @mountiny @Julesssss

https://github.com/Expensify/App/assets/58412969/d654d136-c0dd-4165-82e6-28971b2211ed

@hurali97 Please address this https://github.com/Expensify/App/pull/34218#issuecomment-1884869946

@shubham1206agra did you confirm that does not happen on other Android adhoc builds?

Yes

@hurali97 Please address this #34218 (comment)

@shubham1206agra It's fixed now.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

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

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (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] 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 verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[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] 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] 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(theme.componentBG)

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

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

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/58412969/d654d136-c0dd-4165-82e6-28971b2211ed

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@hurali97 Can you confirm the final size of apk now?

@hurali97 Can you confirm the final size of apk now?

Yeah sure.
After adding keep rules for resources:
| APK Size MB | Download Size MB
-- | -- | --
All architectures | 116.5 | 113
  |   |
There's 0.1 MB increase in Download Size and APK Size remains intact. We still save 10.3 MB in Download size.

Making a new test build

Oh wait, did we confirm the logo issue doesn't exist on other AdHoc builds?

I think the App is working fine. Except the logo, crossed check with other adhoc build where it works fine.

One other thing, did this PR introduce the regression where Android build information isn't shown for AdHoc downloads?

Oh wait, did we confirm the logo issue doesn't exist on other AdHoc builds?

I think the App is working fine. Except the logo, crossed check with other adhoc build where it works fine.

I have checked this. Works fine for me.

I'm still seeing it on a Pixel 6a, perhaps this depends on DP?

@Julesssss I have that on my iPhone adhoc build, other one too, not related

I'm still seeing it on a Pixel 6a, perhaps this depends on DP?

This is a known problem in other builds too

I think this is good to go then!

: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/mountiny in version: 1.4.33-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.33-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Examples wanted

Any update on the WIP examples? It would be great to have them.

Example present here: https://github.com/jfet97/strawberry/wiki/Examples


Radial Menu should be added

Radial Menus should be added eventually. They would be a great asset for items like the RCD.

Check how warframe does radial menus, it supports an infinite amount of things added to it by a spiral menu type thing

Radial menus are now available as per #22799


[BIA-786] Create Power BI query for Section View

Add relation to enable filters in Section tab according to mockups.
Add column Student Name.
Add a column to return the submitted total by row.

Relationships

StudentInternetAccessDim (*) -- (1) DeviceAccess
StudentInternetAccessDim (*) -- (1) DigitalDeviceAccess
StudentInternetAccessDim (*) -- (1) InternetAccessInResidence
StudentInternetAccessDim (*) -- (1) InternetPerformance
StudentInternetAccessDim (*) -- (1) InternetAccessTypeInResidence
StudentInternetAccessDim (1) -- (1) StudentSchoolDim
StudentSectionDim (*) -- (1) StudentSchoolDim
AssignmentDim (1) -- (*) engage_AssignmentSubmissionFact
AssignmentDim (*) -- (1) SectionDim
SectionDim (1) -- (*) StudentSectionDim

So I think there might be some confusion between what is in the engage_AssignmentSubmissionFact view, and then what gets displayed in the table on the report. Looking at the structure of the view, IsPastDue, SubmittedLate, and OnTime are treated as bit fields with 1 or 0 to flag if that specific row(submission) was past due/late/on time and are not a count of how many were submitted past due/late/on time. But then the view itself would need the total of how many were submitted past due/late/on time grouped by section and teacher. If this understanding is correct, then the newly added Total Submitted column is not needed.
Additionally, could you mention what relationships were added either via screenshots showing them or writing them down to make it easy to see what was changed?

@bptillman . When the data filtered by section is added, with the new relationships the table is being grouped by student. In this way, the data is being added for each type (due / late / on time). In the PR I attached a screenshot of the table.

TotalSubmitted should be SUM(SubmittedOnTime) + SUM(SubmittedLate) for any grouping. IsPastDue means that the assignment has not been submitted yet (could also call this a "missing" assignment).


JSX syntax highlighting not working

Hey @jhonGriGi, hanks for raising the issue! Are you using treesitter?
This theme is very reliant on treesitter and I haven't put any effort into supporting regex based JSX highlighting. I should probably write this into the README as well.

hi @JoosepAlviste, I have tried using vim-polyglot, treesitter, vim-jsx-pretty and vim-tsx, but still not working, although my neovim's config is in vimscript, I will try with lua

@jhonGriGi Using Lua for configuration shouldn't affect this plugin at all, so keep using vimscript if you like. Could you try treesitter one more time and share a screenshot of how the tree looks like with https://github.com/nvim-treesitter/playground? Just to make sure that treesitter is correctly set up with JSX.
Also, are you enabling the colorscheme with colorscheme palenightfall? I haven't tried that in a while, I can double check that it still works soon 😄

Angular

React is working

if you want, I could try with Vue Js
Question: The [const] word in typescript has no colors or is a bug?

I don't have idea why React is working, I just update the plugin with :PackerSync lol
I just did a :TSUpdateSync and my typescript files are working again, so I think de issue is close now.
Angular examples

Interesting, I guess it's possible that you had some problems with Treesitter 😄
But good to see that you got it working! I'll close the issue now.


upgrade to support dbt-core v1.5.0

Background
The latest version of dbt Core,dbt-core==1.5.0rc1, was published on April 13, 2023 (PyPI | Github).
How to upgrade
https://github.com/dbt-labs/dbt-core/discussions/7213 is an open discussion with more detailed information. If you have questions, please put them there!
The above linked guide has more information, but below is a high-level checklist of work that would enable a successful 1.5.0 release of your adapter.

[ ] Add support Python 3.11 (if you haven't already)
[ ] Add support for relevant tests (there's a lot of new ones!)
[ ] Add support model contracts
[ ] Add support for materialized views (this likely will be bumped to 1.6.0)

the next minor release: 1.6.0
FYI, dbt-core==1.6.0 is expected to be released at the end of July, with a release cut at least two weeks prior.

Hello, upgrade to support latest dbt-core would be fantastic. We are using custom runtime images in CML public cloud and we had to drop dbt-impala from our latest custom image. There were simply too many outdated dependencies from dbt-core 1.3.

Fixed as https://github.com/cloudera/dbt-impala/pull/195


Appstudio update test-custom-default-branch-gjtg

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-vchz-on-pull-request-
creating pipelinerun test-annotations-vchz-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-ntht-on-pull-request-
creating pipelinerun test-annotations-ntht-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-yrqk-on-pull-request-
creating pipelinerun test-annotations-yrqk-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-gcoj-on-pull-request-
creating pipelinerun test-annotations-gcoj-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-irrl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Contains old and even malware

In this list is still stuff like sonora which wasn't updated since 2015, it's website gives a 403 error.
And even worse mplayerx is still listed even though it becamse quite bad malware at some point.

Also spectacle maintenance has stopped (as per author comment).

@Diskutant @mcha-dev thanks for your interest in this project.
I'd suggest to one relsted Pull Requests, where your suggestions can be discussed and accepted.
Raoul


remove override from test suite

our test suite has override and mock which provide similar functions and confuse our users. This is to remove the override methods so we only provide one mock as the way to replace workflow/activity.

Coverage remained the same at 100.0% when pulling 81d00d82081b57e0732dfb662a45871ea281dcb7 on yiminc:remove_override into 25aa0feb581831769cecfd4bef5094a4ec967aa4 on uber-go:master.


CrossDomain support

If image loaded is from another domain then browser doesn't allow to get data. Is it possible for you to include some kind of workaround for this? (http://blog.codepen.io/2013/10/08/cross-domain-images-tainted-canvas/).
Besides that - great work!

I kept getting the "tainted canvas" error until I went in and changed image.crossOrigin = "anonymous" to image.setAttribute('crossorigin', 'anonymous')  . Then everything worked.

@skitterm Interesting. Could you share what browser you tested in where image.crossOrigin = "anonymous" didn't work?

I was in Chrome 42.

I have the same problem in Chrome 46 on windows.
The crossOrigin=Anonymous didn't work for me.


Added subproc_raise public facing function for calling shell commands

TL;DR
ShellTask works great in simple situations but falls short when the DAG or data structures get complicated.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[ ] Unit tests added
[x] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
A lot of bioinformatics tools are based on Java/Perl/C++ and therefore require using ShellTask. Over the course of developing the variant discovery demo I started with using ShellTask almost exclusively since it's the first-class abstraction for doing that sort of thing. However, I quickly ran into how limiting it was and switched almost exclusively to the function in this PR to enable the flexibility that I need.
For example, I'm using a list of inputs that's not necessarily known at compile time, requiring the use of dynamic workflows. ShellTask works fine in these, but the interface is so rigid that I couldn't repackage the outputs into the requisite dataclasses after processing, without using a new python task specifically for that purpose. Using a regular python task here allows me to unpack and repack dataclasses before and after executing the shell command. I also tried using ShellTasks within eager so I could operate on those outputs within the workflow context, but eager doesn't support them yet. Long story short, ShellTask works great in simple situations but falls short when the DAG or data structures get complicated. I know there's already _run_script but that's marked private/internal so I didn't think that would be appropriate.
I marked this as a draft to start a conversation around this functionality. I think this would be a good option with few drawbacks but would like to solicit feedback.
Follow-up issue
NA

Hmm I'm a bit confused bc that lint error is in a file I didn't touch, hasn't been touched in months, and raises the same error on master... How does anyone get this to pass? 😅

nvm, I found that it's not related your PR, I'll fix it, then merge your PR.


Omit Generated/Internal methods that aren't used by a client

As a follow-up to https://github.com/microsoft/typespec/issues/4218, it would be helpful to pare down the API surface of types in Generated/Internal to eliminate methods that aren't used by the client.  For example, only five of the methods on ClientUriBuilder in the OpenAI .NET client are used, but there are ~27 methods on the type.

Can you help us understand what the problem is that we are trying to solve?
If we were to trim these unused methods, customers wouldn't have the opportunity to discover the set of helper methods that we generate, in case they may want to use them in custom code. Are customers asking for this feature? If the concern is package size, then wouldn't we recommend that they use AOT?

Do we support AOT for everything in our clients today?  Package size is one; code coverage numbers is another.
Are customer asking to have the internal helpers?  Do we have a problem with discoverability?


Display error message for creating cloudevent client to make it more debug friendly

Proposed Changes
Error message from client.NewHTTPClient() is disregarded. This patch
displays the message to make it more debug friendly.
Release Note
NONE

/ok-to-test

Looks like a conflict has been added. sorry

@n3wscott @Harwayne Thank you. It looks like this patch was covered by https://github.com/knative/eventing-sources/pull/240/files#diff-f72d84927429ec2642a59559b3a2d89eR103. I am closing this PR.


Conflicting with AOS Animations

short description of the bug / issue, provide more detail below.

Slick is causing issues with AOS animations on scroll reveal. See https://github.com/michalsnik/aos/issues/309
====================================================================
[  https://credify.one  ]
As in the other issue, you can see this is causing problems of no animation on desktop browser.
In the js/main.js, everything works fine when I comment out the Slick initialisation.
====================================================================
Steps to reproduce the problem

Initialise Slick on document ready.
Initialise AOS after or before (both do not work).
Scroll an AOS data-tagged element into view.

====================================================================
What is the expected behaviour?
Expect element to animate when scrolled into view.
====================================================================
What is observed behaviour?
Nothing animates.
====================================================================
More Details

Doesn't seem to happen on mobile.
jQuery 1.1.3 & Slick 1.8.1

Same with ScrollReveal (v.3/v.4 beta)

Did anyone solved the problem of AOS with Slick slider?

Same for me!

Below is a link please Visit and solve your problem.
https://techkro.in/slick-slider-with-animate-css/

https://github.com/kenwheeler/slick/blob/master/CONTRIBUTING.markdown
Please provide isolated problem on (for example) jsfiddle (hint: not on your webpage where anything could interfere with slick code).

I also have the same error AOS with slick slide

I also have the same error AOS with slick slide. please anyone can solve.

https://github.com/kenwheeler/slick/blob/master/CONTRIBUTING.markdown
Please provide isolated problem on (for example) jsfiddle (hint: not on your webpage where anything could interfere with slick code).

On https://github.com/michalsnik/aos/issues/155#issuecomment-514591450 I found this solution for me:
$(window).on('load', function () {
  AOS.refresh();
});
$(function () {
  AOS.init();
});

Experienced the same behaviour and this made it work for me:
https://github.com/michalsnik/aos/issues/635
$(window).on("scroll", function () {
	 AOS.init();
 });

Experienced the same behaviour and this made it work for me:
michalsnik/aos#635
$(window).on("scroll", function () {
	 AOS.init();
 });

I found this solution worked, but put heavy load on the browser.
This solution seems to be working for me.
$('.carousel').on('init breakpoint', function(event, slick, direction){
	setTimeout(function() {
		AOS.refresh();
	}, 500);
});

The timeout is needed, even though it's messy. Could do with a bit of tweaking.


Release checklist

[x] Implement JSON-RPC for gnosis
[x] Deploy contracts (QuestFactory and Quest + Govern + GovernQueue) on Gnosis
[x] Deploy subgraphs (Govern, Quests) on Gnosis
[x] Create a stagging branch
[x] Register and configure Quests subdomain quests.1hive.org
[x] Configure Vercel to CD in main branch and staging
[x] Create a gnosis-safe on gnosis chain for managing admin operation

Deploy the webapp to IPFS

What it means? So we dont pretend use Vercel to deploy?

Oh maybe I dont know I thought that IPFS was the way to go for web3
projects but actually might me simpler for continuous deployment if we can
stick to vercel but with another domain than quests.vercel.app
On Mon., May 2, 2022, 9:08 p.m. Felipe Novaes F Rocha, <
@.***> wrote:

Deploy the webapp to IPFS

What it means? So we dont pretend use Vercel to deploy?
—
Reply to this email directly, view it on GitHub
https://github.com/1Hive/quests/issues/256#issuecomment-1115516818, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJ7IOXMGQQA6VKHB4ON543VIB4CPANCNFSM5U5NEXIA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I like idea IPFS hosting, maybe just need create some GitHub action to CD
on that.
I just don't know about the stability on that.
Em seg., 2 de mai. de 2022 23:38, Corantin @.***>
escreveu:

Oh maybe I dont know I thought that IPFS was the way to go for web3
projects but actually might me simpler for continuous deployment if we can
stick to vercel but with another domain than quests.vercel.app
On Mon., May 2, 2022, 9:08 p.m. Felipe Novaes F Rocha, <
@.***> wrote:

Deploy the webapp to IPFS

What it means? So we dont pretend use Vercel to deploy?
—
Reply to this email directly, view it on GitHub
https://github.com/1Hive/quests/issues/256#issuecomment-1115516818, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ADJ7IOXMGQQA6VKHB4ON543VIB4CPANCNFSM5U5NEXIA
.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/1Hive/quests/issues/256#issuecomment-1115557731, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFI2NUFTS2QRDKWXFE4IPLVICGRTANCNFSM5U5NEXIA
.
You are receiving this because you commented.Message ID:
@.***>

In fact we already have that script in WebApp package

We are starting using fleek.co in Gardens with eth.limo domain, looks good option to decentralized hosting.


Add University UNINTER

@FabioMazuchi file/lib/domains/br/com/grupouninter/mava.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@FabioMazuchi Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@FabioMazuchi You might miss my previous comment. Please react.


Reduce volume size for rabbit

While 5Gb migth be a good size for the default db volumes, for
rabbitmq is way too much.
It doesnt help that airship creates a rabbitmq container per component
so we end up with several 5Gb volumes around for a lot of containers.
Instead set it to a more reasonable size (1Gb) which should allow for
rabbitmq to store to persist to disk with no issues

@rajdharwadkar did you test with different values when you actually raised it to 5Gb?


Update KeyStores with new root CA certs

Purpose
Update KeyStores with new root CA certs
Goals
Update KeyStores with new root CA certs
Approach
Update KeyStores with new root CA certs
User stories
N/A
Release note
N/A
Documentation
N/A
Training
N/A
Certification
N/A
Marketing
N/A
Automation tests
N/A
Security checks
N/A
Samples
N/A
Related PRs
N/A
Migrations (if applicable)
N/A
Test environment
N/A
Learning
N/A

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tharindu1st:x: jsdjayangaYou have signed the CLA already but the status is still pending? Let us recheck it.


Fix sign comparison warnings

This does take some thunder from #366 but I think the commit messages are more detailed and it also includes some extra changes/improvements that #366 does not.

@mitchellcash so does this more or less replace #366?

@IngCr3at1on now it does ;)


Suspicious changeset in Colombia

https://osmcha.org/changesets/126791464/

User: https://www.openstreetmap.org/user/MarianaGG/ (Mapper since: September 07, 2022)
#126791464:

[ ] User alerted
[ ] Error fixed
[ ] Issue closed

/remind me check in 2 week

@set-reminder today 5pm Prueba

Done https://www.openstreetmap.org/changeset/127546019

she deleted more highways: https://osmcha.org/changesets/126791579?filters={"users"%3A[{"label"%3A"MarianaGG"%2C"value"%3A"MarianaGG"}]%2C"date__gte"%3A[{"label"%3A""%2C"value"%3A""}]}

she deleted more highways: https://osmcha.org/changesets/126791579?filters={"users"%3A[{"label"%3A"MarianaGG"%2C"value"%3A"MarianaGG"}]%2C"date__gte"%3A[{"label"%3A""%2C"value"%3A""}]}

Pero este seria "otro" changeset :-)

Creator: https://www.openstreetmap.org/user/MarianaGG/ (Mapper since: September 07, 2022)
#126791579:

[ ] User alerted
[ ] Error fixed
[ ] Issue closed

Done https://www.openstreetmap.org/changeset/126791579


Import getAsObject in sidebar-stubs component.

Ref: https://github.com/parameter1/base-cms/pull/135

 Links broken in body of Article


endAngle support for pie chart

Version: 3.2.3
Would be great if pie chart has endAngle proproty, similar to the gauge chart. I'm trying to achieve this:

Where what I seem to be able to achieve with pie chart is:

Also, I wonder whether this could be actually rendered as a bar chart with "polar" coordinate system. I haven't seen this type supported in the doc so haven't tried. This would potentially allow to render things like this one?

@jarben Just recently, I was looking for a similar option. I wanted to use the endAngle on a polar bar chart to achieve the exact same look. I solved it in a hacky sort of way, by leveraging echarts.registerProcessor and re-setting the axis extent. I'm not really sure that it is officially supported, so I'll let @pissang and @Ovilia and @100pah chip in.
echarts.registerProcessor(ecModel => {
  if (ecModel.getComponent('polar')) {
    ecModel
      .getComponent('polar')
      .coordinateSystem.getAxis('angle')
      .setExtent(90, -180);
  }
});

Here's a working example.
https://codepen.io/psumstr/pen/VQdNXy?editors=1010
I've used registerProcessor in the past to get some things like bandWidth of heat map to dynamically show or hide labels.

Awesome, thanks so much for the example @jonavila ! Didn't know about registerProcessor - I'm sure I'll find a lot use of that! Again - thanks for your solution & example..

@jarben Just recently, I was looking for a similar option. I wanted to use the endAngle on a polar bar chart to achieve the exact same look. I solved it in a hacky sort of way, by leveraging echarts.registerProcessor and re-setting the axis extent. I'm not really sure that it is officially supported, so I'll let @pissang and @Ovilia and @100pah chip in.
echarts.registerProcessor(ecModel => {
  if (ecModel.getComponent('polar')) {
    ecModel
      .getComponent('polar')
      .coordinateSystem.getAxis('angle')
      .setExtent(90, -180);
  }
});

Here's a working example.
https://codepen.io/psumstr/pen/VQdNXy?editors=1010
I've used registerProcessor in the past to get some things like bandWidth of heat map to dynamically show or hide labels.

This solution dont work in Echarts version 4.0.2+ :|
I dont know WHY? How we can do it in Version 4.6.0 ?


Aggregate metrics for service and service namespace

We want to collect metrics about individual services so we can alert on a particular services 4xx/5xx rates raising.
This will cause issues for anyone who are relying on how the country filter is currently keyed in the prometheus metrics.

This change is

Coverage decreased (-0.04%) to 44.367% when pulling 934d585ef85842617f6c54713498e6a304713e0d on uswitch:service-metrics into f0144a1df4bb16a921fbea46d73dea9977a93a4b on kubernetes:master.

It's going to take a couple of days to get the CLA through our lawyers, but I would be curious of some feedback on other peopls want of this rollup of nginx metrics.

Coverage decreased (-0.08%) to 44.174% when pulling 7f508bc20b7839ba362ffa231d22b919d89c422a on uswitch:service-metrics into 0c6f15e372c831de52fcc393932540bb3a6d51b5 on kubernetes:master.

@tombooth I really like this but it should be an extension not a breaking change for those that already use the prometheus metrics

@aledbf I've added back the old labels, does this work for you?
Still waiting on our corporate CLA...

Coverage decreased (-0.04%) to 43.57% when pulling 241382eb816eafa7c45080bb22250243fac45419 on uswitch:service-metrics into 2d6f811151c3829b42b175745f7f6a9d0fda38ea on kubernetes:master.

Coverage decreased (-0.08%) to 43.43% when pulling f4a6cbc4d42647a62df1734f5eddce3a0e9c122b on uswitch:service-metrics into ba6c89672d9f7a00140663fc510e588d2bebb6bd on kubernetes:master.

Closing. Please sign the CLA and reopen. Thanks!


*: fix client

Fix client code as a pre-step to client e2e test:

pass in kind plural instead of tpr name to Resource().

I have verify it work in e2e. Want to separate them in PRs.

@xiang90

lgtm


feat: tableplus & sequelpro

Add support for Tableplus & Sequelpro on Mac to the tool

@tanc can we merge this please?


Add check for broken links

Add a step to the build workflow to check for broken links (404 errors)

Will try to use muffet for checking broken links locally


lb_result() does not work on macOS without specifying an exit code

When using lb_result without argument (exit code), it is supposed to pick up the last result ($?).
It works on Linux systems, but apparently not on macOS which returns always 0 as last result.
Need to test this further and specify it in documentation.

Need tests, strange behaviour makes it working now

Cannot reproduce


Added search path: '/Applications/Arduino.app/Contents/Java/'

For some reason I was getting the "Board description file (boards.txt) not found" error on my Mac (10.10) with Arduino 1.6.1.
I found where the search path is specified in ano/environments.py and added this path which leads to the correct file.
I'm not sure if any installations use the old path  ('/Applications/Arduino.app/Contents/Resources/Java') but I didn't want to delete it.
Thanks for all the work on this project.

Interesting. Thanks for the fix.


Error: 'unexpected keyoword arguement 'allowed_methods)

Hi, I get the error for both V3 and V2, please advise on what the correct code would be.
from enverus_developer_api import DeveloperAPIv3
v3 = DeveloperAPIv3(secret_key='SECRET')

I can’t reproduce it(I use python 3.11), but it can be related to python version 3.8 and urllib 1.26.14
I found this article - https://developer.squareup.com/forums/t/python-3-8-10-error-got-an-unexpected-keyword-argument-allowed-methods/8528
Can you please try updating your python version?


Move all the plugin object arguments to PluginContainer

@Cybermaxke You raised the same point a while back. Did I miss something ?
Fix https://github.com/SpongePowered/SpongeAPI/issues/1721
Close https://github.com/SpongePowered/SpongeAPI/issues/892

ConfigManager#getPluginConfig(Object instance)
ConfigManager#getSharedConfig(Object instance)
Task.Builder#submit(Object plugin)

@Lignium
Just a quick note:
This is an API PR, as such I'm focusing on the API.
You need to be careful, some of those methods are used by mods too (see ChunkTicketManager), I can't blindly replace everything.
Thank you for the list. I've missed a few, I will fix it soon.

Sponge API is used by only plugins, isn't it? Mods can only use Forge API.

Sponge API is used by only plugins, isn't it? Mods can only use Forge API.

No, mods can freely use the SpongeAPI if they so wish. Note that they can use their ModContainer as the PluginContainer as we mixin the PluginContainer interface into ModContainer.

Sorry, I worded it poorly.
Let me rephrase that: part of the API is implemented in SpongeForge and it's using Forge methods/classes.
https://github.com/SpongePowered/SpongeAPI/blob/6632f971b9a3b04aa839ed28ce4839e02dc32b9b/src/main/java/org/spongepowered/api/world/ChunkTicketManager.java#L57
https://github.com/SpongePowered/SpongeForge/blob/1544c736731f603d7818e5aff1db7090a2085fd9/src/main/java/org/spongepowered/mod/service/world/SpongeChunkTicketManager.java#L62
In this case, I can't change the signature to PluginContainer.
EDIT: dual explained the part about mods being able to use the SpongeAPI

@ImMorpheus But you may well change the implementation of this method, by using a call of PluginContainer#getInstance() to convert from container to instance.

There would be no point in changing the argument type to PluginContainer then. Why convert back and forth between PluginContainer and Object ?

I'm inclined to agree. The fact that Forge needs the actual plugin instance is an implementation detail really and as @Lignium said, we should make the API accept a PluginContainer if we are doing that everywhere else and deal with the conversion in SC/SF.

@ImMorpheus The issue https://github.com/SpongePowered/SpongeAPI/issues/1721 was about the fact that we were requiring the plugin instance/id and id in the build method and doing this inconsistently.
That issue got fixed in https://github.com/SpongePowered/SpongeAPI/commit/d40b52e9a046a02d072af660b52f589d46f87e0c

I hope you will not reject this pull request?

I will not close it, but it's unrelated.

Previously, the majority of these methods required the actual @Plugin annotated instance to be passed to them, not the PluginContainer, unless I'm mistaken. In that vein, shouldn't the javadocs reflect that we're not passing the plugin instance but, rather, the plugin container? The container is now being referred to as the plugin instance and while it should be obvious given the method signature what's required, it seems inconsistent.
Feel free to ignore my ramblings if I'm wildly off-base.

Previously, the majority of these methods required the actual @Plugin annotated instance to be passed to them, not the PluginContainer, unless I'm mistaken. In that vein, shouldn't the javadocs reflect that we're not passing the plugin instance but, rather, the plugin container? The container is now being referred to as the plugin instance and while it should be obvious given the method signature what's required, it seems inconsistent.
Feel free to ignore my ramblings if I'm wildly off-base.

The current Object can be the PluginContainer or the @Plugin annotated instance. Both are valid options.


gong generates ng code in go directory

problem:
with test
ng library is generated in go/models instead of ng/projects/gong

matTargetPath is nil


chore(jsx): export ComponentWithChildren type

When I run npm run type-check on this repository, I get the following type error.
npm run type-check

> type-check
> tsc

src/middleware/layout.ts:4:45 - error TS2345: Argument of type 'FC' is not assignable to parameter of type 'ComponentWithChildren'.
  Type 'HtmlEscapedString | Promise<HtmlEscapedString> | null' is not assignable to type 'HtmlEscapedString | Promise<HtmlEscapedString>'.
    Type 'null' is not assignable to type 'HtmlEscapedString | Promise<HtmlEscapedString>'.

4 export const LayoutMiddleware = jsxRenderer(Layout);
                                              ~~~~~~

Found 1 error in src/middleware/layout.ts:4

I think the easiest way to fix this is to export the ComponentsWithChildren type.
https://github.com/honojs/hono/blob/4eb101dd03e66e20dfda86e6e5ebce8045d61d05/src/middleware/jsx-renderer/index.ts#L28
Since it can happen that a jsx renderer argument is defined in a different jsx file, I think exporting the type is a good idea, what do you think ?
The author should do the following, if applicable

[ ] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

@yusukebe
Error fixed!
Thanks!


Update documentation for; #index and :#getIndex()

I was searching the docs at http://www.jsviews.com/#jsrapi for a way to get the index of the iteration to use it in a select but couldn't find any helpful information.. It's just after looking at the code that I found it;
<option id="{@:#getIndex() @}" value="">{@:#index @}</option>

Please update the docs to let know that those helper functions exist :)
(or I'am missing something?)

Thanks, you are right, and indeed there are quite a few APIs that are either undocumented or only documented indirectly via samples, and in some case via answers to question on the issues db (here) or on StackOverflow. I will be working on adding that content to the documentation very soon. My priority has been to get the code and APIs stabilized for the V1 release - which should be completed in the upcoming commit - then to work on docs before declaring the official V1.
getIndex() and get()

Closing, but putting under #251

Added to docs here: http://jsviews.com/#viewobject@getIndex


New fixes for parallel optimize and minor fixes

Codecov Report

Merging #497 into deploy will increase coverage by 0.24%.
The diff coverage is 79.41%.

@@            Coverage Diff             @@
##           deploy     #497      +/-   ##
==========================================
+ Coverage   49.59%   49.83%   +0.24%
==========================================
  Files         190      190
  Lines       18301    18459     +158
  Branches     2536     2566      +30
==========================================
+ Hits         9076     9199     +123
- Misses       8798     8822      +24
- Partials      427      438      +11

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 013064f...845168a. Read the comment docs.


apt package for Ubuntu

We should try to support "standard package deployment mechanisms" for different operating systems.  For Ubuntu, I think that would be an apt package.  For MacOS, perhaps Homebrew?  I would like to start with Ubuntu as that is a widely-requested platform.

This relates to the following snippet from a customer issue installing and running on Ubuntu:

I renamed the libusb library, its defaulting to:
Traceback (most recent call last):
  File "wasatch/WasatchBus.py", line 50, in update
  File "wasatch/DeviceFinderUSB.py", line 54, in find_usb_devices
  File "usb/core.py", line 1292, in device_iter
  File "usb/backend/libusb0.py", line 456, in enumerate_devices
  File "ctypes/__init__.py", line 387, in __getattr__
    func = self.__getitem__(name)
  File "ctypes/__init__.py", line 392, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /home/odi-developer/Downloads/ENLIGHTEN-3.2.6/libusb-1.0.so.0: undefined symbol: usb_find_busses

I then renamed all the libusb libraries and copied over the libusb-0.1.so.4 from the native libraries directory, and that seemed to do the trick.
I swapped back to the libusb-1.0 and still same error. I'm guessing only libusb-0.1 will work?


fix: Upgrade system packages and npm

Issue #, if available:
Description of changes: Upgrading system packages and npm, to avoid potential vulnerabilities from outdated versions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Does v0 Dockerfile need Update npm version too?

No, nodejs is only in v1. It was installed with code-editor


Delay switching between tabs

Hello everyone.
I followed this example from docs to dynamically set headerTitle according to the current tab.
https://reactnavigation.org/docs/en/navigation-options-resolution.html#a-stack-contains-a-tab-navigator-and-you-want-to-set-the-title-on-the-stack-header
It works. However, there's a delay to set headerTitle when the tab is swiped.
Related to: #578, #1230

Your Environment

software
version

react-navigation
^3.9.1

react-native
https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz

node
v10.15.3

npm or yarn
<EMAIL_ADDRESS>

How to reproduce
<EMAIL_ADDRESS>

@satya164 I've updated react-navigation in my application to ^3.11.0 and I'm still experiencing this problem.
Did I miss something? :thinking:

You need to use the react-navigation-tabs package

@satya164  I've tried importing from react-navigation-tabs using the versions: 1.1.4 and 2.1.2.
I've still got the same results from this picture :cry:

Hello everyone.
I followed this example from docs to dynamically set headerTitle according to the current tab.
https://reactnavigation.org/docs/en/navigation-options-resolution.html#a-stack-contains-a-tab-navigator-and-you-want-to-set-the-title-on-the-stack-header
It works. However, there's a delay to set headerTitle when the tab is swiped.
Related to: #578, #1230

Your Environment
software	version
react-navigation	^3.9.1
react-native	https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz
node	v10.15.3
npm or yarn<EMAIL_ADDRESS>How to reproduce
<EMAIL_ADDRESS>

Ha. I forgot to publish the new version. Please try now.

Awesome @satya164. It looks much more smooth now.


Fix note type id for syscall enter/leave

Summary
Fix note type for syscall enter/leave in sched_note.c
Impact
Affected only when CONFIG_SCHED_INSTRUMENTATION_SYSCALL is used.
Testing

LGTM.


fix YnUpgrader to use timelock for proxies and correct roles

@gearcat0 holesky deployment already done - we'll need to fix that on he live deployment
i suggest we proceed and fix it later


Fixed duplicate word in themes-overview.md

GitHub Issue: #
PR Type
What kind of change does this PR introduce?
Just refactoring a sentence/code update formatting, repeated word include to including
Description

The change was that in themes-overviews.md I updated the sentence from a repeated word to just one-word fix.
PR Checklist
Please check if your PR fulfills the following requirements:

Commits must be following the Conventional Commits specification
[x] Tested the changes where applicable:

[x] UWP
[x] iOS
[x] Android
[x] WASM
[x] MacOS

Other information

Internal Issue (If applicable):

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

@sfazli96 thank you a lot for your PR, I approved the changes.
As I mentioned here, your commit must be in the Conventional Commits format please.

So if you can update and replace your current commit with a similar commit message please:
- fixed repeated word include twice to including in themes-overview.md
+ docs: Fixed duplicate word in themes-overview.md

@sfazli96 thanks for the PR!
It looks like the Conventional Commits check is still failing because you need to prefix your commit message with an appropriate type, such as fix: or docs:

ok, I see so do i have to make another commit, that's where I am just a little confused. Please explain

ok, I see so do i have to make another commit, that's where I am just a little confused. Please explain

@sfazli96 you will need to adjust the current commit (as conventional commit will still fail if there is still a commit without the proper prefix). Here is the related documentation so you can learn how to adjust your commit message :)
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
Let us know if you have additional questions

@sfazli96 gentle ping for this PR. Please let @iurycarlos or me know if you still need help adjusting your commit so we can merge the changes. Thanks again for your contribution

Ok! @sfazli96 !
I created a new PR so you can compare both.
It is the same fix, but with just one commit.
The commit title is now following Conventional Commits https://www.conventionalcommits.org/en/v1.0.0/#summary

This PR got closed Automatically because the PR (https://github.com/unoplatform/Uno.Themes/pull/1308) was merged
Thank you very much @sfazli96  :)


Documentation updates

What is being addressed
Some documentation enhancements in language and consistency.

/test-force-approve

/test-force-approve


ImportError: No module named lxml

After yesterday's sync, this package doesn't install it's dependencies on lxml and yaml.
apt install -y ros-melodic-urdfdom-py

python -c 'import urdf_parser_py.urdf'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/opt/ros/melodic/lib/python2.7/dist-packages/urdf_parser_py/urdf.py", line 1, in <module>
    from urdf_parser_py.xml_reflection.basics import *
  File "/opt/ros/melodic/lib/python2.7/dist-packages/urdf_parser_py/xml_reflection/__init__.py", line 1, in <module>
    from urdf_parser_py.xml_reflection.core import *
  File "/opt/ros/melodic/lib/python2.7/dist-packages/urdf_parser_py/xml_reflection/core.py", line 1, in <module>
    from urdf_parser_py.xml_reflection.basics import *
  File "/opt/ros/melodic/lib/python2.7/dist-packages/urdf_parser_py/xml_reflection/basics.py", line 4, in <module>
    from lxml import etree
ImportError: No module named lxml

If you look at the dependencies of the debian package, it is missing 2 of them. Are the condition tags parsed properly?
apt depends ros-melodic-urdfdom-py
ros-melodic-urdfdom-py
  Depends: ros-melodic-rospy

experiencing the same running travis tests
I guess it was caused by https://github.com/ros/urdf_parser_py/commit/87b2913d5b5cc06178569191e33b5fded2675b13#diff-34ae68f4adad56c25c5bc05dcb64794e

I think this package is released with old bloom tooling.
If you look at ros_comm, the package xml looks like this and after releasing the condition tags are resolved.
When I look at urdfdom_py the condition tags have not been resolved after releasing with bloom.
@sloretz, is it possible to test releasing this package with bloom 0.9.0?

@sloretz, is it possible to test releasing this package with bloom 0.9.0?

Used bloom 0.9.0 to release 0.4.1-2 in https://github.com/ros/rosdistro/pull/22921
Looks like lxml and yaml are now listed as dependencies.

Thanks!

Looks like lxml and yaml are listed as dependencies in ros-testing, so I'll close this issue for now. It should be fixed in the next sync.

Package: ros-melodic-urdfdom-py
Version: 0.4.1-2bionic.20191109.013217
Architecture: amd64
Maintainer: Chris Lalancette<EMAIL_ADDRESS>Installed-Size: 150
Depends: python-lxml, python-yaml, ros-melodic-rospy
Homepage: http://wiki.ros.org/urdfdom_py
Priority: optional
Section: misc
Filename: pool/main/r/ros-melodic-urdfdom-py/ros-melodic-urdfdom-py_0.4.1-2bionic.20191109.013217_amd64.deb
Size: 31720
SHA256: 16e1acf13815bf96d4fcc53b90c89a5185259959b7299395da3d165e7e3f7f01
SHA1: a0db3d31832c814da041e4d1c809f11bb24b44f7
MD5sum: e21d75614aac5627382c0f031b71fd19
Description: Python implementation of the URDF parser.


unknown shorthand flag: 'p' in -p

Checking proxy... unknown shorthand flag: 'p' in -p
See 'docker --help'.

Usage:  docker [OPTIONS] COMMAND

A self-sufficient runtime for containers

Options:

when running deploy.sh on ubuntu server 22 vm

Oh whoops. I forgot to use the autodetected compose command in the service checker. Sorry about that! Fix coming ASAP.

Please run git pull  to update to Lemmy Easy Deploy 1.0.7 and let me know if that resolves the issue!

it no longer errors about the -p flag but I do not know id this issue is related
reating lemmy-easy-deploy_proxy_1    ...

ERROR: for lemmy-easy-deploy_proxy_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for proxy  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

Checking deployment status...
Checking proxy... ERROR:
        Can't find a suitable configuration file in this directory or any
        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml, compose.yml, compose.yaml

"docker inspect" requires at least 1 argument.
See 'docker inspect --help'.

Usage:  docker inspect [OPTIONS] NAME|ID [NAME|ID...]

Return low-level information on Docker objects

New to docker, does this mean I need to move deploy.sh to live and run it there?

No, that's not what it means. This is a new error I've never seen before. It looks like your Docker service is "stuck."
Can you try these steps for me?
cd ./live

docker-compose -p "lemmy-easy-deploy" down

# If the above command errors, try this instead, also from the ./live folder
docker-compose down

Then, from the Lemmy-Easy-Deploy folder, try running ./deploy.sh -f
If you are still having issues, I would recommend either restarting your Docker service (sudo systemctl restart docker), or outright rebooting your server. Then you can try my above troubleshooting steps once more.
Let me know how all that goes!

its still having a hard time with the proxy and finding the docker file.
Creating lemmy-easy-deploy_proxy_1    ... done

Checking deployment status...
Checking proxy... ERROR:
        Can't find a suitable configuration file in this directory or any
        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml, compose.yml, compose.yaml

"docker inspect" requires at least 1 argument.
See 'docker inspect --help'.

Usage:  docker inspect [OPTIONS] NAME|ID [NAME|ID...]

Return low-level information on Docker objects

Can you please git pull  again, run deploy.sh -d, then paste the output for me here? I need some diagnostic info to understand what's going wrong here.

I've pushed another fix that I believe will resolve this for good. I suspect you might be using Docker Compose v1, which apparently doesn't like only having the stack name passed in with -p. I now cd into ./live before performing service checks.
Please git pull one last time, try again, and if you are still having issues, please include the output of ./deploy.sh -d in your next message!

I have reproduced your issue on Ubuntu 22.04, and I can confirm that the issue is now fixed. Please update Lemmy-Easy-Deploy and try your deployment again.
Please note: this happened because you are using an old and unsupported version of Docker Compose. Lemmy Easy Deploy should still work with the fixes I have applied, but I still recommend you follow the advice given in the Readme, and install the official version of Docker rather than the unsupported version supplied by Ubuntu.
Let me know if you have any additional issues!


OWD project proposal: regularize feature namespaces for CSS, HTML, HTTP, and JavaScript

Summary
Some browser compat data is poorly structured, negatively impacting data consistency, MDN page appearance, and other consumers (e.g., caniuse, VS Code). A relatively small number of changes to BCD and MDN content could eliminate these inconsistencies. Fixing this would involve:

Moving data in BCD
Updating pages to use the moved data
Exploring options for the remaining parts not directly specified (i.e., SVG and webextensions)

Background
Historically, structuring BCD was rather loose. This means some unusual cases exist, which are difficult to communicate to consumers, leave much to be desired in terms of rendering on MDN, and may have more widespread issues (e.g., in caniuse or VS Code). It has also prevented a stronger position on semantic versioning for BCD itself.
See https://github.com/mdn/browser-compat-data/issues/13804 for more details.
Prioritization criteria

Effort

Relatively small, as such things go. I imagine the core part (CSS, HTML, HTTP, and JavaScript) could be completed within a couple of weeks, with a dedicated effort by a writer.
The more speculative part is unknown. There's probably a day or two of analysis to be done; completion effort unknown.

Dependencies

None of note.

Community enablement

Not a large effort. It's unlikely to be shared effectively, or lead to more contributions (as this is cleaning up after contributors).

Momentum

This is a new effort, though BCD has substantial reliance factors.

Enabling learners

Not really applicable. Learners are generally unconcerned with compat issues; they need to support their browser, not all browsers.

Enabling professionals

Significant. Developers need reliable information on which browsers support various APIs, CSS properties, etc.

Underrepresented topics / ethical web

Not applicable.

Operational necessities

Not applicable.

Addressing needs of the Web industry

BCD data is widely used on MDN, caniuse, VS Code, and elsewhere. Far reaching in this area.

This project has now been completed!