feat: add unstable Vite support

This PR is based on the initial Vite prototype in pcattori/revive built by @pcattori and myself.
TODO:

[x] Finish initial docs

[x] Move to new Future section
[x] Hosting/runtime/feature compatibility matrix
[x] Call out HMR differences
[x] Thank everyone who provided prior art and/or inspired our work

[x] Finalise API

[x] Rename "experimental" to "unstable"
[x] Move plugin from @remix-run/dev/vite to @remix-run/dev
[x] Remove Remark plugin (for now at least)

[x] Dedupe config resolution logic being used inside Vite plugin
[x] Warn about unstable usage in terminal

hono has a vite-dev-server that is compatible with cloudflare workers. I don't know all the details, but here are some links that might give an idea about cloudflare workers compatibility

https://www.npmjs.com/package/@hono/vite-dev-server
https://github.com/honojs/vite-plugins/tree/main/packages/dev-server
https://github.com/honojs/vite-plugins/blob/f5d4c78cfc94b4e46f9dd191f1cd07da832cdee5/packages/dev-server/src/dev-server.ts#L46-L53
https://github.com/yusukebe/vite-dev-server-examples/blob/main/src/index.ts

maybe related:

https://github.com/cloudflare/miniflare/pull/639
https://github.com/leader22/cfw-bindings-wrangler-bridge
https://github.com/james-elicx/cf-bindings-proxy

@pcattori where should issues be reported?

Yea separate issue with "Vite Nightly" or something like that is the way to go


coveralls has some wonky dependencies, we can use an older version maybe

we should probably add a Gemfile.lock file here, or add a version to the coveralls gem
adding the following dependencies allowed me to install bundle in 1.9.3

Coverage remained the same at 96.943% when pulling 25fcf1e50411ea0a7d502d744249525513f81214 on shmargum:fixes into 5fdf7f43383869976d3e16d9c0ed4695ba35cff3 on damian:master.

Coverage remained the same at 96.943% when pulling 25fcf1e50411ea0a7d502d744249525513f81214 on shmargum:fixes into 5fdf7f43383869976d3e16d9c0ed4695ba35cff3 on damian:master.

Coverage remained the same at 96.943% when pulling 3a7e5766cd836b1f6e1fcfdb007a531a1bc51d65 on shmargum:fixes into 5fdf7f43383869976d3e16d9c0ed4695ba35cff3 on damian:master.

Coverage remained the same at 96.943% when pulling 3a7e5766cd836b1f6e1fcfdb007a531a1bc51d65 on shmargum:fixes into 5fdf7f43383869976d3e16d9c0ed4695ba35cff3 on damian:master.

Coverage remained the same at 96.943% when pulling 3a7e5766cd836b1f6e1fcfdb007a531a1bc51d65 on shmargum:fixes into 5fdf7f43383869976d3e16d9c0ed4695ba35cff3 on damian:master.

after a little bit of googling and clicking, the suggestion at the bottom of this link for googlers worked:
https://github.com/rubygems/rubygems/issues/1419

@shmargum Legend! Thanks dude

Also @shmargum v1.5.0 has been released to rubygems.

thank you 👏


multi_gpu_copy

Hi,
When running test.sh I am getting the following errors:
 Function call failed
torch/install/share/lua/5.1/cutorch/init.lua:21: cuda runtime error (2) : out of memory at /tmp/luarocks_cutorch-scm-1-7982/cutorch/lib/THC/THCStorage.cu:30 ```

I have only one GPU though...
Thanks for your help,

it's okay to have this issue, and is harmless. we wrote the test in the context of GPUs with large memory.


datapath: Redirect from bpf_overlay to egress gw SNAT netdev

Currently, when the egress GW node receives a packet from a remote pod which needs to be SNAT-ed to the egress GW IP, the packet is first handled by bpf_overlay@cilium_vxlan. The prog passes the packet to the stack, and eventually it should make to bpf_host@eth0 which does the SNAT.
However, if there is an iptables SNAT rule in the host netns, it might get into the way of egress GW. This is the case for AWS EKS iptables rules:
# iptables-save | grep AWS-SNAT-CHAIN
:AWS-SNAT-CHAIN-0 - [0:0]
:AWS-SNAT-CHAIN-1 - [0:0]
-A POSTROUTING -m comment --comment "AWS SNAT CHAIN" -j AWS-SNAT-CHAIN-0
-A AWS-SNAT-CHAIN-0 ! -d <IP_ADDRESS>/16 -m comment --comment "AWS SNAT CHAIN" -j AWS-SNAT-CHAIN-1
-A AWS-SNAT-CHAIN-1 ! -o vlan+ -m comment --comment "AWS, SNAT" -m addrtype ! --dst-type LOCAL -j SNAT --to-source <IP_ADDRESS> --random-fully

The SNAT rule was snatting the packet which made it to bypass the egress GW policy.
To prevent from this happening, we should do the ctx_redirect() from bpf_overlay.

@julianwiedmann @jibi Have we already fixed this?

Not yet, we still let the packet in the egress gateway node to go through the stack at the moment

To prevent from this happening, we should do the ctx_redirect() from bpf_overlay.

Just to note that we might have set up custom IP routes in the gateway node, so that traffic gets steered to the correct external interface. Bypassing those with a straight bpf_redirect() would be problematic.

Thinking out loud, but would a FIB lookup or bpf_redirect_neigh() be of any help here? (Not sure if they take into account also the IP rules)

Related: https://github.com/cilium/cilium/issues/23504 (potential solution for the above problem of traffic steering, as per Jibi's suggestion).


Facebook Auto Friending Not Working

m.627144

To enable this feature you need to request user_friends permission from facebook for you Facebook App and enable "Fetch extended profile info (facebook app review is required)" option in Facebook Connect module setting in UNA.


2601 - Extend cli doctor

#2601 Extend cli doctor with cli configuration

Adds cli configuration to cli doctor command. Closes #2601

Awesome! Thank you so much for such a quick turnaround. We'll review it in the coming days

Merged manually. Thank you! 👏


⚠ Turnos 24x7 has degraded performance

In 75a4ec1, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 2775 ms

Resolved: Turnos 24x7 performance has improved in 0c7f3bb.


add duplicate functionality to tags

This will make it easier to create tags with similar color schemes.

done


Release v7.0.0

This PR releases all changes from the alpha branch

:tada: This PR is included in version 7.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Java simulated device

@jeffreyCline,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Inject default feature instance

Feature Request
In some parts of the codebase there are situations were a required feature needs to be injected with a default implementation if none provided, in these situations, the feature is marked as "not required" and then loaded with a default implementation like:
https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/3b7d17938562948e34522d4c919e725269ad0b8b/extensions/api/data-management/asset/src/main/java/org/eclipse/dataspaceconnector/api/datamanagement/asset/AssetApiExtension.java#L68-L72
Would be good to have a way to describe a required feature with a default implementation
Which Areas Would Be Affected?
extension loader, injector
Why Is the Feature Desired?
To simplify the injection of a required feature with a default implementation fallback.
Solution Proposal
The API on injection could look like:
@Inject(defaultImpl = NoopTransactionContext.class)
TransactionContext transactionContext;

Type of Issue
improvement
Checklist

[x] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

@paullatzelsperger and I discussed this today. We came up with a different solution that does not require the client (injected) to have knowledge about the default implementation or whether a particular service has a default implementation or not.
We are thinking of adding the ability for an extension to declare "default provides" - i.e., that the extension can provide a default service if one is not provided by another extension. The behavior of this feature would be:

The default extension declares an optional @Inject field of the defaulted service type. The extension also declares that it "default provides" the service type via an annotation.

If no other extension provides the service, the default extension is instantiated, and the injected field will be null. The extension can check this and register the default implementation.

If another extension provides the service, the default extension will be injected with the other implementation.

The runtime bootrapper will need to determine if an extension that provides a service implementation is configured for this to work. If it is not, the extension providing the default implementation will be used as the providing extension. If there is an extension configured that provides a service implementation, that extension will be used as the providing extension. In the latter case, the default extension will have a "requires" implicitly added that resolves to the other extension. This will guarantee proper extension ordering.
This mechanism will enable us to consolidate a number of extensions. Let's discuss this post-M3 since it is a bit late to introduce this type of change for M3.

@ndr-brt I can take this on if that's ok for you

@paullatzelsperger I already have a solution that at least solves the duplication issue and also the ExecutorInstrumentationImplementation issue, currenty the solution requires the client to specify the default implementation (as I specified in the issue),
but I noticed that this default declaration could be moved on the @Feature annotation, so the default instance is specified by the feature directly, so the clients couldn't need to worry about the default implementation.
I would open this PR as a first step to go in the direction of the 3 points specified by @jimmarino if you agree.

@paullatzelsperger Why don't let the @Feature being able to define a default implementation instead of having a "default extension" to do so? It seems simpler and it covers all the cases currently present in the codebase.

For one, because that would introduce a downstream dependency, for example TransferProcessStore is located in transfer-spi, but the default implementation (=in-mem) would either be located in a separate module, or potentially in the corresponding module in core, thus :core:transfer. Therefore, suddenly :spi:transfer-spi has a dependency on either of those two.
The second reason is, that @bscholtes1A and I were actually conspiring to remove the @Feature annotation altogether, as it is merely an alias for the class name, which is the default already.

Got it, I can work on this since I'm already on it

@paullatzelsperger @ndr-brt How about removing @Feature entirely?

Superseded by #1130


⚠ ClamAV has degraded performance

In 10f7e9f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 182 ms

Resolved: ClamAV performance has improved in bf49d87.


Complete proxy support [bsc#1043538]

This pull request completes the work around handling proxy settings from velum.
It implements missing features like:

Handle the proxy:systemwide pillar that was introduced by this pull request inside of the salt repository.
Handle proxy settings inside of AutoYaST, fixing bsc#1043538.

It also fixes previously uncovered bugs:

Not being able to unset certain pillars from velum (see this specific commit).

Finally it changes the UI to allow an easy way to enable/disable proxy settings. See the video below:

ping @kravciak: if this PR gets merged the openQA needles will need to be updated.

Adding @vitoravelino to review the frontend part of this PR 😉

Rubocop is also complaining. Forgot to mention that.

Rebase also needed.

I fixed all the rubocop issues, @vitoravelino's comments and I rebased.
Now I have to take care of @thkukuk's feedback.

@thkukuk : do you have any idea why AutoYaST sets also the /root/.curlrc file? Aren't the /etc/sysconfig/proxy settings enough?
I'm asking because if that's not enough we should also change our salt states to deal with /root/.curlrc changes too (I've already the code done locally, but I don't want to push something useless/redundant).

 Bug 1043538 - AutoYaST profile has no proxy configuration

On Thu, Jun 29, Flavio Castelli wrote:

@thkukuk : do you have any idea why AutoYaST sets also the /root/.curlrc file?
Aren't the /etc/sysconfig/proxy settings enough?

I couldn't find anybody who remembers why, the people who should know more
are on vacation.
But our best guess is: zypper is using libcurl. So if you run zypper from
a cronjob or su, the /etc/sysconfig/proxy variables are not parsed and set
in the environment. Which means, zypper will not use the proxy and fail.
With /root/.curlrc, libcurl will use the proxies configured there.
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

Thanks @thkukuk, I created https://github.com/kubic-project/salt/pull/140 to handle /root/.curlrc also from salt.

On Thu, Jun 29, Kiall Mac Innes wrote:

@kiall commented on this pull request.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
In app/views/dashboard/autoyast.xml.erb:

@@ -40,6 +40,32 @@

<% end %>

+<% if @proxy_systemwide %>

Why postpartitioning-scripts instead of chroot-scripts? If proxies are normally
done in stage 2 (post reboot), then why would we do them so early? Will yast
fix the permissions on the 2 folder we create? /root needing to being go-rwx
and /etc/sysconfig being go+rx

I think Flavio was using postpartitioning-scripts, because it's easier
to cate the proxy file.
But correct is really to do it as chroot-scripts like the others, and
not use echo, but sed to adjust the variables in /etc/sysconfig/proxy
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

I used a post-partitioning script because the chroot ones are executed after the system has been installed, right before rebooting it (at least that's what I got reading this page).
Assuming a customer has a proxy configured inside of his network and doesn't have SMT (hence packages are taken from SCC), we need to set the proxy before zypper is ever invoked otherwise it won't be possible to download any package.
That was my reasoning.

Hi,
On Thu, Jun 29, Flavio Castelli wrote:

I used a post-partitioning script because the chroot ones are executed after
the system has been installed, right before rebooting it (at least that's what
I got reading this page).
Assuming a customer has a proxy configured inside of his network and doesn't
have SMT (hence packages are taken from SCC), we need to set the proxy before
zypper is ever invoked otherwise it won't be possible to download any package.
That was my reasoning.

zypper is not using this values from the to be installed system, but
from the inst-sys (we call the equivalent of zypper -R ...). So no need
to write this variables very early.
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

zypper is not using this values from the to be installed system, but from the inst-sys (we call the
equivalent of zypper -R ...). So no need to write this variables very early.

Good to know, I'll change the code to create a chroot script then.

There's a ruby syntax error, and rubocop is failing as well. Feel free to ping me whenever it's ready to be reviewed again 😉

@mssola: I fixed the issues. Sorry, the code was broken after I rebased and I wasn't able to run the tests locally because of devenv being broken by the recent changes.

I just squashed the commits together to remove some clutter. Forcefully merging.


Use of @xnext doesn't match its definition

With a build using Ubuntu 22.04's texlive, I was running into floats - Error when inserting figure ! Use of @xnext doesn't match its definition - TeX - LaTeX Stack Exchange. As suggested there, the solution was just to upgrade, in my case by using texlive/texlive Tags | Docker Hub. That is, with something along the lines of:
docker run -u 1000:1000 --rm -it -v $(pwd):/workdir texlive/texlive make

See also xu-cheng/latex-action: :octocat: GitHub Action to compile LaTeX documents, used in Fix typos (#350) · OpenLogicProject/OpenLogic@4da084f.
I'm just documenting this here in case someone else runs into it.

Yep you're fine. I assume Ubuntu 22.04 is a relatively common operating system, and I always search closed GitHub/GitLab issues for hints with build problems, so I was just trying to help someone similar.


path of ias credentials is hardcoded

possible solution:
create template of core.yaml for fabric with placemarks for ias credentials path
expand the template with environment variable set by user

You do mean it is hardcoded in the core.yaml

yes.

Is this still a concern? I also think the title of this PR is a bit misleading as it says hardcoded, which I think refers to hardcoded-in-code-somethere, whereas core.yaml actually points to ias/api_key.txt.
Closed for now. If still an issue we can reopen.


Unofficial store event triggered for Firebase App Distribution

Describe the bug
In my setup, I added supportedAlternativeStores: ['dev.firebase.appdistribution']. But on running the app, the unofficialStore event was triggered.
To Reproduce

On set up, add supportedAlternativeStores: ['dev.firebase.appdistribution'] in androidConfig.

Expected behavior
Installing the app from Firebase App tester should not trigger unofficialStore event.
Please complete the following information:

Device: TECNO CC7
OS version: ANDROID 9
Version of freeRASP: 3.4.0

Hello @klazbaba ,
could you send us your watcherMail and package name on<EMAIL_ADDRESS>We can look at the data to see what is the source of installation.
Kind regards,
Talsec team

Hello @klazbaba ,
could you elaborate further on the issue? Thank you!
Kind regards,
Talsec team

Hello @klazbaba ,
could you elaborate further on the issue? Thank you!
Kind regards, Talsec team

The issue was that I wanted the unsupported source event to not trigger when the app is installed from firebase distribution. So I added supportedAlternativeStores: ['dev.firebase.appdistribution'] like it was mentioned in the doc. But after installing the app via firebase distribution, the event still got triggered.

Hello @klazbaba ,
please elaborate further on sending the watcherMail and package name at<EMAIL_ADDRESS>as asked above, so we can look at the logs.
Kind regards,
Talsec team

Hello @klazbaba , please elaborate further on sending the watcherMail and package name at<EMAIL_ADDRESS>as asked above, so we can look at the logs.
Kind regards, Talsec team

We removed the check for alternate stores after I opened this issue. So I think I'll just close this.

@msikyna I am facing the same issue as the OP and I have sent the app details to the support email. Hoping we can get to the bottom of this issue.


Update sa103f mapping CSV file to v2

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.


Optionally support self signed SSL certs for GitHub Enterprise connections

I would strongly discourage providing this option. Remember, disabling certificate verification doesn't mean only that a self-signed certificate is okay.

Closing in favor of setting CUMULUSCI_SYSTEM_CERTS see: https://github.com/SFDO-Tooling/CumulusCI/blob/main/cumulusci/utils/http/requests_utils.py#L23

Thanks for the feedback @davisagli !


Point to a shared Move Discord #25_12

/canary

:sunny: Canary successful

Not Approving due to lack of description and test coverage. Can we please add more detail.


[Azure Websubhub] Introduce retry feature for subscription verification

Description:

$subject

Please keep the issue assigned to the person who is working on it.


Alignment Fixed #5478

Issue Reference
Link: https://github.com/bagisto/bagisto/issues/5478

now its working


Deprecate visualizer

Changes:

support for models without an entity recogniser (only an intent classifier) - see #116
no more visualizer - use the trainer instead.

add this screenshot to docs

@amn41 please update docker image too, as well would be great to have a better documentation how to use Rasa NLU with docker, I mean to do all the things what we have in get started guide only when you just up the docker container
👍 good interface!


markdown window can't marked color in single view

I've just pushed an update that should fix this issue. Let me know if that's not the case. Thanks for reporting!


test issue to see if I've fixed the console and discord output

Issue created by TheSkeward#1111.

Test of create github function, closing


CouchDB config corrections, reverse proxy documentation, other additions

enable_cors is now under section [chttpd] since version 3.2.
Not everyone will use version 3.2+ so I made it clear that's a new thing.
Added bind_address for making sure the container uses all interfaces given; I myself use Traefik as a reverse proxy and using this somehow made it work, since this option does not harm other reverse proxies and there are lots of Traefik users this option should be there for wider compatibility.
Added spaces between origins elements and removed spaces between the methods elements because it's like this in the official documentation, see 1 and 2.
Added a write permission warning since many newbies had this mistake with couchdb, including myself.

Hi, wasn't able to find documentation on how to selfhost couchdb behind traefik, because of this I overexplained a bit. Shouldn't harm anybody.
The second commit I added the Traefik reverse proxy files and documentation, along with a Table of Contents.


[Bug] The latest version of VSCode does not recognize installed extensions in the user's data folder.

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.74.1
OS Version: (Made using this PowerShell command, ([System.Environment]::OSVersion).ToString()) Microsoft Windows NT 10.0.19045.0

!!! VSCodium is also having the same problem. !!!
Steps to Reproduce:

Update VSCode to the latest version from the previous version (1.74.0).
Open VSCode and expect it to function normally.
Realize that all of your extensions are not on VSCode, making you scream in frustration.

Check the data folder to see if the extensions have been deleted. It's in the scoop/persist/vscode/data directory for me since I installed mine using Scoop.

Open the extensions folder
Check to see if the extensions have been deleted, in this case, it has not happened.

After all this, I downgraded back to the old version.

I saw this same problem with 1.74.1 (also installed from Scoop) and downgraded back to 1.74.0.

Downgrading didn't solve the problem for me, I had to get rid of all the extensions in my folder and manually download all of them.

Same problem here.
See this thread https://github.com/ScoopInstaller/Extras/issues/10013 for more info.

Can you please delete the file .init-default-profile-extensions in the extensions installation folder and restart?

I tried that and it didn't work.

@sandy081 This is what I had to do to get my extensions to be recognized again. See this comment for more info, https://github.com/ScoopInstaller/Extras/issues/10013#issuecomment-1354681002.

Have you also deleted extensions.json file in the extensions installation folder?

I'll try that.

That didn't work for me either. The only working solution for me so far is, delete all the extensions, and manually re-install them through vscode/vscodium.

Should I close this issue or should I keep it open?

Can you please provide me steps to reproduce?

Are these steps to reproduce not enough?

Update VSCode to the latest version from the previous version (1.74.0).
Open VSCode and expect it to function normally.
Realize that all of your extensions are not on VSCode, making you scream in frustration.

Check the data folder to see if the extensions have been deleted. It's in the scoop/persist/vscode/data directory for me since I installed mine using Scoop.

Open the extensions folder
Check to see if the extensions have been deleted, in this case, it has not happened.

After all this, I downgraded back to the old version.

@sandy081 Thank you for your help but I already found a solution for my extensions problem. I just had to change the pass in the extensions.json file to match the current path that vscode/vscodium is in.

See this comment, https://github.com/ScoopInstaller/Extras/issues/10013#issuecomment-1360972157

/duplicate
Seems like the issue is related to paths stored in extensions.json file, then it shall be fixed by https://github.com/microsoft/vscode/issues/169006
Please note that with this fix, you do not need to update paths in the above file.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

@sandy081 Thank you for your time.


Possible to show seconds?

Hi, very nice card, was waiting for this!
Just a short question, is it possible to show seconds?
Thanks!!

Hi, very nice card, was waiting for this!
Just a short question, is it possible to show seconds?
Thanks!!

Oops, sorry, did not read the documentation correctly :-(
My apologies: timeFormat: HH:mm:ss does the trick!


Incomplete Sentence

It's great to see you teach X about Y so that they're.

https://github.com/ksindi/managers-playbook/blame/master/README.md#L141

Thanks @MatthewSclafani! Will update.


Fix Uglify when devtool is not set

Fixes #5.
ExtractText, Uglify, and source-maps together use source map features that are currently broken under HardSource.
Uglify, unless its sourceMap option is explicitly set to false, uses source maps to give more clear warnings and errors. When it does this it sets useSourceMap on modules which when set we'll now store source maps without passed options. That'll retain the need source map info for Uglify to work.

[x] Write a test
[x] Ensure webpack 1 support
[x] Ensure webpack 2 support

Found the issue. The original name of this pull isn't accurate. Its not those three together. Its just the first two. I typo'd devtool to devTool in the original test, thats why the original test fails.
The actual issue is UglifyJsPlugin uses source maps to give more clear warnings and errors. If you don't have a devtool option set, before this Pull HardSource doesn't store source maps. When the second build without maps occurs, HardSource tries to make a SourceMapConsumer without a source map to power it. To fix this we need to store source maps for plugins like UglifyJs to consume. I'm probably going to add an option to store that.

@mzgoddard looks like this is an issue on our end.
https://github.com/MoOx/phenomic/issues/644#issuecomment-241443286
How do you suggest to fix this? Add a devtool field ?

@thangngoc89 I wouldn't say so. You can work around it by setting the devtool to any sourcemap configuration. That instructs HardSource to save those maps.
I discovered into this that UglifyJsPlugin sets useSourceMap on modules. And many module's use that as a trigger to build more complete source map info. I decided to use that same property to determine if sourcemap should be stored separate the devtool configuration.
0.0.19 includes this change, so you shouldn't need to make a config change.
If you wanted you could set UglifyJsPlugin's sourceMap: false option. That may lead to a slightly faster build time as UglifyJsPlugin won't get source maps for its warnings (this will make the warning's file line and column values inaccurate). That option set to false and without devtool being set, HardSource also will store no source maps leading to a possible build boost. Naturally this trades build performance for error information.

I install  0.0.19 for my branch and it works like a charm, this is a huge perf improvement for us. I'll implement hard-source-webpack-plugin for any webpack project that I'm working on. Thanks a lot


Refactor endianness

Right now we got too much flexibility for endianness. Look into having only one at file level; or maybe one for binary one for trace.

Fixed by #57


just allow params as kwargs?

this would remove the need to wrap things in lists.
idk if its worth it though. I need to manufacture myself a user who is not me and figure out what they would like
imagining something like
λ = np.linspace(500, 600,100)
β = np.linspace(0,1,1000)
`interactive_plot(f, λ = λ, β=β

which then is also nice for adding labels to the sliders.

possible should take inspiration from the xarray sel method. I think that allows both explict setting and via a dict


Native token contract wrapper interface

What
Resolves #316, https://github.com/stellar/soroban-token-contract/issues/5, and https://github.com/stellar/soroban-token-contract/issues/80
Why
Interoperability with classic.
Known limitations
No tests yet so it might not actually work

I'm going to resolve conflicts and merge this. We can figure out how to test it after.

No tests yet so it might not actually work

We can figure out how to test it after.

More recently we've started to chew time on things that weren't tested in the host. I think there would be some value in verifying this works with some basic tests, especially if we are suspicious it doesn't work.

I'm not saying we shouldn't test it. I'm saying I want to merge this so it doesn't get stale again.

cc @sisuresh @dmkozh since I think you'll possibly be picking this and #428 up.


Question: Any plans for an Azure Application Gateway task?

Before I go writing one myself, just thought I'd ask if there are any plans for an Azure application gateway task?
Here's a brief description of the use case:
We are currently migrating various legacy sites, to run as containers on Service Fabric. The build and release of these solutions is fully automated via VSTS with the one exception, that if a new container is added to the solution, then an Azure Admin must manually update the application gateway with the new path rule mappings etc.
What I'm thinking, is that a vsts task could use the information in the docker-compose files, to automate this procedure, so that new projects will be automatically mapped, without having to involve manual steps.

@CodedBeard  we have a generic Azure PowerShell and Azure CLI task that would be a good place to start.

We do have plans to add Application Gateway feature, however, it is fairly low on our backlog (>6 months).

Thanks @RoopeshNair, I'll have a go at making one myself in that case.


[IOTDB-4850] Disable first election

First election aims to reduce the unavailable time during consensus group starts-up. However, in current implementation, it may cause new follower receive SHUTDOWN errors.
I'll disable it for now.

This PR is superseded by https://github.com/apache/iotdb/pull/8016. I'm closing this for now.


How to skip the popup thingy?

After i press any boot entry how do i skip the popup and directly go to boot?

The pop up is the console which you can also open by pressing "C" while in the grub menu. When selecting an entry it apparently always opens the console (just in case it needs to print something like "Loading Linux...") so idk, I haven't found a way to hide it yet.

And is there any way to use that console?  You could try to inject some echo commands there.
See here: https://www.gnu.org/software/grub/manual/grub/html_node/Shell_002dlike-scripting.html
Let me know if you achieve a progress bar! Closing this for now.


koord-manager: fix  LessThanOrEqual in elastic quota

Ⅰ. Describe what this PR does
fix LessThanOrEqual for elastic quota webhook

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm
/approve


Production server WSOD

The production server displays a WSOD (white screen of death) 1 minute 32 seconds after starting the optimization of a page with 20 vehicles, 3 shifts loaded to 150%:
Screenshot WSOD:

Screenshot daily plan, after WSOD:

References: google Symfony WSOD

Running the same thing with app_dev displays the same WSOD.

Exception processing in production (config.yml):

Remedies:

Perhaps Symfony and FOS need to be synchronized.
Perhaps revert to the default (no FOS)

Three fixes made, but having no effect on the handling of errors. Symfony and PHP seem to have compatibility issues regarding errors which are handled in different ways.
Removed the FOS implementation in order to reduce complexity and dependancy (now using the default for Symfony/Twig).
References:
Google for "Symfony WSOD", you will find plenty which are both closed and reopened again. There doesn't seem to be any one clear issue for this. The code seems to be lousy.

Leaving this issue for the time being, have more pressing matters to solve.


Add circe-kafka to list of integrations

I wrote a micro-library that makes using circe in combination with Kafka (Streams) very convenient by generating Kafka's Serializer, Deserializer and Serde implicitly from Encoder and Decoder instances.
This PR adds a reference to the library to the README

Codecov Report

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

@@            Coverage Diff            @@
##           master    #914      +/-   ##
=========================================
+ Coverage   85.52%   85.6%   +0.08%
=========================================
  Files          76      76
  Lines        2459    2459
  Branches      157     157
=========================================
+ Hits         2103    2105       +2
+ Misses        356     354       -2

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
90% <0%> (-1.25%)
:arrow_down:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0%> (+2.7%)
:arrow_up:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
100% <0%> (+8.33%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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

Excellent, thanks!


[5.7] Store source locations of builder expressions for regex compilation errors

Cherry-pick of #561.

Store source locations using buildExpression(_:) and print locations upon regex compilation errors. The regex builder DSL proposal already includes a buildExpression(_:) that stores source locations in a RegexComponentBuilder.Component<R> type.
Resolves rdar://96119443.

 Found a reference used before it captured any match. Used at:
// - .../Tests/RegexBuilderTests/RegexDSLTests.swift@testBackreference():1126:10
// - .../Tests/RegexBuilderTests/RegexDSLTests.swift@testBackreference():1127:10

@swift-ci please test

Did you mean to close this one?

Ah, I see your comment on the original.


remove static linking

#617 fix

These issues are intermittent so until we understand why they happen, we won't have any "fix", just attempts at fixing it.

We default to Rust now for linear regression.
On Fri, May 5, 2023 at 11:21 AM Lev Kokotov @.***>
wrote:

@.**** commented on this pull request.
In pgml-extension/tests/test.sql
https://github.com/postgresml/postgresml/pull/620#discussion_r1186384073
:

@@ -27,4 +27,5 @@ SELECT pgml.load_dataset('wine');
\i examples/multi_classification.sql
\i examples/regression.sql
\i examples/vectors.sql

+-- transformers are generally too slow to run in the test suite
+--\i examples/transformers.sql
Yeah, we would segfault inside scikit when trying to train a logistic
regression model (or maybe it was a linear regression). One of those uses
clbas.
—
Reply to this email directly, view it on GitHub
https://github.com/postgresml/postgresml/pull/620#discussion_r1186384073,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACDNHOQBAOX5YUFWVKNKSLXEVAK7ANCNFSM6AAAAAAXWNSUQY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Funny enough, google only knows 1 source for this config, which happens to be @levkk's blog post, which documents that I was the original reporter of a crash, that I'd completely forgotten about, and hadn't really understood, because he was the one doing the Python/Rust transition at the time.
https://postgresml.org/blog/backwards-compatible-or-bust-python-inside-rust-inside-postgres
We know that old versions of scikit crash using CBLAS, and I know that I was on a 18.04LTS when this post was written, so it makes sense I started exercising this crash when @levkk gave Python in Rust access to my dynamically linked CBLAS installation with py03, but my system Python was not otherwise configured with access to CBLAS, so it was unaffected.
This line forces openblas-src crate to skip the ["cblas", "system"] features which dynamic links to system CBLAS, and instead statically link to the bundled OpenBLAS. This prevents scikit from having access to a dynamically linked CBLAS crash in older versions, which "fixed" my original issue, but now we're seeing issues w/ statically linked OpenBLAS on @eeeebbbbrrrr's machine. I think the "right fix" is to upgrade scikit to a version new than 2019, and dynamically link CBLAS, which is the standard, not to statically link OpenBLAS.


*.d.ts, *.js, and *.metadata.json files are getting generated in my src directory when using angular 2 barrels

*.d.ts, *.js, and *.metadata.json files are getting generated in my src directory when using angular 2 barrels. If I remove the barrel, then they are not generated in the src directory.
It would be nice if they were not put in the src directory because when you try and build again the linter and the build fails because it is not expecting those files to be there.
Steps to reproduce:

Create a barrel for a one of your ts files (I tried putting it both outside and inside the source directory and still had the issue)
Update you other ts files to use the barrel to import the class in the ts file.
Run "ionic run android"

Result
*.d.ts, *.js, and *.metadata.json files are get generate next to the *.ts files in the src directory (at least the ones using barrels do)
"scripts": {
    "build": "ionic-app-scripts build",
    "watch": "ionic-app-scripts watch",
    "serve:before": "watch",
    "emulate:before": "build",
    "deploy:before": "build",
    "build:before": "build",
    "run:before": "build"
  },
  "config": {
    "ionic_rollup": "./scripts/rollup.config.js"
  }

Which @ionic/app-scripts version are you using?
ionic CLI 2.1.0
ionic 2 RC0
angular 2.0.1
@ionic/app-scripts 0.0.30 (latest)

Hello, thanks for using Ionic! I am going to close this issue as a duplicate of https://github.com/driftyco/ionic-app-scripts/issues/105.

@jgw96 Is this really the same issue? They were getting the following error:
Error: Module .../ionic/src/app/index.ts does not export ComponentData (imported by .../src/components/module-components/module-component/module-component.ts) at Module.trace (.../node_modules/rollup/dist/rollup.js:7706:29)
I am not getting that error. It builds fine if I delete all those files. I am just getting metadata files generated in my source directory when using barrels. Help me understand how this is the same issue as #105

@jgw96 I am not trying to be annoying. I know you guys are hard at work fixing things. I just want to make sure my issue doesn't get lost. Are you sure this is the same issue as #105? It has to do with barrels, but it appears to me to be a separate issue for me. Would you be able to clarify why you think this is the same issue.
Thanks for ionic and keep up the good work!

Look like its fixed with Ionic RC1 + Angular 2.1.0.

I have updated my app to RC2 and still having this problem.  Is it possible that I have some leftover build options that are still screwing things up?  Any ideas?
Thanks,
Marc

For information...
tsconfig.json:
{   "compilerOptions": {     "allowSyntheticDefaultImports": true,     "declaration": true,     "emitDecoratorMetadata": true,     "experimentalDecorators": true,     "lib": [       "dom",       "es2015"     ],     "module": "es2015",     "moduleResolution": "node",     "target": "es5"   },   "exclude": [     "node_modules"   ],   "compileOnSave": false,   "atom": {     "rewriteTsconfig": false   } }
And tsconfig.tmp.json:
{   "compilerOptions": {     "allowSyntheticDefaultImports": true,     "declaration": true,     "emitDecoratorMetadata": true,     "experimentalDecorators": true,     "lib": [       "dom",       "es2015"     ],     "module": "es2015",     "moduleResolution": "node",     "target": "es5",     "outDir": "{{MyRepo}}\\.tmp"   },   "exclude": [     "node_modules"   ],   "compileOnSave": false,   "atom": {     "rewriteTsconfig": false   },   "include": [     "{{MyRepo}}\\src\\app\\main.dev.ts",     "{{MyRepo}}\\msyp\\Documents\\Bitbucket\\immersive-patient-room\\src\\**\\*.d.ts"   ] }
It seems like the "include" section might be causing problems? No idea.

add
  "include": [
    "src/**/*.ts"
  ]

in your tsconfig

Thanks for the response -- unfortunately that didn't help.  Also tried changing "sourceMap" to false, as I thought maybe that was part of it, but no change.  Any other ideas?
Thanks.

The good news is that for some reason the build is not failing anymore, at the very least... still wondering why all these files started appearing in my src folder...

They are needed for AoT compilation.


Crow server not responding when TLS is used

Code:
#define CROW_ENABLE_SSL
#include "dependencies/crow_all.h"
int main()
{
crow::SimpleApp app;
CROW_ROUTE(app, "/")
( {
return "Hello world!";
});
app.port(18080).ssl_file("test.crt", "test.key").run();
}
Compiling Statement
g++ src/authentication.cpp -o build/authentication -std=c++11 -lboost_thread -lboost_system -pthread -lssl -lcrypto
Execution

Response on Web Browser

Generated test.crt and test.key (compressed)
test.crt+test.key.zip

Did you use https in your url? try https://<IP_ADDRESS>:18080/

@moneroexamples I am currently using crow with apache2 server. HTTPS encryption is functional between Apache server and the client.

It should work. I using crow with nginx server. And HTTPs encryption work very well.


Update dev-ko branch with main branch

Hi, This is my first PR in CNCF glossary.
This PR will update dev-ko branch with the latest changes in main branch.

Hi @yuzin9712
Thank you for your contribution to help management of the localization branch !!
LGTM :)

This PR does not require contents review.
(merge existing commits in main branch into dev-ko branch)
Let me merge this PR as a maintainer.


Add headingRowColor to PaginatedDataTable

Use case
Just like the normal DataTable, PaginatedDataTable should also make it possible to set the heading row color.
Proposal
Add a paramater "headingRowColor" to PaginatedDataTable, similar to the one on DataTable.
Looks like PaginatedDataTable simply uses DataTable internally, so it might only have to be passed through to work.

Can i work on this?

I would like to work on this.

@npsulav did some great work to fix this but unfortunately wasn't able to complete it so the PR has been closed. If anyone would like to start from that PR and apply the review comments and drive this PR to completion, you are definitely welcome to do so! The PR in question is https://github.com/flutter/flutter/pull/101556.


No named parameter with the name 'shadowThemeOnly'.

../../flutter/.pub-cache/git/flutter-cupertino-date-picker-3a6b1513d77636976794b6c64630b7ae219fb371/lib/src/date_picker.dart:103:34: Error: No named parameter with the name 'shadowThemeOnly'.
theme: Theme.of(context, shadowThemeOnly: true),
^^^^^^^^^^^^^^^
../../flutter/packages/flutter/lib/src/material/theme.dart:107:20: Context: Found this candidate, but the arguments don't match.
static ThemeData of(BuildContext context) {
^^
FAILURE: Build failed with an exception.

Making date picker for only days like below, it show only 30 days in the picker, when we show days it should show 31 days in the picker.
DatePicker.showDatePicker(context, dateFormat: 'dd',
        onChange: (date, u) {
        }

You should've migrate to flutter_cupertino_datetime_picker. That solved the problem to me, I found the solution in another thread #152.


lxd-user: Fix use with clusters

Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Testsuite passed


Flow does not report any errors

Flow version: Flow, a static type checker for JavaScript, version 0.95.1
Expected behavior
Type errors are reported.
Actual behavior
No type errors are being reported.
This is not reproducible with the file in question and I can't share the repository. I am happy to provide any additional information or do any sorts of debugging necessary.
An obvious error, like function f(x: number): number { return x } with f("foo") is not reported by flow although type-at-pos reports the correct types for both the function call as well as the declaration. flow ls also contains the file in question.
If in introduce the same error in a smaller file at the top-level of my project it is correctly reported.
.flowconfig:

[ignore]

[include]

[libs]

[lints]

[options]

[strict]

I am sorry for not being able to provide a reproducible use-case or more information. I also don't know at which Flow version this issue started to appear. Only that 0.94.x had the same issue.

@joa did you try flow stop?

@goodmind Yes. As well as flow focus-check file-in-question.js

@joa was your editor open during that check, or terminal only?

I did have the editor open. I re-tested this with the editor being closed and ensuring no node and/or flow process was still active. The result is the same.
However it does seem like I am getting some errors but just not all. For instance, I added another error in a different file and that error was reported correct.

VS Code says that there is 0% coverage from flow.
There is a // @flow header present and when I try to create a minimal working example, I never encounter the  issue and get the appropriate error.

Here is some more output:
> flow stop; flow coverage ./src/sdk/http/assets.js
Trying to connect to server for `/Users/joa/Development/app-web-livevideocloud`
Told server for `/Users/joa/Development/app-web-livevideocloud` to die. Waiting for confirmation...
Successfully killed server for `/Users/joa/Development/app-web-livevideocloud`
Launching Flow server for /Users/joa/Development/app-web-livevideocloud
Spawned flow server (pid=42869)
Logs will go to /private/tmp/flow/zSUserszSjoazSDevelopmentzSapp-web-livevideocloud.log
Monitor logs will go to /private/tmp/flow/zSUserszSjoazSDevelopmentzSapp-web-livevideocloud.monitor_log
Covered: 54.52% (181 of 332 expressions)

> flow stop; flow check ./src/sdk/http/assets.js
Trying to connect to server for `/Users/joa/Development/app-web-livevideocloud`
Told server for `/Users/joa/Development/app-web-livevideocloud` to die. Waiting for confirmation...
Successfully killed server for `/Users/joa/Development/app-web-livevideocloud`
Found 0 errors

> flow stop; flow focus-check ./src/sdk/http/assets.js
Trying to connect to server for `/Users/joa/Development/app-web-livevideocloud`
Warning: no server to kill for `/Users/joa/Development/app-web-livevideocloud`
[2019-03-29 14:25:22.874] Checking 1 files
[2019-03-29 14:25:22.885] executable=/Users/joa/.config/yarn/global/node_modules/flow-bin/flow-osx-v0.95.1/flow
[2019-03-29 14:25:22.885] version=0.95.1
[2019-03-29 14:25:22.885] No saved state available
[2019-03-29 14:25:22.886] Parsing
[2019-03-29 14:25:27.143] Building package heap
[2019-03-29 14:25:27.347] Loading libraries
[2019-03-29 14:25:28.187] Resolving dependencies
[2019-03-29 14:25:29.466] to_merge: Focused: 0, Dependents: 0, Dependencies: 0
[2019-03-29 14:25:29.466] unchanged_checked: Focused: 0, Dependents: 0, Dependencies: 0
[2019-03-29 14:25:29.466] Calculating dependencies
[2019-03-29 14:25:29.466] Merging
[2019-03-29 14:25:29.466] Merge skipped 0 of 0 modules
[2019-03-29 14:25:29.466] Done
[2019-03-29 14:25:29.466] Checked set: Focused: 0, Dependents: 0, Dependencies: 0
Found 0 errors

@joa do you use local (node_modules) flow or global?

@goodmind Both actually. This is a create-react-app project. For all the tests I did, I use just the standalone version.  Local flow is in sync with my global install.

Well, then I have no other ideas

@goodmind Apparently my project layout is like this:

src/app
src/comp
src/sdk

The app and comp folders do have flow coverage and receive errors. Anything within the SDK folder has no coverage whatsoever.

@joa how much of lines files have?

Approx 100kloc total

This is strange. I don't have any ideas other than those covered: the obvious things to confirm were that you have @flow headers and are not [ignore]ing these files. Can you run flow ls at the top level (wherever your .flowconfig is) and confirm that nothing under src/sdk is in the list?

I have something similar if I use function overloading like this, exported function becomes any
declare export function createGraph(opts: {|
  +node: Array<Cmd>,
  +child?: Array<Graph<any>>,
  +from?: Array<Graph<any>>,
|}): Graph<>
declare export function createGraph<Val: {[name: string]: any}>(opts: {|
  +node: Array<Cmd>,
  +child?: Array<Graph<any>>,
  +from?: Array<Graph<any>>,
  +val: Val,
|}): Graph<Val>
export function createGraph({
  node,
  child = [],
  from = [],
  val = {},
}: {|
  +node: Array<Cmd>,
  +child?: Array<Graph<any>>,
  +from?: Array<Graph<any>>,
  val?: {[name: string]: any},
|}): Graph<any> {//implementation}

@avikchaudhuri any thoughts?

This isn't reproducible if I use clean project, and use the same overloading

Yes flow ls shows the file. I might find some time next week to bisect this.

This issue is still labeled repro needed although @goodmind provided one.
This is a serious issue as type errors are simply ignored.

@avikchaudhuri

@joa  did you solve this, i have the same issue

@joa  did you solve this, i have the same issue

what happens if you re-run after first doing: rm -rf /tmp/flow?
I wonder if old definitions are hanging out in your cache (back when there were no issues)

I believe the problem should be fixed by recent version of Flow.

I am facing the same issue with latest version of flow. flow check  is reporting error correctly. but flow status or flow is still failing


no need to specify if the path is absolute or relative

Coverage decreased (-0.07%) to 92.449% when pulling cbc9c22145921cea26467a9b4d1b4e6d7b2bcabe on absolute-paths-detection into 70ea345d52038ac4b4b48f464e4f5805fb5ed8db on master.


[SPARK-17035][SQL][PYSPARK] Improve Timestamp not to lose precision for all cases

What changes were proposed in this pull request?
PySpark loses microsecond precision for some corner cases during converting Timestamp into Long. For example, for the following datetime.max value should be converted a value whose last 6 digits are '999999'. This PR improves the logic not to lose precision for all cases.
Corner case
>>> datetime.datetime.max
datetime.datetime(9999, 12, 31, 23, 59, 59, 999999)

Before
>>> from datetime import datetime
>>> from pyspark.sql import Row
>>> from pyspark.sql.types import StructType, StructField, TimestampType
>>> schema = StructType([StructField("dt", TimestampType(), False)])
>>> [schema.toInternal(row) for row in [{"dt": datetime.max}]]
[(253402329600000000,)]

After
>>> [schema.toInternal(row) for row in [{"dt": datetime.max}]]
[(253402329599999999,)]

How was this patch tested?
Pass the Jenkins test with a new test case.

Test build #63735 has started for PR 14631 at commit 962a052.

Test build #63735 has finished for PR 14631 at commit 962a052.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63735/
Test FAILed.

Test build #63736 has started for PR 14631 at commit b1c1be4.

Test build #63736 has finished for PR 14631 at commit b1c1be4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63736/
Test PASSed.

Hi, @davies .
Could you review this PR when you have some time?

The description is not correct, we keep the microsecond but lost precision in some corner cases, could you update that (also title)?

Thank you for review, @davies !
I'll update like that.

Test build #63751 has started for PR 14631 at commit cb921da.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63751/
Test PASSed.

Merged build finished. Test PASSed.

Hi, @davies .
It's ready for review again. Please let me know if there is something to do more.
Thank you so much again.

Hi, @davies .
Could you review this PR about Timestamp precision again?

LGTM, merging this into master.

Thank you so much, @davies !


consistent default instance_type for az selection

There was a bug relating to the default instance_type being hardcoded as two different values in two different spots for aws. Now the default instance_type for each cloud exists in only one place.

fixes #244


Upgrade to aws sdk v2 and fix issue #7

Hi @aymanbagabas , please help to resolve the merge conflicts.
Thank you so much!

@PhoenixPeca conflicts resolved!

Thank you so much @aymanbagabas ! I will check to make a release soon!

@PhoenixPeca do you need anything else from my end?

@PhoenixPeca do you think you could take another look at this pull request? I'm having issues with route53 and with a bit of luck an update like this might actually fix #11

If maintainer is inactive, would anyone here like to take up a maintainership role for this repo?

@mholt I wouldn't mind taking that role.

@aymanbagabas Sounds good, invite on its way in a moment. I like @charmbracelet btw!

@aymanbagabas Sounds good, invite on its way in a moment. I like @charmbracelet btw!

Thank you! Merging this one...


⚠ AsianCinema has degraded performance

In 8b61078, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 8128 ms

Resolved: AsianCinema performance has improved in 29ef6d7 after 6 minutes.


Populate Event name and Member name in Event Track list

Currently it is difficult to report on who delivered which event types. THe tabke in Event Track list includes reference to memberid and eventid. It is left to user to manually cross reference eventid to ID column in Event List and memberid to ID column in Member List.
Adding columns Member and Event Title/Type to Event Track Details and populating them when adding a row would make it better for tracking member activities better.
I recognize that the app shows activities when clicking on the person in leaderboard but it isn't sustainable in large orgs where sponsors might want to use PowerBI and other ways to report champion activities.

@bhargavshukla  -  we are now populating these items with version 1.2 on the Event Track List! When visiting that list now for recorded events the Member Name and Event title will show. Thanks for the feedback here.


Highlighting similar symbols (names, registers, etc.)

It would be nice if Ghidra highlights similar symbols (names, registers, etc.) in the listing and decompilation views so it is easier to track down where these symbols are being used.
Current behavior:

Desired behavior:

Use the middle mouse button. The feature is there, it's just not terribly discoverable.

And better, you could change it function to use left mouse :D

Also read up in the help section about "Higlight Forward/Backward (Inst) Slice"...
Ghidra then higlights all occurences of the variables plus additional tainted variables are instructions. Pretty neat...


Molecule and wsl2

Hi Jeff,
just playing around with molecule testing some of my clunky scripts and ran into an interesting issue.
It seems that docker on wsl2 isn't able to run systemd despite using your images. The same tests pulled onto a linux laptop work fine, but things like installing npm using your role fail on windows when the ensure running step fires off.
Bit of a pain.. but that's windows for you!!

Interesting... I hadn't spent much time with Molecule running directly under WSL2 but I'm wondering if it's an issue with the privs required through Docker on Windows running under WSL2 not being applied correctly.

It is possible to run Molecule but you need to unlock systemd with genie https://github.com/arkane-systems/genie. Genie allows you to use systemd inside WSL and the Molecule scenario. I tested it with Winver 1909, WSL2 Unbuntu 20.04 and Docker Desktop on Windows.

I was testing systemd permissions issues on WSL1, and it looks like it needs the command on top of privileged (or 'SYS_ADMIN' capability).
This:
privileged: True
command: "/usr/sbin/init"

Or:
capabilities:
  - SYS_ADMIN
command: "/usr/sbin/init"

So for the test scenarios:
platforms:
  - name: sysadmin_init
    image: local/centos7-systemd
    pre_build_image: true
    capabilities:
      - SYS_ADMIN
    command: "/usr/sbin/init"
  - name: sysadmin
    image: local/centos7-systemd
    pre_build_image: true
    capabilities:
      - SYS_ADMIN
  - name: privileged_init
    image: local/centos7-systemd
    pre_build_image: true
    privileged: True
    command: "/usr/sbin/init"
  - name: privileged
    image: local/centos7-systemd
    pre_build_image: true
    privileged: True

On Windows:
$ docker ps | awk '{print $NF}' | grep -vi names | while read line ; do docker exec $line systemctl status | head -n 1; done
    Failed to get D-Bus connection: Operation not permitted
    Failed to get D-Bus connection: Operation not permitted
    ● privileged_init
    ● sysadmin_init

I am also running into an issue, while trying to run molecule in WSL2 with docker desktop integration.
molecule test
zsh: correct 'test' to 'tests' [nyae]? n
INFO     default scenario test matrix: dependency, lint, cleanup, destroy, syntax, create, prepare, converge, idempotence, side_effect, verify, cleanup, destroy
INFO     Performing prerun...
INFO     Added ANSIBLE_LIBRARY=/home/mkukan/.cache/ansible-compat/96cf6a/modules:/home/mkukan/.ansible/plugins/modules:/usr/share/ansible/plugins/modules
INFO     Added ANSIBLE_COLLECTIONS_PATH=/home/mkukan/.cache/ansible-compat/96cf6a/collections:/home/mkukan/.ansible/collections:/usr/share/ansible/collections
INFO     Added ANSIBLE_ROLES_PATH=/home/mkukan/.cache/ansible-compat/96cf6a/roles:/home/mkukan/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
INFO     Using /home/mkukan/.ansible/roles/myname.myrole symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Running default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > lint
INFO     Lint is disabled.
INFO     Running default > cleanup
WARNING  Skipping, cleanup playbook not configured.
INFO     Running default > destroy
INFO     Sanity checks: 'docker'
Traceback (most recent call last):
  File "/home/mkukan/.pyenv/versions/ansible-cookbook/bin/molecule", line 8, in <module>
    sys.exit(main())
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/command/test.py", line 159, in test
    base.execute_cmdline_scenarios(scenario_name, args, command_args, ansible_args)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/command/base.py", line 118, in execute_cmdline_scenarios
    execute_scenario(scenario)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/command/base.py", line 160, in execute_scenario
    execute_subcommand(scenario.config, action)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/command/base.py", line 149, in execute_subcommand
    return command(config).execute()
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/logger.py", line 188, in wrapper
    rt = func(*args, **kwargs)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/command/destroy.py", line 107, in execute
    self._config.provisioner.destroy()
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/provisioner/ansible.py", line 705, in destroy
    pb.execute()
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule/provisioner/ansible_playbook.py", line 110, in execute
    self._config.driver.sanity_checks()
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/molecule_docker/driver.py", line 236, in sanity_checks
    docker_client = docker.from_env()
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/docker/client.py", line 96, in from_env
    return cls(
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/docker/client.py", line 45, in __init__
    self.api = APIClient(*args, **kwargs)
  File "/home/mkukan/.pyenv/versions/3.9.6/envs/ansible-cookbook/lib/python3.9/site-packages/docker/api/client.py", line 113, in __init__
    raise TLSParameterError(
docker.errors.TLSParameterError: If using TLS, the base_url argument must be provided.. TLS configurations should map the Docker CLI client configurations. See https://docs.docker.com/engine/articles/https/ for API details.

While testing the docker python client shows it can talk to docker server.
Python 3.9.6 (default, Aug 21 2021, 19:18:25)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import docker
>>> client = docker.APIClient(base_url='unix://var/run/docker.sock')
>>> client.version()
{'Platform': {'Name': 'Docker Engine - Community'}, 'Components': [{'Name': 'Engine', 'Version': '20.10.8', 'Details': {'ApiVersion': '1.41', 'Arch': 'amd64', 'BuildTime': '2021-07-30T19:52:31.000000000+00:00', 'Experimental': 'false', 'GitCommit': '75249d8', 'GoVersion': 'go1.16.6', 'KernelVersion': '<IP_ADDRESS>-microsoft-standard-WSL2', 'MinAPIVersion': '1.12', 'Os': 'linux'}}, {'Name': 'containerd', 'Version': '1.4.9', 'Details': {'GitCommit': 'e25210fe30a0a703442421b0f60afac609f950a3'}}, {'Name': 'runc', 'Version': '1.0.1', 'Details': {'GitCommit': 'v1.0.1-0-g4144b63'}}, {'Name': 'docker-init', 'Version': '0.19.0', 'Details': {'GitCommit': 'de40ad0'}}], 'Version': '20.10.8', 'ApiVersion': '1.41', 'MinAPIVersion': '1.12', 'GitCommit': '75249d8', 'GoVersion': 'go1.16.6', 'Os': 'linux', 'Arch': 'amd64', 'KernelVersion': '<IP_ADDRESS>-microsoft-standard-WSL2', 'BuildTime': '2021-07-30T19:52:31.000000000+00:00'}

Do you guys recommended going through genie installation that @florianow mentioned or is there a better way?

2024

WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
molecule 5.0.1 using python 3.11
ansible:2.16.4
docker:2.0.0 from molecule_docker requiring collections: community.docker>=3.0.0-a2

driver: docker
platforms:
  - name: rsyslog-server
    image: registry.access.redhat.com/ubi8/ubi-init
    command: /sbin/init
    privileged: True
    cgroupns_mode: host
    capabilities:
      - SYS_ADMIN
    tmpfs:
      - /run
      - /tmp
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:rw
      - /var/lib/containerd


support ie8 in built files

The built file currently contains .default which fails in IE version less than 9. The change I made will make the built file contain ["default"], which works in all browsers.

Thanks!

@ysmood would you be able to publish this change to npm at all?

Sure, tonight. Right now, I don't have a PC on hand.

I published the v0.17.6
Thanks for your support for yalu, and happy new year!


Documentation

Hi, I'm the developer of this Program, but I don't have enough time to make my program perfect. I'll appreciate it if you can help me improve it and become a contributor. Here is an existing issue:
This project lacks detailed documentation, please help me fill in
本项目缺乏完备的文档，请帮助我完善。

Please don't hesitate to ask me questions; also, leave comments before you start your work to avoid duplicated work.
如果你有任何疑问，欢迎留言询问我；请在开始前在此留言，防止他人进行重复的工作。

For subsequent contributors:

Regarding the addition of documents for JMobileSuit, it is necessary to temporarily submit (PR) them to the src branch of the Plastic-Metal.github.io. Currently, JMobileSuit's documents are hosted here (please note that JMobileSuit has undergone a major update in version 1.0, and much of the content may be outdated and may need to be combined with your own practice.

Regarding the addition of documents for MobileSuit, please submit the relevant changes directly to its own repository, whose documents are built based on docfx. Place the documents towards the correct place.

Regarding the addition of documents for PyMobileSuit, the Markdown file can be temporarily placed in the /docs directory of its own repository

对于后续的贡献者：

针对JMobileSuit的文档增加，需要暂时提交到Plastic-Metal.github.io仓库的src分支，目前JMobileSuit的文档被托管于此。请注意，JMobileSuit目前经历了1.0版本的大型更新，许多内容可能已经是过时的，可能需要结合你自己的实践。
针对MobileSuit的文档增加，请直接向他自己的代码仓库提交相关更改，它的文档基于docfx构建，请参考相关配置放置文档。
针对PyMobileSuit的文档增加，可以暂时把Markdown文件放在仓库的/docs目录下直接向他自己的代码仓库PR。


Documentation for secret-cli tool

Some examples of using the secret-cli tool with Trustee will be useful.
Also in general having docs for secret-cli will be useful.

Good idea. The best we have at the moment is https://github.com/confidential-containers/guest-components/blob/main/confidential-data-hub/docs/SEALED_SECRET.md

@fitzthum do you have an example of using sealed secrets with CoCo KBS? I don't find any examples of what should be the provider settings..

Provider should just be kbs.


Doesn't see local resources

please complete the following information:

OS version:       Pop!_OS 20.04

Editor:               VS Code

Editor version:  1.54.3

TabNine extension version: 3.2.16

Engine version (could be located within Tabnine Hub): 3.3.101-18

Issue Details:
Hi there!
As you can see, the local model is limited because my machine as it suggest doesn't satisfy minimum requirements.
But my PC double worth.

Hey @Searge ,
Please note that Tabnine requires FMA instructions (https://www.tabnine.com/faq#fma_instructions) which apparently your CPU does not support.

@boaz-codota ah, ok.
Just couldn't open that link on tooltip.


Shell completions for Cargo

This is a cleanup of a prior PR (#1425) by @ricvelozo.

Adds the ability to output shell completions for cargo using the command rustup completions <shell> cargo
Updates the completion instructions to mention and suggest placing bash completions in the home directory.

Hi @yodaldevoid
Thanks for your contribution.  Could you possibly tidy up the commit sequence (e.g. fold the fixes to formatting into the requisite commits instead of having a 'run rustfmt' commit) to make it easier to review?
I've put this PR on my list to watch but I'd like to see things a little tidier before I review.
I look forward to your changes.
D

Hello @kinnison
Thanks for getting to looking over this.  Is there anything else you would like cleaned up?
I should note that I wanted to keep @ricvelozo's commits mostly intact. They could get merged together with other commits, to condense everything, but I wanted to preserve his contribution.

Fair enough, I can appreciate wanting to maintain that.  I'll put this on my list to review as soon as I can (likely within a day or two)

:umbrella: The latest upstream changes (presumably #1630) made this pull request unmergeable. Please resolve the merge conflicts.

@kinnison Just wanted to ping you to make sure this hasn't fallen by the wayside.

FWIW, I'm proposing a new approach for completions for cargo at https://github.com/rust-lang/cargo/issues/6645.  It may not have any impact here, but just wanted to make you aware.

@ehuss I'll keep an eye on that discussion, and when/if it gets implemented if no one else does it I'll make sure to submit a PR moving to the new system for newer versions of cargo.

Thanks, @ehuss, I've been meaning to cross link that here.

:umbrella: The latest upstream changes (presumably #1704) made this pull request unmergeable. Please resolve the merge conflicts.

@kinnison Sorry about the long time since the last update. As the famous quote goes, "Life... finds a way to always get in the way of projects."
I believe I have addressed all requested changes. Please let me know if there is anything else you would like modified.

Thank you for making the updates, I'll endeavour to review this, likely tomorrow.

@kinnison I hate to be a hypocrite in this regard, but I wanted to ping you about this PR as it has been some time.

@kinnison I hate to be a hypocrite in this regard, but I wanted to ping you about this PR as it has been some time.

No, that's very fair, I needed a kick up the backside it seems the past two weeks have been busy and somehow this slipped off my TODO without me noticing :(

This looks reasonable to me, I'm grateful for the tests too.  I wonder if the user ought to be told about how the completions script they're given may vary with the default toolchain; but ultimately I think that's not worth blocking this for.

When can fish completions be added?

If you want to contribute, please help with https://github.com/rust-lang/cargo/issues/6645 .


Why do we not see full limiits, what about IO and bandwidth?   It makes migration harder to justify and harder to size.

See title, what can we expect currently for 32 vCore with 320GB? It is even worse when not logged in, we just see a page of marketing guff. We cannot see this in the portal any more since this is a retiring product.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 23a05b38-c79e-d02e-e01e-44c6f198a506
Version Independent ID: 34d62647-e41c-5581-7c47-24aa260e133c
Content: Limits - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/single-server/concepts-limits.md
Service: postgresql
Sub-service: single-server
GitHub Login: @sunilagarwal
Microsoft Alias: sunila

@mckenzm
Thanks for your feedback! We will investigate and update as appropriate.

@mckenzm
Thank you for bringing this to our attention.
I've delegated this to content author @markingmyname, who will review it and offer their insightful opinions.

After careful consideration, we have decided to discontinue further updates to single-server content.
This decision was not made lightly. Our team is committed to delivering the best possible experience, and focusing our efforts on Flexible Server will benefit you more in the long run.
#please-close


Issue with 404 mapping

As per customer's feedback:
•	With that bit of diagnostics in place I could see that the problem now was that I was getting a 404 but there was no "error" response defined in the OpenAPI, only the "default" response (the convention in Azure). So I build a jq script to convert all the "default" responses to "4XX" and rebuilt the client.
•	Sadly, this did not fix the problem.  Even with this change I was getting:
Discarding key error with value {'code': '404', 'message': 'Resource not found'}
This method does have a "4XX" response defined
    error_mapping: Dict[str, ParsableFactory] = {
        "4XX": response_error.ResponseError,
    }

So I don't know why it does not handle the 404 like an error response, but it doesn't.
After some investigation I discovered that the problem was the "base_url" was not set correctly -- it did not contain the "/anomalydectector/v1.1" pat segments specified in the "servers.url" of the OpenAPI definition.
"servers": [
{
"url": "{Endpoint}/anomalydetector/{ApiVersion}",
"description": "The Anomaly Detector API detects anomalies automatically in time series data. ",
"variables": {
"Endpoint": {
"default": "",
"description": "Supported Cognitive Services endpoints (protocol and hostname, for example:\nhttps://westus2.api.cognitive.microsoft.com)."
},
"ApiVersion": {
"default": "",
"description": "Api Version",
"enum": [
"v1.1"
]
}
}
}
]
So that I could make progress I just hard-coded these two segments into the base_url I set in the request_adapter, but it seems like there should be a better way.
•	The next problem was
Discarding key error with value {'code': '401', 'message': 'Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.'}
I was still using AzureIdentityAuthenticationProvider but MVAD uses api-key authentication, so for 'credentials' I passed an instance of AzureKeyCredential that was constructed with the api-key. That clearly didn't work. I read in the Kiota docs that I need to use ApiKeyAuthenticationProvider, but I couldn't find an implementation for this in Python.
I really wanted to get this to work so I wrote my own (it was pretty easy).

openapi.zip

CC: @samwelkanda @shemogumbe

There are three parts to this issue:

I don't know why it does not handle the 404 like an error response, but it doesn't.

Fixed in https://github.com/microsoft/kiota/pull/2700. The client raises the error. Missing keys are set in the additional data.
Example:
raise error
cdx.models.multivariate.response_error.ResponseError: {"message": null, "response_status_code": 401, "response_headers": "Headers({'content-length': '224', 'content-type': 'application/json', 'apim-request-id': 'ca74f830-555c-4780-91e0-8115f1fbb3d1', 'date': 'Thu, 22 Jun 2023 10:39:53 GMT'})", "additional_data": {"error": {"code": "0:00:00", "message": "Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource."}}, "code": null}

After some investigation I discovered that the problem was the "base_url" was not set correctly -- it did not contain the "/anomalydectector/v1.1" pat segments specified in the "servers.url" of the OpenAPI definition.

This should be the desired behavior since there are no defaults set in the OpenAPI definition.

I read in the Kiota docs that I need to use ApiKeyAuthenticationProvider, but I couldn't find an implementation for this in Python.

This is being tracked here

Since we fixed the issue that could be fixed in the generator and have an issue tracking the feature gap in the right repo, may I suggest we close this issue @isvargasmsft ?


Fix .trim syntax

Trim function not have arguments

In this example the correct word should not be "string" instead of "String"?

You're right, you should use 'string' in place of 'String'

thanks :+1:


[1.18.2 FABRIC] EMI and entity banner lag

Is it possible to disable mod in the emi menu?
EMI :
emi-0.4.0+1.18.2
Screenshot :

Not currently, but it's planned

Cleaning up old issues, items can be hidden by users and the lag mentioned in the title is unresolveable due simple to the cost of rendering items, so I believe this can be closed.


Creating a Cordova 6.3.0 gitignore file

I was looking to create a GitIgnore file for Cordova 6.3.0.  Would allow me to only commit code, instead of platform specific code from when you build and run cordova applications.

Fixed by #260


Revisit Selection Badges

The general feedback we are getting is that the numbers in the badges are confusing.  We should revisit these and figure out if they make sense, if they need better explanation, or perhaps should be removed or replaced with something else.

I think they should be removed because the numbers make users think the sidebar is a hierarchical ontology tree when it isn't.
Or the numbers could be rejiggered to align with this hierarchical ontology tree mindset.
If/when we implement #43, then we should keep the numbers because then there's no more "drilling down" to facilitate the perception that the sidebar is a hierarchical tree.
Uh, if anyone absolutely don't have anything better to do for 5 minutes, I get on a soap box here and talk about how I feel this issue is part of the broader Google vs faceted searching paradigms.

We need to make sure we remove calculation code for this.

probably better for serban to take a look at this?

#182 to address the removal of the calculation code


Improvement:  stop generating the favicon.ico in images folder on every build

Issue: We delete the favicon.ico file that's included with the initial build, but it is replaced on every build.
Why this is important: this set up does not allow for any other favicon path.
Details: We are using a single theme to provide related themes for different sites. Each site has its own favicons and logos that are placed in brand folders within the images folder. So the brand folders serve each site's favicon. But when there's a favicon file in the outer images folder this file often gets picked up by browsers instead of the favicon specific to that site. Our workaround is to unzip the war file and remove the default favicon each time before deploying.
I think it's helpful to have the favicon file initially, but once deleted it would be great if it could stay deleted...

My suggestion here would be to delete the top-level favicon using a gulp hook.
If you look in your generated theme the favicon is probably coming from ./node_modules/liferay-frontend-theme-unstyled/images/favicon.ico, and it is getting copied every time thanks to the build:base gulp task:
https://github.com/liferay/liferay-js-themes-toolkit/blob/6b5151d2173080b9eabdab4e9cf86b6693d1f9e9/packages/liferay-theme-tasks/tasks/build.js#L98-L105
So, the solution is to add a hook that runs after that task to clean up the unwanted file; something like this in the gulpfile.js:
const fs = require('fs');
const path = require('path');

liferayThemeTasks.registerTasks({
	gulp: gulp,
	hookFn: function(gulp) {
		gulp.hook('after:build:base', function(done) {
			fs.unlinkSync(path.join(__dirname, 'build/images/favicon.ico'));
			done();
		});
	},
});

Thanks that does work. For anyone needing the same fix: I used the asynchronous function fs.unlink rather than the synchronous fs.unlinkSync.


Test case failure

Did npm test and got back this error
not ok 54 should be equal
operator: equal
expected: 2
actual:   3
at: commandHandler (/mongojs/node_modules/mongodb/lib/mongodb/cursor.js:720:16)

...

Tests are running fine since mongodb-core rewrite


[AppDev] Project Map - Projects Classification Criteria

Review and finalize "Projects Classification Criteria" section of Project Map Document: https://github.com/cncf/tag-app-delivery/blob/wg-app-dev-map-review/app-development-map/v1alpha1/index.md#projects-classification-criteria

@salaboy @danieloh30 do you have any inputs on this part? Anything we should change/update?

LGTM! Plz go ahead!

Closing this for now as we wrapped up iteration 1. We are starting a second iteration on the deliverable, and we'll have a second look at each section for further improvements.


fix: add purchase mode flag

Offers a way to build images with the Cart functionality enabled
Description
Can be merged at any time, but won't be useful until #122 and #113 are merged
Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.
Checklist

[ ] Added steps to reproduce the changes in this pull request
[ ] Added relevant testing in this pull request
[ ] Please merge this PR for me once it is approved.

Due to the complexity of using configurations in the pull request they are introduced, and having tested these in isolation, I'm going to merge this, then if any other updates are required, introduce a new PR to fix.


Exception in Thread 1

Hello, I can not run the tests.
I setup the environment with cuda in conda (on linux), but running the tests from the repo always fails.
I tried different python versions: 3.9, 3.11 but none of them work.
The exception is always the ValueError: signal only works in main thread of the main interpreter
python realtimestt_test.py                                                                                 INT ✘  5s   realtimestt 
System initializing, please wait
Exception in thread Thread-3 (_audio_data_worker):
Traceback (most recent call last):
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/threading.py", line 1045, in _bootstrap_inner
Exception in thread Thread-2 (_transcription_worker):
Traceback (most recent call last):
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/threading.py", line 1045, in _bootstrap_inner
    self.run()
    self.run()
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/threading.py", line 982, in run
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/threading.py", line 982, in run
    self._target(*self._args, **self._kwargs)
    self._target(*self._args, **self._kwargs)
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/site-packages/RealtimeSTT/audio_recorder.py", line 897, in _audio_data_worker
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/site-packages/RealtimeSTT/audio_recorder.py", line 862, in _transcription_worker
    system_signal.signal(system_signal.SIGINT, system_signal.SIG_IGN)
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/signal.py", line 58, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: signal only works in main thread of the main interpreter
    worker.run()
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/site-packages/RealtimeSTT/audio_recorder.py", line 124, in run
    system_signal.signal(system_signal.SIGINT, system_signal.SIG_IGN)
  File "/home/marlon/.conda/envs/realtimestt/lib/python3.11/signal.py", line 58, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: signal only works in main thread of the main interpreter

Even this simple example fails:
from RealtimeSTT import AudioToTextRecorder

def process_text(text):
    print(text)

if __name__ == '__main__':
    recorder = AudioToTextRecorder()

    while True:
        recorder.text(process_text)

with the same error as above.

Please look here (check current version from repo, release coming soon)

It work, thank you!


[NSE-27]Reuse exchage to optimize DPP performance

Signed-off-by: Chendi Xue<EMAIL_ADDRESS>Fixed: https://github.com/oap-project/native-sql-engine/issues/27
verified with tpcds_v1_sf500_dpp and tpcds_v2_sf500

@zhouyuan , updated, now it will check if SQLConf.get.adaptiveExecutionEnabled is true in supportAdaptive function.

@zhouyuan , updated, now it will check if SQLConf.get.adaptiveExecutionEnabled is true in supportAdaptive function.


拉取修改后重启bot出现报错，发送指令无响应

使用git pull拉取更新后启动bot，出现错误，QQ群内发送指令无响应。
启动时的错误日志如下：

{"log":"(node:24) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'main' of undefined\n","stream":"stderr","time":"2021-08-13T13:01:01.192609385Z"}
{"log":"    at addPlugin (/bot/src/modules/plugin.ts:56:20)\n","stream":"stderr","time":"2021-08-13T13:01:01.192651468Z"}
{"log":"    at /bot/src/plugins/genshin/init.ts:153:18\n","stream":"stderr","time":"2021-08-13T13:01:01.192670732Z"}
{"log":"    at step (/bot/src/plugins/genshin/init.ts:44:23)\n","stream":"stderr","time":"2021-08-13T13:01:01.192674841Z"}
{"log":"    at Object.next (/bot/src/plugins/genshin/init.ts:25:53)\n","stream":"stderr","time":"2021-08-13T13:01:01.19267863Z"}
{"log":"    at fulfilled (/bot/src/plugins/genshin/init.ts:16:58)\n","stream":"stderr","time":"2021-08-13T13:01:01.192682532Z"}
{"log":"    at processTicksAndRejections (internal/process/task_queues.js:97:5)\n","stream":"stderr","time":"2021-08-13T13:01:01.192686293Z"}
{"log":"(node:24) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)\n","stream":"stderr","time":"2021-08-13T13:01:01.192690207Z"}
{"log":"(node:24) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.\n","stream":"stderr","time":"2021-08-13T13:01:01.192707968Z"}

无法复现，原因不明……不过 docker 启动pull 更新要更新镜像，把原镜像删了才行再构建才行，可以尝试重新拉取

我删掉原有的容器、镜像和git，重新拉取试一下吧


Problems with running Makefile in Windows

Hi Kuroni,
I am having trouble getting this to properly make on Windows 10. I am pretty new to C++ so bear with me here...
I am on the Master branch and have copied the Makefile.windows and renamed it just Makefile. I then opened Makefile in Notepad and edited the lines specifying SFML directory:
`
INCFLAGS := -I"C:\Users\Wuri\Downloads\SFML-2.5.1-windows-vc15-64-bit (1)\SFML-2.5.1/include" -Iinclude
LIBFLAGS := -L"C:\Users\Wuri\Downloads\SFML-2.5.1-windows-vc15-64-bit (1)\SFML-2.5.1/lib"
`
I have also tried the 32 bit version, and tried all forward slashes or all back slashes to no differences.
I installed MinGW for my Windows Command Prompt to be able to make:

But it seems to error out as shown above and creates the following two directories in the project folder obj and -p:

I saw that another user had some similar issue using the nmake -f Makefile command but resolved it when he had the above two lines with double quotes, which I have. So I decided to install Visual Studio. In the Developer CMD Prompt for VS 2019, I ran

At this point I am very not sure what else I need to change or if maybe I am not making properly? If you could offer any insight, that would be amazing! Thank you!
Here is the Makefile if it helps, it should only have the two lines above different from the source.

Hi Wuri,
could you try to rename all folders to your sfml directory to only include a-z?
As in C:\Users\Wuri\Downloads\SFML\SFML.
Spaces and some special characters are often problematic on windows and linux when they are in file or folder names.
You can also put the sfml folder in the same folder as bongocat-osu but instead of writing the full path C:\Users\Wuri\Documents\Github\bongocat-osu\SFML you just write SFML into the makefile.
I don't know the specific syntax for your make but you might want to try to look for a command line flag that always makes all targets. For my make that would be make -B or make --always-make. You can check by using make --help, make -h or make /?
If nothing works, you might want to try it again with a debug flag and attach the output as a file here. For my make that is make -d. You also might want to write it to a text file immediately with make --your-debug-flag-here > output.txt.
The Makefile.windows for some reason uses the linux syntax where -p signifies that mkdir should create sub directories if necessary. This is done by default on windows mkdir. Since windows mkdir does not have any command options it thinks you want to create the directory -p, wich it does. You should be able to remove the -p.
When you share blocks of code, text or similar in the future you might want to think about sharing it within a codeblock as it makes working with the text easier. You can find out more about codeblocks here.

Hi,
Can you try replacing the last lines in the Makefile with these lines?
create:
	mkdir $(OBJDIR) && exit 0
	mkdir bin && exit 0

test:
	bin/bongo.exe

clean:
	del $(OBJ) && exit 0
	del ico/ico.res && exit 0

The reason for your errors is because I tried to use Linux commands (i.e. mkdir) in the context of Linux, and it is not the same on Windows.


Fix PEP8

PEP8 in current master is broken.

Hurray !

Double hurray !

Do you guys can validate that BDD tests are run? I can't tell from the output.
Also it is supposed to display the coverage but it doesn't seems to be the case.

@Natim - running ./manage.py test ONLY runs the unit tests.
To run the BDD tests you need to do ./manage.py test BDD.
However, we currently have failing BDD tests - I am working on fixing this.
I have never had coverage working on the BDD folder - is it necessary? I thought coverage was mainly for unit testing??

I thought coverage was mainly for unit testing??
Yes it is not for bdd tests but I does not seems to be running on the unit tests yet either.

https://travis-ci.org/nlhkabu/connect/jobs/65851493#L242

OK - I think we should look into coveralls for this.  See #48


It looks like wingetbot date is wrong

It look like there is some date issue about @wingetbot.

The date supposed to be 23/11/23 which is past 3 days
https://github.com/microsoft/winget-pkgs/pull/128003/files
My time is in right corner to the taskbar which Windows tell the date

It seem the date format is YYYY-MM-DD


brew tests: suppress "Run options: exclude..." output

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example. No: brew tests is not itself tested.

Gets rid of that Run options: exclude {...} spam in the output of brew tests.
Before:
$ brew tests
Randomized with seed 26599
8 processes for 226 specs, ~ 28 specs per process
Run options: exclude {:needs_linux=>true}
.......Run options: exclude {:needs_linux=>true}
...Run options: exclude {:needs_linux=>true}
Run options: exclude {:needs_linux=>true}
......Run options: exclude {:needs_linux=>true}
.Run options: exclude {:needs_linux=>true}
Run options: exclude {:needs_linux=>true}
.Run options: exclude {:needs_linux=>true}
..................*...........................................................

After:
$ brew tests
Randomized with seed 24974
8 processes for 226 specs, ~ 28 specs per process
..........................................................................................................................................................................................................................................

Actually, this is supported by upstream:
https://github.com/rspec/rspec-core/blob/5e395e2016f1da19475e6db2817eb26dae828c4c/Filtering.md#silencing-filter-announcements

Do you know how to pass an Rspec.configure to the parallel_rspec we're using? I saw that, but didn't know how to make it happen inside how we use Rspec. I'm kind of an Rspec newb.

config.silence_filter_announcements = true in spec_helper.rb.

Oh my gosh; I missed it because I got the case wrong for RSpec in my greping.
New PR: #4298


chunmi.cooker.wy4 set cook-data

Where can I see an example of string cook-data, set-menu-data for the device chunmi.cooker.wy4 actions cooking-start and set-menu?
https://home.miot-spec.com/spec/chunmi.cooker.wy4

Maybe you can find a method in this file. If you discover anything, feel free to share!

chunmi.cooker.wy4.js

@al-one I am trying to figure out something similar for another product (the chunmi.ihcooker.tkcbeu).
How did you come by this .js file? Do you have the same kind of file for the product I am looking for?
Thx ^^

@jannwawerek

https://home.miot-spec.com/s/chunmi.cooker.wy4

Unzip  this  file
Add  a  .js  suffix  to  android/main.bundle


Adjust ranking of Irish community resources

An example, OSM Ireland has the following listed in the index

Website
Mailing list
Telegram
Facebook group
Twitter

These show up in ID in the following order

Twitter
Telegram
Facebook group
Mailing List
Website

Is there some way to allow a preferred ranking to be applied to the list so that it would show in whatever order the local community deems to be most effective e.g. for Ireland, in terms of most active to least active, the following order would apply

Telegram
Mailing List
Facebook group
Twitter
Website

Yes, there is an order field that allows communities to control the sort order.
The current values for the Ireland communities are:

Ireland Twitter - 5
Ireland Telegram - 4
Ireland Facebook - 3
Ireland Mailing List - 2
Ireland Local Chapter website - 1
Ireland IRC - -1

So we can just change the numbers and they will sort differently.
Also feel free to remove whatever resources you're not using.  If nobody is actively using IRC, it's better to just delete it than show it to people.

I ended up just changing them to match the requested order, since I still had the files open from before.

Telegram
Mailing List
Facebook group
Twitter
Website


[MS-519][FE] Change landing page for benchmarking

Description
Code changes covers:

Changing the state management in the benchmark multi step flow component to use reducer.  With all the necessary state calculations in the reducer function, it's easier to change behaviors, like e.g. having different steps for different entry point, etc.
2 of the 3 entry points into the Benchmarking flow uses a flow which has 1 step lesser

Motivation and Context
To show a more intuitive user flow to those who are new to LLM testing so that they understand what is being tested just from reading the description. 2 entry points into the benchmark flow has been updated to land directly on the cookbooks selection screen which has cookbook descriptions.
Type of Change

feat: A new feature

How to Test
Entry point 1

From homepage, click on the middle card (Evaluate against standard tests)
Verify user lands on Cookbooks selection screen
Test the whole benchmark flow
Test navigating back and forth using the next and previous arrow icons

Entry point 2

From left nav, click on Benchmarking and Start new run
Verify same items as above (entry point 1)

Entry point 3

From home page top banner - Click Get Started button.
Verify the flow to be status quo - user lands on topics selection screen
Test the whole benchmark flow
Test navigating back and forth using the next and previous arrow icons

Checklist
Please check all the boxes that apply to this pull request using "x":

[ x]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[ x]  I have added appropriate unit tests or functional tests for the changes made.
[ x]  I have followed the project's coding conventions and style guidelines.
[ x]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[x ]  I have added any necessary dependencies or packages to the project's build configuration.
[ x]  I have performed a self-review of my own code.
[ x]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

https://imda-dsl.atlassian.net/browse/MS-519


[zuul][tempest] Use a pre_deploy hook to create the COO subscription

rdo-check

recheck

I created this PR to independantly test some updates to
https://github.com/openstack-k8s-operators/telemetry-operator/pull/284
Now that it has passed, I'll close this PR and cherry-pick the commit onto efoley-zuul-tempest


Invisible after using with another account

Hi, so just to clear things up, this peace of software is awesome!
So the raspotify device can be discovered on any Device in my LAN, just like it should. If Account 1 plays Music, it disappears. Still fine. But if Account 1 disconnects from the raspotify by switching the playback device back to smartphone or what else, the raspotify keeps beeing visible only to devices logged in to account 1. Devices with other accounts cant see the raspotify, until the serice is beeing restarted.

This is a good question for the actual programmers : https://github.com/librespot-org/librespot