[Feat]: release freebsd images for zot

Is your feature request related to a problem? Please describe.
PR #1660 adds support for freebsd binaries. This issue is being filed so that we track the remaining step of releasing freebsd container images for zot once an official freebsd-minimal image is available.
cc: @dfr
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

@dfr Noticed that the images you are pushing to dockerhub are docker images and not OCI. Is this intended? For example official ubuntu images are pushed as OCI images.
https://hub.docker.com/r/dougrabson/freebsd-minimal/tags

@dfr There are many tools. For example,
https://github.com/google/go-containerregistry/tree/main/cmd/crane
crane manifest <image> | jq .

In comparison, ubuntu
$ crane manifest ubuntu:latest | jq .

{
  "manifests": [
    {
      "digest": "sha256:c9cf959fd83770dfdefd8fb42cfef0761432af36a764c077aed54bbc5bb25368",
      "mediaType": "application/vnd.oci.image.manifest.v1+json",

@dfr So you are pushing docker images to dockerhub. Not sure if this was intentional - from what I understand, FreeBSD is standardizing on OCI?

This is strange - I pushed the same image to both docker.io and quay.io but the manifest type on dockerhub is different.
$ crane manifest docker.io/dougrabson/freebsd13.2-static:13.2p2 | jq .
{
  "schemaVersion": 2,
  "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
  "manifests": [
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "size": 1130,
      "digest": "sha256:4378443a2023c8804997bca2f5e8c33944085e2102e192af0dcea943053b59bb",
      "platform": {
        "architecture": "amd64",
        "os": "freebsd"
      }
    },
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "size": 1132,
      "digest": "sha256:cc62ec2301fdfab24d0e3976ff86ba16938ead54d638acdee1436d3ff5a3c1f9",
      "platform": {
        "architecture": "arm64",
        "os": "freebsd"
      }
    }
  ]
}

$ crane manifest quay.io/dougrabson/freebsd13.2-static:13.2p2 | jq .
{
  "schemaVersion": 2,
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "manifests": [
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "digest": "sha256:4378443a2023c8804997bca2f5e8c33944085e2102e192af0dcea943053b59bb",
      "size": 1130,
      "platform": {
        "architecture": "amd64",
        "os": "freebsd"
      }
    },
    {
      "mediaType": "application/vnd.oci.image.manifest.v1+json",
      "digest": "sha256:cc62ec2301fdfab24d0e3976ff86ba16938ead54d638acdee1436d3ff5a3c1f9",
      "size": 1132,
      "platform": {
        "architecture": "arm64",
        "os": "freebsd"
      }
    }
  ]
}

@dfr
Ah I see. So you are pushing a multi-arch image index (which is docker media-type) but the individual image manifests in that image index are all OCI.
Perhaps your buildah (if that is what you are using) version needs to be a more recent one. There are some known breakages with older versions.
https://github.com/containers/buildah/issues/4395
buildah push --all -f oci ...

@dfr do you have an anticipated time frame for an official freebsd image release? Asking so we can coordinate our release window accordingly if possible.

I can't give a very clear answer but conservatively, Q1 2024 is quite possible. One of the main blocking factors should be resolved with the upcoming 14.0 FreeBSD release and I plan to work with the release engineers after that to integrate my image building scripts into their process.

@dfr FYI, 2.0.0-rc7 released.
https://github.com/project-zot/project-zot.github.io/blob/main/docs/general/whats-new.md
^ docs preview.


[FEAT] Implement API Endpoint for Sending Email Requests

Description
Develop an endpoint to handle requests for sending emails using pre-defined templates. The emails should be placed in a database queue for sending to ensure the application remains responsive. The endpoint should handle variable substitution, replacing placeholders in the templates with actual data.
Acceptance Criteria

The endpoint should receive requests to send emails using specific templates.
The endpoint should handle variable substitution to replace placeholders with actual data.
The email sending request should be stored in a database queue.
The endpoint should return appropriate status codes and responses based on the outcome of the request.
Endpoints should be correctly versioned.

Data Validation

Input Validation: Validate that template_id, recipient, and variables fields are provided and correctly formatted.
Output Validation: Ensure the response contains the correct status and message.
Authentication and Authorization
Authentication: Ensure the endpoint requires valid user authentication.
Authorization: Verify that the user has permission to send emails using the specified template.

Error Handling
Error Responses: Define error responses for scenarios such as missing template, invalid input, and internal server errors.
Edge Cases: Consider edge cases such as template not found, invalid email format, and missing variables.
Performance and Security
Performance Considerations: Ensure the email request queuing system is efficient and does not degrade application performance.
Security Concerns: Address security considerations such as data sanitization, input validation, and protection against injection attacks.
Documentation
API Documentation: Provide comprehensive API documentation for the endpoint, including request and response formats.
Technical Notes: Include any additional technical notes or considerations for implementing the endpoint.
Testing Requirements

Unit Tests: Implement unit tests to verify the functionality of the endpoint.
Integration Tests: Develop integration tests to ensure the endpoint works correctly with other system components.
Dependencies and Impact
Dependencies: Identify any dependencies on other tasks or systems, such as the database queue implementation.
Impact Analysis: Assess the potential impact on other features or components of the application.

Requirements

Implement an API endpoint for sending emails using templates.
Handle variable substitution for placeholders in the email templates.
Store email sending requests in a database queue.
Handle unexpected errors and return the appropriate status codes.
Ensure endpoints are correctly versioned.

Expected Outcome

Users should be able to send requests to the backend to enqueue emails using templates.
Users should receive appropriate status codes and responses based on the outcome of the requests.
Emails should be queued for sending without blocking the main application flow.
Endpoints

[POST] /api/v1/send-email
Description: Enqueues an email request using a specified template.
Request Body:
{
  "template_id": 1,
  "recipient"<EMAIL_ADDRESS>  "variables": {
    "name": "John Doe",
    "product": "Wireless Headphones",
    "order_number": 12345
  }
}
Success Response:
Status Code: 202 Accepted
Body:

{
  "message": "Email sending request accepted and is being processed in the background."
}
Error Responses:
Status Code: 500 Internal Server Error
Body:

{
  "error": "Internal server error."
}
status Code: 404 Not Found
Body:

{
  "error": "Template not found."
}
Status Code: 405 Method Not Allowed
Body:

{
  "error": "This method is not allowed."
}
Status Code: 400 Bad Request
Body:

{
  "error": "An invalid request was sent."
}

Testing
Test Scenarios
Successful Email Sending Request

Ensure that the endpoint accepts a request to send an email using a template.

Verify that the response indicates the request is being processed in the background.

Confirm that the status code is 202 Accepted.

Template Not Found

Simulate a scenario where the specified email template ID does not exist.

Confirm that the response body contains an appropriate error message.

Confirm that the status code is 404 Not Found.

Internal Server Error

Simulate an internal server error to raise an exception.

Verify that the endpoint returns a 500 Internal Server Error status code.

Confirm that the response body contains an appropriate error message.

Invalid Method

Send a request using an invalid HTTP method (e.g., GET) to the endpoint.

Verify that the endpoint returns a 405 Method Not Allowed status code.

Confirm that the response body contains an appropriate error message.

Bad Request

Send a request with invalid data (e.g., missing required fields) to the endpoint.

Verify that the endpoint returns a 400 Bad Request status code.

Confirm that the response body contains an appropriate error message.

This issue is linked to the approved issue


New Version here:

Verify it's not a duplicate bug report

[X] I searched for similar bugs reported on GitHub and nobody has reported a similar issue. Search all issuees.
[X] I read Troubleshooting guide on Readme and there is not a guide on how to solve my problem.

Describe the Bug
I hate to do this, but just couldnt stand it anymore. Seems like this project is dead.
With that said I've totally refactored the original extention to use the new OpenAI 4.0 beta, and best of all, implemented a GPT-Engineer type button to autonomously code. Yup!
Get it here, supports the 16k model, 32k, Azure and OpenAI.
https://marketplace.visualstudio.com/items?itemName=Autonimate.autonimate&ssr=false#review-details
Please tell us if you have customized any of the extension settings or whether you are using the defaults.
Yes big time.
Additional context
r

@Cytranics this isn't a new version.
@anyone else, If you want a more up-to-date extension or even selfhost your own extension check out my open-source project here. I have instructions on how to get it running locally without needing to download any extension for free: https://github.com/gencay/vscode-chatgpt. We will work on addressing the recent changes from OpenAI at some point, we just don't have enough time to do that.

This is your ext bud, I modified your code to work with the latest models. What's the issue?
Sent from Ninehttp://www.9folders.com/

From: Ali Gençay @.***>
Sent: Wednesday, July 12, 2023 6:05 PM
To: ai-genie/chatgpt-vscode
Cc: Cory Coddington; Mention
Subject: Re: [ai-genie/chatgpt-vscode] New Version here: (Issue #121)
@Cytranicshttps://github.com/Cytranics this isn't a new version.
@anyonehttps://github.com/anyone else, If you want a more up-to-date extension or even selfhost your own extension check out my open-source project here. I have instructions on how to get it running locally without needing to download any extension for free: https://github.com/gencay/vscode-chatgpt. We will work on addressing the recent changes from OpenAI at some point, we just don't have enough time to do that.
—
Reply to this email directly, view it on GitHubhttps://github.com/ai-genie/chatgpt-vscode/issues/121#issuecomment-1633269637, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5RL5MGAZCTRGIQNI4NIFS3XP4NTBANCNFSM6AAAAAA2IBRSYI.
You are receiving this because you were mentioned.Message ID: @.***>


Fix: F999 dictionary key '2000q4' repeated with different values

Removal of duplicate line to fix lint error
pandas/tseries/tests/test_tslib.py:685:18: F999 dictionary key '2000q4' repeated with different values
pandas/tseries/tests/test_tslib.py:690:18: F999 dictionary key '2000q4' repeated with different values

Current coverage is 85.24% (diff: 100%)

Merging #14198 into master will not change coverage

@@             master     #14198   diff @@
==========================================
  Files           140        140
  Lines         50556      50556
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          43095      43095
  Misses         7461       7461
  Partials          0          0

Powered by Codecov. Last update 289cd6d...82459ba

this is not a duplicate (it's lowercase)
otherwise the linter would have picked this up before

Have a look: https://github.com/pydata/pandas/blob/master/pandas/tseries/tests/test_tslib.py
line 685 vs line 690:
'2000q4': datetime.datetime(2000, 10, 1),
'2000q4': datetime.datetime(2000, 10, 1),
exactly the same. Line 681 is a different case:
'2000Q4': datetime.datetime(2000, 10, 1),
Lint must have got more stick with repeated keys.

hmm now it's failing
https://travis-ci.org/pydata/pandas/jobs/158971225


Failed to add  as Storage Blob Data Contributor for  : The role assignment already exists.

Following the article, when we try to add the Blob Data Contributor role, I get the error:
"
Failed to add Role assignment
Failed to add  as Storage Blob Data Contributor for  : The role assignment already exists..
It sounds like the ML Workspace provision step, does add the role to the store, so the following step is redundant:
_Enable studio
Azure Machine Learning studio is a web-based application that lets you easily manage your workspace. However, it needs some extra configuration before it can be used with resources secured inside a VNet. Use the following steps to enable studio:
From the Azure portal, select your storage account and then select Access control (IAM).
Select + Add, and then Add role assignment (Preview).
Access control (IAM) page with Add role assignment menu open.
On the Role tab, select the Storage Blob Data Contributor._

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

ID: 12327d27-73c1-c446-ec7b-b9af3a6f68f7
Version Independent ID: 49adc002-e9c7-bbcc-6a6e-cce987883b58
Content: Create a secure workspace - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-create-secure-workspace.md
Service: machine-learning
Sub-service: core
GitHub Login: @Blackmist
Microsoft Alias: larryfr

@msdpalam Thanks for the question. We are investigating the issue and will update you shortly.

@msdpalam Thanks for the feedback. @Blackmist Could you please update the document for the following redundant steps.
https://docs.microsoft.com/en-us/azure/machine-learning/tutorial-create-secure-workspace#enable-studio

Thanks for the feedback @msdpalam I'll check with engineering to make sure this is expected behavior and update the document.

@msdpalam thanks again for the feedback; the document has been updated and will be published later today.
#please-close


[Bug] When a player attempted to access my server, his client crashed.

oh no!
https://mclo.gs/a4fXuGn

Can I get a log of the server also?

This is a crash caused by another mod.


Change registry to registry.k8s.io

No need to merge it for now, just for awareness.
At some point we might need to shift away from k8s.gcr.io because it won't be served anymore.
Feel free to close the PR or change it 🙂
Related issue: https://github.com/giantswarm/roadmap/issues/2534
Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml and values.schema.json are valid.

Important: After this PR is tested and approved, ensure you "Squash and Merge" unless you are updating a subtree. The release automation in use on this repository relies on squashing, but git subtrees will be lost if squashed. This repo allows both, so you may need to change the merge type when merging.

Rules aren't in the Falco charts anymore, but have become a separate repo, and a completely different way of loading them.
Where they have been adjusted by upstream.
Thanks for your efforts.


Natasha/quick fixes

Adds large titles

PLEASE TEST.

the status bar color is white vs the nav bar is off white

there's no bottom grey line under this nav bar anymore

this transition scrolling down doesn't match with the underline bar for all of the tabs... here's an example

The issue with the nav bar and status bar differing colors is with making the nav bar translucent .. its not actually a different color its just translucent so you see the background of it. I tried changing this and it cause a lot of bugs and renders the refresh control unseeable. I don't think its that huge of an issue for the amount of bugs it causes to fix it.

The shadow image is another iOS 11 bug

I've tried that @jackthmp . The problem is when I do then sometimes we get a bug where it now is grey because its taking on the view controllers background image.
Which is the backgroundColor not extending up enough. I can fix that with a background image but then the refresh control isn't visible / the large titles now take up more room below the background image.


Remove header set for uninitialized response.

One of our groups was seeing the following stack track
[ 00 ] libc-2.12.so        __GI___waitpid
[ 01 ] traffic_server      crash_logger_invoke                                                          ( Crash.cc:165 )
[ 02 ] libc-2.12.so
[ 03 ] traffic_server      mime_hdr_field_find                                                          ( MIME.cc:1319 )
[ 04 ] traffic_server      mime_hdr_prepare_for_value_set                                               ( MIME.cc:1692 )
[ 05 ] traffic_server      MIMEHdr::value_set(char const*, int, char const*, int)                       ( MIME.h:1419 )
[ 06 ] traffic_server      HttpSM::do_drain_request_body()                                              ( HttpSM.cc:5755 )
[ 07 ] traffic_server      HttpSM::set_next_state()                                                     ( HttpSM.cc:7601 )
[ 08 ] traffic_server      HttpSM::call_transact_and_set_next_state(void (*)(HttpTransact::State*))     ( HttpSM.cc:7335 )
[ 09 ] traffic_server      HttpSM::handle_api_return()                                                  ( HttpSM.cc:1661 )
[ 10 ] traffic_server      HttpSM::state_api_callout(int, void*)                                        ( HttpSM.cc:1596 )
[ 11 ] traffic_server      HttpSM::state_api_callback(int, void*)                                       ( HttpSM.cc:1363 )
[ 12 ] traffic_server      TSHttpTxnReenable                                                            ( InkAPI.cc:5921 )
[ 13 ] esi.so              globalHookHandler                                                            ( esi.cc:1659 )
[ 14 ] traffic_server      INKContInternal::handle_event(int, void*)                                    ( InkAPI.cc:1064 )
[ 15 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 16 ] traffic_server      APIHook::invoke(int, void*)                                                  ( InkAPI.cc:1284 )
[ 17 ] traffic_server      HttpSM::state_api_callout(int, void*)                                        ( HttpSM.cc:1523 )
[ 18 ] traffic_server      HttpSM::do_api_callout_internal()                                            ( HttpSM.cc:5270 )
[ 19 ] traffic_server      HttpSM::do_api_callout()                                                     ( HttpSM.cc:438 )
[ 20 ] traffic_server      HttpSM::set_next_state()                                                     ( HttpSM.cc:7368 )
[ 21 ] traffic_server      HttpSM::call_transact_and_set_next_state(void (*)(HttpTransact::State*))     ( HttpSM.cc:7335 )
[ 22 ] traffic_server      HttpSM::handle_api_return()                                                  ( HttpSM.cc:1661 )
[ 23 ] traffic_server      HttpSM::state_api_callout(int, void*)                                        ( HttpSM.cc:1596 )
[ 24 ] traffic_server      HttpSM::state_api_callback(int, void*)                                       ( HttpSM.cc:1363 )
[ 25 ] traffic_server      TSHttpTxnReenable                                                            ( InkAPI.cc:5921 )
[ 26 ] libatscppapi.so.7   (anonymous namespace)::handleTransactionEvents(tsapi_cont*, TSEvent, void*)  ( utils_internal.cc:93 )
[ 27 ] traffic_server      INKContInternal::handle_event(int, void*)                                    ( InkAPI.cc:1064 )
[ 28 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 29 ] traffic_server      APIHook::invoke(int, void*)                                                  ( InkAPI.cc:1284 )
[ 30 ] traffic_server      HttpSM::state_api_callout(int, void*)                                        ( HttpSM.cc:1523 )
[ 31 ] traffic_server      HttpSM::do_api_callout_internal()                                            ( HttpSM.cc:5270 )
[ 32 ] traffic_server      HttpSM::do_api_callout()                                                     ( HttpSM.cc:438 )
[ 33 ] traffic_server      HttpSM::set_next_state()                                                     ( HttpSM.cc:7368 )
[ 34 ] traffic_server      HttpSM::call_transact_and_set_next_state(void (*)(HttpTransact::State*))     ( HttpSM.cc:7335 )
[ 35 ] traffic_server      HttpSM::state_cache_open_read(int, void*)                                    ( HttpSM.cc:2671 )
[ 36 ] traffic_server      HttpSM::main_handler(int, void*)                                             ( HttpSM.cc:2733 )
[ 37 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 38 ] traffic_server      HttpCacheSM::state_cache_open_read(int, void*)                               ( HttpCacheSM.cc:132 )
[ 39 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 40 ] traffic_server      CacheVC::callcont(int)                                                       ( P_CacheInternal.h:653 )
[ 41 ] traffic_server      CacheVC::openReadStartHead(int, Event*)                                      ( CacheRead.cc:1158 )
[ 42 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 43 ] traffic_server      CacheVC::handleReadDone(int, Event*)                                         ( Cache.cc:2469 )
[ 44 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 45 ] traffic_server      AIOCallbackInternal::io_complete(int, void*)                                 ( P_AIO.h:117 )
[ 46 ] traffic_server      Continuation::handleEvent(int, void*)                                        ( I_Continuation.h:153 )
[ 47 ] traffic_server      EThread::process_event(Event*, int)                                          ( UnixEThread.cc:131 )
[ 48 ] traffic_server      EThread::process_queue(Queue<Event, Event::Link_link>*, int*, int*)          ( UnixEThread.cc:170 )
[ 49 ] traffic_server      EThread::execute_regular()                                                   ( UnixEThread.cc:230 )
[ 50 ] traffic_server      EThread::execute()                                                           ( UnixEThread.cc:325 )
[ 51 ] traffic_server      spawn_thread_internal                                                        ( Thread.cc:85 )
[ 52 ] libpthread-2.12.so  start_thread

In the stack trace, t_state.hdr_info.client_response is not yet initialized, so eventually things crash because of null heaps. Looking through the response logic, I think it is sufficient the just set t_state.client_info.keep_alive. The build_response logic will look at that flag and set the connection header appropriately.  We have been running with that patch internally and it seems to have fixed the issue.

Updated the PR based on autest failures.  We do need to set the Connection header, but there are two cases for transform and non-transform transactions.  The response headers differ.  So moved the do_drain_request_header into the if-else clauses and pass in the appropriate header to update.

Cherry picked to 8.1.0


⚠ Bookkeeper to the Smart People has degraded performance

In c60f928, Bookkeeper to the Smart People (https://bksp.com.au) experienced degraded performance:

HTTP code: 200
Response time: 8196 ms

Resolved: Bookkeeper to the Smart People performance has improved in 56966a6.


[Bug] End Screen Adjustments

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
When prompted with the end screen, it should say "QUERY;" instead of "daily SQL puzzle" so language remains consistent. Additionally, the "View Answer" button does not work as intended as the user has to click it three times for the answer to properly populate.
Expected behavior
When clicking the "View Answer" button, the answer should populate after the first click.
Game version
0.2.2
Any additional information
No response

Hi @JessicaAKelley thanks so much for opening this issue!
The adjustment of the end screen wording is a great one and something I was able to adjust on my end. I also was able to fix the "View Answer" button as well so it properly populates on the first click.
I haven't released a new cut version of the game, but the fixes from this issue will be resolved in v0.2.3. I will close the issue out once the release is live.


[Bug] cell editor overflows

Before you submit this issue, have you checked the following

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Affected packages and versions
所有版本，包括最新的0.4.1
Reproduction link
这个问题应该没有修复， 最新版本在v0.4.1 中我看到虽然将编辑器限制在工作区内了，但是实际的编辑区还是跟之前一样， 导致了可编辑区域都看不完整。见图

Expected behavior
可编辑区域应该完整的控制在编辑区域内，且能够完整的查看到可编辑区域
Actual behavior
现在可编辑区域在sheet 表格区域外了，并且可编辑区域有部分被隐藏了，在内容较多的时候能够体现到，见图

System information
Running environment
Chrome
System information
System:
OS: Windows 11 10.0.22631
Binaries:
Node: 18.20.2 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
pnpm: 9.8.0 - C:\Program Files\nodejs\pnpm.CMD
Browsers:
Edge: Chromium (128.0.2739.42)
Internet Explorer: 11.0.22621.3527

Please provide the minimal reproduction.

Since we haven't received any new replies for over a week, we're temporarily closing this issue.  If you can provide more helpful information, please feel free to reopen it at any time.


zstandard - zlibWrapper folder is not made available with installation

I would like to be able to use the zlibWrapper that is part of the zstandard (zstd) distribution but it does not get copied/compiled with zstd.

Hi @carmangary
Thanks for posting this issue.
zlibWrapper  is one part of zstandard, but there is no CMakeLists.txt in this module. So it cannot be built with zstd.


Branch v1.4 dg/ug

Describe your changes
Update UG and DG for sort command
Add UML diagram for list command
Issue ticket number and link
builds to #140
builds to #138
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:


Add the active crypto backend to build info (go version -m app)

Resolves https://github.com/microsoft/go/issues/963

There is a different mechanism we could use (see comment on #963) but I think this probably the way to go.

This change makes it easier to tell what backend a program ended up being built with by adding lines like cryptobackend=openssl to the build info key-value pairs:
$ GOEXPERIMENT=systemcrypto go build . && go version -m exp
exp: devel go1.21-a011bc5ece Mon Jul 3 13:03:24 2023 -0500 X:systemcrypto
        build   GOEXPERIMENT=systemcrypto
        build   GOOS=linux
        build   cryptobackend=openssl
... [more pairs above and below this output]

$ go build -tags=goexperiment.systemcrypto . && go version -m exp
exp: devel go1.21-a011bc5ece Mon Jul 3 13:03:24 2023 -0500
        build   -tags=goexperiment.systemcrypto
        build   cryptobackend=openssl
...

$ GOOS=windows GOEXPERIMENT=systemcrypto go build . && go version -m exp.exe
exp.exe: devel go1.21-a011bc5ece Mon Jul 3 13:03:24 2023 -0500 X:systemcrypto
        build   GOEXPERIMENT=systemcrypto
        build   GOOS=windows
        build   cryptobackend=cng
...

Note that X:systemcrypto shows up when using GOEXPERIMENT, but -tags doesn't show up there. The -tags line only shows up when the -tags flag is used for go build. Technically, someone (or a program) can look for these signs and figure out what the program is using by understanding the build logic, but this could be fairly fragile. Instead, we can include the info directly.
buildinfo was added in 1.18.
The built-in pairs are defined at https://pkg.go.dev/runtime/debug#BuildSetting, and I haven't seen any reason we shouldn't add our own pairs. The most likely break I can think of is that an external tool will fail if it sees an unrecognized pair, but it seems more likely to me that it would skip them.

@dagood We intending to keep this PR? I noted it was a year old :-)

I would still argue that we should do this. I think now, it's even more important given https://github.com/microsoft/go/issues/1352 (@qmuntal). We should probably also add some straightforward "used Microsoft Go" data.


Chapter 0: running a custom node

here: https://substrate.dev/substrate-collectables-workshop/#/0/running-a-custom-node
you say Then let's go into the now renamed substratekitties folder and build our pre-configured node:, but ./scripts/build.sh return error:
error[E0432]: unresolved import `substratekitties_runtime`
 --> src/lib.rs:5:9
  |
5 | pub use substratekitties_runtime::*;
  |         ^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type or module `substratekitties_runtime`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
error: Could not compile `node-template-runtime-wasm`.

I just ran into this as well.

The problem probably has to do with an update of my script.
Search your project for "node-template" and replace it with substratekitties
Will fix soon

I think this fixed it, please reopen and ping me if that is not the case. Sorry!
https://github.com/shawntabrizi/substrate-package/commit/ba8590ee5edc24ec77e63ef5fc1f50fb4f473cc1

https://github.com/shawntabrizi/substrate-package/commit/ed1228f49ab2e1db152417096848abe4f4afd72a


Bump version of ev-cli

Requires

https://github.com/EVerest/everest-utils/pull/149

TODO before merge

[x] adapt new version of everest-utils in alpine and debian Dockerfile

closed in favor of #19


[embed] Fix build for different environments

Proposed changes
Previous PR for updating build did not work as expected, fixed it here

Security review issue
This is preparation for splitting ghostnet & mainnet environments on Vercel:

Mainnet will have frame-ancestors for allowlisted dApps only.
Ghostnet will work for any url, but for ghostnet requests only.

Once everything is set up and tested, I'll add frame-ancestors to vercel.mainnet.json
Types of changes

[x] Bugfix
[ ] New feature
[ ] Refactor
[ ] Breaking change
[ ] UI fix

Steps to reproduce
Screenshots
Add the screenshots of how the app used to look like and how it looks now

Before
Now

Checklist

[ ] Tests that prove my fix is effective or that my feature works have been added
[ ] Documentation has been added (if appropriate)
[ ] Screenshots are added (if any UI changes have been made)
[ ] All TODOs have a corresponding task created (and the link is attached to it)

@serjonya-trili

those files are empty jsons anyway, why do we need to copy-paste them?

Once everything is set up and tested, I'll add frame-ancestors to vercel.mainnet.json

If I add it now, it will block ghostnet for all users as the setup is not yet completed (new ghostnet deployment is not yet in use & mainnet deployment will require whitelisting on our side after adding frame-ancestors)

and can't it be solved with env variables?

Production and preview can be used the same way as mainnet and ghostnet env vars.
However, in this case we will have to support one preview deployment with a fixed ghostnet url that mirrors main branch state at all times. Also testing mainnet with preview deployments won't be possible
Having separate vercel projects allows to easily deploy main brach code and test both mainnet and ghostnet with preview deployments before the change goes to production.


[Publishing] Add a publications property

Fixed with https://github.com/aalmiray/kordamp-gradle-plugins/commit/0fc9c5b559adedd5d83561f606b0b834181a5aee


Not working at boot

Even if I ran the "linux-enable-ir-emitter boot enable" command and the status is:
● linux-enable-ir-emitter.service - enable the infrared emitter
     Loaded: loaded (/lib/systemd/system/linux-enable-ir-emitter.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Thu 2021-10-14 08:28:01 CEST; 3h 24min ago
   Main PID: 1477 (code=exited, status=0/SUCCESS)

okt 14 08:28:01 user-linux systemd[1]: Starting enable the infrared emitter...
okt 14 08:28:01 user-linux systemd[1]: linux-enable-ir-emitter.service: Succeeded.
okt 14 08:28:01 user-linux systemd[1]: Finished enable the infrared emitter.

It just doesn't enable the emitter during face scan. I need to run the command again to make it work at the current session.
I'm on Ubuntu 20.4.3 LTS

Yes there is an issue on Ubuntu distro based I think. Someone has open the same issue the previous week. Please look at the wiki I've wrote a small fix. https://github.com/EmixamPP/linux-enable-ir-emitter/wiki/Issues.
But the problem is that I don't have a clean fix for this problem. In other words, this fix need to be done manually for each configuration.

Even if I ran the "linux-enable-ir-emitter boot enable" command and the status is:
     Loaded: loaded (/lib/systemd/system/linux-enable-ir-emitter.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Thu 2021-10-14 08:28:01 CEST; 3h 24min ago
   Main PID: 1477 (code=exited, status=0/SUCCESS)

okt 14 08:28:01 user-linux systemd[1]: Starting enable the infrared emitter...
okt 14 08:28:01 user-linux systemd[1]: linux-enable-ir-emitter.service: Succeeded.
okt 14 08:28:01 user-linux systemd[1]: Finished enable the infrared emitter.

It just doesn't enable the emitter during face scan. I need to run the command again to make it work at the current session. I'm on Ubuntu 20.4.3 LTS

But in your first message I don't see ExecStartPre=/sbin/modprobe uvcvideo (code=exited, status=0/SUCCESS).
Or did you mean that you had already applied the wiki fix before opening the issue ?

It seems to work on the latest version. Thanks.

https://github.com/EmixamPP/linux-enable-ir-emitter/issues/57#issuecomment-960600802

The release 3.2.2 is out and I think this will be resolve your problem.

https://github.com/EmixamPP/linux-enable-ir-emitter/issues/60#issuecomment-962477412 this comment means that this issue is also resolved ?

Even the previous version was working sometimes, sometimes wasn't. Let me test it for a few more days, then I will report back

The lastest version doens't modify the boot systemd (unfortunatly).
When you said "usually after nightlong switched off states", you mean hibernate state ? Or a real shutdown ?
An other issue have been open too for hibernate problem. (This hibernate feature isn't activate by default, right ?)

I mean a real shutdown.

I was having the same issue as described above. However, it seems to work on every boot after changing the type of the service to forking, i.e. Type=forking in /usr/lib/systemd/system/linux-enable-ir-emitter.service.
It is probably not an ideal solution, but it fixes some timing issue for me. With oneshot, my success rate was otherwise ~5%.
PS: Many thanks for the great work on this project.

May be these two sets of rules can fix your problem, execute :

sudo mv /etc/udev/rules.d/99-linux-enable-ir-emitter.rules /etc/udev/rules.d/50-linux-enable-ir-emitter.rules
Find in lsusb your camera device, for me it's Bus 001 Device 002: ID 13d3:5406 IMC Networks Integrated Camera
Note for the next step, the two values after ID
Replace my two values with yours in the following command and then execute : echo 'ACTION=="add|change", ATTRS{idVendor}=="13d3", ATTRS{idProduct}=="5406", RUN+="/usr/bin/linux-enable-ir-emitter run"' | sudo tee -a /etc/udev/rules.d/50-linux-enable-ir-emitter.rules
shutdown and start in order to test the solution

The idea of @AndrejOrsula shouldn't necessary in this case.
If someone of you can test it ? I hope I will a day find a solution which works on all Linux distribution :sweat_smile:

Currently testing this latest solution, seems all right so far.

Changing to Type=forking from Type=oneshot as per @AndrejOrsula 's suggestion worked for me on XPS 9520 and Ubuntu 22.04 LTS.


setuptools 34.0.1 fails on python 2.7

setuptools 34.0.1 with python 2.7.11 on Windows 64 bit fails if used with zc.buildout with the following error after "auto" upgrade to the newest setutools version 34.0.1 with the following traceback:
bin\buildout.exe
Upgraded:
  setuptools version 34.0.1;
restarting.
Generated script 'D:\\...\\bin\\buildout'.
Develop: 'D:\\...\\trunk\\.'
Traceback (most recent call last):
  File "c:\tmp\tmpqbbwgz", line 6, in <module>
    import os, setuptools
  File "d:\home\.buildout\eggs\setuptools-34.0.1-py2.7.egg\setuptools\__init__.py", line 12, in <module>
    import setuptools.version
  File "d:\home\.buildout\eggs\setuptools-34.0.1-py2.7.egg\setuptools\version.py", line 1, in <module>
    import pkg_resources
  File "d:\home\.buildout\eggs\setuptools-34.0.1-py2.7.egg\pkg_resources\__init__.py", line 70, in <module>
    import packaging.version
ImportError: No module named packaging.version
While:
  Installing.
  Processing develop directory ...\\trunk\\.'.

An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "d:\home\.buildout\eggs\zc.buildout-2.5.3-py2.7.egg\zc\buildout\buildout.py", line 1995, in main
    getattr(buildout, command)(args)
  File "d:\home\.buildout\eggs\zc.buildout-2.5.3-py2.7.egg\zc\buildout\buildout.py", line 528, in install
    installed_develop_eggs = self._develop()
  File "d:\home\.buildout\eggs\zc.buildout-2.5.3-py2.7.egg\zc\buildout\buildout.py", line 770, in _develop
    zc.buildout.easy_install.develop(setup, dest)
  File "d:\home\.buildout\eggs\zc.buildout-2.5.3-py2.7.egg\zc\buildout\easy_install.py", line 996, in develop
    call_subprocess(args)
  File "d:\home\.buildout\eggs\zc.buildout-2.5.3-py2.7.egg\zc\buildout\easy_install.py", line 160, in call_subprocess
    % repr(args)[1:-1])
Exception: Failed to run command:
'C:\\Python27\\python.exe', 'c:\\tmp\\tmpqbbwgz', '-q', 'develop', '-mN', '-d', 'D:\\..\\trunk\\develop-eggs\\tmpa7ydv3build'

I'm pretty sure this is a buildout issue that will need to be addressed there. I'm not sure what steps an auto upgrade of setuptools does, but it will probably need to pre-install the dependencies of setuptools or use pip to uninstall/install setuptools.

Hi jaraco, Thanks, I guess your are right. I didn't see the new dependencies in setuptools. Hm, I'm not sure if it's a good idea to require other packages for install setuptools which is used for install packages.
What do you think about vendoring the required packages like in distlib? It seems that using virtual env or mess up the system python will be the only two options to install packages in the future.
I'm not really happy with the direction that the package management goes with python. To me, it seems that pip, setuptools and probably others do things which shouldn't be done just for a better end user experience. The cost we pay is a list of preconditions for installl the installler tools and package in python we don't need in our applications.
Probably I missed something. If so, can you explain how a clean python setup should look like without to get any other package into the python runtime except our own source code and our code dependencies? Don't take that as personal criticque. I'm sure you know what you are doing. I just didn't understand the reason why.
Regards Roger

This work is part of simplifying the ecosystem. See #581 for more background on why I made this change.
The recommended usage to install packages is to simply use pip. The Python Packaging Users Guide is where we'll put our best recommendations, so you can consider that authoritative (although it's subject to error and critique as well).
Hope that helps.


Reduce duplicated code blocks in AzureStack.ComputeAdmin.psm1

Many similar logics were copied between different functions, better made them helper functions for reuse

I'm working on this issue

Closing this as the functionality has been replaced with the new AzureStack module version 1.3.0


In history mode, pushing/replacing query params to the same path does nothing

Version
3.0.1
Reproduction link
http://jsfiddle.net/83fogkav/3/
Steps to reproduce
In the linked jsfiddle:
Click the /home link, then click the /home?iam=home. Notice how the query params don't change according to document.location.search (it does change according to this.$route.query).
If you click on the /foo link and then click the /home?iam=home link then it works. I.e., changing the query params only works if you change the path as well.
Note that the same problem happens if you try to push/replace routes via javascript code. For instance, none of the following 4 lines have any effect on the browser's urlbar.
this.$router.push({query: {x: 5}})
this.$router.push({path: document.location.pathname, query: {x: 5}})
this.$router.replace({query: {x: 5}})
this.$router.replace({path: document.location.pathname, query: {x: 5}})

What is expected?
The query string should always be appended to the url.
What is actually happening?
Nothing. No error is signaled and the URL doesn't change.

If you remove mode: 'history', you get the expected behaviour.
Also, if you change the path to something different from the current path, you get the correct behaviour as well.
Also, even though $route.query gets updated, it's important for the browser's urlbar to update as well.

What browser are you using, it does work on my end. Maybe you're trying to access document.location.search too early (in the computed). Could you try checking in the console instead?

I've tested on chromium 64 and firefox 58, both running on arch linux.
If I evaluate document.location.search on the console I get the same behaviour displayed in the jsfiddle I linked. It's always an empty string, both before or after I click the link that should change the query params.
To be honest, I don't really care about document.location.search.
The real issue I have here is that the url doesn't change on the browser's location bar (I only used document.location.search because that's how I managed to expose the problem in the fiddle).
No matter what I do, I can't seem to add query params to the url unless I also change to a different path.

Hold on. Suddenly the behaviour has become inconsistent. I'll see if I can narrow it down.

document.location shows what is seen on the URL bar 😉
Closing for the moment, will reopen if there's indeed a bug

Hey there, I've found the cause of my issue so I wanted to provide an update. This is more or less what I'm doing:
<router-link :to="{query: q}">Search</router-link>

Where q is initialized in the data object as q: this.$route.query and different attributes of q are modified by user interaction with form elements.
Apparently, some nasty issue happens there. If I inspect the link define above in the browser, the href attributes correcly shows everything inside q, but when I click the link nothing happens.
By now, I've learned that this is completely fixed by replacing the initialization with q: {...this.$route.query}.
However, back when I was debugging this issue I ran into a number of other stuff that kept pushing further and further away from the cause. :-)
For instance, I eventually tried a router-link as simple as :to="{query: {x: 1}}". But I still observed the buggy behaviour because by then I had some other code snippets in my file that prevented navigation altogether. Of course, the fact I managed to "reproduce" my issue on a small jsfiddle didn't help either.
Anyway, thanks for your time. And sorry for the noise.

I have the same problem. This code:
context.$router.push({path: document.location, query: {s: context.search}});
Results in the following url (note the symbol ?#):
http://localhost:2121/?#/articles/
But I expected the url:
http://localhost:2121/#/articles/?s=someString


Can't open files in PR

Issue Type: Bug
This works in other repos so I don't know what's special about this.

Open microsoft/vscode-remote-ssh in a local window
Create a PR (https://github.com/microsoft/vscode-remote-ssh/pull/116)
Click a file in the PR in the sidebar view
Get this error notification

Unable to open 'README.md (Pull Request)': The file working copy resource pr:/Users/roblou/code/vscode-remote-ssh/open-ssh-remote/README.md?{"baseCommit":"196d8e6fdfa49f5ddc949ec44279f13036c70f25","headCommit":"3637dcbabd3dd5318aa874a732bcd06300515007","isBase":false,"fileName":"open-ssh-remote/README.md","prNumber":116,"status":3,"remoteName":"origin"} does not have an associated file system provider..

Extension version: 2021.4.37984
VS Code version: Code - Insiders 1.56.0-insider (19cda32aafccb88db45622e7ae9be90cb71c9744, 2021-04-27T17:44:21.786Z)
OS version: Darwin x64 20.3.0
Remote OS version: Linux x64 5.4.0-1043-azure
Remote OS version: Linux x64 5.4.0-1043-azure
Fetching remote diagnostics for 'Codespaces' failed: Canceled
Fetching remote diagnostics for 'Codespaces' failed: Canceled

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (0.25GB free)

Process Argv
--crash-reporter-id a2c1d522-e9f0-4e3f-b78a-9253f1c2d2d3

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: robfast-vnc

OS
Linux x64 5.4.0-1043-azure

CPUs
Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz (4 x 2095)

Memory (System)
15.64GB (3.13GB free)

VM
0%

Item
Value

Remote
SSH: robfast-vnc

OS
Linux x64 5.4.0-1043-azure

CPUs
Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz (4 x 2095)

Memory (System)
15.64GB (3.13GB free)

VM
0%

Fetching remote diagnostics for 'Codespaces' failed: Canceled
Fetching remote diagnostics for 'Codespaces' failed: Canceled

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvspyt639:30291487
pythontb:30258533
vspre833:30267464
pythonptprofiler:30281269
vsdfh931cf:30280410
vshan820:30294714
pythondataviewer:30285072
vscus158cf:30286554
vscgsv2ct:30286873
vscorehov:30294388

@lramos15 In my editor and diff-editor handler I need to check if the scheme of the given resource is supported by our file systems, so essentially have
if (!this._fileService.canHandleResource(resource)) {
    return undefined;
}

However, you don't allow we return undefined or anything that says "I actually don't handle this resource, it only looked like it at first"


nodepool drain before delete checkbox ui

need a checkbox for nodepools to add a drain before delete bool when create/edit of a nodepool. probably makes sense to put it on the clusters add page near the taints but ok with whatever works.

https://github.com/rancher/rancher/issues/27458

field added to v2.5 in this PR https://github.com/rancher/rancher/pull/31307

Verified this on

Verified this on :
master-head and v2.5-head versions:
Rancher | v2.5-a85f4d1f87feea0083ebf8ae517a140f39de7fbd-head
User Interface | v2.5-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher51

Rancher | master-dbf18389c36b56983c9848c1de1832faea2fc0a6-head
User Interface | vmaster-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher51
From the rancher ember UI, while creating node pools, enabled the option drain before delete while creating the cluster.
While editing the cluster, added disabled/enabled the drain before delete for all the pools.
While editing the cluster, created new node pools and the option [drain before delete checkbox] appears for the new pools.


s3 bucket name doesnt get substituted in the sam template output

s3 bucket name doesnt get substituted in the sam template output
Cli version
aws-cli/1.11.54 Python/3.4.4 Darwin/16.3.0 botocore/1.5.17
template:
LambdaFunction:
Type: AWS::Serverless::Function
Properties:
CodeUri: s3://<bucket>/auth.zip
Description: Lambda Function
Handler: index.handler
Runtime: nodejs4.3
Timeout: 30
I am packaging as below:
aws cloudformation package --template-file ips-v1.yaml --output-template-file ips-template-output-v1.yaml --s3-bucket test_bucket
In the output template it is:
AWSTemplateFormatVersion: '2010-09-09'
Description: Simple API Endpoint configured using Swagger specified inline and backed
by a Lambda function
Resources:
LambdaFunction:
Properties:
CodeUri: s3://<bucket>/auth.zip
Description: Lambda Function
Handler: index.handler
Runtime: nodejs4.3
Timeout: 30
Type: AWS::Serverless::Function
ipsApigw:

In template the CodeUri is a local path, not s3:// uri
From the man page:

   For example, if  your  AWS  Lambda  function  source  code  is  in  the
   /home/user/code/lambdafunction/    folder,    specify    ``    CodeUri:
   /home/user/code/lambdafunction``  for   the   AWS::Serverless::Function
   resource.  The  command  returns a template and replaces the local path
   with the S3 location: CodeUri: s3://mybucket/lambdafunction.zip.

I am running cloudformation package command through codebuild and it is referring code from s3 bucket what i need to do in this case.because in my case it aslo copying the same codeUri from previous template

same issue, it doesn't work. My template has:
Telephony.Service.API/Telephony.Service.API/serverless.template:         "CodeUri": "./Telephony.Service.API.zip"
(that file exists in Telephony.Service.API/Telephony.Service.API/  directory )
So my command is:
aws cloudformation package --template-file ./Telephony.Service.API/Telephony.Service.API/serverless.template --s3-bucket callconnect-dev-deployment --s3-prefix "test" --output-template-file /tmp/output-serverless.template
But, in /tmp/output-serverless.template  it is transformed to:
 Get:     Properties:       CodeUri: s3://callconnect-dev-deployment/test/cd6a69d250df7e596b7f1aa7e8df5daf

@miguelaustro if you look in your S3 bucket, you’ll notice that the file “cd6a69d250df7e596b7f1aa7e8df5daf” and “Telephony.Service.API.zip” are identical. The package command renames the original file to a hash of itself when uploading to S3.

@jarreds It's good if "sam package" command keep name 'Telephony.Service.API.zip' while upload to s3, instead of rename zip file.
Because each time I run "sam package", it will create another file in s3, I don't want that happen
Is there any way to specify zip name while run "sam package" to upload to s3?

@PhungXuanAnh It is actually meant to create another file in S3; see https://github.com/awslabs/serverless-application-model/issues/942#issuecomment-497794963


AttributeError: 'ScrapyPlaywrightDownloadHandler' object has no attribute 'contexts'

Hey there,
I wanted to try and get started with playwright, and what I did to start off was simply add the meta = {'playwright':True} arguments to the scrapy.Request in an already working spider.
However, now the spider immediately stops working and gives the error:
AttributeError: 'ScrapyPlaywrightDownloadHandler' object has no attribute 'contexts'
I already added the following lines to the settings.py of my script:
DOWNLOAD_HANDLERS = {
    "http": "scrapy_playwright.handler.ScrapyPlaywrightDownloadHandler",
    "https": "scrapy_playwright.handler.ScrapyPlaywrightDownloadHandler",
}

TWISTED_REACTOR = "twisted.internet.asyncioreactor.AsyncioSelectorReactor"

Full log:
2022-01-21 19:12:47 [scrapy.utils.signal] ERROR: Error caught on signal handler: <bound method DownloadHandlers._close of <scrapy.core.downloader.handlers.DownloadHandlers object at 0x7fcddf904220>>
Traceback (most recent call last):
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/twisted/internet/defer.py", line 1657, in _inlineCallbacks
    result = current_context.run(
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/twisted/python/failure.py", line 500, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/scrapy/core/downloader/handlers/__init__.py", line 81, in _close
    yield dh.close()
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/twisted/internet/defer.py", line 1657, in _inlineCallbacks
    result = current_context.run(
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/twisted/python/failure.py", line 500, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/scrapy_playwright/handler.py", line 146, in close
    yield deferred_from_coro(self._close())
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/twisted/internet/defer.py", line 1031, in adapt
    extracted = result.result()
  File "/home/jeroen/anaconda3/envs/scratch/lib/python3.8/site-packages/scrapy_playwright/handler.py", line 149, in _close
    self.contexts.clear()
AttributeError: 'ScrapyPlaywrightDownloadHandler' object has no attribute 'contexts'

Seems something is wrong with my setup, anyone got an idea where the issue lies?

Have you tried to install python requirements?
playwright
scrapy-playwright
Scrapy

And then run in the terminal
playwright install

Some useful linkes:

scrapy-playwright examples
scrapy-playwright in Docker

I had only installed the python requirements, but I forgot to run playwright install in console. Thanks for the support.

Seems resolved, thanks for the intervention @b5y 🙌

This is most likely caused by a previous exception preventing the handler from being initialized successfully, causing the closing method to fail because the contexts attribute was not set. The actual exception happened before (in this case it was probably the fact that playwright was not installed), but this message is still confusing. Hopefully it would not be a problem after 023b35d3a9b2c8570580dca743d3292d943c8217.


Issue with k8s.io/ja/docs/tutorials/kubernetes-basics/scale/scale-intro/

fixes #15150

/lgtm

/approve


Issue294 ds citation

Summary: closes #294
Related issue:
Suggested reviewer(s):
Reviewer checklist:

[ ] The headers of all files contain a reference to the repository license (i.e., "License: This file is part of py-mmd-tools, licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0)")
[ ] 100% test coverage of new code - meaning:

[ ] The overall test coverage increased or remained the same as before
[ ] Every function is accompanied with a test suite
[ ] Tests are both positive (testing that the function work as intended with valid data) and negative (testing that the function behaves as expected with invalid data, e.g., that correct exceptions are thrown)
[ ] Functions with optional arguments have separate tests for all options

[ ] Examples are supported by doctests
[ ] All tests are passing
[ ] All names (e.g., files, classes, functions, variables) are explicit
[ ] Documentation (as docstrings) is complete and understandable

The checklist is based on the S-ENDA conventions and definition of done (see https://s-enda-documentation.readthedocs.io/en/latest/general_conventions.html). The above points are not necessarily relevant to all contributions. In that case, please add a short explanation to help the reviewer.

@Teddy-1000 - den er grei. Nå er det merget fra master, så hvis du godkjenner så kan vi lukke denne :)


[Bug]:

Is this a Bug?

[X] I have confirmed that I want to report a Bug

Has this issue been reported before?

[X] I have confirmed that this Issue has not been reported before

Alova Version
3.2.3
Framework
React
Problem Description
When using useRequest with immediate true and initial data, if the resource was previously loaded and we have data on the cache, the initial data will flash on the screen first for a split second before the cache is properly loaded into the component. Note that due to data being found on the cache. The loading state is also false during this whole process.
Screencast from 2024-11-23 20-32-32.webm
The initial data is shown for a small time, breaking the layout.

Expected Behavior
When using useRequest with immediate true and initial data, if the resource was previously loaded and we have data on the cache, the initial data should be replaced by the cached data on initialization of the useRequest call
Reproduction Link
No response
Reproduction Steps

Have a page that calls a resource setup with alova.Get, a any positive cacheTime, initialData and immediate:true
 const { loading, data } = useRequest(getWebflowCollectionsItems, {  initialData() {    const resources = []    for (let i = 0; i < 12; i++) {      resources.push({        id: i,        slug: 'dummy-data',        title: 'Dummy Title',        body: '
Best Ways To Tap Your Home Equity
',        mainImage: 'https://source.unsplash.com/random',        thumbnailImage: 'https://source.unsplash.com/random',      })    }    return resources  },  immediate: true, })

Load the page, render the endpoint data into the page, then navigate away, when navigating back, the state of the page will show the dummy data for a small fraction of time before loading the cache data to the state

System Information
No response
Additional Information
I downloaded the source code and I think i got a solution for this already, with updated unit tests.  This of course may not be the correct approach, but I think the tests will illustrate the error.
https://github.com/alovajs/alova/compare/main...vlaem:alova:replace-initial-data-with-cache-when-hit

We have noticed this issue and currently we are discussing whether it is a bug.

Great, thanks for taking time looking into it.
One more thing, if this IS the expected behavior, then the loading state should start as true when there is a cache hit on initialization as to allow us developers to hide the data with our custom loading state.
In the video I actually have setup skeleton loaders on top of the cards generated by the dummy data, but when navigating back to the page the loading state stays as false and the dummy data is shown for a bit. Either have it start with the cache data or start with loading = true until the cache is loaded would be good options imo.


Top Bar Display Issue

The top bar (or whatever the element in my image is called) is not displaying correctly when using this custom CSS. I’ve tested it without any CSS and with other styles, and it displays correctly in those cases.

@refact0r most likely has to fix this themself as discord updated their design and this might require a design change as well. The way it worked before was by discord splitting the toolbar and search like with server member lists, but now that they've gone back on that and kept the header the same no matter if you have the profile open or not, it won't move automatically anymore and split.

same here


RHEL 7. Calico services aren't restarted after exception.

e.g. calico-felix hit an exception when the connection with the plugin timed out (issue tracked elsewhere). The service was not restarted.

This was fixed when we moved to systemd (RHEL7) and upstart (RHEL6).


Widget lost context during second execution

Hi, I discovered a bug on the widget. I'm using the widget to put my buttons, grouped together inside a table, and put it on a template grid. When I first execute the microflow, the parameter (grid object) exists and I can successfully execute my microflow. But upon second execution, the microflow's parameter is missing. So the microflow can only be executed once after the widget is created. Can anyone investigate this further? I am using Modeler 7.10.0.

We have also hit an issue when using the DropdownDivConverter inside a Template Grid.  In our case it seems to be passing the wrong object altogether into the microflow, in certain circumstances.


Crash on accessing navigation block in advanced rocketry, while rocket is built.

Mod Version:
DynamicSurroundings-1.12.2-<IP_ADDRESS>.jar
Forge Version:
forge-<IP_ADDRESS>47
Link to client log:
ahh, don't have it.
Link to crash log:
I get this:
https://hastebin.com/odusefazox.rb
followed by half a dozen of this:
https://hastebin.com/ubogudolom.rb
before the client actually quits.  i think the multiple crashes is 'VanillaFix' trying to let us continue after the first exception.
Description:
Advanced Rocketry has a block called the Navigation Computer that you add to a rocket.  when the rocket is built, you can enter the rocket, hit 'c' to open the rockets gui, which brings up a panel with 2 squares with blocks in them, one is the station bay, and the other is the navigation computer.  if you click the nav computer, the client crashes.
In the case of crashes, it is good to know things like the following:

Did you just add the mod to a pack? no
Did it just start crashing, or has it always crashed? always crash, every time.
Did you update any other mods in your pack and it started crashing?  has been happening since adv rocketry was added to the pack, as before, we couldn't build a rocket and try to access the nav computer.
If updating multiple mods did you update one by one or all at once?  To help narrow the problem down adding one by one is helpful.
Is the modpack you are using available online somewhere?  MC Eternal version <IP_ADDRESS> (also happened in 1.3.7 and 1.3.6 i think, since they added adv. rocketry to the pack)

Yeah - something is in a bad state where the player information in the Minecraft world is missing.  Not sure what the cause is.  I am adding defensive code to protect DS.

Posted <IP_ADDRESS> to CurseForge as BETA.  MixinBoostrap will also need to be installed.


[GH-#356] Adeed target to difficulty calculation

Resolves #356

@thepiwo This is just the maximum target represented in integer(not scientific). We wouldn't need it in the validation.


Cargo logo in svg

Hi, I'm one of the core maintainers of vscode-icons and I'm willing to add support for Cargo #1367.
The thing is that it would be awesome if you could provide a svg version of your logo for us to use it as an icon for Cargo.lock file.

Unfortunately I'm not sure we have one right now -- https://users.rust-lang.org/t/hi-res-cargo-icon/10733/5

@alexcrichton, do you have access to the source file (.ai, .psd or whatever)?

Unfortunately I don't personally have access (unsure if anyone does)

@wycats or @wifelette maybe?

Ask and you shall receive 😄
Cargo.zip

Thanks @wifelette. I've tried to export this as svg but the result is not near acceptable. I'll try it again when I have more time. By the way, if you happen to excel at psd to svg your help will be really appreciated 😉
Thanks to everyone!

@wifelette @robertohuertasm I can give it a try since I've become pretty good at converting PNG to SVG. I can even try to make an SVG version myself. It will take some time but I think we can do it.

@JimiC, there's no need. I've already got a pretty decent version.

Thanks again for your support. Hopefully we'll be having Cargo icons for vscode in our next week release.

Heres a higher fidelity SVG. Still needs some improvements:
Texturise the bottom wood.
Better morphing of the rust logo.


[Feature]: Appsmith app should be able to listen to messages sent from the parent webpage

When appsmith is embedded as an iframe, listen to messages from parent window.
JS equivalent -> window.addEventListener('message', (ev) => {}).
Method signature

Subscriptions to be unsubscribed:

On page change, because the callback can have references to entities from that page
On app switch/exit, because we want to restrict listening to app's only.

subscribeParentMessages

subscribeParentMessages(
	"https://eco-monk.github.io",
	(message) => { showAlert(message) }
)

unsubscribeParentMessages

unsubscribeParentMessages("https://eco-monk.github.io")

Todo:

[x] decide on UI (Discussed: this will be handled purely in code for now) @kocharrahul7 @RoopKrrish9696
[x] investigate and handle security concerns (we're good with adding domain checks)
[x] handle page switch unsubscribe
[x] unsubscribe and subscribe -> params remain the same
[x] No action creator -> since it's not a widely used method

This seems to be related to Issue#12953 @rimildeyjsr Can you confirm the status of this feature?

I'd be happy to set up a $200 bounty for this feature, if anyone wants to build it!

Adding isParentMessageSuscriptionActive method had to be handled differently.
This possibly has to be a global method, because the existing ActionTriggers logic doesn't support returning values.
This means subscriptionsMap is to be maintained between main thread and worker thread.
And needs to be kept in sync.

I'd be happy to set up a $200 bounty for this feature, if anyone wants to build it!
Seems progress of this feature is slow, will you pay that to accelerate? 😂

Actually just want to understand when is feature will be released in estimation

why was this closed as completed? Any indications on how it was implemented? I can see all PR's ended up close because of inactivity (nobody approved them)


No issue, just wanted to say thanks!

After the let down that was terminal-plus, and the buggy follow up that was platformio, I was relieved to find your fork that solved not one but ALL of my lingering issues. Kudos and many, many thanks!

Thanks mate! :smile:


Error in G4FLLM._call: Aichat is not working

I get
Error in G4FLLM._call: Aichat is not working, trying 1 of 5
Error in G4FLLM._call: Aichat is not working, trying 2 of 5
Error in G4FLLM._call: Aichat is not working, trying 3 of 5
Error in G4FLLM._call: Aichat is not working, trying 4 of 5
Error in G4FLLM._call: Aichat is not working, trying 5 of 5

Lol just as I expected, nothing comes free!!!


fix: add box-sizing, padding, margin to reset

fix: add box-sizing, padding, margin to reset

Obligatory GIF (super important!)

:hammer_and_wrench: Type Of Change

These types will increment the version number on release:

[x] Fix

:book: Description
https://dialpad.atlassian.net/browse/DLT-1633
Added box-sizing: border-box, padding 0 and margin 0 to our reset
:bulb: Context
Finding a lot of spacing inconsistencies between DP1, DP2, and even our storybook. Found that DP1 has margin / padding 0 set on all elements which overrides the default user agent padding/margin. Our storybook and DP2 don't have this set, causing the spacing issues.
Set box-sizing: border-box as well since that's another one we should probably have.
:pencil: Checklist

For all PRs:

[x] I have ensured no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] I have reviewed my changes.

seems to be one spacing issue with the feed item pill after reviewing the visual tests.. looking into.


[Question] Grouping polygons between frames

Hi,
I understand that there's a feature waiting to be released for tracking polygons between frames, similarly to tracking boxes.
I there a way in the mean time to annotate two polygons from two adjacent frames as the same object (i.e. group id)?
Thanks

Hi, I have some detections which are in PASCAL VOC format. These detections correspond to every 10th frame in a video. I'd like to merge them using the interpolation mode. When I try uploading the annotation, the boxes are in "annotation mode" and hence are not being interpolated. Could you kindly help me out on how to change the type from annotation to interpolation?
Thank you!


Custom GitHub action to generate build matrix

We currently have three job configurations for checks, tests, and hunspell regression tests.
The configuration (or build matrix - i.e. target OS, JVM, etc.) can be set in a custom action's outputs instead of hard-coded literals in each job.
The downside is the increased complexity of the workflow definition. I'm not fully sure if the outcome is worth that - I will wait for feedback from others who are interested.
With a custom action, a more complex matrix (e.g., randomizing job configuration on each run) can possibly be generated; I haven't tried.

Hi @mocobeta . This looks impressive that it can be done! I kind of like the verbose version because then you can tell what's going on, whereas the custom action is much more difficult to understand at first glance. I'm fine with committing this in, just observing the fact.

I didn't explain the implementation so it might be hard to figure out what's happening here at the first glance; the matrix value is propagated from the custom action to each job (somewhat like Unix pipe) by the combination of several built-in functions. I'd just like to leave the references to them.

set-output shell command
composite action outputs
job outputs
needs context
fromJson expression

This is a kind of exercise to see how the Actions runner works to me, but we wouldn't need it unless we have a lot more jobs to run.


bugfix/send props to google

Bugfix: Save props (headers) when setting and add to the Google request

@abdolence This makes a) sure that all props are send as header and b) the props throw an exception when called after connected == true

I've created this PR instead.
https://github.com/abdolence/sbt-gcs-resolver/pull/9
Please have a look if this is something you are after.
The reasons:

Support all of the ops, not just put
Having a Map[] of ready to use HTTP headers instead
Using foreach instead of fold to show it has side effects
Not to reimplement setRequestProperty

Sorry, I somehow missed the comments. Else I would have responded. I think there might be a problem with your suggestions, but I'll check the other pr


Remove SlicedStream

Exposing new properties on Stream is bad practice. Refactored AbsolutePosition off of streams in PartitionedUploader and it turned out the extra tracking of the value wasn't needed at all, so I removed the abstract class entirely.

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


Error on live app

requests.exceptions.ConnectionError: This app has encountered an error. The original error message is redacted to prevent data leaks. Full error details have been recorded in the logs (if you're on Streamlit Cloud, click on 'Manage app' in the lower right of your app).

Yep, I need to remove that share link as I can't figure out how to run a FastAPI server in Streamlit Cloud. That's what's causing the error. Try cloning and running it locally instead. Cheers.

I've given up on getting FastAPI running in Streamlit Cloud. See st-media-service instead for a non-FastAPI version of this app which does deploy to Streamlit Cloud.


App crashes when refreshing on no Internet connection

App crashes when refreshing on no Internet connection

NOTICE: this happens only sometimes

Can you provide a log of this please?
On 08-Dec-2015 02:17, "Michał Rokita"<EMAIL_ADDRESS>wrote:

NOTICE: this happens only sometimes
—
Reply to this email directly or view it on GitHub
https://github.com/fossasia/open-event-android/issues/88#issuecomment-162656986
.

@mRokita Can you please provide a log because I am not able to recreate this bug.

Yes application get crashed on offline mode several times, log is attached below!
Uploading logcat.txt…

Yes I also found that application get crashed several times in the offline mode, below I attached the log file with errors which causing this issue.
logcat.txt

I want to fix this. @mananwason

@mananwason I have fixed it please check my pull request.
https://github.com/fossasia/open-event-android/pull/119

#120

Merged #120


Feature request: add HTTP support

I'd love to work on the implementation of HTTP support. I will try to maintain the same approach and interface (where possible) as the existing ICMP one.
CC: @SuperQ @davinci26 @shadialtarsha

@SuperQ I guess we can close this issue as it was merged


Allow partial deployments when sources are missing locally

WHY are these changes introduced?
Fixes https://github.com/Shopify/internal-cli-foundations/issues/384
WHAT is this pull request doing?

Always ask for confirmation before deploying (user can provide --force to skip the confirmation prompt)
Relax constraints so that the deploy can proceed even if an extension (or function) is missing locally
Use new ink-powered prompts to display a summary for the user

How to test your changes?

create a new app: pnpm create-app --path ~/Desktop
cd into app and create an extension pnpm generate extension
open a new terminal side by side, go into the CLI folder and run pnpm shopify app deploy --path ~/Desktop/new-app
you should see the confirmation prompt that you want to create a new extension
type n to cancel
run pnpm shopify app deploy --path ~/Desktop/new-app --force to deploy without any prompts
in the app terminal, create a new extension pnpm generate extension
in the CLI terminal,  and run pnpm shopify app deploy --path ~/Desktop/new-app
you should see the prompt that you want to create a new extension and update an existing extension
type 'y' to proceed
in the app terminal, delete one of the extensions
in the CLI terminal,  run pnpm shopify app deploy --path ~/Desktop/new-app
you should see the prompt that you want to update an extension and that another extension is missing locally

Post-release steps

Coordinate with @shainaraskas for documentation changes

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

@Arkham did you coordinate with @shainaraskas for doc changes? I'm going to remove the post-release-steps label.

I forgot, thanks for reminding me! Just opened this one: https://github.com/Shopify/shopify-dev/pull/30167


Chat Emoji Causes Borking

On Mac, open the character viewer with command-control-space and enter non standard characters. Its easy to bork chat by entering them.

@jashot7 Is there a specific emoji you are using to cause this? I've tried a bunch of them (including some seemingly obscure ones) and I can't reproduce this.
@morebrownies Fellow OSser, does this happen for you?

i haven't found one that does it

We determined that this bug wasn't related to chat emojis, I'm going to close it until we can reproduce it and/or figure out what it was.


[CELEBORN-267] reuse stream when client channel reconnected (#1200)

What changes were proposed in this pull request?
Cherry-picked from main.
Reuse the stream when channel inactive while fetching trunk.
Why are the changes needed?
Stream will be removed when channel inactive while fetching trunk, so even if the client is reconnected, fetch trunk would not success and then client will retry other peer reader for same partition location. We can reuse the stream when client is reconnected to avoid this.
Does this PR introduce any user-facing change?
No
How was this patch tested?
random kill workers & worker high-pressure test

ping @RexXiong

Manually tested.


Fix form buttons

Fix form remove button

i still get
aurelia-logging-console.js:54 ERROR [aurelia-form] an element key propery cannot be null or undefined
though only once now since one button vanished.

This PR can be closed. It has been fixed in aurelia-form
https://github.com/SpoonX/aurelia-form/pull/56
Just need to be merged and then we can update swan-example-client with the latest version of aurelia-form


Migrate views to Webpack

Todo:

[x] Fix topsort alias which currently breaks the digitaljs viewer
[x] Look into merging tsconfigs(?)

[ ] Related: look into merging common code between views

closes #11

I decided to look into this again and managed to fix the topsort issue, so this is finally ready. The views are now located under src/views instead of views/.
All views have now have a shared index.html, vscode.ts and typescript config. I don't think it's a good idea to merge the TS config with our main one; Vue requires some options such as "skipLibCheck": true and "moduleResolution": "bundler", which might not be desirable in the extension itself.
In the near future we might need to share some code with the extension itself; that's not possible with the current setup due to where the tsconfig is placed, but it's likely possible by putting both in the project root and specifying the correct file in the webpack config. But I think it's better to leave that out for now and deal with it when it becomes necessary.


Handle sigint sigterm

We should support graceful shutdown

Instead of process.exit starting back from the start you mean? Not relying on the process restarting itself?

it's mostly for gcp, when a server is terminating you have a grace period to shutdown your process.
if you don't, after 30s, the process is killed and you might have been in the middle of processing something that could corrupt your data.
In our scenario we could have processed a package but not saved it, not critical.
It also helps terminating the process faster than waiting the full grace period


Fix misc. WOCCatalog breaks in Xcode

Various (small) fixes to parts of WOCCatalog when built for iOS

@bdrlamb is added to the review. #Closed

@oliversa-msft is added to the review. #Closed

@davelamb is added to the review. #Closed

:clock1:

:shipit:

:shipit:

Thanks for your contribution.


feat(core): add v6 migration guide

I tried to add a migration guide for v6. I'm not sure if the fieldChanges change is a breaking change.
@aitboudad if someone relied on #1901 they could mitigate it with extending the formGroup and formArray and setting the defaultValue, correct?

if someone relied on #1901 they could mitigate it with extending the formGroup and formArray and setting the defaultValue, correct?

correct and better to mention it in the upgrade!

Thank you @manuelmeister!


drop support for Ruby 1.9

Coverage remained the same at 100.0% when pulling 9534daa305540c2d9c0518081480d1349f108e08 on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.

Coverage remained the same at 100.0% when pulling 58ddceff0f898b9c360f7ce0e3425c46350b6037 on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.

Coverage remained the same at 100.0% when pulling 11b1500141e26a2154686046902e539a1f7c2fe1 on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.

Coverage remained the same at 100.0% when pulling c80e21665df33d7344a23377c907b230367c7dac on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.

Coverage remained the same at 100.0% when pulling 0456c162f2b5391d075dc30e0eec4c1090b05a1b on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.

Coverage remained the same at 100.0% when pulling 0456c162f2b5391d075dc30e0eec4c1090b05a1b on fix-ci into a8aad39d60cd4856065a1c686571269135cd8feb on master.


Move docker system information to a dedicated router and backend.

Because I like the name system better than local :)
This leave us only with the image backend to refactor. But we need to wait until #18347 is merged before doing that.
Signed-off-by: David Calavera<EMAIL_ADDRESS>

Agree on waiting for #18347. Agree on this split of 'systemy' functions into separate router. I can see what's left is 'imagey' functions + build.

LGTM! so clean (just a curiosity)

LGTM


Ruby LSP keeps hanging on save

Description
Ruby LSP Information
Ruby LSP Information
VS Code Version
1.95.2
Ruby LSP Extension Version
0.8.13
Ruby LSP Server Version
0.21.3
Ruby LSP Addons

Ruby LSP Rails

Ruby Version
3.1.2
Ruby Version Manager
none
Installed Extensions

Click to expand

code-spell-checker (3.0.1)
color-highlight (2.8.0)
even-better-toml (0.19.2)
gitlens (15.6.3)
prettier-vscode (11.0.0)
rails (0.22.0)
ruby-lsp (0.8.13)
solargraph (0.24.1)
stimulus-lsp (1.0.4)
vscode-eslint (3.0.10)
vscode-tailwindcss (0.12.12)
vscode-versionlens (1.14.3)
vscode-zipfs (3.0.0)

Ruby LSP Settings

Click to expand
Workspace
{}

User
{
  "enableExperimentalFeatures": false,
  "enabledFeatures": {
    "codeActions": true,
    "diagnostics": true,
    "documentHighlights": true,
    "documentLink": true,
    "documentSymbols": true,
    "foldingRanges": true,
    "formatting": true,
    "hover": true,
    "inlayHint": true,
    "onTypeFormatting": true,
    "selectionRanges": true,
    "semanticHighlighting": true,
    "completion": true,
    "codeLens": true,
    "definition": true,
    "workspaceSymbol": true,
    "signatureHelp": true,
    "typeHierarchy": true
  },
  "featuresConfiguration": {},
  "addonSettings": {},
  "rubyVersionManager": {
    "identifier": "none"
  },
  "customRubyCommand": "",
  "formatter": "auto",
  "linters": null,
  "bundleGemfile": "",
  "testTimeout": 30,
  "branch": "",
  "pullDiagnosticsOn": "both",
  "useBundlerCompose": false,
  "bypassTypechecker": false,
  "rubyExecutablePath": "",
  "indexing": {},
  "erbSupport": true,
  "useLauncher": false,
  "featureFlags": {}
}

Reproduction steps

Start the Ruby LSP using VSCode
Open a Ruby file
Make a change
Save

From this moment forward, it can no longer format files, and is perpetually stuck. LSP Stop sometimes works, sometimes doesn't. Disabling the extension makes saving possible again.
Code snippet or error message
2024-11-10 14:51:08.955 [info] (kaboom) -- check_all_pending!()

2024-11-10 14:51:09.061 [info] (kaboom) Request  failed:

2024-11-10 14:51:09.063 [info] (kaboom) /usr/share/rubygems-integration/all/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:928:in `block in method_missing': undefined method `check_all_pending!' for #<ActiveRecord::Migration:0x00007f48a7575cc8 @name="ActiveRecord::Migration", @version=nil, @connection=nil> (NoMethodError)

This was fixed in https://github.com/Shopify/ruby-lsp-rails/pull/513. Updating to the latest version of the gem should solve it for you.

The problem is that the plugin tries to "augment" the gemfile to install the dependency instead of installing the dependency and then bundle install --local, meaning that this setup does not work with 100% vendored or system (debian) packages.

Before a manual intervention
2024-11-12 18:32:28.469 [info] (kaboom) Running command: `ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM::YJIT), version: RUBY_VERSION, gemPath: Gem.path }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'` in /home/derk-jan/kaboom using shell: /bin/bash
2024-11-12 18:32:32.409 [info] (kaboom) Ruby LSP> Skipping custom bundle setup since /home/derk-jan/kaboom/.ruby-lsp/Gemfile.lock already exists and is up to date

2024-11-12 18:32:32.780 [info] (kaboom) Ruby LSP> Running bundle install for the custom bundle. This may take a while...
Ruby LSP> Command: (bundle _2.3.15_ check || bundle _2.3.15_ install) 1>&2

2024-11-12 18:32:33.390 [info] (kaboom) [DEPRECATED] This Gemfile does not include an explicit global source. Not using an explicit global source may result in a different lockfile being generated depending on the gems you have installed locally before bundler is run. Instead, define a global source in your Gemfile like this: source "https://rubygems.org".

2024-11-12 18:32:33.989 [info] (kaboom) The Gemfile's dependencies are satisfied

2024-11-12 18:32:41.855 [info] (kaboom) Initializing Ruby LSP v0.21.3...
2024-11-12 18:32:41.912 [info] (kaboom) Auto detected formatter: rubocop
2024-11-12 18:32:41.913 [info] (kaboom) Auto detected linters: rubocop
2024-11-12 18:32:41.913 [info] (kaboom) Detected test library: rails
2024-11-12 18:32:41.913 [info] (kaboom) Finished initializing Ruby LSP!
2024-11-12 18:32:43.386 [info] (kaboom) Activating Ruby LSP Rails add-on v0.3.23
2024-11-12 18:32:43.397 [info] (kaboom) Ruby LSP Rails booting server
2024-11-12 18:32:54.911 [info] (kaboom) Finished booting Ruby LSP Rails server
2024-11-12 18:32:54.930 [info] (kaboom) -- check_all_pending!()

2024-11-12 18:32:55.091 [info] (kaboom) Request  failed:

The [DEPRECATED] message in the log is actually a bug in bundler itself, which has since been patches, but without it I would not have been able to quickly identify it.
Installing these gems manually:
gem install ruby-lsp ruby-lsp-rails

Now it works
2024-11-12 18:37:00.741 [info] (kaboom) Running command: `ruby -W0 -rjson -e 'STDERR.print("RUBY_LSP_ACTIVATION_SEPARATOR" + { env: ENV.to_h, yjit: !!defined?(RubyVM::YJIT), version: RUBY_VERSION, gemPath: Gem.path }.to_json + "RUBY_LSP_ACTIVATION_SEPARATOR")'` in /home/derk-jan/kaboom using shell: /bin/bash
2024-11-12 18:37:00.955 [info] (kaboom) [Error - 6:37:00 PM] Server process exited with code 0.
2024-11-12 18:37:03.999 [info] (kaboom) Ruby LSP> Running bundle install for the custom bundle. This may take a while...
Ruby LSP> Command: (bundle _2.3.15_ check || bundle _2.3.15_ install) 1>&2

2024-11-12 18:37:04.591 [info] (kaboom) [DEPRECATED] This Gemfile does not include an explicit global source. Not using an explicit global source may result in a different lockfile being generated depending on the gems you have installed locally before bundler is run. Instead, define a global source in your Gemfile like this: source "https://rubygems.org".

2024-11-12 18:37:05.578 [info] (kaboom) Resolving dependencies...
2024-11-12 18:37:05.908 [info] (kaboom) .
2024-11-12 18:37:06.037 [info] (kaboom) .
2024-11-12 18:37:06.249 [info] (kaboom)

2024-11-12 18:37:06.352 [info] (kaboom) The Gemfile's dependencies are satisfied

2024-11-12 18:37:11.786 [info] (kaboom) Initializing Ruby LSP v0.21.3...
2024-11-12 18:37:11.802 [info] (kaboom) Auto detected formatter: rubocop
2024-11-12 18:37:11.802 [info] (kaboom) Auto detected linters: rubocop
2024-11-12 18:37:11.802 [info] (kaboom) Detected test library: rails
2024-11-12 18:37:11.802 [info] (kaboom) Finished initializing Ruby LSP!
2024-11-12 18:37:12.957 [info] (kaboom) Activating Ruby LSP Rails add-on v0.3.26
2024-11-12 18:37:12.961 [info] (kaboom) Ruby LSP Rails booting server
2024-11-12 18:37:21.976 [info] (kaboom) Finished booting Ruby LSP Rails server

Since the error message is no longer showing at the bottom, and I can run server stop and start without error, I will close this issue, but this means that auto install and update is completely broken for this setup @andyw8


Bootstrap.css Unexpected character '@'

Hi,
Iam trying to use bootstrap-css-only with webpack. Here is my config
var webpack = require('webpack');

module.exports = {
  context: __dirname + '/src',
  entry: {
    app: './app.js',
    vendor: ['angular', 'angular-ui-router', 'jquery', 'bootstrap-only-css']
  },
  devtool: 'source-map',
  output: {
    path: __dirname + '/js',
    filename: 'app.bundle.js'
  },
  module:{
    loaders: [
      {
        test: /\.scss$/,
        loader: "style!css!sass",
        exclude: /node_modules/
    },
      {
        test: /\.(woff|woff2)(\?v=\d+\.\d+\.\d+)?$/,
        loader: 'url?limit=10000&mimetype=application/font-woff'
      },
      {
        test: /\.ttf(\?v=\d+\.\d+\.\d+)?$/,
        loader: 'url?limit=10000&mimetype=application/octet-stream'
      },
      {
        test: /\.eot(\?v=\d+\.\d+\.\d+)?$/,
        loader: 'file'
      },
      {
        test: /\.svg(\?v=\d+\.\d+\.\d+)?$/,
        loader: 'url?limit=10000&mimetype=image/svg+xml'
      }
    ],
  },
  plugins: [
    new webpack.optimize.CommonsChunkPlugin("vendor", "vendor.bundle.js"),
    new webpack.ProvidePlugin({
      $: "jquery",
      jQuery: "jquery",
      moment: "moment"
    })
  ]
};

but the build always shows the error

28% 3/10 build modulesModuleParseError: Module parse failed: /node_modules/bootstrap-only-css/dist/bootstrap.css Unexpected character '@' (1:0)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected character '@' (1:0)

Do I need to add any other loaders to solve this issue?

@hrishikeshqb Not sure if this is actually part of the problem, but the first thing I notice is that your config has "bootstrap-only-css", while the name of the package is "bootstrap-css-only".
I'm definitely not a webpack expert, but according to this webpack issue, it looks like you may need something else?

@fyockm Thanks for the heads up man and excuse me for the late reply.
Changed the package name and ran into another set of errors while building

node_modules/bootstrap-css-only/css/bootstrap.min.css Unexpected token (5:83)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (5:83)

Also following up the issue you just mentioned. Modified my config as follows
var webpack = require('webpack');
module.exports = {
  context: __dirname + '/src',
 entry: {
app: './app.js',
vendor: ['angular', 'angular-ui-router', 'angular-bootstrap-calendar', 'bootstrap-css-only']
},
output: {
path: __dirname + '/js',
filename: 'app.bundle.js'
},
module:{
loaders: [
{
test: /\.scss$/,
loader: "style!css!sass",
},
{ test: /\.(png|woff|woff2|eot|ttf|svg)$/, loader: 'url-loader?limit=100000' }
],
},
plugins: [
new webpack.optimize.CommonsChunkPlugin("vendor", "vendor.bundle.js")
]
};

@fyockm I was in short of a css-loader to handle all the css files. I guess that fixed the issue.  Here is my array of loaders
 loaders: [
{         test: /\.scss$/,         loader: "style!css!sass",       },
{         test: /\.css$/,         loader: "style!css",       },
{ test: /\.(png|woff|woff2|eot|ttf|svg)$/, loader: 'url-loader?limit=100000' }     ]
Hence closing the issue, thanks again @fyockm!

@hrishikeshqb glad you got it figured out! sorry I wasn't able to offer more help.


Write pipeline with abstract elements (review with Kenneth?)

Look at Kenneth's PR
Figure out how best to construct it


Updating zha sensor took longer than the scheduled update interval

Home Assistant release with the issue:
0.76.0b5
Last working Home Assistant release (if known):
none
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu, Python 3.6 venv
Component/platform:
sensor.zha
Description of problem:
Since adding my Xiaomi temperature and humidity sensors, I'm continuously getting errors in the log that Updating the zha sensor took longer than the scheduled update interval. I added these sensors around HA version 0.73. The weird part is it doesn't always happen. Occasionally I'll restart Home Assistant and won't see these errors for a day or two. But more often than not I start getting them as soon as Home Assistant restarts and can't get rid of them.
This also seems to affect turning on/off other zha switch and light entities, but there are no warnings in the logs related to zha switches or lights, only zha sensor.
2018-08-16 22:11:22 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
2018-08-16 22:11:53 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
2018-08-16 22:12:24 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30
2018-08-16 22:12:55 WARNING (MainThread) [homeassistant.components.sensor] Updating zha sensor took longer than the scheduled update interval 0:00:30

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zha:
  usb_path: /dev/zigbee
  database_path: /home/hass/zigbee.db
  device_config:
    00:22:a3:00:00:20:ce:42-1:
      type: light
    00:22:a3:00:00:20:db:24-1:
      type: light

Traceback (if applicable):
N/A

Additional information:
N/A

Totally forgot that I'm running a newer commit of zigpy than what's on PyPi. Did some more testing and the sensor errors look to be related to this commit in zigpy. If I back the requirement to the commit before it, the sensors seem to work fine.
https://github.com/zigpy/zigpy/commit/17fa7fda455b41b72c8ffa25659706329fc79ed5

I added a bunch of debug log statements to the zha component to try tracing down why it seems to be tripping up when I upgrade zigpy to the above commit, and of course after adding the debug statements, I can't reproduce the problem anymore. I'm going to keep messing around with it for a while longer and see if I can get the errors to pop back up and trace it down.

It's been 2 weeks and a couple HA version bumps and I have yet to see the error come back, so I'm going to go ahead and close this. If it comes back I know where to add debugging statements to try and track it down.


install failure

Describe the bug
Extension impossible to install on the latest version comfyUI
To Reproduce
Please attach a workflow file to make it easier for others to reproduce the error!
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Error in console:
[Crystools INFO] Crystools version: 1.11.0
Traceback (most recent call last):
File "C:\Users\Playg\Desktop\ComfyUI\nodes.py", line 1888, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Crystools_init.py", line 18, in
from .nodes.image import CImagePreviewFromImage, CImageLoadWithMetadata, CImageGetResolution, CImagePreviewFromMetadata,
File "C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Crystools\nodes\image.py", line 11, in
from PIL.ExifTags import TAGS, GPSTAGS, IFD
ImportError: cannot import name 'IFD' from 'PIL.ExifTags' (C:\Users\Playg\Desktop\ComfyUI\venv\lib\site-packages\PIL\ExifTags.py)
Cannot import C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Crystools module for custom nodes: cannot import name 'IFD' from 'PIL.ExifTags' (C:\Users\Playg\Desktop\ComfyUI\venv\lib\site-packages\PIL\ExifTags.py)
Loading: ComfyUI-Impact-Pack (V4.83.6)
Loading: ComfyUI-Impact-Pack (Subpack: V0.4)
Loading: ComfyUI-Manager (V2.10.2)
[Impact Pack] Wildcards loading done.
ComfyUI Revision: 2070 [b1a16d45] | Released on '2024-03-18'
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/alter-list.json[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/model-list.json[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json
[ComfyUI-Manager] default cache updated: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/extension-node-map.json
no module 'xformers'. Processing without...
no module 'xformers'. Processing without...
[rgthree] Loaded 34 fantastic nodes.
[rgthree] Will use rgthree's optimized recursive execution.
Import times for custom nodes:
0.0 seconds: C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Crystools-save
0.0 seconds: C:\Users\Playg\Desktop\ComfyUI\custom_nodes\rgthree-comfy
0.1 seconds (IMPORT FAILED): C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Crystools
0.2 seconds: C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Manager
0.5 seconds: C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-Impact-Pack
1.0 seconds: C:\Users\Playg\Desktop\ComfyUI\custom_nodes\ComfyUI-SUPIR
Starting server
To see the GUI go to: http://<IP_ADDRESS>:8188
Versions:
Copy the output of the console (4 parts), like this:
** Python version: 3.10.11 (tags/v3.10.11:7d4cc5a, Apr  5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]

Total VRAM 12287 MB, total RAM 130996 MB
Set vram state to: NORMAL_VRAM

[Crystools INFO] Crystools version: 1.9.2
[Crystools INFO] CPU: AMD Ryzen 9 5950X 16-Core Processor - Arch: AMD64 - OS: Windows 10
[Crystools INFO] GPU/s:
[Crystools INFO] 0) NVIDIA GeForce RTX 3080 Ti
[Crystools INFO] NVIDIA Driver: 546.33

### Loading: ComfyUI-Manager (V1.25.3)
### ComfyUI Revision: 1886 [6a10640f] | Released on '2024-01-08'

Additional context
Add any other context about the problem here.

nvm, issue occurs only when installing through comfy manager, i fixed it with pip install -r requirements.txt

Thanks for your reporting, but I set the version minimum to fix this issue on requirements, and that will work.