Portion of Providers Not Bidding on GPU Workloads When Model Specified

Summary
When an order is created for a GPU enabled SDL which includes a list of requested models - only a portion of providers with available, relevant inventory create bids.  The providers that have available inventory but that are not creating a bid show insufficient capacity for reservation in provider logs despite having sufficient capacity.
If the explicit GPU models are removed from the SDL the affected providers create bid successfully.  Identical SDL used in successful attempt with only the GPUs model list removed.
Other providers create bids on order receipt with GPU model list in SDL.  Thus this is a sporadic issue but appears consistent on affected providers.  Some providers never bid when model list is included.  Other providers bid without issue when GPU models are included.
Details

GPU Testnet
Tested Provider Version - v0.3.1-rc1
Provider logs - https://transfer.sh/BzhMIeEuaS/provider-logs.tar.gz
SDL used in testing - SDL within this Gist is the version that includes a GPU model list - same SDL with GPU list removed was used in the successful deployment example - https://gist.github.com/chainzero/6e7768ea0d948d81fe56e6b82ce1d84b
Provider tested - akash143ypn84kuf379tv9wvcxsmamhj83d5pg2rfc8v
Deployer address - akash1f53fp8kk470f7k26yr5gztd9npzpczqv4ufud7
DSEQ of no bid generated problem deployment (SDL with GPU model list) - 364164
-DSEQ of successful order/bid received (SDL with no GPU model list but otherwise identical to failed attempt) - 364226

Provider Attributes

As shown - the provider  is advertising GPU attribute of 3090 and thus should bid on the SDL that includes 3090 in GPU model list

provider-services query provider get akash143ypn84kuf379tv9wvcxsmamhj83d5pg2rfc8v
attributes:
- key: host
  value: akash
- key: tier
  value: community
- key: capabilities/gpu/vendor/nvidia/model/3090
  value: "true"
host_uri: https://provider.shimpa.org:8443
info:
  email: ""
  website: ""
owner: akash143ypn84kuf379tv9wvcxsmamhj83d5pg2rfc8v

provider 0.3.2-rc4 fixes that


Setup Step 2 (on Mac)

For user in container
Error message:
docker: Error response from daemon: Mounts denied:
The path /Applications/freesurfer/7.2.0/license.txt is not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
See https://docs.docker.com/desktop/mac for more info.
Solution:
add the path of freesurfer license to Docker -> Preferences -> Resources -> File Sharing.

Thank you for providing the solution! Ways to get docker to run on your system, are highly OS-dependent and hence a pre-requisite for PYB!


API load balancer

Once we have the API server running in the cluster, we will want to set it up to be load balanced in the cluster

Load balancer implemented
Ethstat Dashboard
http://a76ab76cfc49440a594d947189734303-848168955.us-west-1.elb.amazonaws.com
Solidity Dashboard
http://a04d1d57d648441d793c178bfae2784e-1027067517.us-west-1.elb.amazonaws.com
Geth
http://a42f3ac8ef865438ca0b99bd673f4e70-871205895.us-west-1.elb.amazonaws.com
API endpoint
http://af2fc18b539ee488984fa4e58de37686-1454411376.us-west-1.elb.amazonaws.com


Please write a guide to install on HASS.IO

If I just copy the files i get this error in frontend:

I haven't had a hass.io instance to test on in a while. I'll work on getting an install guide written up.
The files can't be copied directly (they need to be compiled first) -- sorry, I never updated the docs 😢
Try this as an interim solution:

Install NodeJS if you don't already have it
Install gulp 4 if you don't already have it npm i -g gulp@next
Run gulp build at the root of the repository
The compiled files will output to ./.tmp/ You should be able to copy them directly from there.

Hi lukiffer
I tried to compile it with your instructions but it didn't work.
I will appreciate if you can please send me a link to your compiled files?
Thanks

You should try forcing latest Javascript in the frontend section of the config:
frontend:
javascript_version: latest
Then force fresh browser cache.

Hi KKlitgaard,
Thanks for your replay, unfortunately it dosen't work, now this is what i see in the frontend:

Do you have another idea?
Thanks

@tomerbs apologies for the delay in getting around to this. I just finished up a themes feature that I'll be merging today. Should also have time to at least get the compiled files included in a release as well as improving docs.

Updated the Alternate Installation instructions and have updated the CI build to start attaching ZIP archives of the compiled files to the releases. You can download the zip and then copy it to your hass.io config directory. Once you've copied the zip, simply run unzip haiku-0.1.0.zip -d www (or some equivalent) to extract it into your www folder.
I'm going to go ahead and close this issue. If you are still having troubles feel free to reply and I'll re-open it.


make minimap tap more reliable

it seems to take a few taps usually to open the minimap. Maybe wrap it in an InkWell?

Tried wrapping in an InkWell and it didn't help. I couldn't find any way to get the map to not eat tap events and had to keep using onMapClicked

FIxed in 84e9d07c98c1fa15ea4cddae7dba1ca6d9a0071e


[Feature] New kind of lookup item field in dynamics

Describe the feature
<>
Explain why this feature is needed
textInputBox_with_filter_new kind of control not supported in current set value function.
Additional context
current set value for mention control can not be handled in UCI library;

Hi @aalokkhare.
Can you provide more details please?
Thanks.


[ISSUE #739]🔥Improve the pull message consumption pattern🚀

Which Issue(s) This PR Fixes(Closes)

Fixes #739
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Can't goBack() cursor back to starting position

Bug description
I can't goBack() cursor back to starting position
To Reproduce
Steps to reproduce the behavior:

I input full text of MathField

I input some characters to hide some of characters at start position

Then, I use PreviousButton that move cursor to start position

But I can't move cursor to start position

Hi @GoTrust-BaoNH, thanks for using the package and opening the issue!
This is right now a known limitation, where we do not yet calculate if the cursor reaches the start of the visible area.
The idea right now is that you scroll manually. Can you try to scroll the math field manually (swipe with finger or with trackpad)? And do you think that works for you?

Hi @GoTrust-BaoNH, thanks for using the package and opening the issue!
This is right now a known limitation, where we do not yet calculate if the cursor reaches the start of the visible area.
The idea right now is that you scroll manually. Can you try to scroll the math field manually (swipe with finger or with trackpad)? And do you think that works for you?

It works with scroll the math field manually. But I want use PreviousButton. Can you suggest me a way to fix it?

@GoTrust-BaoNH I think the only way to achieve it is by contributing here.
The way it would work is finding the render box that draws the cursor and ensuring that is visible in the scroll view using: RenderObject.showOnScreen
I think to handle it nicely, we need to adjust flutter_math, but it should be possible to do it without that.


Inline shellescape dependency

Description
This PR relates to the discussion in https://github.com/zalando/go-keyring/pull/113 about the shellescape dependency using a vanity URL and practical solutions for avoiding that.
From my point of view, the dependency is small and stable so the risk of inlining this is low. I understand if you'd prefer not to though.

Let's put it under internal so we don't become a new public package for this :)
https://go.dev/doc/go1.4#internalpackages

👍

:+1:


Fix SlowUnixRefleakBuild timeout

Use a timeout of 5 hours rather than 30 minutes.

@pablogsal: oops, I missed that in your PR :-)
Maybe tests failed with timeout:
https://buildbot.python.org/all/#/builders/16/builds/161

@vstinner Are you going to deploy?

@vstinner Are you going to deploy?

Yeah, it's already deployed. Let's see tomorrow if I didn't mess up :)


Add ability to update the KnativeIngressGateway istio selector

Adds a new API to KnativeServing:
spec:
knative-ingress-gateway:
selector:
istio: "new-istio-selector"
Fixes #50

/lgtm


[V3] TypeScript custom variants

Issue Description
When adding new variants for the components, I get a typing error saying that the variant doesn't exist.
error TS2322: Type '"rounded"' is not assignable to type 'ResponsiveValue<"link" | "solid" | "outline" | "ghost" | "unstyled">'.

83               variant="rounded"
                 ~~~~~~~

  node_modules/native-base/lib/typescript/src/components/primitives/Button/types.d.ts:16:5
    16     variant?: ResponsiveValue<'ghost' | 'outline' | 'solid' | 'link' | 'unstyled'>;
           ~~~~~~~
    The expected type comes from property 'variant' which is declared here on type 'IntrinsicAttributes & IButtonProps & { ref?: any; }'

node, npm, react-native, react and native-base version, expo version if used, xcode version
    "native-base": "^3.0.0-next.40",
    "typescript": "~4.0.0"
    "expo": "^41.0.0",

Expected behaviour
Types should be inferred from theme customisation
Actual behaviour

Steps to reproduce
Add variants to the theme.

We have taken note of this issue and we'll try to fix this ASAP.

This appears to be an issue with fontSize as well.
I added custom fontSizes to my theme as seen below and I get a similar type error as described by @tlenclos.
My custom fontSizes
  fontSizes: {
    x12: 12,
    x14: 14,
    x16: 16,
    x18: 18,
    x24: 24,
    x34: 34,
    x48: 48,
    x60: 60,
    x96: 96,
  }

Type Error
Type '"x12"' is not assignable to type 'number | string[] | number[] | "xs" | "sm" | "md" | "lg" | "xl" | "2xl" | "3xl" | "4xl" | "5xl" | "6xl" | Record<string, string> | undefined'.ts(2322)
types.d.ts(12, 5): The expected type comes from property 'fontSize' which is declared here on type 'IntrinsicAttributes & ITextProps & RefAttributes<unknown>'
(JSX attribute) ITextProps.fontSize?: number | number[] | string[] | "xs" | "sm" | "md" | "lg" | "xl" | "2xl" | "3xl" | "4xl" | "5xl" | "6xl" | Record<string, string> | undefined

Component

I'm getting a similar error, but slightly different.
It seems the Text field does not recognize the variant property at all for me.
Error Message:
Type '{ children: string; variant: string; }' is not assignable to type 'IntrinsicAttributes & ITextProps & RefAttributes<unknown>'.
  Property 'variant' does not exist on type 'IntrinsicAttributes & ITextProps & RefAttributes<unknown>'.

Code

I made a workaround for now...
Component
`
import React from 'react';
import {Button as NButton, IButtonProps} from 'native-base';
import {ResponsiveValue} from 'styled-system';
type Props =
| IButtonProps
| {variant?: IButtonProps['variant'] | ResponsiveValue<'secundary'>};
const Button: React.FC = ({children, variant, ...rest}) => {
const variantsOf: any = variant;
return (
<NButton {...rest} variant={variantsOf}>
{children}

);
};
export default Button;
`

I'm getting a similar error, but slightly different.
It seems the Text field does not recognize the variant property at all for me.
Error Message:
Type '{ children: string; variant: string; }' is not assignable to type 'IntrinsicAttributes & ITextProps & RefAttributes<unknown>'.
  Property 'variant' does not exist on type 'IntrinsicAttributes & ITextProps & RefAttributes<unknown>'.

Code

Came here to post this exact issue. Hoping to see it resolved soon.

Came here to plus 1 this. The Text field doesn't seem to respect thevariant field at all.

Typescript support for custom tokens/variants is added in 3.2.1. You can find the docs on how to enable it here (https://docs.nativebase.io/typescript). Let us know if it works or you face any issues :)

Is anybody experiencing the same while defining a new color variant? In my case:
error
Property 'brand' does not exist on type '{ contrastThreshold: number; white: string; black: string; lightText: string; darkText: string; rose: { 50: string; 100: string; 200: string; 300: string; 400: string; 500: string; 600: string; 700: string; 800: string; 900: string; }; ... 33 more ...; tertiary: IColorHues; }'.

custom theme
import { extendTheme } from "native-base";

const customTheme = extendTheme({
  colors: {
    // primary background color
    brand: {
      100: "#f4f6f8",
      200: "#e4f5ff",
      500: "#189ad8",
      900: "#09374e",
    },
    error: {
      500: "#e61818",
    },
    info: {
      500: "#0fb6dd",
    },
    success: {
      500: "#47c869",
    },
    warning: {
      500: "#ffdb66",
    },
  },
  components: {
    FormControlHelperText: {
      baseStyle: {
        _invalid: { color: "error.500" },
      },
    },
    FormControlLabel: {
      baseStyle: {
        _invalid: { _text: { color: "error.500" } },
      },
      defaultProps: {
        _astrick: {
          color: "transparent",
        },
      },
    },
    Input: {
      baseStyle: {
        height: "60px",
        backgroundColor: "white",
        _invalid: {
          _focus: {
            bgColor: "error.100",
            borderColor: "error.600",
          },
        },
      },
      defaultProps: {
        rounded: "lg",
      },
    },
  },
  fontConfig: {
    Lato: {
      100: {
        normal: "Lato-Light",
      },
      200: {
        normal: "Lato-Light",
      },
      300: {
        normal: "Lato-Light",
      },
      400: {
        normal: "Lato-Regular",
      },
      500: {
        normal: "Lato-Bold",
      },
      600: {
        normal: "Lato-Bold",
      },
    },
  },
  fonts: {
    heading: "Lato",
    body: "Lato",
    mono: "Lato",
  },
});

// 2. Get the type of the CustomTheme
type CustomThemeType = typeof customTheme;

// 3. Extend the internal NativeBase Theme
declare module "native-base" {
  type ICustomTheme = CustomThemeType;
}

In a component (it's a react navigation tab stack, v6)
export default function RegistrationTopTabsStack() {
  const { colors } = useTheme();

  return (
    <RegistrationTopTabs.Navigator
      screenOptions={{
        tabBarActiveTintColor: colors.brand[500],
        tabBarInactiveTintColor: colors.text[400],
        tabBarIndicatorStyle: { backgroundColor: colors.brand[500] },
      }}
    >
      <RegistrationTopTabs.Screen
        name="Consumer"
        component={ConsumerRegistration}
      />
      <RegistrationTopTabs.Screen
        name="Business"
        component={BusinessRegistration}
      />
    </RegistrationTopTabs.Navigator>
  );
}


Add code for unit target in the Makefile.ci

/lgtm

/approve
We are going to figure out what's going on here after this merges, but it is meaningful to have these tests running even if there's a little cruft we need to reduce.

@sohankunkerkar looks like the unit tests failed in CI

@sohankunkerkar looks like the unit tests failed in CI

it's bound to happen since we changed the location of Dockerfile from openshift/Dockerfile to Dockerfile and CI's config still using the old change:
https://github.com/openshift/release/blob/master/ci-operator/config/openshift/kubefed/openshift-kubefed-master.yaml#L9

/retest

/retest

@pmorie  PTAL

/lgtm


Can glog support compress log files?

In some situation, a user want to keep more logs but it cost too much disk space, compression is very useful to resolve this issue

This is pretty much out of scope for glog. You can set up your favorite job scheduler and compress log files to your liking using your favorite compression tool.


Can't auth

File "/Users/voidmain/Desktop/Python Projects/Ensta/PasswordEncryption.py", line 22, in encrypt
recipient_key = load_pem_public_key(data=decoded_public_key)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: Unable to load PEM file. See https://cryptography.io/en/latest/faq/#why-can-t-i-import-my-pem-file for more details. MalformedFraming

you're using an older version of ensta. update it using pip install ensta --upgrade

you're using an older version of ensta. update it using pip install ensta --upgrade

I'm using the latest version. the problem occurs in the password encryption file, which was updated 2 weeks ago

have u edited the file? line 22 doesn't have that.


log event uid on DatumNotFound exception

Debugging problems resulting in DatumNotFound exceptions is made easier if the corresponding event can be quickly found.
This PR logs the event uid corresponding to the DatumNotFound exception.
Would it be better to append the event uid to the DatumNotFound exception message?

As an aside, note that in v2---which relies on event_model.Filler to handle these activities---the exceptions are already improved to be exactly as you wish.
https://github.com/bluesky/event-model/blob/14b082682a428d54e92676368777285b17815183/event_model/__init__.py#L932-L935
Here we are looking at v0 codepaths. It makes sense to apply the same improvements there, since we are still relying on v0 at a couple beamlines.

Yes, I think it would be better to include it in the exception rather than catch/log/re-raise. It is useful to have the information "in band", and of course at NSLS-II we log all exceptions at the application layer (in blueksky_ipython.log) so it will be logged along with everything else.
The function that raises this exception does not have access to the event uid, so we can't just add it there.
https://github.com/bluesky/databroker/blob/82063143b1faa81126b7a18806341b10a28934d7/databroker/assets/core.py#L36-L60
Fortunately, Python gives us raise from, and this situation is exactly what it was designed for.
class SomeNewExceptionType(Exception):
    def __init__(self, event_uid, *args, **kwargs):
        self.event_uid = event_uid
        super().__init__(*arsg, **kwargs)

...

try:
    ...
except DatumNotFound as err:
    raise SomeNewExceptionType(event_uid) from err

Your new exception will be shown at the bottom of the traceback, but the original exception will be above it, and %debug will enable a motivated debugger to access the event_uid programmatically. You might also extend DatumNotFound to capture the datum_id in the same way, enabling something like
class SomeNewExceptionType(Exception):
    def __init__(self, event_uid, datum_id,  *args, **kwargs):
        self.event_uid = event_uid
        super().__init__(*arsg, **kwargs)

...

try:
    ...
except DatumNotFound as err:
    raise SomeNewExceptionType(event_uid, err.datum_id) from err


[cosmetic] Examples on help output are all on a single line

$ jhack utils show-relation --help

 Usage: jhack utils show-relation [OPTIONS] [ENDPOINT1] [ENDPOINT2]

 Displays the databags of two applications or units involved in a relation.
 Examples: $ jhack utils show-relation my_app/0:relation_name other_app/2:other_name $ jhack utils show-relation my_app:relation_name other_app/2:other_name $ jhack utils show-relation my_app:relation_name other_app:other_name

The examples are all smushed together making them hard to read. This happens both on latest/stable (0.3.29) as in latest/edge (<IP_ADDRESS>).

in the meanwhile I figured out a simple workaround for show-relation.
It now shows:

@facundofc should be fixed on edge

It is! Great, thanks!


how to setMyLocationEnabled(true) after enableLocationRequest() success?

I'm trying to setmylocationenable to true when loading the page and the user gives permission, but I get
I have something like this:
`public onMapReady(event): void {
    this.mapView = event.object;

    if(!GeoLocationService.isEnabled()){
         GeoLocationService.enableLocationRequest().then(function(res){
             this.enableLocationLayer();
         }, function(error){

         });
    }else{
        this.enableLocationLayer();
    }

}
public enableLocationLayer(): void{
      if(this.mapView.android) {
            this.mapView.gMap.setMyLocationEnabled(true);
        }
        else if (this.mapView.ios) {
            this.mapView.gMap.myLocationEnabled(true);
        }

}
`
But I get
JS: permission granted!!!
JS: EXCEPTION: Uncaught (in promise): TypeError: Cannot read property 'enableLocationLayer' of null
JS: ORIGINAL STACKTRACE:
JS: Error: Uncaught (in promise): TypeError: Cannot read property 'enableLocationLayer' of null at resolvePromise  (file:///data/data/org.nativescript.testapp/files/app/tns_modules/nativescript-angular/zone.js/dist/zone-nativescript.js:416:31)...
It actually works but I have to go and come back to the page to see the locate icon on the top right hand of the map.
Thanks for your help.

I'm closing this here because I realize that there is a more appropriate place for this.


Batch Conditionals in v3.0.0-RC2 result in NullPointerException

OrientDB Version: 3.0.0RC2
Java Version: 1.8.0_151
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu<IP_ADDRESS>-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
OS: Ubuntu 16.04.3 LTS
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial
Expected behavior
Using the Studio UI at port 2480 in BATCH mode:
if (1 < 2) { return 'yes'; }
Should return 'yes'
Screenshot using OrientDB v2.2.15

Actual behavior
Causes NullPointerException
Screenshot using OrientDB v3.0.0RC2

Steps to reproduce
Navigate to OrientDB UI, click on Browse, click the wrench for 'Query configuration', and change the type to BATCH.
Enter the following into the text field:
if (1 < 2) { return 'yes'; }
I hope that I am simply misunderstanding the new batch requirements.  I know that there were changes with regards to newline characters and semicolons.  I cannot seem to make this work using the HTTP API or the Studio UI.

Hi @pulzzejason
Thank you very much for reporting, I'll check it asap
Thanks
Luigi

Hi @pulzzejason
I just pushed a fix, it will be released with the GA
Thanks
Luigi


[of_stats] @rest not registering staticmethod endpoints

All @staticmethod endpoints are not being registered using the @rest.
I´ve made a quick test and removing the @staticmethod from the main.py file Kytos registered the api endpoint correctly.

We are going to release kytos/of_stats soon. Meanwhile, there's the legacy/of_stats without the rest decorator.
About the @rest decorator and @staticmethod, you should first write @staticmethod and use the rest decorator right before the method.

It will be solved by either #303 or kytos/kytos#599.


Connection problem with Ifm3d

I am stucked with a problem regarding ifm3d since 3 days.
I can ping the camera but cannot run the tests.
In particular I get these after fixing my ipv4 to(<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>):
$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.042 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.044 ms
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2025ms
rtt min/avg/max/mdev = 0.042/0.043/0.044/0.000 ms
But When I run the command
$ ifm3d ls
The output is:
ifm3d error: -100001
Lib: XMLRPC Timeout - can you `ping' the sensor?
I already followed your troubleshooting guide and add this to ~/.bashrc:
no_proxy="<IP_ADDRESS>, localhost,  <IP_ADDRESS>, <IP_ADDRESS>, 192.168.1.* "
I tried also with Ubuntu 18.04 and Ros melodic but nothing changed.
Thanks for the attention,
Best regards

Please post the output of running: ifconfig and netstat -r. Also, is there anything special about your environment? Is this running on the metal? In a VM? In a container? How did you change the IP of the camera if you cannot connect to it? Are you sure it is the camera that is responding to your ping? When you say "after fixing my ipv4..." I just want to be clear that you are talking about the camera IP address and not your host IP address. If you changed your host IP, of course the ping will reply and of course ifm3d cannot connect. Please give us more information about your set up and provide the details I ask about above. Thanks.

Hello tom, thanks for the answer.
I am running Ubuntu 18.04 in a dual boot computer not virtual machine or anything else. Just installed everything yesterday to be sure of having a clean installation. These are the outputs you asked for:
$ ifconfig
enp24s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::846c:8cea:fe82:4d1  prefixlen 64  scopeid 0x20
ether 4c:cc:6a:fd:ec:42  txqueuelen 1000  (Ethernet)
RX packets 7633  bytes 6552837 (6.5 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 5612  bytes 691081 (691.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2067  bytes 193110 (193.1 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2067  bytes 193110 (193.1 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
$ netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         _gateway        <IP_ADDRESS>         UG        0 0          0 enp24s0
link-local      <IP_ADDRESS>         <IP_ADDRESS>     U         0 0          0 enp24s0
<IP_ADDRESS>     <IP_ADDRESS>         <IP_ADDRESS>   U         0 0          0 enp24s0
When I say fixing my ipv4 I meant that I went on the setting of the wired connection and changed my ipv4 address from automatic to manual and I inserted these settings:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
I usually do these passage in order to communicate through ethernet for example with a PLC and I did the same passage in Windows when I used the ifm software.
Thanks for the attention, just tell if you need other informations.

Hey @matteofiorini you have assigned the PC and the camera to the same IPV4 address. You have to change the IP of the PC to something else than <IP_ADDRESS> for example <IP_ADDRESS>. Otherwise the PC can`t route the Ethernet traffic to the camera. The proposed setting on the ifm software are related to the camera not the PC. Another option is to change the IP of the camera. Which needs extra handling of the IP address for ifm3d https://github.com/ifm/ifm3d/blob/master/doc/troubleshoot.md#connecting-the-camera

@graugans Thanks for the answer, I tried your suggestion but this doesn't work. I assigned my ipv4 to: <IP_ADDRESS> but now I get these outputs:
$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.275 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.155 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.222 ms
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2028ms
rtt min/avg/max/mdev = 0.155/0.217/0.275/0.050 ms
So the ping seems to work.
$ ifm3d ls
null
But he can't find the sensor even if the error has changed!
I tried also the test and I get these outputs:
$ catkin_make run_tests
Base path: /home/matteo/catkin/ifm3d
Source space: /home/matteo/catkin/ifm3d/src
Build space: /home/matteo/catkin/ifm3d/build
Devel space: /home/matteo/catkin/ifm3d/devel
Install space: /home/matteo/catkin/ifm3d/install

Running command: "make cmake_check_build_system" in "/home/matteo/catkin/ifm3d/build"

Running command: "make run_tests -j8 -l8" in "/home/matteo/catkin/ifm3d/build"

Built target tests
Removing test result files from '/home/matteo/catkin/ifm3d/build/test_results/ifm3d'

removing '/home/matteo/catkin/ifm3d/build/test_results/ifm3d/rostest-test_ifm3d.xml'
removing '/home/matteo/catkin/ifm3d/build/test_results/ifm3d/rosunit-test_camera.xml'
removing '/home/matteo/catkin/ifm3d/build/test_results/ifm3d/nosetests-test.xml'
Built target clean_test_results_ifm3d
-- run_tests.py: execute commands
/opt/ros/melodic/share/rostest/cmake/../../../bin/rostest --pkgdir=/home/matteo/catkin/ifm3d/src/ifm3d --package=ifm3d --results-filename test_ifm3d.xml --results-base-dir "/home/matteo/catkin/ifm3d/build/test_results" /home/matteo/catkin/ifm3d/src/ifm3d/test/ifm3d.test
-- run_tests.py: execute commands
"/usr/bin/cmake" -E make_directory /home/matteo/catkin/ifm3d/build/test_results/ifm3d
/usr/bin/nosetests-2.7 -P --process-timeout=60 --where=/home/matteo/catkin/ifm3d/src/ifm3d/test --with-xunit --xunit-file=/home/matteo/catkin/ifm3d/build/test_results/ifm3d/nosetests-test.xml

Ran 0 tests in 0.000s
OK
-- run_tests.py: verify result "/home/matteo/catkin/ifm3d/build/test_results/ifm3d/nosetests-test.xml"
... logging to /home/matteo/.ros/log/rostest-matteo-MS-7A37-3403.log
Built target _run_tests_ifm3d_nosetests_test
Built target _run_tests_ifm3d_nosetests
[ROSUNIT] Outputting test results to /home/matteo/catkin/ifm3d/build/test_results/ifm3d/rostest-test_ifm3d.xml
[ INFO] [1564123310.945932194]: Loading nodelet /ifm3d/camera of type ifm3d_ros/camera_nodelet to manager camera_standalone_nodelet with the following remappings:
[ INFO] [1564123310.951787716]: waitForService: Service [/ifm3d/camera_standalone_nodelet/load_nodelet] has not been advertised, waiting...
[ INFO] [1564123310.958186799]: Initializing nodelet with 8 worker threads.
[ INFO] [1564123310.973134544]: waitForService: Service [/ifm3d/camera_standalone_nodelet/load_nodelet] is now available.
[ INFO] [1564123311.035479666]: onInit(): /ifm3d/camera
[ INFO] [1564123311.076651781]: Camera clock will not be sync'd to system clock
[ INFO] [1564123311.076753361]: Running dtors...
[ INFO] [1564123311.076860851]: Initializing camera...
[ INFO] [1564123312.147840464]: Initializing framegrabber...
[ INFO] [1564123312.158553438]: Initializing image buffer...
[ WARN] [1564123312.659295257]: Timeout waiting for camera!
[ WARN] [1564123313.159923456]: Timeout waiting for camera!
[ WARN] [1564123313.660613265]: Timeout waiting for camera!
[ WARN] [1564123314.161072494]: Timeout waiting for camera!
[ WARN] [1564123314.661479293]: Timeout waiting for camera!
[ WARN] [1564123315.162014722]: Timeout waiting for camera!
[ WARN] [1564123315.662400981]: Timeout waiting for camera!
[ WARN] [1564123316.162940120]: Timeout waiting for camera!
[ WARN] [1564123316.663145939]: Timeout waiting for camera!
[ WARN] [1564123317.163606068]: Timeout waiting for camera!
[ WARN] [1564123317.163703148]: Attempting to restart framegrabber...
[ INFO] [1564123317.163735928]: Running dtors...
[ INFO] [1564123317.164382448]: Initializing camera...
[ INFO] [1564123318.174249169]: Initializing framegrabber...
[ INFO] [1564123318.184599253]: Initializing image buffer...
[ WARN] [1564123318.685154742]: Timeout waiting for camera!
[ WARN] [1564123319.185365091]: Timeout waiting for camera!
[ WARN] [1564123319.685569560]: Timeout waiting for camera!
[ WARN] [1564123320.186319559]: Timeout waiting for camera!
[ WARN] [1564123320.686863228]: Timeout waiting for camera!
[ WARN] [1564123321.187617927]: Timeout waiting for camera!
[ WARN] [1564123321.688140896]: Timeout waiting for camera!
[ WARN] [1564123322.188692135]: Timeout waiting for camera!
[ WARN] [1564123322.689216374]: Timeout waiting for camera!
[ WARN] [1564123323.189744283]: Timeout waiting for camera!
[ WARN] [1564123323.189815213]: Attempting to restart framegrabber...
[ INFO] [1564123323.189837523]: Running dtors...
[ INFO] [1564123323.190244753]: Initializing camera...
[ INFO] [1564123324.200339294]: Initializing framegrabber...
[ INFO] [1564123324.210442338]: Initializing image buffer...
[ WARN] [1564123324.710982397]: Timeout waiting for camera!
[ WARN] [1564123325.211514436]: Timeout waiting for camera!
[ WARN] [1564123325.712041035]: Timeout waiting for camera!
[ WARN] [1564123326.212562354]: Timeout waiting for camera!
[ WARN] [1564123326.713061233]: Timeout waiting for camera!
[ WARN] [1564123327.213265262]: Timeout waiting for camera!
[ INFO] [1564123327.556147214]: Unloading nodelet /ifm3d/camera from manager camera_standalone_nodelet
[Testcase: testtest_camera] ... ok
[ROSTEST]-----------------------------------------------------------------------
[ifm3d.rosunit-test_camera/test_camera][FAILURE]--------------------------------
False is not true
File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
File "/home/matteo/catkin/ifm3d/src/ifm3d/test/test_camera.py", line 117, in test_camera
self.assertTrue(self.success_)
File "/usr/lib/python2.7/unittest/case.py", line 422, in assertTrue
raise self.failureException(msg)
SUMMARY

RESULT: FAIL
TESTS: 1
ERRORS: 0
FAILURES: 1

rostest log file is in /home/matteo/.ros/log/rostest-matteo-MS-7A37-3403.log
-- run_tests.py: verify result "/home/matteo/catkin/ifm3d/build/test_results/ifm3d/rostest-test_ifm3d.xml"
Built target _run_tests_ifm3d_rostest_test_ifm3d.test
Built target _run_tests_ifm3d_rostest
Built target _run_tests_ifm3d
Built target run_tests

Update:
After creating an application in Windows now these are the outputs I get:
$ ifm3d ls
[
{
"Active": true,
"Description": "",
"Id": 557985589,
"Index": 1,
"Name": "Misurazione oggetto (oggetti parallelepipedi)"
}
]
So the sensor now works and indeed:
$ ifm3d hz
FrameGrabber running at: 3.2711 Hz
10 frames captured, over 1 runs
But If I run the code in ros and launch $roscore
then in another terminal  $ roslaunch ifm3d camera.launch
and in another one $ roslaunch ifm3d rviz.launch
I can see in rviz all the images but in the terminal of camera.launch I get this output:
$ roslaunch ifm3d camera.launch
... logging to /home/matteo/.ros/log/f4cea386-af90-11e9-8b3e-4ccc6afdec42/roslaunch-matteo-MS-7A37-14357.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://matteo-MS-7A37:32851/
SUMMARY
PARAMETERS

/ifm3d/camera/amplitude/disable_pub_plugins: ['image_transport...
/ifm3d/camera/assume_sw_triggered: False
/ifm3d/camera/confidence/disable_pub_plugins: ['image_transport...
/ifm3d/camera/distance/disable_pub_plugins: ['image_transport...
/ifm3d/camera/frame_id_base: ifm3d/camera
/ifm3d/camera/frame_latency_thresh: 60.0
/ifm3d/camera/good_bad_pixels/disable_pub_plugins: ['image_transport...
/ifm3d/camera/ip: <IP_ADDRESS>
/ifm3d/camera/password:
/ifm3d/camera/raw_amplitude/disable_pub_plugins: ['image_transport...
/ifm3d/camera/schema_mask: 15
/ifm3d/camera/soft_off_timeout_millis: 500
/ifm3d/camera/soft_off_timeout_tolerance_secs: 600.0
/ifm3d/camera/soft_on_timeout_millis: 500
/ifm3d/camera/soft_on_timeout_tolerance_secs: 5.0
/ifm3d/camera/sync_clocks: False
/ifm3d/camera/timeout_millis: 500
/ifm3d/camera/timeout_tolerance_secs: 5.0
/ifm3d/camera/xmlrpc_port: 80
/ifm3d/camera/xyz_image/disable_pub_plugins: ['image_transport...
/rosdistro: melodic
/rosversion: 1.14.3

NODES
/ifm3d/
camera (nodelet/nodelet)
camera_standalone_nodelet (nodelet/nodelet)
camera_tf (tf2_ros/static_transform_publisher)
ROS_MASTER_URI=http://localhost:11311
process[ifm3d/camera_standalone_nodelet-1]: started with pid [14372]
process[ifm3d/camera-2]: started with pid [14373]
process[ifm3d/camera_tf-3]: started with pid [14374]
[ INFO] [1564137283.812351415]: Loading nodelet /ifm3d/camera of type ifm3d_ros/camera_nodelet to manager camera_standalone_nodelet with the following remappings:
[ INFO] [1564137283.814809864]: waitForService: Service [/ifm3d/camera_standalone_nodelet/load_nodelet] has not been advertised, waiting...
[ INFO] [1564137283.827431501]: Initializing nodelet with 8 worker threads.
[ INFO] [1564137283.836005303]: waitForService: Service [/ifm3d/camera_standalone_nodelet/load_nodelet] is now available.
[ INFO] [1564137283.894540572]: onInit(): /ifm3d/camera
[ INFO] [1564137283.944523009]: Camera clock will not be sync'd to system clock
[ INFO] [1564137283.944600249]: Running dtors...
[ INFO] [1564137283.944697750]: Initializing camera...
[ INFO] [1564137284.958698310]: Initializing framegrabber...
[ INFO] [1564137284.970464464]: Initializing image buffer...
[ INFO] [1564137285.074023901]: Got unit vectors, restarting framegrabber with mask: 15
[ INFO] [1564137285.074075971]: Running dtors...
[ INFO] [1564137285.074609003]: Initializing camera...
[ INFO] [1564137286.085475926]: Initializing framegrabber...
[ INFO] [1564137286.096472427]: Initializing image buffer...
[ WARN] [1564137335.274014374]: Timeout waiting for camera!
[ WARN] [1564137342.629679463]: Timeout waiting for camera!
[ WARN] [1564137355.881443418]: Timeout waiting for camera!
[ WARN] [1564137356.973603497]: Timeout waiting for camera!
What is this timeout waiting for camera ? Thanks

This output:
$ ifm3d ls
null

Indicates to me that you are connecting to the camera, however there are no applications to list. Can you attach the output of $ ifm3d dump?
IIRC, you are running an O3D302 which is the so called "smart sensor" and not the O3D303 which is the "camera". @graugans can an O3D302 run a "camera application"? If the problem is simply to create a new application, you can:
$ echo '{"Apps":[{}]}' | ifm3d config

Then see if it is there with:
$ ifm3d ls

You may also want to try
$ ifm3d reset

However, I do not know what the hard reset state is on an O3D302. For an O3D303, it will give you one usable camera application with the factory default settings.

Sorry, I missed your output above that you now have this working. Regarding the timeout in ROS, can you send the output of $ ifm3d dump? Given that the hz application reported 3 Hz, you are likely at the edge of your configured frame rate and the default timeout of the ROS node. You can either, increase your frame rate on the camera itself, or, if you are happy with 3 Hz, increase the ROS node timeout settings to something like 1000 ms. You can do this on the roslaunch command line or edit the launch file directly. The parameter you want is: timeout_millis.

@matteofiorini and @tpanzarella the smartsensor by default has rectification enabled. There is also a different default setting. I highly recommend to post the output of ifm3d dump

Thanks for the answers. This is the output:
$ ifm3d dump
{
  "ifm3d": {
    "Apps": [
      {
        "Description": "",
        "Id": "557985589",
        "Imager": {
          "Channel": "0",
          "ClippingBottom": "131",
          "ClippingCuboid": "{\"XMin\": -3.402823e+38, \"XMax\": 3.402823e+38, \"YMin\": -3.402823e+38, \"YMax\": 3.402823e+38, \"ZMin\": -3.402823e+38, \"ZMax\": 3.402823e+38}",
          "ClippingLeft": "0",
          "ClippingRight": "175",
          "ClippingTop": "0",
          "ContinuousAutoExposure": "false",
          "EnableAmplitudeCorrection": "true",
          "EnableFastFrequency": "false",
          "EnableFilterAmplitudeImage": "true",
          "EnableFilterDistanceImage": "true",
          "EnableRectificationAmplitudeImage": "true",
          "EnableRectificationDistanceImage": "true",
          "ExposureTimeList": "100;1000;5000",
          "FrameRate": "3",
          "MaxAllowedLEDFrameRate": "19.6",
          "MinimumAmplitude": "42",
          "Resolution": "0",
          "SpatialFilter": {},
          "SpatialFilterType": "0",
          "SymmetryThreshold": "0.4",
          "TemporalFilter": {},
          "TemporalFilterType": "0",
          "ThreeFreqMax2FLineDistPercentage": "80",
          "ThreeFreqMax3FLineDistPercentage": "80",
          "TwoFreqMaxLineDistPercentage": "80",
          "Type": "under5m_high",
          "UseSimpleBinning": "false"
        },
        "Index": "1",
        "LogicGraph": "{\n    \"IOMap\": {\n        \"OUT1\": \"USEROUT\",\n        \"OUT2\": \"NONE\",\n        \"OUT3\": \"RFT\"\n    },\n    \"blocks\": {\n        \"B00001\": {\n            \"pos\": {\n                \"x\": 50,\n                \"y\": 200\n            },\n            \"properties\": {\n            },\n            \"type\": \"MODEL_RESULT_DIMENSIONING\"\n        },\n        \"B00002\": {\n            \"pos\": {\n                \"x\": 1300,\n                \"y\": 1000\n            },\n            \"properties\": {\n            },\n            \"type\": \"STATE_DEFINITION_PASS_FAIL\"\n        },\n        \"B00003\": {\n            \"pos\": {\n                \"x\": 1050,\n                \"y\": 1000\n            },\n            \"properties\": {\n            },\n            \"type\": \"AND\"\n        },\n        \"B00004\": {\n            \"pos\": {\n                \"x\": 1300,\n                \"y\": 100\n            },\n            \"properties\": {\n                \"pulse_duration\": 0\n            },\n            \"type\": \"DIGITAL_OUT1\"\n        },\n        \"B00005\": {\n            \"pos\": {\n                \"x\": 50,\n                \"y\": 800\n            },\n            \"properties\": {\n            },\n            \"type\": \"PIN_EVENT_READY_FOR_TRIGGER\"\n        },\n        \"B00006\": {\n            \"pos\": {\n                \"x\": 1300,\n                \"y\": 800\n            },\n            \"properties\": {\n                \"pulse_duration\": 0\n            },\n            \"type\": \"DIGITAL_OUT3\"\n        }\n    },\n    \"connectors\": {\n        \"C00001\": {\n            \"dst\": \"B00002\",\n            \"dstEP\": 0,\n            \"src\": \"B00003\",\n            \"srcEP\": 0\n        },\n        \"C00002\": {\n            \"dst\": \"B00004\",\n            \"dstEP\": 0,\n            \"src\": \"B00001\",\n            \"srcEP\": 0\n        },\n        \"C00003\": {\n            \"dst\": \"B00003\",\n            \"dstEP\": 0,\n            \"src\": \"B00001\",\n            \"srcEP\": 0\n        },\n        \"C00004\": {\n            \"dst\": \"B00006\",\n            \"dstEP\": 0,\n            \"src\": \"B00005\",\n            \"srcEP\": 0\n        }\n    }\n}\n",
        "Name": "Misurazione oggetto (oggetti parallelepipedi)",
        "PcicEipResultSchema": "{\"layouter\" : \"flexible\",\"format\": { \"dataencoding\": \"binary\", \"order\": \"busdepending\" },\"elements\" : [{ \"type\": \"string\", \"value\": \"star\", \"id\": \"start_string\" },{ \"type\": \"records\", \"id\": \"models\",\"elements\": [{ \"type\": \"int16\", \"id\": \"boxFound\" },{ \"type\": \"int16\", \"id\": \"width\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"height\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"length\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"xMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"yMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"zMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"yawAngle\" },{ \"type\": \"int16\", \"id\": \"qualityWidth\" },{ \"type\": \"int16\", \"id\": \"qualityHeight\" },{ \"type\": \"int16\", \"id\": \"qualityLength\" }]},{ \"type\": \"string\", \"value\": \"stop\", \"id\": \"end_string\" }]}",
        "PcicPnioResultSchema": "{\"layouter\" : \"flexible\",\"format\": { \"dataencoding\": \"binary\", \"order\": \"busdepending\" },\"elements\" : [{ \"type\": \"string\", \"value\": \"star\", \"id\": \"start_string\" },{ \"type\": \"records\", \"id\": \"models\",\"elements\": [{ \"type\": \"int16\", \"id\": \"boxFound\" },{ \"type\": \"int16\", \"id\": \"width\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"height\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"length\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"xMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"yMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"zMidTop\", \"format\": { \"scale\": 1000 } },{ \"type\": \"int16\", \"id\": \"yawAngle\" },{ \"type\": \"int16\", \"id\": \"qualityWidth\" },{ \"type\": \"int16\", \"id\": \"qualityHeight\" },{ \"type\": \"int16\", \"id\": \"qualityLength\" }]},{ \"type\": \"string\", \"value\": \"stop\", \"id\": \"end_string\" }]}",
        "PcicTcpResultSchema": "{\"layouter\" : \"flexible\",\"format\": { \"dataencoding\": \"ascii\" },\"elements\" : [{ \"type\": \"string\", \"value\": \"star;\", \"id\": \"start_string\" },{ \"type\": \"records\", \"id\": \"models\",\"elements\": [{ \"type\": \"int8\", \"id\": \"boxFound\" },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"width\", \"format\": { \"precision\": 3 } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"height\", \"format\": { \"precision\": 3 } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"length\", \"format\": { \"precision\": 3 } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"xMidTop\", \"format\": { \"precision\": 3, \"width\": 6, \"fill\": \"+\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"yMidTop\", \"format\": { \"precision\": 3, \"width\": 6, \"fill\": \"+\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"zMidTop\", \"format\": { \"precision\": 3, \"width\": 6, \"fill\": \"+\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"yawAngle\", \"format\": { \"precision\": 0, \"width\": 3, \"fill\": \"0\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"qualityWidth\", \"format\": { \"precision\": 0, \"width\": 3, \"fill\": \"0\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"qualityHeight\", \"format\": { \"precision\": 0, \"width\": 3, \"fill\": \"0\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" },{ \"type\": \"float32\", \"id\": \"qualityLength\", \"format\": { \"precision\": 0, \"width\": 3, \"fill\": \"0\" } },{ \"type\": \"string\", \"value\": \";\", \"id\": \"delimiter\" }]},{ \"type\": \"string\", \"value\": \"stop\", \"id\": \"end_string\" }]}",
        "TemplateInfo": "{\n    \"oc_and\": false,\n    \"oc_height_lt\": false,\n    \"oc_height_on\": false,\n    \"oc_height_value\": 0,\n    \"oc_length_lt\": false,\n    \"oc_length_on\": false,\n    \"oc_length_value\": 0,\n    \"oc_output1_cb\": 0,\n    \"oc_output1_lt\": true,\n    \"oc_output1_value\": 0,\n    \"oc_width_lt\": false,\n    \"oc_width_on\": false,\n    \"oc_width_value\": 0,\n    \"outputMode\": 2,\n    \"pulsDuration\": 20,\n    \"signalMode\": false,\n    \"stateToggle1\": true,\n    \"stateToggle2\": true,\n    \"stateToggle3\": true,\n    \"stateToggle4\": true,\n    \"stateToggle5\": true,\n    \"stateToggle6\": true,\n    \"stateToggle7\": true,\n    \"type\": \"Dimensioning\",\n    \"version\": \"0.0.1\"\n}\n",
        "TriggerMode": "1",
        "Type": "Dimensioning"
      }
    ],
    "Device": {
      "ActiveApplication": "1",
      "ArticleNumber": "O3D302",
      "ArticleStatus": "AD",
      "Description": "",
      "DeviceType": "1:3",
      "EthernetFieldBus": "1",
      "EthernetFieldBusEndianness": "0",
      "EvaluationFinishedMinHoldTime": "10",
      "ExtrinsicCalibRotX": "0",
      "ExtrinsicCalibRotY": "0",
      "ExtrinsicCalibRotZ": "0",
      "ExtrinsicCalibTransX": "0",
      "ExtrinsicCalibTransY": "0",
      "ExtrinsicCalibTransZ": "0",
      "IODebouncing": "true",
      "IOExternApplicationSwitch": "0",
      "IOLogicType": "1",
      "IPAddressConfig": "0",
      "ImageTimestampReference": "0",
      "Name": "ifm3d unit test",
      "OperatingMode": "0",
      "PNIODeviceName": "",
      "PasswordActivated": "false",
      "PcicProtocolVersion": "3",
      "PcicTcpPort": "50010",
      "SaveRestoreStatsOnApplSwitch": "true",
      "ServiceReportFailedBuffer": "15",
      "ServiceReportPassedBuffer": "15",
      "SessionTimeout": "30",
      "TemperatureFront1": "3276.7",
      "TemperatureFront2": "3276.7",
      "TemperatureIMX6": "38.5559997558594",
      "TemperatureIllu": "40",
      "UpTime": "0.524166666666667"
    },
    "Net": {
      "MACAddress": "00:02:01:40:59:EA",
      "NetworkSpeed": "0",
      "StaticIPv4Address": "<IP_ADDRESS>",
      "StaticIPv4Gateway": "<IP_ADDRESS>",
      "StaticIPv4SubNetMask": "<IP_ADDRESS>",
      "UseDHCP": "false"
    },
    "Time": {},
    "_": {
      "Date": "Fri Jul 26 18:11:55 2019",
      "HWInfo": {
        "Connector": "#!02_A310_001_02754976_008022060",
        "Diagnose": "#!02_D312_C32_02832709_008023267",
        "Frontend": "#!02_F342_C32_16_00080_008022797",
        "Illumination": "#!02_I300_001_02746542_008001175",
        "MACAddress": "00:02:01:40:59:EA",
        "Mainboard": "#!02_M381_003_02816713_008022954",
        "MiraSerial": "1030-591d-00a9-0abc"
      },
      "SWVersion": {
        "Algorithm_Version": "1.2.19",
        "Calibration_Device": "00:02:01:40:59:ea",
        "Calibration_Version": "0.9.0",
        "Diagnostic_Controller": "0.3.207",
        "ELDK": "GOLDENEYE_ELDK-2016-07-14_09-36-02-2e9219cce224332ecbe2f36934d2c3c7aa738c78",
        "IFM_Software": "1.6.2114",
        "Linux": "Linux version 3.11.0-00002-gd1bbe0b (eswadmin@dettlx79) (gcc version 4.7.2 (GCC) ) #1 SMP Fri Jun 24 16:34:26 CEST 2016",
        "Main_Application": "0.4.222"
      },
      "ifm3d_version": 1501
    }
  }
}

I am trying to use software triggered mode but it is not working. It works in continuous mode even if I type:
$ GLOG_minloglevel=3 roslaunch ifm3d camera.launch assume_sw_triggered:=true
I also changed the parameter in the camera.launch file but in rviz I can still see continuous images.
Another question:
Do you know which is the best software for recognition using either the point cloud image or the xyz image on ros?
Thanks

For the camera to run in software triggered mode, you need to set that parameter on the camera itself for the particular application in question. Once you have done that, you invoke the ROS node as you have done above. To that end, for your configuration, to set the active application into software triggered mode, you can:
$ ifm3d dump | jq '.ifm3d.Apps[0].TriggerMode="2"' | ifm3d config

This assumes that you have the jq command available. If you do not have it, you can get it with:
$ sudo apt install jq

Per your second question regarding "recognition". 1) It is under-specified; 2) it is outside of the scope of support we can offer for the sensor interface.
HTH.

I am going to mark this issue as closed as your connection problems are solved. If other issues come up, please open a new issue specific to it. Thank you.


Remove dev requirements in production requirements.txt

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.50%. Comparing base (82d02c2) to head (980aab0).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #669   +/-   ##
=======================================
  Coverage   93.50%   93.50%
=======================================
  Files          20       20
  Lines        2125     2125
=======================================
  Hits         1987     1987
  Misses        138      138

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Configurations of OpenTelemetryCollector and AMP Rules for AmpAddOn

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @freschri Thankyou for the PR. I think you might have to close the PR and reopen a new PR for same branch after rebase. I think you are showing changes from many previous PRs merged. Could you please fix that and let us know. I also for some reason dont see your changes for AMP in this PR.

Hi @freschri Thankyou for the PR. I think you might have to close the PR and reopen a new PR for same branch after rebase. I think you are showing changes from many previous PRs merged. Could you please fix that and let us know. I also for some reason dont see your changes for AMP in this PR.

created new one as requested: https://github.com/aws-quickstart/cdk-eks-blueprints/pull/801


feat: use sha in cache lock file, needed for source builds.

Description
This PR adds the ability in the cache to use the sha256 of a key as the cache lock file as well.
This is needed so that source build archives with the same paths but different contents are correctly replaced in the cache.

Ok just tested it out with pixi-build and seems to work like a charm.


Handle encrypted databases during migration

Before the password was only handling startup but would not work for
migrations. This will include password handling as part of migrations as
well as startup.
Fixes #1505

Coverage remained the same at 35.721% when pulling 3cbedec9ab3b2dc8bce77338a470fb83ce7408cd on 1505-interactive-db-password into 2e5cb7812bb8547374e116669aa709d3e2b82801 on master.


Tips for file structure

https://gist.github.com/agendor/9922151

These guys' use this file structure:
|-controllers/
|-dao/
|-models/
|-routes/

Reminds me of the Codeigniter php style file structure. I'm not sure I'm into that - I like the whole namespace setup that would be more like
/src
  |-example
    |-exampleRoutes.js
    |-exampleController.js
    |-exampleModel.js

I set up a working example in the hapi branch. What do you think? Do you think that since the rest of the community seems to organize their files in the former style that we should follow suit?

I wonder if they organize that way to simplify require() calls or something?


Enhancement: Improve API Endpoint Documentation

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs

Why was this change needed? (You can also link to an open issue here)

Other information:

Numbering the APIs looks better,should we do this?
1. /api/answer1
it looks more better ig

@rahul0x00  sorry, yes please push numbering, thank you for the suggestion

Hi, @dartpain
numbered the api's

@dartpain  just a reminder


First Item in CircleLayout Click not found

So i have implemented circleLayout.setOnItemSelectedListener but my problem is I am getting clicks for every other child except the first child in the CircleLayout

setOnItemSelectedListener is used to know which item is closest to the firstChildPosition when the circle is rotating. You have to implement the OnItemClickListener interface if you are intersted in Click events only.


503 Service Unavailable (IBKR/Gateway issue)

Describe the bug
IBKR/Gateway sometimes runs into returning a 503 Service Unavailable error. In this issue we try to understand what can be done to overcome it.
Environment
IBeam-independent, it is the Gateway's issue
Additional context
So far it has been observed when calling:

/iserver/account/{accountId}/orders

In https://github.com/Voyz/ibeam/issues/7#issuecomment-945684378 @Wenuka outlines:
when I tried to place an order (using https://localhost:{port_num}/v1/api/iserver/account/{accountId}/orders API) I am getting a 503 response as below,
{'_content': b'', '_content_consumed': True, '_next': None, 'status_code': 503, 'headers': {'x-response-time': '10000ms', 'X-Cnection': 'close', 'Expires': 'Mon, 18 Oct 2021 11:32:58 GMT', 'Cache-Control': 'max-age=0, no-cache, no-store', 'Pragma': 'no-cache', 'Date': 'Mon, 18 Oct 2021 11:32:58 GMT', 'Connection': 'close', 'Server-Timing': 'cdn-cache; desc=MISS, edge; dur=4, origin; dur=10019', 'Vary': 'Origin', 'Transfer-Encoding': 'chunked'}, 'raw': <urllib3.response.HTTPResponse object at 0x7f15b168d520>, 'url': 'https://localhost:5000/v1/api/iserver/account/XXXXXX/orders', 'encoding': None, 'history': [], 'reason': 'Service Unavailable', 'cookies': <RequestsCookieJar[]>, 'elapsed': datetime.timedelta(seconds=10, microseconds=68901), 'request': <PreparedRequest [POST]>, 'connection': <requests.adapters.HTTPAdapter object at 0x7f15b166aeb0>}

Then I killed the docker session and re-run using the changed proxyRemoteHost value and it worked as expected.

In https://github.com/Voyz/ibeam/issues/19#issuecomment-946766857 @isque03 outlines:
Gateway logs show this:

GET /v1/api/tickle,200|61ms
02:43:34.032 DEBUG vert.x-eventloop-thread-0 ClientPortalService  : tickle > {"session":"asdasdadasd","ssoExpires":469642,"collission":false,"userId":123456,"iserver":{"authStatus":{"authenticated":true,"competing":true,"connected":true,"message":"Another session with the same user name has disconnected your session.","MAC":"00:00:00:00:00:00"}}}

The only workaround I have found so far is to manually log into IBKR on the mobile app (or I suppose web/desktop). It will say "another session is in use, disconnect?" I click "yes" to disconnect, then I explicitly click the logout in the mobile app. After this I'm able to get a properly working brokerage session from the logout/reauthenticate flow.
My suspicion is that it's the call for brokerage session ssodh/init that the gateway makes.
See this document again: https://www.tradersinsight.news/ibkr-quant-news/tutorial-web-api-connect-to-brokerage-session/
Specifically the compete param in here:
`SSODH Init Request
POST  https://api.ibkr.com/v1/api/iserver/auth/ssodh/init
The body, of type x-www-form-urlencoded, must have the following parameters:
      machineId (String)       8 char alphanumberic string e.g. CCCCCC01-99
      mac (String)                   six 2-char alphanumerical pairs separated by a hyphen
      **compete (Boolean)      whether or not the session should compete, usually set to false**
      locale (String)                set to “en_US
      username (String)        set to dash “-“`

The compete param here recommends setting it to false. What I think this does is trigger any other brokerage session to be invalidated, and allow a new one to be created. Setting compete "true" I beleive means that it will not kick out the other session. (Even though that seems sort of backwards from what you'd expect)
The gateway passes complete:true. (From gateway logs)
post={"username":"XXXX","machineId":"12349","compete":true}
Programmatic workarounds here? I think the only choices are:

File a ticket with IBKR and see if they'll add the ability to control the compete param in the gateway
Have iBeam actually implement the ssodh/init /complete flows to explicitly trigger brokerage session creatation (this would replace the call to /reauthenticate). I have not proven this compete true|false theory, so I wouldn't recommend going down this path yet.

@isque03 brought this discussion over from #19. Thanks for being very detailed once again, great information.

I have not proven this compete true|false theory, so I wouldn't recommend going down this path yet.

Have you considered doing it? Would it be as simple as adding a HTTP request to your existing flow to verify this theory?

Giving it a try tonight.
The document here isn't quite correct:
https://www.tradersinsight.news/ibkr-quant-news/tutorial-web-api-connect-to-brokerage-session/

First it's only taking Content-Type: application/json
username has to be the actual username, not '-'.
After those changes I did get a challenge hash.

The response is a bit tougher:
Challenge and Response
The challenge is needed to calculate the challenge response, or R whereby seed = challenge, verifier = st.
To calculate R, ensure both the challenge and session token calculated during initial authentication are in hex form. Then, concatenate the challenge and session tokens, with the challenge being in front.
The problem here is I'm not sure we have access to the "session token" referred to in the document. I can see in the gateway logs it prints the session token out as "K=". It also prints K=XXX for the final challenge response, not the session token. So, that's a bit confusing.
Using test values from the log. This will calculate the correct response value given the challenge, plus the session token.
const crypto = require('crypto'); const hash = crypto.createHash('sha1'); const seed = process.argv[2]; const verifier = process.argv[3]; hash.update(Buffer.from(seed + verifier, 'hex')); const result =  hash.digest('hex'); console.log(result);
Almost there.. Just need to figure out how to get the session token!  I noticed the /v1/api/tickle endpoint returns a property called session in its response. But this doesn't seem to be the correct value. It never matches K= in the logs and when I use that to calculate the response I just get a 10 second delay, then a 503 response.

Just an update here. I wasn't able to get the session token. But it looks like it's available during the initial SSO process. This is the SSO process that is done through the browser.
See #19 for details. Short summary that I followed a suggestion from @DanielHTpg and setup a proxy to intercept the brokerage session initialization call. It turns out that compete=false was actually worse.
I have found that it is stable if I only login in one place. Still testing with paper account, so I basically just don't log into that account except through the gateway.  IBKR allows creating additional login accounts, so for live trading it's probably best to create a new login account that is dedicated to iBeam / gateway logins.

Thanks for the updates on this @isque03 👏 I haven't got anything to comment on the process at this stage, but I appreciate you sharing the results of your attempts. Good observations on logins 👍

I've been using voyz/ibeam:0.4.0-rc1 with docker-compose now for two weeks. I've also added cronjobs to stop ibeam outside of trading hours and restart it before trading opens for the region I trade in. Since those two weeks I didn't have any troubles with getting errors on the trading endpoints. I request order data frequently and before the newest rc1 and docker-compose changes if had to change proxyRemoteHost atleast once a week. Previously I didn't use docker-compose and had the ibeam-container running indefinitely.
Since I don't persist the docker logs in any way, I loose all logs, since docker-compose cleans up the containers daily. So I can't check if the logout happend at some point before. What I also think helps alot now, is that each day ibeam and the IB gateway get a complete clean new container without any previous caches or whatnot. This might be the main reason, that I've not had the issue anymore.

@DanielHTpg thanks for suggesting cleaning out the container daily - that's an interesting observation. Anyone else here tried this method and can comment on its results?
Also, that suggestion to keep the requests repeating is good to point out - thanks for sharing it and that output from your trading system.

But the /iserver/accounts returns an empty account with 200 status

@alex1999Tra that's new, I don't think anyone encountered this yet, we've seen 503s on that endpoint so far. I'd suggest getting in touch with IBKR support and trying to see what they say about it.

@Voyz The issue with no accounts being returned was one of the biggest problems I had after switching the proxyRemoteHost. Sometimes it only went away the next day. Since using docker-compose I haven't this issue.

any update on this issue?
I'm facing response 503 while placing orders. I tried rate limiter to limit the API calls but still no use.

@eswark18 I'd suggest highlighting it with IBKR, as this is an internal server error reported back to IBeam

I'm seeing the same issue. When I place an order then call iserver/reply, I'm getting:
'Response code 503 (Service Unavailable)'

I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to reopen if you'd like to continue the discussion 👍


Opentracing beta5 version

Hello,
there are any plans about implement a newest version of the opentracing API - beta5?

Not sure,I don't know its role.

@jukylin hi! great library here.
Do you have any plans to upgrade to the latest beta5 of opentracing api?
Just asking :)
One of the things that I miss is an easy way for active span management so you don't have to reference always the root span all the time.

done v2.0.8-beta

Thanks a lot!


merge_rule2

Dear author, sometimes during runtime, it gets stuck at the "merge_rule2" section. What could be the reason for this?

Dear author, sometimes during runtime, it gets stuck at the "merge_rule2" section. What could be the reason for this?

Thank you for trying our tools. Could give me more details about the error?  For example, could you show me the code and dataset to reproduce the bug ? Because I haven't encounted the problem before, I can't figure out what happened without your code and dataset.  If the tested dataset is large, you can send the dataset to my email(yuxiaokang2018@163.com). I will  try my best to solve the problem.

Dear author, sometimes during runtime, it gets stuck at the "merge_rule2" section. What could be the reason for this?

Thank you for trying our tools. Could give me more details about the error? For example, could you show me the code and dataset to reproduce the bug ? Because I haven't encounted the problem before, I can't figure out what happened without your code and dataset. If the tested dataset is large, you can send the dataset to my email(yuxiaokang2018@163.com). I will try my best to solve the problem.

Dear author,
It seems I've encountered an issue. Before running, I set ncluster_list as a list containing multiple values. By default, I set it to range from 1 to 20. However, I found that removing the value 1 from this list resolved the problem of it getting stuck. Interestingly, I haven't encountered this error when testing with other datasets using the default range from 1 to 20. So, I'm puzzled as to why this bug occurs. It appears that ncluster_list cannot contain the value 1 for certain datasets. Thank you for your response.

Dear author,
I have a further update. Previously, I set the ncluster_list to range from 1 to 20 because setting it to specific values sometimes resulted in errors like "Optimal number of clusters [ x x x x]". Hence, I opted for a broader range to avoid this bug. However, when I switched to a different preprocessing method for the same dataset, I found that using the range from 1 to 20  led to errors.

Dear author,
I have a further update. Previously, I set the ncluster_list to range from 1 to 20 because setting it to specific values sometimes resulted in errors like "Optimal number of clusters [ x x x x]". Hence, I opted for a broader range to avoid this bug. However, when I switched to a different preprocessing method for the same dataset, I found that using the range from 1 to 20 led to errors.

Thank you for your information, it's look very strange,  I can't give you any useful suggestions now , because I don't know why this happens either😆. Maybe you can provide me a jupyter notebook to reproduce the bug, so I can debug the source code in detail.

Dear author,
I have a further update. Previously, I set the ncluster_list to range from 1 to 20 because setting it to specific values sometimes resulted in errors like "Optimal number of clusters [ x x x x]". Hence, I opted for a broader range to avoid this bug. However, when I switched to a different preprocessing method for the same dataset, I found that using the range from 1 to 20 led to errors.

Thank you for your information, it's look very strange, I can't give you any useful suggestions now , because I don't know why this happens either😆. Maybe you can provide me a jupyter notebook to reproduce the bug, so I can debug the source code in detail.

Hello,
I will send you the ipynb file later, but I may not be able to do it promptly due to some work I have to finish first. I believe the possible error could be that I noticed when the first element in "optimal clusters" is 1 and expect_num_cluster=None, it may lead to this error. The reason for this error is that the data I used is not single-cell data but other data that requires batch effect removal. Therefore, the estimated number of clusters may not represent multiple cell types but possibly only one type.

OK, you can send me the ipynb and test data in your free time.  Don't hesitate to contact me if you have any questions about the package.  Happy to chat😊


Atlantis v0.6.0

What this PR does / why we need it:
Latest Atlantis version and camelCase values.

- upgrade Atlantis to v0.6.0
- use camelCase variables in values.yaml instead of snake_case
- add imagePullSecrets list

Which issue this PR fixes
None
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/lgtm

I've tested this manually on a kube cluster to verify.

/approve

/assign jkodroff jeff-knurek sstarcher

@jkodroff @jeff-knurek I think you need to accept the invite to be a collaborator in this repo in order to be assigned reviews. Did you get the invite?

Closes #12381

I never got an invite.
https://github.com/helm/charts#trusted-collaborator
The process to get added is:

* File an issue asking to be a trusted collaborator
* A Helm Chart Maintainer can then add the user as a read only collaborator to the repository

I also don't think there was ever a request for either of us to become collaborators.

Well this is ridiculous... @jeff-knurek would you mind taking my commits and creating a new pull request? Then I can actually approve it and we can get this fixed merged.

fixes #12530

I also did not receive an invite and have basically given up hope of receiving one.

/lgtm

@jkodroff which invite?

@jkodroff which invite?

https://github.com/helm/charts/issues/12531 invite to be a collaborator of helm/charts so he can jeff can approve Atlantis prs
Thanks @cpanato! If you can help with ☝ that would be awesome, or point us to instructions if there's a better way to accomplish that.


add AWS Community Day - Kochi

Issue #, if available:
Description of changes:
Adding AWS Community Day - Kochi to upcoming events, which is hosting a workshop on AWS Amplify.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks @hnprashanth! Please email aws-amplify-customer@amazon with your name, address, phone number, and tshirt size.


SHA-256 error when using the CDN

When including bootstrap in my website using the CDN Url
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.4.1/css/bootstrap.min.css"
              asp-fallback-href="~/lib/bootstrap/dist/css/bootstrap.min.css"
              asp-fallback-test-class="sr-only" asp-fallback-test-property="position" asp-fallback-test-value="absolute"
              crossorigin="anonymous"
              integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" />

I get the following error in my console:

failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.4.1/css/bootstrap.min.css' with computed SHA-256 integrity 'L/W5Wfqfa0sdBNIKN9cG6QA5F2qx4qICmU2VgLruv9Y='. The resource has been blocked.
Am I missing something?
Using bootstrap 4.4.1 in a .NET Core 3 project. Error happens when visiting the website in Google Chrome.

My mistake. Integrity key should be sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh


Upgrade for support recent OS

Is a big problem for those who install a recent OS like Ubuntu 22 or Debian 11.
The problem is mysql, maybe upgrade with this https://github.com/Sphereserver/Source-X/pull/881 for support newest os

I've tried building / running on Debian 11 (in WSL) and currently it seems pretty simple.
Building
I've deleted all mysql / mariadb libs.
sudo apt install libmysql++-dev Only mysql lib I needed, nothing from external repos.
Running
I've deleted all mysql / mariadb libs again.
sudo apt install libmariadb3 Again from default repository. I've tried connecting to database on different machine (from Debian 11 in WSL to MariaDB 11.0 on localhost) and it works ok (connection, query, getting values from columns).

That pr has too much unneeded files to include, unfortunately... And i won't be sad if we officially switch to mariadb connector

Maybe updating info in readme and/or build actions would be enough to make it clear how to run with current OS / tools.

Should be solved now


Bump up the latest UI

What this PR does / why we need it?

Add favicon, meta tags

You can change SITE_URL in .env for og:url meta tag

Show active style in project tab menu and document list
Apply color according to dark mode in CodeBlock component
Use CSS's @supports which has full browser coverage: https://github.com/facebook/create-react-app/issues/6287

Any background context you want to provide?
What are the relevant tickets?

Fixes #
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

@chacha912 Thanks for your contribution. 👍


gfx_device_metal dependency fails to compile on Mac

Just cloned gfx and wanted to check out the examples but getting compile errors on the gfx_device_metal dependency. Any idea if this is something on my end? Build log below:
Compiling gfx_device_metal v0.1.0 (file:///Users/ccostes/Documents/gameDev/gfx/src/backend/metal)
src/backend/metal/src/command.rs:383:5: 403:6 error: method `clone_empty` is not a member of trait `draw::CommandBuffer` [E0407]
src/backend/metal/src/command.rs:383     fn clone_empty(&self) -> Self {
                                         ^
src/backend/metal/src/command.rs:383:5: 403:6 help: run `rustc --explain E0407` to see a detailed explanation
src/backend/metal/src/factory.rs:299:24: 299:60 error: attempted access of field `stride` on type `u8`, but no field with that name was found
src/backend/metal/src/factory.rs:299         buf.set_stride(desc.attributes[0].unwrap().0.stride as u64);
                                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/backend/metal/src/factory.rs:309:16: 309:27 error: attempted access of field `offset` on type `&u8`, but no field with that name was found
src/backend/metal/src/factory.rs:309             if elem.offset & 1 != 0 {
                                                    ^~~~~~~~~~~
src/backend/metal/src/factory.rs:311:32: 311:43 error: attempted access of field `offset` on type `&u8`, but no field with that name was found
src/backend/metal/src/factory.rs:311                     attr.name, elem.offset);
                                                                    ^~~~~~~~~~~
<log macros>:7:46: 7:77 note: in this expansion of format_args!
<log macros>:9:1: 9:62 note: in this expansion of log! (defined in <log macros>)
<log macros>:4:1: 4:55 note: in this expansion of log! (defined in <log macros>)
src/backend/metal/src/factory.rs:310:17: 311:45 note: in this expansion of error! (defined in <log macros>)
src/backend/metal/src/factory.rs:317:52: 317:63 error: attempted access of field `format` on type `&u8`, but no field with that name was found
src/backend/metal/src/factory.rs:317             attribute.set_format(map_vertex_format(elem.format).unwrap());
                                                                                ^~~~~~~~~~~
src/backend/metal/src/factory.rs:318:34: 318:45 error: attempted access of field `offset` on type `&u8`, but no field with that name was found
src/backend/metal/src/factory.rs:318             attribute.set_offset(elem.offset as u64);
                                                                      ^~~~~~~~~~~
src/backend/metal/src/factory.rs:342:80: 342:92 error: mismatched types [E0308]
src/backend/metal/src/factory.rs:342             pso_descriptor.set_depth_attachment_pixel_format(map_depth_surface(depth_desc.0).unwrap());
                                                                                ^~~~~~~~~~~~
src/backend/metal/src/factory.rs:342:80: 342:92 help: run `rustc --explain E0308` to see a detailed explanation
src/backend/metal/src/factory.rs:342:80: 342:92 note: expected type `gfx_core::format::SurfaceType`
src/backend/metal/src/factory.rs:342:80: 342:92 note:    found type `gfx_core::format::Format`
src/backend/metal/src/mirror.rs:68:44: 68:68 error: missing field `elements` in initializer of `gfx_core::shade::ConstantBufferVar` [E0063]
src/backend/metal/src/mirror.rs:68                 info.constant_buffers.push(shade::ConstantBufferVar {
                                                                              ^~~~~~~~~~~~~~~~~~~~~~~~
src/backend/metal/src/mirror.rs:68:44: 68:68 help: run `rustc --explain E0063` to see a detailed explanation
error: aborting due to 7 previous errors
Build failed, waiting for other jobs to finish...
error: Could not compile `gfx_device_metal`.

I saw that you'd also done this @ccostes , but for future people who might read before it's fixed, here's how I got the current examples to compile on OSX.
remove_metal_diff.txt


chore: Remove macros_api module

Description
Problem
Resolves #6176
Summary
Removes the noir_frontend::macros_api module and fixes the use statements where it appeared.
Additional Context
See the linked ticket for why it's not needed any more.
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Looks good, I've removed the issue number from the PR title as that gets injected when merged anyway.


Prefix

Finishes #13

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

CircleCI is not starting :unamused:

@ocefpaf You need to increment the build number so a new package is uploaded.  Besides that this looks good.

Just notice that too :smile:


Zig build api change

Damn it, the API changes too frequently, it’s really a headache, so I completely separated the build process of 0.11 and nightly. Although this will add a lot of duplicate code, it will reduce the maintenance work in the future.

Thank you @jinzhongjia for maintaining the Zig wrapper. It's exciting. I have yet to look deeply into the Zig wrapper as I'm busy with the C lib and other projects and work. But in general, the other wrapper's developer waits until webui has a new stable release, then they read the release note and wrap the new APIs once. Hopefully, this will be more straightforward and less headache.

Yes, the current commit is mainly used to follow the official zig build system changes. This situation is only temporary.

My main complaint is the changes to the zig build system, which may not stabilize until 0.12 is officially released


Bump version to 0.1.7 in the CocoaPods Repo

Please also bump the version to 0.1.7 in the CocoaPods repository.

Looks like someone did this 😄 thx


Update_button_doc

Description
update documentation for buttons

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Codecov Report

Merging #249 (b0d3fad) into master (55dfd83) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #249      +/-   ##
==========================================
+ Coverage   77.49%   77.51%   +0.01%
==========================================
  Files         130      130
  Lines       12264    12264
  Branches     1305     1307       +2
==========================================
+ Hits         9504     9506       +2
+ Misses       2760     2758       -2

Flag
Coverage Δ

unittests
77.51% <ø> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/lib/components/list/list-items.tsx
97.16% <0.00%> (+1.41%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update dead links in Documentation

Updated a dead link with a direct link to the notebook
Removed reference to a DLRM benchmark that doesn't exist anymore (not sure, please check)

rerun tests


Negative

Hi,
I always got negative value when I was collection data for l2-load-latency workload on your XL710. After some investigation, I came to these two patches.
Can you please have a look on the patch to see if it's the right solution?
Thanks
--jyh

Hi, emmericp
Can you please have a look on the patches?
Thanks
--jyh

Hi Yunhong,
This is a fork of MoonGen that I manage at Princeton. I added the support for XL710 NICs in the existing MoonGen framework. I am busy with some other work at the moment, but will look into these patches soon.
Thanks,
Shahbaz

Ok, just looked through the patches quickly. They look good to me. I will merge them in, shortly.

Shahbaz, thanks for the check.
--jyh

I "merged" the X710 timestamping with your improvements into my dpdk2.0 branch:
https://github.com/emmericp/MoonGen/commit/3025ed5a0d10edc32aa0adc5d8497a286540ea55

Thanks.


Fix/timeline vertical

[x] I have followed the Your First Code Contribution section of the Contributing guide

Fixed the problem with vertical-oriented <Timeline.Content /> component style. The root.base class theme prop is now independent on orientation. The optional root.vertical and root.horizontal props were introduced to make orientation-specific style changes.
Fix #1196
If there are breaking API changes - like adding or removing props, or changing the structure of the theme - describe them, and provide steps to update existing code.
interface FlowbiteTimelineContentTheme has been changed. The theme now supports optional root.vertical and root.horizontal props.

ported to #1430 due to new monorepo structure

ported to #1430 due to new monorepo structure


Pulse page improvements

add border-radius and spacing to bars
use tailwind background classes
Add more space around activity list headers

There is nothing dangerous in this PR so I would backport.


Add case number input to additional info page

Ran into some git squash issues with this branch for some reason - closing this one and merging #233


PHPUnit not installed by default

After run step 6 of DEVELOPMENT_README.md the following message is shown:
...
Installing PHPUnit
Updating channel "doc.php.net"
Update of Channel "doc.php.net" succeeded
Updating channel "pear.php.net"
Channel "pear.php.net" is up to date
Updating channel "pecl.php.net"
Channel "pecl.php.net" is not responding over http://, failed with message: File http://pecl.php.net:80/channel.xml not valid (redirected but no location)
Trying channel "pecl.php.net" over https:// instead
Channel "pecl.php.net" is up to date
Will upgrade channel://pear.php.net/archive_tar
downloading Archive_Tar-1.3.13.tgz ...
Starting to download Archive_Tar-1.3.13.tgz (19,891 bytes)
.......done: 19,891 bytes
upgrade-all ok: channel://pear.php.net/Archive_Tar-1.3.13
config-set succeeded
Attempting to discover channel "pear.phpunit.de"...
downloading End-of-Life-for-PEAR-Installation-Method ...
Starting to download End-of-Life-for-PEAR-Installation-Method (Unknown size)
......done: 28,088 bytes
unknown channel "pear.phpunit.de" in "pear.phpunit.de/PHPUnit-3.4.15"
invalid package name/package file "pear.phpunit.de/PHPUnit-3.4.15"
install failed

PHP version 5.5.20 is now installed. Type: pe 5.5.20

Running example lines of step 7 the following error can be viewed:
The program 'phpunit' is currently not installed.  You can install it by typing:
sudo apt-get install phpunit

The script php-build.sh tries to install PHPUnit via PEAR but that method is no longer supported: https://github.com/sebastianbergmann/phpunit/wiki/End-of-Life-for-PEAR-Installation-Method


chore(package): bump dev deps

coverage: 97.236%. remained the same
when pulling e8da9a9da2112c35db9bc970ac4446fcf44275ac on dev-deps
into 77f320e4dca8247167471393dcbce2b1e333b7cf on master.


Adjust schedules for view and data refresh DAGs

Current Situation

Currently the *_data_refresh run @weekly, so UTC 0 Sunday morning, and the associated refresh_*_view_data run at UTC 00:00 every day except the first of the month.
Suggested Improvement

Since we want the view refresh to run before the data refresh, it might be better to run both sets of DAGs weekly with an offset to allow the view refresh to finish before the data refresh begins. For example, we could switch the view refreshes to @weekly so they run at default Sunday UTC 00:00, and schedule the data refreshes to run weekly on Mondays, so they begin during working hours and having given the view refresh time to complete.
Additional context

In future iterations, we plan on consolidating dependencies into a single data_refresh DAG.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

TL;DR: I don't think we should act on this until #453, which will resolve the scheduling much more effectively by coupling the popularity calculation/matview refresh/data refresh tasks in Airflow.
Currently, we run refresh_all_*_popularity_data (which calculates popularity data and refreshes the matview) on the first day of each month, and refresh_*_view_data (which only refreshes the matview) on all other days. The data refresh itself is run weekly, each Sunday at UTC 0:00.
The matview appears to only be used by the data refresh, so it's not really necessary for it to run every day -- we could just run it weekly, before the data refresh. To my knowledge though, we can't easily express this in a cron expression while also avoiding runs on the first of the month. Of course there are a number of ways to get around this (checking the date within the task, setting up dependencies between the DAGs) but anything more complicated than updating the schedule interval doesn't seem like a worthwhile investment when #453 is already planned for the next milestone.
I think the simplest way forward is to turn off the data refresh DAGs temporarily. This is only because this coming Sunday is May 1st, which happens to be both the first of the month and the first of the week -- so the popularity data calculations and data refreshes will be triggered simultaneously. We should wait for the popularity calculations to complete early next week before turning the data refreshes back on. We then have until January 2023 before the first of the month falls on a Sunday again, in order to complete #453 😄

These are great points Staci! And what an unfortunate calendar collision 😅 Per a discussion in the Make WordPress slack, we're going to close this in favor of #453. We believe that work will cover the problems expressed in this issue.


Remove line-break

This small PR does nothing more than the title says.
FYI @dsarkar.

@Ein-Tim Thanks.


Fix compilation error when compiling with disabled exceptions and c++ >11

Example:
#include "tsl/robin_set.h"
#include <iostream>

int main()
{
	tsl::robin_set<int> Set;
	Set.insert(1234);
	std::cout << Set.size() << '\n';
}

when compiled with standard newer than c++11, for example:
clang++-7 -O3 -std=c++14 -fno-exceptions main.cpp
gives:
In file included from main.cpp:1:
In file included from ./tsl/robin_set.h:34:
./tsl/robin_hash.h:509:48: error: expected expression
                                               TSL_RH_THROW_OR_TERMINATE(std::length_error, "The map exceeds its maxmimum bucket count."):
                                               ^
./tsl/robin_growth_policy.h:56:52: note: expanded from macro 'TSL_RH_THROW_OR_TERMINATE'
#        define TSL_RH_THROW_OR_TERMINATE(ex, msg) do { std::fprintf(stderr, msg); std::terminate(); } while(0)
                                                   ^
In file included from main.cpp:1:
In file included from ./tsl/robin_set.h:34:
./tsl/robin_hash.h:509:48: error: expected ':'
                                               TSL_RH_THROW_OR_TERMINATE(std::length_error, "The map exceeds its maxmimum bucket count."):
                                               ^
                                              :
./tsl/robin_growth_policy.h:56:52: note: expanded from macro 'TSL_RH_THROW_OR_TERMINATE'
#        define TSL_RH_THROW_OR_TERMINATE(ex, msg) do { std::fprintf(stderr, msg); std::terminate(); } while(0)
                                                   ^
./tsl/robin_hash.h:508:80: note: to match this '?'
                                           ((bucket_count > max_bucket_count())?
                                                                               ^
./tsl/robin_hash.h:509:48: error: expected expression
                                               TSL_RH_THROW_OR_TERMINATE(std::length_error, "The map exceeds its maxmimum bucket count."):
                                               ^
./tsl/robin_growth_policy.h:56:52: note: expanded from macro 'TSL_RH_THROW_OR_TERMINATE'
#        define TSL_RH_THROW_OR_TERMINATE(ex, msg) do { std::fprintf(stderr, msg); std::terminate(); } while(0)
                                                   ^
3 errors generated.

After this fix compiles fine.

Hello,
Thank you very much for your contribution. It effectively doesn't work with C++ > 11 since some recent changes in commit 5d3f52f4ef86e321bdcb1cb4521fa8f45c0043c9. I'll check to add some tests with -fno-exceptions in the CI to catch this kind of error earlier.
Concerning the PR, I would avoid that the statement generated by TSL_RH_THROW_OR_TERMINATE returns an integer as even if it works in the current situation, it wouldn't with some other ternary operations like
bucket_count > max_bucket_count()?TSL_RH_THROW_OR_TERMINATE(std::runtime_error, "foo"):
                                  std::string("bar");

I think a better solution would be to leave the macro as it currently is and to change the constructor with:
m_buckets_data(
    [&]() {
        if(bucket_count > max_bucket_count()) {
            TSL_RH_THROW_OR_TERMINATE(std::length_error,
                                        "The map exceeds its maximum bucket count.");
        }

        return bucket_count;
    }(), alloc
)

Would this solution be alright for you?

Hi,
Yeah, good point.
I think your solution is better. 👌

I merged the changes, thank you for your contribution.
I'll check to add some extra tests in the CI tomorrow for -fno-exceptions to avoid breaking inadvertently the compatibility with this option.


Continue processing hands even when time is paused

Since UpdateHandPoses() is called from FixedUpdate(), this is not called when the game is paused using the common method of setting Time.timeScale to 0.0f.  This change ensures that UpdateHandPoses() is still called while time is paused.

Thanks for the PR. This is fixed in the recent versions as you can now designate when poses are updated.


Add cuchi/jinja2-action

That seems like the first action which uses a template engine. I think it should go under the Utility section.

Thanks!


Withdraw collateral asset from vault

Task: Feature Name:
Controller: withdraw collateral asset
High Level Description
This PR add the needed code for the withdraw collateral functionality.
Should be reviewed/merged after #105 .
Code

[ ] Unit test 100% coverage
[x] Does your code follow the naming and code documentation guidelines?

Documentation

[x] Is your code up to date with the spec?
[x] Have you added your tests to the testing doc?

Looks great!! Can we also add a test for cannot remove more collateral than the vault owner has? After that good to merge!

Added.