TypeError: expected string or bytes-like object

Pick a name for the new index
index_name = 'wikipedia-articles'
Check whether the index with the same name already exists - if so, delete it
if index_name in pinecone.list_indexes():
pinecone.delete_index(index_name)
Creates new index
pinecone.create_index(name=index_name, dimension=len(article_df['content_vector'][0]))
index = pinecone.Index(index_name=index_name)
Confirm our index was created
pinecone.list_indexes()

Using_vector_databases_for_embeddings_search

The error message you mentioned, "TypeError: expected string or bytes-like object," typically occurs when a function or method expects a string or bytes-like object as input, but receives a different type of data instead. To resolve this issue, you should ensure that the input provided to the function is a string or can be converted to a string.
Based on the code snippet you provided, it appears that you are using the Pinecone API to create and manage indexes. The error you encountered might be related to how the index_name variable is defined or used in the code. Here's an example of how you can fix the issue:
``
Pick a name for the new index
index_name = 'wikipedia-articles'
Check whether the index with the same name already exists - if so, delete it
if index_name in pinecone.list_indexes():
pinecone.delete_index(index_name)
Creates new index
pinecone.create_index(name=index_name, dimension=len(article_df['content_vector'][0]))
index = pinecone.Index(index_name=index_name)
Confirm our index was created
print(pinecone.list_indexes())
``
Make sure that the pinecone.list_indexes() function returns a list of strings representing the existing indexes. If the error persists, please provide additional information or context about the pinecone library you are using and the specific error traceback.


Removed unnecessary parentheses and change double quote to single quote in model check messages.

I am -0 on this.  I do not see real value in this cleanup.

-0

If you found a few other cleanups it might be fine. Looking at the file, one thing that could be fine is merging lines like:
index_together = [
    ["m2m"],
]

to: index_together = [['m2m']].
That was another pattern that I changed when reviewing your other PR.

Thanks for suggestions, I have make a little more cleanups. Feel free to close this PR if you think there are no value.


browserSupportsWebauthn is not a function?

First, let me say thanks for this great project, very cool use case.
After deploying with CDK, the cloudfront distribution returns index.html, when rendered in the browser (chrome, latest) I get:
Uncaught TypeError: browserSupportsWebauthn is not a function
    at (index):84:12
(anonymous) @ (index):84

Checking in SimpleWebAuthn, it looks like it's still implemented in the latest release https://github.com/MasterKale/SimpleWebAuthn/search?q=browserSupportsWebauthn.
Any ideas as to the issue?

I removed the if statement referencing it, and it seemed to work.


always call the callback and return

Fix for #12

@pibi, I tested the new code and I am still getting the issue mccormicka/Mockgoose#204.
Do we not need to use something like this?
if(typeof(callback) == "function"){
            callback(child.status);
}

at the end?

I also required the conditional described by @Amri91. I'm on Windows 10.
My build of MERN is broken without this. When will it get merged?

there was a rewrite of this library, so I am closing this pull request.


move button row inside alert row

This branch reduces the amount of padding between the button and alert body on the 404 page

Seems right to me.
How about add a margin top of 30~35vh to the content container for this page ?

...

.page-not-found {
    margin-top: 30vh;
}


Laboratory Work #1, Anna Sizykh - 20FPL3

there is no progress to this moment. please start the implementation process - there is plenty of actions to do!

no progress with a pipeline, hurry up!


Update README.md

Docker image 11.1-base no longer exists, update to 11.1.1-base

Thanks for pointing this out. Unfortunately we are unable to accept any pull requests as per CONTRIBUTING.md. I'll update README.md and run.sh internally and push it out.


ResourceExhaustedError

Is there anybody met this? Is my GPU memory short for this model?
Traceback (most recent call last):
File "/home/anaconda/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1334, in _do_call
return fn(*args)
File "/home/anaconda/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1319, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "/home/anaconda/anaconda3/envs/tf/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1407, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.ResourceExhaustedError: Ran out of GPU memory when allocating<PHONE_NUMBER> bytes for
[[{{node softmax_cross_entropy_with_logits}} = SoftmaxCrossEntropyWithLogits[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:GPU:0"](softmax_cross_entropy_with_logits/Reshape, softmax_cross_entropy_with_logits/Reshape_1)]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.130                Driver Version: 384.130                   |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============+================+==================|
|   0  Tesla K40c          Off  | 00000000:04:00.0 Off |                    0 |
| 23%   30C    P0    61W / 235W |      0MiB / 11439MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla K40c          Off  | 00000000:82:00.0 Off |                    0 |
| 23%   31C    P0    67W / 235W |      0MiB / 11439MiB |     99%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|===================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

I got it, my batch_size is too large


Making trident take parameters/annotations from PVC, for creating a corresponding PV that points to a specific endpoint

A single and same NFS share can be declared in multiple PVs and a corresponding PVC can use that. But if we want it in trident way, then trident creates a random PV with non-deterministic endpoint. So, I think it will be a nice to have feature to pass the NFS server and path as annotation or something so that trident creates the PV accordingly. Is anyone working on any similar thing?
PS. This can be for any storage that supports RWX access mode.

Trident's main function is to provision new storage, which entails creating a volume on the storage backend and creating the corresponding PV. What you're asking can easily be accomplished by reusing PVCs. For example, you have a PVC called pvc-bronze that gets bound to a PV that is either statically or dynamically provisioned. Once this PVC is bound, you can have multiple pods referring to the same PVC and consequently accessing the same volume. There is no need for Trident or the admin to create a new PV that points to the original volume.

I agree but my use case is different. I want to acess same pv endpoint from multiple namespace/projects. The I can not re use the pvc in multiple pods in multiple namespaced/projects. Because, pvcs are namespaced/project based. Then thi requirement arises.

Your use case does change things, but I should note that PV details are not necessarily exposed to users. For example, in OpenShift, regular users don't have enough privilege to get the details of a PV, so they can't supply that information using a PVC to Trident.
I admit that this type of cross-namespace workflow hasn't been not considered well in Kubernetes. I've had discussions with members of the community around this issue, particularly as it relates to snapshots, but as I said, there is no good solutions for it now. We can change Trident to create multiple PVs, all pointing to the same volume on the storage backend, and have Trident create the corresponding PVCs in different namespaces, but this type of capability, if not implemented carefully, can potentially cause security concerns, especially for preexisting PVs that shouldn't be accessed across namespaces. One way to alleviate security concerns is to have a Trident-specific annotation in the PVC and in the corresponding Trident-provisioned PV that would allow the PV to be duplicated and accessed across different namespaces. By default, this property should be turned off. In this proposed design, the user doesn't supply the details of the PV in PVC, but instead specifies the namespace(s) where that volume should be accessed. Trident would then create one PV per namespace and the matching PVC pre-bound to those PVs.
The proposed workflow works well for accessing newly created volumes from multiple namespaces, but accessing a preexisting volume from a different namespace is somewhat different and requires a slightly different workflow. Do you expect to access newly created volumes across namespaces or preexisting volumes? Also, how often do you expect that cross-namespace volumes get created in your environment?

My use case follows this flow: user does not provide/create this pvc/pv. Uses a template that does this for the user. Also I do not need this endpoint for my pv in all namespaces, only in those where this particular type of app is deployed using the template and the template should create the pvc and pv. I was hoping in this scenario if I can pass some kind of annotation with the server and path for a pre existing volume to the pvc object creation inside the template and if trident could just create a new pv inside the namespace with the given server and path in pvc annotation and bind the pv with a pre existing endpoint to the pvc, then it would simplified the workflow of templating my app to a decent extent.

Just want to add a bit more of my concern here. For this template to be execute by a dev, I need to give the devs a special custom cluster role like PV-creator which can only create pv and unable to do anything else. But if an annotation can take care of it with the help of trident, then I can get rid of the PV creation handling part and trident can handle the rest.

I think my previous comment addressed all your concerns.

user does not provide/create this pvc/pv. Uses a template that does this for the user

PVC would be the template through which a user can create PVs pointing to the same volume in different namespaces.

Also I do not need this endpoint for my pv in all namespaces, only in those where this particular type of app is deployed using the template and the template should create the pvc and pv.

My earlier comment address this concern: "the user doesn't supply the details of the PV in PVC, but instead specifies the namespace(s) where that volume should be accessed from. Trident would then create one PV per namespace and the matching PVC pre-bound to those PVs."

I was hoping in this scenario if I can pass some kind of annotation with the server and path for a pre existing volume to the pvc object creation inside the template and if trident could just create a new pv inside the namespace with the given server and path in pvc annotation ...

As I said,  "PV details are not necessarily exposed to users. For example, in OpenShift, regular users don't have enough privilege to get the details of a PV, so they can't supply that information using a PVC to Trident." In the case of NFS, one can get NFS share details by running mount in the pod, but in general users don't have any knowledge of the PV (only admins can run kubectl describe pv and get the details of the PV).

For this template to be execute by a dev, I need to give the devs a special custom cluster role like PV-creator which can only create pv and unable to do anything else.

For the proposed solution that I outlined, there is no need to give devs special privileges.
It seems that you want to access a volume after it has been provisioned from a different namespace as opposed to having Trident expose a volume to different namespaces at the time of provisioning. Is that correct?

I also need to reuse the same volumes in multiple namespaces.
Is there an easy way to do that these days?

@asteven I can share some context here related to your ask. Kubernetes expects volumes to be namespaced. Said differently, PVCs are namespaced. There are a couple of approaches to sharing/exposing volumes across namespaces:

User creates a PVC in namespace A, Trident creates a PV and exposes it for an application in the same namespace. To consume the same volume in namespace B, you can statically define a PV that references a pre-existing volume created by Trident.
Alternatively, the storage admin can create a volume on the storage cluster and have the k8s admin/SRE create PVs in the desired namespaces. This way, the volume is created without an associated PVC.

@balaramesh Thanks for the answer. I know how to do this by hand. The question was if trident gives me some sugar here ;-)
Guess that's a no. No Problem.
:wave:

@asteven you are right there isn't a way to achieve this natively through Trident right now

Hi,
we need to share the same image in different namespace without cloning/snapshot it.
I tried, as suggested before, to copy the original pv/pvc and run a pod using the new pvc.
What i did is the following:

Create a Deployment with a pvc in the namspace X
When pods are up&running copied the pvc and pv into a yaml file.
Change pvc and pv name and their references between them.
Apply the new pvc/pv to the cluster in the namespace Y
They were bounded together
Create a 2nd Deployment in the namespace Y
Pods remaining in "Container Creating" status and the error is : MountVolume.SetUp failed for volume "pvc-nginx-nfs-pvc-clone" : rpc error: code = FailedPrecondition desc = staged device info file not found

Any modification to the pvc/pv doesn't change anything...
From the trident pod i can see the following log:
trident-main time="2021-12-16T14:59:33Z" level=error msg="Unable to find staged device info." error="stat /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-nginx-nfs-pvc-clone/globalmount/volumePublishInfo.json: no such file or directory" requestID=f687d4c1-89f6-48de-b64e-52acd9f5dbf7 requestSource=CSI stagingTargetPath=/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-nginx-nfs-pvc-clone/globalmount/volumePublishInfo.json                                                                                trident-main time="2021-12-16T14:59:33Z" level=error msg="GRPC error: rpc error: code = FailedPrecondition desc = staged device info file not found" requestID=f687d4c1-89f6-48de-b64e-52acd9f5dbf7 requestSource=CSI
What i can understand is that the trident plugin is trying to find a json file in a path on the node where the pod is running.
But it's unable to find it, because the file is under the path **/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-c3d33062-d0db-48b6-9ee5-2d2ba24dd234/globalmount/volumePublishInfo.json ** that is the path for the pv in the namespace X.
If i stop the pods on the namespace X , the pods in the namespace Y are working.
So there's a way to use the same pv between different namespace using nfs netapp storage?
Thanks in advance.


updating database_host IP for every user from a server

Solves a part of https://github.com/CartoDB/cartodb-platform/issues/5491

@oleurud review?

Retest this please


New version: ReservoirComputing v0.6.2

Registering package: ReservoirComputing
Repository: https://github.com/SciML/ReservoirComputing.jl
Created by: @MartinuzziFrancesco
Version: v0.6.2
Commit: 924588437e3d3619b7f1bda425ae9e7c94a2e642
Reviewed by: @MartinuzziFrancesco
Reference: https://github.com/SciML/ReservoirComputing.jl/issues/1#issuecomment-787472613

This failed because of an IRTools issue so I'm overriding it.


Upgrade Node 22.11.0 and Yarn 4.5.1

I can't seem to build at all locally so seeing whether this works in CI

going to re-attempt this after #1303 to see if some of the issues resolved given the upgrades made there


Images paired with HTML files in output folder

I'm using the following script to point at an existing localhost server:
gulp.task('screenshot', function () {
  gulp.src('./build/**/*.html')
  .pipe(localScreenshots({
    server: false,
    port: 3009,
    type: 'png'
   }))
  .pipe(gulp.dest('./screens/'));
});

and the output in screens looks like:

file1.png
file1.html
file2.png
file2.html
...

Is this expected? Is there a way to prevent the HTML from being copied?

Hey yep, you can just omit .pipe(gulp.dest('./screens/'));


Add Hubble CLI integration tests and skip running e2e/conformance on Hubble CLI only changes

Since moving Hubble CLI into the Cilium repository I noticed 2 things:

We're running all the regular e2e/conformance tests for Hubble CLI changes. Since we're not building Hubble CLI from source in any of those tests, it doesn't make sense to run them for CLI only changes.
We didn't copy the existing Hubble CLI integration tests.

In this PR I address both of these issues. This is my first time introducing a new Github workflow, so I mostly copied the existing Hubble CLI integration tests and adapted it based on existing conformance test workflows to follow existing conventions 🤞 .

https://github.com/cilium/cilium/actions/runs/9960830594/job/27520969056?pr=33850 needs to be fixed 🔧

/test


Bug: get_many_to_one() and get_one_to_many() examples aren't displaying correctly

What happened?
This is what is currently live on the admiral website:

Session Information
No response
Reproducible Example
No response

Umm...I wonder if admiraldev should be in the example

Also...wonder how that doesn't fall over in the check()

I think the try() wrapper lets us get through with error, but this was an unexpected error.
I stumbled upon it when investigating the implications of https://github.com/pharmaverse/admiral/issues/1572 and https://github.com/pharmaverse/admiraldev/issues/179 . There's actually chain of functions:
derive_param_tte >> assert_one_to_one >> set_dataset
get_many_to_one >> get_dataset
get_one_to_many >> get_dataset
At the bottom of these chains, there's hard code that refers to the .Datasets environment, but both of these .Datasets environments are individually created in both admiral and admiraldev, still trying to dissect that means when we try to consolidate the environment lines


C++ make test fails test #3 and test #4 never seems to end?!

Following the build instructions and running make worked without issue on my Ubuntu VM. However running 'make test' didn't work so well:
$ make test
Running tests...
Test project /home/simon/FASTER/cc/build/Release
    Start 1: in_memory_test
1/5 Test #1: in_memory_test ...................   Passed    2.18 sec
    Start 2: malloc_fixed_page_size_test
2/5 Test #2: malloc_fixed_page_size_test ......   Passed   13.12 sec
    Start 3: paging_queue_test
3/5 Test #3: paging_queue_test ................***Exception: Other340.92 sec
    Start 4: recovery_queue_test

Is test #4 running 'forever' because test #3 failed?
How to debug the test #3 failure?
How long should make test normally take to run?
Is there a way to make it run faster as a kind of quick test after a code change?

More info: Upon re-running make test I monitored the paging_queue_test program for test #3. While running, it used all CPU and memory usage slowly climbed to about 2 GB out of 4 GB total on the VM. Then memory stopped climbing for a good long while, and started climbing again until eventually the exception happens again at higher memory usage.
I'm guessing test #3 requires a minimum amount of GB of RAM to run? It would be good to fix the test so that it complains with a human friendly warning if not enough RAM, instead of the cryptic failure currently output after many minutes.

Thanks, we will look into fixing the test to provide such a warning. We also accept PRs after the CLA is signed :).

We have reduced the testcase data sizes and number of threads so that they complete quicker when run on normal machines.


Compact/compresesed hosts File compatibility?

N.B.: I'm not sure if this is the right place to ask this. Please move as you see fit.
Do the various AG products handle hosts file compacting (usually called "compression" which seems like wrong terminology), such as that performed by https://github.com/ScriptTiger/Hosts-Conversions?  (For that matter, can they handle actual hosts/filterlist compression, like gzip, zip, 7z, &c?) There's some discussion that this will need to be done on some very large adblocking lists due to various problems elseplace (OS issues, browser storage restrictions, &c), so I thought to ask.

AdGuard supports hosts-file syntax only in DNS blocklists, and any valid hosts file should work there. If that is not the actually the case, please file an issue here.
Regarding filter lists compression, there's little point in supporting it for AdGuard, since our apps are bound only by the amount of storage and RAM.

@ngorskikh The major reason I asked re: support for such is for a subscription for such from a 3rd party, so, if the (hosts|filterlist) file is served in 1 or more of the above ways (e.g., 9-hosts-per-line compacted & gzipped), would that be directly supported?

"Compacted" hosts files are valid hosts files, so they are supported.

We don't support loading of gzipped files.

DNS filter lists are not loaded into memory. We rely on reads from disk cache. If decompress them, they will take place in memory, which is not acceptable, e.g. on iOS with hard memory limit for network extensions.

Thanks very much for the clarification! 🙇🏾♂

Another question related to this:  Would there be any advantage/disadvantage to AG apps in using these compacted forms?  Or do they resolve to the same representation internally as the equivalent uncompacted file?

Pretty much the same for AdGuard

Again, thanks very much.


Use Gradle's variant-aware dependency management and allow using Gradle's built-in Java Module System support

Hi 👋 I recently became aware of the current state of JavaFX support in Gradle and there are two things that are quite painful for some users right now. Both could be improved, if the implementation in this plugin (and maybe later JavaFX itself) would rely on Gradle's variant-aware dependency management and Gradle Metadata.
The issues

It's hard to publish libraries relying on JavaFX with good metadata due to the cross-cutting concern of selecting the right "JavaFX Platform Jars". (Which is one of the main use cases that variant-aware dependency management with variant selection based on attributes solves.) See e.g.: https://github.com/gradle/gradle/issues/26144
This plugin is bound to  another plugin –org.javamodularity.moduleplugin – right now. That does not work well together with Gradle's built-in Module System support (added in Gradle 6.4). It would be good if users of JavaFX can choose which of the mechanism they like to use.

Details
(My background is that I worked on both the dependency management and the Java Module support in Gradle – I was part of the Gradle core development team for several years – and continue contributing in these areas.)
This PR proposes a full implementation. It also extends the test coverage to show that things still work as before (from the user perspective) but better. It purposefully does not change the API of JavaFXOptions so that the changes should not have an effect on how users use this plugin. Before the actual code change, this PR contains three commits for the following:

Updating the Gradle Wrapper to the current release (8.3)
Updating the "build.gradle" and "settings.gradle" and the plugins used in them to the latest standards and features. Basically doing some cleanup there. I followed what we do for all the plugins of https://gradlex.org/
Updating and extending the smoke test. It now:

Tests against multiple Gradle versions
Checks the actual -classpath and --module-path parameters used when Gradle calls javac and java by parsing Gradle's --debug output.
Has two additional tests: building with a local JavaFX sdk, using Gradle's built-in Module System support (since Gradle 6.4)

Main code changes

The JavaFX platform selection is now based on variants. This mechanism is available since Gradle 4/5 and stable since Gradle 6. It's prominently used for instance in Kotlin Multi-Platform where many libraries have similar requirements (different artifacts for different target platforms). Here are some docs. I am happy to explain more if there are questions:

Docs: https://docs.gradle.org/current/userguide/variant_model.html
Example with native Jars: https://docs.gradle.org/current/userguide/component_metadata_rules.html#adding_variants_for_native_jars
Discussions: https://github.com/gradlex-org/java-ecosystem-capabilities/issues/57, https://github.com/gradle/gradle/issues/26144#issuecomment-1686037462

Then, based on that or as general improvement/simplification

Transitive dependencies no longer need to be maintained in the plugin
Empty Jars are completely gone from the classpath autoamtically (see test assertions)
Manual classpath and module path modification limited to minimum (only required for running non-modular applications, as Gradle does not support non-modular Apps with some Jars on the --module-path yet directly)
No hard dependency on 'org.javamodularity:moduleplugin' anymore
Dependency declaration done lazily (via withDependencies)

With these changes, the minimal supported Gradle version becomes 6.1 as only then all the dependency management APIs used are available.
Next steps / JavaFX and Gradle Metadata
The change contains a JavaFXComponentMetadataRule. This extends the metadata of JavaFX. In the future, JavaFX could publish this information (using Gradle Metadata) directly. Then this plugin will mostly become a convenience for defining dependencies to JavaFX. But, in particular in Module Path-based projects, JavaFX could even be used without this plugin.

I know this is a rather large change. I can add more documentation and explain things in more detail. I wanted to push this out to get the discussion started.

FWIW I can at least confirm that this is working on a few projects that I quickly tried it (FXyz, litfx, controlsfx, hansolo charts, trinity, etc.) on. It generates the GMM and POM I would expect.
Was able to even remove the manual pom modifiers used on some of these projects to remove the classifier from the generated maven poms.
pom.withXml {
    asNode().dependencies.'*'
            .findAll() { it.groupId.text() == 'org.openjfx' }
            .each { it.remove(it.classifier) }
}

One thing worthy of mention is that projects that relied knowingly/unknowingly on the transitive 'org.javamodularity.moduleplugin' will now have to be explicit about it otherwise their builds could likely fail as a result, hence I’d consider that a breaking change from a plugin perspective so maybe it deserves a bigger version bump, or doc updates highlighting this change.

Thanks for the PR, I believe that can indeed be helpful to developers.
Pinging @abhinayagarwal , @jperedadnr  or @tiainen : can one of you review this?

Thank you for the quick response and the thorough review @jperedadnr. I addressed the feedback and answered the questions. Let me know if you have more.

I think that this will fix the following issues:
https://github.com/openjfx/javafx-gradle-plugin/issues/133
https://github.com/openjfx/javafx-gradle-plugin/issues/126
https://github.com/openjfx/javafx-gradle-plugin/issues/94
Possibly https://github.com/openjfx/javafx-gradle-plugin/issues/26 too.

Okay, let's merge and test before doing a new release, and see if those issues can be closed.

I can test on my local pet projects where I hit this bug. If there's a nightly/integration version out I will test before a stable release is made.

The snapshot gets published to Sonatype, you just need:
pluginManagement {
    repositories {
        maven {
            url = "https://oss.sonatype.org/content/repositories/snapshots"
        }
        gradlePluginPortal()
    }
}

I tested 15-SNAPSHOT and can confirm that, in Eclipse, the JavaFX modules now appear as "is modular" while "Project and External Dependencies" is on the classpath, and the test libraries (JUnit) appear as "not modular". This allows the tests to work on the classpath as they should, while there are no JavaFX missing modules in module-info.java.

I also rolled back to version 14 and saw the problem reappearing, so the snapshot version definitely saves the day here.
Thanks @jjohannes!

I'll note that this revives a problem with the gluonfx gradle plugin that was partially fixed in https://github.com/gluonhq/gluonfx-gradle-plugin/pull/107. I can provide a reproduceable example on that project's repo if needed.

@nlisker can you please open a new issue for this?

@nlisker can you please open a new issue for this?

Created https://github.com/gluonhq/gluonfx-gradle-plugin/issues/179


Create custom component for responsive iframe giphys

It's always the same code which it's being used to write  responsive iframe.

it should be created a custom component (giphy-emb) which accepts the embed URL and a caption. Final result must be:

Closed by #74


Finalize figures for Drivers paper

Thread to discuss drivers paper figures

That sounds like a good plan. I'll review next week and then lets schedule
a time to meet.
On Wed, Oct 18, 2023 at 12:36 PM Thomas Thelen @.***>
wrote:

@anardek https://github.com/anardek @caseydietrich
https://github.com/caseydietrich at long last, I have a draft set of
Drivers paper figures and tables to share. The PowerPoint slide available
at this Googe Drive link
https://docs.google.com/presentation/d/1Xz3-udleOrGq2EITCfPuxjKG18VGCSlx/edit?usp=share_link&ouid=100107816394245514762&rtpof=true&sd=true
contains all the draft section headings, subheadings, figures, tables, and
captions that I plan to include in the Drivers paper. The section headings
are included to give you a sense for how the tables and figures fit in the
narrative flow. Note that some of the figures and tables may be low
resolution because I have snipped them from a Google Doc or somewhere else.
These items will be higher resolution in the final iteration.
There is a lot of content in this slide deck, much of it being content
that you have not seen before. I think it may too much to discuss in one
meeting. Perhaps it would be better to have your two review and comment on
the slides first, then meet to discuss once I have had a chance to review
your comments? Let me know what your thoughts are on the best way to review.
Now that the narrative and draft figures are taking shape, I think it
might also be a good time to circle back to our discussion of what journal
we should target for publication. We discussed this topic way back in the
spring, but tabled the discussion until we had a better sense for what the
paper would look like. It would be nice to know what journal format I
should be targeting as I now finalize figures, formatting, narrative, etc.
I look forward to receiving your feedback on the figures!
—
Reply to this email directly, view it on GitHub
https://github.com/NCSU-CHAZ/Sunny-Day-Flooding/issues/28#issuecomment-1768929885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANXYL54MA3PMEE2CZSQHRT3YAAAPVAVCNFSM6AAAAAA6FZP56CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRYHEZDSOBYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Journal options:

Water Resources Research
Water Research: published studies on NYC flood sensors, Chesapeake Bay tidal flooding WQ sampling and modeling

Hi @anardek and @caseydietrich, I am circling back to this thread to see what the timeline for figure review and discussion might look like. I completely understand if the disruptions that came up this week mean that you all will have to push back your timeline for reviewing past what we originally discussed. Just let me know what you think is a reasonable timeline for review and discussion, and I will plan around that.

Thomas, I reviewed and added comments. @caseydietrich - can you take a look?

Also, I vote for Water or WRR. Lets try Water first.

@ththelen I reviewed and added comments. I'm not familiar with Water Research, but if they have published similar papers, then I agree it is a good target. (cc: @anardek )


[javalinvue] Rework configuration

Not sure why the java test was messing up various tests, but I just removed it...


No FundingLocked is sent from LND funded private channel

Background
LND does not send a FundingLocked in a private channel where it is a funder, so channel never enters operational state. This does not happen when LND is a fundee.
When looking at message log while having an opening channel I see this (funding tx has 8 confirmations at this point):
<-- Init(,82)

--> ChannelReestablish(34d6ca2e25265c70abee4af7ad96f4d99d4804e9138586b33878805a1949cdd8,1,0,Some(0000000000000000000000000000000000000000000000000000000000000000),Some(02055c7176524bffc348d496980306d8687a1f2c3ca8e40498039421aae6c264ef))

<-- ChannelReestablish(34d6ca2e25265c70abee4af7ad96f4d99d4804e9138586b33878805a1949cdd8,1,0,Some(0000000000000000000000000000000000000000000000000000000000000000),Some(02967d09d22fdea3cdc26e1b34bd1ce6887bb91963be08299f522b67e18bf8b921))

--> FundingLocked(34d6ca2e25265c70abee4af7ad96f4d99d4804e9138586b33878805a1949cdd8,02348b6183f96595ab74364622c4553a0d6e30138cad80598e20be68c5c293626b)

<pings, gossip but no FundingLocked from LND>

Your environment
0.5.1-beta commit=v0.5.1-beta-42-g668bd4db33b4c1ceb3b86836061e7faf99b3d080
Steps to reproduce
Fund a private channel using LND.
Expected behaviour
FundingLocked is sent by LND once funding tx gets enough confirmations.
Actual behaviour
No FundingLocked is sent.

Here are the relevant logs on my end: http://paste.ubuntu.com/p/nZCms3RgQP/

Here's another similar channel with logs set to TRC near the end http://paste.ubuntu.com/p/sJ7GDHx53z/

Thanks @juscamarena!

2018-12-04 16:02:26.790 [INF] NTFN: New confirmation subscription: txid=d8cd49195a807838b3868513e904489dd9f496adf74aeeab705c26252ecad634, numconfs=1000
2018-12-04 16:02:26.790 [ERR] FNDG: Unable to register for confirmation of ChannelPoint(d8cd49195a807838b3868513e904489dd9f496adf74aeeab705c26252ecad634:0)
2018-12-04 16:02:26.790 [ERR] FNDG: waiting for funding confirmation failed

The reason for this is because lnd failed to register for a confirmation of the channel point due to attempting to register for 1000 confirmations. At the moment, lnd only allows registering for a maximum of 144.

2018-12-04 16:02:26.138 [INF] FNDG: pendingChan(ec81dc9a10ca44993c815f0a894a93d91dfc2a21386a525a7ef18033f61138eb): remote party proposes num_confs=1000, csv_delay=1440

@btcontract is there a reason for BLW (I'm assuming this is the node on the other end) proposing 1000 confirmations to us? Seems a bit absurd IMO. Maybe just a bug?
We'll only resend FundingLocked once we know of the channel being confirmed, which explains why it's not being sent.
I believe if you restart the lnd node then everything should be fine.

#2275 will  prevent this from happening in the future.
@juscamarena if you'd like to keep this channel, I believe the following diff should be enough. Let me know otherwise.
index 2bf15789..9a729d14 100644
--- a/fundingmanager.go
+++ b/fundingmanager.go
@@ -1856,6 +1856,9 @@ func (f *fundingManager) waitForFundingConfirmation(completeChan *channeldb.Open
 		return
 	}
 	numConfs := uint32(completeChan.NumConfsRequired)
+	if numConfs > 100 {
+		numConfs = 3
+	}
 	confNtfn, err := f.cfg.Notifier.RegisterConfirmationsNtfn(
 		&txid, fundingScript, numConfs, completeChan.FundingBroadcastHeight,
 	)

Great, will try it out, thanks

hurr durr yes it's a BLW bug. I've mixed up htlcMinimumMsat and minimumDepth in AcceptChannel which are 1000 and 1.


template engine use, how should it work?

I'm writing tests and tweaking the functionality, and it seems I broke something, so I need clarification.
If I understand it correctly the use call sets the engine to use for all views. How is that set? It doesn't seem to change defaultEngine.
I'm contemplating creating the client object with a prototype of defaults. One of the defaults would be the templateEngine. That would allow bundlers to set their own default template engine by setting it on the client.
I think the ideal for a template engine to have a path matching variable or function that will determine if the engine supports that type of template. I suppose this way you could even support multiple template types in the same view.
@paulbjensen Please advise

@thepian I'll take a look now

I didn't break it, just wrote a bad test, however the question remains; Fundamentally.
Are we happy with the current logic?
You can assign a template engine to a path. By default it is root. (is root the client dir?)
You can't assign it to an extension or a pattern. Perhaps it could be a combination of,

The engine suggests a file name pattern or extension
The app assigns it to a FS branch.

Pushed the tests to the logging branch. We still need tests for subpaths and for custom template engines.

Do we know of any engines that rely on prefix/suffix of template markup?

I think I understand it now


Is it possible to disable Aerospace in some (MacOS) Spaces?

Wondering whether I can configure Aerospace to be active only in certain MacOS Spaces?
I'd like to use a tiling window manager for my "work" Spaces but leave the window layout alone on other spaces.

Please fill in the checklist


[feat] firendly error output when make nsis bundle on linux but got (os error 2)

Describe the problem
I am using tauri cli 1.5.11, i always get Error failed to bundle project: No such file or directory (os error 2) when i build nsis bundle on linux, i don't know why, then i found a issue #6743 about this error, so i think my tauri version is too low, but after i upgraded to 2.0.0-beta.9, this error still exist.
I am so confused, so i debug the tauri cli line by line, i found my binary file name is not nsis needs, just because my package.productionName is BDSM but nsis needs bdsm, the error occoured at:
https://github.com/tauri-apps/tauri/blob/d349558abbefc78baf98f7837e5237f370758931/tooling/bundler/src/bundle/windows/nsis.rs#L636
Here is the error log:
warning: `bdsm` (bin "bdsm") generated 4 warnings
    Finished release [optimized] target(s) in 4m 08s
    Warn Cross-platform compilation is experimental and does not support all features. Please use a matching host system for full compatibility.
    Info Verifying NSIS package
    Downloading https://github.com/tauri-apps/binary-releases/releases/download/nsis-plugins-v0/NSIS-ApplicationID.zip
    Info extracting NSIS ApplicationID plugin
    Downloading https://github.com/tauri-apps/nsis-tauri-utils/releases/download/nsis_tauri_utils-v0.2.2/nsis_tauri_utils.dll
    Info validating hash
    Info Target: x64
    Info Code signing is currently only supported on Windows hosts, skipping...
    Error failed to bundle project: `No such file or directory (os error 2)`

Describe the solution you'd like
I think, can we provide which file name caused No such file or directory like this:
cannot get metadata for /app/src-tauri/target/x86_64-pc-windows-msvc/release/bdsm.exe: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Alternatives considered
No response
Additional context
No response

The issue you linked was fixed before the first nsis release so i doubt it's related.
Is the output you posted with the --verbose flag?
Also please post the output of the tauri info command so we know the versions and OS we're dealing with here :)
Lastly, do you have a minimal reproduction for this, or is your project public?

Yes I used --verbose flag.
My environment is stable because we use Gitlab Pipelines, so the output of tauri info command is always:
[✘] Environment
    - OS: Debian 12.0.0 X64
    ✘ webkit2gtk-4.1: not installed
      Visit https://tauri.app/v1/guides/getting-started/prerequisites to learn more about tauri prerequisites
    ✔ rsvg2: 2.54.7
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: 1.76.0-x86_64-unknown-linux-gnu (default)
    - node: 18.19.1
    - pnpm: 8.11.0
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.12
    - tauri-build [RUST]: 2.0.0-beta.10
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.6
    - @tauri-apps/cli [NPM]: 2.0.0-beta.10
#19 5.942
[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:5173/
    - framework: Vue.js
    - bundler: Vite

Here is minimal produce code repository: https://github.com/LemonNekoGH/os-error-2-minimal
This error can be fixed by change product name to lowercase.

I also have the same problem by running:
cargo tauri build --runner cargo-xwin --target x86_64-pc-windows-msvc
Error failed to bundle project: No such file or directory (os error 2)
Change product name to lowercase solved it.


[SPARK-44965][PYTHON] Hide internal functions/variables from pyspark.sql.functions

What changes were proposed in this pull request?
Hide internal functions/variables from pyspark.sql.functions
Why are the changes needed?
internal functions/variables should not be exposed to end users:
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /__ / .__/\_,_/_/ /_/\_\   version 3.4.1
      /_/

Using Python version 3.10.12 (main, Jul  5 2023 15:02:25)
Spark context Web UI available at http://localhost:4040/
Spark context available as 'sc' (master = local[*], app id = local-1692949938125).
SparkSession available as 'spark'.

In [1]: from pyspark.sql.functions import *

In [2]: ??to_str
Signature: to_str(value: Any) -> Optional[str]
Source:
def to_str(value: Any) -> Optional[str]:
    """
    A wrapper over str(), but converts bool values to lower case strings.
    If None is given, just returns None, instead of converting it to string "None".
    """
    if isinstance(value, bool):
        return str(value).lower()
    elif value is None:
        return value
    else:
        return str(value)
File:      ~/.dev/bin/spark-3.4.1-bin-hadoop3/python/pyspark/sql/utils.py
Type:      function

to_str here is a internal helper function
Does this PR introduce any user-facing change?
yes
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
NO

also cc @ueshin

merged to master


Retry more than once

Implement multiple in-order retries in the producer.
The mental model here is a fairly straightforward expansion of the existing single-retry logic (where the messages go through the pipeline again, and the leaderDispatcher pauses un-retried messages until all the retries have happened in order to preserve ordering).
The new version just keeps track of the high-watermark retry in progress (aka how many times the most-retried in-flight message has been retried) and makes sure that all messages with a lower retry-count are paused until the chaser has been seen.
Fixes #232

There are simple tests, and I am fairly happy with the theoretical aspects of the state machine.
@wvanbergen @drdee @yagnik @mkobetic @snormore feel free to take a look

@Shopify/kafka this is ready for review. Let me know if you want a walkthrough meeting (it's actually a fairly small number of lines-of-code changed, but the logic can be fairly subtle).

It's probably easiest to review the code for this by just reading https://github.com/Shopify/sarama/blob/multiple-retries/producer.go#L397-L479 which is the main loop of the leaderDispatcher goroutine.

This looks good, but maybe we should add some comments to the test case to make the flow more clear.


Add the blacklist creation function to the list of exports

We use a custom rn-cli.config.js file that specifies a custom blacklist. In addition to blacklisting some of our own directories, we still want to keep RN's default rules for what to blacklist so we also call into the packager's blacklist.
Test Plan: Added a small unit test

sure, why not


Extension host terminated unexpectedly. Please reload the window to recover.

VSCode Version: Code 1.11.1 (d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39, 2017-04-06T14:00:34.044Z)
OS Version: Darwin x64 16.3.0
Extensions: none

Steps to Reproduce:
It happens after a minute max after launching VS Code. It started quite randomly. I removed all the extensions, but the issue persists.
Console messages aren't very helpful:
messageService.ts:126 Extension host terminated unexpectedly. Please reload the window to recover.e.doShow @ messageService.ts:126
extensionHost.ts:323 Extension host terminated unexpectedly. Code:  null  Signal:  SIGABRTd.onExit @ extensionHost.ts:323

It started randomly, possibly after the latest VS update (but not immediately after).

I re-installed VS Code, still having the issue.

Does Disable SCM Preview from the Command Palette work around the issue? (Looks like #23976.)

@chrmarti It seems this fixed it. Thanks!

Tracking as  #23976, thanks.

The latest insider update already has this fixed, care to give it a try?

Windows
macOS
Linux 64bit


feature: Validate pipeline config

We should be able to use the ATC configvalidate module^1 in the same fashion that the validate helpers for fly^2 does.

See #42 for why we'd need a lot of convincing for this one.

@isaacsanders Hi! I'm the author of #42. Since the maintainers of this resource seem reluctant to include validation as a feature, I wrote a new new terraform resource with the sole purpose of validating concourse pipeline yaml. If you (or any future readers) are interested in this, please tag me in a comment. It's closed source at the moment, but with enough interest I might be able to convince my team to open source it.


fix line chart renderer crash: can't form range when end < start

ChartsDemo will crash all the time for the Line Chart1 Chart view controller,
This PR fix the line chart renderer crash: can't form range when end < start while phaseX is 0 (from + 1 ..< from + 0 is crashing); use stride instead, seems stride can gracefully fail the loop
@danielgindi I clicked the charts demo one by one, seems others are good, but I'm not sure if any of the rest for loops will have similar issue. Let's fix what we met first.

@petester42 I see builds keeps failing for swift 3? How can we fix it, or we wait Travis CI to fix? Seems the test machine's compiler is not 2.2 yet.

Travis has to update for it to work.

@petester42 what a quick reply! Thanks

Yeah I've just tried to update the travis configuration file, as they've added xcode 7.3 to their supported version. Let's see if it builds :-)

reran today, still complier error :(


Rewrite python docstrings to use markdown

Correct me if I'm wrong but I think reStructuredText is more idiomatic for Python documentation than Markdown

My plan is to use pdoc to generate the documentation. I was looking for something lightweight I can easily embed into our website. Python's sphinx is a bit overweight in my opinion...

@rkaminsk Fair enough. I hadn't heard of pdoc before


Return the number of messages delivered

deliver_messages always returns nil. Can it return the number of messages delivered? This would be helpful for synchronous use cases.

I'm not sure I want the sync and async producer APIs to diverge too much – can you give an example of what you would use this for?

Also, note that #buffer_size returns the number of messages buffered, so you could do:
begin
  message_count = producer.buffer_size
  producer.deliver_messages # you'll get an error
  message_count
rescue
  0
end

That's a good enough workaround, thanks @dasch!


Use Span::source_text in docs rendering to preserve original formatting

A note for the community from the maintainers
Please vote on this issue by adding a 👍 reaction to help the maintainers with prioritizing it. You may add a comment describing your real use case related to this issue for us to better understand the problem domain.

I tried using Span::source_text() to get the original source code of the default expression, but it always returns the span of the first token instead. The span() implementation of syn::Expr does the following:

Convert syn::Expr into a TokenStream
Join all spans in the TokenStream with join_spans
join_spans, in turn calls proc_macro2::Span::join(), but it only works on nightly.

So there is no good way to obtain the original source code with the original formatting currently on stable.


Error: Check Alignment when using SpikeGLXConverter

Describe the issue
Traceback (most recent call last):
  File "/Users/bendichter/dev/nwb-guide/pyflask/apis/neuroconv.py", line 121, in post
    return get_interface_alignment(neuroconv_api.payload)
  File "/Users/bendichter/dev/nwb-guide/pyflask/manageNeuroconv/manage_neuroconv.py", line 445, in get_interface_alignment
    converter = instantiate_custom_converter(info["source_data"], info["interfaces"])
  File "/Users/bendichter/dev/nwb-guide/pyflask/manageNeuroconv/manage_neuroconv.py", line 283, in instantiate_custom_converter
    return CustomNWBConverter(source_data)
  File "/Users/bendichter/dev/neuroconv/src/neuroconv/nwbconverter.py", line 70, in __init__
    self.data_interface_objects = {
  File "/Users/bendichter/dev/neuroconv/src/neuroconv/nwbconverter.py", line 71, in <dictcomp>
    name: data_interface(**source_data[name])
  File "/Users/bendichter/dev/neuroconv/src/neuroconv/datainterfaces/ecephys/spikeglx/spikeglxconverter.py", line 78, in __init__
    interface = SpikeGLXRecordingInterface(file_path=file_path)
  File "/Users/bendichter/dev/neuroconv/src/neuroconv/datainterfaces/ecephys/spikeglx/spikeglxdatainterface.py", line 60, in __init__
    super().__init__(
  File "/Users/bendichter/dev/neuroconv/src/neuroconv/datainterfaces/ecephys/baserecordingextractorinterface.py", line 38, in __init__
    self.recording_extractor = self.get_extractor()(**source_data)
  File "/Users/bendichter/opt/miniconda3/envs/nwb-guide/lib/python3.9/site-packages/spikeinterface/extractors/neoextractors/spikeglx.py", line 53, in __init__
    NeoBaseRecordingExtractor.__init__(
  File "/Users/bendichter/opt/miniconda3/envs/nwb-guide/lib/python3.9/site-packages/spikeinterface/extractors/neoextractors/neobaseextractor.py", line 217, in __init__
    assert stream_id in stream_ids, f"stream_id {stream_id} is not in {stream_ids}"
AssertionError: stream_id imec0.lf is not in []

Steps to Reproduce
Do the tutorial, using SpikeGLXConverter, and click "Check Alignment"
Operating System
OSX
GUIDE Version
main branch
Code of Conduct
Yes
Did you confirm this issue was not already reported?
Yes

Also when trying to click "Next"

Can you expand the accordions? Did the locate data helper find all the paths? Curious what values you have there

The Check Alignment button just didn't work

So we intended for the tutorial to be run using the SpikeGLXRecordingInterface (file_path) rather than the SpikeGLXConverter (folder_path) because we're not working with multi-stream data, though I agree that this choice should definitely still work in practice.
@bendichter It appears that you should have selected ~/NWB_GUIDE/test-data/data/spikeglx/Session1_g0 as the filepath for the converter—though we don't provide great pointers for which directory to choose for this case. I've done this manually and I'm able to get past the Source Data page, and can replicate your error by manually selecting other directories.
@CodyCBakerPhD How should we ensure that users know what path to select for the converters?

ah, ok, I'll try selecting that instead. The newly merged PR here should help with indicating to users precisely which file or folder to select. https://github.com/catalystneuro/neuroconv/pull/771

I suspected that was the cause; so neither the 'Check Alignment' nor 'Next' button should work on this page if the incorrect path is specified
The error message that will popup depends on the interfaces with the wrong path specified. Perhaps we can define some better interceptions before they reach SI/ROIExtractors, etc. But not much that can be done about this on the GUIDE itself

yes, I can confirm that this was the issue. Thanks for the clarification, @garrettmflynn


ERROR: reflect: call of reflect.Value.Type on zero Value

Copying this example straight out of the documentation (https://gohugo.io/templates/functions/#where:904d9cf85d985550c869e6d9741448cc):
	{{ range where .Data.Pages "Section" "!=" "post" }}
		{{ .Content }}
	{{ end }}

Hugo v0.15 outputs two "ERROR: reflect: call of reflect.Value.Type on zero Value" messages (I have only 2 posts in the site currently, so this makes sense.)
The test seems to work as intended (looking at the output), but the error message remains.

I'm on Windows x64, Hugo AMD64, Windows 10.

Oh, my mistake. This is causing an issue -- on a page I didn't notice before. It occurs on an article page, when that code appears in one of the partials the page layout includes. That appears to be the only way to reproduce this.

The error is produced by Go's stdlib, I wish it was clearer -- but I don't think we can do anything about it. .Data.Pages isn't available on content pages, so don't use it in page templates.


Use printable_unicode_list

Get rid of maybe_string and is_ascii_char if possible

If we cant get ridof maybe_string and is_ascii_char then make them private.

Yup, we can ditch it!


Implement Lua and Rust clients

Rust is increasingly popular choice for extremely fast and memory safe programs.
Lua is an easy to use scripting language similar to Javascript. It's often chosen for use in embedded systems. With https://github.com/openresty/lua-nginx-module , you could use permify to control web server permissions.

HAProxy also offers lua support IIRC.
Traefik and Caddy also have some features that could probably integrate in a similar manner (either via standard config like basicauth (Caddy, Traefik) for getting the user via header and forward_auth (Caddy, Traefik) to query Permify, or perhaps as a separate plugin/module).
While Forward Auth can be used to delegate to another service that authenticates with SSO, that same service may lack in control/flexibility of managing permissions but the response can provide relevant auth headers associated to the authenticated user (eg: Authelia, AuthCrunch / caddy-security) and their groups/claims/role which another request could then be forwarded to Permify for an authorization check.
I personally like Caddy (and Caddy Docker Proxy) for it's simplicity with Caddyfile, but Traefik is also quite popular with the label annotation feature for configuring routing to service containers. Perhaps these would compliment the existing guides that already encourage using a container for Permify?
Compared to a specific application integration, the user would be able to manage the checks at the routing level prior to a request being forwarded by the reverse proxy to a service or API? Might benefit adoption / awareness of Permify further that way, which may further encourage adoption in downstream services? (in other scenarios it makes more sense for the application / service itself to perform checks with Permify, but for routing access based on identity that could be done at the reverse proxy level)
If instead going the custom plugin route, some references might be Souin and Sablier. Both are Go based with various reverse proxy and other integrations.

Also would be good to see a rust client 😎


Add http/main back to examples

Dylan 1:26 PM
we were building from source and the makefile included the command go build -o bin/examples-http github.com/moov-io/ach/examples/http when their is no /http directory.  We got it to launch after removing that code but we are still having the application crash after build

Merged https://github.com/moov-io/ach/pull/615


Initial calibration efforts for the 3D cavity single qubit in the new XLD 1000

Feel free to take this as a starting point for further calibration and modify point pull requests to here.

Thanks Sergi,
Could you please let us know the key parameters that you achieved with it? (T1, T2, Readout Assigment fidelity)

T1 and Assignment fidelity are in the parameters. The fit for T2 did not work as intended

Closing this because this chip is not available anymore. If it is needed in the future we can refer to this PR.


ci: run clippy, doctest tests on buildjet-8vcpu-ubuntu-2204

Summary
Upgrades the clippy worker from buildjet-4vcpu-ubuntu-2204 to buildjet-8vcpu-ubuntu-2204
Background
Clippy builds are pretty heavy and far slower than the regular rust builds because they run on a smaller machine.
Changes

Changed the clippy job to run on a bigger buildjet instance.

I piggybacked on this PR and also added bigger runners (and buildjet caching) to the doctest job.


feat: Implement --annotation-style parameter for uv pip compile

Summary
Hello there! The motivation for this feature is described here #1678
Test Plan
I've added unit tests and also tested this manually on my work project by comparing it to the original pip-compile output - it looks much like the pip-compile generated lock file.

Thanks for contributing! Welcome to the project :)
I'm not entirely sure we want to accept more configuration here, I'll need to check with @charliermarsh.
It looks like the Windows snapshots are failing.  You'll need to adjust the regex at https://github.com/astral-sh/uv/blob/ad12d97e714aefdf79267faa8c51a36d4783459c/crates/uv/tests/common/mod.rs#L261-L264

@zanieb I hope you'll accept this one :) Regarding the tests - fixed!

I'm happy to include this.

I have no idea, why it's failing now 🤔

Will review and merge tonight, hopefully.

Thank you! Great contribution.

Thank you! Great contribution.

Thank you for accept it so quick!


docs: add hint for custom root types

Change Summary
Updated docs regarding the access of __root__ with custom root types.
Related issue number
#1372
Checklist

~Unit tests for the changes exist~
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
~changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)~

thanks so much.


Updating the texture on color change is breaking label

Noted by @kived:
kived: dessant: https://github.com/kivy/kivy/pull/3355
kived: that fixes it right now, and keeps markup color working as well
kived: but the real issue is that updating the texture on color change is breaking label, and it doesn't seem to me that it should

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I have not yet experienced this, if someone can reproduce it, please reopen.


Giving up on disabling tags for now

Signed-off-by: Simon Bennetts<EMAIL_ADDRESS>

Was this a usage issue or did I bungled the implementation somehow?
https://github.com/zaproxy/zaproxy/pull/5774

No, I think I messed up somewhere and just wanted to get the scan running rather than fix my own mistakes :D
It worked fine locally - was also in a meeting so couldnt focus on it too much...


[ADP-2355] remove field delegation from WalletMetadata

removed delegation field from WalletMetadata

Comments

Issue Number

ADP-2355

bors r+

bors r+

bors r+

bors r+

bors r+


Passing URL-encoded values to op doesn't work

This is very minor since we can fix this on the client side of things. But just in case you want to know:
If I generate an URL with op=resize,rotate it works. But URLs generated as op=resize%2Crotate does not. However, the latter should be perfectly valid and was easy to generate by accident by automatically urlencoding all params passed.

Hi, I apologize. I may have jumped the gun on what was going on on my side, this doesn't seem to be the issue exactly.


javascript and int64 as map key

What language does this apply to?
javascript
Describe the problem you are trying to solve.
With an int64 message field, one could annotate it with the option [jstype=JS_STRING], but what to do with an int64 map key?
Describe the solution you'd like
Support for  [jstype=JS_STRING] option with map key/value(or it's already there, but with different syntax?)
Describe alternatives you've considered
Additional context
I'm using protoc 3.6.1, with proto2 syntax

This is a limitation of the current API. We're thinking of introducing an abstraction for 64 bit integers to deal with this.

Is there any update on this topic?
What is the best way to define such a map with the existing support?


Update readme and resolve splat warnings

Thanks so much for this repo, it's saved me a huge amount of time this evening!
Unfortunately, I'm getting warnings and errors when I'm running this. I'm using:
Terraform v0.11.8
+ provider.aws v1.31.0
+ provider.template v1.0.0
+ provider.terraform v1.0.0

Here's a warning:

Warning: output "attribute": must use splat syntax to access aws_lb_ssl_negotiation_policy.policy attribute "attribute", because it has "count" set; use aws_lb_ssl_negotiation_policy.policy.*.attribute to obtain a list of the attributes across all instances

And errors like this:

module.(mymodulename).module.ssl-policy.module.mozilla-old.output.load-balancer: Resource 'aws_lb_ssl_negotiation_policy.policy' not found for variable 'aws_lb_ssl_negotiation_policy.policy.load_balancer'

I've found that by updating to use the splat, everything seems to work correctly. I'm not 100% sure on the implications of this - I guess it may affect other outputs, but it seems to work for my scenario.
I also noticed the readme hasn't changed since the update to the repo name, so I've popped that fix in too :)

@edhgoose Thanks for the PR. I found the relevant change documented at https://www.terraform.io/upgrade-guides/0-11.html#referencing-attributes-from-resources-with-count-0
I'll verify whether this is backwards compatible with our usage and merge soon :raised_hands:

I've merged #2 instead with a similar (but backward compatible) change. Thanks a lot :+1:

Great, can confirm that works too :)


MegaCom and Sample management

Continuation of:
https://github.com/jmamma/MIDICtrl20_MegaCommand/pull/104
https://github.com/jmamma/MIDICtrl20_MegaCommand/pull/128
Those branches are too outdated but I have this comm_wav_merge that I kept synchronizing to master.
@jmamma With the latest enhanced_gui code merged, the PROGMEM limit is reached so I have to drop the wave editor -- but this is not to abandon this functionality -- we can move this to MD.

.spk sample packs in SD-Drive

[x] Push

.syx in SoundBrowserPage

[ ] Send (NOT WORKING)

SampleManager with gateway 0x34

[x] List, implementation in FileBrowserPage
[ ] Rename, erase, copy/paste

Better .wav file support

[x] extended attribute
[x] multi-channel wav files
[ ] smpl chunk

[x] loop points
[ ] root node
[ ] slices

WavEdit

I'm okay with stripping out the wav editor for now.
Unless you think otherwise, MegaCom should not be added to next MCL release, given the scope of changes to GUI and potential for bugs.
We can do a small MCL release shortly after

Unless you think otherwise, MegaCom should not be added to next MCL release, given the scope of changes to GUI and potential for bugs.

So is the wav branch, so I think they can be coordinated.
I cannot maintain two old branches at once T.T


Add top level documentation and tidy for consistency

Ok, hopefully bors is fixed now
bors r+

Nope
bors r-

bors r+


[GH-565] trophies currencies feature

Motivation
Explain why not how.
Closes #issue_number
Summary of changes
List your changes here.
How to test it?
You can explain how you tested it or suggest a way to do so.
Checklist

[ ] Tested the changes locally.
[ ] Reviewed the changes on GitHub, line by line.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Rebase pr


assertContent() Function - Allow option to assert ordering

Probably on by default.
When passing in multiple values to assertContent(), if item 1 is listed after item 2, then the assertion should verify the ordering is the same in the actual response object.
This option needs to be toggle-able, such as for content that is generated from unordered values (randomization, sets, etc).

Implemented, and toggle-able via a passed function param.
Leaving issue open in case we want to create a project settings variable to configure default state (default is to assume ordering is desired).


Nuxt3.3 doesn't work on windows

Environment
I can't
Reproduction
Use windows and run a command.
Describe the bug
Here the log (sorry, I don't really understand the issue)
node:internal/errors:484
ErrorCaptureStackTrace(err);
^
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
at new NodeError (node:internal/errors:393:5)
at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1026:11)
at defaultResolve (node:internal/modules/esm/resolve:1106:3)
at nextResolve (node:internal/modules/esm/loader:163:28)
at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
at ESMLoader.import (node:internal/modules/esm/loader:525:22)
at importModuleDynamically (node:internal/modules/esm/translators:110:35)
at importModuleDynamicallyCallback (node:internal/process/esm_loader:35:14)
at file:///C:/Users/esoubiran/dev/barbapapazes/le-classement.fr/node_modules/.pnpm/nuxi@3.3.0/node_modules/nuxi/dist/cli-wrapper.mjs:9:3 {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
Node.js v18.12.1
Additional context
No response
Logs
No response

Would you provide a reproduction? 🙏

Yes, I'm looking to reproduce this on windows.

This is resolved in Nuxi 3.3.1. Make sure you are running npx nuxi@latest.

Still got the same error using after updating package to nuxt 3.3.1

So.. nuxt 3 no longer works on node 14.. have to use node 18

Node 14 will reach EOL in April and will no longer be supported at that point. But thanks for the heads-up. Fix incoming.

@danielroe  thank you 🙌! There is no real good reason to stay on 14, it was just a surprise and some guess work to figure out the issue. It would prob help some people to include end of support in the April change log. Thanks

We will for sure 💯

I'm using Node 18.15.0, npm 9.6.2, Nuxt 3.3.2, and I'm getting this error. specifically, it's
[worker reload] [worker init] Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

  at new NodeError (node:internal/errors:399:5)
  at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11)                                                                                13:07:17
  at defaultResolve (node:internal/modules/esm/resolve:1135:3)
  at nextResolve (node:internal/modules/esm/loader:163:28)
  at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
  at link (node:internal/modules/esm/module_job:76:36)

My dependencies
"devDependencies": {
    "@nuxt/test-utils-edge": "^3.0.1-rc.0-27810184.d991a55",
    "@nuxtjs/google-fonts": "^3.0.0",
    "@types/d3": "^7.4.0",
    "@types/uuid": "^9.0.1",
    "@vitejs/plugin-vue": "^3.2.0",
    "@vitest/coverage-c8": "^0.25.8",
    "@vue/test-utils": "^2.3.2",
    "jsdom": "^20.0.3",
    "nuxt": "^3.3.2",
    "unplugin-auto-import": "^0.12.2",
    "unplugin-vue-components": "^0.22.12",
    "vitest": "^0.25.2"
  },
  "dependencies": {
    "@auth0/auth0-vue": "^1.0.3",
    "@google-cloud/storage": "^6.9.4",
    "@prisma/client": "^4.11.0",
    "@vue-stripe/vue-stripe": "^4.5.0",
    "@vueup/vue-quill": "^1.1.1",
    "d3": "^7.8.3",
    "jose": "^4.13.1",
    "libsodium-wrappers": "^0.7.11",
    "prisma": "^4.11.0"
  }


[Code health] Complete survey proto definitions

Assign any unimplemented features as TODOs to @gino-m

If we're going for the big bang approach, I can take this one.

Is this a dupe of https://github.com/google/ground-android/issues/2049? @gino-m

Yes! Closing now.