Request for RSNA Detection Dataset Split File

Dear authors,
Thank you for making this valuable project publicly available. I appreciate the contributions you’ve made to the community!
I was wondering if it would be possible for you to release the dataset split files rsna-pneumonia-detection-challenge/maco_splits/train_maco_full.npy and others used in the RSNA detection task? Otherwise, if you could provide the code to recreate the splits from the original csv files or the format details about the npy file, that would be equally helpful.
Thank you for your time and consideration. Looking forward to your response!

Hello Could you please provide me with the requirements.txt that you have configured for this project? I am having a lot of trouble with the author's one. Thank you very much for your reply.

Here is the pip requirement exported from my conda environment. I'm not sure if it will be helpful in your case, as some packages were installed locally. Nonetheless, I hope it can serve as a reference.
absl-py==2.1.0
aiohttp==3.8.6
aiosignal==1.3.1
anyio==3.7.1
apex==0.1
arrow==1.2.3
astroid==2.4.2
async-timeout==4.0.3
asynctest==0.13.0
attrs==24.2.0
beautifulsoup4==4.12.3
blessed==1.20.0
boto3==1.33.13
botocore==1.33.13
brotlipy==0.7.0
cachetools==4.2.4
cffi==1.15.0
charset-normalizer==2.0.4
click==8.1.7
contextlib2==21.6.0
croniter==1.3.15
cryptography==39.0.1
cycler==0.11.0
dateutils==0.6.12
deepdiff==6.7.1
einops==0.6.1
exceptiongroup==1.2.2
fastapi==0.88.0
filelock==3.12.2
fonttools==4.38.0
frozenlist==1.3.3
fsspec==2023.1.0
fvcore==0.1.5.post20221221
google-auth==1.35.0
google-auth-oauthlib==0.4.6
grad-cam==1.4.8
grpcio==1.62.3
h11==0.14.0
huggingface-hub==0.16.4
idna==3.4
imageio==2.31.2
importlib-metadata==6.7.0
inquirer==2.10.1
iopath==0.1.10
isort==5.6.4
itsdangerous==2.1.2
Jinja2==3.1.4
jmespath==1.0.1
joblib==1.3.2
kiwisolver==1.4.5
lazy-object-proxy==1.4.3
lightning==1.9.5
lightning-cloud==0.5.70
lightning-utilities==0.10.1
Markdown==3.4.4
markdown-it-py==2.2.0
MarkupSafe==2.1.5
matplotlib==3.5.3
mccabe==0.6.1
mdurl==0.1.2
mkl-fft==1.2.0
mkl-random==1.1.1
mkl-service==2.3.0
ml-collections==0.1.1
multidict==6.0.5
networkx==2.6.3
numpy=1.19.2
oauthlib==3.2.2
olefile==0.46
opencv-python==<IP_ADDRESS>
ordered-set==4.1.0
packaging==24.0
pandas==1.3.5
Pillow==9.5.0
portalocker==2.7.0
protobuf==3.20.3
psutil==6.0.0
pyasn1==0.5.1
pyasn1-modules==0.3.0
pycocotools==2.0.7
pycparser==2.21
pydantic==1.10.18
pydicom==2.4.4
Pygments==2.17.2
PyJWT==2.8.0
pylint==2.6.0
pyOpenSSL==23.0.0
pyparsing==3.1.4
PySocks==1.7.1
python-dateutil==2.9.0.post0
python-editor==1.0.4
python-multipart==0.0.8
pytorch-lightning==1.9.5
pytz==2024.2
PyWavelets==1.3.0
PyYAML==6.0.1
readchar==4.0.5
regex==2024.4.16
requests==2.28.1
requests-oauthlib==2.0.0
rich==13.8.1
rsa==4.9
s3transfer==0.8.2
sacremoses==0.0.53
safetensors==0.4.5
scikit-image==0.19.3
scikit-learn==1.0.2
scipy==1.7.3
SimpleITK==2.3.0
six==1.15.0
sniffio==1.3.1
soupsieve==2.4.1
starlette==0.22.0
starsessions==1.3.0
tabulate==0.9.0
tensorboard==2.11.2
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.8.1
termcolor==2.3.0
threadpoolctl==3.1.0
tifffile==2021.11.2
timm==0.9.12
tokenizers==0.12.1
toml==0.10.1
torch==1.11.0
torchaudio==0.11.0
torchmetrics==0.11.4
torchvision==0.12.0
tqdm==4.66.5
traitlets==5.9.0
transformers==4.26.1
ttach==0.0.3
typed-ast==1.4.1
typing_extensions==4.7.1
urllib3==1.26.14
uvicorn==0.22.0
wcwidth==0.2.13
websocket-client==1.6.1
websockets==11.0.3
Werkzeug==2.2.3
wrapt==1.11.2
yacs==0.1.8
yarl==1.9.4
zipp==3.15.0

okk. Thanks a lot.!!

Dear authors,
Thank you for making this valuable project publicly available. I appreciate the contributions you’ve made to the community!
I was wondering if it would be possible for you to release the dataset split files rsna-pneumonia-detection-challenge/maco_splits/train_maco_full.npy and others used in the RSNA detection task? Otherwise, if you could provide the code to recreate the splits from the original csv files or the format details about the npy file, that would be equally helpful.
Thank you for your time and consideration. Looking forward to your response!

您好 请问您目前有结果了嘛 如果有的话 能否麻烦分享一下~谢谢啦


Make Logger.Metadata.Key strongly typed

Make Logger.Metadata.Key strongly typed by using a separate struct.
Motivation:
Using String as keys makes it hard to use constants for metadata keys. They have to be defined in some arbitrary namespace. Or if they don't, they're messy to change and even harder to "look up" (e.g. what keys exist on that logger? what key stores what information) since there is no central definition place.
enum SomeMetadataKeyNamespace {
    static let myMetadataKey = "awesome-key"
}

var logger = Logger(label: "some.great.logger")
logger[metadataKey: SomeMetadataKeyNamespace. myMetadataKey] = "what a beautiful value"

// Later on in e.g. a different file (a `LogHandler` implementation for example)
if case .string(let str)? = logger[metadataKey: SomeMetadataKeyNamespace. myMetadataKey], str.contains("beautiful") {
    print("It's beautiful!")
} else {
    print("Not beautiful...")
}

Modifications:

Add Logger.MetadataKey and change the typealias for Logger.Metadata to use Logger.MetadataKey as key instead of String.
Change the protocol requirement in LogHandler to take Logger.Metadata.Key instead of String in subscript(metadataKey:).
Logger.MetadataKey conforms to:

RawRepresentable (RawValue = String)
Hashable
CustomStringConvertible (description being rawValue)
ExpressibleByStringLiteral (StringLiteralType = String)
ExpressibleByStringInterpolation (StringInterpolation = DefaultStringInterpolation)

Result:
Using a separate struct for Logger.Metadata.Key allows static constants on it making metadata "nicer" to use:
extension Logger.Metadata.Key {
     static let myMetadataKey = Logger.Metadata.Key(rawValue: "awesome-key")
}

var logger = Logger(label: "some.great.logger")
logger[metadataKey: .myMetadataKey] = "what a beautiful value"

// Later on in e.g. a different file (a `LogHandler` implementation for example)
if case .string(let str)? = logger[metadataKey: .myMetadataKey], str.contains("beautiful") {
    print("It's beautiful!")
} else {
    print("Not beautiful...")
}

Source Compatibility
I'm not sure this change can be made in a source compatible way - especially since the subscript(metadataKey:) was directly requiring String instead of Logger.Metadata.Key. Most implementations would probably be fine with the deprecated overload I added (similar than what has been done for source - although I've read that this wasn't perfect either). But those implementations that use String APIs will definitively break. Thus this will likely need a new major version - in which case I could remove the "attempted backwards compatibility" 🙂

I'm going to close this as we're working on proposing baggage (from tracing) integration into swift-log, we'll share a proposal soon.

@ktoso I'm sorry that I haven't found time to take another look at this. And thanks for taking this on!

No worries at all, we'll get to a comprehensive solution soon 👍


Invoking "make -j4 -l4" failed

I am trying to build the project on Ubuntu 16.04 with ROS Kinetic and I get the following error:
Scanning dependencies of target std_msgs_generate_messages_eus
[  9%] Built target std_msgs_generate_messages_eus
Scanning dependencies of target geometry_msgs_generate_messages_lisp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
annotation_tool_kth/annotation-tool/src/CMakeFiles/annotation_tool.dir/build.make:82: recipe for target 'annotation_tool_kth/annotation-tool/src/moc_objectsinformation.cxx' failed
make[2]: *** [annotation_tool_kth/annotation-tool/src/moc_objectsinformation.cxx] Error 1
make[2]: *** Waiting for unfinished jobs....
[  9%] Built target geometry_msgs_generate_messages_lisp
Scanning dependencies of target std_msgs_generate_messages_lisp
Scanning dependencies of target sensor_msgs_generate_messages_cpp
[  9%] Built target std_msgs_generate_messages_lisp
[  9%] Built target sensor_msgs_generate_messages_cpp
Scanning dependencies of target sensor_msgs_generate_messages_eus
Scanning dependencies of target sensor_msgs_generate_messages_lisp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
annotation_tool_kth/annotation-tool/src/CMakeFiles/annotation_tool.dir/build.make:62: recipe for target 'annotation_tool_kth/annotation-tool/src/moc_mainwindow.cxx' failed
make[2]: *** [annotation_tool_kth/annotation-tool/src/moc_mainwindow.cxx] Error 1
[  9%] Built target sensor_msgs_generate_messages_eus
[  9%] Built target sensor_msgs_generate_messages_lisp
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
annotation_tool_kth/annotation-tool/src/CMakeFiles/annotation_tool.dir/build.make:72: recipe for target 'annotation_tool_kth/annotation-tool/src/moc_viewerinteractor.cxx' failed
make[2]: *** [annotation_tool_kth/annotation-tool/src/moc_viewerinteractor.cxx] Error 1
CMakeFiles/Makefile2:1255: recipe for target 'annotation_tool_kth/annotation-tool/src/CMakeFiles/annotation_tool.dir/all' failed
make[1]: *** [annotation_tool_kth/annotation-tool/src/CMakeFiles/annotation_tool.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[  9%] Built target nav_msgs_generate_messages_py
[  9%] Built target nav_msgs_generate_messages_eus
[  9%] Built target map_msgs_generate_messages_py
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j4 -l4" failed

@ldepn were you able to solve this error?
I am also working on Ubuntu 16.04 with ROS Kinetic and facing a similar error:
~/annotation_tool_kth-master/annotation-tool/build$ make
[  2%] Generating ui_addobjectdialog.h
[  5%] Generating moc_mainwindow.cxx
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
src/CMakeFiles/annotation_tool.dir/build.make:62: recipe for target 'src/moc_mainwindow.cxx' failed
make[2]: *** [src/moc_mainwindow.cxx] Error 1
CMakeFiles/Makefile2:1212: recipe for target 'src/CMakeFiles/annotation_tool.dir/all' failed
make[1]: *** [src/CMakeFiles/annotation_tool.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

@N-G17 sorry, i have give up this code!

@ldepn did you find any other source to annotate a pcd file for 3D bounding box of an object?

@N-G17 https://github.com/yzrobot/cloud_annotation_tool.git
I haven't used it yet. You can try it.


Does not support adding partial views

There is no support for adding partial views from a mustache template.
Steps to reproduce:

Create a .mustache view
create a .mustache partialview
link to a partial view {{>_list}}

Hi Phillip. There's also a comment in the code about adding this. I'll see if I can get to it (with caching) this week.

Just added this. It doesn't show an error message yet for missing views, but I'll see about adding that later.

Cool. Thanks for the hard work!

Looks good after an initial look at the code. The only issue I see is if a user adds a partial view in this sequece.

Create a Razor template
add mustache partial to razor template
add mustache partial to above mustache partial

This may be an edge case, and really isn't important to me, so I can see leaving it out.

Ooh, you were right. Just pushed a test and the fix for it.

thanks!


RFC: Rename default branch from "master" to "main"

The new standard for Git and platforms like GitHub and GitLab is using main instead of master for the default branch:
https://sfconservancy.org/news/2020/jun/23/gitbranchname/
https://github.com/github/renaming
https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/#default-branch-name-for-new-repositories-now-main
I'd like to change the tesseract-ocr repositories to that new standard and rename the master branch.
This requires updates for existing locally cloned repositories, too (unless they are removed and a new clone is made). Nevertheless I think we should use the standard naming, and switching now is better than switching later.

The name change also requires updates of the documentation. It is possible to have both master and main branches for some time (for example until end of 2021) with mainbeing the default branch and master no longer updated. That would make the change smoother, for example avoid breaking links in the documentation.

:+1:

The name change also requires updates of the documentation. It is possible to have both master and main branches for some time (for example until end of 2021) with mainbeing the default branch and master no longer updated. That would make the change smoother, for example avoid breaking links in the documentation.

I don't think it is necessary to keep the old name.
https://github.blog/changelog/2020-07-17-links-to-deleted-branches-now-redirect-to-the-default-branch/
https://github.com/github/renaming#renaming-existing-branches
I suggest to to rename the branch  from the web interface.

Question: When should we do it?

This week.
Right before the final release of 5.0.0.
Right after the final release of 5.0.0.

if to do it, then ASAP, so it relevant docs/links could be adapter before release 5.0.0.

Yes, I think it should be done before the next tagging.

I tested the rename process for https://github.com/tesseract-ocr/docs. That repository also has GitHub pages https://tesseract-ocr.github.io/docs/. Those have to be activated again after the rename.

Now I changed https://github.com/tesseract-ocr/langdata, too. The existing pull requests are updated automatically.

All tesseract-ocr repsitories now use main as the default branch.
Still open:

Watch continuous integration whether it still works
Update more content and links to use "main" instead of "master"

@stweil That's less than 24 hours between raising the issue and enforcing the new rule. Were you interested at all in any actual discussion around this? (You already had my arguments against this.)

I cite my statement from that discussion (August 2020):

This is the wrong place to discuss the motivation behind that change. And GitHub suggests to postpone it, so we can wait and decide later this year.

The first sentence still applies. We are now a year later. GitHub no longer suggests to postpone the change. Meanwhile main is the new standard. For people who start learning Git and for new repositories that's the norm. Many other Open Source projects already switched to main. So for more and more people using the old name will become increasingly strange.

The first sentence still applies

What a nice way of saying you (still) don't care about the arguments. Where else would you have the discussion then? Just because a company (like Github or SF Conservancy) puts up a certain directive, why should we feel bound by that?

Meanwhile main is the new standard.

For new projects, indeed.

So for more and more people using the old name will become increasingly strange.

I very much doubt that.
First, there are way more things newcomers (to any project) need to get used to than just the branch names. (While for current contributors and dependent projects, it means extra work in adapting their workflows and deployments.)
Second, as you know, Open Source has a long tail – most projects have but one or two committers with only sporadic activity. These will unlikely waste their precious time with such cosmetics. But even if everyone abides by corporate terminology: you cannot just disappear that decades long convention, respected by existing documentation, tutorials, FAQs, books.

Just thought I'd chime in that this change broke the tesseract-git package for Arch Linux. https://aur.archlinux.org/packages/tesseract-git/#news It's not a huge deal or anything, the maintainer just needs to replace master with HEAD and I can edit the PKGBUILD manually to the fix the build myself in the meantime. Arguably it should have been written that way to begin with as a best practice, but the reality of the matter is that for better or for worse lots of existing tooling in the wild does assume that the default branch is master and changing the default branch of existing repositories will break things for people.
To be clear, I'm not demanding the change be undone or anything. Tesseract is wonderful project that I'm very happy to be able to use for free and it's not my place to tell its developers what source control conventions to follow. I just feel that it needs to be pointed out that the cost of this change, however small, is non-zero. Especially when multiplied by the enormous number of projects making such transitions.

Next time we should give more time for feedback about a change with a big impact on our users.
Nevertheless, I still think it's a good change.

Maybe we can re-introduce the master branch. It won't be the default but will always follow main. Does anyone know how to this automatically ?

GitHub already provides backward compatibility, so it is still possible to access master and get redirected to main.

GitHub already provides backward compatibility, so it is still possible to access master and get redirected to main.

Github may do that on their web server, but there is no backwards compatibility on git or http CLI access. That's what will break existing workflows and deployments.

Maybe we can re-introduce the master branch. It won't be the default but will always follow main.

I had suggested that in my initial proposal. Adding an additional branch named master is easy, and synchronisation with main could be done automatically.
Nevertheless I think that we should wait and see whether we really need that (and for which of the tesseract-ocr repositories). The change was done for the default branch which is normally used by people doing development. I am sure they can handle the necessary adjustments - if any are required at all.

the maintainer just needs to replace master with HEAD

We have annotated tags. https://wiki.archlinux.org/title/VCS_package_guidelines#Git suggests better code for that. And that code does not refer to master, main oder HEAD.

Maybe we can re-introduce the master branch. It won't be the default but will always follow main.

I had suggested that in my initial proposal. Adding an additional branch named master is easy, and synchronisation with main could be done automatically.
Nevertheless I think that we should wait and see whether we really need that (and for which of the tesseract-ocr repositories). The change was done for the default branch which is normally used by people doing development. I am sure they can handle the necessary adjustments - if any are required at all.

I find this "let it fail" approach really unfair and unjust, both to external dependent projects and to contributors. It's not hard to imagine what will go wrong without at least a grace period or advance notification.
Example of new CI failures of dependent packages due to rename:
--2021-09-14 06:18:08--  https://github.com/tesseract-ocr/tessdata/raw/master/osd.traineddata
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-09-14 06:18:08 ERROR 404: Not Found.

Please add the aliases ASAP!

I re-introduced the master branch for backward compatibility. main is still the default branch. I only did it for this repo.

@stweil commented 3 days ago

It is possible to have both master and main branches for some time (for example until end of 2021) with mainbeing the default branch and master no longer updated.

Did you mean that master will be frozen in its current state or at 5.0.0 final release or at EOY?
@amitdo commented 19 hours ago

Maybe we can re-introduce the master branch. It won't be the default but will always follow main.

I added my emphasis for the quotes.

GitHub already provides backward compatibility, so it is still possible to access master and get redirected to main.

This change is maddening... You assume this only exists on Github.    Do you seriously not think something like tesseract is not used outside Github by other projects?  WIth their own CI?  And why on Earth was it done so fast?

Please add the aliases ASAP!

Up to now all reported problems in other projects which use Tesseract repositories were caused because something was wrong in those other projects.
So the switch from master to main had the surprising and for me unexpected side effect of uncovering bugs in other projects.
The main problem is that no project which expects to produce reproducable results must depend on the latest development release of another project because that other project can change (or even break) at any time. Instead it should use well defined releases of other projects (either tagged or identified by their git revision).

And why on Earth was it done so fast?

We want to make 5.0.0 soon. And delaying the name switch would not solve any of the problems.

I re-introduced the master branch for backward compatibility. main is still the default branch. I only did it for this repo.

Please don't do it for more repositories. Fixing dependent projects is not difficult and has to be done anyway (see my previous comment).
I don't think we need that additional master branch and would like to get rid of it again soon, for example when the final 5.0.0 is released. Would that be acceptable?

Example of new CI failures of dependent packages due to rename

That's a bug in OCR-D/ocrd_all (it should have used tagged releases) which is fixed with https://github.com/OCR-D/ocrd_all/pull/275.

Please don't do it for more repositories.

I didn't have any intention to so. Actually, I only have write perm mission for this repo.

I am sorry for inconvenience and problems with this change. here few of my thoughts on this:

Regardless politics behind this change – “git main” is new standard. I already have repos with “main” branch and it is quiet annoying to try what it right: main or master. So for actively used repos renaming to main is common sense for me.
This change needed to be done before releasing version 5. New release will draw attentions and doing change after main release would cause more problems IMO. That is why I was/am for making this change ASAP/ fast, so we can fix issues on our side soon. We are still in beta phase so significant changes are ok for me.
If somebody uses master/main (without tags) in outside project, there could be only one reasonable explanation for it – to get notified about changes and breaks. Otherwise there is just made wrong setup on their side and they need to fix it. There is no reason why to complain here about broken external project because of changes in not released code.  It is NORMAL to expect that code in master/main is broken or not working as expected.
In the light of point 2. and 3. creating “master” copy/alias for main repository is WRONG decision IMO. This will hide change - many people will not recognize change and pain of change will last longer. Temporary solutions often become permanent problems.

No, that was tesserocr.

Tesserocr ist fixed now: https://github.com/sirfz/tesserocr/commit/fa34eaf853d0802bb1555d46298ef2ee6ede389b.

Okay, you can undo my 'fix'.

amitdo: I do not want to make significant changes each hour. I just send a message to user and devel forums, so users have some time to react.  So let's give them one week or two ;-)
I believe everybody tries to do their best for this project. As a takeaway:  for an important change like this I suggest waiting some time (7 days), so relevant people can react or we can prepare some time schedule, inform people that do not follow the issue tracker.


Convert School Name text field into dropdown

Resolve: #64
Converted the text field version of school name to a dropdown with preset names.

looks good & functional so far, is there any way we can allow users to type to search v. scroll to search for their schools? it seems that typing while dropdown is open works as well but not for continuous strings

Not that I'm aware of at least not with headlessui. The headlessui api says that keyboard input a-z will "Focuses first item that matches keyboard input"

checked again, input texts look good feel free to merge!


pretraining details

Great work!
I'd like to learn more about the details of the pretraining process mentioned: "During the pretraining process, all modalities gradually align with the language modality through contrastive learning."
Could you clarify if this pretraining process is equivalent to LoRA fine-tuning? In other words, during the pretraining phase, are parameters updated for the video encoder, infrared encoder, depth encoder, and audio encoder using the four types of data contained in VIDAL-10M, namely, video-language data, infrared-language data, depth-language data, and audio-language data, through contrastive learning?

Thanks fou your attention and you are ⭐right.


Support monitoring AWS Cloud EKS

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Related issue https://github.com/apache/skywalking/issues/9883

UI repo has synced
I copied otlp  proto to java-test-service for mocking EKS e2e test

UI screenshot

Node metrics

Service metrics

@pg-yang Let's fix the left issues and merge this :)


https://developer.mozilla.org/ko/docs/XMLHttpRequest

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
The doc's URL is of old format. Please move it under /ko/docs/Web/API. (/ko/docs/Web/API/XMLHttpRequest)

Done. Thanks for reporting!


Add CI for windows, macos and linux, for multiple python versions

Also, some tests are improved to work better on Windows, and scipy was missing from the environment.yml.
This was a really hard one!!

As you can see by the time the tests take, this doesn't slow down the checking step because all checks are run concurrently.

By the way, it looks like one test doesn't pass, but it's because I've replaced the build action, so the GitHub falsely expects a message from the old build as well.

Hi Erik,
thanks for adding scipy to environment.yml! Since you are working on it, maybe it would make sense to also eliminate the invalid escapes (e.g. here). They occur as warnings for all actions. I think the badness level is not too high, but it would remove some lengthy warnings from the logs.

Well done!!

Hi Erik,
thanks for adding scipy to environment.yml! Since you are working on it, maybe it would make sense to also eliminate the invalid escapes (e.g. here). They occur as warnings for all actions. I think the badness level is not too high, but it would remove some lengthy warnings from the logs.

Good point, @jlandmann! I'll add an issue for it. There are quite many small fixes like that, so they would be good to squash in a PR.


rewrite rule for golang.org/x/net/http2

Add rewrite rule for golang.org/x/net/http2 to fix vulnerability fixed on version 0.23.0.

Hi @MovieStoreGuy, do you think this could be merged? Is just bumping a dependency that Snyk is marking having a vulnerability:
✗ High severity vulnerability found in golang.org/x/net/http2
Description: Allocation of Resources Without Limits or Throttling
Info: https://security.snyk.io/vuln/SNYK-GOLANG-GOLANGORGXNETHTTP2-6531285
Introduced through<EMAIL_ADDRESS>From<EMAIL_ADDRESS>Fixed in: 0.23.0

Hey @alvarocabanas ,
Of course it can, I am just not great with github notifications. I'll need you to fix up the conflicts and this can be merged.

Hey @alvarocabanas ,
Of course it can, I am just not great with github notifications. I'll need you to fix up the conflicts and this can be merged.

Thanks @MovieStoreGuy, I have just rebased my branch and fixed the conflicts and is ready to be merged.

I will leave this for dependabot to address.


🚀 [Feature] iOS: BBB only supports Safari browser

🚀 Feature
For mobile iOS devices BBB doesnot support other browsers than the native Safari.
If using another browser toenter a BBB meeting results in this hint and not being ableto actually use the BBB meeting.
We should inform the DreamMall users to use Safari on, if on a iOS device (=>Marketing)

I think this can be closed, since it is not relevant for development. We cannot change this behaviour. It only applies to the fruit computers mobile OS.


Document automatic registration of observers

Hi,
Thanks for providing support for the Observer Design Pattern in Rails via rails-observers, helping us better manage our Rails codebases.
I added instructions for automatically registering observers via naming convention or assumed directory to help easily add observers by convention instead of configuration.
Best regards,
Andy

Thanks for the PR! I'd prefer to just keep it to the manual registration that the guide already recommends 😊


Signature verification failed

Finding this entry in the iCue log and the plugin never connects to Openrgb 0.6.
"2021-06-16 17:48:13.126 W cue.plugin.host: Signature verification failed: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/OpenRGB/CUEORGBPlugin.dll"
I've tried changing the port in Openrgb and the settings.json for the plugin but no difference, always get the error above and it doesn't connect.
OpenRGB 0.6
iCue v. 4.12.214
TIA

iCUE updated their plugin loading code so the signature no longer works, I've changed the dsound wrapper to be more robust by just bypassing the core function they use to verify plugins.

Working again, thank you!


down work :/

/api/user/revunix/2factor Not Found
You seem to have stumbled upon a page that does not exist. Return to the home page.

i don't know hmm ;/

Please wait for v0.7.2 of NodeBB, or utilise the master branch.

Okay. Thanks!!


KMongo unable to save field with name "isClosed" and type "String"

Hi Team,
I have observed that when we are trying to save a document using kmongo methods, field "isClosed" is ignored if it is of type String.
However same field name with Boolean data type works.
Also, if document contains an additional field with name "closed" and type String along with "isClosed", it doesn't save "closed" and rather saves "isClosed".
We have a use case where we need to persist isClosed field name but facing issue.
Is this something which is expected or isClosed as string is some keyword ?

Indeed there is a bug.
Workaround: data class Test1(@get:JsonProperty("isClosed") val isClosed:String)

Looks like a bug in jackson-module-kotlin lib https://github.com/FasterXML/jackson-module-kotlin/issues/575

Thank you for reviewing. We are using the workaround for now.


WGAN GP vs LSGAN

I was wondering if the effort to replace LSGAN with WGAN GP is worthy.
The literature says that the Generate loss becomes a useful metric in WGAN GP. That could be useful.

Hi, we've tried WGAN GP but there was not a significant improvement, at least on Mixamo dataset. Training WGANGP will introduce second-order derivative and there will be a considerable overhead. Personally I feel it is not necessary.

Thanks.


Updating to the Type 2 report link

Coverage: 94.268%. Remained the same when pulling 5e4d0695168094b04799864ff01b6f4557a2f4d6 on reshma-report-link into 856eef31f637c409cbb294476659f6984a3445cd on main.


request: Close all to the left button.

Dear readers and Hero's that maintain the Spyder IDE.
Big fan of your product, don't know what I should do without it.
Could you mabey add a button that closes all tabs to the left. Now there is only a button to close to the right, or close all but this. But no close the the left. You have no Idea how happy I would be if this could be added.

Hi @Leohanhart thank you for the feedback! I think that such an option makes a lot of sense! What do you think @spyder-ide/core-developers ?

I think this is a good idea. It shouldn't be that hard to add that functionality.


The rpm has missing dependencies

It seems that the official RPM is missing a ton of dependencies, at least in Fedora 33.
Check these out: https://download.copr.fedorainfracloud.org/results/zawertun/crystal/fedora-33-x86_64/01906375-crystal/crystal.spec
The dependencies are far more that what gets installed when I use the crystal repo.
AFAICS, you're missing:
gc-devel
gpm-devel
libxml2-devel
libyaml-devel
openssl-devel
xz-devel
My test was trying to build amber framework with the installed crystal version. I've installed v0.35.1 (because 0.36.0 breaks amber).
My system's info:
* OS Release (cat /etc/*-release | uniq):
     Fedora release 33 (Thirty Three)
     NAME=Fedora
     VERSION="33 (Workstation Edition)"
     ID=fedora
     VERSION_ID=33
     VERSION_CODENAME=""
     PLATFORM_ID="platform:f33"
     PRETTY_NAME="Fedora 33 (Workstation Edition)"
     ANSI_COLOR="0;38;2;60;110;180"
     LOGO=fedora-logo-icon
     CPE_NAME="cpe:/o:fedoraproject:fedora:33"
     HOME_URL="https://fedoraproject.org/"
     DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/"
     SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
     BUG_REPORT_URL="https://bugzilla.redhat.com/"
     REDHAT_BUGZILLA_PRODUCT="Fedora"
     REDHAT_BUGZILLA_PRODUCT_VERSION=33
     REDHAT_SUPPORT_PRODUCT="Fedora"
     REDHAT_SUPPORT_PRODUCT_VERSION=33
     PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
     VARIANT="Workstation Edition"
     VARIANT_ID=workstation
     Fedora release 33 (Thirty Three)

* Kernel (uname -r ; cat /proc/cmdline):
     5.10.9-201.fc33.x86_64
     BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.10.9-201.fc33.x86_64 root=UUID=934e5565-cbc7-47c1-b488-ed4dfead07cb ro rootflags=subvol=root rhgb quiet processor.max_cstate=5 rcu_nocbs=0-11

* Desktop(s) Running (ps -eo comm= | grep -E '(gnome-session|startkde|startactive|xfce.?-session|fluxbox|blackbox|hackedbox|ratpoison|enlightenment|icewm-session|od-session|wmaker|wmx|openbox-lxde|openbox-gnome-session|openbox-kde-session|mwm|e16|fvwm|xmonad|sugar-session|mate-session|lxqt-session|cinnamon)' ):
     gnome-session-b
     gnome-session-c
     gnome-session-b

* Desktop(s) Installed (ls -m /usr/share/xsessions/ | sed 's/\.desktop//g' ):
     budgie-desktop, gnome-classic, gnome,
     gnome-xorg

* SELinux Status (sestatus):
     SELinux status:                 enabled
     SELinuxfs mount:                /sys/fs/selinux
     SELinux root directory:         /etc/selinux
     Loaded policy name:             targeted
     Current mode:                   enforcing
     Mode from config file:          enforcing
     Policy MLS status:              enabled
     Policy deny_unknown status:     allowed
     Memory protection checking:     actual (secure)
     Max kernel policy version:      33

* SELinux Errors (selinuxenabled && journalctl --since yesterday |grep avc: | grep -Eo comm="[^ ]+" | sort |uniq -c |sort -rn):
           2 comm="systemd-tmpfile"

* CPU Model (grep 'model name' /proc/cpuinfo | awk -F: '{print $2}' | uniq -c |
     sed -re 's/^ +//' ):
     16  AMD Ryzen 7 1800X Eight-Core Processor

* 64-bit Support (grep -q ' lm ' /proc/cpuinfo && echo Yes || echo No):
     Yes

* Hardware Virtualization Support (grep -Eq '(vmx|svm)' /proc/cpuinfo && echo Yes || echo No):
     Yes

* Load average (uptime):
      17:34:16 up 2 days, 12:16,  1 user,  load average: 0.67, 1.18, 1.30

* Memory usage (free -m):
                   total        used        free      shared  buff/cache   available
     Mem:          64301       12574        1430         207       50297       50956
     Swap:          8191           3        8188

* Top 5 CPU hogs (ps axuScnh | awk '$2!=436183' | sort -rnk3 | head -5):
          107   88678 27.8  9.2 21782828 6095088 ?    Sl   Jan25 701:04 qemu-system-x86
         1000    9830 22.9  0.0  26140 15692 ?        Ss   Jan25 750:25 systemd
         1000  418425 21.6  1.1 4657628 776676 ?      Sl   17:08   5:34 firefox
         1000  423177 14.6  0.0 233804  6704 pts/0    Ss   17:17   2:27 bash
         1000  418649  8.4  0.6 3601236 445680 ?      Sl   17:08   2:10 Web Content

* Top 5 Memory hogs (ps axuScnh | sort -rnk4 | head -5):
          107   88678 27.8  9.2 21782828 6095088 ?    Sl   Jan25 701:04 qemu-system-x86
         1000  418425 21.6  1.1 4657628 776676 ?      Sl   17:08   5:34 firefox
         1000   10426  0.0  1.0 1452188 702940 ?      Sl   Jan25   0:48 gnome-software
            0    1689  0.0  0.9 1184620 612796 ?      Ssl  Jan25   1:09 packagekitd
         1000  418656  2.7  0.6 3439884 451992 ?      Sl   17:08   0:42 Web Content

* Disk space usage (df):
     Filesystem      1K-blocks      Used  Available Use% Mounted on
     devtmpfs         32864392         0   32864392   0% /dev
     tmpfs            32922604     35576   32887028   1% /dev/shm
     tmpfs            13169044      2456   13166588   1% /run
     /dev/nvme0n1p3  498443264 320413504  176661440  65% /
     /dev/nvme0n1p3  498443264 320413504  176661440  65% /srv
     /dev/nvme0n1p3  498443264 320413504  176661440  65% /home
     /dev/nvme0n1p2     999320    288000     642508  31% /boot
     /dev/nvme0n1p1     613184     20772     592412   4% /boot/efi
     tmpfs            32922608      8072   32914536   1% /tmp
     /dev/sda1<PHONE_NUMBER> 601673476<PHONE_NUMBER>  16% /var/lib/libvirt/images
     /dev/nvme0n1p3  498443264 320413504  176661440  65% /var/lib/libvirt/images/fast
     /dev/sda1<PHONE_NUMBER> 601673476<PHONE_NUMBER>  16% /home/renich/Downloads
     /dev/sda1<PHONE_NUMBER> 601673476<PHONE_NUMBER>  16% /home/renich/VirtualMachines/isos
     /dev/sda1<PHONE_NUMBER> 601673476<PHONE_NUMBER>  16% /home/renich/Videos/movies
     /dev/sda1<PHONE_NUMBER> 601673476<PHONE_NUMBER>  16% /home/renich/xzone
     tmpfs             6584520<PHONE_NUMBER>   1% /run/user/1000

* Block devices (blkid):
     /dev/nvme0n1p3: LABEL="fedora" UUID="934e5565-cbc7-47c1-b488-ed4dfead07cb" UUID_SUB="d07aecb3-ed70-4fea-bce7-f568c999b165" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="5a6076d9-174e-46a0-a6f3-38f05ea33d89"
     /dev/nvme0n1p2: UUID="2919b7e6-0ca5-494e-9ca2-f9502faf6d01" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="55884fcb-1fc5-4157-a3ba-9677fc0dd2d2"
     /dev/nvme0n1p1: UUID="866B-15BA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="1c6865f5-cd08-411d-aaf6-c53c3fca0c57"

* PCI devices (lspci -nn):
     00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450]
     00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451]
     00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
     00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
     00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
     00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
     00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
     00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
     00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59)
     00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
     00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460]
     00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461]
     00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462]
     00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463]
     00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464]
     00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465]
     00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
     00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]
     01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804]
     02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02)
     02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller [1022:43b5] (rev 02)
     02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port [1022:43b0] (rev 02)
     03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
     04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242]
     05:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
     06:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
     08:00.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller [1095:3132] (rev 01)
     0b:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:14a0] (rev c1)
     0c:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:14a1]
     0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1)
     0d:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20]
     0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a]
     0e:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456]
     0e:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller [1022:145c]
     0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455]
     0f:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
     0f:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]

* USB devices (lsusb):
     Bus 006 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
     Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 005 Device 004: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
     Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
     Bus 005 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
     Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 003 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
     Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 001 Device 004: ID 046d:085e Logitech, Inc. Logitech BRIO
     Bus 001 Device 003: ID 09e8:0045 AKAI  Professional M.I. Corp. MPK Mini Mk II MIDI Controller
     Bus 001 Device 002: ID 0b05:1825 ASUSTek Computer, Inc. Qualcomm Bluetooth 4.1
     Bus 001 Device 006: ID 145f:024b Trust Trust Wired Keyboard
     Bus 001 Device 007: ID 1d57:ad17 Xenta ZELOTES GAME MOUSE
     Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

* DRM Information (journalctl -k -b | grep -o 'kernel:.*drm.*$' | cut -d ' ' -f 2- ):
     [drm] amdgpu kernel modesetting enabled.
     fb0: switching to amdgpudrmfb from EFI VGA
     [drm] initializing kernel modesetting (VEGA20 0x1002:0x66AF 0x1002:0x081E 0xC1).
     [drm] register mmio base: 0xFCB00000
     [drm] register mmio size: 524288
     [drm] add ip block number 0 <soc15_common>
     [drm] add ip block number 1 <gmc_v9_0>
     [drm] add ip block number 2 <vega10_ih>
     [drm] add ip block number 3 <psp>
     [drm] add ip block number 4 <gfx_v9_0>
     [drm] add ip block number 5 <sdma_v4_0>
     [drm] add ip block number 6 <powerplay>
     [drm] add ip block number 7 <dm>
     [drm] add ip block number 8 <uvd_v7_0>
     [drm] add ip block number 9 <vce_v4_0>
     [drm] UVD(0) is enabled in VM mode
     [drm] UVD(1) is enabled in VM mode
     [drm] UVD(0) ENC is enabled in VM mode
     [drm] UVD(1) ENC is enabled in VM mode
     [drm] VCE enabled in VM mode
     [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
     [drm] Detected VRAM RAM=16368M, BAR=256M
     [drm] RAM width 4096bits HBM
     [drm] amdgpu: 16368M of VRAM memory ready
     [drm] amdgpu: 16368M of GTT memory ready.
     [drm] GART: num cpu pages 131072, num gpu pages 131072
     [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
     [drm] Found UVD firmware ENC: 1.2 DEC: .43 Family ID: 19
     [drm] PSP loading UVD firmware
     [drm] Found VCE firmware Version: 57.6 Binary ID: 4
     [drm] PSP loading VCE firmware
     [drm] reserve 0x400000 from 0x83fec00000 for PSP TMR
     [drm] kiq ring mec 2 pipe 1 q 0
     [drm] Display Core initialized with v3.2.104!
     [drm] UVD and UVD ENC initialized successfully.
     [drm] VCE initialized successfully.
     [drm] fb mappable at 0xE0959000
     [drm] vram apper at 0xE0000000
     [drm] size 19906560
     [drm] fb depth is 24
     [drm]    pitch is 13824
     fbcon: amdgpudrmfb (fb0) is primary device
     amdgpu 0000:0d:00.0: [drm] fb0: amdgpudrmfb frame buffer device
     [drm] Initialized amdgpu 3.40.0 20150101 for 0000:0d:00.0 on minor 0

* Xorg modules (grep LoadModule /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d \" -f 2 | xargs):
     glx amdgpu ati radeon modesetting fbdev vesa fbdevhw fb dri2 glamoregl ramdac libinput

* GL Support (glxinfo | grep -E "OpenGL version|OpenGL renderer"):
     OpenGL renderer string: AMD Radeon VII (VEGA20, DRM 3.40.0, 5.10.9-201.fc33.x86_64, LLVM 11.0.0)
     OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.3.3

* Xorg errors (grep '^\[.*(EE)' /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d ':' -f 2- ):
     [ 23882.071] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
     [ 26328.538] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow
     [ 26703.167] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 29ms, your system is too slow
     [ 27254.938] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
     [ 28592.084] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 21ms, your system is too slow
     [ 29737.977] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 22ms, your system is too slow
     [ 30311.456] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
     [ 31027.544] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
     [ 65641.903] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
     [102414.603] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 12ms, your system is too slow
     [103826.055] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 24ms, your system is too slow
     [104286.367] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 31ms, your system is too slow
     [104374.050] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
     [111278.504] (EE) event7  - ZLY ZELOTES GAME MOUSE: client bug: event processing lagging behind by 124ms, your system is too slow
     [114794.283] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 20ms, your system is too slow
     [116422.089] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
     [117879.555] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
     [119364.104] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 28ms, your system is too slow
     [119915.987] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 29ms, your system is too slow
     [120554.073] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow
     [126507.594] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 24ms, your system is too slow
     [127504.971] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
     [128269.945] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
     [193225.271] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow
     [197628.944] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
     [197634.041] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
     [197788.651] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 19ms, your system is too slow
     [216002.069] (EE) event3  - SEMICO Trust Wired Keyboard: client bug: event processing lagging behind by 31ms, your system is too slow

* Kernel buffer tail (dmesg | tail):
     [214756.158881] wlp6s0: authenticate with b6:c4:40:89:8b:f4
     [214756.212074] wlp6s0: send auth to b6:c4:40:89:8b:f4 (try 1/3)
     [214756.320436] wlp6s0: send auth to b6:c4:40:89:8b:f4 (try 2/3)
     [214756.326458] wlp6s0: authenticated
     [214756.327410] wlp6s0: associate with b6:c4:40:89:8b:f4 (try 1/3)
     [214756.341557] wlp6s0: RX AssocResp from b6:c4:40:89:8b:f4 (capab=0x1431 status=0 aid=5)
     [214756.343713] wlp6s0: associated
     [214756.361502] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
     [214756.393780] wlp6s0: Limiting TX power to 30 (30 - 0) dBm as advertised by b6:c4:40:89:8b:f4
     [215317.939882] wlp6s0: deauthenticating from b6:c4:40:89:8b:f4 by local choice (Reason: 3=DEAUTH_LEAVING)

* Last few reboots (last -x -n10 reboot runlevel):
     runlevel (to lvl 5)   5.10.9-201.fc33. Mon Jan 25 05:18   still running
     reboot   system boot  5.10.9-201.fc33. Mon Jan 25 05:17   still running
     runlevel (to lvl 5)   5.10.9-201.fc33. Sun Jan 24 12:09 - 05:18  (17:08)
     reboot   system boot  5.10.9-201.fc33. Sun Jan 24 12:08   still running
     runlevel (to lvl 5)   5.10.8-200.fc33. Fri Jan 22 08:57 - 12:08 (2+03:10)
     reboot   system boot  5.10.8-200.fc33. Fri Jan 22 08:56 - 12:08 (2+03:11)
     reboot   system boot  5.10.8-200.fc33. Fri Jan 22 00:14 - 00:14  (00:00)
     runlevel (to lvl 5)   5.10.8-200.fc33. Wed Jan 20 09:24 - 00:13 (1+14:49)
     reboot   system boot  5.10.8-200.fc33. Wed Jan 20 09:24 - 00:13 (1+14:49)
     reboot   system boot  5.10.8-200.fc33. Wed Jan 20 09:15 - 00:13 (1+14:58)

     wtmp begins Wed Oct 28 01:12:12 2020

* DNF Repositories (dnf repolist):
     repo id                                                       repo name
     copr:copr.fedorainfracloud.org:elxreno:go-ipfs                Copr repo for go-ipfs owned by elxreno
     copr:copr.fedorainfracloud.org:rodrigofarias77:budgie-desktop Copr repo for budgie-desktop owned by rodrigofarias77
     copr:copr.fedorainfracloud.org:zawertun:crystal               Copr repo for crystal owned by zawertun
     crystal                                                       Crystal
     fedora                                                        Fedora 33 - x86_64
     fedora-cisco-openh264                                         Fedora 33 openh264 (From Cisco) - x86_64
     fedora-modular                                                Fedora Modular 33 - x86_64
     google-chrome                                                 google-chrome
     google-cloud-sdk                                              Google Cloud SDK
     hashicorp                                                     Hashicorp Stable - x86_64
     kubernetes                                                    Kubernetes
     rpmfusion-free                                                RPM Fusion for Fedora 33 - Free
     rpmfusion-free-updates                                        RPM Fusion for Fedora 33 - Free - Updates
     rpmfusion-nonfree                                             RPM Fusion for Fedora 33 - Nonfree
     rpmfusion-nonfree-updates                                     RPM Fusion for Fedora 33 - Nonfree - Updates
     updates                                                       Fedora 33 - x86_64 - Updates
     updates-modular                                               Fedora Modular 33 - x86_64 - Updates

* DNF Extras (dnf -C list extras):
     Crystal                                          11 kB/s | 3.1 kB     00:00
     Is this ok [y/N]: Google Cloud SDK                                 11 kB/s | 3.6 kB     00:00
     Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Google Cloud SDK                                3.1 kB/s | 975  B     00:00
     Is this ok [y/N]: Kubernetes                                       13 kB/s | 3.6 kB     00:00
     Is this ok [y/N]: Is this ok [y/N]: Is this ok [y/N]: Kubernetes                                      3.2 kB/s | 975  B     00:00
     Is this ok [y/N]: Last metadata expiration check: 0:12:54 ago on Wed 27 Jan 2021 05:21:26 PM CST.
     P.R.O. .5.1.2.G.B....................G.Z.0.Y.F.J.Z.9........BO
     Boot0022* Fedora	HD(1,GPT,1c6865f5-cd08-411d-aaf6-c53c3fca0c57,0x800,0x12c000)/File(\EFI\FEDORA\SHIM.EFI)..BO

This has always been the case for rpm packages since there are no "recommended dependencies" as in deb packages.
gc-devel is not needed because a libgc.a is already available in the embedded lib directory.
The other packages are not mandatory for every crystal program, hence they are not dependencies. It could be better to have them for a nicer experiencie, but then if instead of openssl you prefer libressl, how that dependency should be expressed in rpm?
For the record, these are expressed at https://github.com/crystal-lang/distribution-scripts/blob/37e0f6c569547190e12e0580cbbdf19ee622eb37/bintray/Makefile#L220-L221

This has always been the case for rpm packages since there are no "recommended dependencies" as in deb packages.
gc-devel is not needed because a libgc.a is already available in the embedded lib directory.
The other packages are not mandatory for every crystal program, hence they are not dependencies. It could be better to have them for a nicer experiencie, but then if instead of openssl you prefer libressl, how that dependency should be expressed in rpm?
For the record, these are expressed at https://github.com/crystal-lang/distribution-scripts/blob/37e0f6c569547190e12e0580cbbdf19ee622eb37/bintray/Makefile#L220-L221

Man, all of the system info are absolutely not needed here :astonished:

Man, all of the system info are absolutely not needed here :astonished:

OK, well, we have weak and very weak deps: https://rpm.org/user_doc/dependencies.html#weak-dependencies
In any case, it's better to include them. They don't take a lot of space and you definitely want the crystal experience to be complete, IMHO.
Thank you for the gc-devel suggestion, btw.

OK, well, we have weak and very weak deps: https://rpm.org/user_doc/dependencies.html#weak-dependencies
In any case, it's better to include them. They don't take a lot of space and you definitely want the crystal experience to be complete, IMHO.
Thank you for the gc-devel suggestion, btw.

Man, all of the system info are absolutely not needed here 😲

@renich You can edit your post to add a spoiler
My system's info:
<details>

```
foo
```

Man, all of the system info are absolutely not needed here 😲

@renich You can edit your post to add a spoiler
My system's info:
<details>

```
foo
```

@oprypin done.

@oprypin done.


Use package sync

Lets see if this works!
Note: I'm mostly seeing if this works for CI. Although it might be nice to use it?

Thanks @shughes-uk! This, I think, will result in an enormous simplification to the CI setup here. Does package_sync work for things installed via git+https://...? If so, I think that will allow us to delete a couple hundred lines of yaml.

In this CI build we're seeing the following environment-related error:
E               coiled.errors.ClusterCreationError: Cluster status is error (reason: Scheduler Stopped -> Errors installing conda packages:
E               package pywin32-303-py37h89c1867_0 requires python_abi 3.7.* *_cp37m, but none of the providers can be installed) (cluster_id: 45747)

Though I'm confused why Python 3.7 is involved at all as this is supposed to be running on Python 3.9

Apart from the windows errors it looks like all the rest are related to not being robust for 502's in a couple of places, which I'll push a fix for.
It seems like y'all would be very keen for this to work, are proper git dependencies a blocker for that?

I believe so. We need to be able to install the current main branch of dask and distributed from GitHub

It seems like y'all would be very keen for this to work, are proper git dependencies a blocker for that?

From my perspective, git dependencies will be very nice to have for local A/B testing, but package_sync already useful as it is today. So, as far as prioritization goes, I might say medium?

Wait, actually we're using nightly dask and distributed releases on conda. So installing directly from GitHub isn't a blocker. @shughes-uk does package_sync handle detecting different conda channels?

Wait, actually we're using nightly dask and distributed releases on conda. So installing directly from GitHub isn't a blocker. @shughes-uk does package_sync handle detecting different conda channels?

Yes, as long as it's not a private conda channel I should work. Private one's may even work but I have not tested them at all

Okay, good to know. We're only installed from public channels

Working on those macos/windows issues. I have a fix in a MR that should hopefully make it to prod tomorrow

Windows is passing! The cleanup steps fail because I commented out the senv creation step.

Windows/macos is passing! The cleanup steps fail because I commented out the senv creation step.

Woo! Nothing gives me so much joy as deleting yaml!

Woo! Nothing gives me so much joy as deleting yaml!

This has been a great test of package sync, now it's working on linux, macos and windows! Any thoughts? Should this be merged?

Any thoughts? Should this be merged?

I think @jrbourbeau and I can take it over, if you don't mind -- we'll probably want to update some of the pytest fixtures here that do some reasoning about the software environment version, in addition to deleting most of the setup/cleanup work.

I just used this branch locally to run a test https://github.com/coiled/coiled-runtime/pull/212#issuecomment-1205855455 because I absolutely could not be bothered to deal with software environments ever again and it worked fine. Some rather silly mismatches, but no problems AFAICT.
The mismatches are concerning, because it's the sort of thing that'll work until it doesn't. Not being able to be confident that it's deterministic or reproducible will always make me hesitant. But it's not like the senvs currently built in this repo are either, and this is so so so much better to work with.

(But yes, this should be merged)

I just used this branch locally to run a test #212 (comment) because I absolutely could not be bothered to deal with software environments ever again and it worked fine. Some rather silly mismatches, but no problems AFAICT.
The mismatches are concerning, because it's the sort of thing that'll work until it doesn't. Not being able to be confident that it's deterministic or reproducible will always make me hesitant. But it's not like the senvs currently built in this repo are either, and this is so so so much better to work with.

Some of the mismatches are "cosmetic" in the UI. Others are due to using ~= by default. If there are packages you would consider critical to never have any level of mismatch, lemme know.
I'm also going to add a strict mode which means it would only ever replicate an environment exactly (this would fail for everything except a linux machine creating a cluster)

Any thoughts? Should this be merged?

I think @jrbourbeau and I can take it over, if you don't mind -- we'll probably want to update some of the pytest fixtures here that do some reasoning about the software environment version, in addition to deleting most of the setup/cleanup work.

Happy to let you have at it!

are there any packages you'd consider 'critical' and should never mismatch?

msgpack had a patch version mismatch in https://cloud.coiled.io/dask-engineering/clusters/46264/details. cloudpickle, pyarrow, etc. obviously belong on that list. But I also really don't want us to have to maintain a list of "critical packages".

are there any packages you'd consider 'critical' and should never mismatch?

msgpack had a patch version mismatch in https://cloud.coiled.io/dask-engineering/clusters/46264/details. cloudpickle, pyarrow, etc. obviously belong on that list. But I also really don't want us to have to maintain a list of "critical packages".

Ah nice catch, upgraded msgpack to critical on prod. I'm not sure there's any way around it sadly.

@ian-r-rose @jrbourbeau could we merge this? I'm adding some more benchmarks and would love to not have to deal with software environments.

I almost certainly need to update some of the benchmarking-related pytest fixtures before this can be merged, I haven't had the chance to do that yet

Specifically, these: https://github.com/coiled/coiled-runtime/blob/0a3eab5e476b9432b0b24d4317af2522bbcb0319/conftest.py#L66-L100

@gjoseph92, @ian-r-rose @shughes-uk and I spoke offline last Friday about this PR. We're all excited about the prospect of package_sync (as you mentioned, it will makes our lives better) but didn't quite have enough signal that package_sync was 100% the direction coiled is moving in and would be around for a while. We want to avoid ripping out a bunch of software environment code and then having to put it back if package_sync goes away. Though, to be clear, if package_sync is here to stay then I would love to rip out the software environment code.
@shughes-uk we were planning to check back in on this topic this Friday after package_sync had gone through more testing. Are we still in the same place as last Friday, or do we have more information related to package_sync being the way of the future?

didn't quite have enough signal that package_sync was 100% the direction coiled is moving in and would be around for a while. We want to avoid ripping out a bunch of software environment code and then having to put it back

Though I understand that the package_sync interface and implementation may change, I would be very disappointed to hear that having no form of environment synchronization is something we're actually considering. Whether it happens through package_sync, lockfiles, or some other mechanism we haven't come up with yet, I would very much hope that we agree that however we do it, managing software environments as explicit artifacts will be a thing of the past, or at least that there will be an option besides it. So in that case, dropping the software environment code seems like a safe bet, even if we eventually have to change the spelling of package_sync to something else.

Certainly understand your concern @gjoseph92

even if we eventually have to change the spelling of package_sync to something else.

I'm totally fine with changing the spelling of package_sync or some other small interface changes. I'm just wanting more clarity on whether or not environment syncing (regardless of the keyword we choose) is in fact something we generally intend to support. I know folks are excited about it (myself included) but I've yet to hear a definitive answer. My understanding is we're still gathering more data / testing package_sync at the moment. If that understanding is outdated, I'd love to be updated to whatever the current state is.
FWIW it looks like @ian-r-rose is pushing forward over in https://github.com/coiled/coiled-runtime/pull/235 so we can see what impact switching to package_sync would have on the runtime

@gjoseph92 don't sweat it, getting there slowly. I know the current system is painful but hold on just a little longer

@shughes-uk mind if we close this in favor of https://github.com/coiled/coiled-runtime/pull/235?

@shughes-uk mind if we close this in favor of #235?

all yours!


Websocket alternatives

This might be the most unconventional place to do this. What is the alternative to Twirp for Websocket endpoints

😆 this is actually something I've thinking about.
Do you mean something like defining messages in protobuf and then autogenerating consumers / publishers that communicate over websockets?

Exactly. Something similar to that.
The autonomy from the server, as seen in Twirp, along with support for HTTP/1.1, is what is most important.
This resolves the compatibility issues between HTTP/2 and AWS Lambda and others. Moreover, an independent Handler would enable seamless integration with an existing server. Presently, the sole way to handle steaming that I’m aware of involves GRPC-Web, but it brings along its own server, doesn’t use websockets.
Desired Features
•	WebSocket support
•	Independence from a specific server
•	Compatibility with HTTP/1.1
•	Integration with existing servers

Protobuf example

service Foo {
    rpc FooEvent(FooMessage) returns FooResponses
}

message FooResponses {
        oneof data {
              Foo foo = 1;
              Bar bar = 2;
       }
}

***JS implementation ***
This doesn’t look perfect though.
const client = FooService();

client.onConnection = () => {}

client.onMessage({
before() {},
beforeEach(){},
FooEvent(data) {},
  })

Exactly. Something similar to that.
The autonomy from the server, as seen in Twirp, along with support for HTTP/1.1, is what is most important.
This resolves the compatibility issues between HTTP/2 and AWS Lambda and others. Moreover, an independent Handler would enable seamless integration with an existing server. Presently, the sole way to handle steaming that I’m aware of involves GRPC-Web, but it brings along its own server, doesn’t use websockets.
Desired Features
•	WebSocket support
•	Independence from a specific server
•	Compatibility with HTTP/1.1
•	Integration with existing servers

Protobuf example

service Foo {
    rpc FooEvent(FooMessage) returns FooResponses
}

message FooResponses {
        oneof data {
              Foo foo = 1;
              Bar bar = 2;
       }
}

***JS implementation ***
This doesn’t look perfect though.
const client = FooService();

client.onConnection = () => {}

client.onMessage({
before() {},
beforeEach(){},
FooEvent(data) {},
  })

I think high-level I'd approach this like:
// This indicates the server publishes Hat events

service Haberdasher {
  rpc HatCreated(google.protobuf.Empty) returns (stream Hat);
}

// This indicates the server accepts Hat events from the client

service Haberdasher {
  rpc HatCreated(stream Hat) returns (google.protobuf.Empty);
}

// This indicates bidirectional communication, both the server the client can publish Hat events

service Haberdasher {
  rpc HatCreated(stream Hat) returns (stream Hat);
}

The service name and rpc name would be concated with a period to create a message key, so the example above would publish messages that looked like:
message {
  key: 'Haberdasher.HatCreated',
  payload: Hat
}

And the client could look something like:
client.on('Haberdasher.HatCreated', () => { ... })`

or
client.publish('Haberdasher.HatCreated', message)

And the server could look like:
server.on('Haberdasher.HatCreated', Haberdasher.HatCreatedHandler)

or
server.publish('Haberdasher.HatCreated', message)

Could you expand on what you mean by

the compatibility issues between HTTP/2 and AWS Lambda and others

Or point me to something more context?

Also, is this roughly in line with what you’re thinking? Or are you more interested in something request / response style that supports streaming discrete messages?


Removed issues where stores/indexes weren't be loaded properly

Coverage increased (+0.5%) to 47.394% when pulling e00d5cbfecf9d6e7072be0474016cf5c8f840aeb on load-fix into b181e64e05c8f4a58f12c1188d7948341864e274 on master.


Reduce the runtime of two notebooks

Issue #, if available:
There are two pennylane notebooks take too long to finish
Description of changes:
We reduce the runtime by reducing the number of iterations while making sure the result is still reasonable.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@maolinml I'm re-writing these example notebooks now to use hybrid jobs anyways. Should be done in 1-2 weeks once we are code complete.

Please do not merge this PR. @mbeach-aws is rewriting the two examples with Jobs in this PR https://github.com/amazon-braket/amazon-braket-examples/pull/408 and I will close this one once that PR is merged.

Please do not merge this PR. @mbeach-aws is rewriting the two examples with Jobs in this PR #408 and I will close this one once that PR is merged.

Ack. I will close it.

This PR [https://github.com/amazon-braket/amazon-braket-examples/pull/408] has been merged, and the runtimes of the two notebook seem to be decreased to below 1 second [!!!!], so I close this PR.


fetch from origin

Summary
Details and comments

Pull Request Test Coverage Report for Build 285749099

1715 of 1960 (87.5%)  changed or added relevant lines in 82 files are covered.
18 unchanged lines in 10 files lost coverage.
Overall coverage increased (+0.2%) to 83.709%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/aqua/algorithms/linear_solvers/linear_solver_result.py
13
14
92.86%

qiskit/aqua/algorithms/linear_solvers/numpy_ls_solver.py
18
19
94.74%

qiskit/aqua/components/optimizers/bobyqa.py
22
23
95.65%

qiskit/aqua/components/optimizers/imfil.py
21
22
95.45%

qiskit/aqua/components/optimizers/nlopts/nloptimizer.py
0
1
0.0%

qiskit/aqua/operators/primitive_ops/circuit_op.py
16
17
94.12%

qiskit/aqua/operators/state_fns/circuit_state_fn.py
10
11
90.91%

qiskit/aqua/operators/state_fns/dict_state_fn.py
17
18
94.44%

qiskit/aqua/operators/state_fns/operator_state_fn.py
4
5
80.0%

qiskit/aqua/algorithms/minimum_eigen_solvers/vqe.py
15
17
88.24%

Files with Coverage Reduction
New Missed Lines
%

qiskit/aqua/algorithms/eigen_solvers/numpy_eigen_solver.py
1
90.06%

qiskit/aqua/components/optimizers/aqgd.py
1
85.71%

qiskit/aqua/components/oracles/custom_circuit_oracle.py
1
83.33%

qiskit/aqua/components/oracles/logical_expression_oracle.py
1
88.51%

qiskit/aqua/components/oracles/truth_table_oracle.py
1
93.55%

qiskit/aqua/operators/primitive_ops/pauli_op.py
1
91.52%

qiskit/aqua/operators/state_fns/circuit_state_fn.py
1
84.88%

qiskit/optimization/converters/inequality_to_equality.py
1
81.73%

qiskit/finance/data_providers/wikipedia_data_provider.py
3
75.0%

qiskit/finance/data_providers/exchange_data_provider.py
7
65.08%

Totals

Change from base Build 251325941:
0.2%

Covered Lines:
19860

Relevant Lines:
23725

💛  - Coveralls


add interview and answer data model

in the frame of https://github.com/eHealthAfrica/sl-ebola-call-admin/issues/1047
add interview and answer.
PR just to check with @febeling that we are on the same model page :)

I'll complete the data models from https://script.google.com/a/ehealthnigeria.org/d/1Jl8TZMk6LKegC2zXU9ZDnbYBh1yLn0B71neCgImWGlUTj_BFEpQ_i9LG/edit?usp=sharing

@skoni the data model as discussed

@skoni do we need the callId on the interview model? I am missing the part with the callback
does it go like this call 1 --> N (callback) 1 -->  1 Interview 1 --> N Answer?

@emig Im also adding the callbackId to the interview. We pass this by a field and it somehow was not set by the script so far. There is also the humanId, which i dont see any use for, yet - because we can always get that via a callback -> call lookup. But it would be valuable for someone who looks at the actual response spreadsheet and wants to find the related call via fulltext-search. Can you add callbackId and also humanId here?

bon


Support for more 'Options' from the Complex Types

Some methods support additional options like queryOptions, amendOptions, subscribeOptions or previewOptions.
Currently we support adding queryOptions to the soapheader, but the others aren't done yet.
https://knowledgecenter.zuora.com/BC_Developers/SOAP_API/F_SOAP_API_Complex_Types

Options can now be passed to soap methods. Here is an example:
var zOptions = {
  requestOptions: {timeout: 15000},
  queryOptions: {useFastQuery: true}
}
z.query(queryString, zOptions, callbackFn);

040b7e9cf8dffeba1bd27815f856bc358cdf822b


Fix jar incompatibilities with SE runtime(s)

Built jar could have issues running on Java SE jvms with current jar settings.

6e9e4c7 addresses issues with missing jar dependencies, exe and jar files seem to work now on Windows 7


fix random node download failures by upgrading to latest github action with retry logic

Description
Fix random node download failures by upgrading to latest github action with retry logic.
While running builds I am often seeing node setup failures like:
> Run actions/setup-node@v1
Unexpected HTTP response: 500
Waiting [12](https://github.com/microsoft/responsible-ai-toolbox/runs/5834933514?check_suite_focus=true#step:4:12) seconds before trying again
Unexpected HTTP response: 500
Waiting 16 seconds before trying again
Error: Unexpected HTTP response: 500

Based on issue for this setup-node github action:
https://github.com/actions/setup-node/issues/133
It is recommended to update to the latest github action which has caching and better retry logic, which should resolve this issue.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[ ] erroranalysis
[ ] raiutils
[ ] raiwidgets
[ ] rai_core_flask
[ ] responsibleai

Tests

[ ] No new tests required.
[ ] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #1317 (5c6da48) into main (1f2db0a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1317   +/-   ##
=======================================
  Coverage   90.32%   90.32%
=======================================
  Files          34       34
  Lines        1395     1395
=======================================
  Hits         1260     1260
  Misses        135      135

Flag
Coverage Δ

unittests
90.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 1f2db0a...5c6da48. Read the comment docs.


Unpromise array support

Adds back signatures from Typescript lib/es2015.promise.d.ts which I incorrectly believed to be superceded by the iterable interfaces for all cases. In fact both code paths need to be preserved, and all arrays cannot be treated as iterables.

Already merged combined with another PR.


Upgrade Electron to 2.0.8

Before submitting, please confirm you've

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Please provide the following information:
Summary
Upgrade Electron to ~2.0.7~ 2.0.8.
It includes minor bug fixes and improvements for DWM of Windows.
Issue link
#753
Test Cases
Use the app on Windows which is disabling DWM. Please refer to #753.
Additional Notes
~https://circleci.com/gh/yuya-oc/desktop/959#artifacts~
https://circleci.com/gh/yuya-oc/desktop/962#artifacts

Happy to help test this, as we can reproduce the issue referenced in #753

Updated to Electron v2.0.8 due to security fix.
https://electronjs.org/blog/web-preferences-fix

Hi @weekscharlie, thanks for interested in this! Do you have any feedback? We'd be happy to get that.

Happy to test this.  Where can I get my hands on a developmental build to play with?

Based on my testing, the DWM issue in Windows 7 appears to be fixed in this 4.2.0 dev build.
Thanks!

Much appreciated, @weekscharlie!
I couldn't see other significant issues, so I merge this for now.


Remove dependency to Flutter

Package are described as:

A pure-Dart package for reading and writing metadata for different audio format

But in pubspec.yaml there are dependency to Flutter, flutter_test and flutter_lints. The last dependency are not that serious but I would recommend changing this package to be a normal Dart package entirely and therefore instead use https://pub.dev/packages/lints.
The dependency to Fluttes does make this "pure-Dart package" not usable for pure-Dart projects. I have looked in all source files and I see no reason for the Flutter dependency. :)

Hi!
It seems I have messed up with the project generation or whatever. Thank you for reporting this! I'll be more careful for my future projects :)


prometheus.remote_write.metrics_service.receiver Does not exist or is out of scope

What's wrong?
I tried integrating alloy on my server(Ubuntu 24.04) with grafana Cloud. But encountered problems when trying to add the remote config for the node exporter, mysql and loki logs.
Steps to reproduce
I tried to add the config for the node exporter(Connections -> Add new connection -> Linux Server), via the remote config(same thing happens when I tried to add it to the config file, on the server, manually, appending it to the existing contents), I got the following error:
	ts=2024-12-30T11:44:35.814363889Z level=error msg="failed to evaluate config" controller_path=/ controller_id=remotecfg trace_id=1d02509b4cfb1c88ba49cf76a5db8be2 node=NodeExporter.default err="updating custom component: 40:17: component \"prometheus.remote_write.metrics_service.receiver\" does not exist or is out of scope"

Same thing happens when I try to add for mysql or loki logs:
# Loki
ts=2024-12-30T11:44:35.814602786Z level=error msg="failed to fetch remote configuration from the API" service=remotecfg err="87:17: component \"loki.write.grafana_cloud_loki.receiver\" does not exist or is out of scope (and 2 more diagnostics)"

# Mysql
ts=2024-12-30T11:44:35.813944533Z level=error msg="failed to evaluate config" controller_path=/ controller_id=remotecfg trace_id=1d02509b4cfb1c88ba49cf76a5db8be2 node=mariadb.default err="updating custom component: 87:17: component \"loki.write.grafana_cloud_loki.receiver\" does not exist or is out of scope (and 1 more diagnostics)"

System information
Ubuntu 24.04
Software version
Alloy v1.5.1 (branch: HEAD, revision: dc8a365f8)
Configuration
declare "NodeExporter" {
	discovery.relabel "integrations_node_exporter" {
		targets = prometheus.exporter.unix.integrations_node_exporter.targets

		rule {
			target_label = "instance"
			replacement  = constants.hostname
		}

		rule {
			target_label = "job"
			replacement  = "integrations/node_exporter"
		}
	}

	prometheus.exporter.unix "integrations_node_exporter" {
		disable_collectors = ["ipvs", "btrfs", "infiniband", "xfs", "zfs"]

		filesystem {
			fs_types_exclude     = "^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|tmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$"
			mount_points_exclude = "^/(dev|proc|run/credentials/.+|sys|var/lib/docker/.+)($|/)"
			mount_timeout        = "5s"
		}

		netclass {
			ignored_devices = "^(veth.*|cali.*|[a-f0-9]{15})$"
		}

		netdev {
			device_exclude = "^(veth.*|cali.*|[a-f0-9]{15})$"
		}
	}

	prometheus.scrape "integrations_node_exporter" {
		targets    = discovery.relabel.integrations_node_exporter.output
		forward_to = [prometheus.relabel.integrations_node_exporter.receiver]
	}

	prometheus.relabel "integrations_node_exporter" {
		forward_to = [prometheus.remote_write.metrics_service.receiver]

		rule {
			source_labels = ["__name__"]
			regex         = "node_scrape_collector_.+"
			action        = "drop"
		}
	}
}

NodeExporter "default" { }

declare "mariadb" {
	prometheus.exporter.mysql "integrations_mysqld_exporter" {
		data_source_name = "XXXXXX:XXXXXXX@(localhost:3306)/"
	}

	discovery.relabel "integrations_mysqld_exporter" {
		targets = prometheus.exporter.mysql.integrations_mysqld_exporter.targets

		rule {
			target_label = "job"
			replacement  = "integrations/mysql"
		}

		rule {
			target_label = "instance"
			replacement  = constants.hostname
		}
	}

	prometheus.scrape "integrations_mysqld_exporter" {
		targets    = discovery.relabel.integrations_mysqld_exporter.output
		forward_to = [prometheus.remote_write.metrics_service.receiver]
		job_name   = "integrations/mysqld_exporter"
	}

	local.file_match "logs_integrations_mysql" {
		path_targets = [{
			__address__ = "localhost",
			__path__    = "/var/log/mysql/*.log",
			instance    = constants.hostname,
			job         = "integrations/mysql",
		}]
	}

	loki.process "logs_integrations_mysql" {
		forward_to = [loki.write.grafana_cloud_loki.receiver]

		stage.regex {
			expression = "(?P<timestamp>.+) (?P<thread>[\\d]+) \\[(?P<label>.+?)\\]( \\[(?P<err_code>.+?)\\] \\[(?P<subsystem>.+?)\\])? (?P<msg>.+)"
		}

		stage.labels {
			values = {
				err_code  = null,
				level     = "label",
				subsystem = null,
			}
		}

		stage.drop {
			drop_counter_reason = "drop empty lines"
			expression          = "^ *$"
		}
	}

	loki.source.file "logs_integrations_mysql" {
		targets    = local.file_match.logs_integrations_mysql.targets
		forward_to = [loki.process.logs_integrations_mysql.receiver]
	}
}

mariadb "default" { }

declare "self_monitoring_logs_linux" {

	// THIS IS A GENERATED REMOTE CONFIGURATION.
	//
	//   * You can edit the contents and matchers for this configuration without them being overwritten.
	//   * If you delete ALL generated configurations, the latest default versions will be recreated.
	//   * This configuration requires the following environment variables to be set wherever alloy is running:
	//     * GCLOUD_RW_API_KEY: The Grafana Cloud API key with write access to Loki.
	//     * GCLOUD_FM_COLLECTOR_ID: A unique collector ID matching the remotecfg id argument value.

	// Write logs to your Grafana Cloud Loki instance.
	loki.write "grafana_cloud_loki" {
		endpoint {
			url = "https://logs-prod-012.grafana.net/loki/api/v1/push"

			basic_auth {
				username = "XXXXXX"
				password = sys.env("GCLOUD_RW_API_KEY")
			}
		}
	}

	// Read Alloy logs when running as a systemd service with the following additional labels:
	//   * job: "integrations/alloy" is compatible with Grafana Cloud's Alloy Health Integrations.
	//   * collector_id: The unique collector ID matching the remotecfg id argument value.
	//                   Used to match collector-specific metrics to power the 'Collector
	//                   Health' section of the Fleet Management UI.
	loki.source.journal "alloy_logs_unit" {
		matches    = "_SYSTEMD_UNIT=alloy.service"
		forward_to = [loki.write.grafana_cloud_loki.receiver]
		labels     = {"job" = "integrations/alloy", "collector_id" = sys.env("GCLOUD_FM_COLLECTOR_ID")}
	}

	// Read Alloy logs from syslog with the following additional labels:
	//   * job: "integrations/alloy" is compatible with Grafana Cloud's Alloy Health Integrations.
	//   * collector_id: The unique collector ID matching the remotecfg id argument value.
	//                   Used to match collector-specific metrics to power the 'Collector
	//                   Health' section of the Fleet Management UI.
	loki.source.journal "alloy_logs_tag" {
		matches    = "SYSLOG_IDENTIFIER=alloy"
		forward_to = [loki.write.grafana_cloud_loki.receiver]
		labels     = {"job" = "integrations/alloy", "collector_id" = sys.env("GCLOUD_FM_COLLECTOR_ID")}
	}
}

self_monitoring_logs_linux "default" { }

declare "self_monitoring_metrics" {

	// THIS IS A GENERATED REMOTE CONFIGURATION.
	//
	//   * You can edit the contents and matchers for this configuration without them being overwritten.
	//   * If you delete ALL generated configurations, the latest default versions will be recreated.
	//   * This configuration requires the following environment variables to be set wherever alloy is running:
	//     * GCLOUD_RW_API_KEY: The Grafana Cloud API key with write access to Loki.
	//     * GCLOUD_FM_COLLECTOR_ID: A unique collector ID matching the remotecfg id argument value.

	// Export Alloy metrics in memory.
	prometheus.exporter.self "integrations_alloy_health" { }

	// Target Alloy metrics with the following additional labels:
	//   * job: "integrations/alloy" is compatible with Grafana Cloud's Alloy Health Integrations.
	//   * collector_id: The unique collector ID matching the remotecfg id argument value.
	//                   Used to match collector-specific metrics to power the 'Collector
	//                   Health' section of the Fleet Management UI.
	//   * instance: The hostname of the machine running Alloy.
	discovery.relabel "integrations_alloy_health" {
		targets = prometheus.exporter.self.integrations_alloy_health.targets

		rule {
			action       = "replace"
			target_label = "collector_id"
			replacement  = sys.env("GCLOUD_FM_COLLECTOR_ID")
		}

		rule {
			target_label = "instance"
			replacement  = constants.hostname
		}

		rule {
			target_label = "job"
			replacement  = "integrations/alloy"
		}
	}

	// Scrape Alloy metrics and forward them to the remote write component.
	prometheus.scrape "integrations_alloy_health" {
		targets = array.concat(
			discovery.relabel.integrations_alloy_health.output,
		)
		forward_to = [prometheus.remote_write.default.receiver]
		job_name   = "integrations/alloy"
	}

	// Write metrics to your Grafana Cloud Prometheus instance.
	prometheus.remote_write "default" {
		endpoint {
			url = "https://prometheus-prod-24-prod-eu-west-2.grafana.net/api/prom/push"

			basic_auth {
				username = "XXXXXX"
				password = sys.env("GCLOUD_RW_API_KEY")
			}
		}
	}
}

self_monitoring_metrics "default" { }

Logs

This is the same general problem as was raised here https://github.com/grafana/alloy/issues/2281 - Fleet Management does not work out of the box with Integrations right now. It will soon! There should be some remediation instructions in that issue.


docs: enhance documentation by replacing words into attractive badges 📛✨

Description

Currently the Built With section on Documentation uses simple Text like HTML5 but we can make it as badges which will way more improve the readability of OpenTek's Documentation.
By including attractive Badges instead of Plaintext our Documentation will look more structured, concise for the Reader.

Screenshot

CURRENT
DESIRED

Hey there @AnirudhPanda 👋🏻
Please make sure to assign this issue to me to make the work done, Thank you!


cigien: Watch natur(?:e|al)[\W_]+relief[\W_]+cbd[\W_]+oil(?:[\W_]+(?:\d++|[\da-f]{5,}+)s?)*

cigien requests the watch of the watch_keyword natur(?:e|al)[\W_]*+relief[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:\d++|[\da-f]{5,}+)s?)*. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

natur(?:e|al)[\W_]*+relief[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:\d++|[\da-f]{5,}+)s?)* has been seen in 6 true positives, 0 false positives, and 0 NAAs.

natur(?:e|al)[\W_]*+relief[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:\d++|[\da-f]{5,}+)s?)* has been seen in 6 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ

Approved by tripleee in Charcoal HQ


CSS is lost on page navigation in static SSR with page-scoped interactive server directive

So this issue I am finding very difficult to replicate, tried in your examples and it just works fine.
Anyway, the issue.
This is all in Blazor Web App targeting .Net 8
I have the control on a page and it wall works great with theme applied etc.
Now, if I navigate to another page which also has the control on or if navigate away and come back, the control looks like it looses all css formatting i.e. you have the line numbers followed by content, all of this just stacked vertically with overflow happening, all theming loss etc.
I can't attach an example project as it's all confidential stuff and producing an example is not working.
Just wondered if you may know of something that may cause this. All other controls on the pages work fine.
Pressing F5/refresh does fix it

I managed to create an example! it seems to happen if you have the control hidden and then show it after navigating.

BlazorApp1.zip
Attached project.
Steps
Run it and use nav on left and go to Index1
Click button "Reset text" to show the Control, will have json content.
Use nav on left and go to Index2
Click button "Reset text" to show the Control which will have all styling not applied.

Thanks for creating an example of your issue. I will look into it.

The sample can be fixed by replacing,  in App.razor, <HeadOutlet /> with <HeadOutlet @rendermode="InteractiveServer" />.
Would that be acceptable ?

So I confirm that the 2nd approach seems to work fine, although it could be viewed as a horrible hack.

keep the simple <HeadOutlet /> in App.razor
start the app, do an initial load of the page with the theme you want to use
in  browser dev tools, copy the contents of the first style tag

paste the contents in your apps' wwwroot/app.css

I cannot - for now - guarantee this won't have any other side effects, than being unable to switch themes, so I currently don't feel super comfortable with providing this CSS in the wrapper library. Of the 2, I'd recommend the first approach, if possible.

That would break compatibility with WASM
It won't change anything in the present case where you already specify with the page directive, that all components in the page should be rendered in InteractiveServer mode. The problem is that CM6 tries to modify the header of the page. The header is managed in blazor server by HeadOutlet. So if HeadOutlet isn't told that the header could change after rendering the page, it won't try to persist thoses changes on the next navigation.

@Gaz83 can we close this issue ? I added an example project with the new hosting model.

@Gaz83 feel free to reopen if needed

@gaelj Sorry for late reply, been a bit tied up with other things in life. Yes I was happy for this to be closed, thank you.


tensorflow1.15,  Here is a list of operators for which you will need custom implementations: ReorderAxes.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04)  : ubuntu18.04
TensorFlow installed from (source or binary):   conda
TensorFlow version (or github SHA if from source): 1.15

Provide the text output from tflite_convert
# Copy and paste here

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Also, please include a link to a GraphDef or the model if possible.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and files
should be attached.

Some of the operators in the model are not supported by the standard TensorFlow Lite runtime and are not recognized by TensorFlow. If you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CONV_2D, FLOOR_DIV, FULLY_CONNECTED, GATHER, LEAKY_RELU, MEAN, MUL, PACK, PAD, RESHAPE, RSQRT, SHAPE, SQUARE, STRIDED_SLICE, SUB, SUM, TILE, TRANSPOSE, TRANSPOSE_CONV. Here is a list of operators for which you will need custom implementations: ReorderAxes.

converter = tf.lite.TFLiteConverter.from_saved_model(PATH)
print(dir(converter))
#converter.experimental_new_converter = True  ####
#converter.allow_custom_ops = True

converter.optimizations = [tf.lite.Optimize.DEFAULT]
converter.target_spec.supported_types = [tf.float16]
converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS,
                                       tf.lite.OpsSet.SELECT_TF_OPS]
tflite_model = converter.convert()

PATH  = './savedmodel'
converter = tf.lite.TFLiteConverter.from_saved_model(PATH)
print(dir(converter))
#converter.experimental_new_converter = True  ####量化
#converter.allow_custom_ops = True

converter.optimizations = [tf.lite.Optimize.DEFAULT]
converter.target_spec.supported_types = [tf.float16]

converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS,
tf.lite.OpsSet.SELECT_TF_OPS]
tflite_model = converter.convert()
open("./model/andriod/lite/pkl2pt_G_synthesis/converted_model3.tflite", "wb").write(tflite_model)

conver()
Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CONV_2D, FLOOR_DIV, FULLY_CONNECTED, GATHER, LEAKY_RELU, MEAN, MUL, PACK, PAD, RESHAPE, RSQRT, SHAPE, SQUARE, STRIDED_SLICE, SUB, SUM, TILE, TRANSPOSE, TRANSPOSE_CONV. Here is a list of operators for which you will need custom implementations: RandomStandardNormal.

Can you try enabling the custom_ops flag ?
converter.allow_custom_ops = True

@fcqfcq
Any update on this issue please. Thanks!


iOS  - crashes on LocalNotifier.Notify()

When running on iOS I get an exception when I call LocalNotifier.Notify
System.ExecutionEngineException: Attempting to JIT compile method 'LocalNotifications.Plugin.LocalNotifier:createNativeNotification (LocalNotifications.Plugin.Abstractions.LocalNotification)' while running with --aot-only. See http://docs.xamarin.com/ios/about/limitations for more information.
The code to reproduce is written in the AppDelegate in FinishLaunching.
var notifier = new LocalNotifer();
notifer.Notify(new LocalNotification
{
    Title = "Title",
    Text = "Text",
    Id = "1",
    NotifyTime = DateTime.Now,
}

This same code works just find on android.

Hi,
We are too facing the same issue while running the code " notifier.Notify(notification);" from PCL Project in iOS Platform and the same is working fine in Android Platform.
Do we need to include any other parameters in AppDelegate Class?
Exception:
{System.MissingMethodException: Method 'NSDate.op_Implicit' not found.  at LocalNotifications.Plugin.LocalNotifier.Notify (LocalNotifications.Plugin.Abstractions.LocalNotification notification) [0x00000] in :0   at Mobile.View.SamplePage..ctor () [0x0004a] in D:\Kathir\Mobile\Mobile\View\SamplePage.xaml.cs:38 }
Note:
We have followed only the below mentioned instructions in the link.
https://github.com/B1naryStudio/Xamarin.LocalNotifications

@catlin0123
I fixed this bug. Also you can find the working sample of using our plugin:
https://github.com/B1naryStudio/Xamarin.LocalNotifications/tree/master/Samples/LocalNotifications.Samples.iOS


Scripting links

http://www.kahrel.plus.com/indesign/scriptui-2-5.pdf
http://www.davidebarranca.com/2013/08/extendscript-scriptui-events-call-notify-dispatchevent/
https://github.com/fabiantheblind/extendscript
https://github.com/jtnimoy/scripting-for-illustrator-tutorial
Should have links/script section.

http://wwwimages.adobe.com/content/dam/Adobe/en/products/indesign/pdfs/JavaScriptToolsGuide_CS5.pdf

The above can be found via help menu via "Object Model Viewer".

Moving to https://github.com/mhulse/illy-anim