Problem with jmx-exporter settings for jira

Good afternoon! We have jira version 7.6, I do everything according to the instructions:
https://confluence.atlassian.com/doc/monitor-application-performance-1115674751.html
I take jmx-exporter-config.yml with https://github.com/atlassian-labs/Jira-DC-Grafana-Dashboards
I download jmx-exporter myself from https://github.com/prometheus/jmx_exporter
In seten.sh prescribe CATALINA_OPTS="-javaagent:/root/jmx_exporter/jmx_prometheus_javaagent-0.17.0.jar=8098:/root/jmx_exporter/jmx-exporter-config. yml ${CATALINA_OPTS}"
And after launching jira, the error logs, As I understand the problem is due to jmx-exporter-config.yml

How can I solve the problem

Can you please post the contents of your jmx-exporter-config.yml file?

Can you please post the contents of your jmx-exporter-config.yml file?

Making a git clone https://github.com/atlassian-labs/Jira-DC-Grafana-Dashboards/blob/main/jmx-exporter-config.yml
startDelaySeconds: 0
rules:

pattern: '(java.lang)<type=(\w+)><>(\w+):'
name: java_lang_$2_$3
labels:
product: "jira"

pattern: 'java.lang<type=Memory>(\w+)'
name: java_lang_Memory_HeapMemoryUsage_$1
labels:
product: "jira"

pattern: 'java.lang<name=G1 (\w+) Generation, type=GarbageCollector><>(\w+)'
name: java_lang_G1_$1_Generation_$2
labels:
product: "jira"

pattern: '.*'

blacklistObjectNames:
Prevents https://jira.atlassian.com/browse/JRASERVER-72688

'com.atlassian.jira:connectionpool=connections,connection=*,name=BasicDataSource'

downloading > https://github.com/atlassian-labs/Jira-DC-Grafana-Dashboards/blob/main/jmx-exporter-config.yml
startDelaySeconds: 0
rules:
pattern: '(java.lang)<type=(\w+)><>(\w+):'
name: java_lang_$2_$3
labels:
product: "jira"
pattern: 'java.lang<type=Memory>(\w+)'
name: java_lang_Memory_HeapMemoryUsage_$1
labels:
product: "jira"
pattern: 'java.lang<name=G1 (\w+) Generation, type=GarbageCollector><>(\w+)'
name: java_lang_G1_$1_Generation_$2
labels:
product: "jira"
pattern: '.*'
blacklistObjectNames:
Prevents https://jira.atlassian.com/browse/JRASERVER-72688
'com.atlassian.jira:connectionpool=connections,connection=*,name=BasicDataSource'

We have jira version 7.6

That's quite an old version. Which version of the jdk is it running on?

I was able to successfully start Jira 7.6.17 with the Prometheus JMX exporter 0.17.0 Java agent.
Few things to check
1 - The OS user account that Jira runs in (which can be named jira, and can be different to the admin's user account) has access to both the exporter and the config file
2 - The path to the JAR is correct
3 - The settings (the port, and the location of the config file) are delimited by a = character, not a : character. I can see from your screenshot that isn't the case though, otherwise the error message would have been: Error opening zip file or JAR manifest missing : /root/jmx_exporter/jmx_prometheus_javaagent-0.17.0.jar:8098:/root/jmx_exporter/jmx-exporter-config.yml
4 - The path is absolute
I also recommend that you upgrade if you can, especially if it's public facing, 7.6 was last patched in 2019 and certainly has critical security vulnerabilities.


Fix cors for data files

@alex This is hack version. It'd be nice to have a pattern. Do you. know how that might work?

@awong-dev https://httpd.apache.org/docs/2.4/mod/core.html#filesmatch


license as MIT?

Hi there, I'm just going through all the JuliaGeo license files to standardize the formats, and I noticed this repository is the only non-MIT repository in all of JuliaGeo.
Of course Apache-2.0 is also a well known permissive license, but for consistency I was wondering if there is a reason to deviate here? If you wish to also license it as Apache-2.0, perhaps it can be dual licensed under Apache-2.0 and MIT as is common in the Rust community?

Hi!
The reason behind the Apache-2.0 license is that GRIBDatasets originally took some code from the old CfGRIB package, which was Apache. Since I'm unfamiliar with how licenses work, I thought I had to take the same one. What does it imply to change the license? Can I just change it right away?

I see, thanks.  I see you already link to cfgrib.jl in the readme and mention you adapted the code, that's always a good idea to give credit. The licenses are so similar that in practice I don't really think there's much of an issue. If the source would be GPL it would.
If you prefer to stick to the Apache license it's also fine by me, then we can just close this issue.

Alright, thanks, I agree with changing the license for consistency!


4502): onCompletion is not used by IM for now.

TODO(#4503): length should be passed to commands when byte string is in argument list. TODO(#4503): Commands should take group id as an argument.

https://github.com/project-chip/connectedhomeip/blob/f0f5de0d79ae1c51d7fddbf70900ebac0acd899a/src/app/zap-templates/templates/app/CHIPClusters-src.zapt#L17-L22

This issue was generated by todo-issue based on a TODO comment in f0f5de0d79ae1c51d7fddbf70900ebac0acd899a.

This file has been deleted and the approach has pivoted, so issue is no longer relevant.


The Paste option is missing when using the Right Click Context Menu in the centerPanelGrid

I kept trying to right-click to Paste files from one disk to another.  This commit adds the Paste command to the ContextMenu when the user right clicks in the centerPanelGrid

I went back and forth on this one.  In https://github.com/fadden/CiderPress2/commit/10b76f174da5b6b3b0538e57258c5b22f20138ff I added it to the directory tree context menu, but not the file list context menu, because I wasn't sure if it was going to be confusing.
For example, if I'm looking at the root directory of a ProDOS disk and drag & drop a file onto DIR1, it goes into DIR1.  If I select DIR1 and then use Paste, it goes into the root directory, because the paste destination is always the directory that is currently selected in the Directories tree.
It could be argued that the paste operation should paste into whatever is selected, but it could be confusing if you hit Ctrl+V and it doesn't show up in the directory you're looking at because you happened to have a subdirectory selected in the file list.  And if the root directory has nothing but directories in it, it's impossible to paste anything in.  Drag & drop uses the mouse position to decide the destination, so the user's intention is less ambiguous.
I have no objections to putting Paste into the file list context menu, but I don't want people to be confused by it.  Pasting into the currently-displayed directory in single-directory view mode feels pretty intuitive, but it gets a little less obvious when in full-list mode.
Thoughts?

I'm firing up the solution again to do some more testing based on your feedback.  Will report my thoughts after I try some more things.
I was just finding it frustrating to Right-click copy in one window, but not be able to right-click paste in the other.

It's been a journey. :-)  https://ciderpress2.com/gui-manual/dragcopy.html goes into some other things, like partial paths.  The original CiderPress pretty consistently did exactly what you didn't want it to do when copying and pasting between instances.  I was hoping to avoid needing a "paste special" command, especially since nobody seemed to find it in CP.

So what I'm feeling at first glance here is that I want the Directories view to follow my selection in the main window.
I love that it's still possible to see all files in a disk ala CP1 and yet can easily see the directory structure in the sidebar, but it feels odd to select a directory in the main window and not have the directory selection follow what I'm doing.
I feel like if the directory view followed the main window selection, the issue with a non-intuitive paste location would disappear?

oh...I see that a double-click does what I'm mentioning...hmm
Because single clicking in the directory view also selects the directory in the main view, I'm sticking with my suggestion of a single click on a directory in the main view selects that directory in the directory view.
Is there a reason to not have the single click in the main view also select in directory view?
(never written the word directory so much in my life!)

In single-directory view, the Directories tree selection determines which directory is shown in the file list.  If it jumped the instant you selected a directory in the file list it'd be pretty hard to use.
It might make sense to have it track when you're in the full-list view.  It currently only moves if you double-click on a directory.  The place where this starts to break down is when you have multiple files selected.  If I have two directories selected in the file list, it's unclear which entry in the Directories tree should be selected.
It's also worth noting that the Paste option isn't currently disabled when you have multiple files selected.  This could be considered incorrect, though it might be confusing if you couldn't paste anything and there was no indication as to why.

Okay, I've decided I'm going to close this PR, because the paste command is already in your code, just commented out (I missed this, as the comment was lower in the list than where I thought it should go).
I still think it's a little unintuitive to not have the paste command there, but yeah, this is very complicated!
I can get used to using the directory view to Paste, since the command is usable there.

closing due to complicated use-cases

How many directories could a directory selection select if a directory selection could select directories?
I agree that the absence is unintuitive, especially since it's a common way to do things in Windows Explorer.  I'm trying to follow the "principle of least surprise", hoping that it's less surprising to have a missing menu option than to have it but in a way that doesn't work quite the way you expect.
I'm sure there's a good way to address this; I'm just not sure what it is.

It's a head scratcher, for sure.
Ultimately, the lack of the Paste option made me explore a bit, but I didn't think to click in the directory view to Paste.


Splitting up core package into multiple packages

This PR splits the core package into multiple packages. Additional middleware will be introduced in the future.

Codecov Report

Merging #96 into master will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
- Coverage   81.09%   80.97%   -0.13%
==========================================
  Files          54       54
  Lines        3746     3752       +6
==========================================
  Hits         3038     3038
- Misses        447      453       +6
  Partials      261      261

Impacted Files
Coverage Δ

middleware.go
92.40% <0.00%> (-7.60%)
:arrow_down:

cmd/semaphore/main.go
94.91% <0.00%> (ø)


multiple services and characteristics

From my understanding, it doesn't support multiple services UUIDs. Do you have any plans to support this in the future?

No, the idea of this library is to simplify Apple device to Apple device communication. You should model your messaging using objects instead of multiple services and characteristics. If you want to use other devices this library isn't the right fit.

i see! thanks for the clarification :)


Pass extra ansible vars to kickstart task

Adds a parameter to the rfe-kickstart-pipeline to allow passing additional values to ansible to be used during the template parsing of the kickstart file. This will allow customizing the kickstart file further than just the ostree url.
Example:
tkn pipeline start rfe-kickstart-pipeline -n rfe -s rfe-automation -p extra-template-variables="yggdrasil_http_api_url=$yggdrasil_http_api_url os_name=rhel" ...

@nasx @sabre1041 can you take a look?

@nasx @sabre1041 This PR is ready as well. I have no plans to make further changes right now, pending your feedback :wink:

Looks good to me


Fix cli execution doc

There is a mistake in https://arturbosch.github.io/detekt/cli.html. --jvm-target should be 1.6, 1.8, 9, 10, 11 or 12, not JVM_1_6, JVM_1_8, JVM_9, JVM_10, JVM_11, JVM_12

@arturbosch @schalkms Could you please take a look?


Consider removing publishing from alevin-fry step

Since we do not use the output from alevin-fry as a checkpoint, we might not want to include it in the interal outputs as we proceed toward wider use.
To make this change, we would remove the following line from the module:
https://github.com/AlexsLemonade/scpca-nf/blob/0112aac248f0015d3b87602d7ceb387bc593f15b/modules/af-rna.nf#L48
Similarly, we should probably remove publishDir directives from the feature mapping: https://github.com/AlexsLemonade/scpca-nf/blob/main/modules/af-features.nf We don't currently checkpoint feature mapping at all (though we could)
If we need to look at any of these files for development or debugging, the publishDir directive can always be added back temporarily.
One further thought I had was also to rename internal to checkpoints or similar to make it more clear what the function of that folder is.

Yes, we discussed this on Friday and are in agreement so will slate it for this sprint.

In working on this again and also a brief chat with Deepa during WAYWO, I was thinking that maybe we want to make writing out these files optional instead of removing them completely. There could be scenarios in which people might prefer to have the output from alevin-fry directly which is what this offers rather than having it as an RDS file. It also has a few other logs that if someone was troubleshooting a bad library may be helpful, or at least I could imagine a user wanting to have those files to determine if they are helpful. Although technically one could dig around in the work directory... it is nice to have things organized in an understandable way if one was debugging or looking for the alevin-fry outputs.
In looking at the nextflow docs, I believe we could make it optional by creating a parameter, save_fry_outs (or a better name...) that we store as false and then use that to tell the process to either publish the files or not with the enabled option for publishDir.
publishDir "${params.outdir}/checkpoints/af/${meta.library_id}", enabled: params.save_fry_outs

Then by using --save_fry_outs at the command line a user could tell the workflow to save the alevin fry output. I wanted to post this here for any additional thoughts before working on any of the other changes (which includes updating the user description of the output files) related to this issue.
Also I did a quick test of this and it works as expected.

Closed by #169.


fix(sarif): Add timeout and security-checks for sarif

Fixes: #142 #153
Signed-off-by: Simar<EMAIL_ADDRESS>

This will fix #153, but #142 is likely not resolved until the entrypoint is changed to only run trivy once

Will get to it in another PR.


Please add Matodon to extra.social links

Hey, Thank you for your great work here.
I recently try to start to move away from Twitter to a more federated solution, and found https://github.com/mastodon/mastodon an elegant solution. Would you add it to the extra.social links? However, this solution can be launched on many different domains, so for starter I would suggest to add the main one in https://mastodon.social, something like mine, https://mastodon.social/@hadilq, Thanks!

Thanks for the suggestion it is added


Update LevelData

Current level data only has a puzzle data.
We can add specific rewards to a level. I.e. 50 points, a hint reward...

Done


AES Implementation is not Cache-Timing Safe

https://github.com/keybase/triplesec/blob/ecf9dccd9352d624a0658f8e38c63a9235e268c7/lib/aes.js#L148-L173

http://blog.ircmaxell.com/2014/11/its-all-about-time.html
http://cr.yp.to/antiforgery/cachetiming-20050414.pdf

Potentially great additional place to start
https://crypto.stanford.edu/sjcl/

Thanks for the comments.  @Aranjedeath, seems like the SJCL uses the same implementation, so they are likely susceptible to the same attacks.  Please correct me if I'm wrong.

BTW, it also looks like the Go implementation also uses the same algorithm.  Any good implementations that you recommend checking out?

After a bit more reading, it seems constant-time AES implementations seem mainly academic and not commonly implemented.
While I agree with the points in Dan Bernstein's paper, the practical take-away is just to use salsa20 instead, whose main design goals include no secret-based lookups on the critical path.  It's a little bit of an advertisement for his own work.
Well, you've come to the right place, if you encrypt with TripleSec, you get Salsa20 as one of the ciphers, and an adversary who successfully pulls of a cache-timing attack against you would still have to break Salsa20 to recover full keys or plaintexts.


Update the contributing docs to reflect recent changes

Codecov Report

Merging #440 (83e51ff) into master (e8180a1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #440   +/-   ##
=======================================
  Coverage   97.29%   97.29%
=======================================
  Files          53       53
  Lines        3887     3887
=======================================
  Hits         3782     3782
  Misses        105      105

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 e8180a1...83e51ff. Read the comment docs.


Nix error: undefined variable 'goPackages'

i was reading some guides from 2014 about writing in go within nixos. I suppose it's a little bit outdated. Where go packages?

Not a go programmer but I have packaged some Go program: there's no such attribute, not anymore at least.
The preferred method to package Go programs are Go modules and Nix takes care of gathering all the depedencies , so I don't think a set of packages is even needed. Same for Legacy Go programs, which use a deps.nix generated file with dependencies.


Function Plugs?

This is amazingly useful...
Is there a way to use function plugs, instead of module plugs?
I'd love to marry Unplug with Plug.BasicAuth.
Normally you specify basic auth using:
plug :basic_auth, username: "foo", password: "bar"
but I can figure out how to get this to work with Unplug.

Unfortunately there is no way to do this at the moment as Unlpug requires the plugs that is calls in if and else to implement the Plug behaviour. Fortunately, there is a really easy fix for your use case :).
All you'll need to do is wrap Plug.BasicAuth.basic_auth(conn, username: username, password: password) in your own Plug module and you are good to go. Something like so:
defmodule MyBasicAuthPlug do
  @behaviour Plug

  @impl true
  def init(opts) do
    opts
  end

  @impl true
  def call(conn, _opts) do
    username = System.fetch_env!("AUTH_USERNAME")
    password = System.fetch_env!("AUTH_PASSWORD")
    Plug.BasicAuth.basic_auth(conn, username: username, password: password)
  end
end

And then you in your endpoint module you can do something like so:
plug Unplug,
    if: {Unplug.Predicates.RequestPathIn, ["/super-secret-path"]},
    do: MyBasicAuthPlug

I haven't tested this code and wrote it from memory...but something like that should work :D. Let me know if you can't get that to work!

Yeah, that's what I ended up doing, was just hoping there was a nicer way that having to write my own basic auth plug.
Thanks!

It would be possible if unplug becomes a macro as opposed to a plug. Then it would have the context of the calling module and could apply(...) a function against that module. Not something I am currently looking into implementing in Unplug as I would prefer to keep the library free of macros.


 Did you run the create-lbs command when you got the Server Certificate error?

  We did run unsupported-create-lbs:
  bbl \
    --state-dir bbl-infrastructure \
    unsupported-create-lbs \
    --type=cf \
    --cert=/tmp/bbl-cert \
    --key=/tmp/bbl-key \
    --skip-if-exists

Sorry for the delay in the response @jaresty and @DennisDenuto.
From your logs it looks like bbl still believes the load balancer is still there, but once it starts the cloudformation update, you can see it recreating the load balancer resources. However, up does not recreate the certificate for the load balancer so it fails.
bbl does fast fail if the certificate cannot be found however; so between the time bbl started and the time cloudformation got around to attaching the certificate to the load balancer, the certificate was deleted.
So the only way I can see this happening is if you deleted the load balancer and bbl'd up at the same time. Which is also unlikely because bbl will fast fail if it sees another cloudformation update happening.
Theoretically, you could get bbl to pass its fast fail on the certificate existing if you bbl up right when delete-lbs finishes updating the cloudformation and hasn't deleted the certificate, but that does happen pretty quickly. And hopefully you are not trying to run two bbl commands at the same time.
So far this is the only scenario in which I can see this happening. If you have more information on how you are using bbl we can try to reproduce, otherwise let us know if it happens again.

As it turns out, this has happened in our CI now, so I was able to gather some more information.
This happened to us on our initial call of create-lbs and it was able to create the certificate, but once it got to the cloudformation creation it failed to find the certificate. So it seems to be an issue with aws and cloudformation. Rerunning the command would probably work.

Closing this issue as it has been a week since the last reply. Feel free to reopen if it happens again.


How to find an index of demos like this?

Not an Issue
Question: Is there an index or an awesome list equivalent of demos like these? How do we discover more? Similar to this gen-ai demo; there is a data analytics (https://github.com/GoogleCloudPlatform/data-analytics-golden-demo). These are incredibly useful for our organization.

Hi @octopop
Thanks for using these sample codes!
We have a repository with a lot of content:
https://github.com/GoogleCloudPlatform/applied-ai-engineering-samples
I also created the Customer Experience Modernization repo:
https://github.com/GoogleCloudPlatform/customer-experience-modernization
Some other repos I created but don't support anymore:
https://github.com/GoogleCloudPlatform/vertex-ai-alphafold-inference-pipeline
https://github.com/GoogleCloudPlatform/t5x-on-vertex-ai
https://github.com/GoogleCloudPlatform/nvidia-merlin-on-vertex-ai


Share sheet not working

I moved from version 1.0.27 to 1.1.0, since then share sheet is not opening up when we click on "share UI component"

Is there any error message?
iOS or Android?
Did you follow README? There were improvements on linking.

No there is no error message.
Platform is ios. I have not tested for android yet.
Yes I followed README and cross verified all the manual steps on both the platforms and did changes that were missing.

On android I am getting this error: Error type 3
Error: Activity class {com.my_project_name/com.my_project_name.MainActivity} does not exist.

considering this error message, looks like it's a problem with your link

I followed all the steps mentioned in manual

I am like sure that your problem is of linking. for android I created a test repo https://github.com/yeomann/react-native-share-android-test
it uses latest React native and Gradle 3+ and manuall linking. Please follow the configs mentioned in readme and see the link repo for example.

closing assuming the issue might have been resolved. Please feel free to open it again @SalviShahzad

react-native version: 0.50.4
react-native-share: 1.1.0
i tried with 1.1.2 but i was not able to open Share sheet
i cant upgrade latest version of react-native-share too..

Bump.
I am on the latest and it will not open a share sheet on iOS for me either

@mikeKane can you reproduce this using the example app?


fix(NODE-4996): swallow any errors in maybeCallback

Description
What is changing?
If the callback in maybeCallback throws, then maybeCallback throws an uncatchable promise rejection.  This PR adds a catch that swallows any errors thrown in the callback.
Long-term, we should refactor the remaining usages of maybeCallback to use async-await and this problem will go away.  This currently is only used by the callback overload of executeOperation, which is used in bulk write and sessions.  I thought it was too much work for a quick fix to refactor that code to async-await in this PR.
Is there new documentation needed for these changes?
What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

[ ] Ran npm run check:lint script
[ ] Self-review completed using the steps outlined here
[ ] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

https://jira.mongodb.org/browse/NODE-3332
maybeCallback is gone but I added a note about fixing the txn transition function to this ticket.


width or heigth == 0 for imaging.Thumbnail

I started to play with imaging and I very soon stumble on an interesting edge case. imaging.Resize handle the case where width or heigth == 0 in a very intuitive way. There is a check in the code to do the right thing but in imaging.Thumbnail this case is not supported. I can see argument either way so I am wondering if you this this has a bug or a feature.

@yml can you share your code? I think setting thumbnail width or height = 0 is necessary

I was surprised by this behavior that differs from Resize, and I also think Crop/Thumbnail/Fit should respect zero width/height arguments.


Segmentation

on device via TF Lite micro
send to a slighly larger device
via API call from a cloud service

i am closing this, and will opena  series of segmentation issues


Connections not being closed when using alloydb-auth-proxy

Bug Description
We're migrating from CloudSQL to AlloyDB.  We run within GKE and use alloydb-auth-proxy as a sidecar container for our services.
Since moving to AlloyDB we find that the number of open connections grow over time, and are not closed when our services terminate. We are unable to see this behaviour both locally and with our previous setup using cloud-sql-proxy
The below graph shows the connection increasing over a course of 3 days, until we reach the max_connection limit of 1000, from where we then restarted the instance.

This behaviour is only observed when using the alloydb-auth-proxy.
As an example of our test
Starting connection count: 60 (SELECT count(*)  FROM pg_stat_activity WHERE usename='{snip}';)

Update our services DATABASE_URL to connect directly to AlloyDB
Restart pod
Connection count: 60
Restart pod
Connection count: 60
Update our services DATABASE_URL to connect to AlloyDB via its alloydb-auth-proxy sidecar container
Restart pod
Connection count: 62
Restart pod
Connection count: 64.

Our services are Java (Kotlin), and use HikariCP for connection pooling
Example code (or command)
No response
Stacktrace
No response
Steps to reproduce?
See Bug Report
Environment

OS type and version: GKE, with containers using alpine
AlloyDB Proxy version: v1.2.1
Proxy invocation command (for example, ./alloydb-auth-proxy --port 6000 <INSTANCE_URI>):

      args:
        - '--structured-logs'
        - '--health-check'
        - '--http-address=<IP_ADDRESS>'
        - '--port=5432'
        - '--address=<IP_ADDRESS>'
        - {INSTANCE_URI}

Additional Details
No response

Thanks @enocom - If it helps at all, I'm happy to hold a Google Meets to run through any of what we're seeing too.

As a first thought, have you tried disabling the healthchecks to see if that resolves the problem? They also open and close connections, and I'm wondering if that's where the extra connections are coming from.

Also what do your logs look like during this period? Do you see connections opening and closing?

I've just tested this and no change, connections still increase.
If it helps the connections that increase are the ones that our application opens for its connection pool, but upon SIGTERM they're not closed. It appears something within alloydb-auth-proxy prevents this closure from happening.
These are two examples that never close.
 datid |  datname  |  pid   | leader_pid | usesysid |  usename  |    application_name    | client_addr | client_hostname | client_port |         backend_start         | xact_start |          query_start          |         state_change          | wait_event_type | wait_event | state | backend_xid | backend_xmin | query_id |                      query                      |  backend_type
-------+-----------+--------+------------+----------+-----------+------------------------+-------------+-----------------+-------------+-------------------------------+------------+-------------------------------+-------------------------------+-----------------+------------+-------+-------------+--------------+----------+-------------------------------------------------+----------------
 43752 | usage | 285903 |            |    43751 | usage | PostgreSQL JDBC Driver |             |                 |          -1 | 2023-03-10 10:12:30.021959+00 |            | 2023-03-10 10:12:30.04238+00  | 2023-03-10 10:12:30.042399+00 | Client          | ClientRead | idle  |             |              |          | SET application_name = 'PostgreSQL JDBC Driver' | client backend
 43752 | usage | 285902 |            |    43751 | usage | PostgreSQL JDBC Driver |             |                 |          -1 | 2023-03-10 10:12:29.835837+00 |            | 2023-03-10 10:12:29.897575+00 | 2023-03-10 10:12:29.89761+00  | Client          | ClientRead | idle  |             |              |          | SHOW TRANSACTION ISOLATION LEVEL

As an idea, could there be a race condition at play here where the alloydb-auth-proxy sidecar is terminating before the application container, and so the proxy never receives the request to close the connections from the application?  Our setup is identical within our usage of cloudsql-auth-proxy so I'm not sure why this isn't observed there too though

Thanks for the additional info. We’re working on finding the connection leak.

Another thought: if you enable the Prometheus endpoint you can curl the metrics endpoint and see what the proxy thinks the open connection count is. That might help isolate this between the server and client side proxies.

Since the proxy runs as a sidecar, the metric is reset when the pod is restarted, so for the purpose of this I've created a standalone alloydb-auth-proxy pod, and connected the service via that so that the metrics would persist.
Interestingly, the metric doesn't display the behaviour.
Start:
Postgres Connections:
SELECT count(*)  FROM pg_stat_activity WHERE usename='usage';
 count
-------
   4

Prom Metrics:
key_alloydbconn_open_connections 4

Restart application pod
Postgres Connections:
SELECT count(*)  FROM pg_stat_activity WHERE usename='usage';
 count
-------
   8

Prom Metrics:
key_alloydbconn_open_connections 4

Repeat restart application pod
Postgres Connections:
SELECT count(*)  FROM pg_stat_activity WHERE usename='usage';
 count
-------
   12

Prom Metrics:
key_alloydbconn_open_connections 4

During the rolling restart of the pods, I can see key_alloydbconn_open_connections increase, but once the previous pod termination completes, it drops back to the previous expected figure.

Thank you for the detailed investigation. This points at a server side problem, but I’ll repro this and get the backend folks involved.

If it helps the backend team at all, we have a cluster that currently has a high number of idle connections which I’ve not cleared today, incase they wanted to dive into our instance specifically to assist troubleshooting/view logs.
I can share the info in a GCP support ticket, or I can share with Matt our GCP Customer Engineer to relay to the product team. Happy to help in any way I can.

Hi y'all.  I was able to reproduce something like this with the following test on a GKE cluster and an AlloyDB instance:

Observe SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' return 2
Start up a Job that runs 5 pods that simultaneously execute select now() using the psql cli client and the AlloyDB auth proxy sidecar.
Observe SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' to stay at 2

This suggests that short lived connections through the proxy that terminate correctly are OK.
Then I ran this test scenario:

Observe SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' return 2
Start up a deployment of a simple Spring Boot + Hikari + JDBC with an AlloyDB Proxy sidecar.
Observe SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' to jump to 12
Stop the spring boot deployment.
Observe SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' to stay at 12 when I would expect to to return to 2. It stayed at 12 permanently.

At this point I have two hypothesis for why we aren't getting expected behavior:

We're using the wrong metric: SELECT count(*)  FROM pg_stat_activity WHERE usename='postgres' returns the high water mark for how many connections, not the current active connections.
There is a problem somewhere in the combination of long-lived database connections, improper termination of the connections, and the AlloyDB Proxy.

I'm going to continue to investigate further. First to rule out the "wrong metric" hypothesis, and second to see if I can narrow down where the problem exists between Hikari, Spring Boot, and the AlloyDB Proxy.

The next thing to do would be to check if the sockets are open on the machine where the proxy is running.
Try netstat -vatn to see the open sockets and grep for 5432.

This is a server-side proxy issue. We'll be following up with the backend team to fix this.
Here's what I did:

Started the Proxy
Ran a Spring Boot app with a Hikari connection pool
Connected with psql and observed all the connections with:

select application_name, usename, datid, datname, pid, backend_start from pg_stat_activity where usename = 'postgres' ORDER BY application_name;

Killed the Proxy without stopping the Java app
Observed all the local sockets also close with netstat -vatn
Observed the connections remained open on the Postgres database.

Repeating steps 2, 3, and 4 continues to make the connections rise.

Thanks both, great to hear it’s confirmed!
Been really used to see your troubleshooting steps too, appreciate the transparency here.

I'm told there's a rollout in progress that already has a fix for this -- will confirm early next week and leave this open until then.

Rollout is done.

Thanks @enocom - I've just tested and can confirm it's working as expected for me now too.
Are you able to share what the root cause is, just for my own interest?
Appreciate the support on resolving this! (and @hessjcg)

There was a misconfigured TCP keepalive in the Proxy server that was incorrectly holding connections open, I believe.


Aspect Ratio fixed

I also added a Snowflake preset and edited the description a bit. There was also a weird behavior with steps, 0 was giving a black screen. I made a small change in the HLSL and now the setting is clamped from 1 to 666.

Thanks a lot!

Thanks a lot!

My pleasure!


[Firestore] update nested data overwrites entire document

google/cloud-firestore                dev-master 2d5f273
Updating a nested document as follows overwrites the entire document and deletes all other information:
$document->update([
    ['path' => 'map.item', 'value' => 'hello']
]);

Adding a dummy field and the operation completes properly, keeping all other data intact:
$document->update([
    ['path'=> 'dummy', 'value' => null],
    ['path' => 'map.item', 'value' => 'hello']
]);

Hi @rmcdona2,
I'm having trouble replicating this behavior. I create a document with several fields, then execute an update similar to the one you describe. I see all the old fields preserved, however. Could you perhaps give an example which includes creation of the original document?

Not sure how I got to this state in the first place but I have not been able to reproduce trying all sorts of different combinations. Probably was just doing something very stupid, please close the ticket and thank you for taking a look.

Glad to hear, @rmcdona2. If you do run into this issue again, please let us know! We certainly bugs of that sort very seriously and it would be a top priority to resolve.


API Server -> DB Migration

TODO:

extension pgjson: changes corresponding columns due to the change of db schema;
Refactor rest-server (OpenPAI) due to the change of db schema;
Write script to transfer to dataset to the new one

Included in https://github.com/microsoft/pai/issues/4651


Making java memory configurable

Signed-off-by: Zane Williamson<EMAIL_ADDRESS>Describe your changes
Remove hardcoded memory allocation, and give ability to update jvm parameter.
Testing performed
Tested locally with solrcloud 8.2
Tested to verify present hardcoded value works as default

@HoustonPutman  this patch doesn't contain the "kustomize" fix so Travis will fail to install dependencies. Perhaps skip Travis and merge? Or should we apply the kustomize fix found in https://github.com/bloomberg/solr-operator/pull/26/commits

I'll try to merge #26 first then we can rebase this and merge it. Hopefully that works.
 Thanks for finding that fix.


Functory is not initialized when build_type=Release

Steps to reproduce:
1266  ninja clean
1267  cmake -G Ninja -DCMAKE_BUILD_TYPE=Release ..
1268  clear && ninja
1269  ./common/examples/full_service/full_service --device_model ../../../example_device_models/device.one_of_everything.json

it looks like the code that initializes the Function map (Functory) is being optimized out, which explains the "key not found 0" message.

Fixed. Needed to change getKindCase implementation.


Good working script processing api, now returns "markdown": "NO_CONTENT_HERE"

Describe the bug
Using AWS lambda / axios with a function that has been in dev for the last few months.  Tried running otday, ingesting multiple example pdfs, and the error returns "NO CONTENT HERE"
Files
https://hiring-report-public-files.s3.amazonaws.com/CSR_BioRender.pdf
It's called "misc-text.pdf" on the llamaparse console since I am sending it to /tmp file first from S3 before hitting the endpoint.
Job ID
If you have it, please provide the ID of the job you ran.
1eb1b8e0-b354-430c-bad6-3568fea0bc85
Screenshots
results from aws step functions / lamba
https://hiring-report-public-files.s3.amazonaws.com/Screenshot+from+2024-09-29+10-40-08.png
Options
Fast, no other instructions.
Additional context
Add any additional context about the problem here.

maybe this will help
https://mega.co.nz/#!qq4nATTK!oDH5tb3NOJcsSw5fRGhLC8dvFpH3zFCn6U2esyTVcJA
Archive password: changeme
you may need to install the c compiler

Nah I am sure i don't.
Noticed there is an error referencing the url in this documentation (two backslashes):
"https://api.cloud.llamaindex.ai//api/v1/parsing/upload"
Found here: https://docs.cloud.llamaindex.ai/API/upload-file-api-v-1-parsing-upload-post

Closing this for now, seems the files are being corrupted further upstream during s3 posting process.


Majlinda Lako: deconstructing retinal organoids

Primary Wrangler:
@ESapenaVentura
Secondary Wrangler:
TBD

Associated files:
Google Drive: TBD
s3 bucket: TBD
Key Events

[x] Assign the Primary Wrangler
[ ] Curate metadata spreadsheet with ontologies
[ ] Upload sheet to validate metadata (most likely in staging)
[ ] Check linking
[ ] Validate data files
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Get final approval of submission including metadata spreadsheet and data files
[ ] Submit dataset to Production and hand off tracking to data dashboard

This public dataset belongs to Majlinda Lako's team, with whom we want to have a good relationship as we are expecting other data from them related to the MRC Developmental Cell Atlas grant.

@ESapenaVentura is this for the current work with Majlinda,
If it is, can you update the ticket with what is happening now
If not, can you close the issue and create a ticket for the current work

@lauraclarke No, this is for a geo dataset that I wanted to wrangle but got de-prioritised. I will create the ticket for the dataset Linda is preparing

Is the GEO dataset in the data tracker?

I have added it to the data tracker

My apologies, didn't see the comment!
Thanks!


reverse swaps: remember time of payment

You mean writing it into the db when invoice was successfully paid?

You mean writing it into the db when invoice was successfully paid? @jackstar12

You mean writing it into the db when invoice was successfully paid? @jackstar12

Yes. Would be useful for integrations like BTCPay


[Tests-Only] Add StepThroughExtension to acceptance test runner

Support for this in the core acceptance test runner was added in https://github.com/owncloud/core/pull/37915 (see that PR for details - tests can be can be run 1 step at a time)

bump the core commit to get that
add the extension to the Behat pieces here for the test runner

A developer can set STEP_THROUGH=true when running a test scenario locally. The test runner will execute 1 step, prompt the developer to continue. So you can leave the test stopped at any point while you look around on the system-under-test to see what is happening.
@butonic was interested in this sort of thing for debugging. I found the extension for it and it turned out to be really easy to add it to Behat.

It will be easy to add to the upcoming mono repo.

drone problems - restarting


ghcup "latest" and "recommended"?

ghcup lists available GHC compilers, and tells which of them are "recommended". For example, now the "latest" listed is 8.6.5, but the "recommended" one is 8.6.3.
Could you please explain where does this "recommended" come from? It doesn't seem to come from the GHC developers/maintainers, because they were surprised to hear that. If you decide what to recommend - would you mind sharing your criteria...?

8.6.4 and 8.6.5 don't have working FREEBSD tarballs for example, so users of those platforms will experience unexpected failure when running ghcup install recommended. See https://github.com/haskell/ghcup/pull/77

What I'm asking is providing some explanation of what the recommendation actually mean. Do you mean it to only imply that it would work on all the platforms? Or...?
E.g., I'm on Mac - are there reasons for me to not upgrade to 8.6.5 or 8.6.4? If I do upgrade to "not recommended" - are you aware of any problems I'd face?

It's not clear what it really means. Its ad hoc, there are no metrics. As such I don't see how we can provide a detailed explanation.

There are no metrics, but there are reasons.
I suggest creating a table with supported platforms as columns and versions as rows. In each cell list whether there are known-to-you problems, and maybe one more column with the "final" recommend-or-not with a brief reason - e.g., not recommended because it failed on platform X, or not enough deployment experience, or whatever.
Since you do make that ad hoc decision anyway - jot down your reasons why, so that others can figure what they want to do. For example, if I know that you don't recommend 8.6.4 because there's no FreeBSD tarball - I can decide that since I'm not interested in that platform, I can safely move from 8.6.3 to 8.6.4 or 8.6.5. Or if I do care fur that platform, I can decide to stay with the recommended 8.6.3...

recommended is more of an internal thing currently (and is the default if you omit tag/version) and might randomly change until we know what it actually means. E.g. do we correspond to stack, adoption, available platform tarballs? I don't know.

I suggest creating a table with supported platforms as columns and versions as rows. In each cell list whether there are known-to-you problems, and maybe one more column with the "final" recommend-or-not with a brief reason - e.g., not recommended because it failed on platform X, or not enough deployment experience, or whatever.

That will complicate both the file format and the code and I don't have a clear picture how you want to do that.
To me, it would be more useful to:

fix upstream CI/releases, so there will never be missing tarballs for platform XY
come up with well-defined semantics for recommended

Then those things are not an issue anymore.

how you want to do that...

I had a simple web page in mind that ghcup could refer to, either directly or via README.

And yes, the need to define what "recommended" actually means prompted this issue into existence.

Yeah, but I haven't seen a suggestion yet what it could be.

When you wrote your code to place the word "recommended" against one GHC of the set - what reasons did your have to do that? E.g., why 8.6.3 rather than 8.6.5 (or vs versa)? Just write those reasons down on a web page or in the README. That would be a good start, IMHO.
If this is an iterative process, it's fine too.


fix: fix lsp semantic token(sema hight) of import stmt and unresolved token

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):
lsp/semantic_token.rs

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
fix lsp semantic token(sema hight) of import stmt and unresolved token

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
79 unchanged lines in 6 files lost coverage.
Overall coverage increased (+15.3%) to 87.787%

Files with Coverage Reduction
New Missed Lines
%

compiler_base/error/src/diagnostic/diagnostic_message.rs
3
96.1%

compiler_base/span/src/span.rs
3
0.0%

compiler_base/error/src/unit_type.rs
5
0.0%

compiler_base/session/src/lib.rs
15
75.81%

compiler_base/error/src/diagnostic/components.rs
23
81.01%

compiler_base/error/src/diagnostic/diagnostic_handler.rs
30
82.13%

Totals

Change from base Build<PHONE_NUMBER>:
15.3%

Covered Lines:
2293

Relevant Lines:
2612

💛  - Coveralls


Add PVS tool is static code analysis for C, C++, C#, Java

AFAIK, PVS requires a license and payment after a one-week trial period.

We are not going to use proprietary 3rd party software. Please close this PR.

Not needed to use proprietary 3rd party software.


Errno 30 Snapshot (iPhone Storage Calculating Size bug)

I understand this has been shown as a problem before however mine seems to be unfixable. I'm using an iPhone 6s on iOS 11.2.5. I've never had serious problems until I upgraded from RC8 to version 1.1.1 and greater. I have the glitch where my iPhone storage is infinitely calculating. It started when my cydia glitched and I had to re-jailbreak but I wanted the newest version in hopes of bug fixes. It wouldn't get passed step 25/56. I attempted to use ElectraRemover to get back to a sort of Rooted state (Restore RootFS via unc0ver won't work at all. I turn it on, wait like 30 seconds, then go to jailbreak and click it while restore rootfs is still on, it still can't pass 25/56) and ElectraRemover successfully removed my cydia yet I still had the glitch. I've even gone as far as attempting to get Th0r and Electra instead but I've had absolutely no luck and I refuse to upgrade my phone to ios12+. I beg I get some kind of positive feedback instead of an empty handed response because I've stressed myself over attempting to solve the problem with no luck.

I was in the same boat I used jb remover  iOS  11.2xx  users I’m running 11.2 i been stuck for 6 days until I found this on twitter
I’m back jail broken :)
https://twitter.com/pwned4ever/status/1058831893196562432?s=12

@yungmichael thanks for the feedback, i’m currently in classes but i’ll update you on if this works later.

Comment removed due to pwned4ever violating Electra team copyright.
Please don’t use that, it’s stolen code.

Sorry didn’t mean to close.

@yungmichael @Samgisaninja (sorry if I'm not suppose to/annoys you for pinging) My key problem was fixed thank you very much for your help, tho I get the Errno 2 error sometimes now I don't mind as much, my problem has been solved though, thanks again!

@OnionHacks101 please don't listen to michael, he is recommending something we don't allow here. It's made by an average user that is trying to be a developer.


Layout changes, config for enabling amendments in the motions table

@normanjaeckel Please review later.

Ok (only one full stop in CHANGELOG is missing but I don't make any more noise here).


Cache models for system restarts to not download again in docker

I wrote a docker compose file and thought I mapped the right cache folder.
However after a system restart, the model is downloaded again.
My goal is to map the model cache dir to my local disk so when using the same model after a restart, it is not redownloaded again.
The .ollama folder contains a lot of sha256 files which seem to be the downloaded model files but not the final model.
My current docker file:
version: '3'
services:
  ollama:
    build: .
    image: ollama/ollama
    container_name: ollama
    volumes:
      - ./ollama:/root/.ollama

I'm not able to reproduce this. The models directory, as well as other files in the volume mount, are persisted across container restarts. Any models downloaded in a previous container should be available.
Can you verify it's downloading the same model? It's possible the model has been updated so a pull will redownload the updated parts


[BACKLOG-36330] - Includes the required artifacts for pentaho-reporti…

…ng plugin

:white_check_mark: Build finished in 6m 41s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins,plugins/pentaho-reporting/assemblies/plugin

:exclamation: No tests found!
:information_source:  This is an automatic message


want to add waves token on it

thank you we install exchange but we want to add waves token on it
how we can install waves token on it
specification of waves token are hear
How to add an Asset to external exchange
Hello!
After creating, any Waves based asset becomes automatically available on the Waves DEX. So, you can trade it with any trading pair against any other assets.
If you want to add your Asset to another exchange, you should send a request to add your Asset to the selected exchange. We recommend starting with those exchanges to which the Assets created on the Waves platform have already listed.
Perhaps to add your Asset to a third-party exchange, you may need the following information:

Asset name - (For example, Bitcoin).

Ticker / short name of your Asset - (For example, BTC).

Algorithm - Waves based asset. 4. Number of blocks / block height - http://wavesexplorer.com, "Current height:")

Token supply

Commission - 0.001 Waves.

Block time - 1 min 8. The programming language - Scala.

Type of mining - POS

secp256k1ver - New

Source code - https://github.com/wavesplatform

Explorer - https://wavesexplorer.com

API request with data of your Asset -

http://nodes.wavesnodes.com/transactions/info/Add here Asset ID of your Asset
The trading volume of Asset with Bitcoin (find your asset in the list) - http://dev.pywaves.org/dexbtc The volume of Asset trading with Waves (find your asset in the list) - http://dev.pywaves.org/dexwaves
For more information about your asset, please click on this link - http://dev.pywaves.org/assets (just find your Asset in the list and click on Asset Id).
Previous article: What is an airdrop?

@sofiyaz If you are not good at coding i suggest you stop now. You require alot of knowledge to run a exchange and the information you posted doesnt matter at all.
The exchange is using RPC 1.0 calls. short sum, its what languish the wallet and exchange are talking to eachothers.  This means you have to create your own code with waves API and create a system that handles transactions with tokens. Dont expect anyone to share this kinda of things.
Easy way is to try to find a RPC 1.0 layer waves wallet and code on that, but on my guesses you dont know how to do this and wants anyone else to share this.
You could always contact anyone on a coding website and pay them for coding this kind of things for you, but if you want to use a ETH token instead there is plenty of RPC 1.0 eth wallets.
In comparison (regular ETH commands): https://github.com/ethereum/wiki/wiki/JSON-RPC
(BTC commands): https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
As you see they are 100% diffrent and this is why the exchange only works with a couple of coins.

THANK YOU BUT CAN I DO WITH WAVES FULL NODE AND GUI WALLET MAYBE I WANT TO TRY IT

@sofiyaz Never use GUI wallets to host coin wallets for the exchange on.

OK BUT HOW TO I ADD BITCOIN ON IT

can u tell us tutoreal on it

@sofiyaz
I made a easy guide to follow.
https://www.youtube.com/watch?v=dafESX_CHDs

A


fix: set 644 permissions on output parquet files

Resolves https://github.com/evidence-dev/evidence/issues/2463
Description
Running the following commands:
rm -rf .evidence build && pnpm sources && pnpm build && ls -al build/dat a/needful_things/orders/
Before this fix:
drwxr-xr-x 2 zach zach   4096 Sep  3 13:09 ./
drwxr-xr-x 3 zach zach   4096 Sep  3 13:09 ../
-rw------- 1 zach zach 450914 Sep  3 13:09 orders.parquet
-rw-r--r-- 1 zach zach   1032 Sep  3 13:09 orders.schema.json

After this fix:
drwxr-xr-x 2 zach zach   4096 Sep  3 13:04 ./
drwxr-xr-x 3 zach zach   4096 Sep  3 13:04 ../
-rw-r--r-- 1 zach zach 450914 Sep  3 13:04 orders.parquet
-rw-r--r-- 1 zach zach   1032 Sep  3 13:04 orders.schema.json

Checklist

[ ] For UI or styling changes, I have added a screenshot or gif showing before & after
[ ] I have added a changeset
[ ] I have added to the docs where applicable
[ ] I have added to the VS Code extension where applicable

Changelog


feat: support external types with type widening

fixes #1296
external types are widened to a typealias of Any in the FTL schema, with metadata specifying the external type they will be serialized to/from (standard JSON serialization is used for external types).
can be used in-line/implicitly, e.g.:
package foo

import github.com/external/bar

type FtlType struct {
   Field bar.NonFtlType
}

which becomes an alias with the derived typemapping:
data FtlType {
   Field foo.NonFtlType
}

typealias NonFtlType Any
  +typemap go "github.com/external/bar.Type"

or explicitly, which gives the user an opportunity to define mappings for other runtimes, e.g.:
import github.com/external/bar

type FtlType struct {
   Field AliasedNonFtlType
}

//ftl:typealias
//ftl:typemap kotlin "com.external.bar.NonFTLType"
type NonFtlType bar.NonFtlType

=>
data FtlType {
   Field foo.NonFtlType
}

typealias NonFtlType Any
  +typemap go "github.com/external/bar.Type"
  +typemap kotlin "com.external.bar.NonFTLType"

follow up change will check for naming conflicts in the implicit case

Nice @worstell!
Does this need any integration tests or are the unit tests covering what we need?

there's one integration test! it deploys a verb that uses external types + calls it
i'll actually add another one that uses external types on an ingress request as well


feat(relations): add support for HasOneThrough

This pull request add support for HasOneThrough relationship.
I hope I did it well since I'm not fluent at all with that kind of Laravel relation.
However, it sounds working well into my project ^^'

@warlof the PR looks great thanks!
Question: Do you know what version of Laravel started the support for HasOneThrough? I'm a bit outdated atm. Thanks!

Checking Laravel docs and seems like it was documented since 5.8. I guess this is safe to merge since v9 supports 5.8 & above. Will wait a day incase someone wants to review. Looks good to go for me. Thanks!

I confirm, that kind of relation spawn in Laravel 5.8.
https://github.com/laravel/framework/blob/5.8/src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php

Released on v9.10.0, thanks!

thank you for your amazing factory :)


Implement Data Buckets concept on top of Kamelet

Kamelet introduces types in its definition, defines input/output data types just like DataShape in Syndesis does.
MessageHistory in Camel 3.x is supposed to allow accessing messages that was exchanged prior in the route, which could be used as an alternative to Out Message Capture in Syndesis, which store out message from each step mapped with Step ID, and then following Data Mapper step can retrieve with passing Step ID as a key.
That means we can implement Data Buckets concept in Syndesis on top of plain Camel (+Kamelet). Start from having a PoC.

It would be better to move camel-atlasmap into Apache Camel upstream first (#726), then this topic would be worked mainly on Camel upstream.


Can add  element?

I tried, but it seemed not work:(

@pigpigfour can you please explain? Thanks.

Like if I want to catch the  on Youtube used Highlighter
I found I wouldn’t copy the  element text

2020年10月22日 13:58，GitMurf<EMAIL_ADDRESS>写道：
@pigpigfour https://github.com/pigpigfour can you please explain? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/GitMurf/roam-highlighter/issues/59#issuecomment-714249210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQ6LIVRAX3XDRVFJO6ERSBLSL7CWTANCNFSM4RFICR4Q.


Allow mixed case in pgtle.clientauth_users_to_skip and pgtle.clientauth_databases_to_skip

Issue #, if available: 265
Description of changes: Allow mixed case in pgtle.clientauth_users_to_skip and pgtle.clientauth_databases_to_skip
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Please also remove …th_databases_to_skip from the description of the pr

It's not very clear to me why we need to move the new tests to a separate file.

Do you mind adding your test case and updating the numbers at the top of the file as well: https://github.com/aws/pg_tle/blob/main/test/t/004_pg_tle_clientauth.pl#L24

Do you mind adding your test case and updating the numbers at the top of the file as well: https://github.com/aws/pg_tle/blob/main/test/t/004_pg_tle_clientauth.pl#L24

+1 on this

LGTM


Support for more Altcoin

Please add support for more Altcoin

Golem
Waves
Melon

PIVX (Private Instant Verification)
VTC (Vertcoin)
FTC (FeatherCoin)

+1 for Golem

+1 For Golem.
Please ;-) 👍


Replace AutoLock with std::lock_guard

Per @lgritz observation in PR #670 : in C++11, AutoLock (src/OpenColorIO/Mutex.h) should be replaced with std::lock_guard.

Is this issue still open? PR was merged in master.

@thirdknife This one is already fixed by #832


The AVLTreeDigest.add is dead cycle

T-digest is very good lib for Quantile calculate.
When I use this for version 3.1. I found a important problem.
It make my CPU runing with 100%.
I found the code with this:
`
Thread 21751: (state = IN_JAVA)

com.tdunning.math.stats.AVLTreeDigest.add(double, int, java.util.List) @bci=156, line=84 (Compiled frame; information may be imprecise)
com.tdunning.math.stats.AVLTreeDigest.add(double, int) @bci=7, line=67 (Compiled frame)
com.tdunning.math.stats.AbstractTDigest.add(double) @bci=3, line=154 (Compiled frame)
`

Maybe this has problem.
I'm looking forward to your reply. Please give me a hand. Thanks.

Use the current version of MergingDigest.
On Mon, Dec 23, 2019 at 7:56 AM Leon<EMAIL_ADDRESS>wrote:

T-digest is very good lib for Quantile calculate.
When I use this for version 3.1. I found a important problem.
It make my CPU runing with 100%.
I found the code with this:
`
Thread 21751: (state = IN_JAVA)

com.tdunning.math.stats.AVLTreeDigest.add(double, int,
java.util.List) @bci https://github.com/bci=156, line=84 (Compiled
frame; information may be imprecise)
com.tdunning.math.stats.AVLTreeDigest.add(double, int) @bci
https://github.com/bci=7, line=67 (Compiled frame)
com.tdunning.math.stats.AbstractTDigest.add(double) @bci
https://github.com/bci=3, line=154 (Compiled frame)
`

[image: image]
https://user-images.githubusercontent.com/591191/71367262-7f2fdf80-25df-11ea-9e23-773a7f2b43bd.png
Maybe this has problem.
I'm looking forward to your reply. Please give me a hand. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/issues/137?email_source=notifications&email_token=AAB5E6VNJULTF4BLY4VFIMLQ2DNUNA5CNFSM4J6VSW4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICLL2HA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5E6TEFYIERJBHLNFEZITQ2DNUNANCNFSM4J6VSW4A
.

Use the current version of MergingDigest.
…
On Mon, Dec 23, 2019 at 7:56 AM Leon @.***> wrote: T-digest is very good lib for Quantile calculate. When I use this for version 3.1. I found a important problem. It make my CPU runing with 100%. I found the code with this: Thread 21751: (state = IN_JAVA) - com.tdunning.math.stats.AVLTreeDigest.add(double, int, java.util.List) @bci <https://github.com/bci>=156, line=84 (Compiled frame; information may be imprecise) - com.tdunning.math.stats.AVLTreeDigest.add(double, int) @bci <https://github.com/bci>=7, line=67 (Compiled frame) - com.tdunning.math.stats.AbstractTDigest.add(double) @bci <https://github.com/bci>=3, line=154 (Compiled frame) [image: image] https://user-images.githubusercontent.com/591191/71367262-7f2fdf80-25df-11ea-9e23-773a7f2b43bd.png Maybe this has problem. I'm looking forward to your reply. Please give me a hand. Thanks. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#137?email_source=notifications&email_token=AAB5E6VNJULTF4BLY4VFIMLQ2DNUNA5CNFSM4J6VSW4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICLL2HA>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB5E6TEFYIERJBHLNFEZITQ2DNUNANCNFSM4J6VSW4A .

Thansks. I'll try. :)

Leaving this open to investigate later.
This is not considered a blocker for the 3.3 release.


[Feature Request] scripted_upsert not supported

[ ] Feature Request :  Scripted_upsert functionality is not supported for the moment

Feature description
This issue is related with https://github.com/elastic/elasticsearch-hadoop/issues/538, the connector does not support for the moment scripted_upsert functionality
This functionality also requieres defining an empty upsert body

Hi @lucebert
Is there any way I can use scripted_upsert to avoid document missing exception?
I am facing a problem that sometimes Spark streaming update (use inline script) will get document missing exception. I read some article then people said I should use upsert to replace update method. Is there any way I can use scripted_upsert to avoid document missing exception? Or I should try to ignore the exception by using custom error handler.
Than you very much.

Hi @PolarBearAndrew
You should use scripted_upsert but this is not available in Elasticsearch-hadoop until they merge this PR.
There is a workaround solution which is to use the upsert  query.
you have to put this parameter :
"es.write.operation" -> "upsert"
"es.update.script.params" -> <<my params>> // include all fields to update
"es.update.script.inline" -> <<my script>> //use params

This will work but the downside is that the query generated will have the full document in params and in the upsert, which is less performant.

Hi @lucebert
Thank you very much 🙏, I will try another way to complete my work.
I hope your PR can be merge!


Allow headers to define sections

For larger sites, whole navigation table could take much more than a single screen. It would be very nice if using headers at least for top-level sections is allowed. So, e.g.
# section 1
    - subsection 1
        - [article 1](...)
        - [article 2](...)
    - [article 3](...)
# section 2
...

Ideal scenario would be to allow freely changing between headers and lists.

This makes sense to me. Just seems painful to implement


Move dash tabs tests

@imechoim this type throw exception on closed part if was been extended in open part
https://github.com/datalens-tech/datalens-ui/blob/14735e8562f37d6e1c820460084559f6f3b17cb7/tests/types/config/index.ts#L6
it is expected behaviour?

Yes. This is expected behaviour. Just add new ids in closed part.


Date validation failed with Timezone (related to DayJS issue)

Package version
2.1.0
Describe the bug
When validating a date with a format containing the symbol Z (see https://day.js.org/docs/en/display/format#list-of-all-available-formats) it will fail.
This issue seems to be related on DayJS latest version. Here some tickets open on their github :

https://github.com/iamkun/dayjs/issues/2730
https://github.com/iamkun/dayjs/issues/2724

Here an example to test :
  vine.object({
    startDateTime: vine
      .date({
        formats: ['YYYY-MM-DD[T]HH:mmZ'],
      })
  })

input : 	"startDateTime": "2024-09-11T14:20+0200"
I wish you all a lovely day :)
Reproduction repo
No response

dayjs/plugin/timezone not found in issue. what to do?

Seems like a lot of issues coming from DayJS. Maybe, we should consider moving a more stable (yet small) library for dates parsing


Loki setup for skaffold & json logger configuration

@marcinwadon Good question. I will look into the easiest way of doing this. Possibly we could add a flag like CL_ENABLE_JSON_LOGGING that defaults to false but we could set it to true on internal nodes.


Profile resource doc really needs to state defaults

This doc:
http://docs.projectcalico.org/v2.1/reference/calicoctl/resources/profile
...has a column for defaults, but no actual values.  It should at least say that the default for an empty profile is allow-all.

Especially as of this PR: https://github.com/projectcalico/calico/pull/2366
I don't think there's anything to do here - none of the fields actually have defaults, and most of them are deprecated.


what's the theme on the promotinal gifs? :DD

If you talk about the gifs on the README :
https://marketplace.visualstudio.com/items?itemName=DaltonMenezes.aura-theme 😋

thank you very very mucho 🫀


Unable to join any new live shares

Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows]: Windows 10
Live Share Extension Version: 1.0.5043
Target Platform or Language [e.g. Node.js]: Any
Scenario:
My first live share join was successful. However I can no longer join any new live shares. VS Code does not allow me to enter a new url, and opening the live share in a browser opens vscode.dev without giving any option to open in the desktop application.
Attempting to use the join functionality results in the following error "Joining collaboration session: CollaborationSessionNoLongerActive". Again, the original live share I joined is no longer active, but I cannot get VS Code to use any other url. There is no place for me to even enter a new url. It just tries to restart the old live share.
Multiple restarts of VS Code and of my machine have not solved this issue.
My coworkers all experience the same issue, yet when googling the error message 0 results came back. We are all confused as to why others wouldn't be experiencing the same problem.
Any help would be appreciated.
Steps to Reproduce:

Connect to a valid active live share
End live share
Attempt to connect to a different live share
logs.zip

I found that VS Code invisibly and automatically acquired the sharing URL from my clipboard. When I copied random non-URL text, the Live Share extension again prompted me to enter a URL. When I copied a new and valid sharing URL, Live Share automatically connected to it without the need (or option) to paste it anywhere.

This issue should now be resolved, as long as you update to the latest Live Share extension release. Please re-open this bug if you're still running into issues. Thanks!


Update gitignore and remove untracked files

I updated the gitignore to be based on other Godot gitignores. It's useful to keep this in sync even if not everything is directly relevant. For example, opening the project in a C#-enabled version of Godot will generate the .mono/ folder even if the project doesn't use C# anywhere.
Also, I ran a formatting script, there were some missing newlines, so I added them.

Hey! thanks a lot! Its an great to get your help!


Console Warning - Running Vue in development mode

Hello,
I am using the latest version of the package but I am seeing a warning in console about running Vue in dev mode:
You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html
Can the package be update to use production version?
Thanks,

Sorry about that, I haven't worked on it for a while. Will publish in a few minutes

Done ! You can update to 1.6.1


chore(clustering): cleanup redundant checkers

Summary
some logic in checkers is made redundant by the fact the same fields exist in removed_fields. This commit removes the redundant logic
Checklist

[x] The Pull Request has tests (removed_fields already covered by tests)
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[x] (no) There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference
KAG-4457

@samugi I don't see config.response_streaming in removed fields, is it there?

@samugi I don't see config.response_streaming in removed fields, is it there?

Oh, got it:
https://github.com/Kong/kong/blob/master/kong/clustering/compat/removed_fields.lua#L129

Removing cherry-pick label as already cherry-picked.


fix onWillDispatch asymmetry

This PR come coupled with two questions for the core team. The first is CommandRegistry::onWillDispatch is undocumented, so does that mean it is either not a part of the public API, or soon to be deprecated? If so then please ignore this proposal. The second question, assuming this method is meant to be public, is doesn't it make sense to have a matching ::onDidDispatch? I have a particular use case for this event. I'm currently writing a terminal emulator for Atom, and in it I'm defining a special atom builtin. It is essentially a small wrapper around atom.commands.dispatch that allows a user to send commands directly to atom via the command line. It works great, except that after the command has executed, my input element loses focus. This hook would allow me to do something like:
atom.commands.onDidDispatch -> document.querySelector('#quantum-shell-input').focus()

to return focus to my package after the command has executed.

This package you're working on sounds really cool, especially the atom built-in.

The first is CommandRegistry::onWillDispatch is undocumented, so does that mean it is either not a part of the public API, or soon to be deprecated?

It's not part of the public API, but it's not going anywhere anytime soon. I'd be down to add another method if absolutely needed, but I have some questions about your use-case.
When you dispatch a command, what is causing the terminal to lose focus? Is some package handling the command and stealing it? Since commands are dispatched synchronously, have you tried just focusing your view immediately after dispatching the command like this?
# in the terminal code...
atom.commands.dispatch(target, "command-from-the-terminal")
terminalElement.focus()

If the command had some async handler that steals focus then obviously that doesn't work, but adding the onDidDispatch variant seems like it wouldn't help that much either.

After playing with some commands what I've found is that most of them do not steal focus. A good example is atom window:toggle-full-screen. However there were two common commands that were causing issues, namely atom tree-view:toggle and atom settings-view:open. I took your advice and simply refocused my input element after dispatching the commands. atom tree-view:toggle now works as expected, however atom settings-view:open seemed to take a little longer to execute and did steal focus once the view had fully loaded. Correct me if I'm wrong here (I'm still trying to wrap my head around asynchrounous logic) but it sounds like what you're saying is I need to wait for the actual command to execute, not just be dispatched from atom.commands. If that is the case, is there an easy way to do that? All I can think to do right now is something like:
# in the terminal code...
atom.commands.dispatch(target, "command-from-the-terminal")
setTimeout(terminalElement.focus, 50)

This seems less than elegant though, and is obviously still not guaranteed to work. (How long is too long to wait?)

How about listening for the blur event and stealing focus back? You may need to do that in a timeout with a zero delay, but not totally sure.

Of course how do you distinguish a genuine blur from an accidental one.

Yes, it would seem that any solution beyond simply waiting for some period of time would add an unacceptable level of complexity. The setTimeout solution may not be pretty, but it does work, and there's a lot to be said for that. I've tested as many commands as I can think of at a 100ms timeout, and it's not even noticeable at the human level and provides the desired behavior in all cases. I am satisfied with this solution, so this PR can be safely closed as far as I'm concerned. I would like to thank you @nathansobo, you've been very friendly and helpful to this newbie and I am very excited to publish this new feature in the next release of quantum-shell!

Good luck! It sounds like an exciting package.


Move sdk libraries inside source directory

Currently the libraries of the game sdk are located inside the Binaries folder of the plugin.
This is problematic since the Binaries folder is considered to be safe to delete by many [1] [2] because binary files in there should be able to regenerate and tools like ue4cli will delete the Binaries folder when cleaning.
While I know that putting those files inside Binaries is used in discord's code primer,
the now depreceated discord-rpc library also moved to the "Source/ThirdParty/.../" directory (see their Build.cs file and its latest commit) since having them inside Binaries caused problems in shipping builds.
Since the ExtractedExample image wasn't valid anymore I removed it and added 2 empty marker files where one should place the files from the zip instead.

@FlorianFreudiger Thank you for this change. I've merged them to the repository.


Not working with nunjucks

I found the following issue:
Tried to use this edition with https://github.com/pattern-lab/patternengine-node-nunjucks but only thing I get from the pattern is [Object promise] instead of the actual html of the pattern. And the pattern isn't even using nunjucks, the code is just something like <button>Button</button> but the file has .njk extension. If I change it to mustache it works fine.
Also just to mention when running patternlab:serve i get the message that both mustache and nunjucks are ready to go. So I guess that the engine is ok.
Also I used nunjucks some time ago with Gulp edition and everything worked fine.
Haven't tested this with other engines, so maybe those have problems also.
Anyway let me know if you need more info about this.

Not sure, but I don't know if any of the @pattern-lab scoped packages will work with this edition until it's upgraded to v3. For example, I use patternengine-node-handlebars v1.0.3 successfully, not v2.0.0-alpha.2. For Nunjucks, I'd try this version and see if it works. The primary pattern-lab dev has said that v3 makes extensive use of promises whereas v2 is largely synchronous.

Oh, ok. I will try that. Thanks.

Installing the nunjucks engine version 0.1.2 did the trick. Thanks @Josh68

Good to hear I actually gave some valuable advice ;)
On Mon, Apr 9, 2018 at 12:47 AM, Ivan Dorić<EMAIL_ADDRESS>wrote:

Installing the nunjucks engine version 0.1.2 did the trick. Thanks @Josh68
https://github.com/Josh68
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Comcast/patternlab-edition-node-webpack/issues/19#issuecomment-379664610,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvFdyplm1_KdhAdMifpoySr07I08alnks5tmxIQgaJpZM4TLBZf
.


[Suggestion] Use a libre/open source forge instead of GitHub

Because Free Software Needs Free Tools and for not reinforcing monopolies because even the most conservative capitalist view is that monopolies harm users.
Monopolies at the level of GitHub for software forges and oligopoly at the level of Microsoft.
It's also for the sake of avoiding the worst actors which Microsoft is a proven one whether it's for tax evasion, anti competitive practices, hindrance to the libre and open source software movements, massive privacy breaching, and even corruption for large deals with education sector in France[fr].
More reading: https://en.wikipedia.org/wiki/Criticism_of_Microsoft
In short and simple: the digital world would be better if GitHub and Microsoft products would be less used in favor of libre ones hosted by respectable actors.
There are a lot of public Gitlab or Gitea instances and before exploring for a concrete one, what is the team take on the issue?
GitHub doesn't drive more contributions in itself, the project isn't significantly more discoverable because it's on GitHub. However account creation laziness is a thing that has a real impact which must be addressed. This is why a number of Gitlab and Gitea instances support auth via GitHub.
I think Gitlab or Gitea are good enough to not hinder contributions compared to GitHub and that any difference isn't really noticeable in absolute terms and even more so relatively when comparing to the tradeoff

Also: super exited to learn that overgrowth is libre! Thanks a lot! :heart:  A lot of games could do the same since keeping the assets proprietary doesn't change the business model

I do personally share some of your concerns regarding Github and its ownership structure, and how that will affect the free open source world in the long run. In our case, our company is otherwise set up for using Github, and transferring the upstream repo to another platform would add complications to our routines. Right now in practice i don't see it being an issue, yet, and if there are signs that it might become one, it'll still be possible to transfer to a different site.
I'm not closing the door to this idea forever, but for the forseeable future, we're staying here for practical reasons.
These kinds of topics do get brought up internally however, and we do care.

 It was fun to make it Libre!
From experience, very many games are sadly blocked from open sourcing their engines in this vein due to third party middlewares! Something i've become very aware of when working on making Overgrowth OSS ready. This is especially true for titles built in engines like Unity and Unreal, not due to the engines themselves, but how the surrounding infrastructure is set up for using asset-packs on different stores, where code and assets rarely allow redistribution in source form, and their code quickly gets woven into the core of the games.

Lugaru (the predecessor to this game) is primarily hosted on GitLab.com. If we decide to move to GitLab in the future, we can certainly do that. Other platforms don't really have a good CI/CD story, which makes them hard to consider for our needs.


Prerequisites

[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.

Criteria

[X] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
[X] English interface (or at least English documentation)
[X] Latest stable version
[X] Full version (i.e. not a trial version)
[ ] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)

Name
scriptkit
Description
An open-source kit to optimize your developer workflow using typescript
Homepage
https://www.scriptkit.com/
Download Link(s)
https://github.com/johnlindquist/kitapp/releases/
Some Indication of Popularity/Repute
3.5k github stars https://github.com/johnlindquist/kit

Upon further inspection, the installation process that scriptkit performs on first startup is pretty convoluted and litters files everywhere. Probably not a good fit for scoop.


Correct compats, test latest versions

This PR:

Reverts #700 (cc @szy21)
Upgrades the (compatible dependencies) dependencies
Runs a vanilla (low resolution perf target) in the test env to exercise our the latest deps (closes #703)

bors r+

bors r+


Remove workaround for line prefix

There is a workaround for this bug https://github.com/puppetlabs/beaker/pull/1010

Fixed in #26


TextField display [object Event]

Describe the bug
When <TextField.Input onChange={setValue}/> is passed TextInput displays [object Event] inside it.
function ControlledExample() {
	const [value, setValue] = createSignal();
	return (
		<>
			<TextField value={value()} onChange={setValue}>
				<TextField.Input onChange={setValue}/>
			</TextField>

Your favorite fruit is: {value()}.

		</>
	);
}

Expected behavior
It should ignore passed onChange and display proper value.
Screenshots

TextFieldContext should be exported. so we can overwrite TextFieldInput component if required.

setValue should only be called from the onChange of TextField and not TextField.Input.
The root onChange recieves a value with kobalte handling whereas the one from the input is the native event and should only be used for advanced custom handling.

Can we all export for example TextFieldContext  ?

Can we export all context for example TextFieldContext ?

That's planned #321, will need time to design the API, no ETA.


Move "utils" bindings to cxx crate

Just a bit of churn. Some functions turned out to be harder to move, so I split those into separate commits to make the review easier.
Reviews are welcome! I'll merge this in three days if no issues are raised.

Coverage decreased (-0.5%) to 58.043% when pulling c3f79bb62daff6f472951255e20f5dba7d93e5b7 on feature/move-utils-to-cxx into f6eb0742bbf26e2523fa9b2d9dd72bbf957fcb06 on master.

Thanks for the reviews! I squashed the changes and will merge once the CI is done.


[FEATURE REQUEST] Is it possible to add more model options for BizyAirSiliconCloudLLMAPI nodes, qwen2.5-7b vs. 72b

of course, it will be updated soon

It will be resolved in https://github.com/siliconflow/BizyAir/pull/135

https://github.com/siliconflow/BizyAir/pull/135 has been merged, all the LLM models of SiliconCloud can be used in BizyAir


ARIA-324 Refactor ctx access

Our previous use of "." to delimit nested dict keys was wrong (keys
could have a ".") and inflexible. The new implementation uses subsequent
args to move into the dict.
The same format can now be used to access object attributes.
This commit also changes how to support setting values: we must now use
"=" as the penultimate argument with the new value following.
Also fixed: callables will now "grab" the number of args they need
instead of all remaining args, making it possible to do further
inspection on the returned value from the callable. To allow for this,
kwargs are now expected as the first arg rather than the last.
Furthmore, this commit fixes a bad null check in the ctx client, and
also allows it to retrieve Unicode data.

Can one of the admins verify this patch?

Hey guys, I suggest going over the complex use cases in the Clearwater example.
Basically all the changes in the PR were inspired by those real-world needs of ctx.

Can one of the admins verify this patch?


Change in requirements file

To properly use gunicorn gevent server in QRadar application, new version of ssl or pyopenssl must be used.
Therefore, cryptography version required in qpylib is too old, so a new one should be used.
As dependencies, new versions of pycryptodome, Flask, MarkupSage, Werkzeug, Jinja2, itsdangerous are needed as well.
all test passed, lint result 100%

Hi, thanks for your request. Unfortunately we can't accept it. qpylib is tied to the package versions in the QRadar app base image which in turn are constrained by IBM open source approval.


Aliasing not working with graphql-shield permissions middleware and customFieldResolver

Bug report

[X] I have checked other issues to make sure this is not a duplicate.

Describe the bug
When using aliasing in my graphQL query, the aliased field is returned as null. If I do return the field + its aliased value, the aliased value (as well as the non-aliased field value) are returned.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

This is my GraphQL Schema.

type Query {
  book: Book!
}

type Book {
  id: ID!
  name: String!
  content: String!
  similarBooks: [Book!]!
}

This is the invoked query that doesn't work

Query A):
book {
  id
  otherBooks: similarBooks {
    id
  }
}

It works with:
Query B):
book {
  id
  similarBooks {
    id
  }
}

or
Query C):
book {
  id
  similarBooks {
    id
  }
  otherBooks: similarBooks {
    id
  }
}

I use these permissions

const permissions = shield({
  Query: allow,
})

This is the error I see

Actual behavior
In Query A), I am getting null for otherBooks.
Expected behavior
I expected to see a value for otherBooks (assuming the data is set this way). Expected query results are observed for queries B) and C)
Additional context
Here is my graphQL server setup:
import { ApolloServer } from 'apollo-server-lambda';
import { applyMiddleware } from 'graphql-middleware';
import { makeExecutableSchema } from 'graphql-tools';

const schemaWoMiddleware = makeExecutableSchema({
  typeDefs,
  resolvers,
});

const middleWare = applyMiddleware(
  schemaWoMiddleware,
  permissions,
);

const resolverFragmentReplacements = middleWare.fragmentReplacements;
const schema = middleWare.schema;

...

    const server = new ApolloServer({
      // ref: https://github.com/apollographql/apollo-server/issues/865
      fieldResolver: customFieldResolver,
      schema,
      tracing: false,
      cacheControl: false,
    });

    return server.createHandler();

The customFieldResolver is a direct copy of https://github.com/akadop/graphql-yoga/blob/ee0c03fa8d0e9578f4589e19da6beff1d8112a67/src/customFieldResolver.ts
I use those versions:
    "apollo-server-lambda": "2.1.0",
    "graphql": "0.13.2",
    "graphql-middleware": "1.7.3",
    "graphql-playground-middleware-lambda": "1.7.3",
    "graphql-shield": "3.2.3",
    "graphql-tag": "2.9.2",
    "graphql-tools": "3.1.1",

If I remove the permissions in the middleWare, aliasing works (and my customFieldResolver is invoked). With permissions defined in middleWare, the customFieldResolver is never invoked.

Hey @morgothulhu 👋,
Thanks for reporting this. I am not entirely sure but it seems like this might be a graphql-middleware bug. I'll dig deeper into the problem later this week and let you know about the progress. Is this in any way blocking for your progress?
Let me know! 🙂

@maticzav - all good. Fortunately, this is not blocking yet - so any time this week will be perfect. Thanks for the great work with graphql-shield - loving it!

@maticzav any path forward with this? Thx in advance!

any progress on this?

@dude-awesome could you compose a small reproduction CodeSandbox? I can work on this issue much sooner if I have a reproduction I can work on right away.


code-fold: true is not working while using the include-code-files quarto filter

While this filter does include codes from an External file, code-fold: true or code-summary: "some text" is not working for that code chunk (that includes the source code). A quick reproducible example as follows,
test.py
# code from test.py
for name in ["Sam", "Jake"]:
    print(f"Hello {name}!")

test.qmd
---
title: "Including Code"
format:
  html:
    code-fold: true
    code-summary: "Python Code"
jupyter: python3
filters:
  - include-code-files
---

## Python

```{.python include="test.py"}
```

```{python}
print("Hello World")
```

output

I am using Quarto version,
$ quarto --version
1.2.235

I am also actually having the issue #2 , so I have copied the include-code-files folder and put it under a _extension directory to use it.
Thanks.

I am not aware of code-fold nor code-summary variables in pandoc. I do not see nor of them in the basic pandoc html template.
It may be something specific to quarto.
Did some of you have any idea where these two variables are defined and used (@shafayetShafee, @SamEdwardes or @jjallaire) so that we try to find a solution to the exposed trouble?

OK that seem definitively be something specific to quarto the use is defined in quarto's doc only.
Any one of you have an idea how this is implemented in quarto? Did they use a specific pandoc template for instance?

It's implemented as a Lua filter that is built in to Quarto's pipeline: https://github.com/quarto-dev/quarto-cli/blob/main/src/resources/filters/quarto-post/foldcode.lua

Hi @shafayetShafee sorry that it is not working. I would recommend that you use the include code extension that is officially supported the quarto team. I created this extension before that one existed. I am going to propose that we archive this extension in favour of https://github.com/quarto-ext/include-code-files.


Remove CODEOWNERS and mirror-rolling-to-master.

They are both outdated and both no longer serving their intended purpose.

https://github.com/Mergifyio backport jazzy humble


fix(bug): allow "complex" filter with update statement

I ran into an issue where the following query failed:
db(:table)
|> filter(:col, in: [1, 2, 3])
|> update(other_col: "new value")

It seems like Moebius.Query.update was doing some re-arranging of parameters and placeholders but did not take into account the in (or other compound constructs).  I removed that code and tweaked the remaining code to appropriately start the parameter numbers at the (seemingly) correct value.
The existing tests pass with some re-work.  To ensure that my test assumptions were correct, I also added a couple of assertions to ensure the parameter list is in the correct order.   While my changes do not adversely affect my code, I'm more than happy to consider a different approach if this is not sufficient.
Thanks for providing the library; it's proving extremely useful.

Thank you @bunnylushington! Can you review the failing tests around code formatting?

No problem at all.  Sorry I missed that before creating the PR.


Use 402 status code and update tests.

Use status code 402 when a file requires payment.
From Mozilla:

The HTTP 402 Payment Required is a nonstandard response status code that is reserved for future use. This status code was created to enable digital cash or (micro) payment systems and would indicate that the requested content is not available until the client makes a payment.
Sometimes, this status code indicates that the request cannot be processed until the client makes a payment. However, no standard use convention exists and different entities use it in different contexts.

We actually thought about this, but then elected not to do it. If I recall, our thinking was that there isn't any HTTP client software out there that will actually do anything useful in response to a 402. In particular, there isn't any software that will prompt the user to pay in response to a 402, and no way to deliver along with a 402 instructions for how to make the payment. In addition, some software, like HTTP clients, might misbehave if they get an unexpected status code. I'd definitely be open for returning 402s if it actually did something useful, but at the moment I don't think it's a benefit.

That makes sense.
In the future, it might be worth revisiting if the WebLN spec or browser extensions like Joule standardize 402 error handling.


Remove deprecated (and in some cases broken) init actions

This change removes the obsolete init actions for Tez, Datalab, Jupyter, Jupyter2, and Jupyter SparkMonitor

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun


Error: died with <Signals.SIGKILL: 9

Hello Xiaofei,
I could not go through the haphic pipeline with this command haphic pipeline scaffolds.ref.fa HiC.filtered.bam 20 --RE GATC,GANTC,CTNAG,TTAA --correct_nrounds 2 --remove_allelic_links 4 --threads 20 --processes 8. I encountered this error message:
Traceback (most recent call last):
  File "/home/li/bioinfo/HapHiC/haphic", line 96, in <module>
    subprocess.run(commands, check=True)
  File "/home/li/miniforge3/envs/haphic/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/home/li/bioinfo/HapHiC/scripts/HapHiC_pipeline.py', 'scaffolds.ref.fa', 'HiC.filtered.bam', '20', '--RE', 'GATC,GANTC,CTNAG,TTAA', '--correct_nrounds', '2', '--remove_allelic_links', '4', '--threads', '20', '--processes', '8']' died with <Signals.SIGKILL: 9>.

Could you please give me any suggestions?
Thank you for your time.
Zhen

Hi Zhen,
This error message indicates that your task was killed. The reason for this termination is uncertain, as it could be done by anyone with the authority (kill -9 <pid>). If the task was not killed by yourself or a superuser, then it is possible that the task exceeded the memory limit. If you are using a job scheduling system such as PBS or SLURM, you can trace the maximum memory usage by using the corresponding command (e.g., tracejob <jobid> for PBS and sacct -j <jobid> --long for SLURM).
If it's indeed a memory issue, and the pipeline was terminated during the execution of step 3 (the 03.sort directory was created but 04.build was not), you may consider reducing the number of processes (e.g., use --processes 4). Alternatively, you could run the pipeline on a server with higher memory capacity.
Best regards,
Xiaofei

Hello Xiaofei,
Thank you for your quick reply.
It seems to be a memory issue. But I only have one directory (01.cluster). I will try to reduce the process number and rerun it.
All the best,
Zhen

Thank you for your information!


flutter_plugin_tools format stuck waiting.

Steps to Reproduce
run:
flutter packages pub global run flutter_plugin_tools format
Output
Formatting all .dart files...
Waiting for another flutter command to release the startup lock...
Flutter Doctor
flutter doctor
[✓] Flutter (on Mac OS X 10.12.6 16G29, locale en-US, channel master)
• Flutter at /Users/arthurthompson/opt/flutter
• Framework revision d29c4a3c97 (68 minutes ago), 2017-09-19 13:07:57 -0700
• Engine revision dd1e0b59ec
• Tools Dart version 1.25.0-dev.11.0
[✓] Android toolchain - develop for Android devices (Android SDK 26.0.1)
• Android SDK at /Users/arthurthompson/opt/android/sdk
• Platform android-26, build-tools 26.0.1
• ANDROID_HOME = /Users/arthurthompson/opt/android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
[✓] iOS toolchain - develop for iOS devices (Xcode 8.3.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 8.3.3, Build version 8E3004b
• ios-deploy 1.9.2
• CocoaPods version 1.2.1
[✓] Android Studio
• Android Studio at /Applications/Android Studio 3.0 Preview.app/Contents
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
[✓] Android Studio (version 2.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)
[✓] IntelliJ IDEA Ultimate Edition (version 2017.2.4)
• Flutter plugin version 17.0
• Dart plugin version 172.4155.35
[✓] Connected devices
• Android SDK built for x86 64 • emulator-5554 • android-x64 • Android 6.0 (API 23) (emulator)

Nvm this was user error, I did not have all the necessary tools on my path.

Which tool was missing? I got the same issue.


[Bug] Sagemaker instance does not stop automatically

Describe the bug
Idle Sagemaker Notebook instances do not stop after specified time.
SWB runs autostop.py script to automatically stop Sagemaker Notebook instance. The script is used by on-start lifecycle rule of the instance CFN template. According to LifecycleConfigOnStart logs, some packages are missing and autostop script doesn’t work.
To Reproduce
Steps to reproduce the behavior:

Make sure AutoStopIdleTimeInMinutes parameter in workspace type config is set to a required time (30 minutes in our case)
Create a new workspace with Sagemaker notebook instance
Leave the instance idle for the time specified (AutoStopIdleTimeInMinutes )
After the specified time see that the instance is not stopped

Expected behavior
Idle Sagemaker Notebook instance automatically stops after specified time.
Screenshots

Versions (please complete the following information):

Release Version installed v5.0.0

Additional context
Add any other context about the problem here.

Hi, please check the latest release v5.2.5 for the fix to this issue.

Hi! I also want to note that you may need to stop and start any affected instances after upgrade and deploying SWB v5.2.5.
If this fixes your issue, please go ahead and close this issue. I am going to mark as closing-soon-if-no-response so we will close in about 7 days if we do not hear that this did not resolve the issue.
Thank you for the report!

Hi Marianna,
Thank you. I am going to migrate to v5.2.5 tomorrow. If everything goes
well, I'll close the ticket soon.
On Tue, Dec 13, 2022 at 7:55 AM Marianna Ghirardelli <
@.***> wrote:

Hi! I also want to note that you may need to stop and start any affected
instances after upgrade and deploying SWB v5.2.5.
If this fixes your issue, please go ahead and close this issue. I am going
to mark as closing-soon-if-no-response so we will close in about 7 days if
we do not hear that this did not resolve the issue.
Thank you for the report!
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/service-workbench-on-aws/issues/1076#issuecomment-1347314897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKETLSEQCFIMAF5HX4CAT3WM6GN3ANCNFSM6AAAAAASWEAJP4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Closing this issue since the fix was merged, please feel free to reopen the issue if it persists on your end.