bug: revalidatePath() not working in tRPC procedure

Provide environment information
 System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 5600H with Radeon Graphics
    Memory: 1.70 GB / 7.86 GB
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.14.0 - ~\AppData\Local\pnpm\pnpm.CMD

Describe the bug
revalidatePath() in tRPC procedure is not revalidating the database query in server component
import Footer from '@/components/global/footer';
import Header from '@/components/global/header';
import { SubjectsLoader, UserSubjects } from '@/components/pages/dashboard';
import { NewSubjectDrawer } from '@/components/pages/dashboard/client';
import { auth } from '@clerk/nextjs';
import { Metadata } from 'next';
import { redirect } from 'next/navigation';
import { Fragment, Suspense } from 'react';

export const metadata: Metadata = {
	title: 'Dashboard',
};

export default function page() {
	const session = auth();

	if (!session.userId) return redirect('/auth/sign-in');

	return (
		<Fragment>

Your subjects

							<Suspense fallback={<SubjectsLoader />}>
								<UserSubjects session={session} />
							</Suspense>

					<NewSubjectDrawer />

		</Fragment>
	);
}

export const dynamic = 'force-dynamic';

export async function UserSubjects({ session }: { session: SignedInAuthObject }) {
	const userSubjects = await getUrls(session.userId);

	// when there are no user's subjects
	if (userSubjects.length === 0) return
- No Subjects -
;

	return (
		<Fragment>
			{userSubjects.map((val) => (
				<SubjectCard key={val.id} {...val} />
			))}
		</Fragment>
	);
}

when I add a new subject using the client side tRPC api and calling the revalidatePath() in tRPC procedure to fetch the updated subjects from db. But the subjects are not re-fetched.
Reproduction repo
https://github.com/imopbuilder/attendance-app
To reproduce
pnpm i

 cp .env.example .env.development.local

I won't be using any package for env-variables but they are type-safe using zod.
after loading the env-variables run the scripts
pnpm db:push

pnpm dev

head to htts://localhost:3000 and after sign-in to the app, navigate to htts://localhost:3000/dashboard and create a new subject by clicking on the button at bottom-right corner. Fill the form and click on create subject button the subject is being created but not re-fetched using the revalidatePath('/dashboard', 'page') in tRPC procedure
Additional information
I will be using clerk for auth and supabase - postgresql  as database with drizzle-orm

@juliusmarminge sure

@imopbuilder were you able to solve it?

@Alekzv9 No I am using server actions for that


Bind to B

Yes

This will bind to be when the scheduler is falling, not sure if this will cause some form of double unschedule error.


[Callout] website docs: component

Acceptance criteria
Add callout as a variant to the Notification component. Highlighted in the list below and the place you will need to add content for static notification.
Some additional tasks have been added to improve the notification usage docs in general. This will help with understanding these component variants and better align with our content template. If you see other places to enhance the understanding of these docs and still align to our content template then feel free to add them in.
Related PR for this effort #15532
Deliverables

[x] Content draft: Write a first draft of the content required below. It can be written either in boxnote first or Figma (Jeannie has kindly made an editable version of the docs here.) This draft is mostly focused on the written content. Images are not required yet. Once you have a first draft, please share it with the team in slack for review.
[x] Draft with images: Once you have edit to your written copy ready mock the page up in Figma  (if you haven't done so yet). This draft should include images. Share with the team in a meeting when ready for a review.
[x] Pull request: Open a PR to submit the content for a final review before publishing.

Usage tab
Overview section

[x] Add a paragraph under overview introducing notifications. You can reference the notification pattern for content if needed. You can also rewrite the When to use section if needed.
[x] Add Callout to the variants table

Formatting section
### Anatomy

[x] Add Callout to the existing image. Place below inline so its easy to compare
[x] Add any annotations needed to the anatomy list. For example, define that close does not apply to callout.

### Status

[x] Create new H3section for notification status. Migrate the content from the notification pattern notification status section. It will live in both places. Content can be edited if need but should be the same on both pages.

Callout section
This is a new section and where the bulk of the documentation work will be. Determine where to add the static variant amongst the other 3 variant sections (Inline, Toast, Actionable)
## Callout

[x] Write an introduction section that explains what a static notification is and how its different than the other components (focus especially on explaining how it is different than inline). Include examples for when to use this variant and how it addresses the use case / solves a problem for the user.

### Callout formatting

[x] Create a image with micro layouts showing where Callout commonly goes, refer to inline for an example.

#### Sizing

[x] List out any component sizes that are available and provide some guidance about how to choose the best size for the use case. Other topics that may be covered here include considerations around maximum heights, maximum widths, and responsive resizing.

#### Placement

[x] Discuss placement of the component in a broader context, that is: alongside other components, within the grid, etc.

### Behaviors

[x] Add any additional behaviors or features of static notification here. The other component types have Dismissal here, is a relevant topic here as well. You can change the heading title to be more relevant to the content if needed.

Style tab
Structure section

[x] Add a H3 sections for Callout. Copy the inline notification and modify it to callout specifications

Accessibility tab
Out of scope. This tab has not been updated to the new accessibility template yet. We will make a separate issue for this work.

Past questions and answers on this topic:
Variants

It is possible to treat this as its own variant.

Close icon

There will never be a  close icon included in this.

Placement

This can be used as a banner for a more global level of a page, or can be inline with other sections on a page.
This does not relate to toasts and can not be a toast.

Experimental status

The plan is to move this to stable once it is revised in experimental.

PR for notification usage & style document to include guidance for Callout has been pushed. Changes required to be made on the notification pattern page has been moved to a different issue as discussed.

Re-opening the issue as the PR is in review and not merged.


Unable To Use "Stoplight Elements" In React Vite App - require is not defined

Hi Team,
we're using <API/> react component from @stoplight/elements in our Vite/React project.
But the app doesn't work in production - it fails with Uncaught ReferenceError: require is not defined error.
Sample: https://github.com/aerialist7/stoplight-elements-sample/tree/vite-react-component
To reproduce the issue just run preview command in my sample.
Could you please help us to fix it?
relates #2084
cc @lottamus

Hello!
Our team recently took over the stewardship of the elements repo.
Due the volume of un-triaged issues that are pretty old and the time it would take us to get caught up on all of them, we kindly ask that you open up a new ticket if this is still an issue you're struggling with.
If you open a new issue please include:

clear steps to reproduce that include example OAS specs, application setup, code, etc.
the error or issue you are experiencing
the expected behavior

We will be triaging any new tickets in a timely manner.
Thank you for understanding!


helm install failed if k8s doesn't have metrics api implementation

Output of helm version:
version.BuildInfo{Version:"v3.0.0-beta.3", GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a", GitTreeState:"clean", GoVersion:"go1.12.9"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Error: could not get apiVersions from Kubernetes: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
helm.go:81: [debug] unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
could not get apiVersions from Kubernetes
helm.sh/helm/pkg/action.(*Configuration).getCapabilities
/go/src/helm.sh/helm/pkg/action/action.go:100
helm.sh/helm/pkg/action.(*Install).Run
/go/src/helm.sh/helm/pkg/action/install.go:185
main.runInstall
/go/src/helm.sh/helm/cmd/helm/install.go:219
main.newInstallCmd.func1
/go/src/helm.sh/helm/cmd/helm/install.go:109
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).execute
/go/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:762
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).ExecuteC
/go/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:850
helm.sh/helm/vendor/github.com/spf13/cobra.(*Command).Execute
/go/src/helm.sh/helm/vendor/github.com/spf13/cobra/command.go:800
main.main
/go/src/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
/usr/local/go/src/runtime/proc.go:200
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1337

Actually, I was installing stable/prometheus-adapter with helm3 to give k8s a metrics api implementation.

I fixed those issues on my cluster by running this:
( GKE 1.14.3-gke.11 )
kubectl create clusterrolebinding cluster-admin-binding \
    --clusterrole cluster-admin \
    --user "$(gcloud config get-value account)"
kubectl create -f https://raw.githubusercontent.com/GoogleCloudPlatform/k8s-stackdriver/master/custom-metrics-stackdriver-adapter/deploy/production/adapter.yaml

duplicate of https://github.com/helm/helm/issues/6361.


Release/v0.4.0

Contains the following PRs:
https://github.com/decentdao/decent-interface/pull/2635
https://github.com/decentdao/decent-interface/pull/2615
https://github.com/decentdao/decent-interface/pull/2641
https://github.com/decentdao/decent-interface/pull/2639
https://github.com/decentdao/decent-interface/pull/2643
https://github.com/decentdao/decent-interface/pull/2642

I wanted to test each PR, but was unable to do so because the PRs do not contain enough context to be easily testable.
For each PR, included should be clear directions on how to test the PR prior to approval. No one should approve a PR without testing it.
For each PR, please add testing instructions so I can test them each and approve this prod push 🫡  I am on standby to do this any time.

@parkermccurley which PRs specifically do you need testing instructions for?

@parkermccurley by 'test' each PR, you are saying you want to test what these PRs fix right? not that you are testing WITHIN those PRs (as in the PR's deploy preview)?
For testing. I guess the only one that isn't going to be clear is #2615, This is more or less a technical update and nothing to test for that PR

Yep @trainface I actually mean each one... since we don't have unit test coverage and it isn't clear to me in each of these PRs what parts of the app they touch, how am I supposed to make sure the PR was implemented successfully? Including some basic instructions (a user story to run through) on PRs for reviewers should be default
@Da-Colon I'm referring to testing in the deploy previews where UI tests are necessary, yes

@parkermccurley All the individual changes are within this deploy-preview, I'd test them all here versus jumping around.
As far as changes in that PR, these are ALL related to DAOs loading and unloading when the DAO is switched.

@Da-Colon yep I'm also happy to test here on this deploy-preview, just think it will be easier (for developers) moving forward if PR authors add testing instructions in the PRs themselves instead of waiting until this point
Thanks for adding the links, your PRs generally have a good amount of context (screenshots for example) but even these PRs: #2638 #2641 for example I'm not sure where in the application I should be testing if this bug has been removed. PRs should include that context for a reviewer to be able to drop in and test the functionality...
This is like the tip of the iceberg in terms of testing, and its still very possible we merge things to prod that have unwanted side effects and introduce bugs we will not catch, but at a minimum I think a reviewer needs to go to deploy-preview and see for themselves that the intended outcome is there, and I'm happy to be the person to do that when we go to prod but need more context to be an effective tester

@adamgall @Da-Colon maybe I just need to go back to basics here. How do you guys suggest I test this merge to prod, to make sure all of the changes you've made are functional on dev?

@parkermccurley a couple of these PRs are color updates and icon updates. they either already include screenshots (https://github.com/decentdao/decent-interface/pull/2643) or include links to slack messages that include screenshots (https://github.com/decentdao/decent-interface/pull/2635). it feels like a waste of developer time to include further testing instructions in those. i understand that in the future we should be more consistent with testing instructions, but for these PRs i'm going to say no, please click through the links to gain needed context.

I agree thanks @adamgall. For future PRs please make sure the team knows to include testing instructions (if it can be tested in the UI).
That leaves:
#2615 - @Da-Colon just checking again 'cause its a big ol' PR, are there any parts of the application that may have been made fragile by these updates that are worth kicking the tires on?
#2639 - @Da-Colon I'm just not sure how to test it
#2642 - @Da-Colon also not sure how to test it
cc @johnqh

updated the PR description of #2615 to include the test cases. @parkermccurley

"For future PRs please make sure the team knows to include testing instructions"

@parkermccurley if by this you mean the instructions should be in the PR description, I'm gonna have to push back. That's what the linked Linear issue is there for -- ALL the context one would need, which ideally would cover even more than just the one small "happy" path to reproduce the bug esp if there's been discussion in there.
If the linked issue doesn't have enough to reliably reproduce the issue then the failure is on the issue description, not the PR description. I see the PR description as dev facing with comments that code reviewers would/should be interested in. In the same vein, if a dev wants to UI/UX test a PR, then they should also go look at the Linear issue.
If there's no linked issue . . . well. There should have been. I think we'd better solidify the habit of creating issues for EVERYTHING we push a fix/update for, even if it seems trivial. cc @decentdao/engineering

Thanks @Da-Colon! Approving this.

If the linked issue doesn't have enough to reliably reproduce the issue then the failure is on the issue description, not the PR description. I see the PR description as dev facing with comments that code reviewers would/should be interested in. In the same vein, if a dev wants to UI/UX test a PR, then they should also go look at the Linear issue.
If there's no linked issue . . . well. There should have been. I think we'd better solidify the habit of creating issues for EVERYTHING we push a fix/update for, even if it seems trivial. cc @decentdao/engineering

@DarksightKellar I hear you, this makes sense to me. On teams I've worked on in the past, testing instructions were included in Jira issues for PRs in BitBucket, so that is aligned with my experience.
I'm not going to be reviewing code and offering useful input there. For me it is important that before we push to prod I'm confident what we are launching (and what I will be promoting to our users) meets our standards via hands on UI testing. I find this especially important in the absence of test coverage in the code base.
So if I wanted to do this for this push, I'd need to:

Go into every PR
Gather context for what the PR does (remember, I'm not contributing to the codebase - I lack so much context therefore what may seem simple and clear to someone working on this codebase daily, is not simple or clear to me)
Click into the Linear issue
Understand how to test the issue
Go to deploy preview and test it

What I'd really like to see on a prod push is:

Plain english: X was changed in our codebase, and Y should be the result
So I can just get on app.dev and mess around with it before we push to prod.

What's the best way to make that UX for me as a reviewer? Would it be creating a linear ticket that includes all that information for each prod push?


text2image的预训练模型，没有找到啊

hi, I don't find the "pai-painter-commercial-base-zh" or "pai/pai-painter-base-zh" or "alibaba-pai/pai-painter-large-zh" for text2image pretrained model weight

would you give a simple instruction on this @ttliu-kiwi

alibaba-pai/pai-painter-large-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-large-zh.tgz
alibaba-pai/pai-painter-base-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-base-zh.tgz
pai-painter-commercial-base-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-commercial-base-zh.tgz

hi, I don't find the "pai-painter-commercial-base-zh" or "pai/pai-painter-base-zh" or "alibaba-pai/pai-painter-large-zh" for text2image pretrained model weight
alibaba-pai/pai-painter-large-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-large-zh.tgz
alibaba-pai/pai-painter-base-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-base-zh.tgz
pai-painter-commercial-base-zh:
wget https://atp-modelzoo-sh.oss-cn-shanghai.aliyuncs.com/release/easynlp_modelzoo/alibaba-pai/pai-painter-commercial-base-zh.tgz


v-calendar from vuetify

Hi @ClickerMonkey
Do you have any timelines or roadmap of when v-calendar from vuetify will be used for this library?
thx,
Ivan.

+1

I wish I did, I hoped vuetify 2.0 would have the changes I made to v-calendar that updates to this library are depending on but it looks like John Lieder didn't want the changes because of how it affected their test coverage (I believe).
If you want to ask the vuetify team, feel free to post questions here:
https://github.com/vuetifyjs/vuetify/pull/6475

https://github.com/vuetifyjs/vuetify/issues/6307
As the pr is closed, shall we stick at this issue?

Vuetify 2.0.0 beta 5 is released!!!

Any update about this?... Vuetify 2.0.x version is released and I see the events were added

I won't be able to update this library until I have the bandwidth or incentive - Using the vuetify library is a big change and much will be disrupted.


How do I update ?

Hi, I'm running version 1.017 and realised that you already launch v1.018, how can I update ? reinstall this way :
docker pull qjake/hacc
docker run -p 8095:8095 qjake/hacc
??
thank you for your great work
(sorry, this seems not to be right topic, but can't find one)

Hi @jruibarroso Yes, you should be able to stop your container (docker stop <container-id>), and then re-run docker pull qjake/hacc which will pull the latest version, and then re-run the container.

How can I know my container ID ?
Jake Burgy<EMAIL_ADDRESS>escreveu em sáb, 11/04/2020 às 16:56 :

Hi @jruibarroso https://github.com/jruibarroso Yes, you should be able
to stop your container (docker stop ), and then re-run docker
pull qjake/hacc which will pull the latest version, and then re-run the
container.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qJake/HADotNet.CommandCenter/issues/92#issuecomment-612452413,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDQIBN5IRT6CTALRS6HDSDRMCHLRANCNFSM4MF7BUJA
.

--
Enviado pelo meu iPhone Xs

You can run docker ps to see running containers.

Thank you, already updated 😃
Jake Burgy<EMAIL_ADDRESS>escreveu em sáb, 11/04/2020 às 20:39 :

You can run docker ps to see running containers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qJake/HADotNet.CommandCenter/issues/92#issuecomment-612498721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDQIBMNUKG4YIYCUIDJJUTRMDBPDANCNFSM4MF7BUJA
.

--
Enviado pelo meu iPhone Xs


Other python project with name Chirp already registered as package

🐛 Summary
Other Chirp project for Python already exists and it's registered as Python package.
To reproduce
Open PyPi package https://pypi.org/project/chirp/
Expected behavior
I would expect that if project has unique name.

This program is written in python but has no intention of being used as a python package or being uploaded to PYPI, the CISA Hunt and Incident Response Program also as no overlap in its capabilities. There should be no need to rename the program.


Fix istioctl analyze discovery flag to be true boolean

Fixes https://github.com/istio/istio/issues/18718

@sushicw: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-e2e-envoyv2-v1alpha3_istio
5b8ff5605c052deb432f160625dd332144bf0584
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

/retest

In response to a cherrypick label: #18861 failed to apply on top of branch "release-1.4":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	istioctl/cmd/analyze.go
Falling back to patching base and 3-way merge...
Auto-merging istioctl/cmd/analyze.go
CONFLICT (content): Merge conflict in istioctl/cmd/analyze.go
Patch failed at 0001 Fix istioctl analyze discovery flag to be true boolean


Implement the components and styles for the new header bar

Implement the components and styles for the new header bar
Set default component styles for MUI Theme and created button variants for the Logo and MenuItem styles.
Used the SVG component for the branch logo image.

@neutralino1 Thanks for catching those issues. Please take another look. (Screen recording is updated)

Had another iteration to change from using buttons to links.
The latest state is deployed to
https://story.dev-usw2-sematic0.sematic.cloud/?path=/story/sematic-header--header
for preview


Expose cloudflare_record as data source

Current Terraform version
0.13.5
Description
Expose cloudflare_record as a data source.
Use-cases
I am working on a piece of infrastructure that shares DNS zone with a larger infra. The DNS table contains, among other records, an SPF TXT record.
My piece of infra, all described in terraform, needs to have its own value added to this pre-existing SPF TXT record. Ideally, I'd like to be able to read existing SPF TXT record, push my value to the list of mechanisms, then update the DNS record.
Potential Terraform configuration
data "cloudflare_record" "spf" {
  filter {
    name        = "mydomain.com"
    lookup_type = "contains"
    match       = "^v=spf1"
  }
}

resource "cloudflare_record" "spf" {
  name    = "mydomain.com"
  value   = custom_put(data.cloudflare_record.spf.0.value, var.extra_value)
  type    = "TXT"
  ttl     = 1
  proxied = false
}

(I am using to custom_put function here for brevity; it's actual implementation is out of scope of current request)
References
...
Community note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Being able to lookup a record isn't really usable by ID and may introduce a circular dependency. Generally, to use data sources like this there is some sort of filtering mechanism (name, type, etc) which returns an enumerable set to reference.
If you already have these records in Terraform, is there a reason why this couldn't be an attribute on the resource you intend to use in other resources?

Being able to lookup a record isn't really usable by ID and may introduce a circular dependency. Generally, to use data sources like this there is some sort of filtering mechanism (name, type, etc) which returns an enumerable set to reference.

@jacobbednarz That's a valid point. I've updated the "Potential Terraform configuration" to use filtering instead of a static ID. Thanks!

If you already have these records in Terraform

To clarify, I do not have the larger infra, and the DNS records in particular, written down as Terraform configs. The project I am working on is a set o TF configs isolated from the rest of infra (which remains to be managed manually). My project needs to register itself on the DNS table that belongs to a larger infra.

is there a reason why this couldn't be an attribute on the resource you intend to use in other resources?

I've never used data attributes, and I am not sure I am following the question. Can you clarify, possibly with example, what data attribute is used for, and how it could be applied for the case described above?
What I am trying to do, is to go from this:
v=spf1 include:abc.com -all

To this:
v=spf1 include:abc.com include:xyz.com -all

Without the need of copy-pasting existing SPF value in it's entirety to my TF values.

Resource attributes are properties of a resource which are exported and available for reference in other resources. You can check out the full documentation at https://www.terraform.io/docs/configuration/expressions.html#references-to-resource-attributes. There is an example on the documentation page, however the gist is this.
resource "cloudflare_record" "mail_server" {
  name    = "mail.example.com"
  value   = "<IP_ADDRESS>"
  type    = "MX"
  ttl     = 60
  proxied = "false"
}

resource "cloudflare_record" "spf" {
  name    = "@"
  type    = "TXT"
  value  = "v=spf1 include:abc.com include:${cloudflare_record.mail_server.value} -all"
  ttl     = 60
  proxied = "false"
}

In the above, we are creating two cloudflare_record resources, the latter references the value from the former in its own value. This does require the Terraform resources to be accessible to one another though.
As for your example Terraform configuration, let's stick to what is available through the API to avoid filtering on the client end. This would boil down to things like name, content, type and proxied to be filters without any regexes.

Closing this due to lack of information and going stale. Happy to revisit should we wish to continue this conversation with another use case.


ERROR: IOError: Cannot open or read /home/chef-repo/cookbooks/iptables/metadata.rb!

When running:
knife cookbook site install application_ruby
I get:
Pristine copy branch (chef-vendor-iptables) exists, switching to it.
Downloading iptables from the cookbooks site at version 0.14.1 to /home/confucius/chef-repo/cookbooks/iptables.tar.gz
Cookbook saved: /home/confucius/chef-repo/cookbooks/iptables.tar.gz
Removing pre-existing version.
Uncompressing iptables version 0.14.1.
removing downloaded tarball
No changes made to iptables
Checking out the master branch.
ERROR: IOError: Cannot open or read /home/chef-repo/cookbooks/iptables/metadata.rb!
there is a metadata.json file but no metadata.rb file.  When I try and add the metadata.rb from github and re-run install the iptable folder is overwritten and the metadata.rb file is deleted.

Not an issue with this cookbook.


Updates welcome message

Description of changes
Proposed updates to Slackbot welcome message
Issue Resolved
No existing issue

@ksmacleod99 - Once PR https://github.com/OperationCode/operationcode_bot/pull/86 is merged, and you rebase on master, you should no longer have failing tests.

It seems like some commits in this PR (f280b70 thru c87a6b3) are duplicates of commits that are already in master. Seems like this somehow happened during rebase?

I have no idea. How can I clean this up and get it to work properly?

@ksmacleod99
Ideally, a PR should be as lean as possible, and only contain the changes you're proposing to merge in.  It's not the biggest deal in the world, but the duplicate commits contain the same changes that other people have already added (just with new commit hashes), which could be confusing for someone else trying to read thru the commit history in a linear fashion and figure out what happened, when, and why.
So, your branch (ksmacleod99:master) really only needs to contain the commits 0152753(Updates welcome message) and3e4207a` (Delete .DS_Store) that you actually added. Somehow during your rebase/merge/force-push, those other commits (f280b70 thru c87a6b3) got caught in there.
No worries tho! Luckily, you can easily use Git's interactive rebase feature to clean up your commit history that you are proposing to merge in w/ this PR.  I would be happy to walk you through the process.

@jjhampton Yes, that would be great! I have no idea how I did that (but I also had no idea how to rebase, so that might be the problem). I need to call it an evening; but when would be a good time for you?


EsCTC error on seg_ctc_ent_log_fb.py

Sometimes this error happens beacuse of an empty tensor
m_ctc_for_seg_ctc.py", line 138, in log_sum_exp_axis
_max = T.max(a, dim=dim)[0]
RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity

I solved the issue by adding the following lines  to check if tensor is empty
`token_equals = T.nonzero(T.eq(token[:, :-1], token[:, 1:]))#batch, U-1
#print("Token {} len  {}".format(token_equals,len(token_equals.size())))
dim1, dim2 = token_equals.shape

condition = (dim1 != 0) and (dim2 != 0)

if (len(token_equals.size()) == 2) and ( condition ):
    te_b = token_equals[:, 0]
    te_u = token_equals[:, 1]
    have_equal = True
else:
    have_equal = False`


AutoValue_DbRow cannot be resolved

AutoValue_DbRow cannot be resolved

glad to read that it wasn't a code error :)
Thank you for using this project
F.


count() and lean() support

Hello,
I have this kind of query:
(note it's with co and generators)
var item = yield Model
    .findOne({ id: id })
    .sort({ createdAt: -1 })
    .lean()

or
... setup params
  var result = yield {
    count: Model.find(findParams).count(),
    items: Model.find(findParams).sort(sort).limit(limit).skip(limit * page).lean()
  }

I am a bit new to testing mongoose this way, but currently I have count is not a function or
...lean is not a function.

As far i know, sinon does not support generators. However, you can try with [this fork][https://github.com/ingameio/SinonES6.JS] of sinon.
Tell me if it works, so can close this issue :)

The issue is not the generator, I mentioned it because I did not want to rewrite my snippet.
I don't have time to make a test case right now, but if you don't have time I'll do it later. :)
If you do have time, can you add lean and count in your tests and see if they work or fail?

Done! I added two tests (for lean and count methods). Tell me if I'm missing something.

@gaguirre Thank you ! I was able to make it run. So, lean and count were working actually. (But it is still good to include them in the tests :P)
But, I am in some "edge case" maybe although I have seen more people doing the same.
Here is what confused me, but makes sense somehow:
In our API endpoint, we have a Model.find query. But, we use it twice:

once to get the items
once to count how many there are. (so we can paginate)

It looks like this: (we use Koa with generators)
  // setting all the sort, limit, findParams before
  ...
  var q = yield {
    count: Model.find(findParams).count(),
    items: Model.find(findParams).sort(sort).limit(limit).skip(limit * page).lean()
  }

For my test to pass I had to include both "find":
ModelMock
  .expects('find').withArgs({ account: testAccount._id })
  .chain('count')
  .resolves(10)

ModelMock
  .expects('find').withArgs({ account: testAccount._id })
  .chain('sort', '-lastOccurrence')
  .chain('limit', 50)
  .chain('skip', 0)
  .chain('lean')
  .resolves([])

yield request(server.listen())
  .get('/account/' + testAccount.id + '/trace')
  .set('Authorization', 'Bearer ' + user.getToken())
  .expect(200)
  .end()

ModelMock.verify()

The thing is, at first I only tested the "search for items" part, without the "count" part. This would throw an error. It works only if I add both.
The error output is not clear because it does display something like:
 GET /endpoint
{ [ExpectationError: Unexpected call: find({ account: 565754c49b4fe1f405750dc0 })
    Expectation met: find({ account: 565754c49b4fe1f405750dc0 }[, ...]) once] name: 'ExpectationError' }
ExpectationError: Unexpected call: find({ account: 565754c49b4fe1f405750dc0 })
    Expectation met: find({ account: 565754c49b4fe1f405750dc0 }[, ...])
...
super
long
stacktrace
...

So it is confusing to see the expected call with the right parameters displayed, but failing.
It makes sense that in such case one query is solved but not the other. But to be honest it feels magical as how does sinon-mongoose does verify and expects both requests in this manner.

Good to hear you solved it!
You're right it's confusing in some way, but the behavior is similiar to others on sinon.
For example, on parameters expectation.
If you have this code
Model.find({ name: 'Joe' }).exec()

This two expectations will be ok, despite the second didn't check the parameters
sinon.mock(Model)
  .expects('find')
  .withArgs({ name: 'Joe' })
  .chain('exec')

sinon.mock(Model)
  .expects('find')
  .chain('exec')

However, I'm gonna think if there is a way to check chained methods more strictly ;)

I am closing the issue. Thank you for your time, and your module : )


feat: add react 18 support to connect-react

Description
Add react 18 support to connect-react, I tested it on a new next.js app using react 18 and didn't face any issue.
Closes https://github.com/hirosystems/connect/issues/213
Type of Change

[ ] New feature
[ ] Bug fix
[ ] API reference/documentation update
[x] Other

Checklist

[ ] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[ ] yarn lerna run test passes
[ ] Changelog is updated
[ ] Tag 1 of @hstove or @kyranjamie or @aulneau for review

closed via https://github.com/hirosystems/connect/pull/222


NewNotificationChannel property diff for each run

Describe what happened
We create a webhook channel with a property info containing a payload, values etc. However after the initial deployment, subsequent pulumi up's show a terraform specific property popping up, which is not needed I guess. Perhaps the underlying terraform code is appending these fields.
Sample program
notificationChannel, err := newrelic.NewNotificationChannel(ctx, channelName, &newrelic.NotificationChannelArgs{
	AccountId:     pulumi.String(accountId),
	Name:          pulumi.String(channelName),
	Type:          pulumi.String("WEBHOOK"),
	DestinationId: pulumi.String(destinationId),
	Product:       pulumi.String("IINT"),
	Properties: newrelic.NotificationChannelPropertyArray{
		&newrelic.NotificationChannelPropertyArgs{
			Key:   pulumi.String("payload"),
			Value: pulumi.String(string(payload)),
		},
	},
})

pulumi diff (fields are masked)
      ~ properties: [
          ~ [0]: {
                  + __defaults  : []
                  - displayValue: ""
                  ~ key         : "source" => "payload"
                  - label       : "terraform-source-internal"
                  ~ value       :
                      - terraform
                      + xxxxxxxx
          - [1]: {
                  - displayValue: ""
                  - key         : "payload"
                  - label       : ""
                  - value       : xxxxxxxx

Log output
No response
Affected Resource(s)
No response
Output of pulumi about
some fields are masked
CLI
Version      3.131.0
Go Version   go1.23.0
Go Compiler  gc

Plugins
KIND      NAME        VERSION
resource  archive     0.0.6
resource  aws         6.29.0
resource  aws-native  0.13.0
resource  cloudflare  5.16.0
resource  cloudflare  3.5.0
resource  command     0.11.1
resource  fastly      8.4.1
language  go          unknown
resource  kubernetes  4.9.1
resource  newrelic    5.31.0
resource  random      4.2.0
resource  tailscale   0.13.3

Host
OS       darwin
Version  14.6.1
Arch     arm64

This project is written in go: executable='/opt/homebrew/bin/go' version='go version go1.22.2 darwin/arm64'

Current Stack: xxxxxxxxxxx

TYPE                       URN
pulumi:pulumi:Stack        urn:pulumi:newrelic::xxxxxxxx::pulumi:pulumi:Stack::xxxxxxxx-newrelic
pulumi:providers:newrelic  urn:pulumi:newrelic::xxxxxxxx::pulumi:providers:newrelic::default_5_31_0
pulumi:providers:newrelic  urn:pulumi:newrelic::xxxxxxxx::pulumi:providers:newrelic::default_5_17_0

Found no pending operations associated with newrelic

Backend
Name           work.local
URL            s3://xxxxxxxx
User           raywonkari
Organizations
Token type     personal

Dependencies:
NAME                                        VERSION
github.com/aws/aws-sdk-go-v2                v1.21.2
github.com/aws/aws-sdk-go-v2/config         v1.15.15
github.com/aws/aws-sdk-go-v2/service/ecs    v1.9.0
github.com/pulumi/pulumi-aws-native/sdk     v0.13.0
github.com/pulumi/pulumi-random/sdk/v4      v4.2.0
github.com/pulumi/pulumi/sdk/v3             v3.129.0
github.com/stretchr/testify                 v1.9.0
github.com/aws/aws-sdk-go                   v1.44.298
github.com/chartmogul/chartmogul-go/v3      v3.1.1
github.com/docker/docker                    v24.0.7+incompatible
github.com/go-git/go-git/v5                 v5.12.0
github.com/opencontainers/image-spec        v1.0.2
github.com/pulumi/pulumi-archive/sdk        v0.0.6
github.com/pulumi/pulumi-aws/sdk/v6         v6.29.0
github.com/pulumi/pulumi-cloudflare/sdk/v5  v5.16.0
github.com/pulumi/pulumi-command/sdk        v0.11.1
github.com/pulumi/pulumi-fastly/sdk/v8      v8.4.1
github.com/pulumi/pulumi-kubernetes/sdk/v4  v4.9.1
github.com/pulumi/pulumi-newrelic/sdk/v5    v5.31.0
github.com/pulumi/pulumi-tailscale/sdk      v0.13.3
github.com/tdewolff/minify/v2               v2.20.16
github.com/pulumi/pulumi-cloudflare/sdk/v3  v3.5.0

Pulumi locates its logs in /var/folders/m_/y8fbgmsd693cgpl3lh22hqth0000gn/T/ by default

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

hi again @raywonkari - I'm going to need a little help with a reproduction, as I'm not as familiar with the ins and outs of New Relic.
Specifically, can you provide us with a complete program that reproduces this issue you're seeing? This would help us address and root cause much more quickly.

@guineveresaenger I was able to reproduce with this program:
package main

import (
	"github.com/pulumi/pulumi-newrelic/sdk/v5/go/newrelic"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() { pulumi.Run(Main) }

func Main(ctx *pulumi.Context) error {
	d, err := newrelic.NewNotificationDestination(ctx, "d", &newrelic.NotificationDestinationArgs{
		Properties: &newrelic.NotificationDestinationPropertyArray{},
		Type:       pulumi.String("WEBHOOK"),
	})
	if err != nil {
		return err
	}
	_, err = newrelic.NewNotificationChannel(ctx, "example", &newrelic.NotificationChannelArgs{
		Name:          pulumi.String("example"),
		Type:          pulumi.String("WEBHOOK"),
		DestinationId: d.ID(),
		Product:       pulumi.String("IINT"),
		Properties: newrelic.NotificationChannelPropertyArray{
			&newrelic.NotificationChannelPropertyArgs{
				Key:   pulumi.String("payload"),
				Value: pulumi.String("my-payload"),
			},
		},
	})
	return err
}

I see a perma-diff for both the notification destination and the notification channel.

I have reproduced the above code in HCL and tested against the upstream TF provider. There is no perma-diff, indicating a bridge bug.
terraform {
  required_providers {
    newrelic = {
      source = "newrelic/newrelic"
    }
  }
}

resource "newrelic_notification_destination" "example" {
  name = "example"
  property {
    key   = "my-key"
    value = "my-value"
  }
  type = "WEBHOOK"
}

resource "newrelic_notification_channel" "example" {
  name           = "example"
  type           = "WEBHOOK"
  destination_id = newrelic_notification_destination.example.id
  product        = "IINT"
  property {
    key   = "payload"
    value = "my-payload"
  }
}

Thank you for narrowing it down 🙏 Does the perma-diff in TF exist under -refrsh=false? Second question, on the Pulumi side, how does PlanResourceChange influence the result? Much appreciated.

Thank you for narrowing it down 🙏 Does the perma-diff in TF exist under -refrsh=false?

No. TF does not have the perma-diff regardless of refresh.

Second question, on the Pulumi side, how does PlanResourceChange influence the result? Much appreciated.

We don't have PRC turned on in this provider (CC @VenelinMartinov, I thought we had this rolled out to all providers).
PRC fixes the problem. Thanks for the suggestion.


General cleanup

Use gofumpt to format Go sources
Use prettier to format TypeScript sources
Use prettier to format YAML configurations
Refactor Docker Compose configuration to have software versions to
have its software versions read in from .env (which it automatically
recognizes and uses)
Add .envrc (direnv) config that points to the Docker Compose file in
order to avoid using -f docker/docker-compose.yml with every Docker
Compose Command
Add pinned Go version to .tool-versions (ASDF)
Pin Node.js to latest LTS rather than just latest
Refactor Magefile a bit

Going to do a quick self-review and leave some more clarifying comments before un-drafting.


Source control workflow

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

C,
On Mon, Jan 29, 2024, 5:14 AM jaja samuel @.***> wrote:

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Web-Dev-For-Beginners/issues/1253, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQQCC6U7YLEJW6Y4BYJSZM3YQ3PFRAVCNFSM6AAAAABCORGO5GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDINBQGI4TSOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


errors

Traceback (most recent call last):
File "test.py", line 21, in
from SimpleCV import Camera
File "C:\Python27\lib\site-packages\SimpleCV_init_.py", line 3, in
from SimpleCV.base import *

File "C:\Python27\lib\site-packages\SimpleCV\base.py", line 59, in
raise ImportError("Cannot load OpenCV library which is required by SimpleCV"
)
ImportError: Cannot load OpenCV library which is required by SimpleCV

Do you have OpenCV?

I do have it, I installed it via pip install OpenCV .  Blow are the steps I did.
pip install opencv-python
pip install SimpleCV
python -m pip install --user numpy scipy matplotlib ipython jupyter pandas sympy nose pygame


Store query age and discard old ones. Repack query segments each frame

Status: Ready to merge
This attempt 2 of PR i created yesterday #574
This solves problem #523 where queries not working when vsync disabled, which was due to FixedUpdate being called infrequently and query guids were being lost.
This change makes queries persistent, so that it doesnt matter if FixedUpdate is missed for a few frames, but if a query gets too old it is automatically discarded. This is achieved by storing a frame number with the query segment information.
Importantly this PR also recomputes query data segment indices each frame. This effectively compactifies the data every frame, instead of accumulating air bubbles in the data that would waste compute processing.
This should fix the problem, and also not require changes to the API and increased complexity for calling code that #574 added.
@skaughtx0r FYI

I have to disable the higher end of the spectrum. I think you are aware of this with surface velocities issue

Could you speak more to this?

I'll merge for now, let me know about other issue

Could you speak more to this?

Sure. I will see if I can isolate and open an issue.


UIkit enabling dual stream undefined

" UIkit enabling dual stream undefined " , I am getting this while running  the same code explained in this link -https://github.com/AgoraIO-Community/ReactNative-UIKit#readme. Can any one help me on understanding what else I am missing

Dual stream is an optional feature which is disabled by default, the log is safe to ignore. Are you facing any issues?


Add alias rule for webui.fcgi

The general /cgi-bin/ alias in the apache config colides with the default config
Alternative - use another prefix (e.g. openxpki-cgi)

Meanwhile solved by alias mechanism and localconfig.yaml


[vcpkg-tools] update meson to 0.58.2

Library name: meson
New version number: 0.58.2
Other information that may be useful (release notes, etc...)
https://github.com/mesonbuild/meson/releases/latest

@xavier2k6 ,I duplicated this issue to issue #19568,let's update vcpkg-tools together in issue #19568,I temporarily close this issue


Build chef-server on ARM

Following the merge of https://github.com/chef/omnibus-software/pull/751, this PR use the new jre-from-jdk software for opscode-solr4, allowing to build chef-server package for armhf, as demonstrated here: https://github.com/elthariel/chef-server/releases/tag/v12.5.0-arm-alpha
I've been running the chef server on a very small box (Scaleway.com C1 instance: 2GB RAM, Marvell Armada 370/XP CPU) for a few weeks, and it works well. For later reference, here's my /etc/opscode/chef-server.rb file:
# This line is *required*, without it, the keygen timeouts and starts new 'openssl genrsa' processes
# Completely slamming the box, preventin `reconfigure` from ever succeeding
opscode_erchef['keygen_timeout'] = 30000
# Tweak to your tastes
opscode_expander['nodes'] = 3
opscode_erchef['keygen_cache_workers'] = 1
# There's only 2GB of memory on my box, let's be conservative here
opscode_solr4['heap_size'] = 256
postgresql['shared_buffers'] = '256MB'
postgresql['shmall'] = 2097152
postgresql['shmmax'] =<PHONE_NUMBER>

Signed-off-by: Julien 'Lta' BALLET<EMAIL_ADDRESS>

By the way, this build is likely to work OOB on Raspberry Pi, but I havent' access to any right now to test

If you do try to get this going on a Raspberry Pi, you may want to generate the certs and dhparam before hand and feed them in using these config items:
https://github.com/chef/chef-server/blob/master/omnibus/files/private-chef-cookbooks/private-chef/attributes/default.rb#L477-L479
Otherwise the reconfigure might take forever.

I confirm, it does take forever.

Restarting the travis build. It fails in seemingly unrelated places, are some of the tests brittle ?

@elthariel We've been seeing some issues with Travis with respect to installing the version of ruby some of the tests require.  If they fail again I'll try to restart the individual tests.  This PR should't influence any of the Travis tests at all.  I'll put this branch through our internal build system which runs the build and a set of end-to-end tests on all supported platforms.  Once it passes there, I think we are good to go.

@stevendanna, thanks for the update, I hope the tests will pass but there isn't any reasons for them not to pass. Also I closed/reopened the PR to restart the build and it passed, as you can see.


Catppuccin Rainbow preset

I made a new preset called Catppuccin Rainbow, based on Gruvbox Rainbow:

Requirements:

Starship 1.20 and above as it uses the prev_bg and prev_fg specifiers.
NerdFont font

Definition as follows:
"$schema" = 'https://starship.rs/config-schema.json'

format = """
[](color_surface0)\
$os\
[](fg:prev_fg bg:color_maroon)\
$username\
$hostname\
[](fg:prev_bg bg:color_yellow)\
$directory\
[](fg:prev_bg bg:color_teal)\
$git_branch\
$git_commit\
$git_status\
[](fg:prev_bg bg:color_blue)\
$c\
$rust\
$golang\
$nodejs\
$php\
$java\
$kotlin\
$haskell\
$python\
[](fg:prev_bg bg:color_mauve)\
$docker_context\
$conda\
$jobs\
[](fg:prev_bg bg:color_surface0)\
$time\
$cmd_duration\
$memory_usage\
[ ](fg:prev_bg)\
$line_break$character"""

palette = 'catppuccin_mocha'

[palettes.catppuccin_latte]
color_rosewater = "#dc8a78"
color_flamingo = "#dd7878"
color_pink = "#ea76cb"
color_mauve = "#8839ef"
color_red = "#d20f39"
color_maroon = "#e64553"
color_peach = "#fe640b"
color_yellow = "#df8e1d"
color_green = "#40a02b"
color_teal = "#179299"
color_sky = "#04a5e5"
color_sapphire = "#209fb5"
color_blue = "#1e66f5"
color_lavender = "#7287fd"
color_text = "#4c4f69"
color_subtext1 = "#5c5f77"
color_subtext0 = "#6c6f85"
color_overlay2 = "#7c7f93"
color_overlay1 = "#8c8fa1"
color_overlay0 = "#9ca0b0"
color_surface2 = "#acb0be"
color_surface1 = "#bcc0cc"
color_surface0 = "#ccd0da"
color_base = "#eff1f5"
color_mantle = "#e6e9ef"
color_crust = "#dce0e8"

[palettes.catppuccin_frappe]
color_rosewater = "#f2d5cf"
color_flamingo = "#eebebe"
color_pink = "#f4b8e4"
color_mauve = "#ca9ee6"
color_red = "#e78284"
color_maroon = "#ea999c"
color_peach = "#ef9f76"
color_yellow = "#e5c890"
color_green = "#a6d189"
color_teal = "#81c8be"
color_sky = "#99d1db"
color_sapphire = "#85c1dc"
color_blue = "#8caaee"
color_lavender = "#babbf1"
color_text = "#c6d0f5"
color_subtext1 = "#b5bfe2"
color_subtext0 = "#a5adce"
color_overlay2 = "#949cbb"
color_overlay1 = "#838ba7"
color_overlay0 = "#737994"
color_surface2 = "#626880"
color_surface1 = "#51576d"
color_surface0 = "#414559"
color_base = "#303446"
color_mantle = "#292c3c"
color_crust = "#232634"

[palettes.catppuccin_macchiato]
color_rosewater = "#f4dbd6"
color_flamingo = "#f0c6c6"
color_pink = "#f5bde6"
color_mauve = "#c6a0f6"
color_red = "#ed8796"
color_maroon = "#ee99a0"
color_peach = "#f5a97f"
color_yellow = "#eed49f"
color_green = "#a6da95"
color_teal = "#8bd5ca"
color_sky = "#91d7e3"
color_sapphire = "#7dc4e4"
color_blue = "#8aadf4"
color_lavender = "#b7bdf8"
color_text = "#cad3f5"
color_subtext1 = "#b8c0e0"
color_subtext0 = "#a5adcb"
color_overlay2 = "#939ab7"
color_overlay1 = "#8087a2"
color_overlay0 = "#6e738d"
color_surface2 = "#5b6078"
color_surface1 = "#494d64"
color_surface0 = "#363a4f"
color_base = "#24273a"
color_mantle = "#1e2030"
color_crust = "#181926"

[palettes.catppuccin_mocha]
color_rosewater = "#f5e0dc"
color_flamingo = "#f2cdcd"
color_pink = "#f5c2e7"
color_mauve = "#cba6f7"
color_red = "#f38ba8"
color_maroon = "#eba0ac"
color_peach = "#fab387"
color_yellow = "#f9e2af"
color_green = "#a6e3a1"
color_teal = "#94e2d5"
color_sky = "#89dceb"
color_sapphire = "#74c7ec"
color_blue = "#89b4fa"
color_lavender = "#b4befe"
color_text = "#cdd6f4"
color_subtext1 = "#bac2de"
color_subtext0 = "#a6adc8"
color_overlay2 = "#9399b2"
color_overlay1 = "#7f849c"
color_overlay0 = "#6c7086"
color_surface2 = "#585b70"
color_surface1 = "#45475a"
color_surface0 = "#313244"
color_base = "#1e1e2e"
color_mantle = "#181825"
color_crust = "#11111b"

[os]
disabled = false
style = "bg:prev_bg fg:prev_bg"
format = "[$symbol ]($style)"

[os.symbols]
Windows = "[](fg:color_blue bg:prev_fg)"
Ubuntu = "[](fg:color_peach bg:prev_fg)"
SUSE = "[](fg:color_green bg:prev_fg)"
Raspbian = "[󰐿](fg:color_red bg:prev_fg)"
Mint = "[󰣭](fg:color_green bg:prev_fg)"
Macos = "[󰀵](fg:color_text bg:prev_fg)"
Manjaro = "[](fg:color_green bg:prev_fg)"
Linux = "[󰌽](fg:color_text bg:prev_fg)"
Gentoo = "[󰣨](fg:color_text bg:prev_fg)"
Fedora = "[󰣛](fg:color_red bg:prev_fg)"
Alpine = "[](fg:color_teal bg:prev_fg)"
Amazon = "[](fg:color_peach bg:prev_fg)"
Android = "[](fg:color_green bg:prev_fg)"
Arch = "[󰣇](fg:color_blue bg:prev_fg)"
Artix = "[󰣇](fg:color_blue bg:prev_fg)"
EndeavourOS = "[](fg:color_purple bg:prev_fg)"
CentOS = "[](fg:color_blue bg:prev_fg)"
Debian = "[󰣚](fg:color_red bg:prev_fg)"
Redhat = "[󱄛](fg:color_red bg:prev_fg)"
RedHatEnterprise = "[󱄛](fg:color_red bg:prev_fg)"
Pop = "[](fg:color_teal bg:prev_fg)"

[username]
# by default only shows on SSH
style_user = "bg:prev_bg fg:color_crust"
style_root = "bg:prev_bg fg:color_crust"
format = '[  $user ]($style)'

[hostname]
# by default only shows on SSH
ssh_symbol = ""
style = "fg:prev_fg bg:prev_bg"
format = "[$ssh_symbol $hostname ]($style)"

[directory]
style = "bg:prev_bg fg:color_crust"
read_only_style = "fg:color_red bg:prev_bg"
format = "[ $path ]($style)[$read_only]($read_only_style)"
truncation_length = 3
truncation_symbol = "…/"
read_only = "󰌾 "

[git_branch]
symbol = ""
style = "fg:color_crust bg:prev_bg"
format = '[ $symbol $branch ]($style)'

[git_commit]
style = "fg:prev_fg bg:prev_bg"
format = "[($tag)]($style) "

[git_status]
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[($all_status$ahead_behind )]($style)'

[nodejs]
symbol = ""
style = "fg:color_crust bg:prev_bg"
format = '[ $symbol( $version) ](fg:color_crust bg:prev_bg)' # bug, must set explicitly

[c]
symbol = " "
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[rust]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[golang]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[php]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[java]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist

[kotlin]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[haskell]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version) ]($style)'

[python]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $version)( $virtualenv) ]($style)'

[docker_context]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $context) ]($style)'

[conda]
symbol = ""
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = '[ $symbol( $environment) ]($style)'

[jobs]
symbol = "󰆅"
style = "fg:color_crust bg:prev_bg" # fg redefined, as prev module may not exist
format = "[ $symbol( $number) ]($style)"

[time]
disabled = false
time_format = "%R"
style = "fg:color_text bg:prev_bg"
format = '[  $time ]($style)'

[cmd_duration]
style = "fg:prev_fg bg:prev_bg"
format = "[ $duration ]($style)"

[memory_usage]
symbol = "󰍛"
style = "fg:bold color_red bg:prev_bg"
format = "[$symbol ${ram}]($style) "
disabled = false

[character]
disabled = false
success_symbol = '[](bold fg:color_green)'
error_symbol = '[](bold fg:color_red)'
vimcmd_symbol = '[](bold fg:color_green)'
vimcmd_replace_one_symbol = '[](bold fg:color_purple)'
vimcmd_replace_symbol = '[](bold fg:color_purple)'
vimcmd_visual_symbol = '[](bold fg:color_yellow)'

Thanks for the suggestion!! Very pretty config.
As described in https://github.com/catppuccin/starship/pull/4#issuecomment-1973724028 of this PR, this repo is meant to be a copy-and-paste reference for those wanting to incorporate Catppuccin colors. The few applications of the palette colors are for demonstration.
That being said, I think it'd be fun for the community to flex their presets. Come up with a fun name, make a folder called presets/, and add it there. I'll accept the RP asap. 💜

Sounds good to me, whatever fits the ecosystem back. Appreciate your involvement
I'll edit my response to reflect

No worries, thanks for still being engaged with this repository.
I've enabled discussions and added the show and tell category: https://github.com/catppuccin/starship/discussions/categories/show-and-tell

Thank you for helping to coordinate a location! I've shared the preset in the Discussion area.


Executing git push after hub pr checkout doesn't work #2929

Executing git push after hub pr checkout doesn't work #2929


[FEATURE] productObject to include most properties listed in the interface

Description
Currently the product object lacks a severe amount of data that is provided but has to be accessed manually by changing the params and other properties are just not accessible at all.
I recommend to add:

tags
extensions

I would prefer to see the whole interface to be available if requested via the api.
Acceptance criteria

[ ] the product object returns a proper "tags" array
[ ] the product object returns a proper "extensions" array
[ ] clear documentation on how to get request them in case they aren't included by default

hi @BeeJayJayn, I have found that extensions is being ignored during serialization process. the extensions property is just unset in entire entity that's because the condition, and that happens only when the includes filtering is turned on. I believe as same as tags property but I can be wrong about that.
If you want to get the whole product interface you need to disable includes for product entity. then you will have every field, even extensions.
btw. I think it's a perfect candidate for an issue to be reported in official Shopware 6 github to clearify reasons why is that. I'm also curious 👍🏻

@mkucmus What do you mean by disabling includes for the product entity? How would one achieve that?

@mkucmus What do you mean by disabling includes for the product entity? How would one achieve that?

I'm almost sure that's the Shopware 6 core issue and should be handled right there. I reported an issue and looking forward for some news.


Support for Blackbox Terminal and Termux

Self-explanatory.

If you’re looking to add support for different terminals or features, the best way is through a pull request—issues are helpful, but PRs make the real impact.

But why are you closing this issue? It was intended for contributors who is available to add such a feature from this issue into the project. Contributors might want to link such an issue to increase the potential of a PR, such as why must it must be added, is it for fixing a bug or implementing a feature?


Updates for vector-read update.

Check for consistency given the previous coupling of layers and featuresets. Related to DigialGlobe/DeepCore-Dev#329 DigialGlobe/DeepCore-Dev#371 and DigialGlobe/DeepCore-Dev#400. Should not be merged until those are complete.

test this please


Circle: Add *.circle extension handling

Thank you for adding circle support in recent version.
I've found it doesn't show *.circle in open file dialog.
I have to write "*.circle" to see *.circle.
Could you please add this change?
It also has other changes about *.circle support.

Update electron-builder.yml for *.circle association
Update description in setup.py.

This was left out intentionally. It is not clear that maintaining and promoting another duplicate format is the right approach. Currently there seem to be no circle files in circulation so wondering if the time is better spent on tflite support which will lead to less code duplication?


no type arguments for views?

@refried originally filed as https://github.com/playframework/playframework/issues/2194. migrating it here
views/foo1.scala.txt  (won't compile)
@[L<:shapeless.Nat:shapeless.ops.nat.ToInt](bar: Bar[L])

@bar has size @shapeless.Nat.toInt[L]

views/foo2.scala.txt  (will compile, but silly!)
@(bar: Bar[_<:shapeless.Nat], size: Int)

@bar has size @size

controllers/Application.scala
package controllers

import play.api._
import play.api.mvc._
import shapeless.Nat
import shapeless.ops.nat.ToInt

class Bar[L<:Nat]

object Application extends Controller {

  def index = Action {
    Ok(views.html.index("Your new application is ready."))
  }

  // won't compile
  def foo1 = views.txt.foo1(new Bar[Nat._3])

  // needlessly complicated
  def foo2 = {
    def barSize[L<:Nat:ToInt](bar: Bar[L]): Int = Nat.toInt[L]
    val bar = new Bar[Nat._3]
    val size = barSize(bar)
    views.txt.foo2(bar, size)
  }
}

+1

+1, indeed.

+1

+1

+1

+1

+1

Hi, FWIW, a workaround is to use the string interpolator:
import play.twirl.api.StringInterpolation

def foo[L <: Nat : ToInt](bar: Bar[L]): Html =
  html"$bar has size ${Nat.toInt[L]}"

Aha, thanks @julienrf, that’s good to know.

big +1

+1

+1

I'd like to replace DomainId with a type argument; otherwise I'm going to have to duplicate this code all over the place.
@(domains: List[(DomainId, String)])(implicit QPE: QueryParamEncoder[Option[DomainId]])

<select name="domain">
    <option value="@{QPE.encode(None).value}">--- ALL DOMAINS ---</option>
    @for(pair <- domains) {
        <option value="<EMAIL_ADDRESS>    }
</select>


Add a bridge between the embedded nvim and another nvim instance

This is more a feature request than an issue.
If I understand correctly, the editing takes place in the embedded neovim instance's buffers which are invisible and the windows in vscode are just coupled to those buffer in such a way as to make it appear the editing taking place in that window.  I'd like to have the ability to see that buffer in its raw, nvim state.  This would mostly be for development and troubleshooting.
A similar thing, but to different ends, would let you switch between editing the vscode window with focus over to editing it in another instance of nvim, (gui or terminal).  That instance could have it own plugins (which won't have to be constrained to only those plug-ins that are compatible with vscode).  Perhaps this "bridging" could use the mechanism of your invisible buffer rather than a strictly file system based one.
Tom Fetherston

Good idea!

That instance could have it own plugins (which won't have to be constrained to only those plug-ins that are compatible with vscode)

Unfortunately, that won't work, because the method that is currently used is actually doing almost exactly what you described. The difference is that this extension spawns the nvim process, instead of you. If too many Vim-specific plugins are loaded, chances are it breaks the VSCode integration. In theory, you could manually load additional plugins after you have 'switched' from VSCode to the terminal.

Perhaps this extension could be enhanced to take NVIM_LISTEN_ADDRESS into account.

Actually, I'm going through the sources and just now discovered that this extension recognises NEOVIM_DEBUG_HOST and NEOVIM_DEBUG_PORT. So if you set NEOVIM_DEBUG=1 and NEOVIM_DEBUG_PORT=4000 it will try to connect to tcp://<IP_ADDRESS>:400.

Actually, I'm going through the sources and just now discovered that this extension recognises NEOVIM_DEBUG_HOST and NEOVIM_DEBUG_PORT. So if you set NEOVIM_DEBUG=1 and NEOVIM_DEBUG_PORT=4000 it will try to connect to tcp://<IP_ADDRESS>:400.

So, does that mean that we could connect to a NeoVim instance running on a tcp port (with something like nvim --listen <IP_ADDRESS>:6600) instead of a path and it would already work with this extension? Or it doesn't support anything like it at the moment?
Right now I'm trying to fully "containerize" my neovim setup but I still need to run an instance on WSL2 for things like VS Code and Azure Data Studio. But if I could connect through tcp I could use Docker's neovim instance instead and keep all my NeoVim setup on containers. Is it currently possible?

I would use it for editing over ssh, since vscode ssh extension has many issues

There is a new neovim ui session api which could be used here, to attach to buffers remotely.


Question: Detecting a route unloading without ngOnDestroy?

I have a route that displays people: /people, and have another route for creating a person: /people/create.  When the user hits the back button in the browser while in /people/create I would like to be able to detect that the route is unloading so that I might do some work.  I think I would typically do this by implementing the OnDestroy interface and putting my cleanup code in ngOnDestroy, but that doesn't seem to work with the ngrx router.  Is there a similar hook for the ngrx router (I cannot find it)?  ie:
ngrxOnUnload() {
    //do some fantastically interesting cleanup work, like hiding a modal
}

I use ngOnDestroy for exactly the purpose you describe and it's working for me... perhaps you have some issue elsewhere?


Can't sell mobs inside supplementaries cages

Mobs captured inside supplementaries cages can not be sold, the trade item is in stock (grey arrow with no red cross) but when you use the trade button or place your trade item into the payment slot, the item doesn't appear to buy.
image
Thanks for you work on this mod, it helps give a real community feel to the server I play on.

Thank you for your report!
Currently on a break, I'm going to have a hard time fixing this immediately, but I will be back at one point.
This might be an NBT issue.
I can't remember from the top of my head, but the item you are trying to sell may not match the items in stock in the crate. The comparison may be on NBT and the entity stocked/saved in the item NBT may be different from another entity saved in the other item's NBt, effectively making them too different to be considered the same item.

yeah this is an nbt issue,
to make sure you are always selling the same item and all items can stack if needed, the crate trading checks for the NBT tag.
This means that other mods saving an entire entity to the NBT of an item will trip the system, as no entities are the same; For instance, every entity has a different ID.
I would suggest reporting this also to Supplementairy Cages.
If the author believes it is still an issue on my end, I hope we can resolve it together.


Add efidisk support

Fixes: #341
Only lightly tested (apply/destroy) on Windows. The size parameter was ignored as it appears proxmox only supports two flash types--2m and 4m--and creates a 4M backing file regardless.

Completed tasks

[x] Investigate pre-enrolled-keys / pre_enrolled_keys mismatch
Outcome: Not going to support this on first pass.
[x] Determine if there's a more idiomatic way to handle efidisk other than using the first item in the slice ExpandDevicesList returns
Outcome: Will defer to code review; added check to handle negative efidisk case.
[x] Test create, destroy, and clone scenarios
Outcome: Basic scenario tests successful.
[x] Update docs
Outcome: Docs updated.

@mleone87 Anything needed on my part to get this over the finish line?

hello @riverar did you have the opportunity to check my comments on the code?

Not yet, my apologies for the silence, will find some time to revisit asap. We can mark this as a draft until ready if you'd like.

Currently blocked on https://github.com/Telmate/proxmox-api-go/issues/253

@riverar , I just ran into this issue. Any idea when this PR will be merged? Would like to default to EFI-only VM's. Also, are you aware of any way to set the EFI settings, such as disabling secure boot?
Thanks!

Yeah this is blocking me too. Next week is bad for me but I should have lots of free time afterwards to see what's left to work on.

OK, can pick this back up now. Sorry for the delay; had a few life events occur back to back.

Friendly ping @mleone87, anything else needed here for an initial implementation?


Add option to limit maximum joint effort

added function in the widowx client to query joint effort from the motor API
added wrapper that converts actions to null actions when maximum joint effort is reached

Others:

added force_reset option in the wrapper that reboots widowx motors

@zhouzypaul  Thanks for the PR. The new LimitMotorMaxEffort wrapper impl looks good to me. Can you also quickly run the pre-commit run --all-files for some styling diff?

Yea just fixed!


MSID: 92916 Version: 2 DOI: 10.1101/2<IP_ADDRESS>1292

MSID: 92916
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>1292
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92916
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1292

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/92916v2
Update ticket with any problems (add blocked label)
Add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>1292
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/92916/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 6: Add PDF url to manuscripts.json
Pull request created to enhanced-preprint-client

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Hi @fred-atherden I've just added this ticket, it wasn't due til 17th Jan but has been moved up to today. Reviews have been posted.

Hi @acollings, do you think it's worth editing the assessment to remove/unbold 'fundamental'?

Thanks @fred-atherden, yes, let's go with "...studying mechanisms of translation..."


Add "Release Date" attribute to content

The Issue
The need to have a release date tag arose during LBRY YouTube sync discussions with @reillysmith .  Oftentimes users will want the need to display videos on a channel according to their release date. Right now, all videos are sorted by publish date, which equates to the block they were published or updated on - this may not always be the desired sort order.
The requirement would be to add a Release Date attribute to uploaded content. If not populated, it should default to publish date (original block date if update later) - open to discussion.
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

This issue was moved to lbryio/lbryschema#19


Add the ability to disable overclocking

When you enable overclocking support, a file is written to /etc/modprobe.d to enable overdrive support in the driver. Currently there is no way to disable it other than removing the file manually. There should be a button in the GUI to do this.

Added in https://github.com/ilya-zlobintsev/LACT/commit/292c94a9c4d4fbcc6315713e3478c2e345b5e400


Style/MutableConstant false positive for heredoc with frozen_string_literal

Rubocop asks to freeze constant string(written with multiline heredoc style) when # frozen_string_literal: true

Expected behavior
No error occures
Actual behavior
[Correctable] Style/MutableConstant: Freeze mutable objects assigned to constants
Steps to reproduce the problem
# frozen_string_literal: true

class MyClass

  MY_CONSTANT = <<~LUA # raises Style/MutableConstant offence
    lorem ipsum
    lorem ipsum
  LUA

end

RuboCop version
rubocop -V
1.20.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.11.0, running on ruby 3.0.2 x86_64-darwin20)
  - rubocop-faker 1.1.0
  - rubocop-performance 1.11.5
  - rubocop-rails 2.11.3
  - rubocop-rspec 2.4.0

.rubocop.yml
  TargetRubyVersion: 3.0

Hello, I was working on a related example I was wondering, this should be frozen after all right? I ran the Rubocop auto correcter and it corrected to this:
# frozen_string_literal: true

class MyClass

  MY_CONSTANT = <<~LUA.freeze # calling .freeze does not raise Style/MutableConstant offense
    lorem ipsum
    lorem ipsum
  LUA

end

Feel free to correct me if I'm wrong as I don't work with frozen HEREDOCS too much. :)
RuboCop version
rubocop -V
1.22.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.12.0, running on ruby 3.0.2 x86_64-linux)
  - rubocop-performance 1.11.5
  - rubocop-rails 2.12.2
  - rubocop-rspec 2.5.0

.rubocop.yml
  TargetRubyVersion: 3.0

Your heredoc would be frozen, and that .freeze triggers an Style/RedundantFreeze offense:
test.rb:5:17: C: [Correctable] Style/RedundantFreeze: Do not freeze immutable objects, as freezing them has no effect.
  MY_CONSTANT = <<~LUA.freeze # calling .freeze does not raise Style/MutableConstant offense
                ^^^^^^^^^^^^^

What was the original code that was autocorrected to your example?

Original code was:

class MyClass

  MY_CONSTANT = <<~LUA
    lorem ipsum
    lorem ipsum
  LUA

end

Actually figured it out -- I think I had some cached version of Rubocop that was running (1.20.0).
Sorry for the noise, and thanks for the explanation!

Glad you figured it out @Zhao-Andy!


teku metrics polling fails to parse

teku_stats_1  | time="2020-08-17T23:50:04Z" level=warning msg="[metrics-watcher] failed to poll metrics: text format parsing error in line 934: expected float as value for 'quantile' label, got \"50%\""
teku_stats_1  | time="2020-08-17T23:50:04Z" level=info msg="[metrics-watcher] querying metrics"
teku_stats_1  | time="2020-08-17T23:50:04Z" level=error msg="[metrics-watcher] reading text format failed:text format parsing error in line 934: expected float as value for 'quantile' label, got \"50%\""
teku_stats_1  | time="2020-08-17T23:50:04Z" level=warning msg="[metrics-watcher] failed to poll metrics: text format parsing error in line 934: expected float as value for 'quantile' label, got \"50%\""
teku_stats_1  | time="2020-08-17T23:50:05Z" level=info msg="[metrics-watcher] querying metrics"

teku metrics response values
# TYPE validator_attestation_publication_delay summary
validator_attestation_publication_delay{quantile="50%",} 0.0
validator_attestation_publication_delay{quantile="95%",} 0.0
validator_attestation_publication_delay{quantile="99%",} 0.0
validator_attestation_publication_delay{quantile="100%",} 0.0

seems the latest fixed this


Fix Storage rewrite operation to support predefinedAcl on a copy

cc: @danoscarmike

[x] Write fix for Storage rewrite operation to support predefinedAcl on targetObject
[x] Verify broken use case prior to applying fix.
[x] Write IT test to verify behavior.
[ ] Code Review.

Note: A unit test for PredefinedAcl with a CopyRequest exist but a integration test didn't exercise the request.
Fixes: #3466

Looks great, thanks for putting that together.

Thanks @pongad!


Skip filtering computations when not requested

Currently, even when filtering is not requested, xpas-build operates a filtering step, which can results in 75% of useless computations.
See below example where phylo-k-mers computation took 9 seconds while useless filtering computations are  40 seconds.
# on lamarck
$ /beegfs/linard/CLAPPAS/clapas_core/bin/lib/xpas/build/xpas-build-aa-pos --merge-branches -k 5 -o 7.0 --ar-binary "$(which raxml-ng)" --refalign /beegfs/linard/CLAPPAS/33208/pruned/3BDA0/Ax/A0_nx0_la.align --reftree /beegfs/linard/CLAPPAS/33208/pruned/3BDA0/Tx/T0_nx0_la.tree.raxml.bestTree.rerooted --ar-dir /beegfs/linard/CLAPPAS/33208/pruned/3BDA0/Dx/A0_nx0_la/AR --workdir /beegfs/linard/CLAPPAS/33208/pruned/3BDA0/Dx/A0_nx0_la/k5_o7.00 --uncompressed

Building database: [stage 1 / 2]:
Calculated 6206257 phylo-k-mers.
Calculation time: 9472

Building database: [stage 2 / 2]:
Kept 279656 / 279656 k-mers (100%) | 3794695 / 3794695 entries (100%).
Filtering time: 40571     <<<<====== !!!!!!!!

Building database: Done.
Built 279656 phylo-k-mers for 279656 different k-mers.
Total time (ms): 50043

Saving database to: /beegfs/linard/CLAPPAS/33208/pruned/3BDA0/Dx/A0_nx0_la/k5_o7.00/DB_k5_o7.0.rps...
Compression: OFF
Time (ms): 187

There is no filtering happening, all this time is spent to merge temporary node databases (see "Kept ... 100% k-mers"). This example is slow because of intensive I/O, which we can reduce by changing the db_builder::_num_batches parameter. Will do it in the future versions

This should not happen anymore with a791b83c and a5fa858cb (unless you enable --on-disk which I don't advise for CLAPPAS).
I'll release a new version soon. Let me know if you encounter future problems with I/O.


[#2PlaysAMonth]: DevBlog project done

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
DevBlog play is done. it's the 2nd project for 2playsamonth
Fixes #987
Type of change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[X ] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots or example output

Please fix the compilation error before pushing

fixed


Questions about proper usage of setuptools-protobuf

Hello!
I am working on a nice protobuf build process in my project and bumped into your project, which looks very promising.
The problem is, I am new to all this PEP-517 stuff and I can't figure out how I can do several things and can I do it at all:

I need to include builded proto into sdist, but as far I can see, you are injecting into "build" subcommands, so am I understanding correctly that I need to inject something somewhere myself?
I want to build proto while editable installation too.
I need to figure out my protobufs list dynamically, and maybe even move protobuf files into my project tree while building process.
And I can't figure out what I need to write in my pyproject.toml to start using setuptools-protobuf.

I would very much appreciate your consultation, thanks in advance!

See the example in README; however, you won't be able to use this if you need to dynamically figure out the protos to compile. In that case, your only option is passing in options in setup.py.

I believe you are missing some readme about [distutils.*] sections in pyproject.toml to use your shiny new setuptools_protofub.pyprojecttoml_config and get rid of setup.py completely. I am trying to figure out, that maybe I can define some PEP-517 build entry point in my pyproject.toml where I can call your code.
I leave for one week's vacation and will be back to this task in 8-9 days.
Maybe you will issue a new release at that time and I will be able to contribute something.
Thanks!

There shouldn't be a need to explicitly add anything else in your pyproject.toml; installing setuptools_protobuf itself (don't just put in $PYTHONPATH) using pip should install all the right entrypoints.
A couple of my projects (e.g. https://github.com/jelmer/disperse/blob/main/setup.py) do exactly this.

Closing this since I think I've addressed the original questions; please reopen and comment if you'd like me to expand on anything.