Ensure runtime host uniqueness, improve logging

This PR adds some safety and clarity around the creating and usage of dynamic data sources. Subgraph developers have been susceptible to silent cases of unexpected behavior due to the ability to create multiple runtime hosts with identical triggers and data transformations.  In practice this can lead to a situation where triggers are processed through a mapping multiple times because several runtime hosts have been created with the same contract address, trigger, and mapping file.
Now there is a check when creating a runtime host to ensure we are not instantiating any duplicate hosts and emit a warning. Additional logging has also been added to more clearly show the trigger processing path; a runtime_host context is now included which shows the number of matching runtime hosts for the trigger and the index of the current runtime host doing the processing.

This is not taking the data source context into account. Two data sources that are otherwise identical can differ in behavior due to having a different context. It's questionable whether this is an useful pattern, but if in doubt I think we should allow it.

@leoyvens I see your point and in principle would like to allow a subgraph developer to instantiate duplicate data sources if they for some reason need to. However, I think including data source context in the definition of uniqueness here is more likely to shoot someone in the foot than provide any useful functionality.  I'd rather prohibit duplicate runtime host functionality altogether right now to be safe
I can't think of a reason one would need two data sources triggering from the same event, running the same mapping handlers, and updating the same entities.  On the other hand, data source contexts are likely to be used to simply add useful labels to a data sources without intending for this to be a potential loophole to the duplicate functionality check.

@fordN I might be partial to your argument if I hadn't just come across Livepeer using exactly this pattern https://github.com/livepeer/livepeerjs/blob/as/shares/packages/subgraph/src/mappings/bondingManager_LIP11.ts#L54.


Make update consumable

Issue: #141
Summary

Update now inherits from ConsumableObject, so it can be marked as consumed by the handler.
Command handlers now use LinkedHashMap instead of HashMap to preserve and insertion order of handlers.

Possible next steps

Use numeric priorities for the handlers to sort them and don't rely on insertion order.

As per contribution guidelines
▶ ./gradlew ktlintFormat
BUILD SUCCESSFUL in 13s
6 actionable tasks: 6 executed

▶ ./gradlew check
BUILD SUCCESSFUL in 27s
16 actionable tasks: 15 executed, 1 up-to-date

@vjgarciag96 can you please review it? Thanks!

@vjgarciag96 can you please review it? Thanks!

I wonder if it could make sense to implement this at a handler level to keep the Update objects as pure data objects without behaviour and immutable.
However, that would require a bit more thinking and lot of changes, so I'm happy to go with this approach for the moment, which is a simple implementation with a simple API that works properly.
Thank you so much for the contribution! 🙂 @v1ctor
I'll release a new version of the library with these changes

I've also considered other solutions but I didn't want to have breaking changes in the Handler's code. We can try to do that in the next major release. What do you think?

I wonder if it could make sense to implement this at a handler level to keep the Update objects as pure data objects without behaviour and immutable.
However, that would require a bit more thinking and lot of changes, so I'm happy to go with this approach for the moment, which is a simple implementation with a simple API that works properly.
Thank you so much for the contribution! 🙂 @v1ctor
I'll release a new version of the library with these changes

I've also considered other solutions but I didn't want to have breaking changes in the Handler's code. We can try to do that in the next major release. What do you think?


Write access to Dracula Nova theme

@zenorocha - When permissions for the Dracula theme were changed last month, my read-only permissions also applied to the Nova theme that I contribute to. I had some PR rules in place so when I push to the repo, it's rejected.

Sorry about that @bdielman, it should be fixed now ;)

@zenorocha - Thanks!


Issue with "Legacy Authentication Protocols" section

I don't know if this is a documentation issue, or a product design issue, but it is a legitimate issue.  Let's look at this paragraph:

Legacy authentication protocols
The following options are considered legacy authentication protocols
Authenticated SMTP - Used by POP and IMAP client's to send email messages.
Autodiscover - Used by Outlook and EAS clients to find and connect to mailboxes in Exchange Online.
Exchange Online PowerShell - Used to connect to Exchange Online with remote PowerShell. If you block Basic authentication for Exchange Online PowerShell, you need to use the Exchange Online PowerShell Module to connect. For instructions, see Connect to Exchange Online PowerShell using multi-factor authentication.
Exchange Web Services (EWS) - A programming interface that's used by Outlook, Outlook for Mac, and third-party apps.
IMAP4 - Used by IMAP email clients.
MAPI over HTTP (MAPI/HTTP) - Used by Outlook 2010 and later.
Offline Address Book (OAB) - A copy of address list collections that are downloaded and used by Outlook.
Outlook Anywhere (RPC over HTTP) - Used by Outlook 2016 and earlier.
Outlook Service - Used by the Mail and Calendar app for Windows 10.
POP3 - Used by POP email clients.
Reporting Web Services - Used to retrieve report data in Exchange Online.
Other clients - Other protocols identified as utilizing legacy authentication.

To begin with, most of these line items are not Authentication Protocols at all.  Next, some of them are still used even after Modern Authentication has been performed.  Examples are Autodiscover, MAPI over HTTP, Offline Address Book.
The way this is written (or designed by the product team) it's not clear that if Outlook has used Modern Authentication, then the client app will show up as "Mobile Apps and Desktop Clients".
I'm suggesting that every single possible client app label that might show up in Azure AD Sign-Ins, be added here on this page and be clearly described as something that means legacy or modern authentication was used.  It shouldn't have to be such a mystery and guessing game.  The way it is now, things just don't make sense, and people have to make guesses.  I've been fortunate enough to be on the phone with MS Support for Azure AD where they can use a live conversation to explain.
It recently took a step backwards.  It used to be that "Other clients", or "Other clients:<SMTP|POP|IMAP|etc.>" would be the indicator of legacy authentication.  Now it's just an unclear list of things that are not clear one way or another if they are representing legacy or modern authentication.  In other words - this has been tremendously over-complicated and needs to be re-thought out.  It's driving me nuts because I see it from the customer view, and the partner view, and it's crappy across the board.   The way it is now, the deadline for blocking legacy authentication is coming too quickly because customers are being misled and steered in circles around this stuff.  Even just the terminology "legacy authentication" is adding confusion - there is only basic authentication and modern, nothing else, so no need to call it "legacy", that is just a third term added into the conversation with no value for having been added.
I will reiterate the point again - you shouldn't just call things "authentication protocols" when they are nothing of the like.  Kerberos, Windows Integrated Authentication, Basic, OAuth, etc. - are authentication protocols.  "Outlook Service", "Offline Address Book" - are not authentication protocols.
Final point, and this one is more of a product design critique - they could just add an extra property to the Azure AD Sign-Ins data that says "Basic Authentication" or "Modern Authentication", rather than coming up with all of this unnecessary fluff, to try and make (but fail) customers understand this stuff for themselves.

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

ID: ad5f26dc-2f8f-ef76-3d20-a0a42d2bbada
Version Independent ID: a0e971d1-05f2-2c21-06d4-60c087d45c0a
Content: Block legacy authentication - Azure Active Directory
Content Source: articles/active-directory/conditional-access/block-legacy-authentication.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

PS.  I see that this other page has been updated as of Feb 26 2020 - https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-sign-ins#filter-sign-in-activities
That page just so happens to have the fantasy table I've described above, where it lists possible Client App labels and has a checkmark to show if that Client App uses Modern Authentication.  Maybe that table can be referenced from this article?  It is a lot easier to understand the way it is shown in the table on the other page.

@JeremyTBradshaw
Thanks for your feedback! We will investigate and update as appropriate.

Hi @JeremyTBradshaw ,
Thank you for this detailed feedback. I agree that this could be clearer and I think it's a good idea to list that table with the checkmark listing whether the app uses modern authentication. I made a pull request to update the language and have passed your feedback along to the content author, @MicrosoftGuyJFlo , as well.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/108516
Closing this out but will update as more changes are added to the document.


Deploy Push Content API and fixes for Feedback API & XLIFF import

Changelog

[ #1271 ] Fix feedback API endpoint
[ #1099 ] Add push content API
[ #1277 ] Fix change detection for XLIFF import
[ #1276 ] Allow importing unchanged XLIFF files

The failing tests are just the existing problem with our dev pipeline, this should not interfere with the prod release, so I think it's safe to merge despite the failing tests.


Collection initializer with an expression.

An convenience init to create a collection of a given size initialized with the values of an expression :))
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 4.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          18 Errors

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L16: incorrect argument labels in call (have ‘expression:size:’, expected ‘repeating:count:’)
        let newArray = [Int](expression: array.removeLast(), size: array.count)

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L23: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: 0), [1, 2, 3, 4])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L24: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: 5), [4, 1, 2, 3])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L25: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: 4), [1, 2, 3, 4])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L26: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: 1), [4, 1, 2, 3])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L27: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: 3), [2, 3, 4, 1])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L28: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: -1), [2, 3, 4, 1])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L29: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: -3), [4, 1, 2, 3])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L30: value of type ‘[Int]’ has no member ‘rotated’
        XCTAssertEqual(array.rotated(by: -5), [2, 3, 4, 1])

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L36: value of type ‘[Int]’ has no member ‘rotate’
        array.rotate(by: 0)

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L38: value of type ‘[Int]’ has no member ‘rotate’
        array.rotate(by: 2)

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L40: value of type ‘[Int]’ has no member ‘rotate’
        array.rotate(by: -1)

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L46: cannot convert value of type ‘(Int) -> Bool’ to expected argument type ‘Int’
        array.removeFirst { $0 == 1 }

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L49: argument passed to call that takes no arguments
        XCTAssertNil(array.removeFirst { $0 == 10 })

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L51: cannot convert value of type ‘(Int) -> Bool’ to expected argument type ‘Int’
        let removedElement = array.removeFirst { $0 == 2 }

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L55: argument labels ‘(where:)’ do not match any available overloads
        XCTAssertThrowsError(try array.removeFirst(where: { _ in throw NSError() }))

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L60: value of type ‘[Int]’ has no member ‘removeRandomElement’
        XCTAssertNil(emptyArray.removeRandomElement())

:no_entry_sign:
Tests/SwiftStdlibTests/RangeReplaceableCollectionTests.swift#L64: value of type ‘[Int]’ has no member ‘removeRandomElement’
        let removedElement = array.removeRandomElement()!

          2 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 502 tests, with 0 failures (0 unexpected) in 3.071 (3.741) seconds

  Generated by :no_entry_sign: Danger


Need to remove Publishable key from app.module file

Is your feature request related to a problem? Please describe.
need to provide publishable key twise
Describe the solution you'd like
there is a option while importing library .forRoot() we need to use key at single plase
Describe alternatives you've considered
need to improve the import thing
Additional context
nothing

resolved need to test

resolved


DPE-75 Add CI workflows

Hi @pengale! Thanks for the feedback. As this PR is one of the first here focusing in this specific workflow (testing the deploy) it can be used (with some improvements) as a best practice. I closed this one in favor of two new PRs, which split the this PR to be better to review the changes.


Finalize used Translations

Finalizing the used translations in UI-Schema Core and Design System Material UI

[ ] document used translations in core
[x] refactor translations hard coded in MUI widgets (like in GenericList)
[ ] ~document translations used in design system widgets~, see dictionary sources
[ ] create default translations

[x] for EN
[x] for DE

Added new keyword patternError for custom error translation for keyword pattern (regex).
Deprecated t - the dictionary-to-translator factory, as confusing with keywords and properties in docs etc., still exists and reexports the newly makeTranslator function, will be removed in v0.3.0, then only makeTranslator exists.
Added package @ui-schema/dictionary for reusable language dictionaries for the translator.

In material-color are still some aria labels in english, those may introduce too much performance issues because of the current UIMetaProvider implementation, will be checked again after #80

New @ui-schema/dictionary (0.0.2) and makeTranslator released in 0.2.0-rc.2


Folders in timelines, characters, definitions

WARNING: This is google translate :) sorry.
If the project is large and there are a lot of dialogues / plot developments planned in it, then it is very difficult to sort all this. You can, of course, make the names "parameter_parameter_more". But it would be very convenient if it could be done in folders, as in godo itself.
The ability to add an empty dialog node to another scene is still sorely lacking. I don't know how technically difficult it is to accomplish, since this is a whole scene with a huge amount of code, but it would be convenient if I could make a lot of such scenes. And just copy the characters there and develop another huge branch of events.
And finally, you are great! I've looked at a lot of dialog addons, yours is the friendliest!)

The folders part is a duplicate of  #111. I'm not sure what you mean with adding an empty DialogNode.

I'm not sure what you mean with adding an empty DialogNode.

I will try to explain in more detail. I have a main scene (node2d) and I added a dialogic scene to it. I created a lot of storylines there, and I'm moving on to developing a new scene. And I want to add another dialogic there, empty as a new project, just in another scene. To separate the storylines.

This will not be a feature because Dialogic is global. Having separated folders will be possible but if you want to have different Dialogic instances for each scene you would need to make different projects for each scene. I'll be closing this one now because when folders are added this won't be really needed.


Change the "br" action to "branch" in the jira plugin to be more consistent with other actions

Context
The br action is the only action that is used as an abbreviation.
Suggestion Solution
This PR aims at:

Change the br action to branch to be aligned with other actions which don't use appreviations and also to be more consistent with the name of other actions.

Add the branch action in the list of possible actions in README.md which was not previously listed.

Hey there -- I really appreciate the contribution.
Cheers,
Robby


Make ObjectResult inherit from StatusCodeResult

The current Microsoft.AspNetCore.Mvc.ObjectResult does not inherit from Microsoft.AspNetCore.Mvc.StatusCodeResult. Adding this would offer a nice abstraction, as there would be a single class derived from ActionResult with a StatusCode property.

Unfortunately that would be a breaking change.

StatusCodeResult.StatusCode is a required int property: https://github.com/aspnet/Mvc/blob/008a562bf5b1ab89e4b83c60faaabd1d12ffcb82/src/Microsoft.AspNetCore.Mvc.Core/StatusCodeResult.cs#L30
ObjectResult.StatusCode is a nullable int? property: https://github.com/aspnet/Mvc/blob/008a562bf5b1ab89e4b83c60faaabd1d12ffcb82/src/Microsoft.AspNetCore.Mvc.Core/ObjectResult.cs#L33

(It can be done without a breaking change, but it would be very cumbersome with two properties named StatusCode.)

😢

This is dumb, why not just do it? https://github.com/aspnet/Announcements/issues?q=is%3Aissue+is%3Aopen+label%3A"Breaking+change"

Hi @Mardoxx , we're working on a "minor release", which is 2.1, which has a very high bar for making breaking changes. In general we make breaking changes only in major releases, which will be 3.0. Also, the benefit has to outweigh the cost. In this case the benefit is quite small, and the cost of a breaking change is considered very high.

@Eilon will this make 3.0? 😋


Awx support for projects

This pull request adds to the AWX client basic support for retrieving projects, and some examples that show how to use that support.

@zgalor @moolitayer @elad661 @nimrodshn we don't really need it, but it may be useful if we eventually move the AWX client to a different repository, and also as an example of how to add support for other kinds of objects.


Use time from health agent instead of scotty time.

Are you using {{/sys/systime/time}} as a proxy for metric collection time?

Yes. That was my plan. Each individual metric also has a time associated with it, but the time associated with each metric need not be the same.  For cloudhealth, I have to compute values to send. For example memoryUsedPercentage = (totalMem - freeMem) / totalMem * 100.0. If totalMem and freeMem have different timestamps, what timestamp do I use for memoryUsedPercentage? To put such questions to rest, I thought of just using /sys/systime/time which isn't a perfect solution but seems good enough. Thoughts?

So, using /sys/systime/time is in principle a better approximation than taking the time from Scotty. For metrics with different timestamps, you would roll them up to hour boundaries, so that should be fine.
The main problem I see with this change at this time is that the time on a machine can be incorrect and machines may have different ideas about what the time is. This happens when the machine loses sync with a time source (which can happen with silly firewall/security group rules). So, before we can use the time from the end nodes, we need to have the tricorder library give the poll time and then Scotty would compare that value with it's own view of poll time and compute a drift that would then be applied to any timestamps that come with the metrics.
We may be better off deferring this change until we "calibrate" the time that we get from the end nodes. I'm not sure that what we have now is posing a problem.

Ok, so it seems like the thing to do is to close this PR and continue taking the time from scotty for now.

Yes, I think so.


delete and recreate netem qos when update process

[ ] Make sure you have followed Kube-OVN Code Style.

What type of this PR

Bug fixes

1、when update netem qos, the value in qos record changed correctly, but the value with tc only works for the first config.
So delete and recreate netem qos when update value.
Which issue(s) this PR fixes:
Fixes #1745

已回合 release-1.10 和 release-1.9 分支


Fix issue 291

Description
Add link to documentation generated for redhatinsights/insights-operator-cli/commands/help.go
Fixes #291
Type of change

Documentation update

Testing steps
N/A

Codecov Report

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

@@           Coverage Diff           @@
##           master     #325   +/-   ##
=======================================
  Coverage   70.95%   70.95%
=======================================
  Files          12       12
  Lines         730      730
=======================================
  Hits          518      518
  Misses        208      208
  Partials        4        4

Impacted Files
Coverage Δ

commands/help.go
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 50c3c76...b963940. Read the comment docs.


The Emitter now emit body in parts

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#165

Merged. Thank you!


xorg-xrdb is a dependency

Previous behavior:
❯ betterlockscreen -u wallpapers/random.jpg
Got 6400x1440 /home/x/.cache/i3lock/6400x1440
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
/usr/bin/betterlockscreen: line 141: xrdb: command not found
Generating alternate images based on the image you specified,
please wait this might take few seconds...

Converting provided image to match your resolution...

Applying dim and blur effect to resized image
^Cconvert: Expected 8192 bytes; found 7119 bytes `/home/x/.cache/i3lock/current/dim.png' @ warning/png.c/MagickPNGWarningHandler/1748.
convert: Read Exception `/home/x/.cache/i3lock/current/dim.png' @ error/png.c/MagickPNGErrorHandler/1715.
convert: no images defined `/home/x/.cache/i3lock/current/dimblur.png' @ error/convert.c/ConvertImageCommand/3322.

Caching images for faster screen locking
convert: Expected 8192 bytes; found 7119 bytes `/home/x/.cache/i3lock/current/dim.png' @ warning/png.c/MagickPNGWarningHandler/1748.
convert: Read Exception `/home/x/.cache/i3lock/current/dim.png' @ error/png.c/MagickPNGErrorHandler/1715.
convert: no images defined `/home/x/.cache/i3lock/current/l_dim.png' @ error/convert.c/ConvertImageCommand/3322.

All required changes have been applied

The errors were fixed by installing xorg-xrdb with pacman on Arch Linux. Please update the dependency of the AUR package.

Which version from AUR-Packages are you using? Can't find a direct usage other than in a comment in master either than v3.2.0

I was using the non-git version indeed, now I cannot reproduce on the -git one.


Create build.yml

copy bin not do
.dll.  .sys   .exe copy into sdk/bin dir

https://github.com/HyperDbg/gui/blob/main/main_test.go#L27-L36
Last remove bin dir

不，此时还不能build，这个状态的时候，所有头文件是刷新的，应该先执行单元测试触发auto bindgen
---Original---
From: "Sina @.>
Date: Thu, Jul 4, 2024 20:48 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
image.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

😅
build流程如下
1 升级bin
2 升级sdk
3 执行单元测试bind
4 build
---Original---
From: "Sina @.>
Date: Thu, Jul 4, 2024 20:47 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
I'm not sure if I exactly understand what you mean. 🤨🤔
我不确定我是否完全理解你的意思。🤨🤔
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

okay
---Original---
From: "Sina @.>
Date: Thu, Jul 4, 2024 20:55 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
Okay, I'll try to work on it tomorrow. Since the 'Master' branch of HyperDbg is also not updated. I have to go since it's late night here. Will continue working on it tomorrow.
好的，我明天会试着做一下。因为 HyperDbg 的“Master”分支也没有更新。现在太晚了，我得走了。明天会继续做。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Good night
晚安

Good night
---Original---
From: "Sina @.>
Date: Thu, Jul 4, 2024 20:57 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
Good night
晚安
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

我将在处理完所有命令api相关事宜之后合并它，目前yml需要更改job顺序以及加入另外的任务来配合构建逻辑。

ok

看起来gui工程已经接近尾声了，很高兴这么快让gui达到初步可用状态，这个过程中我可能有些言语激烈，因为我性子急，语言冒犯之处还请你谅解。

No worries. Thank you for working on this. You did a great job for the HyperDbg and the reverse engineering community. ❤❤❤
不用担心。感谢您为此付出的努力。您为 HyperDbg 和逆向工程社区做出了巨大贡献。❤❤❤

在这完成之后，我将为ui从布局到sdk调用以及构建流程做一个可视化的草图，不过我不擅长画图，有可能还是用表格来描述这个过程。

Great. I'm currently working on designing a method for exporting JSON files for each command.
太棒了。我目前正在设计一种为每个命令导出 JSON 文件的方法。

ok，别忘记了我最后面提到的那个，为每个命令去一个完整的英文单词名称，并加入到json字段，我将解析它。
---Original---
From: "Sina @.>
Date: Fri, Jul 5, 2024 19:21 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
Great. I'm currently working on designing a method for exporting JSON files for each command.
太棒了。我目前正在设计一种为每个命令导出 JSON 文件的方法。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

之前的命令不用更改了，如果有提交撤回了，现在的要求变成:为每个命令取完整英文单词命名为附加字段。
---Original---
From: "Sina @.>
Date: Fri, Jul 5, 2024 19:21 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [HyperDbg/gui] Create build.yml (PR #137)
Great. I'm currently working on designing a method for exporting JSON files for each command.
太棒了。我目前正在设计一种为每个命令导出 JSON 文件的方法。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

remove this dir
https://github.com/HyperDbg/HyperDbg/tree/dev/hyperdbg%2Fmerge-dlls

This branch can be delete
https://github.com/HyperDbg/HyperDbg/tree/merge-test


voices/list returns sample rate and voice type

Endpoint voices/list now returns more information such as sample rate and voice type. Resolve #39163

@boltomli : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Array sorting by key

This PR adds an optional named argument key: to array's .sorted() method.
If not given, the behaviour is the same as the current one.
If given a function, then it is applied on the array's elements to get keys to then perform comparisons on (think Rust's Vec::sort_by_key or Python's sorted(..., key=...)).
E.g.,
(1, -2, 3).sorted()
// => (-2, 1, 3)
(1, -2, 3).sorted(key: x => x*x)
// => (1, -2, 3)

Mostly done, just missing tests (will add tomorrow).
I think I properly edited the Typst docs (how can I check?).
Also, code got a little bit messy, might clean up tomorrow (if possible).

Also something to consider is that at least the current implementation incurs a performance cost in the previous use case. We can overcome this by moving the match on the key outside of the closure for key_, but that may mean some more code duplication.

Since calling Typst closures is relatively expensive, I'd propose splitting up the two code paths and using sort_by_cached_key.

Ok, I didn't realize it was that expensive. I'll make the changes in a bit.

I split up the code paths and used sort_by_cached_key. Because I really wanted to use sort_by_cached_key instead of keeping my own cache of keys, there is a bit more boilerplate then I would like, and I needed to use a RefCell for the result variable.

Wait, are there no tests for methods on objects? I can't find them.

The tests for sorting are in tests/typ/compiler/array.typ.

Tests added.

I've reverted 3464621f6a448d8a01afafd7db47557709e2f39e (as discussed on Discord) and rebased onto main.


Remove RNA genes from gene neighbour list?

Is this list on the gene pages useful?  Would it be more useful to filter out the RNA genes?  I was thinking about this because I was considering implementing pombase/website#1944. Without the JBrowse image the list of genes is going to look even weirder.

I think it looks better:

Should I go ahead and make that change?

OK, we can see if anyone complains ;)

OK, I've made that change for tonight's update.

Done:


I don't know how to debug this error and get to the root of the issue

So when I start my nextjs project I get this error after updating the packages (tailwind, daisyui, nextjs)

yarn run v1.22.17
$ next dev -p 8000
ready - started server on <IP_ADDRESS>:8000, url: http://localhost:8000
info  - Loaded env from /home/alan/projects/trackonomy/delta_next_dash/.env.development

warn - The `purge`/`content` options have changed in Tailwind CSS v3.0.
warn - Update your configuration file to eliminate this warning.
warn - https://tailwindcss.com/docs/upgrade-guide#configure-content-sources

🌼 daisyUI components 2.13.6  https://github.com/saadeghi/daisyui

  🌼 daisyUI components 2.13.6  https://github.com/saadeghi/daisyui

    🌼 daisyUI components 2.13.6  https://github.com/saadeghi/daisyui
      wait  - compiling...
      error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[5].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[5].use[2]!./node_modules/next/dist/build/webpack/loaders/resolve-url-loader/index.js??ruleSet[1].rules[3].oneOf[5].use[3]!./node_modules/next/dist/compiled/sass-loader/cjs.js??ruleSet[1].rules[3].oneOf[5].use[4]!./styles/components/navbar.module.scss
      Error: Unable to parse color from string:
          at Array.forEach (<anonymous>)
          at Array.forEach (<anonymous>)
          at Array.forEach (<anonymous>)

Is it even a daisyui problem? Or  problem with css-loader, postcss-loader or resolve-url-loader? Because my navbar.module.css has not changed and is still the same:
.navbar {
    @apply shadow-lg;

    nav {
        margin-left: 8rem;
        @apply flex flex-row flex-grow pr-7 items-center;

        > a {
            @apply text-lg uppercase font-bold pt-7 pr-4 pb-7 pl-4 relative leading-8;

            &:after {
                content: '';
                @apply border-b-4 border-solid border-accent;
                @apply w-0;
                @apply absolute bottom-0 right-0 left-0;
                @apply transition-all;
            }

            &.active {
                &:after {
                    @apply w-full;
                }
            }

            &.last {
                @apply pl-0 pr-0 ml-auto flex flex-row items-center;
            }
        }
    }
}

There is one colour there - border-accent... I only posted it here because it prints daisyUI out thrice. But is it even this package's issue?

How is the border-accent colour defined - based on the error message, originating from webpacks loader & via css-loader - I believe this is actually caused by the colour, not its usage - although it is difficult to tell based on the final part of the error message - I'd look at where you're declaring that colour & possible see if you can change that colour for a different one for now to see if that is the issue :) - if hls or rgb I am aware of an issue where this error was being thrown if you used , to delimit colour values, although I'm fairly sure this was removed (I think the initial error was due to the authors wanting to replicate the latest version of the spec :) )

All the colours are defined in tailwind.config.js, which looks like this:
const daisyui = require('daisyui');

module.exports = {
    purge: ['./pages/**/*.{js,ts,jsx,tsx}', './components/**/*.{js,ts,jsx,tsx}'],
    important: true,
    variants: {
        extend: {
            backgroundColor: ['checked'],
            borderColor: ['checked'],
        },
    },
    plugins: [daisyui],
    theme: {
        colors: {
            white: "rgba(255, 255, 255, 1)",
            primary: {
                default: "rgba(0, 57, 107, 1)",
                light: "rgba(0, 57, 107, 0.6)",
                lighter: "rgba(0, 57, 107, 0.36)",
                lightest: "rgba(0, 57, 107, 0.12)",
            },
            accent: {
                default: "rgba(235, 113, 0, 1)",
                light: "rgba(235, 113, 0, 0.6)",
                lighter: "rgba(235, 113, 0, 0.36)",
                lightest: "rgba(235, 113, 0, 0.12)",
            },
            neutral: {
                default: "rgba(38, 50, 56, 1)",
                light: "rgba(38, 50, 56, 0.6)",
                lighter: "rgba(38, 50, 56, 0.36)",
                lightest: "rgba(38, 50, 56, 0.12)",
            },
            base: {
                default: "rgba(255, 255, 255, 1)",
                light: "rgba(255, 255, 255, 0.6)",
                lighter: "rgba(255, 255, 255, 0.36)",
                lightest: "rgba(255, 255, 255, 0.12)",
            },
            border: {
                default: "rgba(207, 216, 220, 1)",
                light: "rgba(207, 216, 220, 0.6)",
                lighter: "rgba(207, 216, 220, 0.36)",
                lightest: "rgba(207, 216, 220, 0.12)",
            },
            bg: {
                default: "rgba(236, 239, 241, 1)",
                light: "rgba(236, 239, 241, 0.6)",
                lighter: "rgba(236, 239, 241, 0.36)",
                lightest: "rgba(236, 239, 241, 0.12)",
            },
            info: {
                default: "rgba(0, 117, 219, 1)",
                light: "rgba(0, 117, 219, 0.6)",
                lighter: "rgba(0, 117, 219, 0.36)",
                lightest: "rgba(0, 117, 219, 0.12)",
            },
            success: {
                default: "rgba(5, 148, 79, 1)",
                light: "rgba(5, 148, 79, 0.6)",
                lighter: "rgba(5, 148, 79, 0.36)",
                lightest: "rgba(5, 148, 79, 0.12)",
            },
            warning: {
                default: "rgba(199, 133, 0, 1)",
                light: "rgba(199, 133, 0, 0.6)",
                lighter: "rgba(199, 133, 0, 0.36)",
                lightest: "rgba(199, 133, 0, 0.12)",
            },
            error: {
                default: "rgba(218, 44, 23, 1)",
                light: "rgba(218, 44, 23, 0.6)",
                lighter: "rgba(218, 44, 23, 0.36)",
                lightest: "rgba(218, 44, 23, 0.12)",
            },
            "decorative-1": {
                default: "rgba(235, 112, 146, 1)",
                light: "rgba(235, 112, 146, 0.6)",
                lighter: "rgba(235, 112, 146, 0.36)",
                lightest: "rgba(235, 112, 146, 0.12)",
            },
            "decorative-2": {
                default: "rgba(3, 180, 167, 1)",
                light: "rgba(3, 180, 167, 0.6)",
                lighter: "rgba(3, 180, 167, 0.36)",
                lightest: "rgba(3, 180, 167, 0.12)",
            },
            "decorative-3": {
                default: "rgba(209, 125, 254, 1)",
                light: "rgba(209, 125, 254, 0.6)",
                lighter: "rgba(209, 125, 254, 0.36)",
                lightest: "rgba(209, 125, 254, 0.12)",
            },
            "dark-primary": {
                default: "rgba(191, 238, 255, 0.96)",
                light: "rgba(191, 238, 255, 0.6)",
                lighter: "rgba(191, 238, 255, 0.36)",
                lightest: "rgba(191, 238, 255, 0.2)",
            },
            "dark-accent": {
                default: "rgba(255, 171, 92, 0.96)",
                light: "rgba(255, 171, 92, 0.6)",
                lighter: "rgba(255, 171, 92, 0.36)",
                lightest: "rgba(255, 171, 92, 0.20)",
            },
            "dark-neutral": {
                default: "rgba(255, 255, 255, 0.96)",
                light: "rgba(255, 255, 255, 0.6)",
                lighter: "rgba(255, 255, 255, 0.36)",
                lightest: "rgba(255, 255, 255, 0.20)",
            },
            "dark-base": {
                default: "rgba(38, 50, 56, 1)",
                light: "rgba(38, 50, 56, 0.6)",
                lighter: "rgba(38, 50, 56, 0.36)",
                lightest: "rgba(38, 50, 56, 0.2)",
            },
            "dark-border": {
                default: "rgba(236, 239, 241, 0.96)",
                light: "rgba(236, 239, 241, 0.6)",
                lighter: "rgba(236, 239, 241, 0.36)",
                lightest: "rgba(236, 239, 241, 0.20)",
            },
            "dark-bg": {
                default: "rgba(55, 71, 79, 0.96)",
                light: "rgba(55, 71, 79, 0.6)",
                lighter: "rgba(55, 71, 79, 0.36)",
                lightest: "rgba(55, 71, 79, 0.20)",
            },
            "dark-info": {
                default: "rgba(120, 199, 252, 0.96)",
                light: "rgba(120, 199, 252, 0.6)",
                lighter: "rgba(120, 199, 252, 0.36)",
                lightest: "rgba(120, 199, 252, 0.20)",
            },
            "dark-success": {
                default: "rgba(144, 223, 157, 0.96)",
                light: "rgba(144, 223, 157, 0.6)",
                lighter: "rgba(144, 223, 157, 0.36)",
                lightest: "rgba(144, 223, 157, 0.20)",
            },
            "dark-warning": {
                default: "rgba(244, 206, 123, 0.96)",
                light: "rgba(244, 206, 123, 0.6)",
                lighter: "rgba(244, 206, 123, 0.36)",
                lightest: "rgba(244, 206, 123, 0.20)",
            },
            "dark-error": {
                default: "rgba(221, 129, 126, 0.96)",
                light: "rgba(221, 129, 126, 0.6)",
                lighter: "rgba(221, 129, 126, 0.36)",
                lightest: "rgba(221, 129, 126, 0.20)",
            },
            "dark-decorative-1": {
                default: "rgba(235, 112, 146, 0.96)",
                light: "rgba(235, 112, 146, 0.6)",
                lighter: "rgba(235, 112, 146, 0.36)",
                lightest: "rgba(235, 112, 146, 0.12)",
            },
            "dark-decorative-2": {
                default: "rgba(158, 169, 241, 0.96)",
                light: "rgba(158, 169, 241, 0.6)",
                lighter: "rgba(158, 169, 241, 0.36)",
                lightest: "rgba(158, 169, 241, 0.20)",
            },
            "dark-decorative-3": {
                default: "rgba(151, 223, 216, 0.96)",
                light: "rgba(151, 223, 216, 0.6)",
                lighter: "rgba(151, 223, 216, 0.36)",
                lightest: "rgba(151, 223, 216, 0.20)",
            },
        },
        fontFamily: {
            header: ["Gotham"],
            body: ["Inter"],
        },
    },
    daisyui: {
        themes: [
            {
                light: {
                    "primary": "rgba(0, 57, 107, 1)",
                    "secondary": "",
                    "accent": "rgba(235, 113, 0, 1)",
                    "neutral": "rgba(38, 50, 56, 1)",
                    "base-100": "rgba(255, 255, 255, 1)",
                    "info": "rgba(0, 117, 219, 1)",
                    "success": "rgba(5, 148, 79, 1)",
                    "warning": "rgba(199, 133, 0, 1)",
                    "error": "rgba(218, 44, 23, 1)",
                },
                dark: {
                    "primary": "rgba(191, 238, 255, 0.96)",
                    "secondary": "",
                    "accent": "rgba(255, 171, 92, 0.96)",
                    "neutral": "rgba(255, 255, 255, 0.96)",
                    "base-100": "rgba(38, 50, 56, 1)",
                    "info": "rgba(120, 199, 252, 0.96)",
                    "success": "rgba(144, 223, 157, 0.96)",
                    "warning": "rgba(244, 206, 123, 0.96)",
                    "error": "rgba(221, 129, 126, 0.96)",
                },
            },
        ],
    },
};

But I think I just figured out what the problem was. There were two colours defined in daisyui settings, which were defined as empty strings. And I guess those were the ones causing the problem ( see secondary colour in the above config file.
@saadeghi I'm not sure if this is a bug, though. As "Please don't configure empty strings as colours in settings" pretty much fixes it.
But the official issue description is:
If colour is configured as empty string the compilation process fails.

That makes sense... an empty string is not a valid color value of course.
And all the required colors in this table should be defined (including secondary)
I guess we can close this issue now


Write Text Problem Since Update to <IP_ADDRESS>121802

Describe the bug
Windows Utils Write Text (several issues) . There is so much wrong with Write Text since update it is difficult to describe.
To Reproduce
Steps to reproduce the behavior:

Create a new folder
Double-click on a button to create a new one
Add a button title (E.G Call it '1')
Click on '+' then 'Action'
Click on 'Windows Utils'
Click on 'Write text'
If 'Write text' has previously been added to a button it will be shown in the 'Write text' box. If not then add a new Windows Utils Write Text. Add text as '1' (without ')
Click 'Save' and 'OK'
Double-click on another button in the same folder and call it '2'
Click on '+' then 'Action'
Click on 'Windows Utils'
Click on 'Write text'
The text box will appear with '1' in it
Change text to '2'
Click 'Save' and 'OK'
Double-click on button 1.
You will see the Windows Utils Write text has changed to '2'

Expected behavior
Each new button should be clear then saved and then the variables should be nulled. It worked in the previous version, 2.6.4.... Only since the plugins reconfig has it stopped working correctly
Screenshots
If applicable, add screenshots to help explain your problem.

This bug is already fixed in version 2.6.7-dev which can be downloaded.


Add HTTPS plugin

Add opentelemetry-plugin-https to allow the user to automatically collect trace data. The package should be used by both server and client. This should be based on BasePlugin interface: https://github.com/open-telemetry/opentelemetry-js/blob/master/packages/opentelemetry-core/src/trace/instrumentation/BasePlugin.ts#L29
We should:

Implementing the patch (by specializing the HttpPlugin class)
Reuse http tests (not copy them) (wrap http tests with functions and pass http or https module. In this way, we will keep sync tests between http and https)
Add an example under examples/https folder (see http example)
Update README like http plugin.

Ref Opencensus: https://github.com/census-instrumentation/opencensus-node/tree/master/packages/opencensus-instrumentation-https
For node 8 only, https forward to http module. This is not the case for other version >= 9.

Feel free to assign to yourself, if you have the bandwidth to work on this. 👍


[miniLLM] The evaluation might be wrong when using dp_size > 1

At the evaluation phase of llama-7b/gpt2-xlarge whose MP_size=1, I try to use 8 gpus to accelerate the evaluation phase. The code is scripts/gpt2/eval/run_eval.sh.
I simplify this code to only evaluate on one task.   The gpu_num=8 which by default is 1.
base_path=${1-"/home/MiniLLM"}
port=2040

ckpt_base_path=/xx/LMOps/minillm/results/gpt2/train/

for data in alpaca_zh
do
    # Evaluate SFT
    for seed in 10
    do
        ckpt="sft/gpt2-base"
        ckpt=$ckpt_base_path"/"$ckpt

        gpu_num=8 # this is wrong
        gpu_num=1 # this is normal
        bash ${base_path}/scripts/gpt2/eval/eval_main_${data}.sh ${base_path} ${port} ${gpu_num} ${ckpt} --seed $seed  --eval-batch-size 8
    done

If I use gpu_num=1, the evaluation is fine. The final rouge value is normal. But for gpu_num=8, the rouge is much lower than ecpected. And the former rouge is consistent with that of the training-time evaluation rouge.
I check results/gpt2/eval_main/alpaca_zh-512/xxx/answers.jsonl for more details.
And I found that there are only 63 lines of responses for the 8 gpu-evaluation setting. But for the 1gpu settting,  the line number is 500, which is the exact number of valid set. I think the dp_size >1 might be the cause of this problem.
For llama-13b whose MP_size=4, if I use gpu_num=4, the validation is normal, but wrong if gpu_num=8.
My evaluation code of alpaca_zh is very similar to that of dolly.   I guess this problem might exist for other dataset like dolly too.

Fixed in https://github.com/microsoft/LMOps/commit/81cf69c60c3c69d7693d42c7e985e80e8d864dc6

Fixed in 81cf69c

Thanks. The evaluation is much faster with dp_size > 1 now.
A tiny problem is that for the same model (llama-7b) and same dataset (alpaca-zh), when I use eval_batch_size=16, the eval rouge is 19.010. When I use eval_batch_size=8, the eval rouge is 18.1586. Total number of val set is 500.
It would be better if this rouge value is more consistent with different eval_batch_size.

To get a more consistent rouge score, you can increase the size of val set or run the evaluation under different random seeds and calculate an average score.


Add a LICENSE

@frankcarey Before I start using this for my work related projects, I need to know under what license you are releasing this.

Done, added the MIT license https://github.com/devinci-code/ahoy/commit/97c85ec02bbb02cef2f31c4418f9b3868ef48f0b


Fix PBMAC1 MAC verification in FIPS mode

The check for fetchability PKCS12KDF doesn't make sense when we have a different MAC mechanism

Checklist

[ ] documentation is added or updated
[x] tests are added or updated

@tomato42 JFYI

@paulidale - please reconfirm

@mattcaswell is it OK to you from the nits perspective?

The failure seems to be a timeout

This pull request is ready to merge

Merged. Thanks for the review.


Jpamodelgen fixes for panache

Please @gavinking can you review this?

Support ORM/HR+Panache types such as anything that extends PanacheEntityBase or PanacheRepositoryBase to make sure to use their session getter type, but never generate a DAO because Quarkus will call the generated static methods. Also support annotations on native methods.
Support Uni<Mutiny.Session> session types
Support session getters with a default implementation, in which case never store the session in a field but always call the getter. This is mostly because reactive sessions can't be stored in a CDI context and need to be obtained for each call.
Fix update/delete method return types that have to return Uni<Integer|Void> for HR
When ORM/HR+Panache is detected, for types that are not Panache entities or repositories, default to the Quarkus way of obtaining a session unless there's a session getter declared. The default way being @Inject EntityManager for ORM and SessionOperations.getSession() for HR. Note that this doesn't respect non-default PU for ORM, but we can improve later, if we have an entity defined (for Panache, we can override the PU per entity), and meanwhile users can always define a session getter to override. HR/Panache doesn't support non-default PU so this is not an issue.

Also, do you want docs for the changes? Tests?

OK, on it.

I think I've treated all the remarks. But for tests, I now realise that the detection allows for either Quarkus ORM or HR, but not both (because that is not supported and both flavours are mutually exclusive), so I'm not sure (especially with Gradle) how to declare a dependency on those libs.
Also, it appears that the tests such as DaoTest only checks that the metamodel is generated, not that it has this or that method or structure, am I missing something?

so I'm not sure (especially with Gradle) how to declare a dependency on those libs.

ugh.

Also, it appears that the tests such as DaoTest only checks that the metamodel is generated, not that it has this or that method or structure, am I missing something?

For now that's all it does indeed. We could probably improve that by adding some code which calls the generated code. But the fact that it is accepted by the compiler is already a fairly demanding test, though not perfect of course.

Also, it appears that the tests such as DaoTest only checks that the metamodel is generated, not that it has this or that method or structure, am I missing something?

For now that's all it does indeed. We could probably improve that by adding some code which calls the generated code. But the fact that it is accepted by the compiler is already a fairly demanding test, though not perfect of course.

What's supposed to be the result of this test:
public interface Dao {
    @HQL("select upper('Hibernate')")
    TypedQuery<String> getName();
}

Because it appears to result in:
@StaticMetamodel(Dao.class)
@Generated("org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor")
public abstract class Dao_ {
}

And… I mean… it does compile, sure… 😂 but is it really supposed to be empty? 🤔

so I'm not sure (especially with Gradle) how to declare a dependency on those libs.

I've figured it out thanks to Steve.

Nice!

And… I mean… it does compile, sure… 😂 but is it really supposed to be empty? 🤔

Um, no, that does not look right. 😬

I've figured it out thanks to Steve

Famous Last Words 🤦
Apparently checkerframework is something that's required, but it doesn't automatically applies to my new source sets and I'm getting a compilation error that it's looking for checker-qual.jar.

@FroMage what's the status of this?

Blocked on the Gradle build of the tests that require quarkus, due to checkerframework :(
I can push what I have, but it doesn't build.

You just had to update that project, @gavinking, you couldn't just leave it be for the 6 months it took me to do this PR 😂
Well, I've rebased, I'll sort out the checkstyle issues and add tests for the non-panache fixes as well as the panache stuff.

Check style doesn't enforce it.

Yeah, so, where does this info come from?

From looking at the rest of the codebase.

Yeah, I have zero excuse :(

OK, rebased on master, reformatted, includes tests for every feature/commit, tests now run as part of regular tests, and checkstyle passes.
So, IMO the only remaining thing might be to document some of those things?

I can rebase again, but we should really merge this because I'm not going to keep doing that every day ;)


the link to unblock a user is dead

https://docs.microsoft.com/en-us/office-365-security/securitycompliance/removing-user-from-restricted-users-portal-after-spam
should be
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/removing-user-from-restricted-users-portal-after-spam

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

ID: 68b20762-e3ee-6aa6-7460-5bc7214fd00e
Version Independent ID: 641814b7-9c30-2119-e5f9-7983118e102f
Content: Responding to a Compromised Email Account in Office 365
Content Source: microsoft-365/compliance/responding-to-a-compromised-email-account.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@Mike-Crowley  - Thank you for submitting feedback.
I will get this issue over to the Microsoft 365 writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@Mike-Crowley - From our understanding, the issue has been resolved. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!


fix(use baseURL in tsconfig.json to fix vercel frontend deployment)

I thought it would be a little confusing for anyone deploying on vercel since you build errors when deploying. This PR just adds a quick fix to the tsconfig giving it a baseurl to work from.
error.log
[16:55:25.838] Running build in Washington, D.C., USA (East) – iad1
[16:55:25.978] Cloning github.com/fredski02/next-dashboard (Branch: main, Commit: 4d18d64)
[16:55:26.356] Previous build cache not available
[16:55:26.664] Cloning completed: 685.757ms
[16:55:26.897] Running "vercel build"
[16:55:27.393] Vercel CLI 33.2.0
[16:55:28.128] Warning: Detected "engines": { "node": ">=18.17.0" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version
[16:55:28.143] Installing dependencies...
[16:55:42.360]
[16:55:42.361] added 573 packages in 14s
[16:55:42.361]
[16:55:42.362] 172 packages are looking for funding
[16:55:42.362]   run `npm fund` for details
[16:55:42.385] Detected Next.js version: 14.0.2
[16:55:42.389] Detected `package-lock.json` generated by npm 7+
[16:55:42.389] Running "npm run build"
[16:55:42.860]
[16:55:42.860] > build
[16:55:42.860] > next build
[16:55:42.860]
[16:55:43.476] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[16:55:43.476] This information is used to shape Next.js' roadmap and prioritize features.
[16:55:43.477] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[16:55:43.477] https://nextjs.org/telemetry
[16:55:43.477]
[16:55:43.576]    ▲ Next.js 14.0.2
[16:55:43.577]
[16:55:43.577]    Creating an optimized production build ...
[16:55:46.546] Failed to compile.
[16:55:46.546]
[16:55:46.547] ./app/layout.tsx
[16:55:46.547] Module not found: Can't resolve './ui/fonts'
[16:55:46.547]
[16:55:46.547] https://nextjs.org/docs/messages/module-not-found
[16:55:46.547]
[16:55:46.547] ./app/page.tsx
[16:55:46.547] Module not found: Can't resolve<EMAIL_ADDRESS>[16:55:46.547]
[16:55:46.548] https://nextjs.org/docs/messages/module-not-found
[16:55:46.548]
[16:55:46.548] ./app/page.tsx
[16:55:46.548] Module not found: Can't resolve './ui/fonts'
[16:55:46.548]
[16:55:46.548] https://nextjs.org/docs/messages/module-not-found
[16:55:46.548]
[16:55:46.548] ./app/ui/acme-logo.tsx
[16:55:46.548] Module not found: Can't resolve '@/app/ui/fonts'
[16:55:46.548]
[16:55:46.548] https://nextjs.org/docs/messages/module-not-found
[16:55:46.549]
[16:55:46.549] Import trace for requested module:
[16:55:46.549] ./app/page.tsx
[16:55:46.549]
[16:55:46.549]
[16:55:46.549] > Build failed because of webpack errors
[16:55:46.572] Error: Command "npm run build" exited with 1
[16:55:46.837]

Duplicate, but thank you!


Use for Teams

Thanks for this great feature! I managed to use the filtered URL in a web page, and even copy to a Teams tab and it works. The trick is to use the html way of entering the address with %20 for the space and %27 for the simple quote
[Enter feedback here]

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

ID: 70b360f3-21a7-adc2-896a-b1dfd5d9e384
Version Independent ID: 15e8c09f-46ad-68f9-75e6-c3d5c2c214e5
Content: Filter a report using query string parameters in the URL - Power BI
Content Source: powerbi-docs/collaborate-share/service-url-filters.md
Service: powerbi
Sub-service: pbi-collaborate-share
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @Didierma92 . This issue has been assigned to the doc author for review.

Hi, @Didierma92 -- good point! Belatedly, I'm updating the article and including your feedback. Changes should be live tomorrow afternoon Jan 6 Pacific time.
Thanks!


Tooltip is not a function

I love this calendar, and I've slowly been piecing it together (the lack of documentation does make that rather hard). However, I have run into an error. When I run the webpage, this error pops up:
$('*[data-toggle="tooltip"]').tooltip is not a function. (In '$('*[data-toggle="tooltip"]').tooltip({container: 'body'})', '$('*[data-toggle="tooltip"]').tooltip' is undefined
The error originates in the calendar.js file, and is located at this line:
$('*[data-toggle="tooltip"]').tooltip({container: 'body'}); // Line 938

I'm not sure what is causing this error, and how to fix it. Any ideas?

Got it! For those wondering, it appears I was using a different version of the bootstrap.js than I needed to be using. The version I was using uses the attr() function to provide tooltips - not the tooltip() function. Since I wanted to continue using the current version of bootstrap, I changed the code in calendar.js to:
$('*[data-toggle="tooltip"]').attr({container: 'body'}); // Line 938

@DazzlingDevelopment you're a king among men!! Thanks for posting this fix :)


C - code with scanf not running!

Script is not running some little programs that are using the function scanf. I don't know why! Other programs that not use this function are running ok.
This is a limitation of the package?
I'm using mac os x
(thanks and sorry for the bad english)

This is a limitation, same as in #385. There's a patch in the works though!
Your English is fine! :smile:

thanks man!


Add Tooltips everywhere. $.tooltip() is not a meteor function.

Fixed by changing meteor package importing order in: /client/.meteor/packages
It must be loaded in the following order:
jQuery -> tether -> bootstrap


Added manual proxy configuration

Sometime it might be beneficial to use manual proxy configuration

Thanks for the PR, looks like some changes have created a conflict with the code in master. I'm currently working a new release I hope to get out today or tomorrow.
I'll be pulling in your changes to a new branch so I can make a few tweaks. then merge it into master.
Thanks again!


migrate the way to get the price of eth wallet

What does this implement/fix? Explain your changes.

前置 coin manager 新增 tbtc
新增 cache_it
替换 eth wallet 获取币价方式

Does this close any currently open issues?
If it fixes a bug or resolves a feature request, be sure to link to that issue.
…
Pull request type

Put an x in the boxes that apply

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Where has this been tested?
…
Any other comments?
后续我再改 btc wallet 的

嗯，我后来看到你上面写的，正在重新过一遍


fix: Use production build config for cypress tests and fix webpack

SUMMARY
Recently we had an issue that only reproed with production build assets. I suspect this would've been caught with cypress, but we build assets in development mode for cypress, so it wasn't caught. This PR should run cypress on prod assets instead of dev ones.
This pr also further resolves the webpack bugs by setting usedExports to globa.
TESTING INSTRUCTIONS
CI
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

to: @eschutho @michael-s-molina @rusackas

🏷 v1.4


Saving model with negative id.

Laravel Version: 5.8 upgrade to 9.0
PHP Version: 7.3 upgrade to 8.1
Database Driver & Version: MySql 8.0.27

Description:
Not sure if this would be classified as a bug but I encountered problems with saving models with negative ids in my PHPUnit tests while upgrading an older Laravel application from 5.8 to 9.0.
I have a model that has one-to-many submodels:
class Model extends \Illuminate\Database\Eloquent\Model {

   public function submodels() {
      return $this->hasMany(Submodel:class);
   }

}

In the seeding for my Unit tests I populate database with:
$model = new Model();
$model->id = -1;
//other attributes
$model->save();

$submodel = new Submodel();
//set $submodel's attributes
$model->submodels()->save($submodel);

These tests run great in old environment (Laravel 5.8 and php:7.3-fpm) but in new (Laravel 9.0 and php:8.1-fpm) they failed.
With testing I have narowed issue to the PHP's PDO::lastInsertId() function in php 8.1 versus 7.3. The problem is that Model after saving has value of $model->id set to<PHONE_NUMBER>3709551615 when in the database it has value -1.
My tests were failing as foreign key constraint for Submodel table failed as there was no Model with id<PHONE_NUMBER>3709551615, only one with id set to -1.
Now, I personally think that this is a bug in PHP and have opened bug report issue in their repo: php/php-src#8746 but got an explanation that this is by design of MySQL API which returns uint64_t value for last insert id and as -1 is negative this results in number<PHONE_NUMBER>3709551615. As can bee seen in the issue I opened in PHP source repository they will not change this, as MySQL actually returns unsigned integer. I must say I can see why PDO should be designed like this and I understand their decision.
I think there should be a "fix" in Laravel - model after saving ($model->save();) should afterall represent state in the database and have in my case id set to -1.
I am just a Laravel user and I am not greatly familiar with the innerworkings of laravel/framework but I do not see a clear way of fixing this. I think Laravel cannot know if id was intentionally changed (with for example a before insert trigger) and PDO::lastInsertId() is returning the correct new id, or if returned id is "wrong" and data in the database actually has id set to the value in the attributes.

It looks like your model does not have an auto incrementing id. If that is the case, set your model's $incrementing property to false to tell Eloquent to not set it using PDO::lastInsertId().
class MyModel extends Model {
    public $incrementing = false;
}

By default Eloquent assumes the primary key is an integer auto incrementing key, as stated in the docs:
https://laravel.com/docs/9.x/eloquent#primary-keys

I am just curious, why would you use a negative ID? (you are not using it to get one model but using it to store a model)

@matiaslauriti I have negative ids due to some legacy things we have to support. As we need to support negative ids we have some database seeding for our PHPUnit test and that is how I discovered this issue after migration form Laravel 5.8.
@rodrigopedra I agree that in my case - as I am setting id manually in PHPUnit test I should have set $incrementing = false; which would solve issue.


PublicClientApplication.addEventCallback has incorrect callback type

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.0.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
2.0.0
Public or Confidential Client?
Public
Description
The type for for the callback parameter in PublicClientApplication.addEventCallback used to be typed as EventCallbackFunction now it is typed as Function
Error Message
No response
Msal Logs
No response
MSAL Configuration
Not a configuration issue

Relevant Code Snippets
msalInstance.addEventCallback((event: EventMessage) => {
  if (event.eventType === EventType.LOGIN_SUCCESS && event.payload) {
    console.log('login success');

    const account = (event.payload as AuthenticationResult).account;
    msalInstance.setActiveAccount(account);
  }
});

Reproduction Steps

Update to v3.0.0
Try to addEventCallback on the PublicClientApplication
Typescript no longer has parameter information for the EventMessage

Expected Behavior
Typescript should have the correct type for the callback parameters
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
@azure/msal-browser 2.38.0
Source
External (Customer)

@bagoette Can you update to the latest 1.x version of MSAL React and 2.x version of MSAL Browser and let us know if you still see this issue?

Do you mean to downgrade both packages? I already went back down to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(which is what I was on previously) the issue is not there.

@bagoette Apologies, I misread the versions. We have recently had an error in our release process, please wait until the latest patch version for MSAL Browser v3 to be released before upgrading again.


ARROW-17211: [Java] Fix java-jar nightly on gh & self-hosted runners

@github-actions crossbow submit java-jars


Implement close()/wait_closed() interface for Pool

Coverage decreased (-0.01%) to 97.155% when pulling 23f4013588c348eb2b9b640dbc741248e33e7d36 on pool_close into 04de8c079ca0dc244ea34c792e2fe34c1e96aa81 on master.


Reverting changes2

Issue Link :link:
It reverts a change from December that we hoped you fix the crash but it didn't.
We have a Firebase crash that we are hoping this will fix.
Goals :soccer:
To fix a crash when lowerBounds is not <= upperBounds
Implementation Details :construction:
Added code to make sure lowerBounds <= upperBounds

@leolobato Once this is merged to master I will be building and testing it in our app.


error while updating 'source' of a view on android null uri

Describe the bug
The title says it's problem.
I check all issues relating this, but I think the situation little different from them sine they uploaded the same error with 'null null'...
I tried to change my fastimageviewmanager.java on this link
https://github.com/DylanVann/react-native-fast-image/commit/f21522c4092c9ccf5a8c83e56f2c5c4ae3ddc1c8
but not helped(No ImageViewWithUrl symbol)
Thanks in advance.
To Reproduce
Steps to reproduce the behavior if possible, or a link to a reproduction repo:

npm install
react-native link
add some FastImage tags

Expected behavior
Images should appear nicely
Screenshots

Dependency versions

React Native version: 0.59
React version: 16.5
React Native Fast Image version: 0.0.5(fast image expo)

Note: if these are not the latest versions of each I recommend updating as extra effort will not be taken to be backwards compatible, and updating might resolving your issue.

Hi @jihyeonjeong11! Can please provide a code sample of what you tried to achieve?
This error means that you are providing a wrong value for source prop, maybe a typo in the imported image or something like that

Thanks for your feedback.
I finally figured out this happens when Flatlist renders FastImage tag without a value on android environment, not ios.
Also, nesting buttons inside FastImage tag also causes this error on android.
like this.
<FastImage>
  <TouchableWithoutFeedback />
</FastImage>

this throws an error on android.


TypeScript callback signature and Rust implementation mismatch

Describe the Bug
I am encountering an issue with wasm-bindgen where the TypeScript callback signature does not seem to match the expected Rust function signature. When defining a TypeScript type for a callback function, the generated Rust code instead of passing this and an argument passes only an argument in place of this to the TypeScript side, and as a consequence TypeScript callback receives undefined instead of an actual argument.
Steps to Reproduce

Declare a type script callback in rust code and a simple use case for the callback:

#[wasm_bindgen]
extern "C" {
    #[wasm_bindgen(typescript_type = "(arg: string) => number")]
    #[derive(Debug)]
    pub type TsCallback;

    #[wasm_bindgen(method, js_name = "call")]
    pub fn call(this: &TsCallback, arg: &str) -> i32;
}

#[wasm_bindgen]
pub fn rust_function(ts_callback: &TsCallback) -> i32 {
    let arg = format!("Hello from Rust! Here is what I've got {ts_callback:?}");
    ts_callback.call(&arg)
}

Compile it with wasm-pack build --target nodejs.
Use it on the TypeScript side:

const result = rust_function(function (this: any, arg: string): number {
    console.log(["Here is what I've passed: ", [this, arg]]);
    return arg.length;
});

Add the rust lib as a dependency.
Run the typescript code with: yarn ts-node src/index.ts

Link to the repo
https://github.com/dima-starosud/wasm-bindgen-callback-issue
Expected Behavior
After running the TypeScript I should see:
[
  "Here is what I've passed: ",
  [
    "TsCallback { ... }",
    "Hello from Rust! Here is what I've got TsCallback { obj: JsValue(Function) }"
  ]
]

Actual Behavior
But the code prints:
[
  "Here is what I've passed: ",
  [
    "Hello from Rust! Here is what I've got TsCallback { obj: JsValue(Function) }",
    undefined
  ]
]

Note, that this is actually an argument, not the callback itself.
Additional Context

wasm-pack 0.12.1
yarn 1.22.21
wasm-bindgen = { version = "0.2.89", features = ["serde-serialize"] }

I am looking for guidance on whether this is the expected behavior or if there is a more conventional way to handle this situation. Any help or suggestions would be greatly appreciated.
Thank you for your assistance!

OK, looks like I've misused the feature, the way below works well.
// Rust
#[wasm_bindgen(typescript_custom_section)]
const X_PEND_CONTENT: &'static str = r#"
export interface TsCallback {
    call(arg: string): number;
}
"#;

#[wasm_bindgen]
extern "C" {
    #[wasm_bindgen(typescript_type = "TsCallback")]
    #[derive(Debug)]
    pub type TsCallback;

    #[wasm_bindgen(method, js_name = "call")]
    pub fn call(this: &TsCallback, arg: &str) -> i32;
}

// TypeScript
class A implements TsCallback {
    call(arg: string): number {
        console.log(["Here is what I've passed: ", [this, arg]]);
        return arg.length;
    }
}

const result = rust_function(new A());
console.log([result]);

// Result:
[
  "Here is what I've passed: ",
  [
    A {},
    "Hello from Rust! Here is what I've got TsCallback { obj: JsValue(Object({})) }"
  ]
]
[ 78 ]


Propagate watch state changes when default profiles change

If default profiles are added/removed, we should cancel or create watch requests as necessary. This probably doesn't happen today (validation necessary)

Start with the test provider sample https://github.com/microsoft/vscode-extension-samples/tree/main/test-provider-sample
Add a command (or just a timeout) that adds a second "run" profile later https://github.com/microsoft/vscode-selfhost-test-provider/blob/c318bd91f3644f8a23053c5f9105a8c6c4a1e35e/src/extension.ts#L146-L153. Make sure the isDefault parameter is true.
Start watching tests by clicking the 👁 icon, then add your second profile.
Verify the runHandler gets called for the second profile as it's added https://github.com/microsoft/vscode-selfhost-test-provider/blob/c318bd91f3644f8a23053c5f9105a8c6c4a1e35e/src/extension.ts#L104


A proper feature matrix for this great product

It's important to advertise the correct feature set, and advise that it is not appropriate for other uses.

It’s true we don’t support bear attacks!


Detect re-frame-trace views via 'devtools outer'

This is more reliable than looking for the namespace, as reagent does not attempt to keep namespace information when compiled with Closure, whereas "devtools outer" is hard-coded as the :display-name for the panel's container and survives compilation/optimization.

Thanks!


Create unit tests for core front end functionality

Create unit tests for core front end functionality. The tests will be used to implemented a CI/CD pipeline.

Relevant resource: https://firebase.google.com/docs/rules/unit-tests

Current status:

Created some toy unit tests for Svelte components and JS/TS functions.
Currently, there does not seem to be any component that can be easily tested with unit tests, and it seems to be a waste of time to go back at the moment and create unit tests for already defined components.

Resources:
Svelte Vitest TDD: https://www.freecodecamp.org/news/how-to-do-test-driven-development-with-svelte-and-vitest/
Setting up Firebase CI: https://www.youtube.com/watch?v=VgQwlMtxbAw

Current status:
Following this guide: https://www.youtube.com/watch?v=VDulvfBpzZE
Wrote a github action to perfrom (not yet created) firebase security rules tests
Having some ESLint issues on functions/test.ts, could be beneficial to revert to JS as they do above.

Current status:
Firebase CI action created, no real tests implemented yet.
Working based on this guide but it seems to be outdated: https://www.youtube.com/watch?v=VDulvfBpzZE&t=502s
Guide uses @firebase/testing, up-to-date package is @firebase/rules-unit-testing docs here. Need to either find a different guide or just follow documentation.


dlpredictor cannot process huge log files

If you have a different process for dlpredictor to process huge log files, please add it to
/Processes/dlpredictor/experiments/

@radibnia77 I was having issues in processing large data of logs. made few changes to post processing scripts and updated code files are committed and pull request is created.

I am reviewing/running your code.
I noticed that line 56 and line 140 contradict each other in main_spark_data_process, you might need to look into that.

Line 140 is not there in final code we are using. It was added for some testing and i forgot to remove before sharing with you.
Also, i have removed few lines related to integrations. if the code doesn't work, you may have to change according to your integration mechanism with ES and model serving system.

I ran your version of the post-process (prediction) code.
This result is equivalent to the original code. I don't see any issue here.
+--------------------------------+---------+
|si                              |sum(impr)|
+--------------------------------+---------+
|d4d7362e879511e5bdec00163e291137|45321    |
|17dd6d8098bf11e5bdec00163e291137|54459    |
|s4z85pd1h8                      |589565   |
|j1430itab9wj3b                  |726600   |
|a8syykhszz                      |797981   |
|k4werqx13k                      |3509653  |
|x2fpfbm8rt                      |4300115  |
|d9jucwkpr3                      |4801039  |
|5cd1c663263511e6af7500163e291137|5392623  |
|z041bf6g4s                      |5514397  |
|71bcd2720e5011e79bc8fa163e05184e|9680103  |
|d971z9825e                      |21667294 |
|l2d4ec6csv                      |27452169 |
|w9fmyd5r0i                      |31180311 |
|w3wx3nv9ow5i97                  |32777583 |
|f1iprgyl13                      |37138436 |
|68bcd2720e5011e79bc8fa163e05184e|46111387 |
|a290af82884e11e5bdec00163e291137|64487036 |
|e351de37263311e6af7500163e291137|71461386 |
|l03493p0r3                      |97185399 |
|7b0d7b55ab0c11e68b7900163e3e481d|97269075 |
|b6le0s4qo8                      |113705360|
|66bcd2720e5011e79bc8fa163e05184e|139935126|
|x0ej5xhk60kjwq                  |159131471|
|a47eavw7ex                      |666862239|
+--------------------------------+---------+


Security Vulnerability in minimist Dependency

Hello!
There's currently a high severity security issue with the minmist package: https://github.com/advisories/GHSA-xvch-5gv4-984h
Does not seem like an actively-maintained project, and there's no ETA on when a fix would be available. There's an ongoing fork though (minimist-lite) that can be used instead of the original package. Was wondering if it'd be possible to switch out the dpenendency on minimist to minimist-lite.
Ongoing issue: https://github.com/substack/minimist/issues/164

https://github.com/elasticsearch-dump/elasticsearch-dump/commit/42610e1a6ce905e2a7a6075943da855472701955


Post user testing results and notes in wiki

Marking a todo: need to post the notes from user tests into the wiki

Notes from old user tests here: https://gist.github.com/smit1678/0909dd0fea2927d419db911cca164a40.


Add minimum password validation and add browsableapi renderer

Thanks for the PR, looks good.
One minor detail:
        try:
            validate_password(password)
        except ValidationError as e:
            return Response({'status': e})

It should be possible to convert this Django Core Validation Error into a Django Rest Validation Error for the password field. This would allow proper validation error mapping for both, the browable API as well as frontend applications.
I will try that out myself and let you know if it works, else we can just merge this as it is :)

Thanks again for the input.
I will be closing this in favour of PR #24.
FYI, a good way of validating the password is within the PasswordTokenSerializer:
class PasswordTokenSerializer(serializers.Serializer):
    password = serializers.CharField(label=_("Password"), style={'input_type': 'password'})
    token = serializers.CharField()

    def validate_password(self, password):
        try:
            validate_password(password)
        except ValidationError as e:
            raise serializers.ValidationError(e.messages)

        return password

Also thanks for the hint with the renderers. I've removed the renderers from the API View alltogether, as we should not restrict the renderer options within our API Views at all.
Now we have a beautiful browsable API that also maps validation errors, e.g.:


How to run in daemon mode? (systemd?)

For systemd you will just keep the process running in foreground.
systemd works best with processes not going into background and logging to stdout.


[Help]: Border noise removal

Hello Alexey.
Border noise appears as highly coherent area  This may affect trend removal due to coherence weighting?

Do you usually have a method for removing this automatically or do you cut the region out?

It also appears as highly stable in psfunction:

Hi, yes, it can affect Gaussian filtering around the border plus unwrapping and trend removal globally. In this case of strong border effects we need to remove the border pixels.

Hi, yes, it can affect Gaussian filtering around the border plus unwrapping and trend removal globally. In this case of strong border effects we need to remove the border pixels.

Do you cut it manually by guessing the limit or do you use a tool?

It can be done as manually as using topological operations from 'utils' module.


Register OVA in OpenNebula

Author Name: OpenNebula Systems Support Team (OpenNebula Systems Support Team)
Original Redmine Issue: 5107, https://dev.opennebula.org/issues/5107
Original Date: 2017-04-11

For both KVM and vcenter based infrastructures

Original Redmine Comment
Author Name: Adrian Menendez (Adrian Menendez)
Original Date: 2017-04-12T06:49:37Z

Automatically deploy a vm from an OVA would be a very interesting functionality. Incredibly useful if you could deploy the vm calling the API with the OVA path or something similar.

Original Redmine Comment
Author Name: EOLE Team (EOLE Team)
Original Date: 2017-05-12T14:16:10Z

+1
Another interesting thing is to export VMs/Services as OVA.
Regards.

Thanks to keep this in backlog.


[AI-AMM] Fork Uniswap v3 into Palomadex repo on Paloma Github for AI-AMM

CHORE:

Fork Uniswap v3 into Paloma Github repo. This will be a Paloma repo
Make the repo public.
Deploy the Uniswap v3 fork to Abitrum to test and verify deployment
Deploy the Uniswap v3 fork to Base to test and verify deployment
Rename from Uniswap to AIAMM

Closing as shipped.


Azure: Add support for user defined environment variables

Add support for user defined environment variables subnet id, NSG id and image id to increase flexibility.

Closed by https://github.com/confidential-containers/cloud-api-adaptor/pull/583


Quitting float after splitting closes split too

First of all.. Love the idea and the plugin. Will try to make it my daily driver. It's going to ease the development flow a lot, especially when working with libraries
Here's my issue.

Use :Detour to open a float on a method.
Use <C-w>s to open it in a split.
Navigate to the detour split, close detour float, closes the previously opened split too

Expected behaviour: Split should remain open when the Detour float is closed.
With tabs, it is working as expected.

Hi, thanks for trying my plugin and thanks for opening the issue. Now, if I understand correctly, when you are closing the detour float, it also closes the split window that you created from the float?
When I've done this in the past, the split would remain open. Here is the gif demonstrating this from the README.md:

Maybe for some reason, when you are closing the detour float, it's also deleting the buffer contained in the float (ie, it's calling :bdelete)? If that's happening it would explain why the split disappears too. I may be off the mark here, but it's my best guess at the moment. I just tried the behavior again on my neovim and it works as expected (ie, the split stays open when the detour float closes).
Does this issue happen consistently for you? Do you think there are any autocmds or plugins that might be causing the issue? Any other details you may have would be appreciated. Maybe you could try to recreate the issue from a minimal neovim setup with no configs except one to install the plugin?
This is a pretty serious issue if the problem is with the plugin so I'd appreciate any more info that you could share.

Howard you closing the popup? If I use <C-w>c it closes the split also

If I use <C-w>c it closes the split also

@burgessa23 That is also strange. For me, using <C-w>c on the popup only closes the popup. The split window remains. Do you have any mappings or plugins that might be causing this behavior?

@carbon-steel  I restarted my session and now it seems to be only closing the popup, sorry for the false alarm

I'm also running into this problem. Here's a short video of what I'm doing. Forgive the hideous colors - I've just installed the plugin and haven't tried adjusting my scheme yet.
https://github.com/carbon-steel/detour.nvim/assets/1951900/b26ae99a-5592-4445-be3b-b6b21b0dee2f
I'm using <C-w>c to close, but the same happens with :q
❯ nvim --version
NVIM v0.10.0-dev-847+gc0ac53e0d-Homebrew
Build type: Release
LuaJIT 2.1.0-beta3
Run "nvim -V1 -v" for more info

I think I see what's going on here. Even if there is a popup in front of a window, it is still possible to have your cursor on the window behind the popup (you can see this by cycling through your windows with <C-w>w). If you close the window behind the popup, the popup will close too (this closing behavior is the intentional design of this plugin). Unfortunately, it can be difficult to distinguish whether the cursor is on the popup or the window behind it.
One way to mitigate this issue is to use a colorscheme that distinguishes between unfocused windows and the focused window.
Or even better, it's easy to just adjust whatever colorscheme you like to use to do this. I like to turn the NormalNC's bg color to be a bit lighter so that unfocused windows look faded. (Though... popups currently seem to have a bug where they don't always show the "focused" colors for some reason. I have an issue for that bug #4)
If anyone thinks that the explanation I presented does not match what is going on in their computer, please comment here. Otherwise, after some time, I'll close this issue.

Turns out that is what's happening. Is there any way to control pop-up / split ordering so we would jump back to the popup after creating that first split? I think it'd be a much more intuitive experience if possible.

@joeblubaugh I think you're right. I created an issue for this feature: #8

Yep. The comment describes what is happening. I am able to "switch" to the pop up after opening a split and close it independently. #8 is a better structured issue.

@carbon-steel what's the best way to select the popup when it's in a split? h and l move me left and right but I can't navigate to the popup. Alternatively, is there a way to focus on the popup immediately after creating the split? The only time I want to create a split is to create the split and then close the popup. Would be great if there's a way to do that through a keybind.

@kandodev responded here


sign verification failed

after last update HA - sign verification failed
at the same time, device (sonoff micro) can be turned on (if it was turned off), but the device status returns back - to "off" after a few seconds, while the device turns on normally.

+, same issue

Closed:

this fix: https://github.com/AlexxIT/SonoffLAN/pull/881/files
(https://github.com/AlexxIT/SonoffLAN/pull/881#issuecomment-1176067573)

this fix:  https://github.com/AlexxIT/SonoffLAN/issues/887#issuecomment-1175877543

@numminorih-git does thta mean a fix will come with an update? I honestly don't feel well about editing those files myself.
I get This account is already configured when I try to reconfigure

Good morning,
Yesterday I had this same problem.
Update following method 2: https://github.com/AlexxIT/SonoffLAN/issues/887#issuecomment-1175877543      and the authorization problem is fixed. But the King Art - King Q4 Cover have stopped working, they remain as if they had no connection. Could you guide me how to solve it?
Thank you very much

Good morning, Yesterday I had this same problem. Update following method 2: #887 (comment) and the authorization problem is fixed. But the King Art - King Q4 Cover have stopped working, they remain as if they had no connection. Could you guide me how to solve it?
Thank you very much

Same here, I have two King Art - King Q4 Cover, which are not working, but the SANTTON_3 Switch is still working, even without the fix, so don't bother I guess ;)

I think it's because the switches I have, camera, etc... are in LAN mode and the KingARTs only support CLOUD, so it's not connecting to the cloud, it doesn't show the error message, but it doesn't connect to the cloud and it's just working locally.

+, same issue

#879


Import custom script and Notify users of new events

The idea is to then be able to use SelectUtxos as well, beside notifications, passing the optional script as filter?


[Translation][French] Translate welcome article

Hi,
I translated the welcome article page in french language.

fixed with suggestions

I will create a new PR to merge to french branch instead of main ;)


Apply MQE on Infra-Windows layer UI-templates

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

Here are some screenshots of the modified and e2e test:

@smartboy37597 Could you provide screenshots to verify your results? We only could do limited review due to most of us don't have Windows.

@smartboy37597 Could you provide screenshots to verify your results? We only could do limited review due to most of us don't have Windows.

I have submitted my screenshot, probably due to network delays not refreshing to see it.

@mikechengwei If you have time, welcome to do a review as well. You contributed this feature in the first time.

@mikechengwei Do you have a chance to verify today? I hope to merge this soon.