[SPARK-33251][PYTHON][DOCS] Migration to NumPy documentation style in ML (pyspark.ml.*)

What changes were proposed in this pull request?

This PR proposes migration of pyspark.ml to NumPy documentation style.
Why are the changes needed?

To improve documentation style.
Does this PR introduce any user-facing change?

Yes, this changes both rendered HTML docs and console representation (SPARK-33243).
How was this patch tested?

dev/lint-python and manual inspection.

Test build #130741 has started for PR 30285 at commit 2d49a1d.

Test build #130741 has finished for PR 30285 at commit 2d49a1d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35350/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35350/

Merged build finished. Test PASSed.

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

Retest this please.

Test build #130746 has started for PR 30285 at commit 2d49a1d.

Test build #130746 has finished for PR 30285 at commit 2d49a1d.

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

Merged build finished. Test PASSed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35355/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35355/

Merged build finished. Test FAILed.

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

Test build #130749 has started for PR 30285 at commit ecf58f4.

Test build #130749 has finished for PR 30285 at commit ecf58f4.

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

Merged build finished. Test PASSed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35358/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35358/

Merged build finished. Test FAILed.

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

Test build #130750 has started for PR 30285 at commit 4e5dadb.

Test build #130750 has finished for PR 30285 at commit 4e5dadb.

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/130750/
Test PASSed.

Merged build finished. Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35359/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35359/

Merged build finished. Test PASSed.

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

Awesome @zero323! I will take a look in the following few ays.

Test build #130755 has started for PR 30285 at commit 3fb2bc9.

Test build #130755 has finished for PR 30285 at commit 3fb2bc9.

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

Merged build finished. Test PASSed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35364/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35364/

Merged build finished. Test FAILed.

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

Test build #130756 has started for PR 30285 at commit bc86028.

Test build #130756 has finished for PR 30285 at commit bc86028.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35365/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35365/

Merged build finished. Test PASSed.

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

cc @huaxingao, @zhengruifeng, @viirya, @BryanCutler, can you take a cursory look when you guys fine some time?

Test build #130791 has started for PR 30285 at commit 4bf8e35.

Test build #130791 has finished for PR 30285 at commit 4bf8e35.

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

Merged build finished. Test PASSed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35400/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35400/

Merged build finished. Test FAILed.

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

Test build #130800 has started for PR 30285 at commit 93abf8e.

Test build #130800 has finished for PR 30285 at commit 93abf8e.

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

Merged build finished. Test PASSed.

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35409/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35409/

Merged build finished. Test PASSed.

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

Test build #130807 has started for PR 30285 at commit f49de34.

Test build #130807 has finished for PR 30285 at commit f49de34.

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

Merged build finished. Test PASSed.

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

Merged to master.
Thanks all!

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35417/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35417/

Merged build finished. Test PASSed.

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


Map on mobile fullscreen

According to the teachers, we can put the map full screen instead scrolling horizontally.

Sections are variable in length. On my mobile phone the middle section is one finger width wide, any smaller than that and seems to me that it would become a problem. And Tauw would probably like to expand/change the current map so it is uncertain whether it would fit in the future.
If the map is shown full screen we should at least make sure it can zoom in.

It has been done


Add xms-ids for notebooks

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

About this Change
APIs will need to start indicating item uniqueness in arrays. By default, uniqueness is the string property called "id" of items in an array. When that property does not exist, the x-ms-identifiers extension property must be used to specify the identifying property(s) or lack thereof. This pull request is my best guess effort to ease resource providers into the new requirement before it becomes enforced. Compliance and accuracy will need to be owned and maintained by the resource provider going forward.
See https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-identifiers.

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@getroyer @geoffreymtroyer I see you contributed to this file earlier. We would like to have people from the RP team to help take a look at the changes. Could you help with a code review? Thanks!

@LinglingTong What is the purpose of the PR and what the is significance of the x-ms-identifiers?
Hey @getroyer The annotation "x-ms-identifiers" was newly introduced end of last year. the x-ms-identifiers annotation is used to indicate the unique identifiers for an object type array. Change analysis team is doing the initial work for all RPs, and that's why this pull request is for. The annotation will be a required annotation and the check will be turned on later after the whole initialization is done.
Hope this helps :)

@LinglingTong What is the purpose of the PR and what the is significance of the x-ms-identifiers?
Hey @getroyer The annotation "x-ms-identifiers" was newly introduced end of last year. the x-ms-identifiers annotation is used to indicate the unique identifiers for an object type array. Change analysis team is doing the initial work for all RPs, and that's why this pull request is for. The annotation will be a required annotation and the check will be turned on later after the whole initialization is done.
Hope this helps :)

Understood, looks fine to me

@msyyc This PR has been signed off already. Could you please help with merging it? Thanks!

The failure about  is not related with this PR.


CompilerCPP does not generate valid c++ for array constant expressions

Invalid c++ is generated for shaders that use constant expressions to initialize arrays.
For example in shaders/frag/constant-array.frag the generated cpp is this:
vec4 indexable[3] = vec4[](vec4(1.0f), vec4(2.0f), vec4(3.0f));
vec4 indexable_1[2][2] = vec4[][](vec4[](vec4(1.0f), vec4(2.0f)), vec4[](vec4(8.0f), vec4(10.0f)));

While this is valid glsl, it is not valid c++.
I fixed this by redefining
virtual std::string constant_expression(const SPIRConstant &c);
in CompilerCPP like this:
string CompilerCPP::constant_expression(const SPIRConstant &c)
{
	if (!c.subconstants.empty())
	{
		// Handles Arrays and structures.
		string res = "{";
		for (auto &elem : c.subconstants)
		{
			res += constant_expression(get<SPIRConstant>(elem));
			if (&elem != &c.subconstants.back())
				res += ", ";
		}
		res += "}";
		return res;
	}
	else if (c.columns() == 1)
	{
		return constant_expression_vector(c, 0);
	}
	else
	{
		string res = "{";
		for (uint32_t col = 0; col < c.columns(); col++)
		{
			res += constant_expression_vector(c, col);
			if (col + 1 < c.columns())
				res += ", ";
		}
		res += "}";
		return res;
	}
}

You must be a mind reader, was just thinking about this :p
This does get quite tricky in C++11 with compounds.
There are other problems like not being able to assign arrays when I think about it. We might need std::array.

To be honest I didn't looked into the problem very thoroughly, but come to the above solution just to fix the specific problem that appears with the shader I mentioned before. Can you describe other cases that will cause problems?

Hm. So the simple case is
int foo[] = { 1, 2, 3, 4 };
Struct foo = { 1, 2, 3, 4 };

That should work for both structs and arrays. As well as arrays of them. I'm less sure about cases where you pass constant structs and arrays as function parameters though. Glslang won't currently hit those cases since parameters are first stored to a local variable before being passed in, but that will probably change.
#version 310 es
precision mediump float;
layout(location = 0) out vec4 FragColor;

vec4 foo(vec4 a[2])
{
   return a[0] + a[1];
}

void main()
{
   FragColor = foo(vec4[](vec4(10.0), vec4(20.0)));
}

I'm not sure if we can properly express the compound here since the array turns into a pointer in C++.

#13


Exception: ValueError: not enough values to unpack (expected 2, got 1)

I am following the guide on: https://github.com/microsoftgraph/msgraph-sdk-python to build a Python package that can pull all my devices from Azure AD (Entra). I have confirmed good working API credentials and that they have the right permissions:
async def get_AADdevices():     MScredential = ClientSecretCredential(         tenant_id=os.environ['MSGraphTenantID'],         client_id=os.environ['MSGraphClientID'],         client_secret=os.environ['MSGraphClientSecret']     )     scopes = ['https://graph.microsoft.com/.default']     client = GraphServiceClient(credentials=MScredential, scopes=scopes)     devices = await client.devices.get()
I am getting the following error when it calls the await client.devices.get():
Executed 'Functions.MachineReconciliation' (Failed, Id=d6a7b205-25fc-4dfa-ad22-3621ed0b4144, Duration=9ms) System.Private.CoreLib: Exception while executing function: Functions.MachineReconciliation. System.Private.CoreLib: Result: Failure Exception: ValueError: not enough values to unpack (expected 2, got 1) Stack:   File "C:\Program Files\Microsoft\Azure Functions Core Tools\workers\python\3.10/WINDOWS/X64\azure_functions_worker\dispatcher.py", line 479, in _handle__invocation_request     call_result = await self._loop.run_in_executor(   File "C:\Users\<user>\AppData\Local\Programs\Python\Python310\lib\concurrent\futures\thread.py", line 58, in run     result = self.fn(*self.args, **self.kwargs)   File "C:\Program Files\Microsoft\Azure Functions Core Tools\workers\python\3.10/WINDOWS/X64\azure_functions_worker\dispatcher.py", line 752, in _run_sync_func     return ExtensionManager.get_sync_invocation_wrapper(context,   File "C:\Program Files\Microsoft\Azure Functions Core Tools\workers\python\3.10/WINDOWS/X64\azure_functions_worker\extension.py", line 215, in _raw_invocation_wrapper     result = function(**args)   File "C:\Users\<path>\function_app.py", line 17, in MachineReconciliation     asyncio.run(get_AADdevices())   File "C:\Users\<user>\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 44, in run     return loop.run_until_complete(main)   File "C:\Users\<user>\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 649, in run_until_complete     return future.result()   File "C:\Users\<path>\function_app.py", line 40, in get_AADdevices     devices = await client.devices.get()   File "C:\Users\<path>\.venv\lib\site-packages\msgraph\generated\devices\devices_request_builder.py", line 70, in get     return await self.request_adapter.send_async(request_info, DeviceCollectionResponse, error_mapping)   File "C:\Users\<path>\.venv\lib\site-packages\kiota_http\httpx_request_adapter.py", line 162, in send_async     parent_span = self.start_tracing_span(request_info, "send_async")   File "C:\Users\<path>\.venv\lib\site-packages\kiota_http\httpx_request_adapter.py", line 131, in start_tracing_span     uri_template = ParametersNameDecodingHandler.decode_uri_encoded_string(   File "C:\Users\<path>\.venv\lib\site-packages\kiota_http\middleware\parameters_name_decoding_handler.py", line 92, in decode_uri_encoded_string     name, value = name_value.split('=')

I also saw this issue.  It has to do with the url decoding logic in the middleware being coupled to the logic that starts the telemetry (which doesn't deal with urls); will have a pr and a fix for review in a second

I am also seeing this issue

Hi everyone,
Thanks for reporting this.
I can see that @ladycarbonfiber already started a pull request #225. I'll provide a review over there shortly.


Fix upper wind anomaly with iterative winds and lower flat z height

TYPE: bug fix & enhancement
KEYWORDS: iterative winds, flat_z_height, wind
SOURCE: Ethan Gutmann, NCAR
DESCRIPTION OF CHANGES:
Primarily, this is a fix for issue #129 . This issue noted that upper level winds in icar could contain anomalous vertical motion when the flat Z height was set somewhere below the model top and the iterative wind solver was used (wind=3). Here we have modified the domain object so that the max level is set to the top of the model, and in the iterative wind solver we have modified wind_K to always defaults to the top of the model. Because there is some potentially valuable behavior in the old configuration, most of that code was left in but commented out.
In addition, this pull request has cleaned up some of the array 2-D/3-D calls to the array utilities, and created 2D arrays for latitude and longitude if they are read from a one dimensional array.  Note that one dimensional arrays should not generally be used for the domain in icar because the grid will not be equal area in that case. However, for small ideal tests, this is a useful functionality to have. We might want to consider adding a warning such that when one dimensional arrays are detected the user is warned that this is not a desirable configuration.
Finally, this pull request has begun adding the functionality to permit a combination of the linear wind solver, and the iterative wind solver to be used. Some of the changes were intermingled, and this functionality should not be considered live yet so no documentation has been added.
ISSUE: Fixes #129
TESTS CONDUCTED:
steps to reproduce in issue used, upper level winds decay to 0 at model top now.
NOTES:
Beyond being a bug fix, this may modify model behavior such that more lifting occurs.  Recommend testing and lowering model top to reproduce old outputs as needed.
Checklist

[x] Closes issue #129
[x] Mostly backwards compatible, model behavior may change slightly
[x] Requires new files? No
[x] Documented in PR and issue

does this make my comments visible?


add two function: matrix_to_quaternion() and quaternion_to_matrix()

please check two additional functions in pytorch3d_utils.py

Hi Cris, Thank you for the contribution.
Currently, we are still testing the stability of different rotation representations. We will merge the code when we finish the test.
Please note that it's not enough to only add utility scripts. If you want to use other rotation representations, you need also to modify the model output dimension and the training logic.
Btw, I think PyTorch3D has a more efficient operation for conversion between quaternion and rotation matrix. Please check the source code.

No problem. Thanks for the clarification. I will modify the what you have mentioned.


proto: gen string as strict text

90c822c
 cabal: sdist of hstream-common-<IP_ADDRESS>: filepath wildcard 'gen-cpp/**/*.h'
refers to the directory 'gen-cpp', which does not exist or is not a directory.
filepath wildcard 'gen-cpp/**/*.h' does not match any files.


Fix name variables in cluster resource doc.

Signed-off-by: cappyzawa<EMAIL_ADDRESS>
Changes
Fix name variables in cluster resource doc because ClusterResource doen't have Name param.

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task and TaskRun to build and release this image

Reviewer Notes
If API changes
are included, additive changes
must be approved by at least two OWNERS
and backwards incompatible changes
must be approved by more than 50% of the OWNERS,
and they must first be added
in a backwards compatible way.

/ok-to-test

/lgtm

/retest


no progressbar

when i try to start IDEA it gives the following error
ERROR: could not find function "bsProgressBar"
was working fine  till last week, Is there any dependency im missing?
Warning: Error in tag: could not find function "bsProgressBar"
Stack trace (innermost first):
    60: tag
    59: tags$div
    58: div
    57: tag
    56: tags$div
    55: div
    54: tag
    53: tags$div
    52: div
    51: tag
    50: tags$div
    49: div
    48: tag
    47: tags$div
    46: div
    45: tagList
    44: attachDependencies
    43: bootstrapPage
    42: shinyUI
     2: shiny::runApp
     1: runIDEA
Error : could not find function "bsProgressBar"

Thank you

didn't see the new dependencies

Sorry for this late reply.  According to your error message, seems to be a dependency issue. As I wrote in README file, this error mainly caused by the latest version of ShinyBS. It removed several fancy function s that employed in IDEA including   bsProgressBar.
To fix this, you have to first remove the current ShinyBS  package and reinstall the 0.25.0 version or type the following command:
devtools::install_github( "likelet/shinyBS")
PS: This error may happen at  every time that you update your packages . plz keep the ShinyBS in a constant version at your R env

Thanks, it is working after removal of shinyBS(remove.packages("shinyBS")) and installing recommended version(devtools::install_github( "likelet/shinyBS"))

any suggestion what dependency is needed to download report.
ERROR: pandoc version 1.12.3 or higher is required and was not found (see the help page ?rmarkdown::pandoc_available).

actually, two packages are required for downloading report:
rmarkdown and pandoc
if it is still not working, try update your knitr packages

Also, i remember  that i had listed this issue in FAO of README file as follow words.
3. "Error: pandoc version 1.12.3 or higher is required and was not found." while clicks the download report button:
Answer: If you see this message that means you upgraded your Rstudio version, the problem is still exist. This means you need a pandoc to render Rmd file into html report. You can install it from https://github.com/jgm/pandoc/releases/tag/<IP_ADDRESS> as YiHui suggested. Then restart your Studio.
you may try this if pandoc can not be used.

hi,
thanks for suggestion.
it worked after installing this version https://github.com/jgm/pandoc/releases/tag/<IP_ADDRESS> as you suggested.


Error: Parameter token or opts.auth is required

I keep getting this error, for some reason token isn't showing up as an input even though it is in the workflow file.
Workflow:
      - name: Trigger Cypress tests
        uses: benc-uk/workflow-dispatch@v1
        with:
          workflow: front-end-pull-request.yml
          token: ${{ secrets.PAT }}
          repo: company/repo-name
          inputs: '{ "BRANCH_NAME": "${{ env.BRANCH_NAME }}", "TEST_URL": "${{ env.TEST_URL }}", "TEST_COMMIT": "${{ env.TEST_COMMIT }}" }'

Output:
Run benc-uk/workflow-dispatch@v1
  with:
    workflow: front-end-pull-request.yml
    repo: company/repo-name
    inputs: { "BRANCH_NAME": "", "TEST_URL": "", "TEST_COMMIT": "" }

Error: Parameter token or opts.auth is required

This turned out to be due to other workflows passing secrets to the current one, so the token secret wasn't being picked up.


[broker] Improved thread safety on PersistentReplicator

Several methods on the PersistentReplicator are accessing & modifying volatile fields (e.g. readBatchSize) and triggering/scheduling calls to readMoreEntries() without synchronization.  This PR fixes that and should improve the stability when replication is involved. It should also help ensure that permits are still valid when triggering readEntries.

@merlimat What about this one?   :)

@lhotari If you're aware of any issues this might address, if you could please tag them here, that would be great.

The pr had no activity for 30 days, mark with Stale label.

Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant.
Generally, adding synchronized at the method level is not a good idea. It can be overkill and highly possible to deadlock. If there's a concurrency issue, please provide either a test to reproduce or describe the problematic execute order.


Replace IllegalStateException by IOException, SecurityException etc. where possible

okhttp seems to throw IllegalStateException quite often, for instance when unexpected data is received (see
https://github.com/square/okhttp/issues/2683).
Please consider replacing all IllegalStateExceptions by

IOException when unexpected network traffic occurs (for instance, HTTP2 frame errors etc)
SecurityException for TLS errors etc.

The IllegalStateExceptions cause apps using okhttp to crash unexpectedly and as far as I know, IllegalStateExceptions should only be thrown when an API is called incorrectly (for instance, sending a request before it was specified or something like that).

Yes, we only intend to throw IllegalStateException on mistakes made by the API user, not on mistakes made by the remote peer. If you have particular examples, I can fix ’em.

For instance, I got this crash:
Caused by: java.lang.IllegalStateException: closed
	at okhttp3.internal.http.Http1xStream$FixedLengthSource.read(Http1xStream.java:374)
	at okio.Buffer.writeAll(Buffer.java:993)
	at okio.RealBufferedSource.readByteArray(RealBufferedSource.java:106)

I never closed a connection twice or something like that, at least not intentionally. Wouldn't it be better to use IOException for that? For instance, Socket bind() throws an IOException too, if the socket is already bound.
I suggest to replace almost all IllegalStateExceptions, especially
IOException could be used here:

src/main/java/okhttp3/internal/connection/RealConnection.java ("already connected")
src/main/java/okhttp3/internal/connection/StreamAllocation.java
src/main/java/okhttp3/internal/http1/Http1Codec.java
src/main/java/okhttp3/internal/http1/Http1Codec.java (for instance, the invalid states)
src/main/java/okhttp3/internal/tls/DistinguishedNameParser.java ("Unexpected end of DN", this really shouldn't be an unchecked exception)
src/main/java/okhttp3/internal/cache2/Relay.java ("closed")
src/main/java/okhttp3/internal/http2/Http2Connection.java
src/main/java/okhttp3/internal/http2/Http2Stream.java (for instance, when response headers are already sent)

Something like URISyntaxException could be used here:

src/main/java/okhttp3/HttpUrl.java (it can easily happen that you build an URL from parts you have received from somewhere; no unchecked exception should occur when you innocently build an URI from such parts)
src/main/java/okhttp3/Response.java (see above)

SecurityException could be used here:

src/main/java/okhttp3/Handshake.java ("cipherSuite == null")
src/main/java/okhttp3/OkHttpClient.java ("Unexpected default trust managers:" etc.)

Looking through most of these it seems like almost all of ’em are caused by clients using the API improperly. For example, it’s not good if a client attempts to read a stream after it has been closed. I’m not sure how you got in that situation, but that’s what we should fix.
The DN example is definitely one we should fix. I’m happy to fix any others that could be triggered by a misbehaving server. But if your client code calls APIs out of sequence that needs to result in a hard exception. Otherwise bugs don’t get fixed!

I’m not sure how you got in that situation, but that’s what we should fix.

I don't have an idea where to begin. The code works in 99,9999% of the time – we have only got a single report, and I guess that it's related to a server/proxy which sends unexpected data (and maybe closes a stream two times or whatever, I don't know it). I doubt that it's caused by incorrect API usage, but if you say so, I'll believe it and just ignore this problem until it happens more often.

I looked into the unchecked exceptions thrown by the DistinguishedNameParser.
It should be impossible for DistinguishedNameParser to throw those exceptions if the input is always a well-behaved X500Principal. The correct behavior is to continue to throw unchecked exceptions here (because they indicate bugs) rather than checked IOExceptions (because they indicate connectivity or protocol problems).
As for the unexpected IllegalStateException, I’d love a testcase.
No further action to take on this.

What is X500Principal?


Add multi-instances folding to AugmentedFCircuit & IVC

Adds the logic to support multi-instances folding in HyperNova's AugmentedFCircuit & IVC.
Adds also methods to generate new LCCCS & CCCS instances that don't depend on the main folding chain, to be folded in in the next step
Updates CycleFold circuit & methods to work other folding schemes than Nova adapting it to fold multiple points per circuit (instead of 2-to-1 as till now)

Rebased to latest main branch updates, this PR is now ready to be reviewed.

Rebased the branch of this PR to latest main branch changes.


Can't figure out how to load graph in IDE.

https://neueda.gitbooks.io/jetbrains-plugin-graph-database-support/content/data-sources/types/neo4j-bolt.html Shows To-Do


[doc] fix typo

The preceding code does not include the class Adult.

While you're at it. Right above that there is a line of code: db.put(Person("Jack", parents)), but Person has no constructor taking more than one argument, so it will fail to compile.

@Minirogue Thank you for your comment, I see what you mean. fixed 5bce465

Great, thanks!


Read a wishlist

As a customer
I need to be able to retrieve a single wishlist by its id
So that I can get the product ids and name of the wishlist
Assumptions:

the list returned will not be one that's persisted

Acceptance Criteria:
Given that I have a wishlist id
When I make a request with that wishlist id
Then i get a wishlist with a name, id, and list of products

This issue looks to me like a duplicate of querying a wishlist by name : Issue 4. The wishlist ID is maintained by us for internal use. So the customer has no information about the wishlist ID

It does seem like a duplicate. Looks like pretty much the "get" method all over again.

We will duplicate it.
On Mon, Oct 16, 2017 at 5:45 PM, Aashish Dugar<EMAIL_ADDRESS>wrote:

It does seem like a duplicate. Looks like pretty much the "get" method all
over again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nyu-devops-golf-team/wishlist/issues/2#issuecomment-337052939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aea0tM0zc_aIei-r_6fYrGdZ8q_PV-Mjks5ss85hgaJpZM4PuGlL
.


[INFO][com.freerdp.utils] - Caught signal 'Segmentation fault'

Hello,
starting xfreerdp /u:user /p:password /v:hostname via VNC I have a Segmentation fault if the vncviewver area size is less than the xfreerdp one.
Could someone help me to solve this issue?
Thanks

with this description, no.

ok I will add more information asap.

closing due to lack of information.
please add at least the versions you use next time.
(for note, tried with current master, and a session size larger than the X11 session and I do not have any issue. Might be a bug in your vnc server


bottle + gunicorn + meinheld errors when having concurrency

I have used this combination for a long time, always behind a nginx serving static and I have not had problems, but now I have needed to serve a file from bottle (basically in a test environment) and I realized that if I make calls to the file static works correctly, but if I make several requests at the same time, the static file never responds.
I start the server like this:
if __name__ == "__main__":
    run(
        port=3322, host="<IP_ADDRESS>",
        server="gunicorn",
        worker_class='egg:meinheld#gunicorn_worker',
        workers=16,
        # reloader=True,
        quiet=False,
        debug=True
    )

I attached some images in case I did not explain myself well:
https://imgur.com/a/JrgoDEm

I have tried other combinations in case my code was wrong and it worked correctly:
gunicorn + gevent
gunicorn + sync
gunicorn + gthreads
meinheld without gunicorn
for now, it has only happened to me in the static files, maybe because they are loaded later?

Bottle is a WSGI framework and relies on a well-behaving multi-threaded runtime. Three assumptions must be true at all times:

A threading.local container must be local to the current thread.
A WSGI request is handled by the same thread from start to finish.
Two WSGI requests are not handled by the same thread at the same time.

If you replace traditional threads by e.g. 'green threads' then you also have to monkey-patch either bottle or threading.local or thread locals like bottle.request will break. I suspect that this is the issue here.


Ghidra should support MIPS Octeon-specific instructions

Describe the bug
Ghidra doesn't seem to decode instructions introduced in the MIPS Octeon processor.  At least with the example I've seen, the instruction is decoded as SPECIAL2, whereas IDA correctly decodes it as SEQI.
To Reproduce

Analyze a binary compiled for the MIPS Octeon.
Look for "SPECIAL" instructions

Expected behavior
No "SPECIAL" instructions.
Screenshots
Ghidra:

IDA:

Attachments
If applicable, please attach any files that caused problems or log files generated by the software.
libtecla.so.1.6.1.zip
Environment (please complete the following information):

OS: MacOS
Java Version: OpenJDK 11
Ghidra Version: 9.1.2 PUBLIC

Oh, see also:
https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20140331/211812.html


Selecting more than one item

How can I “select more than one item” in a NERDTree, if possible at all?
Specifically, I want to select more than one file (for instance, foo.h and foo.c) and then use T to open them in a new tab, together, as vertical splits. If this isn’t implemented yet, then consider it a feature request (in which case, perhaps it would be nice to be able to use two different commands in sequence, i.e. Ts to open a new tab in the background and then open each selected item in a split, or si to open a new vsplit and then add each selected item to a horizontal split in that new vsplit.)

Manipulating multiple items still not possible? 😮

2011 🤷♂

I've written another plugin to do this. Its URL is https://github.com/PhilRunninger/nerdtree-visual-selection, and it will open all the files in a visual selection (in either the previous window, in horizontal or vertical splits, or in tabs). It can also delete all the files in a visual selection, after confirmation.


Why numpy>=1.13.3,<=1.14.5?

I have tried using numpy 1.16.1 and it works. Is there a reason for that specific set of versions?
Thanks

Hi, the only reason is that the two packages are based on ML agents which at the time used this requirement. I'm not sure if there was a particular reason for that but I see they have extended to >=1.13.3,<=1.16.1 in the last version. You can of course use the version you want in your submissions.

Great, thanks!


moon: 1.20.1 -> 1.21.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moonrepo/moon/releases.
meta.description for moon is: A task runner and repo management tool for the web ecosystem, written in Rust
meta.homepage for moon is: https://github.com/moonrepo/moon
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.21.0 with grep in /nix/store/88m58bfpcyjkqb0zfpvqfym9xz4jxqv2-moon-1.21.0
found 1.21.0 in filename of file in /nix/store/88m58bfpcyjkqb0zfpvqfym9xz4jxqv2-moon-1.21.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
moon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/88m58bfpcyjkqb0zfpvqfym9xz4jxqv2-moon-1.21.0 \
  --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 moon https://github.com/r-ryantm/nixpkgs/archive/5d4e1fbfe795e6518231fded25bd6f043172f5a2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5d4e1fbfe795e6518231fded25bd6f043172f5a2#moon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/88m58bfpcyjkqb0zfpvqfym9xz4jxqv2-moon-1.21.0
ls -la /nix/store/88m58bfpcyjkqb0zfpvqfym9xz4jxqv2-moon-1.21.0/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:

moon

Maintainer pings
cc @flemzord for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moonrepo/moon/releases.
meta.description for moon is: A task runner and repo management tool for the web ecosystem, written in Rust
meta.homepage for moon is: https://github.com/moonrepo/moon
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.21.3 with grep in /nix/store/bmn6kk92fycg2vc1rydp3s2sjl158gvb-moon-1.21.3
found 1.21.3 in filename of file in /nix/store/bmn6kk92fycg2vc1rydp3s2sjl158gvb-moon-1.21.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
moon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bmn6kk92fycg2vc1rydp3s2sjl158gvb-moon-1.21.3 \
  --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 moon https://github.com/r-ryantm/nixpkgs/archive/7ad7a8e2dfd36ade33d1e59dc1042417f4302f44.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7ad7a8e2dfd36ade33d1e59dc1042417f4302f44#moon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bmn6kk92fycg2vc1rydp3s2sjl158gvb-moon-1.21.3
ls -la /nix/store/bmn6kk92fycg2vc1rydp3s2sjl158gvb-moon-1.21.3/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:

moon

Maintainer pings
cc @flemzord for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moonrepo/moon/releases.
meta.description for moon is: A task runner and repo management tool for the web ecosystem, written in Rust
meta.homepage for moon is: https://github.com/moonrepo/moon
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.21.4 with grep in /nix/store/hdqwb3q2cbjb3fxfims5i8xyxz701pir-moon-1.21.4
found 1.21.4 in filename of file in /nix/store/hdqwb3q2cbjb3fxfims5i8xyxz701pir-moon-1.21.4

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
moon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hdqwb3q2cbjb3fxfims5i8xyxz701pir-moon-1.21.4 \
  --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 moon https://github.com/r-ryantm/nixpkgs/archive/8cd205247188c2bedd1c3b0650dba606a776af24.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8cd205247188c2bedd1c3b0650dba606a776af24#moon

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hdqwb3q2cbjb3fxfims5i8xyxz701pir-moon-1.21.4
ls -la /nix/store/hdqwb3q2cbjb3fxfims5i8xyxz701pir-moon-1.21.4/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:

moon

Maintainer pings
cc @flemzord for testing.


Assertion failure for differing kernel K and input u

When using the following run command:
python -m s4.train --dataset mnist-classification --model s4 --epochs 10 --bsz 128 --d_model 128 --ssm_n 64
I'm finding that this assertion is faliing:
https://github.com/srush/annotated-s4/blob/2cfd155217cc928ded27f1434fb71e3ef8245a95/s4/s4.py#L343
for the mnist classification task. I'm not quite sure if the failure is intentional or there's an off-by-one bug somewhere between the initialization of the model and the training.  The following lines in the code will pad out any discrepancy between the Kernel length and u length, so the code runs fine if you simply remove the assertion. But that might not be the intended behavior.
        ud = np.fft.rfft(np.pad(u, (0, K.shape[0])))
        Kd = np.fft.rfft(np.pad(K, (0, u.shape[0])))

Good catch. For MNIST classification you can remove the assert and it should be fine.
The real issue is that we are dropping the last pixel [:-1] for generation, and left it in for classification. We should not drop the last classification pixel.

Fixed now.


Could not load dynamic libary

if im loading my FMU, i get this Error:
\v0.7.0-85bef849b4.clean\src\fmi2\fmi2_library.cpp:91: Unable to load dynamic library '-------"......\fmi4cpp_MFLEX_Blocks_FMU_RobotPlattformControlled_52703516/binaries/win32/MFLEX_Blocks_FMU_RobotPlattformControlled.dll'! 126

I can only speculate on the cause. Does it work in other tools?

i just tried it out in Visual studio, my fmu does not support Modelexchange, has it any impacts cause of that?

I doubt it. The error occurs during Windows LoadLibrary, so I'm guessing you will get the same error in other tools. So this is probably not a fmi4cpp issue. That's why I asked if it works in other tools, fmilib, fmpy etc. It might be caused by missing dlls on your system, but I can only speculate.

i treid it out today with fmPy, it works there

Then I guess it is a bitness issue. VS is default 32 bit no? FMPy probably ran it in 64 bit mode.

so... i tried it out, its seems to be a 32/64 bit problem ;) maybe you should write only a 32 bit support in the readme. next person will thank you ;)

maybe you should write only a 32 bit support in the readme. next person will thank you

Well, it's a FMU issue not a fmi4cpp issue.


Support additional environment variables from secret

I don't want environment variables like RELAY_PASSWORD to be in my git repository, so I'd like to be able to configure a Secret where I can specify arbitrary environment variables to be added to the container via envFrom.

Sounds like a good idea to me - what to create a PR?

Unfortunately, I'm not sure what the best way to do that would be, as after diving into it further I noticed that every environment variable is already specified in env and so envFrom would not be able to override it. I ended up manually configuring all the resources per the documentation instead of using this helm chart.

Yeah, probably should create a config map and secret and remove the envs from the deployment.

+1 this is important for secret credentials like RELAY_PASSWORD


referenceStripElement doesn't work?

I'm trying to put a referenceStrip into its own element (I don't want it to overlay on the main image), but I can't get it to work. Neither of the following work:
  var viewer = OpenSeadragon({
    id: 'viewer',
    prefixUrl: 'images/',
    tileSources: tileSrcs,
    showReferenceStrip: true,
    referenceStripElement: 'navstrip'
  });

  var viewer = OpenSeadragon({
    id: 'viewer',
    prefixUrl: 'images/',
    tileSources: tileSrcs,
    showReferenceStrip: true,
    referenceStripElement: document.getElementById('navstrip'),
  });

Both of them wind up throwing Uncaught TypeError: Cannot read property 'style' of undefined at openseadragon.js, line 10305.
I'm pretty sure the problem is in the viewer class: in the viewer class, the referenceStripElement property is assigned to the property id, but in the ReferenceStrip class, there's no way to actually pass in an element (as far as I can tell). Because options.id is set in ReferenceStrip, the if at line 75 never fires, and this.element is always undefined, thanks to the $.extend at line 89.
I think (but am not sure), that allowing an element property in the options to ReferenceStrip would fix the the problem, but might cause other problems, so I don't want to submit a PR.

Why is this still not merged? 5 years... o.O
v2.4.0 still lacks support for custom reference strip container...

Yeah, looks like @mmcclimon walked away from the patch (https://github.com/openseadragon/openseadragon/pull/338) before it was done. @VipSaran would you be up for taking it across the finish line? Doesn't look like there is a lot to do...

Hello, after update to the lates vesion od OSD i do not get the error mentioed above anymore, but at the same place new error appears: [Error] TypeError: undefined is not an object (evaluating 'this.element.tabIndex = 0') 	(anonymous function) (openseadragon.js:16452)

@HemboPagi There was work in progress to fix this on PR https://github.com/openseadragon/openseadragon/pull/1961, but @msalsbery hasn't updated it in a while. Would you be interested in taking it across the finish line?

I have a branch with a bunch of reference strip fixes. The last thing on my TODO for that, which I was starting to work on, was the fix for proper support for using a specific parent element 🙄

@msalsbery Nice! It'll be most welcome :)

@msalsbery would be ready to share your branch?

@msalsbery would be ready to share your branch?

I think I pushed the working branch quite a while ago, but I'm also back working on it. Sorry for the extreme lag!

@HemboPagi I believe the branch in question is https://github.com/openseadragon/openseadragon/pull/1961.

@iangilman gracias! I’ll sync/update it to latest code if I don’t just finish it


use passwordless sudo for wg-quick + wheel

This has only been tested by running the commands listed, but not as part of a full deployment.

@nikhiljha @KeplerC was this meant to be merged into the humble branch?


Add regex behavior description to matchText for find

Should mirror runShell's matchText behavior.

Will be in v2.14.0.


[WIP] Write markers before hashes to fix issues.

Fixes issue with generated lock file when hashes and markers are used together.
Changelog-friendly one-liner:  Fixes https://github.com/jazzband/pip-tools/issues/762
Contributor checklist

[ ] Provided the tests for the changes.
[ ] Requested a review from another contributor.
[x] Gave a clear one-line description in the PR (that the maintainers can add to CHANGELOG.md on release).
[x] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

@atugushev Please review when you get a chance.

@atugushev added test.

@milind-shakya-sp it looks good now. Could you please change the Changelog-friendly one-liner, because the issue number will be attached anyway.

@atugushev updated.

Thanks for the contribution!

pip-tools v3.5.0 is released


Version Dependencies

Creating the following policy allows all users to run all commands:   {"name":"policy_1","users":[""],"actions":[""]} which is what was expected.  However, running the following policy blocks all users from running any commands (even the root user:  {"name":"policy_1","users":["root"],"actions":[""]}. I am running an older docker version (intentionally) which may be the reason the second policy fails.  Are there any authz-broker docker version dependencies which would prevent this policy from working?

@eets8305 you need to use client certificate to authenticate users, unix users are not supported by the docker authorization framework (not specifically this sample plugin).


Add more questions

Add more questions to the Questions.kt file.
How?
Add a Question to questions arraylist in the Object QuestionsBank.
Format:
Question(
           <String: Question to ask here>,
           <Boolean: if the statement made in the question is true or false>,
           <String: The actual fact of the question>
        ),

Example:
Question(
            "Other than water, coffee is the world's most popular drink.",
            true,
            "Coffee is consumed by about one-third of Earth's population."
        ),

Note:

Only one question should be added in a PR, if you need to add more questions, make a pr for each request
Ensure no questions are repeated
The pull request should also contain the source of truth for the question.

I would like to work on it. Can you assign it to me?

@keivalya You can start working on it directly, as this issue asks to add more questions it will be open to everyone.

Oh true. Absolutely.
Thanks!

i would like to solve this

i would like to work on this

Hi @KunalRaghav , I have added one new question for hacktoberfest 2021 on PR.
Thanks for your attention 😄


[joy-ui][Tooltip] Add ability to use tooltip in "childfree" mode

Summary
Currently, the only way to have several elements with the same tooltip is to wrap each element with it:
{rows.map(row => (
	<Tooltip key={rows.id} title={row.tooltipTitle}>

{row.text}

	</Tooltip>
)}

If there are 100 rows, there are 100 divs and 100 Tooltips.
For most cases this is okay.
But, if tooltips are controlled, each row must re-render on tooltip state change.
It seems that using something like a context tooltips can be made to work this way:
{rows.map((row) => (

 setTooltipContextOrSmth({position: e.position, title: row.title)}>
		{row.text}

))}
<Tooltip {...tooltipContextOrSmth} />

I am not sure how big of a portion of this behavior should be part of the library, but at least being able to set position (or anchor) I think is a must.
If this is already possible, I would like to see an example in docs, I did not find any.
You can probably already achieve this with menus or popovers, but it feels weird to reimplement tooltip just to move it somewhere.
Examples
n/a?
Motivation
In my pet project, I'm making a tooltip-synced """chart""":

If you hover one of the top columns or one of the bottom columns, the other's tooltip will open also, and for big """charts""" I'm getting performance on hover.
Yes, this particular use-case is probably solved by an actual charts built with , like mui-charts, but same problem could happen in tables or for github activity for example:

Search keywords: one tooltip multiple hosts childfree childrenless anchor position host

Hey! 👋  Thanks for opening this issue; seeing some Joy UI love is awesome! Just passing by to share that the team might take a bit longer to get back to Joy UI-related issues due to the focus on the two major releases coming up for Material UI this year.
In any case, this sounds like an interesting feature to support on the Tooltip component, and it probably deserves some debate around what's the best API. In the meantime, I've added the "waiting for 👍" label so we can gauge interest from other community members. Definitely feel free to share any progress you’ve had on the issue, if any, though!


[REQUEST] Retry Key

Hello,
these first 2 lines are more of a question, i want to know what happen after RetryKey triggered
does the app change proxy or re-run from same proxy, if yes for how many time
can u link me please to the .cs file, please
A Case
lets say i am testing a website which lunch recaptcha / or any other security in 2 cases:
_ proxy is banned
_ good user
to bypass the the first case of banned proxy, i need to retry from different proxy
then i want to set the config to use recaptcha service if the amont of retries is greater than X
which mean that the combo is good, and recaptcha is on forever
but until here i don't have a variable or a way to save the number of retries of each bot with specific combo
Describe the solution you'd like
Maybe you can set an accessible counter for number of retries for Combo-X in Bot-Y
Describe alternatives you've considered
Do like old S.MBA was doing, there many kind of retries
a normal retry (with the same proxy )
another retry from different proxy ...
what is more important is the following settings:
the ability to send a combo to recheck, after x retry
(Sorry to compare)
i like the first solution more, it would give the user more control
and it is useful with IF function
thanks for reading until here
regards

Retry = the proxy is set back to available in the proxy pool and the data is retried.
Ban = the proxy is set to banned (and it won't be used by any bot until unbanned) and the data is retried.
I will consider the first solution you proposed.

thank you


RFC: View-model, auto diffing section controller

We generate view models to drive all of the cells in a particular section controller on Instagram. These models are derived from a top-level model that is created from server data. The view models are then used to configure things like image and text cells within a section controller.
We can represent this transformation:
protocol ViewModel: IGListDiffable {...}

func map(object: Any) -> [ViewModel] {...}

We could create a section controller that diffs its own array of ViewModel objects, then apply those diffs at the item (e.g. "cell") level.
There are a few gotchas to doing this, that's why I think a built-in and tested version of this would be valuable (similar to the embedded adapter idea in #31).
You end up with diffing of sections/section-controllers and the items/cells within them. It totally converts your setup to being data-driven all the way down to the cell level.

This would really be one-way data flow once built:

Top-level data in IGListAdapterDataSource
Section controller transforms data into an array of view models
View-model to cell class
"Bind" view model to cell (e.g. config)

Don't want to lock down the API too much though, for instance cell selection should still be handled manually I think.

Section controller transforms data into an array of view models

This is "too late" in the flow.
Where we use view models, we're returning them in -itemsFromListAdapter:. The view models need to be the items that are diff'd.

@jessesquires I mean use a top-level array of objects to drive sections, then a view-model array to drive numberOfItems. Then the section controller does diffing for its view models when the top-level model changes.
Not sure if that makes sense.
(basically what we do for feed items tho)

Had some ideas this morning. Need to write them down so they aren't lost.

Instead of calling reload in the infra, if we have a cell bind/configure architecture, we can actually reconfigure the cell instead of calling reload (which does delete+insert internally). This unlocks moving and reloading the cell at the same time!!
Have to take special care not to call reloadSection when diffing the top-level object. If that happens the item-level updates are lost.
Need to avoid over-diffing the view models. Just like the top-level arrays, this should only happen once when the update is performed.
Should the transform be a SC subclass override? a block passed on init? custom object w/ protocol passed on init? Still 🤔 on this
Does #392 need to be done first? I don't think so.
I like the sound of IGListBindable for the cells. Thoughts?

💯


interactsh.com is down?

https://check-host.net/check-report/6440faekaab

[FTL] Could not create client: could not make register request: POST https://interactsh.com/register giving up after 6 attempts: Post "https://interactsh.com/register": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

@077uyp can confirm the https://interactsh.com server is not stable atm and known issue that we are still investigating - https://check-host.net/check-report/64520ddk505, feel free to use https://interact.sh as an alternate server for interactsh client or nuclei using server / iserver flag.

Ok, thank you

Same issue.

@Anon-Exploiter should be fixed with latest release of this project.

Down again

Same issue, both .com and .sh are down

@Y4er @fuomag9 interact.sh seems be working fine - https://check-host.net/check-report/66ffb3ekc85

@Y4er @fuomag9 interact.sh seems be working fine - https://check-host.net/check-report/66ffb3ekc85

You're right, it was an issue on my end. Both are up for me now

➜  ~ curl -vvv "https://interactsh.com/register"
*   Trying <IP_ADDRESS>:443...
* connect to <IP_ADDRESS> port 443 failed: Connection refused
* Failed to connect to interactsh.com port 443: Connection refused
* Closing connection 0
curl: (7) Failed to connect to interactsh.com port 443: Connection refused
➜  ~ curl -vvv "http://interactsh.com/register"
*   Trying <IP_ADDRESS>:80...
* Connected to interactsh.com (<IP_ADDRESS>) port 80 (#0)
> GET /register HTTP/1.1
> Host: interactsh.com
> User-Agent: curl/7.77.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 Bad Request
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Headers: Content-Type, Authorization
< Access-Control-Allow-Origin: https://app.interactsh.com
< Content-Type: application/json; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Fri, 24 Dec 2021 15:02:20 GMT
< Content-Length: 44
<
{"error":"could not decode json body: EOF"}
* Connection #0 to host interactsh.com left intact

maybe 443 port is the problem.

down again. look this https://check-host.net/check-report/6700309k23

To be expected with<PHONE_NUMBER>8752358357 people scanning the Internet for Log4Shell (ab)using interactsh as their endpoint. My suggestion, set up your own server, it's super easy and runs perfectly fine on a $5 VPS from DigitalOcean. 👍🏻

@Y4er as stated here - https://interactsh.com is down and known, the latest version of client uses interact.sh and not .com

but https://app.interactsh.com/ still using interactsh.com, how fix it?

but https://app.interactsh.com/ still using interactsh.com, how fix it?

Here is how you can fix it - https://github.com/projectdiscovery/interactsh/discussions/126#discussioncomment-1813242

@rugk the above URL is valid and usable to use interactsh web client, it's just interactsh.com is not used as interactsh server anymore.

ah now it also works again, it was done when I clicked it or so


You should update page to indicate that fetchXML is limited to 5,000 records even if the pagination is turned up

[Enter feedback here]

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

ID: 4fae8260-c3b8-4582-884d-72119ab256b7
Version Independent ID: a12c64c0-9293-d86c-91c3-bce01efd1e1b
Content: Use lists of rows in flows - Power Automate
Content Source: articles/dataverse/list-rows.md
Service: power-automate
Sub-service: cloud-flow
GitHub Login: @MSFTMan
Microsoft Alias: Matow

Contacted PM for resolution.


refactor rcs_chunked_list and remove its c++ features

remove rcs_chunked_list 's c++ features. All the functionality remain the same
It can pass the make precommit.
in x86 machine (32bit)
size -A release_jerry output

section
master
patch

.note.gnu.build-id
36
36

.text
253351
1253191

.rodata
13564
13596

.eh_frame
26464
26036

.init_array
4
0

.data
1096
1096

.bss
2363776
2363776

.comment
41
41

Total
2658332
2657772

the cppcheck log
jzd@jzd32:~/jerryscript$ cat ./build/bin/debug.linux/cppcheck.log
make[1]: Entering directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
/usr/bin/cmake -H/home/jzd/jerryscript -B/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native --check-build-system CMakeFiles/Makefile.cmake 0
make -f CMakeFiles/Makefile2 cppcheck.debug.linux
make[2]: Entering directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
/usr/bin/cmake -H/home/jzd/jerryscript -B/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles 0
make -f CMakeFiles/Makefile2 CMakeFiles/cppcheck.debug.linux.dir/all
make[3]: Entering directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
make -f CMakeFiles/cppcheck.debug.jerry-core.dir/build.make CMakeFiles/cppcheck.debug.jerry-core.dir/depend
make[4]: Entering directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
cd /home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/jzd/jerryscript /home/jzd/jerryscript /home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native /home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native /home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles/cppcheck.debug.jerry-core.dir/DependInfo.cmake --color=
Dependee "/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles/cppcheck.debug.jerry-core.dir/DependInfo.cmake" is newer than depender "/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles/cppcheck.debug.jerry-core.dir/depend.internal".
Dependee "/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native/CMakeFiles/cppcheck.debug.jerry-core.dir/depend.internal".

Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-gc.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-conversion.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-external-pointers.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-number.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-string.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-value.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers-values-collection.cpp...
1/109 files checked 0% done
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-helpers.cpp...
2/109 files checked 0% done
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-init-finalize.cpp...
3/109 files checked 1% done
Checking /home/jzd/jerryscript/jerry-core/ecma/base/ecma-lcache.cpp...
4/109 files checked 2% done
5/109 files checked 3% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array-prototype.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-array.cpp...
6/109 files checked 4% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-boolean-prototype.cpp...
7/109 files checked 4% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-boolean.cpp...
8/109 files checked 5% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-compact-profile-error.cpp...
9/109 files checked 5% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-date-prototype.cpp...
10/109 files checked 7% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-date.cpp...
11/109 files checked 7% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-error-prototype.cpp...
12/109 files checked 10% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-error.cpp...
13/109 files checked 10% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-evalerror-prototype.cpp...
14/109 files checked 10% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-evalerror.cpp...
15/109 files checked 11% done
16/109 files checked 11% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-function.cpp...
17/109 files checked 11% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-global.cpp...
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-function-prototype.cpp...
18/109 files checked 11% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-helpers-date.cpp...
19/109 files checked 12% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-helpers-json.cpp...
20/109 files checked 13% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-helpers.cpp...
21/109 files checked 13% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-json.cpp...
22/109 files checked 14% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-math.cpp...
23/109 files checked 15% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-number-prototype.cpp...
24/109 files checked 18% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-number.cpp...
25/109 files checked 20% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-object-prototype.cpp...
26/109 files checked 22% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-object.cpp...
27/109 files checked 23% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-rangeerror-prototype.cpp...
28/109 files checked 27% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-rangeerror.cpp...
29/109 files checked 27% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-referenceerror-prototype.cpp...
30/109 files checked 29% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-referenceerror.cpp...
31/109 files checked 30% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-regexp-prototype.cpp...
32/109 files checked 30% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-regexp.cpp...
33/109 files checked 30% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-string-prototype.cpp...
34/109 files checked 30% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-string.cpp...
35/109 files checked 32% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-syntaxerror-prototype.cpp...
36/109 files checked 32% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-syntaxerror.cpp...
37/109 files checked 34% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-type-error-thrower.cpp...
38/109 files checked 34% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-typeerror-prototype.cpp...
39/109 files checked 35% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-typeerror.cpp...
40/109 files checked 35% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-urierror-prototype.cpp...
41/109 files checked 35% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtin-urierror.cpp...
42/109 files checked 35% done
Checking /home/jzd/jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.cpp...
43/109 files checked 35% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-array-object.cpp...
44/109 files checked 36% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-boolean-object.cpp...
45/109 files checked 36% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-comparison.cpp...
46/109 files checked 36% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-conversion.cpp...
47/109 files checked 36% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-eval.cpp...
48/109 files checked 36% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-exceptions.cpp...
49/109 files checked 37% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-function-object.cpp...
50/109 files checked 37% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-get-put-value.cpp...
51/109 files checked 38% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-lex-env.cpp...
52/109 files checked 38% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-number-arithmetic.cpp...
53/109 files checked 39% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-number-object.cpp...
54/109 files checked 40% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-objects-arguments.cpp...
55/109 files checked 40% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-objects-general.cpp...
56/109 files checked 40% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-objects.cpp...
57/109 files checked 41% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-reference.cpp...
58/109 files checked 41% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-regexp-object.cpp...
59/109 files checked 45% done
Checking /home/jzd/jerryscript/jerry-core/ecma/operations/ecma-string-object.cpp...
60/109 files checked 45% done
Checking /home/jzd/jerryscript/jerry-core/jerry.cpp...
61/109 files checked 48% done
Checking /home/jzd/jerryscript/jerry-core/jrt/jrt-bit-fields.cpp...
62/109 files checked 49% done
Checking /home/jzd/jerryscript/jerry-core/jrt/jrt-fatals.cpp...
63/109 files checked 49% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-char-helpers.cpp...
64/109 files checked 50% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-literal-storage.cpp...
65/109 files checked 52% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-literal.cpp...
66/109 files checked 52% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-magic-strings.cpp...
67/109 files checked 53% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-snapshot.cpp...
68/109 files checked 53% done
Checking /home/jzd/jerryscript/jerry-core/lit/lit-strings.cpp...
69/109 files checked 54% done
Checking /home/jzd/jerryscript/jerry-core/mem/mem-allocator.cpp...
70/109 files checked 54% done
Checking /home/jzd/jerryscript/jerry-core/mem/mem-heap.cpp...
71/109 files checked 54% done
Checking /home/jzd/jerryscript/jerry-core/mem/mem-poolman.cpp...
72/109 files checked 56% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/bc/bytecode-data.cpp...
73/109 files checked 56% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/collections/array-list.cpp...
74/109 files checked 58% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/collections/linked-list.cpp...
75/109 files checked 58% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/collections/lit-id-hash-table.cpp...
76/109 files checked 59% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/jsp-early-error.cpp...
77/109 files checked 60% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/jsp-mm.cpp...
78/109 files checked 60% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/lexer.cpp...
79/109 files checked 62% done
80/109 files checked 62% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/opcodes-dumper.cpp...
Checking /home/jzd/jerryscript/jerry-core/parser/js/parser.cpp...
81/109 files checked 65% done
Checking /home/jzd/jerryscript/jerry-core/parser/js/scopes-tree.cpp...
82/109 files checked 66% done
Checking /home/jzd/jerryscript/jerry-core/parser/regexp/re-compiler.cpp...
83/109 files checked 66% done
Checking /home/jzd/jerryscript/jerry-core/parser/regexp/re-parser.cpp...
84/109 files checked 67% done
Checking /home/jzd/jerryscript/jerry-core/rcs/rcs-allocator.cpp...
85/109 files checked 69% done
Checking /home/jzd/jerryscript/jerry-core/rcs/rcs-chunked-list.cpp...
86/109 files checked 71% done
Checking /home/jzd/jerryscript/jerry-core/rcs/rcs-cpointer.cpp...
[/home/jzd/jerryscript/jerry-core/rcs/rcs-chunked-list.cpp:212]: (style) C-style pointer casting
[/home/jzd/jerryscript/jerry-core/rcs/rcs-chunked-list.cpp:244]: (style) C-style pointer casting
[/home/jzd/jerryscript/jerry-core/rcs/rcs-chunked-list.cpp:310]: (style) C-style pointer casting
87/109 files checked 71% done
Checking /home/jzd/jerryscript/jerry-core/rcs/rcs-iterator.cpp...
88/109 files checked 71% done
Checking /home/jzd/jerryscript/jerry-core/rcs/rcs-records.cpp...
89/109 files checked 72% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-agnostic.cpp...
90/109 files checked 72% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-ecma-arithmetics.cpp...
91/109 files checked 73% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-ecma-bitwise.cpp...
[/home/jzd/jerryscript/jerry-core/vm/vm-opcodes.inc.h:123] -> [/home/jzd/jerryscript/jerry-core/vm/vm-opcodes.inc.h:123]: (style) Same expression on both sides of '=='.
92/109 files checked 75% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-ecma-equality.cpp...
93/109 files checked 77% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-ecma-relational.cpp...
94/109 files checked 78% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-ecma-try-catch-finally.cpp...
95/109 files checked 79% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-for-in.cpp...
96/109 files checked 82% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-helpers-variables.cpp...
97/109 files checked 83% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes-varg.cpp...
98/109 files checked 83% done
Checking /home/jzd/jerryscript/jerry-core/vm/opcodes.cpp...
99/109 files checked 83% done
Checking /home/jzd/jerryscript/jerry-core/vm/pretty-printer.cpp...
100/109 files checked 84% done
Checking /home/jzd/jerryscript/jerry-core/vm/vm-stack.cpp...
101/109 files checked 84% done
Checking /home/jzd/jerryscript/jerry-core/vm/vm.cpp...
102/109 files checked 84% done
103/109 files checked 85% done
104/109 files checked 86% done
105/109 files checked 86% done
106/109 files checked 86% done
107/109 files checked 88% done
108/109 files checked 91% done
109/109 files checked 100% done
make[4]: *** [CMakeFiles/cppcheck.debug.jerry-core] Error 1
make[4]: Leaving directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
make[3]: *** [CMakeFiles/cppcheck.debug.jerry-core.dir/all] Error 2
make[3]: Leaving directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
make[2]: *** [CMakeFiles/cppcheck.debug.linux.dir/rule] Error 2
make[2]: Leaving directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'
make[1]: *** [cppcheck.debug.linux] Error 2
make[1]: Leaving directory `/home/jzd/jerryscript/build/obj-VALGRIND-OFF-VALGRIND_FREYA-OFF-LTO-ON-ALL_IN_ONE-OFF/native'

performance in x86 machine.  remain same
                           Benchmark |         RSS
(+ is better) |        Perf
(+ is better) |
                           --------- |                          --- |                         ---- |
                          3d-cube.js |          116->   116 (0.000) |       0.284-> 0.288 (-1.408) |
              access-binary-trees.js |           84->    84 (0.000) |        0.16-> 0.164 (-2.500) |
                  access-fannkuch.js |           44->    44 (0.000) |       0.836->0.8368 (-0.096) |
         bitops-3bit-bits-in-byte.js |           32->    32 (0.000) |        0.236-> 0.236 (0.000) |
              bitops-bits-in-byte.js |           32->    32 (0.000) |       0.2936-> 0.288 (1.907) |
               bitops-bitwise-and.js |           36->    36 (0.000) |        0.292-> 0.292 (0.000) |
            controlflow-recursive.js |          240->   240 (0.000) |        0.144->  0.14 (2.778) |
                       crypto-aes.js |          124->   124 (0.000) |       0.528->0.5296 (-0.303) |
                       crypto-md5.js |          188->   188 (0.000) |      2.4352-> 2.464 (-1.183) |
                      crypto-sha1.js |          136->   136 (0.000) |       1.124-> 1.136 (-1.068) |
                date-format-tofte.js |           76->    76 (0.000) |        0.296-> 0.292 (1.351) |
                date-format-xparb.js |           72->    72 (0.000) |        0.156-> 0.148 (5.128) |
                      math-cordic.js |           40->    40 (0.000) |         0.32-> 0.316 (1.250) |
               math-spectral-norm.js |           40->    40 (0.000) |        0.192-> 0.192 (0.000) |
                    string-base64.js |          168->   168 (0.000) |    28.6832->29.3656 (-2.379) |
                     string-fasta.js |           52->    52 (0.000) |      0.5776->0.5832 (-0.970) |
                     Geometric mean: |            RSS reduction: 0% |            Speed up: 0.1752% |

Could you please repeat these measurements on an ARM board? (The best would be on an RPI2)

I've already started work on this topic (https://github.com/Samsung/jerryscript/pull/791#discussion_r49310940) and I have a not-yet-published patch very similar to yours, but I intended to keep it private until all the code size increase issues I've experienced are solved.
To reduce the chance of duplicating work: I've also been working on the refactoring of the operand class in the parser.

Yes I agree to avoid work duplication. I think you should discuss how to share the work. Perhaps a good topic for Gitter :)

measure on RPI2, @rtakacs is the data similar with yours?
Benchmark |         RSS(+ is better) |        Perf(+ is better) |
--------- |                          --- |                         ---- |
3d-cube.js |          112->   112 (0.000) |        2.97->  2.99 (-0.673) |
access-binary-trees.js |           84->    80 (4.762) |      1.84667->  1.82 (1.444) |
access-fannkuch.js |          40->    36 (10.000) |       8.67->9.00333 (-3.845) |
bitops-3bit-bits-in-byte.js |           32->    32 (0.000) |    2.22333->2.23667 (-0.600) |
bitops-bits-in-byte.js |           32->    32 (0.000) |         2.99->  2.99 (0.000) |
bitops-bitwise-and.js |           32->    32 (0.000) |        3.44->  3.61 (-4.942) |
controlflow-recursive.js |          220->   220 (0.000) |    1.53667->1.55667 (-1.302) |
crypto-aes.js |          124->   120 (3.226) |    5.14667->5.21667 (-1.360) |
crypto-md5.js |          184->   184 (0.000) |    24.3367->24.4133 (-0.315) |
crypto-sha1.js |         132->   136 (-3.030) |       11.22->11.1833 (0.327) |
date-format-tofte.js |           72->    72 (0.000) |    3.19333->3.21333 (-0.626) |
date-format-xparb.js |          76->    80 (-5.263) |     1.65667->1.63667 (1.207) |
math-cordic.js |          40->    36 (10.000) |        3.27->  3.29 (-0.612) |
math-spectral-norm.js |          40->    36 (10.000) |      2.05333->  2.05 (0.162) |
string-fasta.js |           48->    48 (0.000) |    5.29333->5.37667 (-1.574) |
Geometric mean: |       RSS reduction: 1.9588% |            Speed up: -0.834% |

section
master
patch

.note.gnu.build-id
36
36

.text
189192
188320

.rodata
8284
8336

.ARM.exidx
8
8

.init_array
4
0

.data
1096
1096

.bss
2363776
2363776

.comment
43
43

.ARM.attributes
51
51

Total
2658332
2657772

So this is actually a size reduction! Great!

@zherczeg Do you mean the RSS result? I don't know why the rss will change in RPI2. In x86 machine, it is exactly same after the refactor.

@jiangzidong: My last measurement with my patch was at the end of December. The code size was a bit bigger than yours, but the performance test results are similar to yours.

@ruben-ayrapetyan Thanks, I fixed as you commented.

Looks good to me

LGTM, but I'm not a reviewer.

LGTM

@jiangzidong: I'm compiling the project with a standard C compiler and fixing the remaining little C++ features. Before we land this patch, please add a 'typedef' to the rcs_chunked_list_t struct to use it as a type.

@rtakacs: updated. sorry for the mistake

@jiangzidong Thanks for the update. The fix looks good to me.

Landed (dfb22c34419d28c045c7954bab905067b04138f3)


Mysterious stack corruption

Currently unable to reproduce this bug myself, known to be present in https://github.com/DeanoBurrito/northport/commit/04de59a53317a3b5087143ff1e992fce0b3d0e42 and older. OS was run using a standard ubuntu LTS install (qemu 4.2).
Output of readelf -e startup.elf here: https://pastebin.com/NqKK3hsx
Output of addr2line on faulting address:
$ addr2line -e initdisk/apps/startup.elf -a 0x2025f9
0x00000000002025f9
/home/xyz/Documents/Github/northport/libs/np-syscall/SyscallFunctions.cpp:11

Logging output of the kernel from the crash:

A few things worth noting so far:

We're page faulting at cr0, in user code. This is likely a nullptr deref somewhere.
There's no active VM ranges, so the crash is happening before any MapMemory syscalls. This means before the userspace heap is initialized.
From the selectors and saved instruction pointer we know it's crashing in the program code, not a syscall.
The code at the faulting address is:

bool LoopbackTest()
    {
        SyscallData data((uint64_t)SyscallId::LoopbackTest, 0, 0, 0, 0);
        DoSyscall(&data);

        return data.id == SyscallSuccess; // <--- this line here
    }

This is bizzare as this syscall is never called, so we should never reach this point.

Looks like memory corruption. I think I've been able to reproduce this by issuing lots (100s) of IPC calls when running emulated in qemu (instead of kvm). It seems to be a processes saved registers are getting corrupted with kernel heap node addressses. Since some nodes may contain nullptr for next/prev this would make sense with above.
It's also happened with idle threads and the other user program.
Not sure if this is a buffer overrun, use-after-free error or something else yet.

This was a good excuse to rewrite the kernel heap (finished as of today), and with the help of some new debugging features I can confirm that we're not overrunning any heap allocated buffers. The heap is much faster now too, so silver linings!
If it's not a heap buffer, I'm guessing it's a stack overflow haha. I only had a quick look, but it seems we're stilling only allocating a single page for any spawned threads. Program stacks are also identity mapped or mapped in the hhdm, meaning a kernel stack can very easily touch other nearby physical pages, since there's no unmapped pages around it.
I'm thinking I might start allocating kernel and user stacks at a fixed virtual address, or maybe within a range (so they're not predictable). The hhdm is useful, but dangerous to return as 'allocated' memory anywhere. I might do a pass over the kernel so that the hhdm is only used to directly access memory, and all other accesses are done via a virtual mapping. We could enforce this by marking those pages as non-present when not in use, for help with debugging.

After an experiment with allocating each thread's stack at a unique address, surrounded by unmapped pages (so any overruns would case a page fault) it looks like its not going to be that simple. We're not exceeding the bounds of any stacks anywhere.
This means that the issue is not from writing data outside of the bounds of either stack or heap allocated buffers.
At this stage I can only seem to reproduce 2 distinct issues:

a page fault with kernel cs/ss but both %rip and %rsp are kernel heap pointers (%rip should be code). The pointer always seems to be a pointer within the heap. Over various runs it's been a pointer within the pool, or one of the slabs. Strange.
a GP fault during an interrupt return, somehow with kernel selectors and rip, but the stack pointer is the user allocated one. Very dangerous. It is in fact the user thread's stack, and it seems to be misaligned +/- 3 bytes sometimes, which is bizzare.

This leaves a few other options I can think of:

We're still allocating a pointer to the inside of the hhdm somewhere, and writing to it, thus writing to random memory.
It's corruption within the stack, some stack allocated buffer being overrun and corrupting things above it. This is possible as the iret_rip field is the first iret field to be accessed when climbing the stack like that. Strange that it leaves the iret_cs field intact though.

Just did a quick test, the memory corruption (page fault issue) still occurs when not user programs are loaded.

With SMAP being fully enabled (at least of the dev branch) I've squashed the GP fault with kernel selectors and a user stack. The page fault still remains however. I have realised I allocated the kernel stack for threads inside of the hhdm, this might be worth looking into. Although that stack isn't used for much, so it seems unlikely.
My bet is still on corruption within the stack somewhere.

Two more points of interest:

bug is not present when running under VMware or VirtualBox, only qemu. I dont have bochs installed so not tested there.
There have been a few cases of page tables getting corrupted, with the data looking like an iret frame to userspace. These are always in the upper 64 bytes or so, which would line up with where the stack would be if that page was used.

Unable to test right now, but we have a use-after-free bug when a thread is freed by the scheduler.
https://github.com/DeanoBurrito/northport/blob/master/kernel/scheduling/Scheduler.cpp#L312

Tentatively fixed in https://github.com/DeanoBurrito/northport/commit/c8c438629337d05d2eefcc4a16b5c8b9c103c011 (currently on dev, not mirrored on master). Leaving this issue open until I can confirm the issue is truly gone.

Seems like there was another stack corruption issue: this one seems to be related to the scheduler. It's present even when no user space programs are run, and will occur randomly over time. Rapid inputs will trigger it to occur faster (mouse movement/key presses). I've only been able to reproduce this on qemu, again. VirtualBox and real hardware work as expected.


Updated the copyright information in the LICENSE file

Changed from "Copyright (c) 2024 [Your Name]" to "Copyright (c) 2024 Nikita Kuzmenko".

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


1064 profile array elements

Type of PR

[x] FEAT

Is your Pull Request linked to an existing Issue or Pull Request?
Solves issue #1064 for DuckDB
Give a brief description for the solution you have provided
Can now profile the individual elements of an array with the DuckDB linker. This is the default behaviour. Can profile the whole array by setting cast_array_as_string= True
Have written a Backend Agnostic Test for this feature (test_profile_arrays_bat). Can edit this and remove test_profile_with_arrays_spark once the feature has been developed in Spark.
PR Checklist

[ ] Added documentation for changes
[ ] Added feature to example notebooks at tutorial in splink_demos (if appropriate)
[x] Added tests (if appropriate)
[ ] Made changes based off the latest version of Splink
[x] Run the linter

I think you can ignore the postgres test failure. I am pretty certain that's now been fixed in master.
You're welcome to perform another rebase if you'd like to check and confirm.

I really like the idea of Splink enabling more types of exploratory data analysis.
There are a few challenges that come to mind from an API/usability point of view that I wondered if we'd considered.  (Also relevant to the profile arrays PR.)
In summary, the challenge is around designing (expanding) the function signature to accomodate complex options.  The input data has many columns of different types, where as the arguments are currently booleans which are not column specific.
To try and explain this a bit better, I think the difficulty arises from:

Input columns of multiple types.   For an input dataset with columns of multiple types, it's challenging to design the function parameters to allow different profiling to be run depending on data type.  Especially because choices are not deterministic:  you don't always want to explode arrays and you don't always want to treat numeric data as continuous.

Data typing.  The existing distribution plots can be used for any data types, but kde and corr can only be used with with continuous numeric data.  This means it's possible to write a function call that is not 'executable' - e.g. asking for a kde on a 'first name'.  At the moment, as far as I know, we don't do any data type checking in Splink, partly because it's hard to implement in a backend-agnostic way.  It might therefore be hard to produce a descriptive error message.

To give a couple of examples of function calls that could be confusing:
# Example 1: Ambiguity in applying distribution and KDE plots when data contains numeric and non numeric
profile_columns(linker, ["first_name", "salary"], distribution_plots=True, kde_plots=True)

# Example 2: Suppose I want a distribution for age (i.e. treat is a nominal/categorical), and a kde plot for log(salary), it's difficult to design
# the function arguments to accomodate without significant complexity  (e.g. list of booleans, or dict like splink_settings)
profile_columns(linker, column_expressions=["age", "log(salary)"],  distribution_plots=True kde_plots=True)

# Example 3: Or when using the function with zero arguments
profile_columns(linker,  distribution_plots = True, kde_plots=True)

I wondered whether we might be at risk of overloading a single function with too many options that make it difficult to use, and potentially hide the useful new functionality.  Could an alternative option be simply to have separate function(s) for numeric and array profiling, and leave the generic profile_columns as distribution only (could even be deprecated)?
(Note: I'm not very sure about the best solution here - it's just one option and there may well be a better one)


pkg/{kvstore,node}: delay node delete event in kvstore

Instead of checking if the node is still present in the observer, we
should check if the node is still present in the store instead. Checking
if the node is still available in the observer is irrelevant as the node
will never be deleted since the check for its existence in the store
will always be true.
Intead, delay the propagation of the deletion event to the observer in
the store itself.
Fixes: 3137ad5eee6c ("node: Delay handling of node delete events received via kvstore")
Signed-off-by: André Martins<EMAIL_ADDRESS>Remove leftover nodes from cilium node list

This change is

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

Coverage increased (+0.004%) to 44.312% when pulling 3abe65b652d8b4506ddadbda20a45cc9dcf63072 on pr/fix-node-delete into 8f860e7d0037849dec90d501ec11a87ec58ee03a on master.


feat: Current orderbook spot price hook

What is the purpose of the change:
This change adds spot price data from the orderbook smart contract. The price is determined by the provided smart contract address and the token in/out pairing (this will swap depending on the order direction).
Spot price is cached for 2 minutes
Linear Task
 LIM-123: Current Orderbook Spot Price
Brief Changelog

Added useOrderbookSpotPrice hook that returns spot price data from the provided orderbook smart contract
Added loading state for spot price loading condition

https://github.com/osmosis-labs/osmosis-frontend/pull/3352
Moved this PR to here to include usage of the spot price


Process exits immediately on Intel OSX

I'm trying to run this library on my 2020 Macbook Pro (Intel).  The process exits as soon as it runs, and I'm not able to enable any verbosity so far as I can tell to further troubleshoot.
Does this work on Intel hardware?  Apologies if these questions are naive.
$ pip3 install aioblescan
< Install is successful with no warnings >
$ sudo python3 -m aioblescan -r
Password:
$
$ python3 -m aioblescan -r
$
$ aioblescan
$
$ sudo aioblescan
$

No output, no nada.

I will have to wait until Monday or later before I can test that on one of my colleagues' Mac, I do not use Mac.
You may need to specify the device  (use -h for help). What does hciconfig reports (if it exists)?
Could be that the kernel/python is not compiled with Bluetooth socket support.
I usually test on Raspberry Pi 4 with Debian and Ubuntu (Kubuntu actually) with and64

Process also exits immediately on Windows it seems, running as admin or not.  Perhaps an error message would be an interim fix? I'll try a Pi another day. If you'd prefer a new issue that is Windows specific let me know and I'll open one.