Lottie animation doesn't play after Expo upgrade.

Description
I'm using React Native with Expo. Today I upgraded expo from version 42.0.0 to version 44.0.0(last), and I noticed that my lottie animations doesn't play on iOS and Android. However if I change speed from current to another animation starts to work as expected. autoPlay param set to true.
Steps to Reproduce

Use expo version ^44.0.0
Use lottie-react-native version 5.0.1
Use this code:

<LottieView
                      loop={true}
                      speed={1}
                      style={{height: hp('35%'), alignSelf: 'center'}}
                      autoPlay={true}
                      source={require('./../../../assets/lottie/noPlacesInProfile.json')}
                      renderMode={"SOFTWARE"}
         />

Expected behavior: Animation plays
Actual behavior: Animation doesn't play until I change speed param.
Versions
{
npm: '6.14.13',
ares: '1.17.1',
brotli: '1.0.9',
cldr: '38.1',
icu: '68.2',
llhttp: '2.1.3',
modules: '83',
napi: '8',
nghttp2: '1.42.0',
node: '14.17.0',
openssl: '1.1.1k',
tz: '2020d',
unicode: '13.0',
uv: '1.41.0',
v8: '8.4.371.23-node.63',
zlib: '1.2.11'
expo version ^44.0.0
lottie-react-native version 5.0.1
}

I am experiencing this too. autoPlay doesn't start the lottie animation anymore.
Temp workaround: I have found that works now is to attach a ref and run a .reset() then .play() in a use effect on mount.
hope that helps till we get a fix.

We are also experiencing this issue. autoPlay property no longer starts the animation. We also upgraded from 42 -> 44 sdk.
Temp Workaround:
const lottieRef = useRef<AnimatedLottieView|null>(null);

useEffect(() => {
  if (lottieRef.current) {
    setTimeout(() => {
      lottieRef.current?.reset();
      lottieRef.current?.play();
    }, 100);
  }
}, [lottieRef.current]);

...

<LottieView
    ref={lottieRef}
    loop={true}
    speed={1}
    style={{height: hp('35%'), alignSelf: 'center'}}
    source={require('./../../../assets/lottie/noPlacesInProfile.json')}
    renderMode={"SOFTWARE"}
/>

Hope this helps and looking forward to a fix.

Same problem upgrading react-native without expo.
react: 17.0.2
react-native: 0.66.4
lottie-react-native: 5.0.1
lottie-ios: 3.2.3
Workaround by @bakerj417 works fine.

Also experiencing this issue

Ref values shouldn't be used as dependencies to useState as changing the useRef current value won't trigger an update.
We are using this workaround currently:
const lottieRef = useCallback((node: LottieView | null | undefined) => node?.play(), [])

// ...

<LottieView
    ref={lottieRef}
    // ...
/>

Hmm, interesting. If I create a completely new Expo app the autoPlay work as intended 🤔

npx expo-cli@latest init .
npx expo-cli@latest add lottie-react-native
Add a Lottie animation to assets folder, e.g. countdown_10.json
Replace app.js with:import { StatusBar } from 'expo-status-bar';
import LottieView from 'lottie-react-native';
import { StyleSheet, View } from 'react-native';

export default function App() {
  return (
    <View style={styles.container}>
      <StatusBar style="auto" />

      <LottieView
        autoPlay
        loop
        style={{ width: 200, height: 200 }}
        source={require('./assets/countdown_10.json')}
      />
    </View>
  );
}

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

npx expo-cli@latest start
Scan QR on phone and test out

In my case isn't working either without expo, my workaround:
const lottieRef = useRef(null)

...

useEffect(() => {
    if (pending) lottieRef.current?.play()
    else lottieRef.current?.reset()
}, [pending])

..,.

<LottieView
        ref={lottieRef}
        ...
/>

componentDidMount() {
setTimeout(() => {
this.animation.play();
}, 100)
}
i think auto play is broken even if i call this.animation.play() in componentDidMount will not work but if i give it some time it will work

In my case isn't working either without expo, my workaround:
const lottieRef = useRef(null)

...

useEffect(() => {
    if (pending) lottieRef.current?.play()
    else lottieRef.current?.reset()
}, [pending])

..,.

<LottieView
    ref={lottieRef}
    ...
/>

What did you use for the pending variable?

It's a component prop, but could be an state if you want

<LottieView
    ref={lottieRef}
    loop={true}
    speed={1}
    style={{height: hp('35%'), alignSelf: 'center'}}
    source={require('./../../../assets/lottie/noPlacesInProfile.json')}
    renderMode={"SOFTWARE"}
/>

Don't know what has happend. Now even this solution doesn't work...

We are also experiencing this issue. autoPlay property no longer starts the animation. We also upgraded from 42 -> 44 sdk.
Temp Workaround:
const lottieRef = useRef<AnimatedLottieView|null>(null);

useEffect(() => {
  if (lottieRef.current) {
    setTimeout(() => {
      lottieRef.current?.reset();
      lottieRef.current?.play();
    }, 100);
  }
}, [lottieRef.current]);

...

<LottieView
    ref={lottieRef}
    loop={true}
    speed={1}
    style={{height: hp('35%'), alignSelf: 'center'}}
    source={require('./../../../assets/lottie/noPlacesInProfile.json')}
    renderMode={"SOFTWARE"}
/>

Hope this helps and looking forward to a fix.

Don't know what has happend. Even this workaround stopped working...

@emilioicai we defenetly need your help.

I faced the same issue and I found a workaround that should work.
The thing is ref is passed after first rendering, so we should call ref.current 1 tick later.
const lottieRef = useRef<AnimatedLottieView>(null);

useEffect(() => {
    setTimeout(() => {
      if (lottieRef.current) {
        lottieRef.current.play();
       }
    }, 1);
}, []);

...

<LottieView
    ref={lottieRef}
   ...
/>

Still Experiencing above, @taneba's workaround doesn't work for me.
For some reason, changing the speed causes the animation to play. So, I created a useEffect hook that changes a state from 0.9 to 1 when the component loads:
const lottieRef = React.useRef<LottieView | null>(null);
 const [lottieSpeed, setLottieSpeed] = React.useState();

React.useEffect(() => {
  setLottieSpeed(0.9);

  if (lottieRef.current) {
    setTimeout(() => {
      setLottieSpeed(1);
    }, 100);
  }
}, [lottieRef.current]);

Still Experiencing above, @taneba's workaround doesn't work for me.
For some reason, changing the speed causes the animation to play. So, I created a useEffect hook that changes a state from 0.9 to 1 when the component loads:
const lottieRef = React.useRef<LottieView | null>(null);
 const [lottieSpeed, setLottieSpeed] = React.useState();

React.useEffect(() => {
  setLottieSpeed(0.9);

  if (lottieRef.current) {
    setTimeout(() => {
      setLottieSpeed(1);
    }, 100);
  }
}, [lottieRef.current]);

Actually animation starts working not because you change the speed but because you reload component. Good solution.

Just wanted to chip in that I'm having the same issue and some of the solutions above were working inconsistently for me but this is consistently working for me as a workaround, the animations are always playing now:
import React from 'react';

import LottieView from 'lottie-react-native';

const LottieAnimation = () => {
  const lottieRef = React.useRef<LottieView | null>(null);

  React.useEffect(() => {
    if (lottieRef.current) {
      lottieRef.current.play();
    }
  }, [lottieRef.current]);

  return <LottieView ref={lottieRef} source={require('../../assets/my_asset.json')} />;
};

export default LottieAnimation;

I'm not able to reproduce this issue from a newly created expo app. I've got the feeling that the problem may lay on how some screens are mounted on an expo app (maybe react-navigation?). Could anybody share a repo in which I can reproduce this issue?

@kieuquang1110tt Can you share a repo with me where autoplay is failing? I couldn't reproduce it at all

I would need to get access to a repo in which this is happening as I couldn't reproduce in any of my tests.
@tarasvakulka not required but recommended. Previous versions may or may not work

I would need to get access to a repo in which this is happening as I couldn't reproduce in any of my tests.
@tarasvakulka not required but recommended. Previous versions may or may not work

@emilioicai Repo with reproducible demo app -> https://github.com/tarasvakulka/lottie-example-app
There are two ways to reproduce:

Just move app to background and open from background again - animation does not autoplay. For comparing,  on "lottie-react-native": "4.1.3" this bug doesn't appear.
Build release .ipa and open it on IPhone 12 Pro Max IOS 15.5, immediately after app launch you can see that autoplay doesn't work, because animation doesn't play (I also tested on IPhone X and this way doesn't work for it, only first one with move to background and reopen).

@emilioicai Did my repo with example help you to reproduce the bug ? Or may be would be better to create new issue for that ?

For me autoPlay is working perfectly fine one Expo 45. But all the methods on the ref are not working. Only with the   setLottieSpeed(0.9); fix I got it to work on iOS but not android.
"lottie-ios": "3.2.3",
"lottie-react-native": "^5.1.3",
"react-native": "0.68.2",
"expo": "^45.0.0",

import React from 'react';

import LottieView from 'lottie-react-native';

**Many attempts so far, this works great Good job!!**🥳🥳🥳

None of the above workarounds worked for me, but this mish-mash combining answers from @jerearaujo03  and @salmanExpo  did.
    // temp lottie fix begin
    // @see https://github.com/lottie-react-native/lottie-react-native/issues/832
    const lottieRef = useRef(null);
    useEffect(() => {
        lottieRef.current?.reset();
        setTimeout(() => {
            lottieRef.current?.play();
        }, 100)

    }, []);
    // fix end

My workaround:
    const anim = useRef(null);

    useEffect(() => {
        setTimeout(() => {
            anim.current.play();
        }, 0)
    }, [])

Just calling setTimeout function takes enough time as @taneba said.

Ah, nice, I'll try that later @d-rumal, thanks!

None of the workarounds here have worked for me, I'm on Expo SDK 45

Try my fix, but set the timeout to 0, no delay was actually required. BTW i'm on Expo SDK 46

How can I use the workaround with setTimeout and refs if I'm looping through multiple animations using map function and displaying all of them?

I'm still have the same issue. autoPlay doesn't work
I'm using:
"expo": "^47.0.0",
"lottie-react-native": "5.1.4",

import React, { useState, useRef,useEffect } from "react";
import { StyleSheet, View, Text, TouchableOpacity,Animated,Easing } from "react-native";
import Swiper from "react-native-swiper";
import ImageModal from "react-native-image-modal";
import { RFValue } from "react-native-responsive-fontsize";
import Button from "../../components/Common/Button";
import LottieView from 'lottie-react-native';
const OnboardingScreen = ({navigation}) => {
const [currentIndex, setCurrentIndex] = useState(0);
const progress = useRef(new Animated.Value(0)).current;
const progress2 = useRef(new Animated.Value(1)).current;
// // const animationRef = useRef(null)
const lottieRef = useRef(null);
const swiperRef = useRef(null);
const handleNext = () => {
if (currentIndex < 3) {
swiperRef.current.scrollBy(1);
}
};
const handleGetStarted = () => {
navigation.navigate('SignupScreen')
};
const renderNextButton = () => {
if (currentIndex < 3) {
return (

<TouchableOpacity
onPress={()=>navigation.navigate('SignupScreen')}
>
Skip

);
} else {
return ;
}
};
const handleLikeAnimation = () => {
Animated.loop(
Animated.timing(progress, {
toValue: 1,
duration: 3000,
easing: Easing.linear,
useNativeDriver: true,
})
).start();
};
useEffect(() => {
handleLikeAnimation();
}, []);
const handleLikeAnimation2 = () => {
Animated.loop(
Animated.timing(progress2, {
toValue: 1,
duration: 3000,
easing: Easing.linear,
useNativeDriver: true,
})
).start();
};
useEffect(() => {
handleLikeAnimation2();
}, []);
return (

<Swiper
ref={swiperRef}
loop={false}
showsPagination={false}
onIndexChanged={(index) => setCurrentIndex(index)}
>
{/* First onboarding screen */}

  <LottieView
      progress={progress}
      source={require('../../assets/images/finance.json')}
      autoPlay={true}
      loop={true}
      style={{width:300,height:300}}

    />

      </View>

      <View style={styles.pagination}>
        {[0, 1, 2, 3].map((index) => (
          <View
            key={index}
            style={[
              styles.dot,
              currentIndex === index ? styles.activeDot : null,
            ]}
          />
        ))}
      </View>

      <Text style={styles.title}>All your accounts in one app</Text>
      <Text style={styles.desc}>
        See all your bank accounts and{"\n"}
        digital wallets without having to{"\n"}
        switch to other apps.
      </Text>
    </View>

    {/* Second onboarding screen */}
    <View style={styles.slide}>
      <View style={styles.gifContainer}>
      <LottieView
      progress={progress}
      source={require('../../assets/images/payment.json')}
      autoPlay={true}
      loop={true}
      style={{
        width: RFValue(300),
        height:RFValue(300),
      }}
    />
      </View>

      <View style={styles.pagination}>
        {[0, 1, 2, 3].map((index) => (
          <View
            key={index}
            style={[
              styles.dot,
              currentIndex === index ? styles.activeDot : null,
            ]}
          />
        ))}
      </View>

      <Text style={styles.title}>Send money or payments instantly </Text>
      <Text style={styles.desc}>
        Make payments fast and easy{"\n"}
        using a single point to initiate{"\n"}
        all transactions.
      </Text>
    </View>

    {/* Third onboarding screen */}
    <View style={styles.slide}>
      <View style={styles.gifContainer}>
        <ImageModal
          disabled
          imageBackgroundColor="#fff"
          style={{
            width: 300,
            height: 300,
            alignSelf: "center",
            backgroundColor: "red",
            marginTop: 25,
          }}
          // source={require('../../assets/images/test.gif')}
        />
      </View>

      <View style={styles.pagination}>
        {[0, 1, 2, 3].map((index) => (
          <View
            key={index}
            style={[
              styles.dot,
              currentIndex === index ? styles.activeDot : null,
            ]}
          />
        ))}
      </View>

      <Text style={styles.title}>See expenses and income </Text>
      <Text style={styles.desc}>
        Every spending counts. Get statements{"\n"}
        of your accounts and wallets within{"\n"}
        the app.
      </Text>
    </View>

    {/* Fourth onboarding screen */}
    <View style={styles.slide}>
      <View style={styles.gifContainer}>
        <ImageModal
          disabled
          imageBackgroundColor="#fff"
          style={{
            width: 300,
            height: 300,
            alignSelf: "center",
            backgroundColor: "red",
            marginTop: 25,
          }}
          // source={require('../../assets/images/test.gif')}
        />
      </View>

      <View style={styles.pagination}>
        {[0, 1, 2, 3].map((index) => (
          <View
            key={index}
            style={[
              styles.dot,
              currentIndex === index ? styles.activeDot : null,
            ]}
          />
        ))}
      </View>

      <Text style={styles.title}>Set your budget and track it</Text>
      <Text style={styles.desc}>
        Set your financial goals and reach{"\n"}
        them with a simple and intuitive{"\n"}
        budgeting tool.
      </Text>
    </View>
  </Swiper>

  <View style={styles.bottomContainer}>{renderNextButton()}</View>
</View>

);
};
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: "#fff",
},
gifContainer: {
alignSelf: "center",
},
slide: {
flex: 1,
// justifyContent: 'center',
// alignItems: 'center',
},
pagination: {
flexDirection: "row",
justifyContent: "center",
marginTop: RFValue(30),
},
dot: {
width: 8,
height: 8,
borderRadius: 4,
backgroundColor: "#AAA",
marginHorizontal: 4,
},
activeDot: {
backgroundColor: "#000",
},
bottomContainer: {
paddingHorizontal: 16,
paddingBottom: 50,
alignItems: "center",
},
nextButton: {
backgroundColor: "#000",
paddingVertical: 12,
paddingHorizontal: 24,
borderRadius: 24,
},
buttonText: {
color: "#FFF",
fontSize: 16,
fontWeight: "bold",
},
skipText: {
fontSize: RFValue(13),
color: "#65666B",
fontFamily: "SemiBold",
marginTop: 24,
textAlign: "center",
},
title: {
fontSize: RFValue(14),
color: "#181818",
fontFamily: "SemiBold",
textAlign: "center",
marginTop: RFValue(16),
},
desc: {
fontSize: RFValue(14),
color: "#65666B",
fontFamily: "Regular",
textAlign: "center",
marginTop: RFValue(11),
lineHeight: 24,
},
});
export default OnboardingScreen;

I was facing the same issue on IOS side , it was working properly on Android
Here are the steps that I take to solve
Do Import Animated and easing on top
import {,Animated,Easing } from 'react-native
import LottieView from 'lottie-react-native';
const progress = useRef(new Animated.Value(0)).current; (Before Return Statement)
(before Return)
const handleLikeAnimation = () => {
Animated.loop(
Animated.timing(progress, {
toValue: 1,
duration: 3000,
easing: Easing.linear,
useNativeDriver: true,
})
).start();
};
After Retrun (Our lottie code)
<LottieView
progress={progress}
source={require('../../assets/images/finance.json')}
autoPlay={true}
loop={true}
style={{width:300,height:300}}
    />

    Hopefully this works :)

For me just install lottie again with npx expo and it works for expo 48.  npx expo install lottie-react-native.

This shouldn't be closed. Still happening with Expo 52 and React Native 0.76.3


[Bug]: Test Issue 6

Connector Name
module/azure-ad (Azure Active Directory)
What happened?
A bug happened!
Relevant log output
No response

Closing as a test issue.


Lean 2651

@asouqi do you think it makes sense to have the locales here directly rather than exposed in the api?

that will be ok in case we are going to support just one or a couple of languages, but if we need to support all of them it's to add to the app size 1.2 MB

I suggest we support a single locale by default here. If we need any more, we need to pass the locale XML through parameters the same way we send in the style. What do you think?

I suggest we support a single locale by default here. If we need any more, we need to pass the locale XML through parameters the same way we send in the style. What do you think?

that is a great idea, update it based on that.


Repeating a field in validate_required will generate duplicate errors for the field

Elixir version
Erlang/OTP 23 [erts-11.1.8] [source] [64-bit] [smp:10:10] [ds:10:10:10] [async-threads:1] [hipe]  Elixir 1.13.0 (compiled with Erlang/OTP 22)
Database and Version
Postgres 14.1
Ecto Versions
3.8.4
Database Adapter and Versions (postgrex, myxql, etc)
0.16.3
Current behavior
Repeating a field in validate_required will generate duplicate errors for the same field. This is cascading to view layer like duplicate error tags being generated for the same field.
row
|> cast(attrs, [:id, :name])
|> validate_required([:id, :name, :name])

#Ecto.Changeset<
  action: :validate,
  changes: %{id: 1},
  errors: [
    name: {"can't be blank", [validation: :required]},
    name: {"can't be blank", [validation: :required]}
  ],
  data: #ExampleSchema<>,
  valid?: false
>

Expected behavior
Generate one error per field for validate_required.

I was not trying to validate the list twice. In a schema with long list of fields - i had included the same field twice and i discovered this bug.
https://github.com/elixir-ecto/ecto/blob/fa35655eb56db97698c6b7f0af4c7fad70d04811/lib/ecto/changeset.ex#L1816
should be
fields = fields |> List.wrap() |> Enum.uniq()

If same field is validated twice, it wont generate duplicate errors.
row
|> cast(attrs, [:id, :name])
|> validate_required([:id, :name])
|> validate_required([:id, :name])

For this reason, I feel this is a bug and fix is quite simple.

I'm not too sure about this but will let the others weigh in. By your own examples/explanation the problem is the user mistakenly specifying the same fields more than once when they don't want to. It seems reasonable to generate the message as many times as the user asks.

Yes, for now I am more inclined to say it is a user error too. We can always change it later if it a common mistake for osme reason.

Just to be clear - i am not expecting any fix.
Few observations:

changeset.required is supposed to be a uniq list or a list?
changeset.errors and changeset.required are deduped using Enum.uniq  in changeset cast_merge:
https://github.com/elixir-ecto/ecto/blob/fa35655eb56db97698c6b7f0af4c7fad70d04811/lib/ecto/changeset.ex#L968-L972
in validate_required it is quite opposite - no such checks exists and fields are just appended.
when there is an error on the field - further validations for the field are not done in validate_required, except this scenario.
https://github.com/elixir-ecto/ecto/blob/fa35655eb56db97698c6b7f0af4c7fad70d04811/lib/ecto/changeset.ex#L1818-L1824

The expectations of a merge operation are quite different than handling a list of user-provided atoms. Merge means roughly "insert new information AND update existing information on conflict". So for error messages that are the same they would be ignored instead of inserting a duplicate.

any thoughts on whether changeset.required is uniq or a list?

It's a list and not a set, if that's what you mean by 'uniq'.


Update image ghcr.io/gethomepage/homepage to v0.9.2

This PR contains the following updates:

Package
Update
Change

ghcr.io/gethomepage/homepage
patch
v0.9.1 -> v0.9.2

Release Notes

gethomepage/homepage (ghcr.io/gethomepage/homepage)
v0.9.2
Compare Source
What's Changed
Security

This release addresses a vulnerability that could allow leakage of API keys from weather widgets, see https://github.com/gethomepage/homepage/security/advisories/GHSA-cjgf-vhj6-8cx4 . Thanks to Kwstubbs for reporting.

App changes

Fix: caddy widget broken in v0.9.1 by @shamoon in https://github.com/gethomepage/homepage/pull/3579
Fix: omada widget broken in v0.9.1 by @shamoon in https://github.com/gethomepage/homepage/pull/3587
Fix/handle null id in json rpc responses and cpu load representation for openwrt widget by @LiranV in https://github.com/gethomepage/homepage/pull/3576
Fix: wg-easy threshold not properly computed by @ConnerWithAnE in https://github.com/gethomepage/homepage/pull/3574
Enhancement: support multiple instance annotation for Kubernetes Automatic Service Discovery by @aldycool in https://github.com/gethomepage/homepage/pull/3590
Fix: coinmarketcap widget dropdown not clickable by @henry40408 in https://github.com/gethomepage/homepage/pull/3591

New Contributors

@LiranV made their first contribution in https://github.com/gethomepage/homepage/pull/3576
@aldycool made their first contribution in https://github.com/gethomepage/homepage/pull/3590

Full Changelog: https://github.com/gethomepage/homepage/compare/v0.9.1...v0.9.2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Support point-in-time queries

To support a DMSDK requirement for point-in-time queries, REST will support point-in-time query on the following endpoints:

/v1/qbe

/v1/search

/v1/values/{name}

/v1/graphs?graph={graph}

/v1/graphs?default=

/v1/graphs/sparql

/v1/rows

/v1/documents

Java Client API should also support these capabilities.  Since QueryHostBatcher is designed to allow clients to do any operation they want on each batch of matching uris, they will use Java Client API to read documents, update them, delete them, etc.

The only way to get the opaque server timestamp value required for subsequent requests is to first make a request.  REST will provide the timestamp as a response header.  We need a way to surface this timestamp through the java client.  Even the following simple methods need a way to surface the server timestamp:
<T extends AbstractReadHandle> T DocumentManager.read  (String uri, T handle)
<T extends TriplesReadHandle>  T GraphManager   .read  (String uri, T handle)
DocumentPage                     DocumentManager.search(QueryDefinition query, long start)
<T extends SearchReadHandle>   T QueryManager   .search(QueryDefinition query, T handle)
<T extends TuplesReadHandle>   T QueryManager   .values(ValuesDefinition query, T handle)
<T extends ValuesReadHandle>   T QueryManager   .values(ValuesDefinition query, T handle)

We could restrict the availability of the timestamp to calls which return DocumentPage, SearchHandle, TuplesHandle, and ValuesHandle.  But that does not offer a solution for DocumentManager.read nor GraphManager.read which can not be used with any of those specific handles.
Therefore I propose we make the timestamp available on any handle which implements
PointInTimeHandle<H> {
    String getServerTimestamp()
    H withServerTimestamp(String timestamp)
}

We can make all built-in handles implement this interface.  This will be a consistent and easy way to retrieve the server timestamp from the response to any of the above methods.  This will also offer an easy and consistent way to specify the timestamp to any of the above methods.      While one might expect to provide the timestamp as part of the query, that's not the way the REST API is implemented and that is not possible on DocumentManager.read nor GraphManager.read which do not and will not have a query argument.
Does anyone see a better API option?

I'm realizing my proposal doesn't address the simplest DocumentManager.search(QueryDefinition, long) since there is no handle argument.  We could require they use DocumentManager.search(QueryDefinition, long, SearchReadHandle) ...

Erik proposed we could follow the model of optimistic write using DocumentDescriptor.setVersion.  If we did, we would obviously need to do the same on QueryDefinition and ValuesDefinition.  I like that idea for query/read requests, however, we would still need to find a solution to get the timestamp from query/read responses.  I think that would lead us directly back to the original proposal where we add a getServerTimestamp() method to all handles.  Is it better to read the server timestamp from the handles but then send the server timestamp via DocumentDescriptor, QueryDefintion, or ValuesDefinition?

ContentDescriptor bundles up some gettable / settable properties of handles, which inherit from ContentDescriptor.
Would it be consistent to call this a TimestampedContentDescriptor and derive ContentDescriptor from it (assuming that anything that can be timestamped also can have a mimetype)?

Great idea.  That sounds similar to what we did with TemporalDescriptor, except that extends ContentDescriptor.  I think we can go ahead and add
interface TimestampedContentDescriptor {
    String getServerTimestamp()
    void setServerTimestamp(String timestamp)
}

I'm hesitant to make ContentDescriptor extend it on the odd chance that someone has implemented ContentDescriptor and would now have their builds break until they add these methods.  Instead, I propose we have BaseHandle implement this interface which will trickle it down to all the handles we've created.

On further reflection, I'm not seeing a need for another interface, so I'll scrap TimestampedContentDescriptor and instead just add the methods to BaseHandle so then all our handles will have them.

Ok, this is all implemented except for /v1/values and /v1/rows.  We'll add support for those later.

Have written basic test and other stubs. Will flesh out the test when Git 457 is completed. Assigning this back to development.

Can we make a few tweaks to the basic tests?

use getServerTimestamp not getPointInTimeQueryTimestamp (that's for internal use only, like everythign in the impl package)
could we try reading the document after update using insTimeStamp and verify that we don't see the update?
why is the test looking at fragment counts?  I'm not seeing a need for that.
why is the test looking at whether the patch update worked?  I'm not seeing a need for that.
I see the comment "Sleep for some time. Read again with new point In time."  that seems like a good idea, but I don't think it will work if nothing else is updating the db because I'm not sure the server timestamp advances unless something performs an update.
in general, let's not wait for 457 as that's a separate round of development.  Can we dig in and verify what we have and that it works even if it's not polished?

Thanks Sam, Will work on the review comments.

Have changed the test to verify:
use getServerTimestamp not getPointInTimeQueryTimestamp (that's for internal use only, like everythign in the impl package)
could we try reading the document after update using insTimeStamp (pass via setServerTimestamp on the read handle) and verify that we don't see the update?
I have left the fragment counts check. Based on how #457 is fleshed out, might remove them later.


MAIN B-18631 All shipment weight values displayed sc closeout

B-18631
INT PR: https://github.com/transcom/mymove/pull/12264
Summary
This adds the ability to see all HHG shipment weights while Closeout SC is closing out a member's PPM.
This is to be displayed to the closeout counselor during their review of the PPM weights.
How to test
Test using ApprovedMoveWithPPMWeightTicketOfficeWithHHG or create your own move.
With ApprovedMoveWithPPMWeightTicketOfficeWithHHG:

Use ApprovedMoveWithPPMWeightTicketOfficeWithHHG testharness.
Find the move as Closeout SC -> review the documents -> You should see Estimated Weight and Approved Weight above PPM 1 on the right side bar.

With your own move:

Create a move with at least one HHG and a PPM shipment.
As a SC -> Submit the move.
As a TOO -> Approve HHG.
As a Prime -> Update Shipment in Prime Sim for the HHG move.
Fill in the appropriate fields and make note of your Actual Weight and Estimated Weight.
As a customer -> Upload your PPM documents.
As a closeout SC -> use the search function to find the move.
Review the PPM document and you should see Estimated Weight and Approved Weight above PPM 1 on the right side bar.

Screenshots

Warnings

:warning:
This PR does not include changes to storybook, even though it affects component code.

  Generated by :no_entry_sign: dangerJS against c8cc8654bae0128f8c4a70718e6c32d8ef0c59f1

closing this since Main is still locked.

Verify rpt.
there was diffs.
B18631-12343.verify_rpt.txt


Tests report does not cover exported function from typescript.

Describe the bug
I have a file called utils.ts in the folder src/logic/utils.ts that has a simple function that adds three numbers.
export function addThreeNumbers(a: number, b: number, c: number) {
    return a + b + c;
}

in the folder src/__tests__/unit/utils.test.ts I have a test for this sum function.
import { describe, it, expect } from 'vitest'
import {addThreeNumbers} from "src/logic/utils";

describe("Sum of three numbers test", () =>{
    it("1 + 2 + 3 = 6",()=>{
        expect(addThreeNumbers(1,2,3)).toBe(6)
    })
})

My vitest.config.ts file looks like this
export default mergeConfig(
    viteConfig,
    defineConfig({
        test: {
            environment: 'jsdom',
            exclude: [...configDefaults.exclude, 'e2e/*'],
            root: fileURLToPath(new URL('./', import.meta.url)),
            coverage: {
                all: true,
                provider: 'c8',
                // move coverage report to ./tests/unit/coverage
                reportsDirectory: './tests/unit/coverage',
                include: ['src/**/*.vue', "src/**/*.ts", "src/**/*.js"],
                exclude: ['src/router', "**/__tests__/**"]
            },
        }
    })
)

I run vitest run --coverage and I see that ✓ src/__tests__/unit/utils.test.ts (1) is ran but
in the report utils.ts has 0 statements covered.
Reproduction
I hope the files provided are enough to see if there is either a bug or I have a misconfiguration somewhere.
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 5.40 GB / 15.35 GB
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (112.0.1722.58)
    Internet Explorer: 11.0.22000.120

    "vitest": "^0.30.1" (from packages.json)

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Could you try removing the test.coverage.include and test.coverage.exclude and see if the file ends up in the report? And maybe even the test.root?

I can reproduce this now.
When source file is imported using alias the vitenode.fetchCache does not contain full path. This gets filtered out in coverage provider.
import {addThreeNumbers} from "src/logic/utils";
// fetchCache contains entry for "src/logic/utils"

import {addThreeNumbers} from "../../logic/utils";
// fetchCache contains entry for "/x/y/z/repro/src/logic/utils.ts" - Includes the extension and full path

The vitest.config.ts is missing alias. Add following and coverage report is OK:
    alias: {
      src: fileURLToPath(new URL("./src", import.meta.url)),
    }

Or as alternative import the utils.ts with full path instead of relying on project root:
- import {addThreeNumbers} from "src/logic/utils";
+ import {addThreeNumbers} from "../../logic/utils";


Fail fast on missing generator

If you are running generate on a model without a generator block (e.g. https://prisma-errors.netlify.com/report/1301), it still seems to do stuff before failing:
C:\Users\Jan\Documents\throwaway\matt>npx prisma2@alpha generate

info You don't have defined any generator in your schema.prisma, so nothing will be generated.
You can define them like this:

generator client {
  provider = "prisma-client-js"
}

You can now start using Prisma Client in your code:

import { PrismaClient } from '@prisma/client'
// or const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()

Explore the full API: http://pris.ly/d/client

this has been fixed. I see this output if i remove generator from my schema
workplace@workplace-VirtualBox:~/WebstormProjects/untitled$ npx prisma generate

Prisma schema loaded from prisma/schema.prisma

info You don't have any generators defined in your schema.prisma, so nothing will be generated.
You can define them like this:

generator client {
  provider = "prisma-client-js"
}

workplace@workplace-VirtualBox:~/WebstormProjects/untitled$

using:
workplace@workplace-VirtualBox:~/WebstormProjects/untitled$ npx prisma -v

@prisma/cli          : 2.11.0
@prisma/client       : 2.11.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine<PHONE_NUMBER>2e47bdcec77a2f1e7c1fb83a463918 (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli<PHONE_NUMBER>2e47bdcec77a2f1e7c1fb83a463918 (at<EMAIL_ADDRESS>Introspection Engine : introspection-core<PHONE_NUMBER>2e47bdcec77a2f1e7c1fb83a463918 (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt<PHONE_NUMBER>2e47bdcec77a2f1e7c1fb83a463918 (at<EMAIL_ADDRESS>Studio               : 0.311.0

I can also confirm this is fixed. Closing!
thanks @muxahuk


(WCAG 2.1) Add either sr-only or visual text to progress bar indicating status

Required to meet WCAG 2.1 guidelines. Identified during an accessibility audit against WCAG 2.1.
WCAG SC: 4.1.2. Name, Role, Value
Observed results: Progress bars on the Program application review page do not provide accessible name or label.
How to fix:
From a11y team:
"Unlike in the application forms where the progress bars have adjacent textual information displayed (e.g. 1 of 5), the Program application review page can actually display different progress bars for the specific application and therefore it must convey some kind of alternative text or accessible label.
Consider adding textual information on top of the bar such as In progress, Completed, Not started; otherwise, provide role and label to the progress bars for screen readers to convey (see: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/progressbar_role)."
From me:
Should check with UX whether we want to add additional visual text. Otherwise, add alt text.

Adding new text seems reasonable. Another alternative would be to try and make these fully consistent with the block editing page and show the "2 of 5" text to the right of the program name. For not started, it'd say "0 of 5" and for completed it'd say "5 of 5".
An advantage of this approach would be that we could fully reuse the existing localized content.

Done


WIP, TST, BUG: bump to OpenBLAS 0.3.9 stable

Fixes #11693, if I'm lucky with my CI changes & we don't have a timeout, which is another recent issue..

local testing suggests that failures in
TestDifferentialEvolutionSolver::test_L4
observed in Azure CI are related to the version
of OpenBLAS linked to SciPy; bumping from 0.3.7
to 0.3.9 stable locally causes the test to switch
from 100 % fail to 100 % pass on 5 repeats

also, the next release of SciPy will likely use
OpenBLAS 0.3.9 stable of higher, so probably good
to bump anyway

It looks like the numbers/situation is a little different on Windows 32-bit vs. my local mac reproducer. Let me try bumping the tols slightly, but only for 32-bit Windows situation, based on the feedback from @mdhaber in the cognate issue.

Changing status to WIP for a while--I think the test is no longer failing, but the timeout issue is just so common that the matrix entry is not really useable. I'm going to iterate in a debug branch on my fork to see if I can slice the Azure times down a bit, esp. for that Win 32 entry. We should be able to stay well below 60 minutes per entry.

Cutting the number of cores used by runtests.py on Windows Azure CI from auto (4) to an explicit 2 seems to reduce the run times by 10-20 minutes (see my fork PR test: https://github.com/tylerjereddy/scipy/pull/29). Even the 32-bit Windows job that has been plaguing us has 14 minutes to spare there now.
So, I've cherry-picked that adjustment into this PR and fingers crossed.

The exact same run on my fork is 13 minutes faster... something is fishy.

I'll try printing the slowest test durations for the Azure Windows runs. If it comes down to just getting a random assignment of bad nodes from a pool of heterogeneous hardware it may just be a waste of debugging time I suppose.
Of course the worst of the offenders, 32-bit Win, tends to just timeout on the main repo (so wouldn't print the times), so I'll do the same measurement on my fork where it doesn't for some reason.

Now Azure is passing and showing the test times in main repo and in fork for effectively the same code/branch. The fork run is faster and the test timing show this too.
So, I'll probably merge this soon & open a separate issue with links to the logs/timings & ping Microsoft/GitHub folks on that.
The Travis CI MacOS hardware seems to be having unrelated problems.


system call not working as expected

When calling the PHP function systemcall on https://github.com/graphp/graphviz/blob/master/src/GraphViz.php#L210
it returns as if an error happened due to dot program returning the response on the STDERR value even when it is not an error.
In order to solve this simply add 2>&1 at the end of the command like this:
system(escapeshellarg($executable) . ' -T ' . escapeshellarg($this->format) . ' ' . escapeshellarg($tmp) . ' -o ' . escapeshellarg($tmp . '.' . $this->format) . ' 2>&1', $ret)

Hey @Santiagoebizmarts, thanks for bringing this up :+1:
I would ask the question: Is it useful to just add 2>&1, this will write everything from STDERR to STDOUT.
I am curious tho, this could be something caused by Graphviz itself or maybe a bug in this project (unlikely but still possible). Can you give me a bit more information on what you're trying to do and what your output looks like (code examples would be great :+1:)

I'm closing this for now due to a lack of feedback, as we can not reproduce this. Please come back with more details if this problem persists and we can always reopen this :+1:


Revert "Merge pull request #6045 from takagi/cusparselt-0.2.0"

This reverts commit f8908e988f89a79ea66344a79a6349fc76cfb829, reversing
changes made to aabdbba5d6c2975b892b99459df051c3d457751c.
I think we should wait the next cuSPARSELt release (https://github.com/cupy/cupy/issues/6134#issuecomment-974624444).

/test

/test

remaining errors to be fixed by #6141


Prototype for converting triton to linalg

Prototype for converting triton to linalg
Introduction
I would like to share with the triton community this on-going work to add support for converting the triton dialect to the linalg dialect. This PR, which includes contributions from myself and my peers at Microsoft, introduces a prototype that supports linalg conversion for a limited number of scenarios. We hope folks will eventually be able to leverage this work in building new back-ends for triton.
Usage
The pass is exposed via triton-opt and can be invoked by using the --triton-to-linalg flag like so:
triton-opt --triton-to-linalg %file

Impact to the triton compiler
This PR introduces the TritonToLinalg pass and its related analyses. The new code is accessible only via triton-opt; it does not introduce any changes to the triton main compilation path.
Implementation details
Even though a valid triton program can perform load and store in arbitrary memory locations, the prototype only supports lowering programs that have structured memory access patterns.
Analyses
As part of the conversion process, there are three important analyses:

Pointer analysis:

This analysis is responsible for extracting structured memory access patterns from a triton program during load and store; it walks the IR and visits relevant instructions to build strided memory accesses in the memref dialect. The analysis is still in its early stage and does not support all scenarios.

Use analysis:

After "Pointer analysis", instructions that are part of memory address calculation will no longer be necessary in a triton program because their semantics have now been captured by memref operations representing strided memory accesses. To aid with removing these instructions safely, we perform Use analysis to mark which instructions are used only in address calculation (called MetaUse) or used in both address calculation and data manipulation (called MixedUse) operations. Those that are MixedUse are cloned and have their users adjusted accordingly with the goal of separating out the MetaUse ops so that they can be safely deleted.

Mask analysis:

This analysis is responsible for handling masked loads and stores.

Conversion strategy
We introduce the TritonToLinalg pass that converts the triton dialect to the linalg dialect on tensors. This means the resulting IR is fully compatible with linalg tiling and fusion transformation passes. As mentioned in the Pointer analysis's description, we do however have to deal with memref instructions at the load and store boundaries and have to convert them to tensors using bufferization.to_tensor. Here's a simple example of what the IR looks like:
tt.func @kernel(%afloat : !tt.ptr<bf16>, %res : !tt.ptr<bf16>) {
  %0 = tt.make_range {end = 128 : i32, start = 0 : i32} : tensor<128xi32>
  %1 = tt.splat %afloat : (!tt.ptr<bf16>) -> tensor<128x!tt.ptr<bf16>>
  %2 = tt.addptr %1, %0 : tensor<128x!tt.ptr<bf16>>, tensor<128xi32>
  %afm = tt.load %2 {cache = 1 : i32, evict = 1 : i32, isVolatile = false} : tensor<128xbf16>
  %3 = "tt.reduce"(%afm) ({
  ^bb0(%arg5: bf16, %arg6: bf16):
    %21 = arith.addf %arg5, %arg6 : bf16
    tt.reduce.return %21 : bf16
  }) {axis = 0 : i32} : (tensor<128xbf16>) -> bf16
  tt.store %res, %3 : bf16
  tt.return
}

after conversion:
func.func @kernel(%arg0: memref<*xbf16>, %arg1: memref<*xbf16>, %arg2: i32, %arg3: i32, %arg4: i32) {
    %cst = arith.constant 0.000000e+00 : f32
    %reinterpret_cast = memref.reinterpret_cast %arg0 to offset: [0], sizes: [128], strides: [1] :
        memref<*xbf16> to memref<128xbf16, strided<[1]>>
    %alloc = memref.alloc() : memref<128xbf16>
    memref.copy %reinterpret_cast, %alloc : memref<128xbf16, strided<[1]>> to memref<128xbf16>
    %0 = bufferization.to_tensor %alloc restrict writable : memref<128xbf16>
    %1 = bufferization.alloc_tensor() : tensor<f32>
    %inserted = tensor.insert %cst into %1[] : tensor<f32>
    %reduced = linalg.reduce ins(%0 : tensor<128xbf16>) outs(%inserted : tensor<f32>) dimensions = [0]
      (%in: bf16, %init: f32) {
        %3 = arith.extf %in : bf16 to f32
        %4 = arith.addf %3, %init : f32
        linalg.yield %4 : f32
      }
    %extracted = tensor.extract %reduced[] : tensor<f32>
    %2 = arith.truncf %extracted : f32 to bf16
    %reinterpret_cast_0 = memref.reinterpret_cast %arg1 to offset: [0], sizes: [1], strides: [1] :
        memref<*xbf16> to memref<1xbf16, strided<[1]>>
    affine.store %2, %reinterpret_cast_0[0] : memref<1xbf16, strided<[1]>>
    return

}

Important details to note:

tt.load (together with all of its related address calculation instructions such as tt.addptr and tt.splat) are lowered to a combination of memref.reinterpret_cast, memref.alloc, and memref.copy. After the initialization of the local buffer, we convert the memref back to a tensor using bufferization.to_tensor; this op is automatically removed during bufferization.

tt.store lowers to a combination of memref.reinterpret_cast and either affine.store or memref.tensor_store:

%reinterpret_cast = memref.reinterpret_cast %arg2 to offset: [...] memref<*xf32> to memref<1024xf32>
%extracted_slice = tensor.extract_slice %15[0] [%21] [1] : tensor<1024xf32> to tensor<?xf32>
%subview = memref.subview %reinterpret_cast[0] [%21] [1] : memref<1024xf32> to memref<?xf32>
memref.tensor_store %extracted_slice, %subview : memref<?xf32>

element-wise arith and math operators are converted to their corresponding linalg.generic version.
tt.dot becomes linalg.matmul.
tt.reduce becomes linalg.reduce; known limitation: only support addf and maxf reduction in the reduction body for now.

Testing
The prototype was tested on the following triton kernel examples:

vector addition
fused softmax
matrix multiplication
layer normalization
fused attention

In addition to testing on the tutorial kernels, I have also added many lit tests covering various scenarios.

Thanks for all this work! I think that this could be very useful for people who want to hook up Triton to existing Linalg-based compiler infra!

Just want to say this is awesome work @nhat-nguyen to bridge into existing Linalg-based compilers like SHARK/IREE.

Awesome work!
We have also internally developed a Triton To Linalg conversion. The RFC is proposed in https://github.com/openai/triton/discussions/1542, there are some differences in the implementation. But I believe there will be opportunities for collaboration in this process to jointly improve the entire mechanism.

Hello,
In PtrAnalysis we encountered a case where arith.select is the parent of tt.addptr and the PtrAnalysis::visitOperand failed to match. This case will possibly produce non-continuous memory accesses and thus memref/linalg fails to capture. We hope to be inspired by you. Thanks.
    %18:2 = scf.for %arg8 = %c0_i32 to %c8192_i32 step %c2048_i32 iter_args(%arg9 = %cst_7, %arg10 = %cst_6) -> (tensor<1x2048xf32>, tensor<1x2048xi64>)  : i32 {
      %27 = tt.splat %arg8 : (i32) -> tensor<1x2048xi32>
      %28 = arith.addi %27, %7 : tensor<1x2048xi32>
      %29 = arith.cmpi slt, %28, %cst_5 : tensor<1x2048xi32>
      %30 = arith.addi %28, %9 : tensor<1x2048xi32>
      %31 = tt.addptr %10, %30 : tensor<1x2048x!tt.ptr<i64>>, tensor<1x2048xi32>
      %32 = arith.andi %29, %11 : tensor<1x2048xi1>
      %33 = tt.load %31, %32, %cst_6 {cache = 1 : i32, evict = 1 : i32, isVolatile = false} : tensor<1x2048xi64>
      %34 = tt.addptr %12, %30 : tensor<1x2048x!tt.ptr<f32>>, tensor<1x2048xi32>
      %35 = tt.load %34, %32, %cst_7 {cache = 1 : i32, evict = 1 : i32, isVolatile = false} : tensor<1x2048xf32>
      %36 = tt.addptr %13, %30 : tensor<1x2048x!tt.ptr<f32>>, tensor<1x2048xi32>
      %37 = tt.load %36, %32, %cst_7 {cache = 1 : i32, evict = 1 : i32, isVolatile = false} : tensor<1x2048xf32>
      %38 = arith.cmpi ne, %33, %cst_3 : tensor<1x2048xi64>
      %39 = arith.select %38, %33, %cst_6 : tensor<1x2048xi1>, tensor<1x2048xi64>
      %40 = arith.cmpi sge, %39, %cst_6 : tensor<1x2048xi64>
      %41 = arith.cmpi slt, %39, %cst_0 : tensor<1x2048xi64>
      %42 = arith.andi %40, %41 : tensor<1x2048xi1>
      tt.assert %42, "index out of bounds: 0 <= tmp4 < 65", "<frozen importlib._bootstrap_external>", "_call_with_frames_removed", 883 : tensor<1x2048xi1>
      %43 = arith.muli %28, %cst_2 : tensor<1x2048xi32>
      %44 = arith.extsi %43 : tensor<1x2048xi32> to tensor<1x2048xi64>
      %45 = arith.addi %39, %44 : tensor<1x2048xi64>
      %46 = arith.addi %45, %16 : tensor<1x2048xi64>
      %47 = tt.addptr %17, %46 : tensor<1x2048x!tt.ptr<bf16>>, tensor<1x2048xi64>
...
%204 = "arith.select"(%200, %95, %19) {MetaUse} : (tensor<1x2048xi1>, tensor<1x2048xi64>, tensor<1x2048xi64>) -> tensor<1x2048xi64>
encountered addptr operand produced by an unsupported operation
UNREACHABLE executed at /wkspc/hongjing/triton/lib/Analysis/PtrAnalysis.cpp:377!

@yuanfz98 Sorry for the delayed response. Would you mind sharing the triton program that produces this error? We don't currently support non-contiguous memory loads so this could be the reason why.

After internal discussion, we have decided that it would make more sense for this useful utility to live out-of-tree, where other out-of-tree third party backends could also use it to build their binaries

PR redone as a plug-in: https://github.com/openai/triton/pull/2374


Loding config Error with lanenet

Running python planner/Frenet/frenet_planner.py with Error:

Loaded settings from /home/rancho/2-ldl/othors/beliefplanning/planner/Frenet/configs/risk.json
Loaded weights from /home/rancho/2-ldl/othors/beliefplanning/planner/Frenet/configs/weights.json
recorded/hand-crafted/DEU_Muc-4_2_T-1.xml >>> <LaneletNetwork/find_lanelet_by_id>: provided id is not valid! id = None

please help to figure it out, thanks！

Similar error:
(myenv) $ python planner/Frenet/frenet_planner.py
Loaded settings from /home/plusai/cp/beliefplanning/planner/Frenet/configs/risk.json
recorded/hand-crafted/DEU_A9-2_1_T-1.xml >>> state_list[0].time_step=0 != self.initial_time_step=1

similiar error :
recorded/hand-crafted/DEU_Muc-4_2_T-1.xml >>> <LaneletNetwork/find_lanelet_by_id>: provided id is not valid! id = None

@KhMustafa  can you help to solve this?

The problem may be related to the versions of the commonroad packages. Are you using the same versions as the ones specified in the requirements.txt file?

@KhMustafa Thanks for the reply!
Yes, we are using a new conda env with Python 3.8, and the packages are installed with requirement.txt

@KhMustafa same problem with @piqiuni !
I try several versions of commonroad packages, but can't be compatible, so probably the provided requirement.txt is wrong.
can you help me check the versions of packages,  and upload a updated requirement.txt with corrent version.

Similiar error.
It should be noticed that the DEU_Muc-4_2_T-1.xml  file obtained by git clone https://gitlab.lrz.de/tum-cps/commonroad-scenarios in project https://github.com/TUMFTM/EthicalTrajectoryPlanning is different to the one in this project. With the same conda environment, I can run EthicalTrajectoryPlanning perfectly but fail to run this project, which seems weird.

Replace the file DEU_Muc-4_2_T-1.xml in this project with the one obtained from git clone https://gitlab.lrz.de/tum-cps/commonroad-scenarios can avoid this error. However, it still fails to yield normal results.

Replace the file DEU_Muc-4_2_T-1.xml in this project with the one obtained from git clone https://gitlab.lrz.de/tum-cps/commonroad-scenarios can avoid this error. However, it still fails to yield normal results.

yeah，I also notice that this file is not consistent with source file in https://gitlab.lrz.de/tum-cps/commonroad-scenarios.
It should also be noticed that this repo has lots of hard code, most of which are related to the initial pos and obstacle pos differenct to the DEU_Muc-4_2_T-1.xml.
so the hard code must be adjust to the same with scenario file.


Checking buffer length is atleast 2

Messages sent to mirror must be atleast 2 bytes for the message type, disconnect if invalid message

hard coding '2' here is not very elegant.

for one, we might change header to any other number of bytes in the future which would silently break this part
secondly, in cases of readpackedint it might be a variable number of bytes. we aren't using it right now, but who knows..

hard coding '2' here is not very elegant.

for one, we might change header to any other number of bytes in the future which would silently break this part

using const instead of magic number, and adding test to make sure that writing the id is the correct length (test will fail if we change size later on, telling us we need to change the IdSize too)

secondly, in cases of readpackedint it might be a variable number of bytes. we aren't using it right now, but who knows..

We should never be using packedint when writing hashs as they will almost always be longer than normal write.


Missing dependencies on Matplotlib

This likely affects other projects as well.
Warehouse data
requires_dist: null
from Matplotlib 3.1.1's dist-info/METADATA file:
Requires-Dist: cycler (>=0.10)
Requires-Dist: kiwisolver (>=1.0.1)
Requires-Dist: pyparsing (!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1)
Requires-Dist: python-dateutil (>=2.1)
Requires-Dist: numpy (>=1.11)

Found this related issues. From what I gather:

The requires_dist field takes info from whatever dist was uploaded first. Ie if it was a source-dist, it shows null.
There's no distinction between no dependencies, and can't-find-dependencies.
Package info on the warehouse won't be changed once set, even if incorrect.

Is this right? I may have to build my own api to cache this; would be more appropriate as pypi, but I'll press with this plan if this truly is a won't-fix.

https://github.com/David-OConnor/pydeps

Can we consider all dependency info on the warehouse unreliable

Yes, see https://dustingram.com/articles/2018/03/05/why-pypi-doesnt-know-dependencies/, which was linked from #6226.

Thanks. IMO this is not resolved and should be attacked by the warehouse, but I'll press with this sideproject in the meanwhile.


Can't infer unique symbol types via another variable

Literals such as 0 can be inferred correctly but unique symbols are not.

TypeScript Version:  3.7.x-dev.20191224

Search Terms:
Code
let revision: symbol;
const rev = revision = Symbol();
rev === revision;

Expected behavior:
Type rev is unique symbol.
Actual behavior:
Type rev is symbol. Can't even declare that rev is a unique symbol.
Playground Link: https://www.typescriptlang.org/play/index.html?ts=3.8.0-dev.20191224&ssl=1&ssc=1&pln=3&pc=18#code/DYUwLgBATiBuCWBneB7AdgLgogngWwCMVgBuAKAGN1FIZYIBeaOJVNRiAZXyOAAoAlOTqMGTOq3QkgA
Related Issues:

Just to make sure I understand.  You're saying this works as you expect:
let wideNumber: number;
const narrowNumber = wideNumber = 0;
// const narrowNumber: 0 👍

but this doesn't:
let wideSymbol: symbol;
const narrowSymbol = wideSymbol = Symbol();
// const narrowSymbol: symbol 😕

Similarly, this works as you expect:
const narrowNumber = 0;
// const narrowNumber: 0
const alsoNarrowNumber = narrowNumber;
// const alsoNarrowNumber: 0 👍

but this doesn't:
const narrowSymbol = Symbol();
// const narrowSymbol: typeof narrowSymbol
const alsoNarrowSymbol = narrowSymbol;
// const alsoNarrowSymbol: symbol 😕

Playground Link
Right?

const alsoNarrowSymbol = narrowSymbol;
// const alsoNarrowSymbol: symbol 😕

Not my intention but probably legal.

Probably somewhat related. unique symbol has some funky widening rules
https://github.com/microsoft/TypeScript/issues/32242

Just hit a similar widening issue to this and the one described by @AnyhowStep on #32242 (now closed). A unique symbol (typeof foo) becomes just symbol when returned from a generic function of the following signature:
function reduce<T>(fn: (value: T, acc: T) => T, initial: T): T {}

String literal types are not widened by this construct, but unique symbol is. 😕


CSS Problem

Hi all ! i am facing problem with materials ui.
I created a new application and sometimes some messages coming up to user screen "Listen what peoples are telling", then i need to reset cache and this problem disappear.

The issue has been closed because it does not conform to our issue requirements.
Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!


Update Composer dependencies (2024-02-01-00-17)

Visual regression test passed!
View the visual regression test report


What's missing is an explanation of how the RangeStart and RangeEnd parameters are set by the service

What's missing here is the inside scoop of how the two values get used by the service.
For instance, in my queries, I have a case where thousands of tables are uploaded each time the refresh runs.  For this I'm using a List.Generate().  What I'm trying to do is to setup my queries so they don't bother to run for date ranges that will be stored in the service.  I built a report that shows the values of the parameters, in hopes of seeing the values get set by the service, but the entire report so far won't refresh.
Please include the setting of the RangeStart and RangeEnd parameters by the service, for instance in the case that we set "Store data for 3 years" and "update data for the last 10 days", as an exmple.  That will help those of us who have queries that are more complex than "get entire big table"
-thanks
-e

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

ID: fdb026fd-1515-7484-1acd-3d363e143cc8
Version Independent ID: 62650e83-de5c-0323-cacc-31bad6e46361
Content: Incremental refresh in Power BI - Power BI
Content Source: powerbi-docs/admin/service-premium-incremental-refresh.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @ericleigh007.
I've assigned this issue to the doc author for review.
In the meantime, you might find an answer in the Power BI Community.

Hi @ericleigh007,
Apologies for the very late reply. As per the Create parameters section, RangeStart and RangeEnd are set automatically by the service as per this statement:
After the model is published to the service, RangeStart and RangeEnd are overridden automatically by the service to query data defined by the refresh period specified in the incremental refresh policy settings.

Hope this helps,
Kesem


expose no-implicit-* in ddc

Currently, analyzer-cli has flags for --no-implicit-cast and --no-implicit-dynamic.  Should these be exposed in dev_compiler as well?
FWIW, analyzer-cli has options - e.g., linting / disabling strong mode - that don't make sense in dev_compiler, so it's not obvious which ones should or should not be plumbed through (or whether we ought to be considering a more significant refactor).
@jmesserly @leafpetersen

Filed https://github.com/dart-lang/sdk/issues/27252 for the more general issue. We could also add this one as a one-off if you need it sooner.

@danrubel - we can close this, right?  :-)

Fixed as part of https://codereview.chromium.org/2598593003/


Publish network weights

Could you publish the network weights trained on TIMIT which worked best for you?

Unfortunately, I haven't stored them. But you can easily train a network, should be done in a couple hours on a GPU.

I guess that's true, my results seem worse than the example in the Readme, was that one cherry-picked?
I get results like these:

They make some sense, but are by far worse than your example:

Do you know why your input feature prints lock different to mine? I'm not sure if I trained my model for the print only 20 epochs. Some models I experiment with are trained 50 epochs.

Do you know why your input feature prints lock different to mine?

Different matplotlibs with different default colorschemes I think.

I'm not sure if I trained my model for the print only 20 epochs. Some models I experiment with are trained 50 epochs.

Training output shows epoch validation at 34/414, did you train on 414 epochs? The model does still improve after 20 epochs.

Different matplotlibs with different default colorschemes I think.

I tried to repeat my experiments and i get the same green plots like you. It looks like they have less variance.

Training output shows epoch validation at 34/414, did you train on 414 epochs? The model does still improve after 20 epochs.

I trained with 20 or 50 epochs but not more. I picked this example because it was nice, but the other samples looked similar.


fix the promptes in validation webhook

nit: the promptes in the log does not match that provided in cmd flag
/assign @ayj

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: cmluciano
If they are not already assigned, you can assign the PR to them by writing /assign @cmluciano in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Dragon update

Implementation of TR2 Dragon and Bartoli object.
I had to recreate new PR because I corrupted the old one when I merged develop.
DRAGON
Dragon OCB:
0 - The dragon dies when its health points reaches 0
1 - The dragon only gets defeated when its health points reaches 0, Lara must retrieve the dagger to kill the dragon.
It requires DRAGON_FRONT, DRAGON_BACK, DRAGON_BONES_FRONT and DRAGON_BONES_BACK
BARTOLI
Bartoli OCB:
0 - Bartoli body only appears after being triggered, then the explosion and transformation only starts when Lara gets closer than 9 sectors.
1 - Bartoli body is visible since the level start, then the explosion and transformation only starts when the object is triggered.
Bartoli ItemFlags[0]:
The object ID of the enemy that will spawn. (By default the Dragon).
It requires BARTOLI, SPHERE_OF_DOOM1, SPHERE_OF_DOOM2 and SPHERE_OF_DOOM3

I think that OCB 1 behaviour should be default behaviour, and OCB 0 behaviour should be scrapped

Level does not load (Sunday 21st Jan) if contains Marco Bartolli or the Dragon.

PR merged in develop: https://github.com/MontyTRC89/TombEngine/commit/cc333e2f327cf0064b43899767c645d3f42fae0d


Expose Lens Monaco Editor component to extensions-api

close #5094

It points to the following line

This is weird because new typescript version support mixed import declarations like:
import { SomeVariable, type SomeType } from "../some-module"

@lensapp/lens-maintainers any clue?


Run Problem

Description
Files run into a problem that the developer prepare it.
Steps To Reproduce
go to
Steps to fix

eg. Fix crash that occurs when...
eg. Correct action happens when clicking...

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22621.963
Windows Version
Windows 11 Pro Version	22H2
Relevant Assets/Logs

We need a little more information from you in order to investigate this issue including the log file and steps to reproduce the issue.


Suggesting additional ban list sources

http://blocklist.greensnow.co/greensnow.txt
http://charles.the-haleys.org/ssh_dico_attack_hdeny_format.php/hostsdeny.txt
http://osint.bambenekconsulting.com/feeds/c2-ipmasterlist.txt
http://talosintel.com/feeds/ip-filter.blf
http://www.binarydefense.com/banlist.txt
https://www.badips.com/get/list/any/2?age=30d

Thanks!  These have now been added, disabled/commented to be individually enabled as appropriate.
Note that you'll want to be sure to use the latest updBlackList.sh which has been updated as well to accommodate their formatting.


Uncaught Error: Cannot call function 'getPosition' on missing remote object 414

[Enter steps to reproduce:]

...
...

Atom: 1.41.0 x64
Electron: 4.2.7
OS: Microsoft Windows 10 Home Single Language
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot call function 'getPosition' on missing remote object 414
At C:\Users\Dieva\AppData\Local\atom\app-1.41.0\resources\electron.asar\renderer\api\remote.js:222

Error: Cannot call function 'getPosition' on missing remote object 414
    at throwRPCError (~/AppData/Local/atom/app-1.41.0/resources/electron.asar/browser/rpc-server.js:148:17)
    at ~/AppData/Local/atom/app-1.41.0/resources/electron.asar/browser/rpc-server.js:406:5
    at EventEmitter.ipcMain.on.args (~/AppData/Local/atom/app-1.41.0/resources/electron.asar/browser/rpc-server.js:273:21)
    at EventEmitter.emit (events.js:182:13)
    at WebContents.<anonymous> (~/AppData/Local/atom/app-1.41.0/resources/electron.asar/browser/api/web-contents.js:368:21)
    at WebContents.emit (events.js:182:13)

Commands
     -1:21.9.0 intentions:highlight (input.hidden-input)
  3x -1:21.4.0 core:copy (input.hidden-input)
     -1:20.5.0 intentions:highlight (input.hidden-input)
     -1:20.4.0 core:paste (input.hidden-input)
     -1:19.1.0 editor:select-to-beginning-of-word (input.hidden-input)
     -1:18.8.0 intentions:highlight (input.hidden-input)
     -1:18.7.0 core:paste (input.hidden-input)
     -1:18.3.0 intentions:highlight (input.hidden-input)
  4x -1:18.2.0 core:save (input.hidden-input)
     -0:25.1.0 core:move-right (input.hidden-input)
 11x -0:24.8.0 core:select-down (input.hidden-input)
     -0:21.9.0 intentions:highlight (input.hidden-input)
  2x -0:21.5.0 core:select-down (input.hidden-input)
     -0:21 intentions:highlight (input.hidden-input)
  2x -0:20.7.0 core:copy (input.hidden-input)
     -0:13.1.0 tree-view:remove (span.name.icon.icon-file-text)

Non-Core Packages
atom-beautify 0.33.4
atom-formatter-jsbeautify 1.1.2
atom-material-ui 2.1.3
atom-vue 0.6.0
busy-signal 2.0.1
cssbeautify 1.3.0
highlight-colors 0.8.0
highlight-selected 0.16.0
Hydrogen 2.12.1
intentions 1.1.5
linter 2.3.1
linter-eslint 8.5.5
linter-php 1.6.1
linter-tslint 1.10.31
linter-ui-default 1.8.0
minimap 4.29.9
php-cs-fixer 4.1.1
vue-fmt 0.1.1

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/16630 so you can subscribe there for updates if you'd like.
If the error is reproducible for you, please let us know the steps to reproduce and if you can reproduce in safe mode.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Fixed ref-counting of Python object temporaries in unboxing code

Ref-count of arrayobj was not decremented after use in case dpnp.ndarray object was being processed.
Change the flow of managing lifetime of Python temporaries in unboxing code.
This PR replaces use of obj in NRT structure with use of arrayobj, and shifts ref-count manipulation of obj into PyUSMNdArray_ARRAYOBJ.

[x] Have you provided a meaningful PR description?
[ ] Have you added a test, reproducer or referred to an issue with a reproducer?
[ ] Have you tested your changes locally for CPU and GPU devices?
[ ] Have you made sure that new changes do not introduce compiler warnings?
[ ] If this PR is a work in progress, are you filing the PR as a draft?

@oleksandr-pavlyk there are some compile time warnings after these changes.

The memory leak that was occurring with pairwise distance workload is resolved with this fix. Thanks, @oleksandr-pavlyk .

@oleksandr-pavlyk there are some compile time warnings after these changes.

Yes, I pushed a fix for them, by casting PyUSMArrayObject * pointer to PyObject * pointer, which is always safe to do.

coverage: 86.494% (+0.01%) from 86.48%
when pulling 5dcf8af4d2909c96982e28ad524f14b22ab1412c on correct-refcount-handling-fixing-memory-leak
into e36c97917ec97185b52839b800b2bc2f77b79e46 on main.


Flutter web not hot reloading after adding a widget

Hot reload Error
hotRestart: (-32000) Service connection disposed

[√] Flutter (Channel master, 1.23.0-4.0.pre.86, on Microsoft Windows [Version 10.0.19041.508], locale en-US)
• Flutter version 1.23.0-4.0.pre.86 at D:\Program Files\flutter
• Framework revision 57cda51f7e (3 weeks ago), 2020-09-23 16:52:02 -0700
• Engine revision dd35b5b659
• Dart version 2.10.0 (build 2.10.0-156.0.dev)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\dadzi\AppData\Local\Android\sdk
• Platform android-29, build-tools 29.0.3
• Java binary at: D:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
X Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.2)
• Visual Studio at D:\Program Files\Microsoft Visual Studio\2019\Community
• Visual Studio Community 2019 version 16.7.30413.136
• Windows 10 SDK version 10.0.18362.0
[√] Android Studio (version 4.0)
• Android Studio at D:\Program Files\Android\Android Studio
• Flutter plugin version 50.0.1
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] VS Code (version 1.47.3)
• VS Code at C:\Users\dadzi\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.13.2
[√] Connected device (4 available)
• Windows (desktop) • windows    • windows-x64    • Microsoft Windows [Version 10.0.19041.508]
• Web Server (web)  • web-server • web-javascript • Flutter Tools
• Chrome (web)      • chrome     • web-javascript • Google Chrome 79.0.3945.130
• Edge (web)        • edge       • web-javascript • Microsoft Edge 86.0.622.38
! Doctor found issues in 1 category.
if (!ResponsiveWidget.isSmallScreen(context)) Row( mainAxisAlignment: MainAxisAlignment.end,  children: <Widget>[ IconButton( onPressed: () {} icon: Icon(Icons.add) ) ] )

Logs

@michaeldadzie
Please provide flutter doctor -v and a minimal complete reproducible code sample that shows the issue.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Prometheus PVC support for more than one replica or Statefulset

Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST

Version of Helm and Kubernetes:
Kubernetes 1.6.2
Helm 2.6.1
Which chart:
stable/prometheus
What happened:
started 2 repicas of prometheus server with an ebs PVC
'''server:
name: prometheus
persistentVolume:
size: 20Gi
annotations:
volume.alpha.kubernetes.io/storage-class: ebs'''
What you expected to happen:
Start 2 Prometheus servers with one EBS attached each one
How to reproduce it (as minimally and precisely as possible):
Configure server replicas to 2 with persistent storage
Anything else we need to know:

Just experienced this too with alertmanager.
I get two alertmanager pods and one alertmanager pvc which is RWO, so they cannot share it.  I've set only 1 replica for server, due to https://github.com/prometheus/prometheus/issues/2609 , which I'm sure is related.
This file needs updates, at least:
https://github.com/kubernetes/charts/blob/master/stable/prometheus/templates/alertmanager-pvc.yaml

Any Update on supporting replicas for Server or AlertManager?

Is there any update on running more than one replica for alert manager or prometheus server and mapping PVC volumes and how that is done?

/reopen

/remove-lifecycle rotten.


Put an icon into the generated Library files so that it shows up in the Onshape UI properly

When creating a parts library document, one possibility would be to copy this document:
https://cad.onshape.com/documents/b4bcde355d766c6e9812e69f/w/b32317dd4be07517f1400af1/e/1030652948a5fe4d88194779
It has a drawing that is set as the default

That way every document that is a parts library will show up with that icon in the UI

Can we use the the book icon instead.

Here you go
https://cad.onshape.com/documents/c13874b1920731d0c83c9290/w/bf9bdc1a95485ec1268f609f/e/8fdec5ea579c5832541cf59d

When I use this document(clone it with the new name instead of creating a new document) the icon will only render in onshape after I open it.
After I create it with the extension:

When I open it in onshape:

Now it renders like intended:

It seems like an onshape bug, but I'm not sure.


[Automation] Generate Fluent Lite from machinelearningservices#package-2022-10

[Automation] Generate Fluent Lite from machinelearningservices#package-2022-10

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-machinelearning


Add RubyKaigi talk to readme

Motivation

Watched the talk and noticed other talks are linked in the readme.

Signed the CLA, can't find how to retry the workflow


There is no issue

How can I explain?
Read -> https://wiki.odicforcesounds.com  ( single page description )
Read -> License ( few lines of agreement )
I need help to built that challenge, so the world can become better ... in Time..
Maybe You can, maybe you like it..
if not, just ignore this issue and delete it!
Thank You!
Oh, yes.. I am in the condition of the Solar Plexus Expression... Between emotions and Rationality ( if you know what I mean )

Hey @DaoExpression What this?


Detect Datatype within Asammdf and set to decimal for Datatypes not handled by Kusto

In the testing phase, it was detected that uint64 signals were ingested as double64, which resulted in data losses.
The dtype of each signal needs to be used in order to choose which datatype to use in Kusto.
The datatypes we get from Asammdf should also be used as metadata in signals-metadata

Problem is very noticeable in uint64 datatypes, as they will lose precision when cast to a double.
We require a better handling of the different datatypes to avoid precision loss


Changed public -> internal on depositInternal modifier.

Pull Request Test Coverage Report for Build 712

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.751%

Totals

Change from base Build 706:
0.0%

Covered Lines:
300

Relevant Lines:
300

💛  - Coveralls


When using transitioningDelegate, a non-responsive black screen appears

I tried using your example of the transitioningDelegate as you have it with the Custom Transitions classes (DimmingPresentationController, PresentingAnimator, DismissingAnimator) and a black screen appears when a gallery item is selected.
I even code-dumped the example project into mine (except for images) and got a black screen.

i set the animated: bool to 'false' so that it at least displays photographs properly.
`// MARK: - UICollectionViewDelegate
override func collectionView(_ collectionView: UICollectionView, didSelectItemAt indexPath: IndexPath) {

    index = indexPath.item

    let gallery = SwiftPhotoGallery(delegate: self, dataSource: self)

    gallery.backgroundColor = UIColor.black
    gallery.pageIndicatorTintColor = UIColor.gray.withAlphaComponent(0.5)
    gallery.currentPageIndicatorTintColor = appDelegate.globalThemeColor
    gallery.hidePageControl = false
    gallery.modalPresentationStyle = .custom

    // transition animations not working
    //gallery.transitioningDelegate = self

    // load photo viewer on selected image
    present(gallery, animated: false, completion: { () -> Void in
        gallery.currentPage = self.index
    })
}`

@rajathooja Did you resolve this, and if so, how?


Release Notes Bug: Release notes not downloading for all releases

The missing releases seem random. Not happening locally. Unfortunately, the most recent 2 releases are among the missing. The release notes being downloaded:

Fixed in staging by #857, will reopen if it's not also fixed in production (which is not in sync with staging)


Create a card box-shadow effect to be to able distinguish between the cards. #2906

Fixes #2906
Describe the problem
In the "How to Support?" section of the "Contribute" Webpage, all the three cards of Student, Teacher and Developer doesn't look distinguished from each other and is being visible as a single block.
To Reproduce
Steps to reproduce the behavior:
Go to [https://circuitverse.org/contribute]
Scroll down to the "How to Support Section"
See error
Expected behavior
To produce a card box-shadow effect to distinguish the cards from each other.
Screenshots
Before:

After:

Coverage remained the same at 81.774% when pulling 181cea82ff87bac65c12333ff942d973f95b2037 on bhutani2002:Card-box-shadow#2906 into a978b46a15ad68aee6a19924b1d35bbe73eccae1 on CircuitVerse:master.

Can you please attach the screenshots and link the issue with pr ?

Fix Code Climate issues and Can you please attach the screenshots and link the issue with pr ?

Can you please elaborate on this?? I am not able to get ,what it's trying to say.

Fix Code Climate issues and Can you please attach the screenshots and link the issue with pr ?

Can you please elaborate on this?? I am not able to get , what it's trying to say.

Yaa, it is saying that you have to leave an empty line after the declaration  (after }  this bracket )...

Hi @Prerna-0202 thanks for your replies. I guess finally, there no issues. Please check it once. It happened after I guess 8 pushes just due to that spacings and new lines thing 😂. Thank You

Hey @Prerna-0202 what's the status of merging?
Thank You.

Hey @gr455 , @tachyons can you please look into the merging process.
Thank You


NoteStoreClient.findNotes() does not find notes

I am using the Evernote Java SDK with the sandbox account to create a note and search for it.
Note mynote = new Note();
mynote.setTitle("mytitle");
mynote.setContent(content);
Note createdNote = noteStore.createNote(mynote);

NoteFilter filter = new NoteFilter();
String query = "mytitle";
filter.setWords(query);

NoteList notelist = noteStore.findNotes(filter, 0, 10);

The creation of the note works fine but unfortunately findNotes() just returns an empty list. The same code worked some months ago but now it doesn't anymore.

The same issue here, whether on Sandbox or Production mode.


bug in dispersal-connect-matrix

there is some unknown issue that generates an unknwon issue

turns out this was not an issue at all, the original dispersal function was the buggy one. This is being addressed in #5


Make the AdvancedHandler less magical

This PR removes some of the magic from the AdvancedHandler of the AdsTestserver. Namely this is:

PLCVariables will need to be added to the handler before they can be written to or read from
This gives more control over the creation process and makes it more explicit.

PLCVariables need name, value, ads_type and symbol_type on initialisation.
This mirrors more the situation we have with a real plc where we create variables upfront with all necessary type informations at hand. Also it brings more clarity in the tests. One can see which values and types are used by simply looking at the test. No need to search for the default values.

Pull Request Test Coverage Report for Build 668

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.634%

Totals

Change from base Build 666:
0.0%

Covered Lines:
1164

Relevant Lines:
1230

💛  - Coveralls

Pull Request Test Coverage Report for Build 668

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.634%

Totals

Change from base Build 666:
0.0%

Covered Lines:
1164

Relevant Lines:
1230

💛  - Coveralls


Set filters for a column

Is there a way to set filters in a column - see pic

?

Sadly the filter information doesn't exist until the file is opened in Excel.  It's a contender for most annoying missing feature.

OK thanks for the info


add convex hull 3d benchmark

Results on a Mac Mini (M2):

Godot Engine v4.2.1.stable.mono.official.b09f793f5

And here are the results from the laptop on which I originally calibrated the benchmark:
"system":{"cpu_architecture":"x86_64","cpu_count":4,
"cpu_name":"Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz",
"gpu_name":"Intel(R) HD Graphics 520 (SKL GT2)","gpu_vendor":"Intel","os":"Linux"}

AC plugged in (performance mode):

Battery (power saving mode):

(also Godot Engine v4.2.1.stable.mono.official.b09f793f5)

I just noticed that these benchmark weren't working. Follow-up PR soon!


TEST: DON'T MERGE

Only for testing the bot integration. Unsuscribe to stop receiving notifications.
Resolves: https://issues.redhat.com/browse/NMT-943

Testing done


chore: bump dependencies, update release config and docker images

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


General fixes, related to IMC, YAMT and HENlo install.

1st commit is small fix related to rebooting, clarifying you need to open the HENlo page again and fix confirm button #156
2nd is just #156
3rd changing the part about keeping folders (keep VitaDeploy) as the YAMT guide doesn't mention any way to install jailbreaks without enso now, so need to keep that or mention h-encore reactivating. (There needs to be made a guide on how to install VitaShell, as it's necessary for this one and there isn't a proper explanation on the site)

This would be nice to have 👍

This fixes #182
So I'll also add the fix from #181 while I'm at it


./manage.py admin_generator: error: unrecognized arguments: ... and some exceptions...

I would like to generate admin interface for my apps. First I run:
> ./manage.py admin_generator
This command requires an existing app name as argument
Available apps:
    apps.portal.api
    debug_toolbar
    django.contrib.admin
    django.contrib.auth
    django.contrib.contenttypes
    django.contrib.sessions
    django_extensions
    rest_framework

Here I see the list of apps and try to generate_admin for one of them:
> ./manage.py admin_generator apps.portal.api
usage: manage.py admin_generator [-h] [--version] [-v {0,1,2,3}]
                                 [--settings SETTINGS]
                                 [--pythonpath PYTHONPATH] [--traceback]
                                 [--no-color] [-s SEARCH_FIELD]
                                 [-d DATE_HIERARCHY] [-p PREPOPULATED_FIELDS]
                                 [-l LIST_FILTER_THRESHOLD]
                                 [-r RAW_ID_THRESHOLD]
manage.py admin_generator: error: unrecognized arguments: apps.portal.api

I thought I did something wrong and run
> ./manage.py admin_generator --help
Traceback (most recent call last):
  File "./manage.py", line 8, in <module>
    execute_from_command_line(sys.argv)
  File "/home/prokher/Dev/PyVirtEnvs/pSeven/lib/python3.4/site-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
    utility.execute()
  File "/home/prokher/Dev/PyVirtEnvs/pSeven/lib/python3.4/site-packages/django/core/management/__init__.py", line 345, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/prokher/Dev/PyVirtEnvs/pSeven/lib/python3.4/site-packages/django/core/management/base.py", line 339, in run_from_argv
    options = parser.parse_args(argv[2:])
  File "/home/prokher/Dev/PyVirtEnvs/pSeven/lib/python3.4/site-packages/django/core/management/base.py", line 59, in parse_args
    return super(CommandParser, self).parse_args(args, namespace)
  File "/usr/lib/python3.4/argparse.py", line 1737, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.4/argparse.py", line 1769, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.4/argparse.py", line 1975, in _parse_known_args
    start_index = consume_optional(start_index)
  File "/usr/lib/python3.4/argparse.py", line 1915, in consume_optional
    take_action(action, args, option_string)
  File "/usr/lib/python3.4/argparse.py", line 1843, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/lib/python3.4/argparse.py", line 1025, in __call__
    parser.print_help()
  File "/usr/lib/python3.4/argparse.py", line 2368, in print_help
    self._print_message(self.format_help(), file)
  File "/usr/lib/python3.4/argparse.py", line 2352, in format_help
    return formatter.format_help()
  File "/usr/lib/python3.4/argparse.py", line 287, in format_help
    help = self._root_section.format_help()
  File "/usr/lib/python3.4/argparse.py", line 217, in format_help
    func(*args)
  File "/usr/lib/python3.4/argparse.py", line 217, in format_help
    func(*args)
  File "/usr/lib/python3.4/argparse.py", line 524, in _format_action
    help_text = self._expand_help(action)
  File "/usr/lib/python3.4/argparse.py", line 611, in _expand_help
    return self._get_help_string(action) % params
TypeError: %d format: a number is required, not dict

and that is why I am here posting the issue :)
I use Django 1.9.2 and django-extensions installed with pip install git+https://github.com/django-extensions/django-extensions --upgrade

The problem is that if we are working with Django >= 1.8 the default formatter on help argument needs to be written [default: %(default)s] instead of [default: %default] which actually causes the above issue see (argparse documentation) .
However, if we change all the options with [default: %(default)s] formatter it won't see properly on Django < 1.8:
  -s SEARCH_FIELD, --search-field=SEARCH_FIELD
                        Fields named like this will be added to
                        `search_fields` [default: %(default)s]

So, CompatibilityBaseCommand needs to be fixed in order to solve this problem. I've trying to figure out this problem for a while, but I can't see any easy solution right now. Maybe @thecardcheat  can help us so he was the responsible to fix compatibility between Django versions.

Thanks for identifying the issue clearly and linking to those docs (hadn't seem them). I think there is a sensible location to resolve this and I should be able to submit a PR.

Thanks @thecardcheat.  Hope you find out the solution without lose to much time. Let me know if you need help.

@trbs this issue can be closed.

Thanks


fix: Update Actions section

I found more instances in the documentation that need to be updated. Below are few examples, in these sections old action selector UI and its limitations are mentioned. Please check once and let me know if we need to jump on a call.

https://appsmith-docs-doa9grbw2-get-appsmith.vercel.app/core-concepts/writing-code/workflows#complex-workflows
https://appsmith-docs-doa9grbw2-get-appsmith.vercel.app/reference/widgets/button#trigger-actions-with-buttons

One more thing that we need to update, with the redesign we’re encouraging users to use then/catch statements to setup success and error blocks instead of callback arguments style that we’ve been mentioning in the docs.

@danciaclara - @ravikp7 has pointed out:

I found more instances in the documentation that need to be updated. Below are few examples, in these sections old action selector UI and it’s limitations are mentioned. Please check once and let me know if we need to jump on a call.
https://appsmith-docs-doa9grbw2-get-appsmith.vercel.app/core-concepts/writing-code/workflows#complex-workflows
https://appsmith-docs-doa9grbw2-get-appsmith.vercel.app/reference/widgets/button#trigger-actions-with-buttons

As part of Rehaul we are anyways only adding screenshots when absolutely necessary. There are below ways in which we can handle this:

Remove the screenshots from above pages so that users are not confused as suggested by Ravi and work on the pages as part of Rehaul pipeline.
Update the screenshots
Leave them as is

Your thoughts?
CC: @harshilp24


[Feature] Doris supports LLM(chatGPT)  to query and optimize in natural language

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
1、convert natural language into Doris  SQL.
2、suggestions for Doris SQL tuning.
3、doris web console to receive Natural Language Processing (NLP).
Use case
No response
Related issues
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

maybe we could add our work in https://github.com/hwchase17/langchain


Add project for "Running a Kubernetes ingress"

This changes adds:

A project setup as described in the contrib documentation for "Running a Kubernetes ingress" #5

Also this changes modifies:

the project setup script minimally to have the sample readme correctly named "Readme.md" in the new project
the project setup script to be executable

@DiptoChakrabarty this is my proposal, can you please have a look if this is ok?

this looks good , can you change the directory name to running_a_k8s_ingress_kustomize since this project depends on kustomize so heavily
also will it be possible for you to squash your commits

all done @DiptoChakrabarty