Feature: Test running functionality

Hi! I'm not sure if this issue should be opened here or on the elixir-ls repository. Please let me know if this is not the right place and I'll gladly move it.
I've recently been playing around with adding test running functionality to the extension. My first step is to have the extension provide code lenses to automatically run tests on click (like Jest Runner does).
I've got a simple POC which works on the following levels:

A new function in ElixirSense returns all of a file's metadata (I'm guessing this is probably not required, but it was quick and good enough for a POC)
ElixirLS uses that metadata to identify all calls to the functions "test" and "describe" in files for which the path contains "test". Code lenses are returned for each of these calls, as well as for the first line of the file (to run all tests).
VSCode ElixirLS provides a command to run tests based on a provided filter in a terminal, which is invoked upon clicking the code lens.

Before going any further with this I wanted to check for interest for such a feature and gather comments on a good implementation.

@Blond11516 sounds great. Please go on with the PRs

I've moved this to the elixir-ls repository since I think it fits better here.
I think this would be a great enhancement! And I definitely like that ElixirLS would be returning all the potentials locations that could be tested.
Some thoughts:

Ideally we could support other testing frameworks than pure exunit, for example https://github.com/whatyouhide/stream_data
It would be great if we could execute the tests on the server-side but I'm not sure we could show the results to the user in a helpful way, so it's probably to leave that as future work (if ever)

But the benefit would be to get the test-running support to work for any LSP-aware editor instead of only VSCode ElixirLS

@lukaszsamson/@msaraiva do you have any thoughts on the ElixirSense/finding all the tests for a given file?

It would be great if we could execute the tests on the server-side

I'd avoid executing client code in ls process

do you have any thoughts on the ElixirSense/finding all the tests for a given file?

Maybe full metadata is not necessary and we could do a simple test extraction similarly to what DocumentSymbolsProvider does.

It would be great if we could execute the tests on the server-side

I've seen it done (see the Java Test Runner as an example) but you do lose access to the terminal and you have to come up with some other way of displaying test results. So if we wanted to do it, it would require quite a bit more work.

It would be great If we could support running a single test with debugger also. IIRC there were some feature requests for that.

Ideally we could support other testing frameworks than pure exunit, for example whatyouhide/stream_data

I've been looking into this for the past few days and the only way I've found to do this is to manually add checks for the libraries we'd like to support. I've been playing around with Elixir Sense's expand_full function to see if there's something common to all test macros that we could use, but I couldn't get it to expand test, which I'm assuming is normal, but I don't understand ElixirSense (or macro expansion) enough to say why.

It would be great If we could support running a single test with debugger also

Yeah that was on my todo list too. From what I've seen from other extensions this should be fairly easy to do once the test running functionality is done.
I've also been looking for a more robust way to identify runnable tests. By directly playing with ElixirSense's parser and metadata I can fairly easily check whether a module imports ExUnit.Case (and other related modules), which I think would be a fairly good way to identify if a file should be considered as "test file" (although not so clean). From there, as stated previously, I haven't been able to find a more robust or generic way of checking for test calls.
I've opened a draft PR so you can see where I'm at right now: #389

Thanks a lot @axelson and @lukaszsamson for your help on this. This felt a little big and scary at first but your feedback helped me a ton along the way!
I'm really motivated to improve on this, so you can expect to hear from me again in the future ;)

Congrats on getting in! We're glad to have a contribution from you and we look forward to more in the future! :tada:


Kitura Compatibility: Converting to Numeric Types from String's

We talked about this before Harlan, but I wanted to note where this issue was coming up for me. And an ensuing concern.
Previously, I mentioned I had a need to convert from strings to numeric values in my decoding (see https://github.com/hkellaway/Gloss/issues/268). We discussed this and decided at the time that decoding a number from a string might be considered an error or special case. The standard for json integers is to not have them quoted. E.g., {"intvalue": 1}. See also http://www.json.org.
I looked through my code to see where this was coming up and it turns out that it crops up due to my use of Kitura to provide HTTP support for my server. In this, Kitura has a RouterRequest object and this object has a method queryParameters. queryParameters provides, in dictionary form, the parameters from the incoming HTTP request present in the URL. All of the values for the keys in the query are provided as strings. For example if the query was http://foobar.com/?key=100, then the resulting dictionary from queryParameters would be ["key": "100"].
Since Kitura is a pretty common library to use when developing servers using Swift, I wanted to raise my previous issue as a concern again. It seems like we should have Gloss support commonly used server-side use cases. It also looks like Vapor, another popular server side framework, does something similar (see https://vapor.github.io/documentation/http/request.html).

If this is implemented, it needs to be implemented for every "numeric" type Gloss supports, so Int, Double, Float, Decimal, etc.
That is to say you might want to serialize your ["key": "100"] example to:
struct QueryParams {
   let key: Int
}

But I might want to serialize it to:
struct QueryParams {
   let key: Double?
}

But personally, I think this String -> Type conversion would be something better handled inside Kitura/Vapor/etc.  It looks like Vapor at least already does that with SwiftyJSON style .int extensions.  Also it looks like SwiftyJSON is vendored inside Kitura releases anyways.
I think SwiftyJSON is the framework focused on manipulating "untyped" JSON, Gloss is really for JSON <-> struct serialization, IMO adding edge cases to handle malformed JSON sounds like a dangerous path.
And besides, HTTP query parameters aren't really JSON to begin with.  Don't forget that ?key=100&key=101&key=Foo is a valid query parameter in a URL.  Lots of server frameworks in other languages would map to to something like '["key": [100, 101, "Foo"]]'.  My point is that even if this code was added to Gloss it still sounds like there are additional situations that need to be handle upstream and/or in your code.

Interesting. Perhaps I'm using Gloss for something it's not intended for. But, perhaps something could be clarified in the Gloss documentation. Gloss converts between objects and the JSON type which is a Swift dictionary. I usually think of JSON as being either in string format or in actual Javascript, not as Swift dictionaries. I agree that HTTP query parameters are not JSON-like. Swift dictionaries are more JSON-like, but are they JSON?
In any event, for me right now, without this numeric <-> string conversion it costs me specifically is a little less clarity in my model conversion code. I can't use the nice "~~>" style operators in some cases, and have to do things like:
    self.fileVersion = Decoder.decode(int32ForKey: UploadFileRequest.fileVersionKey)(json)

Plus, of course, I have to have an additional Decoder implementation to support this.
So, this raises a slightly different question: Is there a way I could use the "~~>" style notation and "plugin" my feature of numeric <-> string conversion? Does that make sense?

Can't you do?
if let f: String = "key" <~~ json {
    self.fileVersion = Int32(f)
}
else {
    self.fileVersion = nil
}

Or replace the if let with some ! if fileVersion is Int32 rather than Int32?.
Which brings up another good point: these built-in methods would need to return T? since the string might not be parseable so you'd still need to handle that.
You could write your own ~~> function to convert a String to Int? but IMO this shouldn't be something exported by default from Gloss since it'll hurt far more people than it'll help (I'd be mad if I accidentally passed Gloss a string when I typoed an input to a to an Int and it led to runtime issues rather than a failure to compile).  At the very least I'd want it to be a different op like -!> so it's obvious it's doing something non standard, but if I recall correctly Harlan has said he's opposed to adding more ops since it complicates learning the framework.


DocumentDB: cursur within transaction not supported, rest API 500 error above 101 results

Link to reproduction
No response
Describe the Bug
When calling a rest endpoint with a limit higher then 101 and more then 101 results, DocumentDB throws the following error:
MongoServerError: Feature not supported: cursor within transaction. Try increasing the batchsize
This seems to be causes by a limitation of Documentdb
To Reproduce

Add more then 101 items to a collection
Open de admin interface and copy a collection view rest api call
Up the limit to 102 and the api call will return an 500 error {"errors":[{"message":"Something went wrong."}]}

Payload Version
2.3.1
Adapters and Plugins
@payloadcms/db-mongodb

Sorry for the delay. You might consider using the new db: mongooseAdapter( { transactionOptions: false } ) option which disables the use of transactions until this is sorted out.

We are having the same problem. Any possible solution that doesn't require disabling transactions?

@DanRibbens Based on our analysis, this issue seems to stem from the interplay between enabled transactions in Payload CMS, the batchSize setting in Mongoose, and the transaction limitations within AWS DocumentDB.
We require transactions to be enabled for certain hooks to function as expected, ensuring that changes can be reliably rolled back in case of errors. Therefore, disabling transactions entirely is not a viable option for us.
By default, Mongoose uses a batchSize of 101. When a query in DocumentDB returns more than 101 items, Mongoose resorts to using a cursor, which is not supported within transactions in DocumentDB.
We see the following potential solutions:
Increase the batchSize for individual transactions (though this may introduce performance or memory issues).
Disable transactions for specific queries.
Implement a limit and use pagination.
These solutions are applicable in cases where we can directly use the DatabaseAdapter instead of Payload's Local/GraphQL/REST APIs. However, it would be ideal if Payload could provide an option to disable cursor usage within transactions and handle such cases internally.

@r1tsuu and I just talked through this issue and possible solutions. Before we go ahead with a new solution to this problem, we're thinking this is already mitigated by the changes made in v3.
In the beta currently, I've made it so that any read operations don't call initTransaction (they'll use a transaction if one already exists on the req). If I'm correct in this, the only time you'd see a use of the cursor is in a find with pagination that exceeds the cursor limit.
It could be that you also get this when trying to update > 100 docs, in which case we may need a batching mechanism or some custom flags around cursors built into payload or the database adapter.
Can anyone confirm that this is not an issue with documentDB on a recent version of v3 beta of Payload?

@DanRibbens that should fix a lot of the issues, but this will still be an issue in situations where you want to payload.find inside afterChange hooks, where you might want the find changes that are still in the transaction.

@r1tsuu the workaround that we have used for now was to increase the batchsize when querying transactions with mongoose. However this prevents us from using the db adaptor methods. Which batching logic did you have in mind?


Unable to install Gitlab catalog-app from official Helm repository

Rancher versions:
2.1.1
Infrastructure Stack versions:
kubernetes: v1.11.3
Docker version: (docker version,docker info preferred)
Server Version: 17.03.2-ce
Storage Driver: aufs
Root Dir: /big/docker/aufs
Backing Filesystem: extfs
Dirs: 196
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Docker Root Dir: /big/docker
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
4.13.0-46-generic
Ubuntu 17.10
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Add Catalog for Gitlab
Catalog URL: https://charts.gitlab.io/
Branch: master
Kind: Helm

Launch Catalog in desired Project with minimal answers (e.g. for minikube)
name: gitlab (or whatever the suggestion is)
Template Version: 1.2.4
Namespace: gitlab (as suggested by rancher)
Answers (minikube example):

global:
  ingress:
    configureCertmanager: false
    class: "nginx"
  hosts:
    domain: <IP_ADDRESS>.nip.io
    externalIP: <IP_ADDRESS>
certmanager:
  install: false
nginx-ingress:
  enabled: false
gitlab-runner:
  install: false

Results:
The UI indicates that the Catalog-App is in state "Active" but no rescources except for the namespace are actually created.
When deleting the Catalog-App it stays in state "Removing" indefinetly.
I analyzed the Rancher logs and noticed the following:
2018/11/16 09:19:08 [INFO] Creating roleBinding User u-wxv8l Role project-owner
2018/11/16 09:19:08 [INFO] Creating roleBinding User u-wxv8l Role admin
2018/11/16 09:19:08 [INFO] namespaceHandler: addProjectIDLabelToNamespace: adding label field.cattle.io/projectId=p-k2rlq to namespace=gitlab
[main] 2018/11/16 09:19:09 Starting Tiller v2.10.0-rancher5 (tls=false)
[main] 2018/11/16 09:19:09 GRPC listening on :60572
[main] 2018/11/16 09:19:09 Probes listening on :52060
[main] 2018/11/16 09:19:09 Storage driver is ConfigMap
[main] 2018/11/16 09:19:09 Max history per release is 0
[tiller] 2018/11/16 09:19:09 getting history for release gitlab
[storage] 2018/11/16 09:19:09 getting release history for "gitlab"
Release "gitlab" does not exist. Installing it now.
[tiller] 2018/11/16 09:19:09 preparing install for gitlab
[storage] 2018/11/16 09:19:09 getting release history for "gitlab"
[tiller] 2018/11/16 09:19:10 rendering gitlab chart using values
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-role.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-sentinel-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/postgresql/templates/networkpolicy.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-deployment.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/mailroom/templates/deployment.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/role.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-daemonset.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/tcp-configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/clusterrole.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/templates/application.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/operator/templates/operator_deployment.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-rolebinding.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-slave-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-stats-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/minio/templates/minio_networkpolicy.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-server-statefulset.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/default-backend-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-poddisruptionbudget.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/certmanager-issuer/templates/issuer-job.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-pdb.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/postgresql/templates/secrets.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/deployment.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/operator/templates/crd_rbac.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/default-backend-poddisruptionbudget.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-metrics-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-hpa.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/certmanager-issuer/templates/rbac-config.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/rolebinding.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-serviceaccount.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-master-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/serviceaccount.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/ingress.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/pdb.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/hpa.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/certmanager-issuer/templates/cert-manager.yml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/clusterrolebinding.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/udp-configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/registry/templates/configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/headers-configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/controller-service.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/operator/templates/gitlab.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/operator/templates/crd.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/gitlab/charts/mailroom/templates/configmap.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/redis-ha/templates/redis-sentinel-deployment.yaml" is empty. Skipping.
2018/11/16 09:19:10 info: manifest "gitlab/charts/nginx-ingress/templates/default-backend-deployment.yaml" is empty. Skipping.
[tiller] 2018/11/16 09:19:10 performing install for gitlab
[tiller] 2018/11/16 09:19:10 executing 7 crd-install hooks for gitlab
[tiller] 2018/11/16 09:19:10 hooks complete for crd-install gitlab
[tiller] 2018/11/16 09:19:10 executing 7 pre-install hooks for gitlab
[kube] 2018/11/16 09:19:10 building resources from manifest

I find it noteworthy that all templates seem to be empty.
I also looked inside of the Rancher container (exec) and noticed two processes that would not terminate:
root 65632 7  0 09:43 ?  00:00:00 helm upgrade --install --namespace gitlab gitlab --set gitlab-runner.install=false,global.hosts.domain=<IP_ADDRESS>.nip.io,global.hosts.externalIP=<IP_ADDRESS>,global.ingress.class=nginx,global.ingress.configureCertmanager=false,nginx-ingress.enabled=false,certmanager.install=false /tmp/helm-873899453/gitlab
root 65633 7  0 09:43 ?  00:00:00 tiller --listen :60572 --probe :52060

I quick look inside of /tmp/helm-873899453/gitlab suggest that the helm-repo is fully intact with all files present. Here the content for the first templates mentioned:
root@ca3fef8107ae:/var/lib/rancher# ls -la /tmp/helm-873899453/gitlab/charts/redis-ha/templates/
total 60
drwxr-xr-x 2 root root 4096 Nov 16 09:19 .
drwxr-xr-x 3 root root 4096 Nov 16 09:19 ..
-rwxr-xr-x 1 root root  434 Nov 16 09:19 NOTES.txt
-rwxr-xr-x 1 root root 1885 Nov 16 09:19 _helpers.tpl
-rwxr-xr-x 1 root root 2268 Nov 16 09:19 redis-configmap.yaml
-rwxr-xr-x 1 root root  904 Nov 16 09:19 redis-master-service.yaml
-rwxr-xr-x 1 root root  451 Nov 16 09:19 redis-pdb.yaml
-rwxr-xr-x 1 root root  374 Nov 16 09:19 redis-role.yaml
-rwxr-xr-x 1 root root  470 Nov 16 09:19 redis-rolebinding.yaml
-rwxr-xr-x 1 root root 2462 Nov 16 09:19 redis-sentinel-deployment.yaml
-rwxr-xr-x 1 root root  421 Nov 16 09:19 redis-sentinel-service.yaml
-rwxr-xr-x 1 root root 5013 Nov 16 09:19 redis-server-statefulset.yaml
-rwxr-xr-x 1 root root  292 Nov 16 09:19 redis-serviceaccount.yaml
-rwxr-xr-x 1 root root  913 Nov 16 09:19 redis-slave-service.yaml

The only solution to get rid of the stuck application was to kill the helm process in the Rancher container. The UI cleaned up afterwards and the Catalog-App was not visible anymore. I was also able to delete the gitlab namespace from the UI.
I also tested to install something from the Rancher-Catalog and the Helm-Stable Catalog and both Tests worked fine. When installing the Chart using the same values for Helm outside of Rancher it produces the desired results.

@tfiduccia can you try this on v2.2.3? there were some changes in catalog/helm/tiller that might have fixed this.

As it happens I have been trying this on 2.2.3 today with better results, but still no joy.  The namespace is created and the gitlab-ce-postgresql and gitlab-ce-redis containers are deployed and listed as "Active" but with no working pods (the pods are stuck in "Scheduling").  The ingress is defined, but stuck at "Pending".  The app remains in "Deploying" state, and deleting the app now works.

Version: v2.2.3, v2.2.4-rc15, latest master (5/28/19) single-node rancher
(tried to reproduce in each)
I'm having a hard time reproducing the issue; perhaps I am doing something wrong.
Although I did reproduce the info: manifest "gitlab/charts/redis-ha/templates/redis-role.yaml" is empty. Skipping. (and others) as @rothomas mentioned above; that is concerning to me.
When I did the following I saw workloads/pods get created and the app is provisioned. I did notice that gitlab-minio is missing PV info, etc so I can't get it to become "Active" as I am probably missing important information in my config or my setup. Still, the namespace, pods, and everything gets created for me each time I test.

I can also remove the app without any issues. I followed the steps in the issue description very carefully (use the old 1.2.4 template version, use the proper gitlab chart (not ranchers helm chart), try 1.11 k8s, etc).
Some thoughts:
I'm not using the exact same environment as reported. I tried with k8s 1.11.9 (oldest available to me in v2.2.3 rancher) and a few other things and still wasn't able to reproduce the issue except for the issue in logs mentioned earlier.


Add dev tool page and TX builder

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.

Add a dev tool page for us to add some tools that help developers
Add TX builder

Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Add a new input box
Add a nice page

DEMO
View parameters

Failure and successful transactions

Forgot to review this but - I would rather put this section in the footer. For most users, this isn't their focus.

Forgot to review this but - I would rather put this section in the footer. For most users, this isn't their focus.

Sound goo! Done!


Adopt the OCaml Code of Conduct

The OCaml Code of Conduct can be found in ocaml/code-of-conduct and has been discussed in this Discourse thread.
We propose adopting it for ocurrent/ocaml-docs-ci as well.
cc: @novemberkilo @tmcgilchrist

Use https://github.com/ocurrent/.github instead


Fix 'title' tag in Community Guidelines page

Problem: The title of the Community Guidelines page (i.e. community-guidelines.tsx or /community-guidelines path) has a typo.
Solution: To fix & change the tab title from 'Contributors' to 'Community Guidelines'
Expectation: When a user visits the /community-guidelines webpage, he or she should see the words 'Community Guidelines' in the tab of the browser (i.e. title of the document)
Take note: This is a beginner-friendly issue that you can do, with a simple understanding of HTML concepts. You don't need advanced Next.js or TypeScript understanding to handle this. Simply just cltrl F the erroneous title tag & replace it with the correct text.
Images for reference:
Before:

After:

An easy & simple fix to our community website that garners a PR entry for Hacktoberfest 2022 😄

Please ping/tag me here if you wish to be assigned!

I can do this @melvincwng

@GabrielWarner Hi Gabriel, awesome!
Assigned this task to you!
Feel free to add yourself in both CONTRIBUTORS.md & Contributors.tsx webpage if you are familiar with Next.js/React.js
Else, I'll add you as a contributor later.
Thanks!


Create shiftleft-analysis.yml

This is a marketplace action so scan is not required here. Thank you for the PR!


Minor fixes to make oidcng compatible with OpenJDK 11

While building oidcng with an OpenJDK 11 docker image I encountered an issues. With adding an missing dependency it is possible to both build oidcng with OpenJDK 8 and OpenJDK 11.

Merged https://github.com/OpenConext/OpenConext-oidcng/pull/11


Compile and watch (typst 0.1 new feature)

It would be nice if the plugin can support the new feature typst 0.1 has added, adding a command similar to the :VimtexCompile command (which compiles, and opens the pdf file with a pdf viewer, changes made to the source file can be seen in the pdf viewer immediately) from https://github.com/lervag/vimtex would help a lot.

Do you think that the typst-watch branch cover your needs? If so, I'll merge it. Otherwise, what are you missing?
Saying this more for me buuut... This period is a bit hectic for me however I also want to add nice features like this + more in e.g. vimtex. So I'll do it one quick hack at a time and clean up in the future.

Do you think that the update from #12 satisfies your needs? If not, what are you missing?
Saying this more for me buuut... This period is a bit hectic for me however I also want to add nice features like this + more in e.g. vimtex. So I'll do it one quick hack at a time and clean up in the future.

Yep, it's what I need. Thank you!


Add summary stats script

I have not yet run or tested --generate-gene-lof-matrix or --summarize-gene-lof-matrix since it requires a densify

Should we get this PR in too? I can help review if needed. Want to wrap up all the stats tickets.

Hmm so this code was instead ran in a notebook and essentially this runs get_summary_stats() to get per-callset stats (not per sample) of just about exactly what we're doing.
Following this goal, I think we should maybe calculate the TOTALS of everything we're calculating per sample as sums instead from the intermediate file ? I can add the code for it - if we want per-callset instead of per-sample - stats

Should we get this PR in too? I can help review if needed. Want to wrap up all the stats tickets.

so I took a run at this in #611 - just getting those stats from the existing aggregated table, while they're already there. LMK your thoughts.

After another look, this actually looks like it's doing something a bit more complex and productionized and better versionized than the simple code I put into #611 . Running the existing summary stats method =/= calculating things from the intermediate per-sample table , though we can return 99% of the same results from it. @jkgoodrich is this worth pursuing, or is calculating plenty of per-callset stats via #611 good enough ?


Cannot set property 'openerId' of undefined

I cannot test this project with my personal clientId and domain.
After execute npm install and npm start I click on login with Facebook or Google or any else and I receive a popup with this error Cannot set property 'openerId' of undefined
Full stacktrace :
Uncaught Exception:
TypeError: Cannot set property 'openerId' of undefined
    at mergeBrowserWindowOptions (/Users/MaximeFr/Desktop/auth0-electron-samples-sample/node_modules/electron-prebuilt/dist/Electron.app/Contents/Resources/electron.asar/browser/guest-window-manager.js:44:35)
    at EventEmitter.<anonymous> (/Users/MaximeFr/Desktop/auth0-electron-samples-sample/node_modules/electron-prebuilt/dist/Electron.app/Contents/Resources/electron.asar/browser/guest-window-manager.js:144:13)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (/Users/MaximeFr/Desktop/auth0-electron-samples-sample/node_modules/electron-prebuilt/dist/Electron.app/Contents/Resources/electron.asar/browser/api/web-contents.js:219:13)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)

Any update ?

This looks to be an issue with Electron handling opening a new browser window
https://github.com/electron/electron/issues/7519

I test with Electron 1.4.3 and I have same exception.

Thank you your solution work fine.


chore(main): release 0.2.18

:robot: I have created a release beep boop
0.2.18 (2024-11-10)
Bug Fixes

调试使用Github的环境变量26 (b9f710f)
调试使用Github的环境变量27 (b7f791b)
调试使用Github的环境变量28 (af50459)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.2.18
:sunflower:


run works, but packageDeb fails with exit value 1

Steps to reproduce

Create a new compose project with version number prefixed v. (eg: v1.0.0-alpha01)
execute packageDeb using the Gradle menu

Expected Behaviour

Task finishes and deb file generated

Actual Behaviour

Task failed with below stacktrace

7:08:02 PM: Executing task 'packageDeb'...

> Task :wrapper

BUILD SUCCESSFUL in 177ms
1 actionable task: 1 executed
> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :processResources NO-SOURCE
> Task :classes UP-TO-DATE
> Task :inspectClassesForKotlinIC
> Task :jar UP-TO-DATE

> Task :packageDeb
WARNING: Using incubator modules: jdk.incubator.jpackage
java.io.IOException: Command [fakeroot, dpkg-deb, -b, /tmp/jdk.incubator.jpackage10914860152014517490/images, /home/theapache64/IdeaProjects/which-stack/build/compose/binaries/main/deb/which-stack_v1.0.0-alpha01-1_amd64.deb] exited with 2 code

> Task :packageDeb FAILED
4 actionable tasks: 3 executed, 1 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':packageDeb'.
> Process 'command '/home/theapache64/.jdks/openjdk-15.0.1/bin/jpackage'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 7s
7:08:09 PM: Task execution finished 'packageDeb'.

IntelliJ version
Build #IC-203.6682.168, built on December 29, 2020
Runtime version: <IP_ADDRESS>+11-b1145.63 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 4.15.0-133-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1934M
Cores: 6

Current Desktop: Unity

Note

run works

Started to work when I removed v prefix from the version number.
@olonho Is this expected?
Source: #205

Similar problem used to exist on Windows, IIRC, and was fixed by checking regex on version. Maybe we need smth similar?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Feature: Automatically pull terms from description and background

There should be a NER or term recognition tool that automatically extracts relevant terms from the description and the background section, so you don't need to rely on things like tags in the package.json.

Is this something SR should do? How do you envision this?

No, this is not something standard-readme should do. This is somthing another tool should do.


Depending on Mix/Bag/etc. order is a trap, let's document it as such

We should have a separate item in traps that will explain why depending on order of unordered collections is a bad idea. Also see https://github.com/perl6/doc/issues/1105 and https://github.com/perl6/doc/issues/1106.

The traps entry would be a great place to make a parallel to the SQL SELECT-without-ORDER problem.
18:55 < mst> note that lots and lots of people (including past-mst) run
             face-first into the fact that lots of SQL database implementations
18:55 < mst> return things in PK order -most- of the time because that's more
             convenient to the implementation
18:55 < mst> thereby leading to people not realising that the order is
             'whatever the db feels like' unless you provide ORDER BY


Release 2.0.3 with name change warning

Is your feature request related to a problem? Please describe.
With the release of 3.0.0 under a different name (cloudevents instead of cloudevents-sdk), existing users of the 2.x versions will never receive an update or patch unless they know that the module name has changed, and make proactive steps to modify their dependencies.
In order to help smooth the transition for existing users, we should release a 2.0.3 patch version that emits a warning on install that there is a 3.0.x version out now with the new name. This won't guarantee that users see it, especially in automated systems, but it should help.
Describe the solution you would like to see
Issue a 2.0.3 release under the cloudevents-sdk name that includes a warning emitted during install that the name has changed to cloudevents and there is a new major version available.

+1

Fixed in https://github.com/cloudevents/sdk-javascript/commit/9a91d87442611d52898e39df6fe85d4160362e0f


9P filesystems are not working

I have a problem on peertube that the lifestream is not starting.
The Problem itself is very similar to this one https://github.com/Chocobozzz/PeerTube/issues/4308 .
Except that I did not run peertube on WSL but in a container on a KVM/libvirt VM for storage reasons my peertube instance is hosted on a big 9p pass through filesystem, mounted like this:
stream /var/lib/containers/storage/volumes 9p trans=virtio,version=9p2000.L,rw 0 0
It looks as if chokidar does not work on 9p filesystems.
As soon as I configure the affected path over on an ext4 filesystem streaming does work.
As https://github.com/Chocobozzz/PeerTube/issues/4308 states that chokidar is looking for some files and playlists, I guess the root cause of the problem is a lack of support for 9p filesystems.

I just stumbled across this and even though it is a bit older, a short answer: the problem with 9p is that inotify is not supported. The solution is to use polling; just set the environment var CHOKIDAR_USEPOLLING=true for that.
For peertube (docker-compose) this can be done in the .env file which is used by docker compose and then it works fine.
https://github.com/libfuse/libfuse/wiki/Fsnotify-and-FUSE

"just disable the non-working feature" is a workaround, but not a solution.
Thanks for a workaround so far, but would be really great if the community could find an actual solution to this issue.
Not everyone has spare CPU time to waste on polling.


Files crash after <IP_ADDRESS> update

Description
After 5 to 10 mins of Files running and unused, the applications crashs with no error code.
Steps To Reproduce

Open Files.
Let it run.

Expected behavior
Not crashing since I'm not using it.
Files Version
<IP_ADDRESS>
Windows Version
Windows 11 Professionnel 21H2 22000.434
Relevant Assets/Logs
debug.log

@inarrr are you using a custom theme?

@inarrr does resetting the app fix the issue?

@yaichenbaum I'm not using any theme.
How can I reset the app ?
Thank you.

App crashes for me aswell, but only after renaming files.
Resetting doesn't work.

If any more information is required just let me know.

@inarrr you can reset the app from the app page in the Windows Settings app.

@inarrr you can reset the app from the app page in the Windows Settings app.

Resetting doesn't work at all, even crashes in a clean reinstall of windows in a VM

@DutchEclipse is there a specific action that causes the app to crash?

@DutchEclipse is there a specific action that causes the app to crash?

Alwaya happens when renaming a file in tiles modez in other layouts it works fine.
But this has been known already right?

We had a potential fix but it doesn't seem to have worked.

Merging with #7996


SQL Saturday Columbus 2023 - Site Adds

Please add the link to the schedule
https://sessionize.com/api/v2/piprkmwb/view/GridSmart
Please add the precon links
Understanding and Optimizing SQL Server Performance - Joey D'Antoni
https://www.eventbrite.com/e/657500942017
An Introduction to Python for Data Science and Data Engineering - Chris Hyde
https://www.eventbrite.com/e/657503609997

done
From: pshore73 @.>
Sent: Saturday, June 17, 2023 2:59 AM
To: sqlsaturday/sqlsatwebsite @.>
Cc: Subscribed @.***>
Subject: [sqlsaturday/sqlsatwebsite] SQL Saturday Columbus 2023 - Site Adds (Issue #201)
Please add the link to the schedule
https://sessionize.com/api/v2/piprkmwb/view/GridSmart
Please add the precon links
Understanding and Optimizing SQL Server Performance - Joey D'Antoni
https://www.eventbrite.com/e/657500942017
An Introduction to Python for Data Science and Data Engineering - Chris Hyde
https://www.eventbrite.com/e/657503609997
—
Reply to this email directly, view it on GitHubhttps://github.com/sqlsaturday/sqlsatwebsite/issues/201, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6AGDD3EJNGAI37HB4M7EDXLUFOTANCNFSM6AAAAAAZJ5EUZQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
Redgate respects your privacy. To find out how we handle your personal data, see our privacy noticehttps://www.red-gate.com/privacy. Use of our software is subject to our license agreementhttps://www.red-gate.com/eula.
Our head office is Cavendish House, Cambridge Business Park, Cambridge, CB4 0XB, United Kingdom, and we are registered in the UK as company #3857576.


example quick start

Hi,
I installed a fresh new Ubuntu 14.04 and followed the full steps (build from source).
Running the example given in the repo.
First start:
create OK, start OK, translate hanging with java process < 3% during for ever. I stopped it
I rebooted
Second start:
start OK, translate OK "hello world" => "hello mondo"
add (ciao) OK but taking quite long (>20 seconds)
translate: no change "hello mondo" not ciao
I have 30GB of ram and 16 cores on my VM (xeon 2550 2.9Ghz) so should be quite fast
but the java process during "add" above is taking less than a few percents.
thanks for your insight.

correction:
After another dist-upgrade and reboot, it works as expected and quite fast.

Hi vince62s,
Do you have version compiled from the source or binary distribution? I'm asking about it because I have the same problem - wrong incremental translation and slow adding translations. I have newest binary installation so I don't know what to do to upgrade my system. Would you say more how did you fix this problem?
Regards,
Thomas

did you reboot then update / dist-upgrade, reboot again ?
I compiled from source, but the behavior was actually strange.
after the 2 reboots it worked fine.

@davidecaroselli I also had the problem and it looks similar to the problem we had at the AMTA tutorial.
Adding priority for the 0.14

Hi guys!
I suspect we have a race condition at the MMT launch, and not all its components are starting correctly. Could you please attach the log file mmt/runtime/default/logs/embedded-kafka.log ?
Thanks!

here you go.

Hi @vince62s , no file attached

ok, so this log suggests that everything is working as expected. Is this the log from the MMT run that presented the slow(no)-update problem?

of course, sorry for this.
It did not work tuesday night, but then after a reboot I "recreated" the default model yesterday morning.
So yes this is the log of the last build that worked. It overrid the previous one.

Davide, I am rebuilding a new VM from scratch and will give you the detailed log.

Thanks vince62!
Actually the bug should be observed in the mmt start part; so you can reuse the same models, they're just perfect as they are!
so if you execute something like:
./mmt start
./mmt add ibm "example" "esempio"

and the last command takes too much time (normally takes less than a second), you've hit the bug! In this case, if you could provide the content of the file mmt/runtime/default/logs/embedded-kafka.log and the output of the command jps, it would be great!
Thank you!

no it's fast now.

Update on this issue:
The problem was caused by Kafka not starting correctly, and MMT not alerting the problem: the engine kept waiting the update to be published on Kafka that was not running.
We solved both issues and the fix is available starting from commit 67e6a4b63deb5df47672660b095240dc0ce8d426


update query prop if a new one is passed in

Addresses #30
Update the root state when a new query prop is passed in.
From the user perspective, this allows the user to utilize this query prop, and the onQueryChange callback function to essentially move the state of the query out of this component.
Just for insight into my usage: My personal use case of this is with redux in which i save multiple query types.  With the query prop, I am able to select a new query from the drop-down, and which eventually gets set as a prop of this query.  From there the user can edit the populated query fields in-place.
I use the on query change to get the query itself and that hooks up into state, and eventually redux.
I also built the dist files using the command  npm run dist.

Codecov Report

Merging #31 into master will decrease coverage by 1.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master      #31     +/-   ##
=========================================
- Coverage   70.86%   69.76%   -1.1%
=========================================
  Files           6        6
  Lines         127      129      +2
  Branches       17       18      +1
=========================================
  Hits           90       90
- Misses         34       36      +2
  Partials        3        3

Impacted Files
Coverage Δ

lib/QueryBuilder.jsx
45.07% <0%> (-1.31%)
:arrow_down:

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 be9e1bd...f66c6a3. Read the comment docs.

@BradfordMedeiros this looks good. I only need a test that will ensure this use case is covered. I can then merge it in.

@BradfordMedeiros @pavanpodila Needs this PR merged with the same use case you are describing. Is there any blocker? Can I help?

@BradfordMedeiros  @pavanpodila
Currently test cases are failing and also have some conflicts.
Need this PR to complete to implement one functionality can we merge this as soon as possible?

Hi @@BradfordMedeiros
Can you please resolve merge conflicts as it is crucial bug and get it merge as soon as possible.

This was addressed in #67 - closing this PR. If there's more work that should be merged from here, please re-open it.


Footprint-based cell-swapping in forest branch sometimes returns erroneous results

The forest branch contains a method of swapping out cells for more optimal ones.
For example, swapping out black cells (2 outputs) for grey cells (1 output) when the additional output is not required.
This method seems to occasionally swap in invalid cells, as evidenced by this block of code labeled "TEMPORARY 4 AM CODE".
A comprehensive fix is necessary.

Closed by #64


Publish 8/24/2020 10:30 AM PT

Docs Build status updates of commit 951433e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/netsecurity/Get-NetFirewallPortFilter.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


folding in linear view

The new linear view design was made to support folding, need to finish implementing that which helps with files with long runs of embedded data or otherwise with organizing the view.

duplicate of #510


Not work in Mobile Chrome 54.0

The plugin not work on my mobile Chrome 54.0,
but if I comment this code
http://clip2net.com/s/3NJZi2r
it works amesome.

If you need to support older versions of Chrome, I recommend to use version 8.2.0 of LazyLoad which doesn't use the Intersection Observer API, which is quite new.
You can read more about it in the readme file.
PS: Removing that line of code would make the images load all at once, so it's like not having any lazy load at all.

The plugin not work on my mobile Chrome 54.0,
but if I comment this code
http://clip2net.com/s/3NJZi2r
it works amesome.

URL is missing


ConnectionAcquiringListener: listener for connection lifecycle

Hi, as you suggested to add some additinal callbacks to datasource-proxy I would like to introduce listener to the Connection operations.
ConnectionAcquiringListener reacts on next events:

beforeAcquireConnection - before DataSource#getConnection
afterAcquireConnection - after DataSource#getConnection, including acquire time and exception if thown while getting connection.
afterCommitConnection - after Connection#commit, including commit time and exception if thown while committing.
afterRollbackConnection - after Connection#rollback, including rollback time and exception if thown while rolling back.
afterCloseConnection - after Connection#close, including close time and exception if thown while closing.

I didn't include before* for commit/rollback/close as they seem useless, although time for waiting on DataSource#getConnection may be significant if connection pool has no free connections and wait time is limited to a huge number. If you think otherwise it is not a big deal to add them.
Expecting change requests from you I didn't add a documentation/license/since tag, I will do it once you approve the api.

Hi @gavlyukovskiy
Thanks for the PR.
I have a different approach to captures all method invocations on JDBC API.
That'll also include connection lifecycle.
I'm working on preliminary implementation and will share it soon.

this is the branch I'm working on to intercept method calls on JDBC APIs.
https://github.com/ttddyy/datasource-proxy/tree/method-execution-listener

hm, ok.
I prefer having central callback than having individual callback per usecase.
Anyway, I have merged my interceptor branch and released 1.4.3.
So, please try it out, and any feedback is welcomed.
Thanks,


Modified the internal implementation of ModInt

ModArithmetic: interface -> abstract class
ModArithmetic#pow, ModArithmetic#inv:  abstract -> default method

verified :

M-SOLUTIONS 2019 C - Best-of-(2n-1) (M =<PHONE_NUMBER>)
ABC172 E - NEQ (M =<PHONE_NUMBER>)
ABC129 F - Takahashi's Basics in Education and Learning (2 <= M <=<PHONE_NUMBER>)
ARC050 C - LCM 111 (2 <= M <=<PHONE_NUMBER>)
ARC012 D - Don't worry. Be Together (1 <= M <=<PHONE_NUMBER>)


Create article action with tests

Coverage increased (+1.9%) to 85.156% when pulling 3fe2f25a4463977a8f555f00a0451e76c80a2105 on djavolak:test into ff7c855ddf7f919e9fca33eef4f40cf7728606f7 on tasmaniski:master.

Coverage increased (+1.9%) to 85.156% when pulling f80676d8ddb4f28001f05a524c3bbf341747a77c on djavolak:test into ff7c855ddf7f919e9fca33eef4f40cf7728606f7 on tasmaniski:master.


[ocean-dao-brightid] Update ocean-dao-brightid strategy

Changes proposed in this pull request:

Getting the BrightId registry network & block and the snapshot network & block from options object.

@trizin The strategy fail with 500 test addresses due to node limitation, I think this come from the ERC20 on Polygon, can you try without? Here is the error I see:
missing revert data in call exception (error={"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"id\":51,\"error\":{\"code\":-32000,\"message\":\"execution aborted (timeout = 5s)\"}}\n","error":{"code":-32000},"requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0xeefba1e63905ef1d7acba5a8513c70307c1ce441\",\"data\":\"0

@bonustrack thanks, that worked!


VB.Net Print Pdf with filled in text

I have some pdfs i need to print, when i use pdfium to print or even open in pdfiumviewer the text fields come out blank, is there any way to have the typed text print.I have attached a test pdf file.
Any help will be appreciated.
Regards
TEST.pdf

Hi any help will be appreciated

see #175 , you can try print it as image, works for me


signup page and login page creation

There is no signup page and login page

I would be happy to take on this issue. Could you please assign it to me?

@Subhams-GIT if I may, can I work on Login Page only ?

@Subhams-GIT if I may, can I work on Login Page only ?
let the owner decide if he can assign issues to both of us

@Subhams-GIT if I may, can I work on Login Page only ?
let the owner decide if he can assign issues to both of us

Yes, I do not mind at all. It is also better if work is divided among us.

@Subhams-GIT @Anirban780 I have assigned this issue over to both of you.

If this is not yet implemented or stale, can I be assigned this issue?
@braydenidzenga


[Feature]: ignore missing extension google_vacuum_mgmt

Is there an existing issue already for this feature request/idea?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?
any loading from google Cloud SQL you have a missing extension google_vacuum_mgmt need to skip it as is not configurable.
I am not 100% this is the cause so if this is not the issue and something else not in the logs can be done I will look more. Not sure if bug or feature depending on how you look at it.
Describe the solution you'd like
ability to ignore the issue on the pg_restore or some control of not failing in the pre-data
google_vacuum_mgmt
Describe alternatives you've considered

removing the extension from the gcp panel
dumping to a staging system that could accept the ext drop

Additional context
{"level":"info","ts":"2024-06-16T21:37:04Z","msg":"Running pg_restore","logging_pod":"db-1-import","cmd":"pg_restore","options":["-U","postgres","--no-owner","--no-privileges","--role=app","-d","app","--section","pre-data","/var/lib/postgresql/data/pgdata/dumps/odoo.dump"]}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"postgres","msg":"record","logging_pod":"db-1-import","record":{"log_time":"2024-06-16 21:37:04.351 UTC","user_name":"postgres","database_name":"app","process_id":"47","connection_from":"[local]","session_id":"666f5b00.2f","session_line_num":"1","command_tag":"CREATE EXTENSION","session_start_time":"2024-06-16 21:37:04 UTC","virtual_transaction_id":"3/37","transaction_id":"0","error_severity":"ERROR","sql_state_code":"0A000","message":"extension "google_vacuum_mgmt" is not available","detail":"Could not open extension control file "/usr/share/postgresql/15/extension/google_vacuum_mgmt.control": No such file or directory.","hint":"The extension must first be installed on the system where PostgreSQL is running.","query":"CREATE EXTENSION IF NOT EXISTS google_vacuum_mgmt WITH SCHEMA google_vacuum_mgmt;\n\n\n","application_name":"pg_restore","backend_type":"client backend","query_id":"-4877003220278606660"}}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"pg_restore: error: could not execute query: ERROR:  extension "google_vacuum_mgmt" is not available","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"DETAIL:  Could not open extension control file "/usr/share/postgresql/15/extension/google_vacuum_mgmt.control": No such file or directory.","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"HINT:  The extension must first be installed on the system where PostgreSQL is running.","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"Command was: CREATE EXTENSION IF NOT EXISTS google_vacuum_mgmt WITH SCHEMA google_vacuum_mgmt;","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"pg_restore: error: could not execute query: ERROR:  extension "google_vacuum_mgmt" does not exist","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"Command was: COMMENT ON EXTENSION google_vacuum_mgmt IS 'extension for assistive operational tooling';","pipe":"stderr","logging_pod":"db-1-import"}
{"level":"info","ts":"2024-06-16T21:37:04Z","logger":"pg_restore","msg":"pg_restore: warning: errors ignored on restore: 2","pipe":"stderr","logging_pod":"db-1-import"}
Backport?
N/A
Are you willing to actively contribute to this feature?
No
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello @dnplkndll
This i something that the operator can't fix since it's PostgreSQL the one that is getting a dump with an extension that doesn't exists, here there's some options:

Provide the PostgreSQL image with the extension
Take the backup with that extension disabled
Modify the SQL file (if is an SQL file) and remove the creation of that extension manually

Sadly, is out of the operator capabilities to modify or pre-process a dump that it's being dumped into PostgreSQL
Closing since this can't be done
Cheers!

unfortunate as removal of google_vacuum_mgmt is not possible or install on the an image.
so no path forward to accept a database from Google Cloud SQL
use case would be to clone prod db into a review env with operator managed DB
documenting for reference:
https://www.googlecloudcommunity.com/gc/Databases/Unable-to-migrate-from-CloudSQL-Postgres-to-AlloyDB-due-to-the/m-p/762672


etcd-cpp-apiv3 building debian package from source

I am trying to build debian package from source with newer protobuf version:
I tried the following commands in ubuntu:
mkdir build
cd build
cmake ..
cpack
that seems to create the file  etcd-cpp-api-0.2.2-Linux.tar.gz

From Alex Hurd

thanks for posting

I would like to know what your problem exactly is. Are you facing with some build errors? Or, are you not sure how to build such a deb package?

I am not sure how to build debian package with cmake/cpack

I am not sure how to build debian package with cmake/cpack

You could simply
mkdir build
cd build
cmake ..
cpack -G DEB

which will generate the deb package that you want.
I have add a github action to verfify that: https://github.com/etcd-cpp-apiv3/etcd-cpp-apiv3/blob/master/.github/workflows/build-deb-package.yml


fix: eslint/prettier

(cherry picked from commit 8f52860c8761e28db259965acedea0bfc1f32b4f)

Q
A

Branch?
main for features / current stable version branch for bug fixes

Tickets
#...

License
MIT

Doc PR
api-platform/docs#...

This PR is not needed: ESLint is only executed in src and Prettier is executed on the generated files.


Viewer

Discussed in https://github.com/orgs/kolumnin-com/discussions/3

Originally posted by kolumnin November  5, 2022
I am yet the only viewer of this text here, other than the GitHub.
2022-11-05-06:06@kolumnin

2022-11-16


cannot doctest a classdef's disp method

See our @test_classdef example in test.
Its possible this will start working if we use the dot mechanism help test_classdef.disp, which works in (I think) Octave >= 7.

depends on #203

And likely #264.

After #265 (fixing #203) you can doctest test_classdef.disp explicitly.


Tidy schema linting

Description
Just a small tidy following @maxschulz-COL's work in #119.

hatch run schema will now include linting so no need to run hatch run lint manually after that.
hatch run lint with no other arguments still lints all files (not just staged files)
you can change this by overriding arguments e.g. hatch run lint --file=... to just lint some files

Checklist

[x] I have not referenced individuals, products or companies in any commits, directly or indirectly
[x] I have not added data or restricted code in any commits, directly or indirectly
[ ] I have updated the docstring of any public function/class/model changed
[ ] I have added tests to cover my changes (if applicable)

Types of changes

[x] Docs/refactoring (non-breaking change which improves codebase)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

In general, looks good to me 👍
Have we been testing this out? I remember Max previously merging 2-3 PRs on fixing the linting behaviour during the release process, because somehow it didn't behave the way we wanted it to 😄 I remember that double linting call was somehow required? @maxschulz-COL

In principle with this change the linting should not be required at all, so also no double linting should be required. Given that we can always lint manually I would just test this out, and adjust in case this fails for some reason..


serving static files like css from public directory

I believe to get express to serve up the static files from the public directory you would have to have a line in index.js that says app.use(express.static('public'));

Hey @drewlearns , can you please assign this to me?

Hey @drewlearns , can you please assign this to me?


Dependencies not getting installed

I am creating a plugin that is being used by a component. The plugin has a typings dependency on redux. I have typings install -S reduxed in my plugin module properly, and all is good there. Here is the typings.json I am using (removed ambientDependencies for brevity):
{
  "name": "hub.plugin.redux",
  "main": "dist/index.d.ts",
  "dependencies": {
    "redux": "registry:npm/redux#3.0.6+20160214194820"
  }
}

This plugin package contains a typings.json, js, and typings for the js (both of which are created by typescript using outDir in the dist folder).
Once I install this in my component via JSPM, I install the typings for this plugin using file:. The typings.json for that is as follows:
{
  "name": "hub.component.navigation",
  "dependencies": {
    "hub.plugin.redux"<EMAIL_ADDRESS>  }
}

typings install gives me the following:
$ typings install

├─┬ hub.plugin.redux
  └── redux

However, I noticed in the typings folders, there is no redux typings at all. Am I missing something? Am I correct in assuming that dependencies in typings work like npm and jspm dependencies, in that the typings for redux would get installed in my component? I am not able to get any references to redux and importing does nothing. However, I am able to do import {IAction} from '~hub.plugin.redux~redux' and use that, but that would seem silly to have to import that way.
If it helps, the generated index.d.ts can be found here: https://gist.github.com/MrHayato/53ef41356bd2c2fc3423

Running into the same thing - I figure I'm missing something here, and the "workaround" was to install the dependencies manually. Certainly not a long-term solution.

That's not how dependencies work. Closing as it's invalid. Dependencies should never be exposed transitively, that's how you cause conflicts.

work like npm and jspm dependencies

For one, neither of these work that way either. They just happen to print de-duplicated trees. If you're relying on that behaviour, you've already broken your users.

@MrHayato , sorry, I think that is correct. You won't able to use moduleB if you install moduleA that depends on moduleB.
e.g. tslint depends on diff. By npm install tslint, you can only import 'tslint``, but you can't import 'diff'`.

That's too bad... Because our architecture is set up in such a way that the project is going to be large and very modularized so it would be a huge pain for every dev to always install one dependency and manually install every typing for it. I'll just manually install it on our end through our tooling instead.
Thanks

That's not how dependencies work, I don't understand what you're missing here. I'll tell you now, but that is not modular - that's the opposite and it will break for you. But you're welcome to ignore me as you already plan to.

always install one dependency and manually install every typing for it

What are you talking about? It literally installed all the dependencies recursively for you already? It worked as intended and you don't need to install anything else.
I'll try to state out what you're saying you're doing and you're free to take it or leave it. You're relying on the dependency of a dependency becoming the dependency of your project. This is definitely going to break on you, and will break any user using NPM v2 or alternative NPM clients. You're building against a quirk here. On top of that, your whole project will break when:

A dependency removes one of their dependencies you relied on - your project breaks.
A dependency updates one of their dependencies to something incompatible with your project.

Basically, your projects are in a very fragile state and there will always be a situation where the project is broken because when 1 or 2 occurs you need to update everything - the exact opposite of how you should be developing.

...install one dependency and manually install every typing for it

When the vscode extension is ready, hopefully that could help you on this.
What you are looking for is not really typings install <x>, it is really about typings sync or typings auto-install.

@blakeembrey Thanks for elaborating. Let me share my initial experience and maybe you can shed some light on what's expected.
Brand new project, npm install gulp, npm install typings -g, typings install gulp --ambient --save
Gulp typings appear to be installed correctly. Compile some typescript that imports gulp, compiler throws some errors: orchestrator module not found, Q module not found.
So, in this case, "orchestrator" and "Q" are registered dependencies of gulp the npm package, and the type definitions for gulp reference those modules directly.
The only way I see to resolve these compiler errors is to install "orchestrator" and "Q" type definitions. Is that the wrong approach, and if so what's the right approach?

Not --ambient. Just typings install gulp --save
When installing with --ambient, no dependencies will be installed.

Brilliant, thank you.

--ambient is for global stuff such as mode or scripts loaded from script tags. You won't import them.

Mode -> node

@lukeautry Apologies for that, the issue you are facing is not the same as @MrHayato's request. The issue you have is legitimate, and is an unfortunate side-effect of zero versioning in DefinitelyTyped. This may improve on DefinitelyTyped's side with upcoming changes in TypeScript, but for now there's nothing we can do from Typings. There's a few existing issues mentioning this too, the best way is to use proper dependencies from the Typings registry when you can.


Fixed conditional comments in some rare cases

Fix of wrong conditional comment attach to the ProgramNode

Coverage increased (+0.003%) to 98.141% when pulling 6d3c2ae467dca50df6849857a770b6f7c4e38abf on conditional-comments-fix into 023c5b54a7b51511f5e8daae5fd8d0b6f1008cce on master.

Coverage increased (+0.003%) to 98.141% when pulling 6d3c2ae467dca50df6849857a770b6f7c4e38abf on conditional-comments-fix into 023c5b54a7b51511f5e8daae5fd8d0b6f1008cce on master.


Update corefxlab to VS2017.

Upgrade xproj/project.json to csproj.
Upgrade CLI version to one that supports dotnet msbuild.
Make minor changes to build scripts to support dotnet msbuild.
Upgrade dotnet-install to latest version.
This builds and debugs in VS2017.
This builds from the command line with the upgraded CLI.
Tests work and pass, with the exception of:

Tests that reference xunit.performance.core can not be discovered and will not be run in either VS or the command line.
Tests that use resx files fail with a MissingManifestResourceException in VS and will not be discovered on the command line.

This does not include buildtools changes.

Hi @crummel, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

These project files need some love. Did you very the automatic migration produces identical assets as the project.json.

@davidfowl I spot-checked the properties and those all seemed fine.  For functional stuff, the project.json build appears to have included transitive references implicitly, which was not the case after conversion, so those all had to be added, as well as some framework references which I would have thought would also be needed in the project.jsons.  Upgrading to NETCore.Library 1.1.0 also caused a lot of version conflicts on existing references, so I updated those (mostly to 4.3.0 or latest across the board, except for System.Reflection.Metadata.Cil, which depends on an old version of System.Reflection.Metadata).  The auto-migration also had some issues with the projects that don't include all the .cs files in their directory, so I manually fixed those.  So I don't think they're identical, but given that we're upgrading I think I got as close as possible.  I logged https://github.com/dotnet/corefxlab/issues/1155 to fix the remaining test issues.


Funding didn't show up in the app

Funding locally did not work (ie. it did not show up in balance or history), however the backend reckons that the payment was claimed:
grep for the amount ("99999") below to see:
setup was freshly wiped. after this fails, I cannot create another invoice and am stuck.

2023-07-10T05:35:20.577786Z  INFO ln_dlc_node::ln::event_handler: Received event event=PaymentClaimable { receiver_node_id: Some(PublicKey(8021c9d587ae144d435635f6943f255c1f133de19e002500bdebbd4c918a41b70e3169e2a128650233c93170f5b83f2cc31ac78e9e5a1984552e4878ff30cce4)), payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]), amount_msat: 99999000, purpose: InvoicePayment { payment_preimage: Some(PaymentPreimage([46, 61, 241, 233, 179, 40, 235, 73, 160, 118, 53, 76, 238, 90, 99, 179, 166, 148, 127, 16, 120, 160, 33, 36, 201, 75, 198, 236, 208, 138, 114, 215])), payment_secret: PaymentSecret([94, 188, 5, 44, 19, 139, 188, 181, 200, 117, 199, 50, 187, 14, 222, 152, 137, 180, 152, 153, 99, 124, 61, 118, 67, 214, 26, 242, 179, 146, 31, 95]) }, via_channel_id: Some([134, 237, 198, 68, 247, 173, 39, 212, 244, 119, 74, 171, 183, 216, 66, 79, 216, 226, 99, 102, 156, 146, 234, 106, 2, 24, 167, 251, 202, 115, 244, 175]), via_user_channel_id: Some(0) }
2023-07-10T05:35:20.57801Z  INFO ln_dlc_node::ln::event_handler: Received payment payment_hash=0x890xde0xaf0xaa0xa20x4a0xe90x080xfc0x0f0xd20xa70xb80x8b0x820x290x410x920x760x800xab0x0a0x9a0x760x920x8e0xd30x500x970x4c0x130x35 amount_msat=99999000
2023-07-10T05:35:20.578424Z TRACE log: Upgrading HTLC 89deafaaa24ae908fc0fd2a7b88b822941927680ab0a9a76928ed350974c1335 to LocalRemoved with a Fulfill in channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af! log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1956
2023-07-10T05:35:20.57856Z TRACE log: Updating HTLC state for a newly-sent commitment_signed... log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=5828
2023-07-10T05:35:20.579416Z TRACE log: Building commitment transaction number<PHONE_NUMBER>10653 (really 2 xor<PHONE_NUMBER>34881) for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af for remote, generated by us with fee 253... log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1509
2023-07-10T05:35:20.579484Z TRACE log:    ...not including inbound HTLC 0 (hash 89deafaaa24ae908fc0fd2a7b88b822941927680ab0a9a76928ed350974c1335) with value 99999000 due to state (LocalRemoved) log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1573
2023-07-10T05:35:20.57955Z TRACE log:    ...including to_remote output with value 99816 log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1669
2023-07-10T05:35:20.579603Z TRACE log:    ...including to_local output with value 99999 log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1675
2023-07-10T05:35:20.580019Z TRACE log: Tracking monitor update completion action for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af: PaymentClaimed { payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]) } log.target="lightning::ln::channelmanager" log.module_path="lightning::ln::channelmanager" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channelmanager.rs" log.line=4212
2023-07-10T05:35:20.580304Z TRACE log: Updating ChannelMonitor for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af log.target="lightning::chain::chainmonitor" log.module_path="lightning::chain::chainmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/chainmonitor.rs" log.line=691
2023-07-10T05:35:20.580395Z  INFO log: Applying update to monitor 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af, bringing update_id from 2 to 3 with 2 changes. log.target="lightning::chain::channelmonitor" log.module_path="lightning::chain::channelmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/channelmonitor.rs" log.line=2298
2023-07-10T05:35:20.580467Z TRACE log: Updating ChannelMonitor with payment preimage log.target="lightning::chain::channelmonitor" log.module_path="lightning::chain::channelmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/channelmonitor.rs" log.line=2334
2023-07-10T05:35:20.580603Z TRACE log: Updating ChannelMonitor with latest counterparty commitment transaction info log.target="lightning::chain::channelmonitor" log.module_path="lightning::chain::channelmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/channelmonitor.rs" log.line=2330
2023-07-10T05:35:20.58073Z TRACE log: Tracking new counterparty commitment transaction with txid 11a54828a6d6bc344ec2c209038ec399a1898cd28c4ec0daf36403cf8f116ecc at commitment number<PHONE_NUMBER>10653 with 0 HTLC outputs log.target="lightning::chain::channelmonitor" log.module_path="lightning::chain::channelmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/channelmonitor.rs" log.line=2158
2023-07-10T05:35:20.63674Z DEBUG log: Persistence of ChannelMonitorUpdate for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af completed log.target="lightning::chain::chainmonitor" log.module_path="lightning::chain::chainmonitor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/chain/chainmonitor.rs" log.line=711
2023-07-10T05:35:20.636951Z TRACE log: Regenerated latest commitment update in channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af with 0 update_adds, 1 update_fulfills, 0 update_fails, and 0 update_fail_malformeds log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=3971
2023-07-10T05:35:20.638113Z TRACE log: Building commitment transaction number<PHONE_NUMBER>10653 (really 2 xor<PHONE_NUMBER>34881) for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af for remote, generated by us with fee 253... log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1509
2023-07-10T05:35:20.638217Z TRACE log:    ...not including inbound HTLC 0 (hash 89deafaaa24ae908fc0fd2a7b88b822941927680ab0a9a76928ed350974c1335) with value 99999000 due to state (LocalRemoved) log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1573
2023-07-10T05:35:20.6383Z TRACE log:    ...including to_remote output with value 99816 log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1669
2023-07-10T05:35:20.638359Z TRACE log:    ...including to_local output with value 99999 log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=1675
2023-07-10T05:35:20.639367Z TRACE log: Signed remote commitment tx<PHONE_NUMBER>86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af00000000002375778002e8850100000000002200204c8289925568637402c8571dc59069ee87f0604171a2af82ab4e251e57c9b18d9f86010000000000160014702ac9679c3e578dff670aaaf5a600440892a6dc63050d20 (txid 11a54828a6d6bc344ec2c209038ec399a1898cd28c4ec0daf36403cf8f116ecc) with redeemscript 475221029a320f970bc138c54bae49fa70cae045a43df9a6b662fc5eba13f4864dc954d42102a1abf0eb35558bfb22f010dd58ae63eb466f327b840618b800db951d2ff0db4652ae with value 199998 -> 0bd7980bec13c21e29a8eab46474dd721fd7b41591b80f6577030a2380416b3b766dce606aceb6f7b48ba7dc26f53ee3cda3440ef1c726eadcfb523b6f39e640 in channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=5931
2023-07-10T05:35:20.639488Z DEBUG log: Restored monitor updating in channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af resulting in a commitment update and no RAA, with RAA first log.target="lightning::ln::channel" log.module_path="lightning::ln::channel" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channel.rs" log.line=3863
2023-07-10T05:35:20.63979Z TRACE log: Handling channel resumption for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af with no RAA, a commitment update, 0 pending forwards, not broadcasting funding, without channel ready, without announcement log.target="lightning::ln::channelmanager" log.module_path="lightning::ln::channelmanager" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/channelmanager.rs" log.line=4325
2023-07-10T05:35:20.64002Z DEBUG ln_dlc_node::ln::event_handler: Successfully handled event event="PaymentClaimable { receiver_node_id: Some(PublicKey(8021c9d587ae144d435635f6943f255c1f133de19e002500bdebbd4c918a41b70e3169e2a128650233c93170f5b83f2cc31ac78e9e5a1984552e4878ff30cce4)), payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]), amount_msat: 99999000, purpose: InvoicePayment { payment_preimage: Some(PaymentPreimage([46, 61, 241, 233, 179, 40, 235, 73, 160, 118, 53, 76, 238, 90, 99, 179, 166, 148, 127, 16, 120, 160, 33, 36, 201, 75, 198, 236, 208, 138, 114, 215])), payment_secret: PaymentSecret([94, 188, 5, 44, 19, 139, 188, 181, 200, 117, 199, 50, 187, 14, 222, 152, 137, 180, 152, 153, 99, 124, 61, 118, 67, 214, 26, 242, 179, 146, 31, 95]) }, via_channel_id: Some([134, 237, 198, 68, 247, 173, 39, 212, 244, 119, 74, 171, 183, 216, 66, 79, 216, 226, 99, 102, 156, 146, 234, 106, 2, 24, 167, 251, 202, 115, 244, 175]), via_user_channel_id: Some(0) }"
2023-07-10T05:35:20.640393Z  INFO ln_dlc_node::ln::event_handler: Received event event=PaymentClaimed { receiver_node_id: Some(PublicKey(8021c9d587ae144d435635f6943f255c1f133de19e002500bdebbd4c918a41b70e3169e2a128650233c93170f5b83f2cc31ac78e9e5a1984552e4878ff30cce4)), payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]), amount_msat: 99999000, purpose: InvoicePayment { payment_preimage: Some(PaymentPreimage([46, 61, 241, 233, 179, 40, 235, 73, 160, 118, 53, 76, 238, 90, 99, 179, 166, 148, 127, 16, 120, 160, 33, 36, 201, 75, 198, 236, 208, 138, 114, 215])), payment_secret: PaymentSecret([94, 188, 5, 44, 19, 139, 188, 181, 200, 117, 199, 50, 187, 14, 222, 152, 137, 180, 152, 153, 99, 124, 61, 118, 67, 214, 26, 242, 179, 146, 31, 95]) } }
2023-07-10T05:35:20.640567Z  INFO ln_dlc_node::ln::event_handler: Claimed payment amount_msat=99999000 payment_hash=89deafaaa24ae908fc0fd2a7b88b822941927680ab0a9a76928ed350974c1335
2023-07-10T05:35:20.640631Z  INFO native::db: Getting payment payment_hash=PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53])
2023-07-10T05:35:20.641499Z  INFO native::db: Inserting payment payment_hash=PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53])
2023-07-10T05:35:20.655818Z DEBUG ln_dlc_node::ln::event_handler: Successfully handled event event="PaymentClaimed { receiver_node_id: Some(PublicKey(8021c9d587ae144d435635f6943f255c1f133de19e002500bdebbd4c918a41b70e3169e2a128650233c93170f5b83f2cc31ac78e9e5a1984552e4878ff30cce4)), payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]), amount_msat: 99999000, purpose: InvoicePayment { payment_preimage: Some(PaymentPreimage([46, 61, 241, 233, 179, 40, 235, 73, 160, 118, 53, 76, 238, 90, 99, 179, 166, 148, 127, 16, 120, 160, 33, 36, 201, 75, 198, 236, 208, 138, 114, 215])), payment_secret: PaymentSecret([94, 188, 5, 44, 19, 139, 188, 181, 200, 117, 199, 50, 187, 14, 222, 152, 137, 180, 152, 153, 99, 124, 61, 118, 67, 214, 26, 242, 179, 146, 31, 95]) } }"
2023-07-10T05:35:20.656054Z DEBUG log: Handling UpdateHTLCs event in peer_handler for node 02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9 with 0 adds, 1 fulfills, 0 fails for channel 86edc644f7ad27d4f4774aabb7d8424fd8e263669c92ea6a0218a7fbca73f4af log.target="lightning::ln::peer_handler" log.module_path="lightning::ln::peer_handler" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning/src/ln/peer_handler.rs" log.line=1757
2023-07-10T05:35:20.656529Z TRACE log: Persisting ChannelManager... log.target="lightning_background_processor" log.module_path="lightning_background_processor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning-background-processor/src/lib.rs" log.line=472
2023-07-10T05:35:20.678695Z TRACE log: Done persisting ChannelManager. log.target="lightning_background_processor" log.module_path="lightning_background_processor" log.file="/Users/mariusz/.cargo/git/checkouts/rust-lightning-bee3233422fa4387/a663e1f/lightning-background-processor/src/lib.rs" log.line=472
2023-07-10T05:35:20.679138Z DEBUG native::event::event_hub: Publishing event PaymentClaimed(99999000)
2023-07-10T05:35:20.679307Z DEBUG native::channel_fee: Trying to pay channel opening fees of 153
2023-07-10T05:35:20.800741Z  INFO native::db: Got all payments payment_hashes=[PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53])]
2023-07-10T05:35:20.801186Z  INFO native::ln_dlc: Off-chain payment details details=PaymentDetails { payment_hash: PaymentHash([137, 222, 175, 170, 162, 74, 233, 8, 252, 15, 210, 167, 184, 139, 130, 41, 65, 146, 118, 128, 171, 10, 154, 118, 146, 142, 211, 80, 151, 76, 19, 53]), status: Succeeded, flow: Inbound, amount_msat: Some(99999000), timestamp: 2023-07-10 5:35:20.0 +00:00:00, description: "" }
flutter: | 2023-07-10 15:05:20.951 | LogLevel.INFO | Paying invoice succeeded: {"payment_error":"", "payment_preimage":"Lj3x6bMo60mgdjVM7lpjs6aUfxB4oCEkyUvG7NCKctc=", "payment_route":{"total_time_lock":218, "total_fees":"500", "total_amt":"100499", "hops":[{"chan_id":"134140418654208", "chan_capacity":"10000000", "amt_to_forward":"99999", "fee":"500", "expiry":176, "amt_to_forward_msat":"99999000", "fee_msat":"500995", "pub_key":"02dd6abec97f9a748bf76ad502b004ce05d1b2d1f43a9e76bd7d85e767ffb022c9", "tlv_payload":true, "mpp_record":null, "amp_record":null, "custom_records":{}, "metadata":""}, {"chan_id":"1099512479745", "chan_capacity":"99999", "amt_to_forward":"99999", "fee":"0", "expiry":176, "amt_to_forward_msat":"99999000", "fee_msat":"0", "pub_key":"02b7418a914cbdebbd0025009ee13d131f5c253f94f63556434d14ae87d5c92180", "tlv_payload":true, "mpp_record":{"payment_addr":"XrwFLBOLvLXIdccyuw7emIm0mJljfD12Q9Ya8rOSH18=", "total_amt_msat":"99999000"}, "amp_record":null, "custom_records":{}, "metadata":""}], "total_fees_msat":"500995", "total_amt_msat":"100499995"}, "payment_hash":"id6vqqJK6Qj8D9KnuIuCKUGSdoCrCpp2ko7TUJdMEzU="}

Is this reproducible not working or only once in a while?
Could you add the steps on how to reproduce this bug?

With funding you mean, that you did not receive the money into your channel?
Do you have more logs, i.e. around the creation of the funding transaction and whether broadcasting it worked?

Is this reproducible not working or only once in a while?
Could you add the steps on how to reproduce this bug?

I could not reproduce it when I tried today ;/
I simply started just all, tried to fund (with '99999') as the amount, and it never arrived on my node.
I've added a label "dev-environment" to show that this happened on regtest.

I believe we can close this and re-open with more info if it happens again.


Optional variable can't be used when i enables it as an experiments in terraform block

Error: Invalid type specification
│
│   on variables.tf line 45, in variable "pre_configured_rules":
│   45:     preview                 = optional(bool, false)
│
│ Optional attribute modifier expects only one argument: the attribute type.

Are you using terraform version 1.3+? You dont need to enable experiment for 1.3 as the feature is part of 1.3.

From the readme "If you find incompatibilities using Terraform >=0.13, please open an issue."
Terraform version
0.14.11
terraform init

Warning: Experimental feature "module_variable_optional_attrs" is active

  on versions.tf line 3, in terraform:
   3:   experiments      = [module_variable_optional_attrs]

Experimental features are subject to breaking changes in future minor or patch
releases, based on feedback.

If you have feedback on the design of this feature, please open a GitHub issue
to discuss it.

I would recommend opening issue for terraform. If this experimental feature will work in 0.14 as it is in 1.3.
https://github.com/hashicorp/terraform/issues

@imrannayer - Let me elaborate.
I have the below in my root module.
terraform {
  required_version = ">= 0.14"
  experiments      = [module_variable_optional_attrs]
...
}

I can also confirm that module_variable_optional_attrs experimental feature does work with v0.14.11 in other areas in my codebase.
According to terraform, experiments must be enabled per module basis - reference
Therefore experiments  = [module_variable_optional_attrs] should be set on the terraform  {} block within the module source code as well - which I cannot do as the module consumer.
So, can module_variable_optional_attrs be included into the module source?
Similar issue is discussed here

Setting experiments on a stable release does not work any more - ref.


Resolve relative sass_root paths earlier

Revert SassCssCompiler before #64. Supports relative paths by resolving/prefixing them at extension loading. I don't know if it should be implemented this way (it feels hacky?) but I don't see how it could be better.
What do you think of this change @smnandre ?
Tests are missing because I don't know enough how asset-mapper works to design an integration test for an AssetCompiler. Testing the builder instead would be even more work for me because my dev env doesn't supports the default sass binary from the bundle.
I'll not have more time in the next weeks to work on it, feel free to modify this PR as much as you want.

Yeah sorry, I ignored this part on purpose and I took the conservative choice to only rollback SassCssCompiler.
I don't understand the reasoning of the current supports implementation (comparison of two realpaths) but someone might wrote it for a good reason. Because of the missing or broken tests (in my env) I'd rather not prematurely update code not required for relative path support.

I mande a PR on your PR with small change suggestions :)
https://github.com/wryk/sass-bundle/pull/1


chore: Fail fast if Schemathesis.io responds with an error

Codecov Report

Merging #1447 (9c83f52) into master (b148d32) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1447      +/-   ##
==========================================
- Coverage   99.12%   99.01%   -0.12%
==========================================
  Files          86       86
  Lines        6641     6596      -45
  Branches     1162     1133      -29
==========================================
- Hits         6583     6531      -52
- Misses         30       34       +4
- Partials       28       31       +3

Impacted Files
Coverage Δ

src/schemathesis/cli/__init__.py
99.20% <100.00%> (+0.02%)
:arrow_up:

src/schemathesis/cli/output/default.py
100.00% <100.00%> (ø)

src/schemathesis/service/__init__.py
100.00% <100.00%> (ø)

src/schemathesis/service/handler.py
100.00% <100.00%> (ø)

src/schemathesis/service/worker.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/validation.py
76.47% <0.00%> (-11.77%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
98.23% <0.00%> (-1.77%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.36% <0.00%> (-1.64%)
:arrow_down:

src/schemathesis/specs/openapi/loaders.py
98.31% <0.00%> (-0.85%)
:arrow_down:

...rc/schemathesis/specs/openapi/negative/__init__.py
94.11% <0.00%> (-0.17%)
:arrow_down:

... and 21 more

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 b148d32...9c83f52. Read the comment docs.


Logger

Hi @celldweller24, please add description and check what is going on with builds.

Implements #2


enhance(golang): enhance Encrypt, ComputeMAC and Sign memory allocation

Use make function to allocate the slice with a specific capacity  as we already know the size of the slice which is length of primary.Prefix + the length of ct.
https://play.golang.org/p/EffLlzZaw-9

Thanks!


It cannot be run on CentOS.

package name：disk_usage_exporter_linux_amd64.tgz
 [root@localhost opt]# tar -zxvf disk_usage_exporter_linux_amd64.tgz -C diskusage/
._disk_usage_exporter_linux_amd64
tar: Ignoring unknown extended header keyword `LIBARCHIVE.xattr.com.apple.provenance'
disk_usage_exporter_linux_amd64

`[root@localhost diskusage]# file disk_usage_exporter_linux_amd64
disk_usage_exporter_linux_amd64: Mach-O 64-bit executable
`
How can I run it on CentOS? Please advise.

Oh, my mistake. I will replace the file in a while.

Please try to download the file again now. Should be fixed.


/tpahere requests complete even if the requester no longer has permission to execute it at teleport time

In order to avoid that players can teleport other players everywhere, try to make the /tpahere more safe.
For example: teleport the player that accepted the tpahere in the location where the first player asked to teleport to him. Another solution would be allowing teleport requests only in luckperms contexts: where the teleport permission is true, player 2 goes to the player 1, but if the permission is false, player 2 won't go to the player 1.

Removing the bug label from this because this isn't a bug so much as it is an unintended consequence of contextual permissions which is a LuckPerms feature, not a HuskHomes one (though it should still be accounted f or).

See new mode proposed in #139 to fix this


Getting issue in fetching location when device screen is locked Android

Your Environment

Plugin version:0.6.3

Platform: Android

OS version: 12

Device manufacturer and model: OPPO CPH2095

React Native version: 0.64

Plugin configuration options:
BackgroundGeolocation.configure({
desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
stationaryRadius: 50,
distanceFilter: 50,
notificationTitle: 'Background tracking',
notificationText: 'enabled',
debug: true,
startOnBoot: false,
stopOnTerminate: true,
locationProvider: BackgroundGeolocation.RAW_PROVIDER,
interval:50000,
fastestInterval: 50000,
activitiesInterval: 50000,
stopOnStillActivity: false,
url: 'http://<IP_ADDRESS>:3000/location',
httpHeaders: {
'X-FOO': 'bar'
},
postTemplate: {
  lat: '@latitude',
  lon: '@longitude',
  foo: 'bar' // you can also add your own properties
}

});

Context
I am trying to get the location all the time , whether device locked or unlocked , app in foreground or background , I have taken the background Permissions also , but not getting correct location when device is locked. I am not using the url but calling the API after getting location
Steps to Reproduce

open the app or close keep device screen lock 15 seconds and let the device lock itself
location will not be saved in db

did you face some build errors

no

Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
Could not find ::.
Required by:
project :app

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

did you face this error ?

@jagatrajsingh2000 Hello, did you get a solution?

Got any solution for this?

Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081 FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
Could not find ::.
Required by:
project :app

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

To solve the problem add this in your AndroidManifest
<uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_LOCATION" />
and add this services in the same file
<service android:name=".floatingview.FloatingViewService" android:foregroundServiceType="location" android:exported="false" />
That fix my problem


Added "-s" to curl command

Added option "-s" to curl in order to suppress curl statistical data showing up on bash shell standard output

🐧 club, LGTM 😄


Project setup

👇 👇 The following feature was added to the branch 👇 👇
👉 React Application was created
👉 Linters Configured

Hi @gergitokusse,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that is invalid because the README file is not porfessional. Here is a link to the README template to help us create a professional README file
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Could not run 'llm-server' with ollama (openchat/llama2)

Describe the bug
Could not run 'llm-server' locally with Ollama. The docker container sits in a restart loop.
Container log shows error:
ImportError: Could not import llama-cpp-python library. Please install the llama-cpp-python library to use this embedding model: pip install llama-cpp-python

To Reproduce
Steps to reproduce the behavior:

Clone repository 'git clone https://github.com/openchatai/opencopilot.git'
Set environment variables:

OPENAI_API_TYPE=llama2
EMBEDDING_PROVIDER=openchat

Install Ollama
Pull LLM models: ollama pull openchat && ollama pull llama2
Run 'make install' (or 'make install-arm')

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
On 'make install-arm':

Running containers:

Log of 'llm-server':

Desktop (please complete the following information):

OS: MacOS Sonoma 14
Browser: -
Version: -

Additional context
Add any other context about the problem here.

Found out that the 'OPENAI_API_TYPE' value 'llama2' does not work. I also noticed that the llm = get_llm() is used 3 times but not used in the code. A llm is used via chat = get_chat_model().
TLDR. To get OpenCopilot working with locally run LLM via Ollama set these variables in the .ENV file:
OPENAI_API_KEY=unused
CHAT_MODEL=openchat
EMBEDDING_PROVIDER=openchat
LOCAL_IP=http://host.docker.internal
VECTOR_SIZE=4096

Hey @jvgrootveld ,
thanks for mentioning it. Were you able to get it to work ? If not, I can help you with it

@codebanesr Yes I got it working with the variables in the .env file I mentioned above. I looked at the code myself to figure this out, good that it's now part of the readme!

Found out that the 'OPENAI_API_TYPE' value 'llama2' does not work. I also noticed that the llm = get_llm() is used 3 times but not used in the code. A llm is used via chat = get_chat_model().
TLDR. To get OpenCopilot working with locally run LLM via Ollama set these variables in the .env file:
OPENAI_API_KEY=unused
CHAT_MODEL=openchat
EMBEDDING_PROVIDER=openchat
LOCAL_IP=http://host.docker.internal
VECTOR_SIZE=4096

i did according your config, but i got the below reply from bot copilot
"HTTPConnectionPool(host='localhost', port=11434): Max retries exceeded with url: /api/generate/ (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f59863faaf0>: Failed to establish a new connection: [Errno 111] Connection refused'))"
i dont know why this connection refused?