PromQL: Parse label sets using the generated parser

This PR extends the generated part of the PromQL parser to parse label sets.
This allows removing some unneeded parts of the old parser.

I've added some error message improvements.
Will work on proper unit testing tomorrow.

There are unit tests that should trigger all possible error messages inside label matchers.

Thanks!


Any HIP kernel support?

Any HIP kernel build and source code correlation support on the schedule?

Hi @hgtsoi, RGA version 2.9.1 and later can be used to perform binary analysis of prebuilt HIP Code Objects binary. Given a prebuilt HIP Code Object binary, you should be able to see a breakdown of all kernels in the file and get the disassembly, VGPR pressure and resource usage statistics per kernel. Line correlation support for HIP binaries is on the roadmap as well.


Updated README.md, Corrected code to centre crop.

@DominicTobias
is this good to merge?

Yep thanks for the update 👍


Ng-class messes with the width of the slider.

So I have a ng-class on 3 div or 2 divs,  it sets the main divs to col-md-4 or col-md-6 that is set based on a variable.
So there is a slider in each div, and it extends to 100% on each slider.
Without the ng-class the sliders work fine.
Incorrect with the ng-class

Correct without the ng-class

Also Strange, Once I resize the window, the sliders jump into place perfectly.

Fixed the issue by adding
controller.refreshSlider = function () {
console.log("hallo")
$timeout(function () {
$scope.$broadcast('rzSliderForceRender');
});
};


Reset previous commit, kept Step 23 change

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

I don't know what I am doing. I was trying to delete this branch but I used git push --set-upstream origin fix/registrationform-typos because I could not delete the branch locally. Can you delete this PR?
I keep getting this message

warning: deleting branch 'fix/registrationform-typos' that has been merged to
'refs/remotes/origin/fix/registrationform-typos', but not yet merged to HEAD.
Deleted branch fix/registrationform-typos (was edcaaa6ae0).

But when I do git branch -a it is still there.

Why create new PR, this is already merged? Once PR was merged to freeCodeCamp:main, you can safely remove local branch. If git branch -d <pr-branch> results in error that it was not yet merged, you can use git branch -D <pr-branch> to force deletion.

Why create new PR?

It was an accident. For some reason, I can't delete the branches on my machine.

Yes, you can safely delete fix/registrationform-typos branch on your fork, and locally. I've shortly explained above what can be done to delete local branch.
Please try to avoid making PRs when you are unsure about outcome. If you have questions regarding contributing please feel free reach out on chat and/or forum.

I did try -D and that didn't work either - sorry about the extra work.

Come on chat or post on forum and we'll try to figure it out.

I'll go to the chat next time for sure. There must be a delay because the branch was gone this morning. But then I console wouldn't load - it was blank. I had to reload VS Code. I did what I did because I thought I was pushing to my clone copy on GitHub. I'm reading up on the difference between upstream and origin and main and...


[Feature]: Support base64 hashDigest in builtin css modules localIdentName

What problem does this feature solve?
For users migrating existing projects across from Webpack css-loader that currently utilise the base64 hashDigest within the localIdentName for classname hashing (currently used as default and recommended values in the docs https://webpack.js.org/loaders/css-loader/#localidentname), this addition would remove the need to change hashing strategies in their projects.
What does the proposed API of configuration look like?
builtins: {
    css: {
        modules: {
	    localIdentName: "[hash:base64]",
	},
    },
},

Would result in a valid hash.

Seems not be different with FilenameTemplate, the css-loader implements a special templated path here cc @JSerFeng @SyMind

@daveskybet We've decided not to implement this feature due to a couple of reasons:

Rspack is designed to be in alignment with webpack's module.generator['css/module'] (experiments.css) functionality, which does not support the localIdentName format [hash:base64].

2.Should you need to use the [hash:base64], it's possible to do so by utilizing css-loader and rspack.CssExtractRspackPlugin to process your CSS files, with next Rspack version 0.6.0.
@ahabhgk cc

Thanks for the update @SyMind, disappointing but understandable.
Do you by any chance have a rough ETA for version 0.6.0?

Do you by any chance have a rough ETA for version 0.6.0?

You should be able to try it within this week


[AutoPR cognitiveservices/data-plane/FormRecognizer] FormRecognizerReceipt - Initial Commit.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6042

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5558


Update CSV to use taint-nodes

Signed-off-by: Jayashree-panda<EMAIL_ADDRESS>Adding taint-nodes to annotations will allow UI to apply taint on selected nodes for OCS cluster creation.

Also... just to be a stickler, the commits should be in reverse order. The change to the merger should come first, and then the generated changes should come afterwards.

/ok-to-test

Oh, and I just noticed: You should be using your @redhat.com email address in all your signatures.

Oh, and I just noticed: You should be using your @redhat.com email address in all your signatures.

My github account is linked with my personal email and not the @redhat.com.

/test ocs-operator-ci

/backport release-4.8

/cherrypick release-4.8


Add a new docs file of M2 GPS device

Add a new docs file of M2 GPS device which supports static initialization.

fix format  by /home/travis/.cache/bazel/_bazel_travis/540135163923dd7d5820f3ee4b306b32/execroot/apollo/bazel-out/local-dbg/testlogs/modules/drivers/gnss/parser/newtonm2_parser_cpplint/test.log


updates to machine names and series Vm's causing issues

Terraform Version
1.02

...

Terraform Variable File
sample-input-minimal.tfvars

...

Steps to Reproduce
Due to azure policies i have had to alter some Vm settings. detailed below, this is causing issues. below.
policies prevent VM names longer than 15 Characters and the use of V4 series VM's

Expected Behavior

Actual Behavior
╷
│ Error: "resource_group_name" may only contain alphanumeric characters, dash, underscores, parentheses and periods
│
│   with data.azurerm_public_ip.aks_public_ip,
│   on main.tf line 277, in data "azurerm_public_ip" "aks_public_ip":
│  277: data "azurerm_public_ip" "aks_public_ip" {
│
╵
╷
│ Error: Post "https://slazsas-aks-099d0392.hcp.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/configmaps": dial tcp <IP_ADDRESS>:443: i/o timeout
│
│   with kubernetes_config_map.sas_iac_buildinfo,
│   on main.tf line 366, in resource "kubernetes_config_map" "sas_iac_buildinfo":
│  366: resource "kubernetes_config_map" "sas_iac_buildinfo" {
│
╵
╷
│ Error: Post "https://slazsas-aks-099d0392.hcp.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/serviceaccounts": context deadline exceeded
│
│   with module.kubeconfig.kubernetes_service_account.kubernetes_sa[0],
│   on modules/kubeconfig/main.tf line 45, in resource "kubernetes_service_account" "kubernetes_sa":
│   45: resource "kubernetes_service_account" "kubernetes_sa" {
│
╵
╷
│ Error: Post "https://slazsas-aks-099d0392.hcp.westeurope.azmk8s.io:443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings": dial tcp <IP_ADDRESS>:443: i/o timeout
│
│   with module.kubeconfig.kubernetes_cluster_role_binding.kubernetes_crb[0],
│   on modules/kubeconfig/main.tf line 53, in resource "kubernetes_cluster_role_binding" "kubernetes_crb":
│   53: resource "kubernetes_cluster_role_binding" "kubernetes_crb" {

...

Additional Context
main.tf in modules azurerm_vm updated to remove the -VM
resource "azurerm_linux_virtual_machine" "vm" {
name                         = "${var.name}vm01"
location                     = var.azure_rg_location
proximity_placement_group_id = var.proximity_placement_group_id == "" ? null : var.proximity_placement_group_id
resource_group_name          = var.azure_rg_name
size                         = var.machine_type
admin_username               = var.vm_admin
zone                         = var.vm_zone
location updated in variable
variable "location" {
description = "The Azure Region to provision all resources in this script"
default     = "West Europe"
**** the root terrform files the following chnages were made.**
-jump shortened
-nfs shortned**
Maint.tf
module "jump" {
source            = "./modules/azurerm_vm"
count             = var.create_jump_vm ? 1 : 0
name              = "${var.prefix}jmp"
azure_rg_name     = module.resource_group.name
module "nfs" {
source                         = "./modules/azurerm_vm"
count                          = var.storage_type == "standard" ? 1 : 0
name                           = "${var.prefix}nfs"
azure_rg_name                  = module.resource_group.name
Variable.tf was updated to point to the locally gnerated ssh keys
variable "ssh_public_key" {
type    = string
default = "~/.ssh/sas.pub"
vm machines updated to V3 as we currently do not allow V4 Vnms
"Standard_D8s_v4"
set to
"Standard_D8s_v3"
tfvars file additions using minimum file example
prefix   = "slazsas" # this is a prefix that you assign for the resources to be created
location = "West Europe" # e.g., "eastus2"
ssh_public_key = "~/.ssh/sas.pub" # Name of file with public ssh key for connecting to the VMs
default_public_access_cidrs = ["20.xx.xx.x/33"] = x placed to secure
**tags = = again added as per instructions
rest left the same in tfvars file until terraform is working**

References

Your CIDR block is incorrect. Should be:
default_public_access_cidrs = ["20.xx.xx.xx/32"]

Note the /32 not a /33. That's not a valid CIDR mapping.

sorry typo on my part,
it is 32
default_public_access_cidrs = ["20.67.XX.X/32"] # e.g., ["<IP_ADDRESS>/32"]
when i added the XX i typed 33 instead of 32
but the file does contain /32

From the machine you're running the repo code run this command:
curl -s ifconfig.me

That value should be the entry you're adding to the cidr block. Please verify

ok i tried that, CIDR block i was using was CIDR of the VM that i want to run everything from eventually.
but i have update the CIDR block to my current W/S,, but i still get the same errors.
im using windows 10 WSL at the moment.. i will fire up an ubuntu VM 18.04 and report back.

The code base does not support Windows. You'll have to run from a Linux or Mac OS.

Ok update code base to run on ubuntu and i still get the same error msgs

It's a CIDR issue. The entry in your CIDR block must match either the network or the IP of the machine you're accessing the cluster. Also it's complaining about your resource group name in the error you provided did you fix that?

the cidr block
default_public_access_cidrs = ["<IP_ADDRESS>/32"] # e.g., ["<IP_ADDRESS>/32"]
resource group prefix = slazsas
i'll try running it with just = slaz

So as long as your machines IP is: <IP_ADDRESS> things will be fine there. The resource group name looks fine as well. If you saved the file on a Windows machine you may have introduced file format issues. I would start fresh on the Ubuntu box and see how far your get.

Hi
I have copied fresh files and updated them but still the same issue.
could the split on line 278 be my issue
data "azurerm_public_ip" "aks_public_ip" {
name                = split("/", module.aks.cluster_slb_ip_id)[8]
resource_group_name = "MC_${module.resource_group.name}${module.aks.name}${module.resource_group.location}"
depends_on          = [module.aks, module.node_pools]
i assume its a seperater "/" ??

This appears to be the code your referring too:
data "azurerm_public_ip" "cluster_public_ip" {
  count               = var.aks_private_cluster ? 0 : 1

  # effective_outbound_ips is a set of strings, that needs to be converted to a list type
  name                = split("/", tolist(azurerm_kubernetes_cluster.aks.network_profile[0].load_balancer_profile[0].effective_outbound_ips)[0])[8]
  resource_group_name = "MC_${var.aks_cluster_rg}_${var.aks_cluster_name}_${var.aks_cluster_location}"

  depends_on = [azurerm_kubernetes_cluster.aks]
}

Where this line is throwing the error:
  resource_group_name = "MC_${var.aks_cluster_rg}_${var.aks_cluster_name}_${var.aks_cluster_location}"

The error is stating that the variable ${var.aks_cluster_rg} and/or ${var.aks_cluster_name} and/or ${var.aks_cluster_location} are not formed correctly causing the resulting resource_group_name to be malformed.
You'll have to determine what items have been created, i.e.

Was the AKS resource group created? You'll need to check the Azure portal to determine that.
If the cluster was setup what is it's name? Again in the portal you'll need to verify that the AKS cluster was configured
You'll have to validate the cluster location. Azure portal again.

In all cases you can verify what's been created up to a given point by using the Azure Portal. Once you're in the portal you can also look to see if the AKS resource groups name is there and has the correct format.
We've not tested the code in the West Europe location. There may be an issue there.
If you can provide information on what you find in more detail that would help.

OK the Resource group is being created and partially populated. So why the name error i don't know.
i'll do a test in Est US and see if that works.

Resource group and items created
RG created = MC_slazsas-rg_slazsas-aks_westeurope
NAME	TYPE	LOCATION
0ea0362e-51a0-4b9b-be9c-ee9da7071531	Public IP address	West Europe
aks-agentpool-03150549-nsg	Network security group	West Europe
aks-agentpool-03150549-routetable	Route table	West Europe
aks-cas-03150549-vmss	Virtual machine scale set	West Europe
aks-compute-03150549-vmss	Virtual machine scale set	West Europe
aks-connect-03150549-vmss	Virtual machine scale set	West Europe
aks-stateful-03150549-vmss	Virtual machine scale set	West Europe
aks-stateless-03150549-vmss	Virtual machine scale set	West Europe
aks-system-03150549-vmss	Virtual machine scale set	West Europe
kubernetes	Load balancer	West Europe
slazsas-aks-agentpool	Managed Identity	West Europe

Hi Found the issue, Name format must be the name not the display name, format i assume in varaiables and tfvars. I updated both.
az account list-locations -o table.
Now i only have the following errors which i assume relate to the CIDR adddres
│ Error: Post "https://slazsas-aks-87cc1f1a.hcp.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/configmaps": dial tcp <IP_ADDRESS>:443: i/o timeout
│
│   with kubernetes_config_map.sas_iac_buildinfo,
│   on main.tf line 366, in resource "kubernetes_config_map" "sas_iac_buildinfo":
│  366: resource "kubernetes_config_map" "sas_iac_buildinfo" {
│
╵
╷
│ Error: Post "https://slazsas-aks-87cc1f1a.hcp.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/serviceaccounts": context deadline exceeded
│
│   with module.kubeconfig.kubernetes_service_account.kubernetes_sa[0],
│   on modules/kubeconfig/main.tf line 45, in resource "kubernetes_service_account" "kubernetes_sa":
│   45: resource "kubernetes_service_account" "kubernetes_sa" {
│
╵
╷
│ Error: Post "https://slazsas-aks-87cc1f1a.hcp.westeurope.azmk8s.io:443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings": dial tcp <IP_ADDRESS>:443: i/o timeout
│
│   with module.kubeconfig.kubernetes_cluster_role_binding.kubernetes_crb[0],
│   on modules/kubeconfig/main.tf line 53, in resource "kubernetes_cluster_role_binding" "kubernetes_crb":
│   53: resource "kubernetes_cluster_role_binding" "kubernetes_crb" {

Great, and yes the timeout issues are related to the CIDR issue.

would <IP_ADDRESS>/32 be acceptable for testing, as the CIDR is the last hurdle and keeps failing

What machine are your running the terraform/docker/ansible on? From that machine run the following command:
curl -s ifconfig.me

Take the IP returned there and add that to the CIDR block.
For example, if the IP returned was <IP_ADDRESS> you would add "<IP_ADDRESS>/32" to your CIDR block.

Closing this issue. You've figured out the name issue.

just to confirm,, user must have contributor roles on the subscription, with  also identity  contributor role..
as i suspect that is the last issue, i have contributor access on the subscription, but not access to add identities/ users

i have terraform/docker/jq/kubecttl/ azure cli installed

Authentication requirements : https://github.com/sassoftware/viya4-iac-azure/blob/main/docs/user/TerraformAzureAuthentication.md


Permit user programs that decide on stack outputs in a Future

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Current signature Pulumi.run assumes that the program will immediately register the stack outputs:
        Pulumi.run(ctx -> {
            ctx.export("a", Output.of(1));
        });

What if the program does not know what the set of stack outputs is going to be until some CompletableFuture? The awkward workaround right now is to force (join) the Future inside the Pulumi program:
        CompletableFuture<String> xname;
        Pulumi.run(ctx -> {
            var x = xname.join();
            ctx.export(x, Output.of(1));
        });

It would be nice to allow deferring that without blocking a thread. Perhaps Pulumi.run(Function<Context,CompletableFuture<Void>>) overload to let the user program signal to the framework that it has some work to do.
I believe underlying framework supports this just fine, but we do not expose this capability to the user at the moment.
Not sure how useful this is in practice, but logging for posterity.

Affected area/feature

Should be quite easy to achieve, if we decide to expose this kind of API.
Adding an overload to the DefaultRunner and an overloaded run and runAsync should do it from top of my head.
Internally, changing this:
public <T> CompletableFuture<Result<T>> runAsync(Supplier<T> callback) {
            var valueFuture = CompletableFuture.supplyAsync(callback);
            ...

into:
public <T> CompletableFuture<Result<T>> runAsync(CompletableFuture<Supplier<T>> callback) {
            ...

in the DefaultRunner would allow for this API to be added.


Deprecate CLI utility methods in RabbitMQ module

Those utility methods couple the implementation to the cli, which is only provided when using management image. Also, although very convinient methods, it will be hard to maintain for every command in the cli.

I see your point, but this change seriously broke the DX for us. In 1.19.0, we could initialize and configure the complete container in one command on a static field. B/c of the required exception handling (and also the different return type), we now would need to generate a dedicated ApplicationContextInitializer method to execute the raw commands via execInContainer.
What do you think about moving these convenience methods into a dedicated subclass, i.e. RabbitMQMgmtContainer?

Those utility methods couple the implementation to the cli, which is only provided when using management image.

Interestingly enough:
https://github.com/testcontainers/testcontainers-java/blob/dd1427ebd30bbaba7f32184f1376b7c21e725ab5/modules/rabbitmq/src/main/java/org/testcontainers/containers/RabbitMQContainer.java#L39C40-L39C40

Also, although very convinient  methods, it will be hard to maintain for every command in the cli.

@eddumelendez does RabbitMQ have a history of often changing or breaking the CLI options?

Hi, few notes:

Default images should not be used. That's the reason why those are deprecated
Testcontainers responsibility is about container initialization

@eddumelendez i understand you points and that this was the proper action to reduce scope creep of testcontainers.
Do you think it would be OK to keep the current containerIsStarted hook and simply expose a single fluid utility method on RabbitMQContainer where one could add commands to the values array?
At the end of the day that's the biggest loss here and it would be superawesome to still have a way of configuring "onReady" commands while keeping object initialization down to a single command that doesn't require additional exception handling (as it's completely fine the way containerIsStarted currently logs them).

Do you think it would be OK to keep the current containerIsStarted hook and simply expose a single fluid utility method on RabbitMQContainer where one could add commands to the values array?

I think vault and consul are doing it like that. Indeed, this is something we have been discussing. But, aligning all the modules would be until version 2.0.

May I kindly ask you to eat your own dog food and adapt your own tests, e.g.  RabbitMQContainerTest.shouldCreateRabbitMQContainerWithExchangeInVhost ?


add support for a centos7 based image

for a variety of reasons I need a centos based image.   I also added a way to override the url of the file being downloaded so that you could build it locally with for example the supported RedHat amq distribution.

Hi @abedwardsw,
Thanks for this, as I guess you might have figure as you created #89  the main issue here is the build time.
I discussed with colleagues and friends and gave it some thinking. The main benefit of having an image for every possible base image (centos, suse, slackware, etc)  would be to reduce the usage of disk space in a cluster, but that purpose is defeated by the pervasive lack of reproducible builds in the docker world.
Hence, I decided to keep it small and just add the two distros with outstanding value due to a real difference in the approach plus big community outreach: debian + alpine. It also helps me to maintain a reasonable build time that plays well with travis.
Regarding the old versions, I'll comment in the issue. I already marked many as deprecated and maintained as best effort as per strikethrough in version list and excerpt:

All versions of ActiveMQ Artemis are provided for the time being but versions previous to 1.5.5 shall be considered deprecated and could be removed at any time.

However, my plan was to maintain support as long as ActiveMQ Artemis maintain support.
One possible solution to your need could be perhaps to have a parallel activemq-artemis-centos image in dockerhub based on this PR. I would be keen on helping with the occasional maintenance if you want to go ahead with the project. None the less in the meantime, I'm going to close this but not before thanking you again for the time and effort spent on this.


[HELP] How to make a window stay on top

How to make a window stay on top

(set_transient_for)[https://gtk-rs.org/gtk4-rs/stable/latest/docs/gtk4/prelude/trait.NativeDialogExt.html#method.set_transient_for]?


Arm and Disarm trough serial

It is possible or you have experience arming and disarming the alarm trough this interface?

IMHO this is possible, since this can be done with third party modules that hook into the same serial port. Not sure how though.

Good day!
How can I apply the security switch that restarts HardwareSerial after 3 consecutive failed packet decoding attempts?
I have the problem that after a few minutes of operation! can not read the serial again!
thank you


TypeScript Named Tuples cause the coloring to get messed up

TS and JS Grammar Extension version:  1.4.0
Code
const v = {
  room: {
    /** Indexed by grid index. */
    initializedGridEntities: new Map<
      int,
      [gridEntityType: GridEntityType, state: int]
    >(),
  },
};

It looks like this in VSCode:

Notice how the final characters should be white, but they are instead blue because the named tuple messes the rest of the block up.

This is limitation of tmGrammr  Map< is treated as relational operator instead of type argument start because we cant lookup beyond the line.
Duplicate of #738


Issue:53 dependencies needs to be updated

Dependencies updated to the latest version

Sorry I never got around to dealing with this :( Should resolved with https://github.com/reduxjs/cra-template-redux-typescript/releases/tag/v2.0.0 .


kube-dns and kubernetes-dashboard fail to come up

These may be seperate issues but its difficult to tell. I spin up a vanilla cluster in westus2 with file.
cluster comes up and api is accessible, however both the dashboard and kube-dns pods are in a crashloopbackoff. the kube-dns pod is listing some errors.
the dashboard logs are simpler but perhaps more perplexing as the api is accessible but it says it cannot connect.
as both of these are addons it could be a fault with the addon manager whose log is here.

Some further debugging seems to point to the same issue, that neither the dashboard or the dns can access the kubernetes service. The kubedns container seems to start, however it lists the api as nil and then fails to forward the dns requests.
I0120 20:34:05.916909       1 server.go:94] Using https://<IP_ADDRESS>:443 for kubernetes master, kubernetes API: <nil>
I0120 20:34:05.917532       1 server.go:99] v1.4.0-alpha.2.1652+c69e3d32a29cfa-dirty
I0120 20:34:05.917564       1 server.go:101] FLAG: --alsologtostderr="false"
I0120 20:34:05.917572       1 server.go:101] FLAG: --dns-port="10053"
I0120 20:34:05.917578       1 server.go:101] FLAG: --domain="cluster.local."
 Listening on port:10053
I0120 20:34:05.917815       1 server.go:145] skydns: metrics enabled on : /metrics:
I0120 20:34:05.917830       1 dns.go:167] Waiting for service: default/kubernetes
I0120 20:34:05.917921       1 logs.go:41] skydns: ready for queries on cluster.local. for tcp://<IP_ADDRESS>:10053 [rcache 0]
I0120 20:34:05.917941       1 logs.go:41] skydns: ready for queries on cluster.local. for udp://<IP_ADDRESS>:10053 [rcache 0]
I0120 20:34:12.204164       1 logs.go:41] skydns: failure to forward request "read udp <IP_ADDRESS>:54960-><IP_ADDRESS>:53: i/o timeout"
I0120 20:34:12.204256       1 logs.go:41] skydns: failure to forward request "read udp <IP_ADDRESS>:54960-><IP_ADDRESS>:53: i/o timeout"

Please pull the latest ACS-Engine. It includes a fix for this issue. See more details here: https://github.com/Azure/ACS/issues/3

I have pulled and rebuilt with the latest version. However, both the master and agent nodes are brought up with docker 1.13.0

looking into the template on the azure portal itself I can see that the variable for both the master and agent has a variable:
"dockerEngineVersion": "1.12.*"
so it appears that the installation script is for some reason ignoring the version

I'm afraid I can't reproduce this. On HEAD of master with git commit: 7cd3e7f7d17c59e6fe4b014e61688bba3df92cfa
NAMESPACE     NAME                                            READY     STATUS    RESTARTS   AGE
kube-system   heapster-v1.2.0-194960081-hpsl3                 2/2       Running   0          10m
kube-system   kube-addon-manager-k8s-master-33416968-0        1/1       Running   0          10m
kube-system   kube-apiserver-k8s-master-33416968-0            1/1       Running   0          10m
kube-system   kube-controller-manager-k8s-master-33416968-0   1/1       Running   0          10m
kube-system   kube-dns-v19-2j9v0                              3/3       Running   0          10m
kube-system   kube-dns-v19-b1n4z                              3/3       Running   0          10m
kube-system   kube-proxy-cpxsm                                1/1       Running   0          10m
kube-system   kube-proxy-qc30g                                1/1       Running   0          10m
kube-system   kube-proxy-w0z7j                                1/1       Running   0          10m
kube-system   kube-scheduler-k8s-master-33416968-0            1/1       Running   0          10m
kube-system   kubernetes-dashboard-1872455951-b1nts           1/1       Running   0          10m

To help any further, I'd need you to send me these files from the master and at least one node:

/var/log/cloud-init.log
/var/log/cloud-init-output.log
/var/lib/cloud/instance/user-data.txt
/var/lib/cloud/instance/cloud-config.txt

I think the following are probably relavent:
cloud-init-output.log (on master)
The following additional packages will be installed:
  aufs-tools cgroupfs-mount libltdl7
Suggested packages:
  mountall
The following NEW packages will be installed:
  aufs-tools cgroupfs-mount docker-engine libltdl7
0 upgraded, 4 newly installed, 0 to remove and 146 not upgraded.
Need to get 19.3 MB/19.4 MB of archives.
After this operation, 89.2 MB of additional disk space will be used.
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4970 B]
Get:2 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
Get:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 docker-engine amd64 1.13.0-0~ubuntu-xenial [19.2 MB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 19.3 MB in 0s (29.0 MB/s)
Selecting previously unselected package aufs-tools.
(Reading database ... 61253 files and directories currently installed.)
Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
Unpacking cgroupfs-mount (1.2) ...
Selecting previously unselected package libltdl7:amd64.
Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.6-0.1) ...
Selecting previously unselected package docker-engine.
Preparing to unpack .../docker-engine_1.13.0-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-engine (1.13.0-0~ubuntu-xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu6) ...
Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Setting up cgroupfs-mount (1.2) ...
Setting up libltdl7:amd64 (2.4.6-0.1) ...
Setting up docker-engine (1.13.0-0~ubuntu-xenial) ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(group) request, exiting
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Cloud-init v. 0.7.7 running 'modules:final' at Fri, 20 Jan 2017 23:40:44 +0000. Up 40.69 seconds.
Cloud-init v. 0.7.7 finished at Fri, 20 Jan 2017 23:41:44 +0000. Datasource DataSourceAzureNet [seed=/dev/sr0].  Up 102.00 seconds

while the file: /etc/apt/preferences.d/docker.pref
Package: docker-engine Pin: version 1.12.* Pin-Priority: 550

so it appears the pin line is correctly written to apt preferences but the docker-engine install jumps to 1.13.0 anyway

there appears to be a discrepency between the hold lines in cloud-config and user-data.txt
cloud-config.txt:
- echo "deb https://apt.dockerproject.org/repo ubuntu-xenial main" | sudo tee /etc/apt/sources.list.d/docker.list
- 'echo "Package: docker-engine Pin: version 1.12.* Pin-Priority: 550 " > /etc/apt/preferences.d/docker.pref'

while user-data.txt
- "echo \"Package: docker-engine
Pin: version 1.12.*
Pin-Priority: 550
\" > /etc/apt/preferences.d/docker.pref"

checking the ubuntu reference it looks like the individual entries should be on seperate lines but the actual pin file is all on one line. I suspect there is a new line escaping issue here.

I really need all of the files mentioned, please. Like I said, we're not
seeing this anywhere else so I need to figure out why yours is different.
On Fri, Jan 20, 2017 at 4:34 PM, Jonathan Fraser<EMAIL_ADDRESS>wrote:

I think the following are probably relavent:
cloud-init-output.log (on master)
The following additional packages will be installed:
aufs-tools cgroupfs-mount libltdl7
Suggested packages:
mountall
The following NEW packages will be installed:
aufs-tools cgroupfs-mount docker-engine libltdl7
0 upgraded, 4 newly installed, 0 to remove and 146 not upgraded.
Need to get 19.3 MB/19.4 MB of archives.
After this operation, 89.2 MB of additional disk space will be used.
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4970 B]
Get:2 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
Get:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 docker-engine amd64 1.13.0-0~ubuntu-xenial [19.2 MB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 19.3 MB in 0s (29.0 MB/s)
Selecting previously unselected package aufs-tools.
(Reading database ... 61253 files and directories currently installed.)
Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
Unpacking cgroupfs-mount (1.2) ...
Selecting previously unselected package libltdl7:amd64.
Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.6-0.1) ...
Selecting previously unselected package docker-engine.
Preparing to unpack .../docker-engine_1.13.0-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-engine (1.13.0-0~ubuntu-xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu6) ...
Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Setting up cgroupfs-mount (1.2) ...
Setting up libltdl7:amd64 (2.4.6-0.1) ...
Setting up docker-engine (1.13.0-0~ubuntu-xenial) ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(group) request, exiting
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Cloud-init v. 0.7.7 running 'modules:final' at Fri, 20 Jan 2017 23:40:44 +0000. Up 40.69 seconds.
Cloud-init v. 0.7.7 finished at Fri, 20 Jan 2017 23:41:44 +0000. Datasource DataSourceAzureNet [seed=/dev/sr0].  Up 102.00 seconds
while the file: /etc/apt/preferences.d/docker.pref
Package: docker-engine Pin: version 1.12.* Pin-Priority: 550
so it appears the pin line is correctly written to apt preferences but the
docker-engine install jumps to 1.13.0 anyway
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Azure/acs-engine/issues/200#issuecomment-274215974,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAT9dOSJ27MmaEOv1OHqT1Cy35UdbsEwks5rUVKXgaJpZM4LprmD
.

Also, how exactly are you deploying the template afterward?
On Fri, Jan 20, 2017 at 4:43 PM, Cole Mickens<EMAIL_ADDRESS>wrote:

I really need all of the files mentioned, please. Like I said, we're not
seeing this anywhere else so I need to figure out why yours is different.
On Fri, Jan 20, 2017 at 4:34 PM, Jonathan Fraser<EMAIL_ADDRESS>
wrote:

I think the following are probably relavent:
cloud-init-output.log (on master)
The following additional packages will be installed:
aufs-tools cgroupfs-mount libltdl7
Suggested packages:
mountall
The following NEW packages will be installed:
aufs-tools cgroupfs-mount docker-engine libltdl7
0 upgraded, 4 newly installed, 0 to remove and 146 not upgraded.
Need to get 19.3 MB/19.4 MB of archives.
After this operation, 89.2 MB of additional disk space will be used.
Get:1 http://azure.archive.ubuntu.com/ubuntu xenial/universe amd64 cgroupfs-mount all 1.2 [4970 B]
Get:2 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 libltdl7 amd64 2.4.6-0.1 [38.3 kB]
Get:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 docker-engine amd64 1.13.0-0~ubuntu-xenial [19.2 MB]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 19.3 MB in 0s (29.0 MB/s)
Selecting previously unselected package aufs-tools.
(Reading database ... 61253 files and directories currently installed.)
Preparing to unpack .../aufs-tools_1%3a3.2+20130722-1.1ubuntu1_amd64.deb ...
Unpacking aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../cgroupfs-mount_1.2_all.deb ...
Unpacking cgroupfs-mount (1.2) ...
Selecting previously unselected package libltdl7:amd64.
Preparing to unpack .../libltdl7_2.4.6-0.1_amd64.deb ...
Unpacking libltdl7:amd64 (2.4.6-0.1) ...
Selecting previously unselected package docker-engine.
Preparing to unpack .../docker-engine_1.13.0-0~ubuntu-xenial_amd64.deb ...
Unpacking docker-engine (1.13.0-0~ubuntu-xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu6) ...
Setting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...
Setting up cgroupfs-mount (1.2) ...
Setting up libltdl7:amd64 (2.4.6-0.1) ...
Setting up docker-engine (1.13.0-0~ubuntu-xenial) ...
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(group) request, exiting
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Cloud-init v. 0.7.7 running 'modules:final' at Fri, 20 Jan 2017 23:40:44 +0000. Up 40.69 seconds.
Cloud-init v. 0.7.7 finished at Fri, 20 Jan 2017 23:41:44 +0000. Datasource DataSourceAzureNet [seed=/dev/sr0].  Up 102.00 seconds
while the file: /etc/apt/preferences.d/docker.pref
Package: docker-engine Pin: version 1.12.* Pin-Priority: 550
so it appears the pin line is correctly written to apt preferences but
the docker-engine install jumps to 1.13.0 anyway
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Azure/acs-engine/issues/200#issuecomment-274215974,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAT9dOSJ27MmaEOv1OHqT1Cy35UdbsEwks5rUVKXgaJpZM4LprmD
.

azure group deployement create

What version? azure --version?
I'm pretty sure you're being bitten by a bug in the CLI actually. The docs should have instructed you to either downgrade it to a working version, or use the new az cli. I strongly recommend the latter.

the version is 0.10.7, though how would a this be a cli bug?

The CLI doesn't escape the JSON payload correctly. The newlines are rendered as literals and so when they're placed on box, they're incorrect. -- The apt preference file is supposed to be three lines, not one.
Please downgrade azure or switch to az.

(For whatever reason the CLI parses the JSON to ensure it's correctly formatted, but they submit the output of that process, rather than the original body. There's a bug in that process that causes escape literals in javascript to be processed incorrectly. Basically, the file on disk and the file submitted to the Azure API have more differences than just whitespace -- which is the bug).
I'm trying to get confirmation of whether this is fixed in 0.10.8, but like I said, az is better for a lot of reasons anyway.

that would explain the behaviour, I'll make the appropriate script changes and redeploy

It does appear the parser shipped in 0.10.8 is changed, so you might be able to do a minor (not really a bugfix release the way they're doing versioning). Might be less disruptive than changing to az. (But please note, I haven't personally tested 0.10.8.)

although one could argue that those echos should be a write_file instead of a run command as file write happen first anyway. moreover cloud init supports version pinning a file directly as well as install addition repos so most of those commands could be handled in native cloud init.

Good points. If you wanted to file issues for that, or better yet, send PRs, we would take them under consideration.
Let me know if you were unblocked and we can close this one out at least. Thanks!

Looks like that was it, cutting over the the python client fixed the problem.

Glad to hear it. Thanks for the patience and quick back and forth while troubleshooting. Cheers.

I am having the same issues.
Deployed a brand new cluster using kubernetes-anywhere and the kube-dns and dashboard pods are stuck in a Crash Loop.
This issue is marked as "Closed" but I don't understand what I should do to fix the problem.
(using azure v0.10.8, tried kubernetes 1.4.8 and 1.5.2, kubernetes-anywhere master branch)

Hi Aron,
Sounds like you are hitting the following issue: https://github.com/Azure/ACS/issues/3.
You can fix your existing cluster with the workaround script or upgrade to the latest ACS-Engine.
Thanks,
Anthony
From: Aron<EMAIL_ADDRESS>Sent: Saturday, January 28, 2017 5:41 AM
To: Azure/acs-engine<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [Azure/acs-engine] kube-dns and kubernetes-dashboard fail to come up (#200)
I am having the same issues.
Deployed a brand new cluster using kubernetes-anywhere and the kube-dns and dashboard pods are stuck in a Crash Loop.
This issue is marked as "Closed" but I don't understand what I should do to fix the problem.
(using azure v0.10.8, tried kubernetes 1.4.8 and 1.5.2, kubernetes-anywhere master branch)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Facs-engine%2Fissues%2F200%23issuecomment-275848780&data=02|01|Anthony.Howe%40microsoft.com|7181356ca615450e8cff08d4478359fc|72f988bf86f141af91ab2d7cd011db47|1|0|636212076860443596&sdata=hXFwAa8S2HijdqxnYPfpkuwWkIvQHJ1u0KpgRjUvmRA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL_fKhsDEaoy0eCkLnrVouyXZroy_15iks5rW0WAgaJpZM4LprmD&data=02|01|Anthony.Howe%40microsoft.com|7181356ca615450e8cff08d4478359fc|72f988bf86f141af91ab2d7cd011db47|1|0|636212076860443596&sdata=zSy7HItLgpLKXqQDhFE%2FdspkP2zi18CifiHLDOreSCw%3D&reserved=0.

thank you.
indeed downgrading docker to 1.12.* solved that issue for me.
...
Now I'm stuck on the next issue https://github.com/kubernetes/kubernetes/issues/40332
:)

Are you using the latest ACS-Engine?  This is not a problem in the latest ACS-Engine since it uses kubernetes 1.5.1: https://github.com/Azure/acs-engine/blob/master/pkg/acsengine/const.go.
Thanks,
Anthony
From: Aron<EMAIL_ADDRESS>Sent: Saturday, January 28, 2017 10:02 AM
To: Azure/acs-engine<EMAIL_ADDRESS>Cc: Anthony Howe<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Azure/acs-engine] kube-dns and kubernetes-dashboard fail to come up (#200)
thank you.
indeed downgrading docker to 1.12.* solved that issue for me.
...
Now I'm stuck on the next issue kubernetes/kubernetes#40332https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkubernetes%2Fkubernetes%2Fissues%2F40332&data=02|01|Anthony.Howe%40microsoft.com|7b2ea5bfc7874c2ce87d08d447a7b5ef|72f988bf86f141af91ab2d7cd011db47|1|0|636212233018045932&sdata=8YAno7c2IoQjR2zi8NaMSkfliE1QdgW5yhYhCmqEC1k%3D&reserved=0
:)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Facs-engine%2Fissues%2F200%23issuecomment-275863637&data=02|01|Anthony.Howe%40microsoft.com|7b2ea5bfc7874c2ce87d08d447a7b5ef|72f988bf86f141af91ab2d7cd011db47|1|0|636212233018045932&sdata=Zjd34VPVTEswqxQuYGUDG9LkTtTrbvcEwPBChRZy3uw%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL_fKg14qIjSks1h51DyJEarPlBXUbbcks5rW4J_gaJpZM4LprmD&data=02|01|Anthony.Howe%40microsoft.com|7b2ea5bfc7874c2ce87d08d447a7b5ef|72f988bf86f141af91ab2d7cd011db47|1|0|636212233018045932&sdata=t7VJ2GCHFbdQ%2FwcrGAko0vEwZ0N6t4dDKTlqaT5iVQY%3D&reserved=0.

Unfortunately I used kubernetes-anywhere ( https://github.com/kubernetes/kubernetes-anywhere ) to deploy and I chose to use the latest release ( 1.5.2 - https://github.com/kubernetes/kubernetes/releases ).


Update eng.1.csv

Updated all the scores. Added (P) for all the matches that were postponed.

@Berserk21 Again your contributions more than welcome.   Let me highlight again -  NOTE: As written in the readme  - the datasets are (auto-)generated  via https://github.com/openfootball/england - thus, with the next (auto-)update (if there's any) your changes / updates get overwritten.


Saving unsloth fine-tuned Mistral 7B is 15GB

Hi,
Having followed your notebook on fine-tuning the Mistral 7B, then saving as q4_k_m GGUF, I'm surprised to see 3 shards of 5GB each, resulting in a final model of 15GB.

Here's the log from model.save_pretrained_gguf("model_q4_k_m_gguf", tokenizer, quantization_method = "q4_k_m"). Note at the bottom the message "unsloth/llama.cpp/quantize): not found", don't knwo if related or occurs befoe clone of llama.cpp, where quantize.exe is not in the llama.cpp folder (Ubuntu).
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
Unsloth: Merging 4bit and LoRA weights to 16bit...
Unsloth: Will use up to 80.95 out of 106.1 RAM for saving.
100%|██████████| 32/32 [00:00<00:00, 56.41it/s]
tokenizer config file saved in model_q4_k_m_gguf/tokenizer_config.json
Special tokens file saved in model_q4_k_m_gguf/special_tokens_map.json
Model config MistralConfig {
  "_name_or_path": "unsloth/mistral-7b",
  "architectures": [
    "MistralForCausalLM"
  ],
  "attention_dropout": 0.0,
  "bos_token_id": 1,
  "eos_token_id": 2,
  "hidden_act": "silu",
  "hidden_size": 4096,
  "initializer_range": 0.02,
  "intermediate_size": 14336,
  "max_position_embeddings": 32768,
  "model_type": "mistral",
  "num_attention_heads": 32,
  "num_hidden_layers": 32,
  "num_key_value_heads": 8,
  "pad_token_id": 2,
  "rms_norm_eps": 1e-05,
  "rope_theta": 10000.0,
  "sliding_window": 4096,
  "tie_word_embeddings": false,
  "torch_dtype": "bfloat16",
  "transformers_version": "4.38.0.dev0",
  "unsloth_version": "2024.1",
  "use_cache": true,
  "vocab_size": 32000
}

Configuration saved in model_q4_k_m_gguf/config.json
Configuration saved in model_q4_k_m_gguf/generation_config.json
Unsloth: Saving tokenizer... Done.
Unsloth: Saving model... This might take 5 minutes for Llama-7b...
The model is bigger than the maximum size per checkpoint (5GB) and is going to be split in 3 checkpoint shards. You can find where each parameters has been saved in the index located at model_q4_k_m_gguf/model.safetensors.index.json.
Done.
==((====))==  Unsloth: Conversion from QLoRA to GGUF information
   \\   /|    [0] Installing llama.cpp will take 3 minutes.
O^O/ \_/ \    [1] Converting HF to GUUF 16bits will take 3 minutes.
\        /    [2] Converting GGUF 16bits to q4_k_m will take 20 minutes.
 "-____-"     In total, you will have to wait around 26 minutes.

Unsloth: [0] Installing llama.cpp. This will take 3 minutes...
Unsloth: [1] Converting HF into GGUF format. This will take 3 minutes...
Loading model file model_q4_k_m_gguf/model-00001-of-00003.safetensors
Loading model file model_q4_k_m_gguf/model-00001-of-00003.safetensors
Loading model file model_q4_k_m_gguf/model-00002-of-00003.safetensors
Loading model file model_q4_k_m_gguf/model-00003-of-00003.safetensors
params = Params(n_vocab=32000, n_embd=4096, n_layer=32, n_ctx=32768, n_ff=14336, n_head=32, n_head_kv=8, n_experts=None, n_experts_used=None, f_norm_eps=1e-05, rope_scaling_type=None, f_rope_freq_base=10000.0, f_rope_scale=None, n_orig_ctx=None, rope_finetuned=None, ftype=<GGMLFileType.MostlyF16: 1>, path_model=PosixPath('model_q4_k_m_gguf'))
Found vocab files: {'tokenizer.model': PosixPath('model_q4_k_m_gguf/tokenizer.model'), 'vocab.json': None, 'tokenizer.json': PosixPath('model_q4_k_m_gguf/tokenizer.json')}
Loading vocab file 'model_q4_k_m_gguf/tokenizer.model', type 'spm'
Vocab info: <SentencePieceVocab with 32000 base tokens and 0 added tokens>
Special vocab info: <SpecialVocab with 0 merges, special tokens {'bos': 1, 'eos': 2, 'unk': 0, 'pad': 0}, add special tokens {'bos': True, 'eos': False}>
Permuting layer 0
Permuting layer 1
Permuting layer 2
...
Permuting layer 30
Permuting layer 31
model.embed_tokens.weight                        -> token_embd.weight                        | BF16   | [32000, 4096]
model.layers.0.input_layernorm.weight            -> blk.0.attn_norm.weight                   | BF16   | [4096]
model.layers.0.mlp.down_proj.weight              -> blk.0.ffn_down.weight                    | BF16   | [4096, 14336]
...
model.layers.31.self_attn.q_proj.weight          -> blk.31.attn_q.weight                     | BF16   | [4096, 4096]
model.layers.31.self_attn.v_proj.weight          -> blk.31.attn_v.weight                     | BF16   | [1024, 4096]
model.norm.weight                                -> output_norm.weight                       | BF16   | [4096]
Writing model_q4_k_m_gguf-unsloth.F16.gguf, format 1
Ignoring added_tokens.json since model matches vocab size without it.
gguf: This GGUF file is for Little Endian only
gguf: Setting special token type bos to 1
gguf: Setting special token type eos to 2
gguf: Setting special token type unk to 0
gguf: Setting special token type pad to 0
gguf: Setting add_bos_token to True
gguf: Setting add_eos_token to False
[  1/291] Writing tensor token_embd.weight                      | size  32000 x   4096  | type F16  | T+   1
[  2/291] Writing tensor blk.0.attn_norm.weight                 | size   4096           | type F32  | T+   1
[  3/291] Writing tensor blk.0.ffn_down.weight                  | size   4096 x  14336  | type F16  | T+   1
[  4/291] Writing tensor blk.0.ffn_gate.weight                  | size  14336 x   4096  | type F16  | T+   1
[  5/291] Writing tensor blk.0.ffn_up.weight                    | size  14336 x   4096  | type F16  | T+   1
[  6/291] Writing tensor blk.0.ffn_norm.weight                  | size   4096           | type F32  | T+   1
...
[290/291] Writing tensor blk.31.attn_v.weight                   | size   1024 x   4096  | type F16  | T+  16
[291/291] Writing tensor output_norm.weight                     | size   4096           | type F32  | T+  16
Wrote model_q4_k_m_gguf-unsloth.F16.gguf
Unsloth: Conversion completed! Output location: [./model_q4_k_m_gguf-unsloth.F16.gguf](/mnt/samssd/developments/genai-playground/language/05-fine-tuning/unsloth/model_q4_k_m_gguf-unsloth.F16.gguf)
Unsloth: [2] Converting GGUF 16bit into q4_k_m. This will take 20 minutes...
/bin/sh: 1: [./llama.cpp/quantize](/mnt/samssd/developments/genai-playground/language/05-fine-tuning/unsloth/llama.cpp/quantize): not found
Unsloth: Conversion completed! Output location: [./model_q4_k_m_gguf-unsloth.Q4_K_M.gguf](/mnt/samssd/developments/genai-playground/language/05-fine-tuning/unsloth/model_q4_k_m_gguf-unsloth.Q4_K_M.gguf)
/home/ubuntu/.conda/envs/genaiplayground/lib/python3.9/subprocess.py:946: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stderr = io.open(errread, 'rb', bufsize)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)

@corticalstack Ye so the first step is to save it as a float16 file which in fact will be 15GB unfortunately. The 2nd step is to use llama.cpp to save the float16 Pytorch file as a F16.GGUF file. The 3rd step which seems to be failing is the quantize step - to be honest I'm not sure why ur directory does not have quantize. One way is to compile llama.cpp urself using make after cloning git clone llama.cpp then see if the quantize file exists.
Unfortunately I'm nto sure if this is an Unsloth issue or not - on Colab it seems to work perfectly, but in this case, the quantize file does not exist - im stumped myself :(

@danielhanchen following your suggestion, I cloned llama.cpp. Before anything else, verified that quantize does NOT exist. Then executed make, where upon completion quantize DOES exist. Do you do a llama.cpp make in unsloth? Would unsloth replace any existing llama.cpp folder that already exists? Thanks

@corticalstack If you place llama.cpp in the same folder as ur save folder - I will first do a check if llama.cpp exists - if it does - I will skip git cloning and skip make. So it should work now if you run save_pretrained_gguf - again sorry for the inconvenience!
Ie: if not os.path.exists("llama.cpp")

@danielhanchen that worked, whoop!
if True: model.push_to_hub_gguf("CorticalStack/travel-mistral-7B-GGUF", tokenizer, quantization_method = "q4_k_m", token = HF_TOKEN)
successfully quants then pushes to HF hub. However, it did not create a config.json, such as:
{
    "model_type": "mistral"
}

Should unsloth push_to_hub_gguf do this, or do I need to additionally do an extra step manually like:
model.config.to_json_file("config.json")
And have to push this config to HF myself. Or..?
Thanks for all your efforts.

@corticalstack Oh wait does GGUF need a config.json file? Are you running this say on Ooba? If so, delete all arguments in the Colab notebook for Ooba, and just put the model path

@corticalstack Oh wait does GGUF need a config.json file? Are you running this say on Ooba? If so, delete all arguments in the Colab notebook for Ooba, and just put the model path

Hey. I can only say that for example all of TheBloke's GGUF's have a config.json, and believe if you try to load in a GGUF into HF transformers without a config.json, you'll get an error. Would suggest you try with standard HF save and push_to_hub to check generation of config.json. Thanks

@corticalstack Oh ok ok I will get back to you!

@corticalstack Sorry on the delay!! Just pushed a commit to add in a config.json file :) https://huggingface.co/danielhanchen/quantized_trial2/blob/main/config.json for example. I just copied https://huggingface.co/TheBloke/CapybaraHermes-2.5-Mistral-7B-GGUF/blob/main/config.json's example :)

Awesome @danielhanchen , thanks!


Can you include the Python package noise?

Can you include the Python package noise, so that it can be installed with rosdep or specified in the package.xml as e.g. a build dependency like <build_depend>python-noise</build_depend>?

It is possible to do so. Please open a pull request to propose adding them.
Guidelines for contributing can be found here: https://github.com/ros/rosdistro/blob/master/CONTRIBUTING.md


Document custom node exporter labels in grafana example

It looks like the sample dashboard uses metrics from the prometheus node exporter, like node_memory_MemTotal, that include the cluster label: https://github.com/justwatchcom/elasticsearch_exporter/blob/master/examples/grafana/dashboard.json#L156. This label isn't included in the node exporter by default, so I'm guessing you're adding custom labels in your scrape_configs. It would be useful to add a note describing this requirement and showing examples of how to add the custom labels, since several panels in the example dashboard won't work otherwise.

Hi Joshua,
thanks for reporting the issue. I'll have a look what custom labels we are using. Regarding the metrics from node_exporter: we probably don't need to used them as the elasticsearch_exporter exposes OS metrics from the node endpoint itself.

The cluster label is indeed coming from custom tags and relabeling rules. We may want to add a general example how to do this.


Add assertDefined

please ignore the name of this branch

Btw this may be confusing because there are other falsey values. So maybe assertNotNull be better

"Non-defined" does not imply falsy though. Although, we could consider naming it assertNonNullable? That might be clearer. If so, we should rename isDefined to isNonNullable too.

Closing for lack of activity.
https://github.com/sindresorhus/ts-extras/issues/43


Message when receiving a pet

Could the ‘you have a funny feeling you’re being followed’ here be put in bold please i didnt even notice til days later
Also it doesn’t say Beaver in the loot received

Fixed both issues


GitLab support info missing at lfx easycla board

Steps :

PR is gated
Click on Not covered button
3.. Sign up ICLA , See- PR is covered
Now click on Covered icon

Actual results : GitLab & Gerrit information available at lfx easycla board but GitLab info is missing

Need to update the landing page text to include GitLab.

Created PR: https://github.com/communitybridge/easycla/pull/3324

Deployed to DEV:

@thakurveerendras - ready for QA

GitLab information added at easyCla contributor landing page on dev site, So making issue status QA-Passed


Android large notification icon

Readme mentioned use of large icon in data messages, but this functionality seemed to be unimplemented. Added this functionality (works the same way as small icon) and updated the readme file.

Thanks for the contribution.
However the large icon functionality for Android is already implemented and working.
You can verify this by building and running the example project app and sending an FCM message such as android_notification.json.
The large icon file is referenced by naming convention as you'll see if you look in one of the DPI resource directories in the example project.
For example, if you set "icon": "coffee" in the FCM message, then coffee.png will be used for the small icon and coffee_large.png used for the large icon.
This naming convention is outlined in the current documentation.
Thanks again and sorry to close this PR without merging it.


Separate Qt 5 packages from dependent libraries

Motivation for this change
The qt5 package set contained packages that are part of Qt 5, and packages which only depend on Qt 5. This is inappropriate for several reasons, foremost that it may lead to confusion with users.
The documentation for creating Qt and KDE packages was also out-of-date.
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip" N/A: only documentation packages changed
[x] Tested execution of all binary files (usually in ./result/bin/) N/A: only documentation packages changed
[x] Fits CONTRIBUTING.md.

ATTN @gebner @romildo I had to make substantial changes to your packages to fix evaluation errors. Please do not import Qt 5-based package sets, but import individual packages instead. Please make sure you are using wrapQtProgram as necessary.

With the conflicts, this would be best merged alongside another branch I have running, so I'm closing this one.


Update gradle and java versions to meet with latests IDE requrements

I updated gradle version to 8.0 and java version to meet with latest Android Studio requirements.

It looks like you forgot to include most of the files.

It looks like you forgot to include most of the files.

Yes, you are right. Please check pushed files.
Also please note I have updated target sdk to the 33. Now it is mandatory requirement for app to be published over Google Play. I know you not going to publish this sample app, but it is good to confirm chaquopy meets with this version as well.

It has the same issues like https://github.com/chaquo/chaquopy-console/pull/9 PR, but I believe as soon as it passes test coverage it is fine to merge. In case of this app launch over emulator should be fine. (passed API 28 and API 33)

See https://github.com/chaquo/chaquopy-console/pull/9 for why I reverted some files.
Thanks for the contribution!


wasabibackend: 1.1.12 -> <IP_ADDRESS>, use buildDotnetModule

Motivation for this change
#146257
This does seem to crash when launching the executable, though that happens on master as well.
~/nix/nixpkgs > ./result/bin/WasabiBackend
2021-12-31 01:44:00 INFO        InitConfigStartupTask (35)      Wasabi Backend started (38c871a8-8a55-4722-b340-92da8fce08bd).
2021-12-31 01:44:00 INFO        InitConfigStartupTask (42)      Config is successfully initialized.
2021-12-31 01:44:01 INFO        InitConfigStartupTask (47)      RoundConfig is successfully initialized.
2021-12-31 01:44:01 CRITICAL    Program (37)    System.Net.Http.HttpRequestException: Connection refused
 ---> System.Net.Sockets.SocketException (111): Connection refused
   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at NBitcoin.RPC.RPCClient.SendCommandAsyncCore(RPCRequest request, Boolean throwIfRPCError)
   at NBitcoin.RPC.RPCClient.SendCommandAsync(RPCRequest request, Boolean throwIfRPCError)
   at NBitcoin.RPC.RPCClient.GetBlockchainInfoAsync()
   at WalletWasabi.BitcoinCore.RpcClientBase.GetBlockchainInfoAsync()
   at WalletWasabi.Backend.Global.AssertRpcNodeFullyInitializedAsync()
   at WalletWasabi.Backend.Global.InitializeAsync(Config config, CoordinatorRoundConfig roundConfig, IRPCClient rpc, CancellationToken cancel)
   at WalletWasabi.Backend.InitConfigStartupTask.ExecuteAsync(CancellationToken cancellationToken)
   at WalletWasabi.Backend.Extensions.RunWithTasksAsync(IHost host, CancellationToken cancellationToken)
   at WalletWasabi.Backend.Program.Main(String[] args)

You can now fetch the nuget dependencies using nix-build -A wasabibackend.passthru.fetch-deps.
cc @mmahut @prusnak @Stunkymonkey
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, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build wasabibackend

Thanks for the review :)


Web console: add a nice UI for overlord dynamic configs and improve the docs

Add a nice form (with JSON fallback) to the overlord dynamic config dialog

To do this I had to read the docs and found them lacking. I asked @kfaraz to help me make heads and tails of the logic. Here was his summary that I rewrote in the docs.
Here are his original notes (screenshot form Slack DM):

If there are better way to word it I am all ears.

Tried out the new console changes, they are very easy to use now!
Encountered a minor bug. The content in the suggestion box seems to overflow in some cases.


spring-boot error with connection in appConfigurator AzUre

i have this  issue:
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'initConnectionString' defined in class path resource [com/microsoft/azure/spring/cloud/config/A
ppConfigurationBootstrapConfiguration.class]: Unsatisfied dependency expressed through method 'initConnectionString' parameter 0; nested exception is org.springframework.beans.factory.BeanCrea
tionException: Error creating bean with name 'spring.cloud.azure.appconfiguration-com.microsoft.azure.spring.cloud.config.AppConfigurationProperties': Invocation of init method failed; nested
exception is java.lang.IllegalArgumentException: At least one config store has to be configured.
but in my bootstrap.properties my connection endPoint is = spring.cloud.azure.appconfiguration.stores[0].connection-string=Endpoint=https:------------'
and my pom is this:
`

org.springframework.boot
spring-boot-starter-parent
2.2.4.RELEASE

4.0.0
<artifactId>azure-appconfiguration-sample</artifactId>
<name>Spring Cloud Azure App Configuration Sample</name>
<dependencies>
    <dependency>
        <groupId>com.microsoft.azure</groupId>
        <artifactId>spring-cloud-azure-appconfiguration-config</artifactId>
        <version>1.2.2</version>
    </dependency>
</dependencies>

`

@dqvoleto11 Thank you for your feedback! Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team.

Just checking in. Could you please provide the relevant documentation so we can route this question appropriately?

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


feat: handle debug mode

gravitee-io/issues#5803

Closing in favour of https://github.com/gravitee-io/gravitee-api-management/pull/24


Add System Design Questions to Readme

The readme does not contain a system design section for system design questions. This needs to be included in the readme

Hey @tobySolutions ,
Thanks for your suggestions. If you want, you can add some System Design Interview Questions.


Sometimes Flux does not reconciliate - how to debug?

Thanks for your great template - I got a machine up and running in less than 10 minutes.
Having used ArgoCD for several years, It is the first time using flux. Often when I push changes within kubernetes/apps the flux/helm receive the webhook, and explicitly log that no differences are found.
When I run task cluster:reconciliate the changes

sometimes get applied
sometimes don't get applied

In cases they are not getting applied, I am trying to follow https://github.com/onedr0p/flux-cluster-template#-debugging and check the output of flux-system/helm-controller and flux-system/source-controller.
Sometimes there is a hint in the logs - often there isn't.
ArgoCD gives me proper Error Messages on Sync (errors in YAML Files, Connection errors, and so on) - but with Flux I am sometimes stuck without any information.
I am not sure if this is me being too inexperienced with flux, or if you have any hints on this specific setup on how to debug these cases any further - I'd be glad about any hint in the right direction :)

I would say that if the changes aren't getting applied it could be due to GitHub having issues or that you pushed invalid kubernetes configuration that flux cannot reconcile. The debugging link you sent is a great start and next time the changes don't get applied it would be great to share more info regarding the cluster state and in cluster flux resources if possible. Basically dumping the output of those commands in the debugging section here would be pretty helpful in finding what's wrong.


Sentinel Comics RPG

Changes / Comments
Changed "currenthp" & "greenmax" to "health" & "health_max" to allow for healthbars on tokens.
A version update script is included to preserve the old values.

Hi @the-Dissilent there seems to be a conflict in this sheet. Please resolve it when you are able

@Reonin I'm not sure why it was showing both the old and new versions of the sheet, but it's updated now.


Please consider using fetch instead of XMLHttpRequest

All modern browsers support fetch, and using XMLHttpRequest is no longer necessary. This will also make the tools compatible with the edge environments (e.g., Cloudflare Workers).

hmmm, we only use fetch where do you see XMLHttpRequest  being used?
We use cross-fetch for node backwards compatibility. Is that maybe an issue? 🤔

Fixed in https://github.com/getAlby/alby-tools/pull/32
Thanks @fishcakeday !


#187 & #193: Prevent repeated action executions

Resolves:

https://github.com/agiledivider/vagrant-hostsupdater/issues/187
https://github.com/agiledivider/vagrant-hostsupdater/issues/193

For those who interested in applying the fix without waiting for the new release:
cd ~/.vagrant.d/gems/<VERSION>/gems/vagrant-hostsupdater-1.2.1
curl -sSL https://github.com/agiledivider/vagrant-hostsupdater/pull/197.patch -o 197.patch
patch -p1 < 197.patch

I appreciate it much!
Thank you.

Tested on Windows 10 and Linux/Ubuntu OS, works great!
Thank you very much!

Hi @BR0kEN-
Would you consider asking @cgsmith if you could take this project over?

@siliconmeadow I am not the owner of the repo. You'll need to fork it and build it out from their.

Ping @agiledivider

@BR0kEN- good luck with that. He hasn't been involved in the project for a while. I suggest forking and starting a different one.


[AutoPR] search/resource-manager

Created to accumulate context: search/resource-manager

Closing PRs that are older than 1 month.


Contract refactor

Rather than using useContractLoader twice, we now connect the signer onto the contract when passing it into the FunctionForm component.
Also linting fixes.

This might warrant a comment in the code explaining why we do this but I'll leave that up to you.


Link to Zen/Kata from coderdojo.com

Getting to these pages needs to be simple and straightforward to new participants, either directly from the main page or from a dojo's page (using 'Find a dojo').

@dmwelch there is a wireframe and design for a whole new navigation bar which will be in progress as soon as we have more development resources. There will be a lot more direct links to Zen and a more obvious link to Kata in the new navbar :)


Update Composer dependencies (2024-12-13-00-11)

Visual regression test passed!
View the visual regression test report


Allow role being run in check mode

By default, the "Get systemd version" would not run in check mode and thus the variable prometheus_systemd_version would not be set meaning that subsequent tasks that depend on that variable would fail with an error similar to the following:
TASK [cloudalchemy.prometheus : create systemd service unit] ********************************************************************************
fatal: [xxxxx]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'stdout'"}

With this change, the read-only task in question ("Get systemd version") is run even in check mode.

prometheus_systemd_version is needed in systemd service template so lack of this variable will probably cause an error in "create systemd service unit", even when running in check mode.

Exactly, and that is the issue that my suggested change fixes although the check_mode property is a little confusing; I'm quoting the docs here:

Prior to version 2.2 only the equivalent of check_mode: no existed. The notation for that was always_run: yes.

So, with check_mode: false, the task will always run, thus populating the prometheus_systemd_version variable, even in check mode.

In that case this is great! :+1:
Please rebase and I'll merge it.

I have rebased my branch on your master. There are still some tests failing, but they seem unrelated to my change. Anyway, let me know if there's anything else you need me to do. Thanks!

Yeah, those are requests to GitHub API, which are rate limited. Everything looks fine :+1:


Migrate to popper.js v.2

Hi! Are you planning to upgrade popper.js to version 2 and migrate?

sry, dublicate https://github.com/Akryum/v-tooltip/issues/498


Progress bar exceeding container's width

At least in conjunction with the Fedmine plugin (https://github.com/Froiden/fedmine), in the projects list view, the progress bar displayed was exceeding the width of each project's box, hence overlapping between projects.
To fix it, I tried editing lib/progressive/projects_helper_patch.rb and replacing the width, which was being set in two different places, from 30em to 100%. That seems to have fixed it, though I haven't tested it too much.
BTW, nice plugin, thank you!

@jmfarina thanks for interest to the plugin.
This plugin works utilizes pieces of the original Redmine code to render progressbard. It works well with build in themes and several custom themes. So, probably it would be better if you cross-post this issue to https://github.com/Froiden/fedmine repository.


xr.full_like (often) fails when other is chunked and fill_value is non-scalar

I've been running into some issues when using xr.full_like, when my other.data is a chunked dask array, and the fill_value is a numpy array.
Now, I just checked, full_like mentions only scalar in the signature. However, this is a very convenient way to get all the coordinates and dimensions attached to an array like this, so it feels like desirable functionality. And as I mention below, both numpy and dask function similary, taking much more than just scalars.
https://xarray.pydata.org/en/stable/generated/xarray.full_like.html
MCVE Code Sample
x = [1, 2, 3, 4]
y = [1, 2, 3]
da1 = xr.DataArray(dask.array.ones((3, 4), chunks=(1, 4)), {"y": y, "x": x}, ("y", "x"))
da2 = xr.full_like(da1, np.ones((3, 4)))
print(da2.values)

This results in an error:
ValueError: could not broadcast input array from shape (1,3) into shape (1,4)
Expected Output
Expected is a DataArray with the dimensions and coords of other, and the numpy array of fill_value as its data.
Problem Description
The issue lies here: https://github.com/pydata/xarray/blob/2c77eb531b6689f9f1d2adbde0d8bf852f1f7362/xarray/core/common.py#L1420-L1436
Calling dask.array.full with the given number of chunks results in it trying to to apply the fill_value for every individual chunk.
As one would expect, if I set fill_value to the size of a single chunk it doesn't error:
da2 = xr.full_like(da1, np.ones((1, 4)))
print(da2.values)

It does fail on a similarly chunked dask array (since it's applying it for every chunk):
da2 = xr.full_like(da1, dask.array.ones((3, 4)))
print(da2.values)

The most obvious solution would be to force it down the np.full_like route, since all the values already exist in memory anyway. So maybe another type check does the trick. However, full() accepts quite a variety of arguments for the fill value (scalars, numpy arrays, lists, tuples, ranges). The dask docs mention only a scalar in the signature for dask.array.full:
https://docs.dask.org/en/latest/array-api.html#dask.array.full
As does numpy.full:
https://docs.scipy.org/doc/numpy/reference/generated/numpy.full.html
However, in all cases, they still broadcast automatically...
a = np.full((2, 2), [1, 2]
>>> array([[1, 2],
       [1, 2]])

So kind of undefined behavior of a blocked full?
Versions
Output of `xr.show_versions()`
INSTALLED VERSIONS
------------------
commit: None
python: 3.7.6 | packaged by conda-forge | (default, Jan  7 2020, 21:48:41) [MSC v.1916 64 bit (AMD64)]
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
byteorder: little
LC_ALL: None
LANG: en
LOCALE: None.None
libhdf5: 1.10.5
libnetcdf: 4.7.3
xarray: 0.15.1
pandas: 0.25.3
numpy: 1.17.5
scipy: 1.3.1
netCDF4: 1.5.3
pydap: None
h5netcdf: None
h5py: 2.10.0
Nio: None
zarr: 2.4.0
cftime: <IP_ADDRESS>
nc_time_axis: None
PseudoNetCDF: None
rasterio: 1.1.2
cfgrib: None
iris: None
bottleneck: 1.3.2
dask: 2.9.2
distributed: 2.10.0
matplotlib: 3.1.2
cartopy: None
seaborn: 0.10.0
numbagg: None
setuptools: 46.1.3.post20200325
pip: 20.0.2
conda: None
pytest: 5.3.4
IPython: 7.13.0
sphinx: 2.3.1

da2 = da1.copy(data=np.ones((3,4))) should be what you want.
We should raise an error when the input to full_like is not scalar


chore(deps): update dependency maven-wrapper to v3.2.0

This PR contains the following updates:

Package
Update
Change

maven-wrapper
minor
3.1.0 -> 3.2.0

Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend
Frontend
Oracle-API
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Cherry picked in likely corequisite from https://github.com/bcgov/nr-spar/pull/26.


Remove line renderer from the touch pointer

Per customer feedback in #5420, there is minimal value for having the touch pointer render the pointing ray, it will always be under the user's fingertip.
This change removes line rendering related scripts from the touch pointer prefab and brings it in line with similar pointers (ex: mouse,)

/azp run


Module Not Found: "process/browser" Error in React Integration with @fileforge/pdfreader

I am experiencing an issue while integrating @fileforge/pdfreader into my React project. After following the documentation and installing the package, I encountered a Webpack compilation error related to the missing process/browser module.
Error Details:
The following error occurs during the build process:

Additionally, I tried adding a polyfill for process in my Webpack configuration, but the error persists. The issue seems to be related to how the module is handled within @fileforge/pdfreader.
Steps to Reproduce:

Install @fileforge/pdfreader in a React project.
Attempt to import and use the component in the project.
Run the build using Webpack (or a React build tool like Create React App).

Expected Behavior:
The package should work without requiring a manual polyfill for Node.js modules like process.
Actual Behavior:
The build fails with the error above.
Environment:

OS: macOS
Node.js version: v16.x
Webpack version: 5.x
React version: 17.x / 18.x
@fileforge/pdfreader version: x.x.x

Attempts to Resolve:
I attempted to resolve the issue by:

Installing the process polyfill.
Modifying the Webpack configuration to include process/browser.
Ensuring that the paths are correctly set in the module resolution.

Despite these attempts, the error persists, suggesting a deeper issue with how @fileforge/pdfreader handles dependencies.
Request:
Could you provide guidance on how to resolve this error, or update the package to avoid requiring manual Node.js polyfills when used in a browser environment like React? If possible, an example of proper integration would also be very helpful.
Thank you for your time and assistance.

Hey @ANYURU, thanks for the detailed walkthrough!
Vite should handle bundling this gracefully, not sure why there are issues with Webpack specifically. It is likely being introduced by pdfjs-dist, but I can't really confirm at the moment.
Contributions regarding this are welcome!


fix(Examples): MSDK-1192: Fix Leading Spaces issue in the Flash CLI example

Fixed the leading spaces issue in the Flash CLI (1st issue in the ticket).
Removed magic numbers and included relevant ASCII equivalent with Macros.
Included few more check to avoid unwanted echo statements (2nd issue in the ticket).

Corresponding Jira ticket is here
Note: - Line 236 (index != 0) in the updated code would resolve the second issue in the ticket.

Looks good. Minor change request below. Do you also want to filter out arrow keys in this PR?

Yes. I want to filter out the arrow keys in this PR.
 I am testing the code thoroughly and will push the changes ASAP.


feat: mock/feeds deploy

Can we live up a vercel that works with mock/feeds

closed by @ssibrahimbas


I Broke the Compiler Again

Need to rename but honestly not sure what happened here, was greeted with the lovely
--> :0:1
 |
0 |
 | ^ Internal compiler error: Attempted to construct return path error but no source span was found.
Please file an issue on the repository and include the code that triggered this error.
 |
  Aborting due to 1 error.
Error: "Failed to compile BentoBox"

Sway file I was running was this main.sw
contract;

// Needed for Hash Mappings
use std::chain::*;
use std::hash::*;
use std::storage::*;

/* --------------- Rebase Handling --------------- */

pub struct Rebase {
    elastic:u64,
    base:u64,
}

fn to_base(total:Rebase, elastic:u64, roundUp:bool) -> u64 {
    let mut base:u64 = 0;

    if(total.elastic == 0){
        base = elastic;
    } else {
        base = (elastic * total.base) / total.elastic;
        if (roundUp && (base * total.elastic) / total.base < elastic) {
            base = base + 1;
        };
    };

    base
}

fn to_elastic(total:Rebase, base:u64, roundUp:bool) -> u64 {
    let mut elastic:u64 = 0;

    if(total.elastic == 0){
        elastic = base;
    } else {
        elastic = (base * total.elastic) / total.base;

        if (roundUp && (elastic * total.base) / total.elastic < base) {
            elastic = elastic + 1;
        };
    };

    elastic
}

fn add(total:Rebase, elastic:u64, base:u64) -> Rebase {
    total.elastic = total.elastic + elastic;
    total.base = total.base + base;

    total
}

fn sub(total:Rebase, elastic:u64, base:u64) -> Rebase {
    total.elastic = total.elastic - elastic;
    total.base = total.base - base;

    total
}

/* ---------------- Important to note that these methods are different than Boring Solidity ----------- */
// Storage is iffy so this just returns a new rebase every time, Functional Programming remains supreme

fn add_elastic(total:Rebase, elastic:u64) -> Rebase {
    total.elastic = total.elastic + elastic;

    total
}

fn sub_elastic(total:Rebase, elastic:u64) -> Rebase {
    total.elastic = total.elastic - elastic;

    total
}

/* ---------------- Mapping Functions ----------------------- */

pub trait PairMapping {
	fn store(self, key1:b256, key2: b256, value:u64);
	fn retrieve(self, key1:b256, key2: b256) -> u64;
}

pub trait BalanceMapping {
	fn store_bal(self, key1:b256, value:Rebase);
	fn retrieve_bal(self, key1:b256) -> Rebase;
}

// Key (b256, b256) which is address -> (address -> u64)

pub struct BytesMapping{
	map_id : b256
}

impl PairMapping for BytesMapping {
    fn store(self, key1:b256, key2: b256, value:u64) {
        let storage_slot = hash_pair(key1, key2, HashMethod::Sha256);

        store(storage_slot, value);

    }

    fn retrieve(self, key1: b256, key2: b256) -> u64 {
        let storage_slot = hash_pair(key1, key2, HashMethod::Sha256);

        let resultingValue = get::<u64>(storage_slot);

        resultingValue
    }
}

impl BalanceMapping for BytesMapping {

    fn store_bal(self, key1:b256, value:Rebase) {
        let storage_slot = hash_pair(key1, self.map_id, HashMethod::Sha256);
        // Cursed way to store a struct, I am converting the storage slot to a uint
        // incrementing it, then casting back to a byte array
        let mut slotNumber:b256 = storage_slot;
        let mut storage_slot2:b256 = 0x0000000000000000000000000000000000000000000000000000000000000000;
        let shiftvalue:u64 = 1;
        storage_slot2 = asm(s1: slotNumber,s2:storage_slot2, s3:shiftvalue) {
            sll s2 s1 s3;

            s2:b256
        };

        store(storage_slot, value.elastic);
        store(storage_slot2, value.base);

    }

    fn retrieve_bal(self, key1:b256) -> Rebase {
        let storage_slot = hash_pair(key1, self.map_id, HashMethod::Sha256);
        // Cursed way to store a struct, I am converting the storage slot to a uint
        // incrementing it, then casting back to a byte array
        let mut slotNumber:b256 = storage_slot;
        let mut storage_slot2:b256 = 0x0000000000000000000000000000000000000000000000000000000000000000;
        let shiftvalue:u64 = 1;
        storage_slot2 = asm(s1: slotNumber,s2:storage_slot2, s3:shiftvalue) {
            sll s2 s1 s3;

            s2:b256
        };

        let resultingElastic = get::<u64>(storage_slot);
        let resultingBase = get::<u64>(storage_slot2);

        let resultingValue:Rebase = Rebase{
            elastic: resultingElastic,
            base: resultingBase,
        };

        resultingValue
    }
}

pub struct DepositInput {
    input_token:b256,
    from:b256,
    to:b256,
}

abi map_test {
    fn depsoit(gas: u64, coins: u64, asset_id: b256, input: DepositInput) -> u64;

}

impl map_test for Contract {

    fn depsoit(gas: u64, coins: u64, asset_id: b256, input: DepositInput) -> u64 {

    }

}

Forc.toml
[project]
name = "BentoBox"
author = "ControlCplusControlV"
entry = "main.sw"
license = "Apache-2.0"

[dependencies]
core = { git = "http://github.com/FuelLabs/sway-lib-core" }
std = { git = "http://github.com/FuelLabs/sway-lib-std" }

Cargo.toml
[package]
name = "BentoBox"
version = "0.1.0"
authors = ["ControlCplusControlV"]
edition = "2021"
license = "Apache-2.0"

[dependencies]
fuels-abigen-macro = "0.1"
fuels-core = "0.2"
fuels-rs = "0.2"
fuel-gql-client = { version = "0.2", default-features = false }
fuel-tx = "0.2"
rand = "0.8"
tokio = { version = "1.12", features = ["rt", "macros"] }

[[test]]
name = "integration_tests"
path = "tests/harness.rs"
harness = true

All warnings were
  Compiled library "core".
  Compiled library "core".
warning
 --> FuelLabs-sway-lib-std-15bed83/src/result.sw:0:5
  |
...
3 |     Ok: T,
  |     -- Enum variant Ok is never constructed.
  |
warning
 --> FuelLabs-sway-lib-std-15bed83/src/result.sw:0:5
  |
...
4 |     Err: E,
  |     --- Enum variant Err is never constructed.
  |
  Compiled library "lib-std" with 2 warnings.
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
14 | fn to_base(total:Rebase, elastic:u64, roundUp:bool) -> u64 {
15 |     let mut base:u64 = 0;
   |     --------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 |   contract;
 1 |
 2 |   // Needed for Hash Mappings
 3 |   use std::chain::*;
...
16 |
17 |       if(total.elastic == 0){
   |  _____-
...  |
24 | |     };
   | |______- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
17 |     if(total.elastic == 0){
18 |         base = elastic;
   |         --------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
19 |     } else {
20 |         base = (elastic * total.base) / total.elastic;
   |         ---------------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 |   contract;
 1 |
 2 |   // Needed for Hash Mappings
 3 |   use std::chain::*;
...
20 |           base = (elastic * total.base) / total.elastic;
21 |           if (roundUp && (base * total.elastic) / total.base < elastic) {
   |  _________-
22 | |             base = base + 1;
23 | |         };
   | |__________- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:13
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
21 |         if (roundUp && (base * total.elastic) / total.base < elastic) {
22 |             base = base + 1;
   |             ---------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
25 |
26 |     base
   |     ---- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
30 | fn to_elastic(total:Rebase, base:u64, roundUp:bool) -> u64 {
31 |     let mut elastic:u64 = 0;
   |     ------------------------ This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 |   contract;
 1 |
 2 |   // Needed for Hash Mappings
 3 |   use std::chain::*;
...
32 |
33 |       if(total.elastic == 0){
   |  _____-
...  |
41 | |     };
   | |______- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
33 |     if(total.elastic == 0){
34 |         elastic = base;
   |         --------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
35 |     } else {
36 |         elastic = (base * total.elastic) / total.base;
   |         ---------------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:9
   |
 0 |   contract;
 1 |
 2 |   // Needed for Hash Mappings
 3 |   use std::chain::*;
...
37 |
38 |           if (roundUp && (elastic * total.base) / total.elastic < base) {
   |  _________-
39 | |             elastic = elastic + 1;
40 | |         };
   | |__________- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:13
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
38 |         if (roundUp && (elastic * total.base) / total.elastic < base) {
39 |             elastic = elastic + 1;
   |             ---------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
42 |
43 |     elastic
   |     ------- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
46 | fn add(total:Rebase, elastic:u64, base:u64) -> Rebase {
47 |     total.elastic = total.elastic + elastic;
   |     ---------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
47 |     total.elastic = total.elastic + elastic;
48 |     total.base = total.base + base;
   |     ------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
49 |
50 |     total
   |     ----- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
53 | fn sub(total:Rebase, elastic:u64, base:u64) -> Rebase {
54 |     total.elastic = total.elastic - elastic;
   |     ---------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
54 |     total.elastic = total.elastic - elastic;
55 |     total.base = total.base - base;
   |     ------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
56 |
57 |     total
   |     ----- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
63 | fn add_elastic(total:Rebase, elastic:u64) -> Rebase {
64 |     total.elastic = total.elastic + elastic;
   |     ---------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
65 |
66 |     total
   |     ----- This code is unreachable.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
69 | fn sub_elastic(total:Rebase, elastic:u64) -> Rebase {
70 |     total.elastic = total.elastic - elastic;
   |     ---------------------------------------- This declaration is never used.
   |
warning
  --> Sushi-Sway/src/main.sw:5:5
   |
 0 | contract;
 1 |
 2 | // Needed for Hash Mappings
 3 | use std::chain::*;
...
71 |
72 |     total
   |     ----- This code is unreachable.
   |

here

@ControlCplusControlV when I try to compile your code now with master, I get the following error:
thread 'main' panicked at 'assertion failed: total_lines_in_input > total_lines_of_highlight', forc/src/utils/helpers.rs:312:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This is still bad, but the cause of this is that the implementation of depsoit (😆) is expecting a return value. If I change it to return anything, the code compiles without any issues.

@mohammadfawaz That panic is specifically caused by an error with an invalid Span.

Yeah this error is easy to avoid if you write valid code, and I've been able to move past it. But wasn't checking my spelling and ran into it so figured it was worth posting it so compiler panics properly


Remove own default_uncaught_exception_handler

we have OCaml 4.12 now, so Printexc provides it

This PR does not affect the produced WebAssembly code.

Does this change the error output in any way?

Does this change the error output in any way?

No. But I so far haven't figured out how to get backtraces, so that's a point that remains to be clarified.

so far haven't figured out how to get backtraces

I think you need OCAMLRUNPARAM=b before running.
LGTM but if this changes the output it would be good to show before and after in the commit message.

The function replacing ours is  https://github.com/ocaml/ocaml/pull/9263/files#diff-5fa438e4a308c8dfd6c75768649ae4fe17b72159d89f5ae3e7319c8eeaf2b790R273 and looks exactly the same.


Refactoring

For globals, use *mut HashMap instead of Option<HashMap> -> bare Mutex works

hide .html test files


Not all collisions with enemies cause damage to the player

Was able to recreate this bug many times. When the player collides with several enemies in rapid succession, only the first collision causes damage to the player even though all the enemies disappear. In the video, you can see I had 2 hearts when I collided with 3 enemies. My player only took 1 heart of damage even though I collided with 3 enemies.
https://user-images.githubusercontent.com/70303464/231343192-e2f36456-58ad-4c6a-be7f-5035b4b6a1df.mp4

Intended - you can see that the player flashes a bit after being hit to signal a small grace period.  This prevents the player from being one-shot by a pile of enemies.