Question: "Error: task completion callback called too many times"

Hi, I'm getting this error:
Error: task completion callback called too many times
var gulp = require('gulp');
var sass = require('gulp-sass');
var uglify = require('gulp-uglify');
var autoprefixer = require('gulp-autoprefixer');
var cleanCSS = require('gulp-clean-css');
var rename = require('gulp-rename');
var runSequence = require('run-sequence');
var pump = require('pump');

var pumpCb = function (err) {
    if (err) {
        console.log('Error: ', err.toString());
    }
};

// Local

gulp.task('local-sass', function (pumpCb) {
    pump([
            gulp.src('public/assets/src/sass/**/*.scss'),
            sass(),
            autoprefixer(),
            gulp.dest('public/assets/dist/css/')
        ],
        pumpCb
    );
});

gulp.task('local-js', function (pumpCb) {
    pump([
            gulp.src('public/assets/src/js/**/*.js'),
            gulp.dest('public/assets/dist/js/')
        ],
        pumpCb
    );
});

// Production

gulp.task('prod-sass', function (pumpCb) {
    return pump([
            gulp.src('public/assets/src/sass/**/*.scss'),
            sass({outputStyle:'compact'}),
            autoprefixer(),
            gulp.dest('public/assets/dist/css/')
        ],
        pumpCb
    );
});

gulp.task('prod-css', function (pumpCb) {
    return pump([
            gulp.src(['./public/assets/dist/css/**/*.css','!./public/assets/dist/css/**/*.min*']),
            cleanCSS(),
            rename({ suffix: '.min' }),
            gulp.dest('public/assets/dist/css/')
        ],
        pumpCb
    );
});

gulp.task('prod-js', function (pumpCb) {
    return pump([
            gulp.src('public/assets/src/js/**/*.js'),
            uglify(),
            rename({ suffix: '.min' }),
            gulp.dest('public/assets/dist/js')
        ],
        pumpCb
    );
});

// Calls

gulp.task('default', function () {
    gulp.watch('public/assets/src/sass/**/*.scss',['local-sass']);
    gulp.watch('public/assets/src/js/**/*.js',['local-js']);
});

gulp.task('prod', function () {
    runSequence('prod-sass','prod-css','prod-js');
});

Not sure what's going wrong?
Trying to search for answers didn't yield anything that helped.

Also opened a Stack Overflow question:
http://stackoverflow.com/questions/43397298/gulp-pump-run-sequence-task-completion-callback-called-too-many-times?noredirect=1#comment73856191_43397298

@ roberttolton I got that error in my gulp task too. It's because you have a return statement AND you're calling the task callback pumpCb. Remove the return statement.

@roberttolton I got that error in my gulp task too. It's because you have a return statement AND you're calling the task callback pumpCb. Remove the return statement.

@srilankanchurro Thanks! That seems to have done it.


Terminal weirdness on Windows remote

SSH from Mac to Windows remote
I am just collapsing and expanding the panel with cmd+J

Looks like behavior described in https://github.com/microsoft/vscode/issues/91135#issuecomment-589616853

So remote terminals are still stuck on winpty due to https://github.com/microsoft/vscode/issues/76548, so behavior is expected to be a little different. Additionally resizing terminals can often cause weird wrapping problems for Windows, but it looks like collapsing the panel is causing a resize to fire with small dimensions which isn't expected.
This might be different to #91135, that may be a race with the viewport not updating when resizes happen in quick succession?

While this bug may only be visible on Windows, the resize it likely also happening on Linux and mac which is redundant.

/duplicate https://github.com/microsoft/vscode/issues/91135


Config File Issues

This PR will aim to resolve #123 and #138.

Should we have a menu on running install that asks if the user wants to use their old config or utilize a new one?

After testing, #158 appears to no longer be an issue, but #158 also calls for the Logos config to use relative dirs to the installdir. It looks like the main config var that is impacted by that is the WINE_EXE var.
This is found in the following *app files:
https://github.com/FaithLife-Community/LogosLinuxInstaller/blob/fd807def24bb887823ff5a0c3b7315902484703a/gui_app.py#L435-L446
And it will be here in this PR:
https://github.com/FaithLife-Community/LogosLinuxInstaller/pull/158/commits/c613909d16d80b0cfdfbddfffec766285c9281d0#diff-be7d9ff1bf5cd29e78788cdbdfc6a0e25ae02d0340660e50f175d924f862aa67R520-R525
I think the simple way to make this work would be to check if the WINE_EXE var starts with the INSTALLDIR var, and if so, set it to something like:
WINE_EXE = os.path.join(INSTALLDIR, "data/bin/wine-devel_9.12-x86_64.AppImage")

My most recent testing shows that dynamic path generation is working and so this should now resolve #158 entirely.
But I noticed while working in the GUI that checking the logging status now fails and so does swapping it from enabled to disabled.

With this most recent push, I cannot replicate the enable/disable issue, which suggests I fixed some other outlying issues.
I've tested this on Manjaro in both TUI and GUI and all is working.
This is my new config file showing a relative path for WINE_EXE:
cat ~/.config/Logos_on_Linux/Logos_on_Linux.json
{
    "BACKUPDIR": null,
    "FLPRODUCT": "Logos",
    "FLPRODUCTi": "logos4",
    "INSTALLDIR": "/home/thwright/LogosBible10",
    "LAST_UPDATED": "2024-08-27T12:33:30",
    "LLI_LATEST_VERSION": "4.0.0-alpha.14",
    "LOGS": null,
    "RECOMMENDED_WINE64_APPIMAGE_URL": "https://github.com/FaithLife-Community/wine-appimages/releases/download/9.12-devel/wine-devel_9.12-x86_64.AppImage",
    "TARGETVERSION": "10",
    "TARGET_RELEASE_VERSION": "<IP_ADDRESS>0",
    "WINEBIN_CODE": "Recommended",
    "WINECMD_ENCODING": "437",
    "WINETRICKSBIN": "/usr/bin/winetricks",
    "WINE_EXE": "data/bin/wine-devel_9.12-x86_64.AppImage",
    "current_logos_version": "<IP_ADDRESS>0"
}

This is what I'm getting:

Now I see from the scattered exception text that it must be related to the winetricks variable ending up as "Download" somewhere along the way.
Here's the config file:
$ cat .config/Logos_on_Linux/Logos_on_Linux.json
{
    "BACKUPDIR": null,
    "FLPRODUCT": "Logos",
    "FLPRODUCTi": "logos4",
    "INSTALLDIR": "/home/nate/LogosBible10",
    "LAST_UPDATED": "2024-08-28T07:07:58",
    "LLI_LATEST_VERSION": "4.0.0-alpha.14",
    "LOGS": null,
    "RECOMMENDED_WINE64_APPIMAGE_URL": "https://github.com/FaithLife-Community/wine-appimages/releases/download/9.12-devel/wine-devel_9.12-x86_64.AppImage",
    "TARGETVERSION": "10",
    "TARGET_RELEASE_VERSION": "<IP_ADDRESS>9",
    "WINEBIN_CODE": "Recommended",
    "WINECMD_ENCODING": "850",
    "WINETRICKSBIN": "/home/nate/LogosBible10/data/bin/winetricks",
    "WINE_EXE": "/home/nate/LogosBible10/data/bin/wine-devel_9.12-x86_64.AppImage",
    "current_logos_version": null
}

So we use either the winetricks path or the word download in order to know what we need to do to get winetricks installed. What that would suggest is that somewhere the keyword "Download" isn't properly triggering a download but instead is being passed as the path. Hmm…

Also seeing this error:
2024-08-29 08:31:12 ERROR: Curses error in run_control_panel(): addwstr() returned ERR
Traceback (most recent call last):
  File "/home/thwright/Dev/LogosLinuxInstaller/./main.py", line 442, in <module>
    main()
  File "/home/thwright/Dev/LogosLinuxInstaller/./main.py", line 419, in main
    config.ACTION()
  File "/home/thwright/Dev/LogosLinuxInstaller/./main.py", line 304, in run_control_panel
    raise e
  File "/home/thwright/Dev/LogosLinuxInstaller/./main.py", line 292, in run_control_panel
    curses.wrapper(tui_app.control_panel_app)
  File "/usr/lib/python3.12/curses/__init__.py", line 94, in wrapper
    return func(stdscr, *args, **kwds)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/thwright/Dev/LogosLinuxInstaller/tui_app.py", line 708, in control_panel_app
    TUI(stdscr).run()
  File "/home/thwright/Dev/LogosLinuxInstaller/tui_app.py", line 251, in run
    self.display()
  File "/home/thwright/Dev/LogosLinuxInstaller/tui_app.py", line 216, in display
    self.console.display()
  File "/home/thwright/Dev/LogosLinuxInstaller/tui_screen.py", line 92, in display
    self.stdscr.addstr(2 + i, 2, f"{message}")
_curses.error: addwstr() returned ERR

It happens at this point in the log:
tail -n50 ~/.local/state/Logos_on_Linux/Logos_on_Linux.log
2024-08-29 08:31:04 DEBUG: sed status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: grep
2024-08-29 08:31:04 DEBUG: 'grep' installed: grep                                         3.11-1                            core      911.3 kB
2024-08-29 08:31:04 DEBUG: grep status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: gawk
2024-08-29 08:31:04 DEBUG: 'gawk' installed: gawk                                         5.3.0-1                           core      3.5 MB
2024-08-29 08:31:04 DEBUG: gawk status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: cabextract
2024-08-29 08:31:04 DEBUG: 'cabextract' installed: cabextract                                   1.11-2                            extra     73.9 kB
2024-08-29 08:31:04 DEBUG: cabextract status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: samba
2024-08-29 08:31:04 DEBUG: 'samba' installed: samba                                        4.20.4-1                          extra     65.0 MB
2024-08-29 08:31:04 DEBUG: samba status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: bc
2024-08-29 08:31:04 DEBUG: 'bc' installed: bc                                           1.07.1-5                          extra     176.1 kB
2024-08-29 08:31:04 DEBUG: bc status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: libxml2
2024-08-29 08:31:04 DEBUG: 'libxml2' installed: libxml2                                      2.13.3-1                          core      4.0 MB
2024-08-29 08:31:04 DEBUG: libxml2 status: Installed
2024-08-29 08:31:04 DEBUG: Checking for: curl
2024-08-29 08:31:04 DEBUG: 'curl' installed: curl                                         8.9.1-2                           core      2.0 MB
2024-08-29 08:31:04 DEBUG: curl status: Installed
2024-08-29 08:31:04 DEBUG: Packages status: {'patch': 'Installed', 'wget': 'Installed', 'sed': 'Installed', 'grep': 'Installed', 'gawk': 'Installed', 'cabextract': 'Installed', 'samba': 'Installed', 'bc': 'Installed', 'libxml2': 'Installed', 'curl': 'Installed'}
2024-08-29 08:31:07 DEBUG: packages to check: []
2024-08-29 08:31:07 DEBUG: Packages status: {}
2024-08-29 08:31:07 DEBUG: No missing or conflicting dependencies found.
2024-08-29 08:31:07 DEBUG: Performing pre-install dependencies…
2024-08-29 08:31:07 DEBUG: No pre-install dependencies required.
2024-08-29 08:31:12 DEBUG: 'libfuse' found at '/usr/lib/libfuse3.so.3.16.2'
2024-08-29 08:31:12 INFO: * libfuse is installed!
2024-08-29 08:31:12 DEBUG: fuse_lib_installed=True
2024-08-29 08:31:12 DEBUG: No missing packages detected.
2024-08-29 08:31:12 DEBUG: No conflicting packages detected.
2024-08-29 08:31:12 DEBUG: Performing post-install dependencies…
2024-08-29 08:31:12 DEBUG: No post-install dependencies required.
2024-08-29 08:31:12 DEBUG: No dependency install required.
2024-08-29 08:31:12 DEBUG: > Done.
2024-08-29 08:31:12 DEBUG: Install step 11 of 23
2024-08-29 08:31:12 INFO: Progress: 48%
2024-08-29 08:31:12 INFO: Ensuring wine AppImage is downloaded…
2024-08-29 08:31:12 INFO: 'wine-devel_9.12-x86_64.AppImage' exists in /home/thwright/Downloads.
2024-08-29 08:31:12 DEBUG: Checking /home/thwright/LogosBible10 for wine-devel_9.12-x86_64.AppImage.
2024-08-29 08:31:12 DEBUG: Checking /home/thwright/Dev/LogosLinuxInstaller for wine-devel_9.12-x86_64.AppImage.
2024-08-29 08:31:12 DEBUG: Checking /home/thwright/Downloads for wine-devel_9.12-x86_64.AppImage.
2024-08-29 08:31:12 INFO: wine-devel_9.12-x86_64.AppImage exists in /home/thwright/Downloads. Verifying properties.
2024-08-29 08:31:12 INFO: Verifying /home/thwright/Downloads/wine-devel_9.12-x86_64.AppImage…
2024-08-29 08:31:12 DEBUG: Comparing size of https://github.com/FaithLife-Community/wine-appimages/releases/download/9.12-devel/wine-devel_9.12-x86_64.AppImage and /home/thwright/Downloads/wine-devel_9.12-x86_64.AppImage.
2024-08-29 08:31:12 DEBUG: Getting headers from https://github.com/FaithLife-Community/wine-appimages/releases/download/9.12-devel/wine-devel_9.12-x86_64.AppImage.
2024-08-29 08:31:12 DEBUG: Starting new HTTPS connection (1): github.com:443
2024-08-29 08:31:12 ERROR: Curses error in run_control_panel(): addwstr() returned ERR

Got this error while running:
2024-08-29 09:04:39 ERROR: Error running '/usr/bin/winetricks -q settings renderer=gdi': 1

still getting the same "Download" error that I mentioned above. This is starting from a clean ubuntu 20.04 system and installing with the most recent binary built in the test-builds repo.

I have not been able to replicate on my main machine, so I may need to start a VM to test.

I got a successful install with newest binary and no existing config file, but it still shows "Install..." in the curses window rather than "Run...". Still getting the WINETRICKSBIN = 'Download' issue, but trying to trace it down.

My work in #164 introduces a consistently refreshing TUI main menu; it might resolve the Install/Run issue. The only thing I can think otherwise is to evaluate why it might be failing to detect the install and thereby fail to update the menu list. I'm guessing some check is failing, as a successful TUI install has updated the menu for me, to my knowledge, every time.

Trying to sort out the WINETRICKSBIN = 'Download' problem, and here is the logic I'm following:

my existing test config file defines WINETRICKSBIN as /home/<user>/LogosBible10/data/bin/winetricks
installer.py checks for existing config.WINETRICKSBIN; if it is not None and if using curses, then app.set_winetricksbin(config.WINETRICKSBIN) called
tui_app.set_winetricksbin checks if the argument starts with "Download" (it doesn't); then utils.get_winetricks_options() is called and the 1st result ("Download") is set as config.WINETRICKSBIN
and off we go with config.WINETRICKSBIN = 'Download' rather than the pre-defined value in config.WINETRICKSBIN

So I think what should happen is a modification to tui_app.set_winetricksbin. Here's the current function:
    def set_winetricksbin(self, choice):
        if choice.startswith("Download"):
            self.tricksbin_q.put("Download")
        else:
            winetricks_options = utils.get_winetricks_options()
            config.WINETRICKSBIN = winetricks_options[0]
            self.tricksbin_q.put(config.WINETRICKSBIN)
        self.menu_screen.choice = "Processing"
        self.tricksbin_e.set()

but nowhere does it just accept existing config.WINETRICKSBIN as-is if it's already defined in the config file. So maybe it should be more like this?:
    def set_winetricksbin(self, choice):
        if config.WINETRICKSBIN is not None:
            self.tricksbin_q.put(config.WINETRICKSBIN)
        elif choice.startswith("Download"):
            self.tricksbin_q.put("Download")
        else:
            winetricks_options = utils.get_winetricks_options()
            config.WINETRICKSBIN = winetricks_options[0]
            self.tricksbin_q.put(config.WINETRICKSBIN)
        self.menu_screen.choice = "Processing"
        self.tricksbin_e.set()

There are other ways to solve this; e.g. maybe changing the function in installer.py, but I leave that up to @thw26 to figure out because I don't know if there might be other TUI-related ramifications because of how this gets resolved.

This is the installer.py for winetricks:
    if config.WINETRICKSBIN is None:
        # Check if local winetricks version available; else, download it.
        config.WINETRICKSBIN = f"{config.APPDIR_BINDIR}/winetricks"

        if app:
            utils.send_task(app, 'WINETRICKSBIN')
            if config.DIALOG == 'curses':
                app.tricksbin_e.wait()
            winetricksbin = app.tricksbin_q.get()
        else:
            m = f"{utils.get_calling_function_name()}: --install-app is broken"
            logging.critical(m)

        if not winetricksbin.startswith('Download'):
            config.WINETRICKSBIN = winetricksbin
    else:
        if app:
            if config.DIALOG == 'curses':
                app.set_winetricksbin(config.WINETRICKSBIN)
                app.tricksbin_e.wait()

    logging.debug(f"> {config.WINETRICKSBIN=}")

As you can see, the problem is that we never actually trigger set_winetricksbin as a None rule because we define it before we proceed. Looking over to think what is the best way to proceed.

This is the other part of the issue. In installer, we split the steps in two: get the user choice and process it later. This is already happening partially in the TUI code. Without also changing the GUI, we need to make sure that we pass along Download.
def ensure_winetricks_executable(app=None):
    config.INSTALL_STEPS_COUNT += 1
    ensure_wine_executables(app=app)
    config.INSTALL_STEP += 1
    update_install_feedback(
        "Ensuring winetricks executable is available…",
        app=app
    )

    if not os.access(config.WINETRICKSBIN, os.X_OK):
        tricksbin = Path(config.WINETRICKSBIN)
        tricksbin.unlink(missing_ok=True)
        # The choice of System winetricks was made previously. Here we are only
        # concerned about whether the downloaded winetricks is usable.
        msg.logos_msg("Downloading winetricks from the Internet…")
        system.install_winetricks(
            tricksbin.parent,
            app=app
        )
    if config.WINETRICKSBIN:
        logging.debug(f"> {config.WINETRICKSBIN} is executable?: {os.access(config.WINETRICKSBIN, os.X_OK)}")  # noqa: E501
    return 0

I think this is a simpler solution. In this case, we now just check if app is set or not. Then if app is set, we check if the config is None or not. If it is None, we send a task to get a new value. Only in this new situation do we then set config.WINETRICKSBIN to a new value. Otherwise, we keep the old value and we will eventually progress to the ensure winetricks is exectuable step.
def ensure_winetricks_choice(app=None):
    config.INSTALL_STEPS_COUNT += 1
    ensure_wine_choice(app=app)
    config.INSTALL_STEP += 1
    update_install_feedback("Choose winetricks binary…", app=app)
    logging.debug('- config.WINETRICKSBIN')

    if app:
        if config.WINETRICKSBIN is None:
            utils.send_task(app, 'WINETRICKSBIN')
            if config.DIALOG == 'curses':
                app.tricksbin_e.wait()
            config.WINETRICKSBIN = app.tricksbin_q.get()
    else:
        m = f"{utils.get_calling_function_name()}: --install-app is broken"
        logging.critical(m)

    logging.debug(f"> {config.WINETRICKSBIN=}")

I'm in the middle of testing, and things are looking pretty good so far. Here's what I've noticed at this point:

overall things seem to work correctly both with and without an existing config file! :tada:
there's a regression during the actual installation of the Logos MSI: it fails when using the -P (passive MSI install) flag (I use this in testing all the time to speed it up, but most users probably aren't going to use it)
there's a GUI regression in that picking a Logos version other than the top one auto-reverts back to the top one

I'm going to look into them a little deeper next.


Vite crash because of RangeError: Invalid Websocket Frame 1006 WS_ERR_INVALID_CLOSE_CODE

Describe the bug
If the ws dependency module emits an error while HMR is running, it goes unhandled and causes Vite's node process to crash.
node:events:491
throw er; // Unhandled 'error' event

This particular ws throws after the computer goes to sleep and wakes up.
Afaik, this is not reproducible via vite.new
Reproduction
https://stackblitz.com/edit/vitejs-vite-3cq32j?file=index.html&terminal=dev
Steps to reproduce

Start Vite with HMR
Visit your localhost app (Chrome was used)
Put computer to sleep, wait a few seconds
Observe this on your page

And in terminal:

I have a fix for this and will make a PR
In summary,
We need to put an error handler on socket here
You can see the creator of ws approving how the handler was done here
By catching the error on socket, Vite does not crash.
System Info
System:
    OS: macOS 12.6.2
    CPU: (10) arm64 Apple M1 Max
    Memory: 135.20 MB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.0.0 - ~/.nvm/versions/node/v19.0.0/bin/node
    Yarn: 3.3.1 - ~/.nvm/versions/node/v19.0.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v19.0.0/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Firefox: 109.0.1
    Safari: 16.3

Used Package Manager
yarn
Logs

Click to expand! This is the crash
RangeError: Invalid WebSocket frame: invalid status code 1006
at Receiver.controlMessage (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:55108:18)
at Receiver.getData (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:54984:42)
at Receiver.startLoop (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:54700:22)
at Receiver._write (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:54626:10)
 at writeOrBuffer (node:internal/streams/writable:392:12)
 at _write (node:internal/streams/writable:333:10)
 at Writable.write (node:internal/streams/writable:337:10)
at TLSSocket.socketOnData (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:57408:37)
 at TLSSocket.emit (node:events:513:28)
 at addChunk (node:internal/streams/readable:324:12)
 at readableAddChunk (node:internal/streams/readable:297:9)
 at Readable.push (node:internal/streams/readable:234:10)
 at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)
Emitted 'error' event on WebSocket instance at:
at Receiver.receiverOnError (file:///Users/XXX/node_modules/vite/dist/node/chunks/dep-3007b26d.js:57294:13)
 at Receiver.emit (node:events:513:28)
 at emitErrorNT (node:internal/streams/destroy:151:8)
 at emitErrorCloseNT (node:internal/streams/destroy:116:3)
 at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'WS_ERR_INVALID_CLOSE_CODE',
[Symbol(status-code)]: 1002
}

Node.js v19.0.0

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://github.com/vitejs/vite/pull/12007

Ah thanks, I didn't catch the link somehow 😅

It's on me Bjorn - I wrote this issue and didn't update it. Just linked to
the issue from the PR
Thanks for taking a look
On Tue, Feb 14, 2023 at 1:46 AM Bjorn Lu @.***> wrote:

Ah thanks, I didn't catch the link somehow 😅
—
Reply to this email directly, view it on GitHub
https://github.com/vitejs/vite/issues/11991#issuecomment-1429431825, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHGA4BJOQNT5ILO6A4VC4LWXNH6BANCNFSM6AAAAAAUV3J3JE
.
You are receiving this because you were mentioned.Message ID:
@.***>


KAFKA-12254: Ensure MM2 creates topics with source topic configs

MM2 creates new topics on the destination cluster with default configurations. It has an async periodic task to refresh topic configurations from the source to destination. However, this opens up a window where the destination cluster has data produced to it with default configurations. In the worst case, this could cause data loss if the destination topic is created without the right cleanup.policy.
This patch fixes the above issue by ensuring that the right configurations are supplied to AdminClient#createTopics when MM2 creates topics on the destination cluster.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @rajinisivaram @junrao for review

Thanks for the review @rajinisivaram. I ran MirrorConnectorsIntegrationSSLTest a few times locally and it passed. It passed in the latest jenkins run as well. Couple of failures in the latest run seem unrelated to the changes.


querySelector should be propagated to all crawling contexts

As mentioned by @B4nan in #2316

@B4nan do we still want to go through with this? Doesn't waitForSelector and parseWithCheerio work just as fine?

Yeah, I feel like it's more in line with how we want people to create crawlers, when I tried to use the querySelector it felt clunky. I'll close this but we can revisit this later if there are some people using this context helper.


acme: unstable-2020-12-27 -> unstable-2021-02-14

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126070 run on x86_64-darwin 1

2 packages built:

acme
cheesecutter

Result of nixpkgs-review pr 126070 at a5afb78b run on x86_64-linux 1

2 packages built successfully:

acme
cheesecutter


Doesn't Compile in Unity 2018.4

Hi,
I tried to import this in Unity 2018.4.23 but it is using SerializedReference which to my knowledge was only added in 2019.3.
Thanks,
Niall

Yeah, sadly I built based on the SerializedRefernce, what makes retro compatibility impossible, and ATM I don't have plans to implement one alternative


[FIX] Fix jsdoc

Description of change
Fixed a few jsdoc mistakes
References:
https://github.com/pixijs/pixi.js/pull/5537#issuecomment-513457260
https://github.com/pixijs/pixi.js/blob/3630c98f255b2d39ced1909b5cb5d1f70feaaa99/packages/core/src/textures/Texture.js#L596
Pre-Merge Checklist

[x] Documentation is changed or added

Codecov Report

Merging #5944 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #5944   +/-   ##
=======================================
  Coverage   70.38%   70.38%
=======================================
  Files         208      208
  Lines       10493    10493
=======================================
  Hits         7386     7386
  Misses       3107     3107

Impacted Files
Coverage Δ

packages/settings/src/settings.js
100% <ø> (ø)
:arrow_up:

packages/core/src/textures/Texture.js
92.3% <ø> (ø)
:arrow_up:

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 3630c98...4165f7e. Read the comment docs.


Subtitles support

Would it be possible?

I'm not sure, I haven't looked into it, unfortunately.

Does the ChromeCast api allow subtitles for a web URL?

That's a good question, I think so, but I don't know. If Pychromecast has support for subtitles, it would probably be easy to implement.

Hmm, I managed to add support to another tool here, so it's possible, anyways, I got my use case figured out. Thanks!
https://github.com/owyongsk/stream2chromecast/commit/da7c239fc9d34464ab4c826090775265923ecb61

Oh, very interesting! That doesn't seem too hard, I'll see if I can get something implemented quickly (as I need this myself too). Thanks!

Good luck, I needed this to learn Spanish in my subtitles. Haha.

Damn! I'll keep this open, as we do need this. Thanks for the report!

@owyongsk I checked your PR and saw that it's quite easy to add subtitles on catt. Thanks for the nice hint.


resolves #16

updates incorrect port mapping for ui container in:
README.md
docker-compose.yml
docker-compose.override.dev.yml
docker-compose.override.example.yml

Please see /frontend/default.conf.  The configured listening port for the UI container is 80, but all compose files and the example nginx configuration for external access show port 8080, which is not correct.

port 8080 is intentional, as this is the port of the ui container.
Your proxy should forward from 80 to 8080 for the ui.

port 8080 is intentional, as this is the port of the ui container.
Your proxy should forward from 80 to 8080 for the ui.

I don't think you read the issue correctly.  the problem is that the container is listening on port 80, not 8080.  forwarding to port 8080 will result in an error because, as written, the container is listening on port 80 and this PR was to address that by changing it to 8080

You should encounter no errors while setting up Nginx with the configuration suggested. I've created a quick graph for clarity; I hope it helps.

Traffic enters on "app.snypy.com" on ports 80 and 443.
This traffic is then received by the host's Nginx server, which is set to listen on ports 80 and 443.
The host's Nginx server then directs the traffic to a frontend container via port 8080.
Inside the frontend container, there is a port mapping from 8080 to 80.
The Nginx server inside the container, which is listening on port 80, then handles the incoming traffic.


Remove deposit by Junior Campbell from CORE

Date first reported: 12/1/21
Date requested for completion:
Site: Humanities Commons
Area (CORE, profiles, sites, groups, account ): CORE
Description
User Junior Campbell uploaded a document with COVID-19 misinformation and libelous/defamatory attacks against scientists and others that needs to be removed from CORE. Deposit titled "Chronicling Jamaican 'Crown Bishop' Kevin Smith's, my and others' crystal twinning COVID-19 cries."
Further details
COmanage: https://registry.hcommons.org/registry/co_people/index/co:2/Search.givenName:junior/Search.familyName:campbell
WP: https://hcommons.org/members/poeticjazztice/

Immediate steps - DOI change and nginx change completed. Deposit is no
longer reachable. Remaining cleanup will be done later today.
On Wed, Dec 1, 2021 at 2:21 PM Katherine Knowles @.***>
wrote:

Date first reported: 12/1/21
Date requested for completion:
Site: Humanities Commons
Area (CORE, profiles, sites, groups, account ): CORE
Description
User Junior Campbell uploaded a document with COVID-19 misinformation and
libelous/defamatory attacks against scientists and others that needs to be
removed from CORE. Deposit titled "Chronicling Jamaican 'Crown Bishop'
Kevin Smith's, my and others' crystal twinning COVID-19 cries."
Further details
COmanage:
https://registry.hcommons.org/registry/co_people/index/co:2/Search.givenName:junior/Search.familyName:campbell
WP: https://hcommons.org/members/poeticjazztice/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MESH-Research/commons/issues/224, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7ZYVRXYW2LYQJLNMGPIF3UOZYUPANCNFSM5JFI3QMQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
R. Eric Knappe
Head of Software Development
Modern Language Association
85 Broad St. Suite 500
NY, NY 10004
(646) 576-5030
www.mla.org


Use x instead of mica in examples section of function documentation

All functions accepting a CamtrapDP object as argument have an example in documentation at least where mica is used. mica as camtrap DP object is not anymore loaded: we read such an object and we hold it in cache via the reexported camtrapdp function example_dataset(). So, in @example section of ROxygen documentation should start always with:
x <- example_dataset()

and then use x consequently.
Notice that I have already replaced mica with x in all the vignettes in PR #307 .
Agreed with @PietrH to NOT change mica elsewhere, for example in tests.

Close as completed via #325


NotEmptyValidator minimal logging

NotEmptyValidator always returns an empty set for it's bad property regardless of failure causing the Vlad class to return False and log the general "Failed :(" message without an indication of the field that failed or the times it failed. Solution proposed below avoids repetition of empty strings in logger output while providing logging on par with the other Validators.
class NotEmptyValidator(Validator):
    ''' Validates that a field is not empty '''

    def __init__(self):
        self.fail_count = 0
        self.empty = set([])

    def validate(self, field, row={}):
        if field == '':
            self.empty.add(field)
            raise ValidationException("Row has empty field in column")

    @property
    def bad(self):
        return self.empty

Nice catch, thanks @gregorkschroeder!

Thanks for this great utility!


Fixing how the GEOS library is found

When we switched to the GEOS C library in the prior release we did not update the FindGEOS.cmake file, and as a result, it will not find the GEOS library if the C++ version is not installed.

@pjreed I know you looked at the Humble release last time, does this seem okay to you?


Prevent GitHub from opening when installing with --no-interaction

Fixes #8880
I know this issue was assigned to the person who raised it, so I hope you don't mind me raising a PR. The simplest solution in my opinion is to set the confirmation default to false when the no-interaction option is passed.
I've tested this for normal installation (without --no-interaction) and you are still prompted with the default being 'yes'.
When running with --no-interaction or -n, the rest of the script runs as before but the browser is no longer opened with the filament GitHub page.

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Perfect, thanks. You're smashing these! It's really appreciated.

Thanks! I was going to try my hand at this today, but don't mind you doing it at all! Been super busy myself, so haven't been able to code much.

Just came here to say thank you, @ashleyshenton.
Really appreciate people like you jumping in and helping us out getting the issue count down. 🫶


_tryExtHostHandshake depends on winjs.promise timing

This commit https://github.com/Microsoft/vscode/commit/7224bb340dfbd5d7eb11944b39c43675eb58a557 apparently broken debug in weird ways. The $registerDebugTypes was called anymore. This commit fixed it again:
https://github.com/Microsoft/vscode/commit/407a48525a7732774a1fa1a6123f4ff75d4749e7

How can that break debugging 🦀

Good question... I was in revert mode only but my theory is that it sends a message before we are ready for it to be processed (it sends something in a ctor-call).

After some investigation: this is not about the ctor.
TPromise and Promise behave in the same way around the invocation order of the ctor.
The difference is the invocation of then, where Promise always invokes then on the next tick. The result of the promise is an IMessagePassingProtocol and in between those ticks to invoke the then handler, a message (or more) get lost.
I will look into how it would be possible to refactor this... It would almost need pause/resume functionality on IMessagePassingProtocol...


plain-txt-passwd should be plain_text_passwd

Thank you for the blog post. I noticed the error above. It occurs both in the blog post and this repository.
Hope this helps.

Hi, it is text not txt. Hope this helps.

@VPanteleev-S7 Ah gotcha, I went through the documentation and you are write. Let me correct it.


[FEATURE]: Option to run migrations on schema other than public

Describe what you want
I would like to have the option to run my migration against a DB schema that isn't public but tenant_1 for example.
Something like:
import { migrate } from 'drizzle-orm/node-postgres/migrator';
import { database } from './database.js';

await migrate(database, {
  schema: 'tenant_1',
});

Does the schema option shown here fixes this?

@Angelelz No, this issue is about defining the schema while executing the migration. The link you attached is about defining the schema while defining the table. The functionality I ask for could be useful for multi-tenant systems.

I think you could work around it by doing:
// schema.ts
import { serial, text, pgTable, pgSchema } from "drizzle-orm/pg-core";
import { schemaName } from "./migrate.ts"

export const mySchema = pgSchema(schemaName)

export const mySchemaUsers = mySchema.table('users', {
  id: serial('id').primaryKey(),
  name: text('name'),
});

// db.ts
import { drizzle } from 'drizzle-orm/mysql2';
import mysql from 'mysql2/promise';
import * as schema from './schema';

export const connection = mysql.createConnection({
  host: process.env.DB_HOST,
  user: process.env.DB_USER,
  password: process.env.DB_PASSWORD,
  database: process.env.DB_NAME,
  multipleStatements: true,
});
export const db = drizzle(connection, { schema });

//migrate.ts
import 'dotenv/config';
import { migrate } from 'drizzle-orm/mysql2/migrator';
import { db, connection } from './db';

export const schemaName = "MyNewTenant";  // Define your schema name next to the migrate function

await migrate(db, { migrationsFolder: './drizzle' });

await connection.end();

You can specify a custom schema and table for migrations.
If you want to do this with drizzle-kit, please refer to: https://orm.drizzle.team/docs/drizzle-kit-migrate#applied-migrations-log-in-the-database.
For the ORM migrate() function, you can do the same.
await migrate(db, { migrationsFolder: './drizzle', migrationsTable: '', migrationsSchema: '' });

@AndriiSherman I suggest re-opening the issue as it requests another feature. In this issue, I meant that the migrations themselves will create/update/drop tables in a schema that isn't public. Like in a multi-tenant system where you have a separated schema per tenant.


fix/client: Insufficient color contrast on highlighted code block in …

…Dark Mode
Checklist:

[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 main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #42405

I think this solves the issue.

This is the result I got after
Before

After

Ah! Sorry, I didn't test it locally before I made the suggestion.
So I just got a chance to try it now.
In the stylesheet for dark mode (prism-night.css), we will need to add .night to the selectors add to achieve higher specificity. For light mode (prism.css) though, we will need to add .default to beat prism. night and default are the values we use for theme preferences, btw.
The correct code should be:
/* prism-night.css */
.night pre[class*='language-']::selection,
.night pre[class*='language-'] ::selection,
.night code[class*='language-']::selection,
.night code[class*='language-'] ::selection {
  background: var(--selection-color);
}

/* prism.css */
.default pre[class*='language-']::selection,
.default pre[class*='language-'] ::selection,
.default code[class*='language-']::selection,
.default code[class*='language-'] ::selection {
  background: var(--selection-color);
}

And here is the result:

Dark
Light

Notice that the selection color on light mode is a bit darker, it is the blue-dark-translucent from our color lists.

Oo yes I understand and,  Thank you so much for your time
And I updated the files


Refactorization of App.java.

Logic is unchanged to previous version. I have hope that this version is a little easier to read.

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:


Juliainstaller Crash Report

Trying to install Julia 1.10.2 on macOS v14.4.1, M1 iMac. I previously had Julia 1.9 installed by downloading it, but I deleted it and still have this error. When I type 'julia' in command line, I have no Julia installed. I have tried running the install command (curl) with sudo but still doesn't work. Would be nice to know if there is any way to fix this.
Report file:
"name" = "Juliainstaller"
"operating_system" = "Mac OS 14.4.1 [64-bit]"
"crate_version" = "1.14.7"
"explanation" = """
Panic occurred in file 'src/operations.rs' at line 1021
"""
"cause" = """
called `Result::unwrap()` on an `Err` value: Failed to open file /Users/g/.bash_profile.

Caused by:
    Permission denied (os error 13)"""
"method" = "Panic"
"backtrace" = """

   0: 0x104736420 - core::result::unwrap_failed::h79c2cb9e4fc28c72
   1: 0x1045a077c - juliaup::command_config_modifypath::run_command_config_modifypath::h7e32c7395314f06d
   2: 0x104491800 - juliainstaller::main::ha5b6681862e25582
   3: 0x10447eab8 - std::sys_common::backtrace::__rust_begin_short_backtrace::h040e90bfea1c4f44
   4: 0x10449665c - _main"""

I also have exactly the same problem, here.
"name" = "Juliainstaller"
"operating_system" = "Fedora 39.0.0 [64-bit]"
"crate_version" = "1.14.8"
"explanation" = """
Panic occurred in file 'src/operations.rs' at line 1021
"""
"cause" = """
called `Result::unwrap()` on an `Err` value: Failed to open file /home/jubran/.bashrc.

Caused by:
    Permission denied (os error 13)"""
"method" = "Panic"
"backtrace" = """

   0: 0x7fc9fd9e86cd - juliaup::command_config_modifypath::run_command_config_modifypath::hd5a74fa3d14e27b4
   1: 0x7fc9fd8bb8d9 - juliainstaller::main::hc7d4f590be58fbb4
   2: 0x7fc9fd8a38f3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h4fd42de0f5791891
   3: 0x7fc9fd8c165c - main"""

I will just paste my answer from https://github.com/JuliaLang/juliaup/issues/796:

I got the exact same crash report.
Problem caused due to ~/.bash_profile not being owned by the user attempting to edit the file.
Change ownership of .bash_profile:
sudo chown {username} ~/.bash_profile
Then got same error but this time mentioning .zshrc. Again, same solution:
sudo chown {username} ~/.zshrc
After this installation was successful.

I forgot to come back and update, I got it working fine, for some reasons my zsh configuration files that were used by julia installer had a different owner, so I could not run them as sudo, I just had to mess with them a bit before retrying to install julia.


"Closes: #1"

updated validation message to reflect accurate username checking
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Design Public Cloud Wordpress Site

Describe the issue
The private cloud team has launched a new site that is part of an effort to replace devhub with something that is easier for their maintenance capabilities.
Additional context

There is a website at https://cloud.gov.bc.ca which currently doesn't exist but redirects to https://cloud.gov.bc.ca/private-cloud/
The intended structure that Justin had is

cloud.gov.bc.ca

private-cloud

saas

public-cloud

mobile-and-developer-experience

the idea is that cloud is the greeting page, and the visitor is offered a choice to the present services run by each team
we wrote the content
there is general theming already done on the site that is good to reuse for consistency's sake

Definition of done

Cloud Pathfinder PO and the tech writer contractor for platform services has drafted the public-cloud site
Get hold of the draft site, update with PO, and set up a minimal place-holder
Create one sub-section, empty with a link pointing to devhub as a holder for the journey to cloud https://developer.gov.bc.ca/Cloud-Pathfinder-Onboarding-Journey/

tracked in other tickets


Update normalization equations for 3D Tiles metadata

The 3D Metadata Specification now has equations for normalization, defined here. These are the same as the equations defined by glTF for animations (link). The main change is that the min value and the min + 1 value both map to -1.0

E.g. for INT8 — -128 and -127 both map to -1.0

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


seirdy.one

Website: https://seirdy.one
Lighthouse audits are saved in CI artifacts: https://builds.sr.ht/~seirdy/seirdy.one
Homepage weight is under 3kb without non-blocking not-usually-downloaded stuff like the webmanifest and Android icon, and under 6 kb with them. Without any favicons, it should be closer to 2kb.
Notability: hit front page of lobste.rs, 43 points + 109 comments: https://lobste.rs/s/akcw1m/opinionated_list_best_practices_for
I know that lobste.rs isn't listed on the criteria for notability, but I was hoping they could be amended to include it. I'm personally not the biggest fan of Reddit and HN.
The lobsters link also contains links to archived versions from the time of posting.

Also, the article that got linked on lobsters is probably pretty relevant.

Thank you for creating this issue and adding this suggestion.
Added Lobsters to the eligibility criteria in commit 7b05e24.
Added https://seirdy.one to the list of websites in commit 2da9246.


Add python -m argilla server start in Set up the server

@davidberenstein1957 should I add it as an alternative to the Docker installation, in two differents headings? https://docs.argilla.io/en/latest/community/developer_docs.html#set-up-the-server
It would be something like this:
## Set up the Server

Before running the Argilla server, it is recommended to [build the frontend files](#build-frontend-static-files) to be able to access the UI on your local host.

### Set up locally

python -m argilla server start

### Set up with Docker

Then, to run Argilla backend, you will need an ElasticSearch instance up and running for the time being. You can get one running using Docker with the following command:
sh
docker run -d --name elasticsearch-for-argilla -p 9200:9200 -p 9300:9300 -e "ES_JAVA_OPTS=-Xms512m -Xmx512m" -e "discovery.type=single-node" -e "xpack.security.enabled=false" docker.elastic.co/elasticsearch/elasticsearch:8.5.3

If I should place it in any other place, or it is not an alternative, please let me know :)

https://docs.argilla.io/en/latest/reference/cli.html#server

move https://docs.argilla.io/en/latest/community/developer_docs.html#create-the-default-user to setup the database after running migrations

https://docs.argilla.io/en/latest/community/developer_docs.html#set-up-the-server reference that we need the databases up and running


Add option to ignore imports of the python stdlib

I would like to add an option to ignore imports of the python standard library.

I just wrote a 'prototype' version. I would just like to know if you would appreciate such an option. If this is not the case, I won't have to improve my code/write tests, etc.

If you plan to do so, please do not merge this yet. There is still some work to be done.

This sounds all good to me. Let me know if you want anything changed!

This look all good to me. Feel free to review/change my code.

I've resolved all the issues. Please let me know if there's anything else !

Ok, I pushed to the wrong branch ....

Thank you!

Merged and released findimports 2.2.0


docs/External-Commands.md:  Small Environment-Variable Listing Fix

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.  (N/A, as I'm only updating documentation, not modifying any code.)

[ ] Have you successfully run brew tests with your changes locally?  (Mostly, but, no, not entirely; in 'test/os/mac_spec.rb,' 'Locale::parse' failed to parse 'OS::Mac::language,' but this is unrelated.)

     Avoid confusion for authors of external commands by updating 'HOMEBREW_LIBRARY_PATH' to 'HOMEBREW_LIBRARY.'

This is accurate as-is. By default,

HOMEBREW_LIBRARY = /usr/local/Homebrew/Library, while
HOMEBREW_LIBRARY_PATH = /usr/local/Homebrew/Library/Homebrew, where Homebrew's code is located.

@EricFromCanada:
     OK, sorry.  Neither 'HOMEBREW_LIBRARY' nor 'HOMEBREW_LIBRARY_PATH' appear to be documented in man brew's 'ENVIRONMENT' section, though.  Should they be?  I can add them in another PR if you like (or two, if adding them separately would be better.)
P. S.:  Based on your description, the name of 'HOMEBREW_LIBRARY_PATH' doesn't describe its purpose well.  Its also ambiguously close to that of 'HOMEBREW_LIBRARY.'  Has a change to the former environment variable's name ever been considered?

As I understand it, the man page's ENVIRONMENT section only describes variables which change Homebrew's behaviour if assigned values, rather than every variable that Homeberw sets.
I don't know, but I doubt it.

@EricFromCanada:

As I understand it, the man page's ENVIRONMENT section only describes variables which change Homebrew's behaviour if assigned values, rather than every variable that Homeberw sets.
⋮

     It does note the following about 'HOMEBREW_DEBUG_INSTALL' and 'HOMEBREW_DEBUG_PREFIX,' though:

⋮

       HOMEBREW_DEBUG_INSTALL
              When brew install -d or brew install -i drops into a shell, HOMEBREW_DEBUG_INSTALL will be set
              to the name of the formula being brewed.

       HOMEBREW_DEBUG_PREFIX
              When  brew install -d or brew install -i drops into a shell, HOMEBREW_DEBUG_PREFIX will be set
              to the target prefix in the Cellar of the formula being brewed.

⋮

and those are set by Homebrew rather than users, so there's precedent for documenting env. variables like them.

⋮
2. I don't know, but I doubt it.

     Just thought I'd ask, is all.

the man page's ENVIRONMENT section only describes variables which change Homebrew's behaviour if assigned values, rather than every variable that Homeberw sets.

Yes.

and those are set by Homebrew rather than users, so there's precedent for documenting env. variables like them.

We'd review a pull request to remove them.


which is the null hypothesis?

pval = itest(df.iloc[:,ix].values,  df.iloc[:,jx].values, test_args={'statistic': 'mixed_mi', 'n_jobs': 8})
is_independent = (pval >= 1.- 0.95) #confidence_level = 0.95
So, the output is True. So, the two variables are independent.
Which is the null hypothesis here?

The null hypothesis usually refers to independence


Can nosnoc determine the state transition borders (gap functions)?

Hi,
Thanks for the nice tool and quite interesting research papers.
I am not sure how to formulate one hybrid dynamics problem in order to solve it with Nosnoc. In simple terms, it is as follows:
master; % integer, influences the speed capabilities by switching the profiles
u; % continuous control

if master==0
    f = profile_0; % define dynamics profile 0
elseif master==1
    f = profile_1; % define dynamics profile 1
end

% goal: achieve *maximum speed*.
% Determine best `u` (continuous control) and `master` (profile sequence e.g. profile_0, profile_1, profile_0)

I have checked examples, but I start to think you might not be dealing with these cases. I saw that you are defining the gap function. However, in this case the gap function should be kinda determined by the algorithm and it might be changing in time as well.
Would really appreciate feedback.
Best,

Hello,
thanks for your interest in our work. nosnoc cannot determine the gap/switching functions.
In fact, the switching functions, passed via model.c in nosnoc, is a key ingredient in the definition of a nonsmooth dynamical system.
It seems to me, that master corresponds to the switching profile, which are the variables theta in our code and papers ( the Filippov convex multipliers).
It would be helpful if you can determine what triggers the change of master, which state?
Best regards,
Armin

Hi Armin,
Thank you for the response! I was trying to find a way to incorporate and define switching functions for this case. Maybe I can try out with defining some additional optimization variable (continuous decision variable) and constraint. Something like:
   mu = opti.variable(d);
   opti.subject_to(mu*q == 0);

Do you have an example on how to do that with nosnoc?
Best,
Vasilije

Hi Vasilije,
If I understand it correctly, you have a problem and want to find out the switching functions.
So far, we have not dealt with this case and assume the switching functions to be known.
You can pass them to nosnoc via model.c = c where c is some CasADi expression.
Mathematically, it might lead to some difficulties because c(x) the switching function depends on other variables than the differential states.
However, when the pending pull request is merged, we will likely have support for having other unknown parameters (which we call v_global.  And one will be able to define a switching function that can be optimized.
But maybe you can provide me with more details on your problem and I can help formulate it possibly within the currently available tools (which are well-tested and understood). You can also write me an e-mail if you like.
Best regards,
Armin


Add generalized methods

This patch builds on top of  https://github.com/bdaiinstitute/ros_utilities/pull/92  to introduce generalized methods, functions bound to class instances. This restores user facing type annotations and docstrings for generalized callables used in class (or mixin :eyes:) context.

Still on draft until I'm done with unit tests.


Update questions

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


"Quake Mode" launch animation

Description of the new feature/enhancement
A simple sliding animation for the quake mode when it is launched and dismissed. Ideally it would have a linear speed (as opposed to any fancy acceleration or bounce) to bring that "quake console" feel a bit more legitimately.

Proposed technical implementation details (optional)
I'm not sure how this would be implemented. But if you managed to make the quake mode possible in the first place I imagine an animation should also be in the realm of possible too

Nothing else. You guys are doing a fantastic job with the new Terminal. I've been using it for the past few months and having tabs alone is already an incredible QoL improvement. And I'm already very excited with this new way to summon and dismiss it with a key combo.

It should also ideally be optional and disabled by default. As I imagine most users would appreciate quick access through that method

there's already an animation, docs:
quake-mode
global-summon

Yeah I don't know what version you're using but it has support for animation (and disabling it).

Thanks for the replies. I've tried what the documentation says on my settings.json and it seems to straight up ignore the dropdownDuration parameter. Maybe this could use also being in the proper settings

did you disable animations on windows accessibility settings?

That seems to have been the problem, I didn't assume that setting would affect this but I guess that makes sense.
Now my problem is that the animation seems quite glitchy and stuttery. But I guess that's a different issue, so I consider this closed. Thanks for your help.


GO:0018064 & GO:0003908 - missing parent?

I think these two terms need 'GO:0008276 protein methyltransferase activity' as an additional parent?
id: GO:0018064
name: protein-L-histidine N-tele-methyltransferase activity
namespace: molecular_function
def: "Catalysis of the reaction: L-histidyl-[protein] + S-adenosyl-L-methionine = N(tele)-methyl-L-histidyl-[protein] + S-adenosyl-L-homocysteine." [RHEA:19369]
synonym: "actin-specific histidine methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "peptidyl-histidine N-methyltransferase activity" EXACT []
synonym: "protein (histidine) methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "protein methylase IV activity" NARROW [EC:<IP_ADDRESS>]
synonym: "protein-histidine N-methyltransferase activity" BROAD []
synonym: "S-adenosyl methionine:protein-histidine N-methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "S-adenosyl-L-methionine:protein-L-histidine N-tele-methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
xref: EC:<IP_ADDRESS>
xref: MetaCyc:<IP_ADDRESS>-RXN
xref: RHEA:19369
is_a: GO:0008170 ! N-methyltransferase activity
is_a: GO:0008757 ! S-adenosylmethionine-dependent methyltransferase activity
id: GO:0003908
name: methylated-DNA-[protein]-cysteine S-methyltransferase activity
namespace: molecular_function
def: "Catalysis of the reaction: DNA (containing 6-O-methylguanine) + (protein)-L-cysteine = DNA (without 6-O-methylguanine) + protein S-methyl-L-cysteine." [EC:<IP_ADDRESS>]
synonym: "6-O-methylguanine-DNA methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "DNA-6-O-methylguanine:[protein]-L-cysteine S-methyltransferase activity" EXACT []
synonym: "DNA-6-O-methylguanine:protein-L-cysteine S-methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "methylated-DNA-protein-cysteine S-methyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "MGMT" EXACT []
synonym: "O-6-methylguanine-DNA-alkyltransferase activity" RELATED [EC:<IP_ADDRESS>]
synonym: "O6-alkylguanine-DNA alkyltransferase" BROAD []
xref: EC:<IP_ADDRESS>
xref: MetaCyc:<IP_ADDRESS>-RXN
xref: RHEA:24000
is_a: GO:0008172 ! S-methyltransferase activity

Hi @sjm41
No problem for GO:0018064  protein-L-histidine N-tele-methyltransferase activity;
however for GO:0003908 methylated-DNA-[protein]-cysteine S-methyltransferase activity, it seems like the goal of the reaction is not to methlyate the protein, but to demethylate (e repair) the DNA. Therefor the protein is not really a substrate, it's an acceptor, so I would not add the 'protein methylase activity' parent.
What do you think ?
Thanks, Pascale

Hi @pgaudet I see what you mean about GO:0003908...
Though the GO term does seem to be classed as a "methyltransferase" (in the term name, current parentage, EC classification) rather than a "demethylase", so adding the extra "protein methyltransferase activity" parent (in addition to the current "S-methyltransferase activity" parent) doesn't seem wrong?
("protein methyltransferase activity" def: Catalysis of the transfer of a methyl group (CH3-) to a protein.)
Not a biggie either way....

@pgaudet OK if I go ahead and add the suggested parent to these two terms myself?

yes, sure!


Formatting changes on each save for some lines

We have an issue where code such as if (not isArcOn()): will change with each save, it will go from the original code to if ( not isArcOn()) on the next save it goes back to the original code.  There are other formatting changes that do this is well but this is the one that I keep seeing over and over in our PR's on the code because it vacillates with each save of the file.
I have tested this with the latest 0.1.2 code release and the issue is still there.

Hi @mbush92 ,
I'm trying to fix this problem on 00fca1c @ master or release v0.1.3. maybe you can take a try.

That fixed the issue.  Thanks!  Do you plan on releasing this to the VSCode extension store?

That's a good idea 😁 I will release it when I have free time ...


Update container workdir if EE enabled

The host CWD passed to the runner API
will be volume mounted with EE if enabled
and will be used as workdir within the
container
Pass CWD for run action so as to a similar
experience while running ansible on local
sytem VS EE, this enables the use of ansible.cfg
in CWD of host with EE.

recheck


Major refactor of chef-client cookbook

I'd like to propose a complete refactoring of this cookbook. This constitutes a major version change and would likely break current use of the cookbook. As such it needs to be clearly communicated far and wide as to the intent, the rationale, and the scope. We need to make a version that works "as is" for the current state of the world and refer to that version for those who can't upgrade.
Background
This cookbook started life as the chef cookbook, and was intended to provide a way to set up a chef-client daemonized service and manage the /etc/chef/client.rb content, since chef was shipped as a RubyGem only, and RubyGems aren't packages that set up system services or manage their own configuration.
Over time this cookbook has grown in scope. It manages services across multiple different init systems and process supervisors. Some of those are hard dependencies that cause a dependency graph of epic proportions, or confusion (cron, logrotate, windows). Some of those are not hard dependencies, causing their use to not actually work if those cookbooks aren't included elsewhere on the node's run list (bluepill, daemontools, runit). There are more attributes than can be reasoned about in a rationale sense, causing cognitive load on new users.
Proposed Changes
I've broken up my thoughts on the changes I'm proposing into the following sections.
Services
Move all the service management recipes into per platform providers for a new chef_client_service resource for all the "native" services:

bsd
init
launchd
smf
src
upstart
systemd (does not exist, would be created)
windows

These would be per platform/platform family, and per platform version. As much as possible these should leverage core Chef resources to reduce additional dependencies.
Remove the "process supervision" style service management recipes out of this cookbook entirely. These could become new separate cookbooks with dependencies only on the supervision tool they use. For a proof of concept example of this, see chef-client-runit.
The service recipe could be rewritten to leverage the new chef_client_service resource so that the cookbook continues to work as is.
Example:
chef_client_service "upstart-example" do
  upstart_job_dir "/etc/init"
  action [:enable, :start]
end

Scheduler
Move the scheduled task / cron configuration to a new resource, chef_client_scheduler. This will set up chef-client to run on a schedule under "Scheduled Tasks" (Windows) or "cron" (Unix/Linux). This replaces the task and cron recipes.
However, it may worth considering that running chef-client going forward should not be as a cron job or scheduled task. The reason for that in the past was because the process would grow over time when run as a resident service, but the default mode of running is to fork a worker process as of Chef 11.6 (released July 23, 2013).
Configuration
Management of /etc/chef/client.rb will be moved to a new resource, chef_client_config. Attributes can be preserved and be passed into the resource. Additional configuration concerns need to be handled:

Log rotation (see next section)
Report/exception handlers
Ohai plugin management
Gems required by Chef for configuration purposes
"Dot d" directory inclusion

Examples:
chef_client_config "/etc/chef/client.rb" do
  options node['chef_client']['config']
end

chef_client_config "/etc/chef/client.d/my_config.rb" do
  options(:option_key => "option-value", :its => "a hash")
end

Logging
Log rotation/log management may fall under configuration.
We should have a sane way to get Syslog (Unix/Linux) and Event Viewer (Windows) logging in place through configuration. Even if that is just an example that we can document in the README.md, that's okay).
Some "Rules"
Some rules I'd like to follow with this refactoring, and this is incomplete, and up for embellishment/bikeshedding.
No attribute settings in recipes. All attributes will be set in attributes/default.rb to sane and sensible defaults.
No per-platform attributes except if they should be user-tunable. These should be in the per-platform providers for the relevant resources.
We will not support for Chef 10. We'll make a decent effort to support Chef 11, but we're targeting Chef 12 and may make use of Chef 12 features/changes (such as those to chef_gem in 12.1.0). We'll have an older major version updated to work with Chef 11 and ongoing support will be on a best effort basis.
We must have 100% test coverage between ChefSpec unit tests, and ServerSpec integration/post convergence tests.
As much as reasonably possible, we should support running an instance of chef-client as non-privileged.
We should play nice with Chef Server, in that users may wish to manage their Chef Server with chef-client (insert yo dawg joke).
The resources implemented in this cookbook will be in libraries and subclass the Chef::Resource::LWRPBase and Chef::Provider::LWRPBase. We'll also need to write corresponding matchers for others to use ChefSpec, in libraries/matchers.rb.
Certain attributes may be replaced with helper methods. Those will be written in libraries/helpers.rb. If namespacing is deemed a requirement for helpr methods, I propose ChefClientCookbook as the module name.
All outstanding issues and pull requests need to be addressed. See comment below.

Currently the version released is 4.2.4. I propose that this work is done for version 5.0.0, and that we take any changes from the open pull requests/issues into consideration for whether they're in scope for v5, or for a new release of 4.x. The 4.x version would be the last major release that supports Chef 11 entirely.

So I talked with @someara and as far as he knew the only reason for not using resources/ and providers/ and going with HWRPs was renaming the resources, which can be done with provides (and can be back-compat with chef-11 and chef-10).  Are there still other reasons for doing that?

(I'm basically :+1: on the idea, so just picking at that particular nit)

^ Indeed. I had no idea about :provides. I would have used it

All sounds great to me, for what that's worth. :+1:

I've found it easier to reason about unit testing the resource/provider when they're LWRPBase sub classes, but I don't know that unit testing is going to be that valuable - I think we end up wrapping a couple of core Chef resources, and we definitely don't want to test that Chef works, since we know that to be the case.
@lamont-granquist @someara Have an example of the kind of syntax we'd want in a resources/ or providers/ file?

For renaming resources?  Bottom of this:  https://www.chef.io/blog/2015/02/10/chef-12-provider-resolver/
I think you can still unit test LWRPs with ChefSpec, and it should work fine on Chef-12.  With Chef-11 you get the memory leak performance issue catastrophe, but we fixed that in 12 so LWRPs aren't constantly loading/unloading classes in ChefSpec.

:100: :+1: on playing nice with chef-server

As someone who has unsuccessfully tried to pay down some of the tech debt in this cookbook, you have my :+1:

I fully support a more modular approach (*nix philosophy) to managing chef-client.  Also it appears that the proposed changes won't clobber the existing 'chef-client' cookbook namespace, which mans users will upgrade only if they choose to explicitly.

Just a heads up to anyone reading this issue who might be wondering what's going on nearly a year later.  Well it's time to do this. Expect it in the coming month.  One note to add this will be a Chef 12+ cookbook as this rewrite will use Chef 12 custom resources.

Hey folks,
If you care about this refactor please take some time to fill out the survey here:
http://bit.ly/1TqRzZW
This will help inform us of the best way to prioritize changes. Thanks!

I'm going to close this issue out since it's a project more than a feature request or a bug. I think we all know we want to do some refactoring to the cookbook though.


Objectify bodies for k6

Objectify bodies that are strings (i.e. url encoded, Content-Type: application/x-www-form-urlencoded) for k6 javascript since k6 automagically url-encodes.

Implemented and released 1.1


Doc20211108

Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

This post was published here already: https://www.metanorma.org/blog/2021-08-26-pdf-accessibility-for-math-formulas/
Closing.


feature request: add payment methods

I am not sure where to add a feature requests.
I would like to ask to add a Polish payment methods and German SEPA transfers.
Please move/close if this is a wrong place.

Closing this item. P24 has been added. SEPA has been placed on the roadmap, so no need to discuss any further.


919 spanish readme

Description
Spanish readme for Flame
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ X] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
[ X] My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
[ X] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
[ X] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
[ X] I read and followed the Flame Style Guide.
[ X] I have added a description of the change under [next] in CHANGELOG.md.
[ X] I removed the Draft status, by clicking on the Ready for review button in this PR.
[ X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flame users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
[ X] No, this is not a breaking change.

Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.

Thanks the comments. I made another PR.


Admin Dashboard Service List

Show the list of services created filtered according to chosen dates. There will be two date pickers in the query section. The items in the list will show the date, name, creator and the status of the service.

There will be an option for choosing the dates for service creation date and service delivery date.

"List Service Feature" was added to Admin Dashboard, passed the tests and was merged.


Dynamic AR object management for large campuses / areas

Currently only portions of the North-East campus is mapped out. My testing locations at my apartment complex are confined into a small area. However as soon as all the locations will be mapped out (https://github.com/RecyclingTrashCans/RecyclingTrashCans.github.io/issues/2) it won't make sense to place all those objects when AR tracking becomes active. There should be a range (preferably configurable and defaulting to a meaningful number) such as 200-300m radius where the objects would populate. As the students moves around this radius would be re-evaluated and objects could be added and removed dynamically (hence the ticket name).

Badly needed once https://github.com/RecyclingTrashCans/RecyclingTrashCans.github.io/issues/2 is  completed and the number of locations will quadruple, quintuple

Let's only show the closest 20 trashcans at any time, and maybe the ones which are towards the current gaze? Although if the user is yanking around the phone what would lead to violent object creation, so maybe the gaze is not feasible?


Vite injects __vitePreload even if the modulePreload option is disabled

Describe the bug
Vite injects __vitePreload on each dynamic import, I would expected this not be included when modulePreload is set to false.
Eg. If I want to handle preloading manually or not at all.
Related https://github.com/vitejs/vite/issues/13952 https://github.com/vitejs/vite/pull/13973
Reproduction
https://stackblitz.com/edit/vitejs-vite-p54vgg
Steps to reproduce
Run vite build and the output is actually larger then the source.
System Info
..

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Related: https://github.com/vitejs/vite/pull/13973

In our scenario, preloading any file causes errors as we have a tricky way of resolving file paths (our code runs inside a vscode controlled iframe).
Specifically __vitePreload injects a stylesheet link that causes our page to not load.
Following the referenced PRs and issues, I understand why it's the case, but is there a workaround to prevent the runtime injection of the preloads today?


start creating proposal as soon as signer session is initialized

Motivation
Speed up creating and publishing a proposal in 1:N setups.
Description
In the original code, the ProposalBuilder::build was logically divided into 3 stages:

in parallel (up to cfg.workersLimit parallelization) initialize signers' sessions (only done once per signer)
run tortoise tallying votes, mesh hash calculation etc.
in parallel create and publish proposals by eligible singers

The problem was that stage 1 had to finish for all signers before stage 3 could start. It means that a single slow-to-initialize signer blocked all the others (ready to go).
This PR changes the code to have 2 stages running in parallel:

initializes signers' sessions (in parallel)
creates and publishes proposals for eligible signers

First, the already initialized signer's sessions are directly fed into stage 2. Then, the remaining uninitialized ones enter stage 1 for initialization. The stage 1 feeds initialized signer sessions to stage 2 via a channel. The culprit is that stage 2 creates proposals as soon as any signer session becomes ready (and is eligible).
Tallying votes and calculating mesh hash still happens once, and it is executed by the signer that first lands in stage 2 (using sync.OnceValue).
Test Plan

existing tests pass
added a test that verifies if an eligible signer publishes its proposal as soon as possible, even if others are blocked

TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

This looks fine, however, two questions:

If errors from stage 1 do not affect the execution of stage 2 (i.e. stage 2 will try to execute on as many signers anyway), why do we need to split it into 2 stages in the first place?
Why wait with the call to all the OnceValue functions? Why not call them preemptively before even starting to 'initialize' the signers?

This looks fine, however, two questions:

If errors from stage 1 do not affect the execution of stage 2 (i.e. stage 2 will try to execute on as many signers anyway), why do we need to split it into 2 stages in the first place?
Why wait with the call to all the OnceValue functions? Why not call them preemptively before even starting to 'initialize' the signers?

I was also thinking about these 2 points. I don't have a definitive answer because it is not 100% clear why the original code was split this was (init -> tortoise etc. -> publish). I didn't want to change this behavior. My guesses are:
Ad 1. The 1st stage runs with limited parallelism. I'm unsure why, perhaps to avoid too many simultaneous DB queries that would slow down the entire process? The 2nd stage doesn't have this limitation.
Ad 2. Again, I think the reason is to avoid running extra processing when no one is eligible (which is most of the time)

Drafting as I think I broke the builder the last commit (despite tests pass :fearful:).

Bors merge


Fixed LineEdit virtual keyboard inputs on Android

Changed the condition to add a length filter to make it consistent with the documentation (0 means no character limit). Otherwise the default value in LineEdit causes the virtual keyboard to be non-fonctional on Android.
Fixes #35753

Cherry-picked for 3.2.1.


PDF Viewer opens without being asked to on a random PDF

So when I click e right from the KT in a non-PDF topic, to immediately edit the Element Window and then press Enter to add a linebreak it will open the SMA PDF Viewer.
When I press alt twice first, before pressing e, this will not happen.
https://www.loom.com/share/dba30d1dfa8c485b89f4568c48afadaf

Might not be random, might be the last used PDF. Uploading my collection to SMA Dev, just in case this is difficult to replicate.

ah similar random stuff happens without SMA.
It's just a desync that happens, when you don't focus the Element Window first by pressin enter or alt twice.
Should be on the list of "100 surprsing things not to do in SuperMemo", but isn't a SMA bug per se.


Issue with streamlit-condition-tree Component Not Updating Correctly with "config"

Description
I'm experiencing an issue with the streamlit-condition-tree component in my Streamlit application where the component does not seem to update correctly with its configuration. Initially, the component displays a default "index in index" query string, and then it should update based on user interaction and configuration changes. However, this update does not seem to occur as expected.
Steps to Reproduce

Initialize the streamlit-condition-tree component with a DataFrame configuration.
Run the Streamlit application.
Interact with the component or trigger an update.
Observe that the component does not update as expected and remains at the default state.

Expected Behavior
Upon interaction or receiving new configuration data, the streamlit-condition-tree component should update and reflect the changes based on user input or updated configuration.

Current Behavior
The component initializes with a default "index in index" state but does not update as expected with user interactions or when provided with new configuration data.

Environment
Streamlit version: 1.28.2
streamlit-condition-tree version: 0.1.2
Browser version: Chrome Version 119.0.6045.159 (Official Build) (64-bit) / Firefox 119.0.1 (64-bit)
Operating System: Ubuntu 22.04.3 LTS

Additional Context and Observations
The debug logs show that the component is registered and the script reruns on interaction, but the component's state does not seem to update with the new configuration.
Initial tests with different configurations suggest that the issue might be related to how the component's state is managed in Streamlit's reactive framework.
I have tried various troubleshooting steps, including checking the component's initialization, ensuring correct configuration formats, and testing in different environments (local and deployed).

I really appreciate the functionality that streamlit-condition-tree brings to Streamlit applications, and I'm eager to resolve this issue. Any insights or suggestions from the community or maintainers would be incredibly helpful.
Thank you for your time and effort in developing and maintaining this useful component.

Hi @andreabandinu,
Sorry for my late answer and thanks for the effort to report this issue. However, I don't really manage to understand in what context this occurs. In general, as you can see in the demo, the component state and its outputs are updated when the user interacts with it.
Can you please share a minimal example of the code that generates this issue ? Thanks


fix(deps): update cbr + provider version

Description
CBR v1.22.0 requires provider version >= 1.62.0, update the minimum required version for root of module and bump examples to lock to lowest

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

Failing renovate PR: https://github.com/terraform-ibm-modules/terraform-ibm-iam-account-settings/pull/278

/run pipeline

/run pipeline

this PR will fix the issues with the PR https://github.com/terraform-ibm-modules/terraform-ibm-iam-account-settings/pull/278

:tada: This issue has been resolved in version 2.10.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Flatten Vault JSON to Properties

Currently, Secrets uses Map<String, String> to store properties which prevents nested JSON objects.
Vault uses JSON to represent the data element. Keys inside of data can be stored either using dot-notation { 'nested.key' : 'value' } or as objects { 'nested': { 'key': 'value' } }. Both styles have equivalent semantics when viewed from a config perspective:
nested.key=value

Secrets should flatten objects and unfold arrays which makes { 'array[0]': 'value0', 'array[1]' : 'value1'  } equivalent to{ 'array': ['value0', 'value1'] }:
array[0]=value0
array[1]=value1

in my vault, properties are stored in nested json format but config server is flattening it up,
for ex:- { abc : { def : xyz} }  is getting converted into {abc.def : xyz} in the config server response, could you please tell me how can maintain my original structure. I don't want this flattend output. please respond that would be a great help


Fix circular references on assertions before sending across the wire.

We serialize and send copies of assertions errors across the wire on failure.
If assertionError.actual, or assertionError.expected have a circular reference, this causes a problem when process.send converts to JSON.
This replaces serialize-error with destroy-circular. I found one tiny bug with their implementation, but it seems good otherwise.

:angry:
Windows and Node 0.10 are quickly becoming annoying.

It looks like AppVeyor is having some issues. Those pass just fine in my Windows VM. It's not making it through npm install on AppVeyor

What the heck? It was green after rebase! All I did was squash!

Crap. Adding the tap-spec reporter should not have made this pass.
We have intermittent test failures on CI that I can not reproduce locally at all.

@sindresorhus
I think this is ready for merge.
I can drop the tap-spec commits, but I wanted you to see the brittle test issue I'm having before I do. (and if it fails again when I revert to @2f16758, I may toss my computer out the window).

:+1:


Support playback of base64-encoded SWFM files

To enable almost-fully self-contained HTML files that only need the GFX bundle as a runtime, nothing more.

/botio preview

Are you waiting for a review? Is this ready to land?

@tschneidereit is this ready for review?

Any way ididnotknow about it and
Its hebben  am ahorng  man and not guy i cont get enogh from sex i sweer one time the pay me 13000 te make a porn film but i didnot be cous i have recpacf for my body and my big dik


no scroll  for open exploit page

sometime it will not show buttons there should be a scroll button for that

Thank you for the feedback, we will debug and let you know when it will be fixed.


Bump transport to 8.6.1

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 89e24122e6a9573c2e38b9865e610abb25ed0c15

Failed CI Steps

:elasticsearch: :javascript: Elasticsearch Serverless Node.js v20 integration tests

:green_heart: Build Succeeded

Buildkite Build
Commit: 1ec1ce56f3fcbd84bcf39c4be4fe199e5e1b707e

History

:broken_heart: Build #1027 failed 89e24122e6a9573c2e38b9865e610abb25ed0c15


publish patched NekoDTD and NekoHTML to Maven Central

Problem summary
Currently Nokogiri's java native gem depends on patched versions of NekoDTD and NekoHTML. The binary artifacts only exist in Nokogiri's git repo and if I needed to reproduce them I would be starting from scratch.
Historical context
In the past (e.g., 2e5ce32 in 2012 and 6166964 in 2015) we've patched NekoHTML and NekoDTD to fix bugs or parsing errors. These repositories live (I think) at:

https://github.com/jvshahid/nekohtml
https://github.com/jvshahid/nekodtd

A conversation at #1253 suggested using jar-dependencies to manage Java dependencies, and #2432 starting doing so for the artifacts listed on Maven Central.
What do we want to do
This issue is intended to drive a conversation with the following potential outcomes:

[x] ensure shared ownership of the patched NekoHTML and NekoDTD source repositories
[x] set up a Maven Central groupId (@headius pointed us at https://central.sonatype.org/publish/publish-guide/)
[ ] https://github.com/sparklemotion/nekodtd/issues/1
[ ] https://github.com/sparklemotion/nekohtml/issues/3
[ ] use jar-dependencies to manage those dependencies like our other ones

Doing all of the above would allow us to consider further patches on the Neko libraries, e.g., #2436.
cc @jvshahid whose support and assistance I will need

@jvshahid Would you be open to transferring ownership of those repositories to me or to the sparklemotion org? That would unblock me to do the rest of the work.

Thanks, @jvshahid! Repositories have been transferred to @sparklemotion/nokogiri-core

https://github.com/sparklemotion/nekohtml
https://github.com/sparklemotion/nekodtd

I've created a JIRA account at OSSRH and requested a new project with the groupId org.nokogiri: https://issues.sonatype.org/browse/OSSRH-77736

@flavorjones As always let me know if I can help. I get a lot of notifications so I don't always see updates here, but I support this move and will try to help as time permits.

@headius Thanks for checking in! I will be respectful of your time, but may ask for advice or a code review here and there as I work through this and a handful of other JRuby issues for v1.14.0.

Note that on main, we get our HTML parser from neko-htmlunit and not the fork of nekohtml mentioned above. I've updated the title and description to reflect that we don't need to do that work anymore.

See https://github.com/sparklemotion/nokogiri/pull/2538 and https://github.com/sparklemotion/nekodtd/issues/1. This is basicall done, just waiting for CI to go green.


restlay refactoring, better performance, tests

wrote lot of tests to avoid future regressions,
there should be no breaking changes in the connectData API.

complete refactoring of connectData, it should be much more performance now
implements shouldComponentUpdate and only render if data effectively changes (we're keeping object reference and comparing the new data with isEqual, to be improved).
there is 2 new option flags than can be used: freezeTransition and renderLoadingInTransition. we're not using it yet but we'll consider these different load/reload strategies.
there is now a RestlayProvider to render on the top level and that makes the library truely generic and customizable.
there are lot of tests now, testing many things and we'll continue to write more.

to not merge yet