Update jstree.checkbox.js to allow checkbox/selection separation

It is not always desirable to check a checkbox associated with a node when the node is simply clicked upon. In my case, I wish to use this particular event to show additional details about a node. I have therefore added a check_by_selection option which defaults to true. This is used to determine what triggers a node to be checked/unchecked. If it is set to true, clicking anywhere on the node will toggle it. If set to false, only clicking on the checkbox will trigger this.

This is already built in:
http://www.jstree.com/api/#/?q=whole&f=$.jstree.defaults.checkbox.whole_node
There is also tie_selection if you need it.
Best regards,
Ivan

Doh!
Thank you :)
On 14 May 2015 at 18:16, Ivan Bozhanov<EMAIL_ADDRESS>wrote:

This is already built in:
http://www.jstree.com/api/#/?q=whole&f=$.jstree.defaults.checkbox.whole_node
There is also tie_selection if you need it.
Best regards,
Ivan
—
Reply to this email directly or view it on GitHub
https://github.com/vakata/jstree/pull/1115#issuecomment-102106323.


Windows Capable?

I've found and seen info about Linux, but I'm having trouble finding any instructions for installing babelfish on a Windows OS-my priority is installing the dependencies.
Any help or feedback on the matter would be greatly appreciated.

I'm in the same boat. I'll consult with the dev team and reply back here.

@Sawsbucky: Unfortunately we are not planning to support Windows builds for now.

Just in case someone will be looking for Windows builds, I am doing Windows builds in this repo. These builds are done from sources modified for downstream WiltonDB project. If the plan to have Windows support in upstream Babelfish will ever be reconsidered - I can happily contribute Windows patches for that.


List of possible values

Is it possible to get list of possible values for each method?

Take a looksee https://github.com/rguerreiro/device/blob/master/lib/device.js#L47


CommitStats in the Commit struct is always nil

The CommitStats in the Commit struct is always nil.
Comparing the current Commit struct:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/git_commits.go#L44-L62
With the GitHub OpenAPI Spec:

The Stats field is not on the OpenAPI Contract.

I know that structs can be used to represents objects that look alike a lot (hence the CommentCount field).
So I'm not sure if the Stats field is also one of these exceptions. If that's the case, it should be explained just like CommentCount.

I'm not sure I would call this issue a "bug".
According to GitHub, that line was added in 2013 in this commit:
https://github.com/google/go-github/commit/1eaf38380d74925650bee1593df74e1a1c0dc3a7#diff-58a05e976d34ffef86ba94037754253cc9c33d354c78296018a375577ead4b19R21
entitled "implement repos_commits API".
So apparently it was once used by GitHub.  As to its current usage, that would definitely require some investigation.
I'm happy to leave this issue open in case anyone would like to perform some investigation into this field's usage
and add a comment as to how and when it is used.

I'm not sure I would call this issue a "bug".
According to GitHub, that line was added in 2013 in this commit: 1eaf383#diff-58a05e976d34ffef86ba94037754253cc9c33d354c78296018a375577ead4b19R21 entitled "implement repos_commits API".
So apparently it was once used by GitHub. As to its current usage, that would definitely require some investigation. I'm happy to leave this issue open in case anyone would like to perform some investigation into this field's usage and add a comment as to how and when it is used.

Thanks for the quick answer @gmlewis. I will investigate as it wrongly put me into assuming I could check a created commit stats from the response.
I do think that it is not populated at all in any case. If that's the case I can submit a PR removing that field, otherwise a PR explaining where it is used.

I do think that it is not populated at all in any case. If that's the case I can submit a PR removing that field, otherwise a PR explaining where it is used.

Excellent.  Thanks, @acouvreur . Sounds good.  It's yours.

Commit struct analysis:

Usage in struct `CheckSuite`: ✅ No usage
The Commit struct is used in CheckSuite.HeadCommit:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/checks.go#L71-L92
As mentionned, the HeadCommit field is only populated by Webhook events, so let's check CheckSuite Webhooks events:

This is the same for completed, requested and rerequested.
Conclusion: no usage of Stats in CheckSuite.HeadCommit

Usage in struct `MergeGroup`: ✅ No usage
The Commit struct is used in MergeGroup.HeadCommit:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/event_types.go#L842-L854
The MergeGroup structure is only used through the MergeGroupEvent struct, so let's check MergeGroup Webhooks events:

This is the same for checks_requested and destroyed.
Conclusion: no usage of Stats in MergeGroup.HeadCommit

Usage in struct `Commit`: ✅ No usage
The Commit struct is used in Commit.Parents:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/git_commits.go#L44-L62
Parents in Commit look like this (from the OpenAPI Contract):

This could be refined to be a CommitRef instead of Commit though.
Conclusion: no usage of Stats in Commit.Parents

Usage in struct `Timeline`: ✅ No usage
The Timeline struct is used in Timeline.Parents:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/issues_timeline.go#L18-L38
This is only used in a single Timeline event, which is committed: https://docs.github.com/en/rest/using-the-rest-api/issue-event-types?apiVersion=2022-11-28#properties-for-committed
Parents in the Timeline Committed event look like this (from the OpenAPI Contract):

This could be refined to be a CommitRef instead of Commit though, just like the one in Parents.
Conclusion: no usage of Stats in Timeline.Parents

Usage in struct `RepositoryTag`: ✅ No usage
The RepositoryTag struct is used in RepositoryTag.Commit:
https://github.com/google/go-github/blob/master/github/repos.go#L967-L973
This is only used in listing the tags in a repository: https://docs.github.com/en/rest/repos/repos#list-repository-tags
Commit look like this (from the OpenAPI Contract):

This could be refined to be a CommitRef instead of Commit again to avoid confusion.
Conclusion: no usage of Stats in RepositoryTag.Commit

Usage in struct `BranchCommit`: ✅ No usage
The BranchCommit struct is used in BranchCommit.Commit:
https://github.com/google/go-github/blob/master/github/repos_commits.go#L118-L123
This is only used in listing branches for HEAD commit: https://docs.github.com/en/rest/commits/commits#list-branches-for-head-commit
Commit look like this (from the OpenAPI Contract):

This could be refined to be a CommitRef instead of Commit again to avoid confusion.
Conclusion: no usage of Stats in BranchCommit.Commit

Usage in struct `RepositoryCommit`: ✅ No usage
The RepositoryCommit struct is used in RepositoryCommit.Commit and RepositoryCommit.Parents:
https://github.com/google/go-github/blob/c4a49db9ca5d5f737f459fa97e3b86c52339b978/github/repos_commits.go#L16-L34
RepositoryCommit is used in a lot of different places:

Usage in struct `StatusEvent`: ✅ No usage
  The `StatusEvent` struct is not used directly by any function or struct.
And the event schema is defined as:

Conclusion: no usage of Stats in StatusEvent.Commit, StatusEvent.Parents and StatusEvent.Branches.Commit

Usage in function `RepositoriesService.ListBranches`: ✅ No usage
  The `RepositoriesService.ListBranches` function returns a `Branch` which contains a `RepositoryCommit`.
The OpenAPI Schema defines the following:

This could be refined to be a CommitRef instead of Commit again to avoid confusion.
Conclusion: no usage of Stats in Branch.Commit.Commit when called through RepositoriesService.ListBranches

Usage in function `RepositoriesService.GetBranch`: ✅ No usage
  The `RepositoriesService.GetBranch` function returns a `Branch` which contains a `RepositoryCommit`.
The OpenAPI Schema defines the following:

Conclusion: no usage of Stats in Branch.Commit.Commit when called through RepositoriesService.GetBranch

Usage in function `RepositoriesService.RenameBranch`: ✅ No usage
  The `RepositoriesService.RenameBranch` function returns a `Branch` which contains a `RepositoryCommit`.
The OpenAPI Schema defines the following:

Conclusion: no usage of Stats in Branch.Commit.Commit when called through RepositoriesService.RenameBranch

Usage in function `RepositoriesService.CompareCommits`: ✅ No usage
The RepositoriesService.CompareCommits function returns a CommitsComparison which contains two RepositoryCommit (BaseCommit and MergeBaseCommit fields).
The OpenAPI Schema defines the following:

Conclusion: no usage of Stats in CommitComparaison.BaseCommit.Commit and CommitComparaison.MergeBaseCommit.Commit when called through RepositoriesService.CompareCommits

Usage in function `PullRequestsService.ListCommits`: ✅ No usage
The PullRequestsService.ListCommits function returns a CommitsComparison which contains two RepositoryCommit (BaseCommit and MergeBaseCommit fields).
The OpenAPI Schema defines the following:

Conclusion: no usage of Stats in CommitComparaison.BaseCommit.Commit and CommitComparaison.MergeBaseCommit.Commit when called through RepositoriesService.CompareCommits

I have a few more structs to go through, but overall it looks like Stats inside Commit is never actually used in any circumstances.
Does that make sense to deprecate or even remove the field at all ?

Does that make sense to deprecate or even remove the field at all ?

With this detailed analysis, I'm totally fine with you creating a PR to remove the field.
Thank you for doing this deep dive, @acouvreur !


Reliance on toEqual causes problems

I've had a few issues around getting proper equality of the object returned when using jasmine-marbles. It seems to boil down to the use of expect(results).toEqual(expected); in the toBeObservable method. This doesn't feel flexible enough and suffers from the following https://github.com/jasmine/jasmine/issues/598 among other things.
Could an override of toBeObservable be added that would allow for a custom comparison function be passed in rather than the hammer that is expect(results).toEqual(expected);? Something like:
toBeObservable: function(matcher: (results: TestMessage[], expected: any) => void) => ({
    ...

   //expect(results).toEqual(expected);
   matcher(results, expected);
});

this would then allow me to implement this fix https://github.com/jasmine/jasmine/issues/598#issuecomment-340284189 among other things?

It looks like rxjs marble testing already supports this scenario, e.g.:
const testScheduler = new TestScheduler((actual, expected) => {
  // asserting the two objects are equal
  // e.g. using chai.
  expect(actual).deep.equal(expected);
});

In the end I used this framework to get what I need not jasmine-marbles.
https://rxjs-dev.firebaseapp.com/guide/testing/marble-testing


However if I import like this:
import<EMAIL_ADDRESS>
then this works.
How can I get it to understand the pathing?
PS: I've got this in the settings as hinted at elsewhere and it still doesn't work:
    "solidity.packageDefaultDependenciesContractsDirectory": "",
    "solidity.packageDefaultDependenciesDirectory": "node_modules",

Having the very same issue here

Having the very same issue here


Update to heck 0.5, version-compare 0.2 and itertools 0.12

@gdesmott Can we get a release with this?

Sure: 6.2.2


Update public-ip-basic-upgrade-guidance.md

Migration script of ExpressRoute Gateway is GA.
The word "Preview" should be removed from this document as well.

@mbender-ms
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close


Regex repetition not working

The {min, max} syntax doesn't work.
Eg:
> FFaker::String.from_regexp(/[0-9]{5}/)
 => "2{5}"

Expected result would be something like 82621
Reference: http://www.regular-expressions.info/repeat.html

I think this one resolve with d690e66
@rocknruby isn't it released yet?

Not yet released but I will do it now. We just have to update the changelog @marocchino.

New version is released.


Got error unresolved

after i installed the apisauce i got error:
transformed 416/417 (100%)(node:2216) UnhandledPromiseRejectionWarning: Unhandle
d promise rejection (rejection id: 290): UnableToResolveError: Unable to resolve
module http from F:\ReactNative\test\node_modules\axios\lib\adapters\http.js: M
odule does not exist in the module map or in these directories:
F:\ReactNative\test\node_modules
i work with windows 7, npm and android
the files exists in the directory...

Are you using npm 2 by any chance?

I have same issue, it worked fine on react-native 0.39.0 but got error on react-native 0.40.0

It isn't related to version of RN. Try to install "apisauce": "0.7.0".

I wonder if this is related?  https://github.com/mzabriskie/axios/issues/648

No issue here with Android on Mac:

Android 6 api 23
React Native 40
Apisauce 0.8
Axios 15.3

It must be a Windows thing?  I'll poke around some more.
Source if you're interested.
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 * @flow
 */

import React, { Component } from 'react'
import {
  AppRegistry,
  StyleSheet,
  Text,
  View
} from 'react-native'
import {create} from 'apisauce'

// define the api
const api = create({
  baseURL: 'https://api.github.com',
  headers: {'Accept': 'application/vnd.github.v3+json'}
})

export default class ApisauceTest extends Component {

  callApi () {
    // start making calls
    api
      .get('/repos/skellock/apisauce/commits')
      .then((response) => response.data[0].commit)
      .then(console.log)
  }

  render () {
    const callApi = this.callApi.bind(this)
    return (
      <View style={styles.container}>
        <Text style={styles.welcome} onPress={callApi}>
          Welcome to React Native!
        </Text>
      </View>
    )
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF'
  },
  welcome: {
    fontSize: 20,
    textAlign: 'center',
    margin: 10
  },
  instructions: {
    textAlign: 'center',
    color: '#333333',
    marginBottom: 5
  }
})

AppRegistry.registerComponent('ApisauceTest', () => ApisauceTest)

So @GantMan and I tracked it down to:
https://github.com/mzabriskie/axios/blob/master/lib/defaults.js#L23
Comment that line on out on Windows and the packager will finish it's transform process.
More details when we ask some people at Facebook about how the packager works.

https://github.com/facebook/react-native/issues/11498#issuecomment-273972902


Fix OSX build, std::max template resolution with different types.

Description
Fix OSX build:
std::max with different argument types is a compile error.

@zheng-da please incorporate the changes of this PR in file 'tests/cpp/operator/fully_conn_perf.cc' into your new PR as this change has been reverted as well.


Include some open source fonts

Adding some open source fonts like SourceCode Pro would be nice. That would provide the needed bits for powerline to work on this console

Oh that is good to know, I am going to add this.

Added, did not make it to 1.2, but will be in 1.3


Update openknx to 0.6.3

Please update my adapter ioBroker.openknx to version 0.6.3.
This pull request was created by https://www.iobroker.dev c0726ff.

0.6.3 created 10.12.2023

RE-CHECK!


Bug fix: wrong dimensions for premult in TIFFInput::read_tiles

Just noticed this while doing other things. Nobody has reported a problem, but it's clear to me that if people were using the special "give me the unassociated values" attribute, and reading multiple tiles, this would be using the wrong dimensions for the buffer.

LGTM!


Problems with Postfinance

Hi All
I am using csharp-sdk with postfinance. Everything seems to working fine until i see the payment methods, when I choose one (with a click) postfinance redirects me to the given failedUrl. There is no error and no entry in the transactionlog in my Dashboard (when i cancel the transaction without choosing payment method it appears as cancelled), what could be the problem?
I am aware of the fact, that this could be an error by misconfiguration but postfinance - Helpdesk is not very helpful at the moment.
sincerely

Dear Balaban,
It could be that you invoked the API with invalid customer data. However please ask the PostFinance Helpdesk as they are in charge of this.
Regards,
Thomas


fix: add name to components

The components created by using the ?component flag are anonymous.
This sets the components name to the filename.
Additionally, it reverts the changes made in #32. While attribute inheritance might have been broken then, that's not the case anymore. The changes in #32 also made it incompatible with the type definitions. Now it is more inline with  FunctionalComponent again.

Thanks for your PR. Could you please have a look at the failing tests?

Closed because of inactivity


Implement OR-Based Group Validation

Problem Statement
While testing https://github.com/jkroepke/openvpn-auth-oauth2/issues/150 I implemented group validation in my Azure setup first. I noticed that the group membership check is currently requiring a user to be a member of ALL mentioned groups (AND). I would expect (or at least would like to have the option) that a user would only need to be part of one of the mentioned groups (OR).
Proposed Solution
No response
Additional information
No response
Acceptance Criteria
No response

As I know, is can be archived by assign the mandatory groups to the Azure AD App registration itself. For example you can configure 2 group and users only need part of one group.
This is generally prefered, since users get the notice from Azure that they are not part of the group and the login would be denied.
https://learn.microsoft.com/en-us/entra/identity-platform/howto-restrict-your-app-to-a-set-of-users#assign-the-app-to-users-and-groups-to-restrict-access

But after review other solutions, the OR based approach is more commonly used then the AND based approach.


[fix] pfelement | Change default on emitEvent to composed: true

Description of the requested feature
From https://developers.google.com/web/fundamentals/web-components/shadowdom#customevents:
Custom DOM events which are fired on internal nodes in a shadow tree do not bubble out of the shadow boundary unless the event is created using the composed: true.

To ensure that events emitted from components embedded inside other components push up through the Shadow boundaries, I think we should change our composed default to true.
Impacted component(s)

pfelement

If composed: false (default), consumers won't be able to listen for the event outside of your shadow root.
^ I think that should be an opt-in behavior instead.

From @mwcz:
I thought there might be a minor performance cost to (sometimes needlessly) letting events out into the light DOM, but I just did a test and can't see any performance difference no matter how many elements might be listening.

I made a thousand p tags and tried emitting an event from depth 1, depth 500, and depth 1000, and listened for them on the body.  The timing was the same for all three depths

0.07 - 0.1 ms


fix: Divide field by zero

Description
I don't know if this will fully resolve the issue. if the issue persists, i'll also change the code here
https://github.com/noir-lang/noir/blob/master/crates/noirc_evaluator/src/ssa/acir_gen/acir_ir/acir_variable.rs#L367-L382
https://github.com/noir-lang/noir/blob/master/crates/noirc_evaluator/src/ssa/acir_gen/acir_ir/acir_variable.rs#L203-L231
Problem*

Related to https://github.com/noir-lang/noir/issues/2149
Summary*

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Can you diagnose the issue to see if it is fixed by this change?

Closing as this is fixed as per: https://github.com/noir-lang/noir/pull/2475


Fix slight grammatical error

“This above examples” sounds a little odd and might be a slight grammatical error. Perhaps “The above examples” would be more accurate.

Hi, we have merge conflicts, could you please resolve them and I'll get this merged!

Hope that fixes it.


MCA to Azure Plan

Hi, is there still no progress/update on being able to transfer MCA subscriptions to CSP Azure Plan? Same tooling as EA transfer requests. Thank you.

thanks for sharing @wedoazure.
@JulCsc Any Idea on who can authoritatively answer the above questions?

Hi @wedoazure from discussions internally, the subscription mgmt. support team will be able to answer your question. Kindly use this link to raise a support ticket for free.
hope this helps.

We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Error when client certificate is requested

When the server requests a client certificate (in the case of a GnuTLS server, the gnutls_certificate_server_set_request function), the aioquic client returns a QUIC Error: 266, reason: , frame_type: 6 error and the connection is closed

I'm encountering the same problem when implementing a client for communicating with Apple's iOS services (starting at iOS 17)

Hi, I've been wanting to implement this but lack a publicly accessible server against which to test it. If anyone wants to tackle this please make sure you include a full test suite!

@jlaine I added a PR that should handle it
@Payne-X6 can you also make sure this fixes your issue?

@doronz88 I tried your PR. It works with small changes, beware that the client cert does not need to be set (can be set to None).
This is also valid, some server implementations may request but not require a client cert.
But with a few conditions in _client_handle_finished this can be fixed.

@Payne-X6 I fixed the _client_handle_finished to handle no certificates. From my understanding, the certificate being sent twice isn't necessarily bad, since the client cannot tell before trying to establish the connection wether the remote party would use CertificateRequest-based authentication. I could add an option for disabling its send in the Hello packet.
@jlaine Could you take a look at the PR I reopened? I tested it and managed to create a fully working connections with the new iOS services.

@doronz88 Could you add a not-None check for self.certificate_private_key ? It's crashing on self.certificate_private_key.sign(...) (https://github.com/aiortc/aioquic/pull/386/commits/cf348bd870158141d999ffbd1ca1da1063a4c0f8#diff-7ade72bf4580c7d1ea561a54e1067f4d744c1f0f037ccd42737467b0360ab51bR1597).

I stopped caring about aioquic since it seems this project isn't very active on PRs (to say the least).
This support was added instead in:
https://github.com/jawah/qh3

I stopped caring about aioquic since it seems this project isn't very active on PRs (to say the least). This support was added instead in:

Great, love the positive attitude. Stepping up and offering to co-maintain would have just been too much effort.

When the server requests a client certificate (in the case of a GnuTLS server, the gnutls_certificate_server_set_request function), the aioquic client returns a QUIC Error: 266, reason: , frame_type: 6 error and the connection is closed

Do you have a public server where you encountered this please?

When the server requests a client certificate (in the case of a GnuTLS server, the gnutls_certificate_server_set_request function), the aioquic client returns a QUIC Error: 266, reason: , frame_type: 6 error and the connection is closed

Do you have a public server where you encountered this please?

You can use ns2.xdp.cz. for testing.

You can use ns2.xdp.cz. for testing.

Unfortunately I'm not having any luck, that server doesn't respond to my INITIAL packet. Is it actually an HTTP/3 server?

You can use ns2.xdp.cz. for testing.

Unfortunately I'm not having any luck, that server doesn't respond to my INITIAL packet. Is it actually an HTTP/3 server?

It's a DNS server with enabled DNS over QUIC (port 853).

Thank you!

It's a DNS server with enabled DNS over QUIC (port 853).

Ah that's what I was missing. The handshake does complete with the latest code in main both with and without a client certificate. I do however need to disable certificate validation when running the test as the server's certificate does not have any Subject Alternative Name.


profile_card- Sowham Bhuin

Added all files and updated README.md

@DiyaVj Please review this and merge this


[Feature] - Add more wearOS APIs

https://developer.android.com/training/wearables

@fabOnReact Absolutely amazing stuff man!
Hey! I have some experience in developing apps with Jetpack Compose for WearOS and wear OS in general. I think I can help out here but just need a few clarifications regarding the architecture.
As I understand it, for a long time we couldn't use RN to make WearOS apps (which is one of the reasons my team mates and I had to learn Jetpack Compose & Kotlin).
1. Is this repo possible now because of the new Architecture?
We've already developed a bunch of stuff in Kotlin, so in order to make "plugins" for this repo ie Native WearOS functionality ( things like RotaryInput, ScreenDimming) etc.
2. We have to create "Native Modules" like mentioned in the official docs ?
3. Is it possible to create other WearOS modules like Watchfaces, Complications and Tiles
Again, thanks a ton for this repo!

We have to create "Native Modules" like mentioned in the official docs ?

React Native Components for WearOS
You can create React Native Components using Views, but I don't reccomend it. I tried to build a ReactWearScrollView component based on Android WearableRecyclerView, but it required too much work.
There is an old implementation of RecyclerView in ReactNative, but our FlatList implementation is based on ScrollView not RecyclerView.
WearOS now uses JetPack Compose for most of the APIs, which is not very easy to use with React Native (https://github.com/react-native-community/discussions-and-proposals/issues/446)
I see now that we have several new JetPack Compose libraries available for React Native that allows us to use the JetPack compose components in React Native https://www.google.com/search?q=react+native+jetpack+compose+github
There is a Column component in jetpack-compose-react-native, so we would need to add support for ScalingLazyColumn and other APIs.
React Native Modules for WearOS
No problem with native modules, this library itself uses Native Modules to send/receive data between WearOS and Android Devices. https://github.com/fabOnReact/react-native-wear-connectivity/blob/main/android/src/main/java/com/wearconnectivity/WearConnectivityModule.java
CONCLUSION
I believe the best choice is for now developing the WearOS app with Jetpack Compose.
I'm working on the documentation on how to easily connect React Native to Jetpack Compose using this library.
I have an open issue here https://github.com/fabOnReact/react-native-wear-connectivity/issues/32
Watchfaces, Complications and Tiles

Is it possible to create other WearOS modules like Watchfaces, Complications and Tiles?

This library does not allow you to create Watchfaces, Complications or Tiles.
You need to look into the internals of react-native-android-widget and the Android APIs.

closed in favour of https://github.com/fabOnReact/react-native-wear-connectivity/issues/32
see https://github.com/andrew-levy/jetpack-compose-react-native/issues/9#issuecomment-2490336411 for more details on why it may not be a good idea to follow this strategy

https://github.com/andrew-levy/jetpack-compose-react-native/issues/9#issuecomment-2552613782

https://github.com/andrew-levy/jetpack-compose-react-native/issues/9#issuecomment-2558029400


Implement Mixpanel in iOS project that uses Swift.

Cocoapods is not ready for Swift yet. When I implemented Mixpanel into my iOS project that uses Swift, I got several errors.

The bugs come from #import UIKit/UIKit.h. The reason is in Objective-C project, we just need to add
#ifdef __OBJC__
	#import <UIKit/UIKit.h>
	#import <Foundation/Foundation.h>
#endif

in Prefix.pch
However, we don't do this in Swift project and we don't need to add framework one by one. So we have to add import UIKit/UIKit.h in necessary files.
Here is one of file we need to import UIKit/UIKit.h

We also need to add libicucore.dylib, CFNetwork.framework, and Security.framework in Link Binary With Libraries.

Add the libraries as noted in the podfile, and also that you noted (libicucore.dylib, CFNetwork.framework, and Security.framework).  Then create a bridging header file (https://bohemianpolymorph.wordpress.com/2014/07/11/manually-adding-a-swift-bridging-header/) and put the #import "Mixpanel.h" in there.
Establish the shared instance in didFinishLaunchingWithOptions in AppDelegate.swift:
Mixpanel.sharedInstanceWithToken("secretgibberish")
From there you can track things in your Swift code:
let mixpanel = Mixpanel.sharedInstance()
mixpanel.track("Some View", properties: ["Some ID": some_id])

Closing this stale PR.


TestE2E/ConnectionLimit  Close_connections_over_limit e2e test seems to constantly fail

Seems that this test constantly fails now:
https://github.com/envoyproxy/gateway/actions/runs/8434551780/job/23098264792?pr=3022
https://github.com/envoyproxy/gateway/actions/runs/8432274812/job/23091217953

@guydc could you please take a look?
Sorry that I didn't notice that the e2e tests haven't finished yet when merging the PR https://github.com/envoyproxy/gateway/pull/2952. My bad :-(

@zhaohuabing can you send a PR disable the test first?

@zirain sure. https://github.com/envoyproxy/gateway/pull/3025

Sorry, I made a renaming mistake e2e/docs. Trying to fix now.


Some compiler optimizations

Some optimizations from musings in https://github.com/crystal-lang/crystal/issues/8527#issuecomment-559300111
The first two commits are self-explanatory. The third commits has a big commit message explaining the description of the problem. After reading that you can understand how it applies to this particular example:
require "spec"

macro assert(call, file = __FILE__, line = __LINE__)
  {% obj = call.receiver %}
  {% name = call.name %}
  %obj = {{obj}}
  %call = %obj.{{name}}
  unless %call
    fail "Expected #{%obj} to be {{name[0...-1]}}"
  end
end

describe "Foo" do
  {% for i in 0..12_000 %}
    it "bar {{i}}" do
      a = [1, 2, 3]
      assert a.empty?
    end
  {% end %}
end

In the above code the assert macro will define the local variables %obj and %call which will actually expand to variables named something like __temp1 and so on, and they'll all be different. Because of the above compiler bug, all these local variables will be seen in each assert macro invocation. So the first assert expansion can only see the a local variable. The second one will see that plus the two local variables introduced by the previous macro invocation (which shouldn't be seen, but that's the bug the third commit is fixing). On each invocation a Set is created with these local vars. That has something like quadratic complexity which explains why the above code was taking 12 seconds. Now it takes 0.4s (well, at least the "main" semantic phase).
I always thought macro expansion was slow, but apparently it's not. Or at least not that slow.
Once we merge this PR we can see if #3095 is still slow for the snippet I found it to be slow.

Well, actually, it seems power_assert is still slow to compile but because it generates a ton of code. I think the assert could be made simpler, I'll see.

Do you have any benchmarks for this?

Well, actually, it seems power_assert is still slow to compile but because it generates a ton of code. I think the assert could be made simpler, I'll see.

Maybe this simpler generated assert code proposed by RX14 might help

I suppose there's a mistake in the example code from the third commit? Or else I just don't get it.

Ah, yes, there's a mistake. It should be puts id(a). I'll fix it later.
The benchmark is the snippet with that assert. Compile it with the existing compiler and with a compiler with this PR and you'll see a difference (of about 12 seconds less on my machine).

I'd merge but there's no newer "milestone", so I guess we can wait until that exists... or we create one now? Can we merge before 0.32.0 is released?

Merging it for 0.32 is fine on my end. As long as there are no breaking changes :-)

Cool, let's do it!


fix(AjaxObservable): ignore content-type for formdata

Description:
allow undefined content-type header if body is formdata
Related issue (if exists):
references GitHub issue https://github.com/ReactiveX/rxjs/issues/1729

Changes Unknown when pulling 53ac1b9f51aad742a678a4917acf2edd03f6bb25 on LevelBits:formdata-content-type into ** on ReactiveX:master**.

change looks ok to me.


Timer lock

Hi,
is it possible to block putting the passcode for some time duration when limit of attempts was reached by user?

I think currently it is not support.
One way you could achieve it is by resigning the FirstResponder of the PasscodeTextField and call becomeFirstResponder with a Timer and the duration you want to disable the passcode lock.

Ok, thanks for answer :)


getERC1155Listings returns more listings than are open

After creating a few listings, calling getERC1155Listings with params "0", "listed", 20 results in 20 listings, even though there should only be 2 unique listings.

I think this was already fixed at an earlier time but after the diamond was deployed, as the code looks correct.

Let's try this again to see if it works now.   New diamond was deployed yesterday.

Yep, it's fixed.

Re-opening because I just saw this happen again with the latest deployment.

@mudgen This should be fixed now, right?

Yes

Great, closing.


[Question]: How to give the virtual machine more VRAM?

Is your question not already answered in the FAQ?

[X] I made sure the question is not listed in the FAQ.

Is this a general question and not a technical issue?

[X] I am sure my question is not about a technical issue.

Question
By default the virtual machine only has 7MB of VRAM which isn't enough to properly run games. Is there a way I can increase this amount?

I think it is not possible

Try this, check you have enough cpu and ram for this.
docker run -it -e VERSION="13" -e DISK_SIZE="128G" -e RAM_SIZE="10G" -e CPU_CORES="8" -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 dockurr/macos


Tomato Helpline Routing redirecting calls incorrectly

Tomato Helpline Routing is not functioning correctly in the scenario where a search returns a service body ID from Tomato that also exists in the root server configured currently.
It looks like this bug has been around for a while.
Example:
A number is configured to use tomato_helpline_routing and someone searched for a location that returns a service body from tomato that also exists in the predefined root server in the yap configuration.

Fixed in 3.10.0.


Meeting summary 5/12/16

Attendees: Itai & Zvi, David, Shay, Zahi, Or, Dani, Tom, Sefi, Shahar
At the metting, we went through the final design and concept of the project.
We looked on several issues for exmaples, and clarify the schedule for the upcoming 6 weeks.
We agreed on the following:

In the next two weeks, it is understood that a big part of the team is going to focus on studing and acquiring new technologies (GUI & DB teams mostly). On each new subject, please create a wiki page with a short explanation.
At the end of this two weeks, the team should be able to present the work done so far to the class with a short presentation, Code examples are fine. Also partial work is OK at this part.
After Hanukkah, the team should have somthing decent that WORKS and can be presented. There are only two weeks left after the holiday for a final push in this current sprint.

Other things that came up:

It is ok to have open issues, but it is expected to start seeing closed ones as well. Opening  new issues as we go is fine.

The concept we created the issues is fine: a well-defined task and a responsible dev assign to it.

At the bottom line - start coding.

Makre sure that all studying tasks are reflected as issues, best with deliveries such as:

Wiki
Prototype

@idabran @zvili


can we use flip animation for icon?what is the animation name? 'flip' not working

Issue type
I'm submitting a ...  (check one with "x")

[ ] bug report
[ ] feature request

Issue description
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert short code snippets here

Other information:
OS, device, package version
insert information here

@vipinkviswanath as we mentioned in Icon API docs:

Available zoom, pulse and shake. Default is zoom.


SyntaxError in compability.py on Python 3.7

Though I know 3.7 isn't officially released yet, it would be nice to support it beforehand.
One option is to replace asyncio.async with getattr(asyncio, "async"), or even use getattr(asyncio, "ensure_future", getattr(asyncio, "async"))

As far as I can tell, the current implementation already does what you suggest:
https://github.com/aaugustin/websockets/blob/13eb4a09815b7edf3ac6270cbdf131b89b4ccc9d/websockets/compatibility.py#L12-L15
It uses try / except AttributeError instead of getattr but the logic is exactly the same.

Version 6.0 adds support for Python 3.7 and is now available on PyPI: https://pypi.org/project/websockets/6.0/#files


[tool_crash] FileSystemException: Failed to decode data using encoding 'utf-8', null

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Failed to decode data using encoding 'utf-8', null
#0      _File._tryDecode (dart:io/file_impl.dart:564:7)
#1      _File.readAsStringSync (dart:io/file_impl.dart:584:7)
#2      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:96:16)
#3      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:222:22)
#4      _runSync (package:flutter_tools/src/base/error_handling_io.dart:597:14)
#5      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:221:12)
#6      _readFileContent (package:flutter_tools/src/flutter_plugins.dart:255:35)
#7      _writeFlutterPluginsListLegacy (package:flutter_tools/src/flutter_plugins.dart:246:40)
#8      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1051:30)
<asynchronous suspension>
#9      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:316:5)
<asynchronous suspension>
#10     PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:177:5)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#16     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)

[✓] Flutter (Channel stable, 2.10.5, on Microsoft Windows [versÃ£o 10.0.22000.739], locale pt-BR)
    • Flutter version 2.10.5 at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (9 weeks ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at C:\Users\Matt Brevis\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.2.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.2.32616.157
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2021.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[✓] VS Code (version 1.68.1)
    • VS Code at C:\Users\Matt Brevis\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • SM A715F (mobile) • RX8NC0121NV • android-arm64  • Android 12 (API 31)
    • Windows (desktop) • windows     • windows-x64    • Microsoft Windows [versÃ£o 10.0.22000.739]
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 102.0.1245.44

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter Application Metadata
FileSystemException: Failed to decode data using encoding 'utf-8', path = 'C:\Users\Matt Brevis\Desktop\quickpg\quickpg.flutter-plugins'

Closing this as a duplicate of https://github.com/flutter/flutter/issues/65021


opengl version

Opengl 4.4 not supported.

As far as I am concerned, this project will not support OpenGL under version 4.6 in the beginning.

First of all, I see you're rendering using the integrated graphics of your CPU. Do you have any dedicated GPU? If so, you can set preferences (global or application wise) which GPU it should choose. I expect your graphics card to support higher than only 4.4.
We are using OpenGL 4.5 functions, so at least version 4.5 is required as of now. You could tweak the renderer a bit to support lower. Since this engine is still heavily a WIP, by the time it is finished, requiring OpenGL 4.5, or even OpenGL 4.6 should be of no issue.
Keep in mind that in the end, there will be other renderer support, for example Vulkan, or native renderers like DirectX (cherno mentioned 11 if i'm not mistaken).
I'll close this for now, as this is sort of intended at this point. Please go to our Discord if you require any help checking the graphics settings I mentioned before.

Well I'm using intel HD graphics 5500 which supports opengl 4.4


kafka-net-core nuget

Provided kafka-net-core nuget package contains debug binaries?

No, it doesn't have debug information

I published new version just to be sure. It's definitely in release now.
https://www.nuget.org/packages/kafka-net-core/1.0.3
You can check after it will be published and listed

Tested with 1.0.3 version and it works!


Keep browser opened on failure

As suggested in #38, the idea is to intercept a test failure and stop the browser. It is not an easy task and it needs some research. Jest does not provide any API to intercept a test failure, so we have to hack it.
Maybe Jest team could help us to achieve that? @SimenB
#43 could also help to find a solution for this.

Jest does not provide any API to intercept a test failure, so we have to hack it.

What do you mean? Right now we just throw (unless you use done callback), so you could just replace test with your own function with built in try-catch I think?
Or do you want us to have a function on e.g. testEnvironment's where it can intercept errors and either forward or swallow them?

I think it would be better to be able to intercept an error in the test environment. I don’t want to invent another method than « it » and « test ». I could patch them but if every Jest plugin do it, it will become a jungle.
So your advice for now is to patch « it » and « test »?

For now, yeah. You can open up a feature request with jest if you want, but I'm not sure if it'll be accepted. Some examples of the API you envision would be nice :)

I've tried to wrap it with the following function:
global.makeSure = (description, func) => {   return it(description, async () => {     try {       await func();     } catch (e) {       console.log(page);       await page.screenshot({ path: screenshot.png });     }   }); };
The page object is accessible but I'm unable to take a screenshot. Does that mean puppeteer is shut down at this point?

// jest.setup.js
global.it = async function(name, func) {
return await test(name, async () => {
try {
await func();
} catch (e) {
await fs.ensureDir('e2e/screenshots');
await page.screenshot({ path: e2e/screenshots/${name}.png });
throw e;
}
});
};

We got an traction on this guys?

// jest.setup.js

global.it = async function(name, func) {
  return await test(name, async () => {
    try {
      await func();
    } catch (e) {
      await fs.ensureDir('e2e/screenshots');
      await page.screenshot({ path: `e2e/screenshots/${name}.png` });
      throw e;
    }
  });
};

for typescript users:
// jest.setup.ts

declare global {
  namespace NodeJS {
    interface Global {
      it: (name: any, func: any) => Promise<void>;
    }
  }
}

global.it = async function(name, func) {
  return await test(name, async () => {
    try {
      await func();
    } catch (e) {
      await ensureDir("screenshots");
      await page.screenshot({ path: `screenshots/${name}.png` });
      throw e;
    }
  });
};

That works perfectly fine, the only question I have, after I start using that function for screenshots generation, i can't use it.only in tests, getting error it.only is not a function. Maybe someone knows what's wrong?

That works perfectly fine, the only question I have, after I start using that function for screenshots generation, i can't use it.only in tests, getting error it.only is not a function. Maybe someone knows what's wrong? I'm using Jest

I suppose it is not chaining methods. Try this https://stackoverflow.com/questions/44446626/run-only-one-test-with-jest

25.3.0 includes https://github.com/facebook/jest/pull/9397 which should unblock both this and #131 without hacks

@SimenB is there a solution for this problem as of today? I understand Jest now provides the necessary functionalities but I don't understand if jest-puppeteer makes use of them.

@Mahanchello you can do the following instead
global.it = Object.assign(async (name, func, timeout) => {
    return await test(name, async () => {
        try {
            await func();
        } catch (e) {
            if (page) {
                try {
                    await page.screenshot({path: `screenshots/${name}.png`});
                } catch (e) {
                    console.error(e)
                }
            }
            throw e;
        }
    }, timeout);
}, test)

@sjurgis what if page is closed at that time? How can we get the screenshot?

I guess not. Only wanted to try this solution because I was reluctant to try jest-circus.
I've now switched to it and it's much easier and works better (we're actually using Playwright, not Pupeteer). It was as easy as adding testEnvironment: "./jest.environment.js", to our jest.config.js and then
const PlaywrightEnvironment = require('jest-playwright-preset/lib/PlaywrightEnvironment').default

class CustomEnvironment extends PlaywrightEnvironment {
    async handleTestEvent(event) {
        if (event.name === 'test_done' && event.test.errors.length > 0) {
            const parentName = event.test.parent.name.replace(/\W/g, '-')
            const specName = event.test.name.replace(/\W/g, '-')
            try {
                const url = this.global.page.url()
                if (this.global.page && url && url !== 'about:blank') {
                    await this.global.page.screenshot({
                        path: `screenshots/${parentName}_${specName}.png`,
                    })
                }
            } catch (e) {
                console.error(e)
            }
        }
    }
}

module.exports = CustomEnvironment

Why not simply use a very long timer to prevent the browser from closing?

It will not happen. But we will take a screenshot.


Branch1

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

Docs Build status updates of commit 78a57e4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/docfx.json
:white_check_mark:Succeeded

articles/docfx.json
:white_check_mark:Succeeded

articles/index.md
:white_check_mark:Succeeded
View (qsharp-preview)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off

Docs Build status updates of commit e301a2e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/docfx.json
:white_check_mark:Succeeded

articles/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@natke

You can see quantum in this list under ms.prod + ms.technology.
https://docsmetadatatool.azurewebsites.net/allowlists


Support multiple adjustments on the same model instance with {% adjust_bulk %}

Right now, {% adjust_bulk %} lets you do an optimized adjustment of a bunch of (say) image fields for a queryset. But you can only do one adjustment per item in the iterable. That's a problem; often you'll have two fields that need to be adjusted, or one field that needs to be adjusted in two different ways. We should support that.

Specifically the issue here is that you might be looping over one iterable but want to have multiple images rendered for each item in the iterable - say, different sizes depending on window size or device resolution.


UUF: full tutorial on Blazor and EF

Description
RElated issue: #33278
Please! Do a tutorial from scratch like https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-cli-tutorial/installI want to learn how to implement EF Core in a fresh project, and not by cloning a sample repository. Just use the https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-cli-tutorial tutorial and extend it by adding a database. Thanks!
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/blazor-ef-core?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/blazor-ef-core.md
Document ID
2ebc5e4d-bab4-6d30-9018-9a712c482236
Article author
@guardrex

Already covered by https://github.com/dotnet/AspNetCore.Docs/issues/32359.


Possible memory leak on KDE neon 5.19 (Ubuntu 18.04.4)

Host system is KDE neon 5.19 which is based on Ubuntu 18.04.4.
Running procmon with no arguments results in procman running but constantly consuming memory until there is none left.
Steps to repo:

Download + Install procmon
Launch procman like so sudo procmon
Which memory consumption ever-increasing

The number of "Total Events:" never stops increasing which makes me wonder if there's some sort of recursion or loop that is incorrectly calculating the number of events.

If you don't specify any arguments, procmon will trace all the syscalls it knows about: https://github.com/microsoft/ProcMon-for-Linux/blob/ad86920331dda3315538ab0ee30fb24727aff82d/src/configuration/procmon_configuration.cpp#L146-L153
I'm pretty sure what you're seeing is the in memory database growing as events are saved.

How fast is the memory growing? Say, every 5 seconds it grows by X MB?

It looks like it collects around 2500 events every 1 second and grabs about 100MB of memory every 1 second.
lscpu snippet:
Model name:          AMD FX(tm)-8350 Eight-Core Processor
CPU(s):                    8
Core(s) per socket:  4
Thread(s) per core:  2

A small increase is to be expected as events are collected. I'm not, however, able to reproduce the large increase you are seeing.

I let it run for about 4 minutes and it is up to 2,000,000 total events and 8000mb used, and still increasing. Luckily, the moment I ctrl-c, it closes and returns all of the memory.

What does htop show for memory consumption (specifically for procmon)?

Just to be sure, this is Ubuntu 18.04 correct?

It is KDE neon 5.19 which is functionally the same as Kubuntu 18.04.
lsb_release -a
Distributor ID: neon
Description:    KDE neon User Edition 5.19
Release:        18.04
Codename:       bionic

uname -a
Linux egee-workstation 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

There is likely some difference in behavior between the distros. While the preview release is focused on Ubuntu 18.04 we will definitely have to take a closer look at this as we move forward. Thanks for reporting it!

Hello, there is the log under KDE Neon 5.19:
Xarkam@HYKSOS  ~/Téléchargements  uname -a
Linux HYKSOS 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

xarkam@HYKSOS  ~/Téléchargements  sudo procmon
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:26:
In file included from include/linux/irqflags.h:16:
In file included from ./arch/x86/include/asm/irqflags.h:9:
In file included from ./arch/x86/include/asm/nospec-branch.h:314:
./arch/x86/include/asm/segment.h:266:2: error: expected '(' after 'asm'
        alternative_io ("lsl %[seg],%[p]",
        ^
./arch/x86/include/asm/alternative.h:240:2: note: expanded from macro 'alternative_io'
        asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature)   \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
In file included from include/linux/thread_info.h:38:
In file included from ./arch/x86/include/asm/thread_info.h:12:
In file included from ./arch/x86/include/asm/page.h:12:
./arch/x86/include/asm/page_64.h:49:2: error: expected '(' after 'asm'
        alternative_call_2(clear_page_orig,
        ^
./arch/x86/include/asm/alternative.h:256:2: note: expanded from macro 'alternative_call_2'
        asm_inline volatile (ALTERNATIVE_2("call %P[old]", "call %P[new1]", feature1,\
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
In file included from include/linux/thread_info.h:38:
In file included from ./arch/x86/include/asm/thread_info.h:53:
In file included from ./arch/x86/include/asm/cpufeature.h:5:
In file included from ./arch/x86/include/asm/processor.h:24:
./arch/x86/include/asm/special_insns.h:205:2: error: expected '(' after 'asm'
        alternative_io(".byte " __stringify(NOP_DS_PREFIX) "; clflush %P0",
        ^
./arch/x86/include/asm/alternative.h:240:2: note: expanded from macro 'alternative_io'
        asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature)   \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
In file included from include/linux/thread_info.h:38:
In file included from ./arch/x86/include/asm/thread_info.h:53:
In file included from ./arch/x86/include/asm/cpufeature.h:5:
./arch/x86/include/asm/processor.h:795:2: error: expected '(' after 'asm'
        alternative_input(BASE_PREFETCH, "prefetchnta %P1",
        ^
./arch/x86/include/asm/alternative.h:221:2: note: expanded from macro 'alternative_input'
        asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature)   \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
In file included from include/linux/thread_info.h:38:
In file included from ./arch/x86/include/asm/thread_info.h:53:
In file included from ./arch/x86/include/asm/cpufeature.h:5:
./arch/x86/include/asm/processor.h:807:2: error: expected '(' after 'asm'
        alternative_input(BASE_PREFETCH, "prefetchw %P1",
        ^
./arch/x86/include/asm/alternative.h:221:2: note: expanded from macro 'alternative_input'
        asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature)   \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
include/linux/thread_info.h:134:2: error: expected '(' after 'asm'
        WARN(1, "Buffer overflow detected (%d < %lu)!\n", size, count);
        ^
include/asm-generic/bug.h:124:3: note: expanded from macro 'WARN'
                __WARN_printf(TAINT_WARN, format);                      \
                ^
include/asm-generic/bug.h:93:3: note: expanded from macro '__WARN_printf'
                __WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
In file included from include/linux/rcupdate.h:27:
In file included from include/linux/preempt.h:78:
In file included from ./arch/x86/include/asm/preempt.h:7:
include/linux/thread_info.h:150:6: error: expected '(' after 'asm'
        if (WARN_ON_ONCE(bytes > INT_MAX))
            ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:21:
In file included from include/linux/dcache.h:7:
In file included from include/linux/rculist.h:11:
include/linux/rcupdate.h:893:2: error: expected '(' after 'asm'
        WARN_ON_ONCE(func != (rcu_callback_t)~0L);
        ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
In file included from include/linux/xarray.h:14:
In file included from include/linux/gfp.h:6:
In file included from include/linux/mmzone.h:21:
In file included from include/linux/mm_types.h:14:
In file included from include/linux/uprobes.h:49:
In file included from ./arch/x86/include/asm/uprobes.h:13:
In file included from include/linux/notifier.h:16:
In file included from include/linux/srcu.h:21:
In file included from include/linux/workqueue.h:9:
In file included from include/linux/timer.h:6:
include/linux/ktime.h:171:2: error: expected '(' after 'asm'
        WARN_ON(div < 0);
        ^
include/asm-generic/bug.h:115:3: note: expanded from macro 'WARN_ON'
                __WARN();                                               \
                ^
include/asm-generic/bug.h:90:19: note: expanded from macro '__WARN'
#define __WARN()                __WARN_FLAGS(BUGFLAG_TAINT(TAINT_WARN))
                                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
In file included from include/linux/xarray.h:14:
In file included from include/linux/gfp.h:6:
In file included from include/linux/mmzone.h:21:
In file included from include/linux/mm_types.h:14:
In file included from include/linux/uprobes.h:49:
In file included from ./arch/x86/include/asm/uprobes.h:13:
In file included from include/linux/notifier.h:16:
include/linux/srcu.h:179:2: error: expected '(' after 'asm'
        WARN_ON_ONCE(idx & ~0x1);
        ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
In file included from include/linux/xarray.h:14:
In file included from include/linux/gfp.h:6:
In file included from include/linux/mmzone.h:22:
include/linux/page-flags.h:565:2: error: expected '(' after 'asm'
        BUG_ON(!PageHead(page));
        ^
include/asm-generic/bug.h:62:57: note: expanded from macro 'BUG_ON'
#define BUG_ON(condition) do { if (unlikely(condition)) BUG(); } while (0)
                                                        ^
./arch/x86/include/asm/bug.h:73:2: note: expanded from macro 'BUG'
        _BUG_FLAGS(ASM_UD2, 0);                                 \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
In file included from include/linux/xarray.h:14:
In file included from include/linux/gfp.h:6:
In file included from include/linux/mmzone.h:971:
In file included from ./arch/x86/include/asm/mmzone.h:5:
In file included from ./arch/x86/include/asm/mmzone_64.h:11:
In file included from ./arch/x86/include/asm/smp.h:13:
In file included from ./arch/x86/include/asm/apic.h:11:
In file included from ./arch/x86/include/asm/fixmap.h:190:
include/asm-generic/fixmap.h:38:2: error: expected '(' after 'asm'
        BUG_ON(vaddr >= FIXADDR_TOP || vaddr < FIXADDR_START);
        ^
include/asm-generic/bug.h:62:57: note: expanded from macro 'BUG_ON'
#define BUG_ON(condition) do { if (unlikely(condition)) BUG(); } while (0)
                                                        ^
./arch/x86/include/asm/bug.h:73:2: note: expanded from macro 'BUG'
        _BUG_FLAGS(ASM_UD2, 0);                                 \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
In file included from include/linux/xarray.h:14:
In file included from include/linux/gfp.h:6:
In file included from include/linux/mmzone.h:971:
In file included from ./arch/x86/include/asm/mmzone.h:5:
In file included from ./arch/x86/include/asm/mmzone_64.h:11:
In file included from ./arch/x86/include/asm/smp.h:13:
./arch/x86/include/asm/apic.h:107:2: error: expected '(' after 'asm'
        alternative_io("movl %0, %P1", "xchgl %0, %P1", X86_BUG_11AP,
        ^
./arch/x86/include/asm/alternative.h:240:2: note: expanded from macro 'alternative_io'
        asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature)   \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:15:
In file included from include/linux/radix-tree.h:18:
include/linux/xarray.h:54:2: error: expected '(' after 'asm'
        WARN_ON((long)v < 0);
        ^
include/asm-generic/bug.h:115:3: note: expanded from macro 'WARN_ON'
                __WARN();                                               \
                ^
include/asm-generic/bug.h:90:19: note: expanded from macro '__WARN'
#define __WARN()                __WARN_FLAGS(BUGFLAG_TAINT(TAINT_WARN))
                                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:39:
In file included from include/linux/ioprio.h:7:
include/linux/iocontext.h:132:2: error: expected '(' after 'asm'
        WARN_ON_ONCE(atomic_long_read(&ioc->refcount) <= 0);
        ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:39:
In file included from include/linux/ioprio.h:7:
include/linux/iocontext.h:133:2: error: expected '(' after 'asm'
        WARN_ON_ONCE(atomic_read(&ioc->active_ref) <= 0);
        ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:39:
In file included from include/linux/ioprio.h:7:
include/linux/iocontext.h:142:2: error: expected '(' after 'asm'
        WARN_ON_ONCE(atomic_read(&ioc->nr_tasks) <= 0);
        ^
include/asm-generic/bug.h:98:3: note: expanded from macro 'WARN_ON_ONCE'
                __WARN_FLAGS(BUGFLAG_ONCE |                     \
                ^
./arch/x86/include/asm/bug.h:79:2: note: expanded from macro '__WARN_FLAGS'
        _BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags));           \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:245:
include/linux/quota.h:114:3: error: expected '(' after 'asm'
                BUG();
                ^
./arch/x86/include/asm/bug.h:73:2: note: expanded from macro 'BUG'
        _BUG_FLAGS(ASM_UD2, 0);                                 \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
In file included from /virtual/main.c:23:
In file included from include/linux/fdtable.h:16:
In file included from include/linux/fs.h:245:
include/linux/quota.h:141:3: error: expected '(' after 'asm'
                BUG();
                ^
./arch/x86/include/asm/bug.h:73:2: note: expanded from macro 'BUG'
        _BUG_FLAGS(ASM_UD2, 0);                                 \
        ^
./arch/x86/include/asm/bug.h:35:2: note: expanded from macro '_BUG_FLAGS'
        asm_inline volatile("1:\t" ins "\n"                             \
        ^
include/linux/compiler_types.h:210:24: note: expanded from macro 'asm_inline'
#define asm_inline asm __inline
                       ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.

Hello @Xarkam , you are using kernel 5.4, Procmon preview release only works with kernels >=4.18 and <=5.3 so, for now, the behaviour is expected.

As part of our work to enable more distros, we will support a larger number of distros/kernel versions. This work should be coming in the next few months.


Fix polygon offset check for shadows

Yeah...
I think the Chrome 49->50 switch happened right before I introduced this bug so I never noticed that I had accidentally turned polygon offset off.
Now shadow aliasing should be reduced in Firefox. However glPolygonOffset still seems to have almost no effect in Chrome which I opened an issue for here: https://groups.google.com/forum/#!topic/webgl-dev-list/E1dAG65QBhg. Shadowing in Chrome works fine now in version 49 or when ANGLE is disabled in the current version.

Update CHANGES. Do we want this for tomorrow's release? Seems like an obvious fix.

Updated. Yes this ought to go in.

Thanks.


Firewall with support of JWT and Digest authentication

I would like to be able to configure a Firewall on route /api which allow authentication by JWT and Digest Authentication (a bit like in that example: https://symfony.com/doc/current/security/multiple_user_providers.html).
When I define the Firewall like this I got an error: Type error: Argument 4 passed to Symfony\Component\Security\Http\Firewall\DigestAuthenticationListener::__construct() must be an instance of Symfony\Component\Security\Http\EntryPoint\DigestAuthenticationEntryPoint, instance of Lexik\Bundle\JWTAuthenticationBundle\Security\Guard\JWTTokenAuthenticator given
firewalls:
   api:
            pattern:   ^/api
            stateless: true
            provider: jwt_provider
            http_digest:
                provider: in_memory
                realm:    "Secured Demo API"
                secret:   "SECRET"
            guard:
                authenticators:
                    - lexik_jwt_authentication.jwt_token_authenticator

Do you know if this use case could be supported?

Hi. I can't reproduce your issue. Could you provide your full security.yml (replacing sensitive data by dummies if any)?

Yes for sure:
security:

    encoders:
        AppBundle\Entity\User:
            algorithm:        sha512
            encode_as_base64: true
            iterations:       5000

        Symfony\Component\Security\Core\User\User:
            algorithm:  sha1
            iterations: 1
            encode_as_base64: false

    role_hierarchy:
        ROLE_ADMIN:       ROLE_USER
        ROLE_SUPER_ADMIN: [ROLE_USER, ROLE_ADMIN]

    providers:
        default:
            id: app.repository.user
        in_memory:
            memory:
                users:
                    - { name: "USERNAME", password: "PASSWORD", roles: 'ROLE_SUPER_ADMIN' }
        chain_provider:
            chain:
                providers: [in_memory, default]

    firewalls:
        # disables authentication for assets and the profiler, adapt it according to your needs
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false

        #main:
            #anonymous: ~
            # activate different ways to authenticate

            #http_basic: ~
            # http://symfony.com/doc/current/book/security.html#a-configuring-how-your-users-will-authenticate

            # form_login: ~
            # http://symfony.com/doc/current/cookbook/security/form_login_setup.html

        api_login:
            pattern:  ^/api/login
            stateless: true
            anonymous: true
            provider: default
            form_login:
                check_path:               /api/login_check
                success_handler:          lexik_jwt_authentication.handler.authentication_success
                failure_handler:          lexik_jwt_authentication.handler.authentication_failure
                require_previous_session: false

        api:
            pattern:   ^/api
            stateless: true
            http_digest:
                provider: in_memory
                realm:    "Secured Demo API"
                secret:   "SECRET"
            guard:
                provider: default
                authenticators:
                    - lexik_jwt_authentication.jwt_token_authenticator

    access_control:
        - { path: ^/api, roles: IS_AUTHENTICATED_FULLY }
        - { path: ^/api/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/api/brands, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/categories, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/colors, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/countries, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/infractions, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/localities, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/places, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
        - { path: ^/api/place_details, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST,

Note that:

when I remove guard I can authenticate with Digest Authentication.
when I remove http_digest I can authenticate with JWT Authentication.

But when both are present I have the issue.

Could you please paste the full error stack trace?

FatalThrowableError
Type error: Argument 4 passed to Symfony\Component\Security\Http\Firewall\DigestAuthenticationListener::__construct() must be an instance of Symfony\Component\Security\Http\EntryPoint\DigestAuthenticationEntryPoint, instance of Lexik\Bundle\JWTAuthenticationBundle\Security\Guard\JWTTokenAuthenticator given, called in /home/lallement/workspace-vdl/avtax-api-platform/var/cache/dev/appDevDebugProjectContainer.php on line 2735
in DigestAuthenticationListener.php (line 40)
at DigestAuthenticationListener->__construct(object(TokenStorage), object(InMemoryUserProvider), 'api', object(JWTTokenAuthenticator), object(Logger))in appDevDebugProjectContainer.php (line 2735)
at appDevDebugProjectContainer->getSecurity_Firewall_Map_Context_ApiService()in Container.php (line 335)
at Container->get('security.firewall.map.context.api')in appDevDebugProjectContainer.php (line 4336)
at appDevDebugProjectContainer->{closure}()in ServiceLocator.php (line 57)
at ServiceLocator->get('security.firewall.map.context.api')in FirewallMap.php (line 165)
at _FirewallMap->getFirewallContext(object(Request))in FirewallMap.php (line 136)
at _FirewallMap->getFirewallConfig(object(Request))in FirewallListener.php (line 44)
at FirewallListener->onKernelRequest(object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))
at call_user_func(array(object(FirewallListener), 'onKernelRequest'), object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))in WrappedListener.php (line 104)
at WrappedListener->__invoke(object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))
at call_user_func(object(WrappedListener), object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))in EventDispatcher.php (line 212)
at EventDispatcher->doDispatch(array(object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener)), 'kernel.request', object(GetResponseEvent))in EventDispatcher.php (line 44)
at EventDispatcher->dispatch('kernel.request', object(GetResponseEvent))in TraceableEventDispatcher.php (line 146)
at TraceableEventDispatcher->dispatch('kernel.request', object(GetResponseEvent))in HttpKernel.php (line 129)
at HttpKernel->handleRaw(object(Request), 1)in HttpKernel.php (line 68)
at HttpKernel->handle(object(Request), 1, true)in Kernel.php (line 171)
at Kernel->handle(object(Request))in app_dev.php (line 31)

i think you got to put multiple_user_providers
see this https://symfony.com/doc/current/security/multiple_user_providers.html

The problem comes from the fact $defaultEntryPoint is set to security.authentication.provider.jwt.api  in JWTFactory.
In HttpDigestFactory::createEntryPoint, if $defaultEntryPoint is not null this entry_point is used.
If I comment the following lines in HttpDigestFactory::createEntryPoint it works as expected:
protected function createEntryPoint($container, $id, $config, $defaultEntryPoint)
    {
        /*if (null !== $defaultEntryPoint) {
            return $defaultEntryPoint;
        }*/

        $entryPointId = 'security.authentication.digest_entry_point.'.$id;
        $container
            ->setDefinition($entryPointId, new ChildDefinition('security.authentication.digest_entry_point'))
            ->addArgument($config['realm'])
            ->addArgument($config['secret'])
        ;

        return $entryPointId;
    }

I can't reproduce your issue, your configuration runs fine on my side. It feels like a cache issue.
Did you clear your cache (by hand rm -rf var/cache/*)?
If it doesn't help, please tell me your symfony version.

JWTFactory should not be called at all here (it has been deprecated and is wired only if you have lexik_jwt: ~ as key in your firewall). Which version of the bundle are you using?

I use the last stable (from my composer.lock):
"name": "lexik/jwt-authentication-bundle",
"version": "v2.4.1",

Ok I'm able to reproduce the problem, I expected the exception to occur earlier (at compile time, while it occurs only when actually hitting a route that matches the JWT/Digest firewall).
It looks like a symfony bug but I need to confirm that, fortunately I'm maintainer on the symfony security component and bundle.
I will look into this evening and come back.

Thank you very much, it's greatly appreciated.

@chalasr Do you had time to check what is wrong here? I seen you implemented a PR in Symfony to improve exception when an undefined user provider is used inside a firewall (https://github.com/symfony/symfony/pull/24114). Is it directly related to this issue?

It is not related. I looked at this, and there is indeed a bug in symfony/symfony. We need to not use the default provider if it is not an instance of DigestAuthenticationEntryPoint, I'm going to propose a fix today. Keep you informed there.

Thanks!

@chalasr I created a PR in Symfony to fix this issue.

Please see https://github.com/symfony/symfony/issues/10035#issuecomment-329452067

@chalasr I tried with your tip. The Digest authentication works but I always encounter a 401 when trying to authenticate by JWT.
# To get started with security, check out the documentation:
# http://symfony.com/doc/current/book/security.html
security:

    encoders:
        AppBundle\Entity\User:
            algorithm:        md5
            encode_as_base64: false
            iterations:       1

        # For Digest Authentication
        Symfony\Component\Security\Core\User\User:
            algorithm:  sha512
            iterations: 5000
            encode_as_base64: true

    role_hierarchy:
        ROLE_ADMIN:       ROLE_USER
        ROLE_SUPER_ADMIN: [ROLE_USER, ROLE_ADMIN]

    # http://symfony.com/doc/current/book/security.html#where-do-users-come-from-user-providers
    providers:
        default:
            id: app.repository.user
        in_memory:
            memory:
                users:
                    - { name: "USERNAME", password: "ASSWORD", roles: 'ROLE_SUPER_ADMIN' }

    firewalls:
        # disables authentication for assets and the profiler, adapt it according to your needs
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false

        main:
            pattern:   ^/
            entry_point: app.digest_entry_point
            http_basic: ~
            http_digest:
                provider: in_memory
                realm:    "%app.digest_realm%"
                secret:   "%kernel.secret%"

        api_login:
            pattern:  ^/api/login
            stateless: true
            anonymous: true
            provider: default
            form_login:
                check_path:               /api/login_check
                success_handler:          lexik_jwt_authentication.handler.authentication_success
                failure_handler:          lexik_jwt_authentication.handler.authentication_failure
                require_previous_session: false

        api:
            pattern:   ^/api
            stateless: true
            #http_digest:
            #    provider: in_memory
            #    realm:    "Secured Demo API"
            #    secret:   "qDFV5axHjhu56458RAFxs66geRt"
            guard:
                provider: default
                authenticators:
                    - lexik_jwt_authentication.jwt_token_authenticator

    access_control:
        - { path: ^/api, roles: IS_AUTHENTICATED_FULLY }
        - { path: ^/api/login, roles: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/api/brands, roles: [ROLE_SUPER_ADMIN, ROLE_ADMIN], methods: [POST, PUT, DELETE] }
...

Perfect! Thanks for reporting this


Fix TestUnicodeConversion on big endian machines

Wide character literals are stored in native byte order.
Use an array of bytes as a reference instead.
Fixes: https://github.com/FreeRDP/FreeRDP/issues/6968

@floppym thank you.


bridge: node sends out huge number of 'dropping message to peer 12D3XXXX: queue full'

Celestia Node version
v0.8.0
OS
ubuntu 20.04, 22.04
Install tools
source install with default makefile.
Others
no change with all defaults.
Steps to reproduce it
run node as usual, wait maybe 1 day.
Expected result
Don't see too much spam messages in log.
Actual result
hundreds of  message like 'celestia[344985]: 2023-03-31T15:23:53.187+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWGHqdPFz6e3D5Miwh5vrDv5TvF4JQW6iiYUA8VibJQCpF: queue full' per new block.
Relevant log output
Mar 31 15:23:53 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:23:53.186+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWJf5C2hmCTAkVFFeYsMFfydE4AkPkdA47bZBfAm6KxeW5: queue full
Mar 31 15:23:53 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:23:53.186+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWNML73KwmzF71zHc3VjdhrwLoA3PexC63t8Kbc1ekJ7RN: queue full
Mar 31 15:23:53 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:23:53.187+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWKa3xiNNf71V73L6Z9tEEC9gdGhaAKrvK3pK2tSYv1Rnn: queue full
Mar 31 15:23:53 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:23:53.187+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWJqhvFkPKNHwmdbaVCVEM2ReNhTWCvStLGKqvFKWjzkHv: queue full
Mar 31 15:23:53 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:23:53.187+0800        INFO        pubsub        go-libp2p-pubsub@v0.9.3/floodsub.go:95        dropping message to peer 12D3KooWGHqdPFz6e3D5Miwh5vrDv5TvF4JQW6iiYUA8VibJQCpF: queue full
Mar 31 15:24:01 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:24:01.041+0800        INFO        header/store        store/store.go:353        new head        {"height": 134016, "hash": "66B3B9AD473574ECDD9058B76BD2C1DA29935640C7EF0CD52A0259256BBFD12E"}
Mar 31 15:24:11 vmi1095034.contaboserver.net celestia[344985]: 2023-03-31T15:24:11.712+0800        INFO        header/store        store/store.go:353        new head        {"height": 134017, "hash": "30516AB385173D4886C82438EF8F0FE795EF763EF3F80B88B6BCC54909B40A0B"}

Notes
I'm not sure this is just some spam message or here is a real bug, because I don't see a heavy load from my host. the established connections is low too. The node seems refused every connections. Simply suppress this message may not be safe.
I checked the code, this message seems come from the inner side of the pubsub module, I see it is used a lot in the code (at least 20 relative files), It's too difficult for me to locate the source of this problem, then we may need somebody who is more familiar with this module and the workflow of node than me to evaluate this issue. Or someone may give me any direction then I will try to evaluate it again.

Thank you @HoytRen


Remove std feature gate from crypto/merkle.rs

          please look into `crypto/merkle.rs`. I think it doesn't have to be `std` feature gated anymore

Originally posted by @mversic in https://github.com/hyperledger/iroha/pull/4181#pullrequestreview-1848254084

Done by #4181


Hash modifier with hexadecimal format

Hi,
Following format string outputs "0x01" when it should output "0x1001".
uint16_t val = 0x1001;
printf("%#04x", val);

I fixed this in my branch (avr-progmem), commit d85de16af01808f4bde231614f05b7cc65cc7d26
Around line 430, I had to remove:
if (!(flags & FLAGS_PRECISION) && len && ((len == prec) || (len == width))) {
len--;
if (len && (base == 16U)) {
len--;
}
}
It's because 0x adds 2 characters to the length.
It's probably also fixed in other pull requests here.

@mickjc750 : You'd be surprised; for PR's have addressed this issue. But - I'm working on it for my own fork (which aims to be general, not specific to "avr-progrmem", and incorporate the various fixes suggested over the past few years here).

... plus - just removing this results in test case failures. Have you verified all those test case checks are invalid?

Oh, I should also note this problem manifests with the %o specifier as well:
printf_("%#04o", 01001);

should produce 01001, but produces 0001.

... plus - just removing this results in test case failures. Have you verified all those test case checks are invalid?

It didn't break any test cases. At least none that existed at the time.

It didn't break any test cases. At least none that existed at the time.

Ok, but... it breaks the "padding #020" test case on the master branch of this repository.

It didn't break any test cases. At least none that existed at the time.

Ok, but... it breaks the "padding #20" test case on the master branch of this repository.

Ugh.. So it does. In fact 0 padding is broken in my fork (it over pads by 2 0's).
Looks like I will need to dissect these flag acrobatics and fix it. Thankyou!

@mickjc750 : I want to make a suggestion. There's been a lot repeated work that different people have done over what's currently in this repository; and I've been trying to integrate it on my fork (seeing how mpaland has been inactive for two years; though this might change). Now, I realize your repository has a specific scope that's different from the general one(s) - but I still assume it should be useful to you to be able to base it off an up-to-date and responsive general repository, so that your changes remain shallower. If that's indeed the case, please consider trying to do that on the general repository, and possibly coordinating that work with me (or my fork...) so that our efforts don't diverge so much.

@mickjc750 : Both 0 padding and this issue are now fixed on my fork.

Awesome. I think I should rebase my fork from yours, thanks!
On Sat, Jul 31, 2021 at 1:13 AM Eyal Rozenberg @.***>
wrote:

@mickjc750 https://github.com/mickjc750 : Both 0 padding and this issue
are now fixed on my fork.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mpaland/printf/issues/99#issuecomment-889960015, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJ2OLICFF2J7NMH5KOAJ6LT2K6THANCNFSM42UNXPUQ
.

--
Michael Clift - Design Engineer.
Clift Innovations Pty Ltd
Suit 10/13 Walkers Road
Nunawading, VIC 3131
ABN 24 286188328
Tel: +61 3 9877 3109
Fax: +61 3 9999 1406
Mob: 0417 613 680
Email: @.***
Web: www.clift.com.au

PRIVATE AND CONFIDENTIAL
This e-mail and any files transmitted with it are intended solely for the
use of the addressee(s) and may contain information that is confidential or
privileged. If you receive this e-mail and you are not the addressee(s),
please disregard the contents of the e-mail, delete the e-mail and notify
the author immediately.

@mickjc750 : In that case, please try to separate your changes into universal ones, not specific to your target platform, which I could consider for my fork, and the purely AVR-specific changes. Perhaps even use separate branches for them.