Added authorization support for query string

This patch enable to use query string as an alternative to request header for AWS authorization.
http://docs.aws.amazon.com/general/latest/gr/sigv4_signing.html
reproduce step
make a request with AWS authorization info in query string,
$ curl -H "Accept: application/json" \
-H "Content-type: application/json" \
-H "X-Amz-Target:DynamoDB_20120810.ListTables" \
-H "X-Amz-Content-Sha256:my-sha256" \
-X POST -d "{}" \
"http://localhost:4567/\
?X-Amz-Algorithm=AWS4-HMAC-SHA256\
&X-Amz-Credential=cred%2F20150101%2Fus-east-1%2Fdynamodb%2Faws4_request\
&X-Amz-Date=20150101T100000Z\
&X-Amz-Expires=300\
&X-Amz-SignedHeaders=host%3Bx-amz-target\
&X-Amz-Signature=my-signature"

{"__type":"com.amazon.coral.service#MissingAuthenticationTokenException","message":"Request is missing Authentication Token"}

it shows failed to recognize auth info in query string.
test steps
prepare this commit,
$ git remote add pr git@github.com:evalphobia/dynalite.git
$ git fetch pr
$ git checkout -b feature/auth-query-string  pr/feature/auth-query-string

and run dynalite server.
Then, make a request with AWS authorization info in query string,
$ curl -H "Accept: application/json" \
-H "Content-type: application/json" \
-H "X-Amz-Target:DynamoDB_20120810.ListTables" \
-H "X-Amz-Content-Sha256:my-sha256" \
-X POST -d "{}" \
"http://localhost:4567/\
?X-Amz-Algorithm=AWS4-HMAC-SHA256\
&X-Amz-Credential=cred%2F20150101%2Fus-east-1%2Fdynamodb%2Faws4_request\
&X-Amz-Date=20150101T100000Z\
&X-Amz-Expires=300\
&X-Amz-SignedHeaders=host%3Bx-amz-target\
&X-Amz-Signature=my-signature"

{"TableNames":[]}

It shows success with {"TableNames":[]}.
Next, check the missing paramter request,
$ curl -H "Accept: application/json" \
-H "Content-type: application/json" \
-H "X-Amz-Target:DynamoDB_20120810.ListTables" \
-H "X-Amz-Content-Sha256:my-sha256" \
-X POST -d "{}" \
"http://localhost:4567/\
?X-Amz-Algorithm=AWS4-HMAC-SHA256\
&X-Amz-Credential=cred%2F20150101%2Fus-east-1%2Fdynamodb%2Faws4_request\
&X-Amz-Date=20150101T100000Z\
&X-Amz-Expires=300\
&X-Amz-SignedHeaders=host%3Bx-amz-target"

{"__type":"com.amazon.coral.service#MissingAuthenticationTokenException","message":"Request is missing Authentication Token"}

It shows failed to authorize since the rack of necessary parameter.

actually I'm not a nodejs coder, so my code could be violated some common rules.
When that, please tell me  ; )
thanks.

Great! Thanks for doing this – I hadn't realised that DynamoDB could be called this way.
I'm on vacation at the moment, but I should be able to have time in the next few days to look this over.

@mhart
How was your vacation?
It seemed to be conflicted whiled ago, so I just amended my commit and re-pushed it.
If you have anything unsure or a better approach I'd be happy to discuss it ;)

Finally got around to testing this – thanks so much!
Merged in, modified slightly, and published as v0.9.0

Great! thanks!
so I can use dynalite for golang sdk =)

Oh right – so the golang sdk uses query string authentication? Seems a bit weird, no? Isn't it more efficient (ie, less bytes) just to use the standard Authorization header?


⚠ Bofrost.at has degraded performance

In ee123a0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1103 ms

Resolved: Bofrost.at performance has improved in bc7c799.


Issue in generating finished.reuters file

Using calc_finished_ticker() function the news_reuter.csv is to be transformed to finished.reuters file for reading that file and generating the stockPrices_raw.json file in crawlers_yahoo_finance.py code but then the following error arises:
fin = open('./input/finished.reuters')
FileNotFoundError: [Errno 2] No such file or directory: './input/finished.reuters'
due to which stockPrices_raw file not generated and henceforth difficult to generate stockPrices.json.
Please advise.

I think you first need to double check whether "finished.reuters" file is actually generated by calc_finished_ticker() function.

it is not getting generated is there any error in the code line?
def calc_finished_ticker():
os.system("awk -F',' '{print $1}' ./input/news_reuters.csv | sort | uniq > ./input/finished.reuters")

It's essentially using Python to run a bash script:
awk -F',' '{print $1}' ./input/news_reuters.csv | sort | uniq > ./input/finished.reuters
Can you run this script directly on your bash terminal without using Python?


react-native-svg @>=6.5 onPress stops working after navigating between tabs

Hello all,
I'm currently using react-navigation w/ react-native-svg and a weird interaction is occuring: whenever I navigate outside of a screen with a SVG component, when I go back to it the onPress callbacks inside the SVG stops working. From my tests, this happens on RN-SVG after version 6.5, on Android, though I did not have the opportunity to test it out on iOS.
Here's a minimal example showcasing the problem:
import * as React from 'react';
import { Text, View, StyleSheet, Dimensions } from 'react-native';
import Svg, { Circle } from 'react-native-svg';
import {createBottomTabNavigator} from 'react-navigation'

const { width } = Dimensions.get('window');

const FirstTab = () => (
  <View><Text>First Tab</Text></View>
)

const SecondTab = () => (<View style={styles.container}>
        <Svg
          width={`${width}`}
          height={`${width}`}
          viewBox="-200 -200 400 400"
          style={{ backgroundColor: '#fff' }}
          onTouchStart={() => console.log('touchStart')}
          onTouchEnd={() => console.log('touchEnd')}
          onTouchMove={() => console.log('onTouchMove')}>
          <Circle
            onPressIn={() => console.log('onPress')}
            onResponderMove={() => {
              return;
            }}
            onResponderGrant={() => console.log('onResponderGrant')}
            onResponderReject={() => console.log('onResponderReject')}
            onResponderEnd={() => console.log('onResponderEnd')}
            onResponderRelease={() => console.log('onResponderRelease')}
            onResponderStart={() => console.log('onResponderStart')}
            onResponderTerminate={() => console.log('onResponderTerminate')}
            stroke="black"
            strokeWidth="5"
            r="40"
            fill={'#fff'}
          />
        </Svg>
      </View>)

const tabNavigator = createBottomTabNavigator({
  FirstTab,
  SecondTab
})

export default tabNavigator;

const styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
    backgroundColor: '#ecf0f1',
  },
});

Do the following:

Load this code with<EMAIL_ADDRESS>open app, go to "Second Tab"
Press on the circle. Your console will output all relevant events, as expected.
Navigate to "First Tab", and then back to "Second Tab"
Press the circle again. Now, only the SVG's touchStart, touchMove and touchEnd events will fire, as if the Circle never had any onPress events. No Responder granting, no rejecting, nothing.

Do notice that, if you do this on Snack, the error will not occur because Expo uses<EMAIL_ADDRESS>which is working fine.
I've tested this with version 7.0(it still happens there) and all versions from 6.2 to 6.5, which means the error was introduced somewhere in 6.5 I believe.
Thank you for your time.

Can you try with the latest commit from the master branch and this code instead:
I've removed the onResponderGrant/Release/Reject/Terminate handler, not to override the ones from the SvgTouchableMixin, it seems to give all the events, both on first and second view now.
import * as React from 'react';
import { Text, View, StyleSheet, Dimensions } from 'react-native';
import Svg, { Circle } from 'react-native-svg';
import {createBottomTabNavigator} from 'react-navigation'

const { width } = Dimensions.get('window');

const FirstTab = () => (
  <View><Text>First Tab</Text></View>
)

const SecondTab = () => (<View style={styles.container}>
  <Svg
    width={`${width}`}
    height={`${width}`}
    viewBox="-200 -200 400 400"
    style={{ backgroundColor: '#fff' }}
    onTouchStart={() => console.log('touchStart')}
    onTouchEnd={() => console.log('touchEnd')}
    onTouchMove={() => console.log('onTouchMove')}>
    <Circle
      onPressIn={() => console.log('onPressIn')}
      onPress={() => console.log('onPress')}
      onPressOut={() => console.log('onPressOut')}
      onResponderEnd={() => console.log('onResponderEnd')}
      onResponderStart={() => console.log('onResponderStart')}
      stroke="black"
      strokeWidth="5"
      r="40"
      fill={'#fff'}
    />
  </Svg>
</View>)

const tabNavigator = createBottomTabNavigator({
  FirstTab,
  SecondTab
})

export default tabNavigator;

const styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
    backgroundColor: '#ecf0f1',
  },
});

I'm having the same issue on Android (not iOS). I'm using version 7.0.2. I also tried upgrading to 8.0.1 but the issue remains. Also, upgrading to 8.0.1 forced me to update my Gradle version to 3.0.1 and gives me the following error on iOS:

and this on Android:

@tovesson can you provide a full replication? I get the feeling that shouldn't be possible in 8.0.1 are you sure you rebuilt the native code successfully?

I solved it by updating to version 7.2.0 and clearing cache after you instructions :)
https://github.com/react-native-community/react-native-svg/issues/814#issuecomment-430022466

I am using the v 8.0.0 and it is not working...

Try v8.0.3

Nop working with v8.0.3, I am testing in an AVD with nexus 5x API27 (Android 8.1)
Mi SVG.. I should have an extra configuration?
 <View> <Svg width={100} height={100} viewBox={0 0 100 100} >                                 <Circle                                     cx="50%"                                     cy="50%"                                     r="38%"                                     fill="red"                                     onPress={() => alert('Press on Circle')}                                 />                             </Svg> </View>

@tufik2 Seems you have some caching issues. Try
watchman watch-del-all
rm -fr $TMPDIR/react-*
npm start -- --reset-cache

Or,
rm -rf node_modules
npm i
npm start -- --reset-cache


Host: Cancel Game

Currently, there is no way to cancel a game. This should be possible at any point after Open.

done


Unreproducable benchmark result

hyperfine result:
hyperfine 'fastfetch -c ~/bench.jsonc' 'target/release/crabfetch'
Benchmark 1: fastfetch -c ~/bench.jsonc
  Time (mean ± σ):      20.4 ms ±   3.1 ms    [User: 5.5 ms, System: 8.2 ms]
  Range (min … max):    13.1 ms …  31.8 ms    138 runs

Benchmark 2: target/release/crabfetch
  Time (mean ± σ):     104.1 ms ±   4.2 ms    [User: 75.7 ms, System: 19.6 ms]
  Range (min … max):    97.3 ms … 117.0 ms    28 runs

Summary
  fastfetch -c ~/bench.jsonc ran
    5.10 ± 0.80 times faster than target/release/crabfetch

Fastfetch is faster than crab in my machine because of your cheating version detection code doesn't support Fedora.
Crab output:
    carter@carter-macbookpro
    ――――――――――――――――
    CPU > Unknown Unknown (10c 10t) @ 3.23 GHz
    Memory > 9.14 GB / 16.11 GB (56.74%)
    Swap > 68.16 MB / 8.59 GB (0.79%)
    Disk (/) > 28 GB used of 90.59 GB (31.4%) [btrfs]
    Disk (/home) > 28 GB used of 90.59 GB (31.4%) [btrfs]
    Disk (/boot) > 330 MB used of 1.01 GB (32.55%) [ext4]
    Disk (/var/lib/nfs/rpc_pipefs) > 0 KB used of 0.00 KB (NaN%) [rpc_pipefs]
    Disk (/run/media/carter/JZAO_128G) > 34 GB used of 124.59 GB (27.21%) [vfat]
    Host > Unknown
    Display (Unknown Unknown) > 3456x2234 @ 60Hz (eDP-1)
    Display (Unknown Unknown) > 3840x2160 @ 60Hz (HDMI-A-1)
    Operating System > Fedora Linux Asahi Remix 40 (KDE Plasma) (6.9.12-401.asahi.fc40.aarch64+16k)
    Packages > 2841 (rpm)
    Desktop > KDE (wayland)
    Terminal > konsole 24.05.2
    Shell > fish 3.7.0
    Battery > Unknown
    Editor > NeoVim 0.10.1
    Uptime > 1h 20m 44s
    Locale > zh_CN (utf8)
    Music > Unknown
    Init System > systemd
    Total Processes > 419

Crab config
# For more in-depth configuration docs, please view https://github.com/LivacoNew/CrabFetch/wiki

# The modules to display and in what order.
# All modules; space, underline:{length}, segment:{name}, end_segment, hostname, cpu, gpu, memory, swap, mounts, host, displays, os, packages, desktop, terminal, shell, battery, uptime, locale, editor, colors, bright_colors
modules = [
    "hostname",
    "underline:16",

    "cpu",
    "gpu",
    "memory",
    "swap",
    "mounts",
    "host",
    "displays",

    "os",
    "packages",
    "desktop",
    "terminal",
    "shell",
    "battery",
    "editor",
    "uptime",
    "locale",
    "music",
    "initsys",
    "processes",

    "space",
    "colors",
    "bright_colors"
]

# Whether to treat unknown modules as a raw text output, allowing you to use custom strings n stuff.
# Yes, these support color placeholders.
unknown_as_text = false

# The default /separator between a modules title and it's value
separator = " > "
# The default color of a modules title
# Can be; black, red, green, yellow, blue, magenta, cyan, white
# All of these can be prefixed with "bright_" to be lighter versions, e.g bright_red
title_color = "bright_magenta"
# Whether to bold/italic the title by default too
title_bold = false
title_italic = false

# The default decimal places to provide in a module
decimal_places = 2

# Whether to have all module values as inline, e.g; https://i.imgur.com/UNyq2zj.png
# To add padding use the "separator" and add some spaces
inline_values = false

# The character to use in the underline module
underline_character = '―'

# The character for each color in the colors module
color_character = "   "
# Margin between each character
color_margin = 0
# And if to set the color to the background instead of on the character
color_use_background = true

# Format of segments
# Segments can be defined in the modules array
segment_top = "{color-white}[======------{color-brightmagenta} {name} {color-white}------======]"
segment_bottom = "{color-white}[======------{color-brightmagenta} {name_sized_gap} {color-white}------======]"

# Formatting characters used in progress bars
progress_left_border = '['
progress_right_border = ']'
progress_progress = '='
progress_empty = ' '
# The target length of the progress bar
progress_target_length = 20

# Whether to use 'ibibytes opposed to 'gabytes
# E.g use Gibibytes (GiB) opposed to Gigabytes (GB)
use_ibis = false

# Whether to use known checksums to attempt to find the version of some stuff e.g terminal/shell/editor
# Disabled by default as it was seen as "too cheaty"
# If your benchmarking, disable it as well. If your a end user, you likely won't care if it's on or not.
use_version_checksums = false

# Whether to supress any errors that come or not
suppress_errors = true

# Percentage coloring thresholds
# Empty this section to make it not color
# Values are in the format of "{percentage}:{color}"
percentage_color_thresholds = [
    "75:brightgreen",
    "85:brightyellow",
    "90:brightred"
]

[ascii]
# If to display the ASCII distro art or not
display = true

# The colors to render the ASCII in
# This array can be as long as the actual ASCII. Each entry represents the color at a certain %
# E.g ["red", "green"] would render the top half as red and the bottom half as green.
# ["yellow", "blue", "magenta"] would render 33.33% as yellow, then blue, than magenta.
colors = ["bright_magenta"]

# The amount of space to put between the ASCII and the info
margin = 4

# Below here is the actual modules
# Refer to the wiki for any module-specific parameters or hidden parameters
# Also remember that you can override some stuff on these, e.g the title formatting. Again check the wiki.

[hostname]
title = ""
# Placeholders;
# {hostname} -> The hostname
# {username} -> The username of the current user
format = "{color-brightmagenta}{username}{color-white}@{color-brightmagenta}{hostname}"

[cpu]
title = "CPU"
# Placeholders;
# {name} -> The name of the cpu.
# {core_count} -> The number of cores.
# {thread_count} -> The number of threads.
# {current_clock_mhz} -> The current clock speed, in MHz.
# {current_clock_ghz} -> The current clock speed, in GHz.
# {max_clock_mhz} -> The maximum clock speed, in MHz.
# {max_clock_ghz} -> The maximum clock speed, in GHz.
# {arch} -> The architecture of your CPU.
format = "{name} {arch} ({core_count}c {thread_count}t) @ {max_clock_ghz} GHz"

[gpu]
# Whether to try to search a separate AMD specific file to try to improve accuracy on AMD GPU's
amd_accuracy = true

# Ignore any GPU's that are marked as "disabled" by Linux
ignore_disabled_gpus = true

# Placeholders;
# - {index} -> The index of the GPU, only useful if you have more than one GPU.
title = "GPU"
# Placeholders;
# {vendor} -> The vendor of the GPU, e.g AMD
# {model} -> The model of the GPU, e.g Radeon RX 7800XT
# {vram} -> The total memory of the GPU.
format = "{vendor} {model} ({vram})"

[memory]
title = "Memory"
# Placeholders;
# {used} -> The currently in-use memory.
# {max} -> The maximum total memory.
# {bar} -> A progress bar representing the total space available/taken.
# {percent} -> Percentage of memory used
format = "{used} / {max} ({percent})"

[swap]
title = "Swap"
# Placeholders;
# {used} -> The currently used swap.
# {max} -> The maximum total swap.
# {bar} -> A progress bar representing the total space available/taken.
# {percent} -> Percentage of swap used
format = "{used} / {total} ({percent})"

[mounts]
# Each mount has it's own entry. Title Placeholders;
# {device} -> Device, e.g /dev/sda
# {mount} -> The mount point, e.g /home
# {filesystem} -> The filesystem running on that mount.
title = "Disk ({mount})"

# Placeholders;
# {device} -> Device, e.g /dev/sda
# {mount} -> The mount point, e.g /home
# {space_used} -> The space used.
# {space_avail} -> The space available.
# {space_total} -> The total space.
# {filesystem} -> The filesystem running on that mount.
# {bar} -> A progress bar representing the total space available/taken.
# {percent} -> The percentage of the disk used.
format = "{space_used} used of {space_total} ({percent}) [{filesystem}]"

# A ignore list for any point points OR filesystems to ignore
# The entries only need to start with these to be ignored
ignore = [
    # Filesystems
    "tmpfs",
    "fuse",
    "binfmt",
    "configfs",
    "debugfs",
    "mqueue",
    "tracefs",
    "hugetlbfs",
    "bpf",
    "pstore",
    "cgroup",
    "dev",
    "securityfs",
    "autofs",
    "efivar",
    "sys",
    "proc",
    "swap",
    "ramfs",

    # Mounts
    "/boot/",     # Boot partition
    "/snap/",     # Snap
    # Android-Specific Ignored Mounts
    # I have no idea what these do, they just seem to be irrelevant to my termux environment
    "/sys/",
    "/apex/",
    "/dev/",
    "/cache",
    "/data",
    "/product",
    "/prism",
    "/omr",
    "/odm",
    "/efs",
    "/optics",
    "/vendor",
    "/metadata",
    "/system"
]

[host]
title = "Host"
# Placeholders;
# {host} -> The name of the host, either a motherboard name or a laptop model
# {chassis} -> The chassis type, e.g Desktop or Laptop or whatever
format = "{host} ({chassis})"

[displays]
# Will make a new line per entry.
# Title Placeholders;
# {name} -> The monitor DRM name, e.g DP-2
# {make} -> The monitor's make
# {model} -> The monitor's model
title = "Display ({make} {model})"

# The format each display should be in. Placeholders;
# {make} -> The monitor's make
# {model} -> The monitor's model
# {name} -> The monitor DRM name, e.g DP-2
# {width} -> The monitor's width
# {height} -> The monitor's height
# {refresh_rate} -> The monitor's refresh rate. This won't work in x11!
format = "{width}x{height} @ {refresh_rate}Hz ({name})"

# Whether to scale the width/height according to the screen's scale. Only availabe on Wayland.
# This will output wrong with fractional scaling, as the library used to interact with Wayland doesn't support fractional scaling yet.
scale_size = false

[os]
title = "Operating System"
# Placeholders;
# {distro} -> The distro name
# {kernel} -> The kernel version
format = "{distro} ({kernel})"

# Display the kernel version on a newline and if so, what format to use
# Only {kernel} is available in format.
newline_kernel = false
kernel_title = "Kernel"
kernel_format = "Linux {kernel}"

[packages]
title = "Packages"
# This format is for each entry, with all entries being combined into a single string separated by a comma. Placeholders;
# {manager} -> The name of the manager
# {count} -> The amount of packages that manager reports
format = "{count} ({manager})"

# List of package managers to ignore, for whatever reason you choose to
ignore = []

[desktop]
title = "Desktop"
# Placeholders;
# {desktop} -> The name of the desktop
# {display_type} -> The type of display server, aka x11 or wayland.
format = "{desktop} ({display_type})"

[terminal]
title = "Terminal"
# Placeholders;
# {name} -> The name of the terminal, e.g kitty
# {path} -> The path of the terminal, e.g /usr/bin/kitty
# {version} -> The version of the terminal
format = "{name} {version}"

# Whether to find the name of the current PTS if SSH is being used. This is a togglable option as most people probably won't care to go hunting for it.
chase_ssh_pts = false

[shell]
title = "Shell"
# Placeholders;
# {name} -> The name of the shell, e.g zsh
# {path} -> The path of the shell, e.g /usr/bin/zsh
# {version} -> The version of the shell.
format = "{name} {version}"

# Whether to show your default shell, instead of your current shell.
show_default_shell = false

[uptime]
title = "Uptime"

[editor]
title = "Editor"
# Placeholders;
# {name} -> The name of the editor
# {path} -> The path the editor is at
# {version} -> The version of the editor.
format = "{name} {version}"

# Whether to turn the name into a "fancy" variant. E.g "nvim" gets turned into "NeoVim"
fancy = true

[locale]
title = "Locale"
# Placeholders;
# {language} - The selected language
# {encoding} - The encoding selected, most likely UTF-8
format = "{language} ({encoding})"

[music]
title = "Music"
# Placeholders;
# {track} - The name of the track
# {album} - The name of the album
# {track_artists} - The names of all track artists
# {album_artists} - The names of all album artists
format = "{track} by {track_artists} ({album})"

# The player to get music data from
# The player must support the MPRIS standard (most do.)
# Known good selections; (make a GitHub issue if a known good one needs added here)
# - spotify
player = "spotify"

[battery]
title = "Battery"
# Placeholders;
# {percentage} -> The battery percentage
format = "{percentage}%"

[initsys]
title = "Init System"

[processes]
title = "Total Processes"

[datetime]
title = "Date Time"
# Available placeholders; https://docs.rs/chrono/latest/chrono/format/strftime/index.html#specifiers
# CrabFetch wiki page coming soon for it instead (tm)
format = "%H:%M:%S on %e %B %G"

# You've reached the end! Congrats, have a muffin :)

Some comments:

Crab fails to detect my CPU name. It's ok as Crab doesn't support asahi
Crab fails to detect my GPU. Ok too because of asahi
Crab shows a useless mount point. I suggest you add it to your default config so that crab works out of box.
Crab fails to detect my host model. Ok too because of asahi
Crab shows Unknown Unknown as my display model. It's because EDID is not available on asahi. Unknown Unknown is technically ok but not user friendly.
Crab fails to detect my battery level. The comment in crab config file say it's supported. Should be a bug.
Crab fails to detect the music player. You ask users to set the player name of MPRIS standard. My question is: how the can a normal user know what the f*** MPRIS is? You should make crab work out of box.

fastfetch output
                   ##  **                     carter@carter-macbookpro
                *####****.                    ----------------
                  ###,                        CPU > Apple M1 Pro (10) @ 3.23 GHz
               ...,/#,,,..                    GPU > Apple M1 Pro (16) @ 1.30 GHz [Integrated]
          /*,,,,,,,,*,........,,              Memory > 8.55 GiB / 15.00 GiB (57%)
        ,((((((//*,,,,,,,,,......             Swap > 65.00 MiB / 8.00 GiB (1%)
       ((((((((((((((%............            Disk (/) > 26.49 GiB / 84.37 GiB (31%) - btrfs
     ,(((((((((((((((@@(............          Disk (/run/media/carter/JZAO_128G) > 31.58 GiB / 116.04 GiB (27%) - vfat [External]
    (((((((((((((((((@@@@/............        Host > Apple MacBook Pro (16-inch, M1 Pro, 2021)
  ,((((((((((((((((((@@@@@&*...........       Display (HDMI-A-1) > 3840x2160 @ 60 Hz (as 1920x1080) in 32″ [External]
 ((((((((((((((((((((@@@@@@@&,...........     Display (eDP-1) > 3456x2234 @ 60 Hz (as 1728x1117) in 16″ [Built-in] *
(((((((((((((((((((((@@@&%&@@@%,..........    OS > Fedora Linux Asahi Remix 40 (KDE Plasma) aarch64
 /(((((((((((((((((((@@@&%%&@@@@(........     Kernel > Linux 6.9.12-401.asahi.fc40.aarch64+16k
    ,((((((((((((((((@@@&&@@&/&@@@/..         Packages > 2841 (rpm)
        /((((((((((((@@@@@@/.../&&            DE > KDE Plasma 6.1.3
           .(((((((((@@@@(....                Terminal > konsole 24.5.2
               /(((((@@#...                   Shell > fish 3.7.0
                  .((&,                       Battery > 100% [AC Connected]
                                              Editor > nvim 0.10.1
                                              Uptime > 1 hour, 19 mins
                                              Locale > zh_CN.utf8
                                              Media > Yu-peng Chen - Daughter of the Sea and the Moon (Playing)
                                              Init System > systemd 255.10-1.fc40
                                              Processes > 421

Fastfetch config
{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "logo": {
    "color": {
      "1": "35",
      "2": "35"
    }
  },
  "display": {
    "color": "35",
    "separator": " > "
  },
  "modules": [
    "title",
    {
      "type": "separator",
      "length": 16
    },

    "cpu",
    "gpu",
    "memory",
    "swap",
    "disk",
    "host",
    "chassis",
    "display",

    "os",
    "kernel",
    "packages",
    "de",
    "terminal",
    "shell",
    "battery",
    "editor",
    "uptime",
    "locale",
    "media",
    "initsystem",
    "processes",

    "break",
    "colors"
  ]
}

Don't get me wrong! I love crab! No one like me keeps having crab from its very first version! I'd like to make crab better!
And I know you love fastfetch too though you said fastfetch is yucky, or you won't keep taking features from fastfetch ;)

Output of crabfetch --benchmark please, my suspicion is konsole being slow but I wanna confirm it.

because of your cheating version detection code

If your now calling the package manager version query "cheating", I fully disagree. I gave you the checksum complaint, as I agreed it was kinda cheeky, but package manager is a perfectly fine place to get the version a bit faster so long as the binary is in /usr/bin?

Crab fails to detect my battery level. The comment in crab config file say it's supported. Should be a bug.

Output of ls /sys/class/power_supply too please
Currently battery only supports a single battery at a time that gets manually specified, I now have the Rust knowledge to improve this though so can investigate how Asahi does it quickly.

Crab shows a useless mount point. I suggest you add it to your default config so that crab works out of box.

Already got a plan to address this in my 0.4.3 to-do list.

My question is: how the can a normal user know what the f*** MPRIS is?

This is also already planned to be addressed on my to-do list, by making the specifying optional for extra performance if the user requires it. To answer your question, I would argue someone using the command-line would have a basic understanding of how to Google what MPRIS is and have the ability to run playerctl --list for their own system...?

.....? The issue ain't fixed lol, stop closing them early. I just want those outputs to investigate, that's all

Guessing you don't care about this issue since it's closed but I shall update regardless; it appears I have been blind, and this does indeed apply to konsole.
Will add specific detections for these as well as experiment with what else exports these convenient vars today, feel free to re-test once it's commited.


Liberalize type of d3.event

To address #4590 and issues like it, I've created an interface Event that extends both KeyboardEvent and MouseEvent. It should probably extend others, but this should do for starters. It's impossible to really know what event is being handled since d3 uses a single global value (for shame!), so perhaps it's best to pretend it's of many types and let the user handle it as they see fit.
The interface d3.Event is currently empty, but I'll try to find some time to document the properties d3 adds in some situations.

@gustavderdrache thanks mate!


Message json

Don't merge this yet, just making the pull request. I'll let you know when this is done.

Does this seem done to you @Exxonnnnnn

Yeah all looks good, I'm fine with merging it whenever.


mm3

ad

ad

jk

m,

asd

ad

ad

fg

ad

asd

asd

sdf

dsf

asd

asd

as

df

asd

sf

asd

ad

ad

ad

ad

dsda

ok

j

ok

okok

m

ok


[core] Introduce RecordWithPositionIterator interface

Purpose
This is the first step of https://github.com/apache/incubator-paimon/issues/2898, in this PR:

introduce RecordWithPositionIterator
implement it with orc and parquet format

Tests

API and Format

Documentation

+1


pod requires running as root?

I have a PSP defined that limits containers/images running as root. kube-hunter, like many images from public registries, fail with the following events:
Successfully assigned default/kube-hunter-tfm68 to <ip_address>
Pulling image "aquasec/kube-hunter"
Successfully pulled image "aquasec/kube-hunter"
Error: container has runAsNonRoot and image will run as root
Name:           kube-hunter-tfm68
Namespace:      default
Priority:       0
Node:           <hostname/ip_address>
Start Time:     Thu, 10 Oct 2019 01:22:47 +0000
Labels:         controller-uid=
job-name=kube-hunter
Annotations:    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
kubernetes.io/psp: restricted
Status:         Pending
IP:             <IP_ADDRESS>
Controlled By:  Job/kube-hunter
by default maybe this shouldn't run as root

Hi @cvernooy23! sorry about the delay.
Did you try to run kube-hunter with security context of non root user?
As mentioned by @lizrice in #279, the job.yaml spec in this repository is just an example for running kube-hunter and you may change its configuration to fit your needs.

Closing as being stale.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_cb74b0e0-c936-4606-b7e2-45dff1ab7296/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_cb74b0e0-c936-4606-b7e2-45dff1ab7296.git

Docs Build status updates of commit 51dfd7b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-BackendEngineExceptionError] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Implement the OpenBookQA evaluation

On OpenBookQA [MCKS18], GPT-3 improves significantly from zero to few shot settings but is still over 20 points short of the overall SOTA. GPT-3’s few-shot performance is similar to a fine-tuned BERT Large baseline on the leaderboard.

Note: HuggingFace includes this in its datasets package.
https://huggingface.co/datasets/openbookqa

Working on adding this.

#42


Refactor Hit struct to be an enum?

Love this crate. API wrappers are the unsung heroes of any application ecosystem, and I'm glad to see any improvements to Rust's application-level situation. Having said that, I'm curious if this library can map to some common Rust idioms.
In this case, as of version 0.4.0, this library still uses a struct to represent a Hit, or search result from the Genius API.
https://github.com/alt-art/genius-rs/blob/283c0825e88eeaef6cdf79ea9afdf801600f249a/src/search.rs#L5-L11
Can this be changed? serde allows the deserialization of enums, and if there are even types other than "song" that would appear in the type field, an enum could be used to represent them. It would certainly be much easier to use than having to read all the public fields of each type.
I couldn't find a complete list of "type"s that Genius search hits can have, but since they seem to only currently support a song type, it is likely they may simply have future proofed, intending to update their database later on to distinguish between music videos and songs, which they currently do not do. For the time being, a single-variant, #[non-exhaustive] enum could represent this perfectly.

I don't use enums because I have no experience with them, the examples of the enum representation of serde seems disheartening, if you have an example of this I will check.
Genius API supports many types of searches, but they only offer developers a small music search, in a no longer future I will support these types.

Without confirming (I am away from a computer at present), a possible representation could look like:
#[derive(Deserialize, Debug)]
#[serde(tag = "type", content = "result")]
#[non_exhaustive]
pub enum Hit {
    Song(Song)
}

This uses serde's support for adjacent tagging to handle possible outcomes. This sample code may not be ideal, as it does remove support for the index value, but by my recollection, that information isn't really something consumers of the crate would use, since they would presumably get whatever results they need in the Vec of Hits. If the index is used for pagination, that's a crate implementation detail.

Hmm, the way you did it would be possible:
#[derive(Deserialize, Debug)]
#[serde(tag = "type", content = "result")]
#[serde(tag = "type", content = "album")]
#[non_exhaustive]
pub enum Hit {
    #[serde(alias = "song")]
    Song(Song)
    #[serde(alias = "album")]
    Album(Album)
}

?

I reviewed the API responses for certain types of research and I think that even, so I will have to write another structure to treat some cases.
See multiple types search,  articles search and tiny song search


Pass arguments into main application

Forward specified arguments to main application

This is done by specifying arguments to FunStart4J prepended with -J.


Update: Add cursor: pointer to the state panel button

I would like to set the cursor style of the state panel button to pointer.
The reason for it is that I have just recently discovered that it is possible to click on the Form State: ON / OFF text and expand table showing the overall state of the form. There is nothing that indicates that this text is clickable, I believe that this small change might improve that. 🙂

thanks for the PR.


Move Util.kt to identity-android-legacy.

The Util.kt (née Util.java) contains a variety of random utility functions, organically grown over time. Move to
identity-android-legacy library which is already scheduled for deletion.
With this change we can delete the cbor-java dependency from everywhere except identity-android-legacy, appholder, and appverifier meaning we are getting closer to making identity and identity-mdoc true Kotlin Multiplatform libraries.
Test: All unit tests pass.
Test: Manually tested all apps and samples.

Thanks! OK, landing this for now, will followup with a PR for the other things!


Multiple versions

This adds support for multiple versions of PowerDNS. I have limited it to 4.0 and 4.1.
Acceptance tests on CentOS, Ubuntu and Debian were all successful. These tests are not part of Travis CI unfortunately as Vagrant is not supported.
@alexjfisher would you mind having a look at these changes when you have the time?

LGTM.
I do wonder if the module really needs to ship the schema files though?  Instead, is it possible to use the ones that come with the packages?

I never knew they were part of the packages to be honest. I'll open a new issue to look into that.
Thanks for looking at the pull request!


Cannot rate the Google developers articles

I'm getting a 404 page when trying to vote the articles (example).

Even this is off-topic here, I still think it's an important issue to be solved. :smile:
PS. In the future, where to report such issues?

Hmmm, this was fixed, but still the question remains: PS. In the future, where to report such issues?

Appears to be working now.  In the future - this is a great place!


Fixed missing image

Category

[x] Content fix
[ ] New article

Added missing image to The Microsoft 365 Maturity Model – Governance, Risk, and Compliance Competency

Docs Build status updates of commit 32fcb22:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/media/microsoft365-maturity-model--governance-and-compliance/grc-competency-overview.png
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--governance-and-compliance.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


https Fails to work from Cloudflare

Hello,
I installed yourls 1.7.6 on a free web host and it works fine with http, but, when i allowed https from cloudflare it won't create new short links, can  u suggest a way.
http://urlz.ga/go/
THANK U.

There's an issue template and it's not for nothing. Feel free to add details in this issue.

I did not understand your point sir.

When you open an issue, it's pre-filled with a template. This template is here to collect informations that are the bare minimum to expect assistance. "when i allowed https from cloudflare" doesn't give the slightest information on what you exactly did and what might be the "bug" on the YOURLS part.

so i need to close this one and re-open or explain again

As I said above : Feel free to add details in this issue.

ok,
I installed yourls 1.7.6 on 0hi.me free web host.
And it works fine, but when i changed server names to point to cloudflare to get https, the script does not create new urls, it keeps pending without result.
http://urlz.ga/go/

@mtsmayad Your hosting service specifically bans URL shorteners, btw. And you still haven't provided the details required by the issue template.


Update code formatting

!XXX doesn't render as code formatting, XXX does.
Before:

After:

Right, thank you!


Get current namespace when parent namespace is empty string

This fixes issue: #533
Originally pull request #630

Thanks a lot @ibash, please merge your commits into a single one so I can merge your PR as requested in our Guidelines for Submitting a Pull Request :+1:

Squashed and rebased onto latest master. @herom I noticed that my last build failed on node 12: https://travis-ci.org/vpulim/node-soap/jobs/63788061
I just tried it locally and it seemed to pass - if the current one fails can you help me debug?
Thanks!

Thanks @ibash :+1:
I've seen TravisCI builds fail without any reason (last time it failed when testing a PR that only changed our license entry in the package.json) - this one seems to pass now :smiley_cat:


Variables with names that include scope modifiers cannot be removed

Steps to reproduce
$Green = @{ForegroundColor = 'Green'}
Write-Host "Create a variable named literally 'Global:MyVar' in the local scope" @Green
New-Variable -Scope Local -Name Global:MyVar -Value 123
$V = Get-Variable | Where-Object Name -eq Global:MyVar
$V
Write-Host "Try to remove variable 'Global:MyVar'"
$V | Remove-Variable
Write-Host "The variable should no longer be present." @Green
Get-Variable | Where-Object Name -eq Global:MyVar

Expected behavior
Create a variable named literally 'Global:MyVar' in the local scope

Name                           Value
----                           -----
Global:MyVar                   123

Try to remove variable 'Global:MyVar'
The variable should no longer be present.

Actual behavior
Create a variable named literally 'Global:MyVar' in the local scope

Name                           Value
----                           -----
Global:MyVar                   123
Try to remove variable 'Global:MyVar'
Remove-Variable : Object reference not set to an instance of an object.
At line:8 char:6
+ $V | Remove-Variable
+      ~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Remove-Variable], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.RemoveVariableCommand

The variable should no longer be present.
Global:MyVar                   123

Environment data

Name                           Value
----                           -----
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

IMO, New-Variable should not accept variable special chars, because such variables are not possible without `${}``
${bla:foo} = 1`

@kvprasoon
${bla:foo} = 1 => Cannot find drive. A drive with the name 'bla' does not exist
${variable:bla:foo} = 1 => OK

Yes, It works only that way. But New-Variable accepts it and creates nothing. Hence the Bug is in New-Variable as well, or it should allow to create such variables, hence it can be retrieved using ${} notation.

@kvprasoon
The problem is only with variable with a scope modifier prefix (like global: or local:) and remove-variable
New-Variable -Name global:foo -Value 1
Get-Variable -Name global:foo
${variable:global:foo}
Remove-Variable -Name global:foo => Object reference not set to an instance of an object.

With your previous example, everything work :
New-Variable -Name bla:foo -Value 1
Get-Variable -Name bla:foo
${variable:bla:foo}
Remove-Variable -Name bla:foo

${} notation is for all PSProviders and not only variable, if we use a variable prefix that contains ":", it can't determine which PSProvider you want to use. (see provider path in namespace variable notation inconsistency

Understood, but when New-Variable -Name 'bla:foo' -Value 1 works $bla:foo doesn't return it and is possible only via Get-Variable and namespace notation.

So, a variable name itself should not be able to have any : characters in it, really. These are used for scope modifiers, and while there are cases where it appears that a given variable might have that as part of its name, almost all usable cases result in that portion of the name being taken as a scope modifier or PSDrive accessor, as intended. What should not be possible is the creation of a variable in the variable: drive where the actual variable name contains a : character.
There isn't really a good reason to allow this, in my opinion, and it makes more sense to expressly forbid it due to the unavoidable issues it causes thanks to its use as a drive or scope qualifier.
Also, @kvprasoon $local:bla:foo 😄

We are all agree that allowing any : character in variable has no sense.
But exception of this issue, it works if you provide the full syntax.
If you want examples of inconsistency with : character, :
New-Variable -Name : -Value 1
New-Variable -Name :: -Value 2 => A variable with name '::' already exists.
Get-Variable -Name ::
${::}
Get-Variable -Name :

It works right up until you try to remove the variable again.
So.. sort of. 😄

I wrote "But exception of this issue", example "bla:foo" works !

Ah, I missed that, sorry! Good point to be aware of... I guess that makes sense. If it doesn't resolve a usable scope name it probably isn't as problematic for the provider / cmdlets to figure out.

The variable cmdlets certainly appear to have problems but namespace qualified operations work properly:
PS[1] (32) > $variable:global:myvar = 123
PS[1] (33) > $variable:global:myvar
123
PS[1] (34) > rm variable:global:global:myvar
PS[1] (35) > $variable:global:myvar
The variable '$variable:global:myvar' cannot be retrieved because it has not been set.
At line:1 char:1
+ $variable:global:myvar
+ ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (variable:global:myvar:String) [], RuntimeException
    + FullyQualifiedErrorId : VariableIsUndefined

So it seems that the issue can be addressed by fixing the variable cmdlets.

Sure, but does it even make sense to allow the drive/scope delimiter to be usable in a variable name given the additional confusion and disparity it causes in terms of how to define and how to retrieve values when it's used in this way?

FYI, access to such variable is possible via a scope, $local:global:myvar, no namespace syntax required.

Also, $:global:myvar works.  The first colon (in $ syntax) must always be used to describe a scope or drive, the first colon is never part of the variable name.  And two colons can only be used together if they are the first two in the $ syntax.  Additional : require ${} syntax

Talk about weird stuff.
new-variable -name global:myvar -value 1
$:global:myvar # there it is
remove-variable -name global:myvar # oops, error
$:global:myvar # still there
clear-variable -name global:myvar
$:global:myvar # still there
remove-variable -name global:myvar # no error
$:global:myvar # not gone yet!!!
clear-variable -name global:myvar -scope local
$:global:myvar # still there, but empty now
remove-variable -name global:myvar -scope local # no error
$:global:myvar # finally gone

... yep. Looking at that, I can only say that it makes no sense to allow variable names themselves to include a colon character. 😌

Are there any other characters that are not allowed in a variable's name?

You can't include { or } in a variable name without escaping them with a backtick, because they're part of the variable name-enclosing syntax:
PS> ${{a} = 1
At line:1 char:4
+ ${{a} = 1
+    ~
Use `{ instead of { in variable names.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : OpenBraceNeedsToBeBackTickedInVariableName

(Note: while } will work, it just ends the variable name if it's not escaped. Neither are usable in a non-enclosed variable name.)
I think treating : similarly makes sense; if you really want to use it as part of a name instead of a scope modifier, you can escape it with a backtick, and we can add handling on the backend to ensure it's handled correctly instead of being interpreted as a scope. It should error out if the : is not escaped and there's already a drive name or scope modifier in the name.

Lets not forget, that using the ${ } notation, ALL characters are valid, including control characters!  Also the same applies to the variable -name argument of the variable CMDLETs, all characters are valid (though wildcards may need to be escaped).  The only places there are restrictions are with the $ sigil.
Lets explain, to the best of my knowledge, what is going on in the tokenizer:

Meets a $, possibly variable or substatement
Valid second characters are $, ^, {, :, ? or \p{L} (all the letter characters in Unicode, which includes _)
$ and ^ end the variable name immediately
{ begins a expanded character set name, escaping is required for some characters, but any character is otherwise valid, the name ends with an un-escaped }
otherwise the name is any : (as long as the next character is also not :), ? or \p{L}, until a non allowed character is met.
If none of the above matches, then an alternate second character is (, which then tokenizes a substatement.
not a substatement, then the $ is included in any already ongoing token, and that ongoing token continues.

Only after the name is tokenized does drive and scope get decoded, using the first : regardless of the method used to tokenize.  A blank drive or scope is allowed, but the first : is then removed with the process, making it not part of the variable name.
So it this point it would complicate tokenizing to change the current behavior.  The : becomes an allowed character in the variable name because it must be accepted by the tokenizer in the basic name category in order to capture the drive or scope.
The variable CMDLETs need to be fixed.  They neither seem to actually allow a scope to be specified in the -name parameter (which I don't think they should), nor do they work if you do try to, which indicates they are broken, even though they work for all other variable names that include :, plus get-variable / set-variable work correctly.  Then the issue would only be a small issue of confusion by new users as to how to specify the scope part to the variable CMDLETs.   Do note that the variable CMDLET's accept all characters for variable names, since the variable name is an argument.
I do think its weird that in some places the variable: drive accepts scopes and in some places it doesn't.  In the variable namespace notation, it doesn't, but in certain CMDLETs it does, such as 'remove-item' and 'get-content'

We don't need to change tokenizing beyond maybe adding a case similar to what exists for { (e.g, ${a{b} = 2 throws a very intentional error prompting you to use a backtick to escape the brace). I think that may occur in the parser, I'm not sure, would have to look.
Beyond that, we should add checks to ensure the code paths are followed appropriately so we get no errors when we do intentionally try to make such variables. Not sure if that's actually a fault in the cmdlets or if it's more pertaining to the variable provider itself, since I believe similar difficulties arise using the provoder-agnostic *-Item cmdlets. Either way, yeah we need to fix that.

The tokenizer is here if you want to see how things actually work.
Remember that "variable syntax" is not just about variables. It applies to all providers and providers have different rules about which characters are valid in a variable path. This is why ${...} allows any character. The parser/tokenizer cannot determine that a path is valid, only the associated provider can.
And there are other special cases to consider like:
PS /tmp> $function:global:foo = { "Hi there" }
PS /tmp> foo
Hi there


Updates for SQLAlchemy 2.0

SQLAlchemy 2.0 has been released, and SimStore tests are failing now. There were warnings in 1.4 that help migrate to the 2.0 API. This implements those changes.
Still have a couple places where I want to manually check the SQL output to ensure that this is the same, but this PR will fix current errors.

This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Mon 30 Jan 21:00 GMT (15:00 my local).


Add icon to Discord Integration

It could be great to add an icon on this handler,
I know that there is no Discord icon in Font Awesome,
But it could be replaced by fa-microphone or fa-headphone until next version 🎤
This icon is used on front end / back end for login handler

A mic or headphone isn't really accurate either as discord is also a messenger.
The lock is fine for now, hopefully FA will add a discord icon soon. It's the most up-voted issue on their repo :)

For reading purpose: https://github.com/FortAwesome/Font-Awesome/issues/7574


Make adapter ready for Admin v3

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Done with v. 1.0.2


Add new method containing_block() to ChunkSize

containing_block() computes the smallest block of contiguous chunks containing an index.

I ended up not needing this, but it's still complete work which might be useful to someone, or to me in the future.


WIP: optimize: add autoscaling to linprog

Reference issue
Closes gh-10466
Partially addresses #9269
What does this implement/fix?
Adds an autoscaling routine to linprog to enable solution when the original problem is poorly scaled
Additional information

Unfortunately this still doesn't allow interior point to solve problems with huge bounds or RHS (#10288), but I think that's just a shortcoming of the algorithm
This improves the performance of linprog in many tests (see self-review)
I'm not sure that this should enabled by default, though. Results with autoscaling are quite mixed in the literature, so I don't want to make it the default option without a lot of testing/benchmarking (for a future PR)
That leaves a question: how should this option be set in the unit tests? Do all tests have to pass with autoscaling on and autoscaling off?
Currently all tests are set up to pass (on my machine) with autoscaling on to show that linprog autoscaling can pass all tests (with a few tweaks)

Todo

[ ] Cite sources
[ ] Add different autoscale options
[ ] Resolve questions above

By autoscaling, do we mean like balancing ala matrix_balance? matlab has balance and for sparse I think it uses spbalance

@ilayn interesting, didn't know about that. Yes, but more general:

A can (and generally will be) nonsquare
the pre- and post- multiplication matrices don't have to be related like T and T^-1
One thing I should probably do is round to a power of two like matrix_balance.

Using this branch to help confirm that patch gh-10498 is appropriate. See discussion there for details about why.
Note that 1047bbb caused test_bug_10124 to fail on most platforms.
Now I will test a patch.

Remaining failure after fee5b4630955f6f450b733d3270c8320d5b1f5a3 is unrelated to test_bug_10124; fee5b4630955f6f450b733d3270c8320d5b1f5a3 addresses the failure of test_bug_10124. I will apply this patch in gh-10498 so it can be part of 1.3.1.

@Kai-Striega thanks for comments - one thing if you have time: "how should this [autoscale] option be set in the unit tests? Do all tests have to pass with autoscaling on and autoscaling off?" This doesn't seem necessary to me. I think the default should be to have it off, all tests should pass with autoscale off, and I can have just one or a few tests run with autoscale on. Sound OK?

how should this [autoscale] option be set in the unit tests?

I think this should be set to whatever the default is in linprog. Although this could cause issues later on if we have an issue that's not discovered.

Do all tests have to pass with autoscaling on and autoscaling off?

Ideally yes, in practice I don't think that's feasible. The linprog module already runs a [overly] comprehensive test suite. To double the number of tests is going to become an issue.

This doesn't seem necessary to me.

Maybe we could do this [autoscale,presolve,etc. on/off] when running tests with full? The test suite already covers scenarios multiple times.
It may be worthwhile identifying a minimal subset of test such that each scenario is covered (e.g. infeasibilities, cycling, unbounded etc) + existing bugs then run all permutations of options. But that will take more time to complete than I have available right now and should probably be a separate issue.

and I can have just one or a few tests run with autoscale on. Sound OK?

This is probably the best middle ground - run the tests with autoscaling for a subset of problems - then the existing tests with the regular problems.

@mdhaber just checking if you are waiting for me to do a thorough review?

@kai-striega nope things got busy with the 1.0 paper and CZI grant. Those are done, but I still might not finish these for a while. Thanks for checking!

@Kai-Striega OK getting back to this. Responded to your comments. Next I'll work on the test suite, reverting most test changes but separately adding a few tests just for 'autoscale'=True.

@Kai-Striega Do you have time for a more thorough review? I cleaned up the code according to your suggestions, so I think the main thing I'd ask you to do is to look at changes to the tests I had to make to get them to pass. My observations:

This PR addresses #10466, at least for most solvers. Apparently UMFPACK still has trouble after the scaling.
Autoscale improves linprog behavior in several tests. For instance:

test_cyclic_bland doesn't cycle, even without bland's rule on
simplex now solves test_bug_8174, , test_bug_8174_low_tol, test_bug_5400, test_bug_7237_low_tol, test_bug_6139_low_tol (without presolve)

There are few cases where tolerances had to be modified for tests to pass. One test is still failing on one platform; but I didn't see any point in fixing it now since we plan for the default to be 'autoscale':False. Based on the literature, we should not expect an autoscale routine to improve performance on all problems, so I don't see these as issues.

So if you approve, I plan to:

Revert all changes to test_linprog.py
Revert to the default 'autoscale':False
Add a test class with 'autoscale':True' and add a few targeted tests: obviously test_bug_10466with all solvers, but alsotest_nontrivial_problem_with_bad_guessandtest_nontrivial_problem_with_guessforrevised simplexto make sure guess autoscaling is working. Let's also dotest_bug_6139, test_bug_6690,  and test_bug_7237` with all solvers because they are (apparently) real-world problems with the full variety of constraint types.

Sound good?

I think we should be careful about changing the tolerances too much or to make the tests pass. It's really not an issue yet, but I've started noticing many of our "fixes" involve fiddling around with tolerances.

RIght, but we won't have to if we revert all these test changes, leave autoscale off by default, and only add back a few test cases with autoscale on.
Yes, many bug fixes have been tweaking tolerances. Part of that is because finding default values of default tolerances is trial and error, and we believe that tweaking the default is the right thing to do. But yes, sometimes other fixes would be better. I think autoscaling the problem is a step in the right direction, and adding relative tolerance checks at the end of linprog (as added #9671) would help, too.

Waiting to resolve @ilayn's suggestion, but when this is ready I think squash-merge is appropriate.

Just left a comment about an immediate fix. After that I'll try to make another round. These weeks were absolute hell at work so I'm really lagging behind.

@ilayn I noticed #10741, and when it is merged I can look at replacing my equilibration routine with it. In the meantime, shall we merge this one?

Yes please.

Ok. Then @kai-striega never mind the minimum safe value stuff as that will be taken care of when the routines from #10741 is used. Thanks!

Ok no problem. @iilhan having a PR to reference is also good :)
On Sat., 31 Aug. 2019, 04:06 Matt Haberland<EMAIL_ADDRESS>wrote:

Ok. Then @Kai-Striega https://github.com/Kai-Striega never mind the
minimum safe value stuff as that will be taken care of when the routines
from #10741 https://github.com/scipy/scipy/pull/10741 is used. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/pull/10495?email_source=notifications&email_token=AHFOJNJAK5WSUG2XBQGADM3QHF4UVA5CNFSM4IFNSZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SUUQA#issuecomment-526731840,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHFOJNK2IS473SOXSXPAXN3QHF4UVANCNFSM4IFNSZ2Q
.

@ilayn @Kai-Striega it sounds like you both think it's ready for merge, and so do I. Best to squash, I think.

Great! In it goes then, thanks @mdhaber @Kai-Striega


Use readonly to make stores readonly

Copied readonly helper from svelte until the svelte version in peerDependencies is >= 3.56.0

Thank you, I've been thinking about this! Do you think it can be problematic to update the peer dependency version? A lot of people still below this version?

Yea, I think 3.56.0 might be too new.
There are probably many people who use a lower version.
But there should be no breaking changes, so it might be okay to force them to update svelte. I don't know :smile:

The helper will take care of things anyway, so I'll include this in the next update! Thanks :)

Implemented in v2.


Multiple subscriptions

If you have more subscriptions resource list is messy because you are unable to distinguish what service run under which account.
Something like (Subscription) might help...
More on attached image

Issue is still there and there is no way by which one can distinguish which service is under which account .

You can filter the subscriptions in the Manage Subscriptions window and the Explorer will update based on your selection

based on Beatrice's comment, resolving as by design.


default settings discrepency

this article states that the default value for "User Account Control: Behavior of the elevation prompt for standard users" in Group policy would be "Prompt for Credentials", however the following article states otherwise:
https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-standard-users
this reflects a default value of: Prompt for credentials on the secure desktop
please clarify?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 38066882-5022-1f08-3565-c13041b10921
Version Independent ID: 30a904f6-64ce-2d03-f9b1-721f75b8a106
Content: User Account Control Group Policy and registry key settings (Windows)
Content Source: windows/security/identity-protection/user-account-control/user-account-control-group-policy-and-registry-key-settings.md
Product: windows-client
Technology: itpro-security
GitHub Login: @paolomatarazzo
Microsoft Alias: paoloma

Hello @vinpathak84 and thank you for the feedback! Both articles are correct. The first article you are referring to explains the default GPO value, while the second article describes the default OS value. I will reword the second article to make it more clear.

@vinpathak84 I double checked, and you are correct. Thank you for the feedback. I will update the article accordingly.


Make it clear for java classes recursive comparison

Check List:

[x] Unit tests : YES
[x] Javadoc with a code example (on API only) : NA
[x] PR meets the contributing guidelines

Types from java package are not comparable with recursive comparison.
To prevent developers from wasting time looking for the problem, this PR adds an explicit log.
To do so, an element is added in additionalInformation in differences when needed.
This PR does not change the behavior.
Logs before :
Top level actual and expected objects differ:
- actual value  : IntSummaryStatistics{count=0, sum=0, min=2147483647, average=0.000000, max=-2147483648} (IntSummaryStatistics@163e4e87)
- expected value: IntSummaryStatistics{count=0, sum=0, min=2147483647, average=0.000000, max=-2147483648} (IntSummaryStatistics@56de5251)

Logs after :
Top level actual and expected objects differ:
- actual value  : IntSummaryStatistics{count=0, sum=0, min=2147483647, average=0.000000, max=-2147483648} (IntSummaryStatistics@423e4cbb)
- expected value: IntSummaryStatistics{count=0, sum=0, min=2147483647, average=0.000000, max=-2147483648} (IntSummaryStatistics@6e16b8b5)
Comparison objects are of Java types and were then compared with equals method

Thanks @FlorianCousin, I will review your PR shortly !

The error I found in OS ubuntu-latest failed job is as follows.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.0:javadoc (default-cli) on project assertj-guava: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1
[ERROR] error: Error fetching URL: https://javadoc.io/doc/com.google.guava/guava/32.1.2-jre/ (java.io.IOException: Server returned HTTP response code: 521 for URL: https://javadoc.io/doc/com.google.guava/guava/32.1.2-jre/package-list)
[ERROR] error: Error fetching URL: https://javadoc.io/doc/org.assertj/assertj-core/3.25.0-SNAPSHOT/ (java.io.IOException: Server returned HTTP response code: 521 for URL: https://javadoc.io/doc/org.assertj/assertj-core/3.25.0-SNAPSHOT/package-list)

The URL https://javadoc.io/doc/com.google.guava/guava/32.1.2-jre/ is indeed not accessible.
I guess the problem is not caused by my PR but then I don't know how to fix it.
Do you have any idea ?
Could you please launch the workflows again now I rebased on main ?

javadoc.io should be back now so there shouldn't be failures anymore

@joel-costigliola @scordio
I updated my branch by rebasing onto assertj/main and there is no conflict anymore.
Would you please launch the workflows ?

2 tests have been fixed.
I think workflows can be launched again.
Sorry I had not checked the tests on my own machine before.

An error occured during 'Upload reports" :

Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

I guess it is independant of my code changes because it looks linked to the workflows itself.

it is @FlorianCousin

Integrated thanks @FlorianCousin !

Integrated thanks @FlorianCousin !

This is a great news, thank you.


Add the ability to conditionally wrap headers

When wrapping an email, it'd be nice to be able to tell reflow to not wrap
headers.  We assume users are not parsing emails, and so
wrap headers like any other text content, but if users would like, they can
pass a flag (--ignore-headers) on the command line and leave the headers
alone while wrapping.

:+1: great stuff ... and like the rename! ... also if you get tired of the record syntax functions NamedFieldPuns is a good option.

NamedFieldPuns looks super interesting. I didn't know that was a thing.

I love NamedFieldPuns. Here's an example of it in Croniker: https://github.com/gabebw/croniker/blob/6c84db2e6245b78c83061140d3eaa19fb4f868eb/Handler/TodaysProfilesTask.hs#L29


added links and quality of life changes

added links to all the programs that were missing them, choice of links are chosen in the following priority:

github repo
website for project
wikipedia entry
man page

also did some quality of life changes to names, eg.

blackfire.io -> blackfire, the binary is called blackfire
node.js tried to link to "node.js", workaround to make the name part link to nodejs.org as well

This is great, thank you so much!


Max retries exceeded with PiHole url

Dear Maintainer,
I use the docker-compose base setup.
The pihole-exporter is running with PiHole server on the same server.
version: "3.9"
services:
  pihole-influxdb:
    image: avojak/pihole-influxdb:latest
    container_name: pihole-influxdb
    restart: unless-stopped
    environment:
      - "PIHOLE_ALIAS=pihole"
      - "PIHOLE_ADDRESS=http://<IP_ADDRESS>:80"
      - "PIHOLE_TOKEN=***********************************"
      - "PIHOLE_NUM_TOP_ITEMS=25"
      - "PIHOLE_NUM_TOP_CLIENTS=25"
      - "INFLUXDB_ADDRESS=https://*********************"
      - "INFLUXDB_ORG=influxdata"
      - "INFLUXDB_TOKEN=***************************************"
      - "INFLUXDB_BUCKET=pihole"

There are the following errors In the log :
pihole-influxdb  | 20:00:23 [ERROR] [pihole] Error connecting to http://<IP_ADDRESS>:80: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /admin/api.php?summaryRaw&topItems=25&topClients=25&getForwardDestinations&getQueryTypes&auth=dd3ce459b1285a539966dc39                                                                  6bbbaa2d6ac2a002f7b3f36256d9fb3ce0e983e8 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7d969d798920>, 'Connectio                                                                  n to <IP_ADDRESS> timed out. (connect timeout=30.0)'))
pihole-influxdb  | 20:00:53 [ERROR] [pihole] Error connecting to http://<IP_ADDRESS>:80: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /admin/api.php?overTimeData10mins&auth=dd3ce459b1285a539966dc396bbbaa2d6ac2a002f7b3f36256d9fb3ce0e983e8 (Caused by Con                                                                  nectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7d969d47eba0>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=30.0)'))

I checked the connection from the same machine via cUrl.
$ curl -v http://<IP_ADDRESS>/admin/api.php?overTimeData10mins&auth=**************************************
[1] 757581
root@lcloud-bastion:~/pihole-exporter-to-influx2# *   Trying <IP_ADDRESS>:80...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 80 (#0)
> GET /admin/api.php?overTimeData10mins HTTP/1.1
> Host: <IP_ADDRESS>
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
< Set-Cookie: PHPSESSID=95fkskkn7i1mtqrcfa8ddjnf5v; path=/; HttpOnly; SameSite=Strict
< Content-type: application/json
< X-Pi-hole: The Pi-hole Web interface is working!
< X-Frame-Options: DENY
< X-XSS-Protection: 0
< X-Content-Type-Options: nosniff
< Content-Security-Policy: default-src 'self' 'unsafe-inline';
< X-Permitted-Cross-Domain-Policies: none
< Referrer-Policy: same-origin
< Accept-Ranges: bytes
< Content-Length: 2
< Date: Sun, 09 Jun 2024 20:36:49 GMT
< Server: lighttpd/1.4.63
<
* Connection #0 to host <IP_ADDRESS> left intact

The connection is working fine. Did you observe this kind of problem in the past or it would be a specific problem only for me?
Thank you so much for your help!
Regards,
Balazs

I checked with native python scrip based execution. It seems to be working fine without issue. So maybe there will be the problem with my docker configuration or setup.
(pihole-exporter) blenkey@lcloud-bastion:~/pihole-influxdb-monitor$ python3 pihole-influxdb.py     --pihole-alias "pihole"     --pihole-address "http://<IP_ADDRESS>"     --pihole-token "***********************"     --pihole-num-top-items 25     --pihole-num-top-clients 25     --influxdb-address "https://influxdb"     --influxdb-org "influx"     --influxdb-token "----------"     --influxdb-bucket "pihole"
21:29:15 [INFO] ================== Configuration ==================
21:29:15 [INFO] Pi-holes:            pihole http://<IP_ADDRESS> (Auth token provided)
21:29:15 [INFO] Poll interval:       60 seconds
21:29:15 [INFO] InfluxDB address:    https://influxdb
21:29:15 [INFO] InfluxDB org:        influxdata
21:29:15 [INFO] InfluxDB token:      ******
21:29:15 [INFO] InfluxDB bucket:     pihole
21:29:15 [INFO] InfluxDB verify SSL: True
21:29:15 [INFO] ===================================================
21:29:15 [INFO] Starting...
21:29:15 [INFO] [pihole] Queried successfully in 24ms
21:29:17 [INFO] [pihole] Wrote to InfluxDB successfully in 2418ms


Fix deadlock

Fix deadlock that arises when initial row set has >= 10 rows; if this happens, the mpsc::channel is fully filled and tx.send() blocks, but the receiver channel is not yet returned and read from => deadlock.
This PR moves the initial row set handling to the new Tokio task, so the channel can be returned already.

Sorry, this was meant to be a PR against a fork. You can delete this 🙂

Just out of curiosity, would it be better to fix this issue on our side?


update to v18 error: "name_prefix" cannot be less than 3 characters

Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the examples/* directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by running terraform init && terraform apply without any further changes.
If your request is for a new feature, please use the Feature request template.

[X] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version [Required]:

v18.19.0

Terraform version:

Terraform v1.1.7

Provider version(s):
provider registry.terraform.io/hashicorp/aws v4.8.0

provider registry.terraform.io/hashicorp/cloudinit v2.2.0
provider registry.terraform.io/hashicorp/kubernetes v2.9.0
provider registry.terraform.io/hashicorp/local v2.2.2
provider registry.terraform.io/hashicorp/tls v3.2.0
provider registry.terraform.io/terraform-aws-modules/http v2.4.1

Reproduction Code [Required]
terraform {
  required_providers {
    local = {
      source = "hashicorp/local"
    }
  }
}

variable "cluster_name" {
  description = "The name of the cluster"
  type        = string
  default = "april-tf2"
}

module "vpc" {
  source = "terraform-aws-modules/vpc/aws"

  name = var.cluster_name
  cidr = "<IP_ADDRESS>/23"
  secondary_cidr_blocks = ["<IP_ADDRESS>/16"]

  azs             = ["us-east-2a", "us-east-2b"]
  private_subnets = ["<IP_ADDRESS>/28","<IP_ADDRESS>/28", "<IP_ADDRESS>/16"]
  public_subnets = ["<IP_ADDRESS>/28","<IP_ADDRESS>/28"]

  enable_nat_gateway     = true
  single_nat_gateway     = true
  one_nat_gateway_per_az = false

  private_subnet_tags = {
    "kubernetes.io/cluster/${var.cluster_name}" = "owned"
  }
}

module "eks" {
  source          = "terraform-aws-modules/eks/aws"
  version = "~> 18.0"

  cluster_version = "1.21"
  cluster_name    = var.cluster_name
  vpc_id          = module.vpc.vpc_id
  subnet_ids         = module.vpc.private_subnets
  enable_irsa     = true

  # Only need one node to get Karpenter up and running
  self_managed_node_groups = [
    {
      instance_type = "t3a.medium"
      asg_max_size  = 1
    }
  ]

  tags = {
    "karpenter.sh/discovery" = var.cluster_name
  }
}

Steps to reproduce the behavior:

apply with eks module version <18.
change to eks module version ~> 18.
updated based on https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/UPGRADE-18.0.md
clear state, init, then plan

Expected behavior
The plan to successfully generate.

Actual behavior
The plan fails to generate.
│ Error: "name_prefix" cannot be less than 3 characters
│
│   with module.eks.module.self_managed_node_group["0"].aws_launch_template.this[0],
│   on .terraform/modules/eks/modules/self-managed-node-group/main.tf line 55, in resource "aws_launch_template" "this":
│   55:   name_prefix = var.launch_template_use_name_prefix ? "${local.launch_template_name_int}-" : null

Terminal Output Screenshot(s)

Additional context

relevant error
│ Error: **"name_prefix" cannot be less than 3 characters**
│
│   with module.eks.module.self_managed_node_group["0"].aws_launch_template.this[0],
│   on .terraform/modules/eks/modules/self-managed-node-group/main.tf line 55, in resource "aws_launch_template" "this":
│   55:   **name_prefix** = var.launch_template_use_name_prefix ? "${local.launch_template_name_int}-" : **null**

this seems contradictory to me, if var.launch_template_use_name_prefix is false, then null is used, and isn't that <3 chars?

this:
self_managed_node_groups = [
    {
      instance_type = "t3a.medium"
      asg_max_size  = 1
    }
  ]

should be changed to something like this:
self_managed_node_groups = {
    karpenter = {
      instance_type = "t3a.medium"
      asg_max_size  = 1
    }
  }

also, if you're looking to get started with Karpenter using the modules provided here https://github.com/clowdhaus/eks-reference-architecture/tree/main/karpenter
just FYI

thank you!


Push bouncer: Deduplicate device registrations

Fixes #24969
Implements the solution discussed in the issue description and  https://chat.zulip.org/#narrow/stream/48-mobile/topic/iOS.20duplicate.20notifications

I squashed that commit, since indeed it looked correct. However, I have a concern that I'll post in the chat.zulip.org thread.

Pushed with the tweaks mentioned above

Merged, thanks @mateuszmandera!

Posted a backport to https://github.com/zulip/zulip/pull/25586. We technically only need the one line in push_notifications.py, but seemed cleaner to just backport the whole PR.


Add elasticsearch-admin to readme

New tool for administration
https://github.com/stephanediondev/elasticsearch-admin

Supported Elasticsearch versions: 2.x, 5.x, 6.x, 7.x, 8.x (snapshot)
Connection to Elasticsearch: server-side (no CORS issue), private or public, local or remote, http or https, credentials or not
App users: register, login, logout, list, create, read, update, delete
App roles: list, create, read, update (permissions), delete
Cluster: basic metrics, audit, disk thresholds, allocation explain [5.0], settings [5.0] (list, update)
Nodes: list, stats, read, usage [6.0], plugins, reload secure settings [6.4]
Indices: list, stats, reindex, create, read, update (mappings), lifecycle [6.6] (explain, remove policy), delete, close / open, freeze / unfreeze [6.6], force merge [2.1], clear cache, flush, refresh, empty [5.0], search by query, export (CSV, TSV, ODS, XLSX, GEOJSON), import from file (ODS, XLSX), import from database (MySQL, PostgreSQL), aliases (list, create, delete)
Legacy index templates: list, create, read, update, delete, copy
Composable index templates [7.8]: list, create, read, update, delete, simulate, copy
Component templates [7.8]: list, create, read, update, delete, copy
Index lifecycle management policies [6.6]: list, status, start, stop, create, read, update, delete, copy
Shards: list, stats, cluster reroute (move, allocate replica, cancel allocation)
Repositories: list, create (fs, s3, gcs, azure), read, update, delete, cleanup, verify
Snapshot lifecycle management policies [7.4]: list, status, start, stop, create, read, update, delete, execute, history, stats, copy
Snapshots: list, stats, create, read, delete, failures, restore
Elasticsearch users (native realm): list, create, read, update, delete, enable, disable
Elasticsearch roles: list, create, read, update, delete, copy
Tasks [2.3]: list
Remote clusters [5.4]: list
Enrich policies [7.5]: list, stats, create, read, delete, execute, copy
Pipelines [5.0]: list, create, read, update, delete, copy
Cat APIs: list, export (CSV, TSV, ODS, XLSX)
Console
SQL access [6.3]: query, translate to DSL
Deprecations info [5.6]
License [5.0]: read, status / start trial / revert to basic [6.6], features
Index graveyard [5.0]: list
Dangling indices [7.9]: list, import, delete

@stephanediondev awesome, thank you! I am gonna definitely try it myself


[nrf52840] use nrf_security for hardware accelerated cryptography

Previously simple CC310 cryptographic accelerator library was used with the glue layer using MbedTLS _ALT function substitution mechanism. This solution wasn't well tested from a security point of view.
The new cryptographic library is built from the nrf_security project: https://github.com/NordicPlayground/nrfxlib/tree/master/nrf_security. It provides both CC310 libraries with MbedTLS API and special glue layers for situations where both hardware and software implementation is used (i.e for AES as the hardware supports only 128bit keys so software is used for 256bit keys).
The new library undergoes special security verification procedure. Also, the new library is a production-ready version which wasn't the case before.

@LuDuda @e-rk Please review.

Great work Kamil!
Can you please write a few words for community about the reason of this change, so someone can find reference later when this is merged.

@LuDuda You want it here or as a part of the commit message?

Either way is fine!

@LuDuda  I've done both :wink:

Rebased and ready for merge

There is one problem that is more related to the exported heap api.
On IAR, this line is unreachable because of the assert above.

@e-rk i faced this problem in the past. Please use OT_UNREACHABLE_CODE macro like here.

@e-rk i faced this problem in the past. Please use OT_UNREACHABLE_CODE macro like here.

Is this something we want to address in this PR?

@jwhui Yes, we will address it in this PR.

@jwhui Please don't merge this yet - we are waiting for nrf_security 0.9.1

Oops, I believe this PR was not ready for merge as Kamil stated above - @KaSroka?
@jwhui would it be possible to give us permission to set labels in PRs (e.g. work in progress)? Else I think we can try to change PR title to [DNM][.. in the future (DNM - do not merge).

@LuDuda, apologies for that. I rolled master back. Please submit this PR and #4302 again.


'MANUAL' MySQL reserved word added

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Fixes #6033
without adding manual to the MySQL reserved word list even if we set objectQuotingStrategy=LEGACY it led to an error. Adding this new reserved word (available from MySQL from v8.4) to the list of keywords fix this issue.

Things to be aware of

Things to worry about

Additional Context

@tati-qalified we did some code refactoring here, could you validate this one again?


wsk cli does not pass annotations for rules

@erezh16 commented on Sat Mar 16 2019

Environment details:

vagrant

Steps to reproduce the issue:

wsk trigger create testTrigger
wsk rule create testRule testTrigger /whisk.system/utils/echo -a testAnn '{"key":"value"}' -v

Provide the expected results and outputs:
Output request should contain the annotation testAnn
Provide the actual results and outputs:
Output request does not contain the annotation testAnn
Response also does not contain the annotation testAnn
Additional information you deem important:

Seems like a stable issue

@rabbah commented on Sun Mar 17 2019
This is a CLI bug - the request body does not post the annotations.

I verified that the REST API certainly accepts annotations for rules, so the problem is isolated to the CLI.
On a related note, the same problem exists in the javascript client library. I guess that's a separate ticket. I'll look it up.

Filed https://github.com/apache/incubator-openwhisk-client-js/issues/165


Kubernetes pod level

Kubernetes-node-level faults restructured
Signed-off-by: Smriti S<EMAIL_ADDRESS>

Preview environment: https://ci.pr.harness.io/pr-499


[New Feature]: Exit option or button

🎮 feature Request
#Exit button
-where player is exhausted and wants to exit there should be a exit button which stops the current game and displays the score
Point down the features
#Exit button
which can stop the current playing game and displays the score
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

i would like to work on this issue please assign this task to me

I would like to work on this issue please assign this task to me.

Can you please assign this task to me....?? I would like to work on it and very much experienced in doing this.

@VershaDubey @Deepthi-Ramineni Please raise any other issue, i'll assign you
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channals for all projects...
Thank you :)


OSX: Fix rpath

It should be absolute
@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Not working

The mod is not working for me
Thought it was because of Beautified Chat or Chat Heads at first, but even after disabling still doesn't work
Here is the latest.log if that helps:
latest.log

Thank you for your feedback! I noticed that your modloader is Forge, and as far as we know, Forge does not support sending chat animation, only opening chat animation. Unfortunately, my co-author@TexBlock and I don't know how to solve this bug🙁
https://github.com/Wulian233/Chat-Impressive-Animation?tab=readme-ov-file#-features
Can you see the animation of opening the chat, or is the white bar on the left (which the mod removed) visible to you?

Hi!
So the chat opening animation does play but the white line does still appear.

According to your description only part of the mod is working properly
In previous tests forge was able to remove white bars, and a full functional demonstration should look like this https://modrinth.com/mod/chat-impressive-animation/gallery

yeah that sadly was not the case for me


[BUG]: AzureRmWebAppDeployment@4 broken after update

Task name
AzureRmWebAppDeployment@4
Task version
4.223.0
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Microsoft Windows Server 2022
Task log
2023-05-25T11:20:39.6058763Z ##[section]Starting: Deploy to pronet-proseal-test
2023-05-25T11:20:39.6215264Z ==============================================================================
2023-05-25T11:20:39.6215422Z Task         : Azure App Service deploy
2023-05-25T11:20:39.6215509Z Description  : Deploy to Azure App Service a web, mobile, or API app using Docker, Java, .NET, .NET Core, Node.js, PHP, Python, or Ruby
2023-05-25T11:20:39.6215689Z Version      : 4.223.0
2023-05-25T11:20:39.6215763Z Author       : Microsoft Corporation
2023-05-25T11:20:39.6215863Z Help         : https://aka.ms/azureappservicetroubleshooting
2023-05-25T11:20:39.6215962Z ==============================================================================
2023-05-25T11:20:42.4388122Z Got service connection details for Azure App Service:'pronet-proseal-test'
2023-05-25T11:20:43.7843931Z Trying to update App Service Application settings. Data: null
2023-05-25T11:20:44.1540051Z App Service Application settings are already present.
2023-05-25T11:20:44.8167326Z ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined
2023-05-25T11:20:46.4497379Z Successfully added release annotation to the Application Insight : pronet-proseal-test
2023-05-25T11:20:51.4141159Z Successfully updated deployment History at https://pronet-proseal-test.scm.azurewebsites.net/api/deployments/202531685013646441
2023-05-25T11:20:51.4163759Z App Service Application URL: http://pronet-proseal-test.azurewebsites.net
2023-05-25T11:20:51.4338472Z ##[section]Finishing: Deploy to pronet-proseal-test

Relevant log output
##[error]TypeError: Cannot read property 'retrieveSecret' of undefined

Aditional info
Previous version of 4.221.103 was working, and since seeing the update to 4.223.0 I am hitting this error.

Same error here, reverting to 4.221.103 solved the problem.

We are having the same error. Also self hosted.

There is also a breakage in JSON transform, which is very similar to the past issue https://github.com/microsoft/azure-pipelines-tasks/issues/16821
Nothing gets replaced with the following warnings:

##[warning]Resource file haven't been set, can't find loc string for key: JSONvariableSubstitution

I can confirm everything was working with 4.221.103 and got broken with 4.223.0 today.
It's broken on all agents:

Our self-hosted Linux agents
MS Hosted ubuntu-latest
MS Hosted windows-latest

@StefH can you share how to revert to an older version of this task?

We have the same issue with version 4.223.0 , reverting to version  4.221.103 like below helped :
- task<EMAIL_ADDRESS>

Same issue here using V4 of Azure App Service Deploy. It works if we change the version of the task to V3.

Same, also created bug here: https://developercommunity.visualstudio.com/t/Azure-App-Service-deploy-failing/10375407

same here. hosted agents, classic Release.

There is also a breakage in JSON transform, which is very similar to the past issue #16821
Nothing gets replaced with the following warnings:

##[warning]Resource file haven't been set, can't find loc string for key: JSONvariableSubstitution

I can confirm everything was working with 4.221.103 and got broken with 4.223.0 today.
It's broken on all agents:

Our self-hosted Linux agents
MS Hosted ubuntu-latest
MS Hosted windows-latest

@StefH can you share how to revert to an older version of this task?
EDIT1: We are on the classic release definitions, not yaml, and as someone else mentioned, I can't see a way to use precise version there. Just 4.*.

We just changed to version 3 from that drop down, everything seems ok, but had to change some simple configs like slot changes

There's another open issue - seems they've reverted it for now:
https://github.com/microsoft/azure-pipelines-tasks/issues/18361

Yeah confirmed as working now in our pipeline.

Duplicating #18361 .  A fix is applied, you should receive it soon.


The view logs function works in some containers, some containers are not

Hi,
On Rancher UI, when click button View Logs, some containers show logs as normal, some containers show empty. I ensure this container has logs because I also used kubectl logs to verify. And if I restart this empty logs pod (by delete pod) , new pod will have a logs.

Pod have logs

Pod don't have logs

Environment information

Rancher version: v2.5.6
Installation by command: docker run -d --restart=unless-stopped   -p 80:80 -p 443:443   -v /opt/rancher:/var/lib/rancher   --privileged   rancher/rancher:latest

Cluster information

EKS: version 1.19

UP


Support Fedora DNF

Check for dnf before yum in install-rok8s-requirements to not get
warnings from yum about how you should be using dnf instead.
Signed-off-by: Bryan Hundven<EMAIL_ADDRESS>

Looks good to me, thanks!


Added functionality to overwrite private ip/hostname as public ip/hostname

hi @Graeme-Miller, just for info, what's the use-case here, why add this capability?

@geomacy a number of blueprints (e.g. Clocker) rely on the ability of nodes to communicate via the subnet IP.
This functionality is useful in a situation where a cloud you are deploying to gives you a private IP, but you cannot configure that cloud to allow nodes to talk to one another via that IP. In this case, you could use this functionality to ensure that only the public IPs are used.

makes sense thanks @Graeme-Miller

@Graeme-Miller would be useful to include the explanation as a comment. Also examples of concrete clouds where to expect this behaviour if supported by open source jclouds providers.

@neykov the issue I saw was with Azure, which is not currently packaged as part of Brooklyn.

@aledsage re "@andreaturli and @Graeme-Miller looked into this for a while, but didn't manage to get the VMs to be added to the same Azure subnet" that's not entirely true. Adding
templateOptions:
  virtualNetworkName: your-net
  subnetNames:
  - your-subnet

one can place VM in the specified subnet. Notice also that when in the sam subnet VMs can reach one another using private ip address without fiddling with Azure endpoint aka fw rules.

Thanks @Graeme-Miller - merging.

I think my comment was sensible although not addressed. I suppose there are some other compelling use cases - that I'm ignoring now - where this configkey will be useful.