TextField with buildCounter error-state rendering issue

Steps to Reproduce

Execute flutter run on the code sample

Expected results:
Because the number of characters in the text field are greater that the value of maxLength, the text field should show an error highlight.

Actual results:
Text field does not render error highlight

NOTE: comment out the buildCounter: line from the TextField and it will be rendered as expected.
This behaviour has been seen on:

Flutter 3.0.5
Flutter 3.3.8 (current stable)
Flutter 3.6.0-7.0.pre.18 (current master, 2921ca0c48)

I only tested on macOS 13.0.1, but I suspect this is the same on all platforms.

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

InputCounterWidgetBuilder buildCounterFor(String currentValue) =>
    (context, {required currentLength, required isFocused, maxLength}) =>
        Text('$currentLength / $maxLength');

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<StatefulWidget> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final _controller = TextEditingController();

  @override
  void initState() {
    super.initState();
    _controller.text = 'More than 1 character';
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Padding(
          padding: const EdgeInsets.all(8.0),
          child: TextField(
            controller: _controller,
            maxLength: 1,
            buildCounter: buildCounterFor(_controller.text),
          ),
        ),
      ),
    );
  }
}

Logs
flutter doctor:

[✓] Flutter (Channel master, 3.6.0-7.0.pre.18, on macOS 13.0.1 22A400 darwin-arm64, locale en-SE)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[!] Android Studio
    ✗ Unable to find bundled Java version.
[✓] Android Studio (version 2021.2)
[✓] IntelliJ IDEA Community Edition (version 2022.2.2)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

Hi @AdamVe, thanks for filing the issue. This issue is reproducible on the latest stable and master channels.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.8, on macOS 13.0 22A380 darwin-x64, locale en-VN)
    • Flutter version 3.3.8 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 52b3dc25f6 (23 hours ago), 2022-11-09 12:09:26 +0800
    • Engine revision 857bd6b74c
    • Dart version 2.18.4
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 70.0.5
    • Dart plugin version 222.4167.21

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (3 available)
    • iPhone 14 Pro Max (mobile) • 332079AF-E895-4685-910E-7B1E18B0C6B8 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 13.0 22A380 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.6.0-7.0.pre.17, on macOS 13.0 22A380 darwin-x64, locale en-VN)
    • Flutter version 3.6.0-7.0.pre.17 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 182d6c4c94 (2 hours ago), 2022-11-21 19:51:06 -0500
    • Engine revision ddf6a20b86
    • Dart version 2.19.0 (build 2.19.0-414.0.dev)
    • DevTools version 2.19.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 70.0.5
    • Dart plugin version 222.4167.21

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0 22A380 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Hi @justinmc, in our code we are now handling the error state ourselves when the length is greater than maxLength (link to the commit). We cannot use the default input counter because we need to count the number of bytes of the input.
I did more exploration and I am attaching it here for reference:
I found out the following - the decoration behaviour is different depending on the presence of custom counter: without using a buildCounter, it will get red when the length is greater that maxLength, when using buildCounter it will stay black. See the video and a new sample code I attached. I think the decoration behaviour should not be affected by using a buildCounter, because the build counter only builds the widget which is placed under the text field.
Note: in the new code sample I use decoration with outline border to emphasize the issue. You can remove the decoration: to get the default looks of the TextField.
https://user-images.githubusercontent.com/1954891/207817136-0ef497b9-fb6d-4244-883b-77b411919c79.mp4

Updated code sample
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() {
  runApp(const MyApp());
}

InputCounterWidgetBuilder buildCounterFor(String currentValue) =>
    (context, {required currentLength, required isFocused, maxLength}) {
      var style = currentLength > maxLength!
          ? Theme.of(context).textTheme.caption?.copyWith(color: Colors.red)
          : Theme.of(context).textTheme.caption?.copyWith(color: Colors.green);
      return Text('Custom counter: $currentLength/$maxLength', style: style);
    };

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<StatefulWidget> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final _controller = TextEditingController();
  bool _useCustomCounter = false;

  @override
  void initState() {
    super.initState();
    _controller.text = 'More than 5 character';
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Padding(
          padding: const EdgeInsets.all(8.0),
          child: Column(
            crossAxisAlignment: CrossAxisAlignment.center,
            mainAxisAlignment: MainAxisAlignment.center,
            children: [
              Row(
                children: [
                  Checkbox(value: _useCustomCounter, onChanged: (newValue) { setState(() {
                    _useCustomCounter = newValue ?? false;
                  });}),
                  const Text('Use custom counter')
                ],
              ),
              TextField(
                controller: _controller,
                maxLength: 5,
                maxLengthEnforcement: MaxLengthEnforcement.none,
                decoration: const InputDecoration(
                  border: OutlineInputBorder(),
                ),
                buildCounter: _useCustomCounter ? buildCounterFor(_controller.text) : null,
              ),
            ],
          ),
        ),
      ),
    );
  }
}


Re-Assess setting global config

#278 introduced the notion of setting a global config:
self.goog.logLevel = self.goog.LOG_LEVEL.verbose

This isn't overly clean or safe. Should consider if there is a better and what it is.

Will be fixed in V3.


Improve decommissioning, recommissioning, and recovery of killed nodes

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwchkdQkRUw6hZ3z/recuzwzDMoLDci14t?blocks=hide
PM: @awoods187
Eng: @knz, @andreimatei

@knz I have some questions about this work (please redirect me as needed):

Based on my reading of the related CRDB issues in Airtable (copied below for reference), it seems like this work falls in the category of "make decommissioning etc. magically work better" and does not necessarily affect user-facing docs.  Do you agree with that assessment?
Based on the fact that most of the issues below are still open, and given their likely lack of documentation impact, I'm inclined to close this docs issue as there is not (yet) anything concrete to take action on. Do you agree with that assessment?

/cc @johnrk FYI
Related CRDB issues (copied from Airtable):

https://github.com/cockroachdb/cockroach/issues/36676
https://github.com/cockroachdb/cockroach/issues/36583
https://github.com/cockroachdb/cockroach/issues/36623
https://github.com/cockroachdb/cockroach/issues/35890
https://github.com/cockroachdb/cockroach/issues/36397
https://github.com/cockroachdb/cockroach/issues/35938

I agree this air table entry does not seem to require doc changes.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

I agree this air table entry does not seem to require doc changes.

Thank you!  In that case I'll close.


strongswan does not like the modules to be compiled as part of kernel…

…, make them loadable modules. aws operates the ipsec tunnels in ikev1 mode, enabled the conifiguration flags for them

closing this pull request.


Added Toastify Meassage

Hello Project Admin
I Added Toastify Message - Solved #607
Kindly Please go through this PR @himanshu-03
I Created same like in Before Video

I will again raise PR after solving the issues Sorry for inconvenience @himanshu-03

I will again raise PR after solving the issues Sorry for inconvenience @himanshu-03

You need not create anther PR you can push your changes to this PR itself.

I will again raise PR after solving the issues Sorry for inconvenience @himanshu-03

You need not create anther PR you can push your changes to this PR itself. Also, sync your repo with the latest changes of our repo.

Merge the conlicts which arose.

@himanshu-03 I'm new to Contributions that's why I had doubts in these syncing and conflicts but I will try as you said

@himanshu-03 I'm new to Contributions that's why I had doubts in these syncing and conflicts but I will try as you said

sure thing @sailaja-adapa !
you can give it a try otherwise lmk

Yeah okk @himanshu-03

@himanshu-03 It is not allowing me to resolve conflicts why??

yeah okk @himanshu-03 Thank You :)


Release namespace in conjunction with labels selector

I came across an odd behavior with respect to supplied namespaces in conjunction with labels selectors.
Assume this helmfile.yaml
repositories:
- name: incubator
  url: https://charts.helm.sh/incubator
---
releases:

- name: a-release
  chart: incubator/raw
  namespace: EXPECTED-namespace
  labels:
    app: raw

Then supplying the namespace through -n yields below output:
$ helmfile -n UNEXPECTED-namespace list

NAME     	NAMESPACE         	ENABLED	LABELS 	CHART        	VERSION
a-release	EXPECTED-namespace	true   	app:raw	incubator/raw

However, behavior is changed when using above command but also including a label selector:
$ helmfile -n UNEXPECTED-namespace -l app=raw list

NAME     	NAMESPACE           	ENABLED	LABELS                                                         	CHART        	VERSION
a-release	UNEXPECTED-namespace	true   	app:raw,chart:raw,name:a-release,namespace:UNEXPECTED-namespace	incubator/raw

Expectation is that the release's namespace is not changed due to command being used with a label selector or not.
Thoughts?

@mumoshu any thoughts on this?

@gakesson I think you should raise the ticket again in new repo. This repository is not active anymore.


Combining Kicad and Skidl part libraries

I am not sure what I am doing wrong.
My default tool is KICAD and my search paths are like so:
lib_search_paths[KICAD].append('../library/snapEDA')
lib_search_paths[SKIDL].append('../library/skidl_lib')
lib_search_paths[KICAD].append('/usr/share/kicad/library')

in the SKIDL search path the part definition is in a file called gamete_lib.py.
The error I get is:

WARNING: Could not load KiCad schematic library "gamete", falling back to backup library.
Traceback (most recent call last):
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/tools/kicad.py", line 60, in _load_sch_lib_
    f, _ = find_and_open_file(filename, lib_search_paths_, lib_suffixes[KICAD])
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/utilities.py", line 290, in find_and_open_file
    logger, FileNotFoundError, "Can't open file: {}.\n".format(filename)
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/utilities.py", line 820, in log_and_raise
    raise exc_class(message)
FileNotFoundError: Can't open file: gamete.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "gamete.py", line 123, in <module>
    footprint='Package_TO_SOT_SMD:SOT-353_SC-70-5_HandSoldering',
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/Part.py", line 141, in __init__
    raise e
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/Part.py", line 131, in __init__
    lib = SchLib(filename=libname, tool=tool)
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/SchLib.py", line 99, in __init__
    load_func(filename, skidl.lib_search_paths[tool])
  File "/home/alexander/.local/lib/python3.6/site-packages/skidl/tools/kicad.py", line 64, in _load_sch_lib_
    filename, str(e)
FileNotFoundError: Unable to open KiCad Schematic Library File gamete (Can't open file: gamete.
)

The error looks like it is searching for a KICAD libary file. Do I have to change the default tool every time I search for a part that is in the other supported type? Skidl found previous Kicad parts that I instantiated.

Trying my own suggestion didn't work either.
I made the repo public and pushed it in it's failing state. I don't understand why the library isn't being found.
To build you have to cd into this directory:
https://github.com/vegecode/Gamete/tree/master/pcb/skidl
and use command python3 gamete.py
Can someone help me understand why i am getting the above error about the file not being found?

I tried your code and found these errors:

Instead of calling your library gamete_lib.py, you'll need to call it gamete_sklib.py.
When you access the library, you'll have to do it like this:

led_driver = Part(
        'gamete',
        'TPS61169',
        tool=SKIDL,
        manu='Texas Instruments',
        part_no='TPS61169DCKR',
        footprint='Package_TO_SOT_SMD:SOT-353_SC-70-5_HandSoldering',
)

or like this:
led_driver = Part(
        'gamete_sklib.py',
        'TPS61169',
        tool=SKIDL,
        manu='Texas Instruments',
        part_no='TPS61169DCKR',
        footprint='Package_TO_SOT_SMD:SOT-353_SC-70-5_HandSoldering',
)

In gamete_sklib.py, you'll need to change pin functions from things like Pin.PWROUT to Pin.types.PWROUT. (I'll need to fix SKiDL to allow the shorter version of pin functions.)
On line 125 of gamete.py, prepend gen. to Diode_SMD to access the part inside the generic_parts file.

After making these changes, I was able to get your code to compile. There were a lot of unconnected pin warnings and such, but you probably expected those.

Thank you very much.
I figured there was a naming convention I wasn't aware of.
On Wed, Aug 7, 2019, 7:25 PM xesscorp<EMAIL_ADDRESS>wrote:

I tried your code and found these errors:

Instead of calling your library gamete_lib.py, you'll need to call
it gamete_sklib.py.
When you access the library, you'll have to do it like this:

led_driver = Part(
'gamete',
'TPS61169',
tool=SKIDL,
manu='Texas Instruments',
part_no='TPS61169DCKR',
footprint='Package_TO_SOT_SMD:SOT-353_SC-70-5_HandSoldering',
)
or like this:
led_driver = Part(
'gamete_sklib.py',
'TPS61169',
tool=SKIDL,
manu='Texas Instruments',
part_no='TPS61169DCKR',
footprint='Package_TO_SOT_SMD:SOT-353_SC-70-5_HandSoldering',
)

In gamete_sklib.py, you'll need to change pin functions from things
like Pin.PWROUT to Pin.types.PWROUT. (I'll need to fix SKiDL to allow
the shorter version of pin functions.)
On line 125 of gamete.py, prepend gen. to Diode_SMD to access the
part inside the generic_parts file.

After making these changes, I was able to get your code to compile. There
were a lot of unconnected pin warnings and such, but you probably expected
those.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xesscorp/skidl/issues/64?email_source=notifications&email_token=AJOF5C2LUPBOW4BELB35K6LQDNRXHA5CNFSM4IJ3X62KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32CCCI#issuecomment-519315721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJOF5CYTFLEMJVBIFLNSZALQDNRXHANCNFSM4IJ3X62A
.

https://github.com/xesscorp/skidl/blob/729eb362997228dbeb0c81a529920b064662cfcd/skidl/libs/74xgxx_sklib.py#L9
About the Pin.types.PWROUT, are these files just bit-rotted?


No need in RVM overlaps

P-ext does not require SRL/SRA while it is represented in I extension.
P-ext does not require regular MUL while it is represented in M extension.
There is no logic in requiring some "special" mul while not requiring "regular" ones.
P-ext spec should just say that M extension is mandatory. Requiring some specific mul is redundant.

Yes. It is a bit redundant. I will fix it. Thanks!

Removed Zmpmo in b2fffab.


Azure Setup Guide / Example

The Azure Setup Example has been started but is still WIP.
Some help, especially from some Azure Experts would be highly appreciated!
https://github.com/J12934/juicy-ctf/blob/master/guides/azure/azure.md

Hey there. So I'm new to Azure but I took the time to try and solve this and here is what I did for anyone that comes along after me.
Here is the yaml for the LB:
kind: Service
apiVersion: v1
metadata:
name: multi-juicer-loadbalancer
spec:
type: LoadBalancer
selector:
app.kubernetes.io/instance: multi-juicer
app.kubernetes.io/name: multi-juicer
ports:
- name: http
protocol: TCP
port: 80
targetPort: 3000
save that to do-lb.yam
kubectl create -f do-lb.yam
You can check on this with:
kubectl describe services multi-juicer-loadbalancer
This should create an external IP for accessing your multi-juicer in Azure after you have followed the rest of the instructions.
When done do:
kubectl delete -f do-lb.yaml
helm delete multi-juicer

Nice 👍, thanks @c0pp3r
Do you know if there is a easy way to set up https & custom domains for the azure loadbalancers?

Nice 👍, thanks @c0pp3r
Do you know if there is a easy way to set up https & custom domains for the azure loadbalancers?

Apologies for the late response. I honestly haven't tried at this point. I would imagine you could handle that somewhere in azure but would have to do some digging.

Azure guide was update to include external connection, but the guide doesn't show how to set it up using https.
Any help / changes on that front would be extremely welcome 🙏

I've removed the WIP warning from the Azure Guide now 👍
I'll keep the issue open so that we can keep discussing further problems and improvements here if they come up.


DS-154: Refactor AvalancheGo to build/maintain/validate sections

Can we put the postman collection within the AvalancheGo APIs section?
Also, can we change the phrase AvalancheGo Server Software to either just AvalancheGo or AvalancheGo Node?


Cannot Load nuxt-fontawesome...

https://github.com/Qonfucius/nuxt-fontawesome and this nuxt-fontawesome?

Also the setup and usage is very confusing. Could you consolidate it into one piece? Thanks!

The only way to get it working was to import FontAwesomeIcon again in my component .vue file... Any reason why this may be happening? Thanks!
import FontAwesomeIcon from '@fortawesome/vue-fontawesome'
export default {
  components: {
    FontAwesomeIcon
  },
}

@rlam3 Hi there!
Working example should be like this:
module.exports = {
 /* Some other stuff */

  modules: [
    'nuxt-fontawesome',
     /* Some other modules */
  ],
  fontawesome: {
    imports: [
      {
        set: '@fortawesome/fontawesome-free-solid'
      }
    ]
  },
  build: {
    extend (config) {
       /* Tweak build if needed  */
    }
  },

Not inside  build: {, like in your example. That's why you got a problem with importing FontAwesomeIcon. Also, big thanks for pointing at my mistakes with docs, fixed that.
Happy coding!

Hey Vaso2 - thanks so much for creating this plugin!
For anyone who may be playing with the development branch of vue-fontawesome you'll get this same error. To fix it the plugin file can be adjusted from:
import FontAwesomeIcon from '@fortawesome/vue-fontawesome'
to:
 import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome'
Hoping to save someone else time who may also be poking around at things.
Thanks again!


Multiple key presses not registering - debouncing issue?

I have successfully built a yampad and all keys are working, including keys across multiple layers. However, when I rapidly press any of the keys the second and subsequent key presses are not being registered.
Is this a firmware issue or a hardware one? My instinct is that this is a debouncing setting to avoid multiple key presses when you intend only one. However, the current setting means that the numpad is not very usable.

Hi,
have you tried changing the debouncing delay in QMK? Does it improve?

Good call, this was the reason in the end. I used a specific debouncing method (sym_eager_pk) and changed debounce to 2 ms from 5 ms. Now the numpad is a dream to type on. All the firmware files are in https://github.com/Daveyr/yampad. I can issue a pull request if useful?

Glad to hear it. I would happily accept a PR on my qmk firmware fork if you are so inclined.


Fedora uses /usr/libexec/ not /usr/lib/libexec

(as discussed in matrix)
https://github.com/OpenVoiceOS/ovos-buildroot/blob/bfdc33ae1a32912f2630ea39de09ef159f07a3e5/buildroot-external/package/kf5-kconfig/kf5-kconfig.mk#L29
On my systemd (Fedora 37) this file is in /usr/libexec/ not /usr/lib/libexec.  Maybe we could try both?

Lol, just wanted to quickly create an issue such that I don't forget.
Great to have you onboard! You know the drill.

What about using automake to generate the makefile?

No longer needed / an issue


ClassNotFoundException: is.hail.io.bgen.LoadBgenPartition

Hi,
I was trying to run the following snippet on the cluster setup with this repo
ds = hl.import_bgen(
    BGEN_FILE,
    entry_fields=ENTRY_FIELDS,
    sample_file=SAMPLE_FILE
)

ds.write(MATRIX_PATH)

but I'm getting ClassNotFoundException: is.hail.io.bgen.LoadBgenPartition (Hail version: 0.2.13-b1007cadf2bb).
It is not possible to perform any operation on BGENs.
Any solution?

Apparently hail-all-spark.jar and hail-python.zip weren't copied on the worker nodes and somehow scp failed silently (?)

Hi @Angelogeb,
Was this solved? I noticed that the hail-all-spark.jar and hail-python.zip files sometimes are missing (Hail did not compile) but I haven't found out why as the compilation simply fails. This error coincidentally started to occur after the Hail upgrade to Spark 2.4, we use Spark 2.3.0, but again I really haven't found a pattern as it doesn't happen all the time. However, this is a very easy fix. In case the .jar and .zip files are missing, login to the master node, cd into /opt/hail-on-AWS-spot-instances/src/ and execute sh hail_build.sh to re-compile Hail. This operation takes 3-4 minutes and then both the .jar and .zip files should be available at the HOME directory.
You can always go to the log (/tmp/cloudcreation_log.out) and check for output and errors.
I hope this helps.

Hi,
Yes. In my case it wasn't the build that was failing but the scp of the jars to worker nodes.
I'm currently having another issue: the same code (and data) that was running in previous versions of hail/spark is running out of memory with the current setup (cluster launched through this repo and hail cloned from master).
Any idea on what's going on and do you plan to upgrade the scripts for newer versions?

Hi @Angelogeb,
If you are able to successfully spin your cluster (with Hail installed) but the memory issue you are facing occurs after executing a Hail command, then the issue is on the cluster setup. To fix this you should either increase the size of your cluster (more workers) or the instance type for your worker nodes (or even your master node). The instance types listed in the config file of this repo are just suggested and you can always change them to your convenience.
You may be executing a task that becomes memory intensive (like saving a big annotated .mt file) and therefore your task is running out of memory. There are many ways for you to monitor the health of your cluster to help you realize where the error comes from. Also, you can ask these kind of questions directly on the Hail chat, they are very responsive.
I'm closing this issue.


Unable to Create any file or folder in left pane

Issue Type: Bug
Below steps were done to get this issue.

Create test folder 'Mongoose_stuffs' on C:.
On VS Code select File -> Open Folder and choose the folder you just created.
Right click in the left pane for the opened folder and try to create a file or a folder and it creates a file or folder but it just disappears within seconds or if we were able to write the name for the file or folder then it will exist but the name of the folder or file created will be upto the letters that we were able to write within seconds. Also I'm unable to rename the file or folder as whenever i clicks it, it just stays for sometime and then the cursor disappears.

NO, while all the extensions were disabled the problem no more persists.

Then I suggest you use the Start Extension Bisect command to find out which of your extensions is causing the issue. Then raise it with the extension developers.
/causedByExtension

Ok, thanks for helping me out.


Preserve array data

When calling "get_node", data is returned as-is (as expected), but when doing "get_json", just to parse all the data arrays, you notice that they are converted to an object (not expected).
Right now I have to reconvert those objects to arrays, and that's not optimal.

Thank you for the PR, but I can not merge this yet, as jsTree still supports IE8, which means Array.isArray will fail. Would you mind checking the type in a cross browser way, so that I can merge?

Oh yeah, didn't checked that, my bad. Added jQuery isArray check, as other parts of the code.


Add plot RGB distribution page

Added a plot RGB distribution page to quickly get the RGB distribution of an image.

I should mention these links were very helpful:

https://thmsdnnr.com/blog/draw-photo-histograms-d3-canvas/
https://d3-graph-gallery.com/graph/density_basic.html


Nerf Xal'atath Blade of the Black Empire

Either remove it from the quest or heavily nerf the item

Let's nerf it. Trivial to do and no point removing content if it's just as much effort.


Menu not working

The menu is not working, if you are not logged in.
When I select any option from the menu, I get the following error message.

hm. we shouldn't have a menu at this point. perhaps there's a way of not showing it until we're logged in?

i added 'loggedin' view state used to disable some menu items before the login. Not sure i got all of them.


Replacing Echarts with Chartist.

This is part of #972 and will close #989 and #943.

I really like that this commit removes updateChartIfPossible. The chart just gets updated.
Am I allowed to comment on my own code? Just try to stop me. :-D


Suggestion: See who is in each stage.

Here's my suggestion: What if you could see who is in a stage? For example, if you're looking for a friend but you don't know which server they're in. You could look at the stage and see if they're in that stage.

that is available in the discord, but that may be something worth adding for non-discord users.

Yeah, because i'm a non-discord user.


offerService should not allow invalid ServiceDescriptions

adjust offerService() behavior so that it should not allow invalid ServiceDescriptions
(https://github.com/eclipse/iceoryx/blob/master/iceoryx_posh/include/iceoryx_posh/runtime/posh_runtime.hpp)

offerService should return a bool signalling if it was successful

add more test cases to verify the behavior fully

@nihalchari
This issue was already resolved by https://github.com/eclipse-iceoryx/iceoryx/pull/342, therefore i close it.


Import: multi-object animations

I was trying out the mult-object animation stuff in the importer and assuming I understand it correctly, I found some issues.
Track names are not unique per animations
Here's a test file. It's just BoxAnimated from the sample model with three copies of the same animation (which animates two objects); two are named "A", and one is unnamed. It imports like this

So the tracks from the two animations named "A" have the same name and there's no way to tell them apart. On the other hand, the tracks from the unnamed animation are named with the action name, so there's no way to tell that they're part of the same animation.
So I think there should be a preprocessing pass that picks a unique name for each animation in the glTF that can be used as the track name every time it's actions get pushed.
Actions for different objects get pushed onto an object's NLA stack
Again, in the above image, every object has the actions for every other object pushed onto it, not just it's own.
The wrong actions get restored
The importer restores the action from the bottom-most (first) track after importing. In this case, because of the above point, it means that the purple box (inner_box) plays the blue box's action (A_Node) instead of it's own (A_inner_box). It should look like this, but it currently doesn't

Other sample animations suffer similarly (ex. VC).
Restoring the first track's action might also wind up playing actions from two different animations if, say, not all objects are animated by every animation.
So I think the right thing to do is to pick one animation (say the first one) and always restore the actions needed to play that one.
No way to play animations?
Is there a way to actually play an animation encoded as a set of identically-named tracks in Blender? Short of manually selecting them all the right actions? If not, could the addon add a widget somewhere that would do that automatically for you?

Hello,

[ ] 1: Track names are not unique per animations: Great enhancement ideas. Added on my TODO list
[ ] 2: Actions for different objects get pushed onto an object's NLA stack : Clearly a bug
[ ] 3: The wrong actions get restored: consequence of bug 2. Will be solved after solving 2., and can be enhanced by 4.
[ ] 4: restore the first glTF animation: welcome enhancement that will clarify things
[ ] 5: Do think there is any simple way to do it by default in Blender. An addon can help. Not sure this should be included within the importer/exporter, but in a first step, I can create a separate addon.

Thanks for pointing these stuff out!

Let me know if I can help with any of it.


[a11y tool] only add one initial announcement

It seems in documents with more than one equation, the walker is adding an announcement ("nav. math in page, explore with shift+space") for each equation, leading to as many announcements as there are equations in the page -- that's a bit annoying :wink:

I can't see that. Where does that happen?

@pkra This should help.

Fixed in #74

:+1:


[Translation] The Stand

What kind of translation do you want to add (mark with an X, e.g. [X] Descent)?

[x] Mansions of Madness
[ ] Descent

https://raw.githubusercontent.com/GwanGwanish/Mansions2/master/TheStand/

Localization.Portuguese.txt
@GwanGwanish

@Revokee , I see you are still waiting. I usually contact with @GwanGwanish using the BGG. Try there.

Indeed, I only periodically check my accounts. I'm not sure exactly what is
being asked of me here? I tried to check how "The Stand" was currently
listed on Valkyrie, but there is a network error at the moment. Do you need
me to add the Portuguese option? I thought I had already added it, but
maybe I am thinking of one of my other scenarios.
On Mon, Aug 10, 2020 at 7:22 PM vidimus<EMAIL_ADDRESS>wrote:

@Revokee https://github.com/Revokee , I see you are still waiting. I
usually contact with @GwanGwanish https://github.com/GwanGwanish using
the BGG. Try there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NPBruce/valkyrie/issues/1338#issuecomment-671637695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKBBTNHNXJRBFKLUDVOM5STSAB6L7ANCNFSM4PSJGKYA
.

Got it - I see I still need to add this one. Will do so when I have a
moment.
Thanks!
On Tue, Aug 11, 2020 at 9:48 PM GwanGwanish<EMAIL_ADDRESS>wrote:

Indeed, I only periodically check my accounts. I'm not sure exactly what
is being asked of me here? I tried to check how "The Stand" was currently
listed on Valkyrie, but there is a network error at the moment. Do you need
me to add the Portuguese option? I thought I had already added it, but
maybe I am thinking of one of my other scenarios.
On Mon, Aug 10, 2020 at 7:22 PM vidimus<EMAIL_ADDRESS>wrote:

@Revokee https://github.com/Revokee , I see you are still waiting. I
usually contact with @GwanGwanish https://github.com/GwanGwanish using
the BGG. Try there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NPBruce/valkyrie/issues/1338#issuecomment-671637695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKBBTNHNXJRBFKLUDVOM5STSAB6L7ANCNFSM4PSJGKYA
.

I updated Valkyrie with the portuguese addition. I will check later to see
that it uploaded correctly.
Thanks!
On Tue, Aug 11, 2020 at 9:50 PM GwanGwanish<EMAIL_ADDRESS>wrote:

Got it - I see I still need to add this one. Will do so when I have a
moment.
Thanks!
On Tue, Aug 11, 2020 at 9:48 PM GwanGwanish<EMAIL_ADDRESS>wrote:

Indeed, I only periodically check my accounts. I'm not sure exactly what
is being asked of me here? I tried to check how "The Stand" was currently
listed on Valkyrie, but there is a network error at the moment. Do you need
me to add the Portuguese option? I thought I had already added it, but
maybe I am thinking of one of my other scenarios.
On Mon, Aug 10, 2020 at 7:22 PM vidimus<EMAIL_ADDRESS>wrote:

@Revokee https://github.com/Revokee , I see you are still waiting. I
usually contact with @GwanGwanish https://github.com/GwanGwanish
using the BGG. Try there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NPBruce/valkyrie/issues/1338#issuecomment-671637695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKBBTNHNXJRBFKLUDVOM5STSAB6L7ANCNFSM4PSJGKYA
.

Parabems, @Revokee , another scenario translated into Portuguese is already available. Well done!


Mention macros begin & end in docs

Related to https://github.com/crystal-lang/crystal/issues/4899#issuecomment-326037145
I literally cannot find macro's {% begin %} documentation anywhere. I may be blind, so please consider pointing me to it.

We'll merge this: https://github.com/crystal-lang/crystal-book/pull/117


Update LARA Plugin API to V3, use NPM package for type checking, update tests

[#165356734]
Migrate to LARA Plugin API V3 implemented in this PR:
https://github.com/concord-consortium/lara/pull/400
It's an example of how to use and configure @concord-consortium/lara-plugin-api package.

A few more changes. PluginApp has been refactored. It uses the very last LARA Plugin API package (3.0.0-pre.7). I've also implemented better LARA Plugin API mocks.


Fix for IMAGING-265

This change addresses JIRA issue IMAGING-265.  It enhances the TIFF reader logic so that it can handle certain kinds of images that divide RGB values into three separate planes rather than using the more common interleaved format.
At this time, I have only implemented PlanarConfiguration=2 support for TIFF files organized into strips (rather than tiles) using the 24 bit RGB photometric interpreter.

Coverage increased (+0.05%) to 76.381% when pulling 763a7310394ec3138c457a7c2054e2017f9ab318 on gwlucastrig:IMAGING-265 into 5ab6b2059f9201fdec1d73991f6ffce65ae18e79 on apache:master.

Pending review, I believe that this pull request addresses IMAGING-265 and that the issue can be closed.

Okay.   I will update the pull request to use the TiffPlanarConfiguration
enumerated type.
On Tue, Oct 6, 2020, 6:50 AM Bruno P. Kinoshita<EMAIL_ADDRESS>wrote:

@kinow commented on this pull request.
 I see that you
self-assigned this. Does that mean you'll be making the change?
No, sorry it's just an old habit. I believe I cannot assign the issue to
you as you are an external contributor. I normally assign issues & PR's to
myself so other common developers are aware I'm interested in
working/finishing work on some issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/commons-imaging/pull/98#discussion_r500180247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWJDYNAE7UN6M2CJ2M7WQTSJLY57ANCNFSM4RSXZ7OQ
.

I believe this completes the work for Imaging-265.

Merged. Here's what I did to merge @gwlucastrig

checked out branch locally
added a commit with the src/changes/changes.xml entry for this issue
squashed commits
reworded commit to match the change, using the [IMAGING-265] prefix

These are not a must-have, but really nice-to-have, as other components follow this pattern. This helps other common developers to maintain the code.
:+1: just because you are already familiar with most of the ASF development process, so I thought it would be interesting to share more of what happens with the PR's/issues with you :-)
Thanks again for the contribution!
Bruno

Thanks for the information on merge procedures.  The better I understand
the process, the easier it will be next time.
Gary
On Thu, Oct 8, 2020 at 12:14 AM Bruno P. Kinoshita<EMAIL_ADDRESS>wrote:

Merged. Here's what I did to merge @gwlucastrig
https://github.com/gwlucastrig

checked out branch locally
added a commit with the src/changes/changes.xml entry for this issue
squashed commits
reworded commit to match the change, using the [IMAGING-265] prefix

These are not a must-have, but really nice-to-have, as other components
follow this pattern. This helps other common developers to maintain the
code.
👍 just because you are already familiar with most of the ASF development
process, so I thought it would be interesting to share more of what happens
with the PR's/issues with you :-)
Thanks again for the contribution!
Bruno
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/commons-imaging/pull/98#issuecomment-705318187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWJDYIMPSZMCYLTGRAC3HDSJU4D3ANCNFSM4RSXZ7OQ
.


fusible.exe problem

Hello,  I dont't know how I can get fusible.exe used by the depth_fusion.py. Any advice for me?

try:
python depthfusion.py -f dtu -n flow2 --eval_folder data/dtu2/Eval/ --fusibile_exe_path FUSIBILE_PATH/fusibile/build/fusibile
but I got zero points……
**** Fusion for scan1 ****
filter depth map with probability map
Convert mvsnet output to gipuma input
Run depth map fusion & filter
../fusibile/build/fusibile -input_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ -p_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ -images_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ --depth_min=0.001 --depth_max=100000 --normal_thresh=360 --disp_thresh=0.12 --num_consistent=3
Command-line parameter error: unknown option -input_folder
input folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/
image folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/
p folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/
pmvs folder is
numImages is 49
img_filenames is 49
Device memory used: 313.589752MB
Device memory used: 313.589752MB
P folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/
numCameras is 49
Camera size is 49
Accepted intersection angle of central rays is 10.000000 to 30.000000 degrees
Selected views: 49
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48,
Reading normals and depth from disk
Size consideredIds is 49
Reading normal 0
Reading disp 0
Reading normal 1
Reading disp 1
Reading normal 2
Reading disp 2
Reading normal 3
Reading disp 3
Reading normal 4
Reading disp 4
Reading normal 5
Reading disp 5
Reading normal 6
Reading disp 6
Reading normal 7
Reading disp 7
Reading normal 8
Reading disp 8
Reading normal 9
Reading disp 9
Reading normal 10
Reading disp 10
Reading normal 11
Reading disp 11
Reading normal 12
Reading disp 12
Reading normal 13
Reading disp 13
Reading normal 14
Reading disp 14
Reading normal 15
Reading disp 15
Reading normal 16
Reading disp 16
Reading normal 17
Reading disp 17
Reading normal 18
Reading disp 18
Reading normal 19
Reading disp 19
Reading normal 20
Reading disp 20
Reading normal 21
Reading disp 21
Reading normal 22
Reading disp 22
Reading normal 23
Reading disp 23
Reading normal 24
Reading disp 24
Reading normal 25
Reading disp 25
Reading normal 26
Reading disp 26
Reading normal 27
Reading disp 27
Reading normal 28
Reading disp 28
Reading normal 29
Reading disp 29
Reading normal 30
Reading disp 30
Reading normal 31
Reading disp 31
Reading normal 32
Reading disp 32
Reading normal 33
Reading disp 33
Reading normal 34
Reading disp 34
Reading normal 35
Reading disp 35
Reading normal 36
Reading disp 36
Reading normal 37
Reading disp 37
Reading normal 38
Reading disp 38
Reading normal 39
Reading disp 39
Reading normal 40
Reading disp 40
Reading normal 41
Reading disp 41
Reading normal 42
Reading disp 42
Reading normal 43
Reading disp 43
Reading normal 44
Reading disp 44
Reading normal 45
Reading disp 45
Reading normal 46
Reading disp 46
Reading normal 47
Reading disp 47
Reading normal 48
Reading disp 48
Resizing globalstate to 49
Run cuda
Run gipuma
Grid size initrand is grid: 20-15 block: 32-32
Device memory used: 930.152466MB
Number of iterations is 8
Blocksize is 15x15
Disparity threshold is 	0.120000
Normal threshold is 	6.283185
Number of consistent points is 	3
Cam scale is 	1.000000
Fusing points
Processing camera 0
Found 0.00 million points
Processing camera 1
Found 0.00 million points
Processing camera 2
Found 0.00 million points
Processing camera 3
Found 0.00 million points
Processing camera 4
Found 0.00 million points
Processing camera 5
Found 0.00 million points
Processing camera 6
Found 0.00 million points
Processing camera 7
Found 0.00 million points
Processing camera 8
Found 0.00 million points
Processing camera 9
Found 0.00 million points
Processing camera 10
Found 0.00 million points
Processing camera 11
Found 0.00 million points
Processing camera 12
Found 0.00 million points
Processing camera 13
Found 0.00 million points
Processing camera 14
Found 0.00 million points
Processing camera 15
Found 0.00 million points
Processing camera 16
Found 0.00 million points
Processing camera 17
Found 0.00 million points
Processing camera 18
Found 0.00 million points
Processing camera 19
Found 0.00 million points
Processing camera 20
Found 0.00 million points
Processing camera 21
Found 0.00 million points
Processing camera 22
Found 0.00 million points
Processing camera 23
Found 0.00 million points
Processing camera 24
Found 0.00 million points
Processing camera 25
Found 0.00 million points
Processing camera 26
Found 0.00 million points
Processing camera 27
Found 0.00 million points
Processing camera 28
Found 0.00 million points
Processing camera 29
Found 0.00 million points
Processing camera 30
Found 0.00 million points
Processing camera 31
Found 0.00 million points
Processing camera 32
Found 0.00 million points
Processing camera 33
Found 0.00 million points
Processing camera 34
Found 0.00 million points
Processing camera 35
Found 0.00 million points
Processing camera 36
Found 0.00 million points
Processing camera 37
Found 0.00 million points
Processing camera 38
Found 0.00 million points
Processing camera 39
Found 0.00 million points
Processing camera 40
Found 0.00 million points
Processing camera 41
Found 0.00 million points
Processing camera 42
Found 0.00 million points
Processing camera 43
Found 0.00 million points
Processing camera 44
Found 0.00 million points
Processing camera 45
Found 0.00 million points
Processing camera 46
Found 0.00 million points
Processing camera 47
Found 0.00 million points
Processing camera 48
Found 0.00 million points
		ELAPSED 0.268467 seconds
Writing ply file data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1//consistencyCheck-20200525-090847//final3d_model.ply
store 3D points to ply file

Sorry, I made a wrong reply!
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年5月25日(星期一) 上午10:07
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [svip-lab/FastMVSNet] fusible.exe problem (#5)
try:
python depthfusion.py -f dtu -n flow2 --eval_folder data/dtu2/Eval/ --fusibile_exe_path FUSIBILE_PATH/fusibile/build/fusibile
but I got zero points……
**** Fusion for scan1 **** filter depth map with probability map Convert mvsnet output to gipuma input Run depth map fusion & filter ../fusibile/build/fusibile -input_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ -p_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ -images_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ --depth_min=0.001 --depth_max=100000 --normal_thresh=360 --disp_thresh=0.12 --num_consistent=3 Command-line parameter error: unknown option -input_folder input folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ image folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ p folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ pmvs folder is  numImages is 49 img_filenames is 49 Device memory used: 313.589752MB Device memory used: 313.589752MB P folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ numCameras is 49 Camera size is 49 Accepted intersection angle of central rays is 10.000000 to 30.000000 degrees Selected views: 49 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48,  Reading normals and depth from disk Size consideredIds is 49 Reading normal 0 Reading disp 0 Reading normal 1 Reading disp 1 Reading normal 2 Reading disp 2 Reading normal 3 Reading disp 3 Reading normal 4 Reading disp 4 Reading normal 5 Reading disp 5 Reading normal 6 Reading disp 6 Reading normal 7 Reading disp 7 Reading normal 8 Reading disp 8 Reading normal 9 Reading disp 9 Reading normal 10 Reading disp 10 Reading normal 11 Reading disp 11 Reading normal 12 Reading disp 12 Reading normal 13 Reading disp 13 Reading normal 14 Reading disp 14 Reading normal 15 Reading disp 15 Reading normal 16 Reading disp 16 Reading normal 17 Reading disp 17 Reading normal 18 Reading disp 18 Reading normal 19 Reading disp 19 Reading normal 20 Reading disp 20 Reading normal 21 Reading disp 21 Reading normal 22 Reading disp 22 Reading normal 23 Reading disp 23 Reading normal 24 Reading disp 24 Reading normal 25 Reading disp 25 Reading normal 26 Reading disp 26 Reading normal 27 Reading disp 27 Reading normal 28 Reading disp 28 Reading normal 29 Reading disp 29 Reading normal 30 Reading disp 30 Reading normal 31 Reading disp 31 Reading normal 32 Reading disp 32 Reading normal 33 Reading disp 33 Reading normal 34 Reading disp 34 Reading normal 35 Reading disp 35 Reading normal 36 Reading disp 36 Reading normal 37 Reading disp 37 Reading normal 38 Reading disp 38 Reading normal 39 Reading disp 39 Reading normal 40 Reading disp 40 Reading normal 41 Reading disp 41 Reading normal 42 Reading disp 42 Reading normal 43 Reading disp 43 Reading normal 44 Reading disp 44 Reading normal 45 Reading disp 45 Reading normal 46 Reading disp 46 Reading normal 47 Reading disp 47 Reading normal 48 Reading disp 48 Resizing globalstate to 49 Run cuda Run gipuma Grid size initrand is grid: 20-15 block: 32-32 Device memory used: 930.152466MB Number of iterations is 8 Blocksize is 15x15 Disparity threshold is 	0.120000 Normal threshold is 	6.283185 Number of consistent points is 	3 Cam scale is 	1.000000 Fusing points Processing camera 0 Found 0.00 million points Processing camera 1 Found 0.00 million points Processing camera 2 Found 0.00 million points Processing camera 3 Found 0.00 million points Processing camera 4 Found 0.00 million points Processing camera 5 Found 0.00 million points Processing camera 6 Found 0.00 million points Processing camera 7 Found 0.00 million points Processing camera 8 Found 0.00 million points Processing camera 9 Found 0.00 million points Processing camera 10 Found 0.00 million points Processing camera 11 Found 0.00 million points Processing camera 12 Found 0.00 million points Processing camera 13 Found 0.00 million points Processing camera 14 Found 0.00 million points Processing camera 15 Found 0.00 million points Processing camera 16 Found 0.00 million points Processing camera 17 Found 0.00 million points Processing camera 18 Found 0.00 million points Processing camera 19 Found 0.00 million points Processing camera 20 Found 0.00 million points Processing camera 21 Found 0.00 million points Processing camera 22 Found 0.00 million points Processing camera 23 Found 0.00 million points Processing camera 24 Found 0.00 million points Processing camera 25 Found 0.00 million points Processing camera 26 Found 0.00 million points Processing camera 27 Found 0.00 million points Processing camera 28 Found 0.00 million points Processing camera 29 Found 0.00 million points Processing camera 30 Found 0.00 million points Processing camera 31 Found 0.00 million points Processing camera 32 Found 0.00 million points Processing camera 33 Found 0.00 million points Processing camera 34 Found 0.00 million points Processing camera 35 Found 0.00 million points Processing camera 36 Found 0.00 million points Processing camera 37 Found 0.00 million points Processing camera 38 Found 0.00 million points Processing camera 39 Found 0.00 million points Processing camera 40 Found 0.00 million points Processing camera 41 Found 0.00 million points Processing camera 42 Found 0.00 million points Processing camera 43 Found 0.00 million points Processing camera 44 Found 0.00 million points Processing camera 45 Found 0.00 million points Processing camera 46 Found 0.00 million points Processing camera 47 Found 0.00 million points Processing camera 48 Found 0.00 million points 		ELAPSED 0.268467 seconds Writing ply file data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1//consistencyCheck-20200525-090847//final3d_model.ply store 3D points to ply file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think you may need to reorganize the directories for the project, the 'dtu2' directory is supposed to be 'dtu'.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年5月25日(星期一) 上午10:07
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [svip-lab/FastMVSNet] fusible.exe problem (#5)
try:
python depthfusion.py -f dtu -n flow2 --eval_folder data/dtu2/Eval/ --fusibile_exe_path FUSIBILE_PATH/fusibile/build/fusibile
but I got zero points……
**** Fusion for scan1 **** filter depth map with probability map Convert mvsnet output to gipuma input Run depth map fusion & filter ../fusibile/build/fusibile -input_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ -p_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ -images_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ --depth_min=0.001 --depth_max=100000 --normal_thresh=360 --disp_thresh=0.12 --num_consistent=3 Command-line parameter error: unknown option -input_folder input folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ image folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ p folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ pmvs folder is  numImages is 49 img_filenames is 49 Device memory used: 313.589752MB Device memory used: 313.589752MB P folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ numCameras is 49 Camera size is 49 Accepted intersection angle of central rays is 10.000000 to 30.000000 degrees Selected views: 49 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48,  Reading normals and depth from disk Size consideredIds is 49 Reading normal 0 Reading disp 0 Reading normal 1 Reading disp 1 Reading normal 2 Reading disp 2 Reading normal 3 Reading disp 3 Reading normal 4 Reading disp 4 Reading normal 5 Reading disp 5 Reading normal 6 Reading disp 6 Reading normal 7 Reading disp 7 Reading normal 8 Reading disp 8 Reading normal 9 Reading disp 9 Reading normal 10 Reading disp 10 Reading normal 11 Reading disp 11 Reading normal 12 Reading disp 12 Reading normal 13 Reading disp 13 Reading normal 14 Reading disp 14 Reading normal 15 Reading disp 15 Reading normal 16 Reading disp 16 Reading normal 17 Reading disp 17 Reading normal 18 Reading disp 18 Reading normal 19 Reading disp 19 Reading normal 20 Reading disp 20 Reading normal 21 Reading disp 21 Reading normal 22 Reading disp 22 Reading normal 23 Reading disp 23 Reading normal 24 Reading disp 24 Reading normal 25 Reading disp 25 Reading normal 26 Reading disp 26 Reading normal 27 Reading disp 27 Reading normal 28 Reading disp 28 Reading normal 29 Reading disp 29 Reading normal 30 Reading disp 30 Reading normal 31 Reading disp 31 Reading normal 32 Reading disp 32 Reading normal 33 Reading disp 33 Reading normal 34 Reading disp 34 Reading normal 35 Reading disp 35 Reading normal 36 Reading disp 36 Reading normal 37 Reading disp 37 Reading normal 38 Reading disp 38 Reading normal 39 Reading disp 39 Reading normal 40 Reading disp 40 Reading normal 41 Reading disp 41 Reading normal 42 Reading disp 42 Reading normal 43 Reading disp 43 Reading normal 44 Reading disp 44 Reading normal 45 Reading disp 45 Reading normal 46 Reading disp 46 Reading normal 47 Reading disp 47 Reading normal 48 Reading disp 48 Resizing globalstate to 49 Run cuda Run gipuma Grid size initrand is grid: 20-15 block: 32-32 Device memory used: 930.152466MB Number of iterations is 8 Blocksize is 15x15 Disparity threshold is 	0.120000 Normal threshold is 	6.283185 Number of consistent points is 	3 Cam scale is 	1.000000 Fusing points Processing camera 0 Found 0.00 million points Processing camera 1 Found 0.00 million points Processing camera 2 Found 0.00 million points Processing camera 3 Found 0.00 million points Processing camera 4 Found 0.00 million points Processing camera 5 Found 0.00 million points Processing camera 6 Found 0.00 million points Processing camera 7 Found 0.00 million points Processing camera 8 Found 0.00 million points Processing camera 9 Found 0.00 million points Processing camera 10 Found 0.00 million points Processing camera 11 Found 0.00 million points Processing camera 12 Found 0.00 million points Processing camera 13 Found 0.00 million points Processing camera 14 Found 0.00 million points Processing camera 15 Found 0.00 million points Processing camera 16 Found 0.00 million points Processing camera 17 Found 0.00 million points Processing camera 18 Found 0.00 million points Processing camera 19 Found 0.00 million points Processing camera 20 Found 0.00 million points Processing camera 21 Found 0.00 million points Processing camera 22 Found 0.00 million points Processing camera 23 Found 0.00 million points Processing camera 24 Found 0.00 million points Processing camera 25 Found 0.00 million points Processing camera 26 Found 0.00 million points Processing camera 27 Found 0.00 million points Processing camera 28 Found 0.00 million points Processing camera 29 Found 0.00 million points Processing camera 30 Found 0.00 million points Processing camera 31 Found 0.00 million points Processing camera 32 Found 0.00 million points Processing camera 33 Found 0.00 million points Processing camera 34 Found 0.00 million points Processing camera 35 Found 0.00 million points Processing camera 36 Found 0.00 million points Processing camera 37 Found 0.00 million points Processing camera 38 Found 0.00 million points Processing camera 39 Found 0.00 million points Processing camera 40 Found 0.00 million points Processing camera 41 Found 0.00 million points Processing camera 42 Found 0.00 million points Processing camera 43 Found 0.00 million points Processing camera 44 Found 0.00 million points Processing camera 45 Found 0.00 million points Processing camera 46 Found 0.00 million points Processing camera 47 Found 0.00 million points Processing camera 48 Found 0.00 million points 		ELAPSED 0.268467 seconds Writing ply file data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1//consistencyCheck-20200525-090847//final3d_model.ply store 3D points to ply file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

OK, thanks very much！
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年5月25日(星期一) 上午10:07
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [svip-lab/FastMVSNet] fusible.exe problem (#5)
try:
python depthfusion.py -f dtu -n flow2 --eval_folder data/dtu2/Eval/ --fusibile_exe_path FUSIBILE_PATH/fusibile/build/fusibile
but I got zero points……
**** Fusion for scan1 **** filter depth map with probability map Convert mvsnet output to gipuma input Run depth map fusion & filter ../fusibile/build/fusibile -input_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ -p_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ -images_folder data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ --depth_min=0.001 --depth_max=100000 --normal_thresh=360 --disp_thresh=0.12 --num_consistent=3 Command-line parameter error: unknown option -input_folder input folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/ image folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/images/ p folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ pmvs folder is  numImages is 49 img_filenames is 49 Device memory used: 313.589752MB Device memory used: 313.589752MB P folder is data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1/cams/ numCameras is 49 Camera size is 49 Accepted intersection angle of central rays is 10.000000 to 30.000000 degrees Selected views: 49 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48,  Reading normals and depth from disk Size consideredIds is 49 Reading normal 0 Reading disp 0 Reading normal 1 Reading disp 1 Reading normal 2 Reading disp 2 Reading normal 3 Reading disp 3 Reading normal 4 Reading disp 4 Reading normal 5 Reading disp 5 Reading normal 6 Reading disp 6 Reading normal 7 Reading disp 7 Reading normal 8 Reading disp 8 Reading normal 9 Reading disp 9 Reading normal 10 Reading disp 10 Reading normal 11 Reading disp 11 Reading normal 12 Reading disp 12 Reading normal 13 Reading disp 13 Reading normal 14 Reading disp 14 Reading normal 15 Reading disp 15 Reading normal 16 Reading disp 16 Reading normal 17 Reading disp 17 Reading normal 18 Reading disp 18 Reading normal 19 Reading disp 19 Reading normal 20 Reading disp 20 Reading normal 21 Reading disp 21 Reading normal 22 Reading disp 22 Reading normal 23 Reading disp 23 Reading normal 24 Reading disp 24 Reading normal 25 Reading disp 25 Reading normal 26 Reading disp 26 Reading normal 27 Reading disp 27 Reading normal 28 Reading disp 28 Reading normal 29 Reading disp 29 Reading normal 30 Reading disp 30 Reading normal 31 Reading disp 31 Reading normal 32 Reading disp 32 Reading normal 33 Reading disp 33 Reading normal 34 Reading disp 34 Reading normal 35 Reading disp 35 Reading normal 36 Reading disp 36 Reading normal 37 Reading disp 37 Reading normal 38 Reading disp 38 Reading normal 39 Reading disp 39 Reading normal 40 Reading disp 40 Reading normal 41 Reading disp 41 Reading normal 42 Reading disp 42 Reading normal 43 Reading disp 43 Reading normal 44 Reading disp 44 Reading normal 45 Reading disp 45 Reading normal 46 Reading disp 46 Reading normal 47 Reading disp 47 Reading normal 48 Reading disp 48 Resizing globalstate to 49 Run cuda Run gipuma Grid size initrand is grid: 20-15 block: 32-32 Device memory used: 930.152466MB Number of iterations is 8 Blocksize is 15x15 Disparity threshold is 	0.120000 Normal threshold is 	6.283185 Number of consistent points is 	3 Cam scale is 	1.000000 Fusing points Processing camera 0 Found 0.00 million points Processing camera 1 Found 0.00 million points Processing camera 2 Found 0.00 million points Processing camera 3 Found 0.00 million points Processing camera 4 Found 0.00 million points Processing camera 5 Found 0.00 million points Processing camera 6 Found 0.00 million points Processing camera 7 Found 0.00 million points Processing camera 8 Found 0.00 million points Processing camera 9 Found 0.00 million points Processing camera 10 Found 0.00 million points Processing camera 11 Found 0.00 million points Processing camera 12 Found 0.00 million points Processing camera 13 Found 0.00 million points Processing camera 14 Found 0.00 million points Processing camera 15 Found 0.00 million points Processing camera 16 Found 0.00 million points Processing camera 17 Found 0.00 million points Processing camera 18 Found 0.00 million points Processing camera 19 Found 0.00 million points Processing camera 20 Found 0.00 million points Processing camera 21 Found 0.00 million points Processing camera 22 Found 0.00 million points Processing camera 23 Found 0.00 million points Processing camera 24 Found 0.00 million points Processing camera 25 Found 0.00 million points Processing camera 26 Found 0.00 million points Processing camera 27 Found 0.00 million points Processing camera 28 Found 0.00 million points Processing camera 29 Found 0.00 million points Processing camera 30 Found 0.00 million points Processing camera 31 Found 0.00 million points Processing camera 32 Found 0.00 million points Processing camera 33 Found 0.00 million points Processing camera 34 Found 0.00 million points Processing camera 35 Found 0.00 million points Processing camera 36 Found 0.00 million points Processing camera 37 Found 0.00 million points Processing camera 38 Found 0.00 million points Processing camera 39 Found 0.00 million points Processing camera 40 Found 0.00 million points Processing camera 41 Found 0.00 million points Processing camera 42 Found 0.00 million points Processing camera 43 Found 0.00 million points Processing camera 44 Found 0.00 million points Processing camera 45 Found 0.00 million points Processing camera 46 Found 0.00 million points Processing camera 47 Found 0.00 million points Processing camera 48 Found 0.00 million points 		ELAPSED 0.268467 seconds Writing ply file data/dtu2/Eval/dtu/LANCZOS4_3ITER_flow2_ip0.2_fp0.1_d0.12_nc3/scan1//consistencyCheck-20200525-090847//final3d_model.ply store 3D points to ply file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I got the answer to the problem.

Hello, could you tell me exactly how to solve it?This is very important to me, please


use FQCN form types instead of names

follow 2.8+ recommendations

Type names were deprecated and will be removed in Symfony 3.0. Instead of referencing types by name, you should reference them by their fully-qualified class name (FQCN) instead.

also makes it easier to use without having to register the type beforehand (if used outside of the Symfony Framework).

Will there be  a completely 3.0 compatible version of that bundle? That means without any $isSf28 = method_exists('Symfony\Component\Form\AbstractType', 'getBlockPrefix'); ?

@ElectricMaxxx it's not that hard to supports previous 2.x versions so I guess it does not makes much sense to drop support for Symfony < 2.8 before 05/2019 (Sf 2.7 end of life)

Is this safe to merge?

@Burgov I think so


[Stepper] The style of step indicator icons are small

Hi, thanks for building this amazing library, really love it!
Problem Description
Unlike the online demo, when I use it locally, the step indicator svg icons are small (I use exact the same code in the online demo, and all latest version of libraries)
I try to produce a online version, however, is there a online cdn for material-ui?

Versions
React:

"react": "^15.0.1",

"react-dom": "^15.0.1",

Material-UI:

"material-ui": "^0.15.0-beta.1",

"react-tap-event-plugin": "^1.0.0",

Browsers, tested on:

Chrome  49.0.2623.112 (64-bit)
Firefox 45.0.2

@gudh Can you make a demo repo?

I had the same issue (also with the tabs), when I include the following css (which is included in bootstrap):
* {
    -webkit-box-sizing: border-box;
    -moz-box-sizing: border-box;
    box-sizing: border-box;
}

I can solve the problem by giving the Tab and the StepButton a className and setting the box-sizing of the relevant elements to content-box with css.

@Marcoga Thanks for testing that.
@gudh We don't seem to have a policy at the moment for resetting that property if/where needed so I'll have to chat to the others to see if we will put something in, but for now @Marcoga 's solution should do the trick 👍

I have same issue with react 15.4.0 and material-ui 0.16.4.

To change the icon size, just do it like this in 15.4.0 and material-ui 0.16.4:
<StepLabel iconContainerStyle={{width: 36}}></StepLabel>

use this  for icon size
.css-1u4zpwo-MuiSvgIcon-root-MuiStepIcon-root {
height: 50px !important;
width: 50px !important;
}


New syntax: Enable splatting for class instantiations and method calls

This feedback was well-received a couple years ago, with 23 upvotes on Microsoft Connect, but hasn't been implemented yet. Basically, it would be really cool to be able to call a class constructor and "splat" the input parameters, and invoke static & instance methods the same way.
https://connect.microsoft.com/PowerShell/feedback/details/1376904/splatting-for-class-method-input-parameters
class Person {
    [string] $FirstName;
    [string] $LastName;

    Person ([string] $First, [string] $Last) {
        $this.FirstName = $First;
        $this.LastName = $Last;
    }
}

$NewPerson = @{
    FirstName = 'Trevor';
    LastName = 'Sullivan';
    };
[Person]::new(@NewPerson);

Cheers,
Trevor Sullivan
https://trevorsullivan.net
https://twitter.com/pcgeek86

This is discussed in the generalized splatting RFC, see here.

RFC comments reference


Update bootstrap, jquery, select2-bootstrap, moment.js, datepicker

New versions:

bootstrap 2 - 2.3.1 -> 2.3.2
bootstrap 3 - 3.3.1 -> 3.3.5
jquery - 2.1.1 -> 2.1.4
select2-bootstrap - 1.4.1 -> 1.4.6
bootstrap daterangepicker - 1.3.15 -> 1.3.22
moment.js - 2.8.4 -> 2.9.0

I'm working on implementing modals for the edit_view and I needed to update bootstrap to get some fixes to modals. Also, the bootstrap daterangepicker wouldn't work properly in the modals until I updated it.
The daterangepicker has quite a few bug fixes and I finally got my commit for adding data-attributes merged: https://github.com/dangrossman/bootstrap-daterangepicker/commit/abaa4c9c8cd1e9ad2b96c9f261a07c054036b1c1

Do you know if select2-bootstrap is comptible with select2 4.0?

Since select2 4.0 supports themes, they started a new project for it: https://github.com/select2/select2-bootstrap-theme
This pull request didn't update select2 to 4.0 btw, I haven't tried it yet.


Still getting issues :(

Hello
ok Finally i install Ubuntu 20.04 and this time i install script step by step using this guide
Ubuntu/Debian packages are available for both amd64 and arm7 (Raspbian):
Add the PPA key
$ curl -s "https://wouterdebie.github.io/ppa/KEY.gpg" | sudo apt-key add -
Add the locast2tuner repository
$ sudo curl -o /etc/apt/sources.list.d/locast2tuner.list "https://wouterdebie.github.io/ppa/sources.list"
$ sudo apt update
Install locast2tuner
$ sudo apt install locast2tuner
Create a config file. Don't forget to edit the config file!
$ sudo cp /etc/locast2tuner/config.example /etc/locast2tuner/config
Edit the config file
$ nano /etc/locast2tuner/config
Finally, enable and start the service:
$ sudo systemctl enable locast2tuner
$ sudo systemctl start locast2tuner
and perfect without error, actually i installed Apache 2 that si working perfect, i have disabled iptables and i am trying to used on browser for one PC in the same network http://<IP_ADDRESS>:6077
This site can’t be reached<IP_ADDRESS> refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
and apache is working fine, also i configured config with my username and password adn like example but alltime report me This site Can't be reached :(
some suggestion?
thank in advance

OK finally is working :) i am getting tuner.m3u but now i am getting one issues uhmmm i mean using stream direct on VLC local works perfect and using since using since one iptv panel inside US  to my this PC inside works fine but since my other iptv load balance that is in canada no work uhmm is detecting geolocalization from my load balance? wear if use my laod balance here near where i am works fine.
some suggestion?

well Finally is working :), but is wear works for about 10 seconds, after use sudo systemctl start locast2tuner report me a list of .m3u i use on vlc and works for about 10 or 20 seconds, when i i refresh or F5 to tiner.m3u report  This site can't be reached :( but i fi run a sudo systemctl start locast2tuner commans will be works again for 10 or 20 seconds again :(
soem suggestion?

What URL do you give to VLC?

And could you provide some logs from locast2tuner?

I'm closing this issue, given the quality of the feedback is low. I've added an issue template for bugs that should be used to give us as much data about the issue as possible.


Switch this repo to BUILD_WITH_CONTAINER=1

Revamp how protos are generated to simplify things and
use gogo in a way that's consistent with the rest of the
project.

tested this pr, it seems to crater the generated code:
Stevens-MacBook-Pro:operator sdake$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   pkg/vfs/assets.gen.go

Stevens-MacBook-Pro:operator sdake$ git diff
diff --git a/pkg/vfs/assets.gen.go b/pkg/vfs/assets.gen.go
index 6c883319..39aa7cef 100644
--- a/pkg/vfs/assets.gen.go
+++ b/pkg/vfs/assets.gen.go
@@ -1,213 +1,5 @@
 // Code generated by go-bindata.
 // sources:
-// ../../data/charts/crds/Chart.yaml
-// ../../data/charts/crds/files/crd-10.yaml
-// ../../data/charts/crds/files/crd-11.yaml
-// ../../data/charts/crds/files/crd-12.yaml
-// ../../data/charts/crds/files/crd-certmanager-10.yaml
-// ../../data/charts/crds/files/crd-certmanager-11.yaml
-// ../../data/charts/crds/kustomization.yaml
-// ../../data/charts/crds/templates/crds.yaml
-// ../../data/charts/crds/templates/namespaces.yaml
-// ../../data/charts/gateways/istio-egress/Chart.yaml
-// ../../data/charts/gateways/istio-egress/NOTES.txt
-// ../../data/charts/gateways/istio-egress/templates/_affinity.tpl
-// ../../data/charts/gateways/istio-egress/templates/_helpers.tpl
-// ../../data/charts/gateways/istio-egress/templates/autoscale.yaml
...............

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-lint

operator-build
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-lint

operator-build
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-build

operator-mandiff
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-lint

operator-build
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-build

operator-mandiff
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-mandiff

operator-test
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-lint

operator-build
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-build

operator-mandiff
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-mandiff

operator-test
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-build
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-build

operator-mandiff
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-mandiff

operator-test
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-test

operator-lint
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
33cc7e90eac4b451288b4146c48728f2a01878a3
link
/test operator-mandiff

operator-test
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-test

operator-lint
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-lint

operator-build
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-test
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-test

operator-lint
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-lint

operator-build
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-build

operator-mandiff
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-test
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-test

operator-lint
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-lint

operator-mandiff
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-mandiff

operator-build
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-lint
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-lint

operator-mandiff
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-mandiff

operator-build
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-build

operator-test
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
6ac1da4e73b1f96f0652c6f5adeac483bad71f6b
link
/test operator-mandiff

operator-build
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-build

operator-test
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-test

operator-lint
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-build
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-build

operator-test
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-test

operator-lint
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-lint

operator-mandiff
e239aaafe5659a86fd8b9394e4e23cfbc0ba1277
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-test
9122d0ade3db6367c01b2995e401cc350ce9be29
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test operator-test

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-test
9122d0ade3db6367c01b2995e401cc350ce9be29
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-test
ec9d7a022df79ff18bf8d53eb30ea432a5c3d71d
link
/test operator-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
130441356037d47dfe0233397ed997ac745821ca
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
8a1d0d8b453d932730a354490caadba141dbdb27
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test operator-mandiff

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
8a1d0d8b453d932730a354490caadba141dbdb27
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test operator-mandiff

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
8a1d0d8b453d932730a354490caadba141dbdb27
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test operator-mandiff

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
8a1d0d8b453d932730a354490caadba141dbdb27
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test operator-mandiff

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
8a1d0d8b453d932730a354490caadba141dbdb27
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid Would you please to rebase the change sets with latest source tree to pass the operator-mandiff test?
I merged PR to fix the manifest different test yesterday.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

operator-mandiff
f4fc53a62d3dc95130f23d916b5148a7ff8c170f
link
/test operator-mandiff

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Publish "multipermit" and fix the contract used in the Unity demo

Still relevant because sponsored operations didn't make it to P


Add stable_deref_trait as an optional dependency

This allows using Basedrop's Owned and Shared pointer types with self-referential struct libraries. :slightly_smiling_face:
The dependency is optional and disabled by default.

I will have to give this some thought. My initial impression is that stable_deref_trait collapses some distinctions that are currently relevant under Stacked Borrows, i.e. moving a Box<T> or an &mut T invalidates pointers to the T (even though its address remains the same) whereas moving an Rc<T> does not (I generally agree with most of what's said in https://github.com/Storyyeller/stable_deref_trait/issues/15). While both Owned and Shared should behave like Rc rather than Box or &mut T in that regard, I'm still uneasy about exporting impls of StableDeref, since I am not really convinced that it is a sound abstraction for building self-referential types.

After some more research and thinking on my end, I agree that in hindsight, stable_deref_trait doesn't seem a sound enough abstraction for self-referential types.
Since we both agree it's not a great idea for now, I'll close this PR. If it's ever to be considered again, it's an easy enough change anyway.


Add possibility to view object history

It would be nice to have a possibility to view object history in the same was as potlatch does when you press h key. Make it accessible via a menu item would also be handy.

Thanks!  We get this request a lot, and I'm tracking it on #2273.  I agree it is sometimes helpful to view more information about the recent edits of a feature.


plot data missing in v6.72, on regridding

Reported by andrew wittenberg on 9 Apr 2012 19:04 UTC
Not sure if this is related to bugs #883 and #1140.  This is a boiled down version of a failure seen in a user's script.  Ferret v6.7 (05/06/11) gives a correct plot, while v6.72 gives all missing values.  Removing the "l=1:12" or the "gxy=a" seems to remove the inconsistency.
I am attaching a gzipped tar file containing the script, datasets, and resulting plots.
Note also that there is currently no "v6.72" in the version drop-down list on Trac.
set memory/size=140

use a.nc
use b.nc

let a = tca[b = wsa_nir[l=1:12,gxy=a,d=2](d=1,l=1,k=1]
let)/wsa_vis[a
shade b[l=1](l=1:12,gxy=a,d=2]

shade)

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1931

Comment by andrew.wittenberg on 9 Apr 2012 19:07 UTC
The 256k file size limit on Trac is too small to contain the 249Mb tar file, so I am placing it at:
ftp://ftp.gfdl.noaa.gov/pub/atw/EXPORT/ansley/regrid_bug.tgz

Comment by ansley.b.manke on 10 Apr 2012 18:40 UTC
This relates to ticket #1862, which we fixed by adding an XY linear regridding operation in parallel with what's always been done for @AVE regridding. (Note that if you use @AVE regridding with the above example it works fine). This is what was reported in the v6.71 release notes as "A bug was reported dynamic gridding in XY when there are modulo X axes. For some combinations of source grids and destination grids the modulo and regridding operations were done out of order so that the result became garbled.  This is fixed."
I had not given the new XY linear regridding routine enough work space (taken from the Ferret memory). This example which regrids from this very fine to coarser grid brought out this bug.
Fixed in is_regrid.F


[question] How does it compares with RxFire?

I understand this code let you access Firestore collections as stores (observables), right?  Isn't that what RxFire does?
Am I missing something here?
Also, I don't get the OnLine methods.  What are they for?  I thought Firestore handled the offline case transparently for the developer.

I understand this code let you access Firestore collections as stores (observables), right? Isn't that what RxFire does?
Am I missing something here?

Similar to the source inspiration, Sveltefire, this allows you to use Firebase declaratively via Svelte components but adds a few key items among other things:

Typescript intellisense (e.g. component props and data emitted/passed down)
SvelteKit/SSR friendly
Easy integration w/ FirebaseUI for Web auth - that still hasn't updated to Firebase 9
database helpers that save user ids and timestamps

RxFire is great and could easily be used in tandem with this library. However, I've found that with Svelte custom stores being so easy to build, one custom store for documents and one for collections is all I've ever needed, thus making RxFire obsolete for my purposes. As well, RxFire obviously does not provide Svelte components for easy page composition.

Also, I don't get the OnLine methods. What are they for? I thought Firestore handled the offline case transparently for the developer.

I'll copy from https://sveltefirets.vercel.app/8-offline-persistence:

By design Firebase’ addDoc, setDoc, updateDoc, and deleteDoc methods (and by extension this library’s add, set, update, and deleteDocument helper methods) return promises that resolve only once changes are written to the server and NOT the cache. If poor internet or no internet exists, these promises won’t resolve. So in a use case where a user with weak internet creates a new item and you write your code to await the addition of the item to the database before navigating to a page where that item can be edited further, nothing will happen and users will be left wondering what is broken with the site. You won’t discover this in development because you have great internet! But it could plague you if you are unaware. This is why I’ve set up this library to also include the equivalent Firestore Lite helpers methods as seen in https://github.com/jacobbowdoin/sveltefirets/blob/main/packages/sveltefirets/src/lib/client/firestore-lite.ts - addOnline, setOnline, updateOnline, and deleteOnline.

Firebase is built this way by design - see the links in https://sveltefirets.vercel.app/8-offline-persistence for more discussion about this and different ways to handle it based on your needs.

So addOnline, setOnline, etc will work offline and update the server when the network is back?  If so, shouldn't it be called addOffline, setOffline, etc?

So addOnline, setOnline, etc will work offline and update the server when the network is back? If so, shouldn't it be called addOffline, setOffline, etc?

Firebase by default works online or offline, so the default add, set, etc work anytime because of Firestore's cache. The reason for addOnline is sometimes you only want to add a document when the user is truly connected to the server. In one of my use cases, users are allowed to create a new dictionary for their language (they will only ever do this once) and we don't want them creating a dictionary just on their local cache, thinking they actually created one in our system. Neither Firebase' cache nor user internet connections are flawless so certain things of great importance we don't want left to chance that they never actually make it to the server. In theory, Firebase will successfully get the data to the server every time, but in reality this doesn't happen every time. Just like any other database solution, there are certain times you want to make sure data made it to the server before moving users to the next step - in these cases, you should use addOnline.
This is behavior inherent to all users of Firebase, regardless of platform, many users just don't know all the finer nuances of a caching database that's not perfect. In actual usage, we've run into enough issues to know these sorts of saving methods are important to have available.

Thanks for the explanation and for all your patience with me. I am new to Firestore, I am more used to CouchDB/PouchDB.
I am a Fireship Pro subscriber and I watched the aforementioned video, but I must confess that not being used to Angular it was a little difficult to get the point. I found the demo in this repo much more insightful.
One thing that might help in the documentation is to have with sveltefirets/without sveltefirets examples. Maybe the ubiquitous todomvc example or other small application idea.


German translation refinements

Thanks for the contributions! Some of these translations are to long for the UI, will try to post some screenshots in a bit and see what we can do