Random connection issue

Software
Version

PHP
8.1.8

Elasticsearch
8.12.1

Laravel
9.52.16

Laravel Scout
9.8.1

Describe the bug
Thanks for providing this package. However I encoutered an error that I don't know how to solve. Hope you could direct me to the right way.
My app keeps getting this error randomly. I have an instance deployed on Elastic.co.
No alive nodes. All the 1 nodes seem to be down.

Initially thought it was the instance is too small so I upgraded. But still seeing this error randomly. Sometimes it happens with search operation. Initially thought it was caused by syncing 600k records. I have a dedicated queue worker running scout sync jobs. But 600k shouldn't cause such error otherwise ES is a total failure comparing to Algolia.
I reached to Elastic.co's support. They mentioned:

Upon investigating the error message further, I found that it originates from the NodePool component of the client. As described in our official documentation here, the NodePool is responsible for maintaining the list of active nodes. While nodes are generally classified as either “alive” or “dead,” there are often gray areas such as “probably dead but not confirmed” or “timed-out but unclear why.” The NodePool manages these states and ensures the client’s requests are directed to available nodes.
When the NodePool cannot find an active node to connect to, it returns a NoNodeAvailableException, which is what we’re observing here.
The number of retries typically equals the number of nodes in the cluster. For example, if your cluster has 10 nodes, and 9 nodes fail, the request will execute on the 10th node. The first 9 are then marked as “dead” and will not be retried until their “dead” timers reset.
In your case, the error message continually shows No alive nodes. All 1 nodes seem to be down even though additional nodes were added to the cluster. This suggests a potential configuration issue with the NodePool component of the client.

After checking the code, I found out that:
return [
    'default' => env('ELASTIC_CONNECTION', 'default'),
    'connections' => [
    'default' => [
        'hosts' => [
            env('ELASTIC_HOST', 'localhost:9200'),
        ],
        'httpClientOptions' => [
            'timeout' => 2,
            'headers' => [
                'Authorization' => 'ApiKey ' . env('ELASTIC_API_KEY'),
            ],
        ],
    ],
],
];

I only have one URL from Elastic.co. But my deployment is running in 2 zones so more than 2 nodes. This ELASTIC_HOST only provided one node to the config. Could this be a reason? But still, I am very confused why this error happens at all.
To Reproduce
Unable to reproduce. Usually happens when syncing 600k records.

Hey @jasonfish568, this package uses elasticsearch-php under the hood and the client is initialized from the configuration hash as described here.
I can recommend you try a few things:

Increase the number of retries.
Use the ElasticsearchResurrect option for the node pool (see the documentation).

This means your config file would look similar to:
return [
    'default' => env('ELASTIC_CONNECTION', 'default'),
    'connections' => [
    'default' => [
        'hosts' => [
            env('ELASTIC_HOST', 'localhost:9200'),
        ],
        'httpClientOptions' => [
            'timeout' => 2,
            'headers' => [
                'Authorization' => 'ApiKey ' . env('ELASTIC_API_KEY'),
            ],
        ],
        'retries' => 10,
        'nodePool' => new SimpleNodePool(new RoundRobin(), new ElasticsearchResurrect()),
    ],
],
];

Please note that you have complete control over the client creation: you can use the config file, or create your own client builder as described here.
I hope this helps 🙂

Thanks so much for the information. Let me further investigate. I think the resurrect might be the solution.

Thanks Babenkoivan! It has solved the issue.


data/humanoids/humanoid_data/walking_motion_processed.pkl not exist

Error
I finally managed to run the script examples/interactive_play.py and now I can control the fetch robot.
But when I try to control the humanoid I face the following error:
File "habitat-lab/habitat-lab/habitat/articulated_agent_controllers/humanoid_rearrange_controller.py", line 53, in __init__
    raise RuntimeError(
RuntimeError: Path does data/humanoids/humanoid_data/walking_motion_processed.pkl not exist.
Reach out to the paper authors to obtain this data.
python-BaseException

Please advise if I can find this data somewhere (e.g. huggingface?) or I need to contact the authors for the data?
Habitat-Lab and Habitat-Sim versions
Habitat-Lab: v0.3.1
Habitat-Sim: v0.3.1
Other comment

I also think both of the following arguments need to passed for interactive_play with the humanoid:
python examples/interactive_play.py --control-humanoid --use-humanoid-controller

Hi, we need to update the instructions for interactive play, we will be doing this soon!
The motion files are per avatar, so you can find each one underr the folder of the avatar you want to control:
Here is one: data/humanoids/humanoid_data/female_2/female_2_motion_data_smplx.pkl

Thanks @xavierpuigf
I changed the following line:
https://github.com/facebookresearch/habitat-lab/blob/5e9efaa67d54b3edf88ac304b4db7d8673278500/examples/interactive_play.py#L82
to
DEFAULT_POSE_PATH = data/humanoids/female_0/female_0_motion_data_smplx.pkl"
now that is solved but, there is a new error:
Traceback (most recent call last):
  File "habitat-lab/examples/interactive_play.py", line 805, in <module>
    play_env(env, args, config)
  File "/habitat-lab/examples/interactive_play.py", line 499, in play_env
    humanoid_controller.reset(env._sim.articulated_agent.base_pos)
  File "habitat-lab/habitat-lab/habitat/articulated_agent_controllers/humanoid_base_controller.py", line 82, in reset
    self.prev_orientation = base_transformation.transform_vector(
AttributeError: only four-component swizzles are supported at most
corrupted size vs. prev_size

I also notice the class HumanoidBaseController is written by you.
In fact, reset() function expects a mn.Matrix4 but I see a Vector3 is being passed to it, i.e. env._sim.articulated_agent.base_pos!
Any idea?

I also faced a few other errors (like variables not initiated), and just managed to add temporal workarounds and move forward. (I will share later).
But still wondering where is the human.
I want to make sure I'm running the example correctly.
Is there any reference or tutorial for this @ASzot (as I see the example is written by you)?

@amiryanj. Thanks for the note. We should deprecate or update interactive play. We will be using a new interactive mode soon. Let me try to help with this though.
The humanoid controller should expect the base transformation, not the base position. Could you try doing:
humanoid_controller.reset(env.sim.articulated_agent.base_transformation)

You can see in the humanoid tutorial that this is how we reset it.
https://github.com/facebookresearch/habitat-lab/blob/main/examples/tutorials/humanoids_tutorial.ipynb


Enable parsing cookies with an empty or no key

This is basically a proposal for fixing #10 since I came across an instance where I'd need this.
I'm not sure about the handling of the "re-introduced" strict parameter. In order to not change behaviour when not given I set it to default to true for now, but I guess we'd need a better solution here?

Hi @Sebmaster. Thanks for the pull request! If you're interested, it needs a bit of work. Please note that SFDC requires a CLA to be signed in order to accept any PR (either by you or your employer).
We got rid of a similar strict flag when we moved from 1.x to 2.x, so I'd be hesitant to reintroduce it on the parse method. The problem is that folks do stuff like arrayOfStrings.map(Cookie.parse) which leads to some odd behavior since the function passed to Array#map has the signature function(currentValue, index, array). Since 0 is implicitly false, the very first string in the array gets parsed in "non-strict" and the subsequent, non-0 indexes are "strict". So, I'd like to please see a different API implementation. Perhaps tough-cookie needs some kind of global configuration options? Maybe change from "Class-static" to a "default-Factory-method" pattern (similar to how request and node's http.Agent allocate a default global to use)?
I'd like to try to maintain RFC compliance if possible, so unless this is how the RFC says to parse it (I honestly haven't looked yet), I don't think this feature should be "on" by default. You've implemented it as "off" by default, which is great, but I wanted to be clear that we can't just switch to LOOSE_COOKIE_PAIR all the time. Specifically, can you confirm that in the case of both cookie-strings abc and =abc that it's got no key but value abc?
Thanks again for taking the time to contribute this PR :100:

So, I'd like to please see a different API implementation.

I actually thought of another method in the meanwhile: Make the parameter an options object instead and check for explicit existence of a strict property in that object. If the given param is either not an object, or that key doesn't exist, we just ignore it.

Specifically, can you confirm that in the case of both cookie-strings abc and =abc that it's got no key but value abc?

So, according to the RFC this is not actually a valid cookie - I think. However, all browsers can properly parse this cookie. Sending a Set-Cookie equal to "=abc", leads browsers to send a Cookie: abc header back, so we can say "abc" == "=abc". Since setting a cookie with abc= sets a different cookie (abc=), we can conclude that the name of the cookie is empty and the value is abc in both parsing cases.

Please note that SFDC requires a CLA to be signed in order to accept any PR (either by you or your employer).

Where can I find this CLA?

@stash-sfdc @Sebmaster the thing is that nobody fully implements RFC spec :tada:  As far as I remember even IETF tests violate it at some cases in favor of common browser behavior. So, if it doesn't break existing tests and if this behavior is consistent across browsers, I'd rather keep it as non-optional.

@inikulin OK, agreed: if it's both IETF-test-compliant and consistent, then it should be the default behavior.

So we remove the non-strict param altogether? As far as I remember this starts breaking the (IETF part of the) test suite, so what should I do about that?

@Sebmaster please see https://github.com/forcedotcom/idecore/wiki/Contributing-Code regarding the CLA.

@Sebmaster OK, i follow the key-versus-value logic. Thanks for explaining that clearly!
If on-by-default breaks the suite, then perhaps an options Object as the second parameter (that handles the Array#map use-case) would be best.

@Sebmaster I have a feeling what we can make both, we just need a more sophisticated regexp. No facts, just an assumption :walking:

If I remember correctly the IETF suite explicitly tests to disallow the format we want to allow here, so I doubt it. Will look into it though.

Moved to options object and also added another test I found in the IETF tests which looked like a pretty interesting scenario to support (verified in browsers).

CLA is done too now.

Confirm CLA accepted! Welcome @Sebmaster!

@Sebmaster looks good to me. Ready to be merged?

Yep, should be good. :tada:


Refactor internal representations of certificates

I've closed #537 and instead refactored s2n_cert_chain_and_key, s2n_cert_chain, and s2n_cert_public_key. This is in preparation for some of the refactoring needed to add ECDSA support. This is also related to #538. I'm open to suggestions if people feel strongly about naming or how these types are represented.

can you rebase this as there are conflicts

I'm not super happy about having to add another parameter to verify_cert_trust_chain_fn to pass back the cert type. s2n_cert_type describes the type of cert, not just the public key, so I felt it better belonged in the new s2n_cert struct that is intentionally not exposed in the API. Part of the problem may be that we're trying to do too much in verify_cert_trust_chain_fn. We are both parsing and verifying. For now, it's not too problematic, but this function could bloat when we start adding new key types or allowing optional client auth. I'm interested in any thoughts on this.

LGTM. I think @alexw91 should put in a final review.

I'll give this a "Ship it", but this PR is making changes to API's that are removed in https://github.com/awslabs/s2n/pull/618


Performance drawback when using a common parent entity

Use of common base class/parent entity for all entities results in a single table (in SQLite) for all entities which is not good for performance. How are you overcoming this limitation (MMRecord as base entity) or is this not a limitation for the data model that you use this for?

mogenerator (https://github.com/rentzsch/mogenerator) can be used to specify explicit base class to be used instead of the default one (NSManagedObject) used by Xcode. This can be used to avoid all entities ending up in a single SQLite table when using a custom base class.


macOS MonteRey 12.1 brew installation error

Hi,
Not sure if is an issue with dive or with brew so feel free to close if it not relevant here. I am having error when running brew install dive trying to install from brew. Here the error:
IOS version: macOS MonteRey 12.1
Brew installation error:
==> Downloading https://ghcr.io/v2/homebrew/core/dive/manifests/0.10.0
Already downloaded: /Users/pablo/Library/Caches/Homebrew/downloads/96bf72db603204eabc97ae1bfcee2a72d33b878dd57caf38fbc33ae501a22595--dive-0.10.0.bottle_manifest.json
Error: dive: Failed to download resource "dive_bottle_manifest"
The downloaded GitHub Packages manifest was corrupted or modified (it is not valid JSON):
/Users/pablo/Library/Caches/Homebrew/downloads/96bf72db603204eabc97ae1bfcee2a72d33b878dd57caf38fbc33ae501a22595--dive-0.10.0.bottle_manifest.json

Thanks for the help.

Hi! Founded was an issue with brew cache. After removing Cache folder installation was fine.


[LuckPerms] Command execution [editor] has not completed

Description
LuckPerms is not opening the editor with Vault installed
It stopped working randomly, both plugins are up to date
Reproduction Steps
Install Vault and LuckPerms
Execute the command /lp editor
Expected Behaviour
The online editor should open
Server Details
Spigot 1.12.2
LuckPerms Version
5.4.67
Logs and Configs
https://gist.github.com/SoraGD/87f8fc8382499b608ffba43eb56e6760
Extra Details
No response

This does not seem to be an issue with LuckPerms, but with EssentialsX trying to retrieve the jail list.
Out of curiosity, do you use the jails feature in Essentials?

This does not seem to be an issue with LuckPerms, but with EssentialsX trying to retrieve the jail list. Out of curiosity, do you use the jails feature in Essentials?

I do not use the jails feature, and never used it, but I tried running the command and it apparently stopped working, not issuing any more commands after that one

Hey, you're running a very very old version of EssentialsX (around 2-3 years old). Could you try updating EssentialsX?

Hey, you're running a very very old version of EssentialsX (around 2-3 years old). Could you try updating EssentialsX?

Updating fixed it, thanks!


Support using a non-system version of python for markers, wheel tags, wheel building

Description
In rip a number of different operations require the system intepreter. E.g

Venv creation
Determining environment markers
Wheel tags
Wheel building (via venvs)

This has problems when not having a python installation on the PC.
In a lot of windows environments there is no global python installation.
Therefore all these operations fail
Solution
We should add the ability to use a custom python executable for all the above cases.
Some support is there but there are no tests yet.

Closed by #127


Merge pull request #1 from ffnord/master

update

The diff seems empty so there's no reason for a merge, is there?

sorry, verklickt :(


Added a Java book

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
Added a book named Java SE 8 Standard-Bibliothek
Why is this valuable (or not)?
A new resource not already listed
How do we know it's really free?
According to the publisher site, the book is free to read online and also free to print for private use.
For book lists, is it a book? For course lists, is it a course? etc.
It is a book
Checklist:

[X] Not a duplicate
[X] Included author(s) if appropriate
[X] Lists are in alphabetical order
[X] Needed indications added (PDF, access notes, under construction)

Thanks!


Rendering of colors introduces small artifact during rendering to the console

On Linux the color boxes shown below don't have the  artifact of the very thin black lines separating each color box from each other.
CMD.exe

compare to running the equivalent code in bash.

Both of those screenshots are of the console host window? Just the top one is CMD.exe and the bottom one is Bash via WSL to some distro? And they're both the same font?
If yes to all of the above, I am very, very curious. Can you help me understand how I can set this up locally to reproduce it? I'm not familiar with Julia. And is Crayons a default library of Julia? (i.e. if I go search for Julia and download it for Windows and run it, can I simply type what you did and reproduce it here? Same goes for if I install an ubuntu WSL and apt-get or otherwise install Julia?)

Sorry I should've provided a lot more clarification.
The top one uses my modified julia build to try and support VT Term sequences  (link to windows installer https://www.dropbox.com/s/w4zr2tkldz15f12/julia-a62b8ec9c6-win64.exe?dl=0)
after installing julia open it up in a cmd.exe window and run
julia --color=yes -E "using Pkg; Pkg.add(\"Crayons\"); using Crayons; Crayons.test_256_colors(false)"
In WSL you can just use  https://julialang-s3.julialang.org/bin/linux/x64/1.1/julia-1.1.0-linux-x86_64.tar.gz
and run the exact same command

Side by side comparison of other images where these artifacts are more obvious

Now I'm not sure if this is due to libuv doing some wonky thing or what not. In fact, this is the libuv patch incorporated https://github.com/JuliaLang/libuv/pull/51/files
and I modified julia as follows to use utf8 code page https://github.com/musm/julia/commit/db1c6a82233c6fef20d56d735ba832456244ddda
The libuv patch should allow vt sequences to pass through the julia console and allow them to be rendered properly.
(FWIW I'm trying to egg on libuv devs to try and use conpty....)
Now why exactly do I see those artifacts, that I'm not sure. It might be a bug related to conhost?

So it seems that this is an issue due to conhost, because  all the images I have shown above that render properly are from mintty

Interesting. Even though I'm using the same font in the comparisons. I  have noted that if I use Deja Vu Sans Mono the effects are lessened in conhost.

OK, less interesting then. It's probably just the way that conhost decides to render things puts gaps between the cells somehow.
I was very interested if two different clients both hosted in conhost appeared differently.
Any chance you can tee the output from the colors command to a file for me?

myfile.txt
I've attached a test file above, let me know if this is what you were looking for.
It prints the 24bit color block

That's good but I am specifically looking for which Unicode codepoint is being used to print the block character. It looks like you have those files printing the number of every color instead of the square block that your picture above uses.
Do you know specifically which codepoint that block is?

I think it's   ██

Ugh. U+2588 is an ambiguous width block per http://www.unicode.org/Public/UCD/latest/ucd/EastAsianWidth.txt which means it can vary per font.
Which font were you using and what size?

Ahh I see. I was using consolas font for both comparisons, which is a bit confusing then as to why they render differently.

Well, the console host window even with Consolas does some stuff to force characters into a certain cell grid. That might be getting in the way. I'm going to look into it.

That makes more sense then. Ok great, good luck.

Looks like this is fixed because I don't see it anymore !

Wow, great find! We missed closing this one when we did #5743

Thanks for following up


AttributeError: module 'typing' has no attribute '_ClassVar'

realtime-py==0.1.3
error "AttributeError: module 'typing' has no attribute '_ClassVar'"

And same problem here...

Just realised that I never came back on this - I actually have solved the problem by also adding the following:
RUN rm -rf /var/task/dataclasses*

At some point I am going to dive deeper into this and understand why RUN python3.9 -m pip uninstall -y dataclasses wasn't enough...

By looking at the current pyproject.toml I am actually not sure if this dependency is needed at all.
https://github.com/supabase-community/realtime-py/blob/4c808b000bfa3384678ad4aaa5e78f99d5ad89be/pyproject.toml#L8 says that the min python version is Python 3.7, and dataclasses is only really needed for 3.6. Should we just remove the dependency?
I have created https://github.com/supabase-community/realtime-py/pull/48 to address this.

Thanks.


[REQUEST] is it possible to create own skoda connect apps?

It it possible to create own apps nativ on mib2? Skoda connect has news, weather, Traffic... It it possible to create own apps like musik app, spotify api...?

Skoda or VW has not released an SDK. However, it should be possible to be able to make your own webservices that offer data to the unit. This would be something server-side, so no really mib2-toolbox related.


[BUG] load license error

Describe the bug
I recieve this message error "Flutter Error (Unable to load asset: google_fonts/OFL.txt)" everytime the project try to execute the load.
LicenseRegistry.addLicense(() async* {
final license = await rootBundle.loadString('google_fonts/OFL.txt');
yield LicenseEntryWithLineBreaks(['google_fonts'], license);
});
Is it need any other configuration?

Hi, that file needs to exist, and you should add it to your assets. Please re-open if it still doesn't work!


Kinesis Logger POC

TODO

Write a kinesis producer
Write a kinesis consumer
Deploy and test

References

Developing kinesis producer https://docs.aws.amazon.com/streams/latest/dev/building-producers.html

Notes
Writing to a kinesis steam can be done in multiple ways

Amazon Kinesis Data stream service API. https://docs.aws.amazon.com/kinesis/latest/APIReference/Welcome.html
Amazon Kinesis Producer library (KPL)

Basic Kinesis operations using aws cli
https://docs.aws.amazon.com/streams/latest/dev/fundamental-stream.html#put-record

Producer using AWS sdk
Sample code
https://github.com/awsdocs/aws-doc-sdk-examples/blob/main/javav2/example_code/kinesis/src/main/java/com/example/kinesis/StockTradesWriter.java


Uniform sampling without replacement until everything is sampled once

I would like to create a Table object where every unique trajectory is sampled exactly once, until everything is sampled once, then it should reset. I think one might be able to achieve something like that with priorities, i.e.
key| priority
001| 1.0
002| 1.0
...
999| 1.0

Draw with reverb.selectors.Prioritized sample with key=002
key| priority
001| 1.0
002| 0.0
...
999| 1.0

Repeat 998 times
key| priority
001| 0.0
002| 0.0
...
999| 0.0

Reset all priorities to 1.0
key| priority
001| 1.0
002| 1.0
...
999| 1.0

Is that possible?
Thank you :)

Your idea would work, but:

after each sampling you would have to update priority of sampled item(s).
for performance you might want to sample multiple elements at once and then within a single batch elements might be duplicated.

Another option would be to have 2 tables, both with max sample count per element == 1. One table would contain your data initially, the other would be empty. Then you sample from table 1 and insert sampled data to table 2. Once table 1 is empty, "swap" the tables. This way you can batch-sample many elements for performant execution.

Closing this issue to keep the backlog clean. Please reopen if you have follow-up questions.


[Question] if user accidently logs off and login again how can i show the conversation history to the user and how can i make bot start over from where user left last time ? Iam using C#.

This is not for asking questions or filing bugs
To get help with an issue with your bot

"How To" questions should be submitted on Stack Overflow where there is a robust community to help you

To file an issue against a component please go to the components repo

Create Azure Bot Framework Service or Channel issue
Create Bot Builder Tools issue
Create Bot Builder SDK V3 (.NET or Javascript) issue
Create Bot Builder SDK V4 .NET issue
Create Bot Builder SDK V4 Javascript issue
Create Bot Builder SDK V4 Java issue
Create Bot Builder SDK V4 Python issue

Hi @GaganDXC
Closing this issue because this repository is for DCRs only.

I assume you are asking about the WebChat control.  There is extensive discussion about restoring history on page re-load in that repository: https://github.com/Microsoft/BotFramework-WebChat/labels/ask%3Ahistory preservation

Also, here is an older c# example application that stores and loads chat history from sql server: https://github.com/JasonSowers/ChatHistoryBot-Public  (it has an old, custom and self hosted version of WebChat though https://github.com/JasonSowers/ChatHistoryBot-Public/blob/master/ChatHistoryBot/Areas/WebChat/botchat.js )


Turn debug on, telepresence.io docker tutorial requires hot code reloading

Assuming this repository is in support of https://www.telepresence.io/tutorials/docker
The tutorial instructs the user to mount the local repository into the container and then to modify the version number in qotm.py. Once done the user should see an immediate change on their next call. Unfortunately this does not happen because Flask is run with debug=False.
https://github.com/datawire/qotm/blob/9f619b4124197aafea6e77f876c93205f9328e26/qotm/qotm.py#L241
In order to support the telepresence.io tutorial I suggest setting debug=True.

Thanks for the issue. We've switched the tutorial to use a different (and much simpler) service as QotM has other important responsibilities.


add cli command for manually approving a piece of freight for a given stage

Follow up to #1073

#1162 closed this in error. Re-opening.

This really depends on #1222 to function correctly. #1222 has been deferred to v0.4.0, so this must be also.


Alias feature

Context
This PR contains the code base for the alias feature.
Acceptance
It's recommended that you test:

[ ] Add table alias
[ ] Remove table alias
[ ] Add column alias
[ ] Remove table alias
[ ] Other normal column operations
[ ] Import an non-aliased dataset from Data Library
[ ] Import an aliased dataset from Data Library

Ready for you to accept and merge, @mbektas

I removed the unrelated code, sorry about that. Please continue!

ok, thanks


Disable the unaligned feature of the object crate

We mmap the files so they should be reasonably aligned.
Let's see what https://github.com/rust-analyzer/rust-analyzer/pull/6817#issuecomment-744866239 is about.

Weird, it worked this time.
bors r+


Operator Life Cycle Manager: Prometheus Operator Install Fails: file monitoring.coreos.com_prometheusagents.yaml bigger than total allowed limit

Expected behavior
The operator should have installed.
Actual behavior
When using Operator Lifecycle Manager to install the operator from operatorhub.io https://operatorhub.io/operator/prometheus
I encountered the error:
time="2023-09-15T03:10:56Z" level=info msg="Using in-cluster kube client config"
time="2023-09-15T03:10:56Z" level=info msg="Reading file" file=/bundle/manifests/monitoring.coreos.com_alertmanagerconfigs.yaml
time="2023-09-15T03:10:56Z" level=info msg="Reading file" file=/bundle/manifests/monitoring.coreos.com_alertmanagers.yaml
time="2023-09-15T03:10:56Z" level=info msg="Reading file" file=/bundle/manifests/monitoring.coreos.com_podmonitors.yaml
time="2023-09-15T03:10:56Z" level=info msg="Reading file" file=/bundle/manifests/monitoring.coreos.com_probes.yaml
time="2023-09-15T03:10:56Z" level=info msg="Reading file" file=/bundle/manifests/monitoring.coreos.com_prometheusagents.yaml
time="2023-09-15T03:10:56Z" level=error msg="File with size 490794 exceeded 1048576 limit, aboring" file=/bundle/manifests/monitoring.coreos.com_prometheusagents.yaml
Error: error loading manifests from directory: file monitoring.coreos.com_prometheusagents.yaml bigger than total allowed limit

This indicates that the monitoring.coreos.com_prometheusagents.yaml  file was 490794 and exceeded the 1048576 limit. I'm assuming this might be referring to a characters?
Steps:
Follow install instructions on https://operatorhub.io/operator/prometheus
Environment
DigitalOcean Kubernetes using Operator Lifecycle Manager

Prometheus Operator version:
v0.65.1

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4+k3s-", GitCommit:"", GitTreeState:"clean", BuildDate:"2023-05-13T14:15:17Z", GoVersion:"go1.20.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.4", GitCommit:"fa3d7990104d7c1f16943a67f11b154b71f6a132", GitTreeState:"clean", BuildDate:"2023-07-19T12:14:49Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
DigitalOcean

This issue was closed because it has been inactive for 30 days since being marked as stale.

Only inactive due to not receiving any response.


Added Nova 4 support

Fixes #6. Added support for Nova version 4.x as per the official Nova upgrade guide here https://nova.laravel.com/docs/4.0/upgrade.html

Hey, thanks for opening the pull request.
These changes alone wont be enough to make the package compatible with nova 4.
Here is one of our other package, that was made nova v4 compatible, where you can pick some of the things that are needed to make this package compatible with nova v4.
https://github.com/outl1ne/nova-sortable/pull/117


Protecting environment using group name returns error

Describe the bug
When trying to protect an environment using group with group name (https://gitlabform.github.io/gitlabform/reference/protected_environments/), the GitLab API returns the error Deploy access levels is too short (minimum is 1 character). Seems like the API does not support group(https://docs.gitlab.com/ee/api/protected_environments.html#protect-a-single-environment), switching to group_id worked.
GitLabForm version
3.4.1
GitLab version
15.7.7-ee

Thanks for reporting this @long-wan-ep! It's true, we missed adding the support for group names when we implemented this feature and we didn't notice because we didn't have a test for that.
Both of these should be fixed in the linked PR.

Released in v3.4.3.

Thanks for the quick fix @gdubicki. We'll try it out soon.


Twitter accounts not ripping completely

For example: https://twitter.com/littlesexbuddha/ (NSFW)
Scrolling through the media history reveals that it's missing a lot.
When I rip other larger accounts, the number of files it rips are roughly the same, so I'm guessing it stops ripping earlier than it should.
I am using v1.4.14

yep same here, even with accounts with around 100 pics

Could you provide non-NSFW example?

Can confirm

Could somebody post non-NSFW example?

non-NSFW

= SFW

This is because of restriction on Max requests which is at 10. We need to reset this or provide a user friendly input in form of query parameter or path parameter. For now, we can increase the value directly

This is still bugged. Is anyone working on it? Ripme is the only downloader that can download Twitter images and keep the order. Please update...
Thank you.

^ Not quite, https://github.com/mikf/gallery-dl is supposed to support Twitter (besides DA which I've been using it on), but I haven't tested it.
The software's a rather tedious thing to conf, but it's well worth it.

^ Not quite, https://github.com/mikf/gallery-dl is supposed to support Twitter (besides DA which I've been using it on), but I haven't tested it.
The software's a rather tedious thing to conf, but it's well worth it.


Make ELB not required

Set "loadbalancer": "false" to skip creating a loadbalancer
Set "availability": "public" to create instances in a public subnet, and to give them a public IP address (prelude to #45, #50 comes to mind)

tested on develop ✅
Fixes #47

Double checked by deploying with and without ELB, looks good!


[Sql Server] Add support for different integer sizes

Codecov Report

Merging #1250 into master will increase coverage by 2.07%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1250      +/-   ##
=========================================
+ Coverage   72.32%   74.4%   +2.07%
=========================================
  Files          35      35
  Lines        5551    4743     -808
=========================================
- Hits         4015    3529     -486
+ Misses       1536    1214     -322

Impacted Files
Coverage Δ

src/Phinx/Db/Adapter/SqlServerAdapter.php
0% <0%> (ø)
:arrow_up:

src/Phinx/Migration/AbstractTemplateCreation.php
73.33% <0%> (-4.45%)
:arrow_down:

src/Phinx/Console/Command/Breakpoint.php
36% <0%> (-3.29%)
:arrow_down:

src/Phinx/Seed/AbstractSeed.php
46.34% <0%> (-1.58%)
:arrow_down:

src/Phinx/Console/Command/AbstractCommand.php
50.89% <0%> (-1.49%)
:arrow_down:

src/Phinx/Console/Command/Test.php
24.13% <0%> (-0.87%)
:arrow_down:

src/Phinx/Db/Table.php
95.87% <0%> (-0.37%)
:arrow_down:

src/Phinx/Db/Adapter/AbstractAdapter.php
80.32% <0%> (-0.27%)
:arrow_down:

src/Phinx/Db/Adapter/TablePrefixAdapter.php
79.54% <0%> (-0.07%)
:arrow_down:

src/Phinx/Db/Table/ForeignKey.php
97.91% <0%> (-0.05%)
:arrow_down:

... and 25 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 454238f...1668ce1. Read the comment docs.

Why does this happen? Is the SqlServerAdapter not tested in Travis?

Thank you for your contribution. SqlServerAdapter seems to be not tested on Travis. And Appveyor seems to be not triggered.
That aside, I tested your patch on my local computer with sqllocaldb, but it didn't pass. Would it pass on your environment?
C:\var\contributing\phinx>vendor\bin\phpunit tests\Phinx\Db\Adapter\SqlServerAdapterTest.php
PHPUnit 5.7.25 by Sebastian Bergmann and contributors.

............................................EEEEE                                                                                49 / 49 (100%)

Time: 47.38 seconds, Memory: 10.50MB

There were 5 errors:

1) Test\Phinx\Db\Adapter\SqlServerAdapterTest::testBigIntegerColumn
Undefined offset: 1

C:\var\contributing\phinx\tests\Phinx\Db\Adapter\SqlServerAdapterTest.php:771

2) Test\Phinx\Db\Adapter\SqlServerAdapterTest::testMediumIntegerColumn
PDOException: SQLSTATE[42000]: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]The size (16777215) given to the column 'column1' exceeds the maximum allowed for any data type (8000).

C:\var\contributing\phinx\src\Phinx\Db\Adapter\PdoAdapter.php:134
C:\var\contributing\phinx\src\Phinx\Db\Adapter\SqlServerAdapter.php:283
C:\var\contributing\phinx\src\Phinx\Db\Table.php:628
C:\var\contributing\phinx\src\Phinx\Db\Table.php:716
C:\var\contributing\phinx\tests\Phinx\Db\Adapter\SqlServerAdapterTest.php:779

3) Test\Phinx\Db\Adapter\SqlServerAdapterTest::testSmallIntegerColumn
RuntimeException: The SqlServer type: "smallint" is not supported

C:\var\contributing\phinx\src\Phinx\Db\Adapter\SqlServerAdapter.php:967
C:\var\contributing\phinx\src\Phinx\Db\Adapter\SqlServerAdapter.php:385
C:\var\contributing\phinx\src\Phinx\Db\Table.php:219
C:\var\contributing\phinx\tests\Phinx\Db\Adapter\SqlServerAdapterTest.php:790

4) Test\Phinx\Db\Adapter\SqlServerAdapterTest::testTinyIntegerColumn
RuntimeException: The SqlServer type: "tinyint" is not supported

C:\var\contributing\phinx\src\Phinx\Db\Adapter\SqlServerAdapter.php:967
C:\var\contributing\phinx\src\Phinx\Db\Adapter\SqlServerAdapter.php:385
C:\var\contributing\phinx\src\Phinx\Db\Table.php:219
C:\var\contributing\phinx\tests\Phinx\Db\Adapter\SqlServerAdapterTest.php:800

5) Test\Phinx\Db\Adapter\SqlServerAdapterTest::testIntegerColumnLimit
Undefined offset: 1

@chinpei215 Thank you for testing! Yeah I was hoping that I could use the CI process and wouldn't have to set it up myself locally. I'll look at the issues and report back.

@chinpei215 I took this from the MysqlAdapter which does it in the same way.

Oh I didn't know that. Sorry. Then I don't request changes in this PR.

@chinpei215 Oh that's fine 😄 We had several other issues and decided to write native queries in the migrations which is suboptimal but easier in our situation. Thus I'll have to fix these issues in my free time. I'll look at them as soon as possible.

Thanks.

@iluuu1994 Do you still want to add those?
Please resolve conflicts.

Nop, I'm not using this library anymore. You're free to take over.


expose more config options for azure.

What this PR does / why we need it:
This PR expose more cloud provider config for the Azure.
How can this PR be verified?
Is there any change in kubo-deployment?
no, all the fields are optional fields. customer can choose to specifiy it in the manifest by themselves.
Is there any change in kubo-ci?
Does this affect upgrade, or is there any migration required?
Which issue(s) this PR fixes:
Release note:

Hi @andyliuliming does this issue #262 request further properties to be added on top of the ones you have included here, or are they represented within this PR with different names?

Hi @andyliuliming
Could you please remove default values from added properties, so if someone changes defaults in Kubernetes, we will automatically use new defaults

@alex-slynko done. thanks  : )


[TESTING] 4x faster polygon decoding

This speeds up polygon decoding + clipping + encoding by 4x. Polygons are going to be the slowest to overzoom, so this is significant.
The speed boost comes from avoiding the allocation of intermediate vectors to store rings. Instead we collect bbox's while we decode, only clip geometries that are not fully within the target tile, and when we have results we encode them directly to the new feature.
Current master, for test 11 gives:
node bench/bench.js --iterations 500 --concurrency 1 --package vtcomposite
11: tiles completely made of polygons, overzooming and lots of properties ... 166 runs/s (3015ms)

This PR gives, for test 11, gives:
node bench/bench.js --iterations 500 --concurrency 1 --package vtcomposite
11: tiles completely made of polygons, overzooming and lots of properties ... 728 runs/s (687ms)

Next steps:

[ ] Review from @ericfischer
[ ] Review from @flippmoke
[ ] Dev package + test in staging
[ ] determine it is ready to merge + officially release

/cc @mapbox/maps-api @artemp @flippmoke @ericfischer @millzpaugh

The bench results here are bogus and 4x speed-ups are due to the bug https://github.com/mapbox/vtcomposite/issues/95.
With https://github.com/mapbox/vtcomposite/issues/95 fixed I'm getting roughly equivalent results:
Current master
11: tiles completely made of polygons, overzooming and lots of properties ... 252 runs/s (1984ms)

This PR
11: tiles completely made of polygons, overzooming and lots of properties ... 251 runs/s (1992ms)

/cc @mapsam @flippmoke @ian29


g3keymess: add worker support

Codecov Report
Attention: Patch coverage is 30.76923% with 9 lines in your changes missing coverage. Please review.

Project coverage is 31.32%. Comparing base (ad507d1) to head (07931af).
Report is 1 commits behind head on master.

Files with missing lines
Patch %
Lines

lib/g3-types/src/sync/mod.rs
0.00%
6 Missing :warning:

lib/g3-runtime/src/blended.rs
57.14%
3 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (ad507d1) and HEAD (07931af). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (ad507d1)
HEAD (07931af)

lib
1
0

g3proxy
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #470       +/-   ##
===========================================
- Coverage   54.25%   31.32%   -22.94%
===========================================
  Files        1173      714      -459
  Lines      108374    55879    -52495
===========================================
- Hits        58802    17505    -41297
+ Misses      49572    38374    -11198

Flag
Coverage Δ

g3bench
31.32% <30.76%> (-0.01%)
:arrow_down:

g3proxy
?

lib
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


npm warnings: source-map-resolve

Environment
Knex version: 0.21.2
Database + version: MySQL
OS: Ubuntu 18.04
Bug

Explain what kind of behaviour you are getting and how you think it should do

When installing knex through npm, I get the following warnings:
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated

Following the given links, I see that knex needs to use a newer version of source-map-resolve package to avoid these warnings.
This is obviously not very important, but it would be nice not to get those warnings.

Will be fixed when deps are updated every now and then. Closing to prevent dangling open issues and since this is so minor issue. Please leave comment here, if after 6 months those warnings still exists and I will reopen this.


Migrate to ESLint

since TSLint is deprecated it's necessary to use ESLint
https://code.visualstudio.com/api/advanced-topics/tslint-eslint-migration

Is this issue solved or we still discussing this?


Port 5000 is already used on Mac by default

Mac ControlCenter is using port 5000 and 7000
https://developer.apple.com/forums/thread/682332

Hi @remorses. Thanks for pointing this out. This is the first I'd heard of Apple using those port numbers for system services.
For context, the AirPlay Receiver feature in macOS Monterey uses ports 5000 and 7000 when enabled. To disable this feature, you can open System Preferences, go to "Sharing", and uncheck "AirPlay Receiver".
I don't like the precedent of accommodating questionable design choices by Apple, but I think it's worth considering Cog using a different port by default. In my heart, I associate 5000 with Foreman, so I'm all for having Cog carve out its own reservation.

Currently there is no logs if the port is already used, printing a message like port 5000 already in use would already be a great improvement

uvicorn did not throw any error but you are right that if you use Docker it will probably be Docker to throw this error

@remorses Thanks for confirming that. I just opened https://github.com/replicate/cog/pull/1103 which makes this change.


added Example config for NSS on root-server

@Vinnl @jaxoncreed @Mitzi-Laszlo
added extensive documentation, capitalization...

@NSeydoux
thanx for your feedback. will check an alternative node howto.
I' m not yet familiar with jekyll. perhaps lets make two new pages for apache/nginx setup.
for the nginx setup we could ask @etcware
and let' s stay closely synced with @Vinnl @jaxoncreed and @Mitzi-Laszlo

If you are okay with this suggestion, I can merge your changes in as soon as you updated the node howto, and i can take care of moving the Apache setup in a different page if you're not comfortable with Jekyll. This way, it will create a precedent showing how to do it for future contributions, for instance regarding nginx.

okay, very cool. I' ll change the node link when I' m home in a few hours. furthermore I' ll look out for @etcware in the gitter channel and appreciate your help. experiments with jekyll are To-Do for me.
will let you know here in the comments as soon as I' m ready to merge. ;-)

@NSeydoux are you okay with the changes ?
have used an eglish version now...

Great, thanks again. I'll merge this in, and update the content to make the apache conf a separate page.

the node link would need to be formatted as a href with jekyll syntax.....


Bump operator newest v2.3.0-24.2.10 version

I think we're waiting on https://github.com/redpanda-data/helm-charts/pull/1595 to bump the operator release?

Oh and we need to wait for the docker tag to get fixed as well, right?


Cherry picking bug fixes from master into release-1.0

SNI routing
Costin's fixes for global mesh config
Greg Hanson's fixes for Consul/Eureka templates
some mixer bug fixes.
Please wait until all tests pass.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [rshriram]
mixer/OWNERS [rshriram]
pilot/OWNERS [rshriram]
tests/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [costinm,rshriram]
mixer/OWNERS [costinm,rshriram]
pilot/OWNERS [costinm,rshriram]
tests/OWNERS [costinm,rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rshriram from what I can tell, the following PRs/commits from master are included in this:
#6402 (560c9f991fbdfa325fe81a5a180794ecfcb5285b)
#6797 (65a76fba40f5717fbd11bf210c7a2d8cea353a18)
#6800 (62d0e3029b5992857783d61fc1080d70c4c5f0d7)
#6790 (a82c55a9771698d13d54115714cc57caf90d62f7)
#6785 (dc5264ba405dcd3dd0f52d94f6af2945cca11143)
Am I missing anything?


cmd/go: go get -u=patch with argument bumps minor version

What version of Go are you using (go version)?
go version devel +5a720d229d Sat Aug 4 16:37:47 2018 +0000 darwin/amd64
Does this issue reproduce with the latest release?
N/A, building from source
What did you do?
Repro provided.
$ git clone git@github.com:mfridman/srfax.git
$ cd srfax

$ cat go.mod
module github.com/mfridman/srfax

require (
	github.com/mitchellh/mapstructure v0.0.0-20180715050151-f15292f7a699
	github.com/pkg/errors v0.6.0
)

$ go get -u=patch
$ git diff
# no changes

$ go get -u=patch github.com/pkg/errors
$ git diff
-       github.com/pkg/errors v0.6.0
+       github.com/pkg/errors v0.8.0

Based on the docs, I was expecting pkg/errors to remain on v0.6.0, but instead it got bumped to v0.8.0. Running go get -u=patch (without arg) did not update the patch version.

The -u=patch flag (not -u patch) instructs get to update dependencies to use newer patch releases when available

I would only ever expect the minor version to be bumped when running go get -u or go get -u github.com/pkg/errors.
Likewise I would expect -u=patch with or without an arg to operate in the same way.
@gopherbot, please add label modules

The documentation explains this:
The first step is to resolve which dependencies to add.

For each named package or package pattern, get must decide which version of
the corresponding module to use. By default, get chooses the latest tagged
release version, such as v0.4.5 or v1.2.3. If there are no tagged release
versions, get chooses the latest tagged prerelease version, such as
v0.0.1-pre1. If there are no tagged versions at all, get chooses the latest
known commit.

This default version selection can be overridden by adding an @version
suffix to the package argument, as in 'go get<EMAIL_ADDRESS>For modules stored in source control repositories, the version suffix can
also be a commit hash, branch identifier, or other syntax known to the
source control system, as in 'go get golang.org/x/text@master'.
The version suffix @latest explicitly requests the default behavior
described above.

If a module under consideration is already a dependency of the current
development module, then get will update the required version.
Specifying a version earlier than the current required version is valid and
downgrades the dependency. The version suffix @none indicates that the
dependency should be removed entirely.

Although get defaults to using the latest version of the module containing
a named package, it does not use the latest version of that module's
dependencies. Instead it prefers to use the specific dependency versions
requested by that module. For example, if the latest A requires module
B v1.2.3, while B v1.2.4 and v1.3.1 are also available, then 'go get A'
will use the latest A but then use B v1.2.3, as requested by A. (If there
are competing requirements for a particular module, then 'go get' resolves
those requirements by taking the maximum requested version.)

The -u flag instructs get to update dependencies to use newer minor or
patch releases when available. Continuing the previous example,
'go get -u A' will use the latest A with B v1.3.1 (not B v1.2.3).

The -u=patch flag (not -u patch) instructs get to update dependencies
to use newer patch releases when available. Continuing the previous example,
'go get -u=patch A' will use the latest A with B v1.2.4 (not B v1.2.3).

By saying github.com/pkg/errors on the command line you are implicitly saying github.com/pkg/errors@latest. The -u=patch applies to dependencies of the listed packages/modules, not to those packages/modules themselves.
Maybe we can revisit semantics for Go 1.12 but these are the Go 1.11 semantics.

I would agree with the original poster, that this behaviour is very confusing, even reading the docs several times its wasn't clear and caused much hear pulling and time wasted.
I believe the reason for this is that it states dependencies and if you running go -u get <package> in your repo  is a dependency.
The use case IMO for running go get -u=patch <package> is to update just <package> and its dependencies using the patch strategy.
With the current design there is no easy way to update a specific package and its dependencies using the patch strategy. The only option is to manually visit to the repo site look for the version and issue the manual go get -u=patch<EMAIL_ADDRESS>which is a royal PITA.

go get -u=patch some/binary@latest has a pretty clear use-case: you want to build and install the latest version of some/binary@latest, using the patch releases of its dependencies. After #24250 is addressed, that may well be the best default for installing tools from outside of a module. On the other hand, outside of a module, some/binary and some/binary@latest resolve to the same version anyway: perhaps we should only implicitly add @latest to new dependencies rather than existing ones, uniformly.
There is also a bit of a skew between the old and new go get behaviors without -u: in GOPATH mode, go get foo for some package foo already in GOPATH/src does not upgrade the version, but in module mode it implicitly upgrades to @latest.
That provides an opportunity for a nice symmetry: if the @latest version is necessary to upgrade the named package to the latest version, then we could add a similar version @patch, with the meaning “the latest patch release of the minor version already in the module graph”.
I don't think we'll get to this for 1.12, but I'd like to at least make a decision on it early in 1.13

[@patch] can mean "the latest patch version of a module x already in use" (an error if x is not already a depended-upon module). Then we can define that -u=patch changes the default version suffix from @latest to @patch.

If @patch is an error if the module is not already in use, then go get -m -u=patch some/new/module would be an error. I would argue that the user's clear intent in that case is to “install some/new/module and patch all of its dependencies”.
That suggests that @patch should decay to @latest if an explicitly-requested module is not already present in the build graph.


Upsert failing due to PATCH not being an acceptable method

I'm calling upsert on a custom object, where I'm updating based on Id. In the case in question, upsert should perform an insertion since Id is nil. That is the behavior I'm expecting. The SFDC error message reads: METHOD_NOT_ALLOWED: HTTP Method 'PATCH' not allowed. Allowed are GET,HEAD,POST

@cworsley4 Can you give an example of your code? I'm wondering if it might be an example of "Inserting New Records Using Id as the External ID" at https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_upsert.htm, which seems to use POST.


Fix sample README links

Fixes #12

[X] Tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

Codecov Report

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

@@           Coverage Diff           @@
##             master    #13   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?      4
  Branches          ?      0
=======================================
  Hits              ?      4
  Misses            ?      0
  Partials          ?      0

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 c3b0497...95caa4e. Read the comment docs.


Barebones project, breaks when exported to iOS

So I ran into this issue, earlier when testing on latest Unity and exporting as iOS/xcode project.
Anyone has quick thoughts on how to fix it? It seems to have todo with Metal Framework, maybe related to new Unity IDE version...

@alexisoyama was this the similar issue you were getting?

One of the way to get away from this issue is by using XCode 8. Haven't found out a solution yet. It's likely a Unity bug.

Closing this since this is more of Unity's issue. Re-open if there is something we can do from our end.


CasperPad Marketplace

Project name
Kunft Marketplace
URL to be whitelisted
.Kunftmarketplace.io/
Code audit/review URL if available
No response
Project description
Nft Marketplace on Casper network
Project's phase
Testing
Who is the project owner?
Company
Project owner's name
CasperPad
What kind of Web3 functionality will you be offering in your product?

wallet
transfers
contract calls
document signature

Contact details
Abdallah, CEO<EMAIL_ADDRESS>Link to the code
Smart Contract: https://github.com/casperpad/kunft-marketplace-contract Back End: https://github.com/casperpad/kunft-marketplace-backend Front End: https://github.com/casperpad/kunft-marketplace-frontend
Is this a project by an enterprise partner of Casper Association or CasperLabs?
No
Grant/proposal number if this is a project funded by the DEVxDAO
No response

Sorry, just confused.
Opened a wrong issue, closing.


Problem with dead symlinks

I was browsing my home assistant error logs and I found this:
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/watchman/utils.py:255
Integration: Watchman (documentation, issues)
First occurred: 20:35:04 (1 occurrences)
Last logged: 20:35:04

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/watchman/__init__.py", line 257, in async_on_home_assistant_started
    parse_config(hass, reason="HA restart")
  File "/config/custom_components/watchman/__init__.py", line 330, in parse_config
    entity_list, service_list, files_parsed, files_ignored = parse(
  File "/config/custom_components/watchman/utils.py", line 255, in parse
    for i, line in enumerate(open(yaml_file, encoding="utf-8")):
FileNotFoundError: [Errno 2] No such file or directory: '/config/ext/crowdsec/parsers/http-logs.yaml'

I'm mounting some shared volumes into home assistant so I can modify their configurations within automations, one of which belongs to CrowdSec. Sadly this places a bunch of symlinks into that directory which, when not inside the CrowdSec image, result into inaccesible symlinks.
For my config I'll just add anything external to the ignore list, but properly handling this exception would improve this plugin.
By the way; Love the insight this gives me! Takes a lot of the gueswork out of cleaning up old deprecated stuff from my configuration.

Fixed in v0.5.3.


Implement minimum and maximum timespans to protect against DoS

Observed behaviour
With the current implementation, the bot can be DoSed by setting up a recurring reminder as follows:
!remindroom every 1 second; now; spam
Proposed fix
Implement config variables for minimum and maximum timespans, e.g.
reminders:
    timespan_min: "1 minute"
    timespan_max: "1 year"

For reminders above and below the timespan limit, the bot should respond with an error.

There are also already rate limits for the different endpoints in the Client-Server API to prevent similar spam. I think it's good to act like a "good citizen" trying to prevent "spam" at the source.
I wonder if something in nio already takes care of rate limits blocking messages from being sent and retrying. There might not.
I'm assuming these are supposed to apply to the intervals of repeating reminders. What would be the purpose of the upper limit?
Note to potential implementers: remember cronjobs as well.

The upper limit will prevent, for example, reminders that are created just for fun, reminding you of the new century 2100 or something.


documentElement.clientHeight when position is fixed

Hello,
First, thanks a lot for putting this page together; it's a great resource.
Second, I find that if I have html { position:fixed } and the URL bar is collapsed, then percentage heights adjust to the larger size and  document.documentElement.offsetHeight reflects the larger size, but document.documentElement.clientHeight is still the smaller size. To my understanding, it would make more sense for clientHeight to also contain the larger size.
(How can you get the URL bar to hide with html { position:fixed }, you might ask? It seems that returning from a fullscreened video always gets rid of the URL bar.)
Thanks!

Hey @sethbrenith! Apologies for the long delay - this slipped off my radar.
Whoa, that's definitely unintentional. I would expect documentElement.clientHeight to adjust to the larger size as well. It seems that this is specific to the documentElement, making body or any other element fixed does not show the same issue. I suspect there's a special case for documentElement due to it being so quirky (as you can see from its implementation )
I've filed issue 726322 in the Chromium bug tracker to fix this. Thanks for bringing it up!


Building unconditionally with -D_FORTIFY_SOURCE=0 is undesirable

Some build configuration fail with "_FORTIFY_SOURCE being multiply-defined". In any case, the user should be allowed to specify the _FORTIFY_SOURCE level themselves, rather than having it preset in the build system.

Resolved in https://github.com/bloomberg/ntf-core/pull/11


Fix errors and warnings building swift/Sema on Windows using MSVC

Unused variables
Fix a really hard-to-fix assertion that was horrible to find and fix :))
other misc changes

@hughbe My personal preference would be to squash the two later commits into the first since they are just small tweaks addressing review feedback with the original commit.

@rudkx thanks for taking a look. I've removed all ifdefs for pragma mark, and squashed the commits as you asked. I can't trigger tests yet, so could you if we've got to that point?

@swift-ci Please smoke test and merge

Strange... tests have passed but this wasn't automerged


Updated to use navigator.mediaDevices.getUserMedia and srcObject.

Updated to avoid outdated patterns we're trying to deprecate.

@a2sheppy PTAL.

At this point, I'm kind of inclined to just change the code to assume that WebRTC is not prefixed and is more or less up-to-date, which our other samples generally do now, instead of having all the code to work around the variations. Opinions?


Null-safety

Will this library be upgraded to null-safety?

I've made a PR (#5) for null-safety, it has some issues though.

There are no plans to use the null safety features at the moment. I'll tell you right now, you won't run into any null pointer errors in the code. Critical fields are either marked as required or given defaults and nullable fields are checked before they're used. It's not broken, so there's nothing to fix. I'm focused on adding new providers to the library. Cosmetic changes can come later and an upgrade to use Dart's null safety features must be done very carefully.

I am having issues with this package though since it depends on non null-safety versions of other packages such as http.
Because no versions of google_fonts match >2.0.0 <3.0.0 and google_fonts 2.0.0 depends on http ^0.13.0, google_fonts ^2.0.0 requires http ^0.13.0.

And because every version of visa depends on http ^0.12.2, google_fonts ^2.0.0 is incompatible with visa.

So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.
pub get failed (1; So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.)
exit code 1

I won't be accepting your PR right now but I appreciate the effort so I'll show you why you're getting the error. Basically, getAuthData is written to accept a Map<String, String>. When it's called, in SimpleAuth, we pass it the result of _getQueryParams from the OAuth class which you changed to be a Map<String, String?>. I've added both functions here (from your pr) so you'll see what I mean.
getAuthData: (Map<String, String> oauthData) async {
    if (debugMode) debug('In FacebookAuth -> OAuth Data: $oauthData');

    final String token = oauthData[OAuth.TOKEN_KEY];
    final String? token = oauthData[OAuth.TOKEN_KEY];
    if (debugMode) debug('In FacebookAuth -> OAuth token: $token');

    // User profile API endpoint.
    var baseProfileUrl = 'https://graph.facebook.com/me';
    final String profileUrl = '$baseProfileUrl'
        '?access_token=$token'
        '&fields=first_name,last_name,email';
    var profileResponse = await http.get(Uri.parse(profileUrl));
    var profileJson = json.decode(profileResponse.body);
    if (debugMode)
      debug('In FacebookAuth -> Returned Profile Json: $profileJson');
    return authData(profileJson, oauthData);
  });

Map<String, String?> _getQueryParams(String url) {
  if (debugMode) debug('In OAuth -> Getting Query Params From Url: $url');

  final List<String> urlParams = url.split(RegExp('[?&# ]'));
  final Map<String, String> queryParams = HashMap();
  final Map<String, String?> queryParams = HashMap();
  List<String> parts;

  for (String param in urlParams) {
    if (!param.contains('=')) continue;
    parts = param.split('=');
    queryParams[parts[0]] = Uri.decodeFull(parts[1]);
  }
  if (debugMode) debug('In OAuth -> Extracted Query Params: $queryParams');
  return queryParams;
}

I am having issues with this package though since it depends on non null-safety versions of other packages such as http.
Because no versions of google_fonts match >2.0.0 <3.0.0 and google_fonts 2.0.0 depends on http ^0.13.0, google_fonts ^2.0.0 requires http ^0.13.0.

And because every version of visa depends on http ^0.12.2, google_fonts ^2.0.0 is incompatible with visa.

So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.
pub get failed (1; So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.)
exit code 1

Seems like I simply need to upgrade the version of http being used .

I'll look into this

I am having issues with this package though since it depends on non null-safety versions of other packages such as http.
Because no versions of google_fonts match >2.0.0 <3.0.0 and google_fonts 2.0.0 depends on http ^0.13.0, google_fonts ^2.0.0 requires http ^0.13.0.

And because every version of visa depends on http ^0.12.2, google_fonts ^2.0.0 is incompatible with visa.

So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.
pub get failed (1; So, because my_app depends on both visa ^1.0.4 and google_fonts ^2.0.0, version solving failed.)
exit code 1

Seems like I simply need to upgrade the version of http being used .

I don't think that's possible though because the latest version of http is using null-safety.

Ok Th

I won't be accepting your PR right now but I appreciate the effort so I'll show you why you're getting the error. Basically, getAuthData is written to accept a Map<String, String>. When it's called in SimpleAuth, we pass it the result of _getQueryParams from the OAuth class which you changed to be a Map<String, String?>. I've added both functions here (from your pr) so you'll see what I mean.
getAuthData: (Map<String, String> oauthData) async {
    if (debugMode) debug('In FacebookAuth -> OAuth Data: $oauthData');

    final String token = oauthData[OAuth.TOKEN_KEY];
    final String? token = oauthData[OAuth.TOKEN_KEY];
    if (debugMode) debug('In FacebookAuth -> OAuth token: $token');

    // User profile API endpoint.
    var baseProfileUrl = 'https://graph.facebook.com/me';
    final String profileUrl = '$baseProfileUrl'
        '?access_token=$token'
        '&fields=first_name,last_name,email';
    var profileResponse = await http.get(Uri.parse(profileUrl));
    var profileJson = json.decode(profileResponse.body);
    if (debugMode)
      debug('In FacebookAuth -> Returned Profile Json: $profileJson');
    return authData(profileJson, oauthData);
  });

Map<String, String?> _getQueryParams(String url) {
  if (debugMode) debug('In OAuth -> Getting Query Params From Url: $url');

  final List<String> urlParams = url.split(RegExp('[?&# ]'));
  final Map<String, String> queryParams = HashMap();
  final Map<String, String?> queryParams = HashMap();
  List<String> parts;

  for (String param in urlParams) {
    if (!param.contains('=')) continue;
    parts = param.split('=');
    queryParams[parts[0]] = Uri.decodeFull(parts[1]);
  }
  if (debugMode) debug('In OAuth -> Extracted Query Params: $queryParams');
  return queryParams;
}

Thanks, I managed to fix the error!

Updating the dependencies fixed this. Thanks for pointing it out!

All dependencies have been updated in the v2.0.0 release


Choose method using variable

Hi,
More idea than issue:
It would be very useful to be able to choose the methods using a variable. Users could be able to switch methods more easily:
import textdistance
string1="test"
string2="text"
method="hamming.similarity"
textdistance.distance(string1, string2, method)

Python can apply getattr to modules:
getattr(textdistance, 'hamming', 'similarity')('test', 'text')

Ho thanks. Indeed, doing exactly the job.


feat(STONEINTG-398): this is a follow-up enhancement PR

Description
This is an enhancement PR for the previously merged PR, because https://github.com/redhat-appstudio/e2e-tests/pull/496 got merged too soon before I could address the non-blocking review comments.
The test suite still works fine without this PR but this is just an attempt to make this test suite even more readable, concise, and resilient. This PR:

Removes the top-level Describe block from both the files
Moves 3 functions out of the Describe blocks to reduce code duplication
Adds a util function to wait for PLR to get started to make test suites slimmer
Adds a retry logic within the test suite where the GetEphemeralEnvironment function gets called
Ensures each test uses a unique test namespace
Improves the Eventually blocks to return an error instead of a bool

Issue ticket number and link
STONEINTG-398
Type of change

[x] Test

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test all

/lgtm

/lgtm


Case-insensitive command names

I think there should be an option to make command names case-insensitive, or do it by default.
Use Case
There are many use cases for this, and here's an example. Imagine we have a bot that configures PC builds, and includes a footer like this in one of its messages:

See /available_CPUs.

This cannot be handled if the command name passed to the filter doesn't look like the one in the message. And once it's handled the way it is displayed to the user, it can't be handled when the cases are changed, say all lower like /available_cpus.
It is case-insensitive by default in most of the other bot frameworks.

I think it makes a lot of sense for the commands plugin to support this in some way or another. That would also allow the core library to stay lean and not add too many options. There has been little demand for this, but in my personal view, the commands plugin is the right place for supporting every edge case. What do you think?

Honestly, I thought we already supported this 😅
This makes total sense. I'll PQ in a few hours.

Honestly, I thought we already supported this 😅

I honestly was not sure about that, either lol

I'll PQ in a few hours.

So... "few" is a very subject measure okay? 😅


Updating Angular Dependency

This filter should work with Angular 1.3 as well.

Hi!
Could this pull request be merged ? (and released ?)
Thank you!

thanks for the contribution @dritter , and please forgive the delay, I've been really busy.
Here you go @denouche

Thank you very much!


Cluster state archives missing logs for istiod (pilot)

Bug description
Ref: https://preliminary.istio.io/latest/about/bugs/#kubernetes-cluster-state-archives
$ tools/dump_kubernetes.sh
Fetching debug/configz from pilot
Error from server (BadRequest): container istio-proxy is not valid for pod istiod-d49cfb444-n85pq
Fetching debug/endpointz from pilot
Error from server (BadRequest): container istio-proxy is not valid for pod istiod-d49cfb444-n85pq
Fetching debug/adsz from pilot
Error from server (BadRequest): container istio-proxy is not valid for pod istiod-d49cfb444-n85pq
Fetching debug/authenticationz from pilot
Error from server (BadRequest): container istio-proxy is not valid for pod istiod-d49cfb444-n85pq
Fetching metrics from pilot
Error from server (BadRequest): container istio-proxy is not valid for pod istiod-d49cfb444-n85pq

$ istioctl experimental describe pod istiod-d49cfb444-n85pq -n istio-system
Pod: istiod-d49cfb444-n85pq
   Pod Ports: 8080 (discovery), 15010 (discovery), 15017 (discovery), 15053 (discovery)
WARNING: istiod-d49cfb444-n85pq is not part of mesh; no Istio sidecar
--------------------
Error: failed to execute command on sidecar: error execing into istiod-d49cfb444-n85pq/istio-system istio-proxy container:
container istio-proxy is not valid for pod istiod-d49cfb444-n85pq

Expected behavior
Steps to reproduce the bug
tools/dump_kubernetes.sh

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version --remote
client version: 1.7.0-rc.1
control plane version: 1.7.0-rc.1
data plane version: 1.7.0-rc.1 (1 proxies)

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-17T08:59:10Z", GoVersion:"go1.14.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-30T20:19:45Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
$ istioctl install

Environment where bug was observed (cloud vendor, OS, etc)
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
istio-dump.tar.gz

cc: @costinm @howardjohn

Related: https://github.com/istio/istio/pull/24821


How to avoid electron-forge start?

Before using electron-forge, I simply start my app like this:
"start": "electron src/main"

Where src/main.js is a plain JS file. The app is just plain HTML/CSS/JS. I'm just keeping it simple. I don't want to introduce complexity to this.
How do we work with electron-forge for packaging and creating distributables, without interfering with the simple start process?

Use Electron Forge v6.

Alright, I'll give it a try.

For reference, after I try importing my app with v5.2.4, I get some errors when running my app.
Seems like electron-forge is either changing my dependencies, or changing something in my repo, but I don't know what.
Prior to the import attempt, I simply run my app with ./node_modules/.bin/electron src/main/index.js and it works great, just plain Node/Electron
But after installing electron-forge and importing, both my manual electron src/main and electron-forge start have an error.
I could post the error, but I have a feeling it is not relevant. I'm wondering what in the repo is being modified that breaks my app.
Do you have a concrete list of the modifications that electron-forge makes to an existing project? From what I can tell, I see it updates dependencies in package.json, and adds script to package.json. Anything else (though git isn't showing anything else).

@trusktr Anything the forge does through the import command will show in your git diff, it adds some dependencies, removes some dependencies, adds some config files and might move some files around.  But everything it does should be registered by git and diffable.
npx @electron-forge/cli import is the V6 way of doing things.  Check out https://v6.electronforge.io

I tried v6, and... it worked! Nice.
If I have "main": "src/main" in package.json, then what's difference between electron src/main/index.js and electron-forge start?

@trusktr It does a number of things for you.  Checks your current shell/OS is capable of running Electron, ensure any native modules are built and ready, powers our plugin system along with the forge hooks configuration you can set up.  It also does some cool stuff for restarting your app quickly.
You can just type rs into your terminal and hit enter and your app will restart.
I'd suggest you use the start command purely so that all this stuff is handled for you, even if your app is simple now, one day you're gonna add a native module and cry unless you're using start 😄


QT: more releases are planned even for non-commercial 5.x

Link to product page on endoflife.date
https://endoflife.date/qt
Details of incorrect and correct details you have found
5.15 EOL date is not only commercial
What is the source website for the product and for its version information?
https://wiki.qt.io/Qt_5.15_Release
See also: https://github.com/Homebrew/brew/pull/16417#issuecomment-1874109966
Additional context
Add any other context or screenshots about the incorrect details.

Thanks for raising this issue @SMillerDev.
That's not an easy one, so let's recap:

5.15 is documented as EOL on 26 May 2023 for "normal" users (26 May 2025 for commercial users), see https://www.qt.io/blog/qt-5.15-released.
The KDE Project maintains a patch collection to support Qt 5.15 LTS for open-source users.
All commercial updates become free after one year according to https://github.com/Homebrew/brew/pull/16417#issuecomment-1874109966 (quickly searched but did not found an official source).

So for using the 5.15 either you stick to the latest 5.15.x version released before 26 May 2023, or you need to subscribe to a commercial license. This seems confirmed by https://www.qt.io/blog/commercial-lts-qt-5.15.14-released:

Qt 5.15.14 is the last patch release during the standard Qt 5.15 Long-Term Support (LTS) phase that ends on 26th May 2023. The subsequent two years of patch releases will only be available to subscription license holders. For more information, see the May 26th, 2023: Qt 5.15 Standard Support for Legacy License Holders Ends Today and Extended lifetime for Qt 5.15 blog posts.

So here is what we can fix:

the latest 5.15 should not be 5.15.2, which was released in 2020 but 5.15.14. Reverting the latest to this version in https://github.com/endoflife-date/endoflife.date/commit/999e7d4a9f03ce2ddeb5ba9500952efa9a8d3645 was a mistake and needs to be fixed.
we should document the free after one year rule if we can find an "official" link (e.g. something on a qt.io website).

But this won't change anything for the EOL date though. Do you see something to do at this level @SMillerDev ?

@bo98, do you maybe have a link?

Indeed this is a complicated one.

5.15 is documented as EOL on 26 May 2023 for "normal" users (26 May 2025 for commercial users), see https://www.qt.io/blog/qt-5.15-released.

Depends what you mean by a "normal" user. The 2023 date is also a commercial support end, just of a different purchasing tier.
The timeline is more like this:

2021: open source/free support ends and the first commericial-only release is made: https://www.qt.io/blog/commercial-lts-qt-5.15.3-released
2023-05-26: support for commercial users on fixed-term or perpetual licenses ends however those paying on a recurring subscription basis continue to have support (likely because the fixed-term payments were only for 3 years but subscription is constant so can fund longer): https://www.qt.io/blog/qt-5.15-support-ends
2025-05-26: end of Qt 5.15 fully (though last open source release will be 2026)

A contractual agreement made with the KDE Free Qt Foundation means all commercial releases must be made public within a year. This wasn't announced on the Qt blog and is largely quiet from the Qt Company side but KDE do mention it at https://kde.org/community/whatiskde/kdefreeqtfoundation/. This policy has held true, as 5.15.3 was released in 2022: https://lists.qt-project.org/pipermail/development/2022-March/042262.html. This is expected to continue even now that we're in extended subscription-only support.
So it's basically like this:

Version
Open-source (free)
Fixed-term commercial
Extended commercial (subscription)

5.15.0
2020-05-26

5.15.1
2020-09-10

5.15.2
2020-11-20

5.15.3
2022-03-04
2021-03-04

5.15.3
2022-03-04
2021-03-04

5.15.3
2022-03-04
2021-03-04

5.15.3
2022-03-04
2021-03-04

5.15.3
2022-03-04
2021-03-04

However security support still seems to continue. I've not seen any written policy on this so it's maybe informal but here's an example of a security patch being issued for 5.15 for free just two days ago (well into the subscription-only LTS period): https://www.qt.io/blog/security-advisory-potential-integer-overflow-in-qts-http2-implementation with the patch available at https://download.qt.io/official_releases/qt/5.15/0001-CVE-2023-51714-qtbase-5.15.diff and https://download.qt.io/official_releases/qt/5.15/0002-CVE-2023-51714-qtbase-5.15.diff. There's several previous patches been issued in 5.15 over the LTS period: https://download.qt.io/official_releases/qt/5.15.

Indeed this is a complicated one.

5.15 is documented as EOL on 26 May 2023 for "normal" users (26 May 2025 for commercial users), see https://www.qt.io/blog/qt-5.15-released.

Depends what you mean by a "normal" user. The 2023 date is also a commercial support end, just of a different purchasing tier.
The timeline is more like this:

2021 (first release after Qt6): open source/free support ends and the first commericial-only release is made: https://www.qt.io/blog/commercial-lts-qt-5.15.3-released
2023-05-26: support for commercial users on fixed-term or perpetual licenses ends however those paying on a recurring subscription basis continue to have support (likely because the fixed-term payments were only for 3 years but subscription is constant so can fund longer): https://www.qt.io/blog/qt-5.15-support-ends
2025-05-26: end of Qt 5.15 fully (though last open source release will be 2026)

A contractual agreement made with the KDE Free Qt Foundation means all commercial releases must be made public within a year. This wasn't announced on the Qt blog and is largely quiet from the Qt Company side but KDE do mention it at https://kde.org/community/whatiskde/kdefreeqtfoundation/. This policy has held true, as 5.15.3 was released in 2022: https://lists.qt-project.org/pipermail/development/2022-March/042262.html. This is expected to continue even now that we're in extended subscription-only support.
So it's basically like this:

Version table

Version
Open-source (free)
Fixed-term commercial
Subscription commercial

5.15.0
2020-05-26

5.15.1
2020-09-10

5.15.2
2020-11-20

5.15.3
2022-03-04
2021-03-04
As per fixed-term

5.15.4
2022-05-11
2021-05-12
As per fixed-term

5.15.5
2022-06-17
2021-06-18
As per fixed-term

5.15.6
2022-09-07
2021-09-08
As per fixed-term

5.15.7
2022-10-28
2021-10-29
As per fixed-term

5.15.8
2023-01-04
2022-01-04
As per fixed-term

5.15.9
2023-04-06
2022-04-06
As per fixed-term

5.15.10
2023-06-07
2022-06-07
As per fixed-term

5.15.11
2023-10-05
2022-10-05
As per fixed-term

5.15.12
2023-12-22
2022-12-27
As per fixed-term

5.15.13
~2024-03-09
2023-03-09
As per fixed-term

5.15.14
~2024-05-25
2023-05-25
As per fixed-term

5.15.15
~2024-08-31
N/A - see open source
2023-08-31

5.15.16
~2024-11-17
N/A - see open source
2023-11-17

5.15.17
~April 2025
N/A - see open source
~April 2024

5.15.18
~October 2025
N/A - see open source
~October 2024

5.15.19
~April 2026
N/A - see open source
~April 2025

However security support still seems to continue, at least at some level. I've not seen any written policy on this so it's maybe informal but here's an example of a security patch being issued for 5.15 for free just two days ago (well into the subscription-only LTS period): https://www.qt.io/blog/security-advisory-potential-integer-overflow-in-qts-http2-implementation with the patch publicly available at https://download.qt.io/official_releases/qt/5.15/0001-CVE-2023-51714-qtbase-5.15.diff and https://download.qt.io/official_releases/qt/5.15/0002-CVE-2023-51714-qtbase-5.15.diff. There's several previous patches been issued in 5.15 over the LTS period: https://download.qt.io/official_releases/qt/5.15.
And to confuse things even more, QtWebEngine does not have a commerical-only period at all due to further license restrictions from using Chromium. So the current version, QtWebEngine 5.15.16 LTS, is available free for everyone: https://code.qt.io/cgit/qt/qtwebengine.git/tag/?h=v5.15.16-lts

Thanks a lot for all those information @Bo98. I tried to update and summarized what you said in #4451. A preview is available on https://deploy-preview-4451--endoflife-date.netlify.app/qt, could you give me your opinion about it ?

Looks good to me, though I'd maybe rename the first column (eolColumn I think) to something else than the current "Security Support".

Looks good to me, though I'd maybe rename the first column (eolColumn I think) to something else than the current "Security Support" naming.

Thanks for the feedback, changed to "OSS support".


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


tech.ml.datatype mentioned in the doc

https://github.com/scicloj/tablecloth/blob/1e9c8d88c46cdf4492f8fd0e219b4f6af94886a9/docs/index.Rmd#L138
tech.datatype is not active anymore.
It'd make more sense to mention either tech.ml.dataset or dtype-next here.

Thanks Daniel. Can you make a PR or update directly? I will refresh docs and publish then.

The Columns section makes a similar mention, should this mention be removed?
https://github.com/scicloj/tablecloth/blob/ee091ed8afab3a3d52371c2234a4aa65e21214ec/docs/index.Rmd#L875
Becomes Column is a special tech.ml.dataset structure. For our purposes we cat treat columns as typed and named sequence bound to particular dataset.
I can make a PR for this.

Thanks for spotting it. Yes, please, PR welcome!


RFC: Restructuring the structure

I'm generally unhappy with the structure of the docs, especially the guides feel quite unordered and cluttered.
My current thoughts are to group them thematically, in sections like "making mods", "clientside mods", "serverside mods".
i also want the meta-documentation moved to it's own section (restructuredtext cheatsheet, how to contribute) and possibly expanded into docs on contributing to Northstar.

cc: @GeckoEidechse @Dinorush

Agreed sidebar could use some cleanup ^^
In particular something that would also be nice, would be collapsing sections by default, so that on a standard 1080p screen, all main sections are visible on the sidebar without scrolling and then organising things in a proper tree view.
As for how to organise the sections, we have

Quickstart guides
Squirrel related
Skins/Repak
Mapping (related to skins but not quite, very WIP)
Native/C++ and in the future plugins

where the native C++ part is a bit of an odd one out as it is less modding and more development related.
I think something like the above listing could work for the main sections.
Where applicable some guides could also be moved to their respective category but some should stay top-level (like how to upload to Thunderstore) simply cause they encompass multiple of the main headings.

cc: @GeckoEidechse @Dinorush

19th century abbreviation :skull:

lol 💀

so

It might be worth separating "guides" and "docs" IE, how to use a specific function or feature vs how to create a mod from scratch with.

with the closing of #134 i consider

Closing as completed with #134
A few restructure should be done on the new docs located at https://github.com/R2Northstar/NorthstarDocs anyway ^^


Renaming module hpx_parallel_executors into hpx_executors

Just giving it a shorter name. Also, not all implemented executors are 'parallel'...

… or should we name it hpx_execution - might be even more appropriate ...

… or should we name it hpx_execution - might be even more appropriate ...

Good idea. execution would match the standard library header. With that name we would also end up with a global header called hpx/execution.hpp which I think is nicely consistent. The related question to this is if we should move the executors into hpx::execution or even just hpx. The documentation doesn't help here, but we've noticed people having trouble figuring out e.g. that par is in hpx::parallel::execution (plus it's quite a mouthful). I'd be in favour of going all the way up to hpx since that would make the std::par to hpx::par replacement more natural, but hpx::execution would be more consistent with what we've been doing with some of the other modules.

@msimberg The standard has par and friends in std::execution::par (https://en.cppreference.com/w/cpp/algorithm/execution_policy_tag). If we are going to change the namespaces we should move them into hpx::execution. Otherwise I agree 100%.

@msimberg The standard has par and friends in std::execution::par (https://en.cppreference.com/w/cpp/algorithm/execution_policy_tag). If we are going to change the namespaces we should move them into hpx::execution. Otherwise I agree 100%.

Thanks for correcting me! That makes the decision easier I guess. Let's do hpx_execution for the module name then and try to move the functionality to hpx::execution eventually as well.


FEAT Add Copilot Target

Power Pwn connects to copilot; we should add a copilot Target!
https://github.com/mbrg/power-pwn/blob/main/src/powerpwn/copilot/copilot_connector/copilot_connector.py
This should follow the same format as other targets.

@romanlutz I would like to give this open issue a try

Perfect. Reach out if you have any questions or if you want to discuss how to approach this.

Good morning all,
we would like also to add the copilot target to our arsenal of tools with PyRIT.
What is the status on that feature request ?Is the code from powerpwn compatible with the PyRIT project ?

@yachang1125 do you still plan on working on this? If not, we can make it available to others.
@HugeekMcGill are you interested in contributing or mainly asking as a potential user?

@romanlutz both.
I haven't open the PyRIT code deeper enough to integrate it straight away but i could possibly do it I guess, no choice. We need this target and I can help out, just need to ramup

I'm checking with @yachang1125 but it's probably fair to assume that you can pick this one up. Please don't hesitate to ask questions.


Add distributed plugin support

This has been updated with tests, and to support the "discovery" and "accelerate" concepts in the distributed query system.


[Popper] Fix deep merge of PopperProps

Problem
The tooltip arrow positioning was incorrect after passing custom PopperProps to the Tooltip component. We want to pass custom Popper modifiers into the underlying popper.js instance, but could not do so without causing the tooltip arrow positioning to behave unexpectedly.
Investigation
We discovered that the arrow modifier that gets passed to popperOptions was being overwritten as a result of passing anything else in popperOptions.
Solution
Deep-merged the default popperOptions arrow modifier with the custom modifiers passed in by the user.

[x] I have followed (at least) the PR section of the contributing guide.

@valgrindMaster Thanks for raising this issue and working on it! :)

Thanks @oliviertassinari for helping us out with those unit tests, and for such a quick turnaround with the 4.9.5 release! Very much appreciated!


Anonymous Sign In Crash

Goals
Realm should not crash when signing in with Anonymous sign in. The crash is occurring with 10.0.0-beta.6, however I believe it did not crash with beta.4
Expected Results
See above
Actual Results
When signing in with anonymous sign in, Realm Crashes
Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
Steps for others to Reproduce
Use anonymous authentication
Code Sample
MyRealmApp.login(credentials: Credentials.anonymous()) { user, error in
    DispatchQueue.main.sync { //<------- this is the line that crashes
        guard error == nil else {
            print("Login failed: \(error!)")
            return
        }
        print("anon login success")  // Now logged in, do something with user
    }
}

Version of Realm and Tooling
MongoDB Realm
pod 'RealmSwift', '=10.0.0-beta.6'
macOS 10.14 & 10.15
XCode 11.3

Creating a quick ad-hoc app confirms the same. This occurs when an anonymous user has previously logged in on the device.

We'll need to look into this more.

For what it's worth, a check for logging out current users appears to workaround the crash. But I'll still update here once I know more.

@visdyn
When logging in an anonymous user we check to see if a logged-in anonymous user exists. If so, we'll pull the existing anonymous user from the syncManager, set that as the current user, then return that user in the callback.
I believe the DispatchQueue.main.sync within the callback is causing a deadlock when this happens. If you remove this do you still see the crash?

@visdyn
Perfect, thanks. I'm going to close this issue because .logIn is behaving as expected.
The recommendation here is: steer away from using the main.sync in completion blocks. It's not guaranteed as legal in most completion handlers. If you need to dispatch something to .main, please use .async.

@ericjordanmossman
If the issue is being closed, you may want to also update the documentation example(s)
https://docs.mongodb.com/realm/ios/authenticate/#anonymous-authentication

Yes for sure :). They've been notified.


initial commit for adding the p wave pick function

Summary

This change implements a P wave arrival-time pick function based on the probability prediction from machine learning model.

It leverages the SeisBench PhaseNet model for the probability prediction.
A probability threshold is used to choose picks.
Time window is supported for focusing on a certain period of the input.

Testing

unit test added

to fix the docker issue, we can try

exclude cuda library from seisbenc
clean up cache: https://github.com/mspass-team/mspass/actions/caches
try removing https://github.com/mspass-team/mspass/blob/7f959aa19e4fc3393bced4061067032df7b6db95/.github/workflows/docker-publish.yml#L108C1-L109C59

Hi @wangyinz please take a look at this pr, it's ready for review. Thank you.

Hi @wangyinz could you please review this pr? thank you

Sorry for the delays! I just merged it.


Could not resolve "mock-aws-s3"

Hello
I started a starter react project with vite and got thoses errors below
I wanted to test it quickly in a frontend with mapbox and then put the logic in the back
To reproduce

pnpm create vite radars2 --template react-ts
pnpm install @radarlabs/s2
change app.tsx
pnpm dev

import './App.css';

import viteLogo from '/vite.svg';
import { useState } from 'react';

import reactLogo from './assets/react.svg';

const s2 = require('@radarlabs/s2');

function App() {
  const [count, setCount] = useState(0);
  const s2LatLong = new s2.LatLng(32.715651, -117.160542);
  const cellCoveringOptions = { min: 6, max: 13, max_cells: 10 };
  const coveringCells = s2.RegionCoverer.getRadiusCovering(
    s2LatLong,
    10000,
    cellCoveringOptions
  );
  console.log(coveringCells.cellIds().map((cellId) => cellId.token()));
  return (
    <>

Vite + React

        <button onClick={() => setCount((count) => count + 1)}>
          count is {count}
        </button>

          Edit src/App.tsx and save to test HMR

        Click on the Vite and React logos to learn more

    </>
  );
}

export default App;

[ERROR] Could not resolve "mock-aws-s3"

    node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:43:28:
      43 │     const AWSMock = require('mock-aws-s3');
         ╵                             ~~~~~~~~~~~~~

  You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove
  this error. You can also surround this "require" call with a try/catch block to handle this
  failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "aws-sdk"

    node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:76:22:
      76 │   const AWS = require('aws-sdk');
         ╵                       ~~~~~~~~~

  You can mark the path "aws-sdk" as external to exclude it from the bundle, which will remove this
  error. You can also surround this "require" call with a try/catch block to handle this failure at
  run-time instead of bundle-time.

✘ [ERROR] Could not resolve "nock"

    node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:112:23:
      112 │   const nock = require('nock');
          ╵                        ~~~~~~

  You can mark the path "nock" as external to exclude it from the bundle, which will remove this
  error. You can also surround this "require" call with a try/catch block to handle this failure at
  run-time instead of bundle-time.

adding the libs doe not generate the errors anymore but i got the following errors in the browser console
pnpm add<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Uncaught ReferenceError: process is not defined     at module2.exports.get_mockS3Http (s3_setup.js:108:3)     at<EMAIL_ADDRESS>(node-pre-gyp.js:15:49)     at __require2 (chunk-6NOISVLF.js?v=fa4056a4:16:50)     at<EMAIL_ADDRESS>(index.js:2:16)     at __require2 (chunk-6NOISVLF.js?v=fa4056a4:16:50)     at index.js:6:18

i'm getting the same error when i deploy my sveltekit website ,any idea how to remove it please ? , my problem is i don't have any line that importing mock-aws-s3


add logic to run github_changelog_generator in container

What type of PR is this?
/kind cleanup
What does this PR do / why we need it:
Now it is not required to install github_changelog_generator on your system to generate changelog.

/approve


Run logical optimization passes in init stage

Summary
This commit adds Optimize1qGatesDecomposition and InverseCancellation to the init stage for optimization levels 1, 2, and 3. The optimizations these passes run are completely valid on abstract circuits and do not require target qubits to be selected to run
(Optimize1qGatesDecomposition is noise aware and will perform target aware optimizations if one is provided, but if no target information is reported it will operate correctly for any circuit)
Details and comments

Let's add a logical optimization stage. I think it's totally reasonable to break this out into a stage. FWIW, the description and expectations of the init stage is currently:
This stage runs first and is typically used for any initial logical optimization. Because most layout and routing algorithms are only designed to work with 1 and 2 qubit gates, this stage is also used to translate any gates that operate on more than 2 qubits into gates that only operate on 1 or 2 qubits.

which I felt included this. But I think you're right we probably should separate this out form init as it'll make things like doing custom optimizations easier to plug in and not have to worry with gate unrolling or any other circuit preparation.