PulsarListener does not recover after it has startup failure

I'm hitting an issue where the consumption randomly stops working. I haven't seen any pattern to it. I'm using spring-pulsar 1.1.0.
I've spent the past 4 hours trying to figure out why data wasn't being saved to the database. It turned out that the spring-pulsar consumers weren't receiving data. I added more logging to the @PulsarListener annotated method to log out the object after the first line of code. It still didn't log out. I added more logging to the @PulsarListener annotated method, and it started working. I restarted the container (with no code changes), and it stopped logging. I restarted again with no code changes, and it started logging again.
The methods are consuming an Avro topic. The data is being produced, and I verified with the pulsar-admin that new messages are arriving. There are five different methods in that class that are @PulsarListener listener annotated. With this bug, some methods will receive messages and others won't.  The methods are using both topicPattern and topics.  The process is running in a K8s container.
Is there any known limitation or bug that I'm hitting? It makes no sense that the methods stop receiving data with no code changes.

Hi @eljefe6a,

There are five different methods in that class that are @PulsarListener listener annotated

The 5 listeners consuming from the same topic,  are you wanting each listener (method) to consume every message or have them shared across the listeners?
It sounds like all methods are using the same subscription in an exclusive mode - which won't work and could explain the random behavior.
Are you specifying subscriptionType and/or subscriptionName on the @PulsarListener annotation? If not specified, the default type is exclusive.
Anytime I start mentioning subscriptions, I always do myself a favor and look at the nice diagram from the Pulsar docs that details the flexible subscription model.
Can you share the 5 methods (just signatures and listener annotations)?
Thanks

They are consuming five different topics. Each one is using a different subscriber name.
Here two examples:
@PulsarListener(subscriptionName = "${spring.pulsar.client.configurations.subscription-prefix}-OrderInfoWebserviceListener-sub", topicPattern = "${spring.pulsar.client.configurations.league-topic-pattern}", schemaType = SchemaType.AVRO)

@PulsarListener(subscriptionName = "${spring.pulsar.client.configurations.subscription-prefix}-GameInfoWebserviceListener-sub", topics = {
            "${spring.pulsar.client.configurations.game-info-topic}" }, schemaType = SchemaType.AVRO)

The methods are consuming an Avro topic

I took this to mean they were on the same topic. I am glad that they are not on the same topic though as that would be a strange use of the listener :)
Your listeners above look fine. I can't reproduce this locally. Can you do the following:

pare down the # of listeners. start w/ 1 and see if it works. add 2nd and see if it works... and find where it breaks?
provide client and server logs around the time this is happening
if nothing comes out of that, provide a simple app that reproduces the behavior

I wish I had a quick fix/answer for you but I can't reproduce it.
Thanks

I think I've narrowed it down. It looks like the PulsarListener doesn't work correctly after recovering from exclusive consumer exceptions like:
{"TimeStamp":"2024-08-24T08:13:31.2454382Z","Log":"org.springframework.pulsar.PulsarException: {"errorMsg":"Exclusive consumer is already connected","reqId":2154963840234886721, "remote":"dns/ip", "local":"/<IP_ADDRESS>:44716"}"}
{"TimeStamp":"2024-08-24T08:13:31.2454803Z","Log":"\tat org.springframework.pulsar.core.DefaultPulsarConsumerFactory.createConsumer(DefaultPulsarConsumerFactory.java:109) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.245514Z","Log":"\tat org.springframework.pulsar.listener.DefaultPulsarMessageListenerContainer$Listener.\u003Cinit\u003E(DefaultPulsarMessageListenerContainer.java:303) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2455478Z","Log":"\tat org.springframework.pulsar.listener.DefaultPulsarMessageListenerContainer.doStart(DefaultPulsarMessageListenerContainer.java:128) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2455844Z","Log":"\tat org.springframework.pulsar.listener.AbstractPulsarMessageListenerContainer.start(AbstractPulsarMessageListenerContainer.java:103) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2456175Z","Log":"\tat org.springframework.pulsar.listener.ConcurrentPulsarMessageListenerContainer.doStart(ConcurrentPulsarMessageListenerContainer.java:100) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2456512Z","Log":"\tat org.springframework.pulsar.listener.AbstractPulsarMessageListenerContainer.start(AbstractPulsarMessageListenerContainer.java:103) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2456837Z","Log":"\tat org.springframework.pulsar.config.GenericListenerEndpointRegistry.startIfNecessary(GenericListenerEndpointRegistry.java:234) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2457204Z","Log":"\tat org.springframework.pulsar.config.GenericListenerEndpointRegistry.start(GenericListenerEndpointRegistry.java:186) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2457527Z","Log":"\tat org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:288) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2457847Z","Log":"\tat org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:471) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2458178Z","Log":"\tat java.base/java.lang.Iterable.forEach(Iterable.java:75) ~[na:na]"}
{"TimeStamp":"2024-08-24T08:13:31.2458543Z","Log":"\tat org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:260) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2458873Z","Log":"\tat org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:205) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2459198Z","Log":"\tat org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:981) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2459553Z","Log":"\tat org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:627) ~[spring-context-6.1.8.jar!/:6.1.8]"}
{"TimeStamp":"2024-08-24T08:13:31.2460066Z","Log":"\tat org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2460501Z","Log":"\tat org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2461002Z","Log":"\tat org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:456) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2461517Z","Log":"\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:335) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2461936Z","Log":"\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:1363) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2462494Z","Log":"\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:1352) ~[spring-boot-3.3.0.jar!/:3.3.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2463064Z","Log":"\tat ai.alphabet.webservices.WebservicesApplication.main(WebservicesApplication.java:78) ~[!/:0.2.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2463462Z","Log":"\tat java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]"}
{"TimeStamp":"2024-08-24T08:13:31.2464029Z","Log":"\tat java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[na:na]"}
{"TimeStamp":"2024-08-24T08:13:31.2464501Z","Log":"\tat java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]"}
{"TimeStamp":"2024-08-24T08:13:31.2464996Z","Log":"\tat java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[na:na]"}
{"TimeStamp":"2024-08-24T08:13:31.2465381Z","Log":"\tat org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:91) ~[webservices.jar:0.2.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2465771Z","Log":"\tat org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:53) ~[webservices.jar:0.2.0]"}
{"TimeStamp":"2024-08-24T08:13:31.2466101Z","Log":"\tat org.springframework.boot.loader.launch.JarLauncher.main(JarLauncher.java:58) ~[webservices.jar:0.2.0]"}
{"TimeStamp":"2024-08-24T08:13:31.246644Z","Log":"Caused by: org.apache.pulsar.client.api.PulsarClientException$ConsumerBusyException: {"errorMsg":"Exclusive consumer is already connected","reqId":2154963840234886721, "remote":"pb1-pc-96dccc53.aws-use2-production-snci-pool-kid.streamnative.aws.snio.cloud/<IP_ADDRESS>:6651", "local":"/<IP_ADDRESS>:44716"}"}
{"TimeStamp":"2024-08-24T08:13:31.2466958Z","Log":"\tat org.apache.pulsar.client.api.PulsarClientException.unwrap(PulsarClientException.java:1093) ~[pulsar-client-api-3.2.3.jar!/:3.2.3]"}
{"TimeStamp":"2024-08-24T08:13:31.2467498Z","Log":"\tat org.apache.pulsar.client.impl.ConsumerBuilderImpl.subscribe(ConsumerBuilderImpl.java:103) ~[pulsar-client-all-3.2.3.jar!/:3.2.3]"}
{"TimeStamp":"2024-08-24T08:13:31.2467902Z","Log":"\tat org.springframework.pulsar.core.DefaultPulsarConsumerFactory.createConsumer(DefaultPulsarConsumerFactory.java:106) ~[spring-pulsar-1.1.0.jar!/:1.1.0]"}

I've tested this a few times. When the exclusive consumer exception doesn't happen, the consumption starts and works fine. When the exception happens, the consumption doesn't start.

I've run it several more times, and I've confirmed the issue. The Exclusive consumer is already connected seems to prevent the consumer from receiving messages. The SpringBoot process is running K8S.
The container restart process guarantees that two of the same processes are running. One will provision and start while the other waits and will then deprovision.
If I manually stop the container, wait, and then start, the process won't receive an exclusive consumer error and will always receive the messages.

Nice sleuthing @eljefe6a !
Yeh, the listeners are currently not very robust during startup  in the sense that if they fail on startup they do not retry. I have notated your use case in the above feature request and we will be sure your use case is included in the solve. We now have 2 users asking for this so we will look into bumping the priority.
Thanks for the detailed analysis - super helpful.

I am going to close this now as a duplicate of #445.

After some thought, we have re-opened this issue to focus on "Connection Retries" described in here.

Thanks for picking this up.  Is there a way for it to continue retrying in the background in a while loop so that there isn't a state where the consumer doesn't connect again?

Is there a way for it to continue retrying in the background in a while loop so that there isn't a state where the consumer doesn't connect again?

Yep, planning on using spring-retry but in another thread. So first attempt will be synchronous and if it fails then we will async retry every N units (configurable).

@eljefe6a I also thought of a possible workaround for now. You could append an id to the subscription name which would in effect make the 2 processes use a different subscription. Below is example of using random number (which is not ideal).
@PulsarListener(topics = "my-topic", subscriptionName = "my-sub-#{T(java.lang.Math).random()}",

Do you have an id for the process you could use for this?
Both processes would be processing the same data and this may be a problem for your scenario?

The workaround I'm doing now is operational. I'm waiting for the other container to stop before starting the new one.

Hi @eljefe6a , the ability to configure startup failure policy has just been merged. The follow up is to add Spring Boot config props to tune the policy. By default, it is set to fail fast.
When set to RETRY the default is 3 times w/ a fixed 10sec delay between attempts. Likely in your case you will want to specify a custom retry template bean to account for the time it takes your pods to come online etc..
We will be following up w/ some docs on how to configure this w/ and w/o Spring Boot.

Awesome. Thanks for making this change so quickly.
For posterity and those who encounter this issue later, does this restart issue affect consumers that have successfully been created on startup but hit a connectivity issue later in the process' lifecycle?

Awesome. Thanks for making this change so quickly.

You are more than welcome.

For posterity and those who encounter this issue later, does this restart issue affect consumers that have successfully been created on startup but hit a connectivity issue later in the process' lifecycle?

It does not handle post-startup failures. Once started, the listener thread sits in a loop and attempts a batchReceive on the consumer. Under some failure conditions the Pulsar client seems to be able to succeed on a subsequent receives - but it is not guaranteed.
That would be another resiliency feature targeted post-startup.

Closing with the docs commit https://github.com/spring-projects/spring-pulsar/commit/8ed6689e2923cf01fb5ed33648b0d913b89d046a


Standard Bank Site

Add Standard Bank Phish

Thanks for the PR @wagonza due to the way this repository resets every night any PR's from the previous day get lost. I think I will have to move the source files to another branch or repo to avoid this happening in future.

Further pull request can be done on
https://github.com/mitchellkrogza/phishing

@mitchellkrogza awesome. Will track and update that repo. Nice work!


Fixes Neo4jVector.from_existing_graph: "community:neo4j from_existing_graph hf"

Fixes Neo4JVector.from_existing_graph integration with huggingface
Previously threw an error with existing databases, because from_existing_graph query returns empty list of new nodes, which are then passed to embedding function, and huggingface errors with empty list.
Fixes 24401

Also @tomasonjo Noticed that some of the integration tests with calls tosimilarity_search are flaky, as the embeddings are mocked out, but then look for an exact match on the text.
See example
Can put in fix where just looks to see that it returns type Document, and does not look for text match, as the tests are not testing the similarity search functionality, but rather other cases.

@eyurtsev fixes a Neo4j/huggingface integration issue.  Let me know if it looks good -- thanks!

This doesnt really fix anything

@tomasonjo Can you provide more info?  Do you mean it doesn't fix this issue or that fixing it is not needed.


Notification emails are not being sent to office assignor for unassigned complaints

Reported by Heather via Zendesk.

I was able to reproduce the bug on the Dev server. Creating a complaint assigned to the "default assignor" returns an error message: "This complaint does not have an available owner or assignor."
The same error does not occur when running locally (with either in-memory or EF repositories).
Error message location:
https://github.com/gaepdit/complaint-tracking/blob/901254c9f695d216adaced8604d9507ed0856b63/src/AppServices/Complaints/ComplaintService.cs#L186-L201

Retested and the previous comment is incorrect. The error can be reproduced locally with the EF repository. When creating a new Complaint, the assigned office is populated without including the Assignor navigation property. Later when generating the email, this value is used for the recipient, but it is null.


added select all feacture to image selection

Description
Add Select all images radio button feature to delete all images at once
Fixes # (issue)
#390
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
I have clicked on the new radio button and it works fine as shown in gif
Also, include screenshots of app for the verification and reviewing purpose.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Hi, @darkshredder thank you for this pr I have reviewed this but I don't seem to understand what this feature does I mean after selecting all the images what can one actually accomplish with this feature?

Hi, @darkshredder thank you for this pr I have reviewed this but I don't seem to understand what this feature does I mean after selecting all the images what can one actually accomplish with this feature?
And a bit of advice please open an issue before making a PR it would be helpful to keep a record.

Actually the issue is already open and in it its mentioned we can delete all images on single click. (#390 this issue) @carpecodeum


CL.0 Http Request Smuggling vulnerability in Netty

We are using Spring Cloud Gateway as a routing proxy in our application setup. During a penetration test executed by an external security company, a CL.0 Http Request Smuggling vulnerability was reported to us. I tried to reproduce this and came to the conclusion, that the root cause is most likely in the reactive Netty stack used by Spring Cloud Gateway. I reported my findings as comment to an already open Github issue that addressed a similar issue there: https://github.com/netty/netty/issues/13706
I just wanted to make you aware of this problem because it seems there is no reaction on Netty side yet about this. Please note that the TransferEncodingNormalizationHeadersFilter does not solve the problem.

Please report security vulnerabilities here https://github.com/spring-projects/security-advisories
We can then privately determine if it is gateway, reactor netty, or netty itself.


Cautionary accidentals

I suggest to use cautionary accidentals in the following situations:

Notes in the same measure but in different octaves
Notes in the following measure in the same octave
First occuring note of the following measure in any octave

Should we mark cautionary accidentals with @enclose="brack"?

And, should they be marked as supplied? @rettinghaus  ? :)

Everything added by the editors should be enclosed in supplied tags, using @resp to point to the responsible editor.
Cautionary accidentals should be makred with @func="caution".
Using brackets I'm not so shure. If we use brackets on the accidentals, we should add them to everything added, to be consistent. Added bass figures are only text lacking @enclose, and thus they would need additional characters.
What about letting the users choose their individual stylings with XSLT, like adding brackets, use special colours, or simply hide supplied material?

I like the idea of letting the user choose a lot.
If we enclose everything added by the editor in supplied tags, we also need to encode all the original repetitions of accidentals in a measure and identify their omissions accordingly, or am I missing something? Otherwise we treat cautionary and normal accidentals  differently ...

The accidental placement is a bit erratic. @func="caution" is a logical attribute, so it doesn't say anything about, where it may come from.
For normalization it could be nice to remove superfluous accidentals. so we could mark those with a <orig> or a <del> or even with a <sic> (without anything else like <choice>).
Trying to mark everything, that doesn't fit a higher logic would be overkill.

My proposal: put accidentals in the source that may be omitted in modern scores in <orig>, the ones that are missing for a modern score in <reg>, which itself is contained within a <supplied>.

So I went through all the score files and corrected the accidentals I found. Leaving it open for now since the music example are still missing ...


Update main.tf

Hey there, the current setup of azure Postgres doesn't have any config to turn on and off the auto_grow_enabled.
The auto_grow_enalbed gives an advantage to the Postgres to increase their volume once it is 90% full.

Fixes #000
Changes proposed in the pull request:

Hi @surajrubik , thanks for opening this pr. I have one comment, would you please take a look? Thanks.


Removed lastName field

What was the feature/problem?
Removed "lastName".  Renamed "firstName" to "name"
Check lists (check x in [ ] of list items)

[ ] Test passed   (2 mongo tests have a timing issue)
[x ] Coding style (indentation, etc)

Additional Comments (if any)
{Please write here}

Codecov Report

Merging #9 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #9   +/-   ##
=======================================
  Coverage   89.86%   89.86%
=======================================
  Files          19       19
  Lines         217      217
  Branches       13       13
=======================================
  Hits          195      195
  Misses         18       18
  Partials        4        4

Flag
Coverage Δ

#api
95.91% <ø> (ø)
:arrow_up:

#ui
84.87% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

api/src/db/Wish.js
100% <ø> (ø)
:arrow_up:

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 b9e0db0...b6b4009. Read the comment docs.


Loading failed on .min version

Attempting to develop a map that uses this library. Examples found online include the following line of code
<script src="https://raw.github.com/calvinmetcalf/leaflet-ajax/master/dist/leaflet.ajax.min.JS"></script>
But when I attempt to use this link I get the following error
"Loading failed for the

I have the same problem..

try
note the lowercase file extention


Ams sdk

Also - should we split this into a 2-step flow, except we poll the AccountMgmt once per week to check for a new API version? I feel that if we don't have some automated way to check we could fall behind their API.

This api is hosted on gitlab. Any updates will be painful and will need to stay manual due to fact that we use patch. I used patch because we can remove most of their endpoints that we do not use.
AMS will not be documented or updated frequently.
API we are using is stable etc.

Also - should we split this into a 2-step flow, except we poll the AccountMgmt once per week to check for a new API version? I feel that if we don't have some automated way to check we could fall behind their API.

This api is hosted on gitlab

I meant to poll https://api.openshift.com/api/accounts_mgmt/v1/openapi.

Any updates will be painful and will need to stay manual due to fact that we use patch. I used patch because we can remove most of their endpoints that we do not use.
AMS will not be documented or updated frequently. API we are using is stable etc.

That's fine.


Thrower inserters seem to copy more properties than one might deem intended. Also its impossible to repair a directed bounce pad.

I probably shouldn't do 2 bug reports in a single post but.... Such is life.
When you do copy paste on an inserter if you say... Copy the properties of a long handed inserter to a stack inserter it converts the inserter into a long handed stack inserter. While this is a cool feature and would love to be able to keep it. It doesn't seem intentional.
The other bug is that if I place a directed bounce pad and try to manually repair it. It seems to flash "Not Operable" like 20x/second and does not get healed. The strangest part of this bug is that it doesn't seem to happen to regular bounce pads or directed train bounce pads.

That's certainly not intentional but I dont think I can fix it because that's just how Factorio copy and paste works. By how Factorio makes the inserters work, they can only either have the pickup and drop positions changeable or not changeable. I have to have them changeable because of the range adjusting, and there's no setting to only have the drop position changeable. So unfortunately I don't know much that can be done about it but I don't think it's too big a deal for it to be there.
For the bounce pad repair, the directed bounce pad is actually a reskinned constant combinator, unlike the regular bounce pad which is just a "block". I did that because at one point I wanted to be able to control which way the directed bounce pad was facing using the circuit network, or be able to bounce different items in different directions based on the signal, and it being a constant combinator under the hood would let you connect wires to it. But I never followed through on that idea and when I added the ability to toggle the bounce range indicators on the bounce pads on and off by clicking on them, the clicking was opening the constant combinator GUI which was annoying so I made it so all directed bounce pads couldn't be "operated" meaning it wouldn't open the GUI when you clicked it. I didn't know that it would prevent people from repairing it too though, that's new to me. I'll either change the directed bounce pads to a normal "block" entity or actually implement the direction control one day

idk about the copy/pasting of settings but the repairing should work now


docs: Improve start mvp servers docs.

Follow the Guide to build libraries developed in other workspaces.

I guess this guide may not clearly describe how to build the dependence for mvp-dapp.
So I write docs that how to start mvp server step by step.

Section of Start Kuai MVP DApp UI can be appended by adding its link https://github.com/Magickbase/kuai-mvp-dapp-ui

Section of Start Kuai MVP DApp UI can be appended by adding its link Magickbase/kuai-mvp-dapp-ui

Will the link of front-end be added in this PR?
BTW, please have a review @Daryl-L @PainterPuppets


[Feature Request] Add column for "Total Elapsed Time" (in the currently visible month) in the table at the bottom left

Currently, in the table at the bottom left, there is only "Elapsed Time" which is for the last play session. That's nice, but I think it would make a lot of sense to include a column that adds the total elapsed time for that month as well. That way we can get a nice summary of how much we played each game during each month.

You must open issue on https://github.com/Lacro59/playnite-gameactivity-plugin/issues


fix: read iam client id and secret from environment variables

When the IAM Client ID and Secret parameters were added, I forgot to include them in the getServiceCredentials and getCredentialsFromEnvironment methods. They should be included here so they can be specified as environment variables like any other credential parameter.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Plugin loading error

[main/TRACE] [Sponge]: Scanning mods/EconomyLite-5.0.0-2.7.0.jar for plugins
[main/ERROR] [Sponge]: Skipping plugin with duplicate plugin ID 'economylite' from mods/EconomyLite-5.0.0-2.7.0.jar
Using the latest plugin and sponge version 1.11.2-6.0.0-BETA-215.

Do you have two EconomyLite JAR files installed?

Yikes. I didn't realise. Thanks.


aaa

Description
What steps will reproduce the problem?

What is the expected output? What do you see instead?
Please provide any additional information below
File "/Users/md.kamalhossain/opt/anaconda3/envs/spyder/lib/python3.6/site-packages/qtconsole/base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
File "/Users/md.kamalhossain/opt/anaconda3/envs/spyder/lib/python3.6/site-packages/qtconsole/base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
File "/Users/md.kamalhossain/opt/anaconda3/envs/spyder/lib/python3.6/site-packages/qtconsole/base_frontend_mixin.py", line 138, in _dispatch
File "/Users/md.kamalhossain/opt/anaconda3/envs/spyder/lib/python3.6/site-packages/spyder/widgets/ipythonconsole/namespacebrowser.py", line 215, in _handle_execute_reply
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
Traceback (most recent call last):
File "/Users/md.kamalhossain/opt/anaconda3/envs/spyder/lib/python3.6/site-packages/qtconsole/base_frontend_mixin.py", line 138, in _dispatch
Traceback (most recent call last):
Traceback (most recent call last):
Version and main components

Spyder Version: 3.2.3
Python Version: 3.6.13
Qt Versions: 5.9.6, PyQt5 5.9.2 on Darwin

Dependencies
pyflakes >=0.6.0 :  2.4.0 (OK)
pycodestyle >=2.3:  2.8.0 (OK)
pygments >=2.0   :  2.11.2 (OK)
pandas >=0.13.1  :  1.1.5 (OK)
numpy >=1.7      :  1.19.5 (OK)
sphinx >=0.6.6   :  4.4.0 (OK)
rope >=0.9.4     :  0.22.0 (OK)
jedi >=0.9.0     :  0.17.0 (OK)
psutil >=0.3     :  5.8.0 (OK)
nbconvert >=4.0  :  6.0.7 (OK)
sympy >=0.7.3    :  None (NOK)
cython >=0.21    :  None (NOK)
qtconsole >=4.2.0:  5.2.2 (OK)
IPython >=4.0    :  7.16.1 (OK)
pylint >=0.25    :  2.9.6 (OK)

Hey @kamalhossain22, thanks for reporting. You're using a very old Spyder version, which is not supported anymore.
Please read our documentation to learn how to install a more recent version.


Delete with predicate state persisted across data explorer and buckets page

Note how the selected bucket in the delete with predicate overlay is not the same as the bucket that I clicked on.

cc @Asalem1


Knife-ec2 prematurely fails before SSH is even available.

For some reason, When I try bootstrapping a new server, It creates the VM but right away when it gets to the 'Waiting for sshd access to become available' line, it instantly fails within a second or two with "ERROR: Net::SSH::Disconnect: disconnected: Too many authentication failures (2)" even though SSH has not started yet on the server [usually takes a minute or two]. It just seems it tried connecting and failing too FAST even before the new VM wasn't loaded up yet.
Example command.
knife ec2 server create <IP_ADDRESS> -N mytestserver.server.com --image ami-12345 -f t3.medium --region ca-central-1 --ssh-key mykey --subnet subnet-d123455 -g sg-1234567 -E production -r 'role[tester]'  --ebs-optimized --cpu-credits standard --ebs-size 20 -A --server-connect-attribute private_ip_address --private-ip-address <IP_ADDRESS> --aws-profile myawsprofile --sudo --node-ssl-verify-mode none --ssh-verify-host-key never -U root --ssh-gateway<EMAIL_ADDRESS>
Output
Waiting for EC2 to create the instance
Instance ID: i-0b12345678
Flavor: t3.medium
Image: ami-12345
Region: ca-central-1
Availability Zone: ca-central-1a
Security Group Ids: sg-1234567
AWS Tags: Name: mytestserver.server.com
SSH Key: mykey
T2/T3 Unlimited: Disabled

Subnet ID: subnet-d123455
Tenancy: default
Private IP Address: <IP_ADDRESS>

Waiting for sshd access to become available
SSH Target Address: <IP_ADDRESS>(private_ip_address)
ERROR: Net::SSH::Disconnect: disconnected: Too many authentication failures (2)

Versions
chef-client 17.6.18
Using latest Knife gem [knife (17.5.22)
knife-ec2 (2.1.4)

I think it's related with using a ssh-gateway and that it's not waiting.


Saving changes to users (possibly other forms) not working on Microsoft Edge

Describe the bug
While adjusting roles for a user, I noticed it would not update. After going through error logs and doing an update incase it was a bug, it still would not work.
Then I realized I am using Edge these days and used to have google chrome, and low and behold it worked fine on there.
Steps To Reproduce
Steps to reproduce the behavior:

Go to any user, and adjust their settings (add/remove a role)
Click on 'Save'
Instead of being redirected back to the Users page (with the top right notification "Succesfully saved user..") the form will refresh
The user was not updated (and no error was shown)

Expected behavior
To properly save the user
Screenshots
NA
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): Had it on 0.30.4 but now still on 0.31.6
PHP Version: 7.2.24
Hosting Method (Nginx/Apache/Docker):  Nginx (Ubuntu 18.04)

Additional context
This may not be the only form with this issue, but its the only one I tested.

Thanks for reporting @aekramer,
Would you be able to confirm your exact version of edge in use?  I'd generally expect edge to behave the same as chrome with the fairly recent move for edge to use the same base project as chrome. Could possibly be an extension only existing in edge?

Thanks for reporting @aekramer,
Would you be able to confirm your exact version of edge in use? I'd generally expect edge to behave the same as chrome with the fairly recent move for edge to use the same base project as chrome. Could possibly be an extension only existing in edge?

I am using Edge version 88.0.705.74 (64-bits)
While I do have a very barebones chrome (only use it for things that are not supported in edge, or if a website is behaving weirdly I test if its also the case in chrome, and as my laptop is relatively new chrome has been opened less than 10 times in total), edge also does not really have any extensions, I only use an adblocker and password manager. I just tried disabling them and the issue still persist (have not tried uninstalling completely as its a bit more hassle for now), I might try it on a different computer tomorrow that does not have these extensions in edge.

Thanks for confirming @aekramer. Tested on Version 90.0.803.0 (Official build) dev (64-bit) (Thier Linux build) and seems to work fine.
Something similar could occur if the browser was auto-filling the password field(s) in any way. You should see an error message below the fields but it might not be obvious, especially on a smaller screen.

Since there's been no follow-up I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.


Empty/invalid or REST operations are showing for WebSocket APIs

When viewing the WebSocket APIs, it shows invalid operations names. Ideally, it should not show any operations.
Dashboard: Manager Analytics
Widget: API LATENCY TIME
Dashboard: Monitoring
Widgets: ERROR SUMMARY, ERROR SUMMARY OVER TIME, API LATENCY SUMMARY, API LATENCY OVER TIME, API TRAFFIC OVERTIME

This is fixed now. Hence closing.


⚠ ClamAV has degraded performance

In a8b5764, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 578 ms

Resolved: ClamAV performance has improved in 79f7806.


Add an example for Dictionary.merge(), mention lack of recursion

For context, I found that it wasn't recursive while working on https://github.com/Calinou/godot-benchmarks/blob/add-web-interface/merge_json.gd.

Thanks!

Cherry-picked for 4.1.4.


Renaming a column of the table provided in UI Page 4

@QQ-Sortiz Regarding the table provided in UI Page 4,
there is currently a column named "Background Functional Group".
The name of this column should be changed into: "Biotic Resource".
Many thanks!

Changes were implemented. Kindly check.

Thanks a lot; I can now close this issue.


docs: fix simple typo, shuld -> should

There is a small typo in unpickle_test.py.
Should read should rather than shuld.
Semi-automated pull request generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Thanks, applied the patch.


Feature: Resource Limits for backstage container

Description of the change
Adds support for setting requests and limits on the backstage deployment such that folks can execute to their desired best practices on resource consolidation.

Existing or Associated Issue(s)
https://github.com/backstage/charts/issues/26

Additional Information
Looked over my local developer deployment that has a number of added plugins and a few charts etc and what the resource limits were. Set memory fairly high comparatively but cpu should be fully in line.

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
[x] JSON Schema generated.
[x] List tests pass for Chart using the Chart Testing tool and the ct lint command.

So I'm assuming a bit that #18 is just waiting on a touch of things and should update the docs automatically for this, but unclear what that might be waiting on. If we want to proceed with this I can update this and potentially that pr depending on desires.

hey @JoshuaJackson-jobvite yeah, yesterday it was still missing approval from another maintainer and then it was waiting for me to get back to work today (since the culture in Backstage is to self-merge once approved for maintainers). It is merged now. :slightly_smiling_face:
Can you please rebase and run pre-commit?


bing -> being

For all tenses, the progressive gives "bing" instead of "being" for to be.

PR: https://github.com/rossmeissl/verbs/pull/25

bing instead of being still unfixed

@benamente sorry just closed this in #25


WIP: Add Helm Chart for the OpenSearch cluster CR

This fixes #448
PR to add Helm Chart to install OpenSearch cluster CR.

Hi @IshaGirdhar.
IMO this is the wrong approach here.
What would be beneficial is adding a cluster spec to the helm chart of the operator itself (hidden under a by default disabled value), for those who just want to install one cluster and don't want to deploy the operator and the cluster spec separately (for example the prometheus-operator does something similar where you get the operator + 1 prometheus stack by installing the chart and can always create additional stacks by deploying additional CRs).
But a separate helm chart with only a cluster spec is IMO not very helpful. If someone is deploying several opensearch clusters (and is doing this as part of some larger deployment) then they most likely already have either mechanisms for deploying kubernetes yamls (so they don't need the overhead of the helm chart) or have their own custom helm chart around that combines such single yamls into one deployment (my personally preferred approach).
So IMO the helm chart as you have written it is not something we should add to the operator offering.

Hi @IshaGirdhar. IMO this is the wrong approach here.
What would be beneficial is adding a cluster spec to the helm chart of the operator itself (hidden under a by default disabled value), for those who just want to install one cluster and don't want to deploy the operator and the cluster spec separately (for example the prometheus-operator does something similar where you get the operator + 1 prometheus stack by installing the chart and can always create additional stacks by deploying additional CRs).
But a separate helm chart with only a cluster spec is IMO not very helpful. If someone is deploying several opensearch clusters (and is doing this as part of some larger deployment) then they most likely already have either mechanisms for deploying kubernetes yamls (so they don't need the overhead of the helm chart) or have their own custom helm chart around that combines such single yamls into one deployment (my personally preferred approach).
So IMO the helm chart as you have written it is not something we should add to the operator offering.

@swoehrl-mw What you say makes sense to me and that also supports our use case as well. The only reason for taking this approach was to support multiple clusters using helm. Sure I can modify my existing PR or open a new PR for what you proposed.

@swoehrl-mw On second thoughts, this solution seems to be fine as well, as this supports what the operator supports(multiple clusters), doesn't have any technical challenges though yeah users may have their own automated ways to create multiple clusters but that doesn't stop them from using Helm to do the same.

Hey @swoehrl-mw @prudhvigodithi
What are you saying about that PR ?

@swoehrl-mw Please check. I have addresses all review comments.


Need to find <uv.h> properly

Some node engines (for example FreeBSD's port) are using system provided libuv and therefore node include files will not have uv.h installed with them.
A fallback should be provided for this case.

https://github.com/saper/nodegit/commit/4f75bbb1cdd758f9b4449c06803fe566598d5c16 hardcodes the path and works around the problem for my FreeBSD installation

@srajko this broke after we started using uv directly (#836, #1019)


Missing backslash in command examples(?)

It seems that there is an issue with the commands mentioned in the example section towards the end of the article.
The 'Certutil -setreg' commands in the example section towards the end seem to be missing a backslash; the current commands work but it occurs to me that the keys end up in the wrong place and with a wrong, useless name :/ The command 'Certutil -setreg CACRLPeriod Weeks' would create (or update) the 'CACRLPeriod' key directly under 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration' -- Which seems wrong to me 🤔
By using a backslash in the key parameter, i. e. 'Certutil -setreg CA\CRL...' the registry keys would update the existing (and correct) keys (i. e. 'CRLPeriod') under 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CertSvc\Configuration[Name of Root CA]'
The section I believe to be wrong:
"Each of these settings can be configured after the CA has been installed:
CLI
Certutil -setreg CACRLPeriod Weeks
Certutil -setreg CACRLPeriodUnits 1
Certutil -setreg CACRLDeltaPeriod Days
Certutil -setreg CACRLDeltaPeriodUnits 1"
Sidenote -- I do wish the documentation for PKI was a bit more concise and less ambigous :/ 🙏

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

ID: 9c71fe29-dbfd-5d1c-71a6-284f9bfaec38
Version Independent ID: 1968b9b5-40db-e8bc-a1e9-3c17e74e9728
Content: Prepare the CAPolicy.inf File
Content Source: WindowsServerDocs/networking/core-network-guide/cncg/server-certs/Prepare-the-CAPolicy-inf-File.md
Product: windows-server
Technology: networking
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Hacks arent working

My hacks arent working and i did everything im mad

Speedhack will always work, so you're attached to the wrong process.
At this point after clicking "attach process" just YOLO and try every firefox process to see if it works.


feat(frontend): add tapd config-ui

Summary
add config-ui for tapd(only connections and advanced mode)
tapd.svg picture is not good....
Does this close any open issues?
relates to #2673
Screenshots

![image](https://user-images.githubusercontent.com/39366025/182685138-9b9a0c65-f185-41ef-a992-1f9a8d8e33ce.png)
![image](https://user-images.githubusercontent.com/39366025/182684485-f7995cb4-b31b-4d08-a71c-91418e0ac4d8.png)

Other Information
Any other information that is important to this PR.

@warren830 Please confirm Backend changes w/ @klesh.


logging a lot of data quickly causes a ton of errors

any idea how to get logtail to gracefully handle and buffer this, or else just drop messages if the queue is too big?

also, i'm not sure what the message there about "access control checks" has to do with anything — in fact, the logs are totally being accepted by Logtail (confirmed via logtail dashboard and looking at the network tab and seeing 202 ACCEPTED responses for the Logtail XHR requests....)

setting burstProtectionMax: 20 and burstProtectionMilliseconds: 1000 resolves this issue. that said, the error messages here are quite confusing (and on Chrome, you don't even get the note about 'reached max queued data' — just Safari, so it's even more confusing)

Hi @aroman,
thank you for creating the issue! I appreciate it.
We definitely want the library to handle large messages and send them to Better Stack without errors.
My first impression is that we could change batching configuration to take the actual size of messages into account.
I.e. current batchSize is in "number of log lines" but having e.g. batchSizeKb would result in logs being sent more often and not hitting the browser limits.
I'll pass this on to the team for someone to take a look.
Thanks again for rasing this!

Hi @aroman, thanks for reporting this 🙌
I've fixed it in v0.4.19. After reaching 48 KiB of data in queue, the queue gets flushed automatically.
Tested it on this JS snippet:
const logtail = new Logtail("MY_SOURCE_TOKEN");

logtail.info("request 1 " + "X".repeat(10000))
logtail.info("request 2 " + "X".repeat(10000))
logtail.info("request 3 " + "X".repeat(10000))
logtail.info("request 4 " + "X".repeat(10000))
logtail.info("request 5 " + "X".repeat(10000))
logtail.info("request 6 " + "X".repeat(10000))
logtail.info("request 7 " + "X".repeat(10000))
logtail.info("request 8 " + "X".repeat(10000))
logtail.info("request 9 " + "X".repeat(10000))

Previous version of the library triggered the Reached maximum amount of queued data of 64Kb for keepalive requests error as you mentioned.
<script src="https://cdnjs.cloudflare.com/ajax/libs/logtail-browser/0.4.17/dist/umd/logtail.min.js" integrity="sha512-ULxpvdXTYsKoCUAaKxnqE+R/C9+2SaOs/xrrSQ3RKjIfrahLecA98mcTs82TXgtNdjQ+8y2Rf5EeyYC8djBz4g==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>

After the update, data got sent to Better Stack without errors:
<script src="https://cdnjs.cloudflare.com/ajax/libs/logtail-browser/0.4.19/dist/umd/logtail.min.js" integrity="sha512-EYdnWL7Lrn+96R4BDaOxCgCWWOoZQiMSsfy+3NKYSJxK/CAt6y7cPLvGHRWONYO8Y0SsGuk5Y+lC1w3up7f7OA==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>

There are still some cases where the queue can exceed the 64 KiB limit, but hopefully should not occur in real-case scenarios. In that case, we would have to make the queuing process bit more complicated and/or drop logs.


Run Rhasspy on Raspberry Pi 4

Hello,
thanks for this amazing project which I would very much like to try!
However unfortunately I'm not managing to get it running on Rasperry Pi 4 with standard 32bit Raspberry Pi OS.
First I tried the deb package installation like described here: https://rhasspy.readthedocs.io/en/latest/installation/#debian
I installed the current armhf package. Installation worked, but on starting I'm getting this error on console:
CTraceback (most recent call last):
  File "/usr/lib/rhasspy/usr/local/lib/python3.7/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/rhasspy/usr/local/lib/python3.7/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/usr/lib/rhasspy/usr/local/lib/python3.7/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/usr/lib/rhasspy/rhasspy-speakers-cli-hermes/rhasspyspeakers_cli_hermes/__init__.py", line 13, in <module>
    import soundfile
  File "/usr/lib/rhasspy/usr/local/lib/python3.7/site-packages/soundfile.py", line 16, in <module>
    from ctypes.util import find_library as _find_library
  File "/usr/lib/rhasspy/usr/local/lib/python3.7/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: libffi.so.6: cannot open shared object file: No such file or directory

The WebUI works, but none of the recognition / text-to-speech things etc. is working.
Second I tried to install as described here: https://rhasspy.readthedocs.io/en/latest/installation/#virtual-environment
Everything worked until make install stopped with this error:
ERROR: Could not find a version that satisfies the requirement onnxruntime~=1.6.0 (from larynx~=0.3.0->rhasspy==2.5.11) (from versions: none)
ERROR: No matching distribution found for onnxruntime~=1.6.0 (from larynx~=0.3.0->rhasspy==2.5.11)

Thanks for any help and suggestions!

I've fixed the first error with sudo apt-get install libffi6
However, now I'm still not able to record audio and also get a TrainingException.


Fix fzf version URL

Since version 0.54.0 fzf releases are prefix with a v. Don't know how to handle this in a retro-compatible way tbh

Unfortunately there is no way (besides creating another distribution or taking time to integrate https://github.com/devops-works/binenv/pull/252)

Thanks @pichouk !


Fix keep_alive_for by sending an initial keep alive request, otherwise the request hangs forever.

Title.

Possible to get a crates.io release after this one? :D

Possible to get a crates.io release after this one? :D

Sure.

-- I made it also check the initial request before returning the stream.


ISS-149 some extended assembly not taken in account

The following extended assembly is not managed yet by chibicc :
static WEBP_INLINE void GetCPUInfo(int cpu_info[4], int info_type) {
asm volatile (
"xchg{q}\t{%%rbx}, %q1\n"
"cpuid\n"
"xchg{q}\t{%%rbx}, %q1\n"
: "=a"(cpu_info[0]), "=&r"(cpu_info[1]), "=c"(cpu_info[2]),
"=d"(cpu_info[3])
: "a"(info_type), "c"(0));
}
CC       libsharpyuv_la-sharpyuv_cpu.lo
../src/dsp/cpu.c:55:     : "=a"(cpu_info[0]), "=b"(cpu_info[1]), "=c"(cpu_info[2]), "=d"(cpu_info[3])
^ tokenize.c extended_asm.c output_asm 398: in skip : expected ')'

the specific case here about libwebp not fixed. Only some cases about arrays in extended assembly was fixed.


Accessing ReQL: Implement changes

Issue summary
We would like to listen to the change feeds via PHP.
Docs: https://rethinkdb.com/api/javascript/changes/
Issue checklist

[x] Implement changes
[x] Implement changes unit tests
[x] Add changes documentation
[x] Implement changes options
[x] Implement changes options unit tests

Actual Behavior
There is no changes listener in the driver.
Expected Behavior
Given I am listening with changes
When new data is crudding
Then I should see a stream of change messages
Specifications

PHP Version: 7.x
RethinkDB Version: 2.3+

Implemented, only need to write documentation

Documentation also written

This issue has been resolved.


The resources field should be required

According to the current version of the spec:

the container.resources field is required
the container.resources.cpu field is required
the container.resources.memory field is required

I think this is bad, but... it is what the spec says, so we should fix that in Rudr.

See:

https://github.com/oam-dev/spec/blob/master/3.component_model.md#container
https://github.com/oam-dev/spec/pull/218
https://github.com/oam-dev/spec/pull/182


Question: Is Version 2.5.0 Supported

Hi, just got a message Version 2.5.0 is available for B+J Free@Home. Any one already running this together with Henry's Api?

👍Works fine for me. See: https://github.com/henry-spanka/freeathome-api#tested-versions

Will put my glasses 🤓 on next time 😉
Thanks


splash screen size issue in android

i prepare a splash.png file with 2732*2732. i run the command to generate splash screen for both ios and android. for ios is perfect but for android its showing color on background image was not fit properly

+1 the same

+1 the same

duplicate of #172 ?

found the solution: replace in ./android/app/src/main/res/drawable/launch_screen_bitmap.xml value of android:gravity from center to fill

@russ666 It fills, yes, but it resizes image incorrectly if display and image have different ratio

Hello, we just revamped the generator 😁
For up to date icon and splashscreen generation please use @bam.tech/react-native-make
The new version handles 3 different types of rendering for the splashscreen image (center, contain and cover), so it should solve your issue 😉


Improvements on CachingInboundEventSource

Currently CachingInboundEventSource has an issue with initialization of state. Currently the cache is only populated explicitly calling the handleResourceEvent. Therefore when related primary resources is reconciled the state might not be initialized.
To fix this a resource fetching mechanism could be implemented, similarly as in PerResourcePollingEventSource, thus first time the primary resource appears it will initialize the state by fetching the target resource.
Optionally could have a cache expiration period, for the cases if some event is lost, making sure that if a longer period the resource is not refreshed, it is fetched it again.

More generally speaking, I think our caches should be able to transparently check the API server if a resource is not found locally…

I'nm not sure how that would look like, also it really depends on type of resource and event source.  There are different behaviors, like PerResourceEventSource has completely different behavior than PollingEventSource. And I think it is good. So that the event sources populate the caches, with their specific behavior is the way to IMO.

More generally speaking, I think our caches should be able to transparently check the API server if a resource is not found locally…

Regarding external resource caching, at least, the cache should be able to handle staleness. Currently, the resource must be removed from the cache and it become complicated to detect if an event should be triggered especially on deleted resource.


add doc "configure house and rooms"

Greats !
But it's possible to create a fr image ?
And with the new UI please ^^

I fix it in the last commit :)

Thanks !! You're awesome guy !

Hmmm screenshot need to be updated/check for every release, very time consuming.
Most of the time it is useless and in this case it is too small and it doesn't make it easier to understand.
What do you think ?

I agree with you, I copy the documentation style of the actual documentation but yes, I think images can be optional in most cases (and it is time consuming to screenshot for EN, FR and with usefull examples)

I do not agree with you ^^
While screenshots take time but it is a considerable resource for a user who would be lost in explanations !
This is also why 90% of the tutorial integrates images / screenshots.
For the problem of the versions I already thought of it and I would add a selector to adapt the documentation according to the chosen version, the images will also adapt 🙂

I'm not saying that all screenshot are useless but in that case this is documentation, not tutorial / blog post.
Screenshot is small and unreadable.


cannot import to esm project

Describe the bug
import apollo-server-logging into an esm project causes a runtime error (node v19.2.0 here)
(node:16428) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
/Users/user/software/app/node_modules/apollo-server-logging/dist/esm/index.js:1
export * from './plugin.js';
^^^^^^

SyntaxError: Unexpected token 'export'
    at internalCompileFunction (node:internal/vm:74:18)
    at wrapSafe (node:internal/modules/cjs/loader:1141:20)
    at Module._compile (node:internal/modules/cjs/loader:1182:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at Module._load (node:internal/modules/cjs/loader:922:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

To Reproduce
Steps to reproduce the behavior:

import the package into your project 'import ApolloServerLogging from 'apollo-server-logging';'
run your project

Desktop (please complete the following information):
macos, node v19.2.0

I'm able to import this package when the following changes are made.
Add the following to apollo-server-logging's package.json exports,
  "exports": {
    ".": {
      "types": "./dist/types/index.d.ts",
      "import": "./dist/esm/index.js",
      "require": "./dist/cjs/index.js"
    },
+   "./cjs": "./dist/cjs/index.js",
    "./*": {
      "types": "./dist/types/*.d.ts",
      "import": "./dist/esm/*.js",
      "require": "./dist/cjs/*.js"
    }
  },

Import apollo-server-logging in the following way from the dependent project
import { ApolloLoggerPlugin as ApolloServerLogging } from 'apollo-server-logging/cjs';

if you would export the cjs that would help me to use this package.


content-api: python get product example

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/shopping-content/code-example-get-product-offer.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


chore: add max faraday version to tests

Summary
Temp workaround for https://github.com/arsduo/koala/issues/659 to unblock CI until upstream Koala itself supports Faraday 2.0

cc @SomalianIvan this should unblock https://github.com/open-telemetry/opentelemetry-ruby/pull/1043

Sending my grey approval


Relative Arguments contract.json

Is it possible to use relative arguments for contract constructors like so:
# config/contracts.json
{
  ...
  "development": {
    "contracts": {
      "MyContract": {
        "args": [
          "$msg.sender"
        ]
      }
    }
  }
  ...
}

If yes, where can I find documentation about it? If no, what is the best way to handle this, when I can't rely on static contract deployer addresses?

@gianlucaschoefer you can just use msg.sender in solidity in the constructor, in the next version of embark you'll also have options such as from and fromIndex to specify the deployer account


API v2 & v3 errors when filtering across post meta table.

See https://demo.ghost.io/ghost/api/v3/content/posts/?filter=meta_description%3A-null&key=22444f78447824223cefc48062
VS https://demo.ghost.io/ghost/api/v3/content/posts/?filter=slug%3A-null&key=22444f78447824223cefc48062
The query works for all fields which are not part of the new join table. Looks like some configuration for NQL was likely overlooked as part of the work to split the post table.
Technical details:

Ghost Version: 3.4
Database: MySQL

As suspected the main reason for the query failure is lack of defined relation and possibly expansions from posts to posts_meta table in NQL. To be able to define these we'd first have to support 1:1 relations in Mongo-Knex and later examine how expansions would function to be able to expand field filters living in posts_meta table.
I've done a little spike in Ghost when looking into the issue here. It could be useful for a new test confirming a bug and see where things would have to go into when mongo-knex adds needed feature.
Don't have a concrete estimation on how long the change would take but this is what I think needs to be budgeted for:

Design and add something a-la "oneToOne" relation support to Mongo-Knex to be able to expand existing manyToMany query builder.
Investigate how the fields from posts_meta table should be "expanded" and if there's a better way to define where to look for them instead of adding a separate configuration for each field like here.
Implement above in core :)

@ErisDS to give better estimation on the above would need maybe half a day appetite to play with mongo-knex and figure out the deets.

To move on needs appetite to reconfirm mongo-knex is 100% correct path to go and if so specify what exactly an how it would need to change. Guesstimating .5 day.

Similarly to ordering bug solution short term will expand existing configs and NQL to support posts_meta relations. Long term plan, same as in referenced comment.
Timeboxing 1 day of work to see what kind of work might be involved on NQL level to implement short term fix.

@matthanley after tinkering a bit in mongo-knex have a better estimation for what needs to be done:

1:1 relation implementation - ~2 days
Implement a mechanism to add "expansions" generically from the model layer - something that might work would be similar to orderAttributes introduced when solving ordering by relations problem - .5-1 days
Check if there are any collisions with ordering and other relations - few hours, would write some regression tests

To reiterate, these all would be "short term" fixes and something that manages this case of 1:1 relation would need to come from Bookshelf or plugin abstraction.
Let me know if you have any questions around this plan!

Sounds like a good plan - are there any other 1:1 relationships in the codebase that would benefit from this also?

No other relation, I don't think. At the moment the only other 1:1 relation in models is posts <-> emails. Don't know of any usecases where we'd need to filter/order or eager load data. Might be something we could use if any other tables "run out of space", but nothing I could think of from the back of my head straight away.

The approach I've implemented in mongo-knex failed after I tried integrating it into Ghost itself... due to join statements not being picked up by knex when used in filter subqueries :tired_face: Will probably have to do "where in ()" approach that is used in many:many filtering (which has limitations on SQLite) or will try to find a way to hook eager loading of the relation pre-filtering (similar to ordering). Will continue on this issue on Monday

Have finished implementation of this relation in mongo-knex - https://github.com/NexesJS/mongo-knex/pull/36. Next would be merging the PR and integrating new version within Ghost. Guesstimating 1 day of work.

After the merger of https://github.com/TryGhost/Ghost/pull/12307, the bug is fixed. Next step here would be figuring out 1:1 relationship preloading on (most likely) bookshelf layer. Maybe worth creating a new issue with 1:1 support as this bug is fixed and relationship support would be covering more areas than just filtering (other post_meta split issues) // cc @matthanley


Soundbar

Before opening the issue, have you...?

[X] Searched for existing issues

Is your feature request related to a problem? Please describe
Looking to control Samsung soundbar. Tv is LG.
Describe the solution you'd like
Soundbar audio modes / volume control / treble / bass / modes such as night mode, etc
Describe alternatives you've considered
Currently use the SmartThings app
Additional context
I tried adding the plugin, but it doesn't seem to see the soundbar

Soundbars are currently not implemented. I will have a look at it how complicated an implementation would be. I might need your help because I do not have a soundbar myself. So maybe you might need to copy some logs so I can see what the API returns. But first I will have a look at the documentation and see how far I come

Soundbars are currently not implemented. I will have a look at it how complicated an implementation would be. I might need your help because I do not have a soundbar myself. So maybe you might need to copy some logs so I can see what the API returns. But first I will have a look at the documentation and see how far I come

I'm currently using a SmartThings soundbar (Q70T) and just wanted to let you know I can provide any information needed to help the cause.

Hey guys. Sorry for late response - was quite busy the last weeks. Maybe I can find some time the next days. Is it possible one of you could send me an API token with the added SoundBar so I can use it for developing. I will not change anything or trigger any actions but just need to look what the API looks like. Otherwise it would be quite difficult to develop against a blackbox. Please don't post the token here but send it at the email address in my profile.

Hey guys. Sorry for late response - was quite busy the last weeks. Maybe I can find some time the next days. Is it possible one of you could send me an API token with the added SoundBar so I can use it for developing. I will not change anything or trigger any actions but just need to look what the API looks like. Otherwise it would be quite difficult to develop against a blackbox. Please don't post the token here but send it at the email address in my profile.

Email sent, let me know if you end up needing anything else.

Thanks @GreyAsteroid for providing your API token. I was able to implement some basic commands. But I was not really able to test them as I did not want to change anything on your device.
I have created a pre-release version of the plugin. Could anyone please check if the plugin does work as expected and let me know?

Thanks @GreyAsteroid for providing your API token. I was able to implement some basic commands. But I was not really able to test them as I did not want to change anything on your device.
I have created a pre-release version of the plugin. Could anyone please check if the plugin does work as expected and let me know?

Thanks for your work on this! I went ahead and got the pre-release version running and it seems the device shows up properly and can be turned on and off perfectly. The volume slider accessory is also working great. The only issue I've noticed is that input switching seems to be borked.
[smartthings-tv] [Samsung Soundbar Q70T] Error when executing setInputSource of capability samsungvd.audioInputSource: Request failed with status code 422: {"requestId":"6417037913242335142","error":{"code":"ConstraintViolationError","message":"The request is malformed.","details":[{"code":"NotValidValue","target":"commands[0].Command(component=main, capability=samsungvd.audioInputSource, command=setInputSource, commandId=null, arguments=[bluetooth])","message":"setInputSource is not a valid value.","details":[]}]}}
In case you'll find it helpful I've exported and attached the device attributes and commands.
Device Attributes.csv
Device Commands.csv
And regarding changes to the device, I currently have it in an empty guest room so any changes won't bother me.

Hello, is it possible to change the icon into a box so that you can distinguish it.

@GreyAsteroid I just had a look at changing input sources and it should work as expected now. Thanks again for your API token. I did create a new "real" release as I screwed things up with pre-releases. Please let me know if everything works as expected now!

@MrNoooooooob I (probably) found a way to deal with this as well. Soundbars are now published as set top boxes and therefore should have another icon as TVs. I also added a config property so you can select the icon you want to have for each device. Changes have been released as v2.3.0.


TIMESTAMP

I'd love a timestamp command so I could echo times to the log/user window I've set up. I'd want it to use computer system time, not the time in $gametime

whoops! Saw I've already requested this. Sorry!


reorganize passes directory

Since the passes are getting more and cluttered I started organizing them a bit, comments welcome.

It's probably easier to discuss this in a issue, before writing a PR. Anyway, here is a summary of the current view, if I'm understanding correctly (not implying that I agree):
Layout Selection (Placement)
passes/layout/

SetLayout
TrivialLayout
DenseLayout
NoiseAdaptiveLayout
CSPLayout
ApplyLayout
Layout2qDistance
EnlargeWithAncilla
FullAncillaAllocation

Swap Insertion (Routing)
passes/swap/

BasicSwap
LookaheadSwap
StochasticSwap

Basis Change
passes/basis/

Decompose
Unroll3qOrMore
Unroller

Optimizations
passes/optimization/

Optimize1qGates
Collect2qBlocks
ConsolidateBlocks
CXCancellation
CommutationAnalysis
CommutativeCancellation
RemoveDiagonalGatesBeforeMeasure
RemoveResetInZeroState

Circuit Analysis
passes/analysis/

Width
Depth
Size
CountOps
CountOpsLongestPath
NumTensorFactors
DAGLongestPath

Additional Passes
passes/utils/

CheckMap
CheckCXDirection
CXDirection
MergeAdjacentBarriers
BarrierBeforeFinalMeasurements
RemoveFinalMeasurements
FixedPoint
DAGFixedPoint

Maybe a short description for each category?

the category names should be pretty descriptive.
layout passes are responsible for choosing a layout of virtual qubits on physical qubits.
swap passes are responsible for inserting swaps.
etc.
The only thing I'm concerned about is when passes do not fall cleanly within one category, for example a pass that chooses both layout and inserts swaps (#2860 has examples of this i think). But I still think some sort of categorization is useful as the number of passes increase.

Maybe using a tree categorization?
passes/mapping/layout/<same content>
passes/mapping/swap/<same content>
passes/mapping/CheckCXDirection
passes/mapping/PassesDoingBoth

I agree that some sort of categorization is useful at this moment and have no concern on your proposing categorization.
The utils category would be useful for miscellaneous passes which may be categorized in future.
Just a small comment on directory name. I think routing would be slightly better than swap in the future.
Because we'd likely to have some routing passes which use N-hop CNOTs (Bridge gates) as well as SWAPs for resolving CNOTs on non-adjacent qubits (e.g. https://arxiv.org/abs/1907.02686) in the future.

@itoko ok i renamed to routing.
@1ucian0 we don't have such passes yet and i think their utility would be limited as they don't scale well. This is just a simple reorg, and I don't want to make it too complicated structurally yet. Once we get more passes in we can re-evaluate.

I think an important distinction is with passes running on "physical" circuits (after layout embedded) and virtual circuits (without an associated layout). We should include that info somewhere, not sure if in this reorganization...

I added release notes. The passes are accessible under the same namespace qiskit.transpiler.passes, deprecating their individual files is cumbersome and i'm not sure worth it.
The categorization of what is a physical vs. virtual pass is not clear-cut because optimization passes run on both.


Add upload_media_bytes

I found myself needing to upload media in memory (not from file on disk) so thought I'd take a bash at implementing this.
Not super happy with the design; ideally I wanted to have a generic upload_media method which took an AsyncRead reader, but the dyn trait stuff in generator seems to disallow this.
Also, the &[u8] having to be static is less than ideal!
Critique very much appreciated.

ideally I wanted to have a generic upload_media method which took an AsyncRead reader, but the dyn trait stuff in generator seems to disallow this.

I'm interested in why AsyncRead reader is not allowed in dyn, but maybe we can't remove dyn trait from generator. If you have any ideas to use AsyncRead for your ideal upload_media function, please let me know.


vim: add options

Looks good to me :+1: I just added a minor comment which you may or may not want to consider, feel free to merge whenever.

apologies if I already wrote anything about it (I really dislike the current nixpkgs vim configure system, yet no time to fix it), but if you are really interested going that deep into defining options, you might be able to automate it from https://github.com/neovim/neovim/blob/master/src/nvim/options.lua .

@teto I agree that makes sense to automate this part and reuse work made by neovim, but I don't think I will have the possibility to do this myself anytime soon. But thanks for the suggestion anyway.

This pull request has been rebased via git hub pull rebase. Original pull request HEAD was fd5bb1d974ee395a622decd73d41ccac72ea84d3, new (rebased) HEAD is a2e09b4c9dabdf3a4481c51091e472f433b4a0be


Provenance of AMFNetConnection.as and AMFBinaryData.as

AMFNetConnection and AMFBinaryData are ports from JS to AS of amf.js from https://github.com/emilkm/amfjs which is under ALv2.
If you dig through the history, you will find that the code originally came from r-amf, a project now stored at GoogleCode https://code.google.com/archive/p/r-amf/ which claims to be under a Category X license.
However, it was established in https://github.com/emilkm/amfjs/issues/17 that permission was granted to relicense the code under ALv2.

closing

Think this needs to be reopened as it not been resolved see [1]

<EMAIL_ADDRESS>


Allow Gorajan pieces to be reverted

🚀 Feature Proposal
Allow gorajan pieces to be reverted by getting rid of the nex item but returning 2 gorajan shards.
By deleting the nex item, it would prevent smithing experience to be abused.
This comes from no confirmation coming from the new /smith command and I made 4 gorajan occult helmets by accident.

#bso-vote this please.


Product endpoint not working proper when pass search string and category

endpoint : wp-json/wc/v3/products
consumer_key: ck_##############################
consumer_secret: cs_#############################
search:mdh
per_page:10
page:1
orderby:modified
order:desc
category:37
Above is the request parameter when I try to pass both category id and the search string i always get the blank list, I also cross-check that category ID 37 have items with MDH name
Please help me if anyone has a solution for this issue.
Thanks in advance.

Your code isn't specific, but you should note that category must be a string, not int. For example:
products = await wooCommerceCredentials.getProducts(category: "25");


Web Editor doesn't capitalize usernames properly, permissions per-user are not applied

Hey! First time user here, absolutely love the GUI! I am experiencing one problem though, when I use the web editor to modify my per-user permissions, they are not applied when pasting the edits. It shows in the editor "andrew1431" when it should be "Andrew1431" and the permissions fail. Using the command in game worked though, so I am using that for now! Hope this helps =)
Edit: Using the commands to give myself the permissions in game worked !

From what I know does it apply edits using the uuid and not the username.
Is your server in offline mode?

Server is online, just installed the plugin. I would have assumed it uses the UUID but that doesn't appear to be the case, because when I paste the command (And see the confirmation in game, it shows "Permissions added for 'andrew1431'" and as such does not apply). Using the command manually in game to give myself the OP command worked though (as Andrew1431)

Using Spigot (Well, PaperMC actually)

Okay I take it back, it looks like it keeps lowercasing my name, and I am completely unable to add permissions to myself without doing it one at a time via minecraft commands

Gah I don't really know what's happening. Do I have to reload something for changes to come in to effect? At this point I'm unsure where the bug lies, sometimes it works, sometimes it doesn't, so I'm going to close this for now until I can better understand what is happening.


Support for Cloudflare Workers

Allow us to support applications built on Cloudflare workers. There's a lot of useful data in the request context cf property we could make use of.

This is blocked by Connect RPC's requirement to construct a client with a baseUrl. We want to avoid reconstructing a client on each request to the worker.

Related: Connect doesn't work well on Cloudflare, see https://github.com/connectrpc/connect-es/issues/577

I spent a bit of time researching where we're at with support for Cloudflare workers.

This is blocked by Connect RPC's requirement to construct a client with a baseUrl. We want to avoid reconstructing a client on each request to the worker.

Seems there's a few reasons for this:

We want to load our WASM module into the worker outside of the request context so it can be instantiated once rather than on every request. This is why we recommend creating the Arcjet client outside of the request handler for our other adapters.
With https://github.com/arcjet/arcjet-js/pull/1201 we'd like to have a persistent connection to improve latency across requests.
The DX is better when you can define base rules in a client and then withRule any additional rules you might want to combine.

With Cloudflare's move from Service Workers to ES Modules, environment variables are no longer provided in the global scope. Instead, they're passed as a binding to the handler. Trying to access them as a global will error.
Also, creating the connect client requires a base URL, which we configure dynamically based on the environment variables.
Loading WASM
Cloudflare officially supports WASM in workers. They have some history with slow worker startup, but it seems they've implemented a fix for this. From 2020:

We found a way to enable V8’s Liftoff+Tier-up that we like. This should go out to production next week. I think it should cut Wasm startup time by a factor of 5-10. (This still doesn’t use code cache, which is a much bigger project that should cut Wasm startup time to almost nothing. No timeline on that yet, but let’s see how much Liftoff helps.)

It would be interesting to test the startup time of our WASM Module. They must be instantiated in the global scope outside of the handler, which implies some optimization may be going on.
There is also a worker size limit of 1MB for free plans, 10MB for paid plans.
Persistent connections
Cloudflare doesn't support persistent outbound connections so we don't get any benefit here.
You can see in the examples for databases, they create a new connection within the workers handler, then it closes after the request ends.
Given this, we could avoid our usage of the dynamic baseUrl and use a static URL when in the workers environment.
I assume we'd use the fetch client from Connect: https://github.com/connectrpc/connect-es/issues/577#issuecomment-1503185372
Did I miss anything or get anything wrong?


Bring reusable variables out of while loop

In Viewport _process_picking reusable variables for 3D collision object input detection, are declared inside while loop, so their values are re-set on each cycle. These variables used to be declared outside the loop but changed by #50147

Thanks!


HTTP/2 Priority Tree Management

We are currently removing streams from the priority tree as they are closed (maybe subject to a stream removal policy which is being removed as part of https://github.com/netty/netty/issues/3448).  However we should not remove streams from the priority tree at least until they have no dependencies which are in states eligible for data transfer (i.e. OPEN, HALF_CLOSED, ...), or may be eligible for data transfer in the future (i.e. IDLE).

@nmittler - FYI.

We associate priority with the flow control window.  Therefore we rely on both peers sharing a common view of the priority tree.  However there seems to be some confusion (on my part or in the spec) with how to provide feedback when we don't accept a priority frame.  We can't rely upon sending a RST_STREAM to the other end because in section 5.1:

Endpoints MUST ignore
WINDOW_UPDATE or RST_STREAM frames received in this state, though
endpoints MAY choose to treat frames that arrive a significant
time after sending END_STREAM as a connection error
(Section 5.4.1) of type PROTOCOL_ERROR.

Some thought is needed (perhaps when I'm not so tired) as to how we can maintain the priority & flow control association and keep the peers in sync.
For example say stream X is closed, and it has no children.

We remove it from the priority tree.
Later our peer sends a priority frame for stream X.
What do we do:

Should we have been keeping track of stream X's window? (it can't be controlled via WINDOW_UPDATE frames at this point)
Should we ignore it? - What does that say about our windows throughout the tree?

I'm working on a PR for this.  I think I was confused in my late night thought process :)  The window of the individual node doesn't particularly matter because we are considering how much the whole subtree wants to send, and any individual node which is not eligible to send will not contribute to this number.

ignored :)

@nmittler - Humm this didn't get auto closed like we had hoped...closing manually.

@Scottmitch hmm ... maybe updates don't count and the original description has to have the "Fixes: " text?

@nmittler I wonder if a link has to be in the git commit too?

@Scottmitch ah yeah that would make sense.


X86 very early console does not work on PCIe exposed UART port

Describe the bug
Enabled by CONFIG_X86_VERY_EARLY_CONSOLE, it enables early output, even before the kernel starts.
It works well on qemu_x86/qemu_x86_64 which anyway only exposes ultra old legacy IO port as serial console. (it is possible to expose pci based one, which anyway export the registers on a IO port instead of memory. And, so far I could not get the chardev to use such uart ... So no possibility to test this current bug on qemu)
Without it, it's much harder to debug some targets.
early console's code seems legit however, and I have seen it working in the past on the same targets...
To Reproduce
Build any sample for intel_ehl_crb (for instance) with CONFIG_UART_CONSOLE=n and CONFIG_X86_VERY_EARLY_CONSOLE=y
Expected behavior
serial output should happen.
Impact
It's much harder to debug such targets.

Here are some reasons that I can think of:

PCIe location is wrong that UART2 is not at BCD(0, 0x19, 2).
Pinmux?
** I know of some BIOS which can change the pin functions.
Power management?
IP block ownership?

I have applied the following hack to enable PCIe early console on QEMU and it is working fine without issue:
diff --git a/arch/x86/core/early_serial.c b/arch/x86/core/early_serial.c
index 53fb8af7e3a..f14ffaebf75 100644
--- a/arch/x86/core/early_serial.c
+++ b/arch/x86/core/early_serial.c
@@ -11,11 +11,17 @@
 #include <soc.h>

-#if DT_PROP_OR(DT_CHOSEN(zephyr_console), io_mapped, 0) != 0
+//#if DT_PROP_OR(DT_CHOSEN(zephyr_console), io_mapped, 0) != 0
 #define UART_IS_IOPORT_ACCESS 1
-#endif
+//#endif
+
+#define X86_SOC_EARLY_SERIAL_PCIDEV PCIE_BDF(0, 0x02, 0)

-#if defined(UART_IS_IOPORT_ACCESS)
+#if defined(X86_SOC_EARLY_SERIAL_PCIDEV) && defined(UART_IS_IOPORT_ACCESS)
+static uint32_t io_port;
+#define IN(reg)       sys_in8(reg + io_port)
+#define OUT(reg, val) sys_out8(val, reg + io_port)
+#elif defined(UART_IS_IOPORT_ACCESS)
 /* Legacy I/O Port Access to a NS16550 UART */
 #define IN(reg)       sys_in8(reg + DT_REG_ADDR(DT_CHOSEN(zephyr_console)))
 #define OUT(reg, val) sys_out8(val, reg + DT_REG_ADDR(DT_CHOSEN(zephyr_console)))
@@ -90,18 +96,21 @@ int arch_printk_char_out(int c)

 void z_x86_early_serial_init(void)
 {
-#if defined(DEVICE_MMIO_IS_IN_RAM) && !defined(UART_IS_IOPORT_ACCESS)
-#ifdef X86_SOC_EARLY_SERIAL_PCIDEV
+#if defined(X86_SOC_EARLY_SERIAL_PCIDEV)
        struct pcie_bar mbar;
+
+#ifdef UART_IS_IOPORT_ACCESS
+       pcie_get_iobar(X86_SOC_EARLY_SERIAL_PCIDEV, 0, &mbar);
+       io_port = mbar.phys_addr;
+#else
        pcie_get_mbar(X86_SOC_EARLY_SERIAL_PCIDEV, 0, &mbar);
        pcie_set_cmd(X86_SOC_EARLY_SERIAL_PCIDEV, PCIE_CONF_CMDSTAT_MEM, true);
        device_map(&mmio, mbar.phys_addr, mbar.size, K_MEM_CACHE_NONE);
-#else
+#endif
+#elif defined(DEVICE_MMIO_IS_IN_RAM) && !defined(UART_IS_IOPORT_ACCESS)
        device_map(&mmio, X86_SOC_EARLY_SERIAL_MMIO8_ADDR, 0x1000, K_MEM_CACHE_NONE);
 #endif

-#endif /* DEVICE_MMIO_IS_IN_RAM */
-
        OUT(REG_IER, IER_DISABLE);     /* Disable interrupts */
        OUT(REG_LCR, LCR_DLAB_SELECT); /* DLAB select */
        OUT(REG_BRDL, 1);              /* Baud divisor = 1 */
diff --git a/arch/x86/core/prep_c.c b/arch/x86/core/prep_c.c
index 4ff5ffcdc7e..86702e59c29 100644
--- a/arch/x86/core/prep_c.c
+++ b/arch/x86/core/prep_c.c
@@ -63,6 +63,12 @@ FUNC_NORETURN void z_prep_c(void *arg)
         */
        arch_printk_char_out('\n');
 #endif
+
+       arch_printk_char_out('\n');
+       arch_printk_char_out('\n');
+       arch_printk_char_out('\n');
+       arch_printk_char_out('\n');
+       arch_printk_char_out('\n');
 #endif

 #ifdef CONFIG_X86_STACK_PROTECTION
diff --git a/boards/qemu/x86/board.cmake b/boards/qemu/x86/board.cmake
index 660a07fae31..2b0565c7f99 100644
--- a/boards/qemu/x86/board.cmake
+++ b/boards/qemu/x86/board.cmake
@@ -66,6 +66,7 @@ set(QEMU_FLAGS_${ARCH}
   -cpu ${QEMU_CPU_TYPE_${ARCH}}${QEMU_CPU_FLAGS}
   -machine q35
   -device isa-debug-exit,iobase=0xf4,iosize=0x04
+  -device pci-serial,chardev=con
   ${REBOOT_FLAG}
   -nographic
   )

GDB verified that the the IO bar was obtained correctly, and it was using the IO port for serial out. So it seems things are working in general. Closing for now. Re-open if it is still an issue.


Search-related issues

Tasks:

[ ] add tests for basic search
[ ] add tests for each flag
[ ] sort all

Issues:

[ ] #485
[ ] #486

moved to #495


feat(store): 2224 generator to fallback to application modeler keytar

Fallback to loading keytar from the Application Modeler extension node_modules folder (e.g. .vscode\extensions\sapse.sap-ux-application-modeler-extension-1.14.2\node_modules\keytar) if it cannot be loaded.

Successfully tested locally by deleting the node modules keytar

It seems that @Klaus-Keller's questions weren't fully addressed:

Are we sure we want to create this indirect dependency from @sap-ux/store to the Visual Studio Code extension, Application Modeler? Where is this being consumed from?
Proposal: In the module @sap-ux/store, we could allow passing the path to a location where the keytar module with binaries can be found. The consumer would then be responsible for the search, avoiding the need for this low-level module @sap-ux/store to search for the VSCode extension on the file system.

Introducing this dependency couples the low-level library to the presence of the Application Modeler extension. Could you clarify where this is consumed? The pull request description is quite sparse and doesn't explain the motivation behind this change.
Additionally, this change seems to introduce a fallback to the Application Modeler's copy before attempting to use VSCode's copy. There may be valid reasons for this, but without further explanation, it's difficult to understand the rationale.


Doe tensorflow has api  similar to pytorch's “masked_fill_”

pytorch has squeeze , tf also has squeeze.
pytorch has unsqueeze, tf has expand_dims do the same thing with diff name.
pythorh has masked_fill , tf has ?
Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using):  2.2.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
masked_fill_ api doc in pytorch
Will this change the current api? How?
Maybe not. It will add a new api.
Who will benefit with this feature?
someone try to migrate from pytorch to tensorflow like me.
Any Other info.

@jason-liew
Can you please go through tf.boolean_mask and see whether you are looking for similar functionality.Thanks!

No,it's different.
tensorflow:
 t1 = tf.constant([1,2,3])
 t1_mask = numpy.array([1,0,1])
 tf.boolean_mask(t1,t1_mask) # [1, 3]

pytorch:
p1 = torch.tensor([1,2,3])
p1_mask = torch.tensor([1,0,1])
p1.masked_fill_(p1_mask,5) # [5, 2, 5]

@jason-liew
Got it.Thanks!
Are you interested to submit a PR?

@gowthamkpr Hi, I would like to work in this can you help with how and from where I can start ?

@gowthamkp Should we have to add a new api or we can also override boolean_mask with one more parameter which one will be better?

Strawman proposal. Can this be implemented as
def masked_fill(t, mask, value):
return t * (1 - tf.cast(mask, tf.float32)) + value * tf.cast(mask, tf.float32)
Might have to do some dtype handling but roughly should work? What are the performance requirements for this?

@ravikyram @gowthamkpr please review this PR #41975

tf.where([True, False, True],5,[1,2,3])

We recommend the tf.where implementation.


Code improvements

thanks @severedsea

FYI occasionally, build will get stuck because the databases somehow remain inaccessible 🤷♂


sendmail on site

Is your feature request related to a problem? Please describe.
add a possibility to the site to send email (after registration, pwd lost, activation link, ...)
Additional context
smtp info is already set in DB by admin page

phpmailer add and test with information from db
test send mail ok
need to add contact.php
actually put a auto test send mail

create a test mail setting page in admin
start to create a contact.php but need recheck (email forward problem or phpmailer or HP code ????)
when ok but create a recovery password by mail
+
activation link send at signup (manageable by admin for enable or disable the feature


Resource url hash

Description
Add expanded resources from the resource tab to the URL bar and fix the graph links on the resource page.
Motivation and Context
Now that we have the luxury of the task list and graph tab states being stored in the URL, I wanted it on every page. I like to refresh the resource page a lot and always need to re-expand the resources I'm interested in. Not anymore! I also updated the graph links in the expanded resource boxes so they actually work again.
Have you tested this? If so, how?
Ran this locally and in production. I'm willing to add unit tests if possible.

Awesome! :)


Alamofire 5: Empty Response Refactor (2nd Refactor)

This PR refactors the empty response refactor to move the logic all into the ResponseSerializer protocol and protocol extension. This change DRYs up the code and exposes all the functionality in a more convenient way for custom ResponserSerializer types.
I also removed the AnyResponseSerializer type since it no longer appears to be in use. Forgive me if this is not the case.

My only concern with placing all of this under the ResponseSerializer protocol is that, if users don't want conformance with one or the other of the protocols, they lose the functionality. But if this is mostly for us, then yes, this looks good.

I'm going to merge and then build off of this, as I think there are a few bits to improve.

Cool refactor!!Great design


Service implementation

Revisit Twirp::Service implementation

Add a few validations.
Error responses for bad_route: invalid HTTP method, invalid rpc method and invalid Content-Type.
Simplify Rack handler: the Service instance implements call which makes it a Proc that can be used itself as Rack middleware (no need for .rack_handler method).
Handle Twirp::Error responses
Handle Hash attributes to build the response object (no need to explicitly mention the response class in the handler)
Rename "impl" to "handler".
Add basic service test
Fix issue with @@class_vars when defining multiple services (@@rpcs = {} would be shared across every class that inherits from Twirp::Service, essentially it is a global).

@cyrusaf note that this breaks the current example. I'll fix it as soon as we merge this and I will add many tests to the service_test file

Thanks for doing this it looks really nice. All the type assertion really makes me miss Go, but it will be awesome to have a working ruby server. Do you want to merge this in now and keep adding to it with other PRs?

Ruby makes you miss static typing of course, but we will be able to pull off a very intuitive DSL that reports very nice error messages when used wrong. It's always a tradeoff 😄
Yes, I'll merge this in master. Now that we resolved some design questions I'll continue some development straight in master to go faster.


MS Graph API Certificate Issue

I use the MS Graph API to connect with my Teams Chat, but currently the certificate will not be approved and I get following error: {"error":{"code":"ValidationError","message":"HttpRequestException:An error occurred while sending the request. WebException:The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. AuthenticationException:The remote certificate is invalid according to the validation procedure. ","innerError":{"date":"2024-09-30T16:24:35","request-id":"ff84c630-4449-4c5e-858c-4ba3ffb85b03","client-request-id":"ff84c630-4449-4c5e-858c-4ba3ffb85b03"}}} Maybe you can help me? I already change my certificate, but it does not work.

Hi @ACA1993 ,
This seems to be a service issue. Please share this on https://aka.ms/askgraph where the appropriate team will be able to provide further assistance


Suggestion: Automatically publish new versions (tagged commits)

FYI: If you are OK with automation, you can setup a GitHub action to publish on both open-vsx and vscode marketplace.
Example to publish on each new tag:
https://github.com/badetitou/vscode-pharo/blob/main/.github/workflows/publish.yml
A more detailed example:
https://github.com/HaaLeo/vscode-timing/blob/master/.github/workflows/cicd.yml#L1
The instructions of the action are here:
https://github.com/HaaLeo/publish-vscode-extension
How to make a secret:
https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository
(credit to @badetitou for the idea https://github.com/rjmacarthy/twinny/issues/71#issuecomment-1927084174)

@rjmacarthy would you like to me look into it and help? Maybe having a external self-hosted runners so it wouldn't take your credit and building it a container image so swapping between self-hosted runners or GH-hoseted runners would be easier?

Hey @AntonKrug sure if you are able to help that would be great.  I was going to tackle this when the monthly credits roll over. I think we can stick with github actions for now, perhaps with push to main / master branch and will develop against dev branch in the future and merge for releases.
Many thanks,

I updated this now so that commits to main branch will trigger deployments.  The development branch will be used for tracking pre-release status.  I am having issues generating a token on OpenVSX right now but I opened an issue for it.
https://github.com/eclipse/openvsx/issues/866

This is now completed and working on pushes to main.  Thank you for the suggestion and help.


Milestone 2 feedback

Dear group 11,
You guys have made improvements! Great job! Below highlight some feedback for milestone 2. In addition, things under Suggestions: should be taken as suggestions and do not affect your mark.
Writing an analysis that uses multiple scripts: Mechanics
Comments
Your workflow is a bit odd, such that EDA happens after your ML analysis. This is no longer exploratory.
Writing an analysis that uses multiple scripts: Viz
Comments
I like the spacing and the figure captions
Expectations: Mechanics
Comments
Arushi only has two commits, should be more equal in terms of each team member's commits.
Project organization and documentation expectations: Reasoning
Comments
" Our model performed fairly well on test data set with the f1 score being ~0.53." is not entirely convincing. In general, give a well or bad assessment more objectively.
There are no references for README.Rmd
Please define "default payment" what is it? (I'm not a banker) I thought defaulting meant going bankrupt (so I can't make any payments)
"most features show very little overlap" I disagree; many distributions look almost identical
Fig 5 is referred to as Fig 3; it is not clear to me which are the best hyperparameters
Suggestions:
Files don't all have to have 'credit_default' in the name (probably better if they don't)
Overall good work in making the analysis, but mind the interpretation of your values. Also, explain your metrics in layman's terms for the public.
Submission expectations: Mechanics
Comments
Why are there two readme-files in the root directory?
Overall great job!

Hi @andytai7,
Thank you for your feedback and we will work on making the changes you mentioned.
I just wanted to clarify one point about the Readme, you mentioned that we didn't include reference in our Rmd file, but we mention our references in the .bib file and that file is also mentioned in our Rmd at top. The references render in our Readme.md file.  Would request you to reconsider or elaborate more on this point. Thank you!

Hi @Arushi282,
I would suggest adding the list also in the RMD file.
Best,
Andy

Hi @andytai7 ,
Thank you very much for the response. We will definitely work more on that.
To elaborate a little more about ReadMe, we used readme.Rmd for rendering our .md file, because we are getting the results, such as f1 score, from the model, thus we need to render in order to see the values.
That is why we have two files in our repository, one .md for people to read, and one .Rmd to see where the results are coming from. As for the bibliography, bibliography was used to make sure the formatting of the text in BibTex format is correct.