[Bug]: Blocked aria-hidden on a  element

Reproduction
Blocked aria-hidden on a  element
Describe the bug
When I click on the Combobox, something like this will appear in the console
There is a similar situation in the console of https://www.shadcn-vue.com/docs/components/combobox
Blocked aria-hidden on a  element because the element that just received focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
System Info
window : window 11 23H2
Chrome : 128.0.6613.114

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

Update Chrome to 128.0.6613.114 and this problem does not occur

https://github.com/user-attachments/assets/6861b36a-a419-4ede-823b-e576a6f4cd05

any updates?

same problem, I check radix, they dont use aria-hidden

i just set a 150ms timeout and fixed it

i just set a 150ms timeout and fixed it

Could you clarify what you used the setTimeout for?

i just set a 150ms timeout and fixed it

Could you clarify what you used the setTimeout for?

in my instance it was bc it was auto focusing on the underlying input causing err to appear in console. so i swapped to using a set timeout to carry out the focus


Choppy brain mask when top of skull out of FoV

What version of fMRIPrep are you using?
20.2.0rc0
What kind of installation are you using? Containers (Singularity, Docker), or "bare-metal"?
TACC Run
Did fMRIPrep generate the visual report for this particular subject? If yes, could you share it?

Comments
Unlikely to be resolvable in LTS. Should be transferred to sMRIPrep, but I'm here ATM.

Potential duplicate of nipreps/niworkflows#569


Should we resurrect activation logs changes which are now in a separate repo?

The upstream repo is undergoing some refactoring. We haven't picked up changes since June and there are now some conflicts for us to work through.
Will keep an eye on https://github.com/adobe/aio-cli-plugin-runtime/issues/191.

This is a list of commits in our fork that are upstreamable but need a nod from Adobe:

[ ] parameterize the "list" limits
[ ] [fetch multiple activation logs at once)(https://github.com/nimbella/aio-cli-plugin-runtime/commit/2e45c318bea717f3c06c19ee3c7d19f1bce8f577)
[ ] fetch multiple results at once
[ ] make invoke synchronous by default
[ ] filter get last activation by name
[ ] add log banner
[ ] fix triggers in activation list
[ ] add typescript kind
[ ] add --result to activation get
[ ] allow web actions to be created with a secret
[ ] reformat entity list commands
[ ] add human readable date to assets
[ ] omit table headers when lists are empty
[ ] show request id in error when available
[ ] if no activation id is given assume --last
[ ] show code when asked
[ ] remove namespace from lists
[ ] add activation column for sequences and workflows
[ ] allow action create to omit name, use file name instead
[ ] show timeouts in activation list
[ ] add --count for lists
[ ] add --native action support for binaries
[ ] add final annotations when making web actions
[ ] add version to action list
[ ] allow some slicing of log lines and silence header
[ ] format log lines as JSON if possible
[ ] allow get logs --last to skip

Examples of new list format:
> nim action list
Datetime        Access   Kind       Version  Actions
10/21 11:10:54  web      python:3ai 0.0.3    school/import
10/18 14:40:59  web      java:8     0.0.1    qr-java

> nim activation list --limit 10
Datetime        Status   Kind       Version    Activation ID                    Start Wait Init Duration Entity
10/21 11:16:55  error💥  python:3ai 0.0.3      0e73665b18a045fbb3665b18a075fb73 cold  918  3728 3728ms   school/import
10/14 10:35:35  success  python:3   0.0.1      34153295f3544eeb953295f3549eeb27 warm  144  0    2ms      t
10/14 10:35:27  error    python:3   0.0.1      7b6dba1228604249adba122860c24995 cold  549  114  116ms    t
10/11 20:17:31  success  java:8     0.0.9      c100c7821bd84d1080c7821bd83d1026 cold  510  410  980ms    qr-java
10/11 20:15:28  success  java:8     0.0.8      6c3277e6cfa94aeab277e6cfa9daea34 cold  524  461  1071ms   qr-java
10/11 20:14:46  error💥  java:8     0.0.7      fdd0cddaa0ce443290cddaa0ce443288 cold  526  230  230ms    qr-java
10/11 14:08:31  success  java:8     0.0.6      ebdb440fe04a47139b440fe04ab71395 cold  520  352  929ms    qr-java
10/11 14:05:58  success  nodejs:10  0.0.5      112e26379bd546deae26379bd5f6ded0 warm  125  0    11ms     qr
10/11 14:04:45  success  nodejs:10  0.0.5      b3c0a39480fa407a80a39480fae07a7f warm  142  0    8ms      qr
10/11 14:04:26  success  nodejs:10  0.0.5      bfa6d1e3e40a404aa6d1e3e40af04a51 warm  151  0    32ms     qr

I've started to rebase to sync up with upstream. A wholesale rebase didn't work - too many tests failed. I am now cherry picking commits one at a time, and ensuring tests pass at each step. I am working on a new branch for now dev-cherry-pick.
There are at least 3 issues which will require additional work post rebase:

activation log enhancement we added at odds with aio
route override of whisk.system package name
activation poll did not work, requires some aio namespace setting which we don't use
test trigger feed support

Here are the remaining commits which I have not replayed:

[ ] activation logs related: will have to replay those more slowly

commit e73188cb61a6bf29df883e515a27c64318b06d7c
Allow get logs --last to skip for added convenience. Add some parity for --logs with logs command. (#15)
commit a6b3cf31ef9bba68967665460ff8468e51d34465
Pretty print log lines as JSON where possible. (#14)
commit bd667ff2d8b4415dfd5ce2eec3d167fa3ba59d33
Allow log lines to be slices and add flag to supress header. (#13)
commit f1be9edcdefb4d827e9a50af2140a8bf5bf73b59
If no activation id is given, assume --last.
commit 2e45c318bea717f3c06c19ee3c7d19f1bce8f577
Fetch multiple activation logs at once with activation filtering (#14)

[ ] action invoke extra logging header: is this harmless? @joshuaauerbachwatson

commit 2fcaef5b37373df77daed9e4753d5d9e4e996626
In support of nimbella-corp/cloud-workbench#2

[ ] config patch: this causes tests to fail @joshuaauerbachwatson

commit 7e1a1fd3254861297acf5edc23c10c20aa537a51
One possible way to fix config for browsers. (#4)
Probably not the best way.  For nimbella-corp/cloud-workbench#1
commit e685b17f66bace9642f0dcd9a3da437da6e9fcbb
Allow properties file read to fail, eg, in browser

[ ] action create: this is undocumented and i added it as a convenience which i use from time to time but no one has asked for it, leaving for another day

commit f99a5c8322dafdb3a76a48ee06e168489f2b15e0
Allow action create file to imply both the artifact name and action name, dropping the file extension.

[ ] api gateway override

commit 743ef106ce1542db2a2ce775a82da4d856db3ae9
Override API gateway path.

[ ] add ts kind

commit 887912c9213f9bd0557e8632e713a839ce073b72
Add typescript.

[ ] trigger feed: should be subsumed by the rebase

commit 9a45f491f0e0378174b87441b4bc9bd28576125c
Support --feed on 'nim trigger create' (#2)

While I expect to do most of the work on this going forward, I'm assigning @rabbah in addition to myself to keep both of us in the loop.  I will probably need his help again.
A lot of the work will actually be in nimbella-cli and cloud-workbench but tracking it here because Rodric made a good start on laying out the issues and we must ultimately do the merge here.
The immediate issue is getting branches going in the other repos that incorporate dev-cherry-pick branch from this repo.   I've changed some mechanisms in nimbella-cli and have been able to do that.
The resulting branch doesn't build yet.  There are changes in how aio-cli-plugin-runtime exports its internal modules and some utilities have moved to another plugin.   Working on that first.

Branches test-new-aio in public and private nimbella-cli are now building and the deployer tests are passing.   This does not tell us all we need to know yet because (1) I haven't tried building the workbench yet and (2) the deployer tests mostly exercise the deployer (plus nim action [ list | get | invoke ]) but don't exercise other aio functionality very much.
I will try branching the workbench next since several of the questions about omitting or changing commits are about the effect on the workbench.
We can also now put the nim branches through Jenkins, which may reveal a few more things (more usage of aio-based commands in some of the functional tests).

The workbench build has stumbled across some issues.   Working on them but meanwhile testing In Jenkins starting with build job 3627

I can get the workbench to build but I am presently stumped on how to get it to run.  There is a module-level filesystem behavior somewhere in the new aio-lib-runtime that is breaks in a browser.   It might have to do with their logging.  I haven't pinned it down yet.  It's been frustrating.

testing In Jenkins starting with build job 3627

Completed in teardown job 1029 with no intervening failures.   That's the good news.  The workbench is the bad news.

Failures of workbench initialization have been tracked down to the fs-extra package, which is used by aio-lib-runtime in such a way that its module initializations will always execute.   Those module initializations include some that require a real file system and will fail in a browser.   It has been tedious to track these down but I believe it is still the easier course to find them and patch them out (as I have done in other cases) rather than solving the problem through the webpack config.  I think sooner or later we will have to bite the bullet and either clone-and-own the kui webpack builder or start patching its config.  I have avoided this since the kui webpack build is pretty complex.
I still don't know for sure whether fs-extra is the only source of these breakages in the aio runtime 3.0 but I'm hopeful.

It looks like I found all the breakages in fs-extra (three needed correction).
There are also breakages due to aio-lib-runtime usage of globby and (gasp) webpack.      In this case, I didn't chase the problem into the dependencies.   In the case of fs-extra (whose use in aio is now pervasive) it was the less intrusive course.  But, for globby and webpack, which are only used in one place each (and not a place we care about), it was easier to relocate the dependency so the require no longer executes at module scope.
With those five places now patched, the cloud-workbench again initializes.  The workbench tests pass in chrome.  They fail in firefox (timeout while starting up).
Despite the test failures in firefox, the workbench seems to run fine in both firefox and safari (we have no Selenium tests for safari).    Clearly, the problem that motivated commit 7e1a1fd is gone and we can abandon that commit.   That it is no longer needed is plausible since the config plugin has been substantially revised, including some changes to regexes (which were the problem before).

The test failures on firefox seem timing-related and I'm not worrying about them at this point.  I replayed the initial sequence of the test manually in firefox and it works.
Concerning commits 2fcaef5 and 0b4654a, I'll work on those next.   I think commit e685b17 is less immediately critical because it affects only test coverage and not customer-visible behavior.

There was a glitch when it turned out that the latest commits on dev-cherry-pick in Rodric's fork were. not pushed to the nimbella fork.   I redid the tagging and rebuilt the branches in other downstream repos and retested.  No regressions, except that now we have commit 43e5b16, which creates a toggle for the old commit 2fcaef5.   This required a balancing change to nim (which is only made when running in a browser).  The change simply inverts the toggle for that case as Rodric suggested.

The replacement for the old namespace header suppression commit (0b4654a) is 5fd5484.   I've added a toggle for this case and adjusted it a couple of times but I think it's right now.  It is set to false normally (so the header is not suppressed, that is, it is sent).   This is apparently needed by Adobe.   It is not needed by us but the nim command leaves the toggle alone except when running in the workbench, so our CLI paths send it as well.
In nim when running in a the workbench (only), the toggle it is inverted so that the header is suppressed.   This is need to avoid CORS issues in preview versions of the workbench which we need to have working so we can test features.   It is not actually critical for the production workbench but not being able to test features is enough of an issue that I regard this change as necessary.
The mechanism for removing the header is to remove the namespace option from the OW options.   For activation logs (only, among the aio commands that we adopt) there is an options check in aio-lib-runtime that throws due to this omission.   So, in the workbench build (only) we remove that check using patch-package.
The activation logs command works correctly in the CLI and I believe it is actually doing the right thing in the wb too but the output does not show up.   This is a separate regression due to aio 3.0 that also needs resolution before we can merge.
The output change for activation logs in 3.0 is something to do with special routines in aio-lib-runtime that do log printing.   Most of aio-cli-plugin-runtime still does output the old way and that continues to work.   The routines use a logging method that is passed to them.   The interception I am doing in the workbench should mean that this logging method is connected to the capture logger and so it should work but empirically it does not.
Two things to investigate.

The logger gets passed through several places and perhaps somewhere the binding of the method to the CaptureLogger object could get lost.
If anywhere in this code path the Promise chain gets detached, the return of the call stack to the kui dispatcher could race ahead of the output production.   One wouldn't notice this sort of race in the CLI.

Once that is fixed I think it's just cleaning up the aio tests and we can merge.   In fact, once we have "all clear" from nim and wb, we could merge and clean up the aio tests afterwards prior to the next round of sending mods upstream.

I found and fixed what looked like a possible culprit (promise race) but it didn't change the behavior.  A very annoying meta-issue is that debugging gets turned off abruptly during workbench initialization by something newly introduced in aio 3.0 (didn't happen before).   I think this is due the aio core logging plugin, which does an unconditional debug.enable using the value of DEBUG from the process environment.   Since a browser doesn't use the process environment DEBUG variable to control debugging it is always undefined.   Checking out that hypothesis via yet another patch (sigh).

I fixed the debugging which was important in itself.   I then added a lot of debugging output.  I learned that

the capture logger is arriving intact where it is needed and so the hypothesis that it was somehow becoming unbound is rejected
there is no race condition in promise handling as far as I can see

It's simply that the code behaves differently in the workbench versus the CLI for (I think) the same test case.  In the CLI, when the individual activations are fetched and scanned for logs, logs are found.  In the workbench, that scanning operation turns up no logs.  If I am somehow not using the identical test case in both places then I have been on a wild goose chase and there is no problem.   If that's not it, then I have to dig deeper to see why there is this divergence in behavior at the model level.   I no longer think there is output that is being swallowed.  There is simply no output being produced.

If I am somehow not using the identical test case in both places then I have been on a wild goose chase

Yup.   It's true.   I'm a doofus.   I was not running the identical test case in both places.  I think I was more methodical initially, and I think it's probable that there was a promise race which I fixed with PR #20.   But, after that, while continuing to test, I started being careless about choice of tests and thought there was still a problem when there wasn't.
One source of confusion is the help text for the --limit flag.  It says: " Fetch the last LIMIT activation logs" which is misleading.   What it actually does is " Fetch the logs of the last LIMIT activations".   That was leading me to think that, in some cases, logs ought to be found when in fact they wouldn't be (because the last LIMIT activations had no logs, though older ones did).
I believe we can proceed to a merge in the following order

[ ] Merge PR #20 into dev-cherry-pick

I have been asking for reviews from @rabbah for these changes because I wanted to observe his principles about how to maintain that branch.  But, we already have one failing aio test (expectedly) and a coverage deficiency on the aio testing side, and I doubt he will ask me to fix that (he didn't the last two times).   So, think it is better to just go ahead with the plan.   Fixing the tests comes later.   I will do that unless Rodric actively objects soonish.

[ ] Merge the consuming branches in nimbella/nimbella-cli, nimbella-corp/nimbella-cli and cloud-workbench.

this could be done without waiting for the previous since there is already a tag I can use.  Depending on the remaining steps, we might need to redo the tagging one or two more times, which is no big deal.

[ ] Do the hard reset (or whatever) to effectively rename dev-cherry-pick to dev

I want Rodric to either do this or give me a syntactically precise cookbook ... it is outside my present comfort zone
if this orphans the old tag I will redo the tagging.  We want all tags to be on active branches to avoid confusion the next time around

[ ] Fix the aio tests
[ ] Revisit the few commits that Rodric ignored when building dev-cherry-pick

I merged PR 20 and squashed 3 commits related to suppressing of the namespace in certain contexts (into 1). These changes are on the dev-cherry-pick branch now.

I went ahead and merged the consuming branches.  Because of the way we use tags, this means that the change in aio is now live for us, even though the tag is on the dev-cherry-pick branch.
I decided to go ahead and merge ahead of running yet another Jenkins test.   Changes since the last successful Jenkins test have been minor (and mostly in the workbench, which won't be tested by that).   I'd rather go live (internally, since none of this is in stable versions yet) and find any problems through usage ahead of having some need to put out a stable version.

Rodric verified the build post-merge ... he got aio 3.0.   He also renamed the branches.   So, we're almost done.

The remaining problems under this issue are to fix the tests and restore some recent commits of Rodric's which got deferred in his initial push.
One test broke because it was designed to cover the old (unconditional) way that we handled omission of the namespace header.   It was easily fixed by setting the newly-added toggle as part of the test.   This led to "all tests passing" but not quite 100% coverage.   That much is committed.
The jest coverage report does not call out any lines but the problem is definitely in RuntimeBaseCommand.js and Rodric believes, plausibly, that it is due to the try/catch block we added to keep the property file loader from crashing the workbench.   The empty catch block is not covered by any test because the propertiesFile() call is designed not to fail and cannot be made to fail in a CLI without some mockery.   We could add that mockery but I think a better solution is to change the way we accomplish the goal here so that we don't have the try/catch block at all.  I can probably insert some "browser friendliness" directly into properties.js so that it is harmless in a browser and I think that's maybe a better model for the Adobe team if we decide to send this change upstream (the try/catch is pretty indirect and hard to explain whereas a direct "don't use the file system if you're in a browser" seems clearer and more maintainable going forward.

Rodric fixed the tests without changing away from the current try/catch logic.  We now have 100% coverage and I checked off that task.
The remaining task concerns two commits that never got cherry-picked.  Both are enhancements to activation logs.   The bulk of the logic in activation logs (including the output display) is now in aio-lib-runtime which we don't currently fork.    I am leaving it to another day to decide whether to fork that repo and add back our enhancements to activation logs.   I am retitling this issue to cover the residual task.
I am not un-assigning myself from the issue because I need to keep it on my board to remember that the change to aio 3.0 is a significant change affecting the next stable release.   When the next stable release happens, I will take my name off this issue.

It appears that the external kafka test breaks now because it depends on a using the --last --count <n>  feature of nim activation result.   This was regressed.   I don't understand why I didn't catch that when I ran the test (build 3627 -> teardown 1029).   Investigating.

Yes.  External kafka job 655, which was in that sequence, passed.  I checked that the correct branch was being tested in that sequence.  It was.  I don't know why it didn't fail then since it is failing now.   In the log of job 655 you see
nim activation result --last -c 10

and it works.   Starting with job 672 we see
 ›   Error: Unexpected argument: 10

in response.   I get the same response running the command locally.   The likely cause is that the count feature is part of one of the commits we deferred from the cherry pick, thinking that only Rodric was using the functionality.  😄 .   The fact that this wasn't caught earlier is completely unexplained but I'm not wasting more time trying to figure that out.

This was one of the changes where I allowed AIO to take precedence over our change. The flag is now —limit. The —last is implied and may be omitted.

Hmm just noticed there’s a difference when —last used: a banner is printed between each result. The behavior should be the same imo.

Thanks.   I was just looking at the omitted commits and realized I was on the wrong track.  So, we should be able to fix this by just changing the test and no change to aio should be needed.

Oh.  I missed your intervening comment.   So, probably the banner should be eliminated, right?

To be precise: we can fix the external kafka job just by changing the syntax in the job without changing aio as long as --last is not used explicitly (just tried this out).   For some reason (haven't read the code) explicit use of --last triggers this intervening banners business, which is weird and probably should be fixed but is orthogonal.

For now, I am assuming we will fix the test and not change aio at this time.   Leaving this issue open.  If we think more changes are needed we should probably retitle the issue again.

I think one of the commits I dropped added a --quiet flag which omits the banner which I think is useful when looking at multiple results and trying to correlate them to an event.

@joshuaauerbachwatson I propose closing this issue as "completed" good enough for now.

@joshuaauerbachwatson I propose closing this issue as "completed" good enough for now.


Bug in bool props in

Version
3.2.12
Reproduction link
https://codepen.io/catsmeatman/pen/qBjYeve
Steps to reproduce

Define  as Vue component (Vue.defineCustomElement)
Bind some bool prop with value "true"
Use prop in template and see value is false.

What is expected?
Prop value will bee true
What is actually happening?
Bool type is not correctly
In standard Vue component, not , this case is work correctly. See https://codepen.io/catsmeatman/pen/rNwvXgQ

This is because you are using Vue template syntax (:test-value="true")  in plain HTML.

Did i understand correctly? Read this doc https://v3.vuejs.org/guide/web-components.html#passing-dom-properties, that in case i must use
<test-case :test-value.prop="true"></test-case> or <test-case .test-value="true"></test-case>

This is only possible when using custom elements inside Vue templates, because it's Vue's binding syntax.
You are not using the custom element inside a Vue template. You are using it inside plain HTML.

Thanks


Calculate score and show scoring

Calculate score and show ScoreSection and ScoreTotal in "Decimal", "Quantity", "Integer" and "Choice"

Created a new PR


Bedrock snapshot no longer exists

Hi, we're trying to spin up a new OP node and we're getting the following error in the bedrock init container:
...
Bedrock node needs to be initialized...
Initializing via download...
Fetching download link...
Downloading bedrock.tar...

02/13 16:12:20 [NOTICE] Downloading 1 item(s)

02/13 16:12:20 [ERROR] CUID#7 - Download aborted. URI=https://r2-snapshots.fastnode.io/op/op-10-02-2024-full.tar.lz4.tar.lz4
Exception: [AbstractCommand.cc:351] errorCode=3 URI=https://r2-snapshots.fastnode.io/op/op-10-02-2024-full.tar.lz4.tar.lz4
  -> [HttpSkipResponseCommand.cc:218] errorCode=3 Resource not found

02/13 16:12:20 [NOTICE] Download GID#edfb68535c617e6b not complete: //downloads/bedrock.tar.lz4

Download Results:
gid   |stat|avg speed  |path/URI
======+====+===========+=======================================================
edfb68|ERR |       0B/s|//downloads/bedrock.tar.lz4

Status Legend:
(ERR):error occurred.

Actually it does exist, the filename upstream is just malformed (it shouldn't have an extension): https://r2-snapshots.fastnode.io/op/latest-mainnet
https://github.com/smartcontracts/simple-optimism-node/blob/main/scripts/init-bedrock.sh#L27
BEDROCK_TAR_DOWNLOAD="https://r2-snapshots.fastnode.io/op/$(curl -s https://r2-snapshots.fastnode.io/op/latest-mainnet).tar.lz4"

Gets a double extension
https://r2-snapshots.fastnode.io/op/op-10-02-2024-full.tar.lz4.tar.lz4

I think fastnode has changed the format. You can remove extra .tar.lz4 as a hotfix for now.
Will look into this tomorrow.

Should be fixed in recent merge


Fix typos

Fix typos related to with_spec_dirs

@ChengyuZhu6 Looks like we first need to fix some clippy/cargo fmt check. Mind creating a PR to fix it first and then merge this?

Mind creating a PR to fix it first and then merge this?

Sure. I'll do it.

rebase to main to pick up the clippy check fix.


Concourse: randomize container placement

Concourse now supports randomised container placement across the worker pool:
export CONCOURSE_CONTAINER_PLACEMENT_STRATEGY=random
concourse web --container-placement-strategy=random

Volume placement and number of containers running on an instance is not something autoscaling will take into account, so I think it makes more sense to go with random here.

Will try changing to t2 type instances instead for the burst capability, given that we need cache hits for Java builds


Transform context passed to template immediately before rendering

How can I transform the context that's passed to the template immediately before rendering? For example, there should be a way to add/remove/change objects that are passed to the template as context, while having access to req and res.
I can't tell whether I should be looking at app.engine() or app.set('view') (which isn't documented in http://expressjs.com/4x/api.html#app.settings.table so I can't tell exactly what it's for) or somewhere else.
So far I have basic integration set up using Nunjucks templating, it looks like
class NunjucksView {

  constructor(name, opts) {
    this.env = nunjucks.configure('./templates');
    this.name = name;
    this.path = name;
  }

  render(opts, cb) {
    this.env.render(this.name, opts, cb);
  }

}

app.set('view', NunjucksView);

But I don't see any req or res objects or how to modify the context passed to the template.

If the View.render(opts, cb) were passed req and res it would make for the perfect place to hook into for any processing that needs to happen after all middleware and route code has run. What do you think?
The kinds of context modifications I'm talking about are general and apply to multiple routes and templates (if it weren't then res.locals could just be modified in that individual route).
Examples include clearing flash messages right after the template has displayed them (for example https://github.com/expressjs/flash doesn't actually do that!), internationalizing strings that haven't already been internationalized before being passed into the template layer (for example caused by using one of many libraries with poor i18n support), or otherwise massaging the context to a format more suitable for display.
Rather than delegate all of these responsibilites to each route, it's better to have the ability to do it all in one place.
Of course I could create a wrapper for res.render and call the wrapper instead of res.render in all the routes, but then all developers working on the application need to always remember to use the wrapper. It would be better to have this context modification capability happening beneath the res.render layer.

Of course I could create a wrapper for res.render and call the wrapper instead of res.render in all the routes, but then all developers working on the application need to always remember to use the wrapper.

Why not simply modify the render function itself? It's the whole reason we export the prototypes:
var express = require('express');

express.response.render = function render() {
  // define your render hook here
  // req = this.req
  // res = this
}

Otherwise, please send us a PR, but keep in mind that the View class is purposely disconnected from HTTP request/responses, as part of separation of concerns, so we wouldn't accept adding those values into that class.

Modifying the prototype would be fine. In the custom render function, since I"m overriding the original render function what's the way to call the original render function after my hook has prepared the context?

Either a simple manual AOP around, or use a AOP library.
var express = require('express');

around(express.response, 'render', function (inner, args) {
  // do something to the args/contexts
  return inner.apply(this, args);
});

function around(obj, prop, func) {
  var inner = obj[prop];
  obj[prop] = outer;

  function outer() {
    func.apply(this, [inner, Array.prototype.slice.call(arguments)]);
  };
}


feat(*): add typescript definitions

Added typescript definitions

@JamesEggers1 look at this PR, please)

I'll pull in this PR and add it to the next version of the package as soon as I have time a little later this week.
Thank you for the PR!

@JamesEggers1 , just reminder 😃

Package 2.4.1 has been published.


why not change to maven ？

sbt is limited in china ,and maven also have simple scala compile and project manager plugin ,
I think use maven will be more welcome

I do think this is off-topic. It's like someone come to you and ask 'why you choose to wear black hat? I think white is better'

Except that I am very frustrated trying to build with sbt. It timed out trying to download the launcher and now it is complaining because I have no bintray credentials. Why would I need credentials for a repo? Of course, this could easily be solved if there were binary versions available.

@rgoers That doesn't match my experience. I've just cloned this repo 30 minutes back and built it from the command line -- no need for any credentials whatsoever. I haven't used Bintray for anything on this machine either.


Missing pager in pure env: git fails

$ git diff
less -R: less: command not found

$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"16.09.1219.c1068dc"

Could be added to gitFull probably?

This is a common issue with applications that need a pager. You'll notice it also e.g. when calling the help function from Python when using --pure. When I noticed I added less to the closure but this was later reverted (https://github.com/NixOS/nixpkgs/issues/17034).

I guess it's an open question whether $PAGER should be included/wrapped in drvs? I think it's probably best to leave them separate since it will lead to bloated closures. Another potential issue is $EDITOR which git will also expect.

Any news on this issue?

I agree with @matthewbauer Let's leave these to be impure.


KeyError: u'point clusters'

View details in Rollbar: https://rollbar.com/Zooniverse/Zooniverse_Aggregation/items/71/
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/rq/worker.py", line 568, in perform_job
    rv = job.perform()
  File "/usr/local/lib/python2.7/dist-packages/rq/job.py", line 495, in perform
    self._result = self.func(*self.args, **self.kwargs)
  File "/app/engine/jobs.py", line 16, in aggregate
    tarpath = writer.__write_out__(compress=True)
  File "/app/engine/csv_output.py", line 443, in __write_out__
    self.__subject_output__(workflow_id,subject_id,aggregations)
  File "/app/engine/csv_output.py", line 281, in __subject_output__
    self.__marking_row__(workflow_id,task_id,subject_id,aggregations[task_id],shape)
  File "/app/engine/csv_output.py", line 492, in __marking_row__
    for cluster_index,cluster in aggregations[shape + " clusters"].items():
KeyError: u'point clusters'

caused by serengeti wildebeest watch (project id 121) - no longer happening


[Subscription] $expand=ancestors is missing in the specs

Hi,
I opened this issue as recommended from azure-powershell#12391. Azure Portal uses a very helpful parameter and value "$expand=ancestors" to add to the output on where a subscription is located in the management group tree. This parameter and its values sadly is not part of the specs.
Sample API Call with the parameter $expand (managementGroupAncestors is included in the results):
https://management.azure.com/subscriptions/{SubscriptionId}?api-version=2020-01-01&$expand=ancestors
{
  "id": "/subscriptions/....",
  "authorizationSource": "....",
  "managementGroupAncestors": [
    "management-group-level-2",
    "management-group-level-1",
    "{myTenantId}"
  ],
  "managedByTenants": [],
  "subscriptionId": "*****",
  "tenantId": "*****",
  "displayName": "MySubscription",
  "state": "Enabled",
  "subscriptionPolicies": {
    "locationPlacementId": "....",
    "quotaId": "....",
    "spendingLimit": "Off"
  }
}

Sample API Call without the parameter $expand (managementGroupAncestors is not included in the results):
https://management.azure.com/subscriptions/{SubscriptionId}?api-version=2020-01-01
{
  "id": "/subscriptions/....",
  "authorizationSource": "....",
  "managedByTenants": [],
  "subscriptionId": "*****",
  "tenantId": "*****",
  "displayName": "MySubscription",
  "state": "Enabled",
  "subscriptionPolicies": {
    "locationPlacementId": "....",
    "quotaId": "....",
    "spendingLimit": "Off"
  }
}

Would be awesome if this parameter could be officially added and described in the specs:
https://github.com/Azure/azure-rest-api-specs/blob/2cd7c6eacc5430d8956885e8d19b87ce3f3ebd6e/specification/resources/resource-manager/Microsoft.Resources/stable/2021-01-01/subscriptions.json#L95
Many Thanks!

any update here?

any updates here?

Any news here?

I also found myself in need of this. Finding the management group of a certain subscription us currently unreasonably complex, the only way I have found is listing all management groups and then explicitly trying to find that subscription in each management group.
Something like Get descendants or Management Group Subscriptions - Get Subscription. Both requiring a lot of API calls and unnecessary round trips to Azure.


CMake: Build Lagom automatically :^)

Depends on SerenityOS/Serenity#8107. This will build Lagom in Serenity's
Build/Lagom/ directory, install it within the Build directory of this
project, and then link against it. This completely prevents Lagom going
out of sync with the runner.

Don't mind the build error, I didn't cherry-pick the commit properly :man_facepalming:
Removed from the above comment.

As we're already doing a completely separate Lagom build, why still do that in the serenity build dir at all? Would be nice to only get the sources from there and have everything else in our own Build/

This helps if you have an existing Lagom folder, so you don't have to build Lagom twice. However, I can still move it to our build directory if you'd like.

The setup.sh script needs updating (mostly removals AFAICT)

I didn't see anything that needed to be updated, and it seemed to just work. Is there anything I'm missing?

Is there a way to get progress for the LagomProject build step? for me it just looks stuck at [5/13] Performing build step for 'LagomProject' for quite some time. Once that's done it spits out all 605 lines of output at once

Indeed, I'll look into that.

This seems to build everything from Lagom, including all utilities and tests, which seems rather wasteful

Will also look into this.

This helps if you have an existing Lagom folder

That's unlikely, the current default build directory for Lagom is Build/lagom, with a lowercase L :)

I didn't see anything that needed to be updated, and it seemed to just work. Is there anything I'm missing?

The checks for libLagom.a seem useless now as we're going to build our own anyways.
3/4: Thanks!

Superseded by #30.


luamodules: fix compile warning in cjson

Summary
Fix compile warnings -Wstrict-prototypes
Impact
No.
Testing
CI pass

@XuNeo please upstream the patch to lua-cjson, so we can remove the patch in the future.

@XuNeo please upstream the patch to lua-cjson, so we can remove the patch in the future.

Someone has already done that, but seems no one is merging it.

let's ignore macOS broken.


Remove deprecated nuxt-link from codebase

Remove deprecated nuxt-link from codebase. Use router-link instead.
Only affects these buttons on Dashboard view:

Tested with rancher 2.9.0 / operator 1.6.3 / elemental UI 2.0.0-rc1:
Automated tests are able to select and click the buttons, all good.


Site navigation not working

Expected Behavior
Access link
Steps to Reproduce the Problem

Access https://foliotek.github.io/Croppie/
Try to navigate in Documentation or Demos links

Specifications

Browser: Chrome
Version:

This is fixed.  Thanks again.


qgis: 2.8.2 -> 2.10.0

Is version 2.10 released already? or is this a release candidate?

This is a release.

It seems that 2.10 is released as 2.10.1; would you like to update this PR? Thank you.

Done.


Document required args in tkn-results usage.

This change documents the required args to specify result/record parents
in list queries, as well as documents usage of - to handle
multi-parent queries.
Fixes #113

/approve
/lgtm


Allow users to pass NUMACTL_ARGS into bin/cassandra

Patch by Matt Byrd; reviewed by for CASSANDRA-13557

(committed elsewhere)


Create 0000-01-02-SalSalich.md

created a branch, created a file and made a commit, and opened a pull request


On Atlases update the back end to allow for additional fields

Need

We need to be able to capture the following additional information on the atlas:

Highlights - text, not required
Code Links - an array of code links, with an optional name for each link, not required
CELLxGENE Atlas Collection - a CELLxGENE collection id, not required

Approach
Update the Atlas's API to take the above fields when creating.
Update the Atlases list and detail response to include the fields in for the /atlases and /atlas/id GETs.

Complete


I try to run it on frey faces after 40 epoc I get the following error

Please help me fix it.
[instantiating model
iterating
'''''
[Epoch 40 finished. LB:<PHONE_NUMBER>55, time: 0.140044927597
Traceback (most recent call last):
File "/home/hoda/Downloads/Variational-Autoencoder-1-master/run.py", line 66, in
valid_LB = model.likelihood(x_valid)
File "/home/hoda/anaconda2/lib/python2.7/site-packages/theano/compile/function_module.py", line 795, in call
allow_downcast=s.allow_downcast)
File "/home/hoda/anaconda2/lib/python2.7/site-packages/theano/tensor/type.py", line 140, in filter
raise TypeError(err_msg)
TypeError: Bad input argument to theano function with name "/home/hoda/Downloads/Variational-Autoencoder-1-master/VAE.py:158" at index 0 (0-based).
Backtrace when that variable is created:
File "/home/hoda/Downloads/Variational-Autoencoder-1-master/run.py", line 34, in
model = VAE(continuous, hu_encoder, hu_decoder, n_latent, x_train)
File "/home/hoda/Downloads/Variational-Autoencoder-1-master/VAE.py", line 84, in init
self.update, self.likelihood, self.encode, self.decode = self.create_gradientfunctions(x_train)
File "/home/hoda/Downloads/Variational-Autoencoder-1-master/VAE.py", line 128, in create_gradientfunctions
x = T.matrix("x")
TensorType(float32, matrix) cannot store a value of dtype float64 without risking loss of precision. If you do not mind this loss, you can: 1) explicitly cast your data to float32, or 2) set "allow_input_downcast=True" when calling "function". Value: "array([[ 0.65234375,  0.734375  ,  0.79296875, ...,  0.4609375 ,
0.3984375 ,  0.37890625],
[ 0.66796875,  0.74609375,  0.625     , ...,  0.4921875 ,
0.44140625,  0.41015625],
[ 0.6875    ,  0.73828125,  0.6953125 , ...,  0.453125  ,
0.390625  ,  0.37109375],
...,
[ 0.6875    ,  0.671875  ,  0.39453125, ...,  0.56640625,
0.2734375 ,  0.2890625 ],
[ 0.71484375,  0.6640625 ,  0.48828125, ...,  0.47265625,
0.34765625,  0.30859375],
[ 0.7734375 ,  0.65234375,  0.5703125 , ...,  0.3515625 ,
0.30859375,  0.28125   ]])"
](url)](url)
PS: thnx for sharing ur code:

Sorry that was a mistake on my side. Fixed.


CSP error

With<EMAIL_ADDRESS>sometimes I'm getting an error in console about CSP and I have to restart the svelte-kit server.
No errors at all with vite-plugin-svelte@3.
My svelte.config.js is:
import adapter from "@sveltejs/adapter-static";
import { vitePreprocess } from "@sveltejs/vite-plugin-svelte";
import "dotenv/config";

const dev = process.env.NODE_ENV === "development";

function gen_csp() {
  if (dev) return;

  let directives = {
    "default-src": [`https://*.${process.env.PUBLIC_URL}`],
    "style-src": [
      `https://*.${process.env.PUBLIC_URL}`,
      "unsafe-inline",
    ]
  };

  return { directives };
}

/** @type {import('@sveltejs/kit').Config} */
const config = {
  preprocess: vitePreprocess({ script: true }),

  kit: {
    adapter: adapter({
      fallback: "index.html",
    }),

    serviceWorker: {
      register: !dev,
    },

    csp: gen_csp(),
  },
};

export default config;

Why?

you've been around long enough to know that we expect reproductions.  its very unlikely that vps causes a csp violation as it only compiles svelte files in isolation and is not involved in serving. Please open a report with a minimal reproduction that includes the actual error message you are getting in the sveltekit repo.

Here we go, after a few edits in my .svelte files:
(index):42 Refused to create a worker from 'http://localhost:4000/service-worker.js' because it violates the following Content Security Policy directive: "script-src https://*.website.com 'nonce-4r1nfez5GdG7nc+4Ce8Wvg=='". Note that 'worker-src' was not explicitly set, so 'script-src' is used as a fallback.
(index):42 Uncaught (in promise) DOMException: Failed to register a ServiceWorker: The provided scriptURL ('http://localhost:4000/service-worker.js') violates the Content Security Policy.
localhost/:1 Refused to load manifest from 'http://localhost:4000/manifest.webmanifest' because it violates the following Content Security Policy directive: "default-src https://*.website.com". Note that 'manifest-src' was not explicitly set, so 'default-src' is used as a fallback.
6
Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "connect-src 'self'".

I just switched back to v3. It is unusable because of this.

this is a bug tracker for vite-plugin-svelte, not your personal rant box. please stop

For the record, the error you're getting is supposed to happen.
As per the docs, if not worker-src, then script-src, then default-src.
Your default-src is https://*.<public url>
Your service worker is http://localhost:4000/service-worker.js.
Assuming your hostnames are, in fact, matching, your default-src is still specifying that it should accept subdomains and https:// only. So, http://localhost:4000 should fail because its 1) not https 2) not a subdomain matching https://*.website.com
This is also why your http://localhost:4000/manifest.webmanifest file is blocked.

See Defining Sources

You probably want self or http://${public.env.PUBLIC_URL}/ (note the http and trailing slash), or perhaps both.
But +1 to what @dominikg said. These messages notify a lot of people, so please be considerate. Even writing this took 10+ minutes, for a single message. It adds up quickly for all OSS maintainers & it's very very tiring in addition to time-consuming. It doesn't even begin to count the amount of time and effort @dominikg pours into developing, maintaining, and/or triaging actual issues for this core/essential plugin for (all of) Svelte ecosystem.
Please seek out channels like the Discord first for these kinds of things


Send updated sourceFile to getLiteralText

Fixes https://github.com/microsoft/TypeScript/issues/59085#issuecomment-2198774412
When the node's sourceFile is not the same as the currentSourceFile the method returns an incorrect position. In example, in the code below, the position will hit the comment text in foo.ts instead of bar.ts.
// @Filename: foo.ts
// Some comment that is going to be used instead on the correct ['constructor'] text.
import { Bar } from "./bar";

export class Foo extends Bar {
    // | <-- trigger completions here should show ['constructor'] from bar.ts. Instead, crashes.
}

// @Filename: bar.ts
export class ElementNode {
    ['constructor']!: any;
}

Note that I unsuccessfully tried creating the repro as a fourslash test but for some reason the completions api treats the whole thing as a single file avoiding the issue. Also, I don't know how to avoid the test that changed.

Closed in favor of https://github.com/microsoft/TypeScript/pull/58216


add show_job_use.py summary function

only an addition of a new script and a change to init py so it's all good to merge in right away!


Cut the 2.14.0-rc.0 release

Cut the first 2.14.0 release candidate. It is possible I will add one more PR to this release, but I want to get any comments sooner than later.

Thanks for the review, I have updated this for the comments, and rebased to include #6279. Right now I have 6279 listed as security/bugfix, is that ok or should it just be bugfix?

:+1:
security/bugfix and on top is right, as it's basically a reflected XSS.

/benchmark 2.13.1

/benchmark cancel
Benchmark looks good.


Can't edit certain tiles since version <IP_ADDRESS>+

Since version 1310 I can't edit certain tiles.  Might be a new incompatibility with Forestry apiaries.

Yes, I have.

Just to get things clear:
On McEdit <IP_ADDRESS> -> it breaks
On McEdit <IP_ADDRESS> -> It works

https://github.com/Khroki/MCEdit-Unified/commit/9038427a58c3bfb8d2701b92dcedf17573aeab22#diff-ad5c3c6fa85951f43dc970a58b75971cR862

This should fix it, it'll be included in the next build. Let us know if it's fixed by then :-)
E: I can't github.

If you can test it using the old mod version, if that works it's a new issue caused by forestry not by mcedit.

Sorry for my late reply @Rubisk , yes, that's it.


Add Memory game using reactjs

Is your feature request related to a problem? Please describe.
I want to make a game which is called memory game that consist of set of cards. The cards have a pictures on one side and each picture appears on two (or sometimes four) cards. The game starts with all the cards face down and players take turns to turn over two cards.
Describe the solution you'd like
Children will enjoy by playing this game.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @Ayush7614, it has been long since the issue was last updated would love to volunteer to resolve it if it is up for grab


Linting fixes, npm scripts

package.json:

Add npm script check:lint to lint all files per each tsconfig
Add npm script check:tsc to type check all files per each tsconfig
Add npm script check to run both check:tsc and check:lint
Specify engines, NodeJS v14.

Auto-fix many linting issues
Manually fix some linting issues

Rename shadowed variables
Replace eval() when calculating frame rate, with string split & explicit division

Disable linting for some warnings.
.gitignore: Ignore /.idea, added by IntelliJ IDEA

I tried adding a new Workflow to execute check, but it failed to install fsevents. I don't know how to fix this using npm, I suggest replacing npm and package-lock.json with yarn and yarn.lock, which behaves better across different systems.
Failing CI step

I'm loving this 😍
Thank you very much!


Identify 10 topics / LOs for Online Training

Goal is to come up with 10 topics/LOs for either CRDB Basics or New in 19.2 online training.

Came up with LOs for CRDB Basics


Module 04 - Conversational AI

This PR introduces the completed Module 04: Conversational AI, covering key concepts in chat agent design and system context management. It includes four notebooks:
Notebook 01: Building Chat Agents
Notebook 02: System Context Management
Notebook 03: Multi-Turn Conversations
Notebook 04: Conversation Memory

on notebook 3 - multiturn conversations, please also demonstrate how to use conversation.add_messages() to add an array of messages in a single call.

on notebook 4, when demonstrating the SessionCacheConversation, please demonstrate the difference between max size and session cache max size.
Max Size relates to how much the model is actually aware of, while session cache size relates to how much the user is able to see printed out.
Imagine that you have created a chat app and you want your users to see the last 100 messages of the conversation, but you only want the model to be aware of the last 3 messages. In this scenario, we would set max size to 3 and set our session cache max size to 100. This way our user can see 100 messages of history, but the ai will only be aware of the last few messages.
This is helpful if we want to keep token cost low but still allow the user to be able to recall previous parts of the conversation.

Alright thanks. On it, Will implement changes now.

Alright thanks. On it, Will implement changes now.

for the notebook 4 I noticed there isn't any parameter to set the session cache size and it only Takes in max size. So demonstrating the differences i  code seem difficult.
OR Do you mean i should compare max size of session_cache conversation and max size of the normal conversation.

@cobycloud I have updated the notebooks with the correction. Thanks

^please correct this. conversation 2 is showing a long model memory and with a longer user chat history
max_size = model memory
session_max_size = user chat history

oh sorry that was an oversight. Correction effected. Thanks


[Jenkins 37801] ViewCredentialsActionTest#smokes and CredentialsStoreActionTest are failing against Jenkins 2.7.3-RC-3

JENKINS-37801
This PR relaxes the smoke tests in ViewCredentialsActionTest and CredentialsStoreActionTest changing from strict string comparison on XML results to XMLUnit's similar comparison ignoring attributes starting with "_"
This way we preserve backwards compatibility and the test is a little (IMHO) more robust to no relevant changes in the XML like adding a _class attribute

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

Edited to clarify the Jenkins version, the test are failing using the stable-2.7 branch

:bee:

@raul-arabaolaza Congratulations!


[Bug report] SortBy() & SortByDesc() is not correct the result when use for collection with more than 16 elements

Laravel Version: 5.5
PHP Version: 7.2
Database Driver & Version:MySQL - 5.7

Description:
I have 1 collection with more than 16 elements, I use both SortBy() & SortByDesc() and the result is not correct.
Steps To Reproduce:
Example :

My arrays :

$arrays =  [
  0 => [
    "number_1" => "0",
    "number_2" => 1,
    "number_3" => 1920001
  ],
  1 => [
    "number_1" => "3",
    "number_2" => 0,
    "number_3" => 1920004
  ],
  2 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920005
  ],
  3 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920006
  ],
  4 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920007
  ],
  5 => [
    "number_1" => "5",
    "number_2" => 0,
    "number_3" => 1920008
  ],
  6 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920009
  ],
  7 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920010
  ],
  8 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920011
  ],
  9 => [
    "number_1" => "4",
    "number_2" => 0,
    "number_3" => 1920012
  ],
  10 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920013
  ],
  11 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920014
  ],
  12 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920015
  ],
  13 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920017
  ],
  14 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920018
  ],
  15 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920019
  ],
  16 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920020
  ],
  17 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920021
  ],
  18 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920022
  ],
  19 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920023
  ],
  20 => [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920024
  ]
];

I use SortBy & SortByDesc on my source code :

$collection = collect($arrays)->sortByDesc('number_1')->sortByDesc('number_2')->values()->all();

And the result is here :

[
     [
       "number_1" => "0",
       "number_2" => 1,
       "number_3" => 1920001,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920013,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920005,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920006,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920007,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920009,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920010,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920011,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920014,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920015,
     ],
     [
       "number_1" => "5",
       "number_2" => 0,
       "number_3" => 1920008,
     ],
     [
       "number_1" => "4",
       "number_2" => 0,
       "number_3" => 1920012,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920019,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920020,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920021,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920022,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920023,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920017,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920024,
     ],
     [
       "number_1" => "3",
       "number_2" => 0,
       "number_3" => 1920004,
     ],
     [
       "number_1" => "1",
       "number_2" => 0,
       "number_3" => 1920018,
     ],
   ]

But it's not correct , the expectation about result same here
$arrays =  [
  [
    "number_1" => "0",
    "number_2" => 1,
    "number_3" => 1920001
  ],
  [
    "number_1" => "5",
    "number_2" => 0,
    "number_3" => 1920008
  ],
  [
    "number_1" => "4",
    "number_2" => 0,
    "number_3" => 1920012
  ],
  [
    "number_1" => "3",
    "number_2" => 0,
    "number_3" => 1920004
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920005
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920006
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920007
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920009
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920010
  ],
  [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920011
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920013
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920014
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920015
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920017
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920018
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920019
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920020
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920021
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920022
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920023
  ],
   [
    "number_1" => "1",
    "number_2" => 0,
    "number_3" => 1920024
  ]
];

But when I use same with above step  for less than 16 elements. It return the correct data.
So How can I fix this issue?

Please see https://github.com/laravel/ideas/issues/11 on why multiple sortBy[Desc]() clauses don't produce the expected result.
The thread also provides a solution: https://github.com/laravel/ideas/issues/11#issuecomment-398873250

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!


Support non-S3 path (MinIO-like)

Is your feature request related to a problem? Please describe.
I've tested the farthest that I was able to - but I couldn't get MinIO to work with Walrus - after loads of debug (public/download policies, IP/port change, new access key/secret, etc, I was not able to use MinIO with Walrus.
I was also not able to find the reason why on the logs - but if you advise me how to find, I'll try my head to send it all here and send you.
Describe the solution you'd like
MinIO, by default, uses:
hostname.tld/bucket-name/object-name, while S3 uses something like bucket-name.hostname.tld/object-name.
Thus, a great way would be to add a switch or a case, if possible, for both situations.
If I'm mistaken, I'm looking forward to correct soon enough - and also contribute to the project if possible! 😄

Thanks for the testing @devlopesbernardo! Amazon s3 sdk creates bucket-name.hostname.tld/object-name and it seems it doesn't work with minIO. But there is an option to force the use of hostname.tld/bucket-name/object-name which is S3ForcePathStyle https://github.com/aws/aws-sdk-go/blob/master/aws/config.go#L127
so updating these lines https://github.com/Clivern/Walrus/blob/main/core/storage/s3.go#L31-L37 to
    return &S3{
        config: &aws.Config{
            Credentials: credentials.NewStaticCredentials(key, secret, ""),
            Endpoint:    aws.String(endpoint),
            Region:      aws.String(region),
            S3ForcePathStyle: aws.Bool(true),
        },
    }

seems solved the issue. I have to 2 options

Add S3ForcePathStyle by default if it will work with minIO, AWS S3 and Digitalocean Spaces (have to test that).
Add option in the dashboard to identify if s3 uses path style or virtual host style and let users decide.

Hey! Thanks for the quick response, @Clivern! Hope that you're feeling nice today =)
I can provide accesses to minIO, S3 and Spaces for manual testing, however I do not really understand a lot of Go to automatically test it (but should be enough to manually test it).
So, for 1:
I should clone the repo, test it with this platforms, working, submit a PR?
For 2, how does this change would affect the backend?
I will dig further into the code asap to understand it better - this is my first contributtion on open source software, so I'm looking for corrections when they're needed :metal:

For the first option, All you need is to add this config value S3ForcePathStyle & test with different s3 providers.
Here is all you need to change & test:

Clone on github then clone locally.
Install golang on your laptop.
Run etcd locally on ubuntu with this command ./bin/local_etcd_ubuntu.sh or this ./bin/local_etcd_mac.sh on mac.
Change walrus go code.
To run the tower locally, run make run_tower then visit http://<IP_ADDRESS>:8000, install and update settings page with s3 configs.
To run the agent locally, run make run_agent.
Backup a file from your laptop to s3 & check logs.
Run code checks with make ci before pushing into github

Needed for Option Two (UI Changes):
You will need nodejs & npm since it is a single page application uses Vuejs. Here is all you need to run the frontend application or to package it in go code.
$ cd web

# Install packages
$ npm install
$ npm install -g npx

# add tower url to frontend
$ echo "VUE_APP_TOWER_URL=http://<IP_ADDRESS>:8000" > .env

$ cd ..

# Run frontend
$ make serve_ui

# To bundle the frontend into go application
$ make package

I'm really grateful for your detailed guide. I do have all of this installed, since I've messed around with go for a while and work on freelacing nodejs.
I will try it as soon as possible. Hope to buy you a beer anytime :beers:


Change current action

Hello,
Currently hvac_action is always heating despite the operation mode I select. Could we change it so it correlates with current mode?

Maybe, I am not really sure when HVACAction should be IDLE. Right now I am comparing input and output temperatures to show what's happening, but maybe it's not the right idea. https://github.com/jvitkauskas/pybls21/blob/e1e3ef6d6356ef6cc45a756df9810ef302cdce72/pybls21/client.py#L109

Should be fixed now


Competitors benchmark

Resources: https://ghost.org/alternatives/

Well I now realize that we're still lacking a proper performance benchmark.
I think it's something we plan to do soon.
So not going to close this one until then.

Putting the performance benchmark in a new issue

It's now added in the documentation


ci: script to validate embedded examples in the asyncapi.md file

Description

This PR adds a script and CI (will added after the script has been finalized) to validate the embedded examples in the asyncapi.md file

Remaining tasks:

[ ] Script enhancement
[ ] Add a CI file integrating the script

Related issue(s):
Resolves #957

Current State of the script
This is what the script currently does as of 915f808:

This initial script replaces the section in the ex-base-doc.json by extracting the json section by taking the comment given in this format <!-- asyncapi-example-tester:{"test":"Info Object","json_path":"$.info"} -->.

Here test is the object which stores the name of the example (will change the name of object later on for better naming convention)
json_path is the object specifying the location where the example should be replaced.

Future objective:

[ ] Update asyncapi.md file with more improved comments
[ ] Integrate the script with CLI validation
[ ] Add a YAML file for the CI

@asyncapi/bounty_team

/bounty

/au

UPDATE
Hi @smoya :wave:

I have almost finished the script and the CI file.
Thought of using parser-js but chose asyncapi-cli due to more verbose error details. Please give your thoughts upon it.
Ran this test to see the working of the script and CI. It seems to be working fine as of now.
Ran into some validation problems which I've sorted them out. I wrote them in a separate document.
For one of files, I'm unsure about what's going wrong so would require your help in debugging that.

Alternate link for more verbose error log

Ran into some validation problems which I've sorted them out. I wrote them in a separate document.

I don't get the whole content of this file. When you mention lines of a document, to which document do you refer? It seems don't match with the spec file so I don't know which other file could be.

For one of files, I'm unsure about what's going wrong so would require your help in debugging that.

Alternate link for more verbose error log

At a glance, seems like a bug in the JSON Schemas, but I'm investigating it

For one of files, I'm unsure about what's going wrong so would require your help in debugging that.

Alternate link for more verbose error log

The issue is because authorizationUrl field **is not part of clientCredentials oauth flow, but tokenUrl. See:

Source: https://www.asyncapi.com/docs/reference/specification/v3.0.0#oauthFlowObject

Ran into some validation problems which I've sorted them out. I wrote them in a separate document.

I don't get the whole content of this file. When you mention lines of a document, to which document do you refer? It seems don't match with the spec file so I don't know which other file could be.

Ah, it's my shortcoming. I've updated the document with reference to the files being mention. Please have a look once again.

Ran into some validation problems which I've sorted them out. I wrote them in a separate document.

I don't get the whole content of this file. When you mention lines of a document, to which document do you refer? It seems don't match with the spec file so I don't know which other file could be.

Ah, it's my shortcoming. I've updated the document with reference to the files being mentioned. Please have a look once again.

Operation-Object.json
1st change and 2nd change
Congrats! You found some bugs in the examples 🎉 The fixes are the ones you mentioned, so 👍
3rd change
In this case, you should not remove lines but fix the example. Operation Messages should point to the messages of the related channel. The $ref should be, for example, #/channels/<channelName>/messages/<messageName>. More on https://www.asyncapi.com/docs/reference/specification/v3.0.0#operationObject.
Message-Example-Object.jso and Operation-Traits-Object.json
Please share more info about the error instead of the fix you did so I can understand what the issue is.

Ran into some validation problems which I've sorted them out. I wrote them in a separate document.

I don't get the whole content of this file. When you mention lines of a document, to which document do you refer? It seems don't match with the spec file so I don't know which other file could be.

Ah, it's my shortcoming. I've updated the document with reference to the files being mentioned. Please have a look once again.

Operation-Object.json
1st change and 2nd change
Congrats! You found some bugs in the examples 🎉 The fixes are the ones you mentioned, so 👍
3rd change

Thank you! :pray: I suspected that was the case... :eyes:

In this case, you should not remove lines but fix the example. Operation Messages should point to the messages of the related channel. The $ref should be, for example, #/channels/<channelName>/messages/<messageName>. More on https://www.asyncapi.com/docs/reference/specification/v3.0.0#operationObject.

Let me check this again. Will report you back.

Message-Example-Object.jso and Operation-Traits-Object.json
Please share more info about the error instead of the fix you did so I can understand what the issue is.

@smoya I've updated the document to reflect the same. PTAL.

Operation-Object.json
1st change and 2nd change
Congrats! You found some bugs in the examples 🎉 The fixes are the ones you mentioned, so 👍

@smoya shall I make the changes in this PR?
Or open an issue and the corresponding PR fixing it?

Operation-Object.json
1st change and 2nd change
Congrats! You found some bugs in the examples 🎉 The fixes are the ones you mentioned, so 👍

@smoya shall I make the changes in this PR? Or open an issue and the corresponding PR fixing it?

I would say you can open another PR against your branch embedded-examples-validation so you can demonstrate THIS PR will make CI failing but the other contains the fixes. Then you can merge it later.
But not a really big deal, up to you.

Operation-Object.json
1st change and 2nd change
Congrats! You found some bugs in the examples 🎉 The fixes are the ones you mentioned, so 👍

@smoya shall I make the changes in this PR? Or open an issue and the corresponding PR fixing it?

I would say you can open another PR against your branch embedded-examples-validation so you can demonstrate THIS PR will make CI failing but the other contains the fixes. Then you can merge it later.
But not a really big deal, up to you.

@smoya
I'm thinking that a separate issue and a PR approach would be much more neat and manageable for this task. I should keep this PR as issue-oriented as possible
I can create a new issue by referencing the appropriate comment for it, immediately after this PR is merged :+1:
Thanks!

UPDATE
@smoya

So I was testing further on the json merge patch in a separate branch, to keep this branch untouched for the time being.

All the files are being validated as expected after the json merge patch integration except for Operation Object and Security Scheme OAuth Flow Object

The updated version of the script. (naming is different)

The error for Operation Object is like this:

Warning in Operation Object-json-format: "0" property must have required property "type"
Warning in Operation Object-json-format: "0" property must not be valid
Warning in Operation Object-json-format: Property "petstore_auth" is not expected to be here
Warning in Operation Object-json-format: Operation message does not belong to the specified channel.

This is the specified section it's referring to.

The error for Security Scheme OAuth Flow Object is like this:

Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "in"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "scheme"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "name"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "openIdConnectUrl"
Warning in Security Scheme OAuth Flow Object-json-format: Property "flows" is not expected to be here
Warning in Security Scheme OAuth Flow Object-json-format: "clientCredentials" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: Property "scopes" is not expected to be here
Warning in Security Scheme OAuth Flow Object-json-format: Property "flows" is not expected to be here
Warning in Security Scheme OAuth Flow Object-json-format: "clientCredentials" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: Property "scopes" is not expected to be here
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "in"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "scheme"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "name"
Warning in Security Scheme OAuth Flow Object-json-format: "0" property must have required property "openIdConnectUrl"
Warning in Security Scheme OAuth Flow Object-json-format: "oauth" property must have required property "in"
Warning in Security Scheme OAuth Flow Object-json-format: "oauth" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: "oauth" property must have required property "scheme"
Warning in Security Scheme OAuth Flow Object-json-format: "oauth" property must have required property "name"
Warning in Security Scheme OAuth Flow Object-json-format: "oauth" property must have required property "openIdConnectUrl"
Warning in Security Scheme OAuth Flow Object-json-format: Property "flows" is not expected to be here
Warning in Security Scheme OAuth Flow Object-json-format: "clientCredentials" property must not be valid
Warning in Security Scheme OAuth Flow Object-json-format: Property "scopes" is not expected to be here

This is the specified section it's referring to.

There's also one more thing that has been changed in that script. As far as I've understood (please correct me if I'm wrong), for the arrays present in the document, the nature of merge patch is such that it doesn't applied to arrays, and it ignores them or treat it like an object.
The following is an excerpt from the RFC 7396:

There are a few things to note about the function.
If the patch is anything other than an object,
the result will always be to replace the entire target with the entire patch.
Also, it is not possible patch part of a target that is not an object,
such as to replace some of the values in an array.

So keeping this in mind, what I did is that added a check for an array in the script and made this modification in the comments for the jsonPointer of the two array objects: one, two. After that modification, it actually adds the content inside the arrays.
Specific commit where the change was made
I suspect that the errors in the two files above are also due to the nature of the merge patch. Let me know what you think about this whole scenario.

Thanks! :+1:

@AnimeshKumar923 just for the record, I shared with you via Slack DM the fixes of such examples (Yeah, your script is making us discovery errors on the examples! 🎉 👏  ).
Regarding the following:

So keeping this in mind, what I did is that added a check for an array in the script and made this modification in the comments for the jsonPointer of the two array objects: one, two. After that modification, it actually adds the content inside the arrays.

You are pointing to examples with a JSON Pointer such as #/operations/sendUserSignUp/traits/0. That JSON Pointer is not pointing to an array but an object. The element 0 of such an array is a trait object, so I don't think you should find any issue right? I would expect such replacement only if you specify something like #/operations/sendUserSignUp/traits (without the zero index at the end) but it's not the case.

@AnimeshKumar923 just for the record, I shared with you via Slack DM the fixes of such examples (Yeah, your script is making us discovery errors on the examples! 🎉 👏 ).

Thank you! :bow:

Regarding the following:

So keeping this in mind, what I did is that added a check for an array in the script and made this modification in the comments for the jsonPointer of the two array objects: one, two. After that modification, it actually adds the content inside the arrays.

You are pointing to examples with a JSON Pointer such as #/operations/sendUserSignUp/traits/0. That JSON Pointer is not pointing to an array but an object. The element 0 of such an array is a trait object, so I don't think you should find any issue right? I would expect such replacement only if you specify something like #/operations/sendUserSignUp/traits (without the zero index at the end) but it's not the case.

Yes, that is happening in this case here.
So what I observed was that, if we specify this JSON Pointer --> #/operations/sendUserSignUp/traits, it doesn't adds the structure inside the traits array.
And when we use this Pointer instead --> #/operations/sendUserSignUp/traits/0, it add the structure inside the array.

And when we use this Pointer instead --> #/operations/sendUserSignUp/traits/0, it add the structure inside the array.

And this is not enough? I mean, isn't that what you wanted to do?

And when we use this Pointer instead --> #/operations/sendUserSignUp/traits/0, it add the structure inside the array.

And this is not enough? I mean, isn't that what you wanted to do?

@smoya
Yes that's what I wanted. I'm not objecting anything here, I was just stating my observations to you that ''we are following this approach here, and this is what's happening currently" :+1:

Current State of PR
Summary of PR as of 5e1b0be.
Contents required for the validation:

Spec document that contains the embedded examples.

The main script validate-embedded-examples.js which does the validation.

The base document that is utilized by the script, along with the extracted example, to construct a fully valid AsyncAPI document.

An external Avro Scheme file that is referenced in multiple locations in the spec.

Workflow file which is triggered on incoming PR and checks spec examples.

Flow of the validation

Workflow is triggered on every incoming PR.
The script is then executed: (a brief flow)

The spec file is loaded in the memory
The markdown comment and example are extracted. Each component of the comment and the corresponding example is stored in its separate property of the object. The object is stored in an array.
All the metadata is then collected and stored in the combinedData array.
Then for each example present in the combinedData array, a full AsyncAPI document is constructed and validated using the parser-js.
If all goes well, it gives the message All examples validated successfully!. Otherwise, we get the error(s) with the file name and the error output.

Remaining tasks

[ ] Remove non-essential files
[ ] A test run for the workflow at the current branch
[ ] Final review from @smoya

[ ]  Remove non-essential files
[ ]  A test run for the workflow at the current branch
[ ]  Final review from @smoya

👍
And for the record, can you confirm you will work, after merging this (non-related with the Bounty issue) on moving all this knowledge into proper documentation about how validation happens?

[ ]   Remove non-essential files
[ ]   A test run for the workflow at the current branch
[ ]   Final review from @smoya

👍
And for the record, can you confirm you will work, after merging this (non-related with the Bounty issue) on moving all this knowledge into proper documentation about how validation happens?

Yes, gladly! I have added that task.

Workflow Test Runs

Workflow fails: https://github.com/AnimeshKumar923/asyncapi-spec/actions/runs/9806341756/job/27077848952

Workflow passes: https://github.com/AnimeshKumar923/asyncapi-spec/actions/runs/9806389937/job/27078005627

/rtm

https://github.com/asyncapi/spec/pull/1059#issuecomment-2210485497


Mega Drive: FM Audio example where PSG Audio example should be

https://www.copetti.org/writings/consoles/mega-drive-genesis/#functionality

Sorry if I formatted this incorrectly as this is my first GitHub issue.

Fixed, thanks


documentation: Edit README and getting-started for grammar, flow and …

…consistency
Please ensure that your pull request adheres to our contribution guidelines. Thank you!

@adambmarsh please remove the merge commit from the history.


Update: Restructure Readme Template

When creating a Readme file, include:

Readme title

Readme subtitle (optional)

Table of Contents
Description

Sub-headers and subsequent text

Resources Used
Usage (Getting Started)
Contributors
Contact Information

Commit 4bdc840 Update

Refactored the generateMarkdown function to accurately reflect the changes.


cross publish to 2.12

closes #71

Codecov Report

Merging #72 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #72   +/-   ##
=======================================
  Coverage   74.09%   74.09%
=======================================
  Files          15       15
  Lines         772      772
  Branches      106      119   +13
=======================================
  Hits          572      572
  Misses        200      200

I made these changes mechanically. I haven't tried publishing local yet and insuring no weird runtime issues happen. I was planning on doing that sometime this week.

Thanks for taking care of this @joprice, let me know if it works.

[ ] Test publishLocal
[ ] Test the package at runtime

Any update on testing, @joprice ?

Unfortunately, I haven't had the time yet. I'll try to test it tomorrow.

I was able to +publishLocal and use this locally in a project and it worked as expected.

This looks great @joprice. I'll work on merging this and publishing


feat: add event.method and event.headers

🔗 Linked issue
#423, #73

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This PR adds event.method and event.headers support.
📝 Checklist

[x] I have linked an issue or discussion.
[ ]  I have updated the documentation accordingly.

Thanks for the PR! I've made a couple of updates:

Use a getter with lazy evaluation and keep the public interface read-only.

Similar to _handled we have an internal way to override them. Not to be advised.

Fix tests for Node 16 not having global Headers. In H3 we have a working polyfill but thinking to not include it in base bundle.


Unread count api

Hi, I;m author from ShortcutBadger
Can you help me to provide api to set unread count for apps like other launchers?

Can you email<EMAIL_ADDRESS>with details of what you're after?

Thanks for your reply, I have email to you!


Zero-width emotes can't be last on line when text wrapped

Describe your issue
Zero-width emotes can't be last on line when text wrapped. See screenshot
Screenshots

Right most row of pepeL emotes is not covered in cvHazmat. The cvHazmat emotes instead are wrapped to new line
OS and Chatterino Version
OS: Linux mainPC 5.10.0-8parrot1-amd64 #1 SMP Debian 5.10.46-8parrot1 (2021-07-21) x86_64 GNU/Linux
Chatterino: Chatterino 7.3.3 (commit 20a7127)

Just as a note, while we call them zero width emotes both in chat and in code, they are technically full width emote with a negative X margin - that's why they behave like this.
Changes would need to be made to the text-wrapping code to take into account the MessageElementFlag::ZeroWidthEmote when doing the MessageLayoutContainer::fitsInLine call

This issue is probably related - if you post one of those emotes at the beginning of the message without another emote to put it onto, it gets displayed on top of the username

This issue is probably related - if you post one of those emotes at the beginning of the message without another emote to put it onto, it gets displayed on top of the username

This was mentioned in #1433 and even though it's unintended I think it presents more options for creative use than issues, especially with some 7tv zero-width emotes relying on this "bug".
Even though that's a third party thing and doesn't present issues in this project specifically, I still think it should be considered since any changes made to zero-width emotes here would affect the way 7tv zero-width emotes work in their fork as well.


Device option is ignored on Mac OS

https://github.com/MexXxo/node-microphone/blob/ba88bc30b782eeb4f67c452da9bb4e8c5a8be9c7/index.js#L57-L63

I can't test on a mac right now, can we add the device option to mac? If yes, do you have a manual / cmd api description for me?

If you want to provide a PR to add the device option for mac, please also add yourself to the contributors :-)

I could not test on Mac for other reasons, but the highlighted lines from my link show that the option is not used in the spawn() call, while it is used for Linux and Windows.
I guess you could use it in a similar way as Windows (since it’s also Sox). I did not make a PR because I don’t know Sox well and I have not had time to read some doc about it yet.


Fix generated JsonDesererialzer Java code errors

Fixes #66.
Changes proposed in this pull request:

Fix bad case in serializer.py
Add a Java test

@anz-bank/sysl-developers

So I was wrong about the PR not referencing the the issue - there it is right up front. I guess I missed it because I go straight to the commits. I'll pay more attention next time.


[Runtime] Choose the serialization method based on content type

Motivation
See https://github.com/apple/swift-openapi-generator/issues/43 for details. This PR also resolves https://github.com/apple/swift-openapi-generator/issues/42.
This PR introduces the initial content-type-aware coding strategy, which is likely to get expanded in the future.
Modifications
This PR covers the scope described in issue 43 - handling a type: string appropriately, based on whether it's wrapped in application/json or text/plan content.
It introduces new variants of the SPI helper functions, which now has variants per "coding strategy". It's best to read https://github.com/apple/swift-openapi-generator/pull/48/files?short_path=aa92e58#diff-aa92e58fb5a311512cfcd285827a4aa2e6634cae7fdfe0090bd2cfc7b0986140 for details.
Deprecated all of the SPI methods that didn't contain the coding strategy parameter, to be removed in the next breaking version.
Result
We now have explicit control over the coding strategy for ambiguous types, such as String, which conform to both Codable and LosslessStringConvertible, to be taken advantage of by the generator (see the paired PR).
Test Plan
Verified that the default behavior now matches version 0.1.0, and when paired with the updated generator, fully resolves issue 43.
Used code coverage to ensure that Converter+{Common,Client,Server}.swift are now 100% unit tested.

@simonjbeaumont Okay, based on our discussion, I split the CodingStrategy into two: ParameterCodingStrategy and BodyCodingStrategy, as they have different requirements. Ready for your re-review.

@simonjbeaumont This is now ready. It's exactly what we discussed and already codified requirements for in https://github.com/apple/swift-openapi-generator/pull/50
Now, this is a large PR and is by no means perfect, but it's a solid move in the right direction. There are things I'd like to improve in the future, but I wouldn't want to hold this PR open for it.
It's very repetitive, as we're doing ~50 variants of similar logic, but I took special care, and all the methods are unit tested and used in our integration test in the generator repo, so I'm confident that this logic is at least as good as what we have in 0.1.0.


No PLL lock with recordings from Meteor M2 since v0.3

I have recordings from Meteor M2 which can be sucessfully demodulated by version v0.2.1 but not with v0.3. meteor_demod is unable to get PLL lock. For the moment, I use v0.2.1 for M2 and v0.3 only for M2-2 recordings.
A full recording from M2 is available at https://chaospixel.com/pub/rtlsdr/meteor_demod/broken/gqrx_20190908_085103_137100000_140000_fc.wav
I've tried it with meteor_demod *.wav and meteor_demod -m qpsk -r 72000 without luck.

Hi,
Commit a54192b should have fixed the issue with the PLL not locking. If you could build the 'devel' branch and check whether the problem is still there, that'd be fantastic.

Verified that it's fixed with the latest devel branch. Thank you!


importing 'android-keyboard' gradle project takes forever

hey guys thank you for built and improving this beautiful keyboard,
but every time i open Android-keyboard project in android studio it try to importing gradle project that take forever and never finished successfully so please guide me to find out how to use your beautiful project.
Importing 'Android-Keyboard' Gradle project
Gradle: Download keyboardkernel-1.3.14.pom
at the end:
build.gradle: DSL element 'android.dataBinding.enabled' is obsolete and has been replaced with 'android.buildFeatures.dataBinding'.
It will be removed in version 5.0 of the Android Gradle plugin.
Affected Modules: app
Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could not resolve com.nlptech.zengine:keyboardkernel:1.3.14.
Show Details
Affected Modules: app
Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve com.nlptech.zengine:keyboardkernel:1.3.14.
Show Details
Affected Modules: app
Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.nlptech.zengine:keyboardkernel:1.3.14.
Show Details
Affected Modules: app
thank you for your attention
best regards

replace
classpath 'com.android.tools.build:gradle:4.1.0'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.4.10"

Hy there
I have used latest classpath but issue still remains. This lib takes forever to build. Kindly tell me how can I use this.

@ghanimkhan
classpath 'com.android.tools.build:gradle:4.2.2'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.30"
I am using this. but still not working.


dapr register actor  failed to receive placement table update from placement service: EOF

/area runtime
/area placement

Ask your question here
dapr register actor  failed to receive placement table update from placement service: EOF.
i use the endpoint GET http://localhost:<appPort>/dapr/config, gets the registered actors types for this app and the Dapr actor configuration settings.
func main() {
	http.HandleFunc("/dapr/config", func(w http.ResponseWriter, r *http.Request) {
		response := `{
			"entities":["actorType1", "actorType2"],
			"actorIdleTimeout": "1h",
			"actorScanInterval": "30s",
			"drainOngoingCallTimeout": "30s",
			"drainRebalancedActors": true
		}`
		fmt.Println("response", response)

		w.Write([]byte(response))
	})

	fmt.Println("starting HTTP server....")
	http.ListenAndServe(fmt.Sprintf(":%s", port), nil)
}

error logs
== DAPR == time="2020-11-24T17:09:42.427020459+08:00" level=info msg="starting connection attempt to placement service: localhost:50005" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:42.43034532+08:00" level=info msg="established connection to placement service at localhost:50005" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:42.92922055+08:00" level=warning msg="failed to receive placement table update from placement service: EOF" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:42.929358403+08:00" level=info msg="starting connection attempt to placement service: localhost:50005" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:42.933580551+08:00" level=info msg="established connection to placement service at localhost:50005" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:43.430323487+08:00" level=warning msg="failed to receive placement table update from placement service: EOF" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

== DAPR == time="2020-11-24T17:09:43.430386667+08:00" level=info msg="starting connection attempt to placement service: localhost:50005" app_id=actorapp instance=dybxin scope=dapr.runtime.actor type=log ver=0.11.2

@dybxin Please try to use dapr 1.0.0-rc.1 we have lots of improvement in 1.0.0-rc.1
curl -fsSL https://raw.githubusercontent.com/dapr/cli/master/install/install.sh | /bin/bash -s 1.0.0-rc.2

dapr init --runtime-version=1.0.0-rc.1

@youngbupark  I tried version 1.0.0-rc.1.  and i use the way mentioned above to register actors, however, i not find it in dashboard.

logs:
ℹ  Starting Dapr with id actorapp.    This will block until the app is listening on that port." app_id=actorapp instance=dybxin scope=dapr.runtime type=log ver=1.0.0-rc.1

ℹ  Updating metadata for app command: go run main.go
✅  You're up and running!  Status: Running. Init Elapsed 1615.381475ms" app_id=actorapp instance=dybxin scope=dapr.runtime type=log ver=1.0.0-rc.1

== DAPR == time="2020-11-25T18:25:22.076659421+08:00" level=info msg="placement tables updated, version: 0" app_id=actorapp instance=dybxin scope=dapr.runtime.actor.internal.placement type=log ver=1.0.0-rc.1

== DAPR == time="2020-11-25T18:25:24.108337788+08:00" level=info msg="placement tables updated, version: 1" app_id=actorapp instance=dybxin scope=dapr.runtime.actor.internal.placement type=log ver=1.0.0-rc.1

@dybxin the dashboard shows the current activated actors, not actor types. So please try to invoke actor by actor client. then you will be able to see the activated actors.

@youngbupark  Hi, I'm sorry. I don't understand where I am going to get actorID? and i can't activating an actor via http or grpc endpoints?  and i can only pass the example likely .NET SDK Demo to activing an actor?

@youngbupark Hi, I'm sorry. I don't understand where I am going to get actorID? and i can't activating an actor via http or grpc endpoints? and i can only pass the example likely .NET SDK Demo to activing an actor?

Activation/deactivation are managed by Dapr actor runtime. You do not need to care about it. Activation happens when you first call actor via method invocation. Please see this api reference - https://github.com/dapr/docs/blob/master/daprdocs/content/en/reference/api/actors_api.md#invoke-actor-method
dotnet actor sdk also provides crafted api for the users. Here is the example to invoke actors in C#.
When you use remoting call style:
https://github.com/dapr/dotnet-sdk/blob/6c271262231c41b21f3ca866eb0d55f7ce8b7dbc/samples/Actor/ActorClient/Program.cs#L86
When you use non-remoting call:
https://github.com/dapr/dotnet-sdk/blob/6c271262231c41b21f3ca866eb0d55f7ce8b7dbc/samples/Actor/ActorClient/Program.cs#L75-L76
Try to run Actor example. then you can see the actors on dashboard.

@youngbupark thanks a lot. i execute the following application.
const express = require('express');
const bodyParser = require('body-parser');
const app = express();
app.use(bodyParser.json());
const cors = require('cors');

const port = 3000;

app.use(cors());

app.get('/dapr/config', (_req, res) => {
  res.json({
    "entities":["add"],
    "actorIdleTimeout": "1h",
    "actorScanInterval": "30s",
    "drainOngoingCallTimeout": "30s",
    "drainRebalancedActors": true
  });
});

app.post('/add', (req, res) => {
  let args = req.body;
  const [operandOne, operandTwo] = [Number(args['operandOne']), Number(args['operandTwo'])];

  console.log(`Adding ${operandOne} to ${operandTwo}`);

  let result = operandOne + operandTwo;
  res.send(result.toString());
});

app.listen(port, () => console.log(`Listening on port ${port}!`));

dapr run --app-id addapp --app-port 3000 --dapr-http-port 3500 node app.js

use postman

find error:
{
    "errorCode": "ERR_ACTOR_INVOKE_METHOD",
    "message": "error invoke actor method: error from actor service: <!DOCTYPE html>\n\n\n<meta charset=\"utf-8\">\n<title>Error</title>\n\n\n
Cannot PUT /actors/add/addapp/method/add
\n\n\n"
}

the dashboard:

You didn't implement deactivation and invocation endpoint on your application.
Please see this - https://docs.dapr.io/reference/api/actors_api/#http-request-10
This python-SDK implementation will give you more hint to implement actor appcallback layer. - https://github.com/dapr/python-sdk/blob/3570ec3c1db1a0cda93a8632c51a3a58d25bea97/ext/dapr-ext-fastapi/dapr/ext/fastapi/actor.py#L76

@youngbupark ok,thanks a lot.


Fashion Product Search System

Hi Mczhuge, just to know is there any plan to open source the fashion product search demo system to try this in real time ? :)

Not ready yet. But there is a related work done this: https://github.com/UKPLab/MMT-Retrieval


Fix handling of null jq expressions and improve testing coverage

Issues
Refactor - https://github.com/OpsLevel/team-platform/issues/278
Also removes logging - https://github.com/OpsLevel/team-platform/issues/218
Changelog

[ ] TODO

Tophatting

Re-opening as a DRAFT PR, since changes might need to be extracted from here.


[RFE] 1.29 support

Please tell me when the k8s1.29 support plan will be released. This is a matter of concern. Thank you.

This appears to be being tracked in https://github.com/rancher/rancher/issues/43110

@yybht155 https://github.com/rancher/rancher/releases/tag/v2.9.0 supports 1.29 and the chart has been released in rancher-latest

Closing as duplicate


Refactor: Imports and embed fs

What this PR contains:

Refactors some package imports.
Embed fs in it's standalone package and use it elsewhere.
Removed initialization and move initialization closer to command definition.

Look's like my embedding changes breaks something.
Taking a loot at it now.

Fixed embedding issue.
Checking args initialization issue now.


Redesign: Keep certain functions always visible

Examples are: [ Add User ], [ New Issue ], [ Add Tag ] and so on...

What this issue is for?

Just a reminder to keep certain buttons from scrolling out of view in later (redesigned) versions.

Obsolete. Redesign templates are coming anyway.


Allow integration of repeat expansions

Is your feature request related to a problem? Please describe.
We currently cannot properly include repeat expansion, e.g., as called by expansion hunter.
Describe the solution you'd like
Integrate expansion hunter output files.
Describe alternatives you've considered
N/A
Additional context

we need to decide how to properly encode this as small variants

Some comments regarding repeat expansion formats:
https://github.com/Illumina/ExpansionHunter/blob/master/docs/06_OutputVcfFiles.md
Example repeat expansion output by expansionhunter:

The genotype field might be almost unusable and we will need to somehow convey the information for the number of repeats contained. Some issues:
The range of repeats considered normal can vary greatly. Should this kind of information be stored somewhere? Expansionhunter results are already being transferred for CADS and it would be very useful to integrate it in some manner.

A good database for info on repeats is stripy: https://stripy.org/database
Still need to check their data usage permissions.