Support for keeping Joulescope turned on without having to have UI open

Hello,
I got a request which have annoyed me A LOT
I got a test setup where i need to do system test of a DUT.
And here i use Joulescope for measuring current. This turned out to be a big regret as it can enable/disable output.
And i cannot find any way of doing this using the Python library. What i want is to force it to be turned on until i turn it off again.
Currently my only solution is to keep the UI running but then i can't remote control the Joulescope which makes it useless..
Since the PyJoulescope_ui can do it. I would estimate there is API support for it somehow

Hi @Decee1 - I am not entirely sure I understand what you are trying to do.  If you just want to turn power on/off to the DUT, check out the dut_power example.  Does this do what you want?

Hi @mliberty1
That was exactly what i needed.
It was just not documented in the API. Not a big fan of the 'parameter_set' function. Seems like a lazy solution to just making proper API documentation for each of the function calls.
But hey it seems like it works!
Does this time out after some time or will the output stay 'on' until for example the USB port no longer is busy?

The JS110 will remain in the same state until you run another script that changes the state or the host computer no longer provides power to the JS110, such as when the host computer powers off or goes to sleep.

You can find a full list of JS110 parameters and their descriptions in parameters_v1.py.
Since you have a working solution, I am going to close this issue.  If you run into more issues, feel free to reopen this issue or create a new issue.


ko version of the matrix looks broken

Are you requesting a feature, reporting a bug or ask a question?
Bug
What is the current behavior?
there is text displayed where there should be no text
What is the expected behavior?
no text after the Radio button
How would you reproduce the current behavior (if this is a bug)?
just navigate to the example ko page for matrix
Provide the test code and the tested page URL (if applicable)
Tested page URL:
https://surveyjs.io/Examples/Library/?id=questiontype-matrix&platform=Knockoutjs
Specify your

browser: IE / FF
browser version: IE11
surveyjs platform (angular or react or jquery or knockout or vue): ko
surveyjs version: 12.33

fix confirmed on IE and FF, thx!


[Structured List]: Remove margin bottom in the shadow root for flexibility addition of

Description

The AEM team is in the midst of adopting the Structure List and noticed some discrepancies related to the rendering of some of the spacing.
Right now, we have a margin-bottom of 5rem or 80px  within the structure list shadow root which doesn't align with the spacing between the Structured List and the horizontal rule defined in the template (see attached).
The spacing should be set to 160px on max, xlg, lg | 96px on md | 64px on sm - cc: @jwitkowski79

Proposed Solution

Remove margin-bottom and allow for adopters to define the spacing.
the

Component(s) impacted
Structured List
Browser
Chrome, Safari, Firefox, Microsoft Edge
Carbon for IBM.com version
v.1.34.0 +
Severity
Severity 3 = The problem is visible or noticeable to users but does not impede the usability or functionality. Affects minor functionality, has a workaround.
Application/website
AEM
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
N/A
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

@kennylam @oliviaflory Let me know what you both think about my proposed solution (see above) for this issue. Once we have your approval. My team can open a PR to address this issue.


fixed missing string index check

Hello,
while checking this code
? ptr2str(ptr,0,4)[5]
I realized I got value outside of the string bounds, so here is the fix.
Greetings,
Ilir

Hello,
it seems git doesn't allow to pull another request on the same file, so here is the fix: while using
? ptr[1] # attempt to print pointer value
for e in ptr ? e next # attempt to iterate over the pointer list
I got VM crash because PUSHV on list item doesn't handle pointer.
Observe: I immediately decrease nRetItemRet value if > 0 because I noticed unhandled situations like
func retptr
...
return &ptr[1]
This is tested in Ring2B and it works. Still, I think it is not correct to return list item in case of the pointers, e..g whole if section can (should) be removed.
P.S.
I return empty string to disallow changing the pointer in situations like
ptr[1] = 0 // ptr address should be set via setPointer function, not like this

Hello Ilir
(1) At first this is  a complete test program that demonstrates the problem and can be used for testing
`
? "Define a number"
n1 = 12553523
? "Create a pointer to the number"
ptr = varptr("n1",:int)
? "Print the pointer value"
? ptr
? "Get a string using the pointer"
m = ptr2str(ptr,0,4)
? "String Size: " + len(m)
? "Print the ASCII code for each character"
for c in m ? ascii(c) next
? "Print character outsize range"
// ? ptr2str(ptr,0,4)[5]	# CRASH
? "Print each item in pointer list"
for e in ptr
//	? e 			# CRASH
next
? "Print the pointer value"
//	? ptr[1]		# CRASH
? "Call function that return a string"
? mystr()			# String (4 Characters)
? "Access character outside range"
? mystr()[5]			# Missing ERROR!
func mystr
return "1234"
`
(2)  We have two problems, The first is using an index outside the string range (You already solved)
The second problem is using PUSHV with a list item that contains the pointer
The right behavior in this situation should be (Pushing a String that contains the pointer address after converting it to a string)
So using
for e in ptr 	? e 			 next
Should produce a similar result to using
? ptr
(3) I will accept the pull request for now
After that I will change the code
Thank you very much

Hello Mahmoud,
Thank you very much
You're Welcome. The problem is: I don't want to have following situation
? "Define a number"
n1 = 12553523
? "Create a pointer to the number"
ptr = varptr("n1",:int)
setPointer(ptr, 3.14+ ptr[1]) // implicit conversion of a string to number
That's why I return empty string in Ring2B, but now after I revised this, I think I will return NIL to prevent any pointer manipulation outside of the get/setPointer functions in Ring2B+, and match Ring2B to official Ring.
Greetings,
Ilir

Hello Mahmoud,
I understand, maybe I'm overthinking or been overprotected ;) but my goal is to make Ring VM as a development environment taking care about such things before bringing it to compiled executable (without VM).  Somehow in my vision VM is safeguard against later runtime failures at the end of the development cycle.


reenable --checked option in flutter drive

https://github.com/flutter/flutter/commit/6635f1cf9baa6acc869d5c3799f28d780d1b7ad2#diff-09c5be1877aa83342be68006ff74cb82 didn't roll back everything.
/cc @devoncarew

lgtm

lgtm
fyi: I'm planning to remove --checked next week once the debug/profile/release build modes are working on Mac hosts (https://github.com/flutter/flutter/pull/3901)


How to call a leaflet Javascript Function in dropdown menu bar?

Hello,
i have the following problem:
my target is a hybrid app with leaflet. I create a dropdown menu with html/CSS/JQuery.
Here is the code:

<image src="../img/Icon/info.png"/>

Interpretation

Kennblatt

			<image src="http://maps.ioer.de/cgi-bin/wms?MAP=S02RG_1000&&SERVICE=WMS&VERSION=1.3.0&SLD_VERSION=1.1.0&REQUEST=GetLegendGraphic&FORMAT=image/jpeg&LAYER=S02RG_2012_a"/>

<image src="../img/Icon/ebenen.png"/>

<image src="../img/Icon/kalender.png"/>

<image src="../img/Icon/lupe.png"/>

<image src="../img/Icon/helligkeit.png"/>

Now I like to call the search function at the point li id="search".
I know how to call the function within the javascript part, but not within the list element, which is outside the Leaflet function.
My code for the Leaflet Map is:
new L.Control.GeoSearch({
	 	position: 'topcenter',
        provider: new L.GeoSearch.Provider.OpenStreetMap(),
    }).addTo(map);

which I like to implement in the dropdown menu.
Much thanks for Help !

The github issues is not the right place to ask for help using Leaflet, specially when the issue doesn't involve core leaflet but one of the plugins (in this case, OSM search). Please read https://github.com/Leaflet/Leaflet/blob/master/CONTRIBUTING.md#reporting-bugs


Some response security headers are not coming through when applied to traefik dashboard

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[ X] No

This issue was discussed with and demonstrated to Daniel Tomcej @dtomcej before posting here.
What did you do?
docker-compose.yaml:
version: "3.3"
services:
  traefik:
    image: "traefik:v2.0.0"
    container_name: "traefik"
    command:
      - --entryPoints.web.address=:80
      - --log.level=DEBUG
      - --accesslog
      - --api
      - --providers.docker.exposedByDefault=false
      - --providers.file.filename=/dyn.yaml
    ports:
      - "80:80"
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "./dyn.yaml:/dyn.yaml"
    labels:
      - traefik.enable=true
      - traefik.http.routers.traefik-dash2-unsecure.rule=PathPrefix("/")
      - traefik.http.routers.traefik-dash2-unsecure.entrypoints=web
      - traefik.http.routers.traefik-dash2-unsecure.middlewares=testfirefoxheaders@file
      - traefik.http.routers.traefik-dash2-unsecure.service=api@internal
  whoami:
    image: containous/whoami
    labels:
      #- "traefik.enable=true"
      - "traefik.http.routers.whoami_http.rule=PathPrefix(`/`)"
      - "traefik.http.routers.whoami_http.entrypoints=web"
      - traefik.http.routers.whoami_http.middlewares=testfirefoxheaders@file

dyn.yaml:
http:
  middlewares:
    testfirefoxheaders:
      headers:
        browserXssFilter: true
        contentTypeNosniff: true
        frameDeny: true

log excerpt
traefik    | time="2019-10-02T21:15:18Z" level=debug msg="Creating middleware" middlewareName=testfirefoxheaders@file middlewareType=Headers entryPointName=web routerName=traefik-dash2-unsecure@docker
traefik    | time="2019-10-02T21:15:18Z" level=debug msg="Setting up secureHeaders from %v{map[] map[] false [] []  [] 0 false [] [] false false  map[] false 0 false false false true  true true      false}" entryPointName=web routerName=traefik-dash2-unsecure@docker middlewareName=testfirefoxheaders@file middlewareType=Headers

Abridged output of curl -i -vvv http://<IP_ADDRESS>/dashboard/
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 80 (#0)
> GET /dashboard/ HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Content-Length: 3403
Content-Length: 3403
< Content-Type: text/html; charset=utf-8
Content-Type: text/html; charset=utf-8
< Last-Modified: Mon, 16 Sep 2019 17:18:10 GMT
Last-Modified: Mon, 16 Sep 2019 17:18:10 GMT
< Date: Wed, 02 Oct 2019 21:16:14 GMT
Date: Wed, 02 Oct 2019 21:16:14 GMT

<
<!DOCTYPE html>

What did you expect to see?
I expected to see the response headers coming through:
< X-Content-Type-Options: nosniff
< X-Frame-Options: DENY
< X-Xss-Protection: 1; mode=block

What did you see instead?
See above, them NOT coming through.
Note that this is only issue with the dashboard. The headers do come through for other services as can be demonstrated by commenting out the first traefik.enable=true and uncommenting the second.
Some more discussion here: https://community.containo.us/t/middlewares-questions-and-suggestions/1957/6
Output of traefik version: (What version of Traefik are you using?)

Traefik version 2.0.0 built on 2019-09-16T17:35:17Z

What is your environment & configuration (arguments, toml, provider, platform, ...)?
See above.

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
See above

Same is reproducible on 2.0.1

Same for 2.0.5

I can confirm this on 2.0.5, also the tls.options are ignored. Basic auth works fine though, so maybe this is only affecting SSL/TLS related options?

Same issues for 2.1.

Having this same issue on v2.2.0-rc2

Just noticed this issue with 2.2.1 using the following config:
http:
  middlewares:
    hsts-headers:
      headers:
        stsSeconds: 63072000
        stsIncludeSubdomains: true
        stsPreload: true
    security-headers:
      headers:
        frameDeny: true
        contentTypeNosniff: true
        browserXssFilter: true

My docker-compose.yml contains the following label:
"traefik.http.routers.traefik.middlewares=authenticate,compress,hsts-headers@file,security-headers@file"
The authenticate and compress middlewares are also defined per label.
According to the dashboard, all 4 middlewares are active for the router.

Just noticed this issue with 2.2.1 using the following config:
http:
  middlewares:
    hsts-headers:
      headers:
        stsSeconds: 63072000
        stsIncludeSubdomains: true
        stsPreload: true
    security-headers:
      headers:
        frameDeny: true
        contentTypeNosniff: true
        browserXssFilter: true

My docker-compose.yml contains the following label:
"traefik.http.routers.traefik.middlewares=authenticate,compress,hsts-headers@file,security-headers@file"
The authenticate and compress middlewares are also defined per label.
According to the dashboard, all 4 middlewares are active for the router, but neither the HSTS headers are sent, nor the security headers.
Edit: In the meanwhile, I realized that security headers in multiple middlewares cannot be merged, but even with all headers set inside a single middleware, they are not applied to the dashboard router.

I can confirm this issue. Setting the force STS ends in SSL Labs Test Grade B, without force STS it´s an A.

Closed by #6750.


make Gravatar support optional

Is your feature request related to a problem? Please describe.
When NeuVector is used in strict environments without Internet connectivity, accessing external resources may significantly slowdown the application rendering or produce artifacts.
In this particular case it also leads to leaking username to Gravatar. This is most likely not wanted behavior as in corporate use cases such usernames are usually purely technical.
Describe the solution you'd like
Ideally, it would be great to have an opportunity to globally disable Gravatar support via initcfg.yaml on deployment.
Describe alternatives you've considered
As an alternative I may suggest just disabling Gravatar completely as this feature is probably not widely used in corporate environments anyway.
Additional context
The function that is used to format Gravatar URL in current 5.0.4+ release: getAvatar().
It is used in the following places:

4:profile-form.component.html
57:profile-form.component.ts
58:profile-form.component.ts
79:users-grid.component.ts

Thanks for the report. We will follow up on this request.

As of v5.1.2, Gravatar can be enabled by setting manager env variable GRAVATAR_ENABLED (default false).


Clarified and expanded the Slack info

Updated Slack info on the community page: Added  a few channels, fixed the Slack terminology (workspace vs channel), and separated the Slack info into a new section, so that we can link to it more easily. In particular, the new v1.0 support page needs to link to the Slack info.
Fixes https://github.com/kubeflow/website/issues/1521

This change is

Preview: https://deploy-preview-1522--competent-brattain-de2d6d.netlify.com//docs/about/community/#slack-online-chat-and-messaging

/cc @theadactyl
/assign @abhi-g

/lgtm
/approve
/hold to ensure @theadactyl is happy


BHAC MKS Coordinates

BHAC uses a slightly different flavor of MKS coordinates, with
x2 -> pi*x2
hslope -> (1-hslope)
And while this trivial a conversion could be done in-place pretty easily with our python tooling, ipole's support for coordinates needed some love, so I figured I'd do it the right way^(TM).
So, between improving printed output, coordinate system selection, and tests, and rooting out a bunch of places ipole implicitly assumes x2 is in [0,1], ipole got better, and I lost a day.

@bprather is this ready for merge?

I think so, pending your approval.  It passes the old tests and some new ones and I've been using it without issue.  Just been reluctant to rebase the adaptive-res and polyphony work.

Pulling the trigger.  It'll make updating other WIPs easier.


Add possibility to set command parameter as String.

This fix establishes the desired behavior for the "command" parameter as
described in the icinga2 docs and in the icinga2 module parameter
description:
"The command. This can either be an array of individual command arguments.
Alternatively a string can be specified in which case the shell interpreter
(usually /bin/sh) takes care of parsing the command."
Update the rspec tests.

fixed in current master, thx.


Question about Component::Proc function

How can i trigger the Proc function, such as Localization component ?

Hi, @wanggujin you can read this example, the CommonComponentSample component subscribes message from channel /apollo/prediction，which is in common.dag. When the message arrives，it will trigger the proc func.
https://github.com/ApolloAuto/apollo/tree/master/cyber/examples/common_component_example

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions. Thanks!


SC loadBalancer : Cache manager fails to update in case downstream service goes down

ConcurrentHashMap used for caching ServiceInstance does not get update it self as services goes and come.
No provision for TTL.
Tried using redis as cache, no luck as DefaultServiceInstance is not serializable.
Caused by: java.io.NotSerializableException: org.springframework.cloud.client.DefaultServiceInstance

duplicates #638


navbar: Tweak Combined feed description for spectators.

Since spectators cannot mute channels or topics, the combined feed description for spectators is tweaked to exclude that part.
Fixes #30321

Screenshots

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@pratik-pc Please have a look. Its a small one.

This looks good to me

@timabbott Do you want to review this small change directly?

Merged, thanks @kuv2707!


Feedback of Milestone 1

The output of the first two functions are some type, and the unit test of them may be very similar. Porbably consider something different so you can have different test.
The first two function feels like just one line of code (call score function), maybe add some extension

Thank you for the feedback. The issue was addressed in the issue here.


PLAT-142964: Sampler: Fix global knob setting resets when component changes

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] Documentation was verified or is not changed
[x] UI test was passed or is not needed
[x] Screenshot test was verified or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
The global knob setting stays even if the story changes.
Resolution
Referred PR: https://github.com/enactjs/sandstone/pull/906
Additional Considerations
Links
PLAT-142964
Comments

If you click the knobs, the color selector would be displayed.

The 'color' function of the storybook's knob has a bug.
It doesn't return a new value when the preferred value is changed.
globals.accent = color('accent', preferredValue, groupId);
So I also added a workaround to handle it.

Since the 'color' function's bug, I reverted it.


Fix invalid references to MessageInputStream.messageHeader.

Fix invalid reference to MessageInputStream.messageHeader—should be getMessageHeader()—in releaseRenewalLock() and ReceiveService.call().

releaseRenewalLock() is called after the single renewing message finishes, in order to let some other message acquire the renewal lock if it needs it. When it does so, it delivers any newly acquired master token to the waiting message.
The bug is that it never delivered the newly acquired master token to the waiting message. As a result, the waiting message would then acquire the renewal lock and send out a renewable message with the previous master token.
By itself this should be OK, because as far as the server is concerned it's like the new master token got lost, and the client is back to using the previous one. But what's likely to happen is the second message renews the previous master token a second time, to get a third master token that is now the newest one. And if some other message was blocking on acquiring the renewal lock you could see a series of renewable messages with leap-frogging master tokens.
I wonder if this might be causing the master token sequence number out of sync issues we have seen on rare occasions. Although that seems unlikely given master tokens are not immediately renewable.


Make Start Reading button functional..

Description
This Start Reading Now button is not working right now , It should redirect us to the books section so that the user can read the books.......
Screenshots

Any additional information?
I would make this button proper functional..
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hi @rohansx @k-deepak04 I would like to work on this issue , please assign it to me........

@rahulrana701 we are yet to decide where we should redirect the user
meanwhile if you can read the discussion tab and help us in backend functionality it will be much appreciated.


Custom graphql.execution.DataFetcherExceptionHandler

Hello Dear Friend,
I would like to make custom graphql.execution.DataFetcherExceptionHandler for my application like at https://www.graphql-java.com/documentation/v10/execution/:
DataFetcherExceptionHandler handler = new DataFetcherExceptionHandler() {
    @Override
    public void accept(DataFetcherExceptionHandlerParameters handlerParameters) {
                  // do your custom handling here.  The parameters have all you need
    }
};

ExecutionStrategy executionStrategy = new AsyncExecutionStrategy(handler);

Is it possible with graphql-spring-boot?

@paullarionov can you give the code snippet how you did it?

@ankit-joinwal sorry, no snippet available


[BugFix] fix schema change hang when data loading concurrent with schema change

What type of PR is this:

[X] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes:

Fixes #23452
Problem Summary(Required):

Assume there is a partition, current visible version is 13378, and all loading task is finished.
Trigger schema change, it will create new replica, and at the same time, one loading task is trigger and finished, and it's version is 13379.
Before send alter replica request, FE check that all loading task is finished, but loading task on new create replica haven't finish yet and V=1, LFV=13379.
Alter replica finish on BE, and BE send finish alter replica request back to FE. When call handleFinishAlterTask, checkState fail because LFV != -1.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


Update workflow-features-concepts.md

Correct link for know limitations in workflow page
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Issue reference

@Shubhdeep02 Can you please mention the issue in the description?
Issue: https://github.com/dapr/docs/issues/4224

@holopin-bot @Shubhdeep02 Thank you!


Lambda Lifter

This PR redefines the lifter API and separates lifters into two kinds: those that use contextual information to generate lifted callables, and those that use the content to generate the lifted content. The lambda lifter is defined as a content-based lifter, while the classical control lifter is reworked in the new system to be a context-based lifter.
With the lambda lifter, lambdas will be removed from the AST through the Lift Lambdas rewrite step.
#1294

I've finished reviewing the non-test code and left some minor feedback. I'll continue reviewing the test code and following along with the ongoing discussion there.


another error on compiling

Describe your bug here.
source/states/PlayState.hx:107: characters 32-39 : Type not found : HScript
Command Prompt/Terminal logs (if existing)
source/states/PlayState.hx:107: characters 32-39 : Type not found : HScript

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

you didn’t install Hscript

oh...
On Sat, Sep 2, 2023 at 4:33 PM ✞Hoovy✞ @.***> wrote:

you didn’t install Hscript
—
Reply to this email directly, view it on GitHub
https://github.com/ShadowMario/FNF-PsychEngine/issues/13231#issuecomment-1703920038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7GXSH23US4EUOSUUJNMFT3XYOCX7ANCNFSM6AAAAAA4IXPDDI
.
You are receiving this because you authored the thread.Message ID:
@.***>

2.5.0(this is the version


The overview page does not work - It shows an error message

Version of HACS
Last one

Describe the bug
When I click on the Overview button the page is not being shown. It says Something is wrong...
Error code: Kneel before Zod!
Debug log

Add your logs here.

Enable debug logging, then restart and paste the logs after you try it again.

[Errno 2] No such file or directory: '/config/custom_components/hacs/frontend/elements/repository/row_overview.html' 7:05 PM custom_components/hacs/frontend/views/overview.py (ERROR) - message first occured at 7:01 PM and shows up 16 times

Restart Home Assistant, as stated in the release notes.


Expose the TypeScript object inside the ts worker

I've migrated our infra over to handle the new monorepo, but hit a blocker. In the older versions of monaco-typescript, importing vs/language/typescript/tsWorker would trigger window.ts to become the TypeScript object.
This is generally considered a  feature (of a side effect) when importing typescriptServices.js because of this var:

I used that to access the same version of TypeScript as the monaco webworker in the Playground.
I'm not tied to the implementation detail as it's easy to do both, so I felt this might be more ESM-y instead of jamming a window.ts = ts at the end but I think it depends on whether this is classed as a breaking change (and I guess if other people used that side-effect) in which case this can be switched out

I don't think this is enough to fix it

:+1: I've also added an assertion for it in the smoke test.


Fixed round error on mingw

I did some investigating on this:
Firstly just to be sure, under IEEE-754 double-precision 0.49999999999999994 IS representable - the following link shows the breakdown:
http://www.binaryconvert.com/result_double.html?decimal=048046052057057057057057057057057057057057057057057057052
Looking at mingw-w64 round.c it looks like no provision is taken for a result `larger’ than a double which looks like it will result in a double-rounding error:
https://github.com/Alexpux/mingw-w64/blob/b028d1b994ab601843a518a2e4ad0d74a05e9569/mingw-w64-crt/math/round.c
Here is the gcc version of round() in real.c - care is taken to ensure information is not lost during the truncation stage as commented here:
https://github.com/gcc-mirror/gcc/blob/master/gcc/real.c#L31
According to the following article GCC also used to incorrectly calculate round - but this was fixed in 2013 :
http://www.exploringbinary.com/real-c-rounding-is-perfect-gcc-now-converts-correctly/
Presumably if Mingw want to make claims of providing the Gnu Compiler Collection on Windows then they must ensure their algorithms are updated to match?
On 28 Dec 2016, at 03:02, Nobuyoshi Nakada<EMAIL_ADDRESS>wrote:

@nobu commented on this pull request.
In core/float/round_spec.rb:

@@ -10,11 +10,9 @@
0.0.round.should == 0
end

platform_is_not "x64-mingw32" do
it "returns the nearest Integer for Float near the limit" do

 0.49999999999999994.round.should == 0

 -0.49999999999999994.round.should == 0

end

it "returns the nearest Integer for Float near the limit" do
Thank you, posted https://sourceforge.net/p/mingw/bugs/2325/ now.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@nobu Is this fixed (or worked around) in ruby 2.4 or trunk?
If so, we can add a version guard here and merge it.

@nobu Ping :)
Was this fixed in MRI itself?
If so please commit the spec changes directly in ruby/ruby (should be easier).


Question about dependencies.

Type of Issue
[ ] Bug Report
[ ] Feature Request
[*] Question

Description
I'm developing some library which has a dependency on third-party.
Schema looks like this:
Library A depends on the library B.
Application X uses library A, but doesn't need library B.
Is it possible to install just library A, without installing library B?
When I try to add B to the dependencies in package.json ng-packagr says that Dependency B must be explicitly whitelisted.
If I add it to peerDependencies build is fine, but application X now have to install B as it's own dependency to work.
Can you help me with this issue? What am I doing wrong?

I found the answer here https://github.com/dherges/ng-packagr/issues/716


Wordpress.com rendering issues

some pages in the wordpress.com blogging system aren't displayed right at all, a sample screenshot: http://puu.sh/oHQM1/3188fac979.png
wordpress is a staple for many users and should be fully compatible with Min.

Privacy Preferens -> Uncheck "Block trackers and ads" -> Profit

The issue was that element types were being ignored when deciding whether or not to block a resource. This meant that a rule that should only match iframes from wp.com was matching all requests to wp.com.
Fixed in b00bff46e381d5e3d3573e5937a6ab6406d8c5da.


Re-Setup for me

ESlint
Prettier
add packages for development blog

sorry, I create this PR by mistake.


feat(install): Allow tag to be passed in via install command

This allows --tag flag to be used with the install command.

This will support backward compatibility with NRIA_CUSTOM_ATTRIBUTES. It will merge and generate YAML if both configs are defined.
Following are tested and working commands
With both defined:
NRIA_CUSTOM_ATTRIBUTES='{"install_from":"virtuoso"}' ./newrelic install --tag tag3:2345,tag4:abb,made:hzhao -y
With just tags:
./newrelic install --tag justTags:yes

Help Info in CLI:

The expected result is custom attribute section is added to infra config:
cat /etc/newrelic-infra.yml

And you can see the tags in NR1 as well:


API Implementation of /v2/attrs

Fix for Issue#118  for Api implementation of /v2/attrs
Updated specification/quantumleap.yml for API method call.
Added query_NTNENA.py , query_NTNE1A.py for handling APIs.
Added test_NTNENA.py , test_NTNE1A.py for test cases related to API.

@daminichopra great contribution, thank you so much!
I think we need more testing though to make sure we cover all the bases. Specifically, it'd be fantastic if you could implement these test scenarios:

Retrieve the same attribute a across two different entity types T1, T2 for a specified time interval.
Given a time interval, retrieve two attributes a, b across two different entity types T1, T2 where T1.a has the same type of T2.a and, likewise, type (T1.b) = type (T2.b).
Average of a numeric attribute of T1 and T2 in a given time interval.
Average of a numeric attribute of T1 and non-numeric attribute of another entity T3.

The database should initially contain entities for three different types T1, T2, T3 and each type should have a string attribute a, T1 and T2 an integer attribute b whereas T3 too should have an attribute called b but it should have a string type. Also T1, T2, T3 should each have an attribute which is not in common with the other two types---e.g. T1.x, T2.y, T3.z. This way you should be able to use the same DB fixture for all four scenarios. In particular, you can use T1.b and T2.b for (3) whereas T1.b and T3.b should do for (4).
As usual these are just suggestions. Feel free to suggest variations on the theme or more scenarios or whatever you think would be appropriate. Oh also, sorry for the choice of entity/attr names, use whatever naming scheme/convention makes sense to you :-)

Hi  @c0c0n3 , I have Incorporated comments above in update PR.
Regarding points  3) and 4), we can consider them for future enhancement with new separate issue. As, we need to change code for this implementation and also it is not implemented for existing API yet. Also, we have an existing issue Issue#241 - Related to point above.
Please close this PR if it looks good . Thank you :)

Hi @daminichopra thanks for implementing test scenarios (1) and (2). That's great 👍
I agree with you about scenario (4), let's leave it behind for now. I opened a separate issue for it, #296. We still need to test (3) though: to me that's part of this PR, i.e. it should work without changing your code, if it doesn't...well perhaps we should fix it?

from a logic point of view, as regards 4, simply there is no average. so you don't consider them.

Hi @c0c0n3 , I have Updated PR .Please check
Thank you !!!

@c0c0n3 @chicco785 , If PR is ok then Please close this PR.

Gentle Reminder!!

Been busy busy w/ other stuff. Sorry. Will make some time for proper review tomorrow am, but casting a cursory glance... it looks ready to go :-)

@daminichopra thanks for updating the PR with more tests, that's great.
When I looked at it yesterday I just assumed the failed tests where those for geocoding---we have an issue for that already, see #292. So you can ignore failures coming from test_geocoding.py.
But there are other tests that failed too, namely those in

src/tests/test_bc.py

Have a look at the build log for the details. Did you get the green bar on your machine or did the tests fail on your box too? For good measure, always run
$ source setup_dev_env.sh
$ sh run_tests.sh

before committing. I know it takes one hell of a long time and we should actually improve that, but at the moment it's the only safety net we've got :-)
Can you please try reproducing on your box to see what's going on. Thanks!!

I have confirmed the same errors i.e. failing of src/tests/test_bc.py  in master branch in which this
PR is not included. Please check the below screen shot for your reference.

have confirmed the same errors i.e. failing of src/tests/test_bc.py in master

Um, that's weird. PR #299 got a green bar but didn't touch that test or anything related. Perhaps we could try rebasing this PR onto master once I merge PR #299...

HI @c0c0n3 , Please merge this PR if it looks good. Thank you

Hi @daminichopra, thank you so much for implementing geo params in Python :-)
Also, it looks like all tests are passing now, that's grand!
But there's still a couple of things that needs doing though before I can merge:

Add geo params to the QL spec---see my comment in the review.
Rebase this branch onto master.

Thanks!!

Hi @c0c0n3 , updated fix and rebase done. Please close this merge PR. Thank you

@daminichopra thank you for the great contribution, we really appreciate your hard work and dedication!


use distinct MSI log files

What does this PR do?

Add distinct log filenames to Fleet Installer MSI executions in E2E tests
Motivation

https://datadoghq.atlassian.net/browse/WINA-982
Successive Install/Uninstall would overwrite previous log files
Additional Notes

Possible Drawbacks / Trade-offs

Install and Uninstall will throw an error if the log file already exists. We could generate a new unique filename instead, but this way encourages the dev to choose a descriptive name.
Describe how to test/QA your changes

N/A, test change

/merge


feat(content): iOS only scroll bounce

Short description of what this resolves:
https://github.com/driftyco/ionic/issues/5275
Changes proposed in this pull request:

New no-bounce attribute to disable over-scroll bouncing

Ionic Version: 2.x
Fixes: #5275

I have spent literally 3 hours trying to figure out how to prevent the bouncing tonight, it might help others if the "no-bounce" attribute was added to the docs :)

Is this still available in 3.0.1? Tried adding it to the conference app to no avail

Same? Is this going to be fixed?

@manucorporat does this work in<EMAIL_ADDRESS>@markholland @maitham1 did u find any fix for latest ionic version?


Composer

`composer require mangopay/php-sdk-v2:^2.8
Your version of PHP, 5.4.16, is affected by CVE-2013-6420 and cannot safely perform certificate validation, we strongly suggest you upgrade.
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package mangopay/php-sdk-v2 No version set (parsed as 1.0.0) is satisfiable by mangopay/php-sdk-v2[No version set (parsed as 1.0.0)] but these conflict with your requirements or minimum-stability.
Installation failed, reverting ./composer.json to its original content.
`
Cannot run the composer command

Hello @silvermcd123!
Are you still having problems on this point? If so, please let us know what else you have tried so we can help you solve it. Otherwise just let us know.
Thanks!


[Feature] Ability to specify the Data Source using javascript

Summary
It would have been great if there was an option to select the data source associated with the query via javascript.
Motivation
We have production and development APIs which needs to be authenticated using OAuth2. The only difference between Development and Production APIs is the domain name. One is https://api.example.com/resource and other one is https://api-dev.example.com/resource
If I wanted to make requests to these API resources, I have to create multiple queries for each resource. That could be avoided if it could be managed via javascript.
Additional Context

I wanted to add users to different environments according to the selection. Each user addition API calls should be made to respective environment domains

Hi @Nikhil-Nandagopal 👋 thanks for the feature request. We'll support different environments in our Git Sync Feature. #3199
This way you can control which branch points to which set of datasources


Pl3xMap is spamming requests, like a INSANE amount. (Skin Spam/Request Spam)

Just had a chance to look into this. Since you have inspect element open I'm assuming you have Disable cache selected. If you deselect it then the browser should respect the image caching and stop spamming requests.

Just had a chance to look into this. Since you have inspect element open I'm assuming you have Disable cache selected. If you deselect it then the browser should respect the image caching and stop spamming requests.

This happens for EVERY player on the server when they open the map, not when using inspect element.

bump


[JWE] Added support for A256GCM and A128GCM

After considering the comments in #251, I've added support for content encryption using AES GCM according to JWE standard. As I've mentioned there, I increased the minimum iOS target to 13.0 because of CryptoKit.

Thanks for this PR, any thoughts on completing it and releasing new lib version?

From my perspective, it's completed. I'm just waiting for a review.

I hope someone will take a look, seems like most of the PR's are not reviewed at all :(

After considering the comments in #251, I've added support for content encryption using AES GCM according to JWE standard. As I've mentioned there, I increased the minimum iOS target to 13.0 because of CryptoKit.

Any update on this. Please include AES128GCM content encryption algorithm. It is very important and urgent. I dont understand why this is not included in the library?

Hi, any update on this? It will be very useful to have this PR merged.

Looks like it fails lint tests - @tobihagemann

Is there anything we can do to help get this PR merged in?


v1.10.0: Possible false-positive for E3054: 'RequiresCompatibilities' is a required property

CloudFormation Lint Version
1.10.0
What operating system are you using?
Windows 11
Describe the bug
After updating to 1.10.0 i get the following error for AWS::ECS::TaskDefinition:
[cfn-lint] E3054: 'RequiresCompatibilities' is a required property
Registers a new task definition from the supplied ``family`` and ``containerDefinitions``.
Optionally, you can add data volumes to your containers with the ``volumes`` parameter.
For more information about task definition parameters and defaults, see [Amazon ECS Task Definitions]([https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html\](vscode-file://vscode-app/d:/Programme/VSCode/resources/app/out/vs/code/electron-sandbox/workbench/workbench.html)) in the *Amazon Elastic Container Service Developer Guide*.

You can specify a role for your task with the ``taskRoleArn`` parameter.
When you specify a role for a task, its containers can then use the latest versions of the CLI or SDKs to make API requests to the AWS services that are specified in the policy that's associated with the role.
For more information, see [IAM Roles for Tasks]([https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html\](vscode-file://vscode-app/d:/Programme/VSCode/resources/app/out/vs/code/electron-sandbox/workbench/workbench.html)) in the *Amazon Elastic Container Service Developer Guide*.....

Expected behavior
cfn-lint doesn't give that error, since i can deploy the stack.
Reproduction template
  TaskDefinition:
    Type: AWS::ECS::TaskDefinition
    Properties:
      NetworkMode: awsvpc
      TaskRoleArn: !GetAtt TaskRole.Arn
      ExecutionRoleArn: !GetAtt ExecutionRole.Arn
      Cpu: 512
      Memory: 1024
      RuntimePlatform:
        CpuArchitecture: ARM64
      ContainerDefinitions:
        - Name: ContainerName
          Image: <IMAGE>
          LogConfiguration:
            LogDriver: awslogs
            Options:
              awslogs-region: !Ref AWS::Region
              awslogs-group: !Ref LogGroup
              awslogs-stream-prefix: !Ref AWS::StackName

This rule crosses into the AWS::ECS::Service definition as well.  Can you provide that resource as well? We should be triggering this only when the service has a LaunchType of Fargate.
ECSService:
    Type: AWS::ECS::Service
    Properties:
      LaunchType: FARGATE

as part of this comment and replicated through some testing.

Here you go:
  ECSCluster:
    Type: AWS::ECS::Cluster
    Properties:
      ClusterSettings:
        - Name: containerInsights
          Value: enabled
      CapacityProviders:
        - FARGATE

  ECSService:
    Type: AWS::ECS::Service
    Properties:
      Cluster: !Ref ECSCluster
      TaskDefinition: !GetAtt ECSTaskDefinition.TaskDefinitionArn
      DesiredCount: 1
      LaunchType: FARGATE
      PropagateTags: SERVICE
      NetworkConfiguration:
        AwsvpcConfiguration:
          SecurityGroups:
            - !GetAtt SecurityGroup.GroupId
          Subnets:
            - <Subnet>
      EnableExecuteCommand: true

  ECSTaskDefinition:
    Type: AWS::ECS::TaskDefinition
    Properties:
      NetworkMode: awsvpc
      TaskRoleArn: !GetAtt TaskRole.Arn
      ExecutionRoleArn: !GetAtt ExecutionRole.Arn
      Cpu: 512
      Memory: 1024
      RuntimePlatform:
        CpuArchitecture: ARM64
      ContainerDefinitions:
        - Name: ContainerName
          Image: <IMAGE>
          LogConfiguration:
            LogDriver: awslogs
            Options:
              awslogs-region: !Ref AWS::Region
              awslogs-group: !Ref LogGroup
              awslogs-stream-prefix: !Ref AWS::StackName

According to https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html#cfn-ecs-taskdefinition-requirescompatibilities, you do not need RequiresCompatibilities:
RequiresCompatibilities
The task launch types the task definition was validated against.
The valid values are EC2, FARGATE, and EXTERNAL.
For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.

Required: No

Type: Array of String

Update requires: Replacement

Looks like NetworkMode: awsvpc will drop the need of RequiresCompatibilities: [FARGATE]
This will succeed without RequiresCompatibilities specified.  Dropping NetworkMode property will again require the RequiresCompatibilities
ECSTaskDefinition:
    Type: 'AWS::ECS::TaskDefinition'
    Properties:
      NetworkMode: awsvpc

When removing NetworkMode you will get the error  Invalid request provided: CreateService error: Task definition does not support launch_type FARGATE.

This caveat only seems to apply to NetworkMode: awsvpc other network modes still require FARGATE to specified.

This PR will remove this error when NetworkMode is awsvpc or an object (Function to some possibly dynamic value)

Thank you!


Unknown type for the following structure (type: string, class: io.swagger.v3.oas.models.media.PasswordSchema)

Update This issue is tracking errors generated by following schemas:
swagger: "2.0"
info:
  title: Whatever
  version: 1.0.0
host: localhost:1234
schemes:
  - http
definitions:
  Foo:
    type: object
    properties:
      somePassword:
        type: string
        format: password
      someFile:
        type: file
      someBinary:
        type: string
        format: binary

They all generate errors similar to this one:
Error: Unknown type for the following structure (type: string, class: io.swagger.v3.oas.models.media.PasswordSchema):
  class PasswordSchema {
      class Schema {
      }
      type: string
      format: password
  }

Original issue:
Hi,
when using follwing definition:
{"password":{"format":"password","type":"string"}}

I get the following error:
Error: Unknown type for the following structure (type: string, class: io.swagger.v3.oas.models.media.PasswordSchema):
  class PasswordSchema {
      class Schema {
      }
      type: string
      format: password
  }

Any idea what to do about it? I suspect it's a format that has been removed in swagger v3 or something like that

Ok i think i figured it out for password (see #256 ) ... but i have same problem with type: file, which is trickier ... i'm not sure how to handle that one

this is an example of the offending yml...
get:
  summary: get timezone data
  operationId: getTimezoneData
  description: |-
    Get timezone data (also called tzdata)
  responses:
    200:
      description: Succesfully retrieved tzdata.
      schema:
        description: User specific tzdata file.
        type: file

i assume raw response could be used for this but this fails the compilation ... i wonder how to solve this ... perhaps generate response that takes fs2 stream and pipe it to raw response in the generated code?

What's the compiler error?  We've supported type: file for some time now; not sure why it wouldn't work.

@tomasherman akka-http has support for type: file, not sure that http4s has support for that yet. The naive implementation in akka-http uses a helper method to build a java.io.File object, which the file is streamed into.
This isn't a great solution though, I'd much rather go with something InputStream based to stream into a file or to anything else that can behave like an InputStream.

Like i said, the error comes up during generaetion phase:
Error: Unknown type for the following structure (type: string, class: io.swagger.v3.oas.models.media.PasswordSchema):
  class PasswordSchema {
      class Schema {
      }
      type: string
      format: password
  }

This is likely related to
SwaggerGenerator.scala#L103-L111:
      case GetType(model) =>
        val determinedType = Option(model.getType()).fold("No type definition")(s => s"type: $s")
        val className      = model.getClass.getName
        Target.fromOption(
          Option(model.getType()),
          s"""|Unknown type for the following structure (${determinedType}, class: ${className}):
              |  ${model.toString().lines.filterNot(_.contains(": null")).mkString("\n  ")}
              |""".stripMargin
        )

where .getType() returns null, as it should be .getSchema().getType(). I wonder why they embed a Schema[_] into a FileSchema... this seems unnecessary.
Could you try using an OpenAPI 3.x spec to reproduce?
Alternately, I'm realizing that we don't have any tests for type: file in the response structure, which would indicate why this hasn't come up before.

i can provide some failing test case, but is there any chance any of you guys could take a stab at this? I am already battling in two other merge requests and i don't have any more time to invest :(

I can't promise I can get to it this week, unfortunately. Thank you for your efforts iterating on your other PRs, by the way :smile:

well, we either have to make it work for our use cases, or use python at work ... so not really much choice :D but thanks for the guidance ... i might get to it after all, i think i made good progress on the other PRs

Another failure example, if it helps, otherwise this just a self-serving +1 to having the same issue.
      responses:
        '200':
          description: OK
          content:
            image/png:
              schema:
                type: string
                format: binary
            image/jpeg:
              schema:
                type: string
                format: binary
            application/pdf:
              schema:
                type: string
                format: binary

Produces the error:
[ERROR] Error: Unknown type for the following structure (type: string, class: io.swagger.v3.oas.models.media.BinarySchema):
  class BinarySchema {
      class Schema {
      }
      type: string
      format: binary
  }

[ERROR] Failed to generate client
com.twilio.maven.swagger.CodegenFailedException
    at com.twilio.maven.swagger.AbstractSwaggerCodegenMojo.$anonfun$guardrailTwilioTask$4 (AbstractSwaggerCodegenMojo.scala:131)

I wonder how type string format binary should be represented...it seems the easiest solution would be Array[Byte] but i feel Stream[Byte] would be better as these files will probably always be files or something that might be quite large

@Gipetto i believe i patched this issue with #283 but i think further improvements on how binary properties should be handled are in order

There's a similar issue with the format type email. I don't think this one requires special handling (see https://swagger.io/specification/#data-types) but it is also not disallowed.

I am running into a similar issue with type: array
"FooBatch": {
"properties": {
"foos": {
"items": {
"$ref": "#/components/schemas/Foo"
},
"type": "array"
}
}
}
[31mError:Unknown type for the following structure (No type definition, class: io.swagger.v3.oas.models.media.Schema):
class Schema {
properties: {foos=class ArraySchema {
class Schema {
}
type: array
items: class Schema {
$ref: #/components/schemas/Foo
}
}}
}

@nick-bauer: What's the context around FooBatch? Where in the document is it coming from?

Following up, as this bit one of my coworkers -- It turns out that the assumption of type: array with an items that doesn't have a definite type can cause this error.

#1407 improves the situation referred to by @nick-bauer -- I unified the different type transformation logic, which was causing issues with $refs inside of array.
Closing this, thank you 🙂


Make error class initializer signatures more consistent

The goal is to prevent the developer from having to look up docs all the time to figure out how this or that error class is initialized; they should be initialized in a consistent way as much as possible.
Inconsistencies to address include:

Not all classes may be initialized with a title and description. For classes where those are optional, we can add **kwargs, or introduce specializations such as HTTPRangeNotSatisfiable vs. HTTPRangeNotSatisfiableBlank, where the former would take (self, title, description, resource_length, **kwargs).
The above inconsistency alludes to the fact that some errors require title and description, while others do not. Perhaps some of the design could be cleaned up by making everything optional? It is good to set a title and description from a usability perspective, but does the framework need to enforce that?
Some errors use a hard-coded title, while others do not. How to address localization for hard-coded strings, and should more of the errors have static titles, or none of them?

In any case, this must all be done in a backwards-compatible way. This might be accomplished (TBD) by creating generic _init_ methods and then discerning whether the old params are being used, or the new. Only the new ones will be documented so that over time apps will no longer use the deprecated signatures.
def __init__(self, *args, **kwargs):
    # Check what args and kwargs were passed; hopefully this
    # will make it possible to support old and new signatures (TBD)

Alternatively, we could introduce a new errors module and deprecate the current one. A different naming convention could be used for the new-style error classes to distinguish them from the old.
Other ideas?

I was about to open issue asking why some errors require a title and description. Falcon claims to be "un-opinionated" but I think having error classes that explicitly defines a JSON response with two fields "title" and "description" is pretty opinionated.
I know there's even already a mixin I can use to make my own error classes to remove the fields like:
class HTTPBadRequest(OptionalRepresentation, HTTPError):
   def __init__(self, **kwargs):
       super(HTTPBadRequest, self).__init__(status.HTTP_400, **kwargs)

but personally I think that by default error classes should not have any required fields to preserve the un-opinionated nature of Falcon.

@admiralobvious Thanks for the feedback. I do think it makes sense to make those args optional in HTTPError subclasses, as they are in HTTPError itself. That being said, for some errors, there are RFC MUST or SHOULD portions of a response that don't have a sensible default we'll have to consider, but for now I think 416 is the only one we've got that falls into that camp.

@kgriffs Sure thing.
So I did some more research on HTTP status codes vs RFCs and according to RFC 2616:

The 4xx class of status code is intended for cases in which the
client seems to have erred. Except when responding to a HEAD request,
the server SHOULD include an entity containing an explanation of the
error situation, and whether it is a temporary or permanent
condition.

and

Response status codes beginning with the digit "5" indicate cases in
which the server is aware that it has erred or is incapable of
performing the request. Except when responding to a HEAD request, the
server SHOULD include an entity containing an explanation of the
error situation, and whether it is a temporary or permanent
condition.

So it seems none of the 4xx and 5xx status codes MUST have an entity but there is indeed a couple that SHOULD have one. Side note, I think Falcon implementing the SHOULDs is absolutely the right thing to do.
The 4xx and 5xx status codes that SHOULD have an entity are the following:

406 Not Acceptable - Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate.

409 Conflict - The response body SHOULD include enough information for the user to recognize the source of the conflict.

413 Request Entity Too Large - If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.

416 Requested Range Not Satisfiable - When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource.

505 HTTP Version Not Supported - The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.

As you can see, technically only 409 mention anything about a body but I guess you can add 406 and 505 to that list as well as I don't really see where you'd return that information outside of a body. 413 and 416 only mention headers which Falcon already returns.
So I think if Falcon only required title and description (I also don't have a better idea for what those should be nor how they could be made user configurable) for 409 and perhaps 406 and 505 it would already make Falcon much less opinionated status code wise.

We wrote a custom subclass of HTTPBadRequest to add a handle() method that sets the response status and body so we could capture both in our logging middleware. Otherwise all the middleware gets run in the inner try/except block of request processing before the outer try/except block actually handles any remaining uncaught HTTPErrors.
I was thinking of writing a more generic subclass of HTTPError that sets the status to one of the constants in status_codes, pulls the title from that (i.e. title = status_code[4:]), and so the constructor only needs status, description, and kwargs. (It would also have the handle method added as well).
Then I could subclass that and make error-specific versions that only take description and kwargs, and set the status in the __init__().
Either way, it would be more consistent and avoid having any errors that fall through without setting resp.body or resp.status before the request logger can run.

See also: #415

Is this a change that won't make it into 1.0?

I'm happy to try and adapt our solution into a patch if it's still possible to consider. Since it's a subclass of the existing HTTPError, I don't think it would technically introduce breaking changes.

I think that the concept of #415 could be included in such a patch as well. Main difference is that I clip off the status code for the title. Makes sense to use a default description, though I'd prefer to document a best practice to include your own description to give more useful error reporting.

Thanks everyone for the comments. This issue is starting to get overloaded, so I've split it out into several work streams.
Making title and description optional, with a default for the title based on the status:

#776
#778

Reording initializer args to be more consistent:

#777

Please take a look and add any additional thoughts to these issues.

@foresmac We may be able to get something in 1.1 as long as it isn't a breaking change. Would you mind creating a new issue re:

We wrote a custom subclass of HTTPBadRequest to add a handle() method that sets the response status and body so we could capture both in our logging middleware. Otherwise all the middleware gets run in the inner try/except block of request processing before the outer try/except block actually handles any remaining uncaught HTTPErrors.

Then we can pick up the conversation over there. I'm going to go ahead and close this one (#391).
Thanks!


Create http_over_grpc proto

This adds http_over_grpc.proto and enables it to be used.

It might be worth mentioning somewhere that the Transfer Encoding: chunked header isn't supported.

I have added a comment mentioning this. I think we might add streaming support in the future and I will clean up the comment then.

cc @mrhohn


Feature request: Provide current power consumption

With Home Assistant's new energy integration, it would be nice if we could have a sensor which reports current power draw that we can hook right in.
This has been done with the open-source Open Hardware Monitor, although I'm not sure how easy it would be to do here.
There is also this random open-source Google Code project I found which uses WMI to access a random Win32_PowerMeter instance located in the root\cimv2\power namespace; however, it doesn't look like there's a way to condense this code into a single query.

Thanks for creating an issue! We already depend on LibreHardwareMonitor which probably has the same sensors available.

I'm curious about the accuracy of a software-based power monitor. If the data isn't coming directly from the power supply, then how would the software know everything in the system is being used. CPUs and GPUs should be pretty easy to monitor. SSDs and HHDs might be capable. The rest of the components on the motherboard and cooling devices I don't think would be possible.
I am mining with two 3070s. The software reports about 220W being used by the GPUs. The energy monitoring plug is reporting 309W being used. The CPU is running about 7% with 32% of 64GB RAM being used. Disk and Network activity is 0% and there are some RGB fans in the case. (Laptop mining with a 2060 is 81W & 106W, respectively.)

Thanks for creating an issue! We already depend on LibreHardwareMonitor which probably has the same sensors available.

I can confirm that libre hardware monitor can connect to and receive data from my corsair hx1000i PSU


Dart analyzer 1.15.0: problem with UnmodifiableListView

I had code that used to be analyzed fine but now has a warning with dartanalyzer 1.15.0.
$ dartanalyzer --version
dartanalyzer version 1.15.0

My code is like this:
import 'dart:collection';

class Card {
  final String deck;
  final String identifier;

  Card(this.deck, this.identifier);
  Card.fromString(String cardData)
      : deck = cardData.split(" ")[0],
        identifier = cardData.split(" ")[1];

  bool operator ==(Object other) {
    if (other is! Card) return false;
    Card o = other as Card;
    return deck == o.deck && identifier == o.identifier;
  }

  int get hashCode => 37 * (deck.hashCode + 41 * identifier.hashCode);

  static final List<Card> all = new UnmodifiableListView<Card>(<Card>[
    new Card("classic", "c1"),
    new Card("classic", "c2"),
    new Card("classic", "c3"),
    new Card("classic", "c4"),
    new Card("classic", "c5"),
    new Card("classic", "c6"),
    new Card("classic", "c7"),
    new Card("classic", "c8"),
    new Card("classic", "c9"),
    new Card("classic", "c10"),
    new Card("classic", "cj"),
    new Card("classic", "cq"),
    new Card("classic", "ck"),
    new Card("classic", "d1"),
    new Card("classic", "d2"),
    new Card("classic", "d3"),
    new Card("classic", "d4"),
    new Card("classic", "d5"),
    new Card("classic", "d6"),
    new Card("classic", "d7"),
    new Card("classic", "d8"),
    new Card("classic", "d9"),
    new Card("classic", "d10"),
    new Card("classic", "dj"),
    new Card("classic", "dq"),
    new Card("classic", "dk"),
    new Card("classic", "h1"),
    new Card("classic", "h2"),
    new Card("classic", "h3"),
    new Card("classic", "h4"),
    new Card("classic", "h5"),
    new Card("classic", "h6"),
    new Card("classic", "h7"),
    new Card("classic", "h8"),
    new Card("classic", "h9"),
    new Card("classic", "h10"),
    new Card("classic", "hj"),
    new Card("classic", "hq"),
    new Card("classic", "hk"),
    new Card("classic", "s1"),
    new Card("classic", "s2"),
    new Card("classic", "s3"),
    new Card("classic", "s4"),
    new Card("classic", "s5"),
    new Card("classic", "s6"),
    new Card("classic", "s7"),
    new Card("classic", "s8"),
    new Card("classic", "s9"),
    new Card("classic", "s10"),
    new Card("classic", "sj"),
    new Card("classic", "sq"),
    new Card("classic", "sk"),
  ]);

  toString() => "${deck} ${identifier}";

  get string => toString();
}

The warning is:
A value of type 'UnmodifiableListView<Card>' cannot be assigned to a variable of type 'List<Card>'
This may be a regression related to #10090
However, this code has no warnings when plopped into DartPad and only sometimes shows the warning in Atom with the Dart and Flutter plugins.

Do you have strong mode enabled?

I'm not running dartanalyzer with any special flags, and I don't recall configuring it to use strong mode. How can I find out?

If you're not passing in a command-line flag ("--strong", IIRC), then it would have to be in your .analysis_options file and would look like
analyzer:
  strong-mode: true

Yeah, I'm not using the flag, nor does my project have .analysis_options.

Actually, it looks like there are some .analysis_options on my filesystem, but the dartanalyzer I'm using doesn't have strong-mode: true. I see this:
linter:
  rules:
    - annotate_overrides
    - empty_constructor_bodies
    - unnecessary_brace_in_string_interp

Could it be that .analysis_options is based on the actual imported package?
My collections packages at collections-1.5.0 have an analyzer in them with
analyzer:
  strong-mode: true

inside $HOME/.pub-cache/hosted/pub.dartlang.org/collection-1.5.0/.analysis_options

I went back and re-read the original post, and found I'd glossed over:

However, this code has no warnings when plopped into DartPad and only sometimes shows the warning in Atom with the Dart and Flutter plugins.

Options from imported packages are not used, but the options from Flutter are magic and are inherited, and do enable strong mode. I believe that DartPad is not using strong mode, so I'm fairly sure this is a strong mode issue. Thanks!

cc @sethladd as an FYI on confusion arising from options inherited from _embedder.yaml.

I can't reproduce this with the example code above by running the command line dart analyzer in neither strong mode nor spec mode.  Tested with 1.15.0 and 1.16.0-dev.4.0.  Closing this as stale, but if this still reproduces please re-open with more details (i.e. platform, exactly what sdk version you're using, any .analysis_options,  etc).


[Fabric 1.20] Refactor DynamicItemRenderer usage to fix remapping to Yarn

With Yarn mappings, renderByItem gets remapped to render, which has the same signature as DynamicItemRenderer#render, thus causing "unfixable conflicts" when remapping Lootr when it's used as a dependency. This PR changes how DynamicItemRenderer is implemented (wherever it's used), allowing Lootr to be depended upon by mods that use Yarn.

It boggles my mind that they chose the same method signature and method name for an interface like this.


[Feature Request] - Support mono-repo

Hello,
In our team we work with mono-repo (with npm workspaces).
Is it possible to support this kind of project structure ?
Best regards

Will be available in v0.3.0


Add retries for all database operations

Instead of failing if a database operator could not be performed successfully, it should be retried.
There are go modules that provide retry functionality that we can use. See #241 for the list

@mafh314 feel free to reach out about this. I can give you some pointers


Webrtc Support ?

its's great project , but does this support webrtc ?

Thanks for support.
XWebView does not support WebRTC. It just provides a bridge between JavaScript and native code.
WebRTC may be implemented as a plugin of XWebView for iOS. I would like to see that, but I have no time to do in short term. If anyone has interest in this, I will fully offer my support.


Fix RTL styles for ts-control

Fixes for bugs in PR #583
The styles were not taking effect properly due to my lack of understanding of the rtl class. Should be fixed in this PR (tested in my app)

.


Boosted Items off-hand issue

Hello.
I have encountered a bug with the Jobs plugin.
When holding items with a booster in your off-hand the booster does not apply. It appears to only work for armor slots and the item in hand. Could it be made to work for off-hand also?
Thank you.

https://github.com/Zrips/Jobs/commit/7fbfab2c4cc2233868126648274dbd64ca42e489


⚠ Bofrost.lu has degraded performance

In f67dd0a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1700 ms

Resolved: Bofrost.lu performance has improved in 1be33d8 after 25 minutes.


Called the page twice

I have a link and a container:
-# Link
= link_to 'Projects', projects_path

-# Contrainer
#main.container{ "data-pjax-container" => true }

When I click on it, it load the page twice. The first time with the X-PJAX = true but not the second time. (see attached).
Any idea ?
http://imgur.com/4Gfd2

It works now. No clue why tho.


Question 1: part 3, count of precinct by counties

Update: we're currently double checking the above to make sure we have the correct number of precincts per county!

When using st_join(), ensure the following steps for accurate results:

Ensure Unique Values: Check for uniqueness in the key columns of both datasets. If necessary, clean and standardize values to avoid mismatches during the join.
Clean Data: Before joining, perform data cleaning—this includes trimming whitespace, resolving name inconsistencies, and ensuring key columns match.
Check CRS Consistency: Make sure both datasets have the same Coordinate Reference System (CRS). Use st_crs() to verify and st_transform() to align them if needed.
Verify Data Shapes: After the join, check the shape of the resulting dataframe to confirm it aligns with expectations. This helps catch issues like duplicated rows or unexpected geometries.


[trivial] Added immutable to, and got rid of several variables in std.encoding

@schveiguy Fixed

why the inconsistency between const and immutable?

Mistake. I was thinking in terms of my other PR.
@schveiguy Fixed

LGTM. Awaiting Travis...

Auto-merge toggled on


Change base image for Dockerfile

Default user and group id is now 977 as 999 was taken.

[!CAUTION]
!!This may cause permissions issues in existing installations.
The above mentioned permissions issues can be fixed by either:

mounting the volume with another container as a root user and changing ownership of /app/data (including their contents) to 977:977
chmod -R 977:977 /var/lib/docker/volumes/${VOLUME_NAME_OR_HASH} of the volume from the host's volume directory.
chmod -R  777 /app/data (don't do this)

Dockerfile and entrypoint.sh was changed to run NO application code as a privileged user. When the container is running there is no code executed in a privileged context, as anything requiring privileges is run during build time.
Addition of a .dockerignore file to ignore non-application files and improve docker cache hits.

Proposed fix #2288

Seems ready for review, has been stable in my testing environment.

Hmm... I'm a bit worried about changing current behaviour - we have quite wide variety of users, even on some exotic setups. That's also the reason why we basically moved a lot of the logic to the entrypoint.sh script.
I think it requires deeper investigation, I'll try to check some historical issues. I guess you could also browse them by searching for Dockerfile or entrypoint keywords.

The main issues that came to mind are #1762, #1200, #1634.

#1200 would continue to be resolved as we would be running as non root.
#1657, #1762 Pertain to opinionated K8s distributions, more research needed to determine compatibility

Below is a todo list on testing deployments,

[x] docker-compose.yml
[ ] Kubernetes (I'll most likely try it on my home "cluster")
[ ] Redhat Openshift re: #1657 #1762

Could be helpful to see if the users from #1657 and #1762 if they got it up and running and for potential testing.

Confirmed a working fresh install on RedHat Openshift (see above link)

Seems like Openshift's UID randomization still works with user 977 and the rootless container.

A few questions:

Why was a liberica jdk chosen over a jdk from eclipse temurin (eg. eclipse-temurin:21-jre-alpine)? What is the benefit of this? Looking at https://whichjdk.com/, there does not seem to be any significant benefit, so I'm unsure why it was chosen.
Why was a docker image with Class Data Sharing chosen for the build stage, even though it is never enabled/used?

Why was a liberica jdk chosen over a jdk from eclipse temurin (eg. eclipse-temurin:21-jre-alpine)? What is the benefit of this? Looking at https://whichjdk.com/, there does not seem to be any significant benefit, so I'm unsure why it was chosen.

It's smaller

eclipse-temurin:21-jre-alpine - 71mb
liberica-runtime-container:jre21-slim-musl - 45mb
liberica-runtime-container:jre-21-cds-slim-musl - 52mb

I didn't know they have JRE builds

One nice thing about temurin is that maybe we could avoid changing user & group ids.

Why was a docker image with Class Data Sharing chosen for the build stage, even though it is never enabled/used?

I think we should go for the smallest one as long as it works. If that's possible, I guess it'd be nice to have a build without cds.

Why was a docker image with Class Data Sharing chosen for the build stage, even though it is never enabled/used?

That's on me, Bellsoft's tag page is crazy full, will be pushing no cds on build stage shortly.

although, using CDS/CRaC features could be something you look into, as it may improve performance.
CRaC would most likely need explicit support from reposilite, javalin, and jetty (jetty already seems to support it, with some additional configuration. see: CRaC/docs/STEP-BY-STEP.md)
but CDS (& AppCDS/Dynamic CDS) could be a free performance boost at startup. (& help with memory? tbh idk exactly how CDS works, but the website I linked said it could help with memory) at the cost of a slightly larger docker image (tbh I wonder if the CDS archive files can be bundled into the jar, so that everyone can benefit from it)

I'd say this is completely out of scope for now to be fair - we should focus on providing smooth migration first.
It'd be great if you could quickly check if using these Temurin images would still require changes in permissions on our side. If no, then maybe we should use it for now. If we'd still need similar changes with Temurin tho, I guess we could proceed with Liberica for Reposilite 3.6.0, since you've already made these changes.

If we'd still need similar (uid/gid) changes with Temurin tho, I guess we could proceed with Liberica for Reposilite 3.6.0, since you've already made these changes.

All Alpine based images will have a ping group for group 999.
ping:x:999:

If we change to a ubuntu/debian based image such as eclipse-temurin:21-jre-noble, it would be larger but not have a group 999 conflict.

The slim image we're using right now is based on debian, so maybe let's do it the following way:

Move to temurin 21 based on debian in Reposilite 3.5.x
Extend our entrypoint file to provide a migration script that will start using a new default id.
2.1. If existing data is owned by user with old default id, we'll also automatically try to update it to the new one.
For next minor version (e.g. 3.6.0) we could migrate to liberica with a new setup based on alpine

Seems like a pretty good migration strategy, I'll write up changes to the scripts and make a PR, I'll rename this one and maybe return it to draft status.

I don't quite know how to benchmark the two images against each other. But if it offers great enough performance boost it could be worth keeping around.

afaik, CDS only affects memory for classes shared between multiple jvms, as well as decreases startup times. but I could be wrong.

The slim image we're using right now is based on debian, so maybe let's do it the following way:

Move to temurin 21 based on debian in Reposilite 3.5.x
Extend our entrypoint file to provide a migration script that will start using a new default id.
2.1. If existing data is owned by user with old default id, we'll also automatically try to update it to the new one.
For next minor version (e.g. 3.6.0) we could migrate to liberica with a new setup based on alpine

Changes made and PR created #2303


Nights of Azure / Yoru no Nai Kuni [PCSG00557]

App summary

App name: Nights of Azure / Yoru no Nai Kuni
App serial: PCSG00557
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 2973
Commit hash: https://github.com/vita3k/vita3k/commit/40ee98e5
CPU backend: Unicorn
GPU backend: Vulkan

Test environment summary

Tested by: Alastor
OS: Windows 8.1
CPU: Intel e6500 (OC to 3.30GHz)
GPU: Nvidia GeForce GTX 650
RAM: 8 GB

Issues
Using unicorn cpu backend, game is able to boot but gets stuck on black screen after 2 intro images. Using Dynarmic, it crashes before booting.
EDIT: On Latest build (11-Jan-23), game does the same on Dynarmic backend.
Screenshots

Log
vita3k.log
Recommended labels

Menu

App summary

App name: Nights of Azure / Yoru no Nai Kuni
App serial: PCSG00557
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3249
Commit hash: Vita3K/Vita3K@349d89a9
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary
Tested by: space1
OS: Windows 11
CPU: AMD Ryzen 5 3600
GPU: Nvidia 3070
RAM: 32 GB
Issues
Screenshots

Log
PCSG00557 - [よるのないくに].log
Recommended labels
Playable

App summary

App name: Nights of Azure / Yoru no Nai Kuni
App serial: PCSG00557
App version: 1.00

Vita3K summary

Version: v0.2.0
Build number: 3703
Commit hash: Vita3K/Vita3K@0a3ba020
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Alastor
OS: Microsoft Windows 10 Professional (build 19045)
CPU: CPU: 11th Gen Intel(R) Core(TM) i7-11700KF @ 3.60GHz | 16 Threads | 3.6 GHz
GPU: NVIDIA GeForce RTX 3070
RAM: 48 GB

Issues
Game is able to boot but gets stuck on black screen after 2 intro images. As @EternalShackles described.
Screenshots

Log
vita3k.log
Recommended labels

Regression, Intro


Any chances to introduce FeMaSR support?

Thanks to devs for great project.
I would like to see support for FeMaSR project in chainner:
https://github.com/chaofengc/FeMaSR
Pretty good results with that solution.
Thanks in advance!

Thank you devs for implementing FemaSR :)
I have some errors for dimension for scanned or cropped images that are not classic 4:3 shape.
FBCNN and other models dont have these problems.
Keep rocking!

I have some errors for dimension for scanned or cropped images that are not classic 4:3 shape.

2x FeMaSR models require the width and height of the input image to be multiples of 32. Unfortunately, chainner currently doesn't account for that, and so you'll get this shape error. This is something we'll have to fix (https://github.com/chaiNNer-org/chaiNNer/issues/2335).
In the meantime, you can work around this issue by padding the input image yourself. It's cumbersome, but it can be done.

I tried with this "complicated" way, but unsuccessfull. again errors. Maybe I mistaked somehow.But tried in batch.

input image was 640x480px not 1280x960..as error saying.
Could you please share this method project file (.chn) but modifed for batch processing?
thanks!

Your tile size is set to Auto, so the Upscale node may resize your image internally. Set it to No Tiling and then it should work.


(ScreenCloud) Add package

Description
Adds ScreenCloud, a FOSS screenshot and upload utility with plugin support, available for Windows, OS X and Linux.
The package is automated, and since I'm using it I will continue to keep it working.
Motivation and Context
Been using the software for a long time, even wrote some plugins for it, seemed right that it should be available here.
How Has this Been Tested?
Tested the MSI installer, rest is drycoded for the PR hooks to test as I had limited time to set up the AU environment locally.
Types of changes

[ ] 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)
[ ] Migrated package (a package have been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this mean usually the notes in the description of a package).
[ ] I have updated the documentation accordingly (this mean usually the notes in the description of a package).
[x] All files is up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Nice tool (except 35MB size)
Suggestion: provide parameters to skip questions on startup, to make it just run: account, welcome and start with computer. (all those could be set via preferences anyway, and are totally irrelevant if you use FTP)

@majkinetor Those requests are better forwarded to the author of the application, I just intend to maintain the package for Chocolatey.

Thats why those are not requests but suggestions. Apps should be usable ASAP IMO. It might be considered a rant but this app, once installed,  requires another 10 mins to setup which defeats the purpose of automations and the only benefit one gets is from automatic update which this app actually provides nativelly.

Accidentally closed

That should correct all of your requested changes.

@majkinetor The software is mirrored to SourceForge if you'd rather have me use that as a source instead.

You can try to see if its going to chagne the build on AV, sourceforge works from it.

Local tests worked, AV should be happy as well now.

@p3lim Thanks alot for your contribution to this repository.


Release/1.22

I would like to update the main branch with this to move over the documentation to the tket website, ignoring the the not working checks. I have set the version to unreleased in the changelog to point this out.

I would like to update the main branch with this to move over the documentation to the tket website, ignoring the the not working checks. I have set the version to unreleased in the changelog to point this out.

Why do we need to update the main branch to do this? I am anyway not sure it's a good idea, since the extension doesn't work -- I'd be in favour of removing all references to it unless and until it's working again.

We clone the repos from main for the generation of the site. (We could change that for this extension, but I don't think that is a good idea)
I think removing it is valid, too. But that would only show effect after the next pytket release.

Yeah I think we should remove it, and maybe archive the repo.

We don't need this anymore


Unnecesary limit check

if buffer.position() < buffer.limit() is true but the engine still returns buffer underflow, it will loop forever

Hello alonch, and first of all thanks for cloning and using my code, it really cheered me up. :)
The method that these changes are about, handleBufferUnderflow, is called when a BUFFER_UNDERFLOW status appears after an engine.unwrap.  This will happen when:

The SSLEngine was not able to unwrap the incoming data because there were not enough source bytes available to make a complete packet.

that indeed, can mean that the buffer's size is too small to fit the data and in that case, you have to expand it. But, it can also mean that the peer has just not the desired amount of data yet, while the buffer has still plenty of empty bytes. This happens quite a lot in the Demo example of this project (you can print a log message in the if (buffer.position() < buffer.limit()) condition to see for yourself) and if there wasn't for the if condition, the buffer would be enlarged for every buffer underflow, finally causing a Java heap space OutOfMemoryError.
It is true that, if the engine still returned buffer underflow forever, the method would loop forever. But this would be an abnormal situation, that should be faced with a corresponding method (perhaps a response timeout?).
So, I think that the if condition is properly placed there and, unless you have any objection, I will close the request.

Hi Alkarn, Thank you for taking the time to answer me.
I see your point in the client side. I had the problem in the server side where only reads once.
To solve this, it should do
if (engine.getSession().getPacketBufferSize() > buffer.limit()) return buffer;
"if unwrap() were to return a SSLEngineResult.Status.BUFFER_UNDERFLOW, the application should call SSLSession.getPacketBufferSize() to ensure that the source buffer has enough room to hold a record (enlarging if necessary), and then obtain more inbound data."
https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLEngine.html
Let me know what you think

You are definitely correct! The if condition you propose and quote from Java documentation is elegant and solves the problem.
I will include it in my code and commit it with minor - naming - modifications. Thanks! :)

Great, thank you alkarn!
closing PR


Ability to set custom hostname for SolrCloud

Hello,
Much like the addressability.external.domainName value in the SolrCloud resource, it would be helpful to have something like addressability.external.hostName to specify a particular hostname for external accessibility. It appears now that the hostname is always set to <namespace>-<solrcloud-name>-solrcloud (https://github.com/apache/solr-operator/blob/main/api/v1beta1/solrcloud_types.go#L1339) which is a bit redundant for my team's implementation of one SolrCloud per namespace (we end up with something like solralpha-solralpha-solrcloud.domain.com).
Thanks for your consideration!

Had the same need. Perhaps a configurable service-name template would be cool, where the default could be serviceNameTemplate: %n-%r-solrcloud given that %n=namespace, %r=releaseName.

Yeah, I agree that could be cool!


ssh: Add flag to skip availability check for bastion

What this PR does / why we need it:
ssh subcommand: You can now skip the availability check for the bastion host using the flag --skip-availability-check. This is useful when you want to spin up a bastion host but gardenctl can't reach the bastion and thus would not be able to check for the availability.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

`ssh` subcommand: You can now skip the availability check for the bastion host using the flag `--skip-availability-check`. This is useful when you want to spin up a bastion host but `gardenctl` can't reach the bastion and thus would not be able to check for the availability.

Is the purpose of this flag is accelerate ssh access as bastion has already been created

No, this was not the purpose, but it might come in handy in case we support to re-use the bastion instead of re-creating it.
We have a case where the bastion is not directly reachable from the users machine, so the availability check would fail and the bastion creation would time out after 10m. This flag gives the user means to skip the availability check.


Two cards have empty string as their name probably because they have layout=flip but no position=1

Two cards have empty string as their name probably because they have layout=flip but no position=1.
Zndrsplt, Eye of Wisdom and another card are marked as layout flip (and others) when they just reference coin flipping!

This probably needs logging/fixing at mtgjson.

Okaun, Eye of Chaos is the other card.

https://github.com/mtgjson/mtgjson/issues/586
https://github.com/mtgjson/mtgjson/issues/588

When this is fixed
CREATE INDEX idx_name on _cache_card (name(142))

should be changed to
CREATE UNIQUE INDEX idx_name on _cache_card (name(142))

which could have significant perf implications and will warn us about stuff like this in future.

I can't get my mtgjson env working and a complete rewrite of mtgjson is underway so I think I'm going to patch this at our end.

2055089e patches this on our end.
4aac2c02 makes the index on name a unique index.


[Suggestion] Add configuration option for adjusting how much charge holdout zones get from killing monsters and for how long monsters should have a speedboost upon spawning.

Title. The original VoidFieldsQoL mod had configuration options for how much charge killing an enemy gave to the holdout zones in the void fields and how long the speedboost on initial spawning lasts for.
Making these variables adjustable would allow players to better get the kind of experience they want with the mod. Some people may want charge to increase on monster kill but think the default value is too high for example.

Sure, package updated.


NEXT UP: simulate_next_roll for going up to 2 (or 3 if kept_partial_roll=[]) rolls in the future

Return 1D array if num_rolls_more = 1
return 2D array if num_rolls_more = 2
return 2D array if num_rolls_more = 3

If you want to factor in previous roll as a prior then just keep calling it for 1 more round and pass in the 1s target


Add missing translation capabilities to ListGroup

Is your feature request related to a problem? Please describe.
ListGroup has a create, delete and toggle button which all lack translations. Tooltips for these buttons as well as the indicator for how many items the listGroup contains, also lack translations.
Describe the solution you'd like
It should be possible to create translations for these buttons and their tooltips. We could achieve this by passing the translate function as a prop.
Additional context

I would like to tackle this issue.

I think it makes sense. Feel free to tag me on the PR.


Unobtainium Replication

Forgive me if this is an intentional quirk of unobtainium, but unobtainium blocks require 4 ingots to craft, but can be crafted back into 5, leading to an infinite supply of the material.

https://github.com/jsburger/Architects-Palette/blob/1.20.1/src/main/resources/data/architects_palette/recipes/unobtanium.json

This is in fact intentional behavior, no trouble.


Integrate/incorporate https://github.com/STOR-i/Changepoints.jl

opening this quickly before I forget, and will write more later. Software with similar goals exists and we have to think how to integrate or incorporate to not duplicate effort or content: https://github.com/STOR-i/Changepoints.jl

If we use exactly our framework, as it is now, and then use as the indicator metric eg. complexity entropy, and as the change metric e.g., any distribution distance function, we also find change points where it occurs. It is just a matter of what is the indicator and what is the change metric. ChangePoints.jl however uses a compelte different algorithm to find a change point. We use significance testing via surrogates to find a change point. They use optimizing a cost function.

So the question is, how to unite these two compeltely different approaches under a common API.

Closing in favor of #52

And we have solved it: we now have a way to unite these completely different approaches under a common API.


Incorporate parser and data container for sequence assembly graphs?

In talking with Zech and Jamie during a code review yesterday about the positional metadata problem (#1159), one thing that came up was incorporating support for graph-based representation of sequence collections (e.g. assemblies). Most microbial genomes aren't closed, and FASTA format leaves out a bunch of information about the relationships among contigs that can be recovered from the assembler. Would it be useful to have a way to explicitly encode that information within Skbio? In particular, this seems like it would be useful for projects comparing or manipulating large numbers of microbial genome assemblies.
There are a number of formats for representing assembly graphs currently in use, but GFA in particular seems well specified and in use by a number of tools, such as the BANDAGE assembly graph visualization tool.
UPDATE: this is the same as issue #1248.
-j

Let's close this in favor of #1248.


Release v3.3.0

Shout out to everyone. This was definitely a team effort. It's great to see so many names on the CHANGELOG this release.
@jakesjews @rondale-sc @Techn1x @pauln @JosephHalter


NOTICK: Dependency version upgrade for Jackson, JUnit, Hibernate, Detekt and the retry plugin

This PR contains the following dependency version upgrades:

Hibernate 5.6.9.FINAL -> 5.6.10.FINAL
Jackson 2.13.1 -> 2.13.3
JUnit 5.8.2 -> 5.9.0
Detekt 1.20 -> 1.21
Retry plugin 1.3.2 -> 1.4.0

The detekt plugin upgrade has resulted in some legacy code flagging up new warnings, as well as general warnings being reported for incorrectly declared detekt configuration. These have been addressed.

Should you bump the API version? As some dependencies are declared in the runtime-os as well so there might be some version clashes?

Should you bump the API version? As some dependencies are declared in the runtime-os as well so there might be some version clashes?

I think we already have this problem with Jackson - it's at 2.13.1 here and 2.13.2 in runtime-os. It seems that having it declared twice at different versions doesn't affect the build, but it would certainly be better if they were aligned. (I think gradle resolves the clashing dependencies problem for you by picking the higher one, although I don't know how/if it copes with major version skew.) I've just raised https://github.com/corda/corda-runtime-os/pull/1746 that will address the Jackson problem, though there may be others.


Pass full info about blobs shape to AutoDiff

Signed-off-by: Valeriy Fedyunin<EMAIL_ADDRESS>

https://github.com/neoml-lib/neoml/pull/349


Minor error in advanced example

var auth = 'Basic' + Buffer.from(userName + ":" + password, 'utf8').toString('base64');

should be
var auth = 'Basic ' + Buffer.from(userName + ":" + password, 'utf8').toString('base64');

(note the space after "Basic")
Also it should probably be ipconfig instead of ipaddress ;-)

Incorporated and thanks


document --enable-web

In order to work with cocoon you need to run flutter config --enable-web but that isn't documented in the readme.

Triage: is this still an issue?

@digiter According to our own documentation on web development, yes: https://flutter.dev/docs/get-started/web
There hasn't been a change to the cocoon documentation either.

Hello @gaaclarke, is this still an issue now that web has gone stable?

Hello @gaaclarke, is this still an issue now that web has gone stable?

Nope.


[ART-6761] update default arch for microshift

stop syncing microshift for s390x and ppc64 arch

This is ok-ish, though ideally this should be controlled by a config.


fix: do not throw on non-CVE vulnerability

rebuild audit.json file due to https://ossindex.sonatype.org/updates-notice

📦 Published PR as canary version: Canary Versions

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

Ugh, that's a horrible auditjs.json diff 😭

Yeah, they've totally changed ids and as well extended types of vulnerabilities reports

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:

:rocket: PR was released in<EMAIL_ADDRESS>:rocket: