[FlatList] Sometimes FlatList rows are rendered, but not displayed until scroll. RN 0.43

Description
When using FlatList, rows are not displayed though renderItem is called.
Rows appear immediately when scroll is triggered on the list.
Reproduction Steps and Sample Code
export default class List extends Component {
  renderItem({item}) {
    return (
      <Text>{item}</Text>
    );
  }

  render() {
    return (
      <FlatList
        style={{
          flex: 1,
          backgroundColor: 'white',
        }}
        data={[1, 2]}
        renderItem={this.renderItem}
      />
    );
  }
}

Solution
FlatList should always display its rendered items.
Additional Information

React Native version: 0.43.0
Platform: iOS
Development Operating System: MacOS
Dev tools: Xcode

Related https://github.com/facebook/react-native/issues/13202

@joonhocho could you create a gif of this in action? I can't reproduce with your example.

Are you experiencing this issue in a standalone project and/or are you able to reproduce in a standalone project if not?

We're also seeing this issue. Looks like it could be something to do with the FlatList being in a navigator on iOS. Managed to reproduce it in a standalone project. You'll have to excuse the code it's a bit rough.
react-native init and add the following code as your index.ios.js. Once launched, tap on A. Tap remove. Tap back. Then you'll need to scroll to get FlatList to re-render.
We found this on RN0.43.1 iOS simulator, iPad but not android. Seems to work as expected on android
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 * @flow
 */

import React, { Component } from 'react';
import { AppRegistry, StyleSheet, Text, View, FlatList, TouchableOpacity, Navigator } from 'react-native';

let data = [ { id: 'a' }, { id: 'b' }, { id: 'c' } ]
let listeners = []

class List extends Component {
  constructor (props) {
    super(props)
    this.state = { data: Array.from(data) }
  }

  componentDidMount () {
    listeners.push(() => { this.setState({ data: data }) })
  }

  render () {
    return (
      <FlatList
        data={this.state.data}
        keyExtractor={(item) => item.id}
        renderItem={({item}) => (
          <TouchableOpacity onPress={() => this.props.navigator.push({ id: 'r2', item: item })}>
            <View>
              <Text>{item.id}</Text>
              <Text>{item.id}</Text>
              <Text>{item.id}</Text>
              <Text>{item.id}</Text>
            </View>
          </TouchableOpacity>
        )}
      />
    )
  }
}

export default class AwesomeProject extends Component {

  renderScene (route, navigator) {
    if (route.id === 'r1') {
      return (<List navigator={navigator} />)
    } else if (route.id === 'r2') {
      return (
        <View>
          <Text>{route.item.id}</Text>
          <TouchableOpacity onPress={() => {
            data = [data[0], data[2]]
            listeners.forEach((l) => { l() })
          }}>
            <Text>Remove</Text>
          </TouchableOpacity>
          <TouchableOpacity onPress={() => navigator.pop()}>
            <Text>Back</Text>
          </TouchableOpacity>
        </View>
      )
    }
  }

  render() {
    return (
      <View style={[StyleSheet.absoluteFill, { paddingTop: 50 }]}>
        <Navigator initialRoute={{ id: 'r1' }} renderScene={this.renderScene.bind(this)} />
      </View>
    );
  }
}

AppRegistry.registerComponent('AwesomeProject', () => AwesomeProject);

Does setting removeClippedSubviews={false} fix the issue? Sounds like the issue might be related to the navigator which would explain why we don't see this problem at Facebook. cc @shergin

@Thomas101 @sahrens I am using react-navigation for your information.

@sahrens removeClippedSubviews={false} works for us for now.
We are using Navigator for a tab based app.

Navigate to the flatlist scene. List shows.
Navigate to another tab.
Make a change which affects the flatlist scene.
Navigate to the already mounted flatlist scene.
Flatlist shows as empty.
Touch component and the items are made visible.

@raffij @sahrens It also fixed the issue for me as well.

removeClippedSubviews={false} works for us too. I noticed in the VirtualizedList docs there's some discussion around setting this as the default, could I +1 that as I imagine quite a few people will come up against this?

I'm running an experiment in production soon to see the effect on scroll perf. If the hit isn't too bad, we'll turn it off by default.

Running into a similar problem here. It isn't exactly scrolling that's my problem though. What I have is a horizontal FlatList with paging enabled. I have a function that adjusts each item of the list to the width of the screen. What I'm doing right now is using redux and async storage to persist all my items, but the items do not render until I hit a button in my view to add another item in the list. When I set removeClippedSubviews={false} the view renders, but only part of it. I suspect it has something to do with the render prop, because when I render just a TextView I see the display, but not my full custom component. I'll post my code and a video tomorrow.

I had a possibly related issue with a ListView (RN 0.43.2) that seems to be solved by the removeClippedSubviews={false} suggestion.
In my case this ListView was inside an Animated.View with a translateY style (sliding down).  When the animation ended the ListView would have variable space above the first row (as if there was some contentInset padding).  Just barely scrolling the list would snap everything back to normal and the first row would be correctly at the top.
Just noting it here in case it might provide a hint.

I'm putting in a diff to disable removeClippedSubviews by default in VirtualizedList, so it will be opt-in and hopefully won't bite people like this in the future.

@sahrens Could you explain why removeClippedSubviews fixes the issue? Is setting removeClippedSubviews as false an optimal solution or is it just a temporary quick fix?

Could you explain why removeClippedSubviews fixes the issue?

I am wodering this question as well. I am using react-navigation as well. Setting removeClippedSubviews to false also fixed this for me. I'm not sure of it's implications (reduced perf?).

I'm getting this too in RN 0.43.3. Why is this closed?

I think the conclusion is that setting removeClippedSubviews={false} seems to fix these issues? Have you tried this yet?

Yeah, i just figured that out, cheers.  Much better.  But it's still a bug, no?

removeClippedSubviews is now off by default in master.

This also breaks components like react-native-maps (the map gets frozen on some area until swipe or some other gesture event).

This also breaks components like MapView in react-native-maps (the map gets frozen on some area until swipe or some other gesture event). So, this is not just an issue with react-native components.
I also believe MapView uses clipped subviews (markers I believe are clipped), so would this remove markers?

This also breaks components like MapView in react-native-maps (the map gets frozen on some area until swipe or some other gesture event). So, this is not just an issue with react-native components.

Got something really weird.
I'm trying to scroll to the end of my horizontal pager I made out of the Flatlist with this
componentDidMount() {
    this._listRef.scrollToEnd({ animated: false });
  }

Here's my Flatlist:
<FlatList
          ref={(flatList) => { this._listRef = flatList; }}
          data={this.props.log}
          onLayout={this.adjustPageSize}
          renderItem={this.renderPage}
          showsHorizontalScrollIndicator={false}
          getItemLayout={(data, index) => {
            const width = Dimensions.get('window').width;
            return { length: width, offset: width * index, index };
          }}
          removeClippedSubviews
          horizontal
          pagingEnabled
          directionalLockEnabled
        />

When I make it like this, my list does not render until I scroll, but when I change getItemLayout to this:
 getItemLayout={(data, index) => {
            const width = Dimensions.get('window').width;
            return { length: 0, offset: width * index, index };
          }}

with the length attribute as 0, my list renders perfectly fine, and it scrolls to the end correctly in componentDidMount

@huyanhh: that is indeed quite weird. Does it work without the length hack and without removeClippedSubviews?

@sahrens The list renders fine no matter what removeClippedSubviews is, as long as length is 0. Once I change back length to the screen width, regardless if removeClippedSubviews is turned off or not my list goes back to being blank until scroll.

removeClippedSubviews does not work for me, although I'm using a very common FlatList, as below:
<FlatList
   scrollEventThrottle={200}
   onScroll={e => true}
   ref={ref => this.listRef = ref}
   data={this.state.messageList}
   keyExtractor={item => item.messageId}
   removeClippedSubviews={false}
   renderItem={({item, index}) => {
      return (
          <MessageItem item={item}/>
      )
}}/>

Currently, my solution is after retrieving list data, I have to manually scroll down 1px this.listRef.scrollToOffset({offset: 1})
But it's still a bug, I think it should only be closed after fixed by a new release.

@facebook-github-bot reopen

@dzuncoi, do you think you might be able to put together an example project?

@joshyhargreaves will try asap

Why are you setting a useless onScroll property and changing the scroll event throttle? I don't think either of those should break anything, but can you double check removing those?

@sahrens
I just minimized onScroll property in my comment. Remove those properties does not affect anything.
After investigating more, removeClippedSubviews={false} works for me only if I add initialNumToRender={myInitialData.length} either. So my list does not render all items because my initial data size is more than the default number (10) of how many items to render in the initial batch.
Does it worth to emphasize this in FlatList docs?

That shouldn't be a problem - FlatListExample has an initialNumToRender much smaller than the data size with no issue.

@dzuncoi @sahrens Yes, using initialNumToRender={myInitialData.length} should never be done and is just hiding the issue by breaking FlatList and turning it essentially into a ScrollView.
That line basically disables all of FlatList's optimization intended to only render a portion of the items that are on screen and forces it to just render every single item in your list at once.

@dantman

optimization intended to only render a portion of the items that are on screen

So how do FlatList determine how many items will be rendered to fit screen, so that users don't see remaining-not-rendered items, or it just renders 10 items (by default)?
Maybe my problem is now out of this issue's scope.

@dzuncoi AFAICT FlatList uses the normal algorithm for this: Render initialNumToRender items (10), make sure the screen is full of items, if not render initialNumToRender (10) more items until it is, if the user has scrolled do this again to show the newly visible items. Not sure if FlatList does it, but maybe also unmount things that are no longer visible after scroll.

@dantman
I'm quite sure that:

On Android: I have to use both initialNumToRender and removeClippedSubviews to get all initial items rendered.
On iOS: if I use removeClippedSubviews only, I must scroll down 1px after retrieving my initial data to get it worked.

@dzuncoi : that is unfortunate, and I have not seen that before. An full repro case would be really helpful.
@dantman: almost, except maxToRenderPerBatch is used to fill the screen after initialNumToRender. And yes, items outside the render window are unmounted, which is the visible area + buffer, except for the initial items which are never unmounted unless you provide initialScrollIndex.

@joshyhargreaves Here's a GH gist for what I was talking about:
Trying to scroll to the end on load bug

Here is a gif of the behavior.

Here is a gif

initialNumToRender & removeClippedSubviews doesn't seem like a viable answer here, because it removes all the optimisations when you have a huge list full of pictures.

I'm still experiencing this issue. removeClippedSubviews={false} solved the problem for now.

I've experienced this too on RN 0.44.2 and it was solved with removeClippedSubviews={false}. Although, as @rogerkerse mentioned, it is not a optimal solution as it seems to remove some important optimisations.

Hi mine fixed by giving style={{ backgroundColor: 'white' }} to flat list

this is still happening in 44 with removeClippedSubviews={false} set

I don't think it's baked into the latest FlatList, I still has to force removeClippedSubviews={false}. Don't mind forcing it but would be nice to not have these hacks all around.

I have been fighting the problem of a FlatList with horizontal={true} and initialScrollIndex momentarily rendering the content, then blanking out until the view is scrolled again. The FlatList is rendered within a react-navigation StackNavigator.
I found the following combination to work for me:

calculating itemLayout in which length is equal to the window width
explicitly defining a width attribute on the top-level component within the renderitem.

This is my working component; I hope it's helpful:
export default class DetailList extends PureComponent {
  render() {
    return (
      <FlatList
        contentContainerStyle={styles.list}
        data={this.props.shirts}
        getItemLayout={this._itemLayout.bind(this)}
        horizontal={true}
        initialScrollIndex={this.props.showIndex}
        keyExtractor={this._keyExtractor}
        pagingEnabled={true}
        renderItem={this._renderItem.bind(this)}
        showsHorizontalScrollIndicator={false}
      />
    );
  }

  _itemLayout(data, index) {
    const width = this._itemWidth()

    return {
      length: width,
      offset: width * index,
      index,
    };
  }

  _itemWidth() {
    const { width } = Dimensions.get("window");
    return width;
  }

  _keyExtractor(item, index) {
    return item.id;
  }

  _renderItem({index, item: rowData}) {
    return (
      <DetailItem
        index={index}
        shirt={rowData}
        width={this._itemWidth()}
      />
    );
  }
}

In my case, it turned out that I had a bunch of container views in the hierarchy that emitted this behavior. Once I cleared all the unnecessary container views it started to behave the way it is supposed to.

For me, adding removeClippedSubviews={false} with rn 0.46 works.
But make sure that you don't have two items with the same id, I had one of those and it caused the issue - fixing it and adding removeClippedSubviews works.

Why the issue is closed?! :) Why removeClippedSubviews={false} is considered as working solution?
When you set removeClippedSubviews={false} it renders ALL cells even those are out of screen. Now imagine feed with 50-100 images. It will just blow up Android and probably any iOS app.

@rudyryk +1

@rudyryk +1
Unfortunately they considered it as a solution, see https://github.com/facebook/react-native/commit/3bf7856700ca2b7c20dd358b16a58ef8874f074a

Hi, should we limit the fetched list items to be displayed? meaning should I have paginated lists (so we utilize inifiniteScroll) ? are there performance issues (when scrolling for example) when fetching long lists (or all of them (e.g. list of users)) of data and render them.

In my case, I do infinite scrolling loading 100 records per time, so I changed the values of initialNumToRender, maxToRenderPerBatch and windowSize to 50.
<FlatList
    ...
    initialNumToRender={50}
    maxToRenderPerBatch={50}
    windowSize={50}
/>

After loading more than 600 items, if I scroll up quickly, some items appear blank and are quickly loaded again. That was satisfactory to me.

@Kiarash-Z fix works ... but why the f*** ? :D

This is still an issue in RN 0.49.3 if removeClippedSubviews=true.

I am having this issue still even with removeClippedSubviews={false}. Any additional solutions here?

I am still having this issue with removeClippedSubviews = {false} but then setting it false also reducing my rendering performance.
However, @douglasjunior solution worked perfectly fine for me without compromising performance.
Thanks @douglasjunior  👍

https://github.com/facebook/react-native/issues/1831
According to that, the fix was merged in and available for RN 0.50. If you do not want to or cannot upgrade RN yet, you can just change the line as shown in the file.
https://github.com/facebook/react-native/commit/03ae65bc25185fe6d7f62e66f5575ced5c3e8378
On my app, this fix solves the issue and I can still use removeClippedSubviews={true}.

@douglasjunior Sorry to bother, but how did you implement the Activity Indicator while scrolling the FlatList?

When fetching the data, render an ActivityIndicator as ListFooterComponent.  Example here.

This is still a problem with 0.50.3. removeClippedSubviews don't seem to have any effect. Can we reopen this please?

Inspired by the comments in this thread from Kiarash-Z and douglasjunior, my fix to this solution was basically:
ListFooterComponent={() => {
  return <View style={{backgroundColor: 'transparent', height: 1}} />
}}

I could not use a ActivityIndicator but it seems RN needs new content to be rendered, even an "invisible" view (Note, with height of zero the bug still existed).

@BlakeSimpson this is good, but again it is not viable solution in the long run because it is basically a hack.
Why is this closed again, if this is not resolved 👎

@rogerkerse I totally agree. This is a hack and a real solution would be preferable.
We've recently upgraded to RN 0.52 though and the issue seems to be resolved, so I am removing my hack. Perhaps you can upgrade your React Native version also or just use the hack temporarily until you can?

Super weird, when I edited getItemLayout to not match my actual item component, it rendered immediately again for me...
getItemLayout={(data, index) => (
    {
        length: itemWidth - 1, // why does this work
        offset: itemWidth * index,
        index
    }
)}

I might have resolved it by only passing initialScrollIndex if the items would actually go off screen.
initialScrollIndex={sortedEntries.length > 5 ? sortedEntries.length - 1 : 0}

Feels like this kind of logic should not be necessary.

@bensheldon that solved it for me, thanks!
setting length in getItemLayout to window width worked for me
I had set it before to item length

After refactoring to use FlatList I must go back to ListView.
None of these solutions work for me.
ListView just works.
		"react": "^16.2.0",
		"react-native": "^0.53.3",
		"react-native-router-flux": "4.0.0-beta.27",

@esutton can you show your FlatList, getItemLayout and css used in the FlatList?

@DOHere I am not using the getItemLayout option.
  renderRow = ({ item, index }) => {
    const menuItem = item;
    return (
      <MenuItemRow
        menuItem={menuItem}
        onPressMenuItem={this.onPressMenuItem}
        {...this.props}
      />
    );
  }

  render() {
    const { themeStyle } = this.props.state;
    const connecting = (this.state.animating || this.state.connecting)
      ? (<View style={[styles.row, themeStyle.view]}>
        <Text style={[themeStyle.textPrimary, { fontWeight: 'bold' }]}>
          {this.state.progressMessage}
        </Text>
        <ActivityIndicator
          animating={this.state.animating}
          style={[
            styles.centering,
            {
              backgroundColor: themeStyle.textPrimary.backgroundColor,
            },
          ]}
          color={themeStyle.textPrimary.color}
          size="large"
        />
      </View>)
      : null;

    return (
      <View style={styles.listContainer}>
        {connecting}
        <FlatList
          ref={(ref) => { this.listView = ref; }}
          style={themeStyle.view}
          ItemSeparatorComponent={this.renderSeparator}
          data={this.state.dataSource}
          renderItem={this.renderRow}
          refreshing={this.state.animating}
          onRefresh={this.onTrackerScan}
          automaticallyAdjustContentInsets={false}
          keyboardDismissMode="on-drag"
          keyboardShouldPersistTaps="always"
          enableEmptySections
          keyExtractor={this._keyExtractor}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  centering: {
    alignItems: 'center',
    justifyContent: 'center',
    padding: 8,
  },
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  listContainer: {
    flex: 1,
  },
  list: {
    marginTop: 0,
    backgroundColor: '#eeeeee',
  },
  row: {
    flexDirection: 'row',
    alignItems: 'center',
    padding: 8,
    borderWidth: 0,
    borderColor: '#DDDDDD',
    justifyContent: 'space-between',
  },
  rowSeparator: {
    backgroundColor: 'rgba(0, 0, 0, 0.1)',
    height: 1,
    marginLeft: 4,
  },
  rowSeparatorHide: {
    opacity: 0.0,
  },
  separator: {
    backgroundColor: 'rgba(0, 0, 0, 0.1)',
    height: StyleSheet.hairlineWidth,
    marginVertical: 10,
  },
  separatorHorizontal: {
    backgroundColor: 'rgba(0, 0, 0, 0.1)',
    height: StyleSheet.hairlineWidth,
    marginHorizontal: 10,
  },
});

@esutton I suggest you set the height of rows somewhere in css
and also use getItemLayout. Try this:
```
import { Dimensions } from "react-native";
screenHeight = Dimensions.get("window").height;
getItemLayout={(data, index) => ({
length: screenHeight,
offset: index *  + (  - screenHeight ) / 2,
index,
})}

@DOHere Thank you very much for the tip.
I plan to stay with ListView as long as I can.  FlatList has wasted way too much of my time.
After my experience of migrating multiple components to FlatList,  I have had to roll back to ListView several times because of rendering not working properly as ListView did.
I will keep your advice in mind when I am forced to upgrade to FlatList.

Still with the FlatList in React Native 0.54. It started happening all of a sudden and it's actually annoying.

Please reopen, same issue in RN 0.54 for me...

Found a working Hack for this.
render() {         setTimeout(() => {             this.sectionList && this.sectionList.recordInteraction();          }, 50);         return (             <SectionList ref={(view) => { this.sectionList = view }} />         ) }

I dont encounter this error when I install in debugMode. However once I do  react-native run-android --variant=release I get this bug. In my case the rows do render but kind of "not fully". The color of the items are sluggish and blend with the background color.
I have no clue on what to do to fix this. It is really frustrating.

Finally，the only way for me is back to ListView.

<Flatlist style={{ flex: 1 }}/>
This trick work for me without switching to ListView.

Adding removeClippedSubviews = {false}works, but it reducing your rendering performance,if you hava a largelist of image,maybe 500 items can lead to crash.

FlatList is not efficiently maintaining cells of a ListView, instead, you may use Flipkart developed [RecyclerListView]. (https://github.com/Flipkart/recyclerlistview)
Demo: With lots of images, https://snack.expo.io/@naqvitalha/rlv-demo

had the same problem, the problem is that the data source is a JSON and therefore will be passed to the reference and not as a value, by modifying that object from any of its references automatically 'Flatlist' will have these new data and for more if we use setState to try to update the flatList, we will not see the changes until we move because Flatlist will already have that data. It's a bit confusing but here I give you a little 'solution'.
   // We break the reference by making it immutable
   let playlistInitial =  JSON.stringify(store.getState().playlist);

    if (playlistInitial != "") {
      this.setState({ playlistInitial });
      AudioController.init(JSON.parse(playlistInitial), 0, this.onChangeStatus);
    }

 <FlatList
     data={this.state.playlist}
     initialNumToRender={5}
     style={{ flex: 1 }}
     horizontal={true}
     showsHorizontalScrollIndicator={false}
     keyExtractor={item => item["key"]}
     renderItem={({ item }) => <RowStationHome data={item} />}
 />


Telegram Sharing - DESKOP - not working

Hi,
i'm just used this wonderful plugin and i noticed that TELEGRAM sharing not works on desktop with "telegram web".
WHATS EXPECTED:
Share content on Telegram
HOW TO REPLICATE ISSUE:
You can try directly from documentation DEMO page: https://nicolasbeauvais.github.io/vue-social-sharing/?path=/story/vuesocialsharing--multiple-share-networks
ISSUE:
Clicking on Telegram Sharing link opens a new window showing all data set and ready to go.
If you try to click on "Share" green button, nothing happens.
BROWSER:
Chrome (Ubuntu 20.04 - last ver.)

Hi Roby,
Just taking a look at the Telegram popup, it looks like the share URL is an application specific one (https://coderwall.com/p/mtjaeq/ios-custom-url-scheme)
If you hover over the share button it looks like it is trying to directly open a Telegram app on a device tg://.
This is something on telegrams side, not this packages

Thank you @rhyswfbowles for the explanation, if we can do something about this @Roby-iTuna, feel free to re-open this issue.


Create usdaddTimeout.md

timeout function doc added

It’s $timeoutMember not $timeout/$addTimeout. Also file names must be in all lowercase.

It’s $timeoutMember not $timeout/$addTimeout. Also file names must be in all lowercase.

ight finished

It’s $timeoutMember not $timeout/$addTimeout. Also file names must be in all lowercase.

ight finished

Awesome


When table is created with name, register it in data catalog

Description
#587 allows providing a name for a Delta table. However, it won't immediately work for users since we don't register it. We should provide a way to automatically register tables when they are created in a catalog. There may be other changes, like schema changes or deleting tables that will also require an update to the catalog.
Use Case
Related Issue(s)

@wjones127 can you give me a feedback on https://github.com/edmondo1984/delta-rs/commit/b524f66322a388fecb9670a95676329fe9df567c as a starting point? I am a little confused since I found that the call to the catalog was actually within the Python folder and not something shared by all bindings

+1 on @wjones127 's explicit table registration proposal :) The separation of concerns here also avoids unnecessary overhead in table creation when users don't need to register it in the catalog.

I can look into this for the databricks unity catalog. It's one of the use cases I need to touch at work in a couple months.
@houqp @wjones127 is this still a desired feature?


Switch default value of external_metrics_provider.port to 8443

What does this PR do?
Switch the default value of the external metrics provider port (external_metrics_provider.port) from 443 to 8443 to remove the need to run the cluster-agent as root.
Motivation
In order to improve security, we’d like to run the cluster-agent with a non-root user.
Additional Notes
The external metrics server makes sense only on Kubernetes.
And on Kubernetes, 8443 was already the default value

when deployed with the Helm chart: https://github.com/DataDog/helm-charts/blob/9867710765119c7db862a00598e4673d953e699d/charts/datadog/values.yaml#L657-L658
when deployed with the datadog operator: https://github.com/DataDog/datadog-operator/blob/22cf9133ecae817586c1ccfd70ad651aa2294e4f/apis/datadoghq/v1alpha1/datadogagent_default.go#L68

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Note: it's breaking change for Kubernetes < 1.15 where this field is not available


Not detecting light bulbs

Its detecting outdoor plugs but not detecting light bulbs

Having the same problem.  Finds my plugs, cameras, and lock, but not my color bulbs.


use ForwardDiff to compute Jacobian

Adds ForwardDiff to compute \phi if param_jac is not specified in Regression.

Test error is
Test Failed at /home/runner/work/MitosisStochasticDiffEq.jl/MitosisStochasticDiffEq.jl/test/ensemble_test.jl:31
193
  Expression: isapprox(mean(samples1), mean(samples2), rtol = 0.005)
194
   Evaluated: isapprox(0.9903002403934436, 0.9980304907361291; rtol = 0.005)

so a Random.seed! missing in our tests


hydra-init fails if sudo is disabled

Describe the bug
hydra-init (and the rest of hydra) fails if sudo is disabled.
systemd[1]: Starting hydra-init.service...
sudo[2278042]:     root : unable to stat /etc/sudoers : No such file or directory ; PWD=/ ; USER=postgres ;
hydra-init-pre-start[2278042]: sudo: unable to stat /etc/sudoers: No such file or directory
hydra-init-pre-start[2278042]: sudo: no valid sudoers sources found, quitting
hydra-init-pre-start[2278042]: sudo: error initializing audit plugin sudoers_audit
systemd[1]: hydra-init.service: Control process exited, code=exited, status=1/FAILURE

Steps To Reproduce
Install hydra and set security.sudo.enable = false
Expected behavior
Hydra works.
NixOS 21.11

Fixed in #180536


Supabase functions deploy randomly breaking.

Bug report
Supabase functions deploy randomly breaking..
Describe the bug
3 out of 10 times am getting the following during the deployment of supabase functions.
error: Uncaught (in promise) Error: Module not found<EMAIL_ADDRESS>      const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
    at __wbg_new_8d2af00bc1e329ee (https://deno.land/x/eszip@v0.30.0/eszip_wasm.generated.js:312:19)
    at <anonymous> (https://deno.land/x/eszip@v0.30.0/eszip_wasm_bg.wasm:1:79439)
    at <anonymous> (https://deno.land/x/eszip@v0.30.0/eszip_wasm_bg.wasm:1:1388039)
    at <anonymous> (https://deno.land/x/eszip@v0.30.0/eszip_wasm_bg.wasm:1:1862894)
    at __wbg_adapter_18 (https://deno.land/x/eszip@v0.30.0/eszip_wasm.generated.js:146:6)
    at real (https://deno.land/x/eszip@v0.30.0/eszip_wasm.generated.js:130:14)

Try rerunning the command with --debug to troubleshoot the error.
Error: Process completed with exit code 1.

Rerunning failed jobs, runs it again with no issues.
To Reproduce
It's random..
Expected behavior
Deploy the function without breaking the GitHub Action.
System information
runs-on: ubuntu-latest
- uses<EMAIL_ADDRESS>with:
version: 1.42.5
Additional context
Tried different versions, but the problem continue to appear.

@laktek do we need to wrap functions deploy with built-in retry?

Looks like this is happening due to network flakiness. Yeah, a retry logic here would help.

Closing as we are now bundling functions using edge-runtime instead of deno. Feel free to reopen if this issue persists.


Program loads blank when server status page is down.

Unsure if the Server Status page being offline has anything to do with it, but I figured I'd add that info.
To reproduce this issue, this is what I did:
Played WoW till the servers went down.
Thought "I wonder if there's an app that will notify me when they are back up"
Found this app, downloaded and installed.
First run.
App goes "Not Responding" for about 60 seconds, (See first screenshot)
App then unfreezes, gets a background texture, and that's all. nothing more (Screenshot 2)
At best guess (As I'm not a programmer) I'm guessing it can't handle the Server Status page being down?

Maybe not.....
ServerStatus page is back online. reloading WoW Stat shows the same issue. blank window.

resolved in https://github.com/arzynik/wowstat/releases/tag/3.0.2


Finish cleanup

+ Initialize PerformanceCounterFromJsonGauge with value of the environment variable.
+ Implement alternative implementation for unit tests that doesn't need to access remoteenvironmentvariables.azurewebsites.net

:shipit: when Sergey says so. 😄


Links not correctly rendered in preview

Great Plugin - especially with the preview. Unfortunately links are not rendered correctly. Markdown:
[Mark Michaelis](https://github.com/mmichaelis)

will be rendered as:

[Mark Michaelis](https://github.com/mmichaelis)

instead of

Mark Michaelis

Should be fixed by #36.


Feature - YAML search - find properties with a specific scalar value

What's changed?
I have changed the org.openrewrite.yaml.search.FindProperty search recipe to allow searching for yaml properties which have a specific scalar value. The new reciped parameter propertyValue is OPTIONAL which ensures downwards-compatibility.
What's your motivation?
I need this search functionality for a specific use case I am working on.
I want to alter a yamle file if the specified yaml key does have a certain value. The search recipe can act as a Precondition here.
Anything in particular you'd like reviewers to focus on?
I thried to create a dedicated org.openrewrite.yaml.search.FindPropertyWithValue recipe inheriting from org.openrewrite.yaml.search.FindProperty, but recipes are final and do not allow for inheritance. This is why I added an optional parameter to the existing recipe instead.
Also I did not find out how to test a negative search case. I marked hence the negative test as @Disabled.
Have you considered any alternatives or workarounds?
Alternative: Use SourceGraph to find the repos having the specified Yaml condition. Well then I can also run the change with Sourcegraph.
Any additional context
I love the generic yaml stuff you have
Checklist

[x] I've added unit tests to cover both positive and negative cases (well comment about the negative test case)
[x] I've read and applied the recipe conventions and best practices
[x] I've used the IntelliJ IDEA auto-formatter on affected files

Thanks @aamotharald !


create new credential definition - page

User story

As a {HR-Employee}
I want / need {to create a new credential which I can later assign to a DI}
So that {I can create a Mitarbeiterausweis for example}

Acceptance criteria

navigation bar has a tab for credentials

dropdown menu has button "create credentials"

create credentials page includes:

fields:

name (string)
comment (optional, string)

tickbox;

"Revocable" (boolean) (needs to be adjusted in backend)

buttons:

"select icon" (link to a png can be inserted)

dropdown menu for schema selection:

nice addon-feature: have a search-field combined with the dropdown menu where user can search for schema
pick one schema from dropdown-menu

final button below all other things to create credential
feedback on success/error is displayed in frontend

Definition of done (DoD)

Added only after week 5
The same for all features
Here goes the project specific part

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

Meine Tasks: revocable-Token im Backend durchreichen


fix: added support to new version o class-validator

We utilize your package on one of our projects and we identified a vulnerability on the actual version of<EMAIL_ADDRESS>we update our project to use the new version 0.14.0, but it generate an conflict with your package. This pr tries to resolve it, I've executed the tests and it seems to be ok. Mind giving a look on this?

perfect.

Hi, it looks great


[BUG] Unexpected end of JSON input inside the relog.js file. (Line 58)

Describe the bug
Upon logging in, the app throws this error.
https://i.imgur.com/poaxHUz.png
To Reproduce
Unsure. Seems to happen everytime I use the .cookieLogin() function.
Expected behavior
It should just login and throw no error.
Screenshots
https://i.imgur.com/poaxHUz.png
Additional context
Code used to login:
async function startApp () {
    await noblox.cookieLogin("removed-for-security")
    // Do everything else, calling functions and the like.
    var currentUser = await noblox.getCurrentUser();
}
startApp().catch(console.error);

Disregard, it seems that something cleared the cookie file somehow,


Contract saving issues

When reloading a save sometimes a contract that has already been completed or failed will come back, preventing the players from getting a new one while at the same time giving a free contract that wasn't paid for. At the very least it would be good to have a failsafe command to cancel the current contract.

You already have a cancel current contract prompt when you look at current contract status.


NO-JIRA: e2e/utils: improve logs for EnsureSATokenNotMountedUnlessNecessary

What this PR does / why we need it:
When EnsureSATokenNotMountedUnlessNecessary fails, it's hard to know what pod is problematic.
This PR adds that kind of information in the logs.

/close
I moved the commit to #5202


Adaptation UI: Move Help / Preview buttons into separate menu

Describe the bug
For the smallest phone screen sizes, we have been running out of horizontal real estate to place all the toolbar buttons for the adaptation UI. In release 1.2, we have had to eliminate the Help button from the UI if the screen size is too small. In release 1.3, this situation gets compounded by the addition of the Show Translations... and Find in Documents... menu commands.
For the 1.3 release, we should move these secondary commands to a separate dropdown menu:

Show Translations...
Find in Documents...
Show Preview / Hide Preview (toggle menu command)
Help

Issue fixed by previous checkin (see https://github.com/adapt-it/adapt-it-mobile/commit/426ba8c2f5ed3211420fa8795da4bb2092f046e9). Here is a screenshot of the new More Items menu:


Incorrect result when using tf.norm to conduct p-norm computation on float16 precision

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.15.0
Custom code
Yes
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
tf.norm outputs incorrect result under float16 computation when the ord is large. Here is the code to reproduce:
import tensorflow as tf
input = tf.constant(1.751, dtype="float16")
p = 144111111
print(tf.norm(input, p))   # tf.Tensor(1.0, shape=(), dtype=float16)

Instead, if I change the dtype to 'float32', tf.norm outputs inf. It seems that tf.norm overflows during this computation https://github.com/tensorflow/tensorflow/blob/9ce1d5f2f7e5e8866a55633c182cc2dda1a2d6b8/tensorflow/python/ops/linalg_ops.py#L784
Although fixing this issue by letting tf.norm also outputs inf in float16 (which is consistent with the result in float32. I am suggesting another possible fix according to this post https://timvieira.github.io/blog/post/2014/11/10/numerically-stable-p-norms/
Indeed, the original implementation may not be numerical stable, a more stable one is to normalize the input before doing the actual computation. Here is the naive implementation of original tf.norm and the numerical stable one as a possible fix:
import tensorflow as tf
input = tf.constant(1.751, dtype="float16")
p = 144111111

def origin_norm(x, p):
  result = tf.math.abs(x)
  result = tf.math.pow(
      tf.reduce_sum(tf.math.pow(result, p), axis=None, keepdims=True),
      1.0 / p)
  return result

def refined_norm(x, p):
  a = np.abs(x).max()
  return a * origin_norm(x/a, p)

print(f"The original tf.norm's output is: ", tf.norm(input, p))
print(f"The naive implementation of tf.norm: {origin_norm(input, p)}, the refined norm: {refined_norm(input, p)}")

The refined_norm will output correct results (i.e., 1.7509765625) not only for float16 computation but also for float32 computation.
Standalone code to reproduce the issue
import tensorflow as tf
input = tf.constant(1.751, dtype="float16")
p = 144111111

def origin_norm(x, p):
  result = tf.math.abs(x)
  result = tf.math.pow(
      tf.reduce_sum(tf.math.pow(result, p), axis=None, keepdims=True),
      1.0 / p)
  return result

def refined_norm(x, p):
  a = np.abs(x).max()
  return a * origin_norm(x/a, p)

print(f"The original tf.norm's output is: ", tf.norm(input, p))
print(f"The naive implementation of tf.norm: {origin_norm(input, p)}, the refined norm: {refined_norm(input, p)}")

Relevant log output
No response

@QuantumCoder4 Thank you for raising this issue. Could you please have a look at this gist and confirm the results?
Thank you!

Yes, I confirm the result. I would be appreciated if you could fix it.


Do not overwrite/replace the config file on re-installation

When you have already installed and setup/configured the service, try running the setup script again; it would replace the config file /etc/pglistend/config.yml with a fresh generated file.
This should not happen. Or, at least it should keep the copy of original config in case files are overwritten.

@kabirbaidhya is this open for PR?

@anusha5695 Yes, it is.
Just a heads up that - I had worked on this project few years back so there might be chances that things aren't in place. Feel free to ask any queries if you run into issues. Thanks!


Add global lock for tests using mongodb

Since this is for testing, it seems like it would be better to just use lazy_static, as it will be simpler.

Since this is for testing, it seems like it would be better to just use lazy_static, as it will be simpler.

why simpler?

Sure, but this is for testing only, and lazy_static is simpler.
That being said, I think the approach isn't what we want here anyway. I don't think we should be locking tests, but rather creating a wrapper for the database that will drop the database on exit so that tests clean up after themselves.

what if two tests use the db at the same time?

It should not matter if two tests use it at the same time, but if it ever does then we would want a lock for that.

if one test drops the db and cleans it while the other is using it?

This would be an Rc or Arc so that it would only drop when there are no remaining refs.

Superceded by #567


catch possible exception

Codecov Report

Merging #10409 (4e9b56e) into 3.0 (a405256) will increase coverage by 0.10%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##                3.0   #10409      +/-   ##
============================================
+ Coverage     65.55%   65.65%   +0.10%
- Complexity      292      319      +27
============================================
  Files          1234     1234
  Lines         53913    53916       +3
  Branches       8155     8156       +1
============================================
+ Hits          35340    35400      +60
+ Misses        14700    14661      -39
+ Partials       3873     3855      -18

Impacted Files
Coverage Δ

...vent/listener/ServiceInstancesChangedListener.java
79.92% <50.00%> (+0.23%)
:arrow_up:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...che/dubbo/registry/client/NopServiceDiscovery.java
44.44% <0.00%> (-11.12%)
:arrow_down:

...dubbo/remoting/exchange/support/DefaultFuture.java
87.06% <0.00%> (-5.18%)
:arrow_down:

...e/dubbo/rpc/protocol/tri/transport/WriteQueue.java
73.80% <0.00%> (-4.77%)
:arrow_down:

.../dubbo/rpc/protocol/dubbo/DecodeableRpcResult.java
58.97% <0.00%> (-2.57%)
:arrow_down:

...etadata/report/support/AbstractMetadataReport.java
69.09% <0.00%> (-2.28%)
:arrow_down:

...exchange/support/header/HeaderExchangeHandler.java
61.06% <0.00%> (-1.77%)
:arrow_down:

...ubbo/registry/client/ServiceDiscoveryRegistry.java
75.40% <0.00%> (-0.55%)
:arrow_down:

...rg/apache/dubbo/common/timer/HashedWheelTimer.java
85.56% <0.00%> (+0.68%)
:arrow_up:

... and 31 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


feat(ui): incident view filtering by process id and time

implements #438
Demo/Screenshot

noteworthy changes

introducing new dependencies for QueryDSL

reasoning QueryDSL is well supported with the Spring JPA framework and eases the filtering of various attributes

there's a bug fix for popper.js, since the import was broken (visible in JS console of Chrome, when clicking a drop-down menu, created with bootstrap and then there was the error message, that popper.js was missing)
on-top of the ticket, I do introduce sorting of error type and process id to further assist in finding incidents

@nitram509 thank you for your contribution. :tada:  I'll have a look at your PR in the next few days. :eyes:

@nitram509 I'll have a look at your PR next week.

Hi, @nitram509 , did you forget to upload the QIncidentEntity.java ❓


How to pipe hash rate

For the Windows binary is there a way to pipe the hash rate my machine is mining at to another program or write it to a file or any other way to get it?

nheqminer.exe -l equihash.usa.nicehash.com:3357 -u  -t 4 2> logfile.txt
but this will send all console output, your other program will have to parse it.  If you want only the hash rate then some patches would have to be put in..

you can use the api, see #165


doukutsu-rs

An engine reimplementation for cave story but can be used to play the switch version without a switch or switch emulator.
https://github.com/doukutsu-rs/doukutsu-rs

Thanks :D i added it to the list


gem won't use current pg gem

This is related to https://github.com/uhoh-itsmaciek/attr_vault/pull/22
My gemfile is using pg version 1.0.1.
If I try to bundle install this gem it installs version 0.1.2.  If I try to force version 2.0.0 I get:
Bundler could not find compatible versions for gem "pg":

  In snapshot (Gemfile.lock):
    pg (= 1.0.0)

  In Gemfile:
    pg

    attr_vault (= 2.0.0) was resolved to 2.0.0, which depends on
      pg (~> 0.18)

    sequel_pg was resolved to 1.8.1, which depends on
      pg (>= 0.18.0)

If I bundle update when specifying version 2.0.0, it will install pg version 0.21.0 which I don't want.

Thanks for reporting this! Do you know what the right gemspec should be? Basically I want to require at least 0.18 because previous versions had a data corruption bug, but anything after that should work fine.

So you could open-end it like so:
  gem.add_runtime_dependency "pg", '>= 0.18'

which means any version >= 0.18.0 will be allowed.
If you really want to top-bound it you can do a compound like
  gem.add_runtime_dependency "pg", '>= 0.18', '< 2.0'

which would allow 0.18.0 through anything prior to 2.0.  But I think in this case the first option is probably "better" for now?
(sequel_pg as a corroborating example uses s.add_dependency("pg", [">= 0.18.0"]))

Ok, I just shipped 2.1.0 with this change. Can you let me know if that fixes your issue?

will let you know - don't see it up on rubygems yet

looks good to me!  thanks @uhoh-itsmaciek !


Create new notebook - kernel busy

I did start jupyter notebook
I did created new notebook for haskell from jupyter dashboard on http://localhost:8888/tree#
If have new notebook on http://localhost:8888/notebooks/Untitled1.ipynb?kernel_name=haskell
But haskell kernel is continuously busy (grey icon). If I write any code and try it, this not be run.
shell console
[I 03:39:54.217 NotebookApp] Creating new notebook in
[I 03:39:56.567 NotebookApp] Kernel started: c09375e0-b755-47d7-92eb-3bf2e63b4d7c
[W 03:39:57.770 NotebookApp] 404 GET /static/components/codemirror/mode/ihaskell/ihaskell.js?v=20160301033940 (<IP_ADDRESS>) 56.53ms referer=http://localhost:8888/notebooks/Untitled1.ipynb?kernel_name=haskell
ihaskell: main/Main.hs:(240,13)-(250,15): Missing field in record construction protocolVersion
[W 03:40:06.756 NotebookApp] Timeout waiting for kernel_info reply from c09375e0-b755-47d7-92eb-3bf2e63b4d7c

$ ps -ax | jupyter
8725 pts/2    Sl+    0:02 /usr/bin/python3 /usr/local/bin/jupyter-notebook
8847 pts/2    Sl     0:06 /home/domogled/.cabal/bin/ihaskell kernel /run/user/1000/jupyter/kernel-6d2600da-0ad0-45e8-bb9d-9c4684aefefe.json --ghclib /usr/local/haskell/ghc-7.10.3-x86_64/lib/ghc-7.10.3

RESOLVED
I did uninstall haskell-platform (I did used generic package from https://www.haskell.org/platform/
and
I did install haskell-platform from linux-mint repository (ghc 7.6)
It works!!!

While IHaskell builds fine with ghc 7.6, it is not fully supported. I suggest you atleast have ghc 7.8.4 installed.

Yes, of course. However, the simplest recomended way to install haskell on Linux Mint (Ubuntu also) on https://www.haskell.org/platform/ is from ubuntu package repository.
I dont understand, why is in repository so the old version.
I did install first from generic source, unfortunelly it did not work with jupyter ihaskell.
Im considering now, that I will use old version, or I will detect problem reported with message
ihaskell: main/Main.hs:(240,13)-(250,15): Missing field in record construction protocolVersion

Mint and Ubuntu provide old ghc in the official repositories. For knowing the recommended way to get up-to-date ghc, take a look at the learnhaskell guilde.

O great, with stack working all excellent.
ghc 7.10.3, iHaskell with Jupiter work
very Thanks

Glad I could help :smile:


Added neovim rust-analyzer config file to gitignore

The rust-analyzer.json file is the default file for configuring rust-analyzer on a per project basis for rustaceanvim. Added it to the .gitignore as it is similar in function to the .vscode directory. Did not see it fit to add to the changelog as this does not change the hal in in any way and only has to do with not getting config files included in the repo.

Please add entry to CHANGELOG.md for this to be merged, @s7rul . The change itself is harmless, so I don't mind including that entry in .gitignore.

Added to changelog and squahed into one commit.


cloudwatch: Found Error: Error: Missing source file for snapshot exiting

i got an error on cloudwatch while running aws2tf
aws_cloudwatch_log_group <redacted> tf files
Found Error: Error: Missing source file for snapshot exiting ....

I think this one is caused by a race condition when doing parallel imports.
Committed a change that turns down the number of parallel imports that are allowed.
It might help avoid this error
You can also rerun with ./aws2tf.sh -c yes - to jump over tf files already imported

i am using -c yes

are you still seeing the error ?

no. cloudwatch files were generated a few days ago


Validate hash from GCS when present

Would still be cool to add crc32c support but I didn't find a readily available go implementation so.. not worth it for now.


Any way to powder down and makes apache working again?

Hi, when I do powder down, there's no way that Apache is able to gain back control of <IP_ADDRESS>.
Is it because the firewall rules redirection aren't properly deleted?

@allaire I had the same problem on Yosemite (10.10.2) and it drove me nuts.
I created this Gist to completely disable pow and all firewall rules on MacOSX Yosemite, in order to get access to my local webserver (Apache) on port 80 over <IP_ADDRESS>.
Check if it works for you.


Drawing Layer: Change fill_enabled to fill_pattern

[x] Rename fill_enabled to fill_pattern
[x] type should be string instead of boolean

I pushed the changes as requested into your 1122-drawingLayer-fillPatterns branch.


Upgrade Lucene/Solr to 8.1.0

This PR also includes the changes from https://github.com/renekrie/querqy/pull/48. Once it is merged the diff will be reduced to only the relevant one for this PR.
There are some tests failures which I am tracking now. Any help to fix them is welcome!

Thank you @martin-g !  - We are currently preparing a release for issues #32 and #45 (should happen this week). I think it won't conflict too much with your PR but it will need some modifications. Let me create an issue and a branch for Solr 8.x  in this repo after #32 and #45 have been merged.  That might facilitate the collaboration amongst us and with other contributors. (I'll try to merge your PR with that branch as soon as possible)


SharePoint Framework code not working in Internet Explorer

Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
The code is running in the context of an extension. One of the first things that happens is the retrieval of a sharepoint list item value. The code runs fine in Chrome and Edge, but somehow does not run in Internet Explorer 11.
In chrome when using the debugger the following network calls are shown:
GET /sites/Z010/00001/_api/site/rootweb?$select=Url HTTP/1.1
POST /sites/Z010/_api/contextinfo HTTP/1.1
POST /sites/Z010/_api/web/lists/getByTitle('Configuratie')/getitems HTTP/1.1
GET /sites/Z010/00001/_api/site/rootweb?$select=Url HTTP/1.1
POST /sites/Z010/_api/web/lists/getByTitle('Configuratie')/getitems HTTP/1.1
and all is fine
Observed Behavior
However in Internet explorer the browser keeps repeating the following kind of calls without getting any further:
Request URL: https://0-westeurope1-pushp.svc.ms/socket.io/?token=w1-21ca35c1-fc20-4273-8646-83ef9e5fbdee&EIO=3&transport=polling&t=MZ7vdf5&sid=0hrVy9Da0JEyTf9aBUPp
Steps to Reproduce
run extension in chrome/edge/ie. Is a custom component for a customer, maybe I can create a test component performing only list access code to try and simulate this behavior.

Hi, does your exrenation use pnp.js-core? i'd so, did you install the ie111 shim?

Fixed using this package: https://pnp.github.io/pnpjs/documentation/polyfill/


deactivate:unset:1: no such hash table element: pydoc

I have upgraded oh my zsh to the latest version. Still, when I activate my virtual environment, I get this line after opening a new terminal or tab. Please suggest a solution.

Which OMZ plugins are you using, and which version of virtualenv are you running?

I am using virutalenv==14.0.1 and zsh 5.0.2 (x86_64-pc-linux-gnu).

I'm experiencing this too.
I'm running virtualenv version 14.1.0.dev0 and zsh 5.0.8 (x86_64-apple-darwin15.0)
plugins=(git brew dirhistory docker history jsontools pylint python virtualenvwrapper)

This bug has nothing to do with zsh, the problem is with virtualenv. It is fixed in version 15.0.0, but it will persist for venvs created with an earlier venv. You can change in the deactivate function the line unset -f pydoc to unset -f pydoc >/dev/null 2>&1.


Fix constructor deprecation/overload

There is an error in the constructor overload for deprecated constructors, resulting in the new constructor argument to be undefined.
Steps to repro:  Start asm customer emulation and it will not work.  The following error will print in the console.
core.js.pre-build-optimizer.js:7187 ERROR TypeError: Cannot read property 'getOccUserId' of undefined
    at Object.load (spartacus-core.js.pre-build-optimizer.js:24324)
    at Qt._tapNext (spartacus-core.js.pre-build-optimizer.js:24314)
    at Qt._next (tap.js.pre-build-optimizer.js:40)
    at Qt.next (Subscriber.js.pre-build-optimizer.js:49)
    at o._next (distinctUntilChanged.js.pre-build-optimizer.js:50)
    at o.next (Subscriber.js.pre-build-optimizer.js:49)
    at o._next (map.js.pre-build-optimizer.js:35)
    at o.next (Subscriber.js.pre-build-optimizer.js:49)
    at e._subscribe (BehaviorSubject.js.pre-build-optimizer.js:14)
    at e._trySubscribe (Observable.js.pre-build-optimizer.js:42)

PR #4131


Can't add cookie

Using Splash v2.1 through the browser.
Here is my script:
function main(splash)
    splash:add_cookie("foo", "bar")
    assert(splash:go(splash.args.url))
    return splash:html()
end

Then, I use netcat to sniff HTTP request on the target host:
Connection from [<IP_ADDRESS>] port 8888 [tcp/*] accepted (family 2, sport 54730)
GET / HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) splash Safari/538.1
Connection: Keep-Alive
Accept-Encoding: gzip, deflate
Accept-Language: en,*
Host: <IP_ADDRESS>:8888

I think that Cookie section Cookie: foo=bar should be displayed on the HTTP request.
But it doesn't.
I will kindly appreciate any help from you.

Solved

I have same issue on 2.3 from docker. How you solved it ?

@novoxudonoser you should include the path and hostname into cookie as well.
for example:
splash:add_cookie("name", "bar", "/", "example.com")


Hotfix/anon link pdfs

pinging @caileyfitz @nicipfeiffer to make a note of this for the next round of testing


Proposal: increase self-bond scoring weight to 200 points

As discussed in the 1kv Polkadot element room, I'd like to request the self-bond scoring weight to be increased to 200 points.
Currently there is virtually no benefit to having a high self-bond, validators which have joined the programme on good intention get the same amount of elections as those with over 10,000 $DOT bonded. Encouraging validators to have a high self-bond is important to push operators towards becoming a trustworthy and independant brand.
If the self-bond weight won't be changed sufficiently, 1kv validators will likely unbond funds to be used for staking and recouping maintenance costs. By not staking funds validators currently miss out on ~3.86 DOT ($28.74) every single day (when bonding 10,000 $DOT).
Those with high self-bond show confidence in their validator operation and endure additional expense. These validators should be rewarded accordingly.

I personally belive that having contributed to the community and having passed the good intentions evaluation is more valuable than being able to show strong financial support for the validator.
Maybe it would be worthwhile if we can explore the option of rewarding people with high self-stake and great community contributions to get the good intention status, so they can release their self-stake.

I personally belive that having contributed to the community and having passed the good intentions evaluation is more valuable than being able to show strong financial support for the validator.
Maybe it would be worthwhile if we can explore the option of rewarding people with high self-stake and great community contributions to get the good intention status, so they can release their self-stake.

I strongly disagree, at the end of the day the goal for 1kv is to create validators which are self-sustained and get into the election cycle by themselves. Having a substantial amount of skin in the game ensures proper validator management, which is good for the network and stakers. Further more it encourages decentralisation. You won't want to host on AWS for example in case of a black swan event and possibly get slashed losing your self-bond.
Community contributions are great, though you cannot run a network on it.

Thanks for bringing this up: Maybe it’s best to discuss this here: https://gist.github.com/wpank/054ba0170e21786e4e8acaed9dbea7c1 together with all other ideas/changes.


Scrape platform yaml depreciated/being removed

The latest version of Home Assistant Core now warns that scrape is being moved to the UI, and should no longer exist as a yaml entry.
With this in mind, I to believe this may benefit from being turned into an integration. While it can be run from a number of sensors and some data grabs, that could be said of any number of integrations out there. It would also allow for easier updating.

Thanks for getting in touch.
I traced the 'scrape is being moved to the UI' to here.
The workaround is to configure the scrape sensor in the UI Settings. Perhaps documentation for this could be updated to include this new step? Would you be able to contribute a step-by-step guide by adding it here?
Because there is a workaround, at this time I don't see a compelling reason to make a whole new integration.
Life is busy right now, and there is a lot of change going on. When I find time to learn Python and then to learn whatever APIs in Home Assistant are needed, then I would be in a position to write one. That could take considerable time.

I have updated the package yaml to comment-out the Scrape entity, and have given a guide for how to configure the Scrape sensor in the README.md. This acts to restore the as-is functionality.

Did that scrape setting work for you? It seems like no matter what I try, it fails. It wont accept naked versions of the non alphanumeric characters, and escaping them leads to the sensor always reporting as unknown.

idem

Did that scrape setting work for you? It seems like no matter what I try, it fails. It constantly errors with naked versions of the non alphanumeric characters, and escaping them leads to the sensor always reporting as unknown.

@KairuByte  @uroh
Select must be >  dd:TotalImpressions[PEID="5082"]

Unfortunately, setting that through the UI results in the sensor going into the "Unavailable" state.

for me it worked after changing  that line. can be your printer has a different PEID ?

I have changed the package with the new template sensors, also removed the use of scrape and ping.
Where can i place this?

A fork would likely be best, with a PR in case Eventually wants to pull it back.

A fork would likely be best, with a PR in case Eventually wants to pull it back.

I did something haha, I hope it's correct now.
Please note, you need a hacs integration, the link is in the file.
The automation could also use rework, to the new template (instead of automation), but that is beyond my knowledge.

@KairuByte @Ricks88 just came across this and would like to set it up for my envy Instant Ink printer. Where can I find the latest files?

https://github.com/Ricks88/HASS_HPInstantInk


When the icon is cliked and a date and time is selected, the calendar closes but the bubble animation on the icon still remains.

this caused due to re focusing button after date is selected

Do we have any work around for this?

there is no fix, its kept that way only

Thanks !


Expand Information Model coverage

sdmx1 currently covers all widely-used features from the SDMX 2.1 IM §§1–6 and §10 (with some exceptions; see below). Other parts of the IM are uncommon or not visible anywhere in “the wild,” but could still be implemented if there is desire/resources.
This is a master issue for discussing these and tracking other issues and PRs.

As of v2.6.0, bold and “some examples exist” refer to cases where one or more sources currently return actual messages that cannot be parsed by code (as of version 2.6.0). These are excluded from tests here:
https://github.com/khaeru/sdmx/blob/300a3885bac31605bbc439e727afc72747f3b360/sdmx/tests/test_sources.py#L32-L38
As of v2.13.0, all of these exclusions have been removed.

§7 Metadata structure definition and metadata structure set.

#73.
#105 added MetadataflowDefinition, MetadataStructureDefinition.

§8 Hierarchical code list. The base Codelist is already hierarchical; the chief difference is this one seems to support multiple hierarchy.

Some examples exist.
Classes: HierarchicalCodelist, HierarchicalCode, Level, Hierarchy, CodingFormat.
#152.

§9 Structure set and mappings.

Some examples exist.
Base classes: StructureSet, StructureMap, ComponentMap.
Individual classes: ConceptSchemeMap, CategorySchemeMap, CodelistMap, OrganisationSchemeMap, ReportingTaxonomyMap, ConceptMap, CategoryMap, CodeMap, OrganisationMap, ReportingCategoryMap.
#152 (partial)

§10 Constraints. All visible usage is covered, but some imaginable applications are not.
§11 Data provisioning. Partly covered. Some of these classes map very neatly to existing functionality in SDMX, e.g. RESTDataSource could be very similar to Source. However, they are somewhat underdefined; e.g. the IM does not specify property names for all the information that has—in practice, in this package—proven necessary to track actual behaviour of sources, etc.
§12 Process and §13 Transformation and expressions. These sections appear useful, but there are no (?) real-world examples and specimens to check behaviour against, so implementation is probably premature.

Closing, as the initial set of items have all been addressed.
Additional issues can be opened for specific improvements in IM coverage or alignment.


Possible bug in Mesh scaling?

Hi there,
There may possibly be a bug in the mesh scaling in bGUI as I seem to be having an issue with the GUIPanel/GUIText.
In a normal Babylon mesh, I can do scaling like:
myMesh.scaling = new BABYLON.Vector3( 2, 2, 2 );		// will double the size of the mesh
...but in a GUIPanel, when I do:
myGUIPanel.mesh.scaling = new BABYLON.Vector3( 2, 2, 2 );
nothing seems to appear.
I notice when I go:
myGUIPanel.mesh.scaling = new BABYLON.Vector3( 100, 100, 100 );
it does appear (albeit smaller), and when I do:
myGUIPanel.mesh.scaling = new BABYLON.Vector3( 200, 200, 200 );
it is even bigger.
Is this a bug and can it be looked into, or is there another way to do it for the GUIPanel/GUIText ?
Thanks muchly again,
bws.

Hello,
bGUI update the scaling of the mesh, to adapt the panel to the given texture. You have to use this if you want to scale your panel:
panel.mesh.scaling.scaleInPlace(2); // Will scale by 2 the panel


Remove border-radius from section and column

Currently the documentation makes it seem like border-radius should work for mj-section and mj-column, but according to the issues #1104 and #1510 this is known not to work. I propose removing these attributes for these elements if there is no way to fix this.

It still works for background color, and there’s a way to get around it within the first issue. So I don’t see why we should remove it.

On 12 Jul 2019, at 15:35, PMunch<EMAIL_ADDRESS>wrote:
Currently the documentation makes it seem like border-radius should work for mj-section and mj-column, but according to the issues #1104 and #1510 this is known not to work. I propose removing these attributes for these elements if there is no way to fix this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe rename it to background-radius then? I just spent a lot of unnecessary time trying to figure out why this didn't work. At the very least leave a note on this in the documentation..

A warning can be added in the doc, yup. Renaming an attribute will break a lot of templates, so this is not a good solution.

On 12 Jul 2019, at 15:58, PMunch<EMAIL_ADDRESS>wrote:
Maybe rename it to background-radius then? I just spent a lot of unnecessary time trying to figure out why this didn't work. At the very least leave a note on this in the documentation..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

That's a fair point, but as it stands now it's mis-named. It doesn't change the border radius, so naming it border-radius isn't very intuitive. Especially as it shares the same name as the CSS property that does change the border radius. Does mjml support deprecation?

Oh and by the way, the workaround in #1104 doesn't work for multiple columns with borders.

It would need to release a major version only for that...
I don’t really think the name is an issue as it‘s applied as a css border-radius in the final output. It’s not like mjml introduce this behavior, this is how the CSS properties works.
A small warning on the doc will be enough.

On 12 Jul 2019, at 16:03, PMunch<EMAIL_ADDRESS>wrote:
That's a fair point, but as it stands now it's mis-named. It doesn't change the border radius,  naming it border-radius isn't very intuitive. Especially as it shares the same name as the CSS property that does change the border radius. Does mjml support deprecation?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Changing the title


Deprecating tf2 C Headers

Related to this pull request in geometry2 in which we deprecated the .h style headers in favor of .hpp.

This is from rolling onward, there aren't any plans of back porting yet.

This is from rolling onward, there aren't any plans of back porting yet.

Thank you!
We will have to wait for the original PR to be merged and then we can get back to this.
In the meantime, Can you add conditioning in the code so that from rolling on it uses the .hpp, and in the prior versions it uses the .h version?

@CursedRock17 I changed this PR to draft for now. Once your original PR is merged, please mark it as ready

With the recent backports merged, this PR should be good for review.

The backport to jazzy hasn't been released yet, and on rolling it seems that they are not yet available on testing repo although the PR on rosdistro was merged. Let's wait until then, then we could merge because the binary-main jobs are failing already because we did the same with realtime_tools headers.


Integrate prefilight checks into react app

What is the feature that you would like to see in the app? Please describe.
Could we please add the pre-flight checks into the react app
Is your feature request related to a problem? Please describe.
Users with poor connections are surprised by bad call quality
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.

@timmydoza now that the version has been updated, any chance this might come soon... ish? Thanks

We are also looking forward to this returning. It seems like a useful feature.


Music Continues to Go Through The Speakers Despite Despite The Presence of Bluetooth Headphones

Describe the bug
Audio does not go through Bluetooth headphones despite it being the default audio device and all other sounds playing through the Bluetooth device.  The "RestartIntegratedClient" and "RefreshPlayback" tools do not resolve the problem.  This was tested with Spotify_Player being built with the 'rodio-backend' and 'alsa-backend' on 0.16.1 and 'rodio-backend' on 0.16.2
To Reproduce
Pair a Bluetooth device, launch Spotify_Player, and try playing a song.
Expected behavior
Audio successfully playing through the paired Bluetooth deveice.
Log and backtrace
Reference log and backtrace, which are usually located in $HOME/.cache/spotify-player/, of a run reproducing the bug.
The backtrace log is empty with first try on 0.16.1 but on 0.16.2 with trying to get it to work did I get a "No playback devices" error with trying  "RestartIntegratedClient" and "RefreshPlayback" once or a few times.  That produced a proper backtrace log:
Got a panic: PanicInfo {
    payload: Any { .. },
    message: Some(
        called `Result::unwrap()` on an `Err` value: StreamError(DefaultStreamConfigError(DeviceNotAvailable)),
    ),
    location: Location {
        file: "/home/nathan/.cargo/registry/src/index.crates.io-1cd66030c949c28d/librespot-playback-0.4.2/src/audio_backend/rodio.rs",
        line: 178,
        col: 53,
    },
    can_unwind: true,
    force_no_backtrace: false,
}

Stack backtrace:
   0: backtrace::capture::Backtrace::new
   1: spotify_player::init_logging::{{closure}}
   2: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:2021:9
      std::panicking::rust_panic_with_hook
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:735:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:609:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/sys_common/backtrace.rs:170:18
   5: rust_begin_unwind
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
   6: core::panicking::panic_fmt
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
   7: core::result::unwrap_failed
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/result.rs:1652:5
   8: librespot_playback::audio_backend::rodio::mk_rodio
   9: std::sys_common::backtrace::__rust_begin_short_backtrace
  10: core::ops::function::FnOnce::call_once{{vtable.shim}}
  11: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:2007:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:2007:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/sys/unix/thread.rs:108:17

Environment

OS: Ubuntu Noble 24.04 LTS (Development Branch)
Application version: 0.16.1 for when 'alsa-backend' was tested and 'rodio-backend' for both 0.16.2 and 0.16.1 (so it appears that there that this issue is still present on 0.16.2)
Application features: if applicable, provide cargo features used to build spotify_player

Default settings apart from the one instance from when the backend being changed to 'alsa-backend' in which the application was built with '--no-default-features --features alsa-backend'
Additional context
It's highly unlikely that this is something that relates to my device's architecture, but the device Spotify_Player is being used on is an ARMv7h device.  I also used Clang as the compiler.

This is the first time I have seen this kind of error. A brief search leads me to https://github.com/RustAudio/rodio/issues/267. Can you try to install pulseaudio-alsa to see if it fixes the issue?

Whoops!  I should've mentioned that semi-recently did Ubuntu drop PulseAudio in favor of PipeWire.  My system has both pipewire-alsa and pipewire-pulse
Is this project not compatible with PipeWire sound systems?
If I had to guess, it looks like it could work somehow: Issue #299

I don't mean to bring up an old issue, but I am having the same problem as @nathan-2006 and haven't had any luck to solve it. I am just relying on ALSA/Pipewire for audio but I get the same error whenever I try to select my arch linux as a device. DId you end up figuring out how to fix it?
@aome510 I know you brought up to install pulseaudio-alsa but I am using pipewire (with pipewire-pulse installed). I am using Arch Linux 6.8.2

I think it should work with pipewire. I no longer have access to Linux machine so couldn't test it myself. Did you get the same DeviceNotAvailable error? You can also try other audio backends to find one that works.

I think it should work with pipewire. I no longer have access to Linux machine so couldn't test it myself. Did you get the same DeviceNotAvailable error? You can also try other audio backends to find one that works.

Yep, I got the same error. I tried the alsa-backend but everytime I tried to play a song it seemed to have crashed to the terminal I am using but not completely. It was weird, it like glitched weird and I had to force close it. It didn't post anything to the .log file or .backtrace file so not sure what was going on there

Does any of rodio examples work for you? For example, cargo run --example music_mp3. I cannot reproduce this issue on my end, so nothing much I can help unfortunately

@aome510 I will try other backends and post back here on how that goes. What determines which audio device is used? When I use a command like aplay -l I have two cards, my main one is first but I know on spotify-tui, I had to specify for that to get used. Is there anything like that for spotify-player?

@aome510 I fixed my issue, I needed to use the pulseaudio backend, then I went into my pavucontrol (volume control) and made sure my audio device was set to primary, and unmuted then everything worked really well!
Note to others, make sure to have pipewire-pulse installed if you are using pipewire since there isn't a direct backend for it

Nice. Glad that you fixed it yourself.

but I know on spotify-tui, I had to specify for that to get used. Is there anything like that for spotify-player?

I'm pretty sure spotify-tui doesn't support specifying audio device as they don't support streaming. I think you may mean Spotify device which spotify_player also supports, but you need to set up Spotify Connect before. Refer to https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect for more details

@aome510 Ah, you're right, I am thinking of the device config option for spotifyd. I am so thankful that spotify-player doesn't rely on something like spotifyd


[RR Request]: Roadmap Voting App v1.0

Open Source Project name
Roadmap
What is your project?
 Users can upvote/downvote on features, add comments, and request new features. Open-source and fully free.
App’s frontend is built with Remix and the backend is built with Rowy (a lowcode platform for Firebase).
Version
1.0
Date
January 26, 2023
Description of breaking changes
nil
GitHub Repo
https://github.com/rowyio/roadmap
Website
https://roadmap.vote
Link to changelog
https://github.com/rowyio/roadmap/releases/tag/v1.0.0
Social media
https://twitter.com/rowyio/status/1618610641618751488?s=20&t=3i5C5IZsb3bY7Uhga-tR0g
Anything else to add?
No response

Congrats on being featured in the Dec/Jan Festive Release Radar 🥳

Read the blog here
Check out our GitHub Tweet


Represent output from external executables as raw byte streams

The raw text story in Powershell is kind of annoying right now. There's lots of gotchas with newlines and encodings, so a simple command like type foo.txt > bar.txt ends up turning into type foo.txt | out-file -encoding ascii -nonewline bar.txt (and I might still be missing some edge cases).
If an object isn't already a string array, I usually don't want it to be implicitly coerced into one, since:

This can be a lossy transformation, and can introduce subtle data corruption
I'm usually piping stuff from one file descriptor to another (exe to exe, stdout to exe, exe to stdin, etc.), so all the string encoding/decoding roundtrip does is slow things down

It would be useful if decoding I/O streams could be turned into an opt-in feature of certain operators and cmdlets, instead of being implicitly applied to every external data source. Specifically, the result of (echo.exe "foo`nbar").gettype() should be some kind of Stream type instead of a string array.
Without any other changes, this would massively break existing Powershell code that pipes to/from executables and files. However, it is possible to greatly mitigate this issue if the task of guessing a byte stream's encoding and splitting by newline is instead shifted to the pipe operator and cmdlets. In other words, while echo.exe "foo`nbar" is a stream, echo.exe "foo`nbar" | % { $_ } is still an array of lines, as in previous versions, and each $_ is a string.
Piping without decoding the stream can then be provided as an additional binary operator (perhaps |>). If the RHS of the expression is an invocation of an external process, the stream returned from the LHS should simply be fed into the stdin of the new process invocation. If the RHS is a cmdlet/function, the stream should be passed to it as some well-specified variable, similarly to how $input works now.

I believe it is duplicate https://github.com/PowerShell/PowerShell/issues/1908

@iSazonov Yup, dupe


[FR] Open PDF attachments in the browser instead of downloading

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
I would like to store datasheets as attachments for each parts. When I do so, the datasheet gets downloaded to my PC, which quickly makes a mess in the downloads folder.
Suggested solution
It would be much easier if I could view the file directly in the browser instead of downloading an opening it. As far as I know it's a matter of configuring the webserver to add an additional header to each response containing an attachment PDF:
content-disposition: inline; filename="MyFile.pdf"
This could be toggled by a configuration flag, so people cen pick their preferred behavior.
Update: Unfortunately it's not as simple as changing the webserver config. The link itself has the download attribute in html:
<svg class="svg-inline--fa fa-file-pdf fa-w-12" title="" aria-hidden="true" focusable="false" data-prefix="fas" data-icon="file-pdf" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 384 512" data-fa-i2svg="">SNIP</svg> TS78L00_M2206.pdf
Describe alternatives you've considered
I've considered patching the webserver configuration myself, but I'd rather use a clean official release.
Examples of other systems
It's done this way on most suppliers' sites like Mouser and TME.
Do you want to develop this?

[ ] I want to develop this.

Due to how browsers handle windows context this is currently not possible securely with untrusted inputs that can contain code (ie. PDF datasheets, HTML or similar). We handled attachments as requested in the past and received very simple Proof of Concept files that completely broke/exposed instances.
If you check out how big vendors handle this, there are 2 ways:

you "safeguard" contents (mouser)
host on a separate domain (webshop is www.digikey, media is mm.digikey and "PDF" datasheets are jpg in a custom renderer on www.digikey.com/en/htmldatasheets/*)

both are not feasible if we want to keep deployment simple and use the dev resources we have available economically.

@Bart97 the response by @matmair above outlines our approach. We are erring on the side of good security practice.
You will note that our standard proxy setup forces the "attachment" attribute to anything served from the /media/ path:
https://github.com/inventree/InvenTree/blob/7178b95657a59b16d175e01148b7e25b37f84f5c/contrib/container/Caddyfile#L51

Okay, I wasn't aware that this may create security issues. In such case this issue can be closed.


[BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
The game always freezes randomly and it unfreezes and the loophole continues
And I play the game at 144fps
Bloxstrap Log
N/A

Please send your configuration, specifically your ClientAppSettings.json (FFlag list).
Uploading your Bloxstrap configuration
Or through the Bloxstrap Menu go to FastFlags, FastFlag Editor and press Export JSON and paste it here.

The game always freezes randomly and it unfreezes and the loophole continues

And does this happen only with Bloxstrap? https://github.com/pizzaboxer/bloxstrap/wiki/Switching-between-Roblox-and-Bloxstrap

Issue has stale for over a month, and will be reopened if further information is given.


Provide CLI binaries with release

Please provide compiled binaries with the releases.

Same request as @hans-d .
I'm not a golang developer and I'm looking for a simple CLI tool to validate my JSON in CICD pipeline...

FYI this binary will soon be available in nixpkgs https://github.com/NixOS/nixpkgs/pull/306835

fixed with v6.0.0
see https://github.com/santhosh-tekuri/jsonschema/releases/tag/v6.0.0


Set a default timestamp

Doesn't seem to be a way to set a default timestamp.  I've tried all of these:
builder.field(for: \.date, type: .timestamptz, .default("timezone('UTC', now())"))
builder.field(for: \.date, type: .timestamptz, .notNull, .default("timezone('UTC', now())"))
builder.field(for: \.date, .default("timezone('UTC', now())"))

As it's stored exactly the same as a .timestamp, with the offset calculation only occurring during retrieval when the session timezone is explicitly set (SET timezone = 'America/New_York';), it's just the same, no?
https://github.com/vapor/fluent-postgresql/blob/8e3eb9d24d54ac58c8d04c194ad6b24f0b1b667e/Tests/FluentPostgreSQLTests/FluentPostgreSQLTests.swift#L175


$.ajaxPrefilter is not a function

Latest version produces this error message

This is still an issue
//= require jquery
//= require jquery_ujs

application-fe7c426….js:5570 Uncaught TypeError: $.ajaxPrefilter is not a function
JQuery version: 3.1.1 -ajax,-ajax/jsonp,-ajax/load,-ajax/parseXML,-ajax/script,-ajax/var/location,-ajax/var/nonce,-ajax/var/rquery,-ajax/xhr,-manipulation/_evalUrl,-event/ajax,-effects,-effects/animatedSelector,-effects/Tween,-deprecated

I was using the "slim" version of jQuery (my case:  jquery.3.2.1.slim.min) and got this error.
After I moved to using the complete version, this error doesn't show up anymore.

well mine is w.ejsPrefilter is not a function


supply a filter for camel to underscore

Signed-off-by: GongXunyao<EMAIL_ADDRESS>

 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.GongXunyao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Current coverage is 91.57% (diff: 0.00%)

Merging #790 into master will decrease coverage by 0.06%

@@             master       #790   diff @@
==========================================
  Files           111        112     +1
  Lines         16410      16421    +11
  Methods           0          0
  Messages          0          0
  Branches       3845       3848     +3
==========================================
  Hits          15038      15038
- Misses          659        670    +11
  Partials        713        713

Powered by Codecov. Last update fac1398...d65dc7c


React router integration example

Hey, thanks for great work!
Are you guys planning to create example how to integrate React router v4 with Razzle?

The default setup comes with react router 4 out of the box. What sort of example would you like to see?

You may find this useful: https://github.com/jaredpalmer/react-router-nextjs-like-data-fetching

@knipferrc I'm sorry, i was looking at redux example, thanks for the answer!


Unknown/Undefined behavior with Patient

There appears to be some unknown/undefined behavior around Patient .
Using the following CQL:
library test version '0.0.000'

using QDM version '5.3'

context Patient

define "Initial Population":
	"Patient"

define "Patient":
	true

The result type of my definition Initial Population is QDM.Patient. Also, the result type of the definition Patient is QDM.Patient, but is pointing to the definition defined at 10:1-11:5. This definition should return a boolean, however it appears to be referrencing the Patient defined at 5-1-5:15. This can be shown in this xml:
 <statements>
      <def locator="10:1-11:5" resultTypeName="qdm53:Patient" name="Patient" context="Patient">
         <expression xsi:type="SingletonFrom">
            <operand locator="5:1-5:15" dataType="qdm53:Patient" templateId="Patient" xsi:type="Retrieve"/>
         </expression>
      </def>
      <def locator="7:1-8:10" resultTypeName="qdm53:Patient" name="Initial Population" context="Patient" accessLevel="Public">
         <expression locator="8:2-8:10" resultTypeName="qdm53:Patient" name="Patient" xsi:type="ExpressionRef"/>
      </def>
   </statements>

When using this CQL:
library test version '0.0.000'

using QDM version '5.3'

context Population

define "Initial Population":
	"Patient"

define "Patient":
	true

In this CQL, the definition Patient has a result type of QDM.Patient. It is also referencing the expression from line 5:1-5-18 however, this line is talking about Population and not Patient. This expression should return a System.Boolean. Also, the definition Initial Population has a result type of QDM.Patient and not System.Boolean. This can be shown with this ELM output:
   <statements>
      <def locator="10:1-11:5" resultTypeName="qdm53:Patient" name="Patient" context="Population">
         <expression xsi:type="SingletonFrom">
            <operand locator="5:1-5:18" dataType="qdm53:Patient" templateId="Patient" xsi:type="Retrieve"/>
         </expression>
      </def>
      <def locator="7:1-8:10" resultTypeName="qdm53:Patient" name="Initial Population" context="Population" accessLevel="Public">
         <expression locator="8:2-8:10" resultTypeName="qdm53:Patient" name="Patient" xsi:type="ExpressionRef"/>
      </def>
   </statements>

When using this CQL:
library test version '0.0.000'

using QDM version '5.3'

context Population

define "Initial Population":
	true

Patient is still located in the statements as an expression definition. This can be seen through this ELM output:
      <def locator="5:1-5:18" name="Patient" context="Population">
         <expression xsi:type="SingletonFrom">
            <operand locator="5:1-5:18" dataType="qdm53:Patient" templateId="Patient" xsi:type="Retrieve"/>
         </expression>
      </def>
      <def locator="7:1-8:8" resultTypeName="qdm53:Patient" name="Initial Population" context="Population" accessLevel="Public">
         <expression locator="8:2-8:8" resultTypeName="qdm53:Patient" name="Patient" xsi:type="ExpressionRef"/>
      </def>
   </statements>

Should Patient always be coming out in the list of statements? What is the intended behavior supposed to be when their is a definition named Patient?

One of the things that the model info specifies is what "Patient" means, so that the context Patient statement has meaning. Whenever a context statement is encountered, the translator will automatically add the Patient definition to the library, referencing the patient class specified by the model info.
So the translator should be complaining about a duplicate identifier when the CQL itself also contains a definition for Patient, but that isn't happening. So I'm flagging this as a defect.
As far as Patient versus Population context, the Patient definition is always Patient context, so you can reference it from a Population context expression, but if you wanted a Population context that was the list of all patients, you would have to define a new expression for that, something like:
context Population
define Patients: Patient

When you reference a Patient context expression from a Population context, the result is a flattened list of the Patient context expression evaluated for each element of the Population.
Note that the current CQL-Based HQMF IG requires that measures use only Patient context expressions, so you shouldn't encounter any measures that use Population context yet. We are considering a question in the current ballot about whether that restriction should be relaxed, so if you have any input on that, we'd be interested in your thoughts.

Included in the 1.3 CQL Ballot release.


Accessing a chat that user doesn’t have access to will open a blank chat page without any explanation

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

Action Performed:

Create public room with an user that can use policy rooms (Note that we need to mark visibility as public)
Login to another account that cannot use policy rooms
Access the chat link in 1
Observe that we see a blank chat report page without any content

Expected Result:
It should show not found page
Actual Result:
It shows the bank page
Workaround:
unknown
Platforms:

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

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.2.88-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/227221089-b1ebf1f6-5740-4f36-9f3f-f2aae0324fad.mov
https://user-images.githubusercontent.com/43996225/227221503-ca2a4fec-1b9c-4202-92e7-3f5206e2c596.mp4
Expensify/Expensify Issue URL:
Issue reported by: @tienifr
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679553438113879?thread_ts=1679072391.780749&cid=C049HHMV9SM
View all open jobs on GitHub

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

bumping @kavimuru

@miljakljajic Huh... This is 4 days overdue. Who can take care of this?

@hayata-suenaga has been OOO. Let me know if you're able to reproduce this once you're back online, Hayata! :)

I did the following steps.

Login into the production NewDot with an expensifail.com account (which should be behind beta)
Create a workspace
Create a public room
Login into the production NewDot with a gmail.com in different browser window
Paste the URL of the public room created on step 3
Check the screen

And I still got the following message:

@miljakljajic if you have time, could you also try the reproduction steps to confirm this?

Same! I think we can close this out.

@hayata-suenaga @miljakljajic In step 4, you need to log in to an account that doesn't have access to any room

oh looks like this has been fixed already in this PR.


Check how to use the ExecuteMSO PicturesConvertToSmartArt

This does not help the ArrangePics macro, because there is no way to choose the SmartArtLayout in this ExecuteMso method.
We should close this issue.


helloworld-scene sample project has very low framerate on Pixel 4a

Environment
Please provide the following information about your environment:

OS: Mac, Linux
Version: 1.17.0
Device(s): Pixel 4a

Description
The virocode-helloworld-scene sample project (https://s3-us-west-2.amazonaws.com/virocore/1_17_0/virocore-helloworld.zip) runs at ~1 fps. The virocode-helloworld-ar sample project included in the same file runs much faster. These are the sample projects linked from this page. Is there some additional configuration needed to get the scene example to run properly?
Thanks!

@peterstuart The background image & hdr effect has been disabled. Frame rate is ~2fps on the high-poly scenes.


Lab 11/Ex 1/Task 1/Step 4

Lab: 11
Exercise: 01
Task: 01
Step: 04
This line needs to be modified:
"Note: Review the content of the template and note that it deploys an Azure VM hosting Windows Server 2019 Datacenter."
Modified line should be:
"Note: Review the content of the template and note that it deploys Microsoft SQL Server."

updated


Make a MINGW package: mingw-w64-pdfium?

**Is your feature request related to a problem? Please describe. **
Make a MINGW package, it will bring PDFium to more developers, thanks in advance.
Describe the solution you'd like
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-pdfium/PKGBUILD

Hi,
Im trying add support for Windows. When i reach it i will add the windows package for mingw.


Support one more digit on phone number

Brazilian phone numbers are quite big.
Before it would skip the last digit: +5516981216190
PS: It still doesn't support the full format that we usually do here, e.g. +55 (16) 9-8121-6190

Thanks!


Where is the previous version？

hi, l have a question, if you update the trackers/ocsort_tracker/ocsort by byte, then, Where is the previous version？

I don't know what is the "previous version" you want, but you could find byte implementation at trackers/byte_tracker


Default contracts for non-exposed methods not derived

See attached example
def_exposed.txt

(submitted by Nils Rollshausen)


Update engines to node >=10

Summary
v8 dropped out of LTS support, updating the package.json engines to node v10.

Changelog

[General] [Changed] - Bump supported Node engines to >= 10
Test Plan

I think this is now failing builds:


QuantConnectLean C# does not compile in Visual Studio 2017

Expected Behavior

Actual Behavior

Potential Solution

Reproducing the Problem

System Information

Checklist

[ ] I have completely filled out this template
[ ] I have confirmed that this issue exists on the current master branch
[ ] I have confirmed that this is not a duplicate issue by searching issues

[ ] I have provided detailed steps to reproduce the issue

QuantConnectLean C# source code does not complie in Visual Studio 2017 by getting the following error
Error		Couldn't process file WinForms\LeanWinForm.resx due to its being in the Internet or Restricted zone or having the mark of the web on the file. Remove the mark of the web if you want to process these files.	QuantConnect.Views
How to address it?


Few minor changes (the Ukrainian language)

Wrong declension words missing letters, the letters rearranged places

Thanks for wanting to contribute! However, we use Transifex for our translations. Please make the changes there.