Options: Forget Character Data

Offer an option to forget all data about a selected character

Adding on to this: I leveled to 80 with tailoring, then dropped it. Now the concentration tracker still thinks I have tailoring. Need to purge this data when a profession is unlearned. Also, if you can point me to where in the savedvariables to manually do it myself, that would be good.

Most of the character related data can be found in CraftSimDB.crafterDB
its a table mapping from "crafterUIDs" aka e.g. "Player-Server" to their cached data
so I think if you delete those entries u dont need it should work


Develop

We should only merge develop to main when we have a working app (or version/milestone for release).

merge


change in font size

the font size are all different plz assign to make it more attractive

Please assign this issue to me.

i find it first so please assign me

hii @aslams2020  i believe i can do this task efficiently as i have a strong hold over css styling. could you please assign me this task under GSSoC24 extd.

this is my issue so assign me if you want to make it more attractive and responsive


README links may be dead or point to inappropriate code in the repo

There are chances that the links mentioned in the algorithm/DS table become dead or a code cross ([X]) may be pointing to a wrong URL.
A test for this is needed to prevent this in future PRs.

There is a related Bear which checks for dead links InvalidLinkBear you can check out its properties here https://coala.io/#!/languages

I think that having a custom script for this purpose would be better.

@singhpratyush Should we add Awesome_Bot to our Travis

I already checked it. But it won't satisfy our requirement of the correctness of link. I think having custom script would be better.


Feat request: Cconfiguration to allow use of chat gpt-4

Some folks have access to the new gpt-4 version of chat and it would be great to configure the app to allow us to use it

This is available under settings.
See https://github.com/cogentapps/chat-with-gpt/issues/44 for more information.


Subscriptions

Initial work on #113. Largely just a copy/paste/replace job from mutation → subscription.

is it already finished? please set WIP status if it is not ready

It's probably mostly finished. I've also started working on websocket transport for subscriptions, which may need some further changes. I've marked the PR as a draft in case I need to change more things.

Actually, let's just merge this right away. It might take a while to get the websocket transport working, and this will probably not need many changes.

i sound good. let merge your pull request before #112, because I did some refactoring there.
you can merge it. i renamed it


Globalnet: Capture fail-over statistics in active/passive HA

What happened:
This is similar to https://github.com/submariner-io/submariner/issues/722, but with Globalnet deployment.

Observations are captured in the following spread sheet:
https://docs.google.com/spreadsheets/d/1JsXsyRDDXkp6t55Gm-NP5EggWTyYi2yo27pyuDYwlpc/


Bump version up to 0.19.0.

Codecov Report

Merging #184 (26422bb) into main (04ffeaa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #184   +/-   ##
=======================================
  Coverage   96.44%   96.44%
=======================================
  Files          20       20
  Lines        2448     2448
  Branches      231      231
=======================================
  Hits         2361     2361
  Misses         87       87

Flag
Coverage Δ

unittests
96.44% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Prelaunch bugfixes 1

[x] main title spacing
[x] Too little spacing in Resources pages
[x] Information that should be bullet points are laid out like a paragraph
[x] Button link not working
[x] Difficult to get back on the website after we click Join our team button
[x] MORE

Looks like previews got disabled when the GitHub branch was renamed. Just re-enabled them. You might need to re-publish any PRs that don’t have previews.
…
On Feb 10, 2022, at 9:06 PM, sjpaige @.***> wrote:
@dylankershaw https://github.com/dylankershaw did something happen to the PR previews?
—
Reply to this email directly, view it on GitHub <#136 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ.
You are receiving this because you were mentioned.

@dylankershaw have I done it the right way? Not seeing it yet.

Ok yea looks like Amplify previews are buggy. I’m trying some stuff now and will update when I get it working again.

On Feb 11, 2022, at 2:40 PM, sjpaige @.***> wrote:
Looks like previews got disabled when the GitHub branch was renamed. Just re-enabled them. You might need to re-publish any PRs that don’t have previews.
… https://github.com/openseattle/clearviction/pull/136#
On Feb 10, 2022, at 9:06 PM, sjpaige @.***> wrote:
@dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw did something happen to the PR previews?
—
Reply to this email directly, view it on GitHub <#136 (comment) https://github.com/openseattle/clearviction/pull/136#issuecomment-1035887625>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ.
You are receiving this because you were mentioned.
@dylankershaw https://github.com/dylankershaw have I done it the right way? Not seeing it yet.
—
Reply to this email directly, view it on GitHub https://github.com/openseattle/clearviction/pull/138#issuecomment-1036700820, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJNPT7ZHP6B4KYNMFODU2WF4PANCNFSM5OFQUOQQ.
You are receiving this because you were mentioned.

Ok yea looks like Amplify previews are buggy. I’m trying some stuff now and will update when I get it working again.

On Feb 11, 2022, at 2:40 PM, sjpaige @.***> wrote:
Looks like previews got disabled when the GitHub branch was renamed. Just re-enabled them. You might need to re-publish any PRs that don’t have previews.
… https://github.com/openseattle/clearviction/pull/136#
On Feb 10, 2022, at 9:06 PM, sjpaige @.***> wrote:
@dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw did something happen to the PR previews?
—
Reply to this email directly, view it on GitHub <#136 (comment) https://github.com/openseattle/clearviction/pull/136#issuecomment-1035887625>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ.
You are receiving this because you were mentioned.
@dylankershaw https://github.com/dylankershaw have I done it the right way? Not seeing it yet.
—
Reply to this email directly, view it on GitHub https://github.com/openseattle/clearviction/pull/138#issuecomment-1036700820, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJNPT7ZHP6B4KYNMFODU2WF4PANCNFSM5OFQUOQQ.
You are receiving this because you were mentioned.

Ok cool I'll keep an eye to see when you have an idea of a fix.

Alright I think I have it working now. Had to create a new Amplify app for some reason.
Try closing and opening a new PR again.

On Feb 11, 2022, at 6:59 PM, sjpaige @.***> wrote:
Ok yea looks like Amplify previews are buggy. I’m trying some stuff now and will update when I get it working again.
On Feb 11, 2022, at 2:40 PM, sjpaige @.***> wrote:
Looks like previews got disabled when the GitHub branch was renamed. Just re-enabled them. You might need to re-publish any PRs that don’t have previews.
… #136 https://github.com/openseattle/clearviction/pull/136
On Feb 10, 2022, at 9:06 PM, sjpaige @.***> wrote:
@dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw did something happen to the PR previews?
—
Reply to this email directly, view it on GitHub <#136 https://github.com/openseattle/clearviction/pull/136 (comment) #136 (comment) https://github.com/openseattle/clearviction/pull/136#issuecomment-1035887625>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ https://github.com/notifications/unsubscribe-auth/AG5ALJKS5QUR4LEL4D7GIHLU2SKLZANCNFSM5ODCFSUQ.
You are receiving this because you were mentioned.
@dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw https://github.com/dylankershaw have I done it the right way? Not seeing it yet.
—
Reply to this email directly, view it on GitHub #138 (comment) https://github.com/openseattle/clearviction/pull/138#issuecomment-1036700820, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJNPT7ZHP6B4KYNMFODU2WF4PANCNFSM5OFQUOQQ https://github.com/notifications/unsubscribe-auth/AG5ALJNPT7ZHP6B4KYNMFODU2WF4PANCNFSM5OFQUOQQ.
You are receiving this because you were mentioned.
Ok cool I'll keep an eye to see when you have an idea of a fix.
—
Reply to this email directly, view it on GitHub https://github.com/openseattle/clearviction/pull/138#issuecomment-1036966610, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG5ALJMSDBHWLCMPZUABQ5LU2XEIXANCNFSM5OFQUOQQ.
You are receiving this because you were mentioned.

Cool I will try again.


Usage Logs Endpoint unsupported

The SDK does not appear to contain any methods to call the usage API:
https://adobedocs.github.io/analytics-2.0-apis/#/usagelogs/getUsageAccessLogs
https://www.adobe.io/apis/experiencecloud/analytics/docs.html#!AdobeDocs/analytics-2.0-apis/master/usage-logs.md

Hi @arobsco , thanks for raising up this feature request. I don't recall having seen these endpoints when we were working on the SDK.
We certainly can add them. We also welcome PRs, in case you would like to contribute!
cc @sarahxxu @sandeep-paliwal


Update French logbook with additional translations

@Aegyo Should be good on my part, let me know if ever I missed something


Add shapes for callouts

Use a similar technique to how we get the water mark - create a  png and then add the image at a specific location. See comments in #31 for more detail.

Still to do:

smooth out the polygon borders
eliminate overlaps between polygon and text and legend
move the legend to the bottom left while we're messing with component placement?
switch polygon color to something gentler, maybe one of the grays in the timeline clock

For 3, that might be tricky because of Alaska's tail, but we could do it if we added a bit more room between the edge of the map and the edge of the figure

For today, we will try to do 1 smooth out the polygon borders.

Alison will do 2 by moving the california callout text

mwernimont did #1 and #4, unloaded images in slack channel


Forum offline

The forum is offline until the DNS records have been updated.
New address: http://forum.gtnewhorizons.com
I still have to make a few changes to the backend before it can be used again, but you can already bookmark the link

OK

@Teteros
Please check your DNS config.
The A-Record for forum.gtnewhorizons.com is still pointing to <IP_ADDRESS>.

Cloudflare is just being slow...

Seems <IP_ADDRESS> is Cloudflare's IP.
After disabling it for the forum subdomain, it points to <IP_ADDRESS> directly.
Though <IP_ADDRESS> is still the "It Works!" page?

you can remove the www.forum. entry. Just forum. is enough.
Oh and by the way, forum back online :)

Shht, MyBB has a neat portal function too:
http://forum.gtnewhorizons.com/portal.php
totally worth the try :P

Cant log in in the Forum any more

Forgot your password? Works for me.. Front and Backend oO

Maybe something with cookies. I put my Password inside manually in and it works

You come inside the TS?

Ah, yes. The cookie domain has changed, obviously. So if you have issues logging in, clear your browser cache (Ctrl+F5 should be enough)


Bug

i, thanks for the plugin,
But i always got this error message http://imgur.com/a/lstIi , randomly

Hi,
when do you get the error? Does it somehow affects the plugin, like does the plugin stop working after the error? What TV are you using?
Greets

No error at all, since the last update!
Everything is working! No permission request anymore after adding the keyfile
Great! Thank you
My tv is a LG 49uhv750
Best regards
Nicola

Il giorno 12 ago 2017, alle ore 22:37, Marcin<EMAIL_ADDRESS>ha scritto
Hi,
when do you get the error? Does it somehow affects the plugin, like does the plugin stop working after the error? What TV are you using?
Greets
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Good to hear! Thanks for the info!


Java: Exception is thrown when saveInformationAsync is called on a non existent collection

com.microsoft.semantickernel.memory.MemoryException: Attempted to access non-existent collection: foo
        at com.microsoft.semantickernel.memory.VolatileMemoryStore.getCollection(VolatileMemoryStore.java:242)
        at com.microsoft.semantickernel.memory.VolatileMemoryStore.upsertAsync(VolatileMemoryStore.java:67)
        at

To verify and fix or close as necessary.

Fixed by PR #2306


Introduction to Artificial Narrow Intelligence (ANI)

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of article
Introduction to Artificial Narrow Intelligence
Introduction paragraph (2-3 paragraphs):
Artificial intelligence (AI) is one of the most popular term used in  computer science recently. This article discusses one of the classifications of Artificial Intelligence namely Artificial Narrow Intelligence (ANI).
Artificial Narrow Intelligence is also known as WEAK AI. This is an AI that has narrow rangeability holding a perspective that executes specific focused tasks, without the ability to the self -expand mechanism. Narrow AI machines intelligence is achieved through Natural Language Processing concept. This concept is mostly functional in chatbots and other domains where machines are programmed to interact with humans using text recognition or speech.
Key takeaways:

What is Artificial narrow intelligence
Different types of narrow intelligence
The differences between general AI and Narrow AI
Limitations of Narrow intelligence
key examples of Narrow AI

References:
N|A
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

This is an interesting topic. Can we take up an interesting problem or an application where weak ai is used and then use that to explain the concepts. A Google search on weak ai results in similar looking articles with similar content.
Do let us know about an interesting problem or application that you will consider for the purposes of the article.
@hectorkambow

@domiwanja

@domiwanja


Fix goroutine and memory leaks in engine

Fixes: https://github.com/dagger/dagger/issues/6719
See individual commit messages for explanations.
Running the full TestModule suite locally now shows RSS maxing out around 1GB (still high-ish but much more reasonable than 6GB). And most importantly, whereas previously the engine's RSS stayed high after the test suite ended (it stuck around 2-3 GB RSS), now the RSS drops down to reasonable 600MB afterwards, with pprof showing reasonable usage mostly from buildkit's in memory cache metadata:
File: dagger-engine
Type: inuse_space
Time: Feb 27, 2024 at 10:00am (PST)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top
Showing nodes accounting for 38.15MB, 58.54% of 65.17MB total
Showing top 10 nodes out of 306
      flat  flat%   sum%        cum   cum%
      11MB 16.88% 16.88%    12.50MB 19.18%  github.com/moby/buildkit/cache/metadata.newStorageItem.func1
    5.50MB  8.44% 25.32%     5.50MB  8.44%  github.com/moby/buildkit/cache.(*cacheRecord).ref
       5MB  7.67% 33.00%        5MB  7.67%  github.com/moby/buildkit/cache/metadata.(*StorageItem).setValue
    3.50MB  5.37% 38.37%     3.50MB  5.37%  github.com/moby/buildkit/cache.(*cacheRecord).layerDigestChain
       3MB  4.60% 42.97%        3MB  4.60%  runtime.malg
    2.55MB  3.92% 46.89%    20.06MB 30.77%  github.com/moby/buildkit/cache.(*cacheManager).getRecord
    2.29MB  3.52% 50.41%     2.29MB  3.52%  github.com/moby/buildkit/solver/pb.(*Op).Marshal
       2MB  3.07% 53.48%     2.50MB  3.84%  github.com/moby/buildkit/cache/metadata.NewValue
    1.75MB  2.69% 56.16%     1.75MB  2.69%  github.com/moby/buildkit/util/tracing/detect.(*TraceRecorder).ExportSpans
    1.55MB  2.37% 58.54%     1.55MB  2.37%  google.golang.org/grpc/internal/transport.newBufWriter

Also, previously there were 20000+ goroutines laying around after the test suite was done. Now there's only 21.

Nice :tada: Didn't get a chance to review this before merging, but LGTM :tada:
Also fixes https://github.com/dagger/dagger/issues/6604.


Add AES-CMAC mode

Based on RFC 4493 algorithm description. Verified against the data in NIST Special Publication 800-38B.

Hi @gruzdev and thanks for contributing this lovely additional feature :D
I will review it a bit, but it seems legit and merge-able right off the bat :+1:
Again, thanks for your interest in improving this project :)

I've added a few comments where I think your code could be improved ever so slightly.
I would still like to hear from @DamonHD w.r.t. implications for the 8-bit guys, but I think this change will be an improvement for those chips as well.

I've added a few comments where I think your code could be improved ever so slightly.
I would still like to hear from @DamonHD w.r.t. implications for the 8-bit guys, but I think this change will be an improvement for those chips as well.

Hi @kokke! I tried to keep general look and feel of the library while working on the patch. Implemented CMAC algorithm recalculates two subkeys on every call. It's not cpu-wise but allows me to avoid context structure modification. The implementation might be quite hard to read and compare to RFC text. It's the result of my attempts to reduce memory footprint .
Feel free to discard the request if something still does not feel right. Thanks for your work on this project!

@gruzdev you have kept the code very close to my ideals 👍
I don’t think it matters too much with the recalculation, but I would need to run some benchmarks to be sure.
I think the code looks quite good in its current form.
I just need more time to review and brush up on CMAC technicalities :)

One thing that IMO is missing is the ability to compute the combined CMAC of a series of buffers, so it would be used something like this:
AES_CMAC_init(ctx, state)
AES_CMAC_add(ctx, state, data, datalen)
AES_CMAC_add(ctx, state, data2, datalen2)
AES_CMAC_add(ctx, state, data3, datalen3)
AES_CMAC_finalize(ctx, state, output)
We can't do this with the existing AES_CMAC_generate() implementation as it clears the key state each time it is invoked.
Thanks!


Text changes of the home page header

Reason (Why?)
The information in the header should be concise and advertise the website.
Solution (What?)
Change the main text in the header from:

Das schnelle Suchportal für Freiwilligenarbeit

To:

Das Portal für Freiwilligenarbeit

Below that, add a subtitle of how many job offers there are on the website at that moment:

Aktuell xxxx nationale und xxxx internationale Stellenangebote zur Auswahl

xxxx should be the respective number of job offers in the national/international section. Also add into that subtitle the icons for national and international (i.e. the germany flag and the globe). The numbers should be updated with each crawling of data.
Out of scope
The result page or any page that is not the home page. Mobile view.

Do you know, how the query for this data should look like?

Do you know, how the query for this data should look like?

The following two queries should return the number of national and international posts.
Number of national posts
{
    "track_total_hits": true,
    "query": {
        "bool": {
            "must_not": {
                "term": {
                    "categories": "international"
                }
            }
        }
    }

Number of international posts
{
    "track_total_hits": true,
    "query": {
        "bool": {
            "must": {
                "term": {
                    "categories": "international"
                }
            }
        }
    }
}

Example response
Only the number of posts is returned via the following path: /api/_search/posts/?filter_path=hits.total
{
    "hits": {
        "total": {
            "value": 22306,
            "relation": "eq"
        }
    }
}

@KaiDrieHda ist this like expected?

Is currently just dummy data.

When the window is smaller and the text is splitted into two lines, it looks weird because all lines have the same width.
Could you try something like that? The asymmetry looks much better.
Please make sure that "xxx (flag) nationale" and "xxx (flag) internationale" should allways be together without a linebreak. The linebreak should be after "und" or after "nationale".

@KaiDrieHda
Is this ok?

@KaiDrieHda
Is this ok?

Perfect!


Implemented password hashing using bcrypt

Please review this implementation, I can make changes where needed.

Per SEI CERT C Coding Standard This uses bcrypt is a special type of hashing package designed solely for password hashing to hash the admin password. VSP operators can start vspd without a password in the config or commandline after first initiating vspd with an admin password. VSP operators update admin password when they provide it via config or commandline.


spelling corrected - Drupa1 to Drupal

fixed an embarrassing spelling error that used a 1 (one) instead of l (ell) for the last character in the name of CMS app Drupal (not Drupa1)

fixed spelling error for CMS app name Drupal (not Drupa1)

Hi @DanStevensonMSFT, we use a different repo to create PRs. I created a PR last Friday to correct this issue: https://github.com/MicrosoftDocs/OfficeDocs-MicrosoftSearch-pr/pull/1578. If that's okay, can I close this one?

Yes, of course - I was just clicking the path of least resistance. Will that typo get corrected, then?

From: Daniela Bonilla Montero @.>
Sent: Monday, October 7, 2024 9:15 AM
To: MicrosoftDocs/OfficeDocs-MicrosoftSearch @.>
Cc: Dan Stevenson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-MicrosoftSearch] spelling corrected - Drupa1 to Drupal (PR #336)
Hi @DanStevensonMSFThttps://github.com/DanStevensonMSFT, we use a different repo to create PRs. I created a PR last Friday to correct this issue: MicrosoftDocs/OfficeDocs-MicrosoftSearch-pr#1578https://github.com/MicrosoftDocs/OfficeDocs-MicrosoftSearch-pr/pull/1578. If that's okay, can I close this one?
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-MicrosoftSearch/pull/336#issuecomment-2397359429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANBAZKLBA2ZBM4DVE22Y46DZ2KXS7AVCNFSM6AAAAABPLEEGE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXGM2TSNBSHE.
You are receiving this because you were mentioned.Message ID: @.***>

Got it. Yes, @DanStevensonMSFT, the typo will be fixed in this PR: https://github.com/MicrosoftDocs/OfficeDocs-MicrosoftSearch-pr/pull/1578. Thanks!


Reporting Ease

Question -
Where will be able to report users? Only in the 'alliance' (for lack of a better name) server, or in any server

In any server that has added the bot can report users, and ban them. The bot will also make it possible to ban users by command (this will be the easiest way to report bans).
 But not sure how to handle that.


feat/mod/fix: buffers: Texture Format Rewrite

Clarify which pixel formats and types are associated with different image formats
Clarify which formats are supported in custom images
Add missing documentation for R3_G3_B2
Add notes about minimum OpenGL versions or required extensions for some formats and pixel types

Should the page be renamed to Image Format since that's what OpenGL calls it?


ERROR decrypt chromium cookie error err="cipher: message authentication failed"  ( Chrome 128.0.6613.138 )

Describe the bug
Running HackBrowserData in the latest version Chrome 128.0.6613.138 will prompt ERROR decrypt chromium cookie error err="cipher: message authentication failed
It should be that the value encryption and decryption method of the cookie in the new version of Chromium has been modified, resulting in the failure of value decryption.
For your reference:
https://security.googleblog.com/2024/07/improving-security-of-chrome-cookies-on.html

Log Output
2024/09/11 13:57:51 WARN find browser success browser=chrome_default
2024/09/11 13:57:51 WARN find browser success browser=chrome_def
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser="Chrome Beta"
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=Opera
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=OperaGX
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=Vivaldi
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=QQ
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=Chromium
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=CocCoc
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=Brave
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=DC
2024/09/11 13:57:51 WARN find browser failed, profile folder does not exist browser=Sogou
2024/09/11 13:57:52 WARN find browser success browser=microsoft_edge_def
2024/09/11 13:57:52 WARN find browser success browser=microsoft_edge_default
2024/09/11 13:57:52 WARN find browser failed, profile folder does not exist browser=Yandex
2024/09/11 13:57:52 WARN find browser failed, profile folder does not exist browser=360speed
2024/09/11 13:57:52 WARN find browser failed, profile folder does not exist browser=Firefox
2024/09/11 13:57:52 Written 1769472 Bytes to Destination Done.
2024/09/11 13:57:52 INFO get master key success browser=chrome_default
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:52 ERROR decrypt chromium cookie error err="cipher: message authentication failed"
2024/09/11 13:57:53 WARN export success filename=chrome_default_extension.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_history.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_password.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_cookie.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_bookmark.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_download.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_sessionstorage.csv
2024/09/11 13:57:53 WARN export success filename=chrome_default_localstorage.csv
2024/09/11 13:57:53 INFO get master key success browser=chrome_def
2024/09/11 13:57:53 WARN export success filename=chrome_def_sessionstorage.csv
2024/09/11 13:57:53 INFO get master key success browser=microsoft_edge_def
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_def_sessionstorage.csv
2024/09/11 13:57:53 Written 360448 Bytes to Destination Done.
2024/09/11 13:57:53 INFO get master key success browser=microsoft_edge_default
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_cookie.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_extension.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_password.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_sessionstorage.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_localstorage.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_history.csv
2024/09/11 13:57:53 WARN export success filename=microsoft_edge_default_download.csv
2024/09/11 13:57:53 INFO compress success

Desktop (please complete the following information):
Select the operating system(s) you are using:

[x] Windows

[ ] macOS

[ ] Linux

OS Version: Windows 11

OS Architecture: 64-bit

Browser Name: Chrome

Browser Version: 128.0.6613.138

if anybody has information on v20 please message me or reply cus i got some questions regarding the new security being rolled out, this is a new security measure which will be rolled out, the v20 values will only be decryptable by the "same application"


Extending jsonreport.py to also include all branch attributes

The current jsonreport does not include the attributes for covered_branches and missing_branches.
This PR extends jsonreport.py such that it includes these attributes; it also updates test_json.py to account for these newly-dumped attributes.
Current test status:
  py27: commands succeeded
SKIPPED:  py35: InterpreterNotFound: python3.5
  py36: commands succeeded
SKIPPED:  py37: InterpreterNotFound: python3.7
SKIPPED:  py38: InterpreterNotFound: python3.8
SKIPPED:  py39: InterpreterNotFound: python3.9
SKIPPED:  pypy2: InterpreterNotFound: pypy2
SKIPPED:  pypy3: InterpreterNotFound: pypy3

@nedbat any thoughts on this? This seems like a great change, as it allows us to get access to data that would otherwise be missing from the json report.

Codecov Report

Merging #966 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #966   +/-   ##
=======================================
  Coverage   94.10%   94.10%
=======================================
  Files          86       86
  Lines       12107    12107
  Branches     1212     1212
=======================================
  Hits        11393    11393
  Misses        580      580
  Partials      134      134

Impacted Files
Coverage Δ

coverage/jsonreport.py
100.00% <ø> (ø)

tests/test_json.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

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

Thanks, I'll add the fields to the individual files also.

This is available in 5.1: https://pypi.org/project/coverage/5.1/


Namespace/mosaic metadata views - problem with updating

Steps (metadata creation):

Create namespace
Add metadata to created namespace
Wait for transaction confirmation (without switching view)

Result: After transaction confirmation, new metadata is not available to view. You have to switch views and go back to see new metadata.
Steps (metadata edition):

Edit existing namespace metadata value
Wait for transaction confirmation (without switching view)

Result: After transaction confirmation, we can still see the old metadata value. You have to switch views and go back to see the new value.
Video: https://share.getcloudapp.com/bLuxNzwN
The same problem is with the creation/edition of mosaic metadata.

Fixed in https://github.com/symbol/desktop-wallet/pull/1839


Match device serials starting with bc- or hio-

Due to the recent rebranding, the logic that automatically selects a
core module if only one is attached to the host stopped working (newer
core modules have hio-core-module instead of bc-core module in the
serial). This patch fixes the problem.

Thx


执行python3 run.py t报错

Traceback (most recent call last):
File "run.py", line 24, in
from config.emailConf import sendEmail
File "/opt/12306-master/config/emailConf.py", line 4, in
import TickerConfig
File "/opt/12306-master/TickerConfig.py", line 44
TICKET_PEOPLES = [“xxx”]

TICKET_PEOPLES要填乘车人名字


Implement creating a proposal with proxy account UI

figma link
https://www.figma.com/file/vqpglMGW8psHKB00eIVDUV/OpenSquare?node-id=3382%3A15604
preview

Originally posted by @Popoulosss in https://github.com/opensquare-network/collaboration/issues/355#issuecomment-982391027

[ ] Display balance whether it is enough or not

[ ] Fix UI style

[ ] Fix margin


feat: implement GET /issues/ and /issues/{id} and /device/{deviceId}/open_issues

closes #11
closes #13
closes #19

Summary by CodeRabbit

New Features

Enhanced issue tracking and management by introducing new tables to list unresolved and unexempted issues for devices failing checks.
Improved visibility by adding functionality to retrieve issues related to a specific device using its ID.

Bug Fixes

Corrected a description typo in the "will_block_at" column to accurately reflect the device blocking timestamp.

Documentation

Updated documentation with examples and detailed information on new tables and issue management capabilities.

Refactor

Streamlined fetching and managing of issues and device information with new methods and functions to enhance API efficiency and usability.

@coderabbitai review


Custom value of empty option for select

Hello again. Fixes you did for select are working really great. However, I realised there is another issue related to select.
As we talked in #110 there were some issues with treating falsy values. When object attribute is a null it is converted to undefined. Empty option & placeholder works fine.
But as I pointed in #110, I need to nullify object attribute with null or empty string. Because when I select blank option the object atrribute is set to undefined and this undefined attribute is not sent via my request. And since undefined attribute is not present in params, my backend does not know it needs to be set to null.
You wrote that empty string will solve my problem. It did before your changes, but this solution no longer works. When I change $scope.emptyOption[$scope.valueAttribute] to null or empty string then empty option is duplicated.

Sorry to hear that this issue is still giving you trouble, Palo. It's kind of a difficult edge case to handle.

Because when I select blank option the object atrribute is set to undefined and this undefined attribute is not sent via my request. And since undefined attribute is not present in params, my backend does not know it needs to be set to null.

Why is the undefined value not being sent with your params? Is there a simpler solution to this (just updating your application code) than changing selectField?

I tried to fix it using interceptors but it is more complicated then it looks like.
First option using interceptors - if attribute is undefined, I have to convert it to null value or empty string. But I do not want to do this for each attribute of object (this will cause lot of other issues in backend part).

I'm using https://github.com/FineLinePrototyping/angularjs-rails-resource plugin to handle API calls and this is how it works. Basically it is good enough, because as I said I do not want to send each undefined attribute via request. But I want to send undefined/null/empty string values from selects...
I understand this "issue" is edge case, but I think lot of people can find this useful. I tried to work on this, but my JS knowledge is not good enough to fix something like this.
If you'll find some spare time to work on this - I'll be really grateful! But if you won't have time - it's okay, no hard feelings :-).

Ah, I understand a little better now. Thanks for elaborating.
I'll leave the issue open then and try to get to it as soon as I can.
Angular's ngSelect/ngOptions are quickly becoming my least favorite
components to work with though. I wish I could opt-out of using them and
just manage this portion of the DOM myself... :)
On Monday, July 13, 2015, Palo Delinčák<EMAIL_ADDRESS>wrote:

I tried to fix it using interceptors but it is more complicated then it
looks like.
First option using interceptors - if attribute is undefined, I have to
convert it to null value or empty string. But I do not want to do this for
each attribute of object (this will cause lot of other issues in backend
part).

I'm using https://github.com/FineLinePrototyping/angularjs-rails-resource
plugin to handle API calls and this is how it works. Basically it is good
enough, because as I said I do not want to send each undefined attribute
via request. But I want to send undefined/null/empty string values from
selects...
I understand this "issue" is edge case, but I think lot of people can find
this useful. I tried to work on this, but my JS knowledge is not good
enough to fix something like this.
If you'll find some spare time to work on this - I'll be really grateful!
But if you won't have time - it's okay, no hard feelings :-).
—
Reply to this email directly or view it on GitHub
https://github.com/bvaughn/angular-form-for/issues/141#issuecomment-120891254
.

Oh, great! Yes, I know I'm little bit annoying with my issues... I'm sorry about that and I definitely owe you some beers! So when I'm back in SF, I'll bring you some beers from Europe :beer:!

European beer sounds good ;) thanks
On Monday, July 13, 2015, Palo Delinčák<EMAIL_ADDRESS>wrote:

Oh, great! Yes, I know I'm little bit annoying with my issues... I'm sorry
about that and I definitely owe you some beers! So when I'm back in SF,
I'll bring you some beers from Europe [image: :beer:]!
—
Reply to this email directly or view it on GitHub
https://github.com/bvaughn/angular-form-for/issues/141#issuecomment-121032911
.

Hello Brian, any news on this?

Hiya. No news. Haven't forgotten about this issue but haven't had the bandwidth to work on it yet. Sorry mate, things have been busy.

Ah, good news. I have an idea for a way to approach this that I think should work. Hopefully I'll be able to get to it this evening or tomorrow.

I wonder if you would be willing to test this for me using either the diff below or this updated plunker.
diff --git a/dist/form-for.js b/dist/form-for.js
index 9c004d8..394bbd8 100644
--- a/dist/form-for.js
+++ b/dist/form-for.js
@@ -1636,7 +1636,8 @@ var formFor;
                 // Otherwise the Angular select directive will generate an additional empty <option> ~ see #110
                 // Angular 1.2.x-1.3.x may generate an empty <option> regardless, unless the non-selection is undefined.
                 if ($scope.model.bindable === null || $scope.model.bindable === undefined || $scope.model.bindable === '') {
-                    $scope.model.bindable = undefined;
+                    //$scope.model.bindable = undefined;
+                    $scope.emptyOption[$scope.valueAttribute] = $scope.model.bindable;
                 }
                 $scope.bindableOptions.splice(0);
                 if (!$scope.model.bindable || $scope.allowBlank) {
diff --git a/dist/form-for.min.js b/dist/form-for.min.js
index c3c127c..6d187d9 100644
--- a/dist/form-for.min.js
+++ b/dist/form-for.min.js
@@ -1,3 +1,4 @@
-angular.module("formFor",[]);var formFor;!function(e){var t=function(){function e(){this.restrict="A"}return e.prototype.link=function(e,
-e[e.COLLECTION_MAX_SIZE="COLLECTION_MAX_SIZE"]="COLLECTION_MAX_SIZE",e[e.COLLECTION_MIN_SIZE="COLLECTION_MIN_SIZE"]="COLLECTION_MIN_SIZE"
+angular.module("formFor",[]);var formFor;!function(e){var t=function(){function e(){this.restrict="A"}return e.prototype.link=function(e,
+
+!function(e){!function(e){e[e.COLLECTION_MAX_SIZE="COLLECTION_MAX_SIZE"]="COLLECTION_MAX_SIZE",e[e.COLLECTION_MIN_SIZE="COLLECTION_MIN_SI
 //# sourceMappingURL=form-for.min.js.map
\ No newline at end of file
diff --git a/dist/form-for.min.js.map b/dist/form-for.min.js.map
index b619d54..376d1ce 100644
--- a/dist/form-for.min.js.map
+++ b/dist/form-for.min.js.map
@@ -1 +1 @@
-{"version":3,"file":"form-for.min.js","sources":["form-for.js"],"names":["angular","module","formFor","AriaManager","this","restrict","pr
\ No newline at end of file
+{"version":3,"file":"form-for.min.js","sources":["form-for.js"],"names":["angular","module","formFor","AriaManager","this","restrict","pr
\ No newline at end of file
diff --git a/source/directives/select-field.ts b/source/directives/select-field.ts
index c7c2079..20f2e42 100644
--- a/source/directives/select-field.ts
+++ b/source/directives/select-field.ts
@@ -295,7 +295,8 @@ module formFor {
         if ($scope.model.bindable === null ||
             $scope.model.bindable === undefined ||
             $scope.model.bindable === '') {
-          $scope.model.bindable = undefined;
+          //$scope.model.bindable = undefined;
+          $scope.emptyOption[$scope.valueAttribute] = $scope.model.bindable;
         }

         $scope.bindableOptions.splice(0);

Note that this fix requires Angular 1.4.x. (1.3.x had some issues and regressions with select menus that I'm not interested in patching around.)

I'm feeling pretty good about this change so I'm going to move forward with it. Reach out to me with any questions or concerns.

The fix for this issue has been released in version 4.1.1.
Please remember that Angular 1.4.x is strongly suggested to avoid select field issues.

Hey, thanks for your time here!
I'm not sure if I understand how it works. Because when you change (in your Plunker) 6) from value 4 to empty value - it becomes undefined. And it should become null or empty string as I wrote in comments above.
Should I modify $scope.emptyOption[$scope.valueAttribute] and change it to null?
And also when I change 7) to some option and then to empty value it becomes empty string and not undefined as in other cases.

This change sets the value of the empty option to be equal to the
initially-selected value (if that value is falsy). This seemed to be the
only easy way to satisfy your feature request and work within
ngSelect/ngOption limitations.
As I understood your initial request, this should enable you to use null or
empty string.
Does this not work for you? And if not, why?
On Monday, August 3, 2015, Palo Delinčák<EMAIL_ADDRESS>wrote:

Hey, thanks for your time here!
I'm not sure if I understand how it works. Because when you change (in
your Plunker) 6) from value 4 to empty value - it becomes undefined. And
it should become null or empty string as I wrote in comments above.
Should I modify $scope.emptyOption[$scope.valueAttribute] and change it
to null?
And also when I change 7) to some option and then to empty value it
becomes empty string and not undefined as in other cases.
—
Reply to this email directly or view it on GitHub
https://github.com/bvaughn/angular-form-for/issues/141#issuecomment-127290256
.

Unfortunately, it does not work for me. For example 6) from your Plunker - it has preselected value 4 and when I change it to empty option - then I need to update ng-model with null/empty string and not with undefined.
And why? As I wrote earlier - undefined values are not sent in my requests and without this I can't nullify attribute in my backend.

I see. I'm sorry that this solution doesn't work for you. I guess I misunderstood what you were initially saying. I don't have a lot of extra time these days to devote to formFor and it's easy to lose context of more subtle issues like this when I'm only checking in every week or so.
I'll re-open this issue but I'm not going to be able to commit to fixing it by any specific time. I'd welcome contributions (from you or someone else) though if you'd be willing to take a shot at it. :)

Release 4.1.3 is available with your fix. Thanks again for your contribution! :)


Fix HotkeysOverrideProps to be optional

Currently TS will complain that only and except props are required when using ObserveKeys or IgnoredKeys

Quit right, @chipta, these attributes are supposed to be optional.


Image storage

Where are the images stored in the DB, on disk?

The package expands the functionality of spatie/laravel-medilibrary
Images on disk, info about images in DB

U need add required library - spatie/laravel-medilibrary


Value, Object, Any renamings

Looking at the API docs makes it clear that the traits really want to have the names Value and Object. And I came up with the "SomeObject" nomenclature for the root of the Object type hierarchy. So there should be a consistent nomenclature for root types in the type hierarchy, like SomeValue and SomeObject. I'm not in love with Some- as the prefix, so maybe we can come up with something better.
Also, neon::buffer should get moved under neon::value. Should we mirror the type hierarchy in a module hierarchy? Like neon::value::object::{Array, Object} etc, and neon::value::object::typed_array::Uint8Array etc?

A set of constraints I think are worth trying to satisfy in the naming:

avoid painful collisions with common Rust abstractions, in particular Result and String
different names for Object type vs Object trait
different names for Value type vs Value trait
any boilerplate prefixes of names should be short
naming convention for value tags should hew closely to JS naming conventions (e.g. SomeObject isn't great since it's not a familiar JS convention)

Here's a proposed set of names. I think I'll try this out in a PR.
Result

neon::vm::VmResult
neon::vm::JsResult

JS Values

neon::js::JsArray
neon::js::JsBoolean
neon::js::JsFunction
neon::js::JsInteger
neon::js::JsNull
neon::js::JsNumber
neon::js::JsObject
neon::js::JsString
neon::js::JsUndefined
neon::js::JsValue

JS Traits

neon::js::Object
neon::js::Value

JS Typed Arrays

neon::js::binary::JsUint8Array

JS Errors

neon::js::error::JsError

An alternative would be to go ahead and call them e.g. neon::js::String and recommend referring to them with qualified paths like js::String, but then we'd have to come up with alternative names for the Object and Value traits. The Value trait could maybe be Js, but what about Object?

It would also be nice to have a specialized version of v8::Buffer that is used to pack / unpack a Box pointer.  Buffer::new allows you to specify a raw pointer and a callback for a destructor.
This way we could have way to pass structs back and forth across the boundary. Simple example with explicit bindings:
https://github.com/kjvalencik/hello-rust-js/blob/0c00f116862c3c2d26a5bfcf5101004dfe0b8e8c/src/binding.cc#L16-L19
https://github.com/kjvalencik/hello-rust-js/blob/0c00f116862c3c2d26a5bfcf5101004dfe0b8e8c/src/lib.rs#L29-L31

@kjvalencik v8::External is the more "correct" way to pass something like that around.

@Qard Would v8::Persistent be a good option to have a GC callback to free?

@Qard What is the correct way to get a GC callback to free the external resource on v8::External?


chore(starknet-mempool): update gas price threashold to fix main

This change is

#2097  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


[enhancement] Update dependencies

Hi,
Here is a simple pull request to update dependencies of the project. This pull request includes:

Added rimraf module to deep delete a directory on Windows (and so fix the test command of the project)
Updated Rollup plugins for deprecated ones.

rollup-plugin-commonjs --> @rollup/plugin-commonjs
rollup-plugin-json --> @rollup/plugin-json
rollup-plugin-node-resolve --> @rollup/plugin-node-resolve

WARNING: I tried to fix everything, but a module (browserify-fs) includes a lot of dependencies with security problems (3 included 1 with high danger). I didn't find any alternative, so any feedback about it is welcome.

Can this be merged?

Yes it can but it still have all browserify-fs security issues that I can't resolve


analytics: Only update daily stats on day boundaries, and other housekeeping.

I basically just removed the documentation on the CountStat object, since I think the code is more self-explanatory now than it was before. I can write something though if you think it would help.

Automated message from Dropbox CLA bot
@rishig, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @rishig!

I think with the documentation, we'll learn more when we have someone next try using it what is missing.  It's possible we should just mention the definition is documented in the docs?  Idunno.

cool. Leaving as is for now, then.


Trigger build based on PR comment

Acceptance criteria
Given a PR opened
When the user is commenting on the PR and entering a specific command
Then he should be able to trigger a build immediately
Example
@hans-landa build now

Idea 1 💡
@hans <projectId> <workflow> [delay: '1h' | 'tonight' | '1w']
For the delay properties we don't have to add it now. It will be retro compatible API anyway.
Idea2
Based on the idea 1, the projectId and the workflow could be quite painful to remember. It would probably be better to alias them:
@hans buildQA [delay: '1h' | 'tonight' | '1w']
It would be nice to be able to use this alias to trigger multiple builds (ios & android for example)

I like the idea 2 better.
IMO the goal would be to bypass the triggers from the GitHub actions and trigger it manually for the current PR.

wef

test

Entry workflow
   workflows:
            - :
              name: buildQA
              bitrise_app_slug: ca04e0425716e1ce
              bitrise_build_trigger_token: Gs7vZtsWEz-UZ_vNdNxDIA
              build_on: command
            - :
              name: buildQA
              bitrise_app_slug: ca04e0425716e1ceff
              bitrise_build_trigger_token: Gs7vZtsWEz-UZ_vNdNxDIAaaa
              build_on: command
            - :
              name: primary
              bitrise_app_slug: ca04e0425716e1ce
              bitrise_build_trigger_token: Gs7vZtsWEz-UZ_vNdNxDIA
              build_on: [commit, command]

We need to have a function that gets the parameters from the object and validate it


Make sure the range returned by PrepareRenameRequest always contains the position from which the rename was initiated

VS Code rejects the placeholder name returned by the PrepareRenameRequest. When initiating rename on x in the following, this means that VS Code picks its own internal symbol name as the placeholder text, opening the rename textbox with x.
func foo(
  x: Int
) {}

Users then enter y in the expectation to rename only the parameter but sourcekit-lsp expects a function name and thus renames foo to y(x:), which is unexpected.
rdar://125551489

@swift-ci Please test

@swift-ci Please test Windows


Roll Engine from 712f619737f1 to fd87d4e427e4 (8 revisions)

https://github.com/flutter/engine/compare/712f619737f1...fd87d4e427e4
2020-07-01<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 1cpN9... to avEUl... (flutter/engine#19441)
2020-07-01<EMAIL_ADDRESS>Roll Skia from 400ba22f4564 to 16ee98ddeda3 (4 revisions) (flutter/engine#19440)
2020-07-01<EMAIL_ADDRESS>Roll Dart SDK from 22da8934ac8b to bec128612c03 (16 revisions) (flutter/engine#19436)
2020-07-01<EMAIL_ADDRESS>Roll Skia from 492558a10db6 to 400ba22f4564 (3 revisions) (flutter/engine#19437)
2020-07-01<EMAIL_ADDRESS>Roll Skia from 1e6460d552f7 to 492558a10db6 (2 revisions) (flutter/engine#19434)
2020-07-01<EMAIL_ADDRESS>Revert unintended change (flutter/engine#19435)
2020-07-01<EMAIL_ADDRESS>Update scenario UI screenshoots (flutter/engine#19421)
2020-07-01<EMAIL_ADDRESS>Roll Skia from 746460e25a1e to 1e6460d552f7 (8 revisions) (flutter/engine#19429)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from 1cpN9LXjoQj- to avEUlBH4tSg6
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


[build] Save build artifacts on GH-CI runs

Save logs for failed integration tests on gh-ci

Resolves #178
How was this PR tested?

Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Thanks a lot, @nisargthakkar and @FelixGV!


Native AOT - Microsoft.Data.SQLite crashing

Hello
I see this issue here, not sure if related  https://github.com/dotnet/efcore/issues/29725
I am using Visual Studio 2022 LTSC 17.4.4, targeting net7.0-windows
I ran "dotnet add package Microsoft.Data.Sqlite.Core --version 8.0.0-preview.7.23375.4"  to install the package.  perhaps this is a bad version to use in my situation?
I have a simple c# app that uses Microsoft.Data.SQLite, the SqliteConnection and SqliteCommand methods
It works 100% fine when built without AOT.
However when I publish it as AOT, I get an exception / crash.  Exception code: 0x4b1b53b5  which seems meaningless on first glance
Is there some way to get more information about the crash or solve this issue?
Thank you

Closing as this belongs in https://github.com/dotnet/efcore.


Needs updating to include .NET Core 2.1 HttpClientFactory

Additionally, I have not seen much documentation that includes the method encapsulated HttpClient configuration pattern whose DI setup looks like.
'''
services.AddHttpClient<IMyService, MyServiceImplementation>( configuration => ...)
'''

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

ID: 3bfcc1a8-ddda-810c-17b0-56a506045d67
Version Independent ID: 5415878b-e60b-5433-7b4b-efc8259908f0
Content: Create a REST client using .NET Core
Content Source: docs/csharp/tutorials/console-webapiclient.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for raising this issue @rcollette
I've added this to our backlog for the next update to this sample.

Any news on this Bill?

For those of us behind corporate firewalls it would be helpful to include a discussion about proxy handling including examples of setting up the WebProxy and HttpClientHandler classes needed.

For anybody who has trouble with proxy: This worked for me: Replace:
private static readonly HttpClient client = new HttpClient();
with
private static readonly HttpClientHandler handler = new HttpClientHandler
{
DefaultProxyCredentials = System.Net.CredentialCache.DefaultNetworkCredentials
};
private static readonly HttpClient client = new HttpClient(handler);

@dotnet/docs - This issue was not addressed and I still believe it is an important feature to document.

@dotnet/docs - This issue was not addressed and I still believe it is an important feature to document.

@rcollette Have you already read the following doc?
https://docs.microsoft.com/aspnet/core/fundamentals/http-requests
The doc contains some examples of calls to AddHttpClient.

@rcollette Have you already read the following doc?
https://docs.microsoft.com/aspnet/core/fundamentals/http-requests
The doc contains some examples of calls to AddHttpClient.

Yeah that suffices @scottaddie.   Thank you for responding.

Yeah that suffices @scottaddie.   Thank you for responding.

Thanks @Scottaddie.
@rcollette We'll leave this closed, as addressed.

Thanks @Scottaddie.
@rcollette We'll leave this closed, as addressed.


mouse op iphone coordinates when "cancas" ?

also: canvas area uses parent element when canvcas is fixed ratio?


Calling the function requires a slightly different implementation.

The pattern I am using is different. I am holding the array object in state. Close, but I am not sure how exactly to do this.
            return  this.state.data.length > 1
               ? this.state.data.map((item) => (
                   <Card key={item.sku} >
                        <CardImg src={item.image} />
                        <CardTitle> {item.sku} </CardTitle>
                        <CardBody> {item.name} </CardBody>
                        </Card>
               ))
               : null
        }

And I am using it by calling the function (not a parameter).
                                <Row className="grid" > {this.renderData()} </Row>
                        </Container>```

I'm not sure what your question is sorry. Can you provide more context please?


compatibility with tf 2.3

Compatibility with tensorflow  v2.3.0

Pull Request Test Coverage Report for Build 352

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.839%

Totals

Change from base Build 349:
0%

Covered Lines:
766

Relevant Lines:
791

💛  - Coveralls

Thanks. The new version is 0.86.0.


Discretization of the grid for the Abel transform

While I think we all agree on the definition of the image center as discussed in issue #34 , illustrated on the figure below,

the fact that the transform requires odd or even images, also has wider implications on the spatial discretization assumed by the algorithm (which I have personally never considered). For instance in 1D, the two possible discretization are illustrated on the figure below,

where the pixel size is dr. @stggh Regarding your earlier comment, both approaches are uniformly sampled, as far as I understand.
Although, in practice, far away from the origin, I suppose it shouldn't really matter, the way the grid is discretized is probably a fundamental property of a given implementation. Therefore,  I'm not sure we can expect all implementations to support both odd and even images. For instance at present, it appears that there is the following separation,

Odd images : BASEX, BASEX_asym (originally)
Even images: HansenLaw, direct (I think), Fourier-Hankel (I think)

Another applications is, for instance, 2D cylindrical fluid dynamics simulation, that I project with the forward Abel transform, are also in the "Even images" case.
In the particular case of the direct implementation, I'm not so inclined to redo all math to see what it should be if we change the discretization of the grid for odd images, nor do I think it would be that useful (more code => more possibilities for bugs, possible inconsistent behavior between odd and even images, and finally it shouldn't matter anyway for real data of > 1000px ).
So the question is whether in general we should,
a. Raise an error if e.g. an algorithm working with odd images is given an even image
b. Hack the input/output image  as to work both with odd and even images, while actually providing the transform with the an image of the parity it supports. For that  we could use @DhrubajyotiDas proposition, i.e:

even -> odd:  add a fake central row, as an average of the neighbor rows, then remove it after the processing
odd -> even: split the central row in 2, then take the average of the resulting 2 rows before outputting the image.
This would introduce some additional error, particularly near the origin, because of a shift by 1/2 pixel of the whole image when this hack is used, but I don't think it would be that bad, particularly as the data near the origin is noisy already in the majority of implementations.

If we decide to go with b., it would make sens then to go with an implementation, that could be used in all the implementations and not just as a fix to the BASEX algorithm.
Let me know what you think about this.

Wow, amazing work you guys, overnight (oz time). Invigorating!
I was thinking about exactly this speed grid issue. Your grid diagram is excellent. The problem that I see what does tools.generate_speeds() use for as the grid, in combination with tools.reproject_image_into_polar()? Or is it not important. At the moment we force the user to associate radius (velocity) to the speed intensity distribution, when we should return (R, speed)?
I may be confused, but the 0->R grid should correspond to the mid point of each pixel, with the centre of the image always, 0. Hence, oddly enough, the even-image has a grid offset (case B), and the odd-image corresponds to the integer grid.  The bottom line is that the R grid should also be returned.
@rth:

HansenLaw can handle odd images, without the need for padding, but not, at the moment, the way I implement the algorithm. An odd or even sized length row of data (pixels) does not matter.

a. Warning error, allow the method to proceed. In general, the result is "nearly" correct, and better than nothing.
b. It may be that only basex requires odd images. The "quick fix" even->odd requires the speed distribution grid, as I identified above. odd->even may not be required for the other algorithms.

I like the idea of only letting the transform operate on images where it produces the right output. But, as @stggh point out, it might be nice to just have a warning, since 90% of users will not care if the transform is shifted by a pixel.
One approach would be to let the low-level functions, like abel.iabel_basex() demand images that meet the requirements of the method (odd, as far as our current basex implementation goes) and throw an error if given the wrong shape image. However, the user-friendly wrapper function (abel.iabel(im,method="basex")) could accept inputs of the wrong shape. abel.iabel would then modify the image to be the correct shape and print a warning that the wrong image shape was supplied and that the transform may be slightly shifted.
The question of what the heck the reproject_into_polar() function is actually doing is anyone's guess, since I just borrowed that code from Stack Overflow. Confirming that reproject_into_polar is doing the appropriate for all image geometries should be on our to-do list.

reproject_into_polar() does not appear to handle even pixel sized images, due to the use of (integer,integer) coordinate image centre, and the associated np.meshgrid(). I am investigating the path forward to evaluate the speed distribution for even images.

Supplying the real origin, for even images, calculate_speeds(recon,(N2-0.5,N2-0.5)), produces agreement.

All good now. You code for basex odd images was correct all along.

I have revisited abel.tools.reproject_image_onto_polar()

The (old) comments describe a png image, which has (0,0) is bottom left, not the case for numpy arrays.

The default origin is (ny//2, nx//2), and hence the method does not correctly handle an odd-size image.
Adding +ny%2, +nx%2  to the origin coordinate corrects this issue.

The polar grid is defined as r= [0:r.max()], and θ = [θ.min():θ.max()], with respective step sizes determined by nr=r.max(), and nt=ny//2. These coordinates are then used to interpolate the original image. The choice for nr and nt is arbitrary, there may be good reason to use larger values, a smaller grid.
passing and additional parameter polar_grid=None to allow specifying nr, nt as a tuple, limits aliasing. This parameter is now available to calculate_speeds().

I have also added the parameter,  Jacobian=False, to include sinθ in the summation over angle, so the integration over angle is ∫ P(r, θ) sinθ dθ

Here is an example plot. The left side illustrates the effect of sinθ, which in the case of negative anisotropy parameter (β) conveniently suppresses the low θ (and near π) intensities which have inverse Abel transform noise. The right side shows the effect of reducing the polar grid size, the transition peaks are less truncated.

Given the additional parameters for abel.tools.calculate_speeds(IM,  origin=None, Jacobian=False, polar_grid_sizes=None) I think that there is a case for removing the calc_speeds option, and parameters from iabel_<method>(), since, in principle this function should just return inverse Abel transformed image. Otherwise, the parameter space, and definitions, becomes messy. Thoughts?

Thanks for taking a closer look at this @stggh!

I agree that the "move the origin back to the lower left corner" comment is inaccurate/misleading. It's from the stackoverflow post, and it seems like Joe Kington (the guy who made that post) considers the [0,0] index to be the lower left corner. I think that PNG uses [0,0] as the upper left corner, and though a numpy array doesn't necessarily have a spatial orientation, plt.imshow defaults to putting [0,0] in the upper left as well. So, you are correct in both cases I believe.

Great! I'm glad that the fix is easy and that it can now work for odd-sized images.

(Answering out of order) I'm slightly confused about how the Jacobian plays out. I think that once we have our data in r and theta coordinates, then the Jacobian for the angular integration is r*sin(theta), since we are assuming a 3D cylindrically symmetric object. Basically, when we rotate the slice we get more volume for pixels that are further from the axis of cylindrical symmetry (r*sin(theta)).

However, when we transform from cartesian to polar coordinates, I think that there is also a Jacobian of r. Basically, at low r, we are spreading the intensity into numerous theta bins, so we need to compensate by multiplying these by r. So, the total Jacobian would be r**2 * sin(theta). Am I thinking about this correctly? Note that the Jacobian of r should be implemented by the reproject_image_into_polar() function, since it's a result of the coordinate transform. The r*sin(theta) factor should be applied by the calc_speeds (it's called something different now) function.
Oh, and there are probably some dr and dtheta terms that I forgot about. reproject_image_into_polar() should probably also multiply by dr and dtheta.

You make a good observation that the choice of the (r,theta) grid is arbitrary and can have an effect on the outcome. Currently, we are picking an r-grid that should match the pixel spacing of the image, so this seems roughly sensible. I can't imaging that using a grid that is too much smaller than this would help much, but perhaps using twice the number of r-points would help.

The number of points in theta is being set to nt = ny//2, which seems quite arbitrary indeed, and will certainly be too small in some situations. For example, if I think about a square image with pixel dimensions (N,N), then, at the edge of the image, one pixel represents a theta step of arctan(1/N), which in the small angle approximation is 1/N. To adequately sample this step in theta, we would need 2piN values of theta. So, over 6 times what we are currently using.
I think that I sort-of realized this a few years ago, but elected to use fewer theta bins since it considerably sped up the reprojection into polar coordinates. When I switch nt=ny//2 to nt=ny*2*np.pi, this causes the speeds calculation to slow from 0.18 seconds to 1.08 seconds for a 2048x2048 image. So, it scales approximately linearly with the number of theta steps.
Also, I should probably not have set the theta step using ny, since this won't provide consistent behavior for rectangular image. Probably np.max((nx,n)y) should be used.
I am not quite sure how to handle this. Providing a grid size that is adequately small for all situations seems to cause quite a performance hit, but it seems like the right thing to do. Perhaps we can allow the calc_speeds function to take nr and ntheta as arguments, and users can either specify the actual value or leave them to their default values of ntheta='fine' to have them automatically assigned to nt=np.max((nx,ny)) * 2 * np.pi, and perhaps also a 'coarse' setting that uses something more like nt=np.max((nx,ny)) * np.pi//4.
One other option would be to use a triangular array for the polar image, like the one described in the Polar Onion Peeling paper and implemented in this matlab code. Here they change the theta size in order to provide polar bins that more-or-less match the cartesian grid:

Regarding your last question, the plan is to move the speeds calculation out of the iabel_<method>() functions, since this calculation is the same for all of the transform methods so far. So yes, the iabel_<method> functions provide only the 2D transform.

@DanHickstein you have immense clarity of thought!

You are right, the Jacobian should be r**2 sin(theta) and include the dr, dtheta terms.  I imagined that the missing x r factor was at the conversion of speed (r) into energy transformation (r**2).  I need to think this through further. The O- PES is not super sensitive to x r factors, but, along with O2- PES, and other species, provide a good check.
e.g. the original basex.exe speed calculation needed a 1/r intensity factor, due to the way the Abel transform is defined (in the associated paper).

reproject_image_into_polar provides the opportunity to reshape the projrcted image. I am not sure this flexibility should be closed off. I like your solution of nr, nt ='fine' and 'coarse' defaults, since the user is unlikely to know what to choose. I am happy to go with that.

The triangular array is interesting, but how is it possible to follow the r-axis? I will take a look at the method.
x) I an happy to extract calc_speeds from hansenlaw

Oh, I didn't see your check of the ratios using the O- data. That's really cool! Does it still work when we add the extra r factor?

Yes, we should maintain the ability to reshape the image with the reproject_image_into_polar() function. nt and nr can be any integer, or the user can supply the fine/course strings to have the number automatically generated from the image dimensions. Can you check with your data to make sure that having fine correspond to

nt = np.max((nx,ny)) * 2 * np.pi
nr = np.max(R)
# Where R is a list of all of the radial coordinates in the image.

is sufficient?
I also wonder if we should provide an option to crop the output array to the largest r-value that contains data at all angles. I.e., even in a square image, there are regions at the corners that should probably be ignored. Since we would basically be cropping a circle from the original image, this presents the hilarious opportunity to include a crop_circle=True/False flag.
The triangular array looks very similar to our current matrix of theta versus r, except that the theta values are different for each row of r. Here is a screenshot of the matlab code showing the transformation. Original image is no the left, triangular matrix is on the right. The y-axis is the r value, and the x-axis

The only advantage of the triangular array approach would be that it wouldn't oversample (in theta) values at low r. But, as long as we incorporate the jacobian of r, we correct for this anyways and it should not be a problem. Our current rectangular array approach allows us to easily see any r value as a function of theta without doing any extra work. This is probably a large enough advantage that we should just stick with our current approach.

Yes, the extra r scaling is required, the correct Jacobian is r2sinθ

(rough) Gaussian function fits to the 3PJ ← 2P3/2 transitions. Table of amplitudes (FWHM ~ equal), not sure about the validity of the fit error estimates (#):

r sinθ
r2 sinθ
theory

0.104(4)
0.078(4)
0.08

0.407(4)
0.340(4)
0.36

1.012(4)
1.012(4)
1

nr, nt limits:
(i) nr = r.max()     to remap the while image
nr = np.min((nx,ny))  for the speed distribution. Note the min()

(ii) nt = np.max((nx,ny)) * 2 * np.pi   'fine'    and *np.pi/4 'coarse'
In this case use of min or max make little difference.
I will check these grids sizes on the O- PES
For the nr, nt parameters I am concerned about mixing types, string/integers, without creating a code mess and/or user confusion. The requirements of a polar_image projection (a pixel shape, with definite nr, nt) are different to the speed distribution (a grid).  For speed I would prefer a grid with a nice spacing, dr =1, or dr = 0.1, a value which is not easily deduced in specifying the parameter nr.
For nt the 2 or 1/4 factors become somewhat irrelevant for large nx, ny. I think these aspects require some more thought/@DanHickstein innovation/arbitration.
Triangular array:  I agree, we should stick with the current approach. For our current inversion methods the noise accumulates near the image center(-line), and so accurate intensity interpolation near the image center is less important.  For completeness, at some stage the method should be included in the PyAbel arsenal of tools.

Okay, so the r**2 sin(theta) looks good. Awesome!
For the nr, nt situation, I don't see too much problem with letting the user specify a string or a value. I think that it's pretty common in numpy/scipy to allow a variable to be, for example, either a single number or an array of numbers. I think that I've also seen situations where a argument can either be 'auto' or the values can be specified. As long as we document it well, it should not be too confusing. I think that it's important to provide some guidance to the user about what values are appropriate (as we are doing with the coarse/fine presets).
It also seems fine that the reproject_image_into_polar() function accepts arguments in terms of nt and nr, while the function calculating the speeds accepts dr and dtheta. The function calculating the speeds can simply calculate the appropriate numbers to pass to the reproject_image_into_polar() function. The function returning the speeds calculation could also return an array of the r-values, just to make it clear to the user and to make it easier to consistently plot the data even as the user adjusts the dr parameter.
You mention that the exact nt value becomes irrelevant as nx,ny become large. This is true if your features remain broad. In principal, any image size could contain a feature the size of one pixel near the edge. The exact value of nt would determine if this feature is resolved or not. So, it's a question of if we want to default values to deal with a "worst case" scenario at the expense of making the calculation take longer. Actually, I think that it would be fine for the default values of the calc_speeds function to be different than those for the reproject_image_into_polar() function. reproject_image_into_polar() should default to a fine theta step to be able to resolve all of the features, while calc_speeds could use a larger theta step on the assumption that those performing the full integration may be less sensitive to fine angular features.
Good to get this stuff worked out before our overly coarse theta grid fools someone in the future!

For my own photoelectron measurements I(θ) may vary no faster than (3 cos2θ - 1)/2, so angular resolution is not so much of a problem cf the radial coordinate. In this case nt need only to be large enough to sample the cos2 function. Hmm, I now see no advantage in increasing nt beyond the default of nx or ny!
In fact the (fat) chunky pixels(1) limit how large nt, nr may usefully be (I think you mentioned this earlier).  Possibly, nr <= 2*r.max() (dr = 0.5).  Hmm, I was wrong about the flexibility of polar reshaping, as the interpolation is limited by the cartesian original image size.
I now believe that nt = ny//2 may be fine. nr = nx,    2x larger may be enough. No need for parameters.
(1) I was lead astray by my own experimental method in which an image of arbitrary size is generated from centroided sub-pixel electron positions. Larger pixel images provide better resolution (but less signal).

Sort of back to square 1 (sorry!):
The reproject...() method has:
r_i = linspace(r.min(), r.max(), nr) and theta_i = linspace(theta.min(), theta.max(), nt)
with  nr = r.max() and nt = ny//2.  Note, dr is more than 1, because linspace includes the upper limit (and so calculate_speeds() must return the r coordinate values).
The orginal stackoverflow (Kington) code uses nr=nx, nt=ny. i.e. a grid size twice as large.
The Kington values for the polar image are probably optimal, and return the same shape image.
With the speed calculation r should only include the largest whole circle i.e. nr = np.min((nx,ny))//2.  @DanHickstein suggestion of a 'coarse' grid dr=1 or 'fine' grid dr=0.5, parameter option, is adequate. i.e. linspace(0, nr//2+nr%2-1, 2*(nr//2+nr%2)-1).
For theta, nt ~ 360, equivalent to a 1 degree interval is probably more than enough. So, nt = ny//2 should be more than adequate.  If we are looking to reduce execution time, then 360 might be a better choice. I will investigate how the speed distribution changes with the mgnitude of nt.

I modified tools.calculate_speeds(), reproject...() to pass dr and dt (in degrees), and then evaluate nr, nt.
The figure is the O- PES shown above in the radial region of the strongest peak.

The left figure, varies dr=1, 0.5, 0.1 and the resultant nt is shown. It is seen there is an improvement in reducing dr to 0.5, and little in going further. i.e. nr = ny = 1024 appears sufficient.
The right figure, varies dt in degrees (for dr=0.1). Here, quite small large dt (small nt) are ok. The default is nt = nx//2 = 512 is fine.
I think the defaults should be nr = np.min((nx,ny)) (2x old value) and nt = nr//2 (same), and allow dr=None, dt=None to be specified as the user requires. calculate_speeds() must also return the r co-ordinate grid, and IMO, might as well return theta.

Thanks for doing this analysis!
Having dr=0.5 makes some degree of sense. Maybe there is some analogy to be made to Nyquist sampling...
And good catch with the linspace. I suppose we should be using np.max(r) - 1 as the upper limit.
The sensitivity to r and the insensitivity to theta makes sense considering that your images have narrow radial features and broad spectral features. For photoelectron images, this is generally the case and we can see a substantial performance gain by using a coarse angular step.
The polar_integrate() function (this is what we decided to call the combined calc_speeds() and anisotropy calc function, right?) can use default values that are optimized for speed and the broader angular features seen in photoelecton/ion spectra.
In my view, the reproject_image_into_polar function may see broader usage, since it is the only python function that I know about that does this, and reprojecting an image into polar coordinates seems like a fairly common task for a scientist. So, for this function, I'd like to at least have the option for the user to specify the fine grid, which would be sufficient to sample all features, even a single pixel at maximum r.
To me, it doesn't make much difference if we specify nr,nt or dr,dt. Actually, it's a weird situation, because dr is the same for all image sizes, while the appropriate nt or dt depends on the image dimensions.
In any case, we should add an additional functionality to reproject_image_into_polar() to allow the user to specify the maximum r value. rmax='circle' would set the maximum r-value returned to be np.min(nx,ny). rmax='all' would set the maximum r-value to np.max(r) as is done now. Or, the user can specify the actual number. Currently, we are calculating the projection out to the maximum r-value and then cropping it in the calc_speeds() function, which is inefficient.

The polar_integrate() function (this is what we decided to call the combined calc_speeds() and anisotropy calc function, right?)

I missed that discussion, but it makes sense to have just one function.
reproject_image_into_polar(data, origin=None, dr=None, dt=None):  My (rough) code selects rmax based on whether dr is specified. I am not sure that it is necessary to add another parameter?

I think that rmax and dr should be specified independently. For example, some users may want rmax=np.min(nx//2,ny//2), (i.e., the largest circle that can fit into the rectangular image), while other users may want rmax=np.max(r), (i.e., the largest r-value, which lies in the corner of image).

For the radial profile rmax=np.max(r) makes no sense. The data beyond nr=np.min((nx,ny)) has no value. Each radial profile moving (in angle) away from the image corner(s) is further truncated. The speed  distribution beyond nr is a sum mostly of zeros, with a little piece of intensity.
However, perhaps, I am missing the end use. I am happy to go with your call.

Now that I think about it, maybe for simplicity it's best to keep the calc-speeds and anisotropy calculations separate, even if it means that we duplicate the projection. It's possible that we want to use different defaults for the nr and nt values for the two functions anyway.
You're correct that it doesn't make much sense for the calc_speds() function to use r-values that are beyond the largest circle that can fit in the image (np.min((nx,ny))). However, for the reproject_image_into_polar(), I can imaging some situations where the user has real data near the corner of their image and they wish to see that data on their polar plot, even though not all of the newly generated (r,theta) grid will have defined values. In any case, I agree with you that rmax='circle' should be the new default behavior for reproject_iamge_into_polar(). Users who want the other behavior can specify rmax='corner' or input their own value.
I think that it's important to also let users specify any arbitrary rmax to reproject_image_into_polar(). For example, if they are starting with several images of different sizes, but they wish to plot them all onto the same size r,theta grid, then the ability to specify rmax, nr, and nt allows this.

Phew! I looked at combining the two calculate_ functions, and it was not straightforward.
Agreed. dr, dt, rmax='circle'/'corner' parameters for reproject_image_into_polar().
calculate_speeds() can set rmax='circle' for the call to reproject_image_into_polar().


Live script reloading did not work

Operating system or device Android Nexus 7, 6.0.1, - Godot version:2.1
Issue description (what happened, and what was expected):
modify the scripts and save it will not reloaded to the running device.
And each time run on the device require uninstall and reinstall still takes a little more time compare to some other engines that can just update the modified contents.
Steps to reproduce:
setup a simple func _process(delta):
and print something
run on a connected device
modify the contents in the print
still output the original contents.
Link to minimal example project (optional but very welcome):

And each time run on the device require uninstall and reinstall still takes a little more time compare to some other engines that can just update the modified contents.

Have you tried Remote deploy over network?

you need to turn on the option "small deploy over network"
On Wed, Jul 13, 2016 at 7:46 AM, Rémi Verschelde<EMAIL_ADDRESS>wrote:

And each time run on the device require uninstall and reinstall still
takes a little more time compare to some other engines that can just update
the modified contents.
Have you tried Remote deploy over network?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/5671#issuecomment-232320994,
or mute the thread
https://github.com/notifications/unsubscribe/AF-Z20htQCChU88tgFQBAjtrNuGR6NiUks5qVMH7gaJpZM4JLSd9
.

Remote deploy over network failed on v2.1, only remote deploy over usb work.
But Remote deploy over network can work on v2.0.3.
small deploy with network fs is checked on.

As there was no answer to the above request, we're closing this issue as inactive.
If you can still reproduce it, please open a new issue against a currently supported release of Godot.


Update sbt-mima-plugin to 0.9.2

Updates com.typesafe:sbt-mima-plugin from 0.8.1 to 0.9.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe", artifactId = "sbt-mima-plugin" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #108 (c91f66e) into master (87a660e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #108   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           35        35
  Branches         2         2
=========================================
  Hits            35        35

Continue to review full report at Codecov.

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


Quarkus native test

First of all, thanks for creating this extension it is very useful when creating tests.
Rather than asking for a solution, I'd like to understand if you have ever tried to use your extension in native mode
import io.quarkus.test.junit.NativeImageTest;

@NativeImageTestpublic
class NativeFruitsEndpointIT extends FruitsEndpointTest {
    // Runs the same tests as the parent class
}

Just like all the examples in Quarkus-quickstart e.g. https://github.com/quarkusio/quarkus-quickstarts/blob/main/hibernate-orm-panache-quickstart/src/test/java/org/acme/hibernate/orm/panache/NativeFruitsEndpointIT.java

I've tried to execute a native test using Quarkus with no success, it seems that in native mode the extension is not executed. However, all tests in no native mode work perfectly fine. Is this an expected behavior or perhaps the extension requires enhancement for Quarkus Native tests?

Hi @carlosthe19916,
Thanks for the report. I've never tried this with native. I'll need to have a look. It theory it should be possible, but with some limitations (H2 server doesn't work in native for instance).

Hi @carlosthe19916,
I've added an example in #77. Please, check it out.

Awesome! Thank you very much @radcortez


[feat] Import Alert Notifications

It would be nice to be able to import the alerts from grafana.
http://docs.grafana.org/http_api/alerting/

@sstarcher Made you a collaborator to the project!


[FEATURE]Update docs and descriptions based on the CPU & Network requirement investigation result

Is your feature request related to a problem? Please describe.
Need to update Longhorn docs and the description of setting Guaranteed Engine CPU based on the result in #1691

Volume count in the cluster?
Also, I am thinking if we should ask the user to reserve 1/8 of the total CPU count then tell them how many volumes/engine/replicas can be used per node. Since it would be hard for the user to adjust the value later.

Done. The doc has been updated, and the setting description.


Rate Limiting Rules documentation

Preview of the main Rate Limiting Rules topic, under "Custom Rules - Beta", in the "WAF" documentation tile:

Are we using the WAF namespace for this? Shouldn't it be in the Firewall one?

Good job
Pada Rab, 7 Apr 2021 5:47 PTG Miguel de Moura @.***>
menulis:

Are we using the WAF namespace for this? Shouldn't it be in the Firewall
one?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-docs/pull/1080#issuecomment-814775074,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARMDWCAC33EE77PFRDTETGTTHQS3DANCNFSM42QMKBHQ
.

Hi @migueldemoura
We did discuss the location, and the PMs (Michael and Daniele) agreed to use the WAF tile going forward and eventually deprecate the Firewall tile. The "Rulesets - Beta" section would also move to a different (product-agnostic) location in the future.


Terminal breaks badly on window resize

Ubuntu

Open tmux (or any terminal app which takes mouse control)
Resize Code's window

Didn't see this last week at all, started happening today only, so it's probably due to a change delivered since Friday. I wonder if it's related to the Shift select changes?

Hmm, I can't repro after tmux and resizing both dimensions of the window rapidly. Could you try update to latest and try again? I pushed a massive update to xterm.js yesterday but it didn't appear to be published to the apt repo.

Same happens on macOS in 9c5d505c995c73bfa8daf8c537eba6d3450eeca3. 😢

Running out of master:

Open terminal
htop
Resize terminal

I can repro on mac 👍

Oh it doesn't repro on today's insiders. :confused:

:confused:
Weird, I'll still have a look when I get a chance.

What. Seems to have returned today!
I know @sandy081 hits it too.

Yeah, I saw it yesterday and today (after update) I can't reproduce.

@Tyriar Let me know if I can help somehow. This morning it was broken for a while... and somehow it was fixed when I alt-tabbed into it. So weird.
I'm forced to go back to an external terminal. :cry:

I see the issue again in today's insiders. It is random.

I spent an hour or 2 on it yesterday and struggled to reproduce.
Something that would help diagnose: If you happen to reproduce it (ideally out of sources), break where it's throwing which is here:
https://github.com/sourcelair/xterm.js/blob/bfdc468d4bc823b242ada286c7e8ecc7978f2b72/src/Renderer.ts#L142-L145
It would be good to see what the following values are:

y
this._terminal.buffer.ydisp
this._terminal.buffer.ybase
row
this._terminal.buffer.lines.length

I think I found the problem - PR out in https://github.com/sourcelair/xterm.js/pull/923

Upstream issue: https://github.com/sourcelair/xterm.js/issues/924