[BUG] AWS OpenSearch is reporting 4xx errors when indexing documents, even though indexing succeeds

What is the bug?
AWS OpenSearch is reporting one 4xx error for every document being indexed, even though the indexing succeeds.
How can one reproduce the bug?

Create an AWS OpenSearch domain (the node instance type shouldn't matter).

Create your OpenSearchClient:

var client = new OpenSearchClient(
    new AwsSdk2Transport(
        ApacheHttpClient.builder().build(),
        opensearchHost,
        "es",
        Region.US_WEST_2,
        AwsSdk2TransportOptions.builder().build()
    )
);

Write your indexing logic:

openSearchClient.index(builder ->
    builder.id(id)
        .index(indexType.getIndexAliasName())
        .opType(OpType.Index)
        .refresh(Refresh.False)
        .requireAlias(true)
        .timeout(Time.of(builder -> builder.time("10s")))
        .document(document)
);

Invoke the above logic to index a document.

What is the expected behavior?
I wouldn't expect any 4xx errors to occur, as the indexing succeeds on all shards.
What is your host/environment?

AWS OpenSearch 2.5.0 (the latest version AWS supports currently)
Every index has the default refresh policy (1s)
I'm using index aliases for all operations

Do you have any screenshots?

Do you have any additional context?
Using this same OpenSearchClient object, I'm able to query documents without any 4xx errors occurring - it seems to only occur when indexing new documents.
I have a feeling these 4xx errors are due to some HTTP header that I'm not providing in the AwsSdk2TransportOptions, as I think AWS may require certain headers.
I've enabled Error logs on the AWS OpenSearch domain, but there don't seem to be any logs for 4xx errors, unfortunately.
I was going to reach out to AWS support regarding this issue, but thought it would be better to ask here first.
Thank you!

can you share what the 4xx error was? Maybe it's in your cloudwatch.

Unfortunately, there’s no CloudWatch logs whatsoever. I mentioned above
that I’ve already enabled the "Error logs", but nothing is written to
CloudWatch when the 4xx errors occur (other than the test events that
OpenSearch writes when first enabling logs to ensure they’re being
delivered to CloudWatch successfully).
On Tue, Jun 20, 2023 at 10:39 PM William Beckler @.***>
wrote:

can you share what the 4xx error was? Maybe it's in your cloudwatch.
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/opensearch-java/issues/533#issuecomment-1600132897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENINQDZI2MN5YDGT3VV6RDXMKCKTANCNFSM6AAAAAAZOFNLXE
.
You are receiving this because you authored the thread.Message ID:
@.***>

do you know how to enable log4j logging for the client?

No, I’ve just been manually logging responses myself (which just contain
the number of shards that succeeded/failed). Is there any documentation on
how to do that?
On Tue, Jun 20, 2023 at 10:56 PM William Beckler @.***>
wrote:

do you know how to enable log4j logging for the client?
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/opensearch-java/issues/533#issuecomment-1600222153,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENINQBRPLN6KKODNIMQHELXMKEHJANCNFSM6AAAAAAZOFNLXE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I couldn't find any docs for opensearch-java, but it was forked from elasticsearch-java, I think v7.10. This might work: https://www.elastic.co/guide/en/elasticsearch/client/java-api/7.10/_log4j_2_logger.html

Makes sense, thank you! I’ll try it out in the morning and see if it can
identify the root cause.
On Tue, Jun 20, 2023 at 11:01 PM William Beckler @.***>
wrote:

I couldn't find any docs for opensearch-java, but it was forked from
elasticsearch-java, I think v7.10. This might work:
https://www.elastic.co/guide/en/elasticsearch/client/java-api/7.10/_log4j_2_logger.html
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/opensearch-java/issues/533#issuecomment-1600233678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENINQG57TYZIGWL7LTKUEDXMKE4VANCNFSM6AAAAAAZOFNLXE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Because my project uses Spring Boot, I attempted to enable trace logging using logging.level.tracer = TRACE, but nothing is being logged.
I also tried enabling trace logging for everything using logging.level.root = TRACE, but that didn't provide any additional insight into the 4xx errors. The Apache HTTP wire logs to OpenSearch show that the response code is 201.
I think I'll have to open a case with AWS support regarding this.

Re: logging. Let's properly document how to do this? I have some logging configuration that works in https://github.com/dblock/opensearch-java-client-demo that could help. I opened https://github.com/opensearch-project/opensearch-java/issues/535, @jhg023 if you want to work through this starting with my sample I can try to help.
Re: 404s. Is any of this reproducible with curl?

I only see the 4xx errors on the AWS OpenSearch console within the "Cluster health" section, as seen in the screenshot supplied in my original post. When I enabled trace logging for every package in my service, I was able to see logs for both the Apache HTTP client and for the OpenSearch client, but there weren't any logs that indicated a 4xx error was occurring.
I have to step away for most of the day, but I'll try manually indexing with curl later tonight and get back to you with the result.

Update: I was able to use curl to successfully index documents without receiving any 4xx errors, so I knew it was definitely something with the OpenSearchClient.
I reached out to AWS support, and they were able to identify the root cause:

I have also checked the ELB logs to see the specific 4xx errors being thrown:
elb_status_code Total Count: 8867
1 200 7551
2 201 658
3 404 658
4 Other 0
As seen above they are 404 errors. Looking further into the 4xx errors I have also noted that they all come from the below API:
HEAD https://:443//_doc/32955571

As you can see, the OpenSearchClient is sending a HEAD request alongside every PUT request that actually indexes the document, and AWS is only expecting to receive PUT

So exists correctly returns true or false, but uses HEAD, which causes a 404, which is expected? Makes sense. We may want to document this somewhere in the user guide, maybe you'd like to contribute a "check if a document exists" section?
Generally for your application you should probably do some kind of upsert. Checking for a document existence in a distributed system may be eventually consistent ;)

Agreed, I modified my code to use an upsert pattern instead.
I'll see if I can find some time to contribute :)
Thanks again!


[1.12.x] parameter with value {} is replaced with null

Actually there was nothing to fix, but I added the test anyway ;)


Investigate parallel listener calls

On the development environment, are being called simultaneously and resulting in unexpected behaviors.
Actually, blocks are being mined so shortly that a listener for a block is being called before of the call from the last block.
For now, a call will be ignored if has another call running.
Comment extracted from: tasit-action > Action.js > #addConfirmationListener:
// Note:
// On the development env (using ganache-cli)
// Blocks are being mined simultaneously and generating a sort of unexpected behaviors like:
// - once listeners called many times
// - sequential blocks giving same confirmation to a transaction
// - false-positive reorg event emission
// - collaborating for tests non-determinism
//
// Tech debt:
// See if there is another way to avoid these problems, if not
// this solution should be improved with a state structure identifying state per event
//
// Question:
// Is it possible that that behavior (listener concurrent calls for the same event) is desirable?

Extracted from: https://github.com/tasitlabs/TasitSDK/pull/369#discussion_r280218408

For now, a call will be ignored if has another call running.

Is this explicitly enforced in our code, or is this the default behavior?

@pcowgill commented:

Is the non-determinism mostly for tests where the listener is added before or after sending the tx? Or is it a little of both?
We're sure it's not just getting called again with another confirmation for each instantaneous block, right? If so, we could probably disable that in our code and check number of confirmations on each listener call. Or something like that.

For now, a call will be ignored if has another call running.

Is this explicitly enforced in our code, or is this the default behavior?

Is this explicitly enforced in our code:
From Subscription class:
const listener = async (...args) => {
  const eventListener = this.#eventListeners.get(eventName);
  const { isRunning } = eventListener;

  if (isRunning) {
    console.info(`Listener is already running`);
    return;
  }

  this.#decorateEventListener(eventName, { isRunning: true });
  await baseListener(...args);
  this.#decorateEventListener(eventName, { isRunning: false });
};

Got it - thanks


Release Google.Cloud.Talent.V4Beta1 version 3.0.0-beta05

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.Talent.V4Beta1-3.0.0-beta05


Update loss.md

fixed a typo in the equation (missing matrix inverse) and added \left and \right to brackets in TeX math.

To review this, we need to see the rendered result, so I created #137


Update System.Text.Json to 8.0.5

8.0.4 has a critical vulnerability.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
3779

Relevant Lines:
3779

💛  - Coveralls


apt.dockerproject.org is not working

$ curl https://apt.dockerproject.org/

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    <title>503 Connection refused</title>

Error 503 Connection refused

Connection refused

Guru Mediation:

Details: cache-syd1625-SYD<PHONE_NUMBER><PHONE_NUMBER>

Varnish cache server

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

ping @jfrazelle

same issue I encounter
$ ping apt.dockerproject.org
PING j.global-ssl.fastly.net (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=128 time=160 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=128 time=155 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=128 time=164 ms

Yeah I'm having problems too.

I have the same issue

I think it's down for everyone, but unfortunately it's 4.30 am on a Sunday in San Fransisco and afaik, these servers are managed by the open source project maintainers, not Docker, Inc., so no 24/7 support here

I have the same issue too.

Same issue here and I was installing docker.

As a temporary solution, the static builds can still be found on get.docker.com; see https://docs.docker.com/installation/binaries/#get-the-docker-binary

fwiw *.dockerproject.org isn't mentioned on https://status.docker.com/

@pdericson I think that's because it's not managed by Docker, Inc. (but it would make sense to have it included there - I noticed it as well)
@pdericson could you create a separate issue for that / feature request?

fixed we are kinda getting ddosed tho, i will try to block the ips
On Sun, Aug 16, 2015 at 5:36 AM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

@pdericson https://github.com/pdericson I think that's because it's not
managed by Docker, Inc. (but it would make sense to have it included there

I noticed it as well)

@pdericson https://github.com/pdericson could you create a separate
issue for that / feature request?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/15616#issuecomment-131541485.

@thaJeztah thanks, good suggestion - I have created https://github.com/docker/docker/issues/15619
@jfrazelle thanks for the quick turnaround :)

thank so much @jfrazelle, you rule!

awesome @jfrazelle thank you very much!

nice job! @jfrazelle

I'm assuming this was some cron jobs or ci's that are misconfigured on someone servers and just overly hitting us, which means if your ip is now blocked and you are still getting a 502 (or 501) that's you :P and let me know

On Aug 16, 2015, at 06:08, Jessie Frazelle<EMAIL_ADDRESS>wrote:
fixed we are kinda getting ddosed tho, i will try to block the ips

On Sun, Aug 16, 2015 at 5:36 AM, Sebastiaan van Stijn<EMAIL_ADDRESS>wrote:
@pdericson I think that's because it's not managed by Docker, Inc. (but it would make sense to have it included there - I noticed it as well)
@pdericson could you create a separate issue for that / feature request?
—
Reply to this email directly or view it on GitHub.

If I use apt-cacher-ng, it will cause 403 error.
But if I remove apt proxy setting, it's ok.
I don't know why.

will this be happening every sunday?:
ubuntu@ip-10-220-1-167:~$ curl https://apt.dockerproject.org/

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    <title>503 Connection refused</title>

Error 503 Connection refused

Connection refused

Guru Mediation:

Details: cache-lhr6331-LHR<PHONE_NUMBER><PHONE_NUMBER>

Varnish cache server

Happening again? I've got 503 as well.

My IP is <IP_ADDRESS>, hope it is not on the block-list

Ran into this also... sunday again.

$ curl https://apt.dockerproject.org/

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    <title>503 Connection refused</title>

Error 503 Connection refused

Connection refused

Guru Mediation:

Details: cache-lhr6331-LHR<PHONE_NUMBER><PHONE_NUMBER>

Varnish cache server

+1, hoping this gets fixed asap.

how can anyone query apt.dockerproject.org that much, for such a long time ! (3hours till now)

+1

USER POLL
The best way to get notified when there are changes in this discussion is by clicking the Subscribe button in the top right.
The people listed below have appreciated your meaningfull discussion with a random +1:
@xianminx

Can somebody reopen this again? Same problem....

@mvanholsteijn it's reopened here https://github.com/docker/docker/issues/16101

My IP is <IP_ADDRESS>, hope it is not on the block-list

Same issue (503 Error) when trying to access https://apt.dockerproject.org/.

I got this issue just now...
Any workaround for that one?
10x

@lastboy see https://github.com/docker/docker/issues/16101#issuecomment-138078533 for a workaround.

its back up and if people could not set up faulty cron jobs that ping us at hundreds of thousands of requests per second that would be great.
Also just because it happened once before on a sunday weeks ago doesnt mean there is a pattern :p

@jfrazelle :+1:
Sunday ping from hell :imp: :smile:
No Docker on Sunday makes us sad pandas :panda_face:

@GordonTheTurtle, thanks for the reminder. I am sorry to catch what you mean by The people listed below have appreciated your meaningfull discussion with a random +1:.
Do you mean that I should not spam with "+1" action?
ps: there is a minor typo: meaningfull -> meaningful


Updates to documentation for string printf functions

The behaviour of vsnprintf() with count == 0 and buffer != NULL is to return the length of the formatted data, rather than returning -1 — as the documentation currently states. I have cross-referenced the behaviour of vsnprintf() with the C specification, and confirmed that the implementation behaviour (returning the length of the formatted data) conforms to the C specification and is correct. Therefore, the current vsnprintf() documentation is incorrect and needs to be updated.
After making this observation, I conducted a broader review of the documentation for the *sn[w]printf* family of functions, making these updates as a result.
In general, I've corrected a number of errors in the description of the behaviour of the *sn[w]printf* family of functions, and have aligned the information for:

_snprintf_s()/_snwprintf_s() and _vsnprintf_s()/_vsnwprintf_s()
snprintf()/_snprintf()/_snwprintf() and vsnprintf()/_vsnprintf()/_vsnwprintf()

A detailed description of the problems addressed on each page is given below:
_snprintf_s()/_snwprintf_s():

Add description of behaviour which occurs when an encoding error occurs during formatting — setting errno to EILSEQ in all cases and either returning a negative value for a string conversion specifier, or skipping the character for a character conversion specifier.

Clarify that in cases where truncation does not occur, null-termination is performed

Clarify truncation behaviour:

If count < sizeOfBuffer, but formatted data > count, then formatted data is truncated to count characters, null-terminated and -1 is returned with no error handler / update to errno
With count == _TRUNCATE, and formatted data >= sizeOfBuffer, then formatted data is truncated to (sizeOfBuffer - 1) characters, null-terminated and -1 is returned with no error handler / update to errno
If count >= sizeOfBuffer, formatted data >= sizeOfBuffer, and count != _TRUNCATE, the invalid parameter handler is invoked. If continued, the functions truncate the buffer to an empty string, return -1 and set errno to ERANGE

Clarify error handling behaviour:

If buffer is NULL, an EINVAL error occurs if (and only if) either count or sizeOfBuffer are != 0 (if both are 0, no error occurs and 0 is returned)
An EINVAL error does not occur in all cases where count == 0, only when one of the other conditions are met (count cannot be negative, as size_t is unsigned)
If sizeOfBuffer (not count!) == 0, and additionally if buffer is not NULL, then an EINVAL error occurs

Add copy of error conditions table from _vsnprintf_s()/_vsnwprintf_s().

snprintf()/_snprintf()/_snwprintf():

Add description of behaviour which occurs when an encoding error occurs during formatting — setting errno to EILSEQ in all cases and either returning a negative value for a string conversion specifier, or skipping the character for a character conversion specifier.

Clarify truncation behaviour:

For snprintf(), clarify that null-termination by writing to buffer[count-1] is only performed if count != 0.
For _snprintf()/_snwprintf(), clarify that non-terminated truncation is performed only when buffer != NULL (if buffer == NULL and count != 0, it is an error and if if buffer == NULL and count == 0, the length of the formatted data is returned).

_vsnprintf_s()/_vsnwprintf_s():

Add description of behaviour which occurs when an encoding error occurs during formatting — setting errno to EILSEQ in all cases and either returning a negative value for a string conversion specifier, or skipping the character for a character conversion specifier.

Clarify that in cases where truncation does not occur, null-termination is performed

Clarify truncation behaviour:

Note that if count >= sizeOfBuffer and formatted data >= sizeOfBuffer, then only if also count != _TRUNCATE the invalid parameter handler is invoked, etc.

Clarify error handling behaviour:

If buffer is NULL, an EINVAL error occurs if (and only if) either count or sizeOfBuffer are != 0 (if both are 0, no error occurs and 0 is returned)
An EINVAL error does not occur in all cases where count == 0, only when one of the other conditions are met (count cannot be negative, as size_t is unsigned)
If sizeOfBuffer (not count!) == 0, and additionally if buffer is not NULL, then an EINVAL error occurs

Update error conditions table to correct from count == 0 to sizeOfBuffer == 0 as the condition required for an EINVAL error (when buffer != NULL).

vsnprintf()/_vsnprintf()/_vsnwprintf():

Add description of behaviour which occurs when an encoding error occurs during formatting — setting errno to EILSEQ in all cases and either returning a negative value for a string conversion specifier, or skipping the character for a character conversion specifier.

Clarify that in cases where truncation does not occur, null-termination is performed

Clarify truncation behaviour:

For vsnprintf(), clarify that null-termination by writing to buffer[count-1] is only performed if count != 0.
For _vsnprintf()/_vsnwprintf(), clarify that non-terminated truncation is performed only when buffer != NULL (if buffer == NULL and count != 0, it is an error and if if buffer == NULL and count == 0, the length of the formatted data is returned).
For vsnprintf(), clarify that if count == 0 and buffer != NULL, the length of the formatted data is returned, rather than -1 (as is the case for _vsnprintf()/_vsnwprintf()).

To verify the behaviour of these functions, I constructed the attached test code (printf.zip). The updated descriptions of these functions' behaviour can be verified using the output from this:
C:\Temp>cl /Zi /Od /MTd printf.c && printf >printf.txt
Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30528 for x86
Copyright (C) Microsoft Corporation.  All rights reserved.

printf.c
Microsoft (R) Incremental Linker Version 14.30.30528.0
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:printf.exe
/debug
printf.obj

I can't reopen it either. I'll watch for your new one.

Thanks @tycastMSFT — I've opened a new PR: #3411, where I've rolled in my corrected descriptions of the handling of encoding errors.
I realise that it'll need dev review, and there may be a discussion of to what extent you want to codify the current encoding-error-handling behaviour, but hopefully my changes to the docs are an accurate description of the current CRT behaviour and will serve as a useful basis for discussing how the docs should be updated (and may perhaps even be able to be accepted wholesale!)
Andrew R

I believe you meant TylerMSFT, not TycastMSFT. - TCC
From: adr26 @.>
Sent: Tuesday, September 28, 2021 11:01 AM
To: MicrosoftDocs/cpp-docs @.>
Cc: Tyler Castaldo @.>; Mention @.>
Subject: Re: [MicrosoftDocs/cpp-docs] Updates to documentation for string printf functions (#3328)
Thanks @tycastMSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FtycastMSFT&data=04|01|tycast%40microsoft.com|025aa21b2f3f453c1db608d982a19a39|72f988bf86f141af91ab2d7cd011db47|1|0|637684452941143614|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iklTtrcAvrPAiP14lbl1UH%2BUzfGJFeLAIu7pwPKkFJ0%3D&reserved=0 - I've opened a new PR: #3411https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fcpp-docs%2Fpull%2F3411&data=04|01|tycast%40microsoft.com|025aa21b2f3f453c1db608d982a19a39|72f988bf86f141af91ab2d7cd011db47|1|0|637684452941143614|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=EkRu7%2FLJ35Y%2BJ1d%2BblQNvRZioEbbf9RyBZtUJf%2B40Vg%3D&reserved=0, where I've rolled in my corrected descriptions of the handling of encoding errors.
I realise that it'll need dev review, and there may be a discussion of to what extent you want to codify the current encoding-error-handling behaviour, but hopefully my changes to the docs are an accurate description of the current CRT behaviour and will serve as a useful basis for discussing how the docs should be updated (and may perhaps even be able to be accepted wholesale!)
Andrew R

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fcpp-docs%2Fpull%2F3328%23issuecomment-929411005&data=04|01|tycast%40microsoft.com|025aa21b2f3f453c1db608d982a19a39|72f988bf86f141af91ab2d7cd011db47|1|0|637684452941153612|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YwJUtLEFyrzFDTftMMzsF0PIcTVu0k9aT4x7cqS%2FVqQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFPM2L4HLILIDRU5NT4UKYTUEHYGHANCNFSM5C3E22YA&data=04|01|tycast%40microsoft.com|025aa21b2f3f453c1db608d982a19a39|72f988bf86f141af91ab2d7cd011db47|1|0|637684452941153612|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qJ5p31cyJlCmOWc7EqxQQ1xZWhx0MsNI7GODbiGLyBU%3D&reserved=0.

@TylerMSFT Do you not see a "Reopen and comment" button at the bottom of a comment box like this one? There may be other ways to reopen a PR, but this one is how I usually do it. If you don't, then maybe I didn't set up your admin privileges correctly.

@corob-msft - I see the button but it won't respond, i.e. it's not clickable.

Hi @corob-msft, @TylerMSFT,
Please ignore #3328 (I think github refuses to allow you to re-open a PR if you force-pushed, which I did to my repo once I'd rebased my changes with up-to-date changes from the MicrosoftDocs repo).
Instead, please look at my new PR: #3411, where I've rolled in my corrected descriptions of the handling of encoding errors.
I realise that the PR will need dev review, and there may be a discussion of to what extent you want to codify the current encoding-error-handling behaviour, but hopefully my changes to the docs in #3411 are an accurate description of the current CRT behaviour and will serve as a useful basis for discussing how the docs should be updated (and may perhaps even be able to be accepted wholesale!)
Andrew R

@adr26 Don't worry, we'll work with your latest PR. We're just curious why one of our buttons doesn't work as expected. There's hover text associated with the button: "There is already an open pull request from adr26:master to MicrosoftDocs:master". It may be that you can only have one open PR from a particular branch at a time? I bet that's it.


SharePoint Search API result returns unexpected RowCount

In my opinion the following is a bug related to SharePoint Search API
The following request
https://%xyz%.sharepoint.com/_api/search/query?querytext='marco'&rowsperpage=10&rowlimit=200&clienttype='ContentSearchRegular'
Gives a RowCount of 2 (PrimaryQueryResults > RelevantResults). However when I request results starting from row 1 (instead of 0 or with startRow ommited) with the following request
https://%xyz%.sharepoint.com/_api/search/query?querytext='marco'&startrow=1&rowsperpage=10&rowlimit=200&clienttype='ContentSearchRegular'
It gives me the expected RowCount of 10.
In both cases the TotalRows is the same around 24.
Initially the first query worked fine (since 2017) and the unexpected RowCount (and thus the unexpected number of Rows in the corresponding Table) I only started noticing this week (but the issue may be older). Therefore I believe it may be related to an update by Microsoft. Curious to see if anyone else is experiencing the same thing!
PS What is odd is that for other queries with a different queryText e.g. 'sharepoint' I get immediately 10 rows of results.

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

ID: 3b3e4019-1df2-2317-7a63-dbdfba66a3f4
Version Independent ID: 7f409188-f8ae-94cd-d174-b0c7b5183096
Content: SharePoint Search REST API overview
Content Source: docs/general-development/sharepoint-search-rest-api-overview.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

RowsPerPage is not really used. Use RowLimit and StartRow. Does that help?


Replace dots with arrows

Hello,
It would be great if you could replace dots with arrows (like in legacy interface) in the next release as they are more aesthetic and gives high visibility.
I noticed that many people suggested that  that on the forum, it would be nice to be able to choose between dots and arrows on user preferences.
Thanks

can i disable indicator arrow?
my device no indicator report.
it always point to north.
i don't need this


Add graceful behavior when processes are killed

When working with gunicorn I discovered that you'll end up shooting yourself in the foot if you start the process logger at the wrong time because gunicorn will end up killing the logger, which results in apparently nothing happening after you make log calls. This will update the logger to be explicit about how dead it is and why, throwing on log() and close() calls.

@jamie256 Finally got this working again with a few additional process logger changes needed for the container.


[hw,dv_utils] Fix macro substitution issue with Xcelium

As per System Verilog standard, to create macro strings using macro arguments use `" instead of ".
Update the macros processing valueplusargs arguments. Other macros has this change.

@cindychip Any concerns, in particular w.r.t. VCS?


select multiple treated as geo-point in data on server

a select_multiple with answers like
1    Meat
2    Poultry
3    Fish
4    Fruit
5    Vegetables
97    Other
98    Refused
99    Don't Know
mostly has data like
"marktype": "3 4 5",

but will also appear like
"marktype": {
      "latitude": 1,
      "longitude": 3,
      "altitude": 4,
      "precision": 5
    },

(links to example occurrences are on April 4 in the posm channel in the openmapkit slack)

i think this affects 1,200+ submissions across 4+ surveys

same issue, different question

Liberia_Community_Survey_Mar2016_MF_v1/7964a442-178d-4c60-ba03-8e50ee554e87
  "b": {
    "intro": 2,
    "intro_fail": {
      "latitude": 1,
      "longitude": 3,
      "altitude": 4,
      "precision": 97
    },

same issue, multiple questions (marktype question unaffected)

Liberia_Community_Survey_v18/1576a84d-94f5-4c97-92a2-1401ebe6f713/data.json
"n": {
    "treat_mult": {
      "latitude": 5,
      "longitude": 9,
      "altitude": 10,
      "precision": 12
    }
  },
...
"s": {
    "birth_mult": {
      "latitude": 5,
      "longitude": 9,
      "altitude": 10,
      "precision": 13
    }
  },

other examples

Guinee_Sondage_Communautaire_V1-4-7/3c4a90ce-0522-476d-97fc-6fb37700ce7f
Guinee_Sondage_Communautaire_V1-4-7/3eb38179-9b4b-4280-8ec4-52a9a609d498
Guinee_Sondage_Communautaire_V1-4-7/40c71a0a-4718-4980-b76d-cbdec7bee638
Guinee_Sondage_Communautaire_V1-4-7/423cde52-77ce-48c4-a9a9-8f2644d08169

Guinee_Sondage_Communautaire_V1-4-3/fcbd76ce-82f9-4dcd-8fb3-92ad70ba384d
Guinee_Sondage_Communautaire_V1-4-3/f6db9911-c292-4c0f-9b98-2bc2219499d3
Guinee_Sondage_Communautaire_V1-4-3/f6dfce27-2fbe-406b-9a2f-a9af58dbd354
Guinee_Sondage_Communautaire_V1-4-3/fb071755-52ce-441b-a829-178c8e58ef2a

Liberia_Community_Survey_v18/07fd73af-d61b-4742-b1f4-a1e303f22130
Liberia_Community_Survey_v18/0b5ca53a-fc60-4699-9b1b-328e4373ca83
Liberia_Community_Survey_v18/0f9a86f8-239a-43b3-be9c-f1de8453dfb6
Liberia_Community_Survey_v18/11f7b35f-1c07-4b46-bba9-4a7a393aa708

may just be in the JSON. the XML might be okay.
http://omkserver.com/omk/data/submissions/Liberia_Community_Survey_Mar2016_MF_v1/7964a442-178d-4c60-ba03-8e50ee554e87/data.json
&
http://omkserver.com/omk/data/submissions/Liberia_Community_Survey_Mar2016_MF_v1/7964a442-178d-4c60-ba03-8e50ee554e87/data.xml

Should be a simple fix. A reminant of Simple ODK code.

zip attached ( issue59.zip ) with form xlsx, xform xml, and an example data xml submission that is converted incorrectly
question with name intro_fail is a select_multiple with the following choices:

1	Skip the entire introduction
2	Paraphrase the introduction
3	Misrepresent the project or the goal of the Red Cross
4	Fail to introduce himself
97	Other

xform-to-json is sometimes interpreting this in submission data as a geopoint question
as used in process-submission.js


USB no longer connects after disconnect

Linux logs timeouts and errors to syslog. This apparently happens because initial USB enumeration is handled by BootROM, and fernly doesn't handle enumeration at all.

I believe these are EP0 requests that are not handled in Fernly.  Support will need to be added.


On reboot ActiveMQ not starting on AWS instance - Red hat latest

Cookbook version
3.0.0
Chef-client version
[]
Platform Details

RedHat latest - AWS

Scenario:

When I provision ActiveMQ cookbook on AWS cloud instance ActiveMQ service starts fine , but after reboot ActiveMQ does not start.
Tried setup with default attributes.

Later realized we need to add entry in systemd to be able to enable service on reboot.
Suggestion : Modify cookbook to enable service with adding entry in Systemd

This should be working in the 4.x cookbook as it explicitly calls enabled unless the node['activemq']['enabled'] is set to false. Please try with the current version and open an issue if this is still present. We'll need the version of RHEL involved as well if this is the case.


Enabling an extension-to-standard workflow

Objective: If an extension is well liked, we should be able to make it standard without changing its structure types or URIs. That way parsers could be written with a stand-alone tag-to-URI front-end and all of the semantics using URIs, allowing the standardization to have only parser-end impact on the implementation.
Challenge: Currently, extension tags get special dispensation in how they behave.
As written in 7.0.2,

a structure with a standard tag has its substructure types limited by the spec
a structure with an extension tag does not have its substructure types limited by the spec
Notably, this is about tags, not structure types; thus in the following example

1 SCHMA
2 TAG _NAME https://gedcom.io/terms/v7/NAME
2 TAG _DATE https://gedcom.io/terms/v7/DATE
0 SUBM
1 NAME Banned
2 DATE 1903
0 SUBM
1 _NAME Permitted
2 DATE 1903
0 SUBM
1 NAME Also Permitted
2 _DATE 1903

the first DATE is prohibited because g7:NAME has no DATE substructure
the second DATE is permitted because an structure with an extension tag has no substructure limitations
the third DATE is permitted because it uses an extension tag

My instinct is that the third should be permitted: it can be seen as a proposal that g7:NAME be allowed a g7:DATE substructure. But the second should not: if you are proposing a new name that can have a date, it should have a new structure type.
Proposal: change the current text

An extended-use standard structure is a structure whose type, tag, and meaning are defined in this document and whose superstructure is a tagged extension structure.

to

An extended-use standard structure is a structure whose type, tag, and meaning are defined in this document and whose superstructure  has a structure type that is not defined in this document.

This issue is also related to #13 which also addresses extended-use standard structures and may need to be updated depending on how that issue is resolved.

Alternatively, we could simply always allow an undocumented standard structure anywhere. Which will make our life easier in several ways (e.g., we'd not need two CENS, two NCHI, etc) but make validation a bit less robust.

The proposed wording is not precise enough, implicitly allowing arbitrary tags

resolved by #24


cirrus-cli: 0.100.0 -> 0.101.0

Description of changes

Changelog
Also corrected license meta from AGPLv3 Only to AGPL3+ source
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Thanks <3


Your Shifty Build

This pull request includes changes from your build using the "Shift Workbench".
Before merging, you need to:

Checkout the shift-build-333 branch
Review all comments for additional changes
Thoroughly test your application

Don't hesitate to send your feedback to<EMAIL_ADDRESS>or share your :heart: for Shift on Twitter.

:information_source: Shift did not find any class reference strings to convert to the ::class constant.

:white_check_mark: Shift did not find any models which unnecessarily set the $table property.

:white_check_mark: Shift did not find any unnecessary attributes listed in the $dates property of your models.

:warning: Shift detected a dependency for the laravel/framework. Unless you have a special requirement for depending on the entire Laravel framework, it's recommended to add dependencies for the specific illuminate packages instead.

:white_check_mark: Shift did not find any of the common Facade chains which would could be streamlined to helpers.

:white_check_mark: Shift did not find any form request rules which needed conversion to array syntax.

:alembic: The Shift Workbench is still in beta. Please report any issues, feedback, or ideas you might have from this build.


first steps for conversion and handling of simple conditionals

add simple conversion of pytket circuits into qir
this can handle:

classical operations
simple conditionals
quantum gates
measurements into default register

I would merge this now as it is and we can continue the discussion later @cqc-alec ?


[Snyk] Upgrade aws-sdk from 2.1611.0 to 2.1623.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade aws-sdk from 2.1611.0 to 2.1623.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 12 versions ahead of your current version.

The recommended version was released on 21 days ago.

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Closing as we should remove aws-sdk rather than update it


feat: use werf to install modules' charts

Its time to close this first attempt to use werf with addon-operator.


ArchiMate 3 relationship rules as implemented in Archi 4

There are known discrepancies between the published set of relationship rules in the ArchiMate 3.0 spec and Archi 4. This is because the rules are in the process of being revised and Archi contains the latest revisions.
Any comments can be added to this issue.

In version 4.0.1, a Trigger relationship cannot be drawn from a Work package to a Implementation event.
Although, this is allowed in the Archimate 3.0 spec - relationship tables  (4th table)
The error seems to be in the file com.archimatetool.model_<IP_ADDRESS>705261613\model\relationships.xml
<source concept="WorkPackage">
...
<target concept="ImplementationEvent" derived="" relations="o">
should be
<target concept="ImplementationEvent" derived="" relations="fot">

Relationship Tables published as part of ArchiMate 3.0 specs on the OpenGroup website are known to contain a large number of errors, so these should not be taken for granted. The Open Group ArchiMate forum is currently working on a new, corrected, version of those tables.
Archi 4.0 has been shipped with a better table coming from this current OpenGroup activity. Unfortunately, if this table fixes 99,99% of errors, few others have been introduced, and this includes the missing triggering from WorkPackage to ImplementationEven you've found.
A new version of Archi will fix this when the Opengroup will officially publish the corrected tables. In the meantime you can fix this issue by editing relationship.xml file by yourself.

Thanks for the anwser ; it works.
----- Mail original -----
De: "Jean-Baptiste Sarrodie"<EMAIL_ADDRESS>À: "archimatetool/archi"<EMAIL_ADDRESS>Cc: "Katzele"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Envoyé: Jeudi 1 Juin 2017 13:57:40
Objet: Re: [archimatetool/archi] ArchiMate 3 relationship rules as implemented in Archi 4 (#243)
Relationship Tables published as part of ArchiMate 3.0 specs on the OpenGroup website are known to contain a large number of errors, so these should not be taken for granted. The Open Group ArchiMate forum is currently working on a new, corrected, version of those tables.
Archi 4.0 has been shipped with a better table coming from this current OpenGroup activity. Unfortunately, if this table fixes 99,99% of errors, few others have been introduced, and this includes the missing triggering from WorkPackage to ImplementationEven you've found.
A new version of Archi will fix this when the Opengroup will officially publish the corrected tables . In the meantime you can fix this issue by editing relationship.xml file by yourself.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub , or mute the thread .

Closing.


[ldd-img] Responsivity units

Recently we added Spectral_Radiance as units: W/m**2/sr/nm.
However, the img:responsivity_r/g/b/pan attributes are actually in terms of what we call responsivity, or perhaps a good name is "Spectral_Responsivity"?  This is a function of exposure time, and converts the DNs from the sensor to spectral_radiance units.  As such, the unit is really Spectral_Responsivity/(DN/sec), or W/m**2/sr/nm/(DN/sec).
Note that I made up the "Spectral_Responsivity" name; I don't know what this is called generally or if in fact there is a generic name for it.  It's disturbing we can't just put in arbitrary combinations of SI units.  DN is not really an SI unit but it is legal as Units_of_Misc currently.
So is it possible to get this in for use with Mars2020?  It might require a pds core point build, or some such.  If so, the responsivity_r/g/b/pan (but not responsivity_factor*) should be changed to use this unit.  But only if.  The alternative is to just put the unit in a  field.
Note that we need a decision on this ASAP as the RDR Peer Review is in a couple of weeks, and we need to know which way to go on the labels.  Thanks.

Jira won't let me in right now to check if similar issue has been addressed. I know any approved SI unit is allowed just not sure on more custom. I am not an unit expert here though - maybe @acraugh or @mit3ch has some advice? If anything, I would think "W/m**2/sr/nm/(DN/sec)", might be allowed under Miscellaneous_Units, but I do think it might need a quick SCR to get it approved. Lock-in to pass new issues is Jan 17 for the next build cycle. I will also ask the DDWG (this Thursday) if we don't have a path forward before then.

Do we need an SCR for tomorrow's DDWG or will we find out then if we actually need such an SCR?

Hi Trent,
I’m not sure this is the definitive answer. I believe you will want to submit an SCR (using the short form). CCB-251 is an example of a request to add a unit of measure.
BTW, I don’t know which browser you use. While Firefox prohibits access to a site with a flawed or expired certificate, Chrome’s “Advanced” option gives you the option of entering the site anyway.
Mitch
From: Trent Hare<EMAIL_ADDRESS>Sent: Tuesday, December 1, 2020 7:14 PM
To: pds-data-dictionaries/PDS4-LDD-Issue-Repo<EMAIL_ADDRESS>Cc: Mitch Gordon<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [pds-data-dictionaries/PDS4-LDD-Issue-Repo] [ldd-img] Responsivity units (#139)
Jira won't let me in right now to check if similar issue has been addressed. I know any approved SI unit is allowed just not sure on more custom. I am not an unit expert here though - maybe @acraughhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Facraugh&data=04|01|mgordon%40seti.org|c7ec4f971b5742dcd4ca08d896572179|deac5258294749c2a474e8ab151104fb|0|0|637424648264528933|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=FfbrGPetRR0%2BT4Y1Yfuu%2BQAgzCgmbF0GlZHGn2qPFvM%3D&reserved=0 or @mit3chhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmit3ch&data=04|01|mgordon%40seti.org|c7ec4f971b5742dcd4ca08d896572179|deac5258294749c2a474e8ab151104fb|0|0|637424648264528933|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Mgtlvqy3Lr9N2ljzf8ta8zoME995V1cpjgPOOnNR9l4%3D&reserved=0 has some advice? If anything, I would think "W/m**2/sr/nm/(DN/sec)", might be allowed under Miscellaneous_Unitshttps://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsbndev.astro.umd.edu%2Fwiki%2FUnit_Classes_Standard_Values%23Miscellaneous_Units&data=04|01|mgordon%40seti.org|c7ec4f971b5742dcd4ca08d896572179|deac5258294749c2a474e8ab151104fb|0|0|637424648264538931|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=EB6MS1KXffeEmy2fD82bOJLrOj%2FrU%2BLtRt2ytbjM6W4%3D&reserved=0, but I do think it might need a quick SCR to get it approved. Lock-in to pass new issues is Jan 17 for the next build cycle. I will also ask the DDWG (this Thursday) if we don't have a path forward before then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpds-data-dictionaries%2FPDS4-LDD-Issue-Repo%2Fissues%2F139%23issuecomment-736901959&data=04|01|mgordon%40seti.org|c7ec4f971b5742dcd4ca08d896572179|deac5258294749c2a474e8ab151104fb|0|0|637424648264538931|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9WokC2qNqPUxFFXU47PZalFX9E6q8OMuQLcbcdmG10s%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABYIQZAXIGI4VEIGK74OPEDSSWBDPANCNFSM4UJLA2QA&data=04|01|mgordon%40seti.org|c7ec4f971b5742dcd4ca08d896572179|deac5258294749c2a474e8ab151104fb|0|0|637424648264548923|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=SaCB2k71OmMA%2FHLU7w4s9xFgzf4menG5iJSj3Okwjdo%3D&reserved=0.

If the next build is Jan 17, can we use it for 2020?  PR is going out in a couple weeks.  I guess as long as we have a decision by next week we can do it "on spec" for the PR?

I will try to capture this in a new SCR.  BTW, the Jira site is back up.

#rgdeen the original text is a little confusing (which term means what). I have a new SCR for the DDWG but it is stated as. Does this make sense and meet your needs.
Problem Statement: Mars2020 has the need to define a new unit for "spectral responsivity", specifically 'W/m**2/sr/nm/(DN/sec)'.
Requested Changes: Add to 'Miscellaneous_Units' the value of 'W/m**2/sr/nm/(DN/sec)' -- also called 'spectral responsivity'.
Description: spectral radiance is generally represented using 'W/m**2/sr/nm'. Mars2020 however stores pixel values in terms of "spectral responsivity". This is a function of exposure time, and converts the DNs from the sensor to spectral_responsivity units. Thus they are calling this:
Spectral Responsivity = 'Spectral_Radiance/(DN/sec)' or 'W/m**2/sr/nm/(DN/sec)'

Correction to Description:
Description: spectral radiance is represented by M2020 using 'W/m**2/sr/nm'.  The calibration parameters however are also a function of exposure time, thus they are expressed as responsivity = Spectral_Radiance/(DN/sec) meaning that spectral_radiance = DN * responsivity / exposure_time.  The addition of spectral_responsivity allows these calibration parameters to be stored in the label with appropriate unit designations.
Note that there are a number of options for spectral_radiance with different units... so in theory there could be a bunch of responsivity units too.  But for all recent Mars missions all we need is the one, W/m**2/sr/nm/(DN/sec) so I'm okay just adding that, and others can add more if needed.  Seems kind of silly to define them all at this point.

@rgdeen To tie this one up for a vote, can you post an example label (section) using this value? I think that will help clear it up for others.

W/m**2/sr/nm/(DN/s) was approved by DDWG and off to CCB review. Timing is another thing. As this is in the main IM (information model), we might not see it available until IM 1.G.0.0 is released.

W/m**2/sr/nm/(DN/s) was approved by DDWG and off to CCB review. Timing is another thing. As this is in the main IM (information model), we might not see it available until IM 1.G.0.0 is released.

CCB passed this also. This option will be available in PDS Information Model v1.G.0.0


Added support for Pipeline in Elasticsearch sink options

Adding support for pipeline to enable some wrangling and enrichment, courtesy Elasticsearch!

Thanks! Great addition. I merged to dev and master but fighting now with pushing the packages to nuget server.


Problems with storio

buck install app emit compile error could not resolve class com.pushtorefresh.storio.operations.PreparedOperation
Project contains 3 module: common, model, app;
./gradlew okbuck output attached.
okbuck.txt

The reason is: storio has an internal module also named common, and it conflicts with the project's common module.
Working on it now.

fixed


Add Concourse pipeline for IAM module (tf 0.12)

issue #188

It looks like the terraform-google-project-factory.tf file was copy-pasted and incompletely find-replaced.

As I see fixtures made for 0.11 terraform. I've finished updating this module for usage with terraform-0.12, so we need to clarify which version should work at CI.

As I see fixtures made for 0.11 terraform. I've finished updating this module for usage with terraform-0.12, so we need to clarify which version should work at CI.

As Aaron mentioned in chat:

The Terraform fixture files for new pipelines should be written using Terraform 0.11. The pipelines
should be configured to use the Docker images which have Terraform 0.12 as the modules being
tested are written with 0.12.

It looks like the terraform-google-project-factory.tf file was copy-pasted and incompletely find-replaced.

@Jberlinsky I did fixed most of the copy-paste issues, it appears to be I've created PR againts incorrect branch, had to create new one with review fixes included:  https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/209
I'm closing current one PR


Fix typo

Fixes a typo in the command line

Seems same typo in https://github.com/chocolatey/docs/blob/master/link-validation.sh. Will fix it there too

@pascalberger thanks for catching that!


Data source Plugin error after provisioning

What happened?
``When creating datasources in Grafana via Kubernetes resources, each datasource appears correctly in the Grafana UI. However, accessing any newly created datasource shows the following error:
"Query error: An error occurred within the plugin"

These datasources, managed via ArgoCD, are created using Kubernetes resources, allowing configuration as code and ensuring consistency across deployments. In this setup, we manage over 100 datasources, so the current behavior requiring manual activation is particularly challenging.

Despite this error, the datasource successfully connects after manually clicking the "Save & Test" button in the UI. This manual intervention is problematic when deploying multiple datasources, as it requires opening each datasource individually to connect it, which is inefficient.
same datasource but you give it save and test and it works

no pod restarts or log errors

datasource yaml example
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDatasource
metadata:
  name: elasticsearch-peru
  namespace: grafana-operator-system
spec:
  valuesFrom:
    - targetPath: "basicAuthUser"
      valueFrom:
        secretKeyRef:
          name: "extra-credentials"
          key: "user"
    - targetPath: "secureJsonData.basicAuthPassword"
      valueFrom:
        secretKeyRef:
          name: "extra-credentials"
          key: "pass"
  instanceSelector:
    matchLabels:
      grafana: default
  datasource:
    access: proxy
    jsonData:
      timeInterval: 5s
      tlsSkipVerify: false
      index: "banco-pe-omni*"
    secureJsonData:
      "basicAuthPassword": ${pass}
    name: ElasticBFPE
    type: elasticsearch
    url: https://internal url
    basicAuth: true
    basicAuthUser: ${user}

What did you expect to happen?
I expected Grafana to automatically validate and establish connections for each datasource upon creation, without needing to manually interact with the "Save & Test" button.
Did this work before?
This is a new setup, so it hasn't worked correctly with the current versions. I haven’t encountered this issue in previous versions, but the environment has changed recently.
How do we reproduce it?
1- Deploy Grafana with Grafana Operator  and Grafana version 11.2.2.
2- Create a datasource using a Kubernetes resource.
3- Access the datasource in the Grafana UI.
4- Observe the initial error "Query error: An error occurred within the plugin".
5- Manually click "Save & Test" in the UI to establish the connection.
Is the bug inside a dashboard panel?
No, the issue occurs within the datasource configuration UI and not within a dashboard panel.
Environment (with versions)?
Grafana: 11.2.2
OS: linux (kubernetes)
Browser: chrome Versión 129.0
Grafana platform?
Kubernetes
Datasource(s)?
Elasticsearch v8.x

Hi @jcapote22, if you have access to backend logs, are there any error messages logged there that appear when this happens?
Also, what is the version of Grafana Operator you're using? Thanks!

We've gathered more information to help diagnose this issue:

Scope of the Issue: The problem occurs exclusively with the Elasticsearch datasource. Other datasources, such as Instana and Prometheus, are unaffected and connect automatically without needing the "Save & Test" workaround.

Elasticsearch Deployment: Our Elasticsearch instance is running within a Kubernetes cluster.

Grafana User Permissions: The Grafana user interacting with the Elasticsearch datasource has been granted the roles: monitor/main, monitor/remote, and info. These permissions should be sufficient for typical query operations, so we’re unsure why the initial error occurs only for Elasticsearch.

Error Logs:
Before "Save & Test": Attaching logs showing the initial error message ("Query error: An error occurred within the plugin") encountered upon accessing the datasource.
logger=tsdb.elasticsearch endpoint=queryData pluginId=elasticsearch dsName=ElasticBFPE dsUID=b80703e4-c812-46a2-8b29-f13654b90b9a uname="juan francisco capote medina" fromAlert=false t=2024-11-08T14:11:53.32817054Z level=error msg="Failed to get data source info" error="timeField cannot be cast to string"
logger=context userId=2 orgId=1 uname="juan francisco capote medina" t=2024-11-08T14:11:53.32823614Z level=error msg=InternalError error="[plugin.downstreamError] client: failed to query data: timeField cannot be cast to string"

![Image](https://github.com/user-attachments/assets/9386b429-4962-499d-a33b-5fca82406c2f)

After "Save & Test": Attaching logs indicating a successful connection once "Save & Test" is manually triggered.
Environment:
logger=tsdb.elasticsearch endpoint=callResource pluginId=elasticsearch dsName=ElasticBFPE dsUID=b80703e4-c812-46a2-8b29-f13654b90b9a uname="juan francisco capote medina" t=2024-11-08T14:17:56.897675656Z level=info msg="Response received from Elasticsearch" statusCode=200 status=ok duration=98.318128ms stage=databaseRequest contentLength=577 resourcePath=
logger=tsdb.elasticsearch endpoint=callResource pluginId=elasticsearch dsName=ElasticBFPE dsUID=b80703e4-c812-46a2-8b29-f13654b90b9a uname="juan francisco capote medina" t=2024-11-08T14:17:57.163600041Z level=info msg="Response received from Elasticsearch" statusCode=200 status=ok duration=57.692506ms stage=databaseRequest contentLength=1240839 resourcePath=banco-pe-omni*/_mapping

Grafana Operator Version: bitnami/grafana-operator:5.14.0-debian-12-r0
bitnami/grafana-operator:5.14.0-debian-12-r0
grafana/grafana:11.2.2


[B.Tech Tea Shop] Enhancing content and components to Contact Section

Conatct section #3497

Close #3497

Checklist:

[✅] I have mentioned the issue number in my Pull Request.
[✅] I have commented my code, particularly in hard-to-understand areas

Before

After

@MohitGupta121  @TusharKesarwani  Kindly, review this PR


Added posibility to change discussion-tree chevrons

This works well, but currently but after/syntax/gitlab.vim file has a syntax match that includes the chevrons when looking for a username. Can we look into fixing that?
I'm not sure how this would be done, possibly by dynamically searching for the value set in the configuration? This is what it looks like right now.
syntax match Username "\%([]\)\@<= @\S*"
syntax match Mention "\%([] \)\@<!@\S*"

This is what I came up with. In colors.lua we can set global variables:
-- Set icons into global vim variables for syntax matching
local expanders = state.settings.discussion_tree.expanders
vim.g.gitlab_discussion_tree_expander_open = expanders.expanded
vim.g.gitlab_discussion_tree_expander_closed = expanders.collapsed
vim.g.gitlab_discussion_tree_draft = ''
vim.g.gitlab_discussion_tree_resolved = '✓'
vim.g.gitlab_discussion_tree_unresolved = '-'

And then in syntax.vim we can use those variables to match:
if filereadable($VIMRUNTIME . '/syntax/markdown.vim')
  source $VIMRUNTIME/syntax/markdown.vim
endif

syntax match Date "\v\d+\s+\w+\s+ago"
highlight link Date GitlabDate

execute 'syntax match Unresolved /\s' . g:gitlab_discussion_tree_unresolved . '\s\?/'
highlight link Unresolved GitlabUnresolved

execute 'syntax match Resolved /\s' . g:gitlab_discussion_tree_resolved . '\s\?/'
highlight link Resolved GitlabResolved

execute 'syntax match GitlabDiscussionOpen /^' . g:gitlab_discussion_tree_expander_open . '/'
highlight link GitlabDiscussionOpen GitlabChevron

execute 'syntax match GitlabDiscussionClosed /^' . g:gitlab_discussion_tree_expander_closed . '/'
highlight link GitlabDiscussionClosed GitlabChevron

execute 'syntax match Draft /' . g:gitlab_discussion_tree_draft . '/'
highlight link Draft GitlabDraft

execute 'syntax match Username "@\w\+"'
highlight link Username GitlabUsername

execute 'syntax match Mention "\%([' . g:gitlab_discussion_tree_expander_open . g:gitlab_discussion_tree_expander_closed . '] \)\@<! @\S\+"'
highlight link Mention GitlabMention

let b:current_syntax = "gitlab"

What do you guys think of this?

Looks good to me 👍

I added it to my branch, though i'm not sure about the syntax file. The old one had more syntax matches, maybe they werent used?

I added it to my branch, though i'm not sure about the syntax file. The old one had more syntax matches, maybe they werent used?

Yeah I condensed them into one thing, and fixed up some of those changes directly on your branch! I'll merge this into develop now, it'll probably be in main in the next few days, I'll ship it along with the keymap changes.
Thanks for your contribution!


Add Jinja filter for using environmental variables in templates

Adding a Jinja custom filter that allows using environmental variables in templates. This is very useful for passing in secrets for external stages without logging them to STDOUT, like it is done for command line parameters.

Hey @tsavko, thank you so much for your contributions to schemachange! We had two different PRs with support for using environment variables in Jinja. I just published #91 so this one is redundant now. I understand that the two were slightly different approaches, so please let me know if the new features from #91 won't meet your needs for some reason. Thanks again!

Hey @sfc-gh-jhansen, the approach in #91 works just as well, thanks for the info!

Hey @sfc-gh-jhansen, #91 doesn't fully cover our needs, but I was able to easily extend it in #95. Please review that one when you get a chance. Thanks!


Update calibration config files

Update wrapper by adding 'Calibrator' tag to allow remote calibration from motorgui
Merged together calib file for arm and hand

Too old PR, closing.
Anyway we have a backup.


Spell checker integration

During the review meeting an issue with one of the deliverables came up: It has lots of typos!
To prevent such problems in the feature, we might integrate a spell checker in the PDF generator.
Pedro already provided a link to this nice library: https://github.com/blatinier/pyhunspell
The idea would be:

check spelling during PDF generation
mark words with wrong spelling (RED / red line)
add field to document options (spell_check: On / Off)

Optional ideas:

add a watermark to documents which were generated with activated spell checking (to prevent accidental submission of these drafts)
add a wikipage "Dictionary" to which everybody can add words that should be in the spell checker dictionary

Maybe include there selection of the base dictionary (e.g. en-GB vs. en-US)
El 22 sept. 2016 11:15, "Manuel Peuster"<EMAIL_ADDRESS>escribió:

During the review meeting an issue with one of the deliverables came up:
It has lots of typos!
To prevent such problems in the feature, we might integrate a spell
checker in the PDF generator.
Pedro already provided a link to this nice library:
https://github.com/blatinier/pyhunspell
The idea would be:

check spelling during PDF generation
mark words with wrong spelling (RED / red line)
add field to document options (spell_check: On / Off)

Optional ideas:

add a watermark to documents which were generated with activated
spell checking (to prevent accidental submission of these drafts)
add a wikipage "Dictionary" to which everybody can add words that
should be in the spell checker dictionary

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hkarl/mw2pdf/issues/6, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADKqcF-J_8XsSQ8BRqcDeA-hbNAgEBpxks5qskcrgaJpZM4KDre5
.

Played around with spell checking. Learned that its not as trivial as I thought ;-)

Working on the Latex files isn't possible.
Directly manipulating PDFs is no fun.
Marking mistakes in the *.md files is still tricky. Using format changes like <strike> break Latex because spelling mistakes might occur everywhere, e.g., in section headings. Using ??word?? to mark mistakes seems to be reasonable safe!

Commit b4e9a49d5b25d804843db1cfad9b99001bc507d5 provides a first working version without much features.
Use: run build.py with --spellcheck to enable it.
All mistakes are marked like: ??bad-word?? in the output PDF.
Note: Its not activated on the production system yet.


Eagerly Convert Headers Always in Download

Description
Always add azure-eagerly-convert-headers: true to Context for the first range download. This optimizes performance of converting HttpHeaders to the download type.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Add new exercise crypto-square

Add described in #96

Thanks @matthewmorgan, you rocks!

Yeah! Followed the additional process discussed on #106, git push -f origin new-exercise-crypto-square works like a charm and PRs are shown as Merged.

Right on.  Good work.  Now I'll have enough Merge points to level up!

Sweeeeet!


Increment version for storage releases

Increment package version after release of Azure.Storage.Blobs

woops I approved it too many times..


Support for multiple interdependent container content packages

Currently each container package is analysed separately which means that dependencies from one container content package to another is not correctly reflected in the analysis as the plugin incorrectly assumes that this package must run standalone on AEM.
There should be a way to merge with another container package before executing analysis tasks like api-regions-exportsimports which otherwise emits lots of false positives.

Although the readme states one should add an artificial analyse module containing all relevant container packages as dependencies this does sometimes not scale well

As container packages are not supposed to have package dependencies in their metadata (compare with the long discussion in https://issues.apache.org/jira/browse/JCRVLT-443) those dependencies need to be added on another level:

either dedicated plugin parameters or
(filtered) Maven dependencies


Fix G2 unmarshalling

This PR fixes g2_unmarshall routine. Current implementation doesn't work: arguments do not match signature of curve_point constructor.

Thanks!


Proposal for handling migrations with Drizzle ORM

Hello :)
It's really nice to works with SQLocal 😄
Here is some code to handle migrations with drizzle on the browser:
import { sql } from "drizzle-orm";
import { MigrationMeta } from "drizzle-orm/migrator";
import { SqliteRemoteDatabase } from "drizzle-orm/sqlite-proxy";
import { SQLocalDrizzle } from "sqlocal/drizzle";
import * as schema from "../schema";
import journal from "./meta/_journal.json";

const digestMessage = async (message: string) => {
  const msgUint8 = new TextEncoder().encode(message); // encode as (utf-8) Uint8Array
  const hashBuffer = await crypto.subtle.digest("SHA-256", msgUint8); // hash the message
  const hashArray = Array.from(new Uint8Array(hashBuffer)); // convert buffer to byte array
  const hashHex = hashArray
    .map((b) => b.toString(16).padStart(2, "0"))
    .join(""); // convert bytes to hex string
  return hashHex;
};

const readMigrationFiles = async () => {
  const migrationQueries: MigrationMeta[] = [];

  if (!journal) {
    throw new Error(`Can't find meta/_journal.json file`);
  }

  for (const journalEntry of journal.entries) {
    const { default: query } =
      await (import(`./${journalEntry.tag}.sql?raw`) as Promise<
        { default: string }
      >);
    const result = query.split("--> statement-breakpoint").map((it) => it);

    migrationQueries.push({
      sql: result,
      bps: journalEntry.breakpoints,
      folderMillis: journalEntry.when,
      hash: await digestMessage(query),
    });
  }

  return migrationQueries;
};

export const migrate = async (
  db: SqliteRemoteDatabase<typeof schema>,
  transaction: SQLocalDrizzle["transaction"],
) => {
  const migrations = await readMigrationFiles();
  const migrationsTable = "__drizzle_migrations";
  const migrationTableCreate = sql`
    CREATE TABLE IF NOT EXISTS ${sql.identifier(migrationsTable)} (
      id SERIAL PRIMARY KEY,
      hash text NOT NULL,
      created_at numeric
    )
  `;

  await db.run(migrationTableCreate);

  const dbMigrations = await db.values<[number, string, string]>(
    sql`SELECT id, hash, created_at FROM ${
      sql.identifier(migrationsTable)
    } ORDER BY created_at DESC LIMIT 1`,
  );

  const lastDbMigration = dbMigrations[0] ?? undefined;

  await transaction(async (tx) => {
    for (const migration of migrations) {
      if (
        !lastDbMigration || Number(lastDbMigration[2])! < migration.folderMillis
      ) {
        for (const stmt of migration.sql) {
          await tx.sql(stmt);
        }
        await tx.sql(
          `INSERT INTO ${
            sql.identifier(migrationsTable)
          } ("hash", "created_at") VALUES(${migration.hash}, ${migration.folderMillis})`,
        );
      }
    }
  });
};

Here is what I have on the first line on my WebWorker:
let db: SqliteRemoteDatabase<typeof schema>;

async function initialize() {
  const { driver, transaction } = new SQLocalDrizzle("ashiso.sqlite3");
  db = drizzle(driver, { schema });
  await migrate(db, transaction);
  await db.run(sql`PRAGMA journal_mode = WAL;`);
}

I'm using this on my webapp, and it's working totally fine, hope it helps other 😃

Thanks for this. It is similar to what I implemented here to propose for implementation into Drizzle. I have not implemented it into SQLocal itself because Drizzle's migration inner workings are still in flux while Drizzle works toward a version 1.0 release, and ideally, that code should live in the Drizzle repo alongside their other migrators. I explained a bit more on #32.


Add on-failure option to comment-summary-in-pr setting

This PR resolves https://github.com/actions/dependency-review-action/issues/538 by changing comment-summary-in-pr from a boolean to an enum of always, never, on-failure. When on-failure is used the summary will only be posted in a comment if the workflow status is 'failure'.

@sgmurphy This idea looks good, thank you 👍. It will existing behavior (true/false values) in order to keep supporting users. I'm not sure how you'd like to proceed, an idea:

We check the input value and if it's a boolean we map true/false to the new string values.
Update the docs with a mention to this change.
We do a new release bumping the minor version number to 3.1, minimizing impact to existing users with pinned versions.

I can help with (2) and (3), but would like your input on (1), how do you think we should handle this transition for existing users without breaking their existing setups?

@febuiles Thanks for the feedback. I updated the PR to map true => 'always' and false => 'never' so this change shouldn't impact existing users. I also added some unit tests to confirm the mapping works as expected.

@sgmurphy the new options are available starting with v3.0.8, thank you very much!


void-variable root when evaluating editorconfig autoloads

I recently upgraded all straight-pull-all and when trying to rebulid the packages I encountered an error when building editorconfig package:
Debugger entered--Lisp error: (void-variable root)
  eval(root)
  straight--activate-package-autoloads((:type git :flavor melpa :host github :repo "editorconfig/editorconfig-emacs" :package "editorconfig" :local-repo "editorconfig-emacs"))
  #f(compiled-function () #<bytecode -0x15c018de404766a9>)()
  straight--transaction-exec(use-package-\"fd7eeda9dbc814ea9d6411fedf604a84\"-nil-nil :now #f(compiled-function () #<bytecode -0x15c018de404766a9>))
  straight-use-package(editorconfig)

my config:
(use-package editorconfig
  :straight t
  :config
  (editorconfig-mode))

After disabling the editorconfig package the rest of the packages build correctly, so it's only happening for editorconfig so far.
I'm not sure if this is a straight or editorconfig issue.
Originally posted by @danielpza in https://github.com/radian-software/straight.el/issues/946#issuecomment-1146656650
build-cache.el:
https://gist.github.com/danielpza/1dfca0af637f988b5cb73b2130d80f87

Can you try evaluating the following in your *scratch* buffer?
It will install straight.el and editorconfig in a clean environment.
When it has finished, a buffer should pop up with the results. Please share those here.
(straight-bug-report
  :post-bootstrap
  (straight-use-package 'editorconfig)
  (editorconfig-mode)
  (with-current-buffer
      (find-file-noselect
       (straight--build-file "editorconfig" "editorconfig-autoloads.el"))
    (print
     (buffer-string))))

huh, I guess it worked in a clean environment?
Test Case
(straight-bug-report
  :post-bootstrap
  (straight-use-package 'editorconfig)
  (editorconfig-mode)
  (with-current-buffer
      (find-file-noselect
       (straight--build-file "editorconfig" "editorconfig-autoloads.el"))
    (print
     (buffer-string))))

Test run at: 2022-06-06 16:27:12
system-type: gnu/linux
straight-version: prerelease (HEAD -> master, origin/master) 4517e11 2022-04-13
emacs-version: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2022-05-18

Output
Bootstrapping straight.el...
Bootstrapping straight.el...done
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) 9430316 2022-06-06
Cloning editorconfig-emacs (for editorconfig)...
Cloning editorconfig-emacs (for editorconfig)...done
Building editorconfig...
Building editorconfig...done

";;; editorconfig-autoloads.el --- automatically extracted autoloads  -*- lexical-binding: t -*-
;;
;;; Code:

;;;### (autoloads nil \"editorconfig\" \"editorconfig.el\" (0 0 0 0))
;;; Generated autoloads from editorconfig.el

(autoload 'editorconfig-apply \"editorconfig\" \"\\
Get and apply EditorConfig properties to current buffer.

This function does not respect the values of `editorconfig-exclude-modes' and
`editorconfig-exclude-regexps' and always applies available properties.
Use `editorconfig-mode-apply' instead to make use of these variables.\" t nil)

(defvar editorconfig-mode nil \"\\
Non-nil if Editorconfig mode is enabled.
See the `editorconfig-mode' command
for a description of this minor mode.
Setting this variable directly does not take effect;
either customize it (see the info node `Easy Customization')
or call the function `editorconfig-mode'.\")

(custom-autoload 'editorconfig-mode \"editorconfig\" nil)

(autoload 'editorconfig-mode \"editorconfig\" \"\\
Toggle EditorConfig feature.

To disable EditorConfig in some buffers, modify
`editorconfig-exclude-modes' or `editorconfig-exclude-regexps'.

This is a global minor mode.  If called interactively, toggle the
`Editorconfig mode' mode.  If the prefix argument is positive,
enable the mode, and if it is zero or negative, disable the mode.

If called from Lisp, toggle the mode if ARG is `toggle'.  Enable
the mode if ARG is nil, omitted, or is a positive number.
Disable the mode if ARG is a negative number.

To check whether the minor mode is enabled in the current buffer,
evaluate `(default-value \\\\='editorconfig-mode)'.

The mode's hook is called both when the mode is enabled and when
it is disabled.

\\(fn &optional ARG)\" t nil)

(autoload 'editorconfig-find-current-editorconfig \"editorconfig\" \"\\
Find the closest .editorconfig file for current file.\" t nil)

(autoload 'editorconfig-display-current-properties \"editorconfig\" \"\\
Display EditorConfig properties extracted for current buffer.\" t nil)

(defalias 'describe-editorconfig-properties 'editorconfig-display-current-properties)

(autoload 'editorconfig-format-buffer \"editorconfig\" \"\\
Format buffer according to .editorconfig indent_style and indent_width.\" t nil)

(autoload 'editorconfig-version \"editorconfig\" \"\\
Get EditorConfig version as string.

If called interactively or if SHOW-VERSION is non-nil, show the
version in the echo area and the messages buffer.

\\(fn &optional SHOW-VERSION)\" t nil)

(register-definition-prefixes \"editorconfig\" '(\"editorconfig-\"))

;;;***

;;;### (autoloads nil \"editorconfig-conf-mode\" \"editorconfig-conf-mode.el\"
;;;;;;  (0 0 0 0))
;;; Generated autoloads from editorconfig-conf-mode.el

(autoload 'editorconfig-conf-mode \"editorconfig-conf-mode\" \"\\
Major mode for editing .editorconfig files.

\\(fn)\" t nil)

(add-to-list 'auto-mode-alist '(\"\\\\.editorconfig\\\\'\" . editorconfig-conf-mode))

(register-definition-prefixes \"editorconfig-conf-mode\" '(\"editorconfig-conf-mode-\"))

;;;***

;;;### (autoloads nil \"editorconfig-core\" \"editorconfig-core.el\"
;;;;;;  (0 0 0 0))
;;; Generated autoloads from editorconfig-core.el

(autoload 'editorconfig-core-get-nearest-editorconfig \"editorconfig-core\" \"\\
Return path to .editorconfig file that is closest to DIRECTORY.

\\(fn DIRECTORY)\" nil nil)

(autoload 'editorconfig-core-get-properties \"editorconfig-core\" \"\\
Get EditorConfig properties for FILE.
If FILE is not given, use currently visiting file.
Give CONFNAME for basename of config file other than .editorconfig.
If need to specify config format version, give CONFVERSION.

This functions returns alist of properties.  Each element will look like
'(KEY . VALUE) .

\\(fn &optional FILE CONFNAME CONFVERSION)\" nil nil)

(autoload 'editorconfig-core-get-properties-hash \"editorconfig-core\" \"\\
Get EditorConfig properties for FILE.
If FILE is not given, use currently visiting file.
Give CONFNAME for basename of config file other than .editorconfig.
If need to specify config format version, give CONFVERSION.

This function is almost same as `editorconfig-core-get-properties', but returns
hash object instead.

\\(fn &optional FILE CONFNAME CONFVERSION)\" nil nil)

(register-definition-prefixes \"editorconfig-core\" '(\"editorconfig-core--\"))

;;;***

;;;### (autoloads nil \"editorconfig-core-handle\" \"editorconfig-core-handle.el\"
;;;;;;  (0 0 0 0))
;;; Generated autoloads from editorconfig-core-handle.el

(register-definition-prefixes \"editorconfig-core-handle\" '(\"editorconfig-core-handle\"))

;;;***

;;;### (autoloads nil \"editorconfig-fnmatch\" \"editorconfig-fnmatch.el\"
;;;;;;  (0 0 0 0))
;;; Generated autoloads from editorconfig-fnmatch.el

(autoload 'editorconfig-fnmatch-p \"editorconfig-fnmatch\" \"\\
Test whether STRING match PATTERN.

Matching ignores case if `case-fold-search' is non-nil.

PATTERN should be a shell glob pattern, and some zsh-like wildcard matchings can
be used:

*           Matches any string of characters, except path separators (/)
**          Matches any string of characters
?            Thank you @progfolio

I did another update on the editorconfig package and it fixed on its own. I suspect something went wrong with the package update in my machine the first time but I'm not really sure what caused it.
It's all good now, I think it's safe to close the issue, thanks for your help :)

Thanks for the update. Glad it's working for you now.


Apply CLI options even when no pyproject.toml is found

Thanks for all your fantastic work on this remarkable tool!
I've been having an issue that when there is no pyproject.toml found, command line options are ignored in lieu of the hard-coded defaults. For example, foo.py produces two F401 errors by default (good!), but when I try to specify ruff options via the CLI (--select, --ignore, etc.) they're not respected (bad!).
# foo.py
import os
import sys

$ ruff --ignore=F401 foo.py
Found 2 error(s).
foo.py:1:8: F401 `os` imported but unused
foo.py:2:8: F401 `sys` imported but unused
2 potentially fixable with the --fix option.

I can make these command line options work if I put a pyproject.toml anywhere on the path, regardless of its content. I imagine the intended behavior is that options on the CLI should override defaults regardless of whether or not a pyproject.toml is found.
From what I can tell, when a pyproject.toml is found, ruff::resolve() calls Resolver::resolve_settings(), which ultimately calls Configuration::apply(), which is responsible for joining the command line options:
https://github.com/charliermarsh/ruff/blob/765d21c7b06e780fb91cbcc79909836883faf0dd/src/resolver.rs#L131-L133
However, Configuration::apply() is not called unless a pyproject.toml is found. It looks like 9853b0728ba9289753cb3be984de75677a4713c6 removed the following lines which had been responsible for merging command line options with the default configuration:
https://github.com/charliermarsh/ruff/blob/4bb6b4851a639d1855c7fb5d02ea53a074c9a178/src/main.rs#L93-L98
This PR adds back this functionality, although my solution is a bit inelegant given the recent removal of this sort of logic from main.rs. Maybe a better fix would be to break the call to Configuration::apply() above out into a separate method that is called in all cases? Happy to work more on it if so.
Either way, figured I'd offer the PR instead of just opening an issue. :) (Sorry for any silly issues; I'm a baby rustacean.)

Thank you!

(I really appreciate the clarity and thoroughness of your PR summary too.)

Thank you! Very kind of you to say. :)


Add help text to create intent page

We need more of an indicator for users that they need to input multiple examples to the user says and agent responses. Something like the below:
@broham89 should we also add an Add button in case people want to click rather than press enter?

Could you give me the height of the input? I wanna create an enter icon for it

45px @broham89

I believe the plus icon is enough to signify to the user to click to add input

@broham89 how about "Type sample dialogue and hit Enter."

Is the plus icon easy to add with the React components we're using?

addressed by 397193a94585930ee648dc56a96fafbf8c3935f7 but still waiting on confirmation that it is good.

The plus icon is in materialize named add

Fixed the colors a little bit here: ca22ecb89299196ee6fe31f37a725d23393d04c3
Consider this one closed.


upgrade to AI v2

Now that AI v2 is released, can we upgrade this library to use the latest?
I'm happy to provide a PR, because I really need a feature that is in v2.

Oh I didn’t know it was officially released out of alpha/beta! Yeah if it isn’t too big of change and you want to give it a shot that’d be amazing!! 🙌🙌
If not I can try to take a crack at it but I’m away next week so might be tough to squeeze it in.
Any help is always super appreciated! ❤

I was looking at it now and it seems like v2 is a big rewrite compared to v1
I'll give it a try over the weekend and see how far I can get :)

You rock!
Let me know if you need me to look at anything :+1:

Hey Mark, I'm sorry but I didn't get much done last weekend. I'll be off for 2 weeks now, will try again when I'm back. I also couldn't find any reference to v2 on official docs, so I guess it's not that public yet. Feel free to have a look too if you wish.

Is this lib still in active development? Or should we use angular-application-insights-v2 instead?

@MarkPieszak same question as @ntziolis above, is this enhancement still on hold?

@MarkPieszak We really like your lib it's fine if you are too busy to update ;) Just give the community a hint what should we do ;) should we wait, contribute or just move on? :)

Just a heads up: I tried updating this package to appinsights v2 long ago, but faced too may breaking changes. Given that we only needed a thin angular compatibility layer, I ended up with this new package: https://github.com/goenning/ng-appinsights
It might not have all features supported by angular-application-insights, but some people might find it useful.


Add CleverReach

Adds or updates the following companies, events, or universities:

CleverReach

Checklist
Company updates

[X] I have put the most recent relevant date in the "Last Update" column
[ ] I have linked to the article about the change, not the company's homepage (Please put N/A if there is no public post)

-> First Hand Knowledge :-)

Closing due to rebase and staleness. Feel free to re-open after fixes, thanks for your patience.


Unknown prop 'isInitiallOpen' on drawer

Problem description
warning.js:44 Warning: Unknown prop isInitiallyOpen on  tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
in div (created by Paper)
in Paper (created by AppBar)
in AppBar (created by Header)
in div (created by Paper)
in Paper (created by Drawer)
in div (created by Drawer)
in Drawer (created by Header)
in div (created by Header)
in Header (created by Connect(Header))
in Connect(Header) (created by Container)
in div (created by Container)
in Container (created by Connect(Container))
in Connect(Container) (created by FirebaseConnect)
in FirebaseConnect (created by RouterContext)
in RouterContext (created by Router)
in Router (created by App)
in div (created by App)
in Provider (created by App)
in MuiThemeProvider (created by App)
in App (created by Connect(App))
in Connect(App)
Steps to reproduce
The latest update cleared tons of these, but I'm still getting this when using the drawer.
Versions

Material-UI: 0.15.2
React: 15.2.1
Browser: Latest Chrome

@justinhandley You have most likely misspell the property. It's initiallyOpen.


github actions attempt 2

fixes #82

The ubuntu environment includes shellcheck by default, so you need to add this and remove TODO comment from install_test.sh.
- name: shellcheck
  if: matrix.os == 'ubuntu-latest'
  run: shellcheck -s sh ./*.sh


Replace long polling to receive events with Server Sent Events (SSE)

Description:
Server Sent Events(SSE) is better than long polling because it creates only 1 persisted connection to server and keeps it open "forever". This technology was specifically designed to overcome challenges related to short/long polling.
SSE is built on top of HTTP protocol, so also can be used in communication between servers. Also SSE is more compliant with existing IT infrastructure like (Load Balancer, Firewall, etc), unlike WebSockets which can be blocked by some firewall.
Currently all major web browsers supports SSE (for those which don't support it's easy to do fallback to long/short polling). There are some cool features which browsers support out of the box:

automatic reconnection
remember lastEventId and send it automatically on reconnection.

Check this for reference:

https://www.html5rocks.com/en/tutorials/eventsource/basics/
https://stackoverflow.com/questions/9397528/server-sent-events-vs-polling
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events
supported browsers: https://caniuse.com/#feat=eventsource

moved

What can I do to push this forward? Do I need to create a proposal to protocol change as described here?

Yup. That'd be the first steps

I've thought about this a bit before, so I'll dump my thoughts here.  (I don't have time to work on it right now.)

create a new endpoint to do sync over SSE (e.g. /sync/stream)

used to get the same data as continually calling /sync with the same parameters
accepts the same parameters as /sync, except without since or timeout
instead of using the since query parameter, the next batch token will be passed through the Last-Event-ID header.

each event will have the same format as what /sync returns.  The id of each event will be the next_batch token

the server sends events in exactly the same way that it would send responses to /sync calls with the since parameter set to the previous next_batch

Using SSE in this way means that existing code can be reused for SSE

Created proposal for the change

Isn't there a websocket draft already? https://github.com/matrix-org/matrix-doc/blob/master/drafts/websockets.rst Wouldn't that one already serve the same purpose?

The important thing is that event stream is just an HTTP request and it should be easier to use it from native clients (iOS, Android) and for cross server communication

Ah, so it's just easier to implement. Fair enough, I guess that is as good enough of a reason as any, in the end it doesn't really matter after all what approach is used. So I assume if this goes through that websocket draft will go unused? (It'd be a bit weird to attempt to implement both)

For what it's worth, this is somewhat not only blocking F-Droid/non-gapps Android matrix clients from decent battery life, but also those on Linux mobiles like the PinePhone/PineTab/Librem 5, or new ARM64 laptops like repurposed Chromebooks with Linux or the Pinebook. (Since on those platforms, there simply isn't any Firebase or similar available either.)


Installer complains there's a composer issue when there isn't

Currently, the installer complains composer hasn't been updated, yet clicking the Next button without doing anything completes the install.

Looks like this is the result of new namespaces not being re-loaded after an initial composer dumpautoload so the subsequent reflection test fails.
Easy solution: run install and test as independent requests.


Not supported

Hello . I'm trying this for first time. Please help me fix this one?
i can downgrade windows or reinstall if i have to
I tried updating RDPwrapper same not supported

https://github.com/stascorp/rdpwrap/issues/1022#issuecomment-596437997

#1022 (comment)

getting access denied now. everything is green.

Great - that means everything is working.
You just need to work out what the username and password on that computer is. You need to have set a password, and the username might not be the name displayed when you log in. Run 'control userpasswords2' to check what the username really is.

Great - that means everything is working.
You just need to work out what the username and password on that computer is. You need to have set a password, and the username might not be the name displayed when you log in. Run 'control userpasswords2' to check what the username really is.

When i rdp to this pc it is still logging the user out

Yes, it is meant to do that. Especially with 'Single Session per User" selected.
There is a group working on ways to let it create a new session instead of logging the user out at #1064 . They are not having much success.
There is also session shadowing, but it seems that requires a network that logs everyone in using a domain server.
But the problem you opened this issue on is fixed, as rdpwarpper is running on your system. I suggest you close this off and do your research on any other issues you are having.

Yes, it is meant to do that. Especially with 'Single Session per User" selected.
There is a group working on ways to let it create a new session instead of logging the user out at #1064 . They are not having much success.
There is also session shadowing, but it seems that requires a network that logs everyone in using a domain server.
But the problem you opened this issue on is fixed, as rdpwarpper is running on your system. I suggest you close this off and do your research on any other issues you are having.

ok fixed that now new problem , its not mirroring , seems like rdpwrapper created new user?  i can connect but its not the same screen , same pc . wth when i check there is only one user

Duplicate of https://github.com/stascorp/rdpwrap/issues/983


Add project styling guide and best practices

Introduce a comprehensive style guide outlining conventions and best practices for project styling, including guidelines for JavaScript, CSS, and component structure.

add a style guide in client folder


Add switch to disable launcher updates

Flatpak https://github.com/flathub/info.beyondallreason.bar and some other versions need to patch code currently to disable updates, this is to add switch to not have to do that.

Fixed in<PHONE_NUMBER>f7153fc6b4f92eb6152b0056d9b75d


Future support for translations of site to other languages

Versions of the cdevents.dev narrative content in other languages can be added at any time by adding a new, language-specific content root under the content folder in this repo and providing translated duplicates of the files found in content/en.
The [languages] section of config.toml should be updated as documented in https://www.docsy.dev/docs/language/
UI strings are maintained in the i18n folder. You may need to update these if the desired language is not already supported.
In development, run hugo server --printI18nWarnings when doing translation work, as it will give you warnings on what strings are missing.
Translations of the specification documentation will require language-specific forks of the spec repo. The docs subfolder of the content/<new language>/ folder should be linked as a git submodule to the appropriate fork. Note the need to manually maintain and synchronise the releases of translated versions of the spec.

How common is it nowadays that these kinds of websites have support for multiple languages? And what languages would then be the most common ones? I believe some such existing multi-language websites have a different initial language than English and then English translation is added to reach a wider audience, which is not the case for CDEvents.
I currently don't see that we should spend time on translating this info to any other language. It might be interesting if we sometime foresee an increase in CDEvents adopters in some region where English is not commonly understood.
I see a risk that this issue will not be resolved anytime soon. Should we instead document the description from this issue in e.g. a CONTRIBUTING.md document in this repo and then close this issue for now?

If the intent is to establish an international standard, diversity is particularly important, in order to identify localisation challenges that may sit outside the experience of contributors from some regions. Similarly, adoption of a standard can be rapid in highly active tech regions like India and China, if there is localised documentation available to simplify the process.
The CDF has a SIG dedicated to supporting this process: https://github.com/cdfoundation/sig-chinese-localization


Allow usage of a provided buffer

Closes #238

Coverage: 77.686% (+0.1%) from 77.581% when pulling e208c769adb5b57adc7604590abf1f4e9c9a0173 on feat/238/provided-buffer into 4ac21d70f79d22300105342629a92093ff9b5904 on main.


feature(aux-go): aux golang client

expand aptos golang client functionality
replace gopkg.in/yaml.v3 with github.com/goccy/go-yaml for better support of 0x prefixed strings (see here)
add aux specific functions.

Rebase? See some diffs from a previous commit


fix api docs when deploying under /api base url

 API-Docs: Url zur openapi.json ist falsch, wenn das backend unter /api gehostet ist

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 42 (0.0%)  changed or added relevant lines in 5 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.06%) to 83.92%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/util/config.rs
0
3
0.0%

services/src/util/apidoc.rs
0
5
0.0%

services/src/util/server.rs
0
7
0.0%

services/src/server.rs
0
13
0.0%

services/src/pro/server.rs
0
14
0.0%

Files with Coverage Reduction
New Missed Lines
%

operators/src/source/ogr_source/mod.rs
1
92.72%

services/src/pro/server.rs
2
0%

services/src/server.rs
2
0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
37476

Relevant Lines:
44657

💛  - Coveralls

bors merge


Make relative to contain absolute positioned elements

Fixes #11

Thanks @strongpauly will try and get to bug smashing this weekend.