(Feature Request) Ability to use AOT in unit testing

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

Repro steps.

The log given by the failure.

Desired functionality.

At @angular/core/testing v4.2.0, .ngSummary.ts files are introduced to support to use AOT in unit testing ( https://github.com/angular/angular/blob/master/CHANGELOG.md#features-4 ).  Do you have a milestone about this?
I think it's useful to run unit testing with something like ng test --aot .
Mention any other details that might be useful.

If we could run unit tests in AOT than we would have caught the latest bug which was published with 4.4.1 (https://github.com/angular/angular/issues/19219) already on our build server, not just in staging, so this would be super useful.
I read in multiple places, that AOT should become default for angular 5 - is this true? would that resolve this issue afterwards?

Now that Angular@5 is released, this should be have more priority since we now need the reflect-es7 polyfills just to be able to run the unit tests: AOT can be enabled for serve/build, but not unit tests which is against the "AOT by default" promoted with Angular@5.

Sorry for asking a question here but this is a blocking issue for us.
Can anyone explain to me how to use relative template urls (aot style) in the source code, and then unit test that same source code with JIT..  i seem to be missing a trick?
or is there another trick to unit test with AOT?
thanks!

Any update on this issue?

There is a PR for it (https://github.com/angular/angular-cli/pull/8007), as as mentioned in https://github.com/angular/angular-cli/pull/8007#issuecomment-336973766 this support is still experimental and we'll wait until the feature stabilizes before incorporating it into the CLI.

Just a +1 for this. Hopefully the compiler folks determine that AoT support is stable soon. Not only would this AoT compile errors, but it should also vastly speed up test runs because all of the components won't need to be re-compiled over and over again for every single spec method.

This would be very useful. Since we are adopting AOT since 4.0, we ended up having another build step with AOT to ensure everything works

@sinedied with Angular CLI v6 you could use a separate polyfills.ts for the Unit tests in JIT mode. That means you don't need the reflect-ts7 for the real build 🎉

@sinedied with Angular CLI v6 you could use a separate polyfills.ts for the Unit tests in JIT mode. That means you don't need the reflect-ts7 for the real build 🎉

That's good news for a start, but still I don't like the fact that the code going to production is not the same one being tested, with different polyfills and build methods.

That's good news for a start, but still I don't like the fact that the code going to production is not the same one being tested, with different polyfills and build methods.

Our development, QA and E2E testing is done using AOT mode - I can "live" with that danger/rsik that JIT it used for the unit tests for the time being, but totally agree that the AOT support is long overdue :)

There doesn't seem to be a way to use a different polyfill for e2e?
Which means I get the error Failed: Angular could not be found on the page when import 'core-js/es7/reflect'; is commented out.

@timbru31 How are you running your E2E tests in AOT mode? I am on ng6 and there is no --aot option.

Just as a note, the wiki states it is possible:
https://github.com/angular/angular-cli/wiki/test

@boldwade I can't find anything on the wiki you linked that states that aot can be used.

It's ambiguous. The wiki page (listed above) links to the ng test page with supposed options that are available for said command. At the very least, it implies, at least to me, that I can run ng test with --prod options.

But does this mean that aot will/can be used?

right, see the confusion...

I suspect this would also make it possible to include template binding expressions in code coverage reports (as suggested here https://github.com/angular/angular/issues/427) which would be useful - currently I find the code coverage report pretty meaningless for components that include a lot of logic in their templates.

@filipesilva by what feature is this blocked?

Yesterday, I tried to run tests in AOT + IVY and got some success for some simple tests.
I got problem with type checking in templates. I had NO_ERRORS_SCHEME but type checking was enabled for unknown components.

I tried Karma and enableIvy: true too. And I checked out R3TestBedCompiler(not AoT but JiT) makes unit tests so faster :tada:
For now, I close this issue because my motivation, which was to improve performance of unit testing, has already achieved .

@Quramy Which version did you try?

 Can you post more info?

@giggio I've commented https://github.com/angular/angular/issues/12409#issuecomment-561908267


How to only show error when submit?

Right now this widget always shows a validation error right away before the user has the chance to enter any text.
Is there an option to only show the error when submit?

this is a flutter issue, you can play with auto validate mode


Confusion arises regarding how the ctrlmesh-proxy's sidecar effectively proxies requests to the operator's k8s api-server

General Question

I am confused about how the sidecar of ctrlmesh-proxy proxies requests to the operator's k8s api-server. Although ctrlmesh-proxy has been successfully injected into the operator, it has not been injected into initContainers. The proxy-init.sh script is also used as an init image, and the image address is not filled in at startup. Additionally, transparent proxying for http_proxy only proxies fault injection and circuit breaker because the operator typically accesses via serviceAccount, so fake-kubeconfig should not take effect. I hope you can help clarify this. Thank you. @Eikykun

There are currently two methods to implement proxying requests to the apiserver:

(Default) Replace kubeconfig's args or env with fake-kubeconfig. In controller-runtime(controller-runtime/pkg/client/config/config.go), the priority for using certificates is --kubeconfig arg > KUBECONFIG > ServiceAccount. However, this method cannot proxy all HTTP requests.

(In testing) Modify iptables to forward requests to a specific port on localhost.
At the moment, an init container is not being used by default to initialize iptables. We plan to make this feature available in a future release.

If you are interested in this, welcome you to participate in construction with us 👏 @village-way

There are currently two methods to implement proxying requests to the apiserver:

(Default) Replace kubeconfig's args or env with fake-kubeconfig. In controller-runtime(controller-runtime/pkg/client/config/config.go), the priority for using certificates is --kubeconfig arg > KUBECONFIG > ServiceAccount. However, this method cannot proxy all HTTP requests.
(In testing) Modify iptables to forward requests to a specific port on localhost.
At the moment, an init container is not being used by default to initialize iptables. We plan to make this feature available in a future release.

If you are interested in this, welcome you to participate in construction with us 👏 @village-way

There are currently two methods to implement proxying requests to the apiserver:

(Default) Replace kubeconfig's args or env with fake-kubeconfig. In controller-runtime(controller-runtime/pkg/client/config/config.go), the priority for using certificates is --kubeconfig arg > KUBECONFIG > ServiceAccount. However, this method cannot proxy all HTTP requests.
(In testing) Modify iptables to forward requests to a specific port on localhost.
At the moment, an init container is not being used by default to initialize iptables. We plan to make this feature available in a future release.

If you are interested in this, welcome you to participate in construction with us 👏 @village-way

I finally got it, thank you very much for your answer.


Making storechain public

Hi,
I'm trying to use your (great!) crate on quite a large model: ~2500 parameters, 25000 walkers and 100 iterations. This means that emcee tries to reserve a very large amount of memory (~50GiB if I remember correctly) and crashes at the end of the first iteration.
I see you have a storechain variable on EnsembleSampler which is not public (but does have an associated test): setting this to false fixes the problem.
Is there a reason it's not public? If not, then I can put together a patch documenting the variable and making storechain public.
Best wishes,
Josh

Hi, thanks for your interest in my crate!
That's a huge model! Have you tried using the python version? Just for my curiosity you understand, I would hope the Rust version would be more efficient :P
You're right, it is private (I don't think with a good reason) and if you've found it useful then I'm happy to expose it with some documentation. I would think a method name like:
sampler.store_chain(true);

If you're happy to put together a patch then I'd welcome the contribution, thank you!

On 10 Jun 2019, at 21:59, Joshua Hunt<EMAIL_ADDRESS>wrote:
Hi,
I'm trying to use your (great!) crate on quite a large model: ~2500 parameters, 25000 walkers and 100 iterations. This means that emcee tries to reserve a very large amount of memory (~50GiB if I remember correctly) and crashes at the end of the first iteration.
I see you have a storechain variable on EnsembleSampler which is not public (but does have an associated test): setting this to false fixes the problem.
Is there a reason it's not public? If not, then I can put together a patch documenting the variable and making storechain public.
Best wishes,
Josh
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm afraid I haven't tried the python version, no.
Sure, I'll put together a patch when I have time, probably on the weekend.

Also, thin is currently exposed as just a pub field on the struct: would you rather just make the field storechain public? It doesn't feel like having a setter method gains you much here unless e.g. you expect to change the way you internally represent the sampler's settings.

You're absolutely right, i'm happy to just expose the member variable to be public. Could you implement this and check that the tests pass?


bug: Menu does not close after language selection

** discord username: Aşkın#1280 **
Main Page. When change language menu dosent close.  I added video.

Devıce: on desktop
Operating System (with the version): Apple M1 Pro
Version Google Chrome
Browser Version lastest

Mobile Phone Information
https://user-images.githubusercontent.com/101400165/218258090-b2ee12ad-54b3-469a-a867-05233d792664.mov
Additional Context
Add any other context about the bug here

Fixed it. can send a PR if approved.

this should be fixed by PR #677

retested. fix validated

retested. fix validated

@oguzergul Why #780 is reverted? Isn't it solved the problem?

Merge PR 817 after reopening this issue


Feature request: Windows Event Collection (part of Syslog-ng)

At present, centralized WEC requires each Windows node to send to a Windows server and installing a Splunk UF there to read the eventlogs. This is then sent to the indexers. It would be more resilient and require less resources if WEC could be performed directly by SC4S. See:
Syslog-ng WEC administration guide
If there is some licensing issue of using a Syslog-ng PE feature, then maybe this can be implemented independantly for SC4S? Keep in mind that eventlogs are crucial for pretty much any Windows logging.

I believe the Syslog agent is licensed in addition to PE not part of PE. Presently our implementation wraps OSE only as we don't have access to the PE code for testing. I will see if we can change this in the future.

I believe the Syslog agent is licensed in addition to PE not part of PE. Presently our implementation wraps OSE only as we don't have access to the PE code for testing. I will see if we can change this in the future.


portmod: 2.1.0 -> 2.4.2, bsatool2: init at 2.0.1

Description of changes

Update portmod from 2.1.0 to 2.4.2
Add bsatool2 as a binary. It should fix the problem of portmod not working with fallout: new vegas and other, more recent Bethesda games. Turns out this actually isn’t needed, but I’ll still keep it, as I already needed a tool like this in the past, and might need one again in the future.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I checked that it work well with Morrowind. I add two issues, related to updating:

The metadatas should be update (portmod sync)
With morrowind, I add to unmerge openmw-config and merge configtool (portmod <prefix> merge -C openmw-config and portmod morrowind merge configtool. But it seems that everything depends on configtool.)

Fix https://github.com/NixOS/nixpkgs/issues/198109 and should fix https://github.com/NixOS/nixpkgs/issues/197624 (untested for now)

So, after some test, I found two issues:

New Vegas doesn’t work (that’s some issue with portmod, I think)
Mirrors does not work (it’s an API change in GitLab)

Actually, the mirror issue is just a problem with portmod metadata repo.

Turns out that a precompiled bsatool2 is fetched from portmod, and that it isn’t required. I’m a bit hesitant on keeping or removing it (knowing it could be usefull for some toying around in Skyrim. already had issue decompiled modern bsa in the past).
The other issues with fallout are all issues with the metadata repo. I’ll make a PR upstream of my change, but it won’t require change in NixPkgs, as it fetch it at runtime.

Should be ready for review now.

@marius851000 if you could rebase this, merging is imminent

@marius851000 Can this get pushed over the finish line?

Oh, sorry, didn't looked at tyis for some time. I'll do once I'm done with my game jam and potentially r/place, so probably around the end of this month.

Closed as a similar commit was made as 00ee658dfbcaac61a80a0b7ba1bb33d5b5caca44


M8bot not posting stream announcements (overall acting sluggish at moments)

I have M8bot in 2 servers for two streamers. They each have an entire list of streamers they love to shout out in their current streams text chat. However, it seems the bot does not alert the discord they are live. It'll send a message for some streams going live but not others. The bot has all permissions needed yet it still fails to notify. Also, it acts quite sluggish sometimes with commands.
Ping: Pong! Latency is 24ms. API Latency is 60ms

I am currently working on a fix. The issue is due to the bot's sharding (which is required by discord after a bot joins 2500 servers).
Sorry for the issues.

Good afternoon,
Was just wondering if there was a fix for this yet or it was still in development? Just discovered the bot this week and love the features but the inconsistent announcements are a bummer.
Thanks for the awesome work!

Good afternoon,
Was just wondering if there was a fix for this yet or it was still in development? Just discovered the bot this week and love the features but the inconsistent announcements are a bummer.
Thanks for the awesome work!

Still working on a solution, I apologise for the inconvenience


Tasks class fails in example notebook with latest version of HDMF

Could you help me with the following issue.  Using the dev branch of HDMF, I'm getting the following error when trying to run the example notebook.

When looking at the help for the Tasks class, at least at first glance it seems to look ok:

Weird. I am using an older version of dev. I'll take a look.

The following recent PR could be relevant  https://github.com/hdmf-dev/hdmf/pull/741

After some fiddling I saw that Tasks has two unnamed datasets, the task_program and the task_schema. I gave them names, but was met with the error that it can't have a name if quantity was "+", then it can't have a name. I commented out quantity so that It's back to 1. This fixed the error; however, we don't have quantity as "+" anymore. Thoughts?

I commented out quantity so that It's back to 1.

I think that is fine since if you were to use multiple programs I think one would would probably create separate Tasks rather than having multiple programs for a single task. @rly what do you think?
However, I think we should still investigate the error in HDMF as well, since the schema was valid and the class generation should have still worked.

I gave them names,

When using a quantity of 1 or ?, we should use the singular for the names, i.e, we should change the name task_programs to task_program and task_schemas to task_schema``


Multiple bibliography items' citations and "et al."

Apologies if this question is out of place or overly ignorant. I've just updated to econsocart.cls in the midst of drafting my first submission to Econometrica. I have a semi-large library of relevant citations exported from Zotero to a .bib file that's read into the .tex file with
\bibliography{my_bib}
\bibliographystyle{econometrica}

I need to cite multiple bibliography items in-line. The full list of names for each citation is quite long, so I'll need to use et al. for the in-line citation and leave the full list of names for the actual bibliography. Is there a recommended way to accomplish this?
I see this Stack Exchange answer that recommends using a .bst file with the natbib class, but I'm not sure if that's compatible with the econsocart / Econometrica way of doing things (or if perhaps there's an official econsocart .bst file used to achieve it)?

Hello,
usage of natbib package and some .bst for this task is fine.
I'll try to find is there any official .bst for this.

@hack-r could you please confirm that by adding \usepackage{natbib} and
\bibliography{my_bib}
\bibliographystyle{econometrica}

joint with a my_bib.bib file exported from Zotero in the compilation folder, you are able to use automatic references with \cite{referencekey}. I am not able to replicate your example. This is what I have as a resulte trying to cite \cite{hildenbrand_upper_1972}
Package natbib Warning: Citation `hildenbrand_upper_1972' on page 3 undefined o
n input line 187.

Thanks!

including econometrica.bst solved my problem

econometrica.bst is not related to this class. The original plan was to write a new (more integrated) bst, but since it is not in our priority list, this will take some time.
Anyway, if econometrica.bst solves the problem, then go with it. Thanks @sebacea !

ecta-fullname.bst was added.


Use json-iterator in Kubelet client.

This change is

/retest

/lgtm
@wojtek-t PTAL

This looks fine.
@kawych @piosz - did you manage to run any benchmarks/load tests with this change?

Karol has some results.

/retest

/test pull-heapster-e2e

This is one of changes, the other is #1906. This alone doesn't impact performance significantly - the test with 100 nodes and 3k user pods shows no reduced memory usage and CPU usage reduced only slightly (20m vs 18m). This was on standalone instance of heapster.

/retest

/lgtm


Is working with boosts supported or planned to support?

Just interested if i've not found it in grammers or it is not supported yet.
https://core.telegram.org/methods#working-with-boosts-
Thanks for your reply!

Friendly methods in the client, probably not. But the necessary methods should be there. Though you may need to use the git version and to build docs locally to find them inside the grammers-tl-types.


x/website: Add OGP to tour

Add some ogp/twitter meta for the Go tour.
Since these need to be SSR, I've opted to executing a template
each time.

Twitter

Slack

Discord

None of these utilize an image, feel free to let me know if there is one you would prefer/like to use. One note for Twitter, it seems the card wants an absolute URL for the image (Discord was fine with relative).


Add a config for circleci which builds the doc preview

The swagger build doesn't work for lack of the Cross Origin Header from circleci, but the documentation one does.

Build on my fork here: https://circleci.com/gh/Cadair/matrix-doc/tree/circleci

One thing that'd be nice is to have it run on branch/pr that isn't the master branch. Things that go into the master branch are pre-approved and don't really benefit from this kind of review.
Hooking it up to github status checks would be cool too :)

So circle will build on PRs and report build status like TravisCI. I have a bot that on a successful build posts a commit status with the link to the artifact uploaded by circle

yep! It's this but it needs some generalising to support things that's not standard sphinx html output. I am working on it :)

Awesome :D Please update us here when it's ready

@turt2live: any reason we shouldn't just merge this and enable it as it stands? The bot can happen later.

It's annoyingly difficult to get to the generated output, but otherwise no technical reason.

LET'S DO IT.

\o/ https://2-24998719-gh.circle-artifacts.com/0/root/project/scripts/gen/index.html

this might be a silly question, but couldn't we just change this to do a curl hit on the github api to post a comment on the relevant PR?

A comment might be spammy. From the sounds of it, the bot posts a commit status with a link to the docs, which I think is still possible in the line you highlighted.

The main reason I ended up with the bot arranged like it is (using circle ci webhooks and api calls) is to prevent people from opening PRs and being able to control the posting to github of either the commit status or comments.

I will try and do the bot upgrades next week when I am back at home.


M1 Mac    building for iOS Simulator, but linking in dylib built for iOS, file '/Users/xxx/Desktop/Mattermost-mobile/node_modules/react-native-webrtc/ios/WebRTC.framework/WebRTC' for architecture arm64

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.
For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/
If you've found a bug--something appears unintentional--please follow these steps:

Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary
Bug report in one concise sentence
Environment Information

Device Name:
OS Version:
Mattermost App Version:
Mattermost Server Version:

Steps to reproduce
How can we reproduce the issue (what version are you using?)
Expected behavior
Describe your issue in detail
Observed behavior (that appears unintentional)
What did you see happen? Please include relevant error messages, screenshots and/or video recordings.
Possible fixes
If you can, link to the line of code that might be responsible for the problem

Probably some gems needed for cocoapods are failing
I think you need to make sure ffi is installed with your arch.
Something like arch -x86_64 gem install ffi then in the ios folder run pod install

I tried a lot of things.
It doesn't work.
Only the Rosetta mode works.

https://github.com/mattermost/react-native-webrtc is being built and vended as a .framework, not as an XCFramework, and hasn't been rebuilt since 2019 and hasn't been built with arm64 iOS Simulator support.
For pre-built dependencies to run natively on an arm64 Mac under the iOS simulator, they need to be built specifically for the Simulator with the arm64 architecture, and to avoid clashing with arm64 symbols for native iOS devices, the result needs to be packaged as an XCFramework.


support reapply method in composite gate

Summary
Fix #675
Details and comments
Since current composite gate do not have the reapply() method, the circuit generated by composite gate can not be extended or combined with other circuits.

Thanks for both raising the issue and fixing it @chunfuchen!


How to split schemas into separate files?

userSchema: (author schema like the same)

export const schema = [`
type Email {
address: String
verified: Boolean
}

type User {
emails: [Email]
username: String
randomString: String
}
`];

rootSchema:

import { schema as userSchema, resolvers as userResolver } from './user/schema';
const rootSchema = [`
type RootQuery {
author(name: String): Author
user: User
}

schema {
query: RootQuery
}
`]

export const schema = [...rootSchema, ...userSchema, ...authorSchema];

When I trying to contact schemas into 1 typedefinition in GitHunt way(seems its the only one example had separate schemas), I got this:
[ '\n   type RootQuery {\n    author(name: String): Author\n    user: User\n   }\n   \n   \n   schema {\n    query: RootQuery\n  }\n', I20160704-11:08:53.149(8)?   '\n  type Email {\n    address: String\n    verified: Boolean\n  }\n  \n  type User {\n    emails: [Email]\n    username: String\n    randomString: String\n  }\n', I20160704-11:08:53.149(8)?   '\n# This uses the exact field names returned by the GitHub API for simplicity\ntype Author {\n    name: String\n    books: [Book]\n  }\n  \n  type Book {\n    name: String\n    author: [Author]\n    \n' ] { RootQuery: { user: [Function: user], author: [Function: author] }
Also I found the generateSchema in docs is deprecated. And I have no idea how to use the  GraphQLSchema instance generated.

Yes, this is not very well documented at the moment. A type definition can contain other imported type definitions. If they are circular, you can use a function that returns an array as type definition. You should use the makeExecutableSchema function from graphql-tools (not apollo-server) here: https://github.com/apollostack/graphql-tools/blob/88eadb99a11733fb11726df539d6fe1bb3be9a6f/src/schemaGenerator.js#L67
We're planning on making a big push for documentation and content starting next week, so this should be more well-documented soon!

Thanks for answer.
When I trying to use makeExecutableSchema , I still got error when using concated typeDefs:
Am i miss something when doing this?
export const schema = [...rootSchema, ...userSchema, ...authorSchema];

/Users/walter/.meteor/packages/meteor-tool/.1.3.4_1.mi2rro++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:280
W20160704-14:55:00.879(8)? (STDERR) 						throw(ex);
W20160704-14:55:00.879(8)? (STDERR) 						      ^
W20160704-14:55:00.879(8)? (STDERR) Syntax Error GraphQL (27:21) Expected Name, found EOF
W20160704-14:55:00.880(8)? (STDERR)
W20160704-14:55:00.880(8)? (STDERR) 26:     name: String
W20160704-14:55:00.880(8)? (STDERR) 27:     author: [Author]

That should work just fine. Are you sure you don't have a syntax error in your file, like a missing } after [Author]?

Yes I fixed it by remove a comment line. Close.
thank you

@helfer could you show a sample, how to use the makeExecutableSchema function?

Yes, I'll write some documentation today or tomorrow, including an example.

@helfer are you ready? Where can I find the docs & example?

up

+1 for docs on merging schemas and resolvers

Sorry for the delay, we're going to do a major rewrite of the documentation soon, so this might actually take even longer. In the meantime, here's the function signature:
function makeExecutableSchema({
  typeDefs, // shorthand type definitions
  resolvers, // resolve function definitions
  connectors,
  logger, // logging function to be called for every resolver
  allowUndefinedInResolve = false,
  resolverValidationOptions = {},
})

{
    requireResolversForArgs = true,
    requireResolversForNonScalar = true,
}

@helfer Thanks, but unfortunately it's not solve my problem. My app is modularity, and in every module have queries in the Query. So I need to merge this queries to one before I gave it to the makeExecutableSchema.
For example:
post.module.js
const schema = `

type Query {
	posts(limit: Int, offset: Int, sort: String): [Post]
	post(id: Int, code: String): Post
}

type Post {
	id: Int!
	code: String!
	title: String
	content: String
	author: User!
}

type Mutation {
	upVote(postID: Int!): Post
	downVote(postID: Int!): Post
}

user.module.js

const schema = `
type Query {
	users(limit: Int, offset: Int, sort: String): [User]
	user(id: Int, code: String): User
}

type User {
	id: Int!
	code: String!
	fullName: String
	email: String
	username: String
	provider: String
	roles: [String]
	verified: Boolean
	gravatar: String
	lastLogin: Timestamp
	posts(limit: Int, offset: Int, sort: String): [Post]
}

type Mutation {
	createUser(userID Int!): User
	deleteUser(userID: Int!)
}
`

So I need to merge the Query definitions too. In schemaGenerator the concatenateTypeDefs functions concatenate the typeDefs only.
Are there any solution for this problem in the apollo-server or in the graphql-tools?

@icebob Yeah, that's not going to work, because you need to have unique names for everything.
If you want, you could probably write a mergeSchemas function which merges different schemas and even namespaces them. It's not that difficult, all you'd have to do is look into the document and produce a new merged one.

Here's a hacky inspiration,
File1.js,
// ----------------------------------------------------------------------- Schema & Resolvers

// ------------------------------------ Schema
const typeShard = `
type Planet {
  id: String
  name: String
  diameter: String
  gravity: String
  climate: String
  terrain: String
  rotationPeriod: String
  population: String
  orbitalPeriod: String
  surfaceWater: String
}
`;

const queryShard = `
planets: [Planet]
`;

// ------------------------------------ Resolvers
const resolvers = {
  Query: {
    planets() {
      return API.fetch();
    },
  },
};

// ----------------------------------------------------------------------- Exports

export { typeShard, queryShard, resolvers };

File2.js
// ----------------------------------------------------------------------- Schema & Resolvers

// ------------------------------------ Schema
const typeShard = `
type SomeOtherType {
  id: String
  ....
}
type RecordsAndMetaData {
  records: [SomeOtherType]
  totalRecords: String
  currentPage: String
}
`;

const queryShard = `
recordsAndMetaData(currentPage: String): RecordsAndMetaData
`;

// ------------------------------------ Resolvers
const resolvers = {
  Query: {
    recordsAndMetaData(root, { currentPage = '1' } = {}) {
      return API.configure({ currentPage });
    },
  },
  RecordsAndMetaData: {
    records() {
      return API.fetch();
    },
  },
};

// ----------------------------------------------------------------------- Exports

export { typeShard, queryShard, resolvers };

MergeAndCompileStuff.js
// ----------------------------------------------------------------------- Import stuff
import _ from 'lodash';

// ------------------------------------ Data Emulation
import { typeShard as ts1, queryShard as qs1, resolvers as rs1 } from './server/data-emulation/dataEmulation.js';
import { typeShard as ts2, queryShard as qs2, resolvers as rs2 } from './server/data-emulation/paginate.js';

// ----------------------------------------------------------------------- Make stuff

// ------------------------------------ Compile schemas

const compiledSchema = [`
${ts1}
${ts2}
type Query {
  ${qs1}
  ${qs2}
}
schema {
  query: Query
}
`];

// ------------------------------------ Merge resolvers

const mergedResolvers = {};

_.map([rs1, rs2], function (resolverShard) {
  _.map(resolverShard, function (resolvers, outerKey) {

    if (mergedResolvers[outerKey] === undefined) {
      mergedResolvers[outerKey] = {};
    }

    _.map(resolvers, function (resolver, innerKey) {
      mergedResolvers[outerKey][innerKey] = resolver;
    });
  });
});

// ----------------------------------------------------------------------- Export stuff
export const thisPackage = 'sandbox:lib-transmit';
export { compiledSchema as schema, mergedResolvers as resolvers };

@dbx834 thanks, your solution will be good.

If there are namespaces in GraphQL, it solves my problem.
Meanwhile this is my solution to merge schemas & resolvers (similar to @dbx834 solution): https://gist.github.com/icebob/553c1f9f1a9478d828bcb7a08d06790a

I was wondering, whether solution posted by @icebob  is still valid in latest Apollo version?

Yes, I'm using with new Apollo version.

You can additional check when there is no mutation used.
moduleSchema.schema.mutation.trim() != '' ? moduleMutations.push(moduleSchema.schema.mutation): null ;

.....
const moduleTypeMutation = moduleMutations.length > 0  ? `
type Mutation {
${moduleMutations.join('\n')}
}
` : '';

...
const generateSchema = `
type Query {
	${moduleQueries.join('\n')}
}
${moduleTypeDefinitions.join('\n')}
${moduleTypeMutation}
schema {
  query: Query
}
`;

Has anyone worked out a more elegant solution to this problem other than joining everything by hand?
It's unrealistic to expect to have all types in the same file.

same inquiry as @PierBover  here ...

@PierBover @vmatekole we're having a conversation about schema merging/joining over on another repo, please come join us! https://github.com/apollographql/graphql-prism/issues/1

Thanks @helfer — I will join the conv. Incidentally, I came across this and currently giving it a spin — https://github.com/okgrow/merge-graphql-schemas. I haven't looked under the hood but on first use it appears to fulfil basic merging reqs.


Configuring Webcam with Docker

Problem description
Hello, I am using OpenCV in a Python Flask App which uses Facial encoding for Employee registration. I have used a production server using Gunicorn.
gunicorn --config gunicorn_config.py app:app
The gunicorn_config file is as follows:
bind = "<IP_ADDRESS>:5000" threads = 4 certfile="localhost.crt" keyfile="private.key" accesslog="-" loglevel = 'info' errorlog="-"
I am deploying my App on Docker containers. I have first created a docker image and then used Docker compose to deploy it. I am running the docker app as follows:
docker run -t --env="DISPLAY" --volume="/tmp/.X11-unix://tmp/.X11-unix:rw" --device="/dev/video0:/dev/video0" -p 5000:5000 -d docker-flask .
I have followed this tutorial for this: https://medium.com/@zwinny/docker-using-webcam-9fafb26cf1e6
The problem I am facing now is that when any person hits the URL at port 5000(which I am mapping) it always opens the camera connected to the NUC where the docker container is running, while I want the camera connected to the local computer to run.
I am using OpenCV for facial registration and so am accessing the camera using the following code.
camera = cv2.VideoCapture(0)
I have tried modifying the number in Video capture but none of it seems to be working. Please help me on this issue.

Thanks for sharing this. As it is an issue of support and not an issue related to the documentation, I will close it. You may try the Docker Community Forum for help.


I12385 exp

test deploy to exp

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

  Generated by :no_entry_sign: dangerJS against 7150e73eb9650feb27a07b48b2d2e192c3d205e2


No const variants for many classes

Lack of them makes these tools inconvenient to work with in some situations.

I do not know what you mean by "no const variants for many classes." What are you trying to do that the tools are inconvenient?

It was my own mistake. That's why I closed the issue!

Thank you for clarifying. I am open to suggestions on how to improve the code. If you have problems using the code, feel free to contact me. Typically I provide fast turnaround on issues.


Fix or remove all missing tests, remove ported_to_ash tag

Restore the CI

Just for reference:

OTA Operation canceling is tracked by #225 and #266
2 and 3 are handled by the fact that we drop support for v0.1, so we assume v1.0


Request body schema empty in version 2.0.3

Upgrading my springfox library from 2.0.2 to 2.0.3 (#814) seems to have caused a regression.
The request parameters section for a POST to my API now shows an empty JSON hash {} in the model schema. In version 2.0.2, it works flawlessly.
I haven't had time to dig any deeper yet. I'll update the ticket if I get a chance to.

Would appreciate if you could provide steps to reproduce or a breaking test perhaps.

Hi @dilipkrish. I can still reproduce this by only changing the dependency version in my pom.xml. I haven't had time to assemble a minimal example or test case. I'll let you know if I can get something together.

@igilham any updates on this? Has this been resolved

@dilipkrish I'm afraid not. I haven't had the time to experiment or dig into a root cause.

Im closing this issue for now. Please reopen when you have some details.


Implementing Weather Data Provider API Integration

To retrieve weather data for our console application, we need to implement the integration with our chosen weather data provider's API. This involves designing and coding the parts of our application that communicate with the API, retrieve data, and handle any possible errors.
Here are the tasks we need to complete for this issue:

API Integration: Implement the actual integration with the chosen API. This includes making HTTP requests, handling responses, and error handling.
Data Parsing: Parse the data received from the API into a format that our application can use.
Error Handling: Implement robust error handling for potential issues such as network failures, API rate limits, or data unavailability.
Testing: Write tests to verify that our API integration works as expected under different conditions.

Acceptance Criteria:

Our application can successfully retrieve and parse weather data from the chosen provider's API.
Errors are properly handled and do not crash the application. The user is informed when the weather data cannot be retrieved.
Tests confirm the correctness of the API integration and its resilience to common failure scenarios.
The implemented functionality is documented so that other team members can understand how to use it.
Name should contain a specific API name to explicitly inform that it is used.

We found this issue to huge to be as it is. We separated this issue into two new ones -> #36 & #37.


CardStack dirty. '!_dirty': is not true.

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following assertion was thrown while rebuilding dirty elements:
'package:flutter/src/widgets/framework.dart': Failed assertion: line 4224 pos 12: '!_dirty': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md
The relevant error-causing widget was:
CardStack file:///Users/***/lib/main.dart:123:17
When the exception was thrown, this was the stack:
#2      Element.rebuild (package:flutter/src/widgets/framework.dart:4224:12)
#3      BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2627:33)
#4      WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:883:20)
#5      RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:284:5)
#6      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1113:15)
...

Thank you

@cihatduyku
Closing as additional information isn't provided


clh: Complete the 'seccomp' filter list based on the workload from Kata's CI

Which feature do you think can be improved?
As discussed in the issue https://github.com/kata-containers/runtime/issues/2899, the incomplete list of seccomp filter from cloud-hypervisor can introduce (random) failures in our CI jobs. As a workaround, the seccomp option of clh is temporarily disabled  in kata.
How can it be improved?
We should collect the missing syscall triggered by Kata's CI workload, and added them to clh's seccomp filter list. Once we have a complete list (for kata's CI workload), we should bring the seccomp option of clh back to kata, so that we can leverage this security feature from clh.

As a first run of my local VM on the failing tests reported by the CI (e.g. CPU update constrains), I see the following missing syscall: brk. This syscall also contributed to the instability of cloud-hypervisor's CI. It was added to all worker threads of clh (after release v0.9.0).

/cc @jcvenegas @amshinde

@likebreath - I think we can close this issue now?

@jodh-intel Let's keep this one before I do more experiments on whether the seccomp filter is now sufficient to run all the workload from kata's CI jobs. Also, as @amshinde advises, we will also provide an option for users to enable and disable the seccomp filter.

Hi @likebreath - can we close now?

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:
All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

http://lists.katacontainers.io/pipermail/kata-dev/2020-November/001601.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-April/001843.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-May/001896.html

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.


Update README.md

See at https://github.com/msabramo/sshrc/blob/patch-1/README.md

Hey, I'm just not sure I like your version of the readme more. Thanks for submitting though. Is there a typo or something critical that I missed?

Nothing critical I don't think. I think all I did was put backquotes around filenames and stuff so they render in a monospace font, as that seems to be fairly common and I like the way it looks. If it's not your cup of tea, no big deal. Thanks for sharing sshrc!


use hub and tag from istio/pkg DockerBuildInfo

https://github.com/istio/istio/issues/18173

@carolynhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

mandiff_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

mandiff_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test mandiff_operator

gencheck_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

mandiff_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test mandiff_operator

gencheck_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test gencheck_operator

e2e_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

gencheck_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test gencheck_operator

e2e_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test e2e_operator

mandiff_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

e2e_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test e2e_operator

mandiff_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test mandiff_operator

gencheck_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
a14b5917767903a507bd5aa2669dc359123bbfe1
link
/test lint_operator

mandiff_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test mandiff_operator

gencheck_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test gencheck_operator

e2e_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mandiff_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test mandiff_operator

gencheck_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test gencheck_operator

e2e_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test e2e_operator

test_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

yes, that test was not merged. We should update that test also. I'm going to make that commit

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test gencheck_operator

e2e_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test e2e_operator

test_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test test_operator

mandiff_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test e2e_operator

test_operator
ff6902be0b4784343fe842b05e97367d77b6a9ee
link
/test test_operator

mandiff_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test mandiff_operator

gencheck_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mandiff_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test mandiff_operator

gencheck_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test gencheck_operator

e2e_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test e2e_operator

test_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test gencheck_operator

e2e_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test e2e_operator

test_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test test_operator

mandiff_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test e2e_operator

test_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test test_operator

mandiff_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test mandiff_operator

gencheck_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test e2e_operator

test_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test test_operator

gencheck_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
48aaa4189a3011331c0a7f172ae04e6ebb7e6329
link
/test e2e_operator

gencheck_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test gencheck_operator

test_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test gencheck_operator

test_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test test_operator

e2e_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test gencheck_operator

test_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test test_operator

e2e_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

test_operator
bb30174be82471d76eb0d2b2bcf9ae52a11910ee
link
/test test_operator

e2e_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test e2e_operator

gencheck_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test e2e_operator

gencheck_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test gencheck_operator

test_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test gencheck_operator

test_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test test_operator

e2e_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

test_operator
fbb49ff9a37804cedf6f623206f78c1fcab80e4c
link
/test test_operator

e2e_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test e2e_operator

gencheck_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test e2e_operator

gencheck_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test gencheck_operator

test_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test test_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test e2e_operator

gencheck_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test gencheck_operator

test_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test test_operator

lint_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test lint_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test e2e_operator

test_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test test_operator

lint_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test lint_operator

gencheck_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

replace github.com/spf13/viper to github.com/istio/viper for fixing:
# istio.io/pkg/collateral
../../../pkg/mod/istio.io/pkg@v0.0.0-20191029184635-5c2f5ef63692/collateral/control.go:357:35: v.GetAliases undefined (type *viper.Viper has no field or method GetAliases)

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

test_operator
35190e6c5ed5cf1e4c16e18773a690d9c803a5e7
link
/test test_operator

lint_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test lint_operator

gencheck_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test gencheck_operator

e2e_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test lint_operator

e2e_operator
ee4c027bf10ac1883228c6844bc6b91e767da3d9
link
/test e2e_operator

gencheck_operator
922ecafe16b70d9fe9c580825be91e1d3f7f0c5f
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@carolynhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
5a90d5e72b8bf4293ed9c43c7e1b6c94acfcdfbe
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

remember to cherry-pick this PR to 1.4 branch

In response to a cherrypick label: #475 failed to apply on top of branch "release-1.4":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
Patch failed at 0001 update go mod file


Return OCFL path in response

JIRA Ticket: https://fedora-repository.atlassian.net/browse/FCREPO-3935
Alternative implementation to #2079
Relies on: https://github.com/fcrepo/fcrepo-storage-ocfl/pull/58
What does this Pull Request do?
The OCFL FileDetails object has a getStorageRelativePath() function which returns the full path of the hidden Fedora header file when we read the headers. The related fcrepo-storage-ocfl PR passes this path into the storage layer ResourceHeaders, which are then transferred to the kernel level ResourceHeaders and up to the HTTP layer.
This does not show the storage specific prefix. At this level we only have an objectSession and (I think) we would need the entire repository (io.ocfl.api.OcflRepository) to get the storage (io.ocfl.core.storage.OcflStorage) to get the objectRootPath().
~This method also does not have a way to stop this new information from being loaded. Because of the existing functionality, it requires a second touch of the file which (I imagine) will have some performance impacts.~
Edit: I have re-added the toggle property and have made changes in the fcrepo-storage-ocfl PR that hopefully reduces duplication and (by extension) performance impacts.
I can change the name of the triple, etc. I am not sure if this result is worth the effort so I am putting it here for discussion.
How should this be tested?
Build PRs, run Fedora, create an object, add the fcrepo.ocfl.show_path=true property and see the new fedora:ocflPath triple.
> curl -ufedoraAdmin:fedoraAdmin http://localhost:8080/rest/some-container-2
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix fedora: <http://fedora.info/definitions/v4/repository#> .
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .

<http://localhost:8080/rest/some-container-2>
        dc:title               "Some container" ;
        fedora:created         "2024-08-20T16:13:12.925017Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
        fedora:lastModified    "2024-08-20T16:13:12.925017Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
        fedora:createdBy       "fedoraAdmin" ;
        fedora:lastModifiedBy  "fedoraAdmin" ;
        rdf:type               ldp:BasicContainer ;
        rdf:type               ldp:Resource ;
        rdf:type               fedora:Resource ;
        rdf:type               ldp:RDFSource ;
        rdf:type               ldp:Container ;
        rdf:type               fedora:Container ;
        fedora:ocflPath        "4a4/eea/b39/4a4eeab393a29d541a3d3b8c9c8e2c57ac52d1381b2a37f31dd395b578bea3f2/v1/content/.fcrepo/fcr-root.json" ;
        ldp:contains           <http://localhost:8080/rest/some-container-2/some-binary> .

> curl -ufedoraAdmin:fedoraAdmin http://localhost:8080/rest/some-container-2/some-binary/fcr:metadata
@prefix premis: <http://www.loc.gov/premis/rdf/v1#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix fedora: <http://fedora.info/definitions/v4/repository#> .
@prefix ebucore: <http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#> .
@prefix ldp: <http://www.w3.org/ns/ldp#> .

<http://localhost:8080/rest/some-container-2/some-binary>
        premis:hasSize           "3071787"^^<http://www.w3.org/2001/XMLSchema#long> ;
        ebucore:filename         "Claw-burn.gif" ;
        ebucore:hasMimeType      "image/gif" ;
        premis:hasMessageDigest  <urn:sha-512:c2f2628ad1d962e0dc94f7249bec61d755f1e455a264c25f364b8586368795fc23a39b035dc292863ee4cfad264f15310157e2920a993ad0e3b17eeecf6ae418> ;
        fedora:created           "2024-08-20T16:13:29.619804Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
        fedora:lastModified      "2024-08-20T16:13:29.619804Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> ;
        fedora:createdBy         "fedoraAdmin" ;
        fedora:lastModifiedBy    "fedoraAdmin" ;
        rdf:type                 ldp:NonRDFSource ;
        rdf:type                 ldp:Resource ;
        rdf:type                 fedora:Resource ;
        rdf:type                 fedora:Binary ;
        fedora:ocflPath          "97c/313/b71/97c313b71a3398c06831fbd81bd6d31aff914e40671fec95a7a78c1fcc17d0bf/v1/content/.fcrepo/fcr-root~fcr-desc.json" ;
        fedora:hasFixityService  <http://localhost:8080/rest/some-container-2/some-binary/fcr:fixity> .

Interested parties
Tag (@ mention) interested parties or, if unsure, @fcrepo/committers

After looking at the fcrepo-storage-ocfl PR and this one, some thoughts:

it seems like the main advantage of this approach is that we don't have to duplicate the logic of producing a hash and chopping it up into a path. But on the other hand, that logic is unlikely to change since it would be costly to rearrange the OCFL root. So the chance of drift occurring between the two implementations is very low. So it's mainly encapsulating storage concerns at a more appropriate part of the stack.
It doesn't seem like there would be major performance implications with the implementation in this PR, just the extra step of ocflFileDetails.getStorageRelativePath() and the overhead of passing around the header in all cases, even when the user doesn't want to see it.
As you note, we would only get a relative path from this approach, so it's essentially on par with the other PR in terms of functionality.
I assume we'd still need to do a bit of extra processing in this PR to remove the .fcrepo/fcr-root.json part of the path, but putting that off until we decide if this approach is worth pursuing seems reasonable.
My understanding is that this PR would not result in the storageRelativePath header ever getting written out to the header file, is that correct?

So while part of me dislikes duplicating the path calculation so far up the stack, the fact that this approach doesn't get us the option to create correct absolute paths makes to seem less worthwhile to me. I think either approach would be fine, so if you have a preference at this point I'd support that. But perhaps we should go with the first PR and change it to only support relative paths.

Hey @bbpennel

Yes, we get the actual path which is nice if we ever change it. But I agree that this seems unlikely right now.
I am less concerned once I pulled some of the pieces apart a little more. But I'm also not super confident there wouldn't be an impact.
Agreed
Or we don't remove the .fcrepo/fcr-root.json either. This gives you the version path of files too (I.e. .../content/v2/...) which might be a good thing 🤷
Yeah, it is only added to the readHeaders and loadRootResource dynamically on its way up the chain. I also did not add it for staged headers,  so I believe (but didn't test) that you don't get the path for staged objects.

I have no preference and I agree with your concerns about the path calculations. We could also ask @pwinckles if there is a better way in ocfl-java.
The main benefit of the first PR is if you don't want the path it isn't even calculated. Where this PR passes it up to the resource for all objects. Not sure of that's a problem or not.

@bbpennel @whikloj
What if modify ocfl-java to expose RepositoryConfig so Fedora can get a handle to the OcflStorageLayoutExtension? This would allow you to use OcflStorageLayoutExtension.mapObjectId() to get the path to the object. It would be relative the storage root, and not absolute.
This solution is more in line with the first PR, but avoids making assumptions about what the storage layout actually is (and re-implementing the algorithm).
Let me know if this is something you want to pursue. It's unfortunately a little tricky than I'd like to work into ocfl-java based on how I divided up the modules.

@pwinckles would your suggested plan this be any better than what I attempted with these PRs?
Also, do you see a problem with how I hooked into ocfl-java to get the relative path?

@whikloj I don't like the approach in the first PR because it makes assumptions about the layout that are not guaranteed to be true. I'm more okay with the version in this PR. However, I am a little scared by all of the changes in DefaultOclfObjectSession, which is a delicate class, and have not given them a thorough review.

Or we don't remove the .fcrepo/fcr-root.json either. This gives you the version path of files too (I.e. .../content/v2/...) which might be a good thing

What is the goal here? To provide a binary path or a path to the containing ocfl object? It makes me uneasy when people start poking around in ocfl objects, because, while they are understandable by inspecting the filesystem, it has been my experience that people consistently have faulty mental models of how the object is laid out.

This seems to be working for me in basic testing with local storage and s3

@whikloj @bbpennel Are you sure you want to return paths like:
        fedora:ocflPath          "97c/313/b71/97c313b71a3398c06831fbd81bd6d31aff914e40671fec95a7a78c1fcc17d0bf/v1/content/.fcrepo/fcr-root~fcr-desc.json" ;

Why not just to the object root?
        fedora:ocflPath          "97c/313/b71/97c313b71a3398c06831fbd81bd6d31aff914e40671fec95a7a78c1fcc17d0bf" ;

Pointing inside the object like that makes me uneasy, especially since the path you're giving to internal Fedora files and not to user content.

Hi @pwinckles, you are correct and so we are displaying the path to the object root only. I make the change in FedoraResourceImpl when we set the storage path.
https://github.com/fcrepo/fcrepo/pull/2090/files#diff-efbd5f52986f25ae38372d0ed3e71eee6d63dfae02b1cb0d497b36aa80f5c15aR496-R502

@whikloj Ah, I was going by what was in the PR description.

🤦 good point, I'll edit it.


temporal remedy for #75, dirty fix of performance problem

Now report_call(JET.virtual_process!, (String, String, Module, Symbol, JET.JETInterpreter)) runs in 75 secs ...

Codecov Report

Merging #97 (18d30ad) into master (cd2605f) will increase coverage by 0.51%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #97      +/-   ##
==========================================
+ Coverage   82.25%   82.76%   +0.51%
==========================================
  Files          11       11
  Lines         986      992       +6
==========================================
+ Hits          811      821      +10
+ Misses        175      171       -4

Impacted Files
Coverage Δ

src/print.jl
79.59% <100.00%> (+1.37%)
:arrow_up:

src/reports.jl
88.79% <100.00%> (+1.34%)
:arrow_up:

src/typeinfer.jl
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix offchain created from offchain

This is blocking the update to the network subgraph, which now uses file data sources within file data sources.
This is more easily reviewed commit by commit. The first four commits are strictly refactors.

@lutter thanks for the review! I've addressed it and removed the stray dbg!s I forgot to remove in https://github.com/graphprotocol/graph-node/pull/5083.


Add option to disable simulation

Simulation a dummy takes ~10% of CPU 6 cores/12 threads 3.5 GHz. By default, it will be enabled.

With 9 dummies and disabled simulations still, take too much CPU


proposal: test: indicate when no tests match -run

When using go test -run to filter tests, there's no clear indication when no tests match. The proposal is to change testing and test package to provide and display this information.
Examples:
$ go test -run DontMatchAnything
testing: warning: no tests match regexp: DontMatchAnything      # 1
PASS
?   	_/tmp	[no tests match regexp]                         # 2

$ go test -run DontMatchAnything testing/...
?   	testing	[no tests match regexp]
?   	testing/iotest	[no test files]
?   	testing/quick	[no tests match regexp]

$ go test -run Mutually testing/...       # Test matches in testing/quick
?   	testing	[no tests match regexp]
?   	testing/iotest	[no test files]
ok  	testing/quick	0.004s

In all cases the exit code would remaing 0, as it would be without the proposal.
The testing package would output the line indicated by (1) and the go test, instead of "ok ..." would output "? ..." for the package, like in the line indicated by (2), in the same style as when there are no test files.
While it's possible to use -v and inspect whether tests were ran or not, it's easy to get confused as the output for not matching anything (with verbose) is identical to output of matching without verbose.

/cc @ianlancetaylor @robpike @mpvl @adg

Fine with me.

Note that for benchmarks (when -bench is specified too) sometimes it might not desired to run tests again and again. So maybe no warning when -bench matches or when -run=^$ is specified. But i guess if no existing commonly used benchmark analyses tools get confused by the additional output it will be fine too.

no warning when ... -run=^$ is specified

This sounds good to me.

maybe no warning when -bench matches or when -run=^$ is specified

I like no warning when -bench matches. (I don't usually use ^$; I type something like -run xx which doesn't require quoting.)

I always used go test -run=XXX -bench . to run benchmarks, and I guess
people don't necessarily use -run=^$ to skip the tests.
I propose that the testing package either:

Always show a warning if no test is run, or
Show the warning only when there are no other outputs besides "PASS"
(i.e. when no benchmark is run)

Something like this, where -run=xx does not match any tests:

-run=
-bench=
warning

""
""
""

^$ / xx
""
"no tests match -run regexp xx"

""
.
"N tests will run; use -run=^$ to disable" (suppress if N == 0)

^$ / xx
.
""

?

Is the "N tests will run" warning helpful?
If the tests are quick I often do intend them to run before the  benchmarks (to check that the change I'm benchmarking doesn't introduce a bug).

@cespare it'd be useful to me, I often forget to disable tests when running benchmarks.

I'm also inclined not to add the N tests will run warning. Benchmarks are meaningless if you introduce a bug. It is actually not a bad thing to run the tests. I often disable them myself this way and have been bitten by this.

I'm waiting on a review from @rsc related to this code. I can implement this as soon as that is in.

Isn't the warning message reassuring if you intend to run the tests?

To me the message is too much of a suggestion to the user that running benchmarks without running tests first is a good thing. If the user can bear running the tests it is better to do so.

I didn't put much thought into the text I suggested ("N tests will run; use -run=^$ to disable"). It could just as easily be "running N tests" which has no suggestive qualities to it at all.

The initial proposal, to treat no tests matching as equivalent to having no test files, sounds good to me. I don't think there's any need to print the number of tests.

Thanks for the feedback.
My plan is to extend the idea to cover together benchmarks, tests and examples. If testing can't find anything to run, it outputs a warning message and changes the summary line to "? package [no matches]".
The illustrated cases in original proposal description remain the same. In cases where there are benchmarks to run, the warning or the ? will not appear.
@mpvl thanks for volunteering but I already wrote a proof-of-concept and intend to make into a proper change. However, could I count on you to review it once done? :-)

Sure, I can review it. But would be good for CL 19122 to be in first.
Note that returning the count is also problematic, as it is not possible to know how many subtests will be run in advance.

@mpvl could you take a look at https://go-review.googlesource.com/#/c/22341/?
I think it was done in a way that doesn't conflict with subtest matching. I've taken into account the fact that we can't know how many subtests will run in advance.

@mpvl ping :)


Notifications - Redo UI and Modal

A user remarked that the scrollbar for notifications can be easily overlooked.  Especially if the underlying featured app has a white/gray color scheme.

Haven't seen this often but definitely agree that it isn't ideal. Changing the color scheme for just that scrollbar (esp with browser differences) could be a nightmare though. Best option if we want to go that route would probably be a plugin.
Do we really need a scrollbar? Maybe there isn't a max height on that for now? Or overflow "See more" could be put into a Notification modal where they can manage all notifications? Not sure how many notifications people are getting, how long they are staying, or what's realistic. Would be a good topic for more discussion.

Couple ideas for implementation after sprint discussion: @tonyalletag
Rework the notification dropdown to allow more real estate for displaying longer text fields. Also remove the max-height/scrollbar and direct to a Notification modal to see more:

Create a notification modal to display more notifications as well as complete text. Also allow for a "more information" button link (or just allow  tags within the notification text).

@bhalt Both of these are good options.
I could see either of these working. I will ask our content stewards to provide feedback.

Tony, Bethany -- either works for me! My main interest is having more notification space to provide more description. Thanks for addressing this!

@tonyalletag these were actually designed to work in tangent. Still not sure I have all the use cases, but if we foresee users having more notifications than can be seen on the initial dropdown, I'd suggest having a notification modal as the command center to look through all of them.

First addressed in #457

Can you outline what the filters are other than Date? I understand the rest

Hmm. Would be neat to have an "importance" filter (AML platform notifications, then Org notifications, then app notifications by date). If that's too hard of an algorithm we can just show the Filter now, remove the Sort, and just default sort by date. @wski

Sounds good, will investigate importance

I've gone ahead and put the sorting on the back burner for now, I think we should do that when peer 2 peer notifications and app notifications are implemented, but not right now.

What is "more information" supposed to show?

@wski the plan was to expand the notification data to allow for more text (very limited number of characters now) and the option of adding links (buttons), viewed from the modal

The notifications now expand and when user chooses "See more" a notification modal displays with all of the notifications to choose from.

Thanks Tiff....and the hyperlinking is appreciated as well!
On Mon, May 9, 2016 at 3:49 PM, Tiff<EMAIL_ADDRESS>wrote:

The notifications now expand and when user chooses "See more" a
notification modal displays with all of the notifications to choose from.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ozone-development/ozp-center/issues/535#issuecomment-217969384

Passed on staging.


add request limiter when polling for results

Related to b/372751875
I'm still trying to replicate QuotaException error (not able to do so atm), but I'm able to verify that the new solution does not stall and works well with run_batch.

This is still in a draft state, as I verify the solution

@wcourtney PTAL


No output in jupyter notebook -suddenly

Using python 3.6 on Linux with

holoviews 1.13.2
hvplot 0.5.2
bokeh 2.0.2
IPython 7.1.1

When I do something simple like:
df.hvplot(kind="scatter")

A red "Out[nn]"  is shown and nothing else. This frequently happens in notebooks where the same plot showed fine earlier. At some point it stopped working.
Under my imports:
import holoviews as hv
hv.extension("bokeh")
import hvplot
import hvplot.pandas

The following messages are shown:
Javascript error adding output!
TypeError: Bokeh.set_log_level is not a function
See your browser Javascript console for more details

On the Chrome javascript console there are many warnings and the following errors:
Uncaught TypeError: Cannot read property 'embed_items_notebook' of undefined
    at embed_document (<anonymous>:5:20)
    at <anonymous>:8:5
    at <anonymous>:24:3
    at eval (eval at append_javascript (outputarea.js:763), <anonymous>:97:28)
    at Array.forEach (<anonymous>)
    at window._Events.handle_add_output (eval at append_javascript (outputarea.js:763), <anonymous>:86:13)
    at window._Events.dispatch (jquery.min.js:5237)
    at window._Events.elemData.handle (jquery.min.js:5044)
    at Object.trigger (jquery.min.js:8471)
    at window._Events.<anonymous> (jquery.min.js:8549)
events.js:33 Exception in event handler for output_added.OutputArea TypeError: Cannot use 'in' operator to search for '1754' in undefined
    at window._Events.handle_add_output (eval at append_javascript (outputarea.js:763), <anonymous>:103:45)
    at window._Events.dispatch (jquery.min.js:5237)
    at window._Events.elemData.handle (jquery.min.js:5044)
    at Object.trigger (jquery.min.js:8471)
    at window._Events.<anonymous> (jquery.min.js:8549)
    at Function.each (jquery.min.js:367)
    at jQuery.fn.init.each (jquery.min.js:202)
    at jQuery.fn.init.trigger (jquery.min.js:8548)
    at jQuery.fn.init.events.trigger (events.js:31)
    at OutputArea.append_output (outputarea.js:355) Arguments(2)

In the Firefox console I see the following errors:
Comm promise not found for comm id hv-extension-comm comm.js:127
    comm_msg comm.js:127
    proxy jQuery
    _handle_iopub_message kernel.js:1224
    _finish_ws_message kernel.js:1016
    _msg_queue kernel.js:1007
TypeError: root.Bokeh.embed is undefinedplotting-libs.ipynb line 97 > scriptElement:5:3
    embed_document plotting-libs.ipynb line 97 > scriptElement:5
    <anonymous> plotting-libs.ipynb line 97 > scriptElement:8
    <anonymous> plotting-libs.ipynb line 97 > scriptElement:24
    handle_add_output main.min.js:97
    forEach self-hosted:225
    handle_add_output main.min.js:86
    jQuery 7
    trigger events.js:31
    append_output outputarea.js:355
    fromJSON outputarea.js:1046
    fromJSON codecell.js:564
    fromJSON notebook.js:2660
    load_notebook_success notebook.js:3146
    proxy jQuery
Exception in event handler for output_added.OutputArea TypeError: "right-hand side of 'in' should be an object, got undefined"
    handle_add_output main.min.js:103
    jQuery 7
    trigger events.js:31
    append_output outputarea.js:355
    fromJSON outputarea.js:1046
    fromJSON codecell.js:564
    fromJSON notebook.js:2660
    load_notebook_success notebook.js:3146
    proxy jQuery

What I find frustrating is that the same notebook worked fine a bit earlier and there is nothing
obvious that has been changed to explain why it suddenly does not work and no helpful error message as to what might be going wrong.

When I create a completely new notebook (in the same Firefox browser) and copy over the same cells I used in the original notebook where things stopped to work, everything works fine: the error messages under the cell with the imports are not shown, and no error messages appear on the Javascript console and the graph is shown correctly.
Going back to the original notebook with exactly the same cells and running those cells produces the same errors again. Even after restarting the Kernel.
It feels like something "broke"  the notbook itself and changed it so that things do not work properly and there seems to be no way to reset things to the state when it still did work.

OK some more research shows that the presence of other cells in the notebook, even though those cells do not get executed after jupyter notebook or the kernel gets restarted, seems to cause this.
I created a copy and removed all the other cells and then, after restarting the notebook, things work.
The notebook compares a number of Python plotting libs and contains graphs from matplotlib, seaborn, plotly and pygal.
However just using the Jupyter notebook command to clear all the outputs, then restarting the kernel and reloading the notebook page in the browser still does not change anything: the hvplot method still does not show anything in that notebook.

OK, one more attempt: turns out that clearing the output with the shortcut from within the notebook does not seem to remove it from the actual notebook file.
Tried to clean the output by creating a copy like so:
jupyter nbconvert original.ipynb --to notebook --ClearOutputPreprocessor.enabled=True --stdout > cleaned.ipynb

Running the cells in the cleaned.ipynb with a new kernel still does not make it work.

Thanks for the detailed writeup here. Do you, by any chance, still have a copy of the notebook in its broken state?

This is a (gzip-compressed, github does not allow .ipynb extension) notebook where running the cells marked with # RUN 1 and # RUN 2 (at the beginning) followed by # RUN 3 and # Run 4 (close to the end) does not work for me on two different computers.
plotting-libs.ipynb.gz

@philippjfr  did the notebook allow you to replicate the problem?

Sorry I've been totally swamped, hoping to get to it later in the week.

I had the same issue with my own notebook browser independent.
I am using python 3.7 on Windows 10 with

holoviews 1.13.3
hvplot 0.6.0
bokeh 2.1.1
IPython 7.16.1.

I discovered my notebook was working again if I changed markdown cells with Bokeh as text/headline, e.g. "## Bokeh" or "### Bokeh". Error occurs if the Bokeh-Markdown-cell exist at any position in the notebook (before/after import or plot).
As soon as you change all cells with "# Bokeh" to something like "# aBokeh" you shouldn't have the error anymore.
I tested this workaround successfully with my own and with @johann-petrak 's notebook.

OK, this is beyond weird: when I open my notebook, first change the Markdown cell to not contain "# Bokeh" as suggested by @SarahOst , then run the cells marked with "RUN 1" to "RUN 4" the plot indeed gets shown.

I can even specify a tiny bit more:

even if you run the notebook with the failure causing "# Bokeh" you can still change the markdown cell and rerun code cells and they will work now (so, there it is not necessarily to change it first to make the notebook work again)

failure occurs only with the capital version "# Bokeh" and not with "# bokeh"

ref https://github.com/bokeh/bokeh/issues/10002#issuecomment-654810980

Oh wow thanks @mattpap. That's truly awful! 😢

The PR @mattpap references above has now been merged so hopefully this will be fixed in the next bokeh release.

Having this issue now suddenly.
bokeh==3.2.2
holoviews==1.17.1
hvplot==0.8.4
jupyterlab==3.6.3
jupyterlab-pygments==0.2.2
jupyterlab-unfold==0.2.2
jupyterlab_server==2.24.0
panel==1.2.1
param==1.13.0
Python 3.10.12
Actually first, what was happening was that axis were displayed, but no line charts or heatmaps could be displayed. Area charts still plotted. I then updated libraries:
• Updating bokeh (3.2.1 -> 3.2.2)
• Updating holoviews (1.17.0 -> 1.17.1)
And now I'm not getting any output at all in jupyter, not even blank axis.

Actually first, what was happening was that axis were displayed, but no line charts or heatmaps could be displayed

This was related to the Bokeh webgl renderer breaking in certain cases, which should have been fixed by bokeh 3.2.2. Do you see any errors on your JS console?