Feature Request: Parameterize API name in extractor

Scenario
Can we parameterize api name which will be a boolean parameter.
This will help us to create multiple api instances of the same api inside single api management instance
Proposal
No response
Describe alternatives you've considered
No response
Additional context
No response
Contact Details
No response

I'm not sure I understand the requirement.  How would you use this in a practical scenario?

I have a scenario in which i want to create two apis using same arm templates one for prod and other for staging inside same apim instance. So the only difference here is when i deploy this templates the back-end id data will be different.
This scenario is similar to slots feature of function app.

Got it - the problem we have is that when we extract a lot of APIs, each API will be extracted with its own parameter, which will lead to a large variable pollution in the parameters.
I think this only works when extracting a single API.  Would that be your view as well?

yes correct.

This project is now in "maintenance" mode. This means that no new features will be accepted and fixes will be limited to security fixes. We expect to retire the DevOps Resource Kit by the end of 2023. At that time, the DevOps Resource Kit repository will be archived and there will be no further updates.
While you are free to fork the DevOps Resource Kit yourself, we recommend that you migrate to the following products:

If you are using creator, switch over to using Bicep templates. Bicep is a descriptive language for describing infrastructure, fully supports all features of Azure API Management, and is covered in any support agreement that you have with Azure. You can find bicep modules and examples for handling API Management APIs at https://github.com/azure-samples/api-management-sample-apis.
If you are using extractor, switch your pipelines to use APIOps. APIOps applies the concepts of GitOps to API deployments. It is faster and more flexible than the DevOps Resource Kit.


Test failure: KeepAliveHandlerTest

KeepAliveHandlerTest > [1] connectionIdleTimeout=2000, pingInterval=0, mode=CONNECTION_IDLE FAILED
    java.lang.AssertionError:
    Expecting <AtomicInteger(1)> to have value:
      <0>
    but did not.
        at com.linecorp.armeria.internal.common.KeepAliveHandlerTest.testKeepAlive(KeepAliveHandlerTest.java:295)

KeepAliveHandlerTest > shouldNotWritePingIfConnectionIsActive() FAILED
    java.lang.AssertionError:
    Expecting AtomicInteger(1) to have value:
      0
    but did not.
        at com.linecorp.armeria.internal.common.KeepAliveHandlerTest.shouldNotWritePingIfConnectionIsActive(KeepAliveHandlerTest.java:287)

Marked it as @Flaky and we're not seeing the failure anymore.


Linux Runtime 'RUBY|2.7' is not supported.

Linux Runtime 'RUBY|2.7' is not supported.Run 'az webapp list-runtimes --os-type linux' to cross check

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: b9d5437c-5b4f-bf5b-4877-e810d5fefb4f
Version Independent ID: eea67277-74ba-c23c-bee5-af4cf6eb14db
Content: Quickstart: Create a Ruby app - Azure App Service
Content Source: articles/app-service/quickstart-ruby.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@NeilAllen
Thanks for your feedback! We will investigate and update as appropriate.

The original URL is now pointing to a tutorial on how to deploy a Ruby app using custom containers.
Support for Ruby has ended on April 12th, 2023 as announced here.
#please-close


Translations

Hi,
Would be cool if you could create a public repository where you store the documention in order to let people contribute to the documentation by translating the content in various languages or simply by fixing a typo.
I can translate the documentation in English and in French.

Hi,
thanks - good idea - will work on that within the next week :)
Greetings


MahApps.Metro.Demo Build issue

MapApps.Metro.Demo won't build due to package issues with .NET4
Using VS 2017 l5.7.5
Clone MahApps.Metro develop
Expected behavior
builds ok
Screenshots

Environment(please complete the following information):

Latest develop branch
OS: Win10 10.0.17134
Visual Studio 2017 15.7.5
.NET Framework 4.7.2

The issue is fixed by removing the dependency on .NET 4 in the demo.csproj

Closed by #3317


feat: Add knowledge retrieval in Appsmith AI

Description
Frontend Changes

Remove Appsmith AI Query as a default datasource query
Add Appsmith AI Datasource in the AI section of Datasources screen
Creation of Appsmith AI datasource to mimic the mock datasource flow. This was necessary because we are using a trigger in the datasource edit form and inorder for the trigger to function the datasource needs to be created before the trigger call. (We are using the plugin trigger to upload files and hence this change is not required anymore)
Add a new Form control element to support multiple file uploads. The multiple file upload control type can either upload the files to the trigger end point (multipart-form trigger api) or save the files as base64 string in the datasource configuration. If the files are uploaded in the trigger, only the file metadata (name, size, mimeType and id) is saved in the datasource configuration.
Fix a bug in Dropdown control. This fix makes sure that the options that are disabled as infact disabled on the UI.
Add preview for the new Multi file picker control type.

Backend Changes

Add a new trigger end point for datasource to support multipart form data
Add trigger for Appsmith AI datasource to upload files during datasource creation/edit flow
Associate the file ids with the datasourceId in AI Node server
Add Knowledge retrieval implementation in text generation action for Appsmith AI datasource
Add form.json for Appsmith AI Datasource
Add a fetch files trigger for populating the files in the Text generate action.

Media

A video or a GIF is preferred. when using Loom, don’t embed because it
looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

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 not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also
list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features
Introduced a multiple file picker control for users to select and upload multiple files with options for file types and size limits.
Added new AI Query functionality with enhanced file upload capabilities, including timeout settings.
Enhanced datasource editor to display the number of uploaded files or a message if no files are uploaded.
Bug Fixes
Simplified the logic for showing the datasource selector by removing specific conditions related to the Appsmith AI Plugin.
Refactor
Removed unused imports and functionalities related to Appsmith AI across various components.
Updated plugin handling to dynamically determine button text based on plugin type.
Chores
Implemented backend support for file upload and association with datasources and workspaces.
Added new utility functions and DTOs for handling file uploads and AI plugin interactions.
Documentation

No visible changes to end-users.

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Add a TL;DR when description is extra long (helps content team)
Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

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 not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/build-deploy-preview skip-tests=true


Add overload function for sklearn to deal with sparse matrices

Got in the situation where I used some rescaling with StandardScaler and numpy arrays, and pylance kept saying me that the output was possibly a sparse matrix.
I added overload for functions and classes in sklearn/preprocessing/_data.pyi to indicate that the output of those functions is only sparse when the input is itself sparse (up to some details, depending on the functions).

@microsoft-github-policy-service agree

@ClementPinard, thanks for your contribution! There were a couple issues with the return_norm parameter on normalize. I fixed them and added tests.


System::set_code is unsafe

I think this should be considered a runtime execution indeterminism in System::set_code. This happened recently in production on the Kulupu blockchain.
Consider a situation where the wasm engine is updated to expend its supported formats, and a runtime update is activated with code of the new format. The network still contains updated, and non-updated nodes.

For updated nodes, everything still works expected.
For non-updated nodes, it calls System::set_code.

Internally, it calls can_set_code and try to compile the module for once.
However, as the old engine cannot parse the module, it errors out.
The dispatchable, however, succeeds. And it would assume the upgrade was not successful and continue on.

From there, we just have old and new nodes both successfully executes one single block, with different results, and both consider themselves correct. The old nodes will continue to sync (and build blocks, if they are validators). The new nodes will continue to sync and build blocks. However, they are now on different chains. In addition, there's no way for the old nodes to reorg to the other side of the split, even if now they update their nodes, unless they completely purge local data and re-sync.
We just broke one of the most important invariants of online upgrade here -- old nodes didn't stop building and following the incorrect chain, but just continued on. This is actually worse than a hard fork, because in a hard fork situation when one updates the node it will at least suspend following the wrong chain (although it still can't easily revert back to the right one without re-sync).
I would recommend we just remove can_set_code check. In a production environment, you'd expect ecosystem users to check their runtime well in advance anyway. Alternatively if we still want to keep that check, we should discourage usage of System::set_code, and ask everyone to use System::set_code_without_checks unless they understand the safety issues related to the former.

a runtime update is activated with code of the new format.

What is a new format? No wasm anymore?

* Internally, it calls `can_set_code` and try to compile the module for once.

This is not 100% anymore. If the wasm file contains the runtime version section, we will not compile it anymore.

@bkchr The recent change is about the compression I think. Unless we guarantee in the future that we never again extend the format, there is the possibility that this happens again.

If the wasm file contains the runtime version section, we will not compile it anymore.

Even if the wasm file is simply parsed, if the older nodes do not understand the new format, the effect is the same. To work around this, we need to have a "guaranteed" wrapper format that stores something like (version, inner_bytes), but I just don't see the point of doing that given we can simply remove can_set_code to avoid those problems altogether.

@bkchr The recent change is about the compression I think. Unless we guarantee in the future that we never again extend the format, there is the possibility that this happens again.

So your problem is that you tried to apply a compressed runtime upgrade while not all nodes supported the compressed runtime?
And no, we now support to add the runtime version as a custom section in the wasm file.

So your problem is that you tried to apply a compressed runtime upgrade while not all nodes supported the compressed runtime?

I guess that's one of the problems. One of the very points of having online upgrade / forkless upgrade is that we don't have to ask all nodes to update months or even years in advance and thus things can evolve rapidly. At the least when the interface changes, old nodes ought stop syncing but not fork into their own splits. None of our codebase should break this invariant.
Guess we can also be explicitly clear -- we tell ecosystem users they are effectively conducting hard forks (and should be treated as so) when certain Substrate commits / releases are introduced / applied.

This situation is actually worse than a hard fork. In a hard fork, when an old node updates to new version after the activation date, it can at least sense that something is wrong and from that point, stop syncing. However, for the current code, the old node, when updated, will act as if nothing has happened and continue to, without any problems, sync the split chain, because it believes that the runtime is still of the old version.

And no, we now support to add the runtime version as a custom section in the wasm file.

I just want to generally comment on this as well. The issue is not that we use one particular format or another. The issue is an extensible format. If you say, we're just going to freeze the format like this forever and ever. That is okay, and that solves the problem. But it's more likely we'll want to extend the format again in the future, either because we want to incorporate new WebAssembly features or add in something specific for Substrate. Then the issue will come again.
This is also relevant to the contracts module as well (although that's not the point of this issue). EVM had a lot of issues when it tries to update its format because of all sorts of backward compatibility issues. A part of it also happens like this when formats got extended, while things were already deployed. We need to make sure our codebase does not contain pitfalls like this, otherwise two or three years later we'd repeat all the sufferings the EVM community has already suffered from.


Question about experiment setting in the paper

Hi Antoniou !
I cannot understand the following statement in your paper.

The real or fake label was also passed to the network

It means that adding one extra class "fake" to final layer of CNN?
Thank you!

Nope. It means that we condition our classifier on both a data-point X, and a one-hot vector that indicates whether X came from the real or fake distribution. This way the classifier can create separate boundaries for each type of data-point.

Thank you for quick reply!
Now everything is clear!


Please tell me how to properly handle stdio

Describe the bug
I'm developing a plugin using wazero and I'm trying to use stdio to exchange data between host and plugin.
However, I noticed that the behavior of Read was different from that of a normal Go program.
Normally, Read blocks until calling Write syscall, but when I run the plugin using wazero, it always seems to receive io.EOF .
Similarly, when I call Write API for os.Stdout on the plugin side, it could not be Read properly on the host side.
To Reproduce
I prepared example repository to reproduce this issue.
https://github.com/goccy/wazero-example
Plugin code is here.
package main

import (
	"bufio"
	"fmt"
	"os"
)

func main() {
	reader := bufio.NewReader(os.Stdin)
	for {
		content, err := reader.ReadString('\n')
		fmt.Fprintf(os.Stderr, "content = %s. err = %v\n", content, err)
	}
}

Host code is here
package main

import (
	"bytes"
	"context"
	_ "embed"
	"fmt"
	"os"

	"github.com/tetratelabs/wazero"
	"github.com/tetratelabs/wazero/imports/wasi_snapshot_preview1"
)

//go:embed plugin.wasm
var wasmFile []byte

func main() {
	ctx := context.Background()
	cfg := wazero.NewRuntimeConfig()
	r := wazero.NewRuntimeWithConfig(ctx, cfg)

	builder := r.NewHostModuleBuilder("env")
	wasi_snapshot_preview1.NewFunctionExporter().ExportFunctions(builder)
	if _, err := builder.Instantiate(ctx); err != nil {
		panic(err)
	}

	wasi_snapshot_preview1.MustInstantiate(ctx, r)

	mod, err := r.CompileModule(ctx, wasmFile)
	if err != nil {
		panic(err)
	}
	stdin := bytes.NewBuffer([]byte{})
	stdout := bytes.NewBuffer([]byte{})
	modCfg := wazero.NewModuleConfig().
		WithStdin(stdin).
		WithStdout(stdout).
		WithStderr(os.Stderr)

	if _, err := r.InstantiateModule(ctx, mod, modCfg); err != nil {
		panic(err)
	}

	fmt.Fprintf(os.Stderr, "write buffer\n")
	if _, err := stdin.Write([]byte("hello world\n")); err != nil {
		panic(err)
	}
}

Expected behavior
I expect the plugin's fmt.Fprintf to be called only once, but in fact it is called constantly.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the relevant information):

Go version: 1.21.0
wazero Version: v1.7.0
Host architecture: Darwin mc-XJK92G53P9 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000 arm64
Runtime mode: compiler

Additional context
Add any other context about the problem here.

I think that's because you are plugging stdin to a buffer. If you need blocking behavior you can plug os.Stdin, or os.Pipe

@evacchi Thank you for your advice !! I've fixed my example according to your advice, as a result, It's working correctly !


test: clean up ConfigManagement in e2e test

If either of the migrate tests fail early, the ConfigManagement object may be left lingering on the cluster. This will cause the Create call to fail for subsequent executions of these tests on the cluster, because the config-management object already exists.

/assign @nan-yu

/retest


Docs correction

This PR has a goal of restructuring our docs with correction of language/structure to make it more clear an easy to understand

I have read the CLA Document and I hereby sign the CLA

Jenkins please retry a build

Jenkins please retry a build


Move error messages into resource files

Moving string literal error messages discovered in #2752 into appropriate resource files

:shipit: Some of the error messages in ExpressionPrinter don't seem very useful (e.g. about what you should do next) but if they're just meant for debug or are made clear by the context in which they're issued then no problem.

I believe the error messages are generally intended to be useful for debugging. We should also have a chance to revisit them in API review now that they are included in the resources.


[FLINK-4619] - JobManager does not answer to client when restore from savepoint fails

Good idea. Unfortunately, the changed broke some tests:

SavepointITCase.testSubmitWithUnknownSavepointPath
RescalingITCase.testSavepointRescalingFailureWithNonPartitionedState

You can see more in the Travis CI report.

Yes, it's a bit more tricky then I expected... These tests probably also need to be changed, because they relied on previous behaviour... What's more with the change some checks on FlinkMiniCluster start to be non-deterministic... I'll commit fixes when I'll fully understand how it works...

Hmm... I managed to make travis build pass, but I cannot see how jenkins test failures relate to my change...

@StephanEwen can I retrigger this or whatever?

No need to re-trigger this. Travis green light is good.
@uce - Do you think this works well with your latest changes?

Yes, I merge this later today.


Remove the Name property from MethodStubAPIConfiguration class

The Name property of the MethodStubAPIConfiguration class contains the name of an element from the WorkBenchServiceHttp enumeration, which is converted from within the WorkBenchServiceHttp property.
https://github.com/Avanade/Liquid-Application-Framework/blob/1d6c37c44fb5bbb6f84ba2f1d1a8a1b3d646c2ad/src/Liquid.Domain/API/StubAPIConfiguration.cs#L50-L80
We could create a new property of type WorkBenchServiceHttp instead of it being a string. By doing this, we can also remove that giant condition from the WorkBenchServiceHttp property.
Proposed solution
public class MethodStubAPIConfiguration : LightConfig<MethodStubAPIConfiguration>
{
    public WorkBenchServiceHttp Method { get; set; }
    public string Route { get; set; }
    public JToken Request { get; set; }
    public JToken Response { get; set; }

    public override void Validate()
    {
        //removed for clarity
    }
}

The first change should keep the Name property marked as Obsolete. We'll later decide on a windowframe for the removal of such properties (usually, the next major)


Testing XTable through Azure Pipelines not working

We were using Azure Pipelines for testing the project pull requests and changes.
After migration to ASF infrastructure, those triggers have stopped working.
This might not be trivial to solve and needs to be further investigated:
https://issues.apache.org/jira/browse/INFRA-17030

@vinothchandar , it seems the Hudi community has CI enabled through Azure Pipelines. Do you know whether anything changed since INFRA-17030, or had to implement a workaround?

I found the JIRA with a series of PRs: https://issues.apache.org/jira/browse/HUDI-7438
It seems there's a custom workaround in place for Azure Pipelines not having write access to the ASF repo.
I'll delve deeper into this over the next few days, any help / guidance is appreciated.

I found the corresponding documentation. I'll replicate (and document as well) a similar architecture to the one described in: https://cwiki.apache.org/confluence/display/HUDI/Guide+on+CI+infrastructure


[Column/TableCell] Add “icon-S”, “icon-M”, etc.  as options for “size” prop

Currently
The width of a Column (or TableCell) can be set via the size prop to either a fraction represented as a string (e.g. size="2/4") or as the content width (size="content"). If no size is set the column widths are distributed evenly.
Wanted
As discussed with @tar-viturawong-sociomantic, it would be useful to accept our Icon sizes in the size prop. E.g: size="icon-S" or size="icon-L".
This could be used for table layouts where we have columns that contain icons (e.g. columns containing Delete or Edit IconButtons).

@conor-cafferkey-sociomantic what is the difference here form implementing this fixed sizes or using the "content" prop? it isn't enough for this goal to use the "content"prop already implemented?

Hey @eric-martinez-sociomantic, yep fair question, my description above didn't really make that clear.
The use case is when when we want a particular column to have the the size of an icon but we don't necessarily have any content in the table cells in that column. For example:

Fruit
Quantity

Apple
2000

Orange
1500

Kiwi
15
[+]

In this example the  [+] is an icon button that places an order for more Kiwis and that icon button is only shown when the quantity is below a certain amount.


[MNT] upper bound holidays to 0.13 in soft dependencies

Resolves https://github.com/alan-turing-institute/sktime/issues/2748 by upper bounding the holidays indirect soft dependency to 0.13.

seems to work, emergency merge.


Make Jupyter Notebook changes visible on Source Control before commit

I use Jupyter Notebook extension.
As a developer/data scientist I would like to see jupyter notebook code changes when I check on source control before commit my code.

Suggestion:
Jupyter Notebook extension can preview my Jupyter Notebook in Files section when I open it, but before commit to my repo in Source Control section it can only show Jupyter Notebook file as code where I can see my changes in the file.

/extJupyter
you are now currently using the custom editor version of Jupyter notebook, there is a bug on their side which blocks you from seeing the diff editor.


Azure Monitor Diagnostic Settings Export Schema Missing

Hi, I noticed there is nowhere mentioned here how the metrics are exported to the Azure Event Hub. By that I mean the format of the data received in the Event Hub, its Schema. It is documented for other kinds of Events like it is for resource logs: https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/resource-logs-schema
But not for this. Could it be possible to add this?
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 139eae79-d3e5-8101-d6a8-ad1ca25595a0
Version Independent ID: e06704c3-5fd5-57ab-5b72-eb602ccc5705
Content: Metrics export behavior with NULL and zero values - Azure Monitor
Content Source: articles/azure-monitor/essentials/metrics-supported-export-diagnostic-settings.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @rboucher
Microsoft Alias: robb

@ismahernandez. Thanks for the feedback! We are currently investigating and will update you shortly.

@ismahernandez, this issue is being assigned to the content team for further review and update.
@rboucher, Can you please review this. The request is to document the schema of metrics being exported to eventhub, similar to what we have for resource logs here.

Work item #51255 created for this issue.

Tracking internally now at
USER STORY 51255.  #reassign:edbaynash

#reassign:EdB-MSFT

#please-close


Add JetBrains Rider

Summary
Adding JetBrains Rider as another IDE.
Went by alphabetical order. Let me know if you want it moved.

Closing for similar reasoning called out in https://github.com/dotnet/docs/pull/30684#issuecomment-1216900518


Non-docker support?

Hello, I was looking to see if this program can be used with just a python venv or with singularity.
The systems I am working on do not allow for docker/root exposure but there are requests to use alphafold in our environment. I am having trouble identifying any documentation that reveals a non-dockerized use of this software.

Hi, this is possible, it just requires more work to get things set up and we currently provide support only for running via Docker. Assuming your system has all the needed software and libraries, you can just run run_alphafold.py.
You can find more information about running under Singularity here: https://github.com/deepmind/alphafold/issues/10 and https://github.com/deepmind/alphafold/issues/24.


Error in consumer secret hashing and regenerating consumer secret

Description:
Can't generate access token after enabling hashing consumer secret feature since the consumer secret seems not generated properly when application keys are generated. No errors visible in carbon log and in the UI says "Keys generated successfully". But the UI shows option to regenerate consumer secret option.

When "Regenerate Secret" button is clicked it throws following errors in carbon.log but no errors shown in the UI.
[2022-02-09 12:00:22,531] ERROR - GlobalThrowableMapper An unknown exception has been captured by the global exception mapper. java.lang.NullPointerException: null 	at org.wso2.carbon.apimgt.impl.APIConsumerImpl.renewConsumerSecret_aroundBody22(APIConsumerImpl.java:878) ~[org.wso2.carbon.apimgt.impl_9.12.4.jar:?] 	at org.wso2.carbon.apimgt.impl.APIConsumerImpl.renewConsumerSecret(APIConsumerImpl.java:872) ~[org.wso2.carbon.apimgt.impl_9.12.4.jar:?] 	at org.wso2.carbon.apimgt.rest.api.store.v1.impl.ApplicationsApiServiceImpl.applicationsApplicationIdOauthKeysKeyMappingIdRegenerateSecretPost(ApplicationsApiServiceImpl.java:1304) ~[classes/:?] 	at org.wso2.carbon.apimgt.rest.api.store.v1.ApplicationsApi.applicationsApplicationIdOauthKeysKeyMappingIdRegenerateSecretPost(ApplicationsApi.java:395) ~[classes/:?] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_261]
Steps to reproduce:
Followed the steps in https://apim.docs.wso2.com/en/latest/design/api-security/oauth2/hashing-oauth-keys/
Affected Product Version:
Pre-Alpha APIM 4.1 pack

It seems the oauth-keys call returns the hash value of the secret. However, this is not shown properly in the UI.

Same issue reported in https://github.com/wso2/product-apim/issues/11971

Closing as the fix is merged for #11971


error while compiling

hello, i receive this error when i try to compile on windows.

it asks me for a file to patch.

You've chosen not to use any of the issue templates, which means that it is your obligation to provide as much information as possible. Please be so kind to do so.
Suggestions would be: your OS (complete), complete build log, which version of ungoogled-chromium are you trying to build, how are you trying to build it (using wchen342's scripts or how), etc…


Estimate and DimEstimate multiplication issue(s)

I can multiply a matrix by an Estimate
julia> e = Estimate(randn(5), abs.(randn((5,5))))

julia> randn((1,5)) * e
Estimate{Float64, Float64}
Estimate and 1σ uncertainty
1-element Vector{Measurements.Measurement{Float64}}:
 1.6 ± 2.0

But not an estimate by a matrix
julia> e * randn((1,1))
ERROR: MethodError: no method matching *(::Estimate{Float64, Float64}, ::Matrix{Float64})

Multiplication does not work for a DimEstimate times a UnitfulDimMatrix, either way
julia> de = DimEstimate(randn(10), abs.(randn((10,10))), (X(1:5), Y(1:2)))
julia> udm = UnitfulDimMatrix(randn(1,10), fill(unit(1.0), 1), fill(unit(1.0), 10), dims = (Ti = [1], X = 1:10))
julia> udm * de
ERROR: MethodError: no method matching Estimate

I am now realizing why it doesn't make sense to multiply an estimate by a matrix (after writing the code for it and realizing an outer product is silly)! Never mind on that one. Started an @testset for this issue

I spent an hour or two thinking about this and am giving up for the moment. Here is what I've been thinking about -
An Estimate is a vector of size (N x 1) with the associated covariance matrix of size (N x N). It can multiply any matrix of size (M x N), producing an estimate that is (M x 1) with covariance matrix that is (M x M). The multiplication of A * E, where A is a (M x N) matrix and E is an estimate of size (N x1) will be a vector where each row represents the dot product of the ith row of A with E. A way you could use this is to estimate the difference between two values at specified indices of E, by making A a row vector with 1 at one index, and -1 at the other index.
For a DimEstimate (DE), we have the same fundamental setup of a vector of measurements (N x 1) with associated covariances (N x N). However, there are now "subdimensions" - i.e., our measurements have multiple dimensions they occur along. For the case where we have measurements with dimensions (time, state variable, location), we could imagine having an array of size (T, S, L) that we call vec upon to produce the (N x 1) estimate vector. Our covariance matrix will be in this same order.
Any matrix that we want to multiply DE by will have to be of size (M x N). We could imagine making an array with one more dimension than DE, so it would have a size (M, T, S, L). We would then flatten it into a (M x N) matrix, that could be multiplied by the DimEstimate. Right now, the code wants to return a DimEstimate, but I could imagine the result actually being a DimEstimate or Estimate, depending on what the format of the array is. T, S, L definitely are dimensional quantities, but these aren't in the result.
A proposed solution I have to do this - for simplicity, let's assume that M has to be a dimensional quantity, so we want to return a DimEstimate

redefine *(F::AbstractMatrix, x::DimEstimate) to operate on *(F::UnitfulDimMatrix). Is there some type for an Abstract Dimensional Matrix? It may or may not be Unitful.
check that the second dimension of F is equal to the product of the dimensions of x. The first dimension of F will be retained
multiply together, returning a DimEstimate with the same dimensions as F

Update: the workaround I'm using right now is multiplying a DimArray by a DimArray, like this
julia> de2 = DimEstimate(randn(10), abs.(randn((10,10))), (Y(1:2), X(1:5)))
julia> de2.x * de.x

This syntax is a bit confusing, not sure what the solution is here


[HOLD for payment 2023-09-15] [$1000] Adding any invalid text/string as contact method through URL

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

Action Performed:

Go to the following link and write anything you want in "HERE"
https://staging.new.expensify.com/settings/profile/contact-methods/HERE/details
For example:
https://staging.new.expensify.com/settings/profile/contact-methods/Yooooo/details
Notice it shows a magic code validation tab
Click on resend code quickly to stay in the incorrect validation page and bypass error page.
If you don't click an error page will be thrown later

Expected Result:
It should immediately says PageNotFound and not preview Contact Validation with Magic Code sent
Actual Result:
It shows validation page with magic code and you can stay in it if you click on resend code
Workaround:
Unknown
Platforms:

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

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

Version Number: 1.3.53-1
Reproducible in staging?: yes
Reproducible in production?: yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/38435837/9e96f047-2760-4949-be1b-2ea7910222a5
Expensify/Expensify Issue URL:
Issue reported by: @MAkiour
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691207772114549
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013d8b6c25b7efa6cc
Upwork Job ID:<PHONE_NUMBER>548029440
Last Price Increase: 2023-08-21
Automatic offers:

makiour | Contributor | 26292086
MAkiour | Reporter | 26292087

Reproduced. I kind of wonder whether we should be including the specific contact method as part of the URL at all? It doesn't seem realistic that an actual user would ever need to deep link to this specific page.
And if we removed deep linking to a specific contact method, that would largely obviate this issue.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Hardcoding contact method details URL with a non existent contact method shows magic code verification for a brief amount of time before showing not found page.
What is the root cause of that problem?
The root cause of this problem is on ContactMethodDetailsPage.js file, lines 212-215:
const loginData = this.props.loginList[contactMethod];
        if (!contactMethod || !loginData || !loginData.partnerUserID) {
            return <NotFoundPage />;
        }

An existent contact method object will have a bunch of properties when created, one of them being  partnerUserID which I will use for the solution of the problem. A non existent contact method object will only have the validateCodeSent property set to false, getting it from our resetContactMethodValidateCodeSentState method.
On the above code section, we are only checking if the loginData object exists, and it does, with the validateCodeSent property I mentioned above.
This of course is not the correct check to do to determine if the contact method is found, which leads to showing the Magic Code validation page later on the code, which we show when that condition is true:
!loginData.validatedDate && !isFailedAddContactMethod, and of course, since loginData only has the validateCodeSent it becomes true.
What changes do you think we should make in order to solve the problem?
On lines 212-215 , we should add a check for partnerUserID in the condition:
if (!contactMethod || !loginData || !loginData.partnerUserID) {
            return <NotFoundPage />;
        }

https://github.com/Expensify/App/assets/32620770/2e538c28-3cc0-4c34-bad4-84b431ce2f21

Proposals pending review.

Proposals still pending review

Please re-state the problem that we are trying to solve in this issue.
Adding any invalid text/string as a contact method through URL. It goes to the magic code validation tab but it should immediately says PageNotFound and not preview Contact Validation
with Magic Code sent
What is the root cause of that problem?
When we go through the URL using an invalid string, initially it will be rendered the component and check for validation on below file:
https://github.com/Expensify/App/blob/main/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js#L245-L259
{!loginData.validatedDate && !isFailedAddContactMethod && (
<View style={[styles.ph5, styles.mt3, styles.mb7]}>
<DotIndicatorMessage
type="success"
style={[styles.mb3]}
messages={{0: ['contacts.enterMagicCode', {contactMethod: formattedContactMethod}]}}
/>
<ValidateCodeForm
contactMethod={contactMethod}
hasMagicCodeBeenSent={hasMagicCodeBeenSent}
loginList={this.props.loginList}
ref={this.validateCodeFormRef}
/>
</View>
)}

What changes do you think we should make in order to solve the problem?
To solve this issue you need to wrap up the complete component in below mentioned condition on
https://github.com/Expensify/App/blob/main/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js
<>
{!loginData.validatedDate ? (
<NotFoundPage />
) : (
<ScreenWrapper onEntryTransitionEnd={() => this.validateCodeFormRef.current && this.validateCodeFormRef.current.focus()}>
<!-- all content from page inside screen wrapper -->
</ScreenWrapper>
)}
</>

Video
https://drive.google.com/file/d/1EJ5oEk_3MTHlBjNxWxrru3-ozDweRemo/view?usp=sharing

Bumped in Slack

I kind of wonder whether we should be including the specific contact method as part of the URL at all? It doesn't seem realistic that an actual user would ever need to deep link to this specific page.
And if we removed deep linking to a specific contact method, that would largely obviate this issue.

@joekaufmanexpensify, there are legitimate use cases in theory. For example, if you want to open the current page (in this case details for a contact method) in a different browser (we do it all the time when testing PRs). Of course, this is an edge case (there are no other pages like this as far as I know) and even if we remove the deep linking, it will only add one extra click in this specific scenario, but I think we might want to fix this, even the rare cases are possible

@makiour, wow, thank you for such a thorough explanation!
I think we should proceed with option 1.1 of @makiour's proposal, which is changing
https://github.com/Expensify/App/blob/4230f289341c8d6d9a8b780d54da0725d4764b2b/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js#L110-L112
to
componentDidMount() {
    const contactMethod = this.getContactMethod();
    const loginData = this.props.loginList[contactMethod];
    if (loginData) {
        User.resetContactMethodValidateCodeSentState(contactMethod);
    }
}

I think we should also set NotFoundPage to say "Back to contact methods" instead of "Back to home" (and change the actual navigation action). If we navigate back from contact details, we should end up on the contacts page, not just dismiss the modal
🎀👀🎀 C+ reviewed!

Pending internal engineering sign off

@AndrewGable mind taking a look at this proposal when you have a sec? TY!

Bumped Andrew 1:1

@eVoloshchak mind completing the BZ checklist so we can prep to issue payment?

Thanks for bumping! I'll review, and we'll definitely take any internal delays into account when calculating whether a bonus is warranted.

Bumped BZ checklist in Slack so we can prep to issue payment soon.

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/23601
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/23601/files#r1326128384
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: I don't think an additional discussion is needed, we already have a checklist item to cover failure scenarios: I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
Determine if we should create a regression test for this bug.
Is it easy to test for this bug? Yes
Is the bug related to an important user flow? Yes
Is it an impactful bug? No
It's kind of an edge case since it requires a user to manually edit a URL with an invalid contact method, but the same can happen in case there are issues with the back end, so I think we need a regression test

Regression Test Proposal

Go to Settings > Profile > Contact Methods
Verify there is at least one contact method
Open the following link: https://staging.new.expensify.com/settings/profile/contact-methods/invalidContactMethodName/details
Verify that you're presented with 'Hmm... it's not here' page
Press on 'Go back to contact methods'
Select a contact method, verify you're navigated to an according contact method page

Do we agree 👍 or 👎

Great, ty! I'll finish up the checklist so we can issue payment asap.

Checklist is all set!

We discussed this here and confirmed this qualifies for a speed bonus. This means we need to issue the following payments:

@makiour - $1,750 ($1,000 for PR, $500 speed bonus, $250 reporting bonus). Paid via upwork.
@eVoloshchak - $1,500 ($1,000 for C+ and $500 speed bonus). Paid via NewDot.

@eVoloshchak could you please request $1,500 via NewDot and confirm here once complete?

@makiour I sent your $1,750 in two payments, since you had two roles for this one.

@joekaufmanexpensify, requested the payment!

Awesome, ty! @eVoloshchak closing this out for now. If your request hasn't been paid in 7 days LMK, and I'll look into it on my end.

Payment summary message is here.

$1,500 payment for @eVoloshchak approved based on BZ summary.


test: SCE-6 e2e tests tabilize snapshots

Parallelize tests (22mins to 8mins 🔥 credit: @rainandbare 🏆 ✨ )
Extract e2e tests into its own Github action yml file, since Chromatic tests should only be run on pull and NOT on pull_request for screenshot stability
Each Chromatic screenshot requires a UNIQUE snapshot name across the test suite. And this also ensures the screenshots work in tryUntil() block, where one or more of the same screenshot could be taken in the tryUntil block because of the retry. Additionally, a explicitly named screenshot promotes intentional screenshot and easier to debug in Chromatic UI page
Move goToPage() to cellxgeneActions.ts to avoid circular dependency
Add resizeWindow() to ensure the rendered graph is as consistent as possible across different machines. This resolves the problem where locally we could see one sets of lasso counts and in GHA we see another
Add showImageUnderlayInTestMode() to show the image underlay for snapshots that require the image underlay. This is needed because by default we no longer shows the image underlay, since it introduces instability in Chromatic snapshots if we include it in all the snapshots
Add getSnapshotPrefix(testInfo) to create a unique snapshot name based on the test name
We now crop the graph and image underlay before taking snapshots to reduce the area of image that could cause false positive diff
Remove snapshots on tests that don't need them
Increase Chromatic diffThreshold from the default 6.3% to 10%, since the default was still too sensitive for our image underlay
Test mode now doesn't show the image underlay by default to reduce Chromatic snapshot false positive rate

NOTE:

I couldn't completely eliminate the Chromatic snapshot false positives, because technically Chromatic is correct that our image underlay and image are not 100% in sync all the time. So we'll still see 3 to 9 false positives that look like the following and we can just accept them and move on for now:

Thanks so much everyone 😄 👏 🎉 !! GO TEAM!! Merginggg


Bounding Box Incorrect Scaling/Positioning after 97e92fa

So first off thanks again for the tuned performance.  I verified 12 FPS peak on the Raspberry Pi with the Realsense D435.
The thing I noticed (see videos below), is that the scaling/positioning math behind the bounding boxes after 97e92fa (here) seem to be off.
So prior to this commit, they follow me left/right in the live video feed correctly (my center, and the center of the bounding box match well), and the scale matches well too (i.e. my width/height, and the bounding box width/height match well).
After the commit, I notice the following:

The positioning is off: when object is on the left side, the position of the bounding box is too far to the left.  When the object is on the right, the center of the bounding box is too far to the right, etc.
The left/right size is also off.  The box is too large at least in the left/right dimension (and probably also up/down, it seems, but less tested).

Here's a before/correct video (from checkout 80a564cfb02afec5ee3a4ddfa9493c2e3e7d2cff):
https://photos.app.goo.gl/H5ta1X7KnqTdsz7j7
Notice that the bounding box tracks my center well and also my size well.
And here's the after/incorrect video (from checkout 055636afe67f3fb66e4aff46a16899719571038e):
https://photos.app.goo.gl/6zfMgGKaYjbrZRQZ9
Notice in this case the box is too wide (and also seemingly too tall), and goes to far left/right when the object (me) is located left/right of the video feed.
Thanks again!  I'll also try to hunt to see if I can find where this scale/position error was introduced.

So my first guess (which has a high probability of being wrong because I don't know the codebase yet) is that the image preprocessing changed.  And now it's doing this logic on the image if it's realsense:
if self.camera_mode == 0:
    prepimg = cv2.resize(color_image,(532,400))
    prepimg = prepimg[100:100+300,116:116+300]

Instead of (if I'm reading it right), the following logic:
def preprocess_image(src):

    try:
        img = cv2.resize(src, (300, 300))
        img = img - 127.5
        img = img * 0.007843
        img = img[np.newaxis, :, :, :]     # Batch size axis add
        img = img.transpose((0, 3, 1, 2))  # NHWC to NCHW
        return img

I tried replacing that logic and AFAICT (as far as I can tell) that was indeed the problem.
Below is a video of with the following logic for image_preprocessing:
def image_preprocessing(self, color_image):
        prepimg = cv2.resize(color_image, (300, 300))
        prepimg = prepimg - 127.5
        prepimg = prepimg * 0.007843
        prepimg = prepimg[np.newaxis, :, :, :]     # Batch size axis add
        prepimg = prepimg.transpose((0, 3, 1, 2))  # NHWC to NCHW

https://photos.app.goo.gl/SVqpCogZ7J234Kkp9
I did notice on this that the lag/latency is much higher, at least compared to what I remember for the NCS1/NCSDK version, and I'm not sure if it's my change above that's causing that latency.
Best,
Brandon

Watching the videos above, it seems like the latency is just as present before my change compared to after.  I'm going to upload a video of the NCS1 version for comparison WRT latency in a new Github issue, and then @PINTO0309 let me know if you want me to close this issue (the scale/position error, as it seems to just be what I found).
Thanks!
-Brandon


LFS support and minor cleanups

This fixes #52 and a few things that I noticed while working on this.

Hi Uwe,
I am getting this error:
configure.ac:408: error: possibly undefined macro: AC_SYS_LARGEFILE_SENSITIVE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
Regards,
Marcelo.

I don't see this problem, I bet that's because I have the package autoconf-archive installed. I added the necessary m4 file now, so it should also work without this installed.

Awesome!


Fixed use-after-free in ReactiveSocketTest.

@benjchristensen I "tested" whether contbuild fails when a test fails :)

All tests passed, were you expecting one to fail?

After my last commit the test was failing, this PR fixed it.

Ah nice, so it's working as we want it to.


AMBARI-25781: Fix the Zookeeper AdminServer start faild.

What changes were proposed in this pull request?
AMBARI-25781
How was this patch tested?
We can view the zoo.cfg configuration through ambari ui

Test disable Zookeeper AdminServer

Please review Ambari Contributing Guide before opening a pull request.

Thanks @ASimpleCoder ! BTW, can we add quicklink for Zookeeper AdminServer ?

Thanks @ASimpleCoder ! BTW, can we add quicklink for Zookeeper AdminServer ?
I think so too, but if we disable the Zookeeper AdminServer, it should not show up on the Ambari UI.
Currently, Ambari is not supported this feature. We need to add this new feature to Ambari.

Thanks @ASimpleCoder ! BTW, can we add quicklink for Zookeeper AdminServer ?
I think so too, but if we disable the Zookeeper AdminServer, it should not show up on the Ambari UI.
Currently, Ambari is not supported this feature. We need to add this new feature to Ambari.

Sounds great, we can create a JIRA ticket for this !


fix: pre release and solve some issue

Generate libraries.
search UI fix.
send feedback via the GitHub issue link.
Change primary colour.
FAP Add button bottom padding.
change version to 1.0.0.
check for iPad.
Cleanup localizations.
Keyboard text field issue.


Prevent requesting lock for more than 99 users

Discord restricts to lock voice channels up for 99 users. But bot currently accepts limit number argument more than 99.

Ready to fix it, bruh

Ready to fix it, bruh


Uncaught Module 'xxx' not present. (papaparse lib

I have a problem. I've installed papaparse with @types/papaparse in my app. when i fulfill  npm start everything is good, but  the server is fulfilled after  npm run serve.prod command , and there is an error (Uncaught Module 80 not present) after opening the page http://localhost:5555/
my change:
seed.config.ts
   ...
    packages: {
      'papaparse': {
        main: 'papaparse',
        defaultExtension: 'js'
      },
...

home.component.spec.ts
import * as Papa from 'papaparse'
.....
  addName(): boolean {
    // TODO: implement nameListService.post
    this.names.push(this.newName);
    var res = Papa.parse('a,bb,c,d');
    console.log(res);
    this.newName = '';
    return false;
  }

Use:
let additionalPackages: ExtendPackages[] = [{
  name: 'papaparse',
  packageMeta: {
    main: 'papaparse.js'
  }
}];

this.addPackagesBundles(additionalPackages);


"npm test" fails at the end.

npm-debug.txt
Hi,
I am fairly new to Angular2 and was trying this seed project. it fails at the end if in run "npm test".

Can someone guide, if I missing something OR is an issue.

@manish5377 would you try:
rm -rf node_modules
npm cache clean

Or the equivalent on Windows, and try again.

Thanks a lot @mgechev ...It worked....


Algorithm refactoring

Main benefits:

Analysis algorithm implementation is slightly improved. The Btag mask is built immediately after creating trijet combinations and then applied to the Trijet_p4 column at the defining stage. That's why all following after the Trijet_p4 columns are automatically btagged
Avoided all explicit loops

Produced histograms are exactly the same. I left FIXME just as reminder what should be improved. I didn't mean a bug. Maybe it was better to call it to do, but anyway I didn't mean that something is broken

Produced histograms are exactly the same as in previous PR

great! thanks for confirming!

I left FIXME just as reminder what should be improved

I see. Nevertheless, this is a public repository that ROOT users will look at as an example of how an RDF analysis should be written. The implementation should not have FIXMEs or TODOs in it: it shouldn't give the impression that it's unfinished once we tag a v1. Feel free to open GitHub issues if there are to-do items that you don't want to lose track of!

FEXME removed


Running the barys build script with --dry-run does not expose bitbake

If you execute a dry run using the script as you would expect, by running ./barys --dry-run , you cannot execute bitbake and therefore you cannot build resinOS.
This bug is caused by the fact that running a script via  ./ executes it in a new shell, isolated from the one in which the command was written. The bitbake command is exposed via source oe-init-build-env, inside the shell it is ran in. Once barys finishes executing it exits, closes the shell that was created for it, the shell in which bitbake was exposed. This results in the user not being able to bitbake anything, in spite of the fact that this is what the script suggests as the next step.
My workaround was commenting out the final line of the script, exit $EXIT_CODE , and running barys as follows: source barys. The source keyword ensures a script runs in the current environment. This means that everything the script changes about the environment remains there after the it finishes execution. Removing exit is necessary because otherwise the shell would simply quit. A more robust solution would obviously be preferred, but this is what I could hack together to get it running as intended.

Hi @tiniuclx,
Thanks for getting in contact with us. There is a misunderstanding on what --dry-run was designed to do. The intention of this mode is not to get you in a build environment but only create a build directory with configuration. It is expected that afterwards a source layers/poky/oe-init-build-env build command will be needed.
Hopefully this clarifies it.

Hello Andrei,
Thank you for your reply. I've actually been getting that impression over the past few days, after familiarising myself with Yocto and how Resin OS uses it. I still believe it would be helpful if this was stated in the documentation, or within the prompts you get while running barys .
Thanks once more for your help.

I raised a PR which should clarify this. Please take a look: https://github.com/resin-os/resin-yocto-scripts/pull/86 .

Thank you! I had a look, the proposed change would be more than enough to clarify the proper usage.

I'm glad it does @tiniuclx . Cheers!


Fixed inconsistency on the activities of application tokens

Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

I first started on the inconsistency of "of the" vs "for the", and then I re-adapted both activities to match what we are doing in other activities.

LGTM but travis is red


No specs found

I've created the starter and when it runs it shows me this error:
Error detected while processing /Users/joshmedeski/.config/nvim/init.lua:
No specs found for module lazyvim.plugins
Press ENTER or type command to continue

I've confirmed that LazyVim/LazyVim is properly installed, but this line seems to be failing.
Any ideas?

Can you delete the lazy cache? ~/.cache/nvim/lazy/cache.
That should fix it. I'm currently working on a proper fix for this.
Let me know if that works!

Yes, that was it! I've forked LazyVim and want to contribute :)


Failed to compile with clang/libc++ using shared lib mode

Environment
toml++ version and/or commit hash:  3.4.0
Compiler:  clang 17
C++ standard mode:  17, 20, 23
Target arch:  x64
Library configuration overrides:  -DTOML_HEADER_ONLY=0 -DTOML_SHARED_LIB=1
Relevant compilation flags:  -stdlib=libc++
Describe the bug
In shared library mode, Clang failed to compile C++ code using tomlplusplus with libc++.
Undefined reference errors such as undefined reference to toml::v3::ex::parse_file' are reported.
Steps to reproduce (or a small repro code sample)
To reproduce this, use the following command
echo -e "#include <toml++/toml.hpp>\nint main(int, char** argv) {auto tbl=toml::parse_file(argv[1]);}" | clang++ -x c++ -DTOML_HEADER_ONLY=0 -DTOML_SHARED_LIB=1 -ltomlplusplus -stdlib=libc++ -std=c++23 -

Additional information
It also fails regardless of the combination of linkers (lld, ld, gold, mold), the c++ standards (c++17, c++20, c++23) or whether the -fexperimental-library flag is used.
Using clang with libc++ instead of GNU stdlibc++ may be necessary on latest C++ standards due to some conflicts between clang and stdlibc++ on some standard library features.

How are you compiling the shared lib? Presumably you are using a build system? The shared lib instrumentation assumes this is the case.

How are you compiling the shared lib

The shared lib is provided by the operating system repo (Arch). It was built with meson

Was the system-provided lib compiled with libc++ too?

Probably worth pointing out that toml++'s CI uses the lib in shared mode for it's linux runners:
[7/52] Linking target src/libtomlplusplus.so.3.4.0

Methinks this is not a bug in the library, but something about the way that distro packages it, and/or your build system. Have you tried using the header-only mode directly?

Was the system-provided lib compiled with libc++ too?

No,

Methinks this is not a bug in the library,

I think you are right. There could be some conflict with the libc++ compiled project link against the libstdc++ compiled tomlplusplus shared library.
I'm probably better off making a special case for clang to compile the project with tomlplusplus in headers-only mode. Thanks for the help!

There could be some conflict with the libc++ compiled project link against the libstdc++ compiled tomlplusplus shared library.

Yes, that's absolutely the case. You're getting link errors because the two standard library implementations (rightly) use inline namespaces internally to safeguard against this sort of ABI mixing. Even if it did link, it wouldn't work - you'd get all sorts of catastropic bugs at runtime, because their internal implementations are different.

I'm probably better off making a special case for clang/libc++

Yeah, looks like that's your only option here, unfortunately 😅

Thanks for the help!

No worries :)


How to add title field in model definitions

Is it possible to add title field in the definition of a model? I would like to see something like this in generated swagger file:
definitions:
  FooResponse:
    type: "object"
    title: "Foo"

I don't believe this is possible now, without programmatic manipulation. The next version (which we're currently working on) will support it.

@webron Thank you for the quick answer. Could I also ask when I can expect the next version?

Not sure yet, we're working on it. You can track the progress on here. It also depends on the release of the next version of the spec.


Refactor the handling of locals in singlepass

Best reviewed commit-by-commit.
 I'm not actually quite sure why load and serialization performance has improved so significantly.
Still need to evaluate the impact on the runtime performance.

So, we are indeed seeing a significant regression in the runtime performance by not allocating any registers to the locals, at least as per coremark.
Before: 6159.0146; After: 5305.552.
The thing about coremark is that a number of loops that it runs heavily utilize the locals 0 to 4, so a significant portion of reads/writes ended up being pushed out into memory traffic. I'm somewhat torn over whether we should consider this a blocking regression. On one hand not allocating any locals to registers can result in significant perf drop for some workloads, and this is one of those. On another hand, it ain't gonna help average code much. I noted a couple times before, if we're going to be allocating any registers to locals, we should be running a proper register allocator which could allocate these registers in a way that isn't super naive.

I'm somewhat torn over whether we should consider this a blocking regression.
On another hand, it ain't gonna help average code much.

I'd check the latter assumption by, eg, running aurora benchmark. If it doesn't regress, let's ship it?

Uh looks like my written-in-plane code review made me miss the changes since 2h ago, I'll look into it more next week :)

Using the self-contained benchmark from aurora https://github.com/aurora-is-near/aurora-engine/pull/514
running this with the standalone runner takes:
with this patch: 740~750ms
without this patch: 690~700ms
So still ~7% regression. I guess I'll just retain the allocation of registers for now, since none of the rest of the changes actually depend on us allocating everything to stack.

Ping @Ekleog @matklad for a final look/rubberstamp?


Bump ./example to expo 49

Updated demo app with
yarn add expo@latest
npx expo install --fix
npx expo prebuild --clean

and fixed a read screen of death wot this error
 ERROR  Error: NativeViewGestureHandler must be used as a descendant of GestureHandlerRootView. Otherwise the gestures will not be recognized. See https://docs.swmansion.com/react-native-gesture-handler/docs/installation for more details.

This error is located at:
    in NativeViewGestureHandler (created by RNGestureHandlerButton)
    in RNGestureHandlerButton (created by BaseButton)
    in BaseButton (created by GenericTouchable)
    in GenericTouchable (created by TouchableOpacity)
    in TouchableOpacity
    in RCTView (created by View)

Thanks for this, but closing it because it was superseded by later changes, and expo was updated as part of those.


Currently, the dependency is not updated in the multi-project configuration using Gradle's buildSrc.

Dependabot cannot update dependencies on projects built by following the steps in Creating Multi-project Builds in Gradle's Get Started Guides.
https://docs.gradle.org/current/samples/sample_building_java_applications_multi_project.html
This is the project actually created by the above procedure. I've added the GitHub Dependabot settings to this.
https://github.com/kazuyatada/sample-gradle-multi
As a result, build.gradle cannot be detected and an error occurs.
In the configuration using buildSrc, the dependencies that are commonly used in multiple projects are described in the *.gradle files under buildSrc/src, but Dependabot does not refer to the *.gradle files under buildSrc/src. It is the cause.
I hope Dependabot will also update the *.gradle files under buildSrc/src.

Possible duplicate: #2180

Yep, this is a dupe of #2180


Check Point #1B

Roles:
Raunak: Frontend
Kevin: Backend
Isabelle: Scrum Master/Dev Ops
Individual Goals:

[ ] Add login page (Kevin)
[ ] Personalized profile page (Kevin)
[ ] Add personalized skills page (Kevin/Isabelle)
[ ] Add interview page (Isabelle)
[ ] Add page for job offers (Isabelle)
[ ] Frontend layout for pages (Raunak)

Team Goals:

Basic working website that users can post jobs/resumes on

Login System:
Backend:

Frontend:


dnsproxy: 0.35.1 -> 0.35.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AdguardTeam/dnsproxy/releases.
meta.description for dnsproxy is: "Simple DNS proxy with DoH, DoT, and DNSCrypt support"
meta.homepage for dnsproxy is: "https://github.com/AdguardTeam/dnsproxy"
meta.changelog for dnsproxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/c790842b7b57ccf31c8b5a283d0dcdf7

du listing: https://gist.github.com/1bc68e3ecbdc034b1f380b94e9f05e3d

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dnsproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/65lhb9gdmq6m6vg306gikxr4cyzwqha2-dnsproxy-0.35.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dnsproxy https://github.com/r-ryantm/nixpkgs/archive/08adf362cc45ec174ae061f2d66b99674028f23b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/65lhb9gdmq6m6vg306gikxr4cyzwqha2-dnsproxy-0.35.2
ls -la /nix/store/65lhb9gdmq6m6vg306gikxr4cyzwqha2-dnsproxy-0.35.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dnsproxy

Maintainer pings
cc @contrun @kalbasit for testing.

Result of nixpkgs-review pr 114890 at 08adf362 run on aarch64-linux 1

1 package built:

dnsproxy

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/networking/dnsproxy/default.nix:21:5:
   |
21 |     license = licenses.gpl3;
   |     ^

Result of nixpkgs-review pr 114890
./results/dnsproxy/bin/dnsproxy
the required flag `-u, --upstream' was not specified


[UPDATE] boltcards to v0.0.6

https://github.com/lnbits/boltcards/releases/v0.0.6

probably needs rebase to remove the CI jmeter failure


Branch status plan-to-watch

New Status: plan-to-watch

Codecov Report

Merging #142 (ca5862f) into master (a426892) will decrease coverage by 0.15%.
The diff coverage is 53.84%.

@@             Coverage Diff              @@
##             master     #142      +/-   ##
============================================
- Coverage     53.78%   53.62%   -0.16%
  Complexity      340      340
============================================
  Files            79       79
  Lines          1415     1421       +6
  Branches        146      149       +3
============================================
+ Hits            761      762       +1
- Misses          600      602       +2
- Partials         54       57       +3

Impacted Files
Coverage Δ

...java/seedu/trackermon/storage/JsonAdaptedShow.java
0.00% <0.00%> (ø)

.../main/java/seedu/trackermon/model/show/Status.java
63.15% <54.54%> (-21.46%)
:arrow_down:

...java/seedu/trackermon/logic/parser/ParserUtil.java
96.55% <100.00%> (ø)

Continue to review full report at Codecov.

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


[SPARK-16555] Work around Jekyll error-handling bug which led to silent failures

If a custom Jekyll template tag throws Ruby's equivalent of a "file not found" exception, then Jekyll will stop the doc building process but will exit with a successful status, causing our doc publishing jobs to silently fail.
This is caused by https://github.com/jekyll/jekyll/issues/5104, a case of bad error-handling logic in Jekyll. This patch works around this by updating our include_example.rb plugin to catch the exception and exit rather than allowing it to bubble up and be ignored by Jekyll.
I tested this manually with
rm ./examples/src/main/scala/org/apache/spark/examples/sql/SparkSQLExample.scala
cd docs
SKIP_API=1 jekyll build
echo $?

Test build #62353 has started for PR 14209 at commit cd89a2c.

Test build #62353 has finished for PR 14209 at commit cd89a2c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62353/
Test PASSed.

Merged build finished. Test PASSed.

Merging in master/2.0.


Missing QLPlugins?

Environment

App version? 1.2.0
macOS version? macOS 10.15.6 (19G73)

Bug Information

What are you trying to do?

What's the expected behavior?

I expect to see Quicklook previews

What's the actual behavior?

Several of the plugins seem to be missing, though I haven't made any changes!

I presume this isn't related? (Did Glance do this — i.e. the archived QLPlugins?)

Also having this issue.

I have the same issue as @chrismessina in the same environment. Actually it did work at first, but then this error message appeared without me having changed anything.


[$500] Web/Safari - Attachment - Drag and drop popup does not show on Safari

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

Version Number: 1.4.24-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Access staging.new.expensify.com
Sign into a valid account
Drag and attachment to any chat

Access staging.new.expensify.com
Sign into a valid account
Click on "+" > Request money > Scan module
Drag and attachment to the scan module

Expected Result:
User expects there to be a "Drag to upload" popup (Or "+" symbol for the first case) and in the second case a popup that says "Let it go - drag to up upload)
Actual Result:
No popup is shown when dragging and dropping, there is a "+" symbol but this shows ups and then after a while for no reason disappears.
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/9b614215-0a82-41ac-b96a-b5a92ec16311
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~018eedacd3a9252d63
Upwork Job ID:<PHONE_NUMBER>436111360
Last Price Increase: 2024-01-11
Automatic offers:

s77rt | Contributor | 28102162

regression from https://github.com/Expensify/App/pull/33864

@tienifr Can you please take a look at this

Thanks for jumping on it so quickly @tienifr and @s77rt!
PS I can't assign you until you comment here @tienifr.

The PR that introduced the bug has been identified: https://github.com/Expensify/App/pull/33864
The offending PR has been commented on: n/a
A discussion in #expensify-bugs has been started: Not needed
Determine if we should create a regression test for this bug: No. We have a test already https://expensify.testrail.io/index.php?/cases/view/2730088

@amyevans Please close this, no payment to handle here since it's a regression.


Introduce masking and redaction example of international IBANs

Changes

introduce example config to mask IBANs with transform processor
introduce example config to redact IBANs with redaction processor
introduce integration tests for both configs

Do we have some sort of documentation about the difference of redacting and masking? It's clear to me now, but it might be helpful to have a readme or similar that says "use either one or the other, you don't need both" or something along those lines

Not now, but I can sync with Alex regarding this and include it to the example config page, since we will probably include both examples there.


Spyder crash (after rdp install?)

From<EMAIL_ADDRESS>on 2013-02-11T04:15:18Z
Please note that reporting bugs from Spyder's help menu ("?" > "Report
issue...") will fill version details for Spyder, Python and Qt in this description for you.
What steps will reproduce the problem?

Calling spyder What is the expected output? What do you see instead? Spyder IDE window What version of the product are you using? On what operating system? Spyder 2.1.10-2 on Linux Mint Debian Edition (Debian Testing)

Please provide any additional information below
. I just install xrdp in my machine, play with remote computer, then I cannot have Spyder IDE anymore. I think it relates to port management between Spyder and rdp. This is what's shown in the terminal.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/spyderlib/spyder.py", line 2006, in main
mainwindow = run_spyder(app, options)
File "/usr/lib/python2.7/dist-packages/spyderlib/spyder.py", line 1927, in run_spyder
main.post_visible_setup()
File "/usr/lib/python2.7/dist-packages/spyderlib/spyder.py", line 953, in post_visible_setup
self.extconsole.open_interpreter_at_startup()
File "/usr/lib/python2.7/dist-packages/spyderlib/plugins/externalconsole.py", line 1092, in open_interpreter_at_startup
self.open_interpreter()
File "/usr/lib/python2.7/dist-packages/spyderlib/plugins/externalconsole.py", line 1101, in open_interpreter
interact=True, debug=False, python=True)
File "/usr/lib/python2.7/dist-packages/spyderlib/plugins/externalconsole.py", line 851, in start
shellwidget.start_shell()
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/baseshell.py", line 232, in start_shell
self.create_process()
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/pythonshell.py", line 411, in create_process
introspection_server = introspection.start_introspection_server()
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/introspection.py", line 106, in start_introspection_server
INTROSPECTION_SERVER = IntrospectionServer()
File "/usr/lib/python2.7/dist-packages/spyderlib/widgets/externalshell/introspection.py", line 37, in init
self.port = SPYDER_PORT = select_port(default_port=SPYDER_PORT)
File "/usr/lib/python2.7/dist-packages/spyderlib/utils/misc.py", line 57, in select_port
sock.bind( ("<IP_ADDRESS>", default_port) )
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
OverflowError: getsockaddrarg: port must be 0-65535.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1262

From ccordoba12 on 2013-02-11T04:53:40Z
It seems that all ports on your machine are taken. We need to open a port to communicate back and forth with Python external processes.
So I think you need to close/uninstall xrdp or restart your machine to reset your ports state.

From<EMAIL_ADDRESS>on 2013-02-13T02:12:58Z
Thank you.
It's sad that I don't know how to manage ports in Linux or RDP in particular. Apparently, the problem also occur when open new xwindow, eg. on tty8-tty12.

From<EMAIL_ADDRESS>on 2013-02-16T05:48:56Z
Status: Invalid

From<EMAIL_ADDRESS>on 2013-02-15T21:11:30Z
After playing with ports in xrdp.ini (and unsuccessful), I simply did:
$ sudo apt-get remove --purge xrdp vnc4server
I'm happy to have Spyder back.
Btw, I want to cite to Spyder in my paper. How can I do this?
Than you.
Yus

From<EMAIL_ADDRESS>on 2015-01-09T02:09:23Z
I resolved re setting into /etc/network/interfaces the
auto lo
iface lo inet loopback


Options not working because to_json makes everything a string

In Issue #3 you state you can pass arguments correctly. However, if I want to add a callback function such as :onResult => "my_function() { alert('do stuff') }", the resulting javascript ends up looking like:
"onResult": "my_function() { alert('do stuff') }"

onResult() is a string (rather than a function) and thus, not actually executed. It seems this happens because you parse the options using to_json, which would convert any Javascript code into a string rather than pass it straight through. Am I missing something here? Is there a better way to do this using your gem?

Unfortunately, I don't think there is right now. We want to let users pass a real Ruby hash to that method so they don't have to worry about the details of it emitting Javascript.
I would consider accepting a pull request that passes Strings straight through to the Javascript, but encodes everything else with to_json.

@stouset looked into it, should be too hard. Do you think about something like:
transloadit_jquerify :upload, '{wait: true}'

which would passed directly to JS while:
transloadit_jquerify :upload, :wait => true

would be encoded by to_json?
If so, I'll fix that tomorrow, push the commit and document it (off for today)

Alternatively, you could do it in Javascript. Perhaps something like:
VIEW FILE:
transloadit_callbacks = { some: parameters }

transloadit_jquerify :upload, :wait => true

The JS that gets generated would then be refactored to merge in the parameters. As in:
$('#upload').transloadit({
  wait: true,
// merge the custom callbacks array into the ones the gem generated
}.extend(transloadit_callbacks));

See here: https://github.com/transloadit/rails-sdk/pull/20

Honestly, that way seems a lot more obscure to me.
I can't think of a scenario where somebody would already be passing a String for that parameter, so it should be a very trivial patch to transloadit_jquerify. @rmehner has already volunteered, so I won't take away his thunder... :)

I'll try to keep the discussion on this thread. The problem with @rmehner's solution is that it means putting JavaScript code in a Ruby string, and then passed it in as a function argument that then gets parsed back into JavaScript. Not only is that difficult to debug if a developer typo-s something in the function, but it also forces the implementer to use pure JS. But these days, many Ruby developers are using CoffeeScript. My solution lets the caller decide what implementation language they wish to use and then to inject accordingly. It also lets the final code be more dynamic, since the page (i.e., browser) can alter the callback hash at runtime AFTER the your gem has already processed. This seemed more flexible to me.
Keep in mind that my problem is that I want to pass potentially complex JavaScript functions as callbacks to the transloadit jQuery API (you can attach callbacks to events such as an upload completing, I believe). As that logic gets heavier and more complex, the thought of passing that all in as a Ruby string scares me. It made sense to me that the solution kept the Ruby code light and maintainable (by the implementer). Unless I'm misunderstanding the solution presented?

I actually thought about it again and what I think now is the following: we know which callbacks are supported (currently everything that starts with "on" is a callback, see: http://transloadit.com/docs/configuring-the-jquery-plugin). So the patch I would write would do the following:

JSON encode everything that is not a known callback function
everything that is a callback is not encoded with JSON

If you guys accept that way I would write that and push it to this repo.

Tim accidentally closed this.

I like the solution, but it does mean we'll have to make sure the whitelist is always kept in sync with the potential callbacks. They're probably not likely to change, though.

Oops, sorry for closing this.
As for the callbacks: Yeah they won't change.
If there is a big update that would break bc, we'll announce it as a new jQuery SDK version anyway and keep the current one around for legacy.

@rmehner Still got this one? I can jump in if you're busy.

@stouset been sick over the weekend, patch will arrive tomorrow.

Pushed a fix. @michikono please test so @stouset can push out a new gem version.
@stouset: not too happy with the fact that I don't have any tests for this, but I'm on a train right now and internet connection is a bit limited. Couldn't figure out how to test the helper correctly without requiring abstract_unit from ActionView TestCases too. Maybe you have an idea :)
I did some tests within a test app and everything worked so far.

No worries. :)


Fuzzing is generating a false test for Random

Description
Fuzzing is generating a test for Random without mocks - when Mock everything outside class is checked.
The test asserts the value returned by Random and fails.
To Reproduce

Run a project in IntelliJ Idea 2022.1.3  - 2022.2.2
Install RC plugin build
Set Fuzzing to 100% (in File -> Settings -> Tools ->  UnitTestBot)
Generate tests with UnitTestBot for utbot-sample/src/main/java/org/utbot/examples/mock/MockRandomExamples.java
for useSecureRandom() - check Mock everything outside class.

Expected behavior
There should be only valid tests generated.
Possible solutions
Fuzzer can use mock Random(?)
Generated tests should be double-checks that they return same results(?)
other solution(?)
Actual behavior
Fuzzing is generating a test for Random without mocks. It asserts the value returned by Random and fails.
Visual proofs
The following test is generated by Fuzzer:
    ///region FUZZER: SUCCESSFUL EXECUTIONS for method useSecureRandom()

    @Test
    @DisplayName("useSecureRandom: arg_0 = MockRandomExamples() -> return 1")
    public void testUseSecureRandomReturnsOne() {
        MockRandomExamples mockRandomExamples = new MockRandomExamples();

        int actual = mockRandomExamples.useSecureRandom();

        assertEquals(1, actual);
    }
    ///endregion

Environment
Windows 10 Pro
IntelliJ IDEA 2022.2.2
Additional context
Originally posted by @alisevych in https://github.com/UnitTestBot/UTBotJava/issues/1102#issuecomment-1269804477

Also need to think about cases when Random is reused (not created new) - or other Random implementations are used.

concolic executor find some new Random()

Also need to find Random usages.
And other Random implementations can be used.
@korifey Would it be too long to rerun every test generated by Fuzzing? - to check if received data is changing from run to run

Also, there is the same problem with Random when generating tests for vertexSum method from recursion package.
It is worth to mention that it reproduces not every time.
Steps to reproduce:

Run runIde task
Copy recursion package to the test project inside runIde
Generate a test for vertexSum method with the following settings: JUnit5, not parameterized, any mocking strategy. You have to have two generated tests, and regenerate if there is only one.

One (the test below) of the two generated tests will fail when running because of Random usage inside vertexSum method.
///region FUZZER: SUCCESSFUL EXECUTIONS for method vertexSum(int)

/**
 * @utbot.classUnderTest {@link Recursion}
 * @utbot.methodUnderTest {@link Recursion#vertexSum(int)}
 */
@Test
@DisplayName("vertexSum: n = 134217732 (mutated from 4) -> return 293591018")
public void testVertexSum() {
    Recursion recursion = new Recursion();

    int actual = recursion.vertexSum(134217732);

    assertEquals(293591018, actual);
}
///endregion


Make keystone support mod_oauth2

Partial osism/issues#130
Signed-off-by: Arvid Requate<EMAIL_ADDRESS>

Ok, I added the full keystone.conf to the testbed repo instead. Using patches would have the advantage that we store exactly what we needed to change and remain flexible with respect to upstream changes. But it's your repo, your rules, as you like.

You do not need to add the full keystone.conf configuration file. You only need to add there changes you want to do.
For example when you add a keystone.conf to the overlays in the testbed configuration repository with the following content kolla-ansible will merge the default template with this content.
[XXX]
aaa = „bbb“


New text inserted should be selected

when use i or a should also select the text (it could be an option)

It's a lot easier to handle selections movement like this.


i2c clock stretching problem

The implementation limits the maximum duration of clock stretching to only 10 times the duration of function read_sda. The I2C specification does not specify any timeout conditions for clock stretching. Each slave can hold SCL down as long as it needs. The master has to wait until SCL goes high before it can continue.
I have a CCS811 sensor here, that produces clock stretchings up to 60 us. With CLOCK_STRETCH=10 the time the master waits before timeout is much too less and the I2C communication fails. Increasing CLOCK_STRETCH to 200 works for this device but might still produce problems with other devices.
Please increase the CLOCK_STRETCH constant a lot, remove it completly, or make it configurable.

Configurable would be the best option I think.


Add support for Namespace scoped NetworkPolicy CRD

The scope of this PR is as follows:

Generate code for Antrea NP and ExternalEntity types
Add Antrea NetworkPolicy and ExternalEntity CRD yamls in dev mode
OpenAPIv3 validation schema to validate NP spec and ensure AppliedTo and Priority (1-10000) fields are mandatory
Update RBAC for antrea-controller in dev mode
Add Antrea NetworkPolicy and ExternalEntity CRD types

hi @tnqn @jianjuns
This PR is from Abishek, other than changing ExternalEndpoint to Endpoint, do u have any other comments that u'd like us to address?
Thx, Su

/test-all

/test-e2e

/test-windows-conformance


How do you yum install against uploaded RPMs?

My apologies if this is a silly question, but I can't figure this out. I've set this up and have successfully posted RPMs to this service, with /api/upload working perfectly as expected.
I can see the images under /api/repo just fine, returned in JSON format, but it's occurring to me that I can't figure out how to pull RPMs out from there.
I've tried to walk the source code, and it looks like the only API route exposed for /api/repo is configured to only return a JSON.
I don't see any code/handlers to actually pass back the RPMs or expose a xml based resource that yum might understand.
I checked the wiki, commit history, pull request history, and google-fu'd heavily. I also watched the only video I could find on this (https://www.youtube.com/watch?v=xVRBDK6s7Og&feature=youtu.be) and it was alluded to but I couldn't see any code to actually do this.
The meetup page (https://www.meetup.com/DC-continuous-delivery/events/219648907/) which links to some slides (http://marshyski.com/talks/rpm-build-api-ci.html) but that URL does not resolve.

Hi @JonKohler, thank you for your interest in yum-nginx-api! NGINX is used to serve the RPMs for yum/rpm. You can use this configuration and hit this route, https://github.com/FINRAOS/yum-nginx-api/blob/master/nginx/nginx.conf#L54
NGINX is a dependency, but since a lot of organizations support it, it's easiest to get buy-in, but I would love to remove NGINX and serve right from the Go web service. Is this something you are interested in? I can propose a changeset for you to review along with @kood1 if it simplifies your architecture.

I'm all for simplification if you're up for proposing something.
In the meantime, are you saying that with NGINX, one should just be able to point yum.conf like this? or am I misinterpreting thing?
[base]
name=yum-api-repo
enabled=1
baseurl=http://ngnix-here/repo
gpgcheck=0
priority=1

@JonKohler that looks correct, is it not working? I can generate some configurations and Dockerfiles for references. It is time I update the project dependencies.
The proposed change is to serve the static content (RPM) through the go web services at a route such as /yum  I'd like to put together a design document and share it with you since I run into this in multiple environments between debs and RPMs.

@JonKohler @kood1 this is my proposal to support additional functionality in yum-nginx-api and the removal of NGINX with the go web server already being built.
https://gist.github.com/marshyski/f1d69ce007a3080139d9ea8b38477a26

Hey @JonKohler still interested in helping out?

@JonKohler  just cut an updated release, keeping this issue open if anyone is interested in the proposed changes.

@JonKohler  just cut an updated release, keeping this issue open if anyone is interested in the proposed changes.

 I think at a larger level, the rest of the engineering org is just moving things left and right to artifactory though :/

Hey @marshyski - sorry I dropped off the face of the earth, back half of the year was chocked full of shenanigans and I haven't gotten around to drilling back into this project. I think at a larger level, the rest of the engineering org is just moving things left and right to artifactory though :/

@JonKohler makes sense, especially for a larger org. Thank you for trying out yum-nginx-api!

@JonKohler makes sense, especially for a larger org. Thank you for trying out yum-nginx-api!


Redirect if not authenticated

The keycloak request filter automatically redirects if the user is not authenticated. kc_security just ends in 403.
Can you implement a redirect or is this behaviour on purpose?

The first version was make it thinking on backend services, but I want to implements that part, I haven't time yet but it's on my plans.


Update how-to-setup-cmk.md

Improvement to Add Access Policy section.  You must save the changes before leaving the Key Vault instance.

@shsolomo : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Prevent EntityStorages from being opened while inside a mech.

About the PR

EntityStorages now can't be opened anymore while inside the storage of a hydraulic clamp.
Why / Balance

Currently if you open an EntityStorage while it's stored inside the clamp it will put everything it contains into the clamp's storage.
This allows players to fill the clamp's storage over it's limit. It also allows entities, that aren't whitelisted to be grabbed, to be put into the clamp's storage.
Not being able to open the EntityStorage while it's inside the clamp's storage will prevent it from transferring it's contents to the internal storage.
Technical details

When an EntityStorage is grabbed by a hydraulic clamp, the CanOpen value on the component will be set to false.
When the EntityStorage is removed from the hydraulic clamp's storage, CanOpen is set to true again.
When an entity with hands is inside a grabbed EntityStorage, it will check it's held items and set any held EntityStorage's CanOpen value to false.
If a handheld EntityStorage is dropped it's CanOpen value will be set to true again.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: Dygon

fix: Storage objects can't be opened anymore while inside a hydraulic clamp's storage.

NOO RIPLEY'S GRACE

Is there another issue with opening entity storages inside entity storages not putting things into the outer entity storage when not clamped?

Not sure, but after the change I made based on the review from @metalgearsloth it's now impossible to open an EntityStorage inside a container if the outer entity storage isn't a hand.
Are there currently any EntityStorages that should be allowed to be opened while inside another container?

Are there currently any EntityStorages that should be allowed to be opened while inside another container?

I don't think so, no, but will keep this for now with the hands check.


Fit a logistic regression as well?

Hi Jonathan,
After watching this epic video by 3blue1brown https://www.youtube.com/watch?v=Kas0tIxDvrg I thought you could perhaps fit a sigmoid line as well as the exponential.
Or even better (will probably only make sense if you've seen the video)

calculate the change per time step (current value - previous value)
calculate the growth rate (ratio of the current and previous change)
estimate when the above will be 1 (with another kind of fit?)
fit the sigmoid with that time as the inflection point :astonished:?

Thanks, yes this video is great. Interested in doing a PR?

Yes, I'd be interested but unfortunately cannot take on any programming side projects right now, even though this sounds like fun. Last year of my PhD is about to begin 😅

It might be a good idea to add a link to the video in the forecast section


bug: Bad error message on http

I was getting
 ERROR

 gatsby-source-wordpress  GraphQL Request must include at least one of those two parameters: "query" or "queryId" (request)

 If you haven't already, try adding define( 'GRAPHQL_DEBUG', true ); to your wp-config.php for more detailed error messages.

 ERROR

 gatsby-source-wordpress  Encountered errors. See above for details.

not finished createSchemaCustomization - 1.796s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I couldn't figure out the issue till I noticed the URL I'd specified was http. Changing it to https resolved the issue.

@moonmeister I believe I fixed this a few weeks ago but it's hard to tell without being able to reproduce. I think the problem was that some types of redirects are happening in browser from http to https. Since I can't follow in browser redirects it was just returning the html of the 404 or error page. I'm now providing a more useful error message when that happens. Let me know if you run into this again!