npm start failed with the following error - NPM and Nodejs are latest versions.

When I tried executing npm start it failed with the following error. NPM and Nodejs are latest versions. I am trying this on Ubuntu 16.04 64-bit.

<EMAIL_ADDRESS>start /home/amar/Desktop/Gaze Detector/TurkerGaze-master
node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js

sh: 1: node: not found
npm ERR! Linux 4.4.0-21-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the TurkerGaze package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs TurkerGaze
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls TurkerGaze
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/amar/Desktop/Gaze Detector/TurkerGaze-master/npm-debug.log
Can somebody help me with this

Did you install webpack with npm?

Yes I did. Sorry for the late response.

Can you explain what you're doing here?
node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js
You can run
"npm start"
at the root directory of the git repo and it should start node without errors.

Now when I am trying to execute npm-install, I get the following messages.
amarnair@CECSTahdfi:/var/www/TurkerGaze-master$ npm start

<EMAIL_ADDRESS>start /var/www/TurkerGaze-master
node ./node_modules/webpack-dev-server/bin/webpack-dev-server.js

http://localhost:8080/webpack-dev-server/
webpack result is served from /
content is served from ./
404s will fallback to /index.html
Hash: ca7616af249742709dcb
Version: webpack 1.13.0
Time: 470ms
Asset     Size  Chunks             Chunk Names
bundle.js  1.69 kB       0  [emitted]  main
chunk    {0} bundle.js (main) 55 bytes [rendered]
[0] multi main 28 bytes {0} [built]
[1] ./src/index.js 27 bytes {0} [built] [1 error]
ERROR in ./src/index.js
Module not found: Error: Cannot resolve module 'script' in /var/www/TurkerGaze-master/src
@ ./src/index.js 1:0-26
webpack: bundle is now VALID.

I think the problem is with my Webcam. If I fix it and run the 'pugazetrckr.html' file, will it run?

does this file pugazetrckr.html exist?
I couldn't get much further than that. I never got it to completely start with node.  I'm not sure what "script" he refers to in that file.

No it doesn't exist. The readme file is confusing actually.

No it doesn't exist. The readme file is confusing actually.

Has anyone figured out how to run this project? I went to http://localhost:8080/webpack-dev-server/, but all it tells me is "App Ready", and redirects me back to index.html which is correct (I think).
But then, it tells me Webcam is not defined in the index.html page.

When I try running the index.html file after creating a localhost, it tells there are no active hits now, come back later. Have you encountered the same problem?

@amarknair, I copied the page source from pugazetrackr.html from their http://isun.cs.princeton.edu/TurkerGaze/pugazetrackr.html webpage and that gives me that error.
The original index.html source file which I downloaded today did not contain that error. Good way to check is the right file should contain the variable Webcam I believe.
I'm assuming they renamed pugazetrackr to index.

Yes, even I think they renamed the file. But I did not understand what you meant by "right file should contain the variable Webcam I believe." Sorry, I am very new to web-development.

No worries. I have more experience with mobile development too. The part of their index.html file which I'm having a headache with is
Webcam.set({   width: 640,   height: 360,   image_format: 'jpeg',   jpeg_quality: 90 }); Webcam.attach( '#imgCanvas' );
on Lines 164-172. The error I'm receiving is that the Webcam variable cannot be resolved. That's because:
`.../node_modules/webcamjs/webcam.js:718
}(window));
^
ReferenceError: window is not defined
`
It depends on the window, which is a client side DOM element, which is not initialized when the server side JS creates the Webcam variable.

Thank you very much. I think I understood the issue with that.

No worries. :) Let me know if you get it running. I'll post here too if I figure it out.

Yes sure, I will try to run it. I will post here too.

@amarknair I got it working. Let me know if you're still working on this.

@heliumsoule Yes, I am. Could you tell me how you got it running?

@amarknair It seems like they didn't put in the right html file. Save this html page and use it in place of index.html in the project folder. Then go into src, and comment out the line in index.js that requires webcamjs.
It should work now if you run npm start and go to the localhost:8080 domain.

Thanks for the help!

@heliumsoule Thank you for the help. I will try it out in my system and let you know the result.

No problem. Good luck with your projects.
On Tuesday, May 17, 2016, Steven Basart<EMAIL_ADDRESS>wrote:

Thanks for the help!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/PrincetonVision/TurkerGaze/issues/2#issuecomment-219884576

@heliumsoule It is working now. We have to try out the html page you mentioned.
Thanks for the help. :)

@xksteven @heliumsoule Are you able to completer the tracking? My camera is turning off abruptly after starting the application. So I am still not able to run it fully.

@amarknair Sorry for the late responses. I am swamped with work for the next two days. Will look at this tomorrow evening. Thanks for being patient.

@amarknair are you still experiencing issues?

@heliumsoule Yes I could solve the issue. It is  not working with my laptop camera in chrome. When I tried with a USB webcam, it is working fine. This was due to a bug in chrome and chromium which is not solved yet.
https://bugs.chromium.org/p/chromium/issues/detail?id=470717&q=webcam ubuntu&colspec=ID Pri M Week ReleaseBlock Cr Status Owner Summary OS Modified

Okay phew that is good to hear. We'll be working with this framework in our lab for the next few months so let me know if anything else comes up!

Yes, sure. I will definitely post here. We are also going to work on the same framework. Keep in touch!!

Really ....thanks allot.  Cheers. Looking forward to nailing you. 4 cross's in the yard.


Resolve All Security Alert

Done in https://github.com/unarxiv/CVPM/commit/f5baf809917f815adeebe4a6bbbe2a57dc2b43d4


In the SetUp Guide of IssuerNodeUI, the issuer-api-ui-1 container does not start up stably."

After executing the make run-ui command in the SetUp Guide, I checked the status of the running containers with the docker ps command. Right after executing the make run-ui command, the issuer-api-ui-1 container seems to start, but soon it stops running. Therefore, even if I access http://localhost:3002/, I cannot display the frontend of api-ui.
Execution Environment
・AWS EC2 Instance
・OS: Ubuntu 22.04.3 LTS
$ make up
docker compose -p issuer -f /usr/local/share/work/issuer-node/infrastructure/local/docker-compose-infra.yml up -d redis postgres vault
[+] Running 4/4
 ✔ Network issuer-network       Created                                                                                0.1s
 ✔ Container issuer-vault-1     Started                                                                                0.2s
 ✔ Container issuer-postgres-1  Started                                                                                0.2s
 ✔ Container issuer-redis-1     Started                                                                                0.2s
$ docker ps
CONTAINER ID   IMAGE                COMMAND                  CREATED          STATUS                    PORTS                                       NAMES
6e7c4394ed32   postgres:14-alpine   "docker-entrypoint.s…"   12 seconds ago   Up 10 seconds (healthy)   <IP_ADDRESS>:5432->5432/tcp, :::5432->5432/tcp   issuer-postgres-1
c072e6d81e51   vault:1.13.2         "docker-entrypoint.s…"   12 seconds ago   Up 10 seconds             <IP_ADDRESS>:8200->8200/tcp, :::8200->8200/tcp   issuer-vault-1
232d74133606   redis:6-alpine       "docker-entrypoint.s…"   12 seconds ago   Up 10 seconds (healthy)   <IP_ADDRESS>:6379->6379/tcp, :::6379->6379/tcp   issuer-redis-1
$ make run-ui
COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_FILE="Dockerfile" docker compose -p issuer -f /usr/local/share/work/issuer-node/infrastructure/local/docker-compose.yml up -d api-ui ui notifications pending_publisher
WARN[0000] Found orphan containers ([issuer-postgres-1 issuer-vault-1 issuer-redis-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 4/4
 ✔ Container issuer-ui-1                 Started                                                                                0.1s
 ✔ Container issuer-api-ui-1             Started                                                                                0.1s
 ✔ Container issuer-notifications-1      Started                                                                                0.1s
 ✔ Container issuer-pending_publisher-1  Started                                                                                0.1s
$
$ docker ps
CONTAINER ID   IMAGE                      COMMAND                  CREATED          STATUS                    PORTS                                       NAMES
571d742d2264   issuer-ui                  "/bin/sh /app/script…"   6 seconds ago    Up 5 seconds              <IP_ADDRESS>:8088->80/tcp, :::8088->80/tcp       issuer-ui-1
2a74740c7904   issuer-pending_publisher   "sh -c 'sleep 4s && …"   6 seconds ago    Up 5 seconds                                                          issuer-pending_publisher-1
56ac393dd3b9   issuer-api-ui              "sh -c 'sleep 4s && …"   6 seconds ago    Up 5 seconds              <IP_ADDRESS>:3002->3002/tcp, :::3002->3002/tcp   issuer-api-ui-1
6e7c4394ed32   postgres:14-alpine         "docker-entrypoint.s…"   25 seconds ago   Up 23 seconds (healthy)   <IP_ADDRESS>:5432->5432/tcp, :::5432->5432/tcp   issuer-postgres-1
c072e6d81e51   vault:1.13.2               "docker-entrypoint.s…"   25 seconds ago   Up 23 seconds             <IP_ADDRESS>:8200->8200/tcp, :::8200->8200/tcp   issuer-vault-1
232d74133606   redis:6-alpine             "docker-entrypoint.s…"   25 seconds ago   Up 23 seconds (healthy)   <IP_ADDRESS>:6379->6379/tcp, :::6379->6379/tcp   issuer-redis-1
root@ip-10-0-0-115:/usr/local/share/work/issuer-node# docker ps
CONTAINER ID   IMAGE                COMMAND                  CREATED          STATUS                    PORTS                                       NAMES
571d742d2264   issuer-ui            "/bin/sh /app/script…"   14 seconds ago   Up 13 seconds             <IP_ADDRESS>:8088->80/tcp, :::8088->80/tcp       issuer-ui-1
6e7c4394ed32   postgres:14-alpine   "docker-entrypoint.s…"   33 seconds ago   Up 31 seconds (healthy)   <IP_ADDRESS>:5432->5432/tcp, :::5432->5432/tcp   issuer-postgres-1
c072e6d81e51   vault:1.13.2         "docker-entrypoint.s…"   33 seconds ago   Up 31 seconds             <IP_ADDRESS>:8200->8200/tcp, :::8200->8200/tcp   issuer-vault-1
232d74133606   redis:6-alpine       "docker-entrypoint.s…"   33 seconds ago   Up 31 seconds (healthy)   <IP_ADDRESS>:6379->6379/tcp, :::6379->6379/tcp   issuer-redis-1
$

Additional information:
In the SetUp Guide for IssuerNodeCoreAPI, even if I skipped the settings from "Import Wallet Private Key To Vault" to "Add Vault Token to Configuration File," accessing http://localhost:3001/ displayed the issuer API endpoints.
Similarly, in the SetUp Guide for IssuerNodeUI, I have skipped the settings from "Import Wallet Private Key To Vault" to "Add Vault Token to Configuration File." I thought that like IssuerNodeCoreAPI, the api-ui endpoints would be displayed in IssuerNodeUI as well, but in reality, they are not displayed even when accessing http://localhost:3002/.
Please provide a solution.

The issue was resolved without any problems once the wallet's private key was configured.


failed with VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) No compatible source was found for this media.

我的代码如下：

报这个错误

网上 找了一下说什么版本bug
https://github.com/videojs/video.js/issues/5606
怎么解决呢

同问，怎么解决呢？

up

Did you solve it?

up

Have you solved it? I have this problem, too.

Have you found an answer to this? I've come across the same problem

基于谷歌播放格式的支持，不支持m3u8播放，后续又禁止了fash，于是m3u8处于一个很尴尬的情况


I'm not sure how the changes I made in #379 could have caused that problem—it fails even before attempting to run the tests, and I haven't touched anything related to dependencies.
I'm trying to figure out whether my intuition is incorrect, or whether CI is actually failing on master. I notice that the last master change was from a couple months ago, so I'm worried that some dependency has broken in the mean time.

If you look at the log report, you'll see that the error is from gem sass-embedded which is a recent entry into our bundle via jekyll-sass-converter-3.0.
So, the master is most likely affected as well. However, what puzzles me is that the error doesn't occur at repo jekyll/jekyll for same Ruby version. Maybe I am overlooking something obvious...

One thing I noticed when I was working locally (that I managed to deal with separately) was this message:
❯ bundle update
Fetching https://github.com/jez/jekyll-feed.git
Fetching gem metadata from https://rubygems.org/..........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
sass-embedded-1.57.1-x86_64-linux-gnu requires rubygems version >= 3.3.22, which is incompatible with the current version, 3.1.6

I wonder if the bug is that sass-embedded made a change that tied them to a specific bundler version, and only later realized that they should declare that dependency in a version bound?
I wonder if it's possible to fix CI by pinning the sass-embedded version in CI somehow? I still haven't managed to exactly reproduce the failure as seen by CI in my local environment.
(Thanks for taking a moment to look at this.)

That's a different issue @jez. Its asking for a newer version of Rubygems, not Bundler.
You can update the version on your local system by running:
gem update --system

Could you add a commit bumping gem "rake" to use "~> 13.0" on this branch? Please ping me after you push so that I can activate the CI run.

Interesting. Is Rake 12 incompatible with certain features of Ruby 3? I'm surprised we didn't catch this before.

@ashmaroli lmk if the latest commit is what you're looking for

@parkr I'm not sure if Rake 12.x is incompatible with Ruby 3, but gem sass-embedded seems to be using a syntax that is not compatible with Rake 12.
We didn't catch this before because Jekyll Core had moved onto Rake 13 long ago and that sass-embedded only became a default member of our bundle / gemset recently.

@jez CI is passing.
So your mission has been successful. 🙂

@jekyllbot: merge +dev

@parkr Do we really need Rake for this repository?


Add more error handling

handle undefined entityType

This was also required in my node application to stop it from crashing under certain data conditions

In what conditions the entityType is not found? Seems to me it should be always found for the collection so we should rather find the reason why it is not found rather than silently ignore this.

I'm dynamically creating entityTypes from an elasticsearch query (using get mappings API). Sometimes the mapping for a dataset does not exist. Therefore, an entityType will not exist for a EntitySet in my case. With this and #11 and #13, the API will still function (i.e return data) and not crash the node process.


Add Inject State struct level validation tests

What would you like to be added:
Injection State does not have specific struct tests like the other states.

I think that this PR https://github.com/serverlessworkflow/sdk-go/pull/164 also address this issue.
@ricardozanini ^

Fixed on #164


How to decrease mouse steps when scrolling?

Hi!
I've tried to play around with the mouseWheelSpeed option to decrease the amount of steps when scrolling. But nothing is really happening. Am I tweaking wrong option?

searching for an answer as well!


Python3 compatibility: string.letters, range() and dividing by 2

Hello Troy,
thanks for this code.
I added Python 3 funcitonality by

changing xrange() to range()
dividing by 2 not like " / 2" but like " // 2" to only get integers as a result
changing string.letters to string.ascii_letters

My kind regards,
Ben
This is your code example compatible with Python3:
from fuzzywuzzy import fuzz
import random, string

population = 20
generations = 10000
in_str = None
in_str_len = None

class Agent:
    def __init__(self, length):
        self.string = ''.join(random.choice(string.ascii_letters) for _ in range(length))
        self.fitness = -1

    def __str__(self):
        return f'{self.string}\t| {self.fitness}'

def genetic_algorithm():
    agents = init_agents(population, in_str_len)

    for generation in range(generations):
        print(f'Generation {generation}')

        agents = fitness(agents)
        agents = selection(agents)
        agents = crossover(agents)
        agents = mutation(agents)

        if any(agent.fitness >= 90 for agent in agents):
            print('Threshold met.')
            exit(0)

def init_agents(population, length):
    return [Agent(length) for _ in range(population)]

def fitness(agents):
    for agent in agents:
        agent.fitness = fuzz.ratio(agent.string, in_str)
    return agents

def selection(agents):
    agents = sorted(agents, key=lambda agent: agent.fitness, reverse=True)

    print('\n'.join(map(str, agents)))

    agents = agents[:int(0.2 * len(agents))]
    return agents

def crossover(agents):
    offspring = []

    for _ in range((population - len(agents)) // 2):
        parent1 = random.choice(agents)
        parent2 = random.choice(agents)
        child1 = Agent(in_str_len)
        child2 = Agent(in_str_len)
        split = random.randint(0, in_str_len)
        child1.string = parent1.string[0:split] + parent2.string[split:in_str_len]
        child2.string = parent2.string[0:split] + parent1.string[split:in_str_len]

        offspring.append(child1)
        offspring.append(child2)

    agents.extend(offspring)

    return agents

def mutation(agents):
    for agent in agents:
        for idx, param in enumerate(agent.string):
            if random.uniform(0.0, 1.0) <= 0.1:
                agent.string = agent.string[0:idx] + random.choice(string.ascii_letters) + agent.string[idx+1:in_str_len]

    return agents

if __name__ == '__main__':
    in_str = 'TroySquillaci'
    in_str_len = len(in_str)
    genetic_algorithm()

I got this error when I run your code.
I already install fuzzywuzzy package
Python 3.8.2
pip 20.0.2
fuzzywuzzy 0.18.0
Traceback (most recent call last):
  File "D:/python/firstml/geneicAlgo.py", line 3, in <module>
    from fuzzywuzzy import fuzz
ModuleNotFoundError: No module named 'fuzzywuzzy'

@benjordanstanford Thanks for your update. It's a great help to me.


[Prototype] Caching in QiskitDevice

This PR prototypes the logic of adding caching capabilities to QiskitDevice.

Closing this as device caching is being deprecated (see here https://github.com/PennyLaneAI/pennylane/pull/2154).


Crash with autonomatic user with a bucket

i was trying to milk cows with it and crash
crash-2017-02-11_17.42.51-server.txt

Yeah theres some weird antix with null item stacks and entities. http://i.imgur.com/7OwcFKi.png  i havent crashed it yet myself, but i think i see where it could happen.

Try this out in latest version https://minecraft.curseforge.com/projects/cyclic/files/2380823 . Fixed a few things. open another issue if anything happens.


Adding photoflow

Motivation for this change
Adding new software
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Also please use photoflow: init at 0.2.8 as the commit message.

Okay to merge?


Update scala-xml to 2.1.0 in series/0.23

Updates org.scala-lang.modules:scala-xml from 2.0.1 to 2.1.0.
GitHub Release Notes - Version Diff
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.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.0.1).
You might want to review and update them manually.
docs/changelog.md
scalafix/project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang.modules", artifactId = "scala-xml" } ]

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1

Superseded by #6236


Is it possible to choose the response type

Question
I have the following generated struct s.
Even though the server returns the CreateTranscriptionResponseVerboseJson (I see it in proxyman), the response is parsed as CreateTranscriptionResponseJson. I guess because it is a subset of the verbose one and it's the one that's first tried?
Full reproduction: https://github.com/atacan/swift-openai-api/blob/c087e61ed66ea40e627b785e8146bddd44a5e8b8/Tests/OpenAIAsyncHTTPClientTests/OpenAIAsyncHTTPClientTest.swift#L90
Code snippets are below
        /// Represents a transcription response returned by model, based on the provided input.
        ///
        /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseJson`.
        public struct CreateTranscriptionResponseJson: Codable, Hashable, Sendable {
            /// The transcribed text.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseJson/text`.
            public var text: Swift.String
            /// Creates a new `CreateTranscriptionResponseJson`.
            ///
            /// - Parameters:
            ///   - text: The transcribed text.
            public init(text: Swift.String) {
                self.text = text
            }
            public enum CodingKeys: String, CodingKey {
                case text
            }
        }
        /// Represents a verbose json transcription response returned by model, based on the provided input.
        ///
        /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson`.
        public struct CreateTranscriptionResponseVerboseJson: Codable, Hashable, Sendable {
            /// The language of the input audio.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson/language`.
            public var language: Swift.String
            /// The duration of the input audio.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson/duration`.
            public var duration: Swift.String
            /// The transcribed text.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson/text`.
            public var text: Swift.String
            /// Extracted words and their corresponding timestamps.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson/words`.
            public var words: [Components.Schemas.TranscriptionWord]?
            /// Segments of the transcribed text and their corresponding details.
            ///
            /// - Remark: Generated from `#/components/schemas/CreateTranscriptionResponseVerboseJson/segments`.
            public var segments: [Components.Schemas.TranscriptionSegment]?
            /// Creates a new `CreateTranscriptionResponseVerboseJson`.
            ///
            /// - Parameters:
            ///   - language: The language of the input audio.
            ///   - duration: The duration of the input audio.
            ///   - text: The transcribed text.
            ///   - words: Extracted words and their corresponding timestamps.
            ///   - segments: Segments of the transcribed text and their corresponding details.
            public init(
                language: Swift.String,
                duration: Swift.String,
                text: Swift.String,
                words: [Components.Schemas.TranscriptionWord]? = nil,
                segments: [Components.Schemas.TranscriptionSegment]? = nil
            ) {
                self.language = language
                self.duration = duration
                self.text = text
                self.words = words
                self.segments = segments
            }
            public enum CodingKeys: String, CodingKey {
                case language
                case duration
                case text
                case words
                case segments
            }
        }

the code
// ⚠ Even though the server returns VerboseJson, we get Json here
        switch response {
        case .ok(let ok):
            switch try ok.body.json {
            case .CreateTranscriptionResponseVerboseJson(let verbose):
                dump(verbose)
            case .CreateTranscriptionResponseJson(let json):
                dump(json)
            }
        case .undocumented(let statusCode, let undocumentedPayload):
            let buffer = try await undocumentedPayload.body?.collect(upTo: 1024 * 1035 * 2, using: .init())
            let description = String(buffer: buffer!)
            print("❌", statusCode, description)

            struct myerror: Error {}
            throw ClientError.init(operationID: "", operationInput: "", causeDescription: "", underlyingError: myerror())
        }

I expect this OpenAPI document might be missing a discriminator for the anyOf. Without that, there might not be much we can do.
https://redocly.com/docs/resources/discriminator

Thank you. I checked it, and it uses oneOf.
Changing it to anyOf alone didn't work either. I also moved the CreateTranscriptionResponseVerboseJson one line up to be before the other one.
  /audio/transcriptions:
    post:
      operationId: createTranscription
      tags:
        - Audio
      summary: Transcribes audio into the input language.
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: "#/components/schemas/CreateTranscriptionRequest"
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                oneOf:
                  - $ref: "#/components/schemas/CreateTranscriptionResponseJson"
                  - $ref: "#/components/schemas/CreateTranscriptionResponseVerboseJson"

OK. I found the problem. A numeric property is specified as a string.
Putting the expected value before is still important, because in case of anyOf decode tries one by one, and if one type is a subset of the other the decoder will work.
public init(from decoder: any Decoder) throws {
    var errors: [any Error] = []
    do {
        value1 = try .init(from: decoder)
    } catch {
        errors.append(error)
    }
    do {
        value2 = try .init(from: decoder)
    } catch {
        errors.append(error)
    }
    try Swift.DecodingError.verifyAtLeastOneSchemaIsNotNil(
        [
            value1,
            value2
        ],
        type: Self.self,
        codingPath: decoder.codingPath,
        errors: errors
    )
}

The important difference is that the payload must match exactly one schema in a oneOf, and one or more in an allOf. If one is a subset of the other, then by definition it cannot be oneOf (as it can match both), and would be an anyOf.
The discriminator wouldn't make a difference here, because when parsing an anyOf, all the schemas are given a chance to decode the payload.


python311Packages.podman: 4.8.1 -> 4.8.2

Diff: https://github.com/containers/podman-py/compare/refs/tags/v4.8.1...v4.8.2
Changelog: https://github.com/containers/podman-py/releases/tag/v4.8.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 280692 run on x86_64-linux 1

4 packages built:

python311Packages.podman
python311Packages.podman.dist
python312Packages.podman
python312Packages.podman.dist


Update Indicator to Support Font Ligatures

Modified the indicator to ensure compatibility with font ligatures, improving visual presentation in editors and environments that support them.

PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ✔] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[✔ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ✔] Not Applicable
OR
[ ] Documentation needed
- [ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[✔ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

I doubt this change will be accepted because it's a breaking change that doesn't provide any benefit for the majority of people. The only way I can imagine this being accepted is if instead of updating the actual property, you update the formatting. For pscustomobjects the easiest way to do that would be to add a custom type name and add custom formatting for that type.
Before you do that however, I'd advice you to create an issue for this and see what the relevant WG or PS team member has to say about it.

Please create new issue to discuss. (But it is really huge breaking change!)


xiaomi_miio.climate not found

Home Assistant version
0.110.3
SmartIR version
SmartIR configuration

remote:
  - platform: xiaomi_miio
    name: ir_bigroom
    host: <IP_ADDRESS>
    token: *************

climate:
  - platform: smartir
    name: Mitsubishi SRK20ZJ-S BigRoom
    device_code: 999998
    controller_data: remote.ir_bigroom

Describe the bug
With media_player platform SmartIR works fine. But when I try to add air condition, I have an errors...
Debug log
2020-05-28 09:12:22 ERROR (MainThread) [homeassistant.config] Platform error: climate
Traceback (most recent call last):
  File "/var/www/homeassistant/lib/python3.8/site-packages/homeassistant/config.py", line 777, in async_process_component_config
    platform = p_integration.get_platform(domain)
  File "/var/www/homeassistant/lib/python3.8/site-packages/homeassistant/loader.py", line 272, in get_platform
    cache[full_name] = importlib.import_module(
  File "/usr/local/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'homeassistant.components.xiaomi_miio.climate'
2020-05-28 09:12:22 ERROR (MainThread) [homeassistant.config] Platform error: climate
Traceback (most recent call last):
  File "/var/www/homeassistant/lib/python3.8/site-packages/homeassistant/config.py", line 777, in async_process_component_config
    platform = p_integration.get_platform(domain)
  File "/var/www/homeassistant/lib/python3.8/site-packages/homeassistant/loader.py", line 272, in get_platform
    cache[full_name] = importlib.import_module(
  File "/usr/local/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'homeassistant.components.xiaomi_miio.climate'

Additional context
I can not find any additional components , which includes xiaomi_miio/climate.py
Which plugin I must to use with SmartIR for xiaomi IR controller?

You need to fix xiaomi_miio remote integration

I'm follow instructions from https://www.home-assistant.io/integrations/remote.xiaomi_miio/
That is standart component of HomeAssistant in current version.
Which fix i must to apply?

No, you do not need an additional module.
Does the remote.send_command service work properly?

Any chance you can also use https://github.com/syssi/xiaomi_airconditioningcompanion?

Does the remote.send_command service work properly?
Yes, I'm using Your plugin with satellite box (as media player).

- platform: smartir
  name: GS B528 bigroom
  device_code: 999999
  controller_data: remote.ir_bigroom
# power_sensor: binary_sensor.tv_power
  source_names:
    TRICOLOR: 'Триколор ТВ'
    CINEMA: 'Кино'
    BIGTV: 'Большое кино'
    TVGID: 'Телегид'
    RADIO: 'Радио'

Any chance you can also use https://github.com/syssi/xiaomi_airconditioningcompanion?
If there no chances to use Your pugin , then I wil use that.

I'm asking you because I can't imagine from where homeassistant.components.xiaomi_miio.climate comes, except xiaomi_airconditioningcompanion.


spammed with "expected primary-expression before ‘}’ token"

Checklist

[x] Check that you have the GNU C Compiler installed by typing gcc --version into a terminal.
[x] If you don't have the linter package installed, either update to the latest version of linter-gcc or install linter directly with apm install linter.
[x] Ensure that you are using a valid grammar - either C/C++/C++14
[x] Ensure that you have read all the relevant information in the wiki, particularly the Common Issues page.

Issue ((not)including debugging messages):
the linter is giving me a lot of errors that don't point to anything relevant and don't make sense
I know the errors should not be there because the actual GCC compiler makes no mention of them.
https://imgur.com/zR5zaB5 screenshot of errors
im using atom 1.25.1 on Ubuntu 16.04, sorry I don't have any debug messages because when I enabled debug messages I didn't see any. or at least I didn't recognize any if they did appear.

I have the same problem!


invalid hash key

i have created hash key and used it in app setting in facebook
but not working and show message invalid hash key not equal any hash key

Hi @GamalSebaee did you have any solution?

yes ,try this way
this is way worked with me
*************** soluation**************
This is how i solved this problem
Download your APK to your PC in java jdk\bin folder
in my case founded in  C:\Program Files\Java\jdk1.7.0_121\bin
go to java jdk\bin folder and run cmd then
copy the following command in your cmd
keytool -list -printcert -jarfile yourapkname.apk
Copy the SHA1 value to your clip board
like this CD:A1:EA:A3:5C:5C:68:FB:FA:0A:6B:E5:5A:72:64:DD:26:8D:44:84
and open http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.
This is what Facebook requires
get the generated hash " ********************= " and copy the key hash to the facebook app.

please try this soluation .

Thank you @GamalSebaee. It worked for me.


Statements must be separated by newlines or semicolon

Environment data

Language Server version: 2020.6.1
OS and version: Win 10, 2004
Python version (& distribution if applicable, e.g. Anaconda): 2.7.18rc1, virtualenv

Expected behaviour
No Problem message
Actual behaviour
Statements must be separated by newlines or semicolons
Code
x = 10
try:
    print str(x)
except Exception as ex:
    print str(x)

The print keyword is not supported in Python 3, so this code will not run in a Python 3 interpreter.
Pylance does not support Python 2. If you still have Python 2 code that you need to support, you can use the Jedi language server instead.

So python 2.7 is not supported? I was migrating from Microsoft Python Language Server and I did not see it’s not supported.
I am closing this issue. Thanks

How do I turn off this prompt？

How do I turn off this prompt？

How do I turn off this prompt in diagnosticSeverityOverrides？

How do I turn off this prompt in diagnosticSeverityOverrides？

There is no way to disable a syntax error; if you believe there's a bug in the parser, please file a new issue. But, this issue was for Python 2 compatibility, and we have no plans to support Python 2, so if your error stems from the print keyword, that's issue which we aren't going to change.

There is no way to disable a syntax error; if you believe there's a bug in the parser, please file a new issue. But, this issue was for Python 2 compatibility, and we have no plans to support Python 2, so if your error stems from the print keyword, that's issue which we aren't going to change.


[Game Request] Sugar Sweet Temptation

VNDB: https://vndb.org/r105982
Engine: KiriKiri
Extension: .xp3
The Japanese version is already in the database (Shugaten! -sugarfull tempering-), but this key does not work for the English version
Example .xp3: https://jfydro.ru/temp/evimage.xp3

Try krkrextract


bug: Cached response when switching kubectl context

Checklist:

[X] I've searched for similar issues and couldn't find anything matching
[X] I've included steps to reproduce the bug.
[X] I've included the version of Kubernetes and k8sgpt.

Subject of the issue
After changing kubectl context to another cluster, it seems as if k8sgpt just respons with a cache without actually checking. I get the same (identical) response eventhough kubeconfig context was changed.
Your environment

Version of Kubernetes
Client Version: v1.26.1
Kustomize Version: v4.5.7
Server Version: v1.24.6
Host OS and its version / If windows, is it WSL?
System Version: macOS 13.1 (22C65)
Kernel Version: Darwin 22.2.0
Version of k8sgpt
k8sgpt version 0.1.2

Steps to reproduce

Step 1
Execute an analyze
Step 2
Switch kubectl context to a different cluster
Step 3
Execute another analyze

Expected behaviour
I expected to get a new analyze result from the new cluster context.
Actual behaviour
I got the identical response as from when I first ran the analyze
Additional context / screenshots
I've also tried deleting ~/.k8sgpt.yaml as well as ~/.kube/config and thereafter reset a totally fresh kubeconfig context and reinitated the k8sgpt auth. The respons I got after a k8sgpt analyze was the exact same as before, from the cluster I no longer have in my context.
The progress loading is at 0% and the time usage output says | (0/4, 0 it/hr) [0s:0s]0
Additionally, also tried from a different terminal session. Also tried switching to Terminal.app instead of iTerm. Also switched from omzsh to bash. I get the cached response immediately...
I verified that kubectl had correctly switch context between each step and in all the different shell sessions, and that. k8sgpt had not switched. It still gave the identical response.

Fixed in https://github.com/k8sgpt-ai/k8sgpt/pull/155

@AlexsJones - Thanks for the quick response, but alas - v.0.1.4 gives the same incorrect result.
I did a the following, if it is of any help...;
➜  ~ brew upgrade k8sgpt
==> Upgrading k8sgpt-ai/k8sgpt/k8sgpt
  0.1.2 -> 0.1.4

➜  ~ k8sgpt version
k8sgpt version 0.1.4

➜  ~ kubectl config use-context <CLUSTER_1>
Switched to context <CLUSTER_1>

➜  ~ k8sgpt analyse
   0% |                                                                                | (0/4, 0 it/hr) [0s:0s]0 kube-system/kube-prometheus-stack-kube-controller-manager(kube-prometheus-stack-kube-controller-manager)
- Error: Service has no endpoints, expected label component=kube-controller-manager
1 kube-system/kube-prometheus-stack-kube-etcd(kube-prometheus-stack-kube-etcd)
- Error: Service has no endpoints, expected label component=etcd
2 kube-system/kube-prometheus-stack-kube-proxy(kube-prometheus-stack-kube-proxy)
- Error: Service has no endpoints, expected label k8s-app=kube-proxy
3 kube-system/kube-prometheus-stack-kube-scheduler(kube-prometheus-stack-kube-scheduler)
- Error: Service has no endpoints, expected label component=kube-scheduler

➜  ~ kubectl config use-context <CLUSTER_2>
Switched to context <CLUSTER_2>

# verifying that kubectl has switched by inspecting that it is in fact a different cluster
➜  ~ kubectl get ns

➜  ~ k8sgpt analyse
   0% |                                                                                | (0/4, 0 it/hr) [0s:0s]0 kube-system/kube-prometheus-stack-kube-controller-manager(kube-prometheus-stack-kube-controller-manager)
- Error: Service has no endpoints, expected label component=kube-controller-manager
1 kube-system/kube-prometheus-stack-kube-etcd(kube-prometheus-stack-kube-etcd)
- Error: Service has no endpoints, expected label component=etcd
2 kube-system/kube-prometheus-stack-kube-proxy(kube-prometheus-stack-kube-proxy)
- Error: Service has no endpoints, expected label k8s-app=kube-proxy
3 kube-system/kube-prometheus-stack-kube-scheduler(kube-prometheus-stack-kube-scheduler)
- Error: Service has no endpoints, expected label component=kube-scheduler

# 👆 these services does not exist in CLUSTER_2, and the response / result came instantly (seems cached 🤷♂)


Question about module property in package.json

Hi and thank you for the nice article on sitpoint!
In the bootstrap-tool example, the selectedModuleSystem is assigned to the module property in package.json. I was wondering why not the type property?

This is an error in my article, it should be type — thanks for catching this and letting me know!
It's great to hear that you enjoyed the article :)

I replay did enjoy the article.
Thanks for the reply.

Fixed in the bootstrap tool in this repository. I've opened a pull request which fixes it in the article — the changes will hopefully go live early next week.
Thanks again @nicolaibach!


[5.4] Remove unnecessary comment

We use these throughout the framework.

They're also pretty useful to distinguish between return void, and not documented yet.

Yes... but on a __construct?

Yes, connect.

https://3v4l.org/IGGs3

@GrahamCampbell A constructor should never return anything other than an instance of a class though. Is there anywhere in the framework we directly call __construct(), because that seems wrong

A constructor should never return anything other than an instance of a class though.

Wrong, as I proved in that link. It returns nothing.


#936 - Fix Strategy RESET/MAINTAIN

#936

[ ] deposit range strategy

create a strategy with both budgets
trade out everything from 1 order
deposit into the side with budget only
expect: the empty order should keep the same marginal price
actual: the marginal price gets reset somehow
(i believe we should NOT pass any value if there is no change. for this, we should NOT pass 0 budget for the empty order)


Optimization of the graph network

Optimization of the graph network (TorchMD_GN) with NNPOps (https://github.com/openmm/NNPOps).
In a special case, TorchMD_GN is equivalent to SchNet (https://github.com/compsciencelab/torchmd-net/issues/45#issuecomment-968962455), which is already supported by NNPOps:
TorchMD_GN(rbf_type="gauss", trainable_rbf=False, activation="ssp", neighbor_embedding=False)

[x] Implement PyTorch wrapper for CFConvNeighbors and CFConv -- https://github.com/openmm/NNPOps/pull/40
[x] Accelerate the limited TorchMD_GN with NNPOps -- https://github.com/torchmd/torchmd-net/pull/50
[x] Update the installation instructions -- https://github.com/torchmd/torchmd-net/pull/55

[ ] NNPOps package -- https://github.com/openmm/NNPOps/issues/26
[x] PyTorch Geometric package -- https://github.com/torchmd/torchmd-net/pull/53

In general, TorchMD_GN needs these:
TorchMD_GN(rbf_type="expnorm", trainable_rbf=True, activation="silu", neighbor_embedding=True)

[ ] Implement the exponentially-modified Gaussian in CFConv (rbf_type="expnorm")
[ ] Allow to pass arbitrary RBF positions to CFConv (trainable_rbf=True)
[ ] Implement the SILU activation in CFConv (activation="silu")
[ ] Reuse CFConv to accelerate the neighbor embedding (neighbor_embedding=True)

Regarding the interface, it should look and work like this:
 # Create or load a model in any way
model = TorchMD_GN()

# Optional: train or do what ever you want with the model

# Optimize the model
from torchmdnet.optimize import optimize
optimized_model = optimize(model, some_optimization_options)

# Do the inference with the model
results = optimized_model.forward(z, pos, batch)

# Optional: convert the model into TorchScript and save for external use (e.g. OpenMM-Torch)
torch.jit.script(optimized_model).save('model.pt')

It is similar, what is being implemented for the TorchANI optimization (https://github.com/raimis/NNPOps/blob/opt_ani/README.md#example).
@PhilippThoelke @stefdoerr @giadefa any comments?

For a moment, it seems all the PyTorch-Geometric packages are broken (https://github.com/pyg-team/pytorch_geometric/issues/3660).

@peastman I have just finished integrating NNPOps (https://github.com/torchmd/torchmd-net/pull/50). The performance (https://github.com/torchmd/torchmd-net/blob/main/benchmarks/graph_network.ipynb) is just 2-3 time better for the small molecules (10-100 atoms) and no significant improvement for the larger ones.
I'll try to profile to get a better insight. At some, we should discuss, if we can make any further improvements.
cc: @giadefa

It would be useful to separate out all the different optimizations in NNPOps.  Can you identify the effect of each one separately?
Back when we first started designing it, we discussed requirements and decided it would be optimized for molecules of about 100 atoms.  The code is all designed around that assumption.  If we want good performance on much larger molecules, it would need to be written differently.  For example, it uses a O(n^2) algorithm to build the neighbor list, which is very fast for small molecules and very slow for large ones.

100 particles is a good case. However, we have two ways of running multiple
simulations.
In one we batch them where the same molecule is run in a single NN batch
for forces and your kernel does not batch.
In another way, we simply make multiple copies, e.g. 64 far enough and run
it as a single system but in this case the system size is more like 6400
particles.
I think that we need batching in the CUDA kernel for identical molecules
and cell lists which are very fast.
g
On Tue, Feb 22, 2022 at 5:46 PM Peter Eastman @.***>
wrote:

It would be useful to separate out all the different optimizations in
NNPOps. Can you identify the effect of each one separately?
Back when we first started designing it, we discussed requirements and
decided it would be optimized for molecules of about 100 atoms. The code is
all designed around that assumption. If we want good performance on much
larger molecules, it would need to be written differently. For example, it
uses a O(n^2) algorithm to build the neighbor list, which is very fast for
small molecules and very slow for large ones.
—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd-net/issues/48#issuecomment-1047996832,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOQDRFKIOXWBGYPNER3U4O4UXANCNFSM5IT6CSDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

That would definitely need code changes to be efficient.  You want it to know it only needs to check each atom against the other atoms in its own copy, not all the other copies.  Spreading the copies out through space is also inaccurate.  The further an atom is from the origin, the less precisely its position can be specified.

On Tue, Feb 22, 2022 at 6:15 PM Peter Eastman @.***>
wrote:

That would definitely need code changes to be efficient. You want it to
know it only needs to check each atom against the other atoms in its own
copy, not all the other copies. Spreading the copies out through space is
also inaccurate. The further an atom is from the origin, the less precisely
its position can be specified.

Yes, the accuracy is a problem but it is quite efficient done this way.
Some tests on forces showed reasonable results though but I agree that it
is a problem. The other way is batching, can you add batching of multiple
copies of the same molecules in your CUDA kernel?
g

—
Reply to this email directly, view it on GitHub
https://github.com/torchmd/torchmd-net/issues/48#issuecomment-1048025066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3KUOQ5S5EDVZCAV6YRUILU4PABXANCNFSM5IT6CSDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

It's possible.  Can you open an issue on the NNPOps repository describing exactly how you would want it to work?

@raimis can yuo make an issue there as you probbably know the details of what you need in NNPOps.

Just before going into NNPOps, I checked how much CUDA Graphs (https://pytorch.org/blog/accelerating-pytorch-with-cuda-graphs/) can help.
CUDA Graphs don't work with TorchMD_GN due to https://github.com/rusty1s/pytorch_cluster/issues/123. To circumvent this, I have implemented a fake neighbor search, which assume that all the atoms are neighbors, a.k.a. brute force.
The results (https://github.com/raimis/torchmd-net/blob/poc_cuda_graph/benchmarks/graph_network.ipynb) are promising:

For alanine dipeptide (ALA2, 22 atoms) and testosterone (TST, 49 atoms), the brute force approach with CUDA Graphs beat everything else.
For  chignolin (CLN, 166 atoms), the brute force is not longer the best and for larger systems it runs out of memory.

Ping: @giadefa @peastman @claudi

The current implementation doesn't support batching, but it could implemented.

Optimization: round 2
I have wrote optimized kernels for the neighbor search (#61) and message passing (#69). The kernels are drop-in replacement for the generic kernels from PyTorch Geometric and have such optimizations:

Take into account the symmetry (i.e. if A is bonded to B, then B is bonded to A), assume 3D space, etc. (borrowed ideas from @peastman code https://github.com/openmm/NNPOps/tree/master/src/schnet)
Compatible with CUDA Graphs

Speed:

kernels use just the new kernels

kernels+graphs use the new kernels and CUDA Graphs

Other benchmarks as in the previous plot (https://github.com/torchmd/torchmd-net/issues/48#issuecomment-1048899019)

There is a significant speed up for the small molecules, as it even more removes overhead.

For large molecule, the speed is comparable to the @peastman kernels, as time is dominated by computation by itself.

The new kernels fail with STMV, but not due to the lack of memory. Still I need to debug the cause.


feat: Add support for cloudwatch_log_group_class

Description

add optional variable cloudwatch_log_group_class (default: null)
A driveby contribution.
References:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#log_group_class
https://github.com/hashicorp/terraform-provider-aws/releases?q=log_group_class&expanded=true
Motivation and Context

Resolves #33
Breaking Changes

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 2.8.0 :tada:


Allow discovering cl.exe at runtime with setuptools 74.0.0 or later

Closes #8568.
edit: This PR adopts recent setuptools changes, specifically v74.0.0 (which removed setuptools.msvc) and v74.1.0+ (which reverted setuptools.msvc but requires explicit module import instead of import setuptools).

Original description
On Windows platform with setuptools 74+, it will now take 2-3 seconds to find cl.exe. This overhead happens only once per process, and only when the use of nvcc is requested.
setuptools.msvc (which we rely on for years and is now removed) was able to discover cl.exe very quickly as it directly reads the Windows registry. The new approach introduced in this PR (which only uses the public/documented setuptools API) retrives the compiler path through vcvarsall.bat, which incurs subprocess invocation.

Oops, I just noticed setuptools.msvc removal has been reverted...
https://github.com/pypa/setuptools/pull/4626

/test mini

/test mini

/test mini

/test mini
This one is review ready!

/test mini

/test mini

@takagi Failed to backport automatically.

Not cleanly cherry-picked

@takagi This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?


The procees stuck at the SQL PAAS Assessment

Hello,
I run the tool using multiple options for VMware appliance source always without customization. All tries stuck on the "SQL PAAS Assessment". It creates the SQL -Prod-AME-xxx group and then remains on the assessment creation step.
Please find attached a screenshot with the log, the tool status along with the groups, assessments and files created on the AzMigExport directory.

Thank you.

Hello, thank you for your response and creating this issue, the PowerShell script has some bugs, as a result of which the assessments are not being created. Since the assessments are not being created the script is stuck in a loop to get the status of the assessment. Thus, it gets stuck.
We are working on migrating the entire code from PowerShell to embedding it in UI with .NET. This should resolve this issue.

Hello @ekleidaras , we released a new version of the tool yesterday. It has a new UI and better efficiencies compared to the script. Can you please try that?

Hello @hvr2804,  I will give it a try and share the results here. Thank you for the update!


only specific instance types and not instance families can be listed in context.instanceTypes

Describe the Bug
The documentation for context configuration implies that one can supply instance family names (e.g. "c5", "m5", "r5", etc) in the list of instanceTypes used by a context.
See:
https://github.com/aws/amazon-genomics-cli/blob/6ed94111ea167d9177e315aafabc1e1b9752452c/site/content/en/docs/Concepts/contexts.md?plain=1#L81-L90
However, if I try to deploy a context with the following config:
contexts:
    cpuctxminiwdl:
        engines:
            - type: wdl
              engine: miniwdl
        instanceTypes:
          - c5
          - m5
          - r5

the context fails to deploy and I get the following error:
2022-04-29T22:34:03Z ✘   error="1 context deployment failures"
Error: an error occurred invoking 'context deploy'
with variables: {contexts:[] deployAll:false}
caused by: 1 context deployment failures
suggestion: To resolve failure 1, determine the cause of: exit status 1

Steps to Reproduce
Create a new agc project.
Update the agc-project.yaml file to contain:
name: test
schemaVersion: 1
contexts:
    cpuctxminiwdl:
        engines:
            - type: wdl
              engine: miniwdl
        instanceTypes:
          - c5
          - m5
          - r5

Run:
agc context deploy -v cpuctxminiwdl

Relevant Logs
2022-04-29T22:33:53Z ↓
2022-04-29T22:34:03Z 𝒊  /home/ec2-user/.agc/cdk/node_modules/aws-cdk-lib/aws-ec2/lib/instance-types.ts:666
2022-04-29T22:34:03Z 𝒊        throw new Error('Malformed instance type identifier');
2022-04-29T22:34:03Z 𝒊              ^
2022-04-29T22:34:03Z 𝒊  Error: Malformed instance type identifier
2022-04-29T22:34:03Z 𝒊      at InstanceType.get architecture [as architecture] (/home/ec2-user/.agc/cdk/node_modules/aws-cdk-lib/aws-ec2/lib/instance-types.ts:666:13)
2022-04-29T22:34:03Z 𝒊      at /home/ec2-user/.agc/cdk/lib/util/instance-types.ts:179:83
2022-04-29T22:34:03Z 𝒊      at Array.filter (<anonymous>)
2022-04-29T22:34:03Z 𝒊      at Object.exports.getInstanceTypesForBatch (/home/ec2-user/.agc/cdk/lib/util/instance-types.ts:179:45)
2022-04-29T22:34:03Z 𝒊      at Batch.renderComputeEnvironment (/home/ec2-user/.agc/cdk/lib/constructs/batch.ts:203:24)
2022-04-29T22:34:03Z 𝒊      at new Batch (/home/ec2-user/.agc/cdk/lib/constructs/batch.ts:93:36)
2022-04-29T22:34:03Z 𝒊      at MiniwdlEngineConstruct.renderBatch (/home/ec2-user/.agc/cdk/lib/stacks/engines/miniwdl-engine-construct.ts:117:12)
2022-04-29T22:34:03Z 𝒊      at new MiniwdlEngineConstruct (/home/ec2-user/.agc/cdk/lib/stacks/engines/miniwdl-engine-construct.ts:36:30)
2022-04-29T22:34:03Z 𝒊      at ContextStack.renderMiniwdlStack (/home/ec2-user/.agc/cdk/lib/stacks/context-stack.ts:87:5)
2022-04-29T22:34:03Z 𝒊      at new ContextStack (/home/ec2-user/.agc/cdk/lib/stacks/context-stack.ts:37:14)
2022-04-29T22:34:03Z 𝒊  Subprocess exited with error 1
2022-04-29T22:34:03Z ✘  Failed to deploy context 'cpuctxminiwdl'. Below is the log for that deployment
2022-04-29T22:34:03Z ✘  /home/ec2-user/.agc/cdk/node_modules/aws-cdk-lib/aws-ec2/lib/instance-types.ts:666
2022-04-29T22:34:03Z ✘        throw new Error('Malformed instance type identifier');
2022-04-29T22:34:03Z ✘              ^
2022-04-29T22:34:03Z ✘  Error: Malformed instance type identifier
2022-04-29T22:34:03Z ✘      at InstanceType.get architecture [as architecture] (/home/ec2-user/.agc/cdk/node_modules/aws-cdk-lib/aws-ec2/lib/instance-types.ts:666:13)
2022-04-29T22:34:03Z ✘      at /home/ec2-user/.agc/cdk/lib/util/instance-types.ts:179:83
2022-04-29T22:34:03Z ✘      at Array.filter (<anonymous>)
2022-04-29T22:34:03Z ✘      at Object.exports.getInstanceTypesForBatch (/home/ec2-user/.agc/cdk/lib/util/instance-types.ts:179:45)
2022-04-29T22:34:03Z ✘      at Batch.renderComputeEnvironment (/home/ec2-user/.agc/cdk/lib/constructs/batch.ts:203:24)
2022-04-29T22:34:03Z ✘      at new Batch (/home/ec2-user/.agc/cdk/lib/constructs/batch.ts:93:36)
2022-04-29T22:34:03Z ✘      at MiniwdlEngineConstruct.renderBatch (/home/ec2-user/.agc/cdk/lib/stacks/engines/miniwdl-engine-construct.ts:117:12)
2022-04-29T22:34:03Z ✘      at new MiniwdlEngineConstruct (/home/ec2-user/.agc/cdk/lib/stacks/engines/miniwdl-engine-construct.ts:36:30)
2022-04-29T22:34:03Z ✘      at ContextStack.renderMiniwdlStack (/home/ec2-user/.agc/cdk/lib/stacks/context-stack.ts:87:5)
2022-04-29T22:34:03Z ✘      at new ContextStack (/home/ec2-user/.agc/cdk/lib/stacks/context-stack.ts:37:14)
2022-04-29T22:34:03Z ✘  Subprocess exited with error 1

2022-04-29T22:34:03Z ✘   error="1 context deployment failures"
Error: an error occurred invoking 'context deploy'
with variables: {contexts:[] deployAll:false}
caused by: 1 context deployment failures
suggestion: To resolve failure 1, determine the cause of: exit status 1

Expected Behavior
I can use instance familiy names (e.g. "c5", "m5", "r5", etc) in addition to explicitly listing specific instance types, as the documentation states.
Actual Behavior
Using instance family names is not accepted. Deploying a context throws and error. Reverting to specific instance types e.g "c5.xlarge" works.
Screenshots
Additional Context
Operating System: Amazon Linux 2
AGC Version: 1.3.0
Was AGC setup with a custom bucket: no
Was AGC setup with a custom VPC: no

Upvoted. Please at least update in the documentation for now.


fix(valuecard): support long and short errors

Summary

Need to support reporting both a short form and long form of the error message, depending on the available card size

Change List (commits, features, bugs, etc)
Acceptance Test (how to verify the PR)

Check the new short form and long form stories

:tada: This PR is included in version 1.64.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.64.2 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Add Shutdown Functions for Renderer

Currently resources are only freed after the main program terminates.  This makes it so that any objects that the 2D and 3D render use after instantiation are not released even if a layer is removed or the specific renderer is no longer needed.
This can be solved by implementing the Shutdown functions for the 2D and 3D renderers.

Implemented in Commit: be9e8033350fb4363b220b5fce87346743037880


Trying to combine road_following program with detectnet program jetson nano jetracer

@dusty-nv
Hello,
I am trying to combine your detectnet program with a road_rollowing program for the jetson nano jetracer. The road_following program uses csiCamera and detectnet uses gStreamer so it has been a little bit of a struggle trying to combine them into one. Below is the code for each program, the combined program, and the error message I receive when trying to run it.

I am trying to combine the programs so I can make the car stop whenever it recognizes a stop sign. Any help with fixing this would be much appreciated.
Thank you so much.

Hi @CamRoni1339, try calling cudaFromNumpy() followed by cudaConvertColor() on the image returned by cv2 camera.read() before passing it to net.Detect().   No idea what passing camera.cap to net.Detect() would do.

https://github.com/dusty-nv/jetson-inference/blob/master/docs/aux-image.md#converting-from-numpy-arrays
https://github.com/dusty-nv/jetson-utils/blob/master/python/examples/cuda-from-cv.py

@dusty-nv
Hello,
I'm sorry to be asking what has to be simple questions but I am new to this and am not very good at it. I have tried calling cudafromnumpy() and cudaconvertcolor(), but I end up getting the error shown below. I'm sure that I am just simply not calling it correctly, so if you could show me how to do that, that would be great.

Thank you so much for your time.

UPDATE
I figured out the format for cudaFromNumpy, but if you could show me what to do for cudaConvertColor that would be great.
Thank you so much for you time again.

@CamRoni1339 see this example that I had linked to above that shows the use of cudaFromNumpy/cudaConvertColor to convert an OpenCV image:
https://github.com/dusty-nv/jetson-utils/blob/master/python/examples/cuda-from-cv.py

Thank you so much for the help! I have gotten to work.


Indenting in DUs

Document currently reads
> Indent | in type definition by 4 spaces:
Should probably be rephrased slightly to reflect the fact that people may not be using exactly four spaces (though generally they should be!).

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

ID: 8c09996f-24ac-cf39-ef43-d7909cbc2b89
Version Independent ID: 1efdd523-8552-6421-e149-74f76826ef8f
Content: F# code formatting guidelines
Content Source: docs/fsharp/style-guide/formatting.md
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

We're going with 4 as the canonical spacing in the document. It's mentioned at the top and recommended in other areas as well.


Update README.md

Removed Closed PR about keplr integration.
Added OnBloc docs link

Thanks for your contribution @omniwired


reverted the chef version to 16.13.16 due to mtls scenario failure

Signed-off-by: jan shahid shaik<EMAIL_ADDRESS>Description
Mtl sceanrio is failing with chef version 16.16.13.
https://buildkite.com/chef/chef-umbrella-main-chef-server/builds/781#e1adf7b6-ce5f-48f2-bdc5-702e9199f8b8
Issues Resolved
knife issue in the umbrella mtl scenario
https://buildkite.com/chef/chef-umbrella-main-chef-server/builds/781#e1adf7b6-ce5f-48f2-bdc5-702e9199f8b8
Check List

[ ] New functionality includes tests
[ ] All buildkite tests pass
[ ] Full omnibus build and tests in buildkite pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/main/CONTRIBUTING.md#developer-certification-of-origin-dco
[ ] PR title is a worthy inclusion in the CHANGELOG

Will re-run through adhoc and umbrella once the verify pipeline is successful.


Improve snapshot endpoints & UI

Endpoints now support things like this http://localhost:9091/snapshots/input?format=yaml&clusters=cluster-1::cluster-2&namespaces=bookinfo
New URL params:

format
clusters
namespaces
resourceTypes
Improved UI to utilize new options & added direct download button.

Tested various filtering options extensively.
BOT NOTES:
resolves https://github.com/solo-io/skv2/issues/347

@Sodman maybe when generating the html we wrap the capture of the filters in a try with a timeout. If it does not come back we render a simple html template (as it was previously). This way we serve up basic functionality still and protect against other, non performance, related issues as well.


Add support to output provenance information (tool version, options, environment, etc)

Added in 2.1.0


settings: Rename display_settings_labels to preferences_settings_labels.

Finished renaming display_settings_labels to preferences_settings_labels
This helps fixes part of issue #26874.
In this pull request
Renamed display_settings_labels to preferences_settings_labels.
Changed Files:
web/src/settings.js
web/src/settings_config.ts

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @Aditya8840!
I think you can start making PRs that stack several similar commits.


Improvements in Frontend UI

Learn more about HMTL and CSS.
Try making unique HTML templates, instead of using prepared ones.

HTML and CSS with Bootstrap framework is learned via (link 1)[https://getbootstrap.com/docs/5.2/components/navbar/#color-schemes].


Teams output should support adding Links

Background
Description
The Microsoft Teams output, should support adding Links within the card via link buttons
Desired Change
Ability to pass multiple link text and url pairs to the teams output via @teams.links or something similar

Ability added in #1168


Import the Foundation overlay codebase from the Swift repository

This PR imports the Foundation overlay codebase from the Swift
compiler repository up to commit 7f2185d3 on 2020-10-28.
This includes the associated regression tests (ported to XCTest), and
comes complete with a working Xcode project file to build the overlay.
The intention is that the Foundation overlay will be maintained in
this repository from now on; the original codebase will be removed
from the Swift repo once we teach the compiler's build system to pick
up the overlay from here.
Note that while there is significant overlap between functionality,
implementations and test cases between swift-corelibs-foundation and
the Foundation overlay, this particular PR makes no effort to share
code or run unified tests across the two projects.

To build the overlay, you currently need to point Xcode to a local
build of the Swift compiler & stdlib by manually overriding the
SWIFT_EXEC and SWIFT_LIBRARY_PATH build settings to the location of
your custom Swift compiler executable and Swift standard library,
respectively:
env SWIFT_EXEC=.../build/Ninja-ReleaseAssert/swift-macosx-x86_64/bin/swiftc \
  SWIFT_LIBRARY_PATH=.../build/Ninja-ReleaseAssert/swift-macosx-x86_64/lib/swift/macosx \
  xcodebuild

(Replacing macosx with the platform you're targeting, as needed.)

This PR preserves the full commit history of the imported files,
including attribution and commit messages. However, as this is a
partial import, you cannot build the Foundation overlay from
historical commits -- you'll need to use the Swift repository for
that.
The Swift repository's mailmap file as of the commit above was used to
update/fix author names and email addresses.
Resolves rdar://70903483.

All: we are moving things around so that Foundation sources are all together, for both Darwin and off-Darwin.

cc @parker

cc @parkera

@swift-ci please test

@lorentey LGTM

@lorentey Let's give @parkera time to respond before we land.

Note: The bits that don't come verbatim from the Swift repository are isolated in the last dozen or so commits:
https://github.com/apple/swift-corelibs-foundation/pull/2915/files/c7485fb359db306fb73679a2ae1e7444cf1a66d1..b46360970814d1a83de9bc120027f86037494a4b

@swift-ci please test

@swift-ci test linux platform

@swift-ci test linux platform

@swift-ci test linux


Added Pages

Description of your changes
YOUR DESCRIPTION GOES HERE. KEEP IS CONCISE, NO FLUFF.
Category & Link

[ ] NEW FEATURE
[ ] BUG FIX
[ ] CORE CODE
[ ] DOCUMENTATION

Checklist before requesting review

[ ] My code utilizes up to date origin code
[ ] I have performed a self-review of my code.
[ ] I have commented my code, especially in hard-to-understand areas.
[ ] My changes generate no new warnings.

Additional

[ ] This code requires explicit review.
[ ] This code is unfinished and requires assistance.
[ ] This code is dependant on another feature that is still under development.

Issues with merge


fzf-git-add don't execute git add after select

When I select files and press Enter, i see git add -- in command line.

Plugin load with antigen, theme bira, other plugins disabled, macOS.
git add $(git status --porcelain | grep "^.[MD?]" | cut -c 4- | fzf -m)

works fine.
git 2.12.0
zsh 5.3.1

Sorry, it depends of my fix of #8, if I comment
selector-filter "awk '{print \$2}'"

widget executes correct.

Thank you for report!
However I want to view short format and relative path, so I fixed in a different way.
Please try again after update. :bowing_man:

Now it work fine!


Migrate article: Aiven Security Compliance #1081

https://github.com/aiven/devportal/issues/1081
What changed, and why it matters

Closing, we'll point people to https://aiven.io/security-compliance


NullPointerException in FragmentManager.saveFragmentBasicState(...)

FragmentManager: prevented NullPointerException when saving some types of Fragments where mSavedViewState is null and mUserVisibleHint is false.
Instances of this class were causing the NPE:
public abstract class LayoutFragment extends Fragment {
public static LayoutFragment newInstance(final int layoutId) {
	return new LayoutFragment() {
		@Override
		public int getLayoutResourceId() {
			return layoutId;
		}
	};
}

public abstract int getLayoutResourceId();

@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
		Bundle savedInstanceState) {
	return inflater.inflate(getLayoutResourceId(), container, false);
}

}

This is already fixed on the dev branch but I really appreciate the pull request. I've been sitting on it for about two weeks. I swear I'll release 3.5.1 tonight.


[Feature request] Make async: True do everything under the hood

From a user perspective, the less setup required the better. I personally find the second example (example.py) more user-friendly especially for non-very technical users.
The user has to just add an async: True and don't bother tinkering/figuring out stuff for another ~hour about how Queue or something else works.
@jvmvik @ilyazub @hartator what do you guys think?
@aliayar @marm123 @schaferyan have you guys noticed similar issues for the users or have any users requested similar things?

What if instead of this:
# async batch requests: https://github.com/serpapi/google-search-results-python#batch-asynchronous-searches

from serpapi import YoutubeSearch
from queue import Queue
import os, re, json

queries = [
    'burly',
    'creator',
    'doubtful'
]

search_queue = Queue()

for query in queries:
    params = {
        'api_key': '...',
        'engine': 'youtube',
        'device': 'desktop',
        'search_query': query,
        'async': True,                   # ❗
        'no_cache': 'true'
    }
    search = YoutubeSearch(params)
    results = search.get_dict()

    if 'error' in results:
        print(results['error'])
        break

    print(f"Add search to the queue with ID: {results['search_metadata']}")
    search_queue.put(results)

data = []

while not search_queue.empty():
    result = search_queue.get()
    search_id = result['search_metadata']['id']

    print(f'Get search from archive: {search_id}')
    search_archived = search.get_search_archive(search_id)

    print(f"Search ID: {search_id}, Status: {search_archived['search_metadata']['status']}")

    if re.search(r'Cached|Success', search_archived['search_metadata']['status']):
        for video_result in search_archived.get('video_results', []):
            data.append({
                'title': video_result.get('title'),
                'link': video_result.get('link'),
                'channel': video_result.get('channel').get('name'),
            })
    else:
        print(f'Requeue search: {search_id}')
        search_queue.put(result)

Users can do something like this and we handle everything under the hood:
# example.py
# testable example
# example import: from serpapi import async_search

from async_search import async_search
import json

queries = [
    'burly',
    'creator',
    'doubtful',
    'minecraft'
]

# or as we typically pass params dict
data = async_search(queries=queries, api_key='...', engine='youtube', device='desktop')

print(json.dumps(data, indent=2))
print('All searches completed')

Under the hood code example:
# async_search.py
# testable example

from serpapi import YoutubeSearch
from queue import Queue
import os, re

search_queue = Queue()

def async_search(queries, api_key, engine, device):
    data = []
    for query in queries:
        params = {
            'api_key': api_key,
            'engine': engine,
            'device': device,
            'search_query': query,
            'async': True,
            'no_cache': 'true'
        }
        search = YoutubeSearch(params)
        results = search.get_dict()

        if 'error' in results:
            print(results['error'])
            break

        print(f"Add search to the queue with ID: {results['search_metadata']}")
        search_queue.put(results)

    while not search_queue.empty():
        result = search_queue.get()
        search_id = result['search_metadata']['id']

        print(f'Get search from archive: {search_id}')
        search_archived = search.get_search_archive(search_id)

        print(f"Search ID: {search_id}, Status: {search_archived['search_metadata']['status']}")

        if re.search(r'Cached|Success', search_archived['search_metadata']['status']):
            for video_result in search_archived.get('video_results', []):
                data.append({
                    'title': video_result.get('title'),
                    'link': video_result.get('link'),
                    'channel': video_result.get('channel').get('name'),
                })
        else:
            print(f'Requeue search: {search_id}')
            search_queue.put(result)

    return data

Is there a specific reason we haven't done it before?

We have received a few requests asking for an easier and faster way to use but nothing particular Dimitriy.


fibo-quickstart.ttl missing 97 prefixes

I assume dev.fibo-quickstart.ttl should include all ontologies.
The following 97 ontologies are loaded by LoadFIBODev.ttl but have no prefixes defined in fibo-quickstart.ttl:
https://spec.edmcouncil.org/fibo/ontology/BP/Process/FinancialContextAndProcess/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/AgencyMBSIssuance/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/DebtIssuance/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/EquitiesIPOIssuance/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/IssuanceDocuments/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/IssuanceProcess/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/MBSIssuance/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/MuniIssuance/
https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/PrivateLabelMBSIssuance/
https://spec.edmcouncil.org/fibo/ontology/CAE/CorporateEvents/CorporateActionsEvents/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/AssetBaskets/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/AssetDerivatives/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/BondOptions/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/BondReturnSwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquityForwards/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquityOptions/
https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquitySwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/Commodities/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditiesContracts/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommodityForwards/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommodityOptions/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditySpots/
https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditySwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/CreditDerivatives/CreditDefaultSwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ContractsForDifference/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/DerivativesMasterAgreements/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Forwards/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/OptionContractsOnFutures/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Options/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ParticipationNotes/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ReturnSwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/RightsAndWarrants/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Spots/
https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Swaptions/
https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/DerivativesStandardizedTerms/
https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/ExchangeTradedOptions/
https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/Futures/
https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxContracts/
https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxForwards/
https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxOptions/
https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxSpots/
https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxSwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/ForwardRateAgreements/
https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/InflationSwaps/
https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/IROptions/
https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/OTCIndexOptions/
https://spec.edmcouncil.org/fibo/ontology/FBC/DebtAndEquities/CreditFacilities/
https://spec.edmcouncil.org/fibo/ontology/FND/AgreementsExt/ContractElements/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/EconomicResources/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/MarketTransactions/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/QuantifiedResources/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/REAClaimsEvents/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/REATransactions/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/SecuritiesTransactions/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/SupplyTransactions/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionAccounting/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionEvents/
https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionsExtended/
https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Values/
https://spec.edmcouncil.org/fibo/ontology/LOAN/Loans/LoanBasicTerms/
https://spec.edmcouncil.org/fibo/ontology/LOAN/Loans/LoansRegulatory/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/ConstructionLoansTemporal/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoanPhases/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansEvents/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansStatus/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansTemporal/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/CommercialLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/ConstructionLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/CreditProducts/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/GeneralLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/LoanProducts/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/MortgageLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/PersonalLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/SecuredLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/StudentLoans/
https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/UnsecuredLoans/
https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/
https://spec.edmcouncil.org/fibo/ontology/MD/DebtTemporal/DebtAnalytics/
https://spec.edmcouncil.org/fibo/ontology/MD/DebtTemporal/DebtPricingYields/
https://spec.edmcouncil.org/fibo/ontology/MD/DerivativesTemporal/ETOptionsTemporal/
https://spec.edmcouncil.org/fibo/ontology/MD/DerivativesTemporal/FuturesTemporal/
https://spec.edmcouncil.org/fibo/ontology/MD/EquityTemporal/EquityPricing/
https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/InstrumentTemporalTerms/
https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/SecurityCreditStatuses/
https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/SecurityTradingStatuses/
https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/TemporalConcepts/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/AssetBackedSecurities/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/AssetBackedSPVs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CBOs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CDOs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CLOs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CMOs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/LoanParticipationNotes/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/MortgageBackedSecurities/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/PoolBackedSecurities/
https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/SyntheticCDOs/
https://spec.edmcouncil.org/fibo/ontology/SEC/Equities/DepositaryReceipts/

The total dev.ttl.zip has 98 prefixes not defined in fibo-quickstart. I checked, the first URL below is used in quickstart so should be defined.
These are probably the same 97 as listed above plus one extra (haven't checked which one):
@prefix fibo-bp-iss-ambs: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/AgencyMBSIssuance/> .
@prefix fibo-bp-iss-dbti: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/DebtIssuance/> .
@prefix fibo-bp-iss-doc: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/IssuanceDocuments/> .
@prefix fibo-bp-iss-ipo: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/EquitiesIPOIssuance/> .
@prefix fibo-bp-iss-mbs: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/MBSIssuance/> .
@prefix fibo-bp-iss-muni: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/MuniIssuance/> .
@prefix fibo-bp-iss-pmbs: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/PrivateLabelMBSIssuance/> .
@prefix fibo-bp-iss-prc: <https://spec.edmcouncil.org/fibo/ontology/BP/SecuritiesIssuance/IssuanceProcess/> .
@prefix fibo-bp-prc-fcp: <https://spec.edmcouncil.org/fibo/ontology/BP/Process/FinancialContextAndProcess/> .
@prefix fibo-cae-ce-cae: <https://spec.edmcouncil.org/fibo/ontology/CAE/CorporateEvents/CorporateActionsEvents/> .
@prefix fibo-der-ass-ass: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/AssetDerivatives/> .
@prefix fibo-der-ass-bas: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/AssetBaskets/> .
@prefix fibo-der-ass-bo: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/BondOptions/> .
@prefix fibo-der-ass-brs: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/BondReturnSwaps/> .
@prefix fibo-der-ass-eqf: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquityForwards/> .
@prefix fibo-der-ass-eqo: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquityOptions/> .
@prefix fibo-der-ass-eqs: <https://spec.edmcouncil.org/fibo/ontology/DER/AssetDerivatives/EquitySwaps/> .
@prefix fibo-der-com-com: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/Commodities/> .
@prefix fibo-der-com-ctr: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditiesContracts/> .
@prefix fibo-der-com-fwd: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommodityForwards/> .
@prefix fibo-der-com-opt: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommodityOptions/> .
@prefix fibo-der-com-sp: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditySpots/> .
@prefix fibo-der-com-sw: <https://spec.edmcouncil.org/fibo/ontology/DER/CommoditiesDerivatives/CommoditySwaps/> .
@prefix fibo-der-cr-cds: <https://spec.edmcouncil.org/fibo/ontology/DER/CreditDerivatives/CreditDefaultSwaps/> .
@prefix fibo-der-der-cof: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/OptionContractsOnFutures/> .
@prefix fibo-der-der-fwd: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Forwards/> .
@prefix fibo-der-der-opt: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Options/> .
@prefix fibo-der-der-rsw: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ReturnSwaps/> .
@prefix fibo-der-der-sp: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Spots/> .
@prefix fibo-der-der-spn: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/Swaptions/> .
@prefix fibo-der-drc-cfd: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ContractsForDifference/> .
@prefix fibo-der-drc-ma: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/DerivativesMasterAgreements/> .
@prefix fibo-der-drc-pn: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/ParticipationNotes/> .
@prefix fibo-der-drc-raw: <https://spec.edmcouncil.org/fibo/ontology/DER/DerivativesContracts/RightsAndWarrants/> .
@prefix fibo-der-etd-eto: <https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/ExchangeTradedOptions/> .
@prefix fibo-der-etd-fut: <https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/Futures/> .
@prefix fibo-der-etd-std: <https://spec.edmcouncil.org/fibo/ontology/DER/ExchangeTradedDerivatives/DerivativesStandardizedTerms/> .
@prefix fibo-der-fx-ctr: <https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxContracts/> .
@prefix fibo-der-fx-fwd: <https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxForwards/> .
@prefix fibo-der-fx-opt: <https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxOptions/> .
@prefix fibo-der-fx-sp: <https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxSpots/> .
@prefix fibo-der-fx-sw: <https://spec.edmcouncil.org/fibo/ontology/DER/FxDerivatives/FxSwaps/> .
@prefix fibo-der-rat-fra: <https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/ForwardRateAgreements/> .
@prefix fibo-der-rat-indo: <https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/OTCIndexOptions/> .
@prefix fibo-der-rat-iro: <https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/IROptions/> .
@prefix fibo-der-rtd-isw: <https://spec.edmcouncil.org/fibo/ontology/DER/RateDerivatives/InflationSwaps/> .
@prefix fibo-fbc-dae-crf: <https://spec.edmcouncil.org/fibo/ontology/FBC/DebtAndEquities/CreditFacilities/> .
@prefix fibo-fnd-agrx-ele: <https://spec.edmcouncil.org/fibo/ontology/FND/AgreementsExt/ContractElements/> .
@prefix fibo-fnd-arr-arr: <https://spec.edmcouncil.org/fibo/ontology/FND/Arrangements/Documents/> .
@prefix fibo-fnd-txn-acc: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionAccounting/> .
@prefix fibo-fnd-txn-cle: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/REAClaimsEvents/> .
@prefix fibo-fnd-txn-ecr: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/EconomicResources/> .
@prefix fibo-fnd-txn-ev: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionEvents/> .
@prefix fibo-fnd-txn-mkt: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/MarketTransactions/> .
@prefix fibo-fnd-txn-qr: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/QuantifiedResources/> .
@prefix fibo-fnd-txn-rea: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/REATransactions/> .
@prefix fibo-fnd-txn-sec: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/SecuritiesTransactions/> .
@prefix fibo-fnd-txn-sup: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/SupplyTransactions/> .
@prefix fibo-fnd-txn-txnx: <https://spec.edmcouncil.org/fibo/ontology/FND/TransactionsExt/TransactionsExtended/> .
@prefix fibo-fnd-utl-val: <https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/Values/> .
@prefix fibo-loan-loan-loan: <https://spec.edmcouncil.org/fibo/ontology/LOAN/Loans/LoanBasicTerms/> .
@prefix fibo-loan-loan-reg: <https://spec.edmcouncil.org/fibo/ontology/LOAN/Loans/LoansRegulatory/> .
@prefix fibo-loan-tem-cl: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/ConstructionLoansTemporal/> .
@prefix fibo-loan-tem-ev: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansEvents/> .
@prefix fibo-loan-tem-ph: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoanPhases/> .
@prefix fibo-loan-tem-sta: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansStatus/> .
@prefix fibo-loan-tem-tem: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoansTemporal/LoansTemporal/> .
@prefix fibo-loan-typ-cl: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/ConstructionLoans/> .
@prefix fibo-loan-typ-com: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/CommercialLoans/> .
@prefix fibo-loan-typ-cr: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/CreditProducts/> .
@prefix fibo-loan-typ-gen: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/GeneralLoans/> .
@prefix fibo-loan-typ-mtg: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/MortgageLoans/> .
@prefix fibo-loan-typ-per: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/PersonalLoans/> .
@prefix fibo-loan-typ-prod: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/LoanProducts/> .
@prefix fibo-loan-typ-sec: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/SecuredLoans/> .
@prefix fibo-loan-typ-stu: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/StudentLoans/> .
@prefix fibo-loan-typ-uns: <https://spec.edmcouncil.org/fibo/ontology/LOAN/LoanTypes/UnsecuredLoans/> .
@prefix fibo-md-civx-fun: <https://spec.edmcouncil.org/fibo/ontology/MD/CIVTemporal/FundsTemporal/> .
@prefix fibo-md-dbtx-aly: <https://spec.edmcouncil.org/fibo/ontology/MD/DebtTemporal/DebtAnalytics/> .
@prefix fibo-md-dbtx-py: <https://spec.edmcouncil.org/fibo/ontology/MD/DebtTemporal/DebtPricingYields/> .
@prefix fibo-md-der-fut: <https://spec.edmcouncil.org/fibo/ontology/MD/DerivativesTemporal/FuturesTemporal/> .
@prefix fibo-md-derx-eto: <https://spec.edmcouncil.org/fibo/ontology/MD/DerivativesTemporal/ETOptionsTemporal/> .
@prefix fibo-md-eqx-pri: <https://spec.edmcouncil.org/fibo/ontology/MD/EquityTemporal/EquityPricing/> .
@prefix fibo-md-temx-crs: <https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/SecurityCreditStatuses/> .
@prefix fibo-md-temx-ins: <https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/InstrumentTemporalTerms/> .
@prefix fibo-md-temx-tem: <https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/TemporalConcepts/> .
@prefix fibo-md-temx-trs: <https://spec.edmcouncil.org/fibo/ontology/MD/TemporalCore/SecurityTradingStatuses/> .
@prefix fibo-sec-dbt-ab-abs: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/AssetBackedSecurities/> .
@prefix fibo-sec-dbt-ab-cbo: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CBOs/> .
@prefix fibo-sec-dbt-ab-cdo: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CDOs/> .
@prefix fibo-sec-dbt-ab-clo: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CLOs/> .
@prefix fibo-sec-dbt-ab-cmo: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/CMOs/> .
@prefix fibo-sec-dbt-ab-lpn: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/LoanParticipationNotes/> .
@prefix fibo-sec-dbt-ab-mbs: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/MortgageBackedSecurities/> .
@prefix fibo-sec-dbt-ab-pbs: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/PoolBackedSecurities/> .
@prefix fibo-sec-dbt-ab-spv: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/AssetBackedSPVs/> .
@prefix fibo-sec-dbt-ab-syn: <https://spec.edmcouncil.org/fibo/ontology/SEC/Debt/AssetBackedSecurities/SyntheticCDOs/> .
@prefix fibo-sec-eq-dr: <https://spec.edmcouncil.org/fibo/ontology/SEC/Equities/DepositaryReceipts/> .

I noticed this today as well, and was about to create an issue about it, but I saw this one, so I'll use it.
The issue here isn't with quickstart itself, that's a symptom.  The issue is that many files (and I just wrote a script to find out which ones they are, and got the same number as you) don't specify the sm:fileAbbreviation.
I updated my script to actually make the changes to add that in.   I want to do this before the Q2 release goes out.  I'm going to assign this one to me.

These are all provisional ontologies - so it's possible that they have not been treated as rigorously as the released ones.


Select-apps does not fill terminal

select-apps will leave empty space at the bottom of the terminal, depending on terminal size.  Instead, it should fill the list of games to use all available vertical space.

Fix for this was included in https://github.com/tpill90/steam-lancache-prefill/pull/80