TypeError: Cannot read properties of undefined (reading 'AZURE_TRACING_DISABLED')

Package Name:  @azure/storage-blob
Package Version:  ^12.9.0
Operating system: Windows 10
[ No] nodejs

version:

[ Yes] browser

name/version: Chrome/ 99.0.4844.84

[ Yes] typescript

version: ^4.1.3

Is the bug related to documentation in

[ ] README.md
[ Yes] source code documentation
[ Yes] SDK API docs on https://docs.microsoft.com
Link is here: https://docs.microsoft.com/en-us/azure/storage/blobs/quickstart-blobs-javascript-browser

Describe the bug
I am following the tutorial documentation for using Javascript SDK for Azure Blob Storage for the Browser. I am using these codes in Angular framework (not Angular.js). When I use the codes for create/delete a blob, or List Blobs to operate with my Azure Blob Storage, it reports "TypeError: Cannot read properties of undefined (reading 'AZURE_TRACING_DISABLED')". Following the error I trace to this line of code in vendor-es2015.js, "const azureTracingDisabledValue = (_a = process.env.AZURE_TRACING_DISABLED) === null || _a === void 0 ? void 0 : _a.toLowerCase();". Looks like it's trying to call some Node.js variables from my browser, which it shouldn't.
To Reproduce
Steps to reproduce the behavior:

Use Angular CLI to set up a normal angular project.
Install @azure/storage-blob for the project via npm install.
Integrate the below codes to a component ts file, to connect with an Azure blob account.
These codes are from official doc, and I think they don't have problems, but they working only on 1 of my 2 computers.
const createContainer = async () => {
try {
reportStatus(Creating container "${containerName}"...);
await containerClient.create();
reportStatus(Done.);
} catch (error) {
reportStatus(error.message);
}
};
const deleteContainer = async () => {
try {
reportStatus(Deleting container "${containerName}"...);
await containerClient.delete();
reportStatus(Done.);
} catch (error) {
reportStatus(error.message);
}
};
createContainerButton.addEventListener("click", createContainer);
deleteContainerButton.addEventListener("click", deleteContainer);

Expected behavior
Solve the error message and connect successfully with Azure Blob. Any advice is very appreciated if it's not a bug.
Screenshots

Additional context
I am using this package in Angular + Ionic Framework environment. I run these on 2 computers. One computer works without error, but the other one is not working. They are all based on Angular and have installed the @azure/storage-blob as an npm package. One computer runs without the parcel npm package installed, and yet works. The other one I've tried installing parcel npm package, and configured the browsers list, but not working still. I am not really sure if it's a bundler caused issue, as on one of my computer it's running without the parcel bundler, but still works. On the other, it's installed with the bundler as per doc, but doesn't work.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.4647488,Azure.Core:0.40466124,Container Instances:0.023207719'

Hi @glv1at118 - thank you for opening this issue! My theory is that you have some polyfill for process that does not include process.env...
This function should return early in the browser, as process would not be defined...
https://github.com/Azure/azure-sdk-for-js/blob/5762893591c904be4880a47a56041c7298dc959a/sdk/core/core-tracing/src/createSpan.ts#L52-L65
Is it possible that you have some node compatibility shim that includes process but not process.env?
If you can help me dig into it further by creating a minimal repro and uploading it to github I will definitely be able to take a closer look - is that possible?
Thanks!


How to prevent dropping child items into sections

This is not an issue in the demo app as that disallows dragging child items from one group to another.
If I change the onGetChildItemDraggableRange to allow dragging between groups, it is possible to "lose" a child item as it is added as a child of a section (which is not expandable).
Is there some way to cancel a drag\drop operation if the drop target is not suitable?
Thank you.

I don't know enough about GitHub to make pull requests but here is how I solved it:
ExpandableDraggableItemAdapter
void onMoveChildItem(int fromGroupPosition, int fromChildPosition, int toGroupPosition, int toChildPosition);

becomes
boolean onMoveChildItem(int fromGroupPosition, int fromChildPosition, int toGroupPosition, int toChildPosition);

ExpandableRecyclerViewWrapperAdapter
2 occurrences of:
adapter.onMoveChildItem(fromGroupPosition, fromChildPosition, toGroupPosition, modToChildPosition);
mPositionTranslator.moveChildItem(fromGroupPosition, fromChildPosition, toGroupPosition, modToChildPosition);

become
    if (adapter.onMoveChildItem(fromGroupPosition, fromChildPosition, toGroupPosition, modToChildPosition)) {
        mPositionTranslator.moveChildItem(fromGroupPosition, fromChildPosition, toGroupPosition, modToChildPosition);
        }

So now I just return true if I want the drop to succeed (by checking if the target group is not a section) and false if I do not.


How to read MAC address from the device?

Hi,
Thanks for the code! I came here actually from myo-raw project. Since, my question involves low level access to the dongle, I would like to know how to differ between 2 dongles of the same type? Is it also possible to connect multiple devices from the same dongle at the same time?
Thanks a lot!

Question 1 - There is a command for obtaining the MAC address:
COM7: 2016-05-23 21:02:10,338 - bgapi - DEBUG - =>[ 00 00 00 02 ]
COM7: 2016-05-23 21:02:10,339 - bgapi - DEBUG - <=[ 00 06 00 02 23 A4 78 80 07 00 ]
COM7: 2016-05-23 21:02:10,341 - bgapi - INFO - RSP-System Address Get - 23A478800700
Question 2 - You can connect to multiple devices from one dongle.  The BLE112 is capable of up to 8 connections.  I don't know how many they support with the stock firmware, but you edit config.xml to modify how many connections are supported.  Increasing available connections consumes Flash/RAM and limits other things you can do, like the size of your GATT table.  That's why it's not just maxed for all devices.

Hey,
Thanks a lot! I guess sending those bytes on serial connection 00 00 00 02 will return it. I am sorry for forgetting to mention that I am using python to access the device. I will try to send those bytes over serial to see if it returns the MAC address.

Update: sending a command with 0, 0, 0, 2 over serial return exactly something like a MAC address. I can't verify if it is really the MAC address but I am almost sure about it (it doesn't change and it is different among 2 dongles).


Remove incorrect === from deploy.yml

Fixing: https://github.com/Expensify/Expensify/issues/157916
Following-up on https://github.com/Expensify/Expensify.cash/pull/2329
Failed workflow run: https://github.com/Expensify/Expensify.cash/actions/runs/840360949

🚀 Deployed to staging in version: 1.0.43-9🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.44-0🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Create Reissner-Nordstorm.py

Added the Reissner-Nordstorm metric
Fixes #309
@ritzvik
@shreyasbapat

move this to vacuum_solutions.py :)

Kindly Add tests in tests/test_symbolic/test_predefined

Okay!

Hello @obi-wan-shinobi! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/einsteinpy/symbolic/predefined/vacuum_solutions.py:

Line 119:1: E302 expected 2 blank lines, found 1

For tests, add the entry here
https://github.com/einsteinpy/einsteinpy/blob/2f8b5b38e97fbdfb798632e046b5d81bf19a3015/src/einsteinpy/tests/test_symbolic/test_predefined/test_all.py#L27-L51
Also, because Reissner–Nordström is a special case of Kerr-Newman, one addition is also needed here.
https://github.com/einsteinpy/einsteinpy/blob/2f8b5b38e97fbdfb798632e046b5d81bf19a3015/src/einsteinpy/tests/test_symbolic/test_predefined/test_all.py#L54-L63

Don't forget to lint the code
Squash n rebase after this https://github.com/einsteinpy/einsteinpy/wiki/How-to-refactor-commits

The problem may be in definition of the metric

The problem may be in definition of the metric

Yep, working on it :)

:( I'll see to it, in a while

:( I'll see to it, in a while

Thank you! I think I complicated things. I'll try the derivaition before making further changes. :0

Okay, this seems working

I'll give it one more look tomorrow before merging. Squash n rebase meanwhile
https://github.com/einsteinpy/einsteinpy/wiki/How-to-refactor-commits


removed invalid url for zomato,regulations.gov and betterdoctor

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for contribution @AnkitKaura 😄

Issue reference #1590


Option for participant's metadata

It will be nice to have this option. For our case in plugNmeet we always require participant's metadata for various purpose. If user doesn't have metadata then we can't verify lot of other logic in frontend.

implemented already: https://github.com/livekit/ingress/pull/222


Feature/#2 entity searching

Changes Unknown when pulling 2a13a16e1063113302f4df608ebd8ed4aa9689c0 on feature/#2-entity-searching into ** on master**.


Include description and screenshots in manifest

This is a feature request to for manifest app info particularly the screenshots and description members as they will improve the install flow on Android in Chrome.
Squoosh and Twitter are good example of webapps that have already implemented these features

Yeah, @beaufortfrancois did this in Squoosh a while ago.
@nstringham Wanna open a PR?

@nstringham https://web.dev/add-manifest/#screenshots and Chrome Canary DevTools should hopefully help you through this process.

Yeah, @beaufortfrancois did this in Squoosh a while ago.
@nstringham Wanna open a PR?

@surm  I created #529 do I need to do anything else?


Adds dirstack segment to powerline themes

Adds a new segment to the powerline themes to show the pushd level.
Shows only the character if there's just one entry in the stack, else shows the character and the depth.
I'm not sold on either the default color nor the default character and would be happy to discuss alternatives.
-DF

Hi, thanks for all the contributions! Sorry about the delay, work and life got in the way the last couple of weeks...
I'll take a look at your PRs in the next couple of days, promised! I'm currently working through the backlog of PRs that have piled up...

Hi, thanks for all the contributions! Sorry about the delay, work and life got in the way the last couple of weeks...
I'll take a look at your PRs in the next couple of days, promised! I'm currently working through the backlog of PRs that have piled up...

Hey @nwinkler thanks for the note.
Several of my PRs may require updates due other PRs being merged.
I'm happy to update them, but might wait until you have a chance to review the individual PRs and confirm if the changes they represent are something you'll consider merging.
If there's a change you're not likely to merge anyway, then no need updating the PR.
I personally use all of these PRs in my personal prompt configuration, so if you end up not feeling comfortable making them part of the official powerline prompts, I'll likely fork powerline into a custom prompt and submit that.
I do think they are useful and could benefit all powerline users, so I would prefer they get merged there if possible.
Thanks again and please let me know if you have any questions or concerns!
-DF

Hi @davidpfarrell - thanks for the kind words!
I want to merge the changes, just haven't found the time to do it so far.
If it's not too much work for you, could you please rebase the PRs on the current version?
General question: Do your PRs build up on each other? Do you need to rebase the PRs once I have merged the first one? If so, please let me know which one to look at first, and I'll get started with that...
Thanks for your patience, and again sorry for the delays in getting this looked at...

General question: Do your PRs build up on each other? Do you need to rebase the PRs once I have merged the first one? If so, please let me know which one to look at first, and I'll get started with that...

Hi @nwinkler - The PR's don't build on each other but some might need to be updated after others get merged
For tracking purposes (for both of us): Here's the order I think my PRs are best considered in:

#1448 "Makes all powerline vars configurable"
#1450 "Fixes prompt bg color on powerline naked theme"
#1446 "Adds SHORT_USER/HOSTNAME support to powerline themes"
#1443 "Adds shlvl segment to powerline themes"
#1442 "Adds dirstack segment to powerline themes"
#1444 "Adds history + command line number to powerline themes"
#1445 "Adds soft-separator support to powerline main + multiline themes"
#1449 "Adds last segment prompt char to powerline default theme"
#1447 "Adds compact support to powerline themes"

These are in the order of least complexity.
I've also posted this list as a comment on #1448 which has been rebased in preparation for merge.
I'll rebase the others as we move through them.
Thanks again,
-DF

OK - thanks for the patience! I've merged the first three - please rebase #1443 and I'll continue with the merges...

This one seems to be next, needs to be rebased as well...

This one seems to be next, needs to be rebased as well...

Rebase is complete, thanks !

Thanks!


Build errors after reinstalling VS2019

I have integrated Jab into my Xamarin Forms project. It worked very well until I had to reinstall VS2019 some days ago.
Since reinstalling I am getting build errors:
CS0246	The type or namespace name 'Jab' could not be found (are you missing a using directive or an assembly reference?)
and
CS0616	'ServiceProvider' is not an attribute class
and more indicating the Jab package contents cannot be resolved.

I also have the preview of VS2022 installed. There it works perfectly. My colleagues machine uses the same setup with VS2019 and the same code. For him the solution builds without an error.
I'm surely missing something. Thankful for any hints.

Does the same solution build from the command line (dotnet build)?
What's your output of dotnet --info? Is it different from your colleagues?

dotnet build shows different errors because Xamarin is not supported by .net 5.
But I compared the output of dotnet --info to my colleagus output. Turns out I had an old-ish version of the .net 6 preview running. I removed all previews and cleaned up, ran another uninstall-cleanup-install of VS2019.
Now the original error is gone and the namespace, as well as the attributes are recognized again.  Unfortunately the solution still doesn't build because of the following error:
Error	CS8032	An instance of analyzer Jab.ContainerGenerator cannot be created from C:\Users\me\.nuget\packages\jab\0.6.2\analyzers\dotnet\roslyn4.0\Jab.dll : Could not load file or assembly 'Microsoft.CodeAnalysis, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.

I was able to repo your original issue. It's fixed in 0.6.3 package. Unfortunately, I wasn't able to reproduce the updated issue. Can you try the fix and see if it helps?

That did the trick. I just had to update to Jab 0.6.3 and everything compiles and runs perfectly.
From your changes I can grasp what happened. I just wonder what I did differently to cause this.
Thank you very much!


fix: recurse through dirs then files

What does this PR do?
sorts files/folders to folders first then files when searching for components so that we find everything
updates the cache when a parent with more information is found
What issues does this PR fix or reference?
https://github.com/forcedotcom/cli/issues/2230, @W-13629588@
Functionality Before
would have to order modules alphabetically to get deploy to work
Functionality After
order doesn't matter

QA:
The reproducer works with the fix and fails without it.  Here is what I see with the fix (SDR linked to PDR):
plugin-deploy-retrieve/bin/run.js project deploy start

Deploying v57.0 metadata to<EMAIL_ADDRESS>using the v62.0 SOAP API.
Deploy ID: 0AfMN0000010HMr0AM
Status: Succeeded | ████████████████████████████████████████ | 5/5 Components | Tracking: 4/4

Deployed Source
===============================================================================================================================================================
| State   Name                            Type           Path
| ─────── ─────────────────────────────── ────────────── ──────────────────────────────────────────────────────────────────────────────────────────────────────
| Created CustomObject__c.Field1__c       CustomField    force-app/main/default/objects/CustomObject__c/fields/Field1__c.field-meta.xml
| Created CustomObject__c.Field2__c       CustomField    force-app/main/default/objects/CustomObject__c/fields/Field2__c.field-meta.xml
| Created CustomObject__c                 CustomObject   force-app/main/default/objects/CustomObject__c/CustomObject__c.object-meta.xml
| Created CustomObject__c.ValidationRule2 ValidationRule force-app/aa_package/objects/CustomObject__c/validationRules/ValidationRule2.validationRule-meta.xml
| Created CustomObject__c.ValidationRule1 ValidationRule force-app/main/default/objects/CustomObject__c/validationRules/ValidationRule1.validationRule-meta.xml


Fix javadoc_test job (WIP)

This PR is working if the javadoc_test job fails.

Closing this as we've moved to Kokoro


JSX incorrect type refinement invalidation?

Flow version: 0.107.0
type O = {
  a: ?string
}

let o: O = {a: null}

function VanillaComp() {
  return (
    o.a && React.createElement('div', {className: o.a.substr(1)}, console.log())
  )
}

function JSXComp() {
  return (
    o.a &&
{console.log()}

  )
}

Expected behavior
Type refinement (invalidation) should behave the same in JSX as well as in the compiled version.
Actual behavior
VanillaComp has no type errors, JSXComp has a type refinement invalidation type error.
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoAlgWwA5wE4AuYASgKYCGAxkVHnJmAOR4XWMDcqqBAntqWADyYALxgA3qjBhyALjAB+AM4E86AHYBzVAF8uMUkTjzhY8XLDqArjBh7UUK+uro46sADVy69LfIBhemwACgBKCSkwFgIrPHdgyOk4ADpyMAAydJJWAmTKFnICUgBRA0xSdQJgxgATdAA3RgAaCUoYciUlADlycvkU8mSlKwAjFTxggEZQnRbKNyU4A2T4TTDQyI37R2cCV3cAKQBlAA1AnDCI6WjY+MSwAYysgB46+rA2ju7e0hFxAaGo3GUxmAD5xPN1ItlqswjpnsA3qDNrogA

Thanks for the report! It looks like this is because jsx children are incorrectly typechecked before jsx attributes, which in this case causes the refinement invalidation from console.log() to fire before passing o.a.substr into classname. Until we fix this bug, the best thing to do might just be to write something longer-form like
if (o.a) {
  let classname = o.a.substr...

} ...

This bug has other ramifications, like the following unsoundness: https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoAlgWwA5wE4AuYASgKYCGAxkVHnJmAOR4XWMDcqqBAntqWAAKdbAGcwAXjABvAB4AuMADsArpgBGpPAF9OqSjHKjxAYTClZBUkoAm4slQIA6E-VxLrBADzC4YgHwyulwAbuR4YLKSYABE5DF6XmayEnLa-nISACwATNpewCb+qEA

Fixed for v.114


Cleanup pilot metrics

Add secrets and NDS to the push panel
Remove metrics that do not exist (and as far as I can tell, never
did?)
Add tags to some metrics

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
9997fdd1e07c996a88c9111a2120784ab6439074
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


[EyeDropper] It might be good to mention whether the screen under eyedropper is live or not

I can see there to be at least two possible strategies to implement the eyedropper:

the eyedropper floats over a live screen, and it's capturing the color of the live screen
a screenshot is taken, and the eyedropper would just capture color inside that screenshot.

I can see that current Blink implementation is mostly based on the first strategy, but it might be good to mention whether the second strategy could be valid. If it could, web apps may need to take extra steps to ensure UI they don't want to be displayed while eyedropper is open need to be removed first. Maybe it's just easier to say that it shouldn't be, and screen should be live?

I fully understand that the user agent should have the flexibility, but as I mentioned in the op, if we want to allow such flexibility, it should be explicitly called out, because

web apps may need to take extra steps to ensure UI they don't want to be displayed while eyedropper is open need to be removed first

Should this issue be moved to the new WICG repo to continue discussion?

Thanks again for filing the issue, moving the discussion to WICG/eyedropper-api#8!


Set up formatting checks

Closes https://github.com/mlcommons/mobile_app_open/issues/136
Closes https://github.com/mlcommons/mobile_app_open/issues/128

Is something wrong with your git? Many files are touched, but the content is not changed. It has no effect on the code but make review more difficult, and also tracking the history of the files.

Ok. Now I see. Those files are formatted with new line endings. For this kind of change (same change on multiple files), please create it in a separate PR next time. That make it easier to review changes.

Ok. Now I see. Those files are formatted with new line endings. For this kind of change (same change on multiple files), please create it in a separate PR next time. That make it easier to review changes.

Ok. Sorry for the inconvenience.


Secret Store configuration provider doesn't/cannot work

Expected Behavior
I can use the Dapr secret configuration provider to get secrets from Azure Key Vault.
Actual Behavior
The configuration provider tries to load the secrets (configured using the the DaprSecretDescriptors) as soon as the application starts. To do this it makes a call to the Dapr sidecar. However, the sidecar does not accept any incoming connections yet because it's still blocking until the app starts listening. So now we're basically in a deadlock situation with the sidecar waiting for the app, and the app cannot continue because the sidecar doesn't respond:
== DAPR == time="2020-07-21T16:29:12.794225+02:00" level=info msg="application protocol: http. waiting on port 5000.  This will block until the app is listening on that port." app_id=routing instance=MacBook-Pro.localdomain scope=dapr.runtime type=log ver=0.9.0

== APP == Unhandled exception. Grpc.Core.RpcException: Status(StatusCode=Internal, Detail="Error starting gRPC call: Connection refused")

== APP ==    at Dapr.Client.DaprClientGrpc.MakeGrpcCallHandleError[TResponse](Func`2 callFunc, CancellationToken cancellationToken) in /Users/sander/Git/dapr-dotnet-sdk/src/Dapr.Client/DaprClientGrpc.cs:line 562

== APP ==    at Dapr.Client.DaprClientGrpc.GetSecretAsync(String storeName, String key, Dictionary`2 metadata, CancellationToken cancellationToken) in /Users/sander/Git/dapr-dotnet-sdk/src/Dapr.Client/DaprClientGrpc.cs:line 536

== APP ==    at Dapr.Extensions.Configuration.DaprSecretStore.DaprSecretStoreConfigurationProvider.LoadAsync()

== APP ==    at Dapr.Extensions.Configuration.DaprSecretStore.DaprSecretStoreConfigurationProvider.Load()

== APP ==    at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)

== APP ==    at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()

== APP ==    at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()

== APP ==    at Microsoft.Extensions.Hosting.HostBuilder.Build()

== APP ==    at ControllerSample.Program.Main(String[] args) in /Users/sander/Git/dapr-dotnet-sdk/samples/AspNetCore/ControllerSample/Program.cs:line 25

Steps to Reproduce the Problem
I've taken the Dapr AspNetCore Controller sample and added an Azure Key Vault secret store to it. I then added a reference to the (0.9.0-preview01 version) of the Dapr.Extensions.Configuration NuGet package.
In Program.cs I add the Dapr configuration provider:
public static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureAppConfiguration((ctx, builder) =>
        {
            builder.AddDaprSecretStore("azurekeyvault",
                new DaprSecretDescriptor[]
                {
                    new DaprSecretDescriptor("Foo")
                },
                new DaprClientBuilder().Build());
        })
        .ConfigureWebHostDefaults(webBuilder =>
        {
            webBuilder.UseStartup<Startup>();
        });

I run the app in standalone mode:
dapr run --app-id routing --app-port 5000 --components-path ./components dotnet run

Conclusion
I don't see how this could work as it is designed now, unless I'm really missing something 😉
Wouldn't it be better to fetch the secrets just-in-time (like Microsoft.Extensions.Configuration.AzureKeyVault does) instead of directly on startup? That would also have the added benefit of getting the latest version of the secret.

@amolenk Then configuration provider will not work until app starts listening on the specified port as Dapr runtime waits on a response from app. This pull request shows how to workaround this https://github.com/dapr/dotnet-sdk/pull/262/files
@LMWF We should disable building and publishing the configuration provider until it can work and dapr can serve secrets without waiting for app to listen on port.

The extension was meant to be used as any other configuration provider for .NET, but today the only way to make it work is to use a workaround such as the one I added in the PR mentioned by @amanbha.

The extension was meant to be used as any other configuration provider for .NET, but today the only way to make it work is to use a workaround such as the one I added in the PR mentioned by @amanbha.

Thanks @cmendible Could you please share the other scenarios, outside of aspnetcore, because currently users are running into the issue https://github.com/dapr/dotnet-sdk/issues/345. So if there are no other scenarios for this extension then I would prefer to stop shipping it until it can be used without a workaround.

@amolnek since this extension doesn't work as of now unless Dapr runtime supports calling apis unless the app has responded on app port.


Docker cp handles resolv.conf, hostname & hosts, fixes #9998

Handles special files (/etc/hostname, /etc/hosts and /etc/resolv.conf) for the cp command. It won't be an empty file now, it's gonna use the real content of the file.
Fixes #9998
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

@vdemeester it would be really nice if you could add an integration test

@runcom ok :)

@vdemeester I edited your top-comment to add Fixes #9998. That way github will be able to autoclose issue on PR merge.

LGTM

@LK4D4 ok cool. I thought it would also work with the title of the commit :-).

LGTM


[MINOR] fix the comments in IndexShuffleBlockResolver

it might be a typo  introduced at the first moment or some leftover after some renaming......
the name of the method accessing the index file is called getBlockData now (not getBlockLocation as indicated in the comments)

LGTM

Merged build triggered.

Merged build started.

Test build #41021 has started for   PR 8238 at commit 7874b68.

Test build #41021 timed out     for PR 8238 at commit 7874b68     after a configured wait of 175m.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41021/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #41040 has started for   PR 8238 at commit 1aea5c4.

Test build #41040 has finished for   PR 8238 at commit 1aea5c4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41040/
Test FAILed.

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #41090 has started for   PR 8238 at commit 1aea5c4.

Test build #41090 has finished for   PR 8238 at commit 1aea5c4.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41090/
Test FAILed.

Merged build finished. Test FAILed.

The test failures must be spurious. The fix must be correct since there is no method called getBlockLocation anywhere now. Merging ...

thanks


Manual publish 8/30 PM

Need to publish to fix a redirect 404 issue.

Docs Build status updates of commit 9177326:
:clock10: Full build: the average full build time is 138 min(s) 30 sec(s), this is based on the last 96 build(s) for this repository.

Docs Build status updates of commit 9177326:
:warning: Validation status: warnings

File
Status
Preview URL
Details

.openpublishing.redirection.json
:warning:Warning

Details

docs-ref-autogen/azure-iot-device/azure.yml
:warning:Warning
View (azure-python)
Details

docfx.json
:white_check_mark:Succeeded

docs-ref-conceptual/index.md
:white_check_mark:Succeeded
View (azure-python)

.openpublishing.redirection.json

[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs-ref-conceptual/index.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.

docs-ref-autogen/azure-iot-device/azure.yml

[Warning] Uid(azure) has already been defined in docs-ref-autogen/azure-iot-device/azure.yml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


API unstable - alternative approach.

Is your feature request related to a problem? Please describe.
The Glow API is unstable, and partly blamed on "agressive polling" from the Open Source community.
There is a realsitic possibilty they API will be removed.
I wonder if there is a better way from this integration to work?
Describe the solution you'd like
One of the issues is the repeated requests for Daily and Annual readings - which Glow say has a heavy processing cost.
In this integration, we could just read the actual & current meter reading.
The energy integration should work fine off the meter reading.
Users that want the daily and annual calculations could use the utility meter integration.
It would be a breaking change - removing the today & annual sensors, but would push down a less "aggressive polling" approach.
Describe alternatives you've considered
Carry on regardless and hope Glow fix it their end.

Unfortunately as described here: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
meter reading and current consumption are not available via the DCC, as the data is always delayed by 30 mins.
The changes in #191 should reduce the load on the API - I just need to find time to implement them.
Duplicate of #116


Clarity that Exceptions are considered conditions.

Article states that:
Outlook 2013 and later supports showing policy tips for only some conditions
Currently, Outlook 2013 and later supports showing policy tips only for these conditions:
Content contains
Content is shared
Note that all of these conditions work in Outlook, where they will match content and enforce protective actions on content. But showing policy tips to users is not yet supported.
Because Conditions and Exceptions are separate sections in the DLP rule interface. It is worth mentioning that Exceptions are considered conditions, as this has caused some confusion for one of my customers.

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

ID: 0505aba8-2455-5390-b34b-6bb0865b14db
Version Independent ID: 401701a8-86fd-8570-8084-33622f34bb91
Content: Send email notifications and show policy tips for DLP policies - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/use-notifications-and-policy-tips.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@dkotars Thank you for your feedback.  In DLP policies, Conditions define what to include and Exceptions define what to exclude. You can find more information about that on DLP policy conditions, exceptions, and actions document (preview)https://docs.microsoft.com/en-us/microsoft-365/compliance/dlp-conditions-and-exceptions?view=o365-worldwide
Hope this helps!
Thanks
Sri

@dkotars Thank you for your feedback.  In DLP policies, Conditions define what to include and Exceptions define what to exclude. You can find more information about that on DLP policy conditions, exceptions, and actions document (preview)https://docs.microsoft.com/en-us/microsoft-365/compliance/dlp-conditions-and-exceptions?view=o365-worldwide
Hope this helps!
Thanks
Sri

No it doesn't. The article I am mentioning states:
**Outlook 2013 and later supports showing policy tips for only some conditions
Currently, Outlook 2013 and later supports showing policy tips only for these conditions:
Content contains
Content is shared
Note that all of these conditions work in Outlook, where they will match content and enforce protective actions on content. But showing policy tips to users is not yet supported.**
If you implement a DLP rule that has an exception that is not content contains/content is shared, this will prevent to policy tip from appearing as well. This is not noted in the document.

No it doesn't. The article I am mentioning states:
**Outlook 2013 and later supports showing policy tips for only some conditions
Currently, Outlook 2013 and later supports showing policy tips only for these conditions:
Content contains
Content is shared
Note that all of these conditions work in Outlook, where they will match content and enforce protective actions on content. But showing policy tips to users is not yet supported.**
If you implement a DLP rule that has an exception that is not content contains/content is shared, this will prevent to policy tip from appearing as well. This is not noted in the document.

@dkotars Thank you for the explanation. I shall test this on outlook 2013 and update the document if required.
Thanks
Sri

@dkotars Thank you for the explanation. I shall test this on outlook 2013 and update the document if required.
Thanks
Sri

@dkotars Thank you for the feedback. I have updated the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4265. Once the author validates and approves the document will be updated.
Thanks
Sri


Add MAlonzo directory.

Reasons for making this change:
Agda generates a MAlonzo directory, which should not be included in repositories.
Links to documentation supporting these rule changes:
https://wiki.portal.chalmers.se/agda/pmwiki.php?n=Docs.MAlonzo

@mcoblenz thanks!

thanks


how to download one task instance from SWE-bench dataset?

Describe the issue
Given a task ID, is it possible to download that task grin the SWE-bench dataset?
Suggest an improvement to documentation
No response

Don't think so


[SPARK-47304][SQL][TESTS] Distribute tests from DataFrameSuite to more specific suites

What changes were proposed in this pull request?
In the PR, I propose to move some tests from DataFrameSuite out, and distribute them across more specific tests suites and new one DataFrameShowSuite.
Why are the changes needed?

Improve maintainability of DataFrameSuite
Speed up execution of the test suite. Execution time dropped to < 1min.

Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the modified test suites.
Was this patch authored or co-authored using generative AI tooling?
No.

Merging to master. Thank you, @cloud-fan for review.


Check if plan name exists before adding new plan

Should check error back from the client to see if it's an "already exists" error, and toast accordingly. Need to make sure we clean up all the objects involved when creating a new cluster too: Cluster+MigCluster+Secret.


Disney+hotstar giving error of http connection pool

One plus TV

Add-on name: Disney + Hotstar
Add-on version: 1.1.1
Kodi version:  Kodi 19.1
Operating system version/name: Android TV
Using from country: India

Make sure you are connected to the internet. try with another network (eg mobile data). provide reproducible steps to create this error. provide debug logs if possible

Hi Abhi,
I am very new to this. I installed Jio app from repository it's working
fine, which means internet is working fine. But this Disney + Hotstar
giving error. If required logs or some information please let me know in
details so I can send you the same.
Regards,
Sachin
On Wed, 22 Sep 2021 at 12:07 AM, abhi @.***> wrote:

Make sure you are connected to the internet. try with another network (eg
mobile data). provide reproducible steps to create this error. provide
debug logs if possible
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/botallen/repository.botallen/issues/210#issuecomment-924260970,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVXOJ3RFS6OZD6UVA3RXE43UDDGGNANCNFSM5EPG6M7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Thanks and regards,
Sachin Nalawade
+91<PHONE_NUMBER>
+91<PHONE_NUMBER>
Sent from iPhone XR ..

Yes, debug logs will be appreciated. Also since it's an HTTP issue please let me know if you are using any proxy or VPN

No I am not using any VPN or proxy. Please let me know how to generate
debug logs.
Regards,
Sachin
On Thu, 23 Sep 2021 at 11:47 AM, abhi @.***> wrote:

Yes, debug logs will be appreciated. Also since it's an HTTP issue please
let me know if you are using any proxy or VPN
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/botallen/repository.botallen/issues/210#issuecomment-925533709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVXOJ3TBOWAJHTQKGHRUXO3UDLBAPANCNFSM5EPG6M7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Thanks and regards,
Sachin Nalawade
+91<PHONE_NUMBER>
+91<PHONE_NUMBER>
Sent from iPhone XR ..

Follow this guide. https://kodi.wiki/view/Log_file/Easy

Closing since no response from OP

Thanks!
On Mon, 11 Oct 2021 at 4:57 PM, abhi @.***> wrote:

Closed #210 https://github.com/botallen/repository.botallen/issues/210.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/botallen/repository.botallen/issues/210#event-5442626675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVXOJ3QMSI6DPHRZ5PTOBCDUGLCYPANCNFSM5EPG6M7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Thanks and regards,
Sachin Nalawade
+91<PHONE_NUMBER>
+91<PHONE_NUMBER>
Sent from iPhone XR ..


Collapse comments on resolve

Love the new "resolve conversation" button!

Even better would be if I could set a setting for automatically collapsing the conversations when I press resolve :-)

I think this and https://github.com/microsoft/vscode-pull-request-github/issues/5031 are duplicates of each other.

@brettcannon you are correct. Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/5031.


[Mahout-1958] Change the variable type to long to avoid overflow

Purpose of PR:
Please give a short description of what this PR is for.
Important ToDos
Please mark each with an "x"

[x] A JIRA ticket exists (if not, please create this first)[https://issues.apache.org/jira/browse/mahout/]
[x] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX is the JIRA number.
[ ] Created unit tests where appropriate
[ ] Added licenses correct on newly added files
[x] Assigned JIRA to self
[ ] Added documentation in scala docs/java docs, and to website
[ ] Successfully built and ran all unit tests, verified that all tests pass locally.

If all of these things aren't complete, but you still feel it is
appropriate to open a PR, please add [WIP] after MAHOUT-XXXX before the
descriptions- e.g. "MAHOUT-XXXX [WIP] Description of Change"
Does this change break earlier versions?
Is this the beginning of a larger project for which a feature branch should be made?

We can merge if this is looking good @balashashanka , did it build for you?


fix: Prevent Clustering with composable content from displaying default markers

Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #569 🦕

I'd update this too: https://github.com/googlemaps/android-maps-compose/blob/9aa32dccdebe27c41ffe2498eee8d1f1a0abe738/maps-compose-utils/src/main/java/com/google/maps/android/compose/clustering/Clustering.kt#L54-L70

By the way, as I mentioned here, I really believe this is a bug in DefaultClusterRenderer, but this change should be enough to work around that.

@kikoso I'm sorry for the delay here; got wrapped up in some other things. I finally had a chance to incorporate @gmazzotta-bit's suggestion around updating some additional code in the deprecated ReplaceWith comments.
Rebased this off of main and force pushed for a clean history.


When using "subscriberInfoIndexes". Skips reflections to find the parent's subscription information.

When using "subscriberInfoIndexes". After the "moveToSuperclass" method is called, if the parent class has no subscription information, it will always use the reflection to find the subscription information of the parent class. In fact, when using "subscriberInfoIndexes", this step can be skipped because "subscriberInfoIndexes" already contains all the subscription information of the parent class.

when this request can be merged? it help a lot with the eventbus performance


Display 'Recent Staking Rewards Transactions` in the accounts view

Problem
The recent staking rewards transactions section is only displayed when the user signs in to their wallet. This view should also be displayed when a user views an account from the accounts view without having to sign in to a wallet if there are staking transactions present.
Solution
Add staking rewards transactions view to the general accounts view.

Alternatives
No response

The mirror-node REST API does not yet allow to get accurate information for this (so the info we currently display on the Staking page might not always be 100% accurate). Ticket #4703 will provide adequate support.
We might want to wait for this support before generalising this display to the regular account view.


Auto remove minio bucket on job init

Codecov Report

Merging #1781 (c3d4078) into main (62ccee6) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1781      +/-   ##
==========================================
- Coverage   61.96%   61.91%   -0.06%
==========================================
  Files         135      135
  Lines       22910    22910
==========================================
- Hits        14197    14185      -12
- Misses       7128     7136       +8
- Partials     1585     1589       +4

Impacted Files
Coverage Δ

pkg/chunk/cached_store.go
79.11% <0.00%> (-1.11%)
:arrow_down:

pkg/chunk/disk_cache.go
79.85% <0.00%> (-0.49%)
:arrow_down:

pkg/meta/base.go
71.69% <0.00%> (-0.34%)
:arrow_down:

pkg/meta/sql.go
67.04% <0.00%> (-0.11%)
:arrow_down:

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 62ccee6...c3d4078. Read the comment docs.


Add zh-TW localization

Traditional Chinese is widely utilized in Taiwan, Hong Kong, and Macau, boasting a user base of nearly 30 million globally. For this project, I took the traditional Chinese from Taiwan as the basis for creating the messages.po file.
I humbly seek additional feedback from the community users, thank you.

Thanks to @KuwaLee and @noeFly for their contributions to the translation. I'm not sure why "Lint / Run linters (pull_request)" is throwing an error, but I believe we are ready to go.

Thanks to @snowleo208 for the review. I have modified the translation wording based on the suggestions and replaced all instances of "您" with "你" throughout the entire text.
Thanks again for your hard work and contribution.

#: src/view/com/modals/VerifyEmail.tsx:214
msgid "I have a code"
msgstr "我有邀請碼"

約 L1740 處，依照上方參照檔案的檔名看來，這個字串的用途是驗證電子郵件相關，故不太確定是否要將此處的「code」翻譯更改為「驗證碼」。
各位譯者覺得此處應該翻譯成「邀請碼」還是「驗證碼」？

這種時候應該用「驗證碼」(這是在 VerifyEmail.tsx 裡的)；看來源檔案這個字串沒有在其他地方用到，所以應該不會有問題。(另外可以利用 GitHub 的 code review 功能，會比較好追蹤已處理的問題點)

Thanks to @KuwaLee and @noeFly for their contributions to the translation. I'm not sure why "Lint / Run linters (pull_request)" is throwing an error, but I believe we are ready to go.

Someone changed the src/view/com/composer/text-input/TextInput.web.tsx in the latest commit. I saw there's a fixing PR ready but haven't merged yet :disappointed:

我在上面引用了一個PR，看到一位朋友針對翻譯詞進行了一些修改，例如將「Feeds」翻譯為「河道」，以及將「handle」翻譯為「使用者暱稱」，我希望他能夠參與這邊 的討論，以及使用 review 來共同確定最終的翻譯用詞
I've referenced a PR above where a new contributor made modifications to some translations, such as translating "Feeds" to "河道" and "handle" to "使用者暱稱." I hope they can participate in the discussion here, using the review process to collectively decide on the final translation choices.

hi I wanna translate 'feeds' as "河道" and translate 'handle' as "暱稱" . What do you all think?

我在上面引用了一個PR，看到一位朋友針對翻譯詞進行了一些修改，例如將「Feeds」翻譯為「河道」，以及將「handle」翻譯為「使用者暱稱」，我希望他能夠參與這邊 的討論，以及使用 review 來共同確定最終的翻譯用詞 I've referenced a PR above where a new contributor made modifications to some translations, such as translating "Feeds" to "河道" and "handle" to "使用者暱稱." I hope they can participate in the discussion here, using the review process to collectively decide on the final translation choices.

大家好！ 我想說使用河道可能熟悉推特的臺灣使用者會很親切，而handle原本翻譯為識別符，我覺得有一點點拗口，所以翻譯成暱稱。
造成不便還請見諒 謝謝~

Feed 感覺翻譯成河道或是時間軸
河道：推特及噗浪用戶比較習慣
時間軸：會與原意有些許差異

@SciencesVirus 我是覺得把handle譯成䁥稱也不錯，但feeds譯成河道，好像個人色彩重了少許／太playful？ 🤔
我想知道推特也是用河道的嗎？抱歉，其實我一直只用英文介面…… 我特地在推特轉成中文一看，也找不到哪裏寫著河道。可以告訴我在哪裏看到嗎？
不少用戶也是由推特轉會到Bluesky(包括我)，我覺得翻譯若是跟推特的也無不可

@SciencesVirus 我是覺得把handle譯成䁥稱也不錯，但feeds譯成河道，好像個人色彩重了少許／太playful？ 🤔
我想知道推特也是用河道的嗎？抱歉，其實我一直只用英文介面…… 我特地在推特轉成中文一看，也找不到哪裏寫著河道。可以告訴我在哪裏看到嗎？
不少用戶也是由推特轉會到Bluesky(包括我)，我覺得翻譯若是跟推特的也無不可

hi 很抱歉 我表達的不清楚，推特本身好像沒有特別使用河道，但是使用者會使用河道來稱呼feed,噗浪好像也是使用河道來稱呼。

Feed 感覺翻譯成河道或是時間軸
河道：推特及噗浪用戶比較習慣
時間軸：會與原意有些許差異，但與目前界面用圖相符

噗浪和 Twitter 好像都是用「河道」，所以我覺得把 feeds 改成河道比較好理解，但是 handle 確實比較難翻譯，它按文檔的意思是類似於 https://bsky.app/profile/bsky.app 中的 bsky.app 這部分，如果翻譯成「暱稱」的話，可能容易與 display name 或者 username 混淆，可能就不是太合適

噗浪和 Twitter 好像都是用「河道」，所以我覺得把 feeds 改成河道比較好理解，但是 handle 確實比較難翻譯，它按文檔的意思是類似於 https://bsky.app/profile/bsky.app 中的 bsky.app 這部分，如果翻譯成「暱稱」的話，可能容易與 display name 或者 username 混淆，可能就不是太合適

這個我有注意到，可能可以再想想有沒有更合適的譯法~

@auroursa 原來如此。handle有少許像是uuid的概念，我見uuid是翻譯作通用唯一辨識碼（英語：Universally Unique Identifier，縮寫：UUID）
像是用戶辨識碼會不會很難懂？
Display name = 顯示名稱
Username = 用戶名稱
Handle = 用戶辨識碼

唔，還是怪怪的，好像太機械化
或是稱呼如何？ :thinking:

噗浪和 Twitter 好像都是用「河道」，所以我覺得把 feeds 改成河道比較好理解，但是 handle 確實比較難翻譯，它按文檔的意思是類似於 https://bsky.app/profile/bsky.app 中的 bsky.app 這部分，如果翻譯成「暱稱」的話，可能容易與 display name 或者 username 混淆，可能就不是太合適

這個我有注意到，可能可以再想想有沒有更合適的譯法~

剛剛注意到Discord也有使用類似的兩個名稱，他們使用Display name 跟username ，我覺得handle更像username的感覺~

我在原本的英文文檔裏有時都見到username，像是︰
#: src/view/com/auth/login/Login.tsx:99
msgid "Enter your username and password"
msgstr "輸入你的使用者名稱和密碼"

#: src/view/com/auth/login/LoginForm.tsx:115
msgid "Invalid username or password"
msgstr "使用者名稱或密碼無效"

大部分都是在登入前見到，唯一有問題的是ChangeHandle.tsx是在用Bluesky username而不是handle 🤔
#: src/view/com/modals/ChangeHandle.tsx:266
msgid "Sets Bluesky username"
msgstr "設定 Bluesky 使用者名稱"

但我在Bluesky見到的是Handle︰
我猜username是在登入前才會出現的名詞，登入後全都是handle
我是覺得用用戶名稱來翻譯也可以啦，不知各位覺得如何

我剛剛新申請了一個帳號，但是也沒有看到使用username，所以我也不知道到底會用在哪裡，我覺得用戶名稱可以~

我剛剛發現，申請新的帳號時，選擇國際碼的時候，臺灣被當作中國的一省 🙄

There is a PR #2797 dedicated to fixing this issue.

@SciencesVirus 在登入畫面會見到︰

@SciencesVirus 在登入畫面會見到︰

但是這邊其實是要輸入handle (?

我剛剛發現，申請新的帳號時，選擇國際碼的時候，臺灣被當作中國的一省 🙄

There is a PR #2797 dedicated to fixing this issue.

THX

關於「handle」在 YouTube 中官方翻譯是「帳號代碼」，我覺得這個翻譯不會與「Display Name」和「Username」衝突，也容易理解，各位覺得如何呢？

@snowleo208 @snowleo208

According to Cambridge Dictionary
"Handle" is more dedicated noun for name
"Username" usually use as term for "handle"

關於「handle」在 YouTube 中官方翻譯是「帳號代碼」，我覺得這個翻譯不會與「Display Name」和「Username」衝突，也容易理解，各位覺得如何呢？

I have taken note of this help page, and I agree that「帳號代碼」seems more suitable for translating "handle".

Hey all -- love what you're doing here!
I can't read a lot of the discussion. @auroursa since you started the PR, can you let me know when consensus is reached and this PR is ready to go?

@noeFly I've decided to translate "handle" as「帳號代碼」and I changed the translation of "Moderation" to「限制」as it seems to better capture the meaning of that feature.
@SciencesVirus I'm currently unsure if translating "Feeds" as「河道」is appropriate, but I want to leave room for discussion. After receiving more feedback from users, we can decide whether to modify it in the next translation file submission.

@pfrazee Thank you for your patience. There has been quite a bit of discussion about the translation choices since this is the first time deciding to submit a PR for adding zh-TW translation. However, I believe we are ready to go now.

I have some more feedback. I'll put my overall opinions in this comment

"List" (as in the Twitter concept) should probably be 列表.
Follow is 跟隨 on Twitter, 追蹤 on Facebook - I think 跟隨 is less jarring for Bluesky.
"Like" should probably stick to Twitter-esque convention as "喜歡" and not Facebook-like "讚"
zh_TW does not use 自定義 for "custom" or "customize". It is usually "自訂" but can be contextual.
Access is usually 存取 instead of 訪問 (訪問 is usually used for "visit")
There is a distinction between 帳號 and 帳戶: the latter is the account while the former can be synonymous with "username". This convention is used by, for example, Google and Twitter. I don't consider this crucial though.
捨棄 is more familiar than 丟棄 in zh_TW

@noeFly @snowleo208 @SciencesVirus @KuwaLee Hello everyone, let's have a final discussion on this PR. Regarding these translation differences, what are your thoughts?

@noeFly @snowleo208 @SciencesVirus @KuwaLee Hello everyone, let's have a final discussion on this PR. Regarding these translation differences, what are your thoughts?
1.同意
2.我覺得“追蹤”、“跟隨”都可以
3.同意
4.我覺得自定義也很常用但可能不是正式的
5.同意
6.同意
7.同意

@noeFly @snowleo208 @SciencesVirus @KuwaLee Hello everyone, let's have a final discussion on this PR. Regarding these translation differences, what are your thoughts?

對此我跟@KuwaLee 有一樣的看法~

Looks good to me. I agree that the translation terms in Bluesky should be closer to Twitter, given that most users migrated from Twitter. This helps lower the user adaptation threshold. Therefore, I plan to keep it this way for now and discuss further translation modifications in the next PR.

@pan93412

@kisaragi-hiu I have incorporated the review comments above into a single submission.
This is amazing, and I appreciate your thorough review. I have added your name to the translation team section in the format mentioned in #2782.
Thank you for your contributions to improving the quality of zh-TW translation.

This is amazing, and I appreciate your thorough review.

@auroursa Thank you too for your work and your fast responses to feedback!

I have added your name to the translation team section

Thanks :)

I have adjusted all the translation based on the review suggestions, and I believe we are ready to go.

I also think we are ready to go now 😃

I have adjusted all the translation based on the review suggestions, and I believe we are ready to go.

Agree. Looks good to me!

Hello, @pan93412 forwarded the issue to me and I would like to help proofread the translation and just spot some problems. Will submit suggestions soon 🙏🏿

As my concern is mostly addressed in @pan93412's suggestions, further feedbacks are already included there.

@pan93412 Thank you for your hard work. I have merged all uncontroversial modification suggestions.
I've organized the remaining tasks, and I may need more feedback:

Choosing the translation for "build version".
Deciding between "色情內容" or "情色內容".
Improving the translation for "Copies".
Line 2507 seems to need improvement.

To collect reviewers' opinion toward the translation of "Build version". I opened a poll here ⬇
https://github.com/bluesky-social/social-app/pull/2781#discussion_r1484078311

"build version": All seem fine to me though I lean towards 建構版本號 to avoid colliding with "version number". (Hence my vote.)
"色情內容" or "情色內容": either seem fine with me. 色情 is explicit and perhaps has negative connotations (just like English "pornography"), while 情色 is less negative and more eloquent, but both get the point across.
"Copies " in accessibility text: I suggested adding a 會 to indicate that's an action to be taken - this is a little clumsy though. I'm fine with it removed, as pan93412 suggested.
Line 2507 (expanded list of users in notification): I suggest 展開此通知的使用者列表, which gets the point across without having to describe both that the notification has a list of users and that the list is expandable (and this expands it) in the same noun phrase.

I agree with @kisaragi-hiu

I have consolidated the voting results and comments and submitted the modifications.

I have chosen the FOSS-style term 'Build Version Number' for '建構版本號'."
In this PR, I will keep "情色內容" unchanged.
"Copies" has been revised by removing "會."
Line 2507 -> “展開此通知的使用者列表”

Thanks for the responsible reviews, I believe our translation has reached an unprecedented level of quality. Sorry for introducing quite a few simplified Chinese terms in my initial translations, it was unintentional. Once again, thanks to everyone for your contributions.

@pfrazee I am confident that we have reached a consensus and ready to go.

I made some minor modifications: In the previous discussions, we translated "Yes" and "No" as "開" and "關" respectively. However, some descriptions were not synchronized. I have fixed it.

@auroursa Is this PR ready to go? I think we already reached consensus and only need an approval now, right? :smile:

@snowleo208 Yeah I believe this PR is ready to go and awaiting final approval.
Don’t worry, the developers will handle it well. They just have more pressing matters to attend to first.

@pan93412 @toto6038 @kisaragi-hiu @snowleo208
Everyone, I've completed merging the strings from the upstream. Please take a look at commits 22278e1 & cfc9b4d and help me reviewing these new translations. Thank you!

After compiling, I checked each part, and it works well.

Look good to me :smiley:

@pfrazee I have merged all changes from #2879, and it works well in the latest version. I think we are ready to go.

Traditional Chinese is widely utilized in Taiwan, Hong Kong, and Macau, boasting a user base of nearly 30 million globally. For this project, I took the traditional Chinese from Taiwan as the basis for creating the messages.po file.
I humbly seek additional feedback from the community users, thank you.

Looks great so far.

I have fixed it based on the review suggestions.

A small translation correction, this should not be "圖書舘"
I will change it to "圖片庫"

This is ready to go, right? Since this PR already hanging around for a few weeks, I think we should prioritize pushing this PR live first and ignore upstream changes for now.
If there's any upstream changes, we can always create another PR for that. May we ask for review again from bluesky team?

I appreciate your patience and contributions. However, it seems that upstream has temporarily paused merging translations. I will merge your contributions into the .po files once translation merging is reopened.

Okay sorry everybody, I'm back in action for handling translation PRs. @auroursa how do you want to proceed -- should we merge as-is or do you want to factor in more updates?

I have merged the review suggestions and the upstream updates. And I believe additional translation updates should be handled in a new PR, as this one has become too lengthy. So I think we are ready to go. @pfrazee

@cirx1e I haven't figured out how to differentiate between "email" and "email address" yet. It seems a bit odd to translate "email address" as "電子信箱地址". I've merged the other review suggestions into the latest .po file.
I'd like to gather input from other translators and address it in the next translation PR. This PR has been open for too long, and I'd like to push for its merge as soon as possible. Thank you for your hard work.


The recently added collection doesn't show recently published apps

https://flathub.org/apps/collection/recently-added/1
It currently shows random apps, some that have been published ages ago and have hundreds of thousands downloads and some recently added ones

I can only assume that it has something to do with the recent database changes, probably expected(?)

cc: @barthalion


Bug in medstddev calc, no axis specified

Codecov Report

Merging #414 (e2afd96) into main (99c5787) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #414   +/-   ##
=======================================
  Coverage   58.06%   58.06%
=======================================
  Files          71       71
  Lines        7497     7497
=======================================
  Hits         4353     4353
  Misses       3144     3144

Impacted Files
Coverage Δ

src/eureka/S3_data_reduction/s3_reduce.py
93.33% <100.00%> (ø)

src/eureka/lib/medstddev.py
96.15% <100.00%> (ø)

src/eureka/lib/util.py
78.26% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.


self.self.self.self.self compilation issue

Description
self.self.self.self.self compilation issue
Steps to reproduce
This compiles:
struct Foo {
    subscript(index: Int) -> Int { 42 }

    func foo() {
        _ = self.self.self.self.self[1] // any number of self
    }
}

Expected behavior
It should give a compilation error.
Environment

Swift compiler version info 5.7
Xcode version info 14.0.1

Why shouldn’t it compile? x.self(including self.self) is an identity transform.


Manual days configuration

My postalcode doenst get any pickup days on those website.
Would it be hard to rewrite the component so we can manually put in the days trash will be picket up?
This would be wonderfull, the component did use to work on my old postal code.

That would be a total different approach and would require a lot of rewriting. Also there are already components doing things like that. What is your waste provider in your area, maybe I can help out?


Add credits for icons/resources

Add a CREDITS file similar to the main project, containing

credits for self-made icons (CC BY 4.0)
credits for launcher flag icons (CC BY 4.0)

Additionally, add the SVG file for self-made icons.

Closed by ed5f6b7


Optimize getBaselineDivergence

This function is too slow for larger data sets and should be optimized,

Is this solved with #91 ?

Yes, after merging the PR there are no issues with performance


robot keyword for notfication email

Signed-off-by: Tarun Kumar<EMAIL_ADDRESS>

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/596/


[WFCORE-569] : Clean the DiscoveryOption API

DiscoveryOption discover should return a list of connection parameters to a DC instead of only one value set into the DiscoveryOption.
Adding RemoteDomainControllerConnectionConfiguration as a holder class for such parameters.
Jira: https://issues.jboss.org/browse/WFCORE-569

Linux Build 1458 is now running using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb

Windows Build 1117 is now running using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb

Core - Full Integration Build 720 is now running using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb

Linux Build 1458 outcome was SUCCESS using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb
Summary: Tests passed: 3076, ignored: 65 Build time: 0:17:55

Windows Build 1117 outcome was SUCCESS using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb
Summary: Tests passed: 3076, ignored: 65 Build time: 0:21:51

Core - Full Integration Build 720 outcome was SUCCESS using a merge of b004e973d3c9e4b43ee792417bb6d90963800bfb
Summary: Tests passed: 2838, ignored: 416 Build time: 0:51:02

Core - Full Integration Build 759 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Linux Build 1503 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Windows Build 1158 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Linux Build 1503 outcome was SUCCESS using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests passed: 3079, ignored: 67 Build time: 0:18:56

Windows Build 1158 outcome was FAILURE using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests failed: 1 (1 new), passed: 3078, ignored: 67 Build time: 0:19:28
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.domain.SSLMasterSlaveTwoWayTestCase.testReadSlaveStatusFromMaster: <no details avaliable>

retest this plese

Core - Full Integration Build 759 outcome was SUCCESS using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests passed: 2842, ignored: 416 Build time: 0:54:02

Linux Build 1505 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Windows Build 1160 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Core - Full Integration Build 761 is now running using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90

Linux Build 1505 outcome was SUCCESS using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests passed: 3080, ignored: 66 Build time: 0:18:46

Windows Build 1160 outcome was SUCCESS using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests passed: 3080, ignored: 66 Build time: 0:19:40

Core - Full Integration Build 761 outcome was SUCCESS using a merge of dc95b96d6a9a7b5fac026e3869ee923486f29e90
Summary: Tests passed: 2841, ignored: 416, muted: 1 Build time: 0:51:10


Add API overview page for File API

GroupData.json lists "File API" as a Web API with the following contents:
        "File API": {
            "guides":     [ "/docs/Using_files_from_web_applications",
                            "/docs/Extensions/Using_the_DOM_File_API_in_chrome_code" ],
            "interfaces": [ "File",
                            "FileList",
                            "FileReader",
                            "FileReaderSync",
                            "Blob" ],
            "methods":    [],
            "properties": [],
            "events":     []
        },

...but it doesn't have an API overview page. We should write a page and add the "overview" property to GroupData.

@chrisdavidmills , why are these bugs being closed? As far as I can see this page has not been written.

@wbamberg I'm trying to tidy up the repos a bit, and eventually move everything over to the content repo and close the sprints repo. I thought I'd just close these, but maybe I was a bit overzelous; I'm happy to reopen them and move them to the content repo in you think they'd be useful.

This overview page isn't written, and GroupData isn't updated. So the reported problem isn't fixed: if we thought it was a problem before it still is IMO. And the same applies to the other issues.
Can we just move these issues to mdn/content?

I agree with you, but at the same time we have a huge backlog, and some of this stuff has been sitting here not being fixed for years in some cases. I was just trying to make the backlog a bit more manageable. I'll move them to content...


\textbf is not working (in Vietnamese)

I'm using kaobook to write a book in Vietnamese and I have a problem that the commands \textbf, \textsc, etc are not working.
\usepackage[utf8]{inputenc}
\usepackage[vietnamese]{babel}
The above commands are used so that I can write Vietnamese, but the chapter and section titles are not bold.
I need your help.

Hi, thanks for reaching out. I would suggest to use xelatex or lualatex instead of pdflatex. In that case, you don't need the inputenc package, and you'd use polyglossia instead of babel. Also make sure that the bold fonts are installed on your computer.


Does cvat create tasks support concurrency?

Does cvat create tasks support concurrency? For example, can I create multiple tasks at the same time?

@SnowCats , it does. The number of tasks which can be created in parallel are controlled by workers. By default CVAT has 2 works: https://github.com/openvinotoolkit/cvat/blob/d7560bbd39fec68f944515c2591dda74f3764b90/supervisord.conf#L25. This workers are used for dumping datasets and etc. You can increase the number of workers if it necessary.


United Kingdom country code error

I am using this library as a dialogFragment CountryPicker() and when selecting United kingdom as country
it returns call code +44
but the alphabetical code is GB not UK

Could you please update it ?


[Discover] roadmap: update the component view

update the component view
add detail click event and create detail page
create time line view
add axios model
create http utli api

Coverage decreased (-6.2%) to 40.645% when pulling a601709abbc38f04f30dfc39edaae6d8ea699cc0 on travelgeezer:roadmap-list into 90b06826ffa0a1a47084593cb12c4eb1e0b15869 on phodal:master.


cluster resource : possible bug in node_name method

I suspect a bug in node_name method since #274.
if the stdout of command '"rabbitmqctl eval "node()."' does not include quotes, the node_name method return nil.
Using "gsub" instead of "gsub!" should fix the bug.

I'm planning on doing a release of this cookbook tomorrow, can you get a PR in?


Implement circuit ready handler

This may require #163 and https://github.com/Cargill/splinter/pull/424 to work correctly


[FEAT] Support for Launchpad Mini Mk3

Would love to add (even if just partial) support for the Launchpad Mini Mk3.
Using this issue to document my findings so far & any progress.
As per the manual the device has two operational modes: "Live" & "Programmer".
In order to get the device to input & output proper midi, one must:

Hold the Session button for 3 seconds
Press the Stop Solo Mute button to enter "Programmer"-mode
Profit, your device is now in programmer mode!

To undo, either reboot/replug your device, or:

Hold the Session button for 3 seconds
Press the > button (above Stop Solo Mute) to enter "Live"-mode (made for Ableton Live specifically)
Profit, you are now a regular musician again

In addition to the above I discovered the device exposes two midi devices:

It appears the Launchpad Mini MK3 LPMiniMK3 MI does the magic. The DA variant I have yet to figure out what its for lol
A patched version (so far but still in progress) can be found on my temporary fork at lucemans/launchy.
Hope this helps! And I will keep you updated!

It appears the two columns of control buttons have a bit of an odd mapping.
Here is the midi in base 10

I have remapped the top row to be 0-7 (left to right) and the side row 8-15 (top-bottom)

It appears we might be able to swap between & read the state of Programmer vs Live mode 🤔


Unable to scroll the list in Errors and warnings window

When compiling Paladin using Paladin on x86_64 Errors and warnings window are filled with 6257 warnings. This list can't be scrolled while the list is populating.

Hi,
I have this kind of bug on Haiku OS about libraries list (I can't scroll down or up). I have put a ticket in the Haiku OS Bug Database, but they have ask me to return the bug to you. Also I see the last Haiku port of Paladin for x86 system here is an older version than the new  (version 2.0-1 on Haiku and I encounter the same bug on the 1.4-git-4 version) . These version are available in the HaikuDepot application (Official Package installer software for Haiku OS).
Thanks.

I have build the 2.7 version of Paladin from the zip file on Haiku R1/Beta2 I have the same trouble. But something is strange about the version number in the about Paladin windows, this is always mark as 2.6 d...But the folder containing it is mark as Paladin-2.7/Paladin (--for the build folder)

Hello. Thanks for your report. Yes, the build process doesn't correctly pick up the version number yet. There is another ticket open about that too. I shall rectify soon.
I think the bigger issue as you correctly identify is the library list. This limits usefulness for projects.
I also haven't ported the x86 version in a while. I'll add this in to my release workflow. Apologies, I didn't realise anyone was active on this at the moment.


Release 3.3.1

With the fix in #95, as the sass/scss version is currently (somewhat) broken in 3.3.0.

Yea, this would need to be a strange release, as sanitize.css has far moved into a 4x release. Unfortunately, Sass broke midway. I’m working on the 4x release, but the internet is very weak here in the hospital.

Hey, congrats man!
However, making a patch release with this change shouldn't be too complex, even with the master being ahead (doesn't seem like it is on the remote though? Unless I'm overlooking something).
I just tried this in a fork and it worked fine:
$ git checkout tags/v3.3.0
$ git cherry-pick 998ea92
$ npm version patch
$ git push --tags

+ npm publish etc
Result: https://github.com/simon-lifelike/sanitize.css/tree/v3.3.1
In any case, it's not a huuuge deal since we can still override the font definition manually. But it would be nice to have the stable version working again :)
Thanks for a great project! And best of luck

Version 4 is released!

@jonathantneal no more SASS/SCSS support in version 4.0?


Chat RAG can use tool functions and has better performance.

Describe the feature
Current chat is a 2 prompts,

determines context
qaRag prompt

Check backend/utils/llm.py
Chat should be a langchain agent instead, that has a retrieval function with multiple options.
Topics, date based, individual memories..
I want to have a much better chat performance.
Additionally, I want to be able to chat with individual memories.
(This might include a better vectorization of the current memories)

Hey, I would lovw to work on this issue.
I have experience with RAG, VectorDB and langchaun things.
Please assign me this issue : )
Thank you !!
Happy coding : )

Hey, I would love to work on this issue.
I have experience with RAG, VectorDB and langchaun things.
Please assign me this issue : )
Thank you !!
Happy coding : )

@advaitpaliwal

Assigning to @aialok for the next 2 days
Thank you for the help! happy to include a bounty to it :)

Thanks @josancamon19.
I don't find any documentation for setting up the backend. It would be great if there were some.

@josancamon19 need some time.
As last week of my GSoC is going on need to wrap all the things.
Thank you : )

hey @josancamon19, I am quite familiar with RAG/langchain, I am starting to work on this can you please assign this issue to me

Hey @josancamon19 ! I will work on this issue as I discuss with you already I am done with some work.
my GSoC is about to end in week then I will make a PR for sure.

https://discord.com/channels/1192313062041067520/1252164267688591360/1276974348871270493


Touristic contents list exports

Add all fields in list export (types, description, contact, published, ...)
Related to https://github.com/makinacorpus/Geotrek/issues/1313 and https://github.com/makinacorpus/Geotrek/issues/1167

Fixed in 0.31.0


feat(lttng): support for runtime recording of initialization trace points

This PR supports the trace points added by the record function from the middle of the process.
The order of execution of tracepoints related to initialization is related to the indexes such as callback_name.
Therefore, I've added the measurement start time as init_time for initialization and tracepoints to the tracepoints.
This PR is to handle the added init_time and to support the runtime_recording function.

I confirmed that latest commit passes caret_report check.


allow region configuration using ProviderConfig

Signed-off-by: smcavallo<EMAIL_ADDRESS>
Description of your changes
Allow configuration of region in ProviderConfig.  Region set in ProviderConfig overrides all other region settings (with the exception of region being set via annotations.)
This mirrors some of the functionality of the aws sdk where a default region can be set for all clients/calls.
This fixes cases where it's not feasible/possible to override the region at the resource level.  Ex. Calls to STS and other non-resource based requests where the region is not directly exposed or cannot specifically be configured.
Calls to resources where the region is not exposed (iam, route53) can be worked around today using pod annotations to set the endpoint and region, but having to set annotations on each and every resource is not ideal.

Fixes https://github.com/crossplane/provider-aws/issues/596
I have:

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

How has this code been tested

Unit tests
Creating IAM roles in gov cloud using access keys from local kubernetes environment

I've always personally been hesitant to expose the region here because it feels like we're mirroring the behaviour of CLI/SDK rather than mirroring the behaviour of the AWS API, but I think I'm very much the minority here.

@negz I agree that treating region as an authorization information in ProviderConfig is an implementation detail. That's why we came to this conclusion and I think @smcavallo will open another PR superseding this one.

Replaced by https://github.com/crossplane/provider-aws/pull/608


Redundant return statements removed and some if statements flipped to better reflect the function's purpose.

Small change, but many of these functions have inconsistent structures, so I flipped some of the if statements so they better align with the others. What this means is that the branch will have a call to the intended function and the second one what happens when the initial check fails.
I hope this helps!

No update?


Expand opam-vars using current opam variant

If the default opam from the Docker container (say, opam-2.0) is different from the current variant (say, opam-2.1), some errors appear:

[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"

Change to use the current opam variant (while hoping the CLI hasn't changed).

@MisterDA If you rebase this, the OCaml 5.0 build error has been fixed and it can be merged.