Fix kubernetes code gen

Currently the code generator script is failing, preventing new contributions to make changes in the CRD.

Maybe update-codegen.sh shouldn't do "rm -rf "$TEMP"" at the end?

Hi @amandahla :wave:
Thank you for taking the time to check this, that would allow the verification script to work again :+1:
But I think we'll need to go a bit deeper and improve this process. We don't have much documentation about it and we could automate a few things, for example, the full procedure is:

Vendor dependencies go mod vendor
Grant executable permission to code-generator chmod +x vendor/k8s.io/code-generator/*.sh
Run the update/verification ./hack/update-codegen.shand ./hack/verify-codegen.sh

Probably reducing a few steps and adding this to the Makefile could be a better approach. :robot:
Also we need to add a note about backward compatibility in the docs, changes to generated-code would likely represent changes to CRDs and a brake all previous installations :memo:

Totally agree @lucasmdrs
Can I help with this issue?

[ ] Update docs
[ ] Automate procedure using Makefile

Yes! Any contribution on this topic is much appreciated :pray:

@amandahla I'll be working on this next week
I'll review your changes and add some checks to our workflows for this too.
Hopefully that will unblock some of the PRs we have that change the CRD like  #225 and #209


Support https connections for Triplestore integrations

Resolves: https://jira.duraspace.org/browse/FCREPO-2087

@dannylamb forgot to mention -- this is a PR related to the one you just merged. The fcrepo-camel-tests module is just a project that uses pax-exam to test the deployment of these artifacts in an OSGi (i.e. Karaf) container.

@acoburn I'd do it for you, but I don't have write access to this repo :(

@dannylamb you should have access now. Thanks!


feat(tutorials): Each command in a separate “code snippet”

What
The E2E adopter Journey tutorials provides plenty of commands which need to be executed. Currently, more than one commands are in a code snippet section.
command 1
command 2

This should be changed. One command per code snippet section.
command 1

command 2

Why
This makes it more readable and also usable, because the copy paste functionality can be used

Will be closed by #570 , done by @awellnitz-materna


Id Provider ignores flag

Hi,
Got my plugin set up as follows
resourceprovider {     packageName = <appId>     generateIdProvider = false     generateIntegerProvider = false     generateDimenProvider = false     generateColorProvider = false     generateDrawableProvider = false }
Since I only use resource provider for strings, but i'm getting IdProvider generated as well, and i'm guessing it's part of the reason why my project is building so slowly.

Fixed in https://github.com/Comcast/resourceprovider2/pull/9, available in v1.3.3


Support for scripts with unicode content

Summary of changes
Makes the _to_ascii() function able to handle script's contents in unicode format.
Closes #761
Pull Request Checklist

[x] Changes have tests
[x] News fragment added in changelog.d

@pganssle fixed


remove incorrect information about ADP status

https://github.com/CVEProject/cve-schema/blob/30f59c7de92fbc77bddade302601cb500c66f718/README.md?plain=1#L5
This conflicts with the information at https://github.com/CVEProject/cvelistV5/blob/main/README.md in which downstream users are expected or required to parse the adp property tomorrow.

This language was fixed in https://github.com/CVEProject/cve-schema/commit/86a0d6b318b67aa12bb9b2002ed4b91db6abc5d8


AWS Govcloud Cloudtrails will not connect to Azure Sentinel until late June/Early July

Documentation should reflect that you can only connect your AWS Commercial Cloudtrail to Azure Sentinel at this time. AWS Govcloud Cloudtrails will not connect per the instructions on this page. Microsoft engineers confirmed this via support ticket and said Govcloud connection should be available by late June early July.

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

ID: 56d2c45b-3003-3455-d61d-4f2878d8d5cc
Version Independent ID: 0332f921-3051-eebb-e9a1-1046c24da921
Content: Connect AWS CloudTrail to Azure Sentinel
Content Source: articles/sentinel/connect-aws.md
Service: azure-sentinel
Sub-service: azure-sentinel
GitHub Login: @yelevin
Microsoft Alias: yelevin

Hello @drewberrymore, thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you soon.

@drewberrymore, we have made these changes in the doc. Pls expect them to reflect soon. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update cuttle to 1.1

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Thank you for the contribution. It was merged directly as 18aa83dc0edf66291186825dbe58d82e505751a6. Your contribution is still credited to you.


Draftail (rich text editor) - using cmd + left arrow to navigate to the start of the line is broken in Firefox

Issue Summary
I used the Rich text editor for a large amounts of editing links this week and found some very frustrating behaviour with cmd + left arrow interaction.
When there is an inline element (e.g. a link), it is impossible to navigate to the start of the line in the way that works in every other text editor I have used.

cmd + left arrow should navigate to the start of the line.

Instead - this moves the scroll position to the start of the page and loses the focus of the current editor

cmd + shift + left arrow should highlight from the current position to the start of the line

Instead - this does nothing

Oddly the behaviour to the end of the line works great, cmd + right arrow moves to the end of the line & cmd + shift + right arrow selects the text from the current position the end of the line.

Steps to Reproduce

Ensure you are running this in Firefox & on macOS
Load any Wagtail instance with Rich text in use - e.g. the nightly build https://wagtaildemo-nightly.herokuapp.com/admin/pages/64/edit/
Add a link to the Page Body in a rich text block
Using the keyboard only, navigate to the end of the link
On your keyboard, click cmd + left arrow to move to the start of the line
Expected: Cursor moves to the start of the line
Actual: Page scrolls up

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

Technical details

Python version: 3.9
Django version: 4.1
Wagtail version: Tested on 3.0 and on 4.1a (in dev) and issue is present in both
Browser version: Firefox 105 on macOS 12.3

Manual testing

Shortcut
Expectation
Browser
Behaviour

⌘ + ⬅
Navigate from end position to the start of the line
Firefox
❌moves up the page

⌘ + ⬅
Navigate from end position to the start of the line
Firefox
❌ moves up the page

⌘ + ⬅
Navigate from end position to the start of the line
Safari
✅ moves to the start of the line

⌘ + ⬅
Navigate from end position to the start of the line
Safari
✅ moves to the start of the line

⌘ + ⬅
Navigate from end position to the start of the line
Chrome
✅ moves to the start of the line

⌘ + ⬅
Navigate from end position to the start of the line
Chrome
✅ moves to the start of the line

Recording
https://user-images.githubusercontent.com/1396140/195788713-debcf350-0299-4620-ae30-e6c1e795e6d2.mp4

I will be great if you assign me to this @lb-

@Dev-Yusuf we don't really assign issues outside of the core team.
I encourage you to first try to reproduce the problem and confirm it exists, from here maybe have a look at the code and see if you think you know what the issue could be.
After that you may be able to a PR to fix it, if so, just add a comment that you're working on a fix.
Also, I am not sure if this can even be fixed in Wagtail's code, it may be a Draftail issue or even a Draft.js issue. I did search those repos but we may end up moving this bug to a different project.

Hi @lb-  While comparing results on both the Chrome and Firefox browsers, I was able to establish that the problem still exists.
I'm not sure if @Dev-Yusuf  is still tackling the problem or if I may take over.
https://www.youtube.com/watch?v=mWpgbmxRZqg

i didn't experience this issue testing on linux and on firefox. So i don't think it still exist on firefox, don't know if its more of an issue on a specific OS platform though

This appears to be working for me on Wagtail 6.3/6.4a - I am not sure what could have fixed it though.
I am happy to close this now and if anyone else can reproduce the issue we can re-open.


Feature/#438 handle status updates part 2

transfer OutputFiles from ExtractionOrder to Exports
Reviewed by

[x] @hixi

connected to #438

don't merge for now (see https://github.com/geometalab/osmaxx-frontend/pull/452#discussion_r61260025)

replaced by #455


When someone uses channel points to request a reward no text appears in chat, like in Twitch chat.

Describe the bug
So this is purely missing text, not the feature I am reporting. So someone uses Twitch channel points to request me to do something like eg 'Hydrate". In Twitch chat client the text appears in the chat telling me to do the request reward. In Chatterino nothing pops up in chat.
To reproduce
-User requests reward through their Twitch interface
-I don't see request in chat through Chatterino

Chatterino version
Chatterino 2.1.7 (commit 845c8fa63)
Operating system
Windows 10 pro

Not a bug, missing feature. This is being worked on iirc, maybe it has been merged already. Please check the latest nightly release. The latest stable release(2.1.7) is quite outdated.

This functionality was recently added in nightly when this pr got merged, you should try it first.

Perhaps related to this. Seeing the below messages:
Invalid point event type: redemption-status-update
Invalid point event type: custom-reward-updated
These appear to be coming from row 1141 in src/providers/twitch/PubsubClient.cpp with build Chatterino 2.1.7 (commit 36dd640cd)
The resulting chat log messages are empty except for the timestamp

Not a bug, missing feature. ~This is being worked on iirc, maybe~ it has been merged already. Please check the latest nightly release. The latest stable release(2.1.7) which you are running is quite outdated.

Hi, thank you for responding so quick.

It works on the nightly build. Keep doing an awesome job!

Perhaps related to this. Seeing the below messages:
Invalid point event type: redemption-status-update
Invalid point event type: custom-reward-updated
These appear to be coming from row 1141 in src/providers/twitch/PubsubClient.cpp with build Chatterino 2.1.7 (commit 36dd640)
The resulting chat log messages are empty except for the timestamp

Just fyi:
These events are currently not processed because they do not contain the actual reward data.
These events instead update the cost and text for existing rewards if they are changed by the streamer.
Currently if there was a reward redeemed the text and cost of the reward will stay the same while the channel is open in chatterino without ever updating.
Updating existing rewards based on these events is something I'll probably work on in the near future.

this is fixed in the latest version


chore::> Change input type of SignInvokeTransaction, SignDeployAccountTransaction, and SignDeclareTransaction

For issue #590
This PR will Solve #590 pointer 2

Also, the code is failing in some CI test

As discussed internally, we'll need first to create a function to calculate the class hash of legacy contract classes. It'll be done soon


Not allowed to load local resource: file:///android_asset/www/index.html

I am trying to build this on OSX for Android. I am able to run the latest version v2.0 beta 10 on dev server. But when I ran it with Android phone or emulator, I got an File Not Found error. It couldn't find the index.html file.

I checked the  apk file. It is actually there. Below is the debug info from Chrome.

Not allowed to load local resource: file:///android_asset/www/index.html
I am new to mobile app development and have googled around for hours to fix this. So please bear with me if the answer is obvious.

rm -rf platforms/ plugins/ && npm run restore && npm run android
Try reinstalling the app and let me know

Reinstalling the app did the trick. It works now.


As a user, I want to be able to start a service multiple times

this is a new requirement which was discovered for the prysm validator node:
"Each validator represents 3.2 Goerli ETH being staked in the system, so you can spin up as many as you want to have more at stake in the network"

Related: https://github.com/ethereum/grid/issues/245 item number 8.


neotest: Provide the ability to write any values in the tested contract storage

Context
I try to test migration of contracts' storage items using framework provided by neotest package. Sometimes contract stores items within its methods, so technically I could just call exact method. The inconvenience is that such elements are stored in the contract as a result of API methods that are not always easy to call within the test due to the need to follow business logic. At the same time, I did not find other ways.
Proposal
Add functionality to neotest package which allows to directly write key-value item into the contract storage.
Possible solution
The least affecting approach I thought about is to add analogue of<EMAIL_ADDRESS>func CompileContractWithDirectStorageAccess(/*same as CompileFile*/) (writeMethod string)

which, after reading the source code of the contract (but before compiling), adds direct-write method for the life of the test contract. You can call this method later like any other one.
func AnyFreeName(key, value []byte) {
  storage.Put(storage.GetContext(), key, value)
}

Changing contract on the fly is not a good idea, we're supposed to compile/deploy them exactly. Currently it's possible to use custom stores for chain.NewSingleWithCustomConfigAndStore() and chain.NewMultiWithCustomConfigAndStore where you have a complete storage API (seems like you're already doing it). But as you know underlying store may be a bit outdated compared to the internal Blockchain memory cache. Blockchain is specifically designed to never expose its memcache/DAO, but we may think about some specific hooks for tests, that I think will be safer and more appropriate way to handle this problem.

think about some specific hooks for tests

Ofc test hooks in core lib would be much better than contract surgery.

Here's a workaround suggested by @roman-khimov for the case here when you just want to add contract with some data in advance.
	lowLevelStore := storage.NewMemoryStore()
	_dao := dao.NewSimple(lowLevelStore, false, true)

	nativeContracts := native.NewContracts(config.ProtocolConfiguration{})

	err := nativeContracts.Management.InitializeCache(_dao)
	require.NoError(tb, err)

	err = native.PutContractState(_dao, &_state)
	require.NoError(tb, err)

	// store values in lowLevelStore

	_, err = _dao.PersistSync()
	_, err = cachedStore.PersistSync()

	// init blockchain
	useDefaultConfig := func(*config.Blockchain) {}
	blockChain, alphabetSigner := chain.NewSingleWithCustomConfigAndStore(tb, useDefaultConfig, lowLevelStore, true)

However, it is worth noting that after that contract invocations fail with contract not found exceptions. https://pkg.go.dev/github.com/nspcc-dev/neo-go/pkg/core#Blockchain.GetContractState returns nil, but https://pkg.go.dev/github.com/nspcc-dev/neo-go/pkg/core#Blockchain.GetContractScriptHash works.

Please try
blockChain, _ := chain.NewSingleWithCustomConfigAndStore(tb, useDefaultConfig, lowLevelStore, true)
blockChain.Close()
blockChain, alphabetSigner := chain.NewSingleWithCustomConfigAndStore(tb, useDefaultConfig, lowLevelStore, true)

Yeah, it's weird. But otherwise management contract's cache is not really initialized, because we're starting with an (almost) clean DB, it's inited for the genesis and that's it.

Please try

It really works. The only thing I also needed to do is to make no-op Close method of the storage.Store passed on the first init. Without this, blockChain.Close reset underlying maps.


Navigation does not work

Issue Type: Bug
Update the VSCode to the latest version.
Try to use CMD + click to navigation to the function definition.
Nothing happens, it stays on the same line.
VS Code version: Code 1.33.0 (0dd516d, 2019-04-04T15:14:28.026Z)
OS version: MacOS Mojave (10.14.3)
No Extensions.

What language are you using?
/needsMoreInfo

@mjbvz TypeScript (+React). Looks like, if I wait long enough it will finally open the file, but it takes like 10+ seconds.

Duplicate of #71751
See https://github.com/Microsoft/vscode/issues/71751#issuecomment-480126916 for workarounds
@alexpermyakov If that doesn't solve the issue for you, please let me know


eco_lite_rgb_16F_kinetics_v3.pth.tar is not in BaiduYun

Hi @zhang-can , thank you for your work! I can't access to Google Docs, so could you please upload the latest pretrained model eco_lite_rgb_16F_kinetics_v3.pth.tar on BaiduYun?

Hi @zhang-can , thank you for your work! I can't access to Google Docs, so could you please upload the latest pretrained model eco_lite_rgb_16F_kinetics_v3.pth.tar on BaiduYun?

你好，请问你的这个问题解决了吗，我现在从云盘下载还是显示数据损坏。


Document general policy on the use of long-form answers

Long-form answers are hard to analyze and interpret. We should prefer multiple-choice answers whenever possible with the option of a free form "other" answer.
Whatever our policy ends up being, we should document it.

Some questions are necessarily to be open and long form, when a multiple-choice + "other" are not enough. I am not sure we can codify this into a policy, I think it comes down to the topic of the question:

multiple-choice are better suited when we think a defined set of answers covers enough surface ("which version of Rust do you use?"). This helps a lot speeding up parsing.
open and long form are better when we don't want to suggest the solution, show an implied bias or when we want to leave freedom of expressing ideas on multiple axis. Sometime you can use the "other" option an an catchall for this.

Hope this qualifies as a "policy" :slightly_smiling_face:


Add cov report to default pytest settings

Codecov Report

Merging #164 (ebe9151) into main (a1bcbe0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #164   +/-   ##
=======================================
  Coverage   90.53%   90.53%
=======================================
  Files          10       10
  Lines         835      835
=======================================
  Hits          756      756
  Misses         79       79

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 a1bcbe0...ebe9151. Read the comment docs.


aj/refac

I think I just need to fix CI to not run both, but it passed for the push here https://github.com/anandijain/CellMLModelRepository.jl/pull/6/checks?check_run_id=2326004012 so I'm merging


Update kindle (:latest)

We are transitioning to version downloads were possible. Is this no longer available in such a way?

Sorry, I didn't know the rules, and amended the commit. Thanks.

Sorry, I didn't know the rules

No worries. It’s a recent change.


Classpath conflicts between multiple instances of ScalaInterpreters

I have multiple instances of ScalaInterpreters in my custom kernel. I'm using SparkSession inside and for each interpeter i use the following startup code:
import org.apache.spark.sql._
val sparkSession = {NotebookSparkSession.builder()
.master("loca[1]").getOrCreate()}

I start my kernel with option specificLoader=false to share same instance of sparkContext and everything works fine, but from time to time (same code might work or throw an exception) I see serialization errors from spark and i believe it is related to classpath loader.
java.lang.ClassCastException: cannot assign instance of java.lang.invoke.SerializedLambda to field org.apache.spark.rdd.MapPartitionsRDD.f of type scala.Function3 in instance of org.apache.spark.rdd.MapPartitionsRDD

If I start my kernel with  specificLoader=true I don't see this error at all, but every interpreter creates a new instance of sparkContext, which I want to avoid.
My test code is the following:
val sc = sparkSession.sparkContext
val rdd = sc.parallelize(1 to 100, 10)
val n = rdd.map(_ + 1).sum()

I'm not sure I understand what you're trying to achieve: you have a custom kernel, using ScalaInterpreter, and you're trying to have it act like multiple kernels at once, all sharing the same SparkSession, right?
If that's the case, one issue I see is that each instance of ScalaInterpreter will set spark.repl.class.uri in the spark conf. I'm not sure which one spark will retain at the end, but only one of them will likely be accessible. Parts of the logic of ammonite-spark should be customized, so that only one such server is spawned for all the sessions.
Another problem you'll likely run into (I see you aluded to it on the Ammonite gitter) is that the ScalaInterpreters will generate classes with similar names (like cmd1, cmd2, etc.), which is going to be a problem from the spark executors, which won't be able to distinguish between the classes of the various interpreters. That may require some customizations in Ammonite… (to put all classes of a session in a custom package for example).

I'm not sure I understand what you're trying to achieve: you have a custom kernel, using ScalaInterpreter, and you're trying to have it act like multiple kernels at once, all sharing the same SparkSession, right?

Almost, same SparkContext. I have a custom kernel and it creates new ScalaInterpreter with it's own stream for each new Notebook SessionId.
I actually found where the issue is with this ClassCastException, but don't know how to solve it yet.
Looks like Spark is using the classLoader where the context has been created at first place for all serialization, but there is also a closureSerializer in Spark which is ALWAYS Javaserializer and it fails to deserialize data written from one classLoader to the current one of the interpreter.
And I can't set the correct classLoader in the serializer as I don't have any ref to it.

That may require some customizations in Ammonite… (to put all classes of a session in a custom package for example).

How do you make a custom package in Ammonite ?

How do you make a custom package in Ammonite ?

I don't have a definite answer, but at the very end, the package is set in the compiled code around here. By navigating your way in the Ammonite code from there, it may be possible to pass a custom package prefix to ammonite.interp.Interpreter so that it ends up being used there.
Alternatively, the cmd prefix in the class name is defined here. Just allowing to customize it via a field passed to ammonite.interp.Interpreter (and set it yourself to "cmd1_", "cmd2_", etc. so that the classes are named "cmd1_1", "cmd1_2", …) may work as well, and would probably be more straightforward.
The Ammonite README has some doc detailing manual commands to quickly test that kind of changes.

Thank you for your help. I will close an issue!

Sorry for bringing this up
@supperslonic What was your solution for the Spark issue?

Hey, @navado !
We had to modify some internal classes like the HTTP endpoint responsible for handling REPL and CodeClassWrapper.
Each Interpreter is using its own package and its own classloader.
REPL service endpoint detects by the package name which classloader to use to get the lambda-generated classes.


Create 0000-01-02-Sporknotafork.md

Slide show page 0000-01-02-Sporknotafork.md

This is the exercise

Merged for exercise


[FR] extend timers with the concept of reminders

Still bringing what I developed for my previous voice assistant.
If you're not interested for the sake of Home Assistant, or if I'm already asking too much too early, and the voice pipeline needs more maturation, just tell me.
At least the first two commits should be considered.
There's one sentence commented out, because it's being shadowed by timed commands. I'd like your insight on that.
I know it looks like I'm obsessed with naming timers, but it's just because I display them. :rofl:
Way easier when you have three of them at the same time.

(These changes are pushed to my esphome wakeword fork, just no PR open yet.)

Arf, indeed you are thinking one or two steps ahead.
So the main difference between a timer and a reminder is the time frame.
You set a timer for 1,2 hours max.
But you usually set reminders days or even weeks into the future.
Today, we have a somewhat OK-ish solution for timers (it has its limitations), but we do not have a great solution for reminders.
Reminders require to be managed, edited, displayed, etc, etc
So for now, we do not want to mix both concepts, unfortunately.
Because we do not want to set ourselves up for failure in the future once reminders will actually come.
I do like the plural thing on the response. This is top-notch.
Would you mind opening a PR just for that, I can merge it right away.
And do not forget, you can extend any intent you like by putting the files (The same you are working on right now) under consutom_sentences/fr in your home assistant configuration folder.
I would suggest you do just that for reminders if they are close to your heart.
Just a note: We know we need to find a solution for reminders. Definitely.
Thx a lot for your time! I really appreciate seeing more people working on the french sentences!

No worries, I just wanted to share my work. For now these reminders are just a fancy way to name a timer, but you're right I wanted in the middle term to have a reminder at as given time of day, not just a countdown. Something related to calendars maybe, but we could discuss that another day.
Closing this PR. And you're right, these are coming from my custom configuration.


Corrects mailer tests and improves rule injection

TODO:

[ ] Add integration scenario testing for 2w/3w on contract end

The good news is that this is on the same wavelength as #83, so we're not pulling in opposite directions; the less good is that we have a bunch of changes that will conflict. I'm not against merging both and dealing with the conflicts, having the code somewhat fresh in mind. But might it help instead to either add the changes from #83 to this, or the changes from this to #83? Bearing in mind that#83 renames Mailer to NotificationRequest.

I've gone ahead and merged the changes from here into #83, then I'd like to merge #83 quickly. Let me know what you think.


Support GHC 9.8

Needs, at least, bumping base and template-haskell bounds.
/Cc @andreasabel who added support for the previous GHC release (9.6).

Pull request for that is already there, just need to poke @fumieval to merge/publish it.

Thanks, I missed that! For the reference, it’s #13.

Revision has been published.

Awesome sauce!!!

@pacak Issue can be closed.


Update kafka_python to 1.3.4

This version contains important fixes to limit the number of connections made during bootstrapping

🏃 PG1 1949


[Bug] ChatQnA not working on stock Kubernetes cluster

Priority
Undecided
OS type
Ubuntu
Hardware type
Xeon-SPR
Installation method

[X] Pull docker images from hub.docker.com
[ ] Build docker images from source

Deploy method

[ ] Docker compose
[ ] Docker
[X] Kubernetes
[ ] Helm

Running nodes
Single Node
What's the version?
latest tag per the Helm chart at https://github.com/opea-project/GenAIExamples/blob/main/ChatQnA/kubernetes/manifests/xeon/chatqna.yaml.
Description
Deploying ChatQnA on Kubernetes following the instructions at https://github.com/opea-project/GenAIExamples/tree/main/ChatQnA/kubernetes/manifests. The following pods are in ContainerStarting phase and not getting fully started:

pod/chatqna-tei
pod/chatqna-teirerank
pod/chatqna-tgi

@mkbhanda
Reproduce steps
Here are the exact steps: https://gist.github.com/arun-gupta/fd3793baadc9feb4c3883c80b9481161
Raw log
ec2-user:~/environment:$ kubectl get all
NAME                                           READY   STATUS              RESTARTS   AGE
pod/chatqna-79d8c5ffff-m2fb9                   1/1     Running             0          8m29s
pod/chatqna-data-prep-77dcc665f4-gjj7t         1/1     Running             0          8m30s
pod/chatqna-embedding-usvc-55d4dc8f67-6qrln    1/1     Running             0          8m30s
pod/chatqna-llm-uservice-66cc67785-vkpc9       1/1     Running             0          8m30s
pod/chatqna-redis-vector-db-5dcd98f579-x7k9q   1/1     Running             0          8m30s
pod/chatqna-reranking-usvc-759bf96c5c-fl6f8    1/1     Running             0          8m30s
pod/chatqna-retriever-usvc-86f8dfbfb6-pfktk    1/1     Running             0          8m30s
pod/chatqna-tei-565488dd9-p4cj7                0/1     ContainerCreating   0          8m30s
pod/chatqna-teirerank-6c9854cfdf-mmgqh         0/1     ContainerCreating   0          8m30s
pod/chatqna-tgi-587b54f5ff-fcfqn               0/1     ContainerCreating   0          8m29s

NAME                              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
service/chatqna                   ClusterIP   <IP_ADDRESS>   <none>        8888/TCP            8m30s
service/chatqna-data-prep         ClusterIP   <IP_ADDRESS>   <none>        6007/TCP            8m30s
service/chatqna-embedding-usvc    ClusterIP   <IP_ADDRESS>   <none>        6000/TCP            8m30s
service/chatqna-llm-uservice      ClusterIP   <IP_ADDRESS>    <none>        9000/TCP            8m30s
service/chatqna-redis-vector-db   ClusterIP   <IP_ADDRESS>   <none>        6379/TCP,8001/TCP   8m30s
service/chatqna-reranking-usvc    ClusterIP   <IP_ADDRESS>   <none>        8000/TCP            8m30s
service/chatqna-retriever-usvc    ClusterIP   <IP_ADDRESS>   <none>        7000/TCP            8m30s
service/chatqna-tei               ClusterIP   <IP_ADDRESS>    <none>        80/TCP              8m30s
service/chatqna-teirerank         ClusterIP   <IP_ADDRESS>    <none>        80/TCP              8m30s
service/chatqna-tgi               ClusterIP   <IP_ADDRESS>     <none>        80/TCP              8m30s
service/kubernetes                ClusterIP   <IP_ADDRESS>       <none>        443/TCP             24m

NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/chatqna                   1/1     1            1           8m30s
deployment.apps/chatqna-data-prep         1/1     1            1           8m30s
deployment.apps/chatqna-embedding-usvc    1/1     1            1           8m30s
deployment.apps/chatqna-llm-uservice      1/1     1            1           8m30s
deployment.apps/chatqna-redis-vector-db   1/1     1            1           8m30s
deployment.apps/chatqna-reranking-usvc    1/1     1            1           8m30s
deployment.apps/chatqna-retriever-usvc    1/1     1            1           8m30s
deployment.apps/chatqna-tei               0/1     1            0           8m30s
deployment.apps/chatqna-teirerank         0/1     1            0           8m30s
deployment.apps/chatqna-tgi               0/1     1            0           8m30s

NAME                                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/chatqna-79d8c5ffff                   1         1         1       8m29s
replicaset.apps/chatqna-data-prep-77dcc665f4         1         1         1       8m30s
replicaset.apps/chatqna-embedding-usvc-55d4dc8f67    1         1         1       8m30s
replicaset.apps/chatqna-llm-uservice-66cc67785       1         1         1       8m30s
replicaset.apps/chatqna-redis-vector-db-5dcd98f579   1         1         1       8m30s
replicaset.apps/chatqna-reranking-usvc-759bf96c5c    1         1         1       8m30s
replicaset.apps/chatqna-retriever-usvc-86f8dfbfb6    1         1         1       8m30s
replicaset.apps/chatqna-tei-565488dd9                1         1         0       8m30s
replicaset.apps/chatqna-teirerank-6c9854cfdf         1         1         0       8m30s
replicaset.apps/chatqna-tgi-587b54f5ff               1         1         0       8m29s
ec2-user:~/environment:$ kubectl logs pod/chatqna-tei-565488dd9-p4cj7
Error from server (BadRequest): container "tei" in pod "chatqna-tei-565488dd9-p4cj7" is waiting to start: ContainerCreating
ec2-user:~/environment:$ kubectl logs pod/chatqna-teirerank-6c9854cfdf-mmgqh
Error from server (BadRequest): container "teirerank" in pod "chatqna-teirerank-6c9854cfdf-mmgqh" is waiting to start: ContainerCreating
ec2-user:~/environment:$ kubectl logs pod/chatqna-tgi-587b54f5ff-fcfqn
Error from server (BadRequest): container "tgi" in pod "chatqna-tgi-587b54f5ff-fcfqn" is waiting to start: ContainerCreating

Would you also provide the output of kubectl describe?
kubectl describe pod chatqna-tei-565488dd9-p4cj7

I shut down the cluster and will recreate it for you.
Creating a directory /mnt/opea-models specific to a node does not seem k8s-native way. It could be a multi-node cluster and this would make it tricky. Can this be done using a PVC instead?

Yes, PVC already supported from helm-charts deploy:
https://github.com/opea-project/GenAIInfra/tree/main/helm-charts#using-persistent-volume
The manifests deploy is not flexible enough and we want to provide manifests with as less as possible configuration changes.(Assume PVC would require additional setup).
Maybe the best way for manifests is not to set model-volume and have the model downloaded at the container startup.(We can remove the model-volume dependency if you think this way is better)

Anything that requires customization outside of the Helm charts will add to developer friction and should be minimized.
Either way, the /mnt/opea-models step is not documented. I'd recommend removing it but that will add to the container startup time.

This /mnt/opea-models path issue has been fixed by #745
Now by default, the tgi/tei will use a temp volume to download and save Models.


Book updates

In this (larger) commit, several things have been updated in the book as discussed in issue #2007.

the DX section has been moved right after the "getting started" section
a new section has been added to "getting started" that's all about describing the Leptos community, and where to find the leptos-related crates ie. in the "Awesome Leptos repo
this last commit was the biggest one: I have drawn out the inherent structure of the book and explicitly split the book into 2 parts: part 1 on CSR and part 2 on SSR - this structure was already implicit in the text, I've just made it a little more explicit so that people feel like they've accomplished something in part 1 (CSR) before moving onto part 2 (SSR).

This last commit required editing a few sections to make the explicit separation work. I hope you like it, and that it wasn't too much of a large change in one pull request.
(I used to be an English academic & professional editor, before being struck by a debilitating disability and eventually moving into tech; I couldn't help but add a bit more structure to the text)
I've also added a few words here and there in response to questions about the book on Discord - mostly trying to clarify the differences between the CSR and SSR modes.

Awesome! Thanks, I will merge this and then move the book over to the new repo.
For context re: "isomorphic": I am ultimately fine with any term here that you and others decide is reasonable. I tend to use "isomorphic" in the specific sense of "having the same shape," so I say server functions are "isomorphic" because they have the same "shape" when called on either the server or client -- likewise with SSR + hydration, the view tree/tree of components and elements has the same shape on the server and client.
But mostly I'm just fond of it because I've been reading ancient Greek for a long time and so the name makes perfect sense to my brain (isos = equal/same, morphikos = relating to a shape). I recognize that I've had an... unusual path here and it may not make the same sense to other devs 😅


why the rule "cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase1h" does not add {job="apiserver"}

What happened?
Did you expect to see some different?
How to reproduce it (as minimally and precisely as possible):
Environment

Prometheus Operator version:
quay.io/prometheus-operator/prometheus-operator:v0.72.0

Kubernetes version information:
kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.11

Prometheus Logs:

why the rule "cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase1h" does not add {job="apiserver"} ???
`

expr: |
sum by (cluster, verb, scope) (increase(apiserver_request_sli_duration_seconds_count{job="apiserver"}[1h]))
record: cluster_verb_scope:apiserver_request_sli_duration_seconds_count:increase1h

expr: |
sum by (cluster, verb, scope) (avg_over_time(cluster_verb_scope:apiserver_request_sli_duration_seconds_count:increase1h[30d]) * 24 * 30)
record: cluster_verb_scope:apiserver_request_sli_duration_seconds_count:increase30d
expr: |
sum by (cluster, verb, scope, le) (increase(apiserver_request_sli_duration_seconds_bucket[1h]))
record: cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase1h
expr: |
sum by (cluster, verb, scope, le) (avg_over_time(cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase1h[30d]) * 24 * 30)
record: cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase30d
`

then that will case the function in apiserver_request:availability30d get wrong value, the value is less than zero
`
write too slow
        sum by (cluster) (cluster_verb_scope:apiserver_request_sli_duration_seconds_count:increase30d{verb=~"POST|PUT|PATCH|DELETE"})
        -
        sum by (cluster) (cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase30d{verb=~"POST|PUT|PATCH|DELETE",le="1"})

`

Anything else we need to know?:


Systemd process manager has not been set up or is corrupted

Issue Summary
I updated Ghost from v3 to v4 to v5 and everything went smooth.
After I tried to change the configuration to setup the cache since I have waiting time issues with Ghost and am trying to figure out why.
Then, I restarted the server through sudo -u ghostuser ghost restart and the server told me Systemd process manager has not been set up or is corrupted..
I tried to run sudo -u ghostuser setup linux-user systemd had stated in the response but it's saying Systemd service already been set up. and then skip the setting up of it.
The service runs when doing sudo service ghost_blog start but Nginx can't connect to it, it's returning a 502 bad gateway error.
What can I do to fix these errors?
Steps to Reproduce

Add cache configuration to config.production.json
sudo -u ghostuser ghost restart
sudo -u ghostuser ghost setup linux-user systemd

Ghost Version
5.1.1
Node.js Version
14.19.3
How did you install Ghost?
through ghost-cli (latest version)
Database type
Other
Browser & OS version
Debian 10
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

I finally succeed to fix it.
I ran sudo -u ghostuser setup and it worked.


support on update, findOneAndUpdate, findOneAndRemove queries

Its very nice plugin to maintain the update history. Can you tell me do you any plan to implement update, findOneAndUpdate, findOneAndRemove queries to upcoming releases, any ETA? I am eager to know because i need it in my project.

Hi riteshnus,
Since this project hasn't been updated in a while, I forked it and added the support to updateOne(), findOneAndUpdate(), findOneAndRemove(), and findOneAndDelete().
Here are the links:
NPM: https://www.npmjs.com/package/mongoose-history-updated
Git: https://github.com/lsantsan/mongoose-history-updated
The changes include vkarpov15 's pull request and support to Mongoose 5.3.3.
I'll eventually create a new pull request to merge the projects.


Write Enumerable#grep_v specs

@kachick Seeing all your great commits recently,
I would like to propose you to be a RubySpec committer :tada:
So that you can push directly to master if you like :smiley:
Would you like that?

@eregon Thank you! I'm honored :smile:
I'll mainly use the commit rights for simple patch.

:clap:

@kachick I sent you the invitation!

@eregon I received it. Thanks!


More efficient autoloading?

This is a great library, but unfortunately we may end up having to uninstall it because installing it with Composer has added a huge difference to the page load, as profiled with BlackFire.
(Sadly autoloading functions won't be added to PHP anytime soon).
One solution I thought of it adding generation of the functions to Symfony's bootstrap.php.cache file.
However I'm wondering if this library would benefit from providing its own solution for optimizing the loading of functions?

As we no longer support the C extension to be installed side-by-side, would a static require list fix it for you?

@lstrojny Thank you, I'll give it a try and report back :+1:

I believe this new autoloading is performing better, though it's hard to tell; The relative cost of the Composer autoloading path may have decread by could have been skewed by other changes in our codebase.

Alright, the new method should indeed work better. Closing this for now, OK?

@lstrojny All good, thank you :+1:


Removed a repeating allocation of memory

Resolves #1495
This line allocated some memory that was already allocated in the beginning of the function and was essentially creating a leak.

@object71 Thanks! Good catch! :)

@object71 Thanks! Good catch! :)


WIP [release/1.3.1] [DEVOPS-398] Testnet genesis data

This is based on top off #3585, which should be merged first.
Description
Updates the genesis data for testnet.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/DEVOPS-398
QA Steps
nix-build -A connectScripts.testnet.wallet -o connect-testnet.sh
./connect-testnet.sh

Screenshot

Please do not merge because release/1.3.1 does not exist yet.

Until release/1.3.1 has been cut from develop should this PR target develop instead of release/1.3.0? Then the resulting Daedalus installers for https://github.com/input-output-hk/daedalus/pull/1015 could more accurately reflect what release/1.3.1 will eventually be.

I understood that the hotfix release/1.3.1 will not be cut from develop, but rather from the v1.3.0 tag

Yes, my mistake.

Rebased on latest release/1.3.0 and resolved merge conflicts in launch scripts/demo cluster.

On this branch I have tested:
nix-build -A connectScripts.testnet.wallet -o connect-testnet.sh && ./connect-testnet.sh

This sync successfully and proves that the validation errors I was seeing before is because I hadn't merged the right branch into my test branch.
nix-build -A connectScripts.mainnet.wallet -o connect-mainnet.sh && ./connect-mainnet.sh

This fails with:
[node:ERROR:ThreadId 5] [2018-09-19 02:22:01.02 UTC] logException: GenesisHashMismatch "AbstractHash 4832ba94116f22e49f0da1ff5e305ee7fe1a736fecf2fdbe6b8db31039148ae9" "AbstractHash 5f20df933584822601f9e3f8c024eb5eb252fe8cefb24d1317dc3d432e940ebb"
cardano-node: GenesisHashMismatch "AbstractHash 4832ba94116f22e49f0da1ff5e305ee7fe1a736fecf2fdbe6b8db31039148ae9" "AbstractHash 5f20df933584822601f9e3f8c024eb5eb252fe8cefb24d1317dc3d432e940ebb"

which means there is probably something wrong with the mainnet_full configuration in #3585 which needs to be fixed.
(If wondering how to debug this, cat connect-mainnet.sh then adjust the cardano-node command line to use your chosen binary and configuration file.)

I'll try running the wallet on mainnet and staging after hydra builds everything. Unless you already have CO-354 in your branch (as of a few minutes ago) good chance that last commit resolves the issues you're having.

Thanks. Now that #3585 is merged, I have rebased on release/1.3.1 and also generated new genesis data from exactly this configuration.yaml (not one which was slightly different but effectively the same).


Use cxx crate to generate FFI bindings

This PR sets up the build infrastructure and demonstrates how to use cxx for simple functions and for RAII.
Hand-written FFI bindings worked fine until now, because the only types we flung over the FFI boundary were integers, strings, and structures containing integers and strings. As we continue to port more code, we run into functions that takes or returns complex objects like vectors. Those aren't as simple to fling over FFI, for a number of reasons:

elements of a vector might have constructors and destructors that need to be ran at appropriate times;
on the Rust side, we don't have anything like CStr or CString but for Vec—there's no easy way to "pack" a vector into a single pointer that we can fling over FFI;
as a corollary, to faithfully represent a vector we have to store three pieces of data (pointer, size, capacity), not a single pointer like with C strings;
vectors are generic types, and would require either special-casing (writing code for each contained type) or some scaffolding to support that polymorphism.

Clearly we need a better way to write bindings—or generate them.
There's a tool called bindgen, which takes Rust code and generates C bindings for it. If we go with that, we'll have to write C++ wrappers over the generated C. Furthermore, bindgen requires libclang and is a separate tool that one has to install. Overall, I think bindgen is a viable option, but a not-too-compelling one. (I should note that I only ran bindgen like 2 times in my life, so if you have experience with it and I'm wrong about it, please talk to me about that!)
That leads us to the cxx crate. It's three things: 1) a way to describe our FFI boundary in a language that looks exactly like Rust; 2) two code generators that take the description and generate Rust and C++ wrappers of the boundary. As a result, we get idiomatic or near-idiomatic bindings with very little hassle. We will swill have to write wrappers sometimes (e.g. for RAII), and we might need to drop into unsafe for some hard-core bits, but the "happy path" should become way simpler.
There are downsides to cxx, of course. The main one is a slight loss of control: since we aren't writing the wrappers anymore, we can't insert our abort_on_panic! macro that prints backtraces. cxx strings throw std::invalid_argument if the C++ string is not in UTF-8 encoding; for now, I simply let that exception bubble up and crash the application. I don't feel like backtraces obtained from abort_on_panic! were of much use to us, but if someone feels differently, we can get something similar using backtrace(3) (kudos to @pink-snow for teaching me about this function).
Another downside is limited C++ support. This PR uses cxx-0.5, an older version that supports Rust 1.43+ and C++11. The newer cxx-1.0.0 requires Rust 1.48+ and C++14. This rules out GCC 4.9, but if I'm reading this table correctly, we shouldn't need to drop any more compilers in the foreseeable future. I misread the README; cxx 1.0 supports C++11 all right.
Also, the size: cxx pulls additional 12 crates with it.
Comments and reviews are very much welcome. If no-one speaks out against this, I'll merge in a week.

Coverage increased (+0.003%) to 57.612% when pulling 8f88c0a30715c0a79459ed6c565b24eb2b5a0601 on feature/cxx-try-3 into ef2531d7cc17f74e427c436b95330415c69a8368 on master.

There were conflicts with master branch, so I rebased and took this opportunity to squash the fixups.

The fake_install step of some of the CI runs take significantly more time than before.
For example, see the FreeBSD 11.4 builds:

master: https://github.com/newsboat/newsboat/runs/1467390989 (0:02 minutes)
this branch:
https://github.com/newsboat/newsboat/runs/1467910271 (2:50 minutes)

I believe the cargo clippy run regenerates the target/cxxbridge/libnewsboat-ffi/src/%.rs.h files, causing the dependent C++ files to be recompiled.
Relevant part of the .cirrus.yml file:
https://github.com/newsboat/newsboat/blob/de06ef817efe90c3868be3f79f40faaccdb29df4/.cirrus.yml#L45-L52
It might be possible to circumvent this by running the fake_install_script before the clippy_script step.

@dtolnay Ah, sorry, I misread the README! I could swear I saw it say "Rust 1.48+ and C++14", but clearly I'm wrong. I removed that claim from the top post; my apologies for misinforming everyone.
We still can't use cxx 1.0 because its requirement for Rust is too new. We'll bump our MSRV to 1.48 at the end of March, and will migrate to 1.0 then.
Even with cxx 0.5, I had to drop GCC 4.9 since it doesn't support std::is_trivially_move_constructible (https://github.com/newsboat/newsboat/pull/1304/commits/0738d9593831f7914d1a3d9ac3fcefe4fe310e94). That thing is part of C++11, so I didn't report it to you — clearly it's a compiler's problem.
And while I have your attention: thanks for creating cxx! I'm really glad I won't have to dive into FFI that much anymore.

@dennisschagt Thanks for spotting this! I think your suggestion should work nicely, so I pushed it to see if CI agrees :)

Okay, this is ready to be merged. Thanks for the comments everyone!


Construct with 2D array breaks build process in certain situations (inline if)

The following code does not compile:
namespace BreakTest
{
    public class Broken
    {
        private static int nx = 4;
        private static int[,] breaker = new int[,]
        {
            { 1, 2 },
            { 3, 4 }
        };

        private static void BreakIt(int x, int y)
        {
            var retval = (x >= 0 && x < nx && breaker.Length > ((x + 1) * nx)) ? breaker[x, y] : 0;
        }

    }
}

Visual Studio displays:
1>EXEC : error : Parsing error in a file A:\devel\Object.NET\projects\ClassLibrary1\ClassLibrary1\CodeFile1.cs: System.Linq.Enumerable+WhereListIterator'1[ICSharpCode.NRefactory.TypeSystem.Error]
If debugging:

Error triggers when calling ICSharpCode.NRefactory.CSharp.CSharpParser().Parse()
The location in bridge is Bridge.Translator.Translator.GetSyntaxTree() (Translator.InspectAssembly.cs).
Parse() returns with 'HasErrors' true, and its 'Errors' structure points to the line where the inline if is used
The error actually says that the ? character in the line is unexpected.

I guess It is NRefactory parser bug. For example, if wrap breaker[x, y] by braces () then all works
Need to check it with latest NRefactory

@vladsch @fabriciomurta, Seems to work for me:
Bridge Live.

Interesting, I could not reproduce it as well.
Tested with the Live Test Case (posted in the previous comment) and also with local VS 2013 and 2015.

This is fixed by NRefactory and Mono.Cecil updates. Added client test and closing the issue.


cmd/link: Go 1.4.2 ldflags -s still shows the line numbers of the stack trace

What platform did I use for test:
Microsoft Windows 7 x86 , go 1.4.2 windows x86
What code did I use for test:
    // test
    package main
func main() {
    panic("golang")
}

What command did I use for complier the test program:
    go build -ldflags "-s -w" test.go
What am I expected to see :
    Should not print the line number in the stack trace.
What exactly did the complier show:
    panic: golang
goroutine 1 [running]:
main.main()
        D:/Users/lenovo/Desktop/test.go:5 +0x54
...

So... Is it designed to always shows the line numbers ?
There may be security reason that some projects may needs to hide or strip some unexpected printing messages. So I just curious :smile:

-s does not strip line number information.
-s is not tested and is not recommended as it is know to produce broken executables on multiple platforms.

OK , I get it . I think this should be add into the golang document , as I was looking for some ideas to block the whole debugging messages


About defineSiteConfig property author.avatar.

I haven't static url for author.avatar.  Can i use import avatar from './assets/xxx.png' to set auhtor.avatar` ?
Example:
import avatar from './assets/avatar.png'
export default defineSiteConfig({
   author: {
     name: 'My Name',
     avatar: avatar
   }
})

You can use /xxx/yyy.jpg.
And place /xxx/yyy.jpg in public folder.

I tried it, But it didn't work.
Here is a simple repo

It works well in my local computer when I set avatar: '/cat.svg' and put cat.svg in public folder. I think this problem may be caused by StackBlitz.

You should create a new dir public with the same level as pages.
- public
- pages

And not use relative path. you should use absolute path.
If you have a file placed in public, like public/avatar.png.
And set it in author.avatar: '/avatar.png'.


HTTPS not replayed by mitmdump

What's the problem?
Mitmdump is configured as a transparent proxy with ssl support, the certificate is installed. The sites with ssl could be captured but with some thousand URIs for https and http none for https is replayed, only http.
I'm not sure if this is related to #755.
What's expected?
The https sites should be replayed, too.
Which versions are affected?
The master version of mitmdump/libmproxy from yesterday was used.
In 0.13 this problem was not there.
How to reproduce the problem?
The best way I can think of is to search for a file with HTTPS, like a picture from wikipedia, to capture it with a transparent mitmdump and than to replay this. I used --no-pop but I think this doesn't matter.
Why does this happen?
For a better understanding I modified the output of mitmdump. Thus it told me when a replay was done and additionally the value of _hash from flow.py. Therefore I added a print(repr(key)) in front of the return of the _hash function.
Now I used the logo from wikipedia for the test. With the modified hash function there is a line printed for every response in the captured file on startup. In this case it is something like
['443', 'http', 'GET', [...]

When a request occur some new line are printed, in this case something like
['443', 'https', 'GET', [...]
192.168.X.X:59990: clientconnect
192.168.X.X GET https://[...]
192.168.X.X GET https://[...]
 << 200 OK 10kB
192.168.X.X:59990: clientdisconnect

Do not forget, the output is modified thus more is printed than normal. But the problem is also revealed. When the captured file is loaded the saved data is loaded with scheme http. But the request is done with https thus there is no match but a miss and mitmdump did not find the captured data even though it is there.
By looking into the captured file it is clear, that the data is saved with scheme https and thus correctly.
How could the problem be solved?
Well to be true I undo some code. I removed line 249 scheme = "https" if flow.client_conn and flow.client_conn.ssl_established else "http" and set scheme=r.scheme. This is a workaround and I could not tell the side effects of this.
But to say the truth I do not understand why there is such a line. Depending on the comment I think that libmproxy may downgrade https connection to http ones. And to be able to find the data the scheme is modified. But if scheme could only be https and http and that you try to find the response in both cases, I do not know why scheme is not simply removed.

Thanks for the really organized bug reports!

I do not know why scheme is not simply removed.

You may have a case where http://example.com/path gets a redirect to https://example.com/path. The following request to https://example.com/path should consequently return a different response. So, we need the scheme in some way or another.
The code looks fishy as there's also the port which we somehow consider. I'll look into it tomorrow.


Add cliffStart to Smart Escrow contract

Per conversations with the OP team and CB legal, we have determined that the initialTokens "cliff amount" needs to be disbursed by the escrow contract at a later time than the start of the vesting schedule. As such, the logic to handle token release needs a new way to track the two different start times.
This PR adds a cliffStart which strictly releases the initialTokens. The original start date will continue to track the release of tokens according to the vesting schedule. We strictly enforce that start <= cliffStart < end.

Review Error for wilsoncusack @ 2024-05-07 20:42:55 UTC
User failed mfa authentication, see go/mfa-help

This seems good to me. Would be nice to try to think of some fuzz testing where we use vm.warp

I think that we've got some nice fuzzing implemented in testFuzz_release


New feature brainstorming

Please comment on this issue with new feature ideas not already discussed in the readme: https://github.com/cytoscape/cytoscape.js-euler#mozilla-global-sprint-2017-instructions

Please add multi threading, 10 seconds of layouting for 2000 classes and 4500 properties on Firefox 54 (64 bit) even with a Core i7-4790 is probably too much for my users.

A seed attribute for the randomize option would be help users to always get the same layout as long as there are no changes.

The anchor of the link in the issue does not seem to work.

A progress callback would be great to enable progress bars for layouts on large graphs which can take more than 30 seconds.

Also I need a partial layouting when I add new nodes but don't want to change the position of the old ones.

Also I need a partial layouting when I add new nodes but don't want to change the position of the old ones.

That's not a per-layout feature.  You can lock the old nodes.

A progress callback would be great to enable progress bars for layouts on large graphs which can take more than 30 seconds.

The only measure for progress would be the energy/movement of the system each tick.  That's not going to give a nice value for a progress bar.  It decreases exponentially over time.  You could come up with a transformation function that gives a more linear result, but I suspect that function would change significantly given the layout options.

Please add multi threading,

That won't help until the browsers add support for workers/threads with truly shared memory.  The layouts that currently support Weaver for threads only use one --- it just keeps the main ui thread freer and more responsive to user input.
Links of interest:

https://www.w3.org/TR/workers/
https://html.spec.whatwg.org/multipage/workers.html
https://hacks.mozilla.org/2016/05/a-taste-of-javascripts-new-parallel-primitives/

A seed attribute for the randomize option would help users to always get the same layout as long as there are no changes.

It's just using Math.random(), which has no seed support: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/random
There's not much point in re-inventing the wheel for a RNG, so you'd have to pull in a package from npm as a dependency.  Hopefully, it would be not many kB.

Thank you very much for the detailed replies! I did not know that there is no seed support for Math.random(), is the rest of the euler algorithm deterministic apart from the optional initial positioning or does it also use randomness?

It's used in several places: https://github.com/cytoscape/cytoscape.js-euler/search?utf8=✓&q=Math.random&type=


[azure] [feat] Add new relationships between network resources

Description

Added connect_in_graph method to the network resources.

Also added a tests to the new collected resources.

Fixed error with nested sub-resources.

To-Dos

[x] Add test coverage for new or updated functionality
[ ] Add a tests to check successful connections between network resources
[x] Lint and test with tox
[x] Add connections between network resources

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

And I forgot: AzureSubnet: shouldn't this be a resource?

And I forgot: AzureSubnet: shouldn't this be a resource?

We can't take AzureSubnet only by a subscriptionId. Additional parameters required for: resourceGroupNameand virtualNetworkName.
https://learn.microsoft.com/en-us/rest/api/virtualnetwork/subnets/list?view=rest-virtualnetwork-2023-05-01&tabs=HTTP#uri-parameters
URI Parameters

Name
In
Required
Type
Description

resourceGroupName
path
True
string
The name of the resource group.

subscriptionId
path
True
string
The subscription credentials which uniquely identify the Microsoft Azure subscription. The subscription ID forms part of the URI for every service call.

virtualNetworkName
path
True
string
The name of the virtual network.

api-version
query
True
string
Client API version.


Define the blockchain API to add a new transaction

This is entry point to the blockchain component from the transparency log in case of an artefact publication.
The transparency log component creates a payload and asks the blockchain component to store it as a transaction on the blockchain:
could be as simple as add_transaction(payload, listener)
Once this API is defined, the Transparency log component can be implemented.
(Arrow 7a - https://pyrsia.io/docs/developers/pyrsia-high-level-overview/)

Code is living in @chb0github fork waiting to be merged back

Completed on #978


B904 only triggered for error literals

err = ValueError("msg")

try:
    raise Exception
except Exception as exc:
    if isinstance(exc, ValueError):
        raise err # expecting B904 here but ruff is happy

Bugbear has the same behavior very intentionally, though I'm not familiar with what's being described: https://github.com/PyCQA/flake8-bugbear/pull/181#issuecomment-904314876