can't decode byte 0x9a

Hi,
i just installed the latest update for macOS High Sierra (10.13.6).
As I am using Nvidia GTX1080 graphics card, I had installed Nvidia WebDriver.
After the update the WebDriver was no longer compatible with macOS version.
That's why I used this app to patch the version.
When executing the Run.Command the following error occurs:
 ##################################################
 #              Web Driver Toolkit                #
##################################################

OS Version:       10.13.6 - 17G4015
WD Version:       3<IP_ADDRESS>.40.108
WD Target Build:  17G4015
Newest:           None for this build number!
'utf8' codec can't decode byte 0x9a in position 756: invalid start byte

I tracked the problem down. In the bdmesg.py file on line 34, the result of the subprocess is decoded with UTF-8.
   # Runs ioreg -l -p IODeviceTree -w0 and searches for "boot-log"
    p = subprocess.Popen(comm, shell=False, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    bd, be = p.communicate()

    for line in bd.decode("utf-8").split("\n"):
        # We're just looking for the "boot-log" property, then we need to format it
        if not '"boot-log"' in line:
            # Skip it!
            continue

After removing the decode("utf-8"), the script works as expected.
I am not sure, if this problem occurs for every hackintosh or just for me.

Looks like there's some special chars in your boot-log that utf-8 can't decode. Can you run ioreg -l -p IODeviceTree -w0 | grep -i "boot-log" > ~/Desktop/bdmesg.txt in terminal and send the resulting bdmesg.txt file on your Desktop?

So - I tried storing that same char (0x9a) "Ě" in a text file (called text.txt on my desktop), and cating its contents via both python 2 and python 3, then decoding and printing it.  The script used is as follows:
import subprocess as s

p = s.Popen(["cat","text.txt"], shell=False, stdout=s.PIPE, stderr=s.PIPE)
o,e = p.communicate()
print(type(o), o)
print(type(e), e)

print(o.decode("utf-8"))

My hope was to recreate the error you are having above by causing some subprocess to spit out a character that's not terribly friendly with utf-8 and see if I could print and decode it.
The output is as follows:
CorpNewt's iHack:desktop corp$ python3 /Users/corp/Desktop/test.py
<class 'bytes'> b'\xc4\x9a'
<class 'bytes'> b''
Ě
CorpNewt's iHack:desktop corp$ python /Users/corp/Desktop/test.py
(<type 'str'>, '\xc4\x9a')
(<type 'str'>, '')
Ě

Would you mind testing the same process to see if that fails as well?  If it doesn't - could you dump your whole ioreg via the following and send it ioreg -l -p IODeviceTree -w0 > ~/Desktop/ioreg.txt?
Attached is the text doc I used - github does not allow me to send .py files - but the code is above in the first code block.
text.txt

CorpNewt

Thanks for helping me debug this - I'll give the ioreg.txt file a look and see what I can figure out.  Hopefully I'll have more tests to run (or even better, a solution) shortly!
-CorpNewt

No problem :-) Thanks for providing this script. Saved my day more than once!
If I can help you, don't hesitate to ask ...

I just pushed a small update to the bdmesg.py file that should only attempt to decode the output if running py3, and the output type is bytes.  Hopefully that fixes the issue.  If it works, I'll update that module (and a few other things) on my other repos as well.

Yes, indeed.
I just cloned this repository again to catch the latest changes.
When executing the Run.Command the version information about OS etc are shown and also the menu.
It seems that this fixed the problem. Thanks

Sounds good - I'll push the changes to my other repos and close this issue.
Thanks for your patience!
-CorpNewt


Unexpected matchlabels added

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
While installing istio with istioctl 1.16.7 My ingress gateway deployment suddenly has extra matchLabels  even though I didn't add any matchLabels.
Changed matchLabels
spec:
  selector:
    matchLabels:
      app: istio-ingressgateway
      chart: gateways
      heritage: Tiller
      istio: ingressgateway
      release: istio

My former mathLabels were like this
spec:
  selector:
    matchLabels:
      app: istio-ingressgateway
      istio: ingressgateway

Because of these specs I'm unnable to upgrade my istio version to 1.18  with error Invalid value:
v1.LabelSelector{MatchLabels:map[string]string{"app":"istio-ingressgateway", "istio":"ingressgateway"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
But installing with the same specs back to 1.16 works just fine even though I didn't add any match labels
Does anyone have the same problem?
Version
istioctl version
client version: 1.16.7
istiod version: 1.16.7
data plane version: 1.16.7 (1316 proxies)

kubectl version --short
Client Version: v1.25.15
Kustomize Version: v4.5.7
Server Version: v1.25.16-eks-508b6b3

helm version --short
v3.13.1+g3547a4b

Additional Information
No response

Istio 1.16 is (long since) end of life. I am not quite sure the cause of this, but i have verified these are not set on supported versions so I would assume this has been fixed since. Please re-open if you see this on supported versions. Thanks!


Teeeeeeeeeny tiny fix

Set reminders if daily is already claimed

Nice idea

I've said it once, and I'll say it again, not sure why you want to add this functionality, as we have a reminder command as it is lol

ease of use? Easier to type that than ?remind in 1 day to claim daily, plus ive seen users assume it will work that way, so why not add the functionality

On 17 Nov 2017, at 15:15, York<EMAIL_ADDRESS>wrote:
I've said it once, and I'll say it again, not sure why you want to add this functionality, as we have a reminder command as it is lol
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

ease of use? Easier to type that than ?remind in 1 day to claim daily, plus ive seen users assume it will work that way, so why not add the functionality
(Although if you do plan to add it, give it a quick test first, I cant atm)

i will stop dreaming now


Remove Title Bar; How?

Is there a possible option or line of code for the title bar to temporarily minimize/not be seen when windowed if not hovered on by the mouse for awhile?

Hmm… no. It looks like a very specific/odd need to me :thinking:
If you don't want borders, run scrcpy --window-borderless.

Hmm… no. It looks like a very specific/odd need to me 🤔
If you don't want borders, run scrcpy --window-borderless.

Thanks, I'll check it out


Revert "Add support for sqlite3_interrupt"

Reverts mapbox/node-sqlite3#518

reverted due to a failing test: https://travis-ci.org/mapbox/node-sqlite3/jobs/124777119#L1321


Proposal to define a strict value for aud claim in the private_key_jwt

Problem description
Referring to the CIBA specs, the aud claim of the private_key_jwt can be any of the 3 options mentioned below.
The proposal is to prevent reuse of the private_key_jwt at other endpoints.

The Client MUST authenticate to the Backchannel Authentication Endpoint using the authentication method registered for its client_id, such as the authentication methods from Section 9 of [OpenID.Core] or authentication methods defined by extension in other specifications. Note that there's some potential ambiguity around the appropriate audience value to use when JWT client assertion based authentication is employed. To address that ambiguity the Issuer Identifier of the OP SHOULD be used as the value of the audience. To facilitate interoperability, the OP MUST accept its Issuer Identifier, Token Endpoint URL, or Backchannel Authentication Endpoint URL as values that identify it as an intended audience.

Possible evolution
Enforce the aud claim of the private_key_jwt to be the URL of the respective endpoint (as a string) at which the assertion is received, it must not be an item in an array.
The URLs of the endpoint can be populated from the OpenID Provider's /.well-known/openid-configuration with the following metadata:

token_endpoint
backchannel_authentication_endpoint

Example: If the endpoint at which the assertion is being received is the backchannel_authentication_endpoint, the Relying Party will populate the aud claim of the private_key_jwt to be the URL of the backchannel_authentication_endpoint as per the OpenID Provider's /.well-known/openid-configuration.
Alternative solution
N.A
Additional context
OIDC profile is being defined for CAMARA

From my point of view, it is not a good idea to limit the value of the aud claim to that of the endpoint to which the request is made. The CIBA specification is clear (Issuer Identifier, Token Endpoint URL, or Backchannel Authentication Endpoint), and forcing implementations to deviate from the standard by rejecting requests they should accept could jeopardize existing integrations.
If replay attacks are to be avoided, there are better mechanisms, such as the jti claim to prevent reuse of the token.

@garciasolero
The concern is that the same signed JWT can be interchangeably use between the three endpoints:

/bc-authorize
/token
/authorize

/token endpoint should be more secured as it allows client_credentials with scope.
The aud claim can be seem similarly as a scope for access.

Proposed CAMARA OIDC - client-authentication profile states

The Audience MUST be the URL of the Authorization Server's Token Endpoint.

Please clarify on this point.

@mhfoo How about the text in this commit?
https://github.com/camaraproject/IdentityAndConsentManagement/blob/3353d10d371dd95bce6f8f9bc1dc9f3ae60d24a9/documentation/CAMARA-Security-Interoperability.md#client-authentication
Client Authentication
This CAMARA document allows one client authentication method, private_key_jwt, as defined in OIDC OIDC Client Authentication
OIDC Client Authentication defined the following about the audfield:
REQUIRED. Audience. The aud (audience) Claim. Value that identifies the Authorization Server as an intended audience. The Authorization Server MUST verify that it is an intended audience for the token. The Audience SHOULD be the URL of the Authorization Server's Token Endpoint.

This document defines that for OIDC Authorization Code Flow and OAuth2 Client Credentials Grant the audience MUST be the URL of the Authorization Server's Token Endpoint. This document defines that for OIDC CIBA the audience MUST be the Backchannel Authentication Endpoint.

I think it is better to separate the use cases because some involve different types of JSON Web Tokens (JWTs). On one hand, we have the request object parameter, and on the other hand, we have the client assertion for authentication.

Request Object by value in /authorize request: It must be the Authorisation Server Issuer Identifier URL (RFC9101):

The value of aud should be the value of the authorization server (AS) issuer

Client assertion for authentication in server-server requests: I think there could be some confusion here, and certain standards, such as CIBA, are proposing solutions to ensure interoperability. I think setting it up similar to CIBA could be the solution: Authorisation Server Issuer Identifier, Token Endpoint URL or Requested Endpoint URL. So the table you suggested would look like this:

Invoking Endpoint \ Audience
issuer
token endpoint
bc-authorize endpoint
any other endpoint

/token
Accept
Accept
Reject
Reject

/bc-authorize
Accept
Accept
Accept
Reject

The aud claim requirements for authorization servers in the FAPI profile are: issuer, token endpoint, or the endpoint URL (as I suggested above). I'm not sure why the client requirements section restricts sending only the issuer (and as a string, not in an array) when authorization servers are expected to accept the other values. In my opinion, I would include the requirements for the authorization server.

The aud claim requirements for authorization servers in the FAPI profile are: issuer, token endpoint, or the endpoint URL (as I suggested above). I'm not sure why the client requirements section restricts sending only the issuer (and as a string, not in an array) when authorization servers are expected to accept the other values. In my opinion, I would include the requirements for the authorization server.

The section on clients is a "should", so clients can still use the other allowed values in  FAPI 2.0 security.
The current text in #121 is this:

This document defines that for OIDC Authorization Code Flow and OAuth2 Client Credentials Grant the audience MUST be the URL of the Authorization Server's Token Endpoint.
This document defines that for OIDC CIBA the audience MUST be the Backchannel Authentication Endpoint.

In other words, the aud is always the url the request is sent too. Which seems to be a simple rule, which is somewhat more secure than additionally allowing the "issuer" as well.

Invoking Endpoint \ Audience
issuer
token endpoint
bc-authorize endpoint
any other endpoint

/token
Reject
Accept
Reject
Reject

/bc-authorize
Reject
Reject
Accept
Reject

Please suggest "better" text if you think that is needed.

Suggested text aligned with what the CIBA standard and the FAPI profile state:
To facilitate interoperability, the Authorization Server MUST accept its issuer identifier, the token endpoint URL, or the URL of the endpoint at which the assertion was received as values of the audience claim.

@AxelNennker @garciasolero
The current text in https://github.com/camaraproject/IdentityAndConsentManagement/pull/121 is this:

This document defines that for OIDC Authorization Code Flow and OAuth2 Client Credentials Grant the audience MUST be the URL of the Authorization Server's Token Endpoint.
This document defines that for OIDC CIBA the audience MUST be the Backchannel Authentication Endpoint.

In other words, the aud is always the url the request is sent too. Which seems to be a simple rule, which is somewhat more secure than additionally allowing the "issuer" as well.

Invoking Endpoint \ Audience
issuer
token endpoint
bc-authorize endpoint
authorize endpoint
any other endpoint
mulitple endpoints

/token
Reject
Accept
Reject
Reject
Reject
Reject

/bc-authorize
Reject
Reject
Accept
Reject
Reject
Reject

/authorize
Reject
Reject
Reject
Accept
Reject
Reject

Agree with Axel's statement above. The aud claim should not be an array.
The signed Object Request RFC 9101 is a signed JWT and it is communicated in the public domain over the Internet when performing the Auth Code flow.
The signed JWT maybe used to invoke the /token /bc-authorized endpoints by a bad actor, as mentioned in Cross-JWT Confusion.

As described in Section 2.8 of [RFC8725], attackers may attempt to use a JWT issued for one purpose in a context that it was not intended for. The mitigations described for these attacks can be applied to Request Objects.
One way that an attacker might attempt to repurpose a Request Object is to try to use it as a client authentication JWT, as described in Section 2.2 of [RFC7523]. A simple way to prevent this is to never use the client ID as the sub value in a Request Object.

The above proposal is leaving the API Consumer to secure the Operator's endpoint. As an Operator, we should secure our endpoints with restrictions.

Another way to prevent cross-JWT confusion is to use explicit typing, as described in Section 3.11 of [RFC8725]. One would explicitly type a Request Object by including a typ Header Parameter with the value oauth-authz-req+jwt (which is registered in Section 9.4.1). Note, however, that requiring explicitly typed Request Objects at existing authorization servers will break most existing deployments, as existing clients are already commonly using untyped Request Objects, especially with OpenID Connect [OpenID.Core]. However, requiring explicit typing would be a good idea for new OAuth deployment profiles where compatibility with existing deployments is not a consideration.
Finally, yet another way to prevent cross-JWT confusion is to use a key management regime in which keys used to sign Request Objects are identifiably distinct from those used for other purposes. Then, if an adversary attempts to repurpose the Request Object in another context, a key mismatch will occur, thwarting the attack.

Another approach is to issue different client_id for the same backend application when performing auth code flow and CIBA flow.
Bank XYZ will use client_id A for auth code flow, client_id B for CIBA flow. client_id A will not be accepted for CIBA flow, client_Id B will not be accepted for auth code flow.

Regarding the following two sections:

Another approach is to issue different client_id for the same backend application when performing auth code flow and CIBA flow.

Bank XYZ will use client_id A for auth code flow, client_id B for CIBA flow. client_id A will not be accepted for CIBA flow, client_Id B will not be accepted for auth code flow.

@mhfoo Please do not add even more options to the mix.

Not sure why write about 9101. Yes, that is also a signed JWT, and there also can be a mixup-attack.
Does your text after "The signed Object Request..." help with the solution if you assume that we assume that more concrete aud values are more secure?

To summarize this issue's discussion:
Specifying single, specific values for aud depending on the use-case and end point improves security.
Doing that might possibly be bad for interoperability. Even though I am one of the editors of the CIBA standard I do not agree with the interoperability argument. Specifying the correct aud string is simple and I believe that clients are not overburdened with this task. While at the same time, we prevent mixup attacks.
You might challenge the "simple"-argument, but I think the other proposals (key management) are too complicated and implementing the aud-requirement discussed here is indeed simple.
Some examples for aud value in various implementations:
The example seem to use the endpoint url which agrees existing text.

https://developer.okta.com/docs/guides/build-self-signed-jwt/java/main/

aud 	Required. The full URL of the resource that you're trying to access using the JWT to authenticate. For example: https://${yourOktaDomain}/oauth2/default/v1/token

https://cloudentity.com/developers/basics/oauth-client-authentication/private-key-jwt-client-authentication/

Example: "aud" : "https://localhost:8443/{tid}/{aid}/oauth2/authorize"

https://kb.authlete.com/en/s/oauth-and-openid-connect/a/client-auth-private-key-jwt

aud [REQUIRED] Audience. A value that identifies the authorization server as an intended audience. The authorization server must verify that it is an intended audience for the token. The audience should be the URL of the authorization server's token endpoint.

https://connect2id.com/products/server/docs/guides/oauth-client-authentication

aud set to the token endpoint URL.

https://docs.authlib.org/en/v0.15.3/specs/rfc7523.html

The value https://example.com/oauth/token is your authorization servers’s token endpoint, which is used as aud value in JWT.

 As I said, I thing that using the endpoint url is not obstacle for client developers and provides better security.

@AxelNennker
As I mentioned earlier, we should clearly separate the audiences for these endpoints because they have their own requirements: token and bc-authorize endpoints deals with client assertions for authentication, while the authorize endpoint deals with request objects.
In relation to the audience claim within a client assertion, we suggest what CIBA standard or FAPI profile define: to accept the issuer, the token endpoint and the endpoint URL as valid audiences to ensure interoperability.
CIBA:

Note that there's some potential ambiguity around the appropriate audience value to use when JWT client assertion based authentication is employed. To address that ambiguity the Issuer Identifier of the OP SHOULD be used as the value of the audience. To facilitate interoperability, the OP MUST accept its Issuer Identifier, Token Endpoint URL, or Backchannel Authentication Endpoint URL as values that identify it as an intended audience.

FAPI:

5.3.2. Requirements for authorization servers
<IP_ADDRESS>. General requirements
[...]
8. shall accept its issuer identifier value (as defined in [RFC8414]) either as the aud claim (when a string) or as a member of the aud claim (when an array) received in client authentication assertions;
9. should accept its token endpoint url or the url of the endpoint at which the assertion was received, either as the aud claim (when a string) or as a member of the aud claim (when an array) received in client authentication assertions;

Of course, you can simplify the possible values and, for example, accept only the endpoint URL. However, this would affect already deployed solutions that follow the CIBA standard. Therefore, we suggest that the profile should allow authorization servers to accept these three values and recommend using the endpoint URL to clients.

Regarding what would happen if we support RFC9101 by passing request objects by value, the standard already specifies what the value of the audience should be:

The value of aud should be the value of the authorization server (AS) issuer, as defined in [RFC8414].

In relation to your concern about the use of a JWT issued for a request object in authorize flow as a client authentication JWT, the RFC9101 already suggests a way to mitigate this by avoiding the client_id as sub value within the request object:

One way that an attacker might attempt to repurpose a Request Object is to try to use it as a client authentication JWT, as described in Section 2.2 of [RFC7523]. A simple way to prevent this is to never use the client ID as the sub value in a Request Object.

@AxelNennker

Not sure why write about 9101. Yes, that is also a signed JWT, and there also can be a mixup-attack.
Does your text after "The signed Object Request..." help with the solution if you assume that we assume that more concrete aud values are more secure?

Regarding the above question, it is related to #128.
The following is the proposed text for PR #121 under OIDC Authorization Code Flow section.
The OIDC Authorization Code Flow is defined in OpenID Connect, incorporating RFC 9101, Passing a Request Object by Value.

We are not making progress with this issue.
I changed the text regarding client authentication and the aud values to RECOMMEND instead of MUST.
The AZ still MUST ensure that it is the intended audience. The document, as always following the principle of no repeating the obvious, does not mention that fact because the standards are clear and no clarification is needed.
Client Authentication
This CAMARA document allows one client authentication method, private_key_jwt, as defined in OIDC
OIDC Client Authentication
This document RECOMMENDS that for OIDC Authorization Code Flow and OAuth2 Client Credentials Grant the audience SHOULD be the URL of the Authorization Server's Token Endpoint.
This document RECOMMENDS that for OIDC CIBA the audience SHOULD be the Backchannel Authentication Endpoint.


jcpicker: Fix checkver

Closes #XXXX

Relates to #XXXX

[X] I have read the Contributing Guide.

/verify

/verify


Setting Up the Service Principal is not included in Doc

Set up a service principal.
Create an Azure Key Vault instance.
Register an application in Azure AD.
Set up the Verifiable Credentials service.
As per the steps mentioned above in the docs, the Set Up Service Principal Step is missing.  I have perused the doc history and there seems to have been a PowerShell guide which is now scrapped off.
What is the new way to Set Up Service Principal?

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

ID: f84b158e-eebc-7d96-0992-8864316ddf5c
Version Independent ID: 8909ba9b-bf26-fb5c-29f0-76244984e75a
Content: Tutorial - Configure your tenant for Azure AD Verifiable Credentials (preview)
Content Source: articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md
Service: active-directory
Sub-service: verifiable-credentials
GitHub Login: @barclayn
Microsoft Alias: barclayn

@paulinembabu Thank you for opening this issue. We are working internally on this and it will be updated soon. We regret the inconvenience. As the service is in preview at the moment there are multiple E2E validations that we are working on internally and we will update the document soon on this.

@paulinembabu There are some changes to the service which will be updated . For the moment, you would enable the verifiable credentials preview the following service principals automatically get created in your tenant . That is when you click on save and create credentials.

So if you try to search for the following related APIs in the section API my organization uses as mentioned in the article you will see the relevant API . These service principals will only get created, after you have enabled the verifiable credentials .

Hence the section Setting up service principal was removed. Hope this is helpful  Should you still face any issue , please let us know by opening a new issue tagging this one and we will be happy to help .
Thank you .

@shashishailaj Thank You. That works as expected


Change Value classes to decorator pattern.

Instead of only passing our value, pass the type itself so we can make them smarter.

This has been done.


What's the difference between base_map,routing_map and sim_map?

I think that the base_map,routing_map and sim_map are different layers of the map, what kind of objects belongs to base_map or others? I glance over this three files but does not find the rules to differentiate them, could you give a brief introduction? Thanks a lot!

I added some document to explain the different map formats in this pull-request.
https://github.com/ApolloAuto/apollo/pull/3074/files


Caused by: java.lang.UnsupportedOperationException: Method getStatement in class org.neo4j.jdbc.ResultSet is not yet implemented.

fixed

I am using Apache Drill and Neo4j Database for a project. The database needs to be connected to Drill and I should be able to query the data from Apache Drill.
I have copied and pasted neo4j-driver-4.0.10 into the 3rd party folder for jars. Then, I have created a connection with my Neo4j Database on Apache Drill. Below is the config with the storage name as collisions:
{
  "type": "jdbc",
  "driver": "org.neo4j.jdbc.bolt.BoltDriver",
  "url": "jdbc:neo4j:bolt://localhost:7687",
  "username": "neo4j",
  "password": "neo4j",
  "authMode": "SHARED_USER",
  "writerBatchSize": 10000,
  "enabled": true
}

Then when I try to query from the console with this query:
select * from collisions.crashes limit 10;

I get the error: java.lang.UnsupportedOperationException: Method getStatement in class org.neo4j.jdbc.Neo4jResultSet is not yet implemented.
Warning   UserRemoteException :     PLUGIN ERROR: Failed to load schema for schema collisions

org.apache.drill.common.exceptions.UserRemoteException: PLUGIN ERROR: Failed to load schema for schema collisions

java.lang.UnsupportedOperationException: Method getStatement in class org.neo4j.jdbc.Neo4jResultSet is not yet implemented.

[Error Id: 108138ec-05d7-41af-b7c2-f954798256d8 ]

The data is loaded onto the Neo4j database successfully and I am able to query it from the Neo4j Browser. But why is this error showing up. I couldn't find any other useful question or resource to debug this issue. Is this issue related?


AttributeError: 'function' object has no attribute 'get_json'

AttributeError: 'function' object has no attribute 'get_json'
갑자기 이런 에러가 나네요;;;
저번에 만지고 나서 처음 만지는건데
뭐가 문젤까요...ㅜㅜ

In Flask/wrappers.py the method get_json() is defined as method to the class Request.
However, the same file still contains the old, deprecated method json(). If you have an old version of flask, then a) update or b) use request.json() instead.


Enhancement to current validation when creating Tasks, Sample Data Edits

Codecov Report

Merging #94 (cfaacea) into master (5cf627d) will decrease coverage by 0.16%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #94      +/-   ##
============================================
- Coverage     60.98%   60.82%   -0.17%
  Complexity      417      417
============================================
  Files            90       90
  Lines          1520     1524       +4
  Branches        149      151       +2
============================================
  Hits            927      927
- Misses          547      551       +4
  Partials         46       46

Impacted Files
Coverage Δ

...zpz/logic/parser/AddDeadlineTaskCommandParser.java
0.00% <0.00%> (ø)

...geezpz/logic/parser/AddEventTaskCommandParser.java
0.00% <0.00%> (ø)

...ain/java/manageezpz/model/util/SampleDataUtil.java
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


bitcoin-abc: 0.21.5 -> 0.21.10

Motivation for this change
noticed it was out of date in r-ryantm logs
switch from autotools to cmake, as it was deprecated upstream
Things done

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

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

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

seems like the variant without gui bitcoind-abc doesn't build anymore:
builder for '/nix/store/72a1vsxa4x1nrj9r7phxhl3ykx3l3xay-bitcoind-abc-0.21.10.drv' failed with exit code 1; last 10 log lines:
      qt5-config.cmake

    Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
    to a directory containing one of the above files.  If "Qt5" provides a
    separate development package or SDK, be sure it has been installed.

  -- Configuring incomplete, errors occurred!
  See also "/build/source/build/CMakeFiles/CMakeOutput.log".
  See also "/build/source/build/CMakeFiles/CMakeError.log".

@Lassulus fixed

@GrahamcOfBorg build bitcoind-abc


transport_bio_buffered_free frees BIO_next(bio) just like BIO_free_all.

With the use of BIO_free_all everywhere, there's a double free due to the fact that transport_bio_buffered_free frees BIO_next(bio) just like BIO_free_all.
I'm using valgrind on ubuntu 14.04 to expose this bug, with this ../mcscript, but the same can be seen with sanitize and gcc 7 on 18.04.
#!/bin/bash
exec valgrind \
     --leak-check=full \
     --show-leak-kinds=all \
     --keep-stacktraces=alloc-and-free \
     --track-origins=yes \
     "$@"

[pjb@vm-u1404 localhost:10.0 informatimago-FreeRDP]$ ../mc client/X11/xfreerdp /v:${host} /u:${user} /d:${domain}
==3090== Memcheck, a memory error detector
==3090== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==3090== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==3090== Command: client/X11/xfreerdp /v:w0210312.ac.int /u:BOURGUIGNONPA /d:AC.INT
==3090==
20181113T173248.258  DEBUG	 signal.c:112: freerdp_handle_signals() Registering signal hook...
==3090== Warning: ignored attempt to set SIGKILL handler in sigaction();
==3090==          the SIGKILL signal is uncatchable
==3090== Warning: ignored attempt to set SIGSTOP handler in sigaction();
==3090==          the SIGSTOP signal is uncatchable
20181113T173248.891  DEBUG	 cmdline.c:1219: freerdp_client_detect_command_line() windows: 0/1 posix: -1000/0 compat: -1000/0
20181113T173248.059  DEBUG	 cliprdr_main.c:1298: cliprdr_VirtualChannelEntryEx() VirtualChannelEntryEx
20181113T173248.074  INFO	 cmdline.c:2878: freerdp_client_load_static_channel_addin() loading channelEx cliprdr
20181113T173249.200  DEBUG	 xf_client.c:963: xf_get_x11_button_map() Searching for XInput pointer device
20181113T173249.234  DEBUG	 xf_client.c:1015: xf_get_x11_button_map() Pointer device: 10
20181113T173250.370  DEBUG	 nego.c:1177: nego_set_negotiation_enabled() Enabling security layer negotiation: TRUE
20181113T173250.383  DEBUG	 nego.c:1189: nego_set_restricted_admin_mode_required() Enabling restricted admin mode: FALSE
20181113T173250.386  DEBUG	 nego.c:1211: nego_enable_rdp() Enabling RDP security: TRUE
20181113T173250.387  DEBUG	 nego.c:1223: nego_enable_tls() Enabling TLS security: TRUE
20181113T173250.389  DEBUG	 nego.c:1235: nego_enable_nla() Enabling NLA security: TRUE
20181113T173250.390  DEBUG	 nego.c:1247: nego_enable_ext() Enabling NLA extended security: FALSE
20181113T173250.396  DEBUG	 nego.c:159: nego_connect() state: NEGO_STATE_NLA
20181113T173250.397  DEBUG	 nego.c:427: nego_attempt_nla() Attempting NLA security
20181113T173250.412  DEBUG	 tcp.c:1205: freerdp_tcp_connect() connecting to peer <IP_ADDRESS>
20181113T173250.459  DEBUG	 nego.c:858: nego_send_negotiation_request() RequestedProtocols: 3
20181113T173250.482  ERROR	 transport.c:830: transport_write() BIO_should_retry returned a system error 32: Broken pipe
20181113T173250.489  ERROR	 nego.c:165: nego_connect() Protocol Security Negotiation Failure
20181113T173250.493  ERROR	 freerdp.c:845: freerdp_set_last_error() freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
20181113T173250.494  ERROR	 connection.c:302: rdp_client_connect() Error: protocol security negotiation or connection failure
==3090== Thread 2:
==3090== Invalid read of size 4
==3090==    at 0x9F820C3: BIO_free_all (bio_lib.c:689)
==3090==    by 0x65559BB: transport_disconnect (transport.c:1106)
==3090==    by 0x6501968: nego_transport_disconnect (nego.c:307)
==3090==    by 0x65014AE: nego_disconnect (nego.c:209)
==3090==    by 0x653B905: rdp_client_disconnect (connection.c:351)
==3090==    by 0x652A000: freerdp_disconnect (freerdp.c:506)
==3090==    by 0x6529850: freerdp_connect (freerdp.c:291)
==3090==    by 0x429F32: xf_client_thread (xf_client.c:1474)
==3090==    by 0x6E02695: thread_launcher (thread.c:334)
==3090==    by 0x7892183: start_thread (pthread_create.c:312)
==3090==    by 0x719C03C: clone (clone.S:111)
==3090==  Address 0x19f71d00 is 80 bytes inside a block of size 120 free'd
==3090==    at 0x4C2BDEC: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3090==    by 0xA082F1C: CRYPTO_free (mem.c:312)
==3090==    by 0x9F80FE3: BIO_free (bio_lib.c:138)
==3090==    by 0x6549E8C: transport_bio_buffered_free (tcp.c:637)
==3090==    by 0x9F80FA2: BIO_free (bio_lib.c:132)
==3090==    by 0x9F820E0: BIO_free_all (bio_lib.c:691)
==3090==    by 0x65559BB: transport_disconnect (transport.c:1106)
==3090==    by 0x6501968: nego_transport_disconnect (nego.c:307)
==3090==    by 0x65014AE: nego_disconnect (nego.c:209)
==3090==    by 0x653B905: rdp_client_disconnect (connection.c:351)
==3090==    by 0x652A000: freerdp_disconnect (freerdp.c:506)
==3090==    by 0x6529850: freerdp_connect (freerdp.c:291)
==3090==  Block was alloc'd at
==3090==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3090==    by 0xA082CD0: CRYPTO_malloc (mem.c:222)
==3090==    by 0xA082D03: CRYPTO_zalloc (mem.c:230)
==3090==    by 0x9F80D1A: BIO_new (bio_lib.c:73)
==3090==    by 0x6553AAA: transport_attach (transport.c:229)
==3090==    by 0x65541CB: transport_connect (transport.c:432)
==3090==    by 0x65018E1: nego_tcp_connect (nego.c:274)
==3090==    by 0x6501909: nego_transport_connect (nego.c:289)
==3090==    by 0x6501E6B: nego_attempt_nla (nego.c:429)
==3090==    by 0x6502B1C: nego_send (nego.c:788)
==3090==    by 0x650122C: nego_connect (nego.c:160)
==3090==    by 0x653B6DD: rdp_client_connect (connection.c:297)
==3090==
==3090== Invalid read of size 8
==3090==    at 0x9F820CD: BIO_free_all (bio_lib.c:690)
==3090==    by 0x65559BB: transport_disconnect (transport.c:1106)
==3090==    by 0x6501968: nego_transport_disconnect (nego.c:307)
==3090==    by 0x65014AE: nego_disconnect (nego.c:209)
==3090==    by 0x653B905: rdp_client_disconnect (connection.c:351)
==3090==    by 0x652A000: freerdp_disconnect (freerdp.c:506)
==3090==    by 0x6529850: freerdp_connect (freerdp.c:291)
==3090==    by 0x429F32: xf_client_thread (xf_client.c:1474)
==3090==    by 0x6E02695: thread_launcher (thread.c:334)
==3090==    by 0x7892183: start_thread (pthread_create.c:312)
==3090==    by 0x719C03C: clone (clone.S:111)
==3090==  Address 0x19f71cf0 is 64 bytes inside a block of size 120 free'd
==3090==    at 0x4C2BDEC: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3090==    by 0xA082F1C: CRYPTO_free (mem.c:312)
==3090==    by 0x9F80FE3: BIO_free (bio_lib.c:138)
==3090==    by 0x6549E8C: transport_bio_buffered_free (tcp.c:637)
==3090==    by 0x9F80FA2: BIO_free (bio_lib.c:132)
==3090==    by 0x9F820E0: BIO_free_all (bio_lib.c:691)
==3090==    by 0x65559BB: transport_disconnect (transport.c:1106)
==3090==    by 0x6501968: nego_transport_disconnect (nego.c:307)
==3090==    by 0x65014AE: nego_disconnect (nego.c:209)
==3090==    by 0x653B905: rdp_client_disconnect (connection.c:351)
==3090==    by 0x652A000: freerdp_disconnect (freerdp.c:506)
==3090==    by 0x6529850: freerdp_connect (freerdp.c:291)
==3090==  Block was alloc'd at
==3090==    at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3090==    by 0xA082CD0: CRYPTO_malloc (mem.c:222)
==3090==    by 0xA082D03: CRYPTO_zalloc (mem.c:230)
==3090==    by 0x9F80D1A: BIO_new (bio_lib.c:73)
==3090==    by 0x6553AAA: transport_attach (transport.c:229)
==3090==    by 0x65541CB: transport_connect (transport.c:432)
==3090==    by 0x65018E1: nego_tcp_connect (nego.c:274)
==3090==    by 0x6501909: nego_transport_connect (nego.c:289)
==3090==    by 0x6501E6B: nego_attempt_nla (nego.c:429)
==3090==    by 0x6502B1C: nego_send (nego.c:788)
==3090==    by 0x650122C: nego_connect (nego.c:160)
==3090==    by 0x653B6DD: rdp_client_connect (connection.c:297)
[...]

@informatimago which revision are you using? Current master ca6d1d59196e22dd044add9c0d570b4e5e42f3ff does not have BIO_next in transport_bio_buffered_free and #4964 contains all necessary fixes for gateway related cleanups

Sorry, I don't have merged #4964 in my branch.
I rebased by branch from
commit 76c91ee51ae456b2238a3448761b0b336a46d25f (origin/master, origin/HEAD)
Merge: aecc77cd7 6f2caef77
Author: Martin Fleisz<EMAIL_ADDRESS>Date:   Tue Nov 6 13:51:53 2018 +0100

    Merge pull request #4985 from informatimago/issue-4983

    Fix Issue #4983 : Increased size of buffer to encrypt hash with kerbe…

So we can close this issue, I'll rebase.

Ok, closing then.


Improve performance of find_overlaps

Is it possible to improve performance of find_overlaps method? Now it's much slower than R version. Moreover, it's doesn't scale well with the input size.
>>> geneStart = geneStart.resize(maxDist, "center")
>>> start_point = datetime.datetime.now()
>>> o = geneStart.find_overlaps(peakSet[0:10000], ignore_strand=True)
>>> datetime.datetime.now() - start_point
datetime.timedelta(seconds=364, microseconds=630412)

> start_point <- Sys.time()
> o <- S4Vectors::DataFrame(findOverlaps(resize(geneStart, maxDist, "center"), peakSet[0:10000], ignore.strand = TRUE))
> Sys.time() - start_point
Time difference of 0.1187871 secs

done in #69


Traefik IPWhiteList deprecated - Use IPAllowList Instead

What this PR does / why we need it:
Updates references from the deprecated IPWhiteList Traefik middleware to use IPAllowlist instead, so that we don't get deprecation warnings from Traefik
Which issue (if any) this PR fixes:
Fixes #703
Any other useful info:

I'm not super familiar with the typical github and/or ansible-nas-specific PR process so please let me know if I need to make any changes here, I will monitor this PR and respond to feedback accordingly.
I noticed Issue #703 sitting out there and figured I could make a PR pretty quickly for it

This is a good change, thank you.
It has been implemented in a way that will break people with no warning though - please can you add a check for the *whitelist variables being set in the relevant roles, and throw an error if so? You'll find equivalent checks for variables in Drone role, if you need something to use as a reference.

Thanks for the Drone role example, I hope I've followed it as you expected. I set default values in the *whitelist variables of "deprecated" and threw the builtin.fail if the setting had been changed.

That makes much more sense!

Awesome, thank you! 👍


Made few improvements

I've made few improvements based on your code.
Pull it if you want. I want to improve original pod, but looks like @hackiftekhar doesn't want to.

Thank you very much for this PR! I'm about to embark on a three month backpacking trip tomorrow. Not sure when and if I'll be able to look into this again - depends on my mood and the wi-fi ;-)

Great. Let me know if you'll made some changes. I would like to use improvements too.

Hey, sorry for the delay. I got around to take a closer look at the library and your PR. Thank you very much for your work, I highly appreciate it! However I won't be able to merge your PR due to the recent refactorings I made and the open issues (see comments to commits). However I'll include your improvements manually. Please feedback what your think on the commits on my master branch.

Thank you very much again for all your work! In the end I decided agains merging your PR, but incorporated all your features nevertheless. I hope you can work with it this way as well. Any feedback highly appreciated! So let me know what you think, if you've got the time.


Revert "Fix URLs for list-all"

This reverts commit 40d4d7a1e346b294559212c07f8b173f0d851dbc.
Tha fix seems to no longer be needed.

I've verified list-all which means the archives are available so install should work as well.
I don't thing the current URL is a mirror but rather the actual server hosting the files. The URL I've set there in my previous fix seems to be some sort of a reverse proxy, if you go there now you see all the links on the page send you back to the "mirror" server.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:44: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description
ERROR: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:44: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_cexkjwf2ke/clone/recipe/meta.yaml:44: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description
ERROR: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:44: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:44: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_5cl9ma07rp/clone/recipe/meta.yaml:44: missing_dev_url: The recipe is missing a dev_url
Errors were found


Predis setTimeout ?

Hello
Excuse me, please ，Predis supports setTimeout

yes

Just create the client using connection parameters such as timeout (for the connect() operation) and/or read_write_timeout (for the timeout of read and write operations over the network) with values expressed in seconds.

@nrk referring to this:
https://github.com/phpredis/phpredis#expire-settimeout-pexpire

Found #403 but it doesn't seem to explain how to use it with predis?

The function is setex
 * @method int    setex($key, $seconds, $value)


Delete Event User Story

Completed work on edit/delete view, and finished the delete event use case.
note, there are currently imports on entities in editDeleteView, however, these are only used in the main function purely used to visualize and test the view for the interim. These imports will be deleted at finalization, to abide by CA.
further note, since we dont have a main class we can't use cardlayout for managing transitions between views yet, so that logic needs to be implemented still, but most of the logic is there already.

To fix external clean architecture issues:

a) rename data_access Schedule into InMemoryDataAccessObject
b) delete data package
c) write data access interface for: delete, edit, chatbot conflicts
d) merge chris dao branch with data access branch to get the json dao (inmemory, json dao are written)

To fix chatbot event conflict view model:
a) update message to reflect separation of time estimation and event conflict chatbots
b) update ui to include access to time estimation
c) merge with chris-branch-dao-v2 for time estimation usecase

delete event conflict output data, its unused


lightbox: On .player-container direct click, hide lightbox.

When a user clicks on the .player-container node and the click
target is actually that (and not the YT video iFrame within), then
hide the lightbox – they likely mean to exit out of the lightbox.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!


🐛 BUG: --experimental-local fails / Error: npx-import / No matching version found for<EMAIL_ADDRESS>

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
2.14.0
What operating system are you using?
Mac
Describe the Bug
npx wrangler init repro-workers-sdk-3007 -y
cd repro-workers-sdk-3007
npx wrangler dev --experimental-local

Expected result: dev server starts
Actual result:
 ⛅ wrangler 2.14.0
--------------------
[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p<EMAIL_ADDRESS>✘ [ERROR] local worker: Error: npx-import failed for @miniflare/tre with message:

      Command failed with exit code 1: npx --prefer-offline -y -p<EMAIL_ADDRESS>  printenv PATH
  npm ERR! code ETARGET
  npm ERR! notarget No matching version found for<EMAIL_ADDRESS>  npm ERR! notarget In most cases you or one of your dependencies are requesting
  npm ERR! notarget a package version that doesn't exist.

  npm ERR!      /Users/igor/.npm/_logs/2023-04-08T03_54_06_893Z-debug-0.log

  You should install @miniflare/tre locally:
      npm install --save-dev<EMAIL_ADDRESS>

      at npxImport
  (/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:130140:13)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async getMiniflare
  (/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:132187:31)
      at async buildMiniflare3Logger
  (/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:132098:38)
      at async startLocalWorker
  (/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:131707:21)

If I try to workaround this with:
npm install -D<EMAIL_ADDRESS>
I get the following unexpected error:
$ npm install -D<EMAIL_ADDRESS>npm ERR! code 1
npm ERR! path /Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c prebuild-install || node-gyp rebuild --release
npm ERR! prebuild-install warn install No prebuilt binaries found (target=18.15.0 runtime=node arch=arm64 libc= platform=darwin)
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| darwin | arm64
npm ERR! gyp info find Python using Python version 3.9.10 found at<EMAIL_ADDRESS>npm ERR! gyp http GET https://nodejs.org/download/release/v18.15.0/node-v18.15.0-headers.tar.gz
npm ERR! gyp http 200 https://nodejs.org/download/release/v18.15.0/node-v18.15.0-headers.tar.gz
npm ERR! gyp http GET https://nodejs.org/download/release/v18.15.0/SHASUMS256.txt
npm ERR! gyp http 200 https://nodejs.org/download/release/v18.15.0/SHASUMS256.txt
npm ERR! gyp info spawn<EMAIL_ADDRESS>npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/Users/igor/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/better-sqlite3/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/igor/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/igor/Library/Caches/node-gyp/18.15.0/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/Users/igor/Library/Caches/node-gyp/18.15.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/Users/igor/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/Users/igor/Library/Caches/node-gyp/18.15.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/better-sqlite3',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
npm ERR!
npm ERR! No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
npm ERR!
npm ERR! No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
npm ERR!
npm ERR! gyp info spawn make
npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/Users/igor/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Darwin 22.2.0
npm ERR! gyp ERR! command "/Users/igor/.nvm/versions/node/v18.15.0/bin/node" "/Users/igor/.nvm/versions/node/v18.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
npm ERR! gyp ERR! cwd /Users/igor/Development/workers-tests/repro-workers-sdk-3007/node_modules/better-sqlite3
npm ERR! gyp ERR! node -v v18.15.0
npm ERR! gyp ERR! node-gyp -v v9.3.1
npm ERR! gyp ERR! not ok

npm ERR!      /Users/igor/.npm/_logs/2023-04-08T03_56_19_643Z-debug-0.log

I have the latest macos (13.3.1) and command line tools installed:
$ xcode-select --install
xcode-select: error: command line tools are already installed, use "Software Update" in System Settings to install updates

I've retested this and it still fails with 2.15.1:
$ npx wrangler dev --experimental-local

 ⛅ wrangler 2.15.1
--------------------
[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p<EMAIL_ADDRESS>✘ [ERROR] local worker: Error: npx-import failed for @miniflare/tre with message:

      Command failed with exit code 1: npx --prefer-offline -y -p
<EMAIL_ADDRESS>printenv PATH
  npm ERR! code ETARGET
  npm ERR! notarget No matching version found for<EMAIL_ADDRESS>  npm ERR! notarget In most cases you or one of your dependencies are requesting
  npm ERR! notarget a package version that doesn't exist.

  npm ERR!      /Users/iminar/.npm/_logs/2023-04-14T12_18_07_775Z-debug-0.log

  You should install @miniflare/tre locally:
      npm install --save-dev<EMAIL_ADDRESS>

      at npxImport
  (/Users/iminar/Development/workers-repros/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:130143:13)
      at process.processTicksAndRejections
  (node:internal/process/task_queues:95:5)
      at async getMiniflare3
  (/Users/iminar/Development/workers-repros/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:132190:31)
      at async buildMiniflare3Logger
  (/Users/iminar/Development/workers-repros/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:132101:38)
      at async startLocalWorker
  (/Users/iminar/Development/workers-repros/repro-workers-sdk-3007/node_modules/wrangler/wrangler-dist/cli.js:131710:21)

I then deleted cached npm stuff:
# ouch
rm -rf node_modules
# and yikes...
rm -rf ~/.npm/

And tried again:
$ npx wrangler dev --experimental-local

Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
 ⛅ wrangler 2.15.1
--------------------
[NPXI] @miniflare/tre not available locally. Attempting to use npx to install temporarily.
[NPXI] Installing... (npx --prefer-offline -y -p<EMAIL_ADDRESS>[NPXI] Installed into /Users/iminar/.npm/_npx/6d0cb0fae3c8833d/node_modules.
[NPXI] To skip this step in future, run: npm install --save-dev<EMAIL_ADDRESS>[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-04-04",
but you've requested "2023-04-14". Falling back to "2023-04-04"...
workerd/server/server.c++:2302: info: Inspector is listening
⎔ Reloading experimental local server.
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-04-04",
but you've requested "2023-04-14". Falling back to "2023-04-04"...
workerd/server/server.c++:2302: info: Inspector is listening
[mf:inf] Updated and ready on http://<IP_ADDRESS>:8787/

And this time it worked....
This suggests to me that npx can get into a bad state if a native package fails a post install build step which then likely requires the npx cache to be blown away for the system to get back into a good state.
How can we help wrangler devs from falling into this trap? Is this an npx-import issue or npx bug?

Closing since wrangler@3 no longer uses npx-import for installing workerd


Thermostat finder

Find master/slaves in locations and demote slaves - also small radiator valves change
Accompanying change for zone_thermo_improve on both repo's to include radiator valves as thermostats but not give them thermostat if a zone_thermostat or thermostat is present

Lots of debugging and comments still present


Introduce mocking framework and increase coverage

This change introduces three common Golang patterns to the SonyFlake project test framework:

types: this will allow fine-tuned control over imported types by defining how they will be used, project-wide

mock: this allows the generation of mock constructors, which lends itself to testing any individual path in a function by
"injecting" a mock object which matches the expected type

array-based-testing: privateIPv4 and lower16BitPrivateIP were lacking tests for their error paths,
but using types and mocks, I was able add two array-based tests that cover all test cases for these methods

This change also increases test coverage to 💯, while adding no additional time for testing ⌛ .
This is a really cool project, and I'd be happy to contribute more!

I realized I didn't notify anyone about this PR, so I apologize for the bother, and no rush!
@yuokada @osamingo

@BradleyBoutcher Sorry for late reply.
I'm just a contributor. I don't have any responsibility or permission for this repository.

@BradleyBoutcher Sorry for late reply.
I'm just a contributor. I don't have any responsibility or permission for this repository.

No worries! Thank you for the response!

No worries! Thank you for the response!

Thank you for your PR.


Keyboard C++ FFI

I have tried the read-keys example and it is working great on my QEMU vm.
I am trying to do something similar in C++ but cannot seem to find any keyboard classes in either of the generated headers.
Is this something planned for in the future?

Yes! We have been hard at work on the 0.2 version of the library, which should fix the shortcomings of the C/C++ FFI. Everything is yet to be set in stone, but the next branch should be able to have some (although not very ergonomic) way to access keyboard:
https://github.com/memflow/memflow/blob/next/memflow/examples/keyboard.rs
https://github.com/memflow/memflow/blob/next/memflow-ffi/memflow.h
However, it's not yet set in stone, I would say a couple of months before 0.2 is out with a clean C++ wrapper.

If you are eager to try the next branch, I would check the keyboard vtable on OsLayerFunctionTable (which in itself is stored on OsInstance that can be created through inventory_create_os)

Thank you for the fast reply, I'll be sure to check the next branch, if I encounter any issues Ill make sure to let know, and thanks for the great library.

No worries! And thank you :)
The main difference in 0.2 is that win32 is now a plugin like qemu-procfs. It will be necessary to put it in the same path as the connectors (and the qemu connector will need recompiling on the next branch too).


XHR for BMO fails in Opera

In https://github.com/jdm/bugsahoy/issues/12, we've noticed that bz.js triggers a security violation in Opera 11.51 when trying to perform a search. I have no idea whether this is affects other versions or not, but it's something to be aware of. I'm presuming at this point that it's not the fault of bz.js, considering the success rate in other browsers.

I don't know off the top of my head why this would happen, but thanks for reporting!

Could this be that opera pre-flights CORS slightly differently, in a way that the bzapi doensn't support?
If so, the current version doesn't use pre-flights no more for GET requests, jdm, can you check if that reproduces with current master?

How convenient, your recent change fixed this. Thanks!

Sounds like a bug in either opera or our bzapi install then. Mind starting with filing a bug on bzapi?

Oops, I lied. I didn't even get to test bz.js, since loading the script triggered an error.


Allow developing SwiftPM without the bootstrap script

This will allow building and using the swiftpm binary that was built
using swiftpm. The catch is that only one of the runtime
PackageDescription library will be used since we can't build both
runtimes together. This also removes the additional tool and runtime lookup behavior
behind SWIFT_TOOLCHAIN define to minimize chances of bugs when building
SwiftPM for Swift toolchains.
rdar://problem/56865514

@swift-ci smoke test Linux

@swift-ci smoke test macOS

@swift-ci smoke test MaCoS self hosted

@swift-ci smoke test MaCoS self hosted

@swift-ci smoke test macOS self hosted

@swift-ci smoke test macOS self hosted

@swift-ci test self hosted

@swift-ci smoke test self hosted

@swift-ci smoke test self hosted

@swift-ci smoke test self hosted

@swift-ci smoke test

/cc @hartbit

@benlangmuir Do you know if this is intermittent or did I actually break sourcekit-lsp?
20:39:10 Test Case '-[SourceKitTests.SwiftPMIntegrationTests testSwiftPMIntegration]' started.
20:39:10 <unknown>:0: error: -[SourceKitTests.SwiftPMIntegrationTests testSwiftPMIntegration] : failed: caught error: The operation couldn’t be completed. (Build.BuildPlan.Error error 1.)
20:39:10 Test Case '-[SourceKitTests.SwiftPMIntegrationTests testSwiftPMIntegration]' failed (0.081 seconds).
20:39:10 Test Suite 'SwiftPMIntegrationTests' failed at 2019-12-17 20:39:10.497.
20:39:10 	 Executed 1 test, with 1 failure (1 unexpected) in 0.081 (0.081) seconds
20:39:10 Test Suite 'SwiftPMWorkspaceTests' started at 2019-12-17 20:39:10.497
20:39:10 Test Case '-[SKSwiftPMWorkspaceTests.SwiftPMWorkspaceTests testBasicCXXArgs]' started.
20:39:10 Fatal error: 'try!' expression unexpectedly raised an error: the package does not contain a buildable target: file /Users/buildnode/jenkins/workspace/swift-package-manager-PR-osx-smoke-test/sourcekit-lsp/Tests/SKSwiftPMWorkspaceTests/SwiftPMWorkspaceTests.swift, line 327
20:39:10 E[20:39:10.564] Transport error: Input/output error
20:39:10 E[20:39:10.564] Transport error: Input/output error
20:39:10 E[20:39:10.564] Transport error: Input/output error
20:39:10 E[20:39:10.564] Transport error: Input/output error
20:39:10 Exited with signal code 4

@swift-ci smoke test macOS

@swift-ci smoke test self hosted

@swift-ci smoke test self hosted

@swift-ci smoke test macOS self hosted

@swift-ci smoke test

@swift-ci smoke test macOS


dde-daemon: init at <IP_ADDRESS>

Motivation for this change

dde-daemon: init at <IP_ADDRESS> (daemon for handling Deepin Desktop Environment session settings)
dbus-factory: fix instalation directory for source
go-dbus-factory: fix instalation directory for source
go-lib: fix instalation directory for source
go-lib: <IP_ADDRESS> -> <IP_ADDRESS>

Things done

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

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

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

@GrahamcOfBorg eval

@GrahamcOfBorg build dbus-factory go-dbus-factory go-lib dde-daemon

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: dbus-factory, go-dbus-factory, go-lib, dde-daemon
Partial log (click to expand)

Cannot nix-instantiate `go-dbus-factory' because:
error: attribute 'go-dbus-factory' in selection path 'go-dbus-factory' not found

Cannot nix-instantiate `go-lib' because:
error: attribute 'go-lib' in selection path 'go-lib' not found

Cannot nix-instantiate `dde-daemon' because:
error: attribute 'dde-daemon' in selection path 'dde-daemon' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: dbus-factory, go-dbus-factory, go-lib, dde-daemon
Partial log (click to expand)

Cannot nix-instantiate `go-dbus-factory' because:
error: attribute 'go-dbus-factory' in selection path 'go-dbus-factory' not found

Cannot nix-instantiate `go-lib' because:
error: attribute 'go-lib' in selection path 'go-lib' not found

Cannot nix-instantiate `dde-daemon' because:
error: attribute 'dde-daemon' in selection path 'dde-daemon' not found

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: dbus-factory, go-dbus-factory, go-lib, dde-daemon
Partial log (click to expand)

Cannot nix-instantiate `go-dbus-factory' because:
error: attribute 'go-dbus-factory' in selection path 'go-dbus-factory' not found

Cannot nix-instantiate `go-lib' because:
error: attribute 'go-lib' in selection path 'go-lib' not found

Cannot nix-instantiate `dde-daemon' because:
error: attribute 'dde-daemon' in selection path 'dde-daemon' not found

@GrahamcOfBorg build deepin.dbus-factory deepin.go-dbus-factory deepin.go-lib deepin.dde-daemon

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: deepin.dbus-factory, deepin.go-dbus-factory, deepin.go-lib, deepin.dde-daemon
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: deepin.dbus-factory, deepin.go-dbus-factory, deepin.go-lib, deepin.dde-daemon
Partial log (click to expand)
shrinking /nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>/lib/deepin-daemon/dde-authority
shrinking /nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>/lib/deepin-daemon/backlight_helper
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>/lib
patching script interpreter paths in /nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>
checking for references to /build in /nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>...
/nix/store/3m15m24rbv0idx37cv3hj0il1ki3d28w-dbus-factory-3.1.17
/nix/store/nwqhsc74z0jippgizy3mrmlifps39xxy-go-dbus-factory-<IP_ADDRESS>
/nix/store/w7n44n7rpddcy45fg6mslk8vvh6s947z-go-lib-<IP_ADDRESS>
/nix/store/ihq6l9grxqyx71bv1m2xdbrjidq8ll98-dde-daemon-<IP_ADDRESS>

Success on x86_64-linux (full log)
Attempted: deepin.dbus-factory, deepin.go-dbus-factory, deepin.go-lib, deepin.dde-daemon
Partial log (click to expand)
shrinking /nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>/lib/deepin-daemon/dde-authority
shrinking /nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>/lib/deepin-daemon/backlight_helper
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>/lib
patching script interpreter paths in /nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>
checking for references to /build in /nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>...
/nix/store/2674idhvflrssc6hkayl3gdagnzagxpw-dbus-factory-3.1.17
/nix/store/f5zjf533ap2khh18s8ih3bii1nw5q5b7-go-dbus-factory-<IP_ADDRESS>
/nix/store/qv12xrw19k9q1303irdjpv6mlqgir32k-go-lib-<IP_ADDRESS>
/nix/store/3qsxqiz39kwd89g918csbrrxfmy6y53h-dde-daemon-<IP_ADDRESS>


Hosting PDFs

I'm trying to host and/or embed some PDFs in my website. In my obsidian interface the pdfs show up nice but when I deploy locally, the links to the PDF page show up as 404 not found. Is there a common method to have links to your pdfs show up?

Additionally, I am having an issue where some image attachments embedded in the page won't load even though they do show up in Obsidian.

Did you see the PDF available in the final artifacts of the build?
all of the static file (PDF) should include in the final build directory. For example, for my site this note the PDF is resolved correctly based on this line

Thanks, I had added something to my ignorePatterns configuration which was hiding non-markdown files.


packages: perspective and bech32

split out a set of functions in types

tools for manipulating transaction views and perspectives go into 'perspective'
tools for manipulating bech32 strings go into 'bech32'

and configure them to build well
this kinda grew out of some other work i was doing in custody rpc

okay, minimized PR to reorganization, removed all behavior changes. so bech32 util behavior is a mess and definitely seems wrong in places but i can make that a separate PR

#778 for bech32 behavior


Would it be possible to install linuxdeployqt as well ?

Currently it has macdeployqt and windeployqt, but not linuxdeployqt (for AppImage)
https://github.com/probonopd/linuxdeployqt
curl -LO https://github.com/probonopd/linuxdeployqt/releases/download/continuous/linuxdeployqt-continuous-x86_64.AppImage

sudo install linuxdeployqt-continuous-x86_64.AppImage /usr/local/bin/linuxdeployqt

linuxdeployqt isn't an official Qt project AFAIK, so I am not sure it would make sense to install this automatically

As a workaround I added it as an extra step, after running the qt-install-action

Turns out that the binary requires fuse and ubuntu:20.04, so I think it will need a special runner set up anyway.

Hi.

Turns out that the binary requires fuse and ubuntu:20.04

Is there no way to run linuxdeployqt on GitHub Actions Runners? IIRC it works on Oct 15, 2021.

You can follow the experiments here: https://github.com/kubernetes-sigs/minikube-gui/pull/95#issuecomment-1715616461
But that is the supported upstream binary: linuxdeployqt-continuous-x86_64.AppImage

It should not be necessary with fuse / squashfuse here, it is enough with unsquashfs...
Also allows for running the program in a container in the future, and not just in a VM.


dogfooding WASM product might be different in release phase

https://github.com/kachick/dprint-plugin-kdl/blob/aa90fe32085863beda8530b25ca22b38b3a1429a/dprint-dogfooding.json#L6

Resolved in https://github.com/kachick/dprint-plugin-kdl/pull/83


Add GeneratorExt::partition

This should be analogous to Iterator::partition.

Depends on  #10

#10 did not add an Extend like trait, but rather an IntoGenerator trait. partition requires Extend instead.


docker-compose: upgrade Elasticsearch 6.2->6.6

docker.elastic.co/elasticsearch/elasticsearch-oss:6.2.4 -> docker.elastic.co/elasticsearch/elasticsearch-oss:6.6.0

Closed by #119


random chance

My friends like this mod, but according to them, it should be a random chance to lockdown, maybe a warning when you pull the lever to start that tells you that this building has a lockdown feature.

Interesting idea I ll let you know when I implement this feature, It could be as follow in the config file
RandomChanceToLockdown: 1 (0 to 1)
eg. 0.5 to be a 50% chance that each planet can have a lockdown featrure
And it is annouced at the start of the level right ?

Thanks for the quick response.
Yes, I was thinking exactly like that, and it would be cool if during the announcement it told you the time when it locks and the time when it unlocks.

I also think this would be a great feature to have. Would be nice for adding some variety to a modpack without changing the way you have to play the game all of the time.

Yeah, it would be nice, but I don't think that the creator is working on this anymore.


How to compare the result between proposed model and BPG,JPEG?

Hi, Justn-Tan:
I have 3 questions. Hope for your reply.

Where i read the paper, I found the paper compare the result(visual result with same bpp ) between proposed model and BPG,JPEG. Do you know how to get the arbitrary bpp with BPG and JPEG? And how to realize the PSNR and MS-SSIM measures?
2. In your code, "trainer.py" L50 "test_handle = sess.run(gan.test_iterator.string_handle())" and  L62 "sess.run(gan.test_iterator.initializer, feed_dict=feed_dict_test_init)". Maybe test hander is reduntant in train process? I did not find the process of the test image.
3. In your code, First update generator and then update discriminator. And i found in "https://github.com/NVIDIA/pix2pixHD/blob/master/train.py" paper《High-Resolution Image Synthesis and Semantic Manipulation with Conditional GANs》they also apply this update strategy. But it seems first update discriminator and then update generator is more reasonable. So what is the difference between these two strategies? or these two strategies can get same training result?
These are my questions, looking forward to your reply.
Thanks very much for sharing your code.  I have spent much time reading your code and gotten a lot of benefits from your code.

I'm not sure how they compressed their images to a given level with the BPG format unfortunately. The measures you refer to are only applicable in the case where they have the semantic label maps and are implementing selective compression.
Yes, you are right that the test handler is redundant for now, I intend to compute statistics over a test batch in the future.
I would assume that either method would yield very similar results, one interesting direction might be pretraining the generator for a certain number of iterations before reverting to the alternating update schedule.


[WIP] stop ignoring Wmissing-field-initializers and fix

I was also looking at clang-tidy's cppcoreguidelines-pro-type-member-init, but it will require us to initialize absolutely everything.
https://clang.llvm.org/extra/clang-tidy/checks/cppcoreguidelines-pro-type-member-init.html

Comments addressed and rebased on master.


Fix status command in FreeBSD init script

If the init script is called with status, the rc.subr(8) routines check if
the first argument associated with the pid in the pidfile is equal to
procname. By default, procname is equal to the value of command. In our
case, command contains a space (i.e. has multiple arguments), so procname
can never be equal to the first argument of the command associated with the
pid.
Set procname to the first argument of command to fix the status command
of the init script.

Thank you!


Run h2load in CI

Done in https://github.com/bearcove/loona/pull/220 — it doesn't take syscalls into account, only time spent in user code, but.. I don't know, it's something?


Pandas dataframe type not recognized

The Pandas  dataframe type is not being recognized, which results in code completion and hints to not work  with dataframes. Below is an example:

Here is an example of the same code working as expected in VS code:

I have tried both the intellisense database, as well as the experimental intellisense feature.
Thanks

We dup these against issue #3046 to keep track of them.
Our next release will include support for type stubs, so when pandas has type stub files available you will be able to use those. (Currently there is not enough information in their source code for us to automatically infer return types, and we have chosen type stubs as the format to manually specify them.)

Thanks for reaching out and providing some background. I shared the information with some of my coworkers who do Python development, so now we are looking forward to the next release!


Access to gpio

Is there any reason, why all gpio pins are blocked, while using the pico display?
is there any way to access at least two of them, for external sensors?

Startet conunting with pin 1 instead pin 0.
At least pin 0 and pin 1 now working.


docs: automated demo deployment

This PR

adds new section to the getting started guide to automatically deploy and port forward to the demo application

Related Issues

https://github.com/open-feature/open-feature-operator/issues/106
Notes

Follow-up Tasks

How to test

Codecov Report

Merging #310 (4efa95d) into main (99edfeb) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #310   +/-   ##
=======================================
  Coverage   54.99%   54.99%
=======================================
  Files           4        4
  Lines         511      511
=======================================
  Hits          281      281
  Misses        209      209
  Partials       21       21

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Failure to compile

I'm using lapin (with feature rustls-native-certs) which in turn uses this crate and I'm running into the following build error now:
error[E0599]: no method named `decrypt_padded_vec` found for struct `Decryptor` in the current scope
   --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/p12-0.6.2/src/lib.rs:660:9
    |
660 |     rc2.decrypt_padded_vec::<Pkcs7>(data).ok()
    |         ^^^^^^^^^^^^^^^^^^ method not found in `Decryptor<Rc2>`

error[E0599]: no method named `decrypt_padded_vec` found for struct `Decryptor` in the current scope
   --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/p12-0.6.2/src/lib.rs:700:10
    |
700 |     tdes.decrypt_padded_vec::<Pkcs7>(data).ok()
    |          ^^^^^^^^^^^^^^^^^^ method not found in `Decryptor<TdesEde3>`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `p12` due to 2 previous errors

I open this issue here because this seems to be the end of the line:
p12 v0.6.2
└── tcp-stream v0.24.3
    └── amq-protocol-tcp v7.0.0
        └── amq-protocol v7.0.0
            └── lapin v2.0.1
                └── myapp

Not sure this is the right place but maybe you could give me a hint.

You can workaround that by pinning p12 to version 0.6.1
Will publish 0.6.3 with the fix holly

Fixed in p12 0.6.3


checking empty spece on grid

Hi,
Is it any easy way to check if cell on greed is empty or occupied by grid element ?
For example if I have
[    x=0  y=0  occupied  ][   x=4 y=0  empty  ][  x=5 y=0  empty  ][   occupied ]
[         occupied            ] [         occupied     ][        empty          ][   occupied ]
[         occupied            ] [         occupied     ][        empty          ][   occupied ]
how I can find out that 4,0 is empty  and  from 5-0 to 5-2 is also empty space ?
Thanks,

Hi,
I've added is_area_empty API method https://github.com/troolee/gridstack.js#is_area_emptyx-y-width-height


631- add integration and unit tests [WIP]

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #631
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist:

[ ] PR title matches follow: (Feature|Bug|Chore) Task Name
[ ] My code follows the style guidelines of this project
[ ] I have followed all the instructions described in the initial task (check Definitions of Done)
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have added reference to a related issue in the repository
[ ] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request ( for frontend tasks)
[ ] I have pasted a gif showing the feature.
[ ] @mentions of the person or team responsible for reviewing proposed changes

@Maasdamind doesnt pass travis-ci build... complains about some missing '}'
check your package-lock and packahge.json


Feature: add language japanese

What is the feature?
Add Japanese version to homepage
Why is this feature needed?
for internationalization
Any additional comments?
No response
Confirmations

[X] I have read the Code of Conduct
[X] I have read the Issue Reporting Guidelines
[X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[X] I know that any inappropriate content may cause the maintainer to take action base on the Code of Conduct
[ ] This feature request is open because to fix a bug/issue

Sure, but we will do this later, you can open a Pull Request if you want to do it yourself too.


Add pre-defined macro __riscv_p for P extension

I believe this change is straightforward and no controversy since https://github.com/riscv/riscv-p-spec is there for long time.

I'm not a big fan of merging this change, because the P extension is not frozen.

Oh, apology for the rush merge, but I think that's still useful for implementing compiler support for those non-ratified extensions, what do you think if we add few more word to mark that is non-ratified / non-frozen?

I would prefer to keep changes for unfrozen extensions as PRs and tag them with "unfrozen extension".
Once the extension is frozen, we can merge the change. However, I don't want to overtake the extension ratification process.
My plan is to create a proposal for a merge policy, that we can discuss.

My plan is to create a proposal for a merge policy, that we can discuss.

OK, thanks!

Hi @kito-cheng,
Do you plan to revert these changes?
I will create a new PR the same as this. It seems merged PR unable to be reopened.


error: the trait bound <Inner>: Deref is not satisfied

When I do #[derive(Deref)] struct Col(RGB<f32>); why am I getting

error: the trait bound rgb::RGB<f32>: Deref is not satisfied ?

Using this RGB type: https://crates.io/crates/rgb

Can you provide a script that I can use to reproduce the issue? I was unable to reproduce using the latest versions of derive_deref and rgb using the following script:
#[macro_use]
extern crate derive_deref;
extern crate rgb;

#[derive(Deref)]
pub struct Col(rgb::RGB<f32>);

It's a huge project..
Btw, it actually says lazy_static::Deref, any idea why?

error: the trait bound rgb::RGB<f32>: lazy_static::Deref is not satisfied
error: the trait lazy_static::Deref is not implemented for rgb::RGB<f32>

#[derive(Deref, Copy, Clone)]
pub struct Col(pub RGB<f32>);

Huh. That's... Odd. I legitimately have no clue where that could be coming from. This derive is explicitly always qualifying as ::std::ops::Deref, and there are no bound added to that impl (other than any where clause that is on the actual struct).
Maybe try running it through cargo expand, and see if using the generated impl gives a more specific error?

            pub struct Col(pub RGB<f32>);
            impl ::std::ops::Deref for Col {
                type
                Target
                =
                <RGB<f32> as ::std::ops::Deref>::Target;
                #[inline]
                fn deref(&self) -> &Self::Target {
                    <RGB<f32> as ::std::ops::Deref>::deref(&self.0)
                }
            }

Hm, no idea why it confuses it with lazy_static::Deref..

Btw, it is working on another type in the same project!
#[derive(Deref, Clone)]
pub struct Voices(pub Vec<MidiPitch>);


Camera Hight locked

Hallo there. I'm relatively new to Godot4 and I hope I can find help for my noob problems here.
The FPSTemplate is really greate and it helped me a lot learning how to get use of the Nodes in Godot.
But I'm facing a problem at the moment. For my LevelDesign, I need to move the Camera of the FPSInstance a bit, but when I save the scene, the camer jumps to its original position.
I tried to find the place where the lock could have been located but I cannot find it.
Can you pls help me out with it?
Thanks a lot for help and for the great template.
Greetings froom Germany :)

Right, I got so caught up in other things that I never got around to this issue. I even added a comment in the code that was because of this. I think the solution is to change the RESET animations on all of the AnimationPlayer nodes (CrouchAnimation, HeadbobAnimation, JumpAnimation).

For anyone who has this issue, modify the Head's position value in the CrouchAnimation's RESET animation


Adding documentation for v2

What does this PR do ?
Add documentation and guides for the version 2 of KDM

This documentation is outdated


Support for Windows 2019?

I know this question has been asked, and the answer was that there are no plans to support this product for Windows 2019.
This sounds to me as if this product will not be maintained in the near future, I mean we have Exchange 2019 out for a year now and is RECOMMENDING to use Windows 2019.
If you try to integrate Office Online Server with Exchange 2019 on Windows 2019 you run into TLS 1.2 issues and need to apply workarounds, some of this would be resolved by default by supporting Windows 2019.
What is the reason for not supporting Windows 2019 other than "no plans"? The future looks bleak for Office Online Server if the stance is that it will not be supported.

Office Online Server is under the Modern Lifecycle Policy and we will continue to support our release. We cannot share roadmap or future plans at the moment.


Add custom lock prefix support

You can change default lock prefix "/_locks", if you etcd path conflict other apps.

Coverage decreased (-0.2%) to 87.963% when pulling d2f3e09e0fd7b4a4629eb43a3f9afae256e451eb on mingqing:custom-lock-prefix into f9edc6f5a87c076ab4776d1cec575a38fa848fb6 on jplana:master.

@mingqing thanks this is a good patch; merging.


Use a single CentralDogma watcher per file

Fixes the following issues
Race condition in initialization (rare)
java.lang.NullPointerException: null
	at com.linecorp.decaton.centraldogma.CentralDogmaPropertySupplier.getProperty(CentralDogmaPropertySupplier.java:133)
	at com.linecorp.decaton.processor.runtime.internal.AbstractDecatonProperties$Builder.setBySupplier(AbstractDecatonProperties.java:55)
	at com.linecorp.decaton.processor.runtime.SubscriptionBuilder.properties(SubscriptionBuilder.java:103)

It happens because CD watchers don't notify synchronously and instead add a task to watchScheduler. So awaiting initial value does not guarantee that all watchers have been run.
Watchers multiplication
Each watcher polls CD, so with many processors / dynamic properties that's a lot of unnecessary load.
Note that child watchers do not react when a part of the file they are not watching is updated. https://github.com/line/centraldogma/blob/master/client/java/src/main/java/com/linecorp/centraldogma/client/TransformingWatcher.java#L92

@ocadaruma , PTAL 🙇🏻

CD's childWatcher

I heard someone awesome implemented it


Setup Github CI pipeline when branch is merged to main

[x] Any branch when merged to main, it should trigger tests run
[ ] Store the logs, may be Google Drive

https://docs.github.com/en/actions/guides/about-continuous-integration
https://lab.github.com/githubtraining/devops-with-github-actions

https://lab.github.com/githubtraining/github-actions:-hello-world
https://lab.github.com/githubtraining/github-actions:-continuous-integration
Custom workflow
Now that we've learned how to quickly set up CI, let's try a more realistic use case.
Our fictional team has a custom workflow that goes beyond the template we've used so far. We would like the following features:

Test against multiple targets so that we know if our supported operating systems and Node.js versions are working

Dedicated test job so that we can separate out build from test details

Access to build artifacts so that we can deploy them to a target environment

Branch protections so that the main branch can't be deleted or inadvertently broken

Required reviews so that any pull requests are double checked by teammates

Obvious approvals so we can merge quickly and potentially automate merges and deployments
Step 7: Create a custom GitHub Actions workflow
Can GitHub Actions support this workflow? Let's find out. We'll tackle some of the changes to the existing workflow file first.
:keyboard: Activity: Edit the existing workflow with new build targets

Edit your existing workflow file in a new branch
In that file, target versions 12.x and 14.x of Node, only
Open a new pull request titled Improve CI for your change.

I'll respond when you open the pull request.

The project is deployed at https://pypi.org/project/downloadpdf/

https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python?langId=py#testing-with-pytest-and-pytest-cov


[WIP] Refactor applyUpstreamTLSSettings [DestinationRule]

Grouping SIMPLE and MUTUAL mode together instead of ISTIO_MUTUAL and MUTUAL mode. Results in some code duplication but we get better code readability.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@nschhina: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
5b087831a24e294ce31e36b898fc660c693b21e7
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Are there any tests covering this code refactoring? If not, could you please add one?

Are there any tests covering this code refactoring? If not, could you please add one?

TestApplyUpstreamTLSSettings already covers this refactoring.
Ref: https://github.com/istio/istio/blob/master/pilot/pkg/networking/core/v1alpha3/cluster_test.go#L2187

@nschhina: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
cf7c747d557f2da656b64f3400b2a672aca18f17
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Proposal: Color-picker

Bug, feature request, or proposal:
Do the Angular Material Team have any thoughts about creating a color-picker?
What is the expected behavior?
Let the user give the possibility to enter/select a specific color. I was thinking of something similar as Brianpkelley color-picker
What is the current behavior?
Not implemented yet
Is there anything else we should know?
At the moment the Brianpkelley color-picker is a bit outdated for AngularJS and not usable in Angular (2). At the other hand it was very user friendly as we could enter the color-code (hex,rgb,hsl) or select it from the different palettes.

I want this

I want this, too.
I find another material design colorpicker, but it can't change the theme color.

very cool!

I have created a another color picker for Angular Material.
https://ng-matero.github.io/extensions/components/colorpicker

We're in the process of cleaning up our issue backlog. I'm going to close this issue since it's unlikely that we're going to implement this component, because:

It's not in the Material Design specification.
input[type="color"] is widely supported now.
mat-form-field supports input[type="color"].
Getting the accessibility right is going to be really difficult.


Vagrant port forwarding should not use port 6000

I tried running a Django app in port 6000, using python manage.py runserver <IP_ADDRESS>:6000. My local browser could not connect to localhost:6000.
However, my terminal could. I could send a curl -I http://localhost:6000 request from host machine to get response back from guest box.
Firefox told me browser is blocking the request because port 6000 is reserved for some other activity.
We need to select some other port for this. Maybe 3000?

This is not a bug really, it is due to the fact that some other virtual machine or something else is using the same port 6000 or even the same localhost port 8080. So the way to circumvent that right now is to manually get rid of all the rest of the VMs. You can do it most properly by using VirtualBox GUI and delete them manually. vagrant global-status will show everything but not quite sometimes, it is prune to errors. You cannot sometime vagrant destroy stuff due to many reasons. So please try to have a look at all your servers locally running and especially VirtualBox.

We should add the feature in our next release to automate port forwarding address to be randomly changed so that it is not blocked at any time, it will figure out all ports being currently used and then assign each newly spawned virtual machine another random port and displays that to the user at the end in the terminal.

Actually, I always run only one VM. I checked this with netstat command as well, and grepped for ':6000'. Nothing was using port 6000, other than what I intended.
The point is, to an end-user, it would appear our box does not do port forwarding.
Here's a solution for better experience. We use a port on host box randomly, a big number that is unlikely to be used by other running VM's, if any. Maybe something like 12,341.
And we export this $PORT environment variable during provisioining, so user doesn't need to know which random port is being assigned to the server. As for host box, let's use something a bit uncommon too, like 7778.

@alayek when you say client and host machines, I somehow always confuse them, which one is which? Is the client machine the local laptop of the user such as the MacBook Pro?
Yes, if there is absolutely no problem of assigning for the VM such a big port number, why not. 7778 is good since it is not standard for anything. But the key is to later automate this assignment.
Also there is a way to assign to the vagrant VM a specific name so you can reference it much quicker from the vagrant global-status command or it will be displayed nicely under a good nickname inside virtualbox GUI, but this is not necessary and can destroy the multi-vagrant-box development modus.

I think we already modified it to some extent, by using port 5000. It technically solves the issue, but I want to patch it in a way, that it makes a more intelligent decision in Vagrantfile and assigns a safe port somewhat carefully.

@alayek do you still have this problem? I noticed that to have the port forwarding to work properly, you need to match what is written in your Vagrantfile and what is printed in the terminal while doing vagrant up or zeus.py newproject the forwarding port. Say if vagrant forwards 5000 to 5000, then you cannot run python manage.py runserver 6000 since this is not forwarded. You can do it for 5000 and in your local browser it will work.

Yes, the port forwarding is working fine for me. But I was hoping we would add some nifty robust feature so that it works on most machines.
It's doable, Vagrantfile is mostly Ruby, so it would be a while-loop with an if-else test I guess.

Yes I think so, I cannot do Ruby yet. Maybe we should let a ruby programmer do it.

You can add auto_correct: true to your port forward in order to have it detect collisions and increase the port number by 1 to avoid conflicts.

My suggestion would be if there are specific ports that a stack requires you could read an options file that lists which stack a user chose and forward those ports for them.

Great point, I will do that for ports using this method, didn't think of that


Parsing primary & secondary sitemap.xml

Details
When I supply a website URL, the URL includes a sitemap.xml. Inside this sitemap.xml, there is a set of other sitemap.xml files. However, when I run the tool using this primary sitemap.xml, it doesn't appear to parse the secondary or Level II sitemap.xml files. Is this a bug or if this is not implemented yet ?

Hi @TitusRobyK, thanks for the issue :)
As far as I know, this feature is working correctly. Are you able to share the site you're scanning?
Otherwise you can try running with --debug to see what's happening.

Hi @harlan-zw , It does not seem to work ,
Here is the command that i am trying
This is the command that I am trying
unlighthouse-ci --site anthemeap.com/sitemap.xml

Hmm that's a lot of sitemaps! Likely causing the problem?


Problem with RW+ privileges on manager user

Hello, i need to give my user RW+ privileges and i gave privileges him to manager, but ssh git@git info tell me that i have only RW privileges.
Redmine version: 2.6.1
Git version: 1.9.1
Gitolite version	: 3
Redmine Git Hosting: 1.0.0

Hello, i need to give my user RW+ privileges and i gave privileges him to manager, but ssh git@git info tell me that i have only RW privileges.

You need to give the :manage_repository permission to a role. Users with this role (and this permission) will have RW+ privileges on project repositories.

How can i do this?

In Administration -> Roles

Users with manager role has select Manage Repository, but gitoline show only RW.

Users with manager role has select Manage Repository, but gitoline show only RW.

Got the same here :
nicolas@tchoum-desktop:~$ ssh<EMAIL_ADDRESS>info
Debian GNU/Linux 7
hello redmine_developper1_5, this is git@example running gitolite3 v3.6.2-12-g1c61d57 on git 1.9.1
R W	test
repo    @all
  RW+                            = DUMMY_REDMINE_KEY

repo    gitolite-admin
  RW+                            = redmine_gitolite_admin_id_rsa

repo    test
  RW+                            = redmine_admin_1 redmine_developper1_5
  R                              = redmine_rapporter1_6 gitweb
  config redminegitolite.projectid = test
  config redminegitolite.repositoryid =
  config redminegitolite.repositorykey = 4R5zOWFvJ18aNvwn57uLC40nj3Q1RSrRXi9E3B5QIorG0bPUQJkqQWqrADEEo0L
  config http.uploadpack = true
  config http.receivepack = true
  config multimailhook.enabled = false

I don't this is an issue : http://gitolite.com/gitolite/user.html#info http://gitolite.com/gitolite/g2/info_expand.html
The info command only display R W or C status.