add 4C community

under Blockchain and Cryptocurrency

I am not sure about the category, I would update the category if you request any changes.

I am not sure about the JSON data since there wasn't any contributing guidelines specific to this.

Server Icon of 4C

compressed according to the guidelines

@mhxion
Please review the PR.

Please remove the contributing guidelines since you are clearly not interested in open-source contributions.


Possible bug on internal method CoerceEmptyStringToNull

Hi,
I was having trouble making JsonNet convert empty strings to null so I decided I would dig into the code.
As it turns out, ther is a method called CoerceEmptyStringToNull, line 343 on JsonSerializerInternalReader.cs file.
I expected this method to convert empty strings to null, but its implementation seems to be faulty.
`
    private static bool CoerceEmptyStringToNull(Type objectType, JsonContract contract, string s)

    {
        var a = string.IsNullOrEmpty(s);

        var b = objectType != null;

        **var c = objectType != typeof(string);**

        var d = objectType != typeof(object);

        var e = contract != null;

        var f = contract.IsNullable;

        return a && b && c && d && e && f;
    }

`
Condition c seems out of place because I suppose we are expecting a string to be converted no null, but if it is a string, c will fail, thus not letting any string ever be converted to null.

The empty string to null coercion is for nullable non-string types (e.g. int?). Actual strings should still be able to have an empty string value.

Thank you, that makes a lot of sense. I wish there was a way to make simple empty strings be coerced to null too.


Docs

Need
As a developer
I want to have docs about everything
So that the users don't bother me with questions

Deliverables

[x] webdriverIO adapter
[x] looksame adapter userOptions
[x] doc page about how to write your own adapter

Solution
Write & review

@andrei-picus-hs please review, if you have other places where docs should be added, update the deliverables. thanks

@andrei-picus-hs I have added the docs for the webdriverio and looks-same adapters. I also have created the wiki page for Writing  your own adapter.
The wiki has also created a Home page, I guess it is default. We can populate it with the README.md, is that ok ?
I was also thinking it would be great to do a video tutorial, when I write the casper adapter. Of course I will write it before, review etc., and then do the tutorial :laughing: Or you can do it yourself if you want, but it would be very cool and useful I think. let me know :smiley:

The wiki has also created a Home page, I guess it is default. We can populate it with the README.md, is that ok ?

We don't want to maintain 2 pages with the same information. You can leave it like it is right now or you could add a simple helper text e.g. 'use the links on the right to find out stuff'.

I was also thinking it would be great to do a video tutorial, when I write the casper adapter
it would be very cool and useful I think

Don't know :confused: we can talk about this at some point.

I have added 2 phrases on the homepage.
I have turned exemplification into example.
I have add some more docs to the LooksSame Adapter.

Don't know :confused: we can talk about this at some point.

Sure, it is just an idea.

done. What tool is used to create the docs from the JSDoc annotations ? It would be good to create the documentation and to browse it a little bit. This way we can figure out if something is missing.

@andrei-picus-hs please review :smile:

LGTM


Failed on Windows

Any idea what's going on with Windows? Googling the error hasn't been helpful, no matter which way I hunt it down.
On a file change, gulp-slang reports a failed upload:
File Upload Failed: 500 - javax.jcr.RepositoryException: Incorrect workspace. Expecting /C. Received crx.default
I've never changed my workspace, and the same setting works on macOS machines.

@rkbrewer I just debugged this for a current project and it ended up being an issue with the way it was searching the path on Windows machines, searching for jcr_root/ and that forward slash would work on Mac, not Windows.
We had it fixed and working with a local package and after prepping a PR into this repo found it was fixed in a later release: https://github.com/mnlsn/gulp-slang/commit/8fcee043ed96afc79fbad4e4e45c438d0b3c7d52 -- Should be safe to use cross environment now.

I'm still experiencing this error File Upload Failed: 500 - javax.jcr.RepositoryException: Incorrect workspace. Expecting /C. Received crx.default on Windows machine, whilst working on Mac.

For me, this was fixed by replacing the slashes in the paths, i.e:
.pipe(gulp.dest('/etc/designs/foxtel-ui/resources/css/'))

.pipe(gulp.dest('\etc\designs\foxtel-ui\resources\css\\'))


concat is redunant

AFAIK, calling concat(a,b) is redundant and can be replaced with:
abi.encodePacked(a,b)
isn't it?

True, this library predates the introduction of the abi object in Solidity and at the date it was super helpful! 😄


Restrict .providerSpecific.location value to enum

Towards https://github.com/giantswarm/roadmap/issues/2573
To avoid bad values (especially unsupported regions), this PR restricts the location value to a set of defined values, taken from https://github.com/giantswarm/capi-image-builder/blob/v1.6.10/helm/capi-image-builder/values.yaml#L48-L52
This also means that when the list in capi-image-builder gets changed, it should be changed here accordingly.
Please check if PR meets these requirements

[x] Results of the diffs have been examined and no unintended changes are being introduced.

Helper

to disable the GH Action generating manifests diffs for installations, between target and source branches, comment the /no_diffs_printing on the PR.

Trigger e2e tests
/run cluster-test-suites

/run cluster-test-suites

heimdall waits until this check is green /run cluster-test-suites, but every time a new commit is added, those checks are gone.

/run cluster-test-suites


Find and group duplicate publications as each new publication is imported

Currently, we import all of the new publication metadata from each data source, then we find and group duplicate publications, and then we hide any duplicated publications. This has become problematic for two reasons:

For the period of time between when the new publication metadata is imported and when the new duplicates are detected and hidden, duplicate publication metadata is visible to end users.

This series of three steps that operate on all of the publication metadata in bulk makes it a lot more difficult to completely automate a scheduled import of new publication metadata from each data source.

These two problems would be solved by modifying each publication importer so that they detect and hide duplicates of each new publication record that they import as each new record is imported.
This will require updating the following importers:

activity_insight_importer.rb
pure_publication_importer.rb
web_of_science_file_importer.rb
oai_importer.rb

Done for
activity insight import
law school import

This is done for Pure now as well. However, we'll still need to make this change for the Web of Science import if we're going to import any more new data from files:  https://github.com/psu-stewardship/researcher-metadata/issues/149


feat: Support "via" in json output format

Is your feature request related to a problem? Please describe.
Lovely and text outputs have a "via" location. This helps when using modules, because the location points to the module's internal code. As far I could see, all other formats only outputs the "internal" location. Adding the "via" to other formats (specifically json) could helps in tooling and automations.
Describe the solution you'd like
A new field in the json output with the content similar to "via" from the lovely output.
Describe alternatives you've considered
None.
Additional context
Lovely output example:
  terraform-aws-modules/s3-bucket/aws/<REDACTED>/.terraform/modules/cf_log_bucket/main.tf:5-263
   via frontend.tf:92-122 (module.cf_log_bucket)

Json output example:
{
	"rule_id": "AVD-AWS-0088",
	"long_id": "aws-s3-enable-bucket-encryption",
	"rule_description": "Unencrypted S3 bucket.",
	"rule_provider": "aws",
	"rule_service": "s3",
	"impact": "The bucket objects could be read if compromised",
	"resolution": "Configure bucket encryption",
	"links": [
		"https://aquasecurity.github.io/tfsec/v1.21.0/checks/aws/s3/enable-bucket-encryption/",
		"https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket#enable-default-server-side-encryption"
	],
	"description": "Bucket does not have encryption enabled",
	"severity": "HIGH",
	"warning": false,
	"status": 0,
	"resource": "module.cf_log_bucket",
	"location": {
		"filename": "terraform-aws-modules/s3-bucket/aws/<REDACTED>/.terraform/modules/cf_log_bucket/main.tf",
		"start_line": 5,
		"end_line": 263
	}
}

This would be a nice way to provide better feedback in the IDE plugins when changing a module's input would resolve a rule failure.

I think this issue belongs in the aquasecurity/defsec repository which defines all the formatters that this repository uses.

@simar7, this issue can also be closed since https://github.com/aquasecurity/defsec/pull/1383 has implemented this feature request.
However, I am not sure whether there would be a new release for tfsec at this time since tfsec is joining the Trivy family.

This is now supported in Trivy as our efforts have moved to it. The work is being tracked here https://github.com/aquasecurity/trivy/issues/4581


[v1.12] docs: Ignore Helm values, update spelling list

This is the 1.12 equivalent to https://github.com/cilium/cilium/pull/26906.

[x] #26759 (@qmonnet)
[x] https://github.com/cilium/cilium/pull/24099 (@qmonnet)
[ ] https://github.com/cilium/cilium/pull/23752 (@squeed)
[x] https://github.com/cilium/cilium/pull/24014 (@qmonnet)
[ ] https://github.com/cilium/cilium/pull/26892 (@geakstr)
[x] https://github.com/cilium/cilium/pull/20978 (@qmonnet)
[x] https://github.com/cilium/cilium/pull/20997 (@qmonnet)

+ Partial backport for the following PRs (not labelled as backported, since we backport only a minor portion of the changes):

[ ] https://github.com/cilium/cilium/pull/24895 (@tklauser)
[ ] https://github.com/cilium/cilium/pull/24717 (@joestringer)
[ ] https://github.com/cilium/cilium/pull/22979 (@jrajahalme)
[ ] https://github.com/cilium/cilium/pull/22219 (@joestringer)

Cc @gandro
Once this PR is merged, you can update the PR labels via:
for pr in 26759 24099 23752 24014 26892 20978 20997; do contrib/backporting/set-labels.py $pr done 1.13; done

or with
make add-labels BRANCH=v1.13 ISSUES=26759,24099,23752,24014,26892,20978,20997

(No need to run the full CI for documentation-only changes by the way 😄)


Theme not applied with ruby 3?

Hi,
I have a custom theme, which works fine with ruby 2. With ruby 3, the theme does not seem to be applied at all.
Dockerfile:
FROM ruby:alpine

WORKDIR /src
CMD sh

COPY theme /theme/
COPY asciidoctor-pdf /

RUN gem install rouge -v 3.6.0
RUN gem install asciidoctor-pdf --pre

Currently, this is
/src # /usr/local/bundle/bin/asciidoctor-pdf --version
Asciidoctor PDF 1.5.0.alpha.16 using Asciidoctor 2.0.15 [https://asciidoctor.org]
Runtime Environment (ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux-musl]) (lc:UTF-8 fs:UTF-8 in
:UTF-8 ex:UTF-8)

/asciidoctor-pdf is just a frontend to add required args to the invocation, essentially:
/usr/local/bundle/bin/asciidoctor-pdf \
  -a pdf-fontsdir=/theme/Font \
  -a pdf-themesdir=/theme/Theme/ -a pdf-theme=kdo -a icons=font@ "$*"

/theme is:
/theme/
├── Font
│   ├── rotis-sans-serif-bold.TTF
│   ├── rotis-sans-serif-exbd.TTF
│   ├── rotis-sans-serif-italic.TTF
│   ├── rotis-sans-serif-light.TTF
│   ├── rotis-sans-serif-light_italic.TTF
│   └── rotis-sans-serif-normal.TTF
├── Icons
│   └── square.png
├── Templates
│   ├── kdo-footer-kurz.adoc
│   ├── kdo-footer-mit-cl.adoc
│   ├── kdo-footer.adoc
│   └── locale
│       └── attributes.adoc
└── Theme
    ├── KDO-Logo-RGB.png
    ├── digit-cluster-small.png
    ├── kdo-background-page.png
    ├── kdo-background-title.png
    ├── kdo-kurz-theme.yml
    ├── kdo-theme.yml
    └── kdo.rb

Running this, I get
/theme/Font/notoserif-regular-subset.ttf not found
  Use --trace for backtrace

but notoserif is not at all used in my theme.
Why isn't asciidoctor-pdf applying my theme?

The version of Asciidoctor PDF you are using is substantially out of date (and also an alpha version). The current stable version is 1.5.4. Please upgrade and you will find that this likely fixes your error.
If you want to use a Docker container that has the correct version of Asciidoctor PDF already available, consider using the Antora Docker container.

Ok, I actually didn't realize that using --pre would install such an old version. I tried this as suggested in https://github.com/asciidoctor/asciidoctor-pdf/issues/1870#issuecomment-770520162 in order to get a version compatible with ruby 3.
The Dockerfile was just my way of trying to provide a concise description of my environment. My real deploy target is fedora 34, which ships ruby 3.
I think it might be a good idea, to add a more clear warning that as of now, no (current) asciidoctor-pdf gem is compatible with ruby 3. Would have saved at least me a couple of hours an might save you from further issues. I'd suspect, more people will be getting problems due to more linux distros switching to ruby 3.
Any ETA when 2.0 or maybe a preview will be available as a gem?
Thanks for an otherwise great product.

I tried this as suggested in #1870 (comment) in order to get a version compatible with ruby 3.

As I stated in that thread, the only way to get Ruby 3 support is to use the code from the main branch.

I think it might be a good idea, to add a more clear warning that as of now, no (current) asciidoctor-pdf gem is compatible with ruby 3.

The warning is the first item under known limitations in the README. https://github.com/asciidoctor/asciidoctor-pdf/tree/v1.5.x#known-limitations I don't know how to be any more clear.

Any ETA when 2.0 or maybe a preview will be available as a gem?

I can't give you a time, but I can say that I am treating it as a priority and will do it as soon as I can do it.


a vim bundle 504

the script want to download a bundle from http://www.vim.org/scripts/download_script.php?src_id=13400 , but got  504

maybe a network error, try times , it is ok


upgrade openssl and removed automate-ha-elasticsearch component

:nut_and_bolt: Description: What code changed, and why?

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist
All PRs must tick these:

[ ] I have read the CONTRIBUTING document.
[ ] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

created another one: https://github.com/chef/automate/pull/8536


add bot.logger.error() to all keywords, slash commands and message commands

Ok a lot of things were updated here, mostly pertaining to error logging in the development server.


Not able to access the document "SONiC-OTN HLD and plan summary.pdf"

Hi,
Can someone from community help here? I am getting error while accessing "documentation/SONiC-OTN HLD and plan summary.pdf"

Is there  a prompt message "Unable to render code block"?  Maybe it gets something wrong, but you can still download the pdf file by clicking the button on the right. If no reaction, just try again in a few minutes.


using stream-lua-nginx-module not prints log

when I use stream-lua-nginx-module proxy port to zookeeper port 2181，The code is as follows：
worker_processes  1;
error_log  logs/error.log;
events {
    worker_connections  1024;
}
stream {
        upstream backend {
            server <IP_ADDRESS>:2181;
        }
        server {
            listen *:14330;
            content_by_lua_block {
                ngx.log(ngx.ERR, "=========ngx: "..<PHONE_NUMBER>333)
                ngx.say("Hello, Lua!")
            }
            proxy_pass backend;
        }
}

port 2181  is zookeeper's port,  when I  run command   nc <IP_ADDRESS> 14330 ，There is no such a result： Hello, Lua!
，also， error.log has not log:
=========ngx:<PHONE_NUMBER>333.

however，I modified the server code as follows：
server {
            listen *:14330;
            content_by_lua_block {
                ngx.log(ngx.ERR, "=========ngx: "..<PHONE_NUMBER>333)
                ngx.say("Hello, Lua!")
            }
            #proxy_pass backend;
 }

when I  also run   nc <IP_ADDRESS> 14330  ， There is such a result： Hello, Lua!
error.log has  log：
2018/05/05 21:12:25 [error] 17512#16888: *27 stream [lua] content_by_lua(nginx.conf:15):2: =========ngx:<PHONE_NUMBER>333, client: <IP_ADDRESS>, server: <IP_ADDRESS>:14330

Why is there no print log in the first case？

Thank you for your answer, it's really helpful for me.

@dndx
Hello,
I still have some questions as follows, look forward to your replay:

preread_by_lua_block phase is preread,  order of lua nginx model directives: Initalization phase--->Rewrite/Access phase ---> Content phase ---> Log phase,
so does the  preread phase run between Rewrite/Access phase and Content phase ?

2.Can there be only one handler at each phase ? For example, there is only one between proxy_pass and content_by_lua_block at content phase.

@xiongmaodada

The phase order for the stream subsystem is slightly different from http subsystem. You can check out a presentation I made at OpenResty Con 2017 for some detailed explanation: https://con.openresty.org/cn/2017/books/Intruduction to the NGINX stream subsystem and OpenResty's support.pdf
Content phase is unique as it can have only one handler. Other phases, such as preread, can have multiple handlers.
That really depends on the implementation of the directive and it is hard to provide an exhaustive list of this. But as far as the standard modules inside stream subsystem, I believe the proxy module and return module are the only two that uses content handlers.

Thank you ！！！


[Bug] Worker hangs after polling workflow task queue

What are you really trying to do?
To connect a worker to a Temporal server with an authorization header.
Describe the bug
Starting a worker with an incorrect token, causing the server to respond with Request unauthorized, causes the worker to hang indefinitely.
Minimal Reproduction
import asyncio

from temporalio import activity, client, workflow, worker

@activity.defn
async def a() -> None:
    pass

@workflow.defn
class Workflow:
    @workflow.run
    async def run(self) -> None:
        pass

async def main():
    c = await client.Client.connect(
        "my_temporal_host:7233",
        rpc_metadata={"authorization": "wrong_token"},
        tls=True,
    )
    w = worker.Worker(
        c,
        task_queue="default",
        activities=[a],
        workflows=[Workflow],
    )
    await w.run()

if __name__ == "__main__":
    asyncio.run(main())

Output:
2024-09-03T07:26:48.707Z [temporal-worker] 2024-09-03T07:26:48.707200Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 52 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:26:48 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:26:49.544Z [temporal-worker] 2024-09-03T07:26:49.544345Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 52 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:26:49 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:27:51.707Z [temporal-worker] 2024-09-03T07:27:51.707200Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 53 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:27:51 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:27:52.968Z [temporal-worker] 2024-09-03T07:27:52.967933Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 52 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:27:52 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:00.036Z [temporal-worker] 2024-09-03T07:28:00.036155Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 53 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:00 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:00.687Z [temporal-worker] 2024-09-03T07:28:00.687484Z ERROR temporal_client::retry: gRPC call poll_workflow_task_queue retried 53 times error=Status { code: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:00 GMT", "content-type": "text/html", "content-length": "160", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:03.579Z [temporal-worker] 2024-09-03T07:28:03.578940Z  WARN temporal_sdk_core::worker::workflow::wft_poller: Error while polling for workflow tasks error=Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:03 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:03.970Z [temporal-worker] 2024-09-03T07:28:03.583738Z ERROR temporal_sdk_core::worker::workflow::workflow_stream: Workflow processing encountered fatal error and must shut down TonicError(Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:03 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None })
2024-09-03T07:28:03.970Z [temporal-worker] 2024-09-03T07:28:03.969933Z  WARN temporal_sdk_core::worker::workflow::wft_poller: Error while polling for workflow tasks error=Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:03 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:03.970Z [temporal-worker] 2024-09-03T07:28:03.969960Z ERROR temporal_sdk_core::worker::workflow::workflow_stream: Workflow processing encountered fatal error and must shut down TonicError(Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:03 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None })
2024-09-03T07:28:04.023Z [temporal-worker] Worker failed, shutting down
2024-09-03T07:28:04.023Z [temporal-worker] Traceback (most recent call last):
2024-09-03T07:28:04.023Z [temporal-worker]   File "/lib/python3.10/site-packages/temporalio/worker/_workflow.py", line 143, in run
2024-09-03T07:28:04.023Z [temporal-worker]     act = await self._bridge_worker().poll_workflow_activation()
2024-09-03T07:28:04.023Z [temporal-worker]   File "/lib/python3.10/site-packages/temporalio/bridge/worker.py", line 141, in poll_workflow_activation
2024-09-03T07:28:04.023Z [temporal-worker]     await self._ref.poll_workflow_activation()
2024-09-03T07:28:04.023Z [temporal-worker] RuntimeError: Poll failure: Unhandled grpc error when workflow polling: Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Tue, 03 Sep 2024 07:28:03 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }
2024-09-03T07:28:04.023Z [temporal-worker]
2024-09-03T07:28:04.023Z [temporal-worker] The above exception was the direct cause of the following exception:
2024-09-03T07:28:04.023Z [temporal-worker]
2024-09-03T07:28:04.023Z [temporal-worker] Traceback (most recent call last):
2024-09-03T07:28:04.023Z [temporal-worker]   File "/lib/python3.10/site-packages/temporalio/worker/_workflow.py", line 153, in run
2024-09-03T07:28:04.023Z [temporal-worker]     raise RuntimeError("Workflow worker failed") from err
2024-09-03T07:28:04.023Z [temporal-worker] RuntimeError: Workflow worker failed

Environment/Versions

Temporal Version: Server v1.23.1, SDK v1.7.0

Additional context
Related issue: #459

causes the worker to hang indefinitely.

We do check that the worker can connect to the namespace using "describe namespace". So you have a token that works on some calls but not others? Is this self-hosted or cloud?
The stack trace seems to be showing it raising an exception. Are you sure that worker.run() does not raise an exception here? It does take a minute because we retry all polling errors just in case they are spurious.

This issue is two-fold, I reported the one relevant to the SDK here:

I have a worker which sends the correct token to a self-hosted Temporal server (v1.23.1). There is an issue at the ingress level which sometimes causes the server to respond with a 504 Bad Gateway.
As the worker continues to receive this response from the ingress, it exhibits the behavior reported in this bug, eventually hanging and failing to re-connect.

The second issue is what i'm reporting here. The worker ends up raising a RuntimeError and not recovering from it.

The worker ends up raising a RuntimeError and not recovering from it.

Some client errors we can detect as recoverable. For ones we can't, we still try to recover for a minute before failing the worker. We intentionally fail the worker instead of letting it operate in a failed state on something that is not quickly recoverable. Can you confirm whether worker.run() does or does not raise an exception here? We start a worker shutdown, but a worker shutdown sends cancellation to activities and has to wait for activities to complete (see https://github.com/temporalio/sdk-python?tab=readme-ov-file#worker-shutdown).

I'm not sure if you're referring to something different, but the logs shared in the original bug report show that worker.run() is raising a RuntimeError.

Ah, I see it in the trace now. So this is intentional behavior. A fatal error (or at least one we can't tell is non-fatal) that doesn't fix itself after a minute will cause the worker to fail and shutdown instead of pretending to work silently while continuing to fail. You may restart the worker if you wish, though many prefer not to blindly restart but rather investigate.

In our case the worker is failing after a number of intermittent network issues, so we would rather it restarts instead. Is there any recommendation around how to restarting the worker? I tried a simple while True loop to catch the RuntimeError exception raised and re-run await worker.run(), which seemed to complain (I don't have the logs from that right now but I can get them).

I tried a simple while True loop

This should work. Similarly you can consider having whatever is monitoring the process/pod/container do the restart at an outer level.

I did try the following to retry the worker:
    while True:
        try:
            await worker.run()
        except RuntimeError as e:
            print(f"RuntimeError caught: {e}. Retrying...")
            await asyncio.sleep(5)  # wait for 5 seconds before retrying
        except Exception as e:
            print(f"An unexpected error occurred: {e}")
            raise

After running for a while, the worker crashed with the following error when trying to restart:
  File "/home/kelkawi/.cache/pypoetry/virtualenvs/boarding-w3anQpca-py3.10/lib/python3.10/site-packages/temporalio/worker/_workflow.py", line 143, in run
    act = await self._bridge_worker().poll_workflow_activation()
  File "/home/kelkawi/.cache/pypoetry/virtualenvs/boarding-w3anQpca-py3.10/lib/python3.10/site-packages/temporalio/bridge/worker.py", line 141, in poll_workflow_activation
    await self._ref.poll_workflow_activation()
RuntimeError: Poll failure: Unhandled grpc error when workflow polling: Status { code: PermissionDenied, message: "Request unauthorized.", details: b"\x08\x07\x12\x15Request unauthorized.\x1aJ\nHtype.googleapis.com/temporal.api.errordetails.v1.PermissionDeniedFailure", metadata: MetadataMap { headers: {"date": "Thu, 05 Sep 2024 09:43:21 GMT", "content-type": "application/grpc", "content-length": "0", "strict-transport-security": "max-age=15724800; includeSubDomains"} }, source: None }

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/kelkawi/.cache/pypoetry/virtualenvs/boarding-w3anQpca-py3.10/lib/python3.10/site-packages/temporalio/worker/_workflow.py", line 153, in run
    raise RuntimeError("Workflow worker failed") from err
RuntimeError: Workflow worker failed
RuntimeError caught: Workflow worker failed. Retrying...
An unexpected error occurred: 'NoneType' object has no attribute 'validate'
Traceback (most recent call last):
  File "/home/kelkawi/Desktop/CanonicalRepos/hr-automation/boarding/worker.py", line 219, in <module>
    asyncio.run(run_worker())
  File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/home/kelkawi/Desktop/CanonicalRepos/hr-automation/boarding/worker.py", line 207, in run_worker
    await worker.run()
  File "/home/kelkawi/.cache/pypoetry/virtualenvs/boarding-w3anQpca-py3.10/lib/python3.10/site-packages/temporalio/worker/_worker.py", line 478, in run
    await self._bridge_worker.validate()
  File "/home/kelkawi/.cache/pypoetry/virtualenvs/boarding-w3anQpca-py3.10/lib/python3.10/site-packages/temporalio/bridge/worker.py", line 133, in validate
    await self._ref.validate()
AttributeError: 'NoneType' object has no attribute 'validate'

A worker is meant for one run/shutdown. If you want to run a new worker you will need to recreate it again. Unfortunately some validation we added is happening before this check, we will fix that.


If your girlfriend is a programmer and uses GitHub try this on her.
I guarantee that she'll love you for it.

Because i would like to reverse engineer your interiour with my dongle.


feat: support named exports in ESM/TS

This adds support for named exports in ESM (whether it be TS or not).
For example:
export const rule: RuleModule = {
  create: () => { ... };
};

Also, exported symbols:
const rule = { ... };

export {rule};

While ESLint plugins are still usually CJS at time of writing this, many are written as ESM sources, and an increasing number are using named exports.
Reviewer notes
You'll want to hide whitespace changes when reviewing this, as prettier reformatted a bunch of it thanks to changing the level of nesting/chaining.
Fixes #375

Thanks for the quick review @bmish , I'll sort the changes tomorrow 👍

FYI i have at least resolved the two changes
not sure what you want to do about the testing. since it seems like @aladdin-add already ran the remote tester successfully

@bmish i ran it against:

eslint-plugin-compat
eslint-plugin-jest
TSESLint
eslint-plugin-vue
eslint-plugin-prettier

and all seemed well


Watson times out immediately after pressing the mic button

I accepted the mic prompt before (in Chrome, FF).
App runs on BM.

You need to create a speech to text service on bluemix to enable speech. https://www.ibm.com/watson/developercloud/doc/speech-to-text/

ok, that worked


Manual: Added indexing-based simplification to Multivariate Regression Example

Summary
The Multivariate Regression Example included some optimizations but didn't include the, in my opinion, useful simplification recommended at the beginning of the Multiple Indexing and Range Indexing chapter. My substitution should probably be checked, as the order of variables in the "clunky assignment to a local variable" of the MRE and MIRI sections were different.
Reviewer Suggestions
Copyright and Licensing
I assert no rights with regards to copyright & licensing.

Thanks!  That looks great.  Mitzi and I are going to take a run through all of our models and try to update them as soon as we get the compound declare/define and unary vectorization features in.
If someone lets me know how I can check out this change and make sure the manual builds and the link works, I can merge it.

Jenkins, ok to test.

@bob-carpenter, Jenkins will build the manual for us; I'll put up a link once it's done.
It won't pass all the upstream tests since it the commit isn't on stan-dev/stan, but we can merge once you're satisfied that is passes the manual build.

FYI, found some typos while checking if the model compiles so I fixed these in a couple new commits.

The model won't compile, so something is wrong with how I attempted to apply the solution shown at the beginning of the "Multiple Indexing and Range Indexing" chapter. As it is now, it's complaining about the line "y ~ normal(beta[jj] .* x, sigma);" , because the "beta[jj] .* x" part yields a matrix when it needs to be a real, array of reals, vector or row vector.

If you'd like our help debugging, please include the whole
Stan program that doesn't compile.

@bob-carpenter Oh, I was referring to the model in the manual that my pull affects. Here's the full model:
data {   int<lower=0> N;              // num individuals   int<lower=1> K;              // num ind predictors   int<lower=1> J;              // num groups   int<lower=1> L;              // num group predictors   int<lower=1,upper=J> jj[N];  // group for individual   matrix[N, K] x;               // individual predictors   row_vector[L] u[J];          // group predictors   vector[N] y;                 // outcomes } parameters {   matrix[K, J] z;   cholesky_factor_corr[K] L_Omega;     vector<lower=0,upper=pi()/2>[K] tau_unif;     matrix[L, K] gamma;                         // group coeffs   real<lower=0> sigma;                       // prediction error scale } transformed parameters {   matrix[J, K] beta;   vector<lower=0>[K] tau;     // prior scale   for (k in 1:K) tau[k] = 2.5 * tan(tau_unif[k]);   beta = u * gamma + (diag_pre_multiply(tau,L_Omega) * z)'; } model {   to_vector(z) ~ normal(0, 1);    L_Omega ~ lkj_corr_cholesky(2);   to_vector(gamma) ~ normal(0, 5);   y ~ normal(beta[jj] .* x, sigma); }

I believe I got it to work. It seems that rows_dot_product() is necessary.

Once I got it working, the version using rows_dot_product() was quite a bit faster than the version that created x_beta_jj, so I posted another commit that eliminates use/reference to the latter altogether.

Not sure it's of use to anyone, but I ended up creating an example (r code to generate data, then various stan models to test different approaches) while fixing this:
https://gist.github.com/mike-lawrence/bce5f79852e01c904eaf67405585feb7

Thanks.
I'd suggest changing this declaration:
matrix[nS,nX] Smu ;
to
vector[nX] Smu[nS];
in order to vectorize this
Smu[ns] ~ multi_normal(mu,Z) ;

to
Smu ~ multi_normal(mu, Z);
That'll ensure that Z only has to be factored once.

Bob

On Aug 14, 2016, at 9:31 PM, Mike Lawrence<EMAIL_ADDRESS>wrote:
Not sure it's of use to anyone, but I ended up creating an example (r code to generate data, then various stan models to test different approaches) while fixing this:
https://gist.github.com/mike-lawrence/bce5f79852e01c904eaf67405585feb7
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@bob-carpenter unfortunately rows_dot_product() needs Smu to be a matrix. Your suggestion also breaks the hmod_c0 version that creates a variable q instead of using rows_dot_product().

If you need those matrix operations, it'd still be
better to copy the final matrix Smu into a local variable that is
an array of vectors before calling multi_normal.  Way
faster than factoring the matrix in each loop iteration.
We should really add the matrix call.  It wouldn't be hard,
but we have quite a few of these convenience additions stacked
up, so I don't know when we'll get to it.

Bob

On Aug 15, 2016, at 12:21 AM, Mike Lawrence<EMAIL_ADDRESS>wrote:
@bob-carpenter unfortunately rows_dot_product() needs Smu to be a matrix. Your suggestion also breaks the hmod_c0 version that creates a variable q instead of using rows_dot_product().
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

For your suggestion of creating a copy into a local variable that is an array of vectors, would this be what you're thinking?
{
vector[nX] temp[nS] ;
for(ns in 1:nS){
temp[ns] = Smu[ns]' ;
}
temp ~ multi_normal(mu,Z) ;
}

Exactly.
Though if efficiency is a concern, it might be
better to do the transpose, then copy the columns,
because Eigen presumably does the transposes more
efficiently using blocking rather than going one row/column
at a time, which is a big memory locality hit (memory locality
and branch misprediction are the main causes of inefficienty
for code on modern CPUs.  Stan instantiates Eigen in the default
way so as to store the matrices in column-major order, so
that Smu.
But I'm not sure if it'll matter for a simple transpose.
{
matrix[nX, nS] Smu_tr;
vector[nX] Smu_tr_arr[nS];
Smu_tr = Smu';
for (n in 1:nS) Smu_tr_arr[n] = Smu_tr[ , n];
Smu_tr_arr ~ multi_normal(mu, Z);
}
Probably not worth the trouble and lack of clarity, even if
it is a bit faster.

Bob

P.S.  Never space before semicolons, always space after commas.
I'm finding our users aren't used to the C/C++/Java conventions,
and their code is therefore very hard to scan for me because
the syntax is such a distraction.
  Also notice that I tried to use meaningful variable names rather
  than "temp".  I figure now that I'm heading down this road, I
  might as well go all the way in syntax/formatting instructions.

  Also, always indent (we recommend two spaces as it's the convention
  in C and C++, but some users like four, which is the convention for Java).

On Aug 15, 2016, at 2:06 AM, Mike Lawrence<EMAIL_ADDRESS>wrote:
For your suggestion of creating a copy into a local variable that is an array of vectors, would this be what you're thinking?
{
vector[nX] temp[nS] ;
for(ns in 1:nS){
temp[ns] = Smu[ns]' ;
}
temp ~ multi_normal(mu,Z) ;
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@bob-carpenter, the test failure is fine. Feel free to merge when you think it's ready.
The built manual isn't persistent on Jenkins, so I think you'll have to build it locally to see if the manual looks right.


Supply app version to contract keeper

Description

closes: #6977
This PR adds the underlying application version to the callback data and propagates it to the contract keeper interface fns.
Added the backport label since it seems like a valuable feature, happy to remove before merging (and update docs) if there's a good reason not to.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

No backport necessary, this should be included in the callbacks release branch (when created)

Thanks @chatton for an elegant solution here!


Fix missing labels on Items without mismatches

This was probably introduced in #444, when overlooking to consider that $mismatches does not contain info about Items that do not have mismatches and so fails to retrieve their labels.
TODO:

[ ] actually try it out
[x] tests
[x] better commit message

Bug: T321977

Would be nice if someone reviewing could also actually try it out locally. My local installation still doesn't work correctly.


Add basic unit tests

Provides basic unit test base to build upon and ensures that coverage figures can now be tracked.

Coverage remained the same at 6.272% when pulling 347792dd50adcd47ceedd4cdbbb414c4ec8d8676 on Echelon9:feature/unit-tests into 5ee662be6b41b306439e7725764dfc448440baf4 on Tigge:master.

Thanks, good to have this up and running for real!


[Improvement][Task] Improved way to collect yarn job's appIds

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Current way to collect appIds is scan log files and parse them, it's inefficient and will cause OOM if log file is large, which has been mentioned in issue#11214. This potential problem can only be permanently solved by changing a new way to collect appIds which avoid reading log files.
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Do you have any good idea? AFAIK, we can use xx task SDK to submit task, and can get the appId from SDK, then we don't need to parse from log. Or we can optimize the currently parse method to avoid OOM.

Yeh, maybe a practicable solution, we can simply talk about it.
Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered.
Please let me know if you have any good suggestions!

@ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it.
Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered.
Please let me know if you have any good suggestions!

@ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it.
Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered.
Please let me know if you have any good suggestions!

In fact, there is already a issue talk about use agent to collect the appId, but I think it isn't a good way 😢

already

@ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it.
Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered.
Please let me know if you have any good suggestions!

In fact, there is already a issue(#4025) talk about use agent to collect the appId, but I think it isn't a good way 😢 , we need to maintain a agent and we may need to maintain different version agant.

I think there's no need to maintain different version agent, for example, we can parse the appId from some environment variables such as APPLICATION_WEB_PROXY_BASE. All yarn jobs' AM maintain this environment variable, i've already verified it in Flink, Spark, Hive, MR, Spark-SQL. The only difference is how to set java options which can be defined in each  type of task.
So, it seems like yarn jobs submitted by shell command can all get appId in this way. Anyway, there are some other design problems, like where to store the mapping relationship, as mentioned in issue(#4025). I'll carefully think about that.

@ruanwenjun
Hi, i wanna ask some maybe dumb question. When worker failover, in the function of killYarnJob, the logic is send a view log request to worker and then parse it. However, worker is just the client to submit yarn job, the worker failover will not auto-kill submitted yarn jobs, so in the situation that worker is failover and how can it response the log info?

@ruanwenjun Hi, i wanna ask some maybe dumb question. When worker failover, in the function of killYarnJob, the logic is send a view log request to worker and then parse it. However, worker is just the client to submit yarn job, the worker failover will not auto-kill submitted yarn jobs, so in the situation that worker is failover and how can it response the log info?
Feel sorry that i don't have the production environment, so I'm not sure whether it's a bug or i understand it wrong.

This is a history issue, in the before, there exist a LogServer deploy at the worker's machine.

already

@ruanwenjun Yeh, maybe a practicable solution, we can simply talk about it.
Before submitting a yarn job, the client apply the application context from RM first, and get appId which will be then written into NM's environment variable. We can use java agent to read it before executing yarn job's JAR file, also, can take taskInstanceId as input of agent program. However, where to store this mapping relationship need to be further considered.
Please let me know if you have any good suggestions!

In fact, there is already a issue(#4025) talk about use agent to collect the appId, but I think it isn't a good way 😢 , we need to maintain a agent and we may need to maintain different version agant.

I think there's no need to maintain different version agent, for example, we can parse the appId from some environment variables such as APPLICATION_WEB_PROXY_BASE. All yarn jobs' AM maintain this environment variable, i've already verified it in Flink, Spark, Hive, MR, Spark-SQL. The only difference is how to set java options which can be defined in each type of task.
So, it seems like yarn jobs submitted by shell command can all get appId in this way. Anyway, there are some other design problems, like where to store the mapping relationship, as mentioned in issue(#4025). I'll carefully think about that.

You need to make sure the agent can work for all yarn client.

@ruanwenjun  I think most of yarn clients can share the same agent, cuz in these clients, AOP will intercept func submitApplication, except for submitting yarn job with JDBC connection, like beeline(hive server2, as mentioned in issue(https://github.com/apache/dolphinscheduler/issues/4025)), however, beeline may create an external JDBC connection, we can not kill an external yarn job, right? So, if we don't consider these special situations, we can use the same agent for all other yarn clients.

Hi, @Radeity @ruanwenjun
I agree that the current way of getting the yarn application id from the log is not elegant.
Just for discussion, there is another way to get yarn application id as below:
We can put some unique tags on tasks submitted from DS to yarn. E.g., for spark tasks, we can add the configuration --conf spark.yarn.tags some_unique_tag.
After the task is submitted, DS can query the corresponding yarn application id (or other info) through this unique tag.
What do you think? Any comments or discussions are welcome.

Hi, Rick
First, thanks for your idea!
However, i think this way have two problems as follow:

Users may create ShellTask and submit not only one yarn job via command
lines which is hard to add configuration.
Aop way will simply fetch applicationId and write it into appInfo.log
file. I think it's maybe more efficiency than query it through unique tag.
In fact, I don't get how your idea work? Would you like to explain more
about it?

Best wishes
rickchengx @.***> 于2022年9月23日周五 14:35写道：

Hi, @Radeity https://github.com/Radeity @ruanwenjun
https://github.com/ruanwenjun
I agree that the current way of getting the yarn application id from the
log is not elegant.
Just for discussion, there is another way to get yarn application id as
below:
We can put some unique tags on tasks submitted from DS to yarn. E.g.,
for spark tasks, we can add the configuration --conf spark.yarn.tags
some_unique_tag.
After the task is submitted, DS can query the corresponding yarn
application id (or other info) through this unique tag.
What do you think? Any comments or discussions are welcome.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/dolphinscheduler/issues/11262#issuecomment-1255845285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKY23YTHFBEZSS7FEWPLJ4TV7VFTTANCNFSM55KW2JOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi, @Radeity @ruanwenjun
I agree that the current way of getting the yarn application id from the log is not elegant. Just for discussion, there is another way to get yarn application id as below:

We can put some unique tags on tasks submitted from DS to yarn. E.g., for spark tasks, we can add the configuration --conf spark.yarn.tags some_unique_tag.
After the task is submitted, DS can query the corresponding yarn application id (or other info) through this unique tag.

What do you think? Any comments or discussions are welcome.

Hi, @rickchengx
First, thanks for your idea!
However, i think this way have two problems as follow:

Users may create ShellTask and submit not only one yarn job via command lines which is hard to add configuration.
Aop way will simply fetch applicationId and write it into appInfo.log file. I think it's maybe more efficiency than query it through unique tag. In fact, I don't get how your idea work? Would you like to explain more about it?

My best wishes.

@Radeity , thanks for the reply.
Here is more info about the way by tagging:

DS can add some unique tags while building the command of yarn tasks (spark, flink, sqoop, mapreduce, etc.) But ShellTask is not included because DS is not responsible for building commands in shell task. The tag is automatically added by DS, and the user is unaware of it.
After the task is submitted, DS can query the corresponding yarn application id (or other info) through this unique tag.Specifically, through a yarn client.

@rickchengx
Thanks for your detailed explanation.
Compared with the tag way, aop can handle shell task, in addition, not invade into DS task definition code. Also, an additional jar package is required, you're right, however, this temporary appInfo log file is just for fetching applicationId in time, when the task is done, appId will be written into TaskExecutionContext as same as original way.
Moreover, extra maintenance is only need when compute engines change their supported way to add configuration like java-opts or yarn client change its submit function which i really think not a big deal, cuz they have remained unchanged for many years. Think of, for example, Wechat pay has been used for many years and we can scan QR code to pay for something, it's already in widely use and will not suffer a sudden change. Anyway, i have to say, yarn client may update, new compute engine will come out,  but for this aop way in DS, the cost of potential maintenance is relatively smaller enough than other code part, such as generated command line to submit spark task.
For the last point, i agree with you, stability is worth considering.  For smooth transmition, my opinion is to keep both original and new aop way, provide extra configuration for user to choose how to fetch applicationId. If the aop way is stable enough, we can then consider whether to complete replace the original way.
What do you think of it? I'll be appreciated if you have any more elegant idea!


Add: Followed version 1.68 of Japanese display

@tkusano @dolciss @oboenikui @noritada
The version of the Japanese display has been updated to 1.68, and the update has been made to follow.
One concern is the dark mode setting.
Please refer to this page for the intention of "Dim" and "Dark": https://github.com/bluesky-social/social-app/pull/2722#issue-2111197246

#: src/view/com/modals/SelfLabel.tsx:95
msgid "Suggestive"
msgstr "きわどい"

Dim" is set to "グレー".
If "Dim" is set to "薄暗い", it will not match the katakana used in System/Light/Dark, and it will look strange.
Instead, "薄暗い" is indicated in the message displayed in the lower right corner of the window when selected, to supplement the setting.

240603d
https://bsky.app/profile/bosturbo.bsky.social/post/3kkvmt5nihh2x

By the way, why does the "Lint / Run linters (pull_request)" check throw an error? I don't think anything strange has been done, so I hope it will be fixed when the merge is done.

A mistake we introduced, don't worry about it!


Docker Build Steps Update

Docker Build now runs from local paths instead of cloned external repositories
Docker Tag now only tags master branch builds with latest
Docker Push, pushes all tags.

This run of the pipeline built and pushed branch tags only
note commit hash d304fcf

ECR doesn't show push tagged as latest

This run of the pipeline built and pushed branch tags and latest
note commit hash 1e6575a

ECR shows push tagged as branch tag and latest

CasperJS Suite run from local and passed


[WIP] Unified dApp API for wallet providers

This PR is to gather feedback, and will be closed before the real PR is submitted to the main repo.

NEO supports struct in a storage value. I think maybe it's better to return an object ?
https://github.com/nickfujita/proposals/blob/9303ac8aa6bd8652b14a65da9bc8193cd3084e37/nep-dapi.mediawiki#getstorage

NEO supports struct in a storage value. I think maybe it's better to return an object ?
https://github.com/nickfujita/proposals/blob/9303ac8aa6bd8652b14a65da9bc8193cd3084e37/nep-dapi.mediawiki#getstorage

Is the struct returned in a parsed format or the hexstring format from the RPC node?

oh it probably always returns hex string from the node.
then a dapp would have to know it beforehand what is the type of the returning value to properly parse it.
e.g.
{
  "jsonrpc": "2.0",
  "method": "getstorage",
  "params": ["7c1de0a1fba67cbddbfea27aed370ff2ff35e8b2","696e5f63697263756c6174696f6e"],
  "id": 1
}

return this
{
	"jsonrpc": "2.0",
	"id": 1,
	"result": "00cdf4d0bed758"
}

another minor thing, should there be a website field in provider info?
interface Provider {
  name: string;
  version: string;
  compatibility: string[];
}

other than that everything looks good to me for the base protocol level then It's up to the provider to provide more useful functions in the package.
👍


Discussion: Microsoft Security Advisory CVE-2019-0564: ASP.NET Core Denial of Service Vulnerability

Microsoft Security Advisory CVE-2019-0564: ASP.NET Core Denial of Service Vulnerability
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Microsoft is aware of a denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.
A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core application.
System administrators are advised to update PowerShell Core to an unaffected version version (see affected software.)
Discussion
Please use aspnet/AspNetCore#6487 for discussion of the .NET aspects this advisory.
Affected Software
The vulnerability affects PowerShell Core prior to the following versions:

PowerShell Core Version
Fixed in

6.1
6.1.2

6.2
TBD

Advisory FAQ
How do I know if I am affected?
If all of the following are true:

Run pwsh -v, then, check the version in the table in Affected Software to see if your version of PowerShell Core is affected.
If you are running a version of PowerShell Core where the executable is not pwsh or pwsh.exe, then you are affected.  This only existed for preview version of 6.0.
You use System.Net.WebSockets.dll.

How do I update to an unaffected version?
Follow the instructions at Installing PowerShell Core to install the latest version of PowerShell Core.
Other Information
Reporting Security Issues
If you have found a potential security issue in PowerShell Core,
please email details to<EMAIL_ADDRESS>Support
You can ask questions about this issue on GitHub in the PowerShell organization.
This is located at https://github.com/PowerShell/.
The Announcements repo (https://github.com/PowerShell/Announcements)
will contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.
What if the update breaks my script or module?
You can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core.
This should be treated as a temporary measure.
Therefore, the script or module should be updated to work with the patched version of PowerShell Core.
Acknowledgments
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See acknowledgments for more information.
External Links
CVE-2019-0564
Revisions
V1.0 (Jan 15, 2019): Advisory published.
Version 1.0
Last Updated 2019-01-15

@TravisEz13 what do you think about moving this issue to a discussion?


user-agent change

Hi,
According to that article:
[(http://searchnewscentral.com/20110928186/General-SEO/how-to-scrape-search-engines-without-pissing-them-off.html)]
it seems that a scraper is less likely to be blocked if it uses a different user-agent.
For slow/small scraping, I think it would be a good idea to implement that;
having an updatable list of different user-agent and query Google with random UA.
What do you think ?

I think it's a common belief. Unless someone give me serious proof using differents user agents allow to scrap more without blocked, I won't implement this feature. There is so much more important thing to do now. But maybe later.


Minor gripe: straight-process buffer contains peaceful failures

Just did a big update and now every time I boot up emacs I see this in *straight-process*:
$ cd /home/sjung/.emacs.d/straight/repos/epkgs/
$ git config --file .gitmodules --get submodule.let-alist.url

[Return code: 1]

$ cd /home/sjung/.emacs.d/straight/repos/epkgs/
$ git config --file .gitmodules --get submodule.let-alist.url

[Return code: 1]

spent a while debugging it before realizing that this really isn't even an error (let-alist is a built-in). This has probably always had a nonzero return code, but wasn't opening a buffer for it until now. I would prefer to only see this buffer spawned for genuine breakages that need my attention.

Was the buffer displayed in a popup? If so, it shouldn't be. If not, why were you looking at it?
*straight-process* is always created. It logs all external processes that were run; it's not just a tool for presenting errors to the user.
If you dislike the buffer showing up in your buffer list, maybe consider this?
(setq straight-process-buffer " *straight-process*")

Suggestions welcome.

ahh, I understand. I figured it was an error buffer because that was the only output in it. I'm cool with this.


Review issues and PRs in original rickfast/consul-client

Review the issues and open PRs in the original consul-client library to see if there is anything there that we should address.

Issues:

Issue
Title
Resolution
Notes

473
ServiceHealth deserialize failed
Won't Fix
There is a test for this and it passes, so ignoring this report. It doesn't make sense that a service would not have a port.

469
Open CVEs against consul-client 1.5.3
Fixed
We have updated well beyond all the versions with CVEs

462
Update okhttp to version 4.9.2
Fixed
We are using version 4.11.0

458
Recurse to false in delete options not working
Needs Fix
The report appears valid

This is a work in progress...
Pull Requests:

Issue
Title
Resolution
Notes

This is a work in progress...


Remove incorrect information about state param

Omniauth uses the state param for providing automatic CSRF protection, if you do try and pass a ?state=XXX param it will effectively be clobbered internally by omniauth, and will not be echoed back during the callback phase. Example:
GET /auth/slack?state=123

...auth on Slack...

GET /auth/slack/callback?code=XXX&state=OMNIAUTH_CSRF_TOKEN

Thanks @mkdynamic !


AppleScript support

Hello!
I am using better touch tool for scripting the touchbar on new MacBooks. And wanted to add support for controlling the GPMDP from Touch Bar buttons with changing buttons status (play/pause) and showing the current playing song.
For iTunes I can use apple script like this:
if application "iTunes" is running then
	tell application "iTunes"
		if player state is playing then return "pause"
	end tell
end if

return "play"

if application "iTunes" is running then
	tell application "iTunes" to playpause
else
	tell application "iTunes" to activate
end if

And it would be great to be able to do something similar to GPMDP
I know about playback API, but can't use ws to control GPMDP from AppleScript
OS:
macOS 10.13.6
GPMDP Version:
4.6.1

We have our playback API which spits out JSON metadata files and uses a websocket to do two way player control.
You just need to figure out how to do that wiring.  Also we do integrate with macOS's media service so the OS should know our app is playing music.


is Concat function supported ?

Does Arm Compute Library provide a way of concatenating 2 input tensors into 1 output tensor ?

The DepthCacatenateKernel provided by the library can concatenate two input tensors along the depth dimension.

We haven't released the depth concatenate function yet but it is under our plan.

@steniu01
do you know when it will be made available ?

@joel-mi , the CLDepthConcatenate function will be available in the next release, which is coming at next few weeks. It is a memory copy based depth concatenate implementation.
We don't have NEDepthConcatenate implementation yet, but don't see a problem to add into our next quarter plan.

thanks !

Closing the question. Concat function will be part of next release for CL. Reopen if required.


Fix client creation with proxy

The exception has always been thrown, no matter if vendors were present or not.

Ops, I just noticed that CHANGELOG entry is missing. Can you please add it?

Sure, changelog updated.

Thanks! Could this be released anytime soon?

It's an important bug so definitely yes, but I would like to wait a few days to see if some other bug appears to avoid releasing too many times in a short period of time. In the meanwhile you can require the commit hash or the dev-master version


UCheckbox: is it possible for the help property of the checked component to have a link url?

Description
Hello team,
I want to link a label in a help so that the user can click a link that I want to place, all this because I need the text to be coordinated with the checkbox label.
Example:
 <UCheckbox v-model="checkedTerms.term">
            <template #label>
              Acepto los terminos y condiciones
            </template>
            <template #help>

                See terms and conditions

            </template>
         </UCheckbox>

You might want to take a look at the FormGroup component instead that supports the #help slot. Otherwise you can use the #label slot of the Checkbox.

Thanks 🚀


'x' mark doesn't appear on top of the editor panels

Problem Description
After updating all the packages in my conda environment, the spyder's editor panels stop showing 'x' marks. I can still close each script by clicking on the empty space (please see the image below).

What steps will reproduce the problem?

upgrade all packages in the current environment using conda

Package Versions

Spyder: 3.2.8
Python:3.6.5
Qt:5.9.4
PyQt:5.9.2
Operating System: MacOS High Sierra 10.13.3

Thanks for reporting. My guess would be an issue with Qt 5.9 on macOS, particularly High Sierra where Qt support is still rather flaky at last check. Unforunatly, there might not be much we can do about it due to it being Qt's problem...@ccordoba12 ? In the meantime, you can try downgrading Qt (and PyQt) to 5.6.x, although High Sierra is not fully supported there for sure and has some glitches and instability.

Thanks for reporting. I have a 10.12 VM, so I'll take a look at this when I have some time.

@ccordoba12 possible duplicate of https://github.com/spyder-ide/spyder/issues/4580

Right, let's close this one.


fix your install guide

Installation
You can download the repository by cloning it to your system and installing the necessary dependencies:
git clone https://github.com/AlexKrutoy/CEX.IO-bot.git
cd CEX.IO-bot

okay :v

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Stuck on loading currency pair

Stuck on loading BTC_BCY when loading all pairs. Is this possible?

chmod 770 /opt/gunbot


Design Doc: Support Private Registries Behind Auth

Goal:
To support enterprise stacks without the need for git push deis which is often slow in most normal network conditions.
Code Changes:
Client - implement flag -f --forward-credentials

this can utilize a users docker login, to forward credentials from ~/.docker/auth.json
this would be familiar to users of other schedulers

Builder - go-dockerclient and docker remote api support the x-registry-auth and related headers.
Our builder should leverage theses with the forwarded credentials
By always forwarding credentials we improve security dramatically by not storing state in the cluster.
Testing:
Unit tests should be implemented at the builder level for param validation.
Functional tests should test the relationship between the client and the builder service.
Any suggestions?

@miketheprogrammer I'm having a tough time recalling specifically what this use case resolves. Can you please provide your use case as well as how you'd intend to use such a feature in your environment with client command examples?

Please just close this. Its not relevant to the next version anyway
On Feb 25, 2016 1:17 AM, "Matthew Fisher"<EMAIL_ADDRESS>wrote:

@miketheprogrammer https://github.com/miketheprogrammer I'm having a
tough time recalling specifically what this use case resolves. Can you
please provide your use case as well as how you'd intend to use such a
feature in your environment with client command examples?
—
Reply to this email directly or view it on GitHub
https://github.com/deis/deis/issues/4885#issuecomment-188632399.


undefined method `log_alert' for FastlaneCore::Helper:Module (NoMethodError)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
undefined method `log_alert' for FastlaneCore::Helper:Module (NoMethodError)
Complete output when running fastlane, including the stack trace and command used
==> fastlane provision
/Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:36:in `eval': [!] undefined method `log_alert' for FastlaneCore::Helper:Module (NoMethodError)
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:128:in `block in execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:127:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/runner.rb:127:in `execute_action'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:137:in `method_missing'
	from (eval):2:in `block in parse'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:36:in `eval'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:36:in `block in parse'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:33:in `chdir'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:33:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/fast_file.rb:27:in `initialize'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane_manager.rb:12:in `new'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/lane_manager.rb:12:in `cruise_lane'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/lib/fastlane/command_line_handler.rb:31:in `handle'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:35:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.46.3/lib/fastlane_core/ui/fastlane_runner.rb:26:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:136:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane-1.32.1/bin/fastlane:142:in `<top (required)>'
	from /usr/local/bin/fastlane:23:in `load'
	from /usr/local/bin/fastlane:23:in `<main>'

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
# Minimum version of fastlane
fastlane_version "1.32.1"

default_platform :ios

platform :ios do

  # 1
  desc "Creating a code signing certificate and provisioning profile"
  # 2
  lane :provision do
    # 3
    produce(
      app_name: 'HomeControlApp',
      language: 'English',
      app_version: '1.0',
      sku: '123abc'
    )
    # 4
    cert
    # 5
    sigh(force: true)
  end

  error do |lane, exception|
    # This block is called, if there was an error running a specific lane.
  end

end

Environment
fastlane version (run fastlane -v):
==> fastlane -v
fastlane 1.32.1
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?

You're using a really old version of fastlane, please update to the latest version 👍


Error shouldn't occur

http://<IP_ADDRESS>:5000/stock/600096/2022-09-20
Error parameter: Stock 600096 is invalid or not supported yet.

This is due to missing data in 2022-09-20. Won't fix because it's not frequently used.


black screeen in android

What's happening?
Hi,
I installed this module and linked the modules as given in description but I am getting a black screen in android the camera is not opening up.
Build details?
android version 7.1.1
react-native-qrcode-scanner - ^1.0.1
react-native-camera - ^1.1.4
Here are my build.gradle
`buildscript {
repositories {
google()
maven { url "https://maven.google.com" }
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.1.0'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
    maven { url "https://jitpack.io" }
     maven { url "https://maven.google.com" }
     google()
    mavenLocal()
    jcenter()
    maven {
        // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
        url "$rootDir/../node_modules/react-native/android"
    }
}

}
/**

Project-wide gradle configuration properties for use by all modules
*/

ext {
compileSdkVersion           = 26
targetSdkVersion            = 26
buildToolsVersion           = "26.0.2"
googlePlayServicesVersion   = "12.0.1"
supportLibVersion           = "26.1.0"
}`
app/build.gradle
`dependencies {
compile (project(':react-native-camera')) {
exclude group: "com.google.android.gms"
compile ('com.google.android.gms:play-services-vision:12.0.1') {
    force = true
}

}
compile project(':react-native-google-analytics-bridge')
compile project(':react-native-vector-icons')
compile project(':react-native-video')
compile project(':react-native-push-notification')
compile project(':react-native-orientation')
compile project(':react-native-image-resizer')
compile project(':react-native-android-permissions')
compile project(':react-native-webrtc')
compile(project(':react-native-maps')){
exclude group: 'com.google.android.gms', module: 'play-services-base'
exclude group: 'com.google.android.gms', module: 'play-services-maps'
}
compile project(':react-native-device-info')
compile fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:23.0.1"
compile "com.facebook.react:react-native:+"  // From node_modules
compile project(':react-native-image-picker')
   compile 'com.google.android.gms:play-services-base:+'
compile 'com.google.android.gms:play-services-maps:+'
compile fileTree(dir: "node_modules/react-native-device-info/android/libs", include: ["*.jar"])

}
`
in gradle.properties
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
Please anyone suggest me how to solve this

same i

Any update on this?
I am also facing a black screen when opening the scanner on some devices.

@moaazsidat Do you have time to look into this am also facing the same issue. Thanks.


[operator] what is the --image-operator flag even for??

Its mandatory
It also has a default value, so why is it mandatory?
the default is a non-existent image (rancher/elemental-operator)
The config of the image is never used
We already have the operator binary running, what is the image for?

Goes like this:

Asks for image to be provided
Has default image, dont care
Default image doesnt exists
Proceeds to ignore the image completely
Refuses to elaborate

Chad flag, doesnt care about its value but it needs to be specified LOL
IMHO, drop that flag it makes no sense anywhere!

is the legacy from early development and full parameter passing from the helm chart? 🤔
we have a bunch of other parameters we pass there which seems not needed...

Others seems to make more sense as they are passed down the line to some of the controllers. But this one....

shiiiit, found it. Its actually passed to the syncer and used with the displaycommand to gather the output of the custom syncer. Woah. https://github.com/rancher/elemental-operator/blob/main/pkg/services/syncer/types/custom.go#L100


Script not functional after 1 race

I open the room, do 1 race and then i get like 20 times "Loaded Sucre from haxmaps" but its never loaded and the race never starts

I open the room, do 1 race and then i get like 20 times "Loaded Sucre from haxmaps" but its never loaded and the race never starts

@cofimaslisa OK, it's been fixed by changing the code. Here's the output:


Annotation in an Ingress resource overwriting default value defined in ConfigMap for all Ingresses (and perhaps vice versa)

Our ConfigMap for nginx-ingress-controller looks like this:
apiVersion: v1
data:
  proxy-body-size: "10m"
kind: ConfigMap
metadata:
  name: nginx-load-balancer-conf
  labels:
    app: nginx-ingress-lb

We use an annotation in one of our Ingress resources to use a different value for proxy-body-size:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: api
  annotations:
    ingress.kubernetes.io/proxy-body-size: "5500m"
spec:
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: api
          servicePort: 8000

When using nginx-0.9.0-beta.11, the value looks like this in nginx.conf:
# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";

We upgraded to nginx-0.9.0-beta.14 and the result was this:
# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";

I then re-applied the Ingress resource, and now it looks like this:
# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";

So, it looks like the default value from the configmap was used regardless of the annotation when upgrading to the new container and nginx.tmpl, and when applying an annotation to a single Ingress, the value is seen in all Ingresses.

More info: I tried to reproduce this in another cluster, and can't get the annotation to be seen in any of the ingresses. All of them have 10m as the client_max_body_size and deleting and applying or re-applying the Ingress resource doesn't do anything.

Please post the nginx.conf file from the container

Anonymized nginx.conf
I removed most of the redundant custom error locations.


SagePay may start returning PENDING for some transaction registrations

I noticed a potential problem to watch out for in issue #13 and am raising this to track any further observations.
When a PAYMENT is first registered with SagePay, the return status is one of OK, ERROR, MALFORMED or INVALID:

OK - all happy.
OK REPEATED - you've sent me this already, but you obviously didn't get my response, so here it is again.
MALFORMED - WTF did you just sent me?
INVALID - I can see what you are trying to send me, but you got some details wrong.
ERROR - I'm having a bad day; try that again in a few minutes.

The documentation is not totally correct - some tables fail to mention "OK REPEATED", while it is described in some overviews. The overviews also state that no StatusDetail message is returned for OK, when a message most certainly is returned.

Now, the problem.
On my test account running the V3.00 protocol, I made a PAYMENT registration, and got back a status of "PENDING" with a message "2014 : The Transaction was Registered Successfully."
That's new - never seen that before. There is a PENDING status that can be sent by SagePay in the notification callback, and that is used only for "European payment types" or PayPal, depending on which documents you read, but PENDING for the initial transaction registration? Nope.
This could be a change to the protocol, or some bank-holiday experiments they are performing on the test systems, or just an undocumented feature. Whichever way, we need to keep an eye on it. I'll give SagePay a call in the morning to see what could be going on.

After sleeping on it, I can see where some test scripts were getting mixed up at my end. I don't believe SagePay is sending the PENDING status. Okay - I was getting over the flu and my head is a lot clearer today :flushed:


Change group ID to com.azure.autorest and add missing info in pom.xml

This is group everything in com.azure.autorest for better organization.

After a brief discussion we will rename the artifact IDs instead.


Measurements added for Ikea LED2201G8

Device information

Home Assistant Device information

TRADFRI LED bulb E27 1055 lumen, dimmable, white spectrum (LED2201G8)
by IKEA
Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

Measured using 4 parallel bulbs and relatively large sleep time (6 seconds) as HS110 seems to take a while to settle.

Perfect!
Thanks for the PR.


[DEVOPS-529 DEVOPS-657] Add Buildkite pipeline

Cherry picking changes from current release branch.

DEVOPS-529 Buildkite pipeline and script updates
DEVOPS-657 Update nixpkgs version

I added a fix for the missing travis s3 deployments.


Remove 19.10 release from ubuntu solution

Description
Remove the 19.10 ubuntu release from ubuntu solutions as it reached its end of life date last month and is no longer supported.

verified


User friendly error when passing invalid JSON

Hello,
When a user passes invalid JSON data, Restivus responds with a stack trace like "SyntaxError: Unexpected string etc etc". Is it possible to catch the error and give a more user friendly response in such situations?
Regards,
Peter

I'll look into this when I return from vacation.

I would be interested too in a better way to catch payloads with not well formed JSON objects. Could this be handled by middleware ? Thank you for your reply and the great package.

I'm also having this issue with clients able to send invalid formatted JSON. How can we catch this and respond with an error?
post:
abc
Response:
Error: invalid json

    at parse (/home/ubuntu/.meteor/packages/simple_json-routes/.<IP_ADDRESS>bfasl++os+web.browser+web.cordova/npm/node_modules/connect/node_modules/body-parser/lib/types/json.js:83:15)

Then many more lines of error
if they post with invalid object:
{"name": aaa}
response:
SyntaxError: Unexpected token a

    at Object.parse (native)

    at parse (/home/ubuntu/.meteor/packages/simple_json-routes/.<IP_ADDRESS>bfasl++os+web.browser+web.cordova/npm/node_modules/connect/node_modules/body-parser/lib/types/json.js:88:17)

It seems like the simple_json-routes is handling this first before I can even do type checks, obj field checks, etc.
How can we handle this? It doesn't look very good or help the person that doesn't know how to fully use the API.

+1

Hi, is anyone found any workaround for this issue?


Support Windows Arm64 for rpiboot_setup.exe

With Windows Arm64 systems becoming more popular, it'd be nice to have an arm64 version of the installer that can install arm64 drivers.

I think it’s unlikely that we would want to support anymore binary distributions of this.

I think if the embedded copy of wpi-simple.exe is updated, it will just automatically work. It seems like the latest release of that tool has arm64 support. It shouldn't actually require a specific arm64 installer, at least from what my research is showing.

It’s not something that we would spend time testing or supporting do I’m closing this as Not Planned.
If patches for the source are required to fix bugs then we normally accept those as is


Build Title component

Fixes #20

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_2::detail::parse_error'

Hello, I'm trying this project to experience ChatGPT, but when I run the object compiled, I had a crash, the error log is:
./Chat_GPT [my api_key]

Serenity
Enthusiasm
Perseverance
Affection
terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_2::detail::parse_error'
what():  [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - unexpected end of input; expected '[', '{', or a literal
已放弃 (核心已转储)
pls help me,tks.

If you're running the main example, are you sure that you've the sound.mp3 file in the same directory as the executable?

yes, it has a sound.mp3 file in build directory
and it still crash

I compile it on ubuntu20.04, and I'm not sure whether it can affect sth...

That's look weird, have you tried to remove the whisper part?

yes, I have tried, but it still crash...


Display donation widget correctly since the first render

What:
Display donation widget correctly since the first render
Why:
Closes: https://app.asana.com/0/1159164196409156/1197918681594185/f
How:
Including https://www.gatsbyjs.com/plugins/gatsby-plugin-styled-components/ in the gatsby config
The issue was related to styled-components, the styled weren't being loaded in the first render. By adding built-in server-side rendering support this issue does not occur anymore.
Media
https://www.loom.com/share/7aa3a9c973a0404584ca1235f5cdffb0

I'm glad this was only to add a new plugin.
Honestly I have been trying a bit with the CSS modules and Global CSS and I don't enjoy those approaches more than CSS-in-JS (but that's a discussion we can tackle in another moment.)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to scrape for a particular Tweet ID?

Thank you for this work!
I would like to scrape for a particular Tweet via their ID - how can I do that with this API?

same here.

Integrate this into the code base please https://github.com/rishi-raj-jain/twitterUsernamefromUserID


fix publish workflow

What this PR does:
Fix the error that happened here: https://github.com/stargate/stargate-mongoose/actions/runs/6737734269 . Not sure why this workflow can't have dependencies, but it isn't worth blocking releasing
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

Yeah we should be able to


Splitting StringResponse into HtmlResponse and JsonResponse

This is a follow-up to #61.
The HtmlResponse and JsonResponse classes mimics the behaviour of @weierophinney 's RedirectResponse and EmptyResponse (i.e. they directly extend the Response class instead of providing a factory)
Most of the JSON code for handling errors comes from Symfony's JsonResponse.
We could optionnally add a static create method to create the response (a bit like Symfony does...)

Closing in favor of #61, on which @moufmouf is collaborating.

:+1:


Migration should consider inserting as K instead of putting a ! on K.

Silly example:
class HashMapBackedList<T> {
  Map<int, T> _map;

  ...

  T/*!*/ get first => _map[0];

  ...
}

If we migrate this to
  T get first => _map[0]!;

then this changes behavior for nullable instantiations
var x = HashMapBackedList<int/*?*/>();
x.add(null);

// should return null:
x.first;
// instead throws NPE because we call `!` on `_map[0]` which is null.

A better migration is
  T get first => _map[0] as T;

@pq @bwilkerson For similar reasons, we may want to lint this.
Cases this doesn't apply:

if the bound is nullable
if we call a method on the bound type (ie, T extends num, _map[0].floor() should become _map[0]!.floor())
maybe others

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Add aipoemgenerator.org

Hi, we are the makers of https://www.aipoemgenerator.org, and would love to have it listed under the Text > Services category 🙂

I will consider it. At the moment the page appears to be offline from my side. Please check.

@steven2358 Thanks for taking a look! There was an issue earlier but it was fixed about ~2 hours ago, and I can see that it's working again. If you could check it out again that would be great 🙏


Collect training data use keyboard

Hello!
I want to use keyboard to control the vehicle and collect images and information of vehicle like "throttle","steer","brake" at the same time to use imitation learning. What should I do about this or is there any examples like this?

Hi, manual_control.py is an example of how to do that. It's in carla/PythonAPI/examples


Add the ability to configure Winston's file transport logging level

As requested in #126 . I'm not sure if the winston file transport configuration line is in the best place, but this at least seems to work.

Note that this doesn't change the log level of the transport that writes the http access log, but that is an easy change.

I am using farhad-a's version and notice that events.log is still growing.  Is it possible, or advisable, to allow this to be reduced by a config?


Device fallback and fixed typo

Added device fallback to make sure that projects that depend on MoltenVK keep working in certain situations like for CI. Also fixed a typo that prevented the project from building

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

triggering a mux switch on startup

Ah! Damn! Thanks for the reminder that MTLCreateSystemDefaultDevice() forces a GPU switch.
With that in mind I won't make the change that I suggested above, and we'll leave the implementation as it appears in this PR.


Sample during training problem 2

I saw that there was a discussion about this issue before, but it was closed. However, I still have a question to ask.
could you tell me how to go through all the steps from t=1000, ... , 0 to generate a synthetic image？
I just find it in the validation code, but not in the training code.

I guess this is how to go through all the steps, but it only appear to the test code.


Feature request: integrate Postmark's SpamAssassin API

http://spamcheck.postmarkapp.com/

Fantastic!

Stale. Request re-open if there's traction again.


Don't suppress messages without defined level

https://github.com/ogallagher/temp_js_logger/blob/1a7ea582d3d76f90e64e251d614a6c3275c79c0a/temp_js_logger.js#L65
Default level is DEBUG, but it should be something that won't be suppressed at higher logging level settings.

Introduced LEVEL_ALWAYS.


Fontsubsetting causes Arabic copy to change in characters

normal

with font subsetting:

also see project mondelez-menap-tang-everyday-amazing-kids-gcc

@mm-paulie I mentioned this issue in the repository of subset-font, which is the npm package we use for subsetting in the framework, and it looks like this was mainly a font issue. Doesn't have anything to do with our implementation of font subsetting in the framework.
https://github.com/papandreou/subset-font/issues/17
Going to close this issue for now.


Upgrade OneKE from 1.24 to 1.27

Description
OneKE requires software update:

[x] Update Ubuntu to latest 22.04/20230424
[x] Update RKE2 to latest v1.27.1+rke2r1
[x] Update Helm binary to latest v3.11.3
[x] Update Longhorn's Helm Chart to latest 1.4.1/v1.4.1
[x] Update Traefik's Helm Chart to latest 23.0.0/v2.10.0
[x] Update MetalLB's Helm Chart to latest 0.13.9/v0.13.9
[x] Perform conformance testing sonobuoy run --mode=certified-conformance --plugin-env=e2e.E2E_EXTRA_ARGS='--non-blocking-taints=CriticalAddonsOnly,node.longhorn.io/create-default-disk' --ginkgo.v
[x] Release OneKE 1.27 in the Marketplace (make sure storage disks size is reduced to minimum)
[x] Review and update documentation https://docs.opennebula.io/6.6/marketplace/appliances/oneke.html
[x] Create PR in https://github.com/cncf/k8s-conformance -> https://github.com/cncf/k8s-conformance/tree/master/v1.24/OneKE can be used as a template

Use case
OneKE needs to be updated to keep it certified.
Interface Changes
N/A
Additional Context
N/A

Progress Status

[x] Code committed
[x] Testing - QA
[x] Documentation (Release notes - resolved issues, compatibility, known issues)

https://github.com/cncf/k8s-conformance/pull/2601#issuecomment-1548353723 :ok_hand:


JFXTreeTableView with 20,000 rows is slow to clean

Hello, I'm using the JFXTreeTableView, and trying to put more than 20,000 rows working correctly, the problem arises when I want to clean all records, it's very slow. This is the code I have:
private ObservableList<ProductoStockInicialTable> listaProductosSaldo;
listaProductosSaldo = FXCollections.observableArrayList();
tablaSaldos.setRoot(new RecursiveTreeItem<(listaProductosSaldo,RecursiveTreeObject::getChildren));
tablaSaldos.setShowRoot(false);

To add the 20,000 records I do with this method:
public void addListProductoFraccionSaldo(List<ProductoStockInicialTable> listaProductoFraccion) {
        listaProductosSaldo.addAll(listaProductoFraccion);
    }

And to clean it I do with this other method:
public void clearListProductoFraccion() {
      listaProductosSaldo.clear(); // Is very slow
}

I am doing some misuse of the JFXTreeTableView? or maybe there is a more optimal solution to mine? Thank you so much for everything. Regards.

Using the question, how can I do to clear the entire JFXTreeTableView, use clear method(), but I delete the ones that are showing in the table, when I make a filter with the predicate() method, only I delete the ones that are shown with the filter, when I return the filter to its normal state, me the ones that were not shown. How could you solve this problem? Thanks in advance

Hello,
Well you can try deleting JFXTreeTableView items directly instead of deleting from the data model.
can you provide the full code? maybe we can try optimize it.
Regards,