Failed to build

I tried to build it following the instruction, but it failed in the following steps. The jetson-utils was not installed so that I have to manually install it. After it, the timeDiff() function doesn't agree with 3 parameters used in tensorNet.h. Please help, thanks!
nano:~/jetson-inference/build$ make
[ 38%] Built target jetson-utils
[ 39%] Building NVCC (Device) object CMakeFiles/jetson-inference.dir/c/jetson-inference_generated_detectNet.cu.o
:0:7: warning: ISO C++11 requires whitespace after the macro name
:0:7: warning: ISO C++11 requires whitespace after the macro name
:0:7: warning: ISO C++11 requires whitespace after the macro name
:0:7: warning: ISO C++11 requires whitespace after the macro name
:0:7: warning: ISO C++11 requires whitespace after the macro name
/home/lhuang/jetson-inference/c/tensorNet.h(453): error: too many arguments in function call
/home/lhuang/jetson-inference/c/tensorNet.h(454): error: identifier "timeFloat" is undefined
2 errors detected in the compilation of "/tmp/tmpxft_00006a03_00000000-8_detectNet.compute_72.cpp1.ii".
CMake Error at jetson-inference_generated_detectNet.cu.o.cmake:279 (message):
Error generating file
/home/lhuang/jetson-inference/build/CMakeFiles/jetson-inference.dir/c/./jetson-inference_generated_detectNet.cu.o
CMakeFiles/jetson-inference.dir/build.make:63: recipe for target 'CMakeFiles/jetson-inference.dir/c/jetson-inference_generated_detectNet.cu.o' failed
make[2]: *** [CMakeFiles/jetson-inference.dir/c/jetson-inference_generated_detectNet.cu.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/jetson-inference.dir/all' failed
make[1]: *** [CMakeFiles/jetson-inference.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

I got exactly the same error on Jetson Nano

Had you run the "git submodule update --init" step?
Those ISO C++11 whitespace warnings, it tells me an old version of jetson utils is being used.
Can you try recloning jetson-inference repo with this command:
"git clone --recursive https://github.com/dusty-nv/jetson-inference"

From: Agustinus Baskara<EMAIL_ADDRESS>Sent: Wednesday, July 10, 2019 5:27:42 AM
To: dusty-nv/jetson-inference
Cc: Subscribed
Subject: Re: [dusty-nv/jetson-inference] Failed to build (#355)
I got exactly the same error on Jetson Nano
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/355?email_source=notifications&email_token=ADVEGK4556BZGHPGKOORK3LP6WTQ5A5CNFSM4H7LX5VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZS4IDI#issuecomment-509985805, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADVEGK4FSPGBPHI6S3O4OEDP6WTQ5ANCNFSM4H7LX5VA.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Somehow the link to the jetson-utils submodule didn't get updated when I merged the changes yesterday, sorry about that.  I have now updated it manually, so please re-clone the jetson-inference repo and try building again:
git clone --recursive https://github.com/dusty-nv/jetson-inference

Works perfectly now. Thanks!
Regards,
Lei Huang

On Jul 10, 2019, at 8:44 AM, Dustin Franklin<EMAIL_ADDRESS>wrote:
Somehow the link to the jetson-utils submodule didn't get updated when I merged the changes yesterday, sorry about that. I have now updated it manually, so please re-clone the jetson-inference repo and try building again:
git clone --recursive https://github.com/dusty-nv/jetson-inference
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/dusty-nv/jetson-inference/issues/355?email_source=notifications&email_token=AKJ6M2CIVROMPBJIP4CIV6TP6XRUXA5CNFSM4H7LX5VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZTQC2Q#issuecomment-510067050, or mute the thread https://github.com/notifications/unsubscribe-auth/AKJ6M2CH2KZ6LENL5RE5SRLP6XRUXANCNFSM4H7LX5VA.


Support email field, add eslint

Hey!  As discussed with my colleague David, we are going to contribute to your repository. We've created this PR and would like to get your feedback on our code quality, as we've noticed it differs a bit from yours. The things we've added/changed so far:

We added ESLint/Prettier into the repo, and we've tried to respect your code rules.
We had to downgrade node-fetch to v2 because of bug in next13, but eventually it got fixed so we reverted it back.
We added a new Email field with an option to support confirmation. We also created a new shared Input component so that it can be used in InputField, as well as in Email and other Input-related fields later on

Thanks for submitting this PR @Gytjarek
I am unable to test due to an error about importing React. It seems that you have remove React from components/Input/index.js - but due to a underlying dependency of a React version below 17 - this cannot happen.
I am using the following repo to test, so you can see for yourself: https://github.com/robmarshall/next-gravity-forms-example
How to test on the above repo

Removed the next-gravity-forms package from the above repo.
Navigate into your local "next-gravity-forms" root.
Build it using "yarn build"
Navigate into the dist folder and run yarn link
Navigate back to the example repo root and run yarn link "next-gravity-forms"

Few general notes

If you could keep PRs feature specific. There are a few other changes as well as the email addition. If these can be removed and put in as separate PRs - makes reviewing/testing a lot smoother.

An li has been replaced by a div. This goes against how Gravity Forms sets up their form on the frontend if using a WP site so would rather not change this. It would also be a breaking change for users already using this package due to how they may be targeting their CSS.

I have added some general updates/cleanup to main. If you could pull these in, and update this PR to be only for the email feature.

Hi @robmarshall! Thanks for your feedback.
I have a few questions though:

I noticed that you recently updated your example repository to React 18 and Next.js 14. Does this mean we no longer need to support React 17, or do you still want to maintain support for it? If so, what is the reason?

I changed li to div because I thought we wanted to align with the GravityForms plugin as closely as possible, and in the new version, they indeed use divs.  Also, we could easily update users about breaking changes in the README, and I don't think it's really a breaking change, as most users add styles by using CSS classes, which remain the same and not tags. What are your thoughts on this?

Thanks!


mesa (+stdenv / meson): fix cross-compilation support w/ llvm

Motivation for this change
Mesa didn't cross-compile anymore since 21.0.3 (the update to 21.1.x broke it), since the way it's packaged requires llvm since that update. This properly adds llvm-config-native to the meson cross config file and adds the llvm dependency to mesa.
I'm not 100% sure if this should be llvmPackages.llvm or if it can also be e.g. llvmPackages.libllvm, but this seems to work fine.
Things done

Built on platform(s)

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

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

Want to add "Fixes: https://github.com/NixOS/nixpkgs/issues/136926" to your commit message?


[Chore]: Connection error in the E2E tests

Build URL
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/363
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/349
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/324
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/338
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/323
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/280
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-pr/builds/173
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/211
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/138
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-pr/builds/43.1
https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-pr/builds/43
Description
Different tests in the E2E suite seem to be failing sporadically with connection errors. See log bellow for an example failure.
• [FAILED] [4.213 seconds]
Orgs
/tmp/build/3e139e9d/korifi/tests/e2e/orgs_test.go:16
  list domains
  /tmp/build/3e139e9d/korifi/tests/e2e/orgs_test.go:277
    when the user is not authorized in the organization
    /tmp/build/3e139e9d/korifi/tests/e2e/orgs_test.go:313
      [It] returns a not found error
      /tmp/build/3e139e9d/korifi/tests/e2e/orgs_test.go:318

  Begin Captured StdOut/StdErr Output >>
    W0703 18:26:11.358444     519 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead.
    To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
  << End Captured StdOut/StdErr Output

  Begin Captured GinkgoWriter Output >>
    Fail Handler: failure correlation ID: "e91a4d07-428e-4dcc-a512-c65b9d1f9a4f"

    ===== Logs for pod "korifi-api-deployment-ccbb6796d-brhjs" with correlation ID "e91a4d07-428e-4dcc-a512-c65b9d1f9a4f" (last 50 lines) =====
    {"level":"info","ts":1656872768.52545,"logger":"retrying-client","msg":"k8s client returned forbidden","correlation-id":"e91a4d07-428e-4dcc-a512-c65b9d1f9a4f","op":"create","count":1,"error":"rolebindings.rbac.authorization.k8s.io \"cf-98ffe9c334e24367195b34585ce035a0c368a8f9762a6ade1d2ed5c8975f7afd\" already exists"}

    ==============================================

    ===== Logs for pod "korifi-controllers-controller-manager-6d89b879f-pfhrl" (last 50 lines) =====
    1.656872771118818e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfapp", "code": 200, "reason": "", "UID": "6667c493-55e9-40c4-854d-067bb947a504", "allowed": true}
    1.6568727714641182e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/mutate-korifi-cloudfoundry-org-v1alpha1-cfroute", "UID": "4c3c0d93-c6bb-4842-a536-0392497ec714", "kind": "korifi.cloudfoundry.org/v1alpha1, Kind=CFRoute", "resource": {"group":"korifi.cloudfoundry.org","version":"v1alpha1","resource":"cfroutes"}}
    1.656872771464388e+09	INFO	cfroute-resource	Mutating CFRoute webhook handler	{"name": "cf-route-ce9a2308-e12c-43d6-8843-7f2ef37e9d40"}
    1.656872771464774e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/mutate-korifi-cloudfoundry-org-v1alpha1-cfroute", "code": 200, "reason": "", "UID": "4c3c0d93-c6bb-4842-a536-0392497ec714", "allowed": true}
    1.6568727714651327e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfspace", "UID": "9de8e0f5-7f9a-41f4-b10f-12225cfbcbee", "kind": "korifi.cloudfoundry.org/v1alpha1, Kind=CFSpace", "resource": {"group":"korifi.cloudfoundry.org","version":"v1alpha1","resource":"cfspaces"}}
    1.6568727714787273e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfroute", "UID": "0fd113e7-1c8e-45cd-a199-2ace619f8966", "kind": "korifi.cloudfoundry.org/v1alpha1, Kind=CFRoute", "resource": {"group":"korifi.cloudfoundry.org","version":"v1alpha1","resource":"cfroutes"}}
    1.6568727714791434e+09	ERROR	route-validation	Route destination app not found in space	{"error": "CFApp.korifi.cloudfoundry.org \"18887ed9-5cc8-48b8-b48e-cec161478f98\" not found"}
    code.cloudfoundry.org/korifi/controllers/webhooks/networking.(*CFRouteValidator).validateDestinations
    	/workspace/controllers/webhooks/networking/cfroute_validator.go:207
    code.cloudfoundry.org/korifi/controllers/webhooks/networking.(*CFRouteValidator).ValidateUpdate
    	/workspace/controllers/webhooks/networking/cfroute_validator.go:128
    sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*validatorForType).Handle
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/webhook/admission/validator_custom.go:87
    sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).Handle
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/webhook/admission/webhook.go:146
    sigs.k8s.io/controller-runtime/pkg/webhook/admission.(*Webhook).ServeHTTP
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/webhook/admission/http.go:98
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerInFlight.func1
    	/go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:40
    net/http.HandlerFunc.ServeHTTP
    	/usr/local/go/src/net/http/server.go:2084
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerCounter.func1
    	/go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:117
    net/http.HandlerFunc.ServeHTTP
    	/usr/local/go/src/net/http/server.go:2084
    github.com/prometheus/client_golang/prometheus/promhttp.InstrumentHandlerDuration.func2
    	/go/pkg/mod/github.com/prometheus/client_golang@v1.12.2/prometheus/promhttp/instrument_server.go:84
    net/http.HandlerFunc.ServeHTTP
    	/usr/local/go/src/net/http/server.go:2084
    net/http.(*ServeMux).ServeHTTP
    	/usr/local/go/src/net/http/server.go:2462
    net/http.serverHandler.ServeHTTP
    	/usr/local/go/src/net/http/server.go:2916
    net/http.(*conn).serve
    	/usr/local/go/src/net/http/server.go:1966
    1.656872771479265e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfroute", "code": 403, "reason": "{\"validationErrorType\":\"RouteDestinationNotInSpaceError\",\"message\":\"Route destination app not found in space\"}", "UID": "0fd113e7-1c8e-45cd-a199-2ace619f8966", "allowed": false}
    1.656872771488808e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfspace", "code": 200, "reason": "", "UID": "9de8e0f5-7f9a-41f4-b10f-12225cfbcbee", "allowed": true}
    1.6568727715045846e+09	INFO	controllers.CFSpace	Reconciling deletion of cf-space-0c2489b4-ee43-4521-bf35-ef199ab86e11
    1.6568727715612676e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfspace", "UID": "22b1b202-a4ff-4ada-8023-f35579973ff0", "kind": "korifi.cloudfoundry.org/v1alpha1, Kind=CFSpace", "resource": {"group":"korifi.cloudfoundry.org","version":"v1alpha1","resource":"cfspaces"}}
    1.6568727715616474e+09	DEBUG	controller-runtime.webhook.webhooks	wrote response	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfspace", "code": 200, "reason": "", "UID": "22b1b202-a4ff-4ada-8023-f35579973ff0", "allowed": true}
    1.6568727716107204e+09	ERROR	controllers.CFSpace	Error when trying to fetch CFSpace cf-org-8d0f45bb-1437-463d-80cb-9b307f11f1d1/cf-space-0c2489b4-ee43-4521-bf35-ef199ab86e11	{"error": "CFSpace.korifi.cloudfoundry.org \"cf-space-0c2489b4-ee43-4521-bf35-ef199ab86e11\" not found"}
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:121
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:320
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
    sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
    	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
    1.6568727716326892e+09	DEBUG	controller-runtime.webhook.webhooks	received request	{"webhook": "/validate-korifi-cloudfoundry-org-v1alpha1-cfspace", "UID": "5aa9204f-c2ed-4a82-9890-0bd9122abc2e", "kind": "korifi.cloudfoundry.org/v1alpha1, Kind=CFSpace", "resource": {"group":"korifi.cloudfoundry.org","version":"v1alpha1","resource":"cfspaces"}}

    ==============================================

    Fail Handler: completed
  << End Captured GinkgoWriter Output

  Expected
      <helpers.actualRestyResponse>:
      Request: GET https://cf.pr-e2e.korifi.cf-app.com/v3/organizations/cf-org-9f546b5b-e0cd-47f2-9074-9ae537efb8d3/domains
      Request headers:
          X-Correlation-Id: e91a4d07-428e-4dcc-a512-c65b9d1f9a4f
          User-Agent: go-resty/2.7.0 (https://github.com/go-resty/resty)
          Authorization: Bearer <Redacted>
      Request body:
          null
      HTTP Status code: 503
      Response headers:
          Content-Type: text/plain
          Vary: Accept-Encoding
          Date: Sun, 03 Jul 2022 18:26:11 GMT
          Server: envoy
      Response body:
          upstream connect error or disconnect/reset before headers. reset reason: connection failure
  to have HTTP Status code
      <int>: 404
  In [It] at: /go/pkg/mod/github.com/onsi/gomega@v1.19.0/internal/assertion.go:58

Looking at the failure times and superimposing them on the dashboard data for both pr-e2e and concourse clusters it looks like the connection reset is not due to particularly high load or because test run coincided with cluster recreation.
Unfortunately there are not too many logs from the api shim (they are all filtered by correlation id) so not too much insight if the shim crashed.
Could it be some default server configuration that is throttling requests if they get too many?

There are some evidences on the internet that a connection reset could be caused by a timeout between the contour proxy and the api server (i.e. the api server is too slow handling the request). However, in the korifi deployment we set this timeout to 5 minutes, therefore it is not likely to be that.
I have added an "on-failure" task to e2e test (both main and periodics) to get contour's logs, hopefully this should shed more light on the issue.
Blocking until the issue happens again

We have it reproduced on CI with contour logs: https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-main/builds/104

I believe that this was caused by panics in the API shim. We found some evidence in the logs that some logger calls were passing non-even arguments in the key/value part of the argument list, which causes a panic. That would account for Contour losing connection to the API.
We think this should be fixed by this commit
Separately, on a procedural note, should this chore not be a bug? Having the API report 503s feels like a bug to me.

Closing due to inactivity. If we keep seeing the flake we should reopen this issue or log a new one


[ci skip] Remove old unused patches folder

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


Instalation can't be finished

Hello, I have a problem with instalation and running bash
I've enabled the "Windows Subsystem for Linux (Beta)" and after restart runed from command line
bash
The result was:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. Všechna práva vyhrazena.

C:\Users\Filip>bash
-- Beta feature --
This will install Ubuntu on Windows, distributed by Canonical
and licensed under its terms available here:
https://aka.ms/uowterms

Type "y" to continue: y
Downloading from the Windows Store... 100%
Extracting filesystem, this will take a few minutes...`

After that, I can see proccess Init in task manager for hours but nothing happened

If I restart console result is same proccess init, nothing happend
I've tried reinstall:
lxrun /uninstall /full
lxrun /install
and reenable "Windows Subsystem for Linux (Beta)" with no result
Is there any solution? Or are there any posibilites to debug this problem?
Thank you
Filip Richter
C:\Users\Filip>ver
Microsoft Windows [Version 10.0.14393]

Log files from LogMan, that I recorder
lxcore.zip

I have the same problem
Windows 10.0.14393.10
if i restart my pc bash work but isnt good and i cant install any packages

But I'm not able to get to
Please create a default UNIX user account. .....
It stops before it

Problaby a duplicate of https://github.com/Microsoft/BashOnWindows/issues/718
It's the antivirus. Uninstall Avast and try bash again.

Yes, I have Avast, I will try the Beta, thank you

I have Kaspersky. what about it?

Kaspersky also has known issues.  See #475 .  I don't think people have gotten it to work at all yet; you might find that you need to uninstall it entirely.

ops, Do you plan to solve the problem by Microsoft in the future?

Kaspersky is also working on it. https://forum.kaspersky.com/index.php?s=662d01d349ad8497a83c6ea81871f05e&showtopic=354919
It's a matter of time every antivirus/firewall ends being compatible with the WSL.

i uninstalled it entirely and bash work fine!
i installed Eset Security and i dont have any problem
tnx you bro.


Remove all unused forks from our Github account

As part of the onboarding process for OSC, we used to fork the project's repositories to add widgets to their READMEs (if I remember correctly). We stopped doing that around a year ago, I believe?
These forks are outdated, and we get contacted by security researchers who believe it's our code and report various problems.
In order to:

Clean our main account (we can always create a puppet account if we want to do that again in the future)
Avoid confusion on the ownership of these repos

I suggest that we remove all these forks. We may have to use an automated tool, given the number of entries (800+).

Hello 👋 @Betree assign this task to me.

@Hosilamar You won't have enough permission to delete repositories on our account. I suggest looking at this list if you're looking for a good first issue to contribute to: https://github.com/opencollective/opencollective/issues?q=is%3Aopen+is%3Aissue+no%3Aassignee+label%3A"complexity+→+minimal"%2C"complexity+→+simple"+-label%3Ateam%2Cdiscussion%2C"blocked+→+waiting+third+party"%2C"blocked+→+waiting+parent"%2C"blocked+→+waiting+feedback"%2C"needs+design"%2C"needs+specs"+

Came up with a first list that should cover around 650 forks (on a total of 853) where @monkeywithacupcake is an admin.
Our repos lists now look a bit cleaner when not showing archived.
Posting the script I played with to do the changes:
#!/usr/bin/env node

import fs from 'fs';

import { Octokit } from '@octokit/rest';
import { Command } from 'commander';
import { flatten, pick, uniq } from 'lodash';

import { confirm } from './common/helpers';

const LEGIT_FORKS = [
  'opencollective/funders-dashboard',
  'opencollective/burner-email-providers',
  'opencollective/discover',
  'opencollective/next-auth-example',
];

const ARCHIVED_KEEP = [
  'opencollective-cli',
  'opencollective-bot',
  'opencollective-setup',
  'opencollective-zapier',
  'babel-preset-opencollective',
  'opencollective-giftcards-generator',
  'opencollective-email',
  'ledger-archived',
  'opencollective-website',
  'intelligence',
  'opencollective-app',
  'website-static',
  'opencollective-site',
  'opencollective-jobs',
  'npm-postinstall',
  'native',
  'express-server-status',
  'opensource',
  'opencollective-lib',
  'mobileapp-design',
  'style-guide',
];

const CORE_TEAM = [
  'xdamman',
  'arnaudbenard',
  'asood123',
  'sedubois',
  'znarf',
  'Betree',
  'gustavlrsn',
  'kewitz',
  'piamancini',
  'sbinlondon',
  'hdiniz',
  'Philmod',
  'flickz',
  'HipsterBrown',
  'clarete',
];

const program = new Command()
  .option('-f, --force', 'Skip confirmation before delete')
  .option('-p, --printOnly', 'Print repo names (sorted alphabetically) + owner')
  .option('-s, --pageSize <pageSize>', 'Number of repositories to fetch per page')
  .option('-c, --generateCache', 'Generate cache file')
  .option('-a, --archive', 'Archive repositories instead of deleting them')
  .parse(process.argv);

const dryMode = process.env.DRY_RUN !== 'false';
const skipConfirmation = program.getOptionValue('force');
const printOnly = program.getOptionValue('printOnly');
const pageSize = program.getOptionValue('pageSize') || 100;

const octokit = new Octokit({ auth: process.env.GITHUB_TOKEN });

async function getForkedRepositories() {
  const cacheFile = './.forked-repos-cache.json';
  if (program.getOptionValue('generateCache')) {
    // Fetch data
    const reposToProcess = [];
    console.log('Generating forks cache...');

    let page = 1;
    let isDone = false;
    do {
      console.log(`Fetching page ${page}...`);
      const { data } = await octokit.repos.listForOrg({
        org: 'opencollective',
        type: 'forks',
        per_page: pageSize,
        page: page++,
        sort: 'full_name',
      });

      for (const repo of data) {
        if (repo.archived) {
          continue;
        }

        // Uncomment to get only forks where Jess is admin
        // const { data: collaborators } = await octokit.repos.listCollaborators({
        //   owner: repo.owner.login,
        //   repo: repo.name,
        // });
        // if (collaborators.some(c => c.login === 'monkeywithacupcake')) {
        //   reposJessIsAdminOf.push(repo);
        // }

        // Get latest commits to see if they were made by someone from the team
        const { data: commits } = await octokit.repos.listCommits({
          owner: repo.owner.login,
          repo: repo.name,
          per_page: 10,
        });

        const commiters = uniq(flatten(commits.map(c => c.author?.login))).filter(Boolean);
        if (commiters.some(a => CORE_TEAM.includes(a))) {
          continue;
        }

        reposToProcess.push({
          ...pick(repo, ['full_name', 'name', 'owner']),
          commiters,
        });
      }

      isDone = data.length < pageSize;
    } while (!isDone);

    // Write cache file
    fs.writeFileSync(cacheFile, JSON.stringify(reposToProcess, null, 2));
  }

  const repos = JSON.parse(fs.readFileSync(cacheFile, 'utf8'));
  return repos.filter(r => !LEGIT_FORKS.includes(r.full_name) && !ARCHIVED_KEEP.includes(r.name));
}

async function deleteRepository(repo) {
  if (!skipConfirmation) {
    const confirmation = await confirm(`Delete forked repository '${repo.full_name}'? (y/n) `);
    if (!confirmation) {
      console.log(`Skipping deletion of '${repo.full_name}'...`);
      return;
    }
  }

  if (dryMode) {
    console.log(`(DRY MODE) Deleting forked repository '${repo.full_name}'...`);
  } else {
    await octokit.repos.delete({
      owner: 'opencollective',
      repo: repo.name,
    });
    console.log(`Deleted forked repository '${repo.full_name}'.`);
  }
}

async function archiveRepository(repo) {
  if (!skipConfirmation) {
    const confirmation = await confirm(`Archive forked repository '${repo.full_name}'? (y/n) `);
    if (!confirmation) {
      console.log(`Skipping archiving of '${repo.full_name}'...`);
      return;
    }
  }

  if (dryMode) {
    console.log(`(DRY MODE) Archiving forked repository '${repo.full_name}'...`);
  } else {
    await octokit.repos.update({
      owner: 'opencollective',
      repo: repo.name,
      archived: true,
    });
    console.log(`Archived forked repository '${repo.full_name}'.`);
  }
}

async function run() {
  try {
    const forkedRepos = await getForkedRepositories();
    if (printOnly) {
      forkedRepos.sort((a, b) => a.full_name.localeCompare(b.full_name));
      forkedRepos.forEach(repo => {
        console.log(`${repo.full_name}`);
      });
      return;
    }

    for (const repo of forkedRepos) {
      if (program.getOptionValue('archive')) {
        await archiveRepository(repo);
      } else {
        await deleteRepository(repo);
      }
    }
  } catch (error) {
    console.error('An error occurred:', error);
  }
}

run();


Bugfix: Send correct URL to Datacite on garden register-doi

Fixes #474
Overview
Send datacite the correctly formatted URL when registering a doi.
Testing
Added a new unit test in test/test_client.py to verify the URL is correct.

📚 Documentation preview 📚: https://garden-ai--477.org.readthedocs.build/en/477/

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.82%. Comparing base (cb448fb) to head (69d1681).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #477      +/-   ##
==========================================
+ Coverage   76.43%   76.82%   +0.38%
==========================================
  Files          51       51
  Lines        3421     3448      +27
==========================================
+ Hits         2615     2649      +34
+ Misses        806      799       -7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


 This can be seen in the book theme when running myst start locally.

To reproduce - ensure that no cookies are set


optimize code for upgrade

clear_prefix returns a result type, must be used to avoid warning, it's ok to ignore error cases here.
Babe config should be fetched from runtime. https://github.com/paritytech/substrate/pull/11760
Query fee and details for Call. https://github.com/paritytech/substrate/pull/11819

Codecov Report
Base: 60.49% // Head: 60.39% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (dcd2e93) compared to base (d14cefb).
Patch coverage: 17.64% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #342      +/-   ##
==========================================
- Coverage   60.49%   60.39%   -0.10%
==========================================
  Files          70       70
  Lines       18566    18573       +7
==========================================
- Hits        11232    11218      -14
- Misses       7334     7355      +21

Impacted Files
Coverage Δ

runtime/src/lib.rs
10.88% <0.00%> (-0.09%)
:arrow_down:

pallets/staking/src/lib.rs
67.94% <100.00%> (-0.70%)
:arrow_down:

pallets/staking/src/slashing.rs
97.33% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Switch the pre-commit hook used to run prettier

🗣 Description
This pull request switches the pre-commit hook used to run prettier from pre-commit/mirrors-prettier to rbubley/mirrors-prettier.

💭 Motivation and context
The pre-commit/mirrors-prettier hook has been archived due to changes in the upcoming prettier v4 that "break plugins entirely".  A longstanding gripe I have had with the hook is that as soon as a pre-release is cut (basically the first alpha release), the older stable major version no longer gets updated tags. The new hook ignores pre-releases and, so far at least, is only cutting tags for the v3 point releases.

🧪 Testing
Automated tests pass.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

Very late to the game here.  But wanted to thank you for making this change.


Block Letter English Alphabets Detection through Saral App

Block Letter English Alphabets Detection through Saral App

now with the help of new extractionMethod i.e "BLOCK_ALPHANUMERIC_CLASSIFICATION" . Alphanumeric detection is also possible .


Single star mode for sevn does not preserve mass limits

Just browsing this for a class and found that the SinglePop mode makes mass extremes wrong. Thank you for the code.

Hi, I suppose you are referring to the example.py. There was a typo in the example, the call to pop.Binaries wrongly used the parameter mass_range instead of mass_ranges. This is now fixes.
Thank you for spotting this!


CASMMON-72, CASMMON-101, CASMMON-100 : Enable SMART metrics, alerts and grafana dashboard for k8s nodes

Made changes to plotform.yaml by bumping the sysmgmt-health version.
PR
https://github.com/Cray-HPE/cray-sysmgmt-health/pull/38
Resolves
https://connect.us.cray.com/jira/browse/CASMMON-72
https://connect.us.cray.com/jira/browse/CASMMON-101
https://connect.us.cray.com/jira/browse/CASMMON-100
created release tag
https://github.com/Cray-HPE/cray-sysmgmt-health/releases/tag/v1.2.9

/backport main


8bit png

There was no problem with using png type 3, 4 in w2x conversion that #107 provided.
this problem is due to checking function does not recognize type 3 and 4 images as png
if you have other files that includes alpha but 8bit, feel free to test with this PR.
fixes #107

it may conflict with #148, so please merge #148 first.

Seems fixed.
Before:

After:

I'll merge this first because #148 failed.


Insert csv filename

Hi. I could load and insert the data of a csv file into db, but want to know how to insert the filename in the same querry.
Using this code bellow:
Excel::filter('chunk')->load($csvfile)->chunk(500, function($results {
    foreach($results as $row) {
        $models = Model::create([
            'column1' => $row->csv_file_first_row1,
            and other columns....

Do I have to run a second query to update the rows with the filename column?
Thanks.

What about something like:
    $csvFile = 'storage/file.csv';
    Excel::filter('chunk')
        ->load($csvFile)
        ->chunk(500, function ($rows) use ($csvFile) {
            foreach ($rows as $row) {
                App\MyModel::create([
                    'column1' => $row->column1,
                    'filename' => $csvFile,
                    // other columns...
                ]);
            }
        });

Hi @stephanecoinon , thanks for your help!
I just saw it after solving by myself.
I just pulled out from the Insert query and that worked!


Box Users -m flag

I would like to retrieve a list of all managed users.
The Users command with the -m flag is not skipping App Users
box users --managed-users --yes --fields=id,name,login --save-to-file-path=./inputs/UserList.json

@dann815 This should maybe be fixed in the API (which returns the mixed collection of Managed and App users when you pass the query parameter), but we could also add post-filtering of the collection in the CLI to accomplish the same effect.  We'll add it the backlog, but if you need it more quickly you're of course free to submit a PR!

Thanks for posting @dann815. External users will not be included in the result unless you include --filter option and set it to the login of the external user you'd like to fetch. See more at: https://developer.box.com/reference/get-users/#param-filter_term


update instructions to create initial admin account

This updates the README file with instructions for creating an initial admin account with manager-level permissions.  It removes a rake task that no longer works with the new, more advanced account management features.
This addresses ticket #8298.

Minor docs suggestion, but otherwise :+1:

Good suggestion.  I added an example and :squash:ed.

Rebase?

Rebased and ready to :merge:


updating bedrock script to write whitelist

This doesn't set a XUID for the players. I'm keeping it this way so it matches java edition and seems easier. The downside is that it will smash the whitelist on each boot and, thus, nuke the XUIDs that are written to the file. I don't think this is a big deal, but worth noting.

Oh, it would be good to have a note in the README that explains the whitelist parameters maps a little bit differently than the others listed there. With that I'm good to merge.


NixOS 21.11

This seems to be working without any changes besides switching to the new channel. It'd be great if someone else could verify that everything works before I merge this. (Just in case I missed something)

Not sure about 21.11, but I've been running unstable for a while now and it works fine.

I’ve been using 21.11 and it’s fine


Fix merge_lines

As pointed out by the linter, the cyclomatic complexity of this function is too high. Fix repeated content and integrate the auxiliary function with the other very similar function:
https://github.com/CityRiverSpaces/rcoins/blob/ff7b6cf88a957d5068f3d452f86eb5594a240772/R/stroke.R#L215-L223

I suggest putting all the while loop in a separate function and calling it later in merge_lines function.

Done!


fix(footer): all grid-template-areas show gap regardless of existing

fixes #575
What I did

Instead of using row-gap to separate the first and second rows of primary links we are going to use quantity queries in our lightdom file and margin-block-start.

Testing Instructions

Visit https://deploy-preview-576--red-hat-design-system.netlify.app/components/footer/demo/

[ ] Verify, on desktop, there is 64px between the primary links and global footer.

Visit https://deploy-preview-576--red-hat-design-system.netlify.app/components/footer/demo/

Open the dev tools and paste in the following code snipet

document.querySelector('rh-footer').insertAdjacentHTML('beforeend', `
Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

Lorem ipsum

`);

[ ] Verify, on desktop, that there is a 32px gap between row 1 and row 2 of the primary links.

Screenshots

Perhaps a job for subgrid in the future:
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout/Subgrid

@heyMP Design looks good.


ziti shell profile for controller container

add ziti CLI completions

@dovholuknf this is the Helm counterpart to the PR I sent in the ziti repo to enable the shell completions you suggested.

Waiting to merge this until these commits percolate in a release container image we can pin in this chart.yaml.

Merging this should coincide with releasing https://github.com/openziti/ziti/pull/1109.


adding parameters of the SB2001 microphysics 2m scheme

Purpose
adding parameters of the SB2001 microphysics 2m scheme
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,

appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

I have read and checked the items on the review checklist.

bors r+

bors r+


Refs #28592 -- Removed redundant spaces in docs/ref/csrf.txt.

Ticket https://code.djangoproject.com/ticket/28592
Inspired by PR https://github.com/django/django/pull/9071 but with the conflicts resolved.
First in a series of PRs as suggested in #14956.

Remove extra whitespace in ref/csrf.txt

@tommcn Thanks :+1: Welcome aboard :boat:


fix ID2= debug tag explosion

I don't really understand this, but wasn't involved in the original development/review.
Why a shallow copy instead of just a new context?

I want to have a mega-debug tag for the background identifier loop itself BG=3se334EeFe or so.
If we don't copy the Context over, we'll be continuously accumulating tags here

Usually that's OK before we throw these engine.Context's away after using them once.

Ok, it still seems like you could do something along the lines of
bctx := context.WithValue(ctx.NetContext, "BG", "3se334EFe")
for _, uid := range users {
    ctx.NetContext = context.WithValue(bctx, "ID", uid)
    engine.Run(id2eng, ctx)
}

Then the net/context would only be around for a single run of the id2 engine.
If what you have here works, then I'm ok with it.  I think I get confused reading diff with engine.Context and net/context.Context.

The identify2 engine adds its own ID2 tag internally.  I'll switch things around touhg.

this any better?

Yes, that is easier to understand (at least for me!)  thanks.

Cool, thanks for the the help.  This still is already too complicated due to all of the hacks.  Would be much easier to just pass Context's everywhere!

Yeah, unfortunately engine.Context predates net/context too.


fix failure

Fix(temp): console.log
broken dist
Fix: error handling

I'll try to rebase this (maybe) tomorrow. The last commit does not apply to my previous one for some reason. But it's too late now. I was trying to simplify your code a little bit and add error handling for 403, 404 and 422. Just to make it easier for people to see what's wrong.

Replaced by #449


Feature suggestion: Auto select the current word in "find in files" as it does in "find"

VSCode Version: 1.7.1
OS Version: Windows 10

Steps to Reproduce:

In the code editor click "Ctrl+F" to find in the file without having any selection
The in-line search automatically searches for the word where the cursor is placed. If you already have a selection, that is used for the search, so this is only the case if you don't have a selection.
Try the same with the "find in files" (Ctrl+Shift+F) - the same "auto selection" of the current word is not applied here - you have to make a selection before opening the "find in files".

In Visual Studio both Find and Find In Files have the auto-selection behavior.

#17974


Protobuf 22.x experiments

Protobuf upgrade was merged here: https://github.com/grpc/grpc/pull/32606


Type Unknown must have Symbol.iterator Context API

New to Solidjs and relatively new to TypeScript. I'm following the tutorial and encountered this error when trying to use the Context API. The same error is showing up in my local IDE.

It looks like the Value prop of the <Context.Provider> component has a type of unknown.

Not the best at TS or Solid for the matter.
First, it's important that Typescript "error" are really just warning, your counter should still work even if the REPL return Typescript error as there are stripped down when compiling (unless you activate the strict mode).
Here how I manage to deal with the warning/error.
https://playground.solidjs.com/?hash=1737220061&version=1.0.0
We need to tell Typescript what our Context value will look like, so it can understand it.
We can do that by specifying a type in useContext (cf. the like to the playground in the file counter.tsx).
Once Typescript understand what useCounter is returning, you should be good to go.
If you have question in the future, try to open a discussion in https://github.com/solidjs/solid/discussions as I think issues are meant for codebase related matter


Add infrastructure for S2 backend

For the obvious reason, it includes #29 :)
I created it now to speed up everything, you will not need to wait for me to create the next PR.
Soooo, after emerging #29, please review this PR.

I have added the cloudflare api tokens as vars to the workspaces so it should be good to go on merge.


Add logging utility for agent

The commit adds a logging utility to Zambeze agent as requested in #127. This allows using head/tail modes with numlines.
For example:
zambeze logs
zambeze logs --mode=head
zambeze logs --mode=tail --numlines=20

Defaults to tail mode with 10 lines. Doesn't support negative integers, which results in no lines logged.
This is tested with a 1G text file and the utility attempts to efficiently head/tail logs.

The docstring for the logs(mode, num_lines) function is incomplete. It has two input parameters which are not defined in the docstring. Use the NumPy docstring style to define the parameters.

I have added docstring for the log method. As I was trying to debug a few other things, I thought it would be useful to have a follow feature on the tail.
I added the follow segment on the update as well and it has been tested.

May I ask why you want to contribute to this project? Are you using zambeze for work or for a personal project? You recently joined GitHub, you don't have any other repositories on here, and your profile doesn't say anything about yourself. This just seems odd to me. Your contributions are welcome, but I'm curious as to why you would want to contribute to this particular project.

It would be helpful to add some documentation on how to use these features. Can you add a documentation page at docs/source/get-started/logging.rst that describes these logging commands? You can use the comments you posted in this pull request for the documentation.

@flourishingtune I'm not sure why the pytest and ruff checks are waiting for status reports. I updated the GitHub Actions workflows on the main branch to run on push and pull request events. Can you update your fork/branch and see if this enables the checks to run?

@wigging
I setup this profile mostly out of personal interests and wanting to contribute to open projects in my leisure time. I have been developing an orchestrated system myself with my other personal/work account and thought it would be nice to get my hands dirty on similar projects. Mostly just utilizing my leisure time.
I have updated the branch with the documentation page for logging. Seems like the checks are running now.
Sorry I may be a bit late to respond/work on things :)

@sankalpatimilsina12 Thank you for the response. I suggest you use your sankalpatimilsina12 profile for making contributions so they show up on your main profile. The flourishingtune account looks suspicious since it has no commit history and nothing on the profile page. Anyway, thank you for the contribution. I'll merge it with the main branch.


Add Yospace configuration types to connector

The YospaceServerSideAdInsertionConfiguration is currently defined in the THEOplayer Web SDK, and imported by the Yospace connector. This is not ideal:

If the connector wanted to add or change the configuration interface, it would need a new THEOplayer release first.
Since we intend to deprecate (and eventually remove) the Yospace pre-integration shipped in THEOplayer itself, the configuration should be moved out of the Web SDK.

This PR adds the YospaceServerSideAdInsertionConfiguration type to the Yospace Connector itself. It is currently identical to the one shipped with THEOplayer, so customers won't need to change anything in their code. However, we highly recommend updating the imports in your code to use the connector's types, in preparation of a future removal from the Web SDK.

Can we / do we also need the ID3Yospace stuff over?

That's a little bit more difficult, since we actually have special logic for that in the ID3 parser of THEOplayer.
Maybe another time! 😅


flaw in https://api.covid19india.org/csv/latest/district_wise.csv

Hi,
There is apparently a flaw in the above mentioned file.
The data related to Andamans and Nicobar Islands has been unchanged since at least 1st July. The numbers are the same since. When crosschecked with other district level datafiles, this discrepancy was noticed.
Hope this will be checked and rectified at the earliest.
Regards

Andaman Nicobar Islands do not provide districtwise case details. We used to capture it till July 1st with whatever information we could gather from local media and tweets. However, as the case numbers increased and we did not have an anchor on how many cases are present in each district, we have stopped updating the district numbers for AN Islands.

Thanks for your prompt reply.
On Sat, 25 Jul, 2020, 12:20 am Sudev<EMAIL_ADDRESS>wrote:

Andaman Nicobar Islands do not provide districtwise case details. We used
to capture it till July 1st with whatever information we could gather from
local media and tweets. However, as the case numbers increased and we did
not have an anchor on how many cases are present in each district, we have
stopped updating the district numbers for AN Islands.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/covid19india/api/issues/403#issuecomment-663682161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6SA7PIG3TYXEOZZAZRUOLR5HJV5ANCNFSM4PG5GTFQ
.


Comments on Papyrus CX model elements are extremely difficult to read and edit

Issue and tracking information
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below
This is a critical blocker in the Papyrus CX tool which will prevent its use for defining new or modified architectures for an upcoming need. All documentation in IDL and Doxygen ICDs is generated from these comments, so they need to be easily readable and editable.
Comment documentation text fields on existing model elements, found in numerous Property pane locations and popup dialogs, are displayed as single lines of text that extend beyond the right edge of a text box, if longer than the text box width.  It is not possible to read comments longer than this width, or to edit them.  Advancing the cursor does not scroll the text, and no horizontal scrollbar is available.
A simple Word Wrap feature such as found in MS Windows Notepad would fix this issue and make comments on model elements readable and editable.

@J17359 I will work on this issue first as Issue #248 might take a little longer to figure out.

@J17359 I will work on this issue first as Issue #248 might take a little longer to figure out.

Agreed. #247 and #248 are much lower on the priority list (hence me not marking them as "ngc: approved to work" yet)

@J17359 Do you think adding a simple text area at the end of CX properties view would work?? I could not find a way to remove the existing Comments tab.

@J17359 Do you think adding a simple text area at the end of CX properties view would work?? I could not find a way to remove the existing Comments tab.

I think it's much better than before, but I think having the comments tab persist might cause user confusion. If this is the only thing we can do to provide them with a better interface for comments, I'm all for it. But would definitely prefer to avoid having them stumble onto the comments tab where this is not the case.

@J17359 Agreed. I think I can find a way to reuse the existing comment tab. I will let you know soon. Thanks

@J17359 As I was looking into actual code for UML comments I found out that the rich text editor was available through the preference page so I enabled it by default.
Please let me know if this works out, thanks.

@J17359 As I was looking into actual code for UML comments I found out that the rich text editor was available through the preference page so I enabled it by default.
Please let me know if this works out, thanks.

Thanks @ysroh ! I just built the latest CX RPM internally and will test today. I'll report back here after.

@ysroh - I've verified that this fix looks good during my testing. Before we close this issue, however, I'd like to demo this new functionality to the architect who asked for the fix to make sure it works for him. Once I verify that, I'll respond back here. Thanks again for the quick turnaround!


Dockerfile - Add suport for LABEL

@abtris looks like your test example should be changed.

Test fixed, but I'm not sure if possible eliminate problem if key after label contains label word too.

Thanks!


New version: Warzone2100Project.Warzone2100 version 4.3.5

Pull request has been created with Komac v1.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Installs and runs fine for me

@wingetbot run


RootAccessSpec is failing during PKI CI

[INFO] Running RootAccessSpec
Error:  Tests run: 32, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 17.327 s <<< FAILURE! - in RootAccessSpec
Error:  root user can manually report skill for a project they are not an admin of  Time elapsed: 0.716 s  <<< FAILURE!
java.lang.AssertionError: no certificate found for<EMAIL_ADDRESS>Expression: cert. Values: cert = null
	at skills.intTests.root.RootAccessSpec.root user can manually report skill for a project they are not an admin of(RootAccessSpec.groovy:537)

PR: #231


Question: relative path option from bower.json location

I've got a .bowerrc file which specifies my bower_components directory as public/lib, and I'm using the node API to get my files as normal.
However, the array of filepaths I'm getting back from wiredep().js and wiredep().css uses absolute paths from the root of my machine, e.g. /Users/Jason/git/my-project/public/lib/package-name/etc.
Is there a way to specify a relative path that wiredep should use?

To support my question, I tried the following (from just the node command line):
require('wiredep')({ cwd: './'}).js

which produces the same thing as above.
# and also,
require('wiredep')({ cwd: 'public/'}).js

which gives me an error because my bower.json file is not in public/. Would it be easier/better to move bower.json there?

Try:
require('wiredep')({
  cwd: './',
  ignorePath: __dirname + '/public'
});

That turn /Users/Jason/git/my-project/public/lib/package-name/etc into /lib/package-name/etc, which, if I understood your issue correctly, is what you're wanting?

I'm surprised it's giving back absolute paths at all. Doesn't it just give a relative path from source file (index.html) to injected file (some file in a bower package)?

@CWSpear thanks for the suggestion, but unfortunately the ignorePath option is not doing what I would like. Even with it set to ignorePath: /Users/Jason/git/my-project/ explicitly, I'm still getting the absolute path (/Users/Jason/git/my-project/public/lib/some-bower-package/files.js).
I need the paths to come back like this: public/lib/some-bower-package/files.js, which is the path from where the bower.json is located.
The .map solution is what I've ended up leaving as a //TODO: for now.

Like @stephenplusplus said, it is odd that it's the full path. Something else weird is maybe going on? Anyway, that .map solution should be perfectly suitable.

I'm encountering the same issue on Windows. I could use the map function, but it is really not optimal.

@sabrehagen Why is it not optimal? What would be optimal?

Sorry, my last comment was dumb; I thought this was a different issue.
Anyway, @sabrehagen, are you also using .bowerrc? There may be an issue with the way it creates the paths if you are using a path from .bowerrc...

Ok, after digging in the code: it looks like this method has always functioned this way.
And the more I think about it and look at how I use it, and how I've heard other people use it, it's meant to give you the full paths. That way, you can do whatever you want outside of the default wiredep toolchain, and it's usually better to have the full path, and it's easier remove part of a path than add part of one.
So I would argue that using .map is the solution here.
@sabrehagen, @JaKXz If I may ask, what is it you're trying to do that you're using wiredep().js, exactly? (It's perfectly legit to do so, I'm just curious as to why and maybe we can find a better overall solution...?)

@CWSpear I would honestly love it if there was a relativePath option. I'm using wiredep to specify my "lib" files and then using grunt-injector get my app files together. The build process is based on relative paths from the Gruntfile, so it would be awesome if wiredep was consistent with that, rather than having to do the map manually.
Of course, I think it's only worth implementing in wiredep if you guys are not just doing the map behind the scenes. I haven't explored the source enough to know how you're building paths, but I think building paths from the location of the .bowerrc is a reasonable solution for the relativePath option.

I also tried using process.cwd() in the ignorePath option with no luck.

Right, so what happens is that wiredep more or less gets a list of files from the same thing wiredep().js does, and then when it injects them, it looks at all the things like cwd and ignorePath. Those transformations aren't applied in what is exposed with the wiredep().js.
We could change it to be add those transformations, but it would be a breaking change as others could (and do) rely on the current functionality.
I do something similar in my build, but I use gulp, so using a map would be trivial since gulp is just working with files and not massive configs. In my case, gulp.src "relative-izes" the file path for me, so I don't actually have to do that.
Have you tried grunt-injector's ignorePath option?

One thing I've noticed is that bower's api lists files w/ relative paths by default from bower.json. Perhaps for the relativePath option wiredep could walk through the object it returns and filter based on the overrides?

@CWSpear We're using wiredep().js to build a list of our bower packages that we then inject into our grunt watcher and subsequently index.html. grunt-wiredep wasn't able to solve our needs, we we're using wiredep directly.

But to answer your question, @CWSpear, I haven't tried grunt-injector's ignorePath option.

Furthermore, I need to normalise my paths for use in the map function as node reports __dirname as 'c:\repositories\stemn\ but wiredep reports 'C:\repositories\stemn\etc...'

Is this still an issue? If so, I'll reopen

I Found this to still be an issue. My fixes included.
Changing the .bowerrc file as follow
{
  "directory": "./app/bower_components"
}

This results in the bower components living in the app dir with the rest of the index.html and files.  The local server can now see the files.
I also had to change the $.useref.assets().restore() as  discussed.
The bower method in the gulpfile.js now looks like:
// inject bower components
gulp.task('bower', function () {
  return gulp.src(paths.views.main)
    .pipe(wiredep({
      directory: yeoman.app + '/bower_components',
      ignorePath: '..'
    }))
  .pipe(gulp.dest(yeoman.app));
});

This all seems to now work fine in the browser.  I've not tested prod environments etc.. though..
one more note I had issues with the server and ports on windows so that was changed to...
gulp.task('start:client', ['start:server', 'styles'], function () {
  openURL('http://localhost:9002');
});

gulp.task('start:server', function() {
  $.connect.server({
    root: [yeoman.app, '.tmp'],
    livereload: true,
    // Change this to '<IP_ADDRESS>' to access the server from outside.
    port: 9002,
    hostname: 'localhost',
  });
});`

Just in case anybody else gets the Error: listen EACCES <IP_ADDRESS>:9000

@JaKXz I would like also to do the mapping of the file path, may I know how to accomplish the same thing of the hack map in pipe?
I have tried the following but seems not working:
.pipe(wiredep({
      ignorePath: /^(\.\.\/)+/
    }).js.map(path){
      return path.replace("from something", "to something")
   })
...


Using Lens Space in private enviroment

Hi, I want use Lens Space in private env of my company.
So, do you have support for us to self-register and self-manage Lens Space accounts?
Thanks for watching

I would recommend asking via<EMAIL_ADDRESS>


Style Single Tail Page

Single Tail page is going to need some styling.

styled and has basic responsiveness


Keyboard shortcut ALT + Up arrow to move up one folder

What's the Problem?
There seems to be no keyboard shortcut for going up one folder. On many file managers this is ALT + Up arrow.
Solution/Idea
Add ALT+Up arrow shortcut for going up one folder.
Alternatively make keyboard shortcuts customisable and add folder up as an action.
Alternatives
The only alternative I can see is to use the breadcrumbs bar at the top. But I would prefer to use the keyboard.
Priorities

Capability
Priority

Add Folder up keyboard shortcut action
Must

Add keyboard shortcut ALT+Up arrow for folder up
Should

Files Version
No response
Windows Version
No response
Comments
No response

Alt + up is supported in v2.3


Laravel 9 - TailwindCSS 3 - change theme does not  work

Hi! 👋
Firstly, thanks for your work on this project! 🙂
used your package in laravel 9 but i cannot change the theme, i've changed the way you get the highlight.js's styles path
Here is the diff that solved my problem:
diff --git a/node_modules/tailwind-highlightjs/src/utils.js b/node_modules/tailwind-highlightjs/src/utils.js
index bd21658..d8972fc 100644
--- a/node_modules/tailwind-highlightjs/src/utils.js
+++ b/node_modules/tailwind-highlightjs/src/utils.js
@@ -74,8 +74,8 @@ function isThemeOfficial(theme) {
 }

 function getOfficialTheme(theme) {
-  const themePath = path.resolve(
-    `${__dirname}/../node_modules/highlight.js/styles/${theme}.css`,
+  const themePath = path.join(
+    __dirname, "../..", `highlight.js/styles/${theme}.css`,
   );
   const themeContents = fs.readFileSync(themePath, 'utf8');

yes, that fixed the problem! Thanks @notwarp

we should ask the maintainer to merge the branch for permanently have a fix

Sorry I haven't had a chance to look at this yet. It's on the list for this afternoon now. Thanks for being patient.

Fixed in v2.0.1

Thanks @GeoffSelby


Please include instructions for install

Hi! Could you please add your intended instruction for install here? When we do just a go get, the submodule isn't included. E.g.,
/home/vscode/go/pkg/mod/github.com/archspec/archspec-go@v0.0.0-20231117085542-f806bb25b479/archspec/static.go:5:12: pattern json/cpu: no matching files found
make: *** [Makefile:23: flex] Error 1

My temporary fix was to cd to the install location and manually clone, but it would be best if there was a way this could work out of the box (and something added to go.mod). Thanks!

Thank you @alalazo! I should be good for early development, but would be great to have a suggested solution in place after that.


[FR] Smart deprecation of SHA-1 signatures

Current behavior

Is there a current behavior that the feature relates to?

Yes, DNSSEC verifies names signed by algorithm 5 or 7 by default. It is possible to disable validation on build-time for all names. Our engineers prepared system-wide policy, which attempts to enforce RFC 9155 and refuse SHA-1 as valid signature algorithm. Sure, it clashes with RFC 8624, which in turn requires RSASHA-1 to be enabled. Our crypto team made change to OpenSSL policy, which refuses RSASHA-1 signatures verification by default. That would break any RSASHA-1 domains resolution.
Current possible mode is to always disable SHA-1 at build time or leave it enabled. But this behaviour depends on runtime changes to the system.

If yes, would you wish the current behavior to change?

It seems current way is to check algorithm support before validation starts. In our case, it would be better to leave algorithm support check on OpenSSL library. Problem is there does not seems to be any public API, where it may indicate before validation that RSASHA-1 is not available in runtime.
Describe the desired feature
I would like unbound to be able to fall back from secure handling of signature in verify_canonrrset function to insecure record, if EVP_VerifyFinal() returns code indicating used digest function is not acceptable. I would like possiblity to make the record insecure, without ad flag. But avoid SERVFAIL status code and provide result just like the record were not signed at all. It seems some EVP error codes might indicate there is nothing wrong with signature itself, but it is not available due to policy. There seems no alternative
Potential use-case
RHEL9 and CentOS Stream 9 will make EVP_VerifyFinal() fail in crypto-policy DEFAULT mode. But if its mode is changed runtime by administrator to DEFAULT:SHA1, it makes EVP_VerifyFinal() pass even on RSASHA-1 signatures. I would like single binary build to handle both modes.

if SHA1 is disabled, produce INSECURE results without ad bit
if SHA1 is enabled, produce SECURE results with ad bit set
avoid SERVFAIL status if verification failure is related to system-wide policy, not wrong hash or bad key

It will fail EVP_DigestVerifyInit() on unbound, when used key is SHA-1 algorithm.


Mark down - Link is not underlined, heading text is not bold

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.77-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Chat Report View
Action Performed:

Go to staging.new.expensify.com
Go to chat.
Send a link (google.com).
Send a heading markdown.

Expected Result:
Link will be underlined.
Heading text will be bold.
Actual Result:
Link is not underlined.
Heading text is not bold.
Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/7597f25b-2621-47d4-81ff-d08126a5a2dc
View all open jobs on GitHub

I'm suspicious of the changes to react-native-render-html or react-native-live-markdown but haven't done any testing yet, will undertake that now.

Alright confirmed it's the react-native-render-html change.
PR: https://github.com/Expensify/App/pull/52917
With PR merged to main, testing locally:

After stopping the dev server and reverting the PR I did:
rm -rf node_modules/
npm i
npm run web

With PR reverted, testing locally:

So I'll open a revert PR, I think that's the best thing to do to unblock deploy.

Updated revert PR since we had 2 open: https://github.com/Expensify/App/pull/54309
Once it's on staging I'll double check the issue is gone and close this out

PR has been CP'ed, and I verified the result in staging:

Closing!


Creation of a Graph Model, PKI helper object, and a Graph Plugin

This pull request includes the following:

A Graph Model and Optimization using the Ford-Fulkerson Algorithm
A PKI Model to assist the graph model. This class was created to ease the process of updating room counts and enabling/disabling nodes.
A Graph Plugin

I forgot to mention. Since Oracle will be using the paths, it might be easier to label the nodes as their room ids rather than s1, s2, ... etc. The data coming from the seer will have room numbers I think.


is this project dead?

Description
PRs are being closed as "stale" but the issues they resolve are much needed! This discourages contribution.
Please open up the project to more maintainers!
https://github.com/gobuffalo/pop/pull/823
To Reproduce
No response
Additional Context

Details

Paste the output of `buffalo info` here!

@sio4 Any updates? We're forking soon because there's a ton of issues we need fixed ASAP.

This is infuriating. @sio4 can you please remove this bot that closes issues!


[SPARK][K8S] Support auto build Kubernetes client when Kyuubi running in Pod

Why are the changes needed?

Add util object KubernetesUtils help kyuubi build kubernetes client in spark way.
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Codecov Report

Merging #3663 (e7f9ec0) into master (9d0b690) will decrease coverage by 0.05%.
The diff coverage is 34.00%.

:exclamation: Current head e7f9ec0 differs from pull request most recent head a7f0b55. Consider uploading reports for the commit a7f0b55 to get more accurate results

@@             Coverage Diff              @@
##             master    #3663      +/-   ##
============================================
- Coverage     52.02%   51.96%   -0.06%
  Complexity       13       13
============================================
  Files           485      486       +1
  Lines         27202    27238      +36
  Branches       3793     3795       +2
============================================
+ Hits          14151    14155       +4
- Misses        11685    11712      +27
- Partials       1366     1371       +5

Impacted Files
Coverage Δ

...ain/scala/org/apache/kyuubi/util/ThreadUtils.scala
86.11% <0.00%> (-5.07%)
:arrow_down:

...scala/org/apache/kyuubi/util/KubernetesUtils.scala
12.50% <12.50%> (ø)

...kyuubi/engine/KubernetesApplicationOperation.scala
18.03% <57.14%> (+5.53%)
:arrow_up:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
97.35% <100.00%> (+0.01%)
:arrow_up:

...ache/kyuubi/operation/KyuubiOperationManager.scala
79.45% <0.00%> (-2.74%)
:arrow_down:

...rg/apache/kyuubi/ctl/cmd/log/LogBatchCommand.scala
80.00% <0.00%> (-2.00%)
:arrow_down:

...mon/src/main/scala/org/apache/kyuubi/Logging.scala
52.63% <0.00%> (-1.32%)
:arrow_down:

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
72.26% <0.00%> (-0.85%)
:arrow_down:

...yuubi/server/metadata/jdbc/JDBCMetadataStore.scala
89.27% <0.00%> (-0.70%)
:arrow_down:

...n/scala/org/apache/kyuubi/engine/ProcBuilder.scala
80.74% <0.00%> (-0.63%)
:arrow_down:

... and 4 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I try my best to understand what you are trying to say about this PR in the PR desc, but failed

I try my best to understand what you are trying to say about this PR in the PR desc, but failed

This pr aims to add util object KubernetesUtils help kyuubi build kubernetes client in spark way.

refactor only change?

The PR description is updated and should cover the changes in the PR.
Thanks, merging to master

The CI failure caused by known flaky tests


Problems with parallelization within a batch using const token

Hello Again,
So I've been trying to get the parallelization working for this, and when I set n_cores_batch = 2 in the config.json file it keeps giving me the error below.  I'm not sure what is causing this issue, and it persists with any other value for n_cores_batch other than 1.   Do you have any insight into why this might be?
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/home/software/anaconda/3/envs/dso-sw/lib/python3.7/multiprocessing/pool.py", line 121, in worker
    result = (True, func(*args, **kwds))
  File "/home/software/anaconda/3/envs/dso-sw/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/nas0/tluchko/sandbox/deep-symbolic-optimization/dso/dso/train.py", line 28, in work
    optimized_constants = p.optimize()
  File "/nas0/tluchko/sandbox/deep-symbolic-optimization/dso/dso/program.py", line 393, in optimize
    optimized_constants = Program.const_optimizer(f, x0)
TypeError: 'NoneType' object is not callable
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "rundso.py", line 9, in <module>
    model.train()
  File "/nas0/tluchko/sandbox/deep-symbolic-optimization/dso/dso/core.py", line 90, in train
    **self.config_training))
  File "/nas0/tluchko/sandbox/deep-symbolic-optimization/dso/dso/train.py", line 278, in learn
    results = pool.map(work, programs_to_optimize)
  File "/home/software/anaconda/3/envs/dso-sw/lib/python3.7/multiprocessing/pool.py", line 268, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/home/software/anaconda/3/envs/dso-sw/lib/python3.7/multiprocessing/pool.py", line 657, in get
    raise self._value
TypeError: 'NoneType' object is not callable

Hi @Sean-Reilly , can you send me the full config you're using and the method to run (CLI vs Python interface)?

I tried in both CLI and Python interface and got the same error as above.  Below is the full config.json of a failed run.
{
   "experiment": {
      "logdir": "./log",
      "seed": 0,
      "timestamp": "2021-08-18-142149",
      "task_name": "~_nas_rism-symbolic-regression_dso_data_hs_dens_0.1",
      "save_path": "./log/~_nas_rism-symbolic-regression_dso_data_hs_dens_0.1_2021-08-18-142149"
   },
   "task": {
      "task_type": "regression",
      "dataset": "~/nas/rism-symbolic-regression/dso/data/hs_dens_0.1.csv",
      "function_set": [
         "add",
         "mul",
         "div",
         "sub",
         "const"
      ],
      "metric": "inv_nrmse",
      "metric_params": [
         1.0
      ],
      "extra_metric_test": null,
      "extra_metric_test_params": [],
      "threshold": 1e-20,
      "protected": false,
      "reward_noise": 0.0,
      "reward_noise_type": "r",
      "normalize_variance": false
   },
   "training": {
      "n_epochs": null,
      "n_samples": 100000,
      "batch_size": 100,
      "epsilon": 0.05,
      "baseline": "R_e",
      "alpha": 0.5,
      "b_jumpstart": false,
      "n_cores_batch": 4,
      "complexity": "token",
      "const_optimizer": "scipy",
      "const_params": {},
      "verbose": true,
      "debug": 0,
      "early_stopping": true,
      "hof": 5,
      "use_memory": false,
      "memory_capacity": 1000.0,
      "warm_start": null,
      "memory_threshold": null,
      "save_all_epoch": false,
      "save_summary": false,
      "save_positional_entropy": false,
      "save_pareto_front": true,
      "save_cache": false,
      "save_cache_r_min": 0.9,
      "save_freq": 1,
      "runs": 100
   },
   "controller": {
     "max_length": 30,
      "cell": "lstm",
      "num_layers": 1,
      "num_units": 32,
      "initializer": "zeros",
      "embedding": false,
      "embedding_size": 8,
      "learning_rate": 0.0005,
      "optimizer": "adam",
      "observe_action": false,
      "observe_parent": true,
      "observe_sibling": true,
      "entropy_weight": 0.03,
      "entropy_gamma": 0.7,
      "ppo": false,
      "ppo_clip_ratio": 0.2,
      "ppo_n_iters": 10,
      "ppo_n_mb": 4,
      "pqt": false,
      "pqt_k": 10,
      "pqt_batch_size": 1,
      "pqt_weight": 200.0,
      "pqt_use_pg": false,
      "summary": false
   },
   "prior": {
      "relational": {
         "targets": [],
         "effectors": [],
         "relationship": null
      },
      "length": {
         "min_": 4,
         "max_": 30
      },
      "repeat": {
         "tokens": "const",
         "min_": null,
         "max_": 3
      },
      "inverse": {},
      "trig": {},
      "const": {},
      "no_inputs": {},
      "uniform_arity": {},
      "soft_length": {
         "loc": 10,
         "scale": 5
      },
      "language_model": {
         "weight": null
      }
   },
   "postprocess": {
      "show_count": 5,
      "save_plots": true
   }
}

Hi @Sean-Reilly , thanks for the config! I am able to reproduce the bug. Looks like an issue when using n_cores_batch > 1 and the const token. I can reproduce the bug with a simplified config:
{
"task" : {
    "function_set" : ["add", "mul", "div", "sub", "const"]
},
"training" : {
        "n_samples" : 100,
        "batch_size" : 10,
        "n_cores_batch" : 2
    }
}

I will look into this and report back! Thanks.

Hi @Sean-Reilly, as a temporary hack, you can add pool = None in train.py at the beginning of the learn() function. That will break some other use cases (namely, the control task when using PyBullet envs), but should be just fine for regression.
A real fix will be incoming.

This should be fixed in the newest release.


added dark mode to the download button

now it changes its design as we switch to dark mode.
like this

@itsmanojthapa  Amazing work.🌟
Thanks for your Contribution. 🤩
Star the repo.


Gauges + start_http_server Windows 10, Python 3.6 never updates value after initial set

I'm trying to call .set on some Gauge objects every so often, and I've noticed all the values are correct when start_http_server initially runs, but they never update past that. Am I missing something or is this a bug? Here's the relevant code...
def process_request(gauges, plugs):
    plug_levels = get_plug_levels(plugs)
    for gauge, level in zip(gauges, plug_levels):
        gauge.set(level)
gauge_ids = [...]
gauge_names = [...]
PLUG_GAUGES = [Gauge(gauge_id, gauge_name) for gauge_id, gauge_name in zip(gauge_ids, gauge_names)]

port = 9001
logging.info('Starting HTTP server on port {0}.'.format(port))
# Start up the server to expose the metrics.
start_http_server(port)

update_interval = 5000
logging.info('Executing data pull at intervals of {0}ms.'.format(update_interval))
# Generate some requests.
while True:
    process_request(PLUG_GAUGES, all_plugs)
    time.sleep(update_interval)

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Fix builds by checking out submodules

Fixes #56.

Builds are still running for 3 minutes now: https://github.com/3rdparty/eventuals-grpc/runs/4695374734?check_suite_focus=true https://github.com/3rdparty/eventuals-grpc/runs/4695374736?check_suite_focus=true
But gosh do they look fixed, since they're not failing after 4s with "No WORKSPACE file found" errors like in https://github.com/3rdparty/eventuals-grpc/runs/4608427962?check_suite_focus=true
So I suspect this fixes things.

Builds are still running for 3 minutes now: https://github.com/3rdparty/eventuals-grpc/runs/4695374734?check_suite_focus=true https://github.com/3rdparty/eventuals-grpc/runs/4695374736?check_suite_focus=true
But gosh do they look fixed, since they're not failing after 4s with "No WORKSPACE file found" errors like in https://github.com/3rdparty/eventuals-grpc/runs/4608427962?check_suite_focus=true
So I suspect this fixes things.

Confirmed that this fixes builds, since the ubuntu build & test has finished building: https://github.com/3rdparty/eventuals-grpc/runs/4695374736?check_suite_focus=true (ubuntu tests are still running, and mac build is still running: https://github.com/3rdparty/eventuals-grpc/runs/4695374734?check_suite_focus=true )

@while-false could you please remove the old check_code_format action to be able to merge this PR?

Formatting Check

@while-false could you please remove the old check_code_format action to be able to merge this PR?

Arthur, can you say more about this? Do we need to delete https://github.com/3rdparty/eventuals-grpc/blob/main/.github/workflows/check_format_code.yml ? You mention it's an old check: is there something newer that replaces it, like https://github.com/3rdparty/eventuals-grpc/blob/main/tools/pre-commit ? If so, how does that get run?
(Gorm's out this week so I can try to send out more fixes, or we can bundle everything into this PR to make it a "get things working" generic fix)

Formatting Check

@while-false could you please remove the old check_code_format action to be able to merge this PR?

Arthur, can you say more about this? Do we need to delete https://github.com/3rdparty/eventuals-grpc/blob/main/.github/workflows/check_format_code.yml ? You mention it's an old check: is there something newer that replaces it, like https://github.com/3rdparty/eventuals-grpc/blob/main/tools/pre-commit ? If so, how does that get run?
(Gorm's out this week so I can try to send out more fixes, or we can bundle everything into this PR to make it a "get things working" generic fix)

I just filed https://github.com/3rdparty/eventuals-grpc/issues/59 to discuss the format check being seemingly broken: let's discuss there.

Formatting Check

@while-false could you please remove the old check_code_format action to be able to merge this PR?

Arthur, can you say more about this? Do we need to delete https://github.com/3rdparty/eventuals-grpc/blob/main/.github/workflows/check_format_code.yml ? You mention it's an old check: is there something newer that replaces it, like https://github.com/3rdparty/eventuals-grpc/blob/main/tools/pre-commit ? If so, how does that get run?
(Gorm's out this week so I can try to send out more fixes, or we can bundle everything into this PR to make it a "get things working" generic fix)

I just filed #59 to discuss the format check being seemingly broken: let's discuss there.

I think #59 is fixed now, so this PR should now auto-merge once this second round of builds completes (probably in ~30 minutes).

Formatting Check

@while-false could you please remove the old check_code_format action to be able to merge this PR?

Arthur, can you say more about this? Do we need to delete https://github.com/3rdparty/eventuals-grpc/blob/main/.github/workflows/check_format_code.yml ? You mention it's an old check: is there something newer that replaces it, like https://github.com/3rdparty/eventuals-grpc/blob/main/tools/pre-commit ? If so, how does that get run?
(Gorm's out this week so I can try to send out more fixes, or we can bundle everything into this PR to make it a "get things working" generic fix)

I just filed #59 to discuss the format check being seemingly broken: let's discuss there.

I think #59 is fixed now, so this PR should now auto-merge once this second round of builds completes (probably in ~30 minutes).

Wow, exactly! check_format_code is an unexisting action which never ends:) Since I have no permissions to update branch protection rules I asked Gorm:)
Anyway ty for dealing with this!


WIP: debug tput messages

Trying to diagnose these tput messages https://ci.appveyor.com/project/daskdev/dask/build/1.0.1397#L473 I wasn't able to reproduce on my windows VM.

This will be fixed by pandas 0.20.2 (releasing tomorrow). We'll just need to update the pandas version in appveyor.yml.


which is better between pmsignature and SomaticSignatures ??

Hi, author,
which way I should use , pmsignature  or  SomaticSignatures  ??
Expecting your answer!
Best wishes!

Which of the two approaches may be more suited for your analysis depends largely on the scientific question you are trying to address as well as the your data. As both software packages are also based on different methodological approaches, asking for the generally "better" seems not useful. I would suggest to read the manuscripts and have a look at the software documentation to understand the differences of both methods. This way, you will be able to decide what will be the more suited analysis approach for your research.


Fix issue #841 : style on features card

Issues Identification
Closes: #841
Description
Summary
A brief description of what this pull request does and why it is needed.
This pr will add style on feature cards.
Details
Include any detailed information about the changes in this pull request.
Types of Changes
Please check the boxes that apply

[x] Bugfix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes do not break the current system and pass all existing test cases
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Screenshots
If applicable, please attach screenshots of the changes made to the user interface.
https://github.com/user-attachments/assets/cbfd1093-1303-486e-8578-eef427f8c8e3
Additional Information
Please provide any other information that is relevant to this pull request.

Thank you


add example:docker easy-container-upload-data

This pull request related to task 16 create a new container and upload data to it easy-container-upload-data

Please run terraform fmt and remove empty lines for future commits.

sorry, I forget about it.


Calculate married couples allowance: 6th April ratings update for 2017-18

Trello card
Description
This PR contains rate update for next financial that affect married couples allowance.
Factcheck
Preview link
GOVUK
NB: RATES_QUERY_DATE: 2018-04-05 and Jenkins job for all regression tests
Expected changes

Married couples allowance:

maximum_married_couple_allowance: 8445
minimum_married_couple_allowance: 3260

Personal allowance:

income_limit_for_personal_allowances: 28000.0

Before

After

@leenagupte By Increasing the income from 27701 to 28001.. is an attempt to remove the old artefacts from the previous years, allowing the new income_within_limit_for_personal_allowance to be created first.. The context is within these two question whats_the_husbands_income? and whats_the_highest_earners_income ? See https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer_flows/calculate-married-couples-allowance.rb#L70

@ikennaokpala Can you update the commit to that effect? Something like, the personal allowance for income tax is increasing... To be able to see the effect that the change has I am updating earning amount to one that is over the current limit (2016-2017 tax year) but is below the new personal allowance that is coming into effect for the 2017-2018 tax year. If that is indeed what is happening?

@leelongmore 2a40543's commit not contains more

@ikennaokpala The commit title for 2a40543 is:
Preparatory: Update 2016-04-06 to 2017-04-06
What does this refer to?

@leenagupte I have updated the title 28eaf99


Add WMCore libraries to PYTHON27PATH - wmagent version

wmagent version of #8542 (even if the master branch is not the final fix)

 Fix #8543 - Add WMCore libraries to PYTHON27PATH - wmagent version


TST: Add test to verify GDAL detects zip archives

GeoPandas crossref
GDAL already detects ZIP archives without needing /vsizip/ or zip:// prefix.  This adds a test to demonstrate that.
This does not add Fiona's full parsing of URLs, which includes splitting on ! to separate out archive vs file within archive components; I don't have a good test string for that kind of path, and from Fiona #742 I'm not sure if we should support it.

Ah, I didn't know that GDAL does that (maybe only on recent versions?)
But, testing it locally, it also doesn't seem to work in general, so it would be good to understand the exact limitations.
For example, reading a zipped shapefile does not seem to work naively:
>>> df = pyogrio.read_dataframe(geopandas.datasets.get_path("naturalearth_lowres"))
>>> pyogrio.write_dataframe(df, "test_zipped_shapefile.shp", driver="ESRI Shapefile")
# zip the written files manually, try to read back
>>> pyogrio.read_dataframe("test_zipped_shapefile.zip")
...
DataSourceError: 'test_zipped_shapefile.zip' not recognized as a supported file format.
# rename extension of .zip to .shp.zip -> now it works ...
>>> pyogrio.read_dataframe("test_zipped_shapefile.shp.zip")
       pop_est      continent                      name iso_a3  gdp_md_est                                           geometry
0       920938        Oceania                      Fiji    FJI      8374.0  MULTIPOLYGON (((180.00000 -16.06713, 180.00000...
1     53950935         Africa                  Tanzania    TZA    150600.0  POLYGON ((33.90371 -0.95000, 34.07262 -1.05982...
...

So it seems that the file name (the part before the .zip extension) still matters.
Of course, if you know that, you can ensure this is done properly so it will read automatically. But at least for zipped shapefiles, this is not the name you get by default when zipping the different files together using your OS file manager (at least on ubuntu, it will by default give a name with just ".zip").

it would be good to understand the exact limitations

I'm not finding a lot of documentation on this, so it looks like I was hasty in assuming it worked.
I reworked the implementation so that we always attempt to parse paths and thus can auto-detect zip files in either the archive component (preceding !) or in full path.  I tried to add enough test cases to make sure that this works as expected, but it is possible there are still edge cases we aren't handling correctly.

@jorisvandenbossche any ideas on the Windows test failures?  I don't have a Windows machine to test the paths on, so I can't tell if it is because when we use the zip:// prefix that we have to reformat the path from \ to / for GDAL, or if it is some other issue.

Hmm, in geopandas.datasets.get_path, we also naively prepend "zip://", and AFAIK we never got issues about that not working on windows.
If needed, I can fire up my old windows laptop to diagnose.

Turned out the simplest solution was simply to prefix with zip:// then allow it to proceed with the rest of parsing, which sidesteps (I think) the issue with the windows drive letter.

Thanks a lot!


Higher CPU-usage after epoll implementation

The new epoll implementation introduced in rc110 increased the CPU-usage quite drastically (my horizontal pod autoscaler was running on max replicas). Reverting back to rc109 puts it back to normal again. Feels like a busy-loop somewhere.

Please try 111

kubectl top pod output
rc109:

rc111:

Can you explain the screenshots? I don't know much about kubectl output, sorry.

Sorry. 😁 The column with increased numbers is the CPU usage. As you can see there is a 15-20 times increase in CPU at rest. And my autoscaler has decided to scale up to 4 replicas instead of my regular 2.

Please try 112

Better but still a bit higher, about 10 times 109 now:

Numbers look like 109 or am I misinterpreting it?

109 is on 1m, 111 on 25-30m and 112 on 10-15m so still some way off I would say.

Oh, I was looking at Mi, is that Mibibytes memory usage? I have an idea how we can make it 1.

Correct, that's mem-usage. That's been quite constant.

Please test 113 and let me know if it looks fine.

That did the trick. Back down to 1 now. Thanks for quick resolution. ❤


AVRO-2676: Document that lang/py3 will be deprecated

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-2676
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No additional test, since it's a documentation fix. Instead, I ran ant in the doc directory and confirmed the documents were generated as expected.
Commits

[x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

@kojiromike Thanks! Updated the description.

Restarted the CI, seems like an unrelated issue


How might we improve user experience regardless of previous exposure to programming?

(Based on some of the feedback I've gotten so far.)
Idea 1:
Give a code example to set expectations?
Right when a user "opens" the app, set expectations by showing an example of code?
(So change the intro?)
For Example:
Hi! This is Code Tutor.

Here's an example of what you can make:

let greeting = "hi there ";
let name = "someone";
let message = greeting + name;
if (name == "someone")
  say("What's your name?");
for (let i=0; i<3; i++)
  say(message);

Voiceover:
Hi! This is Code Tutor. Here's an example of what you can make:
Let greeting equal hi there.
Let name equal someone.
Let message equal greeting plus name.
If name equals someone, then say what's your name.
And then, while counting from 0, and stopping before 3, say message.

Idea 2:
Suggest the sandbox feature earlier in the conversation flows?

For Idea 1:
It could make use of the example code I've already been working on. I just changed the welcome message so the user can ask for the example (instead of overwhelming them):
You can talk to me to create simple code. I can teach you about variables, arrays, strings, and loops. What would you like to create first? For example, you can say "a variable". Or I can give you an example.

And "sandbox feature" for more advanced users: https://github.com/hchiam/code-tutor/commit/a4a0d2c87ec3aa2bab799656df606c37754142eb

Need to test. Reopen if need to revisit.


two times loading issue

run your project and refresh this url "http://localhost:65060/users". its loading two times (server side and client side). how to avoid the second time loading?

I've been swamped but I'll be posting the cache transfer story / example shortly. Apologies for the delay

I see that as a feature :)
What I am doing is heavily caching prerendering output.
So users get little stale data very fast and app then grabs fresh data using ajax and updates it.
Works great for me!

Not typically, but it always just depends on your Application, whether it's very dynamic in nature, or static etc.
Typically I only put those most important GET Http calls in HttpTransfer logic that reuses them on the client again, just to remove any flicker etc. if calls are very data intensive and take a long Ike to return the result I usually ignore them all together on the server render, and let the client take its time to run them.
Always a million ways you could do any of this stuff right 🙈
I have the working HttpTransfer service/module and Transfer mechanism finished as of last night, just double checking everything and I'll try to get in pushed up to Master this morning. 🎈