refactor protobuf contentview

Currently the protobuf contentview relies on the protoc compiler to be available as shell command (in $PATH).
https://github.com/mitmproxy/mitmproxy/blob/75a0a4c09276ef2aa479c9ae9feab97f7803ed6d/mitmproxy/contentviews/protobuf.py
However, it would be much cleaner to directly use the Python API provided by https://github.com/google/protobuf
https://developers.google.com/protocol-buffers/docs/pythontutorial
We already have that package as dependency, so why not use it?

I will like to fix this issue. I will start working on it now.

It looks like the Python API from google-protobuf has a some severe limitations and is not capable of decoding serialized messages without the .proto file. From the official docs:

The current Python implementation does not track unknown fields.

So the only output we really can get our hands on is the one from protoc CLI tool, and even this only gives us key-value pairs with raw field IDs.
I believe that this could also be done with a simple construct or kaitai decoder to parse the on-the-wire representation into their (nested) key-value tuples.
https://developers.google.com/protocol-buffers/docs/encoding

kaitai just got protobuf support! https://github.com/kaitai-io/kaitai_struct_formats/commit/d4f066eacb4132807bec3fc8ddf9f6e7e690ae34

Yes, implementing this with kaitaistruct is the way to go.
@saganshul, did you start working on this? Otherwise this is free for pick up again.

@mhils I started looking for support for raw decoding in google prototype python module.
I got same thing as @Kriechi said.
I will take a look at kaitai_struct_format and try to resolve this issue.

@mhils @Kriechi
Error on compiling google_protobuf.ksy using kaitai-struct-compiler
Exception in thread "main" io.kaitai.struct.translators.TypeMismatchError: called invalid attribute 'size' on expression of type ArrayType(UserTypeInstream(List(group)))
at io.kaitai.struct.translators.BaseTranslator.detectType(BaseTranslator.scala:337)
at io.kaitai.struct.TypeProcessor$$anonfun$deriveValueType$1.apply(TypeProcessor.scala:63)
at io.kaitai.struct.TypeProcessor$$anonfun$deriveValueType$1.apply(TypeProcessor.scala:56)
at scala.collection.immutable.Map$Map2.foreach(Map.scala:137)
at io.kaitai.struct.TypeProcessor$.deriveValueType(TypeProcessor.scala:56)
at io.kaitai.struct.TypeProcessor$$anonfun$deriveValueType$2.apply(TypeProcessor.scala:83)
at io.kaitai.struct.TypeProcessor$$anonfun$deriveValueType$2.apply(TypeProcessor.scala:81)
at scala.collection.immutable.Map$Map3.foreach(Map.scala:161)
at io.kaitai.struct.TypeProcessor$.deriveValueType(TypeProcessor.scala:81)
at io.kaitai.struct.TypeProcessor$.deriveValueTypes(TypeProcessor.scala:44)
at io.kaitai.struct.TypeProcessor$.processTypes(TypeProcessor.scala:16)
at io.kaitai.struct.formats.JavaKSYParser$.localFileToSpec(JavaKSYParser.scala:17)
at io.kaitai.struct.Main$.compileOne(Main.scala:83)
at io.kaitai.struct.Main$$anonfun$main$1.apply(Main.scala:120)
at io.kaitai.struct.Main$$anonfun$main$1.apply(Main.scala:115)
at scala.collection.immutable.List.foreach(List.scala:381)
at io.kaitai.struct.Main$.main(Main.scala:115)
at io.kaitai.struct.Main.main(Main.scala)
Do you guys know how to fix this?

I am working on this. As of now, we're waiting for KS 0.7 to be released as the .ksy file uses size which is unsupported for KS < 0.7. Upgrading to 0.7 will also involve recompiling the files used for image parsing in mitmproxy/contrib/kaitaistruct.

@s4chin any update on this?

I asked the KS team about the release date. KS 0.7 was supposed to released this Monday, but was delayed. Now it's 50% done, shouldn't be too long.

Thanks! :)


Rename empty organization error!

Gitea version (or commit ref): gitea/gitea:1.14.5 docker image
Git version: 2.30.2 (in docker container)
Operating system:

Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

Log gist:

Description

First, rename empty organization:

Then, error page appears:

Screenshots

Apologies for this bug it's already fixed by #16463 which will be in v1.14.6.

Apologies for this bug it's already fixed by #16463 which will be in v1.14.6.
@zeripath When will v1.14.6 be released?


Weird webhook.

I've just got that when setupping the webhook

Here is my config :
// Required. Name the message will appear to be sent from. Change this to whatever you wish it to be.
$wgDiscordFromName = $wgSitename;
// Avatar to use for messages. If blank, uses the webhook's default avatar.
$wgDiscordAvatarUrl = $wgFavicon;
// URL into your MediaWiki installation with the trailing /.
$wgDiscordNotificationWikiUrl = "https://wiki.plasmatale.cf/";
// Wiki script name. Leave this to default one if you do not have URL rewriting enabled.
$wgDiscordNotificationWikiUrlEnding = "";
// What method will be used to send the data to Discord server. By default this is "curl" which only works if you have the curl extension enabled. There have been cases where VisualEditor extension does not work with the curl method, so in that case the recommended solution is to use the file_get_contents method. This can be: "curl" or "file_get_contents". Default: "curl".
$wgDiscordSendMethod = "curl";

Could you check the version of the extension your wiki uses? If the version is older than fad96aaa, you should use $wgWikiUrl and $wgWikiUrlEnding instead of $wgDiscordNotificationWikiUrl and $wgDiscordNotificationWikiUrlEnding.

Could you check the version of the extension your wiki uses? If the version is older than fad96aa, you should use $wgWikiUrl and $wgWikiUrlEnding instead of $wgDiscordNotificationWikiUrl and $wgDiscordNotificationWikiUrlEnding.

It worked ! Thanks!


Models deployed with ModelMesh-Serving get restarted on upgrade

Describe the bug
KServe community follow an approach to release all repos together irrespective if there are code changes in independent repos or not.
For example, In release v0.11.2, a new tag is created for all repos(modelmesh, modelmesh-runtime-adaptor, rest-proxy etc).
Earlier we had created an image for v0.11.1 but with the new release (v0.11.2), we had created a new set of images by pointing to the v0.11.2 tag.
Now when we roll out a new modelmesh-serving(v0.11.2) controller, all deployed runtimes are restarted because the runtime sidecar container image(modelmesh, modelmesh-runtime-adaptor, rest-proxy) tag has been changed.
Problem is ModelMesh tech stack is quite stable and repos like modelmesh, modelmesh-runtime-adaptor, rest-proxy hardly see any code change between the releases. But to release complete KServe org all together we provide their new versions as well.
Expected behavior
Model runtime pod should not restarted on ModelMesh-Serving controller upgrade, if there is no change at runtime/application level.
Additional context
I am proposing every repo should be released independently only if there is a code change.
For example, On next release cycle, new tag for modelmesh-runtime-adaptor repo should only be created if there are some changes.

@vaibhavjainwiz If we don't set a new tag for modelmesh images that didn't change at all, the restarting issue that all the runtime pods roll out when modelmesh-serving upgraded will be solved?
@ckadner could you please review this ticket?

@vaibhavjainwiz If we don't set a new tag for modelmesh images that didn't change at all, the restarting issue that all the runtime pods roll out when modelmesh-serving upgraded will be solved?

yes.. if we don't build new image for ModelMesh repo where code didn't change since last build then this issue would be resolved.

I am proposing every repo should be released independently only if there is a code change.
For example, On next release cycle, new tag for modelmesh-runtime-adaptor repo should only be created if there are some changes.

There usually are code changes in at least one of the 3 modelmesh repos for each release. At the very least we have a few security fixes. If one of the images changes, a new deployment would get rolled out.
We could make some changes to the MM controller to stagger the update/rollout over time to reduce the resource spike, e.g. one runtime kind at a time.


NO-ISSUE: Update SSHCommand function in e2e

Updated SSHCommand function with "PubkeyAuthentication=no" to avoid that any local SSH key is used for the authentication.
This will avoid a possible "Too many authentication failures" error when the test runs in local env

rebase plz!


Some fancy dead code analysis

This strips any let binding whose variable is not used in any live expression and whose value is pure. What qualifies as pure I hear you ask?

Atoms (references, lambdas, literals)
Partially applied functions
Constructors
Match expressions with one case (and no bindings are consumed)
Binary operators

Match expressions with one case (and no bindings are consumed)

I dun get it.

Ｎｏｔ　ｈａｐｐｙ　ａｂｏｕｔ　ｔｈａｔ　ｍｏｄ− ahem, sorry. Not happy about that module name.


fix: Connect bank - -1 is pre-filled for the tax ID number when connecting a new bank account.

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/45073
PROPOSAL: https://github.com/Expensify/App/issues/45073#issuecomment-2217832947
Tests

Create a workspace and enable workflows
Go through connecting a bank account flow up until the fourth step where it requires you for the tax ID number
Verify tax ID input is empty

[x] Verify that no errors appear in the JS console

Offline tests

Create a workspace and enable workflows
Go through connecting a bank account flow up until the fourth step where it requires you for the tax ID number
Verify tax ID input is empty

QA Steps

Create a workspace and enable workflows
Go through connecting a bank account flow up until the fourth step where it requires you for the tax ID number
Verify tax ID input is empty

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/09b846ef-1b50-4609-8f23-5cbc2ec224ad

Android: mWeb Chrome
https://github.com/user-attachments/assets/f313ca59-9431-4184-a9bc-94c4e383c30e

iOS: Native
https://github.com/user-attachments/assets/5175c251-c369-45bd-8ca1-b8d048f45699

iOS: mWeb Safari
https://github.com/user-attachments/assets/94dd0398-983a-4a0b-a634-2bdaf17f7cd8

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/5019c75d-cb9f-4cbf-8a58-dee3302988d4

MacOS: Desktop
https://github.com/user-attachments/assets/5e39dd63-39b5-472d-8eb7-ccb8231c3d69

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/blimpich in version: 9.0.7-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/thienlnam in version: 9.0.7-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.8-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Feature: Deployment configuration component

Description
Adds a new DeploymentConfiguration component which displays both infrastructure overrides and pull steps. This component will replace the "infra overrides" tab on the deployment page with a new "Configuration" tab.

For https://github.com/PrefectHQ/prefect/issues/10467


DMDs only loading in 1-bit instead of 4-bit?

This is intermittent. Works fine on my system but not on another. Is it a Mac only issue? Need to investigate...

Will be fixed in 0.22. (It's a Pygame Mac thing.)


RT 1.1 : base_bgp_session_parameters_test.go

Hi,
Config Get will fail before configuring protocol config if there is no config present on dut.
Hence removed it.
Thanks,
Prabha

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1602

Relevant Lines:
2177

💛  - Coveralls


CU-861nb3b4f_ingress-with-step_Alok-Hom

CU-861nb3b4f_ingress-with-step_Alok-Hom

Task linked: CU-861nb3b4f ingress with step


[SPARK-20750][SQL] Built-in SQL Function Support - REPLACE

What changes were proposed in this pull request?
This PR adds built-in SQL function (REPLACE(<string_expression>, <search_string> [, <replacement_string>])
REPLACE() return that string that is replaced all occurrences with given string.
How was this patch tested?
added new test suites

Test build #77138 has started for PR 18047 at commit 043d837.

Test build #77138 has finished for PR 18047 at commit 043d837.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class StringReplace(srcExpr: Expression, searchExpr: Expression, replaceExpr: Expression)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77138/
Test FAILed.

Test build #77139 has started for PR 18047 at commit 0218578.

Test build #77141 has started for PR 18047 at commit 96cd85d.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77141/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77139/
Test FAILed.

Merged build finished. Test FAILed.

Test build #77149 has started for PR 18047 at commit 24d777d.

Jenkins, retest this please

Jenkins, retest this please

Test build #77167 has started for PR 18047 at commit 24d777d.

Test build #77167 has finished for PR 18047 at commit 24d777d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77167/
Test FAILed.

Test build #77187 has started for PR 18047 at commit 587d7c5.

Test build #77187 has finished for PR 18047 at commit 587d7c5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77187/
Test PASSed.

Test build #77202 has started for PR 18047 at commit 125528e.

Test build #77202 has finished for PR 18047 at commit 125528e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77202/
Test PASSed.

ping @gatorsmile

Test build #77483 has started for PR 18047 at commit 57990a6.

Test build #77483 has finished for PR 18047 at commit 57990a6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77483/
Test PASSed.

LGTM except two minor comments.

Test build #77492 has started for PR 18047 at commit 2c9c042.

Test build #77492 has finished for PR 18047 at commit 2c9c042.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77492/
Test PASSed.

Merged build finished. Test PASSed.

Test build #77494 has started for PR 18047 at commit 6d0b012.

Merged build finished. Test FAILed.

Jenkins, retest this please

Test build #77496 has started for PR 18047 at commit 6d0b012.

Test build #77496 has finished for PR 18047 at commit 6d0b012.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77496/
Test PASSed.

Thanks! Merging to master.


Fix resolving deps for psr/http-message-implementation

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
https://github.com/php-http/discovery/pull/208#issuecomment-1424221715

Documentation
-

License
MIT

Oops, bad declaration.

Fixes #212 #211


OpenBSD 7.4 - 24 errors

I've tried installing via:
pkg_add py3-py
and also using the git clone as per your readme and the tests give 24 errors.
They are all [Errno 13] Permission denied
I'm not sure if I'm doing something wrong, pf is enabled and running.

Hi,
I'm sorry, this package hasn't been actively maintained for some time, so the errors you're getting must definitely be caused by code being obsolete.
I thought there wasn't much interest in this package anymore, but if you think it could be useful to you, I'll be glad to fix it as soon as possible. I'll get back to you in a few days!
Best regards!

That would be great - thanks.

Hi @jezcaudle,
I've just committed a new version of py-pf, updated to OpenBSD 7.4.
You can install it with python3 setup.py install or from pypi.
Please let me know if you have any issues with it.
Cheers!

Tested and it's working. Thank you very much.


Rollback commit b28e1b2 to fix broken tests

Re: issue #13
I'm not sure the reason behind commit b28e1b2, but the tests pass for me on Windows 7 x64 after applying this patch.

I accidentally included some additional work in this pull request. I closed this one and opened another with just the fix for the tests at #41.


Remove tileshape and enable_direct parameters where they still exist

Cleanup work from #706.

[x] tileshape should be removed/ignored without replacement.
[ ] remove enable_direct

As for enable_direct, we can still support the parameter for a while after #716 is done, but it should be moved to a "select i/o engine" kind of parameter (#753), such that it is available for (almost) all formats.

Hm, seems to be implemented in https://github.com/LiberTEM/LiberTEM/blob/994141ed0952b7d73a530dccdb492b178db9880a/src/libertem/io/dataset/raw.py#L102-L110
Not sure if we close here and leave as-is, or make this a proper deprecation in 0.12? Bumping to next release for evaluation.

I think we can close this - we don't really lose too much by keeping the backwards compatibility.


docs(website): improve taiko nodes documentation

Hey @d1onys1us, here's a revamped version of the Taiko nodes docs.
A few comments:

I replaced the Engine API link with another one because the old one was broken. Need to check if it's the correct one.
I added a few links to terms from the rollup glossary. I'm not sure if it's the right move but I thought since we have some definitions there that we don't have on the website, why not use it?
I used the callout components as you said but at least in the preview, the code doesn't seem to work for some reason. Would appreciate it if you could look into it.
Do we have anything unique to say in the Engine API section? We kind of repeat ourselves there, I wonder if we even need it?

Let me know what you think!

Also, @d1onys1us, I can't seem to link this PR to the issue you created.

hey umede, thanks for the PR! looks great to me, nice work 💯
i made a small fix, if you're curious: 453966e


project structure reorganized added new ui react based

Front end becomes a first citizen class, just created two root subfolders:

backend
frontend

Backend project needs to be reviewed.
Front end project, copied the base from: https://github.com/Lemoncode/az-search-jfk-demo
Please review global readme and front readme, and provide feedback.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: brauliodiez sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Updating to latest packages

This is just an update to the latest packages of the repository. I had to change the information shown on the test because the new version of tap changed the --coverage report in the CLI.

@Bandito11 could you please rebase your PR on latest cpdebase in order to merge it? Thank you!


find -> sort : response time very slow

collection count : 1,200,000
mongo shell command

db.find({TRN_NO: “(trn_no)”}).sort({_id: -1}).limit(1)
response time : 200ms

MongoKitten
let FindResults = collection.find("TRN_NO" == “(trn_no)").sort(["_id":.descending]).limit(1).getAllResults()
response time : 18,000ms
What did I do wrong?
How can I get code to get a quick response?

The only thing I can imagine is that for this query, MongoKitten didn't yet create an authenticated connection to the database. Probably because you used lazyConnect to create an instance.
Successive calls should be far better.

main.swift
let worker_user = "worker"
let worker_passwd = "worker_passwd**"
let worker_db = try Database.synchronousConnect("mongoldb://(worker_user):(worker_passwd)@<IP_ADDRESS>:27017/worker_db
worker_handler.swift
let FindResults = collection.find("TRN_NO" == “(trn_no)").sort(["_id":.descending]).limit(1).getAllResults()
Very slow
I guess it seems to sort all the data in the collection after importing it.
Am I using it wrong?

How large is the dataset? I think your problem might be that getAllResults loads all results into a large array (in memory). If your dataset is bigger than 500 documents, definitely look into another implementation that uses forEach or sequentialForEach.

Thank you for the response.
I solved the problem in another way.
The query was so slow that I solved it by taking the entire result, storing it in an array and processing it.
The entire array of results is updated periodically.


Add basic docs

And add the generated docs

Another thing, any chance of a CI workflow that checks that the docs are up-to-date (or possibly auto-updates them)? I could try to add that in a future PR if you'd prefer.

Ok, I pulled my finger out and made some proper(ish) docs.

Built docs here: https://fortitude.readthedocs.io/en/dev-command/

Yup:
$ uv pip install mkdocs-material
$ mkdocs serve

This watches for file changes and reloads the site as needed.

Yup:
$ uv pip install mkdocs-material
$ mkdocs serve

This watches for file changes and reloads the site as needed.

Amazing, works perfectly (and unlike Sphinx, I don't have to type out file:///the/entire/path/to/my/index.html in my browser to see the changes).
Please could you add this to README.dev.md?
## Building Docs

The documentation can be built locally using:

```bash
pip install mkdocs-material
mkdocs serve
```


GPS required on devices running S+

Android 12 does not require GPS to be turned on when scanning for devices using the BLUETOOTH_CONNECT/BLUETOOTH_SCAN permissions.
It seems that it will not scan unless I turn it on, even tho there's no errors logged.

@matejdro please take a look at this

Whole situation regarding those permissions seems weird.
Android 12 does not require location permission, but it still seems to require location services on to scan for devices. Also note that to scan for some devices (such as beacons), you still need location permission despite new BLUETOOTH_SCAN permission.

I was able to work out the difference as to why your library didn't work while my own code did.
It turns out that omitting the 'neverForLocation' flag on the BLUETOOTH_SCAN permission, will treat it as a location request.
Adding the flag will allow the scan to work correctly without location permissions nor GPS being enabled.
<uses-permission android:name="android.permission.BLUETOOTH_SCAN"
        android:usesPermissionFlags="neverForLocation"/>


close event never fire 🚨

SerialPort Version: V5.0.0
NodeJS Version: V6.3.0
Operating System: WIN 10 64B
I have created this code, I would like to know why close/disconnect event never fire when I disconnect the COM
const express = require('express');
const router = express.Router();
//
const cors = require('cors');
router.use(cors());
//
const SerialPort = require('serialport');
const Readline = SerialPort.parsers.Readline;
const port = new SerialPort('COM7',function (err) {
    if (err) {
        return console.log('Error: ', err.message);
    }
});
const parser = port.pipe(new Readline());
/*
var lastresult = '';
var count = 0;
*/

port.on('open', function() {
    console.log('~Port is open.');
    parser.on('data', console.log);
});
port.on('disconnect', function () {
    console.log('disconnected');
});
port.on('close', function () {
    console.log('closed');
});

router.get('/', function (req, res) {
    res.send('index');
});

module.exports = router;

I'm trying to think if I use it wrong because I havn't saw example for using this event.
Thanks for the help :)

Can some1 please look into my problem i'm kinda stuck

I have the same problem with serialport v5.0.0 and node v8.5.0 on Linux Mint 18.2
If you call the close() on the port instance then the close event is fired. But if you disconnect the cable while the program is running, close event never fires. This was not the case in<EMAIL_ADDRESS>it worked correctly and also emitted both close and disconnect

reconbot, I've update the repository to 6.0.0 and it's work great thanks!


reset OTP token if the risk level changes from high to low.

Description
We should reset the OTP token every time the risk level changes from high to low
Link to Jira
https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-4990
Screenshots
No UI involved

I close this PR, because we need a completely other approach and a new review.


Request for Upload Key for Just King

Game name
Just King
Request type
Adding a new game to the feed
Target frameworks, package dependencies

net45

UnityEngine.Modules, 2021.3.2

Allowed assembly names

Assembly-CSharp
283ade.library
clipper_library
com.rlabrecque.steamworks.net
FM.Event
FM.FloatingText
FM.Pool

Contact details
<EMAIL_ADDRESS>Additional information
I was not sure whether I should add the cinemachine.dll as an allowed assembly name... if you think it is probably worth it, please add it to the list.
Package ownership agreement

[X] I acknowledge and agree to the above rules

Granted upload key as requested


[FEATURE] Improvement of the access to the log files

For most users of the package, especially beginners, the only reason to connect to the NAS via SSH is to view the log files. A solution for this should be worked out if possible.
Using Synology Log Center? Is it possible to pass the log files to the Synology Log Center in a standardized way (without syslog)?
Storage of the logfiles within a standardized share? (/volume1...) to make them available via File Station? The share could also be created during the installation.
Other ideas?

Integrated with release <IP_ADDRESS>-20210706 - DSM7 compatible.
Check documentation at documentation


[VueDX/TS(17001)] JSX elements cannot have multiple attributes with the same name

Describe the bug
When using multiple radio type inputs, VueDX/TS prompts that it cannot have multiple attributes with the same name.
To Reproduce
https://v3.vuejs.org/guide/forms.html#radio
<template>

  <input type="radio" id="one" value="One" v-model="picked" />
  One

  <input type="radio" id="two" value="Two" v-model="picked" />
  Two

  Picked: {{ picked }}

</template>

Expected behavior
No error be reported when using <input type='radio' ...
Screenshots/Recording
If applicable, add screenshots to help explain your problem.

Info (please complete the following information):

Linux x64 5.9.16-1-MANJARO
VS Code 1.52.1
TypeScript 4.1.3
Vue 3.0.5

Same Error! +1

Same Error! +1

+1
  <select
                v-model="selectedFont"
                class="form-control"
                :required="true"
                @change="update"
                @click="loadAllGoogleFonts">

clears if I remove either @change or v-model

Same error for me :
        <select
          id="selected"
          v-model="selected"
          v-on:change="deleteListArticle($event)"
        >
          <option value="select">Select</option>
          <option value="deleteAll">Delete All</option>
        </select>

The error :
(prop) onChange?: ((payload: Event) => void) | undefined JSX elements cannot have multiple attributes with the same name.VueDX/TS(17001) View Problem (⌥F8) No quick fixes available

I'm seeing the same error with a radio switch. If it helps with debugging, I posted a question to SO before I found this bug report: https://stackoverflow.com/questions/66723391/how-do-i-use-v-model-with-an-object-using-vue-and-typescript
It has my component code in it, and a list of errors.


UI breaks when switching apps in iOS production app

When switching apps in iOS using the home button the UI breaks in my app, attaching video and screenshot for reference
please check the video for before and after the ui breaks
Video zip -> bottombar_checkalerts_ui_breaks.MOV.zip
bottomNavigationBar is broken and also backgroundColor is missing for "CHECK ALERTS" and "+"  button

Different screens are also affected by this issue

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-IN)
    • Flutter version 1.22.5 at /Users/dhruv/Desktop/flutter
    • Framework revision<PHONE_NUMBER> (6 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/dhruv/Library/Android/sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.10.0

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 49.0.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] Connected device (1 available)
    • ONEPLUS A6010 (mobile) • <IP_ADDRESS>:5555 • android-arm64 • Android 10 (API 29)
    ! Error: Rajesh’s iPhone8 is not connected. Xcode will continue when Rajesh’s iPhone8 is connected. (code -13)

• No issues found!

My build method looks like this
SafeArea(
      child: Scaffold(
          backgroundColor: BrandColors.gallery,
          body: ValueListenableBuilder<DashboardModel>(
            valueListenable: dashboardBloc.dashModelNotifier,
            builder: (context, snap, child) {
              return IndexedStack(
                index: snap.indexStack,
                children: <Widget>[
                  StreamBuilder<WebviewDataModel>(
                      stream: dashboardBloc.webviewData,
                      builder: (context, snapshot) {
                        if (!snapshot.hasData) {
                          return Container();
                        }
                        return WebviewJsCookie(
                          stackIndex: snap.indexStack,
                          url: snapshot.data.url,
                          analyzeData: snapshot.data.trades,
                          shouldInterceptURLs: true,
                          changeTab: () => goToHome(),
                        );
                      }),
                  _screens[snap.currentIndex],
                ],
              );
            },
          ),
          bottomNavigationBar: showBottomNav
              ? ValueListenableBuilder<DashboardModel>(
                  valueListenable: dashboardBloc.dashModelNotifier,
                  builder: (context, snapVal, child) {
                    return Container(
                      decoration: BoxDecoration(
                        boxShadow: [
                          BoxShadow(
                            color: Colors.grey.withOpacity(0.3),
                            blurRadius: 5,
                            offset: Offset(-1, 0),
                            spreadRadius: 1,
                          )
                        ],
                      ),
                      child: Card(
                        margin: EdgeInsets.all(0),
                        elevation: 10,
                        shape: RoundedRectangleBorder(
                            borderRadius: BorderRadius.only(
                          topLeft: Radius.circular(10),
                          topRight: Radius.circular(10),
                        )),
                        clipBehavior: Clip.antiAlias,
                        child: BottomNavigationBar(
                          elevation: 20,
                          type: BottomNavigationBarType.fixed,
                          selectedItemColor: BrandColors.accentColor,
                          unselectedItemColor: Colors.grey,
                          onTap: (tapvalue) {
                            onNavTapped(tapvalue);
                          },
                          currentIndex: snapVal.currentIndex,
                          items: [
                            BottomNavigationBarItem(
                                icon: Icon(Icons.home), title: Text("Home", style: TextStyle(fontSize: 12))),
                            BottomNavigationBarItem(
                              icon: SvgPicture.asset(
                                'assets/images/analyze.svg',
                                color: snapVal.currentIndex == 1 ? BrandColors.accentColor : Colors.grey,
                              ),
                              title: Text("Analyze", style: TextStyle(fontSize: 12)),
                            ),
                            BottomNavigationBarItem(
                                icon: Icon(Icons.work), title: Text("Positions", style: TextStyle(fontSize: 12))),
                            BottomNavigationBarItem(
                                icon: Icon(Icons.bookmark), title: Text("Watchlist", style: TextStyle(fontSize: 12)))
                          ],
                        ),
                      ),
                    );
                  },
                )
              : Offstage()),
    );

NOTE: This issue does not occur in Flutter STABLE v 1.20.2

Hi @rajeshzmoke
Your code is incomplete, please isolate the code that causes it, provide a minimal sample instead of production code.
Can you please provide flutter run --verbose logs, and a minimal complete reproducible code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


BUG: I can't download the models

Hi everyone!
Describe the bug
I can not use a model, that I haven't used before, because the model can not be downloaded.
For example: moosez -d /path/ -m clin_ct_lungs
To Reproduce

Try to use a model that you haven't used before

Screenshots

Desktop (please complete the following information):

OS: Ubuntu 18.04

Hi @Daniloper,
Could you please let me know the version of moose you are using. We have migrated from ibm to aws. So the links from old versions will not work. Check if the version is the latest. And then reinstall it in a fresh environment. Ideally it should work. Kindly let me know.
Cheers,
Lalith

Hi Lalith,
I am using v2.0.0. I installed it in December and the download was working back then.

Hi there, I would be needing the exact version of moose. You are talking about the "major release". We are at 2.3.9.
You can check your actual version by typing:
pip show moosez

Yes I am using v2.3.4
I am going to try to upgrade it.
Thank you!

Great please keep me posted if it works out.

Hi @Daniloper, Is this solved or are you still having troubles?
Kindly let me know.
Cheers,
Lalith

Could you elaborate more on the MPs check please. I am happy to fix it in the main branch.

I get the following error:

Hey @Daniloper, what is your NVIDIA driver version? According to the posted error, it seems to be too old.

I have no GPU in that maschine. It is expected to run on CPU. But before the running could start, the MPS error occures.

Hi, @Daniloper! I was able to reproduce your error and found a fix. Should be online now, test it and let us know :)

In 2.4.0 - it's fixed!

Hi @Daniloper kindly let us know if the error goes away from moosez 2.4.0. So that we can close the issue :)! Thanks again for pointing us towards the bug. Much appreciated!

Hi @LalithShiyam,
I have tried the v2.4.0. It is working. Everything is fine now. Thank you!


fix: minor UI bugs in provisioning and node modal

Description

Making design changes per design spec for publishing modal
Adding text to node modal indicating need to restart after installation
Updating template sort order list to reflect new package names coming in Friday

More info here

Task Item
fixes #6890
fixes #6970

Coverage decreased (-0.01%) to 50.945% when pulling 9f52b2c9f037962744cc926d150f292265aacd5a on pavolum/bugBashFixes2 into bdc1a28e7dec32c4b643b122f0ad0c266ef93635 on main.


b58decode - Determine whether the return value is out of bounds.

panic: runtime error: slice bounds out of range
goroutine 205 [running]:
github.com/anaskhan96/base58check.Decode(0x0, 0x0, 0x7a5b80, 0xc4204d94e0, 0x16, 0x16)
build/_workspace/src/github.com/anaskhan96/base58check/base58check.go:72 +0x51e

Merged.


Add radiocanadamini.ca

This PR is:

[x] Adding a new domain
[ ] Updating existing domain
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (darktheme.club site)
[ ] Other not listed

[x] The domain is in the correct alphabetical order
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ page, particularly the red section about inappropriate content, and I attest that this site is appropriate based on those criteria.

[x] Check to confirm

- domain: radiocanadamini.ca
  url: https://radiocanadamini.ca/
  method: mediaquery
  last_checked: 2022-10-03

Thanks for your PR!


only getting minute data until 12pm EST everyday in historical mode

This is the first time I am running my script since Jan (it was working fine then), and I had to upgrade to use alpaca backtrader 0.15.0 today.  After upgrading however, I'm now getting mkt data only until noon every day in historical mode (it would move onto the next day).  Does anyone have any idea?  What am I missing?
eg:
2022-06-16 11:54:00:                 h:123.110                 l:122.790                 c:122.790
2022-06-16 11:55:00:                 h:123.050                 l:122.810                 c:122.810
2022-06-16 11:56:00:                 h:123.310                 l:122.940                 c:123.040
2022-06-16 11:57:00:                 h:123.460                 l:123.010                 c:123.460
2022-06-16 11:58:00:                 h:123.950                 l:123.410                 c:123.660
2022-06-16 11:59:00:                 h:124.160                 l:123.660                 c:124.080
2022-06-16 12:00:00:                 h:124.200                 l:123.490                 c:123.540
2022-06-17 05:44:00:                 h:126.610                 l:126.610                 c:126.610
2022-06-17 07:04:00:                 h:126.930                 l:126.930                 c:126.930
2022-06-17 07:05:00:                 h:127.300                 l:127.280                 c:127.300
2022-06-17 07:07:00:                 h:128.000                 l:127.980                 c:128.000
2022-06-17 07:09:00:                 h:128.200                 l:128.200                 c:128.200
2022-06-17 07:40:00:                 h:128.500                 l:128.500                 c:128.500

looks it was a timezone issue


Fixing

I have changed all the Lorems
I have added relative contents
I have added the faculty signup page
After registering its showing error I have also fixed it
Fixed the css part for Faculty sign up page
Fixed the allotment page

Please resolve the conflicts @noobremon

I have resolved the conflicts sir @Harshdev098

There are many thing to be fixed in this pr, I am closing it for now

I can add normal images to it, means how can I get real research papers.Can I do it?? @Harshdev098

Can you please open it I can fix the FAQ and Research Paper portion as they are overlapping on each other and also there is sign up page fac_signup for registering as a Faculty.
When I extracted the file the research paper portion was not like this.
I can fix these issues can you please open it @Harshdev098

Hey can you please reply to me @Harshdev098


Code improvement: replace bubble sort with heap sort

Currently the file `motr/io.c` uses the bubble sort algorithm. As we already know this algorithm has a bad time complexity. One solution to this issue as mentioned in this comment: https://github.com/Seagate/cortx-motr/blob/409f711fcfa22b393e34a14f49eab5fa142131bb/motr/io.c#L136  is to replace bubble sort with heap sort.

Here is a link to the code in question: https://github.com/Seagate/cortx-motr/blob/409f711fcfa22b393e34a14f49eab5fa142131bb/motr/io.c#L124
Here is the link to the issue in the cortx-motr github repo: Seagate/cortx-motr#1424

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/EOS-28372. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

Closing as an obsolete


Add CloudFlare Analytics to website

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?
Collect page views and other analytics data on the DoEKS website to track overall visitors and also understand which patterns are the most trafficked by our users.
Describe the solution you would like
https://developers.cloudflare.com/analytics/web-analytics/
Describe alternatives you have considered
Additional context

Pls assign to me.

Implemented https://github.com/awslabs/data-on-eks/pull/703


Fix nightly

Fix #1349

envvar usage prevented CI from starting. See https://github.com/opendp/opendp/actions/runs/8135561781/workflow. The problem is really with release.yml, not nightly.yml. Simplify, by just repeating inputs.dry_run || inputs.fake. In some cases, only check fake, because not every dry_run is also fake

Does the usage of dry_run vs fake now represent the behavior we want?
Do we really need to support fake? I guess the idea is to speed up the build when we're exercising other parts of this... but I think it has been confusing.
If we do want to support it, would it be more clear to have a select with three options, rather than than two checkboxes, one of which implies the other?

Need to manually run nightly on this branch and confirm that it works.

Started a fake dry-run of release on this branch: https://github.com/opendp/opendp/actions/runs/8145972573

Got almost to the end and then failed with:

subprocess.CalledProcessError: Command '('/home/runner/work/opendp/opendp/docs/venv/bin/python', '-R', '-m', 'sphinx', '-W', '--keep-going', '-D', 'smv_metadata_path=/tmp/tmp5oz_xycs/versions.json', '-D', 'smv_current_version=nightly', '-c', '/home/runner/work/opendp/opendp/docs/source', '/tmp/tmp5oz_xycs/a4aa05bb70d20bf500b2507680e332731ff02934/docs/source', '/home/runner/work/opendp/opendp/docs/build/html/en/nightly')' returned non-zero exit status 1.

Real error is here:
ERROR: Unknown directive type "tabs".

see if tabs was brought over without updating dependencies?

https://github.com/opendp/opendp/actions/runs/8255690917
Rerun with sync and dry-run checked, targeting nightly channel. Check tomorrow if it worked.

yay! sort of: I don't see the earlier error, and I'd guess that forgetting to sync is a likely cause. But there is still an error in the R build:
Run bash tools/r_stage.sh -n
...
***** NOTES *****
Prepare inst/AUTHORS and LICENSE.note
$ Rscript tools/update_notes.R
Error: Error in loadNamespace(x) : there is no package called ‘stringr’
Calls: vapply ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
Execution halted

Running Release with nightly/sync/dry-run on this branch. https://github.com/opendp/opendp/actions/runs/8266421376

R build passed!
Ready for review.


Reorg of Install, Deploy, and Admin content

Reorg based on this draft outline: https://docs.google.com/document/d/1j0WF--wK8Wut1u-AQdQsk_DzKn_WRUuk3Zw0l-32Yss/edit

Code base has moved beyond this PR. Closing.


[18.09 backport] Update containerd to v1.2.7

backport of https://github.com/moby/moby/pull/39364 for 18.09
~created on top of https://github.com/docker/engine/pull/194 - only the last commit is new~
From the release notes: https://github.com/containerd/containerd/releases/tag/v1.2.7

Welcome to the v1.2.7 release of containerd!
The seventh patch release for containerd 1.2 introduces OCI image
descriptor annotation support and contains fixes for containerd shim logs,
container stop/deletion, cri plugin and selinux.
It also contains several important bug fixes for goroutine and file
descriptor leakage in containerd and containerd shims.
Notable Updates

Support annotations in the OCI image descriptor, and filtering image by annotations. containerd/containerd#3254
Support context timeout in ttrpc which can help avoid containerd hangs when a shim is unresponsive. containerd/ttrpc#31
Fix a bug that containerd shim leaks goroutine and file descriptor after containerd restarts. containerd/ttrpc#37
Fix a bug that a container can't be deleted if first deletion attempt is canceled or timeout. containerd/containerd#3264
Fix a bug that containerd leaks file descriptor when using v2 containerd shims, e.g. containerd-shim-runc-v1. containerd/containerd#3273
Fix a bug that a container with lingering processes can't terminate when it shares pid namespace with another container. moby/moby#38978
Fix a bug that containerd can't read shim logs after restart. containerd/containerd#3282
Fix a bug that shim_debug option is not honored for existing containerd shims after containerd restarts. containerd/containerd#3283
cri: Fix a bug that a container can't be stopped when the exit event is not successfully published by the containerd shim. containerd/containerd#3125, containerd/containerd#3177
cri: Fix a bug that exec process is not cleaned up if grpc context is canceled or timeout. contaienrd/cri#1159
Fix a selinux keyring labeling issue by updating runc to v1.0.0-rc.8 and selinux library to v1.2.2. opencontainers/selinux#50
Update ttrpc to f82148331ad2181edea8f3f649a1f7add6c3f9c2. containerd/containerd#3316
Update cri to 49ca74043390bc2eeea7a45a46005fbec58a3f88. containerd/containerd#3330

marked as "WIP" because upstream wasn't merged yet

Rebased, because https://github.com/docker/engine/pull/194 was merged

rebased again to trigger CI

rebased (again) because CI results were purged (again 😞)

[2019-09-24T19:24:05.764Z] === RUN   TestBuildWithHugeFile
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] ----------------------------------------------------------------------
[2019-09-24T19:24:52.405Z] FAIL: check_test.go:347: DockerSwarmSuite.TearDownTest
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] check_test.go:352:
[2019-09-24T19:24:52.405Z]     d.Stop(c)
[2019-09-24T19:24:52.405Z] /go/src/github.com/docker/docker/internal/test/daemon/daemon.go:414:
[2019-09-24T19:24:52.405Z]     t.Fatalf("Error while stopping the daemon %s : %v", d.id, err)
[2019-09-24T19:24:52.405Z] ... Error: Error while stopping the daemon d474da107fa40 : remove /go/src/github.com/docker/docker/bundles/test-integration/3/DockerSwarmSuite.TestAPISwarmLeaveOnPendingJoin/d474da107fa40/docker.pid: no such file or directory
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] ----------------------------------------------------------------------
[2019-09-24T19:24:52.405Z] PANIC: docker_api_swarm_test.go:432: DockerSwarmSuite.TestAPISwarmLeaveOnPendingJoin
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] Creating a new daemon at: /go/src/github.com/docker/docker/bundles/test-integration/3/DockerSwarmSuite.TestAPISwarmLeaveOnPendingJoin
[2019-09-24T19:24:52.405Z] [de1b69f6c1e27] waiting for daemon to start
[2019-09-24T19:24:52.405Z] [de1b69f6c1e27] daemon started
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] Creating a new daemon at: /go/src/github.com/docker/docker/bundles/test-integration/3/DockerSwarmSuite.TestAPISwarmLeaveOnPendingJoin
[2019-09-24T19:24:52.405Z] [d474da107fa40] waiting for daemon to start
[2019-09-24T19:24:52.405Z] [d474da107fa40] daemon started
[2019-09-24T19:24:52.405Z]
[2019-09-24T19:24:52.405Z] waited for 156.299308ms (out of 30s)
[2019-09-24T19:24:52.405Z] [de1b69f6c1e27] exiting daemon
[2019-09-24T19:24:52.405Z] [d474da107fa40] daemon stop timeout
[2019-09-24T19:24:52.405Z] Attempt #2: daemon is still running with pid 14382
[2019-09-24T19:24:52.405Z] Attempt #3: daemon is still running with pid 14382
[2019-09-24T19:24:52.405Z] Attempt #4: daemon is still running with pid 14382
[2019-09-24T19:24:52.405Z] Attempt #5: daemon is still running with pid 14382
[2019-09-24T19:24:52.405Z] tried to interrupt daemon for 6 times, now try to kill it
[2019-09-24T19:24:52.405Z] ... Panic: Fixture has panicked (see related PANIC)


[dcc32 Fatal Error] F2084 Internal Error: DBG3198

Hi, I tried build SpringAndMVC and I have this error final.Why?:)
Ales

You have installed and configured the latest versions of DMVC and Spring4D (release 1.2)?
Has this link Embarcadero that can help you: http://docwiki.embarcadero.com/RADStudio/Seattle/en/F2084_Internal_Error_-%25s%25d(Delphi)

Yes I have,I have the same problem in other project with TSession,

I have same problem with today Spring release/1.2 without DMVC.In Debug mode I get this error,in Release mode compiled ok.Delphi XE6

This is an error in the compiler (reported as https://quality.embarcadero.com/browse/RSP-14974)
The circumstances to cause this are listed in my comment on that issue.
If you follow my recommendation to build Spring4D and then only point to the dcu directory instead of adding the source directories to the library or search path it will not appear as far as I know.
However I removed the inline from the TCollections.Create* methods as they did not have much of a beneficial effect anyway so this error should be gone once you update to the latest commit in release/1.2

Thank you for response Stefan. Very enlightening.


cookie-store: session isn't restored on refresh

I upgraded from ember-simple-auth:0.6.7 to 0.8.0-beta.2 and it doesn't work anymore.
I thinks it might be related to the new secure key introduced in 0.8.0-beta.1; it seems this key is now included in the cookie value :
{"secure":{"authenticator":"authenticator:grails","username":"florentblanvillain@gmail.com","roles":["USER"],"access_token":"2giektv95s0n4cid7gblandq0gf23"}}

That's already fixed on master. Will be released in the next days.

Ok, thank you !


test(e2e): e2e-nightly-test - TestApp_Tx failure

Context / Overview
The e2e-nightly-test is not failing on main but it has been failing on v1.x.
Need to find why the behavior is different. Something that was not back ported?
The failure (see below) can be reproduced in local tests on a Ubuntu VM, but it’s not all the time that the failure happens. Need to run multiple times with the same configuration and manifest and it eventually fails, so not too deterministic.
Description of the Failure
This particular error that has been happening on the e2e-nightly-test for v1.x. This usually happens for more than one particular test.
         --- FAIL: TestApp_Tx (126.10s)
    --- FAIL: TestApp_Tx/validator04 (120.02s)
        e2e_test.go:64:
            	Error Trace:	/cometbft/cometbft/test/e2e/tests/app_test.go:98
            	            				/cometbft/cometbft/test/e2e/tests/e2e_test.go:64
            	Error:      	Condition never satisfied
            	Test:       	TestApp_Tx/validator04
            	Messages:   	submitted tx (3227101E53F267854F48B6F58617DF805AC60759934C3412B0C682B9EFB1F5F5) wasn't committed after 30s
FAIL
FAIL	github.com/cometbft/cometbft/test/e2e/tests	153.834s
FAIL

Definition of Done (DoD)
Tests are passing on v1.x or at least is no errors like the one above are happening for a period of time (a few days).

It seems this PR helps fix the issue.
Ran a e2e manual on v1.x and finally all tests passed. Will wait until the scheduled nightly passes a couple of days without failures and if it's all good will close this PR.

Still failing in the latest nightly run: here and here.
But now they are failing in full nodes, which are not validators.

Investigation continues.

So, some additional information gathered from the failures.
First, I was able to reproduce this error in a very simple scenario considering the version of v1.x from which @andynog has created a branch with improved logging and other features. It was enough to use the proper manifest, run start then test and the error was observed.
The core reason for the error was that the node, in the case a validator, did not broadcast the transaction it has received from the RPC endpoint. This transaction was in the mempool however, this was clear when running the re-checktx code, that always found this transaction and eventually evicted in from the mempool.
By the way, among the debugging improvements that are included in this branch, logging at info level whenever the application evicts a transaction to mempool should be part of the main code, as this helps a lot debugging this kind of failure.
Why the transaction was not sent to any peer by the mempool?
No idea. The behavior is non-deterministic, some times the test fails, some times it does not. I have discarded the component that a node did not sent a transaction because of the state of the peer (e.g., it was lagging), but I could not discard the component that transaction was not sent because it was registered in the mempool that the transaction was already sent or received to or from that peer.
In any case, apparently there was a corner case in the complex mempool concurrency model in which a transaction was added to the mempool but forever ignored by the sender routine. Smells like concurrency to me.

When considering the current version of v1.x, including in particular https://github.com/cometbft/cometbft/pull/4109, it was much harder to reproduce the same issue. Although, as above mentioned, it was observed in the last night execution.
The manifests where the failures have happen are, however, much more complex (more nodes, more perturbations, etc.) and the errors where only observed in full nodes, i.e., non-validators.
Since it is hard to reproduce those failures, we don't know whether the reasons is the same, namely the mempool never broadcasting a transaction received via RPC, or a different one.

Just another update. I've ran another e2e-manual test on v1.x and it all passed. I believe the last night failures might be related to the CI infrastructure. I haven't been able to reproduce these latest failures yet on my local testing.

So, some additional information gathered from the failures.
First, I was able to reproduce this error in a very simple scenario considering the version of v1.x from which @andynog has created a branch with improved logging and other features. It was enough to use the proper manifest, run start then test and the error was observed.
The core reason for the error was that the node, in the case a validator, did not broadcast the transaction it has received from the RPC endpoint. This transaction was in the mempool however, this was clear when running the re-checktx code, that always found this transaction and eventually evicted in from the mempool.
By the way, among the debugging improvements that are included in this branch, logging at info level whenever the application evicts a transaction to mempool should be part of the main code, as this helps a lot debugging this kind of failure.
Why the transaction was not sent to any peer by the mempool?
No idea. The behavior is non-deterministic, some times the test fails, some times it does not. I have discarded the component that a node did not sent a transaction because of the state of the peer (e.g., it was lagging), but I could not discard the component that transaction was not sent because it was registered in the mempool that the transaction was already sent or received to or from that peer.
In any case, apparently there was a corner case in the complex mempool concurrency model in which a transaction was added to the mempool but forever ignored by the sender routine. Smells like concurrency to me.
When considering the current version of v1.x, including in particular #4109, it was much harder to reproduce the same issue. Although, as above mentioned, it was observed in the last night execution.
The manifests where the failures have happen are, however, much more complex (more nodes, more perturbations, etc.) and the errors where only observed in full nodes, i.e., non-validators.
Since it is hard to reproduce those failures, we don't know whether the reasons is the same, namely the mempool never broadcasting a transaction received via RPC, or a different one.

Yes, we should add these additional debug messages to main but we need to be careful not to affect performance and do it the right way. I have some ideas to improve the logic related to this issue, there's a PR opened but I might do it in a different way (allow a binary compilation without the debug messages).

We had several successful runs on v1.x and no failures on main and the problem above is not happening after the two issues have been addressed.
If the runs over the weekend are successful  I'll close this issue next week.

Tests have been passing successfully on v1.x and main, so closing this issue
https://github.com/cometbft/cometbft/actions/workflows/e2e-nightly-1x.yml
https://github.com/cometbft/cometbft/actions/workflows/e2e-nightly-main.yml


Adjustments on this page for a single sentence

By using the information staged in the connector space, the inbound synchronization process creates in the metaverse the integrated view of the data that is stored in the connected data sources.
[Please check the cohesion or structure, i propose: By using the information staged in the connector space, the inbound synchronization process creates integrated view of the data in the metaverse that is stored in the connected data sources.]

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

ID: 6a236d52-de87-bd3f-89b4-eb171a0592b9
Version Independent ID: 8d4b8598-6764-d7f6-11c1-9e0052735797
Content: Azure AD Connect sync: Understanding the architecture - Azure
Content Source: articles/active-directory/hybrid/concept-azure-ad-connect-sync-architecture.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@prontohostau Thanks a lot for sharing your feedback to improve our Azure documentation, our team will review it and update the document accordingly.


apg to fasta

Hi, this is a great tool! I have managed to manually curate my map, however, I was was using the pretext_to_tpf.py script to convert my APG file into a fasta file and got this error.
Traceback (most recent call last):
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/scripts/pretext_to_tpf.py", line 244, in
cli()
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/scripts/pretext_to_tpf.py", line 149, in cli
build_asm.remap_to_input_assembly(prtxt_asm, input_asm)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 74, in remap_to_input_assembly
self.cut_remaining_overhangs()
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 123, in cut_remaining_overhangs
self.cut_fragments(fnd)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 143, in cut_fragments
self.qc_sub_fragments(fnd, sub_fragments)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 187, in qc_sub_fragments
raise ValueError(msg)
ValueError: Sum of fragment lengths 4_694_157 does not match orginal fragment length 4_707_000
Expecting 1 abutting sub fragments but got 0
I used the TPF file I generated before the manual curation and the apg file generated after, I was just wondering what it means by different fragment lengths? I am not sure where the fragments could have gone?
Thank you very much.

Did you fix it? If not, we can help you track down the problem scaffold.

Hi, thank you for such a quick response, I managed to fix it the first time and realised that I didn't flood fill my chromosomes. But I made some more rearrangements after and flood filled it to make sure all the scaffolds were included the second time, but I am still receiving the same error, so I'm not quite sure what's causing it.
This is the error on the second run.
Traceback (most recent call last):
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/scripts/pretext_to_tpf.py", line 244, in
cli()
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/miniconda3/lib/python3.12/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/scripts/pretext_to_tpf.py", line 149, in cli
build_asm.remap_to_input_assembly(prtxt_asm, input_asm)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 74, in remap_to_input_assembly
self.cut_remaining_overhangs()
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 123, in cut_remaining_overhangs
self.cut_fragments(fnd)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 143, in cut_fragments
self.qc_sub_fragments(fnd, sub_fragments)
File "/gpfs01/home/mbars7/yahs/pyrenaica_hap1/agp-tpf-utils/src/tola/assembly/build_assembly.py", line 187, in qc_sub_fragments
raise ValueError(msg)
ValueError: Sum of fragment lengths 4_694_157 does not match orginal fragment length 4_707_000
Expecting 1 abutting sub fragments but got 0
And I have attached the agp file used. Do let me know if you need to see any other file. Any help would be really appreciated.
Thank you so much :)
6_8.3_flod2_pyrenaica_hap1_gap_telomere_gfa.pretext.agp.txt

Sorry, I also found that the "original fragment length" of 4_707_000 relates to scaffold 17 in my TPF file, which also makes up scaffold 5 in my AGP file, do scaffolds have to remain intact? Is this because I split up scaffold 17? Can I ask how the sum of the fragments is calculated as I added up the fragments in scaffold 5 and scaffold 17 separately and it doesn't add up to 4_694_157? So just wondering how it calculated 4_694_157. Thank you!

OK, so running the asm-format script on your file, to generate the STR output format I find useful for debugging:
asm-format -f STR 6_8.3_flod2_pyrenaica_hap1_gap_telomere_gfa.pretext.agp.txt | less

I can see that there is a small 12,843 bp long fragment of scaffold_17 in Scaffold_2, your second chromosome in PretextView:
  Scaffold_2
           115_591  scaffold_2:1-115591(+) Painted
               100  Gap:100 scaffold
            12_843  scaffold_17:64218-77060(+) Painted
               100  Gap:100 scaffold
            64_217  scaffold_6:11828855-11893071(+) Painted
               100  Gap:100 scaffold
        11_764_637  scaffold_6:64218-11828854(-) Painted
               100  Gap:100 scaffold
        22_810_037  scaffold_3:1-22810037(+) Painted
               100  Gap:100 scaffold
         1_053_167  scaffold_39:25687-1078853(-) Painted
               100  Gap:100 scaffold
         5_985_066  scaffold_6:12072881-18057946(-) Painted
               100  Gap:100 scaffold
            38_531  scaffold_6:18057947-18096477(-) Painted
               100  Gap:100 scaffold
           179_809  scaffold_6:11893072-12072880(+) Painted
               100  Gap:100 scaffold
         2_645_759  scaffold_23:102748-2748506(+) Painted

Since it is only 1 pixel long, it is assumed to be a mistake and is discarded. You somehow need to adjust the boundaries of the rearrangement so that this pixel is moved to the end of one of the two other pieces of scaffold_17 found in Scaffold_5 or Scaffold_8. If you have difficulty doing this I can get one of our curators to give you some hints.

Thank you very much, this was really helpful, I will remove these 1 pixel long fragments and see if it works :)

Hi, sorry I had to reopen this, I have tried to take out these one pixel fragments from all my painted scaffolds, I re ran the asm_format.py script on my new agp file to recheck everything. I found no 1 pixel fragments in any of my new painted scaffolds, however I am still getting the same error. I'm wondering if all the fragments of one scaffold have to stay together? as scaffold 17 in chromosome 5 appears to be problematic but i'm not sure why as it's quite a large fragment?
Just incase, this is the new AGP file with the 1 pixel fragments removed.
6_8.5_flod2_pyrenaica_hap1_gap_telomere_gfa.pretext.txt
Thank you!

Hi, Thank you for your reply! By "removed" I meant moving it to the end of the assembly where all the debris was, so it's not included in the painted scaffolds. I'm just wondering, how does this work if fragments in the "debris" section are equivalent to 1 pixel? Would I need to get rid of these in the original fasta file beforehand?
Thank you!

Any small fragments missing from the PretextView AGP will be rescued and added to the unplaced "debris" scaffolds.
This doesn't happen to your single pixel fragment of scaffold_17 because it is part of a cut scaffold.

Hi, thank you this worked great :)


Add "How to support us" page as an ascciidoc for the documentation under the "Eclipse Adoptium" group

Is your feature request related to a problem? Please describe.
Add "How to support us" page as an ascciidoc to describe the preferred, various ways that people and organizations can support our project, and that EF membership fees are directed to general services, not to specific project needs

closed in https://github.com/adoptium/adoptium.net/commit/1856eeba85961222204d1593eaad6a545d24a708


Wrong window icons

I'm getting this in OS X

Force quit and start it up again and it should be fine ✌

That did the trick, thx!


Add Italian translation

Thanks for the great work, you took a lot off work off our shoulders 😌. A big thanks for your contribution. We will happily include your translation in the next release 😄.

I added the backend support for the language on the dev branch, so you can try it out by building from dev, or wait until 1.3.7 will go live, probably in a week or so. Thanks again for the work.

Thank you. Also sorry for the target branch, I totally forgot 😅
Do you plan using a platform like Weblate or Crowdin to handle translations?

Thank you. Also sorry for the target branch, I totally forgot 😅

No worries, we appreciated the confidence of going straight for the master branch😅

Do you plan using a platform like Weblate or Crowdin to handle translations?

We have never considered to use a platform like that, but seeing how difficult it is to manage multiple languages, it seems like a good idea. If you want you can create an issue proposing this, especially if you have experience with any of those platforms and can recommend how / where we should proceed with this.

@gdonisi Sorry that this took so long, but I finally created a release including your translation! 1.3.7 should be live in F-Droid and the Playstore tomorrow.


vscode-eslint is not recognizing eslint v2.x new module flag

Hi I have on my machine eslint v 2.8 and currently I'm working with a js project that have es2015 syntax!.
When I lint my code with the eslint terminal tool everything is correct but when I see the same code in visual studio code using the eslint plugin is showing an error on a file that have import statement.
Currently my .eslintrc.json file see like this:
{
  "env": {
    "browser": true,
    "node": false,
    "es6": true
  },
  "parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module",
    "ecmaFeatures": {
    }
  }
}

and my code looks like this:
import "ngDraggable";
import angular from "angular";
import "./klondike/game.css!";

import "klondike/klondike.js";

angular.module("solitaire", ["klondike", "ngDraggable"]);

angular.element(document).ready( () => {
    angular.bootstrap(document, ["solitaire"]);
});

Now when I change the rules to eslint v 1.x to allow the modules vs code now doesn't show any error on the import statement anymore. But this is not desirable by obvious reasons.
{
  "env": {
    "browser": true,
    "node": false,
    "es6": true
  },
  "ecmaFeatures": {
    "modules": true
  }
}

Do you know If I'm missing something or perhaps is this an error? Thanks!
By the way if you want to read more about this rule you can go to this link: migrating-to-2.0.0#language-options

@Alexisvt sorry for the late answer but I was out on vacation.
This is not desirable. The eslint extension looks for the eslint library at the following locations:

in the node_modules folder of the workspace folder opened in vscode
globally installed.

Could it be that when run in the terminal you use a globally installed eslint and you have a local installed eslint as well. That would explain the different behavior.

Hi @dbaeumer yes! That was the reason, my bad!! I checked the package.json file and I found a devDependencies to a eslint v^1.5.1. Thanks for the help :smile:


[BUG] Zep History not working with Summarizer

Describe the bug
If Zep memory summarizer is enabled throwing an error like "System messages are only permitted as the first passed message." Error message is clear and it's right. I don't understand how is working at the background. I think Zep messages include summarized message and flowise sending all messages to Chat API.
To Reproduce
Steps to reproduce the behavior:

Use Zep open source memory.
Enable the summarizer option from environment variables.
Create a flow using Zep memory.
Keep chatting with Anthropic or some other Chat model.
Message window when exceeded then you will summarized content on the Zep admin UI.
If you will send a new message to chat you will see this error "System messages are only permitted as the first passed message."

Expected behavior
Summarized content must be include the human message template. Selected variable "K" (how many messages will fetched from Zep) should added after summarized content.

Yep, by nature Anthropic doesn't support System Message at later stage, only as the first message at the beginning. Only OpenAI permits that.
Now, I'm not sure if Zep supports other LLM to do the summarization


Minor fixes for Turkish language.

Corrected capitalization in some places to match the referenced English language.
Fixed a spelling mistake in 1 word -> Documentation -> Dökümantasyon -> Dokümantasyon (correct spelling)

Cool!


Add metrics for SSL keystore expiration time

Why are the changes needed?

Add metrics for SSL keystore expiration, then we can add alert if the keystore will expire in 1 month.
How was this patch tested?

Integration testing.

Was this patch authored or co-authored using generative AI tooling?

No.

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

Project coverage is 0.00%. Comparing base (aa33521) to head (3cb6146).

Files with missing lines
Patch %
Lines

...apache/kyuubi/service/TBinaryFrontendService.scala
0.00%
14 Missing :warning:

...e/kyuubi/server/KyuubiTBinaryFrontendService.scala
0.00%
10 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6866   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         687     687
  Lines       42504   42525   +21
  Branches     5798    5800    +2
======================================
- Misses      42504   42525   +21

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

thanks, merged to master/1.10


update material alpha model 01 so that it is not completely transparent

Fixed. If this is still transparent, then it is a bug with that client.


semantic: symbol id is None in if (true) function id() {}

https://github.com/oxc-project/oxc/blob/54e2e76d173d77d57ac1611d4df3b31ae769ef14/crates/oxc_semantic/src/post_transform_checker.rs#L652-L659
This is causing trouble in the linter.

Expression
In the expression form if (function foo() {}) {}, the function (and its name) is completely unobservable at runtime, but I guess we should create a symbol for foo and bind it in the function's scope (same as any other function expression).
Presumably no-one will write such pointless code, so it should only matter in tests.
Declaration
It seems like the function declaration form does create a binding:
// Sloppy mode code
if (true) function foo() {}
console.log(typeof foo); // Logs 'function'

So I guess we should just create a symbol for the function ID, and bind it in the scope above. Same as a var statement, except no error in this case:
let foo;
if (true) function foo() {}

I believe this is a specific case of a more general complication over what scope functions declarations' are bound to in sloppy mode.
https://github.com/babel/babel/pull/14203#issuecomment-1038187168
I don't know what spec says (I think it's Annex B), but in NodeJS and Firefox, the observed behavior is that a function declaration in sloppy mode creates two independent bindings:
function outer() {
    let getInnerF;
    {
        function f() { return 123; }
        getInnerF = () => f;
    }
    console.log(f()); // Logs 123
    console.log(getInnerF()()); // Logs 123
    f = undefined;
    console.log(typeof f); // Logs undefined
    // `f` binding in this scope is now undefined,
    // but in the inner block, `f` is still the function.
    // Therefore there are 2 `f` bindings.
    console.log(getInnerF()()); // Logs 123
}
outer();

https://github.com/oxc-project/oxc/pull/5673


add aspx

Fixes #139
Changes proposed:

[X] Add
[ ] Prepare
[ ] Delete
[ ] Fix

Things I've done:

[X] I've pulled the latest master branch
[ ] I've run npm install to install all the dependenies
[ ] I've checked my code, it is clean.
[ ] I've run ESLint.
[X] My pull request fixes an issue, I referenced the issue.
[X] My pull request is not too big, otherwise I've already squashed it.
[ ] I've run npm run build to build the extension. (If I had done something with the extension.)

adds aspx

Feel free to change the Changelog accordingly if you want.

Okey, I'll submit another pr ;)


ACM-3851 ACM-3850 : Addon detection fix

Regarding:
ACM-3851
ACM-3850
This change reuses an already implemented check for ManagedClusterAddons that lack a respective ManagmentClusterAddon.

/lgtm


Add open window endpoints

Add the documentation to the two endpoints that make use of the remoteClientUI scope.

Thanks! Cherry-picked as aad593a8117654c392cfaab8abe903e480046cad.


Access to PostgreSQL Server from OmniDB with SSH Tunneling

Hi Guys,
I am quite new to OmniDB. I recently came to know about it decided to give it a go after working with pgAdmin (III and IV), EMS SQL Manager for PostgreSQL, DBVisualizer etc.
I was wondering if the tool can:

connect to PostgreSQL instances with SSH tunneling
can "remember" the connection details where SSH is used. At the moment pgAdmin 3 does not allow this.
can show components like DBLinks / foreign servers and their user mappings.

Sorry if this is a question already answered or already documented - any direction would be highly appreciated.

Hi @sadequlh ,
Thank you for your questions. I will try to answer them below.

OmniDB can connect to PostgreSQL through a SSH tunnel, but you have to manage the tunnel manually yourself. It is in the roadmap, in the near future we will add SSH tunneling management features for OmniDB.

Regarding Foreign Servers and Foreign Data Wrappers, it is also in the roadmap, OmniDB will support them very soon.

I suggest to add ability to not only connect via tunnel, but also fully interact with server via ssh.
It'll allow to edit configs, browse logfiles and stop/start server from single console.

Hi @dan-aksenov ,
Thanks for your suggestion, we are already considering this implementation.
Regards,
William Ivanski

Hi all,
One question about ssh tunnelling...
Is it available with MYSQL connections?
Because I'm getting an error during the connection and I don't understand why (below screenshot)

This is my Configuration

the only difference is that i'm trying to connect to the DB using a DNS and not the IP
With a PostgreSQL connection with the same configuration i'm able to access via OmniDB
Testing the connection with a terminal both are working fine
Thanks for the answers

Hi @agentili ,
Thanks for reaching out. Yes, SSH tunnel is independent of RDBMS, so it works with MySQL.
Please check if client addresses are granted privileges in MySQL. You can check this on the Roles tree node in OmniDB, or SELECT * FROM mysql.user as a user with admin rights.
Regards,
William Ivanski

Hi @wind39 ,
I checked your screenshot about SSH runnel, it seems you have tested all connecting with ssh password only and ssh key is blank. I tried to connect with ssh private key, but it seems not working. Can you please confirm that it's working feature at your end?
Regards,
Vishal Z.

Hi @wind39,
I checked again the connection and it works now.
I'm able to connect to the MySQL DB and use it, so I can confirm you that SSH tunnelling works also on MySQL
Thank you for your answers.


Rust semicolon handling

    print(f"hello {a+1} world")

transpiles to
    println!("{}",vec!["hello ", &(a + 1).to_string(), " world"].join(""););

Notice the extraneous semicolon in the end.
I tried fixing it via:
https://paste.ubuntu.com/p/nxDYpDHfZh/
But it needs more work. Some of the semicolons are inserted by the super class, which can't be touched without breaking other languages.

Turns out that the semi colon was caused by an extra ast.Expr() inserted by the rewriter. I've removed it now.
But it still unclear if ast.Expr should or should not insert a semicolon.
https://docs.python.org/3/library/ast.html#ast.Expr
When an expression, such as a function call, appears as a statement by itself with its return value not used or stored, it is wrapped in this container.
It seems appropriate to add a semicolon for this case. I'm not sure if there are other cases where ast.Expr is used.


JavaScript: Avoid a few bad join orders

These only seem to matter on very large snapshots (for the flow-summary projects where I encountered them I'm working with a roughly gecko-sized one).
Consequently, the evaluation on big-apps is not particularly compelling. I had hopes for gecko-dev, but that still timed out on master; I suspect memory pressure, so I'm trying one last rerun with 16G of heap.

That evaluation looks pretty good to me. Unless it causes a regression on smaller snapshots I'd be in favor of merging it even if it doesn't fix gecko.

I can reproduce the problem on gecko-dev locally:
[2020-03-23 11:44:06] (3001s) Tuple counts for Promises::PromiseTypeTracking::promiseStep#2#ffff:
                      32168     ~6%     {3} r1 = SCAN Promises::PromiseTypeTracking::promiseStep#fff AS I OUTPUT I.<1>, I.<0>, I.<2>
                      999998257 ~0%     {4} r2 = JOIN r1 WITH TypeTracking::TypeTracker::append_dispred#fff_102#join_rhs AS R ON FIRST 1 OUTPUT r1.<1>, R.<2>, R.<1>, r1.<2>
                                        return r2

That's just a whisker under a billion tuples in the second pipeline step, and it wasn't done yet. I don't think the version of promiseStep with two type-tracker arguments can be made to scale on gecko-dev in its current formulation.

Unless it causes a regression on smaller snapshots

OK, I can add a few smaller ones into the mix.

I don't think the version of promiseStep with two type-tracker arguments can be made to scale on gecko-dev in its current formulation.

Adding a pragma[inline] fixes it. Should I add that to this PR, or do you want me to open a separate PR?

I encountered the same bad join orders for reachableFromStoreBase and flowThroughProperty in my evaluation of https://github.com/Semmle/ql/pull/3095.
(And a similar bad join order in Configuration::onPath).

I don't think the version of promiseStep with two type-tracker arguments can be made to scale on gecko-dev in its current formulation.

Adding a pragma[inline] fixes it. Should I add that to this PR, or do you want me to open a separate PR?

I encountered the exact same thing here https://github.com/Semmle/ql/pull/3093.
And the same fix is part of that PR.
I think we should add the fix here, and then I'll do a rebase.

I have added the pragma[inline].

I can add a few smaller ones into the mix.

Actually, it turns out I had previously evaluated this PR (minus the pragma[inline]) on smoke-tests.slugs:
Project     e3164d04148@2821b0101  e3164d04148@ee62706ad  tuples    dpm       time
amphtml     2312                   2335                   0.989312  0.997236  1.00995
brackets    1442                   1472                   0.991917  0.998574  1.0208
underscore  267                    276                    0.998853  0.999938  1.03371
ace         1185                   1227                   0.998875  0.999965  1.03544
react       841                    874                    0.991512  0.999076  1.03924

Not exactly comprehensive, of course, but perhaps sufficient as an indication that it doesn't completely ruin small projects?

Oh yeah that looks bad. It looks like the same issue Erik mentioned in https://github.com/Semmle/ql/pull/3093 where he added the much-needed pragma[inline] there.

I tried to see what impact this PR would have on my current performance PR.
In my investigations of join-orders I had had troubles with the UnvalidatedDynamicMethodCall.ql query when running the bwip-js benchmark.
And that exact query/benchmark combination had a performance regression when merging this PR into my PR.
I tried to run a small evaluation of this PR against master to see if it was some kind of "performance-conflict" between the two PRs.
It wasn't, the regression also appears in the evaluation against master:
https://git.semmle.com/erik/dist-compare-reports/tree/profiling-js-asger.northeurope.cloudapp.azure.com_1584974582485
I still think this PR should be merged.


obtain datamodule used in  code

Hi. This is a pleasure to read your paper, which contains interesting and elegant ideas.
Could you provide an introduction to the original data and the general framework of BaseDataModule?Thank you so much!


"CTRL-C" to quit does not work for Python BottleWebProject.

vs environment

python version
download python 3.9.13 from Microsoft store.
Steps to Reproduce

Create BottleWebProject in vs.
Create virtual environment for the project.
Start and run the project.
Hit "Ctrl-C" to quit the terminal.

Expected behavior
server should be quit after press "Ctrl-C" to quit the terminal.
Actual behavior
"CTRL-C" to quit does not work after press ctrl-c.
Additional context and screenshots

Can't repro this either, can you share a gif of what's going on on your side?

The debug mode may interfere with the default Ctrl+C behavior. Debug mode often enables features like code reloading, which can complicate the shutdown process. Try running the server without debug mode to see if the issue persists.

Closing this issue as it appears to be beyond the scope of PTVS to address.


Endpoints to get appointments for customerPets

Description
We need routes to get all of the appointments for a customerPet.

[x] GET /customerPets/:customerPetId/appointments
description: Returns all of the appointments for a customer pet
[x] GET /customerPets/:customerPetId/appointments/:status
description: Returns all of the appointments for a customer pet by the status sent in the parameters
example: GET /customerPets/:customerPetId/appointments/Pending returns all appointments in a Pending Status for the Customer Pet

Type of Change

[ ] This is a bugfix.
[x] This is a new feature.
[ ] This is part of a feature.

Organization

[ ] Have you linked this pull request to a Trello card?
[ ] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[x] Is this a work in progress?
[ ]  Is this ready to be reviewed?
[ ]  Have you added two reviewers to this pull request?

 Endpoints for Customer Pet Appointments

 Endpoints for Customer Pet Appointments


Implement BigQuery Parameterization

https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs/query#request-body
A query can put placeholders in the query text, which can then be filled in with queryParameters. Depending on what parameterMode is set to, the parameter can be positional ? or names @somename.
See also: GoogleCloudPlatform/google-cloud-python#2551

@dwsupplee do you have anything blocking this?  If so, please let me know.  If you are actively working can you give me an estimate to completion?  Thanks!

Hey @danoscarmike, no blockers and the estimated completion is by tomorrow.

@dwsupplee any update?  Can you link PR when ready?  Thanks!

@danoscarmike just wanted to provide a quick update. I ran into a few snags with making sure we support the various standard SQL types that held things up a little bit. Have a good gameplan now and the new ETA is this weekend.

Ha! Looks like we were on each other's minds :)

Thanks David!


Move council google groups under the jupyter.org domain

Our jupyter.org google account enables us to create google groups under the jupyter.org domain, for example<EMAIL_ADDRESS>In addition to having better branding, we can create google groups that have other groups as members. This finally lets us create a union of councils google group that automatically is the union of all of the council groups.

I did some experiments with parent groups and subgroups, and indeed we can create a parent group that sends messages to subgroups.

Some links for reference about how to import messages into a google group:

[recommended?] https://github.com/GAM-team/got-your-back/wiki#--action-restore-group (for examples, see here)
https://www.reddit.com/r/gsuite/comments/gw6994/ importing_messages_into_google_groups/?captcha=1


Creating External Data Source Storage Gen 2 | Scheme Not Supported

Hi,
I need some with creating External Data Source in SQL Server.
I'm trying to create an external source in SQL Server on Azure Storage Gen 2.
I first created Database Scoped Credential using SAS Identity.
And then when I try to create the External Data Source it gives the below error message:
CREATE EXTERNAL DATA SOURCE [datasource]
WITH
( LOCATION =<EMAIL_ADDRESS>CREDENTIAL = [credential]
) ;
Scheme of the input URI is not supported. Please revise the following scheme and try again: 'adls'
I even used the following but the same issue:
CREATE EXTERNAL DATA SOURCE [datasource]
WITH
( LOCATION =<EMAIL_ADDRESS>CREDENTIAL = [credential]
) ;
Thank You,

@MithTiwari09
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

@MithTiwari09
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @MithTiwari09, this syntax varies in different versions of SQL Server. Which version of SQL Server engine are you using?
It looks like in your second example, you're still using abs in the location, not adls. Confirm?
Keep in mind this is for documentation feedback, not tech support. If you have any further questions, this may not be the best forum. I recommend Microsoft Q&A (SQL Server), Microsoft Q & A (Azure SQL), SQL Server Feedback, Microsoft Support, or your support partners.

Closing. Happy to continue given further response.
#please-close


Bundle update (Gemfile.lock)

Update current gems, including rubocop

@JoeCohen if you approve, please feel free to merge and deploy in the morning.

Done.
Thanks for the update.
Question: How often should we be doing this.

Good question - i don't really know.


.resetHard command seems not working as expected

As stated here: https://github.com/TheThingsNetwork/arduino-device-lib/issues/262#issuecomment-640048765 seems like the resetHard method is not working as expected.
A fast check of the resetHard implementation shows that there is a difference between the tested code on the issue linked above.
For completeness, here is the piece of code that actually resets the module, got from the issue:
#define RST 2

pinMode(RST, OUTPUT);
digitalWrite(RST, HIGH);
digitalWrite(RST, LOW);
delay(500);
digitalWrite(RST, HIGH);

Fair enough, I've missed that piece on the doc. Just tested and it works as expected. Closing then. Thank you @jpmeijers.


Update gitignore.md

updating legacy comment per user confusion. dbt_modules was replaced by dbt_packages during 1.0 and we're well into versions so it's no longer needed or needs clarification.
What are you changing in this pull request and why?

Checklist

[ ] Review the Content style guide and About versioning so my content adheres to these guidelines.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):

[ ] Add page to website/sidebars.js
[ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):

[ ] Remove page from website/sidebars.js
[ ] Add an entry website/static/_redirects
[ ] Ran link testing to update the links that point to the deleted page

closing as pr #3476 addresses this alreayd