Add clickZoom to MarkerClusterOptions

Added clickZoom boolean property to MarkerClusterOptions, similar to the ZoomOnClick property of Google's markerclustererplus. Defaults to true, so default behavior is unchanged.
If setting to false, one can use the 'cluster_click' event to decide if/when and how to zoom on cluster clicks.

Why do you want to the feature? Please explain the purpose.

It's so you can customise the behavior in the marker clusterer click handler. Firstly, if you have data points on top of each other, these are best left clustered (another explanation, see second comment on #1905). Zooming in further has no purpose. We are better off handling the all of the data points by, say, displaying a scrolling list on a pop up.
http://zahwa.aikuma.org is a demonstration of this using the javascript API with markerclusterer plus (you will need to  navigate to Taiwan).
Without this, the marker cluster implementation is useless for my use case.
Secondly, you can implement your own zoom. I find, for example, that cluster.getbounds() needs to be modified before passing to the maps view. Markers will be at the extreme edge of the screen and partially visible.

Firstly, if you have data points on top of each other, these are best left clustered

I can not imagine the situation. Please show me the example image.
And if the current implementation is not fit for you, implementing another argorithm would be better for you (by yourself).

I'll try again. Imagine ten data points with exactly the same coordinates (or very close). This is extremely common if your data are user contributions.
The algorithm is fine. Wjat you have done is 99% of the way there. This PR is a very simple change that mirrors an enhancement added in Google's markerclustererplus for exactly the same use cases. I can't see what I can do to.make this clearer. I mean I could show you a custom pop up resulting from clicking a cluster but... Does that really help?
We just want to trigger our own pop-up when a cluster is clicked on at a certain zoom level. I've also explained that the existing zoom behavior is not ideal and it'd be nice to just do your own to zoom if you want. This requires stopping the current click to zoom behavior, that's all.

An example using Javascript API on desktop with Google's markerclustererplus. This is a highly zoomed map, all seven markers are recipes by the same person, so are very close together. In this app, I simply disable click to zoom and handled it manually. When the zoom level is at a certain point, clicking on the cluster does not zoom, instead we trigger a pop up to show all of the data.

You can modify on forked repository. Why do you need to send this PR? Smart phone has small display than desktop. So I can't agree such a popup is good for everyone

Okay this is getting ridiculous. The example shot is from a desktop app, on mobile my forked repo obviously does something suitable for mobile, that is irrelevant.
I've also explained to you that the current zoom is not great (am I'm being polite), and it's totally reasonable for us to implement the zoom ourselves. Jesus for the sake of six lines that does nothing but provide an option allow us to bypass some really inflexible and sub optimal code... An option is not everyone, and we PR because we hope to maintain parity with upstream and benefit from ongoing maintenance and bug fixes.
Anyway forget it, I'll just join the other 600 forks until I can replace this whole thing... sheesh.


Implement environment variable emulation on Windows

Currently, GetEnvironmentVariableW just always returns "env var not found".
Mentoring instructions available

Hello, I'm interested in working on this issue. @RalfJung , may I ask which file I should be working on for this issue?? Thank you :)

@JOE1994 great! Do you have a Windows system to do the development on? Without that, the testing will be a bit annoying as we'll have to use AppVeyor and bors for that. OTOH, I have zero experience with development on Windows, so you might have to do some experiments to get Miri to build and run locally.
The env var implementation for Unix is at
https://github.com/rust-lang/miri/blob/ce5e910e602a46c7e18a6f2f731ddac971da8fdb/src/shims/foreign_items.rs#L414-L493
It would probably be a good idea to start by moving as much of this as possible into a new env.rs module (inside src/shims). foreign_items.rs is already way too long anyway. ;) And then you'll have to figure out which foreign functions libstd calls on Windows for reading and writing environment variables, and emulate them. You can use this test case for that, running it in Miri will tell you which foreign function gets called that is not implemented. GetEnvironmentVariableW will likely be the first one.

Hi, @JOE1994 did you get a chance to look at this? I have been working on the linux side of this and I could give you a hand.

Hello @christianpoveda ,

Hi, @JOE1994 did you get a chance to look at this? I have been working on the linux side of this and I could give you a hand.

That is really nice of you! 👍 I apologize for being irresponsible in working on this issue..
Can I get back to you in a few days after I review the MIRI code and get a better understanding of it?

That is really nice of you! +1 I apologize for being irresponsible in working on this issue..

Don't worry, that happens from time to time.

Can I get back to you in a few days after I review the MIRI code and get a better understanding of it?

Sure, feel free to ask any questions :)

On Widows 10, using rustc 1.40.0-nightly (032a53a06 2019-10-03).
Currently failing call to "SetEnviromentVariableW"

Yes so SetEnvironmentVariableW and GetEnvironmentVariableW are the first two shims that need to be implemented. Those are the equivalents of getenv and setenv (which can be found here).  You need to do the same for the windows shim but taking care of the encoding.

@christianpoveda  Thanks for your help! Can I ask you a question? 😀 😀
I'm currently trying to write code for handling GetEnvironmentVariableW in Windows.

It seems like args[0] and dest should have a same size, in Linux the sizes are the same, but in Windows the sizes are different as below (8 vs 4). It's embarassing to keep asking questions for an E-easy issue, but can you give me some directions on what to do next??
args[0] : &[rustc_mir::interpret::OpTy is an immutable reference, and
dest : rustc_mir::interpret::PlaceTy also contains a member variable place which seems to contain an index to a mir::Local. I'm not sure what I should do here to make args[0] and dest compatible in terms of their layout and size.

Hi. So the problem seems to be that GetEnvironmentVariableW has an slightly different behavior than getenv.
What GetEnvironmentVariableW does, is taking 3 arguments. A pointer to the name of the variable, a pointer to a buffer where the value of the variable will be written, and the size of such buffer (let's say n) . Then the function writes at most n bytes to the buffer and returns an integer to indicate if the operation was successful. More details here.
In contrast, what getenv does is taking as argument a pointer to the name of the variable and then returning a pointer to the value of the variable.
So what we can do here is implement the windows shim in a different function first, be sure that it works. and then try to deduplicate the code that is also used in the Unix shim.
About asking questions, is not embarrassing at all, we are all learning here :)
I'll write more detailed instructions about how to write to a buffer and such tomorrow. I'm in my phone right now :P

It's embarassing to keep asking questions for an E-easy issue

It totally isn't!
Also when I assigned the E-easy label, that was a guess. And even if this issue is easy as Miri issues go, there's still a lot of API surface to learn here.

Another problem you might run into is that GetEnvironmentVariableW probably works with wide strings (the W is suspicious), meaning 2 bytes per character. You'll need something like the Windows OsStringExt to convert that to something you can use in the interpreter.

@JOE1994 some tips:
The signature of this function is:
DWORD GetEnvironmentVariableW(LPCWSTR lpName, LPWSTR lpBuffer, DWORD nSize);

A brief description of the arguments:

lpName is a pointer to wchar_t (those are wide chars, because windows use 2 bytes to encode characters instead of just 1). This points to the name of the variable
lpBuffer is a pointer to char_t (regular 1 byte chars). This is the buffer I mentioned before, where the value of the variable is supposed to be written.
nSize is a 32-bit unsigned integer. It represents the size of lpBuffer.

Instructions:

The args variable contains a bunch of OpTy representing the arguments of the foreign function in the same order as stated above (lpName is args[0] and so on). Take each one of these OpTy and transform it to a more proper representation:

lpName and lpBuffer are both pointers so they need to be transformed from OpTys to Scalars to be able to read to what they are pointing to. This is done in the same way as with the only argument of getenv using InterpCx::read_scalar and then ScalarMaybeUndef::not_undef.
nSize can be transformed into an integer by turning it first into an scalar using InterpCx::read_scalar, this return an ScalarMaybeUndef, then you can use ScalarMaybeUndef::.to_u32 to turn it into a proper integer.

Then after you have lpName as a Pointer you can read from it using Memory::read_c_str. I'm not sure if this will misbehave somehow because lpName is a pointer to wide chars and not just chars, this will return a Vec<u8> which is the actual name of the variable.
With the name of the variable, you can recover the Pointer to the value of the variable that is stored in the EnvVars struct. Then you can read from this pointer in the same way as with lpName to recover the value of the variable, except for one detail: Right now all variables are stored as NAME=VALUE so you need to offset this pointer to not include the NAME= part. You can check getenv to see how to do it.

After this we "just" need to write the actual value to lpBuffer, we can get into that later. Until this point just be sure that the value of a variable actually has what it is supposed to.
PD: I wrote this in the wrong issue, silly me.

@christianpoveda @RalfJung  You guys are so awesome! 😸 I'm on it 😄

Just a brief update.. The latest version of MIRI builds and runs successfully in Ubuntu (under Windows Subsystem for Linux),  but fails to build in my Windows machine. On Windows, there is an issue with linking the syntax crate which seems to be a rustc_private feature. I haven't been able to find out the cause of this issue..

You need to run rustup component add rustc-dev --toolchain nightly.

Thank you for all your help! 😄
Using Memory::read_c_str() to the Pointer of lpName misbehaved,
since utf-16 characters contain a null byte for ASCII characters (ex. A = 0x0041).
I used a more dirty way to read a string from the Pointer of lpName.
Is there a way to convert rustc_mir::interpret::OpTy to rustc_mir::interpret::PlaceTy ?
I want to store the fetched environment-variable's value to lpBuffer, but lpBuffer is of type
OpTy and I'm stuck on how to convert it to PlaceTy so that I can use write_scalar.
Below is a screenshot from my src/shims/env.rs.

Using Memory::read_c_str() to the Pointer of lpName misbehaved,
since utf-16 characters contain a null byte for ASCII characters (ex. A = 0x0041).

Good point. So how do these strings work? Are they terminated by two null-bytes? If yes, I think we should add a new method Memory::read_wide_c_str or so.

I want to store the fetched environment-variable's value to lpBuffer, but lpBuffer is of type
OpTy and I'm stuck on how to convert it to PlaceTy so that I can use write_scalar.

Oh, lpBuffer is a pointer here, right? You will want to use this method to write the actual string. write_scalar wouldn't work, the entire string is not a scalar!

@JOE1994 Maybe it would make sense, as a "warm-up exercise", to do some work on the existing env var emulation. To share code between Unix and Windows, we probably want to use OsStr/OsString in that file as much as we can. (This means support for non-unicode vars will not work properly on Windows hosts, which is fine for now.) That should help you better understand where "host data" (i.e., things in the interpreter) is converted to and from "target data" (i.e., things encoded in the memory of the interpreted program).

Add a new helper method in helpers.rs called alloc_os_str_as_c_str. This is basically just turning the following code into a function:

https://github.com/rust-lang/miri/blob/94732aaf7bf79fd01a4a48d11155c6586b937514/src/eval.rs#L83-L87

In env.rs, change the type of EnvVars::map to HashMap<OsString, Pointer<Tag>>.

In env.rs, rename alloc_env_var to alloc_env_var_as_c_str and make it use alloc_os_str_as_c_str instead of allocate_static_bytes.

In env.rs, replace all uses of read_c_str by read_os_str_from_c_str.

That can all be one PR.

Then, in a next step, we need to have support for reading/writing host OsStr to "wide strings" (not just "c strings" as we have now). So the goal there is to have 2 new methods, read_os_str_from_wide_str and write_os_str_to_wide_str. That is the part where you will need a PR on the rustc side to implement the "read" version of this. But the "write" version can already be implemented, and in fact we basically already have it:
https://github.com/rust-lang/miri/blob/94732aaf7bf79fd01a4a48d11155c6586b937514/src/eval.rs#L132-L141
With those methods in place, we can then have higher-level methods read_os_str_from_target_str and write_os_str_to_target_str that, depending on the target OS, dispatch to the c_str or the wide_str methods. We probably also want the corresponding alloc_* method (both for "wide_str" and "target_str"). And at this point I think we should put all those string helpers into a new file, shims/str.rs, to avoid bloating helpers.rs too much.
At this point, it should not be hard to implement support for current_dir and set_current_dir on Windows.  That should be the goal for the second PR: to get this test working on Windows. That should basically be a matter of adjust this code to use the new "target_str" methods, and to wire this up in foreign_items.rs.

For the third PR, we tackle env var emulation. I think env var simulation should be able to use the new "target_str" methods to have fairly uniform code paths for Unix and Windows.

https://github.com/rust-lang/rust/pull/69326 landed upstream. :) I think the rest of this can happen in Miri, starting with having wide_str versions of all the c_str helpers that we already have.

Fixed by https://github.com/rust-lang/miri/pull/1225 :)


Don't checkout anything by default on local templates

I'm currently translating a cookiecutter template to a copier one, and each time I change something, I have to commit the change for copier to pick it up. At first it was confusing ("why did files that I removed were copied??"), and now it's annoying (a "wip" commit for every change, and then I'll have to squash them or something).
I think it's because copier tries to checkout the latest tag? I'd like it not to do anything if I don't specify the -r, --vcs-ref option.

This is important because copier uses git tags to handle upgrades. Also, copier needs a ref to be saved into the _commit key in .copier-answers.yml.
However, I agree this is a little pain point for template development.
One thing I do is:

Commit your changes.
Add --vcs-ref=HEAD to your copy command.

For unit tests, however, I simply use this pytest fixture, which clones the current template into a temporary directory, including dirty changes, applies a test tag (so I know .copier-answers.yml will always have _commit: test) and returns the Path to that clone, which can be safely used in TDD.
Copier could include a --vcs flag with these options: auto, git, none. It should default to auto (use git if available, none otherwise), but this way users could just give --vcs=none and skip all the gitty stuff.

Copier could include a --vcs flag with these options: auto, git, none. It should default to auto (use git if available, none otherwise), but this way users could just give --vcs=none and skip all the gitty stuff.

That would be great :slightly_smiling_face:
I totally get why the checkouts are important for being able to update the generated projects, though if users could disable it it could really facilitate the development!

It's especially annoying when you have tests for your template: you must commit before running the tests :rofl: !

Not with that fixture provided above. Although you're right this should be fixed.

Oh yes, thanks you! I happen to have written my tests in a simple shell script though :sweat_smile:
But I'll use your fixture if I convert them to a pytest suite.

You can also emulate that fixture as a bash function, it's quite easy.

I'm thinking that a good fix might be to supply that fixture with Copier, so downstream templates can reuse it.

As suggested in #412, could we make these two commands behave differently?

copier . ./tmp

use the local changes instead of the git repo if template_src is not a url

copier copy https://github.com/copier-org/autopretty.git .?

as-is
If this is not what you intended or I'm not understanding a different workflow, then perhaps a flag --local or (--no-git) to change the behavior.

As a user I want to be able to test templates quickly/iteratively using existing cli tool (not via pytest fixture)

Yes, well that makes sense indeed.
However, I cannot predict what you want to test. Is it a copy, a recopy or an update? Besides, when copying a non-git template, the results and features are different, so you could get to unexpected results when comparing your dev with production environments.
However I guess that we can make this assumption: if the template is a local directory and it is dirty, you're developing the template, so you're going to want to test those dirty changes, so Copier could take the freedom to do the wip commit dance automatically and print a warning so you are aware of that.

I'd also really like to see this feature in some kind.
Just some ideas which would simplify local testing during development:

add a flag like --vcs-ref=dirty or something like that. (semantic: if it is a local git repo, just add -dirty to the commit-hash for the answer file and use the dirty, checked out version)
use --vcs-ref=none to disable the git tag stuff completely. IMHO this is completely sufficient for a quick test. Even if the result might differ slightly from a git repository. You could also print a warning about the caveats.

This should only be relevant during development of templates. Depending on your workflow there is still the option to run a commit as soon as you assume you are finshed and run a "real life test with git" before publishing.

Those are OK until somebody creates a branch named dirty or none. 😄
I think I still prefer the suggestion from https://github.com/copier-org/copier/issues/184#issuecomment-861639395.


Use the new storage/messaging libraries

Closes wellcometrust/platform#3628
Now we can run lots of stuff in-memory, so it's faster and easier to debug. Containers we no longer need to run:

goobi_adapter: no DynamoDB
reindexer: no SNS
ingestor: no S3

Rough edges are being documented in wellcometrust/platform#3630

Closing in favour of #59.


[Resolver] Improve sorting of deps with 0 or 1 possibility

As the added comment says, this will force all dependencies where there are only 0 or 1 total specs with that name to be resolved first. Right now, they sort ~last, which leads to poor performance.
(This was one way of fixing some recent resolver issues, even though we've done the proper fixes in Molinillo for them)

I like this a lot, and I believe I have seen many cases of frustrating resolutions or weird conflicts that this will improve.
@bundlerbot r+


Bump eks version list and add v1.31

According to EKS available version list,
we have to add v1.31 and remove v1.27
https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html

Proposed changes

Types of changes

Linked Issues

Further comments

@mantis-toboggan-md  Can you review?

Closing in favor of https://github.com/rancher/dashboard/pull/12309


RHElement (now PatternFly Element) properties support

Hey @btopro, do you need anything added to the base class for RHElement (now PatternFly Element) properties to be wired up correctly?  I was just playing with the component factory and looking at the great stuff you've done with schemas and storybook.

I'll just note here that I'll be opening a PR soon that will include all the project rename updates.  We merged with another project at Red Hat called PatternFly which involved a rebranding.

I found the getter in the gulpfile!  I'll close this out and open a PR soon with the updated project name!  Thanks.

😁😁😁

https://github.com/elmsln/wcfactory/tree/master/packages/generator-wcfactory/generators/start/templates/templates/libraries/RHElement everything to rename and we will gladly accept the updates


More Notebooks and Examples

More Notebooks with different strategies and visualizations (matplotlib, bokeh, mplfinance)

Thanks a lot for creating this framework. Would it be possible to use pandas-ta over DataFrameGroupBy?
ggetDataFrame = getDataFrame.groupby('multiple_tickers')
ggetDataFrame['rsi'] = ggetDataFrame.ta.rsi(length=14)

Thanks! Glad you like it.
I have not tried DataFrame.groupby. If you have something setup already, give it a go and let me know. Just keep in mind that, ggetDataFrame has to be a DataFrame to work.
Regards,
KJ

Hello All,
Recently added the new Pandas TA Strategy Class Examples Notebook. Let me know if it is helpful or missing anything.
What other notebook topics would be helpful to add to the library to help users of all levels?
Have an Notebook you would like to share, put in a pull request.
Thanks for using the library!
KJ

Hello everyone,
It would be awesome if someone made a notebook where all available technical analysis techniques are implemented to a csv database of historical stock data. Is there such a thing?

Nevermind, I found it!
df.ta.strategy("all")
df_list = list(df.columns)
This script is the absolute bomb. Thank you for your efforts!


feat: forks support

Description:
Related issue(s):
Notes for reviewer:
Depends on: https://github.com/hashgraph/hedera-forking/pull/7
Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

As discussed, this PR should be open against branch of https://github.com/hashgraph/hedera-json-rpc-relay/pull/2875 (instead of main). Pls fix @arianejasuwienas.

@arianejasuwienas I guess we can close this in favor of

https://github.com/hashgraph/hedera-json-rpc-relay/pull/2875.

Replaced with: https://github.com/hashgraph/hedera-json-rpc-relay/pull/2875


fix cannot change context in cli issue

Checklist:
No need the parameter for get_cli_helper_sysprompt.  2729
def get_cli_helper_sysprompt() -> str:
    """
    Returns the system prompt to put the chatbot in CLI helper mode
    """
    return CLI_HELPER_SYS_PROMPT

2730, make sure mode_path is PATH

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

@jaideepr97 hi, could you please take a look this one?


CodePipeline: bucketKey is required but shouldn't be

I'm trying to specify a S3 bucket without a bucketKey as the store for source code store via:
val pipelineSourceAction = PipelineSourceAction(PipelineSourceActionProps.builder()
            .withActionName("source_action")
            .withRunOrder(1)
            .withBucket(Bucket.import_(this, "bucket", BucketImportProps.builder().withBucketName("shanetest-bucket").build()))
            .withBucketKey("") // should not end with slash!!!
            .build())

I've tried the following:

not specifying withBucketKey
specifying / as the key
specifying "" (empty string) as the key

On deploying the stack with the code above, I get the following validation error from CloudFormation:
8/9 | 15:55:46 | CREATE_FAILED        | AWS::CodePipeline::Pipeline | pipeline (pipelineDBECAE49) 1 validation error detected: Value '{S3Bucket=shanetest-bucket, S3ObjectKey=}' at 'pipeline.stages.1.member.actions.1.member.configuration' failed to satisfy constraint: Map value must satisfy constraint: [Member must have length less than or equal to 1000, Member must have length greater than or equal to 1] (Service: AWSCodePipeline; Status Code: 400; Error Code: ValidationException; Request ID: e86d50cc-58b5-4221-bd8e-cd035779bec8)
	new Pipeline (/tmp/jsii-kernel-6Hw0x3/node_modules/@aws-cdk/aws-codepipeline/lib/pipeline.js:48:30)
	\_ obj._wrapSandboxCode (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6496:49)
	\_ Kernel._wrapSandboxCode (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6972:20)
	\_ Kernel._create (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6496:26)
	\_ Kernel.create (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6249:21)
	\_ KernelHost.processRequest (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6023:28)
	\_ KernelHost.run (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:5997:14)
	\_ processRequest (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:5997:45)
	\_ promise.then.ret (/tmp/jsii-java-runtime7259556630644295243/jsii-runtime.js:6050:21)
	\_ <anonymous>

If I don't specify bucketKey, I get the following validation error from CDK:
Exception in thread "main" java.lang.NullPointerException: bucketKey is required
        at java.base/java.util.Objects.requireNonNull(Objects.java:246)
        at software.amazon.awscdk.services.s3.PipelineSourceActionProps$Builder$1.<init>(PipelineSourceActionProps.java:103)
	at software.amazon.awscdk.services.s3.PipelineSourceActionProps$Builder.build(PipelineSourceActionProps.java:101)
	at io.futz.stack.CodeBuildStack.<init>(CodeBuildStack.kt:54)
	at io.futz.MyAppKt.main(MyApp.kt:85)
	at io.futz.MyAppKt.main(MyApp.kt)

In the AWS console the bucket key is optional so I expect that I shouldn't have to specify it here.
I'm using latest (0.27.0) version of the CDK.

Hey @digitalsanctum ,
I'm not sure I understand what you're trying to do. The bucketKey property points to a ZIP file in your Bucket that will be used as the output of this Action. It is required in the console (see attached screenshot).
What would leaving out bucketKey mean in this context?

Oh my bad. Sorry for the confusion.


chore: merge release/15.6 changes into develop

Need to guard tsdb 2.9.1 from being built on anything above PG15 - @samrose is there any way of easily doing so?
timescaledb-apache> CMake Error at CMakeLists.txt:348 (message):
timescaledb-apache>   TimescaleDB only supports PostgreSQL 12, 13, 14 and 15

Need to guard tsdb 2.9.1 from being built on anything above PG15 - @samrose is there any way of easily doing so?
timescaledb-apache> CMake Error at CMakeLists.txt:348 (message):
timescaledb-apache>   TimescaleDB only supports PostgreSQL 12, 13, 14 and 15

@pcnc I am going to put a diff in the comments here on your branch that will work, please stand by

@pcnc I am testing the build of this PR here which should fix the issue and you can approve and merge it here if satisfied
https://github.com/supabase/postgres/pull/1321


Add Arrow to First Section and Resolve Alignment Issue in the Second Section

Issue Title:
Add Arrow to First Section and Resolve Alignment Issue in the Second Section
Issue Description:
The current design for the homepage requires a few visual adjustments. Specifically, we need to add an arrow icon to the first section under the job roles to guide users visually. Additionally, the second section ("Post Your Job Opening Today!") has alignment issues that need to be corrected to ensure a clean and consistent layout.
Provide me this issue assign with gssoc-ext label I can resolve it

@Abbas7120  go ahead but make sure it should not affect resposiveness of the component

Ok!


Name Generator

Name generation functionality, but I had to wrap to whole pseudorandom-generator module as well (namegen, noise requires this). The name generator has a very obvious limitation: you can only ever have one name generator at any given time. I have no idea how to wrap a global construct more elegantly, but we do need a separate structure to remain memory safe: libtcod would happily use random number generators that have already been freed (hence the stored copies in Namegen).
If there are any alternative API ideas, I'd be happy to hear them.

Looks good. I can't think of a better API now -- this seems sane enough. Not happy about the mutex but I see the point.
Eventually someone will write a better library that doesn't have to deal with libtcod's baggage and is much more Rusty, but until then, we'll make do :-).


Message on join/leave?

Hi @jimmycuadra
How would someone go about sending a message when a person join or leave a room ?
Thanks in advance for the help

Not possible currently, but not too difficult to add support for. lita-hipchat would need to hook into the on_join and on_leave methods of Jabber::MUC::SimpleMUCClient from the xmpp4r library: https://github.com/xmpp4r/xmpp4r/blob/4be950b6f6915de30f2550478308869495f54e45/lib/xmpp4r/muc/helper/simplemucclient.rb. When joining a room, callbacks would be registered with these methods similar to the existing register_muc_message_callback method: https://github.com/jimmycuadra/lita-hipchat/blob/e4958ecbb570db7e8d0deffb21722518f93f1d90/lib/lita/adapters/hipchat/connector.rb. The callbacks would then trigger events on Lita's robot object that handlers could use.
If you want to take a stab at implementing this, I'd be happy to accept a PR! Otherwise I'll leave the issue open as a feature request. Thanks for your interest!


Day134

Resolves #278.

Pull Request Test Coverage Report for Build 526

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 524:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

Pull Request Test Coverage Report for Build 517

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 524:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Notifiarr Compose - Invalid Env Vars

https://github.com/TRaSH-/Guides-Synology-Templates/blob/1c280bf06b3137a853b6800e164b2b6be21256c7/templates/notifiarr.yml#L20-L21
@BaukeZwart that update to add PUID/GUID should have never been made. GoLift Containers do not support PUID/PGUID
needs to be user: ${PUID}:${PGID}

I will rever it when I'm home.
Thanks for the heads up.

reverted


Simpler whiles

Simplify the while loops for map and zipWith.
I've QAd these locally by throwing tests in with the benchmarks. I've checked edge cases informally as well.

👍 LGTM if it works :) Sorry I missed this.

No prob.

Please feel free to make a release if you're happy.


how it work?

add example in readme?

Actually, this does not work with annotorious.min.js, so this is not really a plugin as such.
As I developed this with the development version of annotorious.js, so it works with it.
I have added an example of how this can be used here. But this is buggy.
[Demo] (https://harshalitalele.github.io/openseadragon-circular-annotation/)


Features: dual execution engine, webpack for browser, proper ErgoError contains file locations

Coverage increased (+0.2%) to 99.058% when pulling aa3a8979b0de217ea4e667c3cb4491bd2c5f8613 on js-feature-dual-engine into 2817b76fc73db3a8d46cd91cf4ac7606796bdd62 on master.


Add index to derivedBy and inputTo links of Files and Biomaterials

@aaclan-ebi does this definitely work? Just wondering because I tried using @Index before but with no success. Can you confirm it worked on your local machine?

yes it does! I tested it locally. The problem before is @Document annotation is missing.On Sep 12, 2018 8:12 AM, rolando-ebi<EMAIL_ADDRESS>wrote:@aaclan-ebi does this definitely work? Just wondering because I tried using @index before but with no success. Can you confirm it worked on your local machine?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.


*: fix 'gosimple', 'gounused' checks

To clean up Travis outputs...

test probably needs some changes to error out if these weren't causing CI to fail

@heyitsanthony @xiang90 Go build cmd seems like just returning 0 for build fails
https://github.com/golang/go/blob/master/src/go/build/build.go#L675
func exit() {
	for _, f := range atexitFuncs {
		f()
	}
	os.Exit(exitStatus) // exitStatus is 0
}

I tried to grep stderr
	if which gosimple >/dev/null; then
		echo "Checking gosimple..."
		for path in $GOSIMPLE_UNUSED_PATHS; do
			simplResult=`gosimple $REPO_PATH/${path} 2>&1`
			if [ -n "${simplResult}" ]; then
				echo -e "gosimple checking ${path} failed:\n${simplResult}"
				exit 255
			fi
		done
	else
		echo "Skipping gosimple..."
	fi

but this doesn't print out the actual error logs so makes it hard to debug; see here https://travis-ci.org/coreos/etcd/jobs/182730600.
All other errors are fixed. https://travis-ci.org/coreos/etcd/jobs/182731343#L508
Thanks.

lgtm

@heyitsanthony Would this break anything in grpcproxy? https://jenkins-etcd.prod.coreos.systems/job/etcd-proxy/262/ doesn't tell much about failures. Can you retrigger?

@heyitsanthony Ok all fixed.
I made it fail with build and test fails as it should https://travis-ci.org/coreos/etcd/jobs/182752373
I made it fail with the new script and works as expected  https://travis-ci.org/coreos/etcd/jobs/182750950

@heyitsanthony It fails if I change the script. https://travis-ci.org/coreos/etcd/jobs/182764154
Do we know why it fails in jenkins?

@gyuho The jenkins path does an out of gopath build so github.com/coreos/etcd doesn't show up in go list ./.... I don't understand why the travis job is fails without the grep-- what is the grep stripping away for travis? Anyway, the test script probably shouldn't be travis-aware, would using pwd be enough so it works for all cases?
If it can't work in both environments, I can set jenkins to ignore the fmt pass, but GOSIMPLE_UNUSED_PATHS will need to move into the fmt_pass function (which is probably a better place for it, regardless).
CI seems to be posting the regress-pr results and not the proxy CI results so it looks like it passes when it doesn't. Ugh.

So I grep by github.com/coreos/etcd to exclude the external depencies.
Then now we have
_/home/travis/gopath/src/github.com/coreos/etcd/alarm
_/home/travis/gopath/src/github.com/coreos/etcd/auth
_/home/travis/gopath/src/github.com/coreos/etcd/auth/authpb
_/home/travis/gopath/src/github.com/coreos/etcd/client
...

Next commands will just replace s/_/home/travis/gopath/src/github.com/coreos/etcd/// just to get etcd packages.

should be fixed https://travis-ci.org/coreos/etcd/jobs/182976362#L503.
removed go list command in test script.

repush to kick off jenkins?

@heyitsanthony just repushed and seems like it passes now?

lgtm. Thanks!


Support local export links with custom text

It might come in handy to be able to make links to exports with some custom text, for example:
[some link]('Module.Foo')

This would appear as some link and link to the same place that 'Module.Foo' would have.
This steps on the markdown link syntax ever so slightly in case people are using relative links with 's at the beginning and end, but that seems very unlikely.

Having this would very quite useful for the haskell-gi bindings, for linking to signals and properties properly. For example, if you look to the documentation for widgetChildNotify in gi-gtk the documentation refers to a signal 'Widget::child-notify'.
The proper link does exist in the documentation, as an anchor:
https://hackage.haskell.org/package/gi-gtk-3.0.31/docs/GI-Gtk-Objects-Widget.html#signal:childNotify
but there seems to be no way to refer to this anchor using the Haddock syntax, while at the same time showing the signal name.


dev -> master

Web app was deployed to IPFS:

Private Gateway: ipfs.kira.network/ipfs/bafybeia72dbvvdzwoxbb75dldyictzajvei2mrvzr4cch7pg3d2qiec52a
Public Gateway: ipfs.io/ipfs/bafybeia72dbvvdzwoxbb75dldyictzajvei2mrvzr4cch7pg3d2qiec52a

This PR is obsolete, dev branch is ahead of your branch.


Read React Docs

Docs

Installation

[ ] Getting Started
[ ] Add React to a Website
[ ] Create a New React App
[ ] CDN Links
[ ] Release Channels

Main Concepts

[ ] 1. Hello World
[ ] 2. Introducing JSX
[ ] 3. Rendering Elements
[ ] 4. Components and Props
[ ] 5. State and Lifecycle
[ ] 6. Handling Events
[ ] 7. Conditional Rendering
[ ] 8. Lists and Keys
[ ] 9. Forms
[ ] 10. Lifting State Up
[ ] 11. Composition vs Inheritance
[ ] 12. Thinking In React

Advanced Guides

[ ] Accessibility
[ ] Code-Splitting
[ ] Context
[ ] Error Boundaries
[ ] Forwarding Refs
[ ] Fragments
[ ] Higher-Order Components
[ ] Integrating with Other Libraries
[ ] JSX In Depth
[ ] Optimizing Performance
[ ] Portals
[ ] Profiler
[ ] React Without ES6
[ ] React Without JSX
[ ] Reconciliation
[ ] Refs and the DOM
[ ] Render Props
[ ] Static Type Checking
[ ] Strict Mode
[ ] Typechecking With PropTypes
[ ] Uncontrolled Components
[ ] Web Components

API Reference

[ ] React
[ ] React.Component
[ ] ReactDOM
[ ] ReactDOMServer
[ ] DOM Elements
[ ] SyntheticEvent
[ ] Test Utilities
[ ] Test Renderer
[ ] JS Environment Requirements
[ ] Glossary

Hooks

[ ] 1. Introducing Hooks
[ ] 2. Hooks at a Glance
[ ] 3. Using the State Hook
[ ] 4. Using the Effect Hook
[ ] 5. Rules of Hooks
[ ] 6. Building Your Own Hooks
[ ] 7. Hooks API Reference
[ ] 8. Hooks FAQ

Testing

[ ] Testing Overview
[ ] Testing Recipes
[ ] Testing Environments

Contributing

[ ] How to Contribute
[ ] Codebase Overview
[ ] Implementation Notes
[ ] Design Principles

FAQ

[ ] AJAX and APIs
[ ] Babel, JSX, and Build Steps
[ ] Passing Functions to Components
[ ] Component State
[ ] Styling and CSS
[ ] File Structure
[ ] Versioning Policy
[ ] Virtual DOM and Internals

Extras

How I built this list
from bs4 import BeautifulSoup
from requests import get

BASE_URL = "https://reactjs.org"

response = get(f"{BASE_URL}/docs/getting-started.html")
soup = BeautifulSoup(response.text, "html.parser")

block = soup.find("div", class_="css-1sdm35g")

for category in block.find_all("button"):
    print(
        f"""\n
  {category.text}
  """
    )
    for point in category.parent("a"):
        print(f"- [ ] [{point.text}]({BASE_URL}{point['href']})")

    print("")

I know 😆

Done!


[ADR] docs: add live-regions adr

Live Regions
tl;dr this ADR will enable us in Primer React to conditionally render components that accurately announce to live regions 🥳 For example
function ExampleComponent() {
  const [loading, setLoading] = React.useState(true);
  if (loading) {
    return <Status>Loading</Status>
  }
  return <Content />
}

For more information about this ADR, check out the rendered view for the ADR.
Feedback
Would love to get your feedback on this approach and if it makes sense to try out more broadly in Primer React and GitHub 👀 This is definitely still experimental but it's been promising so far and we'd love to make use of it when building in Primer React and in GitHub directly.
Some broad questions to get things going:

What do you think of the usage of the custom element here? Does it make sense as a common interop point for Primer and GitHub?
Are there any alternatives that should be explored for accessible live region announcements?
What do you think of Status and Alert? Are the semantics for these components clear along with how to use them?

cc @primer/engineer-reviewers if you have a sec to check this out! Curious to hear what you all think about this approach 👀


Apply Patterns, if necessary, when rendering text

Currently we're not applying Patterns for text, but only for graphics.
This patch is unfortunately not a complete solution, but rather a step on the way, since there are still some PDF files where the Patterns look more like a solid colour, rather than the intended gradient.
I've been unable to fix these issues completely, and I've not managed to determine if the remaining issues are caused either by the pattern code, the canvas code, or perhaps both.
However, given that even this simple patch improves the current situation quite a bit, I figured that it couldn't hurt to submit it as-is.

Fixes #5804.
Fixes #6130.
Improves #3988 a lot, since the text is now visible. However, it looks like the text is one solid colour, instead of the correct gradient.
Improves #5432, since the text is no longer gray. (This file also suffers from the same problem as the previous one.)

/botio-linux preview

/botio test

I suspect that the two files that are not completely fixed by this PR have a solid color because they use a horizontal gradient instead of a vertical gradient in the two fixed files. You might need to specify the direction of the gradient somehow, but that can also be done for a follow-up, I justed wanted to mention my observation.

suspect that the two files that are not completely fixed by this PR have a solid color because they use a horizontal gradient instead of a vertical gradient in the two fixed files.

I'd actually be surprised if it's that simple, since there appears to be issues at play as well.
Look at the PDF files in https://github.com/mozilla/pdf.js/issues/6234#issuecomment-126369593; note that the latter one is included as a test-case in this patch.
Note that in the first one the gradient isn't clipped correctly (the text is continuing off the page), and in the second one the gradient doesn't have the right "turquoise" colour at the end of the text (it's as if only part of the gradient is being used), when compared to Adobe Reader.

/botio-linux preview

/botio test

/botio-linux preview

/botio test

/botio test

IRC log:
<timvandermeij> According to the logs it might be the one after ecma262-pdf, which is https://github.com/mozilla/pdf.js/blob/master/test/test_manifest.json#L379. This did not happen before, so I wonder if an update broke things (I see we're at Firefox 45 on the bots now).

Checking it is the same test
/botio-linux test

/botio test

I tried out issue6286.pdf through x11 and it seems to load fine. It does take awhile, but I think that's just x11 being slow.

/botio test

/botio-linux test

/botio test

/botio makeref

Thank you!


Add option to set invert filter value (e.g. for fully black dark theme)

Motivation
When using an OLED display, I prefer fully black colors (i.e. #000000) when using dark mode. With such an
Description
Currently the invert filter for the preview uses a value of .933333 (see also here). This results in slightly grayish output for originally white pages.
Being able to customize this value could enable users to adjust the background color to fit their theme.
The option could be named e.g. tinymist.preview.invertFilterLevel.
See also maybe LaTeX-Workshop's latex-workshop.view.pdf.invert, which already has this option for their webview.

It is okay to define values for CSS style in configuration but I feel it would expose too much detail in configuration; and it would be easily broken and not upgradable.
We may add enumerated keys to select few builtin themes instead. Each theme will contain HTML and CSS code for customization. In far future, people might be also able to create their owned extension to customize appearance of the viewer with the theme configuration feature.
Specific to this issue, the only two sensible values of the filter might be:

the current default value, 0.933, to protect eyes.
the completely invert value, 1, for better experience on some special display devices.

That would be great!


Add alt_complete! convenience combinator

Follow-up to #132.

@Geal: Friendly ping about this. :smile:

Nice :)
Just a nitpick, could you use _ to match $crate::IResult::Incomplete(_) | $crate::IResult::Error(_) ? This will make the code a little bit easier to read.

@Geal: Oh, nice catch; fixed!

Thanks!


Fix TestRunCreateVolumesInSymlinkDir

Signed-off-by: John Howard<EMAIL_ADDRESS>@cpuguy83 @calavera @mikedougherty
This test is wrong :) Looks like it might have been modified in the past, but modified incorrectly. It used to create a directory on the host, then a file in it, then all it does is create the same directory name in the container, and ignores the file created on the host. In fact, it ignores the directory on the host too. So why even create it? Instead, just used a hard-coded directory inside the container (based on the test name) to use as the base of the symbolic link to (c:)\test, which is what is really being tested here.
This is a problem on Windows CI, or at least will be as soon as we switch to a fast SSD on the D: drive, as the D: drive doesn't exist inside the container. Hence needs to be merged before I can switch the CI servers to dramatically improve the performance of the windowsTP4 runs.

:+1:

Previous changes look to be made in https://github.com/Microsoft/docker/commit/63708dca8a633d68f9342eebd4f7a616e8c48234

Way before that change ;)

Ok, this check is for an old bug where if there existed a path on the host that was the same path as a volume path (e.g. /test on the host and /test in a container), and the container path was a symlink it was causing issues.

@cpuguy83 So would you rather me put it back to how it was, and just don't run it on Windows to Windows CI? I think the updated version of the test still has merit as a test in its own right though.

We should not change the purpose of the test, which is to ensure there's no issues as described above.

@cpuguy83 OK, put test back in with a safety check to skip when running on Windows if the TEMP directory is not on the C: drive. And what was the modification is added as a new test. PTAL

LGTM

LGTM


Added the flatten plugin configuration

Done via https://github.com/spring-cloud/spring-cloud-release/commit/bc87c2129a8e6e69f24f54686063ea39cc688608


Better visualization strategies for large-scale knowledge graphs

Currently, the visualization strategies shown in the demo are only applicable to very small knowledge graphs and can be used to display the results of different conversion strategies (in the paper), for example. It is not applicable for presenting the complete knowledge graph after finalizing the conversion of the whole report. Therefore, there is a need to introduce visualization strategies that are applicable to large knowledge graphs. This can be referred to as Neo4j's solution to visualize the knowledge graph in layers. This is theoretically applicable to our case, as both the report and the SKOS ontology we currently employ have a clear hierarchy. Here are some existing tools:

[ ] ViziQuer
[x] VocView

Instance using VocView is online.


CORE-18282: Fix Flaky Tests

Sort the returned states before building the filters to use so that the
lower bound is always older in time than the upper bound.

I've executed the test 283 times in a row with the changes, no failures whatsoever.


Installation on Ubuntu 20.04.6 LTS `GLIBC_2.33' not found

Hello there,
Thanks a lot for this wonderful piece of software!
I managed to install gpud on Ubuntu 24.04, however, while installing on 20.04.6 I'm getting the following error:
./gpud: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./gpud)
./gpud: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./gpud)
./gpud: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./gpud)

My GLIBC version:
ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9.16) 2.31

Unfortunately, it's a pre-configured image, so I can't upgrade ubuntu.
Is there a way to get it working except complying gpud myself for my version of glibc?
Thanks a lot in advance and thanks for open sourcing it!

@eicca Thanks for the report!
Could you try the Ubuntu 20.04 build binary from this release page? https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha5

Also

I managed to install gpud on Ubuntu 24.04

So, it worked on ubuntu 24.04, but the same binary did not work on 22.04? And which version/binary you used will be helpful :)

@eicca Thanks for the report!
Could you try the Ubuntu 20.04 build binary from this release page? https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha5

Thanks a lot for your reply! Downloading the binary for 20.04 directly worked!
For some reason the installer downloaded the binary for 22.04 :shrug:

@eicca Do you also need Ubuntu 24.04 binary? Or does the binary for either 20.04 or 22.04 work on your 24.04?

The binary for 22.04 worked on my 24.04 without problems :ok:
Thanks a lot for looking into this!

Also

I managed to install gpud on Ubuntu 24.04

So, it worked on ubuntu 24.04, but the same binary did not work on 22.04? And which version/binary you used will be helpful :)

Is that the only way to install gpud on ubuntu 20?

@seanxuu Our latest release has Ubuntu 20.04 builds: https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha6
Could you try?

@seanxuu Our latest release has Ubuntu 20.04 builds: https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha6
Could you try?

I just tryied the v0.0.1-alpha6](https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha6). It worked on Ubuntu 20.04. But the install script in the README.MD does not work on Ubuntu 20.04, and will output `GLIBC_2.33' not found

@Coldmooon Thanks for the report. Yes, we are making the fix the point our install script endpoint to the one that supports Ubuntu 20.04. Will keep you updated.

@Coldmooon @seanxuu Please try again with the install script (our official one also updated).
And https://github.com/leptonai/gpud/releases/tag/v0.0.1-alpha7 has been released.


News items have human readable links. Admin UI for posting news.

For https://github.com/pygame/pygameweb/issues/61

Coverage decreased (-0.3%) to 83.111% when pulling 286eb88ea7682872f89059543a5ee80802724a29 on news-improvements into c1fc54e979b17ab8da512bbc5e0d83656ae0c57c on master.


[CI] Enable HF model caching

Issue #, if available:
Description of changes:

Have setup an AWS Batch job running chronically to sync up our models stored in S3 with HF. An EFS was used as a cache so we don't re-download the model each time.

List of models will be fetched dynamically from our repo with hf_model_list.yaml
All models in the list will be downloaded and synced to our S3, no matter which subfolder it belongs to

CI job will use setup_hf_model_mirror.py to download the corresponding models to ~/.cache/huggingface/hub for the specific subfolder to test.
Updated the structure of the model list.
A follow-up PR to enforce model list updating will be sent

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM. Do we also need to automatically sync our s3 with the hf model hub?

Yes, we are doing that on a nightly basis


Part 2 - Chapter 7

This chapter is on hold for now.

Chapter has been written.

Chapter has been written.


Update the install generator to add Webpacker configuration, Add ReScript component and Fix Issue #1397

This PR contains:
Generator update
Updated the generator to add Webpack configuration on rails generate react_on_rails:install

Add React, Typescript, and CSS modules dependencies to the generator
Add Babel config and webpacker.yml to the
Add Webpack config files

ReScript Example

Add ReScript example component to the spec/dummy/
Boilerplate code provided by ljuster at shakacode/react_on_rails#1215

Display error when SSR config is missing

Fix issue #1397

This change is

Display error when SSR config is missing
Fix issue If config.server_bundle_js_file is blank, nil, commented out, and prerendering is done, page request hangs #1397

Please make separate PR.

Any feedback on https://github.com/shakacode/react_on_rails/blob/master/CONTRIBUTING.md ?

/spec/dummy webpack config should roughly match the generator which should roughly match https://github.com/shakacode/react_on_rails_tutorial_with_ssr_and_hmr_fast_refresh

CI needs to pass
Document steps from clean git clone:
use the generator to build a rescript app
run app in spec/dummy showing rescript component
run test for new rescript component.
Update the basic tutorial given the updated generator https://github.com/shakacode/react_on_rails/blob/master/docs/guides/tutorial.md

Created Separated PR for

Display error when SSR config is missing => #1401
Add Rescript example => #1400


primary_author.profile_image returns unsecure url

Starting with 2.0, the primary_author.profile_image returns an unsecure URL on a secure site, resulting in mixed-content warnings. This was working in 1.x.

@Leandros further information would be useful to help pin this down as this hasn't been observable on any other sites so far.

what is the url in your config.production.json file, does it start with https://?
is it all profile images or only some of them?
what's stored in the DB for the profile image in question?
are you using any storage adapter?

The url in config.production.json is https://arvid.io
It's a profile image which still exists from an upgrade
The absolute url, including the http is stored in the database.
I'm not using any storage adapter.

I gave it a try to simply reupload the images, which does indeed update the urls to a https:// prefix, and therefore fixes the issue.
Even though I could fix it, I'd still consider it a bug (or design flaw) to save an absolute URL in the database.

I've tested and I'm only seeing relative URLs stored in the database. I think this may have something to do with a recent change to return absolute URLs via the API - /cc @kirrg001

@Leandros can you confirm you're seeing absolute URLs in the database itself rather than what's returned in the theme or via the API?

@Leandros
Which version of Ghost 2.x are you on?
Do you still have the 1.0 backup JSON? If yes, could you please share the target post from your JSON backup file?

@kevinansfield
$ mysql -u root -p
> use ghost;
> select profile_image from users;
+------------------------------------------------------------+
| profile_image                                              |
+------------------------------------------------------------+
| https://arvid.io/content/images/2018/10/profile_blog-1.jpg |
+------------------------------------------------------------+
1 row in set (0.00 sec)

@kirrg001 I'm on latest (v2.2.3). Unfortunately, I only backed up the ghost folder, not the database or exported a json backup.

For some reason, my authors are also duplicated after the 2.0 upgrade.

And I also just noticed that the posts are duplicated when scrolling through the post list.

@Leandros And where exactly do you get mixed content?

There is definitely a bug introduced by API v2.

Ghost stores images without domain
API V2 returns e.g. users with absolute urls
Ghost-Admin sends absolute urls back on any save e.g. update user
This will override the relative image path to absolute

And I also just noticed that the posts are duplicated when scrolling through the post list, it starts at the beginning again once I reach the end.

That sounds like a different issue. Can you please either report it in our forum and ask for help or raise a new bug issue if you think it's a bug (Please put steps to reproduce and as much as possible information!).

Ghost-Admin sends absolute urls back on any save e.g. update user
Hmm, that's an interesting one. We probably have a few places where that will be the case 🤔 I'm not sure there's too much we can do about it on the client-side, maybe there's some checks we can do server-side to strip the base URL from image fields if it matches the configured URL?

not sure there's too much we can do about it on the client-side, maybe there's some checks we can do server-side to strip the base URL from image fields if it matches the configured URL?

This needs protection on the server side 👍

I am not really sure how big the outcome of this bug is 🤔I guess it's only a problem if you change your domain or your protocol. Not sure it's super critical, but we should look into the fix and a migration file asap.
I need steps to reproduce to get the mixed content issue, because obviously the profile image is stored correctly with https.

@kirrg001 I got the mixed content in places where my profile picture was displayed, for example on a post.
I'm guessing you could reproduce it by creating an instance on HTTP, uploading a profile picture (which will write the absolute URL to the database), and than changing to HTTPS.


:bug: fix: Plugin hangs at random during generation of 1000+ change log files

Hi!
First, thank you for a GRRRRRRREAT plugin 🚀
Does exactly what we need as part of our release strategy.
We have a monorepo with 1000+ modules and we generate change log files for every module. At random times, the plugin will just hang during change log generation (see below) and never come back to life. Most times it works as it should.

We tried changing our command to:
npx nx run workspace:version --skipProjectChangelog=true
...and that works well.
We don't really need change log files in every module so we are ok with the alternate command.
Just noting this down as an inconvenience.
🍺

Hi @bjornharvold, thanks for the feedback.
Well, I can also notice that the logs look terrible in sync mode. :smile: Regarding the problem you described, we are running the changelog in parallel and we delegate the generation to standard-version, maybe there's a memory leak somewhere.
I think we can find something using the node profiler, your environment (1000+ modules) is pretty large, so it's not easy for me to replicate, if you have time and you are up to, could you run the profiler in your project and give me the outputs?
You can run it this way:
node --prof<EMAIL_ADDRESS>run demo:version

Hi @edbzn
Yes I can. The problem is this issue is random so I don't know if I will be able to get to it. Many times, introducing a profiler, also changes how the program is run and the error doesn't come to light.
Will see what I find and report back.

Hi @edbzn
Not able to replicate with the profiler. Changed my script to call:
npx nx run workspace:version --skipProjectChangelog=true
Will leave it at that.
Thank you 🍺


The  KeysetId of v1 api parse failed, it's not hex string

curl -X GET https://8333.space:3338/v1/keys
{"keysets":[{"id":"I2yN+iRYfkzT","unit":"sat","keys":{"1":"03ba786a2c0745f8c30e490288acd7a72dd53d65afd292ddefa326a4a3fa14c566","2":"03361cd8bd1329fea797a6add1cf1990ffcf2270ceb9fc81eeee0e8e9c1bd0cdf5","4":"036e37..

It's version is Nutshell/0.15.2
curl -X GET https://8333.space:3338/v1/info
{"name":"Cashu test mint","pubkey":"03e3d23e1b66eadaf15ce0d640a908e8ba1984baed34ab98c547aab4cf4249440d","version":"Nutshell/0.15.2","description":"This mint is for testing and development purposes only. Do not use this mint as a default mint in your application! Please use it with caution and only with very small amounts. Your Cashu client could have bugs. Accidents and bugs can lead to loss of funds for which we are not responsible for.","contact":[["",""]],"nuts":{"4":{"methods":[{"method":"bolt11","unit":"sat","min_amount":0,"max_amount":500000}],"disabled":false},"5":{"methods":[{"method":"bolt11","unit":"sat","min_amount":0,"max_amount":500000}],"disabled":false},"7":{"supported":true},"8":{"supported":true},"9":{"supported":true},"10":{"supported":true},"11":{"supported":true},"12":{"supported":true}}}

This is isn't a V1 keyset id so it should fail. Nutshell shouldn't be returning the old keyset ids on the v1 endpoint.
To get around this until its fixed I handle it by ignoring non V1 keysets in the /keysets request and then the specific keys can be requested via the /keys/{keyset_id} endpoint. But would like to take this out as well.
https://github.com/thesimplekid/cashu-crab/blob/664776f1224840c2f7ab944348e6bf534ff993f2/crates/cdk/src/nuts/nut02.rs#L174-L176
I opened an issue in nutshell https://github.com/cashubtc/nutshell/issues/512

Since nutshell does not plan to fix this I updated to now ignore pre v1 keysets ids in the response but not error.


Unique state names for stateful RNN layers

Fixes #17477
It generates {layer_name}/state for GRU and SimpleRNN layers, and {layer_name}/state_{idx} for LSTM layers.

I added the _gen_state_names to the base RNN class.

Hello, Thank you for submitting a pull request.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, merging this PR is not possible at the moment. After the migration is successfully completed, feel free to reopen this PR at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this PR fixes a bug or security issue in legacy tf.keras, you can instead reopen the PR at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.


Islam/dx 411 clarify next axiom setup choices

@bahlo maybe we can merge this until we find a way to improve it?

this has been handled in a different PR. closing.


Data packed with wrong version of caniuse-db

It seems that the generated files in the ./data folder that are published to npm are generated with the wrong version of caniuse-db. If I manually run the npm run pack script the generated files do match the correct version of caniuse-db.
I included a zip with the different ./data/agents.js file as an example:

one file is the current file on master (version 1.0.30001023 / commit ab8f1ec1681d614ed7696437d70762557b526dcb)
one file is packed with caniuse-db 1.0.30001021
one file is packed with caniuse-db 1.0.30001023
agents.zip

As you can see the file for version 1.0.30001023 matches caniuse-db 1.0.30001021 instead. Probably there is a problem with your automated builds.
I noticed this because browserslist does not return edge version 79 in it's query results for this version :)

Hi ai, it seems that the auto start is not running, as caniuse-db has been updated and caniuse-lite does not seem to auto update. If I can help with anything please ask me.

Seems like recentl changes killed auto-update 😔
I will try to connect to auto-release server to find a reason. But it could take few days.

Here is a log. Right now I have no idea what happened. We didn’t change anything related to Babel.
The current auto-release system is too unstable :(

Just npx babel-node just work. Seems like spawn doesn’t see env variables.
Do you have any idea?

It is locally reproducible at my side, trying to fix it now

ai, I opened a PR which resolves the issue. Starting the babel-node command using npx seems to fix it.

Thanks. Now it works.


add note about needing istio first

I think the logical order should be: "the following section assumes the user
has openshift installed" (the section below this) and only then
"assumes the user has istio installed" and not vise versa.

@abonas see the latest for review - the order of the docs should reflect your recommendation.

jay approved, and I believe I incorporated @abonas  suggestion. so this can be merged.


Getting 403 errors even with rotating residential proxies

I have tried rotating proxies from BrightData and SmartProxy and I still get the 403 error, like the code isnt even trying to use it. I have replaced the appropriate fields in proxy_url =

its working good to me, send me an email or a conection request to make a call to guide you how to use the tool


release versioning

Hey!
Congratulations in advance on the project.
I'm a Debian maintainer and I decided to keep your project in our Distro.
I noticed that you sometimes name your releases 2.15 and the most current ones 2.0.16.
To keep your project always updated in our repositories, a standard must be followed.
Because the tracking system says 2.15 is greater than 2.0.16.
The debian tracking system, monitor this url here:
https://github.com/m32/endesive/tags
I believe that if you change the latest release to v.2.16, it will resolve:
because today it is like this:
https://github.com/m32/endesive/releases/tag/v2.0.16
Would it be possible to standardize?

Thanks for noticing endesive, I'm glad to hear that this project was chosen for distribution.
It was an accident with the version, it should be in x.y.z format, but since it is now 2.16, let it stay that way - version released.


Fix #332

As discussed in issue #332, this should resolve any problems with Bootstrap 3.3+

The issue was fixed in Bootstrap 3.3.2


Update hw00.m

Do not send a pull request. Submit your repo’s link to canvas. You can find the programming part in the assignments on canvas.
Best,
Yimin
On Sep 5, 2024, at 3:28 PM, hstraub55 @.***> wrote:

CAUTION: Email Originated Outside of Auburn.

You can view, comment on, or merge this pull request online at:
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2
Commit Summary

98e479bhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/commits/98e479bda377c6cdf9eae9e9d92886900836bb44 Update hw00.m

File Changes
(1 filehttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files)

M hw00.mhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files#diff-1a71dab692e16ecf16e4deb75677cb76022e103c2236034717c0c66e89a5f700 (73)

Patch Links:

https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.patch
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHBBM5U64LGJKAWYMBJ5XOTZVC5HLAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYDQNRVGQZTKOA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Dr. Zhong,
Apologies, I clicked the wrong button and did not know how to undo it. Will the zip file that I submitted for the programming on canvas suffice?
Very respectfully,
Hunter Straub

From: YIMIN ZHONG @.>
Sent: Thursday, September 5, 2024 4:51 PM
To: auburn-comp-math/math-5630-6630.homework.0 @.>
Cc: Hunter Straub @.>; Author @.>
Subject: [EXT] Re: [auburn-comp-math/math-5630-6630.homework.0] Update hw00.m (PR #2)
CAUTION: Email Originated Outside of Auburn.
Do not send a pull request. Submit your repo’s link to canvas. You can find the programming part in the assignments on canvas.
Best,
Yimin
On Sep 5, 2024, at 3:28 PM, hstraub55 @.***> wrote:

CAUTION: Email Originated Outside of Auburn.

You can view, comment on, or merge this pull request online at:
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2
Commit Summary

98e479bhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/commits/98e479bda377c6cdf9eae9e9d92886900836bb44 Update hw00.m

File Changes
(1 filehttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files)

M hw00.mhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files#diff-1a71dab692e16ecf16e4deb75677cb76022e103c2236034717c0c66e89a5f700 (73)

Patch Links:

https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.patch
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHBBM5U64LGJKAWYMBJ5XOTZVC5HLAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYDQNRVGQZTKOA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2#issuecomment-2332686582, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKVFAUUWP5U2U6SUR7KKPCTZVDG6JAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGY4DMNJYGI.
You are receiving this because you authored the thread.Message ID: @.***>

Looks good.
Best,
Yimin

From: hstraub55 @.>
Sent: Thursday, September 5, 2024 5:00 PM
To: auburn-comp-math/math-5630-6630.homework.0 @.>
Cc: Yimin Zhong @.>; Comment @.>
Subject: [EXT] Re: [auburn-comp-math/math-5630-6630.homework.0] Update hw00.m (PR #2)
CAUTION: Email Originated Outside of Auburn.
Dr. Zhong,
Apologies, I clicked the wrong button and did not know how to undo it. Will the zip file that I submitted for the programming on canvas suffice?
Very respectfully,
Hunter Straub

From: YIMIN ZHONG @.>
Sent: Thursday, September 5, 2024 4:51 PM
To: auburn-comp-math/math-5630-6630.homework.0 @.>
Cc: Hunter Straub @.>; Author @.>
Subject: [EXT] Re: [auburn-comp-math/math-5630-6630.homework.0] Update hw00.m (PR #2)
CAUTION: Email Originated Outside of Auburn.
Do not send a pull request. Submit your repo’s link to canvas. You can find the programming part in the assignments on canvas.
Best,
Yimin
On Sep 5, 2024, at 3:28 PM, hstraub55 @.***> wrote:

CAUTION: Email Originated Outside of Auburn.

You can view, comment on, or merge this pull request online at:
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2
Commit Summary

98e479bhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/commits/98e479bda377c6cdf9eae9e9d92886900836bb44 Update hw00.m

File Changes
(1 filehttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files)

M hw00.mhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2/files#diff-1a71dab692e16ecf16e4deb75677cb76022e103c2236034717c0c66e89a5f700 (73)

Patch Links:

https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.patch
https://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHBBM5U64LGJKAWYMBJ5XOTZVC5HLAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYDQNRVGQZTKOA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2#issuecomment-2332686582, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKVFAUUWP5U2U6SUR7KKPCTZVDG6JAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGY4DMNJYGI.
You are receiving this because you authored the thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/auburn-comp-math/math-5630-6630.homework.0/pull/2#issuecomment-2332696596, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHBBM5VEHZVIEDBWTQ7AIZTZVDH7LAVCNFSM6AAAAABNXH4FOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGY4TMNJZGY.
You are receiving this because you commented.Message ID: @.***>


Fix logson typo in src/delivery/errors/mod.rs

This changes logson to logs on in src/delivery/errors/mod.rs

Fixed upstream.


pod recreate needs to remove resourceVersion etc

resourceVersion should not be set on objects to be created}

#11


Seek bug

When seek starts i always get stuck on the roof and get killed

amazing bug report this is totally reproducable


Code release

Thanks for sharing this great work! I was wondering if there is an expected date on when you will be releasing your code and pretrained models for LayoutLM.

The code and models are available at https://github.com/microsoft/unilm/tree/master/layoutlm. Please  have a try.


[Bug]: Load operator: [dummy_input] failed

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
img_embedding_pipe = (
    towhee.dummy_input()
          .pipeline_config(format_priority=['tensorrt', 'onnx']) \
          .config(jit='numba', parallel=multiprocessing.cpu_count()) \
          .image_decode['url', 'img']() \
          .image_embedding.isc['img', 'isc_embedding']() \
          .image_text_embedding.clip['img', 'clip_vit_b32_embedding'](model_name='clip_vit_b32', modality='image') \
          .image_captioning.blip['img', 'captioning_text'](model_name='blip_base') \
          .drop_empty() \
          .as_function()
)

towhee.build_docker_image(img_embedding_pipe, image_name='image_embedding/v1', cuda='11.4')

Step 12/12 : RUN triton_builder /workspace/dag.json /workspace/models
 ---> Running in 1f39246d3716
2022-10-09 18:20:34,792 -<PHONE_NUMBER>64672 - builder.py-builder:166 - ERROR: Load operator: [dummy_input] failed, errs not enough values to unpack (expected 2, got 1), Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/towhee/serve/triton/builder.py", line 158, in _load_op
    hub_id, name = op_name.split('/')
ValueError: not enough values to unpack (expected 2, got 1)

2022-10-09 18:20:34,792 -<PHONE_NUMBER>64672 - builder.py-builder:135 - ERROR: Load operator: [dummy_input] by init args: [None] failed
2022-10-09 18:20:34,793 -<PHONE_NUMBER>64672 - builder.py-builder:181 - ERROR: Create node config failed

Expected Behavior
build succeed
Steps To Reproduce
No response
Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

@shiyu22
could you help to have a look? Thanks.

Hi @pengdaqian2020, it's an error pipeline, you can run with img_embedding_pipe() to check the function.
And there this is the correct pipeline:
img_embedding_pipe = (
    towhee.dummy_input['url']()
          .pipeline_config(format_priority=['tensorrt', 'onnx']) \
          # .config(jit='numba', parallel=multiprocessing.cpu_count()) \
          .image_decode['url', 'img']() \
          .image_embedding.isc['img', 'isc_embedding']() \
          .image_text_embedding.clip['img', 'clip_vit_b32_embedding'](model_name='clip_vit_b32', modality='image') \
          .image_captioning.blip['img', 'captioning_text'](model_name='blip_base') \
          # .drop_empty() \
          .as_function()
)

Then you can run with img_embedding_pipe('https://github.com/towhee-io/towhee/raw/main/towhee_logo.png').
Not that drop_empty() works when running safe(), the numba jit is for the callable functions and the multiprocessing.cpu_count() is too large so I have commented on them. Another thing is that there are several operators that support speedup with triton in towhee, and the operators in your pipeline don't support like tensorrt and onnx, so the performance may not be better.


Adds ignore_exceptions and ignore_transactions options to Configurator

fixes: #710

In order to move this forward, you'll have to update all tests concerning the newly added options.

Has someone fixed an Error while testing on End2EndTest-php:
PHP:  syntax error, unexpected '=' in Unknown on line 24

Tests added.


Convert fractional widths between 0 and 1 to percentages

I’m a big fan of rebass’s fractional width feature.
// wired
<Block width={3 / 5} />

// tired
<Block width={3 / 5 * 100 + '%'} />

Pros:

Component code is a lot easier to read.
It’s easier to integrate constants.

Cons:

it’s slightly magical.

That seems like a good idea.


selector: support for additional configuration

This PR adds support for the following configuration properties (evictionInterval, and cleanupTickPeriod) :
# token selector configuration allows to use different implementations of the token selector
  # the "sherdlock" driver is the default implementation, other possible configurations are: "simple"
  # if empty, the default selector is used
  selector:
    driver: sherdlock
    # tokens might be locked because of an ongoing transaction from the same wallet. Instead of failing immediately, the selector can retry.
    # The interval is the exact amount of seconds (for simple selector) or the max amount of seconds (sherdlock) the selector waits before retrying.
    # default: 5s
    retryInterval: 5s
    # retry to gain a lock on tokens this amount of times before failing the transaction
    numRetries: 3
    # evictionInterval is the period a token can be locked, after which it is forcefully unlocked
    # if evictionInterval is zero, the eviction algorithm is never executed
    evictionInterval: 3m
    # cleanupTickPeriod defines how often the eviction algorithm must be executed
    # if cleanupTickPeriod is zero, the eviction algorithm is never executed
    cleanupTickPeriod: 1m

@arner , please, have a look at the changes. Thanks :)


with code splitting, no new manifest is generated with new chunks versions

I am using webpack code splitting with require.ensure to get a separate chunk per route, recently after upgrade to latest laravel-mix version 0.6, it doesn't generate a new manifest file with the new generated chunk version.

//webpack.mix.js
let mix = require('laravel-mix');

/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for your application, as well as bundling up your JS files.
 |
 */
mix.js('resources/assets/js/app.js', 'public/js')
    .js('resources/assets/js/login.js', 'public/js')
    .js('resources/assets/js/password.js', 'public/js')
    .extract([
        'jquery',
        'bootstrap-sass',
        'retinajs',
        'vue',
        'webui-popover',
        'moment',
        'toastr',
        'quill',
        'lodash'
    ])
    .sass('resources/assets/sass/app.scss', 'public/css')
    .version();

Pretty sure this was fixed with a later release. Upgrade your install of Laravel Mix.
If there still is a problem, please give me reproducible steps from scratch for a fresh Laravel app.


ElevationRequirement not working on Portable App

Brief description of your issue
The "ElevationRequirement" option seems to be ignored in portable apps.
Steps to reproduce

Create a portable manifest (version 1.5.0)
Add "ElevationRequirement" to "elevationRequired" or "elevatesSelf"
Open an unelevated console window and install the app

Expected behavior

If "ElevationRequirement" is set to "elevationRequired" I expected a message the an elevated window is necessary
If "ElevationRequirement" is set to "elevatesSelf " I expected elevation request

Actual behavior

No message occur
The app will be installed. It seems that "ElevationRequirement" is completly ignored

Environment
Windows-Paket-Manager v1.6.2771
Windows: Windows.Desktop v10.0.19045.3448
Paket: Microsoft.DesktopAppInstaller v1.21.2771.0

I've been talking with several folks about this issue. It seems the current consensus is that we should change validation to not allow the elevation requirement for portable packages.
If the tool needs to be run elevated, the installationNotes should be added to the manifest to inform users when they perform an install that the tool should be run as an administrator.


Rework and simplify format service

Simplify things around formatting, add a proper format on save, should test properly before closing format on save issues.
The format on save is mostly a workaround, proper fixes are dependant on https://github.com/Microsoft/vscode/issues/239.

Yeah, I see, just like vscode-go did it. I have nothing against it as we have no alternative for now.
Anyway, awesome job and thank you.


[connectivity-tests] - Throws segmentation violation -> "invalid memory address or nil pointer dereference"

Is there an existing issue for this?

[x] I have searched the existing issues

Version
equal or higher than v1.16.3 and lower than v1.17.0
What happened?
Running the cilium connectivity test  traceback with invalid memory address:
$ cilium connectivty test -n cilium-system
[....]
[=] [cilium-test-1] Test [client-egress-to-cidrgroup-deny] [50/105]
......
[=] [cilium-test-1] Test [client-egress-to-cidr-deny-default] [51/105]
......
[=] [cilium-test-1] Skipping test [clustermesh-endpointslice-sync] [52/105] (skipped by condition)
[=] [cilium-test-1] Test [health] [53/105]
....
[=] [cilium-test-1] Skipping test [north-south-loadbalancing] [54/105] (Feature node-without-cilium is disabled)
[=] [cilium-test-1] Test [pod-to-pod-encryption] [55/105]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x3b8 pc=0x3039042]

goroutine 39573 [running]:
github.com/cilium/cilium/cilium-cli/connectivity/check.Pod.Address({0x0, 0x0, {0x0, 0x0}, {0x0, 0x0}, 0x0, 0x0}, 0x1)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/check/peer.go:107 +0x62
github.com/cilium/cilium/cilium-cli/connectivity/tests.getInterNodeIface({0x55f1af0, 0xc0000df940}, 0xc0007f6c60, 0xc002a0a2c0, 0xc002a0a340, 0xc002a0a280, 0xc002a0a300, 0x1, 0x0)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/tests/encryption.go:54 +0x308
github.com/cilium/cilium/cilium-cli/connectivity/tests.testNoTrafficLeak({0x55f1af0, 0xc0000df940}, 0xc0007f6c60, {0x55cd218, 0xc000fbb6e0}, 0xc002a0a280, 0xc002a0a2c0, 0xc002a0a300, 0xc002a0a340, 0x0, ...)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/tests/encryption.go:303 +0x2bb
github.com/cilium/cilium/cilium-cli/connectivity/tests.(*podToPodEncryption).Run.func1(0x1)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/tests/encryption.go:279 +0x1a6
github.com/cilium/cilium/cilium-cli/connectivity/check.(*Test).ForEachIPFamily(0xc0007f6c60, 0xc002dcdc40)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/check/test.go:840 +0xd8
github.com/cilium/cilium/cilium-cli/connectivity/tests.(*podToPodEncryption).Run(0xc000fbb6e0, {0x55f1af0, 0xc0000df940}, 0xc0007f6c60)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/tests/encryption.go:274 +0x5fa
github.com/cilium/cilium/cilium-cli/connectivity/check.(*Test).Run(0xc0007f6c60, {0x55f1af0, 0xc0000df940}, 0x37)
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/check/test.go:375 +0x664
github.com/cilium/cilium/cilium-cli/connectivity/check.(*ConnectivityTest).Run.func1()
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/check/context.go:411 +0x99
created by github.com/cilium/cilium/cilium-cli/connectivity/check.(*ConnectivityTest).Run in goroutine 894
	/go/src/github.com/cilium/cilium-cli/vendor/github.com/cilium/cilium/cilium-cli/connectivity/check/context.go:405 +0x91

 ....

Implementation details:

Wireguard encryption enabled
Wireguard node-to-node encryption enabled
KubeProxy replacement

How can we reproduce the issue?

Deploy an EKS cluster without any CNI;
Deploy Cilium with the following options:

bpf:
  hostLegacyRouting: false
  masquerade: true

clustermesh:
  replicas: 1
  useAPIServer: false
  apiserver:
    service:
      annotations:
        service.beta.kubernetes.io/aws-load-balancer-internal: "true"
      type: LoadBalancer
    tls:
      enabled: true
      auto:
        enabled: true
        method: cronJob

encryption:
  enabled: true
  nodeEncryption: true
  type: wireguard

eni:
  awsEnablePrefixDelegation: true
  enabled: true

envoy:
  enabled: true
  rollOutPods: true

externalWorkloads:
  enabled: false

gatewayAPI:
  enabled: false

ipam:
  mode: eni

hubble:
  enabled: false
  relay:
    enabled: false
  tls:
    enabled: true
    auto:
      enabled: true
      method: cronJob
operator:
  prometheus:
    enabled: false
  replicas: 1
  unmanagedPodWatcher:
    restart: true

devices: eth0
routingMode: native
k8sServiceHost: <KUBE_API_HOST>
k8sServicePort: 443
kubeProxyReplacement: true

Run cilium connectivty test

Cilium Version
$ cilium version -n cilium-system
cilium-cli: v0.16.20 compiled with go1.23.2 on linux/amd64
cilium image (default): v1.16.3
cilium image (stable): v1.16.3
cilium image (running): v1.16.3@sha256:62d2a09bbef840a46099ac4c69421c90f84f28d018d479749049011329aa7f28

Kernel Version
Not available
Kubernetes Version
$ kubectl version
Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.28.13-eks-a737599

Regression
No response
Sysdump
No response
Relevant log output

Anything else?
Moved here from https://github.com/cilium/cilium-cli/issues/2859. Originally reported by @tchellomello. See https://cilium.slack.com/archives/CHQF00WMT/p1731341576343369.
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

Thanks @learnitall !

Also experiencing this issue.
We have a very similar setup to the OP:

EKS
kube-proxy replacement enabled
Integrated replacement for the AWS VPC CNI enabled

Differences:

No node-to-node wireguard encryption
No cluster mesh

Added a few comments on the code and it seems the serverHost *checkPod is already coming with a wrong address
$ ./cilium  connectivity test -n cilium-system --verbose --debug --test pod-to-pod-encryption
  🐛 Finalizing Test north-south-loadbalancing
  [-] Scenario [pod-to-pod-encryption/pod-to-pod-encryption]

** added a spew on `peer.go`  we can see the object

(string)ip-10-25-46-94.ec2.internal
(check.Pod)(PANIC=runtime error: invalid memory address or nil pointer dereference){K8sClient:(*k8s.Client)<nil> Pod:(*v1.Pod)<nil> scheme:(string) path:(string) port:(uint32)0 Outside:(bool)false}(check.Pod)(PANIC=runtime error: invalid memory address or nil pointer dereference){K8sClient:(*k8s.Client)<nil> Pod:(*v1.Pod)<nil> scheme:(string) path:(string) port:(uint32)0 Outside:(bool)false}([]v1.PodIP)[&PodIP{IP:<IP_ADDRESS>,}]([]v1.PodIP)[&PodIP{IP:<IP_ADDRESS>,}]([]v1.PodIP)[&PodIP{IP:<IP_ADDRESS>,}]([]v1.PodIP)[&PodIP{IP:<IP_ADDRESS>,}]

  🐛 mmello -> srcIP: <IP_ADDRESS>
  🐛 mmello -> dstIP: <IP_ADDRESS>
  🐛 mmello -> ipRouteGetCmd(1): ip -o route get <IP_ADDRESS> from <IP_ADDRESS> iif cilium_host

** then here accessing the `serverHost` raises the trace

%!s(PANIC=String method: runtime error: invalid memory address or nil pointer dereference)

  🐛 Finalizing Test pod-to-pod-encryption
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x3b8 pc=0x10742be68]

  42 func getInterNodeIface(ctx context.Context, t *check.Test,
  43     client, clientHost, server, serverHost *check.Pod, ipFam features.IPFamily,
  44     wgEncap bool) string {
  45
  46     tunnelEnabled := false
  47     tunnelMode := ""
  48     if tunnelFeat, ok := t.Context().Feature(features.Tunnel); ok && tunnelFeat.Enabled {
  49         tunnelEnabled = true
  50         tunnelMode = tunnelFeat.Mode
  51     }
  52
  53     srcIP, dstIP := client.Address(ipFam), server.Address(ipFam)
  54     t.Debugf("mmello -> srcIP: %s", srcIP)
  55     t.Debugf("mmello -> dstIP: %s", dstIP)
  56
  57     //ipRouteGetCmd := fmt.Sprintf("ip -o route get %s from %s", dstIP, srcIP)
  58     ipRouteGetCmd := fmt.Sprintf("ip -o route get %s from %s iif cilium_host", dstIP,          srcIP)
  59     t.Debugf("mmello -> ipRouteGetCmd(1): %s", ipRouteGetCmd)
  60
  61     spew.Printf("%s", serverHost)


Ensure share-icon-color key can be used in $widget-icon-font-options

Add unused parameters to overview icon font mixin to prevent error
caused by unknown parameters.
REDMINE-15986

Coverage remained the same at 99.208% when pulling 02a8924da2acc411a1f6905df06e117d1a145680 on tf:overview-icon-font-theme into 8e90c5f6b10a287a46b46a0b6beb662d964b20da on codevise:master.


Changing performance tier without downtime still requires deallocating VM/detaching disk

In the steps to change the performance tier without downtime, one of the steps still asks to "Either deallocate the VM or detach the disk". It seems to be incorrect, as the feature is supposed to actually avoid this action. Can you please explain why or fix the docs?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9265f128-8638-d90f-e211-327c9e404a94
Version Independent ID: 01175059-931e-1f3d-f76e-c176604b2a59
Content: Change the performance of Azure managed disks using the Azure portal - Azure Virtual Machines
Content Source: articles/virtual-machines/disks-performance-tiers-portal.md
Service: storage
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@helderpinto Thanks for bringing this to our attention, that step is incorrect and we'll go ahead and get it removed from the article.

This change has been merged and will be live later today. Accordingly, I'll close this out.
#please-close


RWA-585 Update task configuration to include case management category

JIRA link (if applicable)
RWA-585
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X ] No

there is no test for this change? Do we need to add any?