WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

generated.Asset

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Bug Report

Kubernetes version (use kubectl version):

Today's HOT.

commit b71def7

Environment:

Build on Ubuntu 16.04

What happened:

git pull of latest code, then make release fails with

+++ [0930 02:04:05] Starting etcd instance
etcd --advertise-client-urls http://127.0.0.1:2379 --data-dir /tmp.k8s/tmp.fcfyJnEiqq --listen-client-urls http://127.0.0.1:2379 --debug > "/dev/null" 2>/dev/null
Waiting for etcd to come up.
+++ [0930 02:04:05] On try 1, etcd: :
{"action":"set","node":{"key":"/_test","value":"","modifiedIndex":3,"createdIndex":3}}
+++ [0930 02:04:06] Running integration test cases
Running tests for APIVersion: v1,apps/v1alpha1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1beta1,autoscaling/v1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1alpha1,
extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1alpha1,rbac.authorization.k8s.io/v1alpha1,storage.k8s.io/v1beta1
+++ [0930 02:04:07] Running tests without code coverage
# k8s.io/kubernetes/test/e2e/framework
test/e2e/framework/gobindata_util.go:30: undefined: generated.Asset
test/e2e/framework/gobindata_util.go:33: undefined: generated.AssetNames
Makefile:118: recipe for target 'test' failed
make[1]: *** [test] Error 1
+++ [0930 02:05:19] Cleaning up etcd
+++ [0930 02:05:19] Integration test cleanup complete
Makefile:130: recipe for target 'test-integration' failed
make: *** [test-integration] Error 1
Makefile:239: recipe for target 'release' failed
make: *** [release] Error 1

What you expected to happen:

Build to complete

How to reproduce it (as minimally and precisely as possible):

git pull; make release

Anything else do we need to know:

I saw the same thing yesterday on a slightly older commit, so this is not a very recent regression.

Issue 2:
Something like:

rules:
- host: foo.bar.com
path: /api
backend:
- serviceName: alpha1
weight: 1, or 33%
- serviceName: alpha2
weight: 2, or 66%

There'er ways to achieve similar splitting with either a deployment or by managing Service labels so they span a mix of alpha1 and alpha2 endpoints, but this seems more intuitive.

On GCE I think we'd have to use iptables stats to satisfy that, but we can't push it down into a Service because today a single Service only understands homogenous endpoints.

Nginx and haproxy understand wrr, so the 33% and 66% would have to apply to all the endpoints of the Service, and we'd just need to make sure the tie is broken evenly.
Issue 1:
I'm deploying a project of mine to Heroku (which appear to be copying the project from a directory in which it is built before starting it). This causes issues with Next.js 5.0.0, which appear to output absolute paths. This can be confirmed by going through the sources.

This was not an issue with 4.2.3.

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

As the default behaviour (and I'm not sure that it can be controlled) on at least Heroku seem to be to build in one directory and run the build in another, I would expect a build to not contain absolute paths.

Current Behavior

I can see, for instance in dist/bundles/pages/_document.js, that absolute paths are being generated.

An example of an error (not in the test repository) is

Error: Cannot find module '/tmp/build_<id>/eweilow-nextjs-deploy-test-<buildId>/node_modules/next/dist/pages/_document.js'
at Function.Module._resolveFilename (module.js:555:15)
at Function.Module._load (module.js:482:25)
at Module.require (module.js:604:17)
at require (internal/module.js:11:18)
at Object.6 (/app/.next/dist/bundles/pages/_document.js:86:18)
at __webpack_require__ (/app/.next/dist/bundles/pages/_document.js:23:31)
at Object.5 (/app/.next/dist/bundles/pages/_document.js:78:18)
at __webpack_require__ (/app/.next/dist/bundles/pages/_document.js:23:31)
at /app/.next/dist/bundles/pages/_document.js:70:18
at Object.<anonymous> (/app/.next/dist/bundles/pages/_document.js:73:10) code: 'MODULE_NOT_FOUND'

Steps to Reproduce (for bugs)

Deploying https://github.com/eweilow/nextjs-deploy-test to Heroku with their default configuration fails.

Your Environment

Tech
Version

next
5.0.0

node
9.x

OS
Ubuntu 16.04 on Heroku

browser
not relevant

etc

Issue 2:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

HTML/JSX examples with <img> elements should have meaningful alt attributes.

Current Behavior

Two examples in readme.md use <img src="..."> with no alt attribute.

Instead, alt attributes should be part of the examples, either with an empty string value if the image is purely decorative (doesn't appear to be the case here), or with a text label that works as an adequate substitute for the image's intended meaning.

Steps to Reproduce (for bugs)

Visit https://github.com/zeit/next.js

Read through the readme

Context

Code examples that don't follow accessibility best practices train developers -- often with zero background or training in accessibility -- to treat accessibility as something superfluous and someone else's job.
Issue 1:
i am new to doctrine... created yml file with name XYZ.Model.User.dcm.yml inside my condig directory

and i run orm:generate-enities command to generate Entities in XYZ\Model\ directory but i got XYZ\Model\XYZ\Model\User.php instead of XYZ\Model\User.php

Issue 2:
i am new to doctrine... created yml file with name XYZ.Model.User.dcm.yml inside my condig directory

and i run orm:generate-enities command to generate Entities in XYZ\Model\ directory but i got XYZ\Model\XYZ\Model\User.php instead of XYZ\Model\User.php
Issue 1:
Description

When trying to boot an electron application with electron command (directly or indirectly) electron does not boot the app, it simply exits without word, reason or logs, there are no exceptions thrown, there are no logs output, there is no indication of what is actually happening. This was initially discovered when our tests started timing out and the ChromeDriver logs also have no details of what is going on.

Operating system: Ubuntu 16.04 x64.

Electron version: v1.2.4

doctor@who ~/development/envygeeks/easy-electron-base (master +) →
node_modules/.bin/electron app/entry.js --enable-logging --debug --verbose

Window does not load.

Contents:

require("babel-register")
require("./win")

Contents of win.js:

import Config from "./config"
import { default as electron, BrowserWindow } from "electron"
import AppMenu from "./menu"
import Dev from "./dev"

// --

let mainWindow
const app = electron.app
const config = global.appConfig = new Config(app)
new AppMenu(app, config).enable()

/*
* Create the main application window.
*/
function createWindow() {
mainWindow = new BrowserWindow({
width: 1280,
minWidth: 1024,
minHeight: 768,
height: 720
})

// So that electron-connect doesn't disrupt.
if (config.nodeEnv == "development")
mainWindow.minimize()

mainWindow.loadURL(`file://${__dirname}/index.html`)
mainWindow.on("closed", () => mainWindow = null)
new Dev(config, BrowserWindow, mainWindow).
possiblyEnable()
}

// --

app.on("ready", createWindow)
app.on("activate", () => {
if (mainWindow === null) {
createWindow()
}
})

// --

app.on("window-all-closed", () => {
if (process.platform !== "darwin") {
config.saveUserConfig(() => {
app.quit()
})
}
})

Important Notes:

This does not happen on v1.2.2 (installed system-wide) or v1.2.3 (what it was before an hour ago).

We have not tested this on macOS or Windows and have only tested on Fedora and Ubuntu.

Issue 2:
Electron version: 1.2.4

Operating system: Linux xxx 4.2.0-38-generic #45~14.04.1-Ubuntu SMP Thu Jun 9 09:27:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I was trying to set 1.2.2 - 1.2.3 versions and works fine. When updating to 1.2.4 app.on('ready'...) never works. No errors output on console.

Trying "Quick start" from electron. https://github.com/electron/electron-quick-start
Issue 1:
When you use <a router-link="foo">Link</a> with an accompanying <router-outlet></router-outlet>, the proper component's template appears in the outlet. The issue is when the user refreshes (on the proper URL extension, i.e., localhost:8080/foo), no templates are loaded (including the original app's template), leaving the page blank. As far as I can tell, what's happening is that as that URL only is marked to use the template of foo, so there is no outlet for it to show up in. There is the chance I am doing this wrong, but everything else is working properly.

Issue 2:
It appears that only the HashLocationStrategy updates the url on calls to router.navigate. When I change my LocationStrategy to the HTML5LocationStrategy the urls no longer update when navigating from "/products/:productId" -> "/". The navigation does occur, though.

This is happening on Alpha.31.

The code I'm using is below.

Component Controller code

updateProduct(product: {productId:string, name:string, description:string}) {
this.productStore.updateProduct(product);

this.router.navigate('/');
}

Routes

@RouteConfig([
{path: '/', component: ProductsList, as: 'Products'},
{path: '/products/:productId', component: UpdateProducts, as: 'UpdateProducts'}
])

Bootstrap

import { httpInjectables } from 'angular2/http';
import { bootstrap, bind } from 'angular2/angular2';
import { routerInjectables, LocationStrategy, HashLocationStrategy, HTML5LocationStrategy } from 'angular2/router';
import { Onboarding } from './components/onboarding/onboarding';

bootstrap(Onboarding, [
httpInjectables,routerInjectables, bind(LocationStrategy).toClass(HTML5LocationStrategy )
]);
Issue 1:
----------------------------------------------------

This works

----------------------------------------------------

import scipy.io as sio

a_dict = {'field1': 0.5, 'field2': 'a string'}

sio.savemat('saved_struct.mat', {'a_dict': a_dict})

----------------------------------------------------

from pydal import DAL, Field

db = DAL('sqlite://storage.db')

db.define_table('thing',Field('name'))

db.thing.insert(name='Chair')

db.commit()

a = db().db.thing.as_dict();

a is a dict, you can print out

Now if you do

sio.savemat('saved_struct.mat', {'a': a})

gives you a type error because

Could not convert None (type <type 'NoneType'>) to array

Issue 2:
The MATLAB equivalent of None is the empty array []. It looks like scipy does not perform this conversion.

But if I try to save a dict with a None inside it, I get this: (scipy 0.13.0 in Anaconda Python on Windows 7 64-bit)

>>> import scipy.io
>>> scipy.io.savemat('test.mat',{'x':3})
>>> scipy.io.savemat('test.mat',{'x':None})
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "c:\app\python\anaconda\1.6.0\envs\daqlogger\lib\site-packages\scipy\io\m
atlab\mio.py", line 204, in savemat
MW.put_variables(mdict)
File "c:\app\python\anaconda\1.6.0\envs\daqlogger\lib\site-packages\scipy\io\m
atlab\mio5.py", line 872, in put_variables
self._matrix_writer.write_top(var, asbytes(name), is_global)
File "c:\app\python\anaconda\1.6.0\envs\daqlogger\lib\site-packages\scipy\io\m
atlab\mio5.py", line 622, in write_top
self.write(arr)
File "c:\app\python\anaconda\1.6.0\envs\daqlogger\lib\site-packages\scipy\io\m
atlab\mio5.py", line 643, in write
% (arr, type(arr)))
TypeError: Could not convert None (type <type 'NoneType'>) to array
Issue 1:
[ √] I have searched the issues of this repository and believe that this is not a duplicate.

[ √] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.1

Operating System version: Mac OS

Java version: 1.8

Steps to reproduce this issue

使用nacos作为注册中心，集群部署

想同时注册到同一nacos下 不同namespace

参考了官方文档只提供了配置如下

nacos://xxxx:8848?namespace=xxxx

或者

nacos://xxxx:8848?backup=xxxx:8850

即单个namespace或不带namespace时使用backup是生效的

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

配置如下 则无法成功注册

xxxx?namespace=111?backup=xxx?namespace=222

What do you expected from the above steps？

Actual Result

不合法的参数

What actually happens?

在参考#4207升级为2.7.6后也是如此。

If there is an exception, please attach the exception trace:

Just put your stack trace here!

Issue 2:
是否进行心跳信息的发送，是靠下面两个属性来判断的。

Long lastRead = (Long) channel.getAttribute(HeaderExchangeHandler.KEY_READ_TIMESTAMP);

Long lastWrite = (Long) channel.getAttribute(HeaderExchangeHandler.KEY_WRITE_TIMESTAMP);

KEY_READ_TIMESTAMP与KEY_WRITE_TIMESTAMP的设置在HeartBeatHandler和HeaderExchangeHandler中都做了一遍。

在HeartBeatHandler中：（代码较多，就不贴了）

连接完成时：设置lastRead和lastWrite

连接断开时：清空lastRead和lastWrite

发送消息时：设置lastWrite

接收消息时：设置lastRead

在HeaderExchangeHandler中：（代码较多，就不贴了）

连接完成时：设置lastRead和lastWrite

连接断开时：也设置而非清空lastRead和lastWrite

发送消息时：设置lastWrite

接收消息时：设置lastRead

而我们构建的nettyHandler的调用链是这样的：

MultiMessageHandler->HeartbeatHandler->AllChannelHandler->DecodeHandler-> HeaderExchangeHandler->ExchangeHandlerAdapter（DubboProtocol.requestHandler）

也就是说每次请求和响应都会走这个链路，那么HeartbeatHandler设置了KEY_READ_TIMESTAMP与KEY_WRITE_TIMESTAMP后，HeaderExchangeHandler为什么还要设置一遍？而且在HeaderExchangeHandler中断开连接的时候为什么是设置而非清空lastRead和lastWrite？
Issue 1:
We coding almost on US.en keyboard, if need switch input method and switch command name to Chinese in brain then input, it's not good idea.

Issue 2:
VSCode Version:

バージョン 0.10.12-insider

コミット ef2a1fc

日付 2016-03-21T11:33:38.240Z

シェル 0.35.6

レンダラー 45.0.2454.85

ノード 4.1.1

Even Japanese people, typing Japanese words are very painful and time-consuming because of IME composition problems.

We expects that the commands are all in English.

For example, if I want to execute git pull, I will type "git pull"; not "git プル".

Hope you can understand our situation.
Issue 1:
Possibly this issue is not an issue of Windows Terminal but of WSL or of one specific distribution within WSL.

Environment

Microsoft Windows [Version 10.0.18362.356]
Windows Terminal (Preview) [Version 0.4.2382.0]
WSL 1 with Ubuntu 18.04 (not sure how to find out the build number)

Steps to reproduce

start Windows Terminal

open a tab with WSL Ubuntu 18.04 (maybe also with other distributions)

choose a light theme (like One Half Light) in the profiles.json file

view a man page (e.g. man grep)

play with values for brightWhite in the choosen color schema

Expected behavior

General text should be colored in generic colors such as foreground or explicit colors like brightWhite should change their color.

Actual behavior

The WSL man page seems to use brightWhite for highlighted text in man pages. brightWhite remains white in the light themes. The remaining text has the color foreground.

grep manpage with default color schema One Half Light:

grep manpage with modified color schema One Half Light (brightWhite set to #FFFFFF):

Issue 2:
Environment

Windows build number: 10.0.18362.0
Windows Terminal version : 0.4.2382.0
ConEmu version: 180626

Steps to reproduce

Copy the color palette for "<Solarized (John Doe)>" from ConEmu to terminal. Here's the relevant JSON:

{
"white" : "#fdf6e3",
"blue" : "#073642",
"green" : "#586e75",
"cyan" : "#657b83",
"red" : "#dc322f",
"purple" : "#6c71c4",
"yellow" : "#cb4b16",
"brightWhite" : "#eee8d5",
"brightBlack" : "#93a1a1",
"brightBlue" : "#268bd2",
"brightGreen" : "#859900",
"brightCyan" : "#2aa198",
"brightRed" : "#839496",
"brightPurple" : "#d33682",
"brightYellow" : "#b58900",
"black" : "#002B36",
"background" : "#002B36",
"foreground" : "#fdf6e3",
"name" : "Solarized (John Doe)"
}

Set powershell's color scheme to "Solarized (John Doe)"

Run [enum]::GetValues([System.ConsoleColor]) | Foreach-Object {Write-Host $_ -ForegroundColor $_} to admire the colors

Expected behavior

Colors look as nice as ConEmu's

Actual behavior

Most colors look nice and similar but "DarkBlue" looks completely different and way worse. See screenshot.

To get a somewhat similar color you need to set blue (DarkBlue) to something like "blue" : "#0B5669"
Issue 1:
The following program fails with the panic:

package main

import (
"fmt"
"net/mail"
)

func main() {
data := "=??Q? ?=<0@0>"
addr, err := mail.ParseAddress(data)
if err != nil {
return
}
_, err = mail.ParseAddress(addr.String())
if err != nil {
fmt.Printf("failed to parse addr: %q -> %q\n", data, addr)
panic(err)
}
}

failed to parse addr: "=??Q? ?=<0@0>" -> "\"=??Q? ?=\" <0@0>"
panic: mail: missing word in phrase: charset not supported: ""

That name should have been escaped.

go version devel +514014c Thu Jun 18 15:54:35 2015 +0200 linux/amd64

Issue 2:
The following program fails the panic:

package main

import (
"fmt"
"net/mail"
)

func main() {
data := "\"\\\x1f,\"<0@0>"
addr, err := mail.ParseAddress(data)
if err != nil {
return
}
_, err = mail.ParseAddress(addr.String())
if err != nil {
fmt.Printf("failed to parse addr: %q -> %q\n", data, addr)
panic(err)
}
}

failed to parse addr: "\"\\\x1f,\"<0@0>" -> "=?utf-8?q?=1F,?= <0@0>"
panic: mail: no angle-addr

ParseAddress must handle result of Address.String, or else first ParseAddress must fail.

go version devel +514014c Thu Jun 18 15:54:35 2015 +0200 linux/amd64
Issue 1:
Bug report

Describe the bug

<Link> will not navigate to pages with Ant Design stylesheets.

To Reproduce

https://github.com/iamricky/nextjs-bug

Expected behavior

The app navigates to each route except /test. It fails silently w/o errors, so I don't have a way of investigating it. The app will navigate to /test if the stylesheets on line 11 of pages/test.js are omitted or commented out:

import 'antd/lib/button/style/css';
import 'antd/lib/checkbox/style/css';
import 'antd/lib/date-picker/style/css';
import 'antd/lib/form/style/css';
import 'antd/lib/input/style/css';
import 'antd/lib/radio/style/css';
import 'antd/lib/select/style/css';
import 'antd/lib/tag/style/css';

System information:

OS: macOS 10.13.6

Browser: Chrome 73.0.3683.86

Version of Next.js: ^8.0.4

Issue 2:
This is bug report

Link does not work with css-module imported. That happens when page with Link has no css, and linked page has. No errors in console, so im not sure about reasons, but there is minimal repo to reproduce:

https://github.com/standy/next-css-error

Bug appears in next@7.0.0 + next-css@1.0.1,

Older next@6.1.2 + next-css@0.2.0 works fine
Issue 1:
Original ticket http://projects.scipy.org/scipy/ticket/1796 on 2012-12-20 by trac user seanBE, assigned to unknown.

FAILED (KNOWNFAIL=15, SKIP=43, errors=1, failures=69)

Tested scipy using the nose package. 69 failures is quite a lot.

Issue 2:
Original ticket http://projects.scipy.org/scipy/ticket/1729 on 2012-09-18 by trac user breuderink, assigned to unknown.

Dear developers,

I installed the development version (the latest would not compile due to VecLib) of SciPy from source:

$ git clone https://github.com/scipy/scipy.git

$ git show

commit 6981d8b

Merge: a4d9a6d cc900a5

Author: Warren Weckesser warren.weckesser@enthought.com

Date: Mon Sep 17 17:34:36 2012 -0700

$ python setup.py build

[see attachment]

$ python setup.py install

[see attachment]

So far, so good. But, when I tried to run the unit tests (I verified this is the only scipy installation on my computer), I get many unit test failures:

$ python -c "import scipy; scipy.test('full')"

[see attachment]

Most seem to be related to arpack. I am really uncomfortable using this scipy installation, and feel that if building succeeds, the unit tests should run without failures. Is there any remedy?

I have attached my environment (both homebrew installed packages and the build environment as well).
Issue 1:
From @srkiNZ84 on 2016-05-09T22:40:20Z

ISSUE TYPE

Bug Report

COMPONENT NAME

ec2_asg

ANSIBLE VERSION

ansible 2.0.0.2

CONFIGURATION

OS / ENVIRONMENT

Running from: Ubuntu Linux

Managing: Ubuntu Linux

SUMMARY

We (seeming randomly) get cases where we'll do a blue/green deploy using the "ec2_asg" module and have an async task waiting for the module to return a result. The task that waits for the result never gets the async notification and therefore fails despite the deploy succeeding.

STEPS TO REPRODUCE

Create a new launch config (our new "blue" deploy)

Run the "ec2_asg" task with the new launch config (with async set and "poll: 0")

Have a task later in the playbook waiting on the result

Confirm that the deploy succeeds in AWS (new instances brought up, old ones terminated)

See that the "async_status" job never gets the notification that the deploy has happened

- name: Create integration tier launch configuration
ec2_lc:
name: "{{ environ }}-int-launch-config-{{ current_time }}"
[OMITTED FOR BREVITY]
register: int_launch_configuration

- name: Create Integration Autoscaling group
ec2_asg:
name: "{{ environ }}-int-asg"
launch_config_name: "{{ environ }}-int-launch-config-{{ current_time }}"
vpc_zone_identifier: "{{ int_subnets }}"
health_check_type: "ELB"
health_check_period: 400
termination_policies: "OldestInstance"
replace_all_instances: yes
wait_timeout: 2400
replace_batch_size: "{{ int_replace_batch_size }}"
async: 1000
poll: 0
register: int_asg_sleeper

- name: 'int ASG - check on fire and forget task'
async_status: jid={{ int_asg_sleeper.ansible_job_id }}
register: int_asg_job_result
until: int_asg_job_result.finished
retries: 60
delay: 15

EXPECTED RESULTS

Expected that when the deploy succeeds and the "old" instances are terminated, the Async job gets the message and reports success.

ACTUAL RESULTS

It appears that the "file" mechanism which Python/Ansible use for checking on the status of background jobs fails and the file is never populated, despite the job finishing. Therefore the job polling the file times out eventually.

08:03:34.063 TASK [launch-config : int ASG - check on fire and forget task] *****************
08:03:34.130 fatal: [localhost]: FAILED! => {"failed": true, "msg": "ERROR! The conditional check 'int_asg_job_result.finished' failed. The error was: ERROR! error while evaluating conditional (int_asg_job_result.finished): ERROR! 'dict object' has no attribute 'finished'"}

Copied from original issue: ansible/ansible-modules-core#3625

Issue 2:
It would be nice to be possible to specify vars in tasks files such as the following:

# playbook.yml
- hosts: localhost
tasks:
- include: tasks.yml

# tasks.yml
vars:
- path: /srv/bar

- name: copy file foo
action: copy src=foo dest=$path/foo

- name: copy file bar
action: copy src=bar dest=$path/bar

This allows to bundle common strings inside a tasks file.
Issue 1:
I've been having some issues on 1.3 that I haven't had on 1.2 on the same machine. Seems like libgit2 update has broken something:

(v1.3) pkg> up
Updating registry at `~/.julia/registries/General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
┌ Warning: Some registries failed to update:
│ — /home/jfrigaa/.julia/registries/General — failed to fetch from repo
└ @ Pkg.Types /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1198
Resolving package versions...
Updating `/data/home/jfrigaa/.julia/environments/v1.3/Project.toml`
[no changes]
Updating `/data/home/jfrigaa/.julia/environments/v1.3/Manifest.toml`

Julia Version 1.3.0-rc2.0
Commit a04936e3e0 (2019-09-12 19:49 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, broadwell)

CentOS Linux release 7.5.1804 (Core)

this means I can't download any packages on 1.3. Has anyone had a similar issue? This is a big upgrade blocker for me right now.

Issue 2:
Opening this issue here since I am pretty sure Pkg has not changed anything, maybe this is related to the libgit2 upgrade (#32806)?

$ julia13 -e 'using Pkg; Pkg.Registry.update()'
Updating registry at `~/.julia/registries/General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
┌ Warning: Some registries failed to update:
│ — /home/fredrik/.julia/registries/General — failed to fetch from repo
└ @ Pkg.Types ~/julia13/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:1189

$ julia12 -e 'using Pkg; Pkg.Registry.update()'
Updating registry at `~/.julia/registries/General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`