CRS warning and error due to mini shift in extent?

niche_vlaanderen version:1
Python version:3
Operating System: Win 7

Niche Python Package question
Description
I get a CRS warning when I try to load the following tifs (here), while it seems to me that they are both in EPSG 31370. When I try to run the model I get an error "error: different grid size or orientation".
There might be a minimal shift (< 0.00001 mm) between the 2 (not even visible in ArcGIS, but) QGIS reports the following characteristics:
grid_brasschaat
CRS EPSG:31370 - Belge 1972 / Belgian Lambert 72 - Projected
Extent
153884.2065000000002328,216245.0000000030559022 :<PHONE_NUMBER>199956858996,227200.0000000000000000
Pixel Size 24.98426339693833143,-24.95444191343267448 (notice they are asymmetric as expected)
bodem
CRS EPSG:31370 - Belge 1972 / Belgian Lambert 72 - Projected
Extent
153884.2065000000002328,216245.0000000000000000 :<PHONE_NUMBER>199999932665,227200.0000000000000000
Pixel Size
24.9842633969465524,-24.95444191343963425
Could this be the cause of the error? Or am I overlooking something else?
What I Did
import niche_vlaanderen as nv
import matplotlib.pyplot as plt

# A simple model
simple = nv.Niche()

# Set the path for the input files
path = "./input/"
simple.set_input("mhw", path + "grid_brasschaat.tif")
simple.set_input("mlw", path + "grid_brasschaat.tif")
simple.set_input("soil_code",path + "bodem_v2_ok_new.tif")

# Warning: CRS definitions are not equal!

simple.run(full_model=False, strict_checks=False)

# error: different grid size or orientation
 ---------------------------------------------------------------------------
SpatialContextError                       Traceback (most recent call last)
<ipython-input-5-03315d4400d0> in <module>()
----> 1 simple.run(full_model=False, strict_checks=False) # an example with a warning for the mean gw levels

~\AppData\Local\Continuum\anaconda3\envs\niche\lib\site-packages\niche_vlaanderen\niche.py in run(self, full_model, deviation, abiotic, strict_checks)
    467                     "Error, different obliged keys are missing")
    468
--> 469         self._check_input_files(full_model)
    470
    471         if full_model and not abiotic:

~\AppData\Local\Continuum\anaconda3\envs\niche\lib\site-packages\niche_vlaanderen\niche.py in _check_input_files(self, full_model)
    355             nodata = dst.nodatavals[0]
    356
--> 357             window = self._context.get_read_window(SpatialContext(dst))
    358             band = dst.read(1, window=window)
    359

~\AppData\Local\Continuum\anaconda3\envs\niche\lib\site-packages\niche_vlaanderen\spatial_context.py in get_read_window(self, new_sc)
    202         if not self.check_overlap(new_sc):
    203             raise SpatialContextError(
--> 204                 "Error: No overlap between both Spatial contexts."
    205             )
    206

SpatialContextError: Error: No overlap between both Spatial contexts.

When checking both files on their metadata using GDAL:

> gdalinfo bodem_v2_ok_new.tif
Driver: GTiff/GeoTIFF
Files: bodem_v2_ok_new.tif
          bodem_v2_ok_new.tif.aux.xml
Size is 524, 439
Coordinate System is:
PROJCS["Belge 1972 / Belgian Lambert 72",
    GEOGCS["Belge 1972",
        DATUM["Reseau_National_Belge_1972",
            SPHEROID["International 1924",6378388,297,
                AUTHORITY["EPSG","7022"]],
            TOWGS84[-106.8686,52.2978,-103.7239,0.3366,-0.457,1.8422,-1.2747],
            AUTHORITY["EPSG","6313"]],
        PRIMEM["Greenwich",0,
            AUTHORITY["EPSG","8901"]],
        UNIT["degree",0.0174532925199433,
            AUTHORITY["EPSG","9122"]],
        AUTHORITY["EPSG","4313"]],
    PROJECTION["Lambert_Conformal_Conic_2SP"],
    PARAMETER["standard_parallel_1",51.16666723333333],
    PARAMETER["standard_parallel_2",49.8333339],
    PARAMETER["latitude_of_origin",90],
    PARAMETER["central_meridian",4.367486666666666],
    PARAMETER["false_easting",150000.013],
    PARAMETER["false_northing",5400088.438],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]],
    AXIS["X",EAST],
    AXIS["Y",NORTH],
    AUTHORITY["EPSG","31370"]]
Origin =<PHONE_NUMBER>00000000233,227200.000000000000000)
Pixel Size = (24.984263396946552,-24.954441913439634)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (  153884.207,  227200.000) (  4d25'23.67"E, 51d21'18.31"N)
Lower Left  (  153884.207,  216245.000) (  4d25'23.24"E, 51d15'23.85"N)
Upper Right (  166975.961,  227200.000) (  4d36'40.17"E, 51d21'17.46"N)
Lower Right (  166975.961,  216245.000) (  4d36'38.32"E, 51d15'23.00"N)
Center      (  160430.084,  221722.500) (  4d31' 1.35"E, 51d18'20.79"N)
Band 1 Block=524x3 Type=Float32, ColorInterp=Gray
  Min=2.000 Max=15.000
  Minimum=2.000, Maximum=15.000, Mean=10.842, StdDev=1.505
  NoData Value=-3.4028234663852886e+38
  Metadata:
    STATISTICS_MAXIMUM=15
    STATISTICS_MEAN=10.841776939262
    STATISTICS_MINIMUM=2
    STATISTICS_STDDEV=1.5048828165499
    STATISTICS_VALID_PERCENT=100

> gdalinfo grid_brasschaat.tif
Driver: GTiff/GeoTIFF
Files: grid_brasschaat.tif
       grid_brasschaat.tif.aux.xml
Size is 524, 439
Coordinate System is:
PROJCS["Belge_1972_Belgian_Lambert_72",
    GEOGCS["GCS_Belge 1972",
        DATUM["Reseau_National_Belge_1972",
            SPHEROID["International_1924",6378388,297,
                AUTHORITY["EPSG","7022"]],
            AUTHORITY["EPSG","6313"]],
        PRIMEM["Greenwich",0],
        UNIT["degree",0.0174532925199433]],
    PROJECTION["Lambert_Conformal_Conic_2SP"],
    PARAMETER["standard_parallel_1",51.16666723333333],
    PARAMETER["standard_parallel_2",49.8333339],
    PARAMETER["latitude_of_origin",90],
    PARAMETER["central_meridian",4.367486666666666],
    PARAMETER["false_easting",150000.013],
    PARAMETER["false_northing",5400088.438],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]]]
Origin =<PHONE_NUMBER>00000000233,227200.000000000000000)
Pixel Size = (24.984263396938331,-24.954441913432674)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (  153884.207,  227200.000) (  4d25'23.67"E, 51d21'18.31"N)
Lower Left  (  153884.207,  216245.000) (  4d25'23.24"E, 51d15'23.85"N)
Upper Right (  166975.961,  227200.000) (  4d36'40.17"E, 51d21'17.46"N)
Lower Right (  166975.961,  216245.000) (  4d36'38.32"E, 51d15'23.00"N)
Center      (  160430.084,  221722.500) (  4d31' 1.35"E, 51d18'20.79"N)
Band 1 Block=524x1 Type=Float64, ColorInterp=Gray
  Min=0.000 Max=100.000
  Minimum=0.000, Maximum=100.000, Mean=49.957, StdDev=29.086
  Metadata:
    STATISTICS_MAXIMUM=100
    STATISTICS_MEAN=49.956815454972
    STATISTICS_MINIMUM=0
    STATISTICS_STDDEV=29.086472440779

There is indeed a small difference in pixel size in between both rasters. I would try to use one of the grids as the reference/mask and match the other values with it using any GIS tooling?
I do not think it would be a good idea to be less strict on the spatial extent matching of the input files.

After trying the following adaptation to both rasters using the gdal command line command gdalwarp:
> gdalwarp -tr 25 -25 -tap -t_srs epsg:31370 grid_brasschaat.tif brasschaat.tif
> gdalwarp -tr 25 -25 -tap -t_srs epsg:31370 bodem_v2_ok_new.tif bodem.tif

I can run the following code:
simple = nv.Niche()
simple.set_input("mhw", path + "brasschaat.tif")
simple.set_input("mlw", path + "brasschaat.tif")
simple.set_input("soil_code",path + "bodem.tif")
simple.run(full_model=False, strict_checks=False)

wihout errors on wrong crs or alignments.

Ok, many thanks for checking!
I (unfortunately) need to stick to the strange pixel sizes I got from the groundwater modellers, but indeed if  I resample everything, it works.
I thought there was a tolerance for shifts smaller than 1 cm (or what does this mean exactly?).
I do not consider a shift <0.0000001 mm as problematic, but I guess it is not that easy to implement a tolerance for every little source of errors ...
May I suggest to adapt the warning for set_input to "Warning: CRS definitions are not equal or different grid size or orientation are used!" instead of "Warning: CRS definitions are not equal or different "?

@cecileherr
It was indeed the intention to ignore shifts <1cm.  I remember we tested this before.
The comment definitely needs an update.
I will try to figure out why it is not working in this case.

@johanvdw make sure to provide the required unit tests as well.

@cecileherr
The tolerance of 0.01m was not applied everywhere.  I made a small adjustment and I think your grid should work now.
You can test by installing the latest version from a conda prompt (before starting python):
pip install git+https://github.com/inbo/niche_vlaanderen.git --upgrade
[ if git is not installed you will get an error, in that case you should first do conda install git ]
If I'm at INBO I will try to adjust the documentation and add a test. We can then see if we can do an updated release or if we include some other small changes.
Strictly speaking we should perhaps also reconsider the absolute 0.01m rule. If we have a huge grid and a small offset in pixel size this will sum up throughout the grid. It might be better to use  1% of the cell size (cumulative over the grid) as cutoff value. Given the typical study areas we currently have this is more a hypothetical problem.

Many thanks for looking at this issue!.
Unfortunately I get an error when I try to install the latest version from github:
Collecting rasterio (from niche-vlaanderen==1.0)   Downloading https://files.pythonhosted.org/packages/ce/90/8af39cdfed9a40bd5980 1f101f74eab5f1562d3557806ddfa2ed86d4be0b/rasterio-1.0.22.tar.gz (1.9MB)     100% |¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦| 1.9MB 451kB/s     Complete output from command python setup.py egg_info:     INFO:root:Building on Windows requires extra options to setup.py to locate n eeded GDAL files. More information is available in the README.     ERROR: A GDAL API version must be specified. Provide a path to gdal-config u sing a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variab le.     ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in C:\Users\cecile_h err\AppData\Local\Temp\pip-build-a_bsw4vi\rasterio\

@cecileherr
Ok, my error it seems. You can use:
pip install git+https://github.com/inbo/niche_vlaanderen.git (without the upgrade)

@johanvdw
OK, this new version works with my slightly shifted (< 0.0001 mm) rasters. I get a CRS warning when I load the input rasters (as expected), but I can run the model without errors.
Thanks again :-)


Add Input Field for Custom Font Value Alongside Slider

Describe the feature
Currently, the font size value is adjusted solely using a drag slider. This method may not provide the best user experience, as users might prefer a more precise way to set the font size rather than relying on a slider alone.

To Reproduce
Steps to reproduce the behavior:

Go to the font adjustment section of the application.
Attempt to change the font size using the drag slider.
Notice the difficulty in achieving a specific font size without the ability to enter a precise value.

Expected behavior
It would be beneficial to have an input field alongside the slider. This allows users to enter a custom font size directly, providing a more flexible and user-friendly experience for adjusting font values.

Screenshots

Additional context
Implementing an input field alongside the slider will enhance usability, allowing users to quickly and accurately set their desired font size without the limitations of the slider. This change could improve the overall user experience significantly.

Were you using it on mobile device? It's just kinda confusing to me since it seems to me that with the current range it would be easy enough for me to select any given value with the slider.

yes, but from the point of user experience the slider doesn't make any sense if you can just take input of that particular range, it's just making it hard to slide to that number appropriate and then release it.

I see, I can make this change later.

interesting , i can fix that issue related to frontend , would you like to assign it to me


Bug:

Bug Type
Function
Bugged function
It responds as false even though there is a var here's the code

bot.command({
  name:"varE",
  code:`$varExists[prefix]`
})

bot.command({
  name:"varE",
  code:`$varExists[$message]`
})

bot.command({
  name:"varE",
  code:`$varExists`
})

I used all of these three codes, what's the write code?

Version of aoi.js
v5.5.5 (Default)
Version of Node.js
v16.6.0
Excepted Output
No response
Relevant log output
No response
Code of Conduct

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

I suggest you use my package: https://www.npmjs.com/package/more-aoi.js
It have this function, and it working with any type of variable.
If you want to you can see how I did it by looking here: https://github.com/zerealone/more-aoi.js/blob/master/lib.js
~ Amit

this function doesn't seems to exist in src code

aoi.js has a new function. We can add our own codes their Ayaka. AYAKA. AYAKA.
I do not need this btw fixed it already lol LLLLLLLL


Cant find any devices while flutter blue scanning

I try to find the devices with de oficial example:
https://github.com/pauldemarco/flutter_blue/tree/master/example
I have several devices (BLE) that should be listed, but they NEVER appear. What am i doing wrong? Please, help me!
All the devices are (BLE).

Have you used another app (ex: LightBlue) to verify that your device can discover these devices?

Have you used another app (ex: LightBlue) to verify that your device can discover these devices?

Have you used another app (ex: LightBlue) to verify that your device can discover these devices?

@gumbypp yes! Not appear to, why flutter_blue only appear BLE devices? I r

I have the same issue. I tried with LG G6 with the example code and it shows nothing. Same if I search for paired devices. My devices are listed on LightBlue and on app built on top of flutter_bluetooth_serial.
scanForDevices() {
print('list of paired devices');
flutterBlue.connectedDevices.asStream().listen((paired) {
  print('paired device: $paired');
});
setState(() {
  _isScanning = true;
});
scanSubscription =
    flutterBlue.scan(timeout: Duration(seconds: 20)).listen((scanResult) {
  var device = scanResult.device;
  print('${device.name} found! rssi: ${scanResult.rssi}');
}, onDone: _stopScan);
scanSubscription.cancel();

}
_logs:
I/flutter (21110): list of paired devices D/BluetoothManager(21110): getConnectedDevices D/FlutterBluePlugin(21110): mGattServers size: 0 D/BluetoothAdapter(21110): isLeEnabled(): ON D/BluetoothLeScanner(21110): onScannerRegistered() - status=0 scannerId=5 mScannerId=0 I/flutter (21110): paired device: []

I also encountered the same situation, but I can search for the device after I open the location of the phone.

Same thing here, just one bluetooth device gets detected although plenty are on in detectable mode. Tried all available ScanModes but no progress  @RuijinYao by opening the location.. do you mean giving your app the location permission?

Same problem

Me too, and I try agin by other bluetooth packages. but no one can work normally.

HI Team ,
 I am also facing the same problem. My use case is I am trying to connect bluetooth scanner device (Socket 7XI[68481F]) but can’t find it with this plugin, though other devices are visible . I also tried the other flutter bluetooth serial plugin but in my case I’ll be needing this functionality in my IOS app .  Does any one has got any work around for this , it will be much appreciate . Thanks in advance .

On Android devices, turn on GPS, and use all the functions in Flutter-blue. If not, phone can discover the device but cannot connect. Maybe you can turn on GPS. I haven't compiled the IOS program, maybe I can try it in a few days.
I am a student studying automation, I don’t know much about android, but I have gained a lot of experience in the process of learning flutter. I am happy to share with you, I hope to keep in touch.

李峦
掌上理工
联系我

------------------ 原始邮件 ------------------
发件人: "Kushal<EMAIL_ADDRESS>发送时间: 2020年2月22日(星期六) 晚上6:37
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [pauldemarco/flutter_blue] Cant find any devices while flutter blue scanning (#336)
HI Team ,
 I am also facing the same problem. My use case is I am trying to connect bluetooth scanner device (Socket 7XI[68481F]) but can’t find it with this plugin, though other devices are visible . I also tried the other flutter bluetooth serial plugin but in my case I’ll be needing this functionality in my IOS app .  Does any one has got any work around for this , it will be much appreciate . Thanks in advance .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

@Skalate thanks for reverting back , but unfortunately your solution didn't work for me . Have anyone got any solutions for this . Thanks in advance .

I don't know how to solve your problem, maybe you can try to contact the author of flutter-blue. Or use mixed development, it will take you some days to study the swift language.
李峦
掌上理工
联系我

------------------ 原始邮件 ------------------
发件人: "Kushal<EMAIL_ADDRESS>发送时间: 2020年2月26日(星期三) 下午4:55
收件人<EMAIL_ADDRESS>抄送: "李峦"<757122943<EMAIL_ADDRESS>主题: Re: [pauldemarco/flutter_blue] Cant find any devices while flutter blue scanning (#336)
@Skalate thanks for reverting back , but unfortunately your solution didn't work for me . Have anyone got any solutions for this . Thanks in advance .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi I also have the same problem with trying to connect my arduino bluetooth using this example code. Is there any solution for this problem?

@GreeceNg I have this problem. Some devices are not listed in this bluetooth plugin because they are different tecnologies. I had to change the plugin and now im using this: https://pub.dev/packages/blue_thermal_printer.

Same Issue
FlutterBluePlugin( 7582): mDevices size: 0

I have the same problem for me. I tried that 6 months ago with the same problem and I am surprised how little changed.
@pauldemarco Hi Paul, do you have any input in this problem.
@luissouza I need basic write and read functionality with BLE. Would the package u use work fort that? https://pub.dev/packages/blue_thermal_printer.
Any alternative packages which are better maintained would be highly appreciated. Any input?

I have the same problem for me. I tried that 6 months ago with the same problem and I am surprised how little changed.
@pauldemarco Hi Paul, do you have any input in this problem.
@luissouza I need basic write and read functionality with BLE. Would the package u use work fort that? Seems like this package works only for Android: https://pub.dev/packages/blue_thermal_printer.
Any alternative packages which are better maintained and work with ios would be highly appreciated. Any input?

That package didn't work for me either it, it doesn't connect

Hello, I checked some information and sorted out the following possible solutions.
1. Try programming with Object-c. Create a new empty directory and use 'flutter create -i objc my-flutter-app' to create a new project.
2. Use a lower version of the API. 'use_frameworks! platform :ios, '9.0''
If none of the above solutions can be solved, I highly recommend you to learn IOS development, Mixed development seems to be the only way
李峦
掌上理工
联系我

------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年3月25日(星期三) 上午6:37
收件人<EMAIL_ADDRESS>抄送: "李峦"<757122943<EMAIL_ADDRESS>主题: Re: [pauldemarco/flutter_blue] Cant find any devices while flutter blue scanning (#336)
I have the same problem for me. I tried that 6 months ago with the same problem and I am surprised how little changed.
@pauldemarco Hi Paul, do you have any input in this problem.
@luissouza I need basic write and read functionality with BLE. Would the package u use work fort that? Seems like this package works only for Android: https://pub.dev/packages/blue_thermal_printer.
Any alternative packages which are better maintained and work with ios would be highly appreciated. Any input?
That package didn't work for me either it, it doesn't connect
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please try to use this branch. Defects got fixed on this branch which might fix ur problems. Keep track of this #145 to see if a new package get created to get better support.
use this in your yaml for now:
flutter_blue:
git:
url: https://github.com/boskokg/flutter_blue.git
ref: 0.7.1

I try to find the devices with de oficial example:
https://github.com/pauldemarco/flutter_blue/tree/master/example
I have several devices (BLE) that should be listed, but they NEVER appear. What am i doing wrong? Please, help me!
All the devices are (BLE).

I also have the same issue. I don't know whats wrong

Same here. I should be able to see a lot of devices around me, but all i can see is my connected SPEN (Galaxy Note10), which i actually can't see when i open my phones bluetooth settings and scan for devices...

I have the same problem for me. I tried that 6 months ago with the same problem and I am surprised how little changed.
@pauldemarco Hi Paul, do you have any input in this problem.
@luissouza I need basic write and read functionality with BLE. Would the package u use work fort that? Seems like this package works only for Android: https://pub.dev/packages/blue_thermal_printer.
Any alternative packages which are better maintained and work with ios would be highly appreciated. Any input?

Im using now esc_pos_bluetooth plugin.
This plugin (esc_pos_bluetooth) cant fin my device too.
I get this plugin example, and i change a bit, in the connection code, like this.
 printerManager.selectPrinter(PrinterBluetooth(
        flutterBluetoothBasic.BluetoothDevice.fromDocument(
            printerName, printerAddress, 0, true)));

Hope it helps!

@ride4sun
Im using now esc_pos_bluetooth plugin.
This plugin (esc_pos_bluetooth) cant fin my device too.
I get this plugin example, and i change a bit, in the connection code, like this.
 printerManager.selectPrinter(PrinterBluetooth(
        flutterBluetoothBasic.BluetoothDevice.fromDocument(printerName, printerAddress, 0,true)));

Hope it helps!

Hii
I'm working on social distancing app
I'm facing same issue couldn't get any mobile devices in scanresult

@javiervalero31, i think, is not return anything because all the devices that you are looking for are not BLE, and this plugin just show BLE devices.. Look in play store for BLE app, this app shows to you if your device is BLE (Bluetooh low energy).

I have the same problem before and all I did is turning on the location/ GPS and try to re-scan again and it works for my ESP32 BLE!

I'm facing same problem too.
It works on many device to connect my thermal printer.  e.g. iphone, ipad, redmi, huewei p30.
But it's not working for my samsung note10lite and note10+.
Any idea?

@nadjwarazali Thank you it worked

Had the same problem with https://github.com/lupyuen/flutter-blue-sample example (based on pauldemarco's) and as others mentioned, turing on GPS (as well as bluetooth) solved this problem. I find it odd that you need location ON in order to find bluetooth devices. Anyone knows why?

Turn on GPS it will work fine...!!!

I was experiencing this issue when testing on a device with the --release flag.
Apparently there is an issue with the minification of flutter blue. There are two ways of working around the problem, as listed in this issue: https://github.com/pauldemarco/flutter_blue/issues/662
In android/app/build.gradle you can disable minifaction:
android {
    ...
    buildTypes {
        release {
            signingConfig signingConfigs.debug
            shrinkResources false
            minifyEnabled false
        }
    }

OR you can create a proguard rule that prevents flutter_blue from minimizing:
In android/app/build.gradle:
android {
    ...
    buildTypes {
        release {
            signingConfig signingConfigs.debug
            minifyEnabled true
            useProguard true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

and create a file at android/app/proguard-rules.pro with the following:
-keep class com.pauldemarco.flutter_blue.** { *; }

I was experiencing this issue when testing on a device with the --release flag.
Apparently there is an issue with the minification of flutter blue. There are two ways of working around the problem, as listed in this issue: https://github.com/pauldemarco/flutter_blue/issues/662
In android/app/build.gradle you can disable minifaction:
android {
    ...
    buildTypes {
        release {
            signingConfig signingConfigs.debug
            shrinkResources false
            minifyEnabled false
        }
    }

OR you can create a proguard rule that prevents flutter_blue from minimizing:
In android/app/build.gradle:
android {
    ...
    buildTypes {
        release {
            signingConfig signingConfigs.debug
            minifyEnabled true
            useProguard true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

and create a file at android/app/proguard-rules.pro with the following:
-keep class com.pauldemarco.flutter_blue.** { *; }

Has anybody tried to connect to an epson TM-T88VI ? It just doesn't show up in the list. Tried to enable GPS and all but still can't detect it (the android/ios app provided by Epson does detect it though...)

Hi all, I'm also having this issue, the scan only returns two devices named 'gDevice-beacon' which are not connectable. I did make sure that the ESP32 was discovered on lightblue, and it shows up. I also enabled location and bluetooth scanning on the app. I also tried disabling minimizing with no luck. I'm just wondering if anyone else has something I could try?

Hi all, I'm also having this issue, the scan only returns two devices named 'gDevice-beacon' which are not connectable. I did make sure that the ESP32 was discovered on lightblue, and it shows up. I also enabled location and bluetooth scanning on the app. I also tried disabling minimizing with no luck. I'm just wondering if anyone else has something I could try?

Are you running your app on your emulator ? If yes, then it's to be expected, since the emulators are not supporting the bluetooth yet (cmiiw). I faced the same issue, but when I try to run it on my android phone, it works just fine.

Hey @AndyTanuC, you're right. I was using an emulator, but decided to buy a cheap android tablet and its working great now. Thanks for your help!

As anywone used this package after change o null safety?
i Have same issue
I tried so many types ,turn on location ,mifinify enablaed false,shrinkresourses false, but no reaction
D/FlutterBluePlugin(20287): mDevices size: 0
@pauldemarco  plase help. I tried all points which have there

at the moment i am using Galaxy s21 and Galaxy fold for test

i had the same problem and it was in the permissions

@DyaaElabasiry how did you resolve it? pls help

Any updates on this? Why this packages is so bad maitained?

hi there i tried all the above added proguard,disabled shrinkResources false
minifyEnabled false and advices from others too , but the scan results dont show the devices which are active

hi there i tried all the above added proguard,disabled shrinkResources false minifyEnabled false and advices from others too , but the scan results dont show the devices which are active

Sto avendo lo stesso problema ma vedo che il dispositivo bluetooth non me lo trovano nemmeno altre app, ma se dal mio smartphone faccio una normale scansione lo trova

Got the same problem, turning in GPS solved my problem.
I also got different bugs on different android versions, all solved by the GPS-thing.
Does anyone have an idea why flutter_blue does correlate with the GPS settings? It has something to do with permissionshandling..

Is this enough to grant permission?

...
I have noticed that several third party apps also cannot find the device

Make sure that device Gps location is enable, if the Gps is disable then you won't be able to scan the device.

Looks like enabling GPS location for our app worked! We did not need to enable GPS when we built from a windows machine...
it only happened when we started building and debugging on macOS. Very weird, I guess when building on mac it really cares about permissions.
Anyways thanks guys

in my case, I added below permission then it worked
I found this from changelog(https://pub.dev/packages/flutter_blue_plus/changelog#140)
<uses-permission android:name="android.permission.BLUETOOTH_SCAN"
  android:usesPermissionFlags="neverForLocation" />

oh my...
in release mode built apk , it still not work (no scan results... )
only debug build apk work.
how to solve this?


Validate the length of fields in Offsite Links

Rather than letting the database raise an error (now that we have a MySQL
version which doesn't silently truncate), let's validate it in the model and
show the user a helpful validation message, not a 5xx error page.
Example of this happening in production: https://errbit.publishing.service.gov.uk/apps/53020d6c0da11585f10000e7/problems/5669211065786305bb340300
Here are the relevant lines from schema.rb

:ship:

:+1: to make the seal happy

SDD (seal-driven development)

Weirdly the branch build passed but it failed when merged to master. The old builds have been purged so we can't see what happened. Fix here: https://github.com/alphagov/whitehall/pull/2420


Client sends textDocument/didOpen for QuickDiffProvider original source

We use a SCM extension (unfortunately not public) that provides a QuickDiffProvider that looks like this:
provideOriginalResource(uri: vscode.Uri, token: vscode.CancellationToken):  vscode.ProviderResult<vscode.Uri> {
  return uri.with({
    scheme: 'piper',
    authority: 'baseline',
    path: '/' + uri.fsPath,
  });
}

The intent is that these URIs are only used by VSCode to provide the baseline content of a file in source control.
When we open a file, our LSP server (clangd) receives textDocument/didOpen events for these piper:// URIs!
This results in:

confusion because we can't work out how such files should be interpreted/build (in general this requires traversing the source tree on the filesystem)
unneccesary work if we do manage to work out how to build these files - e.g. we need to run a second copy of our build system the baseline vs current version have different build configurations in general

From our point of view, it'd be much preferable if Quickdiff original resources were never sent to LSP and treated as textual only (or at least LSP flagged them somehow so our server could choose to ignore them).

@sam-mccall I've heard of such problems with URIs in the past. You may be interested in Microsoft/vscode#21526 and Microsoft/vscode#20859.

This can actually be control by the extension starting the language server. The LSP client module allows to provide document selectors. So the clangd code that creates the LSP client would say that onle 'file' and 'untitled' schemas should be synced.
There is nothing that the LSP can do in general here besides giving clients control over this. There might be a sever being interesting in something different than 'file' and 'untitled' so I can not filter them by default.
I close the issue since this is outside the LSP scope. If VS Code itself decided to filter schemas or to provide and opt in support the LSP client will profit from it automatically.

@dbaeumer The URI scheme is a red herring, I think (sorry I explained poorly).
We noticed the problem because of the weird URIs, but the same problems would exist if the SCM plugin returned file:// (and in fact for our Piper plugin this would be a reasonable choice - I guess there are SCM plugins that do this).
I wasn't sure which project this belongs to, but it seems like VSCode could communicate the semantic distinction between opening for view and fetching for diff, and the LSP client should only examine the former...
For this particular combination of plugins, we do have a workaround though, thanks!

VS Code has an item so that the LSP client could determine whether a file was opened for content reading only (as a text buffer) or is opened in the editor. But it doesn't exist right now so all the LSP client can do is to treat reads as open.


Dark mode for MDN

Request type

[x] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[ ] Correction or update

why there is no dark mode?
Details

Thanks for filing. This request comes up from time to time (see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1427452) but unless something has changed, we're not planning to support a dark mode in MDN.
Pinging @atopal anyway just to confirm that this is still the position (and to register this request).

Yes, confirming that we don't have plans for a dark mode at this time.


SCons: Address minor show_progress issues

Followup to #98154

Realized a minor regression introduced by the above PR causing node count to not be tracked whatsoever if not displaying a progress bar. Additionally, progress_finish as an SCons action is unnecessary & doesn't catch all cases; it's now handled via atexit like the cache cleaning

LGTM

Is it about a fact that [Initial build] disappeared recently?

Needs rebase.

Thanks!


Using lint- and compileWithContext is perfectly fine

Hence, I removed the comment.

Don't we want to use compile when possible?

Don't we want to use compile when possible?

That's not possible. If top level are declared with visibility modifiers the Kotlin script engine cannot compile it.


Decide how to handle proper motion

Proper motions are currently not handled properly in DM. See:
https://jira.lsstcorp.org/browse/DM-8828
So, I will check on the status of this with the DM team, but if DM does not handle proper motion by the time of DC2 we should consider turning it off. For imSim this would mean setting the proper motion components to zero in the instance catalog.  For PhoSim I believe we would pass the ICRS coordinates into the instance catalog instead of the modified ones when we do the CatSim lookup.  @danielsf and @johnrpeterson can comment.

I agree that if DM doesn't handle proper motion we should deactivate proper motion. That will make our life easier at the time of matching input and output catalogs.

@johnrpeterson Can you comment on the above (how we would turn off proper motion in PhoSim instance catalogs)?  Thanks.

Hi @johnrpeterson;
It is looking like handling  proper motion is not something that is on the DM near term roadmap.  Since we think this caused 20mas astrometric errors for us in DC1 we want to understand if we could turn proper motion off so we can decide what to do.
Is this possible in PhoSim, if so, what would the procedure be to make the instance catalogs?
Thanks.

well this is really at the catalog level.   proper motion is either handled by moving the ra/dec at the appropriate time of the observations.  the other case is using the movingpoint object which is normally used for high proper motion objects that move significantly in seconds (e.g. asteroids/comets).  but for that you would just set it to 0.
is that what you are asking?
john
On Nov 6, 2017, at 9:51 PM, Chris Walter <notifications<EMAIL_ADDRESS>wrote:
Hi @johnrpetersonhttps://secure-web.cisco.com/1D2OcuP_lr3M5jPLhTQyVxnL-oF2mt4TEBE3WODtXlXgr7-EhgEZz76qonawkpa2vhKCG9hH5IMba3KgDPKwFBS19vzxOqX_H0zjE_eaoIkGHo5PINmNXmPwnj0R1B4PptvDgx5boVDQxDEzWrTRT_Qj9RdxOFPkXkG3frQ_027GpD6Tg68zdYi3BMgfPA1RE14l2xDCTLbg-bX7WGJwqn75F8861-pI2jEf32tYh8nP9d9vM_p8Eq7R9PVWsgV-mWcRh6RtjEqEBdog4zeIY7LtWkravLk5XAx9V3Tm3JqRVsMzeV_WrhSiw0dMU4-53KyVX12qHl0dRguxQg49PWxklmxbItl_VSGTe8dGQI6E/https%3A%2F%2Fgithub.com%2Fjohnrpeterson;
It is looking like handling proper motion is not something that is on the DM near term roadmap. Since we think this caused 20mas astrometric errors for us in DC1 we want to understand if we could turn proper motion off so we can decide what to do.
Is this possible in PhoSim, if so, what would the procedure be to make the instance catalogs?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1DY5TNhs8o4Fv47MQxvtwyrfhlFJN4bjBPDdJZ5RPXjsFNX1TPMdU8-WXgo1kyFyljMuBtJWqIIIsYZGm7wu5Nq4JU-MX2W59NZIXDLfC8IGzdAWG-IK8ru42K6Dww8yTIU32JQBEJvL4tUxqDppPagyifo-mh4JVQLrUMlgPa8LOS70BkOPEhL3EiXKffQ87EdJmE4otypdG_l7bDHKFthf7SPMP3tUT5KnBjteQdbCMeDX91rF3-j-3YsgtTQobk2rEP5B8hGVkWNmvyCUyju6oUOa2sOte5nNES4WoNBQmV2GF3XTQbhFwJuGTtayvVH7htloTyt4L32heCA-EHGkQ2_wSJAMcykxJwfluEzk/https%3A%2F%2Fgithub.com%2FLSSTDESC%2FDC2_Repo%2Fissues%2F29%23issuecomment-342359298, or mute the threadhttps://secure-web.cisco.com/19mhL9lsvTQBpe-gcbR4JAWe9SpAdPiq0A5GaFXMKhrQSknHn_S0QjVSPpgFfGhPYCeX7Lkv49ZrsgzYs6EZADa0EUlb3wI9Asihy6UPaWGmEGzJw_3XB1Lier2icLcTLRtzSO2EeYOU3YpVWFhUE5c0cjmuRZbwnB2g61HyDcSQK6iyipa6lCfkLOjkK3I7NQDgfQdE3Bzlxdg-AGz3Av0qSCDQo53_fLpbyhPe6bMDXtuY8ZgN5qQDGsngNDXcdWfj1rj59AKJS8ccO5juo6BTYXw-KMWjv4nsYxAxEskpQ4cF_BaQ6SEIWjOq_HXBWW5Z1FbcMOYXVI8Hi-BBVtZUj0_nV5Avb3UCI-SFhYVw/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJbT8u0m7Yu1_kLy4M46XHO_r80MJlfzks5sz8WUgaJpZM4QL2Xm.

We can turn proper motion off in the PhoSim catalogs.  However, it is not as simple as "passing in the ICRS coordinates," since that would mean ignoring the precession, nutation, and other motions of the Earth.  I do not think we talking about removing those, are we?

We can turn proper motion off in the PhoSim catalogs. However, it is not as simple as "passing in the ICRS coordinates," since that would mean ignoring the precession, nutation, and other motions of the Earth. I do not think we talking about removing those, are we?

No.. I don't think so. So, we would need to modify the program that is preparing the instance catalogs for PhoSim and have it not apply any proper motion corrections to the RA and Dec but leave all other modifications to the ICRS coordinates in?

Yes.  We have to replace this method
https://github.com/lsst/sims_catUtils/blob/master/python/lsst/sims/catUtils/mixins/AstrometryMixin.py#L151
with onethat sets pr, pd, and rv to zero.

(are we also turning parallax off?)

FWIW, this is just a noise term in the astrometric residual, so I'm not convinced we should turn it off.
We don't measure parallax at the moment.  Though we could try using these data.

While its true that one can view uncorrected proper motion as a noise term in the astrometric residual, what took a lot of effort to understand in DC1 was the bias this leads to in astrometry, because of the non-zero average proper motion of the stars used to calibrate it.  If we turn off proper motion, it might turn out that parallax becomes the dominant residual, or we might already achieve the rough quality of astrometry that's expected.

It seems that this is not trivial and it might arise some other issues if we are not careful...
My main concern is to have a good spatial match between the input and output catalogs. I guess that if we save a truth table with the average positions of the objects over the period that they are going to be observed (so if we are observing certain object during X years get the mean position over those X years and use that as the truth) the match will be easier than for DC1. This creates some overhead at the time of generating the "truth" but it will make things easier at the time of the analysis, and it might be easier than turn off proper motion.
I don't know if this is the best solution and 20 mas is a tiny scale for most probes so I don't think this will be a big deal at the end of the day. @cwwalter @egawiser what do you think?

In terms of mission-critical items, I worry that this is causing ellipticity due to smearing of the co-added images, and that could affect Weak Lensing.  If I understand correctly, each visit gets astrometric calibration against known reference stars.  Because the instance catalog gives those reference stars proper motion but DM does not correct for this before fitting the astrometric solution, this causes a shift between the coordinate system defined by the average of the reference stars and the true coordinate system that the unmoving galaxies are in.  That should lead to a smearing of the galaxy photometry as time goes on - did you measure ellipticities in DC1?  Can we get WL to give us a requirement on the maximum tolerable level of ellipticity added by astrometric systematics for DC2?

Can we get WL to give us a requirement on the maximum tolerable level of ellipticity added by astrometric systematics for DC2?

I did some math on this a long time ago.  You can see the DESC WL presentation at: https://confluence.slac.stanford.edu/display/LSSTDESC/Minutes+for+telecon+on+October+6%2C+2014.
The estimate then was that 16 mas RMS misregistration error leads to a systematic comparable to the Y10 statistical power.  I'm not sure if there are more recent estimates than this or not...

Using the calculation in the HSC WL paper, the rough estimate of the shear calibration bias due to unrecognized astrometric errors is sqrt(sigma_ast^2 + sigma_psf^2)/sigma_psf - 1, where sigma_psf is the Gaussian sigma of the PSF (i.e., modeled as a Gaussian) and sigma_ast is your RMS astrometric error.  This assumes the PSF and galaxies are comparable in size.  My estimate is that if sigma_ast~0.02 arcsec and PSF FWHM~0.7 arcsec, the shear calibration bias is 0.002.  That's likely similar to our requirement for LSST Y10 (i.e., an astrometric error of that size would eat up our entire systematic error budget).  But DC2 is going to be much smaller area than LSST, so our requirement will be weaker by quite a bit, and this is probably OK for DC2.

@rmandelb What happens though if, as occurred in DC1, there is a 0.02 arcsec astrometric bias in the final co-added image?  I would naively think that bias doesn't affect WL at all, since it's common to all objects, but that smearing of the galaxies along a particular direction due to imperfect alignment of individual visits would still cause trouble.  We can estimate that smearing effect as the delta(average proper motion) between 2023 and 2033 (which I think is less than 0.02 arcsec because the proper motion is mostly caused by an offset between the epoch at which positions were measured and the mid-survey epoch of 2028).  If that's accurate, it seems that 0.02 arcsec is an upper limit on the actual rms astrometric error caused by not correcting for proper motion, reinforcing your welcome conclusion above.  But does that formula assume a truly random distribution of astrometric errors in two dimensions?  This effect is seemingly more coherent than that, which is what worries me.

It seems that this is not trivial and it might arise some other issues if we are not careful...

Could we get a clear answer on this point from @danielsf?  I still an unclear on whether this is easy or not.  In the inSim case is is easy, I'm less clear on PhoSim.

What happens though if, as occurred in DC1, there is a 0.02 arcsec astrometric bias in the final co-added image? I would naively think that bias doesn't affect WL at all, since it's common to all objects, but that smearing of the galaxies along a particular direction due to imperfect alignment of individual visits would still cause trouble. We can estimate that smearing effect as the delta(average proper motion) between 2023 and 2033 (which I think is less than 0.02 arcsec because the proper motion is mostly caused by an offset between the epoch at which positions were measured and the mid-survey epoch of 2028). If that's accurate, it seems that 0.02 arcsec is an upper limit on the actual rms astrometric error caused by not correcting for proper motion, reinforcing your welcome conclusion above. But does that formula assume a truly random distribution of astrometric errors in two dimensions? This effect is seemingly more coherent than that, which is what worries me.

Yes, if you take a look at LSSTDESC/SSim_DC1#43  you can see it is quite complicated.  We were basically not able to figure it out.  There is differential movement because of the MW model and the effect was to get a solution we just couldn't understand.  Galaxies and stars acted differently and we effectively just had to give up on understanding what was going on.  The algorithm needs to come up with some solution, and it's inputs aren't consistent.  So, it's just really hard to understand what it is going to be with all of the movement that is happening.
So, I think if we leave it on, we are just agreeing that we will live with that sort of source dependent shift (with fairly long tails).  So on top of ellipticity concerns (which haven't been studied in DC1 yet), that means we won't be able to see or understand any other astrometric residuals less than 20-50 mas.  Is that OK? I don't have a good sense of this.

@egawiser - The issue of how a bias (as opposed to stochastic offsets) impacts WL depends on things like how is the PSF modeled.  For example, let's say you model the per-exposure PSF, and then coadd the per-exposure PSFs to get the coaddPSF model.  But when you do that coaddition, you don't know about the coherent smearing along some preferred direction.  In that case, the coaddPSF model is wrong, and doesn't describe the fact that everything is smeared a bit along one direction.  If we were inferring the PSF from the coadds (which is a bad idea for many reasons) then that would actually fix this one problem (while creating many others) because we'd see that "hey, the stars all have this preferred ellipticity direction" and it would go into the PSF model.  But since we don't do that, our PSF model will be wrong and hence it will still cause a problem for WL.
The calculation in my earlier post was for a multiplicative shear calibration bias due the random astrometric offsets, which results in the coaddPSF model being too small compared to the real coadded PSF.  In the case of a coherent smearing direction, you'd actually get an additive shear bias correlating with that preferred smearing direction.  This could in principle be modeled and marginalized over.

Now in downtown Toyama... not sure about internet access today but I wanted to follow up a bit on above to clarify my concern on top of the  source dependent shifts we see:
Since we never were able to actually figure out what was going on with the astrometric solution that resulted from not attempting to correct for the motion, I'm afraid there could be other issues which we won't be able to see that could cause other PSF issues like discussed above etc.
We don't actually know how much of the 50mas is due to ignoring the proper motion.  So it could be smaller and there may be other issues; we can't tell.
On the other hand, if we include the motion, we can always re-run the stack later if the proper motion support is added to DM. This is a reconstruction not a simulation issue.

Chris, if our validation dataset is based on 1 year, then presumably the problems due to neglecting proper motion are less severe, and we can check the astrometry and see if any other major issues pop up?  I mean, if we find the same level of problem in 1 year of DC2 data than in 10 years of DC1 data, then that already says it's not proper motion that's the cause.  So could we potentially back-burner this question until we analyze the validation dataset?

That seems like a useful approach.  But let me again point out that if the bulk of the proper motion shift is coming from the difference between epoch ~2000 and epoch 2028, we should see almost as much of a shift in 1 year of DC2 data (but much less smearing effect on the PSF, which hasn't as far as I know been noted yet).   If instead the nominal coordinates are epoch 2017, the shift should be half as much.  @danielsf, can you remind us how the stellar positions are simulated for the instance catalogs?

So could we potentially back-burner this question until we analyze the validation dataset?

I think as long as we are willing to regenerate the dataset in anyway, yes this is fine.
But, I think I recall @fjaviersanchez saw this in the individual exposures and it was seen starting in year one. Can you remind us Javier?
I still haven't exactly nailed down the details of exactly what DM is doing with this but I think the fact that the ICRCs are J2000 and the first OpSim observation is Feb 2022 is also relevant.

(looks like my similar comment crossed with Eric)

@cwwalter yes, that’s correct. I saw this in the individual exposures. Also we have shape measurements on DC1 with hsm  (although there was no cosmic shear) so we should be able to test these things.

@cwwalter I am confident that we can remove the proper motion and just the proper motion in both ImSim and PhoSim.

Just to expand on @danielsf comments. The proper motions are stored in the
base catalog used for imsim and phosim (i.e. the database). It would be
straightforward to set them (and parallax if wanted) to 0 at the point the
database is queried and it should not change anything else in the
generation of the phosim inputs
On Thu, Nov 9, 2017 at 12:01 AM, danielsf<EMAIL_ADDRESS>wrote:

@cwwalter https://github.com/cwwalter I am confident that we can remove
the proper motion and just the proper motion in both ImSim and PhoSim.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/LSSTDESC/DC2_Repo/issues/29#issuecomment-343055778,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDow7J0hG6MKTRuObEgDuUvjUatx5EPks5s0pVWgaJpZM4QL2Xm
.

would be
straightforward to set them (and parallax if wanted) to 0 at the point the
database is queried and it should not change anything else in the
generation of the phosim inputs

Ah, good point!  I see.

With the merging of #45, we now have a flag to turn off proper motion when the catalog is made.
I would like to tentatively propose we do that for DC2 since fixing this is not high on the DM priority list see: https://jira.lsstcorp.org/browse/DM-8828 and (since even in year one of the OpSim run we are 22 years out from J2000) this is a noticeable effect that results in a solution we can't understand and is different for galaxies and stars.  This ~20mas shift could be hiding other problems we aren't aware of yet and can't check.
[arguing against this positions would be: we can live with this shift, perfect correction is not-realistic, HSC lives with it (although it is smaller there), and eventually we can always rerun DM when they implement the correction].
Let's decide on this in the next day or so.
@egawiser @rmandelb do you want to weigh in given your conversation above?

Others with opinions should of course also comment; but let's converge in ~2 days.  If no one objects by then, I will close this and ask Jim and Scott to turn the option on to zero out the motion.

@cwwalter So, ready to close this one? Thanks!

OK.  For DC2 we will turn off proper motion as implemented by Jim and Scott.
Jim, can you comment whether will also turn off parallax? I am still unclear on whether this is necessary. Then after that is documented we can close this issue.

Parallax will still be enabled, i.e., my changes should only affect proper motion.   PR #49 has proper motion disabled by default.  So I agree that we can close this issue.

OK closing.  But we should confirm that parallax is handled by DM and what the consequences are if it isn't.  @danielsf do you know?

I do not know

@ctslater Can you comment?

DM does not currently fit parallax, nor is it used for computing the positions of reference catalog stars.

Is that bad? :)

(quick interjection: it is one or two lines of code to turn parallax off the same way Jim turned proper motion off)

It is not good, but it shares the same root issue as proper motion, so they share a (mostly) common solution. I don't have an easy estimate for the magnitude of the error it would introduce.

Well... unlike the proper motion they are not going to keep getting bigger with time as we move away from the year 2000.  There is just going to be some offset which switches back and forth and so will average out over time.  I assume HSC sees this but it is probably also wiped out by PM. @TallJimbo do you have anything to add?

PM = Proper Motion, not Phil Marshall :)

Nice one!  Can anyone give a reason why we shouldn't turn off parallax along with proper motion, given that DM doesn't fit for it?

HSC sees very little of either proper motion or parallax, except perhaps between bands, as we tend to observe depth-first.

The only reason I can think of is that there is going to some residual left over from our corrections when we really take data.  We are basically getting rid of all of that.  So we would be putting in absolutely perfect correction.

What does this mean?

we tend to observe depth-first.
What does this mean?

We point at an area of sky on a particular night and basically go to full depth in that area, and then move on to another part of the sky.  So for any given area, the baseline for variability is quite small.
I suppose that only applies to the HSC Wide survey, though - we do return regularly to the Deep and UltraDeep fields.

Generically following up on my comment above:  If we perfectly correct for all motion, we are likely going to be doing better in our astrometric performance than in reality.  The reason I wonder if it is a good idea to be "perfect" is if there are in fact correlations with other metrics we want to check.
Will we be making a good test of those other factors if somehow having a perfect astrometric solution makes them too good also. I just have no good feel for this.

If this is in fact important, I guess one solution would be to turn everything off and then introduce jitter on the position of all stars drawn from our expected astrometric performance.

Proper motions are definitely a factor in how good the overall astrometry can be, though we're at least hoping that Gaia will basically solve that part of the problem.  I don't have any idea how much of a problem parallaxes would be in the absence of proper motions.
But proper motions aren't the only reason astrometry is hard, and I don't think you'll go too far into the realm of unrealistic perfection by disabling them if you make sure you have reasonable astrometric distortions due to the atmosphere and optics.

OK thanks Jim.  @jchiang87 and @danielsf Can you please also flip off the parallax in the code?

sure. will do.

@danielsf Any other motion components I should know about now instead of in March? :)

Where do things like nutation show up?

The various transformations applied to the ICRS coordinates are described here:
https://github.com/lsst/sims_catUtils/blob/master/python/lsst/sims/catUtils/mixins/AstrometryMixin.py#L147

Everything due to the motion of the Earth about its axis (precession, nutation, and aberration) is applied by palpy.  We can turn these off by taking palpy out of the loop, but we have to turn them all off.

There are complicated interplays between them and PhoSim right?  You have explained it to me before and I have understood it 5 times for 10 minutes each time.
I think we want refraction on in any case so I think we should leave these on unless people think they are big effects we should remove?

Yes.  It is complicated, but I think we could safely turn them off, if we had to.

Well, we want to turn DCR on so I don't think it would make sense to turn the overall refraction off.  It's looks like that is turned on this this code.
This will leave us with nutation which is on a 19 year cycle (a 9" circle) and the aberration which has a maximum angle of something like 20" over the year.  I assume the corrections would all be in the same DM code that isn't correcting for the other stuff.  I'm inclined to leave this on to get the refraction.
@egawiser and others do you agree?

For the record, PhoSim handles refraction itself.  We explicitly turn CatSim's refraction model off when generating PhoSim InstanceCatalogs
https://github.com/lsst/sims_catUtils/blob/master/python/lsst/sims/catUtils/exampleCatalogDefinitions/phoSimCatalogExamples.py#L363
And the CatSim refraction model is not wavelength dependent at this point.  I would not expect ImSim to produce realistic DCR, unless we do some work to add it.

And the CatSim refraction model is not wavelength dependent at this point. I would not expect ImSim to produce realistic DCR, unless we do some work to add it.

Yes, we will add it.

I'm not an astrometry expert by any means, but I would think that it's fine to simulate "motion of the Earth about its axis (precession, nutation, and aberration)" since those should affect all stars and galaxies similarly and be taken care of by astrometric calibration, which is already part of DM.  We already know from DC1 that this doesn't cause catastrophic problems, at least.

I'm not an astrometry expert by any means, but I would think that it's fine to simulate "motion of the Earth about its axis (precession, nutation, and aberration)" since those should affect all stars and galaxies similarly and be taken care of by astrometric calibration, which is already part of DM. We already know from DC1 that this doesn't cause catastrophic problems, at least.

Yes, good point. OK we leave these on.

For the record, PhoSim handles refraction itself.

This makes me realize there is possible an issue of using the same instance catalog for parameterized or ray-traced atmospheres in imSim.  I am going to leave this closed issue now and move that discussion to the imSim repo.
Thanks for everyone's contributions to this discussion!
Documenting a summary of the decisions for when we look at this in the future:
Due to proper and other motion of MW objects not being handled by DM at this time (see  https://jira.lsstcorp.org/browse/DM-8828) we have decided to turn off proper motion and parallax in the DC2 instance catalogs.
We know from our DC1 experience, that leaving them in introduces complicated and non-negligible astrometric biases.
We will leave in "motion of the Earth about its axis (precession, nutation, and aberration)" along with refraction when appropriate.  These should all affect stars and galaxies in the same way and includes some effects we want to simulate.


handle incorrect identities

Description
handle corrupt identities when listing for dashboard
Related Issues
https://github.com/threefoldtech/js-sdk/issues/1551
Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

Reproduced:

Create identity with explorer that doesn't exist
Try to make it default

Proposed solution

checked on the identity tid j.core.identity.devnet.tid
if it's -1 we don't show that identity at all (identity should be registered in some explorer to be shown)

Make a sanity check by requesting any of it's included explorer object stuff, list farms for example

@waleedhammam added a check on identity.tid which validates the user in explorer and skip it in dashboard if it fails

Codecov Report

Merging #1649 (ab99cd7) into development (da21270) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           development    #1649      +/-   ##
===============================================
- Coverage        32.14%   32.11%   -0.04%
===============================================
  Files              134      134
  Lines            12761    12910     +149
===============================================
+ Hits              4102     4146      +44
- Misses            8659     8764     +105

Impacted Files
Coverage Δ

jumpscale/packages/admin/actors/admin.py
29.90% <0.00%> (-1.41%)
:arrow_down:

jumpscale/tools/notificationsqueue/__init__.py
33.33% <0.00%> (-66.67%)
:arrow_down:

jumpscale/packages/admin/services/stellar.py
37.03% <0.00%> (-51.43%)
:arrow_down:

jumpscale/tools/servicemanager/servicemanager.py
62.88% <0.00%> (-20.45%)
:arrow_down:

...ackages/threebot_deployer/models/user_solutions.py
85.18% <0.00%> (-14.82%)
:arrow_down:

jumpscale/tools/notificationsqueue/queue.py
30.43% <0.00%> (-14.50%)
:arrow_down:

jumpscale/clients/stellar/__init__.py
29.82% <0.00%> (-7.02%)
:arrow_down:

jumpscale/clients/explorer/models.py
96.43% <0.00%> (-3.05%)
:arrow_down:

...ckages/threebot_deployer/chats/restart_threebot.py
39.13% <0.00%> (-1.17%)
:arrow_down:

jumpscale/packages/tfgrid_solutions/utils.py
16.17% <0.00%> (-1.02%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update da21270...ab99cd7. Read the comment docs.

> File "/home/waleed/js-sdk/jumpscale/packages/admin/actors/admin.py", line 52, in list_identities
    if identity.tid < 0:
       │        └ <property object at 0x7f457b988cc0>
       └ Identity(
           instance_name='tt',
           _tid=-1,
           words='coral light army gather adapt blossom school alcohol coral light army gat...

  File "/home/waleed/js-sdk/jumpscale/core/identity/__init__.py", line 122, in tid
    self.register()
    │    └ <function Identity.register at 0x7f457b7b6dc0>
    └ Identity(
        instance_name='tt',
        _tid=-1,
        words='coral light army gather adapt blossom school alcohol coral light army gat...

  File "/home/waleed/js-sdk/jumpscale/core/identity/__init__.py", line 135, in register
    users = resp.json()
            │    └ <function Response.json at 0x7f457e06f280>
            └ <Response [404]>

  File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/requests/models.py", line 898, in json
    return complexjson.loads(self.text, **kwargs)
           │           │     │    │       └ {}
           │           │     │    └ <property object at 0x7f457e06e270>
           │           │     └ <Response [404]>
           │           └ <function loads at 0x7f457efb70d0>
           └ <module 'json' from '/usr/lib/python3.8/json/__init__.py'>
  File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
           │                │      └ '404 page not found\n'
           │                └ <function JSONDecoder.decode at 0x7f457efa69d0>
           └ <json.decoder.JSONDecoder object at 0x7f457efa0f10>
  File "/usr/lib/python3.8/json/decoder.py", line 340, in decode
    raise JSONDecodeError("Extra data", s, end)
          │                             │  └ 4
          │                             └ '404 page not found\n'
          └ <class 'json.decoder.JSONDecodeError'>

json.decoder.JSONDecodeError: Extra data: line 1 column 5 (char 4)
2020-12-09 10:33:52.801 | ERROR    | jumpscale.servers.gedis.server:_execute:231 - error while executing <bound method Admin.list_identities of <admin.Admin object at 0x7f457aedda00>>
Traceback (most recent call last):

  File "/home/waleed/js-sdk/jumpscale/packages/admin/actors/admin.py", line 52, in list_identities
    if identity.tid < 0:
       │        └ <property object at 0x7f457b988cc0>
       └ Identity(
           instance_name='tt',
           _tid=-1,
           words='coral light army gather adapt blossom school alcohol coral light army gat...

  File "/home/waleed/js-sdk/jumpscale/core/identity/__init__.py", line 122, in tid
    self.register()
    │    └ <function Identity.register at 0x7f457b7b6dc0>
    └ Identity(
        instance_name='tt',
        _tid=-1,
        words='coral light army gather adapt blossom school alcohol coral light army gat...

  File "/home/waleed/js-sdk/jumpscale/core/identity/__init__.py", line 135, in register
    users = resp.json()
            │    └ <function Response.json at 0x7f457e06f280>
            └ <Response [404]>

  File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/requests/models.py", line 898, in json
    return complexjson.loads(self.text, **kwargs)
           │           │     │    │       └ {}
           │           │     │    └ <property object at 0x7f457e06e270>
           │           │     └ <Response [404]>
           │           └ <function loads at 0x7f457efb70d0>
           └ <module 'json' from '/usr/lib/python3.8/json/__init__.py'>
  File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
    return _default_decoder.decode(s)
           │                │      └ '404 page not found\n'
           │                └ <function JSONDecoder.decode at 0x7f457efa69d0>
           └ <json.decoder.JSONDecoder object at 0x7f457efa0f10>
  File "/usr/lib/python3.8/json/decoder.py", line 340, in decode
    raise JSONDecodeError("Extra data", s, end)
          │                             │  └ 4
          │                             └ '404 page not found\n'
          └ <class 'json.decoder.JSONDecodeError'>

json.decoder.JSONDecodeError: Extra data: line 1 column 5 (char 4)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/gevent/baseserver.py", line 26, in _handle_and_close_when_done
    return handle(*args_tuple)
           │       └ (<gevent._socket3.socket object, fd=31, family=2, type=1, proto=0>, ('<IP_ADDRESS>', 37724))
           └ <bound method GedisServer._on_connection of GedisServer(
               instance_name='threebot',
               host='<IP_ADDRESS>',
               port=16000,
               enab...
  File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/jumpscale/servers/gedis/server.py", line 279, in _on_connection
    result = self._execute(method, args, kwargs)
    │        │    │        │       │     └ {}
    │        │    │        │       └ []
    │        │    │        └ <bound method Admin.list_identities of <admin.Admin object at 0x7f457aedda00>>
    │        │    └ <function GedisServer._execute at 0x7f457c72adc0>
    │        └ GedisServer(
    │            instance_name='threebot',
    │            host='<IP_ADDRESS>',
    │            port=16000,
    │            enable_system_actor=True,
    │            run_async=True,
    │            _a...
    └ {'error': "alert_raise() got an unexpected keyword argument 'appname'", 'error_type': 3}
> File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/jumpscale/servers/gedis/server.py", line 228, in _execute
    response["result"] = method(*args, **kwargs)
    │                    │       │       └ {}
    │                    │       └ []
    │                    └ <bound method Admin.list_identities of <admin.Admin object at 0x7f457aedda00>>
    └ {}
  File "/home/waleed/js-sdk/.venv/lib/python3.8/site-packages/jumpscale/servers/gedis/baseactor.py", line 25, in wrapper
    result = func(*bound.args, **bound.kwargs)
             │     │     │       │     └ <property object at 0x7f4580fd51d0>
             │     │     │       └ <BoundArguments (self=<admin.Admin object at 0x7f457aedda00>)>
             │     │     └ <property object at 0x7f4580fd5180>
             │     └ <BoundArguments (self=<admin.Admin object at 0x7f457aedda00>)>
             └ <function Admin.list_identities at 0x7f457aefe3a0>

  File "/home/waleed/js-sdk/jumpscale/packages/admin/actors/admin.py", line 60, in list_identities
    j.tools.alerthandler.alert_raise(
    │ └ <property object at 0x7f4580561b30>
    └ <jumpscale.loader.J object at 0x7f4580ace910>

TypeError: alert_raise() got an unexpected keyword argument 'appname'


Image not put in Firefox's cache ?

Hi,
Image on this webpage : https://humbkr.com/
is not put in cache by Firefox (74.0)
In dev tools, a new request is made to proxy every time I reload the page :

Seems OK on Chrome :

Thanks in advance for your support.

I see that the image is served from cache if you use the address bar to re-access the site, but is loaded again when you use f5 or control-r. If response headers had something like Cache-Control: immutable, then it'd probably work with reload buttons, but I don't know if it could cause problems elsewhere.

you're right.
I consider this is working properly, thanks.


ethphunk 9219 - transaction history

I placed a bid for 9219 for .5 and had to refresh the page before that bid showed up in the transaction history.  When I withdrew the bid, the same thing happened.  It only showed as being withdrawn after refreshing the page.

Chopper, I'm still getting accustomed to this github workflow. I was just coming here to type out this same issue re: transaction history not populating after I place a bid and the bid is successfully processed and I see that you have it marked as completed. Does that mean you've seemingly fixed the issue?  If so, I would say that is not the case because, again, it just happened.  It actually happened twice in a row.  -Skim

Chopper, I'm still getting accustomed to this github workflow. I was just coming here to type out this same issue re: transaction history not populating after I place a bid and the bid is successfully processed and I see that you have it marked as completed. Does that mean you've seemingly fixed the issue? If so, I would say that is not the case because, again, it just happened. It actually happened twice in a row. -Skim

No problem. I only closed it because it was a duplicate of a previous reported issue. You don't need to worry about that tho. Continue as you were!


weather full detail

Code looks great, nice use of components. I think the scrollbar replacement got missed though. You can spawn it out into a new ticket if needed, but it would make sense to implement it in the panel container so it applies to all of the different panels.
Please include stories.

Not sure about scrollbar replacement, I applied overflow-y: auto to the panel so it will come with scroll bar as the screenshot displayed.

The scrollbar in the figma is a CSS custom replacement. We would have to hide the browser scrollbar and show that in its place.
https://ishadeed.com/article/custom-scrollbars-css/

Ah! I got it! Thanks
I didn't notice the difference on mock up but here is the replacement:

Storybook added @sukhpalp


[INTERNAL] generateStandaloneAppBundle: Replace AbstractReader#filter with resourceFactory#createFilterReader

Another oversight. Follow up of https://github.com/SAP/ui5-builder/pull/850

Coverage increased (+0.002%) to 94.704% when pulling e6d9ba3e1105dd460e32464b9586daf25200a20b on generateStandaloneAppBundle-filter-reader into b7a507fbc34076f5bf95f92f058fd2c58d79a455 on main.


chore(deps): update concerto dependencies

Updates concerto dependencies to the latest versions

Changes

Mapped axios dependency to jest compatible transpiled file where jest is used for testing

Flags

Screenshots or Video

Related Issues

Issue #
Pull Request #

Author Checklist

[x] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
[ ] Vital features and changes captured in unit and/or integration tests
[x] Commits messages follow AP format
[ ] Extend the documentation, if necessary
[ ] Merging to main from fork:branchname

Current state:
One of the deep dependencies is relying on Axios, which is using ECMA module. Jest is refusing to transform that to CJS module. I am still playing with Jest and Babel configurations to make the transformation happen so that test can run.

Fixed the testing issue.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 6 (33.33%)  changed or added relevant lines in 2 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 69.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/markdown-template/lib/ModelVisitor.js
0
1
0.0%

packages/markdown-template/lib/templatemarkutil.js
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

packages/markdown-template/lib/errorutil.js
1
15.38%

packages/markdown-pdf/src/pdfmakeutil.js
1
72.5%

packages/markdown-template/lib/ModelVisitor.js
20
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2776

Relevant Lines:
3804

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 6 (33.33%)  changed or added relevant lines in 2 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 69.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/markdown-template/lib/ModelVisitor.js
0
1
0.0%

packages/markdown-template/lib/templatemarkutil.js
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

packages/markdown-template/lib/errorutil.js
1
15.38%

packages/markdown-pdf/src/pdfmakeutil.js
1
72.5%

packages/markdown-template/lib/ModelVisitor.js
20
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2776

Relevant Lines:
3804

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 6 (33.33%)  changed or added relevant lines in 2 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 69.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/markdown-template/lib/ModelVisitor.js
0
1
0.0%

packages/markdown-template/lib/templatemarkutil.js
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

packages/markdown-template/lib/errorutil.js
1
15.38%

packages/markdown-pdf/src/pdfmakeutil.js
1
72.5%

packages/markdown-template/lib/ModelVisitor.js
20
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2776

Relevant Lines:
3804

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 6 (33.33%)  changed or added relevant lines in 2 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.3%) to 69.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/markdown-template/lib/ModelVisitor.js
0
1
0.0%

packages/markdown-template/lib/templatemarkutil.js
2
5
40.0%

Files with Coverage Reduction
New Missed Lines
%

packages/markdown-template/lib/errorutil.js
1
15.38%

packages/markdown-pdf/src/pdfmakeutil.js
1
72.5%

packages/markdown-template/lib/ModelVisitor.js
20
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2776

Relevant Lines:
3804

💛  - Coveralls


Bump rake to 11.0.1 or higher

While I would've wanted a bit lower, I figured if people are upgrading
this gem they would be running on a somewhat up to date version of rake
already, and its only a development dependency.
Rake 11.0.0 was yanked, hence the 11.0.1.

@pcreux Let me know what you think about this version bump. Might be a bit steep, going from no version lock to one which is about a year old, but its only a development dependency IMO.

Hey there!
Dumb question: what problem does that solve? 🙂
On Fri, Apr 14, 2017, 02:18 Zeger-Jan van de Weg<EMAIL_ADDRESS>wrote:

@pcreux https://github.com/pcreux Let me know what you think about this
version bump. Might be a bit steep, going from no version lock to one which
is about a year old, but its only a development dependency IMO.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pcreux/rspec-set/pull/10#issuecomment-294098355, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACw82Xswu_T_c8FWNtJxjhtR4XJjL-aks5rvw-ugaJpZM4M8YeW
.

The pipeline failure in #9 https://travis-ci.org/pcreux/rspec-set/builds/219766590
Did I misunderstand the problem?

Ok, I see. That error is happening because rake 12 replaced last_comment with last_description. That's been fixed in RSpec 3.4.4 (https://github.com/rspec/rspec-core/issues/2210). Since rspec-set works with RSpec 3, I'd rather remove the version constraint on rspec.
spec.add_development_dependency "rspec" # , "~> 2.14.1"

Does that make sense?

Sorry I was so lazy while digging. My bad.
Will edit this MR soon and ping you :)
--
Zeger-Jan van de Weg
On 14 April 2017 at 20:21:30, Philippe Creux<EMAIL_ADDRESS>wrote:
Ok, I see. That error is happening because rake 12 replaced last_comment with last_description. That's been fixed in RSpec 3.4.4 (rspec/rspec-core#2210). Since rspec-set works with RSpec 3, I'd rather remove the version constraint on rspec.
spec.add_development_dependency "rspec" # , "~> 2.14.1"
Does that make sense?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Adding jscs (JavaScript Code Style) to the devDependencies

Feature request
Adding JavaScript Code Style to the development tools.
The HACKING.md describes the Code Style, and the idiomatic style is available in the package. I am using this Gist to get the e14n exceptions in the rules.
{
    "preset": "idiomatic",
    "validateIndentation": 4,
    "disallowTabs": true,
    "requireSpacesInsideParentheses": null,
    "disallowSpacesInsideParentheses": null,
    "requireSpacesInsideBrackets": null,
    "disallowSpacesInsideBrackets": true,
    "requireSpacesInsideObjectBrackets": null,
    "requireCamelCaseOrUpperCaseIdentifiers": null,
    "requireCurlyBraces": null,
    "maximumLineLength": {
        "value": 120,
        "tabSize": 4,
        "allExcept": ["urlComments", "regex"]
    },
    "requireSpaceBeforeBinaryOperators": [
        "=", "+=", "-=", "*=", "/=", "%=", "<<=", ">>=", ">>>=",
        "&=", "|=", "^=", "+=",

        "-", "*", "/", "%", "<<", ">>", ">>>", "&",
        "|", "^", "&&", "||", "===", "==", ">=",
        "<=", "<", ">", "!=", "!=="
    ],
    "requireSpaceAfterBinaryOperators": null
}

The idiomatic style uses the JQuery style.
Travel back the road to check if the rules are already defined. Dereference rule with null or just overwrite the rule with a different rule.

@profOnno done! The rules are fairly lax right now since I didn't want to mess with too much of the codebase. We can tighten them up even more at a later time.

@evanp I did my best to preserve the existing codebase style; if anything's wrong, just say so.


Interesting pipe decorator

https://www.npmjs.com/package/flowhttp

Error handling for stream has been managed using defered promise.


Can I use Detours on WinCE ?

And how ?

Have you tried building it with the WinCE SDK? Currently this targets Windows XP and only uses kernel32 APIs so I'd expect it to work without much trouble.

Have you tried building it with the WinCE SDK? Currently this targets Windows XP and only uses kernel32 APIs so I'd expect it to work without much trouble.

I have NOT .
Because there is NOT an sln that I can use to do this ,
I do NOT know how to use an WinCE SDK to build this into an detours.lib ,
Can u give me some kind of help ?

https://github.com/microsoft/Detours/blob/64ec135a509884aa60ac6c19b59564f1da9cb2fa/src/detours.h#L840
My WinCE SDK does NOT have this file,
Can this be disabled by some option ?

My WinCE SDK does NOT have this file,
Can this be disabled by some option ?

Does WinCE SDK include imagehelp.h? I don't have any experience using it, but it looks like there is support for downlevel compilers using the imaghlp.h header instead. Maybe that could also be used on WinCE?
//////////////////////////////////////////////////////////////////////////////
//
#if (_MSC_VER < 1299)
#include <imagehlp.h>
typedef IMAGEHLP_MODULE IMAGEHLP_MODULE64;
typedef PIMAGEHLP_MODULE PIMAGEHLP_MODULE64;
typedef IMAGEHLP_SYMBOL SYMBOL_INFO;
typedef PIMAGEHLP_SYMBOL PSYMBOL_INFO;

static inline
LONG InterlockedCompareExchange(_Inout_ LONG *ptr, _In_ LONG nval, _In_ LONG oval)
{
    return (LONG)::InterlockedCompareExchange((PVOID*)ptr, (PVOID)nval, (PVOID)oval);
}
#else
#pragma warning(push)
#pragma warning(disable:4091) // empty typedef
#include <dbghelp.h>
#pragma warning(pop)
#endif

I'm going to close this issue just because of the how long it's been sitting in active, feel free to re-open in case you have further questions.

My WinCE SDK does NOT have this file,
Can this be disabled by some option ?

I think the dbghelp.h API's are only needed to support DetourFindFunction, unless I missed something in the code. Looking at the API's available in windows CE it looks like it doesn't have support. If you don't need DetourFindFunction support then you might be able to rip it out and get the other pieces compiling and working.
I assume you are targeting a x86 / ARM 32 ISA, and not MIPS / PowerPC / SuperH (not support)?
It looks like Windows CE is a derivative of NT, so it appears to have all the critical API's that detours depends on, so it doesn't seem out of the real of possibility that it might work without too much effort once you get it building.

without DetourFindFunction,
how to fint the address of the function ?

You can use GetProcAddress
On Fri., Dec. 11, 2020, 00:24 yanzixiang<EMAIL_ADDRESS>wrote:

My WinCE SDK does NOT have this file,
Can this be disabled by some option ?
I think the dbghelp.h API's are only needed to support DetourFindFunction
https://github.com/microsoft/Detours/wiki/DetourFindFunction, unless I
missed something in the code. Looking at the API's available in windows CE
https://docs.microsoft.com/en-us/previous-versions/windows/embedded/ee488416(v=winembedded.60)
it looks like it doesn't have support. If you don't need
DetourFindFunction support then you might be able to rip it out and get
the other pieces compiling and working.
I assume you are targeting a x86 / ARM 32 ISA, and not MIPS / PowerPC /
SuperH (not support)?
It looks like Windows CE is a derivative of NT, so it appears to have all
the critical API's that detours depends on, so it doesn't seem out of the
real of possibility that it might work without too much effort once you get
it building.
without DetourFindFunction,
how to fint the address of the function ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Detours/issues/106#issuecomment-742977208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRELNWY2RFHXIGRXRY43QLSUGUKBANCNFSM4NAWUAFA
.


Switch to rollup package bundling with CJS ES UMD outputs

We're having similar issues with CommonJS build like https://github.com/joshwnj/react-visibility-sensor/issues/148
So I updated the build process (ref. https://github.com/joshwnj/react-visibility-sensor/issues/75)

this would also allow to build library into ES6 module. Please merge this!


brew extract returns errors for some formula-version combinations

Please note that we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

> brew config
HOMEBREW_VERSION: 2.1.9-7-gde72a23
ORIGIN: https://github.com/Homebrew/brew
HEAD: de72a2310930c3f0903292770b433f197a8d8a6c
Last commit: 3 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: e58c5f3df889abc9f7ba16b37a0becff972f9237
Core tap last commit: 7 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_NO_ANALYTICS_THIS_RUN: 1
CPU: quad-core 64-bit kabylake
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1001
Git: 2.20.1 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 11.0.4, 1.8.0_211
macOS: 10.14.6-x86_64
CLT: <IP_ADDRESS>.1.1562985497
Xcode: N/A
CLT headers: <IP_ADDRESS>.1.1562985497
XQuartz: 2.7.11 => /opt/X11

> brew doctor
Your system is ready to brew.

What you were trying to do (and why)
I want to extract a specific version of a formula (in this case python 3.6.2) to my own tap.
What happened (include command output)
Extraction failed with an error.

Command output

Error: python: undefined method `undent' for #<String:0x00007f832a57b0e8>

What you expected to happen
This shouldn't return an error.
Step-by-step reproduction instructions (by running brew commands)
This works fine:
> brew extract --version=3.7.2 python <my_repo>/versions
==> Searching repository history
==> Writing formula for python from revision 0940099 to<EMAIL_ADDRESS>
This gives an error:
> brew extract --version=3.6.2 python <my_repo>/versions
==> Searching repository history
Error: python: undefined method `undent' for #<String:0x00007f832a57b0e8>

Note: this is not only for python. I've tried other formulae, same thing happens.

If you run this with --debug you'll see that it never actually gets to version 3.6.2, because the python formula changes from 2.7 to 3.6.4 at some point in the past. Furthermore, because brew extract needs to load each formula, our internal formula interface has changed and some formula code is no longer valid in e.g., brew 2.0.
I think we would be interested in a pull request that caught these cases and improved the error message.

Agreed, will accept PR that fixes that, thanks.


track src from ajax request?

sorry, i am more or less new to inonic. my problem: i can make the audio player work. thats fine. now i want to set the audio src dynamically from an ajax call. when i use
  this.singleTrack = {       src: 'https://archive.org/download/swrembel2010-03-07.tlm170.flac16/swrembel2010-03-07s1t05.mp3',       artist: 'Stephane Wrembel',       title: 'Stephane Wrembel Live',       art: 'assets/img/Stephane.jpg',       preload: 'metadata' // tell the plugin to preload metadata such as duration for this track,  set to 'none' to turn off     };
i can't overwrite src afterwards. if i set this.singleTrack in the ajax success, it seems to be to late.

This is related to #106. No progress so far on that, I'll keep you updated if I find anything useful.

Don't know if this is still relevant, almost a year later, please see #188


feat: [M3-7343] – Display conditional Notices depending on config scenarios in Linode Add/Edit Config dialog

Description 📝
If a user is about to select an unrecommended configuration in the Add/Edit Config dialog, we want to display conditional warning notices informing them of this and what we recommend to avoid the network connectivity issues that would come with the unrecommended configuration.
Changes  🔄

Added unrecommendedConfigNoticeSelector function
Added several constants for copy
Display conditional notices depending on scenario in Add/Edit Config dialog

Preview 📷

Scenario 1

Have a VPC interface and another non-VPC interface (public is fine)
the index of the primary interface !== the index of the VPC interface (i.e., the non-VPC interface should be primary)
nattedIPv4Address (i.e., "Assign a public IPv4 address for this Linode" checked)

Scenario 2

all of Scenario 1, except: !nattedIPv4Address (i.e., "Assign a public IPv4 address for this Linode" unchecked)

Scenario 3

only eth0 populated, and it is a VPC interface where !nattedIPv4Address (i.e., "Assign a public IPv4 address for this Linode" unchecked)

How to test 🧪
Prerequisites

An account with the proper VPC tags

Verification steps
In the Add/Edit Config dialog, ensure that the specific scenarios outlined in the Preview section above are all handled as expected, and that none of the notices display outside of the outlined scenarios.
As an Author I have considered 🤔

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[x] 🔐 Removing all sensitive information from the code and PR description
[x] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[x] 📑 Providing or updating our documentation
[x] 🕛 Scheduling a pair reviewing session
[x] 📱 Providing mobile support
[x] ♿  Providing accessibility support

Question: in messing around with different settings, I created a config that had Public Internet in eth0, VPC in eth1, and VLAN in eth2. When I attempted to save my changes, the form did not submit and no feedback was given in the UI. In the console, I saw the error below. Do we want to either surface this or provide some validation in the form?
I don't know enough about configs to know whether this is related to recent VPC changes or a separate issue related to VLANs (I suspect that we just never surfaced this error) -- or whether a user would ever reasonably even try this, but wanted to raise it. Disregard in this PR if it should be addressed in a follow up.

Good find -- I believe from a networking perspective this would be a counterproductive configuration. The API explicitly forbids VLAN interfaces from being marked as primary, and that field is a newer one tied to the VPC project. We should definitely surface the error, but I find the current wording of it to be ambiguous when it's in the context of Cloud. Going to ask API if the reason can be adjusted and I'll create a follow-up ticket to address this issue.

The follow-up ticket mentioned earlier has been created (M3-7480)


Feat(eos_cli_config_gen): Add router internet-exit.

Change Summary
Add router internet-exit
CLI Config:

router internet-exit
   exit-group eg_01
   !
   exit-group eg_02
      fib-default
   !
   exit-group eg_03
      local connection eg_03_lo_01
      local connection eg_03_lo_02
      fib-default
   !
   exit-group eg_04
      local connection eg_04_lo_01
      local connection eg_04_lo_02
      local connection eg_04_lo_03
   !
   policy po_01
      exit-group po_eg_01_02
      exit-group po_eg_01_01
      exit-group po_eg_01_03
      exit-group po_eg_01_04
   !
   policy po_02
   !
   policy po_03
      exit-group po_eg_03_01

Related Issue(s)
Fixes #3741
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Added new data-model for router internet-exit.
Checklist
Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

I don't think this PR fixes all of #3741 - feel free to split the original issues in several sub issues to fix parts of it?

I don't think this PR fixes all of #3741 - feel free to split the original issues in several sub issues to fix parts of it?

Created sub issue and linked it with https://github.com/aristanetworks/avd/issues/3741

I don't think this PR fixes all of #3741 - feel free to split the original issues in several sub issues to fix parts of it?

Will work on this, changing PR to draft.

I don't think this PR fixes all of #3741 - feel free to split the original issues in several sub issues to fix parts of it?

Will work on this, changing PR to draft.

Done!

Need to check the ordering of exit-groups inside a policy as this is important.
@gauravv9

Need to check the ordering of exit-groups inside a policy as this is important. @gauravv9

Verified and fixed in 59f8153


DOCS-5309 Cilium Integration Edits + Metrics Versioning Organization

What does this PR do?

Adds a Prerequisites section to the README and reshuffles the metrics in the metadata.csv to be according to version (V1, V2, V1 and V2).
Motivation

DOCS-5309, thanks @urseberry for the reminder to reopen this PR!
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

I just noticed that tests are failing for the metadata stuff, let me see if I can sort it out (along with the config spec changes proposed) and update this branch with all that.

Heads up that I've rebased and force-pushed with the changes to the config. For the metadata part, I'm having second thoughts on whether the ordering change helps.


chore(enhancement): query param value matches on decodedURI value set

i found an issues about this repo when it trying to match response with query param, even though my request is exactly the same as the document response.originalRequest, it still cannot match.
The issues is the document query doesn't count for the same key, and its does not decode the query values.
reproduction of the bug

copy ./test/collections/all-request-types.json to main branch
copy requestTypesTest.js to the main brach
run the test

Hey @Xyedo - thanks for the PR.
I think the code could be optimised a bit. Would you be ok with updating to something like this:
if (responseHasQueryMember) {
  const decodeAndSplit = value =>
      value.split(',').map(decodeURI);

  /**
   * Iterate through the query parameters and check the following:
   *
   * 1. If we have already processed a query param with this key - retrieve the value, else return an empty array.
   * 2. Evaluate the current param value
   * 2.1. If the param value is an array, flatten each item of the array and return the decoded version.
   * 2.2. If the param value is not an array, return the decoded version.
   * 3. Update the value in the Key/Value Map.
   */

  for (const param of response.originalRequest.url.query.members) {
      const existingValues = kv.get(param.key) || [];
      const thisParamValues = Array.isArray(param.value)
          ? param.value.flatMap(decodeAndSplit)
          : decodeAndSplit(param.value);
      kv.set(param.key, existingValues.concat(thisParamValues));
  }
}

I've run the tests and everything passes as expected. If you can update your fork and push to the PR I can merge it.

Hi, thanks for checking my PR,
the PR is updated with your optimization and added a case when query is disabled on postman


Make Widgets automatically select Cupertino or MTV style

Everywhere in my code where I need to use a Switch I currently need to check if I'm on iOS and in that case use a CupertinoSwitch.
It would be pretty sweet if I could just use a Switch and it would automatically use a CupertinoSwitch or a MountainviewSwitch depending on the platform. Basically the Switch class would in this case be a wrapper for the platform dependent switches. In the case that I want the component to look the same on both platforms I could just choose to use the platform dependent version.
It would be great if this worked across all widgets, including page routes, etc. Right now, some widgets and behaviors are different across platforms and some are not. I would love to be able to easily choose if I want a specific widget to be the same on both platforms or use the platform specific ones.

This is the plan, yes.
cc @xster

I wonder if this would be a package, in order to experiment first? Or, we want to go straight to the core framework?

Duping into #8410


[ToB] [Frontend] Authentication

Resolves #23692

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Replace the fake user name and surname.

@alexeyinkin I've filed an issue: https://github.com/flutter/flutter/issues/116176

Codecov Report

Merging #287 (37fb90c) into master (cf56af2) will decrease coverage by 0.00%.
The diff coverage is 52.58%.

:exclamation: Current head 37fb90c differs from pull request most recent head 1e38328. Consider uploading reports for the commit 1e38328 to get more accurate results

@@            Coverage Diff             @@
##           master     #287      +/-   ##
==========================================
- Coverage   51.45%   51.45%   -0.01%
==========================================
  Files         241      242       +1
  Lines       29543    29659     +116
==========================================
+ Hits        15202    15260      +58
- Misses      13019    13068      +49
- Partials     1322     1331       +9

Flag
Coverage Δ

go
51.45% <52.58%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

sdks/go/pkg/beam/io/spannerio/spanner.go
52.58% <52.58%> (ø)

sdks/go/pkg/beam/core/metrics/dumper.go
49.20% <0.00%> (-4.77%)
:arrow_down:

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