Tests missing from PyPI

I am trying to package python3-saml for NixOS but cannot run tests because the PyPI package lacks them.
See also the Debian thread about the issue:
https://lists.debian.org/debian-python/2016/04/msg00074.html
tests (unittest.loader._FailedTest) ... ERROR

======================================================================
ERROR: tests (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/nix/store/s3nl02c26303mfjvaaxnc19f8ks9hc8c-python3-3.6.6/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
    module = __import__(module_name)
ModuleNotFoundError: No module named 'tests'

We intentionally removed the test because we saw end users directly serving the library + test on their productions deployments.
As suggested in the thread you shared, you can always use git archive.
See examples of use

You already serve your end users needs by [https://pypi.org/simple/python3-saml/ supplying wheels].  They dont use the sdist.

I notice you are including python2 wheels in this python3 package.  Is that correct?  The other repo seems active still, so I guess you dont want this package installed on python2.

python3-saml is compatible with p2 and p3
python-saml is compatible only with p2


Merging changes from timsutton osx-vm-template

Installing of Puppet fails
I think that the way in which AutoPkg is called has changed recently. Meaning that the recipe name must occur at the end of the command.
As the code stands, attempting to install puppet will fail with an error:
virtualbox-iso: Usage: autopkg run [options] [recipe ...]
virtualbox-iso: Run one or more recipes.

What have I done?
I have updated the cmtool.sh script to match @timsutton puppet.sh as it  currently exists

I can confirm that the current state of puppet.sh works, having just done a build last night.
A note on something I just discovered, though: PL makes available a stable URL of "puppet-latest.dmg" at https://downloads.puppetlabs.com/mac - so if you'd prefer to not bother with the logic provided by AutoPkg, that's another option. I could see osx-vm-templates moving towards that instead and letting the template pass in pinned versions or "latest" for the Puppet and Chef tools. I maintain AutoPkg and the Puppet Labs recipes for those, but removing a dependency is always nice.

Thanks Tim. I was aware that puppet labs hosted the .DMG files. It certainly seems simpler to just download and install those. Certainly something to think about.
I can also confirm that the new code builds in virtualbox.

Just to clarify, the AutoPkg recipes also fetch these same downloads. At
the time I wrote the recipes however (2 years ago), they didn't have the
"latest"-named versions posted, so I wrote some additional code to list all
the items and sort them by version to pick out the highest one. Looks like
that code could be retired now.
Tim
On Tue, Apr 21, 2015 at 11:51 AM, Christopher Johnson <
<EMAIL_ADDRESS>wrote:

Thanks Tim. I was aware that puppet labs hosted the .DMG files. It
certainly seems simpler to just download and install those. Certainly
something to think about.
I can also confirm that the new code builds in virtualbox.
—
Reply to this email directly or view it on GitHub
https://github.com/boxcutter/osx/pull/7#issuecomment-94849975.

Closed per Tim


CIV-3601 civil service point to master

JIRA link
N/A
Change description
fix to point to master. the previous pr was accidentally merged with civil service pointed to pr for testing and demo perporses
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

close because the build keeps failing


NetworkExtensionDiscoveryIntegrationTest.BasicWithoutWarmingConfigFail is flaky

NetworkExtensionDiscoveryIntegrationTest.BasicWithoutWarmingConfigFail is flaky with the following error:
[ RUN      ] IpVersionsClientType/NetworkExtensionDiscoveryIntegrationTest.BasicWithoutWarmingConfigFail/1
test/integration/network_extension_discovery_integration_test.cc:256: Failure
Value of: fake_upstream_connection->waitForData(data_.size() - bytes_drained, &received_data)
  Actual: false (Timed out waiting for data. Got '', waiting for 8 bytes.)
Expected: true
Stack trace:
  0xca37d0: (unknown)
  0xcb7073: (unknown)
  0x7fd0187d031d: testing::internal::HandleSehExceptionsInMethodIfSupported<>()
  0x7fd0187b709e: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x7fd01879e99d: testing::Test::Run()
  0x7fd01879f48e: testing::TestInfo::Run()
... Google Test internal frames ...

link: https://dev.azure.com/cncf/envoy/_build/results?buildId=155651&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff&l=139

A similar error is in ListenerExtensionDiscoveryIntegrationTest.BasicWithoutWarmingConfigFail (error link: https://dev.azure.com/cncf/envoy/_build/results?buildId=155705&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff&l=164)
I'm assuming this is the same error as the test was copied over to Network-ECDS test.
@yanjunxiang-google can you PTAL?

ACK

@yanjunxiang-google any update here? Do you think we should disable in the interim?

FWIW, 3 runs from postsubmit today with this:
https://dev.azure.com/cncf/envoy/_build/results?buildId=155937&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff
https://dev.azure.com/cncf/envoy/_build/results?buildId=155938&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff
https://dev.azure.com/cncf/envoy/_build/results?buildId=155949&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff

After bisecting this issue, it seems the offending PR is #30725.
I don't have enough context there, but I'm assuming it is not a simple refactor.
@vikaschoudhary16 can you PTAL why would it cause a flaky test that uses a tcp client?

I think this is also related to the test failure in: https://dev.azure.com/cncf/envoy/_build/results?buildId=155920&view=logs&j=4e2e4662-2d21-5726-b4bc-9ff5cd6a179b&t=edd1f896-b400-5f76-698a-ad3bf86ca426&l=133
(part of PR #30880).

The test failed when a client created a TCP connection then sends some raw TCP bytes to the upstream. However, the upstream failed to receive the TCP data.  This is a regression issue.
Agree with @adisuissa that https://github.com/envoyproxy/envoy/pull/30725 is very likely the offending PR.

@vadimeisenbergibm, changing from the upstream_.reset(); to deferredDelete(std::move(upstream_)); is highly suspected in the original PR. We need to carefully think and test it.

There is also a thread local storage to extend the upstream lifetime.

Thanks @adisuissa for the revert fix!


FIX: Fixes #15 Non ADMIN users unable to use "Files" admin

Tightened security on root assets folder.
Completely refactored unit-tests for consistency and to increase coverage.
Boyscouting phpdoc and newlines.

Closing in-lieu of a new PR


Ensure support for latest ORSO .ort file format

Limited support as of https://github.com/easyScience/EasyReflectometryLib/commit/828f9ee594ac3e9e0c309d1da0613f8909d16517.

There is now tests for the existing implementation (https://github.com/easyScience/EasyReflectometryLib/commit/c57baa66dd0f335d5b573b6710a4af6aa982aac0) however it would be nice to better expose some of the metadata in the file


fix(complete): Harden --target completions

What does this PR try to resolve?
I found --target wasn't working with rustup as I expected, so this fixes it.  We generally only reference rustup if we are running under it but I think in UX code like this, with a fallback scheme, this should be reasonable enough.
How should we test and review this PR?
Additional information

Its further described in b9fc8d4

clap-rs/clap#5733 removed the rustup proxy so that
CARGO_COMPLETE=bash cargo +nightly works
(with a side benefit of removing the proxy overhead).
As a downside, cargo no longer knows it is running within rustup, so we
aren't reading --target candidates from rustup.
This changes the code to always try rustup.  It is likely a good enough
source, even if the user isn't currently using it.
The candidates should be about the same, just rustup hides some by
default.
Hiding just means it isn't shown by default but if only hidden
candidates match, then we show them.

@bors r+

:pushpin: Commit a5c25f3dd53b3f2ba952f7c185cf02c4d77f6ee4 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit a5c25f3dd53b3f2ba952f7c185cf02c4d77f6ee4 with merge eaee77dc1584be45949b75e4c4c9a841605e3a4b...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing eaee77dc1584be45949b75e4c4c9a841605e3a4b to master...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing eaee77dc1584be45949b75e4c4c9a841605e3a4b to master...

:eyes: Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request.


Attempt to fix GitHub actions macOS builder

See https://github.com/actions/virtual-environments/issues/1811.

Thanks for looking into this :)


Merge envs -> env changes to master

humancellatlas/ingest-central/514

previous PR: https://github.com/HumanCellAtlas/ingest-core/pull/83

This requires this state tracker change https://github.com/HumanCellAtlas/ingest-state-tracking/pull/6
Both should be released at the same time.

Also requires validator change https://github.com/HumanCellAtlas/ingest-validator/commit/49d863b07b350a9cf73ea4dfc6ce21beace5df9f


数据重新加载,原数据依然存在图表上，怎么解决

text值不会改变

Please provide further information for your problem.

I'll close this because it seems like you're inactive


Next 9.0.0

Next version 9.0.0. This version doesn't use easy-peasy but redux as a state management lib.
We decided to use redux, because easy-peasy is built on redux and we could implement this version without breaking changes. We might switch to recoil or useSelectedContext in the future but that is not sure. This version doesn't come with new features but it is more performant, smaller and easier to adapt for older browsers.

Thank you for your hard work! Great tool!


added sign-in and signup functions in auth routes and controllers

Also, provide the changes you made in the description while making a PR.

I think we are going to use passport.js for authentication ? @arjungarg07

Yes @BalgopalPatro

resolved confilcts


Loading a file with csv type leads to java.lang.NullPointerException

I was trying to load a csv file with the csv type and I'm receiving NPE, I have attached the project for debug, but:
Scenario: Working
  * text foo =
  """
    test_id,offer_name,affiliate_name,advertiser_name
    1,autoCsvOffer1,autoCsvAffiliate1,autoCsvAdvertiser1
    2,autoCsvOffer2,autoCsvAffiliate2,autoCsvAdvertiser2
    3,autoCsvOffer3,autoCsvAffiliate3,autoCsvAdvertiser3
    4,autoCsvOffer4,autoCsvAffiliate4,autoCsvAdvertiser4
    5,autoCsvOffer5,autoCsvAffiliate5,autoCsvAdvertiser5
  """
  * csv bar = foo
  * print bar

Scenario: Failing
  * print csvFile
  * csv csvFile = read('this:generalNamesData.csv')
  * print csvFile

It must be related to read function.
anyToCsvNPE.zip

@digoo sorry, csv is for converting strings to JSON, for example:
  * csv csvFile = karate.readAsString('this:generalNamesData.csv')

if you think something needs to be changed, please contribute code (or docs)


ui: Update Boxel teal

This changes the highlight colour to a lighter one, as discussed in the design channel. For buttons with that background the icon and text colour in now black.
I left the Percy diffs unapproved, I recommend looking over them to see how this change affects everything.

Hello @backspace @cmgardella, sharing some thoughts here after reviewing Percy's differences:
Percy Screenshot 7

Circle 1: The close and view more buttons look less visible now, using dark text colour might improve the visual
Circle 2: Same thought if dark text colour can apply instead of white
Circle 3: The Text Button [+ Add Pets] seems a little bit too bright

Percy Screenshot 9 & screenshot relates to Text buttons

Similar thought as per Screenshot 7 Text button, it takes a bit of effort to read due to the light text colour. @cmgardella is there a consideration to introducing a darker teal colour on the text button?

Hello @backspace @cmgardella, sharing some thoughts here after reviewing Percy's differences:
Percy Screenshot 7

* Circle 1: The close and view more buttons look less visible now, using dark text colour might improve the visual
* Circle 2: Same thought if dark text colour can apply instead of white
* Circle 3: The Text Button [+ Add Pets] seems a little bit too bright
Percy Screenshot 9 & screenshot relates to Text buttons

Similar thought as per Screenshot 7 Text button, it takes a bit of effort to read due to the light text colour. @cmgardella is there a consideration to introducing a darker teal colour on the text button?

agreed, this strains my eyes when I look at it

I think we should 1) switch to black icon in the card headers and 2)CTA that isn't encapsulated in a button should be black along with it's accompanying icon

This should include the atom version of cards/pills where icon was formerly teal.  We should display in black or the reversed white accordingly (black in atom card in this image represents a card that is currently open)

The follwing elements with red box should be converted to black icons & text:

Thanks for the feedback, since this is turning out to be significantly more involved than a single variable change we decided to put it on hold for now and schedule it during the next sprint planning.

This should include the atom version of cards/pills where icon was formerly teal. We should display in black or the reversed white accordingly (black in atom card in this image represents a card that is currently open)

I’ve made all the changes except this one, which I can’t find in the codebase. Does anyone have a pointer for me?
It’s possible there are some things that still need tweaking but we can always fix them as the emerge.

I saw this percy change and it looks like the "Open in Code mode" link color changed to black, making it not intuitive that this is a link. Perhaps there are other such cases too, for example icons in top right.

hmm, I see, thanks… this is a byproduct of the button change in the sidebar here:

The follwing elements with red box should be converted to black icons & text:

That button now looks like this:

Maybe in context it’s more clear that it’s a button, or maybe it’s the icon, or the single word… 🤔 this seems like a possible problem with any use of <Button @kind='text-only' …:

Do you have any suggestions, @cmgardella?

Hi @backspace , I'm posting some motion mockups of button hover states so you can get a better feel for the styles we had in mind.  After discussing with Chris T we've opted for the black text and black icon buttons to have a light grey box/container to appear on hover (10% opacity black #000000).  I have an example of this for the create, inherit and delete buttons in code mode.  As for the card header buttons (edit, menu, close) we can still retain the 10% opacity hover for both view (light grey background) and edit modes (bright green background). We can certainly tweak the 10% opacity value for better contrast and readability.  Please let me know if you have any questions.  @lukemelia This falls in line with what I discusssed with Chris T, let me know if you'd like to discuss/revise further.
https://github.com/user-attachments/assets/60cdc85b-5e8b-4017-aad2-6e31f1c66116
https://github.com/user-attachments/assets/d2ca7d2f-01c4-4a75-af5a-17f338913e15

@backspace Let's but the text in a lozenge/button as so:

Okay, I’ve made those changes, thanks!


Complete BLAS level 1 routines in JACC.BLAS

We have axpy and dot BLAS level routines already implemented.
We need to implement the rest of BLAS level-1 operations.
This is implemented in JACCBLAS.jl in JACC.jl/src/
The list of BLAS level -1 routines can be found here:
https://spec.oneapi.io/versions/latest/elements/oneMKL/source/domains/blas/blas-level-1-routines.html
SDSDOT routine shouldn't be implemented, and maybe others too.

Done


Supercoder Issue 1358 Resolved

To address the issue, we need to add detailed logging, validate the incoming request data, and return a detailed error message if the validation fails. This will help in capturing the incoming request data and ensuring all required fields are present and correctly formatted.
To resolve the issue with HTTP basic auth, we need to modify the get_current_user method to check for the presence of HTTP basic auth headers and validate them if present. If HTTP basic auth is used, extract the username from the Authorization header and use it to fetch the user from the database.

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


feat: upgrade all toolchain

Current dependencies on/for this PR:

main

PR #31   👈

This stack of pull requests is managed by Graphite.


if I want to run the script with two clients at the same time, I get an error

It's my code:

Error:
[Client.cpp:285] Receive must not be called simultaneously from two different threads, but this has just happened. Call it from a fixed thread, dedicated for updates and response processing.
Aborted
How can I run multiple clients?

Aiotdlib do not support multiple clients with single tdlib instance for now


DOC: Fix critical value significance levels in stats.anderson_ksamp

Fixes error in documentation for k-sample Anderson test pointed out by @amulliner-dstl in #10263.
My first PR, hoping to contribute lots more! :)
Fixes #10263

@jmmanley thanks for fixing this, I forgot to update the docstring when I extended the values


Perform validation against OpenAPI spec

Follow the instructions as mentioned here to setup a test environment.
Use postman to execute API calls and check if there is discrepancies against GovStack Open API specification

Some observations upon performing API validation:

[ ] Data agreement is missing DPIA field (this is not dpia summary or dpia URL field)

[ ] Id and version field in request body is mandatory for creating and updating policy in consent bb swagger specification

[ ] GET /config/policy/{policyId}/revisions/ consent bb swagger specification response contains only policy object and doesn't contain revisions array

Revisions

[ ] successorId is implemented whereas in consent bb swagger specification its successor.
[ ] authorizedByOtherId is implemented whereas in consent bb swagger specification its authorisedByOther.
[ ] authorizedByIndividualId is implemented whereas in consent bb swagger specification its authorizedByIndividual object
"authorizedByIndividual": {     "id": "",     "externalId": "",     "externalIdType": "",     "identityProviderId": ""   }
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2292C6-L2292C6

[ ] id and version field in request body is mandatory for creating and updating data agreement in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2040
[ ] lifecycle string field is implemented whereas in consent bb swagger specification it's object with the following values
"lifecycle": {       "id": "",       "name": ""     }
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2508
[ ]  dataUse field is missing
[ ] dpia field is missing
[ ] compactibleWithVersionId is implemented whereas in consent bb swagger specification it's  compactableWithVersion
[ ] controller is an object in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2377-L2404

Individual

[ ] id  field in request body is mandatory for creating and updating individual in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2006-L2037

Webhook

[ ] id field in request body is mandatory for creating and updating webhook in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2531-L2572

[ ] revisionId is present in read and list webhook endpoints in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L735-L776

Consent Record

[ ] consentRecord which is implemented is different from consent bb swagger specification
"consentRecord": {      "id": "656ef40ea457a5ffa7233b8b",      "dataAgreementId": "656ee8a7a457a5ffa7233b72",      "dataAgreementRevisionId": "656ee8a7a457a5ffa7233b76",      "dataAgreementRevisionHash": "5eb8f4370a85f165a0dc0f1a7d2f04266340c04c",      "individualId": "656eebc7a457a5ffa7233b7f",      "optIn": true,      "state": "unsigned",      "signatureId": ""  }
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2236-L2289

Create consent record

[ ] Individual id supplied as http header, open api spec passes individualid as query param
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L1333-L1384
Update consent record

[ ] Uses dataagreementId and individualId as queryparams and request body contains only optIn field whereas consent bb swagger specification contains whole consent record object as request body
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L1584-L1634

[ ]  GET /config/policy/{policyId}/revisions/ consent bb swagger specification response contains only policy object and doesn't contain revisions array
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L214

@georgepadayatti Revisions endpoint is returning a single policy object rather revisions. This is an issue that should be rectified from GovStack end.

Webhook

[ ]  id field in request body is mandatory for creating and updating webhook in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2531-L2572
[ ]  revisionId is present in read and list webhook endpoints in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L735-L776

@georgepadayatti Point 2, webhooks doesn't support revisions, so there is no point in having revisionId as query params

consent

authorizedByOther will stay as is.

@albinpa Some comments after discussion with GovStack:

GovStack follows US english so 'z' will be retained in the fields instead of 's'.
Review signature workflow in Consent Records:

When a consent record is updated, it invalidates the signature
Then signature needs to be prepared using create signature endpoint.
Then signature can updated in consent record using update signature endpoint.

[ ]   GET /config/policy/{policyId}/revisions/ consent bb swagger specification response contains only policy object and doesn't contain revisions array
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L214

@georgepadayatti Revisions endpoint is returning a single policy object rather revisions. This is an issue that should be rectified from GovStack end.

@albinpa As discussed, conveyed this to GovStack, they will rectify the 2nd point on their end.

Create consent record

[ ]  Individual id supplied as http header, open api spec passes individualid as query param
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L1333-L1384

Update consent record

[ ]  Uses dataagreementId and individualId as queryparams and request body contains only optIn field whereas consent bb swagger specification contains whole consent record object as request body

https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L1584-L1634

Both points will be rectified on their end.

Consent Record

[ ]  consentRecord which is implemented is different from consent bb swagger specification
"consentRecord": { "id": "656ef40ea457a5ffa7233b8b", "dataAgreementId": "656ee8a7a457a5ffa7233b72", "dataAgreementRevisionId": "656ee8a7a457a5ffa7233b76", "dataAgreementRevisionHash": "5eb8f4370a85f165a0dc0f1a7d2f04266340c04c", "individualId": "656eebc7a457a5ffa7233b7f", "optIn": true, "state": "unsigned", "signatureId": "" }
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2236-L2289

@albinpa As discussed, conveyed this to GovStack, they will rectify on their end.

[ ]  id and version field in request body is mandatory for creating and updating data agreement in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2040
[ ]  lifecycle string field is implemented whereas in consent bb swagger specification it's object with the following values
"lifecycle": { "id": "", "name": "" }
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2508
[ ]   dataUse field is missing
[ ]  dpia field is missing
[ ]  compactibleWithVersionId is implemented whereas in consent bb swagger specification it's  compactableWithVersion
[ ]  controller is an object in consent bb swagger specification
https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2377-L2404

All should be supported except lifecycle as it can be a string.

Revisions

[ ]  successorId is implemented whereas in consent bb swagger specification its successor.
[ ]  authorizedByOtherId is implemented whereas in consent bb swagger specification its authorisedByOther.
[ ]  authorizedByIndividualId is implemented whereas in consent bb swagger specification its authorizedByIndividual object
"authorizedByIndividual": { "id": "", "externalId": "", "externalIdType": "", "identityProviderId": "" }

https://github.com/GovStackWorkingGroup/bb-consent/blob/3f7d2e2fa2b55b1f36890bfc20316227c9ee98ca/api/consent-openapi.yaml#L2292C6-L2292C6

All points will be recitifed on GovStack end, except authorizedByOther, it should not have Id suffix


[ISSUE #3101] Added final modifier for lines 34,36,38,44

Closes #3101
Modifications
Added final modifier for GrpcRetryer fields.
Documentation

Does this pull request introduce a new feature? - no
If yes, how is the feature documented? - not applicable
If a feature is not applicable for documentation, explain why? - minor enhancement

@jonyangx Please, review

@PickBas pls fix build error.

@jonyangx Take a look

@PickBas seems like you have made your modifications directly in the master branch. I will suggest to repost your changes in a new branch. https://eventmesh.apache.org/community/contribute/contribute


tour: Type conversion confusion

Context: https://tour.golang.org/basics/13
Very minor issue here:
"Unlike in C, in Go assignment between items of different type requires an explicit conversion. Try removing the float64 or uint conversions in the example and see what happens."
There are 2 examples on the page. The above statement must refer to the first one, but looks like it refers to the second one.

Just figured out that it actually refers to the example code on the right.


How to mark field as nullable?

I would like to mark Name as nullable field. How can I achieve that?
type Task struct {
	ID        int            `json:"task_id" gorm:"index:idx_name,unique" required:"true"`
	Name      string         `json:"task_name"  required:"true"`
}

I've tried nullable: true, x-nullable: true without much success. Returned json doesn't return anything that would resemble nullability.

Hey @jrozbicki Unfortunately this hasn't been implemented yet.
Ref -  https://github.com/parvez3019/go-swagger3/blob/cc38ece16a6731e11876b5091e8e8bb0531d2887/openApi3Schema/oas.go#L165


SetLocation method for appium dot net driver not defined

I have developed an Appium C# Automated Test Framework to test real Android devices and emulators.  Everything is working well in testing on local devices and emulators.  However, we are transitioning our test cases to run on a Test Cloud Service,  interacting with real devices.  One issue that we need to resolve is to set the GPS coordinates that our AUT will utilize to perform the tests accurately.
I have queried the Test Cloud service and they indicated the usage of the "SetLocation" method.  I have tried to use this AppiumDriver/Android Driver method, but I still get the error that the method is not defined.
Environment

.NET client build version or git revision if you use some shapshot:

All NuGet Packages have been upgraded:

Appium server version:  <IP_ADDRESS>
Desktop OS/version: Windows 10 Professional
Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe:
Mobile platform/version under test: Android OS 6.0
Real device or emulator/simulator: Real Device

Code To Reproduce Issue [ Good To Have ]

@markrhamilton
There is the property. And it seems it has being there for long time.

@markrhamilton Please reopen this issue if there are additional details


Connect MPD to the pulseaudio server running on WSLg

In the past I used to connect to the pulseaudio daemon running on windows by setting the bind adress in sound applications like MPD to localhost. Now I can't find a way to connect to the pulse audio server already running on WSLg.
The pulse audio daemon I used to use had this option.
load-module module-native-protocol-tcp auth-ip-acl=<IP_ADDRESS>

found that you can export /wslg/PulseAudioRDPSink as the audio output source

For anyone else coming to this, with WSLG running on Windows 11, the change to the audio_output block is server "/mnt/wslg/PulseServer"

Hey @dunn where is that setting supposed to be changed? I cant find anything like it in /etc/pulse/default.pa.

oh that was for the mpd configuration


[Platform]: Update DepMap widget with correct data from API

[Platform]: Update DepMap widget with correct data from API
Description
Pull DepMap / essentiality target data from API and update widget:

update target profile header query to display the "core essential gene" chip in the target description
update DepMap widget queries with correct API fields
update widget with correct "data" object
remove sample data from code

Issue: https://github.com/opentargets/issues/issues/2917
Deploy preview: https://deploy-preview-167--ot-platform.netlify.app/
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I've checked the profile page for different genes, comparing the widget's plot to the one on the DepMap website

[ ] H2AC15 has "core essential gene" chip: https://deploy-preview-167--ot-platform.netlify.app/target/ENSG00000275221
[ ] BRAF does not have chip: https://deploy-preview-167--ot-platform.netlify.app/target/ENSG00000157764

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Luca is currently checking whether we can control the way Plotly fits the scale to the data


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vds2465-server for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.vds2465-server
   -

ERRORS:

[ ] :heavy_exclamation_mark: [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '14.0.0' } }" at package.json.
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.5.1 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 2.5.4 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2024 Hirsch-DE<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 Hirsch-DE<EMAIL_ADDRESS>at the start of LICENSE

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W046] devDependency should not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@iobroker/adapter-react:2.0.13"
[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W130] Many "common.news" found in io-package.json. Repositorybuilder will truncate at 7 news. Please remove old news.
[ ] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W515] Why did you decide to disable i18n support?

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

This issue has been replaced by new isse #5
This issue can be closed.
your
ioBroker Check and Service Bot


alvr_launcher crashes on start on Ubuntu 20.04

Description
alvr_launcher crashes a few seconds after opening.
unable to even start on the setup wizard
terminal output:
https://pastebin.com/raw/caue69Xq
Hardware
https://linux-hardware.org/?probe=52a27d926e
Installation
ALVR Version:
16.0.0+1640412182+aee1fd32
SteamVR Version:
1.20.4
Install Type:

[x] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[ ] Source

You need to have chromium installed to keep ALVR from closing


Disables Thread-Safe for local static variables

Fixes #1283.

@xzyfer, @saper, PTAL.

I don't think this is a good idea for one reason. As long as the node releases are built with VS2013 we have to keep compatibility with C++. I don't want to waste 3 days on yet-another-C++-runtime incompatibility the next time we encounter something.
We should simply build with the same compiler and possibly with the same flags as the node engine.
I'll be submitting patch to node and node-gyp to let us know the original PlatformToolset used, so we can possibly use VS2015 in v120 mode to compile node-sass.

The cflag is only applied to 2015. This doesn't effect VS2013.

I understand. We should really use PlatformToolset to set things straight on VS2015 (if that is confirmed working, I didn't try yet).

@saper, I don't think you are understanding it correctly
v120 = VS2013
v140 = VS2015.
If someone has BuiltTools2015 installed, they will not be able to build node-sass because it doesn't have v120 at all. If someone has VS2015 installed without VS2013 toolset (which is optional in the install menu), they will missed out too. Having a compiler flag in gyp is not yet-another-hassle.

On Wed, 20 Jan 2016, Adeel Mujahid wrote:

@saper, I don't think you are understanding it correctly
v120 = VS2013
v140 = VS2015.
If someone has BuiltTools2015 installed, they will not be able to build node-sass because it doesn't have v120 at all. If someone has VS2015 installed without VS2013 toolset (which is optional in the install menu), they will missed out too. Having a compiler flag in gyp is not yet-another-hassle.

We actually need to tell people using node-gyp to use vs2013 or vs2015
with platformtoolset v120 (which is as you say
the C++ compiler taken out of vs2013).
I cannot have C++ compatibility otherwise and that's what we are using.

We actually need to tell people using node-gyp to use vs2013 or vs2015

If someone has VS2015 installed without legacy stuff or BuildTools2015, they will not have v120 targets.

On Wed, 20 Jan 2016, Adeel Mujahid wrote:

We actually need to tell people using node-gyp to use vs2013 or vs2015

If someone has VS2015 installed without legacy stuff or BuildTools2015, they will not have v120 targets.

In other words: I care less about people installing VS2015 with the default or limited settings
and compiling node-sass on their own
I care a lot more about folk using our binaries as is.

This change should not effect our binaries built from VS2013.

On Wed, 20 Jan 2016, Adeel Mujahid wrote:

This change should not effect our binaries built from VS2013.

Let me be a bit blunt here:
I've wasted enough time to work on the "assumed" VS2015 compatibility.
Things were supposed to run smooth, they didn't.
I don't really care if somebody at the Microsoft tried node-sass
personally with VS2015 or not. They haven't obviously used XP
for their testing.
If Microsoft comes with a statement "We do support dynamic loading
of C++ DLLs compiled with Visual Studio 2015 into the address space
of the process runing C++ code compiled with Visual Studio 2013"
then I am fine.
The problem is, nobody at Microsoft will give us such a guarantee
for C++. They may guarantee compatibility for pure C modules only.
Keep in mind that
https://connect.microsoft.com/VisualStudio/feedback/details/1789709/visual-c-2015-runtime-broken-on-windows-server-2003-c-11-magic-statics
got closed as "(works) by design". The workaround is given for this particular
C++ feature.
As for this patch, I don't know why we are setting globally
that npm variable. Building node modules with v140 is simply
wrong, as long as v120 is what node is using.
I am not going to elaborate further on this, sorry.

TLDR: the change in appveyor was not meant for this PR. I have reverted it back. #1352 will take care of AppVeyor. This change remain with zero side effects.


Add Zipkin tracing for http and messages

@trisberg can you please rebase this on the latest master?

I tried but getting some really weird conflicts on files that weren't touched, strange :(

Closed in favor of https://github.com/markfisher/sk8s/pull/45


refactor: replace H256 and U256 with UnsignedFieldElement in VO's

Resolves task 2 of #13:

replace U256 and H256 with UnsignedFieldElement in value objects and providers

This is a messy one, as we're fixing all the misuse of H256 and U256 across a lot of files.

Yeah should have just followed Ethereum and make everything hex.


Information Management Information incorrect

The first three items in the Information Management Section have the same description :-
"Get the site closure status of the site which has a site policy applied"

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

ID: 3b3240d3-6a7d-fc4b-62fd-d3a5375d8a4a
Version Independent ID: 561212df-4dab-92b7-b634-57d53d313c6f
Content: PnP PowerShell overview
Content Source: sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md
GitHub Login: @Techwriter40
Microsoft Alias: kirks

@NPrice99 Thank you for your feedback
We want to make sure your PnP issue is handled appropriately.
We have a separate repo for the PnP PowerShell issues. We want your issue to get the proper attention it deserves.
Please open your issue in this repo: https://github.com/SharePoint/PnP-PowerShell
I am going to close this issue so that we can track to correct one in the PnP PowerShell repo.


VS crashes when the Pi IP address changes

@joaozorro reported in #32 that the extension crashes VS when the Raspberry Pi's IP address changes.

It will also crash if the IP is the same but the credentials change and the wrong default is checked (or wrong credentials are chosen vs [DEFALUT] in "Raspberry Debug Settings". See example with two different SD cards added for same Pi with static address:

Hallo, i have the same Problem. Is there a workaround?


Stash only relevant broker config keys on the broker status

Describe the bug
All keys from a CM are stashed as annotations.
Given CM:
apiVersion: v1
kind: ConfigMap
metadata:
  name: my-broken-kafka-broker-config
data:
  default.topic.partitions: "10"
  default.topic.replication.factor: "1"
  bootstrap.servers: "my-cluster-kafka-bootstrap.kafka:9093"
  auth.secret.ref.name: "not-present"
  blah.blup: foo-bar

Resulting in :
...
  status:
    annotations:
      auth.secret.ref.name: not-present
      blah.blup: foo-bar
      bootstrap.servers: my-cluster-kafka-bootstrap.kafka:9093
      default.topic.partitions: "10"
      default.topic.replication.factor: "1"
    conditions:
...

Expected behavior
Not seeing the blah.blup annotation key on the status

is this related to the same function mentioned in https://github.com/knative-sandbox/eventing-kafka-broker/issues/2577?

/assign

@Vishal-Chdhry not sure I get the question to the function yoy mean.
Somewhere we stash the content as status, but we should filter what we stash

@matzew I am looking into it again, i will ask you if i have any doubts

I was researching on it, i think this functions might be the ones that needs changes.
https://github.com/knative-sandbox/eventing-kafka-broker/blob/c69f88ebc42f709cb014750cf336f3ceede471fb/control-plane/pkg/reconciler/base/reconciler.go#L281-L319
How do we filter annotations to know if they are relevant?

/remove-lifecycle stale

I will look into this

/assign

/remove-lifecycle stale
/triage accepted

Hey @basit9958 , just see are there any update on this issue?

The ConfigMapStatusAnnotations are set in: https://github.com/knative-extensions/eventing-kafka-broker/blob/8a79f31bea81dcb2d94a0bb3524f080fd66ea9c3/control-plane/pkg/reconciler/broker/broker.go#L583-L591
The only keys that we are currently using from this config map are here: https://github.com/knative-extensions/eventing-kafka-broker/blob/8a79f31bea81dcb2d94a0bb3524f080fd66ea9c3/control-plane/pkg/kafka/topic.go#L31-L33
@basit9958


1.7.2 is not compatible with robotframework 2.8.4 anymore.

because 2.8.4 does not have RobotNotRunningError which is added in 2.8.5

When this type of incompatibility is introduced, it should be stated in setup.py

That dependency will be resolved in the next release. It wasn't intentional.

I know you know. I filed the issue in order to help other people understand their issue.

It's fixed in master. I just don't have a windows machine with me to do a new build.

If you haven't been able to upgrade to newer RF versions due to DateTime library introduced in RF 2.8.5 that conflicts with Zope2 DateTime module, you should be now finally be able to upgrade to RF 2.9. It was just released and it contains a fix to this bug:
https://github.com/robotframework/robotframework/issues/1737

1.7.3 should be released on Saturday and will resolve this issue.

@pekkaklarck Yup, using RF 2.9 release is compatible again with Plone/Zope2. Then I can use 1.7.2 without issue.

It's great that Plone/Zope2 people can finally upgrade their RF installations! There have been lot of enhancement since 2.8.4.

This is fixed for 1.7.3.


Create summary maps for transit flow

Not hard to create, but I don't think most end users realize the transit flow is being loaded on the link layer. Having a summary map is a nice way to highlight that.
In addition, we should add a transit diff map to the scenario comparison tool that quickly highlights changes in transit volumes.

Is it doable in FY24? @dkyleward

Done!


Added nil check for state key

This will prevent crash reported in #158
Fixes #158

==> Checking that code complies with gofmt requirements...


Open Oracle Review

What we could do :

Deploy the Open Oracle
Add it as a source to our regular oracle


MetaDraw not finding psmtsv from MetamorpheusXL

Hello everyone,
I have generated XL datasets with Metamorpheus XL.
I would like to annotate those link using MetaDraw on my Mass Spectrum.
However I am unable to find the .psmtsv files that MetaDraw requires. Are those the intra/interlinks.tsv files of my dataset?
How can I input that in on Metadraw?
I am using the GUI version.
Best

Hi Rodolpho,
I answered via email but I'll include my response here for completeness.
There are currently 2 bugs that require workarounds that will be fixed in the next MetaMorpheus release.

The XL results .tsv files can be added to MetaDraw via drag-and-drop. Currently pressing the "Select" button in the interface will not list .tsv as a valid file format, so drag-and-drop is the required workaround
The file name in the XL .tsv file lists the full file path of the data file (e.g., C:\MyData\MyDataFile.raw). Replace this field with the data file name without extension (e.g., MyDataFile instead of C:\MyData\MyDataFile.raw).

These bugs are fixed in #1959 and will be included in the next release. Thanks for the bug report!


Issue #348: Adding ability to reset event monitoring

This change overhauls the event monitoring somewhat so that the MonitorEvents method returns an object off which tracked events can be reset. This also adds a Reset call to the individual event recorders too. The event monitoring setup code has been moved into an EventMonitor class to encapsulate things a little more cleanly. Also, calling MonitorEvents multiple times with different interfaces for the same object adds to the existing events being tracked.
This is to address issue #348.

Documentation changes would need to be made to cover the return value of MonitorEvents, the new IEventMonitor interface calls (Reset, Attach, and GetEventRecorder), and the new Reset method on IEventRecorder.

You've been busy ;-)
What about support for a using block?

I looked at that and found it to be unnecessary. It just didn't really add any value whatsoever. What would it actually do? What gets disposed of? I just couldn't see a useful scenario for it in the end.

Well, it will make the scope of monitoring really explicit. And if the monitored code crashes, the reset will automatically happen without causing side-effect on other (parallel) tests.

Yes, I suppose the Dispose would remove the event recorders for the specific monitor instead of just resetting them. That makes sense.
Would you mind if I cover that in a separate PR once this one is cleared through?


this be looking sexy

wonder who wrote the site and the typing source code, must be some cool dude

yes indeed, moron!


App freeze with anime with a lot of episodes + search issue

If I open one piece episode page the app freezes for a bit (tested on SM-T585)
Also If I try to search for other anime while results from previous search are there it shows results from both searches and sometimes doesn't let me search

I think I know the issue. Thanks for reporting mate. I will upload a new update soon

I fixed the search bug, and uploaded a new build, as for the animes with a lot of episodes I couldn't reproduce. Thanks for reportin.


How to set caching in the settings section

Hello, today i downloaded the gui and i´m really enjoying it at the moment, but there is one problem im having: when i put the caching options (--file-caching=4000 --network-caching=4000 for example) in the custom parameters section, i cant access any stream and it displays this error
"usage: livestreamer.exe [OPTIONS] [URL] [STREAM]"
is there anything i´m doing wrong or is it just a bug?

Hi, thank you!

--file-caching=4000 --network-caching=4000

I guess, you're trying to set VLC parameters, right? Those are no livestreamer parameters...
You need to set these either in the --player or --player-args field. Also don't forget to append the required {filename} if you're using the player-args field (check the livestreamer docs linked in the GUI).

PogChamp IT WORKS PogChamp
Thank you so much :D

np, yw :+1:


Feature: pickle support for StreamField

This is a rework of my original PR #5998 where I described the problem of lack of pickle support. Sadly the implementation is a little bit ugly but after many hours of thinking I didn't find any other way to make it work. I'm open to discussing any other solutions.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[x] For Python changes: Have you added tests to cover the new/fixed behaviour?

I will take a look if that is possible to add pickle support for Block as it is the blocker for implementation without passing field reference.

Ok, with some help of ChatGPT, I was able to make StreamField compatible with pickle in a proper, clean way. I assume it is now safe to merge.

Unfortunately I don't think the issue with callable choices is going to be solvable without a complete change of approach here. If the internal state of BaseChoiceBlock needs to be included as part of the pickled representation, then there will be situations where that internal state will contain a passed-in choices=lambda: ... argument that can't be pickled. If you find a solution that seems to work, it's probably because you've evaluated that callable and stored the result, instead of holding on to the callable itself.
I think the only reasonable way forward here is to somehow exclude the stream_block attribute from StreamValue's pickled representation, so that we're only keeping the stream data, not the corresponding definition. This would be in line with how pickle is intended to work, as per https://docs.python.org/3/library/pickle.html#what-can-be-pickled-and-unpickled:

Similarly, when class instances are pickled, their class’s code and data are not pickled along with them. Only the instance data are pickled. This is done on purpose, so you can fix bugs in a class or add methods to the class and still load objects that were created with an earlier version of the class.

Just as you'd expect to pickle a Python object, stop the program to make some changes to its class definition, start it again, unpickle the object and end up with an object that behaves according to the updated class definition - it seems logical that if you make any changes to a StreamField's definition, any unpickled StreamValues should then follow the new definition, not an older one that was frozen along with the data.
Unfortunately, I can't see a good way of detaching the stream_block attribute and reattaching it on un-pickling. For that to work, Django's Model class would need to provide some way for Fields to participate in the pickling process - essentially, being able to ask StreamField "here's the value I got from self.body - can you turn this into something pickle-safe?" and then later "here's the pickle-safe value I've got - can you turn this back into a usable StreamValue I can assign back to self.body?". Sadly, that mechanism doesn't seem to exist :-(

@gasman thanks for such a detailed review. I'm not sure if lambda is something we should worry about. If lambda causes troubles then it is up to the developer to change it into a named function. I think it is the same case as callable choices in Django itself.
My initial approach was exactly based on reusing the stream_block definition and reconstructing when needed. It is a bit ugly but ugliness is limited to a single place where it happens and covers all possible serialization issues one can face: https://github.com/wagtail/wagtail/pull/10654/commits/4db88e9eaf3eb6c65ac13270aefa3782e6ac71e7#diff-e2bdb68dcc4c5d7c891792878cacc5f769ed9bfe7ccb3ad193a952ab904c3fb5
What you think about this one?

Side note: Using dill instead of pickle solves the issue without any code modification at all. However, it requires some tooling adjustments. It may be as easy as writing a custom cache backend or providing a custom serializer for your cache app.
For example:

https://github.com/Suor/django-cacheops is now allowing to define dill as the default serializer
https://github.com/pinterest/pymemcache allows a custom serializer to be provided in Client constructor, so it can be used together with a custom django cache backend
https://github.com/noripyt/django-cachalot and many others use native django cache, so it is possible to supply one that uses dill instead of pickle

dill seems to be popular but I've never used this in production and I'm not sure about speed comparison vs pickle
https://github.com/uqfoundation/dill

@gasman have you had a chance to look at the latest changes?

@gasman thanks for your input! I've simplified the code per your recommendations.

@pySilver I've had a quick look, but not a full review yet - there are a lot of details here that will need careful consideration, like what happens to inner StreamValues from StreamBlocks nested inside other blocks - presumably those won't have the StreamField reference, and don't need it, but in that case the pickling logic needs to guard against that reference not existing.

Well, let's start with why we are doing this. We are doing this in order to support much-wanted cache support for Django ORM. I haven't seen requests to pickle StreamValue objects on it's own but there were plenty of issues for users like myself that had problems with popular orm cache apps.
Will it fail if we try to pickle StreamValue instance without StreamField reference? Yes, indeed. As much as it will fail without this PR, due to the fact that BaseChoiceBlock is constructed in a way it builds callable in runtime and we didn't find any good way to refactor it.
Do we need some guarding code in case _stream_field reference is not found? Honestly, I think we don't. It will fail anyway. Ok. We can make a descriptive error telling the dev why it did happen. But well it is in the code anyway.
I am also not very happy about this implementation but this is probably the only way at the moment. At least if we want to continue wrapping even static choices into a callable.

Thanks for the clarification! I was under the impression that pickling a StreamValue would require recursively pickling its children, which meant there would be a possibility of encountering another StreamValue further down - but now I see that the call to get_prep_value ensures that it'll only have to pickle the basic JSON-friendly data types.

@gasman What can I do to make this PR happen? :)

Hey 👋,
Just a quick nudge on this PR. I get it is not ideal solution but I don't see how we can improve while maintaining callable choices wrapper. Chances we will make it to the master? I see people are already building their images with this patch, I myself currently use it with monkey patch with no problems.

Sorry for the delay in getting back to this! Have merged in eadf9a6d9cf749f5ed9918b0826523ef64e9b1bf (with a couple of tweaks - some additional comments / error-checking, and reverting the addition of the callable choices block to the test StreamPage, which I don't think is needed now that we're not attempting to pickle the StreamBlock definition).


Update SNET.js

Update API endpoint for SNET provider

Thanks just saw this.  Will test and merge.

Merged, thanks.


Feature/add stability

Updating the util.fn handler to be more error friendly. I noticed that requests can fail from api limits or other errors, but they always come back with http 200. I've added some catches to help properly pipe errors to a catch vs the regular then.
Updated tests to use a new mock required to get test coverage back to 100%.
Added package-lock.json

Coverage remained the same at 100.0% when pulling 67d07decdc9d4003039e2132ad8d651d06aa942a on feature/add-stability into a530a4ad7dfe36792ca1ad8f4afdee0c9e5e0965 on master.

Coverage remained the same at 100.0% when pulling 93eba4541688e0e0a4d7cfd4acf38a2fe3c6aa4e on feature/add-stability into a530a4ad7dfe36792ca1ad8f4afdee0c9e5e0965 on master.


angular6 upgrade - test fixes and lint fixes

resolve unit tests
resolve several lint errors

Great. Thanks.


Lager version 3.5.2, issue of excessive memory usage

My erlang program is deployed in a Docker environment, and the lager writes console logs to the console.log file. However, for unknown reasons, it stores the logs in memory messages instead of writing them to the file.

When this issue occurs, the lager no longer writes logs to the console and console.log file, blocking messages in memory and unable to release them, resulting in an increasing memory usage.
The original console log level was debug, but this issue occurred. I adjusted the console log level to warning and wrote the debug level log to a file instead of the console and file. It seems that this issue has been significantly improved, and there has been no problem of excessive memory usage again.

and you're not logging to stdout or another non-file backend at all? how many logs do you think you were generaying per second?

and you're not logging to stdout or another non-file backend at all? how many logs do you think you were generaying per second?

I output the logs to both the program console and console.log file at the same time, and the speed of the problem depends on the frequency of the log output. When there are more than ten logs per second, this problem occurs in three or four days of college. When there are forty to fifty logs per second or even higher, this problem occurs in less than half an hour.
Perhaps I can send out the tiger configuration file to take a look, but it will need to wait until next Monday.
If I increase the console log level and lower the log level output to the console.log file, can I also solve this problem? Because the system has already been launched into the production environment, when this issue occurred, I set the console and output log levels to a high level, which prevented me from seeing some debug logs and preventing me from stopping my application.

After this issue occurred, I changed my lager configuration file and raised the console log level, making it almost impossible for logs to be output to the console. Secondly, I will output the debug logs to a log file. The log output rate may be around 40-50 per second, and there is no memory freeze caused by the inability to output logs to the console and files, which seems to solve this problem.

My English proficiency is not very good, and I often use translation software to translate into English, which may cause confusion. I hope you can forgive me.


Update to support requirements in DICOM standard 2022a

Tested on Hamamatsu NDPI images. Should improve DICOM compliance.

PhotometricInterpretation - YBR_FULL_422 for lossy standard JPEG, determine from encoder
ImagedVolumeDepth - must not be 0, supply default
WholeSlideMicroscopyImageFrameTypeSequence - required shared group, clone ImageType
LossyImageCompression and related - required for lossy JPEG
ImageType - typo in defined term
SeriesNumber - required, supply default
PositionReferenceIndicator - required, has defined term
[XY]OffsetInSlideCoordinateSystem - required
AcquisitionDateTime - required, supply default
IssuerOfTheContainerIdentifierSequence - required
Various typos e.g. "Unkown"

Thanks for the pull request @JamesDarcy616! It looks like it will fix a lot of requirement that I have missed or not implemented.
I will review this as soon as possible.

Hi @JamesDarcy616,
I merged some changes by mistake to your branch. Im sorry for that and will try to revert.

Great, thanks :)

Thanks for contributing James! I have just published 0.2.0 with these changes.


support running mailcather mounted at a specific http url prefix

very useful if you want to run mailcatcher behind a shared proxy

That would be great !
Could you add a apache config example in the documentation?

@sj26 Hi there, do we have any chance to see this feature being merged ? It is really painful to run mailcatcher behind a proxy without this.

This feature doesn't currently work. I'll see if I can polish it up for release. This has been a common request, and it probably couldn't hurt.

@sj26 Any news ?

I haven't had time to fix it up yet, sorry. Feel free to take a stab if you like.

+1

Thanks. This is supported as --http-path in the newest version.


Do we also add adopters from readme to site?

At site we have users/adopters of tofu. So, should we also add here adopters from readme?

Yes, teams are free to make PRs to add them to docs


Change after 4/18 now downloading 1080p DASH instead of native format?

Now, all my videos after 4.18 began re-downloading (hundreds gigs) because someone decided that ffmpeg 1080p dash all the sudden as default was a good idea without warning.  Where was this change made to stop pulling the highest NATIVE ORIGINAL non-dash no conversion or merge needed which in  cases was 720p?
This is absurd to make that change which when pointed at existing downloads made all old ones look invisible since they did no longer adhere to this new highest format of the merged DASH.  I don't want the merged DASH I don't want any merging of audio and video, I was (as I am guessing many others were) happy with the native, original uploaded 720p without any fake upscaling.  It was also a LOT faster since no ffmpeg was needed at all to simply pull down the single MP4.
So, can someone help with a reasonable workaround - putting in 720p as the highest allowed isn't really a solution is it?  When I use the no dash manifest for some reason the unmerged 1080p still downloads.
Any help greatly appreciated!

Calm down and read the last paragraph of format selection section.

I'm going to also answer to your comments in https://github.com/rg3/youtube-dl/commit/feccf29c876869f44a9c983977371073b9801a51 here:

I honestly missed it but judging from other folks comments I know I'm not alone I still think a new cmdline for this would been better idea I do see value to new behavior

We have actually got a few requests for making downloading the DASH formats the default behaviour, most people expect youtube-dl to download the best quality without any additional parameters (that's what we do for all sites). Making it the default is also important because the feature for merging formats is not easily discoverable, unless you were told it existed you would think it wasn't implemented.

I don't want the merged DASH I don't want any merging of audio and video, I was (as I am guessing many others were) happy with the native, original uploaded 720p without any fake upscaling

For every case of an upscaled video there will be a video whose native resolution won't be served as a single file. For example:

native 1080p videos, they are quite common.
As far as I know 60fps videos are only available as DASH, and some people really appreciate having that framerate.
all those 4k video.

In conclusion, we make the switch because it would allow most users to get the best version by default and people who don't want them can just add -f best to their config file. I'm pretty sure that there were a lot of people that had -f bestvideo+bestaudio/best in their configuration.


Fix tonelib-noisereducer (VERSION_PUBLISHED blank)

The URL no longer has the version number in it. See
https://www.tonelib.net/downloads.html

@philclifford It should be OK now. Thx for the feedback.

Alas you still need to compare with my PR  - the version installed by the deb  is 1.2-0 , which is "less than" the announced version and causes endless bogus "updates", hence the sed fix.
Without something like that you end up with
  [+] tonelib-noisereducer (1.2-0) has an update pending. 1.2.0 is available.


Exception thrown when running as localhost

I get the error message:

0 - An exception has been thrown during the rendering of a template ("Object of class Grav\Common\Page\Media could not be converted to number").

when I am running the plugin - checking for enabled when running as localhost:8000 or a localhost under WAMP.  I do not get this error when running on Linux on my host.  I have isolated it to some code that checks to see if the plugin is enabled:
{% if config.plugins.social-media-links.enabled %}
  {% include 'partials/socialmedia.html.twig' %}
{% endif %}

Specifically: "config.plugins.social-media-links.enabled".   I did not see this in the doc's, but it makes sense this should work, and it does work running on my webhost.  I am not sure why it fails when running locally.
This is my configuration:

PHP 7.4.33
Chrome Browser
Grav <IP_ADDRESS>
Theme: Quark with Blog site skeleton

Thanks

I couldn't reproduce your error - neither locally nor on my server(s). I also tried Linux and Windows - everything works here on my side :-(
As I'm not using grav (and my plugin) anymore it's a bit complicated to track down such errors for me. If you find where this error is coming from and have a solution (or some idea at least) feel free to answer here or open up an PR ;-)
Sidenote: This config switch is (or at least was when I did create this little addon) some kind of standard from a grav template, so I didn't add it to the docs. I think it is mainly shown here for enabling / disabling the plugin:

I am closing this issue as the problem observed is not technically an issue with this plugin, rather a behavior of the twig processor.  Quoting Bluitzen:

According to the documentation about Config Variable Namespacing 1 the plugin filename is part of the config variable namespace and the filename of the social-media-links plugin includes dashes.
So technically this namespace config.plugins.social-media-links.enabled is correct but as @pamtbaau pointed out will fail because Twig treats each dash as an operator (minus).

There are two work arounds suggested by this very kind user as well.  See them here and here.
I am closing this issue.


NIFI-6182: Updated dependency on Lucene to Lucene 8.0.0. Updated code…

… necessary to use the new API. Updated WriteAheadProvenanceRepository so that upon startup if provenance indexes are written using the old Lucene format, , they are considered 'defunct' and the events are re-indexed in a background thread into a new index that uses the Lucene 8 format and the old index is then removed. Added Provenance Repository that consists of about 30 events and added integration test to ensure that the repo can be started up/initialized when pointing to a prov repo that was written using the old lucene format.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Hi,
we wanted to migrate our Nifi version from 1.9.2 to 1.10.0. We did not succeed. It was not possible for us after the update to access the old provenance events. We have not changed anything in our configuration. I read that after the update the index is rebuilt. Can that be a reason or do I have to consider something special? After I changed back to version 1.9.2, my old provenance events were immediately available again.
Do you have any tips on what I can check?
Many thanks
With kind regards


Change default voice font for the emulator

Background
Is your feature request related to a problem? Please describe.
I'd like to be able to test my bots with voice, the current monotone font used by the emulator is very inexpresive and boring... (it matters if you use it all day :))
Describe the solution you'd like
Would it be possible to change the default font to use Jessa or Guy?, having the ability to change the font in settings would be a great plus too.
Describe alternatives you've considered
For a better voice experience, I use webchat that allows me to configure the font, but I need to use ngrok or some other tool to run against localhost.
Note to fixer

[ ] Add the custom voice font feature in BotFramework-WebChat
[ ] Publish a new Web Chat release (prod or dev)
[ ] Transfer the issue back to BotFramework-Emulator
[ ] Bump Web Chat to version that support custom voice font
[ ] Add UI and entry points
Consider implementing UI (in Emulator app) for other speech-related features

[ ] Custom speech (CRIS)
[ ] Provide speech subscription key

References

Custom voice font support is done by changing the URL endpoint, documented here, https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-apis#text-to-speech-api.

transferring this from emulator repo since this requires work in webchat. @seaen, @compulim please triage.

Note to fixer
Custom voice font support is done by changing the URL endpoint, documented here, https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-apis#text-to-speech-api.

Hi, I know that this can be done in webchat, my ask is for the BF Emulator.
Thanks

@gabog Understand this is an ask for Emulator. We are trying out GitHub new issue transfer to get the work done.
The issue is being transferred to BotFramework-WebChat, get it fixed here, and then will transfer back to BotFramework-Emulator for the UI part.
We need a better diagram/dependency graph or to-do list so the issue author (or participants) know what's going on.

Ah, OK, thanks.
From: William Wong<EMAIL_ADDRESS>Sent: Monday, November 26, 2018 6:09 PM
To: Microsoft/BotFramework-WebChat<EMAIL_ADDRESS>Cc: Gabo Gilabert<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/BotFramework-WebChat] Change default voice font for the emulator (#1396)
@gaboghttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgabog&data=02|01|Gabo.Gilabert%40microsoft.com|384bc9ac9c17456d126a08d653f41cc5|72f988bf86f141af91ab2d7cd011db47|1|0|636788705259275026&sdata=96BOZQ0UwtpkKZfiWNtSBlQuzSj0YS5r8Xlt2pQr9oM%3D&reserved=0 Understand this is an ask for Emulator. We are trying out GitHub new issue transfer to get the work done.
The issue is being transferred to BotFramework-WebChat, get it fixed here, and then will transfer back to BotFramework-Emulator for the UI part.
We need a better diagram/dependency graph or to-do list so the issue author (or participants) know what's going on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FBotFramework-WebChat%2Fissues%2F1396%23issuecomment-441835413&data=02|01|Gabo.Gilabert%40microsoft.com|384bc9ac9c17456d126a08d653f41cc5|72f988bf86f141af91ab2d7cd011db47|1|0|636788705259285034&sdata=ddXRcD30v%2Btx372tvDYbZCjXIsmjbM9Y3O3KkgoK9kw%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALsl8r1qzQUI0-ARI4nWA7F7VOpiqI-kks5uzHR7gaJpZM4Yzpec&data=02|01|Gabo.Gilabert%40microsoft.com|384bc9ac9c17456d126a08d653f41cc5|72f988bf86f141af91ab2d7cd011db47|1|0|636788705259285034&sdata=JfrgkiIIRtrpjvJmUL%2BFeCxrqkjIIdevl%2Fgji2cxy1g%3D&reserved=0.

@vishwacsena can we get your input on a priority level here?

Hi, any updates on this one?
Thanks


As a developer, I want to create automatic documentation for the API

User story
Description
Related issues

Look for Open API (Swagger) for automatic documentation, it's really useful for API documentation and easy to understand 👀 😉

Thanks for the advice and sorry for the late response hadn't seen your answer! :)


Add CDNJS version badge in readme

This will add the badge to show its version on CDNJS and also link to its page on CDNJS!

Duplicate of #20917.

@mdo
Sorry, I missed it.


Switch to Horologist AppScaffold

A better reusable implementation of App wide scaffolding.

Nice, looks a lot cleaner


alignment of the copyright line in the footer

please assign this issue to me
the copyright line is not aligned in the centre
To Reproduce
Steps to reproduce the behavior:

Go to 'home page'
Scroll down to 'footer '

Expected behavior
it should be in the center
Screenshots
If applicable, add screenshots to help explain your problem.[
()))

Assign this issue to me
i can make changes in the form that it will apper in center after the social media links in footer section.As major types of website do this things for seeking more number of users on their platform.
Please assign this to me i have more knowledge regarding this.
Lets hope for the best

Assign this issue to me i can make changes in the form that it will apper in center after the social media links in footer section.As major types of website do this things for seeking more number of users on their platform. Please assign this to me i have more knowledge regarding this. Lets hope for the best

well what "MORE" knowledge is required to centre something , raise new issues if required instead of this .


Build stops with Get "https://index.docker.io/v2/": EOF

This looks similar to #6438, in that Kaniko is trying to make a network operation that gets interrupted or fails.
However, the specific operation seems different, so it probably has a different code path.
https://pantheon.corp.google.com/cloud-build/builds;region=us-east1/77af3865-34a4-4fa8-82d9-185883612f85?e=-13802955&mods=logs_tg_prod&project=cloud-cpp-testing-resources
Step #0: error building image: Get "https://index.docker.io/v2/": EOF
Finished Step #0
ERROR
ERROR: build step 0 "gcr.io/kaniko-project/executor:v1.18.0" failed: step exited with non-zero status: 1
Finished Step #7

Closing, Kaniko has been failing, but we haven't seen this error in a while.


Add docker image publishing workflows

Sorry for the radio silence on this, I wanted to get to this sooner but I've been extremely busy as of late unfortunately. Eventually carved out time to work on this :smile: Regards https://github.com/trickstercache/trickster/issues/691 FYI @jnichols-git
These workflows should handle building and pushing images to docker hub and github's container registry, using qemu and docker buildx to build for the arm64 and amd64 platforms.
We have two files here:
publish-docker.yaml:

This will run when a release is created (which excludes prereleases, like release candidates)
On a release workflow, it creates some semver docker tags (like :x.x.x, :x.x, and :x), it also updates the :latest tag from the latest release code, and creates a :sha-<commit sha long> tag
This will run on merges/pushes to main
On a main workflow, it refreshes a :main tag, and creates a :sha-<commit sha long> tag
It also runs the main workflow on a schedule

publish-docker-prerelease.yaml:

This will run when a prerelease is created (which is a checkbox in the github UI when creating a release, and is typically used for betas or release candidates)
On a prerelease workflow, it creates a semver docker tags (like :x.x.x-rc1 for a tagged prerelease like :x.x.x-rc1), and creates a :sha-<commit sha long> tag

A slight change here that I wanted to specifically call out was that this adds a new kind of tag that I don't think you currently do. And this is the tag that will get rebuilt over time from a fresh alpine base. Which is the :main tag. I can also just switch this to be the :latest tag, depending on what you want. But :main gets refreshed every week. :latest will just track the latest released version and will be refreshed every time a release happens. And the semver tags will just be tagged once when a release is cut.
Some important general notes here:

This begins uploading trickster images to github's container registry, which isn't currently done here. I can strip that out here if you want. I just figure it's valuable to have a second registry and basically free since the workflow should manage tagging/uploading there.
This relies on a Docker Hub username and access token with read+write privileges in github secrets, which a maintainer here will need to provide.

Ah, my commits are signed but not signed off on. So I'm failing that DCO check. Will fix that but will have to force push it up.

FYI, I set up mostly the same workflows in a repo of my own just to try them out, and you can see what they did. The only thing I think I stripped out was the docker hub login, for testing purposes I'm just using github's container registry. But here: https://github.com/Starttoaster/ci-playground
I created a release tag, a pre-release tag, and just ran CI against a push to main. Those created the following tagged version https://github.com/Starttoaster/ci-playground/pkgs/container/ci-playground

Closing. I think there's a lack of interest here. I'm just going to own my fork of this repo with security patches :)


How to generate json file in result folder

Hi there,
I'm trying to run recoder on other projects, but I found that the run.py requires to load data at
classcontent = json.load(open("../result/%s.json" % idss, 'r') )
Is there a way to generate such json file for other projects?

I have uploaded the corresponding file.


Load existing models

What is the best way to upload a pth model (a model that was trained somewhere else)?

You should be able to load the model with NN.Module.Load.


Drone: Update README.md

Remove duplicate line

/assign @seanknox

/assign @colinhoglund

Please update the chart version to 0.3.2 in the file Chart.yaml and this will be ready to be merged.

Done :)

Already merged in https://github.com/kubernetes/charts/pull/3594, this PR can be closed.
Thank you anyway for pointing out that typo in the documentation!

Allright, thank you for merging it!


Updates to 'setup.py' for the 0.21 release

Update the supported Python versions
Change Development Status to 4 - Beta
Apply Black formatting
Add python_requires=">=3.5"

Tested against TestPyPI, all good, so I'm going to merge this.

Tested against TestPyPI, all good, so I'm going to merge this.


Not working on Kiwi Browser

Tried it on kiwi browser and it's not working, it just gives the use Edge browser or use the bing app prompt. Doesn't make a difference if I sign in or not.

Yep

#119


Support Circuit Breaker

Description:
Add Circuit Breaker support to BackendTrafficPolicy.

@Xunzhuo - Can you assign this task to me?

need user doc

Track in https://github.com/envoyproxy/gateway/issues/2125


ntrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
H5 启动warning  在哪里修改

@robin-ming
在 prod 文件下添加这一句

webpackChain (chain) {
  chain.performance.set('hints', false);
}

好的  试了下 可以  谢啦
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年7月27日(星期六) 中午12:36
收件人<EMAIL_ADDRESS>抄送: "Ice✨"839786983<EMAIL_ADDRESS>主题: Re: [yinLiangDream/mp-colorui] ntrypoint size limit: The followingentrypoint(s) combined asset size exceeds the recommended limit (244 KiB).This can impact web performance. (#3)
@robin-ming
在 prod 文件下添加这一句
webpackChain (chain) {   chain.performance.set('hints', false); }
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Cannot set property 'keyword' of undefined

Information:

Prism version: 1.21.0
Plugins: 'none'
Environment: Webpack

Description
Use prism-glsl import and see the error (works in 1.20.0).
Browser console:

Browser page (React error):

Example
Some React component:
import Prism from 'prismjs';
import 'prismjs/components/prism-glsl';

...

That's because GLSL depends on some other languages.
Our babel plugin can take care of those dependencies for you. import Prism from 'prismjs' will then return a Prism instance with all your languages, so you don't need to import any languages yourself.
Hope this helps.

@RunDevelopment Thanks for the response. Babel plugin does not suit me, because I don't use babel.
I found a simple solution and it works for me without plugin:
import Prism from 'prismjs';
import 'prismjs/components/prism-c';
import 'prismjs/components/prism-glsl';
...


Is this library dead?

There are unmerged pull request, open issues and it doesn't work with custom User models. I'd be happy to maintain it, as I need it for a project, but if it's dead I'd rather go with something else.

Pull request #119 should be landing soon (we've been using that branch in production for a while) which includes custom User model support and a bunch of other stuff.


fixed secret references and broker CRD

updated README with more details
Fixed CP CRD
Added secret required for Kafka REST

Sure will do.
On Thu, May 18, 2023 at 3:41 AM Moshe Blumberg @.***>
wrote:

@.**** requested changes on this pull request.
LGTM, do you think you can add a Tear down section?
—
Reply to this email directly, view it on GitHub
https://github.com/confluentinc/confluent-kubernetes-examples/pull/240#pullrequestreview-1432212251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHGTLP2B5RVQ2WRHW27AP3XGXHB7ANCNFSM6AAAAAAYAUTF6I
.
You are receiving this because you authored the thread.Message ID:
<confluentinc/confluent-kubernetes-examples/pull/240/review/1432212251@
github.com>

--
https://www.confluent.io
Confluent
Data in Motion
Kaufman Ng
Staff Customer Success Technical Architect
+1<PHONE_NUMBER>
Follow us:  Blog
https://confluent.io/blog?utm_source=footer&utm_medium=email&utm_campaign=ch.email-signature_type.community_content.blog
• Slack https://slackpass.io/confluentcommunity • Twitter
https://twitter.com/ConfluentInc • YouTube https://youtube.com/confluent

added teardown


updating horizontal spacing between icons + buttons

Microsoft Reviewers: Open in CodeFlow

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

This is a larger issue than at first glance. (The spacing between icons + text is different depending on component but we don't have that logic in place yet, so modifying this will modify all spacing between icon + text)


Unable to create build after upgrading to<EMAIL_ADDRESS>

I have updated my package in the React Application to<EMAIL_ADDRESS>On npm start, the application is working but while creating the build, it is throwing the following error.

Output:-
Creating an optimized production build...
Failed to compile.
static/css/main.c713e34d.css from Css Minimizer plugin
Error: Unexpected '/'. Escaping special characters with \ may help.

Reopening the issue with more details.


typo: unecessary -> unnecessary

What does this PR do?
unecessary -> unnecessary
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?
Make sure you had fun coding 🙃

closing in favor of https://github.com/PyTorchLightning/pytorch-lightning/pull/5018


Add Google Search Console

Description

This pull request adds a plugin for Google Search Console, which allows you to view your site performance and indexing status inside Framer.

Thanks! was merged in #45


black does not modify malformed files

Environment data

VS Code version: 1.62.2
Extension version (available under the Extensions sidebar): v2021.10.1336267007
OS and version: macOS 11.6 (M1)
Python version (& distribution if applicable, e.g. Anaconda): 3.8.9
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A
Relevant/affected Python-related VS Code extensions and their versions: ms-python.python
v2021.10.1336267007,
ms-python.vscode-pylance v2021.10.1
Value of the python.languageServer setting: default

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
Formatting the document should reformat the document with "black".
Actual behaviour
The document is not modified.
Steps to reproduce:

Set "black" as the python formatter
Configure the editor to format on save
Save a python document with many pep8 violations
Note that the file does not change
Note that black is clearly called in the logs

Logs
User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'PythonPyTorchProfiler'
User belongs to experiment group 'pythonDeprecatePythonPath'
User belongs to experiment group 'pythonSortEnvs'
User belongs to experiment group 'pythonRunFailedTestsButtonDisplayed'
User belongs to experiment group 'pythonRefreshTestsButtonDisplayed'
User belongs to experiment group 'pythonRememberDebugConfig'
> conda info --json
> /usr/bin/python ~/.vscode/extensions/ms-python.python-2021.10.1336267007/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2021.10.1336267007/pythonFiles/interpreterInfo.py
> /usr/lib/python2.7 ~/.vscode/extensions/ms-python.python-2021.10.1336267007/pythonFiles/interpreterInfo.py
Python interpreter path: /usr/bin/python3
Starting Pylance language server.
> conda --version
> /usr/bin/python3 -m black --diff --quiet ~/Repositories/cad-processing/src/__init__.py
cwd: ~/Repositories/cad-processing
> /usr/bin/python3 -m black --diff --quiet ~/Repositories/cad-processing/src/__init__.py
cwd: ~/Repositories/cad-processing
> /usr/bin/python3 -m black --diff --quiet ~/Repositories/cad-processing/src/__init__.py
cwd: ~/Repositories/cad-processing

Note
Dup of #14078

@chriskuech Please share the code that is not working. Issues like this are hard to reproduce without a specific code to repro it.

@chriskuech could you also copy here the terminal output when you run /usr/bin/python3 -m black --diff --quiet ~/Repositories/cad-processing/src/__init__.py in the terminal directly?


Costs on 1.12

I´m using CommandSign version : 1.5.5 and CraftBukkit version git-Spigot-d5dfb24-ed8c725 (MC: 1.12)
If i setup costs for a sign, the player gets nothing withdraw.
Config: https://pastebin.com/Sn52qVzR

I have made some tests to be sure.
It is working for me.
Thus I have two questions:
What plugin do you use for your economy ?
Who is the player testing the command sign ? Is it you ? Are you op ? By default, OPs don't pay for the use a command sign.

Oh, Sry.
Yes the group have the command sign admin permission.