Allow specifying optional window id for window commands

Suggested change
Allow specifying optional window id for window commands. If not specified, operate on floating window.
- yabai -m window <COMMAND>
+ yabai -m window [window-id] <COMMAND>

Motivation
I've written a script that I'm running on the signals window_created and window_focused that automatically floats non-resizable windows. I only need to run it on window_focused because I cannot run window --toggle float on background windows.
#! /usr/bin/env zsh

[[ "$(yabai -m query --windows --window ${2}) | jq '.resizable == 0 and .floating == 0')" == "true" ]] \
       && yabai -m window --toggle float

I see where you are going with this, and I also think it would be nice to be able to issue commands that interact with arbitrary windows, spaces, displays, based on the Id.
That said, I don't think the current signal design is a good fit for this particular job. Even if you could float an arbitrary window the way you do now, what will happen is:

a window is created
yabai reads properties and w/e, tiles window
signal triggers your script
the script causes the window to be untiled, marked as floating

Now there are in my opinion two issues, well more like annoyances, with this approach:

The window was tiled upon creation, changing its position and size - which remain even if later unfloated, unless manually repositioned/resized.

Unnecessary flicker when the window spawns, giving it a sloppy feel.

I haven't exactly thought this through yet, but if there was some way to override the default handler for certain types of events, you could hook into the event before it is processed. The event could then be in some sort of "pending" state while you do whatever. At the end of that script you'd then return/set some state and someone notify yabai that this event is ready to be processed. It would then be passed a long through the pipeline as usual.

interact with arbitrary windows, spaces, displays, based on the Id.

Yes. That's the end goal basically, although I'm not sure how feasible this is for spaces and displays.
You're right about the example flickering and not being nice. It was just that—an example, that was supposed to show how powerful this is. Entire yabai features could be prototyped using signals, then integrated into the actual window manager later on (e.g. this float-if-non-resizable feature).
Signals are currently unfit for returning a modified state because they are executed asynchronously, which I don't think should be given up for this feature.
There's definitely a lot to consider here.

Implemented on master. All window commands will now operate on the provided window, or the focused window if none is specified.
sample:
yabai -m window 1866 --space 2

yabai -m window 1866 --toggle float

..

Closing this. I don't see myself working on a system that would allow what I mentioned above in the near future, but it is probably something that will remain in the back of my head. If I suddenly find the problem to be an interesting problem to solve I'll start working on it automatically.

Also regarding the ability to specify an id or some form of selector for the space and display commands as well - I think the best way to go for now is to leave it as it, until  a useful feature or use-case which require said functionality can be found.


Multi-select in grid cell

Is it possible to have a "multi-select" in a grid cell ?
So the "Multi-Select" field from this example: http://w2ui.com/web/demos/#!forms/forms-2
in a Grid column?
Thank you.

It seems that the search popup is accepting the 'enum' type, but the grid itself is not :( , it gives the following error :
ERROR: input types "enum" and "file" are not supported in inline editing.

Yes. Multi select in the inline editing is turned off. The reason is because it requires more space then just the column width. I have thought about implement it and played with it, but it did not feel and behave nicely (IMHO).

Multi select in the inline editing is turned off. The reason is because it requires more space then just the column width.

One could require the user to give those columns more width, or render an elipsis button.
In most cases only a few values are required to be rendered, but not being able to do this at all is limiting: now instead of a simple editable grid, an extra "detail" form is required only to edit one field :( ).
The inline grid edit also allows to edit efficiently many fields before saving: having an extra form, breaks this too :(.

Please turn the multiselect inline editing on.
We need this functionality too, and now are using other frameworks for those screens just to be able to achieve such behavior :(.
Regarding the place problem, I think the default behavior for the multiselect (in a grid or not) could be not to span new lines but to hide text on the left, like it happens now even with HTML text fields when the width is smaller than the text length.
Thanks in advance.

In the grid.js, comment out these lines:
            if (['enum', 'file'].indexOf(edit.type) != -1) {
                console.log('ERROR: input types "enum" and "file" are not supported in inline editing.');
                return;
            }

line 2210-2213, and see how it behaves.

In the grid.js ...line 2210-2213, and see how it behaves.

Unfortunately it's not working correctly:

it's not rendering as in a form
I can select one element, but it's constantly hiding, so I can't select another one.
It picks wrongly when a field "value" changed

I did the change and added an example: https://github.com/aadrian/w2ui/commit/9d806636ef78159d11b0310d66abb2c765b59c24
grid-27 in the 'https://github.com/aadrian/w2ui/tree/multi_select_grid' branch
(it's based on the grid-21 example with an extra 'enum' column only)

Will this ever be addressed? It will be very valuable - please reopen and implement

Please reopen limited implementation at least


Extend the application-layer API to avoid hard-coded protocol-related constants in applications

This is an implementation and a demonstration in support of https://github.com/UAVCAN/public_regulated_data_types/pull/109.
Instead of specifying the port-ID explicitly when instantiating a port: node.presentation.make_publisher(Type, 1234)
Now, one uses indirection to source the port-ID from the registry: node.make_publisher(Type, 'my_subject')
The new node factory make_node() removes boilerplate and hard-coded identifiers.
Please find the documentation for this change on the readthedocs PR build site:

https://pyuavcan--154.org.readthedocs.build/en/154/pages/demo.html
https://pyuavcan--154.org.readthedocs.build/en/154/api/pyuavcan.application.html#module-pyuavcan.application

It would be super if one could follow the tutorial along to make sure that it doesn't omit any crucial details. If you do that, note that you will need to install Yakut from a branch for now (I will merge/release it immediately after this PR is accepted):
pip install git+https://github.com/UAVCAN/yakut@orc

I do not recommend reviewing the code because our limited resources are better spent on more important things.

Pull Request Test Coverage Report for Build 37991758

0 of 0   changed or added relevant lines in 0 files are covered.
77 unchanged lines in 12 files lost coverage.
Overall coverage increased (+0.2%) to 95.641%

Files with Coverage Reduction
New Missed Lines
%

/home/appveyor/projects/pyuavcan/pyuavcan/presentation/_port/_subscriber.py
1
82.76%

/home/appveyor/projects/pyuavcan/pyuavcan/application/heartbeat_publisher.py
2
96.4%

/home/appveyor/projects/pyuavcan/pyuavcan/dsdl/_builtin_form.py
2
97.2%

/home/appveyor/projects/pyuavcan/pyuavcan/transport/serial/_serial.py
2
92.73%

/home/appveyor/projects/pyuavcan/pyuavcan/application/diagnostic.py
3
93.02%

/home/appveyor/projects/pyuavcan/pyuavcan/application/_node.py
3
96.85%

/home/appveyor/projects/pyuavcan/pyuavcan/dsdl/_compiler.py
4
93.22%

/home/appveyor/projects/pyuavcan/pyuavcan/presentation/_port/_publisher.py
4
90.0%

/home/appveyor/projects/pyuavcan/tests/demo/_demo_app.py
7
97.12%

/home/appveyor/projects/pyuavcan/pyuavcan/application/plug_and_play.py
13
92.24%

Totals

Change from base Build 37726864:
0.2%

Covered Lines:
12859

Relevant Lines:
13293

💛  - Coveralls

I was trying to work through this and found a bug with the DSDL generation:
pydsdl._error.InternalError: /tmp/pyuavcan_demo/public_regulated_data_types/uavcan/diagnostic/8184.Record.1.1.uavcan:4: Conflicting definitions: [DSDLDefinition(full_name='uavcan.time.SynchronizedTimestamp', version=Version(major=1, minor=0), fixed_port_id=None, file_path='/tmp/pyuavcan_demo/public_regulated_data_types/uavcan/time/SynchronizedTimestamp.1.0.uavcan'), DSDLDefinition(full_name='uavcan.time.SynchronizedTimestamp', version=Version(major=1, minor=0), fixed_port_id=None, file_path='/tmp/pyuavcan_demo/public_regulated_data_types/uavcan/time/SynchronizedTimestamp.1.0.uavcan')]

I get this when running yakut compile public_regulated_data/uavcan on the master branch with the version of yakut you specified (not when running it with 0.1.5). It seems to come from this branch of pyuavcan but I haven't fully verified that.

It was fixed about one month ago: https://github.com/UAVCAN/pydsdl/pull/61
Please make sure you are running the latest PyDSDL: pip install -U pydsdl. I guess we should bump the minimal required version in Nunavut.

Okay with updated dependancies (python package management is just a joy...) I got everything to run well, except for orchestration but I'm assuming that's not important to this PR, and don't have too much time to play with this.
One nit is that the demo app's filename should probably be specified immediately prior to the code, the snippet given in "Running the Application" is the first reference to the filename used for the demo.

I got everything to run well, except for orchestration but I'm assuming that's not important to this PR

The directory removal problem should be fixed now but you are right, this is not that important.
Do you think such register integration can be implemented in uavcan.rs?

Do you think such register integration can be implemented in uavcan.rs?

Yep, although I don't plan on implementing it where I am currently working (which is roughly equivalent to the presentation layer in pyuavcan). I want the core uavcan-rs crate to be as general and cross-platform as possible.
A user-friendly "application" crate on top of the core crate would likely be what I would want to work on after I hit 1.0, and register integration is definitely a natural feature to add there.

A user-friendly "application" crate on top of the core crate would likely be what I would want to work on after I hit 1.0, and register integration is definitely a natural feature to add there.

Okay. I think it's critical though to make the application crate no-std as well. We don't want embedded developers to reinvent this wheel.

[ ]  Provide a step-by-step set of instructions for setting up the proper directory structure for the demo.
[ ] Move the "Just-in-time vs. ahead-of-time DSDL compilation" section to after "running the application section"
[ ] start with a sentence or two about what the demo is demonstrating.
[ ] Print a message from the demo that says "running. ctrl+c to exit"
[ ] The section on Yakut; it's not clear that the examples are all to be run as separate processes. Perhaps you should be explicit about the number of shells. Something like "in addition to the terminal running pyuavcan open four more sessions and start the following yakut listeners..."

Startup sometimes throws:
"Available registers do not encode a valid transport configuration: ['uavcan.can.bitrate', 'uavcan.can.iface', 'uavcan.can.mtu', 'uavcan.loopback', 'uavcan.node.description', 'uavcan.node.id', 'uavcan.node.unique_id', 'uavcan.serial.baudrate', 'uavcan.serial.duplicate_service_transfers', 'uavcan.serial.iface', 'uavcan.udp.duplicate_service_transfers', 'uavcan.udp.iface', 'uavcan.udp.mtu']"
  File "/nxp_linux/demo/demo.py", line 63, in __init__
    self._node = pyuavcan.application.make_node(node_info, DemoApp.REGISTER_FILE)
  File "/nxp_linux/demo/demo.py", line 169, in <module>
    app = DemoApp()

Startup sometimes throws:

It is supposed to do that when you run the application for the first time (i.e., the database file is not yet created) without exporting environment variables. Can you confirm that it happens after you export the variables?

Can we make this into a config file that is read into the demo app?

Kind of like this one? https://github.com/pavel-kirienko/yukon/blob/master/test.orc.yaml
In a way, that's what the last part of the tutorial is about.

$ yakut orc launch.orc.yaml
/bin/sh: 1: ncat: not found
2021-03-05 04:21:13 0031371 WAR yakut.cmd.orchestrate: Call stack: 'launch.orc.yaml' $ 6 ? 0
PID=00031396 Stopping (was started 0.0 sec ago)
2021-03-05 04:21:13 0031371 WAR yakut.cmd.orchestrate: Call stack: 'launch.orc.yaml' $ 2 $ 0
PID=00031384 Stopping (was started 0.1 sec ago)
2021-03-05 04:21:13 0031371 WAR yakut.cmd.orchestrate: Call stack: 'launch.orc.yaml' $ 3
PID=00031387 Stopping (was started 0.1 sec ago)
2021-03-05 04:21:13 0031371 WAR yakut.cmd.orchestrate: Call stack: 'launch.orc.yaml' $ 4
PID=00031390 Stopping (was started 0.1 sec ago)
Traceback (most recent call last):
  File "/nxp_linux/demo/.penv/bin/yakut", line 5, in <module>
    from yakut import main
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/__init__.py", line 15, in <module>
    from .main import main as main, subcommand as subcommand, Purser as Purser, pass_purser as pass_purser
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/main.py", line 13, in <module>
    from yakut.param.transport import transport_factory_option, TransportFactory, Transport
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/param/transport.py", line 9, in <module>
    import pyuavcan
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/__init__.py", line 72, in <module>
    import pyuavcan.dsdl as dsdl  # pylint: disable=wrong-import-position  # noqa
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/__init__.py", line 25, in <module>
    from ._compiler import compile as compile  # pylint: disable=redefined-builtin
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/_compiler.py", line 17, in <module>
    import pydsdl
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/__init__.py", line 25, in <module>
    from ._namespace import read_namespace as read_namespace                            # noqa
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/_namespace.py", line 12, in <module>
    from . import _dsdl_definition
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/_dsdl_definition.py", line 12, in <module>
Traceback (most recent call last):
    from . import _parser
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/_parser.py", line 127, in <module>
  File "/nxp_linux/demo/.penv/bin/yakut", line 5, in <module>
    class _ParseTreeProcessor(parsimonious.NodeVisitor):
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/_parser.py", line 139, in _ParseTreeProcessor
    grammar = parsimonious.Grammar(_grammar_file.read())  # type: ignore
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/grammar.py", line 69, in __init__
    from yakut import main
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/__init__.py", line 15, in <module>
    exprs, first = self._expressions_from_rules(rules, decorated_custom_rules)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/grammar.py", line 105, in _expressions_from_rules
    tree = rule_grammar.parse(rules)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/grammar.py", line 115, in parse
    return self.default_rule.parse(text, pos=pos)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 120, in parse
    node = self.match(text, pos=pos)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 135, in match
    node = self.match_core(text, pos, {}, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 333, in _uncached_match
    node = m.match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 427, in _uncached_match
    node = self.members[0].match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 333, in _uncached_match
    node = m.match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 356, in _uncached_match
    node = m.match_core(text, pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 333, in _uncached_match
    node = m.match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 458, in _uncached_match
    node = self.members[0].match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 356, in _uncached_match
    node = m.match_core(text, pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 333, in _uncached_match
    node = m.match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 333, in _uncached_match
    node = m.match_core(text, new_pos, cache, error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 178, in match_core
    error)
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pydsdl/third_party/parsimonious/expressions.py", line 279, in _uncached_match
    m = self.re.match(text, pos)
KeyboardInterrupt
    from .main import main as main, subcommand as subcommand, Purser as Purser, pass_purser as pass_purser
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/main.py", line 13, in <module>
    from yakut.param.transport import transport_factory_option, TransportFactory, Transport
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/yakut/param/transport.py", line 9, in <module>
    import pyuavcan
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/__init__.py", line 72, in <module>
    import pyuavcan.dsdl as dsdl  # pylint: disable=wrong-import-position  # noqa
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/__init__.py", line 29, in <module>
    from ._composite_object import serialize as serialize
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/_composite_object.py", line 16, in <module>
    from . import _serialized_representation
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/_serialized_representation/__init__.py", line 6, in <module>
    from ._serializer import Serializer as Serializer
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/pyuavcan/dsdl/_serialized_representation/_serializer.py", line 11, in <module>
    import numpy
  File "/nxp_linux/demo/.penv/lib/python3.7/site-packages/numpy/__init__.py", line 143, in <module>
    from . import lib
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 963, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 906, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1280, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1252, in _get_spec

Can you confirm that it happens after you export the variables?

Yeah. The ports and the IP coming from a config file would make this demo so much better.

@thirtytwobits check out my latest changes. I think I addressed everything except:

the environment variables for the port identifiers is clunky. Can we make this into a config file that is read into the demo app? This also makes it WAY easier to debug.

This is not really meant to be very human-friendly. I think it makes sense to start with the basics even if they are not particularly convenient and then gradually introduce more advanced matters like the orchestrator. The orchestration file is essentially the config file you are looking for, but if we introduce it from the start it may get confusing.

Log a warning from demo_app.py if the file is not called demo_app.py since the orc-file part of the tutorial will fail with a big ol' stack trace if you don't adhere to this convention.

I addressed this by making the demo easier to follow along step-by-step such that by the time the reader gets to the orchestrator the file should already be created. I also added another hint about this right after the orchestration script for good measure.

yakut pub --count 10 2345:uavcan.si.unit.temperature.Scalar.1.0 'kelvin: 250' ... example doesn't work (nothing is printed by yakut sub -M 2347:uavcan.si.unit.voltage.Scalar.1.0

Not reproducible, neither locally nor in CI.


Issues getting the Xref working

Having a few issues getting the pipeline with the Xref for unity working. I am using Azure pipelines and have all the documentation generating, but do not have the references to any unity behaviours.
When running it locally i have the names, but no links to the actual unity documentation (is it meant to have a link like it does to object?)
thanks for any pointers that may help

So i got a bit further, i have uploaded the site generated from the Xrefmaps to a new repo with its own github page and pointed the xref variable in the docfx.json to this .yml file. When generating the main documentation though local powershell this now works, however when generating though Azure pipelines it looks like its missing all the unity behaviour and just shows Object as a base class skipping all the unity stuff.

Hi, thank you for opening the issue!
The first problem you have is the same as #3. I'm near to fix it.
The generation of the Xref maps of the Unity API is almost good (can be found here). It's very long to generate them therefore I'm putting this program to a GitHub CI in order to generate them every week and push them on GitHub Pages. Thus they will be available for everyone to use. You won't have to generate them again as you did on your second message.
The second problem you have is the second purpose of the small generating program above: fix the generated links of the xref maps to point to the Unity API. It's almost working, some links are not perfectly handled, but I'm going to fix that too.
For your third problem (the warnings), I have no idea. I think it's related to DocFX. You could ask them by openning an issue on their repo?
I will keep you informed when the xref maps of the Unity API will be online.

I fixed #3, you can use the xref maps of the Unity API I generated.
On your docfx.json:
{
    ...
    "build": {
        ...
        "xref": [ "https://normanderwan.github.io/DocFxForUnity/Unity/xrefmap.yml" ],
        ...
    }
}

If you want a specific version of the Unity API, use instead: https://normanderwan.github.io/DocFxForUnity/Unity/<version>/xrefmap.yml where <version> is a Unity version in the form of YYYY.x (e.g. 2017.4, 2018.4 or 2019.3).

Thanks very much for the help, will run a generation later today and double check all the results, will go to docfx as well for the warning thats popping up.

Hi there
I've tried to regenerate it with the above changes, but its still missing out the field links to unity, not sure if i have missed something else though

Your setup is good, it's on my side. Thank you for pinpointing the problem! References are missing in the xrefmap.yml
I'm fixing it, I'll keep you informed

Sorry, I forgot to ping you.
References should be working now!
Could you try and tell me if it's all good on your side?

Hi there
Thanks for letting me know, i ran another cycle and looks like the links were still not generated for myself, was there any other changes i need to run/pull update into the docs folder (i just rerun the setup i had)

I'm closing the issue. Feel free to comment if you still have the problem, I will re-open it.


Fix mpi macos

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


Extraneous characters displayed in zsh output

I'm brand new to zsh, so this may be my mistake. The zsh examples given in the README and the usage message don't work for me, so I experimented and ended up using this:
%$(git-radar --zsh --fetch)

which results in this:
%{ git:(𝘮 34 ⇄ 65 feature/AUD-1140) 2A

note the '%{' at the beginning, which seems to be caused by the git-radar command, not by some other part of the prompt variable (this is a minimal working example). For what it's worth, within a longer PROMPT variable, the %{ is colored according to the preceding color escape codes.
This is on OS X Yosemite, in iTerm.

Can you post your export PROMPT line from the ~/.zshrc? I think what's happening is the % you've put at the front is escaping the first character in the non-printing character boundary, which is %{, so you get %{ output from %%{. That's my guess.
If I could see your .zshrc I can have a better look at it.

From ZSH Docs - Prompt Expansion:
If the PROMPT_PERCENT option is set, certain escape sequences that start with ‘%’ are expanded. Many escapes are followed by a single character, although some of these take an optional integer argument that should appear between the ‘%’ and the next character of the sequence. More complicated escape sequences are available to provide conditional expansion.

Here are the several different prompts I've tried:
`
my basic prompt, no color
#PS1="[%D %T] %~
#alan@MBP (%j/%!)$
result:
[15-10-21 10:56:26] ~/src
alan@MBP (0/30)$
my basic prompt, with color
#export PROMPT="%F{red}[%D %*] %~
#%F{red}alan@MBP (%F{cyan}%j%F{red}/%!)$%f "
result:
[15-10-21 10:56:26] ~/src
alan@MBP (0/30)$
my basic prompt, with color and git-radar
#export PROMPT="%F{red}[%D %*] %~%f %$(git-radar --zsh --fetch)
#%F{red}alan@MBP (%F{cyan}%j%F{red}/%!)$%f "
result:
[15-10-21 10:56:05] ~/src %{ git:(𝘮 402 ⇄ 8 feature/PLAT-187 1↑) 10M
alan@MBP (0/29)$
other attempts
#export PROMPT="%$(git-radar --zsh --fetch) $ "
result:
%{ git:(𝘮 402 ⇄ 8 feature/PLAT-187 1↑) 10M $
export PROMPT=$'$(git_radar) '
result:
$(git_radar)
#export PROMPT=$'$(git_radar --zsh --fetch) '
result:
$(git_radar --zsh --fetch)
`

Ok, I've got it figured out.
You've only just started with ZSH so likely you haven't actually enabled prompt expansion. It's not something ZSH does by default but most people turn it on.
To do that add this to ~/.zshrc:
setopt PROMPT_SUBST

Now use the form I suggested for your prompt:
export PROMPT=$'$(git-radar --zsh --fetch) '

I have a set of sane defaults I use at dotfiles/zsh/config.zsh. Most of them are commented but YMMV for which you like to use. zstyle ':completion:*' menu select is particularly nice as it lets you arrow key move through completions, making auto-complete feel so much more modern.
Welcome to ZSH!

That works, thanks!

Cool, closing.


Both old and new icons appear on Mac

VSCode Version: Code 1.17.2 (b813d12980308015bcd2b3a2f6efa5c810c33ba5, 2017-10-16T13:47:41.889Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

vscode-docker
Pet
0.0.21

npm-intellisense
chr
1.3.0

jshint
dba
0.10.15

vscode-eslint
dba
1.4.3

gitlens
eam
6.0.0

python
ms-
0.8.0

azure-account
ms-
0.2.2

(1 theme extensions excluded)

Steps to Reproduce:

Open code
There you go, there are two instances, one with the previous logo and one with the new logo.

When I open another project, it opens in the second instance, and then both instances are active.
When I open more than 2 projects, it gets really annoying, because both icons are active and I must guess which icon holds the 2 projects, and when I should use cmd+tab vs cmd+`...

Reproduces without extensions: Yes

I guess Mac caches the icon? Did you try updating to the latest version (v1.18)?

Yes looks like a caching issue, nothing we can do about.


can tensorflow lite be accelerated on android devices below 8.0? can renderscript or any gpu acceleration do the tricks?

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

thx, I'm a fresher, can you provide some advise to tune the performance to classify using tensorflow lite on android. it seems like with the same model, tensorflow lite run on IOS is much faster
btw, i run a test on nexus5x (android 8.1), it cost 800ms to classify a frame, but only 300ms on HUAWEI P9  i don't whether the nnapi is enabled?

Here's the documentation for tuning mobile models:
https://www.tensorflow.org/mobile/optimizing
For further advice, try StackOverflow, as this forum is for bug reports.

I have tested the tflite camera demo on Nexus5X (android 8.1), I found the prediction is slower using NNAPI than not using NNAPI, the time consumes about 500ms per frame when using NNAPI, while 300ms per frame when NNAPI turned off.
It is confused


Select on NgPrime

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior
When using the select input with the require field without the placeholder, it always stuck on validator require
Expected behavior
The Select work with the default value or with one value
Minimal reproduction of the problem with instructions
use for example this schema:
{
"key": "CurrencyId",
"type": "select",
"className": "form-group",
"templateOptions": {
"label": "Currency",
"options": [
{
"value": "1",
"label": "USD"
}
],
"required": true
}
}

Angular version: 5.2.11

Browser: all

Language: TypeScript 2.6.2

well I've just checked and it seems to be an NgPrime issue, there is nothing we can do in our side, sorry  about that!
it may be better to open an issue in NgPrime repot and use a placeholder until it get fixed or use the defaultValue:
{
  "key": "CurrencyId",
  "type": "select",
   "defaultValue": "1"
}


Use version range for soda sql spark

Closes #27. Waiting for a non pre-release version being published for soda-spark-sql

Requires a update due to #58

Closing this PR for now. Waiting for non-alpha releases for soda-sql


fix: Allow for empty S3 SecretKeyRef

Allow for empty S3 SecretKeyRef
Relates to: https://github.com/goharbor/harbor-operator/issues/794
Signed-off-by: Dave Griffiths<EMAIL_ADDRESS>

Please rebase the master branch. Thanks very much. @davidg-sainsbury

@yxxhero - Merged with master. Thanks.  Dave


shadow or drop-shadow wont work on Android or iOS

Describe the bug
shadow or drop-shadow classNames wont work on Android or iOS
To Reproduce
Steps to reproduce the behavior:
https://snack.expo.dev/R_A2j2wZ5

@crazywako try https://www.nativewind.dev/quick-starts/expo. In snack i saw you not installed tailwindcss in dev dependencies yet

The snacks cannot install tailwind due to its use of the crypto module for hashing. The snacks instead use an external compiler.
While strangely intermittent, I can reproduce the issue. I know how to fix the issue, but I want to do some internal refactoring to cleanly handle android/ios style props.

This should be fixed on latest, let me know if you have any issues. Like with RN shadow, the shadow utilities don't always work if a background color is not set.

@marklawlor shadow is still not working

Tailwind shadow refers to a box shadow. React Native <Text> elements do not support box shadows, only text shadows. TailwindCSS doesn't have a utility  class for the CSS prop text-shadow so there's no current way to apply a shadow to text. I'm thinking of adding custom classes to NativeWind based upon this package https://www.npmjs.com/package/tailwindcss-textshadow
Tailwind also has a drop-shadow utility, but there is no native equivalent.
As for the shadow on the view, can you try adding the shadow via inline styles. RN shadows are very buggy and often it's easier to make them work via inline styles and then convert that to Tailwind. If you can make it work with inline styles but not Tailwind, can you please link me an Expo snack demonstrating it.

@marklawlor not sure what the issue is with RN View Shadows, they are different on ios  and android but they work.
it would be nice if you make something similar to 'react-native-zephyr', it's not perfect but it works for now.

Had a similar issue, in spite of 'shadow' being set to a View component (not Text). What fixes it is to always add a shadow color after, for example: shadow-lg shadow-black/40.

shadow-lg shadow-black/40

Yeah had the same, adding the default style for the react-native element worked even better
<Pressable
  style={{
    shadowColor: "#000",
  }}
  className="bg-fuchsia-400 h-auto rounded-lg shadow-xl w-full"
  onPress={() => console.log("press")}
>
  <Text className="p-4 text-white font-bold text-md text-center">
    Button
  </Text>
</Pressable>

Had the same problem, fixed it by using @jeystaats solution but using a tailwind class shadow-black
<View className="p-3 rounded-full shadow- shadow-black"></View>


Improve handling of Aggregate errors in cmdutil.CheckErr

If no errors are included in the aggregate, simply return. If a single error included, treat as single error.

@jlowdermilk ptal

Thanks. I would not be surprised if this was triggering empty errors in weird edge cases. LGTM

Hrm... MultilineErrors already handles the single error case, and the zero error case.  Who is returning an empty aggregate error?

@smarterclayton - I don't know of any case where an empty aggregate error is thrown. However, single errors are not consistently handled. Motivation for this change is #5 here: https://github.com/openshift/origin/issues/2390#issue-78643798

Then shouldn't prefix be set?

Wouldn't it be too repetitive when you have multiple errors?

The point of multiple independent errors is either multiple failures on linear output - think create of 10 items, where 3 fail, and the errors aren't related, but you still want to show them on their own lines - or its typed errors with aggregate behavior like the configuration error.   In the former case you may have output that doesn't look like an error, so "error: " helps identify that.

On May 27, 2015, at 9:55 AM, Cesar Wong<EMAIL_ADDRESS>wrote:
Wouldn't it be too repetitive when you have multiple errors?
—
Reply to this email directly or view it on GitHub.

Removing LGTM tag - this does not appear to be resolved.  I don't think it should be needed.

@smarterclayton - changed the message for multiple errors to use the error prefix as in https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/util/helpers.go#L67-L70

I know this is old, but it's still open - can you show an example before/after where this applies?

Is this PR still active?

Closing this PR, since it's already been covered elsewhere.


How to access global  Neutralino

How to access global  Neutralino
seems need injection to component?

Hey.. please access the library via window.Neutralino


Error running action on windows os

Expected Behaviour
Test PR on windows os.
Actual Behaviour
I get the error below:

<EMAIL_ADDRESS>added 511 packages from 350 contributors in 38.737s
C:\windows\system32\cmd.exe /D /S /C "C:\npm\prefix\aio.cmd app test"
child_process.js:127
p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Object._forkChild (child_process.js:127:5)
at setupChildProcessIpcChannel (internal/bootstrap/pre_execution.js:334:30)
at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:57:3)
at internal/main/run_main_module.js:7:1 {
errno: -4083,
code: 'EBADF',
syscall: 'uv_pipe_open'
}
»   Error: Command failed with ENOENT: jest --passWithNoTests ./test
»   spawn jest ENOENT
Error: The process 'C:\npm\prefix\aio.cmd' failed with exit code 2
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Trigger GitHub action on Windows os
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem

Thanks for raising the issue @PulkitXChadha  !
@sandeep-paliwal , could you have a look?

Release 1.1.1 should address this problem.

Release 1.1.1 should address this problem.


PowerToys Run Crash during random search

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
PowerToysReport_2023-02-20-02-15-25.zip

2023-02-20.txt
✔ Expected Behavior
When typing in new words and pop up search result accordingly.
❌ Actual Behavior
At middle of typing, PowerToys Run crashes and crash report window of PowerToys shown.
Other Software
No response

I've had similar issues, just trying to do a quick Calc and it grinds to a halt as well. Does not even reach a stage where I can submit a Crash Report.

/dup #18166

For any users that are able to replicate this consistently, can you please update to 0.68.1 and disable thumbnail generation to verify if it fixes the issue? Please let us know on #18166!


Graph links on kghub.org to kghub.io are broken

Describe the bug
Links in the KG-Hub Projects table on https://kghub.org/ leading to kghub.io are broken.
To Reproduce
On kghub.org, click this link: https://kghub.io/kg-obo/
Currently, it leads to an error page:
<Error>
  NoSuchKey
  <Message>The specified key does not exist.</Message>
  <Key>kg-obo/</Key>
  <RequestId>R17C16AMDFXJD20F</RequestId>
  <HostId>9f4KtlTnd5QqODqiBlZ3DFRwzkqYyZgFvVXwljyzLEiqlRy7NV4O5xuLsrZePkAl8wpSokdQ6ec=</HostId>
</Error>

Expected behavior
The link above should go to https://kghub.io/kg-obo/index.html.

Is this still open?

Fixed as per #18


ImagesTable: fix grey box under AMI when image build is in progrss

this commit fix the fix grey box under AMI when image build is in progress
FIXES # https://github.com/RedHatInsights/image-builder-frontend/issues/1362

Could you also please add a component to the name of the commit and a short description? Maybe something like this:

ImagesTable: fix grey box under AMI when image build is in progress
Previously a Skeleton component was used as a placeholder for an AMI when the build was still pending. This removes the Skeleton and returns undefined rendering the AMI as empty.

One more tiny nit pick - in the PR name "progrss" -> "progress" and the commit message looks unfinished, it seems to end with "rendering the AMI as" now.


Implemented Margin Density Drift Detection (MD3) Method

MD3 algorithm for drift detection in a semi-supervised context
Paper: https://www.sciencedirect.com/science/article/pii/S0957417417302439
Changes

src/menelaus/concept_drift/md3.py: source code for new detector

Is currently compatible only with sklearn SVM classifiers (concept of margin will have to be generalized for other model types to be compatible as well)
Algorithm based on streaming data (initial reference data is passed in as a batch)

examples/streaming/md3_example.py: example for MD3 detector

Contains example of SVM semi-supervised drift detection using the Circle dataset
Can be added to concept_drift_example.py once finalized

@shashjar On the whole, really solid implementation of the algorithm. I'm impressed by how clean the code is. Most of my nitpicks or notes are to do with making it line up with older work.

Things to do:

[ ]  Before the final merge, we'll probably want to move most outstanding TODO items to separate git issues.
[x]  Unit tests.
[x]  Update the README table to include MD3.

Flagging a couple things that aren't problems, but do need more noodling (i.e. #15), since MD3's API is unusual relative to the other detectors:

[ ]  The set_reference method being called by a streaming detector makes this one a real oddball.  I think it should be possible (and maybe even desirable, down the line) to make the other streaming detectors implement the same thing (even if only a "do nothing" method), though. The one problem is that it doesn't match up with the API for other detectors, and at a minimum would call for updating the examples with the "optional" move of using set_reference in that context.

[ ]  The other unusual thing here is the waiting_for_oracle state and the corresponding give_oracle_label function. The loop has to check for the different state and call the other function instead of update. Again, not necessarily an issue, but something that may need revision later on if, e.g., we modify the API s.t. everything is passed in via update.

[x]  There are retraining steps within the give_oracle_label and calculate_distribution_statistics functions.

This requires that any passed classifier implements the fit method, as in sklearn, which is something we've been able to avoid up until now.
In the former function, if left as-is, the classifier being refit without the user explicitly telling it to be may "feel like" unexpected behavior, even if it's documented. Same might be true for the set_reference call, even though that's the algorithm-as-described.

Potential TODOs/Questions to Address About MD3 in the Future

Add MD3 to the example notebooks and the example scripts --> currently in its own example script

Currently, MD3 has a set_reference to pass in a batch of data as the reference batch, which is inconsistent with the other streaming detectors. We could (1) leave this as is, (2) leave this as is and add set_reference to the other streaming detectors to make them consistent, (3) make MD3's API compatible with both an initial batch or stream-based data for setting the reference, or (4) change MD3 to be compatible only with stream-based data for setting the reference.

waiting_for_oracle state and give_oracle_label method


provide a direct download for the json

This json is updated weekly, but the download involves clicking a confirmation, and resulting in a time-stamped file if you direct download.
Again:  This is makes automating needlessly difficult.  Why dont we have an RSS feed or a static file? like AWS or GCP uses?  This is so 20 years ago.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc5a4cfa-aa84-9f0f-55f4-71ec4861c070
Version Independent ID: d621620a-c924-03b1-8b43-f99c33e58bb8
Content: Add IP addresses and URLs to allow list - Azure DevOps
Content Source: docs/organizations/security/allow-list-ip-url.md
Product: devops
Technology: devops-security
GitHub Login: @chcomley
Microsoft Alias: ChComley

Please see #7936.


scripts to keep

Hi! I'm putting here a list of the scripts that are being used at the moment. And open the discussion to decide which to keep.
One example are the chunking.py, do_chunk.py and duck_chunk.py, which do the same in different manners or from different inputs. The only a bit different is chunking.py which allows for a mask of residues to forcibly be kept or removed (overwriting the duck function namespaces, so I'll have a look if its worth changing the steps.chunk ). In this specific case I suggest unifying them into a single script (e.g. do_chunk.py )
These are the scripts we have right now and what they do

System preparation
Comment
To keep

duck_prepare_sys.py
prepare and equilibrate system for openMM (might be interesting to change name to specify openMM?)
Yes

duck_prepare_sys_for_amber.py
prepare system for Amber
Yes, can be merged with batch?

batch_duck_prepare_for_amber.py
prepare multiple systems for Amber
Yes

do_chunk.py // duck_chunk.py // chunking.py
create and prepare the chunk from the whole protein and an interaction
Yes, merged

Production

Would be ideal to have a single script with the option to start at different steps of the process

run_from_equil.py // duck_smd_runs
run OpenMM duck protocol from equilibrated system (i don't see the difference between the two)
Yes // merge

run_full_duck_pipelin.py
Create chunk, prepare, equilibrate and run MD+SMD in openMM
Yes // merge

run_full_from_fragalysis.py
Hardcoded version of full duck protocol for a specific case (?)
No

from_amber_input.py
Run full openMM duck protocol from Amber topology
Yes, exception to merge as it is a especial case

from_chunk.py
Run full openMM duckprotocol from the chunked protein
Yes // merge

Analysis

getWqbValues.py
obtain $W_{QB}$ from duck output
Yes

jarzynski.py
Obtain $\Delta G_{QB}$ from duck output, with bootstrapping
Yes

duck_report.py // get_wqb.py
Generate report from multiple duck_outputs, I did the duck_report.py but didn't notice that get_wqb.py has a similar structure
Yes // merge

duck_analysis_visualization.py
Generate vmd visualization state from duck output
Yes (?)

Other

trace_diagnostic.py

No

I have been working on merging the duck_chunk scripts trying to unify all the options (yaml, command line, parameters, etc).
So we can simplify it. I also need to update the duck_prepare_sys.py with the options added to the preparation for amber.
Finally I'm also working on a unified script to launch the openMM version of OpenDuck, with the options to chose to start from a full protein, a chunk or an equilibrated system (i'll see if it is worth it to also merge the starting from an amber topology).
With this I believe we can reduce significantly the scripts without losing on functionalities.

Hi @simonbray don't worry. I have been working on having every script in a single executable, with different sub-parsers (kind of how is done in mdmix). I don't know if its the best way of going, but so far, it seems very tidy. The same for the report, and preparation of systems.
I'm doing it in https://github.com/AlvaroSmorras/openduck/tree/scripts_cleanup. I have ended with something like this:
$ openduck -h

usage: openduck [-h]  ...

Open Dynamic Undocking

optional arguments:
  -h, --help            show this help message and exit

Open Dynamic Undocking toolkit. Choose one of the following actions:

    OpenMM_prepare      Preparation of systems for OpenMM simulations
    OpenMM_full-protocol
                        OpenDuck OpenMM full protocol either with or without
                        chunking the protein.
    OpenMM_from-equilibrated
                        OpenDuck openMM protocol starting from a pre-
                        equilibrated system (e.g. from duck_prepare_sys.py)
    OpenMM_from-amber   OpenDuck openMM protocol starting from an amber
                        topology and coordinates (prmtop and inpcrd).
    AMBER_prepare       Preparation of systems, inputs and queue files for
                        AMBER simulations
    report              Generate report for openduck results.
    chunk               Chunk a protein for Dynamic Undocking.

Where the options are displayed (I know they are a bit wordy, I am open to suggestions). And each option has its own input parameters, which I have maintained as much as possible from their original scripts. I have also given the option in each case to give the input as a yaml or directly in the command line.
This would be an example
$ openduck OpenMM_full-protocol -h

usage: openduck OpenMM_full-protocol [-h] [-y YAML_INPUT] [-l LIGAND] [-i INTERACTION] [-r RECEPTOR] [-g GPU_ID]
                                     [--do-chunk] [-c CUTOFF] [-b] [-f {SMIRNOFF,GAFF2}] [-w {tip3p,spce}]
                                     [-ff {amber99sb,amber14-all}] [-ion IONIC_STRENGTH] [-s SOLVENT_BUFFER_DISTANCE]
                                     [-water WATERS_TO_RETAIN] [-F FORCE_CONSTANT_EQ] [-n SMD_CYCLES] [-m MD_LENGTH]
                                     [-W WQB_THRESHOLD] [-v INIT_VELOCITIES] [-d INIT_DISTANCE]

optional arguments:
  -h, --help            show this help message and exit

Main arguments:
  -y YAML_INPUT, --yaml-input YAML_INPUT
                        Input yaml file with the all the arguments for the full openDUck protocol.
  -l LIGAND, --ligand LIGAND
                        ligand mol file to use as reference for interaction.
  -i INTERACTION, --interaction INTERACTION
                        Protein atom to use for ligand interaction.
  -r RECEPTOR, --receptor RECEPTOR
                        Protein pdb file to chunk, or chunked protein if mode is "for_chunk".
  -g GPU_ID, --gpu-id GPU_ID
                        GPU ID, if not specified, runs on CPU only.

Chunking arguments:
  --do-chunk            Chunk initial receptor based on the interaction with ligand and add cappings.
  -c CUTOFF, --cutoff CUTOFF
                        Cutoff distance to define chunk.
  -b, --ignore-buffers  Do not remove buffers (solvent, ions etc.)

Parametrization arguments:
  -f {SMIRNOFF,GAFF2}, --small_molecule_forcefield {SMIRNOFF,GAFF2}
                        Small Molecules forcefield.
  -w {tip3p,spce}, --water-model {tip3p,spce}
                        Water model to parametrize the solvent with.
  -ff {amber99sb,amber14-all}, --protein-forcefield {amber99sb,amber14-all}
                        Protein forcefield to parametrize the chunked protein.
  -ion IONIC_STRENGTH, --ionic-strength IONIC_STRENGTH
                        Ionic strength (concentration) of the counter ion salts (Na+/Cl+). Default = 0.1 M
  -s SOLVENT_BUFFER_DISTANCE, --solvent-buffer-distance SOLVENT_BUFFER_DISTANCE
                        Buffer distance between the periodic box and the protein. Default = 10 A
  -water WATERS_TO_RETAIN, --waters-to-retain WATERS_TO_RETAIN
                        PDB File with structural waters to retain water moleules. Default is waters_to_retain.pdb.

MD/SMD Production arguments:
  -F FORCE_CONSTANT_EQ, --force-constant_eq FORCE_CONSTANT_EQ
                        Force Constant for equilibration
  -n SMD_CYCLES, --smd-cycles SMD_CYCLES
                        Number of MD/SMD cycles to perfrom
  -m MD_LENGTH, --md-length MD_LENGTH
                        Lenght of md sampling between smd runs in ns.
  -W WQB_THRESHOLD, --wqb-threshold WQB_THRESHOLD
                        Minimum WQB threshold to stop simulations.
  -v INIT_VELOCITIES, --init-velocities INIT_VELOCITIES
                        Set initial velocities when heating
  -d INIT_DISTANCE, --init-distance INIT_DISTANCE
                        Set initial HB distance for SMD

I am trying to document everything as much as possible too, and preparing a small test folder to provide and ensure everything works fine. We could have a meeting someday soon and discuss this.


what happens to submitted feeds and operators at conclusion of "add a feed" flow?

When a user currently completes the "add a feed" flow, the new feed and operator models stay in the local Ember Data store. They'll appear in the operators table, until the user presses reload or leaves the Feed Registry.
Is this the behavior we want? If so, should we style the local feeds/operators differently, so it's clear that they are proposed? If not, we should clear the local models after submission, and use copy to explain that it's been submitted for review.
Off the top of my head, I think the latter makes more sense. But what do you think @meghanhade and @souperneon?

I agree that the latter makes more sense here, @drewda. I do think it's important for people to see the feed they just submitted (in a way that the feed is under review), but I don't think that should happen in a way that will disappear once they've left the page/reloaded.

I liked @meghanhade's suggestion of adding "What happens now?" to the page and some information about contacting the submitter (method and timeline of contact to be determined).
Current UI text: "Thank you for adding a feed! We have created a changeset to review on Transitland."
Suggesting something like:
Thank you for submitting a feed to Transitland!
Next, your feed will be reviewed and imported. Occasionally, there are issues with the import process that could cause a delay or make the feed unsuitable for posting on Transitland.
If you provided your contact information, you will be notified when your feed is part of the Transitland feed registry.

This is a big big improvement! Just to clarify, if there is an issue in the import process do we contact the contributor? If we do, we should add that at the end of the second para. Right now it kinda sounds like if there is an issue with the import process nothing will end up happening

At this point, I think the simplest approach will be to use the "success" page to give the information about the process. The local feed and operator models can either be cleared out when the user lands on the success page, or as they're transitioning back to the Feed Registry index. In either case, it's simplest to have the local models gone before the user sees the index again.

Sounds good. One more note @rmglennon, should Feed Registry be in title case?

@drewda and I will test that local data is deleted at the end of the add-a-feed flow

Copying from Rhonda's comment:
Thank you for submitting a feed to Transitland!
Next, your feed will be reviewed and imported. Occasionally, there are issues with the import process that could cause a delay or make the feed unsuitable for posting on Transitland.
If you provided your contact information, you will be notified when your feed is part of the Transitland Feed Registry.

Note to self (and cc @drewda): The submission does show up in the Feed Registry when the user follows the "return to feed registry" link at the bottom of the success step. It does not show up in the FR upon refresh, or when navigating through the header menu to the FR. I'll need to clear out the operators when the success step link is used.

@meghanhade :+1:


validating-deployments-existence-before-going-in-watch-mode

@Creatoon I have included a new test to evaluate the new validation.

Oh shit I did not notice and I have implemented this today XD
I just wanted to inspect through OpenAPIv3 and there was no error info, that's why I added it, then I pushed the changes and I noticed just now that this PR is open.

No problem. I will

By the way, the part of ensureDeploymentsExist is still highly useful, can you update this PR with last changes done by me and add this check to inspect?
I change it to draft meanwhile.

O

@viferga
Absolutely, I will update it asap.


Refresh recyclerview - Swipe/Drag problems

First of all, many thanks for this very easy swipe-drag library!
What's the best way of refreshing the recyclerview? When I reload my data, the swipe/drag functionality malfunctions. For instance, swipe works but items do not move back into position and I am left with a gap where the swiped card was. And dragging is sluggish and does not work well.
To reload the recyclerview, I use the exact same method as to load it. Any tips? Thanks!

@strangerweather have you got some workaround?
I am also facing the same problem as you are saying.
can't have an idea about how to resolve it.

@ParryPatel021 Sorry, I can't remember, that was 2 years ago. I think I just used a different library. I don't have that project anymore so I can't check.

@strangerweather Thanks for the reply. I have solved my problem to prevent the attachment of  ItemTouchHelper to RecyclerView multiple times.
In short, I have attached ItemTouchHelper to RecyclerView by putting it in onCreate() method of an Activity.


Cross-platform PTY backend

Hey! I would like to propose you to use my cross-platform PTY/Qt backend as a base for your terminal project. With it, you can support Linux/MacOS/Windows both with the same interface.
If you are interested, please check out it here: https://github.com/kafeg/ptyqt

Cool, looks nice!  I'll take a closer look once I've added and stabilized some newer features I want in sff and try to bring it in.  Right now I'm still (very slowly) experimenting with what this project might end up looking like so I don't want to add another dependency.

Of course, just suggestion)


Default installation means that any included SASS files don't have access to Foundation variables

+1 having the same issue. When trying to precompile my assets, i'm getting Sass::SyntaxError: Undefined variable: "$primary-color".

i use aws elastic beanstalk for deployment. what i did is that i precompiled my assets first and then deployed the app with the precompilation


Add a debugger

https://github.com/go-delve/delve ?

For the moment we don't have a debugger, but do have a logger package to help decipher messages in the console
https://github.com/hay-i/chronologger/pull/64/commits/7307fcc09847948637a2df87f2f26df41925b3a8

^ does slog do this out-of-the-box? https://go.dev/blog/slog


Multi-Protocol Reach NLRI from Juniper causes a crash

Hello hello,
Parsing this message:
20:57:20.386957 IP6 (class 0xc0, flowlabel 0x5e6ef, hlim 1, next-header TCP (6) payload length: 136) 2404:138:134:120::1.58823 > 2404:138:134:120::2.179: Flags [P.], cksum 0x96aa (correct), seq 64:168, ack 63, win 17074, options [nop,nop,TS val<PHONE_NUMBER> ecr 242517267], length 104: BGP
	Keepalive Message (4), length: 19
	Update Message (2), length: 85
	  Origin (1), length: 1, Flags [T]: IGP
	    0x0000:  00
	  AS Path (2), length: 6, Flags [T]: 38022
	    0x0000:  0201 0000 9486
	  Community (8), length: 4, Flags [OT]: 38022:10700
	    0x0000:  9486 29cc
	  Multi-Protocol Reach NLRI (14), length: 38, Flags [OE]:
	    AFI: IPv6 (2), SAFI: Unicast (1)
	    nexthop: 2404:138:134:120::1, fe80::f21c:2dff:fe7f:a796, nh-length: 32, no SNPA
	      ::/0
	    0x0000:  0002 0120 2404 0138 0134 0120 0000 0000
	    0x0010:  0000 0001 fe80 0000 0000 0000 f21c 2dff
	    0x0020:  fe7f a796 0000

Which looks like this on the wire:
0000   90 0e 00 26 00 02 01 20 24 04 01 38 01 34 01 20  ...&... $..8.4.
0010   00 00 00 00 00 00 00 01 fe 80 00 00 00 00 00 00  ................
0020   f2 1c 2d ff fe 7f a7 96 00 00                    ..-.......

Causes a crash on line 317 in bgp_message.py, because during
afi, safi, next_hop_length = struct.unpack("!HBB", stream.read(4))

The BytesIO object is being created from an empty string. Tracking it back a little bit I have found that in parse_path_attributes the packed_attribute being passed in is just '\x00', which seems wrong.
I ran out of time tonight, but I can have another poke at this later. v4 is working with Juniper OK, from what I can tell.

Nice find! My guess is that it's because we're not supporting the extended length bit (we ignore all the flags which is a little naughty), first byte is 0x90 = 0x80 | 0x10 - this means we have a uint16 for length (0x0026) instead of uint8 (default behaviour) - so we're just reading the first octet and getting 0.
Seems weird that juniper is using this - it's technically part of the standard, but the size is well short of 256 bytes.
I've pushed a workaround to master, can you let me know if this fixes it?


Cron jobs loaded but not running on Heroku-24

On my machine, sidekiq-cron 1.8.0 works fine (with sidekiq 6.4.2), and production Heroku-20 and Heroku-22 machine has been fine as well. I upgraded to Heroku-24 a few days ago, and the sidekiq-cron isn't enqueueing jobs anymore.

Cron jobs are all loaded (seen in UI and checking via console Sidekiq::Cron::Job.all
Cron jobs all have status "Enabled"
UI buttons "Enqueue Now" and "Disable" don't work for active jobs. Disabled jobs have buttons, and those don't work (can't enqueue, disable, nor delete).
Jobs' "last enqueued" was 4 days ago when I upgraded to Heroku-24
I've tried running Sidekiq::Cron::Job.all.first.enque!, and it enqueued and ran it.

Could it be an issue with poller? What can I do to fix this issue?

Hey @jchan172 👋🏼
Sorry I don't use Heroku nowadays, so I don't follow their stack changes anymore.
It will really hard (mostly impossible) for us to help you with those specific versions of Sidekiq, Sidekiq-Cron, Heroku and the rest of gems and code of your app, without having a access to a reproducible scenario. I recommend you to update to more recent versions of Sidekiq and Sidekiq-Cron and see what happens.
Please, if you can provide an example app that reproduces the error locally or a failing test in our suite, don't hesitate to re-open the issue and I'll take a deeper look.
Kind regards,
Marc


Dead Link in readme.md

At the bottom of Readme, the docs link (http://getblimp.github.io/django-rest-framework-jwt) is dead.
I think the correct link should be: http://jpadilla.github.io/django-rest-framework-jwt/
Should I open a PR?

This is now fixed.


page.deleted Event Not Triggered When Page is Deleted Through Context Menu

Issue Summary
The page.deleted event is not being triggered consistently. While the event is successfully fired when a page is deleted from the Settings option within the page, it does not work when the page is deleted using the context menu in the Pages list.
Steps to Reproduce

Navigate to the Pages list.
Perform Ctrl + Mouse Click on a specific page.
From the context menu that appears, select Delete.
Observe that the page.deleted event does not get triggered.

Tested via https://webhook.site.
Ghost Version
5.65.0
Node.js Version
v18.18.0
How did you install Ghost?
Hostinger VPS with CloudPanel on Ubuntu
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Update: page.unpublished also doesn't work via the context menu.

Not Sidebar inside the Editor.
Try performing the steps I've listed in the Steps to Reproduce.
Screenshot -

The control + mouse click itself is not for working in my case, is this the issue?

The control + mouse click itself is not for working in my case, is this the issue?

The menu shows up for me on Ctrl + Mouse Click, Delete or other options work as well but there's no event fired.

Can someone from the core team take a look at this as this doesn't seem to be fixed in 5.66.0?

I would like to work on it, may I be assigned?


Select does not allow for a required attribute

@material-ui/core/Select does not allow for a required attribute like @material-ui/core/TextField

[x] This is a v1.x issue (v0.x is no longer maintained).
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Should be able to add required attribute to the <Select> input and it should:

Add * to label
Add required attribute to the rendered <input> tag

Current Behavior

Currently no support for required attribute on <Select> tags
Steps to Reproduce (for bugs)

https://codesandbox.io/s/qx4x1w8qlj

Add <Select> input with required attribute

Context

Would like <Select> inputs to act like <TextField> inputs to make UI consistent
Your Environment

Tech
Version

Material-UI
v1.0.0

React
v16.3.2

browser
Chrome

@oliviertassinari looks like the non-native solution uses a type=hidden input so the required validation won't really run unfortunately. Attempting to change it to type=text in inputProps results in the following error:

Warning: Failed prop type: You provided a value prop to a form field without an onChange handler.

@mciparelli If you are looking for the native require validation logic, use the native implementation of the select.

Well it's a shame because it would be nice to be able to still have the chance to use the custom select look and feel without losing the HTML5 validation.

@mciparelli Let us know if you find a way to change the implementation to get this done. But I have some doubt that we can achieve it.

@oliviertassinari wouldn't this be possible by forwarding the ref to the input rather than the root div?


How to set different learning rate at different layers when using tf.keras.model.fit

hello:
I am wondering if there is a way that I can use different learning rate for different layers. I am trying to modify a pre-trained model and use it for other tasks. What I want is to speed up the training for new added layers and keep the trained layers at low learning rate in order to prevent them from being distorted. for example, I have a 5-conv-layer pre-trained model. Now I add a new conv layer and fine tune it. The first 5 layers would have learning rate of 0.00001 and the last one would have 0.001. Any idea how to achieve this? another important part is I want to use model.fit().
thanks
If you are reporting a vulnerability, please use the dedicated reporting process.
For high-level discussions about TensorFlow, please post to<EMAIL_ADDRESS>for questions about the development or internal workings of TensorFlow, or if you would like to know how to contribute to TensorFlow, please post to<EMAIL_ADDRESS>

You have to custom implement this piece as we don't out of the box functionality.
This blog can be good starting point in your case.

You have to custom implement this piece as we don't out of the box functionality.
This blog can be good starting point in your case.

I read a part of source code of op and think this method can be used.
from tensorflow.python.training import training_ops
import tensorflow as tf

class Adam_with_layer(tf.keras.optimizers.Adam):
    def __init__(self, lr=0.001):
        super(Adam_with_layer, self).__init__(learning_rate=lr)
        self.dict_lr_schedul = {
            0.01: ["/bert/embeddings"] + ["/bert/encoder/layer_._" + str(i) for i in range(0, 6)],
            0.02: ["/bert/encoder/layer_._" + str(i) for i in range(6, 9)],
            0.1: ["/bert/encoder/layer_._" + str(i) for i in range(9, 12)] + ["/bert/pooler"],
            1: ["bidirectional", "layer_normalization", "label_attention"]
        }
    def _resource_apply_dense(self, grad, var, apply_state=None):
        var_device, var_dtype = var.device, var.dtype.base_dtype
        coefficients = ((apply_state or {}).get((var_device, var_dtype))
                        or self._fallback_apply_state(var_device, var_dtype))

        m = self.get_slot(var, 'm')
        v = self.get_slot(var, 'v')

        if not self.amsgrad:
            return training_ops.resource_apply_adam(
                var.handle,
                m.handle,
                v.handle,
                coefficients['beta_1_power'],
                coefficients['beta_2_power'],
                # coefficients['lr_t'],  # replaced by next
                coefficients['lr_t']*self.lr_with_layer(var),
                coefficients['beta_1_t'],
                coefficients['beta_2_t'],
                coefficients['epsilon'],
                grad,
                use_locking=self._use_locking)
        else:
            vhat = self.get_slot(var, 'vhat')
            return training_ops.resource_apply_adam_with_amsgrad(
                var.handle,
                m.handle,
                v.handle,
                vhat.handle,
                coefficients['beta_1_power'],
                coefficients['beta_2_power'],
                # coefficients['lr_t'],# replaced by next
                coefficients['lr_t'] * self.lr_wide_layer(var),
                coefficients['beta_1_t'],
                coefficients['beta_2_t'],
                coefficients['epsilon'],
                grad,
                use_locking=self._use_locking)

    def lr_with_layer(self,var):
        """

        :return:
        """
        name = var.name
        for k, v in self.dict_lr_schedul.items():
            for title in v:
                if name.find(title) != -1:
                    return k
        return 1

@jianrui1995 Your solution looks good to me, I think the options are either to do that or to override Model.train_step to process the gradients in a custom way. In tf-nightly, there's also the option to supply the gradient_transformers argument in Optimizer.__init__: link. With that argument, you could write a function that multiplies each gradient by some fraction based on its position in the list of Variables.


bufio: Reader cannot buf content greater than 32KB

What version of Go are you using (go version)?

$ go version
1.12.7

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/zhuangtianyi/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/zhuangtianyi/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.7/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.7/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/zhuangtianyi/go/src/github.com/TennyZhuang/net/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_6/hnkq5pbs6l3d94ngc525pnnh0000gp/T/go-build099861045=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

https://play.golang.org/p/i4IqIQPMqFd
Run the server, then just curl it.
What did you expect to see?
The buffer should work, then the output should be:
2019/07/24 20:28:08 Read 4194304 bytes
2019/07/24 20:28:09 Read 4194304 bytes
2019/07/24 20:28:10 Read 4194304 bytes
2019/07/24 20:28:11 Read 4194304 bytes
2019/07/24 20:28:12 Read 4194304 bytes
2019/07/24 20:28:14 Read 4194304 bytes
...

What did you see instead?
2019/07/24 20:30:15 Read 32768 bytes
2019/07/24 20:30:16 Read 32768 bytes
2019/07/24 20:30:17 Read 32768 bytes
2019/07/24 20:30:18 Read 32768 bytes
2019/07/24 20:30:19 Read 32768 bytes
2019/07/24 20:30:20 Read 32768 bytes
2019/07/24 20:30:21 Read 32768 bytes
2019/07/24 20:30:22 Read 32768 bytes
2019/07/24 20:30:23 Read 32768 bytes
2019/07/24 20:30:24 Read 32768 bytes
2019/07/24 20:30:25 Read 32768 bytes
2019/07/24 20:30:26 Read 32768 bytes
2019/07/24 20:30:27 Read 32768 bytes
2019/07/24 20:30:28 Read 32768 bytes
...

Investigation
To reduce the copy buffer, io.Copy will follow the behavior of WriterTo and ReaderFrom firstly.
bufio.Reader implements WriterTo, which will call the w's ReadFrom if possible.
And the implementation of http.ResponseWriter is http.(*response), it implements ReaderFrom to optimize for sendfile. But it has a bad fallback behavior on non-file reader, it call io.CopyBuffer with a small buffer(32KB), which break the buffer behavior of bufio.Reader.
All of above caused the unexpected behavior that bufio.Reader really can not buf anything more than 32KB.
A workaround is just wrap a nothing reader wrapped on *bufio.Reader, but it's not elegant.

/cc @ianlancetaylor
I was able to reproduce the described behavior by running the code in https://play.golang.org/p/i4IqIQPMqFd locally.

We could check in (*response).ReadFrom before we allocate the buffer, if the source is a buffered reader itself, and use WriteTo instead. It's not ideal, but would work.
The real fix is to introduce a buffer size interface and in io.Copy when both src and dst implement WriteTo and ReadFrom, respectively, pick the one with the larger buffer. bufio.Reader has a Size method, maybe that's the interface. This would change the spec of io.Copy subtly, which is probably not allowed. Currently it is spec'd to always chose WriterTo in preference to ReaderFrom.

This is likely a dup of #16474.

@randall77 I meet this bug again and it's difficult to locate this bug, is it ok to fix it use the workaround? I'd like to submit a PR about it.

Which workaround do you mean? There are a few in this thread and in #16474.

you can use io.LimitReader() package and method

you can use bufio.NewReaderSize and bufio.NewWriterSize method

Closing as duplicate of https://github.com/golang/go/issues/16474


DXR Fallback:  The implementation of EmitRaytracingAccelerationStructurePrebuildInfo does not match the DXR headers.

The PREBUILD_INFO_DESC for compacted size is defined as a 64-bit integer in the DXR headers, but the fallback layer as implemented assumes 32 bits.  In the case of multiple RTASes passed to the same Emit() call, the  results will be incorrect.  This behavior also differs from that of the Nvidia DXR driver.

Yup, this is definitely a bug. I'll take a look, seems like a quick fix. Thanks for filing an issue on it!

I've fixed this in the develop-dxr branch, expect this to be moved down to master in a week or so


winget upgrade Microsoft.VCRedist.2013.x64  most current package missing?

Brief description of your issue
when performing the following on a win 11 machine winget provides an incorrect response for the available upgrade package of
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30… Microsoft.VCRedist.2013.x64  version 12.0.40664.0. It cannot be found.
winget upgrade microsoft.vcredist.2013.x64
No applicable upgrade found.
I believe this response to be correct as I cannot find the supposed "Available" version 12.0.40664.0 for the given package.
Either the suggested version is wrongly provided by winget upgrade or there is a package missing
Steps to reproduce
when performing the following on a win 11 machine:
winget upgrade
the following response is:
**Name                                                       Id                                                                             Version      Available    Source
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30… Microsoft.VCRedist.2013.x64 12.0.30501.0 12.0.40664.0 winget**
Following up with an upgrade request for the package we get a no applicable upgrade found request.
winget upgrade microsoft.vcredist.2013.x64
No applicable upgrade found.
I believe this response to be correct as I cannot find the supposed "Available" version 12.0.40664.0 for the given package.
Expected behavior
I expected the suggested most current package to download and install.
Actual behavior
the most current version is not found, a normal not found error is provided.
Environment
Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.1778
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0

What is the output of winget list 'Visual C++ 2013' ?

Kaleb,
I entered it verbatim
C:\Windows\System32>winget list 'Visual C++ 2013'
Windows Package Manager v1.4.10173
Copyright (c) Microsoft Corporation. All rights reserved.
Found a positional argument when none was expected: 'C++'
I switched from a single tic/quote to a double tic/quote to get it to work.
C:\Windows\System32>winget list "Visual C++ 2013"
Name                                                       Id                          Version      Available    Source
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40... Microsoft.VCRedist.2013.x64 12.0.40664.0              winget
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30... Microsoft.VCRedist.2013.x64 12.0.30501.0 12.0.40664.0 winget
Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.40... Microsoft.VCRedist.2013.x64 12.0.40664.0              winget
I see the output has two versions of the x64 packages installed. I will guess this happened during the first attempt to install a day or two ago.
I apologize that I did not recheck the installed package list in Control Panel earlier.
Program list in Control Panel matches the list output somewhat.
@.***
I will probably consider removal of the earlier package after your suggestions.  Given the .86 version was there in March I am not sure what is going on.
George
From: Kaleb Luedtke @.>
Sent: Friday, May 26, 2023 4:29 PM
To: microsoft/winget-cli @.>
Cc: georgewilkin @.>; Author @.>
Subject: Re: [microsoft/winget-cli] winget upgrade Microsoft.VCRedist.2013.x64 most current package missing? (Issue #3276)
What is the output of winget list 'Visual C++ 2013' ?

Reply to this email directly, view it on GitHubhttps://github.com/microsoft/winget-cli/issues/3276#issuecomment-1564978159, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAD735ULWBFH3V57KNJN573XIEOADANCNFSM6AAAAAAYQV7MPQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Custom scale doesn't apply to ASS files

Whenever I've tried to use a custom scale with level structures I've noticed that everything comes out the expected size, but with the wrong positions. After a very quick look I've found this section:
https://github.com/General-101/Halo-Asset-Blender-Development-Toolset/blob/405787167604b0df0aa9f5424170c7a2b846acc6/io_scene_halo/global_functions/global_functions.py#L519-L525
If I change the if to include 'ASS':
if file_type == 'JMS' or file_type == 'ASS':
It seems to work as expected (at least for my simple test scene). I'm not sure if this breaks something else or if it's the only section of code that needs changing to fully fix the issue.

That's like that because ASS has a scale value in the format. Scale from the object gets written there and the unscaled object dimensions are written to the file.
Proper fix would be to make sure the scale value written is correct after using a custom scale value.

Looking at the code I can't see anywhere the custom scale is applied to the file.
Here's a test scene .blend:
Scale Test.zip
The custom scale is set to 10. When I export to ASS and import into a scenario the sizes of everything look right, just the positions are off.

The scale was 10 above, but if I drop it to 2 (and scale the scene by 5X in blender) they are much closer to the correct positions. This lines up with the positions just not being affected by the scale.

The scene is correct in Sapien with the change mentioned in the initial issue.

all i did was make the map biger and blender crashed with error related to toolset
F
An unhandled exception has occurred!
System.InvalidOperationException: Process was not started by this object, so requested information cannot be determined.
at System.Diagnostics.Process.EnsureState(State state)
at
ToolkitLauncher.Utility.Process.Windows.<>c__DisplayClass2_0.<<StartProcessW
ithShell>g_Handle Process|0>d.MoveNext()
End of stack trace from previous location ---
at ToolkitLauncher.Utility.Process.Windows.StartProcessWithShell(String directory, String executable, String args, Boolean lowPriority, InjectionConfig injectionOptions, CancellationToken cancellationToken)
at ToolkitLauncher.Utility.Process.StartProcessWithShell(String directory, String executable, List`1 args, Boolean lowPriority, InjectionConfig injectionOptions, CancellationToken cancellationToken)
at ToolkitLauncher.Toolkit Interface.ToolkitBase.RunToolInternal(ToolType tool, List`1 args, Nullable`1 outputMode, Boolean lowPriority, InjectionConfig injectionOptions, CancellationToken cancellationToken)
at Toolkit Launcher.ToolkitInterface.ToolkitBase.RunTool (ToolType tool, List`1 args, Nullable`1 outputMode, Boolean lowPriority, InjectionConfig injectionOptions, CancellationToken cancellationToken)
at
ToolkitLauncher.Toolkit Interface.H3Toolkit.<>c__DisplayClass11_0.<<FauxLocalF
arm>g RunFastool|0>d.MoveNext()
at
End of stack trace from previous location ---
ToolkitLauncher.Toolkit Interface.H3Toolkit.<>c__DisplayClass11_0.<<FauxLocalF
arm>g RunStage|1>d.MoveNext()
End of stack trace from previous location -
at Toolkit Launcher.Toolkit Interface.H3Toolkit.FauxLocalFarm(String scenario, String bsp, String lightmapGroup, String quality, Int32 clientCount, Boolean ruseFast, OutputMode mode, ICancellable Progress 1 progress)
at Toolkit Launcher.Toolkit Interface.H3Toolkit.Build Lightmap(String scenario, String bsp, LightmapArgs args, ICancellable Progress 1 progress)
at ToolkitLauncher.MainWindow.CompileLevel(String level_path, String bsp_path, String Level_Quality, Single level_slider, Boolean
radiosity_quality_toggle, Int32 instance_count, Boolean phantom_fix, String lightmap_group, String lightmapper_globals)
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
OK
Cancel

Please post that in the Osoyoos github as a new issue. Not here.


Script to generate notes for all person records

LGTM. Please merge it after addressing comments.

Thanks for the review. Merged.


Unhandled Promise rejection: Object(...) is not a function Promise.then ; Value: TypeError: Object(...) is not a function in ionic3?

Current behavior
Got above error after ionic serve
Expected behavior
After ionic serve app is open
Console error:

polyfills.js:3 Unhandled Promise rejection: Object(...) is not a function ; Zone: <root> ; Task: Promise.then ; Value: TypeError: Object(...) is not a function     at new ApplicationRef (vendor.js:15312)     at _createClass (vendor.js:18294)     at _createProviderInstance (vendor.js:18256)     at initNgModule (vendor.js:18189)     at new NgModuleRef_ (vendor.js:18916)     at Object.createNgModuleRef (vendor.js:18905)     at NgModuleFactory_.create (vendor.js:21464)     at vendor.js:15117     at t.invoke (polyfills.js:3)     at Object.onInvoke (vendor.js:14655) TypeError: Object(...) is not a function     at new ApplicationRef (http://localhost:8100/build/vendor.js:15312:64)     at _createClass (http://localhost:8100/build/vendor.js:18294:20)     at _createProviderInstance (http://localhost:8100/build/vendor.js:18256:26)     at initNgModule (http://localhost:8100/build/vendor.js:18189:32)     at new NgModuleRef_ (http://localhost:8100/build/vendor.js:18916:9)     at Object.createNgModuleRef (http://localhost:8100/build/vendor.js:18905:12)     at NgModuleFactory_.create (http://localhost:8100/build/vendor.js:21464:25)     at http://localhost:8100/build/vendor.js:15117:43     at t.invoke (http://localhost:8100/build/polyfills.js:3:14976)     at Object.onInvoke (http://localhost:8100/build/vendor.js:14655:33) n.onUnhandledError @ polyfills.js:3
Steps to reproduce:
From cmd >  npm i<EMAIL_ADDRESS>Version used
li packages: (/usr/lib/node_modules)
@ionic/cli-utils  : 1.19.2
ionic (Ionic CLI) : 3.20.0

global packages:
cordova (Cordova CLI) : not installed
local packages:
@ionic/app-scripts : 3.2.0
Cordova Platforms  : none
Ionic Framework    : ionic-angular 3.9.2
System:
Node : v8.10.0
npm  : 6.3.0
OS   : Linux 4.13
Environment Variables:
ANDROID_HOME : /home/Android/Sdk/

https://github.com/ngx-translate/core/issues/824

#ACivilise  sir i have already installed this plugin but not working

Hi,
You need to install a compatible version with the angular version  used in your ionic project.
You can look in your package.json file to know which version of angular used.

Uninstall the package you installed and then specify the version to install like this :
npm install<EMAIL_ADDRESS>--save
npm install<EMAIL_ADDRESS>--save
Regards.

Inheriting a project someone else made and I've been trying for way too long to make it build. Same issue as OP. Feel like I'm close but can't seem to solve this one. My ng version seems aligned with the appropriate ngx-translate.. So what's going on?
{
  "name": "Brick-IT",
  "version": "0.0.1",
  "author": "Ionic Framework",
  "homepage": "http://ionicframework.com/",
  "private": true,
  "scripts": {
    "start": "ionic-app-scripts serve",
    "clean": "ionic-app-scripts clean",
    "build": "ionic-app-scripts build",
    "lint": "ionic-app-scripts lint",
    "test": "karma start ./test-config/karma.conf.js",
    "test-ci": "karma start ./test-config/karma.conf.js --single-run",
    "test-coverage": "karma start ./test-config/karma.conf.js --coverage",
    "e2e": "npm run e2e-update && npm run e2e-test",
    "e2e-test": "protractor ./test-config/protractor.conf.js",
    "e2e-update": "webdriver-manager update --standalone false --gecko false"
  },
  "dependencies": {
    "@angular/animations": "^7.2.14",
    "@angular/common": "^7.2.14",
    "@angular/compiler": "^7.2.14",
    "@angular/compiler-cli": "^7.2.14",
    "@angular/core": "^7.2.14",
    "@angular/forms": "^7.2.14",
    "@angular/http": "^7.2.14",
    "@angular/platform-browser": "^7.2.14",
    "@angular/platform-browser-dynamic": "^7.2.14",
    "@ionic-native-mocks/qr-scanner": "^2.0.12",
    "@ionic-native/app-version": "^4.0.0",
    "@ionic-native/core": "^4.0.0",
    "@ionic-native/flurry-analytics": "^4.0.0",
    "@ionic-native/globalization": "^4.0.0",
    "@ionic-native/network": "^4.0.0",
    "@ionic-native/qr-scanner": "^4.0.0",
    "@ionic-native/splash-screen": "^4.0.0",
    "@ionic-native/status-bar": "^4.0.0",
    "@ionic/storage": "^2.2.0",
    "@ngrx/effects": "^7.4.0",
    "@ngrx/router-store": "^7.4.0",
    "@ngrx/store": "^7.4.0",
    "@ngx-translate/core": "^11.0.1",
    "@ngx-translate/http-loader": "^4.0.0",
    "@types/aws-sdk": "^2.7.0",
    "@types/graphql": "^14.0.3",
    "apollo-angular": "^1.5.0",
    "apollo-angular-link-http": "^1.6.0",
    "apollo-cache-inmemory": "^1.5.1",
    "apollo-client": "^2.5.1",
    "aws-amplify": "^1.1.26",
    "aws-appsync": "^1.7.2",
    "aws-sdk": "^2.442.0",
    "axios": "^0.18.0",
    "cordova-android": "^8.0.0",
    "cordova-ios": "^5.0.1",
    "cordova-plugin-app-version": "^0.1.9",
    "cordova-plugin-cocoapod-support": "^1.6.0",
    "cordova-plugin-device": "^2.0.2",
    "cordova-plugin-flurryanalytics": "^1.4.6",
    "cordova-plugin-globalization": "^1.11.0",
    "cordova-plugin-ionic-keyboard": "^2.1.3",
    "cordova-plugin-ionic-webview": "^4.0.1",
    "cordova-plugin-native-keyboard": "^2.0.3",
    "cordova-plugin-network-information": "^2.0.1",
    "cordova-plugin-qrscanner": "^3.0.1",
    "cordova-plugin-splashscreen": "^5.0.2",
    "cordova-plugin-statusbar": "^2.4.2",
    "cordova-plugin-whitelist": "^1.3.3",
    "core-js": "^2.4.1",
    "graphql": "^14.2.1",
    "graphql-tag": "^2.8.0",
    "ionic-angular": "^3.9.5",
    "ionicons": "3.0.0",
    "localforage": "^1.7.2",
    "moment": "^2.22.2",
    "moment-timezone": "^0.5.21",
    "random-name": "^0.1.2",
    "randomcolor": "^0.5.3",
    "rxjs": "^5.0.1",
    "rxjs-compat": "^6.5.1",
    "sw-toolbox": "^3.6.0",
    "symbol-observable": "^1.2.0",
    "zone.js": "~0.8.26"
  },
  "devDependencies": {
    "@angular/cli": "~7.3.8",
    "@angular/language-service": "^7.2.14",
    "@ionic/app-scripts": "^3.2.3",
    "@types/jasmine": "^3.3.12",
    "@types/node": "^11.13.7",
    "html-loader": "^0.5.5",
    "ionic3-mocks": "^0.11.22",
    "istanbul-instrumenter-loader": "^3.0.1",
    "jasmine": "^3.4.0",
    "jasmine-spec-reporter": "^4.2.1",
    "karma": "^2.0.2",
    "karma-chrome-launcher": "^2.2.0",
    "karma-coverage-istanbul-reporter": "^2.0.0",
    "karma-jasmine": "^1.1.2",
    "karma-jasmine-html-reporter": "^1.1.0",
    "karma-sourcemap-loader": "^0.3.7",
    "karma-webpack": "^3.0.0",
    "null-loader": "^1.0.0",
    "protractor": "^5.4.2",
    "ts-node": "^8.1.0",
    "tslint": "^5.16.0",
    "typescript": "^3.2.0"
  },
  "cordova": {
    "plugins": {
      "cordova-plugin-whitelist": {},
      "cordova-plugin-statusbar": {},
      "cordova-plugin-device": {},
      "cordova-plugin-splashscreen": {},
      "cordova-plugin-ionic-webview": {
        "ANDROID_SUPPORT_ANNOTATIONS_VERSION": "27.+"
      },
      "cordova-plugin-ionic-keyboard": {},
      "cordova-plugin-network-information": {},
      "cordova-plugin-qrscanner": {},
      "cordova-plugin-native-keyboard": {
        "LICENSE": "TRIAL",
        "LIC_ANDROID": "TRIAL"
      },
      "cordova-plugin-globalization": {},
      "cordova-plugin-flurryanalytics": {},
      "cordova-plugin-app-version": {}
    },
    "platforms": [
      "ios",
      "android"
    ]
  }
}

@binayPUNCH:- sir please  open the issue actually I don't need ng-translate in our app sir so tell me sir how to fix and please open it?


python.pkgs.{gitdb,GitPython}: update

Motivation for this change
I had issues with the outdated GitPython and the gitdb update is a dependency.
@FRidh do you think dropping gitdb2 is the right thing to do, given the merge and that gitdb is the canonical version?
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

From the linked issue:

In 2015 ...

Yes, let's make this change.

To be precise, the split happened in 2015 but the merge back only happened recently. So it may very well be that people are using gitdb2 somewhere. That would break.
It wouldn't be difficult to fix though, so I don't see much point in backwards compatibility here.
I noticed that smmap2 was in a similar situation (from the same devs), so I applied the same change there. nix-review revealed taht gitdb2 is no longer py2 compatible, so I dropped that. I think this is ready now.

Yeah, that might be helpful. How about this?


Hyprland crashes instantly since c2f29be9baccd14ced62105f0fc07e34e6f4fd29.

Hyprland crashes instantly after start since commit https://github.com/hyprwm/Hyprland/commit/c2f29be9baccd14ced62105f0fc07e34e6f4fd29. Everything works great with 16a034a34a8e97aaeed6e3f46d04c87497313c20.
Crash report:
hyprlandCrashReport38501.txt

should be fixed in 41c7d896e38896916f0762acbc7f811a00240b4f
lmk, if not, feel free to reopen

Now it's freezing (with a gray screen and a cursor on every monitor) instead of crashing.

can I getcho config

hypr.tar.gz

thank u uwu

sowwy fow the wwittwe inconwenience onii-chan uwu
can you pwease twy this patch UwU
patch.txt

It's working with the patch applied.

pushed to head


[fpga] Enforce CW310 SAM3X Firmware

As CW310 SAM3X firmware version below "1.5" have an UART flow control bug, enforce that the version is at leaset "1.5". This ensures that the communication over uJSON works flawless.

Unfortunately there seems to be a bug in the CW SAM3X FW. The binary was created on 24.04.24 and should have version number 1.5. However, when reading out the information from the FW on the board, I get:
import chipwhisperer as cw
target = cw.target(None, cw.targets.CW310)
print(target.latest_fw)
print(target.sam_build_date)

{'major': 1, 'minor': 2}
23:46:21 Apr 24 2024

The correct firmware from 24.04.24 is flashed but the version number still is the old one. Reported to NewAE - hence keeping this PR as a draft  until this is resolved.


⚠ Fortnite has degraded performance

In 058af5f, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1523 ms

Resolved: Fortnite performance has improved in e93f76f.


make shell scripts more strict

shell scripts by default skip over errors and continue. it's best practices to use set to harden this using the following flags:

-e: Exit immediately if a command exits with a non-zero status.
-u: Treat unset variables as an error when substituting.
possibly also -o pipefail: If set, the return value of a pipeline is the value of the last (rightmost) command to exit with a non-zero status, or zero if all commands in the pipeline exit successfully. By default, pipelines only return a failure if the last command errors. When used in combination with set -e, pipefail will make a script exit if any command in a pipeline errors.

so far i've used set -eu, but i've seen that OpenSearch has also used set -e -o pipefail (see example below).
i think somebody with expert knowledge in this area (i wouldn't consider myself an expert here) should define the standard to be used in all scripts (or rules for when to use what if there are differentiating needs).
some scripts already have this set, e.g.:
https://github.com/opensearch-project/OpenSearch/blob/c8ac0373895fe6b884792569029bdc9d465850b5/distribution/src/bin/opensearch-env#L3
others don't, e.g. https://github.com/opensearch-project/OpenSearch/blob/main/distribution/packages/src/deb/init.d/opensearch
this is relevant not just for this repository but for all repositories (i'm not aware of a meta-repository where to open such tickets, feel free to move this ticket if such a place exists).
standardising and applying this globally will ensure that errors are not (silently) hidden.

Hey @rursprung !  I agree, standardizing this would keep us from falling into pits, which is always good.
We have a couple of global-ish repos like clients/plugins/meta.  @dblock do you have a thought on where this should go?
At the very least, we could set up the defaults in core (opensearch-project/opensearch) while we figure out the right way to track it against all repos.   @owaiskazi19 can you take a swing at that for core?

I would start doing this work here, then we can expand it into a campaign.

@owaiskazi19 / @dblock: where should we now create a follow-up ticket to apply the same to the other repos? and who'll create the ticket? that ticket should then probably also directly include doing #3343 as well for the others.

We often run these as campaigns. Do you want this to be OpenSearch-wide? Also apply to Dashboards? Only plugins?

We often run these as campaigns. Do you want this to be OpenSearch-wide? Also apply to Dashboards? Only plugins?

i'd suggest to do it consistently for everything under @opensearch-project, i think it applies to all of them.


Broken model links

Thank you very much for your excellent work. It appears that the links for the SlowFast and JHMDB models in MODEL_ZOO.md are broken. The SlowFast may be the same as the one published in HIT_ava's MODEL_ZOO.md. Could you please fix the links? Thank you.

Thank you for noticing that. The links to the SlowFast models from HIT_ava still work (they should be the same).
I haven't added the JHMDB pretrained model yet.

Thank you for your reply. I would like to try training with the SlowFast pretrained model that is available in HIT_ava.

I want to know if you still have the pre-trained model and JHMDB model?