output of predict_proba() and objective= binary:logistic

hi i would put this in : https://discuss.xgboost.ai but it is quite unresponsive.
i have a binary classification problem so i am using xgbclassifier. i set the objective function to binary:logistic. Therefore when i employ: predict.proba(x_test) are these probabilites or scores??

The output of predict_proba() is probability. However, see https://scikit-learn.org/stable/modules/calibration.html about calibrating the model for accurate probability estimates.

The output of predict_proba() is probability. However, see https://scikit-learn.org/stable/modules/calibration.html about calibrating the model for accurate probability estimates.

But I got soemthing bigger than 1 , this doesn't seem to be probabilites


A few documentation changes

I don't see the IOW acronym enough to know what it means without
looking it up. I thought others might have the same issue so I
expanded it. In the same sentence I changed what I think was an
incorrect spelling of "whereas".
I changed the text describing the itmdump of accelerometer readings
to indicate that the actual output seen by the user if they run the
same code won't be exactly as seen here.

bors r+

Thanks :)


PadLocal: Could you send me a token for padlocal test

Please make sure you have read the Wechaty Puppet Service: PadLocal from Wechaty Official Website before you continue writting this issue.
Question
Could you send me a token for padlocal test

@chuckfu Please send an email to oxddoxdd#gmail.com, then we can send you token related material.


[AutoPR policyinsights/resource-manager] Microsoft.PolicyInsights/remediations 2019-07-01

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

(message created by the CI based on PR content)

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


Apply finding template raises javascript / 404 error

When JIRA is enabled, the integration test for applying a template to a finding is failing with a javascript error:
Clicking on the template
{'timestamp':<PHONE_NUMBER>090, 'level': 'SEVERE', 'message': 'http://localhost:8080/static/bootstrap/dist/js/bootstrap.js 1800 Failed to load resource: the server responded with a status of 404 (Not Found)', 'source': 'network'}
There was a SEVERE javascript error in the console, please check all steps fromt the current test to see where it happens
Currently there is no way to find out at which url the error happened.
FAIL
======================================================================
FAIL: test_apply_template_to_a_finding (__main__.FindingTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tests/Finding_unit_test.py", line 229, in test_apply_template_to_a_finding
    self.assertNoConsoleErrors()
  File "/home/travis/build/DefectDojo/django-DefectDojo/tests/base_test_class.py", line 208, in assertNoConsoleErrors
    self.assertNotEqual(entry['level'], 'SEVERE')
AssertionError: 'SEVERE' == 'SEVERE'

Bootstrap is trying to load a resources, but the server returns a 404 I haven't dived into it yet, but it doesn't happen on my own instance. Maybe if I used the same data as the integration tests test data.
For now we only run this specific integration test with JIRA turned off to not block any progress on the dev branch.

solved by #2403


collectd-data: we only need collectd.src - not collectd.out

Motivation for this change
collectd pulls in an unsupported (and insecure) Xen 4.10.
collectd-data is just a few data files needed by influxdb, so create this from
the collectd sources rather than the built output. This significantly limits the
dependencies and makes things work at least for influxdb for now.
Fixes #157543
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Cc @liketechnik


Update/Add [tool name]

Tool information

Tool name: Az (PowerShell Module)
Add or update? update
Desired version: 3.4.0
Approximate size:
If this is an add request:

Brief description of tool: AzSK tool requires Az dependency modules installed
URL for tool's homepage: https://github.com/azsk/DevOpsKit

Area for Triage:

Question, Bug, or Feature?:

Virtual environments affected

Windows Server 2016 R2
Windows Server 2019

Can this tool be installed during the build?
Install-Module Az -Repository PSGallery -RequiredVersion '3.4.0'
Are you willing to submit a PR?

Hello, @Garima-msft
We already have preinstalled Az 3.5.0 PowerShell module  on Windows Server 2016 and 2019 images.
Windows Server 2019 - https://github.com/actions/virtual-environments/blob/releases/win19/20200319/images/win/Windows2019-Readme.md
This version is saved but not installed Location: C:\Modules\az_3.5.0\Az\3.5.0\Az.psd1
Windows Server 2016 - https://github.com/actions/virtual-environments/blob/releases/win16/20200316/images/win/Windows2016-Readme.md
This version is saved but not installed Location: C:\Modules\az_3.5.0\Az\3.5.0\Az.psd1

Hello, @Garima-msft
This behavior is expected that we couldn't  pre-install all desired Az PowerShell module versions on images related due to significantly increase image size, building time, etc.

Can we remove old versions?
No. This can break existing customers who has written there scripts based on the old AzurePS commands and using that specific version in the task.

Can we change default versions?
There are breaking changes between V2.1.0 and V5.13.0, V6.13.1. There are many third party custom tasks that may have taken dependency on V2.1.0 which will break if we change the default version.

Feel free to open thread if you have any concerns.


Fix LLMM1 kernel

As per title.
The kernel is broken and yields wrong generation, for example with TP=2 & llama 2 7B. There are two main issues in the kernel:

Number of thread in a block is not a multiple of the warp size, although we use warp shuffle operations.
Indexing on the block of rows is wrong & indexing to load the weight matrix is wrong.

Example repro:
import torch
from transformers import AutoModelForCausalLM
# from gemv_ext import LLMM1
from vllm import _custom_C

m = 4096
n = 1

for k in range(200, 1600, 8):
    with torch.no_grad():

        down_proj_weight = torch.rand(m, k, device="cuda", dtype=torch.float16)
        inp = torch.rand(n, k, device="cuda", dtype=torch.float16) - 0.5

        out_functional = torch.nn.functional.linear(inp, down_proj_weight)

        out_custom = torch.empty(n, m, dtype=inp.dtype, device="cuda")
        _custom_C.LLMM1(down_proj_weight, inp, out_custom, 4)

        absdiff = (out_functional.to(torch.float32) - out_custom.to(torch.float32)).abs()

        print("------ k:", k)
        print("  % off:", absdiff.mean().item() / out_functional.abs().mean().item())

Thank you, I fixed the linting conflict.

Still have failing CI
Run codespell --toml pyproject.toml
./csrc/custom/custom_kernels.cu:88: accross ==> across
Error: Process completed with exit code 65.

@shajrawi thank you, should be fixed

Merged! Thanks for the fix!!


Bug: There's no error state for DatePicker component

Info
Reported by Alana (https://goa-dio.slack.com/archives/C02PLLT9HQ9/p1708104799434879)
Unlike the rest of our form components, there is no error state for the DatePicker component.
Acceptance Criteria:

An error state exists for the DatePicker component
Should probably follow our existing error state for our other text based form controls (goa-input, goa-textarea)

:tada: This issue has been resolved in version 1.17.0-alpha.43 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.17.0-alpha.22 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.20.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.20.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Portunus 6 4 0 release

Portunus 6.4.0 Release

All reviewed and waiting the go ahead to publish.


Proof of concept for #8504 (Expose requestedRemoteAddress in the Channel interface)

Expose requestedRemoteAddress in the Channel interface (improvement) #8504
Motivation:
Expose requestedRemoteAddress in the Channel interface (improvement) #8504
Modification:
Fixes #8504 .

@Andremoniy first of thanks for your effort. That said we can not do it (also I think it is not a good idea as it is very specific to client side) as we can not just add methods to the Channel interface without breaking people.
What we may could do (not sure if it is a good idea yet) is to include the remoteAddress in the exception so you can get it when you cast it.


Use versioned actions in stack CI

Problem statement
It appears that currently the most common cause of stacks CI failures is a failure to build docker images used by actions. The full output of an example failure is below, but in summary it appears to be a network-based flake when trying to download packages onto the image. We know it's flakey because the same steps will fail intermittently without modification to the dockerfiles used by the actions.

Example output from failed attempt to build docker image
Build container for action use: '/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset/Dockerfile'.
  /usr/bin/docker build -t 8d5581:2d7700d024ce4b7386c7eb4560b81615 -f "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset/Dockerfile" "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset"
  Sending build context to Docker daemon  7.168kB

  Step 1/4 : FROM alpine
  latest: Pulling from library/alpine
  ca7dd9ec2225: Pulling fs layer
  ca7dd9ec2225: Verifying Checksum
  ca7dd9ec2225: Download complete
  ca7dd9ec2225: Pull complete
  Digest: sha256:b95359c2505145f16c6aa384f9cc74eeff78eb36d308ca4fd902eeeb0a0b161b
  Status: Downloaded newer image for alpine:latest
   ---> bfe296a52501
  Step 2/4 : RUN apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*
   ---> Running in f7f5fad6815d
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/main: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/main: No such file or directory
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/community: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/community: No such file or directory
  ERROR: unable to select packages:
    bash (no such package):
      required by: world[bash]
    curl (no such package):
      required by: world[curl]
    git (no such package):
      required by: world[git]
    github-cli (no such package):
      required by: world[github-cli]
    jq (no such package):
      required by: world[jq]
  The command '/bin/sh -c apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*' returned a non-zero code: 5
  Warning: Docker build failed with exit code 5, back off 8.27 seconds before retry.
  /usr/bin/docker build -t 8d5581:2d7700d024ce4b7386c7eb4560b81615 -f "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset/Dockerfile" "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset"
  Sending build context to Docker daemon  7.168kB

  Step 1/4 : FROM alpine
   ---> bfe296a52501
  Step 2/4 : RUN apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*
   ---> Running in 5e92333feaec
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/main: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/main: No such file or directory
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/community: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/community: No such file or directory
  ERROR: unable to select packages:
    bash (no such package):
      required by: world[bash]
    curl (no such package):
      required by: world[curl]
    git (no such package):
      required by: world[git]
    github-cli (no such package):
      required by: world[github-cli]
    jq (no such package):
      required by: world[jq]
  The command '/bin/sh -c apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*' returned a non-zero code: 5
  Warning: Docker build failed with exit code 5, back off 7.292 seconds before retry.
  /usr/bin/docker build -t 8d5581:2d7700d024ce4b7386c7eb4560b81615 -f "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset/Dockerfile" "/home/runner/work/_actions/paketo-buildpacks/github-config/main/actions/release/find-asset"
  Sending build context to Docker daemon  7.168kB

  Step 1/4 : FROM alpine
   ---> bfe296a52501
  Step 2/4 : RUN apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*
   ---> Running in cd7ce404a73a
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz
  fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/main: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/main: No such file or directory
  ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.16/community: network error (check Internet connection and firewall)
  WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.16/community: No such file or directory
  ERROR: unable to select packages:
    bash (no such package):
      required by: world[bash]
    curl (no such package):
      required by: world[curl]
    git (no such package):
      required by: world[git]
    github-cli (no such package):
      required by: world[github-cli]
    jq (no such package):
      required by: world[jq]
  The command '/bin/sh -c apk add     bash     curl     git     github-cli     jq   && rm -rf /var/cache/apk/*' returned a non-zero code: 5
Error: Docker build failed with exit code 5

Proposal
I think we could eliminate this class of failures entirely if we tagged this repo and switched relevant workflow jobs to use docker images from that tag instead of main.
Specifically, we would update each of the actions in the stack create-release.yml workflow e.g.:
paketo-buildpacks/github-config/actions/release/find-and-download-asset@main
would become:
paketo-buildpacks/github-config/actions/release/find-and-download-asset@tag
I propose tagging this repo with both v0.1.0 and v0.1 and updating the actions to use v0.1. This will allow us to increment the patch version (and move the corresponding v0.1 tag) in the future without having to change the references in the workflows. If that seems overly complex, we can instead just use v0.1.0 in the workflows and skip the v0.1 tag entirely.
I also don't propose changing any actions in other workflows from main to a tag at this point. We can evaluate other jobs on a case-by-case basis.
As a side effect, switching to tags would also have a performance benefit as using a pre-built, cached, image is faster than building one every time.
Downsides
Using a cached image means that we will be using outdated packages/libraries.
Given that these docker images are only used to perform simple actions like finding and retrieving assets from GitHub releases, and they are only used for a short time in CI, I think the risk to security is minimal. We are unlikely to require features from newer packages for such simple tasks, but we can always increment the tag to rebuild the images if necessary.
Alternatives
We could explore whether switching away from alpine would improve reliability. However, without a more in-depth investigation, we can't say whether the issue is alpine specifically or if it is something common to other distributions (e.g. a networking issue within GitHub).

Could you explain a bit about how switching to a tag would fix the issue we're seeing? I'm not fully getting how that will prevent the flakiness we're seeing? I'm a little confused why the tag versioning is needed, versus just having a single tag. I think your answer to the first question will answer my second question though

Sure, so it's my understanding that if we tag the repo, and use that same tag in the workflow when we declare the action (e.g. paketo-buildpacks/github-config/actions/release/find-and-download-asset@v0.1.0), then GitHub actions will cache the image and re-use the cached image. Using a branch (i.e. main results)
The flakiness is in building the image, not using it, so if we can build it and cache it, it should eliminate the flakiness.
It's possible that my understanding is wrong, but I'd like to tag the repo and try it. Worst-case, GitHub actions doesn't behave this way, and it rebuilds the image every time. In which case we're no worse off than we are today, and we can revert to the main branch for the versions (and delete the tag on the repo).

Ah that makes sense. Definitely interested to see if you can test it out and see if your idea is right. That would be lovely if we could cut down on the flakes. Thanks for the explanation.
For point 2 - we don't cut releases of this repo so I don't fully understand how versioning is a concern I don't think. I understand that we'd probably have to add new tags to keep it up to date with main

Yeah, I'm just trying it out with a fixed SHA to test the theory.
I know we don't cut releases of this repo, but - assuming all of this caching works as I expect - we could make a new tag to invalidate the cache. We would do this if we wanted to force a rebuild to update packages, or if the actions themselves actually changed (e.g. we updated their logic)

Just as a note, I can see that some actions do not build every time (e.g. out use of setup-go). Instead of a step to build the action, I see the following logs:
Download action repository 'actions/setup-go@v3' (SHA:c4a742cab115ed795e34d4513e2cf7d472deb55f)

I think this might be because these actions are published.

Ok, so we are able to manually build images and push them to a registry, and GitHub will pull them rather than build them.
We do this by changing the action.yml from:
runs:
  using: 'docker'
  image: 'Dockerfile'

runs:
  using: 'docker'
  image: 'docker://my/prebuild-image:v1.2.3'

See this change on a WIP branch for an example. Also see the example CI run below - it pulls the image rather than rebuilding it.


status of m0_client remains offline after rgw restart

I was running 16MB-200Sessions-12KObjects s3bench from client on single node MGW. During this test I observed that I/O started failing. Then I restarted RGW with ../src/stop.sh and ../src/vstart.sh scripts. At this stage, hctl status started showing m0_client as offline. After this, I followed steps like

stopped RGW again with ../src/stop.sh
hctl shutdown, then
hctl bootstrap --mkfs singlenode.yaml
../src/vstart.sh
This brought back the m0_client online

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/EOS-27773. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

@rajeshdesh please verify this again and comment.

yes @vaibhavparatwar , not hitting this issue with latest builds of Cortx-RGW

Closing as per @rajeshdesh's verification.

Vaibhav Prakash Paratwar commented in Jira Server:

.

Vaibhav Prakash Paratwar commented in Jira Server:

.


Prevent child components loading numerous times

Core Library
@azure/msal-browser
Core Library Version
2.12.0
Wrapper Library
@azure/msal-react
Wrapper Library Version
1.0.0-beta.0
Description
Basically child components of <AuthenticatedTemplate> are being loaded multiple times which hits my API each time. I'm trying to prevent this so it only happens once.
MSAL Configuration
import { Configuration, RedirectRequest } from '@azure/msal-browser';

// Config object to be passed to Msal on creation
export const msalConfig: Configuration = {
  auth: {
    clientId: '<client_id>',
    authority: 'https://login.microsoftonline.com/<tenant_id>',
  },
};

// Add here scopes for id token to be used at MS Identity Platform endpoints.
export const loginRequest: RedirectRequest = {
  scopes: ['User.Read'],
};

// Add here the endpoints for MS Graph API services you would like to use.
export const graphConfig = {
  graphMeEndpoint: 'https://graph.microsoft.com/v1.0/me',
};

Relevant Code Snippets
import React from 'react';
import ReactDOM from 'react-dom';
import App from './components/App';
import { PublicClientApplication } from '@azure/msal-browser';
import { MsalProvider } from '@azure/msal-react';
import { msalConfig } from './utils/authConfig';

const msalInstance = new PublicClientApplication(msalConfig);

ReactDOM.render(
  <React.StrictMode>
    <MsalProvider instance={msalInstance}>
      <App />
    </MsalProvider>
  </React.StrictMode>,
  document.getElementById('root')
);

---

import React, { useEffect } from 'react';
import {
  AuthenticatedTemplate,
  useMsal,
  useAccount,
  useIsAuthenticated,
} from '@azure/msal-react';
import { graphConfig, loginRequest } from '../utils/authConfig';
import { InteractionStatus } from '@azure/msal-browser';
import axios from 'axios';

const Token = (props: any) => {
  if (props.account) {
    props.instance
      .acquireTokenSilent({
        ...loginRequest,
        account: props.account,
      })
      .then((response: any) => {
        axios
          .post('/api/v2/auth/aad_token/validate/', {
            access_token: response.accessToken,
            id_token: response.idToken,
            oid: response.uniqueId,
          })
          .then((response) => {
            console.log(response.data);
          })
          .catch((error) => {
            console.log(error);
          });
      });
  }
  return
Test
;
};

const App = () => {
  const isAuthenticated = useIsAuthenticated();
  const { instance, inProgress, accounts } = useMsal();
  const account = useAccount(accounts[0] || {});

  useEffect(() => {
    if (inProgress === InteractionStatus.None && !isAuthenticated) {
      instance.loginRedirect(loginRequest);
    }
  });

  return (

      <AuthenticatedTemplate>
        <Token account={account} instance={instance} />
      </AuthenticatedTemplate>

  );
};

export default App;

Identity Provider
Azure AD / MSA
Source
External (Customer)

I'm not too far into the implementation and have it pretty bear bones and not refactored (and not great coding practices).
This is an Admin portal that uses the company's Azure Active Directory to validate users as opposed to username/password, etc. The flow is this:

User navigates to /admin.
useEffect() starts checking if user isAuthenticated.
If not, they are automatically redirected to login.
Once they have logged in, or are verified as already being isAuthenticated, they can now access components that are children of <AuthenticatedTemplate>.

The only child component currently is <Token>, which for testing purposes, just prints out the JWT token returned from the API. Essentially what happens here is:

The accessToken, idToken, oid are automatically sent to my API for validation server-side as well.
When they are validated, the user is checked against the DB... if they exist, send a JWT... if not, add them and send a JWT.
JWT is saved to sessionStorage and is used subsequently for client-API communication.

The problem I'm running into my API is getting queried four or more times:

@jasonnutter Thanks for pointing those two things out.
I did remove the <React.StrictMode> for testing purposes and refactored the logic where the call to my API is, into a useEffect. This has reduced it down to two API calls:
const Token = () => {
  const { accounts, instance } = useMsal();
  const account = useAccount(accounts[0] || {});

  useEffect(() => {
    // Check if account object exists
    if (account) {
      // If it does then acquire an accessToken
      instance
        .acquireTokenSilent({
          ...loginRequest,
          account: account,
        })
        .then((response: any) => {
          axios
            .post('/api/v2/auth/aad_token/validate/', {
              access_token: response.accessToken,
              id_token: response.idToken,
              oid: response.uniqueId,
            })
            .then((response) => {
              console.log(response.data);
            })
            .catch((error) => {
              console.log(error);
            });
        });
    }
  });

  return
Test
;
};

I'm looking at a reactive implementation that somehow doesn't involve the user's interaction. I'd rather it be an automatic "you're signed in" or redirect to signin since having them click an additional button to sign just doesn't feel like a necessary step.

@cheslijones Can you try giving your useEffect an empty dependency array as per react docs?
This should ensure it's only called once per component mount whether or not you have Strict mode turned on.

That did the trick, I appreciate the help.


Link to GitHub Actions version of Supernote Crossword Automation

https://github.com/arichiv/supernote-nytc

Realized this was a fork, oops :-P


sodium not working

Describe the bug
php: '8.0'
extensions: sodium

Does not seem to install sodium, or at least, what it does install is not linked/compiled against the newest version, and is missing functions.
Version

[x] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[x] v2
[ ] v1

Runners

[x] GitHub Hosted
[ ] Self Hosted

Operating systems
Ubuntu 20.01
PHP versions
8.0
To Reproduce
Uncaught Error: Call to undefined function sodium_crypto_stream_xchacha20_xor()

Expected behavior

Screenshots/Logs

Additional context

Are you willing to submit a PR?

My bad. This function only exists on PHP 8.1.


Need example

Hello there,
could someone please make an example electron app with a native module?
For development and production please.
Thanks and kind regards,
Keyjin

https://github.com/amilajack/erb-sqlite-example/

holy smoke that was a fast response

i think this should be closed now


Added KMP Algorithm

C++ Implementation of KMP algorithm

In reference to Issue #43

Closes #43 🎉

Thank you for your contribution!


[Question] How to handle deleted / edited comments?

Hi. From what I understand this bot will make a commit adding a json file with the following info -
{
  "name": "ibakshay",
  "id": 2423423,
  "comment_id": 534534,
  "repoId": 5433,
  "pullRequestNo": 656,
  "createdAt": "2021-01-22T11:13:02Z"
}

How does this handle the case if the comment is later deleted by the user or edited and the older version is deleted?

Hi @vHanda,
Thank you for reaching out to us. Are you asking about the signature comment  from the contributor ?

Hi @vHanda,
Thank you for reaching out to us. Are you asking about the signature comment  from the contributor ?

Hi @ibakshay . Yes. I'm not sure how this works if the signature comment is deleted or edited.

Hi @ibakshay . Yes. I'm not sure how this works if the signature comment is deleted or edited.

It is a very good question. Unfortunately,  this bot doesn't handle this use case yet. So, the  CLA GitHub Action workflow won't be triggered If the signature comment from the contributor is deleted or edited. One thing a project admin can do is to directly check on the GitHub UI or with GitHub API If the signature comment is edited. However, that is not possible If the contributor deletes the signature comment. That is not a good sign.
That is definitely not a good sign. If you have any idea/thoughts on handling this edge case then feel free to pitch in :) .

It is a very good question. Unfortunately,  this bot doesn't handle this use case yet. So, the  CLA GitHub Action workflow won't be triggered If the signature comment from the contributor is deleted or edited. One thing a project admin can do is to directly check on the GitHub UI or with GitHub API If the signature comment is edited. However, that is not possible If the contributor deletes the signature comment. That is not a good sign.
That is definitely not a good sign. If you have any idea/thoughts on handling this edge case then feel free to pitch in :) .

There is a way to edit a comment and remove the older version. But I guess one would at least be able to see the edited time in that case.
Do you know how the normal cla-assistant handles this case?
--
One way to solve it could be to require the user to also post the digital signature (using pgp) in the comment. And requiring the user to have their public key on a pgp key-exchange server. Or maybe use something like keybase.
What worries me about all these solutions is that I don't know what is or isn't legally acceptable. Especially in different countries.

There is a way to edit a comment and remove the older version. But I guess one would at least be able to see the edited time in that case.
Do you know how the normal cla-assistant handles this case?
--
One way to solve it could be to require the user to also post the digital signature (using pgp) in the comment. And requiring the user to have their public key on a pgp key-exchange server. Or maybe use something like keybase.
What worries me about all these solutions is that I don't know what is or isn't legally acceptable. Especially in different countries.

Do you know how the normal cla-assistant handles this case?
In normal CLA instance, the contributors will be navigated to a seperate web page and contributors will sign with the click of a button.

One way to solve it could be to require the user to also post the digital signature (using pgp) in the comment. And requiring the user to have their public key on a pgp key-exchange server. Or maybe use something like keybase.

Sounds interesting to me. I will dig deeper into this topic to get further insights. The main idea of CLA assistant lite is to reduce the complexity and to keep things as simple as possible. So, we need to make sure it doesn't get complex.
Also, I forgot to mention before. This CLA assistant lite bot wil also automatically, by default, lock the pull request conversation soon after a pull request is merged.
So, the contributor won't be able to edit/delete the signature comments.

I think this feature answers your question to some extent.

Do you know how the normal cla-assistant handles this case?
In normal CLA instance, the contributors will be navigated to a seperate web page and contributors will sign with the click of a button.

One way to solve it could be to require the user to also post the digital signature (using pgp) in the comment. And requiring the user to have their public key on a pgp key-exchange server. Or maybe use something like keybase.

Sounds interesting to me. I will dig deeper into this topic to get further insights. The main idea of CLA assistant lite is to reduce the complexity and to keep things as simple as possible. So, we need to make sure it doesn't get complex.
Also, I forgot to mention before. This CLA assistant lite bot wil also automatically, by default, lock the pull request conversation soon after a pull request is merged.
So, the contributor won't be able to edit/delete the signature comments.

I think this feature answers your question to some extent.

I wonder if tying the signature to various IDs that may be gone in a few years could cause issues? Maybe that signature should contain the comment that was added by the user, for example:
{
	"name": "laurent22",
	"id": 1285584,
	"comment_id":<PHONE_NUMBER>,
	"created_at": "2022-12-21T16:54:13Z",
	"repoId": 79162682,
	"pullRequestNo": 7510,
	"comment": "I have read the CLA Document and I hereby sign the CLA"
}

So there'll be this "comment" field that will probably be the same for everybody, but then the whole thing will still be valid even if the pull request or repo is gone a few years from now.

So there'll be this "comment" field (that will probably be the same for everybody) and then the whole thing will still be valid even if the pull request or repo is gone a few years from now.

Yes, Adding the "comment" field to the signature storage file totally makes sense. Feel free to create a PR or I will do it sometime next week.

Maybe even better, the bot would fetch the user data from the GitHub API and add this to the comment too, so that we have as much info as possible and it will be permanently there. I guess that's an extra step that could be done by us though

What kind of user's metadata would you like to add?

I just made an API call and I guess these fields would be good, and would help to better identify the user:
{
  "login": "laurent22",
  "id": 1285584,
  "node_id": "MDQ6VXNlcjEyODU1ODQ=",
  "url": "https://api.github.com/users/laurent22",
  "type": "User",
  "name": "Laurent Cozic",
  "company": null,
  "blog": "https://joplinapp.org",
  "location": "London",
  "email": null,
  "bio": null,
  "twitter_username": null,
  "public_repos": 183,
  "public_gists": 9,
  "followers": 1768,
  "following": 8,
  "created_at": "2011-12-26T04:20:45Z",
  "updated_at": "2023-02-19T22:23:47Z"
}

I wish I could help with this, but I won't be able at the moment. I think I'd need to set things up so that I can test properly (for my open PR too), and make myself familiar with GH action syntax

I was curious about this as well and found this issue. Wondering what is preventing a person from disputing a CLA agreement, if they've deleted their original comment? Is there anyway to preserve this info or prove it happened?

I thought about another solution (not sure if any easier to implement): whenever a user signs a pull request, the bot quote the comment and append a new comment to the pull request:

@someuser signed the pull request on 12/11/24 with the following comment:

I have read the CLA Document and I hereby sign the CLA

Since the comment would have been created by the bot, it won't be possible for anybody but the repo owner to delete it. I'm not sure it would be any easier to implement but thought I'd mention it as I think it would solve the issue too.


es.yml updated

Some descriptions were translated to spanish

Thanks for contributing to the #1216 issue!


[FLOC-1556] Create container with CPU shares

Fixes FLOC-1556
Please wait for #1218 to be merged before reviewing, it will make the diff a lot smaller.

Looks good, address and merge when buildbot is happy.


Rapid Test Profile: Date of birth can be in the future

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for iOS only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] Bug is not already reported in another issue

Technical details

Device name: iPhone 11
iOS version: iOS 14.5.1
App version: 2.2.1

Describe the bug

The date of birth in the Rapid Test Profile can be set to be in the future.
Steps to reproduce the issue

Open Rapid Test profile
Edit date of birth and scroll in the future

Expected behaviour

The date of birth can be set only for the past. Also the minimun allowed age to use the app should be considered.
Possible Fix

Additional context

Internal Tracking ID: EXPOSUREAPP-7224
Internal Tracking ID: EXPOSUREAPP-7293

@FlightMS Thanks for the report. Internal Tracking ID: EXPOSUREAPP-7224. Best wishes, DS

Corona-Warn-App Open Source Team

Related issue: https://github.com/corona-warn-app/cwa-documentation/issues/605
There is no input validation at all. Seems like that's also the case under Android. Please check.

Is it also possible to set the time to the future under Android? If yes this should be moved to the documentation repository.

@Ein-Tim A date picker is shown on Android as well, though it doesn't use spinners like on iOS, but rather a calendar-like view. I can enter a birth date in the future without problems.
Specifically due to the layout on Android, it could happen that a user swipes to the month they are born in without realizing that they are looking at the year 2021. This is not super likely to happen, but still, maybe only dates that are more than 1 year ago should be allowed to be entered. It is highly likely that no person under the age of 1 is using the app, and since there can only be 1 RAT profile at the same time, such a change might be rather beneficial overall.

Okay, thank you for the confirmation @fynngodau!
@dsarkar Since this affects Android too, please transfer it to the documentation repository.


Add Policy datasource and resource

started work a few days ago

[ ] policy client
[ ] policy resource
[ ] policy datasource
[ ] policy review


Change engine field to be >=8 instead of ^8

This makes sure it works in packagers that honor the field with node v9 and onwards, for example yarn withouth the --ignore-engines argument.

CI tests look the same to me on this PR as they do on master.

CI tests look the same to me on this PR as they do on master.

Yeah, the nodecore stack traces changes all the time so it is hard to write consistent tests.

Thanks :)

I saw you bumped the version for it, but possibly forgot to publish it to npm? :-D

@maritz Haha, you are correct. It is published now :)


Does not validate correct  content

Versions

vee-validate: 2.2.7
vue: 2.6.6

Describe the bug
A few days ago the validation of a custom component worked fine.
After  updating vee-validate, the input is not validated correctly and always returns a false invalid field.
This is the field:
 <currency-input id="product-price"
                                            name="product-price"
                                            v-validate="{ required: true }"
                                            :class="{'form-control': true, 'is-invalid': errors.has('product-price')}"
                                            :currency="currency"
                                            v-model="product.price"/>

The currency input is from here: https://github.com/dm4t2/vue-currency-input
product.price has the value 1.2 in my example. Once I do:
this.$validator.validateAll ().then ((result) => {

				if (result) {
				}
			});

I am getting an error (The product-setup field is required.) and {{errors.has('product-price')}} switches to true (before calling this.$validator.validateAll it's false.

Can you point out which version broke it for you, what version were you on?

Sorry, I just missed that  the component itself got an update, too.
I think this change is the reason why eve-validate  does not  work with  it: https://github.com/dm4t2/vue-currency-input/commit/41042c17c816db1733b7b2cacc6b4e8ed666f172


Schema permissions are not shown for PostgreSQL roles

Description
Role has USAGE & CREATE permissions on "temp" schema as can be seen using this query:
SELECT
       r.rolname AS role_name,
	   n.nspname AS schema_name,
       p.perm AS privilege
FROM pg_catalog.pg_namespace AS n
CROSS JOIN pg_catalog.pg_roles AS r
CROSS JOIN (VALUES ('USAGE'), ('CREATE')) AS p(perm)
WHERE has_schema_privilege(r.oid, n.oid, p.perm)
order by 1,2,3

But in the Role Permissions screen it is not shown as checked:

And they do not show up in "Source" neither:

DBeaver Version
Community Edition v<IP_ADDRESS>401072024
Operating System
Windows 10 64 bit
Database and driver
PostgreSQL v15.5
Steps to reproduce

Run:

CREATE SCHEMA temp;
CREATE ROLE myrole PASSWORD 'Abcdefgh1';
GRANT ALL ON SCHEMA temp TO myrole;

Refresh DB Navigator "Roles" node.
Open myrole "Permissions" tab.
Open myrole "Source" tab.

Additional context
No response

Hello @yoni-yad2
I can't reproduce your issue.

Did you refresh your role after creation?
Also, you can check the metadata queries in the Query Manager (do not forget to enable filters).

I would like to mention I'm experiencing it on an RDS PostgreSQL instance.

Could you please provide a result of the "Test connection" button in your connection settings?

Connected (2509 ms)
Server: PostgreSQL 15.5
PostgreSQL 15.5 on aarch64-unknown-linux-gnu, compiled by gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-6), 64-bit
Driver: PostgreSQL JDBC Driver 42.5.0

I can see the permissions through the Schema Properties/Permissions tab but not through Role Properties/Permissions tab.

For now, I can't reproduce, and I do not have ideas.
Could you please check the metadata queries in the Query Manager (do not forget to enable filters)?

In Query Manager I was able to find the failed query:
SELECT * FROM (
	SELECT DISTINCT relnamespace,
	relacl,
	relname,
	relkind,
(aclexplode(relacl)).grantee as granteeI
FROM
	pg_class
WHERE
	relacl IS NOT NULL
	AND relnamespace IN (
SELECT oid
FROM pg_namespace
WHERE nspname NOT LIKE 'pg_%' AND nspname != 'information_schema')
UNION ALL
SELECT DISTINCT
	n.oid AS relnamespace,
	nspacl AS relacl,
	n.nspname AS relname,
	'C' AS relkind,
(aclexplode(nspacl)).grantee as granteeI
FROM
	pg_catalog.pg_namespace n
WHERE
	n.nspacl IS NOT NULL
	) AS tr
WHERE tr.granteeI=1467441 AND tr.relkind IN('S', 'm', 'C')

Error:
ERROR: UNION types "char" and text cannot be matched
Workaround:
Replacing the "relkind" constant expression in the second SELECT below UNION ALL:
cast('C' as "char") AS relkind,

Yes, I see now — the PostgreSQL version matters.
Thanks for the report.


Wait for containerd installation in GCE scripts

Prior to running the kube-node-installation.service, the containerd
installation should be complete as the k8s installation may have
dependencies on containerd and related binaries (e.g ctr). Add
wants/after systemd directives to ensure
kube-node-installation.service will only start after containerd
installation completes.
Signed-off-by: David Porter<EMAIL_ADDRESS>

/cc @adisky @SergeyKanzhelev @endocrimes

/retest

/ok-to-test

@bobbypage: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name	Commit	Details	Required	Rerun command
pull-containerd-build	6e3cc28 link	true	/test pull-containerd-build
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

🤔

Your credentials are invalid. Please run
$ gcloud auth login
Creating gs://cri-containerd-staging/...
ServiceException: 409 A Cloud Storage bucket named 'cri-containerd-staging' already exists. Try another name. Bucket names must be globally unique across all Google Cloud projects, including those outside of your organization.

/retest pull-containerd-build

/test pull-containerd-build

/retest

very late but LGTM, Thanks for fixing this @bobbypage

Cherrypicked to 1.4 (https://github.com/containerd/containerd/pull/6553) and 1.5 (https://github.com/containerd/containerd/pull/6552)


Update TQDM to support dataloaders of unknown length

The TQDM logger should not depend on state.steps_per_epoch. Instead, it can read len(state.train_dataloader); however, it should gracefully support dataloaders where this length is unknown.

Addressed in #240


Why does 'ls-remote' start from the bottom of versions and not the top?

[Sorry for removing the issue template, but none of the points made sense for this ticket.]
I always wonder why 'ls-remote' doesn't start from the newest version, which mostly would allow for almost instant CTRL+C without waiting half a minute for the complete list. Is there any particular reason for this? Usually I am always too little bothered to mention it somewhere but today I thought that this has been the case for several years now and it finally should be discussed. :)
Seriously, who wants to install the node versions below 1? Below 10? Below 15?.... That ordering should be descending in my humble opinion.
Thanks for this awesome product! 🚀

Because that’s how they’re listed on the remote server, so it would be a lot slower to reverse the entire download - you’d end up waiting more time.

@raphaellueckl I have the same thought every time I go to upgrade node. 😄 🤷
I know it's overkill, but I recently installed html-xml-utils so that I can run this:
curl -s https://nodejs.org/en | hxselect -c .home-downloadbutton | awk -F "<[/]*small>" '{print $1"\\n"$3}'

Which at the time of this post outputs:
18.18.0 LTS
20.8.0 Current

There's probably a cleaner, less-fragile solution, but...
https://xkcd.com/1205/

i mean you can just list the latest major, or --lts, etc, so usually that’s what i do when I’m not trying to see everything.

I mean you're using a negative LS and I get it yeah that's the for listing
features the one not blah blah blah but you know what I think you should do
what if you put a positive LS what would that do I'm just saying try doing
it you never know which way you're going to go with it you know every time
you see something and you think we have to think is what about the opposite
way of doing things so whatever you see try to think of the other side and
what they're doing that's a way to better design that's how I see it man so
instead of negative LS try positive LS see where it gets you I don't know
I'm just saying
On Sun, Oct 8, 2023, 9:27 PM Jordan Harband @.***>
wrote:

i mean you can just list the latest major, or --lts, etc, so usually
that’s what i do when I’m not trying to see everything.
—
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/3216#issuecomment-1752328978, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BAU6EHF3Y3EHQFMZWBTVFVTX6N4L5AVCNFSM6AAAAAA5VJLASKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGMZDQOJXHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

what's a "negative LTS"? --lts says, only show me LTS versions.

@ljharb Thx for responding. If it's the remote that delivers the list in a badly sorted way, can we somehow raise a ticket there? Wherever that is.

You certainly could file an issue on nodejs/release requesting the order be inverted.

😢😭😭

@raphaellueckl I'm actually quite glad that it is this way, since on my machine the listing is instant and I don't have to scroll some 18 pages to get to the latest versions. But if you really prefer it in reverse order nvs seems to have it that way.

You can get this by nvm ls-remote | tac, for example (or a workaround if tac isn't present on your system).
For the reasons described above, I don't think this is something nvm should worry about.

@ljharb It's not the same, since your command has to wait for the completion to show anything...

@kuchta because of the ordering in the source data, that’s impossible to avoid, for nvm or for users.

@ljharb I don't know from where the source data come from, but I'm quite sure it can be improved by first class support in the command, since getting even few thousands lines could be get in a blink of an eye...


Update async to version 2.6.4

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Upgrade async to version 2.6.4(the latest version).
To fix a security issues(CVE-2021-43138):
A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the mapValues() method.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
@Arhell I updated the version by manual, is it right?  Is there any better way to do this kind of thing?

I updated the version by manual, is it right? Is there any better way to do this kind of thing?

@Arhell @rgrupesh any comments? Since we have a bunch of dependencies that need to update. I don't want to do it manually.

I updated the version by manual, is it right? Is there any better way to do this kind of thing?

@Arhell @rgrupesh any comments? Since we have a bunch of dependencies that need to update. I don't want to do it manually.

When I finish with the plans, I can update the dependencies manually, I will keep them up to date

When I finish with the plans, I can update the dependencies manually, I will keep them up to date

Thanks. I'll open an issue for the list of dependencies that needs to be updated.

When I finish with the plans, I can update the dependencies manually, I will keep them up to date

Thanks. I'll open an issue for the list of dependencies that needs to be updated.

Sounds great!


Failed to initialise tesseract engine: .net 6.0 [Tesseract 4.1.1 + Tesseract.Data.English 4.0.0]

Hi, I've recently been looking at Tesseract as a solution for providing OCR for driving licences however, I cannot seem to get the .Net implementations to play ball with what should be the matching learning data for the english language. My implmentation at the moment is super simple and i've created a new .Net 6.0 api project with the following controller code:
[Route("api/[controller]")]
public class OcrController : ControllerBase
{
    public const string folderName = "images/";
    public const string trainedDataFolderName = "tessdata";

    [HttpPost]
    public string DoOCR([FromForm] OcrModel request)
    {

        string name = request.Image.FileName;
        var image = request.Image;

        if (image.Length > 0)
        {
            using (var fileStream = new FileStream(folderName + image.FileName, FileMode.Create))
            {
                image.CopyTo(fileStream);
            }
        }

        string result = "";

        using (var engine = new<EMAIL_ADDRESS>request.DestinationLanguage, EngineMode.TesseractAndLstm))
        {
            using (var img = Pix.LoadFromFile(folderName + name))
            {
                var page = engine.Process(img);
                result = page.GetText();
                Console.WriteLine(result);
            }
        }
        return String.IsNullOrWhiteSpace(result) ? "Ocr is finished. Return empty" : result;
    }

I've installed the following Nuget packages into the solution:

But when it comes to actually running the solution in Swagger or using Postman, as soon as it hits the TesseractEngine initialiser I get a "Failed to initialise tesseract engine.. See https://github.com/charlesw/tesseract/wiki/Error-1 for details." error. I've tried to use this link to diagnose the problem but to be honest it mostly suggests that there may be version differences between the language file and the tesseract version which in this case, both are using the 4.0.x versions so should be compatible.
I've checked the following:

Ensured that the images folder exists
Ensured that the eng.traineddata file is set to 'copy always' in properties
Ensure that the x64 and x86 folders are also set to copy always
Tried different Engine modes but all of them seem to produce the same results

Any assistance with this issue would be greatly appreciated.

How is this related to this repository? This repository contains the data for training the models. Actual engine issues should be reported at the appropriate places - either at the base repository if it corresponds to a general issue or to the wrapper library you use (in your case the wrapper library seems to live at https://github.com/charlesw/tesseract).

Please use the Tesseract user forum for questions.


Finish the rename to FlakeForge

I came across your repo and wanted to give it a try but hit a few snags that seem related to the rename to flakeforge. The changes in this PR address the Python module pathing and some other small path issues that were causing things to break. I was also able to fix the nixosModule so that it would actually serve images. The problem was that the systemd user needed to be added to the nix-deamon trusted users list.

I also added a --refresh to the nix build command because during my testing of things I kept running into the issue of Nix not recognizing changes made to the flake it was suppose to build.

Thanks!


Poor 'file not found' errors

Unfortunately when a File::open fails due to a missing file, it does not report an informative error about which file is missing.
I think we should wrap all File::open calls with something that decorates such errors with the filename, so that the user knows what the problem is. I've hit this a couple of times and haven't been able to work out what is wrong without editing the code.

I can probably do this

@bolshoytoster Thanks, it would be really nice if you could take a look.

I’ve opened a pull request (#64)


A few playful miniapps [toys-dev]

Adding a handful of miniapps of a less serious nature.
A couple of these could use more detailed comment blocks at the top to describe how they can be used.

Mark, I need some time to change these a bit, but in the meantime, do you think we should another reviewer, e.g. @jandrej?

I added the cmake build files and merged the lib-extras-dev which was a bit heavy after thinking about it.
If my merge doesn't break the build I'm ok with it. I didn't toy around too much though 😄

@benson, @NoseKnowsAll, @cjvogl  -- is that something that interest you?

@tzanio ,  I improved the comments in automata and life and also made a few small improvements.    I did not look closely at mandel but I think this PR may be ready for review.

Thanks @mlstowell. Can you take a look at the Appveyor errors?

Since #864 is merged here, should we review that first? @mlstowell, I believe we agreed that needs a bit work...

Yes, I imagine #864 should be merged first.  I've done a little work on that one as well.  I think it's nearly ready.
Incidentally, I believe the Appveyor errors have been resolved.  For sake of portability I switched the random number routines to more standard choices (I didn't realize I was being unconventional).

The toys miniapps are ready for review and comments 🌟
(the full review will wait for#864)

I added a new toy miniapp (Lissajous).
@camierjs do you want to add your minimal surface example here or is that more of an example?
Other ideas for cool toys / miniapps:

Chladni_figures
Reaction-diffusion
Image-to-mesh version of Shaper

@tzanio , the lissajous mini app is lovely!
I noticed two small issues though.  I think there's a word missing from the comment block at the top, ... which appear to vertically and/or ....  Also, I get a warning that tangent[3] is an unused variable in the transformation function.

Thanks @mlstowell! Should be fixed now, but please feel free to make any further improvements / fixes directly :)

Fun! The lissajous example is very well done - I hadn't seen that before.  I was able to run all the examples, but encountered some bugs.  Are we doing a formal review process here?

Say "hello" to Mesher

Another possible name for Mesher is Mondrian [1]. Which one do you prefer?

I vote for Mondrian.

I like Mondrian as well.
On 8 Jan 2020, at 0:57, Mark L. Stowell wrote:

I vote for Mondrian.
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
https://github.com/mfem/mfem/pull/847#issuecomment-571952447


catched nullException error

The GUI will now show that the json file is corrupted!.
close [PE-D] Manually editing countdown JSON preventing app start

Codecov Report

Merging #181 (5fc0461) into master (fc5096a) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #181      +/-   ##
============================================
- Coverage     45.75%   45.63%   -0.12%
  Complexity      470      470
============================================
  Files           115      115
  Lines          2402     2408       +6
  Branches        270      271       +1
============================================
  Hits           1099     1099
- Misses         1237     1243       +6
  Partials         66       66

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/UserInfo.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc5096a...5fc0461. Read the comment docs.


V 0.0.0

This will test to see if I can register Fae.jl

@JuliaRegistrator register

Error while trying to register: "Package version must be greater than 0.0.0"

Well, I guess it's installed then. I'll come back to it after the feature branch is complete and we bump things up to V0.0.1


The readme documentation has incorrect code for file upload

In the section Upload a file for processing in README
await dolbyio.io.uploadFile(jwt, inputUrl, originalFilePath);
Should actually be
await dolbyio.media.io.uploadFile(jwt, inputUrl, originalFilePath);

You're absolutely right, thanks for catching that!


Support Separate Subscription for Jenkins

This is the main commit :
https://github.com/projectkudu/SimpleWAWS/pull/54/commits/6c70732ec5eb8da0205a126605918c6e615b6421

Adding @arroyc


Add parallel to iterative_solver

IMPORTANT: Please search among the Pull request before creating one.
Title
Parallelize solving of the system when computing absorption probabilities.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] New feature (non-breaking change which adds functionality)

Description

Added an option to solve the system in parallel, default is still sequential.
How has this been tested?
No unit tests yet - I will add one test using parallel option.
##Benchmarking
For now, only on pancres, 20 lineages.
Before:
1.12 s ± 23.2 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
After:
954 ms ± 14.4 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
Closes
closes #256
@Marius1311
There was previously this line: x0 = None if ix in init_indices else x, but it doesn't seem correct: https://github.com/theislab/cellrank/blob/master/cellrank/tools/estimators/_base_estimator.py#L419. Am I wrong?

Also, you realize setting ._lin_probs in this method overrides the computation done in .{compute,set}_main_states() in GPCCA?
Just checking whether it's intended.

Hi Mike, what's the issue with x0 = None if ix in init_indices else x? Basically, I want to say that for cells that belong to the same metastable state, use the previous solution as initialization because these problems are likely to have similar solutions. If however the last cell came from a different metastable state, don't use this initialization.
You are right there may be an issue here: cells aren't ordered by metastable states in the matrix B, ie I'm not sure whether I'm really making use of this initialization at all!

The pancreas is too small though to benchmark this, can you try in lung or in the morris reprogramming data please? Because so far, there is no significant speed up.

I think the first thing to check here would really be: in the old formulation without parallelization, did we make use of clever initialization? Because if not, we should change that, and see how much improvement that gives. Once we have that, we can benchmark this against a parallelized version.

Okay, I think the compute_absorption_probabilities function needs a bit of work. Currently, it's too complicated. I will look into this hopefully later today, and refactor it. I will move the heavy lifting into a utility function we can test easily. Until then, I think it makes sense for you to pause your paralelization efforts.

Hi Mike, what's the issue with x0 = None if ix in init_indices else x? Basically, I want to say that for cells that belong to the same metastable state, use the previous solution as initialization because these problems are likely to have similar solutions.

Ah, I see, thanks for the explanation.

Until then, I think it makes sense for you to pause your paralelization efforts.

Agreed.

I'm still on the refactoring, hopefully will be done tomorrow morning!

Thanks @Marius1311 , I'm happy to merge this!


tokens and secrets

Need to be set in repo, and saved on separate word doc sent to core group

It turns out I have the proper level of access, Github token created (towards goal of proper testing infrastructure)

It is unclear to me what this issue is about.


Formatting replaces units with fromUnit_ calls

Description of suggestion or shortcoming:
I start with the code: a = 50k to 100k
Then, I run formatting.
This produces:
a = fromUnit_k(50) to fromUnit_k(100)
You can try this here:
https://squigglehub.org/users/ozziegooen/models/fromUnit-test
This was an issue here:
https://squigglehub.org/users/ozziegooen/models/foom

Yeah, that rewrite is currently done in parser and not available in AST.
Also it's pretty dumb; 1ASDF is interpreted by Squiggle as fromUnit_ASDF function call.

The auto-formatting seems essential for a lot of this stuff, we just need to continue to improve it.


fix install info early return

What does this PR do?
Follow-up of this review: https://github.com/DataDog/datadog-agent/pull/24072#discussion_r1546189334
The code was missing an early return if dpkg is on the system.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Link doesn't load the page with the script duScrollspy:becameActive

This script works well but I discovered that the links to another page doesn't work. The url changed but not the content.
This is the plunker with the script and so the page doesn't load : http://plnkr.co/edit/emrTAvTPMKbLUNYi40Xq?p=preview
And the plunker without the script, the page load :
http://plnkr.co/edit/xfsAWsLADkW6F98exC4P?p=preview

With the new script it's works perfectly ;) Thanks :D

Was just about to write about it haha.

Yes thanks ^^


(Minor) feeding a large file into --exclude-file causes restic to run out of memory

Output of restic version
restic 0.9.3 compiled with go1.11.1 on windows/amd64
How did you run restic exactly?
restic backup C:\ --exclude-file='stupidly large file'

What backend/server/service did you use to store the repository?

In this case, passing in the --exclude-file argument instead of --exclude.

Actual behavior
The program crashes

Steps to reproduce the behavior
Try to create a backup of a directory containing a ridiculously large file.  Something larger than ram and swap combined.
Use restic backup . --exclude-file='that large file' instead of '--exclude'.

Do you have any idea what may have caused this?
See above
Do you have an idea how to solve the issue?
Perform a file size check on '--exclude-file' and give a warning/exit if the file is too large.
Did restic help you or made you happy in any way?
Things worked fine once I saw my mistake.

As mentioned in #2694 exclude check slows down to a crawl when using more than a few thousand exclude entries. That is it might be a good idea to add a limit on the size of excludes.

As mentioned in #2694 exclude check slows down to a crawl when using more than a few thousand exclude entries. That is it might be a good idea to add a limit on the size of excludes.

Hard limits are bad, but maybe show a warning after 1000 regexes which the user have to confirm or override with a flag?
On your branch I don't have issues with out of memory, but my system has 12 GB and I didn't pay attention to the memory consumption.
I probably never had the restic stable run long enough to run into memory issues with the current stable. Additionally, Windows cannot handle large amounts of memory consumption very well in my experience.


Add .ConfigureAwait(false) to all await calls

Never mind.  I see it's from github

aydin

(sent from a phone)
On Jun 3, 2016 7:25 PM, "Brian Friesen"<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/RockFramework/Rock.Core/pull/30
Commit Summary

Add .ConfigureAwait(false) to all await calls

File Changes

M Rock.Core/Mail/SendExtension.cs
https://github.com/RockFramework/Rock.Core/pull/30/files#diff-0 (2)
M Rock.Core/Net/EndpointDetector.cs
https://github.com/RockFramework/Rock.Core/pull/30/files#diff-1 (12)
M Rock.Core/Net/EndpointSelector.cs
https://github.com/RockFramework/Rock.Core/pull/30/files#diff-2 (2)
M Rock.Core/Net/Http/WithRetryExtension.cs
https://github.com/RockFramework/Rock.Core/pull/30/files#diff-3 (4)

Patch Links:

https://github.com/RockFramework/Rock.Core/pull/30.patch
https://github.com/RockFramework/Rock.Core/pull/30.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RockFramework/Rock.Core/pull/30, or mute the thread
https://github.com/notifications/unsubscribe/ACw6E9EpFqWpjW8-FZOMTkhtD_fy95tzks5qILf7gaJpZM4It_EE
.


i18n fixed mistake in es.yml causing error on invite!

Initially the translation had an invalid argument %{nombre} causing missing interpolation argument :nombre in "Estimada/o %{nombre}"

Any chance of getting a bumped version for this?

Done

Thank you!


Revert "someTypeRelatedToType now passes isIntersectionConstituent (#…

…33213)"
This reverts commit 8ca36f35165fc259ee4a567e5933623964f1ac3e.
This is mainly to test whether the whole commit has a perf regression.

@typescript-bot perf test this

This change is not it.
In summary, 50 measures got faster, 38 got slower. 7/50 got 1.x% faster, 43 got 0.x% faster. 4/38 got 1.x% slower, 34/38 got 0.x% slower.


CI POC

Let's try to integrate a CI, perhaps GitHub Actions.
The idea is to create a Proof of Concept (POC) to explore what is possible with the built-in demo, following up from #1.

Closing this, there is now a Circle CI integration. Future work will be around figuring out how it becomes standardized across Building Blocks.


update libvtk-java for xenial and wily

I collapsed it because it's been the same since lucid and we don't support anything older.
See: http://packages.ubuntu.com/xenial/libvtk-java

+1


Track adoption of DOMFrameContentLoaded event

According to this Webkit bug, this event is present in Firefox since 2012 but doesn't work in Safari. Can't find anything on Chromium support.


Pass User Object to Cloud Code

Can an object be sent from the javascript sdk to cloud code?  If so, then how could I go abouts sending a user object to cloud code?   I realize I can query for the object and then update the cloud code but is there another way?
When I run my cloud code function it says "Parse Objects not allowed here".

I'm not sure we support parse objects sent to cloud code, not sent back from cloud code, try sending it as a JSON and creating it back when you have it in cloud code.

Like @flovilmart you cannot send objects to cloud code but what you can do is to send the objectId and if you need all the object then you can query it from the database (by the objectId) and if you don't need the all other fields of the object then you can create a new object of the same type and set only the id to the objectId that was sent to the cloud code function.

Thanks guys! I did that :)


⚠ Samsung has degraded performance

In a2ab41e, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2574 ms

Resolved: Samsung performance has improved in 16f3007.


Putting external links in toctree.

This is to bring the readthedocs version and custom layout closer together. (Maybe they can converge?)
Before:

After:

Vs. RTD version
Before:

After:

LGTM

@jgeewax WDYT of this change?

@jgeewax Bump

LGTM @dhermes

@tseaver You mentioned before that Pyramid had a custom theme. I'd like to discuss a bit more as our two docsets get closer and closer to each other.


Allow dice to be different colors

Currently, we have all dice as SVG files, so we should be able to accomplish this relatively simply.

resolved by 1e2552e743d9094426fb959eaed76871cb2bdf1b


LDS EM is numerical unstable

The EM algorithm for fitting LDS described in the book PRML (ch13) is numerical (very) unstable, that the covariance matrices are often singular.
There is no easy way to fix this. Two options are
(1) Leave it as it is in the book, so that people can learn it but not use it in practice.
(2) write stable algorithm, which is quite different to the one in the book.
Current status is (1).

improved stability a little. Done for now.


Split protobuf from rialto

Summary: Move protobuf source creation into one library and add flag to build shared protobuf library.
Type: Feature
Test Plan: Unittests, Component Tests, Fullstack builds.
Jira: RIALTO-476

https://jenkins.code.rdkcentral.com/job/github-triggered/47403/ started

Job for AI/job/AI_BUILDS/job/AI-Trigger-PullRequests started: https://pv-jen015.uk2.scp.bskyb.com/job/AI/job/AI_BUILDS/job/AI-Trigger-PullRequests/173/

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/19231/ started.

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/37517/

https://jenkins.code.rdkcentral.com/job/github-triggered/47409/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/13048/ started

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/37530/

https://jenkins.code.rdkcentral.com/job/github-triggered/47415/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/47417/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/47419/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/47420/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/13051/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/13052/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/19247/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/19248/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/13053/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/47423/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/19249/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/47426/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/47427/ started

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/37536/

https://jenkins.code.rdkcentral.com/job/github-triggered/47488/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/13103/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/19302/ started.

Sanity tests for ['BCM Reference Refapp2'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/37660/


[NuclideReason] Make things work with toggle-file-symbols

cmd-r to see all the symbols in the file.

Language-server does this


200 year option

title says it all

PayOnce is inconsistently camelCase, should be optional in all cases for backwards compatibility and handled accordingly.
Version should be bumped to 2.3.0 and npm i rerun.
You need to add yourself to the contributor list ;)


Unreliable CTRL-C shutdown

Got the following two errors on 20 Jan 2019 while attempting to quit. I think what happened is that I tried to use CTRL-C to shut down, but some thread or threads were still running and so I had to send CTRL-C a second time, which apparently worked but emitted this error. I suspect one of the threads is stalled for some reason and therefore doesn't terminate itself. There are four threads total: the main thread, two in the gamepad module, and one in the telem module. I am inclined to be a bit more suspicious of the telem module since I don't think it has been tested as extensively; I don't always enable it when testing indoors, for example.
rgottula@nix ~ $ optical_track
Gamepad found and registered.
^CGoodbye!
^CException ignored in: <module 'threading' from '/usr/lib/python3.5/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 1288, in _shutdown
    t.join()
  File "/usr/lib/python3.5/threading.py", line 1054, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.5/threading.py", line 1070, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
KeyboardInterrupt

A similar error in hybrid_track from the same night:
rgottula@nix ~ $ hybrid_track --meridian-side=east tle ~/Desktop/tles/SL16_RB.tle
In TLE file mode: '/home/rgottula/Desktop/tles/SL16_RB.tle'.
Hybrid error source starting in blind tracking state
Gamepad found and registered.
Warning: loop filter update period was 0.2201 s, limit is 0.1000 s.
Warning: loop filter update period was 0.2201 s, limit is 0.1000 s.
^CGoodbye!
^CException ignored in: <module 'threading' from '/usr/lib/python3.5/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 1288, in _shutdown
    t.join()
  File "/usr/lib/python3.5/threading.py", line 1054, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.5/threading.py", line 1070, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
KeyboardInterrupt

See also #118 which appears to be a duplicate of this.

We did a bunch of debugging on this today to figure out what's going on. In the cases where we reproduced the issue, there were 2 threads still running: the main thread (which was using ~20% CPU and appeared to be actively issuing Gemini2 commands over the UDP socket), and another thread (which was not using any CPU, and had a call stack that indicated that it was probably a gamepad-related USB thread, waiting or possibly stuck in poll). Those stack traces are in the Slack DM's.
One thing worth revisiting would be the per-thread strace logs idea, which would help determine exactly which fd was being polld upon by which thread and for how long, etc.
Also we might want to look into updating the Python inputs library from 0.1 (what we are using) to 0.5 (the latest), as it appears that a bunch of relatively recent development has gone into that, which may or may not help matters (as the gamepad code is one of the suspects here).

Actually it's not necessarily a mystery as to why Gemini2 stuff was still happening in the main thread; the destructor for the Gemini2 class calls the stop_motion method, which itself contains a while True loop that could potentially have problems if erroneous conditions cause it to never terminate. So that's worth investigating.

We also discussed some options for ensuring that the mount motion stops even if other threads misbehave. The most promising idea is to explicitly call the destructor on the Mount object in the exception handler for KeyboardInterrupt so that it is called promptly, because otherwise it is not called until all other threads stop and the main thread finishes its cleanup processing (which may never happen if the process has to be terminated in some other way).
It may also be worth investigating adding handlers for other signals like SIGTERM.

Okay. I think we may have solved the most pressing issue, which is that mount safing will occur without first waiting for the other threads to end. I'm going to close, but if we continue to encounter issues this could be reopened. We didn't really identify root cause or correct the problems preventing the other threads from ending.


Lesson 0 crashes on Visual Studio

After following the steps for setting up SDL in Visual Studio, I'm able to build the executable but when I run it fails with a message saying it can't find SDL2.dll

Wording is actually fine I think; I somehow managed to skip that entire sentence.  My bad.  Thanks again!

Not sure if @Twinklebear is willing to revisit the windows setup but, I'm now used to setting up SDL via vcpkg and the cmake toolchain file. VS19 + cmake does the setup automatically even.

vpckg would be cool to add some discusion of to the tutorial, the current setup modes for windows a pre-vcpkg.


cant set -p parameter when using go-dcgm, but cli can

cli can using like this : dcgmi diag -r 4 --fail-early -p "eud.passthrough_args='run_tests=compute'",
but go-dcgm No interface for passing parameters (such as --fail-early or -p paramter )

Correct. The go-dcgm wrapper is much simplified. Please submit a PR if there is functionality you think would benefit the users of go-dcgm.


Add 2.4 release notes

Signed-off-by: Ashish Agrawal<EMAIL_ADDRESS>Issue #, if available:
N/A
Description of changes:
Add 2.4 release notes
CheckList:
[X] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #647 (86c2728) into main (f986238) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #647      +/-   ##
============================================
- Coverage     75.92%   75.88%   -0.05%
  Complexity      116      116
============================================
  Files           124      124
  Lines          6485     6485
  Branches        956      956
============================================
- Hits           4924     4921       -3
- Misses         1077     1078       +1
- Partials        484      486       +2

Impacted Files
Coverage Δ

...destinationmigration/DestinationConversionUtils.kt
70.00% <0.00%> (-2.23%)
:arrow_down:

...nationmigration/DestinationMigrationUtilService.kt
81.45% <0.00%> (-0.81%)
:arrow_down:

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

can we add (or re-tag if a part of another PR) the 2.4 version bump pr in infra


[DOCS] Update PhysicsDirectSpaceState.cast_motion

Second attempt at #25447 since I messed up that branch

Thanks!


Fix dark mode elements appearing in light mode

fixed as of https://github.com/Wrapper-Offline/Wrapper-Offline/commit/07f90da3ead5bf7bd94ab0add47f948ce3aa0b59


feat: add starterkit building block from Likvid Bank implementation

First version of the devops tool chain building block
This can be used standalone or as a meshStack building block. In any case the buildinblock backplane is deployed via collie.
@florianow as a sidenote: The SPN setup in this module is a lot leaner than the one we use in azure/bootstrap (i.e. it has no required_access blocks etc. which iirc are for "grant admin consent"). Maybe we can slim down the azure/bootstrap implementation as well.

Open question @florianow for collie-hub -> should this module be prefixed "azure" (since it's a very azure specific implementation). I think there's very slim chances to generalize this into a multi-platform BB since the backplane and the building block both live in Azure.

this PR is out of date and we now ship updated kits automatically from the likvid-cloudfoundation reference implementation


Rename instances of "monkeypox" to "mpox"

This commit goes through the repo and basically does a find-and-replace of "monkeypox" to "mpox, except for a handful of locations like the #monkeypox-updates Slack notification.
This shouldn't change appearance of build outputs except for:

Updating to "Built by nextstrain/mpox"
Updating page titles to be more descriptive of what each page is showing in terms of lineages / clades
A bug fix to the page description to link to proper build URLs (currently these go to 404)

This has the side effect that intermediate files will begin to propagate to https://data.nextstrain.org/files/workflows/mpox/sequences.fasta.xz, etc... rather than /files/workflows/monkeypox. This may affect users who've been relying on the current URLs. Nothing should break for these users as the old files will continue to exist but they will no longer receive updated data. I think this is an okay trade-off in terms of downstream impacts.

If people request from data.nextstrain.org we should be able to do URL forwarding, shouldn't we? Wouldn't that be better than serving stale data?
Otherwise, for those requesting directly from AWS not via data.nextstrain.org, we have a choice between serving stale data or deleting the old file so that workflows error - each have advantages and disadvantages. Might be worth doing a code search on Github to see who uses the data and ping them.

except for a handful of locations like the #monkeypox-updates Slack notification.

Addressing this separately in #221

These are all the repos that Github could find using https://data.nextstrain.org/files/workflows/monkeypox that could benefit from URL redirects (17, with a handful of non-Nextstrain repos): https://github.com/search?q=data.nextstrain.org%2Ffiles%2Fworkflows%2Fmonkeypox&type=code
These are the repos that use aws s3 paths that can't be redirected (10 mostly ours): https://github.com/search?q=s3%3A%2F%2Fnextstrain-data%2Ffiles%2Fworkflows%2Fmonkeypox&type=code

If people request from data.nextstrain.org we could be able to do URL forwarding, couldn't we?

Yes, definitely possible. Not sure if we need to do it on the Cloudfront side but it's possible to configure S3 website redirections. Also looks like it's possible to redirect requests for an S3 object.

The fetch and ingest workflow completed successfully. However, the artifacts ended up at s3://nextstrain-datafiles/workflows/mpox/branch/rename-to-mpox/. However, it looks good besides this. I'm assuming the best course of action is to merge this PR when it passes review and then to run fetch and ingest again from main so that the files are placed in the proper s3 location.

Thanks @victorlin for the fix with commit b14d6fd147627ec8e34f4c84aeb987dcbb5a2838. I'm going to go ahead and merge this now.

Fetch and ingest is running from master here: https://github.com/nextstrain/mpox/actions/runs/6724598765 and should update S3 files to specify s3://nextstrain-datafiles/workflows/mpox/. I'll monitor and update here when complete.

We discussed redirection rules for monkeypox during today's dev chat and I added @tsibley 's suggested redirection rules to the nextstrain-data S3 bucket.
So now access through data.nextstrain.org should redirect to mpox
$ curl -I https://data.nextstrain.org/files/workflows/monkeypox/metadata.tsv.gz
HTTP/2 301
content-length: 0
location: https://data.nextstrain.org/files/workflows/mpox/metadata.tsv.gz
date: Wed, 01 Nov 2023 23:55:24 GMT
server: AmazonS3
x-cache: Miss from cloudfront
via: 1.1 ac3f0425be668a2439884bb8cbd3ccd8.cloudfront.net (CloudFront)
x-amz-cf-pop: SFO53-C1
x-amz-cf-id: 14QBYLPsKkmgKazVcOsSE7kPxM8NRaCzXSOe-rcV6odttMGDfwU0EA==

Redirection for the s3:// paths are not possible. However, based on Cornelius's search, the s3:// paths are only used for our internal uploads and slack notifications.

Perfect! Thank you @joverlee521.
I can confirm that s3://nextstrain-data/files/workflows/mpox/metadata.tsv.gz and hence https://data.nextstrain.org/files/workflows/mpox/metadata.tsv.gz now exists as expected after running ingest above.
I deleted the monkeypox/ directory in files/workflows/ to reduce confusion. And as expected from your post above, https://data.nextstrain.org/files/workflows/monkeypox/metadata.tsv.gz works to retrieve the mpox/ equivalent.
I believe the next step here is to confirm that a phylogenetics rebuild works as expected. I'll kick this off now.

And actually... this testing already happened with the automatic updates. Earlier today actions including https://github.com/nextstrain/mpox/actions/runs/6735424381 ran and produced updated Auspice JSONs like mpox_all-clades.json. I believe we're set in this case. The corresponding issue https://github.com/nextstrain/mpox/issues/168 is now closed.


Inline and block code

Currently the code formatting which renders < code > tags which are inline elements, but it would also be nice to have a block element (i.e. < pre >) as well. I'm not sure how this could be implemented with respect to the UI, but I think it would be very handy especially for technical documents.

Closing since it is UI-related stuff. Such issues should go to https://github.com/substance/ui/issues in future.


The maximum file count statistics in Linux are calculated incorrectly in VSCODE.

Type: Bug
1、Write a loop code that iterates over the file and counts the number of successful reads.
2、Compile and run this code separately on both the virtual machine and VSCode. You observed that on Ubuntu, the recorded count is 1024, while in VSCode, it unexpectedly reaches over 380,000.
VS Code version: Code 1.81.0 (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:37:13.485Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.91GB (5.66GB free)

Process Argv
--crash-reporter-id bcc80475-e435-456e-b23f-66a7dc4b6ddd

Screen Reader
no

VM
40%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 x 2304)

Memory (System)
7.71GB (6.74GB free)

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vsc-material-theme
Equ
33.8.0

vsc-material-theme-icons
equ
2.8.0

remote-ssh
ms-
0.102.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.0

remote-explorer
ms-
0.4.1

vscode-icons
vsc
12.5.0

vscode-language-pack-zh-hans
MS-
1.81.2023080209

(5 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
282f8724:30602487
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
vsctsb:30748421
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

`#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <strings.h>
#include <stdio.h>
#include <stdio.h>
int main(void)
{
int n = 0;
while (1)
{
int fd = open("src_file", O_RDWR);
    if (fd > 0)
        n++;
    else
    {

        perror("失败");
        break;
    }
}
printf("n:%d\n", n);

}`

#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <strings.h>
#include <stdio.h>
#include <stdio.h>
int main(void)
{
    int n = 0;
    while (1)
    {
        int fd = open("src_file", O_RDWR);

        if (fd > 0)
            n++;
        else
        {

            perror("fail");
            break;
        }
    }
    printf("n:%d\n", n);
}```

#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
#include <strings.h>
#include <stdio.h>
#include <stdio.h>
int main(void)
{
    int n = 0;
    while (1)
    {
        int fd = open("src_file", O_RDWR);

        if (fd > 0)
            n++;
        else
        {

            perror("fail");
            break;
        }
    }
    printf("n:%d\n", n);
}

The same code produces different results when using VSCode's remote connection feature.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

If using "Help: Start extension bisect" didn't resolve the issue, it seems that the problem might not be caused by an extension.

@GanShuPA correct me if I'm wrong but the problem seems related to debugging C, which is only possible with an extension/

When I disable debugging and connect directly to the virtual machine through remote connection, the issue still occurs. Perhaps it's a problem with the remote connection?

I also attempted an SSH connection to the virtual machine in addition to WSL, and encountered the same situation.

@rzhao271 I'm not sure how the max file (open?) count works on Linux, but any idea why it would be different only when on a remote connection?

Potentially related

Open wsl.exe
Run ulimit -n
Notice the output is 1024
Use the WSL extension in VS Code to open a folder in WSL. I opened one under /home rather than /mnt/c.
Run ulimit -n in the integrated terminal
Notice the output is 1048576

I'm not sure whether running ulimit -n 1024 in the integrated terminal would fix the max open file count discrepancy you're seeing while debugging, though, especially if debugging occurs in a different process.
CC @deepak1556

The higher limit you are seeing in the remote scenarios is inherited from the server main process which is a Node.js process. Node.js will adjust the open file descriptors limit (soft limit is quite low in most cases which can easily lead to EMFILE errors) on launch to the hard limit (ulimit -aH) if the hard limit is not unlimited, otherwise it will do a binary search until a higher limit between the soft limit and hard limit is possible for the current process, relevant code is https://github.com/nodejs/node/blob/8dfe4248ca0646a8fc4f4082b52f1d114a7d52ea/src/node.cc#L612-L634. All the subprocess there onwards inherit this resource limit which includes the extension host, terminal etc where the current debugging session occurs.
Closing as the behavior will not be changed in the runtime.

I understand. Thank you for your guidance.


[DevPortal] Cannot subscribe to an Application with already entered default values

When I tried to subscribe to an application with already entered default values in the devportal UI , I was unable to subscribe to it. No message was displayed either.

related to https://github.com/wso2/product-apim/issues/6054 as well

Fixed


multipass: 1.12.0 -> 1.12.1

Description of changes
Bumps multipass to latest patch release
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package built:

multipass


Rate Limited - Fresh Install

I am getting this error after a fresh install of this plugin.

I have all the settings to the default except my api key. Any help would be very much appreciated.

Apologies for the wait. As stated, you should check your plan for the API key on the OpenAI platform and see if it is still active.

No problem! I have a free account to use chat gpt. Do I need to pay for a API key that I can use with weaver?

Could it be another plugin that is breaking it?

You have 30 days of free access to the API. The API is separate from the ChatGPT account.

I see. But I just created the API. Shouldnt I be able to use it for 30 days then?


Update ETHPAY Logo Image for 0xe52e75e8a97546f40991b489e92c68ebb386dc97

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Added here https://github.com/TrustWallet/tokens/commit/58aa22af18e4568cb0749581d9030d09c549ab6b


Add my username to REVIEWERS

@googlebot I signed it!

Appreciate the offer but this system has been deprecated—see this message for info. Thanks


Package Manager UI: Search filter doesn't reapply after you've switched tabs

After you click on Installed, Available, etc you have to retype your search in order for it to apply.

If it is simpler we could just reset it for 0.3 and make it work in 0.4


Select output as a JSON array (Single column list. Ex: List of IDs)

I'm trying to find a way to get a simple JSON array as the output of the Select query.
Example: Select ID from Employee where <SomeCondition> FOR JSON AUTO
Actual Output:

[{"ID":1},{"ID":2},{"ID":3}]

Expected Output:

[1, 2, 3]

@nabilahmed739 Hello, we have at least two documentation articles on FOR JSON AUTO that you can look at:

https://docs.microsoft.com/sql/relational-databases/json/format-query-results-as-json-with-for-json-sql-server
https://docs.microsoft.com/sql/relational-databases/json/format-json-output-automatically-with-auto-mode-sql-server

If the documentation is in error, this Issues website can assist. But no documentation error is being reported here in Issue #2453 .
At the bottom of the above bullet-listed articles, there is a button/link labeled "This Product" (different than "This Page"). The "This Product" link is appropriate for you to click if you want fixes or enhancements to Microsoft SQL Server (which is different than a fix to the documentation).
I am now closing this Issue #2453. The @ notification mechanism continues to work even after an item is Closed, in case further communication is needed.
Thank you for submitting this Issue. We hope to hear from you again.


Making changes to schemas.js

I'm building a documentation pipeline with doca being a large part of it.
I've hit a snag. Your docs say you only run doca init once to bootstrap the project. Making the same call again just throws an error. However, there's no doca function to update and/or pull in new schemas from the parent folder.
The only way I can see this currently working is to remove the documentation folder, and re-run doca init any time I add or remove any schemas.
That in itself is not a problem, but I have to run npm install before I can run npm build when in the documentation folder. npm install takes a bit of time...
It would be great if there could be a new command, like doca update to simply update the list of schemas doca should use.
I'm happy to try and make a pull request, but I don't write node, and I wouldn't know how to write tests for this change either.

 That's why it stops you and you have to manually delete your project first.
I'm assuming that once you've used it you should not ever needed again. In case you are not doing any modifications in your projects (besides adding schemas), it's ok use it again but there is no reason to do it every day. We don't release new versions that often. Most of the changes are in different packages (doca-bootstrap-theme or loaders), not in the app itself. Those can be updated just through npm update (unless it's a major release).
If you need to add another schema, just edit the ./schemas.js and add one more row. Fast and simple.
Also, you can use npm replacement call yarn. It's much faster.

If you need to add another schema, just edit the ./schemas.js and add one more row. Fast and simple.

@Relequestual does that fit your workflow smoothly enough?  Is there a way we can make the documentation more clear?

Thanks @tajo @handrews.
I wasn't expecting that to be how things behave. I've changed my code to anticipate this.
I should be able to make the script update the ./schemas.js file as part of the workflow. It's just not something I want to do manually; all for as automated as possible.
My workflow currently runs build, then extracts the output to a different location. We don't want to run a node server right now.
I agree, once the right schema files are added, that list won't be updated often, only the content of them, potentially.

May be worth documenting that this is expected behaviour. It wasn't clear to me and I spent a half day trying to work it out. Only figured it out when I inspected the doca code... =D