Float the next window going to be opened

I used the following to open iTerm in floating mode (only when I wanted to) - in chunkwm
 cmd  - return      : chunkc set window_float_next 1; /Applications/iTerm.app/Contents/MacOS/iTerm2

How can I implement an equivalent in yabai wm. The following didn't work (the new window remains titled)
cmd  - return      : /Applications/iTerm.app/Contents/MacOS/iTerm2 ;\
       		     yabai -m window --toggle float

What am I missing? Sorry, if it has already been addressed/answered and that I didn't search properly.
Any help is highly appreciated.

What you're missing with your second approach is that you're toggling float on the focused window, which isn't iTerm2 if you've just opened it.
Something like this works pretty well:
yabai -m signal --add label=float_next app='^iTerm2$' event=window_created action='yabai -m signal --remove float_next; yabai -m window $YABAI_WINDOW_ID --toggle float'

Note that the event=window_created signal doesn't trigger when windows are restored when an application launches, so the logic would need to be adapted for this to also works for restored windows.

Thank you @dominiklohmann  for quickly putting up a solution.
I tested it on my machine, adding the above line to yabairc.
When I fire-up a new iTerm2, it fails to float and gets tiled (it also appears that the window gets floated for a fraction of a second at start, but then falls back to be tiled immediately). I have no other rules/signals set for iTerm2. I killed all iTerm2 windows, restarted yabai etc, but nothing worked. It feels as if it's getting overridden by some other setting?

I explained that caveat above.

Note that the event=window_created signal doesn't trigger when windows are restored when an application launches, so the logic would need to be adapted for this to also works for restored windows.

You'll have to hook into event=application_launched, which carries $YABAI_PROCESS_ID, which can then be turned into a set of window ids on start.
Something like this (off the top of my head, this is not battle-tested):
# trigger on window_created
yabai -m signal --add label=float_next_window_created event=window_created action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m window $YABAI_WINDOW_ID --toggle float'

# trigger on application_launched
yabai -m signal --add label=float_next_application_launched event=application_launched action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m query --windows | jq -r ".[] | select(.pid == $YABAI_PROCESS_ID).id" | xargs -I{} yabai -m window {} --toggle float'

Yes, this workaround is ugly. And no, there is no unified window_spawned event that does this for you.

Thank you again.
@dominiklohmann I did update my previous comment - in case you missed it ...
[Update] It has to do something with the way I launch iTerm2. When I launch iTerm through Launchpad --> iTerm2 OR iTerm2-Menu --> Shell --> New Window; then the newly spanned iTerm2 window actually FLOATS. So, wondering what's wrong doing the same through shkd using
cmd - return : /Applications/iTerm.app/Contents/MacOS/iTerm2

I did read your update, and I think you're still misunderstanding the difference between restored windows and created windows on a semantic level.
When an application first launches, the windows opened by it are restored. They do not trigger an event=window_created signal, but rather an event=application_launched signal. Note that this can be multiple windows at the same time, which is why the signal carries a process id, and you need to do an additional query to get all windows that belong to that process id.
Opening additional windows creates them. These do trigger event=window_created, but not event=application_launched. This is always just a single window, which is why this signal carries the window id directly.

Thank you for the explanation and being very helpful. I think I got the point this time.
So, now I am trying to think if it is possible to replicate process involved in doing (clicking)Launchpad --> iTerm2 OR iTerm2-Menu --> Shell --> New Window using an apple-script (then trigger it from shkd). I  am not good in apple-script either and hence could not think of a possibility.
Sorry, if I again missed/mis-understood some thing. Thank you for being considerate and helpful.

The easiest is just to create triggers for both signals as I've shown above:

# trigger on window_created
yabai -m signal --add label=float_next_window_created event=window_created action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m window $YABAI_WINDOW_ID --toggle float'

# trigger on application_launched
yabai -m signal --add label=float_next_application_launched event=application_launched action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m query --windows | jq -r ".[] | select(.pid == $YABAI_PROCESS_ID).id" | xargs -I{} yabai -m window {} --toggle float'

E.g., in your .skhdrc:
 cmd - return : \
    yabai -m signal --add label=float_next_window_created event=window_created action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m window $YABAI_WINDOW_ID --toggle float' ; \
    yabai -m signal --add label=float_next_application_launched event=application_launched action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m query --windows | jq -r ".[] | select(.pid == $YABAI_PROCESS_ID).id" | xargs -I{} yabai -m window {} --toggle float' ; \
    /Applications/iTerm.app/Contents/MacOS/iTerm2

Obviously you could replace the way you open iTerm2 with some sophisticated AppleScript, but that's out of scope for this issue.

I did add the above lines to my .skhdrc for a quick test, but the spanned iTerm2 windows again failed to float.
Reading those lines I am convinced that it should float the next spawned window, but didn't. May be I am still missing/mis-understanding something.... Hope someone successfully gets it to work.
I sincerely appreciate all the efforts of @dominiklohmann

I've simply pasted what's below into my skhdrc and it works. Only thing I've exchanged is how I open iTerm2.
 cmd - return : \
    yabai -m signal --add label=float_next_window_created event=window_created action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m window $YABAI_WINDOW_ID --toggle float' ; \
    yabai -m signal --add label=float_next_application_launched event=application_launched action='yabai -m signal --remove float_next_window_created; yabai -m signal --remove float_next_application_launched; yabai -m query --windows | jq -r ".[] | select(.pid == $YABAI_PROCESS_ID).id" | xargs -I{} yabai -m window {} --toggle float' ; \
    osascript -e 'tell application "iTerm2" to create window with default profile command ""' || open -b com.googlecode.iTerm2

As a sidenote, I am not convinced that cmd + return is a good shortcut, since that actually overrides system functionality (confirm input/form while still in a text field of that input/form). For example, I can send the issue reply I am currently writing by pressing cmd + return without leaving the text field.

I tried with you last script and it WORKED ! Yes, the new iTerm window did FLOAT this time.
When I went back again to /Applications/iTerm.app/Contents/MacOS/iTerm2  , it didn't work.
So, Yes the way you open iTerm2 really matters here (at-least for me).
Anyway, happy to have a nice feature (that I missed for quite a while). Thanks to the command-line wizardry of @dominiklohmann


Unable to install Viewsb: "No matching distribution found for usb_protocol"

OS:
➜  uname -a
Linux mjc-virtual-machine 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
➜

Operating procedures:
➜  python3 -V
Python 3.8.10
➜  python3 -m pip -V
pip 22.1.2 from /home/mjc/.local/lib/python3.8/site-packages/pip (python 3.8)
➜

➜  git clone https://github.com/greatscottgadgets/ViewSB.git
。。。
➜  python3 -m pip install . --proxy http://<IP_ADDRESS>:7890
Defaulting to user installation because normal site-packages is not writeable
Processing /home/mjc/prog/luna_usb/ViewSB
  Preparing metadata (setup.py) ... done
Collecting construct
  Using cached construct-2.10.68.tar.gz (57 kB)
  Preparing metadata (setup.py) ... done
Collecting bitstruct
  Using cached bitstruct-8.15.1.tar.gz (34 kB)
  Preparing metadata (setup.py) ... done
Collecting tableprint
  Using cached tableprint-0.9.1-py3-none-any.whl (6.8 kB)
Collecting urwid
  Using cached urwid-2.1.2.tar.gz (634 kB)
  Preparing metadata (setup.py) ... done
ERROR: Could not find a version that satisfies the requirement usb_protocol (from viewsb) (from versions: none)
ERROR: No matching distribution found for usb_protocol
➜

Not sure what the issue is but locally I did :
pip install<EMAIL_ADDRESS>and that was good enough.

Not sure what the issue is but locally I did :
pip install<EMAIL_ADDRESS>and that was good enough.

I've try this and failed
When I open the url https://github.com/greatscottgadgets/python-usb-protocol
it has been redirect to https://github.com/greatscottgadgets/python-usb-protocol
so I've test command with new url
pip install git+https://github.com/greatscottgadgets/python-usb-protocol
it would install a package with name UNKNOWN, and viewsb.sh fail to locate usb_protocol
so I've test pip install<EMAIL_ADDRESS>but it failed still.
so any suggest to make it work?

We'll have official releases for usb-protocol in the next couple weeks, for now you can try:
pip install "usb-protocol @ git+https://github.com/greatscottgadgets/python-usb-protocol"

We'll have official releases for usb-protocol in the next couple weeks, for now you can try:
pip install "usb-protocol @ git+https://github.com/greatscottgadgets/python-usb-protocol"

Hi antoinevg
Thanks for the reply first
unfortunately it is still failed
I've post the install log with verbose args
is that missing setup.py?
Thanks!
mosquito@mosquito-X260:~/test$ pip -v install "usb-protocol @ git+https://github.com/greatscottgadgets/python-usb-protocol"
Using pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
Defaulting to user installation because normal site-packages is not writeable
Collecting usb-protocol@ git+https://github.com/greatscottgadgets/python-usb-protocol
  Cloning https://github.com/greatscottgadgets/python-usb-protocol to /tmp/pip-install-chbb3vhx/usb-protocol_f041860f504149f59cc5a695b8b02028
  Running command git version
  git version 2.34.1
  Running command git clone --filter=blob:none https://github.com/greatscottgadgets/python-usb-protocol /tmp/pip-install-chbb3vhx/usb-protocol_f041860f504149f59cc5a695b8b02028
  正複製到 '/tmp/pip-install-chbb3vhx/usb-protocol_f041860f504149f59cc5a695b8b02028'...
  Running command git rev-parse HEAD
  5730bc08c5641c7c11fa827d2418dfaf22598004
  Resolved https://github.com/greatscottgadgets/python-usb-protocol to commit 5730bc08c5641c7c11fa827d2418dfaf22598004
  Running command pip subprocess to install build dependencies
  Collecting setuptools>=64
    Using cached setuptools-70.0.0-py3-none-any.whl (863 kB)
  Collecting setuptools-git-versioning<2
    Using cached setuptools_git_versioning-1.13.6-py3-none-any.whl (10 kB)
  Collecting packaging
    Using cached packaging-24.0-py3-none-any.whl (53 kB)
  Collecting toml>=0.10.2
    Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
  Installing collected packages: toml, setuptools, packaging, setuptools-git-versioning
  Successfully installed packaging-24.0 setuptools-70.0.0 setuptools-git-versioning-1.13.6 toml-0.10.2
  Installing build dependencies ... done
  Running command Getting requirements to build wheel
  running egg_info
  creating UNKNOWN.egg-info
  writing manifest file 'UNKNOWN.egg-info/SOURCES.txt'
  writing manifest file 'UNKNOWN.egg-info/SOURCES.txt'
  Getting requirements to build wheel ... done
  Running command pip subprocess to install backend dependencies
  Collecting wheel
    Using cached wheel-0.43.0-py3-none-any.whl (65 kB)
  Installing collected packages: wheel
  Successfully installed wheel-0.43.0
  Installing backend dependencies ... done
  Running command Preparing metadata (pyproject.toml)
  running dist_info
  creating /tmp/pip-modern-metadata-cvgyz9_3/UNKNOWN.egg-info
  writing manifest file '/tmp/pip-modern-metadata-cvgyz9_3/UNKNOWN.egg-info/SOURCES.txt'
  writing manifest file '/tmp/pip-modern-metadata-cvgyz9_3/UNKNOWN.egg-info/SOURCES.txt'
  Preparing metadata (pyproject.toml) ... done
  WARNING: Generating metadata for package usb-protocol produced metadata for project name unknown. Fix your #egg=usb-protocol fragments.
Discarding git+https://github.com/greatscottgadgets/python-usb-protocol: Requested unknown from git+https://github.com/greatscottgadgets/python-usb-protocol has inconsistent name: filename has 'usb-protocol', but metadata has 'unknown'
ERROR: Could not find a version that satisfies the requirement usb-protocol (unavailable) (from versions: 0.0.1, 0.0.2)
ERROR: No matching distribution found for usb-protocol (unavailable)
mosquito@mosquito-X260:~/test$

Ah, the issue here may be that your pip version is 22 and there's been quite a lot of churn with python packaging over the last two years. Are you able to update your pip to version 24 ?

Ah, the issue here may be that your pip version is 22 and there's been quite a lot of churn with python packaging over the last two years. Are you able to update your pip to version 24 ?

Ah~~ it's worked !!!!
I've install usb-protocol sucessfully!
Now I can study how to using ViewSB now
Thanks for your help :D


Fix sample documentation and bump dependencies.

Thanks @minudika for sending these fixes.

Please merge only after analytics.solutions version 1.0.10 and carbon.dashboards version 4.0.37 are released.


add trainable weights in loss function

Hi all,
I want to include trainable weights in loss function. As I dont know how to, I use a layer that contains weight only. This layer only output weights to loss function.
However, there are too many weights variables, I dont want to output all of them for the whole batch. So I decide to select some of related weights variables as an output.
I will use input class info to select weights variables.
For example. My layer has a kernel of size (10, 1024). Then if input is 0, it outputs kernel[0, :]. If input is 1, kernel[1,:]
However, when I implement following model, the input always has a shape of (?, 1).  ? is the undefined batch number. So, I use this line to select output for these inputs.
proxy_of_class = self.kernel[x[:,0], :]
But I always encounter this error:
  File "proxyModel.py", line 18, in call
    proxy_of_class = self.kernel[x[:,0], :]
ValueError: Shapes must be equal rank, but are 1 and 0
        From merging shape 0 with other shapes. for 'proxy/strided_slice_1/stack_1' (op: 'Pack') with input shapes: [?], [].

How can I solve this problem?
Below is my code based on tensorflow1.6
from __future__ import division
import tensorflow as tf
from tensorflow.python.keras.models import Model
from tensorflow.python.keras.layers import Input, Conv2D, MaxPooling2D, Flatten, Dense, Layer

class Proxy(Layer):
    def __init__(self,num_class=2, **kwargs):
        self.num_class = num_class
        super(Proxy, self).__init__(**kwargs)
    def build(self, input_shape):
        self.kernel = self.add_weight(name='kernel',
                                        shape=(self.num_class, 1024),
                                        initializer='uniform',
                                        trainable=True,
                                        constraint=None)
        super(Proxy, self).build(input_shape)
    def call(self, x, mask=None):
        proxy_of_class = self.kernel[x[:,0], :]
        return proxy_of_class
    def compute_output_shape(self, input_shape):
        return (input_shape[0], 1024)

def build_model(image_size, n_classes):
    input1 = Input(shape=image_size) # for image encode
    flat = Flatten()(input1)
    dense = Dense(1024,activation='relu')(flat)
    input2 = Input(shape=(1,))       # for class index
    output = Proxy()(input2)
    model = Model(inputs=[input1, input2], outputs=[dense, output])
    model.summary()
    return model

build_model((224,224,3),2)

Is this a duplication of https://github.com/keras-team/keras/issues/9607?

Yes. It is similar to 9607. I just want to look for a more general method.


docs: update installation to match asdf v0.5.0 command

docs: update installation to match asdf v0.5.0 command
asdf v0.5.0 tells you to manage plugins using the format asdf plugin-{command} ... rather than asdf plugin {command} ...

was using an old version of asdf


cant save/load recordings

when i hit save recording nothing happens and when i hit load recording it says invalid file then loaded recording. Then when I hit start nothing happens

Please let me know which version you're using. Also note that recording files from previous mod versions do not work on newer versions. I'm really sorry for that but due to the mod being so early in development structure of the recording save files changes rather often and stuff gets added to it.

Sorry, ive been on break. Im using Alphine Client to launch the mod on 1.20.1

For that version, a dedicated JRE (Java Runtime Environment) has to be installed on your machine for the save/load mechanism to work. This was updated in later versions.
You are using the first release - I would recommend switching to a newer release for Minecraft 1.20.2 or 1.20.4. The version you are using was a proof of concept. I will check the workload required to support 1.20.1 for the latest mod version. If feasible, I will create a new release in the next few days. Otherwise, I'll let you know via a new comment that I will not be implementing that. In the latter case, feel free to use the 1.20.2 branch to create a working version of the mod's version 0.3.3 for Minecraft 1.20.1 and submit a pull request.


test(sinon): use sinon-jest-matchers for better error messages

Using sinon-jest-matchers for better error messages:
Before:
expect(received).toEqual(expected) // deep equality

Expected: 2
Received: 1

After:
expect(sinon.spy()).sinonToBeCalledTimes(expected)

Expected number of calls: 2
Received number of calls: 1

Disclaimer: I wrote that package, basically after I saw how we asserted spy calls here

Decided not to use this as one of our "selling points" are, we use well known packages


Bring README up to date

Organize the description a bit better
Replace the full example with a link to the module template so that if we change how this action is used we don't have to update this README.
Expand the description of the release-version output.
Add Release & Publishing section

CI started failing with error:0308010C:digital envelope routines::unsupported :(
Not sure if we need to upgrade Node on CI / in .nvmrc. I'll take a closer look at this.

CI started failing when running ncc with error:0308010C:digital envelope routines::unsupported. This has been reported multiple times, but I'm not sure if the maintainers actually fixed the problem.

Solved by upgrading ncc: https://github.com/MetaMask/action-publish-release/pull/67

Not sure if we need to upgrade Node on CI / in .nvmrc. I'll take a closer look at this.

From what I can tell, .nvmrc doesn't seem to be used in the build-lint-test pipeline right now, and we therefore get the image default (18.14.1).

From what I can tell, .nvmrc doesn't seem to be used in the build-lint-test pipeline right now, and we therefore get the image default (18.14.1).

Ah okay. Well, that's fine for now, then.


Unable to resolve data from the feeder file

Hi Team,
Our application uses encoded  values( base64 bit encoding) ,  so we have used a method as  below
def encodeData(data: String): String = {
java.util.Base64.getMimeEncoder().encodeToString(data.getBytes(StandardCharsets.UTF_8))
}
When we use same to method  in scripts
.feed(loginUserFeeder)
.exec(
...
.formParam("data",encodeData("""{"tbl0":{"csrfToken":"${"UserName"}"}}"""))
...
)
User name is not getting resolved with feeder value.
feeder has value "ABC".
After encoding  we are getting value as "eyJ0YmwwIjp7ImNzcmZUb2tlbiI6IiR7IlVzZXJOYW1lIn0ifX0=" which is nothing but {"tbl0":{"csrfToken":"${"UserName"}"}}, we are expecting {"tbl0":{"csrfToken":"ABC"}}
Can any one please help us on this

This is a question, and a user issue, not a Gatling bug.

Hi slandelle,
I tried doing all possible ways, but  was not successful. Can you please help us in resolving this?
I have posted same question on goggle groups, didn't get any reply. If goggle group is not right place to post question, please let us know the right forum.

If the documentation and the public mail list is not enough for you and you need fast answers from the Gatling experts, you can consider subscribing to our support offer: http://gatling.io/#/services


uses stored tablet file to delete bulk file

This looks good to me, should we merge this into main? Right now it's targeted just for elasticity

Hmm.. looking in main the method is not used, but should probably be updated in case its used.  The PR would be a subset of these changes.  I can fix it main first and when I merge it do the additional fix in elasticity.

This is done in bb36e45ef910b25942a394926e85ee8966411ee0 and 52f9e94a15564c79cd6b9c4bcf9bc8fa4be82379.  Fixed it in main and then made the small change needed in elasticity when merging main into elasticity.


ENETUNREACH Issue

Hello,
I am having an issue with Okhttp connecting to one of my servers on digital ocean. I keep getting  the following error:
java.net.ConnectException: failed to connect to /<IP_ADDRESS>  connect failed: ENETUNREACH (Network is unreachable). Note that I changed the ip address for privacy purposes. However, I can open the url in question in the browser with no issue.
This problem started yesterday. I would appreciate if someone has had a similar issue.
okio:1.5.0
okhttp-urlconnection:2.4.0
okhttp:2.4.0
I am also not setting any default connection time outs.
Here is my okhttp call:
     OkHttpClient client = getOkHttpClient();

    Request.Builder requestBuilder = new Request.Builder();
    Request request = requestBuilder.url(url).build();
    Call call = client.newCall(request);
    call.enqueue(new Callback() {
        @Override
        public void onFailure(Request request, IOException e) {
                    Logger.e(TAG,e.getMessage());
        }

        @Override
        public void onResponse(Response response) throws IOException {
                   Logger.d(TAG, response.body().toString());
        }

Does HttpURLConnection work on the same host?

(Closing as there's no action for us to take on this.)


add more fields to tests

Opening this to replace #177
Adding a few Test dimensions that could make analysis a bit easier.
short_name= shorter version of the test name, example. 'unique', instead of long name unique_my_first_model_col
test_type= 'singular' or 'generic'
test_severity_config= 'ERROR' or 'WARN'
model_refs= short name of model dependencies
source_refs= short name of src dependencies

@NiallRees @jaypeedevlin  - opening this to factor in the new changes from #188 . Worth noting I have not tested this since I initially wrote it and only tested on snowflake at the time.

Hi @patkearns10, I ran the integration tests and it looks like there are a couple of small issues. Let me know if I can help.

Thanks Nial, I'll take a look on my end this week!
On Tue, Oct 4, 2022 at 3:48 AM Niall Woodward @.***>
wrote:

Hi @patkearns10 https://github.com/patkearns10, I ran the integration
tests and it looks like there are a couple of small issues. Let me know if
I can help.
—
Reply to this email directly, view it on GitHub
https://github.com/brooklyn-data/dbt_artifacts/pull/213#issuecomment-1266539939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHJ6G3VWIGZXRLXWDRXE3F3WBPOM7ANCNFSM6AAAAAAQ2JRSQQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Pat Kearns
Sr. Analytics Engineer
P: +61 477 539 852
www.getdbt.com
http://www.getdbt.com/?utm_medium=email&utm_source=opensense
http://www.getdbt.com/?utm_medium=email&utm_source=opensenseConnect with
us:
https://github.com/dbt-labs/dbt http://linkedin.com/company/dbtlabs/
https://twitter.com/dbt_labs https://www.youtube.com/c/dbt-labs
https://blog.getdbt.com/of-the-community-by-the-community-for-the-community/?utm_medium=email&utm_source=opensense&utm_campaign=q3-2021_brand-launch

Came back to this! I was having issues with a helper macro, so had to nix that, at the expense of being less DRY. But now it works, tested locally in Snowflake!

@NiallRees @jaypeedevlin -  Does someone on your end need to kick off these tests?

HI @patkearns10 . I'm really sorry about how long is has taken someone to get back to you. I'm afraid your PR got caught up in a bit of limbo.
The changes that you have suggested look really useful and I'd love to be able to get this into the project. Please let me know if you still have appetite to work on this? I completely understand if you are no longer interested though, and I would be happy to bring it up to date with the current repo and make any required changes to ensure it works as expected instead.
One change that would need to happen once it's up to date is that the new fields all need to be added to the bottom of the lists in the upload_ macros as well as the sources.tests table. This is to ensure backwards compatibility with older versions. Let me know if this doesn't make sense and I'll happily demonstrate via a review comment instead.

Hi @glsdown , it has been a while since I have thought about this. A review comment would be extremely helpful :)


Modal cannot be closed by clicking on the backdrop.

The commit 444c488d62e1b653a1b6c98f0bbeed4040835131 removed the ability to close the modal by clicking on backdrop. However the documentation still refers to the option backdrop having the 'static' option. With the current code it is always the static.
We should either make it clear in the documentation that the backdrop option is only true or false (with no ability to close the modal by clicking on the backdrop), or add the functionality back in.

Please try the demo page. You can still close a modal by clicking on the backdrop. http://angular-ui.github.io/bootstrap/#/modal
You're referencing a commit from 2 years ago..

Ahh I see what what happened. I upgraded from 0.6.0 to 0.13.0, but forgot to upgrade the css. So I had to modify the backdrop template so it would close again and found this commit where it was removed.

Aah thats quite a big step haha. Glad it worked out for you.

I want to restrict the user if he clicks on backdrop, the modal pop up should not close

@Jeevanandanj if you want support, please follow the instructions here rather than commenting on a month's old issue, otherwise, no one may see it.


Proposal: A tool to migrate old MFC UI to WinUI

MFC is old and still new at the same time. Many applications are still being built using this framework. Over years there is a lot of code/UI built using this and it would be difficult for developers to migrate them to WinUI manually, one dialog at a time. It would be helpful if there was a wizard or a tool that could migrate these MFC projects to WinUI projects. Enabling organization to quickly adopt WinUI.

While migrating from MFC to WinUI (I.e. Create WinUI Desktop application and reuse the logic in MFC application), can we use MFC classes such as CString, CArray etc in WinUI project?


Check string size before Win32 MultiByte <-> WideChar conversions

This PR adds an additional check to ensure the target length of a string is within the supported maximum string length prior to calling WideCharToMultiByte/MultiByteToWideChar in the Windows runner template.
This is to prevent resize() from failing if called with a count > std::string::max_size().
According to Win32 API docs (WideCharToMultiByte, MultiByteToWideChar) it's the caller responsibility to make sure the buffers are correctly allocated.
This patch was originally proposed by @tgucio in #94608.
Pre-launch Checklist

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[X] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Unfortunately while attempting to rebase #94608 and re-trigger tests, the update to the @tgucio's original repo failed due to a permissioning error. I've re-opened the patch here with a cherry-pick of the original commit (i.e. the commit retains @tgucio as author).


2660 extract storage from table [do NOT merge]

Just leaving it here to see how many tests I've broken

Frontend tests were OK :+1: (details)

This is not final yet, so if you take a look do not strive for perfection. I'll let you know when it's ready for review. I just wanted to give it a try with all tests.

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

I screwed this branch so I'm starting from an early point in another PR


No Errors in logs when PAT expires using AzureDevOpsEntityProvider

Expected Behavior
When it cannot get data from Azure DevOps I would expect errors in logs. This happens with the AzureDevOpsDiscoveryProcessor.
Actual Behavior
It silently fails and the catalog is not updated. Even setting the logging level to debug shows no errors.
Steps to Reproduce

Use an expired PAT or one that doe snot have the correct access to read.
Run Backstage
Look at logs

Context
One day all the content disappeared from backstage (we are using in-memory DB, yet to move the real db) due to an issue with the token.

@goenning you may have an idea on this

I'm not sure tbh, but if there's an exception happening inside the call to Search API, I'd expect the outer functions to catch that and log It so at least it doesn't go completely silent.


Show model equations for inspected HARK AgentType and Market classes

For comparison, the dolo.compiler.model.Model class instances, when inspected in the REPL, provide some nice metadata and the equations for the model.
https://gist.github.com/sbenthall/54772209ab5108801a5fe166cff12b5b
Currently, with HARK AgentType and MarketClasses, it is difficult to find the equations of the models by inspecting the code or the objects.
The equations could potentially be put in the docstrings of these classes.
Or they could be printed to the user when the object is inspected.
This may be related to #446 -- this could be a way to communicate the parameters used in the object definition in a structured way.

depends on #761

Related to #660 #612

If we refactor to have parameters grouped/ available , it will be possible to display them/

We don't have a SST on transition equations. The closest we'll get to that by 1.0 is FrameAgentType.

Moving to 1.1 now that this is resolved for parameters.
need frame/equations explicit for next stage

Moving to 1.1 now that this is resolved for parameters.
need frame/equations explicit for next stage

See #1085
Will be feasible with #1427

Closing because this is a major part of the HARK 1 roadmap, and is actively being worked on.


Syntax highlighting for HTML files

How can I enable Svelte syntax highlighting for HTML files using LSP-svelte.
I've tried using the Svelte package, but it doesn't show up int the package settings just like LSP language server and other packages show up

Hello,
To answer your question,
Select View > Syntax > Open all with current extension as... > Svelte

Thank you 🙏🏼, that solved it


Non blocking attach clients

Enables clients that may be slow or prefer not to block the container's stdio to opt for dropping data over blocking stdio of the container.
This is especially useful for remote clients that may have a connection interruptions or are otherwise too slow to consume all the data produced by the container before the stdio buffers are full.
Note that to keep my sanity while adding this I did some code cleanup for AttachStreams.
As such there are 3 commits:

Adds non-blocking mode to BytesPipe
Cleans up some of the attach code
Plumbs through non-blocking options from clients.

ping @aaronlehmann
Related (in spirit) to #28762

Why should we encourage dropping data? Isn't the need for this feature showing that user is doing something wrong and not understanding the client-server model. It may have very surprising results that user may not realize when turning it on. I think the method we should recommend is docker run -d && docker logs.

useful for remote clients that may have a connection interruptions

Not sure I understand this. If attach stream drops the container will continue on full speed.

I don't think we are encouraging dropping data, rather we are giving the consumer a choice of whether or not the attached stream is important enough to block the container from doing it's work.

Network connections are unreliable (both in performance and stability)
Many applications spit out a lot of data (even if unexpectedly)
In many cases ensuring the task actually runs is way more important than consuming its output

Is there a really compelling reason to not let someone make this choice?

@cpuguy83 I'm not aware of ssh having --drop-data flag while it is exactly the same problem. Stopping users from making bad decisions is a good thing to do. All of the points you listed can be handled atm without dropping data. If the client connection is much slower, logs command can be used, if data is not needed containers can be put to background, opened streams can be configured or detached.

@tonistiigi SSH is a different use-case. This is more like exec where SSH is starting a new process in an existing environment.
Also, in terms of docker experience, only jsonfile and journald are support with docker logs.

I think I agree with Tonis on this one. It seems like the right workaround is to use docker logs. Dropping data has unclear ramifications that might not be noticed until it's too late. I think SSH is a good analogy.

This is fundamentally a different problem than SSH would be dealing with.
Opening an SSH session is not going to block an important service from doing it's work.
To take that even a step further, people use things like screen or tmux to make sure their jobs aren't killed when ssh is disconnected.
In current situation, if an attached client for whatever reason can't consume the pipe everything comes to a halt. The container can't write to it's stdio and as such can't perform work, logs aren't written, etc.
Let's even say in a happy case where the container process does not let itself get blocked on stdio, logs are still dropped, data is still lost.
I'm not sure I understand the line in the sand here.

@cpuguy83 Running a command through SSH blocks the process after a buffer is filled exactly the same way as Docker does it. The problem here is the behavior of user connecting to a processes stdio over a slow connection. I don't see a difference if it is a process in a host or a process inside a container or if you can detach and attach again.

@tonistiigi The difference is ssh is starting a new process, not connecting to an existing one.

If I ssh in and run screen -x, I'd imagine that this can block the process running inside screen.

Does docker attach --noblock compare to docker attach as https://mosh.org compares to ssh?

Just going to go ahead and close since it seems like some are adamantly opposed to introducing this.
Carrying the attach refactors in another PR.


Bug: last package selected displays its details even if there are no search results.

This probably won't be fixed until there's a way to see how many packages are visible, so it may take longer.

Maybe an option to clear selections on search and reset the description textbox's text would be useful.

Once v0.4 is out, this'll be unpinned.


datapy create schema

write a datapy create schema functionality similar to:
datapy create_schema -s <schema_name>

If this is going to be a command line execution then I'd like it to be both intuitive and sql like
datapy --create --schema <schema_name> feels more intuitive to me where datapy -cs <schema_name> would also be acceptable


Ac use zookeeper to preserve its state

This changes the bootstrap sequence, relying on Zookeeper instead of local disk.


WSAD Camera movement

Solves issue #18
Camera movement was moved from _unhandled_input to _process, otherwise the two input was interfering each other, now the mouse input will overwrite the keyboard.
Also _move does not get the mouse position as parameter rather gets directly from viewport

I've reformatted and squashed the changes.
Thanks for contributing!


Illegal instruction (core dumped)

I am running Ubuntu 14.04. The exact same code works on Ubuntu 16.04. I am using python3.
I have tried solutions from this issue with no luck.
I have tried using tensorflow 1.6, 1.5, and 1.4.

When using tensorflow 1.6: I'm relatively sure (no line number error) I get this output when importing keras.
When using tensorflow 1.5 and 1.4: I get the error at this line:

    model.add(LSTM(128, input_shape=(layers[1], layers[0]), return_sequences=True))

Here is some further context:
def build_model(layers):
    d = 0.2
    model = Sequential()
    model.add(LSTM(128, input_shape=(layers[1], layers[0]), return_sequences=True))
    model.add(Dropout(d))
    model.add(LSTM(64, input_shape=(layers[1], layers[0]), return_sequences=False))
    model.add(Dropout(d))
    model.add(Dense(16, kernel_initializer="uniform"))
    model.add(LeakyReLU(alpha=0.3))
    model.add(Dense(layers[2], kernel_initializer="uniform"))
    model.add(LeakyReLU(alpha=0.3))
    #adam = optimizers.Adam(lr=0.001, beta_1=0.9, beta_2=0.999, epsilon=1e-08, decay=0.0)
    model.compile(loss='mse', optimizer="rmsprop", metrics=['accuracy'])
    return model

Is this PowerPc (Minsky) by any chance? Do you get the core dump if you do lstm of size 1? How about of size 2000?
I spent along time debugging a similar issue - I think BLAS was at fault which was extremely hard to pinpoint

I stopped using a virtualenv and everything started working with tensorflow 1.5. No idea why.


FunctionalComponent with array emits does not work as expected

Version
3.0.0
Reproduction link
https://github.com/wonderful-panda/vue-next/commit/5cb6c2d9b3524538235730d22ac2485b5b697b83
Steps to reproduce
Pull linked commit, and run yarn test-dts
This is a problematic code
const Qux: FunctionalComponent<{}, ['foo', 'bar']> = (props, { emit }) => {
  emit('foo')  // OK
  emit('foo', 1, 2)  // OK
  emit('bar')  // TS2345: Argument of type '"bar"' is not assignable to parameter of type '"foo"'
}

What is expected?
No compile error.
What is actually happening?
TS2345 error is reported

Below code works as expected, but I think ['foo', 'bar'] is more straightforward and preferable.
const Qux: FunctionalComponent<{}, ('foo' | 'bar')[]> = (props, { emit }) => {
  ...
}

Sorry, this fix has a problem. (type of $emit is broken)
Before:

After:

I'll fix it and push extra commits.


Anyone can send messages through the API without need for login

How should we solve this?

We could generate a key or uuid, and store it in a list with all the logged in users uuids/keys, and remove it from the list when they log out, and to join the chat & send messages you're asked for it to send it

Probably fixed in b9c5322e599e566f12a753a9c1225eb4179f3e23


Proposal: Add AsyncComputed

Sorry for not opening an issue first, but I had this implementation of an AsyncComputed that I thought could be discussed either for inclusion or as a direction for signalFunction() or a future Relay implementation.
Conceptually AsyncComputed is very similar to signalFunction() or Relays, so there's a ton of overlap. I wrote this while trying to wrap my head around https://github.com/tc39/proposal-signals/issues/30 and the signalFunction(). It's partly based on the shape of the Task utility that we have in Lit.
As I wrote in https://github.com/tc39/proposal-signals/issues/30#issuecomment-2211568430, AsyncComputed has these features:

It takes a Promise-returning computation function with an AbortSignal argument: (signal: AbortSignal) => Promise<T>
The function is called within an internal Signal.Computed, so all synchronous signal access is tracked
When the internal computed runs, it re-runs the compute function, pre-empting any pending run and aborting their abort signals.
It has signal-backed getters for its state:

state: one of 'initial', 'pending', 'complete', or 'error'. state will synchronously change to 'pending' when dependency signals are dirtied.
value: the last completion value if the last completion type was 'complete', otherwise undefined
error: the last error if the last completion type was 'error', otherwise undefined

It has a complete getter that returns a Promise that settles when the AsyncComputed does. If a new run is triggered before the previous completes, the same Promise instance is kept. If a new run is started after a completion, a new Promise is created.
It has a get() method that returns the latest completion value or throws if the last completion was an error.
It has a run() method to manually read from the internal computed and trigger a run. Otherwise the computed is read from the various getters.

I found this API shape and implementation to be relatively simple, and I'm starting to use it throughout my code base.
Compared to signalFunction() I think this mainly has a slightly smaller public API, doesn't use SignalAsyncData, and has AbortSignal support. The completion promise behavior is different - AsyncComputed's complete promise will be shared among concurrent/preempted runs and only settled by the most recent run.
Compared to Relays I think the differences are that there are no consumer APIs for altering the state, and instead of passing get and set functions to the compute function, it relies on the return value of the compute function, and there's no update/destroy concept inside the compute function.
I think it's worth noting that utilities like this are also similar in some ways to libraries like TanStack Query, which are very feature-rich with things like caching, debouncing, etc. I think most of those feature can be implemented as part of the compute function. It may be helpful to pass the AsyncComputed instance back to the compute function to use as a key for caches or WeakMaps that store last invocation time for debouncing. Implementing debouncing inside the compute function would also require some kind of conditional gate on a run - either a shouldRun function in the options, or supporting an AbortError being thrown synchronously from the compute function as a way to cancel preemption.

@NullVoxPopuli this is ready for review now!


Provisioning storage accounts is sometimes very slow

I have noticed that sometimes provisioning storage accounts is very slow.  Example:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2211220&view=logs&j=6645e21d-96b8-5699-8b67-da8d67fe3d82&t=61ded3a0-8afa-5eb1-9668-cc90a8e869e9
It has been repeating Checking deployment status for over 30 minutes now, but will usually succeed eventually.
I assume this is a service issue actually completing the deployment, rather than a client issue in our deployment script.  But it would be nice to understand what causes this, and see if our deployment script could print more information about why the deployment is taking so long (if the service exposes this information).

@mikeharder digging in here it says the job was continuously postponed for a bit by the RP: https://asi.azure.ms/view/services/ARM/pages/Correlation Ids?timestamp=2023-02-23T04%3A16%3A56.8256179Z&correlationId=2e951c84-28a7-4764-ab39-a65247df8359
Is there anything special about the storage accounts that are getting deployed?

Bicep is here: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/storage/Azure.Storage.Blobs/perf-resources.bicep
It's a premium storage account, but otherwise nothing very special.
Looking in the logs you shared, I think we hit the storage RP hourly write quota (1200 writes per hour) and were being throttled:

"statusMessage":"{"error":{"code":"TooManyRequests","message":"The request is being throttled as the limit has been reached for operation type - Write_ObservationWindow_01:00:00. For more information, see - https://aka.ms/srpthrottlinglimits"}}"

I think the only solution here would be to shard test resources across multiple subs.


Create issue-reminder.yml

Description: Create a GitHub Actions workflow that sends reminders on open issues without updates for 7 days. The workflow should post a comment prompting assignees to take action.
fix #132
close #132
Expected Benefits:
Improved responsiveness and prioritization of tasks.
Increased overall productivity.

hey @vanshchauhan21 thanks a lot man it was great working for you

waiting for your response @vanshchauhan21

waiting for your response @vanshchauhan21

Done bro 👍

hey @vanshchauhan21 thanks a lot man it was great working for you can you add level3 label and all the labels

You did a great job 👍

@vanshchauhan21 add level 1, as workflows are = level 1

Done ✅


Added drag and drop support for shader include files in shader editor

This is in reference to issue #74392.
Production edit: Fixes https://github.com/godotengine/godot/issues/74392

Thanks, and congrats on your first merged pull request!

Thanks! @YuriSizov and @clayjohn


Typescript - Component's property types are not correct

Version
Vuejs: 2.5.16
Typescript: 2.8.1
Reproduction link
https://stackblitz.com/edit/typescript-rrnw8z?file=index.ts
Steps to reproduce

Use typescript
Create a component with at least one property

What is expected?
If your property of type X is not required, its type should be X | undefined
What is actually happening?
If your property of type X is not required, its type is still X

More dangerous: The properties are not required by default and you can easily write code that will fail at runtime.
Note: The stackblitz above won't show the error because the types are not correctly assumed and this is assumed as any

https://github.com/vuejs/vue/issues/6901#issuecomment-339054776

Will this issue be fixed in Vue 3.x ?
Or how to correct it with TS 3.4+ ? 😕


progress bar issues

as the header suggests, the progress bar can't react to the 5 seconds skip when clicking the left or right arrow on the keyboard

Same issue with node sliders while resetting them
video

In addition, if I do not have amethyst on my screen and it is running in minimized mode, the progress bar goes slower.

it is very clear that this is not 3:51/4:17 on the progress bar because the track is noticeably quieter in that part.

okay I noticed that part of these issues are solved but this will still be open

1st issue of this issue
Which one?
The arrow keys for me work fine.

1st issue of this issue

Which one? The arrow keys for me work fine.

1st issue of the issue meaning the arrow keys one is fixed
the 2nd issue which I mentioned 3 weeks ago didn't get fixed, it is still there - I'm talking about the progress bar going slower when Amethyst is in minimized mode.


[KMP Algorithm (Knuth-Morris-Pratt)]

String Matching: O(n + m) where n is text length and m is pattern length
Efficiently finds occurrences of a "word" within a main "text string" by employing the observation that when a mismatch occurs, the word itself embodies sufficient information to determine where the next match could begin.

@AlgoGenesis please assign me this task

Do not create unnecessary issues until you complete the previous one.


DOC: fix Numpy version requirement in INSTALL.rst.txt

[ci skip]

backported to 0.16.x in e45089e


Update introduced Split Packages when used with Java Modules

Thanks for stopping by to let us know something could be better!
If you are still having issues, please include as much information as possible:
Environment details

Specify the API at the beginning of the title. For example, "BigQuery: ...").
General, Core, and Other are also allowed as types
OS type and version:
Java version: 11
clouderrorreporting version(s): 0.122.x

Steps to reproduce

Create a project using java modules with a module-info.java file.
Require both google.cloud.errorreporting and proto.google.cloud.error.reporting.v1beta1.
Build the module with maven.

Error shown: module com.example.x reads package com.google.devtools.clouderrorreporting.v1beta1 from both proto.google.cloud.error.reporting.v1beta1 and google.cloud.errorreporting.
Code example
Have a module with pom.xml that includes this library i.e.
        <dependency>
            <groupId>com.google.cloud</groupId>
            <artifactId>google-cloud-errorreporting</artifactId>
            <version>0.122.5-beta</version>
        </dependency>

// example module-info.java
module com.example.x {
  requires google.cloud.errorreporting;
  requires proto.google.cloud.error.reporting.v1beta1;

  exports com.example.x.api;
}

Any additional information below
This was introduced in this pull request when the error reporting API surface was renamed, and the package was then split between the PROTO library and the client if I understand correctly.

Any update on this? It effectively breaks compatibility with Quarkus :/

Development of this library has moved to https://github.com/googleapis/google-cloud-java — if this issue is still relevant, can you please file a new issue there? We've significantly improved our process since this issue was filed, though, and a similar issue was recently closed as "obsolete" (https://github.com/googleapis/google-cloud-java/issues/5760). Thanks!


Does MOCO collapses under simpler augmentation?

Recently I have been applying your implementation to simpler datasets like CIFAR10. A strong augmentation will hurt the moco's convergence on a smaller dataset, so I simplified the augmentation when training MOCO on CIFAR10:
transforms.RandomCrop(32, padding=4),
transforms.RandomHorizontalFlip(),
transforms.ToTensor(),
normalize.
Under this simpler setting, the training top1 and top5 goes up to nearly 100% at about 20th epoch. The other hyperparameters are almost unchanged, except:  batch size=512, lr=0.015, arch=resnet-18, tau=0.1, k=4096.
Is this a phenomenon of collapsing?
Thanks.

Hi, I just curious if it is normal to have collapse in these approaches, because I thought contrastive learning would avoid collapse naturally with negative samples?

I think that these approaches are less likely to suffer from collapse comparing to other models like GANs. The InfoNCE loss can be seen to maximize the latent representation difference between an input vs (its another view and views of other inputs). Hence, the latent representations are designed to be scattered in a high-dimensional latent space.

I think that these approaches are less likely to suffer from collapse comparing to other models like GANs. The InfoNCE loss can be seen to maximize the latent representation difference between an input vs (its another view and views of other inputs). Hence, the latent representations are designed to be scattered in a high-dimensional latent space.

I think you are right. When data augmentation is simple, it cannot provide enough information for different views of each instance. So the trained models can put every instance far away from each other in latent space by over-fitting them thus get very high classification accuracy.

Did you test the downstream classification accuracy?


feat: use -expand option for paletted tiffs

These changes handle TIFFs with a band of Palette colour interpretation type, using the -expand argument to gdal_translate. This takes the contents of the colour palette and applies it to the rgb/rgba bands in the output file.
This resolves the following error encountered when standardising historical imagery survey SN9911:

ERROR 6: GTIFFBuildOverviews() doesn't support building overviews of multiple colormapped bands.

which used the band arguements -b 1 -b 1 -b 1.
It seems plausible that there could be malformed paletted TIFFs which would not be able to be standardised using this change, but it resolves the direct issue for SN9911.

Any files in s3://linz-topographic-upload/skyvuw/SN9911/TILES/ can be used for testing. Here is the gdalinfo output for SN9911_BN32_10k_0405.tif:
{
  "description":"SN9911_BN32_10k_0405.tif",
  "driverShortName":"GTiff",
  "driverLongName":"GeoTIFF",
  "files":[ "SN9911_BN32_10k_0405.tif" ],
  "size":[ 6400, 9600 ],
  "coordinateSystem":{
    "wkt":"PROJCRS[\"NZGD2000 / New Zealand Transverse Mercator 2000\",\n    BASEGEOGCRS[\"NZGD2000\",\n        DATUM[\"New Zealand Geodetic Datum 2000\",\n            ELLIPSOID[\"GRS 1980\",6378137,298.257222101004,\n                LENGTHUNIT[\"metre\",1]]],\n        PRIMEM[\"Greenwich\",0,\n            ANGLEUNIT[\"degree\",0.0174532925199433]],\n        ID[\"EPSG\",4167]],\n    CONVERSION[\"Transverse Mercator\",\n        METHOD[\"Transverse Mercator\",\n            ID[\"EPSG\",9807]],\n        PARAMETER[\"Latitude of natural origin\",0,\n            ANGLEUNIT[\"degree\",0.0174532925199433],\n            ID[\"EPSG\",8801]],\n        PARAMETER[\"Longitude of natural origin\",173,\n            ANGLEUNIT[\"degree\",0.0174532925199433],\n            ID[\"EPSG\",8802]],\n        PARAMETER[\"Scale factor at natural origin\",0.9996,\n            SCALEUNIT[\"unity\",1],\n            ID[\"EPSG\",8805]],\n        PARAMETER[\"False easting\",1600000,\n            LENGTHUNIT[\"metre\",1],\n            ID[\"EPSG\",8806]],\n        PARAMETER[\"False northing\",10000000,\n            LENGTHUNIT[\"metre\",1],\n            ID[\"EPSG\",8807]]],\n    CS[Cartesian,2],\n        AXIS[\"easting\",east,\n            ORDER[1],\n            LENGTHUNIT[\"metre\",1]],\n        AXIS[\"northing\",north,\n            ORDER[2],\n            LENGTHUNIT[\"metre\",1]],\n    ID[\"EPSG\",2193]]",
    "dataAxisToSRSAxisMapping":[ 1, 2
    ]
  },
  "geoTransform":[ 1775200.0, 0.75, 0.0, 5492400.0, 0.0, -0.75 ],
  "metadata":{
    "":{
      "AREA_OR_POINT":"Area"
    },
    "IMAGE_STRUCTURE":{
      "COMPRESSION":"PACKBITS",
      "INTERLEAVE":"BAND",
      "MINISWHITE":"YES"
    }
  },
  "cornerCoordinates":{
    "upperLeft":[ 1775200.0, 5492400.0 ],
    "lowerLeft":[ 1775200.0, 5485200.0 ],
    "lowerRight":[ 1780000.0, 5485200.0 ],
    "upperRight":[ 1780000.0, 5492400.0 ],
    "center":[ 1777600.0, 5488800.0]
  },
  "wgs84Extent":{
    "type":"Polygon",
    "coordinates":[
      [
        [<PHONE_NUMBER>, -40.7006923 ],
        [<PHONE_NUMBER>, -40.765512 ],
        [ 175.132623, -40.7644753 ],
        [<PHONE_NUMBER>, -40.6996579 ],
        [<PHONE_NUMBER>, -40.7006923
        ]
      ]
    ]
  },
  "bands":[
    {
      "band":1,
      "block":[ 6400, 1 ],
      "type":"Byte",
      "colorInterpretation":"Palette",
      "metadata":{},
      "colorTable":{
        "palette":"RGB",
        "count":256,
        "entries":[
          [ 255, 255, 255, 255 ],
          [ 254, 254, 254, 255 ],
          [ 253, 253, 253, 255 ],
          [ 252, 252, 252, 255 ],
          [ 251, 251, 251, 255 ],
          [ 250, 250, 250, 255 ],
          [ 249, 249, 249, 255 ],
          [ 248, 248, 248, 255 ],
          [ 247, 247, 247, 255 ],
          [ 246, 246, 246, 255 ],
          [ 245, 245, 245, 255 ],
          [ 244, 244, 244, 255 ],
          [ 243, 243, 243, 255 ],
          [ 242, 242, 242, 255 ],
          [ 241, 241, 241, 255 ],
          [ 240, 240, 240, 255 ],
          [ 239, 239, 239, 255 ],
          [ 238, 238, 238, 255 ],
          [ 237, 237, 237, 255 ],
          [ 236, 236, 236, 255 ],
          [ 235, 235, 235, 255 ],
          [ 234, 234, 234, 255 ],
          [ 233, 233, 233, 255 ],
          [ 232, 232, 232, 255 ],
          [ 231, 231, 231, 255 ],
          [ 230, 230, 230, 255 ],
          [ 229, 229, 229, 255 ],
          [ 228, 228, 228, 255 ],
          [ 227, 227, 227, 255 ],
          [ 226, 226, 226, 255 ],
          [ 225, 225, 225, 255 ],
          [ 224, 224, 224, 255 ],
          [ 223, 223, 223, 255 ],
          [ 222, 222, 222, 255 ],
          [ 221, 221, 221, 255 ],
          [ 220, 220, 220, 255 ],
          [ 219, 219, 219, 255 ],
          [ 218, 218, 218, 255 ],
          [ 217, 217, 217, 255 ],
          [ 216, 216, 216, 255 ],
          [ 215, 215, 215, 255 ],
          [ 214, 214, 214, 255 ],
          [ 213, 213, 213, 255 ],
          [ 212, 212, 212, 255 ],
          [ 211, 211, 211, 255 ],
          [ 210, 210, 210, 255 ],
          [ 209, 209, 209, 255 ],
          [ 208, 208, 208, 255 ],
          [ 207, 207, 207, 255 ],
          [ 206, 206, 206, 255 ],
          [ 205, 205, 205, 255 ],
          [ 204, 204, 204, 255 ],
          [ 203, 203, 203, 255 ],
          [ 202, 202, 202, 255 ],
          [ 201, 201, 201, 255 ],
          [ 200, 200, 200, 255 ],
          [ 199, 199, 199, 255 ],
          [ 198, 198, 198, 255 ],
          [ 197, 197, 197, 255 ],
          [ 196, 196, 196, 255 ],
          [ 195, 195, 195, 255 ],
          [ 194, 194, 194, 255 ],
          [ 193, 193, 193, 255 ],
          [ 192, 192, 192, 255 ],
          [ 191, 191, 191, 255 ],
          [ 190, 190, 190, 255 ],
          [ 189, 189, 189, 255 ],
          [ 188, 188, 188, 255 ],
          [ 187, 187, 187, 255 ],
          [ 186, 186, 186, 255 ],
          [ 185, 185, 185, 255 ],
          [ 184, 184, 184, 255 ],
          [ 183, 183, 183, 255 ],
          [ 182, 182, 182, 255 ],
          [ 181, 181, 181, 255 ],
          [ 180, 180, 180, 255 ],
          [ 179, 179, 179, 255 ],
          [ 178, 178, 178, 255 ],
          [ 177, 177, 177, 255 ],
          [ 176, 176, 176, 255 ],
          [ 175, 175, 175, 255 ],
          [ 174, 174, 174, 255 ],
          [ 173, 173, 173, 255 ],
          [ 172, 172, 172, 255 ],
          [ 171, 171, 171, 255 ],
          [ 170, 170, 170, 255 ],
          [ 169, 169, 169, 255 ],
          [ 168, 168, 168, 255 ],
          [ 167, 167, 167, 255 ],
          [ 166, 166, 166, 255 ],
          [ 165, 165, 165, 255 ],
          [ 164, 164, 164, 255 ],
          [ 163, 163, 163, 255 ],
          [ 162, 162, 162, 255 ],
          [ 161, 161, 161, 255 ],
          [ 160, 160, 160, 255 ],
          [ 159, 159, 159, 255 ],
          [ 158, 158, 158, 255 ],
          [ 157, 157, 157, 255 ],
          [ 156, 156, 156, 255 ],
          [ 155, 155, 155, 255 ],
          [ 154, 154, 154, 255 ],
          [ 153, 153, 153, 255 ],
          [ 152, 152, 152, 255 ],
          [ 151, 151, 151, 255 ],
          [ 150, 150, 150, 255 ],
          [ 149, 149, 149, 255 ],
          [ 148, 148, 148, 255 ],
          [ 147, 147, 147, 255 ],
          [ 146, 146, 146, 255 ],
          [ 145, 145, 145, 255 ],
          [ 144, 144, 144, 255 ],
          [ 143, 143, 143, 255 ],
          [ 142, 142, 142, 255 ],
          [ 141, 141, 141, 255 ],
          [ 140, 140, 140, 255 ],
          [ 139, 139, 139, 255 ],
          [ 138, 138, 138, 255 ],
          [ 137, 137, 137, 255 ],
          [ 136, 136, 136, 255 ],
          [ 135, 135, 135, 255 ],
          [ 134, 134, 134, 255 ],
          [ 133, 133, 133, 255 ],
          [ 132, 132, 132, 255 ],
          [ 131, 131, 131, 255 ],
          [ 130, 130, 130, 255 ],
          [ 129, 129, 129, 255 ],
          [ 128, 128, 128, 255 ],
          [ 127, 127, 127, 255 ],
          [ 126, 126, 126, 255 ],
          [ 125, 125, 125, 255 ],
          [ 124, 124, 124, 255 ],
          [ 123, 123, 123, 255 ],
          [ 122, 122, 122, 255 ],
          [ 121, 121, 121, 255 ],
          [ 120, 120, 120, 255 ],
          [ 119, 119, 119, 255 ],
          [ 118, 118, 118, 255 ],
          [ 117, 117, 117, 255 ],
          [ 116, 116, 116, 255 ],
          [ 115, 115, 115, 255 ],
          [ 114, 114, 114, 255 ],
          [ 113, 113, 113, 255 ],
          [ 112, 112, 112, 255 ],
          [ 111, 111, 111, 255 ],
          [ 110, 110, 110, 255 ],
          [ 109, 109, 109, 255 ],
          [ 108, 108, 108, 255 ],
          [ 107, 107, 107, 255 ],
          [ 106, 106, 106, 255 ],
          [ 105, 105, 105, 255 ],
          [ 104, 104, 104, 255 ],
          [ 103, 103, 103, 255 ],
          [ 102, 102, 102, 255 ],
          [ 101, 101, 101, 255 ],
          [ 100, 100, 100, 255 ],
          [ 99, 99, 99, 255 ],
          [ 98, 98, 98, 255 ],
          [ 97, 97, 97, 255 ],
          [ 96, 96, 96, 255 ],
          [ 95, 95, 95, 255 ],
          [ 94, 94, 94, 255 ],
          [ 93, 93, 93, 255 ],
          [ 92, 92, 92, 255 ],
          [ 91, 91, 91, 255 ],
          [ 90, 90, 90, 255 ],
          [ 89, 89, 89, 255 ],
          [ 88, 88, 88, 255 ],
          [ 87, 87, 87, 255 ],
          [ 86, 86, 86, 255 ],
          [ 85, 85, 85, 255 ],
          [ 84, 84, 84, 255 ],
          [ 83, 83, 83, 255 ],
          [ 82, 82, 82, 255 ],
          [ 81, 81, 81, 255 ],
          [ 80, 80, 80, 255 ],
          [ 79, 79, 79, 255 ],
          [ 78, 78, 78, 255 ],
          [ 77, 77, 77, 255 ],
          [ 76, 76, 76, 255 ],
          [ 75, 75, 75, 255 ],
          [ 74, 74, 74, 255 ],
          [ 73, 73, 73, 255 ],
          [ 72, 72, 72, 255 ],
          [ 71, 71, 71, 255 ],
          [ 70, 70, 70, 255 ],
          [ 69, 69, 69, 255 ],
          [ 68, 68, 68, 255 ],
          [ 67, 67, 67, 255 ],
          [ 66, 66, 66, 255 ],
          [ 65, 65, 65, 255 ],
          [ 64, 64, 64, 255 ],
          [ 63, 63, 63, 255 ],
          [ 62, 62, 62, 255 ],
          [ 61, 61, 61, 255 ],
          [ 60, 60, 60, 255 ],
          [ 59, 59, 59, 255 ],
          [ 58, 58, 58, 255 ],
          [ 57, 57, 57, 255 ],
          [ 56, 56, 56, 255 ],
          [ 55, 55, 55, 255 ],
          [ 54, 54, 54, 255 ],
          [ 53, 53, 53, 255 ],
          [ 52, 52, 52, 255 ],
          [ 51, 51, 51, 255 ],
          [ 50, 50, 50, 255 ],
          [ 49, 49, 49, 255 ],
          [ 48, 48, 48, 255 ],
          [ 47, 47, 47, 255 ],
          [ 46, 46, 46, 255 ],
          [ 45, 45, 45, 255 ],
          [ 44, 44, 44, 255 ],
          [ 43, 43, 43, 255 ],
          [ 42, 42, 42, 255 ],
          [ 41, 41, 41, 255 ],
          [ 40, 40, 40, 255 ],
          [ 39, 39, 39, 255 ],
          [ 38, 38, 38, 255 ],
          [ 37, 37, 37, 255 ],
          [ 36, 36, 36, 255 ],
          [ 35, 35, 35, 255 ],
          [ 34, 34, 34, 255 ],
          [ 33, 33, 33, 255 ],
          [ 32, 32, 32, 255 ],
          [ 31, 31, 31, 255 ],
          [ 30, 30, 30, 255 ],
          [ 29, 29, 29, 255 ],
          [ 28, 28, 28, 255 ],
          [ 27, 27, 27, 255 ],
          [ 26, 26, 26, 255 ],
          [ 25, 25, 25, 255 ],
          [ 24, 24, 24, 255 ],
          [ 23, 23, 23, 255 ],
          [ 22, 22, 22, 255 ],
          [ 21, 21, 21, 255 ],
          [ 20, 20, 20, 255 ],
          [ 19, 19, 19, 255 ],
          [ 18, 18, 18, 255 ],
          [ 17, 17, 17, 255 ],
          [ 16, 16, 16, 255 ],
          [ 15, 15, 15, 255 ],
          [ 14, 14, 14, 255 ],
          [ 13, 13, 13, 255 ],
          [ 12, 12, 12, 255 ],
          [ 11, 11, 11, 255 ],
          [ 10, 10, 10, 255 ],
          [ 9, 9, 9, 255 ],
          [ 8, 8, 8, 255 ],
          [ 7, 7, 7, 255 ],
          [ 6, 6, 6, 255 ],
          [ 5, 5, 5, 255 ],
          [ 4, 4, 4, 255 ],
          [ 3, 3, 3, 255 ],
          [ 2, 2, 2, 255 ],
          [ 1, 1, 1, 255 ],
          [ 0, 0, 0, 255
          ]
        ]
      }
    }
  ]
}

Superseded by https://github.com/linz/topo-imagery/pull/547


[+Price, +Region/Zone] Implement IBM's PriceInfoHandler and fix some drivers

IBM

Implement PriceInfoHandler
Call wait.Done() when error occurrs (Fix go routine may not end when error occurred.)

Azure

Call wait.Done() when error occurrs (Fix go routine may not end when error occurred.)
Fix typo in GetPriceInfo()

OpenStack

Fix not available message of PriceInfo
Call wait.Done() when error occurrs (Fix go routine may not end when error occurred.)

Need to speed up IBM's GetPriceInfo() with go routine.

IBM: Call wait.Done() when error occurred in PriceInfoHandler


Re-enable TestRemove on windows once it works reliably

We've got intermittent failures on windows builds due to how gps handles its git invocations (@tro3 tracked it down here - https://github.com/golang/dep/issues/214#issuecomment-279156911) - but only on TestRemove. I've disabled the test on windows for now; this issue is to remind us that we need to re-enable the test once gps fixes its underlying issue.

Closing this, should no longer be an issue.


All RenderManagers should share the same logger

Looks like messages from different loggers are interleaved at random.  Have all constructed sub-RenderManagers share their parent's logger so that they log in the appropriate sequence.

Fixed in 7066a349e900b1fd1b99f7feb62251fd56a5f758


Update my-solutions in chapters 7 & 8 to working solutions (issues with heapless)

This pull request adds the my-solutions.md of chapter 7 and 8 to work with version 0.7.x of heapless.
Changes:

Use heapless = "0.7.10" (because why not? I can leave it out if necessary)
Use const generics with heapless (the my-solutions.md got left behind in #432)
Use core::str::from_utf8() instead of heapless::String::from_utf8(), because the latter one got removed in heapless heapless = "0.7.x"

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @adamgreig (or someone else) soon.
Please see the contribution instructions for more information.


Update JIRA Issue query + TableIssue UI

Summary of Changes
This PR:

Updates the jira issue query to use exact match on the full Table Key: .... that we provide. This fixes an issue where unrelated JIRA issues were being displayed due to fuzzy matching.
Update the TableIssue component to show the LoadingSpinner instead of ReportTableIssue. With the updated design, it's cleaner for the whole section to be replaced with the LoadingSpinner as oppose to just the Report Issue text which led also led to a misaligned spinner.

Tests
Updated tests to reflect changes.
Documentation
N/A but big fix can be called out in next patch release.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes, including screenshots of any UI changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes all tests documented in the developer guide

Codecov Report

Merging #415 into master will decrease coverage by 0.06%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##           master     #415      +/-   ##
==========================================
- Coverage   78.33%   78.27%   -0.07%
==========================================
  Files         196      196
  Lines        4889     4889
  Branches      638      638
==========================================
- Hits         3830     3827       -3
- Misses       1013     1016       +3
  Partials       46       46

Impacted Files
Coverage Δ

.../components/TableDetail/ReportTableIssue/index.tsx
91.30% <81.81%> (-6.66%)
:arrow_down:

...ication/proxy/issue_tracker_clients/jira_client.py
79.45% <100.00%> (ø)

...ic/js/components/TableDetail/TableIssues/index.tsx
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Releases v0.0.1

Dears,
We have reached milestone 1! Through our collaboration, we have finished setting up the project repo and building up our initial machine-learning model.
Please check the v0.0.1 release to approve the release or to comment on any potential changes.
Thanks,

Thank you team.

Thanks all. Great work!!


Auto generate port

🚀 Feature request

1.We both know the default port is 4200, but if  the 4200 is already used, the error was throw :
An unhandled exception occurred: Port 4200 is already in use. Use '--port' to specify a different --port, why not auto generate a port without conflicting existing port?
2.When debug multi angular application, it was inconvenient to auto assign new port without conflict with existing port.But for now it was really annoying assign a not-conflicting port.

Command (mark with an x)

[ ] new
[ ] build
[ x] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Hi, in such case you can use port 0 which is a wildcard port.
More info about port 0 https://www.lifewire.com/port-0-in-tcp-and-udp-818145


Fix preverb hyphens in syllabics

Fixes #314.

Codecov Report

Merging #315 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master   #315      +/-   ##
========================================
+ Coverage   84.96%    85%   +0.03%
========================================
  Files          60     60
  Lines        2294   2300       +6
========================================
+ Hits         1949   1955       +6
  Misses        345    345

Impacted Files
Coverage Δ

...eeDictionary/templatetags/creedictionary_extras.py
100% <100%> (ø)
:arrow_up:

...CreeDictionary_tests/test_creedictionary_extras.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


support for hasMany relationship for primitive types (string, int)

Describe the feature
Currently hasMany works only for objects.
e.g.
This works
{
    "person": {
        "name": "Superman",
        "favoritecolors": [{
            "ID": 1,
            "color": "Black"
        },
        {
              "ID": 2,
              "color": "Blue"
          }]
      }
}

This does not
{
    "person": {
        "name": "Superman",
        "favoritecolors": ["Black", "Blue"]
    }
}

Motivation
Many a times when we get data from external sources, we do not have control on data structure and this is pretty common.

Related Issues

Customize a datatype? and save them as string into database?

We won't be able to query them if stored as string. Also I will have to have an intermediate data type that first unmarshalls the data in original format and then convert it to the string format.
{
    "person": {
        "name": "Superman",
        "favoritecolors": "Black, Blue"
    }
}


Auto-complete for Content-Type and Accept dropdowns

Currently hard-coded to a few presets. Would be good to allow any custom values (even omit the Content-Type for GET requests if desired).

yup, would like to use application/x-www-form-urlencoded


chore(AP-1897): add cache-control header to webloader files

hotfix-v1.23-v1.22

Can we put this one into the release?

Can we put this one into the release?

Yes. I assume you mean the September release, yeah?


[MBL-1681] Fix confirm details bonus

📲 What
Use the bonus amount that's passed in to the confirm details page to initialize the stepper.
Note: This also adds tests for the no shipping confirm details vm, since these were missing. I'm skipping the "continue" button test since I think it's probably related to MBL-1687 and should be fixed as part of that work. In order to see changes to the copied test file, review commit by commit.
👀 See
Jira

Before 🐛
After 🦋

✅ Acceptance criteria

[x] Bonus amount/pledge amount persists when navigating to confirm details
[x] Bonus/pledge amount can be further changed on the confirm details page

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: Danger


querySelector('a') has a return type of HTMLAnchorElement | null, but should be HTMLAnchorElement | SVGAElement | null

Bug Report
🔎 Search Terms
querySelector HTMLAnchorElement
🕗 Version & Regression Information
This is the behavior in every version I tried, and I reviewed the FAQ for entries about querySelector
⏯ Playground Link
Playground link with relevant code
💻 Code

const svg = document.createElementNS("http://www.w3.org/2000/svg", "svg");
const a = document.createElementNS("http://www.w3.org/2000/svg", "a")
svg.appendChild(a);
const foundElement = svg.querySelector('a');
console.log(a);

🙁 Actual behavior
TypeScript is convinced that foundElement has type HTMLAnchorElement | null, despite it actually being an SVGAElement.
🙂 Expected behavior
TypeScript should recognize that foundElement has type HTMLAnchorElement | SVGAElement | null.
I think the fix could be to combine the overloads. Currently, it is
querySelector<K extends keyof HTMLElementTagNameMap>(selectors: K): HTMLElementTagNameMap[K] | null;
querySelector<K extends keyof SVGElementTagNameMap>(selectors: K): SVGElementTagNameMap[K] | null;

It could instead be
querySelector<K extends (keyof HTMLElementTagNameMap) | (keyof SVGElementTagNameMap)>(selectors: K):
  | (K extends keyof HTMLElementTagNameMap ? HTMLElementTagNameMap[K] : never)
  | (K extends keyof SVGElementTagNameMap ? SVGElementTagNameMap[K] : never)
  | null;

This seems like it would be incredibly breaky and we'd get a ton of complaints about "Well I don't have any a SVG elements in my document so stop bothering me". If we get more reports of this we can see if something should be done.


Localized Cluster.md

I have Localized the Cluster.md file under the issue #771
Please check.

@abh139 This PR has unwanted commits adding changes on LOCALIZATION.md which is out of the scope of Hindi localization. Can you fix this please

Check now


augur-node breaks if you have $DATABASE_URL set

Right now, it seems that postgres does not work and is not used. However, if you happen to have $DATABASE_URL set (I did), augur-node still tries to use postgres and breaks:
https://github.com/AugurProject/augur-node/blob/3be6f8df5e8a94fe2b32700e24eab75345b80772/src/setup/check-and-initialize-augur-db.ts#L35
The breakage is very annoying and cost me an hour or so, because it's quite hard to figure out why you're getting a SQL error!
Perhaps this line should just be an if(false) instead?
However, it seems that this PR might be re-enabling postgres, so maybe it's worth just ignoring and waiting until then?

https://app.clubhouse.io/augur/story/14663/github-augur-node-breaks-if-you-have-database-url-set

Is it true that Postgres support is currently broken and the only supported database is SQLite?

We've merged in PGSQL support, it should indeed be working. As of yesterday I was able to fully sync/use a UI against augur node.
One known issue is that FTS search doesnt quite work as expected.
Please report any other issues so we can take a look! We'll be updating our dev/test environments to have Postgres backed augur nodes for continuous testing over the next couple weeks.

@TristanH -- This should be working now since we've merged in postgresql support.
Please try again!


Fix soundness issues w/r ExactSizeIterator

Fixes #2118

Looks great! I just want to take a moment to play with this locally to confirm if the &dyn mut has noticeable benchmark / code size impact. Hopefully tomorrow at some point...

I just want to take a moment to play with this locally to confirm if the &dyn mut has noticeable benchmark / code size impact.

@davidhewitt did it make a difference? I'm curious now :)

No measurable perf difference. Code size - a little bit, figured as I couldn't see a perf change overall it seemed right 👍


Wrong rendering of texts with different font-weights on PDF

PhantomJS version: 2.1.1
Operating system: Windows 10 x64
Using PhantomJS binary downloaded from http://phantomjs.org/
Texts looks different in html file opened in browser and converted to PDF.
There is a difference between font-weight:700 and font-weight: 900 in browser but there is no difference in PDF.
Text with font-weight:900 don't look bold enough:

To reproduce:

extract files:
FontWeightIssue.zip
run command: phantomjs.exe "init.js" "test.html" "test.pdf"

One normal font does not support bold or italic, you should the specific fonts, like the code below:
@font-face {
font-family: AdventPro;
src: url(./font/AdventPro.woff2) format("woff2"), url(./font/AdventPro.woff) format("woff");
font-style: normal;
font-weight: normal;
}
@font-face {
font-family: AdventPro;
src: url(./font/AdventPro-Bold.woff2) format("woff2"), url(./font/AdventPro-Bold.woff) format("woff");
font-style: normal;
font-weight: bold;
}


[ja] Localize Loosely Coupled Architecture for Japanese

Describe your changes
Localize Loosely Coupled Architecture for Japanese.
Related issue number or link (ex: resolves #issue-number)
#2446
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

あらゆるところで誤字を生んでいました。
「粗」を「疎」に修正しました。


support vehicle=* tag

Recreation of https://github.com/openstreetmap/iD/issues/3945
In many cases vehicle= tagging is the best representation of situation on the ground
In particular: https://commons.wikimedia.org/wiki/File:Zakaz_ruchu_01.JPG sign is equivalent of vehicle=no, not motor_vehicle=no
See https://taginfo.openstreetmap.org/keys/vehicle https://wiki.openstreetmap.org/wiki/Key%3Avehicle
Ideally access field would allow setting this tag and if set it would also change display of bicycle and motor_vehicle unless this tags would be also set (like access is doing right now)

The logic of which access field affects which access field could get confusing to users who aren’t familiar with the tree on the main access key page. The discussion in openstreetmap/iD#3945 went in the direction of a nested tree of fields (simplified from the wiki page). Alternatively, iD could present a StreetComplete-like palette of access restriction signs to choose from. However, either approach would require changes to the field implementation in the editor itself, not just a simple change to the field definition in id-tagging-schema.

The logic of which access field affects which access field could get confusing to users who aren’t familiar with the tree on the main access key page.

Are you sure? Is the worry that users would be confused by bicycle treated as a vehicle and affected by limiting vehicles?

Yes, because words like “vehicle” have different meanings to different people. Many laypeople consider “vehicle” to mean “motor vehicle”. If “Vehicles” appears along with “Motor Vehicles”, the user might intuit that “Vehicles” excludes bicycles, but does it include horses?
I think it would be helpful to make the connections visually clear. Currently, the only row that affects the other rows is the general one for All, which is self-explanatory. Short of indentation, rearranging the rows to be strictly general to specific might help.

Good point about Vienna Convention vs MUTCD.

As a very first step towards adding support for this, I've modified iD's access field(s) to at least display the implied/derived values of the motor_vehicle and bicycle fields if a value for vehicle is already mapped. For example, a street with access=permissive + vehicle=no would be now shown as follows:

This somewhat improves the situation as existing features are now less wrongly represented in the table of the access field. But it is of course also not a final solution for the issue.

does “Vehicles” include horses?

No.  From a legal point of view a horse is not a vehicle, at least not in Germany.

A horse is legally a vehicle in the US.

What is the problem with simply providing vehicle support for Vienna Convention countries, and let the US sabotage itself. It seems weird that one of the, if not most common access restriction cannot be entered outside of the raw tag editor, and that because of a country that doesn't need it.

To be clear, I don’t mean to argue against the inclusion of a “Vehicles” row. I just think it would be helpful to make the relationships between these keys visually clear, for the same reason that the wiki presents the keys in a tree. Currently, the only row that affects the other rows is the general one for All, which is self-explanatory. Short of indentation, rearranging the rows to be strictly general to specific might help.

Rearranging the rows wouldn’t be bad for Vienna Convention countries, would it?

I just think it would be helpful to make the relationships between these keys visually clear, for the same reason that the wiki presents the keys in a tree.

I didn't comment on that, because, dirty secret, IRL access for vehicle classes are as a rule not defined hierarchically and even when they are, the positions can change depending on context/country/etc. So any order is likely as good as any other.

Thanks, I didn’t know that! In that case, should the logic in openstreetmap/iD@f7d1459c97a249c81aea07f292d56cf98be7cb2d depend on the country or context too?

IMHO not worth the trouble, for example for most countries the Vienna convention sign/rule for no motor vehicle access includes mopeds, but in some it doesn't. This is partially solvable with region specific presets, but  in any case the assumption that "vehicle" = motor_vehicle + bicycle would seem to be wrong, as in not including everything that is considered a vehicle.

@tyrasd would you merge a PR that adds a regional preset as described above? I am very in favor of having a simple fix now before a bigger project is started; that can still happen regardless. Working on the traffic_sign <> osm tagging project I run into this issue a lot.


Clean-ups

No more dymanic allocations
No extern "C" declarations

Waiting for https://github.com/twilio/breakout-massive-iot/pull/27 to be merged.

It looks like the error in CLI slipped by because scripts/verify_samples.sh is missing checking examples/TwilioTests

@rbeiter Do we need test_modem_* functions in OwlCLI.ino? Do you use them?


[5.7] Handle long tagged NSStrings

Cherry-pick of https://github.com/apple/swift/pull/60428

@swift-ci please test

@swift-ci please test

@swift-ci please test

There we go, that got the tests sorted. Good to go now.


initial thoughts on conversions and naming

I’ve realised actually that opaquebytes and valuetype probably want to use
the same function just taking a user-provided pointer and running the
constructor on that.
I do feel strongly that this one and the opaqueptr new() function should
not be called the same thing because they do a very different job.
On Sun, 8 Nov 2020 at 21:04, Scott Wilson<EMAIL_ADDRESS>wrote:

@scott-wilson commented on this pull request.
One thing I'm not super clear on. Are each case going to have a unique
constructor/destructor name? If so, then I think that's going to lead to
confusion. I'd probably prefer that each case has the same
constructor/destructor name, and the user of the method doesn't know/care
what the type is outside of the method's output and the type definition.
I'd probably go with *_new and *_delete, but I know some other people
prefer *_create for the constructor.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vfx-rs/rfcs/pull/4#pullrequestreview-525783986, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOYQXKDY2V5RWHBCH2ME3TSOZGIJANCNFSM4TOC573Q
.

So, this is coming from a Python background. The way you're doing things may be a very C way, so I'd love to have the knowledge gaps filled.
My reasoning for saying that all constructor/destructor methods should be called the same across all cases is because from my experience, the developer doesn't really care where the data comes from, as long as it is created (there's some obvious caveats to that statement). However, having a consistent naming for creating/destroying data is really important.
That's why I don't see having two sets of naming is beneficial. But, I could be the odd one out, so I'll happily take this moment as an educational moment.

Well in Python you don't have to care because everything's allocated on the
heap and the garbage collector takes care of everything for you, while in
Rust, C and C++ you have to make sure that memory is handled correctly, and
exactly how you handle it can have significant performance implications, so
the developer really should care a lot about how it's done.
Beyond that the rest comes down to personal style so everything from hereon
out is opinion. For me, if two functions do a different job then they
should have a different name. That way when I'm reading the code I know
what each function call does just by looking at it (hopefully, if they're
named well). If two functions have the same name but different behaviour I
then have to remember a) that they're different in the first place, b) what
each variant of the function does and then c) figure out which variant of
the function I'm calling by inspecting the types passed to it. Every
overload is essentially another piece of information that I have to hold in
my head while I'm reading the code. At some point my head gets full and
stuff starts spilling out my ears and bugs get introduced.
This is essentially the same argument I was making in the default arguments
thread for the same reason, which to borrow from the Zen of Python is
basically "explicit is better than implicit."
On Mon, 9 Nov 2020 at 17:48, Scott Wilson<EMAIL_ADDRESS>wrote:

So, this is coming from a Python background. The way you're doing things
may be a very C way, so I'd love to have the knowledge gaps filled.
My reasoning for saying that all constructor/destructor methods should be
called the same across all cases is because from my experience, the
developer doesn't really care where the data comes from, as long as it is
created (there's some obvious caveats to that statement). However, having a
consistent naming for creating/destroying data is really important.
That's why I don't see having two sets of naming is beneficial. But, I
could be the odd one out, so I'll happily take this moment as an
educational moment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vfx-rs/rfcs/pull/4#issuecomment-723751363, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOYQXMFMYQUI3E25QSMUB3SO5YB7ANCNFSM4TOC573Q
.


[MM-47202] - Desktop diagnostics

Summary
Add desktop diagnostics under Help => Run Diagnostics.
Ticket Link
https://mattermost.atlassian.net/browse/MM-47202
Screenshots

Example file
diagnostics_30-10-2022_16-29-7-766.txt
Release Note
Added application diagnostics

@tboulis Nice one! What milestone will be added to this? 5.3 I guess?

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/25837
https://circleci.com/gh/mattermost/desktop/25836
https://circleci.com/gh/mattermost/desktop/25835

Artifact links:
https://output.circle-artifacts.com/output/job/e9c7b3a4-1585-4311-ac99-1be70af25404/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-ia32.zip
https://output.circle-artifacts.com/output/job/e9c7b3a4-1585-4311-ac99-1be70af25404/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-x64.zip
https://output.circle-artifacts.com/output/job/e5a495d3-2a60-41dc-8d53-3975c1519f08/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-linux-x64.tar.gz
https://output.circle-artifacts.com/output/job/0fcc9316-ba51-48a8-a843-639c81a14a19/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-m1.dmg
https://output.circle-artifacts.com/output/job/0fcc9316-ba51-48a8-a843-639c81a14a19/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-x64.dmg

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/25837
https://circleci.com/gh/mattermost/desktop/25836
https://circleci.com/gh/mattermost/desktop/25835

Artifact links:
https://output.circle-artifacts.com/output/job/e9c7b3a4-1585-4311-ac99-1be70af25404/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-ia32.zip
https://output.circle-artifacts.com/output/job/e9c7b3a4-1585-4311-ac99-1be70af25404/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-x64.zip
https://output.circle-artifacts.com/output/job/e5a495d3-2a60-41dc-8d53-3975c1519f08/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-linux-x64.tar.gz
https://output.circle-artifacts.com/output/job/0fcc9316-ba51-48a8-a843-639c81a14a19/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-m1.dmg
https://output.circle-artifacts.com/output/job/0fcc9316-ba51-48a8-a843-639c81a14a19/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-x64.dmg

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/desktop/25876
https://circleci.com/gh/mattermost/desktop/25875
https://circleci.com/gh/mattermost/desktop/25874

Artifact links:
https://output.circle-artifacts.com/output/job/e776a8c9-416d-4f14-8684-156a6d5d1d12/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-m1.dmg
https://output.circle-artifacts.com/output/job/e776a8c9-416d-4f14-8684-156a6d5d1d12/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-mac-x64.dmg
https://output.circle-artifacts.com/output/job/b578a5b3-00f8-47ce-963f-3891ad8dc16a/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-ia32.zip
https://output.circle-artifacts.com/output/job/b578a5b3-00f8-47ce-963f-3891ad8dc16a/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-win-x64.zip
https://output.circle-artifacts.com/output/job/3c5891d9-80d4-4905-921c-36a44ec7cc75/artifacts/0/tmp/artifacts/mattermost-desktop-5.2.0-develop.1-linux-x64.tar.gz

@tboulis - Is documentation available on how to interpret the diagnostic report results that can be published via product documentation?


[Feature Request] Read AWS IAM v4 credentials externally

Insomnia Version: 6.0.2
Operating System: Mac 10.13.6

Details
I often use AWS IAM v4 authentication within Insomnia. It's a pain to copy/paste these credentials into Insomnia manually especially when you have different AWS profiles and using aws_session_tokens which often rotate.
It would save lot of time if Insomnia can read the current AWS IAM credentials externally - from ~/.aws/credentials based on profile names.

This sounds like a good use-case for a custom plugin. You could create a Template Tag that reads the file and parses out the necessary contents.

Is anyone aware of a plugin implementing this ?

I just created one! insomnia-plugin-aws-iam
The magic is done by the excellent awscred library.
It works out of the box (at least for me) but more documentation, testing etc will come soon.

Awesome, thanks for sharing @dankelleher! 🤗🎁

@gschier why don't we just instead fallback with getting the aws credentials from the aws sdk?
So from https://github.com/Kong/insomnia/blob/cb715f95659f917dbc8464e987cedc10cc1296f1/packages/insomnia-app/app/network/network.js#L581-L585
We could just do something like
import AWS from 'aws-sdk';
...
const {credentials: awsCreds} = AWS.config;
const credentials = {
   accessKeyId: authentication.accessKeyId || awsCreds?.accessKeyId || '',
   secretAccessKey: authentication.secretAccessKey || awsCreds?.secretAccessKey || '',
   sessionToken: authentication.sessionToken || awsCreds?.sessionToken || ''
};

This would load whatever default credentials that the user has defined. It would also pick up a more complex setup like if they are using profiles or not.


optimasi dockerfile & docker-compose

I optimized the base image which was smaller before, up to 1GB, now it is only 300 MB, I tidy up the writing structure and I update the docker-compose file to build automatically when it's up.

Thanks @jams008 . Can we possibly use a multistage build process?

I have tried it and the ci DCO is still problematic.

Thanks for the PR @jams008 . If you are interested, feel free to make more enhancements and create new PRs.

hi @ashokponkumar , you're welcome.


Rename the project

The name "static-admin" doesn't really evoke anything :D

Should I also get this a domain while I'm at it? Does every project need a domain, or is github pages good enough?

Maybe just a custom landing on my own site - josediazgonzalez.com/PROJECT_NAME_HERE.

This should also come with a new favicon lol.


feat(NODE-4185): Allow opting out of disk use

See also:

https://jira.mongodb.org/browse/MONGOSH-1183
https://jira.mongodb.org/browse/PM-2742

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Hey @lerouxb and @addaleax - the Node team discussed this work yesterday during our triage.  The Node driver currently doesn't pass along a value for allowDiskUse if no value is specified from the user.  This means that drivers changes aren't necessary for this work, because we won't be overriding the new server default with the old default.  The only other work associated with this change sync the new spec tests, which due to a miscommunication and time zone differences, @kampofo completed this morning (see https://github.com/mongodb/node-mongodb-native/pull/3231).  Sorry for the duplicated effort here but we'll close this PR and use Kobby's since the work is completed there.

Talked with @baileympearson on Slack, it seems like https://github.com/mongodb/node-mongodb-native/pull/3231 makes this appear like something that’s already done, but in reality the tests there don’t test the builder API, only the options object API, so we do still want this :slightly_smiling_face:

Yup.  We still want to make this change, but we should add tests for the new options.  I think the tests should go in find_cursor_methods.js.
As far as testing this option, we can use command monitoring on the MongoClient to ensure that the find commands contain the allowDiskUse option when they're sent to the database with the correct value.