Client does not check result of blade operations for errors

Running ruby client and got errors when attempting blade.execute on signalwire.setup and call.receive and blade.subscription on notification channel.  These errors should be checked.  They are not so the client believes it has successfully connected to SignalWire.
<13>:ruby tts.rb
I, [2019-08-11T09:02:14.547971 #19562]  INFO -- SignalWire: Starting up TTSConsumer
D, [2019-08-11T09:02:14.548228 #19562] DEBUG -- SignalWire: Connecting to wss://relay.signalwire.com
D, [2019-08-11T09:02:14.548363 #19562] DEBUG -- SignalWire: Running with epoll true
D, [2019-08-11T09:02:14.869401 #19562] DEBUG -- SignalWire: SEND: {
  "method": "blade.connect",
  "params": {
    "version": {
      "major": 2,
      "minor": 1,
      "revision": 0
    },
    "authentication": {
      "project": "xxxxxxxxxx",
      "token": "xxxxxxxxxxx"
    }
  },
  "jsonrpc": "2.0",
  "id": "e674cd4f-bed9-434f-895a-9e6002ae4761"
}
D, [2019-08-11T09:02:14.923471 #19562] DEBUG -- SignalWire: RECV: {
  "jsonrpc": "2.0",
  "id": "e674cd4f-bed9-434f-895a-9e6002ae4761",
  "result": {
    "session_restored": false,
    "sessionid": "c92d57b6-d2fc-4d4f-b216-2a1f797a69dc",
    "nodeid": "82f8d536-9558-4bba-bc1f-d76d760ba16e",
    "master_nodeid": "00000000-0000-0000-0000-000000000000",
    "authorization": {
      "project": "xxxxxxxxxxxx",
      "expires_at": null,
      "scopes": [
        "calling",
        "messaging"
      ],
      "signature": "xxxxxxxxxx"
    },
    "routes": [

    ],
    "protocols": [

    ],
    "subscriptions": [

    ],
    "authorities": [

    ],
    "authorizations": [

    ],
    "accesses": [

    ],
    "protocols_uncertified": [
      "signalwire"
    ]
  }
}
I, [2019-08-11T09:02:14.943740 #19562]  INFO -- SignalWire: Blade Session connected with id: c92d57b6-d2fc-4d4f-b216-2a1f797a69dc
D, [2019-08-11T09:02:14.943881 #19562] DEBUG -- SignalWire: Relay client connected
D, [2019-08-11T09:02:14.949873 #19562] DEBUG -- SignalWire: SEND: {
  "method": "blade.execute",
  "params": {
    "protocol": "signalwire",
    "method": "setup",
    "params": {
    }
  },
  "jsonrpc": "2.0",
  "id": "fbf5def2-134a-4097-83cb-7fb723639831"
}
D, [2019-08-11T09:02:15.008500 #19562] DEBUG -- SignalWire: RECV: {
  "jsonrpc": "2.0",
  "id": "fbf5def2-134a-4097-83cb-7fb723639831",
  "error": {
    "requester_nodeid": "82f8d536-9558-4bba-bc1f-d76d760ba16e",
    "responder_nodeid": "ae6970c1-b3c6-437a-8d44-fad9e65424d3",
    "code": -32003,
    "message": "Certified clients are not permitted to setup relay protocols"
  }
}
D, [2019-08-11T09:02:15.008917 #19562] DEBUG -- SignalWire: Protocol set up as
D, [2019-08-11T09:02:15.009358 #19562] DEBUG -- SignalWire: SEND: {
  "method": "blade.subscription",
  "params": {
    "protocol": null,
    "command": "add",
    "channels": [
      "notifications"
    ]
  },
  "jsonrpc": "2.0",
  "id": "892cc01d-6ca0-4e96-aaec-4ec261d67ab0"
}
D, [2019-08-11T09:02:15.054812 #19562] DEBUG -- SignalWire: RECV: {
  "jsonrpc": "2.0",
  "id": "892cc01d-6ca0-4e96-aaec-4ec261d67ab0",
  "error": {
    "code": -32602,
    "message": "Invalid SubscriptionParams"
  }
}
D, [2019-08-11T09:02:15.055347 #19562] DEBUG -- SignalWire: Subscribed to notifications for
D, [2019-08-11T09:02:15.056154 #19562] DEBUG -- SignalWire: SEND: {
  "method": "blade.execute",
  "params": {
    "protocol": null,
    "method": "call.receive",
    "params": {
      "context": "tts"
    }
  },
  "jsonrpc": "2.0",
  "id": "6ad7d15f-2745-43ad-8831-c01f0ecead43"
}
D, [2019-08-11T09:02:15.103992 #19562] DEBUG -- SignalWire: RECV: {
  "jsonrpc": "2.0",
  "id": "6ad7d15f-2745-43ad-8831-c01f0ecead43",
  "error": {
    "code": -32602,
    "message": "Invalid ExecuteParams"
  }
}
E, [2019-08-11T09:02:15.104731 #19562] ERROR -- SignalWire: Unknown Relay command failure, result code not found
I, [2019-08-11T09:02:15.105067 #19562]  INFO -- SignalWire: Connected to SignalWire!
 ^CI, [2019-08-11T09:04:23.572414 #19562]  INFO -- SignalWire: TTSConsumer Consumer shutting down.

@lpradovera this is a priority. I'd like to get this in with all the other fixes and release a new patch-level ruby SDK tomorrow.

Fixed in #42


compression not working

running a lighthouse audit gives a very poor performance rating(in single digits). Is compression enabled for the for the react front end?

This example app is made to present a minimal app that builds & runs using Heroku, a starting point for Heroku deployment.
Everything this example app does is right there in the JavaScript code.
Setup Express with compression if you desire… it's not part of this all-in-one design example.


Add support for facets

resonite does not see them as facets. because facets were rewored between neos and reso


Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: TypeError
Error Message: Cannot read properties of undefined (reading 'createClient')
Version: 0.24.8
OS: darwin
OS Release: 22.3.0
Product: Visual Studio Code
Product Version: 1.76.2
Language: en

Call Stack
extension.bundle.js:2:3774915
fulfilled extension.bundle.js:2:3773586

The fix for this bug has been merged and is waiting to be released in the Azure Resources extension. https://github.com/microsoft/vscode-azureresourcegroups/pull/642

This issue has been fixed by the 0.7.0 release of the Azure Resources extension. Please update the Azure Resources extension to version 0.7.0.


Webring violations

The following sites have missing webring icons:

https://travisshears.com/ (@BTBTravis)
https://felipecortez.net/ (@FelipeCortez)

@BTBTravis and @FelipeCortez please react to this issue and include the icon on your site, as mentioned in the readme, if you still wish to be part of the Webring. Otherwise your sites will be removed. ✌

Beep boop. I think we should remove them for now. They can resubmit a pull request if they wish to rejoin the ring. :)

Updated site and forgot to keep ring. My bad thanks for letting me participate.


Include Healthcheck

It would be nice for the container to have a health status.
Here is what I have come up with in compose, but maybe there is a better way and I think it would be great to have the healthcheck included in the image itself.
services:
  database:
    image: sath89/oracle-12c:r1
    healthcheck:
      test: ["CMD-SHELL", "if [ \"`echo \\\"SELECT ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME = 'ANONYMOUS' AND ACCOUNT_STATUS = 'EXPIRED';\\\"|/u01/app/oracle/product/12.1.0/xe/bin/sqlplus -S sys/oracle as sysdba|grep ACCOUNT_STATUS`\" = \"ACCOUNT_STATUS\" ];then true;else false;fi"]
      timeout: 3s
      interval: 30s
      # start_period: 900s
      retries: 30

"start_period" is commented out because https://github.com/docker/cli/pull/475 has been merged but not released yet so compose doesn't support it (yet). "interval" and "retries" can be modified.

This variant seems to work too:
      test: echo "select * from v\$database;" | sqlplus -S sys/oracle as sysdba || exit 1
      timeout: 3s
      interval: 30s
      start_period: 10s
      retries: 30

@MaksymBilenko regarding existing comment what do you except with help wanted flag?
I think we could use one of them test and include inside Dockerfile

I have written a separate service to monitor oracle database to serve this purpose. If you need help configuring please feel free to raise an issue:
https://github.com/tjheslin1/Patterdale


[Feature]: Loosen permissions

New feature you are looking for
Only let Administrators see certain parts of the website per Russ

Volunteers need access only to the Terminal tab and PtW tab and Library tab. But when they click a game on the Library tab (and I assume PtW tab once it it populated), they cannot delete/add/hide.

Any additional context or links?
No response

Fixed in c29ff21


[@vue/compat] Prevent local asset registration from affecting other local apps (fix #5699)

Closes #5699. Because applySingletonAppMutations copies the reference of the singleton context instead of a copy of it, all local asset registration into any local app modifies all other local apps both post-facto and globally. My initial take at solving this was to simply create a shallow copy of the singleton app context instead of copying the reference, but then I realized the existing implementation allows for code like the following to work:
const app = createApp({ template: '<foo />' });
Vue.component('foo', /* some impl */);
app.mount(...); // resolves 'foo' from the global registry even though it was created after the fact

I'm not sure if this is behavior we wanted or meant to have, but in the interest of not breaking anything, I added a test for both the original issue and this one, and fixed both by using a proxy setup which first attempts to resolve components from the singletonApp registry, and if that doesn't work it instead resolves them from the local one. This implementation passes all tests. (If we're not interested in preserving the old behavior of allowing post-facto global registrations to affect local apps, then we can strip off the latter two commits and use the much simpler shallow copy implementation).

I got a notification that e2e tests failed. this test is the culprit, but all the e2e tests pass locally. is something amiss?

I simplified to logic to still pass the test.
Note that:

In the mixins case, the proxy won't be able to mimic the same behavior as objects. Currently it's a simple clone so it won't cover late-applied global mixins for now.

This actually doesn't fix #5699 - it's a separate bug. See 2f07e346

oh nice. using the singleton app's context as the prototype makes for a pretty natural solution. looking forward to the release for this!


Update Jython to latest 2.7.2

Update in our code here:  https://github.com/OpenRefine/OpenRefine/blob/3ca08f6ff189cc1bd806a1d49d2ead538882c0e2/extensions/jython/pom.xml#L124
New features and bugs fixed in Jython 2.7.2 since 2.7.1 are here:
https://github.com/jythontools/jython/blob/v2.7.2/NEWS

Generally speaking we should set up tooling to notify us of newer versions of our dependencies (and potentially create a PR to update them). I suspect that might be available for Maven-based projects like ours.

@wetneb Cool!  I haven't kept completely up-to-date with Maven3 abilities for that.  But sounds useful if Maven can do that for us automatically somehow.... hmm, but then how to notify?  Maybe just do something simple like, part of a Build Failure during CI?

But we don't want to fail every time just because of an outdated library.
Ah, we can generate a report...then send that somewhere...
https://blog.pchudzik.com/201703/how-to-keep-dependencies-up-to-date/

I've used Dependabot for Python dependencies and it looks like there's a Java version too
https://dependabot.com/java/
There's also this vulnerability scanner , but if dependabot's vulnerability scanner  is robust enough, we can just use that.

I've done the initial setup. Dependabot's Java/Maven support is still in beta, so we should check the PRs extra carefully. It will limit itself to 5 open PRs until we clear the initial backlog. I haven't looked at the Maven structure in detail, so don't know if we'll need to separately add the subproject pom.xml, but we should have enough PRs to keep us busy for a little while with the initial setup.

Returning to our original scheduled topic...
The Jython 2.7.2 release was back on March 21, so hopefully any critical bugs have been discovered and I didn't see anything worrying in a quick scan of their issues list for recently submitted bugs. The only potential problem I saw was https://github.com/jythontools/jython/issues/178 but I don't think the JAR within a JAR case applies to our packaging.
2.7.1 is 2 1/2 years old, so this provides a reasonable increment of bug fixes and cleanups, particularly with regard to working the same as CPython.

Agree, I don't think it will be a problem.... BUT, I cannot get our JythonEvaluable tests to even work without causing Maven errors.  Are our test classes working for the Jython extension on your side?
Given:  mvn verify -f "e:\GitHub Repos\OpenRefine\extensions\jython\pom.xml"
Result:
...
{snip}

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
[TestNGClassFinder] Warning: Can't link and determine methods of class com.google.refine.jython.JythonEvaluable
[ERROR] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.45 s <<< FAILURE! - in TestSuite
[ERROR] testWrappedObjectsHaveAttributes(com.google.refine.jython.JythonAttributeTest)  Time elapsed: 0.017 s  <<< FAILURE!
java.lang.Error:
Unresolved compilation problems:
        Row cannot be resolved to a type
        Row cannot be resolved to a type
        Cell cannot be resolved to a type
        Cell cannot be resolved to a type
        The constructor JythonHasFieldsWrapper(HasFields, Properties) refers to the missing type HasFields
        Evaluable cannot be resolved to a type

        at com.google.refine.jython.JythonAttributeTest.testWrappedObjectsHaveAttributes(JythonAttributeTest.java:34)

I've done the initial setup. Dependabot's Java/Maven support is still in beta, so we should check the PRs extra carefully. It will limit itself to 5 open PRs until we clear the initial backlog. I haven't looked at the Maven structure in detail, so don't know if we'll need to separately add the subproject pom.xmls, but we should have enough PRs to keep us busy for a little while with the initial setup.

@tfmorris: this looks very nice and handy! Thanks for this, it can really help and make things easier. Kudo.
Regards,
Antoine


New version: InfiniteRed.Reactotron version <IP_ADDRESS>91

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

/AzurePipelines run


Hey, I just added my profile in the profiles directory

Hey Nirbhay, I just added my profile in the profiles directory.


Type forwarding

This implements API for type forwarding - heavily inspired by https://github.com/AliSoftware/Dip/wiki/type-forwarding.
These changes should be backwards compatible for standard Swinject users, however there are breaking changes in the _Resolver._resolve and Container._register methods - which might affect Swinject extensions using this methods (SwinjectStoryboard, SwinjectAutoregistration).

👍

I've added the documentation to this API.
@yoichitgy What do you think? Do you have some ideas for the API / implementation improvements?
As mentioned above, in order to implement this feature I had to change the signature of some public methods - even though they should not be used by regular users of the Swinject. Do you think we can release this with the 2.3.0 in spite of these breaking changes?

I think it's acceptable to release it as 2.3.0 if the methods have documentation comments telling they are used only for extensions like SwinjectStoryboard 👍


Customize api for paging

Hi Ripple Team,
I have a problem, that I have a medical device to automatically  push vitalsigns information up RippleOsi, so a lot of data is posted up.
When I call api /api/patients/:idpatient/vitalsigns to get the data, the data returns very slowly and many records.
So I want to customize the api to reduce load and paging, for example /api/patients/:idpatient/vitalsigns?start=5&limit=10
Then the result returned 10 records and started from order = 5, but I can not do it.
Also, I also want to customize for the other api: patients, procedures, events ....
Can the Ripple Team be customized to help me or have any other solution?
Thanks and Best Regards.
Quan Nguyen from ThinkLabs-VN

thanks @maxcda101
Sorry for delay on the reply here, we've been busy launching websites etc
See  http://ripple.foundation/ & links to sites for our Documentation plus PulseTIle, QEWD, EtherCIS & related documentation
We can offer to help but would need you to sponsor this work at the moment, its not a priority for us.
If you prefer to review the related code/documentation for this area and suggest an approach, we may be able to guide you as to a solution you can craft and then submit.
Hope that helps?
Tony

thanks Tony
On this issue I have resolved already.
But you should customize the api retrieve data from ethercis, when the data up very large will cause the system to slow down.
Quan Nguyen from ThinkLabs-VN

thanks Quan Nguyen
You say resolved?
Is that something you're submitting a pull request on /need to discuss
further here?
re " customize the api retrieve data from ethercis" .. assume you mean on
the Qewd-Ripple side?
If so what changes do you suggest to the codebase?
thanks
Tony
On 26 June 2017 at 08:07, Nguyen Quan<EMAIL_ADDRESS>wrote:

thanks Tony
On this issue I have resolved already.
But you should customize the api retrieve data from ethercis, when the
data up very large will cause the system to slow down.
Quan Nguyen from ThinkLabs-VN
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RippleOSI/Ripple-Qewd/issues/31#issuecomment-310979854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5X3Lk963eR9OLNrv8MZc442fXeZAMLks5sH1iXgaJpZM4Nz24Q
.


[FT] Run on Server using Python API

Solution/Feature
Ability to Run on Server using Python API

Hi! You can already use running TGI containers as indicated here

Hi! Can you describe a bit more what you would like to see? You can run on server using a model config from a model path, no?

Hi, thanks for the follow up.
Ate you saying we can simply pass a tgi config yaml file to model_config
param of Pipeline class like below?
Could you please provide a minimally reproducible example since I belive
this scenario is not covered in the docs. Thank you!

pipeline = Pipeline(
        tasks=task,
        pipeline_parameters=pipeline_params,
        evaluation_tracker=evaluation_tracker,
        model_config=config.yaml,
        custom_task_directory=None, # if using a custom task
    )

On Mon, Dec 9, 2024, 5:03 AM Clémentine Fourrier @.***>
wrote:

Hi! Can you describe a bit more what you would like to see? You can run on
server using a model config from a model path, no?
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/lighteval/issues/424#issuecomment-2527203461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTMY3OTCFXSVVB2T5UHEED2EVFFRAVCNFSM6AAAAABTDUBRXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRXGIYDGNBWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix OCC.

I have never been able to get OCC/mechanisms to compile, let alone get the tests running. So I finally decided to check it out.  These were the changes I had to make.  The only one I am not sure about is the call to math_BrentMinimum, which seems to be different from the API specified for either OCC 6.9.0 or 7.1.0.
For users of mechanisms, please check that this doesn't break something, maybe it was different on old versions.  The environment I have used for testing is from https://github.com/siconos/siconos-tutorials/blob/master/Dockerfile-with-mechanisms and therefore uses OCE and PythonOCC from github.

Le 11 mai 2017 à 20:45, Stephen Sinclair<EMAIL_ADDRESS>a écrit :
I have never been able to get OCC/mechanisms to compile, let alone get the tests running. So I finally decided to check it out. There were the changes I had to make. The only one I am not sure about is the call to math_BrentMinimum, which seems to be different from the API specified for either OCC 6.9.0 https://www.opencascade.com/doc/occt-6.9.0/refman/html/classmath___brent_minimum.html or 7.1.0 https://www.opencascade.com/doc/occt-7.1.0/refman/html/classmath___brent_minimum.html.

just one more info:
last time I tried to install mechanisms,  I need to downgrade oce/pythonoccI to use it with siconos :
oce —> git checkout OCE-0.16.1
pythonocc —> git checkout 0.16.5
did you succeed with the last version?

For users of mechanisms, please check that this doesn't break something, maybe it was different on old versions. The environment I have used for testing is from https://github.com/siconos/siconos-tutorials/blob/master/Dockerfile-with-mechanisms https://github.com/siconos/siconos-tutorials/blob/master/Dockerfile-with-mechanisms and therefore uses OCE and PythonOCC from github.
You can view, comment on, or merge this pull request online at:
https://github.com/siconos/siconos/pull/139 https://github.com/siconos/siconos/pull/139
Commit Summary
[mechanics occ] Update calls to math_BrentMinimum API.
[mechanics occ] Fill in definitions of specialized contactFaceFace/contactFaceEdge
[mechanics occ] fix WhichGeometer call in OccTest.cpp
[mechanics occ] fix testOcc for when no offset specified to OccBody
File Changes
M mechanics/src/mechanisms/CADMBTB/mymath_FunctionSetRoot.cxx https://github.com/siconos/siconos/pull/139/files#diff-0 (6)
M mechanics/src/occ/Geometer.hpp https://github.com/siconos/siconos/pull/139/files#diff-1 (24)
M mechanics/src/occ/OccBody.cpp https://github.com/siconos/siconos/pull/139/files#diff-2 (29)
M mechanics/src/occ/test/OccTest.cpp https://github.com/siconos/siconos/pull/139/files#diff-3 (2)
Patch Links:
https://github.com/siconos/siconos/pull/139.patch https://github.com/siconos/siconos/pull/139.patch
https://github.com/siconos/siconos/pull/139.diff https://github.com/siconos/siconos/pull/139.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/siconos/siconos/pull/139, or mute the thread https://github.com/notifications/unsubscribe-auth/AHbsU5_5-YgFQDM9BNcku_J5eoKexUrqks5r41c9gaJpZM4NYZrh.

Ah that explains my previous failures.  Sorry if it was mentioned somewhere and I did not notice.
But yes, with this PR, I am able to compile against git master versions of both repositories.  However, I can only confirm it compiles and that OccTest.cpp runs correctly.  I am not familiar enough with Mechanisms to test it fully.


gb build a binary with given name

Similar to "go build" supports -o flag, I feel it would be better if "gb build" supports specifying binary name:
gb build -o myserver package/.../crm_server
Thanks.

Can you please explain why you need this feature. See #97

The main reason is to use gb with bazel. In bazel, a best practice is that the binary name is the same as the target name, and target name can be anything (might different from the folder containing main package). This is important because the built binary might be used by other targets, like a target to build deb file.

If gb were to place binaries into $PROJECT/bin/$GOOS/$GOARCH would this satisfy your requirement ?

No. In bazel the binary would be in a folder as follows (suppose the bazel target is //src/x/y/z:my_binary):
$Project/
|- bazel-bin/
|      |- src/
|           |- x/
|               |- y/
|                   |- z/
|                       |- my_binary
|- src/
|- x/
|- y/
|- z/
|- main.go

I'm sorry, I was confused, I thought you were talking about this
https://bazil.org/fuse/ project.
It looks like bazel has a prescribed project layout which is incompatible
with gb's layout. I'm not sure adding extra flags to gb to make it put
things in the places bazel expected is the right solution. I think bazel
should build Go projects directly without shelling out to gb. What do you
think about that suggestion ?
On Wed, Aug 19, 2015 at 12:01 PM, linuxerwang<EMAIL_ADDRESS>wrote:

No. In bazel the binary would be in a folder as follows (suppose the bazel
target is //src/x/y/z:my_binary):
$Project/
|- bazel-bin/
| |- src/
| |- x/
| |- y/
| |- z/
| |- my_binary
|- src/
|- x/
|- y/
|- z/
|- main.go
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/309#issuecomment-132415699.

You are right, bazel (http://bazel.io) has its own project layout. But currently bazel team hasn't determined how to support golang in bazel so that it works for both Google internal and external projects. So the status quo now is that bazel has no golang support at all. But I really want to use both gb and bazel.  Also, I guess even if bazel added go build support it wouldn't support go vendoring, thus I still need gb to handle the vendor fetch.

Closing as I don't think there is much more to do here. Bazel has one way it wants to build, gb has another, I don't think either are going to change much in the future.

I've come to a particular use case for this feature: building a project with arbitrary tags leads to a binary name including those tags, for instance:
gb build -tags "disable_mysql disable_postgres" cmd/controller

builds a binary named controller-disable_mysql-disable_postgres, which is quite unpleasant. Could you please reconsider implementing the -o flag from go build?

Here is another detail in a similar scenario posted by @falzm, gb build -tags "prod enable_add_cluster" manager would produce binary with name manager-enable_add_cluster-prod, so gb sorts the tags before appending to the binary name.

I am closing this as won't fix. I do not wish to add -o as gb is project based, not package based. -o makes no sense when you consider a project may produce multiple executables.


Allow fetching specific devfile stack version

What type of PR is this:
/kind feature

What does this PR do / why we need it:
This PR allows fetching a specific devfile stack version.
Which issue(s) this PR fixes:

Fixes #6315
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
Try to fetch a Go/Springboot/Python devfile and select the version. Test with ACs described in https://github.com/redhat-developer/odo/issues/6315#issue-1452906773.

/override windows-integration-test/Windows-test
Flaky e2e test


Incomplete Allure Reporting on Errors in before and after Hooks

Description:
There is an issue with the Allure reporting in our Cypress tests where failures in the before and after hooks are not being logged correctly. Specifically:
Error in before Hook:
When an error occurs in the before hook, Cypress stops executing further tests in that suite.
The after hook still executes for cleanup purposes.
Execution of after Hook:
If the after hook executes without any errors, Allure correctly logs the failure details from the before hook.
However, if the after hook also encounters an error, Allure does not properly log the failure details from both the before and after hooks. This results in incomplete error reporting in Allure.
Steps to Reproduce:
Create a Cypress test suite with before and after hooks.
Introduce an error in the before hook.
Ensure the after hook also encounters an error.
Execute the test suite and observe the Allure report.
Expected Result:
Allure should correctly log the errors from both the before and after hooks.
Actual Result:
Allure logs the failure details from the before hook correctly if the after hook executes without errors.
If the after hook also fails, Allure does not log the errors correctly, leading to incomplete reporting.

I see that cypress itself cannot stand this behavior - and it doesn't output error

I'll trye to fix for adllure, but seems it is not so easy
I would suggest better do everything in before hooks

Thanks for the quick response @mmisty . Please try from your end, until then I will modify my code.
But if we can fix that, it would be helpful.

@chaitanyarajugithub JFYI,  this is related to cypress issue (which I've just created) https://github.com/cypress-io/cypress/issues/29762

should be fixed in v2.0.10

Thanks @mmisty for your quick support.


Crypto::Bcrypt + Crypto::Subtle

Mmh, it looks like there is a conflict with the Crypto::Base64.

Why Bcrypt needs its own Base64? What's the difference?
If you need a different Base64 algorithm for Bcrypt you can put it under BCrypt::Bae64, without modifying ::Base64. But if we can avoid having two Base64 types its better :-)

It has a different alphabet and decode table. Your algorithm for the Std::Base64 is specifically designed for the standard MIME-base64 encoding.


[3.9-MP] Revamp Measurement Panel Design: Update measurement panel to match segmentation panel design and add new features

What feature or change would you like to see made?
Revamp the design of the measurement panel to match the new design of the segmentation panel. This should include:

Displaying statistics
Better support for measurement hiding and locking

Why should we prioritize this feature?
The measurement panel has not been updated in a long time. Revamping its design to align with the modern segmentation panel will provide a more consistent and user-friendly experience. Additionally, adding features like measurement locking and better hiding support will enhance usability and productivity for users working with measurements.

https://github.com/OHIF/Viewers/issues/3898#issue-2084067952

@Ouwen I remember you had some ideas for this

Might be interesting to see https://github.com/OHIF/Viewers/issues/4041

https://github.com/OHIF/Viewers/pull/2773


Log when something is wrong

I think it would be nice to log error when some unexpected occurred 🙏

Released as 1.0.1 :+1:


Add Turkish News Category Dataset - 270K - Lite Version

This PR adds the Turkish News Categories Dataset (270K - Lite Version) dataset which is a text classification dataset by me, @basakbuluz and @serdarakyol.
This dataset contains the same news from the current interpress_news_category_tr dataset but contains less information, OCR errors are reduced, can be easily separated, and can be divided into 10 classes ("kültürsanat", "ekonomi", "siyaset", "eğitim", "dünya", "spor", "teknoloji", "magazin", "sağlık", "gündem") were rearranged.

Thanks for the change, merging now !


workaround for mississippi.finished (end-of-stream) intermitent failures

should fix https://github.com/zkat/pacote/issues/143

https://travis-ci.org/zkat/pacote/jobs/360064813 This seems to still be having intermittent failures on CI :(

hmm ENOPACKAGEJSON this time.
Am I right to assume that this can be triggered via the finalize-manifest.js code?
I have initially replaced finished in there as well, but got some errors that I didn't have the time to look into, and I also thought that the fix is over-reaching since my goal was fixing git clone
Commit https://github.com/zkat/pacote/commit/15e4ddf715e87e7746067a22e7a9d4c3c7e0e5b1
Travi CI run https://travis-ci.org/zkat/pacote/jobs/360057598

all green now

I hate heisenbugs, but we may as well try this out and see what happens :\

Any chance of having a pacote release? This way all my team mates can get to confirm or not that the fix is working


Remaining references to traffic_ops_ort in the documentation

I'm submitting a ...

bug report

Traffic Control components affected ...

Documentation

Current behavior:

After #5826, there are still references to traffic_ops_ort in the documentation, mostly just filenames:
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/building.rst#L68
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/index.rst#L30
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.configuration.rst#L19
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.main_routines.rst#L20
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.packaging.rst#L19
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.rst#L21
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.rst#L30-L34
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.to_api.rst#L19
https://github.com/apache/trafficcontrol/blob/577eb63803b2c511d4c7ff29b69846d25dc457c6/docs/source/development/ort/traffic_ops_ort.utils.rst#L19
Expected behavior:

traffic_ops_ort_build is now cache-config_build.
Those RST files should be renamed:

docs/source/development/ort/traffic_ops_ort.configuration.rst
docs/source/development/ort/traffic_ops_ort.main_routines.rst
docs/source/development/ort/traffic_ops_ort.packaging.rst
docs/source/development/ort/traffic_ops_ort.rst
docs/source/development/ort/traffic_ops_ort.to_api.rst
docs/source/development/ort/traffic_ops_ort.utils.rst

The building rst was wrong, but the trafficcontrol/docs/source/development/ort are all autodoc for the Python script, which still exists.


Updated link for C sample

@codingwithcookie : Thanks for your contribution to the Azure documentation! The author, @fsautomata, has been notified to review your proposed change.

requested this update be merged -valid update


Add export for feedback provided on Find

Context
On the course and results page on Find, we give users the option to provide feedback. This is persisted to the Apply db, but we currently aren't exposing it via an export.
Changes proposed in this pull request

Add an export to for feedback provided on Find
Add docs

Guidance to review
Does linking to the page they were on seem reasonable? I could just expose the path/find_controller
Link to Trello card
https://trello.com/c/aIl3Z8AB/3329-add-an-export-for-findfeedback
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] This code does not rely on the addition/removal of Azure config environment variables in the same Pull Request
[x] New environment variables have been added to the Azure config

This ☝ is a new enum value so the warning can be ignored


Add ARPlaneManager

Take a look at
Assets/Samples/PolySpatial/Scenes/MixedReality.unity
Assets/Samples/PolySpatial/MixedReality/Prefabs/AR Default Plane.prefab uses Assets/Samples/PolySpatial/MixedReality/Scripts/PlaneDataUI.cs
This needs to be replaced.

arfoundation-samples/Assets/Scenes/PlaneDetection/PlaneClassificationLabeler.cs at 5.1 · Unity-Technologies/arfoundation-samples
https://github.com/Unity-Technologies/arfoundation-samples/blob/5.1/Assets/Scenes/PlaneDetection/PlaneClassificationLabeler.cs

https://github.com/styly-dev/STYLY-XR-Rig/pull/30


Secure Boot V2 and Certificate Update (IDFGH-12866)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello,
ESP32-S3,
https://docs.espressif.com/projects/esp-idf/en/v5.2.1/esp32s3/security/secure-boot-v2.html
if the Customer wants Time-Limited Root Certificates,
how can this be combined with Secure Boot V2 ?
so after 12 years, if the Root Certificate is no more Valid, is there a secure way to update the Certificate and also accept then the newly signed OTA Updates ?
Thanks,
Franz

The way that I understand it -- secure boot is independent from OTA.
Secure boot is a relationship between a secret burned into a fuses, and signature that is attached to the end of an application where the hardware verifies that the application matches that encoded information burned into the fuses.
An OTA has other credentials which are stored in NVS.   Those credentials provide the mechanism where the system can call into a IOT service, authenticate, and get what it needs.    Commonly, a software package will have a mechanism to fleet provision its credentials.    If something expires, its fleet provisioning process should be able to restart and re-authenticate automatically.
Secure boot (to my knowledge) just never changes.   AND you have the option if applying 3 signatures so that the developer can rotate through those 3 signatures should an attacker find a way to copy one of those signatures and build software that runs on your hardware.    Once those 3 signatures have been rotated through, that hardware exhausts its ability to boot software.  The secure boot process will not look externally for any authentication information.

@diplfranzhoepfinger
Need more information to better comment on your requirements here.
FWIW, Please take a look at this documentation section https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/security/security.html#managing-root-certificates for managing the root certificates on the device side. Please note that, this does not have any direct co-relation with secure boot scheme.

What would be the solution for such requirements, where the application signing key (and certificate) needs to be updated that often? Secure Boot V2 and it's limited key slots doesn't seem to fit the requirement.

trust boot involves verified chain. Chip code verifying bootloader, bootloader verifying app. if the app signing key is leaked then all executable on device shud be updated. how you plan manage early boot software update? best option is to keep bootloader signed with multiple keys and use revocation. it is not practical to manage multiple signing keys, at-least to not my experience... ..for our product we found HSM are best option to take care of signing key.

HSM you mean an external one or what we have in ESP32-S3 ?

@diplfranzhoepfinger  @metala
Sorry for slow turnaround on this topic.
Storing signing key on the device is not a recommended approach. Probably @kayzen9 meant using external HSM (either physical or cloud) for storing the signing key.  Please see few technical posts on this topic [1], [2].

What if the requirements impose that the SW signing keys needs to be rotated every X years? The limited number of secure boot digests and revocation bits in the eFuses are not enough.

I have not come across such a requirement. Could you please elaborate if its any certification specific requirement?
Our recommendation is to store the private keys in secure manner (e.g., FIPS 140-2 level3 compliant storage) and worst case there is a provision for fallback using revocation scheme on the device side. So-far in our experience, the 3 digest slots have been sufficient for most of the customers. We can consider any improvements based on your feedback.
Hope this helps!

OK, an external HSM, like:

Infineon: OPTIGA™ Trust X, there ist a devkit with ESP32 and SW Samples
ATECC608A like used in the Modules ESP32-WROOM-32SE

but not the HMAC or so which comes with the ESP32-S3 ?
right ?

https://blog.espressif.com/secure-signing-using-external-hsm-ebe855a2f2ef

https://blog.espressif.com/esp32-s2-security-improvements-5e5453f98590

The SSBL is verified using the Secure Boot V2 scheme and the PKI chain for the application is verified using the HSM public key from the SSBL signature block or hardcoded as part of the SSBL.

This should be possible by modifying the way 2nd stage bootloader verifies the application. It is possible to customize the 2nd stage bootloader, just that there is maximum size cap with secure boot enabled case.

OK, an external HSM

Yes, ideally it should be FIPS 140-2 level3 (reference) compliant.

but not the HMAC or so which comes with the ESP32-S3 ?

It is strongly recommended to store the signing key outside of the device.
Hope this helps!


nixos/hardware/ipu6: Improve the enable description

The module is doing muich more than just enabling the ipu6 kernel module, so extending the enable options scope to support for these camera modules seems a better fit.
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

typo in commit-message-body:
The module is doing _much_ more than just enabling the ipu6 kernel
module, so extending the enable options scope to support for these
camera modules seems a better fit.

otherwise LGTM


Maint: Hypervolume (pyhv.py) module rewrite

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue

This PR is related to the #366.
This PR rewrites the code that generates the hypervolume indicator, used for multiobjective optimization.
Any suggestions / comments / requests are very welcome.
The purpose is two-fold:

Rewrite / refactor the existing code to improve the general readability and extendability, spot possible bugs, and add documentation
Get rid of the LGPL licence in favour of the standard MIT licence, used by nevergrad.

How Has This Been Tested (if it applies)

(Tests are WIP)
We added some unit tests for the data structure that are used by the HypervolumeIndicator class, although the code coverage is still low. We are working on this.
We tested the main functionality of the new hypervolume algorithm against the old one. More integration tests should be included before this PR can be accepted.
Checklist

[ ] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[ ] All tests passed, and additional code has been covered with new tests.

I believe the mypy issues should be resolved now. The pytest tool is now complaining about something unrelated to the PR (I hope).
HypervolumeIndicator tests should be on the way, working on this now.

@jrapin Could you please have a look at this now? Most of the tests are ready, I guess it could be a good time for review and corrections, if you don't mind.
Thank you!

@teytaud anything to add?
@Corwinpro You can probably remove the pyhv file and the related license

I removed the old code and the license file. Would you like me to add anything?
Thank you!

Thank you very much for the review and the comments. I am ready to merge this if you are happy with all the changes.
Thank you!

Sorry for the delay, let's go then ;)


Display external cloud-provider services

When a Scope-monitored application connects to external cloud-provider services (e.g  RDS, S3, Dynamo ...) we simply display them as "the internet".
As a user I want finer grained information, ideally showing specific nodes for each service I am connecting to.

dup of #1082


Add more complex tests for the components

Currently only basic functionality of components is checked. We need better tests for the components.

#273 added many many tests, which i feel matches the specific letter of this ticket. As we move forwards we should make sure to put testing first, and not let it be something that can be relegated to a gh-issue to be dealt with at an unspecified later date.


Initial Commit of Nightscout applet

This is the Nightscout application for Tidbyt!  This originally spawned from a community request here.
Nightscout is an Open Source Continuous Glucose Monitoring application that is used by diabetics to monitor their blood glucose levels in real time.  This data is uploaded to the cloud, and can then be accessed using a simple REST API.
The app takes the data from the REST API (based on the user's ID), and then displays the trend arrow (one of double up, up, 45 degree up, flat, 45 degree down, down and double down), along with the current BG reading and a delta from the previous reading.
The arrow and current BG reading is color coded red, yellow or green based on the parameters passed to the application (see below for these thresholds).
If the current data is more than 15 minutes out of date, the arrow and current BG reading are coloured grey.

Argument Name
Description
Required / Optional
Default

nightscout_id
The Nightscout ID for the user
Required
None

normal_high
The normal high value - anything above this is considered yellow unless it is above the urgent_high
Optional
150

normal_low
The normal low value - anything below this is considered yellow unless it is below the urgent_low
Optional
100

urgent_high
The urgent high value - anything above this is considered red
Optional
200

urgent_low
The urgent low value - anything below this is considered red
Optional
70

I have read the CLA Document and I hereby sign the CLA
recheck

I get what you're saying  - someone could potentially call something
maliciously though (for example, if I put my ID as "maliciouswebsite.com#"
it would do bad things).
I can do a couple of things -

Validate the ID is only alphanumeric characters
A test call to https://XXX.herokuapp.com/api/v1/status.json first -
that's specific to the Nightscout API (
https://lk7.herokuapp.com/api/v1/status.json).
Blacklist any Tidbyt internal hostnames (if you can provide a list :) )

On Fri, Jan 14, 2022 at 3:15 PM Mark Spicer @.***>
wrote:

@.**** commented on this pull request.
In apps/nightscout/nightscout.star
https://github.com/tidbyt/community/pull/74#discussion_r785174546:

   )

Get the JSON object from the cache

nightscout_data_cached = cache.get(nightscout_id + "_nightscout_data")
if nightscout_data_cached != None:

   nightscout_data_json = json.decode(nightscout_data_cached)

   print("Hit - displaying cached data")

   # Pull the data from the cache

   sgv_current = int(nightscout_data_json["sgv_current"])

   sgv_delta = int(nightscout_data_json["sgv_delta"])

   latest_reading_dt = time.parse_time(nightscout_data_json["latest_reading_date_string"])

   trend = nightscout_data_json["trend"]

else:

   print("Miss - calling Nightscout API")

   nightscout_url = "https://" + nightscout_id + ".herokuapp.com/api/v1/entries.json"

This url created from user input makes me pretty nervous. We really want
to avoid the case where someone could make calls to another service that we
don't intend or even worse - make calls to our internal systems. Can we add
validation to ensure this is actually a valid ID for heroku? We could
either do it through inspection of the string or we could potentially use a
heroku API if they offer it?
—
Reply to this email directly, view it on GitHub
https://github.com/tidbyt/community/pull/74#pullrequestreview-853388113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXARD72AIVQAYKGEY6KZYUDUWCG7ZANCNFSM5L7XTQYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey @jer-tav! I can fix this up and push to your branch if that's ok? Might be easier then the back and fourth

@betterengineering - hey Mark, if you've got the time to do it, that would be great!  The last missing feature is to grab the location of the user via the schema and convert latest_reading_dt before displaying it, plus removing the fails I think.
Did you add number support to the schema as well?
I'm not likely to get a chance to look at it for another week or so with my current work commitments.

Updated! We don't yet have schema support for numbers, will get that added in the coming weeks and will get this updated.


importing methods from larch into a plugin

Save the following as $HOME/.larch/plugins/mymod.py
  from larch import use_plugin_path
  import numpy as np
  use_plugin_path('wx')
  from plotter import (_newplot, _plot)

  def someplot(_larch=None, **kws):
      x = np.linspace(0, 10, 101)
      y1 = np.sin(x)
      _newplot(x, y1)

  def registerLarchPlugin(): # must have a function with this name!
      return ('mymod', { 'someplot': someplot })

At the larch command line, do:
  larch> add_plugin('mymod')
  larch> someplot()
  file <stdin>, line 0
  AttributeError: 'NoneType' object has no attribute 'raise_exception'
      someplot()

The immediate problem is that importing _newplot as explained the other day on the mailing list does not seem to work as advertised.  Or, I suppose, I am not understanding the ad copy....
The other issue is that the error message is not so helpful.  It would, I think, be more helpful to have a backtrace to the point in the code that throws the exception.  It is not even clear from the error message that the _newplot(x,y1) line throws the exception.  (It does.  Comment it out, no exception.)

Plugins are now greatly discouraged...


Support boolean data in Cythonized groupby

reported by @bburan on the mailing list

In [146]: frame = DataFrame({'a': np.random.randint(0, 5, 10), 'b': np.random.ra
ndint(0, 2, 10).astype('bool')})

In [147]: print frame
  a  b
0  1  False
1  2  True
2  2  True
3  1  True
4  3  True
5  3  True
6  3  True
7  1  True
8  2  True
9  1  False

In [150]: frame.groupby('a')['b'].mean()
---------------------------------------------------------------------------
UnboundLocalError                         Traceback (most recent call last)
c:\users\brad\projects\sane\src\sane\scripts\<ipython-input-150-fceb5b21892e> in
 <module>()
----> 1 frame.groupby('a')['b'].mean()

C:\Python27\lib\site-packages\pandas\core\groupby.pyc in mean(self)
   297         For multiple groupings, the result index will be a MultiIndex
   298         """
--> 299         return self._cython_agg_general('mean')
   300
   301     def size(self):

C:\Python27\lib\site-packages\pandas\core\groupby.pyc in _cython_agg_general(sel
f, how)
   347             output[name] = result[mask]
   348
--> 349         return self._wrap_aggregated_output(output, mask)
   350
   351     def _get_multi_index(self, mask):

UnboundLocalError: local variable 'mask' referenced before assignment

Note that agg() does work:

In [153]: frame.groupby('a')['b'].agg(np.mean)
Out[153]:
1    0.5
2    1.0
3    1.0
Name: None, Length: 3

I would also (when appropriate such as for non-numeric column types), catch the UnboundLocalError and raise a different error message (e.g. NotImplementedError).  Some people may be perplexed by the UnboundLocalError and resulting traceback, but a NotImplementedError would hopefully be a clearer indication of what went wrong.

Definitely-- I'll take care of both of those problems

Took care of these two issues in the above commits


Add a topic for graceful shutdown and how it works in Kestrel

We should have a page that describes how graceful shutdown works in Kestrel (for both HTTP/1.1 and HTTP/2) and how it could be configured in various environments with a load balancer to gracefully drain traffic.
cc @Tratcher @halter73

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

ID: f22dcddb-0c25-be1a-9a02-9e71dce86bdb
Version Independent ID: 3e0e12c2-e544-5655-e001-d2ec180b11a8
Content: Kestrel web server implementation in ASP.NET Core
Content Source: aspnetcore/fundamentals/servers/kestrel.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Associated WorkItem - 66053

@Tratcher @halter73 can one of you write this draft?

Rough outline:

The Host receives a shutdown signal (e.g. CTL+C, StopAsync, etc.)
IHostApplicationLifetime.ApplicationStopping is signaled to notify the application. Long running operations should subscribe to this event.
The Host calls IServer.StopAsync with a configurable shutdown timeout (default 30s)
Kestrel (and Http.Sys) close their port bindings and stop accepting new connections. They also signal current connections to stop processing new requests. For HTTP/2 and HTTP/3 this involves sending a preliminary GoAway message to the client. For HTTP/1.1 requests are processed in order so it stops that connection loop.

IIS is a little different, it rejects new requests with a 503.

Active requests are given until the shutdown timeout to complete. If everything completes before the timeout then the server returns control to the host sooner. If the timeout expires then pending connections & requests are forcibly aborted which can cause errors to be reported in the logs and to the clients.

When working with a load balancer several steps can ensure a smooth transition of clients to a new destination.

Bring up the new instance and start balancing traffic to it (you may already be running several instances for scale purposes)
Disable or remove the old instance in the load balancer config so it stops receiving new traffic.
Signal the old instance to shut down
Wait for it to drain or timeout
(need specific examples for different environments)

Moved to https://github.com/dotnet/docs/issues/34879

Fixed in https://github.com/dotnet/docs/pull/35317


just for hacktoberfest 2k19

Thank you for your contribution. I left a comment.
Also you have seemed to created a conflict with yourself. The last commit seems to be cause both issues 🤓 - removing / undoing / fixing this commit 53803e5a983bc751ede1b7ae6b9bfb5a0a7877bd should solve everything. Any questions let me know.

Looks better, but I see your name is already on the list 😉 , it was made in this PR https://github.com/eddiejaoude/hacktoberfest-practice/pull/42/files


[GNSS-ZED-F9P node] error in ubx files generation

Acording to the configuration of the gnss the rawx and sfrbx are transmited on the usb port

The ubx file cant be converted by rtkconv

That's a great find, it's clearly byte-ordering error, probably from developing on x86_64 (little-endian) to run on ARM (big-endian)

Thanks for the great documentation on the bug, working on it ASAP.

ubx file are now readablewith this fix:
L.211 -> gnss_zed_f9p.h
//write frame to bin file
uint8_t sync[2];
sync[0] = 0xb5;
sync[1] = 0x62;

but we are still missing observation packets ( b5 62 02 15 )

when the payload is bigger than 255 bytes, there's a byte ordering problem and the packets doesn't get written.
the payloads always exceed 255 bytes for observations packets

Seems like a bug combo. lscpu shows that it's running in little-endian, so it's not an endianness bug, it appears that the bytes were just badly swapped at write time and that @patcmorneau 's fix solved that piece of the puzzle.
Furthermore, there was an issue in the binary read where the payload was not properly read. I noticed that we are using the read() syscall, which may not always return the proper amount of bytes. I've added a readSerial() method to handle this problem. Adding a check on incoming packets to find observation packets (b5 62 02 15) to print them out gives the expected result: Houston, we have obervation packets.
I'm going to be on the road, so could you please test that everything works with rtkconv and commit the codebase on the test hydroblock once confirmed?
Good job everyone!

Great!
Can we generate a RINEX through rtkconv?

the obs file was send to NRCAN for PPP
i'am waiting for the result

i just recive the repport
2022.pdf

fixed


rdma-core: 34.0 -> 35.0

Motivation for this change
https://github.com/linux-rdma/rdma-core/releases/tag/v35.0
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

The PR is based against against staging to prevent larger changes before the 21.05 branch-off.

Does the program has some kind of useful changelog? If there is not breaking change we can merge it into 21.05. Not like it is likely going to break the entire tree and with just a 100 rebuilds its also not big.

Does the program has some kind of useful changelog?

See link above in the description.
It contains numerous changes beyond simple bugfixes.

See link above in the description.

I already found this and thats why I asked for a useful changelog. Just listing all commits is not useful for me to assess if this can go 21.05 or contains breaking changes.

I already found this and thats why I asked for a useful changelog. Just listing all commits is not useful for me to assess if this can go 21.05 or contains breaking changes.

This is the only changelog the project provides. I suggest we merge it into staging, which is just easier at this point. There is no harm in putting through staging.

aarch64 failure looks to be with a dependency


[Delegation Permissions] RPC to get list of schema ids granted for delegator

on similar lines as #224 , we need  a Get operation
Blocked  by #224
As a provider I should be able to get a list of schema_ids granted for a delegator via RPC call
Acceptance Criteria.

[ ]  Add an RPC call to get a list of schema ids granted for a delegator by a provider
[ ] Update runtime and node/service to add RPC to runtime.
[ ] Tests

@saraswatpuneet
Is this a duplicate of https://github.com/LibertyDSNP/frequency/issues/316

@wilwade  how about now, do we need an RPC call if not we can close this issue as not needed

@saraswatpuneet RPC call is covered by https://github.com/LibertyDSNP/frequency/issues/226 So this is a duplicate (although I like this wording better, so I'll copy it over to the other one)


+1 icon: HATSUNE MIKU, +1 link

Fulfilling requests.
@Hamster45105 Testing #2071.
Added
HATSUNE MIKU: COLORFUL STAGE (com.sega.ColorfulStage.en/com.google.firebase.MessagingUnityPlayerActivity)
Linked
Download Navi (com.tachibana.downloader/com.tachibana.downloader.ui.browser.BrowserIcon → download_navi.svg)
Contributor's checklist

[x] I followed the Lawnicons Guidelines (upd. Jan 2024) and will make changes if someone suggests. I will also make sure that Lawnicons builds correctly.

The comment about the self-review requires a fix.

The comment about the self-review requires a fix.

#2096


Fixed notify happening before association is added to accept queue

When the server socket is operating in non-blocking mode, we wait for
the COMM_UP notification, and then call accept. However, the
association is not added to the accept queue until after the COMM_UP
notification is triggered. This causes the application to have to wait an
indeterminate amount of time and can cause race conditions when the
application calls accept before usrSCTP adds the association to the
accept queue.

Could you provide a minimal test program which doesn't work before you change and does work after it?

I'm working on something else currently, but if I can find some time I'll do that. Not sure how long that'll be though.

Hi @tuexen ... Apologies for the delay. I've created an example using the ekr example program. unzip and replace ekr_server.c, and run the server and client as normal. With the sleep, it spams the console with "usrsctp_accept: Resource temporarily unavailable" until the function returns and adds the association to the accept queue. Without the sleep, it depends on when the OS schedules the main thread to run - sometimes it fails until the second try, sometimes it works.
ekr_server.zip


[Feature Request] Improvement: Adjust cursor/caret color based on background

Is your feature request related to a problem? Please describe.
I love Notepads, it's great and feels very modern. I love using it to jot notes down because of the markdown support. The problem is, the blurred background which is so nice to look at makes it hard to see the caret/cursor when something bright/white is behind it. (Edit: I should mention, I'm on Dark Theme)
For example on a white background such as #FFFFFF, the color of the interface becomes #898989, and the caret itself is #7d7d7d. In bright environments, these colors are contextually similar enough to make it impossible to tell where the caret/cursor is on the screen sometimes. I've felt like the cursor disappeared entirely when it's not really true.
Describe the solution you'd like
I have noticed that on a dark background the caret is much brighter, a background of #111111 produces a #191919 interface and #e8e8e8 colored cursor. This means that the program already does adjust based on the background, but it seems more tailored for dark environments than bright ones.
I don't know how the cursor calculates the color but if it could just remain as bright as the text that's being displayed, that would be golden.
Describe alternatives you've considered
I don't know what kind of color curve would work best, but I have labbed it out and I found that if Notepads is sitting on a #eaeaea background it becomes quite nearly invisible. I assume the cut off is somewhere around there. Originally I was going to suggest giving the program a darker cursor once it reaches that point, but I realized that I could read the white text in that context perfectly fine. A darker cursor would not be a good idea.
Additional context
I've attached an image for your convenience, you can use this behind the program to test the cursor position. The middle color should make the cursor/caret disappear. I'm sorry if this problem has been discussed before but I didn't recognize any threads that have already talked about it.

Okay funny enough after editing my post a billion times in embarrassment I tried out the Light Theme to find it does have the same problem when used against a perfectly black background.
Here's the tester for Light Mode users. Should be the same problem as above: once you reach the middle color the cursor becomes very hard to see. Again, I'm not sure what the solution is but I think we can agree this it's a bit frustrating to use in this condition.

I'm closing this issue. I wrote this in haste, I didn't remember adjusting the opacity at one point. That is entirely the issue here and I can't expect a solution based on user error. Big sorry if I wasted your time on this.


Prepare to support Ruby 2.2 on Rails 3.2.22+

This is in preparation for the next patch release. Similar steps are
being taken by Rails core. See:
https://github.com/rails/rails/commit/8f92edb2b4b6beb5c778283be7cbcef6bf7e596c

LGTM

+1

An odd Test::Unit runner failer I was not previously seeing locally. Will need to dig into that. Also seems  a Ruby bug with something Travis CI has installed :frowning:

Please check, I have same issue too

Yep I get that error now. An update on one of the other repos is likely related. I'll look into and fix this today.

:+1:


Update Validation annotation documentation

The current docs did not make it clear that annotations that were a part
of the Default group had no affect if the Validation annotation did not
contain the Default group (explicitly or implicitly through
inheritance). See PR #2052 for more information.
This commit also adds test cases to make the current behavior explicit
so any regressions can be caught in the future.
Closes #2049
Closes #2052

Coverage remained the same at 84.524% when pulling 11101fe5d58f5c17667b74d9def92b59832edd05 on nickbabcock:group-validation-docs into c0d7379530df147c629b00798430bd73c8d7e7ab on dropwizard:master.

Suggestions applied 👏 🎉

Coverage remained the same at 84.524% when pulling 56bc0a25689807118f8452f9de83fb60988f8fa9 on nickbabcock:group-validation-docs into c0d7379530df147c629b00798430bd73c8d7e7ab on dropwizard:master.


If I want to increase functionality and scope

Hi Nicole,
I love the concept, but as said it is competing with a lot of other interfering extensions.
I wonder if I can get your insight about using this differently. Is there a way to communicate privately?
~in Latin~
this is an email that I used with my band years ago, doesn't mean anything :) but I know is not great :)
<EMAIL_ADDRESS>

sent you an email


Can't compile shader_version

Im getting this error when trying to compile the program:
Compiling shader_version v0.1.0
/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/shader_version-0.1.0/src/lib.rs:37:5: 37:90 error: the trait bound Self: std::marker::Sized is not satisfied [E0277]
/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/shader_version-0.1.0/src/lib.rs:37     fn pick_shader<'a, S: ?Sized>(self, shaders: &Shaders<'a, Self, S>) -> Option<&'a S>;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/shader_version-0.1.0/src/lib.rs:37:5: 37:90 help: run rustc --explain E0277 to see a detailed explanation
/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/shader_version-0.1.0/src/lib.rs:37:5: 37:90 help: consider adding a where Self: std::marker::Sized bound
/home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/shader_version-0.1.0/src/lib.rs:37:5: 37:90 note: required by Shaders
error: aborting due to previous error
Build failed, waiting for other jobs to finish...
error: Could not compile shader_version.
Any idea?

Right now i have no idea, cuz i dropped this repo about a year ago. Sorry. I'd like to continue development soon.

Yeah I see I just wanted to compile it and try it - I would even help but I don't have any knowledge of Rust.

I got the compiling working again. The dependencies were a real mess! (Still are) (And they are now ancient)
The game was for me only a black screen.


[VSCODE] Comma Position Setting Disappeared

Describe the bug
Comma Position setting disappeared (only have screenshot from Prettier SQL, but used to have it in SQL Formatter).
To Reproduce
Go to Extension Settings and search for Comma
Expected behavior
Comma position setting to allow having commas before SELECT and GROUP BY clauses.
Screenshots
Option available in Prettier SQL:

Option no longer available in SQL Formatter:

Usage

What SQL language(s) does this apply to? All of them

What VSCode version are you using?

Version: 1.84.2 (Universal)

Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e

Date: 2023-11-09T10:52:33.687Z

Electron: 25.9.2

ElectronBuildId: 24603566

Chromium: 114.0.5735.289

Node.js: 18.15.0

V8: <IP_ADDRESS>-electron.0

OS: Darwin arm64 22.6.0

What are your currently configured VSCode settings for the SQL Formatter VSCode extension, if relevant to the issue?
No configuration available.

The commaPosition setting has been intentionally removed in sql-formatter 14.0.0 and accordingly in the SQL Formatter VSCode extension 3.0.0.
I notice though that the README of the VSCode extension still lists the two removed config options.
Will fix the README.

Fixed in 3.0.1 of the VSCode extension.

Thanks so much for the quick reply—bummer, that was one of the most useful features for me. Is there any chance to request possibly a new implementation or something?

I'm open for a PR with new implementation. The existing implementation was just one big unmaintainable hack, which is why it was removed.

Ah makes sense—thanks for clarifying!


[VSCode extension] Provide autocompletion for style file, eg .css file

WindiCSS provides @apply autocompletion for style file, eg. .css file. It could be very nice if this feature includes in UnoCSS extension.

btw, I can contribute if someone can point me in the right direction.

+1
For now I just install the windicss intellisense extension and disable almost everything.
Would be nice to have some of its features in the unocss extension too


dns/bind: Add forwarding domains

dns/bind: Add a new tab 'Forward Zones' where you can add zones with the 'forward' type, for when you want to for instance forward queries to an Active Directory

I don't really know how to amend this but some improvement is possible in the descriptions; I used the Primary IPs field in the Domain object to store the servers to forward to ('forwarders' in the configuration file) but it could be called something else than 'Primary IPs' in the UI. Perhaps 'Destination IPs'?

@tinus-github I would recommend using Forwarder IP, based on the forward type zones definitions. Just like the slave zone calls them masters in the definitions, and the form refers to it as Master IP.
And thanks for working on this, I have been watching OPNSense/Plugins on github for this for a while, this is the last feature I need to make switch to OPNSense.

@mimugmail @pmhausen you guys interested in review? does it make sense? otherwise I'll close.

I'd like to postpone review after 23.7 is possible?

Same - "Land unter" as we say in German.

@mimugmail @pmhausen kindly asking for review again ;)
refs https://twitter.com/jurajlutter/status/1725096425279701456

At first glance LGTM (I don't have any testbed ATM, the change looks rather trivial though).

for when you want to for instance forward queries to an Active Directory

For AD, you'll most likely want something like validate-except { "corp.example.com"; }; if DNSSEC validation is enabled. Otherwise, it won't work (unless you are signing those, which is not the case for vast majory of users). Reference

Looking forward to this being implemented. Are there any plans to review and merge this anytime soon? (I think 23.7 was released quite a while back) ;)


Add various options to verify ssl/tls client cert including letting the application handle the authentication.

Add various options to verify ssl/tls client cert including letting the application handle the authentication.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This is ok to test.

Thanks much for the work on this and sorry it took that long to review.
We will also need some end to end testing of these features. See:
est/core/end2end/fixtures/h2_ssl.c for example.

Added an end to end test h2_ssl_cert.c which pretty much tries replicate simple_request test but deviates from the general programming paradigm followed in end2end fixtures/tests.

@jboeuf PTAL. I have added some more comments. Let me know if you wnat to go down the path of introducing a enum only header for security bits as suggested by ctiller

Thanks much for changes, especially for the test. I'm usually not a big fan of macros but I think that this is justified in this case.

LGTM - @jtattermusch will merge.
Jan, let me know if that's not the right procedure...

@jboeuf  yes, that's the correct procedure. Please add the "ready to merge" label once the tests have finished and then me or Nico will merge.

@jboeuf Seems like all checks have passed. Can you approve the change/add the "ready to merge" label. Thanks again for patiently reviewing the change

Done!


cstddef & cstdint?

When I try to compile it gives me the following error:
In file included from C:\Users\34683\OneDrive\Documentos\Cansat\CANSAT-PFe\CodigoArduino\CodigoArduino.ino:1:0:
C:\Users\34683\OneDrive\Documentos\Arduino\libraries\Bolder_Flight_Systems_MPU9250\src/mpu9250.h:36:10: fatal error: cstdint: No such file or directory
#include
^~~~~~~~~
compilation terminated.
exit status 1
Error compilando para la tarjeta Arduino Uno.

Please see the installation instructions, AVR microcontrollers such as Arduino Uno are not supported with the newest release of the library, you might try some older releases to see if they'll work for you.


Cannot test signals on non-node classes in C#

The used GdUnit4 version
4.3.3 (Latest Release)
The used Godot version
v4.3.beta3.mono.official [82cedc83c]
Operating System
Ubutu 24.04
Describe the bug
We're converting our GDScript to C# and we have some non-node classes with signals.  The GDScript unit tests written with GDUnit4 work fine.  But the C# unit tests error with the following:
line 0: Unable to cast object of type 'Fulcrum.Class.AgentsBase' to type 'Godot.Node'.
Also note that we are on GDUnit 4.3.4 - the actual latest release.  (Drop down in issue add page does not list this verson.)
Steps to Reproduce
Add a c# class with a signal based off a non-node class in Godot.
Write GDUnit test for it.
Run test.
Minimal reproduction project
No response

Thanks for reporting, can you please add an example of your test to reproduce


[DO NOT MERGE] Creates @magic-ext/react-native-app-attestation

📦 Pull Request
Creates @magic-ext/react-native-app-attestation and utilizes it with our React Native packages to run the check before rendering the WebView.
Although "code complete" this SHOULD NOT be merged until corresponding updates to Fortmatic BE are released.
** Note to Reviewers **

App Attestation utilizes Apple's Secure Enclave in the background to create the attestation object, as such, you will need to use an IRL device to test this PR. Check the notion doc for a breakdown on how to set that up. Thanks!

Related PR: https://github.com/magiclabs/magic-ios/pull/33

We'll add proper testing to the PR when the corresponding updates to Fortmatic BE are ready.

✅ Fixed Issues

[List any fixed issues here like: Fixes #XXXX]

🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!
Please only add one label:

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

Stale PR, will reopen if this project becomes a priority again.


fix: trim invoice

Describe the changes you have made in this PR
Trim the invoice
Link this PR to an issue
Fixes #1252
Type of change (Remove other not matching type)

fix: Bug fix (non-breaking change which fixes an issue)

How has this been tested?
Tested Manually
Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Is it possible to add a test for this?

I think we'll have to add a check for this after adding e2e tests for app screens

Is it possible to create a unit test which types in an address with spaces and the value will only be the address?

Pro: We have a basic unit test for this component
Contra: We're testing if trim works...

Not sure if we can add a unit test as we'll have to enter a value and then check... we do all that in e2e, right?

Not sure if we can add a unit test as we'll have to enter a value and then check... we do all that in e2e, right?

Currently we do not have e2e tests for this.
Regarding a unit-test I thought we could do i.e. type("  abc   ") and expect(...toHaveValue("abc")) after.
Does this make sense to you?

With the added commit form bumi let's add a unit-test

Thanks!


feat: select subtemplate based on the scheme used

Solves #65. It is not ideal, since I call find_template twice, but it gets the job done. I could change the find_template function to also receive the scheme as a parameter and give that back if a subtemplate with the scheme name is found, but well I'd like to first hear from you :)

Hello! Thanks a lot for the contribution :D
It's a very valid usecase.
I was wondering if perhaps we could make this more explicit and transparent instead of it being implicit behaviour. What if the user could use a {scheme} placeholder in their flavours configuration to refer to the scheme slug? That would make it work with any of the fields.
Would you be interested in making this change?

The shell option uses something similar to substitute the {} placeholder: https://github.com/Misterio77/flavours/blob/606817ef9d8e58235f37d19b1a5e1c340631e994/src/operations/apply.rs#L32

Hey sorry, I was on holidays and just now came back. Thanks for your feedback! Sounds like a good idea with the {sheme} placeholder to make it more explicit. I'll implement it over the weekend :) I'd keep the behaviour that if no subtemplate with the scheme name/slug is found, then "default" is selected.

Welcome back! Hope you rested well.

I'll implement it over the weekend

Thanks a lot!

Didn't get to it last weekend, but have implemented it now. The search for a scheme dependent subtemplate now only happens if the subtemplate's value in the config is set to {scheme}. If no subtemplate with the name of the scheme iis found, default is selected :)

Looks good to me! Thanks a lot for the contribution (and sorry for the wait)!


Post-Release-List

[ ] Update the readme to refer to master and tagged versions
[ ] Update saltyrtc.org

Last blocker as far as I can see: #118.

#118 is resolved for me now. Last thing: #126

What's missing @dbrgn. Can we finally release?

Hm, there was something I wanted to take a look at before we release. I'll take a look on Monday, maybe I can fix that then.

I think it's time. :smile_cat:

Postponed until we're sitting at the same table.

Yeah, I think it's actually good we waited, since the relayed data task brought some changes (like the 'disconnected' message).


Fix Natspec

Fix comment style for some Natspec.
Renamed minter to to for the totalPrice functions for clarity.

@Vectorized I like your suggestion of making a 1.1 branch - should this go into that?


No module named 'hyper_seg'

Because the training failed, I tried to download cityscapes_efficientnet_b1_hyperseg-m.pth to hyperseg/weights, and renamed it to model_best.pth,
I try
python test.py 'weights'
-td "hyper_seg.datasets.cityscapes.CityscapesDataset('data/cityscapes',split='val',mode='fine')"\ -it "seg_transforms.LargerEdgeResize([512,1024])"
--gpus 0

Looking forward to your reply！

You need to add the parent directory of the repository to PYTHONPATH.
That will be ~/Documents/code in your case.

Dear professor, thank you for your reply on this question.
In fact, I added the following sentence into the environment variable before training
export PYTHONPATH=$PYTHONPATH:/home/data/userleo/Documents/code
And  I just tried to add
export PYTHONPATH=$PYTHONPATH:~/Documents/code
export PYTHONPATH=$PYTHONPATH:/Documents/code
Then, I source ~/.bashrc
run the test order
But still the same error.
Looking forward to your reply!

Dear doctor Nirkin, I found the error after reading the code. The test command you gave in the README.md file does not require an underscore.

@leo-hao  I meet the same problem, how do you deal with it?

Hi, I have the same problem, how did you add the directory to the PythonPath, please?


Migrate from Laravel Mix to Vite

This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.
Before merging, you need to:

Checkout the shift-107147 branch
Run composer update
Run npm install
Review all comments for additional changes
Thoroughly test your application (no tests?, no CI?)

Please send your feedback to<EMAIL_ADDRESS>or share the good vibes on Twitter.

:x: Shift did not remove some of the previous npm scripts running mix commands as they appeared to be customized. You should review the scripts configured in your package.json file and update any custom commands to use vite.

:information_source: Previously, Laravel configured several npm scripts for building assets. For Vite, Laravel configures a dev script for generating and watching your assets (for development) and build script for generating your assets (for production).
Shift attempted to replace commands using these scripts with their new Vite script. However, you may still be referencing these scripts in your code or in deployment scripts.

:warning: Shift detected you are using Vue. As such, Vite recommends importing your CSS from your JavaScript entry point. This will improve your development experience by avoiding flashes of unstyled content during hot reloading.
Shift removed your CSS entry point from your Vite configuration. However, you will need to import this CSS in your JavaScript entry point.

:information_source: Vite requires JavaScript files containing JSX to have a .jsx file extension. Shift did not detect any JSX in files with a .js extension under the resources folder. However, if you are using JSX, be sure the files have a .jsx extension.

:information_source: Laravel renamed the environment variables used by Mix to use a VITE_ prefix, instead of MIX_. While Shift automated this change throughout your code, you should check for any additional references which may not be included in your Git repository.

:warning: Shift detected you are using Inertia. You may need to update your require statement for Vue components as well as configure an entry point if you are using SSR.

:information_source: The new @vite Blade directive outputs <script> tags with the type="module" attribute. This attribute implicitly defers the script. This is a difference from Laravel Mix which may change the execution order of the JavaScript on your page.
If you experience JavaScript errors relating to undefined references, you may need to reorder your scripts or add the defer attribute to any inline <script> blocks on your page.

:warning: Shift detected you may be using the tilde (~) prefix to import CSS or JavaScript. You may try to add an alias for the ~ to your Vite configuration. Alternatively, you may update these imports to use an absolute reference or @ alias.

:alembic: This Shift is still being refined. Please report any issues or suggestions to<EMAIL_ADDRESS>Your feedback is what helps improve the experience for everyone.


On Extracting redist stage of Installation (70%) its just stops and keeps hanging at this stage

PLEASE READ THE REQUIREMENT BEFORE FILLING A BUG. ALSO PLEASE CHECK IF A SIMILLAR ISSUE ISN'T OPEN
Photoshop version
CC2021
Describe the bug
On Extracting redist stage of Installation (70%) its just stops and keeps hanging at this stage
To Reproduce
Just run installation on manjaro
Expected behavior
I wanted to install Photoshop CC2021
Screenshots

System informations

Distro : Manjaro Linux 22.0
GPU : AMD Radeon RX 6600 (non-XT)
WINE version : 7.22

Additional context

You should know if you've readed the README.md that the GUI installer is deprecated and will not work anymore.
Please try using the CLI installer as explained in the README.md

Ok, thanks!


Allow require.js by bundling all js dependencies UMD style

This implements javascript dependencies (Bootstrap) via a Webpack bundle.
This should solve require.js issues.
@choldgraf , could you verify this solves the require js issue you tried to solve in #149. If it does, this PR maybe needs an extra cleaning commit regarding the requires changes.

Trying this out by checking the preview:

the plotly interactive figure seems to work fine now
the bootstrap js still seems broken. For example, if I use responsive mode for a smartphone, the "hamburger" menu does not open, and in the console I get a "TypeError: can't convert t to string" error

This was a bug related to jquery version 3.5.0. Downgrading to 3.4.1 fixes this.
The small burger menu when open now looks a little strange, is this behaviour new to this PR?
I will provide a new PR fixing this (to keep'm small ;) )

I see the same behaviour in the preview here, as on the latest deployed site (https://pydata-sphinx-theme.readthedocs.io/en/latest/), so I suppose it is not caused by this PR.
Can you merge in latest master into this branch, there are some conflicts now

Bug is fixed. Conflict is merged.

Thanks!
Let's give @choldgraf some time to check whether this works for him (as this would basically replace https://github.com/pandas-dev/pydata-sphinx-theme/pull/149 right?)

It seems like the requirejs is working just fine in the artifacts from this PR, so other than my two comments I think I'm +1 on this! (though maybe double-check the diff because it seems like there were some unintentional changes in this PR)

though maybe double-check the diff because it seems like there were some unintentional changes in this PR

There are only some changes from your commit left, which I think were awaiting removal/clean-up (also the docs need to be reworded or removed) until your confirmation this is working

I cleaned this PR. The require_js theme option is removed. The *Using with RequireJS

contribution section also felt unnecessary?

All extensions depending on require.js should work plug-and-play without specifying specific require.js related things?

Indeed, this doc section should indeed no longer be needed, as it should work out of the box now. So let's try that out ;)
Thanks a lot @hoetmaaiers for this solution!

fantastic - thanks @hoetmaaiers for the fix. I wonder - @jorisvandenbossche how do you feel about me cutting a patch release to see if the github action works, and then I can test out whether this indeed fixes the problems with requirejs in the sphinx_book_theme  as well?

@choldgraf that sounds perfect!


Add unread @-mention indicator to Recent topics

In #21637 / #22583, we added an @ in the left sidebar to indicate which streams/topics have unread @-mentions.
We should do the same in Recent topics. The @ should be to the left of the unread counter, with styling to match the @ in the left sidebar.
To match the left sidebar, we should not show @ for private messages even after #20890 is integrated. This will likely be a follow-up.

@madrix01 would you be up for picking this one up? It would make the @-mention indicator feature feel a lot more complete.

@alya i will work on this, currently I'm working to fix all the bugs in #20890