fix(pipelinerun): resolve issue with PipelineRun not timing out successfully

fix #8230
cherry-pick: https://github.com/tektoncd/pipeline/pull/8236
When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[ ] pre-commit Passed
[ ] Follows the commit message standard
[ ] Meets the Tekton contributor standards (including functionality, content, code)
[ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind bug

/ok-to-test


No way to use dynamic_sidebar in the view

Unless I'm missing something, there is currently no way of using WordPress widgets in any view as dynamic_sidebar() cannot be called.
It seems you cannot add it to the get_context inside your functions.php file as dynamic_sidebar() seems to echo rather than return. There is currently no get_dynamic_sidebar either, see here for the WordPress specific ticket.
If get_dynamic_sidebar did exist you could do something like:
// inside functions.php
$data['sidebar_footer'] = get_dynamic_sidebar('footer');

// inside twig view
{% if sidebar_footer %}
<div class="container">
	{{sidebar_footer}}
</div>
{% endif %}

i want to do a similar thing, i need to call a widget in my footer
where do I put this code:
$data['sidebar_footer'] = Timber::get_widgets('footer');

@sb-lc  - you could put that in your twig.php functions file where you initialise timber.  That way it is global to your view files.

I have a footer.php file but oin the standard timber / wp setup this is not used to provide data to the footer.twig file so it can't go there. do you mean a file called twig.php that stores global variables? if so how / where is it included?

Put it in functions.php (add context function).

What about is_active_sidebar? I can't figure out how to get that to work in templates/views.


spelling mistake in the pip install command. The correct name of the library is psycopg2, not pyscopg2.

[Enter feedback here]
Please update the following
https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app
Look for pyscopg2-binary and please correct the following error:
Copy code
pip install pyscopg2
ERROR: Could not find a version that satisfies the requirement pyscopg2 (from versions: none)
ERROR: No matching distribution found for pyscopg2
to
Copy code
pip install psycopg2
If you notice, there is a spelling mistake in the pip install command. The correct name of the library is psycopg2, not pyscopg2.

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

ID: 1a96d5fc-0dd1-a344-5416-44039cee39b8
Version Independent ID: 72844ca4-b087-de15-be00-e0d87020a48b
Content: Tutorial: Deploy a Python Django or Flask web app with PostgreSQL - Azure App Service
Content Source: articles/app-service/tutorial-python-postgresql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

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

@KrishnaDistributedcomputing The PR has been closed once reviewed by author will be be visible, We will close this out but if you feel you need more information please just let us know.


Remove isToken, prefix, token_address

Redundant
Mentioned in

https://github.com/raiden-network/microraiden/issues/134#issuecomment-347144899
https://github.com/raiden-network/microraiden/issues/135

Approved and rebased on top of master (there were some conflicts)


Project Approval Request - Alptium Dentist

@AnisjaMaljm, I have added you to the project https://github.com/alptium/dentist


Upgrade to VS 2017

cref  https://github.com/aspnet/Universe/issues/469

Hi @natemcmaster, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:


Read json data from script tag

Using embedding json in HTML where tgvejs is rendered.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script#embedding_data_in_html

Now we can also read another dom element with some tgve-settings and live happier.


some of my certs won't generate/update

I'm getting this in the log. The server has been running fine for a few years without issue and I'm out of touch with this software so have no idea where to start diagnosing the issue
`Creating/renewal emby.mydomainname.com certificates... (emby.mydomainname.com)
[Wed Dec  2 17:22:22 UTC 2020] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Wed Dec  2 17:22:22 UTC 2020] Single domain='emby.mydomainname.com'
[Wed Dec  2 17:22:22 UTC 2020] Getting domain auth token for each domain
[Wed Dec  2 17:22:25 UTC 2020] Getting webroot for domain='emby.mydomainname.com'
[Wed Dec  2 17:22:25 UTC 2020] Verifying: emby.mydomainname.com
[Wed Dec  2 17:22:29 UTC 2020] emby.mydomainname.com:Verify error:Invalid response from https://emby.mydomainname.com/.well-known/acme-challenge/5TFpMkJZeT1c-mPKXGxL6EY-mxcDFuoDrXuC7rGgsp4 [2606:4700:3035::ac43:d7b2]:
[Wed Dec  2 17:22:29 UTC 2020] Please check log file for more details: /dev/null`

Hi. We've recently released a major update (jrcs/letsencrypt-nginx-proxy-companion:2.0.0) that changed a number of things in a non backward compatible way.
Please check #510 and #719.
Your issue appears to be an authorisation issue, please also check https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/blob/master/docs/Invalid-authorizations.md
Switching from v1 to v2 will cause all certificates to be issued again but that should not be an issue if everything is set up to correctly authorise your domains. I switched a few production servers today from v1 to v2 with no issues.
You can and switch back to the latest v1 tagged release (jrcs/letsencrypt-nginx-proxy-companion:v1.13.1) instead of using latest.

Ok, when I bypassed Cloudflare the cert updated. I'll need to come back to this at the weekend, don't have time now

This is an old comment but it might still be helpful: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/issues/247#issuecomment-329233092

Brilliant, hopefully I'll fix this later. Thanks for your help

Same issue with Cloudflare. Fix in #247 didn't help.
Rolling back to v1.13.1 and all is working again.

@tynor88 when updating to v2 of this image, neither certs nor ACME accounts are migrated. The ACME account hold the fact that you already validated some domains. Because it is not migrated, your domains have to be validated again. My guess is that your domains where validated back when you issued certificates for them with v1 of this project, did not need to be validated again for an extended period of time because you used the same ACME account, but now they don't pass validation anymore on a new ACME account.
While the old ACME accounts of v1 aren't migrated to v2, they're not removed from the Docker volume either so going back to v1 will make it look like the issue is fixed. But I think your domains still won't pass validation if required.

Inactive issue, closing.


MSID: 87572 Version: 2 DOI: 2<IP_ADDRESS>1331

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87572)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87572/v2)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1331)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/87572/v2/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87572)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87572

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87572

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87572/v2/87572-v2.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87572)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Issues to resolve


make an example with cifar-10

Make an example with CIFAR-10 dataset https://www.openml.org/t/167124

Hey, Can I help with this?


PsGithub doesn't handle an error from Github

PsGithub throws com.jcabi.xml.ListWrapper$NodeNotFoundException when the access token doesn't exist in the response from Github see https://github.com/yegor256/netbout/issues/933
I think PsGithub should handles an error from Github properly
https://developer.github.com/v3/oauth/#bad-verification-code

com.jcabi.xml.ListWrapper$NodeNotFoundException: XPath '/OAuth/access_token/text()' not found in '\n\n <..162..#bad-verification-code\n': Index (0) is out of bounds (size=0)
at com.jcabi.xml.ListWrapper.get(ListWrapper.java:153)
at org.takes.facets.auth.social.PsGithub.token(PsGithub.java:156)
at org.takes.facets.auth.social.PsGithub.enter(PsGithub.java:115)

@yegor256 please dispatch this issue

@dmzaytsev I set milestone here to 1.0, let me know if it is wrong

@sebing can you please help? Keep in mind this. If you have any technical questions, don't hesitate to ask right here
30 mins is the budget of the task. This is exactly how much will be paid when the problem is solved (no matter how much time you will actually spend). See this for more information

@davvd I have few questions:

How do I reproduce the issue, as I have no clue what the application is currently doing.(Can you guide me to a document or instruction to use the applicaiton)
2)If it is a bit difficult for me start understanding the application and fix the issue, can I get the full stack trace?

I am not sure where exactly the ListWrapper.get method is called.
PsGithub.java:156 and PsGithub.java:115 are both constructor calls

@dmzaytsev thanks for tis bug, I topped your account for 15 mins, transaction 75689897

@sebing you can find the full stack trace here https://github.com/yegor256/netbout/issues/933
so in case of some error Github returns
{
  "add_scopes": [
    "repo"
  ],
  "note": "admin script"
}

I know this is an json example not xml,  but it doesn't matter
there is no any access_token element, right?
but take a look PsGithub.java#L156
the problem is here
 .xml().xpath("/OAuth/access_token/text()").get(0);

we try to return the first element from the empty list
to reproduce you can create a new unit test for PsGithub like existing one
but the sample of  Github response shouldn't contains  access_token element

@dmzaytsev What is the expected behavior?

access_token should be in the xml all the time?
= if yes, do we have to throw a custom Exception than the generic one? And make sure the xml/json data is created with the access_token

@sebing I guess HttpException should be raised in case of empty #xpath("/OAuth/access_token/text()") @yegor256 what do you think?
see another Github error handling https://github.com/yegor256/takes/blob/e3f1155574929fd02e79a7f0b5f1493984950d13/src/main/java/org/takes/facets/auth/social/PsGithub.java#L110`

@dmzaytsev @davvd So I will split the constructor calling codePsGithub.java#L156, and throw the HttpException?

I feel the naming of org.takes.HttpException is very confusing
What about using org.takes.facets.auth.codecs.DecodingException - the class in  codecs is again confusing.
So should i create another exception in org.takes package

@sebing ask @yegor256
he is the architect on this project

@dmzaytsev  Thanks for the guideline.
@yegor256  Can you help me in this regard?

@yegor256 How do we proceed?

@davvd I made a pull request(https://github.com/yegor256/takes/pull/553)
But the travis-ci job is failing with
`[ERROR] Failed to execute goal com.qulice:qulice-maven-plugin:0.14:check (jcabi-check) on project takes: Failure: 4 Checkstyle violations (see log above) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.qulice:qulice-maven-plugin:0.14:check (jcabi-check) on project takes: Failure`
how do I restart the checkstyle task?

@davvd I made a pull request(https://github.com/yegor256/takes/pull/553)
But the travis-ci job is failing with
`[ERROR] Failed to execute goal com.qulice:qulice-maven-plugin:0.14:check (jcabi-check) on project takes: Failure: 4 Checkstyle violations (see log above) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.qulice:qulice-maven-plugin:0.14:check (jcabi-check) on project takes: Failure`
how do I restart the checkstyle task?

@sebing address your technical questions to the project architect (@yegor256)

@sebing read this please: http://www.yegor256.com/2015/02/16/it-is-not-a-school.html

@davvd Can we close this issue as the merge request (https://github.com/yegor256/takes/pull/553) was accepted?

@davvd Can we close this issue as the merge request (https://github.com/yegor256/takes/pull/553) was accepted?

@sebing you should ask ticket author to close it, see http://www.yegor256.com/2014/11/24/principles-of-bug-tracking.html

@dmzaytsev Can we close this issue as the merge request (https://github.com/yegor256/takes/pull/553) was accepted?

@sebing thanks!

@dmzaytsev Thanks.

@davvd This task is finished and closed.

@davvd This task is finished and closed.

@sebing OK thanks

@ypshenychka please, review this issue for QA compliance, as per par.24

@davvd Quality is good.

@davvd Quality is good.

@ypshenychka many thanks

@sebing I added 10 mins to @ypshenychka (for QA review) in transaction 77185576; Many thanks! 30 mins were added to your account in Transaction ID 56bcddcdadaf56566c000112 (task took 358 hours and 49 mins); +30 to your rating, your total score is +75


grpc UNAVAILABLE status returned when calling grpc-json rpc with invalid Number (Long, Integer, ...)

When using HttpJsonTranscoding with grpc, if we call an rpc with an invalid value for a number, we get a grpc status UNAVAILABLE and no log, which makes the diagnostic very cumbersome.
Exemple:
service MyService {
    rpc TestArmeriaGrpcIntFailure(TestArmeriaGrpcIntFailureRequest) returns (TestArmeriaGrpcIntFailureResponse) {}
}

message TestArmeriaGrpcIntFailureRequest {
    int64 number = 1;
}

message TestArmeriaGrpcIntFailureResponse {

}

Create an armeria server with this proto file, enable HttpJsonTranscoding, and call
curl -XPOST -H 'content-type: application/json; charset=utf-8; protocol=gRPC' http://localhost:8080'/MyService/TestArmeriaGrpcIntFailure' -d '{
  "number": 10.12
}'

We get:
< HTTP/1.1 503 Service Unavailable
< content-type: application/json; charset=utf-8
< grpc-status: 14
< content-length: 37
< server: Armeria/1.26.2
< date: Wed, 10 Jan 2024 15:21:11 GMT
<

{"code":14,"grpc-code":"UNAVAILABLE"}

Note the 10.12, which is a valid json Number, but can't be parsed to a Long.
I've tried to check the source code, and I see that a Long.parseLong is used, and it seems the NumberFormatException raised is catched here:
https://github.com/line/armeria/blob/30c9718d54c29d64ce1169b932618d43e0a37479/grpc/src/main/java/com/linecorp/armeria/server/grpc/HttpJsonTranscodingService.java#L572
still I don't know why it results in a UNAVAILABLE status, but at least it would be nice to be able to log something in such case (or have a custom mapping exception handler).

I think it's the wrong request.
To use HttpJsonTranscoding, the HttpRule must be defined.
import "google/api/annotations.proto";
service MyService {
    rpc TestArmeriaGrpcIntFailure(TestArmeriaGrpcIntFailureRequest) returns (TestArmeriaGrpcIntFailureResponse) {
        option (google.api.http) = {
            get: "/test/armeria" // Add path
        };
    };
}

curl -XPOST -H 'content-type: application/json; charset=utf-8; protocol=gRPC' http://localhost:8080/test/armeria -d '{
"number": 10.12
}'
client (rest call) -> (in server) grpc transcoding -> (in server) gRPC call
gRPC code 14 = The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.
https://grpc.github.io/grpc/core/md_doc_statuscodes.html
I think it would be good to refer to this.
https://github.com/line/armeria/blob/main/grpc/src/test/proto/testing/grpc/transcoding.proto
https://github.com/line/armeria/blob/main/grpc/src/test/java/com/linecorp/armeria/it/grpc/GrpcHttpJsonTranscodingServiceAnnotatedAuthServiceTest.java

My description was probably not clear enough, sorry for that. The option (google.api.http) is not required, we already use the json call successfully as long as the number value can be converted to a Long.
This works:
curl -XPOST -H 'content-type: application/json; charset=utf-8; protocol=gRPC' http://localhost:8080'/MyService/TestArmeriaGrpcIntFailure' -d '{
  "number": 10
}'

This doesn't work:
curl -XPOST -H 'content-type: application/json; charset=utf-8; protocol=gRPC' http://localhost:8080'/MyService/TestArmeriaGrpcIntFailure' -d '{
  "number": 10.12
}'

I'm perfectly fine that it doesn't work, because 10.12 is not a valid int64. The problem is that it fails with nothing in the logs, no option to catch the conversion failure, and a misleading 503 http error code. It took us several hours in a production environment to figure out why we were getting 503 errors, first investigating the servers and networks stability, before noticing that the caller had just added decimals to the number.
Does it make more sense with those additional details?

The invalid input causes InvalidProtocolBufferException which is a subtype of IOException.
IOException is translated into UNAVAILABLE.
https://github.com/line/armeria/blob/7f302505a05d24e7704bcffc43fab6337344cb2c/grpc/src/main/java/com/linecorp/armeria/internal/common/grpc/GrpcStatus.java#L143-L144
You can use GrpcExceptionHandlerFunction as a workaround to convert InvalidProtocolBufferException to a proper gRPC status until we fix it.

Thank you for your investigation and the workaround!

INVALID_ARGUMENT seems a proper return code among other codes(https://grpc.io/docs/guides/status-codes/).
Is it okay to return INVALID_ARGUMENT when InvalidProtocolBufferException is thrown?
Can I try?

InvalidProtocolBufferException: Thrown when a protocol message being parsed is invalid in some way, e.g. it contains a malformed varint or a negative byte length.
INVALID_ARGUMENT: The client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name).

INVALID_ARGUMENT sounds good to me.


follow-ups for truncated axis - warning icon, plot line

This is for follow-up items regarding truncated axis stuffs: see the previous PR and https://github.com/VEuPathDB/web-eda/issues/382. Will also make corresponding PR at web-eda.
I have discussed with Sheena about the appropriateness of new warning icon and she said it looked great.

Also here are additional screenshot for X-axis line (depending on the presence of y-axis range, esp. yMin > 0 or not)

Sorry DK - nearly forgot to post this screenshot - could you take another look at log-scale compatibility please?

Sorry DK - nearly forgot to post this screenshot - could you take another look at log-scale compatibility please?

@bobular thank you for finding the bug. I couldn't find such a bug from my tests before so I will take a look at it 👍

Sorry DK - nearly forgot to post this screenshot - could you take another look at log-scale compatibility please?

@bobular I finally found the reason why it happened. For the dependent axis, I did set a condition for log scale to check whether the value is negative, however, I forgot to consider the case of value = 0 which caused -Infinity in the dependent axis min. Here is the screenshot with the same variable and range control values you have used above


add ability to download file containing all users and the studies they are participating in

As a user, I should be able to click a button and download a file containing all the user IDs and the study IDs representing the studies that they are a part of

associated FE issue: https://github.com/cognitive-neuroscience/axon/issues/69


BUG-105438 - adding NONE ssotype by default to pillar for upgradeability

Do not merge yet, I'm checking for other errors

Checked what I wanted so feel free to merge.


#generator-builder/13 toggle switch field support

Issue : https://github.com/InfyOmLabs/generator-builder/issues/13

1 . https://github.com/InfyOmLabs/generator-builder/pull/27 (GUI)
2. https://github.com/InfyOmLabs/adminlte-templates/pull/37 (Script)


Not able to flash via cargo espflash save-image... && espflash flash ... ("Supplied elf image is not valid")

The following works perfectly:
$ cargo espflash flash --release --monitor

But to save the app image and then flash it in a separate step fails:
$ cargo espflash save-image --release --chip esp32c3 firmware.bin
...
Chip type:         esp32c3
Merge:             false
Skip padding:      false
App/part. size:    250,720/4,128,768 bytes, 6.07%

$ espflash flash --partition-table partitions.csv firmware.bin
...
Error: espflash::invalid_elf

  × Supplied elf image is not valid
  ╰─▶ Did not find ELF magic number
  help: Try running `cargo clean` and rebuilding the image

I have a friend with an ESP32C3 based device that I built for them, and I want them to be able to flash an upgraded firmware image to the thing. But they don't have Rust or any type of development setup. I was hoping to be able to just give them the app image and instruct them how to download the espflash  binary here from github and get it on the thing. But this fails and I'm not sure what I'm doing wrong.

I have also tried save-image in combination with write-bin, also without success, but a different error:
$ cargo espflash save-image --release --merge --chip esp32c3 firmware.bin
...

$ espflash write-bin 123 firmware.bin --port /dev/ttyACM0
[2023-03-08T19:09:07Z INFO ] Serial port: '/dev/ttyACM0'
[2023-03-08T19:09:07Z INFO ] Connecting...
[2023-03-08T19:09:07Z INFO ] Using flash stub
[2023-03-08T19:09:07Z INFO ] Serial port: '/dev/ttyACM0'
[2023-03-08T19:09:07Z INFO ] Connecting...
Error: espflash::serial_error

  × Failed to open serial port /dev/ttyACM0
  ├─▶ Failed to open serial port /dev/ttyACM0
  ├─▶ Error while connecting to device
  ├─▶ IO error while using serial port: Device or resource busy
  ╰─▶ Device or resource busy

But the very same device is not at all busy when flashing directly with cargo espflash flash ..., so :shrug:

Waaaait a minute. This was simpler than I thought:
$ cargo build --release
$ espflash flash ~/.cargo/target/riscv32imc-esp-espidf/release/my-firmware-lol

Tada! :partying_face:
I had assumed save-image would output the correct format. Since that was what I had to use when OTA-flashing my other devices, as I figured out when writing esp-ota.


Request to add license

I would like to use your docker images but the repository doesn't seem to have any license. Please consider adding a license
Thank you!

Thanks for opening the issue. I don’t believe there is much to license, but I understand that it would help to add one.
Would MIT work?
Just to avoid confusion the images contain various software artifacts that are covered by their own license of course.


Folded properties / properties that cannot be opened on 3D nodes

Godot version
v4.1.2.stable.official [399c9dc39]
System information
Windows 11 -  Forward+ - 3D Nodes
Issue description
I am experiencing a problem with the properties in the inspector of every 3D-Node. The properties are 'unfolded' and I cannot access them. (see first picture)
This problem affects EVERY project that I have. I cannot modify any 3D properties in the inspector.
The problem does not occur with Control and 2D-Nodes, or with World Environment. (see second picture)
Edit: I have attempted to reinstall Godot and use a previous version (4.1.1), but the issue persists. I am not sure what is causing this bug or how to resolve it.

Steps to reproduce
-I just added the pistol model, that is a standard .blend file
-So the editor reloaded to recognise it.
-And when dragging it into the scene the bug appeared. / maybe it appeared when reloading I can't really tell that
Minimal reproduction project
unfolded_3D_properties.zip
I am not sure whether the bug is related to the project or not, but I have attached a sample project that contains the pistol model for your reference.
However, the bug affects every 3D project, so I suspect that there is a more serious issue than just the model itself.

Answer: Problem: I had enabled only the 2D nodes and control nodes in my editor features.
This might be confusing for some users, as the 3D nodes are not visible at all. To fix this issue, follow these steps:

Go to Editor -> Manage Editor Features...
Choose a profile that supports 3D nodes from the available profiles list.


[AIP-191] Check csharp_namespace for idiomaticity.

This will need a slight change after #370 goes in. Fine to approve both (tests will just start failing after it is merged).


Workaround djl-serving flaky test on Windows

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #842 (fda412f) into master (59b3976) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #842      +/-   ##
============================================
+ Coverage     70.29%   70.33%   +0.03%
- Complexity     4973     4980       +7
============================================
  Files           491      491
  Lines         22020    22020
  Branches       2291     2291
============================================
+ Hits          15480    15487       +7
- Misses         5322     5328       +6
+ Partials       1218     1205      -13

Impacted Files
Coverage Δ
Complexity Δ

...gine/src/main/java/ai/djl/dlr/engine/DlrModel.java
53.12% <0.00%> (-3.13%)
4.00% <0.00%> (ø%)

api/src/main/java/ai/djl/util/Platform.java
46.51% <0.00%> (-2.33%)
8.00% <0.00%> (ø%)

...g/src/main/java/ai/djl/serving/util/Connector.java
55.40% <0.00%> (-1.36%)
21.00% <0.00%> (ø%)

...ngine/src/main/java/ai/djl/mxnet/jna/LibUtils.java
44.73% <0.00%> (-1.32%)
15.00% <0.00%> (ø%)

...ne/src/main/java/ai/djl/mxnet/jna/StringArray.java
92.85% <0.00%> (ø)
9.00% <0.00%> (-1.00%)

...rc/main/java/ai/djl/paddlepaddle/jni/LibUtils.java
51.14% <0.00%> (ø)
14.00% <0.00%> (ø%)

api/src/main/java/ai/djl/inference/Predictor.java
90.38% <0.00%> (+2.88%)
24.00% <0.00%> (+1.00%)

api/src/main/java/ai/djl/training/Trainer.java
94.89% <0.00%> (+3.06%)
34.00% <0.00%> (+1.00%)

...djl/training/listener/LoggingTrainingListener.java
88.49% <0.00%> (+5.30%)
28.00% <0.00%> (+6.00%)

Continue to review full report at Codecov.

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


Adding more precise dbsize

And some refactoring

https://github.com/matthiaz/platformsh-cli/pull/1

It seems the column ALLOCATED_SIZE doesn't exist in information_schema.innodb_sys_tablespaces for older MariaDB versions (works in 10.2, doesn't work in 10.0). We need to test for the existence of that column.

It seems the column ALLOCATED_SIZE doesn't exist in information_schema.innodb_sys_tablespaces for older MariaDB versions (works in 10.2, doesn't work in 10.0). We need to test for the existence of that column.

I fixed that.

I also expanded on the 'cleanup' option
so you can do something like platform db:size -p 3oupdxcaenytw -e master -r database1 --cleanup
InnoDB does not automatically clean up deleted data, but running an ALTER TABLE Engine forces it to be recreated.
--cleanup won't do this without first asking confirmation from the user.


what is the point in putting keywords when you already put the link

Is there an existing issue for this?

[x] I have searched the existing issues

I'm submitting a ...

[ ] bug report
[X] feature request
[ ] support request --> Contact me over mail for support https://github.com/MShawon

Description
make keywords an option
Environment
- OS : windows 11
- Python : 3.10
- Script version : latest

config.json
this is not the cause

To avoid bot detection
To get views from YouTube search
To rank the video for those keywords on YouTube
Later when real user search those keywords your video comes into top results you get organic views

It won't be an optional but you can empty the search.txt without deleting the search.txt if needed
Use python 3.8 or 3.9 for this script

@MShawon
noice
btw when you empty search.txt it says no keywords


fix flash kernel on sm 70

flash attention triton kernel on sm 70 bug fixing
profile throughput bug fixing

chat failed on v100
double enter to end input >>> hi, what's your name

<|im_start|>system
You are an AI assistant whose name is InternLM (书生·浦语).
- InternLM (书生·浦语) is a conversational language model that is developed by Shanghai AI Laboratory (上海人工智能实验室). It is designed to be helpful, honest, and harmless.
- InternLM (书生·浦语) can understand and communicate fluently in the language chosen by the user such as English and 中文.
<|im_end|>
<|im_start|>user
hi, what's your name<|im_end|>
<|im_start|>assistant
 S1 real

double enter to end input >>> yes?

I used internlm2-chat-7b, which is fp16

Done


License view

Some NFTs might contain content that is under a lisence. Haveing a view to show this and some premade builders to create lisences for popular lisences would be a great adition.

Maybe just use https://spdx.org/licenses/


Script Error: Lookup.Administration and RemoteData

I've looked through recent tickets and haven't found one that supports my issue. When I go to New User and then to assign roles, I'm met with a script error and the pop up for the Roles and the Permissions does not appear. Any insight?

Make sure you have correct permitions, also make sure the LookupScript is correct.

I’m trying to get to the permissions section. That’s the problem. Trying to
loads the permissions dialog doesn’t work, and I’ll verify the LookupScript
is correct. I’m also running it in ASP.NET Core.
On Fri, Dec 22, 2017 at 14:27 brunobola<EMAIL_ADDRESS>wrote:

Make sure you have correct permitions, also make sure the LookupScript is
correct.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/volkanceylan/Serenity/issues/3086#issuecomment-353660973,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK6u3cSut3w8r7vUH-MJgwmS0VsnLtLVks5tDAKGgaJpZM4RKrx5
.

In PermissionCheckEditor.ts there is function
private getSortedGroupAndPermissionKeys(titleByKey: Q.Dictionary): string[] {
let keys = <string[]>Q.getRemoteData('Administration.PermissionKeys').Entities;
let titleWithGroup = {};
for (var k of keys) {
let s = k;
            if (!s) {
                continue;
            }

            if (s.charAt(s.length - 1) == ':') {
                s = s.substr(0, s.length - 1);
                if (s.length === 0) {
                    continue;
                }
            }

            if (titleByKey[s]) {
                continue;
            }

            titleByKey[s] = Q.coalesce(Q.tryGetText('Permission.' + s), s);
            let parts = s.split(':');
            let group = '';
            let groupTitle = '';
            for (let i = 0; i < parts.length - 1; i++) {
                group = group + parts[i] + ':';
                let txt = Q.tryGetText('Permission.' + group);
                if (txt == null) {
                    txt = parts[i];
                }
                titleByKey[group] = txt;
                groupTitle = groupTitle + titleByKey[group] + ':';
                titleWithGroup[group] = groupTitle;
            }

            titleWithGroup[s] = groupTitle + titleByKey[s];
        }

        keys = Object.keys(titleByKey);
        keys = keys.sort((x, y) => Q.turkishLocaleCompare(titleWithGroup[x], titleWithGroup[y]));

        return keys;
    }

which is calling ListPermissionKeys() in UserPermissionEndpoint.cs
[DataScript("Administration.PermissionKeys")]
public ListResponse ListPermissionKeys()
{
return new MyRepository().ListPermissionKeys();
}
which get the PermissionKeys in UserPermissionRepository.cs
public ListResponse ListPermissionKeys()
{
return LocalCache.Get("Administration:PermissionKeys", TimeSpan.Zero, () =>
{
var result = new HashSet(StringComparer.OrdinalIgnoreCase);
            result.AddRange(NestedPermissionKeyRegistration.AddNestedPermissions(registry: null));

            foreach (var assembly in ExtensibilityHelper.SelfAssemblies)
            {
                foreach (var attr in assembly.GetCustomAttributes<PermissionAttributeBase>())
                    if (!attr.Permission.IsEmptyOrNull())
                        result.AddRange(SplitPermissions(attr.Permission));

                foreach (var type in assembly.GetTypes())
                {
                    ProcessAttributes<PageAuthorizeAttribute>(result, type, x => x.Permission);
                    ProcessAttributes<PermissionAttributeBase>(result, type, x => x.Permission);
                    ProcessAttributes<ServiceAuthorizeAttribute>(result, type, x => x.Permission);

                    foreach (var member in type.GetMethods(BindingFlags.Instance | BindingFlags.Public))
                    {
                        ProcessAttributes<PageAuthorizeAttribute>(result, member, x => x.Permission);
                        ProcessAttributes<PermissionAttributeBase>(result, member, x => x.Permission);
                        ProcessAttributes<ServiceAuthorizeAttribute>(result, member, x => x.Permission);
                    }

                    foreach (var member in type.GetProperties(BindingFlags.Instance | BindingFlags.Public))
                        if (member.GetIndexParameters().Length == 0)
                            ProcessAttributes<PermissionAttributeBase>(result, member, x => x.Permission);
                }
            }
            if (Authorization.Username != "admin")
            {
                result.Remove(Administration.PermissionKeys.RoleSecurity);
                result.Remove(Administration.PermissionKeys.PermissionSecurity);
                result.Remove(Administration.PermissionKeys.Translation);
                result.Remove(Administration.PermissionKeys.ErrorLogSecurity);
            }
            result.Remove(Administration.PermissionKeys.Offices);
            result.Remove("*");
            result.Remove("?");

            return new ListResponse<string>
            {
                Entities = new List<string>(result)
            };
        });
    }

i hope this will help to find the issue

issue can be here
[DataScript("Administration.PermissionKeys")]
let keys = <string[]>Q.getRemoteData('Administration.PermissionKeys').Entities;


Missing autocomplete for hashmap

Typescript Version: 2.1.5
VSCode Version: 1.8.1
OS Version: Mac OS Sierra 10.12.2

Steps to Reproduce:

var list: { [key: string]: string }; = {}
Writing list. leads to no autocomplete suggestions

Okay, I expected that the hashmap has any methods but it seems I got it wrong.


Add ability to produce non-salmon harvest estimates

[x] Keep whitefish/sheefish columns in prepare_interviews_one()
[x] Include calculation in estimate_catch_per_trip()
[x] Include calculation in estimate_harvest()
[x] Include option to accept this species (potentially plural) in report()
[ ] Create a table that can summarize non-salmon harvest for placement in the appendix
[ ] Create option to produce whitefish harvest estimates in report_tool() and build_rmd()

I may be missing a necessary change here...

The documents can now report nonsalmon harvest. Here is code for a non-salmon appendix:
\clearpage
\setcounter{figure}{0}
\setcounter{table}{0}
\renewcommand\thefigure{B\arabic{figure}}
\renewcommand\thetable{B\arabic{table}}

# Appendix: Non-salmon Harvest Information {-}

```{r estimate-harvest-nonsalmon}
# estimate (via bootstrap) drift net harvest for all species and and strata
boot_out_drift = bootstrap_harvest(interview_data, drift_effort_info,
                                   gear = "drift", n_boot = n_boot, stratify_interviews = TRUE, nonsalmon = TRUE)

# estimate (via bootstrap) set net harvest for all species and and strata
boot_out_set = bootstrap_harvest(interview_data, set_effort_info,
                                 gear = "set", n_boot = n_boot, stratify_interviews = FALSE, nonsalmon = TRUE)

# sum up across gears
boot_out_total = data.frame(iter = boot_out_drift$iter,
                            date = boot_out_drift$date,
                            gear = "total",
                            stratum = boot_out_drift$stratum,
                            sheefish = rowSums(cbind(boot_out_drift[,"sheefish"], boot_out_set[,"sheefish"]), na.rm = TRUE),
                            whitefish = rowSums(cbind(boot_out_drift[,"whitefish"], boot_out_set[,"whitefish"]), na.rm = TRUE),
                            total = rowSums(cbind(boot_out_drift[,"total"], boot_out_set[,"total"]), na.rm = TRUE)
)

# combine drift, set, and total into one data frame of bootstrap output
boot_out <<- rbind(boot_out_total, boot_out_drift, boot_out_set)
```

```{r set-summaries-nonsalmon}
set_harvest = sapply(c("sheefish", "whitefish", "total"), function(sp) report(sp, gear = "set", CI = FALSE, return_numeric = TRUE))
set_spp = KuskoHarvEst:::percentize(set_harvest[c("sheefish", "whitefish")]/set_harvest["total"])
```

* An estimated total of **`r report()`** non-salmon (sheefish and whitefishes) were harvested.
  * An estimated total of **`r report(spp = "sheefish")`** sheefish were harvested.
  * An estimated total of **`r report(spp = "whitefish")`** whitefishes were harvested.
* Harvest by set nets accounted for an estimated **`r report(gear = "set")`** total non-salmon fishes (`r paste0(set_spp["sheefish"], " sheefish and ", set_spp["whitefish"], " whitefishes")`).

```{r}
make_strata_summary_table(interview_data, "drift", nonsalmon = TRUE)
```

```{r}
make_appendix_table(interview_data, "drift", "sheefish")
```

```{r}
make_appendix_table(interview_data, "drift", "whitefish")
```

I'm waiting to produce Rmd script files and interface components for this until I receive feedback from the group.

Closed by #160.


Use Floyd's cycle-finding algorithm for list? function

This changes list? and BiwaScheme.isList to use Floyd's cycle-finding algorithm instead of the previous O(n^2) time, O(n) space naïve algorithm.

Superseded by #43


TraceRequestHttpHeadersFilter overrides all request headers in Spring Cloud Gateway

Oops, I'm not sure it is a bug or question.
I'm trying to integrate Spring Cloud Gateway and Spring Cloud Sleuth. In Spring Boot 2.1.2 and Spring Cloud Greenwich.RELEASE.
I found any of my request Header 'X-Forward-*'  is missing.
After reading the source code, I found a HeaderFilters in the NettyRoutingFIlter and the TraceRequestHttpHeadersFilter was injected.
But TraceRequestHttpHeadersFilter is so strange. Why is its implementation covered instead of append?
class TraceRequestHttpHeadersFilter extends AbstractHttpHeadersFilter {
    private static final Log log = LogFactory.getLog(TraceRequestHttpHeadersFilter.class);

    static HttpHeadersFilter create(HttpTracing httpTracing) {
        return new TraceRequestHttpHeadersFilter(httpTracing);
    }

    private TraceRequestHttpHeadersFilter(HttpTracing httpTracing) {
        super(httpTracing);
    }

    public HttpHeaders filter(HttpHeaders input, ServerWebExchange exchange) {
        if (log.isDebugEnabled()) {
            log.debug("Will instrument the HTTP request headers");
        }

        Builder builder = exchange.getRequest().mutate();
        Span span = this.handler.handleSend(this.injector, builder);
        if (log.isDebugEnabled()) {
            log.debug("Client span  " + span + " created for the request. New headers are " + builder.build().getHeaders().toSingleValueMap());
        }

        exchange.getAttributes().put(SPAN_ATTRIBUTE, span);
        return new HttpHeaders(builder.build().getHeaders());
    }

    public boolean supports(Type type) {
        return type.equals(Type.REQUEST);
    }
}

ps: Forgive my English, I am still trying to learn it.

@marcingrzejszczak any tips on when we can expect 2.1.1 to be released with this bug fix included? (currently blocking our prod release :( )

This change introduced a new bug. If I have multiple headers with the same name, it discards everything and preserves only the first header.
That happens exactly because of this change:
https://github.com/spring-cloud/spring-cloud-sleuth/commit/1775ec1000d638a61dfcb852a54a8bdf2159ed18#diff-80efc26f63f80d00df56ec6edd649968R59

Can you provide more information or a test case that replicates the issue?

Oh you actually did https://github.com/spring-cloud/spring-cloud-sleuth/issues/1352


Actor for Pregel with tests

Scope & Purpose
Small step towards making tests run.

Well, this PR seems to have escalated a little bit.
For context, I had some quite clear (and fairly simple) goals with the code I wrote (rather am writing) in this PR;

Have a type that I can send messages to that will be executed in a sequential way. It was first called MessagableT, and its now called Actor
Not use mutexes/locks, as I did not want to get stuck in the ArangoDB scheduler detail hell.
Have tests that compile and execute in <1 minute from a fresh checkout, and ideally on github.
It be transparent enough that someone can understand the details of the code, but not need to understand all the details of ArangoDB.
Make all that somehow usable in the context of our Pregel code.

Following a suggestion by @mpoeter, I implemented the MPSC queue that is in this PR, and I intend to stay with that queue right now. It is a good learning and teaching experience.
I don't want to assume anything about what the ArangoDB scheduler does. The only thing I want to do is be able to say "schedule this thing, please" to make the Actor go.
Note also, that this PR goes into staging/pregel-refactor, not into devel


Core: Added all well known http status codes

I decided to add all well knowned http status code to Core. The main reason for that is to do not use magic numbers and magic strings and having everything under well defined constants.
Status codes are basing on ints, so they are a good fit for the current code base.
This change also introduces HttpStatusLine for simplifying HttpResponse calls with status codes. In the future HttpResponse function will need to be replaced. One of the reason to do it is that it will be almost impossible to implement HTTP 2.0 protocol (Break api changes required).
The implementation is similar to http implementation in GoLang (https://go.dev/src/net/http/status.go).

Not really sure whether this is useful or obsfuscation, but I guess a list of http status codes does not really hurt, even if in most cases they are not used in its original meanings anyway - I mean, we seldom do 'real' website https, but we do a lot of API http, rest-like or otherwise, and there these codes are pretty arbitrary and almost always not used in original meaning, phrases have to be different as well to better explain the problem (and that is true even if U++ code is just using 3rd party API).
What I think is pretty ugly overengineering is HttpStatusLine class. I would just add another overload of HttpResponse without phrase parameter and supply phrase by HttpStatus::ToString. Much less redundant...

Another comment: This should be reimplemented using HttpStatusCode.i file with
CODE(OK, "OK")
and then include this twice to get enum and ToString. Less source code and much easier to maintain.

Hello Mirek,
Thanks for review! I did as you suggested.
Regards,
Klugier


Show scrollbar when necessary

Firefox on Windows will unconditionally show scrollbars when you specify overflow: scroll. This is bad behavior, as you don't always need the scrollbar. Changing the scroll value to auto fixes this issue and only shows the scrollbar when necessary.
Resolves #20139

LGTM


AttributeError: version cannot be changed directly, use async_update_entry instead

This is what I am getting after upgrade and not sure what to do
Logger: homeassistant.config_entries
Source: config_entries.py:933
First occurred: 9:26:37 AM (1 occurrences)
Last logged: 9:26:37 AM
Error migrating entry AI Automation Suggester for ai_automation_suggester
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 933, in async_migrate
result = await component.async_migrate_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ai_automation_suggester/init.py", line 41, in async_migrate_entry
config_entry.version = 1.08
^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 443, in setattr
raise AttributeError(
AttributeError: version cannot be changed directly, use async_update_entry instead

This appears to be an update issue because of the major changes in the additional providers. Please try the below and report back.
Recommendation is:
If you experience major failures during the upgrade:
Remove all configured AI providers from the integration
Uninstall the integration completely
Restart Home Assistant
Reinstall the integration
Reconfigure your AI providers
This clean installation approach will ensure a fresh start if the migration process encounters any critical issues.

That worked
Thanks
Ian Robson

From: Graham Hosking @.>
Sent: Monday, November 4, 2024 11:00 AM
To: ITSpecialist111/ai_automation_suggester @.>
Cc: Ian K. Robson @.>; Author @.>
Subject: Re: [ITSpecialist111/ai_automation_suggester] AttributeError: version cannot be changed directly, use async_update_entry instead (Issue #28)
This appears to be an update issue because of the major changes in the additional providers. Please try the below and report back.
Recommendation is:
If you experience major failures during the upgrade:
Remove all configured AI providers from the integration
Uninstall the integration completely
Restart Home Assistant
Reinstall the integration
Reconfigure your AI providers
This clean installation approach will ensure a fresh start if the migration process encounters any critical issues.
—
Reply to this email directly, view it on GitHubhttps://github.com/ITSpecialist111/ai_automation_suggester/issues/28#issuecomment-2455093876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUETU5ZBLQRPMTXOLKMKGL3Z66KYTAVCNFSM6AAAAABREP2QJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGA4TGOBXGY.
You are receiving this because you authored the thread.Message ID: @.***>
This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet.

Thank you for your patience with this process. We hope we have resolved the update path from this version. We appreciate your support as an early adopter of this integration.

No worries if there is anything we can do to help let us know.  The integration has great possibilities for us all.
Ian Robson
Bytelink LLC.

From: Graham Hosking @.>
Sent: Monday, November 4, 2024 11:44 AM
To: ITSpecialist111/ai_automation_suggester @.>
Cc: Ian K. Robson @.>; Author @.>
Subject: Re: [ITSpecialist111/ai_automation_suggester] AttributeError: version cannot be changed directly, use async_update_entry instead (Issue #28)
Thank you for your patience with this process. We hope we have resolved the update path from this version. We appreciate your support as an early adopter of this integration.
—
Reply to this email directly, view it on GitHubhttps://github.com/ITSpecialist111/ai_automation_suggester/issues/28#issuecomment-2455199578, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUETU5ZFYKZTQZI3KSH6T7DZ66P5PAVCNFSM6AAAAABREP2QJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJVGE4TSNJXHA.
You are receiving this because you authored the thread.Message ID: @.***>
This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet.

I've tried removing completely and re-adding and I'm unable as follows:
After removing the repository, restarting core, reading the repo, restarting core, downloading v1.1.0, restarting core - and trying to add the integration I'm presented with the following error in the UI
*Error Config flow could not be loaded: {"message":"Invalid handler specified"}
System Logs show the following:
2024-11-05 10:05:35.806 ERROR (ImportExecutor_0) [homeassistant.loader] Unexpected exception importing platform custom_components.ai_automation_suggester.config_flow
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1264, in _load_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1296, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/init.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 991, in exec_module
File "", line 1129, in get_code
File "", line 1059, in source_to_code
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/ai_automation_suggester/config_flow.py", line 259
VERSION = 1.1.0
^^
SyntaxError: invalid syntax
2024-11-05 10:05:35.810 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.ai_automation_suggester.config_flow',) inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 179: return await super()._post_impl(request, data) (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1296: return importlib.import_module(f"{self.pkg_path}.{platform_name}")), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A"integration%3A+config"
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
return await handler(request)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
return await func(self, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
return await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
return await self._post_impl(request, data)
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
return await super()._post_impl(request, data)
2024-11-05 10:05:35.813 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.ai_automation_suggester.config_flow
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 1264, in _load_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1296, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/init.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 991, in exec_module
File "", line 1129, in get_code
File "", line 1059, in source_to_code
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/ai_automation_suggester/config_flow.py", line 259
VERSION = 1.1.0
^^
SyntaxError: invalid syntax
2024-11-05 10:05:35.814 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration ai_automation_suggester: Exception importing custom_components.ai_automation_suggester.config_flow

Thanks for the update. The issue was me (not enough coffee this morning) with the versioning format. This is fixed please redownload

Nope, am getting the exact same after destroying the repository, re-adding, redownloading, etc.
Should I be trying to install v1.0.9 not 1.1.0?

Try 1.1.1 with the actual fix - I've published now

Hrm, that seems to have gotten it beyond the issue I was having this AM. I can now install the integration, but I am now getting a 522 Error back from CloudFlare when trying to configure with OpenAI.   This could be an issue on my end or theirs.  I'll have to mess with a bit later this afternoon.  I'll report back either way.
Cheers

The AI suggester integration doesn't touch CloudFlare. I'm also using CloudFlare as well - Might be worth performing a Full System Restart just to flush everything.

Unfortunately, I'm in adult mode today and have conf calls for the next several hours. But my thinking is that OpenAI are using CF, hence my logs from attempting to connect via API.

2024-11-05 10:54:17.356 ERROR (MainThread) [custom_components.ai_automation_suggester.config_flow] OpenAI validation error response:

api.openai.com | 522: Connection timed out
<<>>

Huzzah, I just hit the button again - I think I was getting ratelimited on the OpenAI side.
A clean reinstall to 1.1.1 seems to have fixed whatever prior issues I was running into.


Embed as wireframe ?

Is it possible ? It's more easier to people to interact with playground right on their website/article rather than redirect to playground website.

Definitely. It can be done. Would you like to attempt it?

Tried to embed with Medium but seems no luck T_T I'll try with simpler approach. But I think we should support medium :P

So perhaps we need to create a page which has a different layout that is easier to embed?

Awesome. :D Thank you!! 💯


glossy case-sensitive alphabetical order

Really enjoying glossy, thanks for this. Noticed that generated glossaries are sorted case-sensitive, i.e. all terms beginning with upper case before all terms beginning with lower case. Is there a way to have case-insensitive sorting?

Glad you like it.
I'll look into adding this as an option in the next few days.

Ok thanks for the suggestion. I added a parameter to #glossary() so you can do #glossary(ignore-case: true).
Should be live once this PR merges: https://github.com/typst/packages/pull/1392
Please reopen if, once it's merged, it doesn't work for you.


backend error notifications

Issue: #73
Revised PR #87

Axios really doesn't provide much info on errors. No status codes or anything for this type of request. I added the request method and the endpoint, but I can add other things if you have some ideas


add small extension to get the edit on github button working

@santisoler: if you have a couple of minutes, I would appreciate your thoughts on this. I suspect there is a simpler way to do this. I copied what we were doing from the gpg to get it working.
Also, this is a "good enough" for now fix. Ideally we will move this content over to myst md in the near future, so there isn't a big motivation to invest a lot in cleaning up sphinx.
edit I will get the tests passing first! (hopefully with #576)

I merged #577, so I think we can safely close this PR.


Implement an admin test page that allows distribution of cards for testing/debugging

Do all work for this task in a branch called issue-79
Add a test page accessible by admin accounts that allows for testing features during development:

Distribute cards to user accounts
-- Add a dropdown of all cards in the database
-- Add a field/dropdown that lets you select a user account to give the selected card to

Added preliminary implementation of page
To-do:

For populating the dropdown list of cards, change the target variable to the public collection of cards
Fix user look-up failing
Revisit how user's cards are updated after My Cards page and functionality is updated

Fixed user lookup
Added publication of registered usernames and displayed them on the DevTest page

DevTest now pulls card information from the ProfCard publication

Created page that allows testing feature implementations.
Started prototyping functionality behind gifting and trading cards. Due to scope of these tasks going beyond original task, closing this issue as completed and moving work to new task.


Chat workspace on right of visual code

I was wondering if there's any possibility of adjusting the position of chat AI window over towards the right handside similar like cursor.sh

fixed this issue

drag and move to secondary side bar


MS Fabric with Azure Service Bus

I am able to process azure service bus messages through MS Fabric notebook. I would like to clarify below points -

Is there any cost involve if it's just waiting for the new messages. I know the Spark Custer will be running.
What would be tentative cost?

@chamolag
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

@SaibabaBalapur-MSFT
I don't have the documentation link. However, I can provide you the piece of code I am using to read service bus messages.
#########################################################################
pip install azure-servicebus
from azure.servicebus import ServiceBusClient, ServiceBusMessage
try:
servicebus_client = ServiceBusClient.from_connection_string(connection_str)
receiver_queue = "onelakeprocess"
sender_queue = "onelakeprocessed"
receiver = servicebus_client.get_queue_receiver(queue_name=receiver_queue)
sender = servicebus_client.get_queue_sender(queue_name=sender_queue)
with receiver:
for received_message in receiver:
response = process_message(received_message)
message = ServiceBusMessage(response)
sender.send_messages(message)
receiver.complete_message(received_message)
except Exception as e:
print("error:", e)
finally:
servicebus_client.close()
sender.close()
#########################################################################
This is something important for us to design the architecture of application based on your inputs.
We would like to know whether MS Fabric- spark cluster will incur any cost if it's waiting for new messages (service bus).

@chamolag
Please Note, GitHub forum is dedicated for Microsoft documentation related issues. So kindly share Microsoft document link which you are following for these steps.

@SaibabaBalapur-MSFT
Thanks for your response. Kindly note this ticket is not about any issue. I just want to inquire about the pricing aspect of service bus type implementation with MS Fabric.
Please refer the other ticket which I raised few weeks back for further details.
https://github.com/MicrosoftDocs/azure-docs/issues/115092

@chamolag
Since this issue isn't directly related to improving our docs, and to gain a better understanding of you can inquire about the pricing issue, I'd recommend working you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows.
Microsoft Teams Community forum


Add labels to all commands

I've made GPREFIX a separate variable for adding a prefix to the name rather than repurposing GUSER.


libusb1: Build everywhere, since MinGW works, for 18.09

Motivation for this change
Backport of #47143
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Success on x86_64-darwin (full log)
Attempted: libusb1
Partial log (click to expand)
/nix/store/h75d19dp50rcr165xa0zya04ay39i711-libusb-1.0.22

Success on x86_64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
these paths will be fetched (0.39 MiB download, 1.59 MiB unpacked):
  /nix/store/gaf83n7ig64i72fr8kxl8lcaw5ij4j2p-libusb-1.0.22
  /nix/store/x4pbhf21ps4lazmbjjaldx4vip9jbkfs-systemd-239-lib
copying path '/nix/store/x4pbhf21ps4lazmbjjaldx4vip9jbkfs-systemd-239-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/gaf83n7ig64i72fr8kxl8lcaw5ij4j2p-libusb-1.0.22' from 'https://cache.nixos.org'...
/nix/store/gaf83n7ig64i72fr8kxl8lcaw5ij4j2p-libusb-1.0.22

Success on aarch64-linux (full log)
Attempted: libusb1
Partial log (click to expand)
  /nix/store/szngijpsf3hcnyn87fg4xrx2zvn0xk2q-libgpg-error-1.28
  /nix/store/vw1y121r5mqv1a3ccnx8hv7gh4vxc0p5-libgcrypt-1.8.3
copying path '/nix/store/2glwg8aamgz98gzj7cx0m54la078hvcb-libcap-2.25-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/3yap906kk4v4p79v406zdi5mli1slj0g-lz4-1.8.2' from 'https://cache.nixos.org'...
copying path '/nix/store/8iy0xs1s4s4g3s5hgc7vj1f47djpmzpa-util-linux-2.32.1' from 'https://cache.nixos.org'...
copying path '/nix/store/szngijpsf3hcnyn87fg4xrx2zvn0xk2q-libgpg-error-1.28' from 'https://cache.nixos.org'...
copying path '/nix/store/vw1y121r5mqv1a3ccnx8hv7gh4vxc0p5-libgcrypt-1.8.3' from 'https://cache.nixos.org'...
copying path '/nix/store/c2n0xkdgy2sff955jirbr2zcshd99rhs-systemd-239-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/2a627gccggykbypmnl3kmwqwgz8d9b8p-libusb-1.0.22' from 'https://cache.nixos.org'...
/nix/store/2a627gccggykbypmnl3kmwqwgz8d9b8p-libusb-1.0.22


Failing to create ca.pem key and node*.pem key

Is this a BUG REPORT or FEATURE REQUEST? (choose one):BUG RE
PORT

Environment:

**Cloud provider or hardware configuration:**Oracle Virtual Box

**OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"): Rhel-7 3.10.0-862.11.6.e17.x86_64

Version of Ansible (ansible --version):<IP_ADDRESS>

**Kubespray version (commit) (git rev-parse --short HEAD):**7bf0994
Network plugin used:flannel
Copy of your inventory file:
[all]
node1 	 ansible_host=localhost ip=localhost ansible_connection=local
node2 	 ansible_host=ip_here ip=ip_here ansible_user=root
node3 	 ansible_host=ip_here ip=ip_here ansible_user=root
[kube-master]
node1
node2
[kube-node]
node2
node3
[etcd]
node1
node2
node3
[k8s-cluster:children]
kube-master
kube-node
[calico-rr]
[vault]
node1
node2
node3
Command used to invoke ansible: ansible-playbook -i hosts.ini cluster.yml --extra-vars "kube_network_plugin=flannel"
Output of ansible run:

Anything else do we need to know:

@rahulmuddagouni I guess maybe your inventory is wrong regarding the definition of node1.
Even if node1 is your control machine, its ansible_host and ip variables should be defined the same way as node2 and node3.

Thanks@mirwan it's working for me.


Document risks and sideeffects of pg upgrades more clearly

What should we add to our content collections?
Re https://github.com/aiven/devportal/blob/main/docs/products/postgresql/howto/upgrade.rst
We "recommend" that ppl test an upgrade on a fork and also "verify the impact": there are two benefits from it: a) ensuring that it succeeds and is performed quickly enough (which might not be the case) and b) to test query performance directly after upgrade under real world load (when no statistics are available and caches are cold). Basically if you cannot survive any surprises during/after a pg upgrade, then such a fork + upgrade + immediate test under real world load (before AUTOVACUUM does the analyse!) should happen. See the next two items which show possible problems/errors:

pg_upgrade usually takes a few seconds, but can take minutes or even hours in some pathological cases (e.g. involving lot's of databases or lot's "large objects". This can potentially also lead to OOM kills if the schema is so large and the plan is too small for it to let the pg_dump/pg_restore phase of pg_upgrade --link succeed. Also some schema changes in PGs default catalog or used extensions in combination with customer objects depending on it could mean that we would not be able to finish the upgrade at all (e.g. if the customer adds a SELECT * view +  function on top of pg_catalog.pg_stat_activity which added an additional field in newer versions -> * returns all columns, but function return value has columns hardcoded).
We do not transfer optimizer statistics and not running the recommended VACUUM would result in a lot of cases (my guess) in very bad query performance. So running ANALYZE ensures that queries run efficiently could be made stronger with an additional Without running ANALYZE it is expected that your query performance will in some cases be drastically worse! or something like that...

(Sidenote: Any failed pg_upgrade will result in a rolled back user config to the old version and the pg_upgrade logs will be emailed to the customer)
In addition, any pg_upgrade has some risk of downtime and data loss if the node goes down before the system is back in a normal state: During upgrade, we will not have any standbys and starting up standbys will only happen after the upgrade has happened AND after the first basebackup is up (which can take a long time, in the double digit hours range for huge clusters!). Currently it says: Standby nodes are removed and replacements are created for the new version which makes it sound we prepare new standbys already beforehand. Basically, if this takes some time, it means we do not have a hot standby during that time which means downtime and data loss if a node goes down (e.g. Cloud provider has problems) as we manually (via support ticket) have to reset the service config to the old pg version, restore from the old backup and cannot replay the wal files from the time pg_upgrade finished until the node went down.
Is this something you would work on yourself?
[ ] I plan to open a pull request for this

Some more infos regarding the impact on disk usage:
A pg upgrade is done inplace (pg_upgrade --link, using filesystem hardlinks for the table data, but in between the schema itself is dumped from the old version and restored on the new version).

If you have very large schemas or (much more likely) use many pg large objects (which is an anti pattern!), the dump file can be enormous (several GB) which a) leads to very slow pg_uprade timings (hours instead of seconds, see above) and b) that file is kept around, so reduces the service disk.
In addition, if you drop tables after a pg_upgrade, the table files are still referenced in the old data directory and so not freed and so again the service volume might have less disk than what should be there just by seeing the consumption of the running PG.

This can be fixed only by a maintenance update (node is replaced) after the pg_upgrade, which we currently not automatically do (so would happen only after we issue another maintenance update)

https://github.com/aiven/devportal/pull/1406


An implementation cannot be declared in ambient contexts.

Search terms
An implementation cannot be declared in ambient contexts.
Expected Behavior
To Generate Documentation
Actual Behavior
Provides Me With An Error, And Does Not Generate Documentation
Using TypeScript 4.0.2 from C:\Users\624234\AppData\Roaming\npm\node_modules\typescript\lib
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(18)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(25)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(38)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(49)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(56)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(67)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(78)
 An implementation cannot be declared in ambient contexts.
Error: C:/Users/624234/Desktop/Blubba/typings/index.d.ts(85)
 An implementation cannot be declared in ambient contexts.
npm ERR! code ELIFECYCLE
npm ERR! errno 4
npm ERR<EMAIL_ADDRESS>docs: `typedoc --out docs --includeDeclarations typings/index.d.ts`
npm ERR! Exit status 4
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>docs script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\624234\AppData\Roaming\npm-cache\_logs\2020-10-10T04_40_03_821Z-debug.log

Steps to reproduce the bug
typedoc --out docs --includeDeclarations typings/index.d.ts
// index.d.ts (first 100 lines)
/**
   * PLAYER ACTION
   *
   * Used to do something related to
   * a player or multiple players.
   *
   * \> Send a message to a player
   * \> Damage or heal a player
   * \> Clear a player's inventory
   */
  export interface player_action {
    /**
     * PLAYER ACTION
     *
     * Used to do something related to
     * a player or multiple players.
     *
     * \> Send a message to a player
     * \> Damage or heal a player
     * \> Clear a player's inventory
     */
    CLOSEINV(): void;

    /**
     * PLAYER ACTION
     *
     * Used to do something related to
     * a player or multiple players.
     *
     * \> Send a message to a player
     * \> Damage or heal a player
     * \> Clear a player's inventory
     */
    CLEAREFFECTS(): void;

    /**
     * PLAYER ACTION
     *
     * Used to do something related to
     * a player or multiple players.
     *
     * \> Send a message to a player
     * \> Damage or heal a player
     * \> Clear a player's inventory
     */
    GIVEITEMS(
      ITEM_S__TO_GIVE: ITEM | ITEM[],
      AMOUNT_TO_GIVE: undefined | NUMBER
    ): void;

Environment

Typedoc version: 4.0.2
TypeScript version: 4.0.2
Node.js version: v12.18.4
OS: Windows 10 (x64)

This is unactionable without a reproduction. Even the first 100 lines of that index.d.ts looks like it might be enough given that it looks like there are errors there.

I can't seem to reproduce this... the declaration file looks fine to me too. I copied your declaration file into a new project:
package.json
{
  "name": "gh1374",
  "version": "1.0.0",
  "main": "index.js",
  "devDependencies": {
    "typedoc": "^0.19.2",
    "typescript": "4.0.2"
  }
}

Copied the typings into typings/index.d.ts, with a slight adjustment to make it compile:
    GIVEITEMS(
      ITEM_S__TO_GIVE: ITEM | ITEM[],
      AMOUNT_TO_GIVE: undefined | NUMBER
    ): void;
}

type ITEM = string
type NUMBER = number

And ran your command, which generated this page.

It took a while since that command also documented everything in the lib, so I also added --excludeExternals to speed it up.

I'm not sure why i supplied that as my first 100 lines,
here's my actual first 100 lines:
declare namespace blubba {
  type ANY_TYPE =
    | (TEXT | string)
    | (NUMBER | number)
    | LOCATION
    | VARIABLE
    | PARTICLE
    | POTION
    | PROJECTILE
    | ITEM
    | SOUND
    | LIST;

  class Value {
    value: any;
  }

  export class TEXT extends Value {
    constructor(value: TEXT | string | VARIABLE) {
      super();
      this.value = value;
    }
  }

  export class NUMBER extends Value {
    constructor(value: NUMBER | number | VARIABLE) {
      super();
      this.value = value;
    }
  }

  export class LOCATION extends Value {
    constructor(
      x: number | VARIABLE,
      y: number | VARIABLE,
      z: number | VARIABLE,
      pitch: number | undefined | VARIABLE,
      yaw: number | undefined | VARIABLE
    ) {
      super();
      this.value = {
        x,
        y,
        z,
        pitch,
        yaw,
      };
    }
  }

  export class VARIABLE extends Value {
    constructor(key: TEXT | string | VARIABLE, value: ANY_TYPE) {
      super();
      this.value = { key, value };
    }
  }

  export class PARTICLE extends Value {
    constructor(value: string | ITEM | VARIABLE) {
      super();
      this.value = value;
    }
  }

  export class POTION extends Value {
    constructor(
      value: string | ITEM | VARIABLE,
      length: number | undefined | VARIABLE,
      amplifier: number | undefined | VARIABLE
    ) {
      super();
      this.value = {
        value,
        length,
        amplifier,
      };
    }
  }

  export class PROJECTILE extends Value {
    constructor(value: string | ITEM | VARIABLE) {
      super();
      this.value = value;
    }
  }

  export class ITEM extends Value {
    constructor(value: string | ITEM | VARIABLE) {
      super();
      this.value = value;
    }
  }
}

Well that explains why it is complaining. You can't have an implementation in a declaration file... just like the error says. It sounds like the file should be named index.ts, not index.d.ts.

Now I'm getting the same errors in that file!

Oh i see! I'm actually implementing the code that would happen, typescript doesn't like that


pycache

The pycache folders should not be in the repo.

sure .. my error in copy and adding

Hai.. if you feel something can be done to improve the repo and add any issues ... please feel free to message and send a comment for same. Very much appreciate your time to solve the issues which did not get updated and will be taking time out to add more nodes and clear the sound player issues.


Choosing directory for --save-images

Hi!
Is there a workaround to be able to specify a different output directory for --save-images?
Thanks!

Hello @nywhere;
Currently, due to the way PySceneDetect is implemented, images are outputted to the working directory.  What are you trying to achieve/implement out of curiosity, and are you using the command-line or Python interface?  (I assume CLI, but just want to make sure)
Assuming command-line, this is definitely possible with a script, but I can see this being a useful feature.  In future versions, do you think it would be worth-while to allow the -si / --save-images flag to accept an optional output directory?  Any feedback on the matter would be much appreciated.

Breakthrough

Hi,
Thanks for your answer! I'm using the CLI and want to obtain the first image of each scene along with the time of this scene change. It would be definitely great to be able to choose the output directory for images so it does not get messy in the working dir.
Few other simple things that could make the life easier, maybe you will find some of them interesting:

base naming convention for images (for example XXXX then the system will export XXXX_00001_IN.jpg). Btw, notice that I put 00001 so it stays consistent in the output folder, for now it orders the picture with 1,10,100,2, 3, 4, 5, 6, 7....
choosing to export IN or OUT or both IN and OUT images
defining output resolution for images (this one would be really cool actually)
output a Json listing the timecode and image filename for each scene change

Thanks!

I want this feature too! Thanks

I'm using https://github.com/handflucht/PySceneDetect to run PySceneDetect and being able to specify an output directory would be really helpful!

As an update, the new v0.5 CLI will support the concept of subcommands, where each subcommand will accept options such as output directory.  My aim for the CLI implementation would be to call something like:
scenedetect --input somevideo.mp4 detect-content --threshold 27 output-images --directory output_image_dir/


[Feature] See what else you can add to the bot

The bot is on it's bare bones right now. See if you can add some trolling to it

Can I add a feature like?
On Tuesday,
"Is it Wednesday?" returns "Keep calm and wait for Wednesday" or "Brace yourself, Wednesday is coming" ?
On Thursday,
"Is it Wednesday?" returns "It was yesterday. Do you want more Wednesdays? Me too"
May I try to do it?

Sure! I'll open a new issue for you

@guieiras #3

Instead of keep giving the same picture maybe we can randomize the image from collection, and i would like to implement it

Sure! I love that suggestion. Maybe we can take the most voted picture from the sub reddit


sample code typo

Describe the issues and typos
Missing comma.
Expected behavior
Just add comma.
Screenshots

If applicable, add screenshots to help explain the reported issues.

Fixed. Thank you :)


Make code more pythonic

[x] Function names are not following the snake case convention
[x] Review variable names
[x] Review module names

implemented in:

403734e
2c9d574
206af82
c920ed0
8c08050
eae268a


Provide ts_skip()

Add a mechanism for skipping tests.  Useful for marking tests as half-written, etc.
This reuses the TS_NOEX output which seems to be a relic of some older revision, but we can reuse it in the case of skipping tests.

That's a good point, the tests cannot pass given my change.  I will update that; ironically, I forgot ts(1) was even tested in this way.  Oops.
As for the NOEX point, TS_NOEX is not used at all, and all instances where 'X' is used to mark a test as non-executable is hard-coded.  I would argue with my change, that we change this to a skip invocation, citing a reason why it was skipped (such as 'not executable', or something).  I see no reason to differentiate S versus X in this case; either way,  the non-executable case cannot run, and is effectively skipped, regardless.

What is it you're asking me to do, exactly?  Are you saying you want to differentiate between TS_NOEX and skipped tests?  Either way, please see the updated patch, fixing up the test suite.  I don't quite see the relevance of having TS_NOEX at all, it's not doing anything, unless I'm missing some dark oddity, as with ts_include()?

I see.  Well, I'm not doing anything further on this, because it does something reasonable, and handles the  non-executable case by marking it as skipped, and outputting a message to the terminal, which I think is useful.  The default colour is yellow (as was the case with TS_NOEX by default), and can be overridden in the environment.
Note that the noex case is handled before any tests inside said file are run, as that cannot happen anyway, and you'll see on your terminal why:  "not executable".

OK, will do.

Actually, the point of putting a touched file inside of ts_test_dir is so that the specific test being skipped is flagged.  Not doing this is going to be a pain.  What's so special about ts_test_dir that it can't be used for this purpose?

Sorry for the delay on this.  See the latest pull-request.  I've updated it, and implemented all of your suggestions.  Same functionality as before, plus some very basic tests.

OK, that's fine.  Sure, I don't mind being added as a contributor.  Thanks.

I've taken a look at this branch, and been using the code recently; seems to work fine, FWIW.

Any  news on this?  Almost two months now...

@thinkerbot - politely asking one last time before I consider forking this project; any news on whether what I've implemented will ever make it into your repository?


Vite 2.3.0 breaks on using vue.draggable.next

Describe the bug
Using vite 2.3.0 i get the following exception when i use https://github.com/SortableJS/vue.draggable.next
The same code works with vite 2.2.4.
vuedraggable.js:136 Uncaught TypeError: external_commonjs_sortablejs_commonjs2_sortablejs_amd_sortablejs_root_Sortable_default.a is not a constructor
    at Proxy.mounted (vuedraggable.js:136)
    at callWithErrorHandling (runtime-core.esm-bundler.js:154)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:163)
    at Array.hook.__weh.hook.__weh (runtime-core.esm-bundler.js:1953)
    at flushPostFlushCbs (runtime-core.esm-bundler.js:355)
    at render2 (runtime-core.esm-bundler.js:4885)
    at mount (runtime-core.esm-bundler.js:3077)
    at Object.app.mount (runtime-dom.esm-bundler.js:1259)
    at main.js:4

Reproduction

Clone https://github.com/mseele/vite-draggable-bug
Exec yarn run dev
Open Browser and check console error

If you change vite version to 2.2.4 in package.json, everything works.

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz
    Memory: 14.45 GB / 31.92 GB
  Binaries:
    Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 90.0.4430.93
    Edge: Spartan (44.19041.964.0), Chromium (90.0.818.56)
    Internet Explorer: 11.0.19041.1
  npmPackages:
    @vitejs/plugin-vue: ^1.2.2 => 1.2.2
    vite: 2.3.0 => 2.3.0

Used package manager: yarn

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

I get the same error when importing a DatePicker from v-calendar:
import DatePicker from 'v-calendar/lib/components/date-picker.umd';
this worked in 2.2.4

import draggable from 'vuedraggable/src/vuedraggable' is work！

import draggable from 'vuedraggable/src/vuedraggable' is work！

Good to hear, but something has been changed or broken functionality with 2.3.x anyway

Especially I think it was this commit: 05fd1e2

Might be something else because https://github.com/vitejs/vite/commit/05fd1e26be1c64c665b5c01161f2e789c1deb6aa has been reverted (https://github.com/vitejs/vite/commit/4112c5d103673b83c50d446096086617dfaac5a3) and i still get the error in vite 2.3.4

@mseele could you try this again with Vite v2.3.7? @Shinigami92 had a similar issue (#3309) that is now fixed.

2.3.7 solved it for me

Marked as solved for now. Feel free to bring it back if it still occurs.


Passing session token via -s argument fails

AWS Consoler version: Latest
Python version: 3.8.2
Operating System: Latest Kali

Description
Attempting to pass the access key, secret key, and session token via CLI arguments failed with the following error. Attempted wrapping arguments in quotes as well. I was able to get around this by creating a profile and using the -p argument instead.
What I Did
aws_consoler -v -a A[REDACTED]V -s [REDACTED] -t IQoJb3JpZ2luX2VjEIf//////////wEaC[REDACTED]A==
2020-05-07 13:45:03,278 [aws_consoler.cli] INFO: Validating arguments...
2020-05-07 13:45:03,278 [aws_consoler.cli] INFO: Calling logic.
2020-05-07 13:45:03,284 [aws_consoler.logic] INFO: Session using credential variables established.
2020-05-07 13:45:03,578 [aws_consoler.logic] INFO: Session valid, attempting to federate as arn:aws:sts::5[REDACTED].
2020-05-07 13:45:03,578 [aws_consoler.cli] CRITICAL: expected string or bytes-like object

Ran the same command with -vv. Output is below.
2020-05-07 14:01:23,282 [aws_consoler.cli] INFO: Validating arguments...
2020-05-07 14:01:23,282 [aws_consoler.cli] INFO: Calling logic.
2020-05-07 14:01:23,282 [aws_consoler.logic] DEBUG: Establishing Boto3 session.
2020-05-07 14:01:23,282 [aws_consoler.logic] DEBUG: Using CLI-provided credentials.
2020-05-07 14:01:23,288 [aws_consoler.logic] INFO: Session using credential variables established.
2020-05-07 14:01:23,584 [aws_consoler.logic] INFO: Session valid, attempting to federate as arn:aws:sts::5[REDACTED].
2020-05-07 14:01:23,584 [aws_consoler.cli] CRITICAL: expected string or bytes-like object

Interesting note. Running as the same user was then working using the command line arguments. I believe this is due to me running
aws configure

I created a new user and ran first command here and replicated the issue. So this may be due to not having aws cli configured in the first place.

I suspect this is an issue with AWS Consoler not knowing what region to use - as of v1.1.0, a region is required to detect what partition should be authenticated to.
However, it doesn't look like there's a good base case (should default to the standard partition) - I'll have to make some changes to make it easier for folks.
In the short-term, you can fix this by passing -R us-east-1 on the command line.

You seem to be correct. Passing the region yields a federation URL to use. Thanks for the quick fix!

@RyanGandrud This has been included in 1.1.1. Please give v1.1.1-rc.1 a shot from the releases page, and let me know if it works for you.

That works! Assumes standard aws region and outputs a message stating as much.

@johnsaigle I'm no longer with the organization, I'd have to check if there's someone able to merge the changes in. You can use the workaround documented above, or grab the rc1 version.


The new 1.4 version brokes "rails new" experience for all existent Rails versions.

https://github.com/rails/rails/issues/35161 for cross-reference

This doesn't seem like a bug in SQLite. Rails should be less brittle.

Closing since it's not considered a SQLite bug

新版本1.4.1 有问题


Feat: Polkadot v1.7 to v1.8 upgrade

Description
This PR is upgrading Runtime's and Node's dependencies from Polkadot-SDK release v1.7.0 to v1.8.0
Notes
Relevant upgrade's notes and comments.

Added ApiVersion type in pallet_contract config.
Breaking changes

3395: benchmarking-cli pallet subcommand: refactor --list and add --all option
3079: Implement transaction_unstable_broadcast and transaction_unstable_stop
3244: Make the benchmark pallet command only require a Hasher
3384: [pallet_contracts] stabilize call_v2, instantiate_v2, lock_dependency and unlock_dependency
3052: Fixes a scenario where a nomination pool's TotalValueLocked is out of sync due to staking's implicit withdraw
3060: Add retry mechanics to pallet-scheduler
3154: Contracts: Stabilize caller_is_root API
3184: Contracts: Remove no longer enforced limits from the Schedule
3230: rpc server remove prometheus metrics substrate_rpc_requests_started/finished and refactor WS ping/pongs.

Kindly refer to the official Polkadot release report for further details: Polkadot v1.8.0

Process

[x] Bump workspace dependencies
[x] Fix issues
[x] Bump spec_ver for both testnet and mainnet Runtime.
[x] Bump node version if there were changes in the node.

Codebase Upgrade Acceptance Criteria

[x] cargo check passes
[x] cargo test passes
[x] cargo build on -- release profile correctly builds
[x] try-runtime and runtime-benchmarks features compile
[x] Single node spinned up from binary works and generates blocks
[x] Zombienet network with 2 peers spawned with block-production config file generates blocks.

Runtime & Node Upgrade Acceptance Criteria

[x] Runtime upgrade works on Zombienet

[x] Node upgrade works on Zombienet

[x] Runtime upgrade works on Chopsticks

[x] Testnet
[x] Mainnet

[x] Try-runtime passes with no pending migrations

[x] Testnet
[x] Mainnet

<!--- PR TEMPLATE CONTENT STARTS HERE -->
Types of Changes
Please select the branch type you are merging and fill in the relevant template.
<!--- Check the following box with an x if the following applies: -->

[ ] Hotfix
[ ] Release
[x] Fix or Feature

Fix or Feature
<!--- Check the following box with an x if the following applies: -->
Types of Changes
<!--- What types of changes does your code introduce? -->

[ ] Tech Debt (Code improvements)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Dependency upgrade (A change in substrate or any 3rd party crate version)

Migrations and Hooks
<!--- Check the following box with an x if the following applies: -->

[ ] This change requires a runtime migration.
[ ] Modifies on_initialize
[ ] Modifies on_finalize

Checklist for Fix or Feature
<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

[x] Change has been tested locally.
[ ] Change adds / updates tests if applicable.
[ ] Changelog doc updated.
[x] spec_version has been incremented.
[ ] network-relayer's events have been updated according to the blockchain events if applicable.
[ ] All CI checks have been passed successfully

Checklist for Hotfix
<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

[ ] Change has been deployed to Testnet.
[ ] Change has been tested in Testnet.
[ ] Changelog has been updated.
[ ] Crate version has been updated.
[ ] spec_version has been incremented.
[ ] Transaction version has been updated if required.
[ ] Pull Request to dev has been created.
[ ] Pull Request to staging has been created.
[ ] network-relayer's events have been updated according to the blockchain events if applicable.
[ ] All CI checks have been passed successfully

Checklist for Release
<!--- All boxes need to be checked. Follow this checklist before requiring PR review -->

[ ] Change has been deployed to Devnet.
[ ] Change has been tested in Devnet.
[ ] Change has been deployed to Qanet.
[ ] Change has been tested in Qanet.
[ ] Change has been deployed to Testnet.
[ ] Change has been tested in Testnet.
[ ] Changelog has been updated.
[ ] Crate version has been updated.
[ ] Spec version has been updated.
[ ] Transaction version has been updated if required.
[ ] All CI checks have been passed successfully

@Aideepakchaudhary pallet::getter has been deprecated and removed in Polkadot v1.8.0. Would it be possible to remove it from all storages and pallets in our codebase?
Please see this https://github.com/paritytech/polkadot-sdk/pull/3371 for example.

Hi @ayushmishra2005 , we'll integrate these changes in the stable branch: https://github.com/Cerebellum-Network/blockchain-node/pull/456