Start section: SQS

Basic coverage of SQS, even just a placeholder.
Quip collaborative doc - work in progress

AWS SQS doc
AWS SQS forum
See SNS or SQS? comment stream for some interesting ways to process SQS items only once, using DynamoDB and Elasticache
aphyr on queues, in general: Oh no, queues

What is a queue service?
How does SQS implement a queue service?
When does one use a queue service like SQS?
What are important limits associated with SQS?

I can possibly take this - have requested access to Quip doc

We now have this started with https://github.com/open-guides/og-aws/pull/505 thanks to @lobster1234
@rjhintz @k3ypad Any follow-on PRs or feedback? I'll close this for now as I can't access that quip doc, but feel free to open a new PR or issue with additional changes!

I don't have any additional feedback at this time.
Rich
+1.510.984.2571
On Sep 19, 2017 8:12 AM, "Joshua Levy"<EMAIL_ADDRESS>wrote:

We now have this started with #505
https://github.com/open-guides/og-aws/pull/505 thanks to @lobster1234
https://github.com/lobster1234
@rjhintz https://github.com/rjhintz @k3ypad https://github.com/k3ypad
Any follow-on PRs or feedback? I'll close this for now as I can't access
that quip doc, but feel free to open a new PR or issue with additional
changes!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/open-guides/og-aws/issues/305#issuecomment-330390922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACx_BiK2jIJQnz8hoj1xzkzIJR1g2lrks5sjwbTgaJpZM4KuJUU
.


Improve error handling

[ ] Differentiate color between errors

500 range = fatal

alarming color
400 range = something unexpected / expired JWT / etc

less alarming

[ ] Print out the title and detail if it has JSON structure

[ ] Verify that error notifications (i.e. unauthorized login) go away once user leaves that route

In general and by default, there should be a clear error message for every unexpected behavior in the web app. All the backend endpoint returns a structured error response in json format. That format must be honored and parsed by the frontend in an intelligent manner for a graded display of error.  The frontend must try to parse the error in an expected format. In case the format is missing or absent, try to qualify the error based on HTTP status code. In case of text based error, generally happened in case of serious server errors (HTTP 500), display the error text.


⚠ Bofrost.es has degraded performance

In a4449a3, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1624 ms

Resolved: Bofrost.es performance has improved in 58a686c after 13 minutes.


Fix interaction between styles and sizes.

Rather than having both textstyle CSS classes and size5 CSS classes affect the font size (and step on each other), implement sizes more the way TeX does: a command like \displaystyle changes the current size.
Remove displaystyle/textstyle CSS classes entirely, since they do nothing now.
This is actually a simplification, since now only size affects the size. Simplifies CSS and computation. Many screenshotter tests change; most of them (all?) change to be more like TeX.

Thanks for the PR.  I wonder how this interacts with https://github.com/Khan/KaTeX/pull/718.  I'm guessing that after rebasing now that #718 has been merged will result in some additional changes to some of the screenshots.  I'll try to review this over the next couple of days.

Nah, there's no interaction between this and #718—this actually assumed #718 :)

(Rebased.)

c2aaf90 fixes a longstanding bug in \sqrt in scriptsizes.

I'm going to re-commit with some changes to the mechanism, because of corner cases in the interaction between sizes and styles.
Here's the issue. Consider:
\scriptstyle\large a vs. \large\scriptstyle a
These commands have no equivalent in TeX, but these work, and have the following result:
$\text{\large$a$}$---$\text{\large$\scriptstyle a$}$---$\scriptstyle\text{\large$a$}$

Note that \large overrides the preceding \scriptstyle size change. The question is, does \large override all properties of \scriptstyle, or just the size?
In this commit, Options has a baseSize which determines the sizes chosen by future style changes. A sizing command overrides both the currently active size and the baseSize, but does not override other aspects of the style.
This means that TeX like \scriptstyle\large a\scriptstyle b will have possibly-surprising results. Both “a” and “b” will nominally be in \scriptstyle (which affects, e.g., math spacing), but “b” will be smaller.
I'm not sure there's a more coherent solution than this (maybe you can think of one), but this seems most TeXlike.

After playing with more examples, including a^{2^{\sqrt{\sqrt{\large 2^{2^2}}}}}\large 2^{2^2}, I now believe sizing commands should change to \textstyle (if the style is currently \scriptstyle or \scriptscriptstyle), and that's what's there now.

The \sqrt changes look awesome.  It's interesting that many of the screenshots changed, but there doesn't appear to be any visual change.  I can only assume that some change in the order of operations of some of the calculations resulted in an imperceptible change to the layout.  I was surprised by the changes to ModScript-chrome.png without changes to ModScript-firefox.png.

I now believe sizing commands should change to \textstyle (if the style is currently \scriptstyle or \scriptscriptstyle), and that's what's there now.

This is so that both the sizes glyphs and the spaces between them is consistent no matter where the sizing command is used, is that right?

The \sqrt changes look awesome. It's interesting that many of the screenshots changed, but there doesn't appear to be any visual change. I can only assume that some change in the order of operations of some of the calculations resulted in an imperceptible change to the layout. I was surprised by the changes to ModScript-chrome.png without changes to ModScript-firefox.png.

That is my assumption too, and I share your surprise. The main change here is that, e.g., \scriptsize changes are applied via the size mechanism, which might be, you know, 0.000001 off from the previous relative fontsize or something.

This is so that both the sizes glyphs and the spaces between them is consistent no matter where the sizing command is used, is that right?

Yes.
For what it's worth, and it's up to you, but this will probably conflict with #519. Whatever gets merged first I'm happy to help resolve conflicts.

Hi @kevinbarabash any other comments on this?

@kohler Did you mean something other than #519?

Whoops, thanks, I meant the @ronkok stretchy wide PR, which is #670

Ah, OK, I figured.  Probably #670 wants to go first, as @kevinbarabash has been working on that for a while.

@kohler sorry for the delay.  I want to merge #670 first.  I'm going to spend some more time tonight looking at it and will hopefully be able to merge it.  My hope is to get your PR reviewed either tomorrow or sometime this weekend.

#670 has landed.  I don't see any conflicts, but perhaps tests need to be rerun?

The new PR is ready, including necessary changes to the stretchy functions (#670). I also added a screenshotter improvement.

I took out the screenshotter diff and updated some comments as requested.

I'm going to check in another commit that adds the 6pt size and implements TeX's size relationships for scriptstyle/scriptscriptstyle. I also gave KaTeX's sizes more significant digits.

The TeX size relationships are in.

Hi @kevinbarabash any comments?

@kohler sorry.  I haven't reviewed changes to buildHTML.js.  I'll have time this weekend.

Thanks for the comments, I checked in some changes.
The MathML values look correct to me in a couple of examples, so I think it's OK.

Hi @kevinbarabash, any more comments or requests on this?
(I have some other changes blocked here.)

@kohler thanks for making those changes and for checking the MathML output.  The output looks good so if there are things that I've missed they must be minor.


[TE] Rootcause frontend draft

RootCauseResource endpoint for processing rootcause search queries

(Hidden) Root-cause table display on "Root Cause Analysis" dashboard tab

Config and param tweaks to support added features

I used a pretty hacky approach in "AnomalyView.js" and "AnomalyModel.js". It does the job, but I'd be glad to learn how to do this right.

amended requested fixes


Add experience levels as a standard to pages

Every page in Concepts, Knowledge, Scripting and Tutorials should have an experience label;

Starter (people that just started out, this is basically child’s play type of easy)
Novice (used to be: Beginner; people that have good experience with the basics and essentials)
Experienced (used to be: Intermediate; people that know a lot about creating addons, basically the level at which you can help beginners and other experienced users out)
Expert (used to be: Advanced; people that are familiar with even the hardest subjects of creating addons, basically people that can write addons with ease and rarely have to ask stuff, stuff with this label is not understandable for starters and hard to understand for beginners)

Colors for each label:

Starter

Light grey with black text

Novice

Vibrant dark green with white text

Experienced

Orangey or Goldish yellow with black text

Expert

Vibrant dark crimson with bright magenta-pink-ish text

A few notes:

We are already sort of doing this, with Beginner, Intermediate, and Advanced. Green -> Yellow -> Red.

I would rather keep with this style for a few reason:

We are already using it
It doesn't require adding new SCSS colors
It looks good on both light-mode, and dark-mode themes

Also worth nothing: We can actually use these categories as sub-headings inside of the actual page. For example starting with a beginners explanation, and then having some intermediate or advanced areas bellow. This is currently already being done.

So yeah, good issue overall. I would definitely support adding more difficulty-level pips around the wiki. Just I don't think we need a NEW entire paradigm, and I'm sorta against cluttering things with new colors.

Yes it was a little far fetched but it is quite nice to atleast change the names and add a starter level.

I did not plan to make the labels appear in the titles of pages. But as labels inside the page, as they appear currently.

Adding them as a necessity to each page will give the wiki a more organized feel and clear up some misconceptions and underestimations about the difficulty of subjects.

but it is quite nice to atleast change the names and add a starter level.

I don't think we should change names/color or add a "starter" label.
Three labels is clean, organized, and follows the accepted flow for color difficulty (green easy, yellow medium, red hard). We can vote on this in the discord though, if you insist.

I am definitely in support of adding these labels everywhere on the wiki to make it consistant tho

Migrated


Borrow local to feedback for Scroll Memory extension

Hi:) ✿(。◕‿◕。)✿ ,can't find Repository, So Borrow local.
Scroll Memory
https://chrome.google.com/webstore/detail/iidnpfiaeiohlkmaehhjoiffcmjclpap
Very good Chrome extension, there are no other alternatives in the Chrome store.
But Scroll Memory is a bug🐞,Not compatible with the following extension 👇
CLUT: Cycle Last Used Tabs
https://chrome.google.com/webstore/detail/cobieddmkhhnbeldhncnfcgcaccmehgn
https://github.com/harshayburadkar/clut-chrome-extension

☝This is also a very practical and powerful extension.
Use for rapid switching to last tab (by pressing once) or to the second to last used tab(by pressing rapidly twice) and so on.

❶ e.g. CLUT sets hotkey to Alt+Q,
❷ Scroll Memory is enabled for memory scrolling (icon turns red),
❸ Use Alt+Qto switch tabs quickly, 🐞 is coming..👇
At this time, I did not close the tab, the switched page(tab) will scroll again🐞.
The reason is that Scroll Memory remembers the position before switching tabs.
Can you fix this problem? Thanks♪(･ω･)ﾉ

Another problem is can add option for ⚓URL#anchor (#hash)
E.g   https://github.com/davidgilbertson/react-recollect#how-big-is-it
#how-big-is-it is URL#anchor(#hash)  ,can it be Set to ignore?


Adding a gist to awesome-dart-pad

I would like to merge my gist https://gist.github.com/53fe98f3984e8b70dcfd0c784653e5fb.git should I do a PR or an issue is enough?
Link to the project https://github.com/jayanthj737/Flutter-Portfolio-App

@jayanthj737 Please create a PR.

@jayanthj737 Closing this issue, Let me know if you need any help.


Autocomplete - provide reference to the parent component in displayFn

feature request:
in displayFn, the this refers to the Mdautocomplete component, not to the custom component in which  displayFn  is implemented.
For translation, I need to grab a translationServive which is injected onto my custom component.
My current implementation is kind of a hack:
    displayFn(enumValue: any): string {
        // this here is acually the Mdautocomplete control
        // HACK to get the AutocompleteEnumFormFieldComponent
        const that = (<any>this).template._parentView.parent.component;
        const translatedValue = that.translateService.instant(enumValue);
        return translatedValue;
    }

You can bind your displayFn to the component with:
[displayWith]="displayFn.bind(this)"
Then you can use this.translateService..... without the hack!

This solves the problem. Thanks @jymdman !

@areijngoudt I think this is also only a hack. Because everywhere else where a function is called, this points to the component. And this should be done in displayWith as well.
Please reopen it

No resolution to this?


[doc-bug][sideloading note]

Add note for sideloading in all Get started procedures

Docs Build status updates of commit ccbcf62:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/sbs-gs-csharp.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-gs-csharp.yml
95
19
link
:white_check_mark:

msteams-platform/sbs-gs-javascript.yml
93
82
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2953841:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/sbs-gs-csharp.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-nodejs.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-spfx.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-gs-csharp.yml
96
18
link
:white_check_mark:

msteams-platform/sbs-gs-javascript.yml
93
81
link
:white_check_mark:

msteams-platform/sbs-gs-nodejs.yml
92
29
link
:white_check_mark:

msteams-platform/sbs-gs-spfx.yml
95
27
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


One character fix to unbreak Netlify

This PR fixes a one-space error introduced in #9086/L205 that caused all subsequent Netlify builds to break.
This PR highlights the fragility of Black Friday-flavor Markdown, and serves as an excellent point of discussion for why we should consider porting Kramdown (in which the majority of repo content was composed) to Go.
/assign @mistyhacks

/lgtm
/approve
@zacharysarah please check your editor as it made unrelated whitespace changes and that's not generally a great idea.


Always instantiate the extends clause, even in the presence of an error

This prevents extra downstream errors from polluting the output in checkJs, and also leaves the component as flexibly consumable in allowJs.

@mhegazy Can I get a rereview? I've had to update the code (since apparently I did have failing tests, I was rerunning the same old file because vscode wasn't actually saving my checker.ts buffer to disk until I went to close the file... but that's another story) to 1. only affect JS (for now), and 2. handle extraneous type arguments more gracefully (ie, not crash or produce follow-on errors).

@weswigham let's get this in and get folks to test it, we can look at weswigham#2 in more details later on.

Alright


update vcpkg baseline to 2023.12.12

this baseline breaks builds on fedora/aarch64 hosts:
-- Running vcpkg install
Detecting compiler hash for triplet arm64-linux...
error: while detecting compiler information:
The log file content at "/home/scarey/repos/github.com/microsoft/vcpkg/buildtrees/detect_compiler/stdout-arm64-linux.log" is:
-- Configuring arm64-linux-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /usr/bin/cmake /home/scarey/repos/github.com/microsoft/vcpkg/scripts/detect_compiler -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/home/scarey/repos/github.com/microsoft/vcpkg/packages/detect_compiler_arm64-linux -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/home/scarey/repos/github.com/microsoft/vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=arm64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/home/scarey/repos/github.com/microsoft/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_LINKER_FLAGS_RELEASE= -DVCPKG_LINKER_FLAGS_DEBUG= -DVCPKG_TARGET_ARCHITECTURE=arm64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -D_VCPKG_ROOT_DIR=/home/scarey/repos/github.com/microsoft/vcpkg -DZ_VCPKG_ROOT_DIR=/home/scarey/repos/github.com/microsoft/vcpkg -D_VCPKG_INSTALLED_DIR=/home/scarey/.cache/jetbrains/remote-deployments/ziti-tunnel-sdk-c/build/fedora-reldbg/vcpkg_installed -DVCPKG_MANIFEST_INSTALL=OFF
    Working Directory: /home/scarey/repos/github.com/microsoft/vcpkg/buildtrees/detect_compiler/arm64-linux-rel
    Error code: 1
    See logs for more information:
      /home/scarey/repos/github.com/microsoft/vcpkg/buildtrees/detect_compiler/config-arm64-linux-rel-CMakeCache.txt.log
      /home/scarey/repos/github.com/microsoft/vcpkg/buildtrees/detect_compiler/config-arm64-linux-rel-out.log
      /home/scarey/repos/github.com/microsoft/vcpkg/buildtrees/detect_compiler/config-arm64-linux-rel-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:344 (vcpkg_execute_required_process)
  scripts/detect_compiler/portfile.cmake:18 (vcpkg_configure_cmake)
  scripts/ports.cmake:170 (include)

error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.
-- Running vcpkg install - failed
CMake Error at /home/scarey/repos/github.com/microsoft/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
  vcpkg install failed.  See logs for more information:
  /home/scarey/.cache/jetbrains/remote-deployments/ziti-tunnel-sdk-c/build/fedora-reldbg/vcpkg-manifest-install.log

config-arm64-linux-rel-out.log:
Re-run cmake no build system arguments
-- Cross compiling arm64 on host aarch64, use cross compiler: aarch64-linux-gnu-g++/aarch64-linux-gnu-gcc
-- The C compiler identification is unknown
-- Configuring incomplete, errors occurred!

looking into it.


Skip Current Day Altogether

I want to tag new todos with creation date, like this: [[Date Created]]: {now}
But I don't want it to appear on todos that are already created in daily page because of redundancy. So I modified it as follows: [[Date Created]]{now:skip dnp}
But now, it always returns [[Date Created]]
Is there a way to get rid of this too? Like in my case:
{[[Date Created]]:skip dnp} {now:skip dnp} didn't work, but is there any other way to do that?
And if there isn't, will you consider adding this feature? Thanks.

I'm amenable to this feature
Current priority is to continue migrating the rest of RoamJS to Roam Depot - could circle back here after

Thanks!

We now recommend the todo feature in smartblocks


Error: Run Selected lines in python therminal

🚨 The issue tracker is not for questions 🚨
If you have a question, please ask it on https://stackoverflow.com/questions/tagged/visual-studio-code.
I upgraded to VS Code 1.34 yesterday. When I then run selected lines in python terminal I get the following error:
C:\Users\sojohans>& C:/Users/sojohans/AppData/Local/Continuum/miniconda3/pythonsdk/envs/tensor113/python.exe & was unexpected at this time.
C:\Users\sojohans>import numpy as np
'import' is not recognized as an internal or external command,
operable program or batch file.

/duplicate https://github.com/microsoft/vscode/issues/74899


Allow array of content as argument to grid

Description
It would be fantastic to allow grid to take an array of content and splat the elements as separate content arguments, so that grid(array_of_content) would be equivalent to grid(array_of_content.at(0), array_of_content.at(1), array_of_content.at(2), ...).
Use Case
A figure with a grid of images with some consistent file-name scheme:
#figure(grid(
{
  let filename_start = "my_prefix"
  let filename_end = ".png"
  let endings = ("1", "2", "3", "4", "5", "6")
  let filename_transformer(ending) = filename_start + ending + filename_end
  let filenames = endings.map(filename_transformer)

  filenames.map(image)
}
))

Great! Thanks for the pointer. It would be nice to see that in an example of that in the documentation for grid as well ^_^

I am unable to find the code that defined the page https://typst.app/docs/reference/layout/grid/, where I would like to add this example. How is one supposed to make PRs to the docs?

It's here: https://github.com/typst/typst/blob/main/crates/typst-library/src/layout/grid.rs#L6


Add support for sbt 1.0

This PR improves the has_supported_sbt_version function, the HerokuBuildpackPlugin, and adds an sbt 1.0 hatchet test.

Tests failed :)


Hide username and ftp details display via config

When I used it in Travis-ci, I noticed that my ftpUsername and ftpHost was displayed in output log. It will be a nice inclusion if I can skip these entries automatically :-)
Great plugin :thumbsup:

Which tests are you running, none of my tests log any actual credentials? They just log dummy ones used to validate helper functions.
Im relatively new to Travis CI so Im not sure how to do something like this off the top of my head but those logs should only be visible when you log in.  I would have to read into Travis but I am not sure their is an easy way to hide those from the output, apart from maybe using Environment Variables.  If this is something you are familiar with and you wanna submit a Pull Request I can gladly take a look at it.

Hi Robert,
I have created a pull request :-)
To understand this, please go to this build first: https://travis-ci.org/MythicAngel/BanglaDateJS/builds/101255653 and navigate to line 352~361. Here, ftpUsername (seorai7) and links are my personal ftp url and they are securely provided (and hidden) via environment settings in travis (line 84-86).
I have provided necessary comments about the pull request, please have a look...

Ahh ok, I see what you mean, sorry I misunderstood.  I'm at work at the moment but I will try to merge it in, add some documentation, and republish a new version tonight.  Thanks for pointing this out.


Correct order of folders

Hi. I added A-D to the folders in order to get them in the correct order (same as I will make in the open-edx). The way I did it was not the most efficient, as the content of the folder with tools were not transferred to the B-folder. @arvidl, can you move the content?

@arvidl
The content was moved, right? If yes, please close this issue.
thanks!


[shared_preferences] Support v2 android embedder.

Description
Migrate shared_preferences to the new android embedding. This PR does the minimum work to migrate the plugin to the 2.0 embedder. No additional refactoring and tests are added.
Note: IAP migration is depended on landing this PR.
Related Issues
https://github.com/flutter/flutter/issues/41848
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

LGTM


Align contents of the plugin jar files.  #239

Make all files present in the IDE build of the jar be present in the Ant builds.
This separates the compilation into three steps, includes files for
running UI forms, and includes the JPS plugin files which were missing.
It also removes some files that were included in the Ant build but were
not necessary.  Note that there are a couple of redundant files in the
wrong places and a Haxe source file that are included by mistake in
the IDE build, but are still not included in the Ant build.
Fixes issue https://github.com/tivo/intellij-haxe/issues/239

Hi @yanhick, Can you please review this?  Thanks.  (Anybody else is welcome to as well.)

Looks good !


amplify mock api - stuck while creating tables locally

I already have an issue which was closed because of inactivity but this is still an issue and the mock ability hasn't worked for me once. #2064
Describe the bug
I am attempting to run the new amplify mock api which allows local mocking and testing for AppSync, this then outputs GraphQL schema compiled successfully. and continues to create the DynamoDB tables locally, then I see each table being created and after creating 10 tables, at the 11th table it is just stuck without any output, I left it running for about an hour and nothing.
note - our schema has 11 @models so maybe this happens for the last table
To Reproduce
Steps to reproduce the behavior:

amplify api add
create your GraphQL schema
amplify push
amplify mock api - this command will never load all of your tables

Expected behavior
Should load all tables locally and open the GraphQL console locally, or give an error saying that it couldn't load table X for reason Y.
Screenshots

Even after deleting the entire schema and only creating one model like so -
type Hello @model {
  id: ID!
}

Desktop (please complete the following information):

OS: [MacOs 10.15.1]
Browser [chrome]
Version [78.0.3904.108]

Additional context
@aws-amplify/cli version - 4.2.0

When running the command amplify mock I get this error code after going to http://localhost:20005 -

@idanlo Thanks for bringing this to our attention. Does it break with one model or does it just print "error"?

It prints a error after going to the endpoint and attempting to perform a query

@idanlo @danny-waite Can you give me more context? If you could share your schema it would greatly help

@idanlo @danny-waite Do you still need help with this?


Should we include optional deployment of spark history server with this ?

Should we include optional deployment of the spark history server with this? If we should, I can work on that.

Hey, could someone describe which History Server helm chart is working with this operator? All those i've found were deprecated. Thanks


attr.Factory is a little wordy

attrs is a huge net win on an object like this:
@attr.s
class Point(object):
    def __init__(self, x, y, z):
        self.x = x
        self.y = y
        self.z = z

import attr
@attr.s
class Point(object):
    x = attr.ib()
    y = attr.ib()
    z = attr.ib()

but it's a lot less clear when you have something like this:
class Cache(object):
    def __init__(self):
        self._stored = []
        self._by_name = {}
        self._by_id = {}

which becomes
@attr.s
class Cache(object):
    _stored = attr.ib(default=attr.Factory(list))
    _by_name = attr.ib(default=attr.Factory(dict))
    _by_id = attr.ib(default=attr.Factory(dict))

I think an alias for this behavior, like:
@attr.s
class Cache(object):
    _stored = attr.ib(new=list)
    _by_name = attr.ib(new=dict)
    _by_id = attr.ib(new=dict)

could make initializing these types of mutable objects a lot less verbose.

Don't really have a strong opinion here, but I've been finding myself really needing factories that take self lately. (I'm getting along with using __attrs_post_init__ but it's kind of a workaround...)
If we're changing the design it'd be nice for the new design to elegantly accommodate these kinds of callables too.

I think it should at least be factory if anything.  But I have to admit that the reason it’s wordy is that I wanted to avoid mutually exclusive arguments.
Sadly, that ship has sailed long ago so keeping it up doesn’t make a lot of sense anymore.

I guess passing a half-initialized self into the factory would make a lot of people happy…

I also think that attr could make it easier to set default mutable attribute values. IMHO having to explicitly create a Factory object is too wordy and not very discoverable.  Thus I like this proposal. In fact I proposed something similar to Hynek via email, although I suggested "factory" rather than "new" for the keyword argument. I think using "factory" rather than "new" would make it more clear than a factory is introduced automatically.
That being said, I think that while this would be nice it would only be a partial solution. It would not make it easy enough to set an attribute default value to a non empty list. To do that currently you need to use a Factory and a lambda:
@attr.s
class Player(object):
    position = attr.ib(default=attr.Factory(lambda: [0, 0, 0]))

IMHO that is way too verbose, complex and obscure for such as common use case. With this new proposal you would do:
@attr.s
class Player(object):
    position = attr.ib(factory=lambda: [0, 0, 0])

which is better, but still a bit obscure.
Instead, or perhaps in addition to the "factory" parameter there should be a simple way to set an attribute default value to a mutable, non empty value. For example there could be a new "mdefault" attribute  (or perhaps "new", if we use "factory" for the previous use case) which would both add the Factory and the lambda for you:
@attr.s
class Player(object):
    position = attr.ib(new=[0, 0, 0])

Ideally attr may be smart enough to detect when the value is immutable and skip the lambda when not needed.

Hm, I see @hynek 's point. I don't actually need self, but I do need the values of other arguments (post-convert, ideally post-validation). There's already an issue for this over at https://github.com/python-attrs/attrs/issues/165.
First of all, I like attr.ib(factory=<callable>). Second, we could run with this and inspect the callable arguments. For every argument, inject the value of the attribute with the same name. No arguments - just call the callable.
@attr.s
class A:
    a = attr.ib(convert=int)
    b = attr.ib(factory=lambda a: a+1)

# Generated __init__ equivalent:
def __init__(self, a, b):
    self.a = int(a)
    self.b = (lambda a: a+1)(self.a)

A small problem with this is runtime errors:
@attr.s
class A:
    a = attr.ib()
    b = attr.ib(factory=lambda c: c+1)
    c = attr.ib()

This should be an error. But we kinda already do this by throwing errors if attributes with default aren't listed last.

On the one hand, I love this because it is incredibly precise and doesn't carry the structural risk of "here's half a self I found lying around in the garbage, do stuff to it, I'm sure it's fine" that you have with __init__.
On the other hand, wow, what terrifying magic.  Where did b come from???
Finally though - there's no problem with putting c into b's arg list, as long as there are no cycles in the graph, we can just topologically sort all attributes by their dependencies and then set them in reverse dependency order in the generated __init__ 😈

Have you guys lost your minds? 😱

Have you guys lost your minds? 😱

You're right, if brevity is the goal, a kwarg is probably not sufficiently terse to be worthwhile.  How about this:
@attr.s
class X:
    a = attr.ib() | None # -> `default=`
    b = attr.ib() ^ list # -> `default=Factory(list)`
    c = attr.ib() & [] # -> `default=Factory(lambda shared_list=[]: copy.deepcopy(shared_list))

Thoughts?

Oh wait, perhaps I missed the obvious here:

@attr.s
class X:
    a = attr.ib() + None # -> `default=None`
    b = attr.ib() * list # -> `default=Factory(list)`
    c = attr.ib() ** [] # -> `default=Factory(lambda shared_list=[]: copy.deepcopy(shared_list))

Silliness aside, if we’d want to pass optionally a half-initialized self, we’d have to distinguish between methods whose only argument happens to be self and functions that take a self.  So I guess we need to use a unique name? half_initialized_self? 😂
Seems fragile and implicit though…

Did we kind of agree on attr.ib(default=attr.Factory(list)) == attr.ib(factory=list)?

(if you need self, you can always use the @x.default decorator)

A lot of people really dislike the word "factory"; it has some baggage.  How do you feel about something even briefer, like attr.ib(new=list)?

I appreciate the marketing angle but we really want to add a second name for the same concept --  a name that doesn't really make a lot of sense? :-/
Don't get me wrong: I'd love to call it new I just have a very hard time to reconcile/rationalize it.

Factory is a pattern for an object with methods that produces other objects with methods.  But the more general concept of making a new thing, or creating something, is far more general than a factory.  For me it makes sense that Factory would be the class, but that the non-Factory way of specifying it would be under a different name.

glyph has a far tighter definition of "factory" than I've ever heard. I think that name is fine, FWIW.
Though oddly, I associate "new" with other languages (Java) and totally think of that as a thing that produces an object with methods.  But then… isn't everything an object with methods in Python?  SIGLOOP

There's some debate; it's certainly used in other ways too.  I didn't mean to say that my definition was precisely technically correct, just that the term has more of a technical connotation due to the design-patterns literature.

For me, a factory is something that poops out instances and isn’t a constructor/initializer.
I have no problem to associate new with creating new objects – you guys are forgetting the “default” part of it. :)  To that end, factory isn’t great either I have to concede. default_new would probably be best I think – but y’all are too lazy to type that, aren’t you? :-|

What I’m thinking about right now is that someone who isn’t intimate with attrs comes to a code base and new seems like something super confusing.  And being hard on code readers has always been a popular point to bash attrs for so I would prefer to not fuel that any more.
Would it kill y’all to have:
def clever_factory(inst):
    ...
    return value

@attr.s
class C:
    x = attr.ib(default_new=list)
    y = attr.ib(default_new(attr.pass_self(clever_factory))
    z = attr.ib(default=42)

?
To me, this seems like a sweet spot for consistency, brevity, and clarity.  Comments? 🙈

For the middle one, what about attr.ib(default=Factory(clever_factory, pass_self=True))?

That’s a great idea @glyph!  I love the idea so much that I built a time machine and implemented it in the past, so it can be in 17.1! :D

At this point I feel like the easiest way of solving this is just changing the docs to:
from attr import Factory as new

@attr.s
class C:
    x = attr.ib(default=new(list))
    y = attr.ib(default=new(clever_factory, takes_self=True))
    z = attr.ib(default=42)

😎

@Tinche… uh… dammit that's too easy!

This is actually what I do in my own code :).

So um after typing attr.ib(default=attr.Factory(list)) 8x for a single class…am I the only one having weird feelings about new=?  Suddenly I’m sympathetic but I don’t want to make decisions out of recent pain.

give in to your anger

OK but I just can’t get over the inconsistency of new/factory.   That would bother me until me death.
Would you consider attr.ib(factory=list) a sufficiently significant improvement?

@Tinche's example is pretty concise, even if you type Factory instead of new, so this seems unnecessary…  I agree with your desire to void mutually exclusive arguments.

Well, we could go as far as adding a factory for Factory called new. 🤣

I do own factoryfactoryfactory.com

attr.ib(factory=list) is certainly a step up!
attr.ib(default=new(list)) looks quite nice too, but new has a lot of baggage in Python speak.

for "correctness" sake attr.ib(default=attr.OciousParameterFreeDataFactory(list)) hides

Don't really have a strong opinion here, but I've been finding myself really needing factories that take self lately. (I'm getting along with using attrs_post_init but it's kind of a workaround...)

Wanted to also confirm this. I've run into this very often, e.g. setting one attr with other attr as a default value. Writing out
    y = attr.ib(default=attr.Factory(lambda self: self.x, takes_self=True))

is a bit too heavy though.
Wondering if takes_self could automatically be set to True automatically if it's a callable whose signature is exactly one argument named self, as a shortcut? This introduces no ambiguity since a "normal factory" isn't expected to accept any arguments anyway. So the above could be just:
    y = attr.ib(factory=lambda self: self.x)

As a working proof of concept:
from inspect import Signature, Parameter, signature

class Factory(attr.Factory):
    def __init__(self, func, takes_self=None):
        if takes_self is None:
            takes_self = signature(func) == Signature(
                [Parameter('self', Parameter.POSITIONAL_OR_KEYWORD)]
            )
        super().__init__(func, takes_self=takes_self)

def attrib(*args, factory=None, **kwargs):
    if factory is not None:
        kwargs['default'] = Factory(factory)
    return attr.ib(*args, **kwargs)

@attr.s
class Bar:
    x = attrib()
    y = attrib(factory=lambda self: self.x)

>>> Bar(42)
Bar(x=42, y=42)

@glyph: The current state of things is pretty good, yo:
@attr.s(auto_attribs=True)
class Cache(object):
    _stored: list = Factory(list)
    _by_name: dict = Factory(dict)
    _by_id: dict = Factory(dict)

makes me wonder if a auto_factory would be a neat thing to have

What would auto_factory mean?
Anyway, I'd assert that the above syntax addresses this ticket.

Oops didn't mean to close

Since this thread has already fans on Twitter and I got annoyed by the wordiness a few times myself, here’s my final offer:
attr.ib(factory=list) as syntactic sugar for attr.ib(default=attr.Factory(list, pass_self=False))
No magic, no nothing. If you need more power: there’s two other ways for it.

Sounds cool!


Vehicle collision cannot be disabled

Hello,
I'm trying to disable collision between vehicles via beamngpy.
In BeamNG the setting is Options->Gameplay->Simplified collision physics.
When changing this setting, the settings.json file in the user folder gets the new line ""disableDynamicCollision":"true""
Using the settings.change("disableDynamicCollision", "true") method works, as long as the disableDynamicCollision value is not already in the settings.json file.
If the value exists and is set to false, the method changes the setting in the json file, but in game the collisions are still enabled
(On further testing, this is not the deciding factor wether it works or not, as just now it failed to apply the settings even after deleting the line before starting)
In the in game settings menu, the simplified physics option is not selected, it does however show the warning below the setting, that normally only shows up when the setting is enabled.
This is my testing script, it has so far always reproduced the error on the second launch:
import time
from beamngpy import BeamNGpy, Scenario, Vehicle

bng = BeamNGpy('localhost', 64256, home='C:/Users/cryst/Documents/beamng/tech', user='C:/Users/cryst/Documents/beamng/user')
bng.open()
scenario = Scenario('smallgrid', 'example')
vehicle = Vehicle('ego_vehicle', model='etk800', license='PYTHON')
scenario.add_vehicle(vehicle, pos=(190, 0, 0), cling=True)
vehicle2 = Vehicle('vehicle2', model='etk800', license='PYTHON2')
scenario.add_vehicle(vehicle2, pos=(180, 0, 0), cling=True)

scenario.make(bng)
bng.settings.change("disableDynamicCollision", "false")
bng.scenario.load(scenario)
bng.scenario.start()
time.sleep(5)
bng.close()

time.sleep(5)

bng.open()
scenario = Scenario('smallgrid', 'example')
vehicle = Vehicle('ego_vehicle', model='etk800', license='PYTHON')
scenario.add_vehicle(vehicle, pos=(190, 0, 0), cling=True)
vehicle2 = Vehicle('vehicle2', model='etk800', license='PYTHON2')
scenario.add_vehicle(vehicle2, pos=(180, 0, 0), cling=True)

scenario.make(bng)
bng.settings.change("disableDynamicCollision", "true")
bng.scenario.load(scenario)
bng.scenario.start()

Hi, I will check the problem with settings, but in the meantime, you should be able to call:
bng.control.queue_lua_command('be:setDynamicCollisionEnabled(false)')

Does it work for you?

Hi,
Unfortunately replacing the previous commands with the lua command did not disable collisions either.


Update doc and add warning message to support future Q# flow deprecation

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

@shenyingjun, please fix the CI linter issues. Thanks.


Angular-Cli

I am new to angular and using templates, in the routes to remove the '#' what should I do?

this is solved


refactor(ES6): Parser.test.js

What kind of change does this PR introduce?
refactor, ES5 => ES6

Did you add tests for your changes?
All existing tests pass

If relevant, link to documentation update:
N/A

Summary
Refactor Parser.test.js to ES6

Does this PR introduce a breaking change?
No

Thanks


Feat/collapsible panel badge support

Please check if the PR fulfills these requirements

[x] The commit(s) message(s) follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Add 'badge' type support for the header content
Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

@charlesnguyen Be carefull

you don't follow the commit guideline for your commit messages : please read it
you had linter errors : please activate eslint on your webstorm project


Add testing

Improve testing in InTrack.

Codecov Report
Base: 70.45% // Head: 71.54% // Increases project coverage by +1.09% :tada:

Coverage data is based on head (1647dc6) compared to base (c351a8c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #232      +/-   ##
============================================
+ Coverage     70.45%   71.54%   +1.09%
- Complexity      640      659      +19
============================================
  Files           106      106
  Lines          2031     2035       +4
  Branches        240      242       +2
============================================
+ Hits           1431     1456      +25
+ Misses          505      482      -23
- Partials         95       97       +2

Impacted Files
Coverage Δ

...main/java/seedu/intrack/model/internship/Name.java
66.66% <0.00%> (-13.34%)
:arrow_down:

.../java/seedu/intrack/model/internship/Position.java
66.66% <0.00%> (-13.34%)
:arrow_down:

...java/seedu/intrack/logic/commands/MailCommand.java
7.69% <0.00%> (+7.69%)
:arrow_up:

...ava/seedu/intrack/model/internship/Internship.java
94.33% <0.00%> (+8.49%)
:arrow_up:

...n/java/seedu/intrack/commons/core/index/Index.java
100.00% <0.00%> (+9.09%)
:arrow_up:

...eedu/intrack/logic/parser/AddTagCommandParser.java
89.47% <0.00%> (+15.78%)
:arrow_up:

...java/seedu/intrack/logic/parser/InTrackParser.java
90.00% <0.00%> (+26.66%)
:arrow_up:

...eedu/intrack/logic/parser/FilterCommandParser.java
100.00% <0.00%> (+33.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


v12 error

just wanted to report this.

Odd.. does this regularly happen to you?
I can only imagine it happening if the init hook somehow doesn't happen, or happens after the first render.

i just saw it as i was preparing my v12 session and i thought you should know im not sure of the details.


Fix empty response from server when running curl on music demo app

This allows curling the music demo app outside of the running container.

@confluentinc It looks like @pantrif just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

@pantrif Hi! You submitted this PR fairly soon after we merged (we think) a fix for this issue, where we changed KAFKA_MUSIC_APP_REST_HOST from localhost to <IP_ADDRESS>. I just want to confirm, were you hitting this issue before or also after we made the above change?
ie did you test the demo app with host 0.0.00 or was it still localhost when running into this?

Regardless of the above, we do ultimately want to set this to kafka-music-application as you've done. I believe this patch should be applied to 5.2.0 branch and later -- could you retarget the PR against 5.2.0-post so we can merge it downstream from there? You may need to rebase, or feel free to just open a new PR and ping us.
Thanks!

Hello @ableegoldman!!  The localhost part was the problematic one. So I was hitting this issue before you make the above change.
However, I tried a few things of my own like setting the host to <IP_ADDRESS> or to <IP_ADDRESS> like you did and both seems to work just fine.
But I believe since you have already set up a host in the docker-compose file (hostname: kafka-music-application) I found better to provide that host (because <IP_ADDRESS> is too generic)

Closing this 5-year old PR. Version 5.x are EOL already.
We also migrated the content of this repo to https://github.com/confluentinc/tutorials in the mean time.


HPA was unable to compute the replica count

Hi,
I have tried to create HPA for my deployment but after create it show it status:

kubectl describe hpa -n directus-prod
Name:                                                     hpa-vj5qg
Namespace:                                                directus-prod
Labels:                                                   cattle.io/creator=norman
Annotations:                                              field.cattle.io/creatorId: u-ae2iyd64j6
                                                          field.cattle.io/displayName: directus-ui-scaler
CreationTimestamp:                                        Thu, 25 Feb 2021 10:39:47 +0000
Reference:                                                Deployment/directus-prod-ui
Metrics:                                                  ( current / target )
  resource memory on pods  (as a percentage of request):  <unknown> / 80%
Min replicas:                                             1
Max replicas:                                             3
Deployment pods:                                          1 current / 0 desired
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource memory: unable to fetch metrics from resource metrics API: the server is currently unable to handle the request (get pods.metrics.k8s.io)
Events:
  Type     Reason                        Age                        From                       Message
  ----     ------                        ----                       ----                       -------
  Warning  FailedGetResourceMetric       <invalid> (x10 over 119s)  horizontal-pod-autoscaler  unable to get metrics for resource memory: unable to fetch metrics from resource metrics API: the server is currently unable to handle the request (get pods.metrics.k8s.io)
  Warning  FailedComputeMetricsReplicas  <invalid> (x10 over 119s)  horizontal-pod-autoscaler  invalid metrics (1 invalid out of 1), first error is: failed to get memory utilization: unable to get metrics for resource memory: unable to fetch metrics from resource metrics API: the server is currently unable to handle the request (get pods.metrics.k8s.io

Please help me for this error message.
I see the warning In order to use resource metrics with HPA, you need to deploy the metrics server. But When I checked Metric Server has deployed on kube-system

This is my deployment config:

Thanks,
Edgar

Useful
Info

Versions
Rancher v2.5.5 UI: v2.5.4

Route
undefined

Have you found any solution?


Rails time_select with Polaris

Hi, I was wondering if there's a way to render something similar to Rails's time_select using Polaris?

Nothing native currently in the repo. You could use a js based solution on top of the polaris_text_field component, similar to this:
        <%= polaris_text_field(
          name: "q[shop_order_created_at_between]",
          value: filter_created_value(params[:q]),
          label_hidden: true,
          placeholder: t(".created"),
          input_options: { data: {daterangepicker_target: 'input'}},
        ) %>

And then hooking it up via Stimulus or similar.


Module parse failed when using Next.js with Nx

Description
Running a development server or building a Next.js application in a Nx monorepo files with a Module parsed failed error
CodeSandbox/Snack link
No response
Steps to reproduce

Generate an Nx workspace: npx create-nx-workspace@latest
cd into the workspace root
Add @nx/next plugin: npx nx add @nx/next
Generate Next.js application: npx nx g @nx/next:app --directory apps/web --e2eTestRunner=none --unitTestRunner=none --projectNameAndRootFormat=as-provided web
a) Use src/ directory
b) Use app router
Follow instructions for setting up gluestack with existing Next.js project: https://gluestack.io/ui/docs/guides/install-nextjs
Run the development server: npx nx dev web
The server fails with Module parse failed: Unexpected token (5:15) at<EMAIL_ADDRESS>
gluestack-ui Version
1.1.9
Platform

[ ] Expo
[ ] React Native CLI
[X] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
Below is my Next.JS configuration (apps/web/next.config.js)
//@ts-check

// eslint-disable-next-line @typescript-eslint/no-var-requires
const { composePlugins, withNx } = require('@nx/next');
const { withGluestackUI } = require("@gluestack/ui-next-adapter")

/**
 * @type {import('@nx/next/plugins/with-nx').WithNxOptions}
 **/
const nextConfig = {
  nx: {
    // Set this to true if you would like to use SVGR
    // See: https://github.com/gregberge/svgr
    svgr: false,
  },
  reactStrictMode: true,
  transpilePackages: ["@gluestack-ui/themed"],
};

const plugins = [
  // Add more Next.js plugins to this list if needed.
  withGluestackUI,
  withNx,
];

module.exports = composePlugins(...plugins)(nextConfig);

Below is the full error output:
<EMAIL_ADDRESS>Module parse failed: Unexpected token (5:15)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| function createView(nativeProps) {
|     return forwardRef((props, ref) => {
>         return <View {...nativeProps} {...props} ref={ref}/>;
|     });
| }

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./src/app/providers.tsx

It seems adding the @expo/html-elements and changing the order in nextConfig results in a rendering page:
//@ts-check

// eslint-disable-next-line @typescript-eslint/no-var-requires
const { composePlugins, withNx } = require('@nx/next');
const { withGluestackUI } = require("@gluestack/ui-next-adapter")

/**
 * @type {import('@nx/next/plugins/with-nx').WithNxOptions}
 **/
const nextConfig = {
  reactStrictMode: true,
  transpilePackages: ["@gluestack-ui/themed", "@expo/html-elements"],
  nx: {
    // Set this to true if you would like to use SVGR
    // See: https://github.com/gregberge/svgr
    svgr: false,
  },
};

const plugins = [
  // Add more Next.js plugins to this list if needed.
  withGluestackUI,
  withNx,
];

module.exports = composePlugins(...plugins)(nextConfig);

Hey @matthew-mccall, here is nx workspace example. Please feel free reopen the issue.

Hi, it same happen for NX with React. Is there any solution?


Explain how to pass params to previous route when going back

https://github.com/react-navigation/react-navigation/issues/288#issuecomment-378412411

dupe of https://github.com/react-navigation/react-navigation.github.io/issues/30 (closed that one)
that issue mentions:
react-navigation/react-navigation#2932
react-navigation/react-navigation#2870


Should mode production add a hash to output main.js?

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

What is the current behavior?
Setting mode production does not add a hash to the default main.js.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Should mode production add a hash to output main.js?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.

No it should not to keep webpack integration simple. Currenlty, asset names are deterministic. If the filename contains a hash, the developer should consume stats.json to lookup the asset name. This is not beginner friendly.

@ooflorent what's the goal of the production mode?  Can you state it?  Thanks.

@joshunger to elaborate further, if we ship hashes out of the box for production mode, then we risk breaking changes to users or forcing them to use a plugin like html-webpack-plugin to manage injecting files with hashes in them.

We will want to have a great preset to enable all of the best production features so that zero config is still a value proposition for those whod like it


What to do with retired licenses?

Discussed in https://github.com/WordPress/openverse/discussions/71

Originally posted by krysal September 17, 2021
Working on the audio results page with the sample in the local API, I found some interesting results:

There are some audio tracks associated with retired Creative Commons (CC) licenses (nc-sampling+, sampling+), this means that CC no longer recommends their use, but these are still valid CC licenses, so several questions come to my mind:

Should we include these results in the Catalog or ignore them? They passed the license validation.
If we include them, should we add them to the licenses filter? What is the compatibility with the commercial or modification use? With time I guess the number of results for these will be low, and potentially there could be several legacy licenses, and my guess is that the CC only wanted to cover the current ones.
Do we include them in the results but not in filters? Only for showing icons, name, version, etc.

Consensus appears to be:

Include the licenses with their names & icons in the results
Group or hide the filters under a collapsible "More" or "Retired Licenses" section


about prev2out and evaluation score

Does the prev2out make big difference in evaluation?
Does anyone had tried this and have evaluation score of this

@DongNaeSwellfish No, it does not effect the performance of the model.

Thanks! I was reproducing the show attend and tell in pytorch and couldn't get the evaluation score same as the paper, so wondered if this problem matters much...

@DongNaeSwellfish If you use pretrained resnet152 instead of vggnet, then the performance of the model will be hugely increased. Good luck!

@yunjey  Thanks for your code! If I use resnet152, image feature will be [2048], an one-dimension vector. So it will lose spatial information and can I still attention to it?

Because I use [2048]dimensions of resnet, the result get worse...

@clever-curl-curl hi can you please share your code for resnet-152 or resnet-50 ?


In Go To File... allow repeat of previous search

An example use case:

I hit Cmd-P and search for "package.json"

Because I'm in a monorepo, there are many files with that name. I select the one I think I wanted.

Oops I chose the wrong one! So I hit Cmd-P again, to look for the right one.

Problem: I have to type "package.json" again.

Solution: I should be able to press something to get the previous search text "package.json" back in the text box.

In the Find In Files search box, we can cycle previous search terms with Up and Down keys, but we cannot use those in Go To File... because they are already used to cycle through the visible list of files.
A keystroke like Cmd-Up would be fine for me.
Or any of the keys Cmd-K / O / L would be conveniently placed on US keyboards. They currently trigger completely separate features, but I think it might be reasonable to give them a different behaviour within this context. Complete keystroke: Cmd-P Cmd-K
(Alternatively, the ^ key could do this, instead of being entered as a literal character. I think that is rarely used to search filenames. Or the ! key, which nods to bash history search, although it seems that is already doing something, but I'm not sure what exactly.)

Configurable in settings:

And duplicate of https://github.com/microsoft/vscode/issues/18232


Drop support for Rails 6.1

Drop support for Rails 6.1, which reached EOL a while back (cf. https://endoflife.date/rails).

coverage: 97.804% (-0.2%) from 98.049%
when pulling 4de3c728aac05172540a5da056f664c52267835c on olivier-thatch:olivier-drop-eol-versions
into 6e54fe8a008a81cd589417dd52b7fb367c1cfc8c on devise-security:main.


KMS: update README.md

added info about environment variables and enabling the API to the KMS README

@DanSanche Do you need us to merge?

I can do the merge, thanks


Getting lower result using pretrained model

Dear authors,
I tried to evaluate ScanNet-pretrained model you provided as illustrated in REANDME and I got 57.3156<EMAIL_ADDRESS>and 34.0198<EMAIL_ADDRESS>but according to issue #11  this result is obvious lower than expected, even lower than my self-reproduced model on ScanNet which could reach 57.6734<EMAIL_ADDRESS>and 34.3470<EMAIL_ADDRESS>This is quite weird that the same pretrained model on the same dataset gives different results and I can't tell what has happened here. Now I have a guessing that this may relate to data corruption or something like that because I experienced a network cut-off when downloading ScanNet, but I'm not sure about it.  Maybe you should test more times and see if you can get a better result or not.

@NUAAXQ Make sense. I run evaluation again and get expected results. Thanks!


More resillience for json parser would be great

Please include the following with each issue:
1. Describe the bug
If you put a comma in the wrong place, the dialog Loading workspace: : Preparing project: 'ModuleApp' will not be closed and cannot be built with Ctrl + Shift + B. The output then only shows the message [Error - 22:25:08] No active project was found. Make sure to select a project in the VS Code Explorer.

2. To Reproduce

Put a comma in the wrong place, e.g. after dependencies -> version.

{
  "id": "b4f939e2-385f-4671-8179-a853e9d909d6",
  "name": "ModuleApp",
  "publisher": "Default publisher",
  "version": "20.0.22221.1",
  "dependencies": [
    {
      "id": "88cf5d4c-8afc-4a98-9cb7-212196c51d74",
      "name": "Continia OPplus",
      "publisher": "Continia Software",
      "version": "<IP_ADDRESS>",
    }
  ],
  "screenshots": [],
  "platform": "<IP_ADDRESS>",
  "application": "<IP_ADDRESS>",
  "idRanges": [
    {
      "from": 50000,
      "to": 50799
    }
  ],
  "resourceExposurePolicy": {
    "allowDebugging": true,
    "allowDownloadingSource": false,
    "includeSourceInSymbolFile": true
  },
  "runtime": "10.0",
  "target": "Cloud",
  "supportedLocales": [
    "de-DE"
  ],
  "features": [
    "NoImplicitWith"
  ]
}

3. Expected behavior
Ctrl + Shift + B should tell me what is wrong. At least the app.json is wrong.
4. Actual behavior
Dialog Loading workspace: : Preparing project: 'ModuleApp' will not be closed and Ctrl + Shift + B doesn't work.
5. Versions:

AL Language: 10.2.719883
Visual Studio Code: 1.74.1
List of Visual Studio Code extensions that you have installed:

AL Language

Final Checklist
Please remember to do the following:

[x] Search the issue repository to ensure you are reporting a new issue
[x] Reproduce the issue after disabling all extensions except the AL Language extension
[x] Simplify your code around the issue to better isolate the problem

This happened to me last week. Yep, it's not easy to detect you misspelled a comma.

Doesn't the issue appear in the Problems tab?

Yes,

But the window Loading workspace will not be closed even if you fix this problem

We have internally discussed this issue and have decided not to accept this issue to be fixed at the moment to prioritize other issues. Our suggested workaround for now is to reload the window if there was a problem loading the app.json.


Error in GiftCard Demo

Hi
just downloaded the 4.1 version of the demo and tried running it. Axon Server starts without issues. Then when I run:
./mvnw spring-boot:run I get the following error: (running openjdk version "11.0.2" 2019-01-15)
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.0.5.RELEASE:run (default-cli) on project giftcard-demo: An exception occurred while running. null: InvocationTargetException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.MappingException: Could not get constructor for org.hibernate.persister.entity.SingleTableEntityPersister: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]: NullPointerException -> [Help 1]

Thanks
Chris

We'd have to look into it, but my guess is that the demo uses an older version of Spring Boot and Hibernate, which aren't JDK 11 compatible. (It's probably a JDK 9+ issue).

Ran the GiftCard Demo with Java 8, 9 and 11, worked perfectly fine.
Additionally, all dependencies have been pushed to the latest.
Due to further inactivity on this issue, I will be closing it as resolved.


Statistics of latest Autoware's Whole Perception Pipeline Latency (camera_lidar_fusion mode)

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Previously,  we statistics the perception pipeline latency of lidar only mode and analyzed the time consumption of multiple main perception nodes.
https://github.com/autowarefoundation/autoware.universe/issues/8752
Now, we plan to statistics the perception pipeline latency of camera_lidar_fusion mode and analyze the time consumption of the main perception nodes.
Environment:
Device: DELL precison3581
OS: Ubuntu22.04
GPU: NVIDIA RTX A1000 6GB Laptop
CPU: intel CORE i7
Purpose
In order to get a detailed of each node and the overall time consumption of the perception pipeline, and to facilitate developers in improving the performance of the perception module.
Possible approaches

Using debug/pipeline_latency_ms topics to get the time consumption of the perception pipeline.

Custom topics to get time consumption of certain perception nodes.

Definition of done
None

Autoware provides debug/processing_time_ms to display processing times for  the node.
Perception module publish the following debug/processing_time_ms  debug information, we subscribe to these topics and analyzed them to evaluate the time consumption of each node  of perception and entire pipeline.
/perception/obstacle_segmentation/crop_box_filter/debug/processing_time_ms
/perception/occupancy_grid_map/raw_pc_downsample_filter/debug/processing_time_ms
/perception/obstacle_segmentation/scan_ground_filter/debug/processing_time_ms
/perception/occupancy_grid_map/obstacle_pc_downsample_filter/debug/processing_time_ms
/perception/occupancy_grid_map/pointcloud_based_occupancy_grid_map/debug/processing_time_ms
/perception/obstacle_segmentation/occupancy_grid_map_outlier_filter/debug/processing_time_ms
/perception/object_recognition/detection/voxel_based_compare_map_filter/debug/processing_time_ms
/perception/object_recognition/detection/clustering/voxel_grid_based_euclidean_cluster/debug/processing_time_ms
/perception/object_recognition/detection/clustering/shape_estimation/debug/processing_time_ms

/perception/object_recognition/detection/tensorrt_yolox/debug/processing_time_ms
/perception/object_recognition/detection/clustering/roi_cluster/roi_pointcloud_fusion/debug/processing_time_ms
/perception/object_recognition/detection/clustering/camera_lidar_fusion/roi_cluster_fusion/debug/processing_time_ms
/perception/object_recognition/detection/clustering/camera_lidar_fusion/low_intensity_cluster_filter_node/debug/processing_time_ms
/perception/object_recognition/detection/clustering/camera_lidar_fusion/shape_estimation/debug/processing_time_ms

/perception/object_recognition/detection/centerpoint/lidar_centerpoint/debug/processing_time_ms
/perception/object_recognition/detection/roi_detected_object_fusion/debug/processing_time_ms
/perception/object_recognition/detection/object_association_merger/debug/processing_time_ms
/perception/object_recognition/tracking/multi_object_tracker/debug/processing_time_ms
/perception/object_recognition/detection/detection_by_tracker/detection_by_tracker/debug/processing_time_ms
/perception/object_recognition/prediction/map_based_prediction/debug/processing_time_ms


[Discuss] Sass improvement

Hi, I'm opening this not to report an issue but to discuss about sass performance.
The problems :

last changes (https://github.com/mgechev/angular-seed/commit/20d8d5cbc1f3cc3608de095e951d18f213f9ce64), create sometime problems with sass with import (some files doesn't change but imports yes, problem : they are not re-processed !).
The scss files are not cached => with medium projects (+30 components -> +30 scss files in app/) it takes about 30s to compute all of them, too long for proper dev.
Finally, some scss files only contain variables, mixins, etc... and should not be processed, or even added to the main.css when build.prod.

I have done some personnal improvement to the build.html_css task, and share here ideas (maybe not the best, that's what I created a talk). File available here. I'll do a PR if validated.
So first of all :

I created a new folder called scss at the root of app/APP_NAME, this folder contains all my "external scss", and none of these files should be compiled.

Into the css/ folder, I just put one file main.scss containing @import '../scss/main'; This file will import all needed scss files and will be compiled. => This ensure a single entry point, and avoid compiling useless scss files (ex: variables, other projects styles, etc...).
I have also created into project.config.ts a new variable :  SCSS_SRC = `${this.APP_SRC}/scss`;

Into build.html_css

New variable const useCache = true; (should go to project.config) to enable/disabled chache.
3 paths :
const appSCSSFiles  = join(Config.APP_SRC, '**', '*.scss'); // all app scss files
const SCSSFiles     = join(Config.SCSS_SRC, '**', '*.scss'); // all "external" scss files that should not be processed
const mainSCSSFiles = join(Config.CSS_SRC, '**', '*.scss'); // entry scss files

Then into processComponentScss()I used a combinaison of gulp_cache, gulp_progeny, and gulp_filter
return gulp.src([
      appSCSSFiles, // all my app scss files
      SCSSFiles // all my "external" scss files
    ])
    .pipe(useCache ? plugins.cached('process-component-scss') : plugins.util.noop()) // check cached files
    .pipe(useCache ? plugins.progeny() : plugins.util.noop()) // check imports
// personal code
    .pipe(debug({title: 'app css before filter'}))
    .pipe(filter([appSCSSFiles, '!' + SCSSFiles])) // remove all "external" scss files that should no be compiled
    .pipe(debug({title: 'app css after filter'}))
// end personal code
    .pipe(plugins.sourcemaps.init())
    .pipe(plugins.sass(Config.getPluginConfig('gulp-sass')).on('error', plugins.sass.logError))
    .pipe(plugins.postcss(processors))
    .on('error', reportPostCssError)
    .pipe(plugins.sourcemaps.write(isProd ? '.' : ''))
    .pipe(gulp.dest(isProd ? Config.TMP_DIR : Config.APP_DEST));

And did the same for getExternalScssStream()
Not a lot of changes but great compilation time improvement.
If more ideas, comment here.

I'm not a Sass user so I haven't noticed all these problems. Thanks for the proposal!
I like the suggestions, it'll be even better if we're able to reduce the number of configuration properties that you introduce, since we already have plenty of them. Do you think we can drop useCache (if we have caching in all cases we don't loose anything, except some memory, right?) and move SCSS_SRC to pluginConfig?

Yes, useCache can be removed. I just used it as a security. By the way, I disabled the shallRunof the CssTask which return true for sass files, but with caching maybe this class will ne be uselfull anymore ?

So I created a fork here: https://github.com/lifaon74/angular-seed
I changes client css files by scss files to provide examples.

Great, thanks for the effort! I will take a look at it later today/tomorrow after I fix the P1 issue in the tracker.

@lifaon74 your modification is useful.  With the current repo, I can't see a clean way to exclude scss files that I don't want compiled and bundled.  With your mod, I would just put those files in the abstract styes folder: Config.SCSS_SRC
Thank you.

Doc available here https://github.com/lifaon74/angular-seed/wiki/Sass
@mgechev tell me when you'll merge and I'll duplicate the wiki page into your git.

+1 :+1: @lifaon74 need to get your sass wiki docs into this projects wiki, will probably help many others like me trying to get sass working

New pull request => https://github.com/mgechev/angular-seed/pull/1568


First time buyer registration

Reason
The buyer needs an account
Description
The potential buyer creates an account with the following inputs

Name - a text box that writes to the CRM platform
Email - a text box that checks the email address and writes to the CRM platform and creates the username for the account
Company - a text box that writes to the CRM platform
Country - a dropdown list of countries This will write to the CRM platform. #31

There is a series of radio buttons for the main cloud storage options.
By clicking the "get started" button, the following actions will commence-

A new account will be created with the details written to the CRM/Account platform
A validation email will be sent to the submitted email address.
When the email is validated, a second email will be sent with details of how to connect to the chosen cloud provider.

Success Criteria

[ ] criteria 1

Additional Information

Why does someone need an account to see "what data we have"?


Select audio output device is only working after reload

Thought this was documented already but can't find an issue.

It is an issue introduced in 3.3.0. But fixed in development.

@so010 Can we close it or should we keep it open?

@so010  ping

Yes, this is fixed. Closing.


Count Sketch Backward, CUDA Memcheck failures

Description
There are cuda memcheck failures for count sketch backward that need to be addressed. There is an invalid read of size 4 bytes that need to be fixed for count sketch backward.
I fixed by adding an index bound on nthreads but that causes a new issue.
The backward pass of this OP needs to be fixed.
This was again encountered during #15118
Environment info (Required)
What to do:
1. Download the diagnosis script from https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py
2. Run the script using `python diagnose.py` and paste its output here.

Package used (Python/R/Scala/Julia):
(I'm using ...)
For Scala user, please provide:

Java version: (java -version)
Maven version: (mvn -version)
Scala runtime if applicable: (scala -version)

For R user, please provide R sessionInfo():
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
MXNet commit hash:
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
Error Message:
(Paste the complete error message, including stack trace.)
Minimum reproducible example
(If you are using your own code, please provide a short script that reproduces the error. Otherwise, please provide link to the existing example.)
Steps to reproduce
(Paste the commands you ran that produced the error.)

What have you tried to solve it?

@mxnet-label-bot add [Cuda, Bug]


Add tests coverage threshold in pull requests

We should add a minimum threshold for test coverage in PR's to make sure the PR's merged at least have some tests if not 100%.
Right now since we don't have any such threshold so its hard to say the coverage and often we need to ask the author to add test.
I think setting  to 65% threshold would be good to go and later we can increase it.
This would make sure every PR has some tests and will help in avoid bug, better maintenance down the line and increase coverage.

Let me pick this up and add some checks in CI and add jest coverages

Go for it @siddhant1 🚀

@siddhant1 Can I help with this? I have some ideas maybe:)

Hey, just checked this, sure @snorfyang you wanna check the PR and add your comments?https://github.com/excalidraw/excalidraw/pull/6559

Hey, just checked this, sure @snorfyang you wanna check the PR and add your comments?#6559

I would like to use another gh action named codecov, and this works well in the PR to my fork.

This also looks good, I will leave this call to @ad1992!

Thanks @siddhant1 @snorfyang for the PRs.
To start I think we would like to first keep it minimal and introduce test coverage checks (not marking as required and see how it looks in practice) and later we can surely migrate to codecov or similar tool which gives more and detailed insights.
Also @snorfyang code cov will be posting comments every time you update the test or does it just post a single comment and keeps updating it ?

Thanks @siddhant1 @snorfyang for the PRs. To start I think we would like to first keep it minimal and introduce test coverage checks (not marking as required and see how it looks in practice) and later we can surely migrate to codecov or similar tool which gives more and detailed insights. Also @snorfyang code cov will be posting comments every time you update the test or does it just post a single comment and keeps updating it ?

It just post a single comment and keeps updating it.

Just saw this, let me update this!

Hey @ad1992 i would like to add test cases for the code which has not covered with test cases.
i know basic of react testing lib, i can learn more and give it a shot add test cases for smaller portion of code & raise PR for that.

Sure @Thedineshk24! You can run yarn test:coverage to understand where coverage is significantly low.
For a start, you can try adding tests for https://github.com/excalidraw/excalidraw/blob/master/src/components/ColorPicker/colorPickerUtils.ts.
You can create a file colorPickerUtils.test.ts in same folder and start writing tests for each util. To check which exact lines are uncovered you can use yarn test:coverage

Thanks @siddhant1 @snorfyang for the PRs. To start I think we would like to first keep it minimal and introduce test coverage checks (not marking as required and see how it looks in practice) and later we can surely migrate to codecov or similar tool which gives more and detailed insights. Also @snorfyang code cov will be posting comments every time you update the test or does it just post a single comment and keeps updating it ?

It just post a single comment and keeps updating it.

Do keep your PR open @snorfyang , we will merge the regular GH action and once it works well we can consider migrating to codecov as well.


fix for 0.6

Left out of 5dfd745c2c167bdcceac9f23e8234428ea442397
@chriscoey, see if this fixes the issue

yep that fixed it!


callback may has multiple arguments

Most of chrome.* API 's callback only has one argument, but someone not, for example:chrome.hid.receive(integer connectionId, function callback)
And, the native resolve() function only accept one argument, even though resolve.apply(null, arguments ).
So below code only get the first argument:
var cp = new ChromePromise();
var connectionId = 4;

cp.hid.receive( connectionId ).then( function( reportId, data ) {
  console.log( reportId ); // 3
  console.log( data ); // undefined
}  );

I think when callback has multiple argumnets, we need put the whole arguments like resolve(arguments) but not resolve.apply(null,arguments).
So the above code will be:
var cp = new ChromePromise();
var connectionId = 4;

cp.hid.receive( connectionId ).then( function( args ) {
  var reportId = args[0];
  var data = args[1];
  console.log( reportId ); // 3
  console.log( data ); // ArrayBuffer
}  );

Thanks for the PR.
I'm not sure if this is the best way to add this feature. I can see a few problems:

This behaviour may be unexpected if someone only wants the first parameter.
If some version of chrome adds a second parameter to a callback, it would break the resolve function.

I will check more functions on the chrome API that use multiple parameters and then I will try to come up with other solutions to this problem.
Will keep in touch.

If some version of chrome adds a second parameter to a callback, it would break the resolve function.

I think so. Maybe always resolve the whole arguments array is the best way?
// change resolve.apply(null, arguments); to
resolve(arguments);

I got a solution.
If we pass true as the first parameter, then the promise return the whole arguments:
var cp = new ChromePromise();
var connectionId = 4;

// if pass true as first param
cp.hid.receive(true, connectionId ).then( function( args ) {
  var reportId = args[0];
  var data = args[1];
  console.log( reportId ); // 3
  console.log( data ); // -------> ArrayBuffer
}  );

// otherwise
cp.hid.receive( connectionId ).then( function( reportId, data ) {
  console.log( reportId ); // 3
  console.log( data ); // --------> undefined
}  );

I use this solution in my chrome-call, but I'm not sure there isn't have any chrome api that exactly use true as first param.

I like that solution. From what I can see, the chrome developers prefer to use an object instead of a boolean.
If you update the PR, I will merge it.

IMHO, the true param still looks a little tricky,
how about adding a new method:
cp.hid.receiveCombine( connectionId ).then(function ( args ) {
  // args === [reportId, data]
})
cp.hid.receive( connectionId ).then(function ( reportId ) {
  // warn user will only get the first result for regular callback.
})

I think that would be the best way. It would be similar to Promise.promisifyAll from bluebird.
I was thinking of changing the constructor to only have one argument: options. Then it would be possible to choose the suffix for this methods.
English is not my native language either. So I will take some time to think of a better word. But Combine is a good start.

I just submitted a PR with a similar change, but also using the spread operator to be more explicit about what is happening.

Regarding amio's suggestion, I don't know of any way to determine which functions need the 'combine' version for multiple callback arguments. Would you just add it for every function, even though the vast majority of callbacks only take one argument? Perhaps you could wrap the native functions to give them a .multipleArgs method for this functionality without polluting the chrome.promise namespace.
I still think simply returning an array of arguments when the callback takes multiple is the simpler, saner approach. And while it's technically a compatibility-breaking change, I think it's a much better API than having two different versions of the function, especially when the default (and current implementation) is to throw away data.

Yeah, it's a simpler API. And it's better to not drag this any longer.
In any case, I will release it as a new major version because it can break some existing code.

I'm closing this as the issue is now solved. Sorry for taking so long. I'm not longer maintaining a chrome extension so I don't have the need of this library.


fix(shim): rewrite cgroups v2 parsing logic

this commit rewrites the cgroups v2 parsing logic in get_cgroup function which is used to fetch stats of a container. The reason for the rewrite was that in some cases the original logic would panic due to index of bound for parsing paths like
0::/kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice:cri-containerd:278a0aac1fff30dfbc41b4a32ba9de4519928fe7480213dba87aa1498838ef34
we ran into this issue in deleting a spin container in the spin shim.
the rewrite replaces index access to properly propogate the error to the caller of the function and added a few unit tests for the parsing logic.
see more discussion https://github.com/spinkube/containerd-shim-spin/issues/39, https://github.com/containerd/runwasi/issues/418

The cgroups v2 parsing logic is inspired by https://github.com/opencontainers/runc/blob/1950892f69597aa844cbf000fbdf77610dda3a44/libcontainer/cgroups/fs2/defaultpath.go#L83
but there is a critical difference:
The runc cgroups parsing logic will actually fail to parse
0::/kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice:cri-containerd:278a0aac1fff30dfbc41b4a32ba9de4519928fe7480213dba87aa1498838ef34
because it does not take the whole path splitted by the colons. The runc parsing logic would only get kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice which is not the actual cgroups path.
I was not sure if this is a bug in runc, or a bug on how spin container's cgroups path was constructed in the first place.

Couple of questions:

Is the path with colons like that valid?
What is generating the path with colons and should this be fixed in the code generating the path to be more idiomatic?

I can validate that with this patch, what we are seeing in https://github.com/spinkube/containerd-shim-spin/issues/39 is now fixed.

Is the path with colons like that valid?

I think runc with Go impl can actually handle path with colons. So it should be valid.

What is generating the path with colons and should this be fixed in the code generating the path to be more idiomatic?

Maybe youki's libcgroups? I am not entirely sure

Could you please take a look, @mxpv 🙏?

Frankly speaking (in longer term) I think we should not carry groups related code in the shim crate. shim crate supposed to be the foundation for building new shim runtimes for containers, without carrying any implementation details.

I think there are two pending issues which are not resolved by this PR where I made an issue for each


Enable quiet output for Statik

I'm generating a Statik project via .gitlab-ci.yml, but I got (gitlab-) errors because
Writing output fi
Job's log exceeded limit of 4194304 bytes.

This project has do deal with a lot of (generated)  pages (from data/Photos/_all.yml):
public$ find . -type  f  |wc -l
56350

... and perhaps my gitlab runner would not fail when I could run Statik in a quiet mode (which only outputs errors), like statik --quiet.
Or I write a wrapper script which suppresses the output...

Good idea - this should be a quick feature to build in.

Now enabled in v0.17.0. I've also relegated the file listing to the DEBUG logging level (for when one explicitly asks for verbose logging) instead of the INFO level. Simply do the following to enable quiet mode (which only outputs errors or exceptions):
> statik --quiet

To run Statik completely silently (no exception/error logging), do the following:
> statik --quiet --fail-silently


nan loss encountered

❓ The question
During the training process, an error message "nan loss encoded" occurred. Upon checking, it was found that the ce_batch_loss value had "nan". What is this ce_batch_loss and how is this situation caused? How should we solve it?

ce_batch_loss is 'cross entropy batch loss', the cross entropy loss summed over a batch. There are many possible causes for nan loss. For example, the training loss could have been diverging towards infinity (e.g., because the learning rate was too high) or a division by 0 might have happened somewhere. You'll probably need to dive deeper to find the cause of the nan.

@jiaxiaolei007 - please reopen this item or a new one if you have further questions.


Can Component fires event before template rendering in CanJS 2.2

Live code here: http://jsfiddle.net/grany8aa/
var Component = can.Component.extend({
    tag: 'content-renderer',
    template: '{{{content}}}',
    viewModel: {
        define: {
            content: {
                type: 'string',
                value: 'loading...',
                set: function(newVal){
                    return newVal;
                }
            }
        }
    },
    events: {
        '{scope} content change': function() {
            var self = this;
            console.log('log from event ' +this.element.html());
            setTimeout(function(){
               console.log('log from timeout ' + self.element.html());
            });
        }
    }
});

In CanJS 2.1, when content attribute changes, the content will be reflected on DOM before the change event fires. But this is not the case in CanJS 2.2
In CanJS 2.2, when content  attribute changes, the this.element.html() will not contain the updated content.
Is this a regression in CanJS 2.2? Otherwise, please suggest a fix for this without having to use setTimeout.

I don't think this is a regression.  The event dispatching order of events handlers compared to the DOM is not documented or tested.
However, it might be possible to control for this deterministically.
I think the internal control needs to be created after the rendering: https://github.com/bitovi/canjs/blob/master/component/component.js#L282
If you can submit a test (and maybe a fix if it's as easy as moving the control initialization under the template rendering), we can get it in a release.

@justinbmeyer I created a failing test for this issue. But the issue will not be resolved by simply change the order of internal control initialization code. I think this would only affect insert event. In my test case, it tested against the change event from viewModel.
Another finding is, if I remove the set function from the content property, this issue will go away.

I'm closing this and marking it as "needs a hero".  @lihan or anyone else who runs into this problem, I'm happy to pair on making the change.  Just ping me when you have an hour to work on it on gitter: https://gitter.im/canjs/canjs


Fix empty gaps between container strings

Commit Summary

Another attempt to remove empty gaps and fix tabulations on the menu screen

:+1:


CI: Add miri pass to check for undefined behavior

We currently are lacking a CI job in our GitHub Actions CI for running our testsuite using the miri tool.
This tool is excellent for checking unsafe Rust code soundness in combination with tests.
At the moment we do not have a lot of unsafe Rust code but this might change in the future with certain optimizations of maybe simply by introducing unsafe user APIs for more efficient accesses or operations on wasmi in certain use cases.
ToDo

[x] Add miri as a new job for our GitHub Actions CI.

The miri job should check the tests under --release configuration, otherwise miri runs will be way too slow.
Since miri cannot perform certain operations such as opening a file we cannot test the Wasm spec testsuite using miri. For tests that technically cannot be run we need to apply the following attribute to the #[test] marked functions: #[cfg_attr(miri, ignore)]

Implemented in https://github.com/paritytech/wasmi/pull/523. Extended in https://github.com/paritytech/wasmi/pull/524. Closed.


Add dead wheels

https://gm0.org/en/latest/docs/common-mechanisms/dead-wheels.html

We should discuss the benefits of two vs. three wheel odometry pods, I believe we have the materials for three but that is not confirmed

The OpenOdometry pods are looking like a good choice, especially if we already have the wheels and some of the bearings.

Here is the CAD Model for the OpenOdometry pods, they look pretty good and we do have most of those materials, would have to check if the whole for the bearing is big enough for the openbuilds ones that we have used, we might have to get more.

honestly the more i look at this the more i want to roll our own, by the time we've adapted everything to work it'll basically be from scratch anyways imo

as for locations, i think the two parallel pods can go between the drive wheels on each side (and we should make our design thin enough that it doesn't extend past the edge of the hubcaps) and the perpendicular pod can go under the robot, between the intake and the shovel.

currently cadding these

cad complete, will assemble after break


test(test-runner): add test global setup

Added and configured a global test setup

Codecov Report

:exclamation: No coverage uploaded for pull request base (lit-migration@8cc96eb). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@               Coverage Diff                @@
##             lit-migration    #2023   +/-   ##
================================================
  Coverage                 ?   85.39%
================================================
  Files                    ?       72
  Lines                    ?     6745
  Branches                 ?      212
================================================
  Hits                     ?     5760
  Misses                   ?      983
  Partials                 ?        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ES Module as allowed component type

If MyComponent is an ES Module, then <MyComponent> should behave the same as <MyComponent.default>
(e.g. transpile to React.createElement(MyComponent.default)).
This is primarily to support syntax such as the following, while ensuring that tree shaking still will still function (see diff for details):
 import ControlPanel from './control-panel';

 export default = () => <ControlPanel>
     <ControlPanel.Button />
     <ControlPanel.Button />
 </ControlPanel>;

closing this as it will likely require a runtime overhead to solve a semantic and fairly uncommon case


Add tests for CUDA.jl array types

Since we plan to support GPU from this new AD package, it would be good to start testing against some CUDA.jl functionalities early in the process. This should be similar to #29 for many cases, but on CuArray types instead of Array.

Agreed. I'll need to get GPU CI set up, which I've done before, and isn't too much of a pain, but it'll take a few days I imagine.

Resolved by #161 -- this has the very basics of a GPU pipeline (Tapir.jl knows about CuArrays, and knows how to differentiate through creating one with undefined elements).


Correct snapshot agent config task name

I imagine this was just a mistake of forgetting to change a copied value, but I noticed this in the file and thought I should PR it.

Thanks!


Sohu fix

Sohu info extractor currently fails from time to time. I fix it and add some test cases.

Add a more generic function to youtube_dl/utils.py based on the implementation at http://stackoverflow.com/a/8926421/3786245

I've fixed title extraction (the original approach was unable to handle titles like "youtube-dl testing video") and add some test cases. Please review it.

Thanks.