Error: file does not exist but it exists

What is the issue?
Hello, I want to push my model to ollama but I got the error
retrieving manifest
Error: file does not exist
but the problem is that I have the file, specifically "C:\Users\User.ollama\models\manifests\registry.ollama.ai_\mymodel\latest"
and my username is _ (link: https://ollama.com/_ ), so and I can't change my username
"""
D:\ollama> ollama create _/mymodel:latest -f Modelfile
transferring model data
using existing layer sha256:617ba424eabae67d228cf4598d2b18d9656b73c1f8f5bfa974ead81485dad2a5
using existing layer sha256:f5dc666b38fce911ccd916bcb13ea78a8002803fd11d5bb6486c4dd76ab8223f
using existing layer sha256:3dddcbf82aec37d515d388e1141900e1530f74f20c5091f64567609a56fe8f43
using existing layer sha256:023c31c9015bbf14d78183c19eec819c3142e791c857bbc3989e53250f00561d
using existing layer sha256:c50ad1ef7469cb081d31e4c321e73562e1e657e890a325b4d7214f8988fd1678
using existing layer sha256:6a6636a5d2ef8c1f29444967fb0f17930369d2c53117d39bd3926760d1062230
writing manifest
success
D:\ollama> ollama list
NAME                            ID              SIZE    MODIFIED
_/mymodel:latest                  37dad3f2b9d3    13 GB   18 seconds ago
mymodel:latest                    37dad3f2b9d3    13 GB   23 minutes ago
D:\ollama> ollama push _/mymodel:latest
retrieving manifest
Error: file does not exist
"""
OS
Windows, WSL2
GPU
Nvidia, Intel
CPU
Intel
Ollama version
0.2.7

Hi @DevLLM, this one slipped past our validation. Send me an email at bruce.macdonald-at-ollama.com and I'll get you switched over to whatever valid namespace you'd like.

@DevLLM Will you please confirm the path you pasted (C:Users\User.ollama\models\manifests\registry.ollama.ai_\mymodel\latest) is correct? If so, it's also a bug that there is no / after .ai and before _.

I tried creating a model and followed this example to execute the ollama commands. Everything went smoothly during the creation process, but when I tried to run the model, it said it couldn't be found. Did I make a mistake somewhere? Could you please help me?
Thank you in advance.
environment: docker ubuntu22.04
Modelfile:
# Modelfile
FROM "/build_docker/Llama-3.2/Llama-3.2-11B-Vision-Instruct-mmproj.f16.gguf"

PARAMETER stop "<|im_start|>"
PARAMETER stop "<|im_end|>"

TEMPLATE """
<|im_start|>system
{{ .System }}<|im_end|>
<|im_start|>user
{{ .Prompt }}<|im_end|>
<|im_start|>assistant
"""

Log:
(py310) root@019a5ec06402:~# ollama create my-own-model -f Modelfile
transferring model data 100%
using existing layer sha256:622429e8d31810962dd984bc98559e706db2fb1d40e99cb073beb7148d909d73
creating new layer sha256:8971eb8e89ce161a65232db6db5019953dbc313fc296d9e6e9d7823e395673b9
creating new layer sha256:f02dd72bb2423204352eabc5637b44d79d17f109fdb510a7c51455892aa2d216
creating new layer sha256:896227e1de4d5b48a7fbf9eec7a095ab38351f5c3efb11cf81f616cb9208570e
writing manifest
success
(py310) root@019a5ec06402:~# ollama list
NAME                   ID              SIZE      MODIFIED
my-own-model:latest    c4901261a022    1.9 GB    About a minute ago
llama3.2:1b            baf6a787fdff    1.3 GB    2 hours ago
(py310) root@019a5ec06402:~# ollama run my-own-model:latest
pulling manifest
Error: pull model manifest: file does not exist
(py310) root@019a5ec06402:~#

ollama serve:
[GIN] 2024/11/15 - 16:38:06 | 200 |      2.5631ms |       <IP_ADDRESS> | POST     "/api/create"
[GIN] 2024/11/15 - 16:38:34 | 200 |        91.4µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:38:34 | 200 |       322.4µs |       <IP_ADDRESS> | GET      "/api/tags"
[GIN] 2024/11/15 - 16:38:41 | 200 |        18.3µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:38:41 | 200 |       357.1µs |       <IP_ADDRESS> | POST     "/api/generate"
[GIN] 2024/11/15 - 16:38:41 | 200 |    133.8325ms |       <IP_ADDRESS> | DELETE   "/api/delete"
[GIN] 2024/11/15 - 16:38:43 | 200 |          18µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:38:43 | 200 |       235.5µs |       <IP_ADDRESS> | GET      "/api/tags"
[GIN] 2024/11/15 - 16:41:16 | 200 |        39.3µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:41:29 | 201 |    5.5687215s |       <IP_ADDRESS> | POST     "/api/blobs/sha256:622429e8d31810962dd984bc98559e706db2fb1d40e99cb073beb7148d909d73"
[GIN] 2024/11/15 - 16:41:29 | 200 |      3.1334ms |       <IP_ADDRESS> | POST     "/api/create"
[GIN] 2024/11/15 - 16:42:48 | 200 |        77.5µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:42:48 | 200 |       784.1µs |       <IP_ADDRESS> | GET      "/api/tags"
[GIN] 2024/11/15 - 16:43:01 | 200 |        18.4µs |       <IP_ADDRESS> | HEAD     "/"
[GIN] 2024/11/15 - 16:43:01 | 404 |       422.2µs |       <IP_ADDRESS> | POST     "/api/show"
[GIN] 2024/11/15 - 16:43:02 | 200 |    1.2704652s |       <IP_ADDRESS> | POST     "/api/pull"

Hi @Minxiangliu it looks like your referencing a file that exists in a docker container: FROM "/build_docker/Llama-3.2/Llama-3.2-11B-Vision-Instruct-mmproj.f16.gguf". Is this file accessible from where the ollama server is running?

Hi @BruceMacD ,
Thank you for your reply, and apologies for my late response. After some testing, I was able to use the ollama3.2-vision model on the ollama server. Among these GGUF models, all of them work except for mmproj.f16 model. Thank you! I'll continue testing with the models on the ollama server.


Create a patterns publishing roadmap for cupcake website

User Story

As a Cupcake website creator

I need to know what patterns will be published on the cupcake website

so that I can: use it for alignment in our team and discussion with the Carbon Team.

Task

Jenny and Lara to work together to figure out what patterns will be published in order of priority.
Jenny to create a publishing roadmap wiki page

Acceptance criteria

[ ] Roadmap items agreed by Wonil, Lara, Jenny.

I've been chatting with Lila and Jill about their time and priorities for documenting their web simplification patterns for the cupcake site. They will try to add stories to their current + upcoming WS sprints to start work on it asap but right now they don't know what they will begin with or when.
Aside from overview and leadspace left-aligned this publishing roadmap is dependent on their availability. I'm thinking we have to move this to backlog.

@lara Got it and yes, let's move this to the backlog.
@RobertaJHahn Can you move this to the backlog for us, please? We will need to set priority once we have more information from Lila and Jill.

Note: We need to update the Website content inventory list for the Carbon website once this task is completed.

@larahanlon2 Great planning work and thank you again for going over the process steps document with Jim, Jacob and I earlier today.
I shared my estimate and I think four sprints are pretty safe to set as an expectation margin. We want to publish content sooner than four sprints and will do so if we can, it all depends on how complex the pattern is going to be and how much material we can gather in Sprint 1.
Let me know what do you think after you have a chance to look at my estimate.

Publishing work will be done post April release and this task will be closed.


Update the extension in Chrome Webstore

There is an old version 0.6.1 of the extension in Chrome Webstore while the current is 0.7.0.
Please update it.

Done. Sorry for delay.
On Wed, Jul 15, 2015 at 9:02 PM Mikhail Nasyrov<EMAIL_ADDRESS>wrote:

There is an old version 0.6.1 of the extension in Chrome Webstore while
the current is 0.7.0.
Please update it.
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/keysocket/issues/141.


[JWT] Enable configurable early token refresh in Java Client

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Same as this https://github.com/apache/pulsar/pull/13951 - but to support the "simpler" JWT auth workflow/client setup.
Solution
Similar to AuthenticationOAuth2 - firstly AuthenticationToken will need to cache the authenticating JWT in a transient volatile field.
This value will also be injected into AuthenticationDataToken - and getCommandData will now return this value - and not lazily generate a new token.
Meanwhile, a scheduled task will be created, similar to https://github.com/apache/pulsar/pull/13951 to refresh the cached token.
Respect backwards compatibility.
Alternatives
Complete https://github.com/apache/pulsar/pull/13951 - and use it. In some cases though, using the OAuth client is not appropriate. For example, when using Vault as an OIDC - while also providing apps a Vault agent to do the Vault auth - a clientID and secretID are not needed by the app (as again the OIDC/Vault auth is abstracted away)
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

@lhotari - if u have some time, can u let me know ur thoughts on the feasibility of having this functionality added? The current details are hopefully enough to enable that conversation - and if no immediate/obvious blockers or issues, I can spend some more time identifying all the changes, and continuing conversation on the dev email distribution. Thanks

if u have some time, can u let me know ur thoughts on the feasibility of having this functionality added? The current details are hopefully enough to enable that conversation - and if no immediate/obvious blockers or issues, I can spend some more time identifying all the changes, and continuing conversation on the dev email distribution. Thanks

@damienburke yes, the plan you have presented looks good to me.

For example, when using Vault as an OIDC - while also providing apps a Vault agent to do the Vault auth - a clientID and secretID are not needed by the app (as again the OIDC/Vault auth is abstracted away)

Just curious, how is this configured with the Pulsar client?

Thanks @lhotari

how is this configured with the Pulsar client?

Sure. We configure the token supplier method to make the Vault API call. This call is proxied through a Vault Agent - and the Vault Agent handles the auth.


Deprecate Purview Catalog SDK

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

I am following the guide here to deprecate the Catalog SDK.
https://github.com/Azure/azure-sdk-for-java/blob/main/doc/deprecation_process.md
Please help to review and approve the changes.


Support multiple languages

At least NL/DE would be good.
We can probably find benevolent translators within the MICA team

Discussed with @EmmaCartuyvels1: this is nice to have.


Modified Readme

(1) Observed a couple of grammatical errors, which I will point out in separate comments
(2) In usage after explaining the conda environment, it is better to also have a dependencies section like in our proposal md, instead of linking to the environment yaml
(3) I pretty sure you already know, but its just good to have a record of it, final model performance need to be discussed.
Everything else looks good, thanks Lianna!

Thank you for reviewing for the first point.
For the second, I will modify and add the dependencies after the file is ready.
For the third, yeah I will need to add it after final version is ready.

(1) Observed a couple of grammatical errors, which I will point out in separate comments
(2) In usage after explaining the conda environment, it is better to also have a dependencies section like in our proposal md, instead of linking to the environment yaml
(3) I pretty sure you already know, but its just good to have a record of it, final model performance need to be discussed.
Everything else looks good, thanks Lianna!

Thank you for reviewing for the first point.
For the second, I will modify and add the dependencies after the file is ready.
For the third, yeah I will need to add it after final version is ready.

I have added the changes, the dependecies will be updated when the file is ready. If no other comment, I think we can merge this for now, and I will make separate PR for the final version. @Arushi282

yeap. looks good


Content of view is streached

I am using this library to showing cards with images and some other content. but the problem is that when I set card's width and height to desired, the content of the card is stretched. Please tell me the solution.

Can you please provide a code snippet?
It sounds to me like an ordinary layout problem that isn't specifically
related to ViewPagers. Can you try wrapping your ImageView (or whichever
child view you're using) in a FrameLayout to see if the problem persists?
On Thu, Sep 7, 2017, 12:00 Rahul Sharma<EMAIL_ADDRESS>wrote:

I am using this library to showing cards with images and some other
content. but the problem is that when I set card's width and height to
desired, the content of the card is stretched. Please tell me the solution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Pixplicity/MultiViewPager/issues/24, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AARdYyBCsZsr2AgJrrXK0Pp-xYcGnepFks5sf77IgaJpZM4PPlH4
.


Add option for balancing a single table at a time when using host regex balancer

This adds a new property balancer.host.regex.concurrent.tables which if true will process multiple tables at a time (this is the default). If set to false the balancer will stop processing after a table is found with migrations
This is a draft PR for now to start getting some feed back on the approach. I have implemented the 4 steps but not quite sure it's actually correct yet. I've been playing around with it for a little while tweaking things and trying to test but it hasn't been tested for real yet (other than the smiple test in BaseHostRegexTAbleLoadBalancerTest) yet.
I made the property a default of true for concurrent but we could negate that and make the property something like balancer.host.regex.single.table and default to false.
This closes #4521

I removed 2.1.4 milestone, since it looks like this PR was closed due to the branch being deleted, but was not merged.

Oops I was cleaning up stale branches and deleted this by mistake so I can restore it, either way it may not be merged at this point so best to take off 2.1.4.


Analytics

Moved the new analytics library from static so it can be easily used in non-rails projects.
PR for analytics library
The tests for analytics used Jasmine 2 so it made sense to upgrade the existing frontend_toolkit tests to use that.
Analytics had one usage of jQuery so replaced that with plain Javascript so it has no dependencies.
Included a sample init to be copied into your own project as GA account IDs should not be stored in this repo.

Other than the comments already made LGTM

Couple of thoughts:
This needs some better documentation as to what it is and how to use it. I would suggest creating a docs folder in the project root and creating some documentation as to what the different parts are and how you can use them.
I know it has now been removed but relying on bind in things that are in the toolkit is fine. The toolkit contains the bind polyfill for people that need to use it. This should just be made clear in the documentation for that feature that you will need to include it.

@edds I've tidied up some of the docs in https://github.com/alphagov/govuk_frontend_toolkit/pull/161, I'll add analytics details when that PR is merged.

Closing while I write documentation.


Dictionaries contain too much Wiktionary code stuff, possible to filter better?

From https://github.com/rdoeffinger/Dictionary/releases/tag/v0.3-oldformat, I downloaded the dictionaries EN.quickdic, DE.quickdic and EN-DE.quickdic and installed these on my Tolino Vision 5 (firmware 15.2.0).
As you can see from the attached screenshots, a lookup of the word "character" in EN.quickdic produces 14 pages, badly formatted with lots of Wiktionary code stuff; a try to translate "character" into German using EN-DE.quickdic produces 31+ pages, partly more useful, but still containg lots of Wiktionary code.

Can I kindly suggest that you revise the Wiktionary code building process a little, to adapt for all this (unwanted/unneeded) extra information, in order to arrive at a more usable output again?
Let me know if you need more information, or how I could possibly help – thanks!
EN.quickdic-character-screenshots.zip
EN-DE.quickdic-character-screenshots.zip
P.S.: I also believe that "Hyphenation" (page 3/14 of "character" lookup) should be a separate subsection (like "Pronunciation"), and the parts of the word more likely displayed like "char·ac·ter".
P.P.S.: I think the output should look more like the Wiktionary page, leaving out the ToC and the non-English parts, probably even the audio player links for pronunciation. (Most e-readers either don’t have audio, might have no Internet connection, or simply won’t be able to switch to the browser and play audio, then return to the same page in the ebook.)

Wikimedia's Enterprise HTML Dumps

This looks interesting but it would/could probably take more space than wikicode...


Version number shown is wrong

Defect description
Version shown isn’t the current version: shows 2.6.0 instead of 2.6.1
Expected Result
Show the correct current version always (2.6.1 in this case). Perhaps adding a test or some automation to our release workflow would help.
Steps to Reproduce

Install version 2.6.1
Go to Settings > About
Shows incorrect version

Affected Versions, OS, Device
All OSs, Version 2.6.1

JIRA link: https://nem-software.atlassian.net/browse/WALL1-21

Hi @coiki this is related to Nem Nis1 wallet not symbol.


Change the version information in the page to v1.12.0

Change the version on the page to v1.12.0

/assign @tengqm

/lgtm
/approve


Image name translation in Virtlet p.2

This is a followup for #400.
Instead of using config file, Virtlet should read image name translation config from CRDs (Custom Resource Definitions). The CRDs should be of kind VirtletImageMapping. All the CRDs of this kind are used, and any changes in these objects as well as adding new ones / deleting some of the CRDs should take effect immediately without the need to restart Virtlet pods.
Below is an example of a CRD:
apiVersion: "virtlet.k8s/v1"
kind: VirtletImageMapping
metadata:
  name: primary
spec:
  translations:
  - name: cirros/current
    url: https://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img
  - name: ubuntu/16.04
    url: https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  - name: cirros/local
    url: http://image-service.default.svc.cluster.local/cirros-0.3.5-x86_64-disk.img
  - regexp: 'cirros/(\d+\.\d+\.\d+)'
    url: 'https://download.cirros-cloud.net/$1/cirros-$1-x86_64-disk.img'
  - regexp: 'centos/(\d+)-(\d+)'
    url: 'https://cloud.centos.org/centos/$1/images/CentOS-$1-x86_64-GenericCloud-$2.qcow2'

I have several suggestions:

add ability to provide additional SSL settings for each image like custom CA and so on. There are also http parameters that sometimes required like how many redirects can be followed, how many times to retry download etc.

drop the regexps. I know it's powerful, but
a. It complicates the syntax and user experience. It's easy to write wrong but when virtlet will eventually  fail to download the image or will download wrong image it won't be easy for a user to find out what went wrong
b. Imagine, that starting from version 9 centos decides to change the naming scheme (url template). How would you specify it? Since each regexp defines an open group of names it is possible for one name to match several regexps at once or you may need to have exclusion from the group for some particular version or range of versions
c. Once you have a fixed list you can restrict image to only those that are listed. Cloud admins often want it.
d. We don't have any real use case / customer request for such power

Can we use docker syntax for versions? I.e. ubuntu/16.04 -> ubuntu:16.04

I think we should keep backward compatibility. If the image is virtlet/something:something then it's the new syntax. If it is virtlet/something.domain (i.e. there is a period in the name) then its the URL

We could also have several alternative image lists (i.e. do not make this new object be a singleton):
virtlet/production/imageName uses VirtletImageMapping production
virtlet/testing/imageName uses image from the testing list
virtlet/imageName is an alias for virtlet/default/imageName

ad.1 +1
ad. 2. IMO we should keep regexes.
ad. a. If user do not know them - he simply can use full matching and not use regexes at all.
ad. b. I'm not sure if i understand that correctly. Do you suggest that some notation should be used always without understanding? Imo it's admin responsibility to add new rule and use it instead of old one for new versions. Providing there so universal method which could group old/new scheme - other than regex (you can describe such thing in regex, two dfferent schemas for different versions) would be nice from UX perspective seen by dumb end user, but for us it's over-complication of idea.
ad. c. Same can be true for list with regexes. You can specify exact text without wildcards in regexes. Btw. very good idea with possibility of limiting images to that only allowed by admins. That desires a separate issue.
ad. 3. Colon has special meaning and if used does not add it - kubelet will add ":latest" to whole image, and that could hurt us a bit. If it's other than ":latest" - we can use that for matching.
ad. 4. Easier would be to keep old style when any rule/entry didn't matched the image url - no need to treat in special way anything.
ad. 5. Do you suggest to use separate CRDs per "prefix/"? Hmmm... That would increase usability/improve UX. I like the idea. If you had in mind something other - please clarify that a bit deeper.

I'd suggest doing this in a followup
Well, regexps are optional. The user can use fixed naming scheme. We may even add a warning to docs about the possibility to shoot oneself in the foot. Yet regexp scheme can save us a lot of hassle when writing examples, debugging stuff etc. E.g. I see a problem with CentOS and want to try another CentOS version. In many cases it will be easier to just edit the pod definition. And implementing this regexp replacement is trivial
This would be nice but would require deeper revamp of our image handling. I'd say this can be good for a followup.
Same as 3. I'd prefer not to touch the image tags for now.
I'd suggest an optional prefix field in the CRD which will make it apply only to the images with that prefix.

my point was that regexps has its own cons and pros and IMO more of a cons. Once you implement it, you will have to document it, support it, have tests for it and when you have a batter idea you cannot just remove the feature without breaking backward compatibility. Currently there are no real use cases for regexps, so why spend time on it? Leave it until you see that there is indeed a problem that requires such solution and there is no better way.

It's not about tagging. It's about keeping backward compatibility with current syntax

I want to ensure - you know that to every image definition which does not contain colon k8s adds ":latest"? You know that this can provide conflict with something on kubelet side, because if you will use colon kubelet will treat that as a tag?

I know that. But I don't see any problems. If you get something:latest you can lookup for something:latest image first and if there is no such entry, look up just for something. Not a big deal.
For me

Ok. Fair enough :)
But still i think that additional syntax for backward compatibility is not needed. Simply - no match in rules - assume that it's plain definition, which should not be "translated".

Well, if I have image
virtlet/cirros I'd better get an error saying that cirros image is not listed in bla-bla. Do the following to add it... rather than 'cannot resolve cirros domain`. This makes user experience better. But I don't insist

Concerning regexps. From the top of my head, one possible use case: the user has several images residing on a web server on a directory with uppercase chars in it, e.g. https://example.com/MyFileQCOW2Images/ while images themselves have lowercase names. That's possible e.g. if the user can upload the images to this dir and control their names but cannot reconfigure the web server for some reason (e.g. particular CI/Artifactory/whatever config in a company etc.). So he writes a rule to translate virtlet/myimages/... to https://example.com/MyFileQCOW2Images/... and that's it.

Or if we support tags (the part after colon), we later can use regexps to have some kind of image versioning. So e.g. a CI system stores different image versions in https://example.com/images/foobar-VVVV.qcow2 and they can be referred to as virtlet/foobar:VVVV with just one rule.

That being said, I'd postpone tags (:xxx) to a followup. They may have implications on both Virtlet and CRI proxy level that can add a couple of days to the task.

Just to note, that in my proposal there was no special treatment for the tags since there are no regexps and auto-translation. I don't know any of those implications so you know it better.
As for regex example above, as I said, I know regexps are powerful and can be used for many good things. My point was that we don't have anybody saying that he cannot just explicitly list all the images rather than create a translation rule. I'm myself was a big fan of powerful generic solutions like this, but it taught me to respect KISS principle - implement the simplest solution possible.
More generic solutions come with complications that are not obvious now, when you have nobody to prove the design. Even for your example, say you defined a rule
- name: (.*)
  url: https://example.com/MyFileQCOW2Images/$1

but then you need to create VM from an image in other location. Since the rule matches every name, you will either have to drop the rule and list all your images explicitly or replace .* with some weird regexp that excludes your image. And in both cases you have a risk of accidentally breaking everything for everyone, if your regexp is bad.
In systems that deal with group matching (e.g. firewalls) there are rule priorities, while lists, black lists, exclusions etc. You don't want to go there now. IMO it's better to always have an explicit list rather than implementing partial solution and then keeping backward compatibility with it

This conversation reminds me of the old joke:
Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.

Well frankly I cared more about myself and other Virtlet devs. Because e.g. I just want to serve some images, e.g. ones used by cirros images, off a local webserver. I start the webserver in simplest way possible, i.e. python -mSimpleHTTPServer. It'll listen on port 8000. I can't make it listen on privileged port 80 without sudo (also I may have other webserver there). This would not be a problem if not for virtlet/ prefix. So <IP_ADDRESS>:8000/cirros is valid. But virtlet/<IP_ADDRESS>:8000/cirros is less so because : is allowed only in the "hostname" part of the image name, and in 2nd case :8000/cirros will be considered an image tag. So I can get problems here trying to run a simple helper webserver for my dev tasks. Like aforementioned image versioning, regexps solve this easily.
As of hard-to-debug cases. When image pull fails, k8s displays the error message received from CRI's pull image. We can include full translated image name in our error messages.

How many images do you use for development? Why can't you explicitly list all of them without regexps?

If you insist that regexps are dangerous for end user, we can make them disabled by default and only enable them in dev/test installations via the configmap. Implementing them is really trivial and docs can be copypasted from this issue :)

One possibility where I may need multiple images e.g. someone struggling with Virtlet or DIND and asking for help, I can use Virtlet for testing efficiently if I can pre-pull all the images that I'll use. Listing them in the file and updating k8s object would add extra burden.

If we go with explicit listing I'll most likely have to write a script that takes directory listing, then generates yaml, then uses kubectl to apply it but it all will take more time than implementing regexps I'm afraid.

I really don't get it. What makes
- name: cirros
   url: http://<IP_ADDRESS>:8000/cirros
- name: ubuntu
   url: http://<IP_ADDRESS>:8000/ubuntu

be any harder than
- regex: .*
  url: http://<IP_ADDRESS>:8000/$0

?
In both cases you are going to create that new k8s object. Listing images explicitly can be hard if you use hundreds of them, but I don't think you do. And when it comes to that scale, simple regexps is not enough as well

how many images do you have in that directory? Don't know about you, bit most of the time I use couple of images and the names don't change a lot. I won't going to memorize the new object Kind and format, instead I'm going to copy-paste this yaml and put the new IP, which is going to change anyway even with regexps. So for me, listing images explicitly doesn't create any additional complexity. But I'm might be wrong and it's just my IMO. Feel free to ignore it

What I think about that:

we should match names first (regardless of matched regexes)
we should match regexes from top to bottom
regexes should be disabled by default and user have to enable them.

@pigmej as this discussion is actually mostly about #400, I've updated the description of that task.

Already done in #409


Create README.md in Greek

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Have not completed the translation. Will continue shortly, as well as translate the whole CONTRIBUTING.md guide.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


Host with multiple features

I'm sorry for opening so many "issues". This one is an idea only. No problem.
Wouldn't it be nice to be able to create a feature host that can work with many different features? This would make code cleaner I think.
To stick with your example I think that the SampleFeature should not include the onFabClicked event. This should be defined in a different feature like in a FabFeature so that the SampleFesture becomes a LifecycleFeature. Still it makes sense to be able to create a host that combines those two features.
What do you think about that?

You are right. I also identified this need.
But keep in mind, that featured is not an event bus. The main difference is that features define a lifecycle contract they expect to be fulfilled by feature host (or rather the class dispatching those events via feature host). In contrast, classes registered at an event bus make no implication about oder or presents of events. Both designs have pros and cons, but this is out of topic.
Currently, features can be inherited. It means you can already build feature inheritance you described. Each feature inheritance level will have its own feature hosts, which are also inherited. What is not implemented is the capability of reuse more generic features in inherited feature hosts. This is what I am working on in feature-lifecycle-inheritance branch. It should come soon.


Memory leaks when switching routes

// Edit: Seems like this has something to do with trying to use the .vue files only. Using components defined in js is working fine..
// Yeah, what I wasn't mentioning was, is that I was running this on windows. Project works when building on linux. Either webpack or vuerouter is messing it up on windows. More likely webpack.
Greetings. I have been aching my head with this for a while.
I got a lot of memory leaks in my bigger project, so I tried getting rid of all the extra libraries and come to conclusion that there has to be something wrong with either vue-router, vue itself or webpack. Vue-router  seems most likely candidate right now.
I'm running vue-router in vuejs-template's webpack-template, with hot-reload dev-build (Problem also applies to the distrubtion build). I am using .vue standalone files.
I have two separate routes. I have buttons in main vue instance for switching between the routes in addition to the router-view component.
I have some very basic rudimentary elements and components inside these views.
Using chrome's profiler, I use heap snapshots and filter these snapshots for "Vue*" classes.
Every time I switch between routes, new VueComponents and Vue$3 objects get added to the heap. Existing ones don't seem to be removed. These never seem to be garbage collected.
Any idea what's going on here?

Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or JSBin containing a set of reproducible steps that can lead to the behaviour you described.

Aye, excuse me for not providing one in initial post. I retract my statement that this only happens on windows. I don't know how I interpreted it working on linux yesterday, but it doesn't.
Since this could likely be something to do with my webpack build, although I haven't changed much, here's the the whole project
https://github.com/badpunman/memoryleakproject
Setup
git clone
npm install
npm run dev
Reproduction steps
Using chrome, go to localhost:8080
F12, Profiles-tab, take heap shot.
Filter result with 'Vue'.
There are 2 VueComponent objects and 7 Vue$3's.
Switch between the views by clicking on "Hello" and "home" buttons a couple of times.
Take another heapshot.
Filter result with 'vue'
There are loads more VueComponents and vue$3s.
These never get released.
This seems to be an issue with .vue single file components only that are referenced in src/router.js

Since this could likely be something to do with my webpack build, although I haven't changed much, here's the the whole project

In that case, can you make sure it is not by first trying to reproduce it on a jsfiddle, please?

In that case, can you make sure it is not by first trying to reproduce it on a jsfiddle, please?

Sorry, I'm not sure how to do that, considering issue concerns .vue single file components. I don't imagine jsfiddle supports webpack and vue-loader.

I meant to be sure it's not a vue-router problem, so without using vue files 😄
Why do you think it's a vue sfc issue?

Ah, yes, well, without using .vue files, instead using components defined in separate .js or in the same file as the src/router.js, it works. Providing jsfiddle of it would be rather pointless if everything is just working.
I just don't understand at all what the mechanism is at play here that makes it so different for .vue. I would presume the vue-router stores the vue-loader's output once and wouldn't spam multiple instances of everything when switching the views.

Ah, yes, well, without using .vue files, instead using components defined in separate .js or in the same file as the src/router.js, it works.

Ok! Sorry, I didn't understood you tested that already.
I'll give it a check

Aye, thanks for checking.
It seems like I can use .vue files without memory leaks as long as I don't assign them directly to the router. It's rather silly, but I guess I'll ensure my router views are declared as non .vue for now.

Sorry for the delay. I got a hard time looking at what you did. There was still a lot of code that didn't affect the issue. It seems to be related to an input having a v-model.
There are things you shouldn't be doing on your Vue files, like creating global components with Vue.component
I couldn't narrow down the issue yet to verify it. So I just wanted to keep you updated

It seems to be related to an input having a v-model.

Oh. That's strange. Seems to be so.

Seems to also trigger when adding @click event handler in a vue file that is a direct route component.
Since both v-model and @click add event handlers to the dom elements, I presume this might be a case of event handlers not being cleaned up from the dom elements upon removal. No idea what the behind the scene mechanisms are for Vue or Vue-router for disposing of components though.

Did you manage to boil down the repro? I'll gladly look at an updated version

Nah, sorry. Been a tad busy as of late. Not sure how much more I can really boil it down.

Results of more digging in to the problem:
It seems like when switching route, the previous Dom-node is retained in vm.$options._refElm. If the dom has those event listeners in the vue components, vue components are then also retained.
Now, I have no insight in to what _refElm is actually used for, or how to fix this.

Yeah, there can be a leak if events are not cleaned when reusing elements

Well, here's a concise example.
Leaking happens when toggling between Foo and Bar router views. Both of these are simple input elements with v-model watchers.
The state cleans up when moving in to Dummy route, with no listeners in template.
https://github.com/badpunman/memoryleakproject/blob/master/src/router.js
Here's a look a the retainers. Deepest Vuecomponent is the current route's component. It holds reference to earlier component's Dom via $options._refElm, which has listeners in the previous vuecomponent, and then the cycle repeats for further components that have been switched in router.

@yyx990803 That's probably something you have to look at. Might also be related to core rather than router.

Was fixed in Vue 2.2 core in #4990

I seem to still be having this same problem in 2.2.3, 2.2.4 and 2.2.5. It seems to be related to adding an @click or v-model, as well as related to vm.$options._refElm.
I've been trying to fix the memory leak for a few days now but having no luck. This is a real problem since the leak seems to carry over into the server-side rendering, increasing the memory use of the Node app until it slows to a crawl.

@jazoom please use a separate issue with repro and more information.

I'm trying to create a minimal reproduction for you but it's not easy to pin down where the actual problem is since it happens only under certain circumstances. I haven't yet worked out the full pattern.


Add EFCore.TimeTraveler to the list of EF Core Extensions

Issue #2000.  Followup of #1864.
Add EFCore.TimeTraveler to the list of EF Core Extensions as well as expand on differences between EFCore.TimeTraveler and EfCoreTemporalTable.
I didn't want to be too verbose here, so I left these details out:

EfCoreTemporalTable exposes the full power of SQL Server Temporal Table history by supporting all available types of temporal queries.
EFCore.TimeTraveler focuses only on querying for a point in time with FOR SYSTEM_TIME AS OF
With EfCoreTemporalTable you query multiple entities from history using JOIN syntax.
With EFCore.TimeTraveler you may use .Include(), '.ThenInclude()', and navigation properties to access an entire object graph persisted from the temporal history of multiple tables.

Thanks @bbrandt!


added convenience property to access previous route

Adds a convenience property called previous to access the previous route (last stored history entry).

Travis doesn't like your changes. Please make sure everything works fine with Travis.

Fixed. Sorry, I believe it was late when I submitted this and didn't do a great job :)


cordova-android 0.9.0

This step adds support for cordova-based Android. It requires vgaidarji/docker-android-cordova docker image.

Thanks so much, we'll do the review on this step on Monday, ASAP! (The process is always a bit longer for a brand new step).

Sorry, busy day. We'll come back tomorrow - so far we think that the Step can be accepted after the suggested changes, and the docker image should be transferred to https://github.com/bitrise-docker or should be merged into the android image (we're still discussing whether we should merge it or not).

It's ok, no hurry anyway, thank you ;)
I've implemented suggested changes. :rocket:

Perfect, thanks for the changes! One last request, if you have the time, could you please squash the commits into one commit? Other than that, everything looks fine ;)

Yes, sure, good point :)
I'll do it once I reach the home in the evening.

Squashed :dancer:

Merged & accepted 😎
Thanks for the contribution!
We'll definitely contact you when we (finally) decide what we should do with the docker image 😉

wohooo, thanks :tada:

After some discussion we think that these pre-installed tools would be great to have in the default Android image. The size difference is not that significant and it'd make it much easier to setup a new project which requires Cordova.
Would you be open to add the required tools to the base & android docker images, and create a pull request? If you don't have the time that's not an issue either, we'll do that a bit later then.

Let's do in this way: who will have time first, will create this PR. Let's the competition begin :dancers:
But to be honest, I'll lose to you, as I'm working on a blog and "Cordova Android" project setup guide :)

Sounds fantastic! All right, thank you, I'll create a ticket for ourself, and let the battle begin! 😂

Please check "How to build Cordova-based Android project on bitrise.io", and if it fits (I hope it does), than feel free to add to bitrise blog ;)


backup still using cache

Hi
I'm using the version of nocache that comes with Ubuntu.
I am making backup of my home directory using tar, something like
nocache tar -zcvp /home -f /mnt/usbhdd/backup.tgz
but when I run
cachestats /mnt/usbhdd/backup.tgz
while running the backup command, it still reports about 3GB of pages in cache.
My understanding was that the used cache should be much smaller. Is there any way to prevent tar and gzip from trashing the cache of the system during backup?

nocache will only uncache-on-close, i.e. when the large backup.tgz file has been fully written and the last writer closes their file descriptor. The problem is that your backup has only a single file. There is really nothing else that nocache can do in its current form.


Login page doesn't work

Needs to redirect to the home page after having logged in

The login page is now able to work


[GraphEdit] Fix port hotzones at zoom levels other than 100%

Fixes #72757.
Reverts #78556. (this worked as a hotfix for certain zoom levels, but the recursive children check was still broken)
With children rects visualized (these were not scaled correctly before, causing the clickable children check to fail when it shouldn't):

Thanks!


[graphiql] Syntax highlighting breaks with .graphql as a function

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When using amplify's graphql api capabilities, the syntax highlighting for anything past the graphql function stops working properly. See screenshot. You can see where the if after .graphql() is yellow instead of the purple like previous as well as the const following that if is white instead of navy blue.

Expected Behavior
This should affect graphql syntax, but not affect other highlighting after using a .graphql() function.
Steps To Reproduce
This is in VS Code Insiders 1.96.0 and I'm also using
Environment

GraphiQL Version: N/A
OS: Windows 11
Browser: N/A
Bundler: N/A
react Version: 18.2.0
graphql Version: N/A
aws-amplify Version: 6.6.7

Anything else?
No response

Happening to me too, I tracked down the commit
v1.3.4 works
v.1.3.5 doesn't
https://github.com/graphql/graphiql/commit/e9fc21ab5f403a3e26cec555b29e5fb9db436838


fix(@angular/cli): logic which determines which temp version of the CLI is to be download during ng update

Previously, when using an older version of the Angular CLI, during ng update, we download the temporary latest version to run the update. The ensured that when running that the runner used to run the update contains the latest bug fixes and improvements.
This however, can be problematic in some cases. Such as when there are API breaking changes, when running a relatively old schematic with the latest CLI can cause runtime issues, especially since those schematics were never meant to be executed on a CLI X major versions in the future.
With this change, we improve the logic to determine which version of the Angular CLI should be used to run the update.
Below is a summarization of this.

When using the --next command line argument, the @next version of the CLI will be used to run the update.
When updating an @angular/ or @nguniversal/ package, the target version will be used to run the update. Example: ng update @angular/core@12,  the update will run on most recent patch version of @angular/cli of that major version @12.2.6.
When updating an @angular/ or @nguniversal/ and no target version is specified. Example: ng update @angular/core the update will run on most latest version of the @angular/cli.
When updating a third-party package, the most recent patch version of the installed @angular/cli will be used to run the update. Example if 13.0.0 is installed and 13.1.1 is available on NPM, the latter will be used.

Does ng update @angular/core go to latest or the next major? If I'm on v10 and run this, it should go to v11 right, since we only allow one major at a time? In that scenario, wouldn't we want to upgrade with the latest patch of the destination major (in this case, @angular/cli@11)?

When no version is specified the update will use the @latest tag. We can improve this but, it might be confusing that updating an angular package will update to the next major version while other packages will update to latest.

Note: once merged, I will create PRs to backport this change to all LTS versions of the CLI.

When no version is specified the update will use the @latest tag. We can improve this but, it might be confusing that updating an angular package will update to the next major version while other packages will update to latest.

Hmm, I'm a bit torn here. npm install @angular/core means @angular/core@latest, so I wouldn't want to diverge from that. It would also be weird for @angular/* packages to be special-cased like you mentioned. On the other hand running with the latest CLI means that it needs to support migrating from more than the previous version, which is what we're hoping to avoid.
I just tried this with today's logic to make sure I understood and running ng update @angular/core @angular/cli on a v10 project fails because it tries to update to v13, which isn't allowed (though the error message doesn't actually say that and we should probably be more clear that it tried to update to @latest).
$ ng update @angular/core @angular/cli
Using package manager: 'npm'
Collecting installed dependencies...
Found 29 dependencies.
Fetching dependency metadata from registry...
Updating multiple major versions of '@angular/core' at once is not supported. Please migrate each major version individually.
Run 'ng update @angular/core@11' in your workspace directory to update to latest '11.x' version of '@angular/core'.

For more information about the update process, see https://update.angular.io/?v=10.0-11.0

So I guess the decision of which CLI runner to use doesn't really matter since the update will fail anyways if @latest is not the next major version. Based on that, I'm ok with using the latest CLI runner as you currently have here, but this is maybe something we should look into when we eventually revamp ng update. I would love to see running ng update just go to the next major with no fuss, and this is something we'd have to tackle more comprehensively to make that happen safely.


Support List and LargeList in Row format (#3159)

Which issue does this PR close?

Part of #3159
Rationale for this change
The longer term goal is to make the Row Format support enough types to use in DataFusion so we can use it for a unified GroupBy operation

What changes are included in this PR?

Add support for encoding/decoding lists from the row format
Are there any user-facing changes?

I can feel DataFusion grouping getting faster.....


Update the default queue name to match what's provisioned in a new org

By default, a new Buildkite org will have one cluster called Default, with a queue named default-queue. This PR updates the elastic ci stack default to match so that we get agents registered with the default queue out of the box.
This might be a breaking change for any orgs that have a queue named default that deploy the elastic stack without supplying a value for BuildkiteQueue.

related: https://linear.app/buildkite/issue/PIP-1198/default-queue-key-doesnt-match-queue-key-in-elastic-stack-default and https://linear.app/buildkite/issue/PIP-1209/the-default-queue-for-elastic-ci-aws-doesnt-match-the-default-queue-we

This seems fine to me, but I'm curious how this PR compares with changing the default cluster's default queue name to be default instead?


Please give Greg Wilson access to this repo

@gvwilson doesn't have permission to push/merge to this repo.

done!


feat(tests): new e2e tests [8/8]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
This add new libsinsp e2e tests for the container runtimes.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: therealbobo
Once this PR has been reviewed and has the lgtm label, please assign lucaguerra for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Given that #1650 is being tracked for 0.19, let's move this too:
/milestone 0.19.0

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: therealbobo
Once this PR has been reviewed and has the lgtm label, please assign lucaguerra for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.19.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, therealbobo
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold


Add broadcast target address to tplink

Home Assistant release with the issue:

0.102.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Integration:

tplink
Description of problem:
The library defaults to a target broadcast of <IP_ADDRESS>. The problem is that this is only going out the default route. In a multi-homed environment, the broadcast address does not go to all interfaces. This should probably be a list of broadcast addresses in the upstream library as the tplink component will only be able to support devices on a single interface regardless of how the address is set.
https://github.com/GadgetReactor/pyHS100/blob/59424d2738866a2bf88f8e256ece2baa06f0b024/pyHS100/discover.py#L46
My use-case here is I have a wired network and a segmented wireless network connected to my home assistant device.
This issue can be seen in a multi-homed environment by running the following:
$ ip route show to match <IP_ADDRESS>

A simple solution would be allowing the user to specify the target broadcast address sent to Discover.discover() in the pyHS100 library.
https://github.com/home-assistant/home-assistant/blob/ab22c617646387af18f088aaf26aba348d606bce/homeassistant/components/tplink/common.py#L62
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
tplink:
  discovery: true

Traceback (if applicable):

Additional information:

Duplicate of #23218


docker-compose fails to build web service

Expected behavior:
Running docker-compose up -d will build and bring up the containers
Actual behavior:
Running docker-compose up -d fails to build the web service. The image build fails at Step 5/14  RUN cd /tmp && yarn install --silent. The last error lines shown before the process exits are
warning pouchdb-load > pouchdb-ajax > request ><EMAIL_ADDRESS>ReDoS
vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
warning pouchdb-load > pouchdb-ajax > request ><EMAIL_ADDRESS>Use uuid module instead

error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=8". Got "6.17.1"
error Found incompatible module

Steps to reproduce:

clone the hospitalrun-frontend repository
cd hospitalrun-frontend
docker-compose up -d

This is a real issue, did anybody fix it somehow ?

Also experiencing this
`Step 3/14 : RUN yarn global add ember-cli@latest
---> Running in fb3d26c888e2
yarn global v1.15.2
[1/4] Resolving packages...
warning ember-cli > broccoli-babel-transpiler ><EMAIL_ADDRESS>🚨 As of Babel 7.4.0, this
package has been deprecated in favor of directly
including core-js/stable (to polyfill ECMAScript
features) and regenerator-runtime/runtime
(needed to use transpiled generator functions):

import "core-js/stable";
import "regenerator-runtime/runtime";
[2/4] Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "8.* || >= 10.*". Got "6.17.1"
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
ERROR: Service 'web' failed to build: The command '/bin/sh -c yarn global add ember-cli@latest' returned a non-zero code: 1`

+1
Same at this end:
# docker-compose up
Building web
Step 1/14 : FROM node:6-alpine
 ---> dfc29bfa7d41
Step 2/14 : RUN apk update && apk add   bash   curl   g++   git   make   python   sudo   wget
 ---> Using cache
 ---> 5c2178d25cfc
Step 3/14 : RUN yarn global add ember-cli@latest
 ---> Running in eeafdcdceb9b
ERROR: Service 'web' failed to build: The command '/bin/sh -c yarn global add ember-cli@latest' returned a non-zero code: 139

Hi @junelsolis!
We're now working on a new major version (2.0) of HospitalRun. Sadly, your request can't be resolved, so we're forced to close this issue.


[Question]:comparison of DistilBERT

I was checking the memory consumption of RoBERTa and DistilBERT. I found there is no significant change in memory usage. Although Inference time is around 1sec for DistilBERT and for RoBERTa is 2sec.
Memory usage on CPU:
Port 9000: DistilBERT
Port 9002: RoBERTa

Have you seen any significant change in memory usage @kaushaltrivedi

Here are my findings:  DistilBERT has 33% less GPU memory footprint than RoBERTa and trains much faster too.

I was asking about inference time usage?

Ok. I haven’t tried that out yet.


Implement date/time histogram widget

Waypoint for #786, implementing the time-series widget for a histogram with a date column.

An example is created at examples/time-widget.html, which requires the vis to be setup with a layer that has a date column for the widget to load as expected.
As agreed after talking with @urbanphes, I've removed the controls for now, will be added/implemented later for a torque-layer.
Refactored the widget-views creation, to a factory that allow defining arbitrary rules of what view to create for a certain context, necessary to differentiate widget of type histogram here. cc @alonsogarciapablo since we discussed it offline

@javierarce can you review?

:ok_hand: for me


utf8 decoding bug

Out of interest, I noted a bug decoding a flac file from Multilingual Librispeech (French). Previous files ran fine, I think the code I ran is up-to-date. I'm afraid github won't let me attach a flac file.
File "WhisperEval/lang/fr/translate/fails.py", line 17, in main
segments, info = model.transcribe("audio/7423/8734/7423_8734_000055.flac", beam_size=1)
File "WhisperEval/opt/faster-whisper-master/faster_whisper/transcribe.py", line 193, in transcribe
audio = decode_audio(
File "WhisperEval/opt/faster-whisper-master/faster_whisper/audio.py", line 37, in decode_audio
with av.open(input_file) as container:
File "av/container/core.pyx", line 401, in av.container.core.open
File "av/container/input.pyx", line 86, in av.container.input.InputContainer.cinit
File "av/utils.pyx", line 26, in av.utils.avdict_to_dict
File "av/utils.pyx", line 14, in av.utils._decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc9 in position 0: invalid continuation byte
Minimal code fragment:
model_path = "WhisperEval/opt/faster_whisper_models/whisper-large-v2-ct2-q_int8"
# Run on GPU
model = WhisperModel(model_path, device="cuda")
segments, info = model.transcribe("audio/7423/8734/7423_8734_000055.flac", beam_size=1)

Yes, the problematic files (4 of 20) run through with the patch to ignore meta data errors. It wasn't an issue for me, just thought I'd mention it since the original code didn't flag any issues with those files. I'll close.


About the json file

Hello author, thanks for your work! I have a little question to ask you:
What is the json file here and how can I get it?
https://github.com/akanazawa/motion_reconstruction/blob/6ff7fc867e9e185d547ada11713a60fbf3caa902/run_openpose.py#LL116C4-L116C4

ok, I understand, it should be an error caused by my openpose not outputting the json file correctly. I would like to ask what version of openpose is used here

are you using the openpose provided in the repo? see README it's a finetuned model.
At anycase, this is quite old, and I don't have access to it anymore that Idk which version of openpose it was, I highly suggest ppl to checkout more recent methods like https://shubham-goel.github.io/4dhumans/ and https://github.com/vye16/slahmr for this task.

how wrong is it, is the scale and translation off? That may have to be adjusted by hand, bc you're transforming this human from video (in its on coordinate frame) to your simulator. Ppl hav used that hmr2bvh code so I think you can make it work. Our recent work like SLAHMR for ex gets rid of this this problem of having to figure out the scale & global translation of ppl unlike this work. Good luck!

There is an error in the position of the root. After I use hmr2bvh, the position of the root in each frame is hundreds of values, not at the origin like the bvh data in your link. Well, maybe I will manually adjust it for convenience at this stage, and I will follow up on your latest work later! Thanks for your reply and good luck!

hmm that's a bit sus, IIRC the released bvh data is the output of this code
i didn't manually change it or anything. Best of luck!
A
On Wed, Jun 28, 2023 at 7:45 PM Peter_Stacy @.***>
wrote:

There is an error in the position of the root. After I use hmr2bvh, the
position of the root in each frame is hundreds of values, not at the origin
like the bvh data in your link. Well, maybe I will manually adjust it for
convenience at this stage, and I will follow up on your latest work later!
Thanks for your reply and good luck!
—
Reply to this email directly, view it on GitHub
https://github.com/akanazawa/motion_reconstruction/issues/19#issuecomment-1612358485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHBXWEWYN2BHH74IQKOWNTXNTT25ANCNFSM6AAAAAAZMX4ZIQ
.
You are receiving this because you commented.Message ID:
@.***>

--
Angjoo Kanazawa
Assistant Professor
Department of Electrical Engineering and Computer Sciences
University of California, Berkeley
https://people.eecs.berkeley.edu/~kanazawa/
She/Her


version

Is the latest release here the same vers as available in UNRAID community apps?

I really don't understand what you mean with that...?
Can you please specify what you mean exactly?

I really don't understand what you mean with that...? Can you please be a bit more precise what you mean exactly? On what Unraid version are you, is anything not working?

I am on 6.11.5 in UNRAID and I installed the it87 plugin (02/11/2022) via community apps plugin. Is your it87 driver in this repo newer and if so how do we install it?

This is the repository for the plugin that you install through the CA App.
No, there is no newer driver available.
Please don't get confused by the plugin version, the plugin will always update itself and the driver.

This is the repository for the plugin that you install through the CA App. No, there is no newer driver available.
Please don't get confused by the plugin version, the plugin will always update itself and the driver.

thank you for clearing this up for me.


add proxy support

@mamantoha Thanks, and sorry for late response. it seems well-tested, I'll merge it.


[Feature Request]: Docker images with both runtime and launch environments

What would you like to happen?
Container environments describe a way to create custom docker images for runtime configuration, but the launch step example still needs access to the source file.
Could you please document a setup where the docker image contains both runtime and launch configuration so that a docker run invocation is enough to launch the job with the dependencies too.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[X] Component: Website
[ ] Component: Infrastructure
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

Have you checked https://cloud.google.com/dataflow/docs/guides/using-custom-containers? or https://github.com/GoogleCloudPlatform/python-docs-samples/tree/main/dataflow/flex-templates/pipeline_with_dependencies

I have. It works, but is not the most convenient as along side a docker image, it also requires maintaining a file in google cloud storage. So, it is not as simple as building a docker image and running it. It would have been nicer if beam supported a better way natively.


Robert Longson: Watch drashishsaini.com

Robert Longson requests the watch of the watch_keyword drashishsaini\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

drashishsaini\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Question: Why this action needed?

When I want to build, test, or bundle I just run ./gradlew task.
Why do i need to download java?

if you use github hosted runner, (aka runs-on: ubunut-latest), it has almost everything installed, check in details https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#android
however, on self-hosted runner, we may need this setp-android to have the android sdk setup to make build work

It's true, if you're using self-hosted runner, so you need to install android on runner or use this action.


Updated emoji db, fixed emoji categories and fixed a crash in emojimanager parser

Updated emoji db, fixed emoji categories and fixed a crash in emojimanager parser
There are new skin variations that are not supported and i had to clue how to implement them. Help?

Thanks for the PR! I'm working on the library right now and I have the same fixes on my PR so I will close this.


[HTML5] Properly set canvas size during setup.

It used to be updated before the first iteration, causing the window/viewport size values to be incorrect during the initialization phase (e.g. during the first _ready notification).
Fixes #46843

Cherry-picked for 3.2.4.


Fix a time conversion error

Previously the offset was subtracted from the time, before the date and
time were used to create a NaiveDateTime object. Then after the
NaiveDateTime object was created the offset was "added" again by means of
the from_utc method.
The problem with this approach is that if the offset is greater the
the time, you should actually go back a day in time. But since this action
was only done on the time, the date was not changed. So when the offset
was "added" again, the clock moved forward and added an additional day.
For example this object:
   DateTimeOffset {                                                                                │[I] ao                                                                                10:28:20
        datetime2: DateTime2 {                                                                                │➜ ~/code/heineken/terraform-aws-ft-brmx/functions aws:(be001oc-cb-datalayer) git:(master) ✗
            date: Date(                                                                                │➜ ~/code/heineken/terraform-aws-ft-brmx/functions aws:(be001oc-cb-datalayer) git:(master) ✗
                737766,                                                                                │[I] ssh -L 1433:<IP_ADDRESS>:1433 mi-0fe1490a4499e13df                                      (1.661s) 10:28:43
            ),                                                                                │Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-54-generic x86_64)
            time: Time {                                                                                │
                increments:<PHONE_NUMBER>,                                                                                │ * Documentation:  https://help.ubuntu.com
                scale: 7,                                                                                │ * Management:     https://landscape.canonical.com
            },                                                                                │ * Support:        https://ubuntu.com/advantage
        },                                                                                │
        offset: 60,                                                                                │  System information as of Wed Dec  9 09:30:55 UTC 2020
    }

Was parsed to 2020-12-09 00:15:31 while it should be 2020-12-08 00:15:31
By first creating the NaiveDateTime object and the subtracting the
offset, it actually updates (if needed) the date as well preventing this
kind of error.

Oh dear! Thank you for this, it's time to cut a new release it seems!

Thanks! And yes, a new release with this one would be nice 😊

https://github.com/prisma/tiberius/blob/master/CHANGELOG.md

Super nice, thanks!


Issues when using the commands

args commands and other components off discord.js errors and unhandledPromiseRegectionWarning. This issues must be fixed otherwise it will be a big problem for the bot.

List of issues:
cannot read property send of undefined
cannot read property members of undefined
args.join is not a function


Added Token Allies

Line.141: Business Tokenization Platform and Marketplace

I´m not familiar in what should I name the patch, is this ok? If not please let me know


Move aya-node install to ansible

In order to provide more value to the community eg people that don't use packer or have a hosting provider that support golden images, move the aya-node installation to an ansible role and playbook.

Work completed


Consider beam_services option when determining the expansion service type

Cherry-picks https://github.com/apache/beam/pull/27345 to 2.49.0 release branch.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @Abacn


Search doesn't work on Termux

Describe the bug
Searching for manga always returns no results, even though the device is connected to the Internet.

Running mangal doctor yields a very weird result as well:

(I have the latest version, installed with curl -L -o mangal https://github.com/metafates/mangal/releases/download/v2.2.0/mangal-android-arm64
Reproduction steps

Download mangal with curl -L -o mangal https://github.com/metafates/mangal/releases/download/v2.2.0/mangal-android-arm64
Run chmod u+x mangal to make execution possible.
Run ./mangal config init
./mangal inline -q "berserk" returns no results as well as any other search query

Expected behavior
Mangal should display a list of mangas to read
Additional context
I'm running Termux v0.118.0 from F-droid on a OnePlus 7 Pro running Android 11
Edit: The same thing happens on the version that can be downloaded from Github
Operating System
Linux
Checks

[x] I've used mangal doctor and it didn't help

Edit: fixed some typos

That's very weird. Unfortunately, I don't have access to any android right not, but I'll see if I can setup an emulator

I tested it on emulators with Android 8 and 10 as well as on another phone running Android 9 with the same results. I also looked into the logcat to see if there are any errors showing up while running Mangal but there aren't any. I doubt that this will help, but this is all I found:
2022-07-09 16:59:14.755 1580-1672/? I/OHPD: [BgDetect]forked proc mangal(pid : 15734 uid: 10491) 6220 during 300027
2022-07-09 17:16:48.020 1580-1672/? I/OHPD: [BgDetect]forked proc mangal(pid : 15734 uid: 10491) 5880 during 300012
2022-07-09 17:57:39.702 1580-1672/? I/OHPD: [BgDetect]forked proc mangal(pid : 15734 uid: 10491) 5990 during 300064
2022-07-09 17:59:00.055 1580-1672/? I/OHPD: [BgDetect]forked proc mangal(pid : 15734 uid: 10491) 6070 during 300130
2022-07-09 18:00:20.458 9988-9988/? W/bash: type=1400 audit(0.0:108731): avc: granted { execute } for name="mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:00:20.458 9988-9988/? W/bash: type=1400 audit(0.0:108732): avc: granted { execute } for name="mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:00:20.458 9988-9988/? W/bash: type=1400 audit(0.0:108733): avc: granted { execute_no_trans } for path="/data/data/com.termux/files/home/Git/mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:00:20.468 9988-9988/? W/mangal: type=1400 audit(0.0:108734): avc: granted { execute } for path="/data/data/com.termux/files/home/Git/mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:00:20.478 9988-9988/? W/mangal: type=1400 audit(0.0:108735): avc: granted { execute } for path="/data/data/com.termux/files/usr/lib/libtermux-exec.so" dev="dm-3" ino=12093171 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:01:45.768 10043-10043/? W/bash: type=1400 audit(0.0:108736): avc: granted { execute } for name="mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:01:45.768 10043-10043/? W/bash: type=1400 audit(0.0:108737): avc: granted { execute } for name="mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:01:45.768 10043-10043/? W/bash: type=1400 audit(0.0:108738): avc: granted { execute_no_trans } for path="/data/data/com.termux/files/home/Git/mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:01:45.768 10043-10043/? W/mangal: type=1400 audit(0.0:108739): avc: granted { execute } for path="/data/data/com.termux/files/home/Git/mangal" dev="dm-3" ino=11830961 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api
2022-07-09 18:01:45.778 10043-10043/? W/mangal: type=1400 audit(0.0:108740): avc: granted { execute } for path="/data/data/com.termux/files/usr/lib/libtermux-exec.so" dev="dm-3" ino=12093171 scontext=u:r:untrusted_app_27:s0:c235,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c235,c257,c512,c768 tclass=file app=com.termux.api

I'm starting to think that it might be a problem with Termux and not with Mangal.

Thanks for the logs, I'll look into them! I had some troubles installing suitable android emulator because m1 macs has some troubles with it so I don't think I'll be able to test it soon, I'll try tho. But keep in mind that android support is not planned, so even if this will be fixed I don't know what else could appear

Closing, since android is not a supported platform. Maybe in the future!


Clean up inconsistencies in the directory where the tests are run from

Fixes #374.
The idea to fix the issue is to alway cd in the submitting user $HOME directory, even if the submitting user is root. I think this is the correct approach as this is closer to a real case setup. At one point, we might want to add a non root submit user to other CI. HTCondor already has one like PBS.

This ended up (again) wit far more changes than I thought at first.
The reason being, on top of launching test from the corresponding docker user home, I also added a shared space in all CIs (but LocalCluster) to be able to launch some tests (for the time being, Security related tests).
So now, except the fact that some CIs are running with non privileged users inside Docker (PBS and HTCondor) and others are not, the setup from each CI is similar.


Do we need a "web.config" in the project?

@Accuraty, I noticed you made updates to the  ATSP web.config file to make some settings up to date with Accuraty standards. Is this a file that would make since in this starter kit?

Its hard to say, we can't really because DNN supplies that and it changes over time. What we really need is - at deploy, or at the point the project is created - to merge in some settings updates that are Accuraty-specific. It is why I asked recently about using JS to update XML.

Ok cool. This is referencing https://github.com/Accuraty/ATSP/issues/13#issuecomment-473730648.

web.config is the default file used by DNN, it is literally the ASP.NET configuration for the site. My adding web-env.config is sorta unrelated and has nothing to do with DNN.


Exclude requested packages/dirs from being mutated

This feature will allow a user to exclude some directories from being mutated.
We can pass a flag with a list of dirs to be excluded by gremlins unleash
gremlin unleash --exclude-dirs="./dir1,./dir2,./dir3"

Config file:
unleash:
  exclude-dirs:
  - "./dir1"
  - "./dir2"
  - "./dir3"

What do you think about that?

I'm not sure if it is better to exclude dirs or packages...
Also, we have to be careful on how it plays with the recently added --coverpkg flag.

Regarding this feature, I was thinking of something more flexible.
To exclude specific mutators for paths:
excludes:
  - path: <path regex>
    mutators:
      - mutator1
      - mutator2

In this case we can have a list of specific path or regex matching paths. For each, we can have a specific list of mutators to match (if not specified will be all mutators).
Same concept can be applied to packages:
excludes:
  - package: <package regex>
    mutators:
      - mutator1
      - mutator2

@k3rn31 Sounds good to me :smile:

Very expecting feature!

Done in PR #228


How to override type?

We have a model in the backend that we refer to as a different name in our public API. We need to override the type returned but haven't found a way to do this yet.
I tried adding def self._type (as I noticed that's where it was grabbing type from) to my base model class as well as the resource serializer but that didn't change the response.
Any help would be appreciated.

https://github.com/cerebris/jsonapi-resources#model-name should do it

Thanks. I tried that and it didn't work. Here's the setup:
project table
project.rb defining Project class
ProjectsController
ProjectResource
I need the type in the json responses for projects to be 'study'.
# still returns type as 'project'
class Api::V2::ProjectResource < JSONAPI::Resource
  model_name 'Study', add_model_hint: false
end

I was able to make it work by changing resource and controller name to the public API name, and using model name to point the public-named resource to the correct backend model.
Not sure if this is a good solution since it's not conventional Rails where the controller name be the same as the model name.

In JR the convention is for the controller to match the resource name. The resource acts as an intermediate layer mapping to the model so the naming disparity is expected.

Alright cool. Thanks @thibaudgg !

@bpourriahi not sure why, but you're welcome anyway! :smile:

Heh. That may or may not been a 'typo'. Thank you @lgebhardt.

@lgebhardt I'm using namespaced STI and I think JR type convention doesn't match this use case.
As explained in http://jsonapi.org/format/#document-resource-objects:

The type member is used to describe resource objects that share common attributes and relationships.

I'm working on an infrastructure management app that includes a lot of models that are namespaced to avoid any collision. For example, my model DNS::Zone will be typed as zones by JR. But I could have another kind of zone in the future.
IMHO, JR type should actually match the URL namespace, which in my case is dns/zones.
This is a little different with namespaced STI like my CDN::Purge which is declined to CDN::Purge::Custom, CDN::Purge::Full and CDN::Purge::Collection that are respectively typed customs, fulls and collections which  have no sense.
My first thought was to rename my models like CDN::Purge::CustomPurge, which would be typed custom_purges.
This would be fine except that the cdn namespace is still missing, and that my controller and route are still purges.
That means that the type should actually not match the controller name, but the model name, given the resource attributes could vary in the same controller.
In any case, the type field should be customizable, even if convention is always better.

Is this something which is being considered? I've tried the workarounds above and had no luck.
We are in a similar situation where we have multiple services which might share resource names (e.g. AssetFile) which will be different across the services. Ideally we want to namespace the types to match the URL namespace e.g. something like this:
model_name "ExampleServiceName::AssetFile"

def type
  "example_service_name/asset_files"
end

Even better would be if we can define the prefix globally across each app by defining this in a base class, or ideally have JR pick the namespacing up from the namespaced model_name in the above example.

I'm also trying to figure this out.
I have STI models Events::Applied, Events::Interview which inherit from base model Event. I'd like to use a common controller/endpoint api/v1/events but have the type as events/applieds or events/interview (similar model names to @gauthier-delacroix which leads to weird pluralization ("applieds"). In hindsight I'd have named the models Events::AppliedEvent etc.
Namespaces type is important to me since my frontend Ember app has a similar folder structure with Event subclasses under an events directory. With a type of events/applied, Ember resolver will look under models/events/applied.js rather than models/applied.js

Did this by using jsonapi-utils by explicitly defining the actions in the controllers so you know exactly whats going on.
# Specify a particular HTTP status code
jsonapi_render json: new_user, status: :created

# Forcing a different resource
jsonapi_render json: User.all, options: { resource: V2::UserResource }

# Using a specific count
jsonapi_render json: User.some_weird_scope, options: { count: User.some_weird_scope_count }

# Hash rendering
jsonapi_render json: { data: { id: 1, first_name: 'Tiago' } }, options: { model: User }

# Collection of Hashes rendering
jsonapi_render json: { data: [{ id: 1, first_name: 'Tiago' }, { id: 2, first_name: 'Doug' }] }, options: { model: User }

2022 and still the same problem: I have versioned models (Api::V1::ModelName, Api::V2::ModelName) and both get typed as 'model-name'. So, if the server gets such a serialiazed model instance and wants to deserialize it, how is it supposed to know the correct model version?
I have tracked this issue to the following code section (in 0.10.7):
#<EMAIL_ADDRESS>lines 445-446
type = subclass.name.demodulize.sub(/Resource$/, '').underscore
subclass._type = type.pluralize.to_sym

So this is where the class name gets demodulized and then, in
#<EMAIL_ADDRESS>on line 172
obj_hash['type'] = format_key(source.class._type.to_s)

the type gets set to the value of _type.to_s which has been set previously. At the moment I cannot see any built-in option for customizing or overriding this hard-coded demodularization. I have therefore modified my local files as follows:
#<EMAIL_ADDRESS>lines 172-173
# obj_hash['type'] = format_key(source.class._type.to_s)
obj_hash['type'] = source.class.to_s

With this, the _type attibute of a resource still gets set to a demodulized value but the serializer now uses the full modularized class name:
reload! JSONAPI::ResourceSerializer.new(Api::V2::ClimateDatumResource).object_hash(Api::V2::ClimateDatumResource.new(Api::V2::ClimateDatum.first, nil), nil)

Now yields:
{"id"=>"1",
 "type"=>"Api::V2::ClimateDatumResource",
 "attributes"=>{"ambient-temperature"=>20.0, "ambient-humidity"=>50.0, "atmospheric-pressure"=>952.0,
 "room-no"=>438, "position"=>"windows", "measured-at"=>"2022-07-22T14:31:20.884Z"},
 "meta"=>{:received_at=>Fri, 22 Jul 2022 14:38:11.107411000 UTC +00:00}}

Et voilà! Again, this is not really configurable and just as hard coded as the previous solution. However, at the moment it suits my needs. In order to make this portable to other machines, I have forked the master branch, patched the code with a commit and am now installing directly from there.
Finally: Thanks to @lgebhardt for this great piece of software!


Resources using JSON fields for titles, should use title capitalization instead

All of the resources are showing the JSON field names for titles, instead the titles should use title capitalization instead.  So formFactor should become Form Factor.

I'm working on this.

Going to leave this open until we get some tests to cover the Resource class.

Complete with units

Need to do the same for HipChat.  Also fix alert.js to do it as well.


Speeding up training by multi GPUs ?

Hi, have you tried training on multi GPUs?
I struggled with the author's codes:
https://nol.cs.nctu.edu.tw:234/open-source/TrackNetv2
but even after training for 10 epochs, the model can not predict any positive example.
        with tf.device('/cpu:0'):
       ┊   model=TrackNet(HEIGHT, WIDTH)
       model_on_gpus = multi_gpu_model(model, gpus=len(gpu_list))

And the new pytorch version seems can only train on single gpu.
Do you know the reason ?
The author has not reply me and my time has limited to finish my project, so I look forward to your reply.
Thx!

Sorry I haven't tried before with multi-gpu training.

https://nol.cs.nctu.edu.tw:234/open-source/TrackNetv2

this project is only version about tensorflow, no pythorch. and I think there are  too some questions for it to run this project.

The official pytorch version can not train with mutil GPUs, either

do u have any Contact information that i can talk with u, like qq?

<EMAIL_ADDRESS>