WindowsEventEngine Client implementation

Doing this work inspired a few changes I'd like to make in later PRs.

A bazel macro for EventEngine test suite definitions, which will create the right bazel libraries/tests/binaries for all of the specialized tests and tools. The two factory definitions are a bit redundant, and should only need to be defined once.
ResolvedAddress needs a mutable alternative, and/or a redesign as a simpler struct. Some copying could be eliminated.
The echo client is added here to inspire reviewer confidence, but will probably be landed in a separate PR. The test suite's ConnectToNonExistentListenerTest passes, but since there is no Listener implementation yet, the rest do not. The WindowsEventEngine-specialized echo client works.

Looks ok, I'd like us to take a consistent stance on std::atomic allowed operations however, and I don't think ++, -- should be in that set.

Removed, given the 2v1 stance. I didn't find any other uses of atomic operator++ in src/core. I don't think this is easily lintable, so I'd recommend creating a gRPC style guide if something like this is going to be enforceable.


add metrics support with example

This adds a message-count-7-days metric as a Deployment label. Example:
            - apiVersion: apigeeregistry/v1
              kind: Deployment
              metadata:
                name: foo-com
                labels:
                    apihub-gateway: apihub-google-cloud-apigee
                annotations:
                    apigee-envgroup: organizations/apigee-apihub-demo/envgroups/foo
                    apigee-environment: organizations/apigee-apihub-demo/environments/test-env
                    apigee-proxy-revision: organizations/apigee-apihub-demo/apis/petstore/revisions/1
                    message-count-7-days: "13"
              data:
                displayName: test-env (foo.com)
                endpointURI: foo.com

Fixes #212

This is support and an example. My thought was we would update under a new PR once we decide on a standard metric set.


Add a label extraction interface

The go-metrics interface is more suited to statsd style metrics where variables are in the metric name.
This has cause an issue in Vault instrumentation (https://github.com/hashicorp/vault/issues/7928) where the number of metrics descriptions can exceed the stackdriver quota of 500 (https://cloud.google.com/monitoring/quotas).
This introduces a way to rewrite the given metric names to extract static labels.
 I'll cut a v.0.2.0 tag with the potentially breaking change (BucketFn now accepts a []string instead of a string) after more testing in case I end up needing to change ExtractLabelsFn interface.


Logical network segmentation

Introduction
Network segmentation has been in existence for many years. If you are a network engineer or a Sys admin segmenting a network is a very essential skill to have in your toolbox. There are two ways of segmenting a network. The first method is physical network segmentation and the other method is logical network segmentation. In this article we are going look in depth about logical network segmentation.
Key takeways
1.An overview of what is segmenting.
2. Reasons for network segmentation.
3. An in depth understanding of what is logical network segmentation.
4. Example of cases when to use logical segmentation.

good topic @josep562 - approved

@josep562 just wanted to follow up on this topic as I'm clearing up the queue where possible?


Get longer-term NDVI data

Either landsat or AVHRR.
Initial work on this is started in setup_ndvi_data.R and the README in ./data/ndvidata/.
LTDR appears to provide daily NDVI data back to 1981 using a combination of AVHRR and MODIS data. Data is available via FTP as one hdf file/day (25-150 MB/file depending on the satellite) and are split up by satellite (with different satellites covering different time periods). The NDVI data is in the AVH13C1 files.

There is an old R package that hypothetically helps with some of this, but it doesn't appear to have been touched in years and has been removed from CRAN. :sob:

@skmorgane, @emchristensen, @davharris, @sdtaylor, @MarconiS: Any thoughts on the relative value/effort of these two different sources of data. My impression at the moment is that the LTDR data will be harder to work with (we'll have to handle creation of composites which I imagine will take a fair bit of work to do well and also probably quite a bit of computer time), but it also goes back an additional 8 years and the shift from 26-34 years of time-series is fairly substantial. Basically I'm contemplating where to invest time/energy given the tradeoffs and would value any thoughts you have on the matter.

@ethanwhite  Is there a need to have something like 16-day NDVI composite images going back to 1981? Creating those images would be a lot of work, but extracting values for ~2000 points and compositing just that data seems easy enough.

Is there a need to have something like 16-day NDVI composite images going back to 1981?

No, now that you mention it, for our purposes I think we just need to composite the points. So, there probably isn't a compute issue, but we'd still need to understand and code the rules for doing the compositing

8 years may be non negligible, indeed... but assuming a bunch of things I guess. We have to assume that the radiometer data collected by AVHRR2 were precise enough to be included in the same time series of AHVRR3 and/or MODIS, and that no artifact comes out of the composing/correcting. I am wondering how much higher uncertainty may grow doing the compositing by ourselves (if for compositing you mean cloud covering removal, and all kinds of corrections, otherwise sorry for the misinterpretation). For what I can grasp performing all the corrections is not only time consuming, but also "risky", especially if it involves only a subset of data (couldn't it lead to patterns driven by artifacts?)... In these cases, if I have enough data, I usually prefer to work with fewer but highly reliable ones (which I guess may be the case of 26  years long time series).

The folks producing the LTDR data are, if I understand things correctly, supposed to be handling the differences between instruments to make the overall time-series comparable.
I agree with @MarconiS's concerns about the challenges of doing the compositing ourselves. We might want to bring in a remote sensing person to help with that if we go in that direction.

@MarconiS It looks like LTDR already does a bunch of corrections for atmosphere, different satellites, and many other things. I can't find a definitive paper on it, but see this presentation. The compositing on our end would just entail sub setting into the data into, for example, 16 day intervals so we get a decent amount of cloud free observations.
The compositing algorithm looks very straightforward, according to this document, pg. 6.

The current procedure for generation of composited, AVHRR-based, NDVI products
is the maximum value compositing (MVC) technique.  This is accomplished by
selecting, on a pixel by pixel basis, the input pixel with the highest NDVI value as output
to the composited product.  The procedure generally includes cloud screening and data
quality checks

The LTDR data includes a QC flag for each pixel, which I'm guessing also has a value for clouds, but I will check on that.

Ok! I'll check it better in the next days; if you are right @sdtaylor, and it is not that complicated and/or time consuming, I guess it would be great to give it a try (it is about 30% increase in temporal horizon, and more than 30 years time series after all)! If you want @ethanwhite I can email a couple of researchers I've worked with in the past who are very strong in remote sensing stuff

If you want @ethanwhite I can email a couple of researchers I've worked with in the past who are very strong in remote sensing stuff

Go for it. It would be great to get some external perspective on this.

Bad news and great news!
Both Dario Papale and Gaia Vaglio Laurin suggested me not to try an improvised compositing of any remote sensing data; way too risky. However here comes the good news. 1) corrected data should already been found in the Gimms3 dataset for NDVI, LAI and fPAR (harmonization of the data done by Ranga Myani); 2) Frederic Baret worked on that in a very nice way years ago (Geoland-2 project). His site is down, but data were open access; hence we can try to contact him and ask harmonized data of our interest!

Here is a really good paper comparing GIMMS, LTDR, and 2 other AVHRR products. Most of the paper says that all AVHRR prodcuts compares reasonably well to Landsat. But one of the last points definitely applies to what we're doing here.

The evaluation against Landsat–NDVI suggests that the LTDR V3 data set is the most accurate in terms of absolute values and the GIMMS data set the most accurate for assessing temporal change. MODIS–NDVI performed better than any AVHRR–NDVI data set.

Which means that, on a pixel to pixel comparison to the "true" landsat values, LTDR is better in a single time point. But on a pixel to pixel comparison comparing the difference between 2 time points, GIMMS was better. I'm not sure if they tested GIMMS v3, so it may better now in the 1st part.

After some digging I think I've found monthly GIMMS data from 1981-2013:
http://ecocast.arc.nasa.gov/data/pub/gimms/
Other things I came across in the search:

GIMMS data, but only MODIS based so stopping in 2000. Maybe useful for filling in the last couple of years if comparable.

http://glam1.gsfc.nasa.gov/
ftp://gimms.gsfc.nasa.gov/MODIS/

Descriptions of data back to 1981, but with broken data links

I just went from installing the gimms package to having the full ndvi time series for portal in about an hour (with the help of the hipergator), so +1 there for GIMMS.

OK, given Sergio's colleague's recommendation, the paper Shawn found, and the ease of working with the data, let's go ahead and start with GIMMS for the time-being.
@sdtaylor, since you've got things working well already would you mind adding a function/script to extract the GIMMS data for all BBS routes in the SQLite database (or just all BBS routes). Let's go ahead and get all of the entire monthly time-series from 1981-present (or almost present) for each route.

Yep, I'm on it.

For GIMMS there is a little pre-processing that needs to be done.

There are bimonthly NDVI values. For our purposes I think we can just average them to get 1 value a month.
It has a quality flag and it's mostly good across all years and sites. But a large chunk is 	FLAG = 3 (NDVI retrieved from spline interpolation) Which I think means a cloudy value was filled in using surrounding dates of the same pixel. I suspect it's probably fine to use.

Should I average monthly values and filter out the bad flags in the get_ndvi script? Or would you rather that be done in the analysis scripts?

and for future reference here is the official citations for GIMMS 3g,  Pinzon & Tucker 2014

Should I average monthly values and filter out the bad flags in the get_ndvi script?

That would be great!

I agree that for our purposes using the spline interpolation should be fine.

#23
This PR replaces MODIS NDVI with GIMMS. But there is still the potential to integrate MODIS back in somehow to fill in the years 2013+ that GIMMS doesn't have yet.

Completed in #23. At some point we will want to come back and fill in 2013+ as @sdtaylor notes, but I'm going to go ahead and close this and replace with a more specific issue.


Receiving 403 error when downloading file

Using Amplify Storage in an iOS Swift app, we are able to upload files from the mobile app to S3 with the access level set to private. However, trying to download a file from the same bucket fails with a 403 error. Attempting to download the same file that was uploaded from the app also fails with a 403.
We have tried downloading to in-memory data and to a file with the same results.
Here's the relevant file download code, taken almost directly from the current Amplify iOS documentation:
        let options = StorageDownloadFileRequest.Options(accessLevel: .private)

        let downloadToFileName = FileManager.default.urls(
            for: .documentDirectory,
            in: .userDomainMask)[0]
            .appendingPathComponent(attachment.filename)

        let storageOperation = Amplify.Storage.downloadFile(
            key: attachment.key,
            local: downloadToFileName,
            options: options)

        progressSink = storageOperation.progressPublisher.sink { progress in print("download progress: \(progress)") }
        resultSink = storageOperation.resultPublisher.sink {
            if case let .failure(storageError) = $0 {
                print("Storage download failed: \(storageError.errorDescription)")
            }
        }
        receiveValue: { data in
            print("Storage Download Completed: \(data)")
        }

Debugging into the AWS code I can see that the current user's Cognito Identity ID, correct access level, and S3 file key are all being used.
Turning on verbose logging for Amplify didn't appear to provide any helpful information about the failure.
Any help from AWS would be appreciated.

Additional information:
I switched the app over to use the CocoaPods libraries instead of Swift Package Manager to see if that made a difference -- it did not, still getting the 403 error.
Also, I attempted to look at the IAM policies associated with Amplify Storage to see if something looked awry there. However, I cannot find the policy in IAM. Should I be able to find it? The policy name in the nested Amplify Storage CloudFormation stack does not seem to exist in IAM, or at least, I cannot find it.
Finally, I looked at the permissions and ACL on the Storage S3 bucket to see if something was off. Here's what I see -- is this correct for a bucket created by Amplify Storage? Should there be additional permissions listed here? This AWS account is owned by the client and I have occasionally found some permissions were not available in various AWS services, so please confirm if this ACL looks correct per what Amplify Storage expects?

Digging into this further I discovered the root issue. The inline IAM policy that should give read access (s3:GetObject) does not exist and is not associated with the authRole used by Cognito.
The readPolicy is listed as a parameter in the CloudFormation template but is not referenced anywhere else. Also, note that the first letter of the read policy is not capitalized like the others -- this hints at the fact it may not have been modified or updated when the other policies were. Just a guess on my part.

The CloudFormation resources show the read policy was not created:

Looking at the resulting policies attached to the IAM authRole show the read policy is in fact missing:

I added the s3:GetObject permission to the private policy:

With this addition, Amplify Storage now successfully downloads the files from the storage bucket. Prior to making this change I added the AWS S3FullAccess policy to this role to test it out, and when that was successful I looked for a more granular fix.
It seems that the read policy is not being generated or attached to the authRole as would be expected. Please investigate why this is as the expectation is that all of the permissions required to perform reads and writes should be setup properly by the Amplify framework.
While making this change has fixed the immediate issue, any updates we make to Amplify Storage or Auth are likely to overwrite this, so we need this fixed in the tool.

hi @testflyjets, could you let us know which answers did you provide to the questions related to the kind of access for the users when you provisioned S3 through amplify add storage?
What kind of access do you want for Authenticated users? `create/update, read, delete`

I suspect if you only allowed "create/update" for Authenciated users then they won't be able to read the data.

@lawmicha  Great question, and I wondered that myself, but I didn't see any way to go back and check that since I did it weeks ago. I vaguely recall thinking to myself, "Shouldn't create/update include read?" but that may just be hindsight.
Is there a way to update this now without trashing the existing auth + storage configuration if that was the case?

Hi @testflyjets, could you try amplify update storage to update the options and then amplify push to apply the changes. Let us know if this works!

Thanks @lawmicha that's exactly what I did. I turned on read as well as delete since we'll need both of those. All is well now, so thanks for pointing the issue out to me. I appreciate you speedy response.

glad it is working for you! Closing this for now, with doc update issue over here https://github.com/aws-amplify/docs/issues/3317


Import streets-houses from red-lists

Import correct streets-houses from red-lists
#273 Loaded test data from UkrPost

not actual


floating point from_chars not supported on clang

What
Use fast_float library for floating point from_chars implementation on all platforms.
Why
LLVM libc++ doesnt have an implementation of from_chars for floating point types.

Disable, just use fixed type UDLs


Debuggee is running...

Debugger somehow never gets into a state where I can actually break all into it.
It stays there after "Task "Driver Post Install Actions" completed successfully
Pressing Break all - in the debug menu does nothing !!!
Any suggestions to what could be wrong ? I just made a standard wizard kmdf driver and followed above changes

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

ID: 81568a12-c39e-a18f-8f33-c54545f14bac
Version Independent ID: 73217b22-1795-b5d0-65cb-1984f38dc661
Content: Write a universal Hello World driver (KMDF)
Content Source: windows-driver-docs-pr/gettingstarted/writing-a-very-small-kmdf--driver.md
Service: unspecified
GitHub Login: @nabazan-microsoft
Microsoft Alias: windowsdriverdev

Hi @serup , sorry you're having this issue with trying to debug the sample driver. To clarify, you deployed the driver to a test computer, then, on the host computer, tried to hit F5 to debug within Visual Studio? Knowing how you got to where you are can help us figure out what steps in the documentation are unclear. Thanks!

Hi again @serup , we've updated the steps for deploying and debugging the example driver for this topic to reflect the recommended debugging method. The changes should be live soon. Let us know if this helps you break into the debugger and experiment with the commands.
If you're still having issues, we recommend posting your question on the following forums, where other driver developers and Microsoft engineers can be found. The community there is very responsive.
Windows Hardware WDK and Driver Development
OSR's ntdev List
Thanks for the feedback in improving the docs!


Adding se00 schema

Added the se00 schema based on how senv is forwarded. The main difference here is that timestamps are used instead of datetime objects.

Update changes.md with se00 update


Which version of SqlPackage.exe runs with only .NET 4.5.2 installed?

We are attempting to run a psh script containing sqlpackage command via Ansible on a tightly controlled server to deploy a dacpac from said "jump" server to a target instance on a database server.
A return value of<PHONE_NUMBER> is encountered which indicates .NET 3.5 Framework needs to be installed on the "jump" server.  Can this be verified?  (I just verified it to need .NET 4.6 not 3.5)
With respect to its dependencies, what is the version history of sqlpackage.exe?  Where can we find more information?

With direct execution of sqlpackage.exe, we found that this version requires .NET 4.6.
Our server can only run .NET 4.5.2.  Which version of sqlpackage.exe should we install?

@Guy--L -- Guy, thank you for your feedback.  Please provide a link to the documentation in question.
You may find information regarding your question here:

DBA Stack Exchange
Stack Overflow

Thank you for your response.  I believe you need a new page with a comprehensive list of the versions, the path under which they install and the .NET versions required to run sqlpackage.exe.
Indeed, is the source of sqlpackage on github anywhere?  Perhaps I can determine some of the contents of the proposed SqlPackage Verions and Dependencies page.

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Add codecs.pxd

The comments are taken from the C API documentation
(https://docs.python.org/3.9/c-api/codec.html).

LGTM, thanks.


add UuidConverter to support UUID

Related issues
Fixes #660
Describe the PR
There was an error before because of the UUID.
Failed to instantiate instance of destination java.util.UUID. Ensure that java.util.UUID has a non-private no-argument constructor.
This PR fixes the errotrby adding an UuidConventer to support UUID.

Merge to master branch by https://github.com/modelmapper/modelmapper/commit/1b8db93be9a5db810ac56db6ad82392af715b9a7


Re-enter API code - where?!

I'm sorry to ask such a simple question, but I cannot find the answer.
I'e had to re-issue the API code on the myenergi website.  I'm struggling to find where I can update Home assistant with the correct code.  Any help appreciated.  I'd rather not have to remove and reinstall Myenergi.

If you go to add-on, remove the integration and then add it back it will prompt you during install for the username and password again then all entries will return as before and your dashboard will resume.

Shouldn’t you close this now?


splunk_hec proxy parameter

Proposed changes
Added functionality to use proxy variables from the configuration file when creating connections.
Similar to #147
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I have read the CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Hello,
The test was failing because there is a dependency with other project: splunk-connect-for-kubernetes

Hello, Could you not update the Gemfile.lock file?
we update gems on needed basis.


Improve type safety

WIP: improving UI -> ExtendScript type safety by adding evalFunction as a typesafe alternative to evalES, that imports function types from your script files.
evalFunction(functionName, ...args);

Note
I also experimented with adding some warnings if you accept or return non JSON primitives, which works well but might end up being confusing without custom error messaging.
...args: Parameters<Scripts[ScriptName]> extends JsonPrimitive[] ? Parameters<Scripts[ScriptName]> : never

Caveats
Since we're now importing types between src/js and src/jsx, type-checking with tsc gets a bit messed up (but things seem to work fine in VS Code).
This is mitigated by including types-for-adobe at the root level, but some errors persist due to conflicting app definitions between programs.

Personally I just don't type check on build, the editor warnings are enough, and the type safety benefits between UI and script functions are well worth it 😅  But will see if I can fix those remaining errors!

Fixes #27

Thanks so much for all your work on this Justin, much appreciated! Looking forward to removing my custom solution and updating to this.
An amazing improvment to an already best in class solution!!


Implemented a static cache making sure it's reset on object destruction

Alternative implementation to https://github.com/loupe-php/loupe/pull/130.
It's not really beautiful but static caches never are :/
@daun would love to get some feedback on the stats you get and also regarding the implementation of course.

Looks great! It's not that pretty, but if it's faster, who cares 🤠 Will run a few benchmarks in a minute.
One question: what's the reason the call to StaticCache::enterContext($this) must happen inside each method call to the Loupe instance?  As opposed to doing it once in the constructor.

One question: what's the reason the call to StaticCache::enterContext($this) must happen inside each method call to the Loupe instance? As opposed to doing it once in the constructor.

Think of an application that works with two or more $loupe instances at the same time in the same process:
$loupe1->addDocument(...);
$loupe2->search(...);
$loupe3->addDocuments(...);
...

I see, that would allow switching back and forth without clearing the cache in between. Nice.

I'm seeing about a 1-2% speed bump for queries across the board. The very obvious question is of course if that's worth all the acrobatics and maintenance burden going forward.
What are you getting?

Similar 😊  I would argue that the work is done now anyway and I'm pretty sure there might be other use cases for a cache where we'd again needed such a static cache management. So I'd merge that for now but we can of course still remove it again if we have weird side-effects or encounter any other issues.

Alright, I'll close the other one.

Thanks for the valuable feedback @daun!


Please provide AI support for python language server Jedi

Jedi is a very good intelligent completion library for Python, but currently the plugin only supports LSP (Microsoft Python Language Server). If you can provide AI support for Jedi, this will enhance the Python programming experience (because PLS is not very stable at the moment) , I prefer Jedi)

@CatNofishing - IntelliCode also supports new Pylance language server https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance. Have you tried it? Thanks.

@MikhailArkhipov   I tried it, but I did not find that it has special support for pylance😂

@CatNofishing - I'm assuming you mean that you are not seeing IntelliCode stars in your completion list when you install IntelliCode for VS Code alongside the Pylance language server, for cases where you would have seen them before under the MPLS? Can you confirm and give examples please? That will help us track things down. It would also be useful to see the contents of your  VS IntelliCode output window (you can see this by switching to the Output tab in VS Code and switching the drop down to "VS IntelliCode"). This will give diagnostic information about the success or failure of loading IntelliCode for your case.
Thanks!

I agree. It should definitely support Jedi as well.

I agree! The more the merrier :)
Jedi is great!

I agree, Jedi is great. I'd love to see it working with intellicode!


ENH: Allow subclassing MainWindow

Over in MNE-Python we want to subclass the MainWindow that is instantiated by BackgroundPlotter to override event processing (https://github.com/mne-tools/mne-python/issues/9182#issuecomment-805737809) .This PR makes it possible to pass the class to use for instantiation.

@GuillaumeFavelier ready for review/merge from my end!


Provide indication of whether any CAN traffic is happening and on which of the connected transports

This is to make issues like #402 easier to debug.

This is easy to pull from PyCyphal via Transport.sample_statistics()


Fix CI

Currently, w hen deploying KotlinTest, the CI is broken. Whenever it tries to execute ./gradlew test, it will become stuck at the first test it tries to execute, and never finishes.
I've done some digging, and I found that the class JUnitTestRunnerListener had an addition from PR #449 that makes it kinda messy:
Line 222:
descriptor = object : AbstractTestDescriptor(id, description.name, source)

When creating this descriptor with a source, the test never completes. I'm not sure what's causing this, but if we create the descriptor with
descriptor = object : AbstractTestDescriptor(id, description.name)

It will work again.
I wasn't able to investigate further, but giving this information may be helpful to solve it. I'll keep digging, but I'm not sure how tests are actually executed

@sksamuel

Ok, I have some more information on this issue:
Currently, source is created using
    val source = ClassSource.from(klazz?.java) ?: null

For some reason, this source only fails if TestType is TestType.Test. It'll never complete the test. However, if we change it to null on TestType.Test, something interesting happen, because it works:
  val source = if (type == TestType.Test) {
      null
    } else {
      ClassSource.from(klazz?.java) ?: null
    }

I have no clue on why this works. But using this way, we're able to goto source on any descriptor that's not the final one (test one).
I'm still trying to find a real reason for this, but having this documented may help any of you to find it.
@sksamuel I also believe that JUnitRunnerListener needs a refactoring. It's pretty hard to understand right now :x

We are green again!


Create contributing chapter

It's here https://github.com/GridTools/gt4py/blob/master/CONTRIBUTING.rst

and here is a list of contributors https://github.com/GridTools/gt4py/blob/master/AUTHORS.rst


Add implementation for binary ops.

The binary tests were ported form webnn-polyfill.
Should we update expected data of double precision which then would benefit to WPT tests?
@huningxin PTAL, thanks.

Thanks @huningxin, I will update this PR based on PR #2.


Update README.md

Added: Documentation (MDN) and Android Dev with Java.

Added the udacity course for android: https://www.udacity.com/course/developing-android-apps--ud853


Propagate the don't write bytecode files flag to generated projects.

If bytecode files are not written out when building projects then that option is propagated through to th generated projects. This means when building from Visual Studio, it too won't write out the bytecode files.
Without this change, you will likely find yourselves having no .cakec files written out when building from
a terminal but after building from Visual Studio, the files will be created.

I should have mentioned this change is incompatible with Python 2.5
However in Issue #11, you state:

We currently require Python 2.7 to run but this is now quite old.

Even if this isn't true, the last release of Python 2.6 was in 2013, so while it would be possible extend this change to work in Python 2.5, it seems like pointless exercise as Python 2.5 is well out of its support cycle.


Add loading indicator on save proccess

This PR is connected to the ticket.
feat: Add loading indicator on saving

create new LoadingDots components
add submitting props to the component (coming from final-form library)
add conditional content rendering in save button

There were also a conversation about adding some kind of 'Saved' indicator, but I think that might be a separate PR if the team agrees on that.

I'll test this out. Thanks for adding this! Definitely a much needed feature.

This looks great! I like the animation.


flax.errors.InvalidRngError: rngs should be a dictionary mapping strings to jax.PRNGKey

This error occurs when I tried to run cifar10 example on GPU (TITAN XP)
Error log
Traceback (most recent call last):
  File "vmoe/main.py", line 71, in <module>
    app.run(main)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/absl/app.py", line 303, in run
    _run_main(main, args)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/absl/app.py", line 251, in _run_main
    sys.exit(main(argv))
  File "vmoe/main.py", line 64, in main
    trainer.train_and_evaluate(config=FLAGS.config, workdir=FLAGS.workdir)
  File "/mnt/cephfs/home/cascol/working-directory/MoE-in-MoE/vmoe/vmoe/train/trainer.py", line 434, in train_and_evaluate
    tree=jax.eval_shape(train_state_initialize_fn, train_state_rngs),
  File "/mnt/cephfs/home/cascol/working-directory/MoE-in-MoE/vmoe/vmoe/train/trainer.py", line 203, in initialize
    variables = model.init(rngs, inputs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/jax/_src/traceback_util.py", line 165, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/flax/linen/module.py", line 1124, in init
    method=method, mutable=mutable, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/jax/_src/traceback_util.py", line 165, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/flax/linen/module.py", line 1092, in init_with_output
    {}, *args, rngs=rngs, method=method, mutable=mutable, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/jax/_src/traceback_util.py", line 165, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/flax/linen/module.py", line 1061, in apply
    )(variables, *args, **kwargs, rngs=rngs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/flax/core/scope.py", line 706, in wrapper
    with bind(variables, rngs=rngs, mutable=mutable).temporary() as root:
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe/lib/python3.7/site-packages/flax/core/scope.py", line 684, in bind
    'rngs should be a dictionary mapping strings to `jax.PRNGKey`.')
jax._src.traceback_util.UnfilteredStackTrace: flax.errors.InvalidRngError: rngs should be a dictionary mapping strings to `jax.PRNGKey`. (https://flax.readthedocs.io/en/latest/flax.errors.html#flax.errors.InvalidRngError)

My Enviroment that may concern
cudatoolkit               11.1.1               h6406543_8    conda-forge
flax                      0.3.6                    pypi_0    pypi
jax                       0.2.27                   pypi_0    pypi
jaxlib                    0.1.75+cuda11.cudnn805          pypi_0    pypi
optax                     0.1.0                    pypi_0    pypi
pytorch                   1.8.0           py3.7_cuda11.1_cudnn8.0.5_0    pytorch

I tried tracking the error and found weird bug (the image on top is the result while setting up training, the image at the bottom is what I think the result should look like)

We use a few experimental features from Jax/Flax which are not yet part of any official release. Upgrade the following packages from GitHub:
pip install -q --upgrade git+https://github.com/google/jax.git;
pip install -q --upgrade git+https://github.com/google/flax.git;
pip install -q --upgrade git+https://github.com/google/CommonLoopUtils.git;

Where should I set up jax_config.jax_enable_custom_prng=True to use these experimental features?

We use a few experimental features from Jax/Flax which are not yet part of any official release. Upgrade the following packages from GitHub:
pip install -q --upgrade git+https://github.com/google/jax.git;
pip install -q --upgrade git+https://github.com/google/flax.git;
pip install -q --upgrade git+https://github.com/google/CommonLoopUtils.git;

You shouldn't set jax_enable_custom_prng. We use jax_default_prng_impl.
https://github.com/google-research/vmoe/blob/bff362c6abfaf6c518f01e09ea0c6a7b21b8c415/vmoe/main.py#L46
The problem is that the current release of FLAX doesn't work well with this, that's why you need to install FLAX from github. I fixed it less than a week ago: https://github.com/google/flax/commit/4d6400cc2e378d9cacf2702629c3b57b70661053
If it's of any help, this is how I installed all the requirements to try training a model on a GCE instance: https://github.com/google-research/vmoe/blob/main/vmoe/scripts/install_gce.sh

Hi, thanks for your patience.
Following your instruction I install all requirements as follows
# install cudatoolkit11 cudnn8.0.5
conda install pytorch==1.8.0 torchvision==0.9.0 torchaudio==0.8.0 cudatoolkit=11.1 -c pytorch -c conda-forge --yes

pip install --upgrade jax[cuda11_cudnn805] -f https://storage.googleapis.com/jax-releases/jax_releases.html

pip install --upgrade git+https://github.com/google/jax.git
pip install --upgrade git+https://github.com/google/flax.git
pip install --upgrade git+https://github.com/google/CommonLoopUtils.git

pip install absl-py cachetools chex einops ml_collections numpy optax pandas scipy tensorflow-cpu tfds-nightly

However, another bug occurs when I tried to run cifar10 example on GPU, namely UNIMPLEMENTED: Requested AllToAll not implemented on GPU
Here is the error log
2022-01-20 16:40:23.258557: E external/org_tensorflow/tensorflow/stream_executor/cuda/cuda_dnn.cc:4584] Disabling cuDNN frontend for the following convolution:
  input: {count: 128 feature_map_count: 3 spatial: 128 128  value_min: 0.000000 value_max: 0.000000 layout: BatchDepthYX}
  filter: {output_feature_map_count: 768 input_feature_map_count: 3 layout: OutputInputYX shape: 16 16 }
  {zero_padding: 0 0  pad_alignment: default filter_strides: 16 16  dilation_rates: 1 1 }
  ... because the current cuDNN version does not support it.
2022-01-20 16:40:24.573497: E external/org_tensorflow/tensorflow/stream_executor/cuda/cuda_dnn.cc:4584] Disabling cuDNN frontend for the following convolution:
  input: {count: 128 feature_map_count: 3 spatial: 128 128  value_min: 0.000000 value_max: 0.000000 layout: BatchDepthYX}
  filter: {output_feature_map_count: 768 input_feature_map_count: 3 layout: OutputInputYX shape: 16 16 }
  {zero_padding: 0 0  pad_alignment: default filter_strides: 16 16  dilation_rates: 1 1 }
  ... because the current cuDNN version does not support it.
Traceback (most recent call last):
  File "vmoe/main.py", line 71, in <module>
    app.run(main)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/absl/app.py", line 312, in run
    _run_main(main, args)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/absl/app.py", line 258, in _run_main
    sys.exit(main(argv))
  File "vmoe/main.py", line 64, in main
    trainer.train_and_evaluate(config=FLAGS.config, workdir=FLAGS.workdir)
  File "/mnt/cephfs/home/cascol/working-directory/MoE-in-MoE/vmoe/vmoe/train/trainer.py", line 492, in train_and_evaluate
    datasets['train'].element_spec['labels']))).compile()
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/_src/api.py", line 521, in compile
    self._lowering.compile(), self.in_tree, self.out_tree,
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/interpreters/pxla.py", line 2056, in compile
    _allow_compile_replicated=_allow_compile_replicated)  # type: ignore
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/interpreters/pxla.py", line 2142, in from_hlo
    compiled = dispatch.compile_or_get_cached(backend, computation, compile_options)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/_src/dispatch.py", line 582, in compile_or_get_cached
    return backend_compile(backend, computation, compile_options)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/_src/profiler.py", line 206, in wrapper
    return func(*args, **kwargs)
  File "/mnt/cephfs/home/cascol/anaconda3/envs/vmoe_new/lib/python3.7/site-packages/jax/_src/dispatch.py", line 537, in backend_compile
    return backend.compile(built_c, compile_options=options)
RuntimeError: UNIMPLEMENTED: Requested AllToAll not implemented on GPU; replica_count: 1; partition_count: 8, group_mode: kCrossPartition, operand_count: 8; NCCL support: 1; first operand array element-type: BF16

Mmm. This seems to be a current limitation of JAX with a GPU backend.
I've tested the on a GPU, but only using 1 device, thus AllToAll is not used.
If you still want to use two GPU devices for taking advantage of data parallelism, and assuming that the model fits entirely on a single one of your GPUs, you could set config.num_expert_partitions = 1. This should prevent AllToAll from being needed, but you'll maybe have to reduce the batch size.

I have changed config.num_expert_partitions = config.model.encoder.moe.num_experts to config.num_expert_partitions = 1.
However, it does not solve the above error.

Mmm. This seems to be a current limitation of JAX with a GPU backend.
I've tested the on a GPU, but only using 1 device, thus AllToAll is not used.
If you still want to use two GPU devices for taking advantage of data parallelism, and assuming that the model fits entirely on a single one of your GPUs, you could set config.num_expert_partitions = 1. This should prevent AllToAll from being needed, but you'll maybe have to reduce the batch size.

@Cascol-SCUT I noticed your error message has BF16 at the end. My understanding is BF16 is only supported by TPU. Since you are using GPUs I think you should set the bfloat16 to False in the config file to proceed.

Thanks for your reply! It solves the problem.

@Cascol-SCUT @jpuigcerver I noticed the error message has BF16 at the end. My understanding is BF16 is only supported by TPU (or at least have limited support from CUDA or Jax). Since you are using GPUs I think you should set the bfloat16 to False in the config file to proceed. Here's a quick look at https://machine-learning-note.readthedocs.io/en/latest/blog/cheatsheets/Nvidia_GPU.html.
It seems like BF16 is only supported in Amphere GPUs. I don't think config.num_expert_partitions is the main problem but it's worth a try as well. Correct me if I'm wrong.


KD-Tree

Codecov Report

Merging #9 into dev will decrease coverage by 5.15%.
The diff coverage is 58.97%.

@@             Coverage Diff              @@
##                dev       #9      +/-   ##
============================================
- Coverage     84.17%   79.02%   -5.16%
- Complexity      147      170      +23
============================================
  Files            23       26       +3
  Lines           455      572     +117
  Branches         38       51      +13
============================================
+ Hits            383      452      +69
- Misses           69      113      +44
- Partials          3        7       +4

Impacted Files
Coverage Δ
Complexity Δ

...abs/introtoprogramming/lab5/scene/SceneObject.java
75% <0%> (-6.82%)
5 <0> (ø)

...ntrotoprogramming/lab5/object/OptimizedObject.java
0% <0%> (ø)
0 <0> (?)

.../java/labs/introtoprogramming/lab5/object/Box.java
96.07% <100%> (+0.42%)
17 <2> (+2)
:arrow_up:

...va/labs/introtoprogramming/lab5/object/Sphere.java
91.3% <100%> (+1.3%)
6 <1> (+1)
:arrow_up:

.../labs/introtoprogramming/lab5/object/Triangle.java
100% <100%> (ø)
8 <1> (+1)
:arrow_up:

...java/labs/introtoprogramming/lab5/tree/KDTree.java
40% <40%> (ø)
10 <10> (?)

...java/labs/introtoprogramming/lab5/tree/KDNode.java
88.46% <88.46%> (ø)
9 <9> (?)

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 3d1adb3...f691c40. Read the comment docs.

 Tree


Restructure dependencies in MadNLP

I think currently MadNLP comes with too many dependencies, which has a significant impact on the precompilation time of the package. Unfortunately, Julia does not support properly conditional dependencies (see the long awaited issue https://github.com/JuliaLang/Pkg.jl/issues/1285). But, since 2020, we can define several packages with different UUID under the same git repo (see this discussion, or this PR for a practical example).
I would suggest to refactor MadNLP the following way, by keeping all the code in this repo.

MadNLP/src would implement only the core interior point algorithm, interface to usual linear solvers (as LapackCPU, or IterativeSolvers) and the lightweights interface (NLPModels and MathOptInterface).
we would move in a new directory MadNLP/lib all "complicated" deps. In MadNLP/lib, each subfolder would be registered as Julia package with its own UUID in Julia's registry.

For instance, we could structure MadNLP/lib as
lib/MadNLPPlasmo    # interface to Plasmo
lib/MadNLPCUDA      # interface to CUDA's Lapack
lib/MadNLPHSL         # interface to HSL
lib/MadNLPMumps    # interface to MUMPS
lib/MadNLPPardiso    # interface to Pardiso

Leading to 5 subpackages ... For the three linear solvers HSL, Mumps and Pardiso, I am wondering if we could build something in common with JuliaSmoothOptimizers, to adopt a common interface for the linear solvers we are using. I have a look at HLS.jl, MUMPS.jl but these two packages implement only a bare-bone wrapper to the C code. I think medium term, it would be nice to share the same interface :
abstract type AbstractLinearSolver end

# dummy functions
introduce(::EmptyLinearSolver) = ""
factorize!(M::EmptyLinearSolver) = M
solve!(::EmptyLinearSolver,x) = x
is_inertia(::EmptyLinearSolver) = false
inertia(::EmptyLinearSolver) = (0,0,0)
improve!(::EmptyLinearSolver) = false
rescale!(::AbstractLinearSystemScaler) = nothing
solve_refine!(y,::AbstractIterator,x) = nothing

Thanks for working on this @frapac!
This looks like a perfect resolution for the dependency diet.
Regarding integration with HSL.jl and MUMPS.jl, I believe we will need extra wrappers on MadNLP side anyway. I think one way to clean things up a little more would be removing the bare-bone wrapper part for HSL and MUMPS from MadNLP.jl and make it depend on HSL.jl and MUMPS.jl.


Parameter descriptions seem mixed up, missing how to find categories.

Part 1:
The description for /user talks about categories and subcategories.
The description for /category talks about user (in the second sentence)
Part 2:
Please describe or link to a description where/how to find categories.
Regards
Bart

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

ID: 6277645c-a679-86bd-3678-ce0f22e0fbd7
Version Independent ID: 186581ae-c5d9-e98c-ffb8-d36c8fc56de3
Content: auditpol set
Content Source: WindowsServerDocs/administration/windows-commands/auditpol-set.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Search field obscures navbar dropdown

What went wrong?
When using the user dropdown in the search page, the search section is positioned over the dropdown.
This happens because the search section has a z-index of 1000.
What did you expect to happen?
The dropdown should always appear on top.
Screenshot

Where did you find the bug?

[X] https://ianalyzer.hum.uu.nl
[ ] https://peopleandparliament.hum.uu.nl
[ ] https://peace.sites.uu.nl
[ ] a server hosted elsewhere (i.e. not by the research software lab)
[X] a local server

Version
5.3.0
Steps to reproduce

Log in
Go to the search page for a corpus
Open the user dropdown (top right)

@lukavdplas Do you remember why you added the z-index for .search-section? It seems just removing this CSS property has no negative consequences and resolved this bug. But I might overlook something.

If I'm blamed on git, I think that's just because I refactored the old code.
I think this has to do with the sticky-top effect for the pagination controls? But it's quite possible this is just not needed. I-analyzer is old enough that we sometimes have CSS rules that just don't do anything anymore.


Punycode pipeline names

We aren't necessarily amazing at Go, so apologies if we've done something anti-idiomatic.
This runs punycode over all pipeline names as metrics are collected, which should solve https://github.com/buildkite/buildkite-metrics/issues/32

This looks great! Thank you so much!

Looks great! Thanks so much! I will get this into a new release of the elastic stack as quick as I can!


Problem with Pi3B+ and camv2.0

Hi,
Thanks for sharing this awesome tools. I am trying to use to to get high fps images with a Pi3B+ and a camv2.0. The build procedure went without errors, but when executing camera_i2c there is an error:
setting GPIO for board revsion: a020d3
Raspberry Pi3B / Pi3B+ / 3A
Set state of 133 to 1
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory

Checking the camera_i2c, there was a comment under my device's case a020d3 that took me to this raspi forum and to this older camera_i2c file.  After reading, it seems to me that Pi3B+ has some special i2c pins configuration not handled by current raspiraw's camera_i2c but done by the older camera_i2c file using rpi3-gpiovirtbuf.
However, I tried the older camera_i2c file that uses rpi3-gpiovirtbuf, without success. I go the same error:
setting GPIO for board revsion: a020d3
Raspberry Pi3
Set state of 133 to 1
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory

Could you please help me out? I am not really sure where to look now. Thanks!
BTW, both raspivid and raspistill are working fine.  Thanks!


Failed to execute the command: 'article_md --format html'

I am unable to open the article view inside the terminal.
The description tells me to configure the 'article_parse_command' option as described on the link:
https://github.com/aome510/hackernews-TUI/blob/main/config.md#article-parse-command
But that blob doesn't exist.
What am I doing wrong?

Hi, recently I moved the config doc to another folder. You can use this link instead https://github.com/aome510/hackernews-TUI/blob/main/doc/config.md#article-parse-command

That helped, thanks so much!


Emphasizing features of CrateDB Cloud

Hi there,
coming from https://github.com/crate/cratedb-guide/issues/131#issuecomment-2476128758, there was a suggestion to improve the All Features page, by also bringing in dedicated features of CrateDB Cloud.

Additionally, labeling this section “All Features” is potentially misleading, as it doesn’t include features specific to CrateDB as a managed service.

We will be happy to improve the situation on the “All Features” page as we go, by also indexing relevant features of CrateDB Cloud in a similar style, when applicable.
An alternative could be to improve the CrateDB Cloud documentation by also adding a dedicated "Features" page in the same style and spirit like the given one, and cross-link both, when applicable.
Let us know about your thoughts on this matter, and where we can support you. Thank you.
With kind regards,
Andreas.

An alternative could be to improve the CrateDB Cloud documentation by also adding a dedicated "Features" page in the same style and spirit like the given one.

https://github.com/crate/cloud-docs/pull/88


Add MSVC solution/projects, fix many warnings, and small enhancements.

Added Visual Studio solutions to msvc/ - Not relying on CMake and VS's less-than-perfect CMake integration. Fuzzer building on Windows for the first time.
Modified programs/programs_helper.h (define PRETTY_FUNCTION)
Modified programs/test_libmgmt.c (reduced iterations so the test does not hang for 10 minutes)
Modified usrsctplib/netinet/sctp_userspace.c (Added support for thread naming on Windows)
Modified usrsctplib/user_socket.c (usrsctp_getladdrs()/usrsctp_freeladdrs()/usrsctp_getpaddrs()/usrsctp_freepaddrs() - made sure the output pointer is set to null upon function entry and that the matching free() functions can handle null. Before that change, starting programs/client.c before the server resulted in a heap corruption: the call to usrsctp_getpaddrs() at line 226 returned < 0, leaving addrs untouched. But addrs had been freed at line 224, and was freed again at line 272, corrupting the heap.)
Added conditional __cdecl attributes to some functions (notably all main() functions) so the library can be built with different calling conventions. Ideally, all public/exported function should have their calling convention specified explicitely in the public header, via some new SCTP_PUBLIC macro that is defined per-compiler and build option, so people can build their app and the library with whatever calling convention they choose. On Windows, we have __fastcall as well as __vectorcall (that everyone should really use) and this change enables building the apps and the lib with those conventions without breaking the CRT or the fuzzer.
Fixed most /W4 warnings (many type casts) instead of globaly suppressing them.
Removed all calls to CreateThread() and TerminateThread()
Implemented proper thread creation on Windows when the thread routing is using CRT functions and in particular the heap.
Implemented proper (graceful) thread termination in sample programs.
Simplified loop in read_random() - now calls BCryptGenRandom() (or RtlGenRandom() pre-Vista)

"A thread in an executable that calls the C run-time library (CRT) should use the _beginthreadex and _endthreadex functions for thread management rather than CreateThread and ExitThread; this requires the use of the multithreaded version of the CRT."
https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createthread
"TerminateThread is a dangerous function that should only be used in the most extreme cases. You should call TerminateThread only if you know exactly what the target thread is doing, and you control all of the code that the target thread could possibly be running at the time of the termination. For example, TerminateThread can result in the following problems:
- If the target thread owns a critical section, the critical section will not be released.
- If the target thread is allocating memory from the heap, the heap lock will not be released.
- If the target thread is executing certain kernel32 calls when it is terminated, the kernel32 state for the thread's process could be inconsistent.
- If the target thread is manipulating the global state of a shared DLL, the state of the DLL could be destroyed, affecting other users of the DLL."
https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminatethread

Could you please split this pull request up in separate ones, each one addressing one issue or adding one feature.


shallowCopy: avoid a second read of the container's layer

Avoid reading the container's layer a second time in shallowCopy() (after the first time it's read, in NewImageSource()).
Our second copy of the diff isn't going to match the first one if it's of any serious size, because when NaiveDiff() is used to generate the diff, whiteout entries have their times set to "now", rather than a
fixed value, which causes both the uncompressed and compressed digests to differ from what NewImageSource() records in the manifest.
Instead, use the generic manifest-reading API that the image library now provides to read the layer info list and the config blob info, and use their values to PutBlob() them to the destination image.
In the medium-term, we can probably drop shallowCopy() completely, since the newer version of the image library has a more reliable HasBlob(), which should save us the time that shallowCopy() was originally meant to save, but we should probably consider the use of compression for this code path as part of that, too.
Fixes #502.

great, I've just tried and it solves the issue I've reported!

@rh-atomic-bot r+
Should we cut a new release?  Anything else we want to get in?


Add containment constraints

I'd like to poll appetite for adding something like:
import annotated_types as at

CountryCode = Annotated[str, at.In({"+1", "+54", "+39"})]

cc @Zac-HD

from typing import Literal

CountryCode = Literal["+1", "+54", "+39"]

But OK, suppose that we wanted to do this for things that can't be represented in a Literal, however common or rare that is.  Quick thoughts:

https://github.com/HypothesisWorks/hypothesis/issues/3795 does explicitly contemplate handling some simple cases in Hypothesis
we can't reasonably support mutable elements
we need some way to check whether the elements are instances of the annotated type, which we can only do in simple cases because a full runtime typechecker is well out of scope for Hypothesis.
we need to have a consistent ordering of the elements, which means either a sequence or a collection where the (allowed) elements are sortable.

Given all the constraints, I'm somewhat dubious that this would be worth the trouble.

Even if hypothesis can’t support this very well, there’s still value for other tools: Pydantic can convert the container into a Rust set and do the fast comparison in Rust. But I admit this only makes sense if it’s a common thing to do and if Literal doesn’t cover these use cases.

I'm inclined to close the issue until/unless someone comes up with two or three cases that Literal doesn't cover but Pydantic could if we added this feature.


feat(dispatcher): elegant and fast Webhook request processing component

❗This feature migrates to https://github.com/flc1125/go-gitlab-webhook

Introduction
An extremely elegant and fast component for receiving and processing Webhook requests has been implemented.
Features

Very convenient registration of listeners
A single listener can implement multiple different webhook functions
Support asynchronous and efficient processing
Multiple Dispatch methods

Example
source: examples/dispatcher.go
package main

import (
	"context"
	"net/http"

	"github.com/xanzy/go-gitlab"
)

var (
	_ gitlab.BuildListener         = (*testBuildListener)(nil)
	_ gitlab.CommitCommentListener = (*testCommitCommentListener)(nil)
	_ gitlab.BuildListener         = (*testBuildAndCommitCommentListener)(nil)
	_ gitlab.CommitCommentListener = (*testBuildAndCommitCommentListener)(nil)
)

type testBuildListener struct{}

func (l *testBuildListener) OnBuild(ctx context.Context, event *gitlab.BuildEvent) error {
	// do something
	return nil
}

type testCommitCommentListener struct{}

func (l *testCommitCommentListener) OnCommitComment(ctx context.Context, event *gitlab.CommitCommentEvent) error {
	// do something
	return nil
}

type testBuildAndCommitCommentListener struct {
}

func (l *testBuildAndCommitCommentListener) OnBuild(ctx context.Context, event *gitlab.BuildEvent) error {
	// do something
	return nil
}

func (l *testBuildAndCommitCommentListener) OnCommitComment(ctx context.Context, event *gitlab.CommitCommentEvent) error {
	// do something
	return nil
}

func loadDispatcher() {
	dispatcher := gitlab.NewDispatcher()

	dispatcher.RegisterListeners(
		&testBuildListener{},
		&testCommitCommentListener{},
		&testBuildAndCommitCommentListener{},
	)

	http.Handle("/webhook", http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		if err := dispatcher.DispatchRequest(r,
			gitlab.DispatchRequestWithContext(context.Background()),
		); err != nil {
			http.Error(w, err.Error(), http.StatusInternalServerError)
			return
		}

		w.WriteHeader(http.StatusNoContent)
	}))

	if err := http.ListenAndServe(":8080", nil); err != nil {
		panic(err)
	}
}

Thanks for the PR, but unfortunately this is not something I am willing to merge as this project only supports what is in the public API docs in order for me to be able to keep maintaining the project.
Maybe its an idea to create a dedicated package instead of trying to add it to this package? In any case I am going to close the PR, sorry!

This feature migrates to https://github.com/flc1125/go-gitlab-webhook

Very cool you took the effort to create a dedicated package for this 👍🏻👍🏻


fix buildx arm64 error

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind bug
What this PR does / why we need it:
fix buildx arm64 error
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/assign @Congrool @kadisi

/lgtm


Touch a worker.started file after worker initialization

Currently when workers are running under Systemd we use SD_NOTIFY to signal that a worker has started, Kubernetes also has a "startup probe" which waits for an indication that the worker is started before starting the readiness probe.
We can touch a startup file that a k8s startup probe can check when we mark the worker as "STARTED"

@jrafanie where are you eager loading the API constants?  Want to ensure it is before this

Going to close this as we don't currently have a requirement for it


Response being truncated when outputting event stream when IIS Express is reverse proxying

I made a repo with simple test case for this issue. Clone and run the below and hit /sse-test and things work great when serving from Kestrel directly, but causes some inconsistent truncation when running through Visual Studio and IIS Express.
https://github.com/svallis/SseTest/
Here's the only real bit of code added to the repo after a dotnet new mvc:
https://github.com/svallis/SseTest/blob/master/Controllers/HomeController.cs#L38-L55
The output on Kestrel looks right and ends up complete:
1 of 5
2 of 5
3 of 5
4 of 5
5 of 5

The output under IIS Express is truncated:
1 of 5
2 of 5
3 of 5
4 of 5
5

I'm guessing this is some kind of response caching or other interference at play. What would be the correct way to get around it? Weirdly enough, using static strings works fine on both, it's only when the data is dynamic that problems seem to occur. The larger and more complex the data gets, the less deterministic the output seems to become.

I found https://github.com/SignalR/SignalR/issues/273 which suggested a working fix for this, adding the following to web.config:
<location path="sse-test">
  <system.webServer>
    <urlCompression doDynamicCompression="false"/>
  </system.webServer>
</location>

The referenced issue also suggests that "There is no fix, it's a limitation of IIS classic mode and nothing can be done about it." Is that still the case, or is there a cleaner fix now we're in the .NET Core world? While the above solution works, it requires remembering to sync your web.config rules with your SSE endpoints. Worse, when it does fail it's hard to spot - the truncation just causes messages to be received late, and only the last one in the example above is never fully parsed (due to the client never seeing the terminating newlines).

@Tratcher any ideas on this? And maybe what repo this bug should go to?

You can't do StatusCode(200) after writing to the body, it throws. Check your app logs to confirm. Change the action return type to void. On kestrel the flush gets the data out first, but in IIS it gets buffered by the response compression and dropped by the exception.

Ah, indeed, it's dangerous to mix MVC's delayed action results along with writing directly to the response stream. You'll want to do one or the other; never both.
So, either set the status code explicitly in the action and then write directly to the stream, returning nothing from the MVC action, or do everything in an MVC action result (e.g. a custom action result that you would write).

Thanks @Tratcher - that was certainly an issue as well, but doesn't solve the core issue I had.
The response caching issue, although it manifests in a far less unpleasant way now and the final event is written out in full, still means events are delayed until the following event. This is what it looks like when running:

Events aren't processed until the newlines are received by the browser, which happens during the flush on the following event.

Yes, that's a limitation of IIS's response buffering as explained in the SignalR thread.


[🐛 BUG]: RPC: can't find method informer.Jobs

No duplicates 🥲.

[X] I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?
A bug happened!
Version (rr --version)
rr version 2023.3.2 (build time: 2023-10-19T16:30:40+0000, go1.21.3), OS: linux, arch: amd64
How to reproduce the issue?
Run workers RPC method line this /usr/local/bin/rr -w /server.latest -c /server.latest/rr.yaml workers
Relevant log output
Workers of [jobs]:
+---------+-----------+---------+---------+---------+--------------------+
|   PID   |  STATUS   |  EXECS  | MEMORY  |  CPU%   |      CREATED       |
+---------+-----------+---------+---------+---------+--------------------+
|   16292 | ready     |       6 | 140 MB  |   12.37 | 1 second ago       |
|   16293 | working   |       3 | 124 MB  |    9.27 | 1 second ago       |
|   16294 | ready     |       6 | 136 MB  |   13.05 | 1 second ago       |
|   16295 | working   |       3 | 127 MB  |    9.98 | 1 second ago       |
|   16296 | working   |       4 | 134 MB  |    8.58 | 1 second ago       |
|   16297 | working   |       3 | 135 MB  |   10.31 | 1 second ago       |
|   16298 | working   |       7 | 140 MB  |   12.03 | 1 second ago       |
|   16299 | ready     |       7 | 143 MB  |   13.08 | 1 second ago       |
|   16300 | working   |       9 | 139 MB  |   13.39 | 1 second ago       |
|   16301 | working   |       3 | 135 MB  |    9.95 | 1 second ago       |
|   16302 | ready     |       5 | 141 MB  |   11.34 | 1 second ago       |
|   16303 | ready     |       8 | 138 MB  |   12.38 | 1 second ago       |
|   16304 | ready     |       8 | 143 MB  |   14.45 | 1 second ago       |
|   16305 | working   |       3 | 137 MB  |   10.66 | 1 second ago       |
|   16306 | working   |      11 | 140 MB  |   13.39 | 1 second ago       |
|   16307 | working   |       6 | 147 MB  |   14.08 | 1 second ago       |
|   16308 | working   |       3 | 134 MB  |    9.27 | 1 second ago       |
|   16309 | working   |       3 | 136 MB  |   10.32 | 1 second ago       |
|   16310 | working   |       9 | 142 MB  |   14.43 | 1 second ago       |
|   16311 | working   |       3 | 135 MB  |    8.59 | 1 second ago       |
|   16363 | working   |       3 | 135 MB  |   13.64 | 1 second ago       |
|   16364 | ready     |       9 | 140 MB  |   19.33 | 1 second ago       |
|   16365 | working   |       4 | 135 MB  |   14.10 | 1 second ago       |
|   16366 | working   |       1 | 134 MB  |   12.59 | 1 second ago       |
|   16367 | working   |       3 | 142 MB  |   17.76 | 1 second ago       |
|   16368 | working   |       3 | 124 MB  |   13.62 | 1 second ago       |
|   16793 | working   |       3 | 125 MB  |   12.53 | 1 second ago       |
|   16794 | ready     |       9 | 143 MB  |   19.91 | 1 second ago       |
|   16795 | working   |       3 | 135 MB  |   13.08 | 1 second ago       |
|   16796 | ready     |       8 | 137 MB  |   19.40 | 1 second ago       |
|   16797 | working   |       3 | 133 MB  |   12.04 | 1 second ago       |
|   16798 | working   |       3 | 134 MB  |   12.04 | 1 second ago       |
+---------+-----------+---------+---------+---------+--------------------+
show_workers: rpc: can't find method informer.Jobs

Hey @Kaspiman 👋🏻
Already fixed ⚡


redesign profile page

This is a meta-ticket for redesigning the profile page.
Originally ... copied from #43:

Think Facebook timeline. A big part of Gittip for me is "the feeling of participation in someone else's story." I want Gittip to help tippees to tell their story. What are they doing to make the world better? Why? How is their vision unfolding? Let's link out to Twitter, blogs, etc. for the narrative, and let's use Gittip to tell the story in numbers. Here's what they're tipped and how much they tip. Here's when they've bombed or been bombed (#131). Here's how their funding goal has evolved (#110). And then the narrative bits add flesh to the bones. Here's what I did with the money. Here's how I made the world better. Here's how I realized my vision.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/316985-redesign-profile-page?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Can this be closed?


included instancing geometry feature and fixed NaN error

Transform, rotation and scale are implemented for Geometry Instancing. It could certainly be better, but for the moment it does the core tasks.
Another thing I added is a check on NaN errors when adding points. This would crash the script when adding SOP data which for instance has been passed through the copy SOP.

@mickeyvanolst be patient with me as I give this a look before integrating. I'm a little slammed with jobs at the moment, so it might take me a minute before this is integrated.


Auto(-save &) continue mode

Time to track this one :smile_cat:
So because:

travis have a limitation of 50 minutes
@mitchellkrogza have a huge Ultimate Hosts/Blacklist he want to test
..... Keep completing this list until this issue is fixed (Let's have some fun :wink: :joy_cat: )

It'll be great to add an auto (save &) continue  mode!

break up list in few pieces and run multiple terminals?

No @xxcriticxx 😜 I already started you gonna see it in the dev branch in few hour I'm gonna sleep 🙂


Support for F16 types in convolution

Does MIOpen support convolution with following combination?
Src = f16, NHWC
Weights = f16, NCHW
Dst = f16, NHWC
Bias = f16, NCHW

Thanks for the confirmation, @atamazov.
Is it the case for other datatypes as well?

I think so.
# ./bin/MIOpenDriver conv -g 1 -n 256 -c 192 -H 28 -W 28 -k 192 -x 3 -y 3 --in_layout NHWC --out_layout NHWC --fil_layout NCHW -F 1 -V 0 -i 1
MIOpenDriver conv -g 1 -n 256 -c 192 -H 28 -W 28 -k 192 -x 3 -y 3 --in_layout NHWC --out_layout NHWC --fil_layout NCHW -F 1 -V 0 -i 1
MIOpen(HIP): Info [get_device_name] Raw device name: gfx906:sramecc+:xnack-
MIOpen(HIP): Info [Handle] stream: 0x19addd0, device_id: 0
MIOpen(HIP): Info [GetFindModeValueImpl] MIOPEN_FIND_MODE = DYNAMIC_HYBRID(5)
MIOpen(HIP): Info [ForwardGetWorkSpaceSize]
MIOpen(HIP): Info [AmdRocmMetadataVersionDetect] ROCm MD version AMDHSA_COv3, HIP version 5.4.22454, MIOpen version <IP_ADDRESS>cb380cb
MIOpen(HIP): Info [GetForwardSolutions]
MIOpen(HIP): Info [Measure] ReadonlyRamDb::Prefetch time: 49.6881 ms
MIOpen(HIP): Info [Measure] RamDb::Prefetch time: 0.036528 ms
MIOpen(HIP): Info [FindConvFwdAlgorithm] requestAlgoCount = 2, workspace = 0
MIOpen(HIP): Info [GetForwardSolutions]
MIOpen(HIP): Info [TryLoad] Find-db regenerating.
MIOpen(HIP): Info [GetPerfDbPathFile] Found exact perf database file
MIOpen Error: /root/github/MLOpen1/src/ocl/convolutionocl.cpp:528: Forward Convolution cannot be executed due to incorrect params
RunForwardGPU() FAILED, rc = 0x7

Let's update the docs.
[Attribution] @junliume @johnny-keker https://github.com/ROCmSoftwarePlatform/MIOpen/labels/documentation https://github.com/ROCmSoftwarePlatform/MIOpen/labels/enhancement https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_normal No ideas about assignee.

@junliume @atamazov Internal ticket is created to update documentation. Thanks!

@ppanchad-amd Let's close this one.

@atamazov Should we close it once docs are updated? Thanks!

@ppanchad-amd Yes


AWS public-cloud terraform apply error output.ami_id: missing dependency: var.all_amis

when I run terraform apply I get the following error
Error configuring: 1 error(s) occurred:
* output.ami_id: missing dependency: var.all_amis

It works with a new download, I guess I had a bad configuration of the aws amis


Support Oracle Wallet

i raised this issue originally on lostash forum https://discuss.elastic.co/t/logstash-reading-data-from-oracle-database-using-oracle-wallet/51181. I provided most of the details on thread.
Currently Logstash not working with Oracle wallet. The jdbc.rb and driver class  need to be enhanced to support Oracle Wallet .I debugged code little bit. I printed the props and args to console. The code is passing the userid , password which is not required in case of wallet. I think "driver" class might be parsing the connection string and passing the host name and port number.
driver.new.connect(args[0], props)
FYR, see below the java code which tested against the Wallet. Please note, there are no properties passed while creating connection.
String url = "jdbc:oracle:thin:/@ALIAS_DB";
Class.forName("oracle.jdbc.OracleDriver");
Connection conn = DriverManager.getConnection(url);
Follow this thread for more explanation and steps to create wallet, configure tnsora.names etc
http://stackoverflow.com/questions/7634196/what-is-correct-jdbc-url-syntax-if-oracle-wallets-are-used

This would be a huge help for those of us that cannot have hard coded credentials in the connection strings and utilize certificates with the wallet authentication. Although we were able to customize the source code to do it, it would be very nice to have this in the mainstream product.

This issue was resolved ? I'm with same problem
Input:
jdbc {
jdbc_driver_class => "Java::oracle.jdbc.driver.OracleDriver"
jdbc_driver_library => "/usr/lib/oracle/19.6/client64/lib/ojdbc8.jar"
jdbc_connection_string => "jdbc:oracle:thin:@dbname?TNS_ADMIN=/home/ubuntu/oracle_driver/wallet/"
jdbc_user => "user"
jdbc_password => "password"
statement => "SELECT count(0) FROM table "
}
Get this error:
[ERROR] 2020-06-30 09:20:01.304 [Ruby-0-Thread-15: :1] jdbc - Unable to connect to database. Tried 1 times {:error_message=>"Java::JavaSql::SQLRecoverableException: IO Error: The Network Adapter could not establish the connection"}


replace 'silence' with 'verbose' option

I've found that the logs are pretty hard to work with when requests come with very long messages (in my case, on the order of 7k tokens). this PR expands the log verbosity options into 3 levels:

verbose=0: suppress tqdm bars and 100% of log output (what the docstring says silent=True should do, although currently it doesn't suppress logs at all)
verbose=1: display tqdm bars and log requests with metadata only
verbose=2: display tqdm bars and log requests with metadata and all request params (including messages). this is roughly equivalent to current behavior of silence=False

I believe verbose=1 is a more sensible default, but kept default verbose=2 to align with the current behavior

@jvmncs shit, you gotta rebase bc of the other PR.

ah I just merged through github UI. can redo with a proper rebase if you prefer

no that's OK. i might update the name of that param to loglevel: "silent" | "warn" | "verbose" or something similar.

damn, tests are failing - i forgot to add tests as required workflow for PRs or we'd have seen it here pre-merge.

Confirmed failing tests had nothing to do with your code so this will ship after I bump version.


[NTR] Increase currentVersion property to 1.1.10

Coverage remained the same at 41.591% when pulling 2d9138ee54c50522eede19b45485928b9ec925c6 on NTR-increase-current-version-plugin-json into efdd90a08592fe248bbf442e7291c1327a03a3ba on master.


feat: added traffic.tag

Added traffic.tag flag to the Cloud Run Resource to the issue #71.
The tag variable was added to the latest versions of the provider v4.22.0 and the PR #5772.

@mitchelljamie Good to be merged.


feat: rewrite the scanner in C

Hey, thanks for the pull request. I wonder why it is needed though, is something wrong with the C++ scanner other than it being a bit ugly?

It's not that it's ugly (well, subjectively, C++ is ugly to me :laughing:), but that a pure C scanner has better support for pure C projects and is easier to work with with regards to compilation/bundling. I can add a fuzz action here too that will fuzz the code for any bugs like buffer overflows, leaks, segfaults, etc

Hey,
One problem i'm seeing is that I think this is a breaking change, downstream projects like nvim-treesitter use the name of the external scanner to compile the parser ( see here https://github.com/nvim-treesitter/nvim-treesitter/blob/ae0415331483bd143f80c186401fb2aa783f33df/lua/nvim-treesitter/parsers.lua#L639 ); due to that i dont feel really great about merging this PR yet.

Well I am a member of nvim-treesitter and I would adapt the changes right away :smile:

Problem is; the parser is also used in semgrep and other projects; i really dont want to break them.

I'm sorry but I don't understand that logic - python, html, bash, c++, and others all were rewritten in C with no complaints from upstream maintainers and are all probably used by more projects than this

I'm sorry but I don't understand that logic - python, html, bash, c++, and others all were rewritten in C with no complaints from upstream maintainers and are all probably used by more projects than this

Semgrep for example has not yet updated to the C one ~ https://github.com/tree-sitter/tree-sitter-cpp/blob/a35a275df92e7583df38f2de2562361f2b69987e/src/scanner.cc ( if its the correct grammar )

I'm afraid that's Semgrep's issue then, as they won't update any fixes/features I or you have made (like one nasty infinite loop bug in Python), and thus shouldn't have any bearing here

I wonder, is there a way we can have both scanners? ( the code is pretty much set i would say ); that way i can take a couple weeks to update all downstream projects i know of ( because i got complains about breaking compiling )

generally they should be able to just exist in parallel, right?

I mean..you could but I don't know how cli picks the scanner to compile
rust/binding.gyp just need the file renamed to ideally prefer the C version.

lets maybe just do this: not release it for a bit and create PRs to bump + fix compiling issues in projects that i know about; does that sound acceptable?

That's totally fine! Thanks for coming to a compromise :slightly_smiling_face:

Ill break out the old fuzzer today in the evening; if that reveals no issues i feel comfortable merging!

Just marked a few more functions static that weren't


Problem with scroll

Hey, everybody,
do you know for what reason the slider at the bottom of the site (heading Handbags) is not scrolling? Since I'm generating it dynamically I've had this problem. The strange thing is that if I do the following action = click on the Products item in the menu, open the first handbag (Luna), then click on the Mybelka logo (gets me back to the homepage) then suddenly my slider works normally.
Thank you for any advice.
Regards
Robert
https://mybelkasro.savana-hosting.cz/

Tiny-slider version:   2.9.3
Browser name && version:  Chrome 105.0.5195.127
OS name && version:   Windows 11

Please, can someone help me?
New link: https://k42n6u6whm-staging.onrocket.site/


Please add hyphen to Koolen de Vries syndrome term

Mondo term (ID and Label):
Koolen de Vries syndrome MONDO:0012496
Suggested new label:
Koolen-de Vries syndrome
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
ClinGen ID/Autism GCEP
Optional: Any additional information (like supporting evidence, PubMed ID, etc.)
As with most eponymous disease terms, there should be a hyphen between the authors two last names: (1) Koolen and (2) de Vries

While names are being considered for this term, I see these are listed as exact synonyms:

microdeletion 17q21.31 syndrome
chromosome 17q21.31 deletion syndrome

But is Koolen-de Vries somehow different from MONDO:0018216
17q21.31 microdeletion syndrome ?
Orphanet 363958 maps to OMIM: 610443
So should these be merged as a part of the term clean up?

@sabrinatoro can you take a look at this one.
I agree with @kanems, I think these two are equiv and should be merged:
MONDO_0018216 '17q21.31 microdeletion syndrome'
MONDO_0012496 'Koolen de Vries syndrome'
this would cause a proxy merge with Orphanet. Looks like OMIM has combined these into one term (see OMIM here).
Thanks for your help!

In the mean time, I relabeled the term per the request above @tibingaman. Thanks for reporting this.

@nicolevasilevsky @kanems
I do not think that MONDO_0018216 '17q21.31 microdeletion syndrome' and MONDO_0012496 'Koolen de Vries syndrome' should be merged.
Looking at the ontology, there is also "Koolen-de Vries syndrome due to a point mutation" (MONDO:0018217).
According to here and  here/)
"(Koolen-de Vries syndrome) is caused by mutations in the KANSL1 gene, or by the loss of a small amount of genetic material in chromosome 17 that includes the KANSL1 gene (chromosome 17 q21.31 microdeletion)."
Based on this information, I propose:

"Koolen-de Vries syndrome" as a parent term
2 children: "Koolen-de Vries syndrome due to 17q21.31 microdeletion", and "Koolen-de Vries syndrome due to a point mutation"

To do:

[ ] rename MONDO_0018216 '17q21.31 microdeletion syndrome' to  Koolen-de Vries syndrome due to 17q21.31 microdeletion.
[ ] move the following xref from "Koolen-de Vries syndrome" to "Koolen-de Vries syndrome due to 17q21.31 microdeletion":
UMLS: C1864871, SCTID:717338006, MESH:C566476, DOID:0070076/DOID:0050880

xref that would stay on the parent term:
GARD:0010727, Orphanet:96169, OMIM:610443 (from omim:A number sign (#) is used with this entry because Koolen-De Vries syndrome can be caused either by heterozygous mutation in the KANSL1 gene (612452) on chromosome 17q21.31 or by a larger deletion of several genes on chromosome 17q21.31.)
xref that I couldn't find (probably obsoleted at the source):
UMLS:CN776874

sounds good @sabrinatoro, thanks!


feat: Added support for @import

added support for @import

Thanks for you contribution @yj1438, but sorry, I'm not going to support @import keywords. You may find a deeper explanation of this design decision at this link. Thanks again.


Remove gradle subprojects from "project_roots" list

Gradle submodules are no longer reported as project_roots if there are no other package manager files located in the submodule root folder.

Please don't forget to squash the commits (or rename them) because  I see a wip commit in there.

This PR has been replaced with the following PR #629


a1ad/mikrotik-logs : failed auth not parsed on ROS 7.9

@a1ad
Seems that the new format to display failed auth is now as follow: denied winbox/dude connect from XXX.XXX.XXX.XXX

Ok, after more tests, both the orignal synthax and the one in first post are used at the same time... The "denied winbox/dude" is when a connection attempt is made from an incompatible client. That could be an interesting addition.

@VA2XJM Is that a full log line?

@a1ad Affirmative!

So that is the full log line? cause from image we can see a date and warning?

No, that is not a syslog line. You need to connect the Tik to a remote syslog server.

I will check next time I am on location (no remote access), I'm relaying the info only, but the owner says this is the complete line in the log file (rsyslogd dump to a fil so Crowdsec can read it).
I'll get back to you sometime next week.


[DESIGN] Move 'Collections' to the top level of the entry type tabs

Jesi will post mockups here

need to also discuss adding a collections field for methods and orgs.

In this version of the idea, we'd add a drop down for collections beside the entry type tabs (always visible on 'all,' as well as each of the tab types when selected). This drop down navigates users to a new page which is the "collections page" for that collection (essentially a search filter, but results with custom page display). That page would give more metadata about the collection (title, description, link to external site) possibly in place of the map, and also display the entries for the collection. probably need to be able to use the search filters for large collections. might display differently from the typical homepage results? featured entries for the collection? design tbd.

precedent of landing page/functionality embedded into another site. white labelled. https://www.decidim.barcelona/

different aesthetic:

Another way to deal with collections is to treat it the same way as the cases, methods and orgs tabs, and then display each collection as a card, with the title and metadata about how many entries are included in the collection (clicking the card would then lead to the landing page), also if you used List View, you could read the descriptions for the collections all in one place. Here we can have a featured collection, as well as bookmark a collection.

Example GOC landing page

title
description (280 char max)
1 link
1 banner image
do not show search filters for collections with less than 20 results, but do show tabs to allow filtering by entry type
(TBC the collections tab disappears on landing pages @ascott - thoughts?)
(TBC scrolling to left or right in the banner image could load the next collection)

(TBC the collections tab disappears on landing pages @ascott - thoughts?)

yes, agreed

(TBC scrolling to left or right in the banner image could load the next collection)

i think we should remove the arrows in the banner image, and just rely on collections tab on the home page to access collections

Another mockup for landing pages (more like a profile page) for consideration.

And another, just food for thought - trying to connect the entry type sorting tabs to the collection information. could be that we don't even want to filter collections by type at all.

ie: without any tabs or filters:

And here's one that looks like a case, with results below the short description (would also allow for multiple images, and links)

After chatting with Amber, adding a vertical separator between the organizations and collections tab, to visually differentiate them subtly. We agree adding collections to the tabs with cards for collections that then lead to the landing pages is a nice solution.
Also showing possible updates to the homepage map overlay for review with Amber today. the idea is there would be some automatic transition/animation/slider/fade or something between the very explicit tagline, and the mission statement - the new [+ entry type] buttons would all remain in place.

also, updated the GOC collection overlay example

Here's a Google Doc to plan the text for the map overlay slideshow/marquee. @plscully

@ascott per our call today - updated spec for landing pages to include text link to "View All Collections" which would take the user to the homepage collections tab. this is obvious im sure but just want to also flag that the link button should have 2 fields in the entry form - one for the url, and one for the custom button text. i'll start finding better banner images for the collections we have so far too. thanks!


Adds seasonal totals for the NCR of the hydrology data

This PR adds the seasonal totals for the hydrology data to display in the hydrology section of the NCR.
You get these additional seasonal totals when requesting /eds/hydrology currently, which in a future version of the API we could change if desired.
In the returned JSON, for each variable and scenario, you should see a seasonal total for Spring, Summer, Fall, and Winter.

Hey I looked at the most recent commits and this is good! I tried a few routes and can confirm that the only variables present are evap and runoff. This matches what we expect in the clients at the moment. The preview piece of the JSON looks good still (all vars). Craig thanks for checking the seasonal math! Merging.


Hostname mismatch

Hostname from the browser should match the curl output.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks, @arjun-urs , I agree. I'm working on updating The Get Started Guide. Actually, I'm removing that part altogether because it's redundant (from part 1). More on this soon: https://github.com/docker/docker.github.io/pull/5828/files


[Cisco CustomLink] - Added SplunkLog Controller

Summary
Project Jira : Ref
Project Doc : NA
Feature : Added new controller to get splunk logs for Cisco
How changes are verified
Tested locally with sample app & gate service, redirection is happening.
Highlights

baseURL, podURL, clusterName should come from .hal/default/profiles/gate-local.yml
podName will be supplied by gateURL (present in .hal/default/profiles/orca-local.yml)

Documentation Updates
Do we need to update dashboards? No
Do we need to update SOP, new hire wiki or other documents? No
Rollback, Deployment Details
Can this change be rolled back automatically without any issue?  Yes
Is this a backwards-compatible change in your opinion ?  Yes
Pre deployment steps : NA
Post deployment steps :

Aman will test this feature with latest gate quay img on k8s setup, redirection should work fine.
If step1 is passed, QA will test this feature with different authN mechanism to be 100% sure

Looks good. Just add a comment in the code to show how a sample base url looks like.

done


fix: consolidate the API of AsyncParser and parseAsync

Closes #468

Coverage remained the same at 100.0% when pulling 3a67571964f994c3fecb0cd8ec301ccbc77b4cd3 on juanjoDiaz:consolidate_async_parsers into 471f5a7a55375a06a66ce4b0438583d719d6db8f on zemirco:master.

Coverage remained the same at 100.0% when pulling 3a67571964f994c3fecb0cd8ec301ccbc77b4cd3 on juanjoDiaz:consolidate_async_parsers into 471f5a7a55375a06a66ce4b0438583d719d6db8f on zemirco:master.

I'm also considering if it make sense the current API:

fromInput allows you to set the input which can be a stream, an array or a single object.
throughTransform allows you to add transforms to the input stream.
toOutput allows you to set the output stream.
promise returns a promise that resolves when the stream ends or errors. Takes a boolean parameter to indicate if the resulting CSV should be kept in-memory and be resolved by the promise.

or if they should be replaced by something simpler and more aligned with the sync API like

parse(input) which takes an input (stream, array or object) and returns the CSV.

The methods throughTransform and toOutput are just wrappers around pipe and don't really provide anything.
The method promise is very similar to the finished method that has been added to the stream/promise API in node.
The only difference is that it can gather the whole JSON in a string and resolve that.
I can see 2 options here:
I could move the promise method to either the JSON2CSVTransform so you can do
const csv = await asyncParse.parse(data).promise();

I could add a utils module with a StreamToString class that gathers the string and exposes a promise method that resolves when the stream ends, so the user can do
const streamToString =  new StreamToString();
asyncParse.parse(data).pipe(streamToString);
const csv = await asyncParse.parse(data).pipe(streamToString).promise()

I like the second one better.
This PR already includes the ArrayAsStream method wich is basically ArrayToStream.
So having StreamToString seems pretty consistent.
Thoughts?

I like option 2 as well

This should be good to merge.

All feedback has been fixed I think.


Crash if image is too small

Description
In reference to this comment, sct_deepseg_gm crashes if the image is too small in the XY plane.
Example of error below:
sct_deepseg_gm -i t2s.nii.gz

--
Spinal Cord Toolbox (master/92f4635e6b35cceeaa558688820c8c778c39d874)
Running /Users/julien/code/sct/scripts/sct_deepseg_gm.py -i t2s.nii.gz
  pixdim: (0.5, 0.5, 7.499999)
  shape: (49, 54, 9)

Calculate new dimensions...
  new shape: (98, 108, 9)
  affine matrix:
[[ -4.99996871e-01  -8.49516226e-08   2.65367720e-02   9.42460155e+00]
 [ -3.10067044e-05   4.99923617e-01  -1.31088883e-01  -1.32206888e+01]
 [  1.76884665e-03   8.73931497e-03   7.49880648e+00   2.58022213e+00]
 [  0.00000000e+00   0.00000000e+00   0.00000000e+00   1.00000000e+00]]

Calculate affine transformation...
  transfo:
[[ 0.5   0.    0.   -0.25]
 [ 0.    0.5   0.   -0.25]
 [ 0.    0.    1.    0.  ]
 [ 0.    0.    0.    1.  ]]
Traceback (most recent call last):
  File "/Users/julien/code/sct/scripts/sct_deepseg_gm.py", line 82, in <module>
    run_main()
  File "/Users/julien/code/sct/scripts/sct_deepseg_gm.py", line 72, in run_main
    model_name, int(verbose))
  File "/Users/julien/code/sct/python/lib/python2.7/site-packages/spinalcordtoolbox/deepseg_gm/deepseg_gm.py", line 226, in segment_file
    nii_resampled.shape[1]))
RuntimeError: Image too small (98, 108)

Possible solution
pad the image if it is too small.
Steps to Reproduce

go to sct_testing_data/t2s
run: sct_deepseg_gm -i t2s.nii.gz
observe crash

State of spinalcordtoolbox
commit: 92f4635e6b35cceeaa558688820c8c778c39d874

This issue is the same as this issue #34 (axondeepseg). The network was trained using a context. A solution for that can be padding, however, the network was trained with this context and this will silently pad the image and input zeros to the network instead of the entire context. In the entire dataset I used (our internal one and the challenge), I didn't saw images of this size after resampling to 0.25x0.25mm, so I would say that when an image has this size, it is usually because it was cropped and is not the original image (was this image that you tested cropped ?).
So there are two paths we can follow from here:

Implement the padding;
Improve the error message (like done in AxonDeepSeg) to tell the user to use the original image or pad by himself, so the padding will be explicitly done by the user;

In summary, if this image size is from a cropped image and this is uncommon, it would make sense to tell the user to use an uncropped image because the network actually uses the context for prediction. However, if this size is common, I will have to implement a way to pad it after resampling, feed into the network and reconstruct it to the original size again and then resample back.
@jcohenadad What do you think ?

ok, i think that going with option 2 is reasonable. I was indeed using a cropped image. It would also be important to mention in the usage/documentation what is the minimum image size required.

@perone didn't you fix it in a merged PR?

Yes this can be closed already.


Replace the WDL language grammar

This PR updates support for the WDL to the latest version (v1.2).
Description
We've written the grammar from scratch to be compliant with the latest version of WDL—currently, the grammar used in linguist is around 6 years old (and represents a very old version of WDL).
A list of some (but not all) improvements being:

Added all keywords (e.g., requirements).
Shell highlighting within command blocks.
Better semantic classification of different keywords.

Checklist:

[x] I am changing the source of a syntax highlighting grammar

Old: https://github.com/broadinstitute/wdl-sublime-syntax-highlighter
New: https://github.com/stjude-rust-labs/sprocket-vscode

(From the I am adding a new language of the template. section, as I'm adding a new example)

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

fq.wdl

Sample license(s): MIT

Okay, I've reverted those samples and added a new one! Let me know what you think, @lildude.

This PR updates support for the WDL to the latest version (v1.2).
Description
We've written the grammar from scratch to be compliant with the latest version of WDL—currently, the grammar used in linguist is around 6 years old (and represents a very old version of WDL).
A list of some (but not all) improvements being:

Added all keywords (e.g., requirements).

Shell highlighting within command blocks.

Better semantic classification of different keywords.

Checklist:

[x] I am changing the source of a syntax highlighting grammar

Old: https://github.com/broadinstitute/wdl-sublime-syntax-highlighter

New: https://github.com/stjude-rust-labs/sprocket-vscode

أُرسلت من الـ iPhoneفي ٣٠/٠٧/٢٠٢٤ الساعة ٨:٥٢ م، كتب/كتبت Clay McLeod @.***>:
Okay, I've reverted those samples and added a new one! Let me know what you think, @lildude.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Please also replace your sample with a real world example and update the template to state where it comes from and the license of the sample.

This should be addressed: I added a new, real-world example and also added the license to the template for the PR and the header of that sample.

The test failure suggests you might not have used the documented method of replacing the grammar as the script sorts the submodules.
Please use the script as documented. You can replace the grammar with itself using the script.

Okay, I think I've resolved this now—I had used the script, but had done some spelunking on the codebase beforehand to try to understand how it worked (in unstaged changes).
I checked out a fresh version of the repo, applied my changes, and then got bundle exec rake running with no errors.


Ensure molecule names are unique at GROMACS export time

Description
Resolves #974
Checklist

[x] Add tests

[x] Test that molecule name clashes are resolved at GROMACS export time

[x] Lint
[x] Update docstrings

[x] Document that GROMACS molecule names might be modified if non-unique before export

@pbuslaev could you have a look at this? I think the test covers what you found but there might be other tests worth adding.

Sure, I will do it first thing tomorrow.

Hi @mattwthompson, I went through the code. Everything looks fine to me. I suggested adding one test, but locally for me everything worked fine. I will continue testing with more complex systems

Thanks much - I'm going to push off adding that test since I don't think I can quickly fix #978 here, but it's a great case to add