text:
COPY relative path misparsed

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
While building a container, the process is interrupted at the following step:
# Copy basic configuration files
COPY ./resources/ /

When enabling --log-level debug, the last entry in the log is:

Error: error building at STEP "COPY ./resources/ /": no files found matching "/opt/jenkins/workspace/product-container-builds/container-apache/apache22-centos6/ --label "org.opencontainers.image.source=https:/git.somecompany.eu/scm/division/container-apache.git" --label "org.opencontainers.image.revision=4b37ccb0834a860be8fd82bc460a06ee557c537b" --label "org.opencontainers.build_tool.source=https:/git.somecompany.eu/scm/division/product-container-builder.git" --label "org.opencontainers.build_tool.revision=215901d4e69917954e64c0dd3828c618d33d71ea" --label "org.opencontainers.image.created=2019-11-08 11:43:19+01:00"/resources": no such file or directory

At first glace, for some reason --label and other irrelevant things seem to have slipped in the path.
Steps to reproduce the issue:

The following Dockerfile is used:

FROM centos6:latest

LABEL \
    org.opencontainers.image.description="Apache Intermediate Image"

# Allow specifying a repository base url and config
ARG REPOURL
ARG LOCAL_REPO_CONFIG

# Copy Repository template
RUN echo "${LOCAL_REPO_CONFIG}" | base64 -d > /etc/yum.repos.d/local-repo.repo

# Make REPOURL value available to the Yum Repo template
RUN echo "${REPOURL}" > /etc/yum/vars/repourl

# Install software packages
RUN yum makecache; \
    time yum install -y \
        httpd \
        httpd-devel \
        httpd-tools \
        mod_ssl \
        mod_authnz_crowd \
        jakarta-commons-httpclient; \
    yum clean all; \
    rm -rf /var/cache/yum;

# Remove default configuration
RUN rm -fr /etc/httpd/conf.d/*

# Copy basic configuration files
COPY ./resources/ /

# Symlink access and error logs to stout and sterr
RUN ln -sf /dev/stdout /var/log/httpd/access_log; ln -sf /dev/stderr /var/log/httpd/error_log

# Request Runtime engine to expose the listening port of the application
EXPOSE 80
EXPOSE 443

CMD ["/usr/sbin/httpd","-D", "FOREGROUND"]

The command used to build (some variables are not expanded because they can't be used for reproducability):

podman build
--build-arg REPOURL="${REPOURL}"
--build-arg LOCAL_REPO_CONFIG="${REPO_CONFIG}"
--log-level debug
--label "org.opencontainers.image.ref.name=${CONTAINER_NAME}:${CONTAINER_TAG}"
--label "org.opencontainers.image.title=${CONTAINER_NAME}"
"${CUSTOM_LABELS}"
--iidfile ${CONTAINER_NAME}.id
--logfile ${CONTAINER_NAME}.log
--force-rm
--no-cache
--tag "${CONTAINER_NAME}:${CONTAINER_TAG}"
-f Dockerfile
.
Describe the results you received:
The container is unable to be built successfully
Describe the results you expected:
Podman copies the files in ./resources and recreates the folder structure inside the container
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.4.4
RemoteAPI Version:  1
Go Version:         go1.10.3
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.10.3
  podman version: 1.4.4
host:
  BuildahVersion: 1.9.0
  Conmon:
    package: podman-1.4.4-4.el7.centos.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 0.3.0, commit: unknown'
  Distribution:
    distribution: '"centos"'
    version: "7"
  MemFree: 2782011392
  MemTotal: 8201572352
  OCIRuntime:
    package: containerd.io-1.2.10-3.2.el7.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8+dev
      commit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
      spec: 1.0.1-dev
  SwapFree: 3999264768
  SwapTotal: 3999264768
  arch: amd64
  cpus: 2
  hostname: platojenkslave4
  kernel: 3.10.0-1062.4.1.el7.x86_64
  os: linux
  rootless: true
  uptime: 191h 31m 8.7s (Approximately 7.96 days)
registries:
  blocked: null
  insecure: null
  search:
  - artifactory.somecompany.eu
  - docker.io
store:
  ConfigFile: /opt/jenkins/.config/containers/storage.conf
  ContainerStore:
    number: 5
  GraphDriverName: vfs
  GraphOptions: null
  GraphRoot: /opt/jenkins/.local/share/containers/storage
  GraphStatus: {}
  ImageStore:
    number: 35
  RunRoot: /run/user/1000
  VolumePath: /opt/jenkins/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.4.4-4.el7.centos.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Centos 7.7 running on a vSphere VM.

@TomSweeneyRedHat PTAL

@carroarmato0 I've tried using your Dockerfile with upstream Buildah and I'm seeing a different error:
STEP 9: COPY ./resources/ /
DEBU COPY []string(nil), imagebuilder.Copy{FromFS:false, From:"", Src:[]string{"./resources/"}, Dest:"/", Download:false, Chown:""}
DEBU error building at step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:copy Args:[./resources/ /] Flags:[] Attrs:map[] Message:COPY ./resources/ / Original:COPY ./resources/ /}: no files found matching "/root/resources": no such file or directory
error building at STEP "COPY ./resources/ /": no files found matching "/root/resources": no such file or directory
[root@localhost ~]#

Which in my case anyway is valid as I don't have a /root/resources directory.  I don't see a command in your Dockerfle that I suspect would create that directory, am I missing something?

@carroarmato0 I've tried using your Dockerfile with upstream Buildah and I'm seeing a different error:
STEP 9: COPY ./resources/ /
DEBU COPY []string(nil), imagebuilder.Copy{FromFS:false, From:"", Src:[]string{"./resources/"}, Dest:"/", Download:false, Chown:""}
DEBU error building at step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:copy Args:[./resources/ /] Flags:[] Attrs:map[] Message:COPY ./resources/ / Original:COPY ./resources/ /}: no files found matching "/root/resources": no such file or directory
error building at STEP "COPY ./resources/ /": no files found matching "/root/resources": no such file or directory
[root@localhost ~]#

Which in my case anyway is valid as I don't have a /root/resources directory. I don't see a command in your Dockerfle that I suspect would create that directory, am I missing something?

So the way I envisioned it to work is having Jenkins pull down a Git repository in a Job.
The structure looks like this:
.
├── Dockerfile
├── Jenkinsfile
└── resources
    └── etc
        └── httpd
            └── conf
                ├── common
                │   ├── status.conf
                │   └── stealth.conf
                └── httpd.conf

The behavior I have with Docker, is that the contents or the resources folder, being applied to "/", results in the configuration files (status.conf, stealth.conf and httpd.conf) being copied inside the container in /etc/httpd/conf/... etc.
I'm not sure if this is a different behavior in buildah.
But the output of the error message makes it look like something went wrong with parsing the full path to the resources folder.

@carroarmato0 Maybe I've late Friday afternoon brain, but the message, although messed up, seems to be saying it can't find the resource directory in that last bit.  I noticed you have an older version of Podman/Buildah.  Any chance you could upgrade and try again?

@carroarmato0 Maybe I've late Friday afternoon brain, but the message, although messed up, seems to be saying it can't find the resource directory in that last bit. I noticed you have an older version of Podman/Buildah. Any chance you could upgrade and try again?

Already 10pm over here, brain definitely set in weekend mode :)
Using Podman for a client, I suspect they want to keep things as vanilla as possible (in this case, whatever CentOS makes available in the repo's on 7.7).
I do believe I can find rpm's for podman 1.6.2 and buildah 1.11.4 from here: https://buildlogs.centos.org/centos/7/virt/x86_64/container/ which I could try out and see what happens.
I wonder though on the other hand if perhaps there's something off about the current directory/context in which Buildah is finding itself in.
I'll only be able to give this some further testing on Tuesday with a newer version.

Thanks @carroarmato0 !  FWIW, unless you want to play with or use Buildah directly, you should only need the Podman rpm from there, that should be enough.   The context directory might be it too, you'd need to be in the same directory as the Dockerfile per your tree above.
Enjoy the weekend and thanks for the help chasing this.

The packages from that link are unusable due to the absence of the libvarlink-util dependency.
Ended up using most packages coming from https://cbs.centos.org.
When trying to use podman I realized the switch to crun instead of runc.
#podman --version && podman info
podman version 1.6.2
Error: could not get runtime: default OCI runtime "crun" not found: invalid argument

I fear this is going to become a slippery slope in Centos 7.7 . Will try reverting and taking a closer look to see if it's really not something weird with the context/path which podman is excuted in.

After some more testing I figured there was something wrong with  "${CUSTOM_LABELS}".
This variable is injected as a parameter to podman. After inspecting it, I don't seem to see anything weird with it.
  podman build \
    --build-arg REPOURL="${REPOURL}" \
    --build-arg LOCAL_REPO_CONFIG="${REPO_CONFIG}" \
    ${DEBUG_STRING} \
    --label "org.opencontainers.image.ref.name=${CONTAINER_NAME}:${CONTAINER_TAG}" \
    --label "org.opencontainers.image.title=${CONTAINER_NAME}" \
    "${CUSTOM_LABELS}" \
    --iidfile ${CONTAINER_NAME}.id \
    --logfile ${CONTAINER_NAME}.log \
    --force-rm \
    --no-cache \
    --tag "${CONTAINER_NAME}:${CONTAINER_TAG}" \
    -f Dockerfile \
    .

CUSTOM_LABELS resolves to:
 --label 'org.opencontainers.image.source=https://git.somecompany.eu/scm/somedivision/container-apache.git' --label 'org.opencontainers.image.revision=4b37ccb0834a860be8fd82bc460a06ee557c537b' --label 'org.opencontainers.build_tool.source=https://git.somecompany.eu/scm/somedivision/product-container-builder.git' --label 'org.opencontainers.build_tool.revision=215901d4e69917954e64c0dd3828c618d33d71ea' --label 'org.opencontainers.image.created=2019-11-08 11:43:19+01:00'
So apparently this is not a context/path issue. Not really sure if there's a subtle issue I'm looking over, max parameter length reached? Or podman getting confuse by too many parameters

I'm going to close this issue as it's clear that there's something wrong with how the values are being passed to podman's commandline arguments, rather than something going wrong with podman itself. Thanks for taking the time to have a look.

authors: TomSweeneyRedHat carroarmato0 mheon

repo: containers/libpod


text:
[WIP] tests: fix rootless tests

based on #2695

root tests are passing!
/cc @baude @rhatdan
let's merge this :-)

LGTM

/lgtm

SUCCESS! -- 463 Passed | 0 Failed | 3 Flaked | 0 Pending | 159 Skipped
Wow that's really nice to see!

source: gharchive/pull-request

authors: baude cevich giuseppe rhatdan

license_type: permissive

license_source: github-api


text:
Update mdbook docs and Add doc link in the Readme

This adds the final documentation for the mdbook documentation itself, as well as adds the link for it in the Readme

Codecov Report

Merging #565 (b6fb530) into main (ecb8bb8) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #565   +/-   ##
=======================================
  Coverage   61.13%   61.14%
=======================================
  Files          85       85
  Lines       12564    12564
=======================================
+ Hits         7681     7682    +1
+ Misses       4883     4882    -1

repo: containers/youki


text:
Fix kubernetes path prefix rule with rewrite-target

When rewrite-target is specified, any existing PathPrefix rule is
removed. Hence an ingress with rewrite-target is always matched
for the same host regardless of path prefix.

I think this makes sense.
@dtomcej @emilevauge WDYT?

I approved because I can't think that the code would be intended to function the way it was written :P I assume that @cheungpat's PR was what was intended.

@ldez do we plan to make another 1.4 patch release, or is it okay to let the fix go into the upcoming 1.5 / master?

Thanks for merging the pull request!

authors: cheungpat dtomcej timoreimann

repo: containous/traefik

license: MIT


text:
fix: no embedded entries check rich text commands [TOL-273]

Rich Text Editor crashes anytime a customer types "/", when the rich text field does not allow embedded entries in validation

LGTM, does this add any TS errors though? If so we can just move the check for commandItems.length in CommandList up above the useCommandList call

Unfortunately we can not do that.. hooks can not be called conditionally and must be called in the exact same order in every component render.
I don't see any typescript errors though

when the rich text field does not allow embedded entries in validation

@YvesRijckaert Do you mean neither inline nor blocks? Wouldn't it make more sense then to not add the mark in the first place on / ?

when the rich text field does not allow embedded entries in validation

@YvesRijckaert Do you mean neither inline nor blocks? Wouldn't it make more sense then to not add the mark in the first place on / ?

Yes that's what I mean. Your comment makes sense, but we do not have access to commandItems in the onKeyDown handler, so how would you check if there are any available blocks?

when the rich text field does not allow embedded entries in validation

@YvesRijckaert Do you mean neither inline nor blocks? Wouldn't it make more sense then to not add the mark in the first place on / ?

I think the listening logic would have to be a little spaghetti-ish if we were to prevent the mark in the first place, or else we'd have to run useCommands() twice which could have a performance impact (how much of an impact does getCachedContentTypes() have?)

repo: contentful/field-editors


text:
chore: upgrade dependencies [EXT-4789]

Can upgrade package-lock (1,158 additions and 8,809 deletions) now that node version is updated

i think this is obsolete now with my PR that was just merged

authors: ghepting jjolton-contentful

repo: contentful/node-apps-toolkit


text:
adopt errors in the stdout of a fork

make them error apps

source: gharchive/issue

repo: contexttesting/zoroaster


text:
Malformed stop-parameter on ollama API Requenst (quotes included "[INST]" instead of [INST])

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[x] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows 10
- Continue: 0.8.24
- IDE: VSCode 1.88.1

Description
The stop parameter in the API request (for the chat window) is generated incorrectly, resulting in incorrect behaviour, since the stop-parameter is not recognized by the ollama provider.
I noticed this when using the Dolphin-Mistral model, which uses <|im_end|> as a stop parameter. In the response, the <|im_end|> always appears at the end of the generated output, which should not happen.
To reproduce

Go to the Continue Settings.
Add the Model

  {
      "model": "AUTODETECT",
      "title": "Ollama",
      "apiBase": "http://localhost:11434",
      "provider": "ollama"
    }

In the Dropdown select dolphin-mistral:latest
Enter "Hello" in the Chat and you will get an answer including the stop-string

Log output
I have recorded the http-traffic with wireshark with mistral and dolphin-mistral (which uses diffrent stop parameters). In both cases you see the stop strings with escaped quotes.
{"model":"mistral:latest","raw":true,"keep_alive":1800,"options":{"stop":["\"[INST]\"","\"[/INST]\""],"num_ctx":4096},"messages":[{"role":"user","content":"Hello"}]}

{"model":"dolphin-mistral:latest","raw":true,"keep_alive":1800,"options":{"stop":["\"<|im_start|>\"","\"<|im_end|>\""],"num_ctx":4096},"messages":[{"role":"user","content":"Hello"}]}

It should be:
{"model":"dolphin-mistral:latest","raw":true,"keep_alive":1800,"options":{"stop":["<|im_start|>","<|im_end|>"],"num_ctx":4096},"messages":[{"role":"user","content":"Hello"}]}

@TheMasterFX thanks for pointing that out! I just fixed it here (https://github.com/continuedev/continue/commit/94b44603612ad47b7456c06a762c646c1c803096) and it'll be in the next pre-release version

authors: TheMasterFX sestinj

repo: continuedev/continue


text:
Using + should add a model to your config, not replace it

Describe the bug
I had GPT-4 set up with Continue. Then, I tried to add a Code Llama by clicking the + button, and it completely replaced my GPT-4 config settings when I selected TogetherAPI.
To Reproduce
Steps to reproduce the behavior:

Set up GPT-4 config
Click on + button and selected another model to add
See it completely replace your existing default model config

fixed!

authors: TyDunn sestinj


text:
wait_interval cannot be set

It's seems that I cannot set the wait_interval to a custom value. If I set it to 20 in my github workflow, it still uses the default of 10 seconds.
I'm pretty new to github actions, but I would guess the problem is, that entrypoint.sh#L16 wants to read the environment variable "INPUT_WAITING_INTERVAL" instead of the declared action input wait_interval in action.yml#L35.

Yes, @patrick1990 you are correct, I just check the documentation; which says that a lowercase input variable is converted to uppercase and prepended with "INPUT_". I hope for a quick fix :)

It looks like this is the issue addressed by the first commit in #34. Perhaps there's a case for cherry picking that fix separately if the rest of the PR isn't ready for release?

authors: MarkoSagadin patrick1990 smfeest

repo: convictional/trigger-workflow-and-wait


text:
Improve build documentation

Hi,
I'm trying to prepare an arch linux package for this but the build documentation is kinda lacking. Right now I got it boiled down to this:

checkout code
run make prepare (this fails on linux because of different sed implementations and I guess you need node and something called rollup.js too?)
run swift build --configuration release -Xswiftc -static-stdlib
take binary from .build/x86_64-unknown-linux-gnu/release/cook

Regarding sed and Linux, what platform would this work to build on?

Considering swift is an apple centric language I would make an educated guess that it works on mac.

IIRC the problem is that macOS ships with BSD sed while most linuxes ship with GNU sed which are not completely compatible. It seems like using GNU sed on macOS would be as simple as installing gsed with homebrew und using that instead of sed.

@SebRut thanks for bringing this up. I'll add the document shortly. Your flow is completely right, except that you don't need to do step 2: it's only required during development to update inlined assets in code.

I added build instructions https://github.com/cooklang/CookCLI#building-from-source for users. Will close this issue after adding build instructions for developers.

Added contribution guidelines.

authors: Scoder12 SebRut dubadub jsbmg

repo: cooklang/CookCLI


text:
Add option for logging output into a log file

Hello
Can we have such option?
for now, I used AI to edit the script and replaced all "print" functions with this function
def custom_logger(msg):
    with open('/tmp/tomato.log', 'w') as log_file:
        log_file.write(f'{msg}\n')

Or maybe a status function like tomato -status
You may ask why I need the output in a log file? well I'm using the output for a block in DWM bar

So, if it's possible to have such option please do so.
If not, please close the issue.
Thanks in advance.

AI generated code for 'tomato -status"
Output is like: Break/Work Minutes:Secons
#!/usr/bin/env python3
# -*- coding: utf-8 -*-

import sys
import time
import subprocess
import os

WORK_MINUTES = 25
BREAK_MINUTES = 5

# File to store the start time and duration
TIMER_FILE = '/tmp/tomato_timer.txt'

def main():
    try:
        if len(sys.argv) <= 1:
            start_timer(WORK_MINUTES)
            print(f'🍅 tomato {WORK_MINUTES} minutes. Ctrl+C to exit')
            tomato(WORK_MINUTES, 'It is time to take a break')

        elif sys.argv[1] == '-t':
            minutes = int(sys.argv[2]) if len(sys.argv) > 2 else WORK_MINUTES
            start_timer(minutes, 'Work')
            print(f'🍅 tomato {minutes} minutes. Ctrl+C to exit')
            tomato(minutes, 'It is time to take a break')

        elif sys.argv[1] == '-b':
            minutes = int(sys.argv[2]) if len(sys.argv) > 2 else BREAK_MINUTES
            start_timer(minutes, 'Break')
            print(f'🛀 break {minutes} minutes. Ctrl+C to exit')
            tomato(minutes, 'It is time to work')

        elif sys.argv[1] == '-status':
            print_status()

        elif sys.argv[1] == '-h':
            help()

        else:
            help()

    except KeyboardInterrupt:
        print('\n👋 goodbye')
    except Exception as ex:
        print(ex)
        exit(1)

def start_timer(minutes, session_type):
    with open(TIMER_FILE, 'w') as f:
        start_time = time.perf_counter()
        f.write(f'{start_time}\n{minutes * 60}\n{session_type}\n')

def print_status():
    if os.path.exists(TIMER_FILE):
        with open(TIMER_FILE, 'r') as f:
            lines = f.readlines()
            if len(lines) < 3:
                print('No active timer.')
                return
            start_time = float(lines[0].strip())
            duration = float(lines[1].strip())
            session_type = lines[2].strip()
            elapsed = time.perf_counter() - start_time
            remaining = duration - elapsed
            if remaining > 0:
                minutes = int(remaining // 60)
                seconds = int(remaining % 60)
                print(f'{session_type} {minutes}:{seconds:02d}')
            else:
                print('No active timer.')
    else:
        print('No active timer.')

Updated main function to have the ability to set sequence of -t and -b.
Now you can have different time sequence for your break and work session.
Like
tomato -t 50 -b 10 -t 25 -b 5
def main():
    try:
        if len(sys.argv) <= 1:
            start_timer(WORK_MINUTES, 'Work')
            print(f'🍅 tomato {WORK_MINUTES} minutes. Ctrl+C to exit')
            tomato(WORK_MINUTES, 'It is time to take a break')
            start_timer(BREAK_MINUTES, 'Break')
            print(f'🛀 break {BREAK_MINUTES} minutes. Ctrl+C to exit')
            tomato(BREAK_MINUTES, 'It is time to work')

        elif sys.argv[1] in ['-t', '-b']:
            i = 1
            while i < len(sys.argv):
                if sys.argv[i] == '-t':
                    minutes = int(sys.argv[i+1]) if i+1 < len(sys.argv) else WORK_MINUTES
                    start_timer(minutes, 'Work')
                    print(f'🍅 tomato {minutes} minutes. Ctrl+C to exit')
                    tomato(minutes, 'It is time to take a break')
                elif sys.argv[i] == '-b':
                    minutes = int(sys.argv[i+1]) if i+1 < len(sys.argv) else BREAK_MINUTES
                    start_timer(minutes, 'Break')
                    print(f'🛀 break {minutes} minutes. Ctrl+C to exit')
                    tomato(minutes, 'It is time to work')
                i += 2

        elif sys.argv[1] == '-status':
            print_status()

        elif sys.argv[1] == '-h':
            help()

        else:
            help()

    except KeyboardInterrupt:
        print('\n👋 goodbye')
    except Exception as ex:
        print(ex)
        exit(1)

repo: coolcode/tomato-clock


text:
Roster Data stop working

Hi, the data of the 2022 roster is not available anymore.
Thanks

Hi @Soteloemma12! Could you please some details to this? What command are you running and what error are you receiving?

Closing as stale and unable to reproduce. @Soteloemma12 please open a new issue with the details I mentioned above if you are still having problems.


text:
Proposal: Rename theme event and node to "layer"

The theme event and node currently don't work like they do in 1.x, although they can be used to achieve a similar effect.
How they currently work in 2.0 is more like this:
Using Change Theme will show all nodes in "layers" (DialogicDisplay_Theme nodes that have that name configured and all they children). All other "layers" will hide. Nodes that aren't decendants of a layer node won't be effected. Themes are not involved in the node or event.

We decided to rename the concept to Style.
Meaning: Change Style Event a DialogicNode_Style node and Subsystem_Style

Implemented in #1231

authors: Jowan-Spooner thebardsrc

repo: coppolaemilio/dialogic


text:
Play Timeline Error

The problem
Describe the bug
I am unable to test my timeline by hitting "Play Timeline," and the output message indicates failure in loading resources.
To Reproduce
Steps to reproduce the behavior:

Go to dialogic
Create a new timeline
Click "Play Timeline"
See error

Expected behavior
I expected the timeline I am testing to run and see the dialogue in the game.
Screenshots

System (please complete the following information):

OS: Mac
Godot Version: Godot 4 beta 10
Dialogic Version: Dialogic 2 Alpha 5

Solutions
Workaround
Possible fixes

Would be great if you could try again with dialogic 2 alpha 6 on godot 4.0 stable release.

Hi, I tried with dialogic 2 alpha 6 on godot 4.0 stable release. I have no problem running the timeline now, but there are still some errors when the timeline ends.

authors: Jowan-Spooner kittygyj


text:
cargo install error. failed to update submodule examples/cfo/deps/openbook-dex

when I called " cargo install --git https://github.com/coral-xyz/anchor avm --locked --force",
I had tried to git cloen https://github.com/openbook-dex/program, but it indicated me it was a empty repository. I could access github normally. what can I do. It's killing me. The following is the error message.
cargo install --git https://github.com/coral-xyz/anchor avm latest  --locked --force
Updating git repository https://github.com/coral-xyz/anchor
Updating git submodule https://github.com/openbook-dex/program
error：The requested URL returned error: 500 (curl_result = 22, http_code = 500, sha1 = 7d1d41538417aa8721aabea9503bf9d99eab7cc4)
error：Unable to find 7d1d41538417aa8721aabea9503bf9d99eab7cc4 under https://gitclone.com/github.com/openbook-dex/program
Cannot obtain needed object 7d1d41538417aa8721aabea9503bf9d99eab7cc4
error: failed to update submodule examples/cfo/deps/openbook-dex
Caused by:
failed to fetch submodule examples/cfo/deps/openbook-dex from https://github.com/openbook-dex/program
Caused by:
process didn't exit successfully: git fetch --force --update-head-ok 'https://github.com/openbook-dex/program' '+7d1d41538417aa8721aabea9503bf9d99eab7cc4:refs/commit/7d1d41538417aa8721aabea9503bf9d99eab7cc4' (exit status: 128)

Looks like a GitHub API issue, so it resolved itself?

Looks like a GitHub API issue, so it resolved itself?

sorry for replying to you so late, I didn't install anchor in the recommended way. Because I didn't know how to solve this issue even I chatgpt it. I install anchor by building the source code then.

authors: acheroncrypto z-hanwen

repo: coral-xyz/anchor


text:
File upload : files over 120 kB returns 500 error

Hi, I found out files over 120 kB cant be uploaded when coraza is enabled, and it is not about a CRS rule file because I disabled them.
create the file with : dd if=/dev/zero of=file.pdf bs=10K count=13
caddy configuration
	coraza_waf {
			directives `
				SecAction \
					"id:900000,\
					phase:1,\
					nolog,\
					pass,\
					t:none,\
					setvar:tx.blocking_paranoia_level=1"
				SecAction \
					"id:900001,\
					phase:1,\
					nolog,\
					pass,\
					t:none,\
					setvar:tx.detection_paranoia_level=1"
			`
		include coraza.conf
		include coreruleset/crs-setup.conf
	}

coraza.conf
I tried uping SecRequestBodyLimit and setting SecRequestBodyAccess but this has no effect
SecRuleEngine On

SecRequestBodyAccess Off

SecRule REQUEST_HEADERS:Content-Type "(?:application(?:/soap\+|/)|text/)xml" \
     "id:'200000',phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML"

SecRule REQUEST_HEADERS:Content-Type "application/json" \
     "id:'200001',phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=JSON"

SecRequestBodyLimit 131072000000

SecRule REQBODY_ERROR "!@eq 0" \
"id:'200002', phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"

SecRule MULTIPART_STRICT_ERROR "!@eq 0" \
"id:'200003',phase:2,t:none,log,deny,status:400, \
msg:'Multipart request body failed strict validation: \
PE %{REQBODY_PROCESSOR_ERROR}, \
BQ %{MULTIPART_BOUNDARY_QUOTED}, \
BW %{MULTIPART_BOUNDARY_WHITESPACE}, \
DB %{MULTIPART_DATA_BEFORE}, \
DA %{MULTIPART_DATA_AFTER}, \
HF %{MULTIPART_HEADER_FOLDING}, \
LF %{MULTIPART_LF_LINE}, \
SM %{MULTIPART_MISSING_SEMICOLON}, \
IQ %{MULTIPART_INVALID_QUOTING}, \
IP %{MULTIPART_INVALID_PART}, \
IH %{MULTIPART_INVALID_HEADER_FOLDING}, \
FL %{MULTIPART_FILE_LIMIT_EXCEEDED}'"

SecRule MULTIPART_UNMATCHED_BOUNDARY "@eq 1" \
    "id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"

SecRule TX:/^COR_/ "!@streq 0" \
        "id:'200005',phase:2,t:none,deny,msg:'Coraza internal error flagged: %{MATCHED_VAR_NAME}'"

SecResponseBodyAccess On
SecResponseBodyMimeType text/plain text/html text/xml
SecResponseBodyLimit 524288
SecResponseBodyLimitAction ProcessPartial
SecTmpDir /tmp/coraza/tmp
SecDataDir /tmp/coraza/data
SecAuditEngine On
SecAuditLogType concurrent
SecAuditLogStorageDir /var/log/caddy/
SecAuditLogRelevantStatus "^(?:(5|4)(0|1)[0-9])$"
SecArgumentSeparator &
SecCookieFormat 0
SecDefaultAction "phase:1,log,auditlog,pass"
SecDefaultAction "phase:2,log,auditlog,pass"

SecAction \
"id:900220,\
 phase:1,\
 nolog,\
 pass,\
 t:none,\
 setvar:'tx.allowed_request_content_type=|application/x-www-form-urlencoded| |multipart/form-data| |multipart/related| |text/xml| |application/xml| |application/soap+xml| |application/x-amf| |application/json| |application/cloudevents+json| |application/cloudevents-batch+json| |application/octet-stream| |application/csp-report| |application/xss-auditor-report| |text/plain| |application/x-www-form-urlencoded;| |multipart/form-data;| |multipart/related;| |text/xml;| |application/xml;| |application/soap+xml;| |application/x-amf;| |application/json;| |application/cloudevents+json;| |application/cloudevents-batch+json;| |application/octet-stream;| |application/csp-report;| |application/xss-auditor-report;| |text/plain|'"

SecCollectionTimeout 600

SecAction \
    "id:900990,\
    phase:1,\
    nolog,\
    pass,\
    t:none,\
    setvar:tx.crs_setup_version=400"

caddy logs
I get this error when triggering the 500 error (/tmp/coraza/tmp is SecTmpDir) :
http.log.error  open /tmp/coraza/tmp/body2809431227: no such file or directory  {"request": {"remote_ip": "::1", "remote_port": "46222", "proto": "HTTP/1.1", "method": "POST", "host": "[redacted]", "uri": "/fr/imce", "headers": {"Te": ["trailers"], "X-Forwarded-For": ["[redacted]"], "Content-Type": ["multipart/form-data; boundary=---------------------------755505775042860173259666447"], "Origin": ["https://www.bookbeo.com"], "Referer": ["[redacted]/imce"], "X-Forwarded-Proto": ["https"], "X-Requested-With": ["XMLHttpRequest"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:106.0) Gecko/20100101 Firefox/106.0"], "Cookie": [], "Sec-Fetch-Site": ["same-origin"], "X-Forwarded-Host": ["[redacted]"], "X-Request-Id": ["g5hzRLV8qFTs3jo9ZoxVB"], "Accept": ["application/json, text/javascript, */*; q=0.01"], "Sec-Fetch-Mode": ["cors"], "Accept-Language": ["fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3"], "Sec-Fetch-Dest": ["empty"], "Content-Length": ["133737"], "Accept-Encoding": ["gzip, deflate"]}}, "duration": 0.323760727}

Hey @Saperlu thank you for your report. Before debugging, can you validate the directory /tmp/coraza/tmp exists and that the user running caddy has access to write to it?

Well played, this dir was not on the container where I was trying to replicate the bug.
So I tried on the prod container (the dir exists on that container) and it seems that setting SecResponseBodyAccess to Off works. Is there a way to disable this for a custom URI only ?
Also, this shouldn't have this behaviour, I guess, so here are caddy logs :
error	http.log.error	EOF	{"request": {"remote_ip": "172.16.40.100", "remote_port": "65182", "proto": "HTTP/2.0", "method": "POST", "host": "www.bookbeo.com", "uri": "/fr/imce", "headers": {"X-Requested-With": ["XMLHttpRequest"], "Sec-Ch-Ua-Platform": ["\"macOS\""], "Sec-Fetch-Site": ["same-origin"], "Sec-Fetch-Dest": ["empty"], "Content-Length": ["16389"], "Sec-Ch-Ua": ["\"Google Chrome\";v=\"107\", \"Chromium\";v=\"107\", \"Not=A?Brand\";v=\"24\""], "Accept-Encoding": ["gzip, deflate, br"], "Accept-Language": ["fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36"], "Referer": ["https://www.bookbeo.com/fr/imce"], "Sec-Ch-Ua-Mobile": ["?0"], "Origin": ["https://www.bookbeo.com"], "Cookie": [], "Accept": ["application/json, text/javascript, */*; q=0.01"], "Content-Type": ["multipart/form-data; boundary=----WebKitFormBoundaryoiUZBSJxElcPL8SO"], "Sec-Fetch-Mode": ["cors"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "h2", "server_name": "www.bookbeo.com"}}, "duration": 0.241701613, "status": 502, "err_id": "3mucdx5hf", "err_trace": "reverseproxy.statusError (reverseproxy.go:1271)"}

Interesting finding. Worth to check cc @anuraaga @m4tteoP
On Thu, 10 Nov 2022, 14:23 Lucien Charleux, @.***>
wrote:

Well played, this dir was not on the container where I was trying to
replicate the bug.
So I tried on the prod container (the dir exists on that container) and it
seems that setting SecResponseBodyAccess to Off works. Is there a way to
disable this for a custom URI only ?
Also, this shouldn't have this behaviour, I guess, so here are caddy logs :
error	http.log.error	EOF	{"request": {"remote_ip": "172.16.40.100", "remote_port": "65182", "proto": "HTTP/2.0", "method": "POST", "host": "www.bookbeo.com", "uri": "/fr/imce", "headers": {"X-Requested-With": ["XMLHttpRequest"], "Sec-Ch-Ua-Platform": [""macOS""], "Sec-Fetch-Site": ["same-origin"], "Sec-Fetch-Dest": ["empty"], "Content-Length": ["16389"], "Sec-Ch-Ua": [""Google Chrome";v="107", "Chromium";v="107", "Not=A?Brand";v="24""], "Accept-Encoding": ["gzip, deflate, br"], "Accept-Language": ["fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36"], "Referer": ["https://www.bookbeo.com/fr/imce"], "Sec-Ch-Ua-Mobile": ["?0"], "Origin": ["https://www.bookbeo.com"], "Cookie": [], "Accept": ["application/json, text/javascript, /; q=0.01"], "Content-Type": ["multipart/form-data; boundary=----WebKitFormBoundaryoiUZBSJxElcPL8SO"], "Sec-Fetch-Mode": ["cors"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "h2", "server_name": "www.bookbeo.com"}}, "duration": 0.241701613, "status": 502, "err_id": "3mucdx5hf", "err_trace": "reverseproxy.statusError (reverseproxy.go:1271)"}
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza-caddy/issues/29#issuecomment-1310276642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAR7QL2PB7BYZPVGU2LWHTZMZANCNFSM6AAAAAAR4M3BIM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Caddy connector is using an old version of coraza. There is a draft PR to upgrade to the new immutability pattern.

Fully Upgraded in https://github.com/corazawaf/coraza-caddy/releases/tag/v1.2.2

Could you please check again @Saperlu ?

We completely rewrite the connector. Could you please try it again?

authors: Saperlu jcchavezs jptosso

repo: corazawaf/coraza-caddy


text:
Add first draft of Alpha deployment instructions

Preview here: https://nadine.preview.docs.r3.com/en/platform/corda/5.0-alpha/deploying/overview.html

I've added suggested changes for most of the updates that I made in the RC-04 deployment doc but there is a new section Example deployment configuration that also needs adding.
As an aside: has the house style changed from sentence case for headings?

Thanks, @davidcurrie. I'll run through these and apply in the morning. Good spot regarding the headings case! No-one in the current TW team agreed with the previous style of sentence case so we are indeed using title case in Corda 5 documentation. (At present, it was considered too large a task to correct for Corda 4 content.)

repo: corda/corda-docs-portal


text:
Give the ability to override service name separately

This would come in handy if we want to adopt an existing service

Please update this to be mergeable and I will merge it.

authors: haad livyfu

repo: coredns/helm


text:
Fix .visuallyhidden not being actually hidden

Refs #106 and #104

Looks good to me.
@colinrotherham, does this still work for your accessibility requirements?

Hi @jlbooker,
I'm against embedding CSS like this in JavaScript, for the following reasons:

In future, an alternative "visually hidden" snippet may be recommended, making this superfluous.
Embedding CSS stops us providing tailored Firefox, legacy IE or mobile styling behind media queries (we're stuck with these rules and only these)
Some users may prefer to see the status.

This is a job for CSS, not script.

@colinrotherham I completely agree that this is better off done with css. But, for better or for worse, this is not how typeahead.js currently works. Just search for '.css' calls over the code base.
What happened with 0.11.1 release was a kind of semver abuse ("patch" and "minor" version number updates must be backwards compatible). Users already depend on typeahead.js doing it's stuff with inline css and do no expect elements popping out of nowhere with minor version update. Moreover, 0.11.1 does not provide any css files one could include to make typehead work as before out of the box.
Changing approach to styling (disabling all inline styles and requiring users to include a css file) is feasible for a minor update behind an option (disabled by default for smooth updates) or for a major update (then we could explicitly state that user must include provided or custom css).

@futpib Agreed.
The status message should really have been a new feature, under a major release number.
You'll need a Windows machine running a JAWS 40 minute trial or VoiceOver for Mac to verify this works before merging. Does everything work still?
Like the other .css() (especially font styling) we can consider consolidating those into a future release.

@futpib The semver abuse is my fault. I didn't realize the message was a breaking change, thus the minor version bump from 1.0.1 to 1.1.0.
I'm in favor of merging this fix now to fix what we broke, and creating a separate issue to look at pulling the styles out into an actual stylesheet in a separate (major version numbered) release.
Does that sound good to everyone?

@jlbooker Sounds great.

@futpib Just published version 1.1.1 on NPM. Have a look!

@jlbooker can you please create a github release?

@ricardobrandao Done! Sorry about that!

authors: colinrotherham futpib jlbooker ricardobrandao

license: mit

license_source: bigquery


text:
Wrong public path

Hi, I think I found a bug. In my project I changed a name of public directory via nuxt.config dir.public to Public and I see that build process do not take into that name. As a result, the font file is missing in the build

fixed in 1.1.0
https://github.com/coremyslo/nuxt-icon-font/pull/10

repo: coremyslo/nuxt-icon-font


text:
Fix typo

Change 'can we done' to 'can be done'.

Thanks!

authors: gosharplite robszumski

repo: coreos/docs


text:
e2e flake: early operator "shutting down, got signal: Terminated"

When e2e finishes, we will delete the pod. But in flaky tests, we saw that operator was terminated earlier than e2e finished.

to track:
logs:
https://console.cloud.google.com/logs/viewer?project=coreos-k8s-scale-testing&authuser=1&minLogLevel=0&expandAll=false&resource=container%2Fcluster_name%2Fjenkins2%2Fnamespace_id%2Fe2e-etcd-operator-1008&advancedFilter=resource.type%3D"container"
resource.labels.cluster_name%3D"jenkins"
resource.labels.namespace_id%3D"e2e-etcd-operator-flaketest-1592"
resource.labels.pod_id%3D"etcd-operator"
NOT "reconciling"

&timestamp=2017-02-03T13:34:34.000000000Z
e2e finish time:
time="2017-02-03T13:39:48Z" level=info msg="e2e teardown successfully"

Not seen anymore. Closing old flaky issue

repo: coreos/etcd-operator


text:
all peers think all other peer connections are unhealthy

Standing up an etcd 2.1.1 cluster on RHEL6 results in each etcd reporting this:
rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy

for every other node in the cluster (with different node IDs for each other node, of course).  All nodes have problems with every other node.  The etcdctl cluster-health command reports messages like raft is making progress [match: 146378->146380] for all nodes, with identical values for each node.  The values continue increasing at a rate of roughly 12-13 every five seconds.  For a 5-node cluster running on five separate machines, it therefore looks like this:
cluster is healthy: raft is making progress [commit index: 146500->146502]
leader is 126d709c680387a5
member 126d709c680387a5 is healthy: raft is making progress [match: 146500->146502]
member 70e10bfbc55ed7a6 is healthy: raft is making progress [match: 146500->146502]
member a238e808898348 is healthy: raft is making progress [match: 146500->146502]
member aba177af7981101a is healthy: raft is making progress [match: 146500->146502]
member fe214d33383f27e0 is healthy: raft is making progress [match: 146500->146502]

I can reproduce this down to a 2-node cluster running on different ports on the same machine.  I've packaged up my local builds of go and etcd (both from current git tags) in RPMs, and would be happy to provide those RPMs (offline; I can't make them public) to someone who wanted to duplicate this setup using a throw-away CentOS 6 build or something.  There's a little more information at https://groups.google.com/forum/#!topic/etcd-dev/elCUk0rQ1CE; please ask if I can provide anything else useful.
Version information:
$ /srv/etcd/bin/etcd --version
etcd Version: 2.1.1+git
Git SHA: 487639b
Go Version: go1.4
Go OS/Arch: linux/amd64

$ lsb_release -a
LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch    Distributor ID: RedHatEnterpriseServer
Description:    Red Hat Enterprise Linux Server release 6.6 (Santiago)
Release:        6.6
Codename:       Santiago

$ uname -a
Linux st74cf01 2.6.32-504.12.2.el6.x86_64 #1 SMP Sun Feb 1 12:14:02 EST 2015 x86_64 x86_64 x86_64 GNU/Linux

Example of starting a 2-node cluster which consistently exhibits the behavior on this system:
node 1:
/srv/etcd/bin/etcd \
  --name $(hostname -s)1 \
  --data-dir /tmp/etcd_localtestt_1 \
  --listen-peer-urls   "http://$(hostname -s):2390" \
  --listen-client-urls "http://localhost:2389,http://$(hostname -s):2389" \
  --advertise-client-urls "http://$(hostname -s):2389" \
  \
  --initial-cluster-token 'localtest' \
  --initial-advertise-peer-urls "http://$(hostname -s):2390" \
  --initial-cluster "$(hostname -s)1=http://$(hostname -s):2390,$(hostname -s)2=http://$(hostname -s):2391" \
  --initial-cluster-state 'new'
2015/08/6 14:09:53 etcdmain: setting maximum number of CPUs to 1, total number of available CPUs is 4
2015/08/6 14:09:53 etcdmain: listening for peers on http://st74cf01:2390
2015/08/6 14:09:53 etcdmain: listening for client requests on http://localhost:2389
2015/08/6 14:09:53 etcdmain: listening for client requests on http://st74cf01:2389
2015/08/6 14:09:53 etcdserver: name = st74cf011
2015/08/6 14:09:53 etcdserver: data dir = /tmp/etcd_localtestt_1
2015/08/6 14:09:53 etcdserver: member dir = /tmp/etcd_localtestt_1/member
2015/08/6 14:09:53 etcdserver: heartbeat = 100ms
2015/08/6 14:09:53 etcdserver: election = 1000ms
2015/08/6 14:09:53 etcdserver: snapshot count = 10000
2015/08/6 14:09:53 etcdserver: advertise client URLs = http://st74cf01:2389
2015/08/6 14:09:53 etcdserver: initial advertise peer URLs = http://st74cf01:2390
2015/08/6 14:09:53 etcdserver: initial cluster = st74cf011=http://st74cf01:2390,st74cf012=http://st74cf01:2391
2015/08/6 14:09:53 etcdserver: starting member 8887eaf3e329a3f8 in cluster 9e94874682ff203f
2015/08/6 14:09:53 raft: 8887eaf3e329a3f8 became follower at term 0
2015/08/6 14:09:53 raft: newRaft 8887eaf3e329a3f8 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/08/6 14:09:53 raft: 8887eaf3e329a3f8 became follower at term 1
2015/08/6 14:09:53 etcdserver: starting server... [version: 2.1.1+git, cluster version: to_be_decided]
2015/08/6 14:09:53 etcdserver: added member 830bc2abd256fd30 [http://st74cf01:2391] to cluster 9e94874682ff203f
2015/08/6 14:09:53 etcdserver: added local member 8887eaf3e329a3f8 [http://st74cf01:2390] to cluster 9e94874682ff203f
2015/08/6 14:09:53 rafthttp: the connection with 830bc2abd256fd30 became active
2015/08/6 14:09:54 raft: 8887eaf3e329a3f8 [term: 1] received a MsgVote message with higher term from 830bc2abd256fd30 [term: 4]
2015/08/6 14:09:54 raft: 8887eaf3e329a3f8 became follower at term 4
2015/08/6 14:09:54 raft: 8887eaf3e329a3f8 [logterm: 1, index: 2, vote: 0] voted for 830bc2abd256fd30 [logterm: 1, index: 2] at term 4
2015/08/6 14:09:54 raft: raft.node: 8887eaf3e329a3f8 elected leader 830bc2abd256fd30 at term 4
2015/08/6 14:09:54 etcdserver: published {Name:st74cf011 ClientURLs:[http://st74cf01:2389]} to cluster 9e94874682ff203f
2015/08/6 14:09:54 etcdserver: set the initial cluster version to 2.1.0
2015/08/6 14:10:23 rafthttp: the connection to peer 830bc2abd256fd30 is unhealthy
2015/08/6 14:10:53 rafthttp: the connection to peer 830bc2abd256fd30 is unhealthy
2015/08/6 14:11:23 rafthttp: the connection to peer 830bc2abd256fd30 is unhealthy
2015/08/6 14:11:53 rafthttp: the connection to peer 830bc2abd256fd30 is unhealthy

node 2:
/srv/etcd/bin/etcd \
  --name $(hostname -s)2 \
  --data-dir /tmp/etcd_localtestt_2 \
  --listen-peer-urls   "http://$(hostname -s):2391" \
  --listen-client-urls "http://localhost:2388,http://$(hostname -s):2388" \
  --advertise-client-urls "http://$(hostname -s):2389" \
  \
  --initial-cluster-token 'localtest' \
  --initial-advertise-peer-urls "http://$(hostname -s):2391" \
  --initial-cluster "$(hostname -s)1=http://$(hostname -s):2390,$(hostname -s)2=http://$(hostname -s):2391" \
  --initial-cluster-state 'new'
2015/08/6 14:09:50 etcdmain: setting maximum number of CPUs to 1, total number of available CPUs is 4
2015/08/6 14:09:50 etcdmain: listening for peers on http://host1:2391
2015/08/6 14:09:50 etcdmain: listening for client requests on http://localhost:2388
2015/08/6 14:09:50 etcdmain: listening for client requests on http://host1:2388
2015/08/6 14:09:50 etcdserver: name = host12
2015/08/6 14:09:50 etcdserver: data dir = /tmp/etcd_localtestt_2
2015/08/6 14:09:50 etcdserver: member dir = /tmp/etcd_localtestt_2/member
2015/08/6 14:09:50 etcdserver: heartbeat = 100ms
2015/08/6 14:09:50 etcdserver: election = 1000ms
2015/08/6 14:09:50 etcdserver: snapshot count = 10000
2015/08/6 14:09:50 etcdserver: advertise client URLs = http://host1:2389
2015/08/6 14:09:50 etcdserver: initial advertise peer URLs = http://host1:2391
2015/08/6 14:09:50 etcdserver: initial cluster = host11=http://host1:2390,host12=http://host1:2391
2015/08/6 14:09:50 etcdserver: starting member 830bc2abd256fd30 in cluster 9e94874682ff203f
2015/08/6 14:09:50 raft: 830bc2abd256fd30 became follower at term 0
2015/08/6 14:09:50 raft: newRaft 830bc2abd256fd30 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/08/6 14:09:50 raft: 830bc2abd256fd30 became follower at term 1
2015/08/6 14:09:50 etcdserver: starting server... [version: 2.1.1+git, cluster version: to_be_decided]
2015/08/6 14:09:50 rafthttp: failed to dial 8887eaf3e329a3f8 on stream MsgApp v2 (dial tcp 10.97.50.35:2390: connection refused)
2015/08/6 14:09:50 etcdserver: added local member 830bc2abd256fd30 [http://host1:2391] to cluster 9e94874682ff203f
2015/08/6 14:09:50 rafthttp: failed to dial 8887eaf3e329a3f8 on stream Message (dial tcp 10.97.50.35:2390: connection refused)
2015/08/6 14:09:50 etcdserver: added member 8887eaf3e329a3f8 [http://host1:2390] to cluster 9e94874682ff203f
2015/08/6 14:09:52 raft: 830bc2abd256fd30 is starting a new election at term 1
2015/08/6 14:09:52 raft: 830bc2abd256fd30 became candidate at term 2
2015/08/6 14:09:52 raft: 830bc2abd256fd30 received vote from 830bc2abd256fd30 at term 2
2015/08/6 14:09:52 raft: 830bc2abd256fd30 [logterm: 1, index: 2] sent vote request to 8887eaf3e329a3f8 at term 2
2015/08/6 14:09:52 rafthttp: failed to write 8887eaf3e329a3f8 on pipeline (dial tcp 10.97.50.35:2390: connection refused)
2015/08/6 14:09:53 raft: 830bc2abd256fd30 is starting a new election at term 2
2015/08/6 14:09:53 raft: 830bc2abd256fd30 became candidate at term 3
2015/08/6 14:09:53 raft: 830bc2abd256fd30 received vote from 830bc2abd256fd30 at term 3
2015/08/6 14:09:53 raft: 830bc2abd256fd30 [logterm: 1, index: 2] sent vote request to 8887eaf3e329a3f8 at term 3
2015/08/6 14:09:53 rafthttp: the connection with 8887eaf3e329a3f8 became active
2015/08/6 14:09:54 raft: 830bc2abd256fd30 is starting a new election at term 3
2015/08/6 14:09:54 raft: 830bc2abd256fd30 became candidate at term 4
2015/08/6 14:09:54 raft: 830bc2abd256fd30 received vote from 830bc2abd256fd30 at term 4
2015/08/6 14:09:54 raft: 830bc2abd256fd30 [logterm: 1, index: 2] sent vote request to 8887eaf3e329a3f8 at term 4
2015/08/6 14:09:54 raft: 830bc2abd256fd30 received vote from 8887eaf3e329a3f8 at term 4
2015/08/6 14:09:54 raft: 830bc2abd256fd30 [q:2] has received 2 votes and 0 vote rejections
2015/08/6 14:09:54 raft: 830bc2abd256fd30 became leader at term 4
2015/08/6 14:09:54 raft: raft.node: 830bc2abd256fd30 elected leader 830bc2abd256fd30 at term 4
2015/08/6 14:09:54 etcdserver: setting up the initial cluster version to 2.1.0
2015/08/6 14:09:54 etcdserver: published {Name:host12 ClientURLs:[http://host1:2389]} to cluster 9e94874682ff203f
2015/08/6 14:09:54 etcdserver: set the initial cluster version to 2.1.0
2015/08/6 14:10:20 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy
2015/08/6 14:10:50 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy
2015/08/6 14:11:20 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy
2015/08/6 14:11:50 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy
2015/08/6 14:12:20 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy
2015/08/6 14:12:50 rafthttp: the connection to peer 8887eaf3e329a3f8 is unhealthy

First, you are trying current master. It is etcd 2.1.1 + git, not the release version of etcd.
Second, I failed to reproduce your issue on my local mac. The behavior is a little bit wried to me. Are you able to reproduce the issue on other linux distro so that I can try to reproduce?

I checked out the 2.1.1 tag from git, so I assumed that matched the current release. :) Was that a bad assumption?
I do not have access to any other distributions at work; we are a RHEL shop. But it should be identical to CentOS 6, which you can get for free. I can test on Ubuntu at home, but I know that using the release tarball on two Ubuntu systems (one old, one new)  with Ubuntu's packaged golang does work.

I can test on Ubuntu at home, but I know that using the release tarball on two Ubuntu systems (one old, one new) with Ubuntu's packaged golang does work.

Try to test on Ubuntu with the same git tag. The release tar and master are different. I will try to set up CentOS to reproduce soon.

Apparently you're right - the tag is not like the release.  I pulled the release file from //github.com/coreos/etcd/releases/download/v2.1.1/etcd-v2.1.1-linux-amd64.tar.gz and it's working properly as a 2-node local cluster which fails under the one I built from the tag.
So I got the source tarball from https://github.com/coreos/etcd/archive/v2.1.1.tar.gz, and ran the build script.  That resulting binary also does not exhibit the same problem.  So, it's apparently the etcd code from the tag, not my machine, hardware, or go implementation.
I'll use the git tag on my Ubuntu machine at home sometime this evening (presuming my wife hasn't built a list of things that I need to do tonight :)) and see if I can reproduce the problem, though.

my machine, hardware, or go implementation.

I am not sure. We added a stricter connection checker in the recent release. It works fine on my local env. I would suggest to check it on ubuntu. And as I said, I will try to reproduce it on CentOS6 on ec2.

I just updated etcd on one node from the five-node cluster which has been griping since it was stood up yesterday, and the cluster-health command on that node is showing all nodes as healthy.  It is not emitting the "connection to peer is unhealthy" messages either.  All of the other nodes still complain about the updated node, though.

@dannysauer Can you try with current master again?

$ git describe
v2.1.1-114-g668a8a8
The individual nodes aren't dumping out the "unhealthy" logs anymore, but I still see this in the cluster-health output on both nodes:
cluster is healthy: raft is making progress [commit index: 297->299]
leader is 8887eaf3e329a3f8
member 830bc2abd256fd30 is healthy: raft is making progress [match: 297->299]
member 8887eaf3e329a3f8 is healthy: raft is making progress [match: 297->299]

@dannysauer What is wrong with the output? It shows your member is healthy.

@dannysauer It just explains why your cluster is healthy and why each member is healthy. I think your problem is solved. : )

Oh, I expected that the values would eventually converge, and that it would just say "member xxx is healthy" like in the older version.  Is it expected that it will always give the "is making progress" message now?

@dannysauer Yes. We will cover it by doc when we release 2.2.

Awesome.  Thanks for the work. :)

repo: coreos/etcd


text:
Question: Why support v2 Storage and API in 3.2?

Given the v2 api is deprecated, what's the reasoning for continuing to support it in 3.2?

There's a period between deprecation and actually removing the feature. Not everyone has migrated to using the v3 API (and probably won't, for that matter)

@davissp14 if you just want to disable the v2 endpoint, it can be done by passing --enable-v2=false to the etcd server...

@heyitsanthony Perfect, thank you!


text:
docs/benchmark: add 2.2.0-rc memory usage benchmark

It records the memory usage for different average value size, and
records the data size limitation.
for #2473

I ran the tests on the cloud environment and updated the doc. PTAL.

LGTM. I think this should be very helpful!

OK. LGTM


text:
Failed to install kube-flannel add-on on kubeadm

I try to install flannel addon after installing kubeadm but there got "CrashLoopBackOff" when get pods.
Expected Behavior
kube-flannel-ds- pod's status becomes running.
Current Behavior
kcm logs kube-flannel-ds-hdqb4
Error from server (BadRequest): a container name must be specified for pod kube-flannel-ds-hdqb4, choose one of: [kube-flannel install-cni]

Steps to Reproduce
YAML link is:
https://github.com/coreos/flannel/blob/master/Documentation/kube-flannel.yml
kubectl apply -f kube-flannel.yml
Your Environment

Flannel version:
dc images | g flannel
quay.io/coreos/flannel                                   v0.7.1-amd64        cd4ae0be5e1b        5 weeks ago         77.76 MB
Kubernetes version :
kubeadm version
kubeadm version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.3", GitCommit:"0480917b552be33e2dba47386e51decb1a211df6", GitTreeState:"clean", BuildDate:"2017-05-10T15:38:08Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Operating System and version:
CentOS Linux release 7.3.1611 (Core)

@willise I think you're getting that BadRequest error because you haven't specified the container in the pod. you should add the flag -c  kube-flannel to specify the container in the pod (since there are two containers in the pod)
Alternatively, you can also do a kubectl describe pod <pod-name> -n kube-system to see what's going on in the pod

@gunjan5 But where to add the flag -c kube-flannel? command like kubectl apply -f kube-flannel.yml -c kube-flannel makes errors.

@willise the error is telling you to provide an argument like kube-flannel to your kubectl log command. That error isn't from flannel.
Error from server (BadRequest): a container name must be specified for pod kube-flannel-ds-hdqb4, choose one of: [kube-flannel install-cni]

How to deal with this problem?

Starting kubernetes and having flannel working is really a master move. I have everything done by a book for CentOS 7 but flannel gets "CrashLoopBackOff". Can you make this working? Is it possible?

authors: AlawnWong ericchiang gunjan5 vglisin willise

repo: coreos/flannel


text:
README: Clean up idiosyncratic indents, other fmt and typos.

On heels of @colhom 's coreos/khealth#12

thanks @joshix !

authors: colhom joshix

repo: coreos/khealth


text:
deleting kube-prometheus yields errors (v0.22.0)

(This is kind of related to previous issue #1571 - for which the resolution was to run kubectl create -f manifests/ twice.)
To summarize the commands below, I found that when I delete kube-prometheus then errors are printed - are the errors benign? If so, then perhaps I should just simply change the command to kubectl delete -f manifests/ | true (to ignore/suppress the errors - i.e. for the command to have a non-error return code)?
~/v0.22.0_prometheus-operator/prometheus-operator/contrib/kube-prometheus
$ kubectl get pods -n monitoring
NAME                                  READY     STATUS              RESTARTS   AGE
alertmanager-main-0                     2/2       Running             0          3h
grafana-67b7f55895-f7qth                1/1       Running             0          3h
kube-state-metrics-69df7cf6bc-z55b6     4/4       Running             0          3h
node-exporter-lwb42                     2/2       Running             0          3h
prometheus-k8s-0                        3/3       Running             1          3h
prometheus-k8s-1                        3/3       Running             1          3h
prometheus-operator-8d78694b-bd2wn      1/1       Running             0          3h
$ kubectl delete -f manifests/
namespace "monitoring" deleted
customresourcedefinition "alertmanagers.monitoring.coreos.com" deleted
customresourcedefinition "prometheuses.monitoring.coreos.com" deleted
customresourcedefinition "prometheusrules.monitoring.coreos.com" deleted
customresourcedefinition "servicemonitors.monitoring.coreos.com" deleted
clusterrole "prometheus-operator" deleted
clusterrolebinding "prometheus-operator" deleted
deployment "prometheus-operator" deleted
service "prometheus-operator" deleted
serviceaccount "prometheus-operator" deleted
secret "alertmanager-main" deleted
service "alertmanager-main" deleted
serviceaccount "alertmanager-main" deleted
secret "grafana-datasources" deleted
configmap "grafana-dashboard-k8s-cluster-rsrc-use" deleted
configmap "grafana-dashboard-k8s-node-rsrc-use" deleted
configmap "grafana-dashboard-k8s-resources-cluster" deleted
configmap "grafana-dashboard-k8s-resources-namespace" deleted
configmap "grafana-dashboard-k8s-resources-pod" deleted
configmap "grafana-dashboard-nodes" deleted
configmap "grafana-dashboard-pods" deleted
configmap "grafana-dashboard-statefulset" deleted
configmap "grafana-dashboards" deleted
clusterrole "kube-state-metrics" deleted
clusterrolebinding "kube-state-metrics" deleted
clusterrole "node-exporter" deleted
clusterrolebinding "node-exporter" deleted
clusterrole "prometheus-k8s" deleted
clusterrolebinding "prometheus-k8s" deleted
rolebinding "prometheus-k8s" deleted
rolebinding "prometheus-k8s" deleted
role "prometheus-k8s" deleted
role "prometheus-k8s" deleted
Error from server (NotFound): error when deleting "manifests/0prometheus-operator-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com prometheus-operator)
Error from server (NotFound): error when deleting "manifests/alertmanager-alertmanager.yaml": the server could not find the requested resource (delete alertmanagers.monitoring.coreos.com main)
Error from server (NotFound): error when deleting "manifests/alertmanager-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com alertmanager)
Error from server (NotFound): error when stopping "manifests/grafana-deployment.yaml": deployments.extensions "grafana" not found
Error from server (NotFound): error when deleting "manifests/grafana-service.yaml": services "grafana" not found
Error from server (NotFound): error when deleting "manifests/grafana-serviceAccount.yaml": serviceaccounts "grafana" not found
Error from server (NotFound): error when stopping "manifests/kube-state-metrics-deployment.yaml": deployments.extensions "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-role.yaml": roles.rbac.authorization.k8s.io "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-roleBinding.yaml": rolebindings.rbac.authorization.k8s.io "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-service.yaml": services "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-serviceAccount.yaml": serviceaccounts "kube-state-metrics" not found
Error from server (NotFound): error when deleting "manifests/kube-state-metrics-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-state-metrics)
Error from server (NotFound): error when stopping "manifests/node-exporter-daemonset.yaml": daemonsets.extensions "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-service.yaml": services "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-serviceAccount.yaml": serviceaccounts "node-exporter" not found
Error from server (NotFound): error when deleting "manifests/node-exporter-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com node-exporter)
Error from server (NotFound): error when deleting "manifests/prometheus-prometheus.yaml": the server could not find the requested resource (delete prometheuses.monitoring.coreos.com k8s)
Error from server (NotFound): error when deleting "manifests/prometheus-roleBindingConfig.yaml": rolebindings.rbac.authorization.k8s.io "prometheus-k8s-config" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleBindingNamespace.yaml": rolebindings.rbac.authorization.k8s.io "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleConfig.yaml": roles.rbac.authorization.k8s.io "prometheus-k8s-config" not found
Error from server (NotFound): error when deleting "manifests/prometheus-roleNamespace.yaml": roles.rbac.authorization.k8s.io "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-rules.yaml": the server could not find the requested resource (delete prometheusrules.monitoring.coreos.com prometheus-k8s-rules)
Error from server (NotFound): error when deleting "manifests/prometheus-service.yaml": services "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-serviceAccount.yaml": serviceaccounts "prometheus-k8s" not found
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitor.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com prometheus)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorApiserver.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-apiserver)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorCoreDNS.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com coredns)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubeControllerManager.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-controller-manager)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubeScheduler.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kube-scheduler)
Error from server (NotFound): error when deleting "manifests/prometheus-serviceMonitorKubelet.yaml": the server could not find the requested resource (delete servicemonitors.monitoring.coreos.com kubelet)

Do the objects actually still exist? The custom resources are cleaned up just by deleting the CRDs, still curious why things like the the ServiceAccounts got those errors.

I verified (for a subset of the objects) that after running the delete that they no longer exist (more details below).
So maybe the only thing here is to do | true? In which case this issue could be closed (if there's nothing in kube-prometheus that needs to be fixed).

After the create ...:
$ kubectl get pods -n monitoring
NAME                                  READY     STATUS    RESTARTS   AGE
alertmanager-main-0                   2/2       Running   0          5m
alertmanager-main-1                   2/2       Running   0          4m
alertmanager-main-2                   2/2       Running   0          4m
grafana-67dbf88558-pk2l7              1/1       Running   0          6m
kube-state-metrics-69df7cf6bc-6hb82   4/4       Running   0          6m
node-exporter-7ckls                   2/2       Running   0          6m
prometheus-k8s-0                      3/3       Running   1          5m
prometheus-k8s-1                      3/3       Running   1          4m
prometheus-operator-8d78694b-f22bv    1/1       Running   0          6m
$ kubectl get services -n monitoring
NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
alertmanager-main       ClusterIP   10.111.8.142     <none>        9093/TCP            6m
alertmanager-operated   ClusterIP   None             <none>        9093/TCP,6783/TCP   5m
grafana                 ClusterIP   10.103.3.124     <none>        3000/TCP            6m
kube-state-metrics      ClusterIP   None             <none>        8443/TCP,9443/TCP   6m
node-exporter           ClusterIP   None             <none>        9100/TCP            6m
prometheus-k8s          ClusterIP   10.102.186.248   <none>        9090/TCP            6m
prometheus-operated     ClusterIP   None             <none>        9090/TCP            5m
prometheus-operator     ClusterIP   None             <none>        8080/TCP            6m
$ kubectl get serviceaccounts -n monitoring
NAME                  SECRETS   AGE
alertmanager-main     1         6m
default               1         6m
grafana               1         6m
kube-state-metrics    1         6m
node-exporter         1         6m
prometheus-k8s        1         6m
prometheus-operator   1         6m
$ kubectl get servicemonitors --all-namespaces
NAMESPACE    NAME                      AGE
monitoring   alertmanager              6m
monitoring   coredns                   6m
monitoring   kube-apiserver            6m
monitoring   kube-controller-manager   6m
monitoring   kube-scheduler            6m
monitoring   kube-state-metrics        6m
monitoring   kubelet                   6m
monitoring   node-exporter             6m
monitoring   prometheus                6m
monitoring   prometheus-operator       6m

and same commands after the delete :
$ kubectl get pods -n monitoring
No resources found.
$ kubectl get services -n monitoring
No resources found.
$ kubectl get serviceaccounts -n monitoring
No resources found.
$ kubectl get servicemonitors --all-namespaces
Error from server (NotFound): Unable to list "servicemonitors": the server could not find the requested resource (get servicemonitors.monitoring.coreos.com)

though I suppose a sentence could be added to the kube-prometheus/README.md to specify the kubectl command to run to teardown the stack

That sounds fantastic, would you like to create a PR and add what you would have expected :slightly_smiling_face: ?

If I were going to make such a change, then the snippet after the line below is what I'd change this part of the README.md to.
But I feel that would be a band-aid at best. Is anyone else at least occasionally encountering this #1609 issue and/or #1571 ? Instead of making the documentation update shown below, I'd of course prefer the steps be fixed so they always work (though I don't have any ideas off the top of my head how to do that).
With the change below, we'd be ignoring any legitimate errors encountered by those kubectl commands, which is obviously not ideal at best.

Simply create the stack by running the following command twice:
$ kubectl create -f manifests/ | true

And to teardown the stack:
$ kubectl delete -f manifests/ | true

I think we're expecting too much from kubectl here. It's not a configuration management tool, it is simply a tool to interact with the Kubernetes API on a simple basis. It doesn't solve all problem and it shouldn't, this is a more complex rollout problem, which kubectl is just not made for.

Totally agree, thanks Frederic. I imagine a solution would involve more than tweaking the two kubectl commands.
Unless I hear otherwise from you, I'll plan on submitting a PR to make the aforementioned README.md change when I get a chance. And maybe eventually some sort of code change can be made to kube-prometheus so it gets deployed & torn-down every time without a hitch (the issues I've encountered with the two commands only happen sometimes).

That sounds good to me, we drop in a note as well that says why that’s there.

repo: coreos/prometheus-operator


text:
pubkey: simplify the code

Just assume that DefaultTransport is an *http.Transport behind the
RoundTripper interface. If this is not true in future, we can adapt.
cc @jonboulle

:+1: thanks

LGTM if green.

authors: iaguis jonboulle krnowak

repo: coreos/rkt


text:
Date picker

Initialized a date picker component

First, pull,

repo: coreui/coreui-free-vue-admin-template


text:
The symlink create command didn't work

I install the nvm and it fails when i try to type 'node' in the command line with
'npm' is not recognized as an internal or external command
Then I check the source and found that the 'mklink' command didn't work, but I can create the same directory symlink in command line by manual, so what cause this problem?

My english is poor, hope you can understand！

try uninstalling nvm, removing all the folders(and installations) related to node(if you have any), install it again and it should work.
The issue that I was facing was due to have node installed already and then nvm failed in oprder to create the symlink.
Hope it helps

Did you run nvm use ____? You have to nvm install ____, then nvm use ___ before node will work.

I'm having trouble with the mklink apparently failing silently.  This has happened both on my local developer machine (where it then started working for no apparent reason) and on a TeamCity build machine.  Older versions worked fine for me.  I'm not sure what is happening.

I ran into this as well, what worked for me was to change the symlink location from C:\Program Files\nodejs to a directory that doesn't need admin rights like C:\Users\<user>\nodejs

I ran into this as well, what worked for me was to change the symlink location from C:\Program Files\nodejs to a directory that doesn't need admin rights like C:\Users\<user>\nodejs

@axelstudios while what You are saying is definitely needed, it doesn't solve the issue. I already have it mapped to a folder with enough privileges, but the symlink is still created at random (and use a command line with elevated privileges).

The original issue suggested npm was not found. The mklink command works, but if the username or path contained a space, the npm executable could not be found. The space issue has been resolved in https://github.com/coreybutler/nvm-windows/releases/tag/1.1.8.

I ran into this as well, what worked for me was to change the symlink location from C:\Program Files\nodejs to a directory that doesn't need admin rights like C:\Users\<user>\nodejs

It was an exactly issue in my case.
Thank you, @axelstudios

authors: KeisukeeLee StephenMcConnel VladimirRybalko axelstudios bitbay coreybutler demetrioalvesnl

repo: coreybutler/nvm-windows


text:
Can't use without admin account

When installing it I saw a UAC prompt to run as admin. So it installed into admin account. Afterwise I want to use it normally from my user account but neither "nvm" nor "bash" commands are not recognized there.

Also I can't run uninstaller from my normal user account

Manual installation didn't help:
C:\Users\Vlad>nvm
ERROR open C:\Users\Vlad\AppData\Local\nvm"\settings.txt: The filename, directory name, or volume label syntax is incorrect.

Windows itself, not NVM4W, requires administrative privileges to perform many features, such as symlinking or accessing files in C:\Program Files. The next version, v1.1.8, adds support for some newer versions of Windows with less restrictive permissions. That will be released sometime this week.
I'm closing this because the permissions requirements come from Windows, not this app.

authors: AqlaSolutions coreybutler


text:
3rd vax cert is hard to find

<!--

* [x] Bug is not mentioned in the [FAQ](https://www.coronawarn.app/en/faq/)
* [x] Bug is specific for iOS only
* [x] Bug is not already reported in another issue

## Technical details

- Device name: iPhone 13
- iOS version: iOS 15.2
- App version: 2.15

## Describe the bug
The location of the 3. booster vaccination certificate is very confusing.
While this is not a technical bug, I do think this is an interface design bug :-)

## Steps to reproduce the issue
After scanning the certificate for the third vaccination,
the certificates list still only shows 2 certificates:
The top certificate is the 2.  vaccination,
the lower certificate looks like the 1. vaccination.
the third vaccination only becomes visible after you select
and double click the bottom certificate

## Expected behaviour
IMHO, the clearest design for the vax certificates is:
- all vax certificates in the certificates list show their date already
 (i.e. no need to click on it to see from when it is)
- all vax certificates are shown on the same level (no nesting)
- vax certificates are sorted by date, newest certificate is always on top of the list

## Additional context
After scanning my 3rd vax certificate, I could not find it in the app;
trying to re-scan it gave me a "VC_ALREADY_REGISTERED" error;
then I scanned the FAQ to figure out how to delete a registered-but-invisible vax cert;
eventually following the few github issues that mention VC_ALREADY_REGISTERED,
I found out that you need to look in the _older_ vax cert to see the newest one - ???

So, it cost me more than an hour of time to figure out where the app put my booster vax cert...
and to show it, e.g. when going in to work IRL, I need to remember how to access it.
- I think this could and should be be much more intuitive.

hope this is helpful?
best adc

Hi @adcxyz
Could you provide some details, please?

Ah sorry, I had written it all up, and apparently did not save the issue properly!
I'll write it again now.

iphone 13, current iOS, cwa also current 2.15
I find the way the iOS app shows the 3rd vax cert quite confusing,
and believe this could be both simpler and clearer.
Background:
After scanning my 3rd vax cert, the certif. panel showed me 2 certif. entries,
just like it was before with two vax dates.
the two entries look exactly the same, just the QR code.
I expected to see 3 entries now, so it seemed the scan of the 3rd cert had failed.
On the upper entry of the two,
clicking on the details showed my second vax date (6/2021);
all the way at the bottom, it has entries for
vax cert 2 (6/2021) and
vax 1 (5/2 021) .
The lower certif. entry actually shows only the third vaccination;
because I expected this to be the older cert of my 1st vax, I did not
read this patiently enough, and spent some time trying to repeat the scanning,
which failed with "VC_ALREADY_REGISTERED" ...
Crosschechkin on the android caw app 2.15.1:
this shows only a single top vax certificate, also without date,
and clicking for details shows indiv. vax. dates with newest on top:
vax 3 11/2021,
vax 2 6/2021,
vax 1 5/2021
This is already clearer, and I think it could be even clearer:
The top level entries in the certificates panel should also show
the date of the newest vax (of the series captured) in that entry,
so users know immediately which QR code to show on entering offices etc.
Thanks!

iOS should actually behave the same way as Android does and I can confirm that this is the case on my iPhone XR:

(I have only stored 2/2 and 3/3 cert in the app).
A new tile on the certificates tab is only created if the names or date of births differ from the other certificate.

authors: Ein-Tim adcxyz

repo: corona-warn-app/cwa-app-ios


text:
Translation Delivery

Translation Delivery

This pull request is for translation delivery. Please review and approve them.


text:
Error result from Uni Wuppertal survey linked from blog

Where to find the issue

https://www.coronawarn.app/en/blog/2021-02-23-corona-warn-app-survey/ "Corona-Warn-App Survey"
https://www.coronawarn.app/de/blog/2021-02-23-corona-warn-app-survey/ "Umfrage zur Corona-Warn-App"

Describe the issue
The link https://umfrage.uni-wuppertal.de/index.php/765823?lang=de embedded in the blog leads to an error message:

Fehler
Es tut uns leid, aber diese Umfrage ist abgelaufen und nicht mehr verfügbar.
Bitte kontaktieren Sie Tim Katzwinkel für weitere Informationen.
katzwinkel@uni-wuppertal.de

Suggested change
There are several options:

Do nothing and assume that the web page will continue to stay online giving out the present information.
Remove the link to the survey https://umfrage.uni-wuppertal.de/index.php/765823?lang=de in the source files found in https://github.com/corona-warn-app/cwa-website/tree/master/blog/2021-02-23-umfrage-uni-wuppertal and state that the survey has been discontinued
Contact the survey author katzwinkel@uni-wuppertal.de from the Bergische Universität Wuppertal to find out if the survey produced results.
If there are useful results, then consider publishing them to the Science Blog

Hello,
I've written an E-mail to to survery author asking him wether there are any results to the survey that can be linked. Can I update the Blog post when I get an answer?

@LucaSchwan

Can I update the Blog post when I get an answer?

It would be great if you could first share an answer if you do get a reply. After that we might discuss exactly what to do after that and get agreement.

I have just gotten an answer. The Survey has been conducted for SAP and they should have all the results. So as far as I know there isn't any official pulication.

@LucaSchwan
The question now, for SAP (and RKI), is if they want to publish the results or at least make some statement, after having enlisted the cooperation of users. This is all quite old now though.

Thanks for your report @MikeMcC399. We have created an internal ticket for it and will raise this topic internally.
Internal Tracking ID: EXPOSUREAPP-11551

Corona-Warn-App Open Source Team

@larswmh Do you have any update on this, which you could share with us?

Option 2. from the suggestions was used to resolve this issue:

Remove the link to the survey https://umfrage.uni-wuppertal.de/index.php/765823?lang=de in the source files found in https://github.com/corona-warn-app/cwa-website/tree/master/blog/2021-02-23-umfrage-uni-wuppertal and state that the survey has been discontinued

authors: Ein-Tim LucaSchwan MikeMcC399 larswmh

repo: corona-warn-app/cwa-website


text:
Bump copyright year in README.md

Description
This PR bumps the copyright year in the README.md file.
Happy new year! 🎉
Note
This PR should only be merged once a change to any content of this repository was done.

Internal Tracking ID: EXPOSUREAPP-14521

@MikeMcC399 To me, it looks like the NOTICE file of this repository was never correctly established. When comparing the file from this repository to the file in the documentation repository , it looks like the contributors are missing. But also there, in the documentation repo, the copyright year has never been changed. I'm unsure if this file is really relevant.

Honestly, I'm not sure. I will forward it and let you know.
I'd suggest we merge this and make a separate or for the notice.
Also Happy New Year to both of you. I will be on vacation for around two weeks and only check in here irregularly, but @dsarkar is back in action.  🎉

@Ein-Tim / @brianebeling
https://www.apache.org/licenses/LICENSE-2.0 in the section "HOW TO APPLY THE APACHE LICENSE TO YOUR WORK" says:
"Include a copy of the Apache License, typically in a file called LICENSE, in your work, and consider also including a NOTICE file that references the License."
however since the suggested text is already in the README, Licensing section and NOTICE is incorrectly completed, then I suggest that the NOTICE file is deleted as part of any Copyright update review.

@larswmh
If the README only refers to itself:
"Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License."
and the NOTICE file refers to "them" without specifying what "them" means as in:
"you may not use them except in compliance with the License."
then this should be cleaned up.
My reading of opinions about Copyright notices says that they are not really necessary, so if they are not necessary, then it doesn't matter if they are clean or not, however this should be sorted out by legal experts.
Thank for passing on the concerns in any case.

authors: Ein-Tim MikeMcC399 brianebeling


text:
Unhandled 'error' event #167

events.js:167
throw er; // Unhandled 'error' event
^
Error: EPERM: operation not permitted, lstat 'F:\sasa\android\app\build\generated\source\r\debug\android\arch\core\R.java'
Emitted 'error' event at:
at NodeWatcher. (F:\sasa\node_modules\sane\src\node_watcher.js:306:14)
at F:\sasa\node_modules\graceful-fs\polyfills.js:282:31
at FSReqWrap.oncomplete (fs.js:154:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sasa@0.0.1 start: node node_modules/react-native/local-cli/cli.js start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sasa@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\tf\AppData\Roaming\npm-cache_logs\2019-01-04T07_43_17_428Z-debug.log
F:\sasa>npm -v
6.5.0

Slingshot only supports Node 8+.

authors: coryhouse tfak

repo: coryhouse/react-slingshot


text:
Fix react-native 0.40 imports

https://github.com/facebook/react-native/releases/tag/v0.40.0

FYI, I just merged #83 which includes updates to the imports and released v0.4.0 to NPM.

Oh, sorry missed this PR

No worries, I took a while to merge it in

authors: corymsmith farwayer

repo: corymsmith/react-native-fabric


text:
Logo

I'm made a V2 logo for the RTD, gathering thoughts. Color scheme is that of EPFL and STI right now

Currently this PR changes the logo files and the documentation conf.py/

One small comment: the perspective on the box feels weird, I'm not sure why.
One larger comment: I find this logo a bit crowded, with a lot going on. I would maybe simplify the shape behind COSMO, and make it a flat color instead of shades of purples in small circles. I like it when we can use logos as favicon in the website, and that means they need to look nice as 64x64 pixels images, leaving very little room for fine details.

One small comment: the perspective on the box feels weird, I'm not sure why.
One larger comment: I find this logo a bit crowded, with a lot going on. I would maybe simplify the shape behind COSMO, and make it a flat color instead of shades of purples in small circles. I like it when we can use logos as favicon in the website, and that means they need to look nice as 64x64 pixels images, leaving very little room for fine details.

One small comment: the perspective on the box feels weird, I'm not sure why.
One larger comment: I find this logo a bit crowded, with a lot going on. I would maybe simplify the shape behind COSMO, and make it a flat color instead of shades of purples in small circles. I like it when we can use logos as favicon in the website, and that means they need to look nice as 64x64 pixels images, leaving very little room for fine details.

Here's a solid background option with the EPFL/STI color scheme.

One small comment: the perspective on the box feels weird, I'm not sure why.
One larger comment: I find this logo a bit crowded, with a lot going on. I would maybe simplify the shape behind COSMO, and make it a flat color instead of shades of purples in small circles. I like it when we can use logos as favicon in the website, and that means they need to look nice as 64x64 pixels images, leaving very little room for fine details.

Here's a solid background option with the EPFL/STI color scheme.

That should work much better!

That should work much better!

Maybe I'm wrong, but do purple and red definitely go well together?

Maybe I'm wrong, but do purple and red definitely go well together?

Maybe I'm wrong, but do purple and red definitely go well together?

I quite literally chose the lazy option of putting EPFL (red) and STI (purple) 's colors together. We could choose to coordinate with i-pi or librascal's colors, but I haven't put much time into it.

Maybe I'm wrong, but do purple and red definitely go well together?

I quite literally chose the lazy option of putting EPFL (red) and STI (purple) 's colors together. We could choose to coordinate with i-pi or librascal's colors, but I haven't put much time into it.

authors: Luthaf hurricane642 rosecers

repo: cosmo-epfl/scikit-cosmo


text:
Add ValiDAO endpoints, seed node

Add ValiDAO seeds + rpcs

Please use an appropriate PR title

Apologies, fixed now!

authors: murakamikaze reversesigh

repo: cosmos/chain-registry


text:
Feat: option to add fee payer account

This PR involves allowing users to set an account as FeePayer, as it is needed for the transaction type /osmos.authz.v1beta1.MsgExec to execute.
Reference Issue: https://github.com/cosmos/cosmjs/issues/1155

payer and granter fields are added as part of StdFee interface.

The sequence of transactions for a complete authz+feegrant are as follows:

/cosmos.authz.v1beta1.MsgGrant
/cosmos.feegrant.v1beta1.MsgGrantAllowance
/cosmos.authz.v1beta1.MsgExec

The test should execute the above messages sequentially. We can consider packages/stargate/src/modules/authz/queries.spec.ts as a reference.
Before proceeding with writing this test, I have a query. As mentioned in HACKING.md, we need to run few scripts and set flags to perform complete test suite run. In the current version of HACKING.md present on main branch, there is mention of running launchpad blockchain, although its corresponding scripts aren't present in the main branch. So, I wanted to know about the scipts we need to run and the flags that needs to set instead of launchpad?

Anything I can do to help this along?

Anything I can do to help this along?

Thank you @dckc. I am hesitant to merge this without the feature being tested. I don't want this feature to fail in the user's environment. Also having a test case serves as an always up-to-date example how to use the feature. Writing tests may detect flaws in the API. If you could add tests on top of that PR, I think we can get this out.
Please note that on latest main we have Cosmos SDK 0.44 and 0.46 (simapp44/simapp46) test chains. simapp42 was removed. With those chains it should be possible to test the whole flow.

I'm finishing this work in #1262. The test is in https://github.com/cosmos/cosmjs/pull/1262/commits/c959343cacd868ed60891cbd7c92a1a2f24448ba. Turns out no /cosmos.authz.v1beta1.MsgGrant and /cosmos.authz.v1beta1.MsgExec is needed to test that as you can use feegrant for a simple bank send.

repo: cosmos/cosmjs


text:
Document capabilities in IBC core spec

Summary
Capabilities in the core spec for IBC needs to be finished

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

I will leave it in v10 milestone for now, but since with the port router refactor we will probably get rid of the capability module, then this wouldn't be needed anymore.

authors: colin-axner crodriguezvega

repo: cosmos/ibc-go


text:
add tx cmd to wasm client

Description

The 7.3 release didn't export the tx command. This PR adds that.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Note for myself: add changelog.

Ah, false alarm: we had already fixed this but hadn't released it yet. 😓 I will make the release this week.
Thank you anyways, @nicolaslara!

authors: crodriguezvega nicolaslara


text:
Fix Electron vulnarability

UI Version: 0.9.4
Description:
https://electronjs.org/blog/web-preferences-fix

We already upgraded to 2.0.8

repo: cosmos/voyager


text:
Update header parser in Secure Cell master key API

Passphrase API added in #577 has added quite a few new utilities and more robust and readable approach to parsing Secure Cell headers. Fuzzing with AFL in #579 and #583 has uncovered a bunch of sleeper issues in parsing code. This PR incorporates those improvements and updates master key API implementation to resolve all those issues.
First bunch of commits unifies master key implementation with passphrase one, now they are more or less similar, with differences only in KDF processing and header handling. Maybe later we will be able to reduce code duplication even further.
Some next commits resolve miscellaneous issues found in #583 for passphrase API which were also actual for master key API. This should unbreak fuzzing tests performed by #579.
And there are some minor commits with “collateral damage”: extracted common code from passphrase API implementation and some fixups in tests to expect different error codes.
Checklist

[X] Change is covered by automated tests
[ ] Benchmark results are attached (manually compare with master)
[X] The coding guidelines are followed
[X] Public API has proper documentation (no changes)
[X] Changelog is updated (will update in bulk before release)

Since I did not teach our CI to compare benchmark results yet, I'm filling it for this job.
Here are reports for master and this PR, they check only processing of 4 KB of data.

Encryption
Decryption

Before
4.38 µs ± 0.73 µs
3.10 µs ± 0.26 µs

After
4.20 µs ± 0.18 µs
3.01 µs ± 0.28 µs

So it’s even a slight improvement but within the variance so I doubt it is statistically significant.
Performance optimization is not a goal of this PR so I won‘t be doing measurements manually. I’m fine with not having any obvious degradation.

repo: cossacklabs/themis


text:
¿Is there a way to change the image shown when sharing a post?

Checklist

[x] I have read the tutorials and know the correct effect of the functional design.
[x] There are no similar question on existing issues (including closed ones).
[x] I searched the Internet for related problems, but still couldn't solve it.
[x] My question is based on the latest code of master branch.

Description

I would like to know if it is possible to change the image shown when sharing a link for a post in social media. Currently, every link shows the avatar that appears in the sidebar and I would like to set a specific image for each post.
Thank you in advance.

Yes, you can add a image to a post by:
---
image: /path/to/image
---

See the source code.

Thank you very much!

I'm using the stater version of the theme is there's no _layouts directory


text:
🛑 Mainnet [TezTools] (eu01-node.teztools.net) is down

In e3bb5f9, Mainnet [TezTools] (eu01-node.teztools.net) (https://eu01-node.teztools.net/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 381 ms

Resolved: Mainnet [TezTools] (eu01-node.teztools.net) is back up in 98ef666.

repo: cotezos/teznodes


text:
🛑 Mainnet [TezTools] (eu01-node.teztools.net) is down

In 0e888f1, Mainnet [TezTools] (eu01-node.teztools.net) (https://eu01-node.teztools.net/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 181 ms

Resolved: Mainnet [TezTools] (eu01-node.teztools.net) is back up in d2b88cf.


text:
🛑 Mainnet [Marigold] (mainnet.tezos.marigold.dev) is down

In fb9c936, Mainnet [Marigold] (mainnet.tezos.marigold.dev) (https://mainnet.tezos.marigold.dev/chains/main/blocks/head/header) was down:

HTTP code: 503
Response time: 584 ms

Resolved: Mainnet [Marigold] (mainnet.tezos.marigold.dev) is back up in 7932753 after 8 minutes.


text:
🛑 Testnet Giganode [tezos Ukraine] is down

In 18fa150, Testnet Giganode [tezos Ukraine] (https://testnet-tezos.giganode.io/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 457 ms

Resolved: Testnet Giganode [tezos Ukraine] is back up in b830ee0.


text:
--clusters regEx engine not working as expected

The --clusters flag can take a regex that will be matched to the names of the relevant clusters. However this is not behaving as expected. E.g when we have 2 clusters, called local and remote, the following should just return the nodes for the remote cluster, but it instead returns the nodes for both:
👤 Westwooo 🏠 remote in ☁ default._default._default
> nodes --clusters r*
╭─────┬───────────┬──────────────────────────────────────────────────────────────────────────────────────┬───────────┬────────────────────────────┬────────────────────────┬────────────────────────────┬───────────────┬──────────────┬──────────╮
│   # │  cluster  │                                       hostname                                       │  status   │          services          │        version         │             os             │ memory_total  │ memory_free  │ capella  │
├─────┼───────────┼──────────────────────────────────────────────────────────────────────────────────────┼───────────┼────────────────────────────┼────────────────────────┼────────────────────────────┼───────────────┼──────────────┼──────────┤
│   0 │ local     │ 192.168.107.128:8091                                                                 │ healthy   │ search,indexing,kv,query   │ 7.6.2-3505-enterprise  │ aarch64-unknown-linux-gnu  │    6201221120 │   3719835648 │ false    │
│   1 │ local     │ 192.168.107.129:8091                                                                 │ healthy   │ search,indexing,kv,query   │ 7.6.2-3505-enterprise  │ aarch64-unknown-linux-gnu  │    6201221120 │   3718000640 │ false    │
│   2 │ local     │ 192.168.107.130:8091                                                                 │ healthy   │ search,indexing,kv,query   │ 7.6.2-3505-enterprise  │ aarch64-unknown-linux-gnu  │    6201221120 │   3719835648 │ false    │
│   3 │ remote    │ svc-dqi-node-001.mxqbkexvumvjcve.customsubdomain.nonprod-project-avengers.com:8091   │ healthy   │ indexing,kv,query          │ 7.6.2-3721-enterprise  │ aarch64-unknown-linux-gnu  │   16373264384 │  15498129408 │ true     │
╰─────┴───────────┴──────────────────────────────────────────────────────────────────────────────────────┴───────────┴────────────────────────────┴────────────────────────┴────────────────────────────┴───────────────┴──────────────┴──────────╯

Also I'd expect to be able to pass in "*" to match against all clusters, however this results in an error:
👤 Westwooo 🏠 remote in ☁ default._default._default
> nodes --clusters *
Error:   × regex parse error:
  │     *
  │     ^
  │ error: repetition operator missing expression
   ╭─[entry #4:1:1]
 1 │ nodes --clusters *
   · ──┬──
   ·   ╰──
   ╰────
  help: Failed to parse identifier used for specifying clusters

My expectations were incorrect, this is working fine

repo: couchbaselabs/couchbase-shell


text:
chore(snyk): check if snyk can digest our package-locks

https://coveord.atlassian.net/browse/CDX-722
Proposed changes
Simulate what would happen on release to ensure Snyk will not fail at the last minute.
Testing
CI

CDX-722

Irrelevant, now that we run Snyk on master and PRs.

repo: coveo/cli