Working 'version' of WaveGlow

Hi everyone! I'm getting acquainted with this repo, particularly with trying out inference.ipynb. I have a question: I followed the instructions and ran "git submodule init; git submodule update" but it seems it didn't behave as expected (no waveglow folder created).
So I manually cloned from the github of WaveGlow (cloning, initializing and updating) and tried running inference.ipynb, but then ran into lots of errors that I think are related to version mismatches of waveglow and torch, etc. e.g. 'Conv1d' object has no attribute '_ non_persistent buffers set'
So may I ask if anyone has a copy/folder of waveglow that currently works this repo that you can share?
Thanks a lot and please let me know if there's anything I can provide to make my question clearer!

Found out that this error was actually related to PyTorch's version. Closed.


[WIP] Improved test coverage of ruby tests

This PR improves coverage of ruby tests.
Coverage of src/if_ruby.c was only 64.96% prior to this change according to codecov:
https://codecov.io/gh/vim/vim/src/master/src/if_ruby.c
I also made minor changes to the documentation runtime/doc/if_ruby.txt to clarify things that were ambiguous.

Codecov Report

Merging #3252 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3252      +/-   ##
==========================================
+ Coverage   76.48%   76.56%   +0.08%
==========================================
  Files          93       93
  Lines      136826   136826
==========================================
+ Hits       104648   104758     +110
+ Misses      32178    32068     -110

Impacted Files
Coverage Δ

src/ex_cmds.c
79.81% <0%> (-0.23%)
:arrow_down:

src/gui.c
49.48% <0%> (-0.11%)
:arrow_down:

src/undo.c
83.09% <0%> (-0.07%)
:arrow_down:

src/channel.c
83.03% <0%> (-0.04%)
:arrow_down:

src/screen.c
76.75% <0%> (+0.04%)
:arrow_up:

src/gui_gtk_x11.c
48.23% <0%> (+0.19%)
:arrow_up:

src/window.c
82.39% <0%> (+0.51%)
:arrow_up:

src/gui_beval.c
62.44% <0%> (+7.42%)
:arrow_up:

src/if_ruby.c
86.18% <0%> (+21.22%)
:arrow_up:

Continue to review full report at Codecov.

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

This PR is ready for merging in master.
Coverage of if_ruby.c went from 64.96% to 92.07% according to codecov.


revert vlim=joint in TF tutorial

reverts a tutorial change that was mostly meant as a test of changes to module code; turns out it's already demoed elsewhere (and is more appropriate in those other contexts)
ref: https://github.com/mne-tools/mne-python/pull/11051#issuecomment-1220354886  and subsequent comments.

back to normal: https://output.circle-artifacts.com/output/job/6bb066e5-c51a-46ba-9cac-6ce98b86a1af/artifacts/0/dev/auto_tutorials/time-freq/20_sensors_time_frequency.html#frequency-analysis


Converting SVG resulted in empty .tsx file

Observed results
Running convert on two svgs resulted in one working and the other creating a blank .tsx file. The only differences I see between the two svg files I used, is the RepeatIcon.svg below has transform, while the other does not. Possibly that is the issue?
Logs
// RepeatIcon.svg
<svg xmlns="http://www.w3.org/2000/svg" width="27.413" height="15.42" viewBox="0 0 27.413 15.42"><defs><style>.a{fill:#a0a0a0;}</style></defs><g transform="translate(0 -4)"><path class="a" d="M19.707,14.28V6.57A2.573,2.573,0,0,0,17.137,4H6L9.427,7.427H16.28V14.28H12.853l5.14,5.14,5.14-5.14Z" transform="translate(4.28 0)"/><path class="a" d="M6.853,15.993V9.14H10.28L5.14,4,0,9.14H3.427v7.71A2.573,2.573,0,0,0,6,19.42H17.133l-3.427-3.427Z" transform="translate(0 0)"/></g></svg>

Steps to reproduce

Put RepeatIcon.svg in app/assets/svg
Run airfoil convert svg

Was able to reproduce - this is very strange. Works on
https://react-svgr.com/playground

Issue ended up being the inline <style> tag. Fix imminent in #37 .

Should be fixed in version 0.3.1 - https://github.com/teamairship/airfoil/releases/tag/v0.3.1


Feature Request: Please add run tests in file menu back

There was a menu run tests in file before, I forgot from which version it was removed. without this menu,you have to right click at the beginning of the file or the end of the file(or some where not in a test case) to run all tests in the file. which is not convenient because you might need to scroll first to do it. with the old menu 'run tests in file', you can do it by right click at any place in the file.   (This was extremely annoying when there was a bug with jest each)
SO PLEASE ADD IT BACK.

its still there, just open the command palette strg+shift+p and search for "jest file".
i just dont want to flood the command menu with to many options.

are you happy with this option?


Fix for #29

Description

Motivation and Context

#29
How Has This Been Tested?

Added one new unit test
Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Codecov Report

Merging #30 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
+ Coverage   90.52%   90.57%   +0.04%
==========================================
  Files           2        2
  Lines         401      403       +2
==========================================
+ Hits          363      365       +2
  Misses         38       38

Flag
Coverage Δ

#HTMLEntities
90.57% <100%> (+0.04%)
:arrow_up:

Impacted Files
Coverage Δ

Sources/HTMLEntities/String+HTMLEntities.swift
89.44% <100%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

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


Add check in UTF test function for null project

The DCAF Core package does not have a project file, thus no UTF tests can be run.  The build of this package will always fail with error unless we check for a null project string and skip tests.  Alternative would be to not call the dcafpipeline, but a different one for this package.  Might go with second approach, since this is the metapackage that defines a release.

Fixed by iterating across an array of UTF projects, with empty arrays permitted.


feat(documentation): adds metadata story

The curren version of the metadata page please mention if there is something missing or other suggestions.

I still think that "Foundations" is the wrong navigation point to show this. I would rather create a new Navigation point like "General" or "Setup" or add this story to the "Getting Started" section.

Adding too many sections will not help either. Patterns could be a good place because it fits with the forms document there. We can discuss about the naming of that section.


Give Flag!"each" a more descriptive name

This makes it more obvious that "no" means "stop" and "yes" means
"continue".

Should be backwards compatible since the new enum uses Flag!"each" as its base type.
@atilaneves This introduces a new public symbol, Continue.

std/algorithm/iteration.d(841:6)[warn]: Public declaration 'Continue' has no documented example.

I'm unclear whether creating a federation of names is better than one simple convention.

@andralex In isolation, it's ambiguous whether return Yes.each; means "yes, stop" or "yes, keep going." return Continue.yes; is unambiguous.
If the question is, why not change the flag type to Flag!"continue" (Yes.continue, No.continue) instead of creating a new enum—it's to avoid breaking backwards compatibility.

@andralex In isolation, it's ambiguous whether return Yes.each; means "yes, stop" or "yes, keep going." return Continue.yes; is unambiguous.

To me Yes.each means to go on with each and No.each would mean to stop. If these are not obvious, a look at the documentation should settle it once and for all. Escalating this to an addition to the standard library seems much.
The larger problem is this creates a precedent whereby creating slightly clearer names becomes an art of it own. It's Good Work that will create opportunities for more Good Work.

If the question is, why not change the flag type to Flag!"continue" (Yes.continue, No.continue) instead of creating a new enum—it's to avoid breaking backwards compatibility.

I just see no utility in adding ever slightly better synonyms - this is an unending pit.

I guess it's up to @atilaneves. If Phobos policy is "all names are final" then I'll withdraw this. In any case, I do not intend to set a precedent here.
Perhaps it would be better to start a list of "names to improve in future std versions."

The named argument DIP (approved) should render this flag usage obsolete. It's not necessary to improve the names. As to what "yes" means, I'm reminded of https://www.youtube.com/watch?v=2rHW0Gl2lbM

Withdrawn in accordance with feedback.

@thewilsonator Please don't approve PRs that introduce new public symbols (it could have taken me more than 72 hours to see it). Thanks!

The named argument DIP (approved) should render this flag usage obsolete.

The flag is not passed as a parameter, and you can't give a return value a name, so I don't think that applies to this particular flag.


Micro continues to run in the background even after safe exit

Only started using now dev as of recently and my bad habit of spamming Ctrl+C to exit/close the server has resulted in Micro not closing correctly/safely and as such now when the server is "closed" I can still go to http://localhost:3000 and it will still be serving.
If I start the dev server up again it will continue to serve that old content and any change made since stopping the server previously will not be applied.
Is this a known bug? And is there a way to fix this? Have already restarted my system & cleared dev server cache, still persisting 😅

This issue can now be ignored. Seems that Chrome was instead caching the redirects I was setting 🤦♂


Search for help to test the modle by using my own dataset

I have got in troubles since I tried to test EDTER using my own datasets. I have been suffered a lot. So, would anyone like to give me a hand and answer my questions, extremly appreciated for that.
1.I have installed the mmcv==1.7.1, but i rewrited the range of the assert of version, the error about the mmcv version hadn't occured then, but I am not sure whether this operation wuold cause unknown issues.
2.I failed to kill the error of "BSDSDataset is not registried" by all methods i've learned including check the correct config of mmseg pakage.
3.I once tried to delet the dataloader part and write my own dataloader, but the code confused me, the logic of connection of different files is too complicated to adjust.

You can modify MMCV_MAX = '1.2.7' to MMCV_MAX = '1.7.1' in https://github.com/MengyangPu/EDTER/blob/de6438b82a1049f8b45ceb10f9137072151c1d17/mmseg/init.py#L6
Please try to：
cd EDTER
pip install -e .  # or "python setup.py develop"
pip install -r requirements/optional.txt
The dataloader codes in /mmseg/datasets/pipelines/


too many linestring cause preformance very show

I have more than 30000 points (about vehicle trajectory)， now I need to show on openlayer with lines, so I change points to linestrings, finally it casue my page perform very slow. How can I resolve it?

resolove it by https://openlayers.org/en/latest/examples/webgl-draw-line.html


Multiple select

I'm submitting a ...
[ ] bug report
[X ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

The multiple select is not working well. In the online demo is not present inside 'Form Inputs'.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

Multiple select it suppossed to work like Angular 1 Blur-Admin version: http://akveo.com/blur-admin-mint/#/form/inputs

What is the motivation / use case for changing the behavior?

I think it is an important and useful feature.

Please tell us about your environment:

Angular version: 2.0.0
Browser: [all | Chrome 53 | Firefox 49]

hey @FacundoGFlores, we updated the demo and now multiselect presented there http://akveo.com/ng2-admin/#/pages/forms/inputs


Episode idea: Kustomize

Doing Kustomize this week as episode 072.
The process for producing an episode is here.  All the detail for the steps below is there.
Monday or Tuesday:

[ ] Pick a topic and create/use an issue in the repo
[ ] If applicable coordinate with an upstream project if they're interested in attending the show
[ ] Create the graphic
[ ] Schedule on Youtube
[ ] Add scheduled episode to TGIK playlist on YT
[ ] Create short link in rebrandly
[ ] Tweet about it from your personal account

[ ] Post tweets on internal #tgik slack channel and cc @castrojo and @boschem
[ ] Get confirmation from @boschem that he's seen the tweet and is scheduling it

Before episode:

[ ] Create HackMD page for live notes.  Start with README template in this repo
[ ] Paste HackMD URL on internal #tgik channel and cc @castrojo or other assistant

[ ] Assistant adds ~5-10 news items from around the web as possible "News of the Week"

[ ] Get everything tested well before episode so you can debug
[ ] Use internal slack channel to ensure that AV setup is good

After show (ideally right away but can wait until Monday):

Create/submit PR for this repo

[ ] Episode directory and README from hackmd
[ ] Any other files from the episode that might be useful
[ ] Update playlist.md with episode
Feel free to self merge

[ ] Edit YT description to point to episode directory here
[ ] OBS/OS Upgrade if applicable (Never on the day of a show)

https://j.hept.io/tgik072

This looks great, can't wait to see it.
FYI, the most recent Kustomize documentation is in the new kubectl docs

Jetstack article on cert-manager+kustomize: https://blog.jetstack.io/blog/kustomize-cert-manager/

hackmd: https://hackmd.io/dn0KfrC3R3awmHpEgFMQSw?edit


Separate toolbox items into independently-wrappable "words"

The current toolbox cannot wrap in between "Permalink" or "Pin" or "Pin" and "References (…)" (and thus can horizontally overflow the viewport when a definition is near the right margin), but can wrap in between "References" and "(…)" (splitting a link and on the second line intruding into what otherwise looks like box padding). This PR disables wrapping inside those links and inserts break opportunities in between them.
Before

After

The excess horizontal width is a known issue with CSS "shrink-wrapping" that already exists and is not changed by this PR:
current excessive width

Thanks!


task CredScan@2 Microsoft.Security.CredScan broken

Since morning we are observing issue with Microsoft CredScan task
Unfortunately task documentation has no link to any repo, only https://learn.microsoft.com/en-us/previous-versions/azure/security/develop/security-code-analysis-overview, perhaps article author @TerryLanfear could help?
Starting: CredScan
==============================================================================
Task         : Credential Scanner
Description  : Scan source code for committed credentials
Version      : 2.336.0
Author       : Microsoft Corporation
Help         : [Extension Docs](https://aka.ms/mscadocs)
==============================================================================
Enabling TLS 1.2...
Initializing analysis environment...
Downloaded nuget.exe: D:\a\_sdt\nuget.exe
"D:\a\_sdt\nuget.exe" install Microsoft.Security.CredScan -Source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json -ConfigFile D:\a\_sdt\dt.nuget.config -NonInteractive
Feeds used:
  https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json

Installing package 'Microsoft.Security.CredScan' to 'D:\a\_sdt'.
Using credentials from config. UserName: VssSessionToken
Unable to load the service index for source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json.
  Response status code does not indicate success: 401 (Unauthorized).

Hello - MSCA is no longer supported and has been past end of life support since March 2022. Customers can gain support of our latest tooling through MSDO and GitHub Advanced Security for AzDO.


Convert menu icons to SVG

This code is an extension of @allcaps's #4464 that converts all icons in the main menu to SVG. All other icons in the admin are still loaded with the icon font.
Opening it as its own PR so I can see if the CI checks will pass. I've got the tests passing locally, but I want to ensure I didn't miss any edge cases.
This should not affect users of wagtailfontawesome at all, which is included in the bakery demo and still working when I test it locally.

To do:

[ ] Cross-browser testing
[ ] Per CodeCov, looks like we need some new tests
[ ] Update docs
[ ] Update changelog
[ ] ??? It's my first contribution to Wagtail; what am I missing? 😄

Thanks @Scotchester! I made a new label just for you :)

Adding the discussion from #4821 for future reference:

https://github.com/wagtail/wagtail/pull/4464#issue-180843464

This is a POC to componentise icons and make them screen-reader friendly using SVG and templates.
Related issues: #4463, #2349, #1224
Goals:

Wagtail icon font to svg
Insert icon via template tag
Way to hook in extra icons (your app or third party)
Way to override some icons (customisation)
Way to override all icons (icon packs)
Documentation
See if SVG icons need to be in the base template or can live in a external file/view.

This POC:

Convert Wagtail icon font to SVG symbols
Each symbol its own template. (easy overrides)
Add a hook to register new icons
Add templatetag inserting icons (DRY)
Add CSS to position icons
Add templatetag to load icons into the base template
Made small preperations for a view serving a icon sprite (as alternative to including all icons in the base template)

TODO:

Figure out if we want all icons each request OR that they should be served via a view (and set cache headers).
JS should also use the use-tag.
Provide an alternative for the most popular wagtail package: wagtailfontawesome
Add correct styling for drawer menu.
Remove icon fonts and icon CSS.
...

Test drive:
INSTALLED_APPS += [
    'wagtail.customapp',
    'wagtail.contrib.styleguide',
]

See settings => styleguide => icons. There are two sets. The icon font icons and the new SVG icons.
The wagtail.customapp inserts a custom icon and overrides an existing one.
The main menu and drawer have SVG-icons. (Some menu-items are replaced by JS and have the old icon font).

@thibaudcolas Ping! What do you think? Should we use a separate view for an icon sprite? OR is it okay to include all these icons in the base template?

https://github.com/wagtail/wagtail/pull/4464#issuecomment-380575587

@allcaps I think this is super duper amazing! Thank you for getting this started. I don't have much time to review this right now unfortunately, but I'd love to.
From the perspective of "getting this merged", the thing that's the least likely to get in as-is is the idify hack. It's not reliable enough to auto-convert class names to an icon identifier, we'll have to painstackingly refactor all of the existing icon call sites to refer to icons by name only.
Sorry I can't get a more thoughtful review – here are other things that come to mind:

Try to sync this work with https://github.com/wagtail/wagtail/pull/4381#pullrequestreview-110299442
If you want to help with that thankless refactoring of all icon call sites, have a look at https://github.com/wagtail/wagtail/issues/4199#issuecomment-379581195.
Is it really useful to be able to override all icons?

Rebased onto latest master. I'll be looking into the icon’s implementation over the next few weeks, for accessibility purposes. I’ll most likely only be changing the icon font implementation to be screen-reader-friendly, not doing the switch to SVG.

Worth adding https://www.sarasoueidan.com/blog/accessible-icon-buttons/ to the reading mix. Hopefully there will be useful tips and tricks in that article that can be applied to this PR

I ended up improving the current icon fonts implementation (#5359) instead of pursuing this SVG refactor. Got to experience some of the pain points of icon fonts, that show why this refactor is relevant:

When fonts fail to load, users see a wall of "failed to render" Unicode characters
Or they get unreliable characters from fallback fonts, https://www.zachleat.com/web/font-display-icon-fonts/ (thanks @zerolab)
The icons were really hard to update or even just rename, because of the .woff binary that has to be re-generated in Icomoon.

It’s especially problematic with the current implementation that icon classes are applied on arbitrary elements (instead of having a dedicated ), as this makes it harder to provide alternative text for them.

I've just rebased this PR on master.

Force-pushed the most recent commit, amended to correct a mistake I made in rebasing.

@thibaudcolas I've just noticed that the Draftail buttons use the Icon component, and are now quite broken 😆

I could use your advice on how to approach solving that.

@thibaudcolas I've just noticed that the Draftail buttons use the Icon component, and are now quite broken 😆

Fixed in 7680354.

Just a note for future reference that if we do go for an external SVG file we’ll need a polyfill for IE11 – https://github.com/jonathantneal/svg4everybody, or the simpler https://github.com/Keyamoon/svgxuse.

@thibaudcolas and @Scotchester
Let's get this one shipped! I've rebased this PR on master and did some clean-up.
I'll write documentation. Maybe we get better ideas about the backwards-compatibility and deprecation consequences once working with the new icons is clear.

I’ve tagged as "Needs Design Decision" so we discuss in a core team meeting whether this can be merged early without documentation or not.

@allcaps and @thibaudcolas I'm so sorry I've neglected this! I promise I will make time to review the latest updates and conversation tomorrow, before the core team meeting on Wednesday.

Yay @allcaps! I think this is really, really close. The only backwards-compatibility I have identified currently is with:
{% if not icon_name %}
       class="{{ classnames }}"
{% endif %}

If we remove that to keep class="{{ classnames }}" then I think that as this PR stands there shouldn’t be any other concerns. I think that if not might be something you added when this was based on the idify filter, and might not be relevant anymore.

Per my comment on the particular lines: Done!

I’ve picked up two small things while looking at this again – and one slightly bigger one: some of the ids for the new symbols would clash with existing ids used in Wagtail:
…
I’m sure we could easily rewrite that existing code to use different ids, but it might be easier to just prefix the id of all symbols with icon- to not have to worry about this as much?

Gooooood catch. I have a commit that could fix this for the given implementation, BUT it also ties in with the work I had in progress last  summer before it got dropped for months (which I apparently never commented on here, I think I may have just told you about it in person or over Slack, @thibaudcolas):
We can move the combined SVG markup for all the icons into an external SVG file that can be cached by browser and not bloat the markup of every page load in the admin. It would also conveniently sidestep this ID clashing problem.
The one downside is that it requires a JS polyfill for IE11 support. When I left off last summer, I recall having trouble getting the polyfill to work as expected, and in re-testing it tonight, the polyfill I was trying out (svgxuse) works well for IE 11, but seems overly aggressive in activating itself, even in modern browsers that support external use references. There are some more recently-updated alternatives to consider these days, such as SVG for Everybody and External SVG Polyfill.
If we want to take a little more time to test one or both of those and see if they're more reliable, we could avoid that id collision issue and use the less repetitive values for the icon_name property, but it would also be fine to fix the ID collisions with your reasonable suggestion of prefixing with icon-, go ahead with this PR, and then move the SVG code to its own file in a separate PR.
Let me know what you think.

The one downside is that it requires a JS polyfill for IE11 support.

I tired an external sprite but then the icons load after all other content is loaded. And this gives a nasty flash each page load.
An external sprite is a nice to have (and 90% implemented see deleted commits), but I'd prefer to keep it out of scope for now. Just get this merged.

I tired an external sprite but then the icons load after all other content is loaded. And this gives a nasty flash each page load.
An external sprite is a nice to have (and 90% implemented see deleted commits), but I'd prefer to keep it out of scope for now. Just get this merged.

I think that big delayed flash may have been due to the polyfill activating unnecessarily, if you were trying svgxuse like I was, but I agree that it's fine to keep further investigation out of this PR and move forward.

I’ve picked up two small things while looking at this again – and one slightly bigger one: some of the ids for the new symbols would clash with existing ids used in Wagtail:
…
I’m sure we could easily rewrite that existing code to use different ids, but it might be easier to just prefix the id of all symbols with icon- to not have to worry about this as much?

Gooooood catch. I have a commit that could fix this for the given implementation

Pushed this in https://github.com/wagtail/wagtail/pull/4821/commits/0391fe06468a149bc529084339149a55a33cde9f
Looks like it caused some test failures. I'll try to sort those out.

Wrap up
This PR add SVG icons to the Wagtail admin interface.
The new implementation addresses accessibility concerns. Adds title attribute and prevents problems with font rendering and screen readers.
This PR

All icon font icons converted to SVG symbols
All symbols added to skeleton.html to make them available in the ui.
Single icon html template icon.html
Single icon js component Icon.js
register_icons hook to manage icons (add, overide) wagtail/admin/wagtail_hooks.py
All icons in de admin interface use SVG
Icon fonts are still compatible. See for example bakery demo, it has both Wagtail SVG and wagtail-fontawesome.

Out of scope

Documentation how to add custom icons (keep it an internal feature for now).
Drop icon fonts. We stay backward compatible.
External sprite view to reduce page load. Needs poly fill to accommodate IE11. Is the next thing to tackle.

@thibaudcolas / @allcaps - is this an appropriate commit message? I am attempting to sum everything up.
Add SVG Icons and include in admin menu
* This commit only covers the migration of the icons in the menu and draftail editor. All
other admin menu icons remain implemented as before.
* Existing font based icon support still exists.
* Convert menu icons to SVG
* This could be considered a breaking change for any Wagtail sites or
packages that are leveraging Wagtail's Button and Icon React components.
* Remove references to unused `submenu-trigger` class
* Fix size of icons in Draftail toolbar
* Fix size of link icons in Draftail editor
* Restore output of classnames on menu items at all times
* Prefix icon `id`s with `icon-` to prevent `id` collisions
* Add hooks support (not yet documented) for adding custom icons

@lb- Thank you for the review.

Fix size of icons in Draftail toolbar
Fix size of link icons in Draftail editor

Can be removed. The SVG icons  are visually the same as before. So no real change here.

Restore output of classnames on menu items at all times

Can be removed. Classnames where dropped and brought it back in. So no real change here.

Merged in via eed16e00348c6ddfe8f997e1150006a3211a1216
Thanks for the amazing work on this @Scotchester @allcaps  & @thibaudcolas
Note: I have not closed any of the related issues mentioned here https://github.com/wagtail/wagtail/pull/4821#issuecomment-433686197 as it appears they are not fully resolved as of this initial work.


Working with dynatrace_iam_policy and dynatrace_iam_policy_bindings resources (SaaS)

Describe the bug
Cannot export dynatrace_iam_policy and dynatrace_iam_policy_bindings resources using the Export Utility
To Reproduce
Configure OAuth Client (and Service User) with the following permissions:

account-env-read
account-env-write
account-idm-read
account-idm-write
iam-policies-management
iam:bindings:read
iam:bindings:write
iam:effective-permissions:read
iam:policies:read
iam:policies:write

Configure environment variables with appropriate values:

DYNATRACE_ENV_URL
DYNATRACE_TARGET_FOLDER
DT_CLIENT_ID
DT_CLIENT_SECRET
DT_ACCOUNT_ID

Execute:
./terraform-provider-dynatrace -export -ref -id dynatrace_iam_policy dynatrace_iam_policy_bindings
Observe output:

Downloading "dynatrace_iam_policy"
Downloading "dynatrace_iam_policy_bindings"
Post-Processing Resources ...
Writing resources.tf
Writing datasources.tf
Writing main.tf
Writing variables.tf
Writing providers.tf
Executing 'terraform init'

Observe that there's no modules folder, no iam_policy module, no iam_policy_bindings module, and no resources downloaded.
Expected behavior
All dynatrace_iam_policy and dynatrace_iam_policy_bindings resources to be exported/downloaded.
Desktop (please complete the following information):

OS: macOS Sonoma 14.0
Version 1.47.2

Additional context
I've validated that my OAuth Client/Service user has the right permissions working with the Dynatrace Account Management API directly and can retrieve global, account, and environment policies OK.

Configuring the following environment variables:

DYNATRACE_DEBUG=true
DYNATRACE_LOG_HTTP=terraform-provider-dynatrace.http.log
DYNATRACE_HTTP_RESPONSE=true

Results in a log of:

2023/12/01 03:24:48 [DISCOVER] [dynatrace_iam_policy] 0 items found.
2023/12/01 03:24:48 [DISCOVER] [dynatrace_iam_policy_bindings] 0 items found.

Hi @gitFurious,
Our apologies, looks like the IAM policy and policy bindings export functionality was never implemented but the documentation stated otherwise. The export feature will now be available for the two resources in the next release.
Thanks!


logging tweaks

more fine grained configuration of connection logging
replace ~exn with ": %S" (Printexc.to_string exn)

addresses #183


Operands with periodically repeating rows/columns for faster testing

iree-amd-aie would like to run large matmul tests in CI. To make this feasible (not too slow), the calculation of the correct values on CPU needs to be significantly faster. I have tried improving the algorithm implemented in IREE (M-, N-, K- tiling) but the speedups are not significant enough. This PR takes a different approach: it makes the baseline calculation faster by forcing the matrices being multiplied to have a specific structure which can be taken advantage of. Specifically, LHS (RHS) has periodically repeating (rows) columns.
iree-amd-aie uses
https://github.com/iree-org/iree/blob/main/tools/testing/e2e/iree-e2e-matmul-test.cc but does not use
https://github.com/iree-org/iree/blame/main/tests/e2e/matmul/generate_e2e_matmul_tests.py -- it has it's own version of this file
https://github.com/nod-ai/iree-amd-aie/blob/main/tests/matmul/generate_e2e_matmul_tests.py which is modified is this PR:
https://github.com/nod-ai/iree-amd-aie/pull/321
Currently this IREE PR does not have testing (I will add) but the corresponding iree-amd-aie PR above shows how this IREE PR works end-to-end.

Maybe if you're fine with repeating values you could also just run smaller matmuls?

+1. Can you change the sizes you are testing or shard the tests across multiple threads / runners?

My thinking is that if the period of repetition is a largish prime number (93 say) then we'd have to be incredibly unlucky to let a bug through. It would require that the implementation being tested reads from row r-k*93 for some k, instead of row r. That's not impossible, and you could argue that just having the possibility of a bug slipping through will be hanging over us and make us sleep less easily, but it seems like a pragmatic solution.

Maybe if you're fine with repeating values you could also just run smaller matmuls?

The current backend compiler stack is fragile, and it's definitely not case that if m=n=k=128 passes a numerical test, that is any guarantee that m=n=k=256 will pass.
The current generation of AIE has ~4 teraops of compute, and that's going to go up dramatically. Back of the envelope suggests that the performance of CPU for bfloat16 or int8 matmul is ~40 gops, so 100x gap even if the reference performance is improved.
All that said, I agree it makes sense to start with at least making the reference implementation decent.

Good point - sounds reasonable. But yeah, let's make the impl cleaner first before it gets too complex for anyone to reverse engineer and improve later on :)

That makes sense to me. I will have a go at making the matmul faster when I have time

Do you think it would be possible to have an option to use llvm-cpu backend for the reference matmul? We could then use llvm-cpu (which would need to be tested on a different path) to bootstrap new backends.

There seems to be some aversion to C++ (see https://github.com/iree-org/iree/blob/c1cfbfc48f0abb07ff2cfd6335eeb541097acda2/tools/testing/e2e/iree-e2e-matmul-test.cc#L599) in some parts of IREE... but would it be ok to use C++ templates for a reference matmul instead of macros (might be cleaner) ?

Nah we don't want to use codegen for the reference - that prevents us from running the test on devices that may not have LLVM CPU support, etc and makes it significantly more complex to understand what it's doing. The justification for having the tool is that it'd be simple, self-contained, and easy to debug so it's important we stick with that.
As a general rule of thumb any tool designed to run on target devices is written in C so that it runs anywhere IREE can run (and for consistency in the codebase) - but we aren't very strict with that for test-only tools. The only reason this tool includes C++ is because I was lazy wiring up the VM module but I wanted to keep the option of taking it back to C. I'm not sure I care about it strongly in this particular case, though, and if templates allow for avoiding more complexity in the reference impl that seems like it's worth it. I still wouldn't blindly convert the file, though, as people tend to use it as a reference for how to use the IREE C API and that gets obscured if everything gets all C++-ified.
In general though this tool shouldn't be on the critical path or very expensive - it's meant for unit testing matmul implementations and not benchmarking. The check-every flag usually keeps it pretty fast in cases where things match. Getting traces and using that to optimize things would be useful if you're noticing it take awhile.

The check-every flag usually keeps it pretty fast in cases where things match.

I kind of overlooked the check-every flag when I first looked at this code. It seems risky having check-every as anything but an explicit opt-in option (it's currently not even something we can opt-out of).  I am running a matmul with m=n=2304 and the check_every is chosen here to be 531... I'm slightly terrified now that none of our large matmuls work!
My current plan is

make check-every a user specifiable flag. Or maybe max-number-of-checks (from which check-every is calculated).
make matmul faster (by honest means)
revisit this PR.

Please let me know if that sounds reasonable (@benvanik @ScottTodd)

--max_elements_to_check=0 does what you suggest I think? https://github.com/iree-org/iree/blob/8ae8aafb827419ce261ba43af5d9b1277049e3cb/tools/testing/e2e/test_utils.c#L40-L47

--max_elements_to_check=0 does what you suggest I think?
https://github.com/iree-org/iree/blob/8ae8aafb827419ce261ba43af5d9b1277049e3cb/tools/testing/e2e/test_utils.c#L40-L47

Thanks!


V11 problems I found

[ ] Suddenly the journal was missing three sessions of changes.
[ ] Any changes to the actors seemed to exist.
[ ] No actor images could be changed.

[ ]  Suddenly the journal was missing three sessions of changes.
[ ]  Any changes to the actors seemed to exist.

This happened when you updated FoundryVTT from 10 to 11 and migrated the world, or under some other circumstance? I've been playing with the system in v11 for over a month and I haven't seen this happen.

As I read that again I realized how bad error report that was. So I did it again on my test server, first having a save from my V10 game exported one of the actors. Upgraded to V11 and did it again. Both json-files are present in the zip-file connected to this message.
If you need access to my test V11 game just let me know and I will send it to you. My test game is totally seperated from my true game so...
export files - fvtt-Actor-maggi-silva.zip
What happens is that the character seems to have lost the past 3 sessions of data from the journal. Which would mean some items aren't transferred and this is true for all actors.
Also as you click on the actor's image to change the image nothing happens - no error, no nothing. I checked the html-code but it is the same as in my own system so I can't really understand what is the problem there. Creating a new actor doesn't fix this, but all actors new and old have this problem.

Here is the log from Foundry from during my update:
{"level":"info","message":"Running on Node.js - Version 16.15.0","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Foundry Virtual Tabletop - Version 10 Build 291","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"User Data Directory - "C:/FoundryVTT"","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Application Options:\n{\n  "port": 30000,\n  "upnp": true,\n  "fullscreen": false,\n  "hostname": null,\n  "localHostname": null,\n  "routePrefix": null,\n  "sslCert": null,\n  "sslKey": null,\n  "awsConfig": null,\n  "passwordSalt": null,\n  "proxySSL": false,\n  "proxyPort": null,\n  "serviceConfig": null,\n  "updateChannel": "stable",\n  "language": "en.core",\n  "upnpLeaseDuration": null,\n  "compressStatic": true,\n  "world": null,\n  "protocol": null,\n  "adminPassword": "••••••••••••••••"\n}","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Software license verification succeeded","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Requesting UPnP port forwarding to destination port 30000","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Running Electron application with version 20.1.0 using Chromium 104.0.5112.102","timestamp":"2023-06-26 07:58:21"}
{"level":"info","message":"Server started and listening on port 30000","timestamp":"2023-06-26 07:58:22"}
{"level":"info","message":"Created client session dd07a99cf991100032bce632","timestamp":"2023-06-26 07:58:26"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using "author" which is deprecated in favor of "authors"\nDeprecated since Version 9\nBackwards-compatible support will be removed in Version 11","timestamp":"2023-06-26 07:58:26"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains dependencies using "name" which is deprecated in favor of "id"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:26"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains "dependencies" which is deprecated in favor of "relationships.requires"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:26"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using the old flat core compatibility fields which are deprecated in favor of the new "compatibility" object\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:26"}
{"level":"warn","message":"The module "super-select" is using "author" which is deprecated in favor of "authors"\nDeprecated since Version 9\nBackwards-compatible support will be removed in Version 11","timestamp":"2023-06-26 07:58:26"}
{"level":"info","message":"Administrator authentication successful for session dd07a99cf991100032bce632","timestamp":"2023-06-26 07:58:31"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using "author" which is deprecated in favor of "authors"\nDeprecated since Version 9\nBackwards-compatible support will be removed in Version 11","timestamp":"2023-06-26 07:58:47"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains dependencies using "name" which is deprecated in favor of "id"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:47"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains "dependencies" which is deprecated in favor of "relationships.requires"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:47"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using the old flat core compatibility fields which are deprecated in favor of the new "compatibility" object\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 07:58:47"}
{"level":"warn","message":"The module "super-select" is using "author" which is deprecated in favor of "authors"\nDeprecated since Version 9\nBackwards-compatible support will be removed in Version 11","timestamp":"2023-06-26 07:58:47"}
{"ip":"::1","level":"info","message":"User authentication successful for user Gamemaster","session":"dd07a99cf991100032bce632","timestamp":"2023-06-26 07:58:53"}
{"level":"info","message":"No system update for Genesys is currently available.","timestamp":"2023-06-26 07:58:56"}
{"level":"info","message":"Vended World data to User [kspBdlaIOQD60l5s] in 1636ms","timestamp":"2023-06-26 07:58:56"}
{"level":"info","message":"Shutting down Foundry Virtual Tabletop server","timestamp":"2023-06-26 07:59:25"}
{"level":"info","message":"Shut-down success. Goodbye!","timestamp":"2023-06-26 07:59:25"}
{"level":"info","message":"Running on Node.js - Version 18.12.1","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Foundry Virtual Tabletop - Version 11 Build 302","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"User Data Directory - "C:/FoundryVTT"","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Application Options:\n{\n  "port": 30000,\n  "upnp": true,\n  "fullscreen": false,\n  "hostname": null,\n  "localHostname": null,\n  "routePrefix": null,\n  "sslCert": null,\n  "sslKey": null,\n  "awsConfig": null,\n  "passwordSalt": null,\n  "proxySSL": false,\n  "proxyPort": null,\n  "serviceConfig": null,\n  "updateChannel": "stable",\n  "language": "en.core",\n  "upnpLeaseDuration": null,\n  "compressStatic": true,\n  "world": null,\n  "compressSocket": true,\n  "cssTheme": "foundry",\n  "deleteNEDB": false,\n  "hotReload": false,\n  "protocol": null,\n  "telemetry": true,\n  "adminPassword": "••••••••••••••••"\n}","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Software license verification succeeded","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Requesting UPnP port forwarding to destination port 30000","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Running Electron application with version 23.2.3 using Chromium 110.0.5481.208","timestamp":"2023-06-26 08:01:44"}
{"level":"info","message":"Server started and listening on port 30000","timestamp":"2023-06-26 08:01:45"}
{"level":"info","message":"Created client session 44bd3b4ddf2ef7e4720e9113","timestamp":"2023-06-26 08:01:49"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains dependencies using "name" which is deprecated in favor of "id"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:01:49"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains "dependencies" which is deprecated in favor of "relationships.requires"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:01:49"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using the old flat core compatibility fields which are deprecated in favor of the new "compatibility" object\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:01:49"}
{"level":"warn","message":"module "dice-so-nice" declares media.link which is unsupported, media.url should be used\nDeprecated since Version 11\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:01:49"}
{"level":"info","message":"Administrator authentication successful for session 44bd3b4ddf2ef7e4720e9113","timestamp":"2023-06-26 08:01:53"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains dependencies using "name" which is deprecated in favor of "id"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:02:02"}
{"level":"warn","message":"The module "Custom-Token-Animations" contains "dependencies" which is deprecated in favor of "relationships.requires"\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:02:02"}
{"level":"warn","message":"The module "Custom-Token-Animations" is using the old flat core compatibility fields which are deprecated in favor of the new "compatibility" object\nDeprecated since Version 10\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:02:02"}
{"level":"warn","message":"module "dice-so-nice" declares media.link which is unsupported, media.url should be used\nDeprecated since Version 11\nBackwards-compatible support will be removed in Version 13","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "actors"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "cards"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "messages"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "combats"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "drawings"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "fog"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "folders"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "items"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "journal"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "macros"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "playlists"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "tables"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "scenes"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "settings"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "users"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"Launching World peris-rho in Safe Mode","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Created Setting with id [dVF1rQ5TAsvviG0m]","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "genesys.crb-skills"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Connected to database "world.game-skills"","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"Migrating World peris-rho to updated core platform 11.302","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"Core platform migrations for World peris-rho to version 11.302 completed successfully","timestamp":"2023-06-26 08:02:02"}
{"level":"info","message":"FoundryVTT | Created 0 Folder documents with ids: []","timestamp":"2023-06-26 08:02:02"}
{"ip":"::1","level":"info","message":"User authentication successful for user Gamemaster","session":"44bd3b4ddf2ef7e4720e9113","timestamp":"2023-06-26 08:02:07"}
{"level":"info","message":"No system update for Genesys is currently available.","timestamp":"2023-06-26 08:02:08"}
{"level":"info","message":"Vended World data to User [kspBdlaIOQD60l5s] in 601ms","timestamp":"2023-06-26 08:02:08"}
{"level":"info","message":"FoundryVTT | Created ChatMessage with id [cLvEuAjXuLJkxakC]","timestamp":"2023-06-26 08:02:09"}


Wasm cross-platform support

I'm want to compile a C++ library that uses grpc to WASM (Web Assembly) using Emscripten (Upstream) + CMake (3.18.0)
I've managed to compile the grpc library itself after patching (hacking) a little bit of code to prevent grpc from using some features that don't exist (as far as I can tell) in WASM.
 Also feel free to pop in and convince me that what I'm doing doesn't make sense (I'll use it in production eventually)
EDIT: The hello world example fails with this error code when launching greeter_server - RuntimeError: abort(CompileError: AsyncCompile: Wasm decoding failed: unexpected section: Code @+37085)
Thanks in advance

This looks like a pretty fundamental issue, like the wasm file produced by emscripten is not valid.  Lets follow up on emscripten-core/emscripten#12257.

Updating after getting some help in the Emscripten repo.
Now the server starts running but I get another error.
I intend to continue investigating, so feel free to leave this issue open and I'll update here on my progress.
node --experimental-wasm-threads --experimental-worker --experimental-wasm-bulk-memory greeter_server.js
E0919 20:05:53.487000000  632752 cpu_posix.cc:41]                      Cannot determine number of CPUs: assuming 1
E0919 20:05:53.504000000  632752 socket_utils_common_posix.cc:223]     check for SO_REUSEPORT: {"created":"@1600535153.504000000","description":"Protocol not available","errno":50,"file":"~/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":198,"os_error":"Protocol not available","syscall":"setsockopt(SO_REUSEPORT)"}
E0919 20:05:53.506000000  632752 server_chttp2.cc:40]                  {"created":"@1600535153.505000000","description":"No address added out of total 1 resolved","file":"~/grpc/src/core/ext/transport/chttp2/server/chttp2_server.cc","file_line":307,"referenced_errors":[{"created":"@1600535153.505000000","description":"Failed to add any wildcard listeners","file":"~/grpc/src/core/lib/iomgr/tcp_server_posix.cc","file_line":341,"referenced_errors":[{"created":"@1600535153.505000000","description":"Unable to configure socket","fd":3,"file":"~/grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":215,"referenced_errors":[{"created":"@1600535153.505000000","description":"Protocol not available","errno":50,"file":"~/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":239,"os_error":"Protocol not available","syscall":"setsockopt(TCP_NODELAY)"}]},{"created":"@1600535153.505000000","description":"Unable to configure socket","fd":3,"file":"~/grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":215,"referenced_errors":[{"created":"@1600535153.505000000","description":"Protocol not available","errno":50,"file":"~/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":239,"os_error":"Protocol not available","syscall":"setsockopt(TCP_NODELAY)"}]}]}]}
Server listening on <IP_ADDRESS>:50051
exception thrown: RuntimeError: memory access out of bounds,RuntimeError: memory access out of bounds
    at <anonymous>:wasm-function[61]:0x9d26
    at main (<anonymous>:wasm-function[63]:0x9e6f)
    at ~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:26530
    at callMain (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:211052)
    at doRun (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:211649)
    at run (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:211821)
    at runCaller (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:210458)
    at removeRunDependency (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:25341)
    at receiveInstance (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:27553)
    at receiveInstantiatedSource (~/grpc/examples/cpp/helloworld/cmake/build/greeter_server.js:1:27883)

Updating again, I hacked into grpc code again and disabled additional socket features - SO_REUSEADDR, SO_REUSEPORT, and TCP_NODELAY. Now the code runs without errors but Stub->SayHello (using greeter_client.cc) never returns.
I used Wireshark to sniff the loopback device and I didn't see and network activity initiated by the wasm greeter client.
Due to the limited debugging in WASM I'm not sure what will be the best approach to narrowing done what's the problem on the grpc side of things (besides inserting prints in the grpc code and waiting a couple of minutes between compile times).
Since the support seems experimental at best, I've decided against using grpc within WASM at the moment. If you need anything further from me than please let me know.

Seems like this is not being actively worked on at the moment, so I'm going to close it.  Feel free to file a new issue if you need something else.

Updating again, I hacked into grpc code again and disabled additional socket features - SO_REUSEADDR, SO_REUSEPORT, and TCP_NODELAY. Now the code runs without errors but Stub->SayHello (using greeter_client.cc) never returns. I used Wireshark to sniff the loopback device and I didn't see and network activity initiated by the wasm greeter client. Due to the limited debugging in WASM I'm not sure what will be the best approach to narrowing done what's the problem on the grpc side of things (besides inserting prints in the grpc code and waiting a couple of minutes between compile times). Since the support seems experimental at best, I've decided against using grpc within WASM at the moment. If you need anything further from me than please let me know.

I'm trying to compile gRPC with Web WASM with Emscripten, but it keeps giving errors.
I wonder if you could do it?
Thanks.

Are there any plans to add support for WASM support. I'm currently investigating if we can run CuraEngine (the slicing engine of UltiMaker Cura) client-side using WASM.


Fix typo in titanium code. Only try JSONP if not titanium.

@wei-lee As requested - on new branch, as not sure what's going on with dist not being included in that branch.

@cianclarke  the generated files are not saved in the repo anymore - they will be created automatically by travis when a tag is created and upload to Github releases.


foreman start does not handle SIGTERM correctly

I have encountered this issue in both Mac os X Lion and an ubuntu server (on which I was manually running foreman start).
I have the following over-simple Procfile
web:    export RAILS_ENV=production; bundle exec rails server thin -p $PORT
worker: export RAILS_ENV=production; bundle exec rake jobs:work

This produces a number of processes including rails s thin, which is managed by the parent process (the one launched by foreman start).
Then I just press CTRL-C, which stops foreman, but then I can observe the child process still running when inspecting it with ps -ef.
It looks like foreman is not properly SIGTERming its child processes when it is SIGTERMed itself.

I have the same issue when working with rescue workers. My Procfile looks like this:
web: bundle exec thin start -p $PORT
resque-web: resque-web -s thin -p 9999 -L -F
worker_lo: bundle exec rake resque:workers QUEUE="high,med,low" COUNT=5 VERBOSE=1
worker_hi: bundle exec rake resque:workers VERBOSE=1 QUEUE="critical" COUNT=5
scheduler: bundle exec rake resque:scheduler VERBOSE=1
After sending foreman a ctrl-c, I still have all rescue worker processes running and need to manually kill them. I also tried the suggestion above (using env), with no success. Also the thin server ("web" task) tries to restart when receiving the signal SIGTERM (instead of terminating), which results in an error message.
^CSIGINT received
12:25:46 system        | sending SIGTERM to all processes
[...]
12:25:46 worker_lo.1   | rake aborted!
12:25:46 worker_lo.1   | SIGHUP
12:25:46 worker_lo.1   |
12:25:46 worker_lo.1   | Tasks: TOP => resque:work
12:25:46 worker_lo.1   | (See full trace by running task with --trace)
12:25:46 worker_hi.1   | rake aborted!
12:25:46 worker_hi.1   | SIGHUP
12:25:46 worker_hi.1   |
12:25:46 worker_hi.1   | Tasks: TOP => resque:work
12:25:46 worker_hi.1   | (See full trace by running task with --trace)
[...]
12:25:46 web.1         | >> Restarting ...
12:25:47 web.1         | >> Using rack adapter
12:25:47 web.1         | >> Thin web server (v1.2.11 codename Bat-Shit Crazy)
12:25:47 web.1         | >> Maximum connections set to 1024
12:25:47 web.1         | >> Listening on <IP_ADDRESS>:5000, CTRL+C to stop
12:25:47 web.1         | /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in start_tcp_server': no acceptor (RuntimeError) 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:572:in start_server'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/backends/tcp_server.rb:16:in connect' 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/backends/base.rb:53:in block in start'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in call' 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in run_machine'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in run' 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/backends/base.rb:61:in start'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/server.rb:159:in start' 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/controllers/controller.rb:86:in start'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/runner.rb:185:in run_command' 12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/lib/thin/runner.rb:151:in run!'
12:25:47 web.1         | 	from /usr/local/lib/ruby/gems/1.9.1/gems/thin-1.2.11/bin/thin:6:in <top (required)>' 12:25:47 web.1         | 	from /usr/local/bin/thin:19:in load'
12:25:47 web.1         | 	from /usr/local/bin/thin:19:in `'
12:25:47 web.1         | process exiting


URLSearchParams not accept number as a value

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
The URLSearchParams only accepts a Record<string, string>, but a number can be accepted for a value without any problems, why not use a Record<string, string | number>, I think this can be more friendly to not force to use a bunch of type casts in code.
If this is ok, I can make this contribuition.

Duplicate of #43738.

sorry, thaks for reply.


Add line about csharp.unitTestDebuggingOptions.type option to changelog

I'm going to go ahead and merge this. Let me know if you spot anything and I'll fix it up later.

@DustinCampbell LGTM


Exception in _handle_event when dispatching

Describe the bug
Issues with plugin updates, log exception
To Reproduce
Steps to reproduce the behavior:

Restart HA
Look at home-assistant.log

Expected behavior
Plugin always working and log clean
Screenshots
If applicable, add screenshots to help explain your problem.
System details

Home-assistant (version): 0.109.5
Hassio (Yes/No): No
alexa_media  (version from const.py or HA startup): v2.7.0
alexapy (version from pip show alexapy or HA startup):

Logs
Please provide logs. We'll be most likely asking for them anyway.
2020-05-10 13:52:31 ERROR (MainThread) [homeassistant.util.logging] Exception in _handle_event when dispatching 'alexa_media_s*************i@g***': ({'player_state': {'destinationUserId': 'xxxxxxxxxxxxxxx', 'dopplerId': {'deviceType': 'xxxxxxxxxxxxxxxx', 'deviceSerialNumber': 'xxxxxxxxxxxxxx'}, 'bass': 0, 'midrange': 0, 'treble': 0}},)
Traceback (most recent call last):
  File "/config/custom_components/alexa_media/media_player.py", line 381, in _handle_event
    await _refresh_if_no_audiopush(already_refreshed)
  File "/config/custom_components/alexa_media/media_player.py", line 271, in _refresh_if_no_audiopush
    await self.async_update()
  File "/config/custom_components/alexa_media/helpers.py", line 148, in wrapper
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/media_player.py", line 769, in async_update
    device, no_throttle=True
  File "/config/custom_components/alexa_media/helpers.py", line 148, in wrapper
    result = await func(*args, **kwargs)
  File "/config/custom_components/alexa_media/media_player.py", line 532, in refresh
    session = await self.alexa_api.get_state()
  File "/usr/local/lib/python3.7/site-packages/alexapy/alexaapi.py", line 687, in get_state
    return await response.json(content_type=None)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 1040, in json
    return loads(stripped.decode(encoding))
  File "/usr/local/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.7/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Additional context
Add any other context about the problem here.

Thanks. Work around would be to refresh your cookie. It's being rejected. But we'll need to catch this error.

Anything I can do to help debugging before refreshing ?
Is disable/enable plugin the only and best way to refresh ?
Simone

Thanks but no, that's enough info for me to track this error down. Rename your .pickle file. It's in your config/.storage/ directory.

@keatontaylor I think I need your eyes on this. This should already be caught by the wrapper _catch_all_exceptions in AlexaAPI but for some reason it isn't. I think the issue may be caused by the fact the async call is dispatched? But I'm not that familiar with that level of python. Any thoughts?


Make compelling demo script

Ideally it should show us doing something complex, in few steps:

initializing an app
Searching for a prototype that does something complex, maybe instantiates a service and a deployment
Customize
Create 2 environments
diff between them
Deploy to dev

Closing this for the demo script work @abiogenesis-now has completed.


Update to Enigma 2.0

Depends on QuiltMC/enigma#168

we should change the package to enigma_plugin to match conventions


how to use vue table

I gone through documentation and tried to use ratiw/vue-table , everytime failed from last three days.can u guide me how i will use vue-table on npm.

@AnguruMona Look into the example first and state your problem clearly. It's just another NPM package, If you're not familiar with NPM, try the javascript version as in the example first.

i used the command  npm install vuetable
this my table.vue
`

List of Users

and this is my main.js
import Router from 'vue-router'
import Resource from 'vue-resource'
import VueFilter from 'vue-filter'
import  vuetable from 'vuetable'
import VuetablePagination from 'VuetablePagination'
import VuetablePaginationDropdown from 'VuetablePaginationDropdown'
import App from './App.vue'
import tabledata from './components/table.vue'
var Vue = require('vue');
Vue.use(vuetable)
Vue.use(Router)
Vue.use(Resource)
Vue.use(VueFilter)
Vue.use(VuetablePaginationDropdown)
Vue.use(VuetablePagination)
// routing
var router = new Router()
router.map({
'/commitDetails':{
component:tabledata
}
})
router.start(App, '#app')
`
i included
data is not displaying and getting warning message :
1.The "data" option should be a function that returns a per-instance value in component definitions
2. Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.
can u tell where i did mistake ?

i used command  npm install vuetable
this my table.vue

and this is my main.js
import Router from 'vue-router'
import Resource from 'vue-resource'
import VueFilter from 'vue-filter'
import  vuetable from 'vuetable'
import VuetablePagination from 'VuetablePagination'
import VuetablePaginationDropdown from 'VuetablePaginationDropdown'
import App from './App.vue'
import tabledata from './components/table.vue'
var Vue = require('vue');
Vue.use(vuetable)
Vue.use(Router)
Vue.use(Resource)
Vue.use(VueFilter)
Vue.use(VuetablePaginationDropdown)
Vue.use(VuetablePagination)
// routing
var router = new Router()
router.map({
'/commitDetails':{
component:tabledata
}
})
router.start(App, '#app')
i included
data is not displaying and getting warning message :
1.The "data" option should be a function that returns a per-instance value in component definitions
2. Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.
can u tell where i did mistake ?

i used command  npm install vuetable
this is my main.js
import Router from 'vue-router'
import Resource from 'vue-resource'
import VueFilter from 'vue-filter'
import  vuetable from 'vuetable'
import VuetablePagination from 'VuetablePagination'
import VuetablePaginationDropdown from 'VuetablePaginationDropdown'
import App from './App.vue'
import tabledata from './components/table.vue'
var Vue = require('vue');
Vue.use(vuetable)
Vue.use(Router)
Vue.use(Resource)
Vue.use(VueFilter)
Vue.use(VuetablePaginationDropdown)
Vue.use(VuetablePagination)
// routing
var router = new Router()
router.map({
'/commitDetails':{
component:tabledata
}
})
router.start(App, '#app')
and this is my template

data is not displaying and getting warning message :
1.The "data" option should be a function that returns a per-instance value in component definitions
2. Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.
can u tell where i did mistake ?

@AnguruMona 'vuetableis not a plugin, you don't have toVue.use(...)` it.
When using npm, you should import from src/components directory, like so.
import vuetable from 'vuetable/src/components/Vuetable.vue'
import VuetablePagination from 'vuetable/src/components/VuetablePagination.vue'
import VuetablePaginationDropdown from 'vuetable/src/components/VuetablePaginationDropdown.vue'

First of Thank U so Much.
Can u have look this file.
Pls tell me if i did any mistake
Vue.zip

@AnguruMona Sorry, you should put it in github. I would look into the source code, when I have time.
But it looks like you're using Vue 2.0, aren't you? If so, this version is not compatible with Vue 2.0.

I am using  Vue 2.4.0 .is it compatible or not

@AnguruMona Nope, it's only working with Vue 1.x.
vuetable 2 will be released after the stable version of Vue 2.0 is released.

Thank u so much


Unsupported Redmine version for version > v5

If upgrading to a newer version than 4.2.11, the container throws the following message:
ERROR: Unsupported Redmine version (5.0.6)
ERROR: Unsupported Redmine version (5.1.0)
The upgrade seems not be fully implemented.

https://github.com/sameersbn/docker-redmine/blob/91c789af059ab63d9f1152b16565562c3ff9d9e3/assets/runtime/functions#L491
I think here version 5 should be added

Good catch

Fixed in 5.0.7-1 and 5.1.1


Supress ProgressAction parameter from New-MarkdownHelp output

Summary of the new feature / enhancement
Typically, I run New-MarkdownHelp (v14.2) in PowerShell 5.1x. I recently had occasion to run it in PowerShell 7.4.3. When I did, every cmdlet got a new ProgressAction parameter. According to about_CommonParameters, ProgressAction is a common parameter like Debug or Verbose. Unclear why only that common parameter is getting added to cmdlet articles.
Proposed technical implementation details (optional)
ProgressAction doesn't need to appear in the output of New-MarkdownHelp. This issue might be similar to the AsJob parameter as described in #339 (although AsJob was related to remote PowerShell).

I tried forking and building from source but was having issues getting it done. Anyways, re:

Unclear why only that common parameter is getting added to cmdlet articles

See:
https://github.com/PowerShell/platyPS/blob/f9fa12821b6dbacdd16cc486b77787cdc51242fa/src/platyPS/platyPS.psm1#L2530-L2547
It's hard coded. Wouldn't something like this be future proof:
if ([System.Management.Automation.PSCmdlet]::CommonParameters.Contains($parameterName) -or
    [System.Management.Automation.PSCmdlet]::OptionalCommonParameters.Contains($parameterName)) {
       return true;
 }

I believe this is being addressed in this PR I would love to get a new release with this fix.


Start loading wait"1" immediately after all with wait"0" loaded?

Is your feature request related to a problem? Please describe.
I do not see much use case for any numeric values of wait modifier other than wait"0".
For now zplugin with different wait values would:

first set the prompt (and other immediate stuff to set up)
synchronously load plugins with wait"0" ice modifier in the order specified in config
wait up to 1 second
load plugins (if any) with wait"1" modifier
... and so on

As I see it, I think wait is expected to be used to specify the order rather then the exact number of seconds to wait before loading.
Describe the solution you'd like
As wait"0" means "immediately after prompt load", it might be more convenient to define wait"1" as "immediately after all plugins with wait"0" loaded".
This would let the user to have his configuration fully loaded as fast as possible while preserving the desired order.

That's an interesting idea. Currently, there is an automatic division of a single time-slot wait'X' – maximum of 20 events will get executed, the remaining ones will be deferred to the next time-slot.
But the idea means something different. It means to divide single time-slot into multiple event-firing sessions. This way, the prompt would not block even for large number of events in them in total.
That's an interesting, actually a ground-breaking change that would help to deliver the promise of loading in background, without interference. I'll have to think about it for a little (it seems to be completely doable at first sight) and find time to implement it.

Almost an miracle resolution – the automatic division now re-schedules the events to be run immediately after the current firing-session. In other words:

a fact: the prompt is being blocked inside a single firing session,
by re-scheduling the events into another firing-session we volunteer CPU time to the prompt – the prompt is being active in between the sessions
the new firing-session is being run instantly after the current one, so there is no gap and the events are being fired continuously

I've lowered the automatic-dividing number of events to 5. So in another words: the prompt is being activated after each 5 events automatically.

I updated zplugin, but I don't really notice the difference, heh.
Let me illustrate what I envisioned. Consider the following made-up code:
mkdir -p "${HOME}/.zplugin/plugins/_local---null" >/dev/null
zplugin ice lucid wait"0" atload"echo Wave 0 plugin 00"; zload _local/null
zplugin ice lucid wait"1" atload"echo Wave 1 plugin 10"; zload _local/null
zplugin ice lucid wait"1" atload"echo Wave 1 plugin 11"; zload _local/null
zplugin ice lucid wait"2" atload"echo Wave 2 plugin 20"; zload _local/null
zplugin ice lucid wait"2" atload"echo Wave 2 plugin 21"; zload _local/null
zplugin ice lucid wait"3" atload"echo Wave 3 plugin 30"; zload _local/null
zplugin ice lucid wait"3" atload"echo Wave 3 plugin 31"; zload _local/null

The code is loaded in about 3 seconds, while it probably could be load almost instantly (if we see 'wait' modifier as a purely setting the order rather than time in seconds).
In the code ^ the user specifies, that he wants plugins 1X be loaded strictly before plugins 2X, for example.
While the order of inside the "wave" (the time slot, as you call it) is probably not that important and might change when the user rearranges the lines.
Here is the reason why I think the order of loading should not be set by the order of the lines: the user will probably choose to have commands and their completions be located close to one another in his zshrc, while still being loaded in different waves (time slots), e.g.:
zplugin ice wait"1" ... ; zplugin load <some_commands>
zplugin ice wait"0" ... ; zplugin snippet <the_commands_completions>

As I understand the changes you made - is that now zplugin re-draws the prompt more frequently (every 5 (why not every 1, by the way?) loaded plugins instead of every 20) in between loading the plugins. Which is nice, but not the exact thing I meant. However, I'm confused by this statement

the new firing-session is being run instantly after the current one, so there is no gap and the events are still being fired continuously

as the code I listed loades in 3 seconds, while the statement (as I understand it) implies it should be loaded instatnly. Am I getting something wrong?

A fast reply: use wait'0' or in general wait'X' (i.e. the same wait'' argument) – the packs of fives are gathered among the same wait''-arguments.

As I read more thoroughly through your post, I have an opinion that the change from treating the wait'X' argument from (A) time slot to (B) order of loading number is too complex to the end user. I already was thinking about adding (C) order of loading letter to the (A) time slot, i.e. e.g.: wait'1a', wait'1b', etc. and I might still go on with this, however, is it possible to see this feature in a real-world example? I.e. a longer block of zplugin commands? To see the benefits that you mention, i.e.:

the user will probably choose to have commands and their completions be located close to one another in his zshrc, while still being loaded in different waves (time slots), e.g.:

As for the current feature, to see that it is active and working, edit -zplg-scheduler function in a live Zsh-session by using zed:
autoload zed; zed -f -zplg-scheduler

Add echo rescheduled after the sched +0 -zplg-scheduler following-additional  line:
...
[[ $(( ++__idx, __count += ${${REPLY:+1}:-0} )) -gt 5 && "$1" != "burst" ]] && {
    sched +0 -zplg-scheduler following-additional
    echo 'rescheduled'
    break
}
...

and then execute following code:
for (( i=0; i<=22; i ++ )); do
    zplg ice as"command" pick"wd.sh" atinit"echo Firing $i" wait'1' lucid
    zplg light mfaerevaag/wd
done

As for why I've chosen the number 5 as the size of the single firing-session pack, it might be irrational, indeed. I've just didn't want to stress sched that much, i.e. to reschedule that often. But provided that sched has no bugs, it should work without problem also with the pack size set to 1. Let's see if users report any problems with the size of 5 and then change it to 1 :tada:

Sorry for being unresponsive for a while.

the change from treating the wait'X' argument from (A) time slot to (B) order of loading number is too complex to the end user

I think there is some misunderstanding having place, as the way I see it, changing (A) to (B) would only make the loading continuous by reducing the gaps (when all events in time-slot N'th has finished loading, the is no reason not to start executing events in N+1'th slot).
While this change would break no current users' configurations, it would also allow users to re-implement the (C) scheme by setting wait'11' and wait'12' instead of wait'1a' and wait'1b' - as the fact that gaps between time-slots (or waves) would be removed (or it can be seen as time-slots being shrinked to their minimal necessary duration), it would be fine setting big numbers like 11 or 12 for wait modifier.

I.e. a longer block of zplugin commands? To see the benefits that you mention

Consider my own config. I am placing events for loading commands and sourcing their completions nearby (as I guess most zplugin's users would do). However, I choose to load commands after their completions (as I need completions while I'm typing, but the commands would be executed only after I press Enter). If i would choose to go with more sophisticated setup and would use higher numbers in wait modifier, I might end up with a command-not-found error, for example.
I've played around modifying -zplg-scheduler a little, and contrarily to my initial belief it did not re-draw the prompt upon rescheduling. Thus it seems to be a very internal thing, not sure how it affects the end user. Setting different pack sizes does not change the loading behavior in any noticeable (without echo'ing "rescheduled") way either.
I feel a little weird that i fail to explain myself so far. I might be missing some technical detail that seems obvious to you, heh. I tried to illustrate my idea with a scheme of loading process:

It is related to the code example I wrote above

mkdir -p "${HOME}/.zplugin/plugins/_local---null" >/dev/null
zplugin ice lucid wait"0" atload"echo Wave 0 plugin 00"; zplugin load _local/null
zplugin ice lucid wait"1" atload"echo Wave 1 plugin 10"; zplugin load _local/null
zplugin ice lucid wait"1" atload"echo Wave 1 plugin 11"; zplugin load _local/null
zplugin ice lucid wait"2" atload"echo Wave 2 plugin 20"; zplugin load _local/null
zplugin ice lucid wait"2" atload"echo Wave 2 plugin 21"; zplugin load _local/null
zplugin ice lucid wait"3" atload"echo Wave 3 plugin 30"; zplugin load _local/null
zplugin ice lucid wait"3" atload"echo Wave 3 plugin 31"; zplugin load _local/null

So my idea is basically to get rid of the red parts of time line.

Ok I understand what you mean. I've had the picture before. However I was thinking: "if the user wants to effectively divide the time slots even to the extent of abolishing the time slots completely in favor of single, maximum-fast time slot, then why 3-4 sub-slots per single time-slot would not be satisfactory? I know it's a big step-back from the single-wave, but isn't it just satisfactory?".
I'm getting a little inspired by the idea of single max-speed wave, I might code something and provide it as an option.

It seems that to implement the single-wave solution, it is sufficient to add the +1000 below in the -zplg-scheduler:
    integer __t=EPOCHSECONDS+1000 __i correct=0

I've started multiple sessions and the results seem good :)

Oh, using multiple wait modifiers with the same order-setting letter just did not come to my mind.
I've tried both ways (setting it with wait'0a-z' and modifying -zplg-scheduler, and both seem to work fine.
Cool! I think this should be very useful.
Closing the issue now.

BTW. thanks for sharing the zshrc, it has many interesting solutions.

@lainiwa: Could you consider adding your zplugin.zsh into the new zplugin-configs repository? I can add it myself if you don't wan't to bother with a PR if you give me a permission.

Is this feature documented anywhere?  Could the main page wait doco at least refer to this issue?

@HaleTom You're referring to a,b,c suffixes?


Custom pieces

Allows the diagram to display custom piece types (eg, fairy chess pieces, checkers pieces, etc). Chessdiagram now has a pieceDefinitions prop. pieceDefinitions should be an object where the keys are the pieces' FEN characters and the values are callbacks that have transformString as a parameter and return an <svg> element. The callback is passed to the Piece components. Chessdiagram._getPiecesFromFen checks if FEN characters are in pieceDefinition's keys instead of testing against a hardcoded regex.

Wow - love your work. You are awesome. I'll need a a little time to check it out, but looks good. cheers, Judd


return results instead of a count for tests

Realized this is part of #3192, updating description there


[ZEPPELIN-4799] Use spark resource configuration

What is this PR for?
With this PR, we use spark configuration values for K8s Pod resources. A memory limit is not set because of a potential OOM-Killer.
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits

If you set a memory limit of 4GiB for that Container, the kubelet (and container runtime ) enforce the limit. The runtime prevents the container from using more than the configured resource limit. For example: when a process in the container tries to consume more than the allowed amount of memory, the system kernel terminates the process that attempted the allocation, with an out of memory (OOM) error.

@zjffdu Are using a YARN cluster to schedule your Interpreters? Maybe we should change the location of the calculation class.
What type of PR is it?

Improvement

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-4799

How should this be tested?

Travis-CI: https://travis-ci.org/github/Reamer/zeppelin/builds/683269227

Questions:

Maybe a higher default memory overhead?
Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@zjffdu Are using a YARN cluster to schedule your Interpreters? Maybe we should change the location of the calculation class.

@Reamer  I don't get it , what do you mean ?

@zjffdu Are using a YARN cluster to schedule your Interpreters? Maybe we should change the location of the calculation class.

@Reamer I don't get it , what do you mean ?

The spark documentation mentions also YARN clusters for spark.driver.memoryOverhead.

This option is currently supported on YARN and Kubernetes.

I don't have a YARN cluster to execute spark jobs, and I don't even know how YARN really works, but I think that this calculation is also suitable for YARN. If that is not the case, forget my question.

@Reamer  For yarn, this calculation is done by spark. e.g. if user specify spark.driver.memory as 1g, actually spark will ask for one container of (1g + 384m).
For k8s, I suspect maybe spark already done this kind of calculation.

For k8s, I suspect maybe spark already done this kind of calculation.

For technical reasons, Spark can only limit resources in K8s, if you are working in cluster mode. If you run Spark in client mode, as Zeppelin does, you should set --driver-memory (already implemented).

Ich nehme an, dass kein höherer Speicher Overhead benötigt wird, weil wir das in der Vergangenheit auch nicht für YARN benötigt haben.

Thank @Reamer for the improvement! I'm merging this to master and branch-0.9.


Check obsolescence of nearest-neighbour distance

Added a test for this distance functor in 689597aea06c2b1fc315f7b8fe7025edc1d85274. At least it is being used now, even though its significance is of course debatable (maybe it might be useful as a lower bound on the Wasserstein distance or something).


Problems when installing the Gem

I ran the following command to install the gem:
gem install ruby-caldav

And got the following error:

ERROR:  Could not find a valid gem 'ruby-caldav' (>= 0) in any repository

Same here


Add profile rule activation importer

As the natural next step after issue #13, we need a command to import a set of rules to activate with the severity to set. Ideally, we want to be able to create a new profile or add the rules to an existing one.

Resolved by this pull request


Bump Dependencies #11016536093

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/11016536093

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Advertise the community survey on donejs.com

https://github.com/donejs/bit-docs-donejs-theme/releases/tag/v1.3.0


Migrate Prow-related labels from k/t-i repo

It would be great to migrate Prow-related labels from k/t-i repo.
[As-is]
According to https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.yaml,
These labels exist in kubernetes/test-infra repo:

area/prow
area/prow/branchprotector
area/prow/bump
area/prow/clonerefs
area/prow/crier
area/prow/config-bootstrapper
area/prow/deck
area/prow/entrypoint
area/prow/gcsupload
area/prow/gerrit
area/prow/hook
area/prow/horologium
area/prow/initupload
area/prow/jenkins-operator
area/prow/knative-build
area/prow/mkpj
area/prow/mkpod
area/prow/peribolos
area/prow/phony
area/prow/plank (Note: plank has been deprecated.)
area/prow/plugins
area/prow/pubsub
area/prow/sidecar
area/prow/sinker
area/prow/splice
area/prow/status-reconciler
area/prow/spyglass
area/prow/tide
area/prow/tot
area/prow/pod-utilities

[Option 1]
Migrate Prow-related labels as-is:

area/prow
area/prow/branchprotector
area/prow/bump
area/prow/clonerefs
area/prow/crier
area/prow/config-bootstrapper
area/prow/deck
area/prow/entrypoint
area/prow/gcsupload
area/prow/gerrit
area/prow/hook
area/prow/horologium
area/prow/initupload
area/prow/jenkins-operator
area/prow/knative-build
area/prow/mkpj
area/prow/mkpod
area/prow/peribolos
area/prow/phony
~area/prow/plank~ (Note: plank has been deprecated.)
area/prow/plugins
area/prow/pubsub
area/prow/sidecar
area/prow/sinker
area/prow/splice
area/prow/status-reconciler
area/prow/spyglass
area/prow/tide
area/prow/tot
area/prow/pod-utilities

[Option 2]
Since this repo is all about Prow, so remove the prow prefix from all labels, and the area/prow label itself:

~area/prow~
area/branchprotector
area/bump
area/clonerefs
area/crier
area/config-bootstrapper
area/deck
area/entrypoint
area/gcsupload
area/gerrit
area/hook
area/horologium
area/initupload
area/jenkins-operator
area/knative-build
area/mkpj
area/mkpod
area/peribolos
area/phony
~area/plank~ (Note: plank has been deprecated.)
area/plugins
area/pubsub
area/sidecar
area/sinker
area/splice
area/status-reconciler
area/spyglass
area/tide
area/tot
area/pod-utilities

Which option seems better? Any opinions are welcome!
Note: I don't know whether label_sync is enabled for this repo (k-s/prow). If not, then we need to enable as well.
Note: We need to add OWNERS file to each directory, to enable Prow's auto-labeling.
(The PR #101 affects the location of OWNERS file that will be added.)
/assign

/reopen
/remove-lifecyle rotten
I'd like this (along with some other contributor experience improvements)

/reopen
/remove-lifecycle rotten


Add support for session affinity

For user facing web apps a consistent hash-based load balancing would be more suitable than the default round robin one.
In order to enable session affinity, Flagger should create and use Istio destination rules. The Canary CRD should contain one of following affinity options: source IP, HTTP header and cookie.
This implies a breaking change to the bootstrap processes since the current Virtual Service created by Flagger is not using destination rules.

Session affinity over weighted destinations is not supported by Istio.
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: podinfo-destination
  namespace: test
spec:
  host: podinfo
  trafficPolicy:
    loadBalancer:
      consistentHash:
        httpCookie:
          name: istiouser
          ttl: 30s
  subsets:
    - name: primary
      labels:
        app: podinfo
        role: primary
    - name: canary
      labels:
        app: podinfo
        role: canary

With the above rule, a client will be load balanced between primary and canary, since the consistent hash doesn't work across multiple destinations.


Black Page on certain links (ie: Twitter)

My Setup

Operating System: Windows 10
App Version: 3.0.4 (also true on 3.0.3)
Installation type: exe

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description
When posting a twitter link, the "description" automatically added below contain the text, a link to the image, and the date (with its permalink url).
Clicking on the image or date link does nothing or let RocketChat in a black page (no server/room/discussion are visible anymore).
EDIT: To illustrate :

Current Behavior
Clicking on the image/date link of a twitter URL description leave rocket chat on a black page
Expected Behavior
The link should be openned within the default browser.

Probably a server-side issue too, i.e., the web client is not opening those links in a new window/tab.
@Nono-m0le do you mind opening an issue there while I'll be working around it in the app?

Not sure if this is related, but the behavior seem pretty similar with issue #1834

I confirm, still not fixed on 3.0.5 thus the milestones changes I guess.


set rounding execution mode to RTE to match libclc expectations

CI-clvk-ubuntu-clang-debug  is failing with the following reason:
[CLVK] supports_capability: Capability 4467 not yet mapped to a feature.
[CLVK] check_capabilities: Device does not support SPIR-V capability 4467 (spv::CapabilityRoundingModeRTE).
[CLVK] Missing support for required SPIR-V capabilities.

I think that is just not implemented in swiftshader. I am not sure how to deal with that. Ideas are welcome here.

clvk will need https://github.com/kpet/clvk/pull/563 to support the capability. But even with this commit simple_test is failing.

Maybe we should set the execution mode only if we generate OpConvertUToF/OpConvertSToF.

It appears the logic for adding the capability is incorrect.


discussion: How can we make the function authoring process more robust?

We have caught bugs where (1) The Eager evaluator has different behavior than functions (2) onnx checker doesn't report an invalid function or graph (3) TorchscriptEvaluator has a bug where boolean constant inputs were not handled (All addressed in #428)
For discussion and ideas, what can we do to make the function authoring process more robust?
@BowenBao @titaiwangms @fatcat-z @xiaowuhu @gramalingam @shubhambhokare1

(1) The Eager evaluator has different behavior than functions
Could you remind me of this one?

(1) The Eager evaluator has different behavior than functions

Could you remind me of this one?

Probably this one?

(2) must be fixed in ONNX. Is this a reference to this issue ? As discussed there, ONNX checking logic, for historical reasons, consists of two parts. Type-based checking is distinct from the basic checker. This PR exposes that functionality in a way it can be directly called for a function (we could use it previously, but only by constructing a Model representing the function).
Are there are other checks missing in ONNX?

Are there are other checks missing in ONNX?

So far this is the only check I am aware of!

https://github.com/microsoft/onnx-script/pull/454#discussion_r1117095052


[Project] Improve wechaty-puppet-lark

Hello students!
We want Wechaty to be the universal instant messaging SDK on all IM platforms for chatbot makers to build their great conversational user interface, so while these are our ideas of what we think would make good projects for the summer, we're eager to hear your ideas and proposals as well.
Try us out and get to know the Wechaty code with examples!
Link to #30
Required skills for all projects

git version control
collaborative software development on github.com
software development in at least one of Wechaty's six languages on at least one of Linux, macOS, and Windows.

Implement Lark Puppet (wechaty/wishlist#34). The Puppet abstraction allows Wechaty to provide a consisting API on all IM platforms for build a chatbot. We are supporting WeChat, WeCom, Whatsapp already, and last year, we completed the initial development of the Lark Puppet. We want to improve this puppet so that our developers can run their chatbots on Lark more conveniently.

Required skills: TypeScript programming language, Git, Lark API, HTTP.
Likely mentors: @Roxanne718 , @huan

Useful Links

Introducing Wechaty Puppet Service (Providers)
Wechaty puppet
Wechaty puppet mock
Lark API
Lark Puppet

Hello students!
We want Wechaty to be the universal instant messaging SDK on all IM platforms for chatbot makers to build their great conversational user interface, so while these are our ideas of what we think would make good projects for the summer, we're eager to hear your ideas and proposals as well.
Try us out and get to know the Wechaty code with examples!
Link to #30
Required skills for all projects

git version control
collaborative software development on github.com
software development in at least one of Wechaty's six languages on at least one of Linux, macOS, and Windows.

Implement Lark Puppet (wechaty/wishlist#34). The Puppet abstraction allows Wechaty to provide a consisting API on all IM platforms for build a chatbot. We are supporting WeChat, WeCom, Whatsapp already, and last year, we completed the initial development of the Lark Puppet. We want to improve this puppet so that our developers can run their chatbots on Lark more conveniently.

Required skills: TypeScript programming language, Git, Lark API, HTTP.
Likely mentors: @Roxanne718 , @huan

Useful Links

Introducing Wechaty Puppet Service (Providers)
Wechaty puppet
Wechaty puppet mock
Lark API
Lark Puppet

I think LARK_APPID and other environment variables can be loaded in the form of a configuration file, otherwise it is very troublesome to export every time.

期末视频
展示视频：https://youtu.be/-HOF0LV1d54
国内：https://v.qq.com/x/page/h3280md1b6i.html
Live Demo 视频：https://youtu.be/lH3giTpdOtM
国内：https://v.qq.com/x/page/h3280a7pbwi.html


Instructions to install without the need for docker

Do we have any installation document on installing without docker?

No?

Not really an answer, but as the Dockerfile is there, you can see all steps required to build from source, and how to run it.
For node, you will probably use something like pm2

Dockerfile isn't very helpful
Thanks anyway

Prerequisites
You need to have git and Node.js installed on your system.
Downloading source code
git clone https://github.com/pawelmalak/flame
cd flame

# installing dependencies (it might take some time)
npm run dev-init

Building client
cd client
npm run build

Then create data and public directories in root directory of the project. Move all content of client/build to public directory.
Running
Edit .env file in root directory - change NODE_ENV variable to:
NODE_ENV=production

Start Flame with:
node server.js

Wait till server starts. You should get following logs in the terminal:
Socket: listen
Server is running on port 5005 in production mode
Connected to database
All models were synced
Initial config created

Flame is now running. Visit it at localhost:5005

thank you so much, it worked perfectly. !!!

Glad it worked. Added installation guide to the wiki and updated README.md with link to it.