Share authentication COOKIES between .NET 6 Core App and .NET 4.8 Application with FormAuthentication

Hello Everyone,
I have a legacy application which is built in .NET 4.8 with FormsAuthentication (Membership) in it and now I need to migrate this to newer .NET 6 version so I have created a new .NET 6 Core App. The idea is to create a COOKIE from  .NET 6 Core API which can be shared with .NET 4.8 application. I have generated the COOKIE successful from .NET 6 and sent it to .NET 4.8 app but it did not work as FormsAuthentication does not seem to work with this.
I need some guidance to resolve this blocker so that would be great if anybody can help.
@guardrex  @Rick-Anderson
Thanks,
Sohaib

Hello @sohaibameenpk007 ... The only guidance that we keep is ...
https://learn.microsoft.com/en-us/aspnet/core/security/cookie-sharing?view=aspnetcore-7.0
... in particular, see this section ...
https://learn.microsoft.com/en-us/aspnet/core/security/cookie-sharing?view=aspnetcore-7.0#share-authentication-cookies-between-aspnet-4x-and-aspnet-core-apps
I'm going to close now because that's all that we have on it. If you run into trouble or have a different situation with your apps to address, we recommend chatting with devs on the usual support forums around the Net ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter


docs(vectorstores/integrations/chroma): Fix loading and saving

Description: Fix loading and saving code about Chroma
Issue: the issue #7436
Dependencies: -
Tag maintainer: @rlancemartin, @eyurtsev
Twitter handle: https://twitter.com/ftnext

thanks @ftnext!


test: Simplify DNS proxy port / TFTP source port conflict test.

Since we address NodePort in k8s2 using the DNS proxy port of k8s2 as
the source port from k8s1, one round is enough regardless of the
backend selection, as in both cases the replies are reverse NATted at
k8s2 (where the port conflict was happening before it was fixed by
#12248).
Fixes: #12336
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

test-me-please

Coverage decreased (-0.03%) to 36.927% when pulling c55927c32f6eeac680fece7ed39f9ec9b436bdf2 on pr/jrajahalme/test-simplify-tftp-dns-collision-test into 53c17cd91fbabfa4490e367862b6c5a9f238ff1d on master.


dropdown's within the navbar are sluggish and intermittent

http://www.frostjedi.com/terra/scripts/demo/metis.html
Sometimes the #problem <ul> "opens" with a height of 0px and when it doesn't it opens sluggishly. I don't think the description I gave is very helpful but hopefully the link will demonstrate what I mean.

@terrafrost
In the example you are trying to do, the bootstrap dropdown plugin and the metisMenu plugin are conflict. You should choose only one.


[SPARK-48263] Collate function support for non UTF8_BINARY strings

What changes were proposed in this pull request?
collate("xx", "") does not work when there is a config for default collation set which configures non UTF8_BINARY collation as default.
Why are the changes needed?
Fixing the compatibility issue with default collation config and collate function.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added tests.
Was this patch authored or co-authored using generative AI tooling?
No.

Please take a look :) @uros-db @stefankandic @nikolamand-db

btw, I'd say that this PR does introduce some user-facing changes - so I'd update the PR description to reflect this with more details

thanks, merging to master!


How the properly upload an image to Mastodon

Question
How to properly upload an image to Mastodon
        try {
            const client = await this.Login()
            const media_url = "https://i.pinimg.com/originals/aa/11/c9/aa11c95b8aa4be2220b4def9bf48b18a.jpg";
            const image_blob = await fetch(media_url).then(res => res.blob());
            const result = client.postMediaAttachment({file:image_blob});
            console.log((await result).json.id);
        }
        catch (error) {
            console.error(error);
        }

}

this is how I am currently handling this, however this results in failure but with the status code 200
  failed: true,
  json: {
    id: '111059411755644935',
    type: 'image',
    url: 'https://files.botsin.space/media_attachments/files/111/059/411/755/644/935/original/871c258c14cf28b8.jpeg',
    preview_url: 'https://files.botsin.space/media_attachments/files/111/059/411/755/644/935/small/871c258c14cf28b8.jpeg',
    remote_url: null,
    preview_remote_url: null,
    text_url: null,
    meta: { original: [Object], small: [Object] },
    description: null,
    blurhash: 'UTRo:D$~?]IXiuoLo~j[_MIqD+%Kbxogs+Rj'
  },
  path: 'media',
  response: Response {
    [Symbol(realm)]: null,
    [Symbol(state)]: {
      aborted: false,
      rangeRequested: false,
      timingAllowPassed: true,
      requestIncludesCredentials: true,
      type: 'default',
      status: 200,
      timingInfo: [Object],
      cacheState: '',
      statusText: 'OK',
      headersList: [HeadersList],
      urlList: [Array],
      body: [Object]
    },
    [Symbol(headers)]: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    }
  },
  status: 200,
  rateLimit: 30
}`

Package (please complete the following information):

Source: [NPM]
Version [0.4.0]

Hello, @SkyMTF!
Thank you for the report. This is a bug in the library. The validation of the JSON response expects a focus point, which is not necessarily present as seen in you response example.

Hello @SkyMTF,
please take a look at PR #31, install the related branch with
npm i --no-save github:typescriptlibs/tsl-mastodon-api.git#bugfix/30-image-post-validation

and check if the bugfix is working for you.

I can confirm that it works and I no longer get an error

Thank you for testing!


Fix #2026, CFE_FS_ParseInputFileNameEx avoid uninit var

Describe the contribution

Fix #2026
Uses input buffer if default is NULL to set output to avoid uninitialized variables in unit test

Testing performed
Build/run unit tests with valgrind, eliminates warning
Expected behavior changes
Unit test only
System(s) tested on

Hardware: i5/Docker
OS: Ubuntu 18.04
Versions: Bundle main + this commit

Additional context
I wonder if this would have been caught sooner if we had a different bucket for "critical" static analysis checks.
Third party code
None
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB:2022-01-19 APPROVED


Mac Version

I know there was a version of this for Mac at one point in time, but I don't see it here. Where is it?

It has not been updated for a long time. Scroll all the way back to 2.0.3
It is, however, 32-bit, not 64-bit as will be required in the next macOS release.

how do i open it on mac

you could compile it for mac (maybe), it is C#


tes/list: hitting max response size limits

On a project using boltdb and a relatively small amount of tasks + logs, I'm getting errors and slowness from dashboard.
./funnel task list
Error: [STATUS CODE - 403]	{"error":"grpc: trying to send message larger than max (8044641 vs. 4194304)","code":8}

The web dashboard doesn't load. The terminal dashboard works, but is very slow.

Possible solution: https://jbrandhorst.com/post/grpc-binary-blob-stream/

I think it's good that it's failing. An 8MB response is too much. Probably just need to optimize the clients to return smaller pages by default.

Also interesting, the majority of the message weight comes from the OutputFileLog which is part of the basic view.


Not being able to configure bodyParser limit from http.js file

As suggested in the documentation here: https://sailsjs.com/documentation/reference/configuration/sails-config-http#?configuring-skipper, I did uncomment the configuration as follows,
module.exports.http = {
middleware: {
order: [
   'cookieParser',
   'session',
   'bodyParser',
   'compress',
   'poweredBy',
   'router',
   'www',
   'favicon',
 ],

bodyParser: (function _configureBodyParser(){
   var skipper = require('skipper');
   var middlewareFn = skipper(
     {
       strict: true,
       limit: '50mb'
     }
     );
   return middlewareFn;
})(),

},
};
Even after this, I am not being able to upload files which are more than 1 MB.
Skipper Version being used: "sails": "^1.0.2"
Sails version being used: "skipper": "^0.8.7"

Hi @kiranattilicho,
Just wanted to give you a heads up that we are moving all open Sails issues into one repo.
~Cheers!

Hi @kiranattilicho, I was looking into the docs and it appears that limit is not listed as available to configure in the bodyParser. Have you been able to add maxBytes: 3000000 to your actions to control the size of your uploads?


Reintroduce option webhook.enable

Purpose of this PR
Close #2137.
Proposed changes:

Reintroduce option webhook.enable
The webhook is enabled by default, but users can choose to disable the webhook server when webhooks are forbidden in K8s

Change Category
Indicate the type of change by marking the applicable boxes:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] Feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that could affect existing functionality)
[ ] Documentation update

Rationale
Checklist
Before submitting your PR, please review the following:

[x] I have conducted a self-review of my own code.
[ ] I have updated documentation accordingly.
[x] I have added tests that prove my changes are effective or that my feature works.
[x] Existing unit tests pass locally with my changes.

Additional Notes

/assign @vara-bonthu @jacobsalway


General Grievance: Watch softude.com

General Grievance requests the watch of the watch_keyword softude\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

softude\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Feedly has probably changed something and selectors may need updating

Hi!
The extension seems to have stopped working. I fiddled a little with the code and, altough I'm no real programmer, it seems to me that the selectors may need to be updated. For instance, for closed title only articles it seems that it needs to be changed for ".entry--selected a.entry__title"...
Regards

Here's a different extension that does the same thing (and is currently working): https://chrome.google.com/webstore/detail/feedly-background-article/oilgpoalabnhlfokadagigcpjhnoailn/related?hl=en


Monomorphiser eliminates main

f p = p

g p = f p

main = g 1

The main function is eliminated and we get:
*** Exception: No main function present!

CallStack (from HasCallStack):
  error, called at /Users/abhiroopsarkar/C/Sense-VM/frontend/CamIoT/src/Desugaring/Desugar.hs:33:27 in main:Desugaring.Desugar

A possible fix from @Rewbert
In Renaming.hs
    DTypeSig id t       -> do
        b <- isRenamed id
        if b
            then do ds' <- renameDef ds
                    return $ DTypeSig id t : ds'
            else do id' <- fresh
                    inEnv (id, id') (do ds' <- renameDef ds
                                        return $ DTypeSig id' t : ds')

and in Desugar.hs Line #114 and and #115
desugarMain m [AST.DTypeSig _ _, def]    = desugarMain m [def]


WIP: python3Packages.bokeh: 1.4.0 -> 2.0.1

Tests still don't function. Somehow fixtures cannot be found causing massive failures...

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

note 2.0.2 has been tagged

pushed 2.0.2 in 491b4dafe6228bf2399bb0806157a50da8e68e5c (note incorrect commit message)


Pin Blocks for Organizational Purposes

For advanced developers it would be nice if we could pin the blocks
function A upper left
function B upper right
etc
This would help keep our code organized when bouncing between JS and blockly
Obviously in the real world we code from top to bottom and left to right (In most countries)
So if we could pin blocks even though we bounce between JS and blockly we would know where our code is if we pinned it.
Right now I would organize my blockly, Go to JS, Add a little JS, and then when I go back to the blockly it is all unorganized again.
Not really a big deal on small projects but I have one with like 6 bigger functions and it quickly becomes a mess.
Thanks In Advance

@jaygriggs are you asking for microbit?


I want to use different color for different dates selected in view didload??  I used the latest version

IMPORTANT - BEFORE CREATING YOUR ISSUE PLEASE READ THE FOLLOWING:

PLEASE STATE THE VERSION NUMBER you are using.
Are you using the latest version of JTAppleCalendar? Latest version is currently 7.1.5
PROVIDE ENOUGH INPORMATION SO I CAN RECREATE THE PROBLEM.

This library is a UICollectionView (similar to a UITableView)
The same way you would have different colors for a collectionViewCells or tableViewCells, is the exact same way you would do it for this library.

closing issue.
If you still need help then let me know.


bundle install fatal error

Installing linecache19 (0.5.12) Unfortunately, a fatal error has occurred. Please report this error to the Bundler issue tracker at https://github.com/carlhuda/bundler/issues so that we can fix it. Thanks!

Please provide your Gemfile, the full output of Bundle install and information about what system you are running this on

Please also see ISSUES on troubleshooting and instructions to provide. This is usually due to missing libraries needed to compile this gem.

let's close this.  I think I have other issues with versions.


Resolving Recursive References

This might already be a known issue, but I haven't found anything exact. There seems to be an issue resolving external references that are recursive. Here's an example (a bit contrived, but narrowed down to the essentials):
foo.yaml:
Foo:
  type: object
  properties:
    bar:
      type: object
      properties:
        foo:
          $ref: '#/Bar'

bar.yaml:
Bar:
  type: object
  properties:
    foo:
      $ref: '#/Bar'

But when resolving through the CLI with json-refs resolve foo.yaml, I get a non-existent reference:
Foo:
  type: object
  properties:
    bar:
      type: object
      properties:
        foo:
          $ref: '#/Bar'

This might be expected behavior (I'm not well versed in the JSON Reference specification); however, one workaround that comes to mind would be to update the reference to where it's actually resolved:
Foo:
  type: object
  properties:
    bar:
      type: object
      properties:
        foo:
          $ref: '#/Foo/properties/bar'

Version of json-refs: 3.0.13

Just curious, is there an ETA on this?

I'll get it out today.  Sorry, priorities didn't let me get to it sooner.

I have this fixed locally, but I need to upgrade gulp so that TravisCI passes.  My plan is to update all dependencies, and gulp, commit and once the build is passing, I'll cut the release.
Good news is that while working on this, I found two other circular-reference resolution bugs and fixed them too.

I just went ahead and cut a release<EMAIL_ADDRESS>fixes this issue.

@dillonredding Do you mind verifying this implemented what you were requesting?

Not quite.   The idea is that when you have a circular reference, we leave it as-is and let whatever tooling is there to resolve it.  The bug you reported is that for locally-circular references in nested documents, doing that (keeping the local reference as-is) meant that the resolved value was left in a state where it's unresolvable in the resolved document.  That problem is fixed now, as locally-circular references in nested documents are fully-qualified when injected into the resolved document, allowing the resolved document to reference the documents where the circular chain was introduced.
That being said, I almost took a path similar to what you are wanting back in the day and was worried it was too much magic.  Manipulating $ref values wasn't something I wanted to do...I either wanted to replace/resolve them or leave them as-is.  But I guess now, this new approach, does in fact manipulate $ref values by making them full-qualified in the aforementioned case.  (Good news though, the reference metadata retains the original definition as expected.)
I would definitely say that in one way, maybe not exactly as you wanted, the original description of the issue is fixed.  But let me give this some thought, to see if something jumps out at me in the circular processing that is making this behave different than intended.

Yeah, what I'm asking for might be pretty specific. Specifically, I'm wanting to remove the references outside the file and have it be completely self-contained. I have no issues with manipulating $refs as long as the file remains "equivalent", but I might not be considering every scenario.

I get what you mean, and it might be easier than I thought.  I'm going to reopen this to avoid it falling through the cracks.


[vim] Don't set wfw, wfh, bh options when opening popup

This PR tries to fix the issue #2041.

Makes sense, thanks!


feat: add support for PGO

The new profiles attribute on native_image can be used to apply profile-guided optimization.

I tested this on turbine and got a nice further speedup.
@sgammon If you have time, could you create a release with this PR merged?

@fmeum Yep


What is the right way of calling node.js modules from inside iframe?

Question:
What is the right way of calling node.js modules from inside iframe?
The core of the problem:
In our big browser-oriented web-application we use "dhtmlx" javascript library, wich draws its own "windows" on the main page using iframe, thus imitating MDI interface. Every such a window is a separate html page, with its own purpose.
We are going to create an Electron-based application having more features than the browser-based one. We need to call node.js modules both from the main page (which is loaded in Electron) and from the pages that reside in several iframes located on the main page.
We can't use webview, because iframes are being created dynamically by a third-party library.
Simple call to "require" from the page loaded into iframe doesn't work.
Let's use a simple "default_app"-based example from Electron distribution to demonstrate the problem.
First we create a two-lines file "node-call.js" in "resources/default_app" folder:
os = require('os');
document.write(os.type());
Next we create another one-line file "iframe-content.html" in the same folder:
<html><script src='node-call.js'></script></html>
Then we add 2 lines into "default_app/index.html" file just before the closing </body> tag:
<script src='node-call.js'></script>
<iframe src='iframe-content.html'><iframe>
Let's start Electron. First output of document.write works, so we see our OS type on the main page. The second output from inside iframe doesn't work. We see an error in console:
Uncaught ReferenceError: require is not defined
So, node.js is not available by default inside iframe. Unfortunately, we didn't find a way to activate it in the manual. If there is such a way, please, tell us.
One can suppose it was designed this way in sake of security. However, if we alter "node-call.js" by adding a "top" to "require"
os = top.require('os');
both calls work fine. Hence, either the reason is not a security concern, or developers didn't take into account that one could call modules through "top".
Anyway it is bad because either the thing that should work does not, or works one that should not.
This means that the possibility of the call through a "top" could be blocked in next releases. Or we do something wrong.
Please help us!

The node integration in iframe is removed as a part of #1044, you can find the technical reasons there.


enhancement request: naming to conform to Glyphs.app?

This is motivated by the notodiff tool which is part of https://github.com/googlei18n/nototools.
Here's the sample output produced when I compared NotoSansSymbols2-Regular.ttf generated by the pipeline (A mentioned below) and the generated by the Glyphs.app (B mentioned below) from the same source in noto-source/src/NotoSansSymbols2-Regular.glyphs:
"....
in A but not B: ['nonmarkingreturn', 'null', 'space', 'uni1018B', 'uni1018C', 'uni1018D', 'uni1018E', 'uni10190', 'uni10191', 'uni10192', 'uni10193', 'uni10194', 'uni10195', 'uni10196', 'uni10197', 'uni10198', 'uni10199', 'uni1019A', 'uni1019B', 'uni101A0', 'uni101D0', 'uni101D1', 'uni101D2', 'uni101D3', 'uni101D4', 'uni101D5', 'uni101D6', 'uni101D7', 'uni101D8', 'uni101D9', 'uni101DA', 'uni101DB', 'uni101DC', 'uni101DD', 'uni101DE', 'uni101DF', 'uni101E0', 'uni
....
in B but not A: ['u1018B', 'u1018C', 'u1018D', 'u1018E', 'u10190', 'u10191', 'u10192', 'u10193', 'u10194', 'u10195', 'u10196', 'u10197', 'u10198', 'u10199', 'u1019A', 'u1019B', 'u101A0', 'u101D0', 'u101D1', 'u101D2', 'u101D3', 'u101D4', 'u101D5', 'u101D6', 'u101D7', 'u101D8', 'u101D9', 'u101DA', 'u101DB', 'u101DC', 'u101DD', 'u101DE', 'u101DF', 'u.....
"
You can notice that uni1018B in A corresponds to u1018B in B, uni1018D in A corresponds to u1018D in B, etc... However notodiff doesn't notice this...
I could add an option to notodiff (e.g., --try-matching-harder) that would retrieve the last 4 or 5 hex digits in the name and use this as a key to the name matching, but I  wanted to understand if we could make some changes in the font generation tools.

B has the correct naming:
https://github.com/adobe-type-tools/agl-specification
The shortened form "u"  is followed by a sequence of four to six hexadecimal digits, and is used for non-BMP characters, while "uni" is for 0000-FFFF.

ufo2ft does the right thing:
https://github.com/googlei18n/ufo2ft/blob/master/Lib/ufo2ft/otfPostProcessor.py#L57

Yea. uni1018B is a name found in the Glyphs source, but even so it shouldn't be used since ufo2ft uses production names by default. I'm not able to reproduce this.

Oh, is it possible Marek that you have the two fonts mixed up? I think that the Glyphs TTF output has incorrect "uni"-prefixed names. If that's true perhaps we should file a bug against Glyphs.

I'll check again. If that's the case I'll file a bug against glyphs.
On Wed, Sep 7, 2016 at 4:08 AM, James Godfrey-Kittle <
<EMAIL_ADDRESS>wrote:

Oh, is it possible Marek that you have the two fonts mixed up? I think
that the Glyphs TTF output has incorrect "uni"-prefixed names. If that's
true perhaps we should file a bug against Glyphs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/fontmake/issues/138#issuecomment-245248382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMtJfzOBrGDOxG-LBniLyF-oT0Zi7Odbks5qnpsmgaJpZM4Joyiv
.

--
Marek Z Jeziorek [ 老马 ] |<EMAIL_ADDRESS>|<PHONE_NUMBER>

cc @schriftgestalt

Glyphs does the design name to production name replacement based on the GlyphData file. The mentioned Unicodes are not in the list and thous are not replace.
But the recommendation for uni-names is to use the shorter version for upper plain codes as design name to begin with.

@marekjez86 can this be closed?


value of CMAKE_GENERATOR_TOOLSET:INTERNAL is getting prefixed with "host=" every time we try to configure a project

Brief Issue Summary
After Making change in GUI, editing the CMake configuration using "Edit CMake Cache (UI)" and saving the changes,
value of "CMAKE_GENERATOR_TOOLSET:INTERNAL" in cache file will end up with prefixing the "host=" to already existing value.
Ex:
CMAKE_GENERATOR_TOOLSET:INTERNAL=host=x86
if above value is already present, I make the change in CMakeCache using Edit CMake Cache(UI) option and saving it will result in below statement in CMake cache file
CMAKE_GENERATOR_TOOLSET:INTERNAL=host=host=x86.
This will result in the error while configuring the project like below:
[cmake] CMake Error: Error: generator toolset: host=x86
[cmake] Does not match the toolset used previously: host=host=x86
I had to manually edit the CMakeCache file again, to have the correct value and configure again.
Expected:
it should should prefix the value on every Save!

Thank you for reporting this.  I think we have enough information to investigate.  We'll let you know if we need anything else.

Thank you for reporting this.  I think we have enough information to investigate.  We'll let you know if we need anything else.

We almost have CMake Tools 1.6.0 release out the door. Until then, if you want, you can also verify if this problem has been fixed correctly by installing the vsix built here: https://github.com/microsoft/vscode-cmake-tools/actions/runs/557242002#artifacts.


Error: failed to initialize database: file missing

Summary of Bug
I'm running cosmovisor run start --x-crisis-skip-assert-invariants, but it fails with:

Error: failed to initialize database: file missing

+ /usr/bin/cosmovisor init /usr/bin/fxcored
+ /usr/bin/cosmovisor run start --x-crisis-skip-assert-invariants
4:24PM INF replace cosmovisor module=cosmovisor replace-flag=false
4:24PM INF running app args=["start","--x-crisis-skip-assert-invariants"] module=cosmovisor path=/home/fxcore/.fxcore/cosmovisor/genesis/bin/fxcored
04:24:54PM ERR failed to open DB error="failed to initialize database: file missing"
Error: failed to initialize database: file missing
Error: exit status 1
4:24PM ERR error="exit status 1" module=cosmovisor

The data files are there:
$ ls ~/.fxcore/data
application.db  blockstore.db  cs.wal  evidence.db  priv_validator_state.json  snapshots  state.db  tx_index.db

How do I know which file is missing?
Version
fxcore:~$ fxcored version
release/v4.2.x-v4.2.2
fxcore:~$ cosmovisor version
cosmovisor version: devel-214c176dd766220aee7873f5ed958eaed46b21e7
app version: release/v4.2.x-v4.2.2

I'm using Docker version.
Steps to Reproduce
cosmovisor init /usr/bin/fxcored
cosmovisor run start --x-crisis-skip-assert-invariants

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned
[ ] Is a spike necessary to map out how the issue should be approached?

Ok, I've re-downloaded db dump from fxcore-pruned-snapshot-mainnet-2023-11-24.tar.gz and it worked.


.gitlab publish fix

@samba  this was your catch from earlier today

Thanks @DStorck.
I'm going to retry some CI jobs here to ensure this has a passing status, but I'm hoping to merge it ASAP.
/cc @davidewatson

This is failing only the e2e phase of testing, based on the known UDP issue (#998).
I approve this change.


[StateCodelab] Not Found Class in Step 7 - Dynamic UI based on state

After I change compose version to beta02, some method is not found in Todo Components.kt file.

Thanks for reporting. The codelab currently uses beta02 and Github actions pass successfully.


Add log compare test for socket example

Add a log compare test for this example for enable example CI testing
@SeppoTakalo please review

Hi @jamesbeyond, is that required version of htrun already published, and as Mbed OS requirement have been installed, do I already have the correct version?
Or do I need to install it separately?


Can't make work ckeditor widgets plugins

Hello,
I'm having an issue with this package : I'm trying to create a ckeditor widget to add to the toolbars, I followed [this official tutorial] (https://docs.ckeditor.com/ckeditor4/latest/guide/widget_sdk_tutorial_1.html ) and it does not seem to work, even if I take the exact same code for the widget as in the tutorial. No new icon is getting added on the toolbar.
Here is the way I added the widget, in the "plugins" folder :

Here is my django config :

As you can see, I loaded the "widget" plugin as it is specified as a requirement, and then I loaded my custom plugin "simplebar", which is present in my first toolbar.
It's probably only a configuration issue that I forgot/did wrong, or It might be a bug, I really don't know, anyway, I would really appreciate getting some help to try resolve it ! Thanks guys !

I have the same issue. Some feedback or at least workaround would be nice.

I found the cause of the problem. It's caused by custom toolbar definition:
https://dev.ckeditor.com/ticket/12576
In order to use a widget in the custom toolbar, you need to enter title-cased plugin name, like so:
'toolbar': [[... 'Simplebox']],


new_benchmark

Submitting benchmark results of formula graph self-attention network for materials discovery (Finder) algorithm. Finder is a GNN architecture that can be used with or without crystal structures. 8 matbench regression tasks are considered in this submission.
Please note that there are two new benchmark directories matbench_v0.1_Finder_v1.2_composition and matbench_v0.1_Finder_v1.2_structure for composition-only and structure-based versions of Finder, respectively.

@ihalage I just pushed a fix (I think), let's see if it is able to pass tests now

Thanks @ihalage !!

Thanks for your help @ardunn. Really glad to see Finder listed on matbench leaderboard :)


Generated directive selector name should be camelcase

Version
$ ng --version
(node:20286) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.6
node: 6.2.1
os: linux x64

Repro steps
The following generate command produces a kebab case selector name instead of camelCase.
$ ng g directive shared/directives/wrap-if
(node:20210) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing directive
  create src/app/shared/directives/wrap-if.directive.spec.ts
  create src/app/shared/directives/wrap-if.directive.ts

src/app/shared/directives/wrap-if.directive.ts
import { Directive } from '@angular/core';

@Directive({
  selector: '[wrap-if]'
})
export class WrapIf {

  constructor() {}

}

As per the styleguide,

Do Use lower camel case for naming the selectors of our directives.

I've passed ng generate the name in kebab case because the README states so and follows the convention of passing the file name where file names should use dashes to separate words in the descriptive name.
I've read #424 and acknowledge that passing the name as camelCase to ng generate produces the correct selector but it is unintuitive and doesn't follow the README. I don't think we should make an exception to the convention of passing kebab case file names to ng generate.
Instead of not modifying the selector name at all for directives, I think they should be modified to be camelCase as per the styleguide.

As an addition according to the Style-Guide, the Selector for Directives should also take the prefix of the app into account. So I would assume
ng g directive lower-case

to create a Direktive with the selector
[appLowerCase]

@Brocco can you weigh in?

The style guide does dictate camelCase for directive selectors and prefixing them with the application prefix. I will put together a PR for this.
Reference: https://angular.io/docs/ts/latest/guide/style-guide.html#!#02-08

what if you prefix is kebab case? app-something, then you are doomed. why is component kebab case and directive camel case in style guide? can't we just use kebab case for everything consistently?


Exit status incorrect when output reporting error

moreover, I noticed the exit status of the command is 0 even if the reported error gets output and I think this should be fixed

Originally posted by @nicbus in https://github.com/RGB-WG/rgb/issues/173#issuecomment-2068833949

The exec of commands, pay function of WalletProvider return errors.
The current design is really good without bugs, this issue is also possibly out of the scope of this crate, in there we swallow an error and just print it out.

The exec of commands, pay function of WalletProvider return errors.
The current design is really good without bugs, this issue is also possibly out of the scope of this crate, in there we swallow an error and just print it out.

I'm having a hard time understanding what you mean, so I'll explain what I think is the issue in more detail.
In my opinion the issue here is that when a non-recoverable error is encountered, the command exits without completing the task it was supposed to, but exits with a zero status code, which means everything went well. This is a problem because a CLI user (or pipeline, or script) then assumes that the command worked and produced the expected results, while this is not the case and further operations down the line will fail because of this.
IMO it's important to report that the command did not produce the expected result by exiting with a non-zero status code, which can be handled by the user (e.g. by checking $?) or automatically (e.g. setting the shell's -e option).
As a more concrete example, in the original issue the command to create a wallet was the one failing with an error, which means the intended result of the command (creating a wallet) had not been achieved, which is why I think the exit status should have been non-zero. With a zero exit code, the user (or script) continues with the following commands (e.g. trying to generate an address) but they will fail because the wallet is not there.

The $? thing is shell operation, I know what you mean.  We do not have a shell (.sh) in the repo.
This happens when $rgb something and an error occurs with successful exit status. This is about the rust program and not about the shell.  Did I misunderstand something?
The main.rs returns an error code if the error is raised.
https://github.com/RGB-WG/rgb/blob/76a227730abb710cdd02f09207c2b36c64d938f6/cli/src/main.rs#L47C1-L47C26
If there is an error report with a successful exit status, it means the system swallows an error somewhere.

The main.rs returns an error code if the error is raised.
https://github.com/RGB-WG/rgb/blob/76a227730abb710cdd02f09207c2b36c64d938f6/cli/src/main.rs#L47C1-L47C26

If there is an error report with a successful exit status, it means the system swallows an error somewhere, because Result is a primary type and can be used for Rust function return, if some error happens and is swallowed it will not pass to the return.

You're right, the exit code was being masked by the fact that some rgb commands were executed inside a subshell or pipe. I didn't spot that difference initially, sorry for that, this can be closed.

This can open here if it is not confusing because this reflects the one issue we ran into before and we still have no mitigation.


docs(community): Add adevinta logo to Spinnaker users

Add Adevinta's logo to the Spinnaker users page.

Hi @gerardsegarra, thanks for adding this! I'll go ahead and merge this to get it added. Note that @stuposluns volunteered to do a followup change to put it in alphabetical order (in case you look for it later and can't find it).


Do not require workspace members to sync with --frozen

Summary
Closes https://github.com/astral-sh/uv/issues/6685.

There are some downsides to this. Like I guess we won't look at the requires-python of all members...?


WIP: Open api to worker bridge

Now we can upload the same open-api doc to both worker-bridge and external API gateways

Too early, let me make an example that work with shopping-cart


Auto forward upstream headers

Closes gh-1183

Possibly the configuration property needs to be a pattern, not literal values? And we should explicitly remove a couple of things, even if they match (“content-length” for instance).


new check: com.google.fonts/check/required_tables

Added to Universal profile.
Ported from https://github.com/fonttools/fontbakery/blob/624f6050b49b70b5f8da3d4e95568f7f74a87aae/Lib/fontbakery/checks/universal/tables.py#L5

This looks fine, but instead of a separate conditions, can we put methods on the TestFont object?

Thank you!


Suddenly stopped saving and reading files in hard drive and don't push to github

Type: Bug
VScode was working fine and suddenly stopped saving files in my external hardrive (I've been working in that drive for a couple of  months and has 2TB of space). It says "Failed to sane 'scripName.py': Unable to write file", I have tried with multiple files and says the same.
Then, I tried to push my changes to github (I do it almost everyday from VScode) and says "Git:fatal: Unable to create 'path to file/.git/index.lock': Read only" and shows me the following code:

git add -A -- path-to-file/file.py
fatal: Unable to create 'path-to-file/.git/index.lock': Read-only file system

I saved the files before the error, but it just stopped. I already updated VScode and the problem was fixed like for 2 minutes
VS Code version: Code 1.72.1 (129500ee4c8ab7263461ffe327268ba56b9f210d, 2022-10-10T17:23:00.760Z)
OS version: Linux x64 5.15.0-50-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 4490)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
7.55GB (3.92GB free)

Process Argv
--unity-launch --crash-reporter-id b7cf5b5d-060a-48ec-afdb-22b945ccc194

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (13)

Extension
Author (truncated)
Version

vscode-html-css
ecm
1.13.1

vscode-pull-request-github
Git
0.50.0

python
ms-
2022.16.0

vscode-pylance
ms-
2022.10.20

jupyter
ms-
2022.9.1202862440

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.10

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.255.3

powershell
ms-
2022.8.5

LiveServer
rit
5.7.9

JavaScriptSnippets
xab
1.8.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
2144e591:30553903
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30573243

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I did it, I followed these instructions https://code.visualstudio.com/docs/setup/linux

This is unlikely to be caused by VS Code. In a Linux command shell (not a VS Code terminal) can you create a file on that filesystem? For example:
touch /myBiDriveMountPoint/junkFile

Hi, you are right, it wasn't VScode, it was an unexpected damage in the external hard drive. Thanks!


Neomake should not create files in current repo.

here is what git status show:
On branch version-control
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   autoload/SpaceVim/default.vim

Untracked files:
  (use "git add <file>..." to include in what will be committed)

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>	autoload/SpaceVim/layers/VersionControl.vim

no changes added to commit (use "git add" and/or "git commit -a")

I think neomake should not create files like:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

There are some issues / discussion regarding this already.
Normally it should not really be a problem, but mostly only if you run Neomake and then Ctrlz Vim while it is running still etc - or in case it was not removed properly (which is a bug).
As a workaround you can add .*@neomake* to your global (git) ignore file.

Related issues: https://github.com/neomake/neomake/issues/1212 https://github.com/neomake/neomake/issues/1595 https://github.com/neomake/neomake/issues/1617

@blueyed This happens when I use :wq in neovim. ok, I will update gitignore of my projects.

It should not happen though: it should get cleaned up on VimLeave - but maybe this is related to #1617 then.
Does it happen always? Do you have steps to reproduce it?

no, I do not have reproduce step, but it only sometimes happens when I use :wq.

Can we get a config flag to tell neomake where to store tmpfiles? I already put files like this in ~/.vim/tmp/{backup,swap,undo} and would prefer to be able to configure neomake to use something like ~/.vim/tmp/neomake.

Yes, would make sense.
For reference, the code is this https://github.com/neomake/neomake/blob/ffa7ee5b534d86f6db5d51ff788f82a6ddc9161c/autoload/neomake.vim#L515-L552 (and could need some revisit in general I suppose).

ok, I will update gitignore of my projects

@wsdjeg you can also make a global gitignore file that you do not have to keep in the git repo but applies to all repos — see the core.excludesFile git config option.

I just had the same problem because vim crashed, apparently while neomake was doing something.
@blueyed From your snippet, but it looks like neomake uses tempname(). According to :h tempfile, if $TMPDIR is set, then it will be used preferably instead of /tmp or the current directory. Would it then be enough to just define this variable to avoid this problem in the future?

So I started looking into this and I made a small change that enables customizing the location the tempfiles are saved in.
This is the branch:
https://github.com/chancez/neomake/tree/custom_tempfile_dir
If you're using vim-plug you can test it out with:
Plug 'git@github.com:chancez/neomake.git', { 'branch': 'custom_tempfile_dir' }
let g:neomake_tempfile_base_directory = '/Users/chance/.vim/tmp/neomake/'

I'm not really sure how to add tests or where in the doc/neovim.txt this should go, but if this turns out to work for others, perhaps it could be upstreamed.

@blueyed I'm pretty new to vimscript and plugins overall, what would I need to do to get this added as a new option in neomake? I'm sure tests/docs, but I may need some help/guidance on where to put this in the docs/what the existing neomake-makers-tempfile_enabled section should be modified to look like. And tests...that is definitely something I'm less familiar with.

It should use neomake#utils#GetSetting, so that it can be configured per buffer/maker etc.
I'm looking into it later.

See https://github.com/neomake/neomake/pull/1788.
Feedback would be appreciated, of course.


Update for the new skins

how to update manually for the new skin

From what it says it has auto update but it is not

New little legends added ( a69d613ebb9215e9e7516879b5e69e0393a73e43 )
note: Auto update is for skins of little legends. Newly added little legends are not updated automatically.


#7055 changes taxonomy weight

This purposed changes add a new property with the full weight of a term(FullWeight) which is made using his weight and id and his parent's weight and id. This way we can lexicographically sort the terms via this property using simple sql and avoid algorithmic logic to sort them.
The terms update his FullWeight property whenever they are updated in the controller or the driver(including his children terms).Also they can be updated to use this new functionality importing all of them in the Import method using an 'old' recipe or migrating them in the Orchard.Upgrade module if they exist already.

And there is an update task, that's a great effort, thank you.
Can you paste some example values of FullWeight to understand simply how it works?

This is an example of what you get ordering by FullWeight in sql

I totally forgot how weights affect the terms order in the hierarchy, can you refresh my mind?

Weights are just used to order terms having same level(path) in the sort method. Using fullweight its the same if they have the same path they are ordered from higher weight to lower.

@jardg Can you sign the CLA ?
@jersiovic @urbanit would you mind testing the change? I assume it will make taxonomies faster.

@sebastienros I've been designing this feature with @jardg we work side by side on the same room at XKProject/Pccom. On next week it is expected we will test it on preproduction server.

@sebastienros I've been designing this feature with @jardg we work side by side on the same room at XKProject/Pccom. On next week it is expected we will test it on preproduction server.

@sebastienros I will try it during weekend hopefully...

Just waiting for @urbanit then we can merge

@jardg, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

Status update: I am testing it now in a multilanguage enviroment with 3 levels and some ci related...

Hi, test was completed.. As said, in a multilingual enviroment. Works nice, except from a bug that probably is not due to this PR but on localization [Quick Bug Description: cannot translate a 2nd level (child) term].
Reordering works smoothly.
Performance wise I cannot be precise, @jardg  & @jersiovic may tested the changes more thoroughly.

Improvements in family weight basically allow you to use pagination when you render families cause till now it was not a good option because to get the absolute order needed for pagination you need to load all the terms in the taxonomy so it had no sense cause that had por performance than not to paginate. Now with this feature you can paginate the rendering of a taxonomy tree using pagination with better performance cause you only load what you are going to render.
When you don't paginate a minor improvement that we have not meassured how much it improves is that you don't need to order the terms in memory after loading them cause actually they come ordered from db.

Seems logical. Thank you for clarifivation @jersiovic .


How can I throw the error from middleware or can response an error from here in the middleware file

I am using your library but I am not able to get a way where I can throw the error or throw json response error in it without letting it to reach to the controller.

@muriloacs

@see the code and really appear be a issue. I am in vacation right now without access a computer.
@murilocs If a middleware return a response, maybe we can render that, what you think about?


Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That is the worst kind of
vulnerability that exists. By merely existing on the classpath, this
library causes the Java serialization parser for the entire JVM process
to go from being a state machine to a turing machine. A turing machine
with an exec() function!
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103
https://commons.apache.org/proper/commons-collections/security-reports.html
http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

Hi, thank you very much for the pull request.
I now merged Commons Validator v1.5.0 into the master-branch in 45aa4abe8480a3f40eaa522bc9b9533bc60de3ca, which includes the change you requested: https://github.com/floscher/commons-validator/compare/4716a134e3265e5886acb9250a1c880d7d2bb3ce...45aa4abe8480a3f40eaa522bc9b9533bc60de3ca#diff-600376dffeb79835ede4a0b285078036L232


[Attention] Generalize Attention Tiling and Decomposition

Attention tiling and decomposition today are hardcoded. It assumes the rank and position of some dimensions. This makes it hard to do fusions with attention. This needs to be fixed by making the tiling and decomposition depend on the indexing maps for attention instead.

Closed by https://github.com/iree-org/iree/pull/17536


@l2success => Tooltips A/B test for admins

Waiting on a reaction bump for SSR issues

👌🏾 Looks good


JSON editor doesn't allow invalid intermediate states

Any time I try to change anything in the editor, it gets reset immediately if it results in invalid JSON (for example, adding a comma at the end to add a new element to an array). I guess this is kind of related to #353.
Actually, this is also true for other style inputs fields: try to clear our a mandatory(?) field via backspace (example: line width).  It always keeps the last digit, as an empty field would not be valid.

According to git bisect this was introduced with https://github.com/maputnik/editor/commit/1a8349f82158cda50d0791e537b8f438d769f171.

The bug is related to the switch from componentWillReceiveProps -> getDerivedStateFromProps (JSONEditor.jsx in https://github.com/maputnik/editor/commit/1aa90bef3738e1bdbc8189af91337d9d02085b46#diff-a85193e1bed4f1ffc51b04784dee3711).
Reverting to
UNSAFE_componentWillReceiveProps(nextProps) {
    this.setState({
      code: JSON.stringify(nextProps.layer, null, 2)
    })

allows invalid intermediate states again.

The same is happening in the numerical inputs (e.g. opacity) -- it's not possible to change the values (If I write "0.", it get's "reverted" to "0" before I get a chance to finish inputting the correct value.)

@petrsloup thanks, sounds similar but a bit different than https://github.com/maputnik/editor/issues/488.
Can't reproduce, do you see this with a public OpenMapTiles style? If yes, which style and which layer?

Yes, this happens with any style (I think it's the identical issue as this one -- the getDerivedStateFromProps is the issue somehow.)

Submitted a potential fix in https://github.com/maputnik/editor/pull/501 .
@petrsloup @sk1p @zstadler maybe you would like to try it out, your feedback would be much appreciated:
https://1281-67726921-gh.circle-artifacts.com/0/artifacts/build/index.html
Please note: This is only for fixing the JSON editor.

Thanks @pathmapper for the potential fix!
When I try to enter -0.4 as a numeric value, after typing -0, the cursor jumps to the end of the JSON code and the .4 suffix appears after the closing bracket of the code:

Perhaps this is a result of trying to enter semantically-incorrect data in the stops array. However, it is strange for the cursor to jump as a result of such an error.

@pathmapper Thanks! Seems to work from a short check. @zstadler I can confirm the issue with -0. Strangely, -1.something works fine. In my tests, even typing -0 outside of the context of stops triggers this behavior, for example as the value for any other key.

@zstadler @sk1p thanks for your feedback! The bug cursor jumps to the end of the JSON code  exists since v1.1.0, opened https://github.com/maputnik/editor/issues/502 to track it.
The numerical input bug is tracked in https://github.com/maputnik/editor/issues/488.


Add ability to select calendars

I've currently hard coded to fetch from my default Google calendar and my Outlook calendar named Valsoft. Switch it so that you can create multiple calendar providers with specific named calendars.
foreach calendarService
    fetch calendars
        print "Do you want to display events from calendar?"

Use this to create the DI container constructing each service with the calendar ID.

This was completed with my Calendar rework


Relative path to the build directory is treated like absolute

When using the command line:
python manage.py build report.views.RenderView  --build-dir ./build
bakery tries to create the top level directory /build and fails because of permissions.
fs.errors.PermissionDenied: permission denied mkdir: ./build: No such file or directory
It should instead create it in the current directory because there is a dot in front.
Is this by design?
It is not something that one cannot get around, but when using singularity and some workflow systems (nextflow), using absolute paths may become messy, as you're working with isolated directories.

Interesting. The code that makes it happen is right here:
    def init_build_dir(self):
        """
        Clear out the build directory and create a new one.
        """
        # Destroy the build directory, if it exists
        logger.debug("Initializing %s" % self.build_dir)
        if self.verbosity > 1:
            self.stdout.write("Initializing build directory")
        if self.fs.exists(self.build_dir):
            self.fs.removetree(self.build_dir)
        # Then recreate it from scratch
        self.fs.makedirs(self.build_dir)

Anything look off?

Okay. I'm open to a change along these lines, but I'd like to add some testing to verify its working now and in the future. What different path inputs could you imagine we should test for?

I would think these:
/directory
/directory/directory

~/
~/directory

./
./directory

../
../directory
../../directory

a symlink directory

Can't see anything else.

@ClaudiuCreanga, would you be interested in developing a patch to solve this problem?


Miniaudio streams

WIP as usual, just showing my work

[x] Lua API for append
[x] Find and fix all the bugs
[x] Remove asserts from lovrSoundDataReadRing because it's not on the main thread
[x] SoundData:getDuration() so we can know how much is buffered

Note: I had to add a struct tag in miniaudio.h or otherwise I'd have to pollute the soundData.h header with miniaudio.h :S just FYI...

@bjornbytes I think this is done. I'll branch off of this work on setting sound devices...

I bumped to a version of miniaudio that fixes a Quest issue, so now it should work on all platforms afaik


fix TestCriticalCrdsAreReady race test

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @hklai

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b53157116fc3ec66cd9f35bb6eb04ada9b3395a3
link
/test istio-pilot-multicluster-e2e

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

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
430b86340f43dbc6ab77f92871793f86ed832a12
link
/test istio-pilot-multicluster-e2e

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


[Bug Report] Title Here

Describe the bug
The bot stopped working today
when the playlist starts, the answer is silence
To Reproduce
Steps to reproduce the behavior:
1.I go to the text channel
2.I enter the command
3.bot does not play
Screenshots
https://skr.sh/s5NdzGsFnLh?a
Debug Info
debug_information (1).txt
Additional context
when restarting, incomprehensible errors with the token, but then successfully logs in
log.log

You are using version 0.2.7, which is severely outdated. Please use the latest release.


Not working?

Is this still working? I tried to use it today but it keeps saying the component failed.

Hello,
I am still working on this, because I need it for my home automation.
Did you try it with the newest version. I had some problems with the persistance
saving of the login token. This should be fixed now.


Priority propagation

My department requires all scripts to be ran with nice -19, however DaskSSH will not propagate this priority to the worker machines from what I know. It would be very nice if this could be a feature, if it is not already implemented.

Sure.  I'm a little surprised that Python doesn't propagate this.  Do you
have suggestions on how we might do this?  We're just using the
multiprocessing.Process API
On Thu, Aug 29, 2019 at 1:01 PM landonzweigle<EMAIL_ADDRESS>wrote:

My department requires all scripts to be ran with nice -19, however Dask
will not propagate this priority to the worker machines from what I know.
It would be very nice if this could be a feature, if it is not already
implemented.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5349?email_source=notifications&email_token=AACKZTED5FQQQ74GYKBMIJLQHATKPA5CNFSM4ISGJQU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HIJKI2Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACKZTHPVMPRHWR7W2O2SX3QHATKPANCNFSM4ISGJQUQ
.

@landonzweigle SSHCluster was recently refactored. Can you check if the new implementation solves this issue for you?

Hi! Sorry, I totally forgot about this issue (I circumvented the issue).
I have updated to 2.6.0. When running:
nice -19 dask-ssh --scheduler butternut --hostfile /s/fir/e/nobackup/Fresh-Phish/Code/hf.txt --ssh-username lzweigle --ssh-private-key ~/.ssh/id_rsa --nthreads=1 --nprocs=3 --memory-limit 5GB

the workers still seem have the default priority. This refactor doesn't seem to have solved my problem. Any ideas?

For general awareness, the new SSHCluster isn't connected to the dask-ssh
CLI.  There wasn't a trivial way to keep the old CLI keywords, so I've left
this for now.  The old implementation is still around for this.
(Landon, this doesn't concern you, I mostly wanted Tom to be aware)
On Fri, Oct 25, 2019 at 4:00 PM landonzweigle<EMAIL_ADDRESS>wrote:

Hi! Sorry, I totally forgot about this issue (I circumvented the issue).
I have updated to 2.6.0. When running:
nice -19 dask-ssh --scheduler butternut --hostfile /s/fir/e/nobackup/Fresh-Phish/Code/hf.txt --ssh-username lzweigle --ssh-private-key ~/.ssh/id_rsa --nthreads=1 --nprocs=3 --memory-limit 5GB
the workers still seem have the default priority. This refactor doesn't
seem to have solved my problem. Any ideas?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/5349?email_source=notifications&email_token=AACKZTAWSXLZJAXTEPXRCJLQQN275A5CNFSM4ISGJQU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECJYL6A#issuecomment-546539000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTAVIMIRTAI2MBTIVP3QQN275ANCNFSM4ISGJQUQ
.

My comment from before probably still holds.

Sure.  I'm a little surprised that Python doesn't propagate this.  Do you
have suggestions on how we might do this?  We're just using the
multiprocessing.Process API

It would be good if someone investigated the behavior of nice and the Python multiprocessing module.  It doesn't look like this is anyone's priority, so I expect that this issue will probably linger for a while.  @landonzweigle , if you have time to investigate this, that might be your fastest path to success.


UI Enhancements

FW Logs
Terminal
Calibration UI

Superseded by https://github.com/IntelRealSense/librealsense/pull/6679


Overwrite image of the same file name with different file size

This situation sometimes occurs.
Several files from D5600 are already in the local folder.
eg) DSC_8797.JPG   DSC_8798.JPG   DSC_8799.JPG   DSC_8800.JPG
When a picture taken on another D3200 is transferred, the existing file is automatically overwritten.
Although the file name is the same, the picture content and file size are completely different...
As a result, the first 4 photos of D5600 are disappearing forever.
Description on YouTube : http://youtu.be/ldOYSxq-Y-0
If the name of the file in the local folder is the same but the file size is different, it is reasonable to rename and transfer as follows.
eg) DSC_8797-1.JPG   DSC_8798-1.JPG   DSC_8799-1.JPG   DSC_8800-1.JPG
Is it technically possible?
For reference, in the same situation the previous eye-fi sd renames the files and transferred.

This behavior is intentional.
It is for overwriting a file corrupted during the previous copy. To be honest, I have not expected that anyone may risk their files by using the same local folder when a file name can be duplicated.
I recommend not to specify the same local folder in such case in the first place. But it can happen accidentally. So I add setting not to overwrite existing files.
https://github.com/emoacht/SnowyImageCopy/commit/25093ecc61606e9514b71a7794beb5d575c7396f https://github.com/emoacht/SnowyImageCopy/commit/e90ea92831b8a1aa44b39c4a69cb457f5460b35a
Please note the number of same file name files are limited to 65535.


Remove EndpointStateNotifier.getErrors()

We can use the getEndpointState Flux to propagate any errors on the link and simplify the experience.

Once an error is transmitted, the flux immediately ends. we don't want this behaviour.


Feat/ga/91 content tree redesign

Issue
https://github.com/SAP/guided-answers-extension/issues/91
Description

Checklist for Pull Requests

[ ] Supplied as many details as possible on this change
[ ] Included the link to the associated issue in the Issue section above
[ ] The code conforms to the general development guidelines.
[ ] The code has unit tests where applicable and is easily unit-testable
[ ] This branch is appropriately named for the associated issue

@unseen1980, no clue why SonarCloud shows
0.0% Coverage

I see you added tests for GuidedAnswerNavPath and if I run test report local, it is shown:

Somehow this is not picked up by SonarQube, @kranthie-sap, any idea?

Thanks!


Scheduler opens in new Tab

First Noticed in #21.
When the date is selected, a new tab opens with the scheduler open. This may be a target _blank issue with the scheduler.

The issue may be browser or iFrame based. The Acuity Support Team has been notified on the issue.

Issue was caused by a bug with the Acuity Scheduling Tool. They have fixed the problem on their end (super quickly too)! 😄


Respect BSD-3-License please

As it was recognised during the CNCF Sanbox review (https://github.com/cncf/sandbox/issues/15) some parts of this code are slightly modified variant of CPU-Pooler. The original CPU-Pooler code was releases under the BSD-3-Clause license. Please follow the license obligations requested by the license. I copy them here for your convenience:

Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

Thanks

@CsatariGergely  Complete respect BSD-3-License. The following modifications：

Redistributions of source code with third_party/forked/nokia/CPU-Pooler directory;
Add Copyright.md base on third_party.


Feature: File or Pipe input for 'Azcopy Remove'

azcopy version 10.2.1
It would be extremely useful if 'azcopy remove' could recieve input from pipe or iterate over a list of blobs.
The best work around at the moment is to use xargs in parrallel like:
xargs -P4 -l1 -n1 -I@ -a $HOME/db_blob_no_match.list azcopy remove --recursive=false "https://${ACCOUNT}.blob.core.windows.net/${CONTAINER}/@${SAS}"
But even in parrallel this is very slow as there is time wasted waiting for the OK response from Azure API.
You can get creative using the --include="" but this has an upper limit on total amount of words it will allow within the --include clause.

Hi @nofunatall, thanks for reaching out!
We'll have support for this feature in the next release. You'll be able to use --list-of-files.

Any ETA on the next release?

@nofunatall we are targeting the next few weeks.

We don't publish the dates, I'm sorry.

Ok so no dates - last comment was a few weeks which was almost 3 weeks ago.

I'll raise your question at today's team meeting.

Hi @nofunatall. I raised your question at today's team meeting. Email me if you'd like to discuss.

Thanks but not needed - I will just keep note maybe expect release sometime next month.

The release is out now.  Version number is 10.3.  The file format is just literally a list of relative filenames, as described here: https://github.com/Azure/azure-storage-azcopy/wiki/Listing-specific-files-to-transfer


Can the default of google authenticator produce totp changed into 10 minutes?

Hello, I wanna ask something. Is it possible to change the default of totp generated from the authenticator app to become a 10m Period totp code? Because in my code, all OTP that are generated is for 10m period (Message, Email, etc)  thats why, I need all verify code to be a 10m period totp code, where 30m totp code cannot be used to verify 10m totp code, so all code that is generated from GA is failed, but if I change all verify back to 30m GA can be used again. Anyone has a suggestion? Thankyou

But why?

yes you can, change the 30 seconds parameter in the function call to any number you want and on verify the number generate a number based on the new logic you changed


Tech Debt: Simplify ProxiedReference

Need to investigate the uses of ProxiedReference as it might be possible to simplify some of this and not have public methods that aren't really meant for public use.  The suppression of checkstyle and use of non-standard method names suggests there may be a cleaner way of doing this.
This will probably be a breaking change, as these methods are public although they are only meant for internal use

proxied references are going away


Issue #36 handle errors on the front end

This logic uses https://sweetalert.js.org/docs/

Some screenshots of the new feature:


Todo status

Value proposition
**As auser,
**I want to click the status button to change the color
**so that have a better overview
Description

Acceptance criteria

[ ] now Todos are unchecked
[ ] Tap the red "Aufgabe" button and the color will change to yellow and the text will change to "In Arbeit. When you're done, you can tap the yellow button and its color change to green and the text to "Erledigt".
[ ]  Checking/unchecking does not change sort order

Complexity
Small
Tasks

[ ] Create branch
[ ] Setup stories for Todoitem
[ ] implement status button
[ ]  Write specs for TodoItem
[ ] Implement Todoitem
[ ] Update state logic in App with Todoitem

Hi @Mitrovic-Milan ✌
well done, so far.  I have some comments.
Value proposition
What's the users benefit of this feature - be more specific.
For example:
As a user:  typo, missing whitespace
I want to change the status of my todos
So that I  get a better overview which todos still needs to be done
Acceptance criteria

now Todos are unchecked typo: new todos - Tap the red "Aufgabe" button and the color will change to yellow and the text will change to "In Arbeit. When you're done, you can tap the yellow button and its color change to green and the text to "Erledigt" : From a user and UX/UI perspective, it is unfavorable. To change the status from "In Arbeit" back to "Aufgaben", you will first marking the todo as "Erledigt". In further User Stories you can think about an other solution

Checking/unchecking does not change sort order: what means Checking/unchecking?
Notice: It would be a cool feature to sort your todos by priority or status, wouldn't it?  ☝

Your formatting is not correct in the "Value proposition".  In markdown you can add bold text with **I am bold**

If you have any question, feel free to as me 🙂


[Feature] COSH Formula Implementation

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
COSH Formula not implemented
Solution
@abdelrahmanzaitoun830a: I can solve it.
Ref: https://support.google.com/docs/answer/3093477

duplicate of https://github.com/dream-num/univer/issues/2425


Update

Complete overhaul

@WebFreak001 So, this now uses serve-d directly to spawn the language server. However, when I use this on project, I get all sorts of errors. Does serve-d require a specific procedure for spawning?
https://github.com/aminya/atomize-d/blob/update/src/atomize-d.ts#L24
To install:
pnpm i
pnpm get.served
apm link .

Open any D project
atom ./d-project

@WebFreak001 So, this now uses serve-d directly to spawn the language server. However, when I use this on project, I get all sorts of errors. Does serve-d require a specific procedure for spawning?
https://github.com/aminya/atomize-d/blob/update/src/atomize-d.ts#L24
To install:
pnpm i
pnpm get.served
apm link .

Open any D project
atom ./d-project

wow thanks for the PR and the interest in maintaining atomize-d!

@WebFreak001 So, this now uses serve-d directly to spawn the language server. However, when I use this on project, I get all sorts of errors. Does serve-d require a specific procedure for spawning?

Hm it should just be standard LSP protocol, are you using the latest nightly or beta serve-d build to test? Otherwise send me a complete LSP log and I will check what's wrong.

wow thanks for the PR and the interest in maintaining atomize-d!

@WebFreak001 So, this now uses serve-d directly to spawn the language server. However, when I use this on project, I get all sorts of errors. Does serve-d require a specific procedure for spawning?

Hm it should just be standard LSP protocol, are you using the latest nightly or beta serve-d build to test? Otherwise send me a complete LSP log and I will check what's wrong.

are you using the latest nightly or beta serve-d build to test?

The latest github pre-release.

,Otherwise send me a complete LSP log and I will check what's wrong.

Not sure, which one gives more information

are you using the latest nightly or beta serve-d build to test?

The latest github pre-release.

,Otherwise send me a complete LSP log and I will check what's wrong.

Not sure, which one gives more information

If you wanted to try this yourself, don't forget to enable this config in the settings:

If you wanted to try this yourself, don't forget to enable this config in the settings:

Here is the error expanded:

Here is the error expanded:

Ok. That error is gone! I was using the wrong spawn function. The example in the documentation misled me. serve-d is a real executable that should be spawned directly not with Node.

 The datatips don't work:

DCD fails to download on Windows:

@WebFreak001 Where does this error come from?
D (serve-d) stderr 2021-02-02T21:03:27.057 [error] source\served\extension.d:1090:__lambda1 Failed to attach DCD component to C:\Users\aminy\Documents\GitHub\D\atomize-d\spec\fixtures: Failed to spawn new process (The system cannot find the file specified.)
warn @ C:\Users\aminy\Documents\GitHub\JavaScript\@atom-ide-community\ide-python\node_modules\atom-languageclient\build\lib\logger.js:10

that is a handled error inside an error:
It tried to call load on the DCD component in workspace-d, but it threw an exception with the message "Failed to spawn new process (The system cannot find the file specified.)"
This very likely means it failed to launch dcd-server.exe (as dcd-client has been integrated into workspace-d a while ago)

So, what is the solution? I am not using workspace-d. I am just using serve-d directly.

I think I fixed the error by coping serve-d exe into code/bin folder

Now, the errors are different when I hover for getting datatip:

workspace-d is used by serve-d, which is why you are seeing the error. Putting the DCD exe next to serve-d will always work because that's the first path serve-d/workspace-d search for the exe, otherwise the configurations (d.dcdServerPath) need to be properly sent with the exe file (not folder or something)
In your last error it somehow crashes fatally (segfault or something), I need to investigate that, but can only do so on linux. If you want you could try compiling serve-d from source in debug mode (just dub build --compiler=ldc2) and try to attach to the process when you launch atom (launch serve-d with --wait for it to wait 2s at startup)

Some of the errors are gone. I had to copy the dll files! 🤦♂
However, datatips return an empty array:

can you share how atom does the initialization procedure? (initialize, initialized & if it sends any configurations afterwards)
functionality might be there, just not actually resolving to anything.

This is the log. It seems that it is calling the correct code

Yay. The datatips are fixed!

@WebFreak001 Could you please give me write access to this repository? I want to merge and register it. I would like to change the package name to ide-d which is a convention for the ide packages in Atom


Native Image Not Rebuilt If Previous Run Resulted in an Error

General Summary
Our build system is building a few artifacts using the Native Image tool.
The builds are cached to not rebuild the whole image every time the artifact is needed for other steps (as the build takes a long time). However this caching is sometimes broken. Whenever the native image build fails, the current task fails, but the cache somehow thinks that it has succeeded and so whenever the artifact is needed again in a subsequent task, the cache thinks that it is up-to-date; if an existing executable is available, it is then used, even though it is not actually up-to-date. To get an up-to-date build after a failure the executable must be manually removed.
This can lead to issues with testing, where the developer thinks that the executable has been rebuilt, but it is actually an older version.
Steps to Reproduce

Open the sbt console.
Run buildLauncherDistribution; ensure that you have very little free RAM left so that the process will fail with out of memory error.
See that the command has failed.
Run buildLauncherDistribution again.

Expected Result
The next run should again try to rebuild the Native Image, to make it up-to-date.
Actual Result
[info] No source changes, enso Native Image is up to date.

Enso Version
Current main.

A very simple solution could be to just remove the previous executable once the new build is started. Thus, even if it fails, the old executable will no longer be available and thus will force a rebuild the next time.
The only downside is that we remove a working executable that could have been used for testing if the build failed, but such usecase seems rather very rare.


clean up cvTriangulatePoints by using C++ primitives directly.

also fixes the Calib3d_StereoCalibrate_C testcase.

thanks! :+1:


Revamped BUTTON_IDEAS.MD

Fixes #375
Fixed style table structure.
The last row in the style table was not alligned and was appearing outside the table.

Thank you for your contribution but please next time comment on the issue to be assigned to it before working on it.
@all-contributors please add @nitish-awasthi for content


Add QuickDash as QuickSFV alternative.

changelog: Added my program QuickDash as alternative to QuickSFV.
Edited README.md and nothing else

Added crates.io link


respond_to doesn't match with regex

@respond_to(r'FAILURE\: Job \'company/(\w+)/master', re.IGNORECASE)
if message is => FAILURE: Job 'company/ui/master [166]' which should match to regex, but bot sends DEFAULT_REPLY back and doesn't call handler

Hi @ozonni,
Part of the issue may be that you're testing via DM. There is some improvement that could be made to the matcher code there, but the short of it is, it's trying to read a nickname before the colon. If your bot user is named testbot, try sending:
testbot: FAILURE: Job 'company/ui/master [166]' or @testbot FAILURE: Job 'company/ui/master [166]'
If it's in a channel, you'd have to send the bot name for a respond_to to match. Note that a listen_to does work correctly. So, there is a bug here around the matching logic used in DMs. I'll update the bug title and description to reflect that.


QGB E2E scripts retry starting nodes

When starting E2E network, the scripts used to boot up the orchestrator, relayer and nodes can fail for various reasons. These failures are sometimes due to an orchestrator/relayer starting before the corresponding node starts.
Thus, we need to include a retry mechanism in the bash scripts that retries a number of times in case of failures.
This would make the tests less flaky.

per sync discussion, this issue is outdated due to the move to QGB 2.0


PR: convert leoAtFile.py to leoAtFile.ts

Leo issue #2275 what Leo's python-to-typescript command does, and what it doesn't (can't) do.
Status of leoAtFile.ts

leoAtFile.ts is exactly the output of Leo's python-to-typescript command.
vs-code colorizes all lines correctly.
tsc issues hundreds of errors about translated f-strings. For example:

src/core/leoAtFile.ts:4267:45 - error TS1434: Unexpected keyword or identifier.
4267             g.trace(`Invalid external file: ${sfn}`);

I have no idea why tsc issues these error messages!
Summary
Imo, leoAtFile.ts is a good starting point for the final version of leoAtFile.ts, to be completed by you, Félix.
Work on Leo's python-to-typescript command is complete, for now.  I'll be happy to fix bugs in this command. If you like, we can zoom to discuss any possible improvements in python-to-typescript.

Let's close this PR. It's way out of date.


[Bug]:  NO SUPPORT MODULE LOADED

All of the following criteria must be met

[X] All Requirements must be installed.
[ ] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[X] Was able to see the Start Screen.

Describe the issue.
ERROR NO SUPPORT MODULE LOADED

Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Maybe attach the file itself instead of a screenshot

Marking this as invalid.
You have provided only a screenshot and not the actual log file as requested.


Cannot see device in Home App

Checklist

[x] I have read the common issues wiki page
[x] I have checked to make sure the plugin is up to date

Describe the bug
First of all, thank you for your work on this plugin.
I have a smart IR transmitter that controls my Air Conditioner and TV via Infrared. I've gone through the steps in the readme and wiki, and have configured the plugin to expose my Air Conditioner to HomeKit.
My configuration looks like this:
{
            "options": {
                "username": "XXX",
                "password": "XXX",
                "accessId": "XXX",
                "accessKey": "XXX",
                "lang": "en",
                "projectType": "2",
                "appSchema": "tuyaSmart",
                "countryCode": 123,
                "debug": true
            },
            "name": "TuyaPlatform",
            "platform": "TuyaPlatform",
            "devices": [
                {
                    "name": "Living Room Cooler",
                    "type": "AirConditioner",
                    "manufacturer": "Daikin",
                    "model": "XXX",
                    "id": "XXX",
                    "key": "XXX",
                    "noHeat": true,
                    "minTemperature": 19,
                    "maxTemperature": 31,
                    "minTemperatureSteps": 1
                }
            ]
        }

I can even see in the logs that the plugin discovers my devices:
Adding: Smart IR (wnykq / XXXX)
Adding: Air Conditioning (infrared_ac / XXXX)
Adding: TV (infrared_tv / XXXX)

My issue is, I can't see any of these devices in my actual Home app, or theAccessories tab in homebridge config UI.
Expected behavior
The accessories added in the config should show up in the Home app.
Environment (please complete the following information):

OS: Raspbian GNU/Linux 10 (buster)
iOS version: 14.7
Homehubs: ?
Node Version: v14.17.2
Plugin Version: 1.3.0
Accessory Type: Air Conditioner (via Smart IR)

Hey, this isn't my plugin. My plugin just called Tuya, not TuyaPlatfrom

Incorrect Issue, closed.


fix: tekton-chains job fails to start

Configuring the job to run as non-root caused it to fail to start. Setting a specific user should address this.
closes: #240

lgtm

@ShakedAviv50313 please take a look at the issue and how we addressed it.


cxd56 audio with buffering

Summary

This PR consists for 3 commits for spresense audio.
The first commit handles the final audio buffer to send stop message. In previous implementation, the final audio buffer was not handled. Thus, audio driver always stopped after detected DMA underrun. With this commit, audio driver stops correctly at the end of audio file.
The second commit add audio buffering feature to audio/cxd56. In this implementation, CXD56_DEV_STATE_BUFFERING is newly added to distinguish from pause state for buffering. And if pending queue is empty in cxd56_start_dma(), it sends AUDIO_MSG_USER to the worker thread to start buffering. In the worker thread, it sets CXD56_DEV_STATE_BUFFERING when received AUDIO_MSG_USER. Then if AUDIO_MSG_ENQUEUE received, it checks conditions such as pendingq exceeds the threshold or pendingq contains the final buffer and if it matches the condition then start dma again by calling cxd56_resume().
The third commit adjusts audio buffer (4KB x 32 -> 2KB x 32) and prealloc mq size (4 -> 32) for audio streaming with wifi.

Impact

This PR affects spresense audio driver and wifi configuration.

Testing

I tested this PR with nxplayer for both local file playback and http audio streaming.

Hi @jerpelea , @tobias2johansson,
I'm sorry to forgot to leave comments for review before merging.
I thought I had left comments...
Anyway, as you can see, I added a buffering feature to cxd56 audio and
if you have any concerns, please let me know.

The PR message looks good and should be replicated in the commit messages
@masayuki2009 please add commit messages


Add SPANISH translation to plugins-list.json

Hi @robiso,
I made the SPANISH translation for WonderCMS : https://github.com/perdigano/translation-spanish
Could you merge this, please?
Regards.

Hi @perdigano, I've manually forked your translation and added it to the official repository.
This should be now available to all users (that check for updates in their settings panel).
Would you be so kind to send me over your first/last name + website (Twitter or Personal) so we can add it do our list of contributors? https://www.wondercms.com/special-contributors

Hi again @robiso !
Great to know spanish translation is now official !
If you want you can add my real name (Victor Rodriguez Aragones) to WCMS contributors list.
My personal website (running WCMS of course ) is www.perdigano.com
Thanks for such a great (and tiny) CMS and best regards from southern Spain!

@perdigano thank you again for your effort. :)
Is there anything specifically you like or dislike/is missing from WonderCMS?
You've been added to our official list of contributors: https://www.wondercms.com/special-contributors
Cheers!


circular dependency found

$ npm run bundle

><EMAIL_ADDRESS>bundle /Users/weiran/repo/github/cherow
> cross-env rimraf dist && node scripts/bundle.js

creating normal bundle
Circular dependency: src/lexer/common.ts -> src/lexer/identifier.ts -> src/lexer/common.ts
Circular dependency: src/parser/expressions.ts -> src/parser/pattern.ts -> src/parser/expressions.ts
Circular dependency: src/parser/statements.ts -> src/parser/expressions.ts -> src/parser/statements.ts
Circular dependency: src/parser/expressions.ts -> src/parser/directives.ts -> src/parser/expressions.ts
Circular dependency: src/parser/expressions.ts -> src/parser/jsx.ts -> src/parser/expressions.ts

it works fine -- just a warning.

@aladdin-add As far as I understand your example is not taken from the Master branch. directives.ts and jsx.ts doesn't exist in the parser folder on the Master branch as seen here, But you are right - the circular dependency exist.

Thanks for this issue. This repository and project will no longer be maintained, please consider its successor: https://github.com/meriyah/meriyah
Thanks for understanding and we apologize for any inconvenience!


Make 0.3.0 release

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge-admin, please restart ci

I think we probably also need to delete this, which I added for the dev build:
https://github.com/conda-forge/sunode-feedstock/pull/15/commits/4fa2597184d2e16f75359ac7c18bec55c795e65e#diff-ff61408cdc05bc9667deeadb55e4aaceb1371972076b6bf6934f9008920f2bd2
and after that also another rerender?

I think we probably also need to delete this, which I added for the dev build: 4fa2597#diff-ff61408cdc05bc9667deeadb55e4aaceb1371972076b6bf6934f9008920f2bd2
and after that also another rerender?

I did that in https://github.com/conda-forge/sunode-feedstock/pull/15/commits/283a8af6e8dc2e490285277292a1e7e047b580bb, already followed by a re-render.
If the tests pass this time, I will squash the last four commits and then we should be good to go

In the overall PR diff there's no -alpha and the SHA256 is the one for the .tar.gz of the 0.3.0 release
Is that not correct?

I think we were talking about two different things. I meant the file conda_build_config.yml.
"No -alpha" in the path name and "the sha256 of the released tar.gz" should both be correct.

Oh, yeah I totally overlooked that. It's gone now.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Looks good to me