Feature Request: Anonymous Polls

The syntax could look something like
/anonymous-poll Do you believe in God?
Yes
No

The output should be like a normal poll that displays the number of votes without any names.

This is a reasonable feature request, but we probably should postpone working on it until we get more customer feedback that this will be useful.  In my limited experience people are pretty comfortable with attaching their name to a vote on the poll, and being able to see who's voting for what will usually lead to follow-up conversations that can help decide whatever the poll is about.

This is a reasonable feature request, but we probably should postpone working on it until we get more customer feedback that this will be useful.  In my limited experience people are pretty comfortable with attaching their name to a vote on the poll, and being able to see who's voting for what will usually lead to follow-up conversations that can help decide whatever the poll is about.

I think another reason to have a poll widget that doesn't display names is for polls where a very large number of responses is expected.
The "lots of responses" use case could diverge from the anonymous polls use case if we allow names to be shown on hover.

At my university, we are trialing using this in courses (specifically, one realm per course).  A common request is more anonymous feedback mechanisms, so that students can participate without feeling so vulnerable.  This anonymous poll feature was specifically requested!
Another possibility for this use case is "visible only to moderator and above".

I'd appreciate this as well. We sometimes have polls where attaching your name is likely to skew the result in one direction or another.

Adding my support for anonymous polls. In addition to the in-class use case mentioned by rkdarst above, which I share, there are many issues around compensation and workers' rights where we don't want to be asking people to answer them non-anonymously, and responding non-anonymously could change how many people respond to the poll and what responses they give. (If you want specific use cases feel free to reach out to me by email.)

I second that request.

I am surprised the request of an anonymous polls option was not satisfied after so much time. We all know that non anonymous answers can be biased. Students commenting on courses, workers assessing their managers, both cases in which there are incentives to be not sincere.
I ask for this option again with hope! Thanks

Also wishing it existed!


First Stable Version

First Stable Version
This is the first stable version of the software. It contains all the design components and styles.

I think this looks good to me. So, as administrator, I will approve and pass the PR. 👌


JS: add query: js/useless-defensive-code

This PR introduces js/useless-defensive-code as a recommendation query. The query is based on syntactic patterns, and type inference for a variable in each pattern.
Defensive code is typically a condition that prevents null or undefined values from causing a crash later on. Defensive code is useless when the condition evaluates to a single value for all execution paths. In that case, the condition might as well be removed. I welcome a discussion of the patterns.
The end result is that:

Some alerts from js/trivial-conditional and js/comparison-between-incompatible-types are whitelisted
The above whitelisted alerts are flagged by js/useless-defensive-code
Additional, more advanced, unnecessary defensive code variants are also flagged by js/useless-defensive-code

The most important consequence of this is that the remaining alerts from js/trivial-conditional and js/comparison-between-incompatible-types now are much more severe on average. A secondary consequence is that alerts caused by type inference improvements will be easier to judge the value of.
Please note that the query deliberately treats cases like o === undefined || o.p and o === undefined && o.p identically, for the sake of simplicity. It is the responsibility of another query to flag the definite error in the latter case.
Bullet 1 and 2 above may cause a special kind of wobbliness: if we gain precision because of a simpler program or because of an improved analysis implementation, then additional alerts may be flagged by js/useless-defensive-code, while a more complex program may change those alerts to js/trivial-conditional. C.f. another evaluation.
An oldish evaluation shows that performance is fine and an interesting amount of result changes, with a net additional 69 alerts that the programmer will be presented for by default. A smaller, but more recent, evaluation on top of the current master shows that this still scales.

While we're on the subject, am I the only one who thinks the word "useless" sounds rude? I liked the previously suggested "unnecessary defensive programming".
Do I understand it correctly that this will not introduce any new alerts, but merely reclassify existing ones into this less severe query? It's not quite clear from bullet 3 if this means new alerts.

The phrasing is inherited from js/trivial-conditional aka UselessConditional.ql which has @name Useless conditional. We should change both or none.

Brand new alerts will be added because of some additional constant folding steps in this query. Consider the simple case of:
    if (u !== undefined) {
        u.p;
    }

This is obviously not flagged by js/heterogeneous-comparison because the comparison is homogeneous, and it is not flagged by js/trivial-conditional because we do not have a type inference step for the result of a comparison.
Another example is:
    typeof f === "function" && f();

Maybe we should let js/trivial-conditional know that null coerces to false, but that is the only low hanging fruit I have seen.

Ping @Semmle/doc on whether "useless" is considered rude; as a non-native speaker I don't feel qualified to judge.

Overall, the large number of syntactic checks seems quite cumbersome.

Agreed, but I believe we must use syntactic checks to identify the relevant programming patterns.
This could be simplified a bit if we added constant folding for boolean results to the type inference, but we decided that it may not be worth it for just this query and js/trivial-conditional. Such a constant folding would also mean that js/trivial-conditional needed a whitelist for the js/heterogenous-comparison.

and I'm not confident I fully understand all of the patterns being checked for.

I have added source code examples to the docstrings.

Rebased on current master to make the tests for js/trivial-conditional work.

Asked @semmledocs-ac for help as I'm not a native speaker either. Please let me know when this is ready for a doc review. Thanks.

@mc-semmle I have addressed the "is useless" comments, and this PR is ready for doc review.

esben-semmle - doc review completed. This LGTM, I have just made a few minor comments / suggestions. Feel free to ignore them if you don't agree.

Thank you @mc-semmle
The query description is now "Defensive code that guards against a situation that never happens is not needed." And the query name is "Unneeded defensive code"

Thank you for the updates @esben-semmle - LGTM 👍

Conflicts.

Conflicts resolved.


Update Contributing guide with guidelines on uploading files

Old issue was #11

since people are always in personal contact with us organizers we tell them directly what to do


suggestion

it's such a common use case to generate json or other structured response, perhaps it's better to instead wrap this into a library? albeit just one function call but then it contains more logic than the infamous left pad :)

Thanks for the suggestion. I will do up a library after I finish up on Functions and Agents for this repo:)

@tanchongmin  I would also suggest for the output format to use JSON schema instead, at the expense of more tokens but gpt based llms seem to be very familiar with the output

with strict_text (Strict JSON v2), we can now get nested outputs!

Nested output formats of multiple lists and dictionaries are now supported with StrictJSON v2.2.0. You can even do type checking for various output fields! Check it out!


Migrate from analytics.js to gtag.js

Use gtag.js instead of analytics.js snippet, as it is now the preferred option.
Google Analytics docs suggest using window['ga-disable-GA_TRACKING_ID'] = true; as a way to disable tracking, so that's added as well. :)
Here's the link to the docs: https://developers.google.com/analytics/devguides/collection/gtagjs/user-opt-out
Cheers!

as it is now the preferred option

@mladenilic could you provide official source that supports this statement?

@DirtyF there's no official statement that I'm aware of, it's just that when you create the Google Analytics account, the tracking code provided is the new gtag.js one.
https://s3.amazonaws.com/drei.one-public/gtag.png


http_error on every API call

Every API call I make gives me RouteError (http_error). After a bit of debugging I found out that  the actual exception is #<Netrc::Error: unexpected EOF>. Tried re-generating API tokens but error is still there. Version 1.1.1.

\cc @baptistejamin

Hello @Fodoj
I digged into your issue and I tried with the 1.1.1 release, using ruby v2.3.0 with the following sample:
require 'crisp-api'

client = Crisp::Client.new

client.authenticate("IDENTIFIER", "KEY")

client.website.list_conversations("WEBSITE_ID", 1)

list = client.website.list_conversations("-JzqEmX56venQuQw4YV8", 1)

puts(list)

I didnt have any issue using this sample. Could you try and let me know?

@baptistejamin that's exactly what I tried to do :( Could it be that my token or Crisp account has some issues? We are still on trial, but I could generate tokens just  fine. Ruby 2.5 here.

Is this using development? production?
Do you have a proxy? VPN? Firewall?
A token should return a completely different error.

No proxy, no firewall. I did not  find any info in Crisp docs regarding development or production environments, it seems like I can only use tokens against my Crisp website.

My question was more if you are running the code on a Heroku or on your own computer.

My personal laptop
Am 28. März 2019, 18:48 +0100 schrieb Baptiste Jamin<EMAIL_ADDRESS>
My question was more if you are running the code on a Heroku or on your own computer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I just tried generating new token and running code sample you provided above, same error. This is blocking as from switching to Crisp, as only step left is integration with out main backend :(

What's your server's outbound IP address? We can check our edges logs.

@valeriansaliou <IP_ADDRESS>. That's my house IP, from ISP.

Thanks. When did you last try a request from the library?

I do have ipv6 address too. Last attempt was around 2 hours ago

What's your IPv6 address so that I check?

Won't be able to provide it till the evening sadly. I will also try to do simple curl query tonight to check if it's network issue.

I tried with curl as well as Crisp Python SDK. Both  attempts returned new error:
>>> client.website.list_conversations(website_id, 0)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/fodoj/.local/lib/python2.7/site-packages/crisp_api/resources/website.py", line 61, in list_conversations
    return self.parent.get(self.__url_website(website_id, "/conversations/%d" % page_number))
  File "/home/fodoj/.local/lib/python2.7/site-packages/crisp_api/__init__.py", line 55, in get
    return self.__do_request("GET", resource, query=query)
  File "/home/fodoj/.local/lib/python2.7/site-packages/crisp_api/__init__.py", line 92, in __do_request
    raise RouteError(result["reason"] if ("reason" in result) else "error")
crisp_api.errors.route.RouteError: invalid_session

Why's session invalid?

As for IPs:
IPv6: 2001:a61:480f:2201:c9d3:549:37f6:ecf1
IPv4: <IP_ADDRESS>

Do you happen to run a script, somewhere, that creates a lot of sessions? We use a sliding window mechanism to invalidate old sessions, if you create too many of them. We allow up to 15 simultaneous sessions tokens to be active at any given time.

@valeriansaliou funny thing: I just created a new token pair and I finally have a working API call via python sdk. But Ruby SDK still returns http_error with exactly same token and same API call.

Perhaps try yourself? This is my actual credentials. As our Crisp setup is not live yet, I dont care if tokens are published here, I will regenerate them later:
CRISP = Crisp::Client.new
CRISP.authenticate("a5305c79-5e6d-4afa-a549-6ca61d9ca03c","625bc42632c7c5dc36b1354dbd875f5d70c77ebc4501df9c12bd64d764f32561")
CRISP.website.list_conversations("03014c76-9a44-4192-8fea-2333bb8407f6", 0)

I've just tried your code, and... it succeeded, even with your token.

I am out of ideas then. I just run:
2.5.0 :001 > require 'crisp-api'
 => true
2.5.0 :002 > CRISP = Crisp::Client.new
 => #<Crisp::Client:0x00000000028b4a28 @auth={}, @bucket=#<Crisp::BucketResource:0x00000000028b45a0 @parent=#<Crisp::Client:0x00000000028b4a28 ...>>, @website=#<Crisp::WebsiteResource:0x00000000028b4550 @parent=#<Crisp::Client:0x00000000028b4a28 ...>>>
2.5.0 :003 > CRISP.authenticate("a5305c79-5e6d-4afa-a549-6ca61d9ca03c","625bc42632c7c5dc36b1354dbd875f5d70c77ebc4501df9c12bd64d764f32561")
 => "625bc42632c7c5dc36b1354dbd875f5d70c77ebc4501df9c12bd64d764f32561"
2.5.0 :004 > CRISP.website.list_conversations("03014c76-9a44-4192-8fea-2333bb8407f6", 0)
Traceback (most recent call last):
        5: from /home/fodoj/.rvm/rubies/ruby-2.5.0/bin/irb:11:in `<main>'
        4: from (irb):4
        3: from /home/fodoj/.rvm/gems/ruby-2.5.0/gems/crisp-api-1.1.1/lib/resources/website.rb:85:in `list_conversations'
        2: from /home/fodoj/.rvm/gems/ruby-2.5.0/gems/crisp-api-1.1.1/lib/crisp-api.rb:50:in `get'
        1: from /home/fodoj/.rvm/gems/ruby-2.5.0/gems/crisp-api-1.1.1/lib/crisp-api.rb:114:in `_do_request'
RouteError (http_error)
2.5.0 :005 >

With Python it works.

Ok, I just tried to run exactly same code on an EC2 instance and it worked. Only difference I can think of is lack of IPv6 on EC2 instance.

Can you try again now with the Ruby API? I've lowered our bot protection system security level.

@valeriansaliou same same. It really seems some lower level network quirk. Perhaps Ruby lib used for requests doesnt handle ipv6 well or something similar..

I guess, but it's all out of our control there. We use the rest-client Gem for HTTP calls.

So also nothing in the logs?

Yes, nothing. The request is blocked before it hits our edges.

Note that I'm also running IPv6, and I can hit our APIs w/o any issue either w/ my token or your token:
⋊> ~/C/ruby-crisp-api on master ◦ ruby --version                                                                               08:52:34
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]

gem list | grep rest
rest-client (2.0.2)

This gets even better: it only happens under my personal system user. Running same code as root works fine.

I think we can conclude that your system forbids you to access the IPv6 networking stack at the kernel level 😉

I figured what the issue was but I am hesitent to share it here. But I think it is still a bug in the library. Can we have a short 5-10min call so that I explain it to you?

You can email<EMAIL_ADDRESS>and I'll have a review later on in the day / tomorrow.

I've deleted your comment giving away your API tokens, just to be sure nothing bad can happen.

So, root cause is the bug in RestClient: https://github.com/rest-client/rest-client/issues/524.
Would you be open to switching to HTTParty? :)

I think we can wait for rest-client version 2.1 in which this seems to have been fixed. I want to stick to this library.

Up to you of course, but it seems like 2.1 is not coming any time soon, it's stuck as rc since 2017:

Anyways, many thanks for prompt support. For time being I will update my .netrc file when working on Crips-related project. :)

I am facing the exact same issue. what is required in the .netrc file?


Vagrantfile: unset locales in the virtual machine

Setting locale fails when ssh-ing into the virtual machine. This unsets all the
locales to avoid annoying warnings.
It is up to user to install locales packages if she likes.
Solves one of the warnings reported in #102.
Signed-off-by: Michele Di Giorgio<EMAIL_ADDRESS>

Can we add to this PR another set of patches to address Basil's comments?
I've collected the requirements in #117

:+1: going to do it

@derkling I pushed a new commit with what you've asked. When you have time could you please have a look at it?
For the Android APIs either we explicitly set which one to install in the filter option (we can only use numbers that are going to change) or we install everything (as it is currently).


Help with modal dialog

I have built an external package that can introduce form in a modal. see the image bellow.
its not really matter for now how i did it, ill release it once its working, or even make a pull request.
Save action seems to be working good.
The problem is that after save the form redirect to the list, I want to intercept on save action in the client side in prevent that, is it possible?
in the client on after save i want to call my function, is it possible?
Thanks

@vlados you example it is above.
https://github.com/avifatal/laravel-admin-modal

How works?


Init with new cli in js project

I am working on a standard react project in JS.
I was able to initialize everything fine with the previous CLI, then I could use the Manual Install of the components and pull out the typescript.
With the new CLI, it appears to be searching for tsconfig.
Does the new CLI only init in a typescript environment?
Also missing the manual install from docs now is a bummer as stated in #642

https://github.com/shadcn/ui/issues/642#issuecomment-1604074845

Does the new CLI only init in a typescript environment?

Yes, you need a TypeScript project to use the cli since the components are written in TS.
p.s. : The manual installation is back. https://github.com/shadcn/ui/issues/642#issuecomment-1604074845

With manual install back, this can probably be closed,


Fix status code for response of Post and Delete requests

Added types PostResponder and DeleteResponder implementing Responder interface to write responses for post and delete requests respectively
Updated ServeHTTP method to create instances of Responder on the basis of request methods
For details refer https://github.com/gofr-dev/gofr/issues/446

@ssshekhu53 - It is not advisable to create new duplicate responders just for the sake of adding statusCodes in response.
We would need to look into a better approach to resolve this.

@ssshekhu53 - It is not advisable to create new duplicate responders just for the sake of adding statusCodes in response. We would need to look into a better approach to resolve this.

Have removed the new responders and added a field method in responder struct. Factory function for responder has been updated too to accept ResponseWriter and method in the parameter.  HTTPStatusFromRequestMethod will deduce the status code on the basis of http method for success cases.


Support connecting to the MQTT Broker over TLS

@palto42 This branch is now releases as ghcr.io/kbialek/deye-inverter-mqtt:2023.05.4-beta-1. Let's test it


Deleting a question that has show/hide rules attached to it will not cleanup related questions

Description
If you delete a question that has show/hide rules attached to it, the hidden questions keep the attribute and stay hidden forever.
Steps to reproduce

For Question 1, add a form element, e.g. Radio buttons.
Create 2 options: Yes and No.
For Question 2, add another form element, e.g. Short Answer.
Go back to Question 1 and Add a rule.
If option selected is "No", show Question 2.
Save. Test. Everything is good.
Go back to edit and remove Question 1 completely.
Test the form again, and Question 2 is no longer visible which is confusing to the user.

Expected behaviour
If a question is related to another question via conditional logic, and that "parent" question is deleted, the related question should be "freed" from the condition and be always visible.
Screenshots or videos

Additional context
Reported in Freshdesk Ticket 17383. Thanks @connorscarolyns for finding the issue!

Related to #3627


Fix iOS CI which once in a while fails (flaky), while it works well locally

Lower priority, will work on it later

Lower priority, will work on it later


Make logging on by default

And other minor cleanup
Followup for #2479.

Is there any reason we shouldn't put this in KoreBuild itself? It's used in multiple places now, if I'm not mistaken.

I am trying to turn logging on by default here since this was the first time this was asked for but I don't mind putting it in KoreBuild. Let's figure out a good mechanism for this first because I don't really like the current way it's implemented.

My concern remains the same. This relies on 'internal' API in KoreBuild. We have tentative plans to change this part of code in 2.2.0-mq, and this may break. We make no promised about targets or properties that are "internal" i.e. things that start with an underscore.

I hate seeing a test failed only to realize that I didn't set the environment variable. I could put it in my profile, but that doesn't help when I'm ssh'd into a CI agent for example.
@natemcmaster I don't think this is the first 'internal' API from one aspnet repo being called from another. Couldn't we just update Kestrel when if and when we make the 2.2.0-mq changes in KoreBuild?

After talking to @natemcmaster, it seems this only works if you run the tests as part of a build and not if you run from VS or "dotnet test". That's not ideal and this PR is pretty old, so I'm closing.


Note that<EMAIL_ADDRESS>supports async/await.

Somewhere there's a line stating only one minifier "as of this writing" supports current features. Need to re-evaluate/rewrite.

Using uglify-es in v3 so this can be closed for now.


Add more IHV data collection

Added more data to the log.
This is Marvell device specific change.

Thanks!


slow response time for remote operations

lxc list for a remote is far slower than docker ps between the same client and host. lxc list executed locally is fast.
on OSX client, remote ubuntu:
time lxc list
real    0m0.806s

Executed on lxd host
time lxc list
real    0m0.137s

docker ps on OSX client, remote ubuntu:
time docker ps
real    0m0.036s

(docker does not use TLS encryption in this setup).

It's a known Go issue, nothing to do with LXD.
Go 1.5 is supposed to finally have the fix for this which will save 700ms on the network case and end up to a similar execution time as local.

Is there an unencrypted, insecure way of using lxd?

Nothing that LXD itself exposes, nor are we planning on doing so. You can however use socat or other tools to forward /var/lib/lxd/unix.socket to a tcp socket. Though you'll have to forward it back to a unix socket on the client side as the lxc command line tool doesn't support unencrypted transport over tcp, nor do we intend to add this.


Give the hash.sh input for password

Is your feature request related to a problem? Please describe.
When I'm generating passwords, I can't see what I'm pasting into the hash.sh utility (it doesn't show stars or anything).
Describe the solution you'd like
Let me provide the password as an command line input argument (i.e. ./hash.sh -p thepassword) and output only the generated hash.
Describe alternatives you've considered
Additional context

[Triage] Closing because resolved.


Assets are not cached on command anymore

#861mue3y2

Task linked: CU-861mue3y2 Fix: Asset are cached after every command


cockroachdb-architecture.html 404s

Issue Description
The first link when googling cockroachdb architecture 404s: https://www.cockroachlabs.com/docs/stable/cockroachdb-architecture.html

Suggested Resolution

@benesch I thought this would get caught by the redirect for some reason. How should we handle removing a page and redirecting it to something within a subdirectory? redirect_from: ../cockroachdb-architecture.html?

Yep! Though I'd recommend just using an "absolute" path (i.e., where a leading / means cockroachlabs.com/docs/) rather than ... This should do it:
key: cockroachdb-architecture.html
redirect_from: [index.html, /cockroachdb-architecture.html]


Migrate to CircleCI

Changes from previous setup:

Switches from "exclude" approach to explicitly listing each version tested.
Replaces multiple bespoke gemfiles with CircleCI parameters.
Only tests ruby from latest version available as a CircleCI Orb, and which doesn't crash when installing nokogiri (2.5.x, released 4-5 years ago)

Let me know whether dropping tests for Ruby < 2.5 is acceptable! 🙏
We can probably make it work by manually installing it instead of using the orbs, but as those versions are quite old, I'm not sure if it's worth the extra effort?

I think it would be great to support all the version of Ruby/Rails we did with Travis. Could you please give it a try? If it's a couple of hours of effort then I think it would be well worth it.

@tomek-ac As the CI is currently not working, I'll merge this first and then maybe we can quickly chat in today's meeting about prioritizing the work required to have CI support for old ruby versions?


Add olre rpubs tutorial

The rpubs inbostats tutorial about observation level random effects

@hansvancalster @ThierryO and I decided to close this PR as it is not releveant anymore.
Reason: this tutorial is already online. Who searches for it, will find it.


Replace older mod.rs style with newer .rs style

I think, it is better to use the newer style, since it is mostly pretty annoying when having many mod.rs files open in the editor.
Also the older style makes it sometimes difficult, when searching a module file. At the current state of the project, this might not be such an issue, but when the project grows, it will be better to use the newer style.

@Sharktheone I have not heard of one of the styles superseding the other.  The way I've seen the two styles used depends upon how complex the module is.  Do you have a link that further discusses what you have in mind?

It is mentioned in the Rust-book.

I'll take a look and refresh my memory. It's been a little while since I read that.

@Sharktheone it seems you are correct.  I vaguely remember reading that section, but it seems I forgot it.  Most of us, including myself, are at a fairly early stage in learning Rust.
Can you bring your PR up to date with latest main?

Github does't let me update the branch, i reopen this

I reopened this as #107 I didn't thinked about this, that i shouldn't push something like this to main 🤦


updated the code to new version of aiohttp, fixed some typos and deco…

I wanted to run the examples but could not...

@Arfey can you please update this PR?

@jettify done!


fix(Masthead): keep focus in sub menus

Related Ticket(s)
#3663
Description
Added a sentinel in order to keep focus on the currently selected sub menu

@RaphaelAmadeu it works nicely for the second level menu items! Nice! One thing I noticed is we get the issue happening again if we go to the third level of menu items


Receive backpressure support

Hi,
Is is possible for the application to indicate that it isn't ready to receive any more messages at this time. so the library will stop recv()-ing data from the client, until the application indicates it is ready to receive more?
Suppose that I am putting received data into a queue and I have another thread that is processing from the queue, and it is resource-intensive. I can't let the queue grow without bounds if data is being received faster than it is being processed. I need to pause receiving data until the queue has drained sufficiently.

For compatibility with TLS you cannot stop receiving without also stopping writing, TLS cannot receive without also sending.
If you want to stop both, that could be added in uSockets like us_socket_throttle but you could probably just use us_poll_change on the socket. If you look in uSockets it should be reasonably simple to add.
 I can't help right now but that's the idea

This is tracked in uSockets repo, closing this as duplicate. Feel free to PR something at uSockets.


Create electron app for hyperdrive-daemon

As discussed in the calls with hyperdivision, we want to prototype a little electron menu bar app that hosts https://github.com/andrewosh/hyperdrive-daemon, and uses https://github.com/andrewosh/hyperdrive-daemon-client to connect to it.
This will help us get familiar with the project, and serve as a simple one-click installer for the daemon.
In my mind this would be a small hack project, that goes over 3-5 days, and can be done after the Hypergraph Desktop demo on Tuesday March 31st.
Some features to include:

monitoring
start / stop
installer
auto updates

cc @jameslibscie

Sounds good! @juliangruber :)


deps: swap react-lottie for lottie-react

Replaced in https://github.com/bcgov/nr-silva-webapp/pull/16.


Updated email content

Hi @adamgajzlerowicz, the app is in English at this moment. So I cannot let this patch through.


JMeter Service: Allow dynamic loading of extensions

Follow up of #2552
In PR #2825 @grabnerandi has implemented variant 1 of #2552, where he included an extension statically in the Docker Image.
The scope of this issue is to make this dynamic, e.g., by including it in the configuration repo. Original text below.

Another option could be to allow our Keptn users to upload their extensions to the Keptn Project Configuration Repo. I would suggest to upload them on the master/main branch into a directory called jmeter/lib/ext. The Keptn JMeter Service can then pull all extensions before launching JMeter and copy them into the lib/ext directory.
This solution would however require the Keptn Configuration API to provide an option to get the list of all files in a directory which is currently not possible. Without that capability its not possible to know which files have been uploaded

JMeter has been moved out of this repo


ci: Fix go-vet errors

Azure CI is failing due to go-vet errors of "composite literal uses
unkeyed fields". Use keyed fields in structs to fix the issue.
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>

Coverage remained the same at 65.235% when pulling 2cd138fdb836670edb485ac6df909bc70e041d6f on amshinde:fix-go-vet-errors into aea3a893f2156e2e802b6eaa8675fbe94c274b7d on containers:master.

Coverage remained the same at 65.235% when pulling 80986741d4e92c8f74c1802914d7fbed90fcf708 on amshinde:fix-go-vet-errors into aea3a893f2156e2e802b6eaa8675fbe94c274b7d on containers:master.

Can you add the Fixes #417 to the commit which is the issue reporting this errors?

Coverage remained the same at 65.235% when pulling 8cce97a3c4f01327db0c540bad39a96a96f35c9c on amshinde:fix-go-vet-errors into aea3a893f2156e2e802b6eaa8675fbe94c274b7d on containers:master.

Coverage remained the same at 65.235% when pulling a13eb2c52fcd62213c0256df6566d66a00f9c2e0 on amshinde:fix-go-vet-errors into aea3a893f2156e2e802b6eaa8675fbe94c274b7d on containers:master.

Coverage remained the same at 65.235% when pulling 3ae5af698bfaa93f3e2dfe8ddb9135801103720d on amshinde:fix-go-vet-errors into aea3a893f2156e2e802b6eaa8675fbe94c274b7d on containers:master.

lgtm


Ensure that restrictions on Barrier instructions in WebGPU are enforced

Wording of these restrictions was clarified in gpuweb/spirv-execution-env@131313e. Need to confirm that the implementation matches the new text.

OpControlBarrier* restrictions:

The Execution scope operand must be Workgroup
The Memory scope operand must be Workgroup
The Semantics operand:
Memory Semantics Order bits: Must set the AcquireRelease bit, and no other bits.
Memory Semantics Storage Class bits: Must set the WorkgroupMemory bit, and no
other bits.
Must not set any Memory Semantics Propagation bits.

Note: To ensure propagation of Workgroup writes to readers,
individual accesses of Workgroup memory should use availability
and visibility semantics:
MakePointerAvailableKHR with Workgroup scope on writes,
MakePointerVisibleKHR with Workgroup scope on reads,
and NonPrivatePointerKHR on both.

OpMemoryBarrier* restrictions:

The Memory  scope operand must be Workgroup
The Semantics operand:
Must not set any Memory Semantics Order bits.
Memory Semantics Storage Class bits: Must set the ImageMemory bit, and no other
bits.
Must not set any Memory Semantics Propagation bits.

Note: OpMemoryBarrier is only used to order reads and writes by the same
invocation to the same locations in image memory.

This is actually resolved by #2775 . I thought there was more work needed, but that is in a different issue.


Updates to the contributing file

Connects to #265

updated contributing doc to include instructions for adding props & vars tables
updated the instructions for adding new styles.

or.. maybe we could make components just for these instances that have the headers already setup?

Im just going to update this with the markup that they can copy and paste for now. Im not sure how I would go about making this into a component.

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


lfs: 1.3.0 -> 1.3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Canop/lfs/releases.
meta.description for lfs is: "Get information on your mounted disks"
meta.homepage for lfs is: "https://github.com/Canop/lfs"
meta.changelog for lfs is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1/bin/lfs passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 1.3.1 with grep in /nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1
found 1.3.1 in filename of file in /nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
lfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lfs https://github.com/r-ryantm/nixpkgs/archive/71bc8dd292fd583f621a4d2f1f4027b17d0523b4.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1
ls -la /nix/store/sxr3sbfzxljsrhjy6f4v9d695ikwbpja-lfs-1.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

lfs

Maintainer pings
cc @k0ral for testing.

Change looks good to me

upgrade termimad for better table fitting (especially when some mount points have long paths)


warning on npm install

hi
at npm install I receive some warning messages:
Cloning into '/ors-app'...
npm WARN deprecated<EMAIL_ADDRESS>This module is now under the @mapbox namespace: install @mapbox/leaflet-omnivore instead
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>Module has been renamed to @turf/points-within-polygon
npm WARN deprecated<EMAIL_ADDRESS>Module deprecated in favor of @turf/length
npm WARN deprecated<EMAIL_ADDRESS>Module has been renamed to @turf/boolean-point-in-polygon
npm WARN deprecated<EMAIL_ADDRESS>This module is now under the @mapbox namespace: install @mapbox/corslite instead
npm WARN deprecated<EMAIL_ADDRESS>This module has moved: please install @mapbox/togeojson instead
npm WARN deprecated<EMAIL_ADDRESS>Use topojson-client, topojson-server or topojson-simplify directly.
npm WARN deprecated<EMAIL_ADDRESS>This module is now under the @mapbox namespace: install @mapbox/polyline instead
npm WARN deprecated<EMAIL_ADDRESS>This module is now under the @mapbox namespace: install @mapbox/sexagesimal instead
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

Yes, that is "normal"
It would take too much time to fix this, as it might introduce breaking changes and we don't have the resources to do this :/
We are currently also working on a new client in VueJs that will replace this one in the long run.
But it will still need some time to be completed (couple of months 5+)
https://openrouteservice.org/map/#/
Best regards

I got it, then probably it is best to ignore them until they create blocking problems
and waiting for a new, is there already a repository / branch open for new app?
vuejs lib & vue-cli might be a good choice

There is a repository but this is currently only available internally within HeiGIT.
We will open source this at some point, but not before the official release.
We are using vuetify for this as well as vue2leaflet and a lot of other stuff...


Fixed #35980 -- Updated setuptools and project name.

Trac ticket number

ticket-35980
Branch description
Updates the minimum version of setuptool to v69.3.0 and updates the project name in the metadata to be lowercase.
This is because we will need to comply with PEP 625 to continue uploading to PyPI in the future.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] I have attached screenshots in both light and dark modes for any UI changes.

Hey @nessita 👋🏻 I don't follow... I've only pinned to specify the minimum version that works for this new requirement to conform to PEP 625, but with the unbounded maximum it will use the latest available.

Hey @nessita 👋🏻 I don't follow... I've only pinned to specify the minimum version that works for this new requirement to conform to PEP 625, but with the unbounded maximum it will use the latest available.

Sorry, I did not ask a very good question, my bad.
My question is whether there is a specific need to pin to the proposed version or we could pin to the latest released (75.6.0).

Hey @ngnpope, following the conversations in this PR's ticket and in the referenced tickets in setuptools, I think the rename for the project name should be reverted. I think it's fine to just upgrade setuptools version and have the branch from Baptiste (https://github.com/django/djangoproject.com/pull/1801).
Will mark the ticket as "patch needs improvement", please unset the flag once the project name restore is pushed. Thanks!


Fix build failure due to patch conflict

Description
This PR is a continuation of https://github.com/opensearch-project/k-NN/pull/1833 to fix build failure when patch is applied more than once.
The previous PR resolved an issue for manual build where it uses git am and the Cmake system skips applying patches by comparing patch id.  However the build script which runs in CI build system still fails because it uses git apply which does not commit the patch and we cannot use patch-id to determine if patches are already applied or not.
Therefore introduced a new parameter, build.lib.apply_patches to disable patching for the second run of :cmakeJniLib task inside build script.
Related Issues
https://github.com/opensearch-project/k-NN/issues/1842

Check List

[X] New functionality includes testing.
[X] New functionality has been documented.
[X] API changes companion pull request created.
[X] Commits are signed per the DCO using --signoff.
[X] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

BWC test is failing because OS distribution does not have knn 2.16 which will be fixed once this PR is merged.
The alternative is making the build script to use git am by setting git user.name and user.email. This approach will provide more control when setting user.name and user.email is not desired.


WebGL on composer.space context could not be created on old devices and freeze on mobile

App Commit e2cde42
runtime.js:3139 THREE.WebGLRenderer: A WebGL context could not be created. Reason:  Could not create a WebGL context, VENDOR = 0x8086, DEVICE = 0x0046, GL_VENDOR = Google Inc. (Intel), GL_RENDERER = ANGLE (Intel, Mesa Intel(R) HD Graphics (ILK), OpenGL 2.1 Mesa 24.2.6), GL_VERSION = 24.2.6, Sandboxed = no, Optimus = yes, AMD switchable = no, Reset notification strategy = 0x8252, ErrorMessage = BindToCurrentSequence failed: .
 Reason:  Failed to create a WebGL2 context.
 Device info, os, browser, etc. Reproduction steps at minimum. This above isn't enough information to take any action on.

On mobile chrome, background animation freeze ui, and user input email not functioning.
Please disable animation on mobile devices.

@drunkod could you provide some more details? Device info, os, browser, etc. Reproduction steps at minimum. This above isn't enough information to take any action

From dev tools chrome https://developer.chrome.com/docs/devtools/recorder
Recording 01.12.2024 at 12_04_28.JSON
on.
js.tar.gz


Update version to v1.18.8

Changeset only contains the version bump:
$ glol -1
1dc117914 2024-03-17 22:27:10 -0500  (HEAD -> version_bump_v1.18.8, origin/version_bump_v1.18.8<EMAIL_ADDRESS>Update version to v1.18.8
$ git diff v1.18..HEAD | grep -vE "^ |^@@ |^--- |^\+\+\+ |^index |^diff |^-( \")?(solana|agave).*1.18.7|^\+( \")?(solana|agave).*1.18.8|^-version|^\+version"
$

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

Project coverage is 81.6%. Comparing base (6c4fb98) to head (1dc1179).

Additional details and impacted files
@@           Coverage Diff           @@
##            v1.18     #285   +/-   ##
=======================================
  Coverage    81.6%    81.6%
=======================================
  Files         827      827
  Lines      224515   224515
=======================================
+ Hits       183297   183328   +31
+ Misses      41218    41187   -31


Hook up shibboleth in the UI

Support for shibboleth authentication through the UI. The configuration is already in place, we just need to check which authentication strategy is currently enabled and show the appropriate form.

Assigning to myself for implementation

Setting this to high priority as we will start to use this on our QA servers soon

Coverage remained the same at 100.0% when pulling 728c76c4f399ba654ca5fe2c3d777ff8509b7b7b on Coenego:issue-128-shibboleth into 6df786cf5bd4d95c9e323586208dce3bfba9f55e on CUL-DigitalServices:master.

Coverage remained the same at 100.0% when pulling 1f5702ef3f66c04e63404896dd2378b959bcd905 on Coenego:issue-128-shibboleth into 6df786cf5bd4d95c9e323586208dce3bfba9f55e on CUL-DigitalServices:master.

Assigning to @bp323 for review

Coverage remained the same at 100.0% when pulling fedc9a9ac9fa25023bf9508f694529de4a26a507 on Coenego:issue-128-shibboleth into 469646eb63b8a5911dfc8def86c277b53bc61850 on CUL-DigitalServices:master.

Verified and merged


[cocoon scheduler] Add GitHub PushEvent trigger support

https://github.com/flutter/cocoon/pull/1109 added webhook scheduling based on pull requests being closed + merged. This captures 99.9% of commits added to flutter repos.
However, release channels are pushed to based on the release candidate branches.
For now, these release channel pushes will need to use the cron based method until the PushEvent is added to package:github and implemented by the cocoon scheduler.

\cc @christopherfujino


Auto comment on opened PR and merged or closed PR

I'll create a workflow that will auto comment on an opened PR and will also auto comment if the PR is merged or if the PR is closed. This will be helpful for the user to navigate further.
This will also make the work of PA easy.

please assign this issue to me under gssoc

Hi @MohanRamSridhar,
Thank you for taking the initiative on this! I have assigned this issue to you under GSSOC. It's great to connect and collaborate with you on creating a workflow to auto-comment on opened, merged, or closed PRs. This will certainly enhance the user experience and streamline the process for project maintainers.
If you need any assistance or have any questions along the way, feel free to reach out. Looking forward to seeing your contributions!
Best regards,
Sanika
[https://www.linkedin.com/in/sanika-chavan-52457b236]


fix the wrong logic in VMStatus::status_code()

fix the wrong logic in VMStatus::status_code()

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
unit test case is attached

@tnowacki How about we temporarily comment out the status_type check in VMStatus::status_code()?

Thanks!


Mantra MFS100 does not work on Android 12 (API 31) and up

When attempting to connect to the scanner on these devices, an error is logged from MFS100 line 693 in the Mantra SDK:
uk.ac.lshtm.keppel.android: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.

It looks like the Mantra SDK (or at least the version we're using) does not support API 31+.

I just cross-checked this on Android 14 / Google Pixel 7a.
Keppel v0.3 Seems to work fine as far as I can tell just from capturing fingerprint template.

What I did

plugged mantra in to phone via USB-C adapter

Opened an ODK form and captured data from Mantra

What I didn’t do

test coherence of data

Ah that makes sense because 0.3 targeted an older version of Android (29). That means for the next release, we should either integrate the new Mantra SDK or drop support for the MFS100. The former is obviously the better option!


bugfix: ignore validation of ArgvInput

Q
A

Bugfix
yes

Description

Ignores the validation of ArgvInput while detecting the --container option.
Caveat
This will only work if the --container option is being passed before the commands name or right after the command name.
If the command has arguments, the --container option must be preceding the commands very first argument.
OK
$ laminas --container=<path> <command> [<argument>]
$ laminas <command> --container=<path> [<argument>]

NOK
$ laminas <command> <argument> --container=<path>

fixes #74

#75 would always detect the --container option, no matter where it is positioned.


Test hangs in verifier

This test hangs for no reason: https://github.com/dblock/alexa-app/blob/test-hangs/test/test_alexa_verifier_middleware_hangs.js, the middleware never fires on('end', function() { }), not sure what's going on.

@mreinstein you might be able to explain this one, I'm probably missing something obvious

So ... we need a body parser after the middleware. Does this mean https://github.com/alexa-js/alexa-app/pull/155?

the alexa-verifier-middleware already effectively acts like a JSON body parser. see: https://github.com/alexa-js/alexa-verifier-middleware/blob/master/index.js#L31
I think the logic should be:
if(checkCert) {
  install middleware
} else {
  install regular json body parser
}

the if clause is already implemented. just need the else

Ok, cool, updated.
I am also not moving body-parser into dependencies just like we do with express. I assume this is correct?

I am also not moving body-parser

if the code is using body-parser why would it not be a dependency?

We only use it in the express scenario, but you're right.


Cannot sync two AEM 6.4 instances

Hi guys,
I've been trying to sync two AEM systems using Grabbit and everything seems to be installed properly and active in the bundles on both systems. I can succesfully trigger a job, but after I check /CRX/DE, the content is not synced. Here is my info and what I am trying to do.
What version of AEM are you running?
AEM 6.4.1 with Grabbit 7.1.5
How do you produce the issue?
I installed  Grabbit 7.1.5 on both machines and I configured the following config.json on the server:
{
    "serverUsername" : "admin",
    "serverPassword" : "admin",
    "serverHost" : "test-server",
    "serverScheme" : "https",
    "serverPort" : "443",
    "batchSize" : 150,
    "deltaContent" : false,
    "pathConfigurations" :  [
        {
            "path" : "/etc/designs/test-server/clienlibs/test",
            "batchSize" : 50
        }
    ]
}

I run the following command on the same server where the config.json is, and I succesfully trigger a job:
curl -v -X PUT --header 'Content-Type: text/plain' --data-binary @/mnt/crx/author/grabbit/config.json -u admin:admin http://test-client:4502/grabbit/job
* About to connect() to test-client port 4502 (#0)
*   Trying <IP_ADDRESS>...
* Connected to test-client (<IP_ADDRESS>) port 4502 (#0)
* Server auth using Basic with user 'admin'
> PUT /grabbit/job HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.29.0
> Host: test-client:4502
> Accept: */*
> Content-Type: text/plain
> Content-Length: 421
>
* upload completely sent off: 421 out of 421 bytes
< HTTP/1.1 200 OK
< Date: Wed, 17 Apr 2019 16:24:00 GMT
< X-Content-Type-Options: nosniff
< Set-Cookie: cq-authoring-mode=TOUCH;Path=/;Expires=Wed, 24-Apr-2019 16:24:00 GMT;Max-Age=604800
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Content-Type: application/json
< GRABBIT_TRANSACTION_ID:<PHONE_NUMBER>045048571
< Content-Length: 21
<
* Connection #0 to host test-client left intact

This is what the test-client reports after receiving the config.json:
17.04.2019 11:54:08.481 *INFO* [<IP_ADDRESS> [1555516448434] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.batch.ClientBatchJob Kicked off job with ID :<PHONE_NUMBER>766088911
17.04.2019 11:54:08.481 *INFO* [<IP_ADDRESS> [1555516448434] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Jobs started : [6678845723766088911]
17.04.2019 11:54:08.481 *INFO* [<IP_ADDRESS> [1555516448434] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Transaction started<PHONE_NUMBER>747771147
17.04.2019 11:54:08.486 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Starting job : JobExecution: id=6678845723766088911, version=1, startTime=Wed Apr 17 11:54:08 EDT 2019, endTime=null, lastUpdated=Wed Apr 17 11:54:08 EDT 2019, status=STARTED, exitStatus=exitCode=UNKNOWN;exitDescription=, job=[JobInstance: id=11, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=4251115638747771147, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1555516448467, serverUsername=admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}]

17.04.2019 11:54:08.508 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet WorkflowConfig :
17.04.2019 11:54:08.508 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet Nothing to process...
17.04.2019 11:54:08.528 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.steps.workspace.DeleteBeforeWriteDecider Will retain nodes under job path for<PHONE_NUMBER>766088911...
17.04.2019 11:55:08.645 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Cleanup : JobExecution: id=6678845723766088911, version=1, startTime=Wed Apr 17 11:54:08 EDT 2019, endTime=Wed Apr 17 11:55:08 EDT 2019, lastUpdated=Wed Apr 17 11:54:08 EDT 2019, status=FAILED, exitStatus=exitCode=FAILED;exitDescription=, job=[JobInstance: id=11, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=4251115638747771147, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1555516448467, serverUsername=admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}] . Job Complete. Releasing session, and input stream
17.04.2019 11:55:08.649 *INFO* [clientJobLauncherTaskExecutor-1] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Grab from test-server for Current Path /etc/designs/test-server/clienlibs/test took : 60164 milliseconds

17.04.2019 12:00:42.695 *INFO* [<IP_ADDRESS> [1555516842644] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.batch.ClientBatchJob Kicked off job with ID :<PHONE_NUMBER>779498180
17.04.2019 12:00:42.695 *INFO* [<IP_ADDRESS> [1555516842644] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Jobs started : [6569392098779498180]
17.04.2019 12:00:42.695 *INFO* [<IP_ADDRESS> [1555516842644] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Transaction started<PHONE_NUMBER>447537021
17.04.2019 12:00:42.701 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Starting job : JobExecution: id=6569392098779498180, version=1, startTime=Wed Apr 17 12:00:42 EDT 2019, endTime=null, lastUpdated=Wed Apr 17 12:00:42 EDT 2019, status=STARTED, exitStatus=exitCode=UNKNOWN;exitDescription=, job=[JobInstance: id=12, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=6876129364447537021, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1555516842680, serverUsername=aem_admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}]

17.04.2019 12:00:42.724 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet WorkflowConfig :
17.04.2019 12:00:42.724 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet Nothing to process...
17.04.2019 12:00:42.744 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.steps.workspace.DeleteBeforeWriteDecider Will retain nodes under job path for<PHONE_NUMBER>779498180...
17.04.2019 12:01:42.808 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Cleanup : JobExecution: id=6569392098779498180, version=1, startTime=Wed Apr 17 12:00:42 EDT 2019, endTime=Wed Apr 17 12:01:42 EDT 2019, lastUpdated=Wed Apr 17 12:00:42 EDT 2019, status=FAILED, exitStatus=exitCode=FAILED;exitDescription=, job=[JobInstance: id=12, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=6876129364447537021, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1555516842680, serverUsername=aem_admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}] . Job Complete. Releasing session, and input stream
17.04.2019 12:01:42.812 *INFO* [clientJobLauncherTaskExecutor-2] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Grab from test-server for Current Path /etc/designs/test-server/clienlibs/test took : 60112 milliseconds

The job is reported as FAILED and I do not know why.
Does the issue occur consistently?
Yes, I am not able to sync the folder at all. here is what it looks like in ./grabbit.sh:
Job when running:
{
    "endTime": null,
    "exitStatus": {
        "exitCode": "UNKNOWN",
        "exitDescription": "",
        "running": true
    },
    "jcrNodesWritten": -1,
    "jobExecutionId":<PHONE_NUMBER>563395306,
    "path": "/etc/designs/test-server/clienlibs/test",
    "startTime": "2019-04-17T16:57:29+0000",
    "timeTaken": -1,
    "transactionID":<PHONE_NUMBER>603729269
}

Job when FAILED:
{
    "endTime": "2019-04-17T16:58:29+0000",
    "exitStatus": {
        "exitCode": "FAILED",
        "exitDescription": "",
        "running": false
    },
    "jcrNodesWritten": -1,
    "jobExecutionId":<PHONE_NUMBER>563395306,
    "path": "/etc/designs/test-server/clienlibs/test",
    "startTime": "2019-04-17T16:57:29+0000",
    "timeTaken": 60161,
    "transactionID":<PHONE_NUMBER>603729269
}

Help pointing in the right direction
Do you guys have any idea what I should be looking at? I have been poking at this for about two days and I can't figure out what's wrong. I'm really hoping someone can point me in the right direction.

I faced similar issues.. did you check the grabbit bundle active and running on source and destination servers? check by hitting http://server:port/grabbit/job/all on both servers. if both are running then to get the real error message go to configMgr and enable debug logging for grabbitrecevice and aem error.log. those logs will help you in identifying the root cause of the failure.

Thanks for pointing out the DEBUG selection in configMgr @sivaprasad504. I went in and I checked the /grabbit/job/all on boths systems:
The server displays this (which is normal, since there are were never jobs running on it):
[]

the client displays this (which is fine,s ince all the jobs are support to run on this client, but the FAILED status still exists):
[{
	"transactionID":<PHONE_NUMBER>603729269,
	"jobExecutionId":<PHONE_NUMBER>563395306,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T16:58:29+0000",
	"timeTaken": 60161,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T16:57:29+0000"
}, {
	"transactionID":<PHONE_NUMBER>045048571,
	"jobExecutionId":<PHONE_NUMBER>700547502,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T16:25:00+0000",
	"timeTaken": 60167,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T16:24:00+0000"
}, {
	"transactionID":<PHONE_NUMBER>963492825,
	"jobExecutionId":<PHONE_NUMBER>675336536,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T16:12:30+0000",
	"timeTaken": 60170,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T16:11:30+0000"
}, {
	"transactionID":<PHONE_NUMBER>447537021,
	"jobExecutionId":<PHONE_NUMBER>779498180,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T16:01:42+0000",
	"timeTaken": 60112,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T16:00:42+0000"
}, {
	"transactionID":<PHONE_NUMBER>747771147,
	"jobExecutionId":<PHONE_NUMBER>766088911,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T15:55:08+0000",
	"timeTaken": 60164,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T15:54:08+0000"
}, {
	"transactionID":<PHONE_NUMBER>355819451,
	"jobExecutionId":<PHONE_NUMBER>472688390,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	},
	"endTime": "2019-04-17T15:51:50+0000",
	"timeTaken": 60167,
	"path": "/etc/designs/test-server/clienlibs/test",
	"startTime": "2019-04-17T15:50:50+0000"
}, {
	"transactionID":<PHONE_NUMBER>317332505,
	"jobExecutionId":<PHONE_NUMBER>926338844,
	"jcrNodesWritten": -1,
	"exitStatus": {
		"exitDescription": "",
		"exitCode": "FAILED",
		"running": false
	}
	...
	TRIMMED FOR BREVITY

After activating the DEBUG mode in condigMgr it seems to spit out a bit more info, however still along the same line. Here is what I mean:
24.04.2019 08:28:15.811 *DEBUG* [<IP_ADDRESS> [1556108895809] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Input: {
    "serverUsername" : "admin",
    "serverPassword" : "admin",
    "serverHost" : "test-server",
    "serverScheme" : "https",
    "serverPort" : "443",
    "batchSize" : 150,
    "deltaContent" : false,
    "pathConfigurations" :  [
        {
            "path" : "/etc/designs/test-server/clienlibs/test",
            "batchSize" : 50
        }
    ]
}

24.04.2019 08:28:15.863 *DEBUG* [<IP_ADDRESS> [1556108895809] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.batch.ClientBatchJob Current Job Params : timestamp=1556108895863,path=/etc/designs/test-server/clienlibs/test,scheme=https,host=test-server,port=443,clientUsername=admin,serverUsername=admin,serverPassword=admin,transactionID=8465422468680473942,excludePaths=,workflowConfigIds=,deleteBeforeWrite=false,pathDeltaContent=false,batchSize=50
24.04.2019 08:28:15.881 *INFO* [<IP_ADDRESS> [1556108895809] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.batch.ClientBatchJob Kicked off job with ID :<PHONE_NUMBER>041483526
24.04.2019 08:28:15.881 *INFO* [<IP_ADDRESS> [1556108895809] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Jobs started : [7642905644041483526]
24.04.2019 08:28:15.881 *INFO* [<IP_ADDRESS> [1556108895809] PUT /grabbit/job HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Transaction started<PHONE_NUMBER>680473942
24.04.2019 08:28:15.886 *DEBUG* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener SlingRepository : com.adobe.granite.repository.impl.SlingRepositoryImpl@13fb8ca0
24.04.2019 08:28:15.891 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Starting job : JobExecution: id=7642905644041483526, version=1, startTime=Wed Apr 24 08:28:15 EDT 2019, endTime=null, lastUpdated=Wed Apr 24 08:28:15 EDT 2019, status=STARTED, exitStatus=exitCode=UNKNOWN;exitDescription=, job=[JobInstance: id=16, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=8465422468680473942, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1556108895863, serverUsername=admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}]

24.04.2019 08:28:15.891 *DEBUG* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.steps.validation.ValidJobDecider com.twcable.grabbit.client.batch.steps.validation.ValidJobDecider Job determined to be valid for job path /etc/designs/test-server/clienlibs/test
24.04.2019 08:28:15.918 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet WorkflowConfig :
24.04.2019 08:28:15.919 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet Nothing to process...
24.04.2019 08:28:15.938 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.steps.workspace.DeleteBeforeWriteDecider Will retain nodes under job path for<PHONE_NUMBER>041483526...
24.04.2019 08:28:30.578 *DEBUG* [<IP_ADDRESS> [1556108910571] GET /grabbit/job/7642905644041483526.json HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Current Status : {"transactionID":8465422468680473942,"jobExecutionId":7642905644041483526,"jcrNodesWritten":-1,"exitStatus":{"exitDescription":"","exitCode":"UNKNOWN","running":true},"endTime":null,"timeTaken":-1,"path":"/etc/designs/test-server/clienlibs/test","startTime":"2019-04-24T12:28:15+0000"}
24.04.2019 08:29:13.661 *DEBUG* [<IP_ADDRESS> [1556108953656] GET /grabbit/job/7642905644041483526.json HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Current Status : {"transactionID":8465422468680473942,"jobExecutionId":7642905644041483526,"jcrNodesWritten":-1,"exitStatus":{"exitDescription":"","exitCode":"UNKNOWN","running":true},"endTime":null,"timeTaken":-1,"path":"/etc/designs/test-server/clienlibs/test","startTime":"2019-04-24T12:28:15+0000"}
24.04.2019 08:29:16.047 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Cleanup : JobExecution: id=7642905644041483526, version=1, startTime=Wed Apr 24 08:28:15 EDT 2019, endTime=Wed Apr 24 08:29:16 EDT 2019, lastUpdated=Wed Apr 24 08:28:15 EDT 2019, status=FAILED, exitStatus=exitCode=FAILED;exitDescription=, job=[JobInstance: id=16, version=0, Job=[clientJob]], jobParameters=[{serverPassword=admin, deleteBeforeWrite=false, scheme=https, port=443, transactionID=8465422468680473942, clientUsername=admin, excludePaths=, workflowConfigIds=, batchSize=50, timestamp=1556108895863, serverUsername=admin, host=test-server, pathDeltaContent=false, path=/etc/designs/test-server/clienlibs/test}] . Job Complete. Releasing session, and input stream
24.04.2019 08:29:16.051 *INFO* [clientJobLauncherTaskExecutor-6] com.twcable.grabbit.client.batch.ClientBatchJobExecutionListener Grab from test-server for Current Path /etc/designs/test-server/clienlibs/test took : 60166 milliseconds

24.04.2019 08:29:21.977 *DEBUG* [<IP_ADDRESS> [1556108961972] GET /grabbit/job/7642905644041483526.json HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Current Status : {"transactionID":8465422468680473942,"jobExecutionId":7642905644041483526,"jcrNodesWritten":-1,"exitStatus":{"exitDescription":"","exitCode":"FAILED","running":false},"endTime":"2019-04-24T12:29:16+0000","timeTaken":60166,"path":"/etc/designs/test-server/clienlibs/test","startTime":"2019-04-24T12:28:15+0000"}
24.04.2019 08:39:22.059 *WARN* [<IP_ADDRESS> [1556109562058] GET /grabbit/job/.json HTTP/1.1] com.twcable.grabbit.client.servlets.GrabbitJobServlet Bad request to receive job status for : /grabbit/job/.json. A job ID was not provided in the request.

I'm starting to believe this is some sort of silent timeout error, or something that I do not fully know how to track down. Do you guys know if that might be the case?

Exactly I have faced all these and were able to fix.. it's a default timeout issue. Update timeout setting on both source and destination servers by going to configmgr and search for something with http jetty and update from default 60000 ms which is one hr to 10hrs by adding a zero to it. You will be all set to happy grabbing from then 😀

Exactly I have faced all these and were able to fix.. it's a default timeout issue. Update timeout setting on both source and destination servers by going to configmgr and search for something with http jetty and update from default 60000 ms which is one hr to 10hrs by adding a zero to it. You will be all set to happy grabbing from then 😀

Alright, one of the main reasons why the job was always taking around 60 sec, was because of the timeout issue. @sivaprasad504 you had a great suggestion to check that out, because I saw my test-server firewall was blocking the test-client from connecting back.
The funny thing is, now the job fails instantly (156 miliseconds). I would say this is progress, but I am still in the dark about the exact reason:
{
    "endTime": "2019-04-25T16:10:16+0000",
    "exitStatus": {
        "exitCode": "FAILED",
        "exitDescription": "",
        "running": false
    },
    "jcrNodesWritten": -1,
    "jobExecutionId":<PHONE_NUMBER>009632152,
    "path": "/etc/designs/test-server/clienlibs/test",
    "startTime": "2019-04-25T16:10:16+0000",
    "timeTaken": 156,
    "transactionID":<PHONE_NUMBER>429985364
}

Is there any other more comprehensive log that I can monitor to see why this job fails? Even on DEBUG the Grabbit logs behave like everything is ok.

I am starting to think that this log message tries to tell me something is wrong, but I cannot figure out what it means:
26.04.2019 08:04:19.347 *DEBUG* [clientJobLauncherTaskExecutor-10] com.twcable.grabbit.client.batch.steps.validation.ValidJobDecider com.twcable.grabbit.client.batch.steps.validation.ValidJobDecider Job determined to be valid for job path /etc/designs/test-server/clienlibs/test
26.04.2019 08:04:19.374 *INFO* [clientJobLauncherTaskExecutor-10] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet WorkflowConfig :
26.04.2019 08:04:19.374 *INFO* [clientJobLauncherTaskExecutor-10] com.twcable.grabbit.client.batch.steps.workflows.WorkflowOffTasklet Nothing to process...
26.04.2019 08:04:19.392 *INFO* [clientJobLauncherTaskExecutor-10] com.twcable.grabbit.client.batch.steps.workspace.DeleteBeforeWriteDecider Will retain nodes under job path for<PHONE_NUMBER>019933516...

AEM error logshould give you more details on the error, which I'm guessing would be on the timeout of jetty http request. go to configMgr and increase that to few hours and try again.
Note: this needs to be done on both source and destination servers.

Hi @dandinu Can you share following packages if possible i have been trying to get but the links were outdated.

Sun-Misc-Fragment-Bundle-1.0.0
Grabbit-Apache-Sling-Login-Whitelist-1.0
Grabbit-Deserialization-Firewall-Configuration-1.0
Grabbit-7.1.5

Thanks,
Krishna


Delete workspace.xml

It's annoying that this file is mentioned whenever moving between branches. We don't really need to push this file either since it is related to our local workspace. So let's remove it 💪🏻

You should also add it to .gitignore if it's not already there!

You should also add it to .gitignore if it's not already there!

We do have it in the .gitignore! I suppose git still wants the file updated if it is in the repo 🤔

As far as I can tell, the reason its still there is because it wasn't added to the .gitignore until after it was already uploaded 🤔.


doc/building-running.md: Add database creation step

No idea why this failed on MacOS, but this is a documentation only PR, so just going to merge it,


Conventionalizing stride semantics

Swift offers two stride functions, stride(to:, by:) and stride(through:, by:). This proposal introduces a third style and renames the existing to and through styles.

@gribozavr @dabrahams ?

On Mar 11, 2016, at 12:35 PM, Chris Lattner<EMAIL_ADDRESS>wrote:
@gribozavr https://github.com/gribozavr @dabrahams https://github.com/dabrahams ?

Quite honestly, in its current state, this half of the split proposal did not have strong support
when brought up on list. I'd rather not waste the team's time pushing a proposal without legs.
The problem it would be fixing would probably be better addressed by stepping back and re-thinking
closed and open intervals, ranges, strides, etc. (I know this is problematic given the resources
and time available to address this.)
-- Erica, who has been filling notebook pages with scribbles trying to think
through what she really wants from progressions

On Mar 11, 2016, at 1:41 PM, Erica Sadun<EMAIL_ADDRESS>wrote:

On Mar 11, 2016, at 12:35 PM, Chris Lattner<EMAIL_ADDRESS>wrote:
@gribozavr https://github.com/gribozavr @dabrahams https://github.com/dabrahams ?

Quite honestly, in its current state, this half of the split proposal did not have strong support
when brought up on list. I'd rather not waste the team's time pushing a proposal without legs.
The problem it would be fixing would probably be better addressed by stepping back and re-thinking
closed and open intervals, ranges, strides, etc. (I know this is problematic given the resources
and time available to address this.)

I am impressed that you are taking the long view!  I was thinking the same thing (especially in light of the new indexing model) but there’s no justification for rejecting the proposals for review at this point… unless you’re asking to withdraw them.
I just merged both proposals, but if you give me the word I’ll revert those changes.
-Dave

On Mar 11, 2016, at 2:46 PM, Dave Abrahams<EMAIL_ADDRESS>wrote:

On Mar 11, 2016, at 1:41 PM, Erica Sadun<EMAIL_ADDRESS>wrote:

On Mar 11, 2016, at 12:35 PM, Chris Lattner<EMAIL_ADDRESS>wrote:
@gribozavr https://github.com/gribozavr @dabrahams https://github.com/dabrahams ?

Quite honestly, in its current state, this half of the split proposal did not have strong support
when brought up on list. I'd rather not waste the team's time pushing a proposal without legs.
The problem it would be fixing would probably be better addressed by stepping back and re-thinking
closed and open intervals, ranges, strides, etc. (I know this is problematic given the resources
and time available to address this.)

I am impressed that you are taking the long view! I was thinking the same thing (especially in light of the new indexing model) but there’s no justification for rejecting the proposals for review at this point… unless you’re asking to withdraw them.
I just merged both proposals, but if you give me the word I’ll revert those changes.
-Dave

@gribozavr <https://github.com/gribozavr https://github.com/gribozavr> @dabrahams <https://github.com/dabrahams https://github.com/dabrahams>
I actually do stand behind this proposal. I just worry that I'm fighting the wrong battle.
The other proposal's issues are clear: the math is demonstrably bad, and there are a bunch of
ways you can fix that for the short term while waiting for a better system in the long term.
With this proposal, the main objection voiced by the community was this: the words I chose
did not reflect the semantics of open and closed ranges. And I think that's the wrong objection.
I believe my semantics reflect natural ways to express the end progressions. These are end scenarios
that you'd encounter in for-loops, while-loops, and repeat-until loops. I was easily able to find reasons
to use all three situations that reflect: "while less than", "while less than or equal to", and
"until greater than or equal to".
At the same time, there are multiple issues with the current stride/interval/range system. I don't
want to waste everyone's time bailing water instead of designing a better hull.
Let me know what you think I should do.
-- Erica

I generally prefer to make a holistic analysis of an area of the library to making fixes that are likely to be obsoleted by something that looks very different.  If you feel that there’s a better answer to be had with a broader analysis, I'd suggest we do that for Swift 4 or something.  Otherwise, we should go ahead with the proposals as submitted.

I suspect there's a better answer to be had with a broader analysis.
-- E

On Mar 11, 2016, at 4:48 PM, Dave Abrahams<EMAIL_ADDRESS>wrote:
I generally prefer to make a holistic analysis of an area of the library to making fixes that are likely to be obsoleted by something that looks very different. If you feel that there’s a better answer to be had with a broader analysis, I'd suggest we do that for Swift 4 or something. Otherwise, we should go ahead with the proposals as submitted.
—
Reply to this email directly or view it on GitHub https://github.com/apple/swift-evolution/pull/184#issuecomment-195605647.


Use updated versions of coil

Markwon isn't usable for jetpack compose 1.2.1 because its using an older version of coil.

Hello @dessalines ,
Markwon has a plugin to load images with Coil, but you can use Markwon without it


Static IP feedback with k8s via AWS EKS

I spent the past few weeks working off and on to get a static IP added to an existing EKS cluster. I'm not sure if I'm bad at this (probably), or if it's just hard for everybody, but it took a lot of trial and error. I put a bunch of notes over here: https://github.com/freelawproject/courtlistener/issues/2273#issuecomment-1386258025
Is there value in adding some or all of these notes to this repo somewhere? I'd be happy to do an addition to the readme or a Wiki page if you want to turn that feature on in the Github settings. (Or maybe this issue is enough!)
Anyway, our system utilizing webhook-sentry is deploying now and we're really excited to get static egress and the security benefits this offers. Thank you once more!

Apologies for the delayed response here @mlissner  -- it would absolutely be useful to have that info in the readme. Please send a PR to add it to the README when you get the chance.


feat(cli): ✨ allow issues hint to be customized w/ issuesHint option

Pull Request Checklist
🚨 Please review the guidelines for contributing to this repository.

[x] Appropriate label or labels have been added
[x] ✅ Tests for the changes have been added (for type:fix / type:feat)
[x] 📝 Docs have been reviewed, added or updated if needed (for type:fix / type:feat)
[ ] 🏁 Issue number has been linked if this PR closes one

Description
Please describe your pull request.
Breaking Change?

[ ] 💥 Yes
[x] No

❤ Thank you for contributing!

Codecov Report

Merging #336 (ed05568) into master (892276c) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #336      +/-   ##
==========================================
+ Coverage   97.44%   97.46%   +0.01%
==========================================
  Files          31       31
  Lines         392      394       +2
  Branches       67       67
==========================================
+ Hits          382      384       +2
  Misses          8        8
  Partials        2        2

Impacted Files
Coverage Δ

src/config/helpers/validate-config/lang.ts
100.00% <ø> (ø)

src/defaults/config.ts
100.00% <ø> (ø)

src/config/helpers/validate-config/schema.ts
100.00% <100.00%> (ø)

src/prompts/issues.ts
100.00% <100.00%> (ø)

src/prompts/lang.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


1080p not "best" quality in youtube-dl -F

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.10.01. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[0] I've verified and I assure that I'm running youtube-dl 2017.10.01

i am on 2017.09.24, it seems macports hasn't added today's update to its repos yet. (i did run youtube-dl -U and it told me to run macports' update procedure, which itself says everything is up to date. so. there you go.) that's unsurprising given there's been less than 24 hours for them to add it.
however, the question i'm asking about has been the case for at least 2 years, and i see no other raised issues about this, so i doubt this matters too much.
Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue
hi, first off i want to say, i apologise if this has been answered already. i searched the github issues for "1080p", but couldn't find anything actually telling me why this is the case.
i'm curious as to why the automatic detection in youtube-dl -F for the best quality seems to top out at 720p? even when 1080p or higher is available, it insists one of the 720p options is "best".
it seems like this heuristic prefers files that are audio+video together, and all 1080p or higher streams are listed as "video only", even though muxing together formats after download is completely fine and is what youtube-dl actually does in practise anyway.
this strikes me as extra weird because youtube-dl does in fact download the 1080p version with separate audio (then muxes) when you give no flags. maybe this is simply a case of youtube-dl -F's display lagging behind actual behaviour?
i saw someone mention this in 2015 in a stackexchange thread, though that person said you need to specify the 1080p stream to get it to download, so obviously something about this has been changed since then.
thanks in advance for your time and answer c:

Read what does best actually mean.


README

Hi,
i just saw this lib posted on google and asking for feedback so here is some.
Great coverage and code climate! I like that kind of thing.
But, I was wondering why you would write a new library when there is four listed already. And i don't mean that in a bad way, really. Just  a question.
If you think of selling it, what would be it's strong points.
Or if you think of convincing me to use (and then quite likely contribute), why would i choose this one.
I'd suggest you put that in the readme, so it's not just for me.
Would also be nice to hear how you use it, possible an example.

Hi!
Sorry for the delayed response, the holidays have me busy. Thank you for the great compliments and interest!
I hope you do not find my motivations dissatisfying, but it mainly started out of a desire to learn the API more throughly for a side project I was working on. After reviewing the Gems that existed at the time (I believe there were only 3 then? I may be mistaken about this) the available options were either not fitting what I needed (i.e. implemented endpoints), were (seemingly) unmaintained, or of a style that I did not really enjoy working with (i.e. Active Record style). While none of these things are absolutely cause for creating a new wrapper or bad in any way I figured I wanted to learn the API more throughly so why not?
The strong point I feel for this library are that it is meant to be as minimal as possible. I am trying to avoid doing any unnecessary processing on top of the responses from the API (i.e. object instantiation for the use as an interface) which was a motivation as well in removing Hashie from this library and returning straight JSON. That being said, I can not honestly say this is a better approach than any of the other libraries out there (they all look great as well), just my preferred implementation so that a user can control what they do with the JSON after the fact. I suppose I figure that I am not the only one wishing to have something of this style so why not make it and add it as a a possible option for other users?
Given all of this I have not added something to the README of this nature for the reason that I do not think there is anything compellingly different other than methodology and opinion (which I would love to discuss). I hope that this does not discourage you from trying the Gem or contributing to it if you use it, I just like to be frank about my motivations :smile:.
Thank you for your feed back!

Hi
thanks for the elaborate and honest answer. I think it's well worth putting this minimal approach into the readme. The pure json thing, it's a good thing to know for people who have to make choices.
I'll still give a spin, though i do like my objects. I just tried themoviedb-api and that looked to be working.
Also has good coverage, i do so like good coverage.
Speaking of themoviedb-api, check out their readme https://github.com/18Months/themoviedb-api
which goes a long way to make one want to use it.
I'll get back with a new issue if i have something, thanks


Update Readme.md

Noticed, that link was leading to the example.com instead of documentation. Little bit tired to read code now, so "Update Readme.md" 😄

Noticed, that link was leading to the example.com instead of documentation. Little bit tired to read code now, so "Update Readme.md" 😄

You are aware that this project is not a part of hacktoberfest yet right ?

Yeah, but it doesn't mean I can't contribute to it (:

oh great then , thanks for the pr


range function added

Love this library!  This pull request adds a range function that behaves the same as python's range function.

Awesome!


implement findMatch endpoint

@mdiller
fixes #1883

This looks fantastic! Thanks!

This is deployed, give it a try?


fix: the order of transform plugins

re-order the transform plugins, so we can get the source code in user config transform

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-next@cd0e6b1). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             release-next     #391   +/-   ##
===============================================
  Coverage                ?   79.97%
===============================================
  Files                   ?       80
  Lines                   ?     6792
  Branches                ?      801
===============================================
  Hits                    ?     5432
  Misses                  ?     1351
  Partials                ?        9

Continue to review full report at Codecov.

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


basic deployment of PostgreSQL

Merging directly as it had no impact on the rest of the code (plus it works).


[INLONG-6858][Manager][Sort] Support extract node of Apache Hudi

Prepare a Pull Request
[INLONG-6858][Sort] Support extract node of Apache Hudi

Fixes #6858

Motivation

Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)

[x] This change is a trivial rework/code cleanup without any test coverage.

[x] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Please add the related guide after the PR.

https://github.com/apache/inlong-website/pull/658


We need an update

When I run an npm command, such as npm audit fix, I get this:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

But I have a later (the latest?) version of jest installed, ^25.1.0! We need to update jest-preset-coffeescript to require this later version of jest if they are compatible, or if they are not, we need to make them compatible.

@ovikholt See #34… But yes I will bump the dependencies as soon as I can get my setup back up and running…

@ovikholt Just released a new version 1.2.0… so please do test! Also, I will be migrating this package to GitHub Package Registry in future… Although apparently GitHub just acquired npm, so this might happen anyway.


add head function

head receives array as the argument, and returns first element of the array
const arr = [1, 2, 3, 4, 5];
const result = head(arr);
// result: 1

Taken by @rudk0


Type name clash when Model and ModelUpdate is defined in the schema

Bug description
Prior context: https://github.com/prisma/prisma/issues/9421
We are encountering a conflict in our generated typing when a model named User for example is defined along with UserUpdate, it will generate invalid type that won't compile.
How to reproduce
Generate client with the following model:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id String @id @default(cuid())
}

model UserUpdate {
  id String @id @default(cuid())
}

Expected behavior
Client should generate valid types for any valid schema
Prisma information

See above in "how to reproduce"
Environment & setup

OS: Windows 10
Database: Postgres
Node.js version: 14.17.0

Prisma Version
Environment variables loaded from prisma\.env
prisma                  : 3.2.0-dev.48
@prisma/client          : 3.2.0-dev.48
Current platform        : windows
Query Engine (Node-API) : libquery-engine a153cf0caf0e5e24b69198dcdc040568256a1124 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli a153cf0caf0e5e24b69198dcdc040568256a1124 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core a153cf0caf0e5e24b69198dcdc040568256a1124 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt a153cf0caf0e5e24b69198dcdc040568256a1124 (at<EMAIL_ADDRESS>Default Engines Hash    : a153cf0caf0e5e24b69198dcdc040568256a1124
Studio                  : 0.435.0

Hello,
Any news on this?
I get the same error, when trying to build for production, while on dev environment everything seems to be working properly.
The error:
#0 63.80 ../node_modules/.prisma/client/index.d.ts:10331:62
#0 63.80 Type error: Type 'S["include"][P]' does not satisfy the constraint 'boolean | AccountssArgs | null | undefined'.
#0 63.80   Type 'S["include"]["created_by_account"]' is not assignable to type 'boolean | AccountssArgs | null | undefined'.
#0 63.80     Type 'S["include"]["created_by_account"]' is not assignable to type 'boolean | AccountssArgs | null | undefined'.
#0 63.80       Type 'S["include"]["created_by_account"]' is not assignable to type 'AccountssArgs'.
#0 63.80         Type 'S["include"]["created_by_account"]' is not assignable to type 'AccountssArgs'.
#0 63.80           Type 'S["include"][P]' is not assignable to type 'AccountssArgs'.
#0 63.80             Type 'S["include"]["created_by_account"]' is not assignable to type 'AccountssArgs'.
#0 63.80               Type 'S["include"]["created_by_account"]' is not assignable to type 'AccountssArgs'.
#0 63.80
#0 63.80   10329 |     ? Accountss  & {
#0 63.80   10330 |     [P in TrueKeys<S['include']>]:
#0 63.80 > 10331 |         P extends 'created_by_account' ? AccountssGetPayload<S['include'][P]> :
#0 63.80         |                                                              ^
#0 63.80   10332 |         P extends 'modified_by_account' ? AccountssGetPayload<S['include'][P]> :
#0 63.80   10333 |         P extends 'account_is_personel' ? personel_employeesGetPayload<S['include'][P]> | null :
#0 63.80   10334 |         P extends 'students' ? studentsGetPayload<S['include'][P]> | null :
#0 63.93
#0 63.93 > Build error occurred

The "solution" mentioned in #9421 of renaming model fooUpdate when having another model foo in the schema did not resolve the error for me.
Environment & Setup

OS: Artix Linux
Database: MariaDB
Node.js version: v14.20.0
Typescript version: 4.8.2

Prisma Version
prisma                  : 3.10.0
@prisma/client          : 3.10.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 73e60b76d394f8d37d8ebd1f8918c79029f0db86 (at<EMAIL_ADDRESS>Default Engines Hash    : 73e60b76d394f8d37d8ebd1f8918c79029f0db86
Studio                  : 0.458.0
Preview Features        : interactiveTransactions, filterJson

I ran into the same issue today with Typescript 4.9 and Prisma 4.6.1 (In fact, I actually upgraded everything hoping it would fix itself).
The errors:
  Type 'EventPostUpdateFindUniqueArgsBase' is not assignable to type 'boolean | EventPostUpdateArgs | null | undefined'.
    Type 'EventPostUpdateFindUniqueArgsBase' is not assignable to type 'EventPostUpdateArgs'.
      Type 'T' is not assignable to type 'EventPostUpdateArgs'.```

Renaming the models from `FooUpdate` to `FooChanges` fixed the issue instantly, but it required an insane amount of google-fu to reach this issue.

I just found out today that it also happens when properties are also named update or updates, again, renamed "update" to "props" has circumvented the issue.


Kindly Outreach Follow-ups

[ ] Continue follow-up work with Codecademy, Stanford, Discord, Scratch, and any other potential partners
[x] Reach out unicef education colleagues to see if there are partnerships we have OR platforms they know of (https://directory.unicef.org/office/3003?people=5417) (https://www.unicef.org/education)
[x] Email Afrooz a summary of latest development with Kindly

Emailed 3 ed colleagues. Have 2 more who I will reach out to if I don't hear from the initial 3.

Emailed 2 additional ed colleagues, followed up with the previous 2. Also asked Mara + Wendy if they have contacts.

Will close this for now and create a new one for next sprint


Example usage of only tracking algorithm

Hello,
I have a 4D data (3DxT) and it is already segmented, meaning that for each T, I have 3D masks.
Is there any instructions of using the algorithm + model on already segmented data?
I think a simple example like this:
https://btrack.readthedocs.io/en/latest/user_guide/simple_example.html
Might be useful.
Thanks a lot,
Oren

Thank you for your question. Currently, this feature is not available, but I appreciate your interest in using it. I am considering two approaches for implementing this feature: using only segmentation results as inputs, or using segmentation results along with a probability map of cell regions. If the segmentation results are highly accurate, using segmentation results alone may be sufficient. However, if there are mistakes in the segmentation, adding a probability map generated by the deep network (or at least the raw cell images) may help improve the accuracy of the final cell positions.

Thanks @WenChentao, I actually did not know that the model also use probability maps.
I'll get in the details of my pipeline, and maybe it will help.
We use 2p microscope to get long (T) recording of volumes (About 2Hz per plane). I average 40 time-steps from the raw recordings to get a clear cell image in the volumes. (for example if I have raw data of [1000,30,100,100] = [T,Z,X,Y], I mean every 40 frames to get to data of [25,30,100,100])
We then use cellpose to extract the masks of the cells in the volumes, and when I say use cellpose I mean the whole pipeline that includes correcting the labels and fine-tunning the model. Not sure if cellpose segmentation model is the best (especially for 3D), but the gui that they have make it much easier to correct the segmentation and teach ppl how to do the segmentation.
As far as I know, cellpose output but masks and probability maps, therefor I can supply both.
I hope it helps, let me know if I can help in anyway.

Thank you for providing more details, @orena1.
Our program (v5.0.2-alpha) currently uses StarDist3D for segmentation and stores the segmented cell positions (2D array of shape (cell_number, 3)) and probability maps of cell regions (3D array of shape (size_height, size_width, size_depth)) in the 'seg' folder with filenames like 'coordst0001.npy' and 'probt0001.npy' (Related codes)
If you can prepare these two types of files by yourself (with CellPose, for example), you can use our track_stardist_single_mode.ipynb or track_stardist_ensemble_mode.ipynb notebooks for tracking without needing to perform segmentation (Section B in these notebooks).
I will consider adding this feature to the program in the future. However, I cannot guarantee a specific timeline for this development.

Thanks @WenChentao  do you have an example of those 'coordst0001.npy' and 'probt0001.npy' files so I can try to recreate them?

@orena1
Here are the samples of my demo data in Jupyter notebook:
np.load("worm1/seg/coords0001.npy").shape # (number_cells, 3)
(163, 3)
np.load("worm1/seg/coords0001.npy")

array([[262, 472,   7],
[362, 560,   7],
[220, 274,   9],
...
[224, 256,   8]], dtype=int64)

np.load("worm1/seg/prob0001.npy").shape # (height, width, depth)

(256, 512, 21)

Please note that the order of the three coordinates in each row and the order of the probability array should be the same. Additionally, ensure that the coordinates are transformed to have consistent units in x, y, and z, and that the probability values fall between 0 and 1.
Is this what you were looking for?
If you want to know more details, I recommend that you actually install my package and run the tracking notebooks using my demo data, which is publicly available.


Cannot open the same program multiple times at the same time

It'll be better if it could open the same console filedialog multiple times at the same time. Thank you!

Hi mouzei. I was going to ask what scenario would require multiple instances, but then I saw that you closed the issue. I'm curious to learn the details.
Les