Cellular dropping on 12.1 since b36-b38

Cellular data randomly disconnects while in jb state never in non jb state
no known way to reproduce, it is random
I will upload a screenshot when it happens next
Device (please complete the following information):
-iOS 12.1
-iphone 8

unc0ver Version: b~38

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[x] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x] this issue is present after a rootfs restore
[x] this issue is present on the latest version of unc0ver

no logs
Before you close this like the other ones and say it is not related to unc0ver, just think. It doesnt happen in normal mode
it did not start until jb
not tweak related(to my knowledge)
Please just give it some thought, please.

@wbraffman Please post unc0ver diagnostics. That way I can see if its unc0ver related.

Of course, where do I find the diagnostic?

On Mar 1, 2019, at 12:30 PM, Liam(Cryptic<EMAIL_ADDRESS>wrote:
@wbraffman https://github.com/wbraffman Please post unc0ver diagnostics. That way I can see if its unc0ver related.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pwn20wndstuff/Undecimus/issues/640#issuecomment-468745154, or mute the thread https://github.com/notifications/unsubscribe-auth/AorB-TpyaOBLzq2bx_dL2WSNaHTn1vYgks5vSWPIgaJpZM4bZeIA.

@wbraffman unc0ver settings, scroll down, share diagnostics.

diagnostics.plist.zip
here sorry to make u wait, do u need a screenshot as well?

Same issue iPhone X 12.1.1

https://mega.nz/#!04tl2ISa!olF2JePsw7nbIki0aWMq_UJ7c0F8QZcvi1gBqO9tVgM

I have the same problem, iPhone X, iOS 12.1.1 Beta 3, unc0ver b38

Same issue iPhone X iOS 12.1.1
unc0ver 3.0.0~b38

Same issue here in b36 and b38

12.1.1 is buggy as it is, but it happening on 12.1 is odd, we will see, it hasnt happend much recently
for me

12.1 is buggy because you have pirated tweaks that break your device. Remove packages from pirate repos then remove the pirate repos. See if that fixes the problem.

I have only legit repos, I bought every paid tweak, nothing pirated. I have problem with cellular dropping

Post diagnostics. @wbraffman @mikigal

I haven't this issue since last reboot (today morning).
Here's my diagnostics from unc0ver: https://loveani.me/diagnostics.plist

Haven’t had this issue yet using unc0ver b39 it seems to be patched

Same

On Mar 4, 2019, at 4:27 PM, Rickie Noel<EMAIL_ADDRESS>wrote:
Haven’t had this issue yet using unc0ver b39 it seems to be patched
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pwn20wndstuff/Undecimus/issues/640#issuecomment-469428224, or mute the thread https://github.com/notifications/unsubscribe-auth/AorB-UxJjD9nxgJsHC2d3dIvMgudCrC5ks5vTY-5gaJpZM4bZeIA.


[test] Add rom_e2e_bootstrap_rma, iteration 1

This is the first half of #15677.

@alphan Ping :)


Image Grid not putting all images in to a grid

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
No
Minimal theme version
6.1.9
Describe the bug
The image grid doesn't consistently put images in to a grid. Sometimes it'll only put 2 or 3 images in to a grid and the rest will be full width on their own.
Here are some example images:

Here you can see that only the bottom two images are next to each other despite the source having what should be two more rows above it.
TestImages.zip
Here is a test vault that exhibits the issue. This was created using a completely fresh vault with nothing else installed but the required plugins.
 If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

This happened to me too, can you try to resize the images? ![[imagename.png||100x100]] change 100x100 for the dimensions that suit you. In my case, after doing that, they did rearrange in a grid

This happened to me too, can you try to resize the images? ![[imagename.png||100x100]] change 100x100 for the dimensions that suit you. In my case, after doing that, they did rearrange in a grid. If that does not work, try to write them next to each other, instead of making a new line in between

I managed to get around it by making sure all of the images are png or jpeg. Lot of effort though. I think it's webp in particular that seem to break things.

Ah, I didn't even realize they were webp. I'm glad you could solve it :)

I'd like to add that BMP images also do not work.
Now that we know more details of the bug, I'd appreciate if the author updated the title and description to reflect the core issue being image grids not working with all image types. Hopefully that helps produce some momentum on this!

Fixed in 7.0


Senawave shows up multiple times in reports

@jpechmann Check out OBJECTID's 1100 & 1101 in UBBMAP.UBBADMIN.BB_Service_Wireless. Are they duplicates?

No, one is residential service and the other is commercial service. The commercial has faster speeds.

I'm assuming that this is why Kelleigh is seeing duplicate Senica entries.
Am I supposed to be removing duplicate businesses in the report? I don't
believe that it does this currently.
On Mon, Apr 20, 2015 at 5:04 PM, jpechmann<EMAIL_ADDRESS>wrote:

No, one is residential service and the other is commercial service. The
commercial has faster speeds.
—
Reply to this email directly or view it on GitHub
https://github.com/agrc/bb-econ/issues/80#issuecomment-94588382.

--
Scott Davis
Utah AGRC http://gis.utah.gov/developer/
<EMAIL_ADDRESS>@ScottAGRC https://twitter.com/ScottAGRC

I think maybe it doesn't check for duplicates in wireless, but it does in wireline? I checked an area I know has residential and business for wireline (Emery Telcom in Castle Dale) and it doesn't duplicate Emery in the report under other fixed providers.

@jpechmann: So I should be removing duplicate providers between the "Fiber" and "Other Fixed Broadband" lists? If they show up in "Fiber" then they should be removed from "Other"?
For example, check out this report. SenaWave, Syringa Networks, and XO Communications should be removed from "Other"?

There can be duplicates between "Fiber" and "Other Fixed", I think the issue was that SenaWave was listed twice under "Other Fixed". Although I just ran this report and its listed three times under Fiber- http://locate.utah.gov/report.html?x=425017.3444575727&y=4512504.2185141295&address=424 S State St&city=Salt Lake City&zip=84111&county=Salt Lake. So.. I think you just need to double check for duplicates within each list.

Only "other" providers were being filtered for duplicates. I added a duplicate filter for fiber now as well.


Points feature does not show points in recent release

@Composable
fun App(component: VisualizationComponent) {
val state by component.state.collectAsState()
val viewScope = MapViewScope.remember(state.mapTileProvider)

MaterialTheme {
    Box(modifier = Modifier.fillMaxSize()) {

        MapView(
            viewScope = viewScope,
            features = FeatureGroup.build(WebMercatorSpace) {
                state.routesShown.forEach { route ->
                    points(route).color(Color.Blue) // does not show anything

                    // works completely fine
                    var prevPoint: Pair<Double, Double>? = null
                    route.forEach { point ->
                        prevPoint?.let {
                            line(it, point).color(Color.Blue)
                        }
                        prevPoint = point
                    }
                }

            }
        )

    }
}

}


Connect to Tor Proxy Server

Hi all,
I have a private irc server running over Tor. Is it possible to add proxy server settings (i.e., hostname, port, type (Socks5)) to the json configuration? I have the server added as address.onion/ and port 6667. I just need to add the proxy network settings.

Hi there! I don't think we have support for proxy servers. This would probably need support in the upstream irc-upd dependency. I'll mark this as a feature request for now, but as the project is largely in maintenance mode, it's unlikely we'll get to this anytime soon.


Encode pending/resolved status of VariationIndex table in write-fonts

Update: I woke up with an idea for how we could actually use the type system here: it would require replacing the VariationIndex struct (in write-fonts) with an enum, that has 'finalized' and 'pending' variants. I don't think this would be much additional code, and would remove any chance of misuse.
Originally posted by @cmyr in https://github.com/cmyr/fea-rs/pull/185#discussion_r1269749806

added and used in #194


Release version 1.0.3

We should ship a release that contains the new documentation bundle.

Candidate commit: ff3d2212b6b093db7f177d0855adbc4ef9c5f036
Diff: https://github.com/apple/swift-atomics/compare/1.0.2...main
These changes consist of documentation updates and package manifest / build configuration changes. I think we can get away with a shortened release validation before tagging, but we'll still need to exercise the new manifests in at least two separate runs with 5.3+ and 5.5+ compilers.
I'll skip Windows testing; I trust that the CMake build results on macOS & Linux indicate that Windows will pass too.
The new tag is expected to produce documentation on the Swift Package Index. Any issues with that will only be found after tagging, though.
Testing progress:
macOS/AS

[ ] macOS 13, Apple Silicon, Xcode 14.1 (Swift 5.7.1)
[ ] macOS 12.5, Apple Silicon, Xcode 13.3.1 (Swift 5.6.0)
[ ] macOS 12.5, Apple Silicon, Xcode 13.2.1 (Swift 5.5.2)
[ ] macOS 12.5, Apple Silicon, Xcode 12.5.1 (Swift 5.4.2)
[ ] macOS 12.5, Apple Silicon, Xcode 12.4 (Swift 5.3.2)

macOS/x86_64

[ ] macOS 13, x86_64, Xcode 14.1 (Swift 5.7.1)
[ ] macOS 12.5, x86_64, x86_64 , Xcode 13.4.1 (Swift 5.6.1)
[ ] macOS 12.5, x86_64, x86_64 , Xcode 13.0 (Swift 5.5)
[ ] macOS 12.5, x86_64, x86_64 , Xcode 12.5.1 (Swift 5.4.2)
[ ] macOS 12.5, x86_64, x86_64 , Xcode 12.4 (Swift 5.3.2)

Linux/Aarch64

[ ] Ubuntu 20.04, Aarch64, Swift 5.8 nightly build
[ ] Ubuntu 20.04, Aarch64, Swift 5.7.1 release
[ ] Ubuntu 20.04, Aarch64, Swift 5.6.2 release

Linux/x86_64

[x] Ubuntu 20.04, x86_64, Swift 5.8 nightly build
[x] Ubuntu 20.04, x86_64, Swift 5.7.1 release
[ ] Ubuntu 20.04, x86_64, Swift 5.6.2 release
[x] Ubuntu 20.04, x86_64, Swift 5.5.3 release
[ ] Ubuntu 20.04, x86_64, Swift 5.4.3 release
[x] Ubuntu 20.04, x86_64, Swift 5.3.3 release

Windows 10/x86_64

[ ] Windows 10, x86_64, Swift 5.8 nightly build
[ ] Windows 10, x86_64, Swift 5.7.1 release
[ ] Windows 10, x86_64, Swift 5.6.1 release

(Note: I expect most of this matrix will remain untested in this tag.)

Additionally, manually rebuilding from a fresh clone produces valid semantic issues in Xcode 14.1 when library evolution is enabled:
/tmp/swift-atomics/Sources/Atomics/autogenerated/AtomicLazyReference.swift:142:10: error: initializer for class 'ManagedAtomicLazyReference<Instance>' is '@inlinable' and must delegate to another initializer
/tmp/swift-atomics/Sources/Atomics/autogenerated/HighLevelTypes.swift:84:10: error: initializer for class 'ManagedAtomic<Value>' is '@_alwaysEmitIntoClient' and must delegate to another initializer
/tmp/swift-atomics/Sources/Atomics/AtomicStrongReference.swift:324:14: error: 'self' used before 'self.init' call or assignment to 'self'
/tmp/swift-atomics/Sources/Atomics/AtomicStrongReference.swift:325:3: error: 'self.init' isn't called on all paths before returning from initializer
/tmp/swift-atomics/Sources/Atomics/AtomicStrongReference.swift:447:14: error: 'self' used before 'self.init' call or assignment to 'self'
/tmp/swift-atomics/Sources/Atomics/AtomicStrongReference.swift:448:3: error: 'self.init' isn't called on all paths before returning from initializer

It isn't clear why these aren't being reported by the full-test script.

The library evolution test case failure also seem to be reproducing in 1.0.2; in any case, this need not hold back the release.

1.0.3 is out!


set testRetryCount default to 0

Motivation;:

testRetryCount system property is used by a custom IRetryAnalyzer
unfortunately in case of retry the Before/After hooks are not executed and the system is in an unpredictable status during retries
it is better to change the default to 0 and let the user or CI configuration to opt-in explicitly this feature
Maven Surefire plugin has a specific standard configuration option, it is better to use that option

Changes:
set the default value to 0, both in pom.xml and in Java code
If you want to use this feature you can simply run your build with -DtestRetryCount=1

@merlimat @ivankelly it looks like you worked in these file recently, please take a look
@lhotari I think that this fix will make the tests more reliable, probably uncovering new flaky tests, but rerunning a test in an unknown environment is far worse that seeing a flaky test.
Flaky tests can be a symptom that something is going wrong, we should not rely on this kind of tricks
cc @sijie @rdhabalia

I can set the rerunFailureTests option in surefire.
The way this option is implemented is not reliable.
Otherwise I can add the option to the command line of every github actions build

@eolivelli If we are going to set the option for every GitHub action, why do we want to change the default value? For people who want to disable retryCount, they can just set the retryCount to 0 themselves. In other words, I don't know what exactly the value this PR brings. If you can show it improves the stability of CI, I am fine with it. Otherwise, I would hold on this change, because people can disable the retryCount themselves.

Basically the problem is that the way we are rerunning failed tests in not well done.
Because the second execution runs in a polluted environment.
I will push an example as soon as I have time.
I saw this problem when I was working on a fix, and I realized that the second execution was using a stale PulsarService started by the first tentative

There is no hurry to merge this patch

@sijie @merlimat is my example useful in order to understand the problem?

@codelipenghui that do you think about this patch ?
@sijie is my point convincing ?

@codelipenghui that do you think about this patch ?
@sijie is my point convincing ?


Devices without magnetic sensor has issue with image rotation.

Environment: Samsung Galaxy tab 4 (SM-T230) Android version 4.4.2
Users who own devices without magnetic sensor will be experiencing issue with image after they shoot the photo of the offense, e.g. if user shoot a photo in portrait device orientation, he'll get all thumbnails and image on the "enter car plate number" screen rotated to the 90˚ CCW.

[update]
Environment: Samsung Galaxy Grand Duos with Android 4.4.2
This device, according to the specs,  has accelerometer and compass but has the same issue when after taking photo image rotated to the 90˚ CCW


Lists have an odd padding at the bottom

The first 5 tabs have the above padding, but the last tab has a much larger one:

almost fixed in v1.1.1. current state:
top:

bottom:

top is fine

the bottom is... I think the padding is now a tiny bit smaller


OnXUkagakaLinkOpen

https://github.com/Taromati2/ghost/commit/0bf3e98340c720592a2fb2bd098c5e5707c01626
This assumes that the user knows what he is doing
If you are worried about this, maybe you can add a define request to let the user show that he knows what he is doing

ported


how to change the favicon

I'm submitting a ...
[ ] bug report
[ ] feature request
[ x] question about the decisions made in the repository

Do you want to request a feature or report a bug?

just a question

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

You can change favicon.ico file as you like

@labyed Take a look at config/head-config.common.js.  You can update the png file as defined there or you can change the path to point to your own png file.


remove google third party

@t-webber
If you thinks it's a good idea
Should be tested !

Why not, we could even maybe use the font that is in the corporate identity (Avenir Next), so that the website font is consistent with the rest of Telecom Etude  ?

Yes why not the CA/communication departement agree !


Restore and blocked operations clarity

The call out box states on this page states;

When you perform a restore operation, Azure Storage blocks data operations on the blobs in the ranges being restored for the duration of the operation. Read, write, and delete operations are blocked in the primary location.

Suggesting in the first line that any blobs outside of the range will not be affected.
This doc states;

While a restore job is in progress, blobs in the storage cannot be read or written to.

Suggesting the whole storage account is blocked.
As Operational Backup uses point in time restore I would expect the statements to be the same. Can we get some clarity if the whole storage account or just the blobs in range are blocked and update accordingly please?

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

ID: ac6b8ef7-1727-9f8c-cc35-7f12c25845f4
Version Independent ID: 1f455058-e981-8fb6-299a-cac94b1a2e5b
Content: Point-in-time restore for block blobs - Azure Storage
Content Source: articles/storage/blobs/point-in-time-restore-overview.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

@briggsb9 Thanks for the question! We are investigating and will update you shortly.

@briggsb9 - The first statement is correct. We're updating the second one. The change should go live later today.
@v-amallick - Please verify that my change is acceptable.
#reassign: @tamram
#please-close

Can you confirm if this is the case as the portal it also suggests the whole storage account will be blocked for blobs read/write

@briggsb9 - Just wanted to let you know that I've raised this issue with the Azure Backup team, and they will be updating the message in future iterations of the portal.


What is the feature dimension for person ReID?

Were the feature embedding sizes defined here used for your person ReID experiments link, i.e., 96 for Swin Tiny, 96 for Swin Small, and 128 for Swin Base? Or did you use embeddings of higher dimension? It was not mentioned in the paper. Thanks.

Thanks for your attention. The feature embedding size used for ReID is the same as that for the pre-training, which can be found in link.


AttributeError: module 'fastembed' has no attribute 'TextEmbedding'

What happened?
# Initialize embeddings
embeddings = FastEmbedEmbeddings(
    model_name="BAAI/bge-small-en-v1.5",
    max_length=512,
    batch_size=512,
    threads=8,
    parallel=True
)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
[<ipython-input-17-de927adb1d31>](https://localhost:8080/#) in <cell line: 9>()
      7
      8 # Initialize embeddings
----> 9 embeddings = FastEmbedEmbeddings(
     10     model_name="BAAI/bge-small-en-v1.5",
     11     max_length=512,

3 frames
[/usr/local/lib/python3.10/dist-packages/langchain_community/embeddings/fastembed.py](https://localhost:8080/#) in validate_environment(cls, values)
     92             )
     93
---> 94         values["_model"] = fastembed.TextEmbedding(
     95             model_name=model_name,
     96             max_length=max_length,

AttributeError: module 'fastembed' has no attribute 'TextEmbedding'

What Python version are you on? e.g. python --version
fastembed=0.3.6
python=3.10.10
cuda=12.1
GPU=Tesla T4 Colab Enterprise
OS=Windows 11 x64bit
Version
0.2.7 (Latest)
What os are you seeing the problem on?
Windows
Relevant stack traces and/or logs
No response

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Hi! Are you running your code in colab in browser, which is installed on Windows?

Here is my try:
https://colab.research.google.com/drive/1Q8RBWlD1yiZGRXGsGKtTS3x2EtKr-pK4?usp=sharing
Looks like it works. Feel free to reopen it if you got some more details

Thanks! @I8dNLo


Validate setting only if defined

if settings are not defined and we validate empty string it was failing for tektondashboard url, but anyway we should validate only if value is set.
Signed-off-by: Shivam Mukhade<EMAIL_ADDRESS>
Changes

Submitter Checklist

[x] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[x] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[x] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[x] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[x] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #963 (90d0b15) into main (f4ee846) will decrease coverage by 0.02%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main     #963      +/-   ##
==========================================
- Coverage   63.21%   63.18%   -0.03%
==========================================
  Files          85       85
  Lines        5431     5427       -4
==========================================
- Hits         3433     3429       -4
  Misses       1673     1673
  Partials      325      325

Impacted Files
Coverage Δ

pkg/params/settings/validation.go
81.48% <80.00%> (ø)

pkg/matcher/annotation_matcher.go
93.57% <0.00%> (-0.29%)
:arrow_down:

pkg/acl/acl.go
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

💯 🎯


In-App Purchases support

Is the integration of the oculus in-app purchases planned for the future? If it is not, what would be the best way to integrate them?

Are you referring to https://developer.oculus.com/documentation/platform/latest/concepts/dg-iap/? I don't see those APIs in the Mobile SDK (as of 1.0.3).

Yes, I was referring to that. Sorry, I didn't notice it was in the platform SDK.. so we need to wait for it to be in the mobile SDK first and then it can be implemented in the framework?

I thinks so.

@andrejsinigoj If you don't have any other questions can we close this issue?

Yes, we can close.


Support multi-persons transfer

Sometimes I'm too lazy to do multiple transfer commands, so I could just do
transfer 2 to `@alex-1` `@alex-2` for awesome jobs

We have two ways to split:

(almost) evenly split (the extra goes to a random person)
randomly distribute all the koins

I guess ppl don't transfer much, so maybe just do 1)

Cannot assign this to myself, I'm going to work on this, would have a PR ready soon


Test the UT failure

Description of your changes

Fixes #
I have:

[ ] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer

use another PR to play


Remove [] from allowed path chars

[ and ] are added as allowed path chars.
https://github.com/line/armeria/blob/55504bdf4f09b05adf07a16a076ec28e3fbfccf4/core/src/main/java/com/linecorp/armeria/internal/common/PathAndQuery.java#L68-L69
According to RFC 3986 the valid characters for the path component are:
a-z A-Z 0-9 . - _ ~ ! $ & ' ( ) * + , ; = : @

😱


[ko] Re-arrange categories of Korean contribute doc as same as English

This is a Feature Request

What would you like to be added
Change the weights in _index.md file of Document style overview and Reference Docs Overview in Contribute docs.
Why is this needed
Since the weights are same, and was sorted by first letter of Korean, the order of listed categories in contribute docs of Korean is different with that of English.
Comments
Check the difference and comment me if it is needed.
https://kubernetes.io/ko/docs/contribute/
https://kubernetes.io/docs/contribute/

/language ko
/assign

[영문]

Suggesting content improvements - weight: 10
Contributing new content - weight: 20
Reviewing changes - weight: 30
Localizing Kubernetes documentation - weight: 50
Participating in SIG Docs - weight: 60
Documentation style overview - weight: 80

파일이 생성될 때 weight: 80 으로 설정됨

Reference Docs Overview - weight: 80

파일이 생성될 때 weight: 80 으로 설정됨

Advanced contributing - weight: 98
Viewing Site Analytics - weight: 100

[한국어]

쿠버네티스 문서 한글화 가이드 - weight가 없네요 ㅎㅎ


Fix spellcheck CI task

Description

Related Issue

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

I kept meaning to circle back to this. Thanks @phiggins

I wrote a description for this and must have forgotten to click save. Whoops!


Bug artisan migrate

CreateDataTypeTable is already exist when migrating

Issue closed, we have to rename files in a specific order


Don't load scripts if python is not installed

Separated from whitespace normalization per the last PR conversation.

This feature is merged in #208


How can we use it with vue-class-component?

I am trying examples with https://github.com/vuejs/vue-class-component but it doesn't work like below:
export default class App extends Vue {
    metaInfo = {
      title: 'Title'
    }
}

I trying examples with https://github.com/vuejs/vue-class-component but it doesn't work like below:
export default class App extends Vue {
    metaInfo = {
      title: 'Title'
    }
}

It works like below:
@Component({
    metaInfo: {
      title: title
   })

@vishr please look at https://github.com/vuejs/vue-class-component#adding-custom-hooks
import Component from 'vue-class-component'

Component.registerHooks([
  'metaInfo'
])

@Atinux Thanks for your response, I will have a look it.

@vishr, I use it like that and it works fine on client rendering:
@Component
export default class Home extends Vue {

    public metaInfo(): any {
        return {
            meta: [
                { name: 'description', content: 'Test description' },
                { name: 'keywords', content: 'Test keywords' },
            ],
            title: 'Test Title',
        };
    }
}

But it does not work in SSR. While doing
const { title, meta } = context.meta.inject();

in server.js it says that context.meta is undefined.
Maybe @declandewet or @Atinux can help us?

Just to mention it in case someone else runs into it, the vue-class-component docs on additional hooks are now at https://class-component.vuejs.org/guide/additional-hooks.html, and it's essential that you register the metaInfo hook before defining any components (as described in the docs). Otherwise, metadata won't be updated when a component is initially mounted (although it will update after hot-reload), and you'll get This vue app/component has no vue-meta configuration if you manually call this.$meta().refresh().


Read and update data using Room

Test your database
Issue: tests don't run. FAILURE:
Build failed with an exception.

What went wrong:
Execution failed for task ':app:connectedDebugAndroidTest'.

try upgrading android gradle plugin using upgrade assistant


Python 3.6: SystemError: Bad call flags in PyCFunction_Call. METH_OLDARGS is no longer supported! (pyo3 v0.14.5)

🐛 Bug Reports
Building on python 3.6.15 fails to run on python 3.6.13. Below is the error message:
❯ python
Python 3.6.13 |Anaconda, Inc.| (default, Feb 23 2021, 12:58:59)
[GCC Clang 10.0.0 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import string_sum
>>> string_sum.sum_as_string(1, 2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
SystemError: Bad call flags in PyCFunction_Call. METH_OLDARGS is no longer supported!

If I build the same project using python 3.6.13 on my laptop, it runs successfully.
🌍 Build Environment (Github Workflow)

OS: runs-on: macos-latest, Mac OS X 10.15.7 19H1417
python version: 3.6.15
python installation: actions/setup-python@v2, with: python-version: 3.6, architecture: x64
rust: stable-x86_64-apple-darwin unchanged - rustc 1.55.0 (c8dfcfe04 2021-09-06)
Your PyO3 version: pyo3 v0.14.5

Run Environment (My Laptop)

OS: Mac OS X 11.6
python version: 3.6.13
python installation: conda install python=3.6

💥 Reproducing
lib.rs
use pyo3::prelude::*;

/// Formats the sum of two numbers as string.
#[pyfunction]
fn sum_as_string(a: usize, b: usize) -> PyResult<String> {
    Ok((a + b).to_string())
}

/// A Python module implemented in Rust. The name of this function must match
/// the `lib.name` setting in the `Cargo.toml`, else Python will not be able to
/// import the module.
#[pymodule]
fn string_sum(_py: Python, m: &PyModule) -> PyResult<()> {
    m.add_function(wrap_pyfunction!(sum_as_string, m)?)?;

    Ok(())
}

Cargo.toml
[package]
name = "string_sum"
version = "0.1.0"
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[lib]
crate-type = ["cdylib"]

[dependencies]
pyo3 = { version = "0.14.5", features = ["extension-module"] }

pyproject.toml
[project]
name = "congyu_pyo3_bug"
version = "0.0.1"

[build-system]
requires = ["maturin>=0.11,<0.12"]
build-backend = "maturin"

Installing package:
pip install congyu_pyo3_bug==0.0.1 -i https://test.pypi.org/simple

Reproduce bug:
❯ python
Python 3.6.13 |Anaconda, Inc.| (default, Feb 23 2021, 12:58:59)
[GCC Clang 10.0.0 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import string_sum
>>> string_sum.sum_as_string(1, 2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
SystemError: Bad call flags in PyCFunction_Call. METH_OLDARGS is no longer supported!

The repository where I built this: https://github.com/Congyuwang/congyu_pyo3_debug
Built using GitHub workflow: https://github.com/Congyuwang/congyu_pyo3_debug/blob/master/.github/workflows/blank.yml

@Congyuwang See https://github.com/messense/maturin-action/commit/3c864831d650744ae7b5d3bd65d005fea448bae1
Please give it try with uses: messense/maturin-action@main


Workhour picker wants the both AM/PM and 24h

Workhour picker wants to able to automatic switch between AM/PM and 24h according to local user setting in product.
Related to the issue for 42771 and hope to fix soon

look at the template, there seems no "timepicker"
https://github.com/Teleopti/styleguide/blob/master/directives/time-range-picker/time-range-picker.directive.js#L164

I dont remember but i think we decided to use the uib-timepicker just because it had support for Am/Pm, does it not also have support for 24?
Personaly I think the working-hours-picker could use a general overhaul - i have had my PR about the layout for some time and if we also need to support Am/Pm/24 maybe its time to rethink it a bit?
As far as im aware it is used in outbound, request and forecaster so it wouldnt be a huge job replacing it.

We also have a issue on the Front end board about he overnight button being visible in forecaster, so some more options like that would be nice to have

@tiaoshi the work hour picker contians four level of directives inside. Kind of like workhous picker ->time range picker -> time range picker wraper -> uib timepicker.
The AM/PM to 24h switch is located on the uib timepicker. I have looked into the uib documentation, they support the time format switch and we used it at the time range picker wraper level. The attr for to controll the switch is updated and renamed, and apprently we did not notice it. I guess so. One more thing is we used $local to support the switch but now we are thinking more to do the switch depend on the user setting instead of by $local.
:

More findings:
Initially, the locale is "en-us", and the meridians are "AM" and "PM". The uib-timepicker will take the data but not bind the data to itself. Therefore when the locale is changed, for example, to "de", the uib-timepicker does not update the meridian labels.
When the working-hours-picker begins to render its view, the locale will have been changed. Though I suspect that is guaranteed, that may explain why the working periods take the locale into account, as described in the bug.

Could not be a fast fix so lets open a new issuse for design the new workhour picker :)

After some talking at HQ we were thinking to divide and conquer:
Since the its not really the working-hours-picker that is missing the am/pm/24 option but rather the time-range-picker, it would be best to fix that one first and then try to redesign the working-hours-picker with the time-range-picker as a more loosely connected directive, a better flow, a smaller footprint and better overview of details (we were talking about a week timeline but that might be a bit ambitious)

Yes, the real problem is the uib-timepicker used in the time-range-picker.
To address this issue quickly, one option is copy and paste the uib-timepicker into the styleguide, modify and maintain it by ourselves.
It is just one line of code that prevents us from updating the meridians:
https://github.com/angular-ui/bootstrap/blob/master/src/timepicker/timepicker.js#L22

Do you think it is worth the effort of maintaining the library by on our own for this fix?

Since the uib-timepicker is stable and we use it in a limited scope, I wouldn't expect much maintenance in the future. It is one single file anyway.

Was anything done to the library?
When i was developing the new work hour picker i used the plain uib-timepicker and i had a option for time format, so i allow the user to switch it. This works for now and is requiered since some customers dont want their locale timeformat, but it should really be a global user defined setting saved to the db.


Fixed broken link and broken duplicate links.

Fixed a broken link and tidied up the readme in a few lines. (Duplicates).

Hello Bulutyazilim/awesome-Datascience,
Thank you for your email! Someone from our team will get back to you as
soon as we are back at the office. Our office hours are 9 am to 5 pm ET US.
Thank you!
Lillian Pierson & Team
{#HS:903162748-32948#}


Custom ContainerLoaderInterface by application

Q
A

Documentation
yes

Bugfix
yes

BC Break
no

New Feature
yes

Description

I am currently migrating a project from zf-console to laminas-cli.
This project also works with doctrine and thus currently provides cli-config.php which is parsed by doctrine when using vendor/bin/doctrine.
To avoid having multiple symfony command toolings around, I would like to integrate these commands from doctrine/orm into laminas-cli.

As of now, this would only be possible by manually adding all of the commands to a config file. If there will be new commands, they wont be added automatically to laminas-cli and thus, manual work needs to be done.
I was thinking on how that could work and implemented this as a PoC.

Current workaround to add doctrine commands to laminas-cli:
<?php

declare(strict_types=1);

use Application\Doctrine\DoctrineCommandAbstractFactory;
use Doctrine\ORM\Tools\Console\Command\ClearCache\MetadataCommand;
use Doctrine\ORM\Tools\Console\Command\ClearCache\QueryCommand;
use Doctrine\ORM\Tools\Console\Command\ClearCache\ResultCommand;
use Doctrine\ORM\Tools\Console\Command\GenerateProxiesCommand;
use Doctrine\ORM\Tools\Console\Command\ValidateSchemaCommand;

return (static function (): array {
    return [
        'dependencies' => [
            'factories' => [
                MetadataCommand::class => DoctrineCommandAbstractFactory::class,
                QueryCommand::class => DoctrineCommandAbstractFactory::class,
                ResultCommand::class => DoctrineCommandAbstractFactory::class,
                GenerateProxiesCommand::class => DoctrineCommandAbstractFactory::class,
                ValidateSchemaCommand::class => DoctrineCommandAbstractFactory::class,
            ],
        ],
        'laminas-cli' => [
            'commands' => [
                'orm:clear-cache:metadata' => MetadataCommand::class,
                'orm:clear-cache:query' => QueryCommand::class,
                'orm:clear-cache:result' => ResultCommand::class,
                'orm:generate-proxies' => GenerateProxiesCommand::class,
                'orm:validate-schema' => ValidateSchemaCommand::class,
            ],
        ],
    ];
})();

<?php

declare(strict_types=1);

namespace Application\Doctrine;

use Doctrine\ORM\EntityManagerInterface;
use Doctrine\ORM\Tools\Console\Command\ClearCache\MetadataCommand;
use Doctrine\ORM\Tools\Console\Command\ClearCache\QueryCommand;
use Doctrine\ORM\Tools\Console\Command\ClearCache\ResultCommand;
use Doctrine\ORM\Tools\Console\Command\GenerateProxiesCommand;
use Doctrine\ORM\Tools\Console\Command\ValidateSchemaCommand;
use Doctrine\ORM\Tools\Console\EntityManagerProvider;
use Interop\Container\ContainerInterface;
use InvalidArgumentException;
use Laminas\ServiceManager\Factory\AbstractFactoryInterface;
use Webmozart\Assert\Assert;
use function assert;
use function in_array;

final class DoctrineCommandAbstractFactory implements AbstractFactoryInterface
{
    private const COMMANDS = [
        MetadataCommand::class,
        QueryCommand::class,
        ResultCommand::class,
        GenerateProxiesCommand::class,
        ValidateSchemaCommand::class,
    ];

    public function canCreate(ContainerInterface $container, $requestedName)
    {
        return in_array($requestedName, self::COMMANDS, true);
    }

    public function __invoke(ContainerInterface $container, $requestedName, ?array $options = null)
    {
        if (!in_array($requestedName, self::COMMANDS, true)) {
            throw new InvalidArgumentException(sprintf(
                'Command %s is not explicitly allowed by %s',
                $requestedName,
                self::class
            ));
        }

        return new $requestedName($this->createEntityManagerProvider($container));
    }

    private function createEntityManagerProvider(ContainerInterface $container): EntityManagerProvider
    {
        return new class($container) implements EntityManagerProvider {
            private ContainerInterface $container;

            public function __construct(ContainerInterface $container)
            {
                $this->container = $container;
            }

            public function getDefaultManager(): EntityManagerInterface
            {
                return $this->container->get(EntityManagerInterface::class);
            }

            public function getManager(string $name): EntityManagerInterface
            {
                Assert::startsWith($name, 'doctrine.entitymanager.');
                $entityManager = $this->container->get($name);
                assert($entityManager instanceof EntityManagerInterface);

                return $entityManager;
            }
        };
    }
}

@boesing I'be removed this from the 1.2.0 milestone, as we first want 8.1 support to be pushed out

Closing here as it is possible to do this manually and this would be only convenience to users who wants to use non-laminas-specific symfony commands (e.g. for doctrine, etc.)


Add option to control xbreaks in plot.

Possibly an option called something like “Multiples of 10”?

can use xbreak argument once specified.

done


Change ChooseDeviceType prompt

And make it different based on if choosing new or
existing device.
r? @malgorithms @maxtaco

Good with me if good for @malgorithms

well, the text at the top looks good. I don't know anything about what the code is doing :-)


unsupported operation: can't call foreign function posix_spawnattr_init on OS macos

This foreign function is used by std::process::Command::status(), so it seems like a common enough operation.
Flags: I of course ran with -Zmiri-disable-isolation since I'm doing I/O.
rustc version and arch info:
rustc 1.81.0-nightly (d0227c6a1 2024-06-11)
binary: rustc
commit-hash: d0227c6a19c2d6e8dceb87c7a2776dc2b10d2a04
commit-date: 2024-06-11
host: aarch64-apple-darwin
release: 1.81.0-nightly
LLVM version: 18.1.7

We should probably have a more detailed explanation of the path forward for these errors. Adding shims for the process-spawning functions is uninteresting until someone has a full plan for how to support subprocesses.

This is effectively a duplicate of https://github.com/rust-lang/miri/issues/3374 -- we don't support Command.


Various projects are now depending on .Net Core instead of .Net Standard

Various projects depend on netcoreapp while they used to depend on netstandard. This narrows the availability of these projects to a single platform. (i.e. .Net Core). (.NetStandard can be used from the .Net Framework as well.)
For example, we use here the Microsoft.AspNetCore.Authentication.JwtBearer as a library to validate JWT tokens. Up to version 2.x this works fine, from V3 onward this library has become a .Net Core library and is no longer usable from .Net Standard libraries.
Is there a possibility that these libraries could remain in .Net Standard?

This has been discussed at length here: https://github.com/aspnet/AspNetCore/issues/3753.
If your library depends on ASP.NET Core, then the most sensible option is to move to netcoreapp3.0. If it doesn't, you'll probably want to directly use System.IdentityModel.Tokens.Jwt, which is the package the ASP.NET Core JWT handler relies on under the hood.

@PinpointTownes Alright, wasn't aware of that discussion, thanks for the info :)


Added gl3w

Well, the test bot failed in building python for the dependency. I don't think there's actually anything I can do to fix that, the issue shouldn't be with my formula after all.

Could anyone help in fixing it so it doesn't error while building python for --dependencies-only?

@BrewTestBot test this please.


[SPARK-36130][SQL] UnwrapCastInBinaryComparison should skip In expression when in.list contains an expression that is not literal

What changes were proposed in this pull request?

Fix comment
This PR fix rule UnwrapCastInBinaryComparison bug. Rule UnwrapCastInBinaryComparison should skip In expression when in.list contains an expression that is not literal.

In

Before this pr, the following example will throw an exception.
  withTable("tbl") {
    sql("CREATE TABLE tbl (d decimal(33, 27)) USING PARQUET")
    sql("SELECT d FROM tbl WHERE d NOT IN (d + 1)")
  }

InSet

As the analyzer guarantee that all the elements in the inSet.hset are literal, so this is not an issue for InSet.
https://github.com/apache/spark/blob/fbf53dee37129a493a4e5d5a007625b35f44fbda/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/expressions.scala#L264-L279
Does this PR introduce any user-facing change?

No, only bug fix.
How was this patch tested?

New test.

Can one of the admins verify this patch?

cc @allisonwang-db @cloud-fan

merging to maste/3.2


Updates receiver creators to take a zap.Logger parameter.

Fix for issue #66

Codecov Report

Merging #74 into master will decrease coverage by 0.03%.
The diff coverage is 22.22%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   71.37%   71.33%   -0.04%
==========================================
  Files          91       91
  Lines        6022     6025       +3
==========================================
  Hits         4298     4298
- Misses       1500     1503       +3
  Partials      224      224

Impacted Files
Coverage Δ

receiver/opencensusreceiver/factory.go
82.35% <ø> (ø)
:arrow_up:

receiver/zipkinreceiver/factory.go
100% <ø> (ø)
:arrow_up:

factories/factories.go
100% <ø> (ø)
:arrow_up:

receiver/jaegerreceiver/factory.go
100% <ø> (ø)
:arrow_up:

configv2/example_factories.go
55.33% <ø> (ø)
:arrow_up:

receiver/prometheusreceiver/factory.go
77.5% <0%> (+5.4%)
:arrow_up:

receiver/prometheusreceiver/metrics_receiver.go
63.49% <0%> (-6.69%)
:arrow_down:

cmd/occollector/app/builder/receivers_builder.go
85.18% <100%> (ø)
:arrow_up:

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 07fc0f3...5d034c9. Read the comment docs.


Support TypeScript and Flow

Highlighting TypeScript and Flow would be nice. Not sure how you can achieve both syntaxes.

I haven't used either TS or flow, but I agree it'd be nice.
Are you interested in researching this a bit and submit a prototype PR just to get us started?

It's going to be challenging since type annotation is a syntax feature while highlighting is much more low-level.
Currently Cardinal already gracefully handles TS code quite well (since it operates at the token level), i.e. it doesn't stop working or bail out when encountering type annotations:

Any update here? I'd like to have the @types/cardinal for ts user.


feat: fetch the username and use it in the header

fixes #278

PR Storybook available here

I don't like how the PR storybook is behaving with this, will check it out further.

Ah, turns out my token had expired today apparently, seems to work fine.


Add sync lock to create job functions

Add sync lock to make create job calls thread safe.

This method have a select {} at the end, so my thinking is it may be blocked for a while if we use locking there. On my view i am thinking why not set lastcall = "c" + job-handle or some random to prevent overwriting?

The function we saved is used when we get a response that is JOB_CREATED in the processLoop() function. That's the first time we get the job handle so we can't use that. We also need to be able to find the correct handler at that point so a random value would not work.
The only alternative I can think of that might work would be to make a queue instead of a single function to handle the JOB_CREATED responses we get. However I can't find it documented anywhere in gearman that the server guarantees that we get JOB_CREATED in the same order we sent the SUBMIT_JOB requests.

Putting "c" in inner handler is safe cause it is putting the same handler for all. So no overlapping. But lastcall = 'c' is not safe. This lastcall is only used inside processLoop() when client received an error this lastcall is trying to map the error to last calling job. But this is not safe, can be overridden.
Dig some dipper and find out, this mapping is not required. Job failure returned with WorkFail,
Error is kind of Network Error. So this could be ignored or may be logged only.
cc: @mikespook

The function is not the same on every call because it will use the "result" go channel from the outer scope. This means that when the innerhandle["c"] function is called in processLoop() if there are several callers it will assign the job handle to the wrong job. This in turn means that we will return the wrong handle in the select statement and that means that the results of jobs may be sent as response to the wrong one.

@No-ops , I work with @sadlil and we are trying to solve this issue in our fork https://github.com/appscode/g2.
Based on my understanding, I think this problem can't be solved using a shared TCP connection between client and server. Say, multiple go routines in an application p1 are trying to submit background jobs. First go routine, submits a job with uid_1. Then second go routine submits a job with uid_2. Now, gearman server might return JOB_CREATED response with handle_1 and handle_2 in any order. From the protocol description no ordering in guaranteed. So, the only way to be completely sure, is to use separate TCP connection (separate client). Then gearman server will return JOB_CREATED response with respective job handle to the correct client.
Using a queue will not work, because the JOB_CREATED response does not return any field from the original client request. So, there is no way to associate a request with the response.
All the other client requests can be done in a shared connection, since the request/response both contains the job handle.
I would like to hear your thought, @No-ops .

I agree that the inability to give some sort of id when doing a SUBMIT_JOB that can be used to identify the related JOB_CREATED is an oversight in the gearman protocol. I also agree that my solution will slow down the job creation significantly but seeing that it will only slow it down in the same cases where we otherwise would get a race condition I find it acceptable.
I haven't looked that deep into the gearman protocol but wouldn't WORK_COMPLETE to the client be sent on the same connection that the SUBMIT_JOB was sent on? In that case the whole client library would have to work with a dedicated connection for each job.

I haven't looked that deep into the gearman protocol but wouldn't WORK_COMPLETE to the client be sent on the same connection that the SUBMIT_JOB was sent on? In that case the whole client library would have to work with a dedicated connection for each job.

I am making the assumption that in case of a background job, server will always send JOB_CREATED response before sending WORK_xxx responses. This can be enforced on the server and sounds quite reasonable.

I think @No-ops is correct. There is a race in the function.
While I think maybe we needn't use defer to unlock the mutex.
Do you think to put the Unlock before line  240 & 242 is better?

@mikespook If we unlock at line 242 we don't solve the race condition. The race condition happens because the innerhandler["c"] callback will get a new function with a different result channel before we get a response and go through the select statement. We need the call to complete before we can unlock and allow anyone to write to the innerhandler["c"] callback which means the unlock needs to happen after the select statement.

@No-ops Ops, I think you are right.
The gearman has a bad design of the protocol. That innerhandler["c"] is the tricky design to make handling responses easier. However, it was designed several years ago, maybe, we need a redesign here.
I've added you (@No-ops, @sadlil, and @TamalSaha) as collaborators and let's discuss what's the better solution for this.
PS: I'm not using gearman in production environment anymore, but I'm still interesting working on gearman-go.

Thanks for adding us as collaborator @mikespook . We think the client must be concurrent-safe. Here is my opinion on this issue:

Immediate term: Merge the pr in place to add lock. This will fix the bug.
Medium term: We want to create an inner tcp connection for submission and remove the lock.
Long term: Define next iteration of protocol and fix the underlying issue in spec. This is out of scope of this ticket.

Since this has been open a while now and there's no objections I'm going ahead and merge this.

@No-ops is there any plan to move this forward with proposal?

Do you mean the suggestion @TamalSaha made?
I don't think we can eliminate the risk of having to wait for the gearman server to send JOB_CREATED completely. The "inner connection" that we create must be kept alive until the job finalizes if we want a response so making one for each job would be resource intensive and error prone. I suggest we make a connection pool for creating jobs. That way we can mitigate the problem without risking having too many long running tcp connections alive.

Created a new issue on this #77 so we can move the discussion over there.


228 - Create static pages for BDS 3-Clause License / Privacy / Terms of Use

Issue Number
Closing #228
Purpose/Implementation Notes
NOTE: The changes in 7 files were simply the result of links config changes and minor style tweaks.
Create the following static pages pages and linked them from the footer navigation:

BDS 3-Clause License
Privacy
Terms of Use

Please see the latest UI here.
@dvenprasad Please take a quick look at UI and let me know if any style adjustments necessary 🔎 It mostly matches the current refine.bio except a wrapper container width (used 800px instead of 700px) etc, thank you!
Types of changes

Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

@nozomione the styling looks good to me!


feat(file) implement env var substitution for state files

Introducing support for envirment variable substitution in state files.
This is primarily intended for injecting sensitive data at runtime.
Fix #191

There are two ways to achieve this:

Ask user to include DECK_ prefix to all env vars in the state file.
Implicitly append (and document accordingly) DECK_ prefix to any invocation, eg: ${{ env "FOO" }} will be substituted with the value of DECK_FOO.

@hbagdi

Which one do you prefer?

I find the former less "magical" and less confusing. The latter approach seems acceptable too, if it gets documented well enough.

I'm also in favor of the first option, where users must include the DECK_ prefix on variables in the state file. Using the same variable name in both the state file and environment feels simplest, and users need to be aware of the requirement either way to set the properly-named variables in the environment.

@mflendrich @rainest Perfect. I get an odd sense of happiness we all agree AND use the exact same argument, however small the issue maybe.
I've updated the patch to match our discussion.
I'm not sure what is up with dependabot.

@mflendrich @rainest Friendly ping to review this when you get a chance.

I found one UX gotcha during practical testing: unset variables in the template will (probably, depending on the field type) result in an invalid state, and the resulting error doesn't make the issue cause clear.

Fair. What if we error out early whenever we encounter an unset environment variable?

@rainest I updated the code to include your patch and also added a test case for it. PTAL.
ping @mflendrich


Can't access my admin

- Do you want to request a feature or report a bug?
- What is the current behavior?
- If the current behavior is a bug, please provide the steps to reproduce.
- What is the expected behavior?

- Please mention your CMS, node.js, and operating system version.

- Please link or paste your config.yml below if applicable.

@Zinenda Please ask on our Gitter channel: https://gitter.im/netlify/NetlifyCMS


Added bsc Jetswap btcb-bnb

mooJetswapBTCB-BNB
vault: https://bscscan.com/address/0xda93aF3b269BAB2A47D1808c6CDCDee7A861bF65#code
strategy: https://bscscan.com/address/0xdEd0e7C71960502553420045f38292750D5fA4Cd#code
beefy API PR: beefyfinance/beefy-api#333

Same with this one. Contracts on BSC need to inherit the Gas Throttler contract.


empty(); method in Basket

Add method to empty the basket after the purchase

Method done but we need to refresh the GUI


cert-manager: fast-forward to upstream dab1d42d

Update chart for v0.2.5 release (jetstack/cert-manager#518)

This is an automated PR, generated by a new script I am testing.
In future, these kinds of PRs will be made by a bot user 😃

/lgtm


Change SearchAsync signature

Pull Request
What does this PR do?
The old signature was a bit akward, it took as first paramater a string for the query and a second parameter an optional SearchQuery object where we store later the first parameter into the Q property of the SearchQuery.
// Old signature
public async Task<SearchResult<T>> SearchAsync<T>(string query,
            SearchQuery searchAttributes = default(SearchQuery), CancellationToken cancellationToken = default)
{
}

The main issue was that the SearchQuery can be created with the default constructor which is wrong. The SearchQuery object must be created by passing a search query to the constructor to be in a valid state.
The new signature is now always using the SearchQuery parameter like in other SDK
// New signature
public async Task<SearchResult<T>> SearchAsync<T>(SearchQuery searchQuery, CancellationToken cancellationToken = default)
{
}

PR checklist
Please check if your PR fulfills the following requirements:

[X] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[X] Have you read the contributing guidelines?
[X] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Hi @juchom,
Thanks a lot for your RP but the old signature although akward indeed is the right one. For example in other SDK it's:
In php:
    public function search(?string $query, array $searchParams = [], array $options = [])

In python:
    def search(self, query: str, opt_params: dict[str, Any] | None = None) -> dict[str, Any]

In Go:
    func (i Index) Search(query string, request *SearchRequest) (*SearchResponse, error)

It was decided by the integration team, that the signature always proposes the first parameter to be the query as string.
So I think maybe the issue is more how the SearchQuery is built after that and also I don't think it was a good naming SearchQuery is should be something like SearchParam or SearchRequest maybe.
I can see that your solution brings clarity to the code but we try as much as possible to keep a certain consistency between the different SDKs

Sorry for the mistake, when I worked on the samples, I was pretty sure Java and Rust were using it like in this PR.
I understand what you want to do. You are right the SearchQuery object has a bad name it should be SearchParameters and should not expose a Q property.
I close this PR, because it's not in line with other SDKs. I will have a look later at this.
Thanks for the review 👍

Yes I'm sorry but thank you very much for this PR anyway ❤

This message is sent automatically
Thanks again for contributing to Meilisearch :heart:
If you are participating in Hacktoberfest, and you would like to receive some gift from Meilisearch too, please complete this form.


gotemplate: 3.9.2 -> 3.10.1

Version bump to the newly released 3.10.1, no big changes.
changelog for 3.10.0
changelog for 3.10.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Repeated "gotemplate" instad of using pname as requested (I also run the file through nixfmt, while I was at it).
Re-built locally on x86_64-linux and tested basic functionality.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356248

x86_64-linux

:white_check_mark: 1 package built:

gotemplate

aarch64-linux

:white_check_mark: 1 package built:

gotemplate

x86_64-darwin

:white_check_mark: 1 package built:

gotemplate

aarch64-darwin

:white_check_mark: 1 package built:

gotemplate

@GaetanLepage @drupol Thanks for reviewing this!


How to achieve similar features like Object.assign?

First: store(key,{id:1,name:'John'})
I get: {"id":1,"name":"John"}
Then: store(key,{age:40})
I get: {"age":40}
How can I expect to get: {"id":1,"name":"John","age":40}
Thanks!
(I translated these into English with Tencent Mr. Translator :))

You'll have to use Object.assign. We don't currently have any sort of store.combine(key, newVal) function, though that's not a half-bad idea...
First: store(key,{id:1,name:'John'})
Then: store.set(key, Object.assign(store.get(key), {age:40}))

Seeing as such uses have been desired before, i decided to see how hard it'd be to implement a reasonable store.add(key, data) that would concat to an array, merge two objects, or + any other combination of types. Turns out it wasn't hard. Version 2.7.0 was just released with this feature. Enjoy!


Merge latest master from parent repository

I just realized that my exponential backoff changes were merged into a separate branch in the parent repo, not master. That's why they don't also show up here (with https://github.com/Gusto/gh-ost/pull/4 open). I asked the maintainer if they're still undergoing testing.

Accepted by nikhilmat!


Add support for DELETE, PUT, POST, MERGE operation

placeholder issue , will be specified in more detail
Library / DirectBuilder usage = experimental prototype for this feature.

[x] @AlapanGhosh  - add support for generating GET and DELETE url parts for entities for DirectBuilder usage only.

PR #72

[x] @AlapanGhosh  - add support for generating PUT  - also only url part

PR #81

[x] @AlapanGhosh  - add support for generating POST  - solve http body payload fuzzing

PR #81

[x] @AlapanGhosh  - add support for generating MERGE  - solve http body payload fuzzing

PR #91

[x] @AlapanGhosh  - developer (library usage, DirectBuilder) documentation - https://github.com/SAP/odfuzz/blob/master/doc/http_methods.rst

CLI USAGE

[ ] @phanak-sap - refactor fuzzer.py, Query class and most importantly the  def build_string() usage for different HTTP methods.

Here clashes code flow of normal CLI usage and DirectBuilder usage (going from "below" from entities.py); also clash of configuration by env. variables and Config class (CLI usage) versus constructors/functions parameters configuration in DirectBuilder usage as python library.
Query class also does not ONLY cover bulding an url part, but also has properties relevant to fuzzing process itself (generation+mutation) and is also closely tied with specific database  (MongoDB, line 1031 self._id = ObjectId() ), making the necessary separation of fuzzer.py module into smaller and more isolated modules more complicated.
Dispatcher itself expects only sending GET HTTP requests at the moment.

[ ] @phanak-sap - add support for GET and DELETE for CLI usage of odfuzz also.

[ ] @phanak-sap  - bump versionfor this new feature

Delete queries with filter option
https://stackoverflow.com/questions/33279744/odata-delete-with-filter

Hi,
I looked through the v2 operations documentation.
Based on sections 2.8 and 2.11, and also the above attached stackoverflow thread, we can assume DELETE wont be taking any query options, other than while deleting links.
Which would mean the first step would be to decouple the invocation of the query-options generation in the workflow.
Any pointers on where and how I can safely stop the query-options generation?
Thanks

@AlapanGhosh, I believe you have to modify the following method:
https://github.com/SAP/odfuzz/blob/41d244111b0255854bcff3ecbc68bf679a59312c/odfuzz/fuzzer.py#L353-L361
Query options are generated and added to a specific query in the for loop. The method build_string() assembles a final query string from an entity's URI and query options' values:
https://github.com/SAP/odfuzz/blob/41d244111b0255854bcff3ecbc68bf679a59312c/odfuzz/fuzzer.py#L1115-L1133
As long as a query does not reference any query options, the for loop will not be executed.
Also, I recommend you to take a look at the method _add_appendix() which is called from the method build_string(). This method appends additional query options to the URL by default:
https://github.com/SAP/odfuzz/blob/41d244111b0255854bcff3ecbc68bf679a59312c/odfuzz/fuzzer.py#L1164-L1168

Hi @phanak-sap
As per our last discussion you mentioned you have not committed the n-odata-server  test application. So, would you be in a position to commit so that I can install the test app locally and test out the DELETE PoC?
Thanks

@AlapanGhosh  I only tested that the  n-odata-server (from samples) produces valid metadata, so it is not stopped on first step. Then I went to vacation as discussed. So at the moment I don't have the sample app (but I guess you can use the internal fiorigoat for testing first changes)
Also, I am against direct modifying the  generate_options() method in the fuzzer.py. It would be better, to as part of module de-coupling, to move anything relevant to URL query generation - this method and accompanying utilities - out of fuzzer.py to most probably new module or next to Queriable (entities.py).
Remember, it would be good to move towards like a library code, that would generate URLs (and after that, mutates them) for provided metadata, without networking and database and CLI / gevent runtime.

I am closing this issue with no CLI task implemented, just covering the support in the DirectBuilder only.
There is currently discussed variant that odfuzz will in the future use only the DirectBuilder in some core module, to better modularize the project. DispatchedBuilder entanglement with practically all other parts of odfuzz (e.g. in issue description) make it really hard to maintain. In the future there is also possibility to remove mongoDB dependency (and perhaps even drop the mutation part), in favor of more CLI usage with sqlite/files only.


Adjust class weights to improve performance

Following the successfull implementation of the class weights in issue #2, here I will try to adjust the class weights to get better performance, spceifically on the classes with low class_wise_IU.

Using the weights implemented in the SCDD thesis as w3
class_weights = [     0.2,  # "bckgnd"     1.0,  # "sp multi"     1.0,  # "sp mono"     1.0,  # "sp dogbone"     3.0,  # "ribbons"     1.0,  # "border"     1.0,  # "text"     1.0,  # "padding"     1.0,  # "clamp"     1.0,  # "busbars"     1.0,  # "crack rbn edge"     10.0, # "inactive"     1.0,  # "rings"     1.0,  # "material"     20.0, # "crack"     10.0, # "gridline"     1.0,  # "splice"     1.0,  # "dead cell"     1.0,  # "corrosion"     1.0,  # "belt mark"     1.0,  # "edge dark"     1.0,  # "frame edge"     1.0,  # "jbox"     1.0   # "meas artifact" ]

Class Name
Class Index
IoU
Run Name

bckgnd
0
0.855889906958644
train_SCDD_20211104_w3_fit_test

sp multi
1
0.497968055949343
train_SCDD_20211104_w3_fit_test

sp mono
2
0.622260140508315
train_SCDD_20211104_w3_fit_test

sp dogbone
3
0.0
train_SCDD_20211104_w3_fit_test

ribbons
4
0.536192004891844
train_SCDD_20211104_w3_fit_test

border
5
0.399513103572069
train_SCDD_20211104_w3_fit_test

text
6
0.0
train_SCDD_20211104_w3_fit_test

padding
7
0.989229429576983
train_SCDD_20211104_w3_fit_test

clamp
8
0.0
train_SCDD_20211104_w3_fit_test

busbars
9
0.246435845213849
train_SCDD_20211104_w3_fit_test

crack rbn edge
10
0.0
train_SCDD_20211104_w3_fit_test

inactive
11
0.1127481933628
train_SCDD_20211104_w3_fit_test

rings
12
0.0
train_SCDD_20211104_w3_fit_test

material
13
0.0203970381138418
train_SCDD_20211104_w3_fit_test

crack
14
0.146418134040619
train_SCDD_20211104_w3_fit_test

gridline
15
0.259917261323015
train_SCDD_20211104_w3_fit_test

splice
16
0.0
train_SCDD_20211104_w3_fit_test

dead cell
17
0.0
train_SCDD_20211104_w3_fit_test

corrosion
18
0.0872898849896785
train_SCDD_20211104_w3_fit_test

belt mark
19
0.0
train_SCDD_20211104_w3_fit_test

edge dark
20
0.00228194726166328
train_SCDD_20211104_w3_fit_test

frame edge
21
0.325072399198039
train_SCDD_20211104_w3_fit_test

jbox
22
0.0
train_SCDD_20211104_w3_fit_test

meas artifact
23
0.0
train_SCDD_20211104_w3_fit_test

Adjusting weights and setting all the classes with 0 IoU to have the weight equal to 10, weights as w4
class_weights = [     0.2,  # "bckgnd"     1.0,  # "sp multi"     1.0,  # "sp mono"     10.0,  # "sp dogbone"     3.0,  # "ribbons"     1.0,  # "border"     10.0,  # "text"     1.0,  # "padding"     10.0,  # "clamp"     1.0,  # "busbars"     10.0,  # "crack rbn edge"     10.0, # "inactive"     10.0,  # "rings"     1.0,  # "material"     20.0, # "crack"     10.0, # "gridline"     10.0,  # "splice"     10.0,  # "dead cell"     1.0,  # "corrosion"     10.0,  # "belt mark"     1.0,  # "edge dark"     1.0,  # "frame edge"     10.0,  # "jbox"     10.0   # "meas artifact" ]

Adjusting weights and setting all the classes with 0 IoU to have the weight equal to 20, weights as w5
class_weights = [     0.2,  # "bckgnd"     1.0,  # "sp multi"     1.0,  # "sp mono"     20.0,  # "sp dogbone"     3.0,  # "ribbons"     1.0,  # "border"     20.0,  # "text"     1.0,  # "padding"     20.0,  # "clamp"     1.0,  # "busbars"     20.0,  # "crack rbn edge"     10.0, # "inactive"     20.0,  # "rings"     1.0,  # "material"     20.0, # "crack"     10.0, # "gridline"     20.0,  # "splice"     20.0,  # "dead cell"     1.0,  # "corrosion"     20.0,  # "belt mark"     1.0,  # "edge dark"     1.0,  # "frame edge"     20.0,  # "jbox"     20.0   # "meas artifact" ]

Class Name
Class Index
IoU
Run Name

bckgnd
0
0.835278849565681
train_SCDD_20211104_w5_e1_speFull

sp multi
1
0.0853787682677146
train_SCDD_20211104_w5_e1_speFull

sp mono
2
0.462534478272183
train_SCDD_20211104_w5_e1_speFull

sp dogbone
3
0.0
train_SCDD_20211104_w5_e1_speFull

ribbons
4
0.487104627944925
train_SCDD_20211104_w5_e1_speFull

border
5
0.267594510161816
train_SCDD_20211104_w5_e1_speFull

text
6
0.0
train_SCDD_20211104_w5_e1_speFull

padding
7
0.958277875711479
train_SCDD_20211104_w5_e1_speFull

clamp
8
0.0
train_SCDD_20211104_w5_e1_speFull

busbars
9
0.0
train_SCDD_20211104_w5_e1_speFull

crack rbn edge
10
0.0
train_SCDD_20211104_w5_e1_speFull

inactive
11
0.188680822604915
train_SCDD_20211104_w5_e1_speFull

rings
12
0.0
train_SCDD_20211104_w5_e1_speFull

material
13
0.000229326239508324
train_SCDD_20211104_w5_e1_speFull

crack
14
0.11961398186102
train_SCDD_20211104_w5_e1_speFull

gridline
15
0.203175669564992
train_SCDD_20211104_w5_e1_speFull

splice
16
0.0
train_SCDD_20211104_w5_e1_speFull

dead cell
17
0.0
train_SCDD_20211104_w5_e1_speFull

corrosion
18
0.164641885766092
train_SCDD_20211104_w5_e1_speFull

belt mark
19
0.0
train_SCDD_20211104_w5_e1_speFull

edge dark
20
0.00241304219881113
train_SCDD_20211104_w5_e1_speFull

frame edge
21
0.119280553883202
train_SCDD_20211104_w5_e1_speFull

jbox
22
0.0
train_SCDD_20211104_w5_e1_speFull

meas artifact
23
0.0
train_SCDD_20211104_w5_e1_speFull

w6 = w3 + sp dogbone = 50.0
class_weights = [     0.2,  # "bckgnd"     1.0,  # "sp multi"     1.0,  # "sp mono"     50.0,  # "sp dogbone"     3.0,  # "ribbons"     1.0,  # "border"     1.0,  # "text"     1.0,  # "padding"     1.0,  # "clamp"     1.0,  # "busbars"     1.0,  # "crack rbn edge"     10.0, # "inactive"     1.0,  # "rings"     1.0,  # "material"     20.0, # "crack"     10.0, # "gridline"     1.0,  # "splice"     1.0,  # "dead cell"     1.0,  # "corrosion"     1.0,  # "belt mark"     1.0,  # "edge dark"     1.0,  # "frame edge"     1.0,  # "jbox"     1.0   # "meas artifact" ]

w6 = w3 + sp dogbone = 50.0
class_weights = [     0.2,  # "bckgnd"     1.0,  # "sp multi"     1.0,  # "sp mono"     50.0,  # "sp dogbone"     3.0,  # "ribbons"     1.0,  # "border"     1.0,  # "text"     1.0,  # "padding"     1.0,  # "clamp"     1.0,  # "busbars"     1.0,  # "crack rbn edge"     10.0, # "inactive"     1.0,  # "rings"     1.0,  # "material"     20.0, # "crack"     10.0, # "gridline"     1.0,  # "splice"     1.0,  # "dead cell"     1.0,  # "corrosion"     1.0,  # "belt mark"     1.0,  # "edge dark"     1.0,  # "frame edge"     1.0,  # "jbox"     1.0   # "meas artifact" ]


Synology Sends an error every minute to the logs relating the converting temp to Farenheit

Home Assistant release with the issue:
0.79.3
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Synology
Description of problem:
Error in the log
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity.py", line 234, in async_update_ha_state
    state = self.state
  File "/usr/src/app/homeassistant/components/sensor/synologydsm.py", line 240, in state
    return round(attr * 1.8 + 32.0, 1)
TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'

Additional information:

This is resolved.


fix async input.

The async-input is not really async. We create a thread to peek input event from X, but the event is pushed into FREERDP_INPUT_MESSAGE_QUEUE as message and FREERDP_INPUT_MESSAGE_QUEUE is processed in main client thread. Therefore the input event is still processed in main client thread actually.
The fix make the message also be processed in input thread.
The original issue is discussed in #2338. When we have heavy image update, the input event will hardly  get a chance to be handled. In this case we may want to use async input but it does't actually work in this case.
But I'm not sure if I understand the purpose of async input correctly.

@freerdp-bot test

@realjiangms there are different "types" of async (input, update, channel, transport). What did you test your pull request with?

@bmiklautz I tested with +async-input, without any other 'async' inputs. The fix proposed is for +async-input
Actually I agree that this fix is not really necessary. The issue reported in #2338 could be resolved by using +async-transport or +async-update instead of +async-input. (+async-update may finally panic with out-of-memory as we have unlimited update message queue)
I raise this pull-request just for discussion on the 'meaning' of async-input, and the difference in detail behavior for 'async-input' between (android/X11) and (Windows/Mac).
These days I kept trying +async-transport to test if it could workaround issue in #2338, unfortunately I found another race condition which could cause thread hung.
After several day's investigation, I've just found the root cause and I'll reorganize wording at this weekend.to report it

@realjiangms thanks for the information.

I would want to close this pull request as it's not really necessary. The issue could be resolved by using +async-transport instead of +async-input. We don't even need +async-input in x11 client.
The hung issue mentioned in previous note is described in #2519

The hung issue is completely fixed by #3364


Added  MAXSUBARR from Codechef

Maximum Subarray (MAXSUBARR) Solution from Codechef

Star the repo and consider giving me a follow ;) thanks


Add prefix option to change output sitemap filenames

Description (required)
Add prefix to sitemap options so that the filename can be changed optionally.
For Astro version: 4.4. See astro PR https://github.com/withastro/astro/pull/9846

Is this an upcoming feature? I tried to run this on a stackblitz instance and it didn't worked there 😕

Yes, it is.
It will be released in astro v4.4.

I could not find it in their milestone 😕, can you pinpoint it ?

I have received this comment so I am assuming it will be released in v4.4.
https://github.com/withastro/astro/pull/9846#issuecomment-1941558211

Ah, I see everyone's confusion! Because this is an integration minor, it doesn't release necessarily with Astro 4.4, but rather with the next version of @astrojs/sitemap! Integration packages release separately from core, and could be together but might not be!
I'll update the PR description!

!coauthor

I share here that revert https://github.com/withastro/astro/pull/9846.
detail: https://github.com/withastro/astro/pull/10179

Hi @ktym4a !
I've checked with our core platform team, and they think the best thing to do with the reverting of the other PR is to close this docs PR right now.
This PR can be reopened if we go with this solution in future! Or, if another solution is created, a new Docs PR can be created!
So, I will close this one right now, but I think we are in a good place to know how to document a similar solution if it's implemented! 🙌


Typo

There is a typo in this link: Use scheduled events to proactively response to VM impacting events
I believe the word should be "respond".

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

ID: 948b29e3-d488-0a0e-89c7-42849a93522d
Version Independent ID: 8c986086-9343-4b99-ae53-f4fd1159d4f8
Content: Manage the availability of Windows VMs in Azure - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/manage-availability.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for bringing this to our attention. I have created a PR with the update, changes will be live shortly.


Make isLength() / isByteLength() accept options {min, max}

Usage:

isLength(str, {min: 4, max: 6})
isLength(str, {min: 4})
isLength(str, {max: 10})

Because:

More consitent with isInt({min:0, max:0}) and isFloat({min:0, max: 0})
More consitent with isCurrency(str, options)
Avoids confusions like #465
Allows isLength({max: 10})
Backwards compatible.
Better readability:

isLength(str, 4) reads like (str.length == 4), but actually is (str.length >= 4)
Before: isLength(str, 4, 10) what do 4 and 10 mean?
After: isLength(str, {min: 4, max:10})

closes #474

Looks good, thanks!

Nice PR btw 👌

Thanks :)

Thanks :+1:
Only now realised that the README will display the new api, even though it's not available until a new version is released. Should 2.5.1 be published since it is a non breaking change?

I've published 4.5.1 with the changes.


Add ebpf library build and commit to CI

Resolve #5.
This PR adds two new CI pipelines: for building docker image for library build, and for building and commiting library using this docker image. Despite failing due to the bug (I've sent a fix request to authors), library was built and is commited.

Tested auto-generated libraries on CentOS 7 with 3.10 and 4.19, both work.


LoggingLevelSwitch support

Does this sink support runtime changes of LogEventLevel? If not then it would be really helpful to implement such option.

Hi @raV720!
Thank you for writing us. The log level setting is not managed by this sink but can be controlled by Microsoft.Extension.Logging or by Serilog.Extension.Logging respectively. It should be able to update the log level property depending on the source of the setting (appsettings).
Further reading:
https://devblogs.microsoft.com/dotnet/asp-net-core-logging/
https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line#change-log-levels-in-a-running-app

So according to https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line#change-log-levels-in-a-running-app it is not possible to change log level at runtime unless modifying appsetting.json?
Isn't it just matter of adding levelSwitch parameter in line:
https://github.com/serilog-mssql/serilog-sinks-mssqlserver/blob/216330e944efa85cf5ebe2c3c4a28814fc50d583/src/Serilog.Sinks.MSSqlServer/Configuration/Extensions/Microsoft.Extensions.Configuration/LoggerConfigurationMSSqlServerExtensions.cs#L131

The code you are referring to is only called once during initialization the logger. It cannot be called again later during runtime of your app.

Yes, but if I understand correctly: passed levelSwitch can be used later during runtime to change log level.

Ah, got ya! I will look into that.

We just released the preview version  6.2.0-dev-00041 to nuget.org which features a way to pass a LevelSwitch via the sink options object.
Please try it out and let us know if you find any problems.


Improve the Kubernetes Api Functionality

Our service discovery classes are badly implemented, refactoring a business dsl is required

A single common library for service/pod discovery for akka cluster, remote interactions, remote event listeners


Assignment

There should be a draft of this already
Location: http://rman.eeb.utoronto.ca/01-basicr/01-01-coding-basics.html#running


monir:修改节点名称

Codecov Report

Merging #457 (02761d2) into v2.6.x_develop (7b9e58e) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           v2.6.x_develop     #457   +/-   ##
===============================================
  Coverage           62.62%   62.62%
===============================================
  Files                 441      441
  Lines               27030    27030
===============================================
  Hits                16927    16927
  Misses              10103    10103

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 7b9e58e...02761d2. Read the comment docs.


Funkin'Team.FridayNightFunkin' version v2.8

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Instead of Funkin'Team.FridayNightFunkin', FunkinTeam.FridayNightFunkin would be proper


BigQuery.py file is out of date with current provider package

Describe the bug
The KWARGS in the Hooks of this file need to be updated to reflect the current KWARGS of the airflow provider package.
Additional context
Some of the Kwargs are in the BigQueryHook: use_legacy_sql, location

hi @erdos2n, Can you please paste the link of the file you're mentioning for the issue? Do you have an example DAG/script which is complaining about not accepting those parameters? I also see have an example DAG accepting location in the operators in this DAG file https://github.com/astronomer/astronomer-providers/blob/dbbd110c230ae22a6dec0fc850ca89cb1dc84725/astronomer/providers/google/cloud/example_dags/example_bigquery_queries.py#L66
As far as I can see, in the module https://github.com/astronomer/astronomer-providers/blob/dbbd110c230ae22a6dec0fc850ca89cb1dc84725/astronomer/providers/google/cloud/hooks/bigquery.py#L25, they use the sync hook from the upstream provider, so I'm guessing it should accept all the kwargs

hi @erdos2n I am closing this for now, but feel free to reopen it if you've more comments/details.
cc: @phanikumv


standard.lintFiles() doesn't use process.cwd()

Here's what I did
Files

package.json
{
  "name": "testcase",
  "version": "1.0.0",
  "type": "module",
  "dependencies": {
    "standard": "17.1.0"
  }
}

index.js
import fs from "node:fs/promises";
import process from "node:process";
import standard from "standard";

console.log(await fs.readFile("foo/bar.js", "utf8"));
console.log(await standard.lintFiles(["foo/bar.js"]));

process.chdir("foo");
console.log(await fs.readFile("bar.js", "utf8"));
console.log(await standard.lintFiles(["bar.js"]));

foo/bar.js
var baz = 'qux'

Steps

npm install
node index.js

What I expected to happen
var baz = 'qux'

[
  {
    filePath: '/home/regseb/testcase/foo/bar.js',
    messages: [ [Object], [Object] ],
    suppressedMessages: [],
    errorCount: 1,
    fatalErrorCount: 0,
    warningCount: 1,
    fixableErrorCount: 0,
    fixableWarningCount: 1,
    source: "var baz = 'qux'\n",
    usedDeprecatedRules: [Getter]
  }
]
var baz = 'qux'

[
  {
    filePath: '/home/regseb/testcase/foo/bar.js',
    messages: [ [Object], [Object] ],
    suppressedMessages: [],
    errorCount: 1,
    fatalErrorCount: 0,
    warningCount: 1,
    fixableErrorCount: 0,
    fixableWarningCount: 1,
    source: "var baz = 'qux'\n",
    usedDeprecatedRules: [Getter]
  }
]

What seems to have happened
var baz = 'qux'

[
  {
    filePath: '/home/regseb/testcase/foo/bar.js',
    messages: [ [Object], [Object] ],
    suppressedMessages: [],
    errorCount: 1,
    fatalErrorCount: 0,
    warningCount: 1,
    fixableErrorCount: 0,
    fixableWarningCount: 1,
    source: "var baz = 'qux'\n",
    usedDeprecatedRules: [Getter]
  }
]
var baz = 'qux'

/home/regseb/testcase/node_modules/eslint/lib/cli-engine/file-enumerator.js:320
                    throw new NoFilesFoundError(
                          ^

NoFilesFoundError: No files matching 'bar.js' were found.
    at FileEnumerator.iterateFiles (/home/regseb/testcase/node_modules/eslint/lib/cli-engine/file-enumerator.js:320:27)
    at iterateFiles.next (<anonymous>)
    at CLIEngine.executeOnFiles (/home/regseb/testcase/node_modules/eslint/lib/cli-engine/cli-engine.js:797:48)
    at ESLint.lintFiles (/home/regseb/testcase/node_modules/eslint/lib/eslint/eslint.js:551:23)
    at StandardEngine.lintFiles (/home/regseb/testcase/node_modules/standard-engine/index.js:89:41)
    at file:///home/regseb/testcase/index.js:11:28 {
  messageTemplate: 'file-not-found',
  messageData: { pattern: 'bar.js', globDisabled: false }
}

Node.js v20.10.0

Standard doesn't use the current directory. It uses the current directory when importing "standard":

https://github.com/standard/standard-engine/blob/12c96e5/index.js#L105
https://github.com/standard/standard-engine/blob/12c96e5/index.js#L36
https://github.com/standard/standard/blob/d1cc665/index.js#L5

Looks like it might be relatively simple to add cwd = process.cwd() in lib/options? Want to open a PR for that?

Want to open a PR for that?

I opened the pull request https://github.com/standard/standard-engine/pull/329

Thanks for taking the time to submit the PR. I must apologize, I'm somewhat confused on the use case you reference in the PR. It feels like you may want to investigate spawning a child process per linter instead of changing the process dir. As @wesleytodd mentioned, adjusting the cwd in flight can get hairy because so many things can rely on it.
Nonetheless, your issue as described is currently possible by simply adjusting the cwd property on standard before linting the files. Which utilizing your sample code looks like the following:
import fs from "node:fs/promises";
import process from "node:process";
import standard from "standard";

console.log(await fs.readFile("foo/bar.js", "utf8"));
console.log(await standard.lintFiles(["foo/bar.js"]));

process.chdir("foo");
console.log(await fs.readFile("bar.js", "utf8"));
standard.cwd = process.cwd()
console.log(await standard.lintFiles(["bar.js"]));

Tested locally with node 20 and standard 17 on an intel macOS and it worked fine for me.

I worked around the bug with this code (and the directory change works):
const results = await standard.lintFiles(["bar.js"], {
    cwd: process.cwd(),
});

I've opened this issue and a PR to fix the problem in Standard so that everyone can benefit from it. And also because it's strange to pass the default value; you feel like removing it because it seems useless.
If you don't want to correct this problem, I think the documentation should be changed to reflect reality.

Confirmed. I didn't understand then. The workaround (what I thought you were implying was not working properly) is what I believe should be done in this case.

it's strange to pass the default value; you feel like removing it because it seems useless.

I concede your point: we should not require a user to specify a default property. On the other hand, I remain convinced it's better practice to avoid defaulting to the process at function call time instead setting it when the class constructor is called. The existing code allows for this. In fact, I believe we would find the majority of users are not using standard in this manner anyway, but are executing it via the cli or some manner of integration. For those reasons, I'm -1 on accepting the adjustment and +1 on correcting the documentation.
I'll submit a preliminary PR, but allow time for you or others to weigh in if you feel I've missed something. Thanks again for raising this issue.


[WIP] Updated details view per recommendations from Keir

In this PR:

Added angular material elements
Layout uses angular material instead of boostrap
Removed a bunch of "px" from "0px" in CSS

This PR is intended as a "first pass." I tagged it WIP because it's not quite done, but I wanted to get something reviewable out there before I spend much more time fine-tuning it.
Ex. You'll notice that the <app-header> used in Keir's mock-up is missing from this implementation. That's because I'm not sure how to use  with the correct icon for the app (which is currently using <portlet-icon> directive.
Screenshots

Looks cool so far!

Coverage remained the same at 15.509% when pulling ecaea786c68156ae2b8427f427e4012e2914971f on thevoiceofzeke:details into 26b9bc9575e4137ad5835076b7871f0ce950761b on UW-Madison-DoIT:master.

Looks good so far. If you wanted to read more about the app-header checkout the docs http://uw-madison-doit.github.io/uw-frame/latest/#/md/directives . You may need to use the app-header-two-way-bind directive to get it to work. I also kind of like the no app-header for the details, so maybe run that by Jess Jones (Keir's replacement)

testing out @jjones770 mentioning.  Everyone can ignore

Coverage remained the same at 15.509% when pulling c65ec2acafb89163abb38d6f94feb125a46530bd on thevoiceofzeke:details into 26b9bc9575e4137ad5835076b7871f0ce950761b on UW-Madison-DoIT:master.

Coverage remained the same at 15.509% when pulling e053483b41ab50780e4bb6d60a5d8c3fd4f5b9b6 on thevoiceofzeke:details into 26b9bc9575e4137ad5835076b7871f0ce950761b on UW-Madison-DoIT:master.


Update ex_doc to 0.21.1

The old version of ex_doc was not fetching available lexers from Makeup.Registry

Looks good but keep in mind that once ex_doc depends makeup_erlang, we won't be able to depend on ex_doc, we will have to do a similar schema to makeup_elixir.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:

we will have to do a similar schema to makeup_elixir

ExDoc will never have to depend on makeup_erlang. The whole point of lexer discovery is that ExDoc will automatically be able to detect the erlang lexer if it is installed. Because ExDoc is mostly used to document Elixir projects, I keep makeup_elixir as a dependency, but it could be made optional too.

We plan to make ex_doc work with Erlang projects as soon as it adopts EEP48 and that’s when we will depend on it, but it is still a couple months ahead of us.


problem in ZGDanmakuDispatcher.java

what's the meaning of "if (nextRendererList.size() + mLines < MAX_READERING_NUMBER) " should it be nextRendererList.size() <MAX_READERING_NUMBER

It just means that at this frame at most mLines danmaku have finished renderering and ran out of the screen.
Of course it's not a fixed point that you can feel free to remove mLines which is OK.
You also see that const MAX_READERING_NUMBER is changable for developers.

It just means that at this frame at most mLines danmaku have finished renderering and ran out of the screen.
Of course it's not a fixed point that you can feel free to remove mLines which is OK.
You also see that const MAX_READERING_NUMBER is changable for developers.


Error uploading file

Server: Mobius 0.5.6
Server OS: Windows
Client: HL 1.2.3 PPC
Client OS: Mac OS 9
Emulator: QEMU PPC
Mobius server reports the following error when trying to upload a file from the client:
2022-06-19T20:25:08.160-0600    info    Received Transaction    {"login": "guest", "name": "ben", "RequestType": "tranUploadFile"}
2022-06-19T20:25:08.178-0600    info    File upload started     {"transactionRef": "YVlYxw==", "dstFile": "c:\\hlserver/Files///HotlineClient123PPC.sit"}
2022-06-19T20:25:08.229-0600    error   file transfer error     {"reason": "rename c:\\hlserver/Files///HotlineClient123PPC.sit.incomplete c:\\hlserver/Files///HotlineClient123PPC.sit: The process cannot access the file because it is being used by another process."}

If I view the folder in Windows Explorer, I see that the file is not renamed...

Running the same build on WSL allows for a file upload w/o error.
2022-06-19T20:32:08.086-0600    info    Received Transaction    {"login": "guest", "name": "ben", "RequestType": "tranUploadFile"}
2022-06-19T20:32:08.108-0600    info    File upload started     {"transactionRef": "p32LSg==", "dstFile": "./config/Files///HotlineClient123PPC.sit"}
2022-06-19T20:32:08.157-0600    info    File upload complete    {"transactionRef": "p32LSg==", "dstFile": "./config/Files///HotlineClient123PPC.sit"}

I did a bunch of cleanup and testing on Windows.  This should be fixed in master now.


[R000589] Rep. E. Rigell

Rep. E. Rigell:
http://rigell.house.gov
Likely contact form URL to start with:
http://rigell.house.gov/contact/

YMAL file not found. I am working on it.


Questions about motion-corrected individual functional task run in MNI space in a volume

Hello,
I'm wondering what specific preprocessing steps have been applied to the motion-corrected files in volume space (sub-#/ses-#/func/sub-#_ses-#_task-(MID|nback|SST|rest)_run-#_space-MNI_bold.nii.gz). For example, did these images undergo Advanced Normalization Tools (ANTs) and DCANBOLDProcessing (DBP)? Thank you so much for your time!

HI Tommyng730!
The volume space files have been normalized to the MNI space (i.e. distortion correction, motion-correction, atlas registration). DCAN BOLD processing was not run on the data. Effectively, these images are output from fMRIVolume (see here: for more details https://collection3165.readthedocs.io/en/stable/pipeline/#stage-4-fmrivolume).
Please let us know if you have any further questions, thanks!


Options don't seem to be having any effect

I have all of the options set like in the demo:

Then in my controller I have:
    // Parameters
    $scope.parameters = {
      dragEnabled: true,
      emptyPlaceholderEnabled: false,
      maxDepth: 10,
      dragDelay: 0,
      dragDistance: 50,
      lockX: true,
      lockY: false,
      boundTo: '',
      spacing: 10,
      coverage: 10,
      cancelKey: 'esc',
      copyKey: 'shift',
      selectKey: 'ctrl',
      enableExpandOnHover: true,
      expandOnHover: 10
    };

I've verified that the values are being populated correctly in scope, however expand on hover doesn't seem to do anything, also the lockX isn't locking.
Any ideas? Thank you

lockx/locky appear to have been removed from the code at some point.