Auth0 API login says my account has been blocked (even though it hasn't) when trying to log in

Checklist

[X] The issue can be reproduced in the auth0_flutter sample app (or N/A).
[X] I have looked into the README and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
When trying to log in with username/password flow with the following code:
    final credentials = await auth0.api.login(       audience: Environment.auth0Audience,         usernameOrEmail: '**********',         password: '********',         connectionOrRealm: 'Username-Password-Authentication');
I get the following error message:
Unhandled Exception: too_many_attempts: Your account has been blocked after multiple consecutive login attempts. We've sent you an email with instructions on how to unblock it.
which I believe is invalid, because I got no email and I can still login with that account using the web authentication:
      final credentials = await auth0.webAuthentication().login(audience: Environment.auth0Audience, useEphemeralSession: true,           redirectUrl: Environment.auth0RedirectUri);
I think the error code is wrong, and if it's not, it's quite misleading.
Full error trace:
[VERBOSE-2:ui_dart_state.cc(198)] Unhandled Exception: too_many_attempts: Your account has been blocked after multiple consecutive login attempts. We've sent you an email with instructions on how to unblock it. #0      MethodChannelAuth0FlutterAuth.invokeRequest (package:auth0_flutter_platform_interface/src/method_channel_auth0_flutter_auth.dart:79:7) <asynchronous suspension> #1      MethodChannelAuth0FlutterAuth.login (package:auth0_flutter_platform_interface/src/method_channel_auth0_flutter_auth.dart:27:9) <asynchronous suspension> #2      AppAuthService.signIn (package:mer_connect_app/state/auth_state_provider.dart:82:25) <asynchronous suspension>
Reproduction

Set up auth0 client: Auth0 auth0 =  auth0 =  Auth0('domain', clientId);
Try loggin in with     final credentials = await auth0.api.login(    audience: Environment.auth0Audience,      usernameOrEmail: '**********',      password: '********',      connectionOrRealm: 'Username-Password-Authentication');
See error Unhandled Exception: too_many_attempts: Your account has been blocked after multiple consecutive login attempts. We've sent you an email with instructions on how to unblock it.

auth0_flutter version
1.0.0
Flutter version
3.0.5
Platform
iOS
Platform version(s)
15.6.1

Edit:
Tried with a different connectionOrRealm and it worked. The error message I received wasn't very clear though.


Does DoWhy have a function to validate a causal graph?

I am looking for a function that will take a causal graph (.gml) and dataframe, and will return a binary output whether the data confirms the supplied graph or not. For example if the graph says there's a confounder [A]<-[X]->[Y] but the data doesn't show a correlation between A and X, then the result will be false.
Is this supported by DoWhy at the moment? (couldn't find it in any of the docs), if not, any recommendations how to implement this in a methodic way? (want to scan a complete graph, not go manually over each relationship per, direct and in-direct and test it)

Hey @fredthedead that's a great question. No, currently does not support it.
But this would be a great addition as a new refutation method. So given a causal model m, we can refute/test whether the dataset follows constraints from the causal model.
The trick is to find all falsifiable constraints that are entailed by a causal model. One methodic way is to consider all pairs, triplets and so on.  Here's a start:

Enumerate over all pairs (edges) and check for non-zero correlation with a statistical test.
Enumerate all triplets in the graph,  identify its type (path structure, confounder structure, collider structure, etc.) and then check whether the data follows expected correlation and independence constraints.

Pairs and triplets can be extended to quartets and so on. That said,  it is still a heuristic because we leave out longer paths or nodes connected by more than 1-2 edges.
What do you think?

Thanks for your reply @amit-sharma, much appreciated. The approach you describe is what I had in mind and was hoping it might of been implemented. I've started looking at the code a bit to estimate how much time it'll take me to add it, might give it a go next time I have some availability...

@amit-sharma @fredthedead was this implemented?

Not yet unfortunately. Would you like to contribute @mauriciozuardi ?

@amit-sharma I'm still familiarizing with the concepts (of causal analysis) and the code (of the repository), but as soon as I get confident enough I'll give it a try.

Got it. Let me try to start the implementation with something simple and then maybe you can contribute.

Hi all, this is something that I e been looking for as well, and it seems that it would be a commonly used part of the causal analysis process. Any developments on this implementation?

Yes, there is now a causal graph refutation functions that checks the independence constraints.  This notebook includes an example usage (see Step 4):
https://github.com/py-why/dowhy/blob/8fb32a7bf617c1a64a2f8b61ed7a4a50ccaf8d8c/docs/source/example_notebooks/graph_conditional_independence_refuter.ipynb#L239
The documentation needs to be improved to make this easier to find.

You can also take a look at: https://github.com/py-why/dowhy/blob/main/dowhy/gcm/validation.py#L24 and see the very recent discussion in https://github.com/py-why/dowhy/discussions/926. We are actually working on a new method there, hopefully can add this soon.

Quick update regarding the novel refutation method mentioned by @bloebp. In #930 we added a function validate_lmc which tests the implied (conditional) independencies (via local Markov condition [LMC]) on some data (very similar to what @amit-sharma described). Additionally, we added a function falsify_graph to compare the result of this test to a baseline of random node-permutations to find whether the graph is significantly better than random. Here you can find an example notebook that highlights the key ideas and features of this function. We would greatly appreciate any feedback or comments! Please let me know if you have any questions!

Much appreciated! @eeulig


A3 integration test

Finish implementation of a3-highgpu-8g integration test. The underlying challenge of the integration test is that the A3 solution is implemented as 3 blueprints. This test makes the following changes relative to the user experience:

It provisions the NFS server as a simple nfs-server blueprint in the default network alongside the cluster. This simplifies the state dependencies and removes testing dependencies upon Filestore and peering.
It builds the custom image, retaining the image until the cluster deployment is attempted.

Future work will include:

expansion of Slurm job submissions to explicitly test A3 functionality
nightly cleanup of these resources if we find that they are frequently strayed.

Submission Checklist
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cloud HPC Toolkit Contribution guidelines #

@nick-stroud I believe this is ready. The last integration test failed on debug partition due to stockout. I might take advice on switching regions or zones, but this does not reflect a failure of the test per se.
I watched the test and verified that the simple jobs triggered running the special prolog / epilog for A3 nodes. The trigger is any multi-node job.


Any plan on releasing Swift Package Support?

Would make integration easier and far superior vs cocoa pods.

Hi there.
In the future we will certainly integrate Swift Package Manager, but at the moment it does not support some features that are necessary to make the SDK work, for example it does not allow you to add external resources. These limits will disappear in the next versions of the package manager, and it will then be possible to use it for our SDK.

Sorry to re-open this, but Xcode 12.2 has released with an update to SPM, I am not sure if it is now possible to revisit this issue yet? If it is still not possible, what would be the steps to manually integrate since we have moved our projects away from cocoa pods.


Wrap streams to catch errors

This closes #317.
This is the other solution as mentioned in #326  (read that one first).
In this case a new utility function gets created which adds an error event listener to a stream to store that event. Then, if any new event listeners get added at a later point in time that stored event will be sent to the listener callback function just as if it happened at that point in time. This way Node.js buffering a stream and throwing an error before we attach a listener is not an issue. Buffering does not cause an "end" event to be fired early so we don't have to listen to that one in advance.
Similar to the monitor, a warning will be logged if an error event gets triggered but no listener gets added within a certain time.
This function should be called every time a new stream gets created to wrap it. From that point on that stream is "safe". I might have missed some basic streams such as streamifyArray([ 'data' ]) since those should always be safe anyway.
After spending way too much time to test if the logger actually emitted the warning I gave up on that as I have no idea how to correctly mock there to handle that.

After discussion with @joachimvh on the topic of #326 versus #327:

the number of places where streams need to be wrapped (#327) is probably higher than for #326
however, #326 does have a stronger impact on what the code looks like

My proposal is to go for #327, but to explicitly enforce it via TypeScript. That is, all of our interfaces take a GuardedReadable as input instead of Readable, such that wrapping them cannot be forgotten. That way, we always have the guarantee that the streams we are working with behave in the manner of #327.

My proposal is to go for #327, but to explicitly enforce it via TypeScript. That is, all of our interfaces take a GuardedReadable as input instead of Readable, such that wrapping them cannot be forgotten. That way, we always have the guarantee that the streams we are working with behave in the manner of #327.

The one issue currently is that we can't use an interface interface GuardedReadable extends Readable { }. If we use that interface TypeScript is still going to be ok with us passing normal Readable to functions with those parameters as a Readable fulfills the same interface (changing it to an abstract class doens't make a difference). One solution would be to add an arbitrary field to the GuardedReadable interface (which is not in the Readable interface). This would require us to then patch that field into the streams that we wrap though.
Unless someone else knows some TypeScript typing magic to fix this?

Unless someone else knows some TypeScript typing magic to fix this?

Apparently you can do this with enum magic as seen here. This is already an open issue from 2018. Going to look deeper into everything suggested there.

I updated the function (now guardStream) to do everything discussed above. All the other changes are changing interfaces everywhere to now require Guarded<Readable> and to call the function on new streams. It is now required to apply this function everywhere though, even in places where we know it wouldn't be necessary, but no real way around that (unless we start casting but let's not do that).
I could create a utility function perhaps to cover the case of guardStream(arrayifyStream(['data'])) since that is the most common case where it feels a bit overkill.
I also haven't added a trace parameter to the function yet since I first wanted see the response here.


Some experiments on conformer_ctc with modified attention

I am using a modified attention (Conv1dAbs) to replace the original multi-head attention. The modified entails are showed in my codes (conformer.py).  The Conv1dAbs module is showed in conv1d_abs_attention.py. The conv1d_abs_attention.py is modified based on https://github.com/pytorch/pytorch/blob/b08d64202af31e94db76b460c1b54cb3fbf9d05c/torch/nn/modules/conv.py#L174
All the experiments run with librispeech 100h training data based on conformer_ctc recipe.
And I will update the relative results with real time.
-----------------------------------------------------------------------------------------
                     setting                                       |  test-clean (WER) based on ctc-decoding
-----------------------------------------------------------------------------------------
            baseline (with multi-head attention)                   |   7.23
-----------------------------------------------------------------------------------------
linear1(512, 1024), conv1d_abs(1024, 64, 21, 10), linear2(64, 512) |   running

Plan to explore:

[ ] Performance based on different kernel size.
[ ] Performance based on two conv1dabs layers or more.

After doing some changes for the Conv1dAbs (the modified attention module), there are some initial results:
Only use one conv1dabs layer:
----------------------------------------------
kernel size | test-clean(WER%) | test-other(WER%)
----------------------------------------------
      5     |
----------------------------------------------
      11    |   not converge   |  not converge
----------------------------------------------
      17    |   not converge   |  not converge
----------------------------------------------
      21    |        10.54     |    29.02
----------------------------------------------
      27    |       running    |   running
----------------------------------------------

Dan @danpovey , when I training the librispeech (100 hours) based on feedforward+mha+conv1dabs+conv+macaron with kernel_size=31, the ctc_loss seems that it can not converge. The tensorboard log shows as follows:

Please show me the code so I can check.
On Tue, Jan 11, 2022 at 10:28 AM Mingshuang Luo @.***>
wrote:

Dan @danpovey https://github.com/danpovey , when I training the
librispeech (100 hours) based on feedforward+mha+conv1dabs+conv+macaron
with kernel_size=31, the ctc_loss seems that it can not converge. The
tensorboard log shows as follows:
[image: image]
https://user-images.githubusercontent.com/37799481/148870669-97d3290b-10b2-4de9-aa24-7275cb8f92a5.png
—
Reply to this email directly, view it on GitHub
https://github.com/k2-fsa/icefall/pull/148#issuecomment-1009543200, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLO5QMROS2V542J47LHDUVOIWVANCNFSM5J5IP23A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

The modified code shows https://github.com/k2-fsa/icefall/pull/148/commits/99274cbb8f30bff7a23287a502cbb0599255e8a5.

Please show me the code so I can check.
…
On Tue, Jan 11, 2022 at 10:28 AM Mingshuang Luo @.> wrote: Dan @danpovey https://github.com/danpovey , when I training the librispeech (100 hours) based on feedforward+mha+conv1dabs+conv+macaron with kernel_size=31, the ctc_loss seems that it can not converge. The tensorboard log shows as follows: [image: image] https://user-images.githubusercontent.com/37799481/148870669-97d3290b-10b2-4de9-aa24-7275cb8f92a5.png — Reply to this email directly, view it on GitHub <#148 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZFLO5QMROS2V542J47LHDUVOIWVANCNFSM5J5IP23A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.>

The layernorm layer mean value when using pad 1 for modified conv1dabs attention module is as follows (training for 10 epochs):

The result of the layernorm layer mean value when use pad 0 (training for 10 epochs):

OK. In:
src = 0.01*self.linear1(src*0.25)

now try removing the 0.01.

OK, will do it.

OK. In:
src = 0.01*self.linear1(src*0.25)

now try removing the 0.01.

The mean value of layernorm shows as follows when pad 1 without 0.01 weight before exp:

I have the last try for this modified conformer module and have a test for the mean value of layernorm.
In the new version, I change src=self.linear1(src*0.25) to src=self.linear1(src*0.1).
When trained for 15 epochs, the mean value of the layernorm shows as follows:
For encoder.layers.0.layernorm.weight, mean=0.0072962334379553795
For encoder.layers.0.layernorm.bias, mean=0.011188712902367115
For encoder.layers.1.layernorm.weight, mean=0.07447759807109833
For encoder.layers.1.layernorm.bias, mean=0.07214517891407013
For encoder.layers.2.layernorm.weight, mean=0.03586212173104286
For encoder.layers.2.layernorm.bias, mean=0.06976518034934998
For encoder.layers.3.layernorm.weight, mean=0.046055275946855545
For encoder.layers.3.layernorm.bias, mean=0.06139731779694557
For encoder.layers.4.layernorm.weight, mean=0.03832120820879936
For encoder.layers.4.layernorm.bias, mean=0.05394076928496361
For encoder.layers.5.layernorm.weight, mean=0.030041566118597984
For encoder.layers.5.layernorm.bias, mean=0.04935842752456665
For encoder.layers.6.layernorm.weight, mean=0.029694974422454834
For encoder.layers.6.layernorm.bias, mean=0.04677904024720192
For encoder.layers.7.layernorm.weight, mean=0.03506067395210266
For encoder.layers.7.layernorm.bias, mean=0.05236825346946716
For encoder.layers.8.layernorm.weight, mean=0.07589758932590485
For encoder.layers.8.layernorm.bias, mean=0.05215064436197281
For encoder.layers.9.layernorm.weight, mean=0.056298039853572845
For encoder.layers.9.layernorm.bias, mean=0.05461011081933975
For encoder.layers.10.layernorm.weight, mean=0.03979481756687164
For encoder.layers.10.layernorm.bias, mean=0.0660540759563446
For encoder.layers.11.layernorm.weight, mean=0.04926107078790665
For encoder.layers.11.layernorm.bias, mean=0.10245299339294434

As a comparison, there are the results when src=self.linear1(src*0.25) trained for the same epochs:
For encoder.layers.0.layernorm.weight, mean=0.00931955873966217
For encoder.layers.0.layernorm.bias, mean=0.00999502930790186
For encoder.layers.1.layernorm.weight, mean=0.07056383788585663
For encoder.layers.1.layernorm.bias, mean=0.09829900413751602
For encoder.layers.2.layernorm.weight, mean=0.038799967616796494
For encoder.layers.2.layernorm.bias, mean=0.07130247354507446
For encoder.layers.3.layernorm.weight, mean=0.05083261430263519
For encoder.layers.3.layernorm.bias, mean=0.06508266180753708
For encoder.layers.4.layernorm.weight, mean=0.02101621963083744
For encoder.layers.4.layernorm.bias, mean=0.0661473423242569
For encoder.layers.5.layernorm.weight, mean=0.019956035539507866
For encoder.layers.5.layernorm.bias, mean=0.04898737743496895
For encoder.layers.6.layernorm.weight, mean=0.02077903226017952
For encoder.layers.6.layernorm.bias, mean=0.04869864135980606
For encoder.layers.7.layernorm.weight, mean=0.03686948120594025
For encoder.layers.7.layernorm.bias, mean=0.05601784586906433
For encoder.layers.8.layernorm.weight, mean=0.0672810971736908
For encoder.layers.8.layernorm.bias, mean=0.05286660045385361
For encoder.layers.9.layernorm.weight, mean=0.04314831271767616
For encoder.layers.9.layernorm.bias, mean=0.04859684407711029
For encoder.layers.10.layernorm.weight, mean=0.046929847449064255
For encoder.layers.10.layernorm.bias, mean=0.06688806414604187
For encoder.layers.11.layernorm.weight, mean=0.0457349568605423
For encoder.layers.11.layernorm.bias, mean=0.10489862412214279

It seems that the mean value of the layernorm doesn't have an obvious increase.
@danpovey , according to the above results, I think maybe we have to give up this idea. How do you think?

OK, can close this PR.


Added terraform code for anomaly detection

Tests are failing, but it is for code from another guide.


Add Support for Dopamine

Which you mind adding support for all your visualizers for Dopamine :)
https://github.com/digimezzo/Dopamine

@Sleetui Dopamine has not any necessary API to support rainmeter yet. And it's audio play's duty to implement such a support.

We could always go the old Spotify route, does it display the song info in the window title?
But yeah if it has an API that would make making a plugin much better

https://github.com/digimezzo/Dopamine/issues/252 - Here is the issue on the Dopamine repo.

So now, external control is rather stable now though the sample is of C# instead of C++. Maybe it's now the time to take a look into this?

Yeah I'm on it, I'll look into seeing if we can integrate it into the official now playing plugin tonight. If we can not I will make a standalone plugin when I get the time to.

Just to kinda post an update I have been busy on other more important projects and have decided that instead of rolling out a standalone plugin for dopamine it will be part of my merged music plugin. Probably will be a few weeks before I get around to it.

I have started work on my UnifiedNowPlaying plugin. Given the scale of it it will probably 2 weeks before it is beta ready and 3 or 4 before I can have it ready to implement in Monstercat Visualizer if Marco will allow me.

I will close this issue for now until there is a plugin which supports Dopamine.
Please comment down below if there is any progress made!


Adding an "Introduction to regulations" page to help people understand eRegulations

To help people understand eRegulations (especially potential contributors and users), this adds a page with background information about regulations, customized to the needs of people interested in eRegulations. It explains what regulations are, how they change, their structure, and definitions of terms used in eRegulations (and in discussions among contributors).
Original issue filed over here: https://github.com/18F/atf-eregs/issues/195
This could still use more review for accuracy, and suggestions/comments are welcome!

Very nice, @brittag !

Thanks @cmc333333! I added another commit with the following changes based on your comments:

Rearrange and revise “Where regulations are published” to tell a clear story of who does what. I also included that the official annual CFR gets released in four parts throughout the year instead of all on the same day - this is a bit of a weird detail, but I wouldn't want people to get the incorrect mental model that the annual CFR is released in once big update once a year (and then later have to correct their mental model).
Correct “Advanced” to “Advance” in “Advanced Notice of Proposed Rulemaking”, and remove an unnecessary sentence in that section.
Clarify the contents of a Notice of Proposed Rulemaking and a Final Rule.
Better explanation of the numbered titles.
More general descriptions of the components of a regulation.


Manage externalTrafficPolicy through operator

Is your feature request related to a problem? Please describe.
Right ingress gateway service is deployed with externalTrafficPolicy=Cluster and there is no way to change it to 'Local' type in operator config. But externalTrafficPolicy=Local is the only way to retrieve real source IP from the access log.
Describe the solution you'd like to see
I would like to see the following option in the operator config:
  gateways:
    enabled: true
    ingress:
      enabled: true
      externalTrafficPolicy: Local

Describe alternatives you've considered
Right now the only way is to edit svc resource manually using kubectl.

Hi @danil-fomichev,
Sorry for not getting back to this issue earlier, but in the newest release (image: banzaicloud/istio-operator:0.7.1, chart 0.0.61) the feature is available.
Please note that the name of the field is serviceExternalTrafficPolicy, see the PR description for more details.


Fixing local_new_component

This patch fixes problems with local_new such that the allocation of local
components goes through the runtime_support server to facilitate component
factories.

Apparently it all boils down to the fact that local_new circumvents using our factory mechanism for components which can cause for the allocation to happen in a different module than the deallocation. Using the runtime_support object to allocate the component (even for local_new) ensures that the component is created using the factory.

@sithhell this breaks circleci now.

This isn't going to work as proposed ... I am working on a proper fix right now to avoid multiple instances of the heap.


Updated PKGBUILD and added 0001_msysize.patch for 0.8.17

Don't need this. Need run "autoreconf" after patch.

Actually 0000_msysize.patch doesn't work with 0.8.17, it's for 0.8.15 (I guess).

iris package is under development still. Feel free to update patch, but patch need to modify next autotools files: configure.ac, Makefile.am, *.m4(except libtool macroses)


Preprocessor disabled code-section leads to generated MockClass code

Describe the bug
If the C++ ClassToMock header contains code-sections that are disabled by using the C preprocessor idiom #if 0 ... #endif, the disabled code-section causes generated ClassA::method1 code in FSeamMockData.hpp:
class ClassToMock
{
public:
   ...
#if 0
    // -- DISABLED CODE SECTION: NotImplementedYet / NotSupportedYet
    void method1(UnknownClass value);
#endif

WORK-AROUND: Use comments instead of preprocessor to disable the code-section (comment it out).
To Reproduce
Described above.
If the disabled code-section causes problems with FSeam, compile-time errors are caused.
Expected behavior
Disabled code-section (especially with this simple-idiom that requires no knowledge of preprocessor-defines) should not lead to code in generated MockData.

Code generation is based on the c++ header parser https://github.com/robotpy/robotpy-cppheaderparser.
It is unfortunately, a naive approach that may not give the code generator the appropriate informations to decide which preprocessor condition is true or not.
The graal of this code generator would be to use a  libclang and actually not have a naive python parser but something working directly with the AST, I will update the documentation and try to think how we could solve this issue in a naive way.


Sync with upstream release v3.8.0-beta.60

Context
We are out of sync compared with the OHIF Viewer
Changes & Results
Sync with OHIF Viewer release v3.8.0-beta.60
Testing
Deploy and test in QA-MIDRC. Make sure everything running correctly.
Checklist
PR

[x] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[x] My code has been well-documented (function documentation, inline comments,
etc.)

Public Documentation Updates

[x] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[ ] OS:
[ ] Node version:
[ ] Browser:

Closing - We rebased the master-gen3 branch with these changes and will release gen3-v3.8.0 soon 👍


Changed config.ini location to AppDomain base directory

I couldn't start the application when it was installed as a service.
Turns out it tries to find the config.ini from a different location.
Vsgallery now tries to find it in the application location.

Thank you very much for this fix :)

No problem. Just trying to contribute :)


fix test that checks if systemd has failed units

The features/base/test/test_systemd test does not detect (all) failed units. Currently, if we manually verify on a booted GL image, we get the following failed units:

rsyslog
syslog
fail2ban

Maybe this is a timing issue. Test could run before the first units have failed.

This test runs on nightly platform tests see
This test does not run on chroot target, so if you execute ./test kvm-pyton_dev it will not run.
I can reproduce the issue. I build a kvm-python_dev, started it and have failed systemd units. I opened a python3 interpreter, and executed the test steps manually, to see if the test logic is broken. Manually stepping through a copy-paste (with adaptions) version of the test works as expected and detects the failed units.

=> I suspect that this is a timing issue. The tests executed as part of the platform tests is executed before the system is fully booted, so that the failed units have not failed yet.


Upgrade actions/setup-java v3.6.0 -> v3.7.0

This PR contains the following updates:

Package
Type
Update
Change

actions/setup-java
action
minor
v3.6.0 -> v3.7.0

Release Notes

actions/setup-java
v3.7.0
Compare Source
In scope of this release we added support for Oracle JDK (https://github.com/actions/setup-java/pull/401). Besides, we added logic to Pass the token input through on GHES for Microsoft Build of OpenJDK (https://github.com/actions/setup-java/pull/395) and updated minimatch dependency.
steps:
  - name: Checkout
    uses: actions/checkout@v3
  - name: Setup-java
    uses: actions/setup-java@v3
    with:
      distribution: oracle
      java-version: 17

Supported distributions
Currently, the following distributions are supported:

Keyword
Distribution
Official site
License

temurin
Eclipse Temurin
Link
Link

zulu
Azul Zulu OpenJDK
Link
Link

adopt or adopt-hotspot
AdoptOpenJDK Hotspot
Link
Link

adopt-openj9
AdoptOpenJDK OpenJ9
Link
Link

liberica
Liberica JDK
Link
Link

microsoft
Microsoft Build of OpenJDK
Link
Link

corretto
Amazon Corretto Build of OpenJDK
Link
Link

oracle
Oracle JDK
Link
Link

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade actions/setup-java v3.6.0 -> v3.7.0


Allow changing an EPerson's password through the CLI

References

Fixes #3363

Description
Add to 'bin/dspace user' and option to set a new password.
Instructions for Reviewers
List of changes in this PR:

A new option '--newPassword' is added to the '--modify' operation.  It should prompt for a password (which will not be echoed), prompt for the password again (to verify it), calculate a new password hash using a new salt and the default hashing algorithm, and set the EPerson's hash, salt and algorithm to these new values.  If the two passwords do not match, the password is not changed, but other modifications that were requested will be attempted.

After running bin/dspace user --modify --newPassword {email or netid} the old password should no longer be valid for the EPerson and the new password should be valid.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[x] My PR passes Checkstyle validation based on the Code Style Guide.
[x] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[x] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

Per today's meeting this was flagged as 1 approval (which it already has).  Merging immediately. Thanks again, @mwoodiupui !


fix: remove ESM package.json declaration (fixes 'Element' is not exported from '@prismicio/richtext')

Types of changes

[ ] Chore (a non-breaking change which is related to package maintenance)
[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR removes the explicit ES Module declaration by removing "type": "module" from package.json.
Declaring the package as an ES Module has caused issues in the following circumstances:

Next.js on Vercel: The entry file must use the .mjs extension to resolve correctly during server-rendered requests. This causes issues in build systems that do not recognize .mjs (e.g. Create React App). This only happens when deployed to Vercel in production. (See #108)
Create React App 4: .mjs files are unsupported. It works with a .js file extension, which breaks Next.js support.
Create React App 5: .mjs with "type": "module" is supported, but breaks backwards compatibility with CRA 4.

The most straightforward solution that ensures everything works out-of-the-box is to remove "type": "module" from package.json. When the ecosystem is more aligned behind ESM, we can restore it to a proper ES Module.
Fixes #117
Checklist:

[ ] My change requires an update to the official documentation.
[x] All TSDoc comments are up-to-date and new ones have been added where necessary.
[x] All new and existing tests are passing.

🙃

Codecov Report

Merging #122 (1b16476) into master (27c502f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #122   +/-   ##
=======================================
  Coverage   92.25%   92.25%
=======================================
  Files          16       16
  Lines         271      271
  Branches       60       60
=======================================
  Hits          250      250
  Misses          5        5
  Partials       16       16

Continue to review full report at Codecov.

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


In TokenView, why the lib is using OAuthLibCore instead of oauth2_settings.OAUTH2_BACKEND_CLASS?

I need to execute my own implementation, but the lib is blocking me of doing this.
There's some way to make my custom class works?
class TokenView(CsrfExemptMixin, OAuthLibMixin, APIView):
    """
    Implements an endpoint to provide access tokens

    The endpoint is used in the following flows:

    * Authorization code
    * Password
    * Client credentials
    """
    server_class = oauth2_settings.OAUTH2_SERVER_CLASS
    validator_class = oauth2_settings.OAUTH2_VALIDATOR_CLASS
    oauthlib_backend_class = OAuthLibCore  # ??????????
    permission_classes = (permissions.AllowAny,)

    def post(self, request, *args, **kwargs):
        # Use the rest framework `.data` to fake the post body of the django request.
        request._request.POST = request._request.POST.copy()
        for key, value in request.data.items():
            request._request.POST[key] = value

        url, headers, body, status = self.create_token_response(request._request)
        response = Response(data=json.loads(body), status=status)

        for k, v in headers.items():
            response[k] = v
        return response

This is an oversight on my part.
Will fix when I have the time. A PR is also welcome


Feature/el 69

Added Borrow History Unit Tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 2.50%. Comparing base (e3a297a) to head (cc4b191).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           develop     #38      +/-   ##
==========================================
+ Coverage     1.97%   2.50%   +0.52%
==========================================
  Files           69      69
  Lines         3589    3589
  Branches       140     140
==========================================
+ Hits            71      90      +19
+ Misses        3515    3496      -19
  Partials         3       3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Review was performed. No findings were found.


:wrench: Move statistics to src folder

Codecov Report

Merging #16 (67d7952) into main (268374b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #16   +/-   ##
=======================================
  Coverage   77.20%   77.20%
=======================================
  Files          35       35
  Lines        2694     2694
  Branches      345      345
=======================================
  Hits         2080     2080
  Misses        462      462
  Partials      152      152

Impacted Files
Coverage Δ

src/EagleRepair.Monitor/ChangeTracker.cs
83.20% <ø> (ø)

src/EagleRepair.Statistics/StaticAnalysisRules.cs
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Validation error, missing field when using optional[any] with default None value

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Hello world,
I'm using pydantic 2.5.2, and I got a strange issue (which i hadn't with pydantic v1).
If I use a Field as Optional[Any] and set inside the Field a default value to None, pydantic raise a field error.
If I remove the Field and set None directly it works.
I try to search on many places and also inside the documentation, but it "should" work, or I missed something ?
Thanks!
Example Code
from typing import Optional,Any
from pydantic import BaseModel, Field

class Job(BaseModel):
    id: str
    result: Optional[Any] = Field(defaut=None)

# ko
Job(id="myid")

# ok
Job(id="myid", result=None)

# If I remove `Field` and set to None directly

class Job(BaseModel):
    id: str
    result: Optional[Any] = None

# ok
Job(id="myid")

Python, Pydantic & OS Version
       pydantic version: 2.5.2
  pydantic-core version: 2.14.5
    pydantic-core build: profile=release pgo=true
           install path: /usr/local/myapp/.pex/installed_wheels/dd7271a4ebe824aa0a0c00700eaba0d43a826b49ccca6a270cdb6613f388af23/pydantic-2.5.2-py3-none-any.whl/pydantic
         python version: 3.9.5 (default, May 27 2021, 16:11:10)  [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
               platform: Linux-3.10.0-1160.105.1.el7.x86_64-x86_64-with-glibc2.17
       related packages: typing_extensions-4.9.0 fastapi-0.104.1 pydantic-settings-2.1.0

You have a typo defaut=None, where it should be default=None
This definition works fine:
class Job(BaseModel):
    id: str
    result: Optional[Any] = Field(default=None)  # note spelled correctly

Hi David,
I'm feeling so dumb  ... in french "default" is "défaut".
My model is composed with 15 Fields, all of them are "default" and just thoses 2 which are "any" had the typo.
That's why I didn't found anything about optional any and default :laughing:
Thanks a lot :heart:


database corrupt when trying to save deep learning network data in it.

Sounds like It was caused by get_account

Disable block broadcast via network to workaround this problem.


[R] Submitting to CRAN?

Hello,
What is the idea of submitting LightGBM to CRAN?.
Thanks,
Carlos.

Currently we need to have a stable release first. Then we also need to check if the package can be compiled on any OS, including exotic ones (Solaris, etc.).
After it will be submitted to CRAN once we reach that level and a good documentation of the R package (currently the doc is sparse about parameters and their impacts). @guolinke did so far a great job at fixing all the issues we are finding when it comes to the LightGBM backend integration in R.
About the R package documentation issue, anyone can submit PRs to help us (and also provide larger / more custom examples).

Sorry, thanks for your reply and clarifications.
If I see the possibility I could participate in creating a vignette for the package.
Thanks again,
Carlos.

@Laurae2
Do you think it is ready now ?

@guolinke We will need to switch to MinGW by default first and fix all CRAN issues encountered.

move to #629


Resource.uri and Resource.name are incorrect in browser

If you do something like this:
value resource = `module com.foo.bar`.resourceByPath("image.png");

When running on the JVM, the value of resource.uri will be a classpath:/ URI pointing to the resource and the value of resource.name will be "image.png", as expected. When running in a browser (Firefox, at least), the URI will be "module/com/foo/bar" and the name will be "bar". (I haven't checked what node.js does here.)

@chochos one for you.

This works correctly in node. I get:
file:/private/tmp/modules/test/0.1/module-resources/test/caca.txt
caca.txt

So it's just the browser environment that has this problem.


Add A* search algorithm option for path solving

The shortest_path now has the option to solve with either
Dijkstra or A*. A* offers some performance advantage since
is relies on the distance heuristic. Existing code is
unchanged since the algorithm choice is an optional parameter,
defaulting to Dijkstra. Example 2 script is modified to show
how it is used and a speed comparison.
Output from examples/2_calculate_shortest_distance.py:
Solved with Dijkstra's algorithm in 2.5208137035369873 seconds.
Solved with A* algorithm in 1.7424323558807373 seconds.
Shortest path distance: 16215.660241221995

I needed A* for my own use, so thought I might as well open a PR.

Quick comparison for anyone interested in using A* with this.
The blue nodes are actually visited by the solver.


Switch to execFileSync for better sanitization

Switch to execFileSync for better arg sanitization

More work as part of #21


Fix unrounded durations messing up the time

A better solution would be to make a minimum timeout duration like a minimum of 1 minute aka 60s

A better solution would be to make a minimum timeout duration like a minimum of 1 minute aka 60s

Done


Update README.md

Added some basic info on how to install the PQAnalysis tool.
Maybe the needed Python version and alternative package managers can be added as well.

I just updated the suggested changes. Basically for the standard usage of PQAnalysis it should be sufficient to just install it directly from the PYPI repo - meaning pip install pqanalysis.
In general, only if someone is interested in making some contributions one has to clone the repo from github.


Replace the obsolete JS media type

RFC-4329 is obsolete.
According to RFC-9239,

Changed the intended usage of the media type "text/javascript" from OBSOLETE to COMMON.
Changed the intended usage for all other script media types to obsolete.

Thanks for heads up @euj1n0ng!
Falcon isn't heavily tied to Javascript, so I suppose this is just about updating constants.py::MEDIA_JS. Would you like to create a PR?

Hey, this is my first time contributing to open source. Is this issue still open? @vytas7 @euj1n0ng
Also will this contribute to hacktoberfest?

Aha, I was unaware of the context. In fact, we need to check if this type constant is actually enforced when serving static files, otherwise you'll need to submit a PR to the CPython (or PyPy) itself :slightly_smiling_face:
(Or we need to modify Falcon to prioritize these constants to the system's mimetypes.)

Hi all, is this issue fixed? if not, I would like to contribute. I'm new to open source and was looking for good first issues.
@vytas7 @euj1n0ng

Hi @harshashetty67, this is not fixed, but there is already an open PR.
@harshashetty67 if you are okay with contributing documentation, we have a bunch of good first issues. We don't have that many good first issues for coding at the moment...
You can view all issues that need a contributor here: https://github.com/falconry/falcon/issues?q=is%3Aopen+is%3Aissue+label%3A"needs+contributor"
Maybe one of these could suit you?

https://github.com/falconry/falcon/issues/1026
https://github.com/falconry/falcon/issues/1137
And as said, if you're fine with writing documentation, that we have tons of good first issues. I can help you picking something there.


Reflect the fact that atom-dark is no longer the default

This changed in atom v0.188.0

@AgentAntelope Right! Thank you.

It's still my favourite though! :shrug:

:+1: It will keep being bundled.

Awesome!
Is a similar change needed over at https://github.com/atom/atom-dark-ui ?

Actually.. yes. And I guess also for the light themes: https://github.com/atom/atom-light-ui + https://github.com/atom/atom-light-syntax. If you feel like it. :bow:


Compatibility renderer: Alternate viewport display modes don't work

Godot version
v4.0.stable.official [92bee43ad]
System information
Arch Linux, AMD RX 6700S, opengl3
Issue description
With the OpenGL3 compatibility renderer, the viewport display modes have no effect. In Godot 3.4, these options are disabled, but they are not disabled in Godot 4.
https://user-images.githubusercontent.com/5725958/222947167-f2fc68f0-3bb9-44bb-b8cb-1c042f085af1.mp4
Steps to reproduce

Create a new project with the Compatibility renderer
Create a 3D scene with a MeshInstance3d
Try different display render modes in the 3D viewport

Minimal reproduction project
project.zip

Regression from #35241?

Indeed, they should likely be disabled like in 3.x (cc @Calinou).


Do not fail if an SNS subscription has no topics

If an SNS subscription exists, but the topic has been deleted, listing SNS subscriptions will fail with:
An error occurred (NotFound) when calling the GetSubscriptionAttributes operation: Topic does not exist

This will catch these failures and continue to enumerate the SNS subscription ARNs - just without the details.

:shipit:


size mismatch for encoder.embedding.embedding.weight when testing model

Hello,
I was following instructions in the repository (with a very small number of iterations to check that everything is set up properly on my machine) as follows:
python train_equivariant_scan.py --split add_jump --equivariance verb --use_attention --bidirectional --n_iters 500
Output:

I then ran:
python test_equivariant_scan.py --experiment_dir models/add_jump/rnn_GLSTM_hidden_64_directions_2/model1/ --fully_trained
However, the result was a size mismatch error for the encoder embedding weight:

Apologies if I have missed something really obvious, but could you please let me know whether I need to run additional steps to solve this issue or this is a bug in the code?
Thank you!

Hello,
Thank you for catching this! There was an issue with the default settings of the train / test scripts, which has now been fixed. If you pull the latest changes, this should now work.


Appstudio update test-component-pac-rxgw

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-rxgw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
10 seconds
deprecated-base-image-check

✅ Succeeded
10 seconds
sanity-inspect-image

✅ Succeeded
1 minute
clair-scan

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
11 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary


Remove x icon from close icon in top right

hi
how i can remove x from close icon in top right?
best regards

thank you for your answer
but i mean is remove content of close icon (x)
in other words remove content of jconfirm-closeIcon tag

x

Why would you like to remove it's content, it's the same as removing the tag itself right?

If you want to keep the tag but remove it's content then use this,
this.$closeIcon.html('') // set an empty string.

Please reopen the issue if any updates


Changing profile.*.lto in Cargo.toml shouldn't rebuild everything

Neither should adding, modifying or removing linker flags via -C link-arg or -C link-args in .cargo/config (build.rustflags or target.*.rustflags).
These only affect the compilation of the top crate.

I'd prefer to keep Cargo from parsing rustflags and trying to learn about specific flags, but Cargo already has intrusive knowledge of lto to fixing that seems reasonable to me!

codegen-units is the same kind of thing, isn't it. Nothing needs to be rebuilt.
In rustbuild, I would like it to not rebuild anything when -Ccodegen-units=x is added in rustflags. (Maybe rustbuild has some specific option for this).

We just ran into this one again. It seems that adding lto = true to the dev profile means that switching between cargo build and cargo build --tests will now rebuild the entire crate graph every time, which is pretty unfortunate (and was also fairly hard to track down to this issue).
I think this should be considered a bug instead of a feature request.

@jonas-schievink That sounds like a different issue. This issue is about changing the LTO setting.  What you're mentioning sounds like a rebuild-detection issue when switching between commands.  Can you file a new issue with a reproduction? Also, beware, there has been a recent change which might affect the behavior that will appear in the next nightly.

@ehuss Okay, filed https://github.com/rust-lang/cargo/issues/8669

Since this was created, #8192 was merged which optimized LTO builds by doing work in dependencies that isn't needed.  This makes LTO affect dependencies and not just the final artifact.  There are times where sharing could occur which is being tracked in #8343.  The lack of sharing can also cause surprising rebuilds like in #8762.
rust-lang/rfcs#3310 was proposed as a general mechanism for specifying final-artifact-only rustflags.  However, that was postpined.

Between LTO changing dependencies and the tracking of link-only arguments in #4349, I'm going to close this.


4.1.68 security advisories use floating links for code references

The security reports for 4.1.68, GHSA-9vjp-v76f-g363 and GHSA-grg4-wf29-r9vv, contain a few reference links to their related code areas. However they use links to the 4.1 branch which may float over time, and so while they may be correct now they will likely become incorrect as the various files change. The references should used fixed links such as via the release tag to ensure they remain appropriate.

Fixed... Thanks!


Summaries from VS are not properly colorized inside a razor file

When I invoke method/class summary in normal C#:

When I do the same thing in a .razor file:

As you see, all colors are gone. Please fix it.

ping @dibarbet

@NTaylorMullen c# appears to be returning the correct classified text runs

Additionally, I verified that using LSP in a normal C# document does return classified text (with these text runs).  Could it potentially be getting dropped on the razor side?

Could it potentially be getting dropped on the razor side?

Oh wow ya agree it's probably being dropped on the Razor side, so interesting! Thanks for confirming!

Oh wow ya agree it's probably being dropped on the Razor side, so interesting!

If you walk in the debugger down the path for signature help request to HtmlCSharp server, you will find your last stop here:
https://github.com/dotnet/razor-tooling/blob/472b7aefcda5ae9877946bb739b5dc556492b034/src/Razor/src/Microsoft.VisualStudio.LanguageServerClient.Razor/HtmlCSharp/RazorHtmlCSharpLanguageServer.cs#L230-L239
If you make this method async and modify  return ExecuteRequestAsync... line to:
var signatures = await ExecuteRequestAsync...
return signatures;

...then you will be able to put a breakpoint and see what is in signatures variable. And they will be eventually the same as they are on @dibarbet's screenshot with ColorizedLabel and ClassifiedRuns inside.
According to VS code lens, SignatureHelpAsync method is not directly called from anywhere else in the repo. Also in the debugger's call stack this is the last method, that is called by "external code". If to look at containing type (RazorHtmlCSharpLanguageServer), it is only used (besides test code) in RazorHtmlCSharpLanguageServerClient class, that is exported as a VS language client. In that class the only place the server instance in used is in ActivateAsync method, that returns Connection to a language server. So as I understand, language server client gives a connection to the actual server, and then individual methods are invoked by the LSP platform. Also searching in the repo with SignatureHelp query findes only classes from this codepath: SignatureHelpHandler -> RazorHtmlCSharpLanguageServer, test references and SignatureHelpOptions stuff. No other mentions. Considering everything above, I made a conclusion, that this might be an LSP platform bug (but that is not certain, I am not that much familiar with the platform and code flow in it).
My research here is over) Can someone confirm/deny it?  I went ahead and debugged through it as well to verify we're returning the right data (we are) but platform isn't respecting that. @matteo-prosperi is there a known issue on the platform we could associate?

@matteo-prosperi mentioned on his side there's nothing known but on the CoreEditor side there might be. @gundermanc do you happen to know of anything?

@gundermanc do you happen to know of anything?

Yes I suspect this is due to a hack in the VS LSP client which seems to hard code the content type for the language server client classifier: https://devdiv.visualstudio.com/DevDiv/_git/VSLanguageServerClient?path=/src/product/RemoteLanguage/Impl/Features/SignatureHelp/SignatureHelpClassifierProvider.cs&version=GBdevelop&line=14&lineEnd=16&lineStartColumn=1&lineEndColumn=47&lineStyle=plain&_a=contents.
Maybe adding [ContentType("Razor Signature Help")] would work-around this.
Can you file a bug in Editor area path? I'd prefer we finally fix this the right way and make it just work for every language.

Ah that's definitely it. Thanks @gundermanc! I've filed: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1593495
@DoctorKrolic I'm going to close this as external for now

Ok. Btw in such cases it is better to close the issue as "not planned". You can find this options by clicking the dropdown near the normal "Close issue" button (I believe, such button is present even in already closed issues). No pressure, just want more devs to know about this recent github feature and use it more actively


[Slide] Showing an error: "Types of property 'children' are incompatible"

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯

React + Typescript
When I try to use the popover TransitionComponent to create a slide animation, this error persists
Expected behavior 🤔
No response
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎
No response

Could you please provide a reproduction on codesandbox so we can take a closer look at the problem?

Please check the codesandbox below, I have no idea how to set the animation of popover content with TransitionComponent, I wanna the content can appear from the bottom of the screen with slide animation
https://codesandbox.io/s/popovercontentanimation-x4tuvo?file=/src/App.tsx

Slide's children are more restricted than usual - they have React.ReactElement<any, any> type.
You can make it work by either typing your Transition's props as SlideProps:
import { Typography, Button, Popover, Slide, SlideProps } from "@mui/material";

//...

const Transition = React.forwardRef((props: SlideProps, ref) => (
  <Slide direction="up" ref={ref} {...props} />
));

or creating your own interface with children typed correctly:
interface TransitionProps {
  children: React.ReactElement<any, any>;
}

const Transition = React.forwardRef((props: TransitionProps, ref) => (
  <Slide direction="up" ref={ref} {...props} />
));

Let me know id it helps.


Missing implicit downcast in DDC for fields with override inferred types

I believe the following code should have an implicit downcast on the initialization of the messages field:
abstract class A {
  final Map<String, int> messages;
}
class B extends A {
  final messages = foo();
  static foo() => {"hello": "world" as dynamic};
}

void main() {
  var b = new B();
  print(b.messages["hello"].isEven);
}

The analyzer seems to be correctly inferring the type of the messages in the subclass based on the override, but there seems to be no downcast inserted by DDC.

The analyzer seems to be correctly inferring the type of the messages in the subclass based on the override, but there seems to be no downcast inserted by DDC.

Downcasts are the responsibility of the front end. In Analyzer checker.dart sets the "implicit cast" flag on the Expression, in Kernel the coercions are reified with AsExpression nodes.
So, most likely this is an Analyzer bug. From a quick look at CodeChecker.visitVariableDeclarationList in Analyzer, it doesn't seem aware that an inferred field is a possibility (it skips all checking if there was not a TypeAnnotation AST node present, which there is not in this case).

@jmesserly I'm guessing that this is no longer interesting given that ddc will be moving to kernel soon. If that's true, could you please close this issue?

good catch. I tagged this bug to indicate that it will be fixed with Kernel. Not sure if we should close them until DDC is switched over (because until then, the bug exists)? I guess we could say "closed not planned"?


Could this compiler support XDP_REDIRECT

The XDP_TX return code only support to send the packets to the same NIC card .  And XDP_REDIRECT can send the received packets to another NIC .  However , this compiler seems not to implement XDP_REDIRECT ?  Is there any other way to implement forwarding function from one nic like eth1 to another NIC like eth2 using P4C-XDP compiler?
I notice that the xdp_model.p4 has defined xdp_output:
struct xdp_output {
    xdp_action output_action;
    bit<32> output_port;  // output port for packet
}

As for the output_port , is it used to appoint the different NIC id?

The work in the compiler to support XDP_REDIRECT is very simple.
At the time we implemented this it wasn't supported by the kernel. Maybe this has changed.
@williamtu : do you know how one has to proceed to use XDP_REDIRECT?

In fact, no work in the compiler is needed. You can just add XDP_REDIRECT to the p4include/xdp_model.p4 file and it will produce the right C. I will submit a PR. However, I still don't know how you should use it.

Thank you for your prompt reply.
After I add XDP_REDIRECT to the xdp_model.p4 , I can successfully compile the xdp program with XDP_REDIRECT .
I guess the xout.output_port is related to different NICs. For example , output_port set to 0 corresponds to eth1 and 1 corresponds to eth2.  Then I still set output_port as 0 and output_action as XDP_REDIRECT to implement the same function of XDP_TX transmitting received packets to the same NIC eth0.
if(hd.ipv4.isValid())
        {
            dstmactable.apply();
            xout.output_port = 0;
            xout.output_action = xoutdrop ? xdp_action.XDP_DROP : xdp_action.XDP_REDIRECT;
        }

and the generated xdp5.c file :
    xout.output_port = 0;
    if (xoutdrop_0)
            tmp = XDP_DROP;
    else
            tmp = XDP_REDIRECT;
    xout.output_action = tmp;

However, I cannot capture any transmitted packets .   And then I did another test to set the out_port as 1 and output_action as XDP_REDIRECT to see if I can capture packets in the eth1. Unfortunately still cannot.
So how to implement sending packets to different NIC using XDP_REDIRECT and how to specify the NIC id ?  Is it the output_port to specify which NIC to redirect to ?
I see there is a map, called ebpf_outTable, only has one max_entries in /sys/fs/bpf/xdp/ . Is this map used to specify different NICs cooperating with XDP_REDIRECT ？
Thank you for your attention to this matter. It would be nice if you could provide a bit more information on this question.

Hi,
XDP_REDIRECT requires using a map, ebpf_outTable, to lookup the output port.
And the now we send packet using TC, not XDP, by calling a bpf helper function called bpf_clone_redirect.
For example, if you want to send to eth8, eth8's ifindex should be programmed into the value of the map.
Are you able to see the contents in the ebpf_outTable? ex: by using the bpftool?
Thanks

Thank you for your prompt reply.
Yes, I can see the contents of ebpf_outTable generated by xdp5.p4 with command :
bpftool map dump pinned /sys/fs/bpf/xdp/globals/ebpf_outTable

the output is
key:
00 00 00 00
value (CPU 00): 00 00 00 00
value (CPU 01): 01 00 00 00
value (CPU 02): 00 00 00 00
value (CPU 03): 00 00 00 00
value (CPU 04): 00 00 00 00
value (CPU 05): 00 00 00 00
value (CPU 06): 00 00 00 00
value (CPU 07): 00 00 00 00
Found 1 element

Do you have any simple examples that using TC cooperating with xdp program generated by P4C-XDP  to send raw packets from one NIC to another .  The xdp program just pass packets. Then TC receives the packets and send to another NIC.
Really appreciate your help!

Actually the ebpf_outTable only has one entry in the xdp.c file. And how to specify the max_entries of this map in P4 program?  Do you know how to specify which NIC to send packets in P4 program ?
I guess maybe the xout.output_port in P4 program is the ebpf_outTable's key and NIC's ifindex is the value ?
It would be nice if you could provide a bit more information on this question.

So looking into more details, XDP_REDIRECT is not supported now.
The way p4c-xdp implemented redirect or send to another port is to use TC.
So idea is that the XDP program always return XDP_PASS, and the packet will
go to the TC layer.
At the TC layer, we have to insert another ebpf program to forward this packet,
based on the lookup result of ebpf_outTable.
So in your case, it doesn't work because you need another ebpf program attached to TC.
The reason we did this is because at the time we started the program, there is no XDP_REDIRECT support.
Now the right way to do XDP_REDIRECT is through BPF_MAP_TYPE_DEVMAP
see this slide for more details
http://people.netfilter.org/hawk/presentations/LLC2018/XDP_LLC2018_redirect.pdf
In this way, we don't need TC to send packet, the packet will be handled at XDP layer.

Hi,
Thanks a lot for your help.  Do you have any simple ebpf program attched to TC which uses ebpf_outTable to send raw packets from one NIC to another ?

Yes, the hash_table(64) can appoint the dstmactable's max entries. Actually I want to specify the max entries of ebpf_outTable. However, it seems that there is no method to specify this in P4 program .
And as for the forwarding workflow , I guess it's maybe like this:

First, user knows which packet should be passed to the TC layer to be forwarded. For example , user wants the packet , which dst IP address is <IP_ADDRESS> , received from eth0 to be passed to TC and forwarded to eth8. So the P4 table might like this :

action Fallback_action {
        xout.output_port = 8;
        xout.output_action = XDP_PASS;
}

table dstmactable {
        key = { hd.ipv4.dstAddr : exact; }
        actions = {
            Fallback_action;
            Drop_action;
        }
        default_action = Drop_action;
        implementation = hash_table(64);
    }

the table entry is

key
actions

<IP_ADDRESS>
Fallback_action

It means that once a packet whose dst IP address is <IP_ADDRESS> from eth0 arrives at XDP layer, the XDP program will match the first entry of dstmactable and set output_port = 8 and pass the packet to TC layer.  And all this actions don't have effect on the ebpf_outTable.

Second, user knows that once TC layer receives a packet , that packet must be the one which user wants to forward.  In this case , only packet of which the dst ip address is equal to <IP_ADDRESS> will be passed to TC.
So , user updates the ebpf_outTable by adding <output_port , ifindex > to ebpf_outTable:

key
value

8
666

the 8 is the output port number which P4 program sets.  And 666 is the eth8's ifindex.

Third, user  writes another ebpf program to attach to TC layer. Once TC gets packets, it looks up the ebpf_outTable by using output port 8 as key which assigned in P4 program and gets the ifindex of NIC .  After that  ,  TC calls bpf_clone_redirect helper function to forward this packet to the eth8's egress.

And here is the question:
How would TC know the output port is 8 .  I mean, in TC layer , TC only gets the raw packets and no other information.  And how the P4 program transfer the output port information to TC .  Or the user just knows it and sets the output port as a static number in TC's ebpf program ? But in this way, it seems the output_port field belongs to struct xout  in P4 program is no use. User could assign any number as key because only the ifindex is valuable . And what if user wants to forward to a third interface, the method of setting the output port as a static number won't work well.
What I think is that if TC wants to know which interface egress should be selected to forward packets , TC must parse the packet and get the dst IP address. But that might seem like overkill.

Hi,
Thanks a lot for your help. Do you have any simple ebpf program attched to TC which uses ebpf_outTable to send raw packets from one NIC to another ?

I don't have an exactly working example, but you can follow this sample code
https://elixir.bootlin.com/linux/latest/source/samples/bpf/tcbpf1_kern.c
which uses bpf_clone_redirect and specify ifindex for output packet

And here is the question:
How would TC know the output port is 8 . I mean, in TC layer , TC only gets the raw packets and no other information. And how the P4 program transfer the output port information to TC . Or the user just knows it and sets the output port as a static number in TC's ebpf program ? But in this way, it seems the output_port field belongs to struct xout in P4 program is no use. User could assign any number as key because only the ifindex is valuable . And what if user wants to forward to a third interface, the method of setting the output port as a static number won't work well.
What I think is that if TC wants to know which interface egress should be selected to forward packets , TC must parse the packet and get the dst IP address. But that might seem like overkill.

TC doesn't need to know key is 8, all TC does is to get the first entry in the map and output the packet to the ifindex 888.
And every time before the packet pass XDP layer, the map entry will be updated for the coming packet arriving at TC layer. So we don't need to parse the packet again at the TC layer.

Hi,
Is there any update on doing XDP_REDIRECT without using TC?

Technically I don't think any changes need to be made in the compiler; it's probably just the control-plane setup that needs to be adapted. I personally don't have a machine where I can test XDP; I don't know if @williamtu has time to build an example.

I'm not able to redirect packets using code generated by p4c-xdp.
Also, if I use bpf_redirect, I can process only upto 500K packets.

Using code generated by p4c-xdp, I was not able to redirect.
Used redirect_map helper inside XDP code to redirect packets successfully.

Can you contribute an example?


Changed imports to work with current source code...

This fixed issue #8 for me - after go build everything seems to work... I don't know if this is a correct approach, sorry if not :-)

Go Modules is probably the solution to this. I'll be looking into adding that soon™. Changing imports to paths like this is dependent on where source is on the system. I'd rather not do that

Go Modules is probably the solution to this. I'll be looking into adding that soon™. Changing imports to paths like this is dependent on where source is on the system. I'd rather not do that

I am quite not sure what you mean as the main.go uses similar relative-path imports. Those imports are included in the git project, they are not external modules so relative path shoud not change (unless some refactoring cames along). Would you, please, elaborate more? I am trying to understand the correct approach... :-) Thank you very much.


[notification hubs] Add tests typechecking

Packages impacted by this PR
@azure/notification-hubs
Issues associated with this PR
N/A
Describe the problem that is addressed by this PR
This PR migrates notification-hubs to typecheck tests and samples. It also includes DOM in the typing context for src so we don't have to roll out our own web types.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A
Are there test cases added in this PR? (If not, why?)
N/A
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


TextField Safari: cursor position resets to end of text input whenever value changes

In Safari, whenever editing the value in a TextField, the cursor position jumps to the end of the line.
something like the following will reproduce the bug (using linkstate for simplicity
<TextField type="text"
	className={style.firstName}
	id="profileFirstName"
	name="profileFirstName"
	label="First Name"
	value={form.firstName}
	onInput={linkState(this, 'form.firstName')}
/>

A PR has already been created for material-components/material-components-web https://github.com/material-components/material-components-web/pull/4160

Well what should we do about that? It's an mdc bug, so there's nothing we can do.
I'll close this, but feel free to comment, if I miss understood you.

Sorry I just saw that we where also doing this


Make creation and visitation of SyntaxData more efficient

Make SyntaxData an efficient value type that eagerly tracks how a raw node relates to a source file tree, like its absolute offset and its parent.
SyntaxData has no identity and Syntax types are no longer Equatable/Hashable.
Syntax objects are fully thread-safe now, LazyNonThreadSafeCache has been removed.
child(at:) and numberOfChildren have been removed from the Syntax API due to child(at:)'s performance becoming O(n). Clients should be using the provided Sequences for efficient visitation.

@swift-ci Please test

This looks great! :boat:

Build failed
Swift Test OS X Platform
Git Sha - f024a1fde86e63387628dceba9103df866a5e4ba


Feature request: server mode for solving CGNAT issues on GPRS IoT devices

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

(X) feature request

I'm currently working on a IoT project involving ModBus TCP communications with remote low power devices connected via GPRS. Those devices are in a CGNAT (Carrier Grade NAT) network, which means that the assigned IP of the device is not accessible from the internet. The only solution (and the one we've previously used and is more or less the standard solution in related forums) we have come up with, is to start the communications from the device (as if it were a client interrogating our central server) and then re-use that channel from the server to interrogate the device.
It's doable from regular code, and (I think) a common enough problem to be considered a nice feature to have in this project.
The main caveats are:

non standard solution (albeit commonly used)
keeping alive the connection: forces us to send regular "heartbeats" via exceptions (whose codes may even be used to notify changes in the device, and thus trigger an update from the service)

In case you are interested in adding this functionality to the project, I can devote some of my time to do so (If, again, you are so inclined too) and publish it via pull-request.
Thanks for your time and for such a great node-red module!!
Pedro.

Hi Pedro,
you're welcome to send your pull request.
please read the contributing.md

please, try to write tests for the new code ...

please, work on branch develop - many changes are there - to fit into later releases

reopen with your pull request


Optimise query in the events admin detail page

When we select a record to display in the all events admin, we can optimise the query not to UNION other event tables but stick to the original table only.

Thanks! It seems like the direct module import of the models causes them to be prematurely loaded before apps are configured. Changing it to a nested import fixes the suite, so Ill add that change upon release

Just deployed this in the 3.5.0 release. It should be on pypi within the next 15 minutes!


Read all columns of metadata to prevent column missing

Why are the changes needed?

Since https://github.com/apache/kyuubi/issues/4843, we need the requestConf column to get application manager info.
So now the stateOnly option for metadata select is not needed.
private val METADATA_ALL_COLUMNS = Seq(
    METADATA_STATE_ONLY_COLUMNS,
    "resource",
    "class_name",
    "request_conf",
    "request_args").mkString(",")

In this pr, I remove the stateOnly flag to select all metadata columns to prevent column missing and make it easy to maintain.
How was this patch tested?
Existing UT.
Was this patch authored or co-authored using generative AI tooling?
No

LGTM if CI pass

thanks, merging to master


Cache newly rendered cells on horizontal scrolling as jQuery objects.

These were being added as DOM nodes and causing errors on cell selection.
The issue occurred with 40+ columns on my 1920 width screen.

Thanks!


problem with ATI Radeon HD 6420

Hi,
I've tried to run a Unity project included Spout sender on a pc with AMD Radeon HD 6450 but game crashes and displays "ATI Radeon Driver Stop Working" message. I've run this project on another computer before (with Geforce Graphic).
I just want to know is there any special compatibility for running a Spout Sender in unity?
Thank you

KlakSpout doesn't support "CPU mode" that is implemented for old/low-end hardware. The problem is that I don't have any device that requires the CPU mode, so I can't test it.

Thank you Keijiro, I used your code in different situations and worked really good. :)
Is there any way that I can use a Spout Sender in "CPU Mode" ?

I can't remember details, but I think it's not easy. It may require modification in several parts of the code.

I'm closing this issue ticket now as duplication of issue #20


Various Cleanups

This PR does three more-or-less unrelated things that are all necessary for the upcoming counters series.

It updates to tool chain and re-runs make generate.  Note that mockery 1.0 does not play nicely with go lint.  The problem is fixed by  this PR https://github.com/vektra/mockery/pull/167, but unfortunately until that's merged we'll need to make sure we're cloning the updated version locally before re-running.

The PR refactors the Amazon client a bit.

The PR changes api/client to use mockery instead of the manually implemented solution we had.

@luise, pushed a new version in case you want to look over the changes.


[8.x] Add allowIf and denyIf helpers to HandlesAuthorization

This PR allows a way to quickly return a policy response conditionally using similar syntax that is used elsewhere in the framework such as $this->when( ... ), abort_if( ... ) and throw_if( ... ).
The two methods would accept either a value or a callback.
I have only allowed the message and code to be specified for the deny response as I was unsure as to where/when an allow response would actually ever be returned and used as a response.
An example of its usage is;

// Current implementation
public function delete(User $user, Patient $patient): Response
{
    if ($user->hasPatient($patient)) {
        return $this->allow();
    }

    return $this->deny('You must be assigned to this patient.');
}

// Using new methods
public function delete(User $user, Patient $patient): Response
{
    return $this->allowIf($user->hasPatient($patient), 'You must be assigned to this patient.');
}

And to deny;
public function delete(User $user, Product $product)
{
    return $this->denyIf($user->isCustomer());
}

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Correct noirc_abi dependency problem

Installation of noir_js results in:
Couldn't find any versions for "@noir-lang/noirc_abi" that matches "workspace:*"

Seems like this might be to do with the fact that we use npm publish rather than publishing through yarn. npm wouldn't support yarn workspaces so it's not automatically rewiring these dependencies.


3 buttons or more in alert

when i but 3 buttons in the alert it show me like this
link
i think should the alert be like that 🤔
link

hello! thanks for submitting an issue. The photos you shared are not accessible.

i'm sorry it's bad website
here
what i see
link
what should i see
link

did you try to set isActionButtonsVertical to true?

niccccce thankkk u ❤👌🏻


How can I play sound effects?

They should already play automatically when e.g. connecting to a server. If you try to connect to a server, can you hear any sound at all? Or can you hear other clients but specifically not sound effects?

1 we can do. ill create a separate issue. a soundboard is out of scope for this project i think. you could look for some kind of virtual audio device program (i think i myself have used plain old pulseaudio for this) and a separate soundboard. i cant really help you with that though, sorry.


change mechanism for deps; add depsRequired; add depsFrom.

@roberth It would be amazing if you could review this. I really want to get this right.
With this commit, the user is forced to explicitly specify all required dependency names via depsRequired. options.deps contains generated options for all names of depsRequired. These options are populated with defaults from depsFrom, The examples under ./examples show how this is used.
The coercedTo type of deps had some weaknesses:

It was not possible to specify required dependencies explicitly, because it was not possible to create nested options likeoptions.deps.bash = mkOption ....
Because of (1.) I had to add a manual check in makeModule.nix to ensure that all required deps are populated by the user.

Having actual options for all required dependencies allows to reduce complexity and hand the checking off to the module system.
Also, when rendering the options for a package to a doc, all dependencies now appear as an option, which I think is great. It allows the user to see all inputs of a package without having to read the code.
This whole deps mechanism is generic enough to suit as a general inputs. It probably should be renamed to inputs in the future, but I don't want to clutter this PR too much.
EDIT:
options.stdenv can now probably be moved to options.deps.stdenv. It is basically just a dependency of the derivation and I see no need for special treatment.

should be renamed to inputs

Those could be understood to be flake inputs. Arguably those shouldn't be in scope though, so perhaps shadowing is a good thing. Still potentially confusing though. Especially inputs = { inputs, ... }: inputs.foo is a bit odd.

I'm also surprised to see that pkgs is even in the package module arguments. Was that needed for something? (before this PR)

Which package module arguments do you mean?

Did you try with mkOption { apply } instead of type = coercedTo?

Not yet, but I will experiment with it now.

I'm also surprised to see that pkgs is even in the package module arguments. Was that needed for something? (before this PR)

Which package module arguments do you mean?

I think I inferred this wrong when reading the code. Maybe got confused by what you said is a bad example.

It was not possible to specify required dependencies explicitly, because it was not possible to create nested options likeoptions.deps.bash = mkOption ....

Did you try with mkOption { apply } instead of type = coercedTo?

Which type would I pick that allows nested options? If I pick submodule, I cannot define a function for deps anymore, because it gets interpreted as a module, and errors out.

Which type would I pick that allows nested options? If I pick submodule, I cannot define a function for deps anymore, because it gets interpreted as a module, and errors out.

functionTo submodule? Or maybe the dependency sets could be specialArgs?

To explain my though process a bit better:
One underlying question seems to be: Who gets to pick dependencies? The package maintainer, or the caller?
deps = { pkgs, ... }: puts the decision in the hand of the maintainer which makes sense in a mono repo like nixpkgs, where maintainers just want to add a file and have everything sorted.
Out in the decentralized wild, it might be more valuable to let the caller satisfy the dependencies, which requires that requirements are discoverable in some way.
Therefore I thought it's a good idea to enforce an option for each dependency.
Thinking about an end game where nix competes with language specific package managers, the decentralized fashion seems to be the more generic approach vs. nixpkgs is more specific. Maybe the logic of how dependencies are picked within nixpkgs, should be factored out into a separate module?

functionTo submodule? Or maybe the dependency sets could be specialArgs?

Genius! submoduleWith {modules = []; specialArgs = packageSets;} seems to work wonderfully. Thanks for that.
With that, I can get rid of depsDefault, as a mechanism to provide defaults.
depsRequired still seems necessary, if we want discoverable dependencies.
Maybe one can get rid of deps in most cases by providing a default implementation for deps that intersects depsRequired with a default dependencySet like pkgs.
A package module would then look like this:
{config, lib, ...}: {
  name = "test";
  # all required deps must always be declared
  depsRequired = {
    foo = true;
    bar = true;
    bash = true;
  };
  # `deps` is only required for picking non-default versions
  # This logic is specific to the repo the package resides in, but can easily
  #   be removed by a `mkForce`.
  deps = {pkgs, ...}: {
    # pick a special version for bar
    bar = pkgs.bar_2;
  };
}

Out in the decentralized wild, it might be more valuable to let the caller satisfy the dependencies, which requires that requirements are discoverable in some way.

I don't think the change will be huge. A lot of people already live in a decentralized wild (without Nix) and they rely on distributions to provide such things as docker base images. Even a gentoo user doesn't stitch together all dependencies by hand. (I think? It's been over a decade.)

depsRequired still seems necessary, if we want discoverable dependencies.

or mkOption, right?

depsRequired

types.enum [ true ];? types.submodule {}?
I never know what to make of sets of names.

  # `deps` is only required for picking non-default versions
  # This logic is specific to the repo the package resides in, but can easily
  #   be removed by a `mkForce`.
  deps = {pkgs, ...}: {
    # pick a special version for bar
    bar = pkgs.bar_2;
  };

Not sure if going in circles, but what about depsRequired = lib.attrNames (lib.lazyFunction config.deps (throw "The attribute set returned by depsmust have a static set of attribute names, so nooptionalAttrsor anything else that may depend on the arguments of thedeps function."))?
I should probably merge this, shouldn't I:

https://github.com/NixOS/nixpkgs/pull/194514

I don't think the change will be huge. A lot of people already live in a decentralized wild (without Nix) and they rely on distributions to provide such things as docker base images. Even a gentoo user doesn't stitch together all dependencies by hand. (I think? It's been over a decade.)

Even if you have a community maintained package set, where the community picks one good version for everything, that approach only scales so far. There will always be the necessity to assemble environments with dependency versions different from the ones found in the community set. Language specific environments are the best example for that.
Customizing dependency trees can be done by hand or by a resolver, but in any case, to support this well, the requirements of a package should be discoverable.
Currently this is not the case in nixpkgs, which is one major reason for the big gap between the automated language2nix approaches and nixpkgs. Combining the two is hard. One is either in this world or in that world.
It would be nice if mixed approaches would be supported, so that users can satisfy their requirements, by taking some packages from nixpkgs and others from elsewhere (auto-generated, or different repos, etc...). Automatically.
Expanding a bit on the depsRequired idea, we could have, for example:
{
  depsRequired = {
    foo = "^2.0.0";
    bar = "*";
    baz = "~2.0";
  };
}

If packages had that, mixing dynamic language2nix approaches with nixpkgs would be a charm. Knowing more about a package is beneficial for automation. And automation is key to scale.

depsRequired still seems necessary, if we want discoverable dependencies.

or mkOption, right?

depsRequired is creating options for deps behind the scenes. It's equivalent of using mkOption. It just requires less typing.
Anyways, I might be biased by dealing with language2nix too much, and I do not want to pollute the core of drv-parts with anything that we don't agree is absolutely necessary.

I now opened https://github.com/DavHau/drv-parts/pull/11 which is a more minimal change, just allowing nested options for deps.
The new PR:

doesn't add any additional options like depsRequired etc.
keeps the deps = {pkgs, ...}: {inherit (deps) ...;} style intact

so this implementation / PR will be closed?


Custom views: Expand/Collapse state is not saved after refresh

Issue Type: Bug
Seems like there's been some new tree work? This issue repros on most of our Azure extensions and only on insiders (works fine on VS Code v1.36.1). I'll use the storage extension as an example.
Repro steps:

Expand several items down the tree

Right click on subscription ("erijiz test") and refresh

Expected:
Tree looks basically the same with all nodes still expanded
Actual:
Everything under subscription is collapsed

VS Code version: Code - Insiders 1.37.0-insider (360e4e4dfa989135f28edc0d6f7e42df33cddf87, 2019-07-10T05:29:59.244Z)
OS version: Darwin x64 18.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (2.80GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

azurerm-vscode-tools
ms-
0.6.1

vscode-azureappservice
ms-
0.15.0

vscode-azurefunctions
ms-
0.17.1

vscode-azurestorage
ms-
0.7.0

vscode-docker
ms-
0.7.0

remote-containers
ms-
0.66.0

remote-ssh
ms-
0.44.0

remote-ssh-edit
ms-
0.44.0

remote-ssh-explorer
ms-
0.44.0

azure-account
ms-
0.8.4

vscode-typescript-tslint-plugin
ms-
1.2.1

sort-lines
Tyr
1.8.0

This should already be fixed if you update to the latest insiders!

No longer repros - thanks!


[iOS] Apply Sponsor View Design

Issue

close #558

Overview (Required)

Apply the design.
Open link with SafariView when items are tapped.
Show spinner during loading data.
I feel scrolling is not smooth 🤔 (Images are too large??)

Links

Screenshot

PLATINUM-GOLD
GOLD-SUPPORTER
Loading

@sudachi808
There was a small and obvious conflict. I fix it to merge early 🙏🏼


How login a user?

How would I login to a user using postAsync?

Hi. There is no way to login using the WooCommerce API. Please have a look at some other ways to login. There are solutions for WordPress Auth.


file last_access based view in filetree.php

Do we have any option to replace mtime with last-access time.

something list total size vs last access over 10y, 5-10 years ..


feat(relational-states): use relational states (table_id) to replace operator_id in hash join.

…_id in hash join.
What's changed and what's your intention?
Replace operator_id to table_id for HashJoin.
Motivation: https://singularity-data.quip.com/tlLHAbb9VQF5/RFC-Store-States-as-a-Cell-based-Relational-Table

Add a fields table_ids in StreamNode proto. This is designed to replace operator_id in future.
Compute how many table ids should be allocted in fragmenter. First calculate the num table ids in each fragment, then the total will be num of actors * each fragment table ids number.
Allocate a [table id, table_id + interval] from id manager. Just like fragment id and actor id, local table id + offset to get the unique table id.
HashJoin read table ids from proto and use as keyspace.

Some minor issues might fix:

Too many as u32, as u64. We should better unify the type and avoid casting.
Because we only enable hash join as table states, there are some if ...  hack in the code. It might be eliminated when we extend to all operators.
some API tweak: HashJoin might create table keyspace inside new  instead of accept as parameters

Have discussed with @yezizp2012 , we do not need to hanlde fail over. As long as it is in the proto, meta will persist it.
Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

From my perspective, only stateful executors have table id, while all executors have operator_id.


added fips-noisepp to registry

What are you using all those noise-libs for? :D

trying to build a voxel engine

using this https://github.com/nothings/stb/blob/master/stb_voxel_render.h ? if yes let me know how it works :)

Nope, currently PolyVox - but I will try that one, too


Global node click based on child nodes length

It's logical to allow clicking every node in global view. Right now it's available for every node except central node. Better approach would be to allow interaction based on child nodes. If there is no child nodes there is no point in showing empty region view. And if there are any nodes in region view, we're allowing interaction.

Closed on favour of #59


Adding a course about "Information Retrieval"

Hey everyone. I am a junior BSc student, and currently, I am taking a course about Information Retrieval. The course relies on the famous Stanford textbook, which is however available for free.
By looking at the curriculum here, I found no course related to this topic. I believe it must be listed under the "Core Applications" section because it is considered an essential application of the data structure and database theories. This topic by the way seems to be underrated, but still crucial.
This is the homepage of the textbook and it includes two other links for published slides and assignments from two different universities.
https://nlp.stanford.edu/IR-book/information-retrieval-book.html
I wonder if it can be listed in the curriculum.

Hi Hamzakat,
Glad to hear that you are taking a course you find fascinating and valuable. And to hear of free high quality materials.
As our contributing guide points out, successful proposals to change the curriculum will refer to our curricular guidelines. You can read an example of such a successful proposal here (and find many other such RFCs in closed issues).
I'm closing this issue for the moment, but feel free to reopen it with additional information.


Collapse doesn't work if target/id attribute starts with a number

After upgrading from 4.1.1 to 4.1.2, collapse no longer works if the target/id combination starts with a number. I can provide an example that you can run in codepen. I have tried to paste the full html sample in here but it doesn't display correctly.

Example Codepen

Because it's not a valid ID attribute value. The same issue as in #27208.

Yep that's because currently we use native methods to query our DOM elements (querySelector and querySelectorAll for more information about correct selector see: https://github.com/twbs/bootstrap/blob/v4-dev/site/docs/4.1/getting-started/javascript.md#selectors