[NEW FEATURE]BROADCASTING consumer's consume detail is empty

When use BROADCASTING mode, offset only store on the machine which consumer is running on. Admin must login every machine to find out what offset  it is . It will make hard for analyzing some problems.

This is because the broadcast mode offset store is managed locally. If there is a better solution, you can submit a pull request.

If we can update offset to broker under broadcast mode, the offset store in broker only used by admin cli?

When client restarts, it will use a different client ID. Offset may not be well managed.

When client restarts, it will use a different client ID. Offset may not be well managed.

how about use the client's ip to identify every client?

maybe you can have a try on other solution: using different cluster consumer ids under cluster model instead of broadcast...

so, under what situation, shoud we use broadcasting，it seems that broadcast model has certain flaws.


Cut 0.67 Docs

Description
Why
Cutting docs for 0.67 release. API updates included.
Microsoft Reviewers: Open in CodeFlow

Getting Started page should have been updated to create a new react-native app with 0.67, not 0.66. So there should be a version-0.67/getting-started.md.


Upgrade to PF version 5

Description
Upgrades version of Patternfly to version 5 releases.
Type of change

[x] Feature
[x] Build related changes

Known issues:

Commits list on application overview has disappearing rows.
Unit test failures

/retest

/retest

@abhinandan13jan I'm not seeing that padding

@abhinandan13jan I'm not seeing that padding

Ok, it went away after a few refreshes

@rottencandy Fixed mentioned issues. PTAL.

@rohitkrai03 I don't believe the Learning resources changes have anything to do with our changes.

/retest


Updating to Chromium 98.0.4758.102

https://chromereleases.googleblog.com/2022/02/stable-channel-update-for-desktop_14.html

@Ahrotahn sorry for being annoying


fix(actionbar): ensure Poppover padding is managed for content direction

Description
fixes #1042

uses logical CSS properties to ensure padding is applied in a content direction relative manner

How and where has this been tested?

How this was tested: Using steps in #1042
Browser(s) and OS(s) this was tested with: Chrome on macOS

Screenshots

To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[x] This pull request is ready to merge.

This looks like it's failing the visual regression internal to the CI. It's not clear in the output there if it's just my one pattern, as expected, or not. Is there anything I can/need to do about that being I expect there to be one pattern with failure(s) here?

Hi @Westbrook,
Could you please create the feature branch in this repo? Due to the limitation of github action, the VRT result could not be published from fork feature branch.

Btw that failed VRT scenario(it is an animation) is expected which means you PR passed the VRT.

@jianliao I'll get that copied over.
FYI for the VRT we do in Spectrum Web Components we use the following to prevent animations from interrupting our screenshots.
                              --spectrum-global-animation-duration-0: 0ms;
                              --spectrum-global-animation-duration-100: 0ms;
                              --spectrum-global-animation-duration-200: 0ms;
                              --spectrum-global-animation-duration-300: 0ms;
                              --spectrum-global-animation-duration-400: 0ms;
                              --spectrum-global-animation-duration-500: 0ms;
                              --spectrum-global-animation-duration-600: 0ms;
                              --spectrum-global-animation-duration-700: 0ms;
                              --spectrum-global-animation-duration-800: 0ms;
                              --spectrum-global-animation-duration-900: 0ms;
                              --spectrum-global-animation-duration-1000: 0ms;
                              --spectrum-global-animation-duration-2000: 0ms;
                              --spectrum-global-animation-duration-4000: 0ms;

Not sure if it would help here or not, but something to think about.

Interesting, I'll give it a try. Thanks.

closing in preference of #1049


finder_action_keys open should be

The actions  use  to open  so it is very odd that  by default the finder_action_keys open key is o and  not CR.
The default should be  for consistency  with how most users will use this.

Additionally, I  have  mapped to other things  in my vim as well so it  would be nice if  the  from lspsaga could override it temporarily for this popup window.

you can custom it. i think this is not problem right ..


Error occurs when afx install

WHY
When executing afx install, panic occurs with the following error message and the installation fails.
$ afx install
? OK to install these packages? zsh-users/zsh-completions, zsh-users/zsh-autosuggestions, zdharma-continuum/fast-syntax-highlighting, ... (5 packages) Yes
✔ b4b4r07/enhancd
panic: assignment to entry in nil maprs/zsh-autosuggestions, zdharma-continuum/fast-syntax-highl...

goroutine 83 [running]:
github.com/b4b4r07/afx/pkg/state.add(...)
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/pkg/state/state.go:122
github.com/b4b4r07/afx/pkg/state.(*State).Add(0xc00038c140?, {0x7f96d535bf98?, 0xc00013ecf0?})
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/pkg/state/state.go:287 +0x1b3
github.com/b4b4r07/afx/cmd.(*installCmd).run.func2()
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/cmd/install.go:120 +0x1c5
golang.org/x/sync/errgroup.(*Group).Go.func1()
        /home/jshin/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:57 +0x67
created by golang.org/x/sync/errgroup.(*Group).Go
        /home/jshin/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:54 +0x8d

Environment
OS : Ubuntu 20.04.4
Go : 1.18
afx version : v0.1.19
yaml file
github:
  - name: zsh-users/zsh-completions
    owner: zsh-users
    repo: zsh-completions
    plugin:
      sources:
        - zsh-completions.plugin.zsh
  - name: zsh-users/zsh-autosuggestions
    owner: zsh-users
    repo: zsh-autosuggestions
    plugin:
      sources:
        - zsh-completions.plugin.zsh
  - name: zdharma-continuum/fast-syntax-highlighting
    owner: zdharma-continuum
    repo: fast-syntax-highlighting
    plugin:
      sources:
        - fast-syntax-highlighting.plugin.zsh
  - name: b4b4r07/enhancd
    owner: b4b4r07
    repo: enhancd
    plugin:
      sources:
        - init.sh
      env:
        ENHANCD_DISABLE_HOME: 1
  - name: tmux-plugins/tpm
    owner: tmux-plugins
    repo: tpm
    command:
      link:
      - from: .
        to: $HOME/.tmux/plugins/tpm

Debug log is here.
$ AFX_LOG=debug afx install
2022/03/24 00:23:59 [INFO] afx version: unset
2022/03/24 00:23:59 [INFO] Go runtime version: go1.18
2022/03/24 00:23:59 [INFO] Build tag/SHA: unset/unset
2022/03/24 00:23:59 [INFO] CLI args: []string{"afx", "install"}
2022/03/24 00:23:59 [INFO] Reading config /home/jshin/.config/afx/github.yaml...
2022/03/24 00:23:59 [DEBUG] (goroutine): checking new updates...
2022/03/24 00:23:59 [INFO] Parsing config...
2022/03/24 00:23:59 [DEBUG] mkdir /home/jshin/.afx
2022/03/24 00:23:59 [DEBUG] mkdir /home/jshin/bin
2022/03/24 00:23:59 [ERROR] there're some states or packages which needs operations: cannot refresh state
2022/03/24 00:23:59 [INFO] state additions: (5) []string{"zdharma-continuum/fast-syntax-highlighting", "b4b4r07/enhancd", "tmux-plugins/tpm", "zsh-users/zsh-completions", "zsh-users/zsh-autosuggestions"}
2022/03/24 00:23:59 [INFO] state deletions: (0) []string(nil)
2022/03/24 00:23:59 [INFO] state changes: (0) []string(nil)
2022/03/24 00:23:59 [INFO] state unchanges: (0) []string{...skip...}
? OK to install these packages? zdharma-continuum/fast-syntax-highlighting, b4b4r07/enhancd, tmux-plugins/tpm, ... (5 packages) Yes
2022/03/24 00:24:00 [DEBUG] (install): start to run each pkg.Install()
2022/03/24 00:24:00 [DEBUG] zsh-users/zsh-completions: added to state
panic: assignment to entry in nil map

goroutine 16 [running]:
github.com/b4b4r07/afx/pkg/state.add(...)
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/pkg/state/state.go:122
github.com/b4b4r07/afx/pkg/state.(*State).Add(0xc000379cc0?, {0x7fe23ca088d8?, 0xc0000be900?})
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/pkg/state/state.go:287 +0x1b3
github.com/b4b4r07/afx/cmd.(*installCmd).run.func2()
        /home/jshin/go/pkg/mod/github.com/b4b4r07/afx@v0.1.19/cmd/install.go:120 +0x1c5
golang.org/x/sync/errgroup.(*Group).Go.func1()
        /home/jshin/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:57 +0x67
created by golang.org/x/sync/errgroup.(*Group).Go
        /home/jshin/go/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:54 +0x8d

Thank you for the report and sorry for inconvenience. It has been fixed now in latest version.


Dynamic stage count

I have a need to dynamically increase or decrease the processor and/or batcher stage count depending on throughput.
Or is there a suggested best practice?  A monitor process that restarts the pipeline based on current throughput?
Thanks! Broadway is rad :)

A monitor process that restarts the pipeline based on current throughput?

yeah, that would be the only way for now. Just keep in mind that restarting the whole thing might take some time depending on the number of stages, the size of the buffers and number of in-flight messages in the pipeline.

Got it ... should be easy enough!

Chase, can you please explain the need to increase the number of stages? In
theory, everything will be fine if you “overspec” your pipeline. The VM is
really good at managing idle processes and GenStage really good at handling
demand.
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

Thanks José!
Basically I'm just taking in events and storing them in BigQuery. We're doing some other stuff like schema management, type checking, etc but basically it's just a BigQuery pipeline.
Each user has sources. Each source has it's own Broadway pipeline. This is creating a lot of processes and some sources have significantly more throughput than others.  Like 2_000 per second vs 1 or zero mostly. To handle 2k per second I can't increase all pipelines or I would have process limit issues very soon.
And I think this is why we're running into the BEAM busy wait thing. Which isn't an issue per se, unless we want to autoscale on CPU. Ultimately we'll be autoscaling on run queue (I think) but that is a bit more work.
Anyways, the main reason I like this model is becuase one source can't interfere with another. If some odd payload or BigQuery response crashes a pipeline, only one part of one customer is affected and not all pipelines for all customers.
Now ultimately we still will have issues when there are say 200_000 sources in the system but I think we can pick 3 of N nodes for source processes to live on.  And by that time this will be a good problem to have!

May I ask why not a single pipeline? The number of machine resources is
limited, creating the extra topologies may not help besides by drastically
increasing the amount of IO (or by introducing an intermediate process that
will most likely slow things down).
Also, the busy wait should not impact this. Unless the machines are not
busy at all and you are using something like Kubernetes pods. But it can be
easily disabled.
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D

The main reason I like this model is because one source can't interfere with another. If some odd payload or BigQuery response crashes a pipeline, only one part of one customer is affected and not all pipelines for all customers.
Maybe at this point I'd be comfortable moving to one pipeline now that we're doing this reliably at a decent scale. Having independent pipelines has really helped edge cases not affect everyone.
Yeah we're moving to k8s pods. Turning that off altogether is probably a good idea.

Feel free to just close this if you want. Creating a monitor proc is easy enough, and dynamic counts would probably just confuse people.

Yeah, I will do that. We will keep paying attention to use cases and we can always revisit in the future.


Update New Project Request

Note
This is for the layout/style only. The single user and multi-user selector components will be in separate issues.
New mockup with updated grid and styles
Noted that select single user (data manager) and multiple users (data users) are subject to change, referencing ticket #3 and #4;
suggestion for adding a "Save" button in between cancel and submit buttons

https://www.figma.com/design/rgzEYTpnGl6l68moRSVwYg/Phase-1-UI-Details?node-id=10-425&t=hQYCP2oJiWZyyU8x-4
When submits without required fields: highlight text box in red with warning icon and message.

https://www.figma.com/design/rgzEYTpnGl6l68moRSVwYg/Phase-1-UI-Details?node-id=190-9287&t=cTawxYHIUmwNYrqN-4
Originally posted by @yiwenxx in https://github.com/pulibrary/aux/issues/2#issuecomment-2394479923

Single user select: https://github.com/pulibrary/tigerdata-app/issues/980

Multiple user, multiple roles select: https://github.com/pulibrary/tigerdata-app/issues/984


second_level_cache (redis)namespace does not work

I have defined a namespace for my second level cache for doctrine. However this namespace is not used. Looking into this it looks like doctrine sets its own namespace that Redis uses. Is this a bug or something that cannot be changed because of how doctrine does this? If its not possible to set the namespace for the second level cache i think it would be a good idea to make sure this configuration option fails.
My yml file looks like this:
doctrine:
    orm:
        second_level_cache:
            region_cache_driver:
                type: redis
            region_lifetime: 100

snc_redis:
    doctrine:
        second_level_cache:
            client: doctrine_cache
            entity_manager: default
            namespace: "slc_%release_version%"

Yep, should fail.


Got "RangeError: Maximum call stack size exceeded" for many to many relation

The setup is the following: I have models called web, space and spaceview. Spaces and spaceviews are many-to-many and a web entity has lists of spaces and spaceviews. I use the REST serializer with the include method so that I want to return my spaces and spaceviews whenever I fetch webs.
I have a following acceptance test:
  test('visiting /web', async function(assert) {
    let space = this.server.create('space', {
      id: 1
    });

    let spaceview = this.server.create('spaceview', {
      id: 1,
      spaceIds: [1]
    });

    let web = this.server.create('web', {
      id: 1,
      spaceIds: [1],
      spaceviewIds: [1]
    })

    this.server.get('/webs', (s, r) => {
      return web;
    });

    await visit('/web');

    assert.equal(currentURL(), '/web');
  });

when I run it I've got my error

At the same time if I use a set of fixtures to load the same setup it works fine (in normal dev i mean).
It's possible that I setup my tests incorrectly, if that's the case any help would be appreciated. Otherwise it looks like a bug to me.
Sorry, saw the boilerplate link too late, I've created a small example app myself, here it is https://github.com/stukalin/embermiragetestselfreferences
Use the http://localhost:4200/tests to see the issue and the http://localhost:4200/web to see the same setup in dev environment with fixtures.

@samselikoff may I attract your attention? It sits here for a while already...

You're using RestSerializer which expects there to be models. Looks like you haven't defined any. If you haven't I'd recommend giving the ORM and Models sections of the docs a read.

@samselikoff as a matter of fact I have defined models (see https://github.com/stukalin/embermiragetestselfreferences/tree/master/app/models) and this setup works in normal (non-test) env. Or am I missing anything?

Spent a few hours on this. Have tracked it down to this line https://github.com/miragejs/miragejs/blob/46fcd385ccc1495fb44b2aac92163a4eda2e0dab/lib/serializer.js#L403 At some point the included resources has no models, this causes the line a few down https://github.com/miragejs/miragejs/blob/46fcd385ccc1495fb44b2aac92163a4eda2e0dab/lib/serializer.js#L408 to create an empty array and that breaks it out of the loop.  When you run tests, it always has a model.  I have not yet found why the resource has no model (making it work). It seems to be it should always have a model and thus never work.
Will spend more time when I can but there is clearly some magic code that breaks it out.
Its not the didSerialize array, when it does work its checking against collection:space(1) and model:space(1) is in the array, actually a coupe times due to the collection/model difference.  One would think the didSerialize array would be the one kicking it out of the loop, but its not.

@cah-briangantzler @samselikoff
I also spent a bit more time on this and now I know the difference between these 2 setups.
When I use my fixtures I don't explicitly create circular references, i.e. I declare my entities like this
let space = {
  id: 1
};

let spaceview = {
  id: 1,
  spaceIds: [2]
};

let web = {
  id: 1,
  spaceIds: [1],
  spaceviewIds: [1],
}

and ember (or is it still mirage?) is smart enough to realise that the space and the spaceview and the web are referring each other and they are reachable from each other.
Now when I try to create the same setup in my test
    let space = this.server.create('space', {
      id: 1
    });

    let spaceview = this.server.create('spaceview', {
      id: 1,
      spaceIds: [1]
    });

    let web = this.server.create('web', {
      id: 1,
      spaceIds: [1],
      spaceviewIds: [1]
    })

the following happens: when I add an entity which has a reference in an already declared entity then this already declared entity receives the ID of the new entity, i.e. after adding e.g. a spaceview my space would emplicitly receive spaceviewIds: [1], same would happen with the web etc. The buildPayload apparently can't solve this and keeps adding the space and the spaceview in the queue until the stack overflows.
A possible workaround to this is not to create models via server.create but just return an object like this
    this.server.get('/webs', (s, r) => {
      return {
        web: {
          id: 1,
        },
        spaces: [{
          id: 1,
          web:1
        },{
          id: 2,
          web:1
        }],
        spaceviews: [{
          id: 1,
          spaces: [2],
          web:1
        },{
          id: 2,
          spaces: [1, 2],
          web:1
        }]
      }
    });

which is fine, but I'd prefer to use the server.create. Do my findings help to identify the problem and a possible workaround?

Do you possibly have a repo with this data I could then step through and possibly see the problem.
First guess this would be in mirageJS not ember-cli-mirage, so posting an issue there may also get you a response

@cah-briangantzler yep, was in the original post: https://github.com/stukalin/embermiragetestselfreferences. Do you think I should duplicate the issue in the miragejs repo? I agree it really seems like to be more relevant there.

I think you should, will be more likely to get Sams attention there


Problem with languageerrata.lua

I have installed new Version 1.4.1 and activate languageerrata.lua. Now same problem. Error in loading game. And "last stand" not function. Here the Warrior:

Lua Error:

languageerrata.lua Code:
-- This file is to allow you to correct misspellings from the translator.
-- This is not for the feint at heart.
-- GS-E uses the enUS dictionary as the master disctionary.  If a word is not
-- translated (comes up red) it means it is missing from the disctionary.  If
-- it is missing completely and not just misspelt you will need to add the reverse
-- for your language
-- To use this you need to uncomment the function below. and put the correction
-- pointing to a spellID.
-- -- This function converts an enUS spell name to an ID.
GSAvailableLanguages[GSTRStaticHash]["enUS"] = {
["Last Stand"] = 12975,
}
-- -- This function converts a lowercalse enUS spell name to an ID.
GSAvailableLanguages[GSTRStaticShadow]["enUS"] = {
["last stand"] = 12975,
}
-- -- This function adds a spell to your local language.
-- -- You can override GetLocale() and provide a specific language like "esMX"
GSAvailableLanguages[GSTRStaticKey]["deDE"] = {
[12975] = ["Letztes Gefecht"],
}
What is wrong?
Thx for help!

Which is line 27 of the errata?

Line 27:
[12975] = ["Letztes Gefecht"],

And you have a solution?

No I don't.  I cant create the problem.  If i put your code in my myMacros
file its fine.  All I can come up with is that the "'s copied into the file
are the wrong ones and look right
["Letztes Gefecht"],  what if you make it
['Letztes Gefecht'],
do you get the same problem?
On Thu, Oct 6, 2016 at 1:28 AM, tiegars<EMAIL_ADDRESS>wrote:

And you have a solution?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GnomeSequenced-Enhanced/issues/98#issuecomment-251700193,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjBFRuM9gYKeON8K6sOTyQx_na_QbGJks5qw7sogaJpZM4KLuqd
.

I have have change to ['Letztes Gefecht'], same problem :(

I can now reporduce the error. The error only appears when you make reload ui.

I've added Last Stand, Flame On and Eye for an Eye to the translator so this modification should not be needed.


Ask original authors

Hello @jarrodcolburn and @t-kozak! 👋
I notice that you'd created a Dart SDK feature for devcontainers but it wasn't on the https://containers.dev/features list. I figured you might be interested in this repo.

Hi @jcbhmr, thanks for reaching out.
Jarrod's repo contains a Flutter and Android feature. Since it's my first time playing with these features, I've used it as a starting point and converted it into Dart SDK.
That script of mine is mostly a copy of a script in the official Dart docker container image. Unfortunately, since the Dart team does not have an official pointer to what's "latest" version of the Dart SDK, the versions, URLs and package checksums are hardcoded in the script.
I could potentially improve the script to pull these from devcontainer.json, but in this form, this feature's configuration would always have to be manually updated to catch up with the release rollout of Dart SDK, which is kind of meh experience IMO.
Let me know your thoughts.

I think it might be possible to use something like this? https://github.com/devcontainers/features/blob/main/src/github-cli/install.sh#L80 find_version_from_git_tags or something to get the latest version from https://github.com/dart-lang/sdk/tags ?? maybe not idk.

i tried using apt to install it and didn't get very far 😅 #2

@t-kozak There's also @eitsupi's https://github.com/devcontainers-community/features/blob/8522fe1bf77b027373dbf10b332010599afc0633/src/dart/install.sh Dart feature that worked, but I don't know if it fits your (exemplifying the typical Dart user 😅 you're the Dart-expert here 🤣) use case.
https://github.com/devcontainers-community/features/blob/8522fe1bf77b027373dbf10b332010599afc0633/src/dart/install.sh

By eitsupi https://github.com/eitsupi Dev Container expert
#!/usr/bin/env bash

VERSION=${VERSION:-"latest"}
CHANNEL=${CHANNEL:-"stable"}

DART_SDK="/usr/lib/dart"

set -e
source _common.sh

if [ "$(id -u)" -ne 0 ]; then
    echo -e 'Script must be run as root. Use sudo, su, or add "USER root" to your Dockerfile before running this script.'
    exit 1
fi

architecture="$(dpkg --print-architecture)"
if [ "${architecture}" != "amd64" ] && [ "${architecture}" != "arm64" ]; then
    echo "(!) Architecture $architecture unsupported"
    exit 1
fi

# Clean up
rm -rf /var/lib/apt/lists/*

find_version_from_git_tags() {
    local variable_name=$1
    local requested_version=${!variable_name}
    if [ "${requested_version}" = "none" ]; then return; fi
    local repository=$2
    local prefix=${3:-"tags/v"}
    local separator=${4:-"."}
    local last_part_optional=${5:-""}
    if [ "$(echo "${requested_version}" | grep -o "." | wc -l)" != "2" ]; then
        local escaped_separator=${separator//./\\.}
        local last_part
        if [ -n "${last_part_optional}" ]; then
            last_part=".*${last_part_optional}"
        else
            last_part=""
        fi
        local regex="${prefix}\\K[0-9]+${escaped_separator}[0-9]+${escaped_separator}[0-9]+${last_part}$"
        local version_list
        check_git
        check_packages ca-certificates
        version_list="$(git ls-remote --tags "${repository}" | grep -oP "${regex}" | tr -d ' ' | tr "${separator}" "." | sort -rV)"
        if [ "${requested_version}" = "latest" ] || [ "${requested_version}" = "current" ] || [ "${requested_version}" = "lts" ]; then
            declare -g "${variable_name}"="$(echo "${version_list}" | head -n 1)"
        else
            set +e
            declare -g "${variable_name}"="$(echo "${version_list}" | grep -E -m 1 "^${requested_version//./\\.}([\\.\\s]|$)")"
            set -e
        fi
    fi
    if [ -z "${!variable_name}" ] || ! echo "${version_list}" | grep "^${!variable_name//./\\.}$" >/dev/null 2>&1; then
        echo -e "Invalid ${variable_name} value: ${requested_version}\nValid values:\n${version_list}" >&2
        exit 1
    fi
    echo "${variable_name}=${!variable_name}"
}

export DEBIAN_FRONTEND=noninteractive

check_packages curl ca-certificates unzip

case "$architecture" in
amd64)
    SDK_ARCH="x64"
    ;;
arm64)
    SDK_ARCH="arm64"
    ;;
esac

if [ "${CHANNEL}" = "main" ]; then
    URL="https://storage.googleapis.com/dart-archive/channels/be/raw/latest/sdk/dartsdk-linux-${SDK_ARCH}-release.zip"
else
    if [ "${CHANNEL}" = "stable" ]; then
        LAST_PART=""
    elif [ "${CHANNEL}" = "beta" ]; then
        LAST_PART="beta"
    elif [ "${CHANNEL}" = "dev" ]; then
        LAST_PART="dev"
    else
        echo "(!) Channel ${CHANNEL} unsupported"
        exit 1
    fi
    # Soft version matching
    find_version_from_git_tags VERSION "https://github.com/dart-lang/sdk" "tags/" "." "${LAST_PART}"

    URL="https://storage.googleapis.com/dart-archive/channels/${CHANNEL}/release/${VERSION}/sdk/dartsdk-linux-${SDK_ARCH}-release.zip"
fi

echo "Downloading Dart..."

mkdir "${DART_SDK}"

# Working directory
mkdir /tmp/dvcf-dart
pushd /tmp/dvcf-dart

curl -sL "${URL}" -o dart.zip
unzip -q dart.zip
mv dart-sdk/* "${DART_SDK}"/.

chmod 755 "${DART_SDK}" "${DART_SDK}/bin"

popd
rm -rf /tmp/dvcf-dart

# Clean up
rm -rf /var/lib/apt/lists/*

echo "Done!"

It downloads the Dart zip archive, but it doesn't do the magic checksum that the current feature does. idk if this is a requirement 🤷♀
https://github.com/devcontainers-community/features-dart-sdk/blob/4e19d6a3d15823543501c949b49faa25b2b7a2d9/install.sh#L34
anyways, just thought now that there's discussion on improvement, itd be good to bring the another Dart installation magician into the conversation.
Oh, and thanks for participating in this discussion about something you probably wrote once and forgot about 🤣

Ya know.... After looking at it again, I may have changed my mind. Maybe the dart-docker and zip is the right approach. It would support M1 macs.🤔

Yea, after looking at it some more. I like the way you were doing it best.
https://github.com/jarrodcolburn/features-dart-sdk/blob/patch-1/install.sh
Look at my PR. I try to rewrite file it so hashes aren't hardcoded and should work with any dart version.
I'm not on a computer that's setup to test this at the moment. Please git it a try.


Laravel v9.44+ Support

@bogdankharchenko ,
I appreciate the PR for this. However, I ended up updating the package to drop support for Laravel 4.1 - 8.x, so the Str class in this package isn't even needed anymore.
The new 3.0.0 tag for this support was released today. The old 2.1.0 tags will still work if you need Laravel <= 8x or PHP <= 8.0.
Thanks,
Patrick


Feature/async job

Codecov Report

Merging #444 into develop will decrease coverage by 0.33%.
The diff coverage is 94.44%.

@@             Coverage Diff             @@
##           develop     #444      +/-   ##
===========================================
- Coverage    68.71%   68.38%   -0.34%
===========================================
  Files          216      216
  Lines        11777    11788      +11
===========================================
- Hits          8093     8061      -32
- Misses        3684     3727      +43

Impacted Files
Coverage Δ

framework/data_source/curl/curl_data_source.cpp
82.47% <91.66%> (-3.60%)
:arrow_down:

framework/data_source/curl/curlShare.cpp
100.00% <100.00%> (ø)

mediaPlayer/player_msg_control.cpp
76.19% <0.00%> (-6.35%)
:arrow_down:

framework/demuxer/avFormatDemuxer.cpp
78.57% <0.00%> (-2.86%)
:arrow_down:

mediaPlayer/media_packet_queue.cpp
73.60% <0.00%> (-2.41%)
:arrow_down:

mediaPlayer/buffer_controller.cpp
50.00% <0.00%> (-1.70%)
:arrow_down:

framework/demuxer/play_list/HLSStream.cpp
66.75% <0.00%> (-1.55%)
:arrow_down:

mediaPlayer/player_notifier.cpp
82.88% <0.00%> (-0.54%)
:arrow_down:

mediaPlayer/MediaPlayer.cpp
70.85% <0.00%> (-0.42%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Process.new(-1).exists? returns true in Linux

While trying to initialize a variable that represents a pid to something I thought was safe (an Integer that could never be a valid pid), I ended up killing my VM by doing:
pid = -1 # Invalid pid
Process.new(pid).exists? # returns true
Process.new(pid).kill # kills all processes in my Linux VM

Then I found that kill -9 -1 also kills my Linux VM. Possibly related Stack Overflow thread.
Even if Process.new(-1).kill is intended behaviour, should Process.new(-1).exists? return true?

The initialize method of Process is defined as protected, but that's the default visibility status, so that new becomes public. It's probably a bug in the compiler. I will mark it as private. You shouldn't be able to instantiate a process by pid like that.

Just to provide more context on why this had the effect that it had - trying to kill PID -1 results in everything except the kill process itself and init being killed.


TWIF 60 and docs updates

I have to investigate why this has conflicts, it shouldn't and doesn't if the pr is built up via cherry-pick... odd, fixed up in https://github.com/infinyon/fluvio-website/pull/828


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2815 ms

Resolved: Bofrost.at performance has improved in dd22fab.


How to add a length() or other function to the where condition

Example :
Model.find().where('length(id)=4').sort('id desc').exec(function(err,objs){
});
other : sum(id)  max(id) ...
Is there such a use in the waterline,thank you.

Waterline currently doesn't support these in it's query language but you can use .query to run these as a native query on your adapter.


Support .NET Core "Preview" Tooling

As described in the Project Roadmap, Fixie 2.x should leverage .NET Core, and it should allow testing of projects that leverage .NET Core.  This Issue is meant to track the high-level to-do list and as a starting point for discussion of the implementation.
Note: This issue was originally intended to cover full .NET Core support. In late 2016, Microsoft introduced significant breaking changes to their .NET Core testing infrastructure while also introducing a VS2017 prerequisite. This issue has since changed in name and scope to represent only the work in support of the "Preview" tooling in place during the summer and fall of 2016. In other words, this issue covers the work involved in support of the project.json / xproj style of projects, before dotnet test was rewritten to work atop MSBuild.

[x] Revise internal messaging infrastructure to lessen dependencies on AppDomains.
[x] Console runner runs exactly one test assembly per run (to meet the dotnet test model).
[x] Revise XML reporting command line arguments and file save paths (to account for the dotnet test model).
[x] Port a representative library (Parsley) to .NET Core RC2 (using xUnit temporarily).
[x] Convert all projects to .NET Core RTM project files, while still targeting only the regular .NET Framework.
[x] Update Parsley to .NET Core RTM.
[x] Migrate the existing console runner to become the dotnet test runner's console mode implemetnation.
[x] Extend the dotnet test runner to support IDE mode.
[x] Refactor the existing legacy Visual Studio runner to defer to dotnet-test-fixie.exe in IDE mode.
[x] Publish a prerelease NuGet package of 2.x for initial round of feedback.
[x] Consolidate all remaining AppDomain dependencies to within the dotnet test runner.
[x] Cross-compile Fixie.dll
[x] Cross-compile Fixie.Execution.dll
[x] Cross-compile Fixie.TestDriven
[x] Cross-compile dotnet-test-fixie.exe
[x] Enable dotnet-test-fixie to be located by dotnet-test when not targeting the full .NET Framework.
[x] Cross-compile Fixie.Samples
[x] Cross-compile Fixie.Tests
[x] Fixie.Tests and Fixie.Samples pass for full framework as well as netcoreapp/netstandard.

Hi,
I'd like to help with both porting fixie to .NET Core.
Would you accept contributions?

@plioi
I am just getting into .Net Core, so forgive me my ignorance.

Drop the plain console runner in favor of dotnet test?
Drop the legacy Visual Studio runner in favor of dotnet test?

Can test still be executed interactively from VS after these moves?

Yes they would, the .NET Core test protocol has design-time capabilities that would allow fixie to integrate nicely with Visual Studio, both for listing and executing tests.

Ah, thanks good to know,
I really need to catch up on .Net Core :smile:

@mderriey I just converted the project files over to the new project.json formats in #146. It would still only work for the regular .NET Framework, and would not yet support "dotnet test".  As soon as I publish a prerelease NuGet package, sometime next week, I'd appreciate some help testing that I haven't broken everything in the process.

Anybody working on the Add a dotnet test runner item?

@dennisroche Yes, I'm claiming that one. Between NUnit's solution, xUnit's solution, and Fixie's existing older-style Visual Studio plugin, I should have enough to go on.

@plioi need help with anything else? :)

2.0.0-alpha-0001
2.0.0-alpha-0000 was a dumpster fire, so let's never speak of it again. Announcing 2.0.0-alpha-0001! This release has been published for early adopters to experiment with.
What it IS NOT: This release will not test cross-platform projects, such as projects that target netstandard.
What it IS: Integration with the new dotnet tooling, both at the command line and in the Visual Studio Test Explorer, for old csproj test projects, and for new xproj/project.json test projects which target the normal framework: net45 and up. Much progress has been made to support netstandard too, but it's just not there yet.
Known Issues:

Attempting to run this against a 32 bit test assembly will not work. If you use Test Explorer, be sure it is set to 64 bit mode.
When using Test Explorer against an xproj/project.json project, expect the Output \ Tests pane to include some misleading output in which it claims to skip a test assembly "because it is not a test assembly", along with more output demonstrating that they are in fact being executed. Visual Studio is mistakenly running BOTH a legacy csproj style runner, which accomplishes no work, as well as the dotnet test variety which does provide results.

Working Examples

Rook is an old csproj style project, which demonstrates that the 2.x series can still work for such projects. Instead of using the new dotnet tooling, the build script invokes dotnet-test-fixie.exe directly. View the source as of this commit: https://github.com/plioi/rook/tree/1254f718596dea83d2aee4579fa81f8872390444
Fixie.Runners.Sandbox is a sample project used in integration testing Fixie.  Here we see new style xproj/project.json projects, but note that at this point they still have to target the regular framework, net45. The build script uses the new dotnet tooling, and Test Explorer also works via the new dotnet tooling. View the source as of this commit: https://github.com/fixie/fixie.runners.sandbox/tree/9c08a95186d5fc76b538a224590adb56e5a308d3

Your Project.json
A typical test project's project.json will look like this:
{
  "testRunner": "fixie",
  "dependencies": {
    "Some.Project.In.Your.Solution": { "target": "project" },
    "Fixie": "2.0.0-alpha-0001",
    "Should": "1.1.20"
  },
  "frameworks": {
    "net45": {}
  }
}

Because Microsoft has introduced significant breaking changes to .NET Core testing infrastructure while also introducing a new VS2017 prerequisite, I have renamed this issue to reflect what it really is, and am closing it. The project.json / xproj tooling is to be replaced soon by Microsoft, and a separate issue will cover integration with that tooling once the dust settles.  2.0.0-alpha-0001 remains for those currently on the deprecated project.json / xproj tooling, but we can't sink more time and effort into improving that integration when it's disappearing anyway.

Is there a way to use fixie as part of netcoreapp1.1 project?


Updated to 1.21

When will you update to 1.21?

bro, 1.20.6 already works on 1.21 💀

tried to compile it myself after adding 1.21 in the list of compatible versions and ran into a number of issues with outdated gradle features -- not sure how to get this version in a usable state :')

Apologies for the inactivity, I will try to get a 1.21 release out in the next few days.
The latest fabric version of the mod appears compatible with 1.21. If you want to use it before I put out the fix you can open the jar file (using WinRAR or 7Zip), then open fabric.mod.json, go to depends->minecraft and add "1.21.x" to the versions list, save the file and update the archive when prompted.
As for the forge version, it appears to need recompiling for 1.21, I will try and get this out in the next few days.
As for 1.18.2 on modrinth, I want to look into porting the latest version of the mod to older versions at some point.

just wonderin, when's the update coming out?
(take ur time if u need :) )

Just released version 2.1 which supports 1.21 now.
Apologies for the long wait.


Extending the explanatory system to allow for both taxlog and le expl…

…anations types as requested by the user. Taxlog and LE highlighting are working. This also correct the parsing problem with and/or. Please update the server.

Please, complete the merge and update the server. le_output is fixed. The taxlog/1 wrapper for the explanation is a proposal to distinguish the original rendering of explanations from the new le/1 wrapped explanation.


Get unassigned IPs

SendGrid returns a list of all IP addresses on your account. It also returns a list of assigned IP addresses.
What it doesn't do is return a list of unassigned IPs.
Please create a method that will get the IPs available and return any that do not have a subuser assigned to them.
See GET /ips for more information

Can you please provide a sample account with which I can work on this.

Hello @gr8shivam,
You can get a free SendGrid account here.
With Best Regards,
Elmer

You want the method to be placed where?

@gr8shivam,
Please create a helper here.

Since there has been no activity on this issue since March 1, 2020, we are closing this issue. Please feel free to reopen or create a new issue if you still require assistance. Thank you!


lib/BridgeFactory: Make methods only accept valid class names

This moves the responsibility for getting a valid class name to the users of BridgeFactory, avoiding the repeated sanitation. Improper use can also be checked statically.
Picked from https://github.com/RSS-Bridge/rss-bridge/pull/2889

I liked that the previous sanitization/normalization was contained inside the factory. Was inclined to move the whitelisting logic into it too.
In your pr the create() method only does instantiation. The factory is gradually losing its purpose. In the future I still want to call $factory->create('InstagramBridge') even if it's under the RssBridge or RssBridge\Bridges namespace.
I am thinking in the future we want to do this:
    // This is a typical factory which executes some logic depending on the input
    public function create(string $name): BridgeInterface
    {
        $name = $this->normalize($name);
        switch ($name) {
            case GettrBridge::class:
                return new GettrBridge($this->httpClient, $this->logger, $this->cache);

            default: return new $name();
        }
    }

Currently all these are valid names:

Gettr
GETTR
GettrBridge
GEttrBRidge

It looks like from the code that GettrBridge.php was supported earlier but that doesn't work now (before the pr).
From the codebase I think only the shortform Gettr is used. Unsure of any existing feeds use the alternative names. We could break this and insist on the shortform name.

I liked that the previous sanitization/normalization was contained inside the factory.

My motivation is that there are principally three different ways one could create a bridge:

Using a user-provided (unsafe) name
Using a safe name coming from RSS-Bridge (e.g. obtained with BridgeFactory::getBridgeNames())
Using URL (currently handled by DetectAction).

The create() method currently handles the first two ways, even though they have little in common.
In this PR, I have decided to focus create() just on the second goal, moving the responsibility for the first one to actions.
My vision is basically that actions will be responsible for normalizing all human inputs and the library will only accept a single canonical representation. That will make the core library simpler, reducing the space for bugs.

Was inclined to move the whitelisting logic into it too.

I am not sure if this should be the responsibility of the core library. On one hand, whitelisting is a concern for the library consumers (e.g. RSS-Bridge app), which may want to implement it differently, including adding ACL; on the other, having it in core may make it harder to accidentally grant access.

In your pr the create() method only does instantiation. The factory is gradually losing its purpose.

The factory is still useful as an abstraction. We still need it for getting the list of bridges so I would leave the create for familiarity. It is also somewhat useful for dependency injection.

In the future I still want to call $factory->create('InstagramBridge') even if it's under the RssBridge or RssBridge\Bridges namespace.

With this change, you would call $factory->create(InstagramBridge::class), which, in my opinion, is much clearer. With the string, it is not clear what it means but class constant unambiguously signals that you are referring to an existing class.

Okay I like your arguments. I merge if there's no other objections.

You guys are way more knowledgeable on this, so I agree with your assessment dvikan


Alibaba support in OpenSDS

What this PR does / why we need it:
This adds support of Alibaba OSS as a storage backend in Gelato.
Design spec: https://github.com/Click2Cloud-Gamma/design-specs/blob/8370d867c1cbaae42b407acb874ccf7f2c0b7483/specs/daito/alibaba-provider.md
API Test report: https://drive.google.com/file/d/1O0QAixh7RQTebjh01fFwNKLSuukQxwu7/view?usp=sharing
TODO: Update dashboard code for Alibaba OSS Storage
Special notes for your reviewer:
Release note:

This will allow following operations with Alibaba as Object Storage Backend:
1. Create Backend
2. Delete Backend
3. Create OpenSDS Bucket
4. Delete OpenSDS Bucket
5. Upload Object
6. Download Object
7. Delete Object
8. Lifecycle related operations on OpenSDS Bucket including cross-cloud migration
9. Also, user will be able to migrate its bucket from any OpenSDS supported public cloud or local storage to Alibaba cloud and vice-versa.

Please attach the test cases performed. Migration..Lifecycle transition supported in-cloud or between-cloud ..

API Test report: https://drive.google.com/file/d/1O0QAixh7RQTebjh01fFwNKLSuukQxwu7/view?usp=sharing

What this PR does / why we need it:
This adds support of Alibaba OSS as a storage backend in Gelato.
Design spec: https://github.com/Click2Cloud-Gamma/design-specs/blob/8370d867c1cbaae42b407acb874ccf7f2c0b7483/specs/daito/alibaba-provider.md
API Test report: https://drive.google.com/file/d/1O0QAixh7RQTebjh01fFwNKLSuukQxwu7/view?usp=sharing
TODO: Update dashboard code for Alibaba OSS Storage
Special notes for your reviewer:
Release note:
This will allow following operations with Alibaba as Object Storage Backend:
1. Create Backend
2. Delete Backend
3. Create OpenSDS Bucket
4. Delete OpenSDS Bucket
5. Upload Object
6. Download Object
7. Delete Object
8. Lifecycle related operations on OpenSDS Bucket including cross-cloud migration
9. Also, user will be able to migrate its bucket from any OpenSDS supported public cloud or local storage to Alibaba cloud and vice-versa.

Did we open issues for the failed test-cases?

LGTM.
Please open Issues for the features which are not working.

LGTM.
Please open Issues for the features which are not working.

The object uploaded to SSE enabled bucket was not downloaded properly for some cloud vendors like AWS, IBM & Alibaba too but it works fine with Azure. For this I will raise a issue except this all functionality using APIs works fine.
Thanks

LGTM.
Please open Issues for the features which are not working.

https://github.com/sodafoundation/multi-cloud/issues/930

Hi @kumarashit & @himanshuvar  I have tested it with Keystone and V4 authentication, all functionalities are working properly as expected. Thanks


Add update check

https://api.nuget.org/v3/registration5-gz-semver2/stylecop.analyzers/index.json

this should be handled by the dotnet tool ecosystem


No stdout / stderr for CommandOutputParameter type

Version: 2019.12.06
IDE: vscode (Version: 1.41.0)
Benten is reporting a problem when stderr | stdout is used as a type on a CommandOutputParameter, but I believe (and CWLTool validate is saying) it's okay.

Minimum example:
cwlVersion: v1.0
class: CommandLineTool
baseCommand: "echo"
inputs:
  inp:
    type: File
    inputBinding:
        position: 0
outputs:
  std: stdout

@illusional Thanks for reporting this.
Did you first install Benten before Sept 2019? If that is possible, could you try one check - under ~/.config/sevenbridges/benten/ can you remove the schema-v1.0.json file? In the original schema these were not formally written up as acceptable types. I patched the schema that is distributed with Benten, but only on 13th Sept (https://github.com/rabix/benten/blob/84868af60a6a997bb49887efdabe77bb392d5135/benten/000.package.data/schema-v1.0.json#L237). If you installed it earlier the new schema will not overwrite the existing one. Deleting and restarting Benten will copy over the news schema.
If this is not the issue, I will look into it. Thanks!

That was it, thanks @kaushik-work!


Fix typo in MathJax Help Modal

I just stumbled on this typo and thought that as it is so simple to fix I should submit it in a pull request. The change is:
-...you can scall all the math...
+...you can scale all the math...

Fixes #3140

Sorry - wrong repo! I will open this in the MathJax-src repository.


error while loading shared libraries: libx265.so.165 on Centos

I've being trying to install and run the server on Centos but getting an error
target/release/fits_web_ql: error while loading shared libraries: libx265.so.165: cannot open shared object file: No such file or directory
The library is certainly there. I even copied it to target/release but it didn't help. Any thoughts?

Resolved.

Glad it has been resolved. If you are planning on running it on a server but accessing it from another computer (i.e. your laptop), there is a special option to make fits_web_ql listen on all network interfaces (not just the special localhost):
"an alternative network interface (only needed to make the local version run in a quasi-server mode)
cargo run --release -- --interface <IP_ADDRESS>"
Then on your laptop you can point the web browser to http://your.server.ip.address:8080 to browse FITS files residing on the remote server. The port number can be changed too as per the README.

I'm getting the page that displays ALMA/HSC/NRO45M, and doesn't allow me just browse. What could be the reason?

What is the full command you are using to run fits_web_ql (cargo run or cargo build)? Most likely your --features string contains a word "server". The "features" part should not contains any words "server". The "server" feature is reserved for use in the JVO environment. Normally the ALMA/HSC/NRO45M test page will be displayed if --features contains a server flag.
If you just run the vanilla "cargo run --release" and point your browser to http://localhost:8080 you should be seeing the correct file browser page. Then you can add extra options like --port, --interface or --home:
cargo run --release -- --port 8000 --interface <IP_ADDRESS> --home /a/path/to/your/FITS/files

Indeed, I was using --feature. Now it looks fine. Thanks.
BTW. On Centos, "cargo run" causes an attempt to rebuild everything. The check takes up to 2 mins delay in starting the server.
Instead, I'm run it directly
target/release/fits_web_ql --release -- --port 8080 --interface <IP_ADDRESS>
I just want to check that this doesn't have any unintended consequences?

It is perfectly OK to do a time consuming "cargo build --release" only once and then launch the server many times the way you do it (with optional parameters when needed). By the way, the port defaults to 8080 so unless you are planning to use a different port number, you do not need the port parameter.
With hindsight, regarding the --features section, in the future releases I will probably rename "server" to "jvo" and also remove the (now obsolete) "production" feature. This should make it less confusing for users from outside the JVO. Plus will also update the README file to make it clear that the "jvo" and other features are not meant for regular use. It is safe to use the "cdn" feature in order to reduce load on your fits_web_ql server. Then most of the boiler-plate static resources will be served from a nearby jsDelivr CDN server. You'd better test it with and without "cdn" to see which works better.

By the way, the correct way of launching it after "cargo build --release" is:
target/release/fits_web_ql --port 8080 --interface <IP_ADDRESS>
There is no longer a need for adding "--release --".

For whatever reason I can't get --home to work. It still goes to my personal home directory.

There are a few things at play:

The FITSWebQL file viewer website remembers the last visited directory. Upon visiting http://localhost:8080 again it shows the last-visited directory, irrespective of the --home switch. Clicking on the "Home" link (the top-right part of the page) will bring you to the home directory (either specified by --home or the default $HOME).

Are you using the latest FITSWebQL version? The --home switch has been introduced only recently (5 days ago) in v4.1.5. If you have cloned from the master github repository, doing "git pull" from the fits_web_ql directory, and then "cargo update" from within the fits_web_ql directory will bring fits_web_ql and all the dependencies up to date. Or you can just download the latest release v4.1.5 and build from scratch.

Periodically doing "cargo update" does not harm, it will bring the related dependencies up to date.

Aha! This is the answer! I cloned 7 days ago.

A hint how to speed up FITSWebQL when using SSDs. It it best to clone fits_web_ql onto a directory residing on the fastest storage medium you have (ideally NVME SSD). Inside fits_web_ql there is an internal FITSCACHE directory where the program caches half-float-converted FITS files (applicable only to bitpix = -32).
The first time a FITS file is accessed it will be read from its original location (ideally from a fast NVME SSD). The second time somebody accesses that same FITS file, fits_web_ql will read the FITS header from the original location and then proceed to load half-float binary cache from the FITSCACHE directory.
So even if your large FITS files reside on a fast SSD, if fits_web_ql itself is located on a slow HDD second-time loads of FITS files will appear slow compared with first-time accesses.


[Feature Request] custom url

Hi @seleznev!
I just wanted to aks if you have time to update the firefox plugin with all the nice features the chrom plugin already has. At least the custom url would be nice for me.
Thank you. Daniel

Do separate issues for each feature you want and be specific about what that feature does.

Thank you, I am not yet familiar with the "usual way" here on github.


Links are badly displayed in inline chat streaming response

Verifying stable 0.18:
https://github.com/user-attachments/assets/0a426468-89d9-4fd6-9570-1544d2da4c1c

This happens for links that have a ) in their arguments


Accounts SDK login error: No Auth Service Configurations defined

Description:
I’ve been trying to integrate the Ticketmaster SDK using the provided demo from the following repository: https://github.com/ticketmaster/react-native-ticketmaster-ignite.
I passed the required apiKey and clientName into the IgniteProvider as shown below:
<IgniteProvider
  // analytics={igniteAnalytics}
  options={{
    apiKey: '*************',
    clientName: '*****maker',
    primaryColor: '#000000',
  }}
>

However, I keep encountering the following error:
LOG: Accounts SDK login error: No Auth Service Configurations have been defined.
I've also updated the demo constants as follows, but the error persists:
export default {
  DEMO_VENUE_ID: 'KovZ917ANwG',
  DEMO_ATTRACTION_ID: 'K8vZ9171ov0',
  DEMO_EVENT_ID: 'G5dIZb8kECzK3',
};

Expected Behavior:
The SDK should initialize properly and allow me to use the Ticket SDK modal as per my project requirements.
Actual Behavior:
The error persists, indicating that no auth service configurations have been defined, despite passing the required parameters.
Steps to Reproduce:

Clone the demo project from the GitHub repo.
Pass the API key and client name as required.
Attempt to run the project and observe the error.

Additional Context:
Any guidance on additional configurations or steps to resolve this would be greatly appreciated.
Thank you for your help!

For privacy/confidentiality reasons all issues should now be directed to<EMAIL_ADDRESS>


Fixes #117

Fixes #117

@RebeccaStevens Nice work as usual :-). Given the amount of good work you have done on this package I would be happy to add you as a collaborator (github+npm) so you can release your changes faster. Let me know if you're interested in that or if I should go ahead and release this PR.

Hey @jonaskello,
I'd love to be collaborator on the package. However I've never been a collaborator on someone else's package before so I'm a bit nervous that I'll do something wrong. I'd probably need you to walk me through everything at first to make sure I'm doing it right.
But anyway, yes this PR is ready to be released.

Great, I added you to this repo so you should have gotten an invite. Once you have that I think you should be able to merge this PR.
No problem with doing things wrong, there are always ways to fix it :-). I think you will be able to figure it out and if you have any questions just make an issue and ask. I'll outline some steps below to get you started.
So what I usually do after a PR is merged:

Update the changelog under the heading "unreleased" with a short description and links to issue and PR if releveant. For the changelog format I try to follow some simple rules from keep a changelog. It would actually be better if the changelog additions were part of each PR but I haven't gotten around to nagging contributors about that, but feel free to add changelog entries to this PR :-).

Then when I want to release a new version (which is usually right after merging a PR, but sometimes I collect several changes):

Figure out the new version number for the release. I try to follow semver as far as possible.
Create a new heading in the changelog with the new version number, taking care to update the comparision links at the bottom.
Move stuff from the "unreleased" section to the new heading with the new version number.
Commit and push the above.
Run the appropriate publish script which will automatically increment the version in package.json and publish to npm.
Done :-)

@RebeccaStevens  Btw, I also need your npm username in order to give you access to publishing. Is it the same as your github username?

@jonaskello I'll try not to let you down.
My npm username is: rebeccastevens
Just a quick question on future PRs I make, should I continue making them on my fork or should I just make a new branch on here for them?

Well, I don't have a preference for that. I guess making branches directly in this repo might be more convenient for you and that is totally OK with me.
I think I have managed to add you as github and npm collaborator now so you can go ahead and merge and release this if you want. Let me know if you need any help :-).


automatically start Homebridge with launchd

I created a plist file with the listed contents, dropped it in ~/Library/LaunchAgents, but I can't seem to get Homebridge to start up on boot. I tried running the load/unload command manually, it executes but Homebridge does not actually start. When I start Homebridge by typing Homebridge in a terminal window it runs no problem.
Any help would be greatly appreciated

just follow this wiki page https://github.com/nfarina/homebridge/wiki/Homebridge-autostart-at-boot-(init.d)-on-Ubuntu-(linux)

I have updated the Mac wiki page with instructions that actually work.
https://github.com/nfarina/homebridge/wiki/Install-Homebridge-on-macOS


Automated Package Upgrade

:tada: This PR is included in version 5.0.337 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issue-54: Support for RequestMethod PATCH

Support for RequestMethod PATCH

apologies for being very late getting to this pr.
there appears to have been a problem with the repo owners getting notified which we will work on.


problem with noun_phrases and case sensitivity

Is it possible to get a word in source case?
>>>text = '''Main Python wrapper for correcting spelling and grammar mistakes.'''
>>> blob = TextBlob(text)
>>> blob.sentences[0].noun_phrases[0]
'python'
>>> blob.sentences[0].noun_phrases[0].islower()
True
>>> blob.replace(blob.sentences[0].noun_phrases[0], 'Program')
TextBlob("Main Python wrapper for correcting spelling and grammar mistakes.")

@ksantr check line 438 of textblob/blob.py
return WordList([phrase.strip().lower()
it might be the standard thing to do


Tests for write_templatized_file

Resolves #5
Changes proposed in this pull request:

Adds config.py to store paths and content for hardening_manifest.yaml
Adds a file to the tests/data directory for comparison with a written test file
Adds assertions to the test function

@kcpevey Let me know if this is going where you planned.

Thank you! I've incorporated these changes into another PR. I thought it would be best to start a new one since I didn't intend for an additional level of configuration, but rather the conf.py to be filled out.


Python3.10 patching

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

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.

there is still a windows/python3.10 issue:
´%SRC_DIR%\sources\shiboken2\libshiboken\signature.cpp(949): error C2065: 'ssize_t': undeclared identifier`
@jschueller

@conda-forge-admin, please restart ci

@conda-forge-admin, please rerender

@conda-forge-admin, please restart ci

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

@conda-forge-admin, please rerender


Close #253: MQTT: Add support for disabling Retain flag

How it is controlled that remotely downloaded JSON configuration supports all configuration options user can enter here?

The remotely downloaded JSON configuration overrides configuration options from the current configuration.
If some option is not present in the remotely downloaded JSON, then this option retains its value on the gateway.
If the remotely downloaded JSON has some unsupported option, it will be ignored.


Workflow adds unwanted first line in csv

Current Behavior
First line in green is an unwanted row, being added by the workflow used for fetching this data

The workflow is - https://github.com/layer5io/docs/blob/master/.github/workflows/generate-keys.yml
Expected Behavior
the first row, should not be fetched,

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Layer5 site in Figma (open invite)
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Has this been taken care of @iArchitSharma?

Yes Lee, this issue is taken care of in this PR - https://github.com/layer5io/docs/pull/318
I'm closing this issue


test commit for testing bot

Checklist

[x] I have read the Contributing Guidelines
[x] I acknowledge that any submitted code will be licensed under the ISC License
[x] I confirm that submitted code is my own work
[x] I have tested the code, and confirm that it works

Enviroment

Operating System: N/A
Node version: N/A
NPM version: N/A

Description

test

JESUS STOP


WebSocket

This package has been great, waiting for someone to write the api for a project so this has helped me build the frontend without waiting around.
Anyway I want to use websockets to continuously get updated data real-time.
Can someone show me an example of doing this with json-server

Heads up, I'm not a maintainer or anything. Just what I would do.
You can add a WebSocket server to your
const jsonServer = require('json-server')
const app = jsonServer.create()
const http = require('http')
const server = http.createServer(app);
const router = jsonServer.router('db.json')
const WebSocket = require('ws')
const wss = new WebSocket.Server({ server });
let sockets = []
// .. etc basic jsonServer setup, for instance

app.use(jsonServer.rewriter({
  '/api/*': '/$1'
}))

app.use(router)

// websocket listener
wss.on('connection', (ws) => {
  sockets.push(ws)

  ws.on('message', function incoming(message) {
    console.log('received: %s', message);
    // route your websocket messages
  });

  ws.send('Hi there, I am a WebSocket server');
});

server.listen(port, () => {
  console.log(`Server started on port ${server.address().port} :)`);
});

As for sending updates to any connections you have open, in your routes just say something like:
db.get('posts')
  .push({ id: 1, title: 'lowdb is awesome'})
  .write()

sockets.forEach(function(socket) { socket.send({id: 1, title: 'lowdb is awesome'}) })

Checkout lowdb which the json-server is based on: https://github.com/typicode/lowdb

Any update on this? I am not able to establish web socket connection with my JSON Server.


Where is the Azure Retrieve part?

I want to retireve the secret in my pipeline yaml - nothing on this whatsoever despite the title - incredibly poor doc.

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

ID: 23617aaa-af93-2f09-5a7a-2a9a977dc5f2
Version Independent ID: 0d68d344-4b56-6f3b-ac02-08d43e2ac559
Content: Azure Quickstart - Set and retrieve a secret from Key Vault using Azure portal
Content Source: articles/key-vault/quick-create-portal.md
Service: key-vault
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@John-Blair Thanks for your feedback! We will investigate and update as appropriate.

@John-Blair You can refer to Azure Key Vault task in Azure DevOps Pipeline to retrieve the secrets.

Thanks... That info should be in the doc
On 11 Oct 2019 22:28, SaurabhSharma-MSFT<EMAIL_ADDRESS>wrote:
@John-Blairhttps://github.com/John-Blair You can refer to Azure Key Vault task in Azure DevOps Pipelinehttps://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-key-vault?view=azure-devops#yaml-snippet to retrieve the secrets.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/40595?email_source=notifications&email_token=AG3ZR4WAG3JEBYISLRZKSCDQODVZPA5CNFSM4I727SZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBIJWY#issuecomment-541230299, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG3ZR4TLGHFNHDWM7OSRL5LQODVZPANCNFSM4I727SZQ.

@John-Blair Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

Hey, the title is "Set and retrieve a secret", but as of now there is still nothing about how to retrieve, can you guys update it at your earliest convenience?

Document updated

#please-close


DLRS Access Issue for Non System Admins

When non system admins try to access the Manage Lookup Rollup Summaries tab they receive the below error "Salesforce Metadata API connection failure, click the link below to configure."
System admins do not receive this error. Users in question have both Lookup Rollup Summaries permission sets.
Any advice?

@afawcett any thoughts?


Update and rename SpaceLatte.css to toastminimal.css

w00t
toasty time

@newbold uhh can you close this please XD

merge*


How to specify options for Float type

I need to generate negative float type from -10.0 to -0.1 I can see there is an options thing
https://github.com/APIs-guru/graphql-faker/blob/master/src/fake.ts#L22
But not sure what type to use how to pass min and max.
By looking in to https://github.com/APIs-guru/graphql-faker/blob/master/src/fake_definition.graphql I tried to go with type: money  but it is eventually does not work returning always 0
neg: Float @fake(type: money, options: { minMoney: -10, maxMoney: -0.1 })
If I go just like neg: Float @fake(options: { min: -5, max: -0.1 }) that does not work as type is requited.
Any thoughts?

@kuncevic I just published 1.8.0 📦 with support for:
neg: Float @fake(type: number, options: { minNumber: -10, maxNumber: -0.1, precisionNumber: 0.01})

You are awesome!


.Net Core 2 Support

It would be nice to support .net core 2 projects

@Caldas Thank you for raising the issue. I agree that library needs .NET Core support, probably .NET Standard 1.3 (or even 1.1) will be a good target. Will you be able to find time for that?

To support .net core you would need to change the build pipeline as well. I can look into upgrading to Net Standard, but not the build and packaging. Would that be helpful to you?

Closed via #14. 0.7.0 version targets .NET Standard.


Caching support for get requests

Are there any implementation options for caching get requests?
I've seen a package from spatie, but I'm not sure if it fits me. My path is /employee/{employee}/items, but the party says that the cache works for every user, but I don't have users, but employees.

Caching is not covered by the Laravel JSON:API package, because caching is not something defined by the JSON:API spec. Using a Laravel package that specifically deals with caching would be the solution. I can't really advise which package to use or how a specific caching package works. Spatie are a good choice for packages as their packages are normally really good. If you have questions about their caching package, you'll need to ask them.


mbn

[Enter feedback here]
The quickstart for the personalizer quickstart at https://docs.microsoft.com/en-us/azure/cognitive-services/personalizer/quickstart-personalizer-sdk?pivots=programming-language-javascript does not work for the javascript version. When the code written in javascript is run locally there is a syntax error saying:
sample.js:127
    const rankResponse = await personalizerClient.rank(rankRequest);
                         ^^^^^

SyntaxError: await is only valid in async function
    at wrapSafe (internal/modules/cjs/loader.js:979:16)
    at Module._compile (internal/modules/cjs/loader.js:1027:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47

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

ID: a3976ea4-0c0e-e22e-11b6-05ab7de0e9d5
Version Independent ID: 0eee3a80-fb8d-70bb-4a51-791df9982519
Content: Quickstart: Create and use learning loop with SDK - Personalizer - Azure Cognitive Services
Content Source: articles/cognitive-services/personalizer/quickstart-personalizer-sdk.md
Service: cognitive-services
Sub-service: personalizer
GitHub Login: @edjez
Microsoft Alias: edjez

@simoncen Thanks for the feedback! We will review and update accordingly.


docs: Switch to Furo theme.

About
This pull request is about changing our theme on the documentation website to go from Karma to Furo, which addresses numerous concerns raised by the community:

Lack of theme picker (dark/light)
Inability to view source code
Search bar poorly functional with automodule usage
Current theme has colors uncomfortable to the eye
Inability to permalink to a method, class or attr
Cannot preview attr/arg types when hovering (hover refs)

Checklist

[x] I've ran pre-commit to format and lint the change(s) made.
[x] I've checked to make sure the change(s) work on 3.8.6 and higher.
[ ] This fixes/solves an Issue.

(If existent):

[ ] I've made this pull request for/as: (check all that apply)

[x] Documentation
[ ] Breaking change
[x] New feature/enhancement
[ ] Bugfix

closing this pr as i'm currently fighting rebasing hell every time i want to do it, and that's a no bueno for me.


Make IFeatureSettingsProvider and IFeatureSettings public

Trying to provide my own feature provider and get:
'IFeatureSettingsProvider' is inaccessible due to its protection level
Using version 1.0.0-preview-009000001-1251
Also please make IFeatureSettings public.

Can you look into this for next release. Thanks @dmcweeney.

@jimmyca15 is this in the latest release?

@zhenlan custom feature setting provider requires design review and has not added in the latest release. It would be a new set of APIs. It is still a target.
Also just realized I said "can you look into this" in my previous reply and I meant to just say "can look into this".

This has been added in recent release of Microsoft.FeatureManagement 2.2.0-preview.


Error with GLEW initialization

This is the output that I got:
Creating window glfw
ERROR: GLEW initalization error: Missing GL version
My setup:
Python3.5, Ubuntu 16.04, gym from openai official github.

Resolving. Please reopen if you still face issues.


Passed flake8

Normally use flake8 that is a Python syntax checker tool in Python projects.
It will suppress unwanted error messages if use flake8 on a parent project.

I’d rather add a files property to package.json that whitelists only the required files so that npm install utf8 doesn’t include the Python script anymore.

This is done in v2.1.1. Hopefully this resolves the issue for you.


com.alibaba.polardbx.server.ServerConnection#ServerConnection

重复代码
    instanceId = CobarServer.getInstance().getConfig().getSystem().getInstanceId();

    instanceId = CobarServer.getInstance().getConfig().getSystem().getInstanceId();

Thanks for your code review. This duplicated code will be optimized later. And it is recommend that you can take part in our development and summit a merge request to optimize the code here~


/collections/{folderid}

Hi!
Today I found an incorrect API behavior. For example:
GET https://www.deviantart.com/api/v1/oauth2/collections/DA1D523A-EAC0-972C-FB81-99D113195E94?username=ryky&offset=10&limit=10&mature_content=true
If I understand correctly, the server should return an array containing 10 elements. In fact, it returns only 9 elements with the next offset 20. Is it the bug?

This is expected sometimes we filter out deviations for various reason, clients should respect the offset hints even if there are less items in the response.


[Bug]: custom/script receiving multiple lines rapidly only displays first line

Checklist

[x] I have read the appropriate section in the contributing guidelines
[X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part
[X] I have searched for other open and closed issues that may have already reported this problem
[X] I have checked the known issues page for this problem.
[X] I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce
Just run polybar with the minimal config.
You might have to exit and rerun it a couple times to see the bug. On my main system the bug appears every time, but when I tried it on a virtual machine it sometimes correctly displayed 2, and sometimes incorrectly 1.
Minimal config
[bar/bar1]
modules-right = test

[module/test]
type = custom/script
tail = true
exec = echo -e "1\\n2" && sleep infinity

Polybar log
notice: Parsing config file: /home/user/.config/polybar/config.ini
- config_parser: Parsing /home/user/.config/polybar/config.ini
* Loaded monitor eDP-1 (1920x1080+0+0)
* Configured DPI = 96x96
* Bar geometry: 1920x24+0+0; Borders: 0,0,0,0
- bar: Attach X event sink
- bar: Attach signal receiver
- controller: Setup user-defined modules
notice: Loading module 'test' of type 'custom/script'
notice: Loaded 1 modules
* Starting application
- controller: Main thread id = 1
* Entering event loop (thread-id=1)
- bar: Create renderer
- renderer: Get TrueColor visual
* renderer: Using 32-bit TrueColor visual: 0x283
- renderer: Allocate colormap
- renderer: Allocate output window
- renderer: Allocate window pixmaps
- renderer: Allocate graphic contexts
- renderer: Allocate alignment blocks
- renderer: Allocate cairo components
- renderer: Load fonts
warn: No fonts specified, using fallback font "fixed"
notice: Loaded font "fixed" (name=Noto Sans, offset=0, file=/usr/share/fonts/noto/NotoSans-Regular.ttf)
* Bar window: 0x4a00001
- bar: Reconfigure window
- bar: Set window WM_NAME
- bar: Set window _NET_WM_WINDOW_TYPE
- bar: Set window _NET_WM_STATE
- bar: Set window _NET_WM_DESKTOP
- bar: Set window _NET_WM_PID
- bar: Map window
- background_manager: update_geometry
- background_manager: deactivating because there are no slices to observe
- bar: Draw empty bar
- bar: Setup tray manager
* Starting module/test
* script_runner: Invoking shell command: "echo -e "1\n2" && sleep infinity"
* module/test: Rebuilding cache
- bar: Force update
* Redrawing bar window
- bar: Received expose event
- background_manager: update_geometry
- background_manager: deactivating because there are no slices to observe
- background_manager: update_geometry
- background_manager: deactivating because there are no slices to observe
* module/test: Rebuilding cache
* Redrawing bar window
- renderer: flush(3 geom=9x24+1911+0, falloff=0)

Expected behavior
When receiving two lines at the same time or in rapid succession I expect the module to display the last received one. In this case it should display 2.
Actual behavior
The module only displays the first received line. In this case 1.
Window Manager and Version
i3 4.23-3
Linux Distribution
Arch
Polybar version
polybar 3.7.1

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g -ffile-prefix-map=/build/polybar/src=/usr/src/debug/polybar -flto=auto -O3 -DNDEBUG -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -flto=auto -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override  -Wall -Wextra -Wpedantic -Wdeprecated-copy-dtor -Wsuggest-override

Additional Context / Screenshots
The bug is present when building from source as well.
The bug comes from the following code in src/adapters/script_runner.cpp
  while (!m_stopping && cmd.is_running() && !io_util::poll(fd, POLLHUP, 0)) {
    if (io_util::poll_read(fd, 250)) {
      auto changed = set_output(cmd.readline());

      if (changed) {
        m_on_update(m_data);
      }
    }
  }

What I believe is happening is that io_util::poll_read(fd, 250) will poll the stdout file descriptor of the script. If there is data in the file descriptor cmd.readline() will read the first line and the second line will get automatically buffered by the underlying stream. When io_util::poll_read(fd, 250) runs again, the file descriptor will be empty since the data has already been read into the m_stdout_reader stream buffer. Therefore the second line never gets displayed.
One solution is to create a function in src/utils/command.cpp that will first check the stream buffer and then poll the file descriptor.
 bool command<output_policy::REDIRECTED>::wait_for_data(int timeout_ms) {
   return (m_stdout_reader && m_stdout_reader->rdbuf()->in_avail() > 0) ||
           io_util::poll_read(get_stdout(PIPE_READ), timeout_ms);
 }

Then call cmd.wait_for_data(250) instead of io_util::poll_read(fd, 250).
This partially resolves the bug. There still appears to be a small chance that the bug will occur. This is because sometimes polybar will rebuild the cache immediately after receiving the first line, and while doing so it will receive the second line.
Relevant code in include/modules/meta/base.inl:
    if (m_changed) {
      m_log.info("%s: Rebuilding cache", name());
      m_cache = CAST_MOD(Impl)->get_output();
      // Make sure builder is really empty
      m_builder->flush();
      if (!m_cache.empty()) {
        // Add a reset tag after the module
        m_builder->control(tags::controltag::R);
        m_cache += m_builder->flush();
      }
      m_changed = false;
    }

One possible solution is to move the m_changed = false; to the beginning of the if statement, so that it can get set back to true even when it's already building the cache. Or maybe a mutex lock could be used instead.

Thanks a lot for getting to the bottom of this. Your entire analysis is spot-on.
Totally agree that we need the wait_for_data function. As for m_changed, I would suggest replacing the if header with if (m_changed.exchange(false)) {. This way, we atomically set it to false and never lose an update to m_changed.
Do you want to open a PR with the fix? Ideally, branch off the 3.7.1 tag and target the hotfix/3.7.2 branch when opening the PR, so that we can get it into the next bugfix release.

Great! I will open a PR with the changes.


[DiceDB-206]: support KEEPTTL option for SET command

resolves: https://github.com/DiceDB/dice/issues/206
~Quick Notes:~
- Issue with keys that have an EX mentioned on master (see video to view the issue)
- Manual tests and end-to-end tests are also failing because of this reason
~https://github.com/user-attachments/assets/33b90960-382e-4f2a-9d67-f59dead4518f~

Thanks for this contribution, the key expiry issue will be fixed once #209 is merged. Will review this then.

@JyotinderSingh I wanted to mention something about the expiry implementation itself.
Within Redis, a cycle is being run that checks all keys associated with a TTL and removes them if they are expired.
Source Code: https://github.com/redis/redis/blob/a92921da135e38eedd89138e15fe9fd1ffdd9b48/src/expire.c#L98
Although the current implementation isn't wrong, since we have to be careful about the memory we're using, an approach inspired by this would seem like an ideal one to take.
Keen to hear your thoughts on this. If you'd like this to be implemented, could I take it up?

@kolharsam Can you rebase with the lastest changes in master branch? it would be easier for us to ensure correctness. Thanks again!

@kolharsam Can you rebase with the lastest changes in master branch? it would be easier for us to ensure correctness. Thanks again!

Hey @arpitbbhayani I've merged the latest from master branch. Thanks!

@kolharsam looks like there are some new conflicts, could you rebase again?

@JyotinderSingh I have updated the branch

@JyotinderSingh could you please review whenever you have some time?
Thanks!

@JyotinderSingh Thanks for your input. Will get to these soon. Had a busy weekend.

Closing this in favor of #318


Remove unused time var in material scripts

Signed-off-by: Ian Chen<EMAIL_ADDRESS>🦟 Bug fix
Summary
The time param declared in the ogre2 material scripts are no longer used in the shaders.
Here are the corresponding shaders. You can see that there are no uniforms called time:
gpu_ray_1st_pass_fs.glsl - time removed in #388
depth_camera_fs.glsl - time was probably never used.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-01-10/1228/1


Any plan for iOS?

Thanks for your job.
Is there any plan for iOS?

See #8

I don't think #8 in its current enough to help us understand what is going on.  I am very confused by the end of it all.  Is this working for iOS, yes, no, or somewhere in between?  According to the README, it doesn't, but you can install it...  very confusing.


Fetching group topic offsets does not work

I'm trying to use this lib to calculate the offset lag for a particular group ID. It seems able to fetch topic metadata though KafkaClient::fetch_offsets just fine, but when specifying a group with KafkaClient::fetch_group_topic_offsets, it returns an UnknownTopicOrPartition error in the resulting offset entry.
fn main() {
    ...
    let kafka_config = config.kafka_config;

    let mut client = KafkaClient::new(kafka_config.broker_list.clone());
    client.load_metadata(&kafka_config.topics).unwrap();

    let offsets = client.fetch_offsets(&kafka_config.topics, FetchOffset::Latest)
        .unwrap();
    println!("{:#?}", offsets);

    for topic in kafka_config.topics {
        let group_offsets = client.fetch_group_topic_offsets(&kafka_config.group, &topic)
            .unwrap();
        println!("{:#?}", group_offsets);
    }
}

this prints out
{
    "foo": [
        PartitionOffset {
            offset: Ok(
                299905
            ),
            partition: 3
        },
        PartitionOffset {
            offset: Ok(
                299905
            ),
            partition: 6
        },
    ...
}
[
    TopicPartitionOffset {
        offset: Err(
            Kafka(
                UnknownTopicOrPartition
            )
        ),
        topic: "foo",
        partition: 3
    },
    TopicPartitionOffset {
        offset: Err(
            Kafka(
                UnknownTopicOrPartition
            )
        ),
        topic: "foo",
        partition: 6
    },
    ...
]

These are active Kafka (v0.9) topics that are known to be working with the official Java library, and have committed offsets. It's also worth mentioning that when I create a Consumer and poll messages on the same group ID, it does not find a committed offset for the group, even though it does have one--it falls back to the offset specified by the fallback option.

it seems to me you're hitting a compatibility issue between different protocol versions. this library uses v0 while your java clients are probably using v1: The protocol says that v0 offsets are stored in zookeeper (so this is where kafka-rust will fetch the offsets from) while your java clients (using v1) are storing the offsets in kafka itself (__consumer_offsets topic.)
since v0 and v1 are identical on the wire, you could try merely replacing https://github.com/spicavigo/kafka-rust/blob/master/src/protocol/consumer.rs#L78 with the value 1.

Indeed, kafka-rust's implementation for fetching group offsets is not correct. It just happens to work with the zookeeper based strategy for offset persistence, but breaks when trying to communicate on the v1 protocol with a kafka 0.9 broker. I'll have a look at how to best fix this and try to provide a way such that client code can choose to prefer the v1 protocol.

Does this mean committing won't work either?

Well, committing offsets from within kafka-rust (and fetching them) right now works on the protocol version v0 which means the offsets will end up in zookeeper. A rust program using kafka-rust therefore will consistently store and load those offsets from the zookeeper instance (which is behind the kafka brokers) and things should be working as expected.
However, if your java clients are using v1 or v2 (which they obviously are) they will not use the zookeeper based storage (but will use kafka's owned storage, i.e. based on the __consumer_offset topic) and, hence, will not see offsets committed by kafka-rust. This is similar to the situation when using two java programs where one uses a new and the other an old version of KafkaConsumer for example; it will probably happen that the one program doesn't see the offsets of the other (even though using the same "groupId".) Once I fix this issue, we should have support for the v0, v1, and v2 offset fetching/committing protocol, and you should be able to successfully read offsets committed by a java client based on the 0.9 kafka client library.
However, the story around offset management got even a bit more complicated with kafka 0.9 with the group membership API (are your java clients using KafkaConsumer#subscribe?), which kafka-rust does not support at the moment. This is something we'll probably be addressing only as part of #92.
BTW: I already had a change to do some proof-of-concept work on this issue and learned that kafka 0.9 will sometimes not provide "old" offsets. It appears to keep offsets only for a defined period of time. If you had a consumer which was inactive for let's say 2 days, it might then tell you there's no committed offsets for that consumer (even though it did some commits; i'm still not 100% sure where the problem lies.) If you want to build a resilient lag monitor for a kafka 0.9 instance, it'd probably be better to directly read the __consumer_offsets topic, in the way projects like KafkaOffsetMonitor or kafka-manager do.

Ah, I see. Currently, we do not use the subscribe API, though we planned on switching to it at some point.
Reading from the __consumer_offsets topic might work, although I've noticed it's a binary format. Do you know if the format has documentation anywhere, and if it would be difficult to put together a parser?

i'm sorry, i haven't seen the format documented (but i haven't searched extensively). however, i'm sure you can find it in one of the two mentioned projects; i'm not much familiar with scala, but this seems to be the place where kafka-manager starts reading/processing the topic.

@dead10ck i just pushed my partial efforts to the branch pete/group-offsets; there's still some work left to do, but it'd be great if you could test the early result on your setup and give me some feedback if things don't work out for you.
you'd need to locally checkout the branch pete/group-offsets-v1 (which hard-codes the v1 protocol version for group offset management) and reference it from within your project using for example:
[dependencies.kafka]
path = "../kafka-rust"

@xitep awesome, thank you! However, I am currently on vacation, so I won't be able to test this until next week. I will definitely give it a go next week though!

just a minor update: i'm dropping the branch pete/group-offsets-v1 in favor of the newly available option to allow clients to choose the offset storage themselves in the branch pete/group-offsets like in the following example:
    use kafka::client::{KafkaClient, GroupOffsetStorage};
    ...
    let mut client = KafkaClient::new(vec!["localhost:9092"]);
    // ~ this is new and will switch the fetch/commit group offset to protocol v1
    // ~ the default is GroupOffsetStorage::Zookeeper for backwards compatibility
    client.set_group_offset_storage(GroupOffsetStorage::Kafka);
    try!(client.load_metadata_all());
    ...

Having that said, the public API should be set in this branch; but there's still some work left to do. Nevertheless, I'll be glad if you had a chance to try it out and provide some feedback.

@xitep that branch appears to be working perfectly :) it is now fetching offsets correctly from Kafka itself on my 0.9 broker

that sounds good :) thank you for testing! i still need to handle two more error cases which can occur and can/should be transparently handled by KafkaClient. i'll tackle this over the weekend and after some more testing i'll be merging and releasing it. feel free to shout in case you spot any troubles.

Available in master now; will be released as 0.4 later on crates.io; i'll then close the ticket if everything fine until then.

Published on crates.io.


ISPN-13312 NonRecursiveEventLoopGroup shutdown deadlock

https://issues.redhat.com/browse/ISPN-13312

BlockingTaskAwareExecutorServiceImpl should not retry tasks
after stopping
CacheNotifierImpl should not try to remove cluster listeners
from other nodes after stopping

Looks like a lot of Eviction related test failures now? https://ci.infinispan.org/job/Infinispan/job/PR-9547/1/#showFailuresLink


az account subscription list fails

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az account subscription list Extension Name: account. Version: 0.2.2.
Errors:
No module named 'azure.core.rest'
Traceback (most recent call last):
Temp\pip-unpacked-wheel-2lthyver\knack\cli.py, ln 215, in invoke
cli\core\commands\__init__.py, ln 654, in execute
cli\core\commands\__init__.py, ln 717, in _run_jobs_serially
cli\core\commands\__init__.py, ln 710, in _run_job
Local\Temp\pip-unpacked-wheel-o9e7nicr\six.py, ln 703, in reraise
cli\core\commands\__init__.py, ln 688, in _run_job
...
azext_account\vendored_sdks\subscription\_subscription_client.py, ln 12, in <module>
    from azure.core.rest import HttpRequest, HttpResponse
ModuleNotFoundError: No module named 'azure.core.rest'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az account subscription list

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer:

azure-cli 2.15.1 *

Extensions:
account 0.2.2
azure-devops 0.21.0
blueprint 0.3.1
costmanagement 0.1.1
image-copy-extension 0.2.8
resource-graph 1.1.0
storage-preview 0.7.1
subscription 0.1.4
virtual-wan 0.2.11

Additional Context

@jiasli for awareness

I cannot repro on the latest Azure CLI:
> az account subscription list
Command group 'account subscription' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus
[
  {
    "authorizationSource": "RoleBased",
    "displayName": "AzureSDKTest",
    "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590",
    "state": "Enabled",
    "subscriptionId": "0b1f6471-1bf0-4dda-aec3-cb9272f09590",
    "subscriptionPolicies": {
      "locationPlacementId": "Internal_2014-09-01",
      "quotaId": "Internal_2014-09-01",
      "spendingLimit": "Off"
    }
  }
]

Azure CLI 2.15.1 is a very old version. Please update to the latest and see if it works.

let me upgrade first and test


Gazelle: detect any directory with /test in path as test package

We have not very java-like structure in our monorepo:

So current func IsTestPackage doesn't detect our tests as tests and we have found MULTIPLE results in rule index error because of the same package in test classes.
We propose the fix, so files in packages like //common/test will also fit as test packages.

Thanks for the contribution!


Unable to import a module locally on Mac M1 or M2 but works on Windows 11

Environment

Operating System: Darwin
Node Version:     v20.11.1
Nuxt Version:     3.10.2
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
reproduction.zip
Describe the bug
I tried to reproduce a minimal version that works on Windows 11 but not on my mac mini m2 and not on my mac book m1 either.

Additional context
No response
Logs
No response

This is probably because you have not run npm run dev:prepare within the module directory on those other two computers.


Issues with postgres

I get an error when I'm deploying my project to my production server where I use prostgresql.
relation "cmsplugin_text" does not exist
LINE 1: ...."cmsplugin_ptr_id", "cmsplugin_text"."body" FROM "cmsplugin...
Is there some obious solution to this and what can I do to help?

Yeah I resolved this issue....the main thing was that i was using django 1.7 and by default it was trying to run south migrations so in order to resolve that i just added this to MIGRATION_MODULE under the settings.py:
'djangocms_text_ckeditor': 'djangocms_text_ckeditor.migrations_django',
This will explicitly tell the framework to run migrations instead of south migrations.
Since the main issue was djangocms_text_ckeditor's table was not getting created under the db


Added information on XML parsers

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: We do not allow copy/paste of content from another site.
Thank you and happy coding.


Footer markup mangled on t3

The pages are being served up on t3 with this markup for the footer element:
<footer clabeass="site__footer" role="contentinfo">
where the nonsense word 'clabeass' should be class

Resolved now on FreeCEN and FreeREG, still needs addressing on FreeBMD.

Ready for testing in test3


HyperDHT is not working with BunJS

I am trying to use amazing hyperdht with Bunjs but I am getting this error
bun: symbol lookup error: /home/zafaransari/projects/bun/pglite/node_modules/udx-native/prebuilds/linux-x64/udx-native.node: undefined symbol: uv_interface_addresses

How can I solve this issue?

It only runs on libuv


[New Feature]: Warn if ARP Data is similar between different packages

Description of the new feature/enhancement
The feature request comes as a consequence of https://github.com/microsoft/winget-pkgs/issues/95155 where users of an official package got upgraded to a third-party repackaged software that made unwanted changes to their current installation.
The reason was that both the official and the repackaged version shared the same PackageName, Publisher and even ProductCode (as it was an exe based installer where unique ProductCodes are not guaranteed). These fields are the primary ones for upgrade matching in case of an exe installer.
Proposed technical implementation details (optional)
Pipelines should compare the ARP fields between different PackageIdentifiers (fuzzy match for PackageName, exact match for ProductCode and Publisher) in addition to comparing the SHA-256 hash. Similar to an SHA-256 collision, a Possible-Duplicate label calling for manual review can be added upon detecting a duplicate with an existing PackageIdentifier.

@denelon https://github.com/microsoft/winget-pkgs/labels/Area-Validation-Pipeline label please


Дизайн css

Hi @KuzinHouse :wave:
I'm not sure if you opened this issue by accident and if so please close it, otherwise you need to provide details about your request.


external contacts resource

https://developers.zoom.us/docs/api/rest/reference/phone/methods/#tag/External-Contacts

ops https://registry.terraform.io/providers/folio-sec/zoom/latest/docs/resources/phone_external_contact


Don't highlight titles of read threads

I can't use the SDK at the moment, but I think this should do it:
in FirstPage.qml in the Label item with 'text: title' @ 284:
old:
                            color: highlighted || item.hasNews ? Theme.highlightColor
                                                               : Theme.primaryColor

new:
                            color: highlighted || item.hasNews
                                   ? Theme.highlightColor
                                   : (item.lastPostNumber < highest_post_number
                                      ? Theme.primaryColor
                                      : Theme.secondaryColor)

Works great, thanks!

Fixed in 0.9.3