NavigationExperimental behavior is buggy when replacing stack entries

Or maybe I'm misunderstanding what's supposed to happen.
Let's say my initial navigation state is
{ key: 'root', index: 0, children: [ { key: 'home' } ] }
and then I replace it with
{ key: 'root', index: 0, children: [ { key: 'settings' } ] }
As far as I can tell, NavigationScenesReducer, via NavigationAnimatedView, will keep rendering both settings and home, and since they both have the same index, compareScenes ends up sorting by alpha. Should isStale be part of compareScenes?
(Also, to be honest, I don't totally understand why stale scenes are part of the result returned by NavigationScenesReducer, it'd be great to have some more comments in the code to explain why it works this way.)

cc @ericvicenti

I experienced the same issue yesterday and searched around and found a relevant few comments/issues:

renderOverlay receives wrong scene after replace - https://github.com/ericvicenti/navigation-rfc/issues/73
https://github.com/aksonov/react-native-router-flux/issues/474
https://github.com/aksonov/react-native-router-flux/issues/636 - suggests skipping 0.25 and waiting for 0.26
• https://github.com/aksonov/react-native-router-flux/pull/618/commits/e828fb071b6705e2579399cc1f77c4f96e43a67f - this PR addresses this issue and I implemented it in my project (it's a hack).

There are probably other GitHub issues around describing the same problem.

I reported ericvicenti/navigation-rfc#73. The stale scenes are kept around during animation. They are removed in NavigationAnimatedView._onProgressChange after the transition completed.
The issue with the same numeric index is very easy to fix (as mentioned in my other issue). After thinking about it some more, I think the best fix would be to change NavigationScenesReducer not to produce a stale scene if there already is a fresh scene at the same index with a different key.

I'm a newbie in NavigationExperimental and I'd like to know something more about the magic behind this:

(Also, to be honest, I don't totally understand why stale scenes are part of the result returned by NavigationScenesReducer, it'd be great to have some more comments in the code to explain why it works this way.)

I also don't get the reason behind having the scenes saved in the internal state of NavigationAnimatedView, which is causing some confusion when replacing the stack entries with a custom reducer...

Hey folks, sorry to hear about the troubles! Also cc @hedgerwang

(Also, to be honest, I don't totally understand why stale scenes are part of the result returned by NavigationScenesReducer, it'd be great to have some more comments in the code to explain why it works this way.)
I also don't get the reason behind having the scenes saved in the internal state of NavigationAnimatedView, which is causing some confusion when replacing the stack entries with a custom reducer...

It is done in this way so that the scene stays around for the duration of the animation as the removed scene exits the screen. We keep the internal state in the AnimatedView because it is usually a bad idea to maintain the animation state in your app state.
That said, it seems like we have a bug in the scenes reducer while doing a replace. If somebody wants to debug this, write a failing test case, or add a failing UIExplorer 'replace' example, we would greatly appreciate it!

Ah, that's what I suspected (about keeping stale scenes for animation). I suspect one issue is around the animation being tied to index, which in this case would be from to 0 to 0, so the stale scene is never removed. I saw you assigned the bug to yourself - do you still need someone to poke around at this?

Yeah, that's the problem. I was mistaken earlier and thought this was a problem with the scenes reducer. But you're right that this is more of a fundamental design problem. Hedger and I will work on a solution that decouples the transition from the index.

Hey @ericvicenti, any news regarding this issue?  🌊

@mmazzarolo I believe @ericvicenti and @hedgerwang are working on a new version of NavigationAnimatedView called NavigationTransitionerthat's been redesigned to address the issues mentioned here. That being said, NavigationTransitioner comes with its own set of issues that need to be addressed before it can replace NavigationAnimatedView.
See  jmurzy/react-router-native/issues/3
🍺

@jmurzy Thank you man!
In the meantime does anybody know a way to reset the stack in the current version of Navigation Experimental?  (or at least a way to unmount the components after a replace so that it can be re-rendered?)

I created a little MonkeyPatch for my own purpose of NavigationAnimated view that allows stack to be replaced, use it at your own risk:
// scenesReducer.js

const invariant = require('fbjs/lib/invariant');
const SCENE_KEY_PREFIX = 'scene_';

/**
 * Helper function to compare route keys (e.g. "9", "11").
 */
function compareKey(one: string, two: string): number {
    const delta = one.length - two.length;
    if (delta > 0) {
        return 1;
    }
    if (delta < 0) {
        return -1;
    }
    return one > two ? 1 : -1;
}

/**
 * Helper function to sort scenes based on their index and view key.
 */
function compareScenes(one, two) {
    if (one.index > two.index) {
        return 1;
    }
    if (one.index < two.index) {
        return -1;
    }

    return compareKey(one.key, two.key);
}

function areScenesShallowEqual(one, two): boolean {
    return (
        one.key === two.key &&
        one.index === two.index &&
        one.isStale === two.isStale &&
        one.navigationState === two.navigationState &&
        one.navigationState.key === two.navigationState.key
    );
}

export default function NavigationScenesReducer(scenes, nextState, prevState) {
    const prevScenes = new Map();
    const freshScenes = new Map();
    const staleScenes = new Map();

    // Populate stale scenes from previous scenes marked as stale.
    scenes.forEach(scene => {
        if (scene.index !== -1) {
            const { key } = scene;
            if (scene.isStale) {
                staleScenes.set(key, scene);
            }
            prevScenes.set(key, scene);
        }
    });

    const nextKeys = new Set();
    nextState.children.forEach((navigationState, index) => {
        const key = SCENE_KEY_PREFIX + navigationState.key;
        const scene = {
            index,
            isStale: false,
            key,
            navigationState,
        };
        invariant(
            !nextKeys.has(key),
            `navigationState.children[${index}].key "${key}" conflicts with` +
            'another child!'
        );
        nextKeys.add(key);

        if (staleScenes.has(key)) {
            // A previously `stale` scene is now part of the nextState, so we
            // revive it by removing it from the stale scene map.
            staleScenes.delete(key);
        }
        freshScenes.set(key, scene);
    });

    if (prevState) {
        // Look at the previous children and classify any removed scenes as `stale`.
        prevState.children.forEach((navigationState, index) => {
            const key = SCENE_KEY_PREFIX + navigationState.key;
            if (freshScenes.has(key)) {
                return;
            }
            staleScenes.set(key, {
                index,
                isStale: true,
                key,
                navigationState,
            });
        });
    }

    const nextScenes = [];

    const mergeScene = (nextScene => {
        const { key } = nextScene;
        const prevScene = prevScenes.has(key) ? prevScenes.get(key) : null;
        if (prevScene && areScenesShallowEqual(prevScene, nextScene)) {
            // Reuse `prevScene` as `scene` so view can avoid unnecessary re-render.
            // This assumes that the scene's navigation state is immutable.
            nextScenes.push(prevScene);
        } else {
            nextScenes.push(nextScene);
        }
    });

    const freshScenesArray = [...freshScenes.values()];
    staleScenes.forEach(scene => {
        if (scene.index === 0 && freshScenesArray.find(({ index }) => index === scene.index)) {
            scene.index = -1;
        }
        mergeScene(scene);
    });

    freshScenesArray.forEach(mergeScene);

    return nextScenes.sort(compareScenes);
}

// NavigationAnimatedView.js
/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 *
 */
/* eslint-disable no-underscore-dangle */

import React, { PropTypes } from 'react';
import { Animated, NavigationExperimental, StyleSheet, View } from 'react-native';
import scenesReducer from './scenesReducer';

const {
    Container: NavigationContainer,
    PropTypes: NavigationPropTypes,
} = NavigationExperimental;

function applyDefaultAnimation(position, navigationState, prevNavigationState) {
    if (navigationState.index === prevNavigationState.index) {
        position.setValue(-1);
    }
    Animated.spring(
        position,
        {
            bounciness: 0,
            toValue: navigationState.index,
        }
    ).start();
}

class NavigationAnimatedView extends React.Component {

    static propTypes = {
        applyAnimation: PropTypes.func,
        navigationState: NavigationPropTypes.navigationState.isRequired,
        onNavigate: PropTypes.func.isRequired,
        renderOverlay: PropTypes.func,
        renderScene: PropTypes.func.isRequired,
        style: View.propTypes.style,
    };

    static defaultProps = {
        applyAnimation: applyDefaultAnimation,
    };

    state = {
        layout: {
            height: new Animated.Value(0),
            initHeight: 0,
            initWidth: 0,
            isMeasured: false,
            width: new Animated.Value(0),
        },
        position: new Animated.Value(this.props.navigationState.index),
        scenes: scenesReducer([], this.props.navigationState),
    }

    componentDidMount() {
        this._positionListener = this.state.position.addListener(this._onProgressChange);
    }

    componentWillReceiveProps(nextProps) {
        if (nextProps.navigationState !== this.props.navigationState) {
            this.setState({
                scenes: scenesReducer(
                    this.state.scenes,
                    nextProps.navigationState,
                    this.props.navigationState
                ),
            });
        }
    }

    componentDidUpdate(lastProps) {
        const { index: lastIndex, children: lastChildren } = lastProps.navigationState;
        const { index, children } = this.props.navigationState;
        if (
            lastIndex !== index || (
                index === 0 &&
                children && lastChildren &&
                children.length && lastChildren.length &&
                children[0].key !== lastChildren[0].key
            )
        ) {
            this.props.applyAnimation(
                this.state.position,
                this.props.navigationState,
                lastProps.navigationState
            );
        }
    }

    componentWillUnmount() {
        this.state.position.removeListener(this._positionListener);
    }

    _onProgressChange = (data: Object) => {
        const delta = Math.abs(data.value - this.props.navigationState.index);
        if (delta > Number.EPSILON) {
            return;
        }

        const scenes = this.state.scenes.filter(scene => !scene.isStale);

        if (scenes.length !== this.state.scenes.length) {
            this.setState({ scenes });
        }
    }

    _onLayout = (event) => {
        const { height, width } = event.nativeEvent.layout;

        const layout = {
            ...this.state.layout,
            initHeight: height,
            initWidth: width,
            isMeasured: true,
        };

        layout.height.setValue(height);
        layout.width.setValue(width);

        this.setState({ layout });
    }

    _renderScenes() {
        return this.state.scenes.map(this._renderScene, this);
    }

    _renderScene(scene) {
        const {
            navigationState,
            onNavigate,
            renderScene,
        } = this.props;

        const {
            position,
            scenes,
        } = this.state;

        return renderScene({
            layout: this.state.layout,
            navigationState,
            onNavigate,
            position,
            scene,
            scenes,
        });
    }

    _renderOverlay() {
        if (this.props.renderOverlay) {
            const {
                navigationState,
                onNavigate,
                renderOverlay,
            } = this.props;

            const {
                position,
                scenes,
            } = this.state;

            return renderOverlay({
                layout: this.state.layout,
                navigationState,
                onNavigate,
                position,
                scene: scenes[navigationState.index],
                scenes,
            });
        }
        return null;
    }

    render() {
        const overlay = this._renderOverlay();
        const scenes = this._renderScenes();
        return (
            <View
              onLayout={this._onLayout}
              style={this.props.style}>
                <View style={styles.scenes} key="scenes">
                    {scenes}
                </View>
                {overlay}
            </View>
        );
    }
}

const styles = StyleSheet.create({
    scenes: {
        flex: 1,
    },
});

export default NavigationContainer.create(NavigationAnimatedView);

@fdecampredon I admit I didn't even investigate on what you're patching in those two components but they works fine for me, thank you 🍰

Hey there, I just wanted to let you know that @fdecampredon solution works on<EMAIL_ADDRESS>too, just remember to change:
export default NavigationContainer.create(NavigationAnimatedView);

to:
export default NavigationAnimatedView;

Still hoping for a more serious solution though.

@mmazzarolo AnimatedView is deprecated. NavigationTransitioner in v0.28.0-rc.0 should address most of these issues. Can you upgrade and let us know if it resolves it for you?
🍺

@ericvicenti @jmurzy
Sorry man, I've been really busy lately.
Sadly the I'm still having the issue on RN 28...
I'm not doing anything too fancy, I just have a CardStack wrapped in Drawer:
<Drawer
  currentRoute={currentRoute}
  onNavigate={this._handleAction}
>
  <CardStack
    navigationState={navState}
    onNavigate={this._handleAction}
    renderScene={this._renderScene}
  />
</Drawer>

The drawer has some button that when pressed should reset the stack and bring the user to the specific route.
The reducer reset action is the following (I changed it like 999 times):
case 'NAV_RESET': {
  const { route } = action
  return NavigationStateUtils.reset(state, [route], 0)
}

Unfortunately resetting the scene stack this way doesn't work: the new route is not rendered.
The reducer works correctly but I can clearly see that the in NavigationExperimental's scenes there are still the old routes (with isStale: true).
This setup worked perfectly with @fdecampredon solution.
Do you have any suggestions?

@mmazzarolo Sorry about this. I think your issue may be related to https://github.com/facebook/react-native/commit/c57bac4767fe4301ff4515b073d26245c6905610#commitcomment-17977007. Both @hedgerwang and @ericvicenti have been working hard in fixing things up over last few days. See facebook/react-native@c57bac4767fe4301ff4515b073d26245c6905610, facebook/react-native@b4d15d3c5ac4542931e0f3d1b93b42109e523550.
Unfortunately though, these patches did not make it into 0.29-rc. I hope to get those cherry picked into 0.29, facebook/react-native#8333.
If you are still having issues after applying above patches and have a repo that reproduces the issue, I'm happy to take a look.
🍺

Thank you and no worries @jmurzy , I'll try to update as soon as the commits get cherry picked 🏄

Hi.
I'm facing the same situation as @mmazzarolo
The reset scene does not render the new routes.
I've applied the patchs suggested by @jmurzy, but the behaviour is still the same.
As @mmazzarolo states, the solution provided by @fdecampredon worked.
Regards.

I'm trying to apply @fdecampredon's solution on RN-0.28.0
Do I just replace the entire contents of NavigationAnimatedView.js with the code above? they are pretty different so it's hard to figure out what changed and how to apply it correctly.
Also, I don't have an existing scenesReducer.js should i create it?

Hey @yonahforst, I suggest to copy NavigationAnimatedView.js and scenesReducer.js in your own project and then to use the copied NavigationAnimatedView instead of the RN one.
scenesReducer.js is just a dependency of NavigaitionAnimatedView.js:
import scenesReducer from './scenesReducer';

you don't need to use it directly

Hey @mmazzarolo, and thanks for the quick reply!
Thing is, I'm not actually using NavigaitionAnimatedView anywhere. I have a similar setup to what you described above, just a CardStack wrapped in a drawer.

My bad, you're using RN 0.28, I thought you were using RN 0.27 🙈
I don't know if NavigationAnimatedView still works in 0.28 (I guess not since it was deprecated on RN 0.27).
If you're interested in RN 0.27 I used the patched NavigationAnimatedView this way (an I'm still stucked in this version since the stack replacing doesn't work):
    return (
      <Drawer
        currentRoute={currentRoute}
        isOpen={isDrawerOpen}
        isEnabled={isDrawerEnabled}
        onNavigate={this._handleAction}
        navigationActions={this.navigationActions}
      >
        <NavigationAnimatedView
          navigationState={navState}
          onNavigate={this._handleAction}
          renderOverlay={this._renderToolbar}
          style={styles.container}
          renderScene={props => (
            <Card
              {...props}
              panHandlers={null}
              renderScene={this._renderScene}
              key={`card_${props.scene.navigationState.key}`}
            />
          )}
        />
      </Drawer>
    )

You can skip the <Card> component, I used it for only disabling the panHandler.

hmmm. didn't work. There were a bunch of breaking changes in 0.28.0 (e.g. navigationState.children was renamed to navigationState.routes). I tried adjusting correcting them but then i ran into some other errors, I'm assuming related to the breaking changes in 0.28.0.
I'm going to see what I can find about implementing a CardStack using the NavigationTransitioner since the AnimatedView deprecated (as you mentioned)

@jmurzy @hedgerwang @ericvicenti
I sadly confirm what @finalquest said, replacing the stack is still not working on 0.29.0-rc.2 😿
Don't take it as a critic (I know that working on an entire new navigation system can be incredibly hard... I would even like to help but I don't have enough knowledge of it) but: do you have any idea of what can be the source of this bug and/or if can be fixed in a short time?
I'm asking because this bug has been haunting me since April and I need to decide if I should switch to another Navigator (the old one or something like react-native-router-flux) or if I should just wait a bit more (I must be production ready in two months).
And again, thank you for you work guys 👊

@mmazzarolo
I was finally able to get mine working on 0.28.0 by replacing NavigationAnimatedView with NavigationTransitioner, basically copying this example: https://github.com/jlyman/RN-NavigationExperimental-Redux-Example/blob/master/app/containers/AppContainer.js
What's your setup? are you still using the solution by @fdecampredon? Here's my navigator component, if it's any help: https://gist.github.com/yonahforst/ef490002d2aed3b412979669347b04b4

@yonahforst thanks!
Replacing/resetting with NavigationTransitioner does work in 0.28.0 but it does not work with NavigationCardStack (also, NavigationCardStack won't work even on 0.29.0-rc2).
This does not work with stack resetting:
<Drawer
  currentRoute={currentRoute}
  isOpen={navState.isDrawerOpen}
  isEnabled={isDrawerEnabled}
  onNavigate={this._handleAction}
  navigationActions={this.navigationActions}
>
  <NavigationCardStack
    navigationState={navState}
    onNavigate={this._handleAction}
    renderScene={this._renderScene}
    renderOverlay={this._renderToolbar}
    style={styles.container}
  />
</Drawer>

This does work with stack resetting:
<Drawer
  currentRoute={currentRoute}
  isOpen={navState.isDrawerOpen}
  isEnabled={isDrawerEnabled}
  onNavigate={this._handleAction}
  navigationActions={this.navigationActions}
>
  <NavigationTransitioner
    navigationState={navState}
    onNavigate={this._handleAction}
    renderOverlay={this._renderToolbar}
    style={styles.container}
    renderScene={props =>
      <NavigationCard
        {...props}
        panHandlers={null}
        renderScene={this._renderScene}
        key={props.scene.route.key}
      />
    }
  />
</Drawer>

Example of action that resets the stack:
case 'NAV_RESET': {
  const { route } = action
  return NavigationStateUtils.reset(state, [route], 0)
}

Also please keep in mind that the above solution won't work out of the box in the future release of RN 0.29.0: it will need some kind of tweaks (e.g.: renderScene will be renamed to render etc.) but keep an eye on @jlyman example, he's constantly updating it (thanks 👍 ).
(@finalquest you might be interested)

@mmazzarolo - yeah, I was also using the NavigationCardStack component and replaced it with  NavigationTransitioner. As far as I can tell, I'm not missing anything and everything still pretty much works the same.
and yes, thank you @jlyman!

@mmazzarolo @yonahforst  NavigationCardStack in v0.29.0-rc2 is still using NavigationAnimatedView— deprecated. This is fixed in master. If NavigationTransitioner fixes your issue, then to fix NavigationCardStack, you would have to cherry pick this (and most probably apply to it this patch that cleans it up further) until a new release is cut.
🍺

@jmurzy
Replacing works in NavigationCardStack on 0.30.0-rc.0! 🆒
I wanted to report two other "issues" though (also, can you point me to a better place for discussing them?)
1. CardStack
The style applied to NavigationCardStack is now propagated to renderOverlay (it didn't work this way on versions < 0.27.0).
For example using the style { flex: 1, paddingTop: 64 } on NavigationCardStack now applies the padding to the navigation bar too (with the navigation bar being rendered by renderOverlay).
Not a real issue though, just a breaking visual change.
2. Card
panHandlers={null} doesn't disable "swipe to back gesture" anymore (it did on 0.27.0).
And thank you for all you've done and the support 👍

@mmazzarolo replacing does indeed work on 0.30.0-rc.0, though the animation isn't functioning correctly for me. Seems to just spontaneously change. The title in the nav bar for example, you can see the new title before the old title simply disappears.

@jmurzy still same situation on React-Native 0.30.0...
Is the stuff above considered the standard now?

Just going to confirm that my above comment is still accurate in the 0.30 release.

I'm using 0.30, and I've found the prop scene will not be set in render under the following situation:

Start at index 0
Push scene to index 1
Replace scene at index 1 (no animation)
Pop scene (so back at index 0)
NavigationCardStack will not pass the prop scene to its render methods

Same issue here with 0.30 - the scene prop is missing after a reset.

Can anyone please confirm that is it working on 0.31? @ng-marcus  @mmazzarolo

Working fine for me in 0.31 at the moment

I had the same issue and at seems to be working as expected now in 0.31

Closing this issue as it seems to be working fine now.


redmi k30pro android 11 cannot connet with wlan

Microsoft Windows [版本 10.0.17763.55]
(c) 2018 Microsoft Corporation。保留所有权利。
C:\Users\aylov\Desktop\scrcpy-win64-v1.17>adb pair <IP_ADDRESS>:37517
Enter pairing code: 582097
Successfully paired to <IP_ADDRESS>:37517 [guid=adb-8079df11-FeTcHY]
C:\Users\aylov\Desktop\scrcpy-win64-v1.17>scrcpy
INFO: scrcpy 1.17 https://github.com/Genymobile/scrcpy
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1

Is the device listed in adb devices?

设备是否列在中adb devices？

I don't quite understand. It's connected through WiFi. What should I do

https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#device-not-detected
I've never used adb pair, but for scrcpy to work, the device must be detected via adb devices.

https://developer.android.com/studio/command-line/adb
Did you call adb connect after adb pair?

https://developer.android.com/studio/command-line/adb#connect-to-a-device-over-wi-fi-android-11+步骤9
你叫adb connect后adb pair？

OK, let me study it. I just want to say that wireless connection is more convenient. thank you

I don't know if this will work for you, but after following these steps it worked!
https://www.youtube.com/watch?v=vuTdxa-w1js


Minor fixes (build passing)

Dependencies updated.
Rubocop long line complaints resolved.
Server start command in Readme updated to match convention.

Thanks for the contribution!


make dynamic tabs actually ARIA 1.1 practices compliant

A breaking change, but would like to squeeze this into v5 if we can: turn dynamic tabs into actual "Tabs with automatic activation" (see https://www.w3.org/TR/wai-aria-practices-1.1/examples/tabs/tabs-1/tabs.html and https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel /)

only the currently selected/active tab receives focus, all other tabs are not focusable (tabindex="-1" added dynamically to them)
cursor keys cycle between tabs, setting both the tabindex="0" and aria-selected="true" to the newly active tab (and tabindex="-1" / aria-selected="false" on the now not selected one)
mouse behavior can remain as now (though need to flip tabindex accordingly)
document this in the docs, referencing specifically the "automatic activation" route (so authors aren't confused/don't wonder why using SPACE or whatever does nothing)

it may even be worth making tabs a separate page/item in the navigation (and calling it "Tabs" as that's what many authors will be looking for in vain)

also, would love to (assuming it's buried in the code somewhere) remove any support for dropdowns inside dynamic tab interfaces. these are an abomination, and they don't map to any sane ARIA pattern

if not deemed too much of a breaking change, could consider backporting to v4 if reasonably straightforward...

Dear @patrickhlauke thank you so much for fixing this. Were you able to backport to v4?


[1.8] Move networkd setup to mesos unit

High-level description
Fix for networkd overlay network in coreOS. Previous fix only worked when the 'install-prereqs' feature of the dcos_installer was used, which is not a guaranteed setup step.
Corresponding DC/OS tickets (obligatory)
https://jira.mesosphere.com/browse/DCOS_OSS-2003
Checklist for all PRs

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: Updating service unit file
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee


drivers/adc: add adc drivers on it8xxx2_evb platform

This commit is about the it8xxx2 analog to digital converter
driver. Support 8 channels ch0~ch7.
Signed-off-by: Tim Lin<EMAIL_ADDRESS>

Hi @anangl,
Could you please review this request, thanks. If you have any questions or concerns, please let me know.

Hi @anangl, @galak, @kgugala, @pgielda,
Could you please review this request, thanks. If you have any questions or concerns, please let me know.

Please can you put a tag, like 'ite:' in your subject line? Or at least a consistent tag that you always use. It should not be it8xxx2_evb since that is an eval board...but this is useful for any board that uses that chip.
I cannot find your PRs at present since it seems github does not support partial search.

The tag has been added in the subject(https://github.com/zephyrproject-rtos/zephyr/pull/31417/commits/f18edf95b3a1a4b113568b277e9ae8a4843401d4),  but the subject of this PR seems not to be changed?
The PR path is as follows:
https://github.com/zephyrproject-rtos/zephyr/pull/31417


[Bug]: warn: Dropping unmatched character  (U+e745)

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

install polybar 3.5.7
install UbuntuMono NF
set a workspace name as a symbol
set up a minimal config and launch.sh

Minimal config
[bar/base]
enable-ipc = true
font-0 = UbuntuMono:size=12:antialiasing=true;
...

[module/workspaces]
type = internal/xworkspaces
...
label-focused = %icon%
...
label-unfocused = %icon%
...
label-visible = %icon%
...
label-urgent = %icon%

Polybar log
notice: pulseaudio: using default sink alsa_output.pci-0000_28_00.4.analog-stereo
notice: Loaded font "UbuntuMono:size=12:antialiasing=true" (name=Ubuntu Mono, offset=0, file=/usr/share/fonts/truetype/ubuntu/UbuntuMono-R.ttf)
warn: Dropping unmatched character  (U+f120) in '  '
warn: Dropping unmatched character  (U+e745) in '  '

Expected behavior
My bar would display the correct symbols I set as my workspace names.
Actual behavior
the bar drops the symbols and does not display them
Window Manager and Version
dkwm 1.7
Linux Distribution
Pop!_OS 22.04
Polybar version
polybar 3.5.7

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

Additional Context / Screenshots
All "fixes" in closed issues have been attempted and been unsuccessful

notice: Loaded font "UbuntuMono:size=12:antialiasing=true" (name=Ubuntu Mono, offset=0, file=/usr/share/fonts/truetype/ubuntu/UbuntuMono-R.ttf)

You're not loading Ubuntu Mono Nerd Font, you are loading the regular Ubuntu Mono (which doesn't have any of the nerd fonts characters).
Please read the font debugging guide.


el6 not working in vagrant

EL6 not working with Vagrant
Description of problem

What did you do?

vagrant up el6-agent

What happened?

errors

What did you expect to happen?

The VM to come up without errors

How can someone reproduce the problem?

vagrant up el6-agent
Command used and debugging output
$ vagrant up el6-agent

Bringing machine 'el6-agent' up with 'virtualbox' provider...
==> el6-agent: Checking if box 'centos/6' is up to date...
==> el6-agent: Clearing any previously set forwarded ports...
==> el6-agent: Fixed port collision for 22 => 2222. Now on port 2203.
==> el6-agent: Clearing any previously set network interfaces...
==> el6-agent: Preparing network interfaces based on configuration...
    el6-agent: Adapter 1: nat
    el6-agent: Adapter 2: hostonly
==> el6-agent: Forwarding ports...
    el6-agent: 22 (guest) => 2203 (host) (adapter 1)
==> el6-agent: Running 'pre-boot' VM customizations...
==> el6-agent: Booting VM...
==> el6-agent: Waiting for machine to boot. This may take a few minutes...
    el6-agent: SSH address: <IP_ADDRESS>:2203
    el6-agent: SSH username: vagrant
    el6-agent: SSH auth method: private key
    el6-agent: Warning: Connection reset. Retrying...
    el6-agent: Warning: Remote connection disconnect. Retrying...
    el6-agent: Warning: Connection reset. Retrying...
    el6-agent: Warning: Remote connection disconnect. Retrying...
==> el6-agent: Machine booted and ready!
[el6-agent] No installation found.
Loaded plugins: fastestmirror, security
Setting up Install Process
Determining fastest mirrors
 * base: mirror.ash.fastserv.com
 * extras: mirror.ash.fastserv.com
 * updates: repos-tx.psychz.net
Package kernel-devel-2.6.32-754.2.1.el6.x86_64 already installed and latest version
No package kernel-devel-2.6.32-696.28.1.el6.x86_64 available.
Package gcc-4.4.7-23.el6.x86_64 already installed and latest version
Package binutils-<IP_ADDRESS>.2-5.48.el6.x86_64 already installed and latest version
Package 1:make-3.81-23.el6.x86_64 already installed and latest version
Package 4:perl-5.10.1-144.el6.x86_64 already installed and latest version
Package bzip2-1.0.5-7.el6_0.x86_64 already installed and latest version
Nothing to do
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
Installing Virtualbox Guest Additions 5.2.12 - guest version is unknown
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.12 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.12 of VirtualBox Guest Additions...
You may need to restart your guest system to finish removing the guest drivers.
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
    kernel-devel kernel-devel-2.6.32-696.28.1.el6.x86_64
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
    kernel-devel kernel-devel-2.6.32-696.28.1.el6.x86_64
An error occurred during installation of VirtualBox Guest Additions 5.2.12. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
    kernel-devel kernel-devel-2.6.32-696.28.1.el6.x86_64
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> el6-agent: Checking for guest additions in VM...
    el6-agent: No guest additions were detected on the base box for this VM! Guest
    el6-agent: additions are required for forwarded ports, shared folders, host only
    el6-agent: networking, and more. If SSH fails on this machine, please install
    el6-agent: the guest additions and repackage the box to continue.
    el6-agent:
    el6-agent: This is not an error message; everything may continue to work properly,
    el6-agent: in which case you may ignore this message.
==> el6-agent: Setting hostname...
==> el6-agent: Configuring and enabling network interfaces...
    el6-agent: SSH address: <IP_ADDRESS>:2203
    el6-agent: SSH username: vagrant
    el6-agent: SSH auth method: private key
==> el6-agent: Mounting shared folders...
    el6-agent: /vagrant => /Users/gh/git/sensu-puppet
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=500,gid=500 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

Platform and version information
MacOS High Sierra
Vagrant - 2.1.2
VirtualBox - 5.2.12 r122591

This looks like an issue with the centos/6 box being built for 6.9 and latest is now 6.10.  Fix is hopefully temporary until CentOS updates the box for 6.10.

vagrant up el6-agent
failure
vagrant ssh el6-agent
sudo su -
yum update kernel\*
Exit out of VM
vagrant reload el6-agent
Success

Thanks for the steps to fix!


Add Chocolatey command to gohugo.io

At the bottom of the home page under install the site says "Using HomeBrew?" and then shows a home brew command for installing it.
There is also a chocolatey package maintained for hugo, so you could also have:
Using Chocolatey?
"choco install hugo -confirm"

Thanks for the heads up -- I notice that Hugo 0.19 is already available there, which means someone actually maintains that package, which is fantastic! Last time I had a look Chocolatey was a few versions behind.
https://chocolatey.org/packages/hugo

@bep - fyi you can also request to be the package maintainer and then integrate the chocolatey package generation into your CI.

@budparr already added this command in this redesign of the homepage that is likely to be deployed soon. Shall we close it then?

I'm closing this -- and people arguing that "it's not fixed on the live site": This is analogue to doing code changes to master: It is fixed, but not released yet.


Prisma doesn't accept json field paths when trying to order by json field.

Bug description
I'm trying to order my data by a value of a field in a json column, but Prisma doesn't accept the path structure that where accepts. It seems that this feature of PostgreSQL is not supported yet.
How to reproduce
Just write a query that tries to pass a path to the orderBy parameter (there is no such parameter).
Expected behavior
I expect it to work as it works with json filtering. Something like:
orderBy: {
    myJsonField: {
        path: ["foo", "bar"],
        orderDirection: "asc"
    },
}

Prisma information
You can try this with any json field.
Environment & setup

OS: Windows
Database: PostgreSQL
Node.js version: v14.18.1

Prisma Version
3.5.0

This would be an incredibly useful feature, found this which includes some useful info for possible implementation or workaround: https://jianjye.com/articles/32/how-to-sort-mysql-json-data-correctly

This would be an incredibly useful feature, found this which includes some useful info for possible implementation or workaround: https://jianjye.com/articles/32/how-to-sort-mysql-json-data-correctly

This is for MySQL though. What I'm thinking about is to add a regular SQL query builder and feed its result to the raw sql query option in Prisma while I'm waiting for this.

@janpio do you have a ballpark ETA for this feature?

No. Right now this is not a priority, which does not mean it might not be picked up by a team soon and solved. But no time to communicate.

What I'm thinking about is to add a regular SQL query builder and feed its result to the raw sql query option in Prisma while I'm waiting for this.

@adam-arold I had the same idea, Sequelize seems to be the only builder with a cast method (I am using MySQL with PlanetScale). However I'm at a very early stage with my project so would prefer to wait on this feature if it is planned to avoid the extra work of maintaining two schemas.

@adam-arold did you find any sort of workaround for this?
I have a scenario where I need to sort data by a postgres json field as well.

@adam-arold did you find any sort of workaround for this? I have a scenario where I need to sort data by a postgres json field as well.

Yep. Moved away from Prisma. 😂

Not the answer I was hoping for 🙈 but appreciate it anyway!
+1 for this request

Not the answer I was hoping for 🙈 but appreciate it anyway! +1 for this request

Yeah, I was upset too, but I've come to the realization that most drivers are good enough that I can use them as-is or create adapters around them.

+1 for this request

+1

Any news about this missing feature ?

+1, really need this

It seems to me a must to have feature

+1, my project also needs this

+1, need this

+1, want this

+1

+1, this would be really helpful

+1

+1

+1

+1

+1

+1

I have a similar issue, but with by from groupBy instead of orderBy. I guess this is related, or is there some way to group by a JSON field without a raw query?

Two years later, this feature is still needed...

We kept prisma as migration engine, and are moving to kysely as query builder. Happened to many times that prisma was standing between me and getting work done

Totally agree with what's been mentioned before. There have been too many times when it just gets in the way of actually getting things done. So, I've decided to create a task to replace Prisma entirely.
When it's working, it's excellent. But for more complex projects, it just has too many restrictions.

Any update...?

It's understandably confusing as to why there's filter support but not sort support for even just top level json objects, it just seems feature incomplete. Are there any plans or progress being made in this effort? or at least a justification beyond "it's not a priority"? Thanks.

Can someone of the prisma team give us a comment. just to checking that some read our comments.

We read all comments. There is currently no plan to work on this in the immediate future, we have many other issues and are working on these. We are doing our best to balance that, but in this case it means this issue is currently not getting the attention some of you would prefer, sorry. We will update here when this changes.

Thanks!
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
14/06/24,
06:15:19 p.m.
On Fri, 14 Jun 2024 at 18:06, Jan Piotrowski @.***>
wrote:

We read all comments. There is currently no plan to work on this in the
immediate future, we have many other issues and are working on these. We
are doing our best to balance that, but in this case it means this issue is
currently not getting the attention some of you would prefer, sorry. We
will update here when this changes.
—
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/10346#issuecomment-2167482827,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6JPJ3PWKUONIGBJ22HAS3ZHKQBJAVCNFSM5ILYOC7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJWG42DQMRYGI3Q
.
You are receiving this because you commented.Message ID:
@.***>

I am very shocked this is still not implemented almost 3 years since it is raised


[17] Revert start-of-cycle scaling

Context
To handle increased activity on Apply on the first few days of the start of cycle, we increased the number of web replicas and the database CPU.
Changes proposed in this pull request
Revert back to normal now that activity is again at normal levels
Guidance to review
We will need to arrange for down time when this is merged.
Things to check

[x] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[x] API release notes have been updated if necessary
[x] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[x] Required environment variables have been updated added to the Azure KeyVault
[x] Inform data insights team due to database changes
[x] Make sure all information from the Trello card is in here
[x] Rebased main
[x] Cleaned commit history
[x] Tested by running locally
[x] Add PR link to Trello card

 Revert start-of-cycle scaling in Apply

Will this actually cause segnificant downtime? I'm not very familiar to what's going to happen, K8s magic

This one won't actually cause any downtime at all. I forgot to update the description. Downscaling the db would cause downtime, but we've decided not to do that. The web replicas change won't cause downtime. Just in case, I'll merge early in the morning.


Lint "build" code in addition to "src" code.

I'd like to see the root *.js and tools/*.js files get linted, using ES5 rules.

Good point. This brings a bigger question: Should the build code be in ES6 for consistency? I lean toward yes. Could use babel-node to compile it.

That would be great. node -r babel-register ./script is how I've been doing it with babel 6.

Build code is now being linted. I'll open a separate issue for tracking upgrading the build scripts to ES6. Thanks for the linting suggestion!


GitHub repo description and URL

The description only mentions PNG, when this plugin can accept PNG/JPG/SVG.
Also the URL is not real/valid.

Thank you, I didn't realize it.


Fixed getObject path parsing issue

Closes #2131
Fixed getObject path parsing issue.
Is this a breaking change (Yes/No):
No

Since the unit tests are also passing, there should be no problem.


SVGs don't handle scaling properly

I've been trying to add an SVG as a border in one of my apps. In trying to do so I realized that this plugin doesn't seem to handle scaling properly. On iOS it preserves the aspect ratio. On Android it scales the SVG, but leaves some space. I've put a link to a sample project below that just shows a simple rectangle SVG and how it is very different on both iOS and Android. It also shows that when I use AbsoluteLayout, there is some space on Android. I think it makes sense for this plugin to respect the preserveAspectRatio attribute for scaling and handle it the same on both platforms.
https://drive.google.com/file/d/0B68aZqcn2sxXS2Z6bWRZOFFfTk0/view?usp=sharing

Have crated a PR for this https://github.com/paulpatarinski/Xamarin.Forms.Plugins/pull/116 hopefully Paul will merge soon in mean time am using local nuget package.

Thanks @mannyvw for creating the PR. @paulpatarinski, could you release a new NuGet Package with this fix soon? Currently all SVG images are not preserving there aspect ratio on Android.

Oh, I have found a solution for my aspect ratio problem on Android. Just set HorizontalOptions and VerticalOptions to Center:
        new SvgImage {
            SvgAssembly = typeof(App).GetTypeInfo().Assembly,
            SvgPath = "logo.svg",
            WidthRequest = 178,
            HeightRequest = 22,
            HorizontalOptions = LayoutOptions.Center,
            VerticalOptions = LayoutOptions.Center,
        };


problem with deploy url build

i m deploying my app through

ng build --env=prod --prod --aot --build-optimizer --deploy-url //-distribution-.cloudfront.net/ --output-hashing none --nosourcemap

after build in dist/index.html

it only produces single '/' for scripts.bundle.js why???

Heya, I tried doing ng build --deploy-url //-distribution-.cloudfront.net/ on the latest version (1.5.0-beta.2) and this is what I got in index.html:
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>MasterProject</title>
  <base href="/">

  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="icon" type="image/x-icon" href="favicon.ico">
</head>
<body>
  <app-root></app-root>
<script type="text/javascript" src="//-distribution-.cloudfront.net/inline.bundle.js"></script><script type="text/javascript" src="//-distribution-.cloudfront.net/polyfills.bundle.js"></script><script type="text/javascript" src="//-distribution-.cloudfront.net/scripts.bundle.js"></script><script type="text/javascript" src="//-distribution-.cloudfront.net/styles.bundle.js"></script><script type="text/javascript" src="//-distribution-.cloudfront.net/vendor.bundle.js"></script><script type="text/javascript" src="//-distribution-.cloudfront.net/main.bundle.js"></script></body>
</html>

So I don't see the single slash here. Can you provide more details including a way to reproduce?

i don't know why it produced but i correct it out by replacing //-distribution-.cloudfront.net/  with https://-distribution-.cloudfront.net/ in ng build command

Glad to hear you have it sorted then 👍

hi @filipesilva  sir, i was encountered with  same problem of getting  single slash after deploying,  then i figured out that my project's package.json contains angular-cli of version ^1.4.2 but on my machine it is 1.4.3 globally installed after that i degarade it 1.4.2  and update my nodejs to 8.6.0 then build produce results that i wanted. Sir can you suggest me any reference to clear my doubts on these things i did above how these are connected to angular build or you state me how these are connected .

@ajit-jain I'm sorry, but I don't quite understand what you are trying to say. Did you find a way to reproduce this problem? If you have, I'll reopen the issue to investigate.
Can you setup a minimal repro please? You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.


Fix environment variable persistence

Closes #60
I added test in the most appropriate place I could think of and verified the test fails without the fix.
All other specs pass locally.

Coverage decreased (-1.0%) to 93.885% when pulling 7f16d2fb82edd3993186212ccb5fd067e3c2fb49 on DannyBen:fix-env-vars-persistence into 1f0777df14c82444bec0d973b595091002023111 on piotrmurach:master.

Would you have time to...

Yes. Stand by :)

Pulled and merged upstream master
Added changelog entry
Resolved all but one Hound complaints
Simplified the spec to compare only to the part of the string we care about


[Stream] Teach allocation of encoding to take bcast map into account.

The bcast_map represents the iteration domain mapping from the source of dispatch to matmul. So it uses bcast_map in getMapForOperandIndex() when it is present.

@benvanik you can ignore the PR because it is not merging into main. We're using a remote branch to brainstorm what's needed in encodings.

@Max191 I'm thinking that we can just replace the corresponding indexing_map with the bcast_map now.. We can look at details after we have an e2e example.

oh, there is a bug in the indexing map, fixing...

I'm thinking that we can just replace the corresponding indexing_map with the bcast_map now.. We can look at details after we have an e2e example.

So I think we only need the composed indexing_map, see the changes in the PR.


Program freezes on Combat_Crit.xnb

Program does not extract any file, freezing from the start, at Combat_Crit.xnb file.

Can confirm. Ran into the problem on my Mac, and Java spat out this to the terminal window I was using:
Exception in thread "Thread-1" ai: unsupported asset type: ReLogic.Graphics.DynamicSpriteFontReader
	at aj.a(Unknown Source)
	at L.a(Unknown Source)
	at L.a(Unknown Source)
	at L.a(Unknown Source)
	at Q.run(Unknown Source)

All you need to do is go and find your Terraria\Content file, and temporarely re-place your Fonts folder to somewhere else.


startup polygon mask

Implementing this https://github.com/VincentGarreau/particles.js/pull/202

this code is actually untested

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 18

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 7

See the complete overview on Codacy


Examples tables

Unexpanded Scenario Outlines and Examples tables
This PR adds support for rendering unexpanded Scenario Outlines and their Examples tables in the HTML reports. Included also is a fix for issue #40 which was necessary to include here to ensure that the < and > parameter delimiters in outline templates are escaped and rendered correctly.
Sample snapshot below:

Build and tests passed but requires pass phrase.


All the countries in the world organised by largest population to smallest.

select Name, Population
from country
order by population DESC


feat: add searchIcon prop to lookup component

feat: #775
Changes proposed in this PR:

add searchIcon prop to make component more customizable

[ ] I have followed (at least) the PR section of the contributing guide.
@90milesbridge/tigger

Pull Request Test Coverage Report for Build 3069

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 80.996%

Totals

Change from base Build 3059:
0.02%

Covered Lines:
2666

Relevant Lines:
3181

💛  - Coveralls


Create example-redis-config.yaml

resolves #44794

Hello @dipesh-rawat Please Check I have created the example-redis-config.yaml regarding the issue on #44794

/retitle [hi] Add example yaml files for "Configuring Redis using a ConfigMap" tutorial

Hello @dipesh-rawat Please check I have added the redis-pods.yaml


KAFKA-4333: Report coordinator id of consumer groups with consumer group '--list' option

Enhance the output of the consumer group command and report the coordinator id of each group (for Java API based consumers) when --list option is used.

KIP-175 addresses reporting the coordinator id. Closing the PR.


How to use multiple GPUs for training?

Hi @ssxxx1a!
We have not experimented with multi-GPU training, and currently it is not supported.
While I might add this feature in the future, feel free to open a PR in case you look further into it.


any trick to "jump to previous desktop"?

I am a new chunkwm/skhd user coming from linux + i3.
Is there any functionality Ii can put together to "jump back to previous desktop"?  I used this quite a bit with i3; it was the workspace_auto_back_and_forth functionality.
https://i3wm.org/docs/userguide.html#workspace_auto_back_and_forth
Is there anyway to bind something to "jump to previous desktop" with skhd and chunkwm?
workspace_auto_back_and_forth yes
bindsym $mod+z workspace back_and_forth

Thanks in advance,

You can use the following, if you have chunkwm-sa installed:
cmd + alt - z : chunkc tiling::desktop --focus $(chunkc get _last_active_desktop)

I had a solution that did not require chunkwm-sa, but I don't have that available.
You might find it if you look through the history of the sample config in this repo.


update to 019.1rc7

Update to latest daemon RC for next app RC.
We'll upgrade to 0.19.1 final release once all goes well.

Closing, 0.19.1 is out


[orgmode] hide / disable a post

Is there  way to temporarily disable a post if you have not finished writing it yet ?
I have been failing to find an option.

You can hide a post using the draft tag: https://getnikola.com/handbook.html#drafts (this is not specific to the orgmode plugin)


TSLint 4 support

and more dependencies updated, now uses @types/... instead of typings.
Formatted files with updated formatter/typescript.
Requires TSLint 4 as a peer dependency, so this is a breaking change.

Fixes #2.


python312Packages.craft-application: unpin pygit2

Description of changes
fixes the build of snapcraft

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335906 run on x86_64-linux 1

4 packages marked as broken and skipped:

python311Packages.craft-application
python311Packages.craft-application.dist
python312Packages.craft-application
python312Packages.craft-application.dist

6 packages built:

charmcraft
charmcraft.dist
rockcraft
rockcraft.dist
snapcraft
snapcraft.dist

Thanks @dotlambda! This doesn't seem to build, though I don't think that's because of this patch. It seems that craft-parts was also updated in such a way that it's now marked broken.
I can make the builds succeed with the following patch:
diff --git a/pkgs/development/python-modules/craft-application/default.nix b/pkgs/development/python-modules/craft-application/default.nix
index 04c488586c9e..a8944f6ac93a 100644
--- a/pkgs/development/python-modules/craft-application/default.nix
+++ b/pkgs/development/python-modules/craft-application/default.nix
@@ -2,27 +2,35 @@
   lib,
   stdenv,
   buildPythonPackage,
-  craft-archives,
-  craft-cli,
-  craft-grammar,
-  craft-parts,
-  craft-providers,
   fetchFromGitHub,
   git,
-  hypothesis,
   nix-update-script,
-  pydantic-yaml,
-  pyfakefs,
-  pygit2,
-  pytest-check,
-  pytest-mock,
-  pytestCheckHook,
+  python3,
   pythonOlder,
-  pyyaml,
-  responses,
-  setuptools-scm,
-  snap-helpers,
 }:
+let
+  python = python3.override {
+    self = python;
+    packageOverrides = self: super: {
+      pydantic-yaml = super.pydantic-yaml.overridePythonAttrs (old: rec {
+        version = "0.11.2";
+        src = fetchFromGitHub {
+          owner = "NowanIlfideme";
+          repo = "pydantic-yaml";
+          rev = "refs/tags/v${version}";
+          hash = "sha256-AeUyVav0/k4Fz69Qizn4hcJKoi/CDR9eUan/nJhWsDY=";
+        };
+        dependencies = with self; [
+          deprecated
+          importlib-metadata
+          pydantic_1
+          ruamel-yaml
+          types-deprecated
+        ];
+      });
+    };
+  };
+in

 buildPythonPackage rec {
   pname = "craft-application";
@@ -43,14 +51,14 @@ buildPythonPackage rec {
       --replace-fail "setuptools==70.1.0" "setuptools"
   '';

-  build-system = [ setuptools-scm ];
+  build-system = with python.pkgs; [ setuptools-scm ];

   pythonRelaxDeps = [
     "pygit2"
     "requests"
   ];

-  dependencies = [
+  dependencies = with python.pkgs; [
     craft-archives
     craft-cli
     craft-grammar
@@ -62,7 +70,7 @@ buildPythonPackage rec {
     snap-helpers
   ];

-  nativeCheckInputs = [
+  nativeCheckInputs = with python.pkgs; [
     git
     hypothesis
     pyfakefs
diff --git a/pkgs/development/python-modules/craft-parts/default.nix b/pkgs/development/python-modules/craft-parts/default.nix
index 2ad66a7d4a75..f14d20c7e725 100644
--- a/pkgs/development/python-modules/craft-parts/default.nix
+++ b/pkgs/development/python-modules/craft-parts/default.nix
@@ -1,28 +1,36 @@
 {
-  lib,
   buildPythonPackage,
   fetchFromGitHub,
-  nix-update-script,
-  overrides,
-  pydantic_1,
-  pydantic-yaml,
-  pyxdg,
-  pyyaml,
-  requests,
-  requests-unixsocket,
-  urllib3,
-  pytestCheckHook,
-  pytest-check,
-  pytest-mock,
-  pytest-subprocess,
-  requests-mock,
-  hypothesis,
   git,
+  lib,
+  nix-update-script,
+  python3,
   squashfsTools,
-  setuptools-scm,
   stdenv,
 }:
-
+let
+  python = python3.override {
+    self = python;
+    packageOverrides = self: super: {
+      pydantic-yaml = super.pydantic-yaml.overridePythonAttrs (old: rec {
+        version = "0.11.2";
+        src = fetchFromGitHub {
+          owner = "NowanIlfideme";
+          repo = "pydantic-yaml";
+          rev = "refs/tags/v${version}";
+          hash = "sha256-AeUyVav0/k4Fz69Qizn4hcJKoi/CDR9eUan/nJhWsDY=";
+        };
+        dependencies = with self; [
+          deprecated
+          importlib-metadata
+          pydantic_1
+          ruamel-yaml
+          types-deprecated
+        ];
+      });
+    };
+  };
+in
 buildPythonPackage rec {
   pname = "craft-parts";
   version = "1.33.0";
@@ -38,14 +46,15 @@ buildPythonPackage rec {

   patches = [ ./bash-path.patch ];

-  build-system = [ setuptools-scm ];
+  build-system = with python.pkgs; [ setuptools-scm ];

   pythonRelaxDeps = [
+    "pydantic-yaml"
     "requests"
     "urllib3"
   ];

-  dependencies = [
+  dependencies = with python.pkgs; [
     overrides
     pydantic_1
     pydantic-yaml
@@ -58,7 +67,7 @@ buildPythonPackage rec {

   pythonImportsCheck = [ "craft_parts" ];

-  nativeCheckInputs = [
+  nativeCheckInputs = with python.pkgs; [
     git
     hypothesis
     pytest-check
@@ -105,7 +114,7 @@ buildPythonPackage rec {
   passthru.updateScript = nix-update-script { };

   meta = {
-    broken = lib.versionAtLeast pydantic-yaml.version "1";
+    broken = lib.versionAtLeast python.pkgs.pydantic-yaml.version "1";
     description = "Software artifact parts builder from Canonical";
     homepage = "https://github.com/canonical/craft-parts";
     changelog = "https://github.com/canonical/craft-parts/releases/tag/${version}";

Happy to push to this PR with a couple of commits if you'd like, or perhaps there is a better solution I'm missing?
(Thankfully, the crafts are pretty close to moving to pydantic >= 2, which will stop a lot of the version shenanigans)

Overrides are not allowed within python3Packages. This PR fixes snapcraft etc.


Update all connected gates

Refactor function to update all connected gates from starting list of gates

Moved to gate module


fix: adr linting

Description
Fixing the CI issue https://github.com/Amzani/shapeup/pull/40

/rtm


Return an empty string as the only 'example' for an empty regex

Coverage remained the same at 100.0% when pulling 53ae0542600b24562844413cf30707abae38452b on fix_empty_regex_examples into 28000d3a52762dda981db0aa139efe150b161381 on master.


Enable watch option for relay-compiler

Is this work for you? I try to run yarn relay --watch or and it always ends.`

Yes, it does work for me


Perhaps CSS imports from PDF module don't work

At least, in the todo app, they don't seem to work anymore

Actually, this is due to {#bundle/} which generates a screen CSS import:
      <link rel="stylesheet" media="screen" href="/static/bundle/main-LH23AIE5.css" />

@ia3andy are you sure this is the right thing to do? It won't get loaded when doing PDF rendering.

Actually, this is due to {#bundle/} which generates a screen CSS import:
      <link rel="stylesheet" media="screen" href="/static/bundle/main-LH23AIE5.css" />

@ia3andy are you sure this is the right thing to do? It won't get loaded when doing PDF rendering.
I don't know why I added this 🤔 but yes we should remove this!


docs: fix links to archived versions

What kind of change does this PR introduce? Documentation fix
Did you add tests for your changes? N/A
If relevant, did you update the documentation? Yes
Summary
In the documentation site, fix the following links to the archived versions.

In the top right menu, the links to these versions were broken since the condition parts[0] <= 19 && parts[1] <= 2 && parts[2] <= 2 is false when any number > 3. I switched it to use the semver library, which is already used in generate_docs.ts.

18.0.5
18.0.4
18.0.3
17.1.3
15.5.0
15.4.2
15.4.1
15.4.0
15.3.2
15.3.1
15.3.0

In the Chromium Support page https://pptr.dev/chromium-support the links to these versions were broken.

20.0.0 and above, since https://pptr.dev/20.0.0 isn't working

from 19.4.0 to 19.8.0, since the git tag in the url was v19.8.0 instead of puppeteer-v19.8.0

15.1.0 was not linked since the checks were on < 15.0.0 and >= 15.3.0

New screenshot from running locally:

Does this PR introduce a breaking change? No
Other information

Fixed in https://github.com/puppeteer/puppeteer/pull/11136


lld cannot use libstdc++.so.6: cannot open shared object file: No such file or directory

Describe the bug
llvm-tblgen can not find libstdc++.so.6.
FAILED: include/llvm/IR/Attributes.inc <llvm-project>/llvm-project/build/include/llvm/IR/Attributes.inc
cd <llvm-project>/llvm-project/build && <llvm-project>/llvm-project/build/bin/llvm-tblgen -gen-attrs -I <llvm-project>/llvm-project/llvm/include/llvm/IR -I<llvm-project>/llvm-project/build/include -I<llvm-project>/llvm-project/llvm/include <llvm-project>/llvm-project/llvm/include/llvm/IR/Attributes.td --write-if-changed -o include/llvm/IR/Attributes.inc -d include/llvm/IR/Attributes.inc.d
<llvm-project>/llvm-project/build/bin/llvm-tblgen: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Confirmed that g++/clang++ can generate correct minimal C++ binary (with libstdc++), but recently llvm-tblgen breaks.
Steps To Reproduce
Steps to reproduce the behavior:

Use recent nixpkgs/nixos-unstable
build the llvm-project

LLVM Revision: d768b97424f9e1a0aae45440a18b99f21c4027ce
Flags:

LLVM=~llvm-project

llvm_base="$LLVM"
build_mode="Debug"
build_dir="build"
build_base="${llvm_base}/${build_dir}"
llvm_enable_projects="clang;mlir"

cmake -DBUILD_SHARED_LIBS:STRING=On \
-DCMAKE_BUILD_TYPE:STRING=${build_mode} \
-DLLVM_APPEND_VC_REV:STRING=Off \
-DLLVM_ENABLE_LLD:STRING=On \
-DLLVM_ENABLE_PROJECTS:STRING="${llvm_enable_projects}" \
-DLLVM_LINK_LLVM_DYLIB:STRING=Off \
-DLLVM_OPTIMIZED_TABLEGEN=Off \
-DLLVM_CCACHE_BUILD:BOOL=FALSE \
-DLLVM_USE_SPLIT_DWARF=On \
-DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE \
-DCMAKE_C_COMPILER:FILEPATH=${CC:-"gcc"} \
-DCMAKE_CXX_COMPILER:FILEPATH=${CXX:-"g++"} \
-S${llvm_base}/llvm \
-B${build_base} -G Ninja \
-DLLVM_TARGETS_TO_BUILD="host;RISCV;"

Expected behavior
Compile LLVM successfully as before
Notify maintainers
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.9, NixOS, 23.05 (Stoat), 23.05.20230206.5a350a8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

According to some of my local tests, -DLLVM_ENABLE_LLD is important to reproduce. BFD linker gives me other warnings:
[user@system:~]$ cmake --build build
[313/5616] Linking CXX executable bin/not
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[328/5616] Linking CXX executable bin/UnicodeNameMappingGenerator
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[331/5616] Linking CXX executable bin/split-file
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[333/5616] Linking CXX executable bin/yaml-bench
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[529/5616] Linking CXX executable bin/FileCheck
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[553/5616] Linking CXX executable bin/llvm-tblgen
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
[594/5616] Linking CXX executable bin/clang-tblgen
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: librt.so.1, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)
/nix/store/r2b9k28c6aghczpqfvh71y9xavm7rr68-binutils-2.39/bin/ld: warning: libdl.so.2, needed by lib/libLLVMSupport.so.17git, not found (try using -rpath or -rpath-link)

CC @Ericson2314

Working fine with following shell.
with import <nixpkgs> { };
pkgs.clangStdenv.mkDerivation {
  name = "test";
  nativeBuildInputs = with pkgs; [
    lld
  ];
}

Working fine with following shell.
with import <nixpkgs> { };
pkgs.clangStdenv.mkDerivation {
  name = "test";
  nativeBuildInputs = with pkgs; [
    lld
  ];
}

I made a nix flake that reproduces this problem:
{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    flake-utils.url = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, flake-utils, ... }@inputs:
    flake-utils.lib.eachDefaultSystem (system:
      let
        pkgs = import nixpkgs { inherit system; };
      in
      {
        devShells.default = pkgs.mkShell
          {
            nativeBuildInputs = with pkgs; [
              clang_14
              lld_14
            ];
          };
      });
}

https://gist.github.com/inclyc/8df38510fd141965da238c6d4d6edeca

CC maintainers: @Ericson2314 @sternenseemann @lovek323 @dtzWill @primeos

Does staging-next branch work for you? Chances are it is fixed by https://github.com/NixOS/nixpkgs/pull/213185

Does staging-next branch work for you? Chances are it is fixed by #213185

Happy to test whether the current staging-next branch nixpkgs would solve the issue. However, after I switch to staging-next, lld_14 and clang_14 need to compile a lot of packages when I tried to enter nix develop shell. Is there any way to speed up the compilation? The solutions I think of are: increase the number of parallel compilations? , looking for binaryCache for staging-next?

increase the number of parallel compilations

nix develop compiles the required dependencies almost sequentially, and a lot of time is spent on "configuring xx, checking for xxx" on a single core. Is there any way to increase the scale of parallelism? (I've set big-parallel option).

nix develop -j <N> should increase job parallelism. nix develop --cores <N> should increase build parallelism within a job. If you want to build less you can sync to latest commit hydra already built for staging-next. For https://hydra.nixos.org/jobset/nixpkgs/staging-next looks like 123c88b is reasonably complete.

Came upon the same error down to the minimal repro when trying to build llvm with nix-provided mold.
[nix-shell:~/repos/llvm-project]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.0-119-generic, Ubuntu, 22.04.4 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.1`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Should I open an issue?


feat: add democase for vxbtn, vxbtngroup, vxchip

PR needs rebase.

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


Use case where resize doesn't happen

Hi,
I have a typical setup (crossdomain) where everything works as expected. Illustration:

Initialize IFrame to a.html
a.html hyperlinks to b.html
Resize is triggered uppon loading b.html, test OK

Both a.html and b.html load up iframeResizer.contentWindow js.
But in this particular case it fails:

Initialize IFrame to a.html
a.html hyperlinks to diagram.svg
diagram.svg hyperlinks to b.html
Resize for b.html is not triggered, test NOK.

I get no error logs from iFrameSizer after loading b.html. iframeResizer.contentWindow.js is loaded for b.html.
Is there anyway to solve this?
Thanks for the help.

What version are you using? When b.html loads it should fire the onLoad event on the parent page and the most recent version, as a backup, b.html will also send the parent a message saying it has loaded.

I'm using v3.5.5.
The target application is quite peculiar.. I did some JS code changes on the target and it seems to be to be triggering correctly. I do get sometimes an issue where the iframe is refreshed and the resize is only triggered some seconds after (but i'ts rare).
Also, i'm loading the contentWindow.js with Javascript and not declarative, which also can have some side effects.
So i guess this is a non issue.
Just a quick question, if i want to "force" a resize from the target site, I should do this? :
parentIFrame.size();
Thanks for the help.

Yep, but wrap it in a test for parentIFrame, in case the page loads outside the iFrame


[Snyk] Security upgrade grafana/grafana from 8.5.16 to 8.5.20

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

docker/grafana/Dockerfile

We recommend upgrading to grafana/grafana:8.5.20-ubuntu, as this image has only 24 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

471
CVE-2023-0215 SNYK-ALPINE315-OPENSSL-3314621
No Known Exploit

571
CVE-2023-0286 SNYK-ALPINE315-OPENSSL-3314622
No Known Exploit

221
CVE-2022-4304 SNYK-ALPINE315-OPENSSL-3314628
No Known Exploit

567
CVE-2022-4450 SNYK-ALPINE315-OPENSSL-3314629
No Known Exploit

567
CVE-2022-4450 SNYK-ALPINE315-OPENSSL-3314629
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

:tada: This PR is included in v1.6.0 :tada:


Specify depth level for opening at start

Hi,
Thanks for this brilliant package.
I'm displaying JSON data from an API. The base structure of every successful response is this:
{
  "result": {},
  "stat": "ok"
}

I'd like the JsonView to open just one level at startup, so the first level of the result object can be seen.
For example:
Depth 0:
{
  "result": { ... },
  "stat": "ok"
}

Depth 1 (what I want):
{
  "result": {
    "breakfast": { ... },
    "lunch": { ... },
    "dinner": { ... }
  },
  "stat": "ok"
}

Depth 2:
{
  "result": {
    "breakfast": {
      "food": "Cereal",
      "drink": "Milk"
    },
    "lunch": {
      "food": "Sandwiches",
      "drink": "Juice"
    },
    "dinner": {
      "food": "Steak",
      "drink": "Wine"
    }
  },
  "stat": "ok"
}

etc.

great idea! I will add this feature😆

@hacker1024  version 0.4.0 has been released !
now can set default open depth in JsonConfigData , JsonView or JsonViewBody
and i will close this issue for now.

ConfigData

JsonConfigData(
  style: JsonStyleScheme(
    depth: 2,
  ),
)

JsonView

            JsonView(
              styleScheme: JsonStyleScheme(depth: 2),
              json: getJsonData(),
            ),

JsonViewBody

            JsonViewBody(
              styleScheme: JsonStyleScheme(depth: 2),
              json: getJsonData(),
            ),


VIAF and Dates

Its seems that VIAF and birth and death dates can override one another. If I enter a VIAF number and save, and then enter random birth and death dates, the VIAF disappears. If I enter birth and death dates and save, and then enter a random VIAF, the birth and death dates disappear. This is a problem because some of the dates in VIAF are incorrect, but we still want to retain the VIAF link.

I think this is really a duplicate of #29, but I'm going to leave it open because I would like you to confirm that the VIAF + date behavior is workable.
Right now, if you add a VIAF id it will populate the birth and death dates from the VIAF record.  (This can actually happen two different ways: when you pick an item from the autocomplete or if you save a record with a VIAF id but no dates, the backend code will try to look up the dates and set them.  This is a result of the change to support searching on VIAF number, because previously the birth and death dates weren't available in the autocomplete data.)
This behavior only happens when you change the VIAF id using the autocomplete.  So if you associate a person with a VIAF id and then correct the dates, they will not be changed (unless you do the VIAF lookup again).
As we discussed before, for the import script #14, any dates in the xml will be used - the VIAF lookup is only used when a person has a VIAF id but no birth/death dates.

I checked with @elspethgreen and she thought this was fine at the meeting, but she will check in with @jkotin that this functionality is OK.

Checked with Josh, he says it's okay!


crc status should provide information on the preset used

I've restarted an instance of OpenShift Local. No idea what is the preset
crc status should provide information on the preset used

@slemeur we don't expose the preset as part of human readable status but it is part of json which is used by the tools ( like podman desktop and VS extensions). To end user if they use the podman preset then there would be no openshift version as part of status and for microshift/okd/openshift preset there is openshift version and that is what user more interested if the openshift is running or not and api is accessible instead preset. preset is important on tooling side so it is part of json output.
$ ./crc status -ojson
{
  "success": true,
  "crcStatus": "Running",
  "openshiftStatus": "Running",
  "openshiftVersion": "4.12.9",
  "diskUsage":<PHONE_NUMBER>2,
  "diskSize":<PHONE_NUMBER>6,
  "cacheUsage":<PHONE_NUMBER>03,
  "cacheDir": "/home/prkumar/.crc/cache",
  "ramSize":<PHONE_NUMBER>,
  "ramUsage":<PHONE_NUMBER>,
  "preset": "openshift"
}

The preset is inferred from the message like: OpenShift version and the
statements around this, or Podman version.
We discussed to specifically add some clarity by stating Microshift V4.13,
etc.
On Wed, May 3, 2023 at 8:28 PM Praveen Kumar @.***>
wrote:

@slemeur https://github.com/slemeur we don't expose the preset as part
of human readable status but it is part of json which is used by the tools
( like podman desktop and VS extensions). To end user if they use the
podman preset then there would be no openshift version as part of status
and for microshift/okd/openshift preset there is openshift version and
that is what user more interested if the openshift is running or not and
api is accessible instead preset. preset is important on tooling side so
it is part of json output.
$ ./crc status -ojson
{
"success": true,
"crcStatus": "Running",
"openshiftStatus": "Running",
"openshiftVersion": "4.12.9",
"diskUsage":<PHONE_NUMBER>2,
"diskSize":<PHONE_NUMBER>6,
"cacheUsage":<PHONE_NUMBER>03,
"cacheDir": "/home/prkumar/.crc/cache",
"ramSize":<PHONE_NUMBER>,
"ramUsage":<PHONE_NUMBER>,
"preset": "openshift"
}
—
Reply to this email directly, view it on GitHub
https://github.com/crc-org/crc/issues/3626#issuecomment-1532941205, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZVM4VXZTY2JFEOSF33XEJFPTANCNFSM6AAAAAAXUJ67GE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]

I want to work on this issue. Could someone please assign it to me?

Hello, I think we can add preset information in crc status just  below CRC VM section like this:
CRC VM:                  Running
+CRC Preset:              microshift
MicroShift:              Starting (v4.16.14)
RAM Usage:               1.156GB of 3.821GB
Disk Usage:              5.086GB of 16.1GB (Inside the CRC VM)
Persistent Volume Usage: 0B of 15GB (Allocated)
Cache Usage:             12.56GB
Cache Directory:         /home/rokumar/.crc/cache

Since now as part of status we show Microshift: Starting (v4.16.14) in case of microshift and OpenShift: Starting (v4.16.14) so doesn't that mean it is already solved and we don't have to add extra filed for UX?

@praveenkumar : From my outsider's perspective, it's still unclear. We can change the line format to CRC Preset : MicroShift (Starting v4.16.14)

Looking at code in status.go , we only seem to got OpenShift/ MicroShift status for openshift and microshift presets, not for okd:
https://github.com/crc-org/crc/blob/f71d9cea2c99444488f1358f0217f1ff9be4f2a4/cmd/crc/cmd/status.go#L198-L202

Looking at code in status.go , we only seem to got OpenShift/ MicroShift status for openshift and microshift presets, not for okd:

OKD/OCP from end user prospective is same because both consume same amount of resource. This request is came from because of resource requirement was different for OCP and podman preset (we didn't get any issue from user). @crc-org/crc-team wdyt?

crc status should be accurate about what we are running, if we are running OKD, don't mention openshift. If you want to group okd and openshift under a common name, better to use one which is not ambiguous, eg OpenShift/OKD: ...


camera not enabled

Hello
I got a bananaPI M2 Zero and got the recommended camera module.
Trying to follow this manual, downloaded the image, it is working.
when trying to init the camera i get this:
pi@banana:~$ sudo media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:YUYV8_2X8/1280x720]'
Failed to enumerate /dev/media1 (-2)
pi@banana:~$ sudo media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:YUYV8_2X8/640x480]'
Failed to enumerate /dev/media1 (-2)
pi@banana:~$
I activated all io of the board (i2c etc') no help.
From DMESG:
pi@banana:~$ dmesg | grep capture -a3 -n5
109-[    1.192517] libata version 3.00 loaded.
110-[    1.192815] usbcore: registered new interface driver usbfs
111-[    1.192863] usbcore: registered new interface driver hub
112-[    1.192910] usbcore: registered new device driver usb
113-[    1.193053] mc: Linux media interface: v0.10
114:[    1.193087] videodev: Linux video capture interface: v2.00
115-[    1.193217] pps_core: LinuxPPS API ver. 1 registered
116-[    1.193225] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>117-[    1.193245] PTP clock support registered
118-[    1.193965] Advanced Linux Sound Architecture Driver Initialized.
119-[    1.194992] NetLabel: Initializing
pi@banana:~$
so, would like help in getting it to work.
Thank you.

Guy

I'm not sure what's causing your problem. It looks like a hardware problem.
Are you 100% sure that you have the OV5640 camera suitable for the BananaPIi-M2? There are OV5640 cameras with opposite wiring.
I downloaded the image again and tested it on my BPi. No problems here. I have listed a number of diagnostic screens below.

Thank you for your comment, i was following the next :
https://github.com/Qengineering/BananaPi-M2-Zero-OV5640
And bought the camera mentioned there :
https://nl.aliexpress.com/item/32660117929.html
The one that I got looks the same as the photos by the manual and the
aliexpress dealer.
Let me test the things you show in the screen shots.
Thank you
Guy
On Fri, Jul 15, 2022 at 12:53 PM Q-engineering @.***>
wrote:

I'm not sure what's causing your problem. It looks like a hardware problem.
Are you 100% sure that you have the OV5640 camera suitable for the
BananaPIi-M2? There are OV5640 cameras with opposite wiring.
I downloaded the image again and tested it on my BPi. No problems here. I
have listed a number of diagnostic screens below.
[image: Screenshot_2022-07-15_09-38-32]
https://user-images.githubusercontent.com/44409029/179199383-10f3a675-95c1-4e4d-9545-a2e1b08b3189.png
[image: Screenshot_2022-07-15_09-39-44]
https://user-images.githubusercontent.com/44409029/179199464-64be7776-47e4-409d-a824-dd1dd7742b71.png
[image: Screenshot_2022-07-15_09-39-21]
https://user-images.githubusercontent.com/44409029/179199528-dc2934c3-d757-4787-9dd7-54d3de6ba682.png
[image: Screenshot_2022-07-15_09-27-24]
https://user-images.githubusercontent.com/44409029/179199572-b1733fea-ce94-43c8-9fa9-b2292fabdb15.png
—
Reply to this email directly, view it on GitHub
https://github.com/Qengineering/BananaPi-M2-Zero-OV5640/issues/4#issuecomment-1185379465,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJTXH2SUADVFVRSKDGPXAFTVUEYIPANCNFSM53OSIAAA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
~Guy

In that case it should (eventually) work; you use the same hardware.

I experienced this problem with the same board and camera. Initially, on first boot I successfully used the camera following the instructions in the readme. I then updated all packages in aptitude and rebooted. Afterwards, /dev/media1 and /dev/video1 were no longer present.
pi@banana:~$ v4l2-ctl --list-devices
cedrus (platform:cedrus):
	/dev/video0

pi@banana:~$ ls /dev/video*
/dev/video0
pi@banana:~$ ls /dev/media*
/dev/media0
pi@banana:~$

After this I restored a fresh image and the camera worked once more. Looking at scrollback from my earlier session, I noticed that one of the packages that was upgraded was linux-image-current-sunxi. I suspect that doing so caused my problems, although I haven't confirmed. If appropriate, I would suggest putting a hold on that package in aptitude.

Amazing !
Used the same img file and somehow it works now .. very slow, but working.
Thank you for the help !!!!!!
[image: image.png]
On Fri, Jul 15, 2022 at 1:55 PM Q-engineering @.***>
wrote:

In that case it should (eventually) work; you use the same hardware.
—
Reply to this email directly, view it on GitHub
https://github.com/Qengineering/BananaPi-M2-Zero-OV5640/issues/4#issuecomment-1185429087,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJTXH2X355ONZSHCALJG3ITVUE7RBANCNFSM53OSIAAA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
~Guy


Travis CI - We don't have build instructions for 5.2.1

Hi @kylef,
I'm just seeing an issue where the installer is failing for 5.2(.1) but working for 5.1 on travis-ci.org
export SWIFT_VERSION=5.2.1
eval "$(curl -sL https://swiftenv.fuller.li/en/latest/install.sh)"
> We don't have build instructions for 5.2.1

I'm not sure if this is a travis issue or a swiftenv issue. I'll try to dig into it a bit, but if you've got any pointers, it would be much appreciated. Thanks

Is that when running against Ubuntu or macOS, and which version of the respective platform are you running against?

@kylef
This is the reduced travis config, that works fine for 5.1, but then fails on 5.2/5.2.1.
language: generic
dist: trusty
osx_image: xcode11.4
os:
  - linux
  - osx
env:
  - SWIFT_VERSION=5.1
install:
  - eval "$(curl -sL https://swiftenv.fuller.li/en/latest/install.sh)"
script:
  - set -o pipefail
  - swift test

Meant to post this link to the build, which should be public. Let me know if not, and I'll add you to the repo.
This is not urgent on my side, but just wanted to post it while it's fresh. Have a good one and hopefully catch you when all the craziness is over.

Try switching to dist: bionic. The Swift project no longer include binaries for Ubuntu 14.04 (trusty), switching to a more modern Ubuntu should provider you compatibility for Swift 5.2.1.

Thanks @kylef. Switching to bionic has done the trick.

Thanks for bringing this up. I've refreshed the docs at https://swiftenv.fuller.li/en/latest/integrations/travis-ci.html to specify bionic by default, that should work on Swift 4.2.3 onwards.


Minor cleanup: make MockClient.defaultResponse not null

I've identified that MockClient.defaultResponse can always be set to new Invocation(), avoiding potential NullPointerExceptions.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

but this is correct, an Invocation is a record of an invocation, a default invocation could or could not exist. You don't have any test documenting when a NPE might happen, can you add some?


Clickable AnimationView in Xamarin Forms

Are there any plans to add a Command property to the AnimationView or make GestureRecognizers to work with the AnimationView?
// This does not work
AnimationView.GestureRecognizers.Add(new TapGestureRecognizer()
{
    Command = new Command(() => {
         var i = 42;
    })
});

I'm interested in implementing either the Command property and/or fix the GestureRecognizer bug (if it is a bug).

I would accept a PR to implement the Command property.

@johankson Hi did you manage to work on the GestureRecognizer and/or command. Can someone point me in the right direction

I have added 4 different types of click events for android. Should I make this a branch in this repo or make my own? I plan to add same click events for iOS.

@johankson Just update yourXF.Lottie package to a new version. It has both - ClickedCommand and OnClick event.


onCellDoubleClick argument JSRecord is not a JSRecord is an object

Hi,
the process onCellDoubleClick have 4 arguments  the third argument says that is a JSRecord but is not , is an object. the problem is when we are using de svyNavigation in the process "scopes.svyNavigation.open" we are doing tricks things to change to a JSRecord .
I was wondering if the right way, shouldn't it be to return a JSRecord?
Un Saludo
Juan Ramírez

Hi,
it is an object, because for grouped records, the clicked record does not actually have a matching foundset in Servoy code, and so it can't return a record; for non-grouped records, it does return the right JSRecord, as those are from the component's foundset. There is already a case open for this on Servoy support, https://support.servoy.com/browse/SVY-14981, the fix maybe will be only a rename of the argument, from record to row, and a better documentation.
Regards,
Gabi

Hi,
after having another look I did see that we actually can use the record type for the callbacks, and that will be always a record in the the grid's foundset, even if the callback is on a grouped row.
Regards,
Gabi


Add associated taxons input form

For https://trello.com/c/fkKqW1rA/206-allow-taxons-to-be-associated-to-each-other-in-content-tagger
This PR adds the ability to add associated taxons to taxons. It's part of the work we're doing around world locations to be rendered as taxon pages. This PR adds a new input field and shows them on the show page (if present).
When deleting a taxon that is being associated from another taxon, the publishing api automatically updates to remove the taxon accordingly, so there's no need to cater for this explicitly in the ContentTagger app.

Screenshots
Before - edit/new

After - edit/new

Before - show

After - show

This looks good, but I'm unsure of the let blocks. The lazy loading in this case is not necessary in these test cases, and in some cases we explicitly don't want it (hence the let!). Using ivars in this case guarantees us that the code is executed, and makes the tests a little less magic. I would prefer to keep the acceptance tests free from let statements.

Thanks @tijmenb, have removed that last commit with the let block change. I've had to disable a rubocop instead since it wasn't happy about the instance variable naming of @taxon_3 (and others) 🙄

@davidbasalla great!


Use Go pilosa import options

Fixes #77
Fixes #75

These commits are included in #83 along with some changes.


API Design: consolidating intake-cmip and intake-cesm into one package

Adding these for future reference:
@andersy005, it strikes me that this routine is no-longer exactly appropriate in this class. It carries unnecessary logic to select the collection_type. I think that logic belongs in CesmMetadataStoreCatalog.build_collection. Let's imagine our proposed extension to encompass intake-cmip: we will need to understand the collection_type to know which method to call at the CesmMetadataStoreCatalog level.
Let me know what you think. I am happy to accept this PR and address this in a future iteration.
Originally posted by @matt-long in https://github.com/NCAR/intake-cesm/pull/28
Would an alternate implementation be to make this a class method? In that case the API might be something like
col = cesm_metadatastore.build_cesm_metadatastore(**kwarg)

whilst preserving the original interface to init.
It's not obvious to me which is preferable.
Originally posted by @matt-long in https://github.com/NCAR/intake-cesm/pull/28

intake-cesm + intake-cmip consolidation:

[ ] New name: intake-esm
[ ] Change intake-cesm name to the new name
[ ] Dump content of intake-cmip into the new package
[ ] Separate cmip5 and cmip6 catalog generation
[ ] Add columns to self to build_collection() method