Error hover semantic information should be rendered separate of error message

From @octref in #62159

This is a regression on the diagnostics display.
1.28:

Insiders:

In both case, the diagnostics returned are:
const diagnostics = {
  code: "unknownProperties",
  source: "css.lint.unknownProperties",
  message: "Unknown property: 'foo1'"
}

If we have access to semantic information we should render it much better. The message should come first. Then the source on a separate line, with a Source: label preceding it and in non-monospace font (since source should be a user-readable string like CSS Lint). Then, the code with the same style, but with monospace, since code is often a library/OS error code. Something like:

Unknown property: 'foo1'
Source: CSS Lint
Code: unknownProperties

cc @sandy081  @ramya-rao-a @misolori

Another problem: changing source back to css is not nice in problems view. Previously I get:

Now I get:

Good things I miss from previous one:

source and code displayed together in the left, the most prominent & easily-scannable place
I'm able to see the code even in half screen, whereas if the message is long, I lose the code at the end

@jrieken
I see your point, but there are also cases when, say, a user is enforcing some new linter rules throughout a codebase. He would want to see which errors/warnings are caused by exactly these rules. He might also add pragmas to disable certain rules for some lines, when the rulename is useful.
From an extension author point of view, he doesn't care about passing in semantically correct info. He only knows the messages displayed on hover and problems are ${code} ${message} ${source} ${range}, and he tries to make best use of that format. We see that with HTML all the time, don't we...

which errors/warnings are caused by exactly these rules.

That sounds a little artificial but if that is the case, then I would probably search for that specific error code using the filter box on the upper right. (actually I wouldn't use the UI et all but I'd use the command line)

Inline widget renders the source and code similar to Problems view.
Hover renders the source and code as suggested in description

@jrieken @joaomoreno @misolori Feedback is welcome.

I think having source and code on separate lines gives them way more attention than they should have.  And to my eyes it also looks ugly. What again is wrong about the inline rendering and why is it only wrong in the hover?

Since it is a suggestion from @joaomoreno I would request him to reply for above comment.

Pushed changes in inline view - made source and code less prominent just like in problems view.

Error Code than Code would be more explicit and easy to understand in the inline hover. The [2551] (417, 98) in the problems view is mystic and hard to understand. Just my 2 cents.

Made Hover consistent with Inline and Problems view

This is the best can be done before introducing more UI changes. I would not invest more as the current approach is OKish and do not see complains from users.

Since some of us does not like how the current metadata is shown in the hover I am proposing following options. Each option shows hover for single line and multi line errors.

Option 1 (Current)

Option 2 (As suggested in description)

Option 3 (Do not show metadata)

@Microsoft/vscode Please give the option you like

I vote for Option 3. Imho a user is not interested in the source and of course not the code.
I would always render source and code in the problems panel such that users who are interested in this can go to the view that provides more details. Similar analogy is debug hover, gives you minimalistic information, if you want more please open the debug viewlet.
If we decide to go with option 2 I suggest to right align it so it is less noticable and less space between it and the actual error.

If we decide to go with option 2 I suggest to right align it so it is less noticable and less space between it and the actual error.

Yeah, if we have

Minimal width of the diagnostics
Right align the source/code
Give source/code a smaller font size (maybe with a fading grey color too)

This would look great to me.
Option 3 would mean "I should not follow the semantics of the Diagnostic interface", because I need the source and code presented to users. Look at issue like https://github.com/vuejs/vetur/issues/261.
I also hope code can be a link for use cases like https://github.com/vuejs/vetur/issues/849. Otherwise the only way I can do it is to append code to message as a MD link.

I think first we have to decide whether the metadata should be shown at all, or whether it should be configurable to be hidden, etc. Then, if it's shown, how it should be displayed.
I think it should be shown because if I have multiple extensions contributing diagnostics, I want to know where a message is coming from. The error code is also useful, e.g. if you want to know which rule in a tslint.json is associated with an error message. I prefer option 1, I think 2 doesn't need to be so verbose.

Another thought is a hybrid of option 1 & 3 where we have some way for a user to expand the additional information but it's hidden by default (similar to the suggest widget info box).

@roblourens @octref Source and code information are hidden only in hover. If you want you can find them in Problems view. Is not that enough and helpful?

Source and code information are hidden only in hover.

That's what I currently resort to:

If you want you can find them in Problems view. Is not that enough and helpful?

I need to open panel, find the matching message (hard if I have many errors) and read the error rule id. It's not my workflow.
Plus, this makes it much harder for people to write inline pragmas such as /* eslint-disable [ruleId] */.

This is what I meant:

Code/Source are displayed but do not command too much attention
code, often the ruleId, should be linkable. That's https://github.com/Microsoft/vscode/issues/11847 but not https://github.com/Microsoft/vscode/issues/54272.

I think source and code on two lines takes up too much vertical space. Could there be a dedicated single line for "metadata"?
Source: ts | Code: 2430
(but possibly done with CSS background/border instead of just a textual pipe character)

I didn't realize that @sandy081... slightly better but personally would still prefer it in the hover for the same reasons @octref stated.

This is how it looks when I align it to right. Not sure right alignment looks good for all. May be it is better to go with left alignment?

I would decrease the font and make it more opaque, @misolori might have more ideas
I am still not convinced that we need to show them. Why don't we discuss this at the next UX meeting?

Another idea is to have everything in single line and left aligned. Some realtime examples:

I would prefer either show or not show them but not configurable (through setting or action) as it is not worth.
I personally think above aproach is the best out of all where metadata is not prominent and rendered nicely.

Another idea is to have everything in single line

I feel so ignored. 😄

How about always using top right corner?
Sick paint skills:

There have been too many iterations done on this and thanks to all for the suggestions. Since it is highly individual opinionated, I would collect more feedback on the current approach before changing and going in circles.

Yes, the comment 6 days ago https://github.com/Microsoft/vscode/issues/62370#issuecomment-441257120 got most upvotes and everyone seems to like it. That looked great:

but suddenly you changed it to the current form.

I don't know what's the reason we can't have one extra line for the source/code. It's easy for user to locate and read, and it's always aligned. Vertical space is not limited for diagnostics hovers, are they?
And the new design generates inconsistencies. User now will be confused for "what's inside a parenthesis" and "what's inside a bracket". This goes against our effort to "make errors/hovers consistent". /cc @joaomoreno @misolori for input.

In the UX call yesterday we discussed both of those options and even though we all liked both versions, we all agreed that we liked the cleaner look of last one (the one that's now on insiders).

@octref To be fair, the option to not show any additional information is actually the one with the most likes and it is what Visual Studio does too.
https://github.com/Microsoft/vscode/issues/62370#issuecomment-440323548

@roblourens https://github.com/Microsoft/vscode/issues/62370#issuecomment-440459469

I think it should be shown because if I have multiple extensions contributing diagnostics, I want to know where a message is coming from. The error code is also useful, e.g. if you want to know which rule in a tslint.json is associated with an error message. I prefer option 1.

Note that the hovers in vscode are clickable. If said information is not shown, what about clicking the hover and having it shift focus to the full diagnostic in the problems view? Personally, I think it would make sense as most people eventually get an idea of where a diagnostic is coming from an no longer need that data.

Fixes for his have caused regression for https://github.com/rust-lang/rls-vscode. We used backtick-enclosed strings for types and since everything is escaped now to render a custom hover window, the error messages are illegible now, for example:
current output
note: expected type std::option::Option<std::string::String> found type std::option::Option<&std::string::String>
previous output
note: expected type std::option::Option<std::string::String> found type std::option::Option<&std::string::String>
See https://github.com/rust-lang/rls-vscode/issues/479 for more details.

Suffering the same issue as @Xanewok in https://github.com/nwolverson/vscode-ide-purescript/issues/115 - diagnostics are rendering fine in problems and tooltip but replaced by displayed HTML entities in the hover


O8S (P1) naming cleanup

Cleaned up some of the intro kefka namings. They're (intentionally, probably) confusing, but for reference, this is a quick glossary I compiled while doing this and normal mode:

Gravitational Wave is the west half arena hit, and Intemperate Will is the east half.
Ave Maria is the question mark gaze looking at the statue, Indolent Will is the gaze looking away.
Inexorable Will are the ordinary targeted ground aoes.
Indomitable Will is the four stack markers during first graven.
These aren't in the timeline, but Indulgent Will is the confuse application, Idyllic Will is the sleep.

I also split it out into Graven sections, combined Blizzard+Thunder to make the actual event happening more clear from the timeline, and added the untargetable line for the enrage.

Looks great! Thanks for the cleanup!


[FR] Support SQLite3

Hi,
Is tere any way to support SQLite3?
Thanks.
Jerry

Thank you.
I was hesitant because it would be difficult to implement if there were a large number of databases to support, but if there is a request, I would like to work for SQLite3 after the current modifications are completed. (since v0.12)

Thank you for your willingness to add this feature!
BTW, i've recorded a YouTube video for your works:

Nyagos: https://youtu.be/WsfIrBWwAh0
SQL-Bless and CSVI: https://youtu.be/_cxBQKpfUds

Although they are all introduced in Chinese, they are accompanied by CC subtitles in English, Japanese, etc. Maybe you'll be interested.

Thank you. I saw then yesterday and they are very encouraging!
I would create links to them from README.md of the repositories .

SQLite3 is supported now on Release v0.12.0 · hymkor/sqlbless !

👍


[FABC-891] Create missing index on postgres db

Postgres db users.id does not have index causing register delays.

Bug fix

Description
Our group have tested on AWS aurora r5.4xlarge and got only 100 registers per second on a c5.12xlarge ec2 instance.
However, even though the CPU utilization for both database and instance was below 30% we were getting more than 10-sec delays for register and modify for 100 requests per second.
So we thought there was a bottleneck somewhere. We found that the select * from users where id = ? was taking more than 700ms. There we asked ourselves, is there no index in users table?
There it was. In hyperledger/fabric-ca repository, lib/server/db/postgres/postgres.go, no primary key or index was found in the users table compared to the MySQL version which explicitly had a primary key in id.
Additional details
Related issues

You'll also need to regenerate the mock, change to lib/server/db/postgres and run go generate ./...

LGTM, @mastersingh24 do you see an issue with adding a primary key to the Postgres DB, or was it just an accidental omission at design time?

LGTM; performing a local test before merging.

Looks good. Only thing left is to rebase on top of current master and then I'm happy to merge.
Thanks for the contribution!

@jamesHanKey - it appears that this PR is almost ready to merge. Can you rebase on top of current master?


Use path.join for constructing path to package.json

Using Node.js v5.7 I'm receiving the following error when trying to run the app:
Using storage env:  development
module.js:341
    throw err;
    ^

Error: Cannot find module '/private/tmp/watchmen/webserver/routes../../../package.json'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Object.module.exports.getRoutes (/private/tmp/watchmen/webserver/routes/api-ping-plugins-route.js:8:17)
    at module.exports (/private/tmp/watchmen/webserver/app.js:42:35)
    at Object.<anonymous> (/private/tmp/watchmen/run-web-server.js:23:11)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)

It appears as if joining the path using + has a different outcome, I'd say it's better in any case to join it using the path-module.

Hi Marcus, thanks for the PR!
It seems like the require internal implementation changed in node 5 and it is not accepting anymore the weird relative path that it was provided as a result  of doing string concatenation between __dirnameand a relative path (that was pretty ugly actually)
Using path.join is indeed a much better option but I think path.resolve would be better suited for this scenario. What do you think?

I changed here: https://github.com/iloire/watchmen/commit/45108473494712c6a0de2a6f605a70b75f38b622
thanks again!

:+1: path.resolve indeed sounds like what we want to use for this.


How to set the default username and password?

Could you help me to solve the login problem?
I find that there are no users in the database.

If you run it in docker-compose, the user name and password is<EMAIL_ADDRESS>/ passw0rd

@zheng1 Thanks!


Update assign-roles-azure-service-principals.md

If customers have multiple EA Billing Accounts and they want to at the EnrollmentReader or EA Purchaser role at EA billing account scope, they need to grant the SPN the specific role for each EA billing accounts separately. The SPN role assignment at EA Billing Account will not inherit to all the EA billing accounts which customer is not aware of and its not mentioned in this document.

The document does not say anything about currently granting SPN EnrollmentReader roles is all under the hood and its not visible/possible on the UX to check or grant any EnrollmentReader to the SPN.

Regarding the SPN enterprise object ID, the document does not have any reference to help customer find the right SPN object ID. When an Application Registration is created in Azure AD, it will have its own object ID which customer should not be using. Instead when the Application Registrations is created, it will create it's own Enterprise App (SPN). The customer should navigate to the App Registration's Enterprise App and use that Object ID while granting the EA roles to the SPN.

Customers are getting confused on they need to generate a unique GUID for each billingRoleAssignmentName. Hence, it would be good to add a note about the same at the beginning.

@bandersmsft
Can you review the proposed changes? The new note on line 19 needs to be formatted as a Markdown callout instead of plain text.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@darushah This PR appears to be a duplicate of https://github.com/MicrosoftDocs/azure-docs/pull/103838, where I've left feedback about required changes. Please make the updates in that PR and close this PR. Thanks.

@bandersmsft I am unable to edit the changes requested in this https://github.com/MicrosoftDocs/azure-docs/pull/103838 as the repo was deleted.
Hence, can we please treat this request as primary one?
Whatever changed to requested in the previous request has been updated in this commit edda9b50915f023773e07e2b05ebbc08f9a48605.
@bandersmsft  Please review

@darushah Please close this PR. I opened a PR to make the update for you with https://github.com/MicrosoftDocs/azure-docs-pr/pull/224271.

@bandersmsft sure closing this one.


Add reverse world

Proposed changes
Added Reverse World Feature: Entities added using the world:spawn() function will now receive negative numbers as their IDs.
Additional comments
During the development and usage of the ECS (Entity Component System) on the client-side, I encountered challenges in distinguishing whether an entity was created locally on the client or synchronized from the server. This ambiguity can lead to confusion and potential bugs in the system's behavior, especially in environments where client-server synchronization is critical.
To address this issue, I propose introducing a feature that utilizes opposite ID allocation strategies for the client and server worlds. By assigning negative IDs to entities spawned on the client and reserving positive IDs for server-spawned entities (or vice versa), we can easily identify the origin of any given entity based on its ID. This change simplifies the logic needed to differentiate between client-created and server-synchronized entities, improving the robustness and maintainability of the system.

This is sort of an orthogonal approach to stable entity IDs cross worlds. Which is also a very bad idea. We already have solved network synchronization by keeping a table that maps server entities to client entities. And from a technical standpoint this would make require us to use hash lookups for entity locations which will make our storages non-contiguous.
When you want to propose changes, please make an issue first in the future so that we can discuss it before you put in any work.

Whatever your preference for representing entities is, I don't think that Matter's core library should consider replication. I do think that, in the future, Matter should have a first party, fully fleshed out replication library (separate from Matter itself), and I have several things in mind for that, but that's a topic for another day.


GET_ENVIRON_PTR()

  Description: get_environ_ptr() (sched/sched_getenvironptr.c) is not implemented.
               The representation of the environment strings selected for
               NuttX is not compatible with the operation.  Some significant
               re-design would be required to implement this function and that
               effort is thought to be not worth the result.
  Status:      Open.  No change is planned.
  Priority:    Low -- There is no plan to implement this.

https://github.com/apache/incubator-nuttx/issues/3391
Description: The definition of environ in stdlib.h is bogus and will not
               work as it should.  This is because the underlying
               representation of the environment is not an array of pointers.
  Status:      Open
  Priority:    Medium

Fix by https://github.com/apache/incubator-nuttx/pull/6083


Fix: Modal closes immediately after launch

Details

AttachmentPicker: Since this is a multi index component - to keep props interface uniform it was extracted to separate file
Converted native AttachmentPicker to a class based component, preserving existing props interface
Removed logic that causes a side effect that closes the attachment options modal

Discussed here: https://github.com/Expensify/Expensify.cash/issues/1913#issuecomment-807851083

Added error handling to let the user know when image picking fails for reasons other than permissions instead of leaving him guessing
The wrapped calls to RNImage picker with promises to keep a uniform and easy to follow interface

Fixed Issues
Fixes #1913
Tests

For web, mWeb and Desktop
Found a bug related to Safari, please use another browser to test (Chrome works): #2019

Open a chat
Press the (+) plus button to open the input menu
Select "Add Attachment"
The browser's file picker should open and you can select a file
When you select a file you should see File Preview modal
Pressing upload should upload the file and you should see the attachment/thumb inside the chat
Upon the File Preview closes (previous step) focus should be returned to the compose input field

iOS/Android

Open a chat
Press the (+) plus button to open the input menu
Select "Add Attachment"
A second modal should open and show options for: camera, gallery, document

Selecting "Take Photo"

default flow: You shoot a photo, select "Use Photo" and continue to the next step (File Preview)
other cases:

pressing "Cancel" closes any modals and returns you to the "Chat". If the input was focused prior starting this flow it will be focused again
not granting permission should display a helpful Alert message
other errors should display a general error message to let the user know something did go right. You can verify this by selecting "Take Photo" on a iOS simulator - you should see a message that taking photos on a simulator is not supported

Selecting "Choose from Gallery"

default flow: You select a photo from the gallery and continue to the next step (File Preview)
other cases:

pressing "Cancel" closes any modals and returns you to the "Chat". If the input was focused prior starting this flow it will be focused again
there's error handling that should alert the user in case of an error but I don't know a way to trigger it. I tested it by manually forcing code execution through that flow

Selecting "Choose Document"

default flow: You select a document and continue to the next step (File Preview)
other cases: Same as in "Choose from Gallery"

File Preview

At this point you should see a preview of whatever was selected using the previous options
Pressing "Upload" should upload the file and you should see the attachment/thumb inside the chat
Pressing (x) close on the top right corner should close the preview and not upload anything
Upon the File Preview closes focus should be returned to the compose input field

Regarding field input focusing

the field is no longer focused when any modal closes
the field would be auto focused after a modal closes if previous focus (before the modal opened) was on the field
the field would autofocus at the end of the full attachment flow no matter where focus previously was

QA Steps
Same as above
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

I have read the CLA Document and I hereby sign the CLA

recheck

going to also add @Julesssss here as a reviewer since he's got context to for issue and proposed solution

the field is no longer focused when any modal closes

This is a regression for Web & Desktop. We need to regain focus when the attachment picker closes (not for mobile though)
Also, it looks like we're not closing the AttachmentPicker menu when on item is selected, can we do this? IMO it's odd mobile UX to see the prior modal when cancelling from the gallery (for example) -- I would expect the modal to close as the gallery/camera/picker is launched

It tested well on Web and mobile, but mobile web (iOS) didn't work for me. I see the AttachmentModal, but tapping Add Attachment does nothing.
I also would expect the options here to match mobile?

This is a regression for Web & Desktop. We need to regain focus when the attachment picker closes (not for mobile though)

I've also brought this up here: https://github.com/Expensify/Expensify.cash/issues/2129#issuecomment-809554367
Autofocus should be handled differently on mobile vs web/desktop but I don't think this can be address by the current PR

Also, it looks like we're not closing the AttachmentPicker menu when on item is selected, can we do this? IMO it's odd mobile UX to see the prior modal when cancelling from the gallery (for example) -- I would expect the modal to close as the gallery/camera/picker is launched

I wasn't sure about this, I can update it to close. My logic was that if I selected gallery by mistake I can press "Cancel" and return to select something else like documents

I also would expect the options here to match mobile?

I don't think the options would match on mWeb, it would use the web component with the hidden input - that would bring whatever file picker the browser would display to you.
Something like this:

It's not even possible to test it right now as this issue is also affecting mobile Chrome: #2109:

Updated

reverted changes regarding "This is a regression for Web & Desktop."
this also closes the 2nd modal when "Cancel" is picked inside the gallery/camera

Autofocus should be handled differently on mobile vs web/desktop but I don't think this can be address by the current PR.

Yeah, no problem. I just mentioned it in case it simplified things, clearly not :D

Updated
Included a fix for Android camera permissions - it appears on android the response.error is different...

Still needs a designer touch as the message is used as title.
Maybe something like:
Alert.alert(
  'Expensify.cash does not have access to your camera', // Title
  'To enable access, tap Settings and turn on Camera.', // Message
  [...]
)

Updated

improved error messages

Alert.alert(
  'Expensify.cash does not have access to your camera', // Title
  'Please enable the permission and try again.', // Message
  [...]
)

I think that should be fine if we leave it as the message:
Title: Camera Permission Required
Message: Expensify.cash does not have access to your camera', please enable the permission and try again.

Updated

@Julesssss @NikkiWines
I have nothing more to do for this PR. Can you please take a look when you get a chance

Just a note that I'm experiencing different behavior than what is shown in the iOS video in the OP re: focusing

Toggling the keyboard on the simulator will switch between these behaviors. Though for a real device the keyboard will always pop out (unless it has an external keyboard)

I would like to use rebase to resolve the merge conflicts
To preserve review history, I'll push a backup branch or a tag that will store the original commits
This way I think review history will be kept as the original commits would still exist
Relevant discussion on slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1617306783315300

Updated

To preserve review history, I'll push a backup branch or a tag that will store the original commits
This way I think review history will be kept as the original commits would still exist

Sorry this didn't work. 😞
You can still see what changes were requested in the Conversation tab, but they won't appear in "File Changes"
I've addressed all merge conflicts and tested that this still works as expected

PR was a pass, only thing is that we were able to reproduce this

This issue was reproducible in mWeb iOS only. On mWeb Android it was working as expected.
Title:
iOS mWeb - Attachment - Upload photo button does not work
Expected Result
The 3 attachment options appear.
Actual Result
Nothing happens after clicking the upload photo button
Action Performed

In a iOS device, go to Safari or Chrome
Navigate to staging.expensify.cash
Log in and navigate to a conversation
Click on the attachment button
Click on upload photo button.

Platform
mWeb iOS ✔
Version Number: 1.0.11-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/44479856/113798727-bddca100-9721-11eb-9386-be1c9c8f674d.mp4

Step 7 of the Web steps is failing only on firefox browser. Chrome browser works as expected.
Title:
Web - Firefox browser - After File Preview closes focus does not return to the input field automatically
Expected Result
After File Preview closes focus should be returned to the compose input field
Actual Result
After File Preview closes focus does not return to the input field automatically
Action Performed

Login in app https://staging.expensify.cash/signin
Open a chat
Press the (+) plus button to open the input menu
Select "Add Attachment"
The browser's file picker should open and you can select a file
When you select a file you should see File Preview modal
Pressing upload should upload the file and you should see the attachment/thumb inside the chat

Platform
Web (Firefox) ✔
Build: 1.0.13-0
Notes/Images/Videos
Important: This is only happening on Firefox. Let me know if I should open a separate issue for this. On chrome, the PR was a pass.
https://user-images.githubusercontent.com/44479856/113799871-ecf41200-9723-11eb-9e33-c8f5a2e92d53.mp4

This issue was reproducible in mWeb iOS only. On mWeb Android it was working as expected.

It wouldn't do anything on desktop Safari too

Web - Firefox browser - After File Preview closes focus does not return to the input field automatically

I've went to the point before the changes introduced here - v1.0.10-2 and the issue is still recreatable - it predates these changes

Thanks @isagoico. We have these issues covered already:
iOS mWeb - Attachment - Upload photo button does not work

We have a separate issue for Safari attachments, which currently doesn't work

Web - Firefox browser - After File Preview closes focus does not return to the input field automatically

We're handling focus issues together, I'll add this not to the issue to ensure Firefox is tested with the eventual fix: https://github.com/Expensify/Expensify/issues/154180

Thanks for the clarification! Will check the PR off then 🙇


New rule: ban index signatures entirely

Index signatures lead to all sorts of unsoundness and you're better off using a real Map in almost every case.

This rule should recommend https://immutable-js.github.io/immutable-js/docs/#/Map or TypeScript's ReadonlyMap type if the builtin Map really must be used.

First, my deep appreciation. Fantastic eslint plugin :)
I noticed that there is still a problem with this code
get scoreValueSingle(): ScoreValueType | null {
        const values: ScoreValueType | undefined = this.scoreValue[0];
        return values;
    }

TS said that the variable "values" is ScoreValueType. Which is obviously wrong :/

Thanks for the kind words @szagi3891 . What you describe is a good catch (thanks!) but it's a separate issue to the one in this ticket. I've created https://github.com/danielnixon/eslint-plugin-total-functions/issues/68 for the issue you describe. PR welcome ;-)

I think I found the reason. I submitted a PR :)
https://github.com/danielnixon/eslint-plugin-total-functions/pull/69/files
@danielnixon Could you please take a look at it?

This just landed a few hours ago: https://github.com/typescript-eslint/typescript-eslint/commit/d7dc108580cdcb9890ac0539e7223aedbff4a0ed
Maybe the best approach here is to teach that rule a new never option (akin to https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/consistent-type-assertions.md#assertionstyle)

This is less of an issue now that https://devblogs.microsoft.com/typescript/announcing-typescript-4-1-beta/#no-unchecked-indexed-access is a thing but probably still worth doing.

Even with noUncheckedIndexedAccess, there are other reasons to prefer real Map types: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map#objects_vs._maps


[SPARK-40669][TESTS] Parameterize rowsNum in InMemoryColumnarBenchmark

What changes were proposed in this pull request?
This PR aims to parameterize InMemoryColumnarBenchmark to accept rowsNum.
Why are the changes needed?
This enables us to benchmark more flexibly.
build/sbt "sql/test:runMain org.apache.spark.sql.execution.columnar.InMemoryColumnarBenchmark 1000000"
...
[info] Running benchmark: Int In-Memory scan
[info]   Running case: columnar deserialization + columnar-to-row
[info]   Stopped after 3 iterations, 444 ms
[info]   Running case: row-based deserialization
[info]   Stopped after 3 iterations, 462 ms
[info] OpenJDK 64-Bit Server VM 17.0.4+8-LTS on Mac OS X 12.6
[info] Apple M1 Max
[info] Int In-Memory scan:                         Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
[info] --------------------------------------------------------------------------------------------------------------------------
[info] columnar deserialization + columnar-to-row            119            148          26          8.4         118.5       1.0X
[info] row-based deserialization                             119            154          32          8.4         119.5       1.0X

$ build/sbt "sql/test:runMain org.apache.spark.sql.execution.columnar.InMemoryColumnarBenchmark 10000000"
...
[info] Running benchmark: Int In-Memory scan
[info]   Running case: columnar deserialization + columnar-to-row
[info]   Stopped after 3 iterations, 3855 ms
[info]   Running case: row-based deserialization
[info]   Stopped after 3 iterations, 4250 ms
[info] OpenJDK 64-Bit Server VM 17.0.4+8-LTS on Mac OS X 12.6
[info] Apple M1 Max
[info] Int In-Memory scan:                         Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
[info] --------------------------------------------------------------------------------------------------------------------------
[info] columnar deserialization + columnar-to-row           1082           1285         199          9.2         108.2       1.0X
[info] row-based deserialization                            1057           1417         335          9.5         105.7       1.0X

$ build/sbt "sql/test:runMain org.apache.spark.sql.execution.columnar.InMemoryColumnarBenchmark 20000000"
[info] Running benchmark: Int In-Memory scan
[info]   Running case: columnar deserialization + columnar-to-row
[info]   Stopped after 3 iterations, 8482 ms
[info]   Running case: row-based deserialization
[info]   Stopped after 3 iterations, 7534 ms
[info] OpenJDK 64-Bit Server VM 17.0.4+8-LTS on Mac OS X 12.6
[info] Apple M1 Max
[info] Int In-Memory scan:                         Best Time(ms)   Avg Time(ms)   Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
[info] --------------------------------------------------------------------------------------------------------------------------
[info] columnar deserialization + columnar-to-row           2261           2828         555          8.8         113.1       1.0X
[info] row-based deserialization                            1788           2511        1187         11.2          89.4       1.3X

Does this PR introduce any user-facing change?
No. This is a benchmark test code.
How was this patch tested?
Manually.

Hi, @viirya . Could you review this test PR?

LGTM. One minor comment.

Since this test PR is already manually tested to attach the result into the PR description and the last two commits are about string changes about benchmark title, I'll merge this~ Thank you!

Merged to master/3.3.


Initial support for wedge rendering

Add initial support for "wedge" rendering, where a single property is ramped between two values across successive screenshots, and the resulting image set is merged into a strip.  The new feature is activated by pressing the 'W' key in the MaterialX viewer, and settings for the render are hardcoded for now.
Add hotkeys for adjusting camera zoom (+/-).
Add utilities FilePath::addExtension and MaterialX::stringEndsWith.
Refactor Viewer::drawContents for greater flexibility.
Update changelog for recent work.

Here's an example of a wedge render, where the roughness property is interpolated between 0 and 1.  This feature should be useful in upcoming physically-based shading tasks such as #403:


Condense schema README

README was a perfect resource, Giulio.
Where it went?

@guillempuche most of the documentation has been moved to the website: https://effect.website/docs/guides/schema (this PR added a link in the README under "Documentation")


Improve drawable errors for attributes with known values

The drawable xml from #3301 contains android:fillType attribute with unsupported value 1.
This causes an exception at runtime:
Exception in thread "AWT-EventQueue-0" java.lang.UnsupportedOperationException: unknown fillType: 1
	at androidx.compose.ui.res.vector.DesktopValueParsers_desktopKt.parseFillType(DesktopValueParsers.desktop.kt:73)

The error is justified, because the 1 is not a valid value for the fillType.
However, the error could list valid possible values like happens during build on Android (Android's message is also somewhat confusing, but at least it mentions the valid values):
Android resource linking failed
com.example.myapplication.app-main-46:/drawable/customicon.xml:3: error: '1' is incompatible with attribute fillType (attr) enum [evenOdd=1, nonZero=0].
error: failed linking file resources.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


enhanceRemove unnecessary locks

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Remove unnecessary locks
Release note
Remove unnecessary locks
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[x] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[x] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run cloud_p0


docs: Rename localhost DNS name to host.docker.internal

Description:
I found that docker.for.mac.localhost has been deprecated, which is used in envoy docs.
This PR renames them to host.docker.internal which is supported on Docker v18.03.0 above.
https://docs.docker.com/docker-for-mac/release-notes/#docker-community-edition-18030-ce-mac59-2018-03-26
Risk Level: Low
Testing: N/A
Docs Changes: fix sample code in grpc_json_transcoder_filter
Release Notes: N/A

/wait


Vert.x Native template

Initial import of the vertx native template to the template store.
This template uses Eclipse Vert.x as the toolkit to write functions and compiles the java code to native using GraalVM SVM, making the final function a native binary with instant startup and reduced memory usage.

Hi @pmlopes this is looking 💯
My for the openfaas/templates repo is that it contains 1st party templates which the immediate project team is comfortable maintaining and supporting.
I'd see Vert.x as a third-party template held on your own GitHub repo and maintained by yourself. The way we'd get this in the hands of developers is through the template store -> https://github.com/openfaas/store/blob/master/templates.json
Please can you:

Publish this PR in your own empty templates repo (pmlopes/vertx-native-template) ?
Send a PR to the template store

👍 profit
Alex

@alexellis I've created the new PR on the store here:
https://github.com/openfaas/store/pull/66
And Have moved the the code from this PR to:
https://github.com/pmlopes/openfaas-vertx-native-template

Thanks I've merged your store PR.


Add a polyfill for the HashCode struct

Add a polyfill for the HashCode struct, .NET Source.

My bad, this is already implemented.


Strictly hierarchical assertions preceding fit method

Deprecates pandas tags leaving pure numpy in methods.py and probabilistic_methods.py
Saves unnecesary computation to failed run after some fit time spent.

First is in place.
Second we could add a class attribute IS_STRICTLY_HIERARCHICAL that can be checked in reconcile, but it's a minor thing imho (in time).


Adyen tests with credit card and 3D secure not passing

Description
Fix tests for Adyen with credit card and 3D secure

:tada: This issue has been resolved in version 4.0.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ch14.1-14.4

Job d2l-zh/PR-922/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-922/

Job d2l-zh/PR-922/4 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-922/

Job d2l-zh/PR-922/5 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-922/

Let me know when this is merged so i'll build

Job d2l-zh/PR-922/6 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-922/

Job d2l-zh/PR-922/7 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-922/


Don't use normalized url in Angular custom nav client

Using the normalized url is causing side effects resulting in a broken experience. Given the normalization is there for the Angular router (which isn't being used for navigateToLoginRequestUrl), we can just use the absolute url provided as-is.

Codecov Report

Merging #3757 (2a2659e) into dev (2a529d8) will increase coverage by 0.03%.
The diff coverage is 83.33%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
95.65% <83.33%> (+0.99%)
:arrow_up:

msal-browser
84.64% <ø> (ø)

Carriedforward from 2a529d8

msal-common
83.41% <ø> (ø)

Carriedforward from 2a529d8

msal-core
73.02% <ø> (ø)

Carriedforward from 2a529d8

msal-node
78.35% <ø> (ø)

Carriedforward from 2a529d8

msal-react
93.77% <ø> (ø)

Carriedforward from 2a529d8

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

lib/msal-angular/src/msal.navigation.client.ts
92.85% <83.33%> (+15.93%)
:arrow_up:


[Message] Keep header case sensitivity

Hey!
This PR tries to fix #43 I'm not really fan of the changes I have made on the filterHeaders but I would like some feedbacks first.
Btw, with this fix, the tests of egeloen/ivory-http-adapter#74 are green again :)

@weierophinney Any thoughts?

@egeloen I've created a PR against your branch (linked above) that shows what I was trying to get across. There may be a few more tests to write, but what I've got demonstrates the behaviors I'm expecting.

@weierophinney Thanks for your PR! I have merged it and fixed an issue about headers initialization.
Ready for merging!


Hide Ad Position till Ads Getting Loaded

Hi ! I am wondering if there possibility with recycler view like view.GONE and view.VISIBLE on ads loaded, loading as well loading failed.

@karopass Hi,
I really tried to implement it but I had no enough time to get with it. Maybe a bit later! It's really annoying. If you'll solve it earlier than me, kindly suggest a commit to the trunk.

@karopass Please get the latest from the branch https://github.com/clockbyte/admobadapter/tree/experimental. I have fixed this issue there. I should warn you that I've made a lot changes there and you could get some errors after updating but I'm sure that this game is worth the candle :) Also I'm going to make my library Gradle/Maven-linkable soon...


Vulnerability roundup 91: libredwg-<IP_ADDRESS>07: 1 advisory [6.5]

search, files

[ ] CVE-2020-15807 CVSSv3=6.5 (nixos-unstable)

Scanned versions: nixos-unstable: 840c782d507. May contain false positives.
Cc @thorstenweber83

This looks like a false positive to me.
All the commits referenced in the issues the CVE lists are already part of <IP_ADDRESS>07 as far as I can see.

This is why we have to review these. Version information in CVEs is not always correct.


test(concurrency): add versioned state proxy flow test

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.06%. Comparing base (461631e) to head (f0df9a2).

Additional details and impacted files
@@                                 Coverage Diff                                  @@
##           mohammad/versioned-db/add-versioned-proxy-flow-test    #1828   +/-   ##
====================================================================================
  Coverage                                                76.06%   76.06%
====================================================================================
  Files                                                       60       60
  Lines                                                     8556     8556
  Branches                                                  8556     8556
====================================================================================
  Hits                                                      6508     6508
  Misses                                                    1622     1622
  Partials                                                   426      426

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


esp_netif_list_lock/esp_netif_list_unlock freeing mutex creates problems (IDFGH-11088)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v4.4.4 / latest master
Operating System used.
Windows
How did you build your project?
Command line with CMake
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-wrover-kit
Power Supply used.
USB
What is the expected behavior?
No race conditions leading to crashes
What is the actual behavior?
Race conditions leading to crashes:
The issue is that the mutex protecting the esp_netif_list isn't thread-safe.
Two reasons:

In theory two threads could try and create an interface at the same time, each reaching esp_netif_list_lock at the same time. The first thread could context-switch just after having detected that the current mutex is null, and planning to allocate a new one. The other could then allocate one as well, and lock it, before context switching back. When the first one is brought back up, it will overwrite the first one, causing corruption.
The chances of this happening are small though, but it is still bad design.
The correct way of doing this is initing the relevant mutexes once in some init function.

The fact that the mutex is again optionally destroyed on esp_netif_list_unlock is really bad. (See here  )
For instance, if we call esp_netif_get_handle_from_ifkey (e.g. by mdns_init) at the same time and/or just before an interface is created, it can lead to the mutex being allocated, freed, but also simultaenously used.

This has led to constant crashes of spinlocks asserts that can be found in the debug logs.
Note that this guy https://www.esp32.com/viewtopic.php?t=20233 has clearly seen this issue before in 2021 already.
A correct design would have an init function, deinit function, and not alloc/dealloc mutexes at runtime..
Steps to reproduce.
Problem 1) Create two threads, that simultaneously try to create interfaces. (Very hard to reproduce though)
Problem 2) Also a tricky race condition, but was able to reproduce this in a constant crashloop:

Call mdns_init in one thread
In other thread, simultaneously create the FIRST interface

By slightly varying the delays between the thread execution sequences, the spinlock crash can be triggered. (But as this is a race condition, this is tricky. Anyway, just from reading the code the issue can be clearly spotted)
Debug Logs.
`
assert failed: spinlock_acquire spinlock.h:123 ((result == SPINLOCK_FREE) == (lock->count == 0))

Backtrace: 0x4008231d:0x3ffd73d0 0x40095185:0x3ffd73f0 0x4009c0ed:0x3ffd7410 0x40099441:0x3ffd7530 0x400963f5:0x3ffd7570 0x40142f55:0x3ffd75b0 0x4014310d:0x3ffd75d0 0x40143c61:0x3ffd75f0 0x401460db:0x3ffd7620 0x400f84a2:0x3ffd7650 0x40099211:0x3ffd7820
0x4008231d: panic_abort at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_system/panic.c:408

0x40095185: esp_system_abort at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_system/esp_system.c:137

0x4009c0ed: __assert_func at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/newlib/assert.c:85

0x40099441: spinlock_acquire at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_hw_support/include/soc/spinlock.h:123
 (inlined by) xPortEnterCriticalTimeout at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/freertos/port/xtensa/port.c:301

0x400963f5: vPortEnterCritical at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/freertos/port/xtensa/include/freertos/portmacro.h:578
 (inlined by) xQueueSemaphoreTake at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/freertos/queue.c:1563

0x40142f55: esp_netif_list_lock at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_netif/esp_netif_objects.c:51

0x4014310d: esp_netif_get_handle_from_ifkey at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_netif/esp_netif_objects.c:175

0x40143c61: esp_netif_new at C:/ESP32/esp-idf-eclipse-444/esp-idf/esp-idf-v4.4.4/components/esp_netif/lwip/esp_netif_lwip.c:462
`

More Information.
No response

Hi @david-cermak
Is it possible to change the esp_netif_next() implementation to use esp_netif_tcpip_exec()
so it won't impact with existing users?
Otherwise you are actually asking exist users to repeat similar implementation in various places.

Hi @AxelLin
I'm afraid that's not possible. The problem is in the API design itself (similar to the macro NETIF_FOREACH() in lwip), which could not assure thread safety between iterations.
That's why I marked the esp_netif_next() deprecated, so the existing users would get notified and should think about their usecases to do one of the following:

just rename esp_netif_next() -> esp_netif_next_unsafe() if all interfaces are strictly under their control and are created once.
rework the iteration, for example using esp_netif_find_if() for searching interfaces in a safe way, if the application interfaces could be created/destroyed runtime from multiple tasks

Then I need to wait until the fix is available in stable branches, and update application code accordingly.

Yes, will fix on all release branches (down to v4.3)


There is a new version of the vnote (2.10 --> 3.2.0)

There is a new version of the vnote (2.10 --> 3.2.0)
https://github.com/vnotex/vnote/releases

Vnote.json is missing checkver field.
https://github.com/lukesampson/scoop-extras/blob/b3c4b46dda148ef40a29e83723925659b19a57a6/bucket/vnote.json
    "checkver": {
        "github": "https://github.com/vnotex/vnote"
    },


Fill chat box

Right now, in chat, old messages are deleted when 10 messages are reached. However, due to the size of the chat box, this looks really weird:

The chat should continue to fill up until it is full before it starts deleting old messages.

Does it even have to start deleting old messages at all? What about scrolling?

That's a good idea. However, if a user were to leave the chat open for a while, would the amount of messages start to slow down their client? (I'm not sure). Each time a new message is sent, more memory is allocated for the message.

If it would start slowing down the client then we should of either detecting it some way or let the user clear the chat.  (BTW the send button is not aligned)

It would slow down if you collected messages infinitely, but it would take a long time. If that's a concern you can always do what SE does with chat - it pages it after X period of time and you have to explicitly request for the past Y messages

I like @danpantry 's idea, however that would probably require we store chat messages on the server; is this something we should do?

or just trim it at a certain length past visibility, and don't page the messages. like web IRC clients do

@Phrancis We could make it an option on that the server can store the message. When the client connect it checks if the server store message and store it somewhere. So if it's enabled the option of @danpantry would query the server and if not it does nothing. This will make it the chat system more elaborate though.

Maybe we could combine some ideas. We can have the chat trim at a certain length past visibility, and if the user wants to see older messages, they can press a button to get older messages stored on the server.

That's a good compromise, @marcandregirard. Perhaps have it so that the individual "version" of Cardshifter (based on the card sets given by users) can specify the URL to post/receive chat from. If not specified it just stays in localStorage or similar

We have way too many better things to focus on than having the client query the server for old chat messages.
We should investigate what users prefer (or what they are okay with) before wasting time on adding a feature that potentially no one would even want.

@Zomis Should anything be done in the meantime, or should we just ignore this until later?

I think we should use a scrollbar for the chatmessages until that becomes a problem for game clients.

@Zomis +1. overflow-y: scroll

This is implemented in vanilla-js-rewrite branch using CSS grids, commit 71ad9f81.

Confirmed this is continuing to be an issue in Vue.js client, will address while working on #136.


[Event Request] Codeunit 5051 SegManagement - IsHandled pattern to test the Salesperson code in the TestFields function

Hi,
Is it possible to add the lines that check the value of the Salesperson code in a separate function?
Current solution:
    local procedure TestFields(var SegmentLine: Record "Segment Line"; Deliver: Boolean)
    var
        Cont: Record Contact;
        Salesperson: Record "Salesperson/Purchaser";
        Campaign: Record Campaign;
        InteractTmpl: Record "Interaction Template";
        ContAltAddr: Record "Contact Alt. Address";
    begin
        with SegmentLine do begin
            TestField(Date);
            TestField("Contact No.");
            Cont.Get("Contact No.");
            if "Document Type" = "Document Type"::" " then begin
                TestField("Salesperson Code");
                Salesperson.Get("Salesperson Code");
            end;

Proposed:
    local procedure TestFields(var SegmentLine: Record "Segment Line"; Deliver: Boolean)
    var
        Cont: Record Contact;
        Salesperson: Record "Salesperson/Purchaser";
        Campaign: Record Campaign;
        InteractTmpl: Record "Interaction Template";
        ContAltAddr: Record "Contact Alt. Address";
    begin
        with SegmentLine do begin
            TestField(Date);
            TestField("Contact No.");
            Cont.Get("Contact No.");
            if "Document Type" = "Document Type"::" " then
               **TestSalespersonCode(SegmentLine);  // call the new function**

    local procedure TestSalespersonCode(var SegmentLine: Record "Segment Line")
    var
        Salesperson: Record "Salesperson/Purchaser";
        IsHandled: Boolean;
    begin
        OnBeforeTestSalespersonCode(SegmentLine, IsHandled);
        if IsHandled then
            exit;

        SegmentLine.TestField("Salesperson Code");
        Salesperson.Get(SegmentLine."Salesperson Code");
    end;

And add the event OnBeforeTestSalespersonCode(SegmentLine, IsHandled);
  [IntegrationEvent(true, false)]
    local procedure OnBeforeTestSalespersonCode(var SegmentLine: Record "Segment Line"; var IsHandled: Boolean)
    begin
    end;

Thank you!
Monica Suica

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


How to get client list from redis

I need to get client list from Redis. But if i write:
var Redis = require('ioredis');
var redis = new Redis();

var clientList = new Redis.Command('client list', null, function (err, result) {
  console.log(result);
});

redis.sendCommand(clientList);

i see:
Unhandled rejection ReplyError: ERR unknown command 'client list'
    at JavascriptReplyParser.replyParser.Parser.returnError (node_modules/ioredis/lib/redis/parser.js:25:25)

P.S. If i use redis-cli then i can to get client list:

Just redis.client('list', function (err, result) {}); should work. ioredis supports all redis commands so that you don't need to create new Redis.Command instances yourself.

@luin Thank you! It works!
But perhaps it is worth adding a parser for redis.client('list') from returned string:
id=112 addr=<IP_ADDRESS>:55153 fd=6 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client

You can define your own reply transformer to parse it (https://github.com/luin/ioredis#transforming-arguments--replies) or simply parse it on the client side.

Thank you!


infer in visdrone when uses csq!

when i use queydet to train in visdrone, everything is ok, but when i infer in visdrone, there is some issues about spconv.

the spconv`s version is 2.x

I met the problem. The spconv is only used in inference, that's why there is no problem in training.
I have tried the spconv-cu102-2.1.21, spconv-cu102-2.1.19,spconv-cu102-2.1.5, it still doesn't work.

I met the problem. The spconv is only used in inference, that's why there is no problem in training. I have tried the spconv-cu102-2.1.21, spconv-cu102-2.1.19,spconv-cu102-2.1.5, it still doesn't work.

maybe it`s because the code is based pm spconv 1.x? i find that the usage of spconv is based on spconv 1.x

i try to replace spconv 2.x with spconv 1.2.1 and i successfully run infer_visdrone.py


Error while placing order or withdraw

What version are you using?
What did you do?
placing orders doesn't work
What did you expect to see?
What did you see instead?
"An error occurred while processing this request. This is usually due to a bug within the server software. Trying this request again may succeed if the bug is transient, otherwise please report this issue to the issue tracker at: https://github.com/stellar/go/issues. Please include this response in your issue."

Can you provide more information? Is it your local Horizon, if so can you send a log? What was the transaction envelope?

I was trying to place an order on StellarX.com  and got message:
"An error occurred while processing this request. This is usually due to a bug within the server software. Trying this request again may succeed if the bug is transient, otherwise please report this issue to the issue tracker at: https://github.com/stellar/go/issues. Please include this response in your issue."
Same thing is when I tried to withdraw funds

Please contact StellarX support here: https://stellarxsupport.zendesk.com/hc/en-us Looks like it's StellarX issue.

Can you provide more information? Is it your local Horizon, if so can you send a log? What was the transaction envelope?

Please contact StellarX support here: https://stellarxsupport.zendesk.com/hc/en-us Looks like it's StellarX issue.

Ok, thank You, that sounds logical :) . I got here for reporting cause it was stated like that in error message. Have a nice day!

This is why we need #2034

Hi, thank you for fast response. Unfortunatelly I don't understand what to
do. Im not developer nor using third party app. I was trying to place
orders throuh web page www.stellarx.com via chrome browser and via firefox
browser. What should i do?
Best regards,
Ivan
On Thu, 27 Feb 2020, 16:56 Eric Saunders<EMAIL_ADDRESS>wrote:

This is why we need #2034 https://github.com/stellar/go/issues/2034
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stellar/go/issues/2333?email_source=notifications&email_token=ALDPC5Z322MKERMLOBU4QLLRE7PD3A5CNFSM4K43MXR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENE3Q6I#issuecomment-592033913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDPC52QXLERLKNSZ4FNCNDRE7PD3ANCNFSM4K43MXRQ
.

Sorry Ivan, my comment is for our benefit so we can improve this and future people won't get sent here. You should go ahead and contact StellarX support as @bartekn suggested. Good luck!


Nuxt/Auth provider

We should add a Nuxt auth provider. Details here:
https://github.com/nuxt-community/auth-module/issues/1082

@sduduzog any experience with this side of things? I'm gonna dive into it this weekend and build something.

I have none at all.  I might join you but mostly for the TS setup. I've never had a chance to use the auth module

So I think we would need to make a scheme and a provider. Similar to how auth0 is done.
https://github.com/nuxt-community/auth-module/tree/dev/src/schemes
https://github.com/nuxt-community/auth-module/tree/dev/src/providers


Batch insert support

Hi,
We currently have an application which needs to insert large sets of records into a SQLServer database.
This can be accomplished either with a "Table Valued Parameter" which is passed to a stored procedure. The "Table Value Parameter" contains a set of records which can be passed from the client to the driver. It's much more efficient then inserting sets row by row.
The SQLServer odbc driver supports this variable type:
https://learn.microsoft.com/en-us/sql/relational-databases/native-client-odbc-table-valued-parameters/table-valued-parameters-odbc?view=sql-server-ver16.
The other (probably more generic approach) is to support the ODBC SQLBulkOperations function:
https://learn.microsoft.com/en-us/sql/odbc/reference/syntax/sqlbulkoperations-function?view=sql-server-ver16.
We are willing to assist in implementing such a feature or donate to someone who's willing to implement this.
Please let us know if this is possible.
Kind regards.

Hi @ErikJansenIRefact ,
This might be a duplicate of #75, but your idea to use SQLBulkOperations is new, I was planning on using some batch support. This was actually the next major enhancement I wanted to implement before I got waylaid with other work. I think I actually have a half-complete branch somewhere. Let me take another peek at this and do some rough architectural sketches of what is involved.

Hi Mark,
Would be great. In the meantime we are trying to implement SQLBulkOperations and see how it goes.

Do not close.

Any news on batch insert support ? @markdirish


Ci tests

Quick scaffold for https://github.com/DispatchMe/meteor-mocha/issues/10
These are simple no-op passing tests on client and server.  Currently passing on CircleCI.
Perhaps would be nice to have more fine grained tests, like testing that failing tests exit with correct exit codes. But could be overkill.

Wrong branch


ARROW-284: Disable arrow_parquet module in Travis CI to triage builds

+1. Merging to unblock other patches from getting green builds


Complete overhaul of CCL compilation framework

Ok, so I know how a pull request affecting 41 files with 70,161 deletions is going to look, but just hear me out first ;-)
Long story short, here is what this PR will allow you to do (once approved and uploaded to PyPi):
$ pip install pyccl

No questions asked, whether running on cori, a random linux or even on Mac OS X.
Here are a few more details:

pip installable CCL package from PyPi
compiles seamlessly on Mac OS X and Linux with support of clang and gcc
automatically finds all dependencies if installed on the system and downloads missing requirements (including swig, class, fftw, gsl) with no intervention from the user
automated (re-)generation of swig interface (as needed, no intervention from the user)
automatically finds the correct python and numpy libraries to link to
proper install of C library with pkg-config file
Adds Travis CI tests for Mac OS X

The main motivation for these changes is that I got annoyed that I couldn't pip install ccl on my local cluster... but they also address a number of open issues #269 #270 #160 #70
The price to pay for all of this automation is to get rid of the current autotools-based build system and switch to CMake goodness instead. CMake takes care of everything for you (including downloading and building missing dependencies) and is completely cross-platform. The build process for the C library now becomes:
$ mkdir build && cd build    # creates a separate build directory to store all the generated files
$ cmake ..                   # CMake configuration: looks for C compiler, python interpreter, fftw, gsl...
$ make                       # Builds  C library along with missing dependencies

and for the python module it's even easier:
$ python setup.py install

no need to worry about class, swig, gsl, or fftw.
Now, in terms of modifications, here is what I changed:

removed all the makefiles, configure, install_gsl.sh, and class_install.py  files.
All of this is now replaced by CMake. The main script is in CMakeLists.txt with a few extra modules in cmake/Module to take care of finding/compiling external libraries (downloading, compiling and adding CLASS to the project is just one CMake command).
simplified setup.py and added extra fields for PyPi
Because all of the  heavy lifting is done by CMake, the setup.py only needs to call cmake and collect the output library.
python module: automated swig generation, standalone install, includes ccl_params.ini
To make sure the python code is portable, I have removed the pre-computed swig interface, it is now automatically regenerated  (not a problem because swig is found or downloaded by cmake so will always be available). In order to make the python module standalone, it is linked against static libraries so that you don't have to install the  C library and can erase the CCL folder afterwards without breaking the python module. Also, ccl_params.ini gets added to the python module when it is built and at runtime in __init__.py will check if the environment variable CCL_PARAM_FILE already exists, otherwise it defaults to the ccl_params.ini included in the package. Finally, I have switched to nose tests which automatically discovers all the python tests without needing a separate script.
created pkg-config file:
A pkg-config file for CCL is now automatically created and installed on the system, so that other projects can easily link to CCL. In particular, compiling a c file and linking it to ccl becomes:

$ gcc ccl_sample_run.c `pkg-config --libs --cflags ccl` -o ccl_sample_run

Updated documentation:
I have updated the documentation on the install procedure to reflect the new cmake process

Concerning license issues, I think my modifications are OK, I am not packaging CLASS along with the code, it is downloaded and compiled by the user everytime. As long as we only upload a src package to PyPi it should be ok.
I have tested all of this on my various linux PCs, my local cluster, cori and Mac OS X using travis CI, but that doesn't cover all the variety of setups out there, if people find any difficulties in building CCL I will be  happy to provide all the necessary support.

I just tried the following install:
conda create -n CCLTEST python=3.6 pip
source activate CCLTEST
pip install git+git://github.com/EiffL/CCL.git

but it failed to download CLASS:
    ...
    [  2%] Creating directories for 'CLASS'
    [  5%] Performing download step (download, verify and extract) for 'CLASS'
    -- downloading...
         src='https://github.com/lesgourg/class_public/archive/v2.6.3.tar.gz'
         dst='/private/var/folders/7j/j43qxbs15w73xp3ldj323sh40000gn/T/pip-7rtv5m_3-build/build/CLASS/src/v2.6.3.tar.gz'
         timeout='none'
    CMake Error at CLASS-stamp/download-CLASS.cmake:27 (message):
      error: downloading
      'https://github.com/lesgourg/class_public/archive/v2.6.3.tar.gz' failed

        status_code: 35
        status_string: "SSL connect error"
        log:   Trying <IP_ADDRESS>...

      Connected to github.com (<IP_ADDRESS>) port 443 (#0)

      Unknown SSL protocol error in connection to github.com:-9836

      Closing connection 0

The direct link https://github.com/lesgourg/class_public/archive/v2.6.3.tar.gz works in my browser, so this looks like a problem with the SSL credentials used by the python downloader.

Ok thanks David. No worries, if SSL is an issue we can download class using
git. It may be even a better idea, people could specify as an option which
class repo/branch/tag to use when building CCL.
On Fri, Mar 30, 2018, 10:32 AM David Kirkby<EMAIL_ADDRESS>wrote:

The direct link
https://github.com/lesgourg/class_public/archive/v2.6.3.tar.gz works in
my browser, so this looks like a problem with the SSL credentials used by
the python downloader.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/CCL/pull/357#issuecomment-377536743, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0ll7NFoQXFIIXttHjn-5oHvDy5yfMXks5tjkISgaJpZM4TBXY_
.

There, that should fix it.

Thanks @fjaviersanchez

Pull Request Test Coverage Report for Build 1468

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 93.956%

Totals

Change from base Build 1448:
0.03%

Covered Lines:
513

Relevant Lines:
546

💛  - Coveralls

@elisachisari Ok done. Everything works now, including the Angpow integration, I think it's ready to merge. There is one last reference to my fork of Angpow4CCL but hopefully Jeremy can get that merged tomorrow.
I have uploaded a release to the test pypi:
https://test.pypi.org/project/pyccl
Looks very nice and can be installed with:
$ pip install --user --index-url https://test.pypi.org/simple/ pyccl

@fjaviersanchez you had created a pyccl package on pypi I think. I don't have the password for the desc ccl author, but I have created a section (untested) in the .travis.yml which should upload automatically to pypi whenever a new version of ccl is tagged.
Could you encrypt the password using the procedure described here: https://docs.travis-ci.com/user/deployment/pypi/

Thanks @fjaviersanchez, I tried to test it on my fork, but of course it didnt work because the sure
credentials  only work from this repo. I'm pretty it'll work fine though, we can always  fix it if it doesn't work once it's  merged in master


omc logs doesn't display full logs

Running omc logs doesn't display full logs at times, example (giving last lines only):
2024-04-25T10:27:16.123509482Z -------------------------------------------------------------------------------
2024-04-25T10:27:16.136898334Z {"level":"error","ts":1714040836.136772,"logger":"logging_event_handler","msg":"","name":"tower-na1","namespace":"tower","gvk":"automationcontroller.ansible.com/v1beta1, Kind=AutomationController","event_type":"runner_on_failed","job":"7146056215829118087","EventData.Task":"Apply deployment resources","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/roles/installer/tasks/resources_configuration.yml:248","error":"[playbook task failed]","stacktrace":"github.com/operator-framework/operator-sdk/internal/ansible/events.loggingEventHandler.Handle\n\toperator-sdk/internal/ansible/events/log_events.go:111"}

What the last lines of the log file is:
2024-05-01T16:49:13.191554233Z
2024-05-01T16:49:13.191554233Z ----- Ansible Task Status Event StdOut (automationcontroller.ansible.com/v1beta1, Kind=AutomationController) -----
2024-05-01T16:49:13.191554233Z
2024-05-01T16:49:13.191554233Z
2024-05-01T16:49:13.191554233Z PLAY RECAP *********************************************************************
2024-05-01T16:49:13.191554233Z localhost                  : ok=84   changed=0    unreachable=0    failed=0    skipped=80   rescued=0    ignored=1
2024-05-01T16:49:13.191554233Z
2024-05-01T16:49:13.191554233Z
2024-05-01T16:49:13.191554233Z ----------

For context, this file is 19837 lines long and 6.0M.

@rh-dluong I've done a test with a file of 95622 lines and 23M, it worked well, so please share the must-gather you are using, either here with the sensitive data obfuscated or on Slack, thank you!


Auto Resize Text Using Button Without Pinch

Hello,
Can we do Auto Resize of Text on Button without Pinch.
https://user-images.githubusercontent.com/91049174/147642885-cdf72f1d-01a0-4e32-a5bb-ad44a6b438f3.mov
Thanks in advanced

Sorry, I don’t think I will support this feature.


cannot load module with webpack and bower

I am using webpack and bower together, however, i got the below error:
10:20:37 webpack.1 | Module not found: Error: Cannot resolve module 'pickadate' in (my_app_path)

here is my bower.json
{
  "name": "my app",
  "version": "1.0.0",
  "description": "my app",
  "dependencies": {
    "pickadate": "~3.5.6"
  }
}

then i use require('pickadate') in my js
any ideas?

See #779

Does not solve the issue for me. Using webpack 2. I can see that AMD is off, though $.pickadate is not a function.

This solution is for ng-pickadate (wrapper that uses pickadate), but I think it can apply to pickadate as well (specially the trick of the files and disable AMD for the pickadate path).
Following the steps mentioned in this thread, I manage to make it work without having to tweak the code under node_modules. Just a quick recap (angular 1, webpack 2 solution):
First install ng-pickadate
npm install ng-pickadate

It will download as well jquery and pickadate dependencies.

Then we need to add the depencies in our webpack.config, here there's a catch  pickadate.js package json main seems not to be pointing to the right entry point, we have to manually indicate which files we want to include:
module.exports = {
  context: path.join(basePath, 'src'),
  resolve: {
    extensions: ['.js', '.ts']
  },
  entry: {
    app: './app/app.ts',
    vendor: [
+      'jquery',
+      'angular',
+      'pickadate/lib/picker',
+      'pickadate/lib/picker.date',
+      'ng-pickadate',
    ],

Now comes fun part, pickadate will try to load AMD modules, in my case we need commonjs, we don't want to change the code on the library, rather disable this
using a rule (loader), just only for the pickadate folder:
  module: {
    rules: [
+      {
+        test: /pickadate/,
+        parser: { amd: false }
+      },
      {
        test: /\.ts$/,

Now let's  review our provide plugin and ensure we have all this ways of global referencing jquery (window.jquery quite important !)
  plugins: [
+    new webpack.ProvidePlugin({
+      "$": "jquery",
+      "jQuery": "jquery",
+      "window.jQuery": "jquery",
    }),

It's time to start using this in our app, let's include it in the angular module where
we are using it (we are using angular 1.6):
import * as angular from 'angular';
import { LoginComponent } from './login.component';

export const LoginModule = angular.module('loginModule',
+ ['pickadate'])
  .component('login', LoginComponent)
;

And let's use the directive in the HTML (input)

                            Birthdate
                            <input
                                type="text"
+                                pick-a-date="vm.curDate"/>

All this steps are just a recap of feedback got from several issues that were open, thanks to all the chaps that were providing the right tips :-).

Hi, I am new pickadate module.
I am just using this module in laravel application for custom datepicker
but I am getting $(...).pickadate is not a function error now .
So I think this is because I have not include the modules in right place.
I am using webpack  and laravel mix for Js compiling.
But I am not sure how can I include this module in my project.
Thank you for regarding my issue.

Closing as this issue is very old and we did not receive further feedback.
You might want to try the externals option of webpack.


Uploaded file:: FUMEC university

FUMEC University

@casima I am sorry for a delay with processing your request.
Pull request merged. Thank you!


Support older versions of Android

Is your feature request related to a problem? Please describe.
I added the RUM SDK to our React Native app, and tested with iOS. Everything was great. Then I tried to test it on Android and it wouldn't compile. The reason is this SDK requires API version 31, which is the Android ecosystem is super recent. I did some exploring and 25% of our users are on SDK version 30, so we won't be able to use the SDK given the version dependency on 31+.
Further exploration, if you open the Android Studio and create a new project, today's (April 20, 2022) distribution is this:

This leads me to believe the current 31+ requirement will capture less than a quarter of the Android market.
Describe the solution you'd like
For us, supporting Android SDK 30 would be sufficient, but looking at the stats above, others might need even older than that depending on their user base.
Describe alternatives you've considered
I considered changing our app to require SDK 31, but that would knock out 25% of our user base.
Additional context
The official docs https://developer.android.com/about/dashboards is what led me to use the Create New Project wizard and then click on the "Help me choose" stats.
Other resources here: https://gs.statcounter.com/os-version-market-share/android

Hello @pas256. Requirement for using SDK 31 is regarding compileSdkVersion, not minSdkVersion (it is mandatory to have compileSdkVersion = 31 to have WorkManager library working on Android 12+ devices).
So you can safely bump compileSdkVersion to 31, while keeping minSdkVersion the same as you have right now and not loosing the user base.

Hello @pas256! I believe your question was answered, so I am closing this ticket. Don't hesitate to re-open it if you still have questions regarding the versions used.

Yes, thank you!


🐛 [firebase_crashlytics] Unreadble stacktrace

Bug report
Describe the bug
App released with crashlytics integration from documentation.
Stacktrace of event are unreadable.
An exemple of what I got :

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: LateInitializationError: Field 'Nff' has not been initialized.. Error thrown Instance of 'qE'.
at .    #00 abs 0 virt<PHONE_NUMBER>61f0d7 _kDartIsolateSnapshotInstructions+0x2ae637(.java)
at .    #01 abs 0 virt<PHONE_NUMBER>4d67af _kDartIsolateSnapshotInstructions+0x165d0f(.java)
at .    #02 abs 0 virt<PHONE_NUMBER>4d6743 _kDartIsolateSnapshotInstructions+0x165ca3(.java)
at .    #03 abs 0 virt<PHONE_NUMBER>4d68c7 _kDartIsolateSnapshotInstructions+0x165e27(.java)
at .    #04 abs 0 virt<PHONE_NUMBER>579fff _kDartIsolateSnapshotInstructions+0x20955f(.java)
at .    #05 abs 0 virt<PHONE_NUMBER>8dbdcf _kDartIsolateSnapshotInstructions+0x56b32f(.java)
at .    #06 abs 0 virt<PHONE_NUMBER>8dba2b _kDartIsolateSnapshotInstructions+0x56af8b(.java)
at .    #07 abs 0 virt<PHONE_NUMBER>3d4a1b _kDartIsolateSnapshotInstructions+0x63f7b(.java)
at .    #08 abs 0 virt<PHONE_NUMBER>3d4873 _kDartIsolateSnapshotInstructions+0x63dd3(.java)
at .    #09 abs 0 virt<PHONE_NUMBER>3d46af _kDartIsolateSnapshotInstructions+0x63c0f(.java)
at .    #10 abs 0 virt<PHONE_NUMBER>3d457f _kDartIsolateSnapshotInstructions+0x63adf(.java)
at .    #11 abs 0 virt<PHONE_NUMBER>37b91b _kDartIsolateSnapshotInstructions+0xae7b(.java)
at .    #12 abs 0 virt<PHONE_NUMBER>37ba07 _kDartIsolateSnapshotInstructions+0xaf67(.java)
at .    #13 abs 0 virt<PHONE_NUMBER>8b5dfb _kDartIsolateSnapshotInstructions+0x54535b(.java)
at .    #14 abs 0 virt<PHONE_NUMBER>8b7ee3 _kDartIsolateSnapshotInstructions+0x547443(.java)
at .    #15 abs 0 virt<PHONE_NUMBER>381e9b _kDartIsolateSnapshotInstructions+0x113fb(.java)
at .    #16 abs 0 virt<PHONE_NUMBER>389cc3 _kDartIsolateSnapshotInstructions+0x19223(.java)
at .    #17 abs 0 virt<PHONE_NUMBER>389c7f _kDartIsolateSnapshotInstructions+0x191df(.java)
at .    #18 abs 0 virt<PHONE_NUMBER>389d3b _kDartIsolateSnapshotInstructions+0x1929b(.java)

I'm expecting an human readable stack that help me to understand the problem.
Is it the normal behaviour ?
Thank you

Thank you

Additional context

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [version 10.0.22000.258], locale fr-FR)
    • Flutter version 2.5.3 at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (3 days ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\quent\AppData\Local\Android\sdk
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.61.1)
    • VS Code at C:\Users\quent\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.14.1

[√] Connected device (1 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86 • Android 8.0.0 (API 26) (emulator)

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.14.4
Flutter SDK 2.5.3
gamevent 0.8.1+315

dependencies:
- add_2_calendar 2.1.2 [flutter]
- auto_size_text 3.0.0-nullsafety.0 [flutter]
- cached_network_image 3.1.0 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- characters 1.1.0
- cloud_firestore 2.5.3 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- collection 1.15.0
- device_info 2.0.2 [flutter device_info_platform_interface]
- diacritic 0.1.3
- enum_to_string 2.0.1
- feedback 2.0.0 [flutter flutter_localizations meta]
- firebase_analytics 8.3.3 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_auth 3.1.3 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.7.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.2.3 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_database 8.0.0 [firebase_core firebase_database_platform_interface firebase_database_web flutter]
- firebase_messaging 10.0.8 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 0.11.0 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface flutter]
- firebase_storage 10.0.5 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_chat_ui 1.4.4 [flutter diffutil_dart equatable flutter_chat_types flutter_link_previewer intl meta photo_view]
- flutter_inappwebview 5.3.2 [flutter]
- flutter_keyboard_visibility 5.1.0 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_web flutter]
- flutter_local_notifications 9.0.0 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_localizations 0.0.0 [flutter intl characters clock collection meta path typed_data vector_math]
- flutter_staggered_animations 1.0.0 [flutter]
- font_awesome_flutter 9.1.0 [flutter]
- get 4.3.8 [flutter]
- get_storage 2.0.3 [flutter get path_provider]
- giphy_get 2.0.3 [flutter provider extended_image flutter_staggered_grid_view meta http]
- google_fonts 2.1.0 [flutter http path_provider crypto]
- image 3.0.8 [archive meta xml]
- in_app_review 2.0.3 [flutter in_app_review_platform_interface]
- infinite_scroll_pagination 3.1.0 [flutter sliver_tools]
- intl 0.17.0 [clock path]
- introduction_screen 2.1.0 [flutter dots_indicator]
- like_button 2.0.3 [flutter]
- native_admob_flutter 1.5.0 [flutter]
- overflow_view 0.3.1 [flutter value_layout_builder]
- package_info 2.0.2 [flutter]
- rive 0.7.32 [collection flutter graphs http meta]
- scrollable_positioned_list 0.2.2 [flutter collection]
- share_plus 3.0.4 [meta mime flutter share_plus_platform_interface share_plus_linux share_plus_macos share_plus_windows share_plus_web]
- showcaseview 1.1.2 [flutter]
- sliding_sheet 0.5.0 [flutter]
- table_sticky_headers 2.0.0 [flutter]
- tcard 1.3.5 [flutter]
- toggle_switch 1.2.0 [flutter]
- uni_links 0.5.1 [flutter uni_links_platform_interface uni_links_web]

dev dependencies:
- device_preview 0.7.4 [flutter flutter_localizations provider path_provider device_frame font_awesome_flutter http freezed_annotation json_annotation shared_preferences pedantic path]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_lints 1.0.4 [lints]
- flutter_native_splash 1.2.4 [args image meta path xml yaml universal_io]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

dependency overrides:
- provider 6.0.1 [collection flutter nested]

transitive dependencies:
- archive 3.1.6 [crypto path]
- args 2.3.0
- async 2.8.1 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- charcode 1.3.1
- clock 1.1.0
- cloud_firestore_platform_interface 5.4.2 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.4.3 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- crypto 3.0.1 [collection typed_data]
- csslib 0.17.1 [source_span]
- dbus 0.5.6 [args ffi meta pedantic xml]
- device_frame 0.4.2 [flutter_svg path_drawing freezed_annotation flutter]
- device_info_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- diffutil_dart 2.0.0+1
- dots_indicator 2.0.0 [flutter]
- equatable 2.0.3 [collection meta]
- extended_image 4.2.1 [extended_image_library flutter meta]
- extended_image_library 3.1.0 [crypto flutter http_client_helper path path_provider]
- fake_async 1.2.0 [clock collection]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase 9.0.2 [http http_parser js]
- firebase_analytics_platform_interface 2.0.1 [flutter meta]
- firebase_analytics_web 0.3.0+1 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_auth_platform_interface 6.1.1 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.1.2 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.1 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.1.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.1.3 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_platform_interface 0.1.0 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_web 0.1.0 [firebase_core firebase_core_web firebase_database_platform_interface flutter flutter_web_plugins js]
- firebase_messaging_platform_interface 3.0.6 [firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 2.0.6 [firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_remote_config_platform_interface 0.3.0+6 [firebase_core flutter meta plugin_platform_interface]
- firebase_storage_platform_interface 4.0.3 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.0.3 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flutter_blurhash 0.6.0 [flutter meta pedantic]
- flutter_cache_manager 3.1.2 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_chat_types 3.1.4 [equatable json_annotation meta]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_link_previewer 2.5.2 [flutter flutter_chat_types flutter_linkify html http linkify meta url_launcher]
- flutter_linkify 5.0.2 [flutter linkify]
- flutter_local_notifications_linux 0.3.0 [flutter flutter_local_notifications_platform_interface dbus path xdg_directories]
- flutter_local_notifications_platform_interface 5.0.0 [flutter plugin_platform_interface]
- flutter_staggered_grid_view 0.4.1 [flutter]
- flutter_svg 0.22.0 [flutter meta path_drawing vector_math xml]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- freezed_annotation 0.14.3 [collection json_annotation meta]
- graphs 2.1.0 [collection]
- html 0.15.0 [csslib source_span]
- http 0.13.4 [async http_parser meta path]
- http_client_helper 2.0.2 [http]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- in_app_review_platform_interface 2.0.2 [flutter url_launcher plugin_platform_interface platform]
- js 0.6.3
- json_annotation 4.3.0 [meta]
- linkify 4.1.0
- lints 1.0.1
- matcher 0.12.10 [stack_trace]
- meta 1.7.0
- mime 1.0.0
- nested 1.0.0 [flutter]
- octo_image 1.0.0+1 [flutter flutter_blurhash]
- path 1.8.0
- path_drawing 0.5.1+1 [vector_math meta path_parsing flutter]
- path_parsing 0.2.1 [vector_math meta]
- path_provider 2.0.5 [flutter path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_linux 2.1.0 [flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.2 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.3 [ffi flutter meta path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 4.3.0 [meta]
- photo_view 0.12.0 [flutter]
- platform 3.0.2
- plugin_platform_interface 2.0.2 [meta]
- process 4.2.3 [file path platform]
- rxdart 0.27.2
- share_plus_linux 2.0.4 [share_plus_platform_interface file flutter meta url_launcher]
- share_plus_macos 2.0.2 [share_plus_platform_interface flutter]
- share_plus_platform_interface 2.0.1 [flutter meta mime plugin_platform_interface]
- share_plus_web 2.0.4 [share_plus_platform_interface url_launcher flutter flutter_web_plugins meta]
- share_plus_windows 2.0.3 [share_plus_platform_interface flutter meta url_launcher]
- shared_preferences 2.0.8 [flutter meta shared_preferences_linux shared_preferences_macos shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shared_preferences_linux 2.0.2 [file meta flutter path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 2.0.2 [flutter shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.0.0 [flutter]
- shared_preferences_web 2.0.2 [flutter flutter_web_plugins meta shared_preferences_platform_interface]
- shared_preferences_windows 2.0.2 [flutter file meta path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sky_engine 0.0.99
- sliver_tools 0.2.5 [flutter]
- source_span 1.8.1 [collection path term_glyph]
- sqflite 2.0.0+4 [flutter sqflite_common path]
- sqflite_common 2.0.1+1 [synchronized path meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0
- term_glyph 1.2.0
- test_api 0.4.2 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timezone 0.8.0 [path]
- typed_data 1.3.0 [collection]
- uni_links_platform_interface 1.0.0 [flutter plugin_platform_interface]
- uni_links_web 0.1.0 [flutter flutter_web_plugins uni_links_platform_interface]
- universal_io 2.0.4 [collection crypto meta typed_data]
- url_launcher 6.0.12 [flutter meta url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- url_launcher_linux 2.0.2 [flutter]
- url_launcher_macos 2.0.2 [flutter]
- url_launcher_platform_interface 2.0.4 [flutter plugin_platform_interface]
- url_launcher_web 2.0.4 [flutter flutter_web_plugins meta url_launcher_platform_interface]
- url_launcher_windows 2.0.2 [flutter]
- uuid 3.0.5 [crypto]
- value_layout_builder 0.3.1 [flutter]
- vector_math 2.1.0
- win32 2.2.9 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.3.0 [collection meta petitparser]
- yaml 3.1.0 [collection source_span string_scanner]

@QuentinSc
Reply from flutterfire team member:
deobfuscation is a manual process. The PR mentioned makes obfuscated stack traces parsable by the user manually
With that said, you'll need to deobfuscate manually. Going ahead and closing this as WAI.


feat(dbm-services): 独立出mysql升级 mysqlcheck 步骤

关联研发信息
dev_branch: feat/separation_mysqlcheck_for_upgrade/#8604
target_branch: v1.5.0


[nbc:NBCSportsVPlayer] Corrected video URL (fixes issue #13873)

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Updated the extractor to use the correct video URL and replaced the broken tests - issue #13873.
Cheers and thank you!
Parmjit V.

@dstftw - Does this PR require any corrections?  I believe the fix for this issue is pretty straightforward.  Thanks!

@dstftw - Are any collaborators available for a first review of this PR?  Much appreciated!

@dstftw - The test suite has been updated as requested.  Please let me know if there are any further corrections that need to be made.  Cheers!

@dstftw - The duplicate test has been removed, please review at your convenience.  Thank you!

@dstftw - The test suite has been updated with the correct URLs, thanks for your patience.  Please let me know if there is anything else still outstanding for this PR.


[Code Style] automatic listener setup for componentWillMount & componentWillUnmount

If I want to handle some events, I need to register and unregister manually now
 componentWillMount() {
    SomeComponent.addEventListener('event', this._event);
  }
  componentWillUnmount() {
     SomeComponent.removeEventListener('event', this._event);
  }
  _event() {
     ...
  }

Very often we forgot to unregister from events listening (a notification on iOS) and it could lead to dangerous result.
The component could automatically unregister from events when its become inactive (gets unmounted)
Swift implementation - https://gist.github.com/jverkoey/dfa473635a810ab436d3
Some ideas for implementation, not perfect :)
componentLifeBindings() {
   return [ {SomeComponent, 'event', this._event},
            {View, 'move', this._hadleMovement}]
}

You can use mixins to manage lifecycle stuff like this (this is how timers are handled). Maybe @ericvicenti can provide more info?

Mixins are good for this, see react-timer-mixin for example.
Alternatively, you could use some kind of compositional technique like ES7 decorators or a component enhancing functions. For example, check out @johanneslumpe's blog post about adding a gesture decorator.

This might help. https://github.com/facebook/react-native/blob/8b93b99d4a769f86fffc95d65434f2f6a3fd827d/Libraries/Components/Subscribable.js
According to @ericvicenti from a previous issue...
"Subscribable.Mixin is something we use internally to make sure nobody forgets to unsubscribe to an emitter from a component on unmount. The mixin will automatically remove subscriptions added with this.addListenerOn"

Nice one @christopherdro :smile:

Thanks for answers! Great resources

@brentvatne still keep this open with all the solutions out there like Subscribable?

@browniefed - yeah I think those solutions are good, close seems appropriate!


fix retryable error logic and swallow initialization errors

match other SDKs by swallowing and logging initialization errors while returning a usable client instance
fix logic for retryable errors to check for 5xx errors

Current dependencies on/for this PR:

main

PR #58   👈

PR #62

This comment was auto-generated by Graphite.


Forms overhaul (including several components)

💡 What is the current behavior?

GitHub Issue Number: #
🆕 What is the new behavior?

🏁 Checklist
A pull request can only be merged if all of these conditions are met (where applicable):

[ ] 🦮 Accessibility (a11y) features were implemented
[ ] 🗺 Internationalization (i18n) - no hard coded strings
[ ] 📲 Responsiveness - components handle viewport changes and content overflow gracefully
[ ] 📄 Documentation was reviewed/updated (pnpm run docs)
[ ] 🧪 Unit tests were added/updated and pass (pnpm test)
[ ] 📸 Visual regression tests were added/updated and pass (Guide)
[ ] 🧐 Static code analysis passes (pnpm lint)
[ ] 🏗 Successful compilation (pnpm build, changes pushed)

👨💻 Help & support

/snapshots:approve --args=form-fields.e2e.ts

/release:pr

/release:pr

/release:pr