Changes behaviors of OnRequest, uses []byte instead of string in a couple places

This PR changes how hooks work slightly; they now take a HTTPRequestMeta object as their parameter which has a bunch more information on it.

lgtm


Script error in IE9

Hi all,
Simple script
var renderer = new PIXI.CanvasRenderer(700, 550);

give me a lot of error repeating :
SCRIPT16389: Erreur non spécifiée. (unspecified error)
pixi_test.html, Ligne 1 Caractère 1
Also, i cannot make my game works on IE9 with the new pixi v3 version...
Another code :
var renderer = new PIXI.WebGLRenderer(700, 550,{transparent:true});
var stage = new PIXI.Container();
$(renderer.view).appendTo("body");

Give me :
SCRIPT5009: « ArrayBuffer » est indéfini (is not defined)
pixi_test.html, Ligne 12 Caractère 1
Any idea ?

IE9 doesn't support WebGL, so creating a WebGLRenderer will never work there. However, We have tested the canvas renderer on IE9 quite a bit, and have even shipped a thing or two.
Can you show me a running example of something that breaks for you? Everything I have runs fine on IE9 (using canvas).

I have trying severals things...but i have always some problems. Now problem seems to come from the loader. Theses bugs come only on IE9 and not other IE, chrome, firefox safari or mobile device
var load0 = PIXI.loader;
load0.add('essai',"essai.json");
load0.once('complete',onas0);
load0.load();

function onas0()
{
   var mov=[];
   for (var j=0;j<8;j++)
	mov.push(PIXI.Texture.fromFrame(""+j));

The essai.json file
{"frames": {
"0":
{
"frame": {"x":0,"y":0,"w":37,"h":41},
"rotated": false,
"trimmed": false,
"spriteSourceSize": {"x":0,"y":0,"w":37,"h":41},
"sourceSize": {"w":37,"h":41},
"pivot": {"x":0.5,"y":0.5}
},
"1":
...

Give error : SCRIPT5022: The frameId "0" does not exist in the texture cache

Are you 100% sure you are using v3.0.3? There were some IE9 bugs in the loader fixed in that version.

I have tried with pixi.min  and pixi.js version 3.0.3 :
Journal : Pixi.js 3.0.3 - Canvas - http://www.pixijs.com/
Journal : la
Journal : ici
SCRIPT5022: The frameId "0" does not exist in the texture cache
pixi_test.html, Ligne 548 Caractère 3

On another script i have tested on IE9, it seems the complete event is never fired. I think there's severals problems with IE9 and pixi 3, with pixi 2 i haven't these problem with the same script (adapted to pixi 2)

Can you give me a running example so I can debug it?

This should be working in latest versions of pixi, if not please opena  new issue with a running test case for debugging.

Hi, i’m sorry because i’m very busy in this time, i try quickly 3.0.5 and YES ! This works now :-)
Thank you

Le 15 mai 2015 à 17:44, Chad Engler<EMAIL_ADDRESS>a écrit :
This should be working in latest versions of pixi, if not please opena new issue with a running test case for debugging.
—
Reply to this email directly or view it on GitHub https://github.com/GoodBoyDigital/pixi.js/issues/1771#issuecomment-102440730.


Upon failure, an error message is displayed (“wrong username or password”)

closed by https://github.com/sopra-fs22-group-10/server/commit/253aefa4dc6ff59fd8734ecd20e6c8fb0b1f071c


Clarification Needed on Valid Identifiers in Policies

Before opening, please confirm:

[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.

Bug Category
Schemas and Validation
Describe the bug
I have been encountering errors of this type when setting up AVP w/ Cedar to perform route-based API authorization:
identifier `get /foo` contains characters that fall outside of the General Security Profile for Identifiers

API route identifiers of the flavor get /foo seem to violate constraints Cedar is expecting, but are used in documentation such as this:
https://aws.amazon.com/blogs/security/authorize-api-gateway-apis-using-amazon-verified-permissions-and-amazon-cognito/
I have also encountered this issue in the console when using the automated 'Set up with API Gateway and an identity provider' starting action.
Expected behavior
According to the documentation, API routes of the format get /foo should be valid actions.
Reproduction steps

Create an API Gateway with a get /foo endpoint.
Create AVP request authorizer and attach to API.
Attempt to create a simple policy such as:

permit (
  principal in {{NAMESPACE}}::UserGroup::"{{USER_POOL_ID}}|{{USER_GROUP_NAME}}",
  action in
  [
    {{NAMESPACE}}::Action::"get /foo"
  ],
  resource
);

Log output
Warning:   ⚠ for policy `policy0`, identifier `get /foo` contains characters that fall outside of the General Security Profile for Identifiers

Additional configuration
No response
Operating  System
No response
Additional information and screenshots
No response

Currently, the / character triggers this warning, but should not: #621

Hi @cdisselkoen - just to clarify, I see this as a warning in the Cedar CLI, but it actually blocks the creation of policies in the Cedar AWS console. It lists the same error as being a validation warning, but you are blocked from actually creating the policy. The Chrome console states that it is running against Cedar 3.3.0.

Understood, but this is a problem in the Verified Permissions service or console, not in Cedar.  Cedar reports it as a warning and not an error, as you say.  So even though Cedar could improve by not reporting a warning at all in this case (#621), the behavior of blocking policy creation is somewhere in Verified Permissions code.

You can use the "feedback" button in the footer of the console.  If you have an AWS support contract or account manager, I recommend going through them instead / as well.  If you're internal to AWS, ping me internally (@cdiss) and I'll give you internal details on how to report.

Closing this, feel free to open a new issue if needed.

FYI, we've merged a fix to substantially limit when we emit this warning on the Cedar side in #1336. AVP console should pick up this change eventually, but I don't have timeline.


Help with complex nested form and validations

Sorry for posting so many issues/questions, but I recently discovered your excellent gem and am hoping it can help me replace my own similar (but less sophisticated implementation).
With basic objects, all of this is pretty easy. But I have the following complex scenario:
I am building a shopping cart with Products. A Products has many Variants, which are its children, making the product a parent.
Now a Product can have feature combinations like: Color=Red, Size=Small
This Product's Variants require:
A) Must have feature keys (i.e. Color, Size) that the parent has
B) The feature key/value combinations must be different from the parent. So in this case, the variant can't have Color=Red, Size=Small. But Color=Blue, Size=Large is ok.
C) The feature key/value combinations must also be different from other Variants (i.e. siblings)
My current implementation uses custom validation mappings across a series of service objects that I roll up into a larger service object that tries to manage and delegate all of these concerns.
My hope is that reform can replace a lot of this for me, but I'm confused on how to include nested validations for my case.
PS: I'm also using the lotus validations because I hope to be able to flatten the nested errors.
I can provide more detail if you like, but would first like to know if this is something you can help me get a handle on. Thanks.

You can nest forms, e.g.
class ProductForm < Reform::Form
  collection :variants do
    property :size
  end

  validate do
    variants.each do |v|
      v.size == "Small" or errors.add("so", "wrong")
    end
  end
end

product.variants #=> [<Variant size="Small">, ...]
form = ProductForm.new(product)
form.variants[0].size #=> "Small"

A nested form is simply an object graph with Ruby API and you can use it for complex validations, etc. I recommend reading the Nested Forms and Mastering Forms chapters of the Trailblazer book, they discuss this!

The #validate method is what I needed! This is great, thank you!


Bug: Terraform Init Fails Due to Azure Storage Account Network Configuration in Landing Zone Deployment

The deployment of the Azure Landing Zone consistently fails during the Terraform initialization (terraform init) stage. The deployment only succeeds when I manually alter the Azure Storage Account’s network configuration. Specifically, I need to change the network access setting from its default (restricted access) to "Enabled from all networks" in the Azure Portal.
Steps to Reproduce:

Deploy the Azure Landing Zone.
During the Terraform initialization stage, the deployment fails.
Manually adjust the Storage Account settings:

Go to Azure Portal ->
Storage Accounts ->
Select the relevant account ->
Networking ->
Set network access to "Enabled from all networks."

Retry the deployment, which then succeeds

Encountered a 403 Authorization Failure when attempting to initialize Terraform with Azure.
Error: Failed to get existing workspaces: containers.Client#ListBlobs: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailure" Message="This request is not authorized to perform this operation.\nRequestId:XXXX\nTime:2024-08-26T01:37:53.6259929Z"
Please investigate why the default network configuration is causing the deployment to fail and recommend a solution that doesn't require manual intervention.

@ifeanyindukwe  We would need to understand your inputs to investigate this. Are you using the local option?

Hi Jaredfholgate,
I am using Azure Pipeline Agent Pools in Azure DevOps, and I've set my azure_devops_personal_access_token to token-1 in my inputs.yaml file. However, I'm not quite sure I understand what you mean by the 'local option.' Could you please provide more details or clarify if my response is not addressing your question?
Ifeanyi Ndukwe
Data Engineer

From: Jared Holgate @.>
Sent: 04 September 2024 01:21
To: Azure/ALZ-PowerShell-Module @.>
Cc: Ifeanyi Ndukwe @.>; Mention @.>
Subject: Re: [Azure/ALZ-PowerShell-Module] Bug: Terraform Init Fails Due to Azure Storage Account Network Configuration in Landing Zone Deployment (Issue #151)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@ifeanyindukwehttps://github.com/ifeanyindukwe We would need to understand your inputs to investigate this. Are you using the local option?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/ALZ-PowerShell-Module/issues/151#issuecomment-2326512052, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKFHBEISHP4PCRWFZTJBGQTZUWZUBAVCNFSM6AAAAABNQRDZ52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRWGUYTEMBVGI.
You are receiving this because you were mentioned.Message ID: @.***>

@ifeanyindukwe We would need to understand your inputs to investigate this. Are you using the local option?

Please find attached my input.yaml file. Identifiable information such as subscription IDs, emails, and generated tokens have been masked with "XXXX" for privacy reasons.

Thanks for this info. I see you are using Microsoft-hosted agents use_self_hosted_agents: "false" and have use_private_networking: "true". This combination is not possible and should be handled by the code, it should be ignoring the use_private_networking option. So it looks like you may have uncovered a bug here, that we'll investigate. In the meantime, setting use_private_networking: "false" should hopefully fix it for you.

A fix has been released now in v3.0.2 of the bootstrap modules.

I have successfully set use_private_networking: false as you suggested, and it resolved the issue. However, I had to first destroy the ALZ that was already deployed and then remove the bootstrap environment from Azure DevOps. Is there an alternate way to update through Azure DevOps settings without having to destroy and redeploy it entirely and rerun the bootstrap from scratch?

I have successfully set use_private_networking: false as you suggested, and it resolved the issue. However, I had to first destroy the ALZ that was already deployed and then remove the bootstrap environment from Azure DevOps. Is there an alternate way to update through Azure DevOps settings without having to destroy and redeploy it entirely and rerun the bootstrap from scratch?

I'm not sure why you had to destroy it, you should have been able to update it in place? The bootstrap stores a state file that it uses to plan for just the changes. Did you delete the output folder?

I was using a different device and initially thought that the bootstrap was a one-time process to orchestrate the initial resources in Azure and Azure DevOps. I assumed that after the initial setup, it wouldn’t be needed again. It’s interesting to learn that the bootstrap stores the state file, which allows for in-place updates rather than requiring a full redeployment. I’ll definitely keep this in mind moving forward.
However, when migrating from v3.0.1 to v3.0.2, I encountered the following error:
I executed the command:
Deploy-Accelerator -inputs "c:\accelerator\config\inputs.yaml" -output "c:\accelerator\output"

and accepted all the prompts with Y to proceed with the migration from v3.0.1 to v3.0.2.
The error I received is as follows:
Error: Update repository file failed, repositoryID: XXXX, branch: refs/heads/main, file: .pipelines/cd.yaml . Error: TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.
│
│   with module.azure_devops.azuredevops_git_repository_file.alz[".pipelines/cd.yaml"],
│   on ..\..\modules\azure_devops\repository_module.tf line 11, in resource "azuredevops_git_repository_file" "alz":
│   11: resource "azuredevops_git_repository_file" "alz" {

Could you please advise on how to resolve this issue?

I was using a different device and initially thought that the bootstrap was a one-time process to orchestrate the initial resources in Azure and Azure DevOps. I assumed that after the initial setup, it wouldn’t be needed again. It’s interesting to learn that the bootstrap stores the state file, which allows for in-place updates rather than requiring a full redeployment. I’ll definitely keep this in mind moving forward.
However, when migrating from v3.0.1 to v3.0.2, I encountered the following error:
I executed the command:
Deploy-Accelerator -inputs "c:\accelerator\config\inputs.yaml" -output "c:\accelerator\output"

and accepted all the prompts with Y to proceed with the migration from v3.0.1 to v3.0.2.
The error I received is as follows:
Error: Update repository file failed, repositoryID: XXXX, branch: refs/heads/main, file: .pipelines/cd.yaml . Error: TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch.
│
│   with module.azure_devops.azuredevops_git_repository_file.alz[".pipelines/cd.yaml"],
│   on ..\..\modules\azure_devops\repository_module.tf line 11, in resource "azuredevops_git_repository_file" "alz":
│   11: resource "azuredevops_git_repository_file" "alz" {

Could you please advise on how to resolve this issue?

This is a known issue that I plan to take another look at, in the meantime you can just manually turn off branch protection or turn it off in the inputs: https://github.com/Azure/ALZ-PowerShell-Module/issues/136

Thank you @jaredfholgate and to everyone involved for the support and valuable feedback! The issue was resolved after following the suggestions provided by the team. I successfully migrated from v3.0.1 to v3.0.2 by temporarily turning off branch protection and rerunning the deployment. Everything functions as expected, and I'm excited to continue using the accelerator.
I appreciate the quick response and look forward to any future improvements. Thanks again for the assistance!


[Bug]: Broken link in README.md for Dockerfiles example

💻

[ ] Would you like to work on a fix?

Current behavior
Broken link here https://github.com/PrefectHQ/prefect-recipes/blob/main/README.md#dockerfiles
It's redirecting on 404 page
Expected behavior
Link should works or that list item should be deleted
Possible solution
No response
Additional context
No response

Hi @Creep-ai -- sorry about this!
We removed this dead link last week in #213
Let us know if you'd like to see a specific dockerfile related recipe


CI setup on OLCF Crusher

I have been trying to run a cron driven CI setup for psi-j on OLCF Crusher. Looking at the logs, there seems to be a few problems. First, as indicated on the comments, I added a module load statement in the psij-ci-load file. However, I am seeing in the testing.log that the module command is throwing error: psij-ci-load: line 5: module: command not found.
Next, I am seeing that the setup is trying to ssh into localhost and failing because it requires MFA:
DEBUG Output from ['ssh', '-oBatchMode=yes', '-oStrictHostKeyChecking=no', 'localhost', 'true']
Which leads to a credential prompt and error:
ketan2@localhost: Permission denied (publickey,keyboard-interactive,hostbased).
I am seeing more errors further down on tests for slurm but unable to find the cause and suspect that these above issues might be the reason for those.

Thanks Ketan.

I have been trying to run a cron driven CI setup for psi-j on OLCF Crusher. Looking at the logs, there seems to be a few problems. First, as indicated on the comments, I added a module load statement in the psij-ci-load file. However, I am seeing in the testing.log that the module command is throwing error: psij-ci-load: line 5: module: command not found.

I'm a bit confused here. What comments are you referring to? Do you need to load a module in order for tests to work? Is the module system installed on crusher?

Next, I am seeing that the setup is trying to ssh into localhost and failing because it requires MFA: DEBUG Output from ['ssh', '-oBatchMode=yes', '-oStrictHostKeyChecking=no', 'localhost', 'true']

One test does need SSH, so the setup tries to run that in order to add the site key. We could probably add a timeout to that part.

Which leads to a credential prompt and error: ketan2@localhost: Permission denied (publickey,keyboard-interactive,hostbased).
I am seeing more errors further down on tests for slurm but unable to find the cause and suspect that these above issues might be the reason for those.

Possibly, but we can't tell without more information. Perhaps paste some of those errors here.

By comments, I am referring to the ones in the psij-ci-load file:
$ cat psij-ci-load
# This file can be used to set up an environment before tests are run.
# For example, one can issue relevant "module load" commands here. The
# file will then be sourced by both psij-ci-setup and psij-ci-run.

module load cray-python/<IP_ADDRESS>

The other errors further down are as follows:
            f"{self.status_code} Server Error: {reason} for url: {self.url}"
        )

    if http_error_msg:

      raise HTTPError(http_error_msg, response=self)

E           requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://psij.testing.exaworks.org/result
______________ ERROR at teardown of test_simple_job[slurm:single] ______________
capsys = <_pytest.capture.CaptureFixture object at 0x7fffcfb52fd0>
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fffcfb52fa0>
request = <SubRequest 'report' for <Function test_simple_job[slurm:single]>>
pytestconfig = <_pytest.config.Config object at 0x7fffe8c0dca0>
@pytest.fixture(autouse=True)
def report(capsys, caplog, request, pytestconfig):
    save = pytestconfig.getoption('save_results')
    upload = pytestconfig.getoption('upload_results')
    if save or upload:
        caplog.set_level(logging.DEBUG)
        start = _now()

And many others that are spread over the 60K+ lines of the testing.log file.

I can't quite make out what the error is. I suspect there's more relevant info in the log. Can you do me a favor and email me two files:
psij-ci-env
testing.log

Sent. Thank you.

So I looked at the log. It seems like some python is available to run things, so the fact that the module load fails is not critical. It's puzzling though. So maybe we can work more to figure that out next week.
I'll take a look at the server logs. For some reason, the results fail to upload.

Module load failing or the module command not being available  may hint at incomplete shell initialization.  Is the shell used to run the crontab entry the same as your login shell?  If so, are some parts of your shell initialization (~/.bashrc) shielded for non-interactive logins?
If everything else fails, a source ~/.bashrc (for bash, your mileage may vary) before the module load might help, or maybe you can trigger the use of an interactive login shell (bash -il)?

@andre-merzky, to add some info to the discussion, the environment is saved in psij-ci-env. However, I noticed now that psij-ci-load is invoked before psij-ci-env. Perhaps not the right choice. Thoughts?

Module is a bash function on Crusher. I am not setting it up. I believe it is being set somewhere as part of /etc/rc:
<EMAIL_ADDRESS>~]$ type module
module is a function
module ()
{
    eval $($LMOD_CMD bash "$@") && eval $(${LMOD_SETTARG_CMD:-:} -s sh)
}

Module is a bash function

I was suspecting this to be the case. And I don't think functions are saved in psij-ci-env. However, the result of calling module load x is. So you can remove it from psij-ci-load.

@andre-merzky, to add some info to the discussion, the environment is saved in psij-ci-env. However, I noticed now that psij-ci-load is invoked before psij-ci-env. Perhaps not the right choice. Thoughts

Yes, I agree - switching those around would seem like a reasonable choice IMHO.
PS.: I just checked the env capture, and the problem might be here actually (in addition to the proposed switch): module is declared as a bash function, and bash has the (non-POSIX compliant) way to export functions as env variables:
$ foo(){ echo bar; }
$ foo
bar
$ export -f foo
$ env | grep foo
BASH_FUNC_foo%%=() {  echo bar
$ declare -x | grep foo
declare -x foo

Our env capture uses declare -x, but as seen above that does not capture the function body, and thus the module function will not be made available in the new shell.
We have been struggling with bash for quite a bit in the past - if you are interested, radical.utils has an env_dump and env_prep which addresses this issue.  Feel free to use or copy that code if you think it's useful:
$ . ~/j/ru/bin/radical-utils-env.sh
$ env_dump | grep foo > tmp.env
$ cat tmp.env
BASH_FUNC_foo%%=() {  echo bar\n}
$ env_prep -s tmp.env -t prep.env
$ cat prep.env

# blacklist
unset 'PS1'
unset 'LS_COLORS'
unset '_'

# export

# functions
foo () {
 echo bar
}
export -f foo

# end
$ unset -f foo
$ foo
command not found
$ . prep.env
$ foo
bar

Our env capture uses declare -x, but as seen above that does not capture the function body, and thus the module function will not be made available in the new shell.

That was intentional. The environment saved in psij-ci-env is not meant to be an interactive one. In other words, it is meant to capture what happens after module load rather than enable one to invoke module load. I think the problem is the comment in psij-ci-load which seems to suggest, a bit too quickly, that some kind of module load should be added there. I believe the solution is to make it clear that this should only be done if things fail to work without. Perhaps a quick test that starts with an empty environment, loads psij-ci-env, and invokes a simple python tool during setup may be useful to inform the user that things are likely to be ok.
I would perhaps caution against a too-complex solution for this problem if the problem isn't even a problem.

We claim Python 3.6 compatibility, but the text parameter appears to have been added in Python 3.7.
We could fix based on this statement in the python docs:

The universal_newlines argument is equivalent to text and is provided for backwards compatibility.

(from https://docs.python.org/3/library/subprocess.html#subprocess.run)

OK, it turns out that we require Python 3.7. Can you retry with an appropriate python version?

I loaded cray-python v 3.9 and re-ran the tests. Looking at logs, it looks like most tests are passing. I have sent the logs and env files in email to you Mihael. Thank you for all the help!

No update for 6 month. Closing this issue. Testing sites will be handled in a separate issue again.


api/auth/signing not working properly

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
Submitting a POST request to api/auth/signing results in the following error:
2024-04-12T00:29:25.585362846Z   File "/opt/venv/lib/python3.10/site-packages/rest_framework/views.py", line 332, in check_permissions
2024-04-12T00:29:25.585365972Z     if not permission.has_permission(request, self):
2024-04-12T00:29:25.585369104Z   File "/home/django/cvat/apps/iam/permissions.py", line 2032, in has_permission
2024-04-12T00:29:25.585372323Z     if not view.detail:
2024-04-12T00:29:25.585375258Z AttributeError: 'SigningView' object has no attribute 'detail'

Expected Behavior
The method is supposed to return a string (signed URL).
Possible Solution
N/A
Context

Environment
https://app.cvat.ai/

Probably, wrong swagger specification.
Signin is not implemented actually as far as I remember.
@Marishka17

is this implemented?


[Helix] Tests skipped due to can't find sln

Tracking all the tests that are skipped due to depending on a sln file being present. (Src is not part of helix test payloads)
Azure\ApplicationInsights.HostingStartup\test\UnitTests\JavaScriptSnippetTest.cs (all tests)
Azure\ApplicationInsights.HostingStartup\test\UnitTests\LoggingTest.cs (all tests)
DefaultBuilder\test\Microsoft.AspNetCore.FunctionalTests\WebHostFunctionalTests.cs (all tests)
Hosting\test\FunctionalTests\WebHostBuilderTests.cs (all tests)
Identity\test\Identity.Test\CdnScriptTaghelperTests.cs (IdentityUI_ScriptTags_SubresourceIntegrityCheck)
mvc\test\Microsoft.AspNetCore.Mvc.Analyzers.Test\AvoidHtmlPartialAnalyzerTest.cs
\Razor\Mvc.Razor.Extensions\test\IntegrationTestsCodeGenerationIntegrationTest.cs (all tests)

Summary of what tests are depending on in sources:
Identity.Test - Needs to scan all razor pages for script tags to verify CDN content matches

Individual issues exist for these now, or are tracked via https://github.com/aspnet/AspNetCore/issues/4248


New version: Peppy.Osu! version 2024.131.0

Pull request has been created with komac v2.0.2 :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-No-Executables

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


Fix: Don't throw when match is used with an unknown location

The following currently throws but it should be possible to use match with unknown urls
const routes = (
  <Route path="/" component={App}>
    <Route path="child/" component={Child} />
  </Route>
);

store.dispatch(server.match('/404', () => {}))

Dupe #122


GPU not detected by JAX. Warning: No GPU/TPU found, falling back to CPU.

JAX library does not use the GPU and shows warning
path/venv/lib/python3.6/site-packages/jax/lib/xla_bridge.py:130: UserWarning: No GPU/TPU found, falling back to CPU.
  warnings.warn('No GPU/TPU found, falling back to CPU.')

My code looks somewhat like this. I am not able to post the exact code I was using, as it is a part of an exercise.
from trax.fastmath import numpy as fastnp
v1 = np.array([[0.1172474, 0.6472824, 0.8061181],[0.6172836 , 0.5123475, 0.9017283]])
v2 = np.array([[ 0.5933123,  0.1162829,  0.9063872],[-0.6481012 , -0.57543534, -0.7162344]])
margin=0.25
scores = fastnp.dot(v1, v2.T)

Also, on checking the backend devices with the following code, I get to see only the CPU.
from jax.lib import xla_bridge
print(xla_bridge.get_backend().platform)

cpu

However, if I check devices using tensorflow, I can see the GPU.
import tensorflow as tf
tf.config.list_physical_devices('GPU')

[PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')]

Here are the outputs of nvcc and nvidia-smi.
nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Sun_Jul_28_19:07:16_PDT_2019
Cuda compilation tools, release 10.1, V10.1.243

Fri Aug 14 11:19:05 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.57       Driver Version: 450.57       CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 2070    Off  | 00000000:31:00.0  On |                  N/A |
|  0%   49C    P8    17W / 175W |    894MiB /  7979MiB |      3%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1562      G   /usr/lib/xorg/Xorg                 24MiB |
|    0   N/A  N/A      1696      G   /usr/bin/gnome-shell               50MiB |
|    0   N/A  N/A      1939      G   /usr/lib/xorg/Xorg                493MiB |
|    0   N/A  N/A      2071      G   /usr/bin/gnome-shell              188MiB |
|    0   N/A  N/A      2984      G   .../debug.log --shared-files       17MiB |
|    0   N/A  N/A      3386      G   /usr/lib/firefox/firefox            2MiB |
|    0   N/A  N/A      4283      G   /usr/lib/firefox/firefox            2MiB |
|    0   N/A  N/A      5579      C   ...ffice/program/soffice.bin       97MiB |
|    0   N/A  N/A      5665      G   /usr/lib/firefox/firefox            2MiB |
|    0   N/A  N/A      5813      G   /usr/lib/firefox/firefox            2MiB |
|    0   N/A  N/A      8409      G   /usr/lib/firefox/firefox            2MiB |
+-----------------------------------------------------------------------------+

Can I make JAX use the GPU?

Closing the issue as the problem has been resolved.  It turns out that I had CUDA installed. I also installed CUDNN and then installed JAX with both CPU and GPU support (using existing CUDA and CUDNN libraries) according to the instructions here.


contracts/: several changes

Add WRAPPEDNATIVE to version for CWrappedNative.
Return underlyingPrice in CTokenMetadata.
Return nativeTokenBalance in CTokenBalances.

Deployment steps:

Upgrade comptroller (for new cToken version).
Upgrade CWrappedNative (currently only crWMATIC on polygon).
Deploy a new lens.

LGTM


Material Tree Table

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
I wonder if there are tree table like ng-treetable (https://www.npmjs.com/package/ng-treetable), but with a column size correct when expand detail.

Thank you

Please keep GitHub issues for bug reports / feature requests. Better avenues for troubleshooting / questions are stack overflow, gitter, mailing list, etc.
(this is a canned response)


edited pakiti.sql

tables added in pakiti.sql

Please use exactly the same syntax (uppercase, lowercase, indentation, ...) which is used in the rest of the file.


Change support menu

Is your feature request related to a problem? Please describe.
For now, we hide debug menu for all production builds (alpha/beta test channel included). There is a request to show this menu for test builds.
Describe the solution you'd like
Menu items:
DELETE Wallet
Alternatives you've considered
I'd suggest adding this missing puzzle to the Settings' screen overflow menu.

Closing as not needed anymore.


How to check the first radio in radiogroup by default?

Describe the bug
I have multiple radios, and need the first one to be checked by default. However radiogroup has no more arguments except value.
To Reproduce
Steps to reproduce the behavior:

Code/Link to Repo:

Expected behavior
Want the first raido to be checked by default
Screenshots
If applicable, add screenshots to help explain your problem.
** Specifics (please complete the following information):**

Python Version: 3.7
Pynecone Version: 0.1.28
OS:
Browser (Optional):

Additional context
Add any other context about the problem here.

from pcconfig import config

import pynecone as pc

choices = ["a", "b", "c"]

class State(pc.State):

    pass

def index() -> pc.Component:
    return pc.center(
        pc.vstack(
            pc.radio_group(
                choices,
                default_value="a",
                # This also works:
                # default_value=choices[0],
                default_checked=True,
            ),
        ),
        padding_top="10%",
    )

app = pc.App(state=State)
app.add_page(index)
app.compile()

This does not work, no radio is checked.

You need to upgrade to the latest version of pynecone. This won't work on 0.1.28.

Thank u Shawn, upgraded to 0.1.29, it works.


Action is failing due to secondary rate limit warning

The action is randomly failing due to secondary rate limit errors.
Observed Error:
github.GithubException.RateLimitExceededException: 403 {"documentation_url": "https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits", "message": "You have exceeded a secondary rate limit. Please wait a few minutes before you try again."}
(happens after 2s of execution)
The action is invoked like this:
Run EnricoMi/publish-unit-test-result-action@v1
with:
check_name:  Results
comment_title: Results
files: ./junit.xml
github_token: ***
github_retries: 10
fail_on: test failures
hide_comments: all but latest
comment_mode: update last
compare_to_earlier_commit: true
pull_request_build: merge
check_run_annotations: all tests, skipped tests
seconds_between_github_reads: 0.25
seconds_between_github_writes: 2.0
Stack Trace
Traceback (most recent call last):
File "/action/publish_unit_test_results.py", line 283, in
main(settings, gha)
File "/action/publish_unit_test_results.py", line 96, in main
Publisher(settings, gh, gha).publish(stats, results.case_results, conclusion)
File "/action/publish/publisher.py", line 66, in publish
pull = self.get_pull(self._settings.commit)
File "/action/publish/publisher.py", line 82, in get_pull
logger.debug(f'found {issues.totalCount} pull requests in repo {self._settings.repo} for commit {commit}')
File "/usr/local/lib/python3.6/site-packages/github/PaginatedList.py", line 150, in totalCount
"GET", self.__firstUrl, parameters=params, headers=self.__headers
File "/usr/local/lib/python3.6/site-packages/github/Requester.py", line 355, in requestJsonAndCheck
verb, url, parameters, headers, input, self.__customConnection(url)
File "/usr/local/lib/python3.6/site-packages/github/Requester.py", line 378, in __check
raise self.__createException(status, responseHeaders, output)
github.GithubException.RateLimitExceededException: 403 {"documentation_url": "https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits", "message": "You have exceeded a secondary rate limit. Please wait a few minutes before you try again."}

Can you provide me a link to such a workflow run if the repo is public? Can you set ROOT_LOG_LEVEL and LOG_LEVEL to DEBUG to get some extra insights?

Unfortunately the workflows are all private. I will work on a trace with DEBUG enabled. This may take a few days.
Since the issue happens after 2s, it may be related to retry-behavior of 403. We checked the primary rate limit for the GITHUB_TOKEN and it is way under the 15K limit (using GHEC).

The latest release does not retry 403 responses at all, retrying those is sitting unreleased in master. I am wondering which API access might trigger this.

It seems the retry for 403 has been released now. We´ll try the new version and re-open the issue if the error occurs again.


[Accessibility]A11y_VSCode_VSCLicenseAgreement_Keyboard: All the Links are not accessible by keyboard using tab key.

Environment Details:
VSCode Version : 1.24.1
OS Version : Win10
Additional Details:
NVDA 2018.2, MAS2.1.1
Repro Steps:
1.On VSC Setup Wizard, click on "Next" button.
2.Check using tab key able to access links or  present inside (edit  read only  multi line dialogue box )
Actual:
Links are not accessible by keyboard using tab key (present inside (edit  read only  multi line dialogue box)
Expected:
All links should be accessible by keyboard using tab key present inside (edit  read only  multi line dialogue box )
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
The user will not be able to access the controls using tab key.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
Does this issue occur when all extensions are disabled?: Yes
Attachment for Reference:

@AccessibilityTestingTeam-TCS This needs to go into https://github.com/jrsoftware/issrc


Define use case for F2 skip mapping

Each QSO returned by a query should have a link added to it that takes the user to the results of a new query where each row contains the shortest distance between an ionosonde and the QSO path from tx to rx stations.
The user can then sort or filter these to limit the number of ionosondes that are applied to determine the height of an ionosphere's F2 layer along the path of a QSO at the time of the QSO.

Creating tables in datasette.


[BUG] KS Device Endpoint Manager creates BiDi endpoints only for USB devices with exactly two pins (in and out)

Applies To
Midi2.KSMidiEndpointManager.cpp, OnDeviceAdded
Describe the bug
Has a gate on 2 pins, but needs to work for 1-n pins. The result right now is many KS devices don't appear to the API because they don't have BiDi endpoints.
This was originally by design, but after the meetings in Redmond and elsewhere, this is now a bug.
AFAIK, this doesn't impact devices exposed by the new USB driver, only devices exposed by the legacy driver, or third-party drivers.

Fixed for Developer Preview 6


Master build unstable

https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/424/testReport/

runtime.RuntimeValidatedConntrackTable Testing proxy redirect after installing L3-L4-L7 policy over an existing L3-L4 policy
runtime.RuntimeValidatedConntrackTable Testing L3-L4-L7 policy while the L3-L4 connection was previously made to confirm L3-L4-L7 policy enforcement over the proxy with the same source port

https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/422/testReport/

runtime.RuntimeValidatedConntrackTable Testing L3-L4-L7 policy while the L3-L4 connection was previously made to confirm L3-L4-L7 policy enforcement over the proxy with the same source port

The issue is tracked in https://github.com/cilium/cilium/issues/3208.
Can we close this one?

#3255 disabled this test in master so it can be tracked separately, so yes, let's close this.


provider random password resource number to numerical change.

What problem are you facing?
With https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/password version 3.3.0 they have changed from number to numerical string. This can be checked on https://registry.terraform.io/providers/hashicorp/random/3.3.0/docs/resources/password
When we use latest version of pre-commit-terraform (v1.77.0)  it complains that it does not recognize numerical string. It would be nice that it supports both string.

How could pre-commit-terraform help solve your problem?

Hey @omerfsen
pre-commit-terraform is a wrapper for other tools which do lint code and alike.
To help identify which exact tool is failing for you we need more info. First off please post output of pre-commit-terraform where the error you faced is visible.


Opening GLTF Importer causes embedded textures to become unintentionally extracted

Godot version
v4.0.beta.custom_build [705273140]
System information
windows 10
Issue description
When double-clicking a gltf file in the project, the Importer panel will open, but it will also extract the embedded textures.
This never happened in the previous version I was using (I'm not sure which beta I was using last- maybe 13 or 14).
Steps to reproduce
open the project, and double-click the gltf file to open the importer, see that it creates an image file when it should stay embedded.
Minimal reproduction project
gltf import bug.zip

As keeping the embedded textures uncompressed was not viable, we made the change to provide three options:

extract textures
save as basisu
make the image empty like white

As keeping the embedded textures uncompressed was not viable, we made the change to provide three options:

extract textures
save as basisu for portable textures
make the image empty like white

It totally defeats the purpose using embedded textures though, if that's that case. I don't want to have a ton of texture image files clogging up my folders.
In previous versions it seemed to work fine- what exactly caused the decision to make it worse?

@prominentdetail The reason for the change was that gltf files with embedded textures could not be properly compressed: in every version up to now, those embedded images were getting shipped uncompressed (well, compressed losslessly as png, but they would be loaded into graphics memory uncompressed)
To get an idea of the problem, each 2048x2048 texture consumes 16MB of graphics memory on your GPU if stored uncompressed, while it will only consume 2MB of GPU memory if vram compressed without alpha (the default for 3d projects), so that means the embedded textures in glb files were incurring up to 8x overhead (or 4x with alpha).
So that's the main issue which led to this decision. There's certainly room for debate and discussion: that's why we rushed to get this into beta16, because we want to hear from users.
I'd be curious your thoughts on this trade-off. Also, have you considered using Basis Universal for your textures? that would allow it to be compressed as part of the gltf import process.

@lyuma
How would I keep the images UNcompressed in the gltf files? I need them lossless quality because I am using low-res pixel-art textures.
Seems like beta 16 forces the texture quality to get all mangled up due to the compression of the basis universal.
You can see here how it looks messed up now in beta 16:

We're experimenting with adding the old behavior back in #72440 as a setting "Embed as Uncompressed". It will be settable as a project default here:

Thanks for the issue and providing a real world example showing how the intended workflow of using compressed textures was impacting your project.

Thanks for working on this, and adding that option! I appreciate all the help you've provided! :)


Setup Authentication Frontend

Description
Altinn Authentication Frontend will use the same pattern as Altinn Access Management Frontend. Meaning

A SPA (Single Page App) frontend based on React
A Backend for Frontend based on .Net
Build and deploy pipelines in Github
Hosted as an Azure Container App

The following epic describes the different tasks to set up the basic structure for this architecture.
Tasks should be separated into separate issues when started on.
In scope

Setup Code
Setup tests
Setup pipelines for build and deploy
Setup infrastructure

Out of scope

Create functionality related to new functionality in Altinn Authentication

Additional Information
We need to think about handling scenarios where the user is not authenticated. This component is where we will add authentication for methods not available in ID-porten. Like Self authenticated user. How should we handle routes where we have some URL that require that the user is authenticated and other routes that should work when user is not authenticated?
Architecture Recommendation
TODO
Recommended Project Setup
Set up a new solution called Altinn.Authentication.UI with the following projects

Altinn.AuthenticationUI -  .Net Core 7 API project
Altinn.Authentication.UI.Core  - Core models and interfaces
Altinn.Authentication.UI.Integration - Clients to call
Altinn.Authentication.UI.Mocks  - Mock implementation for clients to be used for testing
Altinn.Authentication.UI.Tests - .Net integration test of BFF

Where relevant, we should reuse integration code and API from Altinn.AccessManagment.UI

Duplicate Profile API from Altinn Access Management BFF
Duplicate Authenticaiton API from Altinn Access Management BFF

Database
Security
Infrastructure
### Authentication Frontend
- [ ] #5

### Authentication BFF
- [ ] #8
- [ ] #9

### Azure Infrastructure
- [ ] Setup Azure Container apps with URL authn.ui.altinn.no in prod
- [ ] Define infrastructure setup for hosting the BFF with frontend
- [ ] Domain certificate for the application
- [ ] Create Platform certificate for integration with platofrm components

### CI/CD
- [x] Action for frontend build. See Access Management frontend
- [ ] Action for BFF build See Access Management frontend
- [ ] Deploy action for AT environments
- [ ] Release action for the Authentication frontend app
- [ ] Add sonar cloud linting

### Test Automation
- [x] Setup basic test to test Hello World View: an initial goal is a Cypress end-to-end test
- [ ] Implement K6 Tests for authentication bff application

Today a pipeline demonstrated several features of the Frontend repo, including:

checkout of the entire repo to the Github Runner environment (set to ubuntu-22.04)

installing of Frontend dependencies (yarn packages) in a working-directory

the Cypress component tests were successfully run (yarn coverage)

and the Vite build configuration was tested by the yarn build command (works locally, works in pipeline),
producing a javascript bundle along with other assets (see screenshots below): this build is a pre-requisite for the "wrapping" of the React app by the dotnet BFF app etc...

See frontend_build_and_cypress.yaml file for details.
This experimental pipeline is only triggered by a push to the cypress8 branch
in order to limit noise.


sha3 on Python 3.4.3 on Mac OSX

When trying to use triplesec on Mac OSX 10 after installing Python 3 using homebrew, it fails on the sha3 functions because of the following:
if sys.version_info < (3, 4):
    import sha3

When I run a hashlib.algorithms_available, there are no sha3 algos listed.

Fixed with my PR being merged.


NPC Indicators - Show NPC Focus

Do you ever get frustrated when you haven't tagged all the Dust Devils, Bloodvelds, or other AFKable NPC's?
Wouldn't it be handy to have the NPC indicator tile change colour when the NPC is focusing on you?

For the first line, that's what the NPCs to Highlight list is for. In the next update, there'll be an option on the shift right click menu to do that without having to type the name.
As for the second, I think that comes under Jagex's Statement: Indicates which player an NPC is focused on, though it might be far enough away to be fine; really not sure

@Hydrox6 My apologies, the first line was meant in the sense of, 'tagging' with damage to gain agro against the foe.


[My habits] User doesn't get points for each day of habits in progress

Environment: Windows 10 Version 21H2, Chrome Version 116.0.5845.97.
Reproducible: always.
Build found: 24.08.2023
Preconditions
Registered user has at least one habit in progress
Steps to reproduce

Go to: https://www.greencity.social/.
Sign in.
Go to the 'My habits' page.
Pay attention to the 'Rate' on the left.

Actual result
'Rate' is 0 (see attachment).
Expected result
User gets 1 point for each day of habits in progress
Postconditions
User story and test case links
User story #997
Test case"
Labels to be added

Not reproducible
https://github.com/ita-social-projects/GreenCity/assets/122612827/c3b07927-ab38-4535-9345-f6a4ee15c178


Decouple "Active Terminal" and "Focused Control"

Summary of the Pull Request
Unties the concept of "focused control" from "active control".
Previously, we were exclusively using the "Focused" state of TermControls to determine which one was active. This was fraught with gotchas - if anything else became focused, then suddenly there was no pane focused in the Tab. This happened especially frequently if the user clicked on a tab to focus the window. Furthermore, in experimental branches with more UI added to the Terminal (such as dev/migrie/f/2046-command-palette), when these UIs were added to the Terminal, they'd take focus, which again meant that there was no focused pane.
This fixes these issue by having each Tab manually track which Pane is active in that tab. The Tab is now the arbiter of who in the tree is "active". Panes still track this state, for them to be able to MoveFocus appropriately.
It also contains a related fix to prevent the tab separator from stealing focus from the TermControl. This required us to set the color of the un-focused Pane border to some color other that Transparent, so I went with the TabViewBackground. Panes now look like the following:

References
See also: #2046
PR Checklist

[x] Closes #1205
[x] Closes #522
[x] Closes #999
[x] I work here
[😢] Tests added/passed
[n/a] Requires documentation to be updated

Validation Steps Performed
Tested manually opening panes, closing panes, clicking around panes, the whole dance.

 The whole lambda in Split should be gone, that should just be the AttachPaneEventHandlers(second) call


feature: configurable single source of truth for keymaps

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
I - as several others i realise after skimming reddit and the issues - have some problems changing LazyVims default keymaps. I am not saying it is not possible. I am just saying it requires knowledge of how lazyloading works and a multitude of changes in different files (overriding plugin options, changes in my own keymap.lua) along with a lot of copy pasting of anonymous functions that i cannot just map to.
My usecase in particular was that I wanted to change the "prefix" for code actions from <leader>c to <leader>C.
From my experience this is a problem that some (most?) of the neovim distributions have (i have used LunarVim and NvChad before). Let me know if this has been adressed in another neovim distribution in some way.
Describe the solution you'd like
I would like a definition file covering all keymaps like this:
{
  "PrefixCode" = "<leader>c",
  "KeymapMason" = "%PrefixCode%m",
  "KeymapFormatInjected" = "%PrefixCode%F",
  ...
}

So if i want to change the defaults, i can just override in my file:
{
  "KeymapFormatInjected" = "gFF", -- just change one particular keycombo
  "PrefixCode" = "<leader>C", -- change the prefix and everything that depends on it
}

at startup the two dictionaries are merged and populated (replace placeholders by actual values until the dict does not change anymore). The result is the available throughout all the plugin initializations, which only refer to the ids of keymaps looking them up in the merged dict.
This would make changing defaults a lot more straighforward and would require no knowledge about when and how plugins are loaded and keymaps are set.
Describe alternatives you've considered
Manually remapping each individual keycombo that involves <leader>c which not only is a major pita but also will probably break on some future change where a LazyVim extra introduces a new keycombo.
Additional context
If you do not have any considerations about performance impact or other caveats i havent thought about, i would love to work on this if it has a chance of getting merged.

Hello @pathetic-lynx,
Reading your excellent feature request, I discern two use-cases.
First use case: Change one or more individual keys

My usecase in particular was that I wanted to change the "prefix" for code actions from c to C.

This is only one key, <leader>ca.
Changing lsp keys is explained in the LazyVim docs:
lsp keymaps
customizing lsp keymaps
The knowledge obtained by changing the key is very valuable.
After all, LazyVim is intended to make it easy to customize and extend your config.
Second use case: Change a complete top level menu

Manually remapping each individual keycombo that involves c which not only is a major pita but also will probably break on some future change where a LazyVim extra introduces a new keycombo.

I agree that in this case the amount of work is considerable.
Especially given the intent of the user: To use the corresponding leader key for something else.
I wrote a plugin implementing the second use case: lazyvim-menu-addon
The reason for writing the plugin is explained here
The plugin is announced in the discussions section: show and tell
I would be very interested in your feedback!
@folke, what do you think?

Hi @abeldekat,
first of all thanks for writing a plugin! <3 This was really keeping me from using Lazyvim. I was working on sth myself but it would've probably taken me much longer.

First use case: Change one or more individual keys

I did non mean code action but rather "anything that starts with <leader>c". But the two usecases exist nonetheless and I share your opinion that using the already well-documented way of changing keybinds is preferred here.
There still is an advantage when rebinding is done separately from plugin configuration, namely that when changing a keybind you sometimes also have to add plugin options unrelated to the keybind to your customization config. This leads to potentially incompatible plugin config when someone updates the plugin and changes the defaults or invalidates the snippet that was copied to change the keybind.
Somebody going the way to change individual keybinds for a plugin that person might already have changed the default config or would not mind fixing the config when it breaks (which i would assume does not happen that often) so i believe this is not an issue.
I totally agree with you on the cons of my approach, it would require everybody to be aware of the definition file and how to use it.
I can see a middle way where the keybinds (again a ExposedFunctionality -> Keybind map) are a separate part of the plugin configuration thus avoiding the problems of incompatible configs.
I think for now I'll use your plugin and report back :)

Thanks, @pathetic-lynx!
I think I don't fully understand what you mean when you mention "incompatible config".
Basically, whenever a user starts customizing LazyVim, there is always a chance that the base spec being customized changes. At its core, in my opinion, LazyVim is just a bunch of lazy.nvim specs. That's part of its power: The user can customize almost everything without limitations.
As a consequence, that user might need to inspect incoming updates for changes that might affect those customizations.

Somebody going the way to change individual keybinds for a plugin that person might already have changed the default config or would not mind fixing the config when it breaks (which i would assume does not happen that often) so i believe this is not an issue.

Looking at my config I think I can say that I customized a lot. And as such, gained the knowledge to fix any incoming incompatibilities. Most of the time, there is nothing to fix... Except on breaking changes, which are announced as breaking.
I am now using the addon for leaders b, q and w. You chose the most difficult leader to change... I would be curious to know the new purpose of your leader c.
I do wish to say that as a user I am just expressing an opinion. If it were up to me, the second use case we where talking about would be supported by LazyVim itself.

I can see a middle way where the keybinds (again a ExposedFunctionality -> Keybind map) are a separate part of the plugin configuration thus avoiding the problems of  incompatible configs.

Interesting!
Best regards!

Thank you for the suggestion, but I think this would complicate things and would be too different from how you configure plugins with lazy.nvim.
And thank you @abeldekat to provide a plugin to make it possible to change top-level keys!
That should solve op's issue.

This plugin stopped working some time ago. I have been able to fix one problem in the e2e test (https://github.com/pathetic-lynx/lazyvim-menu-addon/commit/0813f0c16847a3bf92fd87cc04733c5540279107) but the other problem eludes me. I tried pinning LazyVim, lazy.nvim and which-key.nvim to older versions but to no avail.
Could @abeldekat or someone more familiar with the architecture look into this? I spent quite some time trying to fix this but I'm out of ideas :/


Exception when calling TextPrompt.DefaultValue(value) with brackets

Information

OS: MacOS
Version: 0.46.1.preview.0.8
Terminal: iTerm

Describe the bug
TextPrompt.DefaultValue is not escaped when displayed in TextPrompt.
To Reproduce
  var queryStr = "root['config'][0]";

  AnsiConsole.Prompt(new TextPrompt<string?>("Query: ").DefaultValue(queryStr).AllowEmpty());

Exception is thrown: System.InvalidOperationException: Could not find color or style ''config''.
Workaround of using Markup.Escape() is not suitable as it retains the markup.
  var result = AnsiConsole.Prompt(new TextPrompt<string?>("Query:").DefaultValue(Markup.Escape(queryStr)).AllowEmpty());

Result retains escaping: root[['config']][[0]]
A clear and concise description of what the bug is.
Expected behavior
DefaultValue is escaped when displayed.

I can confirm running into this issue as well. I have a prompt to set names for objects with the previous name as a default option so a user can just press enter for no change. If the name is set to something like "[ABC] DEF" it will except when trying to parse markup in the default value display.


zoxide: 0.4.1 -> 0.4.3

https://github.com/ajeetdsouza/zoxide/compare/v0.4.1...v0.4.3
Also removes unnecessary rec and stdenv.

Motivation for this change
New release.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Reviewed points

[x] package name fits guidelines
[x] package version fits guidelines
[x] package build on Darwin 19.5.0
[x] executables tested on Darwin 19.5.0
[ ] all depending packages build

Possible improvements
Comments

Result of nixpkgs-review pr 92250 1

1 package built:
- zoxide


suggested fix for issue 235

inventory_quantity: cast string values to int
allow 0 as a value for inventory_quantity

Hey I also hit this one and this PR fixes it for me too, only way I could update my products via admin besides editing directly in database

Thanks! Solved in #325


Include vcpkg.exe in the repo

Unless I missed some important information, I see no possibility how to differentiate between updates to the vcpkg source code and changes to the "content", i.e. the portfiles and such.  This causes that uin my automation scripts I always need to call bootstrap-vcpkg which builds the executable from source. It would help a lot if you either (a) check in a compatible self-contained vcpkg.exe binary or (b) (and even better) separate the content from the package manger implementation completely. By the way, why on earth is this implemented in C++ and not is PowerShell & Co.?

This issue hasn’t been updated in a year; if it is still an issue, please reopen.


Basic issues left with currently available data

Summary
There are some issues that are highlighted by our coverage scripts. Most of them should be easy to handle, they just need to be verified with the spec and committed to the repository.
Issues:

[ ] Box enca is not listed as container for box sinf
[ ] Box strk is not listed as container for box stsg
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Box sbgp is not listed as container for box alst
[ ] Path ~enca.sinf is not listed as container for box schi
[ ] Box mp4a was found in submitted files and it exists in MP4RA but not in our database
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Path ~enca.sinf is not listed as container for box schm
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Box mp4s was found in submitted files and it exists in MP4RA but not in our database
[ ] Box sbgp is not listed as container for box nalm
[ ] Box lhe1 is not listed as container for box btrt
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Box sbgp is not listed as container for box rash
[ ] Box lhv1 is not listed as container for box btrt
[ ] Box hvt1 is not listed as container for box btrt
[ ] Box iref is not listed as container for box cdsc
[ ] Box mp4v was found in submitted files and it exists in MP4RA but not in our database
[ ] Box m4ae was found in submitted files and it exists in MP4RA but not in our database
[ ] Box tref is not listed as container for box sync
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Path ~enca.sinf is not listed as container for box frma
[ ] Box sbgp is not listed as container for box roll
[ ] Box sbgp is not listed as container for box tele
[ ] Box esds was found in submitted files and it exists in MP4RA but not in our database
[ ] Box tref is not listed as container for box dpnd
[ ] Box sbgp is not listed as container for box rap
[ ] Box sbgp is not listed as container for box rap
[ ] Box sbgp is not listed as container for box refs
[ ] Box iods was found in submitted files and it exists in MP4RA but not in our database

Steps to reproduce
You run run npm install && npm test on root directory

Looks like esds got a few mentions there.


Rename hypervisor.Pod to hypervisor.PodStatus

Too many things called Pod

just a rename, I will merge it at once


Due to slower performance revert tests to sub-tests from separate functions

Separating a test into functions make the test considerably slower. Therefore, splitting the test should only be a last resort course of action

test_support.go

Improves the delete integrations function to wait for the deletion to complete before moving on

Release Note
NONE

Upgrade tests failed due to failure to download dependencies.


Question nav: the control buttons take too much height on a narrow but landscape screen

Here's how the Numbas app looked when I loaded it on my mac:

There's only space for one question in the list, because the controls at the bottom take up too much height. They don't use much width, so they could be laid out horizontally.

I think this is fixed. This is what the menu looks like now:


Computing Transaction ID in Transaction Builder

As an application developer, I would like to know what a trx_id will be for a particular transaction I'm about to broadcast for the purpose of polling for this transaction later after it has been broadcasted, so that I can find it in case of timeout or other service interruption.
AC

[x] Steem::TransactionBuilder is able to compute trx_id before broadcast

Change in #15, specific line: https://github.com/steemit/steem-ruby/pull/15/files#diff-32ad2e86b72b0220bd2a568d75ec1e7eR240


Implement Global Broker for WIS2

In addition to each issue (one per GB), I think it is useful to have a shared one where we can discuss aspects that are common to all GB and use this place instead of exchanging emails and keep easily tracks of you discussions.
@Haddouch101 can you please assign this issue to Weiqing, Wang and Kari? Thanks.

@golfvert We will start work on GB soon (hopefully from next week). I remembered that you mentioned some docs on setting up GB. Would you be able to share that. What I am looking for is a bit of guidance.

The Global Broker is made of two (almost) independent components:

a MQTT broker setup. Typically to be chosen between RabbitMQ, EMQX, VerneMQ, Mosquitto. The latter is the simplest to deploy but can't be clustered. So, it would be a SPOF if used. It could be an option though to start quickly something while working in parallel on implementing a more complex solution. RabbitMQ (version 3.11.6 at time of writing) is an open source solution. Not the simplest tool to deploy. Not (yet) MQTT 5.0 compliant (I have been told that a RabbitMQ compliant with MQTT 5.0 should be released toward the middle of this year). These two are open source and free of charge. VerneMQ is a payable solution. No experience in EMQX. I would suggest either Mosquitto (to start quickyl) or RabbtMQ (to start in a clustered mode) to be chose.
an anti loop feature ahead of the broker. Here https://github.com/golfvert/WIS2-GlobalBroker-NodeRed an example that is used by Météo-France. It also gives the details of what should be done.

A quick (and dirty) solution would be for those not familiar with MQTT broker and no anti-loop tool ready to start with Mosquitto and WIS2-GlobalBroker-NodeRed tool as a start getting familiar with WIS2 solution and introduce redundancy in the design of the pilot. And rapidly to move to a clustered RabbitMQ and another anti-loop solution in eg. python.
For those (CMA) having already a RabbitMQ installation, obviously, no need to "downgrade" to Mosquitto.

We should also clarify QoS parameters as well as retention periods (the WIS2 Guide would where these could be documented for clarification).

OK: https://github.com/wmo-im/wis2-guide/issues/5


SQLite.Net.SQLiteException: unrecognized token

This is working:
SELECT * FROM Stock WHERE ProductName LIKE '%áa%'
This is throwing:
SELECT * FROM Stock WHERE ProductName LIKE '%aá%';
Here is the error:
[MonoDroid] UNHANDLED EXCEPTION:
[MonoDroid] SQLite.Net.SQLiteException: unrecognized token: "'%aá%"
As you can notice, there is a missing " ' " at the end of the query.
I´ve checked the query with a console trace and the last " ' " is there but it´s missing in the actual execution as you can see in the error.

I had similar issue, what I did I used parameters. So do something like this, the
string query = "SELECT * FROM Stock WHERE ProductName LIKE ?";
var result = connection.Query(query, "%áa%");


TCP Sync Client

Hi:
I'm still reasonably new to Rust. I tried to run your client example from here https://github.com/slowtec/tokio-modbus/blob/main/examples/tcp-client-sync.rs, but it gave me the error via vscode: failed to resolve: use of undeclared crate or module sync
Any ideas?
Thanks
G

You need to enable the required features manually: https://github.com/rust-lang/cargo/issues/4663
cargo run --example tcp-client-sync --features tcp-sync

I did that, and it returns error: none of the selected packages contains these features: tcp-sync

I tested it on the main branch and it works.

I don't know anything about your private project. But it looks like you forgot to add the features to the dependency.

Thanks Uwe. That was my bad. I got it to build ok. I changed the example like this
fn main() {
    use tokio_modbus::prelude::*;

    let socket_addr = "<IP_ADDRESS>:502".parse().unwrap();
    let mut ctx = sync::tcp::connect(socket_addr).unwrap();
    let buff = ctx.read_input_registers(3, 1).unwrap();
    println!("Response is '{buff:?}'");
}

And it returns
    Finished dev [unoptimized + debuginfo] target(s) in 0.04s
     Running `../tokio-modbus/target/debug/examples/tcp-client-sync`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: ExceptionResponse { function: 4, exception: IllegalDataAddress } }', examples/tcp-client-sync.rs:11:47
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Yet mbpoll is able to see the data:
mbpoll -m tcp -a 1 -t 4 -r 3 -c 1 -1 <IP_ADDRESS>
......

Protocol configuration: Modbus TCP
Slave configuration...: address = [1]
                        start reference = 3, count = 1
Communication.........: <IP_ADDRESS>, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, output (holding) register table

-- Polling slave 1...
[3]: 	2

Any ideas?

Check the tokio-modbus docs about 0/1-based addressing.

I'm having the same issue as the OP:
I have tried both:
[dependencies]
tokio-modbus = "*"
and
[dependencies]
tokio-modbus = { version = "*", default-features = false, features = ["tcp"] }
in my .toml file.
My main.rs file in the src folder has the code from https://github.com/slowtec/tokio-modbus/blob/main/examples/tcp-client.rs
Can you help me resolve the confusion please?

Further: when I invoke cargo run --features tcp I get
"none of the selected packages contains these features: tcp"


The two missing pieces of talk export

I need additional requirements and category; once again, I can't test this locally!
@lukesneeringer could you sanity check this for me?

LGTM

Thank you!


Crash on fresh Windows

Today I tried running wgpu on a fresh Windows 11 machine, the compute example worked, but anything that required a window crashed hard. Not even panic, just crash. It took me a few minutes to realize that I should probably install gpu drivers (the machine has a Nvidia card), but I can imagine users easily overlook this, since there was already an Nvidia icon in the taskbar.
Things worked fine as soon as I installed the driver.
We may want to document somewhere that if examples crash at the moment that the window is shown, they should probably try updating their drivers.

I wonder if using the Dx12 backend on Windows will prevent this. I'll try to uninstall the driver to see if I can reproduce the issue, and then try using dx12.

Fixed (to the degree that we can, from here) in #382


ACAO Headers

The "detektiiif" chrome plugin is warning that Wellcome manifests aren't CORS enabled.
However, the ACAO header is present when UV etc asks for a manifest, with fetch.
Playing around in POSTMAN I find that I can't trigger an ACAO header on the response, even with origin header set.
Also I find that an OPTIONS request returns a 405 not allowed from Cloudfront.
So CORS / ACAO is working on Wellcome (otherwise viewers couldn't load cross domain) but client has to send exactly the right headers.
Reasses how we're handling CORS headers, for example ACAO is always present rather than requiring specific headers.

The issue is this one:
https://weblog.west-wind.com/posts/2016/sep/26/aspnet-core-and-cors-gotchas#Watch-out-for-testing-CORS-without-Cross-Domain!
The question is whether we replace the "clever" CORS policy provided by services.AddCors(..) with a blanket middleware that adds the ACAO header to all outgoing requests.
FWIW, the wc.org API responses to have "blanket" CORS headers regardless of what headers you send:
https://api.wellcomecollection.org/catalogue/v2/works/n3cc5qa3
Are there any implications for how cloudfront caches this?

The question is whether we replace the "clever" CORS policy provided by services.AddCors(..) with a blanket middleware that adds the ACAO header to all outgoing requests.

We have this for the thumbs service in Protagonist -
https://github.com/dlcs/protagonist/blob/develop/src/protagonist/DLCS.Web/Middleware/AlwaysCorsMiddleware.cs

Are there any implications for how cloudfront caches this?

AWS docs on CORS + Cloudfront: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/header-caching.html#header-caching-web-cors. Can't recall how we've set it up, would need to check.

Update - tested today and I can get ACAO header set when setting an Origin header (irrelevant headers removed):
λ curl --head -X GET https://iiif.wellcomecollection.org/presentation/b2101310x
HTTP/1.1 200 OK
Content-Type: application/ld+json; profile="http://iiif.io/api/presentation/3/context.json"
Date: Mon, 12 Jun 2023 11:35:05 GMT

λ curl  -H "Origin:my-origin" --head -X GET https://iiif.wellcomecollection.org/presentation/b2101310x
HTTP/1.1 200 OK
Content-Type: application/ld+json; profile="http://iiif.io/api/presentation/3/context.json"
Date: Mon, 12 Jun 2023 11:28:36 GMT
Access-Control-Allow-Origin: *

CORS headers are being set when requested with Origin header - we should open an issue in the detektiiif repo to get an answer as to why it's not picking up, e.g. https://wellcomecollection.org/works/zjytxny8/items


all-in-one-postgres TLS error

Hello
I juste create a new cluser (1.12) on EKS
And run https://github.com/Kong/kubernetes-ingress-controller/blob/next/deploy/single/all-in-one-postgres.yaml
After that, I link Ip Adress to my domain with Gandi
@ | A | 10800 | 21x.7x.14x.4x
And open in browser my domaine <abc.com>
It switch to HTTPS
Is it normal ?

So I tried to add a ssl certificate
Simply like this :
https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
And create a dummy app with tls
    apiVersion: extensions/v1beta1
    kind: Ingress
    metadata:
      name: dummy
      namespace:  dummy
      annotations:
        kubernetes.io/ingress.class: "kong"
        secretName: tls-test
    spec:
      rules:
        - host: mmm.app
          http:
            paths:
              - path: "/dummy"
                backend:
                  serviceName: http-svc
                  servicePort: http

The url /dummy continue to say certificat error
Need your help
Thanks

@mmaryo The secrete needs to be added in the tls section under spec and not under annotations like you have in the YAML you'v posted.
Also, please ensure the certificate is a valid and signed by a public CA.

thanks @hbagdi I correct that
In summary, today I do :
1/
kubectl apply -f https://bit.ly/kong-ingress
2/
kubectl -n dummy create secret tls tls-test --key *.mmm.app.key --cert  *.mmm.app.chain.pem
3/
Then add an application
  apiVersion: v1
  kind: Namespace
  metadata:
    name: dummy
  ---
  apiVersion: v1
  kind: Service
  metadata:
    name: echoserver
    namespace: dummy
  spec:
    ports:
      - port: 80
        targetPort: 8080
        protocol: TCP
    type: NodePort
    selector:
      app: echoserver
  ---
  apiVersion: extensions/v1beta1
  kind: Deployment
  metadata:
    name: echoserver
    namespace: dummy
  spec:
    replicas: 1
    template:
      metadata:
        labels:
          app: echoserver
      spec:
        containers:
          - image: gcr.io/google_containers/echoserver:1.4
            imagePullPolicy: Always
            name: echoserver
            ports:
              - containerPort: 8080
  ---
  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name: echoserver
    namespace: dummy
    annotations:
      kubernetes.io/ingress.class: kong
  spec:
    tls:
      - hosts:
          - mmm.app
        secretName: tls-test
    rules:
      - host: mmm.app
        http:
          paths:
            - path: /dummy
              backend:
                serviceName: echoserver
                servicePort: 80

4/ Try to ping server with curl
curl -XGET http://mmm.app/dummy
{"message":"no Route matched with those values"}
-> Why ? Everything seems good
4/ With https
curl -XGET https://mmm.app/dummy
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.```

6/ I tested my certificat :
`openssl s_client -connect mmm.app:443 -tls1_2`

CONNECTED(00000003)
depth=0 C = US, ST = California, L = San Francisco, O = Kong, OU = IT Department, CN = localhost
verify error:num=18:self signed certificate
verify return:1
depth=0 C = US, ST = California, L = San Francisco, O = Kong, OU = IT Department, CN = localhost
verify return:1
Certificate chain
0 s:/C=US/ST=California/L=San Francisco/O=Kong/OU=IT Department/CN=localhost
i:/C=US/ST=California/L=San Francisco/O=Kong/OU=IT Department/CN=localhost
...
-----END CERTIFICATE-----
subject=/C=US/ST=California/L=San Francisco/O=Kong/OU=IT Department/CN=localhost
issuer=/C=US/ST=California/L=San Francisco/O=Kong/OU=IT Department/CN=localhost

-> Why O=Kong ??

@mmaryo Can you please curl the following endpoint on Kong's Admin API: curl http://localhost:8001/snis and post the output here. Do you see mmm.app registered as an SNI in Kong?

thanks @hbagdi
To requete Kong Admin I forward port to localhost :
➜  kubectl port-forward service/kong-ingress-controller 8001:8001
Forwarding from <IP_ADDRESS>:8001 -> 8001
Forwarding from [::1]:8001 -> 8001
Handling connection for 8001
➜  curl http://localhost:8001/snis
{"next":null,"data":[]}%
Is it wrong ?

@mmaryo It seems like you are probably running into the same bug as #285 which is now fixed and will be available in the next release.

thanks @hbagdi
do you know when next version will be release ?

I'm not sure yet.
We have a couple of bugs to fix.
0.5.0 will be in some time in June, we might be able to do 0.4.1 with the bug fixes later this month.


ScreenSharing doesn't work on Ubuntu 16.04

My Setup

My OS name and version: ubuntu 16.04/unity
My current app version: 2.7.0

[x ] I have tested with the latest application version
[ ] I can simulate the issue easily

Description

Current Behavior

I cant choose every screen/ one screen/application and after i start i sometimes see my own screen but never everyone else.
So Bugs are:

Preparation window is empty
Screenshare doesnt get sent to others.
Screenshot:

If you wanna help directly, join my channel at https://crypto.rocket.chat
Cheers
Crazysoldier

Same behavior on OSX 10.11.6 w client v.2.8.0

We are facing the same Problem.
System: Ubuntu 16.04 with v.2.8.0.
Inbuild WebRTC gives me the Message "ScreenSharing Extension needs to be installed" ..
Jitsi-Meet WebRTC doesn't show me any Windows to share.

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


Update data-factory-build-your-first-pipeline-using-editor.md

fix typo

Hi @johnbooze, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Fix the missing "-cert" suffix when applying SSL certificates in rabbitmq-ha chart

What this PR does / why we need it:
https://github.com/kubernetes/charts/blob/master/stable/rabbitmq-ha rabbitmq-ha chart does not use the certificates and keys set up in rabbitmqCert section. This PR fixes the missing certificate -cert suffix.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
There is no existing issue for this PR.
Special notes for your reviewer:
cc @etiennetremel
This change has been tested in my local environment.

/assign @sameersbn

/ok-to-test

/assign

/lgtm


[Request] Self-sizing (auto layout) cells for Pinterest layout

Hello!
I noticed in the Pinterest layout that a delegate method is called to ask the cells how tall they should be based on their content. Is there a way to work with cells that self-size using Auto Layout? This would be really useful for cells that have dynamically sized content like text.

Hello,
That is a good question!
In order to answer it, we need to take a look at how self-sizing cells work for UICollectionView. In WWDC 2016 video session 219 : What’s New in UICollectionView in iOS 10 Apple says that there are 3 options for self-sizing cells, one of them is what you mentioned (using Auto Layout).
For instance, in cases when we have UILabel that may have undefined number of lines and font size, we obviously don't know the size of a cell in advance. We need to calculate it. This means that the intrinsicContentSize of a multiline UILabel cannot be determined from its content alone, as well as cell's size, since it depends on intrinsicContentSize. In order to solve such an issue, we need to either define width or height. Usually, we define width, so the height can grow and be determined at runtime. That is why in Pinterest layout implementation the delegate method returns the height, which allows the cell to be auto-sized based on run-time requirements.
In cases when we have completely dynamic content and don't know anything ahead of time, we need to implement callbacks that will check for content as soon as it's available during the run-time and delegate the heights to the layout. Then, sum up the heights in prepare method, so the final cell's height can be calculated correctly and everything can fit. That is a solution #1 and some cases it's preferable, but in some cases it's hard to properly implement.
Another solution for dynamic text is to get rid of any predefined heights (as it's done in the Pinterest layout), then remove UIStackView (I'm not saying that it's a must, just for this case) and add missing constraints for vertical and horizontal constraints, relative to the UIImage and the neighbour UILabel components. Then call sizeToFit in awakeFromNib so the size of the UILabel can be adjusted accordingly when the contents have changed. Here is the example of Pinterest layout but with dynamic and multiline text :

Font sizes have grown and can be dynamically changed, if you compare this screen shoot with the previous one that has completely different font size:

I hope, I did understand you right and it will help you! 😉

This was extremely helpful. Thank you!

your images is static can you help me for download image from server..When i download image from server than it is look like this https://i.stack.imgur.com/wErOM.png

What you mean is that the images are in app's bundle, rather than in a remote server (by referring to it as static). However, having images in a remove server has nothing to do with layouts, since those are two completely different tasks.
You need to figure our how to download images, cache them, prepare low-res previews and wire then up with a collection view instance (and make everything asynchronous). You may have different layouts and my previous message fully explains how to achieve self-sizing in UICollectionView. Please, read it thoroughly and check out the WWDC sessions.


Basic e2e test setup

We've had a couple of bugs by now that would have been caught by a simple e2e tests. The suggested setup for a test like this in CI:

setup minikube
setup parca
setup parca-agent
do a gRPC range query across all of time to ensure some data is successfully returned

Once we have this setup we can extend it wit things like #190.

One more thing to check:

Pinned rust-nightly works on both x86 and arm64

(note I think that's a follow up, but one that depends on e2e tests being in place)


npm and nodejs prereq missing in codelab Overiew page

https://codelabs.developers.google.com/codelabs/firebase-web/#3
This page says:
To install the CLI you need to have installed npm which typically comes with NodeJS.
This should be mentioned as a prereq in the What you'll need section on the Overview page.
https://codelabs.developers.google.com/codelabs/firebase-web/#0
Otherwise, the learner has to spend several minutes updating XCode and installing nodejs in the middle of the codelab.

Good call, added.


Update allowedPeers.mainnet.ts

Motivation
Describe why this issue should be fixed and link to any relevant design docs, issues or other relevant items.
Change Summary
Added my peer
Merge Checklist
Choose all relevant options below by adding an x now or at any time before submitting for review

[ ] PR title adheres to the conventional commits standard
[ ] PR has a changeset
[ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore)
[ ] PR includes documentation if necessary.
[ ] All commits have been signed

Additional Context
If this is a relatively large or complex change, provide more details here that will help reviewers

PR-Codex overview
This PR focuses on adding a new peer to the allowedPeers list in the mainnet configuration file.
Detailed summary

Added a new peer 12D3KooWMnBM89F4hyWSQJJuQtRaS4YXKvhsXsZ49bfvRCgv8Msf to the allowedPeers list in the mainnet configuration file.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

The username doesn't match a known farcaster username. We need to have this so that we can reach out to you in case we need to debug.
Please make a new PR in the allowlist-mainnet repo  with the correct username to get this merged: https://github.com/farcasterxyz/allowlist-mainnet


API Keys: add constants for warning and error messages

Completes comms sync AK-59
Summary:
Add constants in _security.py with steady-state error messages and rollout phasing warning messages, so they're all in one place.
Prerequisites:

[x] Merging against the api-keys branch
[x] Branch is up-to-date with the branch to be merged with
[ ] ~Build is successful~ intentionally nonbuilding; these constants still need to be threaded through the printer logic in place of API_KEY_WARNING_TEXT
[ ] Code is cleaned up and formatted

Open question: Do we want

KEY_REGISTRATION_FORM
TEMPORARY_KEY
CONTACT_POINT

to be hard-coded or read from environment variables?

Added manually in order to avoid conflicts.


[incubator/aws-alb-ingress-controller] Add volumes/volumeMounts option to aws-alb-ingress-controller

Signed-off-by: cw-sakamoto<EMAIL_ADDRESS>
What this PR does / why we need it:

I use kube-aws-iam-controller for attach iam role to application
This tools needs volumes and volumeMounts, so I add volumes/volumeMounts option

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

@M00nF1sh Thanks for maintenance of this charts! Please review this PR.

@cw-sakamoto Hi, thanks for making this change.
But I wonder is the 'meta/aws-iam' ever going to work?  since the controller will looks for credentials from ec2MetaData / environment variables.
If you want to assign roles to controller, you should be able to use kube2iam or kiam.  And we are working on a IAM solution based on serviceAccount.

@M00nF1sh Thanks for your comment!
It is possible to use a credential file by using environment variables(AWS_SHARED_CREDENTIALS_FILE) as well. I confirmed with this PR that it works with this settings.yaml.
extraEnv:
  AWS_SHARED_CREDENTIALS_FILE: /meta/aws-iam/credentials

volumeMounts:
  - name: aws-iam-credentials
     mountPath: /meta/aws-iam
     readOnly: true

volumes:
  - name: aws-iam-credentials
     secret:
       secretName: alb-ingress-controller-role

you should be able to use kube2iam or kiam. And we are working on a IAM solution based on serviceAccount.

Sure, kiam/kube2iam is useful tool, and we used to use kiam. but we troubled this problem with kiam/kube2iam some times, now we use kube-aws-iam-controller.
This tools is secrets controller for aws iam role credential with sts:assumerole,so the issued credential has an expiration time, it is the same as kiam/kube2iam.

@M00nF1sh
I think that volumeMounts/volumes itself is a common option, so can I delete the comments for kube-aws-iam-controller from values.yaml?

@M00nF1sh Hey! Thanks as always for providing the world's greatest cloud ☺
Just wanted to chime-in to express that I wish PRs like this to get merged to any charts related to AWS IAM.
I have some experience maintaining multiple K8s clusters on AWS myself, and heard from various experiences from kube-aws users while maintaining the project.
That being said, practically, EC2 Metadata Service or it's proxy(kube2iam, kiam) turned out to add more latencies and give us less availability compared to "local files" containing AWS credentials. And that's exactly kube-aws-iam-controller provides :)
Not saying kube2iam or kiam, or even your serviceaccount-based solution, is bad. They are/would be actually great tools. I've used both kube2iam and kiam in production for years.
It is just that focusing on latencies and availability, kube-aws-iam-controller seems superior to me(and maybe @cw-sakamoto). In other words, a PR like this allows us to use AWS IAM better in some regards.

@mumoshu @cw-sakamoto
This seems the only usecase for volume mounts, and for such use case,  I would suggest use the following instead(which uses k8s's downwards API):
- name: AWS_ACCESS_KEY_ID
   valueFrom:
   secretKeyRef:
         name: aws-secret
         key: key_id
         optional: true
- name: AWS_SECRET_ACCESS_KEY
   valueFrom:
   secretKeyRef:
          name: aws-secret
          key: access_key
          optional: true

BTW, I don't recommend to use fixed credentials like that:
1. it's not secure to store aws credentials as secret(wrong RBAC configuration will leak it)
2. it's generally a best practice to use IAM role instead of IAM user(static credentials without rotation is bad)

@M00nF1sh Hey! Thanks for your response.

I don't recommend to use static credentials like that

Definitely! That's why we might want to use kube-aws-iam-controller 😄
The controller periodically fetch temporary AWS creds, writes it to K8s secret, and ROTATEs it. K8s "periodically" syncs the secret to the volume so that you can have the good latency and reliability of the creds on local disk, while rotating creds for security.

So with kube-aws-iam-controller,

it's not secure to store aws credentials as secret(wrong RBAC configuration will leak it)

That's true, but kube2iam and kiam suffers from other type of misconfigurations like wrong "namespace" annotation(they use it to limit to role access per k8s ns), or even wrong pod annotation(you can't restrict annotation by RBAC) leaks creds! So kube-aws-iam-controller can be better in regard to your point on RBAC misconfigs.

it's a best practice to use IAM role instead of IAM user(static credentials without rotation is bad)

kube-aws-iam-controller uses IAM role :) It assumes IAM role to obtain temporary creds, and that's the same as kube2iam and kiam.

@M00nF1sh
Could you confirm this PR...?

@M00nF1sh
Could you confirm this PR...?

Hi, I'm good to approve this CR.  As I can see the prow is using similar mechanism to mount AWS Secrets: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-aws/sig-aws-credentials.yaml#L20
But I'm not sure if the secretKeyRef can handle this case as well, mainly whether it can handle credentials rotation. haven't got time to test it out yet.
like the way i commented above:
- name: AWS_ACCESS_KEY_ID
   valueFrom:
   secretKeyRef:
         name: aws-secret
         key: key_id
         optional: true
- name: AWS_SECRET_ACCESS_KEY
   valueFrom:
   secretKeyRef:
          name: aws-secret
          key: access_key
          optional: true

@M00nF1sh Thanks for your reply!

if the secretKeyRef can also handle credentials rotation,

I have tested this method but environment value not change for credentials rotation...

/lgtm

@M00nF1sh Sorry for being intrusive! But thanks again for maintaining the chart :bow:


feat: update query param on issues tab url based on search query

Issue :

https://github.com/Real-Dev-Squad/website-status/issues/971

Description :

This pull request introduces the efficient representation of search query by updating it as query param on the issues tab address bar.

Code Changes :

utils/getQueryString.test.tsx : Efficiently handles the processing of search query in both the cases where there is a query string and where there is no query string i.e no value passed.
issues/index.tsx : If 'dev' is set to 'true', we update the URL by appending the 'q' parameter with a search prefix for a more meaningful URL structure. Additionally, we split and extract relevant search information from the URL query, so as to fetch issues correctly.
tests/Utils/getQueryString.test.ts : Provided test cases cover both empty and non-empty search queries, ensuring that the getQueryString function behaves as expected in all scenarios.

Anything you would like to inform the reviewer about:
Dev Tested :

[x] Yes

Test Stats :

Images/video of the change :
https://github.com/Real-Dev-Squad/website-status/assets/53934353/912014f6-e8e5-4b53-af03-d74bc3364146
Follow-up Issues (if any) :

The query should persist in the search bar after sharing.
The API should be search?q=dark%20mode or  search?q=dark+mode (That's what Google use)

Thankyou for pointing this out, I will persist the search query in search bar.
Coming to your second point I have constructed the query param as per discussion with @ankushdharkar, here is the screenshot for the same :

-So for issues it should be /issues?q=<some-key>%3A<dynamic-string>
Example : q=search%3Adark+mode

Please add tests for your feature.

The query should persist in the search bar after sharing.
The API should be search?q=dark%20mode or  search?q=dark+mode (That's what Google use)

Thankyou for pointing this out, I will persist the search query in search bar.
Coming to your second point I have constructed the query param as per discussion with @ankushdharkar, here is the screenshot for the same :

-So for issues it should be /issues?q=<some-key>%3A<dynamic-string>
Example : q=search%3Adark+mode

For this case, it looks good.

You haven't added a test case to verify whether the changes are actually reflected in the search URL or not when the input field is changed.

Done.

The search should show closest suggestion of query EX - If user search Dark mod missing e, the result should show for dark mode currently it is showing the exact value to query

Hello, regarding this comment of yours Gaurav : https://github.com/Real-Dev-Squad/website-status/pull/989#pullrequestreview-1724069975
The issue we are addressing in this task is only to update query params, the comment that you have put is out of scope for this issue.
Here is the issue link, acceptance criteria has been mentioned very clearly :
https://github.com/Real-Dev-Squad/website-status/issues/971

The search should show closest suggestion of query EX - If user search Dark mod missing e, the result should show for dark mode currently it is showing the exact value to query

Hello, regarding this comment of yours Gaurav : https://github.com/Real-Dev-Squad/website-status/pull/989#pullrequestreview-1724069975
The issue we are addressing in this task is only to update query params, the comment that you have put is out of scope for this issue.
Here is the issue link, acceptance criteria has been mentioned very clearly :
https://github.com/Real-Dev-Squad/website-status/issues/971

If the behaviour is same, after making your changes then it's fine.


New UX for custom role system + Feature Spec for create_a_role

 Issue by chriskacerguis
Wednesday Jan 21, 2015 at 15:00 GMT
Originally opened as https://github.com/projectjellyfish/ux/issues/100

We need to add a custom role system.  This should be accessible to admins only.
Ties with core issue: https://github.com/projectjellyfish/api/issues/100

This is done with the groups.


Fixed the issue with log level on the chef config

Description

In the chef config, there are two different options to set the log level. One is the log_level and the other is the verbose. The verbose has more preference, meaning that if it is set, it will overwrite the log_level based on the verbosity level.
Currently, If the verbosity is not set, the code will default the log_level to warn even if the user specifies a different log_level on the config.rb or the credentials file.
This PR will update that flow so that, if the verbosity is not set, it will use whatever value is already set on the log_level and if that is nil, it will default to warn.
Related Issue

Types of changes

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

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@nikhil2611 can you take another look at the specs, there are still failures