Uninformative error message when using .fail() in tests

Take this module:
module test {
    var x: int

    action init = x' = 1

    action inc = x' = x + 1

    action failAction =
        all {
            false,
            x' = 0
        }

    run FailTest = {
        init.then(
            failAction.fail()
        ).then(
            inc
        )
    }
}

Consider in particular the FailTest.
This might seem reasonable at first glance, but running it gives the following error message:
  test
    1) FailTest failed after 1 test(s)

  1 failed

  1) FailTest:
      /Users/offtermatt/projects/interchain-security/tests/mbt/model/test.qnt:2:5 - error: [QNT502] Variable x is not set
      2:     var x: int
    Use --seed=0x2f54eaed29061 --match=FailTest to repeat.

  Use --verbosity=3 to show executions.
  Further debug with: quint --verbosity=3 test.qnt
/Users/offtermatt/projects/interchain-security/tests/mbt/model/test.qnt:2:5 - error: [QNT502] Variable x is not set
2:     var x: int
       ^^^^^^^^^^

error: Tests failed

In particular, the error message is test.qnt:2:5 - error: [QNT502] Variable x is not set
The real error seems to be from line 16, e.g. if I replace that line simply with inc, everything works fine.
I personally think the original test is probably reasonable and should work, but I don't understand the semantics of fail and then closely enough to be sure. However, if it is expected that it does not work, the error message should for sure point not to line 5, but in the best case to line 16, and it should be detectable during typechecking (just like having actions with different updates gives an error during typechecking).
$ quint --version
0.18.3

As far as I remember, fail does not expect any extensions of an execution. It's meant to be a terminal action. However, I agree that it is not obvious from the error message.

I see. I think it would be useful to allow fail inside traces - it can be useful to e.g. check that a certain action is disabled, even when the run itself is useful and we want to keep it going.
Would be nice to have, but probably not super high priority.


Ledger - Confirming receiving address

Thanks for adding Ledger support! Great!
Could you please add the possibility to confirm that the Receiving address shown in the Receive tab is actually part of the Ledger wallet? That is, the Receiving address should be possible to be shown in the Ledger device window. This is supported by the offical Chrome app for Ledger, so there should be an API call for this.

CashAddr is now supported as of 3.2


Feature request: Option for @state_trigger to only trigger once

I have an automation which turns on/off some exterior lights with a lux-sensor as input.
But the automation gets triggered every time the lux value changes and is above 50.
I have not found an option to make it only trigger once, and then not trig again until after the trigger-statement has been false.
@state_trigger( "int(sensor.lux_outside_the_garage) > 50" )
def automate_exterior_lights_off_in_morning():
    if pyscript.ext_light_off_done == 'off' and input_boolean.exterior_lights_wanted_state == 'on':
        input_boolean.exterior_lights_wanted_state = 'off'
        pyscript.ext_light_off_done = 'on'

One option is of course to add an extra condition , like this:
@state_trigger( "int(sensor.lux_outside_the_garage) > 50 and int(sensor.lux_outside_the_garage.old) <= 50")

Another option that allows you to intentionally set when the function will trigger, and when it will be allowed to trigger again.
@state_trigger( "int(sensor.lux_outside_the_garage) > 50" )
def automate_exterior_lights_off_in_morning():
    task.unique('exterior_lights', kill_me=True)
    if pyscript.ext_light_off_done == 'off' and input_boolean.exterior_lights_wanted_state == 'on':
        input_boolean.exterior_lights_wanted_state = 'off'
        pyscript.ext_light_off_done = 'on'
    task.wait_until(state_trigger="int(sensor.lux_outside_the_garage) < 50")

A third option: create a binary sensor template in Home Assistant for lux > 50 and use that in your state_trigger.
Or a fourth option, use a global variable as a binary sensor template of sorts and do it all in pyscript... (untested)...
TRIGGER_STATE = None

@time_trigger("startup")
@state_trigger("sensor.lux_outside_the_garage")
def automate_exterior_lights_off_in_morning(value=None):
    global TRIGGER_STATE

    if int(value) > 50:
        if TRIGGER_STATE == 'off':
            if pyscript.ext_light_off_done == 'off' and input_boolean.exterior_lights_wanted_state == 'on':
                input_boolean.exterior_lights_wanted_state = 'off'
                pyscript.ext_light_off_done = 'on'
        TRIGGER_STATE = 'on'
    else:
        TRIGGER_STATE = 'off'

Thanks for your good solution. The last one was more what I had in mind.
Would it be possible to build in your last solution as an option in the trigger, to keep the automation clean ? Like:
@state_trigger( "int(sensor.lux_outside_the_garage) > 50", armOnFalse=true)
def automate_exterior_lights_off_in_morning():
    ...

I think that this kind of problem only occurs when you have a state that's not binary like lux and temperature.

@craigbarratt can speak to weather a feature like this should be in PyScript. I agree that it's useful. It can even affect binary states when there is an "or" in the condition.
In your particular case, it seems you may already be keeping track of this and it could be handled with a state_active()?
@state_trigger( "int(sensor.lux_outside_the_garage) > 50" )
@state_active("pyscript.ext_light_off_done == 'off' and input_boolean.exterior_lights_wanted_state == 'on'")
def automate_exterior_lights_off_in_morning():
        input_boolean.exterior_lights_wanted_state = 'off'
        pyscript.ext_light_off_done = 'on'

Deciding how to express this cleanly in syntax is the most difficult part, in my opinion. "arm_on_false" isn't particularly easy to understand. A different kwarg, perhaps? Or, a "pseudo variable" like "last_eval" available to state_active... so that this would work:
@state_trigger('int(sensor.lux) > 50')
@state_active('not last_eval')
def a():
  light.exterior.turn_on()

Or maybe a different decorator entirely to indicate this functionality?

Thanks for the suggestion, and all the different ideas.  It seems the first option
@state_trigger( "int(sensor.lux_outside_the_garage) > 50 and int(sensor.lux_outside_the_garage.old) <= 50")

is the cleanest approach until we add a new feature.
I'm warming up to the idea of adding a new optional argument to @state_trigger, but I'm struggling with finding an informative parameter name that isn't too long.  Perhaps it could be state_was_false?
Another issue is how to handle start up - specifically, how is the first trigger handled when state_was_false is True?  How about this:

if state_check_now=False (which is default), then the first trigger succeeds; it doesn't need to previously be False
if state_check_now=True, then the trigger is checked at startup; if that check is False then the next trigger will succeed.  If it's True immediately, we ignore it and continue to wait until the trigger is False before the next trigger succeeds.

That way you get get either behavior (ie, requiring False first or not) by combining state_check_now with state_was_false.
Do we also need a state_hold_false parameter so that the False value has to be held for that long; any earlier True triggers will be ignored?  Or could we just use state_hold to mean both True and False hold times?  I'd rather avoid adding more parameters unless they are really essential.
This is sounding a bit complicated....

Perhaps we could just have a single new parameter state_hold_false, default None?  It seems easier to explain: "the trigger expression must be False for this amount of time in seconds before a positive value causes a trigger.  The default of None is easy to understand.  A value of 0 means it does have to be False.  A value >0 means it has to be False for at least that amount of time.

I'm rolling this state_hold_false=None/0/1+ around. I like the name because it works just like state_hold, but for the "false" side of the trigger. It covers every use case I can think of, as well.

When I started to use Home Assistant and discovered this fantastic pyscript-integration (Thank you so much for this !) a couple of weeks ago, I was surprised that triggers re-trigger on every value change. I think this happens both in yaml-automations and in pyscript with @state_trigger.
To me, the function of a trigger means something that triggers on an event and then don't re-triggers as long as the condition is still true. If it retriggers then it's a more of a condition than a trigger.
Question: Do you have a forum for pyscript, or is it correct to lift this kind of questions as an github-issue ?
Thanks so much for your support !

Github issues are definitely a good place to post feature requests, and this discussion is definitely appropriate for a Github issue.
No, there isn't a forum for pyscript. I haven't thought about creating a forum, nor do I know where a good place would be to host it. As more people start using pyscript, a forum could be helpful. Suggestions are welcome.

Can't we just use the normal community forum but with a subcategory like AppDaemon
https://community.home-assistant.io/c/third-party/appdaemon/21
In that way it will also create more buzz in the normal HA community.

I think this happens both in yaml-automations and in pyscript with @state_trigger.

Yes and no.
If you write your YAML automation like this, it'll trigger over and over again. Additionally, this is currently what a pyscript state_trigger is the equivalent to in Home Assistant.
- alias: triggers over and over
  trigger:
    - platform: state
      entity_id: sensor.lux
  condition:
    - platform: template
      value_template: "{{ states('sensor.lux')|int > 50 }}"

But when you use a template trigger, it will only trigger when the "True/False" state of the entire template changes from False to True. I think most people would write this automation this way:
- alias: only triggers once
  trigger:
    - platform: template
      value_template: "{{ states('sensor.lux')|int > 50 }}"

This alternate syntax is also available:
- alias: only trigger once alt
  trigger:
    - platform: numeric_state
      entity_id: sensor.lux
      above: 50

Ah, yes, you are correct. The following trigger (Numeric state trigger), triggers only one time when the value passes below 50, which is also described in the documentation: ".....fires if the value is changing from above to below or from below to above the given threshold."
automation:
  - alias: Test of numeric_state-below automation
    trigger:
    - platform: numeric_state
      entity_id: sensor.lux_outside_the_garage
      below: 50

Could it be good for similarity with the yaml-config to have a matching @numeric_state_trigger() ? But on the other hand, yaml has a lot of different special triggers (sun, tag .... )

I'd like to chime in and say I also found this confusing. If the trigger continues triggering after it reaches the met condition--what's the difference between @state_trigger and @state_active? Seems like they behave the same in this case.

Can't we just use the normal community forum but with a subcategory like AppDaemon
https://community.home-assistant.io/c/third-party/appdaemon/21
In that way it will also create more buzz in the normal HA community.

Sounds like a good idea.  How do I create a 3rd-party forum?

@craigbarratt I think a moderator has to do it for you. I'll see if I can figure out who that might be.

Thank you so much ! Very nice and clear documentation too !

@craigbarratt this looks great!!

Closing this since it's now supported, but discussion of startup case continue in #95.


fixes #191

https://github.com/intel/dffml/blob/6dd23ba005772ca3292f1a67010f55af77508a72/dffml/base.py#L273
ast was being used but wasn't imported.


pip install celiagg Fails on MacOS Python 3.11

May fail on other platforms as well - haven't tested yet.
Collecting celiagg
  Using cached celiagg-2.1.3.tar.gz (737 kB)
  Preparing metadata (setup.py) ... done
Installing collected packages: celiagg
  DEPRECATION: celiagg is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  Running setup.py install for celiagg ... error
  error: subprocess-exited-with-error

  × Running setup.py install for celiagg did not run successfully.
  │ exit code: 1
  ╰─> [305 lines of output]
      Cython does not appear to be installed.  Will attempt to use pre-made cpp file...
      running install
      /Users/cwebster/.venvs/enable/lib/python3.11/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build/lib.macosx-12.0-x86_64-cpython-311
      creating build/lib.macosx-12.0-x86_64-cpython-311/celiagg
      copying celiagg/__init__.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg
      creating build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_transform.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_font.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_no_text.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/__init__.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_canvas.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_drawing.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_state.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_text.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_path.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      copying celiagg/tests/test_paint.py -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/tests
      creating build/lib.macosx-12.0-x86_64-cpython-311/celiagg/data
      copying celiagg/data/OFL.txt -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/data
      copying celiagg/data/Montserrat-Regular.ttf -> build/lib.macosx-12.0-x86_64-cpython-311/celiagg/data
      running build_ext
      building 'celiagg._celiagg' extension
      creating build/temp.macosx-12.0-x86_64-cpython-311
      creating build/temp.macosx-12.0-x86_64-cpython-311/agg-svn
      creating build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4
      creating build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/font_freetype
      creating build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src
      creating build/temp.macosx-12.0-x86_64-cpython-311/celiagg
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/font_freetype/agg_font_freetype.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/font_freetype/agg_font_freetype.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/font_freetype/agg_font_freetype.cpp:18:
      In file included from agg-svn/agg-2.4/font_freetype/agg_font_freetype.h:27:
      In file included from agg-svn/agg-2.4/include/agg_scanline_storage_aa.h:30:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      In file included from agg-svn/agg-2.4/font_freetype/agg_font_freetype.cpp:18:
      In file included from agg-svn/agg-2.4/font_freetype/agg_font_freetype.h:35:
      agg-svn/agg-2.4/include/agg_trans_affine.h:295:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:303:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:311:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double d = determinant_reciprocal();
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:312:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double a = (*x - tx) * d;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:313:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double b = (*y - ty) * d;
              ^~~~~~~~~
      agg-svn/agg-2.4/font_freetype/agg_font_freetype.cpp:115:18: warning: variable 'len' set but not used [-Wunused-but-set-variable]
              unsigned len = 0;
                       ^
      7 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_arc.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_arc.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_arc.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_arc.h:24:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_arrowhead.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_arrowhead.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_arrowhead.cpp:20:
      In file included from agg-svn/agg-2.4/include/agg_arrowhead.h:22:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_bezier_arc.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_bezier_arc.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_bezier_arc.cpp:23:
      In file included from agg-svn/agg-2.4/include/agg_bezier_arc.h:24:
      In file included from agg-svn/agg-2.4/include/agg_conv_transform.h:22:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      In file included from agg-svn/agg-2.4/src/agg_bezier_arc.cpp:23:
      In file included from agg-svn/agg-2.4/include/agg_bezier_arc.h:24:
      In file included from agg-svn/agg-2.4/include/agg_conv_transform.h:23:
      agg-svn/agg-2.4/include/agg_trans_affine.h:295:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:303:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:311:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double d = determinant_reciprocal();
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:312:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double a = (*x - tx) * d;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:313:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double b = (*y - ty) * d;
              ^~~~~~~~~
      6 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_bspline.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_bspline.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_bspline.cpp:20:
      In file included from agg-svn/agg-2.4/include/agg_bspline.h:23:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_color_rgba.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_color_rgba.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_curves.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_curves.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_curves.cpp:17:
      In file included from agg-svn/agg-2.4/include/agg_curves.h:20:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      agg-svn/agg-2.4/src/agg_curves.cpp:24:18: warning: unused variable 'curve_distance_epsilon' [-Wunused-const-variable]
          const double curve_distance_epsilon                  = 1e-30;
                       ^
      2 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_embedded_raster_fonts.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_embedded_raster_fonts.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_embedded_raster_fonts.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_embedded_raster_fonts.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_gsv_text.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_gsv_text.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_gsv_text.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_gsv_text.h:23:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      In file included from agg-svn/agg-2.4/src/agg_gsv_text.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_gsv_text.h:25:
      In file included from agg-svn/agg-2.4/include/agg_conv_transform.h:23:
      agg-svn/agg-2.4/include/agg_trans_affine.h:295:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:303:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:311:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double d = determinant_reciprocal();
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:312:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double a = (*x - tx) * d;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:313:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double b = (*y - ty) * d;
              ^~~~~~~~~
      6 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_image_filters.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_image_filters.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_image_filters.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_image_filters.h:23:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_line_aa_basics.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_line_aa_basics.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_line_aa_basics.cpp:17:
      In file included from agg-svn/agg-2.4/include/agg_line_aa_basics.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_line_profile_aa.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_line_profile_aa.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_line_profile_aa.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_renderer_outline_aa.h:18:
      In file included from agg-svn/agg-2.4/include/agg_array.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_rounded_rect.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_rounded_rect.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_rounded_rect.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_rounded_rect.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_sqrt_tables.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_sqrt_tables.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_sqrt_tables.cpp:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_trans_affine.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_trans_affine.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_trans_affine.cpp:19:
      In file included from agg-svn/agg-2.4/include/agg_trans_affine.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      In file included from agg-svn/agg-2.4/src/agg_trans_affine.cpp:19:
      agg-svn/agg-2.4/include/agg_trans_affine.h:295:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:303:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double tmp = *x;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:311:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double d = determinant_reciprocal();
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:312:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double a = (*x - tx) * d;
              ^~~~~~~~~
      agg-svn/agg-2.4/include/agg_trans_affine.h:313:9: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
              register double b = (*y - ty) * d;
              ^~~~~~~~~
      6 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_trans_double_path.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_trans_double_path.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_trans_double_path.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_math.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      agg-svn/agg-2.4/src/agg_trans_double_path.cpp:25:9: warning: field 'm_kindex2' will be initialized after field 'm_base_length' [-Wreorder-ctor]
              m_kindex2(0.0),
              ^~~~~~~~~~~~~~
              m_base_height(1.0)
      2 warnings generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_trans_single_path.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_trans_single_path.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_trans_single_path.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_math.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_trans_warp_magnifier.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_trans_warp_magnifier.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_bspline.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_bspline.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_bspline.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_bspline.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_contour.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_contour.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_contour.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_contour.h:19:
      In file included from agg-svn/agg-2.4/include/agg_math_stroke.h:23:
      In file included from agg-svn/agg-2.4/include/agg_math.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_dash.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_dash.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_dash.cpp:21:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_dash.h:22:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_markers_term.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_markers_term.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_markers_term.cpp:20:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_markers_term.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_smooth_poly1.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_smooth_poly1.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_smooth_poly1.cpp:20:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_smooth_poly1.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vcgen_stroke.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vcgen_stroke.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vcgen_stroke.cpp:20:
      In file included from agg-svn/agg-2.4/include/agg_vcgen_stroke.h:19:
      In file included from agg-svn/agg-2.4/include/agg_math_stroke.h:23:
      In file included from agg-svn/agg-2.4/include/agg_math.h:23:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vpgen_clip_polygon.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vpgen_clip_polygon.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vpgen_clip_polygon.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_vpgen_clip_polygon.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vpgen_clip_polyline.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vpgen_clip_polyline.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vpgen_clip_polyline.cpp:16:
      In file included from agg-svn/agg-2.4/include/agg_vpgen_clip_polyline.h:19:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c agg-svn/agg-2.4/src/agg_vpgen_segmentator.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/agg-svn/agg-2.4/src/agg_vpgen_segmentator.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      In file included from agg-svn/agg-2.4/src/agg_vpgen_segmentator.cpp:17:
      In file included from agg-svn/agg-2.4/include/agg_vpgen_segmentator.h:20:
      agg-svn/agg-2.4/include/agg_basics.h:231:13: warning: 'register' storage class specifier is deprecated and incompatible with C++17 [-Wdeprecated-register]
                  register unsigned q = a * b + (1 << (Shift-1));
                  ^~~~~~~~~
      1 warning generated.
      /usr/bin/clang -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -pipe -Os -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -D_USE_FREETYPE -D_ENABLE_TEXT_RENDERING -Iagg-svn/agg-2.4/include -Iagg-svn/agg-2.4 -Iceliagg -I/Users/cwebster/.venvs/enable/lib/python3.11/site-packages/numpy/core/include -Iagg-svn/agg-2.4/font_freetype -I/Users/cwebster/.venvs/enable/include -I/opt/local/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11 -c celiagg/_celiagg.cpp -o build/temp.macosx-12.0-x86_64-cpython-311/celiagg/_celiagg.o -Wfatal-errors -Wno-unused-function -std=c++11 -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I/opt/local/include
      celiagg/_celiagg.cpp:224:12: fatal error: 'longintrepr.h' file not found
        #include "longintrepr.h"
                 ^~~~~~~~~~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> celiagg

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

Seems related to https://github.com/cython/cython/pull/4428

On the other hand pip install -e . seems to work.  Has this been resolved since last release?

Nope - problem is probably that sdist was generated with an old Cython which is incompatible with Python 3.11.  Regenerating the sdist with current Cython would likely fix (or not shipping the generated C/C++ files in the sdist).

I'm actually having the same same problem (I'm also MacOS, python3.11)... Will installed from git source then


Fix POSIX compliance on bootstrap

./script/bootstrap  was failing on linux
./script/bootstrap: 8: ./script/bootstrap: [[: not found

Fixed by using POSIX compliant [ instead of [[

👍  thanks!


WMS service will occupy 3dtiles network request resources

WMS service will occupy 3dtiles network request resources, which leads to the slow loading of 3dtiles. How can I solve this problem?

There was some discussion on this issue here: https://github.com/CesiumGS/cesium/issues/5954.
If you are seeing a significant delay in 3D Tiles loading when having an imagery layer in the scene, please provide a minimal Sandcastle example that demonstrates this issue.

Closing since no reproducible example was provided.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter swiss-weather-api for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.swiss-weather-api
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.5.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 4.1.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E157] js-controller 3.3.22 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E254] Version "2.0.1" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W529] Plugin "manual-review" missing at .releaseconfig.json. Please add.
[ ] :eyes: [W951] .npmignore found but "files" is used at package.json. Please remove .npmignore.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 13 Sep 2024 13:39:21 GMT based on commit 82276c9d7fb6dda69499c3d6e193a682eaabf7d0
ioBroker.repochecker 3.0.5

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E951] .npmignore found but "files" is used at package.json. Please remove .npmignore.
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[W951] .npmignore found but "files" is used at package.json. Please remove .npmignore.


Run all tests in a package ?

When I right click on a directory, I can "Run 'All tests'" but this is launched with jUnit runner plugin (hence, for ex, you can not click on a test name to navigate to the source)
I tried to create a configuration manually but it seems there is no option to launch on a directory (or package)
For ex, that would be the same as when you create a jUnit configuration, you have the option 'Test kind' that can be set to 'All in package'

For some reason I always get surprised when people run All tests. I've never seen that intention in my life xD
I suppose you can still run all tests via ./gradlew test for now, until we create an intention for all tests with KT

Just to explain more context.
The goal is not to run all tests of project (I indeed use that sometimes when I refactor the db or ... but this is unusual).
However, I often run all tests of a package (the package I am working on)
Also, note that running all tests with the jUnit plugin works, the problem is just that you can not navigate to a specific test failure (now that I installed the plugin, I navigate to the test and then run only the failing test so this is far better than before for me)

Yeah, JUnit's integration with Gradle wasn't a big priority for Gradle's team, and some features that we need are not yet available
That's why we don't have a very nice integration with JUnit right now (and probably never will).
Your report makes sense, thanks for it!

I need to update the plugin to capture the "run all tests" action.

Ehm, the intention of running all tests is pretty clear - to make sure that you did not break something seemingly unrelated to the feature you are working on.

It is, yes.
Currently we can execute all tests with gradlew test.

Afaik running all tests with Gradle does not allow you to jump to the source of failed tests by clicking them in the run window, while this is possible when the tests are run with the plugin via "Run x".
To me it seems that this is actually a pretty desirable feature and executing via "Run all tests" is just more beneficial than the Gradle task.

Does right click on a package name not show the run all tests option? Using plugin 1.0.5+

Oh, it does. I was under the assumption that this is still an open point as both related issues were closed with wontfix, but it seems like this is supported now? 😄
I'm currently unable to really use the plugin because of https://github.com/mockk/mockk/issues/459 and just found this issue, but I should have made sure that this is even still relevant before reviving this thread. Sorry about that.
Thanks for clarifying!

Are you using intellij or android studio
On Mon, 20 Jul 2020, 07:47 Christian Stoenescu<EMAIL_ADDRESS>wrote:

Oh, it does. I was under the assumption that this is still an open point
as both related issues were closed with wontfix, but it seems like this
is supported now? 😄
I'm currently unable to really use the plugin because of mockk/mockk#459
https://github.com/mockk/mockk/issues/459 and just found this issue,
but I should have made sure that this is even still relevant before
reviving this thread. Sorry about that.
Thanks for clarifying!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/16#issuecomment-661014927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGQDOE6FEVPA3LS3BL3R4Q4FFANCNFSM4HJ4KO4A
.

I'm using Android Studio.

It seems to be a problem with the classpath setup in AS.
On Mon, 20 Jul 2020 at 08:30, Christian Stoenescu<EMAIL_ADDRESS>wrote:

I'm using Android Studio.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/16#issuecomment-661040662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGTIRKSR3MOYPCMOZSDR4RBHZANCNFSM4HJ4KO4A
.

Is there a workaround? I'm experiencing the same issue.

Even though the last few comments were unrelated to the topic, I can confirm that with the latest Kotest plugin version (1.1.9) everything seems to be working fine in Android Studio 🎉

Is this really solved? For me using plugin version 1.1.49-IC-213-EAP-SNAPSHOT it still does not use kotest to run tests if I right click on a package and select "Run tests" (see screenshot)

What output do you get ?


[WIP] Fix #379, Enum with 0 value not shown on Example

See #379
The bug seems to be caused by
https://github.com/commandlineparser/commandline/blob/4d69a3898b84c821161b2db948075cd9e162832c/src/CommandLine/UnParserExtensions.cs#L251
returned to
https://github.com/commandlineparser/commandline/blob/4d69a3898b84c821161b2db948075cd9e162832c/src/CommandLine/UnParserExtensions.cs#L124
I ran all tests after the change and none of them failed.

+1
That fix the bug

My change caused another issue so you might want to close this.
see https://github.com/commandlineparser/commandline/issues/379#issuecomment-498055220

Instead of closing the Pr, you can convert the PR to WIP (Work In Progress) by modifying the title and add WIP as a prefix, and take your time to resolve the side effect.
I think these  methods are  needed to be added:
  object  GetDefaultValue(this OptionSpecification option )
  {
    //get the default value from the specification of option
  }

bool  HasDefaultValue(this OptionSpecification option )
  {
    //if  the option has a default value from specification return  true otherwise return false
  }

and  IsEmpty()  can be  based on the computation of these methods.
I see IsEmpty() is calculated from the default value of the  BaseType and it should also calculated based on its spec Default.
L252
        if (value is ValueType && value.Equals(value.GetType().GetDefaultValue())) return true;

Sure, I'll give it a try this week or the next

The best I could do was to change it to:
if (!spec.Required && value is ValueType && value.Equals(value.GetType().GetDefaultValue())) return true;
This solves the issue by always including required value types, and skipping non-required ones which have a default value.
At first I tried replacing the line with this:
if (spec.HasDefaultValue() && value.Equals(spec.DefaultValue.FromJust())) return true;

but it broke some UnParserExtensionsTests.
For example:
UnParsing_instance_returns_command_line
Message: Expected string to be equivalent to
"-i 1 2 3" with a length of 8, but
"-i 1 2 3 0" has a length of 10.

The BaseType default was included even though it wasn't supposed to be.


Separation between build and generate

Describe the feature
Is there an option in the roadmap that allows build and generate separately?
Imagining an image that contains a build (uses nuxi build) and the entrypoint only runs nuxi generate but reuses the previously generated build.
I was trying out the buildCache but unfortunately it always builds everything during generate even if the build was generated in the image itself.
I have been using 2 patches:

Nuxi - Not cleaning buildDir when generate runs
Nuxt - Not calling bundle(nuxt) when generate runs

And I'm using a fixed buildId.
This has allowed me to run both build and generate separately but with future.compabilityVersion = 4 I can no longer work with it, which is fine since patches are always something that shouldn't be done and I can live without them.
I also checked for recent issues/PRs regarding similar situations and ended up reaching #8142, #14605, #28726.
As I understood by @danielroe comment, this is something that the team wants to implement and one of the first steps was #28726, will this expand? Since it doesn't cache the whole build, just the client.
With buildCache it could potentially implement the whole idea if it caches the entire build
Additional information

[x] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[x] Read the contribution guide.
[x] Check existing discussions and issues.

This indeed should be possible already (as far as nuxt builds - the nitro build will still be called) and if it isn't, it's a bug. Would you provide a reproduction to show what you are trying?


[TASK] Streamline doc style, fix some typos

Coverage remained the same at 24.045% when pulling ddd6d5aae538ff0221f76a0680a5e484acb349e1 on afoeder:patch-1 into aac66263e833a2265d793f1f22b80962086a36bf on prooph:master.


[style]: Want to design project page

What's the style idea?
We need to improve  the project designing section . AS it can be more attractive by replacing buttons to other style, also by changing the box style. As a designer I want you to please assign me this task so that I can start working for this project.
Add screenshots
Add screenshots

Code of Conduct

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

hey, @Ks103 someone is working on this page. we will also add a search bar & some features.


Bundle generation using generate:bundle command does not work

$ php bin/console generate:bundle

  Welcome to the Symfony bundle generator!

Are you planning on sharing this bundle across multiple applications? [no]:

Your application code must be written in bundles. This command helps
you generate them easily.

Give your bundle a descriptive name, like BlogBundle.
Bundle name: BlogBundle

Bundles are usually generated into the src/ directory. Unless you're
doing something custom, hit enter to keep this default!

Target Directory [src/]:

What format do you want to use for your generated configuration?

Configuration format (annotation, yml, xml, php) [annotation]:

  Bundle generation

> Generating a sample bundle skeleton into app/../src/BlogBundle
  created ./app/../src/BlogBundle/
  created ./app/../src/BlogBundle/BlogBundle.php
  created ./app/../src/BlogBundle/Controller/
  created ./app/../src/BlogBundle/Controller/DefaultController.php
  created ./app/../tests/BlogBundle/Controller/
  created ./app/../tests/BlogBundle/Controller/DefaultControllerTest.php
  created ./app/../src/BlogBundle/Resources/views/Default/
  created ./app/../src/BlogBundle/Resources/views/Default/index.html.twig
  created ./app/../src/BlogBundle/Resources/config/
  created ./app/../src/BlogBundle/Resources/config/services.yml
> Checking that the bundle is autoloaded
> Enabling the bundle inside app/AppKernel.php
  updated ./app/AppKernel.php
> Importing the bundle's routes from the app/config/routing.yml file
  updated ./app/config/routing.yml
> Importing the bundle's services.yml from the app/config/config.yml file
  updated ./app/config/config.yml

  Everything is OK! Now get to work :).

$ php bin/console

PHP Fatal error:  Uncaught Symfony\Component\Debug\Exception\ClassNotFoundException: Attempted to load class "BlogBundle" from namespace "BlogBundle".
Did you forget a "use" statement for another namespace? in /var/www/vagrant/app/AppKernel.php:19

Stack trace:
#0 /var/www/vagrant/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(450): AppKernel->registerBundles()
#1 /var/www/vagrant/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(116): Symfony\Component\HttpKernel\Kernel->initializeBundles()
#2 /var/www/vagrant/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(137): Symfony\Component\HttpKernel\Kernel->boot()
#3 /var/www/vagrant/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(124): Symfony\Bundle\FrameworkBundle\Console\Application->registerCommands()
#4 /var/www/vagrant/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(90): Symfony\Bundle\FrameworkBundle\Console\Application->add(Object(Symfony\Component\Con in /var/www/vagrant/app/AppKernel.php on line 19

Same to me. See #1097

Works fine with version 3.1 but not in versions 3.2, 3.3, 3.4

Tag v3.3.2 works fine too.

You need to make change in composer.json, change
        "psr-4": {
            "AppBundle\\": "src/AppBundle"
        },

to
        "psr-4": { "": "src/" },

This solved the issue for me

Well,maybe add bundle namespace to psr4 is better. Let me try.

I change

    "psr-4": {
        "AppBundle\\": "src/AppBundle"
    },

to
    "psr-4": {
        "AppBundle\\": "src/AppBundle",
        "AdminBundle\\": "src/AdminBundle"
    },

works fine. I believe that this can get better performance.

Any solution?

Any solution?

I'm not sure the generator should change the contents of the composer.json file.
But something that can be done is that the generator may check whether the file exists when autoloaded, if not, add a warning that the file is not covered by psr-4 rules.
WDYT?

Considering symfonfy flex does this command have any future at all? I doubt it.

Having the kernel in src/ should not prevent having bundles too especially when you need to override one, what would be the reason to stop supporting it?

Even though the recommendation is to have bundleless apps, Symfony still needs bundles to decouple some features into separate packages.
Therefore, having bundles is something that should be supported in any way. Especially when the command is able to generate boilerplate code needed in most third-party bundles.

I found the problem 😆
https://github.com/symfony/symfony-standard/pull/1048
But I don't understand why there is a pull request which brokes a command which the most users use @Pierstoval.
I mean okay, specify the namespaces looks great and everything but its like with NPM or Composer itself. If symfony users using php bin/console generate:bundle and after that everything is broken that is stupid. 😢
The composer commands modify the composer.json so that the bundle can do this, too. Why not. If everything is working well then 😄
So I think either it will be reverted or we update the generator bundle, too.

I wonder if this shouldn't be reported in the SensioGeneratorBundle repository instead. IMO the bundle could easily make sure that the autoloader is updated or report a message if the composer.json file could not be manipulated/found.

The #1048 PR was made to optimize autoloading, because having an empty namespace pointing to a directory has an impact on autoloading performances. Even though it's not documented, I think it's useful to get benefit from this small upgrade.
That certainly is the reason why in Flex the original namespace is App pointing to src/: autoloading performances, but I'm not sure.

There are two different problems, both reported on https://github.com/sensiolabs/SensioGeneratorBundle/issues/555 and https://github.com/sensiolabs/SensioGeneratorBundle/issues/558

Maybe should we just revert https://github.com/symfony/symfony-standard/pull/1048 while SensioGeneratorBundle isn't fixed? It looks like it creates a lot of problem for newcomers https://stackoverflow.com/questions/45151067/class-not-found-exception-in-appkernel-after-moving-to-symfony2-8-24#comment77274270_45151067

@dunglas I think the newcomers will read the documentation and know that they must add the bundle. https://symfony.com/doc/current/bundles/SensioGeneratorBundle/commands/generate_bundle.html
The problem is that "old" developers like I know the way it was with symfony2 and try to use it like it was.
So at the end nobody reads the documentation all the time they develope.
Like the certificated specialists who wondering that this way changed 😄

A lot of material still exist and don't use new best practices, and nobody will read this documentation :)
The generator should at least display a message pointing to this doc, or asking the user to copy a line in composer.json.

@dunglas This has been fixed some days ago. We did 2 things: first, we fixed the error message that was not displayed anymore when the generator was not able to register the bundle. Then, we added some docs about the issue.

That being said, we can also revert the change here if that helps. That does not make a big difference anyway.

In https://github.com/symfony/symfony-standard/issues/1098#issuecomment-313868965 I suggested that the SensioGeneratorBundle could try to update the autoload section in the composer.json file. Would that be an option in addition to the error reporting changes that have been made?

@xabbuh Indeed, that would be even better!


[TO-PR] [Twitter] Privacy Report Submission.

name: Twitter
ratings:
locationTracking: 0
dataRetention: 1
userControl: 0
darkPatterns: 0
crossSiteTracking: 0
summary: "/privacy-report-card/details/twitter"
reference: "https://google.com/privacy"
category: "privacy-report-detail"
Twitter's Privacy Policy - Summary

opksfsd

This issue was automatically created from an API call.


lvgl/lvgl.h: No such file or directory when using FT81X

Describe the issue
When building the project, if I use a development board such as the WROVER kit v4.1 it builds correclty however, if I select to use a screen driver such as the FT81x I get a compilation error
Code to reproduce the issue
standard git clone (with recursion) on master
Expected Results
build correcltly
Actual Results
../components/lvgl_esp32_drivers/lvgl_tft/EVE_config.h:41:10: fatal error: lvgl/lvgl.h: No such file or directory
 #include "lvgl/lvgl.h"
          ^~~~~~~~~~~~~
compilation terminated.

ESP32 Chip version
N/A
ESP-IDF version
tried it on v4.1.1 as well as 4.0
Development kit used
N/A
Development machine OS
Tried on windows 10 as well as windows 8.1
Compilation warnings/errors (if available)
ir/FT81x.c.obj -MF esp-idf\lvgl_tft\CMakeFiles\__idf_lvgl_tft.dir\FT81x.c.obj.d -o esp-idf/lvgl_tft/CMakeFiles/__idf_lvgl_tft.dir/FT81x.c.obj   -c ../components/lvgl_esp32_drivers/lvgl_tft/FT81x.c
In file included from ../components/lvgl_esp32_drivers/lvgl_tft/EVE.h:39,
                 from ../components/lvgl_esp32_drivers/lvgl_tft/FT81x.c:8:
../components/lvgl_esp32_drivers/lvgl_tft/EVE_config.h:41:10: fatal error: lvgl/lvgl.h: No such file or directory
 #include "lvgl/lvgl.h"
          ^~~~~~~~~~~~~
compilation terminated.
[925/934] Building C object esp-idf/lvgl_tft/CMakeFiles/__idf_lvgl_tft.dir/disp_spi.c.obj
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

If possible, copy the compilation log into a file and attach it here

Im having the same problem with FT810 display driver with 7 inch Satoz TFT.
It looks there is a bug in the driver

Hello @Mair
This line https://github.com/lvgl/lvgl_esp32_drivers/blob/master/lvgl_tft/EVE_config.h#L38 should resolve to #include "lvgl.h".
This was broken by commit https://github.com/lvgl/lvgl_esp32_drivers/commit/a2a00bd7455dc9cedfeeafe05c4d0e9dc54b5247 and then reverted (but not with git revert) by commit https://github.com/lvgl/lvgl_esp32_drivers/commit/a2a00bd7455dc9cedfeeafe05c4d0e9dc54b5247
https://github.com/lvgl/lvgl_esp32_drivers/blob/master/lvgl_tft/EVE_config.h was forgotten in the process.
@C47D  Can you move this issue to https://github.com/lvgl/lvgl_esp32_drivers repo?


Altair Visualization

Description
As an admin, I want to have a metric, visualization, of the progress of mentees, so that I can offer support to mentees that are not progressing. Using Altair, this project first checks to see if it can talk to the API. Then it pulls all the information from the API. We use the Experience Level retrieved from the API to produce an Altair bar chart visualization. There is still one null value that still needs to be removed in a future PR. The bar chart is then converted to a json script.  This json is not clean json, so we used json.loads() to convert the data to clean json. We then save the JSON object locally as a .json file. This step is not necessary for API implementation, but a potential way to send backend an example the json object to be used.
Dependencies that are required for this change.
requests, altair, and json
Contributors

Ryland Gomez
Dagim Bantikassegn
John Baker

Video Link
https://www.loom.com/share/654a9bdcb0674eb3a7c4181b9a0584a4?sharedAppSource=personal_library
Trello Link
https://trello.com/c/B2OnTRrc/151-as-an-admin-i-want-to-have-a-metrics-visualization-of-the-progress-of-mentees-so-that-i-can-offer-support-to-mentee
##This is a new feature.

[x] New feature
[x] This change requires a documentation update

Checklist:

[x] My code follows PEP8 style guide
[x] I have removed unnecessary print statements from my code
[x] My changes generate no errors
[x] No commented-out code
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Everything looks good to me, and good idea adding the generated sample .json to be referenced, that way if we need a quick file to transfer to backend as a working example, we have one ready to go! Solid work learning Altair and accessing the database successfully!


run prettier on all JS files in a monolithic make-things-pretty PR

@jdhoffa maybe you could run prettier on all JS files in a monolithic make-things-pretty PR?
Automatic processes making unrelated changes to PRs makes things more difficult to review/understand/track/etc.

Originally posted by @cjyetman in https://github.com/RMI-PACTA/pacta-dashboard-svelte/pull/115#discussion_r1869579571

I spent about a day doing this already to close https://github.com/RMI-PACTA/pacta-dashboard-svelte/issues/29
I don't plan to do that again.
I won't approve PRs that have failing CI checks.

you fixed linting, but you did not fix all the things that prettier wants to force us to do, so now whenever someone touches a JS file, prettier is going to force us to make all these formatting changes to things that have been there since long ago.
I'm not asking to submit PRs with un-pretty or un-linty lines (in the precise changes that I made in that PR). I'm asking that when I submit a PR I'm not forced to fix formatting that is not related to the PR. If you just make it do all the fixes you want it to do now, I'll be happy submitting PRs against the super awesome, beautiful, perfect code that is already there.

Please see: https://github.com/RMI-PACTA/pacta-dashboard-svelte/pull/115#discussion_r1869928802
That has already been done.
The changes were not "formatting", and were entirely related to your PR.

you're mixing up what the linter does and what prettier does.... they're not the same

https://github.com/RMI-PACTA/pacta-dashboard-svelte/blob/e3f8f5ac01fe4d46321e9febe38a3ed17b889d75/package.json#L13

you know what && mean, right? 🤣


typo: Double word "shares"

@nschonni : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Merging per Angela's approval in email.


React DataGrid example for Data Binding

Can you provide an example of a data grid implementation using React, with a focus on how to bind data to the Datagrid?

Hey I am a newcomer in this project and I would like to contribute

@Kunalp3127 one of the variants you may consider to get the value of DataGrid component in your React component:
`
const dataGridRef = useRef();
const [dataGridValue, setDataGridValue] = useState([]);
 {
          dataGridRef.current = form.getComponent('dataGrid');
        }}
        onChange={()=>{
          if (dataGridRef.current){
           setDataGridValue(dataGridRef.current.dataValue);
          }
        }}**
 />
`


Can add copyrights documentation to the website

We can add copy rights documentation so that when clicked copy right it will direct to copy right page of your website
Kindly assign me the work @GVishnudhasan under gssoc'24 extd label
like this

you can assign this task to me...


sharedUtilsshowLoading not disappear

Hello,I just started  learning ionic and I really like your application.
In login page when I don't insert anything  and click login button a showloading keep running.it's not disappear and doesn't show alert until I refresh page
but I can login normaly if I insert true email and password.
can you teach me how to fix this please

In this project, I have written the code to hide the loading icon.
Have you configured the app according to this tutorial:
https://www.youtube.com/watch?v=GKlnjdbmPxU&feature=youtu.be
Will let you know, if i find any bug or fixes !!


Convert coverage to xml before uploading

Codecov Report

Merging #7 (ff434ab) into main (de40f6e) will increase coverage by 7.31%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           main      #7      +/-   ##
=======================================
+ Coverage      0   7.31%   +7.31%
=======================================
  Files         0      15      +15
  Lines         0    1094    +1094
=======================================
+ Hits          0      80      +80
- Misses        0    1014    +1014

Impacted Files
Coverage Δ

pykdeconnect/client.py
0.00% <0.00%> (ø)

pykdeconnect/device_manager.py
0.00% <0.00%> (ø)

pykdeconnect/const.py
0.00% <0.00%> (ø)

pykdeconnect/helpers.py
0.00% <0.00%> (ø)

pykdeconnect/__main__.py
0.00% <0.00%> (ø)

pykdeconnect/plugins/ping.py
0.00% <0.00%> (ø)

pykdeconnect/plugin_registry.py
0.00% <0.00%> (ø)

pykdeconnect/devices.py
0.00% <0.00%> (ø)

pykdeconnect/payloads.py
0.00% <0.00%> (ø)

pykdeconnect/plugins/battery.py
0.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


with_structured_output format depends on whether we're using pydantic proper or pydantic.v1 namespace

Privileged issue

[X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

Issue Content

from pydantic.v1 import BaseModel
from pydantic import BaseModel as BaseModelV2

class Answer(BaseModel):
    answer: str

class Answer2(BaseModelV2):
    """"The answer."""
    answer: str

from langchain_openai import ChatOpenAI

model = ChatOpenAI()

model.with_structured_output(Answer).invoke('the answer is foo') # <-- Returns pydantic object

model.with_structured_output(Answer2).invoke('the answer is foo') # <--- Returns dict

There's a bug in the chat model when checking whether a pydantic model  (from pydantic import BaseModel) ends up being classified as not a pydantic model.
But if we fix that logic, we get stuck here:
https://github.com/langchain-ai/langchain/blob/232908a46d6371ff3d65381966ffe4831545cb25/libs/core/langchain_core/output_parsers/openai_tools.py#L177-L177
The code
class PydanticToolsParser(JsonOutputToolsParser):
    """Parse tools from OpenAI response."""

    tools: List[Type[BaseModel]]

Which will not work since JsonOutputToolsParser inherits from BaseModel as well

It also emits the wrong schema  in general for nested objects


Data at-rest encryption - for different services included in Epiphany.

New, more specific tasks defined.


Custom sorting with an array

Hi,
I've tried your example from issue  #319 and it doesn't work or doesn't work anymore?
How can I achieve a custom order on initalizing mixitup?
Thanks in advance
Rainer

Hi there,
Can you confirm you are using the latest version, v3.3.1?

Hi,
I don't expected such a fast response. Thank you!
No, I used v3.3.0 but changed to v3.3.1 and get the same error:
TypeError: 0 is read-only
0 ist the first element of targets.

Would you be able to post a link or recreation?

Hi,
yes, loaded my test to http://www.rrdata.de/dev/test/test.htm

Hi @nytwyk,
Thanks a lot for that. Yes this is a bug - this feature was actually broken for a long time and I only recently fixed it for general sorting after load, but forgot to check sorting on load. Looking at the issue, it should be a simple fix, but in the mean time, you can probably "fake", by sorting immediately after load like this:
const ids = [35, 33, 34];
const targets = ids.map(id => document.querySelector('[data-id="' + id + '"]'));

// Create mixer with animations disabled

const mixer = mixitup('.container', {
    animation: {enable: false}
});

// Immediately sort the container

mixer.sort(targets)
    .then(() => mixer.configure({
        // Re-enable animations for subsequent operations
        animation: {enable: true}
    }));


added report icon to the main menu

Added a "Report Icon" link to the menu to open the "Icon Update" template and simplify icon reporting in the main repository.

#49  I don't care one way or the other. If I was forced to choose, I wouldn't add it. A link to the website repo is not that relevant. The product is the icon library, the website is merely a showcase.
#58 is superseded by #39. We could close it, even.
#39 is good, and we should do it. It would also help add the third parties links (there is a ticket for that) and any other links necessary in the future

Could you leave comments with you thoughts for each of these on those particular issues?
The larger point, that brings those issues and this Pull Request together, is that (1) the header needs some work to begin with and (2) throwing more and more links in the header isn't sustainable; the link to the disclaimer (arguably) shouldn't even be there (we put it there for now because it's a very important link). By "do you have any ideas" I meant do you have any ideas on how we could redesign this in a more sustainable way? (apologies for not being very clear the first time around :sweat_smile:)

Could you leave comments with you thoughts for each of these on those particular issues?
The larger point, that brings those issues and this Pull Request together, is that (1) the header needs some work to begin with and (2) throwing more and more links in the header isn't sustainable; the link to the disclaimer (arguably) shouldn't even be there (we put it there for now because it's a very important link). By "do you have any ideas" I meant do you have any ideas on how we could redesign this in a more sustainable way? (apologies for not being very clear the first time around 😅)

I don't, but I know someone has because I saw a design for this menu with icons in an icon preview. I need to look for it.

I've added changes to this PR to conform to the changes in #99 . The icon I chose is a placeholder, if anyone has a different option, it's very likely to be better than this one

I personally don't think the chosen icon (see
preview) clearly conveys where the link is taking you - or even that it is a link at all (though it being next to the other links should make that somewhat clear, it could also just be interpreted as "there's a warning and we choose to put it here").
An alert symbol could mean so many things and, in my experience, is rarely used by itself as a button/link. If I visited the website as a new user, I would have no idea what this button did and I would definitely not expect it to take me to a new GitHub issue page.
I strongly feel like we should "add this because it's nice to have a convenient link on the website to report outdated icons" if there's even the slightest chance (a not-significant group of) people will get confused.
Also, the link should be https://github.com/simple-icons/simple-icons/issues/new?assignees=&labels=icon+outdated&template=icon_update.yml&title=Update%3A+.

I think this should definitely not be merged with the current icon. The current in no way communicates that it will let the user report an outdated icon. From my perspective it just look like an interactive warning, which if clicked will tell you what the warning is.
I have no suggestion for a better icon. I strongly believe we're better off not adding anything in this regard than adding something that is confusing. I think the only suitable solution is to do in text form. Also, we could perhaps start by adding a link like this to the README of the main project as a trail, to see if having something like this actually increases the number of outdated icons reported.
Also the link is incorrect, it should be: https://github.com/simple-icons/simple-icons/issues/new?labels=icon+outdated&template=icon_update.yml&title=Update%3A+

I think this should definitely not be merged with the current icon. The current in no way communicates that it will let the user report an outdated icon. From my perspective it just look like an interactive warning, which if clicked will tell you what the warning is.
I have no suggestion for a better icon. I strongly believe we're better off not adding anything in this regard than adding something that is confusing. I think the only suitable solution is to do in text form. Also, we could perhaps start by adding a link like this to the README of the main project as a trail, to see if having something like this actually increases the number of outdated icons reported.
Also the link is incorrect, it should be: https://github.com/simple-icons/simple-icons/issues/new?labels=icon+outdated&template=icon_update.yml&title=Update%3A+

Adding this as text is not an option after changing the menu to icons.
Unless it is added outside the menu, somewhere else.
A different icon could be a megaphone or a flag.
Adding the link in the Readme is fine. Not sure if one thing supersedes the other.
If it were up to me, the report outdate icon would be an option for each one of the icons, with a little flag, in the footer of the icon card (from left to right, it would be color div, icon for svg download, icon for colored svg download, icon for pdf download, icon to report outdated).

Adding this as text is not an option after changing the menu to icons.

Agreed that wasn't my suggestion. If it's text it should go somewhere else (as you suggested), probably somewhere else in the <header>. Alternatively, if we implement a sidemenu (that can also house the header links on small screens) we could put it in there.

A different icon could be a megaphone or a flag.

I don't think either of these, in the header, are good alternatives. I think the flag would be a reasonable candidate if we add it to the cards.

Adding the link in the Readme is fine. Not sure if one thing supersedes the other.

I would consider it unrelated, neither change depends on the other.

If it were up to me, the report outdate icon would be an option for each one of the icons, with a little flag, in the footer of the icon card (from left to right, it would be color div, icon for svg download, icon for colored svg download, icon for pdf download, icon to report outdated).

You could give it a try, but I think this would add too much HTML to the site right now. But hey, maybe it turns out it barely adds anything compared to the overall site :upside_down_face:
I do think this would be more realistic when we have pagination or lazy-loading implemented.

I do think this would be more realistic when we have pagination or lazy-loading implemented.

Isn't lazy loading implemented via HTML attribute already?

I meant lazy loading of the HTML content, not just lazy rendering the SVGs.

Closing this PR since we discussed adding the report icon to the card rather than the menu.


fix: replace deprecated function

Hi @matejvasek I added them on PR before.. https://github.com/knative/func/pull/2032 .. take a look


Feature: OpenAI Assistants API

The instrumentation-openai package should be able to capture calls to the OpenAI Assistants API. Specifically, it should be able to trace this program taken from the linked quickstart documentation:
import OpenAI from "openai";
const openai = new OpenAI({ apiKey: OPENAI_KEY });

async function main() {
  const assistant = await openai.beta.assistants.create({
    name: "Math Tutor",
    instructions: "You are a personal math tutor. Write and run code to answer math questions.",
    tools: [{ type: "code_interpreter" }],
    model: "gpt-4o"
  });
  const thread = await openai.beta.threads.create();
  const message = await openai.beta.threads.messages.create(
    thread.id,
    {
      role: "user",
      content: "I need to solve the equation `3x + 11 = 14`. Can you help me?"
    }
  );
  let run = await openai.beta.threads.runs.createAndPoll(
    thread.id,
    {
      assistant_id: assistant.id,
      instructions: "Please address the user as Jane Doe. The user has a premium account."
    }
  );
  if (run.status === 'completed') {
    const messages = await openai.beta.threads.messages.list(
      run.thread_id
    );
    for (const message of messages.data.reverse()) {
      console.log(`${message.role} > ${message.content[0].text.value}`);
    }
  } else {
    console.log(run.status);
  }
}

main();

Yes @michael-hhai! Do you plan on working on this?

Great @michael-hhai, I'll post it on slack as well maybe someone will want it

hey @nirga @michael-hhai  I would like to work on this.

Yes please @vr-varad go ahead!


Error compling sass

I compile sass with compass (sass v 3.4.9) and have following error:
error sass/materialize.scss (Line 353 of sass/components/_global.scss: ".collection .active" failed to @extend ".blue-text.lighten-4".
The selector ".blue-text.lighten-4" was not found.
Use "@extend .blue-text.lighten-4 !optional" if the extend should be able to fail.
)

BTW. This library is amazing and very well done!! Congs +1

I get the same error in Codekit when compiling :
Error: ".collection .active" failed to @extend ".blue-text.lighten-4".
       The selector ".blue-text.lighten-4" was not found.
       Use "@extend .blue-text.lighten-4 !optional" if the extend should be able to fail.
        on line 353 of /Library/WebServer/Documents/provo new/dist/sass/components/_global.scss

I've followed tip from the error message Use "@extend .blue-text.lighten-4 !optional" if the extend should be able to fail. and added !optional in line 353 of sass/components/_global.scss and then woks fine.

It seems to be a typo. The most up to date version should be fine

Fixed in 9e6a50841e68302bc2b6e3c79c3416b20c292208


[Numpy] numpy compatible invert

Description

add numpy compatible invert
add a helper function for checking if input or output is integer

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

add invert and its test
a helper function to check for checking if input and output is of type integer at  src/operator/operator_common.h type_is_int

Comments

pass CPU,GPU test, pylint, cpplint
Thank @haojin2 for reviewing

@mxnet-label-bot add [numpy]