doc(README): remove typo

Description:
This Pull Request fixes a typographical error in the README.md file.
Changes Made:

Corrected "accelarate" to "accelerate" in the README.md file.

Additional Information:
This fix is not related to any existing issue. It's a minor typo that I noticed while reviewing the README.
Thank you for considering this contribution.****

Thank u for your correction!


Failed to do make or make docs

hello,
I'm a beginner in cowboy web server, I just started to learn, and as a beginner, I started to follow the README. But unfortunately I realized a fault. The "make" and "make docs" reports some error when creatink symlink. Please check below logs, and let me know if I did something wrong.
Here is the log about what I did
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private> mkdir cowboy
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private> cd cowboy
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy> git clone https://github.com/ninenines/cowboy.git
Cloning into 'cowboy'...
remote: Counting objects: 7368, done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 7368 (delta 3), reused 0 (delta 0), pack-reused 7354
Receiving objects: 100% (7368/7368), 5.57 MiB | 1.33 MiB/s, done.
Resolving deltas: 100% (4346/4346), done.
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy> ls
cowboy
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy> cd cowboy/
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)> ls
all.sh        CHANGELOG.md     erlang.mk  Makefile      ROADMAP.md
AUTHORS       CONTRIBUTING.md  examples   README.md     src
build.config  doc              LICENSE    rebar.config  test
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)> make
 DEP    cowlib
ln: failed to create symbolic link `./erlang.mk': Read-only file system
make: *** [/mnt/ethrbh/private/cowboy/cowboy/deps/cowlib] Error 1
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)> ls -la
total 131
drwxrwxrwx 1 root root  4096 Jun 16 15:09 .
drwxrwxrwx 1 root root     0 Jun 16 15:08 ..
-rwxrwxrwx 1 root root   354 Jun 16 15:08 all.sh
-rwxrwxrwx 1 root root  1166 Jun 16 15:08 AUTHORS
-rwxrwxrwx 1 root root   597 Jun 16 15:08 build.config
-rwxrwxrwx 1 root root 30831 Jun 16 15:08 CHANGELOG.md
-rwxrwxrwx 1 root root  5498 Jun 16 15:08 CONTRIBUTING.md
drwxrwxrwx 1 root root     0 Jun 16 15:09 deps
drwxrwxrwx 1 root root     0 Jun 16 15:08 doc
-rwxrwxrwx 1 root root 58278 Jun 16 15:08 erlang.mk
drwxrwxrwx 1 root root  4096 Jun 16 15:08 examples
drwxrwxrwx 1 root root  4096 Jun 16 15:08 .git
-rwxrwxrwx 1 root root   102 Jun 16 15:08 .gitignore
-rwxrwxrwx 1 root root   757 Jun 16 15:08 LICENSE
-rwxrwxrwx 1 root root  2628 Jun 16 15:08 Makefile
-rwxrwxrwx 1 root root  1431 Jun 16 15:08 README.md
-rwxrwxrwx 1 root root   158 Jun 16 15:08 rebar.config
-rwxrwxrwx 1 root root  4123 Jun 16 15:08 ROADMAP.md
drwxrwxrwx 1 root root  8192 Jun 16 15:08 src
drwxrwxrwx 1 root root  4096 Jun 16 15:08 test
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)> make docs
 GEN    distclean-asciidoc
 GEN    clean-docs
 DEP    ezdoc
ln: failed to create symbolic link `./erlang.mk': Read-only file system
make: *** [/mnt/ethrbh/private/cowboy/cowboy/deps/ezdoc] Error 1
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)>

thanks for your help,
/Robi

Not sure why it tells you that you are on a read only filesystem. What OS is that? Maybe someone who uses Virtualbox can pinch in?

hello,
I am using pure Ubuntu inside Virtualbox. What is interested is, that I can clone and make other project like Erlang/ALE and make it work. That project uses erlang.mk system too, since I added into that.
Anyway here is the OS version I use
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)> uname -a
Linux ethrbh-VirtualBox 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
ethrbh@ethrbh-VirtualBox:/mnt/ethrbh/private/cowboy/cowboy(master)>
thanks for your help,
/Robi

Any chance the repository you work in is a Virtualbox shared directory?
If not, I don't really know. I can try but no sooner than in a few days.

hello,
Yes, I am working in a shared dir, and it was not a problem till now. Anyway, I could clone and do the make in my home dir. Later on I try find why cowboy does not work in the shared dir.
I guess, you can close the ticket.
thanks for your help,
/Robi

Right so there's a few very long standing bug in Virtualbox that makes file operations sometimes fail for no good reason. Nothing I can do about it, sorry. :-)
Yours specifically is probably this one: https://www.virtualbox.org/ticket/10085
Closing then!

hello,
No problem at all. I can leave with this. The good, that I can start toe learn cowboy.
thanks for your help again,
/Robi


Vue Component does not render when used in blade file with production vite build, but works with vite dev

Hello,
I'm rendering a vue component within a blade file which works fine when running npm run dev, but when I package for production with npm run build, the vue component no longer renders when visiting the page.
Did I miss a config somewhere? Again, everything works as expected when on dev with vite running in dev mode, but the vue component does not render within the HTML on prod bundle. No console or network errors either.
Here are my files
package.json
"scripts": {
    "dev": "vite",
    "build": "vite build"
},
"devDependencies": {
    ......
    "laravel-vite-plugin": "^0.3.0",
    "@vitejs/plugin-vue": "^2.3.3",
    "vite": "^2.9.11",
    "vue": "^3.2.25"
    ......

vite.config.js
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';
import vue from '@vitejs/plugin-vue';

export default defineConfig({
    plugins: [
        laravel({
            input:[
                'resources/css/app.css',
                'resources/js/app.js',
            ],
            refresh: true,
        }),
        vue({
            template: {
                transformAssetUrls: {
                    base: null,
                    includeAbsolute: false,
                },
            },
        }),
    ],
    server: {
        hmr: {
            host: 'localhost',
        }
    }
});

app.js
import { createApp } from 'vue'
import TagsInput from './Components/TagsInput.vue'

const app = createApp({})
app.component('tags-input', TagsInput);
app.mount('#admin-app')

create.blade.php
@vite directive is placed in parent layout file like this
@vite(['resources/css/app.css', 'resources/js/app.js'])
<div id="admin-app">
    <tags-input />
</div>

Inspecting the DOM after prod build, I see that vue is attached to the correct HTML element, but nothing within it was rendered

Now comparing the DOM while running vite in dev, HTML appears as expected:

I was able to get a little bit more information from the console by running vite build --mode dev
the console then gave this warning
[Vue warn]: Component provided template option but runtime compilation is not supported in this build of Vue. Configure your bundler to alias "vue" to "vue/dist/vue.esm-bundler.js".
  at <App>

That led me to the two following pages:
https://github.com/fengyuanchen/vue-feather/issues/8
https://github.com/vuejs/vue-next-webpack-preview/issues/8
I swapped the vue import in my app.js file to this new import, which does fix my problem of the vue component not displaying on prod build.
import { createApp } from 'vue/dist/vue.esm-bundler';
``

As the warning suggests, I could alias vue to this new path, but is this a valid solution for my problem?

Thanks

Just a head's up, you are not using this package, lol. You're using the official integration.
And yes, AFAIK this is the right solution.


faster riot.mount.selctAllTags

riot.mount.selctAllTags is slow, this alternative function is 55% faster.
I think parameter 'sel' is not neccesary.
In rare cases, cache with allTags var avoids unnecessary call.
See the test in jsperf.com

Wow awesome thank you very much!

y w
(old plain for is even faster)

@GianlucaGuarini I'm sorry.
Can you revert this commit please?
forEach() does not exist in IE8, I will create new PR with plain for.

thanks


Update kantan.sbt-kantan, ... to 2.5.1

Updates

com.nrinaudo:kantan.sbt-kantan
com.nrinaudo:kantan.sbt-scalajs

from 2.5.0 to 2.5.1.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.nrinaudo" } ]

labels: semver-patch

Already done as part of another MR


Crop and rotate everywhere

Crop and rotate are things that I frequently do with images. I would greatly appreciate it if it would also be available in filter chain and other tools.

Cropping is impossible at the moment for batch  modes, so if you need to filter and crop at the same time then take a look at a single edit screen, it has all the most used features :)

Thanks you. I was not aware of this.
Too many features ;)

Thank you. I was not aware of this.
Too many features ;)

:)


@Builder seems to ignore initialization of fields (default value)

Hi,
Great tool that you are building there. Helped me a lot. There is just this tiny issue that I was running against, when using the builders together with default initialization of fields.
Thanks for your time,
Stefan
@Builder @Data
public class BuilderInitialization {
    private String aString;
    @Singular private List<String> aListOfStrings = new ArrayList<>();

    public void addString(String some) {
        aListOfStrings.add(some);
    }

    public static void main(String[] args) {
        // Say we build the instance with a builder
        BuilderInitialization myInstance = BuilderInitialization.builder().aString("some String").build();

        myInstance.addString("Some String");
        // NullPointerException: aListOfStrings is <null>
    }
}

Note that it also does not work if I put the initialization of the fields in a constructor.
Changing the code to not use the builder and use "normal" constructors work like a charm

I tried to reproduce it and I get an UnsupportedOperationException, which is actually correct as @Builder is primarily meant for immutables (and uses either Collections.unmodifiableList or Guava's ImmutableList here).
In case you're really getting a NullPointerException, this is a bug (I guess you should try the newest version before the developers look into it).

Not honoring your initializer expresssion is no bug: When you look at the generated constructor (e.g. in the "members" view), you can see
 BuilderInitialization(String, List<String>)

which only makes sense, when the initializer expresssion gets ignored. That's not nice (there could be a warning), but it's logical:

Finally, applying @Builder to a class is as if you added @AllArgsConstructor(access = AccessLevel.PACKAGE) to the class and applied the @Builder annotation to this all-args-constructor.

Add an explicit constructor or another XArgsConstructor annotation or simply make aListOfStrings final.

Hello @Maaartinus,
Thank you for your reply. I tried the sample with the newest lombok version and you are right. UnsupportedOperationException is thrown instead of NullPointerException.
Your reasoning is completely understandable. I will change this accordingly.
Sorry for not having tried this on the newest version first.
Stefan

Another one bit by this issue: http://stackoverflow.com/a/39591047/581205
A good solution is hard to find, but a warning would be really helpful. I guess, @Builder should warn whenever there's any non-static initializer expression.


Transition to using dep for dependencies

Thanks for your PR. Prometheus is currently experimenting with dep, I'd prefer that to complete before switching away from what is the current standard.

@brian-brazil what do you typically do when you're not using dep to accomplish adding a new dependency for this repo? do you just download it and copy?

Govendor is the current standard.

Should this be updated to use Go Modules instead?

Yeah, Go modules is the done thing now.


JZ instruction

Closes #15
Implementation

Add JZ in the instruction set and identify it in binread.
In the processor after every instruction is executed check if the top of the stack is 0 or not (the result of the last instruction), if it is 0 then turn on the zero flag otherwise turn it off.
To check the top value of the stack add a new method in Stack struct called top() which returns the top most value of the stack.
To execute JZ jump to the index if zero flag is set, otherwise continue sequential execution.

All integration tests and yamtests passing. Merging this.


Missing "projector_info" key and others in ollama.show() dictionary output for version 0.4.1

I'm not sure if I'm doing something wrong but does ollama version 0.4.1 have less model info listed for the .show function?
The projector_info key is missing in the version 0.4.1 dictionary compare to 0.3.3
Here is the output for ollama.show("llava") in ollama version 0.3.3
{'license': '                                 Apache License\n                           Version 2.0, January 2004\n                        http://www.apache.org/licenses/\n\n   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n   1. Definitions.\n\n      "License" shall mean the terms and conditions for use, reproduction,\n      and distribution as defined by Sections 1 through 9 of this document.\n\n      "Licensor" shall mean the copyright owner or entity authorized by\n      the copyright owner that is granting the License.\n\n      "Legal Entity" shall mean the union of the acting entity and all\n      other entities that control, are controlled by, or are under common\n      control with that entity. For the purposes of this definition,\n      "control" means (i) the power, direct or indirect, to cause the\n      direction or management of such entity, whether by contract or\n      otherwise, or (ii) ownership of fifty percent (50%) or more of the\n      outstanding shares, or (iii) beneficial ownership of such entity.\n\n      "You" (or "Your") shall mean an individual or Legal Entity\n      exercising permissions granted by this License.\n\n      "Source" form shall mean the preferred form for making modifications,\n      including but not limited to software source code, documentation\n      source, and configuration files.\n\n      "Object" form shall mean any form resulting from mechanical\n      transformation or translation of a Source form, including but\n      not limited to compiled object code, generated documentation,\n      and conversions to other media types.\n\n      "Work" shall mean the work of authorship, whether in Source or\n      Object form, made available under the License, as indicated by a\n      copyright notice that is included in or attached to the work\n      (an example is provided in the Appendix below).\n\n      "Derivative Works" shall mean any work, whether in Source or Object\n      form, that is based on (or derived from) the Work and for which the\n      editorial revisions, annotations, elaborations, or other modifications\n      represent, as a whole, an original work of authorship. For the purposes\n      of this License, Derivative Works shall not include works that remain\n      separable from, or merely link (or bind by name) to the interfaces of,\n      the Work and Derivative Works thereof.\n\n      "Contribution" shall mean any work of authorship, including\n      the original version of the Work and any modifications or additions\n      to that Work or Derivative Works thereof, that is intentionally\n      submitted to Licensor for inclusion in the Work by the copyright owner\n      or by an individual or Legal Entity authorized to submit on behalf of\n      the copyright owner. For the purposes of this definition, "submitted"\n      means any form of electronic, verbal, or written communication sent\n      to the Licensor or its representatives, including but not limited to\n      communication on electronic mailing lists, source code control systems,\n      and issue tracking systems that are managed by, or on behalf of, the\n      Licensor for the purpose of discussing and improving the Work, but\n      excluding communication that is conspicuously marked or otherwise\n      designated in writing by the copyright owner as "Not a Contribution."\n\n      "Contributor" shall mean Licensor and any individual or Legal Entity\n      on behalf of whom a Contribution has been received by Licensor and\n      subsequently incorporated within the Work.\n\n   2. Grant of Copyright License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      copyright license to reproduce, prepare Derivative Works of,\n      publicly display, publicly perform, sublicense, and distribute the\n      Work and such Derivative Works in Source or Object form.\n\n   3. Grant of Patent License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      (except as stated in this section) patent license to make, have made,\n      use, offer to sell, sell, import, and otherwise transfer the Work,\n      where such license applies only to those patent claims licensable\n      by such Contributor that are necessarily infringed by their\n      Contribution(s) alone or by combination of their Contribution(s)\n      with the Work to which such Contribution(s) was submitted. If You\n      institute patent litigation against any entity (including a\n      cross-claim or counterclaim in a lawsuit) alleging that the Work\n      or a Contribution incorporated within the Work constitutes direct\n      or contributory patent infringement, then any patent licenses\n      granted to You under this License for that Work shall terminate\n      as of the date such litigation is filed.\n\n   4. Redistribution. You may reproduce and distribute copies of the\n      Work or Derivative Works thereof in any medium, with or without\n      modifications, and in Source or Object form, provided that You\n      meet the following conditions:\n\n      (a) You must give any other recipients of the Work or\n          Derivative Works a copy of this License; and\n\n      (b) You must cause any modified files to carry prominent notices\n          stating that You changed the files; and\n\n      (c) You must retain, in the Source form of any Derivative Works\n          that You distribute, all copyright, patent, trademark, and\n          attribution notices from the Source form of the Work,\n          excluding those notices that do not pertain to any part of\n          the Derivative Works; and\n\n      (d) If the Work includes a "NOTICE" text file as part of its\n          distribution, then any Derivative Works that You distribute must\n          include a readable copy of the attribution notices contained\n          within such NOTICE file, excluding those notices that do not\n          pertain to any part of the Derivative Works, in at least one\n          of the following places: within a NOTICE text file distributed\n          as part of the Derivative Works; within the Source form or\n          documentation, if provided along with the Derivative Works; or,\n          within a display generated by the Derivative Works, if and\n          wherever such third-party notices normally appear. The contents\n          of the NOTICE file are for informational purposes only and\n          do not modify the License. You may add Your own attribution\n          notices within Derivative Works that You distribute, alongside\n          or as an addendum to the NOTICE text from the Work, provided\n          that such additional attribution notices cannot be construed\n          as modifying the License.\n\n      You may add Your own copyright statement to Your modifications and\n      may provide additional or different license terms and conditions\n      for use, reproduction, or distribution of Your modifications, or\n      for any such Derivative Works as a whole, provided Your use,\n      reproduction, and distribution of the Work otherwise complies with\n      the conditions stated in this License.\n\n   5. Submission of Contributions. Unless You explicitly state otherwise,\n      any Contribution intentionally submitted for inclusion in the Work\n      by You to the Licensor shall be under the terms and conditions of\n      this License, without any additional terms or conditions.\n      Notwithstanding the above, nothing herein shall supersede or modify\n      the terms of any separate license agreement you may have executed\n      with Licensor regarding such Contributions.\n\n   6. Trademarks. This License does not grant permission to use the trade\n      names, trademarks, service marks, or product names of the Licensor,\n      except as required for reasonable and customary use in describing the\n      origin of the Work and reproducing the content of the NOTICE file.\n\n   7. Disclaimer of Warranty. Unless required by applicable law or\n      agreed to in writing, Licensor provides the Work (and each\n      Contributor provides its Contributions) on an "AS IS" BASIS,\n      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n      implied, including, without limitation, any warranties or conditions\n      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n      PARTICULAR PURPOSE. You are solely responsible for determining the\n      appropriateness of using or redistributing the Work and assume any\n      risks associated with Your exercise of permissions under this License.\n\n   8. Limitation of Liability. In no event and under no legal theory,\n      whether in tort (including negligence), contract, or otherwise,\n      unless required by applicable law (such as deliberate and grossly\n      negligent acts) or agreed to in writing, shall any Contributor be\n      liable to You for damages, including any direct, indirect, special,\n      incidental, or consequential damages of any character arising as a\n      result of this License or out of the use or inability to use the\n      Work (including but not limited to damages for loss of goodwill,\n      work stoppage, computer failure or malfunction, or any and all\n      other commercial damages or losses), even if such Contributor\n      has been advised of the possibility of such damages.\n\n   9. Accepting Warranty or Additional Liability. While redistributing\n      the Work or Derivative Works thereof, You may choose to offer,\n      and charge a fee for, acceptance of support, warranty, indemnity,\n      or other liability obligations and/or rights consistent with this\n      License. However, in accepting such obligations, You may act only\n      on Your own behalf and on Your sole responsibility, not on behalf\n      of any other Contributor, and only if You agree to indemnify,\n      defend, and hold each Contributor harmless for any liability\n      incurred by, or claims asserted against, such Contributor by reason\n      of your accepting any such warranty or additional liability.\n\n   END OF TERMS AND CONDITIONS\n\n   APPENDIX: How to apply the Apache License to your work.\n\n      To apply the Apache License to your work, attach the following\n      boilerplate notice, with the fields enclosed by brackets "[]"\n      replaced with your own identifying information. (Don't include\n      the brackets!)  The text should be enclosed in the appropriate\n      comment syntax for the file format. We also recommend that a\n      file or class name and description of purpose be included on the\n      same "printed page" as the copyright notice for easier\n      identification within third-party archives.\n\n   Copyright [yyyy] [name of copyright owner]\n\n   Licensed under the Apache License, Version 2.0 (the "License");\n   you may not use this file except in compliance with the License.\n   You may obtain a copy of the License at\n\n       http://www.apache.org/licenses/LICENSE-2.0\n\n   Unless required by applicable law or agreed to in writing, software\n   distributed under the License is distributed on an "AS IS" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n   See the License for the specific language governing permissions and\n   limitations under the License.', 'modelfile': '# Modelfile generated by "ollama show"\n# To build a new Modelfile based on this, replace FROM with:\n# FROM llava:latest\n\nFROM C:\Users\cloud\.ollama\models\blobs\sha256-170370233dd5c5415250a2ecd5c71586352850729062ccef1496385647293868\nFROM C:\Users\cloud\.ollama\models\blobs\sha256-72d6f08a42f656d36b356dbe0920675899a99ce21192fd66266fb7d82ed07539\nTEMPLATE [INST] {{ if .System }}{{ .System }} {{ end }}{{ .Prompt }} [/INST]\nPARAMETER stop [INST]\nPARAMETER stop [/INST]\nLICENSE """                                 Apache License\n                           Version 2.0, January 2004\n
http://www.apache.org/licenses/\n\n   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n   1. Definitions.\n\n      "License" shall mean the terms and conditions for use, reproduction,\n      and distribution as defined by Sections 1 through 9 of this document.\n\n      "Licensor" shall mean the copyright owner or entity authorized by\n      the copyright owner that is granting the License.\n\n      "Legal Entity" shall mean the union of the acting entity and all\n      other entities that control, are controlled by, or are under common\n      control with that entity. For the purposes of this definition,\n      "control" means (i) the power, direct or indirect, to cause the\n      direction or management of such entity, whether by contract or\n      otherwise, or (ii) ownership of fifty percent (50%) or more of the\n      outstanding shares, or (iii) beneficial ownership of such entity.\n\n      "You" (or "Your") shall mean an individual or Legal Entity\n      exercising permissions granted by this License.\n\n      "Source" form shall mean the preferred form for making modifications,\n      including but not limited to software source code, documentation\n      source, and configuration files.\n\n      "Object" form shall mean any form resulting from mechanical\n      transformation or translation of a Source form, including but\n      not limited to compiled object code, generated documentation,\n      and conversions to other media types.\n\n      "Work" shall mean the work of authorship, whether in Source or\n      Object form, made available under the License, as indicated by a\n      copyright notice that is included in or attached to the work\n      (an example is provided in the Appendix below).\n\n      "Derivative Works" shall mean any work, whether in Source or Object\n      form, that is based on (or derived from) the Work and for which the\n      editorial revisions, annotations, elaborations, or other modifications\n      represent, as a whole, an original work of authorship. For the purposes\n      of this License, Derivative Works shall not include works that remain\n      separable from, or merely link (or bind by name) to the interfaces of,\n      the Work and Derivative Works thereof.\n\n      "Contribution" shall mean any work of authorship, including\n      the original version of the Work and any modifications or additions\n      to that Work or Derivative Works thereof, that is intentionally\n      submitted to Licensor for inclusion in the Work by the copyright owner\n      or by an individual or Legal Entity authorized to submit on behalf of\n      the copyright owner. For the purposes of this definition, "submitted"\n      means any form of electronic, verbal, or written communication sent\n      to the Licensor or its representatives, including but not limited to\n      communication on electronic mailing lists, source code control systems,\n      and issue tracking systems that are managed by, or on behalf of, the\n      Licensor for the purpose of discussing and improving the Work, but\n      excluding communication that is conspicuously marked or otherwise\n      designated in writing by the copyright owner as "Not a Contribution."\n\n      "Contributor" shall mean Licensor and any individual or Legal Entity\n      on behalf of whom a Contribution has been received by Licensor and\n      subsequently incorporated within the Work.\n\n   2. Grant of Copyright License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      copyright license to reproduce, prepare Derivative Works of,\n      publicly display, publicly perform, sublicense, and distribute the\n      Work and such Derivative Works in Source or Object form.\n\n   3. Grant of Patent License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      (except as stated in this section) patent license to make, have made,\n      use, offer to sell, sell, import, and otherwise transfer the Work,\n      where such license applies only to those patent claims licensable\n      by such Contributor that are necessarily infringed by their\n      Contribution(s) alone or by combination of their Contribution(s)\n      with the Work to which such Contribution(s) was submitted. If You\n      institute patent litigation against any entity (including a\n      cross-claim or counterclaim in a lawsuit) alleging that the Work\n      or a Contribution incorporated within the Work constitutes direct\n      or contributory patent infringement, then any patent licenses\n      granted to You under this License for that Work shall terminate\n      as of the date such litigation is filed.\n\n   4. Redistribution. You may reproduce and distribute copies of the\n      Work or Derivative Works thereof in any medium, with or without\n      modifications, and in Source or Object form, provided that You\n      meet the following conditions:\n\n      (a) You must give any other recipients of the Work or\n          Derivative Works a copy of this License; and\n\n      (b) You must cause any modified files to carry prominent notices\n          stating that You changed the files; and\n\n      (c) You must retain, in the Source form of any Derivative Works\n          that You distribute, all copyright, patent, trademark, and\n          attribution notices from the Source form of the Work,\n          excluding those notices that do not pertain to any part of\n          the Derivative Works; and\n\n      (d) If the Work includes a "NOTICE" text file as part of its\n          distribution, then any Derivative Works that You distribute must\n          include a readable copy of the attribution notices contained\n          within such NOTICE file, excluding those notices that do not\n          pertain to any part of the Derivative Works, in at least one\n          of the following places: within a NOTICE text file distributed\n          as part of the Derivative Works; within the Source form or\n          documentation, if provided along with the Derivative Works; or,\n          within a display generated by the Derivative Works, if and\n          wherever such third-party notices normally appear. The contents\n          of the NOTICE file are for informational purposes only and\n          do not modify the License. You may add Your own attribution\n          notices within Derivative Works that You distribute, alongside\n          or as an addendum to the NOTICE text from the Work, provided\n          that such additional attribution notices cannot be construed\n          as modifying the License.\n\n      You may add Your own copyright statement to Your modifications and\n      may provide additional or different license terms and conditions\n      for use, reproduction, or distribution of Your modifications, or\n      for any such Derivative Works as a whole, provided Your use,\n      reproduction, and distribution of the Work otherwise complies with\n      the conditions stated in this License.\n\n   5. Submission of Contributions. Unless You explicitly state otherwise,\n      any Contribution intentionally submitted for inclusion in the Work\n      by You to the Licensor shall be under the terms and conditions of\n      this License, without any additional terms or conditions.\n      Notwithstanding the above, nothing herein shall supersede or modify\n      the terms of any separate license agreement you may have executed\n      with Licensor regarding such Contributions.\n\n   6. Trademarks. This License does not grant permission to use the trade\n      names, trademarks, service marks, or product names of the Licensor,\n      except as required for reasonable and customary use in describing the\n      origin of the Work and reproducing the content of the NOTICE file.\n\n   7. Disclaimer of Warranty. Unless required by applicable law or\n      agreed to in writing, Licensor provides the Work (and each\n      Contributor provides its Contributions) on an "AS IS" BASIS,\n      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n      implied, including, without limitation, any warranties or conditions\n      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n      PARTICULAR PURPOSE. You are solely responsible for determining the\n      appropriateness of using or redistributing the Work and assume any\n      risks associated with Your exercise of permissions under this License.\n\n   8. Limitation of Liability. In no event and under no legal theory,\n      whether in tort (including negligence), contract, or otherwise,\n      unless required by applicable law (such as deliberate and grossly\n      negligent acts) or agreed to in writing, shall any Contributor be\n      liable to You for damages, including any direct, indirect, special,\n      incidental, or consequential damages of any character arising as a\n      result of this License or out of the use or inability to use the\n      Work (including but not limited to damages for loss of goodwill,\n      work stoppage, computer failure or malfunction, or any and all\n      other commercial damages or losses), even if such Contributor\n      has been advised of the possibility of such damages.\n\n   9. Accepting Warranty or Additional Liability. While redistributing\n      the Work or Derivative Works thereof, You may choose to offer,\n      and charge a fee for, acceptance of support, warranty, indemnity,\n      or other liability obligations and/or rights consistent with this\n      License. However, in accepting such obligations, You may act only\n      on Your own behalf and on Your sole responsibility, not on behalf\n      of any other Contributor, and only if You agree to indemnify,\n      defend, and hold each Contributor harmless for any liability\n      incurred by, or claims asserted against, such Contributor by reason\n      of your accepting any such warranty or additional liability.\n\n   END OF TERMS AND CONDITIONS\n\n   APPENDIX: How to apply the Apache License to your work.\n\n      To apply the Apache License to your work, attach the following\n      boilerplate notice, with the fields enclosed by brackets "[]"\n      replaced with your own identifying information. (Don't include\n      the brackets!)  The text should be enclosed in the appropriate\n      comment syntax for the file format. We also recommend that a\n      file or class name and description of purpose be included on the\n      same "printed page" as the copyright notice for easier\n      identification within third-party archives.\n\n   Copyright [yyyy] [name of copyright owner]\n\n   Licensed under the Apache License, Version 2.0 (the "License");\n   you may not use this file except in compliance with the License.\n   You may obtain a copy of the License at\n\n       http://www.apache.org/licenses/LICENSE-2.0\n\n   Unless required by applicable law or agreed to in writing, software\n   distributed under the License is distributed on an "AS IS" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n   See the License for the specific language governing permissions and\n   limitations under the License."""\n', 'parameters': 'stop                           "[INST]"\nstop
"[/INST]"', 'template': '[INST] {{ if .System }}{{ .System }} {{ end }}{{ .Prompt }} [/INST]', 'details': {'parent_model': '', 'format': 'gguf', 'family': 'llama', 'families': ['llama', 'clip'], 'parameter_size': '7B', 'quantization_level': 'Q4_0'}, 'model_info': {'general.architecture': 'llama', 'general.file_type': 2, 'general.parameter_count':<PHONE_NUMBER>, 'general.quantization_version': 2, 'llama.attention.head_count': 32, 'llama.attention.head_count_kv': 8, 'llama.attention.layer_norm_rms_epsilon': 1e-05, 'llama.block_count': 32, 'llama.context_length': 32768, 'llama.embedding_length': 4096, 'llama.feed_forward_length': 14336, 'llama.rope.dimension_count': 128, 'llama.rope.freq_base': 1000000, 'tokenizer.ggml.add_bos_token': True, 'tokenizer.ggml.add_eos_token': False, 'tokenizer.ggml.bos_token_id': 1, 'tokenizer.ggml.eos_token_id': 2, 'tokenizer.ggml.model': 'llama', 'tokenizer.ggml.padding_token_id': 0, 'tokenizer.ggml.scores': None, 'tokenizer.ggml.token_type': None, 'tokenizer.ggml.tokens': None, 'tokenizer.ggml.unknown_token_id': 0}, 'projector_info': {'clip.has_llava_projector': True, 'clip.has_text_encoder': False, 'clip.has_vision_encoder': True, 'clip.projector_type': 'mlp', 'clip.use_gelu': False, 'clip.vision.attention.head_count': 16, 'clip.vision.attention.layer_norm_epsilon': 1e-05, 'clip.vision.block_count': 23, 'clip.vision.embedding_length': 1024, 'clip.vision.feed_forward_length': 4096, 'clip.vision.image_mean': [0.48145467, 0.4578275, 0.40821072], 'clip.vision.image_size': 336, 'clip.vision.image_std': [0.26862955, 0.2613026, 0.2757771], 'clip.vision.patch_size': 14, 'clip.vision.projection_dim': 768, 'general.architecture': 'clip', 'general.description': 'image encoder for LLaVA', 'general.file_type': 1, 'general.name': 'openai/clip-vit-large-patch14-336', 'general.parameter_count': 311888896}, 'modified_at': '2024-11-27T20:22:19.0725553-05:00'}
Now here  is the output for ollama.show("llava") in ollama version 0.4.1
modified_at=datetime.datetime(2024, 11, 27, 20, 22, 19, 72555, tzinfo=TzInfo(-05:00)) template='[INST] {{ if .System }}{{ .System }} {{ end }}{{ .Prompt }} [/INST]' modelfile='# Modelfile generated by "ollama show"\n# To build a new Modelfile based on this, replace FROM with:\n# FROM llava:latest\n\nFROM C:\Users\cloud\.ollama\models\blobs\sha256-170370233dd5c5415250a2ecd5c71586352850729062ccef1496385647293868\nFROM C:\Users\cloud\.ollama\models\blobs\sha256-72d6f08a42f656d36b356dbe0920675899a99ce21192fd66266fb7d82ed07539\nTEMPLATE [INST] {{ if .System }}{{ .System }} {{ end }}{{ .Prompt }} [/INST]\nPARAMETER stop [INST]\nPARAMETER stop [/INST]\nLICENSE """                                 Apache License\n                           Version 2.0, January 2004\n                        http://www.apache.org/licenses/\n\n   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n   1. Definitions.\n\n      "License" shall mean the terms and conditions for use, reproduction,\n      and distribution as defined by Sections 1 through 9 of this document.\n\n      "Licensor" shall mean the copyright owner or entity authorized by\n      the copyright owner that is granting the License.\n\n      "Legal Entity" shall mean the union of the acting entity and all\n      other entities that control, are controlled by, or are under common\n      control with that entity. For the purposes of this definition,\n      "control" means (i) the power, direct or indirect, to cause the\n      direction or management of such entity, whether by contract or\n      otherwise, or (ii) ownership of fifty percent (50%) or more of the\n      outstanding shares, or (iii) beneficial ownership of such entity.\n\n      "You" (or "Your") shall mean an individual or Legal Entity\n      exercising permissions granted by this License.\n\n      "Source" form shall mean the preferred form for making modifications,\n      including but not limited to software source code, documentation\n      source, and configuration files.\n\n      "Object" form shall mean any form resulting from mechanical\n      transformation or translation of a Source form, including but\n      not limited to compiled object code, generated documentation,\n      and conversions to other media types.\n\n      "Work" shall mean the work of authorship, whether in Source or\n      Object form, made available under the License, as indicated by a\n      copyright notice that is included in or attached to the work\n      (an example is provided in the Appendix below).\n\n      "Derivative Works" shall mean any work, whether in Source or Object\n      form, that is based on (or derived from) the Work and for which the\n      editorial revisions, annotations, elaborations, or other modifications\n      represent, as a whole, an original work of authorship. For the purposes\n      of this License, Derivative Works shall not include works that remain\n      separable from, or merely link (or bind by name) to the interfaces of,\n      the Work and Derivative Works thereof.\n\n      "Contribution" shall mean any work of authorship, including\n      the original version of the Work and any modifications or additions\n      to that Work or Derivative Works thereof, that is intentionally\n      submitted to Licensor for inclusion in the Work by the copyright owner\n      or by an individual or Legal Entity authorized to submit on behalf of\n      the copyright owner. For the purposes of this definition, "submitted"\n      means any form of electronic, verbal, or written communication sent\n      to the Licensor or its representatives, including but not limited to\n      communication on electronic mailing lists, source code control systems,\n      and issue tracking systems that are managed by, or on behalf of, the\n      Licensor for the purpose of discussing and improving the Work, but\n      excluding communication that is conspicuously marked or otherwise\n      designated in writing by the copyright owner as "Not a Contribution."\n\n      "Contributor" shall mean Licensor and any individual or Legal Entity\n      on behalf of whom a Contribution has been received by Licensor and\n      subsequently incorporated within the Work.\n\n   2. Grant of Copyright License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      copyright license to reproduce, prepare Derivative Works of,\n      publicly display, publicly perform, sublicense, and distribute the\n      Work and such Derivative Works in Source or Object form.\n\n   3. Grant of Patent License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      (except as stated in this section) patent license to make, have made,\n      use, offer to sell, sell, import, and otherwise transfer the Work,\n      where such license applies only to those patent claims licensable\n      by such Contributor that are necessarily infringed by their\n      Contribution(s) alone or by combination of their Contribution(s)\n      with the Work to which such Contribution(s) was submitted. If You\n      institute patent litigation against any entity (including a\n      cross-claim or counterclaim in a lawsuit) alleging that the Work\n      or a Contribution incorporated within the Work constitutes direct\n      or contributory patent infringement, then any patent licenses\n      granted to You under this License for that Work shall terminate\n      as of the date such litigation is filed.\n\n   4. Redistribution. You may reproduce and distribute copies of the\n      Work or Derivative Works thereof in any medium, with or without\n      modifications, and in Source or Object form, provided that You\n      meet the following conditions:\n\n      (a) You must give any other recipients of the Work or\n          Derivative Works a copy of this License; and\n\n      (b) You must cause any modified files to carry prominent notices\n          stating that You changed the files; and\n\n      (c) You must retain, in the Source form of any Derivative Works\n          that You distribute, all copyright, patent, trademark, and\n          attribution notices from the Source form of the Work,\n          excluding those notices that do not pertain to any part of\n          the Derivative Works; and\n\n      (d) If the Work includes a "NOTICE" text file as part of its\n          distribution, then any Derivative Works that You distribute must\n          include a readable copy of the attribution notices contained\n          within such NOTICE file, excluding those notices that do not\n          pertain to any part of the Derivative Works, in at least one\n          of the following places: within a NOTICE text file distributed\n          as part of the Derivative Works; within the Source form or\n          documentation, if provided along with the Derivative Works; or,\n          within a display generated by the Derivative Works, if and\n          wherever such third-party notices normally appear. The contents\n          of the NOTICE file are for informational purposes only and\n          do not modify the License. You may add Your own attribution\n          notices within Derivative Works that You distribute, alongside\n          or as an addendum to the NOTICE text from the Work, provided\n          that such additional attribution notices cannot be construed\n          as modifying the License.\n\n      You may add Your own copyright statement to Your modifications and\n      may provide additional or different license terms and conditions\n      for use, reproduction, or distribution of Your modifications, or\n      for any such Derivative Works as a whole, provided Your use,\n      reproduction, and distribution of the Work otherwise complies with\n      the conditions stated in this License.\n\n   5. Submission of Contributions. Unless You explicitly state otherwise,\n      any Contribution intentionally submitted for inclusion in the Work\n      by You to the Licensor shall be under the terms and conditions of\n      this License, without any additional terms or conditions.\n      Notwithstanding the above, nothing herein shall supersede or modify\n      the terms of any separate license agreement you may have executed\n      with Licensor regarding such Contributions.\n\n   6. Trademarks. This License does not grant permission to use the trade\n      names, trademarks, service marks, or product names of the Licensor,\n      except as required for reasonable and customary use in describing the\n      origin of the Work and reproducing the content of the NOTICE file.\n\n   7. Disclaimer of Warranty. Unless required by applicable law or\n      agreed to in writing, Licensor provides the Work (and each\n      Contributor provides its Contributions) on an "AS IS" BASIS,\n      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n      implied, including, without limitation, any warranties or conditions\n      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n      PARTICULAR PURPOSE. You are solely responsible for determining the\n      appropriateness of using or redistributing the Work and assume any\n      risks associated with Your exercise of permissions under this License.\n\n   8. Limitation of Liability. In no event and under no legal theory,\n      whether in tort (including negligence), contract, or otherwise,\n      unless required by applicable law (such as deliberate and grossly\n      negligent acts) or agreed to in writing, shall any Contributor be\n      liable to You for damages, including any direct, indirect, special,\n      incidental, or consequential damages of any character arising as a\n      result of this License or out of the use or inability to use the\n      Work (including but not limited to damages for loss of goodwill,\n      work stoppage, computer failure or malfunction, or any and all\n      other commercial damages or losses), even if such Contributor\n      has been advised of the possibility of such damages.\n\n   9. Accepting Warranty or Additional Liability. While redistributing\n      the Work or Derivative Works thereof, You may choose to offer,\n      and charge a fee for, acceptance of support, warranty, indemnity,\n      or other liability obligations and/or rights consistent with this\n      License. However, in accepting such obligations, You may act only\n      on Your own behalf and on Your sole responsibility, not on behalf\n      of any other Contributor, and only if You agree to indemnify,\n      defend, and hold each Contributor harmless for any liability\n      incurred by, or claims asserted against, such Contributor by reason\n      of your accepting any such warranty or additional liability.\n\n   END OF TERMS AND CONDITIONS\n\n   APPENDIX: How to apply the Apache License to your work.\n\n      To apply the Apache License to your work, attach the following\n      boilerplate notice, with the fields enclosed by brackets "[]"\n      replaced with your own identifying information. (Don't include\n      the brackets!)  The text should be enclosed in the appropriate\n      comment syntax for the file format. We also recommend that a\n      file or class name and description of purpose be included on the\n      same "printed page" as the copyright notice for easier\n      identification within third-party archives.\n\n   Copyright [yyyy] [name of copyright owner]\n\n   Licensed under the Apache License, Version 2.0 (the "License");\n   you may not use this file except in compliance with the License.\n   You may obtain a copy of the License at\n\n       http://www.apache.org/licenses/LICENSE-2.0\n\n   Unless required by applicable law or agreed to in writing, software\n   distributed under the License is distributed on an "AS IS" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n   See the License for the specific language governing permissions and\n   limitations under the License."""\n' license='                                 Apache License\n                           Version 2.0, January 2004\n                        http://www.apache.org/licenses/\n\n   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n   1. Definitions.\n\n      "License" shall mean the terms and conditions for use, reproduction,\n      and distribution as defined by Sections 1 through 9 of this document.\n\n      "Licensor" shall mean the copyright owner or entity authorized by\n      the copyright owner that is granting the License.\n\n      "Legal Entity" shall mean the union of the acting entity and all\n      other entities that control, are controlled by, or are under common\n      control with that entity. For the purposes of this definition,\n      "control" means (i) the power, direct or indirect, to cause the\n      direction or management of such entity, whether by contract or\n      otherwise, or (ii) ownership of fifty percent (50%) or more of the\n      outstanding shares, or (iii) beneficial ownership of such entity.\n\n      "You" (or "Your") shall mean an individual or Legal Entity\n      exercising permissions granted by this License.\n\n      "Source" form shall mean the preferred form for making modifications,\n      including but not limited to software source code, documentation\n      source, and configuration files.\n\n      "Object" form shall mean any form resulting from mechanical\n      transformation or translation of a Source form, including but\n      not limited to compiled object code, generated documentation,\n      and conversions to other media types.\n\n      "Work" shall mean the work of authorship, whether in Source or\n      Object form, made available under the License, as indicated by a\n      copyright notice that is included in or attached to the work\n      (an example is provided in the Appendix below).\n\n      "Derivative Works" shall mean any work, whether in Source or Object\n      form, that is based on (or derived from) the Work and for which the\n      editorial revisions, annotations, elaborations, or other modifications\n      represent, as a whole, an original work of authorship. For the purposes\n      of this License, Derivative Works shall not include works that remain\n      separable from, or merely link (or bind by name) to the interfaces of,\n      the Work and Derivative Works thereof.\n\n      "Contribution" shall mean any work of authorship, including\n      the original version of the Work and any modifications or additions\n      to that Work or Derivative Works thereof, that is intentionally\n      submitted to Licensor for inclusion in the Work by the copyright owner\n      or by an individual or Legal Entity authorized to submit on behalf of\n      the copyright owner. For the purposes of this definition, "submitted"\n      means any form of electronic, verbal, or written communication sent\n      to the Licensor or its representatives, including but not limited to\n      communication on electronic mailing lists, source code control systems,\n      and issue tracking systems that are managed by, or on behalf of, the\n      Licensor for the purpose of discussing and improving the Work, but\n      excluding communication that is conspicuously marked or otherwise\n      designated in writing by the copyright owner as "Not a Contribution."\n\n      "Contributor" shall mean Licensor and any individual or Legal Entity\n      on behalf of whom a Contribution has been received by Licensor and\n      subsequently incorporated within the Work.\n\n   2. Grant of Copyright License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      copyright license to reproduce, prepare Derivative Works of,\n      publicly display, publicly perform, sublicense, and distribute the\n      Work and such Derivative Works in Source or Object form.\n\n   3. Grant of Patent License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      (except as stated in this section) patent license to make, have made,\n      use, offer to sell, sell, import, and otherwise transfer the Work,\n      where such license applies only to those patent claims licensable\n      by such Contributor that are necessarily infringed by their\n      Contribution(s) alone or by combination of their Contribution(s)\n      with the Work to which such Contribution(s) was submitted. If You\n      institute patent litigation against any entity (including a\n      cross-claim or counterclaim in a lawsuit) alleging that the Work\n      or a Contribution incorporated within the Work constitutes direct\n      or contributory patent infringement, then any patent licenses\n      granted to You under this License for that Work shall terminate\n      as of the date such litigation is filed.\n\n   4. Redistribution. You may reproduce and distribute copies of the\n      Work or Derivative Works thereof in any medium, with or without\n      modifications, and in Source or Object form, provided that You\n      meet the following conditions:\n\n      (a) You must give any other recipients of the Work or\n          Derivative Works a copy of this License; and\n\n      (b) You must cause any modified files to carry prominent notices\n          stating that You changed the files; and\n\n      (c) You must retain, in the Source form of any Derivative Works\n          that You distribute, all copyright, patent, trademark, and\n          attribution notices from the Source form of the Work,\n          excluding those notices that do not pertain to any part of\n          the Derivative Works; and\n\n      (d) If the Work includes a "NOTICE" text file as part of its\n          distribution, then any Derivative Works that You distribute must\n          include a readable copy of the attribution notices contained\n          within such NOTICE file, excluding those notices that do not\n          pertain to any part of the Derivative Works, in at least one\n          of the following places: within a NOTICE text file distributed\n          as part of the Derivative Works; within the Source form or\n          documentation, if provided along with the Derivative Works; or,\n          within a display generated by the Derivative Works, if and\n          wherever such third-party notices normally appear. The contents\n          of the NOTICE file are for informational purposes only and\n          do not modify the License. You may add Your own attribution\n          notices within Derivative Works that You distribute, alongside\n          or as an addendum to the NOTICE text from the Work, provided\n          that such additional attribution notices cannot be construed\n          as modifying the License.\n\n      You may add Your own copyright statement to Your modifications and\n      may provide additional or different license terms and conditions\n      for use, reproduction, or distribution of Your modifications, or\n      for any such Derivative Works as a whole, provided Your use,\n      reproduction, and distribution of the Work otherwise complies with\n      the conditions stated in this License.\n\n   5. Submission of Contributions. Unless You explicitly state otherwise,\n      any Contribution intentionally submitted for inclusion in the Work\n      by You to the Licensor shall be under the terms and conditions of\n      this License, without any additional terms or conditions.\n      Notwithstanding the above, nothing herein shall supersede or modify\n      the terms of any separate license agreement you may have executed\n      with Licensor regarding such Contributions.\n\n   6. Trademarks. This License does not grant permission to use the trade\n      names, trademarks, service marks, or product names of the Licensor,\n      except as required for reasonable and customary use in describing the\n      origin of the Work and reproducing the content of the NOTICE file.\n\n   7. Disclaimer of Warranty. Unless required by applicable law or\n      agreed to in writing, Licensor provides the Work (and each\n      Contributor provides its Contributions) on an "AS IS" BASIS,\n      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n      implied, including, without limitation, any warranties or conditions\n      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n      PARTICULAR PURPOSE. You are solely responsible for determining the\n      appropriateness of using or redistributing the Work and assume any\n      risks associated with Your exercise of permissions under this License.\n\n   8. Limitation of Liability. In no event and under no legal theory,\n      whether in tort (including negligence), contract, or otherwise,\n      unless required by applicable law (such as deliberate and grossly\n      negligent acts) or agreed to in writing, shall any Contributor be\n      liable to You for damages, including any direct, indirect, special,\n      incidental, or consequential damages of any character arising as a\n      result of this License or out of the use or inability to use the\n      Work (including but not limited to damages for loss of goodwill,\n      work stoppage, computer failure or malfunction, or any and all\n      other commercial damages or losses), even if such Contributor\n      has been advised of the possibility of such damages.\n\n   9. Accepting Warranty or Additional Liability. While redistributing\n      the Work or Derivative Works thereof, You may choose to offer,\n      and charge a fee for, acceptance of support, warranty, indemnity,\n      or other liability obligations and/or rights consistent with this\n      License. However, in accepting such obligations, You may act only\n      on Your own behalf and on Your sole responsibility, not on behalf\n      of any other Contributor, and only if You agree to indemnify,\n      defend, and hold each Contributor harmless for any liability\n      incurred by, or claims asserted against, such Contributor by reason\n      of your accepting any such warranty or additional liability.\n\n   END OF TERMS AND CONDITIONS\n\n   APPENDIX: How to apply the Apache License to your work.\n\n      To apply the Apache License to your work, attach the following\n      boilerplate notice, with the fields enclosed by brackets "[]"\n      replaced with your own identifying information. (Don't include\n      the brackets!)  The text should be enclosed in the appropriate\n      comment syntax for the file format. We also recommend that a\n      file or class name and description of purpose be included on the\n      same "printed page" as the copyright notice for easier\n      identification within third-party archives.\n\n   Copyright [yyyy] [name of copyright owner]\n\n   Licensed under the Apache License, Version 2.0 (the "License");\n   you may not use this file except in compliance with the License.\n   You may obtain a copy of the License at\n\n       http://www.apache.org/licenses/LICENSE-2.0\n\n   Unless required by applicable law or agreed to in writing, software\n   distributed under the License is distributed on an "AS IS" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n   See the License for the specific language governing permissions and\n   limitations under the License.' details=ModelDetails(parent_model='', format='gguf', family='llama', families=['llama', 'clip'], parameter_size='7B', quantization_level='Q4_0') modelinfo={'general.architecture': 'llama', 'general.file_type': 2, 'general.parameter_count':<PHONE_NUMBER>, 'general.quantization_version': 2, 'llama.attention.head_count': 32, 'llama.attention.head_count_kv': 8, 'llama.attention.layer_norm_rms_epsilon': 1e-05, 'llama.block_count': 32, 'llama.context_length': 32768, 'llama.embedding_length': 4096, 'llama.feed_forward_length': 14336, 'llama.rope.dimension_count': 128, 'llama.rope.freq_base': 1000000, 'tokenizer.ggml.add_bos_token': True, 'tokenizer.ggml.add_eos_token': False, 'tokenizer.ggml.bos_token_id': 1, 'tokenizer.ggml.eos_token_id': 2, 'tokenizer.ggml.model': 'llama', 'tokenizer.ggml.padding_token_id': 0, 'tokenizer.ggml.scores': None, 'tokenizer.ggml.token_type': None, 'tokenizer.ggml.tokens': None, 'tokenizer.ggml.unknown_token_id': 0} parameters='stop                           "[INST]"\nstop
"[/INST]"'

Hey! Appreciate you raising this. Could you please provide a slightly more formatted version? Can't fully check the diff with so much of the license information. Would recommend using Rich to print and paste the (non-license) output here. Happy to look into it with that!

Thanks @cp3249 - I'll check this out and look into it!


XR Plugin, HDRP +2019.4 - Screen position out of view frustum

I keep getting this message with the XR plugin.
This happens in editor and build.
Screen position out of view frustum (screen pos 840.000000, 0.000000, 1000.000000) (Camera rect 0 0 840 560)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

I get this error too, though it doesn't stop anything working. I'm not sure why, as it happens regardless of where my headset is within the virtual room space.

Thanks for the report. Closing as we're tracking this issue here: https://github.com/ValveSoftware/unity-xr-plugin/issues/6


Way to run it directly in "Bash on Ubuntu on Windows"

Hello,
let me first thank you for this amazing emulator.
Question: Is there a way to run it directly from "Bash on Ubuntu on Windows" with theme (colors, fonts, etc.)?
This is how it looks when opened through open-wsl.exe (on the right) vs the default bash on the left.
PS: using the agnoster theme for oh-my-zsh
(Great tutorial on how to change the theme)

If I change the .bashrc to open zsh on startup it has broken colors like:

First off "Bash on Ubuntu on Windows" is the deprecated version of WSL.  You should uninstall that and use the newer supported version on the Microsoft Store.   After that you should use chsh within wsl to set your login shell as /bin/zsh then run the 6-set-default-shell in the tools folder inside the wsl-terminal download.  The official Ubuntu start menu entry will then open zsh in the windows console and open-wsl.exe will open zsh in mintty.  the file tools/4-create-start-menu-shortcuts.js will add a start menu entry for you to open wsl in this mintty which replicates the functionality of the ubuntu shortcut but with a better terminal.

Thanks for the reply, do you happen to know if it is possible to run this shell in VS Code as default shell? If I add the path to open-wsl.exe to VS Code then  it opens new window instead...

You can change the colors here:


Data formatting issues

Hi, first of all, great work and thank you for providing the full implementation of your project! My question is regarding the data organization. I've seen your answer on how to prepare the text file for RGB and optical flow images from issue #22,
"It is quite simple, it must have the following form:
Faces/file_name0.jpg 0
Faces/file_name1.jpg 1
Faces/file_name2.jpg 1
Faces/file_name3.jpg 0
...

And a different folder with the pre-calculated Optical Flow
Faces_Flow/file_name0.jpg 0
Faces_Flow/file_name1.jpg 1
Faces_Flow/file_name2.jpg 1
Faces_Flow/file_name3.jpg 0
...

Please take a look at data_loader script and change variables accordingly."
I only have a few uncertainties:
a) Although I have all the image and optical flow names in two separate text files, will I need to place all of the BP4D images in one directory as well, or should I keep them as they are in their respective subject folders and just make sure that my root path is correctly defined?
b) What do the numbers after the file names represent?
c) I was able to retrieve the three-fold information that you use. To do training on the same three folds, will I need to make three separate text files for each fold, or sort the images in different directories for each time?
Thank you very much for your help, any help would be appreciated!

I have figured out the formatting using the BP4D AU labels and your previous answers!


Update bobwarfare.cfg

Fix some translations.
Add new translations(!)
Reorder lines to fit original modules.
Change some translations to fit other modules in pack.
RU

building one cumulitive merge.


Fix bug preventing file selection on iPhone 6 iOS 12.5

Using the legacy build of PdfJS allows for the Select File button to open the file dialog on iPhone 6 12.5.4. It also fixes the Ontario Ministry of Health button and an error that appears due to PdfJS import when opening the app in dev mode.
Fix selected files not being used when selected on iOS devices. Safari on these devices currently does not support "input" event on selected file change. "change" event should be used to support these devices. https://stackoverflow.com/a/58342757 https://caniuse.com/input-event

I do not have an Apple Developer account currently, so I cannot test Apple Wallet pkpass generation and backend verification. However, I can verify that the Save Photo feature continues to print the receipt as expected on both my iPhone (iPhone 6 12.5.4) and my Mac (Safari 14.1.1 (156<IP_ADDRESS>.6, 15611), Firefox 92.0.1 (64-bit), and Chrome 94.0.4606.61 (Official Build) (x86_64)).
edit: Did another test and noticed that on my iPhone 6, the photo is generated but does not save. I believe this is due to file-saver module - it should open a new window with the image upon call to saveAs, not sure how to solve this yet.

@Coteh thank you very much for doing this! Definitely please let us know if you find a fix for the file-saver module issue - we probably need to make sure the whole flow works before we can merge iPhone 6 support, however I know we've gotten numerous requests for it so that will be very appreciated if we can get it working!

@straxus I was able to narrow it down to html-to-image library erroring out when parsing   characters. I replaced it with a margin-left and the image was then able to generate fine using file-saver.
Also, I noticed that if image/png is in the accept attribute for file input, then my iPhone 6 won't let me select a PDF. I changed it to .png instead after reading this SO post and it seemed to fix the problem. I also checked the iPhone 11 simulator I was using, which did not experience this, and it still accepts both PDFs and PNGs even after this change.

@Coteh excellent, thank you very much for your work on this and for your help in improving our older iOS version support!


Large code process

Bot needs to read length of code to large-sized post

rephrase it please 😎

rephrase it please 😎

For preventing user to post bulk lines of code on the chat section and prompt them to use bin sites.

For preventing user to post bulk lines of code on the chat section and prompt them to use bin sites.

yeah i wrote that code. may be you can see in some commit. But IDK why i have replaced it with !code command 😕

yeah i wrote that code. may be you can see in some commit. But IDK why i have replaced it with !code command 😕


How to load reward ad without displaying it?

I need to load the reward ad without displaying it in order to show it to the user later so that he does not wait when it is needed to be shown. How can I do that?

Yes how to do so?

load video ads functionality is added in unity_ads_plugin: ^0.3.0
UnityAds.load(
  placementId: 'PLACEMENT_ID',
  onComplete: (placementId) => print('Load Complete $placementId'),
  onFailed: (placementId, error, message) => print('Load Failed $placementId: $error $message'),
);


Account have sufficient balance, but can't buy ram or delegatebw cpu

Currently, many accounts created by 3rd party have no ram and cpu resource. So "buy ram" action will fail due to lack cpu bandwidth, also "delegatebw cpu" action will fail due to lack ram resource even though the account has sufficient balance. Then, these accounts can't do anything due to lack ram or cpu resource.
So, I propose to add a subcommand for cleos to pack  "buy ram" action and "delegatebw cpu" action in one transaction to fix above issue. However, in this case, system only allows 3000us  cpu bandwidth(leeway) to execute one transaction ,  while the two actions usually  cost 4000+ us. So system will throw below exception .
"Error 3081001: transaction reached the deadline set due to leeway on account CPU limits"
Therefore, EOS should make default leeway value large enough(may 6000us)  to execute "buy ram" action and "delegatebw cpu" action in one transaction.

Hi @itleaks , try to let another account buyram for testtest1233

@noprom Thanks, your suggestion is one solution to solve this problem. But it's not easy to find another account currently. And I think eos should provide this basic ability.

Yeah this is a big issue.   These accounts are effectively stuck and can't do anything.  Really poor design choice to not let accounts delegate bandwidth to themselves, because there is not enough bandwidth available to perform the actions.

I think it's better to enhance cleos to support "delegatebw" with "buyram" in one transaction.

Please follow the pull request https://github.com/EOSIO/eos/pull/4635

What if the account doesn't have enough cpu and net for now? how to save itself?

The workable solution is to execute "delegatebw" and "buyram" inside a single transaction, this is implemented in #4635 as enhancement. For now you need to ask somebody to stake net/cpu for you.

This should be fin even if you don't have stakes for cpu/net, as final validation will use the new cpu/net stake values.

Got it, thanks for reply.

This is fixed. If you still have the problem and wish to discuss further, please post it in https://eosio.stackexchange.com.


Consider parameterizing Constant over the type of its underlying value

Would that interact well with the rest of the library? Would that be useful? This brings out the more general question of how to deal with parameterized type classes, which is a can of worms. See this for some more comments on parameterized type classes.

The Constant concept is now parameterized, both in the documentation and in practice, via the C::value_type alias. This is not a super elegant solution IMO, but it does the job. Closing this.


Update real_labels.py

this probably is a bug when you calculate the accuracy for each topK
I hope I can enchance this project with you  in  future!


rename package

I think it would also be a good idea to add a change to README.md in here to correct the  and  in the config part of the installation instructions, see - https://github.com/evolvedbinary/PLMultiAnalyzer#add-the-analyzer-dependency-in-exist-start-up-script


Raise BlueprintLists iOS target to 10.0

LG, but also should we do Listable while we're at it?

should we do Listable while we're at it?

Left that for another pass, there are some available checks to look at.


fdt: Add initial FDT support and procfs for userspace export

Summary
This provides the initial hooks for Flattened Device Tree support with QEMU RV. It also provides a new procfs file that exposes the fdt to userspace much like the /sys/firmware/fdt endpoint in Linux. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-ofw
Nodes in the fdt are not yet usable by the OS.
This change is not about adding device tree support as the way to define hardware in NuttX.  Instead it is about providing the interface for better integrating with "hardware" like QEMU or others where the expectation is that hardware mapping is provided by the FDT.  A follow on application PR will provide a interface for dumping the FDT in human readable form.
Impact
The FDT provided by QEMU is now available to the kernel and userspace through procfs.  No drivers make use of the interface at this time, but I do plan to add support for more virtio devices to be able to use this information.

Kernel build is not working quite right yet. I need to figure out how to properly map the physical address to a virtual address with the MMU.  I have not use kernel mode with riscv yet on NuttX, so any pointers are helpful.
❯ qemu-system-riscv64 -s -S -semihosting -M virt,aclint=on -cpu rv64 -smp 8 -bios none -kernel nuttx -nographic
ABC
NuttShell (NSH) NuttX-12.1.0
nsh> hexdump /proc/fdt
[   10.683000] riscv_exception: EXCEPTION: Load page fault. MCAUSE:<PHONE_NUMBER>00000d, EPC:<PHONE_NUMBER>010230, MTVAL:<PHONE_NUMBER>000004
[   10.683000] riscv_exception: PANIC!!! Exception =<PHONE_NUMBER>00000d
[   10.683000] _assert: Current Version: NuttX  12.1.0 9cd8ff5a0b-dirty May  6 2023 23:41:40 risc-v
[   10.683000] _assert: Assertion failed panic: at file: common/riscv_exception.c:85 task: /system/bin/init 0xc000004a

Kernel build is not working quite right yet. I need to figure out how to properly map the physical address to a virtual address with the MMU. I have not use kernel mode with riscv yet on NuttX, so any pointers are helpful.
❯ qemu-system-riscv64 -s -S -semihosting -M virt,aclint=on -cpu rv64 -smp 8 -bios none -kernel nuttx -nographic
ABC
NuttShell (NSH) NuttX-12.1.0
nsh> hexdump /proc/fdt
[   10.683000] riscv_exception: EXCEPTION: Load page fault. MCAUSE:<PHONE_NUMBER>00000d, EPC:<PHONE_NUMBER>010230, MTVAL:<PHONE_NUMBER>000004
[   10.683000] riscv_exception: PANIC!!! Exception =<PHONE_NUMBER>00000d
[   10.683000] _assert: Current Version: NuttX  12.1.0 9cd8ff5a0b-dirty May  6 2023 23:41:40 risc-v
[   10.683000] _assert: Assertion failed panic: at file: common/riscv_exception.c:85 task: /system/bin/init 0xc000004a

0000000087000004 <- this is the physical address of the FDT.

@pussuw could you help? BTW, does it work in FLAT mode? @btashton

Kernel build is not working quite right yet. I need to figure out how to properly map the physical address to a virtual address with the MMU. I have not use kernel mode with riscv yet on NuttX, so any pointers are helpful.
❯ qemu-system-riscv64 -s -S -semihosting -M virt,aclint=on -cpu rv64 -smp 8 -bios none -kernel nuttx -nographic
ABC
NuttShell (NSH) NuttX-12.1.0
nsh> hexdump /proc/fdt
[   10.683000] riscv_exception: EXCEPTION: Load page fault. MCAUSE:<PHONE_NUMBER>00000d, EPC:<PHONE_NUMBER>010230, MTVAL:<PHONE_NUMBER>000004
[   10.683000] riscv_exception: PANIC!!! Exception =<PHONE_NUMBER>00000d
[   10.683000] _assert: Current Version: NuttX  12.1.0 9cd8ff5a0b-dirty May  6 2023 23:41:40 risc-v
[   10.683000] _assert: Assertion failed panic: at file: common/riscv_exception.c:85 task: /system/bin/init 0xc000004a

0000000087000004 <- this is the physical address of the FDT.

What is the problem, the kernel does not see the FDT ? Where does it go in the image ? If it goes to kernel .data section it should just work. If it goes somewhere else you can look at the file below for an example on how to add kernel mappings.
https://github.com/apache/nuttx/blob/master/arch/risc-v/src/qemu-rv/qemu_rv_mm_init.c
That file does the code and RAM mappings for kernel. You can add the mapping there.

It won't be known until runtime (passed via a0 which is what I wired up) so sounds like I need to add another mapping. I was looking in that code last night but need to spend a little more time understanding how it works.

It should be as simple as
map_region(FDT_PADDR_START, FDT_VADDR_START, FDT_SIZE, MMU_KDATA_FLAGS);

@pussuw I think I am missing something.  Right now it looks like we map 1:1 physical and virtual addresses for the kernel text and data, but that means I cannot just simply extend the existing logic like this:
  binfo("map kernel text\n");
  map_region(KFLASH_START, KFLASH_START, KFLASH_SIZE, MMU_KTEXT_FLAGS);

  binfo("map kernel data\n");
  map_region(KSRAM_START, KSRAM_START, KSRAM_SIZE, MMU_KDATA_FLAGS);

  binfo("map fdt data\n");
  fdt = devicetree_get_fdt();
  map_region((uintptr_t)fdt, (uintptr_t)fdt,
             be32toh(((struct fdt_header_s *)fdt)->totalsize),
             (PTE_R | PTE_G));

This will fail to return a pbase
      /* See if a mapping exists ? */

      pbase = mmu_pte_to_paddr(mmu_ln_getentry(
                 KMM_SPBASE_IDX, KMM_SPBASE, vaddr));

which will then call slab_alloc which will fail.

@xiaoxiang781216  I'll restructure this to make fdt the top level, I think that makes sense.  I think I also sorted the kernel build changes, but I need to do a little more verification that I did not break something else.

@pussuw I think I am missing something. Right now it looks like we map 1:1 physical and virtual addresses for the kernel text and data, but that means I cannot just simply extend the existing logic like this:
  binfo("map kernel text\n");
  map_region(KFLASH_START, KFLASH_START, KFLASH_SIZE, MMU_KTEXT_FLAGS);

  binfo("map kernel data\n");
  map_region(KSRAM_START, KSRAM_START, KSRAM_SIZE, MMU_KDATA_FLAGS);

  binfo("map fdt data\n");
  fdt = devicetree_get_fdt();
  map_region((uintptr_t)fdt, (uintptr_t)fdt,
             be32toh(((struct fdt_header_s *)fdt)->totalsize),
             (PTE_R | PTE_G));

This will fail to return a pbase
      /* See if a mapping exists ? */

      pbase = mmu_pte_to_paddr(mmu_ln_getentry(
                 KMM_SPBASE_IDX, KMM_SPBASE, vaddr));

which will then call slab_alloc which will fail.

The slab allocator is for the L3 page table entries. You need to increase the L3 page table size.
Also keep in mind, that the current implementation can ONLY map 1GiB of continuous memory with 4K page granularity. This is because we have only 1 L2 page table and that can map 1GiB only.
So depending on your memory layout you might need to fix that too...

After doing a little more digging I think the cleanest thing to do is to just copy the structure into some allocated memory.  Internal to QEMU the address of the FDT passed could reside in the DRAM address space or after it, depending on if DRAM spans the 3GB address mark (to support 32bit).
Relevant logic is in https://github.com/qemu/qemu/blob/8844bb8d896595ee1d25d21c770e6e6f29803097/hw/riscv/boot.c#L277-L325 Since this logic is specific to the qemu sim, I dont see a great reason to not to just set aside 512kB (which would be massive FDT) and memcpy from a1 to that based on the FDT header size information.

So I do not forget.  The boot spec that qemu uses matches Linux understanding for arm64, so the address to the dtb should be in the x0 register for arm64 https://github.com/torvalds/linux/blob/v6.3/Documentation/arm64/booting.rst?plain=1#L162
r2for arm https://github.com/torvalds/linux/blob/v6.3/Documentation/arm/booting.rst?plain=1#L194

@btashton when do you plan to finish this patch? it is very useful with patch https://github.com/apache/nuttx/pull/9297.

@btashton when do you plan to finish this patch? it is very useful with patch https://github.com/apache/nuttx/pull/9297.

I should be able to make my changes this week.

That's great, we can automatically find and register all virito devices from device tree.

I made the changes with the new storage in bss that we copy to, but because the fdt may be fairly large this is causing issues in the kernel build when I extend from the default of 2M to 16M.  I think there actually may be a bug in the mmu logic which I am trying to dig deeper into.

could you provide a patch for flat/protected mode and improve it later?

@btashton @leo11261 update your patch to fix the issue mention in the comment, could you review it?


Remove symbols that are removed in python 3.10

Those functions and variable are listed in https://docs.python.org/3.10/whatsnew/3.10.html#id4

Rebased on master and moved the CHANGELOG entry into a new unreleased section, will merge shortly...


Diagnostic Settings -  Category on the logs is null

Bug Report

SDK function: armmonitor.NewDiagnosticSettingsClient
apiVersion: "2021-05-01-preview"
output : "logs": [
{
"category": null,
"categoryGroup": "audit",
"enabled": true,
"retentionPolicy": {
"enabled": false,
"days": 0
}
},
{
"category": null,
"categoryGroup": "allLogs",
"enabled": true,
"retentionPolicy": {
"enabled": false,
"days": 0
}
}
],

It seems that instead of “category”, the api returns “categoryGroup”, but on the SDK there is no such parameter.

What happened?

When we’re trying to get the diagnostic settings, the category on the logs is null.
It seems that instead of “category”, the api returns “categoryGroup”, but on the SDK there is no such parameter.

What did you expect or want to happen?
the function needs to return non-null category

How can we reproduce it?
create diagnostic settings for Azure Key Vault:
client, _ := armmonitor.NewDiagnosticSettingsClient(cred, &arm.ClientOptions{
ClientOptions: policy.ClientOptions{
Transport: &apiVersionTransporter{
apiVersion: "2021-05-01-preview",
httpClient: http.DefaultClient,
},
},
})
diagnosticSettings, err := client.List(c.context, s.id, nil)
if err != nil {
return err
}

@tadelesh could you help to take a look?

@yaminSapir Sorry for delayed reply. The API-version in the SDK is not 2021-05-01-preview, but 2017-05-01-preview. We will let service team to update the release tag and release the new version.

@yaminSapir Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

Adding the Service team.
@sameergMS, @dadunl  Please look into this ask and provide an update once you get a chance. Thanks in advance.

We are looking for category in the diagnostic setting response and not seeing it - any update would be helpful!

We've released a new version of armmonitor package which contains the latest diagnostic setting API. Please upgrade and have a try.


feat: bigger height for expanded help, dummy shortcuts for github actions

Summary
How did you test this change?
Images/Videos

Current dependencies on/for this PR:

main

PR #160

PR #161   👈

This comment was auto-generated by Graphite.


Restrict assignments to calls and incidents

Describe the feature
It occurred to me while we were discussing https://github.com/SnailyCAD/snaily-cadv4/issues/555 that in some instances or for some departments you wouldn't want a unit to be attached to another incident and/or 911 call.
How difficult would it be to add an option for each department to have a setting that is user toggled that allows it to support assignment of multiple incidents/calls to one unit?
Or at least a global CAD option that specifies (similar to the current configurations for how many units they can create) how many assignments they can have for 911 and for incidents.
Eg. A cap of 1 x incident assignment and 1 x 911 call assignment per unit.
Additional Context
No response

Unfortunately this will not show in the UI whether the unit can be assigned. In the API it will skip the unit if it cannot be assigned anymore


Compatibility with $q.all

Hi there. Thank you for putting together a very useful library. One thing I've run into and been struggling with the last two days, is trying to get $q.all(promises) resolve when the stubs are resolved in each promise.
I have this method I am testing:
attachPhotoData: function (photos) {
  ... ... ...
  promises.push(fileReader.readAsDataUrl(photo)); // populate with $q promise objects
  return $q.all(promises)
        .then(function (photos) {
          console.log('Resolved collection:', photos); // <- never get here from test
          return photos;
        })
}

Everything works fine in the browser, but I have issues in tests where I mock like that:
module(function($provide) {
      $provide.value('fileReader', {
        readAsDataUrl: sinon.stub().resolves('data:image/jpeg;base64,some-photo-data')
      });
    });

and a test like this:
it('attaches photo data to each photo', function(done) {
      var photosWithData = postForm.attachPhotoData(photos);
      photosWithData
      .then(function(result) {
        console.log('Resolved photos:', result); // <- never get here
        done();
      });

      $rootScope.$apply();
});

It appears that, though the readAsDataUrl stub resolves each promise as expected, Angular $q.all never gets resolved. Seems like $q.all doesn't detect that all sinon-as-promissed promises in the promisses array have been resolved and my test times out after 2 seconds as it should. Everything works fine if I modify the stub to use $q.when instead:
beforeEach(function() {
 ...
  inject(function(_$q_, _$rootScope_, _postForm_, _fileReader_) {
    postForm = _postForm_;
    fileReader = _fileReader_;
    $q = _$q_;
    $rootScope = _$rootScope_;
    fileReader.readAsDataUrl = sinon.stub().returns($q.when('data:image/jpeg;base64,some-photo-data'));
  });
});

Wonder, if this is something you've run into before.

Hmm. So sinon-as-promised as of v2 returns thenables rather than promises. It works pretty much exactly the way knex queries do. There's a method then, but it's not a real promise. Promise implementations are supposed to call then anytime a return value has it as a method.
Can't see any reason why there would be problems:
https://github.com/angular/angular.js/blob/master/src/ng/q.js#L514-L536
Do me favor and write up a reproduction that I can clone and npm test. Also make sure you're calling sinonAsPromised($q): https://github.com/bendrucker/sinon-as-promised/blob/master/examples/angular/test.js#L12

Also make sure you're calling sinonAsPromised($q)

Sure enough, I forgot to call this in beforeEach block. Everything is working smooth now. Thank you.


Add Nov 2020 CC Release Notes

The content is copied over from the CRDB v20.2.0 release notes.
Closes #8974.
cc: @kannanlakshmi

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/bb7adcf6accbb7bb522aeb5481285d7411f690ed/
Edited pages:

releases/cockroachcloud-11192020.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4c631a35b2f6021ac620a761a68d1592f5353ed5/
Edited pages:

releases/cockroachcloud-11192020.md


Gulp upgrade: Remove parallel task

Though earlier code works fine in dev, CSS was not getting loaded when deployed. Checking if removing parallel task helps

Coverage remained the same at 60.791% when pulling 8965cf1af52567f13c58d3cbfa180ef80e485d19 on charhate:upgrades into 456575b88b73e4dcc6e7b9d9ac410e8aa8884d1f on Netflix:master.


ShareX URL Empty: Unable to receive link after uploading images

Hey I was able to get zipline up in 2 minutes with docker-compose and images successfully upload into zipline, however after sharex uploads an image it returns "ERROR URL EMPTY".
I used to example ShareX config from the docs
{
  "Version": "13.2.1",
  "Name": "CDN",
  "DestinationType": "ImageUploader, TextUploader",
  "RequestMethod": "POST",
  "RequestURL": "https://domain.tld/api/upload",
  "Headers": {
    "Authorization": "1234567",
    "Embed": "true"
  },
  "URL": "$json:data.url$",
  "Body": "MultipartFormData",
  "FileFormName": "file"
}

2021-07-15 15:05:26.843 - File opened: C:\Users\duck\Documents\ShareX\Logs\ShareX-Log-2021-07.txt
2021-07-15 15:05:46.596 - ApplicationConfig save started: C:\Users\duck\Documents\ShareX\ApplicationConfig.json
2021-07-15 15:05:46.596 - UploadersConfig save started: C:\Users\duck\Documents\ShareX\UploadersConfig.json
2021-07-15 15:05:46.597 - HotkeysConfig save started: C:\Users\duck\Documents\ShareX\HotkeysConfig.json
2021-07-15 15:05:46.727 - UploadersConfig save successful: C:\Users\duck\Documents\ShareX\UploadersConfig.json
2021-07-15 15:05:46.763 - HotkeysConfig save successful: C:\Users\duck\Documents\ShareX\HotkeysConfig.json
2021-07-15 15:05:46.799 - ApplicationConfig save successful: C:\Users\duck\Documents\ShareX\ApplicationConfig.json
2021-07-15 15:06:09.890 - UploadersConfig save started: C:\Users\duck\Documents\ShareX\UploadersConfig.json
2021-07-15 15:06:09.986 - UploadersConfig save successful: C:\Users\duck\Documents\ShareX\UploadersConfig.json
2021-07-15 15:07:49.288 - CommandLine: -CustomUploader "C:\Users\duck\Downloads\zip.sxcu"
2021-07-15 15:08:09.310 - CommandLine: C:\Users\duck\Pictures\idols\E4knzMnXMAQQUJN.jpg
2021-07-15 15:08:09.311 - Task in queue. Job: FileUpload, Type: Image, Host: Custom image uploader
2021-07-15 15:08:09.362 - Task status: Preparing
2021-07-15 15:08:09.389 - Upload started. Filename: E4knzMnXMAQQUJN.jpg, Filepath: C:\Users\duck\Pictures\idols\E4knzMnXMAQQUJN.jpg
2021-07-15 15:08:09.423 - Task failed. Filename: E4knzMnXMAQQUJN.jpg, Errors:
URL is empty.

2021-07-15 07:07:10,020 PM INFO  [url] 200: /api/user

2021-07-15 07:07:10,126 PM INFO  [url] 200: /api/user/images

2021-07-15 07:07:10,188 PM INFO  [url] 200: /api/stats

2021-07-15 07:08:10,254 PM INFO  [url] 200: /api/upload

2021-07-15 07:08:10,273 PM INFO  [image] User ducky (1) uploaded an image GrfvkL.jpg (6)

2021-07-15 07:11:42,246 PM INFO  [url] 200: /api/upload

2021-07-15 07:11:42,282 PM INFO  [image] User ducky (1) uploaded an image T0GZWr.jpg (7)

2021-07-15 07:13:07,783 PM INFO  [url] 200: /api/upload

2021-07-15 07:13:07,861 PM INFO  [image] User ducky (1) uploaded an image RkuwrT.jpg (8)

Now I can manually log into zipline and copy the url from the web ui and share it. It works perfectly that way.

Sorry, I havent updated the docs to have the correct url in the sharex config.
Just change the URL to $json:url$, or in the GUI of sharex just input url into the JsonPath

Thanks it works now


Backspace bug with Samsung Keyboard on mobile

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When I hold backspace with using Samsung Keyboard, editor crashes.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/gmertk/e61z7nfa/.
https://youtu.be/FOU08Msdb1s
What is the expected behavior?
It should remove all text when I hold backspace button with using Samsung Keyboard.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Samsung Internet / Chrome / android
It crashes at all of draft-js examples.

  function handleEditor(editorState: Draft.EditorState) {
    if (!editorState.getCurrentContent().hasText()) {
      const newContent = Modifier.insertText(
        editorState.getCurrentContent(),
        editorState.getSelection(),
        "  "
      );

      const newEditorState = EditorState.push(
        editorState,
        newContent,
        "insert-characters"
      );

      setEditorState(newEditorState);
    } else {
      setEditorState(editorState);
    }
  }

Just don't allow to be empty


xds: gracefully handle stream termination without error

Today, we only reconnect on the stream erroring. If it ends with a
success, we ~infinite loop doing nothing.
In standard operations, Istiod will never end the stream without an
error. However, it is possible to expose Istiod with a proxy that does.

Reproducer:

admin:
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 9901 }

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address: { address: <IP_ADDRESS>, port_value: 15011 }
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          stream_idle_timeout: 2s
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match: { prefix: "/" }
                route: { cluster: some_service }
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
  clusters:
  - name: some_service
    connect_timeout: 0.25s
    type: STATIC
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: some_service
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 15010

    typed_extension_protocol_options:
      envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
        "@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
        explicit_http_config:
          http2_protocol_options:
            connection_keepalive:
              interval: 30s
              timeout: 5s

PROXY_WORKLOAD_INFO=default/local/default PROXY_MODE=dedicated FAKE_CA=true XDS_ADDRESS="http://localhost:15011" cargo run -F testing

In response to a cherrypick label: new pull request created: #1370

In response to a cherrypick label: new pull request created: #1395

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/ztunnel#release-1.24 from head istio-testing:cherry-pick-1368-to-release-1.24: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between istio:release-1.24 and istio-testing:cherry-pick-1368-to-release-1.24"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}


card-tricks: introduction should expand on slicing options

Firstly, the introduction.md document of the card-tricks exercise very briefly mentions how to get a subslice from a slice. It would be very useful to update the example to show a slice and a subslice operation on that slice and show what is returned for the subslice.
Secondly, the exemplar solution interacts with slices in three ways that the student doesn't know about:

Getting a single element: https://github.com/exercism/go/blob/main/exercises/concept/card-tricks/.meta/exemplar.go#L9
Getting the elements up to an index: https://github.com/exercism/go/blob/main/exercises/concept/card-tricks/.meta/exemplar.go#L40
Gettting the elements from an index: https://github.com/exercism/go/blob/main/exercises/concept/card-tricks/.meta/exemplar.go#L40

The introduction.md document should introduce all syntax that the student must know about to complete the exercise. For more information, check the docs.

Assigning myself (to discourage duplicate work), but moshegood is handling this in #1665


Request for the GPS trajectories of TaxiBJ21 dataset.

Dear Weiwei,
I hope this message finds you well. I have been reading your paper "Big Data for Traffic Estimation and Prediction: A Survey of Data and Tools" and I found it to be a fascinating piece of work.
In the paper, you mentioned that the source taxi trajectories on November 2012, November 2014, and November 2015 has been published on this Github repository, but unfortunately, I have been unable to find it.
I am currently a PostDoc working on Zhejiang Lab and I requires a dataset of GPS trajectories for my project and your dataset would be a valuable resource for my research. Therefore, I kindly request your assistance in locating the dataset or if possible, sharing it with me.
I understand that you may have a busy schedule, but if it is not too much trouble, I would be very grateful if you could provide me with any information regarding the dataset or how to access it. Your help would be greatly appreciated.
Thank you for your time and consideration. I look forward to your response.
Sincerely,
Shen Fang<EMAIL_ADDRESS>

I have contacted the author via email and this issue should be closed.


DMP-1290: Set up Role Permission for External Services

Before creating a pull request make sure that:

[ x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[ x] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DMP-1290
Change description
Data Setip for External Services - XHIBIT, CPP, DAR_PD & MID_TIER
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Do you need to add DAR_MIDTIER_USER_NAME and DAR_MIDTIER_PASSWORD to docker-compose-local.yml?

@karen-hedges yes we would need it in docker-compose yaml

@hemantasharma1129 The JIRA mentions security_group for the external processing user - but I don't see any inserts into these tables?