kubernetes-helm: 3.6.3 -> 3.7.0

Motivation for this change
Update to latest version.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[x] (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.

Result of nixpkgs-review pr 139189 run on x86_64-linux 1

3 packages built:

helmfile
kubernetes-helm
kubernetes-helm-wrapped

I'm not able to build the manual, due to:
Doing a combined check...
./manual-combined.xml: Not valid:
Line 101259:
101256	     <listitem>
101257	       <para>
101258	         Three new options,
101259	         <link linkend="opt-xdg.mime.addedAssociations">xdg.mime.addedAssociations</link>,
101260	         <link linkend="opt-xdg.mime.defaultApplications">xdg.mime.defaultApplications</link>,
101261	         and
101262	         <link linkend="opt-xdg.mime.removedAssociations">xdg.mime.removedAssociations</link>
     error: IDREF
    "opt-xdg.mime.addedAssociations"
    without matching ID;

Result of nixpkgs-review pr 139189 at bbdb3460 run on aarch64-linux 1

3 packages built successfully:

helmfile
kubernetes-helm
nixos-install-tools


[gdal] build failure

Operating system
windows
Compiler
GCC
Steps to reproduce the behavior
`./vcpkg install gdal`

Failure logs
Computing installation plan...
Error: Cannot find definition for package netcdf-c while getting netcdf-c:x86-windows.
Additional context
No response

Ok, I have solved this issue by reinstall vcpkg.


Allow IP + Port machine definition in quickstart yaml

What would you like to be added:
I would like to be able to speficy the machine list in yaml including both the IP address and a port. So, for example
  - <IP_ADDRESS>:50000
  - <IP_ADDRESS>:50001
  - <IP_ADDRESS>:50002

Why is this needed:
I am trying to deploy OpenPAI using an Azure Virtual Machine Scale Set. This will allow us to easily deploy a cluster using Low Priority Virtual Machines for the compute. By default, a VMSS will expose each machine on a common IPv4 address but with a unique SSH Port. This uses a Load Balaner. This approach allows us to use a local dev-box to manage the cluster and use the single public IP address plus port.
Without this feature, how does the current module work：
The current code validates a correct IPv4 address and fails

2019-02-27 17:33:33,023 [ERROR] - deployment.k8sPaiLibrary.maintainlib.common : <IP_ADDRESS>:50000 is not a correct ipv4 address!

Components that may involve changes:

Likely to just be a case of modifying cluster_util.py to support a unique IPv4+Port combo. At present ssh-port can be defined but this applies to all the IPv4 addresses
cluster-configuration.yaml already supports hostip and sshport on a per machine basis so assume that given a valid config file everything else should just work.

Hopefully I'll get time to take a look at this issue to send a PR myself. I would appreciate the core team advising if this is appropriate and if there is a preferred approach please?

Hi @cauldnz,
quick-start is only used as a template for generating the config.
So you can generate the config, then manually update the port.

@cauldnz - Hi Chris, does @hao1939 's suggestion helps? are you able to walk around the issue?

Hi @cauldnz , I will close it now. Feel free to reopen it if you have more question.


Iterate on docs for working with object storage

I think our working with object storage docs should explicitly distinguish the following scenarios:

its a 2i2c hub's user environment and its 2i2c hub's associated cloud bucket
In this case, writing data should work straight away as credentials should be setup and available for the user as long as the user environment image has relevant cloud CLI tools installed like aws, gcloud, or az.
I know that the pangeo/pangeo-notebook is an image that includes the aws CLI of relevance for the showcase hub with an AWS bucket.

its their environment / laptop and its 2i2c hub's associated cloud bucket
In this case, they need to acquire and configure credentials manually first. They could either get temporary credentials by extracting such from a 2i2c user environment, or use dedicated credentials in the cloud project setup for them personally.
Extracting temporary credentials is discussed in https://github.com/2i2c-org/features/issues/22 and isn't an established  and user friendly procedure yet.

its their environment / laptop and its their cloud bucket
I don't think its in scope for 2i2c to help with this or write docs focused on this situation.

Closed by https://github.com/2i2c-org/docs/issues/226


3-fasttext, no bigrams in function predict_sentiment

Update predict_sentiment function at the end to include bigrams.
In addition, since most bigrams do not have pretrained word embeddings they are initialized as all zeros, which is a bad practice. Try to initialize randomly (as in xavier initializer).

Thanks for spotting these! I'll admit I wasn't even aware of unk_init and always assumed TorchText just randomly initialized words outside of the vector vocab, not just set them all to zero.
I'll sort them out now.

@bentrevett now  and  tokens get non zero weights in embedding. Logically you dont want  or  to influence anything, thus weights of zero are optimal for them, imo. So, that's a new problem :D. Unless, we hope them to converge to zero automatically, not sure. I think fixing  to zeros throughout whole training is very reasonable idea, not sure how to do that though.

Yep, looks like we have to manually make the unk and padding vectors zero. We can do this with:
model.embedding.weight.data[TEXT.vocab.stoi['<unk>']] = torch.zeros(EMBEDDING_DIM)
model.embedding.weight.data[TEXT.vocab.stoi['<pad>']] = torch.zeros(EMBEDDING_DIM)

after we load the pre-trained embeddings.
We can also fix the padding tokens to stay zeros by passing the index of the padding token (1 by default, or got from TEXT.vocab.stoi['<pad>']) as the padding_idxargument to thenn.Embedding` layer
self.embedding = nn.Embedding(vocab_size, embedding_dim, padding_idx=padding_idx)

So, PyTorch initializes embedding weights by N(0, 1), so I'm happy to keep unk_init to how it is for now.
I might mention how you can define your own initialization if needed and use Xavier as an example as something like:
def xavier_init(tensor):
    nn.init.xavier_uniform_(tensor.unsqueeze(0))
    return tensor.squeeze(0)

TEXT.build_vocab(train_data, max_size=25000, vectors="glove.6B.100d", unk_init=xavier_init)

okay, thanks a lot!

So fan-in in our case is 25,000 (vocab size) and fan-out 100 (embedding dimension).
I suppose you cannot just set fan-in to 1 by unsqueezing. You should manually perform division by vocab size so that it will be xavier. I understand that this is a bit ugly.

Ah, you're right. That does make it a bit ugly unfortunately. If it comes out on top during the testing then I'll try and figure out a way to implement it without some ugly hack.

Ran some experiments with this and they basically get the same results for the models used in this tutorial so I'm going to leave it with the Normal initialization for now.


Added replacement for name of Portuguese langpack

Turns out vscode langpacks have the name pt-BR instead of pt-br, this generates the wrong id for the langpacks. To fix this from now on, this replacement check has been added.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.007%) to 42.552%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.007%

Covered Lines:
26727

Relevant Lines:
56924

💛  - Coveralls


IP address shows when searched but not in report IP Inventory

I am running Netdisco 2.58.3 and most things appear to be working quite well (I haven't tried all the features).  If I search for an IP address in the 'Find Anything' field such as <IP_ADDRESS>, it shows me which switch it is connected to and all the normal info.  If I go to Reports -> IP -> IP Inventory and then put in <IP_ADDRESS>/24, a small subset of the devices I can look up via the 'find anything' appear.  Any idea why?

I'm moving this into the main repo issues since it's probably unrelated to running in docker


Update miniconda url in README.md

The miniconda url in README.md is outdated

Thanks for fixing the link


Pinokio blocked by some company VPNs - Isolate the "install via url" field

Hello,
Pinokio website (and so also Discover page) is blocked by some company's VPN for "high risk phishing" threat :(
Could it be possible to detach the "install via url" field from the Discover page so it's independant on the UI, so it could probably be possible to use it without needing access to the website ? (We can download the client here on Github releases page).

Workaround :
Clone apps manually in username/pinokio/api from https://github.com/cocktailpeanutlabs repos then start Pinokio and click on an app then "install".
Closing :)
(Thanks Morpheus on Discord for the hint)


#490 [PageListBlock] Fix Insight template font not consistent

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


changes HOME href

Earlier When clicking on the Home button on Navbar the page would reload ,it felt out of place as other buttons would scroll to the particular section , Now on clicking the home button it would scroll back to the home section

looks good, thanks for the PR.


Feat: Removed old events for reactions and added !channelToggle remove

Since role-react and !group-toggle are being refactored any events related to reactions in the old event folder can be deleted
This still needs testing and reformatting :)
!closes #498

Github why are you being shit?

This PR adds multiple fixes for reactionRole, where when adding the reaction the bot would also get the role.

Rest LGTM, nice work!


ssm:GetParameter fails

I'm using the latest codebases for both the bootstrap-kit examples, as well as the latest 1.91.0-locked libraries and aws-bootstrap-kit package (thanks for updating that btw 🥇 ).
I have followed the tutorial found here without making custom changes or doing anything different: https://activate.workshop.aws/
Call failed: getParameter({"Name":"/cdk-bootstrap/hnb659fds/version"}) => User: arn:aws:sts::<CICD_ACCOUNT_NUMBER>:assumed-role/cdk-hnb659fds-deploy-role-<CICD_ACCOUNT_NUMBER>-us-west-2/aws-cdk-root is not authorized to perform: ssm:GetParameter on resource: arn:aws:ssm:us-west-2:<CICD_ACCOUNT_NUMBER>:parameter/cdk-bootstrap/hnb659fds/version (code=AccessDeniedException)
From my command line, I am not able to retrieve that SSM Parameter as my "dev" user with "DevOpsEngineer" role/privileges on the CICD account.
my aws profile for "cicd" is my "armenr-dev" user, configured for my CICD account # and is configured to use the DevOpsEngineer/DevOpsAccess permissions and role.
[profile cicd]
sso_start_url = REMOVED
sso_region = us-west-2
sso_account_id = CICD_ACCOUNT_NUMBER
sso_role_name = DevOpsAccess
region = us-west-2
output = json

╭─ armenr  ~/Des/ste/gru/infra                                                                                  ✔  10066  03:22:37
├─  main ● 
╰─ aws ssm get-parameters-by-path --path "/cdk-bootstrap/hnb659fds/" --region us-west-2 --profile cicd

An error occurred (AccessDeniedException) when calling the GetParametersByPath operation: User: arn:aws:sts::CICD_ACCOUNT_NUMBER:assumed-role/AWSReservedSSO_DevOpsAccess_cd96dc9ee675f305/armenr-dev is not authorized to perform: ssm:GetParametersByPath on resource: arn:aws:ssm:us-west-2:CICD_ACCOUNT_NUMBER:parameter/cdk-bootstrap/hnb659fds/

DevOpsAccess "Permissions Sets" have the following managed policies attached:

SecretsManagerReadWrite
AWSCodePipeline_FullAccess
AmazonEC2ContainerRegistryFullAccess
AWSCodeBuildAdminAccess
AWSCloudFormationFullAccess
AmazonS3FullAccess
SecretsManagerReadWrite

NOTE: Can someone confirm that the correct managed policy is "AWSCodePipeline_FullAccess" and NOT "AWSCodePipelineFullAccess" (without the underscore)?
Any guidance or suggestions would be much appreciated...even if it means I need to add a permission or role myself.
Thank you for all of your excellent work!

If it helps at all, here's the IAM role in question. This IAM Role resides in the master account.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudformation:CreateChangeSet",
                "cloudformation:DeleteChangeSet",
                "cloudformation:DescribeChangeSet",
                "cloudformation:DescribeStacks",
                "cloudformation:ExecuteChangeSet",
                "s3:GetObject*",
                "s3:GetBucket*",
                "s3:List*",
                "s3:Abort*",
                "s3:DeleteObject*",
                "s3:PutObject*",
                "kms:Decrypt",
                "kms:DescribeKey",
                "kms:Encrypt",
                "kms:ReEncrypt*",
                "kms:GenerateDataKey*"
            ],
            "Resource": "*",
            "Effect": "Allow"
        },
        {
            "Action": "iam:PassRole",
            "Resource": "arn:aws:iam::MASTER_ACCOUNT_NUMBER:role/cdk-hnb659fds-cfn-exec-role-MASTER_ACCOUNT_NUMBER-us-west-2",
            "Effect": "Allow"
        },
        {
            "Action": [
                "cloudformation:DescribeStackEvents",
                "cloudformation:GetTemplate",
                "cloudformation:DeleteStack",
                "cloudformation:UpdateTerminationProtection",
                "sts:GetCallerIdentity"
            ],
            "Resource": "*",
            "Effect": "Allow",
            "Sid": "CliPermissions"
        },
        {
            "Action": [
                "ssm:GetParameter"
            ],
            "Resource": [
                "arn:aws:ssm:us-west-2:MASTER_ACCOUNT_NUMBER:parameter/cdk-bootstrap/hnb659fds/version"
            ],
            "Effect": "Allow",
            "Sid": "ReadVersion"
        }
    ]
}

Could this be the reason why?
The operation being performed is "GetParameter," however the modified cdk-bootstrap-template.yml which resides in this 1-SDLC repo has:
            # PipelineSelfMutate
          - Effect: Allow
            Action:
              - ssm:GetParameters
            Resource: !Sub "arn:aws:ssm:${AWS::Region}:${AWS::AccountId}:parameter/cdk-bootstrap/*"

The original at: https://github.com/aws/aws-cdk/blob/master/packages/aws-cdk/lib/api/bootstrap/bootstrap-template.yaml
has
GetParameter --> Not GetParameters

Indeed good catch . Not a blocker for now but will fix asap.

Found fix.
Forking, branching, and opening a PR for review.
Will reference this issue in the PR as well.


Sophos Endpoint Protection (using REST API) (Preview) - Fails due to table name Custom-SophosEPEvents_CL containing hyphen.

The deployment tries to create a table called Custom-SophosEPEvents_CL which fails due to the inclusion of a hyphen.
Connector resource creation failed
Failed to create required resources for data connector InvalidPayload:Data collection rule is invalid, [{"code":"InvalidOutputTable","message":"Table for output stream 'Custom-SophosEPAlerts_CL' is not available for destination 'clv2ws1'.","target":"properties.dataFlows[0]"},{"code":"InvalidOutputTable","message":"Table for output stream 'Custom-SophosEPEvents_CL' is not available for destination 'clv2ws1'.","target":"properties.dataFlows[1]"}]

The naming is referenced in the below files and will likely need renaming to CustomSophosEPEvents_CL
./Data Connectors/SophosEP_ccp/SophosEP_PollingConfig.json:67:                "streamName": "Custom-SophosEPEvents_CL"
./Data Connectors/SophosEP_ccp/SophosEP_DCR.json:70:                "Custom-SophosEPEvents_CL": {
./Data Connectors/SophosEP_ccp/SophosEP_DCR.json:188:                        "Custom-SophosEPEvents_CL"
./Data Connectors/SophosEP_ccp/SophosEP_DCR.json:194:                    "outputStream": "Custom-SophosEPEvents_CL"
./Package/mainTemplate.json:850:                  "Custom-SophosEPEvents_CL": {
./Package/mainTemplate.json:968:                      "Custom-SophosEPEvents_CL"
./Package/mainTemplate.json:974:                    "outputStream": "Custom-SophosEPEvents_CL"

Thanks

Hi @synapse303, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 30-05-2024. Thanks!

Hey @synapse303, Could you please let us know where exactly this error occurred and if possible, please share the screenshots with us. Thanks!

Hi,
When trying to Add the connector in Content Hub/ Sophos Endpoint Protection/Data Connectors/ Sophos Endpoint Protection (using REST API) (Preview)

Error:

Hey @synapse303, The error you're getting is only after installing the solution and data connector OR after trying to connect the connector Sophos Endpoint Protection (using REST API) (Preview) by entering its credentials?
And if the error before configuring the connector, then could you please check the same into another different Workspace and let us know the same error you're having.
If issue still persist, please share your mail ID with us to connect for a call to check on this issue. Thanks!

@synapse303 Thanks for sharing screenshots. will check and get back to you with update.

I can confirm. We are having the same issue in the same place.

We're also having this issue, do we have an update?

Hi @ViniMelo, Our team is still working on investigating on this issue, currently team is facing some challenges on updating the solution. Once changes are done, we will raise the PR with changes and update you. Thanks!

We have the same issue. Any update on this?

Hi @synapse303,
We have updated the template and will raise PR with the changes. Meantime, could you please custom deploy the Solution MainTemplate and check whether your issue get resolved.
Sharing the MainTemplate and Custom deployment steps-
Custom Deployment -  Custom Deployment of the Solution - Copy.docx
Main template: - mainTemplate_sophos_new 3 (1).json
Thanks!

I deployed via custom solution and it has worked.
thankyou

@synapse303, thank you for response, will update this solution and fix will get available in upcoming solution version. So, closing this issue from GitHub. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.

@v-sudkharat  perhaps a solution to this error has been found.


Is it possible to hide the table borders?

Is it possible to hide the table borders?
Is it possible to change the color to white or transparent?

Hi again,
By default tables have no borders. A table like the following won't show any borders

    Cell 1
    Cell 2

If you use the table-bordered class or have defined the border attribute greater than 0, then it will show the borders, just as the html


Yadda 20150107 rc

This pull request is only for Yadda part 1. There is some additional work in it for parts 2, 3, and 4; I plan to submit separate PRs for those after the work has been reviewed by other members of my team (Trogdor).
Files for part 1:
-yadda/yadda-schema.sql
The schema file contains instructions on how to use.

@ryancowan Reviewed Part 1: Some minor things, ensure that table names are in plural form. Also you are missing your created_by field. Also normalize the beers table. You don't have to resubmit part1 so these changes should be in part 2.


LeViT training and bench on GTSRB dataset

Hello
I'm trying to use your SOTA LeViT for GTSRB but encounter some problems when testing. The accuracy after testing 12K images in GTSRB was only 13.4%, 347 FPS on 3080Ti. I believe that your model could break any record of my survey and training may be the main cause. I have tried levit.py and levit_c.py to load the model with only arg num_classes = 43 for training. I also use the same training, and testing method for GhostNet 1.0 and MobileNetV3 Large. Could you please point out some points in the training code that made my testbench not work with your work? Thank you in advance.
import torch
import torchvision
from torchvision import models
import torch.nn as nn
import torch.optim as optim
import torchvision.transforms as transforms
from torch.utils.data import DataLoader
from torchsummary import summary
from utils import save_plots
from levit_c import LeViT_c_128S
mean=(0.485, 0.456, 0.406)
std=(0.229, 0.224, 0.225)
transform_train = transforms.Compose([
    transforms.Resize((224,224)),
    transforms.ToTensor(),
    transforms.Normalize(mean,std),
])
trainset = torchvision.datasets.GTSRB(root='data', download=False, transform=transform_train)   # download=True if you did not download yet
trainloader = DataLoader(trainset, batch_size=32, shuffle=True, num_workers=8)
model = LeViT_c_128S(num_classes=43)
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
model = model.to(device)
# Config Training HyperParameter
criterion = torch.nn.CrossEntropyLoss()
optimizer = optim.SGD(model.parameters(), lr=0.1, momentum=0.9, weight_decay=1e-4)
scheduler = optim.lr_scheduler.StepLR(optimizer, step_size=20, gamma=0.5)
# Lists to keep track of losses and accuracies.
train_loss= []
train_acc= []
# Training
epochs = 50
model.train()
epoch_acc = 0
epoch_loss = 0
for epoch in range(epochs):
    print("\n Epoch: %d"%(epoch+1))
    sum_loss = 0.0
    correct = 0.0
    total =0.0
    for i, data in enumerate(trainloader,0):
        length = len(trainloader)
        inputs,labels = data
        inputs,labels = inputs.to(device),labels.to(device)
        optimizer.zero_grad()
        # forward+backward
        outputs, x = model(inputs)
        loss = criterion(outputs,labels)
        loss.backward()
        optimizer.step()
        # 每个epoch输出损失和正确率
        sum_loss += loss.item()
        _, predicted = torch.max(outputs.data,1)
        total += labels.size(0)
        correct += predicted.eq(labels.data).cpu().sum()
        print("[epoch:%d, iter:%d] Loss: %.03F | Acc: %.3f%%"
              %(epoch+1, (i+1+epoch*length), sum_loss/(i+1), 100.*correct/total))
    scheduler.step()      # Adjust Learning Rate for next epoch
    epoch_loss = sum_loss/(i+1)
    epoch_acc = 100.*correct/total
    train_loss.append(epoch_loss)
    train_acc.append(epoch_acc)
#Display Training Result
model_name = "LeViT_128s"
save_plots(model_name, train_acc, train_loss)
print("Model: LeViT_128s")
print(f"Training Hyperparameter - Epochs: %s, Batch-size: 32, Learning-rate: 0.1, Optimizer: SGD, Momentum: 0.9 " % epochs)
print("[epoch:%d, iter:%d] Loss: %.03F | Acc: %.3f%%" %(epoch+1, (i+1+epoch*length), sum_loss/(i+1), 100.*correct/total))
print(f"Model was saved as %s.pth" % model_name)
torch.save(model.state_dict(),'LeViT_128s.pth')

Is the problem that the training accuracy goes up to 100%, but that it does not generalize to the test set?
LeViT was created with ImageNet in mind, and the statistics of ImageNet images are quite different to GTSRB images.

Hi,
Thank for your reply, I have tried to adjust the training hyperparameters and data augmentation. The LeVit_128S now can achieve 30% accuracy - 346FPS,  and LeViT_192 60% accuracy - FPS 277. While the MobileNetV3 Large can achieve 98.37%-355FPS, GhostNet 1.0 97.26%-275FPS. I use the same training and testing method for 3 models but the LeVit model doesn't not fit my method and I really want to improve. That's why I contact you, I would love to see your model working as expected. :(  The benchmark illustrates your LeViT_128s have the higher accuracy and speed than both MobileNet and GhostNet. I'm looking forward for your advices.

(https://colab.research.google.com/drive/1yPpAtsibYw8jkzOarLBhdXnWvJR0Uqlo?usp=sharing#scrollTo=r377ZaaKKImT)

Sorry, but I don't know enough about GTSRB  to help.


Async i18n messages proposal

This PR allows i18n messages to be loaded async and allows to change the locale through a query param.
Usage:
<Admin
messages={{
fr: import('./i18n/fr.js').then(m=>m.default)
}}

IMO, it would be better to add/change the current locale actions so that they may include messages. This way, it would be possible to load them on demand and from any source (file, db, API, whatever).

@djhi : I changed the implementation to what you've suggested. I had some issues with my initial solution and this implementation is cleaner.

Moved list query issue to separate PR https://github.com/marmelab/admin-on-rest/pull/1326 and rebased.

A way to force reload of the locale without reloading the app would also be great. Then we could administer and reload locale via react-admin :)


Can someone tell me whats going on here?

Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

events.js:160
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::51826
at Object.exports._errnoException (util.js:1020:11)
at exports._exceptionWithHostPort (util.js:1043:20)
at Server._listen2 (net.js:1258:14)
at listen (net.js:1294:10)
at Server.listen (net.js:1390:5)
at EventedHTTPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:60:19)
at HAPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:158:20)
at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:557:16)
at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:114:16)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:372:14)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
at /usr/local/lib/node_modules/homebridge-nest/index.js:155:6

Homebridge is already running.

HAP Warning: Characteristic 00000054-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 0000003E-0000-1000-8000-0026BB765291. Adding anyway.
[8/27/2017, 1:37:44 PM] Software version for Fort Myers Thermostat (Home) is: 5.6.3-1
[8/27/2017, 1:37:44 PM] Temperature unit for Fort Myers Thermostat (Home) is: Fahrenheit
[8/27/2017, 1:37:44 PM] Current temperature for Fort Myers Thermostat (Home) is: 72.86 F
[8/27/2017, 1:37:44 PM] Current heating for Fort Myers Thermostat (Home) is: Cooling
[8/27/2017, 1:37:44 PM] Current humidity for Fort Myers Thermostat (Home) is: 50%
[8/27/2017, 1:37:44 PM] Target temperature for Fort Myers Thermostat (Home) is: 72.86 F
[8/27/2017, 1:37:44 PM] Target heating for Fort Myers Thermostat (Home) is: Cooling
[8/27/2017, 1:37:44 PM] Initializing platform accessory 'Fort Myers Thermostat (Home)'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

events.js:160
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::51826
at Object.exports._errnoException (util.js:1020:11)
at exports._exceptionWithHostPort (util.js:1043:20)
at Server._listen2 (net.js:1258:14)
at listen (net.js:1294:10)
at Server.listen (net.js:1390:5)
at EventedHTTPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:60:19)
at HAPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:158:20)
at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:557:16)
at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:114:16)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:372:14)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
at /usr/local/lib/node_modules/homebridge-nest/index.js:155:6
Jimmis-iMac:~ omega$

run netstat-ano
Find out which pid is using the 51826 port,PID is at the far right. and do a sudo kill -9

netstat-ano says command not found
nets tat brings up a bunch of stuff but nothing showing 51826

You need to find out which service is using the port.
Or did you auto run homebridge? systemd?

Simply restart

can't i just change the port?
I port forwarded the 51826 in Airport utility and it used to work fine.
I changed the port to 51836 in my config.json and reran home bridge in terminal and it didn't give the error but all my devices show "No response" in the home app.
I deleted the port forwarding and changed the config.json back to 51826 and reran homebridge and the error comes back

you must have homebridge auto launching in Launchd, so running it manually is starting a second instance.


v1.16 Backports 2024-08-19

[ ] #34076 (@chaunceyjiang)
[ ] #34231 (@hemanthmalla) :warning: resolved conflicts
[ ] #34234 (@tamilmani1989)
[x] #34285 (@julianwiedmann)
[x] #34270 (@rastislavs)
[x] #34227 (@dylandreimerink)
[x] #34303 (@julianwiedmann)
[x] #34336 (@aanm)
[x] #34339 (@sayboras)
[x] #34236 (@mhofstetter) :warning: resolved conflicts
[x] #34282 (@chancez) :warning: resolved conflicts
[x] #34229 (@chancez)
[x] #34335 (@rastislavs)
[ ] #34346 (@jrajahalme)
[ ] #34372 (@Artyop)
[x] #33625 (@julianwiedmann) :warning: resolved conflicts
[x] #34415 (@harsimran-pabla)
[x] #34420 (@julianwiedmann) :warning: resolved conflicts
[x] #34400 (@mhofstetter)
[x] #34361 (@chancez)
[x] #34388 (@pchaigno)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 34076 34231 34234 34285 34270 34227 34303 34336 34339 34236 34282 34229 34335 34346 34372 33625 34415 34420 34400 34361 34388

/test-backport-1.16

Reviewed @rastislavs  PRs since he is on 🏖

/test-backport-1.16

@sayboras may I ask you to review https://github.com/cilium/cilium/pull/34336 changes instead of André (he is on vacation).

@learnitall could you please review https://github.com/cilium/cilium/pull/34234 changes?

@squeed could you please review https://github.com/cilium/cilium/pull/34346 changes?

I would suggest to drop the commit 58ccc89. The changes in this PR are a lot different from the upstream PR so it would make sense to let @hemanthmalla to perform the backport himself.

Done, thank you!

/test-backport-1.16

Yeah, some of the changes didn't really look relevant to my original commit and I didn't need to do those for our 1.14 / 1.15 backports. I'll handle this one separately. Thanks for looking into this @viktor-kurchenko / @aanm


Feature request: Select list item by mouse click

Hi Shall the windowswitcher directly activate the window on a mouse click or only select it the item which then will be activated by a return?

I'd prefer the direct activation like in a web link.

Check out version 1.04 please should be working in the draft.

v1.0.8 is public release and it includes the requested feature by @simarust


UIA: incorrect word boundary across wrapped lines

Windows Terminal version (or Windows build number)
Latest main
Other Software
No response
Steps to reproduce

view test case file (cat, type, etc; sent privately) in a conhost.
Move the NVDA review cursor up by line until you reach the start of the file.
Navigate forward by word through the end of the file.

Expected Behavior
Each word is read separately through the end of the file.
Actual Behavior
You'll eventually hit a word that includes an entire line!

You know, this almost certainly has a dupe that's my fault. That being said, Carlos tells me that it's almost certainly his oversight. So I'm putting him on the 'assigned to'. Thanks!

From Bill: This definitely happens in conhost, not sure if this happens in Terminal


[FIX-141/161] Budgeteer administration menu.

This PR should be ready for review now.
The administration menu is started as a separate web app (this one is set to run on port 8090) and
can be started from the root folder by running ./gradlew budgeteer-admin-interface:bootRun.
The first user to log in to it is made global admin.
The global admin currently has the following abilities:

Set the password/email of any user in the Budgeteer
Delete any user in the budgeteer
Make any other user admin as well
Delete any project
Change the permissions of users in a project
Remove/Add users from/to a project
Edit the project name and start/end dates.

This adresses issue #141 and issue #161

I have added a migration script and upped the version to 1.1.1 (as Flyway seems to require that and I'm not against incremental point updates). Upon starting the web-interface war the DB (V1.1.0 database) will be updated. Afterwards the admin-interface can be started as well.

Does not look like it is going to work. Take a look at
ALTER TABLE BUDGETEER_USER ADD(GLOBAL_ROLE NUMBER(10,0) NOT NULL ENABLE);
this will fail on every row already present in the USER table since you add a mandatory field without giving a default.
Also, it is not clear how a CONTRACT_SORTING corresponds to the task at hand.

I believe I have fixed the script as well as a few bugs that came up while testing.
On the subject of contract sorting. This feature was added to the master branch in PR #303. It has nothing to do with the administration of users, but must be added to the migration script for the migration to be successful (because this branch is up to date with master).

Hey @LeonieAdis, can you please adapt the suggested changes.

I implemented all my suggestions, except for the missing feedback messages for the e-mail-entries.
I know, a similar e-mail-entry with correct feedback messages is used in the "Register"-page, but I wasn't able to transfer that functionality.
I tried different ways, but couldn't figure out how to get it working.
Maybe someone else can help here.
In my opinion, the missing feedback messages aren't a big issue, so it may also just be kept like it is right now.
The earlier version of this PR was - due to addition of not-nullable attributes - not compatible with an already filled database. I fixed this by setting those attributes nullable.
Additional there was a logic mistake in the project administration:
If the current logged in user was a project admin, his admin rights could only be unset, if there was another project admin. But if the current logged in user wasn't a project admin and there was another project admin, the admin rights of this second admin could be removed, so there was no project admin left.
I changed this logic:
Now the application checks, if there is more than one project admin. Then all project admins can become non-admins.
If there is only one project admin left, you can't remove his admin rights.
In this way, there always has to be an project admin.
The only exception is a project, that was created in a earlier version of the application, when we didn't have user roles. Then by default, there is no project admin.
In this case, you first have to give admin rights to a user in the project.


OUS Demographic Future Enhancements

Calculating demographic stats from raw survey shapes is slow to do in real-time, if precise (using polygon intersection/overlap test).  For Maldives, a draft offshore plan that Will shared with takes about 15 seconds to run.  I think that's acceptable for now, for the offshore.  For example, an inshore network I created with shoreline clipping creating many vertices, took 90 seconds to run.  This is quickly not acceptable.
We may be able to use the H3 indexing system to summarize demographic metrics including heatmap value for reports, rather than generating raster heatmaps, which don't make a great intermediate format, especially for sparse data.  Use of H3 was already explored for generating h3 heatmaps for display, we should be able to use them for reports as well -- https://github.com/seasketch/geoprocessing/pull/110.
This ties into the discussion of a core feature of SeaSketch Next for storing heatmaps for display in the database and publishing as vector tiles for use by the map.
Requirements:

use all-touched containment strategy for fill method with recently released H3 v4.  This way we can use coarser h3 index levels and ensure we're getting coverage of shapes.

Method 1: index the respondent IDs

pre-calculate heatmaps for combination of sector/gear type/community.  This is potentially hundreds of combinations.  Find the best way structure this data and store and retrieve it (S3 bucket?).

an index could be a list of H3 cell IDs with a list of respondents that overlap with each cell.
for each heatmap combination, filter the shapes down.
loop through the shapes and us h3.fill to bin the respondent IDs.
push the indexes to S3.

Calculating overlap

GP function retrieves h3 index of respondent IDs
get the h3 cells that overlap with a given sketch, and aggregate the unique list of respondent IDs

Method 2: index the heatmap value and all the metrics for each h3 cell

Pulled this into In Progress because performance enhancements will be needed for Azores Nearshore reports.


chore: array syntax highlighting

User type names like structs and contracts were not highlighted at all (not only on arrays). With this change, they are highlighted properly in both cases:

Closes #385

Codecov Report

:exclamation: No coverage uploaded for pull request base (development@9a32862). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 769d654 differs from pull request most recent head 0a005ae. Consider uploading reports for the commit 0a005ae to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@              Coverage Diff               @@
##             development     #443   +/-   ##
==============================================
  Coverage               ?   55.38%
==============================================
  Files                  ?      176
  Lines                  ?     4505
  Branches               ?      746
==============================================
  Hits                   ?     2495
  Misses                 ?     1774
  Partials               ?      236

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


Bug 1015 protect my offer request create ethan

Changed  to .  This is easier to read than the way it is done in MasterPage.tsx.

This pull request is on top of previous pull request.  To see the change this pull request did compared to other pull request, look at last commit.


⚠ Bofrost.de has degraded performance

In 21695f1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 708 ms

Resolved: Bofrost.de performance has improved in 250002b.


[ML] [Pipelines] fix: _get_snapshot_path_info used a different ignore…

Description
cherry-pick from (#30338)

fix: _get_snapshot_path_info return wrong asset hash

fix ci by manually update hash to Linux value (should fail on windows)

fix ci and add test for cross os case

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


[minio-cpp] Update to 0.2.0

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

CI seems stuck

/azp run

Thanks for the update!


Optimized the configuration to improve CPU utilization.

Airline
w/o CrossProduct
bin/testDecisionForest Y 23013803 13 3000000 13 F A 160 model-inference/decisionTree/experiments/airline_classification.csv_test.csv
bin/testDecisionForest N 23013803 13 3000000 13 F A 160 model-inference/decisionTree/experiments/airline_classification.csv_test.csv model-inference/decisionTree/experiments/models/airline_classification_xgboost_1600_8_netsdb XGBoost
****UDF Execution Time Duration: ****1071.08 secs.
output count:23013803
positive count:15176946
w/ CrossProduct
bin/testDecisionForestWithCrossProduct Y 23013803 13 500000 13 28 model-inference/decisionTree/experiments/airline_classification.csv_test.csv  model-inference/decisionTree/experiments/models/airline_classification_xgboost_1600_8_netsdb XGBoost
bin/testDecisionForestWithCrossProduct N 23013803 13 500000 13 28 model-inference/decisionTree/experiments/airline_classification.csv_test.csv  model-inference/decisionTree/experiments/models/airline_classification_xgboost_1600_8_netsdb XGBoost 1600
****Model Inference Time Duration: ****220.045 secs.
total count:23013803
positive count:15176946

I can reproduce the results of w/ CrossProduct. Will test w/o CrossProduct tomorrow.
****Model Inference Time Duration: ****222.23 secs.

From my side, the results of w/o Crossproduct:
****UDF Execution Time Duration: ****962.45 secs.
****UDF Load Model Time Duration: ****6.1425 secs.
It is similar to your results. It looks good to me.


Only analyze classes from checks-api plugin

Consistent with https://github.com/jenkinsci/checks-api-plugin/blob/1a45e19783b3aa219d65bf0ece0364d06db6b160/src/test/java/io/jenkins/plugins/checks/PackageArchitectureTest.java#L20. Discovered in https://github.com/jenkinsci/bom/pull/1385#issuecomment-1211020782.
CC @uhafner

Thanks @ufhaner! I tested this PR in this run and the Checks API tests are now passing, so I would appreciate a merge and release for BOM purposes.

Thank you, Tim! :bowing_man:


Fixing isolation in isolated notebook tests

Fixes isolation in isolated notebook tests.
Also fixes notebooks that are broken.
With the cirq.kraus renaming change, couple of notebooks are failing, however the isolated notebook tests did not capture the errors. This is because they were not truly isolated as they inherited the PYTHONPATH env var and never tested the execution path where cirq is not installed.

Automerge cancelled: A status check is failing.


What's the difference between your implementation and this KISS implementation?

What's the difference between your implementation and this KISS implementation?
const allLimit = async (promises, { concurrency = 0 } = {}) => {
  if (concurrency < 1) {
    return (await Promise.all(promises.map((p) => p())));
  }
  let result = [];
  for (const promisesChunk of chunk(promises, concurrency)) {
    const t = await Promise.all(promisesChunk.map((p) => p()));
    result = result.concat(t);
  }
  return result;
};

Do we really need yocto-queue?

Do we really need yocto-queue?

Yes: https://github.com/sindresorhus/p-limit/pull/46

Thank you I haven't found this merge request before.
It's pretty clear to me.
I close this issue.


PEP8 violations at a few places

While going through the codebase, I've noticed a few PEP8 violations which can be fixed by a static code analysis tool like coala.

@yash-nisar feel to go through this alright imho as a low priority and small touches at a time.
Remember than PEP8 is not an end of its own though: See https://www.youtube.com/watch?v=wf-BqAjZb8M
And making large format changes to a codebase is fraught with problems for any pending PR and work in progress

Closing this as duplicate of #532


Receive video stream as input

Hi, I tried to modify test_simple.py to implement support for input video files for depth prediction, but this doesn't seem to work because PoseNet in the paper predicts from multiple frame images.
Is this correct? How should I modify the code to achieve this or is there any existing code for this?

Hi, you don't need the PoseNet when inferring the model. So, it's possible to take a video as the input.
This for loop loads the path of each image and feeds it into the DepthNet. Therefore, you can write your video loading code here and you input each frame of the video.

Thank you for your answer.


Update free-programming-books-ar.md

Added AVR section
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

It's usually not helpful to add a category for a single resource. Try to find another category, or see if there are other books in our lists that would fit into your category. "AVR" is awfully specific, if this can't go in Arduino or r-Pi, maybe make a "hardware" category?

What about homogenize like in other lists?

https://github.com/EbookFoundation/free-programming-books/search?q=embedded
https://github.com/EbookFoundation/free-programming-books/search?q=rtos

- Embedded Systems
  - Arduino

let's use existing "Arduino" and let someone who's read it make the correction if it's wrong

Workflows off since https://github.com/EbookFoundation/free-programming-books/pull/6426/commits/185cd4e86189a33f6edf6958f8b45387f48a4949 :worried:


Print error when resizer is unable to repair all setup violations

We print an error when we run out of space when fixing setup and hold violations, but print nothing if we give up because we aren't making forward progress in setup repair. Our subsequent timing analysis will show up any issues, but it's useful to know what went wrong.

You need to update the messages.txt file using etc/FindMessages.tcl

Thanks for the review.

You need to update the messages.txt file using etc/FindMessages.tcl

@maliberty I updated messages.txt.

Errors throw an error and abort the command script.
I don't think that is appropriate behavior.
I could see adding a warning, but not an error

@jjcherry56 Makes sense, I changed it to a warning.

At some point the logger will have a command to remap message severity so you could change it.


Comparison to kube-aws etc. ?

Hi there,
Any plan to break down differences from going with kube-aws? I'm new to Kubernetes and Kubernetes-on-AWS, coming from AWS ECS experience. I was happy to find your example (through the AWS blog), but then one of the first things I sought was a comparison table or other rationale about why not to build on that tool. Is it to be demonstrative, or for some other design choice?
I'm going to dig in and answer these questions for myself anyways — but thought I'd leave this issue in this persona, wondering this way, since you probably want to know how people receive this :-) So here's one case.
Cheers

Hey @hangtwenty
While we do not have a feature comparison table at the moment, the most important and crucial difference to keep in mind is that our quick start is meant as a way to get a kubernetes cluster up and running fast but not emphasizing on aspects that are required for a production-ready cluster (i.e. multi-master configuration, DR, security hardening -- other than what's recommended by AWS best practices -- and so forth), whereas the aim of tools like kube-aws is to provide you with the options and facilities to bootstrap a production-ready cluster.

OK, so someone like me could:

Start with your quick start to tinker
Once I grok some of it, start looking into kube-aws and kops, comparing and deciding what to proceed with?

Is that how you think of it?

@hangtwenty
That's definitely one of the aims of the quick start and a natural progression path  =)

Thanks!


Installation on official python container fails with "Could not build wheels for duckdb, which is required to install pyproject.toml-based projects"

Installing harlequin into the official python docker image fails when using this Dockerfile and docker build -t harlequin . -f Dockerfile
FROM python
RUN pip install harlequin

Some messages from the log that may be relevant:
/usr/local/lib/python3.12/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.

warning: no files found matching '*.h' under directory 'duckdb'
warning: no files found matching '*.hpp' under directory 'duckdb'
warning: no files found matching '*.cpp' under directory 'duckdb'
warning: no files found matching '*.h' under directory 'src'

If you want to distribute this package, please make sure that 'duckdb-stubs.value' is explicitly added to the `packages` configuration field.

Here is more from the log:
Building wheels for collected packages: duckdb, pyperclip
13.73   Building wheel for duckdb (setup.py): started
74.50   Building wheel for duckdb (setup.py): still running...
135.2   Building wheel for duckdb (setup.py): still running...
195.2   Building wheel for duckdb (setup.py): still running...
210.4   Building wheel for duckdb (setup.py): finished with status 'error'
211.3   error: subprocess-exited-with-error
211.3
211.3   × python setup.py bdist_wheel did not run successfully.
211.3   │ exit code: 1
211.3   ╰─> [4776 lines of output]
211.3       /usr/local/lib/python3.12/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
211.3       !!
211.3
211.3               ********************************************************************************
211.3               Requirements should be satisfied by a PEP 517 installer.
211.3               If you are using pip, you can try `pip install --use-pep517`.
211.3               ********************************************************************************
211.3
211.3       !!
211.3         dist.fetch_build_eggs(dist.setup_requires)
211.3       running bdist_wheel
211.3       running build
211.3       running build_py
211.3       creating build
211.3       creating build/lib.linux-x86_64-cpython-312
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb
211.3       copying duckdb/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb
211.3       copying duckdb/bytes_io_wrapper.py -> build/lib.linux-x86_64-cpython-312/duckdb
211.3       copying duckdb/filesystem.py -> build/lib.linux-x86_64-cpython-312/duckdb
211.3       copying duckdb/udf.py -> build/lib.linux-x86_64-cpython-312/duckdb
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/typing
211.3       copying duckdb/typing/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb/typing
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/functional
211.3       copying duckdb/functional/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb/functional
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/value
211.3       copying duckdb/value/constant.py -> build/lib.linux-x86_64-cpython-312/duckdb/value
211.3       creating build/lib.linux-x86_64-cpython-312/adbc_driver_duckdb
211.3       copying adbc_driver_duckdb/__init__.py -> build/lib.linux-x86_64-cpython-312/adbc_driver_duckdb
211.3       copying adbc_driver_duckdb/dbapi.py -> build/lib.linux-x86_64-cpython-312/adbc_driver_duckdb
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/experimental
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/conf.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/_globals.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/exception.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/_typing.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       copying duckdb/experimental/spark/context.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/group.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/conf.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/readwriter.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/streaming.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/types.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/catalog.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/udf.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/column.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/type_utils.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/_typing.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/session.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/dataframe.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       copying duckdb/experimental/spark/sql/functions.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark/sql
211.3       running egg_info
211.3       writing duckdb.egg-info/PKG-INFO
211.3       writing dependency_links to duckdb.egg-info/dependency_links.txt
211.3       writing top-level names to duckdb.egg-info/top_level.txt
211.3       listing git files failed - pretending there aren't any
211.3       reading manifest file 'duckdb.egg-info/SOURCES.txt'
211.3       reading manifest template 'MANIFEST.in'
211.3       warning: no files found matching '*.h' under directory 'duckdb'
211.3       warning: no files found matching '*.hpp' under directory 'duckdb'
211.3       warning: no files found matching '*.cpp' under directory 'duckdb'
211.3       warning: no files found matching '*.h' under directory 'src'
211.3       warning: manifest_maker: MANIFEST.in, line 6: 'recursive-include' expects <dir> <pattern1> <pattern2> ...
211.3
211.3       writing manifest file 'duckdb.egg-info/SOURCES.txt'
211.3       /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'duckdb-stubs.value' is absent from the `packages` configuration.
211.3       !!
211.3
211.3               ********************************************************************************
211.3               ############################
211.3               # Package would be ignored #
211.3               ############################
211.3               Python recognizes 'duckdb-stubs.value' as an importable package[^1],
211.3               but it is absent from setuptools' `packages` configuration.
211.3
211.3               This leads to an ambiguous overall configuration. If you want to distribute this
211.3               package, please make sure that 'duckdb-stubs.value' is explicitly added
211.3               to the `packages` configuration field.
211.3
211.3               Alternatively, you can also rely on setuptools' discovery methods
211.3               (for example by using `find_namespace_packages(...)`/`find_namespace:`
211.3               instead of `find_packages(...)`/`find:`).
211.3
211.3               You can read more about "package discovery" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
211.3
211.3               If you don't want 'duckdb-stubs.value' to be distributed and are
211.3               already explicitly excluding 'duckdb-stubs.value' via
211.3               `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
211.3               you can try to use `exclude_package_data`, or `include-package-data=False` in
211.3               combination with a more fine grained `package-data` configuration.
211.3
211.3               You can read more about "package data files" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
211.3
211.3
211.3               [^1]: For Python, any directory (with suitable naming) can be imported,
211.3                     even if it does not contain any `.py` files.
211.3                     On the other hand, currently there is no concept of package data
211.3                     directory, all directories are treated like packages.
211.3               ********************************************************************************
211.3
211.3       !!
211.3         check.warn(importable)
211.3       /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'duckdb-stubs.value.constant' is absent from the `packages` configuration.
211.3       !!
211.3
211.3               ********************************************************************************
211.3               ############################
211.3               # Package would be ignored #
211.3               ############################
211.3               Python recognizes 'duckdb-stubs.value.constant' as an importable package[^1],
211.3               but it is absent from setuptools' `packages` configuration.
211.3
211.3               This leads to an ambiguous overall configuration. If you want to distribute this
211.3               package, please make sure that 'duckdb-stubs.value.constant' is explicitly added
211.3               to the `packages` configuration field.
211.3
211.3               Alternatively, you can also rely on setuptools' discovery methods
211.3               (for example by using `find_namespace_packages(...)`/`find_namespace:`
211.3               instead of `find_packages(...)`/`find:`).
211.3
211.3               You can read more about "package discovery" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
211.3
211.3               If you don't want 'duckdb-stubs.value.constant' to be distributed and are
211.3               already explicitly excluding 'duckdb-stubs.value.constant' via
211.3               `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
211.3               you can try to use `exclude_package_data`, or `include-package-data=False` in
211.3               combination with a more fine grained `package-data` configuration.
211.3
211.3               You can read more about "package data files" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
211.3
211.3
211.3               [^1]: For Python, any directory (with suitable naming) can be imported,
211.3                     even if it does not contain any `.py` files.
211.3                     On the other hand, currently there is no concept of package data
211.3                     directory, all directories are treated like packages.
211.3               ********************************************************************************
211.3
211.3       !!
211.3         check.warn(importable)
211.3       /usr/local/lib/python3.12/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'duckdb.experimental' is absent from the `packages` configuration.
211.3       !!
211.3
211.3               ********************************************************************************
211.3               ############################
211.3               # Package would be ignored #
211.3               ############################
211.3               Python recognizes 'duckdb.experimental' as an importable package[^1],
211.3               but it is absent from setuptools' `packages` configuration.
211.3
211.3               This leads to an ambiguous overall configuration. If you want to distribute this
211.3               package, please make sure that 'duckdb.experimental' is explicitly added
211.3               to the `packages` configuration field.
211.3
211.3               Alternatively, you can also rely on setuptools' discovery methods
211.3               (for example by using `find_namespace_packages(...)`/`find_namespace:`
211.3               instead of `find_packages(...)`/`find:`).
211.3
211.3               You can read more about "package discovery" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
211.3
211.3               If you don't want 'duckdb.experimental' to be distributed and are
211.3               already explicitly excluding 'duckdb.experimental' via
211.3               `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
211.3               you can try to use `exclude_package_data`, or `include-package-data=False` in
211.3               combination with a more fine grained `package-data` configuration.
211.3
211.3               You can read more about "package data files" on setuptools documentation page:
211.3
211.3               - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
211.3
211.3
211.3               [^1]: For Python, any directory (with suitable naming) can be imported,
211.3                     even if it does not contain any `.py` files.
211.3                     On the other hand, currently there is no concept of package data
211.3                     directory, all directories are treated like packages.
211.3               ********************************************************************************
211.3
211.3       !!
211.3         check.warn(importable)
211.3       copying duckdb/experimental/__init__.py -> build/lib.linux-x86_64-cpython-312/duckdb/experimental
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb-stubs
211.3       copying duckdb-stubs/__init__.pyi -> build/lib.linux-x86_64-cpython-312/duckdb-stubs
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb-stubs/value
211.3       copying duckdb-stubs/value/__init__.pyi -> build/lib.linux-x86_64-cpython-312/duckdb-stubs/value
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb-stubs/value/constant
211.3       copying duckdb-stubs/value/constant/__init__.pyi -> build/lib.linux-x86_64-cpython-312/duckdb-stubs/value/constant
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb-stubs/functional
211.3       copying duckdb-stubs/functional/__init__.pyi -> build/lib.linux-x86_64-cpython-312/duckdb-stubs/functional
211.3       creating build/lib.linux-x86_64-cpython-312/duckdb-stubs/typing
211.3       copying duckdb-stubs/typing/__init__.pyi -> build/lib.linux-x86_64-cpython-312/duckdb-stubs/typing
211.3       copying duckdb/experimental/spark/LICENSE -> build/lib.linux-x86_64-cpython-312/duckdb/experimental/spark
211.3       running build_ext
211.3       building 'duckdb.duckdb' extension
211.3       creating build/temp.linux-x86_64-cpython-312
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/fts
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/icu
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/icu/third_party
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/icu/third_party/icu
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/icu/third_party/icu/stubdata
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/jemalloc
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/jemalloc/jemalloc
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/jemalloc/jemalloc/src
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/json
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/json/yyjson
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/parquet
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/tpcds
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/tpcds/dsdgen
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/tpcds/dsdgen/dsdgen-c
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/tpch
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/extension/tpch/dbgen
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/src
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/src/common
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/src/common/vector_operations
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/src/verification
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/fastpforlib
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/fmt
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/fsst
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/hyperloglog
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/libpg_query
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/mbedtls
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/mbedtls/library
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/miniz
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/parquet
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/re2
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/re2/re2
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/re2/util
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/snappy
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/snowball
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/snowball/libstemmer
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/snowball/runtime
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/snowball/src_c
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/thrift
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/thrift/thrift
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/thrift/thrift/protocol
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/thrift/thrift/transport
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/utf8proc
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/zstd
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/zstd/common
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/zstd/compress
211.3       creating build/temp.linux-x86_64-cpython-312/duckdb_build/third_party/zstd/decompress
211.3       creating build/temp.linux-x86_64-cpython-312/src
211.3       creating build/temp.linux-x86_64-cpython-312/src/arrow
211.3       creating build/temp.linux-x86_64-cpython-312/src/common
211.3       creating build/temp.linux-x86_64-cpython-312/src/functional
211.3       creating build/temp.linux-x86_64-cpython-312/src/jupyter
211.3       creating build/temp.linux-x86_64-cpython-312/src/native
211.3       creating build/temp.linux-x86_64-cpython-312/src/numpy
211.3       creating build/temp.linux-x86_64-cpython-312/src/pandas
211.3       creating build/temp.linux-x86_64-cpython-312/src/pybind11
211.3       creating build/temp.linux-x86_64-cpython-312/src/pyconnection
211.3       creating build/temp.linux-x86_64-cpython-312/src/pyduckdb
211.3       creating build/temp.linux-x86_64-cpython-312/src/pyexpression
211.3       creating build/temp.linux-x86_64-cpython-312/src/pyrelation
211.3       creating build/temp.linux-x86_64-cpython-312/src/typing
211.3

--- snip ---
... many more rows here ...
--- snip ---

211.3   ERROR: Failed building wheel for duckdb
211.4   Running setup.py clean for duckdb
211.5   Building wheel for pyperclip (setup.py): started
211.7   Building wheel for pyperclip (setup.py): finished with status 'done'
211.7   Created wheel for pyperclip: filename=pyperclip-1.8.2-py3-none-any.whl size=11125 sha256=28d9b1bcc67de63d88f78ad1e95082fad931a58d71220945fce8d110d21a62ef
211.7   Stored in directory: /root/.cache/pip/wheels/b7/e1/45/ce0a91b8cdfed625867580ed90242e4581c4995f69fd062e07
211.7 Successfully built pyperclip
211.7 Failed to build duckdb

It looks like using the official image for python 3.11 works:
FROM python:3.11
RUN pip install harlequin

DuckDB does not yet support Python 3.12; please use a 3.11 image instead.


Update Github actions to latest versions, update Java

Issue #

Description of changes

Update the actions/checkout, actions/cache, and actions/setup-java Github actions to the latest versions
Installs Corretto 17 (latest Corretto LTS version) for its JVM

New/existing dependencies impact assessment, if applicable
No new dependencies were added to this change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/codegen-build-test

/codegen-build-test


zsh-powerlevel10k:init at 2019-07-23

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

What about #65246? Maybe we only need to bump the version there.

@averelld you're right


[FBX] general purpose fixes 🎄

Improving FBX support

Better materials

default values will no longer trigger things like emission, clear coat being enabled etc incorrectly, mostly importers misunderstand this value, a value of 1 is not actually enabled emission, it must have a non zero setting other than emission value for the emission flags to actually be enabled correctly in our engine #42386
lambert materials are warned against significantly, do not use Lambert in Godot, use a PBR material like Ai Standard Surface (it's like going from low quality to high definition in terms of output in scenes and on assets, other engines just make you build the material from scratch)
roughness values are calculated correctly in this version

Fixes for normal's array - some normal's from some files were dropped and generated, this is now fixed.

FBX indexing for items with (-1) index, for normal data is supported, this is super helpful at increasing our range of compatibility of FBX meshes.

Fix bone rest data no longer requiring go to bind pose in Maya and various applications

Partial fix for #43688, animations & skinning needs rebuilt to support this correctly

Validation tools added for validating large projects
Provide package name, vendor and FBX vendor in the log.
Implemented metadata properties so we can read extra document info required for bug reporting
FBX 2011 (version 7200) is unsupported now, you must re-export your file in Maya or Max to upgrade the file format.
Fixes skin bind poses being generated based on node xforms in the scene, this is fixed.
Fixes duplicate bones being added to skin and prevents add_bones from registering skeleton bones it now registers skin bind poses, but this should really be documented in the engine correctly right now it doesn't tell you this is the case.

known bugs:

euler to quat is failing for some files
blender is not exporting skins in the correct format.
- localise skeleton localises but loses important joint orient information (will write better algorithm at end for this to keep skeleton looking good in the engine)
- skinning is disabled & animations are broken by the new changes this will be fixed in a following commit.

OK so #43688 looks like a Euler To Quaternion bug I will dump them all to CSV and make a conversion utility.

blender is not exporting skins in the correct format.

Is this an issue with the importer or Blender itself? If the latter, is there a ticket open on their bug tracker?

blender is not exporting skins in the correct format.

Is this an issue with the importer or Blender itself? If the latter, is there a ticket open on their bug tracker?

The SDK is expecting the skin in global bind pose clusters for the mesh and they export in their own format. I'm going to be discussing this with them directly, but for now Blender FBX won't work for animated meshes. I've already said in the past their exporter can't export to the official SDK correctly skinned meshes, you can't import blender fbx into maya. It's one way at the moment because of this Maya to Blender but not back the way.

Thanks!


Vbguest warning

This plugin was throwing a warning in Windows, so I disabled. Again, squash this please.
https://github.com/dotless-de/vagrant-vbguest
Fixes #14

I have multiple windows fixes. Going to clean up commit history and package as one.


FE-67: Lefthand menu collapse/expand icon not working for Corda community 4.10

Overview
Jira: https://r3-cev.atlassian.net/browse/FE-67
The collapse/expand icon (point right when collapsed, and point down when expand) on the lefthand menu does not work for Corda Community 4.10 page. Works fine on all others.
The cause
the identifier value for release-notes set to "4-10-release-notes", then it was used to dynamically setup data-bs-target & aria-controls attributes for the collapse/expand button. But CSS/html rules string start with number does not works with querySelector, hence the error here. Then it causes the collapse/expand icons not working for the whole page.

Fix
Change the identifier and related fields to "corda-community-4-10-release-notes" will solve the bug.

Good explanation.


Remove cpt-class validation

closes #384

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.7%) to 88.605%

Files with Coverage Reduction
New Missed Lines
%

cpt.py
6
92.68%

broxml/resolvers.py
9
79.83%

Totals

Change from base Build<PHONE_NUMBER>8:
0.7%

Covered Lines:
972

Relevant Lines:
1097

💛  - Coveralls


Auditing for Delete Uk PropertyAnnualSubmission

Pending the upgrade of bootstap-backend-play-28 to 7.11.0


Fix links to project files that result in 404s

Pull Request Description
Fix https://github.com/enso-org/enso-org.github.io/issues/32. This pull request replaces the broken relative references with absolute references.
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, and Rust style guides.
[x] All documentation and configuration conforms to the markdown and YAML style guides.
[x] All code has been tested where possible.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@npentrel to close the ➿, having a look into whether this is fixable on the jekyll side (i.e. in the handling of relative links) because that would mean docs writers don't have to change how they write the docs. However I think this is probably due to the use of this gem and it assuming that all relative links are to other docs in the static site, which is why it's failing to make good links for these build files

@npentrel Ah, ok think I've got it!
jekyll-relative-links can be set to exclude certain directories and files from it's conversion in the site's _config.yml. So the files for which you've had to change the URLs to absolute here can be added to that instead, or the directory when that directory isn't root, I think.

It seems you can only exclude whole files or whole directories. There's files that contain relative links to the repo and to the docs - so excluding the file would break the other links. 🤷♀

Hmm ok. I'd like to find a solution to this that doesn't involve diving into that gem...I would prefer we do absolute paths in that case but as they're GitHub URLs, @iamrecursion's concern is that will break docs navigation in local clones.

Hi @npentrel! Thanks so much for this contribution! Has there been any luck fixing this on the Jekyll side?

This is a substantial problem on the Jekyll side. I'm going to close this for now whilst I find a way to do it, but there is a chance this could circle back round to it being easier to absolute link these things.


Added initialize() to isAuthenticated() function to correctly handle redirects correctly

After logging in, if we input into the address bar http://localhost:3000/profile this would fail authentication and redirect to /failed. The reason is because isAuthenticated() does not have .initialize() and throws an error

{
"errorCode": "uninitialized_public_client_application",
"errorMessage": "You must call and await the initialize function before attempting to call any other MSAL API.  For more visit: aka.ms/msaljs/browser-errors",
"subError": "",
"name": "BrowserAuthError"
}

This should not be needed here. If you're getting an uninitialized error it means you haven't verified inProgress is 'none' before invoking your login/acquireToken APIs.


Grant rights to Azure Function to Get Existing Alerts and to Change their State

Is your question related to a specific version? If so, please specify:
.Net 7
What language does your question apply to? (e.g. C#, JavaScript, Java, All)
C#
Question
I have 2 Azure Functions that need to be able to interact with log alerts in application insights.  I have enabled managed identities for these roles and tried to give them the Contributor role in in just Application Insights.  My code threw the following error: a Exception: Azure.Identity.AuthenticationFailedException: ManagedIdentityCredential authentication failed: Service request failed exception.
I tried granting the identities the owner role in both Application Insights and then in the entire resource group with the same result.

The functions work properly when run locally, but not when published to Azure even though the functions now have the same rights that I do.
Here is the code that I am using to get a bearer token to use with the resource manager Rest API:
        try
        {
            token = await GetAccessTokenAsync("https://management.azure.com/.default");
        }
        catch(Exception ex)
        {
            var result = $"Error retrieving token: {ex.Message}";
            _logger.LogError(ex, result);
            return result;
        }

        public async Task<string> GetAccessTokenAsync(string resourceId)
        {
            var tokenCredential = new DefaultAzureCredential();
            var accessToken = await tokenCredential.GetTokenAsync(
                new TokenRequestContext(scopes: new string[] { resourceId }));
            return accessToken.Token;
        }

Please advise on how I should proceed.
Thank you,
Jason

Please let me know if this this to right place to ask this.

@fabiocav not to push (too much), but do we know roughly when the feature is expected?  I need to decide if I need to build out alternate persistence for alerts I can modify while I wait.


Separate out training config from transformer config

Else it's super annoying to have training details there when you just want a transformer for inference tasks

Done on hooked_prisma branch


Expand descriptions of the various compilation stages

This is what we currently have: https://github.com/rust-lang-nursery/rustc-guide/blob/46864ca9714707f18e658afba9d2ea62afbe2374/src/how-to-build-and-run.md#running-xpy-and-building-a-stage1-compiler
There's a relevant thread on reddit about what these stages all mean and I think the descriptions in this answer could be incorporated into this section in the rustc guide

I am interested in this as my very first PR. I'll prepare it over this weekend.

Thanks @frewsxcv and @ehsanmok :)


[-F] CSV? Get filesize?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Hello,
I'm not familiar with the Python string syntax, and, if possible, I need the following output when running "-F":

CSV instead of JSON
For some reason, the following doesn't return the filesize column:

-F returns this:
ID                                                   EXT RESOLUTION FPS |   FILESIZE   TBR PROTO | VCODEC        VBR ACODEC      ABR ASR MORE INFO
-------------------------------------------------------------------------------------------------------------------------------------------------------------
dash-akfire_interconnect_quic_sep-video-997127a5     mp4 426x240     25 | ~198.61MiB  306k dash  | avc1.640015  306k video only          DASH video, mp4_dash
…

c:\youtube-dlp.exe -q --print "%(formats.:.{format_id,ext,resolution,filesize,vcodec,acodec,})#l" https://acme.com/123456
→
{'format_id': 'hls-akfire_interconnect_quic_sep-audio-high-Original', 'ext': 'mp4', 'resolution': 'audio only', 'vcodec': 'none'}

Thank you.
Provide verbose output that clearly demonstrates the problem

[x] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[x] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
C:\WINDOWS\system32>c:\youtube-dlp.exe -vU
[debug] Command-line config: ['-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [24f827875] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-11-05-git-44a0148fad-essentials_build-www.gyan.dev (setts), ffprobe 2023-11-05-git-44a0148fad-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.19.0, brotli-1.1.0, certifi-2023.07.22, mutagen-1.47.0, requests-2.31.0, sqlite3-3.35.5, urllib3-2.1.0, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests
[debug] Loaded 1901 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
[debug] Downloading _update_spec from https://github.com/yt-dlp/yt-dlp/releases/latest/download/_update_spec
[debug] Downloading SHA2-256SUMS from https://github.com/yt-dlp/yt-dlp/releases/download/2023.12.30/SHA2-256SUMS
Current version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
Current Build Hash: 6de14b1127af1c314864ae0cb04c91ebbf61c230b9cbfb316eade9ea9c5cd982
Updating to<EMAIL_ADDRESS>from yt-dlp/yt-dlp ...
[debug] Downloading yt-dlp.exe from https://github.com/yt-dlp/yt-dlp/releases/download/2023.12.30/yt-dlp.exe
Updated yt-dlp to<EMAIL_ADDRESS>from yt-dlp/yt-dlp
No response

There is currently no support for CSV. There was some discussion on https://github.com/yt-dlp/yt-dlp/issues/6855, but we never managed to come to a consensus. For now, you'll have to pipe the output to an external tools/script to convert the json to csv

Thank you. I'll see if I can find a library that can parse JSON input.
And what about getting the filesize column?

Use --compat-options manifest-filesize-approx and then get filesize_approx. See https://github.com/yt-dlp/yt-dlp/pull/8356 for details


fix minor typo permision -> permission

fix typo permision -> permission

/retitle Fix spelling error in “Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller”
We'll merge this; please do consider a whole-page update when suggesting future changes.
/lgtm
/approve


Override default Flow Router routing event

I was wondering if it's possible to override the default Flow Router page view event?
If so, how would one go about doing this?
We would like to add some extra fields to the default object being sent to the analytic API?
Thanks in advance!

Unfortunately I don't think it would be possible without some refactoring.


qtile: enable wayland backend

Motivation for this change
I wanted to try qtile as a wayland compositor
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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.

Thanks!
Does qtile start -b wayland work for you? I'm getting a segfault, not sure what's going on

Thanks!
Does ./result/bin/qtile start -b wayland work for you? I'm getting a segfault, not sure what's going on

It does work for me, yeah. Both nested in a sway session and from a tty.

Okay good. I also tested with my own derivations and it works when I inherit the dependencies from nixpkgs stable channel, but gives a segfault on current master. Maybe something is wonky in my environment.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/qtile-0-18-wayland-session-not-working/14737/3