Discussion, why do we have metadata and attributes (sometimes on the same model) ?

Correct me if I'm mistaken, technically the attributes are a model instance with (key, value) fields and metadata items are JSONFields. Both are the same in terms of the idea (a dict is a key value) and how can we use them (at least the interface provided for usage can be the same), here's what I'm thinking
Attribute groups ->
- Group1 (Metadata)
- SelectedAttr1 (attribute, values)
- SelectedAttr2 (attribute, values)
- ....
- Group2 (Attributes)
- SelectedAttr1
-  ...
and we could (if we wanted) call a group "Metadata" and another "Attributes" instead of having 2 things that are implicitly sharing the same idea with different implementation
We can benefit from this a lot, lemme list some of them

We can share the same dashboard implementation of both of them, so metadata items can have dropdowns, booleans, ...etc
Faster queries on data intensive backends, (no JSON encoding or decoding happens for EACH element that we're comparing when querying metadata (a must have anyway, by my implementation or another) GH-6683

This of course is a breaking change, this is why this is a discussion.

@patrys What do you think about this?

@patrys What do you think about this?

Attributes enforce a schema while metadata does not and it's often impractical for it to do so. We've intended metadata to serve machines (eg. to be constructed and consumed by code) while attributes serve humans (typical use case is to display information to customers).

Attributes enforce a schema while metadata does not and it's often impractical for it to do so. We've intended metadata to serve machines (eg. to be constructed and consumed by code) while attributes serve humans (typical use case is to display information to customers).

Attributes enforce a schema while metadata does not and it's often impractical for it to do so. We've intended metadata to serve machines (eg. to be constructed and consumed by code) while attributes serve humans (typical use case is to display information to customers).

I understand, but attributes also can serve machines well (better performance, as mentioned) by adding a specific attribute group that plays the metadata role (conventionally, not enforced), I think if metadata serves machine then they shouldn't appear on the dashboard, but they do, so they serve both humans and machines, anyway what do you think about adding attributes to other models like category? for adding something like "Featured categories" ?

Attributes enforce a schema while metadata does not and it's often impractical for it to do so. We've intended metadata to serve machines (eg. to be constructed and consumed by code) while attributes serve humans (typical use case is to display information to customers).

I understand, but attributes also can serve machines well (better performance, as mentioned) by adding a specific attribute group that plays the metadata role (conventionally, not enforced), I think if metadata serves machine then they shouldn't appear on the dashboard, but they do, so they serve both humans and machines, anyway what do you think about adding attributes to other models like category? for adding something like "Featured categories" ?

@maarcingebala @korycins  any thoughts?

@maarcingebala @korycins  any thoughts?

We intend to cover most of the objects with metadata because thanks of its flexibility it will allow us to use it in different apps. For now, attributes will stay in products and pages.


Implement set 'difference' for IP resources

In order to see which IP prefixes/ranges/addresses or AS ranges/numbers are exclusively found in an (old) set (i.e. removed), or a new set (i.e. added) we need to implement fn difference, in keeping with the naming used for this in the rust std libs.

Implemented in #139 for 0.10 and #142 for 0.11.


Problem with analyze

Some commit broke Analyze. When finish a form, and try to view the Analyze, this happen:

The file in the log is: submit-form.client.directive.js
And all of this logs print it when makes a scroll on the page

In fact, the problem is ".activeField" doesn't exist

Other problem is you can't do a "Form" if you're logged

@AdrianP- what do you mean by do a Form?

Like submit a form if you are logged in?

With "do a Form" I meant the option "View Form" in the Admin panel.
That happens me also with the last commit. Can you test it?

@AdrianP- just to clarify this bug only happens when you are logged in, correct?

Exactly. Thanks for your time @whitef0x0

@AdrianP- what file is this bug referencing?

Technically in the analyze view there should be no element with the 'activeField' class so it should be erroring. I haven't had s chance to test this yet

The file:

First Error happens when press the "View Form" button and you're logged.
The second, when you scroll in the Analyze tab
Thanks!


[BUG]

npm token list # What / Why

n/a

When

n/a

Where

n/a

How
Current Behavior

n/a

Steps to Reproduce

n/a

Expected Behavior

n/a

Who

n/a

References

n/a

Closed #330


Checks can be re-run

Now that #73 is in, it appears there is a "re-run" button on the checks page which triggers a POST to the bot. We should look into rerunning the check if this is clicked.

What button? I don't see any buttons.

On the checks tab.
Also see this section of the docs: https://developer.github.com/v3/activity/events/types/#checkrunevent

Oh, I can't see it. Maybe only author or maintainer sees it.


Improvements to k4run

BEGINRELEASENOTES

Add improvements to k4run: clean up code, use the logging module, parse all the arguments using argparse, sort display of options

ENDRELEASENOTES

Parsing is done using argparse only instead of the previous combination of manual parsing and argparse. I think this is cleaner and if the arguments are wrong it will show the usage automatically (before there was a explicit testing of this)
Code was cleaned up a bit, for example there were very deeply nested if/for that can be changed a bit. Indentation is (and was) inconsistent so if we agree on 2 or 4 spaces I can change that; it makes the diff very hard to read so we can keep it for the last change.
Previously the display of options wouldn't be sorted and would be different each time because there was a list(set( that has undetermined ordering, now it will always be sorted in the same order as they were defined in the file (for python >= 3.7, since it is a one liner in that case).
Now using logging for messages as per #50. Right now there is a [k4run] for the messages that come from k4run but this is a placeholder. For example for the Gaudi processes the format looks like [ MESSAGE "VXDEndcapDigitiser"] and many things can be done like adding the date, the level of the message, etc. I don't have a strong opinion. This is how it looks now:

[k4run] LcioEvent --> MyAIDAProcessor --> EventNumber --> InitDD4hep --> Config --> OverlayFalse --> VXDBarrelDigitiser --> VXDEndcapDigitiser --> InnerPlanarDigiProcessor --> InnerEndcapPlanarDigiProcessor --> OuterPlanarDigiProcessor --> OuterEndcapPlanarDigiProcessor --> MyConformalTracking --> ClonesAndSplitTracksFinder --> Refit --> MyDDCaloDigi --> MyDDSimpleMuonDigi --> MyDDMarlinPandora --> LumiCalReco --> MergeRP --> MergeClusters --> MyClicEfficiencyCalculator --> MyRecoMCTruthLinker --> MyTrackChecker --> CLICPfoSelectorDefault_HE --> CLICPfoSelectorLoose_HE --> CLICPfoSelectorTight_HE --> CLICPfoSelectorDefault_LE --> CLICPfoSelectorLoose_LE --> CLICPfoSelectorTight_LE --> RenameCollection --> VertexFinder --> JetClusteringAndRefiner --> Output_REC --> Output_DST
[k4run] Option name: EventDataSvc.OutputLevel EventDataSvc.OutputLevel 0
[k4run] Option name: LcioEvent.OutputLevel LcioEvent.OutputLevel 4
[k4run] Option name: LcioEvent.Files LcioEvent.Files ['ttbar.slcio']
[k4run] Option name: InitDD4hep.OutputLevel InitDD4hep.OutputLevel 4
[k4run] Option name: InitDD4hep.ProcessorType InitDD4hep.ProcessorType InitializeDD4hep

I ran clicReconstruction.py on the same file and got similar results
Other related issues:

#89 I could reproduce with the podio reader but this has been fixed in https://github.com/AIDASoft/podio/pull/355. With the LCIO reader it exits without crashing. Can we close it?
#90 I checked and certainly by default the option to attach gdb is set to false for Gaudi. I could reproduce this issue with the podio reader before https://github.com/AIDASoft/podio/pull/355 (by trying to open a non-existent file, now fixed), where TFile.Open fails and pulls gdb. It was very very slow. Interestingly I ran with everything local (without cvmfs) and it took just a couple of seconds to display the backtrace, so cvmfs is at least partly responsible for the slowness.
#72 Using --npcus with a number different from 0 fails with:

  File "/cvmfs/sw.hsf.org/spackages6/gaudi/36.5/x86_64-centos7-gcc11.2.0-opt/z2prd/python/Gaudi/Main.py", line 476, in run
    result = self.runParallel(ncpus)
  File "/cvmfs/sw.hsf.org/spackages6/gaudi/36.5/x86_64-centos7-gcc11.2.0-opt/z2prd/python/Gaudi/Main.py", line 561, in runParallel
    Parall = gpp.Coord(ncpus, c, self.log)
  File "/cvmfs/sw.hsf.org/spackages6/gaudi/36.5/x86_64-centos7-gcc11.2.0-opt/z2prd/python/GaudiMP/GMPBase.py", line 1378, in __init__
    sub = Subworker(
  File "/cvmfs/sw.hsf.org/spackages6/gaudi/36.5/x86_64-centos7-gcc11.2.0-opt/z2prd/python/GaudiMP/GMPBase.py", line 834, in __init__
    GMPComponent.__init__(
  File "/cvmfs/sw.hsf.org/spackages6/gaudi/36.5/x86_64-centos7-gcc11.2.0-opt/z2prd/python/GaudiMP/GMPBase.py", line 473, in __init__
    self.msgFormat = self.config["MessageSvc"].Format
KeyError: 'MessageSvc'

See my comment on the commit: https://github.com/key4hep/k4FWCore/pull/93/commits/59b0c68f60d131bcd56fa28b079a8a42291e68cb#r1068103342
The
[k4run] Option name: EventDataSvc.OutputLevel EventDataSvc.OutputLevel 0
[k4run] Option name: LcioEvent.OutputLevel LcioEvent.OutputLevel 4
[k4run] Option name: LcioEvent.Files LcioEvent.Files ['ttbar.slcio']
[k4run] Option name: InitDD4hep.OutputLevel InitDD4hep.OutputLevel 4
[k4run] Option name: InitDD4hep.ProcessorType InitDD4hep.ProcessorType InitializeDD4hep

logging was added for some ad-hoc debugging, in principle this information is stored in the metadata by  the joboptions service. It could be removed, but maybe it is nice to have in the logs.


Mark's cafe incorrectly showing that it's open

Contact OpenData Help, they'll reach out to the appropriate people at Business Services to have this resolved. We used to have a contact at Business Services for direct contact, but they may have changed. Let me know if you still want their contact info anyways.

Closing because not inherent bug with the mobile server but rather with data source


Output more optimized DocumentNode

Removing empty array fields should work the same, and reduce bundle size.

Fixed and released !


Rename the helm chart release_name variable to name

Context
In #25 Kapitan has changed the helm chart name from release_name to name. Consider a renaming with the next major release.
Alternatives
Just keep the naming as is.

From our perspective (Tarazed), there's no need to rename the component parameter. We believe it's good to have parameters which clearly communicate what they're configuring, and with a parameter name, I have no idea what's getting configured. Therefore we prefer to keep the component parameter as release_name, even if Kapitan's Helm support has changed the parameter.


comotanmuchacho by srraccon

Song Name
comotanmuchacho
Artist Name
srraccon
Source
Youtube
Youtube Link
https://youtu.be/VCRdCd6Jh8M?si=db5cw58OGQKn3my-
Direct File Link
No response
Song ID
71817083
Extra
Created from Auto Nong.
Created for level: 106853591

It's just a meme okay?

It's just a meme okay?


Refactor to use nm-configurator

Patch looks good... anyway, why not support both nmc and nmstate? The library behind it is the same, ti changes "just" the binary and the syntax, changes to the code could be minimal. This would open to wider usage in community images where nmstate could be already be available or packaged for some base OS images, while supporting also the nmc binary where nmstate is not available (or nmc is preferred). The idea could be to have a kind of "autodetection" just probing for the nmc binary first. How would that look?

Could be an idea, but I would avoid any autodetection for simplicity.
We could have a configurator.type field that defaults to nmc but allows nmstate and at this point I can reintroduce the nmconnections one, since the implementation is also very similar.

@fgiudici I added network.configurator that can accept nmc (default), nmstate, nmconnections values.
I'd also like to install both nmc and nmstate in the dev image, so that we can locally test with both and for example have three-flavors of sample registrations.
Documentation should also be updated accordingly (so most likely one subpage for each configurator, with a few examples)
I'll work on that if you are ok with this solution


Redesign this step

Composition is weird, and is incorrect in the sequence. First select the column, then the operation depeding on that (sum or avg can only be done with Numeric columns)

so, if I understood correctly, you mean something like this:
1st state:

2nd state:

Yep
On Jun 19, 2015 8:59 PM, "josecruz"<EMAIL_ADDRESS>wrote:

so, if I understood correctly, you mean something like this:
1st state:
[image: 2nd step copy 3]
https://cloud.githubusercontent.com/assets/596509/8260772/0c265ef6-16c6-11e5-8f1a-1c9f957e0ba7.png
2nd state:
[image: 2nd step copy]
https://cloud.githubusercontent.com/assets/596509/8260774/10a1844c-16c6-11e5-98e0-eca2bd98b1af.png
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/4137#issuecomment-113606710.

hey @josecruz be sure everything is in place, and that @viddo know the changes


Cannot Authenticate Cloud SQL proxy

While I see a few issues related to sql connection, I do not see anything matching this scenario._
Currently following the App Engine Flexible Bookshelf Tutorial.
Upon reaching the step "Creating the Database Tables":
The client application fails, unable to make a connection through the proxy.
First Step:  I checked the threads on #129 #92 and #126 to make sure I was configuring and authenticating as documented.
The error logged in the proxy service :
Response: {
  "error" : "invalid_grant"
}

Implemented  the use cases that fit my needs:

"Credentials supplied by local environment"
"Credentials supplied in the proxy invocation command"
Both approaches failed to resolve the error.

side note: when using setting file path for credential file in CLI, the user is not informed if there is an issue with the file path, file name, or reading the file. I raise this because I do not know if the the launch script is able to locate the cred file since it does not throw a warning if there is an error if it fails to do so.
Abandoning the table creation script  python bookshelf/model_cloudsql.py
attempted to access the proxy via mysql directly
mysql --host <IP_ADDRESS> --user root --password
same  error message on proxy as before.
MySQL error:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
I have placed the issue here because I am following the tutorial and configuring a directed.

@andrewsg  My error.   Closing.


Consider exporting Directory.list in cephfs package

In a comment on #217 we have interest in having the list function exported. This is a convenience function that returns all entries in a directory in a single slice.
Alternatively, I had considered a ListN(int) version that could possibly split the difference between convenience and scalability.

This was discussed recently over voice chat and we came to the conclusion that a very-thin list function is probably too "middle ground" outside of a few narrow use cases.
Rather, if we build on top of  ceph_readdirplus_r we can get results that are similar (if not the same as) the Go os packages FileInfo result type. Using that we can more closely match the os-agnostic results that many Go programs expect to achieve.

Closing this as a duplicate of #326 as that issue was filed by a non-maintainer and demonstrates some demand rather than my pure speculation.


[improve][broker] Add metrics related interfaces for BrokerInterceptor

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
When I want to monitor the relevant data in the BrokerInterceptor, currently the BrokerInterceptor does not provide relevant interfaces.
I think providing such extensions is necessary.
Solution
https://github.com/apache/pulsar/blob/e96b3398912163eb6e0528c10aed3507c95952fd/pulsar-broker/src/main/java/org/apache/pulsar/broker/intercept/BrokerInterceptor.java
Add a interface, like this:
default void addCustomizeMetrics(PrometheusMetricStreams streams, PulsarService pulsar){
}

https://github.com/apache/pulsar/blob/e96b3398912163eb6e0528c10aed3507c95952fd/pulsar-broker/src/main/java/org/apache/pulsar/broker/stats/prometheus/PrometheusMetricsGenerator.java#L185-L187
Then callback the addCustomizeMetrics(stream, pulsar) method here.
This is just a draft.
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

@codelipenghui Please take a look.

I think it's ok.
I presume you need high granularity metrics - topic level, which is why you want to use PrometheusMetricStreams, right?
This only emphasize the need to solve this properly via OpenTelemetry API and let plugins register their own metrics easily, as part of PIP-264: https://github.com/apache/pulsar/issues/20197

I read the PIP-264 and discussion threads, it sounds great, but it looks like it will take a lot of time investment.
Therefore, I think we can add this feature within the current context.


Rebaseline Sparta on Roci-HBM - Crossroads hardware in the open enclave

@amagela will rebaseline Sparta on Roci-HBM (same hardware as Crossroads)
Include description of number of cores we are running on for strong scaling and why, put this in the introduction.
Explain what we are doing, when we ramp up the number of cores, and why.. bindings, etc..
smallest Numa domain, 1/4, 1/2, full numa domains
Name game, Crossroads is the name.
Crossroads
We will define crossroads in the introduction documentation.

I added some introduction information on Crossroads in another issue.


Clarify the need for lambda VPC endpoint in the documentation

Forgive me if this has already been asked but I haven't found the answer in the documentation or in other issues.
I understand the need for the EC2 VPC endpoint to replace the routes in the route table when there are connectivity issues. But I don't see that the lambda VPC endpoint is needed for this. If I'm correct, the lambda endpoint is used for testing purposes only, Could you please confirm if this is the case?
I would be happy open a PR to update the documentation if thats the case. Maybe its not a big saving, but having an extra VPCe in 4 AZs could represent aroud 30$/month.
Thank you

Yes, that's true, I can't see think of any reason why a Lambda endpoint would be necessary. If connectivity is down through the NAT gateway, the Lambda would detect the issue and send requests to the EC2 API to switch the route. The Lambda API wouldn't be called. I don't see any reason why it's strictly necessary.
PR welcome!

I was trying to read the tests in more detail to update the documentation, but even in the tests I've got the impression that the lambda VPC endpoint is not used at all. Should the PR go in the direction of removing the VPC endpoint altogether instead of updating the documentation?
Cheers

Yeah, let's just remove it. This will be marked as a backward incompatible release, which I generally avoid, but since we don't need an endpoint to Lambda then we may as well remove it now rather than later.
We should strip out all the Lambda endpoint stuff from main.tf, variables.tf, and the README. Not sure if it's mentioned anywhere else.


Callback when done

Hi,
Thanks for a very nice tool.
Please is there a callback function when create or validate is done?

Up


[ETCM-470] Change node datadir location

Make it possible for the user to select / change the Mantis node data directory location.

Select initial data directory on first start
Change datadir location while running Mantis wallet (via a settings option)
the wallet will seamlessly restart the node in the background with the new data directory in use

It will initialize a new data directory when a Mantis directory doesn't exist at the path.
If there's already a data directory:

It will check the enclosed version.txt to see if the datadir is compatible with the current Mantis node
If there's no version.txt, it will ask the user if the wallet should put one there or proceed with the normal "incompatible version" flow - moving or deleting the old datadir.

Updated the following datadir-location dependent functions:

Logger
Log exporter

And added a way to get notifications from the store on update.
Important config changes:

dataDir became walletDataDir to better distinguish it from the Mantis datadir config option
mantis.dataDirName became mantis.dataDir to not confuse users (it's a path now)
If it's set, it will override the setting option on the UI and the field will be disabled.

Bonus:

Eliminate walletState.getOverviewProps
Fix load errors in storybook
Fix previously broken story: Wallet Restore
Fix isSyncing return type
Limit SyncStatus percentage decimals to 4
Fix typo in Support modal
Update storyshot settings for more consistent runs
Run storyshots:update before feature commit to update storyshots for previous PRs

FYI: Buildkite doesn't work anymore. It doesn't seem to be related to this PR, other builds fail too.

FYI: Buildkite doesn't work anymore. It doesn't seem to be related to this PR, other builds fail too.


Touchpad needs a lot of pressure applied

Hello, I updated my chroot today. When I went into xfce4 I thought at first that the mousepad was broken but then realised that i need to apply a lot of pressure to the mousepad in order to get it to react. Also, tap to click doesn't work.
I have the Samsung Chromebook XE303C12
Here is the output from croutonversion
chronos@localhost / $ sudo enter-chroot croutonversion
Entering /mnt/stateful_partition/crouton/chroots/precise...
crouton: version 1-20151104200003~master:2a1fc9da
release: precise
architecture: armhf
xmethod: xorg
targets: keyboard,xfce
host: version 7390.61.0 (Official Build) stable-channel daisy
kernel: Linux localhost 3.8.11 #1 SMP Thu Oct 15 02:21:14 PDT 2015 armv7l armv7l armv7l    GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/precise...

Is there anything else you need from me?
Edit: After a restart I went back into crouton and for the first few seconds the mousepad worked, but then quickly required more and more pressure to register. Thought that might help.

Exactly the same issue with my Acer Chromebook 14. Weird is, that it works fine in xfce4 but not in DWM (apt-get install dwm).

I haven't noticed any issues reported with the Samsung ARM Chromebook (daisy) but there have been some adjustments made on a few others. Take a look at this Pull Request#725 merged on Mar 29, 2014.
You might be able to use that method to adjust the trackpad sensitivity, it uses the synclient command with a couple of parameters, similar to:
synclient FingerLow=1 FingerHigh=5
You may have to experiment with the values but hopefully it'll make an improvement.
Hope this helps,
-DennisL


[openssl] add source vcpkg_from_github

Describe the pull request

What does your PR fix?
add source vcpkg_from_github

Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>

Does your PR follow the maintainer guide?
Your answer

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
<Yes / I am still working on this PR>

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@JackBoosY Ready for review. Please don't hold this PR, for your PR will need upstream approve.

Please don't hold this PR, for your PR will need upstream approve.

But this PR here isn't strictly needed, and still it forces rebuilds on us.

Please don't hold this PR, for your PR will need upstream approve.

But this PR here isn't strictly needed, and still it forces rebuilds on us.

I will close this PR once the @JackBoosY openssl 3.0.4 PR will merge.
If it will hold for any reason, My request is to review this PR first.
Thank you.


Unable to complete a feedback request

Expected behaviour:
When being done with providing feedback, clicking the "complete" action in the notification overview should send an email to the user and remove the plan from the overview
Actual behaviour:
Getting the following error message
" Error: Unable to notify user that you have finished providing feedback."
Steps to reproduce:
Click the "complete" button for any of the plans submitted for feedback on https://dmponline-test.dcc.ac.uk/org_admin/plans

Think this is actually due to the plan->org_id link that propagated up from the Master branch (so a data-issue with DMPonline-test)
I'm running the rake:task that came along with that work and will re-ping for testing once that's finished running

That's done running now

Works for me, @magdalenadrafiova do you want to confirm and close?

comments and hitting feedback complete worked well. closing :)


tags parameter for generating PDF in Latin1 (with german umlaut)

Hi,
I'm using your awesome lib in Titanium framework (it is similar node) I try to generate PDF's with german umlauts (äöüÄÖÜß). Please give me a hint or example how can I use it.
I'm using jsPDF standard_fonts_metrics plugin.
Cheers!

Duplicate of #12
UTF-8 Solution coming soon

wehn ?

since few months.


Postgres db connector

Initial commit for some feedback on what the postgres connector can improve as this is a really simple solution for the connection to the database and don't know what pitfalls it might have until I look at it better

Looks good, Thanks!

There is a known issue with the Redis Integration test in Github

Redis container added on Github Workflow, the test is green now.

@ehsaniara this was an initial draft there is a problem with this implementation. which if for some reason the lock doesn't get deleted it will be locked forever and it needs manual intervention. I would like to implement a clean up which would check if a lock is expired based on the ttl and the now time both when trying to acquire the lock and when starting up the client.


Usage of DigitalOcean Managed PostgreSQL with Supabase

Thank you for this repo!
I wonder if we can use the existing managed DO PostgreSQL cluster with Supabase services installed in the droplet using this repo? Running PostgreSQL inside a single droplet without replication looks like not the best idea for production (i.e. no HA), but if we can somehow use DO-managed PostgreSQL it will be totally different picture. I read in other places that some extensions are required in PostgreSQL to be running, otherwise, Supabase will not work with it (E.g. people tried to connect to AWS RDS and that did not work well). Do you know anything about it from managed DB on DO? Are there any other instructions/suggestions on how to run Supabase in DigitalOcean in "HA" mode?
Our requirement is simple: we run DO k8s and DO-managed PostgreSQL DB and we want to have Supabase running that utilize the SAME DO-managed PostgreSQL instance.  We could be just using Supabase hosting of course with our existing k8s cluster in DO, but they setup DB itself in AWS, not in DO, so I assume it's going to be huge latency (between DO k8s and AWS Supabase infra) if we do it that way.... Thoughts?

@evereq any updates on how you handled that issue? I'm at the same position, asking myself if its wise to use Supabase with Digital Ocean in the first place.

@appinteractive Unfortunately no, we did not find any "easy" way to do it. It will require a lot of work to deploy Supabase manually with PostgreSQL installed in droplets/pods in HA mode, together with backups, etc.
We analyzed many options we found on how to install PostgreSQL in HA in k8s:

https://github.com/zalando/postgres-operator (3.5k ⭐ )
https://github.com/CrunchyData/postgres-operator (3.4k ⭐ )
https://github.com/cloudnative-pg/cloudnative-pg (1.7k ⭐ )
https://github.com/ongres/stackgres (637 ⭐ )
https://github.com/bitnami/charts/blob/main/bitnami/postgresql-ha
https://github.com/zalando/patroni (5.9k ⭐ )

None was "easy" to run and we gave up for now 😢
DigitalOcean provided us with huge free credits for running our open-source projects (http://github.com/ever-co) recently (https://www.digitalocean.com/open-source/credits-for-projects), so we will most probably return to this task again soon, unless Supabase will make it "natively" possible to deploy clusters into DO (in addition to AWS / Azure / GCP), that would be amazing!

@evereq thanks for sharing your research! Really appreciate it 🙏

I surmise it depends on the component. Supabase does require the availability of custom pg extensions and cloud managed instances only support vetted ones. I suppose if one is only interested in self managing auth, for example, should be able to do so. (of course, without the support of pg_net, real time, etc.)


Removing meteorkitchen

Hey @Urigo
removing a dead link to meteorkitchen.
Cheers!

it works, it just didn't update the SSL certificate

hmm, yeah, that means it isn't accessible (unless you actively allow it).

I just checked and the link work perfectly. they certainly fixed their SSL issue.
I think this PR can be removed.

Just need to change it to https

It redirects too. Let's close it.


Replaced os.getcwd()

Replaced the os.getcwd() with Path.cwd()
Changes done only scoped to ruff errors
Refs: #783

Thank you again, @OmAximani0! Looks great. I will have this merged once tests pass. 🥳


Refresh token strategy

Hello, I have configured my identity provider, and everything is functioning properly. However, after approximately an hour, the access token expires and fails to refresh. The refresh only occurs after deleting the cookie. I have also enabled the 'offline_access' scope, as I have read that this is related to facilitating the refresh token expiration. What steps should I take to ensure that my access token is automatically refreshed before it expires?

What is the solution to this? I am currently seeing following log error:
ERROR:root:Error fetching user groups: 401 {"error":{"code":"InvalidAuthenticationToken","message":"Lifetime validation failed, the token is expired.","innerError":{"date":"2024-03-28T12:09:54","request-id":"...","client-request-id":"..."}}}

@KevinJaroschewski , what is the solution, I'm facing the same issue.


[Module Name] Describe the bug

Related module
Code in sustc-api
What happened
why there is nothing about video ,but it can still posted
What you expected to happen
No response
How to reproduce
No response
Anything else
No response

just cuz the logger has some problem displaying the Object[] args, you may fix it by explicitly print the elements in the array
we would not modify the framework cuz this doesn't affect the outcome, but if you'd like to contribute a fix of it, pr welcome


Re-export bech32 crate

rust-bitcoin is a lot further from 1.0 than bech32 is. We previously removed the re-export of bech32 because we thought it might hold us up releasing rust-bitcoin 1.0 but in hindsite this was incorrect.
Having a public re-export of dependencies helps users keep their deps in sync with those in rust-bitcoin and is thus useful.
Close: #3650

Are you using 0.32 @DanGould? Do you want this backported?

Stoked to see this!
rust-payjoin is on 0.32.2 and about to update to 0.32.4 We would immediately use it if released in a patch version.
https://github.com/payjoin/rust-payjoin/pull/410


Allow long URLs migration fails upgrading wagtail to 2.13.3

Issue Summary
Hello, I'm upgrading an existing Wagtail site 2.7.3 to 2.13.3. All worked fine on my test database, but when running the migrations on production data I encountered the following error when wagtailembeds.0008_allow_long_urls was applied:
psycopg2.errors.StringDataRightTruncation: value too long for type character varying(200)

After a bit of digging, I found that my production data has a couple of Embed objects with thumbnail_url lengths greater than 200.
This seemed OK, as Wagtail 2.7.3 has thumbnail_url max length of 255:
thumbnail_url = models.URLField(max_length=255, null=True, blank=True)

I tried a quick fix by updating the wagtailembeds.0008_allow_long_urls migration by adding max_length=255. It seemed to fix the problem and the migration ran OK on my production data.
However, I'm not sure if this is the preferred or right solution:
migrations.AlterField(
    model_name="embed",
    name="thumbnail_url",
    field=models.URLField(
        blank=True,
        default="",
        max_length=255,
    ),
    preserve_default=False,
),

Steps to Reproduce
I have only tried this on a existing Wagtail instance, but I suppose it could be recreated on a fresh (but older 2.7.3?) instance of Wagtail, creating an Embed object with a thumbnail_url greater that 200 in length and then migrating to the latest Wagtail (2.13.3).

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: No

Technical details

Python version: Python 3.6.4
Django version: 3.2.5
Wagtail version: 2.13.3
Browser version: N/A

Thanks for the report @marts! I think your suggested fix is correct - the AlterField operation in question is only needed as a workaround for a MySQL issue, and is immediately followed by changing it to a TextField where max_length doesn't apply. Other than the addition of default="", the field definition here should have matched the previous state, namely the one set in migration 0005 - but the max_length was missed here.
Marking this as for 2.13.4 - while 2.14 is coming pretty soon, we ought to put out a 2.12.x and 2.13.x release with this fix as it's a potential blocker for people doing point-by-point upgrades.

This fix is now released as 2.12.6 and 2.13.4.

@gasman much appreciated, thanks


Add a maximum server tab width of 17px

I confirm (by marking "x" in the [ ] below):

[X] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
[X] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[X] I have read contributing guidelines.

Summary
Add a maximum server tab width of 17px
Steps to reproduce
Create a very long server tab name, 40-50 characters long
Expected behavior
Server name is truncated (common in web browsers such as Firefox)

Observed behavior
The entire server name appears in the tab bar. This can cause issues where if you have two or three servers each with a long server name, the last one isn't visible on the desktop app UI

Possible fixes
Add a maximum server tab width of 17px. This should fit up to 20 character server names.
If the name doesn't fit within 17px, the server name should be truncated with ... at the end.

^@yuya-oc feel free to comment if you feel the 17px limit is too restrictive, but I estimated it based on the Firefox browser tab widths.
(in Chrome, the browser tab width auto-adjusts based on how many tabs you have open, but I don't think we need that since it's not likely for a user to belong to a lot of Mattermost instances at once)


Add support specifying LocakbelResources by Label

This is extension to lockableResource , adding ability to specify resource label, and because of this also made resource names optional

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

Please address the remaining isses and then squash all commits to a single one


ICS Error

Still getting an error:

Warning:  Undefined property: stdClass::$published_at in /var/www/vhosts/johnromanodorazio.com/httpdocs/LiturgicalCalendar/LitCalEngine.php on line 2731

Fatal error:  Uncaught Error: Call to undefined function ParseColorString() in /var/www/vhosts/johnromanodorazio.com/httpdocs/LiturgicalCalendar/LitCalEngine.php:2769
Stack trace:
#0 /var/www/vhosts/johnromanodorazio.com/httpdocs/LiturgicalCalendar/LitCalEngine.php(3073): LitCalEngine->generateResponse()
#1 /var/www/vhosts/johnromanodorazio.com/httpdocs/LiturgicalCalendar/LitCalEngine.php(73): LitCalEngine->Init()
#2 {main}
  thrown in /var/www/vhosts/johnromanodorazio.com/httpdocs/LiturgicalCalendar/LitCalEngine.php on line 2769

I believe you are using an old endpoint. The latest dev endpoint can be found at https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php . Here is an example of ICS for the United States in the year 2025:
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&nationalpreset=USA&returntype=ICS
There just happened to be another warning for the year 2025, since Saints Jean Brebeuf and companion martyrs falls on a Sunday that year, I was trying to output the name of the liturgical event when it didn't exist. Fixed in commit 10a6406a9a6d529c7218fcd5b45b4ae23a86367e .

When do these changes get added to the production server?

There isn't a deadline. They'll be added when the development is stable enough to be passed to the production server. I think it should be fairly ready within the next week or so though.

Thanks for being so responsive, and for a great app!

I believe that with the latest updates to the development branch, ICS generation should now be working correctly:

2f58d24756079cf690fb94b0c4d40b4ac11ad06c create LitCommon enum
22199b5b521b1647014252911b1a3721ec54b7b5 fix LitCommon i18n
e16d1faff4256797e790f451caebfac0fe9bb34e fix StJaneFrancesNewDate error for Sunday coincidence
87c6720bf14504cd32ab216fd7a3b9941ab9355f fix latin strings in LitCalAPI

I have run these tests, and they all seem to be working correctly for me:

https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2029&nationalpreset=USA&returntype=ICS
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&nationalpreset=USA&returntype=ICS
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&nationalpreset=ITALY&returntype=ICS
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&returntype=JSON
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&nationalpreset=ITALY&returntype=JSON
https://litcal.johnromanodorazio.com/api/dev/LitCalEngine.php?year=2025&nationalpreset=USA&returntype=JSON

Can you confirm on your end?

I've done a little more cleanup :

1c742a8458027e1e56c036999807eb7e45c7d847 make LitGrade constructable
4d6dd7a548bf51c1751627360b77aff966c687de make sure 'from the common' is translated into latin

Excellent, working fine for me.
Thanks.  Is it possible to let me know when this works its way into the production server - If a problem, no sweat.

On Dec 17, 2021, at 7:18 AM, JohnRDOrazio @.***> wrote:
I've done a little more cleanup :
1c742a8 https://github.com/Liturgical-Calendar/LiturgicalCalendarAPI/commit/1c742a8458027e1e56c036999807eb7e45c7d847 make LitGrade constructable
4d6dd7a https://github.com/Liturgical-Calendar/LiturgicalCalendarAPI/commit/4d6dd7a548bf51c1751627360b77aff966c687de make sure 'from the common' is translated into latin
—
Reply to this email directly, view it on GitHub https://github.com/Liturgical-Calendar/LiturgicalCalendarAPI/issues/67#issuecomment-996680087, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENJQIEDKQTXN55UCAVL4ILURMTC7ANCNFSM5KGFPAEQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

Hello @mdecaro , not sure how else to let you know, I have just released v3.0 of the API. The presentation website has been updated to reflect these changes, and had started using the v3 endpoint:

Website: https://litcal.johnromanodorazio.com/
Liturgical Calendar API (liturgical data endpoint): https://litcal.johnromanodorazio.com/api/v3/LitCalEngine.php
Liturgical Calendar API (metadata endpoint): https://litcal.johnromanodorazio.com/api/v3/LitCalMetadata.php
Liturgical Calendar API (Dates of Easter endpoint): https://litcal.johnromanodorazio.com/api/v3/DateOfEaster.php

Much appreciated, thanks.

On Dec 26, 2021, at 9:28 AM, JohnRDOrazio @.***> wrote:
Hello @mdecaro https://github.com/mdecaro , not sure how else to let you know, I have just released v3.0 of the API. The presentation website has been updated to reflect these changes, and had started using the v3 endpoint:
Website: https://litcal.johnromanodorazio.com/ https://litcal.johnromanodorazio.com/
Liturgical Calendar API (liturgical data endpoint): https://litcal.johnromanodorazio.com/api/v3/LitCalEngine.php https://litcal.johnromanodorazio.com/api/v3/LitCalEngine.php
Liturgical Calendar API (metadata endpoint): https://litcal.johnromanodorazio.com/api/v3/LitCalMetadata.php https://litcal.johnromanodorazio.com/api/v3/LitCalMetadata.php
Liturgical Calendar API (Dates of Easter endpoint): https://litcal.johnromanodorazio.com/api/v3/DateOfEaster.php https://litcal.johnromanodorazio.com/api/v3/DateOfEaster.php
—
Reply to this email directly, view it on GitHub https://github.com/Liturgical-Calendar/LiturgicalCalendarAPI/issues/67#issuecomment-1001191287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENJQIF35SUSZV4HWPNABGTUS4RCJANCNFSM5KGFPAEQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

Are you by chance on our slack workspace "Catholic Devs" ? Feel free to join if you haven't already!
https://join.slack.com/t/catholicdevs/shared_invite/zt-dz50teya-019q4Zake3JdmsWiTxRBBg


Allow for even more privacy friendliness by including all assets (css, js, fonts, ...) in the image

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the problem to be solved
Allow even more privacy friendliness.
Suggest a solution
It would be great if there was an option to bundle all required resources in the Docker image itself.
Additional context
#130

That would also be a feature that I would really like to have. Thanks for the cool software.

Thank you all for your engagement and for prioritizing this feature. I'm currently working on a new major version of the error pages. While I haven't yet figured out how to embed everything into a single static page, I'm actively working on it


Problem in adding hydrogen and water in ligand preparation for hydrated docking

When i prepare ligand with mk_prepare_ligand.py script, both hydrogens are not added automatically and water molecules are badly added to the file and even bind to the ligand. How can i fix this?
ligand.tar.gz

Hi, meeko does not add hydrogens since v0.3.0. The input molecule for meeko needs to be protonated.
The water positions are likely incorrect without hydrogens. But, Pymol often displays bonds between waters (even if the waters are in their expected positions) whenever two waters are close to each other.

Thank you for the quick reply.

You are welcome


can't find a configuration that will build and run

I know that this stuff is a moving target but am looking for advice. I am trying to build the master branch from source. The closest I got was by updating my node to version 12 LTS and running
npm install -g npm-check-updates
ncu -u
npm update
npm install

That let me get to the end of npm install.  Now I am trying to do npm start. I get
 ERROR  Failed to compile with 2 errors                                                           3:00:09 PM

 error  in ./src/index.js

Module Error (from ./node_modules/eslint-loader/dist/cjs.js):

  ✘  http://eslint.org/docs/rules/arrow-parens  Expected parentheses around arrow function argument
  src/index.js:58:11

and

 error  in ./src/index.js

Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Plugin/Preset files are not allowed to export objects, only functions. In /home/ubuntu/projects/stackedit/node_modules/babel-preset-stage-2/lib/index.js

When I try a npm run build I get another error:
Error: webpack.optimize.UglifyJsPlugin has been removed, please use config.optimization.minimize instead.

I really want to run stackedit in an environment where it gets all of the markdown from a server. Edit the markdown in the browser possibly offline. Publish back to the server. I am comfortable with the synchronization. I am also positive that I can't make as good a UX as StackEdit.

This is issue "build issues: postinstall fails with prism 1.9 #1411." I fixed it by changing the gulp dependency to:

--- a/package.json
+++ b/package.json
@@ -91,7 +91,7 @@
     "favicons-webpack-plugin": "^0.0.9",
     "file-loader": "^1.1.11",
     "friendly-errors-webpack-plugin": "^1.7.0",
-    "gulp": "^3.9.1",
+    "gulp": "^4.0.0",
     "gulp-concat": "^2.6.1",
     "html-webpack-plugin": "^3.2.0",
     "http-proxy-middleware": "^0.18.0",


Fix slf4j version range in POM so manifest uses [1.7,2) version range

Because of the version ranges used in the POM slf4j version 1.8.0-beta4 is resolved during builds.
As a result the manifest contains:
org.slf4j;version="[1.8,2)"
With this PR only 1.7.x versions are resolved so the manifest contains:
org.slf4j;version="[1.7,2)"
This way usage of the 1.8.0 beta version is no longer forced when using the bundle with OSGi.

Thanks for the PR. I don't like putting the specific version of slf4j (i.e. 1.7.100 in this case) as the right border for the version number. I have tried to deal with this issue myself using the [1.7.2,1.8) for version specification, which from my understanding means that all versions before 1.8 will be working. Does it work for you?
Probably putting same version for the following dependency may do the trick for you:
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <version>1.8.0-beta2</version>
            <scope>test</scope>
        </dependency>

will become:
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <version>[1.7.2,1.8)</version>
            <scope>test</scope>
        </dependency>

Does it make any sense? :)

I also tried using that version range on all slf4j dependencies but it doesn't help. The issue is that the ranges in the manifest are not determined by the ranges specific in the POM. They are determined by semantic versioning and the version that is on the classpath at compile time.
The 1.8 version in the manifest is caused by the range specified on slf4j-api. If you run mvn dependency:list you can see Maven prefers the beta artifact:
The following files have been resolved:
   junit:junit:jar:4.11:test
   com.fasterxml.jackson.core:jackson-annotations:jar:2.9.8:compile
   org.jmdns:jmdns:jar:3.5.5:compile
   com.fasterxml.jackson.core:jackson-databind:jar:2.9.8:compile
   org.slf4j:slf4j-api:jar:1.8.0-beta4:compile
   com.google.protobuf:protobuf-java:jar:2.6.0:compile
   org.hamcrest:hamcrest-core:jar:1.3:test
   com.fasterxml.jackson.core:jackson-core:jar:2.9.8:compile
   org.slf4j:slf4j-simple:jar:1.8.0-beta2:test

I read this is issue is normally resolved by only using repositories that contain stable/GA releases.
Other ways to fix this are:

Not using version ranges. Many also consider these version ranges a bad practice because it results in releases that are not easily 100% reproducible.
Making sure the slf4j-api artifacts are resolved using a repository that only has stable/GA artifacts.
Adding some configuration to the Maven bundle plugin so it uses 1.7 as version range lower bound instead.

Of all these options and the fact that this project uses version ranges I think the current solution makes the most sense.

This makes sense. Thank you very much for a detailed explanation. I have chosen and merged your solution.

Do you already have some plans for releasing 0.11.0 @vitalidze ?
We'd like to use the library as a bundle with https://github.com/openhab/openhab2-addons/pull/5274.

@vitalidze could You please take a look at this? This currently is a blocker.

I think I can release it today. I had some plans do more breaks in backwards compatibility by moving Multicast DNS to a sub-module with pluggable architecture, which will go to 0.12 then.

@wborn @Misiu I have just released the 0.11.0. It will be available in Maven Central within several hours. Enjoy! :D

Thanks a lot @vitalidze ! :+1:  I've updated my PR so we can use the bundle now. :-)


softupdate: requirements.txt update

I am getting an error when I try to install this:
INFO: pip is looking at multiple versions of langchain-google-vertexai to determine which version is compatible with other requirements. This could take a while.
The conflict is caused by:
The user requested langchain-core==0.2.13
langchain-cohere 0.1.9 depends on langchain-core<0.3 and >=0.2.2
langchain-google-genai 1.0.7 depends on langchain-core<0.3 and >=0.2.9
langchain[docarray] 0.2.7 depends on langchain-core<0.3.0 and >=0.2.12
langchain-anthropic 0.1.19 depends on langchain-core<0.3 and >=0.2.10
langchain-chroma 0.1.2 depends on langchain-core<0.3 and >=0.1.40
langchain-experimental 0.0.62 depends on langchain-core<0.3.0 and >=0.2.10
langchain-google-vertexai 0.1.3 depends on langchain-core<0.2.0 and >=0.1.42
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

Pip subprocess error:

WARNING: langchain 0.2.7 does not provide the extra 'docarray'
WARNING: langchain 0.2.7 does not provide the extra 'docarray'
ERROR: Cannot install -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 21), -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 23), -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 25), -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 26), -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 28), -r /Users/ben/generative_ai_with_langchain/requirements.txt (line 29), langchain-core==0.2.13 and langchain[docarray]==0.2.7 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

failed
CondaEnvException: Pip failed

@benman1
It is interesting:

The conflict is caused by:
The user requested langchain-core==0.2.13
langchain-cohere 0.1.9 depends on langchain-core<0.3 and >=0.2.2
langchain-google-genai 1.0.7 depends on langchain-core<0.3 and >=0.2.9
langchain[docarray] 0.2.7 depends on langchain-core<0.3.0 and >=0.2.12
langchain-anthropic 0.1.19 depends on langchain-core<0.3 and >=0.2.10
langchain-chroma 0.1.2 depends on langchain-core<0.3 and >=0.1.40
langchain-experimental 0.0.62 depends on langchain-core<0.3.0 and >=0.2.10
langchain-google-vertexai 0.1.3 depends on langchain-core<0.2.0 and >=0.1.42

The user requested langchain-core==0.2.13 - that is not in conflict with any of ^ but langchain-google-vertexai.
I see the langchain-google-vertexai current version is "1.0.8". Something wrong here.

@leo-gan I'll close this.


Add new find methods to enable more complex search criteria

In particular, to allow searching using operators (=, >, <, !=, between, in, etc).
(Thought there was already an issue for this, but couldn't find it @grahamwallis -- do you know?)
From a verbal discussion, leaning towards implementing this as a new set of find methods rather than updating the existing ones (eg. by sub-classing the existing InstanceProperties), as the latter approach would probably break existing repositories that have no way of handling such an extended InstanceProperties.

@cmgrote - I thought we had raised an issue about that but I cannot find it.
This would be a nice enhancement. My original thinking was to subclass the InstanceProperties to create a more powerful MatchProperties object. However, I do take your point about how a repository connector would manage to tell the difference and behave sensibly if it does not support the sub-class.
A key consideration for the design of the enhanced API is whether, instead of matchCriteria applying to all property-conditions, there should be separate conditions and combinators allowing more complex conditions to be constructed (e.g. (A or B) and !(C and D). Need to be careful though not to make either the class interface (or grammar) too complex for its own good.

Good point — wondering if we do this in stages and do not initially handle nested / sub-expressions (leave that to if / when we eventually develop a search-specific “language” or for a search index)?

Based on our Tuesday call, I'm moving ahead with a structure like the following:
{
  "class": "EntityFindRequest",
  "typeGUID": "0db3e6ec-f5ef-4d75-ae38-b7ee6fd6ec0a",
  "pageSize": 10,
  "matchProperties": {
    "conditions": [
      {
        "property": "displayName",
        "operator": "like",
        "value": {
          "instancePropertyCategory": "PRIMITIVE",
          "primitiveDefCategory": "OM_PRIMITIVE_TYPE_STRING",
          "primitiveValue": "(?i).*\\Qaddress\\E.*"
        }
      },
      {
        "property": "updatedTime",
        "operator": ">",
        "value": {
          "instancePropertyCategory": "PRIMITIVE",
          "primitiveDefCategory": "OM_PRIMITIVE_TYPE_DATE",
          "primitiveValue": "123456789"
        }
      },
      {
        "nestedConditions": {
          "conditions": [
            {
              "property": "...",
              "operator": "...",
              "value": {
                "instancePropertyCategory": "...",
                "primitiveDefCategory" : "...",
                "primitiveValue" : "..."
              }
            }
          ],
          "matchCriteria": "ANY"
        }
      }
    ],
    "matchCriteria": "ALL"
  },
  "limitResultsByStatus": [ "ACTIVE" ],
  "matchClassifications": {
    "conditions": [
      {
        "name": "Confidentiality",
        "matchProperties": {
          "conditions": [
            {
              "property": "...",
              "operator": "...",
              "value": {
                "instancePropertyCategory": "...",
                "primitiveDefCategory" : "...",
                "primitiveValue" : "..."
              }
            }
          ],
          "matchCriteria": "ALL"
        }
      }
    ],
    "matchCriteria": "ALL"
  }
}

Notes:

Allows for multiple conditions against the same property (so it is possible to achieve a "range" or "between" semantic by using the same property in two conditions, each with different operators).
Allows for an arbitrary number of sub-conditions nested within other conditions (under the nestedConditions).
Adds similar property-based conditions within the classifications, to allow classification property-based matching.
I originally suggested the ability to provide a list of type GUIDs to search, but in considering it further I think this will make the interface significantly more complex (and different from the other interfaces) -- as we would need to embed all of the classification match conditions, statuses, etc under the type as well: basically creating a super-structure that matches that above, but all in a single search request.  I would therefore suggest we continue to do these searches against a single type (and continue to leverage super-types for broader searches, and the search index approach for more optimised multi-type searches).
I also originally suggested having a more complex semantic for the statuses (re-using MatchCriteria) but realised this does not make sense: you cannot have an ALL on statuses, as a given instance will have only a single status at a time.  Therefore I reverted this back to just a list of the statuses that should be used to limit the results.

I will implement the following validations of such requests:

Using nestedConditions or the property, value, operator combination should be mutually-exclusive to avoid any confusion over precedence (checked recursively given the arbitrary nesting possible)
Certain operators should only apply to certain types of information:

the IN_LIST operator will require an ArrayPropertyValue value
the <, <=, >=, and > operators will require a numeric or a date (primitive) value
the LIKE operator will require a string (primitive) value

Any violations of the above will result in an InvalidParameterException on the findEntities / findRelationships method as part of its validation

Another idea:

[ ] Add a "sub-type filter" criteria, so that while you can only search for one main type, which the properties used for matching need to exist on, you can also provide a list of sub-type GUIDs for that type that you want to appear in the results (to further narrow, but not fundamentally search across non-overlapping types).

Am starting to look into implementing these operations in the IGC connector, so would like to push this forward to the 1.7 release as tech preview to be able to start building against.

We've identified this will be important to achieve optimal performance in the Open Lineage Services scanning (and initial load)...

@grahamwallis I believe the base code and implementation for the in-memory repository are now done (as well as an initial implementation on the entity find method in the IGC connector).  I think we still need to implement this for the graph repository, though, so adding you as an assignee 🙏

PR #4290 adds findEntities and findRelationships methods to the Graph Repository.
The CTS does not yet cover these find methods, but the above PR has been manually tested with both linear and nested SearchProperties.
There is one operator that cannot yet be supported in the graph repository, namely the 'IN' operator. This is due to a bug in JanusGraph in which the type checking of the value supplied to the 'within' predicate incorrectly checks against the type of the property rather than accepting an array of elements of that type. This happens when the has..within step is nested with a logical step such as OR, AND, etc. This is fatal for SearchProperties in which the hierarchically nested structure of the SearchProperties requires that the graph traversal is constructed from the leaves upward, with each each set of branches being combined using the MatchCriteria specified for that 'level' in the SearchProperties. The result is that it is always the case that a has..within set will be nested. The JG bug is covered by (JG) issue 2188.
PR #2857 includes all the code needed to support the 'IN' operator, including the array property handling and the use of the has..within step has been verified by temporarily coercing the traversal to avoid the issue above. This coercion has since been reverted and the 'IN' operator support has been temporarily replaced by code that throw a FunctionNotSupportedException. When JanusGraph 0.6.0 is available ( no date yet) the appropriate lines of code in GraphOMRSMetadataStore should be uncommented and the throw clauses removed. That should be all that is needed to restore support for the 'IN' operator.

I believe the incorporation of findEntities and findRelationships is now complete based on the above mentioned PRs.

I believe the incorporation of findEntities and findRelationships is now complete based on the above mentioned PRs.


Remove PoET round 4 work around

Motivation
Closes #5030
Changes

remove mitigation for PoET round 4
mitigation code itself is not removed in case we need it in the future

Test Plan

n/a

TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed
[x] Update changelog as needed

bors merge

bors merge


I got error: Android Gradle Plugin 8.0.0 with Kotlin 1.8.20 causes OkHttp3 R8 minify problem

After upgrading to Kotlin 1.8.20 with Android Gradle Plugin (AGP) 8.0.0, I suddendly get the following error messages when running the :app:minifyProdWithR8 Gradle task :
Missing class org.bouncycastle.jsse.BCSSLSocket (referenced from: void okhttp3.internal.platform.BouncyCastlePlatform.configureTlsExtensions(javax.net.ssl.SSLSocket, java.lang.String, java.util.List) and 5 other contexts)
Missing class org.bouncycastle.jsse.provider.BouncyCastleJsseProvider (referenced from: void okhttp3.internal.platform.BouncyCastlePlatform.())
Missing class org.conscrypt.Conscrypt$Version (referenced from: boolean okhttp3.internal.platform.ConscryptPlatform$Companion.atLeastVersion(int, int, int))
Missing class org.conscrypt.Conscrypt (referenced from: boolean okhttp3.internal.platform.ConscryptPlatform$Companion.atLeastVersion(int, int, int) and 4 other contexts)
Missing class org.conscrypt.ConscryptHostnameVerifier (referenced from: okhttp3.internal.platform.ConscryptPlatform$DisabledHostnameVerifier)
Missing class org.openjsse.javax.net.ssl.SSLParameters (referenced from: void okhttp3.internal.platform.OpenJSSEPlatform.configureTlsExtensions(javax.net.ssl.SSLSocket, java.lang.String, java.util.List))
Missing class org.openjsse.javax.net.ssl.SSLSocket (referenced from: void okhttp3.internal.platform.OpenJSSEPlatform.configureTlsExtensions(javax.net.ssl.SSLSocket, java.lang.String, java.util.List) and 1 other context)
Missing class org.openjsse.net.ssl.OpenJSSE (referenced from: void okhttp3.internal.platform.OpenJSSEPlatform.())
Missing class org.slf4j.impl.StaticLoggerBinder (referenced from: void org.slf4j.LoggerFactory.bind() and 3 other contexts)

Based on the following this pull request on the OkHttp Library itself, you added the following rules to my proguard-rules.pro file:
-dontwarn okhttp3.internal.platform.**
-dontwarn org.conscrypt.**
-dontwarn org.bouncycastle.**
-dontwarn org.openjsse.**
-dontwarn org.slf4j.impl.StaticLoggerBinder


create API how to and documentation

The API needs an how to and a complete documentation for all via REST available routes.

look at phpugl/DimeTimetrackerBundle#7


Should typedoc-default-themes be an optional dependency?

In the case where a user provides their own theme, it is redundant to pull the (relatively large) typedoc-default-themes package. Rather it should be defined as an optional dependency so consumers that use their own theme don't download it.

I don't think so. optionalDependencies are still installed, they are just allowed to fail on things like the build step. Also, I think the package should remain a seamless experience for all users. I'll see what I can do about shrinking the installation size.

True that they are installed anyway by default, but not if installed with npm install --no-optional (https://docs.npmjs.com/cli/install) which would be done in ci/cd etc where install performance is desireable

Keeping it as a dependency. I don't see any compelling reason to change it since 99% of people will be using this.


Duplicate Maven POM plugin entries, and invalid element? etc..

I forked the repo and opened it in IntelliJ, and there are duplicate plugins

Maven JavaDoc Plugin
Maven Source Plugin

Is there any reason these are listed twice?
Also there is an error in the POM under the Nexus Staging Maven Plugin

I have made no modifications to anything in this project, simply imported it.
And 1 last issue I see is the lack of specific formatting in the POM? Would it be ok if I added proper spacing in between the blocks to make it more readable?
The project doesn't specify target version and this causes IntelliJ  to assume 1.5, this language level clashes with certain language features you use such as

and

I am not using maven for development, I use this pom mainly for creating and uploading the required artifacts for maven central through Sonatype. I could try to run this with your requested fixes and see what will happen.

I've made what I believe to be necessary changes to the pom in this gist. @uklimaschewski
POM Gist

Thanks @Sxtanna, I will try it out this weekend, if I find some time.

Ok thank you, looking forward to it. @uklimaschewski

@Sxtanna
I have tested your new pom.xml and it worked without error.
Though there is one problem with it: Only the javacode jar was uploaded to Sonatype and Maven central for version 1.14.
The javadoc and sources jars are missing. Possibly that is the reason why they were twice in the pom.
You can see the result at Maven central:
http://search.maven.org/#search|gav|1|g%3A"com.udojava" AND a%3A"EvalEx"
And the log of the build process is here:
http://www.rultor.com/t/13000-1

Addressed in #129 and resolved in #131


PoS Implement Bitset data structure

Current dependencies on/for this PR:

feature/pos-messaging-schema

PR #555

PR #558

PR #564   👈

This comment was auto-generated by Graphite.


documentation demonstrates incorrect key generation

in both the readme and crate docs you have this snippet:
    HttpServer::new(move || {
        App::new()
            .wrap(
                SessionMiddleware::builder(session_store.clone(), Key::generate())

this is very subtly incorrect as it will generate a different key for each server worker
please amend it to
    let key = Key::generate();

    HttpServer::new(move || {
        App::new()
            .wrap(
                SessionMiddleware::builder(session_store.clone(), key.clone())

and publish a new release so users of this crate can copy-paste from the updated crates.io page

Thank you for opening an issue for this, would have never noticed that

fixed the other occurence in #3


Copy ci_token_file file to the devscript directory

https://github.com/openstack-k8s-operators/ci-framework/pull/678 added the support for pull secret and ci-token var. It also introduces a typo in the ci_token file conditional.
This patch first copy the ci_token_file in the devscript (if devscript role is used via reproducer) and then cat the output of ci_token to avoid unwanted failure.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
/lgtm


ConfigurationPropertiesRebinder can't reset remove config bean filelds

https://github.com/spring-cloud/spring-cloud-commons/blob/f58895373b89b7f43c891f4f0b9fefa8e48b0187/spring-cloud-context/src/main/java/org/springframework/cloud/context/properties/ConfigurationPropertiesRebinder.java#L105
@ConfigurationProperties bean if has one value, i change config to remove filed value, this case bean filed value not refresh, not my expected！
any solution for this case ?

@spencergibb need help？i can impl this feature。
i will use BeanUtils.copyPropties(BeanUtils.instantiateClass(beanType), bean) reset bean fields;
and i suggest rebind will use event keys rebind part of the ConfigPropertiesBean，not all beans

I was just looking at this.
If I remove the property and then refresh, I see a similar behavior where the property value is not changed.
The version of ConfigurationPropertiesRebinder you linked to above is quite old.  What version of Spring Cloud are you using?
As always, we are happy to have PRs from the community, so if you have an idea on how to make this work please submit a PR.

Also I assume the problem is that you are removing the property completely and not just removing the value, correct?

When we remove the property there is no longer a property to update in the bean when the refresh occurs.  The property needs to be present in order to the JavaBeanBinder to set the value.  With the property missing, no update will occur.
https://github.com/spring-projects/spring-boot/blob/2.3.x/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/properties/bind/JavaBeanBinder.java#L92
https://github.com/spring-projects/spring-boot/blob/2.3.x/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/properties/bind/Binder.java#L369
https://github.com/spring-projects/spring-boot/blob/2.3.x/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/properties/bind/Binder.java#L418

I was just looking at this.
If I remove the property and then refresh, I see a similar behavior where the property value is not changed.
The version of ConfigurationPropertiesRebinder you linked to above is quite old. What version of Spring Cloud are you using?
As always, we are happy to have PRs from the community, so if you have an idea on how to make this work please submit a PR.

i use 2.0.1.REALEASE & 1.2.0 RC ;
They all have that problem

Also I assume the problem is that you are removing the property completely and not just removing the value, correct?

yes

When we remove the property there is no longer a property to update in the bean when the refresh occurs. The property needs to be present in order to the JavaBeanBinder to set the value. With the property missing, no update will occur.

i know this logic，but i think it`s unreasonable.
When we remove the properties on the remote configuration server, this change should be synchronized to the application, but not synchronized;

The trouble is that's all in spring boot. You could, rather than checking on the absence of a property, check one that disables something when set to false.

When we remove the property there is no longer a property to update in the bean when the refresh occurs. The property needs to be present in order to the JavaBeanBinder to set the value. With the property missing, no update will occur.

i know this logic，but i think it`s unreasonable.
When we remove the properties on the remote configuration server, this change should be synchronized to the application, but not synchronized;

in this case

The trouble is that's all in spring boot. You could, rather than checking on the absence of a property, check one that disables something when set to false.

This is also a solution, but requires users to adhere to the convention。

in the offline abTest case：
support remove flow:
remove the key -> delete code & redeploy
check enable flow:
change enable to false -> delete code & redeploy -> remove the key

Sometimes adhering to a convention for a maybe little used feature is better than the additional maintenance burden of trying to work around spring boot functionality

Sometimes adhering to a convention for a maybe little used feature is better than the additional maintenance burden of trying to work around spring boot functionality

i think this case not spring boot issue
ConfigurationPropertiesBindingPostProcessor just bind fields in source，because maybe other BeanPostProcessor set bean fields；
so should be reinit fields on rebinder，rebinder is rebind starting point，rebinder knows if the bean needs to be reinitialized

@fudali113
this is all we currently do
https://github.com/spring-cloud/spring-cloud-commons/blob/2.2.x/spring-cloud-context/src/main/java/org/springframework/cloud/context/properties/ConfigurationPropertiesRebinder.java#L105-L108
We pretty much rely on Boot and Framework to handle updating the Bean values and the logic that is currently there relies on the presence of the property key to do that.
You really have three options to make your use case work.

Instead of relying on the absence a value to trigger whatever logic you are trying to enable rely on the presence of a value
Just remove the value of the key and leave the key in the properties file
Remove the key and value and redeploy the app


Pause/stop pipeline without closing device

Would it make sense to add a method to pause or stop a loaded pipeline, i.e. the opposite operation of Device::startPipeline? Currently, the device must be closed and re-opened to start/stop a pipeline.
Perhaps an unrelated question to the above; but is it or will it be possible to switch between pipelines in the future without reopening the device?

Might be added although not planned for now.
Most likely no in the near future - a reset of the device gives a clean state that we need to start constructing and starting the pipeline. Because of underlying limitations of the firmware framework that we are using, doing so would require a dive into it and rework, as well as making sure that it plays nicely with everything else.


Indicate if it is gluten free

It doesn't indicate if it is gluten free.

Great point, I will make that change. Thank you.


Cant Resolves certain modules in dll.

And yes, both modules are in the dependency (Not devDependencies) section of my package.json
It just seems to be these two particular packages.

Try moving those dependencies to devDependencies. I think that might fix it

But they're not dev dependencies?
It's not going to help much for production build?
On 23 Feb 2018 00:50, "Amila Welihinda"<EMAIL_ADDRESS>wrote:

Try moving those dependencies to devDependencies. I think that might fix
it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chentsulin/electron-react-boilerplate/issues/1434#issuecomment-367873374,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFPshioF85zw0eFP4fYpa10ZST0HHwz_ks5tXgtFgaJpZM4SPaZy
.

Yea it's a little confusing. The devDependencies aren't bundled by the dll.

But when I make a production build the devdependencies wont be bundled in
the actual production bundle code? Therefore I'll get errors about those
modules being missing in production builds?
On 23 Feb 2018 07:07, "Amila Welihinda"<EMAIL_ADDRESS>wrote:
Yea it's a little confusing. The devDependencies aren't bundled by the dll.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chentsulin/electron-react-boilerplate/issues/1434#issuecomment-367928218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFPshkQ4jwFT6MmVXJQi_qelmpCmEZ6Tks5tXmO3gaJpZM4SPaZy
.

None of the dependencies and devDependencies are packaged in production


Feature: Update the Nigerian Pizza description

Description

This PR adds the feature of enhancing Nigeria's pizza recipe.
What type of PR is this? (check all applicable)

[ ] ☝ Add a pizza fact or trivia
[x] 🧑🍳 Add a pizza recipe
[ ] 🗺 Add a regional pizza
[ ] 📝 Documentation Update

Related Tickets & Documents

Fixes/Relates to #77
Added to documentation?

[x] 📜 README.md
[ ] 🙅 no documentation needed

[optional] What GIF best describes this PR or how it makes you feel?

Hey @madefromjames,
Thank you for your contribution! ✨
I have a little review here for you to fix.
Also, please address the things below:

Change the PR title to be more descriptive to your changes. For example, "Feature: Update the Nigerian Pizza description".
In the "Related Tickets and Documents" section, please link to your issue number, which is Add a pizza Recipe! (Please Keep This Issue Open) #77. You can see the issue number right beside your issue title, as in the screenshot below. And please add the word "Closes" before the issue number.

Please let me know if you have any questions.
Thank you! 😊

Hi @adiati98 I appreciate your follow-up with me, I have linked the issue number.

I have also committed changes to the header Nigeria Pizza
Please let me know what more needs to be done.


[feature request] option for recreating generalized tables

for development and testing it would be greatful if we would have an option to just drop and recreate the generalized tables without all the import stuff.

duplicate of #218


Ctrl+Shift+V pastes twice

Describe the bug
Pressing Ctrl+Shift+V in an input field pastes the text from clipboard twice.

OS: Windows Server 2012 R2
Browser: Franz, obviously
Version: 5.1.0
Release: 4.1.4 / win32 / x64

Additional context
Oof, GitHub forgot the text I had written, but since the issue is pretty simple, I hope it's okay that I don't follow the template.

Same for Franz 5.2.0 on Windows 10 Pro (64 bit) Version 1903 (OS Build 18362.239).
CTRL+SHIFT+V (paste as plain-text) pastes copied texts twice (happens at least with Facebook, WhatsApp, Hangouts and Telegram).

Same for Franz 5.3.3 on Windows 10 Pro (64 bit) version 1903 (OS Build 18362.356).  Ctrl+Shift+V pastes text twice (in Gmail, Hangouts, WhatsApp) Interestingly, this does NOT happened with Android Messages or Google Calendar services.

This also happens with 5.3.1 on Linux (KUbuntu 18.04) with Teams (I have not tried another service).

Bumping this. Also happening to me for a while now, currently on Franz 5.3.3, Windows 10 Home Version 10.0.17763 Build 17763.

I also have this issue, running Franz 5.4.0 on Windows 10 Pro 1903 18362.418.

Hello,
I have the same issue. It is annoying.
Thanks

I learned to deal with it for now by pressing CTRL + Z immediately after, which only undos the duplicate part. But I am a little amazed this obvious bug has persisted this long, especially considering it affects a presumably common keyboard shortcut.

Thanks for the tip, it works :)

Interestingly the exact same thing happens when using a similar app called Biscuit, which leads me to believe it's an Electron issue.

Same issue for me too.
I can't see any reports made for Electron directly, but appears someone has reported for Atom too, which is an Electron app if I'm correct: https://github.com/atom/atom/issues/1945

Same issue here ...

I have this issue in Station too, that use Electron

the same

It is fixed in Ferdi (fork of Franz) https://github.com/getferdi/ferdi/pull/1723 - can we port this patch to Franz too?


Dark mode issue

In dark mode, both background and font are black, unreadable unless change system theme to light.
Device: Redmi Note 7 Pro(violet)
Rom: Resurrection Remix 8.7.1
Screenshot

https://github.com/Dr-TSNG/ApplistDetector/commit/68c97eb4d18a30842f834b4d4eee2d0dd7bb4ef6
Has been fixed, please wait for the new building


[Enhancement] Try Gradio UI

Descriptions
We can add the Gradio to improve the user interface

build in release #v0.0.5


Spree 3.0 stable branch

Hello,
Could you create a 3-0-stable branch because your master is already at 3.1 and not 3.0 ?
Thanks.

Done

Thank you @JDutil !


java: Added auto load library code to the SWIG interface file

Signed-off-by: Stefan Andritoiu<EMAIL_ADDRESS>

Merged, Thanks!


Migrating form v0.100.2 to v1.0

It will be nice to have a document guide to migrate from v0.100.2 to v1.0. Else if it's already there can it be displayed in a more prominent place in the landing page. I had a lot of struggle in migrating my things.

Where would you expect the upgrade guide to be? We have one but have not publicized it well
https://github.com/Dogfalo/materialize/blob/v1-dev/v1-upgrade-guide.md

It will be a good resource to have on the homepage just below the position where the release version is written [ Release: 1.0.0-rc.1 ]

Added https://github.com/Dogfalo/materialize/pull/5897


Terminator Terminal Support

[ ] I have read the FAQs (https://dvlv.github.io/BoxBuddyRS/faqs)
[ ] My feature is not on the Roadmap (https://dvlv.github.io/BoxBuddyRS/ROADMAP)
[ ] I have searched for previous issues (https://github.com/Dvlv/BoxBuddyRS/issues?q=is%3Aissue+is%3Aclosed)

Describe your feature request below
It states in the FAQ to drop an issue for a request for a terminal support. Would it be feasible to add Terminator to this list?
Thanks

Hello
thanks for the suggestion, I have added Terminator support, and pushed to master.


install nsenter on k8s nodes

nsenter is not installed but expected by docker, accoding to these error messages:
NetworkPlugin kubenet failed on the status hook for pod "kube-dns-v19-2cb5w_kube-system": Unexpected command output nsenter: cannot open : No such file or directory

@jackfrancis any idea if this is still an issue?

Let's assume no based on age and lack of thread count


Fallback resolver & Latency

The greatest weakness of DNCrypt is for most people the latency, now we have a fallback resolver mechanism but the main issue isn't fixed. Whenever a resolver/server is slow it tries now to switch to another server, however, this is theoretically a good idea but in fact, it ends up with lots of roundtrips and you might see already in your Browser a DNS error until another resolver was found.
I gave DNSCrypt-Proxy (as a test for an article) 5 different people with different skills and 4 made a complaint about the same thing, the latency. So how we are going to resolve this issue? My idea would be that there could be a check/configuration option to ensure the resolver is not slower than let's say 60 ms which would also already sort out lots of servers on the list.
The problem is that latency is really an important thing because most people which simply want to browse or play online games they care more about this part than the 'security' aspect, in most cases from what I know it ends up that people going to disable it for this time but a workaround to solve this would be a better solution.
I would be thankful for ideas and a discussion ground because 'then disable it' is not really what I like to hear because that's still in my eyes a no-go. I do not really expect low-latency but at least no errors and or disconnects would be fine and I think lots of people could life with that.

The main issue with DNS, especially over UDP, is that when you don't get a response, there are no reliable way to know what happened. Was the response lost? Is the server slow? Did it ignore this specific query, but is otherwise fine with other query types or queries for other domains?
The only way to know if the server is actually slow or dead is to perform multiple attempts to gradually converge towards an educated guess.
After the proxy is started, there is a warmup period, where all the resolvers are given an equal probability to be chosen as the current best resolver. That warmup period can be shortened. On hosts that are not very chatty, the current value can be too short, but on hosts sending a lot of queries after a network change (such as macOS), it's too long.
That can be a knob, as well as the maximum latency after which we ignore a server. But these knobs would be hard to tune correctly.
Something I'd like to implement is serving cold responses, possibly from a persistent cache. That is, after a timeout, if we sent the same request previously, and even if more time passed than the TTL for this response, we return the response instead of an error. As obvious as it sounds, and in spite of this becoming a common practice, there might be some patents around it, though :(

When I was using dnscrypt-proxy v1, I started 4 processes configured to use different servers and different local addresses. Below there was a dnsmasq which used these 4 local addresses and an option "all servers" in its config file. So, for every DNS query dnsmasq resent these to 4 different DNScrypt-proxies and used first received answer. This configuration was very fast with really low latency. Of course, using 4 different servers means unnecessary network and servers load but I think that this was compensated by using dnsmasq cache.
Unfortunately I still haven't time to study the code for load balancing features of the dnscrypt-proxy v2 (and I don't have much knowledge of Go), so I can only suggest a similar idea: what if dnscrypt-proxy asks not just one but several servers for each query, returns first answer to the consumer and at the same time gathers statistics (server reachability, latency, etc.) for future use to find a pool of most accessible servers.
Is there any docs regarding load balancing, requesting strategy, etc.? It would by quite interesting to read.

Broadcast every single query to all (currently 67) servers? Please, no, you're not the only user of these servers.
This also means that each query has to be encrypted and decrypted for every single server. That would be very bandwidth and CPU intensive, even client side.

Of course, not to all servers, just a few. And, perhaps this might be needed only for first one hundred requests or so. After that you will have some statistics which shows the best servers for your location and you can use one or two. This might really speed things up. And, since you have cache, I don't think that load will be too high.
Just a note: when I switched from v1 to v2, the DNS requests sometimes take tens of seconds, and sometimes the address was not found though if I check "dig host @<IP_ADDRESS>" it returns valid address.

 So, does it mean that using only one server selected by dnscrypt-proxy produces the problem? Or, other solution can be suggested for negative answers? What about asking two or more servers in parallel?

Looks like dnscrypt-proxy just relayed what it received.
It received NXDOMAIN. So it relayed NXDOMAIN. There are no timeouts or SERVFAIL here.
Asking the same question to multiple servers is probably the worse strategy we can use.
Try different resolvers maybe?

You can check what resolvers is currently being used with dnscrypt-proxy -resolve linuxjournal.cmail19.com

Sure, it relayed what it received,  NXDOMAIN, but why? Host exists, according to google nameserver.

Why Cisco? I'm writing about the setup on my Linux computer.

Do you know what resolvers are returning NXDOMAIN for this query?

How can I ask a dnscrypt-proxy running in background about any particular query?

BTW, you have a list of all available DNS-crypt resolvers... Why don't you ask all of them about this query?

dnscrypt-proxy -resolve linuxjournal.cmail19.com

$ /opt/dnscrypt-proxy/dnscrypt-proxy -resolve linuxjournal.cmail19.com
Resolving [linuxjournal.cmail19.com]
Domain exists:  probably not, or blocked by the proxy
Canonical name: -
IP addresses:   -
TXT records:    -
Resolver IP:    <IP_ADDRESS>

$ drill linuxjournal.cmail19.com @<IP_ADDRESS>

;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 47678

Not even using DNSCrypt at all here. Looks like this resolver (CS Spain) is buggy or has been blacklisted by linuxjournal servers.
Not sure why. I heard a while back that Cryptostorm was filtering some domain names. This might actually be the case, and the exact criteria are unclear.
Can you try to confirm that with them? If they are filtering things, the filtering flag must be added to their properties.

Looks like this is what they do: https://cryptostorm.org/viewtopic.php?f=46&t=8981
The intent is to filter ads and trackers but there might be false positives.
So I guess we need to add the filter flag to all of them :/

Done.

A bit offtopic: Could you please explain, what the different load-balancing strategies in the *.toml do? A short non-technical answer would be enough, than you. ;-)

This should be in the documentation :)
Ok, this thread has been hijacked and doesn't really make sense any more. Gonna open a new ticket dedicated to load balancing instead.


project desktop version of portiflio

complete the desktop version of the home page

-Make sure your portfolio desktop version matches the Figma design

Thanks @beteland123 and @BenMKT for your feedback.
I'm working on this issue, and hope to present the whole desktop version today.

Thanks for your suggestions. All are done.


Browser based installer

Have had some feedback that some users would like a wordpress style browser based installation/upgrade process

For now closing this as cli installer is the main focus


ApiGatewayToDynamoDB: customize resource name on REST API

Hello, I would like to customize the generated resource name on my REST API when using ApiGatewayToDynamoDB.
Use Case
Currently, the resource name is generated from the DynamoDB partition key
https://github.com/awslabs/aws-solutions-constructs/blob/0bc9043be48b2ad635888e0359404e9b9dfc9337/source/patterns/%40aws-solutions-constructs/aws-apigateway-dynamodb/lib/index.ts#L152
However, I am trying to implement a more complex use case where my integration will query on the sort key. It feel weird to have to write:
readRequestTemplate: `{ \
  "TableName": "${dynamodbTable.tableName}", \
  "KeyConditionExpression": "PK = :v2 AND SK = :v1", \
  "ExpressionAttributeValues": { \
    ":v1": { \
      "S": "$input.params('PK')" \
    }, \
    ":v2": { \
      "S": "MY_VALUE" \
    } \
  } \
}`,

I understand that this is the default use case, but it should be customizable IMO.
Proposed Solution
Add an optional resourceName string parameter on the construct and use it to define the resource name if it is passed. Otherwise, use the table's partition key like in the current implementation.
Other

[x] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

We understand the concept and can see the value - but when we read the snippet it looks reasonable to us. We will take a look at what an implementation involves - but could you provide an example of what the snippet would look like after the change you're proposing?  (BTW - there's a significant change to API Gateway constructs coming imminently although this item is not addressed.)

The weird thing in the example I gave is that the SK = :v1 condition in the KeyConditionExpression uses a param named PK in the path (":v1": { "S": "$input.params('PK')" }). This would kind of seem like I mixed up my partition and sort keys.
My proposed change is to:

add an optional resourceName argument to the construct
if this resourceName is not defined, default to the partitionKeyName
when adding the resource, use this.apiGateway.root.addResource("{" + resourceName + "}");
then, say that for example, I have set resourceName: 'userId' as a construct argument, I'll be able to write  readRequestTemplate: `{ \
     "TableName": "${dynamodbTable.tableName}", \
     "KeyConditionExpression": "PK = :v2 AND SK = :v1", \
     "ExpressionAttributeValues": { \
       ":v1": { \
         "S": "$input.params('userId')" \
       }, \
       ":v2": { \
         "S": "MY_VALUE" \
       } \
     } \
   }`,

which would be less confusing IMO.
I'll try and drop a PR to address this, WDYT?

We had put this on our list to implement, but will hold off if you want to give it a try. As we see it, there's a new optional attribute on the Construct props, resourceName. If supplied, this is used in place of partitionKeyName on line 249. It's also used in every input.params('${partitionKeyName}' statement, but "KeyConditionExpression": "${partitionKeyName} = :v1", \ statements remain unchanged. Your use case will still require a custom template, as you are swapping Sort Key for Primary Key.
This is only applicable to this construct, the default resource names on the other apigateway constructs are specific to the content (Records, Message, etc.). We'd want to see at least one more unit test and one more integration test.
Let us know if you want to take it on.

That's correct! I'll still need a custom template indeed

So just to clarify - will you be submitting a PR, or should we add it to our board?

I should be able to submit a PR at the beginning of next week!


Convert to NuGet

Convert to use NuGet and fix version constraints.

I am seeing CHANGELOGs, but they do not seem like they are being used.
Somewhat related is a question of versioning. I don't see any mention of concrete versions anywhere except in the .github/* directory. Did I miss something related to how we are versioning packages?

I'll get those updated.


Pair of nodes in the BST which sum to S

📚 Documentation
find pair of nodes in the BST which sum to S. BST and an integer(sum) will be given as input.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


crash

Before you create a new issue, please search for similar issues. It's possible somebody has encountered this bug already. PLEASE REMOVE THIS LINE TO ACKNOWLEDGE THAT AN ISSUE DOESN'T ALREADY EXIST FOR THIS BUG
Describe the bug
Caused by java.lang.NullPointerException
Attempt to invoke virtual method 'android.content.Context android.content.Context.getApplicationContext()' on a null object reference
com.paypal.authcore.util.BasePreferences.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Android Version: [e.g. API 30]
Device: [e.g. Emulator or One Plus 9]
Browser [e.g. chrome, safari] <- only applicable for app switches or fallback situations
SDK Version [e.g. 0.1.0]

Additional context
Add any other context about the problem here.

@HuixingWong Please provide steps to reproduce the bug.
Also, please fill in the requested information (SDK version, Device, OS version, etc.)

@HuixingWong we've passed this to the auth team. Once they fix it, we'll let you know.


Calling lazy() on a filename that doesn't exist produces confusing error

This is what happens if you call lazy() on a path that doesn't exist:
>>> import uproot4
>>> uproot4.lazy('nonexistent_file.root')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/mproffit/miniconda3/lib/python3.8/site-packages/uproot4/behaviors/TBranch.py", line 585, in lazy
    raise ValueError(
ValueError: allow_missing=True and no TTrees found in

Obviously this doesn't really indicate the actual problem--that the file doesn't exist. It also strangely claims that allow_missing=True, which is not correct since the default is False. It says the same thing even if you explicitly set allow_missing=False:
>>> uproot4.lazy('nonexistent_file.root', allow_missing=False)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/mproffit/miniconda3/lib/python3.8/site-packages/uproot4/behaviors/TBranch.py", line 585, in lazy
    raise ValueError(
ValueError: allow_missing=True and no TTrees found in

Just leaving a note for fixing this in the future; it's somewhere in here:
https://github.com/scikit-hep/uproot4/blob/7e42e2f71d9fb20dbfb12d177403b3b0839d0cc2/uproot4/behaviors/TBranch.py#L2707-L2786


Added Username field

Codecov Report

Merging #98 (17e0df9) into master (d82f153) will decrease coverage by 0.32%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master      #98      +/-   ##
============================================
- Coverage     63.09%   62.76%   -0.33%
- Complexity      466      472       +6
============================================
  Files            95       96       +1
  Lines          1764     1786      +22
  Branches        184      188       +4
============================================
+ Hits           1113     1121       +8
- Misses          591      601      +10
- Partials         60       64       +4

Impacted Files
Coverage Δ

.../java/seedu/address/logic/commands/AddCommand.java
85.71% <0.00%> (-14.29%)
:arrow_down:

...a/seedu/address/logic/commands/AddTaskCommand.java
0.00% <ø> (ø)

...a/seedu/address/logic/parser/AddCommandParser.java
0.00% <0.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
75.55% <0.00%> (-9.45%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
12.50% <ø> (ø)

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

...a/seedu/address/model/person/UniquePersonList.java
89.13% <60.00%> (-3.56%)
:arrow_down:

...main/java/seedu/address/model/person/Username.java
80.00% <80.00%> (ø)

...java/seedu/address/logic/commands/EditCommand.java
88.05% <85.71%> (+0.18%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


Frontend: Email/messaging

I (Ryan McCoding) have completed the message page wireframe
👍👍👍

Cool! I recommend you focus on functionality for now, and instead of username just test with user ids. Ideally we have that be a dropdown menu of available people to message for convenience (like Canvas).
I'm also gonna do some redesigning of that wireframe so don't go too hard on frontend for now


Not able to update comments

pynetbox version
v7.3.3
NetBox version
v4.0.2
Python version
3.11
Steps to Reproduce
Please note I am using Python 3.12 version, as it is not there in the drop-down above I selected 3.11
I am trying to update comments on a device, but it is not accepting comments as an argument
  File "/Users/vishnu/drive/network-infra-ops/provision/scripts/netbox_update.py", line 74, in check_device_parameters
    self.nb.dcim.devices.update(x, comments=device['comments'])
TypeError: Endpoint.update() got an unexpected keyword argument 'comments'

Expected Behavior
it should be able to update the comments section of the device
Observed Behavior
giving error as TypeError: Endpoint.update() got an unexpected keyword argument 'comments'

Please ignore this ticket. I was passing the argument in wrong way.


Fix invalid pointer - integer comparison warning

On Windows, HANDLE is a void*. The value for the invalid handle is
roughly (HANDLE)(-1), so just cast the value to avoid a warning.

Thank you!


Support only specifying some joints in the space.

Partially resolves https://github.com/personalrobotics/rewd_controllers/issues/13.

Also, shouldn't this PR target to master branch instead of test/brianhou/rightarm branch?

Thanks for helping with the changes. Looks good, but I'll double-check by testing things over the weekend before merging.

We can't test this until the left arm is fixed, so I'm just going to merge this.


Helm uninstall will not delete the CRDs

We have several problems when using helm chart:

CRDs will not be deleted, we should leverage the hooks like     "helm.sh/hook": pre-delete
Namespace should be deleted manually, if this can be automatically, it  will be great
LWS namespace and controller should be deleted automatically, right now, we have to handle it manually.

/help


Move Developer Related Documentation to CONTRIBUTING.md

Move developer related documentation to CONTRIBUTING.md and add some information to README.md including the build badges.
Fixes #15

Works as expected after merging in the add-nav-bar and add-scroll-bar. Thanks for cleaning up the readme documentation.

@faithghlee : And thanks for the review. :smile:


test-branch/execute-job/quoted-authorization/50b615d9-9d90-4fb3-9dc8-f182c2b2e178

PR for testing 246d8f55196306d3ddd1f3a86ee011f8382b0e63

/canonical/self-hosted-runners/run-workflows 246d8f55196306d3ddd1f3a86ee011f8382b0e63


bugfix: correctly detect unicode support when &fencoding is empty

Without this, vim 8.1 (debian) and latest vim 9, will use ascii
box-drawing characters on my Debian system.
(Note: I suspect autoload/calendar/google/calendar.vim also might
need the same fix, but I am unable to test that.)

Thanks!