Flexvolume plugin error

I'm seeing this in my k3s logs.
W1116 12:10:13.254151    1893 probe.go:268] Flexvolume plugin directory at /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ does not exist. Recreating.
E1116 12:10:13.254450    1893 plugins.go:600] Error initializing dynamic plugin prober: Error (re-)creating driver directory: mkdir /usr/libexec/kubernetes: read-only file system

I'm guessing it's because /usris the squashfs mounted as ro. Should /usr/libexec be writeable like /usr/lib/firmware is?

@zimme yes, /usr is sourced from the squashfs embedded in the /k3os/system/k3os/current/k3os executable.
hmm, based off of https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md#prerequisites you should be able to override with --flex-volume-plugin-dir (not sure how you're deploying, helm?)
that said, i wonder if we could just be more friendly by setting up a symlink to somewhere under /var/lib

@zimme yes, /usr is sourced from the squashfs embedded in the /k3os/system/k3os/current/k3os executable.
hmm, based off of https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md#prerequisites you should be able to override with --flex-volume-plugin-dir (not sure how you're deploying, helm?)
that said, i wonder if we could just be more friendly by setting up a symlink to somewhere under /var/lib

good candidate opportunity for leverage a boot_cmd :smile:

This is on a clean k3os install, I haven't deployed flexvolume myself

this config.yaml did the trick:
k3os:
  k3s_args:
  - "--kube-controller-arg=flex-volume-plugin-dir=/var/lib/kubernetes/kubelet-plugins/volume/exec"

/cc @erikwilson do you have any input on this? my assumption is that the FlexVolume plugin is just something included with k3s and proper configuration is left as an exercise to the "user".

I'm thinking that k3os should provide a default config for this or synlink the default path to somethink writable. As this comes with k3s/k3os by default

I'm thinking that k3os should provide a default config for this or synlink the default path to something writable. As this comes with k3s/k3os by default

yes, /usr/libexec/kubernetes could be easily pointed to /var/lib/kubernetes but because it is so simple and doesn't seem necessary i am inclined to let he user/operator deal with it. i'll ask @ibuildthecloud what he thinks after kubecon

@dweomer, did @ibuildthecloud have an opinion on this?

I’ve been meaning to just default it via a symlink in /usr space

Fixed via #447


train.csv

hello, when i run the MAML_TrainStd.ipynb, it shown FileNotFoundError: [Errno 2] No such file or directory: '../../../dataset/train.csv'
, so how can i get the train.csv file. thank you

Here you go csv files


Support mapping of SPARQL to Controlled Natural Language

The requests and answers need to become more human-readable but stay reliable. The best solution for this are controlled natural language mappings, because they offer little ambiguity, because they are still pretty formalic and therefore stay reliable, but at the same time provide you with a format that is more human readable that SPARQL.
Popular controlled natural languages are for example https://en.wikipedia.org/wiki/Attempto_Controlled_English.
Maybe it could work based on this: https://github.com/AKSW/SPARQL2NL

Maybe this could help: https://jens-lehmann.org/files/2013/www_sparql2nl.pdf

This only describes SPARQL -> NL but not NL -> SPARQL. This is often done with natural language processing AI, for example https://www.lymba.com/nl2query

For this you need an AI model, for example: https://huggingface.co/PopularPenguin/text-to-sparql-t5-base-2024-10-01_04-05


Eliminate false positives in Checking data consistency

Same for https://github.com/spine-generic/data-single-subject/issues/17


Change ServerConnectionType.NONE to ServerConnectionType.DIRECT_HTTP.

Current dependencies on/for this PR:

main

PR #199

PR #202

PR #204   👈

This stack of pull requests is managed by Graphite.

For a moment I thought it might make more sense to name TCP, thinking about in the future possibly supporting UDP (as opposed to TCP), gRPC (as opposed to HTTP, but still flowing over this same connection), or Teleport. To me it's just more confusing because it won't clearly signal that the major difference from the other types is "NO ENCRYPTION HERE." Which I think makes a different point - this really isn't the "ConnectionType", as SSH tunnels, aws_ssm, and tls all flow through http, so something like a UDP or gRPC variant isn't relevant here. This is really the encryption type. What do you think about leaving this as NONE but changing to EncryptionType.NONE, EncryptionType.TLS, EncryptionType.SSH, etc. and changing the connection_type as well? Cc @jlewitt1

oooh, I think EncryptionType could be good. @jlewitt1


Pass DOM events to custom functions

The motivation is to display tooltip if the click was done inside of an area. The click event is not passed to functionBefore, so it can't be done easily. A similar case is when we want to prevent hover on certain elements.
I suggest adding a new optional event parameter to functionBefore and functionAfter. It can be undefined if the tooltip was shown manually. Potentially event may even replace origin because it has it as a target.
function(origin, ev, continueTooltip)

I think you should use custom triggers for your use cases.

With custom triggers I can't make the tooltip close automatically on click outside of the element. I will need to reimplement most of the behavior although I need only to filter some events before opening.
I captured the event manually. The solution works but it is ugly.
var ev;
$(obj).on("click", function(event) {
            ev = event;
        }).tooltipster({
            trigger: "click",
            functionBefore: function(origin, continueTooltip) {
               if (checkEvent(ev)) continueTooltip();
            }
            ...
});

I understand but it adds complexity for a use case which is quite custom.
In v4, all callback functions have the same signature, I don't like the idea of changing that again, especially if the argument is going to be sometimes undefined.
Another solution would be to pass a helper object to all callbacks, like :
this.options.onBefore({
    origin: $el,
    event: ev
});

at least it leaves to possibility to pass more properties in the future... but I don't know if it's worth it yet.

I have just changed the input signature of user callbacks in v4, on the v4 branch of the project. functionInit, functionBefore etc are now called like this: callback(instance, helper). In the case of functionBefore and open callbacks, helper.event will hold the triggering event if there was one, or is null otherwise.
If you upgrade to v4, beware that there are breaking changes. All necessary information is included in the updated bundled documentation. Thank you for the suggestion.

Tooltipster v4 is out and passes the event through the helper. Thanks for your input.
What's new in v4: #565
Migration guide from v3 to v4: #566


bump pyrlp version to get rid of deprecation warnings

What was wrong?
rlp==1.1.0 raises deprecation warnings.
How was it fixed?
updated to >=1.2.0 that has the fix for the deprecations warnings.
Cute Animal Picture

The warnings aren't actually gone.  Need to do one more PR to pyrlp to fix them (thought they were already fixed but I was wrong)


Buggy textwrapping on mobile

It's maybe a bit weird putting an issue on your personal blog, but it's not because of the content. Currently deep into your blogpost about Rust and reasoning about types, and its good! Keep up the good work!
However I have a problem when trying to read the blogpost because the text doesn't wrap correctly. The header is displaying correctly, but the main content is overflowing the edge of my screen. Hence I need to zoom out to be able to see it, and that makes it hard to read. This is probably a stylesheet related problem.
I looked through site.css, and on line 84 I found a missing colon. This missing colon shouldn't be the issue, but I cannot find any other error-inducing lines. Hence this might be related to the issue, but I'm highly uncertain (Sorry for the lack of a link to the line of code, but I am currently on my phone and unable to create a link).
I'm using Chrome 64.0.3282.137 on Android 7.0.0.

Thanks for the report! Definitely not weird to me, in fact, very appreciated. :)
I don't have an Android device to test, but I did fix the typo you pointed out. Can you test if that fixed it? If not, I'll probably have to install an Android emulator to play around or something.

It might also be a result of the way you have linebreaks in the markdown-files. Maybe if you test it in Chrome with responsive layout you'll see the same issue as me?

The problem only occurs on specific blogposts that contain images and code. Maybe it's because of the code blocks. Again just guessing :thumb:

Ah, yeah, it is actually reproducible in desktop Chrome. That's promising. It looks like the issue is indeed the source code blocks. I've shrunk their font-size which is a sort of temporary fix (at least works on the latest post), but it's less than ideal. Of course, this is the problem with preformatted text and small displays.

And code blocks are set to white-space: pre-wrap now, so, it should be totally fixed. :)

Ah yeah, I'm familiar with the problem.. I've had troubles with preformatted text before. I usually delt with the problem by not preformatting text, but that's a nasty solution when you want to open up a file in an editor that doesn't support wrapping text on long lines.
Another solution might be to add white-space: normal; to code-blocks. This will cause line breaks in code, which is generally ugly..
A third solution could be to make the codeblock have a percentage width and make the user scroll horizontally within the codeblock to view the code on smaller devices. This is in my opinion a clean solution.


resolution of save_png output

It'd be nice to be able to save a figure as a higher resolution PNG than how it shows up in a notebook.  The relevant javascript code is around here.
Instead of that, perhaps the type of the output could be an option so that one could programmatically save to SVG instead of PNG.  That might be an easier change (the code is around here).

Solved in #660 with a save to SVG option


fix/raise sync limit

Currently, the limit for concurrent sync jobs per user is 3.  While such a limit may be appropriate for ad hoc syncs invoked from the UI by many users, we have replaced syncs from the UI with backend sync jobs, all of which run under the maps data account.  This will enable a greater volume of datasets to be synced simultaneously.

Changes look ok. Only thing I will suggest is that we should merge the changes to blp_dev.
In Dev/QA, we are using blp_dev build. Once it looks ok in QA, then same change will be merged to blp_prod.

The changes have been deployed to QA and dev and tested there, and have also been tested on top of blp_prod on my local PC. I can submit a pull request for blp_dev as well.


⚠ Bofrost.de has degraded performance

In 225e986, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1879 ms

Resolved: Bofrost.de performance has improved in 11b9cf8.


Ensuring MiAIRR is not NCBI specific - RE: CRWG

Hi All,
This is not urgent, but wanted to log it as it is something that we should probably address in coordination with CRWG.
I am pretty sure that we discussed this, but I can't seem to find that discussion in the issues... I think we agreed that the standard should use NCBI examples but not explicitly state that NCBI should always be used...
I raised this issue at the Common Repository Group meeting a fair while ago (https://github.com/airr-community/common-repo-wg/issues/10) about wording that is too NCBI specific (their Recommendation 4:). The group agreed that this was probably not appropriate but that the wording came from the Minimal Standards working group and that the issue should be agreed by Minimal Standards and perhaps provide some alternate wording.
Current wording is: "Recommendation 4: For long-term storage, data and metadata should be deposited in the Sequence Read Archive (SRA)and GenBank, per the recommendations established by the AIRR Minimal Standards Working Group. The AIRR Working Groups should work with SRA/GenBank to customize metadata capture for AIRR data." Note the explicit mention that it should be deposited in SRA/Genbank.
I suggested changing the wording to something like this:
"Recommendation 4: For long-term storage, data and metadata should be deposited in one of the International Nucleotide Sequence Database Collaboration (INSDC) or similar archives such as SRA, Genbank, and ENA, per the recommendations established by the AIRR Minimal Standards Working Group. The AIRR Working Groups should work with the INSDC archives to coordinate the accurate gathering and storage of metadata for AIRR data."
It would be good if we could provide the CRWG some feedback on this so we can close off the issue.

We had a related dicussing several month ago, when we were working on the GenBank specification. The two sentences that we had in the preface were:
"In general, it is RECOMMENDED to deposit section 5 and 6 information in a database compliant with the recommendations of the AIRR common repository working group (WG) [REF]. However, in terms of standard compliance, it is sufficient to deposit the required information in other general-purpose databases, if an AIRR-accepted specification on information mapping exists for the respective database."

CRWG recommendation 4 has now been broadened to cover all INSDC databases (commit c8e751a).


Switch from display name to UID

Fixes #88
Using the displayName property is brittle. It usually worked because by default, all our AzDo instances set the displayName to match the WhoIs database. But, if they were different, it failed.
Fixes #86
Avoid excess requests by caching the results of queries to match GitHub IDs to Microsoft emails.

This is now ready for review and merging.


suggested changes to AssetLineageEventType

AssetLineageEventType has
PROCESS_CONTEXT_EVENT                   (0, "ProcessContextEvent", "Has the full context for a Process"),
TECHNICAL_ELEMENT_CONTEXT_EVENT         (1, "ProcessContextEvent", "Has the full context for a technical element"),
CLASSIFICATION_CONTEXT_EVENT            (2, "ProcessContextEvent", "Has the full context for a classified element"),
UPDATE_ENTITY_EVENT                     (3, "UpdateEvent", "Has the entity that is being updated"),
DELETE_ENTITY_EVENT                     (3, "DeleteEvent", "Has the entity to be deleted"),

I notice DELETE_ENTITY_EVENT has the same number (3) as update.
ProcessContextEvent is in 3 of the events.
I suggest removing the "Has the " from the start of each description.
Is the description of CLASSIFICATION_CONTEXT_EVENT  correct? I assume that this event would occur when an element is declassified as well - in this case the event is not for a classified element.
Maybe talk of the asset getting a classification change; or will we get this event for a glossary term classification as well (if so do we need 2 types of events one for assets and one for glossary terms).
I am wondering whether UPDATE_ENTITY_EVENT should be UPDATE_ASSET_EVENT, and  DELETE_ENTITY_EVENT should be DELETE_ASSET_EVENT - so it is very clear what we are dealing with.
I am wondering whether we need asset create and asset restore events?

Thanks David for pointing it 1 and 2 will be fixed. Regarding 4 when we deal with classification we will see it is not is the scope for next release so there has not been any investigation for the cases we can have.
For 5 we delete and update entities that are not assets so I don't see a point of changing it and for 5 if we handle events of those in the future then will be added now it is not necessary.


SQLite problem.

var db = $cordovaSQLite.openDB({name:"banco.db"});
$cordovaSQLite.execute(db, 'CREATE TABLE IF NOT EXISTS registros (id integer primary key, data text)');
ERROR: Uncaught TypeError: Cannot read property 'openDatabase' of undefined

Could you put together a minimal reproduction of this issue here or in a github repo that I can pull to investigate this issue for you?  I'll re-open this when you do that.


Omni for Terminal(Unix and Powershell)

I would like to suggest the Omni theme for operating system terminals as well, besides that it would be something totally fun! In case you need my help, I make myself available ;)
I opened the issue here because I had no idea where to open it otherwise.

Exists from Hyper, but I understand u
Do U want from Power Shell, Zsh, CMD and others, it's a good idea.

We still do not have these options, but feel free to send us a suggestion.

Suggestion -> https://github.com/vilelagit/omni-terminal-app.

Can I start developing the theme for Linux terminals and send the suggestion to you? I was thinking of doing something like ["https://github.com/Mayccoll/Gogh]"("Gogh")

Suggestion --> https://github.com/GuiLra/tilix-omni

Suggestion Omni for vim

Yeah, I'would love Omni form vim! And Kitty too, but if there was for zsh, it would cover "all" terminals.

Suggestion Omni for vim

Did you who do this?

Suggestion --> https://github.com/Mdsp9070/kitty-omni

Did you who do this?

Yes.

Oh, I really like it! Did you have a repo or a vim script to use it?

Oh, I really like it! Did you have a repo or a vim script to use it?

No, but I can create a repo.

Ok then! I thought to edit the offcial dracula theme, however I'm not used to vim scripts

Suggestion --> https://github.com/GuiLra/vim-omni

Thank you so much! If I want to change the constants color, what I need to change?

You need to go in autoload/omni.vim

Ok then, thank you!

I'll be more specific: When declaring variables on javascript/typescript, variable name is white, however, on omn theme to VScode, variable name is purple. The dracula/omni vim theme have a file "typescript.vim" that set color to each type of word, however I didn't find where to change the variable name color, only the variables keywords color (let and const).

Suggestion --> https://github.com/Mdsp9070/alacritty-omni

Hey guys, we really appreciate your conversation and enthusiasm around the theme 💜
Soon we are going to include new themes and I'm going to reach out on Twitter, so make sure to follow me there.
Thanks again for all your contributions to the project. I'll be closing this issue now, but feel free to continue the conversation!


Use standard id as MODEL_ID.

Use standard id as MODEL_ID.

@michellegong-google we will connect with you about a new process for Model Garden notebooks. I will close this PR for now.


DCOS-46615 - Retry downloading pkgpanda pkg if file size incorrect

High-level description
AWS S3, from which we download pre-built pkgpanda packages, might sometimes end the connection before the package has been fully downloaded. (See https://github.com/aws/aws-sdk-js/issues/312 and https://github.com/boto/boto3/issues/540 for more context on this)
In our case that leads to invalid tar.xz archives which cause unexpected end of input errors and result in faulty builds of DC/OS (dcos_generate_config.sh) which contain these invalid archives and then result in install-time errors for users. See this comment for an investigation into how this can affect installation errors: https://jira.mesosphere.com/browse/DCOS_OSS-4097?focusedCommentId=219259&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-219259
This change here adds a sanity check to the download function used by pkgpanda. It checks whether the final file size (after flushing the file to disk) matches the Content-Length we get from S3. If it doesn't match, it sleep for 2, 4, 8, ... seconds and then retries until it either downloads the file completely or the retries are exhausted. In that case, it raises an exception.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

[DCOS-46615] Pkgpanda - package dcos-image - xz: (stdin): Unexpected end of input - JIRA

Related tickets (optional)
Other tickets related to this change:

[DCOS_OSS-4097] pkgpanda: Explicitly create user groups for all users - JIRA

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: it's internal behaviour that's not exposed to the user
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: I didn't include a test yet, since that would need to involve setting up a mock http server etc. and I wanted to get input on this first
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label Ready for Review

@gpaul @adamtheturtle Can you re-review? I removed the useless legacy code, worked in all of your suggestions and switched to retrying – the only thing left is the long-running thread for the mock http server, which will run until the end of the test suite, I guess. I don't think that's a huge issue, but I'll look into it.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot sync

@mesosphere-mergebot sync


Added a meaningful PR template (Alternative 1)

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed tickets
none

Related issues/PRs
#2080

License
MIT

Documentation PR
none

What's in this PR?
I'd like to put an alternative proposal to #2080 up for discussion. This version puts a focus on:

Usability: Reduce the number of interactions needed to adapt the template.
Conciseness: Short and concise text that is easily understood.
Usefulness: Remove everything from the template that is not commonly needed.
Examples: Provide code examples. They speak more than thousand words.

Why?
At the moment, it's hard to understand the PRs created in this repository without deep inside knowledge. Both #2080 and this PR try to fix this.

That's simpler, indeed :)


Print warning instead of error in case of unstable cluster

Fixes: Issue #4284
Solution/Idea
Since the code doesn't exit, the error messaging might be confusing to users. Changed it to Warn
INFO Operator network is progressing
INFO Operator network is progressing
INFO Operator network is progressing
INFO Operator network is progressing
INFO Operator network is progressing
INFO Operator network is progressing
INFO Operator network is progressing
WARN Cluster is not ready: cluster operators are still not stable after 10m0.695631268s
INFO Adding crc-admin and crc-developer contexts to kubeconfig...
ERRO Cannot update kubeconfig: Head "https://oauth-openshift.apps-crc.testing:443": read tcp <IP_ADDRESS>:60782-><IP_ADDRESS>:443: read: connection reset by peer
Started the OpenShift cluster.

The server is accessible via web console at:
  https://console-openshift-console.apps-crc.testing

Log in as administrator:
  Username: kubeadmin
  Password: 3NM8K-C5kvg-YTRW4-FhiUM

Log in as user:
  Username: developer
  Password: developer

Use the 'oc' command line interface:
  $ eval $(crc oc-env)
  $ oc login -u developer https://api.crc.testing:6443

Testing
crc start and cluster operators should not get ready within the timeout. I did it by cordoning the cluster node and running start again.

@vyasgun can you check in case of ERRO Cannot update kubeconfig: Head "https://oauth-openshift.apps-crc.testing:443": read tcp <IP_ADDRESS>:60782-><IP_ADDRESS>:443: read: connection reset by peer Started the OpenShift cluster. the error code is non-zero ?

@praveenkumar No. Do we want it to return a non-zero exit code?

@praveenkumar No. Do we want it to return a non-zero exit code?

For any error, yes we should return non-zero otherwise we should change it to warn but I think if we are not able to update the kubeconfig file then tell user how they can still access it.

@praveenkumar In theStart function, only 2 logging.Errorf() statements have been used and neither of them is followed by a non-zero return.
Also, kubeconfig is being updated in other places inside the function and all of them except the last one are returning an error. For example:
https://github.com/crc-org/crc/blob/main/pkg/crc/machine/start.go#L603
https://github.com/crc-org/crc/blob/main/pkg/crc/machine/start.go#L528
I'm not sure if there is a particular reason for these statements and the differences (or if it's just an oversight). Additionally, I think if updating kubeconfig is grounds for a non-zero return, so is an unstable cluster (to indicate a failure in Start). We should return these errors in the end and put any extra processing that might be still required in defer so it's always executed.

Additionally, I think if updating kubeconfig is grounds for a non-zero return, so is an unstable cluster (to indicate a failure in Start).

We could return a different error code in both cases when crc completes. Different error codes we might want to ignore 'cluster unstable'
The 'cannot update kubeconfig' message deserves to be made a lot more userfriendly :)

Additionally, I think if updating kubeconfig is grounds for a non-zero return, so is an unstable cluster (to indicate a failure in Start).

We could return a different error code in both cases when crc completes. Different error codes we might want to ignore 'cluster unstable'
The 'cannot update kubeconfig' message deserves to be made a lot more userfriendly :) Explain what won't work when this fails (I think this only means kube contexts can't be used, and that an explicit login to the cluster will be needed).

Yes, it should tell user how to access the cluster (like export KUBECONFIG=$HOME/.crc/machine/crc/kubeconfig or use oc --kubeconfig=$HOME/.crc/machine/crc/kubeconfig . They should able to debug or check which cluster operator is not in available state.

We probably can get this in, and create follow-up issues for the various improvements that have been discussed during the review?

@vyasgun Can you create the follow up issue which is discussed here? Once follow up issue is created we can merge this one.


SAA-991: Add option for setting location to Off Wing

Codecov Report
Patch coverage: 80.00% and no project coverage change.

Comparison is base (3d4054c) 85.57% compared to head (d262a0e) 85.57%.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #552   +/-   ##
=========================================
  Coverage     85.57%   85.57%
- Complexity     2626     2631    +5
=========================================
  Files           307      307
  Lines          9405     9420   +15
  Branches        665      671    +6
=========================================
+ Hits           8048     8061   +13
  Misses         1022     1022
- Partials        335      337    +2

Files Changed
Coverage Δ

...activitiesmanagementapi/service/ActivityService.kt
76.26% <55.55%> (-0.32%)
:arrow_down:

...ps/hmppsactivitiesmanagementapi/entity/Activity.kt
92.71% <100.00%> (+0.09%)
:arrow_up:

...pps/hmppsactivitiesmanagementapi/model/Activity.kt
100.00% <100.00%> (ø)

...hmppsactivitiesmanagementapi/model/ActivityLite.kt
100.00% <100.00%> (ø)

...nagementapi/model/request/ActivityCreateRequest.kt
94.73% <100.00%> (+0.14%)
:arrow_up:

...nagementapi/model/request/ActivityUpdateRequest.kt
100.00% <100.00%> (ø)

...activitiesmanagementapi/util/TransformFunctions.kt
79.41% <100.00%> (+0.06%)
:arrow_up:

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


Add laser pen feature

Adding a features to use laser pen while teaching would be really helpful for the teachers.
Expected behavior: It should behave like normal pen, just the difference should be that after highlighting a certain text or notes with it should disappear after few seconds.
Any suggestions from you @goliakshay357 for the expected behavior?

hey, can I add the required user laser pen feature?


Can rwa-desktop be updated to match latest release?

Hi,
Thanks for your project.
Can the rwa-desktop release be updated to match latest rclone-webui-angular release?
Thanks

The update is automatical. It will fetch lastest version on launch.

Ok, cool. Is there a way to verify that? e.g. show version in the app


CPU usage during idle listening 50%

I see that when GlaDOS is sitting idle and just "Listening..." my CPU usage is hovering at 50% usage on a 14900k.
Is this expected?  Im just tryiong to determine if this is expected or if im not using a Cuda library somewhere.
This is with the recent windows installer.

Seems like its inferencing on CPU.

Im still troubleshooting.  Seems like everything is running on cudda except for onnxruntime.  When I check my device info with ```

import onnxruntime as rt
rt.get_device()
'GPU'

Make sure you have uninstalled onnxruntime before installing onnxruntime-gpu.

Make sure you have uninstalled onnxruntime before installing onnxruntime-gpu.

while in venv I did
pip uninstall onnxruntime
pip uninstall onnxruntime-gpu
pip cache purge
pip install onnxruntime-gpu
Still sits at 45-50% usage.    It sees the device as GPU but somehow sets the provider to CPU.

Seems this is CPU only.
https://github.com/snakers4/silero-vad/discussions/388


Possibility to reset some options

There are situations when we need to reset the offset parameter after window resize. For example: after a media query will be applied, a fixed-position navigation menu will have another height. So IMHO this library should implement a common for jQuery plugins way to apply a new option.

Thanks @C4Grey, this is something I'll pick up in the next round of updates.

Now in version 0.1.13 there is a method called setOptions you can parse an object to update the initialisation options.


home-manager: improve handling of conflicting files

Description
When files conflict during activation, home-manager will also print the path of the source file that wants to overwrite the other.
I think it would be even better if compared the files on conflict to determine if there actually is a conflict (which would resolve #1213), but this would create a dependency to diffutils and I don't know if that's okay.
Checklist

[x] Code formatted with ./format.

[x] Code tested through nix-shell --pure tests -A run.all.

[ ] Test cases updated/added. See example.

[x] Commit messages are formatted like
{component}: {description}

{long description}

See CONTRIBUTING for more information and recent commit messages for examples.

Thanks! Rebased to master in 6c7a0313673687368a33197e58bc28f4290ec244.

About diffutils, the activation script already depends on it but I'm skeptical about silently replacing actual files with symlinks in general, regardless of whether the content of the files is equal. Perhaps with a new Boolean option replaceIfEqual or something.

If the files are equal, do we need to replace them with a symlink? Or can we simply leave them be?


[Feature] v5 with forked handcraftedinthealps/elasticsearch-dsl

Could you please add a release for v5 with handcraftedinthealps/elasticsearch-dsl instead of ongr/elasticsearch-dsl?
ongr/elasticsearch-dsl requires symfony 5 and this prevents an update to laravel 10, which requires symfony 6.

Hey. Feel free to send a PR

I think here, we need to initialize a v5.x branch, and we need to release version 5.x from that branch. We can initialize that branch from tags, what do you think? @matchish @m-lotze

This is the latest 5.x tag https://github.com/matchish/laravel-scout-elasticsearch/releases/tag/v5.0.2

Completely agree

I have forked the repository, created a branch from v5.0.2 and committed the changes to composer.json.
https://github.com/m-lotze/laravel-scout-elasticsearch/tree/v5
If you could create a branch for v5, i can submit a pull request.

@m-lotze I've created 5.x branch could you  push the PR?

Sure. Repushed the pull request to 5.x.

merged

Great. Thank you.


Create a Visual Studio Code extension

Hi @Gama11 - this is amazing work, really nice!
I wanted to use this with "format on save" in visual studio code, so have started the work necessary to make it an extension.

I had to change how errors are logged, as I was receiving a compile error earlier
I added hxml files, as I'm more familiar with working with these. I can remove if desired
I added the boilerplate to generate the extension and run it in debug mode. You run the project from the "Debug" tab in VSCode, and it will launch a new window with the autoformatter active. (You may have to configure formatOnSave to be turned on for your workspace)

Would you be interested in merging this or publishing it? It might also be good to include it in the main vshaxe extension, but that would require more co-ordination between repos. When I considered that, I thought having two extensions to install isn't that bad :)

(p.s. I'm also working on some line wrapping for array and object declarations over a certain length, but will put in a separate PR)

While I'm happy somebody else is excited about code formatting, I now wish I had written a readme to save you this work. :) Here's the deal: this is already integrated in vshaxe / haxe-languageserver, but locked behind #if debug:
https://github.com/vshaxe/haxe-languageserver/blob/d7799fa0570b91f10ec272ee4e7287f0224acf09/src/haxeLanguageServer/Context.hx#L257-L259
So if you install vshaxe from source and make a debug build, you can use the formatter.
I consider this project more of an unfinished experiment... The approach I took with using a parse tree means the formatter will never be able to deal with conditional compilation properly, see also the thoughts I wrote down here.
Recently I've been wondering if we could use @AlexHaxe's tokentree library. This would be similar to clang-format, which is also based on tokens rather than a proper parse tree, it seems, and is able to deal with conditional compilation as a result. Right now I don't really have time for that though.

Hahaha no worries. Thanks for the explanation! And sorry I missed the discussion thread.
Would you be interested in a PR that makes the formatter available behind a setting, rather than requiring a debug build? I understand if you'd prefer to keep it hidden until a more complete implementation is available.

Maybe we could have an undocumented setting for it... Like you guessed, I don't really want people to start relying on this too much yet and switch over their projects, since it's not the "proper solution" I'm hoping is going to exist one day.
How usable have you found it so far in practice?
Also, nice to see you getting back to some Haxe dev. ;)

Thanks! I don't use Haxe at my current job (mostly react+flow and some elm), but I still love using it for side projects.
I'll take a look at tokentree, I've gotten really attached to prettier, elm-fmt and go-fmt and don't want to have to format my own code anymore :) This project worked on simple things I tried, but it looks like tokentree has some fault tolerance as well, which might be good to include

Since there is a certain amount of overlap between a checkstyle and a formatter tool, it might make sense to build some kind of common API / layer, so that both have the same information and can make decisions based on identical data.
e.g. haxe-checkstyle has an indentation check based on tokentree. It operates in two stages:

gather information and build a model of ideal indentation per line
compare model with reality

The model currently has three arrays with one entry per line each. One just holds indentation levels, one holds excluded lines (comments, multiline strings) and the third holds lines of wrapped code.
Tokentree doesn't store whitespace and has no concept of line numbers, all position are byte offsets calculated from file start.

I've built an initial version of a tokentree based formatter: https://github.com/HaxeCheckstyle/tokentree-formatter
There are quite a few things missing, most of them should be fairly easy.
Building a VSCode extension around it should also work and would be able support full or partial formatting (line based).

A few months later, we now have a working haxe formatter! \o/

https://community.haxe.org/t/new-formatter-haxelib-library/987
https://github.com/vshaxe/vshaxe/wiki/Formatting

I'm going to mark this repo as "archived".


Support for inclusion as git submodule + add_subdirectory?

What platform/OS are you using?
Ubuntu 18.04
Which version of the SDK?
1.6.0 (or whatever git master is currently)
What compiler are you using? what version?
g++-9
What are your CMake arguments?
none
Can you provide a TRACE level log? (sanitize any sensitive information)
I'm trying to include the sdk as a git submodule and subsequently as a add_subdirectory dependency in a larger cmake project. For example ideally I would like to write a cmake file such as:
add_subdirectory(external/aws-sdk-cpp/)
target_link_libraries(test aws-cpp-sdk-s3)

Is this supported? I can't seem to get this to work. For example, Issue #1210 appears to make compilation fail (make seeks write permissions to a system directory)

Hi @mpetri ,
Right so, the PR is trying to solve a sudo call that happens when you don't manually install the SDKs dependencies, we do these automatically and by default they try to install themselves in the local lib folder which on some cases require sudo calls. If you're having the same issue, it'd work by doing "sudo cmake", or installing the dependencies individually or specifying an installation path.
The second thing is, we don't "support" what you're trying to do in like, we don't have documentation or examples and we wouldn't consider it a bug if it didn't work, but I see no reason why you wouldn't be able to do this, so I might be able to help you get it to work.
For now, I'll try to reproduce this and meanwhile could you tell me, what error are you getting and at what step?

Hello, thanks for the response!
A simple example to reproduce what I'm trying to do:

mkdir test_aws
cd test_aws
git clone https://github.com/aws/aws-sdk-cpp.git
Create CMakeLists.txt with content:

project(test LANGUAGES CXX)

add_subdirectory(./aws-sdk-cpp/)
add_executable(test test.cpp)
target_link_libraries(test aws-cpp-sdk-s3)

mkdir build
cd build && cmake ..
make test

So preferably the aws sdk should be built in the build directory and not installed system wide and I should just be able to add for example the aws-cpp-sdk-s3 target.
Quite a few other c++ libraries work like this. For example many logging frameworks etc.

ah, I misunderstood what you're trying to do there, this might help you then:
Basically, you'd have to build and install the libraries before you can use them.
Let me know if the guide helped.

I followed the instructions you provided before and it works. I just don't like that the sdk (1) has to be installed it system wide (2) I can't just use add_subdirectory and have the whole code for my application be in one directory managed by git and git submodule.
Closing this issue as I think it is resolved. Thanks anyway.


Build failure: nixosTests.installed-tests.pipewire (pipewire)

Steps To Reproduce
At master:

nix build .#nixosTests.installed-tests.pipewire

Build log
>   File "/nix/store/sffpwqark4h2969lwniqicnfpzvqsmc7-nixos-test-driver-1.1/lib/python3.11/site-packages/test_driver/machine.py", line 611, in succeed
       >     raise Exception(f"command `{command}` failed (exit code {status})")
       > Exception: command `gnome-desktop-testing-runner  -d '/nix/store/wkw7lszrap1x9hbca4snflcn6vr6lc15-pipewire-1.0.7-installedTests/share'` failed (exit code 2)

Logs: https://termbin.com/kvnc
Additional context

Test is failing for master.

(Opening issue to track issue until resolution.)
Notify maintainers
CC @kranzes @k900

It's a known thing, our VMs don't have sound outputs.

It's a known thing, our VMs don't have sound outputs.

Can't it be marked broken?


TextSelection on could misbehave inside a Nested Overlay

The following code can show a couple of problems with the TextSelection on Android.
import 'package:flutter/material.dart';

class TextSelectionHomePage extends StatefulWidget {
  _TextSelectionHomePageSate createState() => _TextSelectionHomePageSate();
}

class _TextSelectionHomePageSate extends State<TextSelectionHomePage> {

  TextEditingController _controller;
  @override
  void initState() {
    _controller = TextEditingController(
      text: "This is a test that shows some odd behavior with Text Selection!"
    );

    super.initState();
  }

  @override
  void dispose() {
    _controller.dispose();

    super.dispose();
  }

  @override
  Widget build(BuildContext context) {

    Overlay overlay = Overlay(
      initialEntries: [
        OverlayEntry(
          builder: (context) => Center(
              child: TextField(controller: _controller),
          )
        )
      ],
    );

    return Scaffold(
        body: Container(
          color: Colors.grey,
          child: Center(
              child: Container(
                  color: Colors.red,
                  width: 300,
                  height: 600,
                  child: overlay
              )
          ),
        )
    );
  }
}

A nested overlay could be desirable for certain reasons, but the TextSelection on Android doesn't do very well with it.
If the overlay's width isn't as wide as what the TextSelection toolbar needs, an overflow can be seen. Also, as you move the cursor around while changing the selection size, the toolbar moves around on the screen as well, which feels weird. Finally, if a ClipRect is placed around the nested overlay, then the Toolbar gets cut off.
Could the TextSelection just use the navigator's overlay instead of the nearest overlay in the tree?
Here is a screenshot of the behavior I'm seeing.

At the very least, if the toolbar could remain aligned with the overlay it is inside, that would be a huge improvement. The size of the overlay being too small is something a developer would need to avoid I guess, although maybe using an OverflowBox or something could potentially help with that too.

Another, much bigger issue found with this, is that tapping on the buttons in the toolbar doesn't register a tap at all, so the toolbar is completely useless.
I also wonder if #42774 could be related to this.
/cc @justinmc

@justinmc My original patch proposed in #42774 actually fixes this bug!

The following patch fixes the problem. It however, does not fix #42774.
lib/src/widgets/text_selection.dart patch
--- a/packages/flutter/lib/src/widgets/text_selection.dart	2019-09-22 10:17:46.000000000 -0400
+++ b/packages/flutter/lib/src/widgets/text_selection.dart	2019-10-09 10:14:13.000000000 -0400
@@ -283,12 +283,12 @@
        assert(handlesVisible != null),
        _handlesVisible = handlesVisible,
        _value = value {
-    final OverlayState overlay = Overlay.of(context);
-    assert(overlay != null,
+    _overlay = Overlay.of(context, debugRequiredFor: debugRequiredFor);
+    assert(_overlay != null,
       'No Overlay widget exists above $context.\n'
       'Usually the Navigator created by WidgetsApp provides the overlay. Perhaps your '
       'app content was created above the Navigator with the WidgetsApp builder parameter.');
-    _toolbarController = AnimationController(duration: fadeDuration, vsync: overlay);
+    _toolbarController = AnimationController(duration: fadeDuration, vsync: _overlay);
   }

   /// The context in which the selection handles should appear.
@@ -361,6 +361,9 @@

   TextEditingValue _value;

+  /// The Overlay on which the toolbar and handles will be displayed
+  OverlayState _overlay;
+
   /// A pair of handles. If this is non-null, there are always 2, though the
   /// second is hidden when the selection is collapsed.
   List<OverlayEntry> _handles;
@@ -410,7 +413,7 @@

-    Overlay.of(context, debugRequiredFor: debugRequiredFor).insertAll(_handles);
+    _overlay.insertAll(_handles);
   }

   /// Destroys the handles by removing them from overlay.
@@ -426,7 +429,7 @@
   void showToolbar() {
     assert(_toolbar == null);
     _toolbar = OverlayEntry(builder: _buildToolbar);
-    Overlay.of(context, debugRequiredFor: debugRequiredFor).insert(_toolbar);
+    _overlay.insert(_toolbar);
     _toolbarController.forward(from: 0.0);
   }

@@ -528,8 +531,8 @@
         renderObject.getEndpointsForSelection(_selection);

     final Rect editingRegion = Rect.fromPoints(
-      renderObject.localToGlobal(Offset.zero),
-      renderObject.localToGlobal(renderObject.size.bottomRight(Offset.zero)),
+      renderObject.localToGlobal(Offset.zero, ancestor: _overlay.context?.findRenderObject()),
+      renderObject.localToGlobal(renderObject.size.bottomRight(Offset.zero), ancestor: _overlay.context?.findRenderObject()),
     );

     final bool isMultiline = endpoints.last.point.dy - endpoints.first.point.dy >

The patch fixes the alignment issue and the touch issues. It does not fix the overflow issue.

Another patch is needed for the Material text selection code, as it uses the screen size for laying out the toolbar.
lib/src/material/text_selection.dart patch
--- a/packages/flutter/lib/src/material/text_selection.dart	2019-11-01 13:46:10.000000000 -0400
+++ b/packages/flutter/lib/src/material/text_selection.dart	2019-11-01 13:42:34.000000000 -0400
@@ -162,11 +162,13 @@
         : startTextSelectionPoint.point.dy + _kToolbarHeight + _kToolbarContentDistanceBelow;
     final Offset preciseMidpoint = Offset(position.dx, y);

+    // get the Overlay's render box
+    RenderBox overlayBox = Overlay.of(context).context?.findRenderObject();
     return ConstrainedBox(
       constraints: BoxConstraints.tight(globalEditableRegion.size),
       child: CustomSingleChildLayout(
         delegate: _TextSelectionToolbarLayout(
-          MediaQuery.of(context).size,
+          overlayBox.size,
           globalEditableRegion,
           preciseMidpoint,
         ),

I have created another separate bug for the Overflow issue, because it also happens without a nested overlay, when the device has the Large Display setting turned on.
The bug is #44005.

It sounds like the problem is that the toolbar is going outside its overlay, in which case the hit testing is expected not to work, since the hits would only get to the toolbar if they're first inside the overlay.
Seems like we probably just want to always use the outermost overlay ("rootmost" maybe) when displaying a toolbar. That would be consistent with the Android platform's behaviour of having the toolbar be a floating window.

@Hixie  Yes, if I try to do the type of thing I'm trying to accomplish, but in native Android, the toolbar would float around outside of the equivalent parent view. So I think that your idea is also a suitable one to handle this, as it would be consistent with expectations there. Are there any plans to do some kind of overflow menu to fix #44005 and a magnifying lens effect for text selection?

The "plan" is for us to fix all our bugs, especially fidelity bugs like that one. The question is more one of timeline, and that is much harder to predict...

The text selection overflow problem is being tracked in https://github.com/flutter/flutter/issues/35826, and someone has opened a pull request in progress for the overflow menu in https://github.com/flutter/flutter/pull/39624.  I think that overflow problem is probably the most embarrassing bug on my radar right now, so I hope we can finish a fix for it soon.
The magnifying glass effect is being tracked in https://github.com/flutter/flutter/issues/9507.  It lost a bit of steam when Apple removed it from iOS13, but we should still implement it for Android.

I've got a working solution to using the root overlay. We'll update our PR in the coming days/weeks.

I have updated the PR "ef94e59b6" to commit Danny's solution.
From the original PR, I tried to revert the change in "packages/flutter/lib/src/material/text_selection.dart", but I might have deleted the file instead. Can't find a way to revert the deletion. Need help on that and review the new changes. Thanks!

Okay. i have got everything in the PR back on track now. Please review the PR to using the root overlay. Thanks!
https://github.com/flutter/flutter/pull/44018

@justinmc @Hixie  Have you taken a look at the PR #44018?

Just submitting a review, sorry for the delay!


Alpha PNG may cause constant burn rather than raster.

The transparency loaded with the png images might cause issues that are not accounted for. Needs direct testing. See notes at #71

Mentioned in notes at #71; TIFF images with an alpha channel included (embedded in inkscape SVG) also constant burned for me.
Will try a few other image converters to make sure it's not any other specific file issue. Not sure what's driving the problem; other than a transparent background may "appear" black to the translation.

Most transparents are transparent black. Which is a black and thus gets stuck on. Though I haven't actually checked the code itself, but that makes sense.

This issue is closable when #102 gets finished and integrated. I created a different image pixel parser for RGBA vs. RGB. https://github.com/meerk40t/meerk40t/pull/102/commits/4a4de182a8c6bbe90d1843394f07cd1fbc01576e
       elif mode == "RGBA":
            def image_filter(pixel):
                return (1.0 - (pixel[0] + pixel[1] + pixel[2]) / 765.0) * pixel[3] / 255.0

When it has alpha it multiplies the entire thing by the alpha. So 255 is opaque so the color value is scaled with the sum of the pixels. When alpha is 0. The filter can only return 0 which is a do not burn value.


Update regex to look for the last " in a filename

when constructing filenames, the input may look something like this: filename="wei"rd.pdf".
the previous regex expression would stop at the second located ", which caused errors where files contained " in their name.
update the regex expression to not exclude " from a potential match.

v0.2.0


htlc mismatch: predicate not satisfied after time out  - continue

@halseth This issue is related to #1632.
IMHO, the conclusion that it is solved by #1608 is wrong.

--- PASS: TestLightningNetworkDaemon/test_multi-hop_htlc_local_chain_claim (7.50s)
--- PASS: TestLightningNetworkDaemon/test_multi-hop_htlc_remote_chain_claim (7.45s)
--- FAIL: TestLightningNetworkDaemon/switch_circuit_persistence (37.02s)
lnd_test.go:74: Failed: (switch circuit persistence): exited with error:
*errors.errorString htlc mismatch: predicate not satisfied after time out
/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:9428 (0xc089ce)
testSwitchCircuitPersistence: t.Fatalf("htlc mismatch: %v", err)
/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:99 (0xbcaccb)
(*harnessTest).RunTestCase: testCase.test(net, h)
/home/travis/gopath/src/github.com/lightningnetwork/lnd/lnd_test.go:11258 (0xc236ba)
TestLightningNetworkDaemon.func3: ht.RunTestCase(testCase, lndHarness)
/home/travis/.gimme/versions/go1.9.4.linux.amd64/src/testing/testing.go:746 (0x4f6aa0)
tRunner: fn(t)
/home/travis/.gimme/versions/go1.9.4.linux.amd64/src/runtime/asm_amd64.s:2337 (0x45ecf1)
goexit: BYTE	$0x90	// NOP

The test which failed is switch_circuit_persistence. Logic is:  create channels C<->D<->A<->B,  Start C in a mode that cause it not to provide preimages, create 5 invoices by C, make 5 payments by B, check that all nodes has 5 pending HTLCS, restart, check again, Make C send the 5 preimages.
The problem is cause by A not sending the perimages to B.
This can be seen in A log file at time 2018-07-24 11:01:59.662. A received 5 UpdateFulfillHTLC but never forwarded to B. The reason for that is that the channel between A and B was closed at 2018-07-24 11:01:57.437. Relevant error message at
2018-07-24 11:01:57.361 [WRN] HSWC: ChannelPoint(cd518f4905100727cdbb4249b885aec4dba5435086122c3c5ead24127bd6b8b9:0): received unknown message of type *lnwire.ChannelReestablish
All relevant log files are here.
output-39-Carol-02240054.log
output-38-Dave-028fdc5f.log
output-1-Alice-038101c0.log
output-0-Bob-02d3141f.log

Can this be melded into that prior issue rather than opening a new one?

@Roasbeef I opened a new issue for this one as requested by @halseth in #1632 after you decided to close it regardless my comment there that it is not related to #1608.

@offerm Can you open a new issue for the failure, if you believe it is not covered by #1608? Thanks!

Thank you for these logs @offerm! Something defintely seems off here, as we receive an additional channel reestablish after the link has (presumably) already received a prior one. I will start looking into probable causes

Closing for now, since i think this was fixed in #1785


Autogenerated documentation to github pages

[x] setup initial sphinx setup
[x] generate diagrams
[x] setup pipeline adapting from https://circleci.com/blog/deploying-documentation-to-github-pages-with-continuous-integration/

https://jonykalavera.github.io/kafkaescli/


OAK-8910 - Improve OAK Lucene Index Documentation

Let me know if you want me to commit the change.

Let me know if you want me to commit the change.
To svn? Yes, please. I have added the patch to the issue as well.
https://issues.apache.org/jira/browse/OAK-8910


anyone has issue with Android Emulator

I am having issue with Android emulator, basically my emulator don't have any access to internet.
thanks!

seems like not hblock.


Fix unwanted cancellation of Artboard tool caused by switching tools

Fixes a bug caused by previous PR related to aborting of transactions
also adds keyhints for cancellation (Rmb/ESC)

!build


WIP: Removal of allowlist from priviledged tests

Description
This change updates priviledged test to consider
only containers from CNF under test. As a result of this change, the 'allowlist_helm_chart_container_names' parameter in the cnf-testsuite.yml configuration file is no longer needed.
Therefore this patch also removes this parameter from the configuration, as well as from all samples and examples.
Issues:
Refs: #1906
How has this been tested:

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[ ] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[ ] Kind cluster

[ ] Have not tested

Types of changes:

[x] 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)
[x] Documentation update

Checklist:
Documentation

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] No updates required.

Code Review

[ ] Does the test handle fatal exceptions, ie. rescue block

Issue

[ ] Tasks in issue are checked off

Thank you for the updates. Waiting for the build to run for the main branch.
I will re-run this build once the main branch is green - https://github.com/cnti-testcatalog/testsuite/actions/runs/8345433746

https://github.com/lfn-cnti/bestpractices/blob/main/doc/cbpps/0004-do-not-run-containers-with-privilege-flag.md#notesconstraintscaveats
https://github.com/lfn-cnti/bestpractices/blob/main/doc/cbpps/0003-exceptions.md#summary

Needs further discussion and updates

lgtm

This change is more or less done, but I am still verifying if all tests are running as expected.

@horecoli rebase and this should be good to merge.
cc: @agentpoyo @HashNuke

Some sample CNFs still have empty arrays:

sample-nonroot
sample_coredns_default_namespace

Some sample CNFs still have empty arrays:

sample-nonroot
sample_coredns_default_namespace

Those two samples were added even after I created this PR, so at that time, they were not there. And now I just rebased and forgot to do some grep to check if there is something new. So I fixed it in the latest change. Thank you :)


Create screenshot: Fix resources not recreated with the right sizes

See https://forum.babylonjs.com/t/babylonjs-5-0-5-5-5-ios-15-4-safari-15-4-issues/30195/27

It is the basis loader test which is failing, so likely not coming from my PR.

cc @RaananW

We just merged https://github.com/BabylonJS/Babylon.js/pull/12662 which is likely the reason. But the CI was fine for that PR?

Oh, I know why. You have to make sure to merge latest after that change goes in because the config needs to point to the correct Basis files.

Actually, never mind. It should still work since we kept the old Basis files at the same location. The visualization test for the basis loader still works on the playground: https://playground.babylonjs.com/#4RN0VF#102.


HDDS-1159. Remove flaky tag from TestContainerStateManagerIntegration

What changes were proposed in this pull request?
Removed the @Flaky annotation from TestContainerStateManagerIntegration.testGetMatchingContainerMultipleThreads because the failure can not be reproduced by repeated execution of the tests in CI.
What is the link to the Apache JIRA
HDDS-1159
How was this patch tested?
By repeated execution of the tests in CI to check if failure can be reproduced but all the tests has passed.
Link for one of the test jobs result:  https://github.com/HD372000/ozone/actions/runs/6165606906/job/16733664079#step:4:3794

Thanks @HD372000 for the patch, and for checking this flaky test.


Incomplete/buggy rule breaks process replay on #4976

x+-y -> x-y rule didn't cover -y+x which is the same because a + b = b + a and my nicer uops always does that, but because this rule didn't cover that case that it was probably supposed to cover process replay broke
Here's diff:

Old rule:  21)))+(-(((val
New rule: val21)))-(((val
etc

process replay diff: https://github.com/tinygrad/tinygrad/actions/runs/9527939440/job/26265125669#step:23:43


⚠ Bofrost.fr has degraded performance

In ac991ee, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1789 ms

Resolved: Bofrost.fr performance has improved in a3e8ec5 after 6 minutes.


Failed to rename container with unknown error

Environment created on HUB. Logined to my peer under admin user.
Trying to rename container to 1:

karaflogs2016-12-02 15-55-25.txt

Disabled functionality for Hub containers. Needs to be implemented on Hub first.
@soffokl please recheck.

Done


Freebase reconciliation service doesn't work

[This was #805, but that got hijacked for a new feature request.]
The Freebase reconciliation service was proxied through the freebaseapps.com domain (ie Acre) which has been shut down.  Freebase itself will be shutdown shortly, so all the machinery associated with it should be removed.
I think most of this has been done, but we need to double check that there are no remaining loose ends.

PR created.
The code was deployed under:
http://<IP_ADDRESS>:3333/
Please help to verify if it works properly and also check the reconsideration part. If need to install some extension, let me know.


Support Renaming File During POST

In Payload.rb, line 206, support user defined filenames. https://github.com/rest-client/rest-client/blob/master/lib/restclient/payload.rb#L206
Scenario: I create a bunch of local files that are unique to my organization methods. When I transmit those files anywhere, I should be able to specify a remote filename. Meaning, when the recipient sees the POST the file's content-disposition header will contain the new filename, not the original filename. My local organization/storage methods mean nothing to others.
Here's how Rest-Client works now:
{
    "filename"=>"AKSDJLKJWNELNAS3823NSA.jpg",
    "type"=>"image/jpeg",
    "name"=>"file",
    "tempfile"=>"#<File:0x007f00091c7888>",
    "head"=>"Content-Disposition: form-data; name=\"file\"; filename=\"AKSDJLKJWNELNAS3823NSA.jpg\"\r\nContent-Type: image/jpeg\r\n"
}

Rest-Client should give me the ability to define "filename", thus renaming the File object to whatever is defined in "filename". In this case, dog.jpg.
{
    "filename"=>"dog.jpg",
    "type"=>"image/jpeg",
    "name"=>"file",
    "tempfile"=>"#<File:0x007f00091c7888>",
    "head"=>"Content-Disposition: form-data; name=\"file\"; filename=\"dog.jpg\"\r\nContent-Type: image/jpeg\r\n"
}

So...picking through the code and seeing use of :original_filename, I managed to hack at this by defining a singleton method on my File object like this:
file = File.new(file_path)
filename = "My_file_name.txt" #Be careful with scope here for the next line
file.define_singleton_method(:original_filename) { filename }
RestClient::Request.execute(
  method: :post,
  url: url
  payload: {
    multipart: true,
    file: file
  }
)


0.63, layering/bases. Is this supposed to work?

I read:
https://github.com/roboll/helmfile/blob/255d92064e232c40c10dddab72e19d66e9211cc5/docs/writing-helmfile.md
Tried this w/ 0.63
helmfile.yaml
bases:
  - myenv.yaml

helmDefaults:
  tillerNamespace: kube-system
  kubeContext: {{ .Environment.Values.kubeContext }}
  verify: false
  {{ if .Environment.Values.wait }}
  wait: true
  {{ else }}
  wait: false
  {{ end }}
  timeout: 600
  recreatePods: false
  force: true

releases:
  - name: test1
    chart: mychart-{{ .Environment.Values.myname }}
    values:
      replicaCount: 1
      image:
        repository: "nginx"
        tag: "latest"

myenv.yaml
environments:
  test:
    values:
      - test.env.yaml

test.env.yaml
kubeContext: test
wait: false
cvOnly: false
myname: "dog"

Exec:
bash-4.4$ ./helmfile --log-level debug -f test.helmfile.yaml -e test apply
processing file "helmfile.yaml" in directory "."
first-pass rendering input of "helmfile.yaml.part.0": {test map[]}
could not deduce `environment:` block, configuring only .Environment.Name. error: failed to read helmfile.yaml.part.0: reading document at index 1: yaml: unmarshal errors:
  line 19: cannot unmarshal !!map into []interface {}
error in first-pass rendering: result of "helmfile.yaml.part.0":
 0: bases:
 1:   - myenv.yaml
 2:
 3: helmDefaults:
 4:   tillerNamespace: kube-system
 5:   kubeContext: <no value>
 6:   verify: false
 7:
 8:   wait: false
 9:
10:   timeout: 600
11:   recreatePods: false
12:   force: true
13:
14: releases:
15:   - name: test1
16:     chart: mychart-<no value>
17:     values:
18:       replicaCount: 1
19:       image:
20:         repository: "nginx"
21:         tag: "latest"
22:

first-pass rendering result of "helmfile.yaml.part.0": {test map[]}
second-pass rendering failed, input of "helmfile.yaml.part.0":
 0: bases:
 1:   - myenv.yaml
 2:
 3: helmDefaults:
 4:   tillerNamespace: kube-system
 5:   kubeContext: {{ .Environment.Values.kubeContext }}
 6:   verify: false
 7:   {{ if .Environment.Values.wait }}
 8:   wait: true
 9:   {{ else }}
10:   wait: false
11:   {{ end }}
12:   timeout: 600
13:   recreatePods: false
14:   force: true
15:
16: releases:
17:   - name: test1
18:     chart: mychart-{{ .Environment.Values.myname }}
19:     values:
20:       replicaCount: 1
21:       image:
22:         repository: "nginx"
23:         tag: "latest"
24:

err: error during helmfile.yaml.part.0 parsing: template: stringTemplate:6:30: executing "stringTemplate" at <.Environment.Values.kubeContext>: map has no entry for key "kubeContext"
in ./helmfile.yaml: error during helmfile.yaml.part.0 parsing: template: stringTemplate:6:30: executing "stringTemplate" at <.Environment.Values.kubeContext>: map has no entry for key "kubeContext"

@bitsofinfo Hey! Thanks for reporting.
Unfortunately, your example won't work due to how the double-rendering works #308. The gotcha here is your go template(=helmfile.yaml) is evaluated "to generate YAML". So {{ .Environment.Values.myname }} needs to know about myname BEFORE the template expression is evaluated.
Try separating your state file with ---, so that myname is available in your last template:
bases:
  - myenv.yaml

---

helmDefaults:
  tillerNamespace: kube-system
  kubeContext: {{ .Environment.Values.kubeContext }}
  verify: false
  {{ if .Environment.Values.wait }}
  wait: true
  {{ else }}
  wait: false
  {{ end }}
  timeout: 600
  recreatePods: false
  force: true

releases:
  - name: test1
    chart: mychart-{{ .Environment.Values.myname }}
    values:
      replicaCount: 1
      image:
        repository: "nginx"
        tag: "latest"

Yeah still doesn't work. No matter how many doc separations one uses, if you specify -e test it still throws errors because, it appears your environments: cannot live inside of a bases: referenced include?
first-pass rendering input of "helmfile.yaml.part.0": {test map[]}
could not deduce `environment:` block, configuring only .Environment.Name. error: failed to read helmfile.yaml.part.0: environment "test" is not defined

@bitsofinfo Thanks for your confirmation, and sorry for the trouble!
It's supposed to work and I think I've written tests to verify it, but something looks broken as you pointed out. I'll take a look asap.

@bitsofinfo #609 should fix this.

cool thanks I'll try it out

Verified this works,


bash: initExtra after autojump config

Description
Allow for initExtra to manipulate results of autojump, eg, remove aliases. I noticed this while trying to use jc
Checklist

[ ] Change is backwards compatible.  - maybe, depends on if someone currently is using initExtra to change things before autojump, i can't think of many cases of that

[x] Code formatted with ./format.

[x] Code tested through nix-shell --pure tests -A run.all.

[ ] Test cases updated/added. See example.

[x] Commit messages are formatted like

If this PR adds a new module

[ ] Added myself as module maintainer. See example.

[ ] Added myself and the module files to .github/CODEOWNERS.

Thanks! Rebased to master in ae8f432a759d42b03ade24f01ed7466869cbbf90.


Towny Assistant tag

Hi there!
Would you be able to add an assistants tag to Depenizen? I asked on the denizen IRC and mcmonkey pointed me here.
There IS already the<EMAIL_ADDRESS>tag. Something like <player.townyrank> would be great, or a<EMAIL_ADDRESS>list.
I'm not really sure how this would work with the custom ranks, but those seem extra niche to me.
As always, thank you for creating Depenizen!
Tea

Added the following tags:
<EMAIL_ADDRESS>- dList of player's nation ranks
<EMAIL_ADDRESS>- dList of player's town ranks
<EMAIL_ADDRESS>- dList(dPlayer) of nation's assistants
<EMAIL_ADDRESS>- dList(dPlayer) of nation's residents
<EMAIL_ADDRESS>- dList(dPlayer) of town's assistants
<EMAIL_ADDRESS>- dList(dPlayer) of town's residents

Holy you work fast. Thank you very much!


In my case the Lottie splash screen is not integrated it have error.

"react-native-lottie-splash-screen": "^1.1.2",
platform (Android)

Join a screenshot or video of the problem on the simulator or device?
this is the launch_screen.xml file.
_**
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
tools:context=".MainActivity"
android:orientation="vertical"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:background="@drawable/launch_screen"

<com.airbnb.lottie.LottieAnimationView
        android:id="@+id/lottie"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:lottie_rawRes="@raw/loading"
        app:lottie_autoPlay="true"
        app:lottie_loop="false"
/>

**_
this is the error message in text.
_*** What went wrong:
Execution failed for task ':app:mergeDebugResources'.

A failure occurred while executing com.android.build.gradle.internal.res.ResourceCompilerRunnable
Resource compilation failed (Failed to compile resource file: D:\Apps\ReactNative\HisabKitab\android\app\src\main\res\layout\launch_screen.xml: . Cause: com.ctc.wstx.exc.WstxParsingException: Illegal processing instruction target ("xml"); xml (case insensitive) is reserved by the specs.
at [row,col {unknown-source}]: [31,5]). Check logs for more details.**_

I don't think the problem lies with this library.
You can refer to this https://stackoverflow.com/questions/23359572/android-studio-execution-failed-for-task-appmergedebugresources-if-projec

I will close the issue.


Suggestion to add ability to sort STpackage servers by initial ping

As it stands now we have multiple STpackage servers listed under stpackage.domain.com, without anycasting we have to rely on a basic DNS round-robin.
Suggestion is to add the ability to ping each IP and return the fastest result, using that as the STpackage server to download an OS PKG from.
For example this one-liner does a rudimentary ping towards a remote server, returning the latency:
for ip in $(dig +short stpackage.domain.com); do ping -c 1 $ip | grep time | head -n1 | awk '{ print $7 }' | tr -d 'time='; done
10.0
5.94 <-- use this one for this run

https://git.glasklar.is/system-transparency/core/stboot/-/tree/main/

This is completed?


[BUG] Crash when starting application

Describe the bug
Crash when CmlLib.Core.VersionLoader.MojangJsonVersionLoaderV2.getManifest calls JsonSerializer.DeserializeAsync() due to Reflection-based serialization disabled.
Logs
Full Stacktrace + exception description:

Environment:

OS: Windows 11 (24H2 build 26100.2605)
CmlLib.Core Version: [e.g. 4.0.3]
.NET version: .NET 8.0

Additional context
This is being run as published to folder with "Produce single fil" enabled and targeting net8.0-windows and using JetBrains Rider. Full config screenshot:

currently the library doesn't support trimming. uncheck the 'trim unused assemblies' option.

That did the trick! Thanks!


GraphQL schema-first: fix type checks for conditions

ConditionModelBuilder.checkArgumentIsListOf uses isEqualTo to compare the expected and actual types. This will always succeed if both types are lists, because it doesn't recurse into subtypes. We need to compare the element types instead.
ConditionModelBuilder.checkArgumentIsSameAs might be subject to the same issue.

I don't see a problem with checkArgumentIsSameAs. I think it does not need to check recursive types.

I don't see a problem with checkArgumentIsSameAs. I think it does not need to check recursive types.

See this test.


Bug: new users are created as inactive

Spotted this demonstrating a user trying to sign up with the new team invite codes.

Here's why: https://github.com/natbat/pillarpointstewards/blob/7d41b6c4c8a246d22b3fc6813d04fc1d7729fb21/pillarpointstewards/auth0_login/views.py#L136-L147
That's using the old ActiveUserSignupLink mechanism which has been obsoleted by this new mechanism: https://github.com/natbat/pillarpointstewards/blob/7d41b6c4c8a246d22b3fc6813d04fc1d7729fb21/pillarpointstewards/teams/models.py#L28-L35

I should drop ActiveUserSignupLink entirely to avoid future confusion.

Manually tested with adjunct-flex.0j test user, it worked correctly.


Show current number of characters entered in "make squeak" dialog

The dialog should show the <current number of entered characters>/280
For example: "157/280"
So the user knows how many characters they have already used out of the total allowed.
The content is already set as a state variable:
https://github.com/yzernik/squeaknode/blob/ed9cf92ccc02762a99105dd06631edbef1216e38/frontend/src/components/MakeSqueakDialog/MakeSqueakDialog.js#L41

https://github.com/squeaknode/squeaknode/pull/1936


Providing a sync version

Hi @ricmoo,
I'm opening this issue because I'm interested in using this library instead of scryptsy, as that one uses crypto-browserify in the browser, and that implies a huge bundle that normally doesn't get tree-shaken and doesn't seem to work with Rollup.
The problem is that some projects, like ethereumjs-wallet here, use the sync version of scryptsy. This is not ideal, but can't be changed without introducing a breaking change.
I'm wondering if you are open to adding a sync version to this library.
Thanks!

Yes, this is something I’ve thought about adding. It shouldn’t be too hard, since it can just call the co-routine component without using a setImmediate.
As an aside, if you use my ethers library (or the beta v5 sub-package, @ethersproject/json-wallets) to decrypt an Ethereum Wallet, you get the async version of wallet decrypting, so you can update a progress bar in the UI. :)

if you use my ethers library (or the beta v5 sub-package, @ethersproject/json-wallets)

Thanks for pointing me to that package. Looks very useful!

There is now a sync version available in this library, and the async version returns a Promise instead of archaic callbacks.
Please try it out and let me know if you have any problems. :)


JavaDocs JFlag no longer seems to get set with Gradle 3.4

We use the JavaDoc task to build our JavaDocs and we use our own doclets package to filter out what doesn't need to be added to the JavaDoc documentation.  From the JavaDoc task options closurer, we set the JFlag parameter to a system property which is then picked up within our doclets package.
After switching to Gradle 3.4, setting the system property with the JFlag parameter doesn't seem to get set as when I viewed the system property from within the doclets package, the system property was set to null.
We use the following JavaDoc task:
task apiDocs(type: Javadoc, dependsOn: configurations.midoclet) {
destinationDir = new File(apiDocsDir, "build")
failOnError = true
options.showFromPublic()
options.use()
options.doclet = "com.sample.tools.doclets.standard.Doclet"
options.docTitle = "${product_name} ${version} API"
options.JFlags = ["-Dpublic.api=com.sample.tools.VisibilityPublic"]
options.footer = "${product_name} ${version}"
options.header = "${product_name} ${version}"
options.windowTitle = "${product_name} ${version} API"
One of the doclets classes fetches the system parameter:
String property = System.getProperty("public.api")
In previous versions of Gradle it would have returned 'com.sample.tools.VisibilityPublic', but after switching to Gradle 3.4 it returns null.
We use the JavaDoc task to build our JavaDocs and we use our own doclets package to filter out what doesn't need to be added to the JavaDoc documentation.  From the JavaDoc task options type, we set the JFlag parameter to a system property which is then picked up within our doclets package.
After switching to Gradle 3.4, setting the system property with the JFlag parameter doesn't seem to get set as when I viewed the system property from within the doclets package, the system property was set to null.
We use the following JavaDoc task:
task apiDocs(type: Javadoc) {
destinationDir = new File(apiDocsDir, "build")
failOnError = true
options.showFromPublic()
options.use()
options.doclet = "com.sample.tools.doclets.standard.Doclet"
options.JFlags = ["-Dpublic.api=com.sample.tools.VisibilityPublic"]
One of the doclets classes fetches the system parameter:
String property = System.getProperty("public.api")
In previous versions of Gradle it would have returned 'com.sample.tools.VisibilityPublic', but after switching to Gradle 3.4 it returns null.

Thanks @andykane
I've confirmed that this is a problem. I don't see a workaround for now, but we'll get this fixed.

@big-guy Can you please add a milestone for the issue?

I believe this has been fixed and it should be closed in order to avoid misleading people.

This has been fixed in Gradle 3.5.


"Văcărești" is listed in the drop-down menu

Description:
"Văcăreștii" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Description:
"Văcăreștii" is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Văcărești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Văcărești , Dambovita".

The bug is located in the description of the test case. The name of the location is "Văcărești", not "Văcăreștii".

Am rezolvat. multumesc


Max retries exceeded

getting errors while calling txt2img api
requests.exceptions.ConnectionError: HTTPSConnectionPool(host="%3cmodule%20'app.url'%20from%20'", port=443): Max retries exceeded with url: /home/sunny/PycharmProjects/pythonStableDiffusion/app/url.py'%3E:443/sdapi/v1/txt2img (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff5b8fb7640>: Failed to establish a new connection: [Errno -2] Name or service not known'))

for that type of errors, you should check in this repo https://github.com/AUTOMATIC1111/stable-diffusion-webui

Apart from this how do I get the static Public URL?
Model loaded in 52.5s (load weights from disk: 46.9s, create model: 1.0s, apply weights to model: 2.6s, apply half(): 1.3s, move model to device: 0.6s).
Running on public URL: https://1467d1a6-5e43-4a2442.gradio.live

Running on public URL: https://1467d1a6-5e43-4a2442.gradio.live

this is the public url

Right this is the public URL, but it changes every time, I need the static URL

I don't think you can do that with colab, you can do it with RunPod https://www.runpod.io/console/gpu-secure-cloud?template=runpod-stable-unified

Which one should I use, could you please suggest me?

choose the template fast stable diffusion, inside the workspace, there are three notebooks, A1111, DBv1 and DBv2

please do me one more favor, could you please tell me which one should I use GPU instance?


[SPARK-44490][WEBUI] Remove TaskPagedTable in StagePage

What changes were proposed in this pull request?
Remove TaskPagedTable
Why are the changes needed?
In SPARK-21809, we introduced stagespage-template.html to show the running status of Stage.
TaskPagedTable is no longer effective, but there are still many PRs updating related codes.
Does this PR introduce any user-facing change?
No
How was this patch tested?
local test

@LuciferYang Please help to review, thanks.

also cc @yaooqinn FYI

Could you please attach one or more screenshots in the description?

Could you please attach one or more screenshots in the description?

PR

cc @sarutak @gengliangwang

@cxzl25 Could you attach another screenshot showing a task table which consists of multiple pages to verify it works with pagenation?

Could you attach another screenshot showing a task table which consists of multiple pages to verify it works with pagenation?

Hi @cxzl25, would you please rebase the master branch?

Merging to master.
Thank you @cxzl25 and all!


Impossible to remove permissions section from repo settings

Permissions section is not removed when repo settings are updated from
repo:
  type: file
  storage: default
  permissions:
    artipie:
      - download

to
repo:
  type: file
  storage: default

Permissions section is not required, so second yaml is valid and correct. Also, not required section settings is added on update with value null.

@rultor release, tag=0.4.8

@rultor release, tag=0.4.8

@olenagerasimova OK, I will release it now. Please check the progress here

@rultor release, tag=0.4.8

@olenagerasimova Done! FYI, the full log is here (took me 9min)


Debug utility

This PR addresses the TODO in #206 to add a logging utility.  It is only used in the Dropdown for now as the Dropdown is our proving grounds for removing jQuery and setting our v1.0.0 precedence.
Two debug logs were generating object differences, see componentWillReceiveProps and componentDidUpdate.  This logic was pulled into an objectDiff util and tested.

Couple of thoughts:

Even though the debugger will noop during production, the arguments are still always evaluated. This is needlessly expensive in production or even outside of development. Consider lazily running debug statements, i.e.:

debug(() => object.diff(...))

As a corollary, all of these debug statements are still invoked in production, even if they are just noop. I know it's a lot of work to wrap everything in environment checks, but for a public library I think it could be optimized a bit further. The pattern used here is similar to what we do in our business apps, but that's a bit of a different realm than a public library. Not sure if there's an easy way to abstract this logic so it's removed at compile time, but it should be considered.

Agreed on all counts and considered these things prior to the PR. In the future we'll have an optimization phase which will include a transform to remove debugs, static propTypes, and static_meta from production code.
I want to get more components moved to the 1.0 pattern before optimizing further. This PR moves us from console statements to a debug pattern we can iterate on.


client switches to secure encryption only when receiving the SHLO

It should do so when it receives a REJ that contains enough information.

The AEADs have an interesting property, which is not immediately obvious to me.
The server can open messages sealed by a client that created his AEAD without a diversification nonce. However, this doesn't work the other way round: the client cannot read messages sealed by the server if he doesn't know the diversification nonce.
I created a little test that should make things obvious: https://gist.github.com/marten-seemann/03282d5175eff2c0c0458749d4c946fa

The diversification nonce only enters the server's encryption key, not its decryption key. See here: https://github.com/lucas-clemente/quic-go/blob/d5ec70fc7db3e498bbd3a7a8db33d2187a1e364c/crypto/key_derivation.go#L66

Okay, that's not obvious, but it makes sense now looking at the key derivation code.
What that means for the client crypto setup is the following: We'll need to create two different secureAEADs, one for sealing packets and for opening packets. The one for sealing is created right after sending the non-inchoate CHLO, and the one for opening is created when receiving a diversification nonce. That way we'll be able to send non-forward-secure requests one RTT before becoming forward-secure.

The problem with this solution is that we'll need to expand the signaling to the session. At the moment, we try to decrypt undecryptable packets every time something is sent on the aeadChanged chan. However, we'd only send EncryptionLevelSecure on this channel when creating the secureAEAD for sealing (that's the one that doesn't require the diversification nonce), because that's the moment the application can send requests.

This has been outdated for a long time.


<EMAIL_ADDRESS>decompress error

The following text is copied from my console, Powershell running in Windows Terminal 2,
Thank you in advance!
~ $ scoop install typora
Installing 'typora' (0.9.89) [64bit]
Loading typora-setup-x64.exe from cache
Checking hash of typora-setup-x64.exe ... ok.
Extracting typora-setup-x64.exe ... Invoke-ExternalCommand : Cannot validate argument on parameter 'FilePath'. The argument is null or em
pty. Provide an argument that is not null or empty, and then try the command again.
At D:\apps\Scoop\apps\scoop\current\lib\decompress.ps1:192 char:38

... tus = Invoke-ExternalCommand (Get-HelperPath -Helper Innounp) $ArgLis ...

                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Invoke-ExternalCommand], ParameterBindingValidationE
xception
FullyQualifiedErrorId : ParameterArgumentValidationError,Invoke-ExternalCommand

Failed to extract files from D:\apps\Scoop\apps\typora\0.9.89\typora-setup-x64.exe.
Log file:
D:\apps\Scoop\apps\typora\0.9.89\innounp.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/lukesampson/scoop-extras/issues/new?title=typora%400.9.89%3A+decompress+error
~ $ scoop update typora
typora: 0.9.89 (latest version)
Latest versions for all apps are installed! For more information try 'scoop status'
~ $
~ $ scoop uninstall typora
Uninstalling 'typora' (0.9.89).
'typora' was uninstalled.

have you tried it in regular powershell - without wsl2?

scoop install innounp and then reinstall


fix prometheus response parsing issue

Description
fix parsing but [object Object] is not valid JSON in prometheus metrics
Issues Resolved
#1665
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

https://github.com/opensearch-project/dashboards-observability/assets/48943349/179c5b40-530b-49dd-9be5-a949476c68e5


🐛Bug: Slow to render a lot of components

Describe the bug
I tried instantiating a lot of Sliders, it incurs a significant overhead on page load before anything can be interacted with
In contrast plain input components load instantly
To Reproduce
Set useRadix = false to compare
<script lang="ts">
 import { Slider } from 'radix-svelte';
 let value = 0;

 let useRadix = true;
</script>

<form>
    {#if useRadix}
        {#each Array(100) as _, i}
            <Slider.Root
                class="relative flex h-5
                       w-full touch-none select-none items-center
                       data-[orientation=vertical]:h-[200px]
                       data-[orientation=vertical]:w-5
                       data-[orientation=vertical]:flex-col
                       "
                value={[50]}
                min={0}
                max={100}
                step={1}
                name={"asd!"}
                disabled={false}
                aria-label="Volume"
            >
                <Slider.Track
                    class="relative grow rounded-full bg-black/50
                           data-[orientation=horizontal]:h-[3px]
                           data-[orientation=vertical]:w-[3px]"
                >
                    <Slider.Range
                        class="absolute rounded-full bg-white
                               data-[orientation=horizontal]:h-full data-[orientation=vertical]:w-full"
                    />
                </Slider.Track>
                <Slider.Thumb
                    class="block h-5 w-5 rounded-[10px] bg-white shadow-[0_2px_10px] shadow-black/10
                           hover:bg-vermilion-100 focus:shadow-[0_0_0_5px] focus:shadow-black/30 focus:outline-none"
                />
            </Slider.Root>
        {/each}
    {:else}
        {#each Array(100) as _, i}
            <input min={0} max={100} step={1} value={70} type="range" style="width: 100%;" />
        {/each}
    {/if}
</form>

Expected behavior
Components should take a reasonable amount of time to load
Screenshots
Performance graph

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: 110.0.5481.177

@space-nuko Thanks for raising this issue! Quickly testing on a Macbook M1 yields fast results, but I'll try on another PC later on.
Would you mind giving me your PC specs? It is expected for components to be slower than native HTML elements, but 2-3s is quite slow.

AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz with 64GB of RAM, RTX 3090

AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz with 64GB of RAM, RTX 3090

Thank you for sharing, I'll look into this


[Fix - #341] - Updating the Maesh Logo from old to new.

Description
This PR fixes #341
Updating the Maesh Logo from old to new.
Signed commits

[x] Yes, I signed my commits.

Deployed Successfully, working Well (as per Netlify preview) but not able to resolve the DCO Check (https://github.com/layer5io/meshery.io/pull/349/checks?check_run_id=1263694232) even after running the same commands.
@leecalcote

git commit --amend --signoff
git push --force-with-lease origin patch-logo

@PluckyPrecious Successfully Passed DCO.
Instead of this
git commit --amend --signoff
git push --force-with-lease origin patch-logo

This works.
git commit -s -m "commit-msg."
git push --force-with-lease origin patch-logo

I just change the origin file. I just replaced the logo file with the new logo file having the same name. So, it'll automatically reflect on every reference.
See the Netlify preview:

@leecalcote  You want me to do this?

@leecalcote You want me to do this?

Yes. You can check out the other html files that has maesh and update them to traefik mesh as well.

Yes. You can check out the other html files that has maesh and update them to traefik mesh as well. It’s like a total maesh update.

Okay, I'll work on it.

Replacing reference of Maesh to Traefik Maesh on the main page along with the new logo.
@leecalcote @PluckyPrecious

@akashprasher, if you do pick up on these other 3 items, feel free to create an issue for each one and self-assign.

Thank you for helping get this over the line, @akashgp09

Sure. I'll create issue for this.

Thank you, @akashprasher (or 3 issues 😉 )


Define governance structure - ECDSA and Random Beacon

RandomBeaconGovernance smart contract and WalletRegistryGovernance smart contract control a whole set of parameters for Random Beacon and ECDSA operators and allow the governance contract owner alter them. We need to decide who is in charge of changing these parameters.
There are some hard questions to answer, for example:

Should the staker DAO control slashing amounts? Feels like a wrong choice.
Should callback gas limit be controlled by the DAO? Feels like a wrong choice.
What is the ideal governance delay?
Instead of a DAO, can we have some council controlling these parameters?

We need to adjust the code so that it's possible to unplug governance contracts.

It is possible to transfer the ownership of WalletRegistry and RandomBeacon application contracts to some other address. The existing RandomBeaconGovernance and WalletRegistryGovernance are good enough for the start so I am moving this issue into solidity/v1.1.0 milestone.


Fix block name typo and mark old one deprecated

1. Why is this change necessary?
It is just a typo.
2. What does this change do, exactly?
Fix a typo but provide both blocks to ensure compatibility.
3. Describe each step to reproduce the issue or behaviour.
Override this block but write the name by hand and type reference correctly.
4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

gg I did a typo myself in the commit message 🤦 Do we want to keep it in like that as funny coincedence? I'll amend it otherwise.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-9133
Please use this issue to track the state of your pull request.


Added flexbox, removed whitespace and aligned tooltip

Signed-off-by: Rohith Raju<EMAIL_ADDRESS>Description
Removed whitespace and aligned tooltip by using flexbox
This PR fixes #715
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Any changes @warunicorn19 @leecalcote  @chinmaym07 @theBeginner86

Yes @warunicorn19 on it!!

Hey guys, it's all done
@warunicorn19 @leecalcote @theBeginner86

Some merge conflicts to address.

@warunicorn19 Can you do it now ?

@Rohith-Raju you'll have to work on the styles again here, unfortunately. The changes that you made are not compatible with refactored styles. Also with regards to Merge conflicts you'd have to get rid of the >>>>HEAD and the other commit IDs, that's why the build was failing. You could try again in this PR itself or open up a fresh new PR.

Not a problem @warunicorn19, new pr it is then


MultiLanguageRecognizer - Recognizers dictionary does not use case-insensitive key comparer

Version
4.13.0-rc4
Describe the bug
Multi-language recognizer is unable to select the corresponding recognizer for a given locale if there is a case mismatch between the recognizer locale key and either the locale in the incoming activity or the default locale from the LanguagePolicy.
To Reproduce
Steps to reproduce the behavior:

Using the latest Composer nightly build, create a new Conversational Core bot.
Provision required resources in Azure, including LUIS.
Publish bot to Azure.
Start a conversation with the bot.

Expected behavior

Screenshots

Additional context
Related to https://github.com/microsoft/BotFramework-Composer/issues/6893.
When creating a new bot on the adaptive runtime, the bot is created using a default locale of 'en-US', which is fed in to the ConfigurationLanguagePolicy. This language policy is ultimately referenced in MultiLanguageRecognizer.
If no locale is explicitly set, we are able to correctly find the language policy corresponding to en-US. However, per ConversationalCore.lu.dialog scaffolded in recognizers dir for new bot, the locale is configured as 'en-us'. When attempting to select the recognizer based on the language policy locale value, it is not discovered because the recognizers dictionary is deserialized into a dictionary that uses a case-sensitive key comparer.

Contents of recognizer\CoinversationalCore.lu.dialog for reference:
{
  "$kind": "Microsoft.MultiLanguageRecognizer",
  "id": "LUIS_ConversationalCore",
  "recognizers": {
    "en-us": "ConversationalCore.en-us.lu",
    "": "ConversationalCore.en-us.lu"
  }
}


please include documentation to not set the container hostname

when the container is run with a hostname such as
docker run -d \
    -h my-host-dockergen-lets-encrypt \
    -v /path/to/certs:/etc/nginx/certs:rw \
    --volumes-from nginx-proxy \
    -v /var/run/docker.sock:/var/run/docker.sock:ro \
    jrcs/letsencrypt-nginx-proxy-companion

then this resulting curl call from within the docker_api function fails...
curl -s --unix-socket /var/run/docker.sock -XGET http://localhost/containers/my-host-dockergen-lets-encrypt/json
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/blob/master/app/functions.sh#L51
I'd be happy to provide a small PR if you're favorable to this inclusion.

Sorry, i don't understand why the function fails if you are giving a hostname to your container ?
The docker API use container ID not hostname.

this is the call to docker_api from within check_writable_directory which fails due to it's use of $HOSTNAME:
docker_api "/containers/$HOSTNAME/json" | jq ".Mounts[].Destination" | grep -q "^\"$dir\"$"
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion/blob/master/app/entrypoint.sh#L45

Commit 8b97f203
@bnfinet can you check with the dev version of the container ?

@JrCs I had this same issue due to the fact that I'm deploying via Docker Cloud and they set a hostname for you by default.  I tested this with the :dev version and it has fixed the issue.  Thank you!  I can move forward with :dev for now but a tagged container with this change would be welcome :)

This was fixed on master by commit 86ee879


Add fragment selected fields

Description
This PR adds fragment and variable info to the selected_field attribute on info.
Types of Changes

[x] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Fixes #1197

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to Jonathan Kim for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


it seems SSL stuff is not working anymore

it seems after SSL stuff is not compiling at all

I saw you're saying that #58 fixes this issue. What was an issue?

I see Debug is not derived.

I see. Debug could not be derived automatically. Good catch, thank you.

I've checked. Now it works.