Flutter Localizations intl version

[✓] Flutter (Channel stable, v1.9.1+hotfix.4, on Mac OS X 10.14.6 18G103, locale
    tr-TR)
    • Flutter version 1.9.1+hotfix.4 at /Dosyalar/flutter_src/flutter
    • Framework revision cc949a8e8b (10 days ago), 2019-09-27 15:04:59 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/malikdoksoz/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.7.5

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.0.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.38.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.5.1

[✓] Connected device (1 available)
    • SM N910C • 4100cf49f20512e9 • android-arm • Android 6.0.1 (API 23)

• No issues found!

**pubspec.yaml**

flutter_localizations:
sdk: flutter
intl: ^0.16.0

**Running "flutter pub get" in flutterappexample...
Because flutterappexample depends on flutter_localizations any from sdk which depends on intl 0.15.8, intl 0.15.8 is required.

So, because flutterappexample depends on intl ^0.16.0, version solving failed.**

Hm, flutter_localizations depends on intl 0.16.0 https://github.com/flutter/flutter/blob/master/packages/flutter_localizations/pubspec.yaml.
@malikdoksoz Can you try to run flutter pub get without having intl in flutterappexample dependency? May be it will update the package as it's needed.

Hm, flutter_localizations depends on intl 0.16.0 https://github.com/flutter/flutter/blob/master/packages/flutter_localizations/pubspec.yaml.
But upgrade was done in v1.10.3 which is not in stable yet. I think you will need to use 0.15.8 or switch to dev/master branch.

I fixed with this dependency_overrides
dependency_overrides:
  intl: ^0.16.0

i have this issue but i need solution
without update to 16 .
any help  plesss
[✓] Flutter (Channel beta, v1.12.13+hotfix.6, on Linux, locale en_US.UTF-8)
• Flutter version 1.12.13+hotfix.6 at /home/ppain/development/flutter
• Framework revision 18cd7a3601 (5 weeks ago), 2019-12-11 06:35:39 -0800
• Engine revision 2994f7e1e6
• Dart version 2.7.0

Hm, flutter_localizations depende da int 0.16.0 https://github.com/flutter/flutter/blob/master/packages/flutter_localizations/pubspec.yaml .
Mas a atualização foi feita na v1.10.3, que ainda não está estável. Eu acho que você precisará usar 0.15.8 ou mudar para o ramo dev / master.

Corrigi com este dependency_overrides
dependency_overrides:
  intl: ^0.16.0

Serviu para mim

when i try to override dependency, it do not show any error but when i try to run main.dart, it gives the following error,

Running Gradle task 'assembleDebug'...
../../snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/gradient_app_bar-0.1.3/lib/gradient_app_bar.dart:407:57: Error: No named parameter with the name 'nullOk'.
final ScaffoldState scaffold = Scaffold.of(context, nullOk: true);
^^^^^^
../../snap/flutter/common/flutter/packages/flutter/lib/src/material/scaffold.dart:1944:24: Context: Found this candidate, but the arguments don't match.
static ScaffoldState of(BuildContext context) {
^^
../../snap/flutter/common/flutter/.pub-cache/hosted/pub.dartlang.org/gradient_app_bar-0.1.3/lib/gradient_app_bar.dart:636:20: Error: The method 'ancestorRenderObjectOfType' isn't defined for the class 'BuildContext'.

'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('../../snap/flutter/common/flutter/packages/flutter/lib/src/widgets/framework.dart').
Try correcting the name to the name of an existing method, or defining a method named 'ancestorRenderObjectOfType'.
return context.ancestorRenderObjectOfType(
^^^^^^^^^^^^^^^^^^^^^^^^^^

FAILURE: Build failed with an exception.

Where:
Script '/home/invisible/snap/flutter/common/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 991

What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.

Process 'command '/home/invisible/snap/flutter/common/flutter/bin/flutter'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 21s
Exception: Gradle task assembleDebug failed with exit code 1

my pubspec.yaml looks like this
name: (myAppName)
description: A new Flutter application.

version: 1.0.0+1

environment:
  sdk: ">=2.2.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  intl: ^0.16.0
  flutter_form_builder: ^4.2.0
  table_calendar: ^2.3.3

  gradient_app_bar: ^0.1.3
  flutter_slidable: "^0.5.3"

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_launcher_icons: ^0.7.3

flutter_icons:
  android: "launcher_icon"
  ios: true
  image_path: "assets/icon/icon.png"

dependency_overrides:
  intl: ^0.16.0

can someone help me with this please. thank you very much


006 super resolution

fixed #26

[x] implement smoothed Laplace
[x] reduce dimension through an likelihood approximation
[x] CUQIpy-Pytorch's NUTS

This notebook shows a combined use of smoothed Laplace prior, reduced likelihood computation and efficient gradient sampler;

The forward model and the associated indices for the reduced likelihood are imported from binary files prepared by the author;
This notebook uses NUTS from CUQIpy-PyTorch;
The sampling is rather expensive, consuming like 20 hours on the gbar HPC;
The index of this notebook will be 12 as 6 is taken by the one  on PnP

It looks great and I like the additional final explanations added as agreed this morning.
It seems the generated outputs were not saved in this version, so please can you rerun and include the outputs, so the notebooks can be browsed with results directly on github.
Also, in the readme, please add in the list of topics covered: CUQIpy-pyTorch plugin.

Done, sorry for not noticing the loss of outputs (it seems due to an accident merge) but they are back now.

Thank @jakobsj and @raff0722 for your review. I'm now merging this branch to the main.


dragToss and dragWithSpring props doesn't work on Android

Environment:
Android 7.1.2
Packages:
react: 16.3.1
react-native: 0.55.4
react-native-interactable: 0.1.10
Values (Weird values just for example and visualization bellow of the diferences between behaviors)
dragWithSpring={{ tension: 2000, damping: 0 }}
dragToss={0}

Behaviors
iOS:

Android:

I only want that both platforms to have the same behavior

resolved with PR #255


use current balance toggle in calculator is not functional when disabled

Description
use current balance toggle turns boxes to gold but boxes does not turn back to normal when disabled
Screencast from 10-09-2023 11:06:46 AM.webm
normal view:

view after using use current balance:

(boxes turn into gold)
view after disabling use current balance:

the UI gold color for the boxes does not change neihter the cost of the deployment

Blocked as I was working on another issue #1018

All done and waiting for review

working on handling this issue in same pr https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1236

is the golden color removed?

is the golden color removed?

golden color is still available

Verified,
Devnet, 14a9eaf.
The use of the current balance toggle is working fine when enabled.

And when it is disabled, the balance amount is reset to 0 and recalculated.

And also, the gold package still has the golden color.

TC2291 - Calculate Deployment Cost using the current balance

Verified:

Devnet
ebf75a3

toggle certified node filter only; shows the $/month is ok

toggle certified node filter + public IPv4 filter; shows the $/month in bad shape (need better round for the value)

verified with the last changes and working fine

Verified:

Devnet
842ebef


Projects: Project list page

Create projects page which lists active projects.  Look similar to current AV project page, displaying projects in order of most recently active.
Probably depends on a projects query from the backend, although you can develop using mock/fixture data.

Maybe use refetchInterval setting to keep data fresh:
https://www.gatsbyjs.com/plugins/gatsby-source-graphql/


Divison by zero?

I get a strange message, when enabling all features and image types:
File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 162, in calculateFeatures
self.featureValues[feature] = getattr(self, 'get%sFeatureValue' % feature)()
File "/usr/local/lib/python3.6/dist-packages/radiomics/ngtdm.py", line 238, in getContrastFeatureValue
contrast = (numpy.sum(p_i[:, None] * p_i[None, :] * (i[:, None] - i[None, :]) ** 2) / (Ngp * (Ngp - 1))) *
File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
_showwarnmsg_impl(msg)
File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
text = _formatwarnmsg(msg)
File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'
Inspecting the line, it seems that the error occurs if the divisor, D = (numpy.sum(s_i)) / Nvp, is zero.
There is no check for this there, and probably one should be added.
(Again thanks for the great package :D)

Nvp is the number of voxels which have a valid region. If that number is zero, this most likely means that your segmentation consists only of individual voxels here and there. In that case, it is not possible to calculated texture and you should review that case and consider excluding it.
If this case does contain a valid segmentation, could you share an anonymized copy so we can debug?

I will check the segmentation again, and come back to you. (And for sure you are right)
But nonetheless, would a proper error logging like "Unable to compute contrast, is the segmentation correct?" not better than just crashing? Also, as i often compute many features inside a simple, i'd personally like that there is just a warning instead of a crash, but i could clearly catch the error myself.

@aydindemircioglu There already is some checking of validity of the mask prior to feature calculation. Moreover, the division by 0 is just causing a warning, not a crash. The error you get is a format error, in that ITK is unable to format the warning message and therefore throws an error. I will look into this further...

strange, i had to reinstall my linux OS on one of my computers, there, with python 3.5, i dont get the above error message but just "invalid value encountered in double_scalars". the mask itself it pretty large, around 13000 voxels, and from very first sight (non-radiologist and 8bit compressed image) i'm sure that there is contrast there. its also not loosely connected, as i explicitly throw out everything except for the largest region (using "all-direction" connecteness). will try to understand what happens there.

@JoostJM
its hard for me to debug properly, but it seems a bit like there is not enough contrast,
thus only 1 bin gets applied, thus(?) there only one s_i coeffient, which is zero.
something along those lines perhaps? the start of the log file is like this, the INVALID line
i added just prior to the offending line, just to see where to look at.
it actually happens multiple times for the image/mask combination, i assume this is because
of different image types.
INFO:radiomics.featureextractor: No valid config parameter, applying defaults: {'normalize': False, 'resegmentRange': None, 'force2Ddimension': 0, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'preCrop': False, 'label': 1, 'padDistance': 5, 'distances': [1], 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Enabled image types: {'Original': {}}
INFO:radiomics.featureextractor: Enabled features: {'shape': [], 'firstorder': [], 'glrlm': [], 'gldm': [], 'glszm': [], 'ngtdm': [], 'glcm': []}
DEBUG:radiomics.featureextractor: Enabling all features in all feature classes
DEBUG:radiomics.featureextractor: Enabled features: {'shape': [], 'firstorder': [], 'glrlm': [], 'gldm': [], 'glszm': [], 'ngtdm': [], 'glcm': []}
DEBUG:radiomics.featureextractor: Enabling all image types
DEBUG:radiomics.featureextractor: Enabled images types: {'LBP3D': {}, 'Square': {}, 'Gradient': {}, 'Original': {}, 'Logarithm': {}, 'LoG': {}, 'SquareRoot': {}, 'Exponential': {}, 'Wavelet': {}, 'LBP2D': {}}
DEBUG:radiomics.featureextractor: Enabling image type LoG (additional custom settings: {'sigma': [1.0]})
DEBUG:radiomics.featureextractor: Enabled images types: {'LBP3D': {}, 'Square': {}, 'Gradient': {}, 'Original': {}, 'Logarithm': {}, 'LoG': {'sigma': [1.0]}, 'SquareRoot': {}, 'Exponential': {}, 'Wavelet': {}, 'LBP2D': {}}
INFO:radiomics.featureextractor: Calculating features with label: 1
DEBUG:radiomics.featureextractor: Enabled images types: {'LBP3D': {}, 'Square': {}, 'Gradient': {}, 'Original': {}, 'Logarithm': {}, 'LoG': {'sigma': [1.0]}, 'SquareRoot': {}, 'Exponential': {}, 'Wavelet': {}, 'LBP2D': {}}
DEBUG:radiomics.featureextractor: Enabled features: {'shape': [], 'firstorder': [], 'glrlm': [], 'gldm': [], 'glszm': [], 'ngtdm': [], 'glcm': []}
DEBUG:radiomics.featureextractor: Current settings: {'normalize': False, 'resegmentRange': None, 'force2Ddimension': 0, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'preCrop': False, 'label': 1, 'padDistance': 5, 'distances': [1], 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Loading image and mask
DEBUG:radiomics.imageoperations: Checking mask with label 1
DEBUG:radiomics.imageoperations: Calculating bounding box
DEBUG:radiomics.imageoperations: Checking minimum number of dimensions requirements (1)
DEBUG:radiomics.featureextractor: Image and Mask loaded and valid, starting extraction
INFO:radiomics.featureextractor: Adding additional extraction information
DEBUG:radiomics.imageoperations: Cropping to size [61 54 15]
INFO:radiomics.featureextractor: Computing shape
DEBUG:radiomics.shape: Initializing feature class
DEBUG:radiomics.shape: Padding the mask with 0s
DEBUG:radiomics.shape: Pre-calculate Volume, Surface Area and Eigenvalues
DEBUG:radiomics.shape: Calculating Surface Area in C
DEBUG:radiomics.shape: Shape feature class initialized
DEBUG:radiomics.shape: Calculating features
DEBUG:radiomics.shape: Calculating Maximum 3D diameter in C
DEBUG:radiomics.imageoperations: Generating angles
DEBUG:radiomics.imageoperations: Generated 13 angles
DEBUG:radiomics.featureextractor: Creating image type iterator
INFO:radiomics.featureextractor: Adding image type "LBP3D" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Square" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Gradient" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Original" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Logarithm" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "LoG" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'sigma': [1.0], 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "SquareRoot" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Exponential" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "Wavelet" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
INFO:radiomics.featureextractor: Adding image type "LBP2D" with settings: {'normalize': False, 'force2Ddimension': 0, 'resampledPixelSpacing': None, 'normalizeScale': 1, 'enableCExtensions': True, 'minimumROISize': None, 'label': 1, 'distances': [1], 'resegmentRange': None, 'removeOutliers': None, 'force2D': False, 'minimumROIDimensions': 1, 'preCrop': False, 'padDistance': 5, 'additionalInfo': True, 'interpolator': 'sitkBSpline'}
DEBUG:radiomics.featureextractor: Extracting features
INFO:radiomics.featureextractor: Calculating features for lbp-3D-m1 image
DEBUG:radiomics.imageoperations: Cropping to size [61 54 15]
INFO:radiomics.featureextractor: Computing firstorder
DEBUG:radiomics.firstorder: Initializing feature class
DEBUG:radiomics.firstorder: First order feature class initialized
DEBUG:radiomics.firstorder: Calculating features
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
INFO:radiomics.featureextractor: Computing glrlm
DEBUG:radiomics.glrlm: Initializing feature class
DEBUG:radiomics.imageoperations: Discretizing gray levels inside ROI
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
DEBUG:radiomics.glrlm: Calculating GLRLM matrix in C
DEBUG:radiomics.imageoperations: Generating angles
DEBUG:radiomics.imageoperations: Generated 13 angles
DEBUG:radiomics.glrlm: Process calculated matrix
DEBUG:radiomics.glrlm: No empty angles
DEBUG:radiomics.glrlm: Calculating GLRLM coefficients
DEBUG:radiomics.glrlm: GLRLM feature class initialized, calculated GLRLM with shape (1, 54, 13)
DEBUG:radiomics.glrlm: Calculating features
INFO:radiomics.featureextractor: Computing gldm
DEBUG:radiomics.gldm: Initializing feature class
DEBUG:radiomics.imageoperations: Discretizing gray levels inside ROI
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
DEBUG:radiomics.imageoperations: Generating angles
DEBUG:radiomics.imageoperations: Generated 13 angles
DEBUG:radiomics.gldm: Feature class initialized, calculated GLDM with shape (1, 24)
DEBUG:radiomics.gldm: Calculating features
INFO:radiomics.featureextractor: Computing glszm
DEBUG:radiomics.glszm: Initializing feature class
DEBUG:radiomics.imageoperations: Discretizing gray levels inside ROI
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
DEBUG:radiomics.glszm: Calculating GLSZM matrix in C
DEBUG:radiomics.imageoperations: Generating angles
DEBUG:radiomics.imageoperations: Generated 13 angles
DEBUG:radiomics.glszm: Calculating GLSZM coefficients
DEBUG:radiomics.glszm: GLSZM feature class initialized, calculated GLSZM with shape (1, 1)
DEBUG:radiomics.glszm: Calculating features
INFO:radiomics.featureextractor: Computing ngtdm
DEBUG:radiomics.ngtdm: Initializing feature class
DEBUG:radiomics.imageoperations: Discretizing gray levels inside ROI
DEBUG:radiomics.imageoperations: Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
DEBUG:radiomics.imageoperations: Generating angles
DEBUG:radiomics.imageoperations: Generated 13 angles
DEBUG:radiomics.ngtdm: Calculating features
ERROR:radiomics.ngtdm: INVALID

i also have a warning like
Calculating Local Binary Pattern in 2D, but extracting features in 3D. Use with caution!
on the command line (but i cant see it in the log file)-- i made sure to have trimesh, scipy
and scikit-images installed, do i overlook something?

mmh, this seems actually to happen much often than i thought-- i did not see it because to fix my loop i just did check if s_i == 0 if so, i return 0. maybe our images from this study have too low contrast for ngtdm to work?

@aydindemircioglu, not necessarily, what kind of values do you get for originial_firstorder_range
The problem is that for texture calculation, you need to discretize your gray values. This is controlled by the binWidth parameter, which is by default 25 (aimed at CT).

As to the warning "Calculating Local Binary Pattern in 2D, but extracting features in 3D. Use with caution!" that is due to the fact that PyRadiomics implements a local binary pattern filter for 2D and 3D separately (different calculation, see documentation). This warning is displayed when your extraction method (2D or 3D) does not comply with the chosen filter. Because you have both filters enabled, it gives the warning for the LBP2D filter (as your features are extracted in 3D).

thanks for all the input.
the range over all images is like this:

z$original_firstorder_Range
[1]<PHONE_NUMBER>  694 1253  770 1739  802 1056  751  807<PHONE_NUMBER>  768
[16]  696  222  863  595<PHONE_NUMBER><PHONE_NUMBER>  471  845<PHONE_NUMBER>
[31] 1267  989 1068<PHONE_NUMBER>  423  848  420<PHONE_NUMBER><PHONE_NUMBER>
[46] 1079  568  703  521  570

i just tried binWidth=5, but that doesnt help with the problem, i actually get then some other division by zero errors in other features. i also wanted to use binWidth=1, but then i guess this does not make much sense, and the matrices get quite large.
so for now i just skip ntgdm, i will check if i can send you an image so you can see the problem first hand.

@aydindemircioglu I think I discovered the error, take a look at this line from your output:
INFO:radiomics.featureextractor: Calculating features for lbp-3D-m1 image
This means it's calculating features on this filter, and as is mentioned in the documentation of that filter, local binary pattern tends to have very small ranges of gray values, so for LBP, it makes sense to use a small binwidth (1 is fine, possibly even smaller than 1, but stick with 1 to start).
To apply a customized binwidth only for LBP, specify your parameter file like this:
imageType:
  Original: {}  # No customized settings for original filter
  LBP3D:
    binWidth: 1.0

featureClass:
  (...)  # Specify features to extract here

setting:
  (...)  # Specify your general settings here

Hi @JoostJM , as you said , I specifed the parameter " LBP3D" in my parameter file like this:

imageType:
  LBP3D:
    binWidth: 1.0

then I run it and I get this error:
Key 'LBP3D' was not defined. Path: '/imageType'.: Path: '/'>
What happend? I'm sure I have updated to the latest edition. Look forward to your reply and thank you for your time.

@QiChen2014, This is a bug, I'm fixing it in #364.

i wont be able to test until next week, just in case you wonder.

i am really sorry, but i have to defer testing to mid may :S
you may want to close it for now, i can reopen it, if the error still persists.

ok, i took me only two month to get back to the topic :D (sorry again)
this is now a completely different data set, but i have the very same problem. i followed your advise, @JoostJM, and did apply the binwidth like this:
```extractor.enableImageTypeByName('LBP3D', True, {'binwidth': 1.0})```

but it did not help. also when i completely turn off the LBP computations
```extractor.enableImageTypeByName('LBP2D', False, {})

extractor.enableImageTypeByName('LBP3D', False, {})```
the error is still there.tried also with a binwidth of 0.5, 0.1 and 0.01 same thing. masks, as far as i can see them, are not constant or empty. disabling NGMT directly helps, as said.

@aydindemircioglu Can you share your log? that really helps tracking issues like this down

Also, can you share the results if you run only extracting firstorder Range (with all your intended filters enabled)?
Calculating features with label: 1
Enabled images types: {'Original': {}, 'Exponential': {}, 'Gradient': {}, 'LBP2D': {}, 'LoG': {'sigma': [1.0]}, 'Logarithm': {}, 'Square': {}, 'SquareRoot': {}, 'Wavelet': {}}
Enabled features: {'firstorder': [], 'glcm': [], 'gldm': [], 'glrlm': [], 'glszm': [], 'ngtdm': [], 'shape': []}
Current settings: {'minimumROIDimensions': 1, 'minimumROISize': None, 'normalize': False, 'normalizeScale': 1, 'removeOutliers': None, 'resampledPixelSpacing': None, 'interpolator': 'sitkBSpline', 'preCrop': False, 'padDistance': 5, 'distances': [1], 'force2D': False, 'force2Ddimension': 0, 'resegmentRange': None, 'label': 1, 'additionalInfo': True, 'voxelBased': False}
Loading image and mask
Checking mask with label 1
Calculating bounding box
Checking minimum number of dimensions requirements (1)
Image and Mask loaded and valid, starting extraction
Adding additional extraction information
Cropping to size [114 107  38]
Computing shape
Initializing feature class
Padding the mask with 0s
Pre-calculate Volume, Surface Area and Eigenvalues
Calculating Surface Area in C
Shape feature class initialized
Calculating features
Calculating Maximum diameters in C
Creating image type iterator
Adding image type "Original" with custom settings: {}
Adding image type "Exponential" with custom settings: {}
Adding image type "Gradient" with custom settings: {}
Adding image type "LBP2D" with custom settings: {}
Adding image type "LoG" with custom settings: {'sigma': [1.0]}
Adding image type "Logarithm" with custom settings: {}
Adding image type "Square" with custom settings: {}
Adding image type "SquareRoot" with custom settings: {}
Adding image type "Wavelet" with custom settings: {}
Extracting features
Yielding original image
Calculating features for original image
Cropping to size [114 107  38]
Computing firstorder
Initializing feature class
First order feature class initialized
Calculating features
Calculated 10 bins for bin width 25 with edges: [ 25.  50.  75. 100. 125. 150. 175. 200. 225. 250. 275.])
Computing glcm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 10 bins for bin width 25 with edges: [ 25  50  75 100 125 150 175 200 225 250 275])
Calculating GLCM matrix in C
Process calculated matrix
Create symmetrical matrix
No empty angles
Calculating GLCM coefficients
GLCM feature class initialized, calculated GLCM with shape (10, 10, 13)
Calculating features
GLCM is symmetrical, therefore Sum Average = 2 * Joint Average, only 1 needs to be calculated
Computing gldm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 10 bins for bin width 25 with edges: [ 25  50  75 100 125 150 175 200 225 250 275])
Feature class initialized, calculated GLDM with shape (10, 27)
Calculating features
Computing glrlm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 10 bins for bin width 25 with edges: [ 25  50  75 100 125 150 175 200 225 250 275])
Calculating GLRLM matrix in C
Process calculated matrix
No empty angles
Calculating GLRLM coefficients
GLRLM feature class initialized, calculated GLRLM with shape (10, 73, 13)
Calculating features
Computing glszm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 10 bins for bin width 25 with edges: [ 25  50  75 100 125 150 175 200 225 250 275])
Calculating GLSZM matrix in C
Calculating GLSZM coefficients
GLSZM feature class initialized, calculated GLSZM with shape (10, 54)
Calculating features
Computing ngtdm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 10 bins for bin width 25 with edges: [ 25  50  75 100 125 150 175 200 225 250 275])
Calculating features
Yielding exponential image
Calculating features for exponential image
Cropping to size [114 107  38]
Computing firstorder
Initializing feature class
First order feature class initialized
Calculating features
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Computing glcm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Calculating GLCM matrix in C
Process calculated matrix
Create symmetrical matrix
No empty angles
Calculating GLCM coefficients
GLCM feature class initialized, calculated GLCM with shape (2, 2, 13)
Calculating features
GLCM is symmetrical, therefore Sum Average = 2 * Joint Average, only 1 needs to be calculated
Computing gldm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Feature class initialized, calculated GLDM with shape (2, 27)
Calculating features
Computing glrlm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Calculating GLRLM matrix in C
Process calculated matrix
No empty angles
Calculating GLRLM coefficients
GLRLM feature class initialized, calculated GLRLM with shape (2, 114, 13)
Calculating features
Computing glszm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Calculating GLSZM matrix in C
Calculating GLSZM coefficients
GLSZM feature class initialized, calculated GLSZM with shape (2, 15)
Calculating features
Computing ngtdm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 2 bins for bin width 25 with edges: [ 0. 25. 50.])
Calculating features
Calculating features for gradient image
Cropping to size [114 107  38]
Computing firstorder
Initializing feature class
First order feature class initialized
Calculating features
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Computing glcm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Calculating GLCM matrix in C
Process calculated matrix
Create symmetrical matrix
No empty angles
Calculating GLCM coefficients
GLCM feature class initialized, calculated GLCM with shape (5, 5, 13)
Calculating features
GLCM is symmetrical, therefore Sum Average = 2 * Joint Average, only 1 needs to be calculated
Computing gldm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Feature class initialized, calculated GLDM with shape (5, 27)
Calculating features
Computing glrlm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Calculating GLRLM matrix in C
Process calculated matrix
No empty angles
Calculating GLRLM coefficients
GLRLM feature class initialized, calculated GLRLM with shape (5, 113, 13)
Calculating features
Computing glszm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Calculating GLSZM matrix in C
Calculating GLSZM coefficients
GLSZM feature class initialized, calculated GLSZM with shape (5, 52)
Calculating features
Computing ngtdm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 5 bins for bin width 25 with edges: [  0.  25.  50.  75. 100. 125.])
Calculating features
Calculating Local Binary Pattern in 2D, but extracting features in 3D. Use with caution!
Calculating features for lbp-2D image
Cropping to size [114 107  38]
Computing firstorder
Initializing feature class
First order feature class initialized
Calculating features
Calculated 1 bins for bin width 25 with edges: [ 0. 25.])
Computing glcm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1 bins for bin width 25 with edges: [ 0 25])
Calculating GLCM matrix in C
Process calculated matrix
Create symmetrical matrix
No empty angles
Calculating GLCM coefficients
GLCM feature class initialized, calculated GLCM with shape (1, 1, 13)
Calculating features
GLCM is symmetrical, therefore Sum Average = 2 * Joint Average, only 1 needs to be calculated
Computing gldm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1 bins for bin width 25 with edges: [ 0 25])
Feature class initialized, calculated GLDM with shape (1, 20)
Calculating features
Computing glrlm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1 bins for bin width 25 with edges: [ 0 25])
Calculating GLRLM matrix in C
Process calculated matrix
No empty angles
Calculating GLRLM coefficients
GLRLM feature class initialized, calculated GLRLM with shape (1, 114, 13)
Calculating features
Computing glszm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1 bins for bin width 25 with edges: [ 0 25])
Calculating GLSZM matrix in C
Calculating GLSZM coefficients
GLSZM feature class initialized, calculated GLSZM with shape (1, 1)
Calculating features
Computing ngtdm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1 bins for bin width 25 with edges: [ 0 25])
Calculating features
FAILED: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 297, in _calculateFeatures
    yield True, feature, getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/ngtdm.py", line 161, in getContrastFeatureValue
    contrast = (numpy.sum(p_i[:, None] * p_i[None, :] * (i[:, None] - i[None, :]) ** 2) / (Ngp * (Ngp - 1))) * \
  File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
    _showwarnmsg_impl(msg)
  File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
    text = _formatwarnmsg(msg)
  File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
    msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

Generating LoG images
Computing LoG with sigma 1
Yielding log-sigma-1-0-mm-3D image
Calculating features for log-sigma-1-0-mm-3D image
Cropping to size [114 107  38]
Computing firstorder

i call pyradiomics with these lines (here with lbp-2d, but as said, does not seem to matter)
            extractor = featureextractor.RadiomicsFeaturesExtractor()

            # enable all features and filters
            extractor.enableAllFeatures()
            #extractor.enableFeatureClassByName('ngtdm', enabled = False)

            extractor.enableAllImageTypes()
            extractor.enableImageTypeByName('LoG', True, {'sigma': [1.0]})
            extractor.enableImageTypeByName('LBP3D', False, {})
            extractor.enableImageTypeByName('LBP2D', True, {})

i relly wonder what i am doing wrong, as seemingly no one else is experiencing the problem. i will retest it on another computer to make sure i can reproduce this.
i also updated to the latest master.

regarding the range, i have several series (km, dce, darkfluid whatever), e.g. with darkfluid and a random image (it does not seem to depend on the image, i added a shuffle, so each time it is another image) i get 'original_firstorder_Range', 343.0

@aydindemircioglu, that range is a lot smaller than the range of your average CT (on which the default bin width of 25 is based). You can see this reflected in your log, with generally less than 10 bins calculated.
Additionally, it is certainly too large for the LBP filter, so maybe use a custom even smaller binWidth there.
I suggest trying:
extractor = featureextractor.RadiomicsFeaturesExtractor()

# enable all features and filters
extractor.enableAllFeatures()
#extractor.enableFeatureClassByName('ngtdm', enabled = False)

extractor.settings['binWidth'] = 2.5  # Applies generally, overrides default binWidth - 25

extractor.enableAllImageTypes()
extractor.enableImageTypeByName('LoG', True, {'sigma': [1.0]})
extractor.enableImageTypeByName('LBP3D', False, {'binWidth': 0.5})  # Override the general binWidth of 2.5, as LBP generally returns small values.
# extractor.enableImageTypeByName('LBP2D', True, {})  # You are extracting in 3D, so you can use the LBP in 3D as well

Finally, as to the error you're getting, that is a bug in (Simple)ITK, not in PyRadiomics. In your older installation with python 3.5, your installed SimpleITK did not have that bug, and correctly formatted the warning it is trying to give ("invalid value encountered in double_scalars", which happens in case of a division by 0)

thanks for all quick answer.
but i am still a bit puzzled. it does still not fix the error, i think, these are the new debug lines, could ib e that  the binwidth is too small and the problem occurs in gldm instead of ngtdm?
should i normalize the images beforehand, by using the option in pyradiomics to be on the safe side?

Calculating features with label: 1
Enabled images types: {'Original': {}, 'Exponential': {}, 'Gradient': {}, 'LBP2D': {}, 'LoG': {'sigma': [1.0]}, 'Logarithm': {}, 'Square': {}, 'SquareRoot': {}, 'Wavelet': {}}
Enabled features: {'firstorder': [], 'glcm': [], 'gldm': [], 'glrlm': [], 'glszm': [], 'ngtdm': [], 'shape': []}
Current settings: {'minimumROIDimensions': 1, 'minimumROISize': None, 'normalize': False, 'normalizeScale': 1, 'removeOutliers': None, 'resampledPixelSpacing': None, 'interpolator': 'sitkBSpline', 'preCrop': False, 'padDistance': 5, 'distances': [1], 'force2D': False, 'force2Ddimension': 0, 'resegmentRange': None, 'label': 1, 'additionalInfo': True, 'binWidth': 2.5, 'voxelBased': False}
Loading image and mask
Checking mask with label 1
Calculating bounding box
Checking minimum number of dimensions requirements (1)
Image and Mask loaded and valid, starting extraction
Adding additional extraction information
Cropping to size [43 27  7]
Computing shape
Initializing feature class
Padding the mask with 0s
Pre-calculate Volume, Surface Area and Eigenvalues
Calculating Surface Area in C
Shape feature class initialized
Calculating features
Calculating Maximum diameters in C
Creating image type iterator
Adding image type "Original" with custom settings: {}
Adding image type "Exponential" with custom settings: {}
Adding image type "Gradient" with custom settings: {}
Adding image type "LBP2D" with custom settings: {}
Adding image type "LoG" with custom settings: {'sigma': [1.0]}
Adding image type "Logarithm" with custom settings: {}
Adding image type "Square" with custom settings: {}
Adding image type "SquareRoot" with custom settings: {}
Adding image type "Wavelet" with custom settings: {}
Extracting features
Yielding original image
Calculating features for original image
Cropping to size [43 27  7]
Computing firstorder
Initializing feature class
First order feature class initialized
Calculating features
Calculated 1247 bins for bin width 2.5 with edges: [ 505.   507.5  510.  ... 3617.5 3620.  3622.5])
Computing glcm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1247 bins for bin width 2.5 with edges: [ 505.   507.5  510.  ... 3617.5 3620.  3622.5])
Calculating GLCM matrix in C
Process calculated matrix
Create symmetrical matrix
No empty angles
Calculating GLCM coefficients
GLCM feature class initialized, calculated GLCM with shape (323, 323, 13)
Calculating features
GLCM is symmetrical, therefore Sum Average = 2 * Joint Average, only 1 needs to be calculated
Computing gldm
Initializing feature class
Discretizing gray levels inside ROI
Calculated 1247 bins for bin width 2.5 with edges: [ 505.   507.5  510.  ... 3617.5 3620.  3622.5])
Feature class initialized, calculated GLDM with shape (323, 5)
Calculating features
FAILED: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 297, in _calculateFeatures
    yield True, feature, getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/gldm.py", line 377, in getLargeDependenceLowGrayLevelEmphasisFeatureValue
    ldlgle = numpy.sum(self.P_gldm * (jvector[None, :] ** 2) / (ivector[:, None] ** 2)) / Nz
  File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
    _showwarnmsg_impl(msg)
  File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
    text = _formatwarnmsg(msg)
  File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
    msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

FAILED: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 297, in _calculateFeatures
    yield True, feature, getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/gldm.py", line 300, in getLowGrayLevelEmphasisFeatureValue
    lgle = numpy.sum(pg / (ivector ** 2)) / Nz
  File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
    _showwarnmsg_impl(msg)
  File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
    text = _formatwarnmsg(msg)
  File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
    msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

FAILED: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 297, in _calculateFeatures
    yield True, feature, getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/gldm.py", line 339, in getSmallDependenceLowGrayLevelEmphasisFeatureValue
    sdlgle = numpy.sum(self.P_gldm / ((ivector[:, None] ** 2) * (jvector[None, :] ** 2))) / Nz
  File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
    _showwarnmsg_impl(msg)
  File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
    text = _formatwarnmsg(msg)
  File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
    msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

Computing glrlm
Initializing feature class
Discretizing gray levels inside ROI

ok, adding normaliziation seems to fix the error (at least on first sight)-- so what is not clear to me is whether normalization is a good thing to do, do you have experience on this? usually i'd obviously normalize everything in sight, but am not sure if in the radiomics domain the absolut values carry some important information. or in other words: why normalization is not turned on by default?

@aydindemircioglu Which version of SimpleITK do you have installed? (you can find this out by running pip list). An older version of SimpleITK may fix your error. This is important as these warnings can occur, also in case of a 'valid' feature extraction (that's why they're warnings, not errors).
As to normalization, it is disabled as it is not always necessary and we want to prevent users from accidentally leaving it on when they don't intend to (i.e. when it's turned on, the user explicitly configured it).
As to when to apply it: In general, I use it mainly when extracting from MR, as the gray values are relative values (and therefore less comparable between scans than say, gray values between 2 CT's, which have absolute (HU) values).

thanks for the infos on normalization, as a non-medical guy with not-so-much experience in medical imaging its very helpful to get hints from your experience. i will keep normalization then.
i had used the latest version 1.1.0 i think, i downgraded to 1.0.0, but the warning is still there. but i am confused, i added some verbose pritnting into ntgdm to see whats happening, and the denominator was zero, if i recall correctly. i will look at it again, to understand whether normalization has fixed the problem or not.
will report probably tomorrow.

I tried to reproduce the issue on mac. Testing with python 3.6.1 and SimpleITK 1.0.1 (seems to be the latest), I am unable to reproduce. If I add division by zero to the feature calculation function, I get the below, as expected, using helloRadiomics.py example from the repository:
FAILED: Traceback (most recent call last):
  File "/Users/fedorov/.pyenv/versions/3.6.1/Python.framework/Versions/3.6/lib/python3.6/site-packages/pyradiomics-1.3.0.post125.dev0+g69933c7-py3.6-macosx-10.12-x86_64.egg/radiomics/base.py", line 297, in _calculateFeatures
    yield True, feature, getattr(self, 'get%sFeatureValue' % feature)()
  File "/Users/fedorov/.pyenv/versions/3.6.1/Python.framework/Versions/3.6/lib/python3.6/site-packages/pyradiomics-1.3.0.post125.dev0+g69933c7-py3.6-macosx-10.12-x86_64.egg/radiomics/firstorder.py", line 191, in getMeanFeatureValue
    return 100./0.
ZeroDivisionError: float division by zero

The error message @aydindemircioglu reported
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

does not make sense to me - the itk prefix seems to imply SimpleITK, but there is no SimpleITK involved in the calculation. And there is no such class or function in SimpleITK if I search for it.
I wonder if something got messed up in the python package installation. Can you try installing a fresh python via pyenv, installing pyradiomics from scratch and see if you can reproduce?
Also please let us know the answers to the following:

are you using the latest pyradiomics source?
how are you using pyradiomics - can you share the code that invokes feature calculation?

thanks andrey for looking into the matter.
first, i today again started to compute features, and when i disable ngtdm everything works without problems, had binWidth=0.05 and normalization turned on. this is now on another machine, but as i myself did the installation too, its "correlated" to my other machine. i could go ahead and reproduce in an clean virtualenv, but only on  extrarequest, as i have to learn virtualevn first and i dont think it is related to the package installations. on this machine here i have python 3.6.5 and SimpleITK 1.0.1-- the latest is 1.1.0 (and i just installed it here too :D) and i usually have a recent pyradiomics working (master from monday on the other machine, here pip tells me pyradiomics==1.3.0.post69+gdffb440)
when i enable ngtdm, then the error occurs as written. i also suspect it has something to do with the contrast and range of the image, so i'd also believe that with 'finetuning' the binwidth i could probably get around the problem. but for me now disabling ngtdm is a much faster workaround.
second, to test where the error stems from, i now did  two things: a) write out the contrast (the two denorminators) in the code and b) just plainly divide by zero, as you said. the first thing i already tested when opening the issue, and i get the same thing:
Ngp*(Ngp-1): 0
Nvp: 382.0
FAILED: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 162, in calculateFeatures
    self.featureValues[feature] = getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/ngtdm.py", line 239, in getContrastFeatureValue
    contrast = (numpy.sum(p_i[:, None] * p_i[None, :] * (i[:, None] - i[None, :]) ** 2) / (Ngp * (Ngp - 1))) * \
  File "/usr/lib/python3.6/warnings.py", line 101, in _showwarnmsg
    _showwarnmsg_impl(msg)
  File "/usr/lib/python3.6/warnings.py", line 28, in _showwarnmsg_impl
    text = _formatwarnmsg(msg)
  File "/usr/lib/python3.6/warnings.py", line 116, in _formatwarnmsg
    msg.filename, msg.lineno, line=msg.line)
TypeError: itkFormatWarning() got an unexpected keyword argument 'line'

so it really seems that Ngp is 1 and as this should be the number of graylevels, i seem to have there an image+mask that becomes zero after binning (at 0.05).
ok, now, if insert a plain z=1/0 as you did, i get
  File "/usr/local/lib/python3.6/dist-packages/radiomics/base.py", line 162, in calculateFeatures
    self.featureValues[feature] = getattr(self, 'get%sFeatureValue' % feature)()
  File "/usr/local/lib/python3.6/dist-packages/radiomics/ngtdm.py", line 236, in getContrastFeatureValue
    z = 1/0
ZeroDivisionError: division by zero

but if i use z = numpy.sum(p_i[:, None] * p_i[None, :] * (i[:, None] - i[None, :]) ** 2)/0 i get the SimpleITK error again. printing out the type of this z i get <class 'numpy.float64'>. so i somehow assume that this is a class, even it looks like an usual float. so looked at my code again, and i realize that i do not convert them to numpy-- i just pass them as they are to the extractor, like this:
fv = extractor.execute(series, mask_image, l)

so maybe this is why SimpleITK comes into play? am not any kind of expert on python classes in general or SimpleITK in special. but i'd doubt that the error stems from anywhere else than an denominator that becomes in my case zero, because of some contrast/binning issues.

i'm closing the issue now, as the problem is really with the number of bincounts, it seems.


Add 'async' to Javascript tag

I could be wrong, but I would think most people would want the gist's to load asynchronously and not stop page render.
<script src="http://gist.github.com/xxx.js" async></script>

Scripts that are loaded asynchronously cannot call document.write().
The gist embed script calls document.write()
The gist embed script cannot be called asynchronously.

Thanks, @pathawks!

Thanks for the explanation @pathawks, TIL


darkmode config does not work as configured

Describe the bug
not sure if it's my fault, but the darkmode config is not working when setting to darkMode: 'media'
the classes generated are only prefixed with .dark instead of wrapped within @media (prefers-color-scheme: dark) {
clean reproduction repo here
stackblitz reproduction here
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (6) x64 Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
    Memory: 15.50 GB / 31.94 GB
  Binaries:
    Node: 17.0.1 - ~\AppData\Local\Volta\tools\image\node\17.0.1\node.EXE
    Yarn: 1.22.11 - ~\AppData\Local\Volta\tools\image\yarn\1.22.11\bin\yarn.CMD
    npm: 8.1.0 - ~\AppData\Local\Volta\tools\image\node\17.0.1\npm.CMD
  Browsers:
    Chrome: 95.0.4638.69
    Edge: Spartan (44.22000.120.0), Chromium (95.0.1020.53), ChromiumDev (93.0.910.5)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    svelte: 3.44.1 => 3.44.1
    svelte-windicss-preprocess: 4.1.6 => 4.1.6

Used Package Manager
yarn

Thanks for the report. I will try to reproduce this issue, however I don't have it in my repos.

Sorry for coming back lately. But I think you miss to define the configPath in your windi({}) call


Adding an Open in DevZero button

DevZero is a dev environment platform. Using this link, all contributors to this project will be able to use a DevZero environment as their dev workspace.
DevZero supports a free plan that individual contributors to OSS projects can utilize to make their contributions and/or to just test out the project.

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

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


Strange doi presentation with springer-mathphys

Description
In springer-mathphys, doi are prefaced by https://doi.org/, but that isn't part of the link, which looks weird.
Reproduction URL
No response
Operating system
No response
Typst version

[X] I am using the latest version of Typst

Could be related to https://github.com/typst/typst/issues/2853


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2dm70olty7/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_2dm70olty7/clone/recipe/meta.yaml:41: missing_pip_check: For pypi packages, pip check should be present in the test commands
INFO: /tmp/abs_2dm70olty7/clone/recipe/meta.yaml:50: invalid_url: https://docs.microsoft.com/en-us/python/api/overview/azure/container-registry : URL domain redirect docs.microsoft.com ->  learn.microsoft.com
WARNING: /tmp/abs_2dm70olty7/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f365cyp1ci/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_f365cyp1ci/clone/recipe/meta.yaml:41: missing_pip_check: For pypi packages, pip check should be present in the test commands
INFO: /tmp/abs_f365cyp1ci/clone/recipe/meta.yaml:50: invalid_url: https://docs.microsoft.com/en-us/python/api/overview/azure/container-registry : URL domain redirect docs.microsoft.com ->  learn.microsoft.com
WARNING: /tmp/abs_f365cyp1ci/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
Errors were found


issue with date picker / dropdown changing height when values assigned

When the value of the date picker and dropdown is empty the height is normal and as shown in the documentation.

When a value is selected the height of them seems to change and look a bit more blocky, anything I can do to fix the sizing?

Hi @thornec, thanks for spotting this! Would you mind sharing some kind of code snippet so that I can have a look at it in a bit more detail?

I am not sure about this issue  May be he has added additional library for styling that is causing conflict. Is it cause conflict with tailwind ?
I am using Vite and Tailwind
here is the screenshot

Here is my code:
https://stackblitz.com/edit/vitejs-vite-nvxrbb?file=tailwind.config.cjs,src%2Findex.css,src%2FApp.jsx,src%2Fmain.jsx,package.json&terminal=dev

hi @Junaid300, this is a specificity issue introduced by tailwinds pre-flight config. Specifically, this part:
/*
1. Correct the inability to style clickable types in iOS and Safari.
2. Remove default button styles.
*/

button,
[type='button'],
[type='reset'],
[type='submit'] {
  -webkit-appearance: button; /* 1 */
  background-color: transparent; /* 2 */
  background-image: none; /* 2 */
}

We are evaluating how we can best increase specificity for our button elements to avoid this kind of behaviour. For now, I would suggest that you first import the index.css file in your project and then the tremor.css file in your main.jsx. This should work for now.


Hello

I Have Problem

Hi there. Please submit your problems here. It would be better if you can upload  any informations when running the programme in your enviroment.
However, this repo is made only for education, not for production, which means it just work, not work well.
But I'm still going to do the best I can to help you.

Can you send me by making a video how to install it

I did everything but later there was a problem that it was not downloading


wrong batman package

I still I don't have the right batman package. A warning would be good. Change
https://github.com/3fon3fonov/trifon/blob/ecf3a143af07748ad312525c06bd4efee1207614/lib/RV_mod/__init__.py#L1399
to
        try:
           self.init_transit_params()
        except:
            print("You have probably the wrong batman packages.")

Then at least it runs (and I don't need to install it).

See #19

OK Mathias,
I just included a similar (but more sophisticated) fix. Now if you don't have batman or you have the wrong one, you should still be able to boot the ES and use the RV part including the mcmc and Nest. Samp, Orbital Evol, etc. Tell me if it works because I dont have the "wrong" batman.

https://github.com/3fon3fonov/trifon/blob/5ecd80462bc9bddfac9d9efc408331c83fda0e25/gui.py#L58
does not catch
Traceback (most recent call last):
  File "gui.py", line 55, in <module>
    bat_test = batman.TransitParams()
AttributeError: module 'batman' has no attribute 'TransitParams'

So change to:
    except (ImportError, KeyError, AttributeError) as e:

Ok. Now it is implemented and works.


Sort out whether AllowPartiallyTrustedCallers gets defined

I think the removal of System.Security.AllowPartiallyTrustedCallers assembly attribute from Windsor should be listed under "Breaking Changes" (@alinapopa)

I thought Castle Core was defining the attribute and so I was going to say it should go back in, however it appears the attribute was never defined out of the box for Castle Core.
For Castle Core:

Prior to v4 you could specify a property to get it to be defined: https://github.com/castleproject/Core/blob/v3.3.3/buildscripts/Castle.Common.Targets#L115
With the v4 work it got moved to being conditionally compiled if FEATURE_APTCA was defined so it could be enabled on .NET Core: https://github.com/castleproject/Core/blob/v4.0.0/buildscripts/CommonAssemblyInfo.cs#L51-L53

I mentioned this file already to @fir3pho3nixx in https://github.com/castleproject/Core/pull/261#issuecomment-302629087 where it got removed in a open PR.
Interesting that Windsor was always defining the attribute and then had the option to define it in the build scripts:

https://github.com/castleproject/Windsor/blob/v3.4.0/src/Castle.Windsor/SecurityAssemblyInfo.cs#L4
https://github.com/castleproject/Windsor/blob/v3.4.0/buildscripts/Castle.Common.Targets#L118

Looking at MSDN I think these two remarks are the reason APTCA got all messed up and we didn't want to always define it:

"The .NET Framework 4 introduces new security rules that affect the behavior of the AllowPartiallyTrustedCallersAttribute attribute (see Security-Transparent Code, Level 2). In the .NET Framework 4, all code defaults to security-transparent, that is, partially trusted. However, you can annotate individual types and members to assign them other transparency attributes. For this and other security changes, see Security Changes in the .NET Framework."
"Caution: The presence of this assembly-level attribute prevents the default behavior of placing FullTrustLinkDemand security checks, and makes the assembly callable from any other (partially or fully trusted) assembly."
(https://msdn.microsoft.com/en-us/library/system.security.allowpartiallytrustedcallersattribute(v=vs.110).aspx)

We should make a decision whether we want this in the code and then implement it in both Castle Core and Windsor.

I'm voting to remove all APTCA from both projects (and note it in the changelog). If someone still needs to build their build with it enabled they can just add it to the CommonAssemblyInfo.cs file and build rather than stuffing around with build properties.
/cc @alinapopa @fir3pho3nixx

I will make sure this is inactive in Core.

@jonorossi - Looks like this is already goneskies from the refactor-build branch. Should we close it?


🐛 Use providerID when set on metal3machine

What this PR does / why we need it:
Instead of always creating it from BMH UID.
Currently, after pivoting, the BMH UID has changed so the
provider IDs do not match anymore since we always used the BMH UID.
Instead, use the providerID if set in the Metal3Machine already to
avoid this issue.
Which issue(s) this PR fixes :
Fixes #88

/test-v1a4-integration

/cc @kashifest
/cc @fmuyassarov
/cc @Jaakko-Os

/lgtm


Update article.md

Typo in Dataentry Signup form
https://docs.nativescript.org/angular/app-and-screen-templates/common-screens/dataentry
Please review it.

Closes Soundug/NativeScript/docs #1414

@hdeshev This is my first contribution towards Hacktoberfest NativeScript. Please review it.


RST-5969 rails 7

Jira link (if applicable)
https://tools.hmcts.net/jira/browse/RST-5969

Closing this CI doesn't seem to like this PR


Sound request: I'd like a new hat

Describe the sound
[Describe what in-game sound you would like to see added to the resource pack. e.g. "Add a new sound for pig oinking."]
This sound would be one of the villager sounds where the villager would say I'd like a new hat
Link to sound clip
[Add a link to a Twitch clip or YouTube video (with timestamp) of Poofesure making this sound, if applicable.]
Additional comments
[Add anything else about the sound here, if applicable.]

Thanks for the suggestion @spectre729 ! The new sound is available now in Version 4.0.0


[FEATURE] Add transaction support

RFC: streamnative/community#2
Tasks

[ ] Transaction Coordinator

[x] producer id manager #372
[x] producer fence
[x] transaction metadata #295
[x] add partitions to transaction #295
[x] end transaction #295
[x] transcation marker channel handler #295
[ ] transaction log

[x] Consumer Coordinator

[x] transaction offset commit #365
[x] write transaction marker #365

[ ] Topic Partition Leader Broker

[x] find transaction coordinator #295
[x] send transaction message #295
[x] write transaction marker #295
[x] read isolation #295
[ ] aborted index log

[ ] Test

[x] basic produce transaction messages and consume test (read_committed, read_uncommitted) #295
[ ] Kafka client test migrate

Hi @gaoran10 Is there any unassigned issue which I would like to pick up.

Hi @gaoran10 Is there any unassigned issue which I would like to pick up.

I'm working on processing the producer state snapshot and recovery. Could you help check that is there any more transaction tests in Kafka? Migrate them to KoP first if exists.
I think there are many codes that need to refine, if you find anything about the transaction need to do, you could open an issue to track the task, and this will help us to sync status. Thanks.


Table component sample code compiler error

What is the expected behavior?
none complier errors.
What is the current behavior?
official: https://material.angular.io/components/table/overview
line: 16
  @ViewChild(MatPaginator, {static: true}) paginator: MatPaginator;

errors:
Argument of type '{ static: boolean; }' is not assignable to parameter of type '{ read?: any; }'.   Object literal may only specify known properties, and 'static' does not exist in type '{ read?: any; }'.
What are the steps to reproduce?
https://stackblitz.com/angular/egkyqnreoxr?file=app%2Ftable-pagination-example.ts
Which versions of Angular, Material, OS, TypeScript, browsers are affected?

angular 7.2.11
material 7.3.6
MacOS 10.13.6
TypeScript 3.2.2
IDE IntelliJ Idea 2019.1

Is there anything else we should know?
none

Duplicate of https://github.com/angular/material2/issues/15632.

It only works like this:
@ViewChild(MatPaginator) paginator: MatPaginator;

PR 30948 should be the solution for your problem.


Resolve issue of duplicate entries in Dicover tab

Issue
Some time you get duplicates in the discover tab.
Analyse
It hapen when google search api get more then 1 entry for a device/country/keyword.
It is because the page is included in the dimentions of the google search console api call.
Solution
I have not change the api call because the data is stored locally and used also in other tabs (with the page dimension).
I grouped and sumerizing the stats in the Discover tab.
Remark : i included also an update of  dev dependencies of react in package.json
(i actually, dont know how to make a separate pull request for it)

I make the changes

This PR looks great, anything more to do here?

This PR looks great, anything more to do here?

No it's ready, waiting for review


flutter_controller_->engine()->SetNextFrameCallback() never been called, in windows desktop release build

Release build will startup once. When you close the window and try to start it again, you will find that the window no longer appears. In the task manager  you will see many of its zombie processes. If you start it with gdb or lldb it will work every time.  Weird thing its't it.
#119415

Closing this as a duplicate of #119415.
Feel free to share your findings in the main issue.
Thank you


Is it possible to use std / println?

Hello, first thank you for this awesome project!
I want to create a simple terminal application. Is it possible to simply log to screen? Or do I have to stick with the graphics example.
Thanks

Since we still don't have official/std support (although it's on its way), only ways of logging information are through the current graphics support (which isn't the best as it essentially uses CPU rendering) or logging via diag/macros

Thanks for the clarification. These are some amazing news! Would this allow us to leverage most of the crates?

Thanks for the clarification. These are some amazing news! Would this allow us to leverage most of the crates?

That is part of the goal :)


fix: update point coords scaling for mask

This fixes the point coord scaling to match to kijai segment anything 2 point coords computed for the model.
Using sample image, the coordinates computed by both nodes were:
kijai:  tensor([[[716.4031, 219.1440]]], device='cuda:0')
realtime:  tensor([[[716., 219.]]], device='cuda:0')

LGTM.  Thanks!


Update version to match published version

TBR=@arv

This is to fix an issue created in the last publish.
FWIW I upgraded my npm from something in 1. range to 2.3 and this time make git-update-publish worked just fine.

LGTM
Not clear why this was needed though?

Manual updating for the last release was inaccurate I believe.


Send attendance reports to the CoC automatically

Weekly, Saturday at midnight, was approved by Christen

Still name/email/major though?

Yes, the same report as the current Nova export.


eirini-controller EATs broken

See: https://jetson.eirini.cf-app.com/teams/main/pipelines/eirini-controller/jobs/run-eats-tests-regular/builds/16.1

It's fine if you deploy first!


Is this]]

Hi there,
I like this project. It has quite interesting non intrusive approach with updating images tags in GitOps fashion. However, I am a bit worried about release cycle (last release is from 21.01.2023).
Can you provide more information regarding the current state of the project? Are there sufficient contributors to ensure its long-term viability? Specifically, in which stages of software development do you require the most active participation?
Cheers

The project seems to be stagnating.

Hey, the release has been created. There are multiple maintainers supporting the project.
We will try to create releases each 3 - 4 months , same as ArgoCD doing


border-color isn't changing on github.com

On the page: https://github.com/vtnorton/TrueDarkMode/issues the classes: .border-left, .border-bottom, .border-right, isn't making any changes.

#6 the same issue


[QUERY] Release new version of Microsoft.Azure.WebJobs.Extensions.EventGrid

Library name and version
Microsoft.Azure.WebJobs.Extensions.EventGrid 3.0.x
Query/Question
I recently reported an issue with Microsoft.Azure.WebJobs.Extensions.EventGrid version 3.0.0 (#25810). This was fixed in #25813, but I am wondering how long we need to wait until a new release is available so we can get our issue fixed. I didn't really find any information on how you usually manage new releases. If we have to wait long for a new release of Microsoft.Azure.WebJobs.Extensions.EventGrid we need to work our way around our issue some other way.
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @smafre,
We generally release new versions the second week of each month, so we'd be looking at the week of Jan 10th. Would this work for your timelines?

@JoshLove-msft We need it as soon as possible. If the release won't be out until the week of Jan 10th we need to work our way around the issue some other way.

Released 3.0.1 - https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.EventGrid/3.0.1
Please let us know if you are still seeing the issue.


Fix the default use_registry value

use_registry defaults to try in BinderHub
https://github.com/jupyterhub/binderhub/blob/03545a1587f2d781ff4934beac8b8b8a19280754/binderhub/app.py#L261-L270
but the Helm chart implicitly defaults to False:
https://github.com/jupyterhub/binderhub/blob/03545a1587f2d781ff4934beac8b8b8a19280754/helm-chart/binderhub/templates/deployment.yaml#L68-L76
Which will lead to a broken deployment.
Also includes a commit to fix the CI upgrade/diff check.

Ah, so c.BinderHub.use_registry is one of those software configurations that is required to be known also during chart template rendering. In z2jh c.JupyterHub.base_url is a configuration like that as well.
A big plus if we can make that explicit in comments going onwards as that is a very relevant piece of understanding for refactoring work in general.


How to use this App

Hello how to use this App?
If this is pure PHP app then what is the document Root and what is the nginx or apache settings, or if this NodeJS app then how to run this and what will be the nodejs port?

Hi Umar,
This a PHP. A Laravel application to be precise.
After cloning the repo, it's best to follow the official Laravel documentation on how to install and configure everything.
We also have a short – but probably not beginner friendly – documentation on how to self host the app.
Regarding configuring a web server, please checkout this documentation section about "Public Directory".
(The webserver must point to public/index.php)

I want to update the documentation soon, to be more beginner friendly and to make the app more accessible for more users.

Thanks for you reply, I will look into it


[monitor-ot-exporter][test] remove 15 minutes timeout limit

This build pipelines occasionally went over 15 minutes limit. This PR removes the limit, so that default of 60 minutes is used.

API change check for @azure/monitor-opentelemetry-exporter
API changes are not detected in this pull request for @azure/monitor-opentelemetry-exporter


Recursive lazy-loaded TreeView is broken in Clarity 1.1.2

Describe the bug
When opening an expandable node in a recursive lazy-loaded TreeView an error is thrown and logged in the console:
Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'ngIf: true'. Current value: 'ngIf: false'.
How to reproduce

Go to https://stackblitz.com/edit/clarity-light-theme-v1-0-vppqhq
Click on node b to expand it
See error in console

Expected behavior
No error in the console.
Versions

Clarity: 1.1.2

Additional notes
This issue does not occur in Clarity 1.1.1. I assume this is related to either https://github.com/vmware/clarity/pull/3211 or https://github.com/vmware/clarity/pull/3227 (looking at the changelog of 1.1.2)

Yes, I see an error in your stackblitz. But that error is totally different than what you are describing above. It's asking you to define your getChildren parameter function.

Argh, sorry. I must have saved to the wrong StackBlitz. Will reopen when I get the repro up and running again.

@Shijir I've updated the Stackblitz. Can you reopen the issue? I've narrowed the issue down to returning promises from the getChildren call.

I'll just create a new issue.


Feature Request: Provide extra responsive design prefix/modifiers

@antfu hello 👋
So In my opinion, I think it would be nice to have some extra responsive design prefix for utility classes like provided in windicss.
Some what of a modifier for the responsive prefixes.
Take lg as an example
<lg => smaller than this breakpoint
@lg => exactly this breakpoint range

Example Usage
<lg:p-2 @lg:p-3
To generate
@media (min-width: 1024px) and (max-width: 1279.9px) {
  .\@lg\:p-3 {
    padding: 0.75rem;
  }
}
@media (max-width: 1023.9px) {
  .\<lg\:p-2 {
    padding: 0.5rem;
  }
}

Example/idea gotten from windicss

You are looking for https://uno.antfu.me/?s=lt-lg:p-2 and https://uno.antfu.me/?s=at-lg:p-2

Oh awesome. Thanks. I didn't know this exists already. I wish there was a way to alias the gt,  lt and at to >, '<' and @ respectively🥲. I kind of prefer that syntax more


Removing Thought Process from UI

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

How can we remove "thought process" from the UI? Thanks!!!

OS and Version?

macOS

azd version?

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

This branch shows how to do it:
https://github.com/Azure-Samples/azure-search-openai-demo/compare/main...pamelafox:azure-search-openai-demo:rm-thoughtprocess?expand=1
You need to remove the icon as well as the tab.

Thank you, Pamela!


Combine docker-compose.yml files in TI

DevEx/OpEx
Update base docker-compose TI to stand up the db as well as the TI app in Docker instead of having to run 2 commands
Tasks

[ ] Something.

Additional Context

https://flexion.slack.com/archives/C055XTF22B0/p1713382055379129
Add any other context or screenshots about the work here.

Starting


Support Age encrypted files

Here's the spec
https://github.com/C2SP/C2SP/blob/main/age.md

Fixed in #60


fix flattening

This issue was brought up in our partner slack channel:
Issue:
we were properly flattening any compound objects like nested arrays, objects ONLY if it was nested under an object.
However, top level arrays that contained objects were being sent as [object Object] such as the products array from Completed Order events.
I had to catch the array of objects before the toString.call(value) !== '[object Object]' if test because otherwise, products array would fall in that block, while objects of objects/arrays were not and thus properly flattened.
This PR should properly stringify the entire nested array and also continue to take care of any objects that include compound objects.

[ ] server side PR

@f2prateek

Current coverage is 90.90% (diff: 100%)

Merging #8 into master will increase coverage by 0.43%

@@             master         #8   diff @@
==========================================
  Files             1          1
  Lines            84         88     +4
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             76         80     +4
  Misses            8          8
  Partials          0          0

Powered by Codecov. Last update 066e120...8c1ba3d

LGTM


Store build.log in log directory

With this commit we move Rally's build log from a race-specific
directory to its log directory. This file captures Gradle's output when
users are benchmarking a source build of Elasticsearch. By moving this
file to the log directory it is better visible to users (already in the
same location as other log files).

Marked as breaking as the build log file moves and thus it may have an impact on users.

Thanks!


Add installation instructions to README: Issue #488

This PR adds the Installation section to the README as written in #488.

Great, thanks!


Generate the documentation from product usage

Generate the public documentation of usage

@kkazmierczyk  Please review: https://github.com/IBM/javacore-analyser/wiki

I made few minor changes. Except that it looks good for me. Closing as fixed.


Default Values

For custom scripts (ie. not viewer, treater), it should be clear which config options they are taking from defaults.py vs ones they are overriding themselves.
This brings up the interesting design decision of whether to use context management (ie. a big dictionary of all config options, or in this case the Config class), rather than having everything as modularised as possible.
I think it has been clearly better to modularise :
For functions that only need one particular config option, they accept the ones they need as stand-alone params.
A big example was adding bold support for all colour printing.
Yes it was a pain to implement, but it made functions more isolated.
It also makes it possible to test without needing the whole chunk of the config class.

Ideally, it should be possible to write a configuration file for these temporary scripts.
Although, the problem is that their paths are generated at run time.
Potential options:

Write a config (ie. Stateful), but then leave the path names as filler. No, this violates the invariant that in order for a config to be made, its file needs to exist. Also, Stateful requires a config name which is dependent on the $MVE_CONFIGS environment variable.
Just make a function that sets the config options for all impermanent scripts.

Ick
It does slightly bug me that if the config changes, it will get pushed in the repo. but so be it.

Done for moment.py in 1bf3d6f.
Now, just need to do it for focus.py.

Done for focus in 2bda136


Distinct college/university icon

Fixes #694. Changes the rendering for amenity=college and amenity=university (in OMT, class=college + subclass=college/university) to a mortarboard cap-style icon: . Previously, these were rendered as a generic school icon ; this schoolhouse icon is now reserved for amenity=school and amenity=kindergarten.
I think the "higher ed"/"schools for adults" vs "schools for children" is a useful distinction for the map to make. Meanwhile, the distinction between an OSM college and university is a bit fuzzy in practice IMO, so this PR renders both tags the same. In #694, while there were multiple potential icons in various US map samples, the consensus was that a mortarboard cap was the most recognizable symbol of institutions of higher education. The new legend entry is "College or university", whereas the schoolhouse icon retains "School". I think this is not too confusing, but I'm open to suggestions.
The icon itself is a modified version of the maki symbol. I'm open to modifying the dimensions/length ratios/style/etc.
I've added rendering to begin at z14, one zoom level out compared to most other POIs, since colleges and universities can be quite important local destinations (I think that eventually starting zoom levels for POIs might need to be reconsidered more holistically, but that's out of scope for this PR). Rendering at z<14 is not currently possible, as non-transport POIs only appear in the tiles at z14 (https://github.com/openmaptiles/openmaptiles/issues/387). In the future, it might also be good to render these objects as areas as well, but I also leave that out for now.
Samples:
UCLA z14 (localhost link):

Note that the Anderson School of Management is tagged as amenity=university, which may or may not be a tagging error.
UCLA z15 (localhost link):

Indiana University Bloomington (localhost link):

The icon renders near the center of the university polygon. This may or may not be equivalent to the main activity center of the campus. This problem could be helped, though not really entirely solved, by rendering the area as a boundary.
City College of San Francisco (localhost link):

This is a two-year community college, the predominant use of amenity=college I anecdotally observe in the US. I see these institutions are more close to a university than they are to e.g. a high school, so I think it makes more sense to render them together with universities.
Boston/Cambridge, MA (localhost link):

Cambridge, UK (localhost link):

Again, these seem like tagging errors to me, though the UK university/college system is incredibly convoluted so I wouldn't go in and change the tags myself. But this seems at least an improvement over rendering them the same as elementary schools.

I think the original filename of poi_mortarboard is better. As the number of icons grow, they'll be easier to understand in the code if they're closer in description to what's in the icon rather than what the icon represents.

Sorry for the slowness on getting back to this. After the discussions on here and slack I don't think there's anything holding this design up from being merged

Looks great, thanks!


adding Canal to CNI compatibility matrix

Special notes for your reviewer:
Thx !

Signed!

Thank you!


Add HTTP transport

This PR adds HTTP transport to goflow2 allowing it to send data to any existing observability tool or application that accepts a JSON array over an HTTP endpoint.
Here is an example.
./goflow2 -transport=http \
  -transport.http.destination=http://localhost:5080/api/default/gflow3/_json \
  -transport.http.batchSize=1000 \
  -transport.http.auth.header=Authorization \
  -transport.http.auth.credentials="Basic cm9vdEBleGFtcGxlLmNvbTpDb21wbGV4cGFzcyMxMjM="

Implements https://github.com/netsampler/goflow2/issues/276

Hello,
Than you for your contribution but unfortunately I have to reject new transport/formats since I do not have the ability to maintain them.
In #276 I also suggested an alternative using other tools. I do not think it should be achieved inside this tool: retry/failure scenarios are difficult to implement.
The amount of people this would benefit is unclear and has not been discussed. Also please refrain from advertising products, especially in the README.
On the code side: this should have tests and support contexts. There are no protection against slow responses, no async query, no keying and furthermore this hardcodes JSON while the format can be anything the user wants (protobuf, text).


Converting a json import that doesn't work as expected

Description
ts-bridge converts json imports to .json.cjs or .json.mjs after compilation, which is incorrect behavior.

require("./data.json.cjs") // should be require("./data.json")

Steps to reproduce

https://github.com/Innei/ts-bridge-repro
Refer: https://github.com/MetaMask/providers/issues/339

This is fixed in<EMAIL_ADDRESS>Thanks for reporting it!