Crashing after a large number of refreshes

I don't know the specific number, but I've noticed that xbar is often crashing after a large number of refreshes.
I use a single script ran every second to report system vitals, including a request to an IP service I run, and a ping. At some point every few days, I notice the IP has changed as I'm changing networks, and that the other figures are also frozen.
Has anyone else experienced this? To fix it, I quit xbar and restart it.

@adamkdean hmm, sounds like something's wrong. Can you share the plugin that's causing this?

I've been noticing this too. All my info in the menubar and menus stops updating. After it happens, clicking menu items under any plugins stops doing anything, refresh and refresh all stop doing anything, and I have to quit/restart. I have a bunch of plugins so I'm not sure which could be causing it. @matryer any tips to try to narrow it down? Maybe I could run a debug build or something if it would help and dump state when the problem occurs.

@matryer sorry for the delay, here's the script that I use, stats.1s.sh. I cobbled it together back when BitBar came out, and it worked fine for years until I upgraded. If you need anything else, let me know. Thanks.
#!/usr/bin/env bash

#
# Functions
#
function get_ifstat {
  interface=$1
  # 1 sample for 0.5 second interval
  # outputs two values (in/out) in kilobits per second
  /usr/local/bin/ifstat -n -w -i "${interface}" -b 0.5 1 | tail -n 1
}

function kilo_to_mega {
  printf "%0.2f\n" "$(bc -q <<< scale=2\;"${1}"/1000)"
}

function bits_to_bytes {
  printf "%0.2f\n" "$(bc -q <<< scale=2\;"${1}"/8)"
}

function print_ifstat {
  kbits_in=$(echo "$1" | awk '{ print $1 }')
  kbits_out=$(echo "$1" | awk '{ print $2 }')
  rxv=$kbits_in
  rxs="KB/s"
  txv=$kbits_out
  txs="KB/s"

  if [[ $(echo "$kbits_in > 1000" | bc -l) -eq 0 ]]; then
    kbs_in=$(bits_to_bytes "$kbits_in")
    rxv=$kbs_in
    rxs="KB/s"
  else
    mbits_in=$(kilo_to_mega "$kbits_in")
    mbs_in=$(bits_to_bytes "$mbits_in")
    rxv=$mbs_in
    rxs="MB/s"
  fi

  if [[ $(echo "$kbits_out > 1000" | bc -l) -eq 0 ]]; then
    kbs_out=$(bits_to_bytes "$kbits_out")
    txv=$kbs_out
    txs="KB/s"
  else
    mbits_out=$(kilo_to_mega "$kbits_out")
    mbs_out=$(bits_to_bytes "$mbits_out")
    txv=$mbs_out
    txs="MB/s"
  fi

  echo "RX: $rxv $rxs TX: $txv $txs"
}

function TWODP {
  printf "%0.2f\n" "$(bc -q <<< scale=2\;"${1}")"
}

#
# Get stats
#
INTERFACE="en1"
HOST="<IP_ADDRESS>"
LATENCY="? MS"
LATENCY=$(ping -c 1 $HOST | awk '/64 bytes from/ { print $7 }' | cut -d "=" -f2)
LATENCY=$(TWODP $LATENCY)
TRAFFIC=$(print_ifstat "$(get_ifstat ${INTERFACE})")
IP=$(curl -s -4 https://ip.adamkdean.co.uk)

CPU_NCPU=$(sysctl -n hw.logicalcpu)
CPU_TOTAL=$(ps -Ao %cpu= | paste -sd+ - | bc)
CPU_USAGE=$(echo "scale = 2; $CPU_TOTAL / $CPU_NCPU" | bc)
CPU_LOADAVG=$(sysctl -n vm.loadavg | cut -d " " -f2-4)

MEM_PAGES_WIRED=$(vm_stat | grep "Pages wired down:" | awk '{print $4}')
MEM_WIRED=$(echo "($MEM_PAGES_WIRED*4096)/1024/1024" | bc)
MEM_PAGES_ACTIVE=$(vm_stat | grep "Pages active:" | awk '{print $3}')
MEM_ACTIVE=$(echo "($MEM_PAGES_ACTIVE*4096)/1024/1024" | bc)
MEM_USED=$(echo "$MEM_WIRED+$MEM_ACTIVE" | bc)

#
# Output
#
# printf "CPU: %0.1f%% (%s)    MEM: %s MB    %s    LATENCY: %s MS    QUOTA: %s    IPV4: %s" \
#   "$CPU_USAGE" "$CPU_LOADAVG" "$MEM_USED" "$TRAFFIC" "$LATENCY" "$QUOTA" "$IP"
printf "CPU: %0.1f%% (%s)    MEM: %s MB    %s    LATENCY: %s MS    IPV4: %s" \
  "$CPU_USAGE" "$CPU_LOADAVG" "$MEM_USED" "$TRAFFIC" "$LATENCY" "$IP"

I, too, have begun to see this issue. I have three home grown scripts I run with bar. one weather script refreshes every 3 minutes and locks up after a few days. It is the most noticeable one to fail as the others refresh more infrequently or don't obviously show that they have failed.
to fix it requires stopping and restarting xbar.
 ;;
    esac
}

print_temperature() {
    temperature=$1
    echo -n "$temperature°F"
}

WEATHER_DATA=$(curl -s https://api.openweathermap.org/data/2.5/onecall?lat\=45.55\&lon\=\-122.83\&exclude\=minutely,hourly\&units\=imperial\&appid=46dbf339ebad14ae0cba898ff2ce1fcc)

# echo $WEATHER_DATA

NOW_TEMP=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r '.current.temp')
declare -i icon
icon=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r '.current.weather[0].id')
echo "$(print_weather_icon $icon) $NOW_TEMP"

echo "---"
DAY1=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[1].sunrise')
DAY1DATEXX="$(date -r $DAY1 '+%a, %b %d')"
DAY2=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[2].sunrise')
DAY2DATEXX="$(date -r $DAY2 '+%a, %b %d')"
DAY3=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[3].sunrise')
DAY3DATEXX="$(date -r $DAY3 '+%a, %b %d')"
DAY4=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[4].sunrise')
DAY4DATEXX="$(date -r $DAY4 '+%a, %b %d')"
DAY5=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[5].sunrise')
DAY5DATEXX="$(date -r $DAY5 '+%a, %b %d')"
DAY6=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[6].sunrise')
DAY6DATEXX="$(date -r $DAY6 '+%a, %b %d')"
DAY7=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[7].sunrise')
DAY7DATEXX="$(date -r $DAY7 '+%a, %b %d')"

DAY0MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[0].temp.max' | sed '{s/[.].*$//;}')
DAY1MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[1].temp.max' | sed '{s/[.].*$//;}')
DAY2MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[2].temp.max' | sed '{s/[.].*$//;}')
DAY3MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[3].temp.max' | sed '{s/[.].*$//;}')
DAY4MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[4].temp.max' | sed '{s/[.].*$//;}')
DAY5MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[5].temp.max' | sed '{s/[.].*$//;}')
DAY6MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[6].temp.max' | sed '{s/[.].*$//;}')
DAY7MAX=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[7].temp.max' | sed '{s/[.].*$//;}')
DAY0MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[0].temp.min' | sed '{s/[.].*$//;}')
DAY1MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[1].temp.min' | sed '{s/[.].*$//;}')
DAY2MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[2].temp.min' | sed '{s/[.].*$//;}')
DAY3MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[3].temp.min' | sed '{s/[.].*$//;}')
DAY4MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[4].temp.min' | sed '{s/[.].*$//;}')
DAY5MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[5].temp.min' | sed '{s/[.].*$//;}')
DAY6MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[6].temp.min' | sed '{s/[.].*$//;}')
DAY7MIN=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[7].temp.min' | sed '{s/[.].*$//;}')
DAY0ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[0].weather[0].id' | sed '{s/-day//;}')
DAY1ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[1].weather[0].id' | sed '{s/-day//;}')
DAY2ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[2].weather[0].id' | sed '{s/-day//;}')
DAY3ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[3].weather[0].id' | sed '{s/-day//;}')
DAY4ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[4].weather[0].id' | sed '{s/-day//;}')
DAY5ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[5].weather[0].id' | sed '{s/-day//;}')
DAY6ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[6].weather[0].id' | sed '{s/-day//;}')
DAY7ICON=$(echo "$WEATHER_DATA" | /usr/local/bin/jq -r .'daily[7].weather[0].id' | sed '{s/-day//;}')

echo "      Today:  $DAY0MAX/$DAY0MIN  - $(print_weather_icon $DAY0ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY1DATEXX:  $DAY1MAX/$DAY1MIN  - $(print_weather_icon $DAY1ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY2DATEXX:  $DAY2MAX/$DAY2MIN  - $(print_weather_icon $DAY2ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY3DATEXX:  $DAY3MAX/$DAY3MIN  - $(print_weather_icon $DAY3ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY4DATEXX:  $DAY4MAX/$DAY4MIN  - $(print_weather_icon $DAY4ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY5DATEXX:  $DAY5MAX/$DAY5MIN  - $(print_weather_icon $DAY5ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY6DATEXX:  $DAY6MAX/$DAY6MIN  - $(print_weather_icon $DAY6ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'
echo "$DAY7DATEXX:  $DAY7MAX/$DAY7MIN  - $(print_weather_icon $DAY7ICON) | color=#000000" | sed '{s/$/ font=Courier/;}'

If you run xbar in terminal, you should see any output in the event of a crash.
~/Applications/xbar.app/Contents/MacOS/xbar

@leaanthony Perhaps you and I can pair on this at some point and see if we can recreate it?

Yeah cool. Let me know when you're free

I have been running xbar from the command line and have seen multiple failures where it hangs. These failures appear to be caused by local network failures in which local hosts that my xbar scripts access are not available. Still, perhaps these log messages would be useful to those who understand xbar.
The first failure shows an interesting 'feature' in the logging. For some reason, when a single script (of three active scripts) fails, the other two scripts show 'finished' instead of 'cycling' or 'refresh' at the time of failure. I'm not sure why this run failed, but I suspect it was because the pihole host was not accessible.

2021/05/15 20:08:58 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:08:58 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:08:59 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:03 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:09:03 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:09:04 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:08 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:09:08 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:09:09 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:13 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:09:13 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:09:14 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:18 pihole.30s.sh: refreshing: pihole.30s.sh
2021/05/15 20:09:18 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:09:18 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:09:19 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:23 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/15 20:09:23 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 20:09:24 battery.1h.py: cycling: battery.1h.py
2021/05/15 20:09:27 openweather.3m.sh: finished
2021/05/15 20:09:27 battery.1h.py: finished
2021/05/15 20:09:43 pihole.30s.sh: ERR: signal: killed

The next run I captured the startup:

m1mini--/Users/tbrown➜ /Applications/xbar.app/Contents/MacOS/xbar
xbar v2.0.42-beta
2021/05/15 21:40:53 battery.1h.py: cycling: battery.1h.py
2021/05/15 21:40:54 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 21:40:57 checking for updates... (current: v2.0.42-beta)
2021/05/15 21:40:57 updates: passive true
2021/05/15 21:40:57 updates: AutoUpdate true
2021/05/15 21:40:57 update: you have the latest version
2021/05/15 21:40:58 battery.1h.py: cycling: battery.1h.py
2021/05/15 21:40:59 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/15 21:41:03 battery.1h.py: cycling: battery.1h.py
2021/05/15 21:41:04 openweather.3m.sh: cycling: openweather.3m.sh

This run failed when the url access to the pihole failed:

2021/05/16 05:37:57 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/16 05:38:00 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/16 05:38:01 battery.1h.py: cycling: battery.1h.py
2021/05/16 05:38:02 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/16 05:38:03 battery.1h.py: finished
2021/05/16 05:38:03 openweather.3m.sh: finished
Traceback (most recent call last):
File "/Users/tbrown/bin/pistats.py", line 26, in
print(str(summary['ads_percentage_today']) + '% Blocked')
KeyError: 'ads_percentage_today'
2021/05/16 05:58:46 pihole.30s.sh: ERR: signal: killed: Traceback (most recent call last):
pihole.30s.sh:   File "/Users/tbrown/bin/pistats.py", line 26, in
pihole.30s.sh:     print(str(summary['ads_percentage_today']) + '% Blocked')
pihole.30s.sh: KeyError: 'ads_percentage_today'
pihole.30s.sh:

At this point, I think my failures are caused by my own internal network failures. There were name resolution issues which I fixed. Then a host failure caused the failure of pinhole.30s.sh.
However, for some reason, Xbar hangs as a result of the network failure in a script. Seems like Xbar shouldn't care about this and should keep attempting to run scripts even if they fail. It is probably important that Xbar reports 'finished' on the other two scripts run at the time the third script failed. What does this mean?

Thanks @tthkbw this is great.

For what it's worth, I am often changing networks, various VPNs. That's how I notice it hasn't updated, when the IP is wrong in xbar.

This is a good lead. We’ll see if network issues do in fact cause xbar to hang somewhere.

Here is a log from my latest failure. I'm not sure what happened here. As far as I can tell, the network did not fail. The message "(23) Failed writing body" is a new one:

2021/05/20 20:13:30 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:33 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:34 battery.1h.py: cycling: battery.1h.py
2021/05/20 20:13:35 pihole.30s.sh: refreshing: pihole.30s.sh
2021/05/20 20:13:35 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:38 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:40 battery.1h.py: cycling: battery.1h.py
2021/05/20 20:13:41 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:43 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:45 battery.1h.py: cycling: battery.1h.py
2021/05/20 20:13:46 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:48 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:50 battery.1h.py: cycling: battery.1h.py
2021/05/20 20:13:51 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:53 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:55 battery.1h.py: cycling: battery.1h.py
2021/05/20 20:13:56 pihole.30s.sh: cycling: pihole.30s.sh
2021/05/20 20:13:57 openweather.3m.sh: refreshing: openweather.3m.sh
2021/05/20 20:13:58 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/20 20:13:58 pihole.30s.sh: finished
2021/05/20 20:13:58 battery.1h.py: finished
(23) Failed writing body
2021/05/20 20:13:58 openweather.3m.sh: ERR: signal: killed: (23) Failed writing body
openweather.3m.sh:
2021/05/20 21:55:20 checking for updates... (current: v2.0.42-beta)
2021/05/20 21:55:20 updates: passive true
2021/05/20 21:55:20 updates: AutoUpdate true
2021/05/20 21:55:20 update: you have the latest version

This ran for a couple of days, although I was playing with the pihole.30.sh script during that time. Interesting that it looks like xbar restarted more that an hour and a half after the failure, but it was not updating any scripts after that.
I have lots of time to play around with this, so if folks have suggestions for me to try to assist in debug, let me know. For now, I am going to test with a script that updates rapidly (like every second), prints the time in the menubar (so I can easily tell if it fails), and pings local machines on my network.

Here is the latest failure:
2021/05/22 05:33:48 openweather.3m.sh: cycling: openweather.3m.sh
2021/05/22 05:33:50 battery.1h.py: cycling: battery.1h.py
2021/05/22 05:33:50 pihole.10s.sh: refreshing: pihole.10s.sh
2021/05/22 05:33:50 pihole.10s.sh: cycling: pihole.10s.sh
2021/05/22 05:33:52 clock.5s.sh: finished
2021/05/22 05:33:52 openweather.3m.sh: finished
2021/05/22 05:33:52 battery.1h.py: finished
2021/05/22 05:33:52 pihole.10s.sh: ERR: signal: killed

clock.5s.sh ran the command 'date', then pinged three local machines.
pinhole.10s.sh used sshpass to grab statistics from my pinhole server (a raspberry pi adblocker) and display them.
This run lasted nearly 24 hours before failing.
Based on what I have seen so far, I am suspicious that xbar doesn't like it if processes it runs take to long? Maybe only network processes? I going to futz around with this some more and see if I can prove that.

@tthkbw wrote:

Based on what I have seen so far, I am suspicious that xbar doesn't like it if processes it runs take to long?

Looking at https://github.com/matryer/xbar/issues/704, it seems there's currently a hard-coded time limit of one minute; I'm not a Go person so I'm not the one to look at the code around that and see if it's implicated, but I wonder if this is somehow involved.
I'm experiencing this issue too, so I'm going to try to ensure all that of my plugins which perform potentially long operations (in particular network operations) have timeouts on those operations, and see if that helps. 🤷🏻♂ Might be a red herring, of course.

I haven't done that yet, but I did write a script that kills/relaunches xbar when I notice it's stuck — in case that's of use to anyone else.

I think I've disproven my timeout hypothesis...
Here's a plugin which just reads and displays three random hex digits from dev/random:
#!/bin/bash
# <xbar.title>Rando Calrissian</xbar.title>
# <xbar.version>v1.0</xbar.version>
# <xbar.author>Andy Gimblett</xbar.author>
# <xbar.author.github>gimbo</xbar.author.github>
# <xbar.desc>Just randomly show a 3 printable characters; for investigating issue #714</xbar.desc>

# Via https://gist.github.com/princebot/0c7ecb7410509744006bd94b3756edeb
LC_CTYPE=C tr -d -c '[:xdigit:]' </dev/urandom | head -c 3

echo "| color=gray | font='Fira Mono' | size=11"

I've had it running every 5 seconds since Friday (barring laptop downtime, and with a couple of reboots along the way), and I've just noticed that it stopped updating some time today. Refresh / Refresh All have no effect, but xbar's UI seems to be completely responsive otherwise.
AFAICS there's no way this plugin should ever crash or time out itself... Seems pretty safe?
So I think that whatever's crashing, it's independent of the specific plugins used/their timing issues, etc.
... and that's probably about the limit of my ability to debug this problem. Back to the experts!

I'm seeing this, too, with xbar v2.0.42-beta. It runs well for a while and then stops updating and doesn't respond to "Refresh," "Refresh All," or any of the menu actions. It runs for at least a day or so, but I haven't noted this duration carefully. I just found the debugging advice in this thread, and I'll log the next run. I have a 1s plugin and a 5s plugin, and a plugins/disabled folder with an old BitBar plugin.
Here are the contents of my plugins folder:
pomodoro.1s.sh
#!/bin/bash
#
# <bitbar.title>Pomodoro Timer</bitbar.title>
# <bitbar.version>v1.0</bitbar.version>
# <bitbar.author>Goran Gajic</bitbar.author>
# <bitbar.author.github>gorangajic</bitbar.author.github>
# <bitbar.desc>Pomodoro Timer that uses Pomodoro Technique™</bitbar.desc>
# <bitbar.image>http://i.imgur.com/T0zFY89.png</bitbar.image>

WORK_TIME=25
BREAK_TIME=3

SAVE_LOCATION=$TMPDIR/bitbar-promodo
TOMATO='🍅'

WORK_TIME_IN_SECONDS=$((WORK_TIME * 60))
BREAK_TIME_IN_SECONDS=$((BREAK_TIME * 60))

CURRENT_TIME=$(date +%s)

if [ -f "$SAVE_LOCATION" ];
then
    DATA=$(cat "$SAVE_LOCATION")

else
    DATA="$CURRENT_TIME|0"
fi

TIME=$(echo "$DATA" | cut -d "|" -f1)
STATUS=$(echo "$DATA" | cut -d "|" -f2)

function changeStatus {
    echo "$CURRENT_TIME|$1" > "$SAVE_LOCATION";
    osascript -e "display notification \"$2\" with title \"$TOMATO Pomodoro\" sound name \"$3\"" &> /dev/null
}

function breakMode {
    changeStatus "2" "Break Mode" "Glass"
}

function workMode {
    changeStatus "1" "Work Mode" "Blow"
}

case "$1" in
"work")
    workMode
    exit
  ;;
"break")
    breakMode
    exit
  ;;
"disable")
    changeStatus "0" "Disabled"
    exit
  ;;
esac

function timeLeft {
    local FROM=$1
    local TIME_DIFF=$((CURRENT_TIME - TIME))
    local TIME_LEFT=$((FROM - TIME_DIFF))
    echo "$TIME_LEFT";
}

function getSeconds {
    echo $(($1 % 60))
}

function getMinutes {
    echo $(($1 / 60))
}

function printTime {
    SECONDS=$(getSeconds "$1")
    MINUTES=$(getMinutes "$1")
    printf "%s %02d:%02d| color=%s\n" "$TOMATO" "$MINUTES" "$SECONDS"  "$2"
}

case "$STATUS" in
# STOP MODE
"0")
    echo "$TOMATO"
  ;;
"1")
    TIME_LEFT=$(timeLeft $WORK_TIME_IN_SECONDS)
    if (( "$TIME_LEFT" < 0 )); then
        breakMode
    fi
    printTime "$TIME_LEFT" "red"
  ;;
"2")
    TIME_LEFT=$(timeLeft $BREAK_TIME_IN_SECONDS)
    if (("$TIME_LEFT" < 0)); then
        workMode
    fi
    printTime "$TIME_LEFT" "green"
  ;;
esac

echo "---";
echo "👔 Work | bash=\"$0\" param1=work terminal=false"
echo "☕ Break | bash=\"$0\" param1=break terminal=false"
echo "🔌 Disable | bash=\"$0\" param1=disable terminal=false"

time.5s.sh
#!/bin/bash

# Utility: https://xbarapp.com/docs/plugins/Dev/totp.20s.sh.html
if [[ "$1" == "copy" ]]; then
  echo -n "$(echo -n "$2")" | pbcopy
  exit
fi

# setup
myUuid=$(uuidgen | tr '[:upper:]' '[:lower:]' | tr -d '\n')
zeroUuid='00000000-0000-0000-0000-000000000000'
shortDate=$(date -u +"%Y-%m-%dT%H:%MZ")
fullDate=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
migrationTemplate=$(date -u +"%Y%m%d%H%M%S-newmigration.js")

# output
echo "$shortDate"
echo '---'
echo $(date -u +"Sprint %Y-%U") "| href=https://app.asana.com/0/home/[redacted]"
echo "$myUuid | bash='$0' param1=copy param2='$myUuid' terminal=false"
echo "$zeroUuid | bash='$0' param1=copy param2='$zeroUuid' terminal=false | alternate=true"
echo "$fullDate | bash='$0' param1=copy param2='$fullDate' terminal=false"
echo "$migrationTemplate | bash='$0' param1=copy param2='$migrationTemplate' terminal=false | alternate=true"

Update: it crashed overnight. Here are the logs:
2021/06/30 05:30:47 time.5s.sh: refreshing: time.5s.sh
2021/06/30 05:30:47 time.5s.sh: cycling: time.5s.sh
2021/06/30 05:30:48 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:49 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:50 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:51 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:52 time.5s.sh: cycling: time.5s.sh
2021/06/30 05:30:52 time.5s.sh: refreshing: time.5s.sh
2021/06/30 05:30:53 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:54 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:55 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:56 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:57 time.5s.sh: cycling: time.5s.sh
2021/06/30 05:30:57 time.5s.sh: refreshing: time.5s.sh
2021/06/30 05:30:57 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/06/30 05:30:58 time.5s.sh: ERR: signal: killed
2021/06/30 09:55:58 checking for updates... (current: v2.0.42-beta)
2021/06/30 09:55:58 updates: passive true
2021/06/30 09:55:58 updates: AutoUpdate false
2021/06/30 09:55:58 update: you have the latest version

Here's how I invoked it: $ /Applications/xbar.app/Contents/MacOS/xbar | tee -a ~/xbar-$( date -u +"%Y-%m-%dT%H:%M:%SZ").log
I don't have the top of the log, just the recent scrollback, because it looks like the relaunch wiped the file (last modified 09:55 with no contents).
It looks like the update check at 09:55 PDT was almost exactly 24 hours after I launched it (2021-06-29T16:55:46Z), so some part of xbar was still running and doing scheduled update checks, it seems?
In case we're trying to count iterations: the crash was about 70512 seconds after the launch, so 70512 runs of pomodoro and 14102 runs of time.

Potentially fixed by #736

Was #736 included in v2.1.0-beta? If so, the issue persists I'm afraid.

It was only a potential as I didn't know if your issue was memory related or not.

@leaanthony no worries, just reporting my experience after updating a few days ago. 🙂

I'll try running your 2 plugins in debug mode and see where we get

I upgraded to 2.1.0-beta last night, and notice the same crash has happened again on the new version.

On Jul 5, 2021, at 6:05 AM, Lea Anthony @.***> wrote:
I'll try running your 2 plugins in debug mode and see where we get
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/matryer/xbar/issues/714#issuecomment-874097236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB22GZ5CCCKYH7SZ4PYGWFLTWGUY5ANCNFSM43ZVIQJA.

I, too, can verify that the 2.1.0 beta does not change this bug. I have built a monitoring system that verifies xbar is updating on a scheduled basis and restarts it if it hangs. With my xbar scripts, xbar works for about two days and then crashes and is restarted. I don't think this has changed at all with 2.1.0.
I don't have any insight as to what causes the crash. I have moved scripts that use the network and have a propensity for failure or taking a lot of time out of xbar (I have those scripts running from plist files and creating local text files that xbar scripts monitor), and have played with update frequencies without getting any useful information.

Still seeing this crash under v2.1.4-beta. Running with logging now with a single, very minimal plugin enabled. This reoccurs for me around once every day or two.

@alexthehurst thank you, let me know if you find any clues

@alexthehurst - Is what you are seeing most likely related to known issues with actually executing a script, eg network issues, laptop goes to sleep, etc, or does it feel more like a system error, eg memory runs out?

Hard to say. I've seen this happen while running a plug-in which doesn't do much (time.sh upthread), but I'm running a test now with a stripped down plug-in that does almost nothing at all and I'll update with the result. I can't rule out system issues, but I haven't made a connection with anything specific.

For what it’s worth: I ran a test with three scripts, one that does quite a
bit (shared above) and two that simply incremented a number in a file, one
every second and one every two seconds. All three scripts crashed at the
same time, once after 30,000 seconds, and the next about about 250,000
seconds.
I can’t say for sure whether the machine sleeping caused this though. It’s
a hard thing to notice.
On Tue, 10 Aug 2021 at 21:52, Alex Hurst @.***> wrote:

Hard to say. I've seen this happen while running a plug-in which doesn't
do much (time.sh upthread), but I'm running a test now with a stripped down
plug-in that does almost nothing at all and I'll update with the result. I
can't rule out system issues, but I haven't made a connection with anything
specific.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/matryer/xbar/issues/714#issuecomment-896308595, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMQIZZBTS23NQOQ4YUEN23T4GGQLANCNFSM43ZVIQJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@leaanthony:

Is what you are seeing most likely related to known issues with actually executing a script, eg network issues, laptop goes to sleep, etc, or does it feel more like a system error, eg memory runs out?

I know that question wasn't directed at me, but did you see this comment? Just generating random numbers is sufficient to trigger this behaviour.

@gimbo thanks

@gimbo I'm not entirely convinced the scripts are the issue. Even simple scripts incrementing a number in a file crash, and when they do, all xbar scripts crash. We've had a lot of reports of xbar crashing, but have there been any instances where it doesn't crash ever?

I'll carve out a couple of hours over the weekend for this. It would help if there was a way to quickly make it crash as the last time I looked at this I ran my "acid test" script for a whole weekend and it didn't fall over. Suggestions?

Nothing I've tried has made it crash more frequently, however, I wonder if you were to change the execution interval from 1s to say 10ms etc, if you could then drastically reduce the time to crash?

@alexthehurst thank you, let me know if you find any clues

I ran this test with a minimal script for 8 days straight and didn't encounter the crash. Starting another run with the full set of scripts to see what we see.

What would be really useful is to run it from the CLI via the .app package and capture the terminal output. I'm keen to get some visibility on the crash.

What would be really useful is to run it from the CLI via the .app package and capture the terminal output. I'm keen to get some visibility on the crash.

Yep! That's the approach I'm taking. On an earlier run, it got me the output that you've seen upthread:
2021/07/03 20:31:27 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/07/03 20:31:28 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/07/03 20:31:29 time.5s.sh: cycling: time.5s.sh
2021/07/03 20:31:29 time.5s.sh: refreshing: time.5s.sh
2021/07/03 20:31:30 pomodoro.1s.sh: refreshing: pomodoro.1s.sh
2021/07/03 20:31:30 time.5s.sh: finished
2021/07/03 20:31:30 pomodoro.1s.sh: ERR: signal: killed
2021/07/03 22:44:59 checking for updates... (current: v2.0.42-beta)
2021/07/03 22:44:59 updates: passive true
2021/07/03 22:44:59 updates: AutoUpdate false

Not sure what I'm seeking this time aside from reproducibility. What does scriptname: finished mean? It seems to happen every 12 hours, like so (this log from a test that did not crash):
2021/08/13 06:03:03 time.5s.sh: refreshing: time.5s.sh
2021/08/13 06:03:08 time.5s.sh: cycling: time.5s.sh
2021/08/13 06:03:08 time.5s.sh: refreshing: time.5s.sh
2021/08/13 06:03:11 time.5s.sh: finished
2021/08/13 06:03:16 time.5s.sh: cycling: time.5s.sh
2021/08/13 06:03:16 time.5s.sh: refreshing: time.5s.sh
2021/08/13 06:03:21 time.5s.sh: cycling: time.5s.sh

Something that may be a complete red herring: throughout the summer I've been regularly experiencing thermal CPU throttling on my Intel MacBook Pro because I'm in a hot room. A couple of weeks ago we got the AC fixed, and I haven't seen the overheating since, which roughly corresponds to the timespan of that last minimal test that didn't crash. I didn't notice one way or another whether the crashes actually coincided with the throttling, unfortunately.

Just on the overheating part, I've been running this on an iMac Pro with adequate cooling, often running quite under-utilised, and still getting crashes every day or two. I do put the machine to sleep a lot though.

New crash today. Log is attached. At the top of the log, I include the source of all the plugins which were enabled. One (time.sh) is custom, and the others are installed through the xbar plugin browser. Circumstance: after idling the computer overnight, I used it for about an hour, then got up for a coffee break and returned. The crash happened around the time I left the computer and came back to it (sorry I can't be more precise). Nothing of note in the system logs.
Most relevant part, like we've seen before: at some point everything says "finished" while one script says "killed", then there are no more script runs, but the autoupdater continues on schedule.
2021/08/20 06:08:45 mtop.5s.sh: cycling: 001-mtop.5s.sh
2021/08/20 06:08:45 cpu-thermal-throttle.30s.sh: refreshing: 001-cpu-thermal-throttle.30s.sh
2021/08/20 06:08:45 cpu-thermal-throttle.30s.sh: cycling: 001-cpu-thermal-throttle.30s.sh
2021/08/20 06:08:46 clipboard-history.3s.sh: refreshing: 001-clipboard-history.3s.sh
2021/08/20 06:08:48 time.5s.sh: cycling: time.5s.sh
2021/08/20 06:08:48 time.5s.sh: refreshing: time.5s.sh
2021/08/20 06:08:49 time.5s.sh: finished
2021/08/20 06:08:49 clipboard-history.3s.sh: finished
2021/08/20 06:08:49 cpu-thermal-throttle.30s.sh: finished
2021/08/20 06:08:49 mtop.5s.sh: ERR: signal: killed
2021/08/20 09:11:53 checking for updates... (current: v2.1.4-beta)
2021/08/20 09:11:53 updates: passive true
2021/08/20 09:11:53 updates: AutoUpdate false
2021/08/20 09:11:54 update: you have the latest version

2021-08-18-xbar-log.gz

Thanks for this. DID the computer go to sleep during that time?

I've been noticing this too. All my info in the menubar and menus stops updating. After it happens, clicking menu items under any plugins stops doing anything, refresh and refresh all stop doing anything, and I have to quit/restart. I have a bunch of plugins so I'm not sure which could be causing it. @matryer any tips to try to narrow it down? Maybe I could run a debug build or something if it would help and dump state when the problem occurs.

https://github.com/matryer/xbar/issues/714#issuecomment-831968574
@leaanthony I have this same issue, usually in the morning after the Mac has been sleeping through the night, I have a process sample taken with Activity Monitor while xbar was behaving in that way if it's of any use

Please upload 👍

@leaanthony there https://gist.github.com/elia/365e64e392b7d707424ba18400645906

Thanks. I suspect it's in relation to http timeouts and goroutines.  I suspect it's in relation to http timeouts and goroutines. Searching for anything around "laptop sleep goroutines" returns mainly false positives 😔

I'm not so sure that http requests factor into this, at least, in tests I've performed, there have been crashes with a simple bash script counter alone. At this point, I just know to quit and restart daily. I wish I could help more in debugging but not really sure where to start — MacOS isn't my area of expertise sadly!
Happy to run any tests that may help though.

@leaanthony said:

Thanks. I suspect it's in relation to http timeouts and goroutines.

@adamkdean replied:

I'm not so sure that http requests factor into this

I second that, at least as far as plugins are concerned; e.g. see this comment. Also, I'm now only running plugins which access local files (no http), and I'm still getting crashes.
The core of xbar probably does some http work, so timeouts+goroutines could factor in there though?
I haven't tried running xbar without any plugins at all, which I suppose (if the problem occurs) would prove the problem is in core. I'm going to try that now; if I get to the point where (to quote @elia) "clicking on Quit triggered the marble of death" then we can pretty be sure (I guess!) that it's got nothing to do with running plugins.

I haven't tried running xbar without any plugins at all, which I suppose (if the problem occurs) would prove the problem is in core. I'm going to try that now; if I get to the point where (to quote @elia) "clicking on Quit triggered the marble of death" then we can pretty be sure (I guess!) that it's got nothing to do with running plugins.

No crashes over the last week of doing this; AFAICS running xbar without plugins doesn't lead to these crashes. (But of course this is just indicative; I could be totally wrong about that.)

Is this still an ongoing issue? I've had to stop using this because of the crashes and honestly, my life is less without it :(

That's brilliant to hear. I'm sorry I can't help out more, this isn't my forte sadly, but I can't wait to become an active user again. Happy to run user testing though when it comes to that. Feel free @ me if you need anything. Thanks again for the hard work!

The one thing that would absolutely help is to nail down the smallest, minimal plugin that reproduces this

I had a simple script that caused this.
On Wed, 14 Sep 2022 at 13:59, Lea Anthony @.***> wrote:

The one thing that would absolutely help is to nail down the smallest,
minimal plugin that reproduces this
—
Reply to this email directly, view it on GitHub
https://github.com/matryer/xbar/issues/714#issuecomment-1246729797, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMQIZ5ERFOZGXCETBSYNCLV6HD4NANCNFSM43ZVIQJA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm running time.1s.sh and will let you know if I experience a crash:
#!/bin/bash

date

Memory corruption crashes every few days swiftbar/SwiftBar#319

Seems swift bar has fixed this issue in their issue tracker.

I never did manage to test SwiftBar, and haven't used xbar in a while now due to this issue. Is anyone/everyone else still seeing this?

Yes I'm seeing this still. Definitely related to sleep in my observation. Whenever my computer wakes from sleep xbar is killed and requires a restart:
2024/02/01 08:08:15 001-bandwidth_KBps_MBps.1s.sh: refreshing: 001-001-bandwidth_KBps_MBps.1s.sh
2024/02/01 08:08:22 001-bandwidth_KBps_MBps.1s.sh: refreshing: 001-001-bandwidth_KBps_MBps.1s.sh
2024/02/01 08:08:22 001-bandwidth_KBps_MBps.1s.sh: ERR: signal: killed

I never got to the bottom of this. It's such a hard problem to google as the keywords involved just give you results about putting your laptop to sleep. I'll see if chatGPT has any ideas


Push patches at a specific time?

Hi There!
Is there any plans to be able to schedule a time to push patches and to do an auto reboot?

This is being worked on in PR #65. Duplicate to #64.


Add nice table to web component

The web component should make sending a table to a node simple. So a nice (bootstrap?) table where you can add and remove rows and columns should be added. Additionally there needs to be a way to enter the peer id to send the table to.
The JS should create the correctly formatted string (send <node> <table>) and send it to the management component.

Implemented with 63130e9c99237d20a3a321aff4ca9aa016888aa4 and 36b09ad.


Prodlem with challenge

Challenge [Waypoint: Target the same element with multiple jQuery Selectors] has an issue. Can somebody help with this.

@efrGas thanks for posting this issue!
Please, provide your code, thanks!

Please review the Guidelines for Contributing, thank you!.

jQuery Playground

#left-well

#target1
#target2
#target3

#right-well

#target4
#target5
#target6

Here are my code
http://codepen.io/efrGas/pen/zvgNPW

You have spaces after your first two class names in your addClass calls. Once you've resolved that you'll find that you will get an error because you should only be adding one class with each of your addClass statements.
Thanks and happy coding!

It's woking!!!! thanks.


Failed to generate diagram - Error: Unable to calculate a unique id for an empty set of components

npx cdk-dia fails with the following error:
% npx cdk-dia
Failed to generate diagram - Error: Unable to calculate a unique id for an empty set of components
/usr/local/lib/node_modules/cdk-dia/node_modules/@aws-cdk/core/lib/private/uniqueid.js:33
        throw new Error('Unable to calculate a unique id for an empty set of components');
              ^

Error: Unable to calculate a unique id for an empty set of components
    at makeUniqueId (/usr/local/lib/node_modules/cdk-dia/node_modules/@aws-cdk/core/lib/private/uniqueid.js:33:15)
    at AwsEdgeResolver.findUniqueResourceId (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/aws/aws-edge-resolver.js:83:44)
    at /usr/local/lib/node_modules/cdk-dia/dist/src/diagram/aws/aws-edge-resolver.js:55:47
    at DiagramComponent.subTreeFindComponentRec (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/component/component.js:137:13)
    at DiagramComponent.subTreeFindComponent (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/component/component.js:134:21)
    at /usr/local/lib/node_modules/cdk-dia/dist/src/diagram/component/component.js:140:23
    at Array.map (<anonymous>)
    at DiagramComponent.subTreeFindComponentRec (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/component/component.js:139:40)
    at DiagramComponent.subTreeFindComponent (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/component/component.js:134:21)
    at AwsEdgeResolver.findTargetComponent (/usr/local/lib/node_modules/cdk-dia/dist/src/diagram/aws/aws-edge-resolver.js:54:47)

workaround for now: go to:
/usr/local/lib/node_modules/cdk-dia/node_modules/@aws-cdk/core/lib/private
change this:
function makeUniqueId(components) {
    components = components.filter(x => x !== HIDDEN_ID);
    if (components.length === 0) {
        throw new Error('Unable to calculate a unique id for an empty set of components');
    }

to this:
function makeUniqueId(components) {
    components = components.filter(x => x !== HIDDEN_ID);
    if (components.length < 0) {
        throw new Error('Unable to calculate a unique id for an empty set of components');
    }

Before cdk-dia calls makeUniqueId it checks, that the components array isn't empty (if (pathParts.length === 0) return false).
Therefore, I guess this line filters the component, creating an empty array.
Could you share some CDK code to help reproduce the issue?
I would prefer trying to solve the issue downstream, then copying the non-exported const HIDDEN_ID = 'Default'; variable to CDK-Dia.


doc: pin pygments,urllib3 to 2.7.4,1.26.3

Signed-off-by: Rodrigo Rojo<EMAIL_ADDRESS>

Coverage remained the same at 66.243% when pulling 9ca9bf5c657e09e5ce72f8b4deaa06e2f5f377cc on rrojo/pin-doc-requirements into e62360eb00f1006f1541f9d7d3e452ac490a69da on master.


Create a Promotion Model

As a marketing manager
I need a resource that is a representation of a special promotion or sale that is running against a product or perhaps the entire store
So that a promotion can be applied
Details and Assumptions

Will be updated off current model
Some examples are "buy 1 get 1 free", "20% off", etc. Discount promotions usually apply for a given duration (e.g., sale for 1 week only)."

Acceptance Criteria
Given the model
When I run the model
Then the model returns promotions

This was based on the feedback we received from John on the last hw


Citation Keys Issue

Hi BBT Team
I've been trying to change my citation key as per the picture below.

However, I'm still getting this(default) options instead. Can you help me? Thank you.

Debug Log ID : EBHICKI7-apse

You get this even if you select these items, right-click, and choose "BBT->Refresh"?

There's no team btw, there's just me.

Yup. Still getting the same error even after I've refreshh.

Can you reproduce that problem, then right-click a few of those items and send a debug log from that popup menu? The log ID will have -refs- in it.

Can't do anything without more info.

closing for inactivity


[otgrpc] add ctx in SpanDecorator option

This is a copy of the PR https://github.com/grpc-ecosystem/grpc-opentracing/pull/47 from @mmoustai for this repository.
It adds a context argument to the Spandecorator.
This fixes: https://github.com/opentracing-contrib/go-grpc/issues/6

thanks!


[Mgmt] Remove global configuration "multiapi"

https://github.com/Azure/azure-sdk-for-python/issues/24540

/azp run


Quick fix to allow CAdvisor and kubelet to work

for  #2098 and rancher/rancher#9848

backported to 1.0.5_ #2110


Enable rdsModel directive

Add unit tests to ensure parity on overlap with model directive Fixes some issues with orchestration

Description of changes
Puts in some tweaks to get the RDS model plugin working, a model orchestrator to keep type definitions from colliding, and test coverage

CDK / CloudFormation Parameters Changed

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Following a different strategy


Getting something went wrong page after deleting a user

Describe the issue:

Getting a something went wrong page after deleting a user in a organization. Following stacktrace can be seen in the browser console.

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at He (19026.aa890b44.chunk.js:1:26394)
    at 19026.aa890b44.chunk.js:1:23364
    at il (vendor.14e7fb03.js:102:1548714)
    at Sc (vendor.14e7fb03.js:102:1568844)
    at cc (vendor.14e7fb03.js:102:1561145)
    at ji (vendor.14e7fb03.js:102:1502107)
    at rc (vendor.14e7fb03.js:102:1558301)
    at ns (vendor.14e7fb03.js:102:1523593)
    at 19026.aa890b44.chunk.js:1:17859
    at <anonymous>

Reproducible with latest IS snapshot build (console v2.2.0).
How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This issue cannot be reproduced in the most recent build using Console version 2.3.0.

This issue can be reproduced within a sub-organization.


Group chat - No tooltip when hovering over group member avatar in details page

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

Version Number: 1.3.81-4
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go to any group chat
Click on the group chat header
Hover over the avatars in group details page

Expected Result:
Tooltip appears when hovering over group member avatar
Actual Result:
Tooltip does not appear when hovering over group member avatar
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/78819774/5571c049-1ed2-4d6d-9d77-454e86606d37

MacOS: Desktop

View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Tooltip is not working in group details page avatars
What is the root cause of that problem?
In RoomHeaderAvatar component, avatars are not wrapped in tooltip
https://github.com/Expensify/App/blob/907e65e074d1fec41b2038eacdd78455d2fdb161/src/components/RoomHeaderAvatars.js#L90-L98
What changes do you think we should make in order to solve the problem?
We should wrap avatar components in UserDetailsTooltip, like this:
 <UserDetailsTooltip
                                        key={`stackedAvatars-${index}`}
                                        accountID={icon.id}
                                        icon={icon}
                                        fallbackUserDetails={{
                                            displayName: icon.name,
                                            avatar: icon.avatar,
                                        }}
                                    >
                                        <View>
                                    <Avatar
                                        source={icon.source}
                                        fill={themeColors.iconSuccessFill}
                                        size={CONST.AVATAR_SIZE.LARGE}
                                        containerStyles={[...iconStyle, StyleUtils.getAvatarBorderRadius(CONST.AVATAR_SIZE.LARGE_BORDERED, icon.type)]}
                                        name={icon.name}
                                        type={icon.type}
                                        fallbackIcon={icon.fallbackIcon}
                                    /></View>
                                        </UserDetailsTooltip>

What alternative solutions did you explore? (Optional)

This is not a deploy blocker. On production, when clicking the header we get shown the following:

On staging, those details are now under the "Members" selection:

Under the "Members" selection everything works correctly with the tooltip:

This begs the question...do we want to show the tool tip on the "RoomHeaderAvatars" as per @alitoshmatov 's proposal?

We added this change as part of this wave 8 issue: https://github.com/Expensify/App/issues/27394 so I will tag @MitchExpensify @trjExpensify @shawnborton to confirm if we want to show the tooltip or not, but I agree that it shouldn't be a deploy blocker.

Cool cool. Given that it is also not a bug, I'm going to un-assign myself while that discussion happens.

I think we want to show the tooltip as we do everywhere for consistency but I agree this is not a blocker, we could export this for $250

I think we want to show the tooltip as we do everywhere for consistency but I agree this is not a blocker, we could export this for $250

Huh? What's the issue here? We don't show a tooltip when you hover over a user avatar in the profile page, why do we need to do it here in the group details page? A tooltip on hover over the name is enough IMO.

I am going to close this because this is expected behaviour. Please re-open the issue or bring a discussion in Slack if you disagree.

Alright, we used to show the tooltip almost everywhere so if these are the exception, thats fine


Focus the first field on the page when browsing /auth/login or /auth/resetpassword

Overview
On pages where the first user action is unambiguously filing in the first text field, autofocus that field.

Shares a point with #376


cp: There is a test that assumes it fails on android, but it does in fact not

should it be completely deleted then?

obsolete, handled in https://github.com/uutils/coreutils/pull/5894 as well


🚀 Feature Request: Log whether new versions are available as a part of wrangler --version

Describe the solution
If I'm checking my version, I'm probably also interested in seeing if there are new versions available. The only reason I can think to not do this is if we ever encourage something like node --version > .nvmrc or node --version > .node-version for other tools to pick it up or for us to read that in some CI environment or whatever.

SOunds good. Happy to output newer available versions when !isTTY

In fact, we should just use printWranglerBanner() when !isTTY, it includes this information and looks nice

Assigning to @cameron-robey


Create Google OAuth 2.0 application for ROCC

I've created Google OAuth 2.0 in the past for the SageBio Collaboration Portal.

Not needed now.


django-redis link

the GH account has been changed from https://github.com/niwinz/django-redis/ to https://github.com/jazzband/django-redis
the redirect works for the GH account but no redirect for http://niwinz.github.io/django-redis/latest/
This PR points to the GH account

back to green https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-docs/354/

Staged at https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-docs/lastSuccessfulBuild/artifact/omero/_build/html/sysadmins/unix/install-web.html#customizing-your-omero-web-installation.


:seedling: Uplift BMO to v0.6.3 and IPAM to v1.7.4

Bumping IPAM to v1.7.4 and BMO to v0.6.3

/test metal3-centos-e2e-integration-test-release-1-7

/cc @adilGhaffarDev

/lgtm

/retest


Resolving AL0468

Similar to #3498
We are getting this warning:

Length of the table field name must not exceed 30 characters. Longer field names are prone to cause SQL errors. This warning will become an error in a future release.

In trying to resolve it, we have made the field ObsoleteState = Pending;, added new field with shorter name, wrote upgrade CU to move the data.  But we are still getting this warning on the obsolete field.
Also we have fields that are marked ObsoleteState = Removed; that are getting the warning.
How do we resolve these warnings?  Shouldn't the ObsoleteState be considered?  Or is there a bigger problem here to resolve?
AL Language Information:

Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 3.0.115791
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al

VS Code Information

Version: 1.32.3 (user setup)
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Date: 2019-03-14T23:43:35.476Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

BC Information

On Premise
Version: GB Dynamics NAV 13.3 (27233)
Created: 09/10/2018 17:07

Hi @GreatScott000, we will suppress the warning for table fields with ObsoleteState = Removed.

@JohanStenberg100  Please also suppress for fields in tables with ObsoleteState = Removed even if the field itself is not marked.

@AskeHolst will do, thanks.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 31126 and VS Code Extension Version 3.0.117557.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

Has this been released?


[Bug] Links not connected to node if node symbol type is rect

Version
5.4.3
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html
Steps to Reproduce
With graph settings (for example symbolSize: [120, 50], symbol: 'rect',... ) the arrow is hidden behind node 1 and 2. It seems the link connection(s) to the node(s) is based on a circle which should now be a rectangular (as the symbol of the node itself).
option = {
  title: {
    text: 'Basic Graph'
  },
  tooltip: {},
  animationDurationUpdate: 1500,
  animationEasingUpdate: 'quinticInOut',
  series: [
    {
      type: 'graph',
      layout: 'none',
      symbolSize: [120, 50],
      symbol: 'rect',
      roam: true,
      draggable: true,
      label: {
        show: true
      },
      edgeSymbol: ['circle', 'arrow'],
      edgeSymbolSize: [4, 10],
      edgeLabel: {
        fontSize: 20
      },
      data: [
        {
          name: 'Node 1',
          x: 300,
          y: 300
        },
        {
          name: 'Node 2',
          x: 800,
          y: 300
        },
        {
          name: 'Node 3',
          x: 550,
          y: 100
        },
        {
          name: 'Node 4',
          x: 550,
          y: 500
        }
      ],
      // links: [],
      links: [
        {
          source: 0,
          target: 1,
          symbolSize: [5, 20],
          label: {
            show: true
          },
          lineStyle: {
            width: 5,
            curveness: 0.2
          }
        },
        {
          source: 'Node 2',
          target: 'Node 1',
          label: {
            show: true
          },
          lineStyle: {
            curveness: 0.2
          }
        },
        {
          source: 'Node 1',
          target: 'Node 3'
        },
        {
          source: 'Node 2',
          target: 'Node 3'
        },
        {
          source: 'Node 2',
          target: 'Node 4'
        },
        {
          source: 'Node 1',
          target: 'Node 4'
        }
      ],
      lineStyle: {
        opacity: 0.9,
        width: 2,
        curveness: 0
      }
    }
  ]
};

Current Behavior
Arrow of link not correctly linked to the node(s).
Expected Behavior
The arrow or link so end at the edge of the rectangular symbol/node.
Environment
- OS: All
- Browser: All
- Framework:

Any additional comments?
No response

see related #18247

assign me this

same problem


Controller manager label finalization

We now have a final form for operator controller-manager pod labeling of the format openstack.org/operator-name: <operator name> and are no longer relying on the inconsistent labels created by various operator-sdk versions.  All operators that lack this standardized pattern are being updated.

In line with what we did in glance, thanks!


Update incar.py

Found a couple typos as I was looking through the source code. Biggest one was you defined the function add_keyword_modifer rather than modifier. That could be confusing to users as every instance of a function like this has the word modifier. I changed it in every instance I found it in this code.

Thanks! Looks like I was just copying/pasting without double checking.
Also, checks are failing because of this same typo in tests, but I'll fix it and then merge

all tests pass locally. The CI failing is a separate issue with a new SciPy release (see #166). I'm merging this for now and will fix the CI in a separate PR


feat: add typings for ts-jest options via transform config

Summary

Since we migrated from globals config to transformer config, we need to support types for this migration.
Test plan

Green CI
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
N.A.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 34 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.456%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
3929

Relevant Lines:
4093

💛  - Coveralls


refactor Sanguine

Entire interface changed to material-ui. chart components are combined for comparison. Data filter is managed centrally.

Force pushed these commits onto master


Bump deps

bumps requirements to make it compatible with latest react/socket-client and adds php 7 and 7.1 to travis build.
also updates composer requirement syntax to latest standards.

ping @clue

Thank you for filing this PR! :+1: I've fixed the failing tests with #35, #36 and #37 and have just updated the SocketClient dependency with #38!
This will be released as v0.3.2 shortly, with more version bumps planned for the upcoming v0.4.0 release :shipit:


convert \\n into \n in wrangler pages deploy commit messages

With the following command:
$ npx wrangler pages deploy . --commit-message="this is a \ntest"

Before:

After:

(note: the newline in the dashboard is removed, that is ok as it is consistent with standard multiline git commits)

Closing as this isn't a bug/problem with wrangler itself


Pipe output to jq to validate and compress

The generated part should be piped to jq with the compress flag to have basic validation and make the result smaller.

Implemented in #13


SyncBot: Update reply documentation

Updated reply docs to reference >

Change-Type: patch

Contributor checklist

[ ] Build output been rebuilt and tested
[ ] Introduces security considerations
[ ] Tests are included
[x] Documentation is added or changed
[ ] Affects the development, build or deployment processes of the component

Reviewer Guidelines

When submitting a review, please pick:

'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

@hedss this PR should take about 10 seconds to approve, it is an update to the docs to reflect the reality of >.


Add support for generating examples from a pexpr

Ok, I left a bunch of comments. Overall this looks pretty good!
One more thing: I'd rename the file to pexprs-generateExamples.js -- it's more descriptive, and it's consistent with the name of the method that it defines.


Added source code hosting alternative

Thank you for this RP.
I think this section should be under the already existent "Developer tools" section. Can you modify it?
Also, as a side note, this repo is being mirrored in a Gitea instance. I plan to move it to Codeberg, but I still want to have it active here in GitHub, so I need to find a way to have it updated in both places.  AFAIK, Codeberg does not allow mirroring repos.

Codeberg does not allow mirroring repos.

Allowing people from codeberg to contribute to the repo on gitea should become as easy as if it were on codeberg, once gitea federation becomes stable and is released.

@somerandomguy24 Regarding...

Can you modify it?

I think they're asking you to fix your PR. 😺

@somerandomguy24 Regarding this:

Can you modify it?

I think they're asking you to fix your PR. smiley_cat

I didn't make it, @nuschpl did.


fix: Allow use of hostname in meshNetworks gateways

Part of #13581 - might well fix it?

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mikebryant
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @mikebryant. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-local-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-integ-local-tests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-local-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-integ-local-tests

prow/istio-pilot-multicluster-e2e.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-multicluster-e2e

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-presubmit

prow/istio-unit-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-unit-tests

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-dashboard

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e-simpleTests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-simpleTests

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-local-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-integ-local-tests

prow/istio-pilot-multicluster-e2e.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-integ-k8s-tests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
f28900ad2bd9c0fb9c0f24c4eca35590a12acf95
link
/test istio-integ-k8s-tests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/release-test.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test release-test

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-mixer-no_auth

prow/e2e-bookInfoTests-trustdomain.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test istio_auth_sds_e2e

prow/e2e-bookInfoTests-v1alpha3.sh
ff6c0cb707b87c3b11e38efb7fad1a1c62dc9a4e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
f28900ad2bd9c0fb9c0f24c4eca35590a12acf95
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
f28900ad2bd9c0fb9c0f24c4eca35590a12acf95
link
/test istio-pilot-multicluster-e2e

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
f28900ad2bd9c0fb9c0f24c4eca35590a12acf95
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
78ed94296608e7d522d95c23a3935045c3b3a268
link
/test istio-integ-k8s-tests

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

@mikebryant: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
78ed94296608e7d522d95c23a3935045c3b3a268
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
78ed94296608e7d522d95c23a3935045c3b3a268
link
/test istio-pilot-multicluster-e2e

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

I'm not sure why the tests are failing - I'd appreciate some help with that

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, mikebryant
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest

Cool, tests passed :).
Is there anything else I need to do for this PR? :)


Could not load file or assembly 'Microsoft.Build'

Environment data

`dotnet --info` output:
.NET Core SDK (reflecting any global.json):
 Version:   2.2.100
 Commit:    b9f2fa0ca8

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.100\

Host (useful for support):
  Version: 2.2.0
  Commit:  1249f08fed

.NET Core SDKs installed:
  2.2.100 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

VS Code version:
Version: 1.30.2 (system setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.17134

C# Extension version: Perhaps any version other than newest(1.17.1), for example 1.17.0
Steps to reproduce
This problem only happends when I use Install Another Version to install old versions. I tested several version, all of them have this issue. But back to the time when they were the newest version, I didn't encounter this issue.
I have tried https://github.com/OmniSharp/omnisharp-vscode/issues/2208#issuecomment-384735388 but it doesn't work.
It's also OK to just close. After all, the newest version works and I don't know whether this is my system's problem because it works fine in my win7 x86 VM.
Output Log

Log
Starting OmniSharp server at 1/26/2019, 4:59:45 PM
    Target: c:\dotnet

OmniSharp server started.
    Path: C:\Users\xxx\.vscode\extensions\ms-vscode.csharp-1.17.0\.omnisharp\1.32.6\OmniSharp.exe
    PID: 19264

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Windows 6.2.9200.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Visual Studio Community 2019 16.0.28522.59 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\15.0\Bin"
            2: StandAlone 15.0 - "C:\Users\xxx\.vscode\extensions\ms-vscode.csharp-1.17.0\.omnisharp\1.32.6\msbuild\15.0\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Visual Studio Community 2019 16.0.28522.59 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\15.0\Bin"
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'c:\dotnet'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in 'c:\dotnet'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'c:\dotnet\dotnet.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'c:\dotnet'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location 'c:\dotnet' on host 17296.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: c:\dotnet\dotnet.csproj
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file 'c:\dotnet\dotnet.csproj'.
c:\dotnet\dotnet.csproj(1,1)
System.IO.FileNotFoundException: Could not load file or assembly “Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” or one of its dependencies. The system can not find the file specified.
File name:“Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”
   at OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Load(String filePath, ProjectLoader loader)
   at OmniSharp.MSBuild.ProjectManager.LoadOrReloadProject(String projectFilePath, Func`1 loader)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[fail]: OmniSharp.MSBuild.ProjectManager
        Attemped to update project that is not loaded: c:\dotnet\dotnet.csproj

Currently failing with exact same error message on the latest version of C# Estenstion and VSCode
Starting OmniSharp server at 7/11/2019, 5:57:54 PM
Target: c:\WorkSpace\src\repos\WikiFeedbackLinkInjector
Log
OmniSharp server started.
Path: c:\Users\celabu.vscode\extensions\ms-vscode.csharp-1.20.0.omnisharp\1.32.20\OmniSharp.exe
PID: 45760
    Starting OmniSharp on Windows 6.2.9200.0 (x64)

    DotNetPath set to dotnet

    Located 2 MSBuild instance(s)
        1: Visual Studio Enterprise 2017 15.9.28307.770 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Current\Bin"
        2: StandAlone 15.0 - "c:\Users\celabu\.vscode\extensions\ms-vscode.csharp-1.20.0\.omnisharp\1.32.20\.msbuild\Current\Bin"

    Registered MSBuild instance: Visual Studio Enterprise 2017 15.9.28307.770 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Current\Bin"

    Detecting Cake files in 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector'.

    Could not find any Cake files

    Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.

    No solution files found in 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector'

    Queue project update for 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector\WikiFeedbackLinkInjector.csproj'

    Detecting CSX files in 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider

    Loading project: c:\WorkSpace\src\repos\WikiFeedbackLinkInjector\WikiFeedbackLinkInjector.csproj

    Failed to load project file 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector\WikiFeedbackLinkInjector.csproj'.

c:\WorkSpace\src\repos\WikiFeedbackLinkInjector\WikiFeedbackLinkInjector.csproj(1,1)
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Load(String filePath, ProjectIdInfo projectIdInfo, ProjectLoader loader)
at OmniSharp.MSBuild.ProjectManager.LoadOrReloadProject(String projectFilePath, Func`1 loader) in D:\a\1\s\src\OmniSharp.MSBuild\ProjectManager.cs:line 304
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    Attempted to update project that is not loaded: c:\WorkSpace\src\repos\WikiFeedbackLinkInjector\WikiFeedbackLinkInjector.csproj

    Configuration finished.

    Omnisharp server running using Stdio at location 'c:\WorkSpace\src\repos\WikiFeedbackLinkInjector' on host 30900.

@Cedz You'd better open a new issue


refactor: create PermissionGuardType + allow embeds as custom reply

Please describe the changes this PR makes and why it should be merged:
Simple modification who replace the content (string) option by PermissionGuardOption to control ephemeral state and choose between string or embed for reply content.
Package
@discordx/utilities

Please add documentation to \packages\utilities\README.md

Please add documentation to \packages\utilities\README.md

Done !

\examples\guards\commands\PermissionGuards.ts does not compile at all, please update this file and run it through tsc

see https://github.com/oceanroleplay/discord.ts/commit/07043351fee7f06b85b9a51da23257ed215bfbe9

also see https://github.com/oceanroleplay/discord.ts/commit/641fba58183f6d84e94878f5e44980a899f3cb04
and this changes are untested
cc @VictoriqueMoe

also see 641fba5
and this changes are untested
cc @VictoriqueMoe

Okay. I thought you wanted to avoid:
MessageOptions & {
  ephemeral?: boolean;
};

due to using only djs types? but i am happy with this anyway

Make sure you update the examples and docs

I did but untested updates. so would be good if you test everything.

I would get @bycop to test, as he is the one using this guard

I've tested and it's ok for me


unix,win: support IDNA 2008 in uv_getaddrinfo()

Encode domain names before passing them on to the libc resolver.
Some getaddrinfo() implementations support IDNA 2008, some only
IDNA 2003 and some don't support i18n domain names at all.
This is a potential security issue because it means a domain name
might resolve differently depending on the system that libuv is
running on.
Fixes: https://github.com/libuv/libuv/issues/2028
CI: https://ci.nodejs.org/job/libuv-test-commit/1072/
CI: https://ci.nodejs.org/job/libuv-test-commit/1073/ (double check)

Added more tests and disabled it on z/OS because it breaks the getaddrinfo tests. I speculate it doesn't work because z/OS uses EBCDIC instead of ASCII but that's just guesswork.
CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1074/

Disabled the IDNA test itself on z/OS. I'm pretty convinced by now it's because of EBCDIC. :-)
CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1075/

@cjihrig @santigimeno Can I persuade one of you to take a look? I realize it's a pretty big and subtle PR. I'd have broken it into smaller pieces if I could but it's a pretty atomic change already.

Good idea: https://ci.nodejs.org/view/libuv/job/libuv-in-node/69/
I added one more functional change: uv__idna_toascii() now explicitly rejects invalid UTF-8 with UV_EINVAL.


when is ipv6 supported in the future

I expect that ipv6 can be supported soon.
When is ipv6 supported in the future.

Duplicate of https://github.com/EOSIO/eos/issues/8169


Fix type name typo in Debug Adapter Protocol

Basis is made of Vector3, not Vector2.
I also threw in some other typo fixes, just comments and documentation.

Thanks!


Transfer fee changes

The Chore
https://github.com/vegaprotocol/vega/pull/9983 was recently merged to accomadate changes to transfer fees. We need to update the transfer fee UI to use the new endpoints to provide more accurate estimations
Tasks

[ ] Remove hard coded calculation on the client
[ ] Connect to the new core endpoints covered here that will expose the fees
[ ] Dev
[ ] Test

Additional details / background info

Changes are merged but not in stagnet yet .. once they are we need to do this asap, and we need a good way of deploying it preferably in a way that doesnt mean we need to sync up with Core release in mid-Dec.

While core change is merged it did not make it into the patch release, and now the "Palazzo I" release is not due until January.
Therefore this can be pushed out.  We can pick up once we know we have a new Core version into Stagnet that includes these changes

Closing as dupe of https://github.com/vegaprotocol/frontend-monorepo/issues/5554


[ko] Update outdated files in dev-1.23-ko.2 (M40-M49)

한 PR에 너무 많은 변경사항을 포함시키면 리뷰하기 어려울 수 있어서, 적절히 분할하여 올립니다. 😊

Related issue: #31647 (dev-1.23-ko.2)

10 files to be modified

[ ]  M40.  content/en/docs/reference/_index.md  | 8(+XS) 6(-)
[ ]  M41.  content/en/docs/reference/command-line-tools-reference/feature-gates.md  | 63(+M) 30(-)
[ ]  M42.  content/en/docs/reference/glossary/container-runtime-interface.md  | 1(+XS) 1(-)
[ ]  M43.  content/en/docs/reference/glossary/container-runtime.md  | 2(+XS) 2(-)
[ ]  M44.  content/en/docs/reference/kubectl/conventions.md  | 23(+S) 0(-)
[ ]  M45.  content/en/docs/reference/labels-annotations-taints.md  | 14(+S) 0(-)
[ ]  M46.  content/en/docs/reference/scheduling/policies.md  | 1(+XS) 1(-)
[ ]  M47.  content/en/docs/reference/tools/_index.md  | 13(+S) 6(-)
[ ]  M48.  content/en/docs/reference/using-api/client-libraries.md  | 1(+XS) 0(-)
[ ]  M49.  content/en/docs/setup/best-practices/certificates.md  | 1(+XS) 1(-)

1 files to be renamed

[ ]  R1.  R100 content/en/docs/tutorials/clusters/apparmor.md -> content/en/docs/tutorials/security/apparmor.md

/language ko

/assign

@jihoon-seo 감사합니다!
/lgtm
/approve


Updated Packages for compatibility with RN > 0.60

NetInfo and rn-fetch-blob upgraded

Seems like author of this package is not responding for a long time. In case, if the package is not bing updated for the latest RN, then anyone can remove this and use the forked and updated package which i am using for RN > 0.60 projects.
https://www.npmjs.com/package/@devshq/rn-cached-image
Thanks

Seems like author of this package is not responding for a long time. In case, if the package is not bing updated for the latest RN, then anyone can remove this and use the forked and updated package which i am using for RN > 0.60 projects.
https://www.npmjs.com/package/@devshq/rn-cached-image
Thanks

This one is now working either.  Async storage issue

Seems like author of this package is not responding for a long time. In case, if the package is not bing updated for the latest RN, then anyone can remove this and use the forked and updated package which i am using for RN > 0.60 projects.
https://www.npmjs.com/package/@devshq/rn-cached-image
Thanks

This one is now working either. Async storage issue

Can you share the issue?


Always prompt to log in

I can enter Bingchat, but I can't log in

try to create a new ms account? I met this before. and i created a new ms account, it works.

#119


Learning analytics: Add judgement of learning component

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[ ] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I strictly followed the client coding and design guidelines.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[ ] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[ ] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context

We want to see how students judge themselves with regards to the mastery of a competency.
Description

Remove lots of bugs in star rating and make the fractional stars work
Add a judgement of learning component -> Placed it on the student course dashboard for testing

Steps for Testing
Navigate to the student course dashboard and check it out
Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[ ] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[ ] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

Somehow I did not add the JoL component, it is committed now...