Upgrading from 3.0.0-beta.19 to 3.1.0 gives a lot of errors

Description
It can build fine with:
"next": "^13.5.6",
"next-intl": "3.0.0-beta.19",
when try to upgrade next-intl to 3.1.0, I get a lot of errors when builing. At the same time I upgrade next to 14.0.3
It gives an error like this for each path in the app
Error occurred prerendering page "/es/about". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the unstable_setRequestLocale API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router-server-components#static-rendering
at /home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65554
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:179223
at l (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:66180)
at f (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64882)
at h (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64966)
at v (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65053)
at b (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65310)
at em (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:128381)
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140081
at Object.toJSON (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:143659)
Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the unstable_setRequestLocale API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router-server-components#static-rendering
at /home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65554
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:179223
... 5 lines matching cause stack trace ...
at em (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:128381)
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140081
at Object.toJSON (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:143659) {
[cause]: n [Error]: Dynamic server usage: Page couldn't be rendered statically because it used headers. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
at l (/home/oaj/projects/kanowa_app/.next/server/chunks/4312.js:1:3737)
at d (/home/oaj/projects/kanowa_app/.next/server/chunks/4312.js:1:1093)
at /home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65456
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:179223
at l (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:66180)
at f (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64882)
at h (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64966)
at v (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65053)
at b (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65310)
at em (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:128381) {
digest: 'DYNAMIC_SERVER_USAGE'
}
}
Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the unstable_setRequestLocale API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router-server-components#static-rendering
at /home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65554
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:179223
... 5 lines matching cause stack trace ...
at em (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:128381)
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:140081
at Object.toJSON (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:143659) {
[cause]: n [Error]: Dynamic server usage: Page couldn't be rendered statically because it used headers. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
at l (/home/oaj/projects/kanowa_app/.next/server/chunks/4312.js:1:3737)
at d (/home/oaj/projects/kanowa_app/.next/server/chunks/4312.js:1:1093)
at /home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65456
at /home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:179223
at l (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:66180)
at f (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64882)
at h (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:64966)
at v (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65053)
at b (/home/oaj/projects/kanowa_app/.next/server/chunks/5121.js:124:65310)
at em (/home/oaj/projects/kanowa_app/node_modules/.pnpm/next@14.0.3_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:128381) {
digest: 'DYNAMIC_SERVER_USAGE'
}
}
This the about page mentiont in the error  message:
"use client"
import {NextPage} from "next";

export default function About() {

    return (

About

    )
}

Mandatory reproduction URL (CodeSandbox or GitHub repository)

Reproduction description
Steps to reproduce:

Open reproduction
Click on …
See error: …

Expected behaviour
No errors

Sorry, there was no reproduction provided, therefore I can not look into this.
Please be careful to review the release notes for 3.0 and consult the examples when in doubt.


WIP istanbul bump

Summary
/cc @coreyfarrell. I've updated some snapshots that looked correct, but left a few alone. ~I'll update after you've fixed the sourceFinder issue~

Test plan
Green CI. We'll need to figure out what to do about TS types. Should probably wait for this to be stable as well. We can upgrade without a new major anyways as this is all internal stuff. I wouldn't consider changes in the coverage report to be breaking

We can upgrade without a new major anyways as this is all internal stuff.

Only if you've already dropped node.js 6 (these new versions require node.js 8).

Yeah, we've landed that on master, just not released yet.

I see we have a windows test failure, though...

Codecov Report

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

@@            Coverage Diff             @@
##           master    #9192      +/-   ##
==========================================
+ Coverage   64.85%   64.88%   +0.03%
==========================================
  Files         279      276       -3
  Lines       11744    11741       -3
  Branches     2888     2888
==========================================
+ Hits         7616     7618       +2
+ Misses       3510     3506       -4
+ Partials      618      617       -1

Impacted Files
Coverage Δ

...ckages/jest-reporters/src/generateEmptyCoverage.ts
88.88% <ø> (ø)
:arrow_up:

packages/jest-reporters/src/coverage_reporter.ts
61.53% <100%> (ø)
:arrow_up:

e2e/babel-plugin-jest-hoist/__test_modules__/b.js

...babel-plugin-jest-hoist/__test_modules__/Mocked.js

e2e/babel-plugin-jest-hoist/__test_modules__/a.js

packages/expect/src/utils.ts
96.2% <0%> (+1.26%)
:arrow_up:

Continue to review full report at Codecov.

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

added some ts-ignores just to verify this is good to go beyond type updates, and it seems so

Let's land this so it can be included in the upcoming beta release of jest


Dequeue efficient queue using stack

💥 Proposal
Implementing a Queue using two stacks and making it Dequeue efficient in C++ language.
Have you read the Contributing Guidelines on Pull Requests?
Yes
Implementing a Queue using two stacks and making it Dequeue efficient in C++ language.

/assign


Add support for Django 1.11

It looks like upstream already supports Django 1.11, but some updates needed to be made for tests.

I should say r+

@jlward Is it possible to write a changelog for release note please?

I can add an update note. I have found a bug in testing (looks like it also affects django 1.8). Do you want me to update this PR or make a new one? I have a test with a fix already.

It also seems travis no longer has a python 3.3 interpreter, I would be happy to drop that from the travis config in this PR as well, if you'd like @safwanrahman

@jlward Sure, update it and add it in changelog.

Updated the issue description with a blurb about the follow up issue I fixed. Let me know if there is anything else I can do :)


Implement code points validator

Fixes #875
Implemented based on graphemes validation.

Thank you for creating this PR! I will try to review and merge it in the next weeks. 🙏

I might export the implementation of _getCodePointCoun to other validators (e.g. Zod) in the future.

I just want to let you know that I am focusing on our v1 release first before reviewing this PR.

That's not good news. I'll wait for v1.1.0.
And I want to get permission to publish _getCodePointCount as my independent package from you.

Yes, feel free to create your own package. No permission required.


Searching for nothing actually searches for "OR"

See https://name-resolution-sri.renci.org/lookup?string=&autocomplete=true&offset=0&limit=10
This is presumably because when autocomplete=true, we turn the query into {query} OR {query}*, so we're really just searching for that OR now.

This is now fixed, although what we do instead is return everything in our Solr database sorted by decreasing clique identifier count. Cute.
I've written a PR to replace that with returning an empty list (https://github.com/TranslatorSRI/NameResolution/pull/167); once that's merged, it'll close this ticket.


Create lora objects into heap

In order to reduce stack usage, create lora objects into heap.

Wait for 5.8.3 to be released, merge only after that

Why do we need to create them on the heap now? That's just moving the problem?

@kivaisan @AnttiKauppila It's actually easier to handle memory outage if the stuff is on stack. It has been the norm lately in Mbed world to use stack for storage.

Ok. Good point. I'll close this PR.


how about the ap in widerface compared with star-cloud version centerface?

Since the ap's computaion method is different from the star-cloud , Maybe there is nothing to compare.  If you are intertested to it ,you could compare them using the same method.

@yokings  Hi, I have added the pretrained model 's  ap on the wilderface. And the centerface's ap is computed with the multi-scale,while I got it by single-scale withe voc's ap

@yokings Hi, I have added the pretrained model 's ap on the wilderface. And the centerface's ap is computed with the multi-scale,while I got it by single-scale withe voc's ap

thanks ,good job

thansk goog job


Added single stream read/write, callback capability

This adds functionality and functions similar to the Python PyAudio interface to the PortAudio library.

As I mentioned in #51, I added some more commits on top of your changes in that PR and pushed to the wherrera_10_test branch, most importantly getting the tests working again, including travis testing.
Would you mind rebasing this onto that branch? Currently I can't run the tests as-is on this PR (are they working for you?). Also, most of the commits here are just the name of the file that was created or updated. Can you squash down to fewer and more descriptive commits? It makes it a lot easier for me to see what's going on.
Thanks a lot! I'm looking forward to digging into these changes and getting this merged.

It seems that I cannot get the GitHub web site to do a rebase, so I deleted
the fork, reforked master, and changed portaudio.jl, README.md, and
build.jl plus added the example files. GitHub it seems does not like trying
to fork your forks, it wants to fork from master only.
I'll hold off on sending a pull request til you ask though. I have audio
working, which means that I can believe in what Julia does with streaming
data in general. So I will be able to get back to the actual
work-in-progress, which is with much lower frequency, multiband EDF data
file stream files, not audio really.
--Bill
On Thu, Dec 3, 2015 at 10:03 AM, Spencer Russell<EMAIL_ADDRESS>wrote:

As I mentioned in #51 https://github.com/ssfrr/AudioIO.jl/pull/51, I
added some more commits on top of your changes in that PR and pushed to the
wherrera_10_test branch, most importantly getting the tests working
again, including travis testing.
Would you mind rebasing this onto that branch? Currently I can't run the
tests as-is on this PR (are they working for you?). Also, most of the
commits here are just the name of the file that was created or updated. Can
you squash down to fewer and more descriptive commits? It makes it a lot
easier for me to see what's going on.
Thanks a lot! I'm looking forward to digging into these changes and
getting this merged.
—
Reply to this email directly or view it on GitHub
https://github.com/ssfrr/AudioIO.jl/pull/55#issuecomment-161767165.

Does your new PR work off of the wherrera10_test branch that gets the unit tests working? That's the main thing. Secondarily having a smaller number of commits with descriptive names keeps the repo history more tidy and easier to manage.
Also, as an aside - are you doing all your git interaction through the GitHub web interface? If so I'd recommend using a local git client (I hear GitHub Desktop is quite good), as there are lots of things you can't do from the website (rebasing, squashing commits, putting together multi-file commits).

I guess I cannot easily get my Github program to clone and fork a fork-- it
wants master.
I did compare my revised file to the wherrera10 branch and found two places
where the wherrera10 had an update in portaudio.jl and added those to the
branch here, so a pull should work. I guess you are working on a
substantial revision though?
On Wed, Dec 9, 2015 at 4:55 AM, Spencer Russell<EMAIL_ADDRESS>wrote:

Does your new PR work off of the wherrera10_test branch that gets the
unit tests working? That's the main thing. Secondarily having a smaller
number of commits with descriptive names keeps the repo history more tidy
and easier to manage.
Also, as an aside - are you doing all your git interaction through the
GitHub web interface? If so I'd recommend using a local git client (I hear
GitHub Desktop is quite good), as there are lots of things you can't do
from the website (rebasing, squashing commits, putting together multi-file
commits).
—
Reply to this email directly or view it on GitHub
https://github.com/ssfrr/AudioIO.jl/pull/55#issuecomment-163279070.


[📚][firebase_auth] When is the result of User.getIdToken null?

The result of User.getIdToken was recently made nullable, but I cannot find any information under which circumstances null is returned. The SDKs for the other platforms all seem to use a non-nullable return type.
Looking into this a bit further, most of the fields of IdTokenResult are not nullable on the other platforms (for example Web) as well.

The token can be null for instance on the Android platform: https://firebase.google.com/docs/reference/android/com/google/firebase/auth/GetTokenResult


Support multiple "item" types, not just posts

Platypub's schema has a :post document baked in. Right now we use that for two different types of documents: posts and pages. Some themes would benefit from additional types of documents, like events. We need to figure out how to handle this without bloating the core schema.
See #41. We could have the custom schema define not only individual attributes, but document types as well. This may require some hammock time.

What should be in "core" schema and what should be in theme schema? Currently I think most of the post schema should be moved out of core and into themes. Perhaps all of it can be. However Platypub needs to know how to display items in the UI. For example, post-list-item (https://github.com/jacobobryant/platypub/blob/master/src/com/platypub/feat/posts.clj#L267) needs to know the values of :post/{title,status,published-at,edited-at,tags}. Perhaps we have the theme define how items should be rendered in Platypub's navigation.
The core schema will at least need to define which user owns the document. Perhaps we replace the :post/user attribute with an :item/user attribute, and then push everything into the themes' schema.
How should Platypub/themes know if a given document has a certain type? We could add a :item/type attribute (:item/types might be better), or say "any document with attributes X, Y and Z is a valid Foo document." Or we could have themes define a predicate/malli spec which is used to filter documents. Then themes can use whatever method they want for defining document types. (That may be tricky though--eventually we want to not trust theme code.)

I like item/types - with a core platypub schema -- then, tell me if I am getting too complicated, a new platypub menu selection for type - maybe have some defaults but for example a user could create an event type and the attributes could be tags, place holders for css directives etc. -- so the item schema would handle content and the type schema would handle location, formatting and display- the themes could reference the type to place or format the item

menu selection for type - maybe have some defaults but for example a user could create an event type

I think we'll want the themes to define the types, since the themes know what kind of data they need. If users create the types, then every theme has to start out by saying "this theme needs documents of type X, Y and Z, so make some new types for those and include these attributes..." (i.e. either way the theme has to create the type, but this way it's forced to go through the user). A while ago I tried to make an application that stored all the user's data in their own Airtable account and that was the main problem I ran into.
(Let me know if I'm misunderstanding your suggestion.)
As for :item/types -- the thing I'm trying to figure out is, how will it work out for extensibility/interoperability? e.g. say you've been using theme A which works with event documents. However you need to add/change some behavior, so you write theme B which also works with events. For theme B, you want to extend theme A's schema for events such that any events you create while using theme A will still be recognized by theme B, and vice-versa.
Maybe that would be possible with :item/types; I just haven't thought about it enough yet to have all the details hashed out. That's why letting themes define a general predicate function appeals to me: no need to figure out the details; just let the themes figure it out over time ;). checking for a specific value of :item/types would be a special case of a predicate function anyway.
It might not actually be that hard to let themes define a malli spec, but sanitize the spec to make sure it doesn't have any arbitrary code (e.g. don't allow fn schemas).
However I do also want to avoid overthinking things.* Either way I think we need a proof-of-concept of some sort so we can talk about the concrete implementation details more easily.
*If this was a commercial product I'd probably just hard code a few schemas into Platypub and get on with it, but since it's not I feel ok taking some extra time to play around and make something very extensible :).

If you really want to go down the rabbit hole on this, https://www.inkandswitch.com/cambria/ is a good (and long) read.
I also get the feeling that this problem is essentially the same as the expression problem perhaps? Basically I'm thinking that if I just brush up on Clojure's polymorphism/data type handling stuff maybe the correct implementation for platypub will become obvious. Just need to spend a bit of time on it.

I read that also! Interesting article.

Didn't quite finish a proof of concept on this today, but am planning to have something ready to discuss either tomorrow or friday next week.
as a sneak peak I'm thinking that themes can have a config.edn file which will subsume the custom-schema.edn file, while providing some extra stuff. Here's the start of what that might look like for the default theme:
{:site-fields
 [{:label "Primary color"
   :default "#343a40"
   :key :com.platypub/primary-color}
  {:label "Accent color"
   :default "#009b50"
   :key :com.platypub/accent-color}
  {:label "Tertiary color"
   :default "#e5e7eb"
   :key :com.platypub/tertiary-color}
  {:label "Logo image URL"
   :description "Suggested dimensions: 320x60 px"
   :key :com.platypub/logo-image}
  {:label "Logo destination URL"
   :description "Where should people go when they click on the logo?"
   :default "/"
   :key :com.platypub/logo-url}
  {:label "Author name"
   :key :com.platypub/author-name}
  {:label "Author URL"
   :key :com.platypub/author-url}
  {:label "Author image URL"
   :key :com.platypub/author-image}
  {:label "Discourse forum URL"
   :description "Optional. If you set up a Discourse forum, you can use it to embed comments on your blog posts."
   :key :com.platypub/discourse-url}
  {:label "Embed HTML"
   :description "This snippet will be injected into the head of every page. Useful for analytics."
   :key :com.platypub/embed-html}
  {:label "Navigation links"
   :default "/ Home\n/archive/ Archive\n/about/ About"
   :key :com.platypub/nav-links
   :type :textarea}]

 :items
 [{:key :com.platypub/post
   :label "Post"

   ;; query-keys will be translated to the following when getting the documents to display on the posts page:
   ;  '{:find [[item :com.platypub.post/title]
   ;           [item :com.platypub/types :com.platypub/post]]}
   :query-keys [:com.platypub.post/title
                [:com.platypub/types :com.platypub/post]]

   :fields
   [{:key :com.platypub.post/title
     :label "Title"}
    {:key :com.platypub.post/published-at
     :label "Published at"
     :type :instant}]

   :sendable true

   :render/label :com.platypub.post/title
   }]}

That's very incomplete*, but with just a few more keys I think we can move all the post-specific information into this file and have Platypub deal only with generic items. Once I have this example file finished, the next step would be to try to rewrite the platypub core code so it never uses any :post/* keys explicitly. And see if any problems come up.
in particular, need to add at least one more :render/ key to define e.g. how the small line of text underneath each post title in on the posts page should be rendered. Also would like to add some kind of :table-settings key or something, that defines grouping and sorting as data. can be used to group posts by draft vs. published and sort by edited/published date.

I've been working on this the past few days, and hopefully will have it finished tomorrow. If not, then friday. Nav bar will look like this:

Now instead of "posts" there will be "items", and themes will define what those items are via this config.edn file. The default theme defines "posts" and "pages" as seen in the screenshot.

This is now complete. It's on an items branch (https://github.com/jacobobryant/platypub/tree/items). I will probably merge it to master tomorrow/monday. This is a pretty big set of changes. It also requires running a DB migration:

check out the items branch
run ./task dev
go to repl.clj and call the migrate-items! function

After that you can go to localhost:8080 and you should see the new UI as seen in the screenshot above.
Custom themes will need to be updated. See get-render-opts (the return value is what gets passed to the theme): https://github.com/jacobobryant/platypub/blob/fe2dc098fbd197cc70d9b29e0b158bfe85cfcf49/src/com/platypub/util.clj#L200 and derive-opts (this is what the default theme does to the result of get-render-opts before passing it on to the rest of the theme code): https://github.com/jacobobryant/platypub/blob/fe2dc098fbd197cc70d9b29e0b158bfe85cfcf49/themes/default/common.bb#L189

Closed by https://github.com/jacobobryant/platypub/commit/146850e30ffe59ab32b7ec5f2a53b447fcb11e86


Upgrade go to 1.11 and switch to go modules from gvt

This super seeds #50
Fixes #32
Followed the instructions from https://github.com/FiloSottile/gvt

can somebody merge it?


Scanhentaifr

Source name
Scanhentaifr
Source link
https://scanhentai.com/
Source language
French
Other details
Yes +18
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

@KirinRaikage on a changé Les règles non?

@KirinRaikage on a retiré la blague pour ceux qui comprenaient pas l'anglais

@KirinRaikage on l'ajoute quand plus on a mieux c'est non

@AwkwardPeak7 Mon dernier espoir

@WoodlyBasquin56 don't ping contributors, they're not obligated to do any work. This is all done by contributors volunteering their time & willingness as mentioned in the message above yours.
Go through the contributing guide if you are desperate for the extension, otherwise wait patiently or use something else.


missing tables in

The tables StoreUpdateQueue and SteamKeys are missing.
Errors occur for StoreUpdateQueue if CanQueryStore is enabled.
SteamKeys seems to be needed for IRC even if IRC->Enabled is set to false for some timer event.

Don't enable CanQueryStore.


Enable reading global profiler settings not only by admins and bots

Is your feature request related to a problem? Please describe.
We have a feature on our platform where we enable users to execute profiling jobs themselves. We provide curated workflow template, users update table and schema name and execute ad-hoc jobs for their tables. This was working fine until we upgraded to OM <IP_ADDRESS>, where https://github.com/open-metadata/OpenMetadata/pull/15889 was introduced. Now, regular users (not admins or bots) cannot execute profiling jobs as they get 403 error on fetching global profiler config.
Describe the solution you'd like
Requesting global profiler config (get /api/v1/system/settings/profilerConfiguration) is not restricted only to admins and bots. Proposed approaches:

move this resource out of system settings
create resource ProfilerConfig (or more generic SystemSettings) with operations create edit read like with other resources

What's particularly interesting about aforementioned implementation is that authorizeAdminOrBot method is used only once throughout whole OM service - in said endpoint.
Describe alternatives you've considered
Since we are grouping permissions using Teams/Groups (we have Teams A, B, C and we assign users to their respective teams, then we assign DatabaseSchema owner to a team. For example schema transactions from Trino service is owned by team A and all members of team A can edit metadata in transactions schema tables) we considered extending functionality of OpenMetadata with scoped bot users (so we could create bot X that would be a member of team A - this bot would inherit permissions of the team but would be treated as bot) https://github.com/open-metadata/OpenMetadata/issues/15891.
Additional context
We follow shift-left paradigm, so instead of running profiling jobs within OM Airflow, we instead allow users to do this with their personal credentials and on their own desired cadence. This is very important security-wise, as our OM instance service connections cannot use accounts (NPAs) that have access to actual data so moving this responsibility to end users is our only way to get profiling data into OM.

cc @TeddyCr as you've been working on global profiler config

Hello @mgorsk1 thanks for the detail, could you share a bit more about the below? I would love to understand this flow a bit better.

We have a feature on our platform where we enable users to execute profiling jobs themselves. We provide curated workflow template, users update table and schema name and execute ad-hoc jobs for their tables.

Sure, we enable our users to use om profiling workflows themselves from within their personal jupiter notebooks. In such case they connect to appropriate systems using their personal credentials and authenticate against om api using their personal jwt tokens

Ok I see, what you mean. let's take a look. I'll mark it as 1.6, but we'll try to tackle it for a minor 1.5.x release.


Change chain.go to use LinkRules

Change how the rules for which sections are allowed in which team link types is expressed in chain.go. This is meant to be a translation expressing exactly the same rules. The LinkRules strategy nice because it's less code and stricter. So when adding a new link type or changing stuff you're likely to accidentally be too strict rather than too loose.
If this will conflict with any of your PRs please let me know. I'd rather wait and rebase this because it's relatively easy to rebase than cause more work for you on the hard PRs.

[ ] Make a ticket for the TODO

Failed in:
2018-02-22 12:04:49.38240 settings_test.go:23    : [D] - CreateRootTeam -> cannot post link (precheck): appending 0->1: link type 'team.root' unexpected at beginning [time=61.582337ms]
	assertions.go:239:

	Error Trace:	settings_test.go:24

	Error:      	Received unexpected error:

	            	cannot post link (precheck): appending 0->1: link type 'team.root' unexpected at beginning
	test_logger.go:56: TEST FAILED: TestSettings
	test_logger.go:79:

Fixed


Create DigitCount

This C++ program gives the count of a particular digit in the input number.
For example ,
input
n=100
d=0
output=2
because count of digit 0 in 100 is 2
Description
enter here if you have any details
Program Name -       Digit Count
Issue No.- #360

Type issue number after hash(#)

Checklist(self check)

[x] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

Invalid isssue numer.
No Edabit question
Un assigned PR


Rename the env variable HF_ENDPOINT.

This improves consistency across HF ecosystem.
https://github.com/huggingface/transformers/blob/c595b6e6a90c29242c9dbfeecc5b132fe2e3d1f4/src/transformers/utils/hub.py#L110
https://github.com/huggingface/datasets/blob/8c5f27889657a1a6a7203b2f054bd0ceffce2178/src/datasets/config.py#L24
Fixes #798

Pinging @SBrandeis since your made the initial modification so you are aware of this name change.
Is it OK to change the name here ?

Yes @Narsil that is fine

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Thanks for the fix @Narsil . It'd be nice if for future PRs you'd create the feature branches on your fork rather than the main repo 😊

Thanks for the fix @Narsil . It'd be nice if for future PRs you'd create the feature branches on your fork rather than the main repo blush

Ok, thanks for the heads up.


Ability to add n number of users to all public streams

As community manager I often have to migrate guest users to full members, which means also adding them to all of our 20-30 streams.  Right now I have to add each person, one by one, to each stream.  It's incredibly inefficient and laborious.
Ideally there would be two approaches available to this:

Simply tick a box "Add user(s) to all public streams"
Ability to select which streams you want to add the user(s) to, and they would be bulk added all at once after confirming.

Thank you.

@vanclute I wonder if it makes sense for you to use https://zulip.com/api/subscribe; the API supports this sort of bulk operation, and I suspect you could write a 10-line program with the API that lets you pass the user's email address and will add it to a specific set of streams.

Oh no question this could absolutely be handled via the API.  However implementing this is beyond me, and while one of our founders could definitely do this, it's a waste of his time to have to when he's got way too much on his plate already.  This seems like such a basic feature that anyone who uses the guest model to give people a taste of a community, and then gives them an upgrade path to full member, would need.  Would just be so much simpler for admin users to simply have a tick box "Add to all public streams" on the Manage Streams page next to the Stream Membership Add Subscribers field, for example.

When we build the admin version of this, I wonder if we should also add a user-side "subscribe to all public streams" option.

That actually seems like a really reasonable thing to me.  In our case I don't think any of our members have even discovered that they can unsubscribe from streams, but in case they ever do and want to just get back in all of them, I think this would be helpful.


A confusing CUBLAS_STATUS_EXECUTION_FAILED error during training process of some sets of data

Thanks for this nice work.
I met some problems. I work on a 3090 GPU, 24GB VRAM. When I tried to train the scene "misc_keyboard" in hypernerf dataset, one strange error occurred.
My command is
python train.py -s data/hypernerf/misc/keyboard -m output/hypernerf/misc/keyboard --eval --is_6dof
and the error which happened at iters 6900 is
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasLtMatmul( ltHandle, computeDesc.descriptor(), &alpha_val, mat1_ptr, Adesc.descriptor(), mat2_ptr, Bdesc.descriptor(), &beta_val, result_ptr, Cdesc.descriptor(), result_ptr, Cdesc.descriptor(), &heuristicResult.algo, workspace.data_ptr(), workspaceSize, at::cuda::getCurrentCUDAStream())`
It's strange because it only happened in a few sets of data, and changed with device changing(I use multiple devices to log in and train on the local server). For example, all data of dnerf is ok, but hypernerf is not, "as_novel_view" in nerfds is ok, "bell_novel_view" also in nerfds is not.  In the same server, "as_novel_view" can be trained in one device's terminal but cant in another's
I guess it may be caused by out of memory, but I dont know how to fix it and why it changes with device changing while the server doesn't change.

I also meet the same problem

Hi @1van2ha0 @KarryLxh, thanks for your interest in our work.
I believe the oom issue you mentioned mainly occurs in the HyperNeRF dataset. I think the camera pose in the HyperNeRF dataset is not accurate, which is why in the latest version of my paper, I switched to using the NeRF-DS dataset instead of HyperNeRF. This inaccuracy can lead to an abnormal increase in the number of 3D Gaussians, causing oom problems during rasterization (note that querying millions of point clouds in the MLP will not lead to oom).
I believe this, to some extent, actually demonstrates the precision of the deformable-GS model; it will oom or fail to converge in scenes with highly inaccurate poses. I don't have any particularly good solutions for the oom issues in some HyperNeRF scenes. If you have to use this scene, I think imposing certain constraints on the delta transform might be an effective solution.


Update how-to-use-tls-certificate.md

fixed typo - "Azure Spring Apps Resource Provider" -> "Azure Spring Cloud Resource Provider"

@KarlErickson

Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@gkgaurav31 thanks for the fix! We've verified that the screenshot accurately reflects what shows up in the portal, so I'll accept this change. I'll also escalate this to the product team so that they can rename the resource provider to reflect the new service name.
#sign-off


Non-Staff (non-admin) users can't see findings

Even with all permissions added to a group, and a non-staff users in that group, that user cannot see findings. It forwards them to the login screen (session isn't killed, but can't see findings). It appears that this happens with numerous menu options as well. And even with all the permissions added, there are no menu options for Engagements, Tests, Findings, etc.... only Products, Reports, Metrics and Configuration. The user is also added to the authorized users field of a product. Anything we are doing wrong on our end?

@rkane-nm will have this fixed in my next pr (should be tomorrow).


[Unexpected Behavior] MIDI input not functioning properly

StepMania 5.3-git-09ae1e4e29
20200819
Explain what function you're using and what arguments you're giving.
Using MIDI input on "Test Input" screen:

MIDI note-on data
MIDI CC data

Explain what you expected to happen or the function to return
Expected Return:

Note-on and corresponding note-off received
CC received

Actual Return:

Note-on data received, no corresponding note-off for release
No CC data receieved

Additional Info:

this was fixed.


Filtering strings

When i do searchTextField.filterStrings(stringsArray), i don't get all items present in stringsArray.
is there an explanation for this ?

Initial function name states: FILTERED strings. But agree, would be great to have such callback closure.

you check this?
// Set the max number of results. By default it's not limited mySearchTextField.maxNumberOfResults = 5


POST - Power On Self Test

As a devops
I want to know if the configuration is correction
So that I can correct it
The server

should check that the database connections are correct

Can we write mocha tests that the server runs in the background?

While the idea of power on self testing is good, what makes startup so special?  We only spend a fraction of the uptime in this state.  Continuous self testing is better.  The system now examines its responses and checks for errors.


Not working with Insert Plugin

As it's mentioned in the readme Known Issues Section, It doesn't work with some version of it.
Would be better at least if you can mention it works with which version of it.
Thanks

@msaiyaff Thanks for reporting. Since it's been 2 years, I don't remember the version number. If you test and it work with the current version of insert plugin, please let me know.

@smiled0g I tried this multi-placeholder plugin with insert-plugin v2.4.0
It's working.
But, has got some style issues. As in, some alignment issues for the placeholder and the text that we type.

So the placeholder alignment and the alignment of the text we type goes apart as you see in the picture. Assuming that it's some style has overridden with another package I am using may be.

@msaiyaff Do you have any clue what causes the misalignment? Since I don't use the plugin myself anymore, it might take me some time to resolve the issue. If you manage to fix it, please feel free to send a PR :)


Email Invitations

As a group administrator, I want to easily invite new users to join the platform.
Currently, the flow to do this is that the new user needs to manually create an account, and then the group admin can lookup the user's email address to add them to the group.
Instead of this, the "Add User" flow should be augmented. Currently, a dropdown list is shown of users whose email address match the group's domain filter. It now should be possible to enter any email address (which matches the domain filter) even if that address is not registered to the platform.

if the email address corresponds to an existing user, that user should be shown in the autocomplete window, and would be added to the group immediately (unchanged behaviour)
If the email address does not correspond to an existing user, the admin will be shown a prompt, asking if he would like to send an email invitation to the user.
If the admin approves, an email will be sent to the new user, containing a registration link with a unique invitation code.
A field for entering the invitation code should be displayed in the registration form, but it should be prefilled from the emailed link. In case the field has not been prefilled (e.g. the user is registering on a different device), the user can enter the value manually.
After filling in the registration form, the invitation code is used to automatically assign the user to the user group. The invitation code should also be invalidated to prevent reuse.
When a user registers with an invitation code, the "Email verification" step is skipped, and the user should be logged in immediately after filling in the registration form.
The invitation feature must be available to group admins, but should also be accessible to platform admins, who may use this feature to bootstrap a new group by inviting the first users (see #295)

@jc-skushnir some notes about this task and some of the related ones (#295 and #296):

The invitation code

is unique per invitation i.e. every user will receive own uniqe code
should be a 6 characters value (for now it is enough, later on we may difits or other sybols and extend its length)
should have an expiration time (can be set via config file)
should be used by only one person, i.e. can't be 2 registration using a single code

Once invited user used the invitation link and was redirected to the Registration page
The list of invited users should be visible for Group admin and Platfrom admin
Group admin and Platfrom admin can remove inviations and re-send them

Some notes copied from our conversation:

If the user is entering the code manually from a different device, we can't block them from entering a different email address. In this case I think it should trigger a validation error if the email address they enter is different from the one that the invitation code is associated with.
We do need to be a bit careful about security, because we are not only allowing registration but also granting access to an existing user group. To combat this, my preferred solution would be to add rate-limiting to one registration attempt per second for a given email address. This could be combined with a short code (6 Uppercase + Numeric chars) that is easy to enter but would still take several years to crack. I don't know how easy this is to achieve in Laravel, however, and I don't want to increase the scope of the ticket. So if it's not easy to do rate limiting, I would rather stick to a long code (15 Upper, Lower + numeric characters)


[Feature] [UI] Export the eBPF Profiling flame graph

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Currently,  we could generate the flame graph in the UI based on the analysis data of eBPF Profiling.
To enhance interactivity, we can add a button to export the flame graph (including selection and tip functions), similar to the "Export image" function in the Trace control.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Should I continue to push this later in 9.3.0? As we are focusing on ebpf network profiling feature as a key feature of 9.3.0?

It's ok for me. Also, we could using the skywalking-cli to export the flame graph, using UI to export it just other way.

After some discussion, we noticed this would cost too much as it is not just exporting an image, it has to include html/js with data. There is no real case why users can't use our UI but an exported page.
Close for now.


{CosmosDB} Make sure analytical-storage-ttl is applied as only argument for Gremlin graphs

Active customer bug
When creating a Cosmos DB Gremlin graph, the parameter 'analytical-storage-ttl' currently isn't added to the HTTP payload if it is the only container-specific parameter. This PR fixes the issue.

CosmosDB

/azp run


Parser should accept spaces for args

Right now parser operates on single tokens only. Would be more intelligent to start using prepositions to break things up and allow use of labels with spaces in them.
Further, in world, could make it such that a non-space version is always allowed; e.g. "THING ALIAS" could also be referred to by "THINGALIAS" in commands.

did it except for making it so space variations are allowed. thats kind of silly tbh


I cant login in play store

I have followed all the steps but I can't login to google play

make sure you update everything within the store before attempting to login

because sepolicy apply fails. Use kernelsu to setenforce 0 and login and setenfore 1

Is that possible to use a proxy server to log in to Google Play?

It's a Windows Firewall Problem, i don't know how to solve without deactivate Firewall

It seems we should wait for the moment when we can share network cross through Windows and WSA

because sepolicy apply fails. Use kernelsu to setenforce 0 and login and setenfore 1

@yujincheng08 Could you clarify in more detail how to do that for non-professionals?

+1, fresh install.  I made sure to use the update function first in Google Play before attempting to sign-in, it updated fine including the Google Play Services thus a network issue seems unlikely.  When I clicked the "Sign In" button nothing happens.

For me nothing happens when I click sign in

It's a Windows Firewall Problem, i don't know how to solve without deactivate Firewall

It doesn't work for me.

Any news ? Still got the problem even with firewall off.

Same. Can't go any further than the Google Store sign in. Any Tests I can run? Network ect...


Make the rest of ZHA platforms to use ZHA class registry

Description:
Not a breaking change. Tests were added in a reasonable attempt to ensure we maintain the current behavior. This is PR is a part of a larger effort in ZHA entities discovery and loading refactoring, so we could support  multiple entities per a single ZCL cluster, e.g. SmartEnergy cluster  may support more than one sensor, but currently we're only creating a sensor for the active_power.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@dmulcahey may be easier to review by commits. Commits were broken into logical changes. The idea of the change in the last two commits, everything before those two is just tests and cleanups/preparations.

Lots of really good stuff here! 1 question / suggestion and the CI issues. will approve once resolved.

I think tplink integration broke the tests.

Rebased to 1ee299b079b3672aad3dcdce8ce1ecf4e5238d07 Still have no ideas why it fails in zwave tests.


Master Control Panel with Agents

Please confirm these before moving forward.

[X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
[X] This improvement is not a bug. If you want to report a bug, please use this template.

Describe the improvement
Is there a master control panel that can talk to all versions installed on clients systems?
Describe how this improvement could help users
Managing many remote systems appears to eb an essential feature

Is there a master control panel that can talk to all versions installed on clients systems?

UniGetUI is not designed as a tool to deploy software to machines, though this could be an interesting feature

Martin,
May be not a tool to deploy (yet) but it would be superb as a managment product
I am going to examine the CLI options to see how it functions on remote systems.
One issue tat does appear is requests to install some packages - is there a "LocalSystemUser" option
Terry

I don't understand what you mean


TreeDataProvider: Allows an input box to be displayed, similar to the input box shown by VSCODE when clicking the New File button in the EXPLORER

I need to add a new file operation in the plug-in, which requires the user to enter the file name. The plug-in only provides the method window.showinputbox, but the location of the input box in the showInputBox does not conform to the user's habits

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Allow multi-line input box (#39969)

It's not the same need


x/build: add FreeBSD/arm64 builder

Creating a tracking issue for the task of adding a freebsd/arm64 builder, factored out from https://github.com/golang/go/issues/24715#issuecomment-537742727.
/cc @dmgk @bradfitz @bcmills

Relevant CL: https://go-review.googlesource.com/c/build/+/198597

The builder is up [1]. I haven't done steps 7-8 yet as they seem to depend on step 4 [2]
[1] https://build.golang.org/
[2] https://github.com/golang/go/wiki/DashboardBuilders#how-to-set-up-a-builder

Closing as this issue is resolved, the freebsd-arm64-dmgk builder has been running and passing for a while now. It's also being maintained and fixed with quick turnaround, see #37601. Thank you very much @dmgk.


[VTA] Tutorial on how to deploy and execute model on device without RPC

This is a follow up to forum post: https://discuss.tvm.ai/t/solved-pynq-vta-run-model-locally-on-pynq-z1-instead-of-via-rpc/4336/11
The idea is to complement the existing VTA tutorials to having one that shows how to run a model directly on the device without relying on RPC.
Assigning to @flip1995

@tmoreau89 I have time to write up this documentation now. Should I start a new page in the documentation or just append this to a previous document? Can you post a quick link where to put this documentation in either case?
Sorry for the delay. I forgot about this and just discovered it in my saved issues again.

@flip1995 if you could start a new page of the doc (see: https://github.com/apache/incubator-tvm/tree/master/docs/vta), and from your private fork issue a PR. When it's ready please assign the PR to be reviewed by me. Thank you!

@tmoreau89 @flip1995 Could you please point me to this document if it is available?

Oh damn, I totally forgot about it. Basically you have to add those two lines to your python script, that runs your model on the PYNQ:
dll_path = "/home/xilinx/tvm/build/libvta.so"
ctypes.CDLL(dll_path, ctypes.RTLD_GLOBAL)

before the graph_runtime.create(..) command.
I hope this still works. I haven't used TVM/VTA for a long time now.

Or to be more precise, you have to load your model like this:
import ctypes

import tvm
from tvm.contrib import graph_runtime as runtime

libvta_path = "/home/xilinx/tvm/build/libvta.so"
ctypes.CDLL(libvta_path, ctypes.RTLD_GLOBAL)

# load compiled model
with open("graph.json", "r") as graph_file:
    graph = graph_file.read()
with open("params.params", "rb") as params_file:
    params = bytearray(params_file.read())
lib = tvm.module.load("./lib.tar")

ctx = tvm.ext_dev(0)

module = runtime.create(graph, lib, ctx)
module.load_params(params)

After that module.run(**<input-dict>) should work

hello guys I am equally new to tvm, and I am trying to run inference on the zynq board without rpc but I keep getting the error stated below, I have not even gotten to making the changes as discussed on this forum, can I get some guidance?
OSError: libmkl_intel_lp64.so.1: cannot open shared object file: No such file or directory

I haven't worked with TVM in ages. But this is probably unrelated to this issue. Either this lib is not installed on the device or you should try to run the same commands with root privileges. The latter usually solved things like this on the PYNQ for me.

Hello yes thank you so much for your feedback I am aware it has been a
minute since you worked on TVM, but please bear with me I need this for my
studies, I am also trying to run the prediction of a cat from the FPGA
directly, and I saw your modifications you made to have that working, in
the case of the picture model to run on the board are there any other
modifications i should add?
On Fri, Feb 3, 2023 at 12:53 PM Philipp Krones @.***>
wrote:

I haven't worked with TVM in ages. But this is probably unrelated to this
issue. Either this lib is not installed on the device or you should try to
run the same commands with root privileges. The latter usually solved
things like this on the PYNQ for me.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/tvm/issues/4272#issuecomment-1415764195, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZH5JBO4WPHJA53AQMRGMMLWVTWSZANCNFSM4JKLY5TA
.
You are receiving this because you commented.Message ID:
@.***>

I'm not aware of any other modifications. However, when I used TVM it was even pre-Apache time. So a lot has happened since then. So take all of the suggestions here with a grain of salt.

w. but any
import ctypes
import tvmfrom tvm.contrib import graph_runtime as runtime
libvta_path = "/home/xilinx/tvm/build/libvta.so"ctypes.CDLL(libvta_path,
ctypes.RTLD_GLOBAL)
load compiled modelwith open("graph.json", "r") as graph_file:
graph = graph_file.read()with open("params.params", "rb") as params_file:
params = bytearray(params_file.read())lib = tvm.module.load("./lib.tar")

ctx = tvm.ext_dev(0)
module = runtime.create(graph, lib, ctx)module.load_params(params)
okay so if i run my own python script like this i should be able to
run tvm on the board with rpc and yes i am aware TVM has long improved
from then till now but i am open to any contributions you might
suggest about running tvm on the fpga board directlyKrones
@.***> wrote:
I'm not aware of any other modifications. However, when I used TVM it was

even pre-Apache time. So a lot has happened since then. So take all of the
suggestions here with a grain of salt.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/tvm/issues/4272#issuecomment-1415854684, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZH5JBNECBHHULNXEU4RIU3WVUAAJANCNFSM4JKLY5TA
.
You are receiving this because you commented.Message ID:
@.***>

okay so if i run my own python script like this i should be able to
run tvm on the board with rpc and yes i am aware TVM has long improved
from then till no
import ctypes
import tvm
from tvm.contrib import graph_runtime as runtime
libvta_path = "/home/xilinx/tvm/build/libvta.so"
ctypes.CDLL(libvta_path, ctypes.RTLD_GLOBAL)
load compiled model
with open("graph.json", "r") as graph_file:
graph = graph_file.read()
with open("params.params", "rb") as params_file:
params = bytearray(params_file.read())
lib = tvm.module.load("./lib.tar")
ctx = tvm.ext_dev(0)
module = runtime.create(graph, lib, ctx)
module.load_params(params)
okay so if i run my own python script like this i should be able to run tvm
on the board with rpc and yes i am aware TVM has long improved from then
till now but i am open to any contributions you might suggest about running
tvm on the fpga board
On Fri, Feb 3, 2023 at 2:13 PM Philipp Krones @.***>
wrote:

I'm not aware of any other modifications. However, when I used TVM it was
even pre-Apache time. So a lot has happened since then. So take all of the
suggestions here with a grain of salt.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/tvm/issues/4272#issuecomment-1415854684, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZH5JBNECBHHULNXEU4RIU3WVUAAJANCNFSM4JKLY5TA
.
You are receiving this because you commented.Message ID:
@.***>


[BUG] full screen video doesn't work

I'm using Wallpanel for my Home Assistant dashboard, actually all work fine, but I can't zoom video to full screen. In the video player window the full screen icon appear disabled

Hello. Is this fixable? Not being able to fullscreen camera streams is not ideal. Please tell me that there is hope :) Thank you.

I am also experiencing the same issue. I can click the button to go full screen on a video but nothing happens. With fully kiosk it does work.


MQTT Autodiscovery

Is it possible for you to integrate MQTT discovery for Home Assistant? In this way the integration will be very similar to the original MiFlora component, just over MQTT.
https://www.home-assistant.io/docs/mqtt/discovery/

Implemented with version 0.6.0


Library name change request - M5Unit-ACSSR

Library repository URL
https://github.com/m5stack/M5Unit-ACSSR

Hi @Tinyu-Zhao. I am confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will close this issue when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager


[Skungee] Timed out when attempting to send network variable

When attempting to send a network variable, I get the following error:
[02:10:21 INFO]: Welcome brobie1kanobi, to Mega GAME World!
[02:10:22 INFO]: [Skungee] Timed out attempting to send network variable {tp::parkour::*}
ver skungee
[02:12:00 INFO]: Skungee version 2.0.0-ALPHA-9
[02:12:00 INFO]: Author: Skungee

I am trying to(/ways to recreate):

Set a variable on the "hub" adding the player to it. (See 1st code below) then send them to the "games" server

When they connect, check said variable and if the player is in it (2nd code below)

Send them to a specific world via a command (also, I HAVE tried the "on join" event, but doesn't change the outcome).

Here is my code for on the Hub server to send the player to a specific world which has no errors:
command games [<text>]:
  trigger:
    if arg is not set:
      player command "server Gamemode1"
    else:
      if arg is "parkour":
        set network variable {tp::parkour::*} to player
        player command "games"

Also, I've tried add player to network variable {tp::parkour::*}
Here is the code from the "Games" server to check the variable with even the "debugs" left in for testing (though I don't think it matters, as it doesn't get this far):
on player connect:
  wait 1 second
  network variable {tp::parkour::*} contains player:
    send "variable found" to player
    player command "mvtp parkour"
    remove player from {tp::parkour::*}
    send "removed from var" to player

If this is not a bug or I did something wrong, I'm sorry for the peremptive report but I have not found any other issues where this was reported or any forums discussing this.

Not using this build or add-on anymore. Marking closed as I'm sure it's just a pre-current build issue.

Not using this build or add-on anymore. Marking closed as I'm sure it's just a pre-current build issue.


drt: sort insts and nets to ensure stable results

I have a test case for global and detailed routing where the results of detailed routing are different if an odb or def is used. Both the odb and def are created at the same time (before global routing), and there should be nothing in the odb at that stage that cannot be represented by the def.
One difference (pointed out by Matt) is that write_def sorts insts and nets, so we iterate through them in a different order. Sorting them before using them in drt fixes the issue.
Signed-off-by: Anton Blanchard<EMAIL_ADDRESS>

I pulled the template straight out of odb. Is it overkill? Should odb be sorting these in their iterators? Should we be sorting other things in drt (eg obstructions)?

IMO we should probably add a set of API methods to ODB to support sort iterators, or potentially just store them in sorted order.

IMO we should probably add a set of API methods to ODB to support sorted iterators, or potentially just store them in sorted order.

Sounds good. In this specific case we should also experiment with sorting by the worst n% of slacks, similar to what we do in gpl and now grt. That might help route critical timing nets better.

Sorry, I put this aside and then lost track of it.  This only works because drt copies odb and once that is resolved this wouldn't be possible anymore.  It also doesn't solve the similar problems that can occur in any module.
I'm not sure we need to guarantee that we get the same result no matter how the netlist is reordered.  If we do then we need to look at it everywhere.  Most algorithms should be order independent or should have some more meaningful ordering than names.
Would you say more about why this is an issue?

Sorry, I put this aside and then lost track of it. This only works because drt copies odb and once that is resolved this wouldn't be possible anymore. It also doesn't solve the similar problems that can occur in any module.
I'm not sure we need to guarantee that we get the same result no matter how the netlist is reordered. If we do then we need to look at it everywhere. Most algorithms should be order independent or should have some more meaningful ordering than names.
Would you say more about why this is an issue?

This started because I built a test case using lib/lef/def/sdc and it didn't reproduce the issue. It turns out I needed the odb because the sorting between the two formats was different.
This is less of an issue now that the odb format is more stable and we can use it for test cases.

@antonblanchard what do you want to have happen here - merge or close?  Your last comment suggests this is no longer a problem.


pcsx2: 1.7.3165 -> 1.7.3272

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pcsx2/versions.
meta.description for pcsx2 is: "Playstation 2 emulator"
meta.homepage for pcsx2 is: "https://pcsx2.net"
meta.changelog for pcsx2 is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.3221 with grep in /nix/store/bdkgxz3k26z6716d4gndid1zlvfplimc-pcsx2-1.7.3221
found 1.7.3221 in filename of file in /nix/store/bdkgxz3k26z6716d4gndid1zlvfplimc-pcsx2-1.7.3221

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pcsx2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bdkgxz3k26z6716d4gndid1zlvfplimc-pcsx2-1.7.3221 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pcsx2 https://github.com/r-ryantm/nixpkgs/archive/ce3b4a1f261def5c7d686ec44c668bcc3adfab41.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bdkgxz3k26z6716d4gndid1zlvfplimc-pcsx2-1.7.3221
ls -la /nix/store/bdkgxz3k26z6716d4gndid1zlvfplimc-pcsx2-1.7.3221/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pcsx2

Maintainer pings
cc @hrdinka @GovanifY for testing.

This is just a pre-release https://github.com/PCSX2/pcsx2/releases/tag/v1.7.3221
Why is this used? @ryantm

I've actually asked earlier ryantm and didn't get any answer, it pings me on every dev build, which are made at each PR merged. Needless to say, this is a little bit high frequency.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pcsx2/versions.
meta.description for pcsx2 is: "Playstation 2 emulator"
meta.homepage for pcsx2 is: "https://pcsx2.net"
meta.changelog for pcsx2 is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.3256 with grep in /nix/store/aq92fail8zph7lh711xfr6xwa98j1xjp-pcsx2-1.7.3256
found 1.7.3256 in filename of file in /nix/store/aq92fail8zph7lh711xfr6xwa98j1xjp-pcsx2-1.7.3256

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pcsx2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aq92fail8zph7lh711xfr6xwa98j1xjp-pcsx2-1.7.3256 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pcsx2 https://github.com/r-ryantm/nixpkgs/archive/ff75467bcfdae14d438b224b68f66151c0544c8b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/aq92fail8zph7lh711xfr6xwa98j1xjp-pcsx2-1.7.3256
ls -la /nix/store/aq92fail8zph7lh711xfr6xwa98j1xjp-pcsx2-1.7.3256/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pcsx2

Maintainer pings
cc @hrdinka @GovanifY for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pcsx2/versions.
meta.description for pcsx2 is: "Playstation 2 emulator"
meta.homepage for pcsx2 is: "https://pcsx2.net"
meta.changelog for pcsx2 is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.3272 with grep in /nix/store/za00hrl6f0rb4hcswawlhclxay2pqzfl-pcsx2-1.7.3272
found 1.7.3272 in filename of file in /nix/store/za00hrl6f0rb4hcswawlhclxay2pqzfl-pcsx2-1.7.3272

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pcsx2

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/za00hrl6f0rb4hcswawlhclxay2pqzfl-pcsx2-1.7.3272 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pcsx2 https://github.com/r-ryantm/nixpkgs/archive/eb8f5f96506a2cb55985f729b7dbb4c1fcb10d53.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/za00hrl6f0rb4hcswawlhclxay2pqzfl-pcsx2-1.7.3272
ls -la /nix/store/za00hrl6f0rb4hcswawlhclxay2pqzfl-pcsx2-1.7.3272/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pcsx2

Maintainer pings
cc @hrdinka @GovanifY for testing.

Closing due to #190739 being merged.

Closed because of https://github.com/NixOS/nixpkgs/pull/190739


ibmcloud: Added test case to check peer pod created with job

Added test cases to check peer pod created via job in ibmcloud cloud-provider
Fixes: #930

Does this catch the error that is described in https://github.com/confidential-containers/cloud-api-adaptor/issues/930#issuecomment-1545527587 ?
If so do we want to merge a failing test or wait until the problem is identified and fixed?

Does this catch the error that is described in #930 (comment) ?
If so do we want to merge a failing test or wait until the problem is identified and fixed?

@sudharshanibm3 - as JT says, it looks like we need to rework the test to be exactly the same job as is used in kata-containers and then ensure that this test gets the correct result (which should be a failure at the moment), so we might not want to merge this until we understand the issue.

Hey @sudharshanibm3 - I've tried this locally and it's failing for me:
=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/Job_Peer_Pod
time="2023-05-16T03:54:28-07:00" level=info msg="Creating Job..."
time="2023-05-16T03:54:28-07:00" level=info msg="Verifying Job..."
=== RUN   TestCreatePeerPodWithJob/Job_Peer_Pod/Peer_Pod_successfully_created_by_Job
    common_suite_test.go:311: container "pi" in pod "pi-vnb4s" is waiting to start: ContainerCreating
--- FAIL: TestCreatePeerPodWithJob (0.42s)
    --- FAIL: TestCreatePeerPodWithJob/Job_Peer_Pod (0.42s)
        --- FAIL: TestCreatePeerPodWithJob/Job_Peer_Pod/Peer_Pod_successfully_created_by_Job (0.15s)
FAIL

It's not a big surprise as we think there might be an underlying defect, but it means we can't get this merged in yet

Hi @stevenhorsman ,
I've updated the code to catch the Failing pod status.
Could you please try now?

Hi @stevenhorsman , I've updated the code to catch the Failing pod status. Could you please try now?

It still seems to be failing:
=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/Job_Peer_Pod
time="2023-05-16T04:13:31-07:00" level=info msg="Creating Job..."
time="2023-05-16T04:13:31-07:00" level=info msg="Verifying Job..."
time="2023-05-16T04:13:31-07:00" level=info msg="List pods that belong to the job: pi-qrm6r"
time="2023-05-16T04:13:31-07:00" level=info msg="Verifying that the job is completed for the pod pi-qrm6r..."
    common_suite_test.go:289: timed out waiting for the condition
--- FAIL: TestCreatePeerPodWithJob (300.18s)
    --- FAIL: TestCreatePeerPodWithJob/Job_Peer_Pod (300.18s)

Can you expand on the 'catch the Failing pod status' comment please too?

time="2023-05-17T09:00:14+05:30" level=info msg="Wait for Job to be completed..."
time="2023-05-17T09:02:25+05:30" level=info msg="List pods that belong to the job:"
time="2023-05-17T09:02:25+05:30" level=info msg="1. pi-2nx5d"
time="2023-05-17T09:02:25+05:30" level=info msg="2. pi-8p6tc"
time="2023-05-17T09:02:25+05:30" level=info msg="3. pi-8tkl6"
time="2023-05-17T09:02:25+05:30" level=info msg="4. pi-r862t"
=== RUN   TestCreatePeerPodWithJob/Job_Peer_Pod/Check_Peer_pod_created_via_job
pi-2nx5d -- StartError
Events of pod - pi-8p6tc
-- Starting
-- InvalidDiskCapacity
-- NodeHasSufficientMemory
-- NodeHasNoDiskPressure
-- NodeHasSufficientPID
-- NodeAllocatableEnforced
-- Starting
-- Scheduled
-- Pulling
-- Pulled
-- Created
-- Failed
-- Scheduled
-- Pulling
-- Pulled
-- Created
-- Started
pi-8p6tc -- Started -- Completed
pi-8tkl6 -- StartError
pi-r862t -- StartError
time="2023-05-17T09:02:27+05:30" level=info msg="Output Log from Pod:\n3.14156"
--- PASS: TestCreatePeerPodWithJob (133.45s)
    --- PASS: TestCreatePeerPodWithJob/Job_Peer_Pod (133.45s)
        --- PASS: TestCreatePeerPodWithJob/Job_Peer_Pod/Check_Peer_pod_created_via_job (2.28s)
PASS

Thanks for the investigation Sudharshan. I'm concerned that if we mark the tests as PASS when there is an issues with some of the pods created that it's effectively a false positive hiding the problem, but I'm not sure what the behaviour should be. I think ideally I would like it to have the status:

PASS - if all the pods are successful
WARNING - if 1+ pods fails, but one of them completes and gives the correct result
FAIL if none complete successfully
The warning shows that there are some issues. My problem is that I don't think there is a warning option in golang testing that I could see quickly

Hi @stevenhorsman ,
Used t.Skip() for warning
Now the test results will be like :

PASS - if all the pods are successful

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:172: SUCCESS: job-pi-5jlkh - Completed - LOG: 3.14156
time="2023-05-17T20:02:33+05:30" level=info msg="Output Log from Pod: 3.14156"
time="2023-05-17T20:02:34+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (32.30s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (32.30s)
        --- PASS: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.40s)
PASS

WARNING - if 1+ pods fails, but one of them completes and gives the correct result

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-b7v89 - StartError
    common_suite_test.go:149: WARNING: job-pi-m92mw - StartError
    common_suite_test.go:172: SUCCESS: job-pi-nd6ml - Completed - LOG: 3.14156
    common_suite_test.go:184: Expected Completed status on all pods
time="2023-05-17T20:21:05+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (93.97s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (93.97s)
        --- SKIP: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (3.07s)
PASS
ok      github.com/confidential-containers/cloud-api-adaptor/test/e2e   139.750s

FAIL if none complete successfully

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
    common_suite_test.go:100: timed out waiting for the condition
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-48m47 - StartError
    common_suite_test.go:149: WARNING: job-pi-5nm26 - StartError
    common_suite_test.go:149: WARNING: job-pi-bcz5j - StartError
    common_suite_test.go:149: WARNING: job-pi-js5mj - StartError
    common_suite_test.go:149: WARNING: job-pi-mx2jf - StartError
    common_suite_test.go:181: Job Failed to Start pod
    common_suite_test.go:189: Job Created pod with Invalid log
time="2023-05-17T20:34:21+05:30" level=info msg="Deleting Job... job-pi"
--- FAIL: TestCreatePeerPodWithJob (304.88s)
    --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod (304.88s)
        --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.10s)
FAIL
FAIL    github.com/confidential-containers/cloud-api-adaptor/test/e2e   353.265s
FAIL

Also Converted code structure to match with refactored code

Hi @stevenhorsman , Used t.Skip() for warning
Now the test results will be like :

PASS - if all the pods are successful

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:172: SUCCESS: job-pi-5jlkh - Completed - LOG: 3.14156
time="2023-05-17T20:02:33+05:30" level=info msg="Output Log from Pod: 3.14156"
time="2023-05-17T20:02:34+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (32.30s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (32.30s)
        --- PASS: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.40s)
PASS

WARNING - if 1+ pods fails, but one of them completes and gives the correct result

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-b7v89 - StartError
    common_suite_test.go:149: WARNING: job-pi-m92mw - StartError
    common_suite_test.go:172: SUCCESS: job-pi-nd6ml - Completed - LOG: 3.14156
    common_suite_test.go:184: Expected Completed status on all pods
time="2023-05-17T20:21:05+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (93.97s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (93.97s)
        --- SKIP: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (3.07s)
PASS
ok      github.com/confidential-containers/cloud-api-adaptor/test/e2e   139.750s

FAIL if none complete successfully

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
    common_suite_test.go:100: timed out waiting for the condition
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-48m47 - StartError
    common_suite_test.go:149: WARNING: job-pi-5nm26 - StartError
    common_suite_test.go:149: WARNING: job-pi-bcz5j - StartError
    common_suite_test.go:149: WARNING: job-pi-js5mj - StartError
    common_suite_test.go:149: WARNING: job-pi-mx2jf - StartError
    common_suite_test.go:181: Job Failed to Start pod
    common_suite_test.go:189: Job Created pod with Invalid log
time="2023-05-17T20:34:21+05:30" level=info msg="Deleting Job... job-pi"
--- FAIL: TestCreatePeerPodWithJob (304.88s)
    --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod (304.88s)
        --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.10s)
FAIL
FAIL    github.com/confidential-containers/cloud-api-adaptor/test/e2e   353.265s
FAIL

Also Converted code structure to match with refactored code

Hey Sudharshan - thanks for the update and demo. It's not ideal and I think we should raise an issue for the failure, but that seems the best we can do if we want to get the test delivered.

When I ran this locally I didn't see the SKIP, was that just because I got lucky this time and it worked on the first attempt?

Yes, this job have unstable behaviour , sometimes it will get completed on first attempt and sometimes it will fail two or three pods to reach completed status

Hi @steven ,
Update code with following changes

Increased BackoffLimit to 8
Increased WAIT_JOB_RUNNING_TIMEOUT to 10m

Thanks, locally I ran it to test it and got:
=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:150: WARNING: job-pi-2f8kb - StartError
    common_suite_test.go:173: SUCCESS: job-pi-84gh2 - Completed - LOG: 3.14156
    common_suite_test.go:150: WARNING: job-pi-gqclv - StartError
    common_suite_test.go:185: Expected Completed status on first attempt
time="2023-05-19T05:24:48-07:00" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (110.61s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (110.61s)
        --- SKIP: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (0.20s)
PASS

@mattarnoatibm - if you get a chance, can you review this to see if you have any suggestion about how this new jobs case integrates with the testCase framework please? Thanks!

Hi @mattarnoatibm ,
Updated code with above mentioned changes
Could you please review the code?
Thanks!

Hi @mattarnoatibm ,
Updated code with suggested changes

Hi @wainersm ,
Could you please review this PR?
Thanks!

Hey Sudharshan, I'm not sure quite the best way to document it - probably in the commit message and a comment in the test code, but I think we want to reflect that this is a weird test as sometimes the job doesn't work, so you have the skip as a form of warning, which isn't great. I think we've seen similar in the kata job too though, the approach taken there was just to sleep for a minute and hope that one job will have succeeded, but with peer pods that sleep would need to be longer, so we monitor until the first one succeeds. Otherwise I'm not sure this behaviour and reason would be obvious to people from seeing the code. If you could reference the issue raised for this as well that would help provide context. Thanks!

Hi @stevenhorsman , Used t.Skip() for warning
Now the test results will be like :
* PASS - if all the pods are successful

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:172: SUCCESS: job-pi-5jlkh - Completed - LOG: 3.14156
time="2023-05-17T20:02:33+05:30" level=info msg="Output Log from Pod: 3.14156"
time="2023-05-17T20:02:34+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (32.30s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (32.30s)
        --- PASS: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.40s)
PASS

* WARNING - if 1+ pods fails, but one of them completes and gives the correct result

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-b7v89 - StartError
    common_suite_test.go:149: WARNING: job-pi-m92mw - StartError
    common_suite_test.go:172: SUCCESS: job-pi-nd6ml - Completed - LOG: 3.14156
    common_suite_test.go:184: Expected Completed status on all pods
time="2023-05-17T20:21:05+05:30" level=info msg="Deleting Job... job-pi"
--- PASS: TestCreatePeerPodWithJob (93.97s)
    --- PASS: TestCreatePeerPodWithJob/job-pi_Pod (93.97s)
        --- SKIP: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (3.07s)
PASS
ok      github.com/confidential-containers/cloud-api-adaptor/test/e2e   139.750s

* FAIL if none complete successfully

=== RUN   TestCreatePeerPodWithJob
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod
    common_suite_test.go:100: timed out waiting for the condition
=== RUN   TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created
    common_suite_test.go:149: WARNING: job-pi-48m47 - StartError
    common_suite_test.go:149: WARNING: job-pi-5nm26 - StartError
    common_suite_test.go:149: WARNING: job-pi-bcz5j - StartError
    common_suite_test.go:149: WARNING: job-pi-js5mj - StartError
    common_suite_test.go:149: WARNING: job-pi-mx2jf - StartError
    common_suite_test.go:181: Job Failed to Start pod
    common_suite_test.go:189: Job Created pod with Invalid log
time="2023-05-17T20:34:21+05:30" level=info msg="Deleting Job... job-pi"
--- FAIL: TestCreatePeerPodWithJob (304.88s)
    --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod (304.88s)
        --- FAIL: TestCreatePeerPodWithJob/job-pi_Pod/Job_has_been_created (1.10s)
FAIL
FAIL    github.com/confidential-containers/cloud-api-adaptor/test/e2e   353.265s
FAIL

* Also Converted code structure to match with refactored code

@sudharshanibm3 are you using the same amount of pods on the PASS, WARNING and FAIL executions above? I got the impression that if you increase the amount of pods then it tend to FAIL.

hi @sudharshanibm3 , first of all, thanks for contribution this test case!
I reviewed it already and left a few comments. Apart from that, I think that func (tc *testCase) run() became a kind of convoluted with those spaghetti if job then test_job else if pod then test_pod blocks. Perhaps it should be refactored further, but I am okay if it is done later on a separated PR.

Thanks for your suggestions @wainersm ,

@sudharshanibm3 are you using the same amount of pods on the PASS, WARNING and FAIL executions above? I got the impression that if you increase the amount of pods then it tend to FAIL.

As per this issue #1004 , we have resolved the FAIL case by increasing BackoffLimit of the pod, so now we will get only PASS and SKIP/WARNING status only

Sorry @sudharshanibm3 - I picked the wrong PR earlier, can you rebase this one and then I'll re-test it locally. Thanks

Hi @stevenhorsman ,
Rebased the code with latest staging branch

Now code freeze has lifted and they have been no extra review changes for 2 weeks I think this is good to merge. Thanks for your patience!

I reviewed it already and left a few comments. Apart from that, I think that func (tc *testCase) run() became a kind of convoluted with those spaghetti if job then test_job else if pod then test_pod blocks. Perhaps it should be refactored further, but I am okay if it is done later on a separated PR.

@sudharshanibm3 - just to check, now that this PR is merged - do you have an issue/plan to work on this refactor that Wainer suggested soon? I just want to make sure we don't forget about it.

@sudharshanibm3 - just to check, now that this PR is merged - do you have an issue/plan to work on this refactor that Wainer suggested soon? I just want to make sure we don't forget about it.

Sure @stevenhorsman ,
Will create a separate issue and PR for that shortly, also in future it might required to toggle between multiple resources like job, pods, deployment, daemonset etc


Can't install angular/web-animations

Whenever I attempt to run an npm ci on one of the Cypress images that I'm running through GitLab's CI/CD pipelines, I get the following error:
npm ERR! /usr/bin/git ls-remote -h -t<EMAIL_ADDRESS>npm ERR!
npm ERR! Host key verification failed.
npm ERR! fatal: Could not read from remote repository.

Here is my cache stage, and the stage where the error happens, for reference:
cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - .cache/*
    - cache/Cypress
    - node_modules
    - build

npm install:
  image: cypress/browsers:node12.14.1-chrome85-ff81
  stage: install
  script:
    - npm ci

i changed ssh://.../angular to git+https://github.com/angular

@avelops Is this issue resolved?

@avelops Is this issue resolved?

it worked for me (the package.json change) but in another docker image - i haven't tested in cypress docker images, just wrote the solution i found here incase anyone gets this error


Composite types should implement Serializable

Can't use CompositeType directly as an ID with SpringData or as @Id with HOM. Also the SerializerTypeInferrer doesn't know about composite types

both of these are fixed but not in a released build.  if you get
"master" you can build yourself and will have this fix
On Wed, Feb 8, 2012 at 10:44 PM, mkolesnikov
<EMAIL_ADDRESS>wrote:

Can't use CompositeType directly as an ID with SpringData or as @Id with HOM. Also the SerializerTypeInferrer doesn't know about composite types

Reply to this email directly or view it on GitHub:
https://github.com/rantav/hector/issues/416


Upgrade to plk 0.14.6 + add UNION support

Issue #, if available:

Closes https://github.com/partiql/partiql-scribe/issues/55
Related to https://github.com/partiql/partiql-lang-kotlin/pull/1506

Description of changes:

Upgrades Scribe to partiql-lang-kotlin v0.14.6

v0.14.6 has not yet been released to Maven as https://github.com/partiql/partiql-lang-kotlin/pull/1506 needs to be merged in first
Tested with a local Maven published version of v0.14.6
Fixes some tests related to BETWEEN operator and ANTLR dependency internalizing

Adds UNION support

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Verified the transpiled test queries for each of the dialects.
For reference, commands for the table creation:
Redshift
CREATE TABLE SIMPLE_T (
    a BOOL,
    b INT4,
    c VARCHAR
);

INSERT INTO SIMPLE_T VALUES(
    true,
    1,
    'foo'
);

Spark
CREATE TABLE SIMPLE_T AS (SELECT true AS a, 2 AS b, 'foo' AS c);

Trino
WITH SIMPLE_T AS (
	SELECT true AS a,
		2 AS b,
		'foo' AS c
)


nanopolish extract not recognizing fast5 files

nanopolish-0.8.3 running on CentOS7
The nanopolish extract function appears to ask for FAST5 files as an input but then the -b, --basecaller option says it will "consider only data produced by basecaller NAME, optionally with given exact VERSION"
This does not make any sense to me because basecallers take FAST5 as inputs, and produce FASTQ files.
Also, the nanopolish index function calls for "-d nanopore_raw_file_directory reads.fastq"
The reads.fastq and the raw ont signal files (FAST5) are not the same, but they seem to be referred to interchangeably in the help files.
Please send an example of both commands being used with the appropriate file input.
Thank you.

[yrw4@biolinux nanopolish-0.8.3]$ ./nanopolish extract --help
Usage: nanopolish extract [OPTIONS] <fast5|dir>...
Extract reads in fasta format
  --help                           display this help and exit
  --version                        display version

-v, --verbose                        display verbose output
-r, --recurse                        recurse into subdirectories
-q, --fastq                          extract fastq (default: fasta)
-t, --type=TYPE                      read type: template, complement, 2d, 2d-or-template, any
(default: 2d-or-template)
-b, --basecaller=NAME[:VERSION]      consider only data produced by basecaller NAME,
optionally with given exact VERSION
-o, --output=FILE                    write output to FILE
Report bugs to https://github.com/jts/nanopolish/issues
[yrw4@biolinux nanopolish-0.8.3]$ ./nanopolish index --help
Usage: nanopolish index [OPTIONS] -d nanopore_raw_file_directory reads.fastq
Build an index mapping from basecalled reads to the signals measured by the sequencer
  --help                           display this help and exit
  --version                        display version

-v, --verbose                        display verbose output
-d, --directory                      path to the directory containing the raw ONT signal files. This option can be given multiple times.
-f, --fast5-fofn                     file containing the paths to each fast5 file for the run
Report bugs to https://github.com/jts/nanopolish/issues

nanopolish extract is an old subprogram that was used for data basecalled using albacore <= 2.0, which produced fast5 as output. You can ignore it unless you are working on old data.
Please follow this tutorial for an example of how to run nanopolish index:
http://nanopolish.readthedocs.io/en/latest/quickstart_consensus.html


Add HTML Rendering

This PR aims to solve #155
I have used flutter_widget_from_html which convert html into flutter widgets so that they can be previewed in the preview pane.

Expected Response:

This PR:

Hi @animator! The goal of this PR was to add HTML rendering, however it looks like I need to simply add a webview. Should I go ahead with that?

I had already shared more details with you on discord, in case you missed it.

WebView is a solution you can explore.

Can I work on this issue please?

Sure @monstajoe2002

I had already shared more details with you on discord, in case you missed it.
WebView is a solution you can explore.

Unfortunately, that's not possible with desktop apps in Flutter since the WebView feature is mobile only. Even then, desktop implementations don't work 100% especially when we don't have access to the request url from its repective widget.

Hey guys! I created a pull request for this feature here: https://github.com/foss42/apidash/pull/243


Remove unnecessary rules from .gitignore

Remove run*, test* and example-deconstructor* example-reformatter* rules from .gitignore.
Case:

Download lib from Github.
Add lib to your project
Push your project to Github.
Pull your project from Github.
Try to compile your project with libyaml.

Expected result:

All comiles and work

Actual result:

Libyaml doesn't compiles because of missing files (test files)

Error that I get:
make[2]: Entering directory '/tmp/rt/lib/libyaml/tests' make[2]: *** No rule to make target 'run-scanner.c', needed by 'run-scanner.o'.  Stop.

Note: I don't know why the run-* scripts were originally added to .gitignore.
A workaround: do git add -f libyaml, this will also add files that would be igored otherwise

I see this was changed in d050fe3f3006b55edf33a2ef91019a67d6c3fb10
Seems this was an oversight.

Created #177
Thanks!

@perlpunk, no problem!

Released 0.2.5!


fix: Add perm for showing DBC-UI in Global Nav

SUMMARY

Add perm check for showing DBC-UI inside the global nav create nav button, users must have can_write -> Database to be able to see the links
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

cc @yousoph

/testenv up

/testenv up

With gamma role set:

/testenv up

/testenv up


Clarify behavior of  decorator ordering

We need to make clear our philosophy and resolution method for functions such as:
@extract_fields({'out_value1': int, 'out_value2': str})
@tag(test_key="test-value")
@check_output(data_type=dict, importance="fail")
@does(_dummy)
def uber_decorated_function(in_value1: int, in_value2: str) -> dict:
    pass

Right now it is not clear, nor obvious.
Current behavior
This is what the graph looks like:

So it would be unexpected to see check_output over the output of extract_fields.
Steps to replicate behavior
Function code:
def _dummy(**values) -> dict:
    return {f"out_{k.split('_')[1]}": v for k, v in values.items()}

@extract_fields({'out_value1': int, 'out_value2': str})
@tag(test_key="test-value")
@check_output(data_type=dict, importance="fail")
@does(_dummy)
def uber_decorated_function(in_value1: int, in_value2: str) -> dict:
    pass

Expected behavior
check_output should probably operate over what's directly underneath that.
tag similarly should apply to all? or just what's underneath?
does should apply to uber_decorated_function
extract_fields is the last thing that's applied?
Additional context
Thoughts: can we create a linter that reorders decorators?

We are moving repositories! Please see the new version of this issue at https://github.com/DAGWorks-Inc/hamilton/issues/57. Also, please give us a star/update any of your internal links.
Note that everything else (slack community, pypi packages, etc...) will not change at all.