Upgrade react-native-sdk to v8.3.0

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/14678
PROPOSAL: https://github.com/Expensify/App/issues/14678#issuecomment-1697142962
Tests / QA Steps

Open Settings > Workspaces > Select any workspace > Connect Bank Account > Add manually
Complete step 1-3 to open the onfido page
Ensure camera permissions are set to Only while using the App
Minimise the app (by heading to the home screen)
Reopen the app.

[x] Verify that no errors appear in the JS console
[x] Verify that no camera permission not granted dialog appears in step 5

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 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 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/58412969/20807691-ce46-4090-81d9-88659dc13e41

Mobile Web - Chrome
NA

Mobile Web - Safari
NA

Desktop
NA

iOS
https://github.com/Expensify/App/assets/58412969/06428b7c-f0e1-49b1-91d7-23cdde8fc9a3

Android

@robertKozik I am unable to do test this on emulator due to problem with playstore.
I think you need to use real device to test this (I am unable to take a screen record from the physical device)

@shubham1206agra What problem with play store? Maybe I can help :)

It's after plaid connection. Play Store is opened and the progress is lost for step 1

@robertKozik Any updates here

@robertKozik ??

Sorry coming back to that PR! 👀

I think we should extend the test cases to cover the entire Onfido flow. After all, we are bumping the library, so checking the whole process would be prudent

@robertKozik ??

I'll take care of testing on the physical devices, but will need a little more time to do so. Until then, please update the screenshots/videos for all platforms, to show up how the onfido flow is behaving (until the point where you cannot access further).

@robertKozik I think we should complete this cause this has taken a month already.

Yeah, I'm on it right 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(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 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 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

Web
https://github.com/Expensify/App/assets/61146594/9b439ae2-b310-40ea-b87b-122f9d623a68

Mobile Web - Chrome
https://github.com/Expensify/App/assets/61146594/19a2371e-9d12-49e1-9e29-97f910f76424

Mobile Web - Safari
https://github.com/Expensify/App/assets/61146594/9936ecb1-1e42-4310-9cfe-9d7603e89cc2

Desktop
https://github.com/Expensify/App/assets/61146594/54fb4cb3-0746-4a4c-b916-20279c691de2

iOS
https://github.com/Expensify/App/assets/61146594/bcabe23a-293f-4ce6-ac82-2ba492d63292

Android
https://github.com/Expensify/App/assets/61146594/eee2423f-7409-4c28-b00d-50ae5d4db075
https://github.com/Expensify/App/assets/61146594/db169e3f-7208-45d8-a89f-170a0cd913cd

Reopen the app and observe that a camera permission not granted dialog appears

Isn't this the bug we are trying to fix? Why is it listed as a test step for QA to observe? 🤔

Reopen the app and observe that a camera permission not granted dialog appears

Isn't this the bug we are trying to fix? Why is it listed as a test step for QA to observe? 🤔

My bad. I have just corrected the step

@robertKozik Can you tell me how did you test the Android?

@shubham1206agra Actually I didn't do anything unusual. It worked for me in emulator with no setup

@marcaaron I have updated the Android video

You can merge this PR now

: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/marcaaron in version: 1.3.84-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform
result

🤖 android 🤖
skipped 🚫

🖥 desktop 🖥
skipped 🚫

🍎 iOS 🍎
skipped 🚫

🕸 web 🕸
skipped 🚫

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.85-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.85-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Update: add DisplayVersion to Araxis Merge 2024.5981

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @gjmatthews,
This manifest adds a DisplayVersion to the AppsAndFeaturesEntries that isn't present in previous manifest versions. This entry should be added to the previous versions, or removed from this version.
(Automated response - build 895.)

Hi @gjmatthews,
This PR and https://github.com/microsoft/winget-pkgs/pull/173755 are creating an issue blocking our Publish pipeline. The DisplayVersion has to be unique across the PackageIdentifier, but these 2 and https://github.com/microsoft/winget-pkgs/pull/173254 all have the same DisplayVersion.
I'm guessing that https://github.com/microsoft/winget-pkgs/pull/173254 has the correct version, since the last 4 digits match the PackageVersion.

Should the DisplayVersion here be updated to 74.30.5981?

@stephengillie The version information here is incorrect, my bad. I shall determine the correct information forthwith and comment here. Apologies for the error.

Please re-check my above comment, as I've heavily edited it with a new and better plan. The current situation might make it difficult for more than 1 manifest for this package to be in the repo at a time.

@stephengillie Thank you for the additional comments – they’re very helpful. We are trying to solve an infinite upgrade problem with the existing 2024.6001 manifest, which is why we are adding the DisplayVersion fields. We do also have a problem with overlapping version ranges in the ARP versions in these latest PRs, caused by the second component of the version number being 30 for EN and 10 for JA.
Your suggestion to split the EN and JA packages looks like a good solution. Please therefore kill this PR (#173756), #173755, and #173254. We will then submit new requests accordingly.
Many thanks again for your help, and once more I extend my apologies for the inconvenience.


Provide an envoy binary package based on RPM and Ubuntu instances for ARM64 architecture

I am trying to install envoy on the arm64 platform using this document, but it is failing. On using the command  sudo apt install -y getenvoy-envoy it displays the error E: Unable to locate package getenvoy-envoy.  It looks like the envoy binary is not available for the arm64 platform. It will be useful if we have a envoy binary for the arm64 platform.
If interested, we can get access to ARM H/W through WorksOnArm.

hi @odidev this has been an outstanding issue for a while (there are few related existing tickets)
we recenty made some progress here and now have debs (with the static Envoy binary)  built/tested in CI - for both x86_64  and arm64
the next steps are adding rpm support and hooking up the website to start publishing the builds

Sounds good. Can you please provide some possible dates when you are going to release the arm64 binary?

at this point, not sure about exact dates
at this point Envoy CI is building and testing the binaries so I guess before we start publishing these officially it would be good to start testing them
i can add a PR that adds the first part of the publishing pipeline in the next few days - once that is in place it should be possible to download the debs and test them with dpkg -i
in terms of rpms i have tried a couple of approaches - one based on rules_pkg and another (more hermetic) build based on https://github.com/google/rpmpack
i havent tested in a while but rules_pkg has been developed quite a bit so i want to look again at it (this is what is being used to package debs)
any help testing or progressing this would be greatly appreciated

It’s good to know that you have already made some progress. It would be nice if PR was available. I will try to contribute from my side.

Any updates on this?

not as yet, ive been busy with other things, but its v much on my todo list

I understand, let me know if I can help when you are ready

Any news on this?

Hi Team,
Adding a gentle reminder to take a look at the above issue.

hi see #16867  for further info


Why doesn't the Compphys notebook show any interactive plot?

I think the 3D plotting is not properly installed. Play with it a little and it will work. it happened to me too, then I fixed it. @Mosaddeq107

@ I have that problem too. How did you fix it @uarif

I have solved the problem. https://github.com/ubsuny/23-Homework7G5/pull/40

Did you figure out? @Mosaddeq107 . If not I can share my part of the code which works and you can see what is it working for me,

I have solved the problem. ubsuny/23-Homework7G5#40

what exactly is the solution to the problem?

I think adding these lines should resolve the prob.
%matplotlib inline
import matplotlib.pyplot as plt
from mpl_toolkits.mplot3d import Axes3D

It works for me.

Yes, I guess it doesn't work for some people but there is a solution


Fix grammar in PULL_REQUEST_TEMPLATE.md

Description
Fix grammar in PR template

Oh good catch, thanks @nohwnd


Customizing the TimelineItem middle element

It is not such a big thing, but... I have a requirement to modify the padding and border for this middle element to:
		timelineYear: {
			alignSelf: 'flex-start',
			padding: '0 12px',
borderRadius: '50%',
			backgroundColor: props => props.yearBackgroundColor,
			color: props => props.yearColor,
		},

Could be possible to make them as a props too, or maybe the class itself to be overridden?
Thanks.

Yes, it can be extended, will do so tomorrow.


Error in using multi GPUs

I'm sorry that when I use your code on huggingface to use multi GPUs, I encountered the following error:
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_bmm)
The script core is as follows:
def split_model(model_name):
device_map = {}
world_size = torch.cuda.device_count()
num_layers = {
'InternVL2-1B': 24, 'InternVL2-2B': 24, 'InternVL2-4B': 32, 'InternVL2-8B': 32,
'InternVL2-26B': 48, 'InternVL2-40B': 60, 'InternVL2-Llama3-76B': 80}[model_name]
# Since the first GPU will be used for ViT, treat it as half a GPU.
num_layers_per_gpu = math.ceil(num_layers / (world_size - 0.5))
num_layers_per_gpu = [num_layers_per_gpu] * world_size
num_layers_per_gpu[0] = math.ceil(num_layers_per_gpu[0] * 0.5)
layer_cnt = 0
for i, num_layer in enumerate(num_layers_per_gpu):
for j in range(num_layer):
device_map[f'language_model.model.layers.{layer_cnt}'] = i
layer_cnt += 1
device_map['vision_model'] = 0
device_map['mlp1'] = 0
device_map['language_model.model.tok_embeddings'] = 0
device_map['language_model.model.embed_tokens'] = 0
device_map['language_model.output'] = 0
device_map['language_model.model.norm'] = 0
device_map['language_model.lm_head'] = 0
device_map[f'language_model.model.layers.{num_layers - 1}'] = 0
return device_map

path = 'OpenGVLab/InternVL2-40B'
device_map = split_model('InternVL2-40B')
model = AutoModel.from_pretrained(
path,
torch_dtype=torch.bfloat16,
load_in_8bit=True,
low_cpu_mem_usage=True,
use_flash_attn=True,
trust_remote_code=True,
device_map=device_map).eval()
tokenizer = AutoTokenizer.from_pretrained(path, trust_remote_code=True, use_fast=False)
So how can I adjust it to implement multi GPU inference on V100? Thank you very much for your reply.

This error may occur when the version of transformers is higher than 4.44, you can add the following code when constructing the device map to fix this issue: device_map['language_model.model.rotary_emb'] = 0

Thank you very much for your suggestion. Now this problem is solved. I have another question: if I want to use a message type, which consists several "role"s and "content"s, which function should I use ? And how can I pass the parameters?
message=[
                {"role": "system", "content": f"..."},
                {
                    "role": "user",
                    "content":' ...',
                },
                {
                    "role": "assistant",
                    "content": "...",
                },
                ]

We organize the inputs into the message type in this part. You can implement your inference code by referring the the batch chat function of InternVL.


Only warnThemePackage on not restart

if (logLevel && !isRestart) {
    warnThemePackage(themePackage, logger);
}

if (hasIssues) {
	logger.warn(
		"These warnings in order to notice for people who are preparing to submit theme to the Astro integration page, ",
	);
	logger.warn(
		"If you don't want to submit your theme, you can set `'private': true` inside the `package.json` to suppress these warnings.",
	);
}

Thanks for tackling this! I updated the branch and push some tweaks to the warning messages (I hope that is ok). What do you think? Should we tweak them more?

it's ok


index cache: Cache expanded postings

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
Fixes https://github.com/thanos-io/thanos/issues/6417.
This pr adds new methods in index cache to store and fetch expanded postings. Previously, we store postings which associated with a label. This means to calculate expanded postings, we need to fetch all postings from cache and then expand the postings. This could waste resources if the expanded posting length is mucher smaller than the size of original postings. By caching expanded postings, it saves both mem/bandwidth and CPU times to download data and calculate postings.
Verification
Tests updated. Also tested locally with both in memory cache and memcached

Before making this change, we have around 90K requests going to our index cache to fetch postings.
After having expanded postings cache, we have around 300 requests going to index and postings request reduced drastically.


Class fields are too new for Uglifier

I was seeing errors when trying to precompile assets for production environment (RAILS_ENV=production bundle exec rake app:assets:precompile in the docker container).

Uglifier::Error: Unexpected token: operator (=)
--
87160     funder_name.css('border-color', '#ccc');
87161   }
87162 }
87163 ;
87164 // Example:
87165 // $("body").trigger("clear_inputs", [$(el)])
87166
87167 class InputClearableListener {
=>   eventName = "clear_inputs"
87169
87170   constructor(){
87171     this.registerListeners()
87172   }
87173
87174   registerListeners(){
87175     $("body").on(this.eventName, this.onEvent.bind(this))
87176   }

It looks like these compile if moved into the constructor.

Could we update Uglifier, or is that brought in from upstream?
I suppose an alternative would be move the code outside of the asset pipeline, and require it from a public folder.

Could we update Uglifier, or is that brought in from upstream?
I suppose an alternative would be move the code outside of the asset pipeline, and require it from a public folder.

I don't think we can upgrade Uglifier to handle this.  I was using an online ESLint and none of the available ECMA Version options liked the class fields.  I don't think we should bypass Uglifier because I'd be afraid of not having browser support for it. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields#browser_compatibility)
I think this should spawn a discussion about browser support and which versions we are claiming to support for which parts of the application (backend vs. frontend).

I don't think we can upgrade Uglifier to handle this.  I was using an online ESLint and none of the available ECMA Version options liked the class fields.  I don't think we should bypass Uglifier because I'd be afraid of not having browser support for it. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields#browser_compatibility)
I think this should spawn a discussion about browser support and which versions we are claiming to support for which parts of the application (backend vs. frontend).

Thanks for explaining @cjcolvar. I'll keep in mind that the class properties are not yet available to us.

Thanks for explaining @cjcolvar. I'll keep in mind that the class properties are not yet available to us.


Is Blazor development is possible (on linux) or someone have worked with Blazor on linux

Yesterday I tried Blazor on my windows machine and it's look good. I am interested to use my linux machine for programming web-app using Blazor.
Do someone have successfully used Blazor on Mac and linux. Most of time I seen demos using VS on Windows machine.
Did someone tried it practically.

It works great on Windows, Mac, and Linux. There is nothing OS-specific about developing with it or where it can run.

@anirugu Thanks for contacting us.
@Eilon answer is correct.
If you find something is not working on either Mac or Linux, please file an issue with a repro project and detailed repro steps and we'll investigate.
Thanks!


Resolve symlinks for cargo and xargo home.

Resolve symlinks for the xargo and cargo home (as well as the Nix store) prior to mounting, since they are mounted at a fixed location anyway. This is because podman mounts symlinks as root by default. We always canonicalize the paths on the host, after creating them, to ensure that any symlinks are resolved.
Say we have /path/to/home, and /path/to is a symlink but /path/to/home doesn't exist yet. Trying to canonicalize /path/to/home/.xargo will fail, and will still be a symlink if we maybe canonicalize before. First creating the directories and canonicalizing them on the host should always work.
Change the mount points from /cargo, /xargo, and /rust to the same paths as on the host, which avoids unnecessary recompilation when cargo and cross are intermittently used.
Closes #280.
Closes #373.
Closes #551.

bors r-

Yeah, I planned on converting this to a draft before my internet died.

I think this is ready: it fails if the symlink exists but is broken, but that's a feature I believe, and will error with the following warning:
rror:
   0: File exists (os error 17)

We probably want to wrap that error to explain what file exists, however.

This is a cool change, it also makes it more clear in verbose build that you're actually running a binary mounted from your host system, since /my/home/.rustup/toolchain/toolchain is more prevalent now

test_host is failing due to stable-x86_64-unknown-linux-gnu not existing, I think it's fine to pre-install this toolchain in the test job (only in the test job though)

test_host is failing due to stable-x86_64-unknown-linux-gnu not existing, I think it's fine to pre-install this toolchain in the test job (only in the test job though)

We might need a better strategy. Let me think...

Ok I've changed this to use the host target triple (only for the unittest), so the toolchain will always be installed.

bors r=Emilgardis


api: Thermocycler execute profile bug in opentrons_simulate 5.0.2

Overview
We have an issue where there is a key error for any "execute_profile."

Steps to reproduce

Include tc_execute_profile with any quantity of steps on 5.x.x
Receive a software error

metadata = {
    'protocolName': 'Thermocycler Example Protocol',
    'author': 'Opentrons<EMAIL_ADDRESS>    'source': 'Protocol Library',
    'apiLevel': '2.12'
    }

def run(protocol):
    tc_mod = protocol.load_module('thermocycler')
    # run profile
    profile = [
        {'temperature': 90, 'hold_time_seconds': 10}
    ]

    tc_mod.execute_profile(steps=profile, repetitions=1)

Current behavior
Traceback (most recent call last):
  File "/Users/alexcopperman/opt/anaconda3/bin/opentrons_simulate", line 8, in <module>
    sys.exit(main())
  File "/Users/alexcopperman/opt/anaconda3/lib/python3.9/site-packages/opentrons/simulate.py", line 605, in main
    print(format_runlog(runlog))
  File "/Users/alexcopperman/opt/anaconda3/lib/python3.9/site-packages/opentrons/simulate.py", line 391, in format_runlog
    + command["payload"].get("text", "").format(**command["payload"])
KeyError: "'temperature'

Expected behavior
Thermocycler starting 1 repetitions of cycle composed of the following steps: [{'temperature': 90, 'hold_time_seconds': 10}]

work around
install 4.7.0

Same as #9799

Same problem for me when simulation protocol with a thermocycler profile. Any solutions?🐶
Traceback (most recent call last):
File "/Users/fankangmeng/opt/anaconda3/bin/opentrons_simulate", line 8, in
sys.exit(main())
File "/Users/fankangmeng/opt/anaconda3/lib/python3.8/site-packages/opentrons/simulate.py", line 605, in main
print(format_runlog(runlog))
File "/Users/fankangmeng/opt/anaconda3/lib/python3.8/site-packages/opentrons/simulate.py", line 391, in format_runlog
+ command["payload"].get("text", "").format(**command["payload"])
KeyError: "'temperature'"

@FankangMeng this will be resolved in the upcoming v5.1.0 release, which is currently undergoing testing

@FankangMeng this will be resolved in the upcoming v5.1.0 release, which is currently undergoing testing

Thank you!

Just a heads up @FankangMeng the next release will be v6.0.0 (but this will still be part of that)


Illegal instructions

I try to run script on Linux Ubuntu 20.04
Got error illegal instructions
Can anyone help me out of this

you didn't provide much information, but most likely you're trying to use too new of a version of tfjs-node that relies on modern instructions such as avx that are not supported on older cpus or some virtualized systems (such as when using qemu which is common in university environments).
solution? find older version of tfjs-node that works or switch to wasm backend that uses bytecode.


UnrecognizedPropertyException

Hi,
When I want to get account info I get a com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.
What am I doing wrong?

The server API has changed since the last time I checked the client compatibility. Consider using the following guide to generate the client library from the OpenAPI specification Alpaca provides.


fix: Run locally with 'act' fails (#28)

Use jbang full path to bypass 'act' issue with PATH env var (See https://github.com/nektos/act/issues/896)

Closing. Will open new one.


wofi and bemenu don't display correctly

while using magmawm, if I spawn a wofi or bemenu_run process, it handles input and spawns programs as it should, but the wofi/bemenu window never updates
the issue was found on fedora 39 with magmawm installed from git main following the instructions in the readme
below is a recording of this behavior (with magmawm running on an x11 window, sorry for the quality and aspect ratio)
https://github.com/MagmaWM/MagmaWM/assets/132933465/ac2c4c7b-b09f-4ca8-b30f-1e31ae5e705d
log files obtained by running
export WAYLAND_DEBUG=1
sway &> sway_bemenu # use bemenu_run in sway
sway &> sway_wofi # use bemenu_run in sway
<magma run script> &> magma_bemenu # use bemenu_run in magma
<magma run script> &> magma_wofi # use wofi in magma

in a tty
magma_bemenu.log
magma_wofi.log
sway_bemenu.log
sway_wofi.log
the magma config
config.ron.txt
and the wofi config, if it's needed
config.txt
style.css.txt
(edit)
I provided the wrong logs, these logs were obtained by running
# in magmawm
wofi &> magma_wofi
bemenu-run &> magma_bemenu
# on sway
wofi &> sway_wofi
bemenu-run &> sway_bemenu

magma_bemenu.log
magma_wofi.log
sway_bemenu.log
sway_wofi.log
(the .log extension was added to let github upload the files to the issue)

able to reproduce using wofi -d via magmawm inside awesomewm, i cant type into it myself
will be testing further to see if i can reproduce, also reproduced with fuzzel (wofi is unmaintained, fuzzel recommended)

It's because no frames are getting sent to any layer surfaces.
Tacking on
diff --git a/src/backends/winit.rs b/src/backends/winit.rs
index a11f44e..4d5174f 100644
--- a/src/backends/winit.rs
+++ b/src/backends/winit.rs
@@ -343,6 +343,16 @@ pub fn winit_dispatch(
         )
     });

+    drop(layer_map);
+    for layer in layer_map_for_output(output).layers() {
+        layer.send_frame(
+            output,
+            state.start_time.elapsed(),
+            Some(Duration::ZERO),
+            |_, _| Some(output.clone()),
+        );
+    }
+
     workspace.windows().for_each(|e| e.refresh());
     data.display_handle.flush_clients().unwrap();
     state.popup_manager.cleanup();

seems to fix the issue. Though there might be a better place to put this idk, and you'd need to do the same for the udev side

ty, i will look into implementing this
sorry for the late response, development has been stalled lately


Contributions

Hello @kennethreitz, is this repo open for contributions and if yes, is there a quick start guide about this for the contributors? I'd be happy to contribute to this.

i'm still in prototype sprint mode, but i'll try to take a look at anything you come up with!

@kennethreitz Any quick start guide shall be very helpful to get started on what the project is about!


Multi PAT support for GH to GH migrations

For GH to GH migrations we need to support a source PAT in addition to the target PAT. By default if it is not provided, it should fall back to the target PAT.
Todo

[ ] Leverage GH_SOURCE_PAT for the source repo, if not provided fall back to the existing GH_PAT.

This is only for gei version of the CLI. The ado2gh one will continue to use ADO_PAT for source ADO and GH_PAT for target GitHub.


Transactor: LoadWallet

Should attempt to decrypt the on-disk file. On success, sets the private key on the transactor struct.
Make a call to rusk, method Keys. Return the public key.

Related to #411

Fixed via #450


Cannot publish when using TypeScriptOutDir

When my project contains a custom typescipt output directory, I cannot publish my project using VS 2013 Update 3/4 or when pushed to Azure/Kudu.
e.g. Inside Host.csproj:
 <TypeScriptOutDir>.\obj\jsoutput</TypeScriptOutDir>

will cause the following error appears in the publish log:
Copying file .\obj\jsoutput\Host.js to obj\Debug\Package\PackageTmp\.\obj\jsoutput\Host.js failed.

Could not find a part of the path '.\obj\jsoutput\Host.js'.

If I comment the line out, the publish succeeds. This happens with various other paths, not just the one from the example above.
A similar issue this was previously raised here: https://github.com/Microsoft/TypeScript/issues/292

The good news is this is fixed - I installed the 1.5 beta and could successfully publish.
The bad news is it's not on Azure/Kudu yet, so I have to stick with manual publishes!
Thanks for your help.


[Python] environment files are not parsed correctly

First of all the current .env Shenanigans:
this is my .env file (just to be sure i also used the {$env:VAR} syntax)
BASEPATH=G:/Path/ProjectName PYTHONPATH=${env:BASEPATH}/src/pri1;${BASEPATH}/src/pri2;${BASEPATH}/src/sub1;${BASEPATH}/src/sub2;${BASEPATH};${env:PYTHONPATH}
this is show_pythonpath.py
`import os
print(str(os.environ['PYTHONPATH']))`
now we start it in debug configuration to make sure the envfile is actualy considered.
here the output
(.venv) PS G:\Path\ProjectName>  & 'g:\SIMS4\ModYourselfe\.venv\scripts\python.exe' 'c:\Users\anon\.vscode-insiders\extensions\ms-python.python-2021.2.513962232-dev\pythonFiles\lib\python\debugpy\launcher' '52428' '--' 'g:\Path\ProjectName\show_pythonpath.py' ${env:BASEPATH}/src/pri1;${BASEPATH}/src/pri2;${BASEPATH}/src/sub1;${BASEPATH}/src/sub2;${BASEPATH};${env:PYTHONPATH}
so first line is the call and second line the output from the print call.
yesterday befor the insider update there would actualy be full paths in the output. just every PYTHONPATH setup i use doesn't work right now. i tried to set it in the workspace settings but there was no substitution at all.
now to the second part:
working with environment variables is like crazy right now. one day your setup works. the next day a random update appears and your setup is trashed and sometimes the workarounds are just too farfetched to be even considered.
to give something constructive:
the whole .env stuff is actualy good as it's intended in the documentary, if it would work as intended. there is still a thing i would improve. Make the console environment selectable. 3 options: "default env fiel", "config","system"

i just looked at the the second entry of the bot and will repost this in the extension repostry.
i'll leave it open for the case that the second part is considerable

i just looked at the the second entry of the bot and will repost this in the extension repostry.
i'll leave it open for the case that the second part is considerable

/extPython

/extPython


Event AnalyticsEventScreenView is not available

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.2.0b2.3094
Firebase Unity SDK version: 6.15.2
Source you installed the SDK: Unity Package Manager (.unitypackage or Unity Package Manager)
Problematic Firebase Component: Crashlytics, Analytics (Auth, Database, etc.)
Other Firebase Components in use: none (Auth, Database, etc.)
Additional SDKs you are using: none (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Mac (Mac, Windows, or Linux)
Platform you are targeting: iOS (iOS, Android, and/or desktop)
Scripting Runtime: Not sure what this means (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:
The blog post at https://firebase.googleblog.com/2020/08/google-analytics-manual-screen-view.html mentions that calling SetCurrentScreen is deprecated.
But there is no AnalyticsEventScreenView event in Firebase.Analytics.FirebaseAnalytics
I even tried sending a screen_view string (as that is what is mentioned in the blog post) but I'm getting back an error saying
Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: error (_err), {
    ga_debug (_dbg) = 1;
    ga_error (_err) = EventNameIsReserved (13);
    ga_error_value (_ev) = screen_view;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
}

FYI, manually updating the pod file to use
  pod 'Firebase/Analytics', '6.29.0'
  pod 'Firebase/Core', '6.29.0'

Made this work:
        Firebase.Analytics.FirebaseAnalytics.LogEvent("screen_view", new Firebase.Analytics.Parameter("screen_name", name));

Thanks for reporting this and giving us a workaround. If you've installed Messaging via the unitypackage (vs. via EDM4U), you should be able to change MessagingDependencies.xml from this:
<dependencies>
  <iosPods>
    <iosPod name="Firebase/Messaging" version="6.24.0" minTargetSdk="8.0">
    </iosPod>
  </iosPods>
  <androidPackages>
    <androidPackage spec="com.google.firebase:firebase-messaging:20.1.7">
    </androidPackage>
    <androidPackage spec="com.google.firebase:firebase-analytics:17.4.1">
    </androidPackage>
    <androidPackage spec="com.google.firebase:firebase-messaging-unity:6.15.2">
      <repositories>
        <repository>Assets/Firebase/m2repository</repository>
      </repositories>
    </androidPackage>
  </androidPackages>
</dependencies>

to this:

<dependencies>
  <iosPods>
    <iosPod name="Firebase/Messaging" version="6.29.0" minTargetSdk="8.0">
    </iosPod>
  </iosPods>
  <androidPackages>
    <androidPackage spec="com.google.firebase:firebase-messaging:20.1.7">
    </androidPackage>
    <androidPackage spec="com.google.firebase:firebase-analytics:17.4.1">
    </androidPackage>
    <androidPackage spec="com.google.firebase:firebase-messaging-unity:6.15.2">
      <repositories>
        <repository>Assets/Firebase/m2repository</repository>
      </repositories>
    </androidPackage>
  </androidPackages>
</dependencies>

(ie: change the version to match the pod).
I don't know if you'll also have to track down Firebase/Core to make a similar change in AppDependencies.xml. See this medium post as an explanation of how this is all going together.
I'm going to mark this as a feature request, and it'll likely get resolved the next time the Firebase Games SDK for Unity is updated.

Good news. 6.16.0 is release and it should be using iOS SDK 6.32.2, which is above 6.29.0
I'll close this issue for now.  If the issue remains, please report a new bug using bug template


Make "run example" more visible

The contrast on the "run" button is pretty low, which causes it to be missed by people not familiar with the doc page. It should have more contrast, maybe a 🏃♀ or 🚀 emoji there

@auareyoualgolia Can you give us your insight on that?

Sure!! Can I get screenshot please? :)

Sure @auareyoualgolia :)

I think the main issue is the position of the button, it should be on the very right to gain a bit more visibility, and if we fix the color like this I think it will really improve.

Ignore the icon for copy, it's from the last iteration we did :)

You could also go for this one, if you don't want it to be something that draws attention as you scroll:

Closed because the documentation has been migrated to the Algolia documentation website.


TP2000-215 Add defusedxml package to protect against XML parsing vulnerabilities (pt.2)

TP2000-215 Add defusedxml package to protect against XML parsing vulnerabilities (pt.2)

Why

The commodities importer throws a 500 when given a file with a document type declaration. The other importer silently errors when given dodgy files
What

Refactor importer forms to inherit from ImportForm and add view and form tests for importer/create endpoint.
Update test files to set file type as xml
Add superuser test fixtures

Codecov Report

Merging #659 (c1cc33a) into master (a952c85) will increase coverage by 0.03%.
 Consider uploading reports for the commit c66ddaf to get more accurate results

@@            Coverage Diff             @@
##           master     #659      +/-   ##
==========================================
+ Coverage   93.40%   93.43%   +0.03%
==========================================
  Files         324      325       +1
  Lines       21051    21107      +56
  Branches     1671     1671
==========================================
+ Hits        19663    19722      +59
+ Misses       1068     1065       -3
  Partials      320      320

Impacted Files
Coverage Δ

commodities/tests/test_views.py
100.00% <ø> (ø)

importer/forms.py
80.00% <79.54%> (+1.87%)
:arrow_up:

commodities/forms.py
72.00% <80.00%> (-5.62%)
:arrow_down:

commodities/tests/test_forms.py
100.00% <100.00%> (ø)

conftest.py
95.81% <100.00%> (+0.06%)
:arrow_up:

importer/tests/test_forms.py
100.00% <100.00%> (ø)

importer/tests/test_views.py
100.00% <100.00%> (ø)

importer/views.py
100.00% <0.00%> (+9.52%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


assert target.dim() == 3 error

I got a error in loss.py line 54. I print my target size is (2,768,768,3), but the code shows it should be dim 3. my predict size is (2,3,768,768).
I use my own dataset, picture annotation like cityscapes. then I get this error. I don't know what happen.

Hi @midtom
How did you resolve this issue?
I am facing it at the moment when I use my own model for training. Thanks in advance.

@dronefreak ,@midtom
did you resolve this issue?
I have the same problem,can you give me some advice? thank you!

@dronefreak ,@midtom
did you resolve this issue?
I have the same problem,can you give me some advice? thank you!

Please confirm whether the label is single channel.

This is essentially a dimension mismatch issue, looks like your target size is in channels_last format whereas your prediction is in channels_first. Reshaping either of the two tensors will solve your issue. Also, please make sure that your both target and predictions are single channel tensors.

thank you so much. i got it

@Tramac,@dronefreak,i meet anthor problem:
when i reshape both my target size and images size are channels_first,an error was reported below:
Traceback (most recent call last):   File "train.py", line 208, in <module>     trainer.train()   File "train.py", line 130, in train     for i, (images, targets) in enumerate(self.train_loader):   File "/home/liyanzhou/anaconda3/envs/py36torch10_fastscnn/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 560, in __next__     batch = self.collate_fn([self.dataset[i] for i in indices])   File "/home/liyanzhou/anaconda3/envs/py36torch10_fastscnn/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 560, in <listcomp>     batch = self.collate_fn([self.dataset[i] for i in indices])   File "/home/liyanzhou/pycharm_project/demo/Fast-SCNN-pytorch-master/data_loader/segbase.py", line 50, in __getitem__     img = self.transform(img)   File "/home/liyanzhou/anaconda3/envs/py36torch10_fastscnn/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 61, in __call__     img = t(img)   File "/home/liyanzhou/anaconda3/envs/py36torch10_fastscnn/lib/python3.6/site-packages/torchvision/transforms/transforms.py", line 164, in __call__     return F.normalize(tensor, self.mean, self.std, self.inplace)   File "/home/liyanzhou/anaconda3/envs/py36torch10_fastscnn/lib/python3.6/site-packages/torchvision/transforms/functional.py", line 208, in normalize     tensor.sub_(mean[:, None, None]).div_(std[:, None, None]) RuntimeError: The size of tensor a (768) must match the size of tensor b (3) at non-singleton dimension 0
the image size and target size are transform transpose img shape: (1, 768, 768) transform transpose mask shape: (1, 768, 768)
how to resolve it?i need some advice,thank you!

Oh you would need to expand the dimensions using torch.unsqueeze(), this will add a 4th dim to your tensor (batch size), which is expected by your pytorch model. Input tensors to the model should have 4 dimensions, [batch_size, channels, height, width].

Wonderful!Maybe I read the images was wrong! I should read them with RGB,but I read them with single channel.Thank you!
Now the network can run,but the loss is high loss =0.1887. The learning rate is 0.001.
By the way,the shape of outputs and target are torch.Size([4, 2, 768, 768]) torch.Size([768, 768]),is this normal?
@Tramac @dronefreak

Okay so that means you have a batch size of 4 and perhaps you are doing a binary (2-class) classification? Target size seems a bit off, as there should be the num_channels and batch_dim as well. Ideally your label should have the same size as that of your output, otherwise you would run into potential dimension mismatch issues, while calculating your losses.

if there is a contradiction between the 'your label should have the same size as that of your output' and ’assert predict.dim() == 4 assert target.dim() == 3 ‘ ?

你好，李yanzhou已经收到你的邮件，谢谢！

请问您最后怎么解决的呢？outputs：torch.Size([2, 2, 768, 768]) ；target：torch.Size([2, 768, 768, 3])


Is it safe to access one buntdb(data.db) from both processes?

Assuming that there are two processes, one process only reads and the other process reads and writes, is it safe to do so?

I wouldn't count on it being safe. BuntDB is only designed for one process at a time.


Old Leiningen template

Running lein new swagger1st myproject as instrcuted in README finds [swagger1st/lein-template "0.15.1"] on Clojars and generates a project that has [io.sarnowski/swagger1st "0.15.0"] as dependency.

Good point, thanks. I think the code has been updated, so we should be good with just releasing a new version of the template.

Hi @sebastianpoeplau, any news on this issue or can we close?

@LappleApple I'm afraid we don't have access to the Clojars account that hosts the template. @sarnowski, would you mind giving us access?

Why was this closed?

@immoh Because @sarnowski provided the information requested.

I upgraded everything and released it to clojars:
https://clojars.org/swagger1st/lein-template/versions/0.25.0


wncm14a2a modem should be moved to a shield configuration

The modem is part of a shield, currently is hardcoded into the frdm_k64f board DTS. We should move it to a shield an make it available to other boards.

@erwango What is your recommendation for establishing digital pin exports from the main board in DTS?
Under non-shield configuration:
       wncm14a2a {
               compatible = "wnc,m14a2a";
               label = "wncm14a2a";
               mdm-boot-mode-sel-gpios = <&gpioc 17 0>;
               mdm-power-gpios = <&gpiob 9 0>;
               mdm-keep-awake-gpios = <&gpioc 2 0>;
               mdm-reset-gpios = <&gpioc 12 0>;
               mdm-shld-trans-ena-gpios = <&gpioc 4 0>;
               mdm-send-ok-gpios = <&gpiod 0 0>;
               status = "ok";
       };

These should be exported in some way from the main board's DTS (note this doesn't work):
arduino_d10: <&gpiod 0 0>; {};
arduino_d9: <&gpioc 4 0>; {};
arduino_d8: <&gpioc 12 0>; {};
arduino_d6: <&gpioc 2 0>; {};
arduino_d2: <&gpiob 9 0>; {};
arduino_d1: <&gpioc 17 0>; {};

@mike-scott
There were on going work on dtc to enable similar stuff (https://elinux.org/images/d/d0/Panto.pdf) , but I don't know current status. I'll check on dtc status and come back to you.
There are some ways to get dtc compiled and have something like (in dts_compiled file). For instance:
arduino_spi: &spi1 {

	arduino_dx: pin {
		 gpios = <&gpioa 8 0>;
	 };

Would compile into
		arduino_spi: spi1: spi@40013000 {
			[...]
			arduino_dx: pin {
				gpios = <0x5 0x8 0x0>;
				phandle = <0x6>;
			};

			bt0: spbtle-rf@0 {
				[...]
				reset-gpios = <0x6>;
			};
		};

But then it requires some hack in extract_dts_include script to do the last step, would be better to have this done in dtc. So this would work, but would be a divergence from Linux. It seems we are a the edge of the dtc features here... Maybe @galak you have more inputs?
So either we chose our on way, waiting to have things integrated (maybe in a different way) in Linux, either we wait Linux. Let's check last dtc status before going further.

Did we come to any resolution for making placeholders for the gpio pins:
Hack extract_dts_include script or make a change to dtc?
I didn't see @galak weigh in on either.

Did we come to any resolution for making placeholders for the gpio pins:
Hack extract_dts_include script or make a change to dtc?
I didn't see @galak weigh in on either.

what do you mean by place holders?

I was explaining above, that along with the UART which can currently be configured in the shield dts as a placeholder like so:
&arduino_serial {
       wncm14a2a {
               compatible = "wnc,m14a2a";
               label = "wncm14a2a";
               status = "ok";
       };
};

This is "connected" to the K64F dts (exposes the fact that there's a serial on the arduino headers):
arduino_serial: &uart2 {};

There are also 5 GPIO pins which need to be handled by the modem driver.  These are not so easy to export in this way.  @erwango had a fairly good idea illustrated above.
Something like this connecting the Arduino D13 pin to the K64F's PTD1 pin:
	arduino_d13: pin {
		 gpios = <&gpiod 1 0>;
	 };

@agross-linaro , did you had the chance to discuss this point at plumbers?

RFC to discuss supporting GPIOs in a sane way for shields: https://github.com/zephyrproject-rtos/zephyr/pull/14057

Closed by: https://github.com/zephyrproject-rtos/zephyr/commit/c0d9e7fcb5c4a3329273f8b137187abb288feda5#diff-a56763253b3f0eebe8c067f6a3ebba0b


Image deletion improvement

Currently the method to delete is all over the place.
We could have made this a separate controller so all deletions go through this.
Controllers below don't have image deletion method:

[x] Bundle Controller

Created a new Image controller to handle image deletions at commit 6bc3387


Improve response latency against a large DB

Looking at the logs are are some opportunities:
<EMAIL_ADDRESS>  | Profiling Endpoint: /api/projects/Project1/rank
<EMAIL_ADDRESS>  | |-> getRanking(projectId=Project1,userIdParam=000000000007,idType=ID) (1) : 5s 012ms [016ms]
<EMAIL_ADDRESS>  | |     |-> RankingLoader.doGetUserSkillsRanking (1) : 4s 984ms [006ms]
<EMAIL_ADDRESS>  | |     |     |-> RankingLoader.findNumberOfUsers (1) : 4s 976ms
<EMAIL_ADDRESS>  | |     |     |-> RankingLoader.calculateNumberOfUsersWithGreaterPoints (1) : 002ms

this ticket was suppose to be in the skills-service project; furthermore research showed that there is no easy solution since the count queries are on a slower side in postgres; after further discussion adding a distributed caching is a long term solution; this ticket is then OBE


[Middleware CRDs] Schema never is the same as in the documentation

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
10.22.0
What version of Traefik are you using?
2.7.1
What did you do?
I have installed the Helm chart as described in the docs. I just used flux for the Helmrelease for GitOps but should be the same.
This is my Helmrelease:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: traefik
  namespace: traefik
spec:
  interval: 5m
  timeout: 30m
  chart:
    spec:
      chart: traefik
      version: "10.22.0"
      sourceRef:
        kind: HelmRepository
        name: traefik
        namespace: flux-system
      interval: 1m
  values:
    image:
      name: traefik # {"$imagepolicy": "flux-system:traefik:name"}
      tag: 2.7.1 # {"$imagepolicy": "flux-system:traefik:tag"}
    logs:
      general:
        level: INFO
      access:
        enabled: true
    ingressRoute:
      dashboard:
        enabled: true
    dashboard:
      enabled: true
      domain: traefik.oblivioncoding.pro
    rbac:
      enabled: true
    api:
      dashboard: true
      insecure: true
    globalArguments:
      - "--global.checknewversion"
    additionalArguments:
      - "--providers.kubernetesingress.ingressclass=traefik"
    #    - "--log.filePath=/var/log/traefik/traefik.log"
    #    - "--accesslog.filepath=/var/log/traefik/access.log"
    global:
      sendAnonymousUsage: false
    pilot:
      enabled: true
      token: "caf24dcf-2370-44cc-8feb-2ec08e69764b"
      dashboard: true
    providers:
      kubernetesCRD:
        enabled: true
        allowCrossNamespace: true
        allowExternalNameServices: true
      kubernetesIngress:
        enabled: true
        allowExternalNameServices: true
    service:
      enabled: true
      type: LoadBalancer
      spec:
        loadBalancerIP: <IP_ADDRESS>
    ingressClass:
      enabled: true
      isDefaultClass: true
    autoscaling:
      enabled: true
      minReplicas: 2
      maxReplicas: 4
    ports:
      websecure:
        tls:
          enabled: true

Now i want to add a middleware:
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: test-header
spec:
  headers:
    customRequestHeaders:
      X-Script-Name: "test"
    customResponseHeaders:
      X-Custom-Response-Header: "value"

It should at my middleware now.
What did you see instead?
But if i apply that deployment i see the following:
error: error validating "ingress.yaml": error validating data: ValidationError(Middleware.spec): unknown field "headers" in us.containo.traefik.v1alpha1.Middleware.spec; if you choose to ignore these errors, turn validation off with --validate=false

What is your environment & configuration?
Kubernetes with talos.dev and YAML with Flux CI
Additional Information
No response

I seem to be experiencing similar behavior that no matter the headers provided. I get the following error message when checking the logs for the traefik-ingress pod:
level=error msg="headers configuration not valid"

I can confirm that using another middleware type (such as replacePath or redirectScheme) seems to work without any problem.

Hello,
Thanks for your interest in Traefik !
This repository is about the Helm Chart of Traefik.
The behavior you describe seems to be an issue with Traefik itself and not the Helm chart.
=> So I invite you to test again on last Traefik version and submit an issue on Traefik repo if it's still there.


[Feature Request] wootility: add a desktop icon

Issue description
It would be nice if the wootility packages provided a .desktop icon.
Steps to reproduce

Import the following in your configuration.nix:{ pkgs, ... }:
{
  environment.systemPackages = [ pkgs.wootility ];
}

Run nixos-rebuild switch
Open up a graphical application launcher and search for Wootility.

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.106, NixOS, 22.11 (Raccoon), 22.11.3689.fda0d99c2cb`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"nixos-22.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

PR submitted that, among other things, adds a desktop-entry file.


deprecation warnings with 3.3.1 plugin and gradle 7.4.x

Using gradle 7.4.2 and liberty gradle plugin 3.3.1, I get a couple of warnings about deprecated properties which are scheduled to be removed in Gradle 8.0, as follows:
The AbstractArchiveTask.archiveName property has been deprecated. This is scheduled to be removed in Gradle 8.0.
Please use the archiveFileName property instead.
See https://docs.gradle.org/7.4.2/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:archiveName
for more details.

and:
The AbstractArchiveTask.baseName property has been deprecated. This is scheduled to be removed in Gradle 8.0.
Please use the archiveBaseName property instead.
See https://docs.gradle.org/7.4.2/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:baseName
for more details.

Closing as duplicate of #620.


Support Amazon RedShift (Currently No such table: information_schema.sequence error on npx prisma db pull)

Bug description
I am attempting to connect a Redshift database to Prisma using the postgresql drivers. I did the setup as outlined here successfully. i followed the database url instructions found here with my credentials matching the following pattern:
postgresql://username:password@abc-12-345-67-890.eu-west-1.redshift.amazonaws.com:1234/databaseName?schema=foo&readOnlyMode=always
i run DEBUG="*" npx prisma db pull and i get the following error:
 prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
Prisma schema loaded from prisma/schema.prisma
  prisma:loadEnv project root found at ./package.json +0ms
  prisma:tryLoadEnv Environment variables loaded from ./.env +0ms
Environment variables loaded from .env
  prisma:getConfig Using CLI Query Engine (Node-API Library) at<EMAIL_ADDRESS>+0ms
Datasource "db": PostgreSQL database "databaseName", schema "foo" at "abc-12-345-67-890.eu-west-1.redshift.amazonaws.com:1234"

Introspecting based on datasource defined in prisma/schema.prisma …
  prisma:introspectionEngine:rpc starting introspection engine with binary<EMAIL_ADDRESS>+0ms
  prisma:introspectionEngine:rpc SENDING RPC CALL {"id":1,"jsonrpc":"2.0","method":"introspect","params":[{"schema":"// This is your Prisma schema file,\n// learn more about it in the docs: https://pris.ly/d/prisma-schema\n\ngenerator client {\n  provider = \"prisma-client-js\"\n}\n\ndatasource db {\n  provider = \"postgresql\"\n  url      = env(\"DATABASE_URL\")\n}\n"}]} +21ms
  prisma:introspectionEngine:rpc {
  prisma:introspectionEngine:rpc   jsonrpc: '2.0',
  prisma:introspectionEngine:rpc   error: {
  prisma:introspectionEngine:rpc     code: 4466,
  prisma:introspectionEngine:rpc     message: 'An error happened. Check the data field for details.',
  prisma:introspectionEngine:rpc     data: {
  prisma:introspectionEngine:rpc       is_panic: false,
  prisma:introspectionEngine:rpc       message: 'Error in connector: Error querying the database: Error querying the database: No such table: information_schema.sequences',
  prisma:introspectionEngine:rpc       backtrace: null
  prisma:introspectionEngine:rpc     }
  prisma:introspectionEngine:rpc   },
  prisma:introspectionEngine:rpc   id: 1
  prisma:introspectionEngine:rpc } +868ms

Error: Error: Error in connector: Error querying the database: Error querying the database: No such table: information_schema.sequences

    at Object.<anonymous> (./node_modules/prisma/build/index.js:46523:29)
    at Object.handleResponse ./node_modules/prisma/build/index.js:46401:38)
    at LineStream4.<anonymous> (./node_modules/prisma/build/index.js:46479:20)
    at LineStream4.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at LineStream4.Readable.push (node:internal/streams/readable:228:10)
    at LineStream4._pushBuffer (./node_modules/prisma/build/index.js:46244:21)
    at LineStream4._transform (./node_modules/prisma/build/index.js:46238:12)
    at LineStream4.Transform._write (node:internal/streams/transform:184:23)

i use the same database url for my current postgres drivers with KnexJS, and would like to migrate to Prisma for it's ability to sync data models with my database.
How to reproduce

have a Redshift database that you can connect to with postgres drivers
initialize Prisma for an existing project
run DEBUG="*" npx prisma db pull
see error

Expected behavior
I expect the initialization to happen without an error.
Prisma information

from .env:
# Environment variables declared in this file are automatically made available to Prisma.

# See the documentation for more detail: https://pris.ly/d/prisma-schema#accessing-environment-variables-from-the-schema

# Prisma supports the native connection string format for PostgreSQL, MySQL, SQLite, SQL Server, MongoDB (Preview) and CockroachDB (Preview).

# See the documentation for all the connection string options: https://pris.ly/d/connection-strings

DATABASE_URL="postgresql://username:password@abc-12-345-67-890.eu-west-1.redshift.amazonaws.com:1234/databaseName?schema=foo&readOnlyMode=always"

from schema.prisma:

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Environment & setup

OS: Windows 10, 64-bit, WSL1 using Ubuntu 18.04
Database: Redshift with Postgresql drivers
Node version: v16.13.2

Prisma Version
Environment variables loaded from .env
prisma                  : 3.9.2
@prisma/client          : Not found
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Default Engines Hash    : bcc2ff906db47790ee902e7bbc76d7ffb1893009
Studio                  : 0.457.0

Introspection depends on some system databases and tables being present, and one of those seems to be missing for Redshift with PostgreSQL. https://docs.aws.amazon.com/redshift/latest/dg/c_redshift-and-postgres-sql.html mentions something in that direction:

Because it addresses very different requirements, the specialized data storage schema and query execution engine that Amazon Redshift uses are completely different from the PostgreSQL implementation.

Can you generally use this PostgreSQL connection string in database UIs like DBeaver or similar?

I can use DBeaver to connect to the Redshift database successfully using the PostgreSQL Binaries from Windows 10. I can also use pg and knex packages to connect to it as well. My stack uses NextJS, TypeScript, and React-Query and using Prisma would make this a lot smoother for keeping sync with the Redshift database.

I'm not a PostgreSQL expert, but I'm asking to maybe solve this issue:

does the ?schema=public always have to be equal to public? for my usage, i have the value analytics to make DBeaver work because that schema contains the tables I an querying against.
do I need to have readOnly=true or readOnlyMode=always to make Prisma read only for Redshift?

Understood. So it seems like Prisma would need to add a new strategy for db pull for Redshift to bypass this behavior difference, right?

Awesome; looks like a good exercise. Do you need anything else from me on this issue to move forward?

No, our next steps now is to a) reproduce the behavior you are seeing and then b) prioritize and implement any necessary changes. No promises and ETA obviously, this is the first time we hear about someone trying to use Prisma with Redshift, so the demand is not super high. On the other hand this is interesting and might be simple to fix.

Although, where you could help: What are the fastest steps to make a new Redshift cluster available to the internet to connect to? Is https://aws.amazon.com/premiumsupport/knowledge-center/redshift-cluster-private-public/ enough? Does it need an Elastic IP connected (which the UI offers, but the steps linked above don't mention)?

Unfortunately I do not know; my account doesn't have those permissions with my company.

Any update on the priority of this feature?

Super low, you are the first and only person asking for support of Amazon RedShift. Many other requests have more people asking for it, and so these will be prioritized unfortunately - but hopefully understandably.
Right now this would mostly be a "side project" for one of our Engineers, fighting through the missing information in RedShift to see if we can get Introspection working. Then we might uncover follow up problems in Migrations or Query Engine.
The biggest practical blocker here is that there is no Docker or other local testing environment available for Redshit that I could find.  That would make it pretty hard to run our tests regularly on a environment that really behaves like Redshift.

@janpio I would be a plus one to this Redshift-support-request!
Since the release of Prisma 1 I'm a huge fan of this ORM for my private projects. Usually I use a PostgreSQL database in the background and everything works like a charm.
Now I would like to introduce Prisma in the tech stack of my company too, but we use Redshift as database in our AWS environment.
Did you come to any known workaround in the meantime to make Prisma compatible with Redshift?

You can try migrating the same schema on a PostgreSQL, then db pull on that and then use the resulting Prisma Schema with your Redshift instance. That would let you skip the problem above (the missing table is not used when just using Prisma Client) - but of course there might be other, unknown problems waiting for you there.

wanted to comment to follow up and see if this is any traction
already use Prisma everywhere else and have a use case in q4 that could definitely benefit from this having db pull work with Redshift, happy to experiment if you need data as well.
also wanted to see if any one has had any luck going the manual schema route, and just using the client?

@wildky I ended up not using Prisma for this; I used Knex. I created a script to introspect the Redshift schema and translate all the table definitions that I needed into TypeScript interfaces, and then fed them into Knex on the server. It worked pretty well :)

@wildky I ended up not using Prisma for this; I used Knex. I created a script to introspect the Redshift schema and translate all the table definitions that I needed into TypeScript interfaces, and then fed them into Knex on the server. It worked pretty well :)

I also ended up using knex! I was mainly doing big complicated data queries with redshift for this project so Prisma lost a lot of its value quickly anyway.

Is there any updates regarding this?

None we are aware of. Last time we checked, RedShift was not emulating this standard PostgreSQL database table that we require on db pull.

+1 for redshift integration from me!

+1 for Redshift integration


Add Joom

Data

name: Joom
url: https://www.joom.com/en/privacy
difficulty: easy
notes: Login to your account, scroll down to the bottom of the privacy policy and click delete account. Confirm the deletion dialog. OPTIONAL Enter an email address to be notified of when deletion completes.
domains: www.joom.com

Thanks for the suggestion!


[Bug]: Deletion of data sources is blocked if any one deletion is busy

Is there an existing issue for this?

[X] I have searched the existing issues

Description
deleting a datasource is already slow and fraught with problems (https://github.com/appsmithorg/appsmith/issues/16866), but this issue becomes more prominent because of the slowness: When I attempt to delete a datasource, the delete button for that datasource acquires a busy indicator - this is ok.
BUT while the delete is processing, I am not able to delete any other datasource - when I try to do that, I see the busy indicator on all other datasources as well.
Steps To Reproduce
https://user-images.githubusercontent.com/94514895/195765285-27b79563-ff93-41d9-b769-5ecc8ab360c4.mov
Public Sample App
No response
Version
Cloud

Since this problem claims that individual datasources can be removed concurrently, we are unable to test it using Cypress since we must first interact with the elements, and by the time we do, the deletion apis may or may not have finished. Therefore, the test cases won't always be accurate. The test case for this use case was therefore determined to be skipped by @Aishwarya-U-R  and @AmanAgarwal041 . cc - @rohan-arthur


Should .gitignore ignore everything ?

It looks like an amazing idea to get nothing done. But I wonder what should be the .gignore behaviour ?
Should it ignore everything including .gitignore or ignore nothing

would be better ignore this doubt once that nothing will be there to ignore.


No support for wallet standard?

Describe the bug
Am on Svelte and was hoping to use this project, but it looks like https://solana-svelte-counter.netlify.app/ doesn't work with all Solana wallets.

To Reproduce
Visit https://solana-svelte-counter.netlify.app/ and connect a wallet
Expected behavior
I expected something like https://solana-labs.github.io/wallet-adapter/example/:

Hah have already started working on this! See https://github.com/solana-labs/wallet-adapter/issues/788#issuecomment-1590296678
@cogoo I ended up forking svelte-on-solana as I needed to fix a couple of things - npm, using prettier defaults, showing installed wallets first, etc. I'm adding wallet standard right now.

@mikemaccana @silvestrevivo @cogoo
will this repo ever be revived?
or we should just use forks?
https://github.com/portalpayments/svelte-on-solana-wallet-adapter
https://github.com/aztemi/svelte-on-solana-wallet-adapter
Which to use now?
Why not add these chads a members of this org?
How has such important repo gone silent?
why is no one fighting for this?

Hello, trying to connect wallet on my sveltekit app, any progress for this project?


Update(Mutation) returns Unauthorized even though IAM AuthPolicy is specified

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.3
Amplify CLI Version
7.6.8
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, api
Amplify Commands
codegen, update
Describe the bug
I added it with amplify add api (AppSync).
Initially I was using UserPool for login authentication, but I am trying to change to IAM authentication because I need guest login.
I'm also allowing guests with the amplify update api.
The UserPool authentication is working perfectly.
However, when I login with IAM authentication, only the Mutation update function is not available due to an authentication error, even though it is specified in AuthPolicy.
I am able to get it with the get function.
The changes to DynamoDB are returned in a Response like the one below.
The policy is auto-generated by schema, so I think the mutation permissions are set correctly.
Is there any possible cause for this?
Do I need to add the policy somewhere else?
Is there any way to verify that the authorization is set from local?
Is there something wrong with the code?
(It's also strange that two AuthPolicies were generated, 01 and 02, even though they were generated automatically.)
Expected behavior
When I try to change DyanamoDB, it becomes Unauthorized.
Response(catch error)
{
  "data": {
    "updateUsers": null
  },
  "errors": [
    {
      "path": [
        "updateUsers"
      ],
      "data": null,
      "errorType": "Unauthorized",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "Not Authorized to access updateUsers on type Mutation"
    }
  ]
}

Reproduction steps
main.ts(ionic - amplify.js)
//  "aws_appsync_authenticationType": "AMAZON_COGNITO_USER_POOLS",
Amplify.configure({ ...awsconfig,});

↓
Amplify.configure({ ...awsconfig,
  aws_appsync_authenticationType: 'AWS_IAM',
});

GraphQL schema(s)

# Put schemas below this line

type Users @model
@auth(rules: [
  { allow: owner, ownerField: "id" }
  { allow: groups, groups: ["employee"] }
  { allow: private, provider: iam }
]) {
  id: ID!
  data1: String
  data2: String
  data3: String
}

Log output

# Put your logs below this line

Additional information

@shichi18 Can you clarify the below.

when I login with IAM authentication, only the Mutation update function is not available due to an authentication error, even though it is specified in AuthPolicy

Do you mean createUsers is working but not the updateUsers?
Can you share what the AuthPolicy looks like?
Is the user id you are using to test the access authenticated by Auth (Cognito UserPool)?

@sundersc

Do you mean createUsers is working but not the updateUsers?

Only updateUsers.
I don't think the other Table updates are working either.
Create, delete, and read are working.

Can you share what the AuthPolicy looks like?

I'm sorry. It's not possible to share in detail, but these was all generated and updated with amplify commands.
All have @model in GraphQL.

Is the user id you are using to test the access authenticated by Auth (Cognito UserPool)?

It is certified.
I've also done things like creating Cognito from code, and it works.
I can't do Update from Appsync.
By the way,
In the beginning, I was using Amplify.configure only at the beginning of main.ts, but I would like to switch Amplify.configure between IAM and User Pool at the time of login and logout, Is it possible to do this?

Having the same problem with Groups in Amplify Mock Api
createUser works, however, when I try to updateUser I get: <Unauthorized on [id, firstName]>
I have fieldLevel auth in place to allow groups "Admin".  Problem occurs when Auth options Groups are set to "Admin"
I am running the newest 7.6.10 version of CLI
Not sure if the same problem occurs when pushed to cloud.
Anyone else experiencing the same?

Moving this to pending-triage .

I can't do Update from Appsync.

It may not work from AppSync because of the way IAM private rule work in v2. Have you tried using library? I've tested in a sample app, I'm unable to reproduce it.

@madahatter - Your issue might be caused by a different reason. Can you open a new issue and include your schema?

@shichi18 - Have you tried this option to use iam auth from AppSync console?
https://docs.amplify.aws/cli/graphql/authorization-rules/#use-iam-authorization-within-the-appsync-console

@sundersc thank you for the response!  Much appreciated.
I opened a new thread with my issue here:
https://github.com/aws-amplify/amplify-cli/issues/9635

@sundersc
Thank you!

Have you tried this option to use iam auth from AppSync console?
https://docs.amplify.aws/cli/graphql/authorization-rules/#use-iam-authorization-within-the-appsync-console

As a result, I didn't think this was the cause of the problem.
However, I was able to reproduce the phenomenon, so I will describe it below.
Here's how to reproduce it.
In my project, I have "customer" and "employee" groupe in Cognito.
I had added both or one of them to a group in my account.
I deactivated it once to avoid belonging to a group to try to solve the problem.
Then it worked as expected!
Then I added one or both of the groups again and restarted the application, and the "update" that caused the problem did not work. (It may be that other things are also not working, but in my case, "update" was the only thing that did not work.)
By the way, I manually added the policy to the group with both roles generated by Auth.
I don't know if you can reproduce this on your end, but I think this may be a bug.
Or is this the expected behavior?
Here is the final Auth configuration
type Users @model
@auth(rules: [
  { allow: private, provider: iam, operations: [create, update, read] }
  { allow: owner, ownerField: "id" }
  { allow: groups, groups: ["employee"] }
  { allow: groups, groups: ["customer"] }
]) {
...
}

@shichi18 - Thanks for the updates. I was able to reproduce it, marking it as bug.
Here are the steps I've followed to reproduce the issue:

Add an api amplify add api with Cognito (default) and IAM auth modes.
Update auth amplify update auth and add user pool groups.
Push the resources to the cloud amplify push.
Create a user, login and check update mutation (using IAM auth) in JS app, it works as expected.
Add user to a group, login and check update mutation (using IAM auth) in JS app, now it throws 401 - Unauthorized error. (Expected result: Update should work similar to Step 4).

Schema
type Users @model
@auth(rules: [
  { allow: owner, ownerField: "id" }
  { allow: groups, groups: ["employee"] }
  { allow: private, provider: iam }
  { allow: public, provider: iam }
]) {
  id: ID!
  data1: String
  data2: String
  data3: String
}

@shichi18 - Couple of things going wrong here,

IAM policy for the role used by the user pool group. (Roles attached to user pool groups don't have access to call AppSync service)
Error in resolver code. (Correction required to IAM private rule logic)

IAM policy for the role used by the user pool group
What I have done to resolve this is to take the policy attached to authRole and add it to the user pool group's role.
Error in resolver code
On Mutation.updateUsers.auth.1.res.vtl, replace
#if( $ctx.identity.userArn == $ctx.stash.authRole )

with this
#if( ($ctx.identity.userArn == $ctx.stash.authRole) || ($ctx.identity.cognitoIdentityPoolId == "COGNITO ID HERE" && $ctx.identity.cognitoIdentityAuthType == "authenticated") )

You can also see this statement in Subscription.onUpdateUsers.auth.1.req.vtl for correct logic. Also, you can override the resolver so that the changes doesn't get lost on subsequent push.
https://docs.amplify.aws/cli/graphql/custom-business-logic/#override-amplify-generated-resolvers
We are working on the fix.

I think a couple things need to happen here:
Ideally, what should happens is: we push all authorization logic into the resolver instead of having it be defined in the IAM role.
If that's not possible a another solution could be:
if a static group auth rule is specified, for example @auth(rules: [{ allow: group, groupName: “Admins”, operations: [create, read, update]}])
then on amplify push, the CLI should check if the group already exists.
-> Does the group exists?
->No - create the user pool group, and then update its IAM policies.
->Yes - update IAM policies to match operations
A few edge cases we should handle:

What if someone removes a group from an auth rule. We shouldn't remove the group itself but rather only its access.
How does this work with Amplify Studio, which creates user pool groups using SDK calls instead CloudFormation?
What if a user pool group was created via the Admins Actions API https://docs.amplify.aws/cli/auth/admin/ ? Will it be compatible?
What if a customer imports an existing user pool via amplify import auth?


fix: Local storage now cleanly initializes

LGTM.  On page load with an empty IndexedDB, the appropriate data is set in localStorage to display all dashboards.  Code looks good too.


PHPUnit 10 Shift

This pull request contains changes for upgrading to PHPUnit 10 automated by the PHPUnit 10 Shift.
Before merging, you need to:

Checkout the shift-120659 branch
Review all pull request comments for additional changes
Run composer update (if the scripts fail, try with --no-scripts)
Run your tests suite: vendor/bin/phpunit

If there were changes you felt could have been automated, please reply to the follow-up email with your feedback or on Twitter.

:warning: PHPUnit 10 has made several changes to the configuration file. After running composer update, you may run vendor/bin/phpunit --migrate-configuration to have PHPUnit upgrade your configuration file.

:warning: PHPUnit 10 now requires any base test class to have a TestCase suffix. In addition, this class should be defined as abstract. If you have a custom base test class, you should ensure it meets these new requirements.

:information_source: PHPUnit has documented declaring test classes as final since PHPUnit 8. In an effort to modernize your test suite, Shift has declared your test classes as final.
Shift understands developers have different preferences when it comes to using final. If you do not wish to declare your test classes as final, you may undo this change by running: git revert 62cb448d

:alembic: This Shift is still being refined. Please report any issues or suggestions to<EMAIL_ADDRESS>Your feedback is what helps improve the experience for everyone.


Publish as AppX package and add to Microsoft Store

Many Windows apps get distributed over the Microsoft Store - Window's App Store. This store allows users to more easily and more securely installs applications. Additionally, some versions of Windows - like Windows 10 S - don't even give the user the ability to run normal .exe apps anymore.
ElectronJS has published a guide on how we can get Ferdi onto the Microsoft Store: https://www.electronjs.org/docs/tutorial/windows-store-guide
This would require us to use the electron-windows-store to package our Windows build to the AppX format. We would also need to create a Microsoft Developer Account which costs a one-time fee of $19.
This would also be a solution to #112

Adding this via https://github.com/getferdi/ferdi/tree/feat/appx - we would require #415 to test this setup though.

@vantezzen Do we need electron-windows-store in the end? I think your branch re-use electron-builder right? Also, we should be careful to still keep auto-update available for NSIS. Let me know if I should go ahead and get the developer account or if you planned on doing it 🙏

Yes, I noticed that electeon-builder has AppX supper build-in so we don't need the extra package.
I used electrons process.windowsstore to disable updates, which should only be true if we are coming from the store.
I'll test AppX on our Windows VM and only after that I'll need the dev account - I'll notify you so you can set that up.


application did not be traced

What version of pinpoint are you using?
pinpoint1.6.2
Describe your problem
when I start agent correctly,there is nothing shows in web UI. but I had send request locally
What have you done?
Steps you have taken to trigger the problem, for example:

start agent with 1.6.2
send a request from chrom .call my local service
nothing shows in web UI
4.my application is springboot project.but it is shown with image below.is there any configuration i should set?

Screenshots

Logs
If applicable, please attach agent/collector/web DEBUG log that includes the part where you have
no error log

@yale2
Take a look at our FAQ on this.


Bug: Getting bad request after clicking on approve button for protect approval.

📜 Description
Getting below error while trying to save the approve button from mail subject for config approval.

Logs of orchestrator
{"level":"error","ts":1716793656.4566267,"caller":"drafts/ConfigDraftService.go:267","msg":"user contributed to this draft","draftId":11,"userId":509,"stacktrace":"github.com/devtron-labs/devtron/enterprise/pkg/drafts.(*ConfigDraftServiceImpl).validateDraftAction\n\t/go/src/github.com/devtron-labs/devtron/enterprise/pkg/drafts/ConfigDraftService.go:267\ngithub.com/devtron-labs/devtron/enterprise/pkg/drafts.(*ConfigDraftServiceImpl).ApproveDraft\n\t/go/src/github.com/devtron-labs/devtron/enterprise/pkg/drafts/ConfigDraftService.go:410\ngithub.com/devtron-labs/devtron/enterprise/api/drafts.(*ConfigDraftRestHandlerImpl).CheckAccessAndApproveDraft\n\t/go/src/github.com/devtron-labs/devtron/enterprise/api/drafts/ConfigDraftRestHandler.go:410\ngithub.com/devtron-labs/devtron/api/restHandler.NotificationRestHandlerImpl.ApproveConfigDraftForNotification\n\t/go/src/github.com/devtron-labs/devtron/api/restHandler/NotificationRestHandler.go:1180\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2122\ngo.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux.traceware.ServeHTTP\n\t/go/src/github.com/devtron-labs/devtron/vendor/go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux/mux.go:179\ngithub.c
requestMethod: POST, urlPath: /orchestrator/notification/channel/config/approve, queryParams: , updatedBy: , updatedOn: 2024-05-27 07:07:36.444772468 +0000 UTC m=+333898.273793262, apiResponseCode: 400, requestPayload:
Affected areas
CD
Additional affected areas
Other CRITICAL functionality
Prod/Non-prod environments?
Prod
Is User unblocked?
Yes
How was the user un-blocked?
TEMPORARILY - By disabling a CRITICAL functionality
Impact on Enterprise
Currently We need to apply protect configuration for all the prod applications , before that I was testing end to end and getting this error due to this client is not able to use this feature.
👟 Steps to replicate the Issue

Apply the protect configuration for an env for an Devtron application .
Use SES to get the mail for protect configuration.
Try to click on approve button from mail.

👍 Expected behavior
It should approved .
👎 Actual Behavior
Currently It through bad request .
☸ Kubernetes version
1.25
Cloud provider

AWS

🌍 Browser
Chrome
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#9853

In this case, when a user requests configuration approval and then tries to approve it themselves, we are displaying an appropriate message from the API. However, this message is not handled properly by the UI. Product intervention is needed to display the correct message in the UI. @uxarya-d @abhibhaw

If the API throws an error, by default UI shows a toast with error details I believe cc: @vivek-devtron ?

@abhibhaw This is via Email approval flow. Currently I believe "Something went wrong" is generic handling for any error state. While approving from the dashboard we have proper messaging. We'll do the same in email approval flow as well.


Configurable Delegation Limits

Node enhancement to give validators the ability to configure a minimum and maximum delegation amount which would then be enforced for their delegators.
Please find the detailed proposal in the CEP request here

Dev to check and update in L1 daily.


Disqus does not seem to be working on Github pages

hugo version: Hugo Static Site Generator v0.53/extended darwin/amd64 BuildDate: unknown
config.toml:
baseURL = "/"
languageCode = "en"
title = "fberrez.com"
theme = "cactus-plus"
googleAnalytics = ""

# Set the value to true if your site include CJK (Chinese, Japanese, and Korean languages) characters
hasCJKLanguage = false

[params]
        [...]
	enableDisqus = true
	disqusShortname = "fberrez"
[...]

What?
Disqus cannot be loaded on a github pages website. It returns the error We were unable to load Disqus. If you are a moderator please see our [troubleshooting guide](https://help.disqus.com/troubleshooting/im-receiving-the-message-we-were-unable-to-load-disqus)..
It does not help to read the troubleshooting guide. See my Disqus config below:

My config was not correct. Sorry for this useless issue.


Local planner

Motivation and Context
The current greedy follower wasn't designed in a world were sliding was disabled and action noise existed, so it isn't great in those situations.  This PR switches it out for a local motion primitive planner that does a considerably better job and also sets things up for action noise (by allowing the user to specify what key should be emitted for each action to take as the planner needs to plan on noiseless actions).
Compared to the old one, there is a bump of ~0.02 SPL when sliding is enabled.  When sliding is disabled however, SPL is increased from ~0.85 (with a ~12% failure rate) to ~0.95 (with a ~2% failure rate), which is much better.
How Has This Been Tested
Via the tests!
Types of changes

New feature (non-breaking change which adds functionality)

For thrashing, it occurs when you enter a loop of left->right->left->right->left->right....  the way to get out of that is to take the best primitive and execute it fully instead of executing the first action and re-planning.
For the situation you described (no action better than just colliding), that results in an error (the cpp code returns an ERROR token and python then throws an error).

As a side note, I haven't seen a case where this thing actually thrashes.  I am not sure if you actually need that logic since we have access to the ground truth navmesh to plan on, but its simple enough to have it :)

@aclegg3 Can you double check esp::core::RigidState

@aclegg3 Can you double check esp::core::RigidState

Looks good. Thanks!

The current greedy follower wasn't designed in a world were sliding was disabled and action noise existed, so it isn't great in those situations. This PR switches it out for a local motion primitive planner that does a considerably better job and also sets things up for action noise (by allowing the user to specify what key should be emitted for each action to take as the planner needs to plan on noiseless actions).
Compared to the old one, there is a bump of ~0.02 SPL when sliding is enabled. When sliding is disabled however, SPL is increased from ~0.85 (with a ~12% failure rate) to ~0.95 (with a ~2% failure rate), which is much better.


adjust to new loading of dynamic key adding to libp2p-crypto

Depends on https://github.com/libp2p/js-libp2p-crypto/pull/74

@yusefnapora @diasdavid please review this

Sounds like a better approach to DI then the circular dep it had.
Have you confirmed that you can browserify and webpack libp2p-ipfs-browser without having any hurdles?

It works fine with libp2p-crypto, but haven't tested it as a dependency for libp2p-ipfs-browser

out of date


Adds danger job and install-rubydocker-dependencies command

Adds Danger job and install-rubydocker-dependencies command

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/revenuecat/sdks-common-config?version=dev:acce9cdca8d6a1a5a7bd9177038a6ec835ba4316

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/revenuecat/sdks-common-config?version=dev:03dcf77317a473616cc6ad417206af412a9cbc2d

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/revenuecat/sdks-common-config?version=dev:03dcf77317a473616cc6ad417206af412a9cbc2d

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/revenuecat/sdks-common-config?version=1.1.0


ping 404 response

when go build on different directory ,  custom directory have a error
ip=<IP_ADDRESS>:52250 latency=73.828µs method=GET status=404 url=/api/v1/p
ing

but in src/github.com/anthonynsimon/parrot/parrot-api is worked.

That's because the API which is written in Go, is located at the parrot-api directory. You should built on the right directory, src/github.com/anthonynsimon/parrot/parrot-api. Additionally, you might want to take a look at the build scripts that are included, for any additional build steps that you might require.