Is Snowflake still active?

I'm  not able to work actively on Snowflake.  If a PR is created, I would
merge, but that is about the  most I can do at this time.  If anyone wants
to take it over, I would like that.
On Jan 17, 2017 4:15 PM, "Ryan"<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bartonhammond/snowflake/issues/178, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABORPLD7ISS-lsVUmopHS8ETNOB0GRAxks5rTT2CgaJpZM4LmO0z
.

I'd love to but just started with RN, so need some time to get familiar with it.

Hi Kuba,
Let me know if I can help.  I've tried to document everything I've done -
it might not be exhaustive but it should help you.  Be sure to look at
http://bartonhammond.github.io/snowflake/snowflake.js.html for the code
documentation - as to the project it's all in the
https://github.com/bartonhammond/snowflake page.
You might want to think about upgrading the project to the newest release
of RN.  It's a little tedious sometimes 'cause the iOS and Android code
includes numerous add ons that need to stay but when doing the
'react-native upgrade' if you're not careful, they will be removed during
the upgrade.  The upgrade allows one to look at the diffs to help manage
this.  When I do an upgrade, I look at the diffs and use this "diff" option
and manually make the changes unless there's just too many.  If I allow the
upgrade to make the modifications, I have to have taken note what changes
were removed.  It is a good way to learn about RN as when the upgrade to
the native portions are complete, you still need to consider the impact of
upgrading w/ Jest.  It sometimes takes a lot of work to do this.  But if
you're going to learn RN, it's something you'll have to learn eventually.
Here's a couple of links that might help you make the process easier:
https://blog.chendry.org/2016/01/09/react-native-upgrade-checklist.html
https://hashnode.com/post/upgrading-react-native-in-an-existing-project-ciqg696ub0hceaj53wmweggap
https://github.com/tjunnone/npm-check-updates
Good luck!
Barton
On Sat, Jan 28, 2017 at 8:33 PM, Kuba Siemiątkowski <
<EMAIL_ADDRESS>wrote:

I'd love to but just started with RN, so need some time to get familiar
with it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bartonhammond/snowflake/issues/178#issuecomment-275889515,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABORPMvYOG4NTi7n-JH7vA-5bghErrbHks5rW_p0gaJpZM4LmO0z
.

I successfully updated my local project to latest RN ( I think it's 0.41.2) so I should have a PR soon.

That would be great!  I look forward to it..
On Feb 21, 2017 7:03 AM, "Kuba Siemiątkowski"<EMAIL_ADDRESS>wrote:

I successfully updated my local project to latest RN ( I think it's
0.41.2) so I should have a PR soon.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bartonhammond/snowflake/issues/178#issuecomment-281338615,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABORPMcVaNPQoYINVZFoRzUVIDorRi1Iks5reuCmgaJpZM4LmO0z
.

Many thanks, again, @siemiatj - I really appreciate your efforts.  Snowflake now has 25 contributors and I am thankful for everyone's contribution.  As long as there is interest in Snowflake and people want to contribute, I will stay involved and manage the PR merges.
Again, thanks!

@bartonhammond Send me an email sometime, I don't mind stepping in and helping clean this up for you given your situation. I've reached a pretty good place with my hamsters.js project and need something else to look at in my free time.


WARNING: Ignoring invalid distribution ~ip (C:\Python312\Lib\site-packages)

Hi Djdefrag,
I havent used this in a while, so i went to update. Having some issues w the requirements.
WARNING: Ignoring invalid distribution ~ip (C:\Python312\Lib\site-packages)

Can you elaborate on this issue? I was updating from 2.11.  Perhaps the issue is on my end since I haven't used python in a while.
Cheers.
Edit: it appears to be running through the program without any issues or warnings, so maybe this is a non issue.
Cheers,

Perfect my friend!


added safety measures to cleanup script.

Description
Add one more safety measure for rm command.
How Has This Been Tested?
No need to test.
Merge criteria:

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

/retest

/retest


Update active-directory-accessmanagement-groups-with-advanced-rules.md

Updated max size of rule 255 to 2048

Hi @RobdeJong, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (rodejo). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


[bug] Tutorials link in Readme can be missed

Please describe the bug
Maybe my search ability is poor today, but locating https://nokogiri.org/tutorials/modifying_an_html_xml_document.html took me an embarrassingly long time

Once I found tutorial I started to finally progress with my plan to write proper code to merge multiple SVG files into one.
Help us reproduce what you're seeing
Try to parse and edit SVG using ruby without memory how it can be done.
Expected behavior
Tutorials are existing and easy to find. Note that once I found tutorial my problems become solved, despite not finding solution for previous 40 minutes.
Environment
Not relevant
Additional context
Yes, now that I create this issue I see tutorials being mentioned in https://github.com/sparklemotion/nokogiri#reading Not entirely sure why I missed this particular mention, maybe I got distracted by Tidelift.
I propose
(1)
linking relevant tutorials in

reading, writing, modifying, and querying documents

in header of readme ( https://github.com/sparklemotion/nokogiri#nokogiri )
(2)
adding "good documentation and tutorials" in https://github.com/sparklemotion/nokogiri#features-overview with word tutorials linking to https://nokogiri.org/tutorials/toc.html

Hi! If you'd like to submit some suggestions in a PR I'd be happy to take a look. Thanks!

Hi! If you'd like to submit some suggestions in a PR I'd be happy to take a look. Thanks!

Done!


updating generated generator to use yeoman 1.0

Re-closes https://github.com/donejs/generator-donejs/issues/179.

Coverage remained the same at 97.473% when pulling 79282d6577ec5420e5de8378a98a443a16e2f31c on generator-generator-yeoman-1.0 into 6143a635f15489fda558ec1d3784c8f261a54da4 on major.

Coverage remained the same at 97.473% when pulling 79282d6577ec5420e5de8378a98a443a16e2f31c on generator-generator-yeoman-1.0 into 6143a635f15489fda558ec1d3784c8f261a54da4 on major.


Consul service not running in smebberson/alpine-consul-nodejs

Sorry to open an issue on this but I have been racking my brain and googling and can't figure out what I need to change to get the consul service working.
The documentation states: "This container has been setup to automatically connect to a Consul cluster, created with a service name of consul."
I'm trying to bring this up in a standalone vagrant vm:
docker run -d --name consul-test smebberson/alpine-consul-nodejs
...
Status: Downloaded newer image for smebberson/alpine-consul-nodejs:latest
b19f29cc949e2f65cefbb91509602d124bd5abcc3dcd0e03fb6a595cb461c287
docker ps
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS              PORTS                                                              NAMES
b19f29cc949e        smebberson/alpine-consul-nodejs   "/init"                  49 seconds ago      Up 48 seconds       53/tcp, 53/udp, 8300-8302/tcp, 8400/tcp, 8500/tcp, 8301-8302/udp   consul-test
docker exec -t -i b19f29cc949e sh
/ # dig @localhost google.com
google.com.		299	IN	A	<IP_ADDRESS>
/ # dig @localhost consul.service.consul
;consul.service.consul.		IN	A
The only log file with anything in it is /var/log/go-dnsmasq/go-dnsmasq.log
time="2017-01-16T22:08:14Z" level=info msg="Starting go-dnsmasq server 1.0.7"
time="2017-01-16T22:08:14Z" level=info msg="Nameservers: [<IP_ADDRESS>:53]"
time="2017-01-16T22:08:14Z" level=info msg="Setting host nameserver to <IP_ADDRESS>"
time="2017-01-16T22:08:14Z" level=info msg="Ready for queries on tcp://<IP_ADDRESS>:53"
time="2017-01-16T22:08:14Z" level=info msg="Ready for queries on udp://<IP_ADDRESS>:53"
time="2017-01-16T22:09:45Z" level=error msg="[64612] Error looking up literal qname 'consul.service.consul.' with upstreams: read udp <IP_ADDRESS>:39666-><IP_ADDRESS>:8600: read: connection refused"
time="2017-01-16T22:09:45Z" level=error msg="[65000] Error looking up literal qname 'consul.service.consul.' with upstreams: read udp <IP_ADDRESS>:44608-><IP_ADDRESS>:8600: read: connection refused"
The only thing that appears to be listening is DNS:
/ # netstat -ant |grep LISTEN
tcp        0      0 <IP_ADDRESS>:53            <IP_ADDRESS>:*               LISTEN
What i'm hoping to accomplish is that the container boots, connects to consul.service.ourdomain.consul (consul running on different servers) but every time I try to query that domain it tries to connect to the consul service that should be running locally.
Any advice would be appreciated since I'm not seeing anything in the logs.

I think that I just got a step closer as I now see consul mentioned in docker logs when I launch my container using:
docker run -d --name consul-test -e CONSUL_DOMAIN='ourdomain.consul' -e CONSUL_DC='loc' -e CONSUL_SERVER_NAME='consul.service.ourdomain.consul' smebberson/alpine-consul-nodejs

More headway, I added the following to the /etc/hosts file on my docker hosts: "<IP_ADDRESS>	consul.service.ourdomain.consul"
The container now connects to my consul server so this confirms my suspicion that it is a DNS issue.

I think that I know what the problem is.
Our consul servers are not running in Docker so the default name of "consul" won't work. We have a separate consul cluster for each environment tier so I'm trying to build the container with CONSUL_DOMAIN='ourdomain.consul' and CONSUL_SERVER_NAME='consul.service.ourdomain.consul'. consul.service.ourdomain.consul resolves properly on the docker host to the environment tier's respective consul servers.
The problem lies in this file https://github.com/smebberson/docker-alpine/blob/master/alpine-consul/root/etc/services.d/resolver/run#L7 which configures queries for CONSUL_DOMAIN to resolve to consul on the containers IP. This happens before the consul service has started and connected to the consul cluster thus causing the CONSUL_SERVER_NAME dns query to go to the consul service in the container....which isn't running yet.
Other than injecting an IP of the consul cluster nodes into the docker /etc/hosts file is there a way to tell go-dnsmasq to not send queries for consul.service.ourdomain.consul to the local consul service?

I'm experiencing the same issue when running in Google Container Engine with Kubernetes. Did you find a solution @claflico?

@claflico, sorry for not chiming in here previously.... Have you guys looked at --stubzones in go-dnsmasq?
That should allow you to configure a sub zone for which queries will be forwarded to another DNS server.
That should help with your problem right?

We went a different route. We are building our own containers now integrating consul-template and the run command gets the IP address of the container gateway (the host) and connects to the consul client running on the host via the gateway IP.
Feel free to close.


Fixes for add command

[ ] add an artifice test so we know it works against e.g. the dependency API
[ ] get gem version list directly from source using fetcher
[ ] either remove --source option or respect it when fetching the list of gem versions
[ ] handle gem names that aren't present on rubygems.org

@b-ggs any interest in doing this?

Wanna contribute .. Leads will be appreciated.TIA

@shuboid the task items @indirect has posted above should be a good outline of the work that needs to be done

Hi @indirect,
I'm working on an implementation of this feature and i have a couple of questions. In terms of the interface is the idea you have along the lines of bundler add pg '~> 1.5'?  I assume that we allow users to specify the version and maybe also specify optional groups as a flag like --group development as well. Thoughts?

@shuboid Could you let me know if you're working on this feature? If you're not, then I'd like to work on it.

Adding the RFC here:
https://github.com/hmistry/rfcs/blob/bundle-add/text/0000-bundle-add.md
I'm currently giving this a try. Let me know if someone else is already working on this.

I think this one can be closed.

Closed by https://github.com/bundler/bundler/pull/5486


Task tree view using --task-type ext-program option gives broken task tree

What version of Ctrl-Q are you using?
3.13.2
What version of Node.js are you using? Not applicable if you use the standalone version of Ctrl-Q.

What command did you use to start Ctrl-Q?
ctrl-q task-get --auth-type cert --host ... --auth-cert-file ./cert/client.pem --auth-cert-key-file ./cert/client_key.pem --auth-user-dir ... --auth-user-id ... --tree-icons --text-color yes --tree-details --task-type ext-program
What operating system are you using?
Linux
What CPU architecture are you using?
x86
What Qlik Sense versions are you using?
2023-May
Describe the Bug
The current way of working for the --task-type option does not make sense when showing task trees.
If only external program tasks are viewed, using --task-type ext-program, the result looks like this:

When using --task-type reload the result is:

In both cases the excluded task type is still included in the task tree.
This was supposed to be addressed by #319, but it seems it was not quite fixed then.
Expected Behavior
--task-type should not be allowed when creating task trees.
To Reproduce
No response

Version 3.14 was just released (download here), it contains (among other things) changes related to this ticket.


fix typo in Japanese message catalog

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

This PR corrects a minor typo in Japanese message catalog.
Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 87.755% when pulling b9e256adfad37fda2619b892af37ce4878d7b510 on node-red-hitachi:fix-typo-in-jp-message-catalog into 9066cedc297025f8c219d19f788a0708dc6bfb34 on node-red:master.

Coverage remained the same at 87.755% when pulling b9e256adfad37fda2619b892af37ce4878d7b510 on node-red-hitachi:fix-typo-in-jp-message-catalog into 9066cedc297025f8c219d19f788a0708dc6bfb34 on node-red:master.

Coverage remained the same at 87.755% when pulling b9e256adfad37fda2619b892af37ce4878d7b510 on node-red-hitachi:fix-typo-in-jp-message-catalog into 9066cedc297025f8c219d19f788a0708dc6bfb34 on node-red:master.


Linaaf/bedrock/guardrails

Added doc for amazon safeguards

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: katarzyna-koltun-mx:x: mx-awsdevteamYou have signed the CLA already but the status is still pending? Let us recheck it.


Incorrect number of charge phases

In charging details, all my charges at home (only placed I have charged since installing 6 weeks ago - due to Covid) show as:
230 Volts (correct)
16 Amps (correct)
2 phases (clearly wrong)
11 Kw (correct)
Do the math 230 * 16 * 2 = 7.360 w
It should be 230 * 16 * 3 = 11 Kw

I assume the API gives at least Volts, amps and wattage - not sure if it reports phases or this is calculated??

TeslaMate Version: all since 1.18

Duplicate of #605, #414


Plugin Configuration

Much like #138, it would also be nice to be able to spinkle plugin configuration.
I am thinking of creating a new plugin and it would be nice to have the ability to configure things specific to the plugin, rather than entirely in the component.
let Foo: { environment: string, url: string }[] = [
  { "environment": 'test', "url": "localhost:3000" },
  { "environment": 'stage', "url": "localhost:3001" },
];

Possibly under the createPlugin
EDIT:
Expanded idea: it would also be nice if I can added to SidebarItem from the config as well.

Completely agree that we need something here.
From a related discussion on discord:

... we might use something similar for configuring plugins, but it depends a bit on where we go with the plugin API. One idea is that a plugin would announce that they depend on a config object registered as for example "foo.bar", and the app would register a configuration for that name.

Just came across this when looking for a way of passing environment variables for different URLS to a plugin.
Would be happy to help out with this if there are any implementation ideas 🙂

This is the recommended solution for this atm.
Use process.env.NODE_ENV checks inside apis.ts if you want different config for dev/prod. We'll likely bring in an env API soon that makes that a bit simpler.
Then we'll likely continue exploring ways of supplying plugin config as we look closer at how to tie in backends.
Ideas are still very welcome though!

I believe the root of this issue has been resolved, and is described here:
https://backstage.io/docs/conf/defining
Plugins can define a config schema, validate against it, and allow users to configure settings via the app-config.yaml.
Would others agree?  Possibly good to close.

I believe the root of this issue has been resolved, and is described here:
https://backstage.io/docs/conf/defining
Plugins can define a config schema, validate against it, and allow users to configure settings via the app-config.yaml.
Would others agree?  Possibly good to close.

🧹 🧹 🧹 🧹

🧹 🧹 🧹 🧹


Clean Old API out of the repostiory

Would appreciate any eyes and hands on this to ensure nothing is removed that should not be.

@ironfroggy -Will deploy this branch to a public test instance on Friday (2/27/15) for the team to review.

@ironfroggy - Tried to build this and get import errors related to ga_resources
hydroshare_1    |   File "/home/docker/hydroshare/ga_resources/urls.py", line 2, in <module>
hydroshare_1    |     from ga_resources import api, views
hydroshare_1    | ImportError: cannot import name api

ga_resources makes use of tastypie, and is a repository that was forked from Jefferson Heard when he was implementing the project. There are other modules that import it, but I'm unsure of what we actually make use of in that app, and will consult with the rest of the team about it's use.

I have removed the pieces from here that used the removed API module, not hearing otherwise from your team. If anyone finds something that was needed, at this point it isn't worth keeping TastyPie for and can be recreated with the new API.


Target profile page rewrite: Update the page title

We used react-helmet on the genetics portal, which seemed to work well. The format should be:
<symbol> | Open Targets Platform

Closed in https://github.com/opentargets/platform-app/pull/20


Rendering issue in atom

Description

I just installed the latest version of atom. And this kind of weird rendering issue is showing up. I have tested this in safe mode and with --disable-gpu but still the issue persists.

I don't know exactly how often this issue is reproducible in other systems...

Versions

Using windows 10 home.

C:\>apm --version
apm  2.6.2
npm  6.14.13
node 12.14.1 x64
atom 1.58.0
python 3.8.5
git 2.29.2.windows.3
visual studio 2019

C:\>atom --version

Atom    : 1.58.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1

It has happened before but none of the discussions have been resolved so far
https://github.com/atom/atom/discussions/22402
https://github.com/atom/atom/discussions/22900
https://github.com/atom/atom/discussions/23144
https://github.com/atom/atom/discussions/23150

I have the same kind of issue in vscode, but its fixed by disabling hardware acceleration. But don't know what is wrong with atom...


ansible-review import issue

I encountered the following issue when running ansible-review:
$ ansible-review
/apps/tools/pip/lib/python2.6/site-packages/cryptography/__init__.py:26: DeprecationWarning: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of cryptography will drop support for Python 2.6
  DeprecationWarning
Traceback (most recent call last):
  File "/apps/tools/pip/bin/ansible-review", line 8, in <module>
    from ansiblereview.version import __version__
  File "/apps/tools/pip/lib/python2.6/site-packages/ansiblereview/__init__.py", line 6, in <module>
    import utils
  File "/apps/tools/pip/lib/python2.6/site-packages/ansiblereview/utils/__init__.py", line 12, in <module>
    import importlib
ImportError: No module named importlib

As you can guess this is on python2.6.6.
It seems that installing ansible-review via pip doesn't install importlib. Should this dependency exist?
Installing import lib via pip seems to have resolved the issue.

hint: should be a simple PR to fix this
would be good to have a tox test that checks this too.

Fixed by #13

I am having major problems getting ansible-review to pass tests with python-2.6
Are you unable to run ansible-review on a RHEL7 host or similar?
I don't really plan to support python-2.6, although MRs that pass all existing tests are welcomed. My attempts so far are on the travis_fix branch. I'll probably role master back to including the importlib but not including the 2.6 tox tests so that travis actually passes.

Not yet. Will try with software collections. Don't worry about the 2.6
support.
On 13 Oct 2016 12:14 pm, "Will Thames"<EMAIL_ADDRESS>wrote:

I am having major problems getting ansible-review to pass tests with
python-2.6
Are you unable to run ansible-review on a RHEL7 host or similar?
I don't really plan to support python-2.6, although MRs that pass all
existing tests are welcomed. My attempts so far are on the travis_fix
branch. I'll probably role master back to including the importlib but not
including the 2.6 tox tests so that travis actually passes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/willthames/ansible-review/issues/11#issuecomment-253393900,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJcwL8zF1eDePYkAgkQJNzIbNJ2nUcaIks5qzZQBgaJpZM4KTQxw
.


SSL Handshake failed in 7.1.0 on Ubuntu 18.04 with OpenSSL 1.1.1

After upgrading from PowerShell 7.0.3 to 7.1.0 on a fully patched Ubuntu 18.04 server with OpenSSL 1.1.1, web cmdlets (Invoke-RestMethod and Invoke-WebRequest) throw a Authentication failed, see inner exception. when connecting to our Infoblox API (which is running the latest available version of its NIOS OS, 8.5.1). Expanding the inner exception reveals the underlying problem is an SSL handshake failure. Downgrading PowerShell back to 7.0.3 fixes the problem.
NOTE: Requests to other internal TLS sites using PS 7.1.0 work just fine. This only seems to be a problem specifically with Infoblox (that I've found so far).
Steps to reproduce
# a simple call to the grid master's documentation endpoint which requires no authentication
Invoke-RestMethod https://gridmaster.test/wapidoc/

Expected behavior
The web request succeeds return normal responses.
Actual behavior
Invoke-RestMethod: Authentication failed, see inner exception.

Serializing the exception using $Error[0].Exception.ToString() produces the following output:
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception.
 ---> Interop+OpenSsl+SslException: SSL Handshake failed with OpenSSL error - SSL_ERROR_SSL.
 ---> Interop+Crypto+OpenSslCryptographicException: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
   --- End of inner exception stack trace ---
   at Interop.OpenSsl.DoSslHandshake(SafeSslHandle context, ReadOnlySpan`1 input, Byte[]& sendBuf, Int32& sendCount)
   at System.Net.Security.SslStreamPal.HandshakeInternal(SafeFreeCredentials credential, SafeDeleteSslContext& context, ReadOnlySpan`1 inputBuffer, Byte[]& outputBuffer, SslAuthenticationOptions sslAuthenticationOptions)
   --- End of inner exception stack trace ---
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(HttpClient client, HttpRequestMessage request, Boolean keepAuthorization) in /PowerShell/src/Microsoft.PowerShell.Commands.Utility/commands/utility/WebCmdlet/Common/WebRequestPSCmdlet.Common.cs:line 1361
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord() in /PowerShell/src/Microsoft.PowerShell.Commands.Utility/commands/utility/WebCmdlet/Common/WebRequestPSCmdlet.Common.cs:line 1518

Environment data
$PSVersionTable ouput
Name                           Value
----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Linux 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

apt-cache policy openssl output
openssl:
  Installed: 1.1.1-1ubuntu2.1~18.04.6
  Candidate: 1.1.1-1ubuntu2.1~18.04.6
  Version table:
 *** 1.1.1-1ubuntu2.1~18.04.6 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1.1.0g-2ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Unfortunately, Infoblox doesn't allow root access to the appliance's operating system or webserver to give exact versions on things there. But the managed CLI does allow some ability to tweak TLS protocol versions and ciphers. These are the current values. TLSv1.3 is not an option and the ciphers in the list are all that is available.
> show ssl_tls_protocols
TLSv1.2
> show ssl_tls_ciphers
  1. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 enabled
  2. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 enabled
  3. TLS_DHE_RSA_WITH_AES_128_CBC_SHA    enabled
  4. TLS_DHE_RSA_WITH_AES_256_CBC_SHA    enabled
  5. TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 enabled
  6. TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 enabled
  7. TLS_RSA_WITH_AES_128_GCM_SHA256     enabled
  8. TLS_RSA_WITH_AES_128_CBC_SHA        enabled
  9. TLS_RSA_WITH_AES_128_CBC_SHA256     enabled
 10. TLS_RSA_WITH_3DES_EDE_CBC_SHA       enabled
 11. TLS_RSA_WITH_AES_256_GCM_SHA384     enabled
 12. TLS_RSA_WITH_AES_256_CBC_SHA        enabled
 13. TLS_RSA_WITH_AES_256_CBC_SHA256     enabled
     TLS_DHE_DSS_WITH_AES_256_CBC_SHA    disabled
     TLS_DH_RSA_WITH_3DES_EDE_CBC_SHA    disabled
     TLS_DH_DSS_WITH_3DES_EDE_CBC_SHA    disabled
     TLS_DHE_DSS_WITH_AES_128_CBC_SHA    disabled
     TLS_RSA_WITH_RC4_128_SHA            disabled
     TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 disabled
     TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 disabled
     TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 disabled
     TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 disabled

@rmbolger Thanks for your investigations!
PowerShell does directly nothing with SSL - it utilize .Net. HttpClient class. Please open issue in .Net Runtime repository. (If you could make simple C# demo app it helped them.)
Notice, PowerShell 7.0 is on .Net 3.1, PowerShell 7.1 is on .Net 5.0.

Just to follow up here so answers are easier to find. Here's are the details on what is needed to fix the issue.
The crux of the issue deals with a change in the default behavior for TLS in .NET 5.0 that is described in this doc.
https://docs.microsoft.com/en-us/dotnet/core/compatibility/cryptography/5.0/default-cipher-suites-for-tls-on-linux
In summary, .NET 5.0 will respect CipherString settings (among others) in the OS's /etc/ssl/openssl.cnf file. But if the settings aren't specified (which is the default in Ubuntu 18.04), .NET 5.0 defaults to a very restrictive/secure/modern default set of ciphers whereas .NET 3.1 defaults to a very loose/compatible set of ciphers. So if you are connecting to services that aren't capable of modern ciphers, you need to configure the OS's config to allow one or more of the ciphers your service does support. The other option is a code level change in your app that deals with CipherSuitePolicy and SslStream objects. But since my issue is with PowerShell, I don't have control of the code. So my only option is the OS config change.
In my particular case, I decided to use the Mozilla SSL Configuration Generator on the "Intermediate" configuration setting as a guide for what ciphers to allow while remaining compatible, but still as secure as possible. And I added the following to my /etc/ssl/openssl.cnf file right before the [ new_oids ] section.
openssl_conf = default_conf

[default_conf]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
CipherString = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384

The last two in the list match ciphers that are available from the Infoblox appliance. When re-testing both my .NET sample app and PowerShell's web cmdlets, neither throw an error anymore.


Degree of Variation Experiment

Hello Author，I am curious about two component features after Fourier Filter, can you tell me the details or show me the code  how you did the visualization study on features and how can I calculate Degree of Variation

Hello, you can calculate Degree of Variation as follows:

decompose the series into time-invariant component and time-variant component;
utilize the two components to train MLPs;
calculate the standard deviation of linear weighting.


Support new version of uwsgi metrics serialized format

In order to properly support dimensionalized uwsgi metrics we need to be able to differentiate between metrics with the same name but different dimension sets. With the current dropwizard format, where metric objects are indexed by name inside the type dictionary, this isn't possible without somehow mutating the name to reflect the dimension set (i.e. perhaps appending the dim key hash etc). However the simplest solution is to have each type key (i.e. "counters", "gauges") simply map to a list of metric objects, thus not requiring uniqueness of name. Conceptual this fits better as well I think.
The PR includes updated tests, and is backwards compatible to existing behavior. I do think it's a bit clunky (with the extra extraction function) and could benefit from a little generic function love (i.e. the parser.parseMapOfMap could be replaced with a generic function pointer with the correct type and then we could simply reassign based on the format and use the same function without the extra extraction function. But that would require touching the BaseParser code and be a little bit more far reaching, so perhaps the next PR will be refactoring that.

lg2m

@zachm GSI paged me about this change recently, shall we push for getting this merged? I think this PR is the only thing blocking the dimensionalized uwsgi_metrics.


Cannot reproduce the results.

I download the reproduction data reproduction_data.zip through Google Drive, and directly use the model_predictions_converted folder in reproduction_data.zip to do the evaluation. However, I can't reproduce the results in the official report.
I follows the given scripts with evaluate_times=4, but my reproduction results are always much lower than the official.
Pass Rate:

Method
Evaluation
I1-Inst.
I1-Tool.
I1-Cat.
I2-Inst.
I2-Cat.
I3-Inst.
Average

ChatGPT-ReACT
official
41.5
44
44.5
42.5
46.5
22
40.2

ChatGPT-ReACT
my reproduction (1)
36
41
42
36
41.5
22
36.4

ChatGPT-ReACT
my reproduction (2)
35.5
40
38
36
40.5
23
35.5

ChatGPT-DFSDT
official
54.5
65
60.5
75
71.5
62
64.8

ChatGPT-DFSDT
my reproduction
55
58.5
54
73
65.5
59
60.8

Win Rate:

Method
Evaluation
I1-Inst.
I1-Tool
I1-Cate.
I2-Inst.
I2-Cate.
I3-Inst.
Average

ChatGPT-DFSDT
official
60.5
62
57.3
72
64.8
69
64.3

ChatGPT-DFSDT
my reproduction
54
59
48
65.5
59.5
67
58.8

What are the possible reasons?

Hi, thank you for your question. We've updated the tooleval code by replacing some outdated parts which should have been replaced at first. Kindly attempt to reproduce our results using the most recent code. We apologize for any inconvenience this may have caused.

I am using the model_predictions_converted folder in reproduction_data.zip from Google Drive to do the evaluation, without using the convert script. So it should not be affected by this bug?
I also try to pull the updated code, run the run_convert_answer.sh script and the evaluation scripts, but still get a low result similar with the result reported above.

following


Issue 46

added scripts to deploy to gh pages.
decided against integrating into CI. Prefer to deploy manually when required

fixes #46


Declaring the revision process over

After finalising ideas prompted by @zag's suggestions, which included a more generic placement block, display texts for codes that can fail, and a new Formula block, it seems to me that the specification process for the language has come to a natural end.
The issue of signaling where customisations are to be found remains open, but can be considered an implementation detail at this time - IMHO.
Unless a significant new change is identified, I suggest the specification here can be moved to the Raku Steering Council for adoption.
@thoughtstream @Raku/docteam @Raku/core Any objections?

There remains the issue of @zag's :checkbox proposal,
which I'll address in the separate thread.
I don't think we should pursue the more extensive "selector"  mechanism
that @zag also proposed, as it seems to be tied closely to his Podlite design,
which has some fundamental differences from our RakuDoc approach.
As for @zag's W<URI> proposal, I'm still not sure I entirely understand it,
but it does already seem to be covered by: N<P<URI>>
So, apart from :checkbox, yes I agree that our redesign process has reached a natural conclusion
and (assuming we can quickly address the above issue) should be moved to the RSC for approval.

process completed. normal revision.


Fix the link_args variable inside the caf script.

This commit introduces a fix to src/mpi/CMakeLists.txt which contains
a rule that creates the link_args shell variable that is used inside
the caf script. Before the fix, the caf script contains a line:
link_args=-fcoarray=lib -lcaf_mpi
which produces an error when running caf:
$ caf -w
/opt/opencoarrays/gcc-5.1.1/mpich-3.1.4/bin/caf: line 37: -lcaf_mpi: command not found
caf wraps CAFC=mpif90
link_args needs to be enclosed in double quotes:
link_args="-fcoarray=lib -lcaf_mpi"
so that caf can work as expected.
Signed-off-by: milancurcic<EMAIL_ADDRESS>

Resolved by commit https://github.com/sourceryinstitute/opencoarrays/commit/ef5b51103c19446e6a1b23a7aa1acf8496ddd6c7.


.env variables are being expanded when I don't want them to be

Version
3.5.0
Environment info
Sorry... I don't run vue globally.  It's just part of my project.  So not sure how to get this.

Steps to reproduce
I have some urls inside my .env file like this
VUE_APP_GEOCODE_URL=https://maps.googleapis.com/maps/api/geocode/json?address=${address}&components=country:${country}&key=${key}
I use to be able to access this in my javascript as
process.env.VUE_APP_GEOCODE_URL and do parameter substitution with es6-dynamic-template (https://www.npmjs.com/package/es6-dynamic-template)
However, the latest version of vue-cli seems to have changed this, and is expanding the url for me (with non-existent variables).  I noticed this commit https://github.com/vuejs/vue-cli/pull/3534 that is using https://github.com/motdotla/dotenv-expand.  I suspect this is causing my issues.  How do we prevent it from processing our variables or how can I escape it so I control the substitution?
What is expected?
Previous versions did not expand the environment variables.
What is actually happening?
My environment variables are being expanded.  I use to do the substitution myself at runtime.

Ok... I should have tried this first...
VUE_APP_GEOCODE_URL=https://maps.googleapis.com/maps/api/geocode/json?address=${address}&components=country:${country}&key=${key}
Seems to work.  Hopefully this helps someone else.

Thanks for your feedback and glad to see that you found a workaround.
But we are unlikely to revert this feature.
Technically, every bug fix/ new feature can be a breaking change for someone relying on the buggy implementation. In this case, we see the auto-expand behavior as the more intuitive one, since every *nix system and most other similar utilities (e.g. create-react-app) expand environment variables by default.


[Issue] Prevent writing LAST_ACTION to localStorage unless predicate is true.

On the codebase that I am working on, we are dealing with very large state objects that exceed the amount allowed by localStorage. We had to override actionStorageMiddleware with our own version that prevented localStorage.setItem('LAST_ACTION', .. from happening unless action.type was allowed. So my question is, does every action have to be stored even if you're only allowing a few of them? Let me know if this tweak falls within the purpose of redux-state-sync and we can continue this conversation.

I think it's not necessary to store those actions which are not allowed. Do you want to send a pull request with the tweak that you did?

We have some syntactic sugar(wrapper) around the framework, so we made the change in our codebase. We overwrote the middleware portion of your framework. From what I'm seeing, it may require a few changes to the API, I could be mistaken though. Could you checkout my code snippet below and fiddle around with some ideas on how you would like to accomplish this?
// TabSyncMiddleware.js
import { createStorageListener, withReduxStateSync } from 'redux-state-sync';
import ActionWhiteList from './ActionWhiteList'; // actions we want to sync across tabs

function s4() {
  return Math.floor((1 + Math.random()) * 0x10000).toString(16).substring(1);
}

function guid() {
  return `${s4()}-${s4()}-${s4()}-${s4()}-${s4()}-${s4()}-${s4()}-${s4()}`;
}

export const reducerTabSync = withReduxStateSync;

export const tabSyncMiddleware = ({ getState }) => (next) => (action) => {
  if (action && !action.$uuid) {
    const stampedAction = {
      $uuid: guid(),
      ...action
    };

    try {
      if (action.type === '&_SEND_INIT_STATE') {
        if (getState()) {
          stampedAction.payload = getState();
          localStorage.setItem('LAST_ACTION', JSON.stringify(stampedAction));
        }
        return next(action);
      }

      if (ActionWhiteList.includes(action.type)) { // here's the part we needed
        localStorage.setItem('LAST_ACTION', JSON.stringify(stampedAction));
      }
    } catch (e) {
      console.error('Failed to store `LAST_ACTION` to localStorage.');
    }
  }
  return next(action);
};

export const TabSyncWrapper = (store) => {
  createStorageListener(store, {
    initiateWithState: true,
    predicate: (actionType) => {
      return ActionWhiteList.includes(actionType);
    }
  });

  return store;
};

Usage
//  index.js
import { tabSyncMiddleware, TabSyncWrapper, reducerTabSync } from './middleware/TabSyncMiddleware';

// ...

const enhancer = composeEnhancers(
  applyMiddleware( ..., ..., tabSyncMiddleware)
);

const store = TabSyncWrapper(createStore(
  reducerTabSync(reducers),
  enhancer
));

// ...

render(
  <Provider store={store}>
    <AppRouter />
  </Provider>,
  document.getElementById('root')
);

Sorry for the long delay, I just released redux-state-sync 2.0, Your problem should be fixed in the new version.


Generic scroll event service

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
To have a service that handles the adding of scroll eventlisteners.
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Due to the html/css layout scrolling does not occur on the body so eg. the mobile browser feature of when scrolling the menu/adressbar gets a minimalistic UI or disappears does not work.
Also this could be a great performance improvement in many apps as attaching listeners to scroll in multiple components/services is common and quite costly in terms of performance.
Perhaps this could be done within the CDK?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

It's not very well documented, but the ScrollDispatcher service does this already: https://github.com/angular/material2/blob/master/src/cdk/scrolling/scroll-dispatcher.ts

Yep, it's part of the cdk that we don't have full docs for yet


Unregistered definition type ‘defalias’

I am trying to advise the ielm function and I am getting the following fatal error.
Unregistered definition type ‘defalias’. Here is my code
(el-patch-defun ielm ()
      "Interactively evaluate Emacs Lisp expressions.
  Switches to the buffer `*ielm*', or creates it if it does not exist.
  See `inferior-emacs-lisp-mode' for details."
      (interactive)
      (let (old-point)
        (unless (comint-check-proc "*ielm*")
          (with-current-buffer (get-buffer-create "*ielm*")
            (unless (zerop (buffer-size)) (setq old-point (point)))
            (inferior-emacs-lisp-mode)))
        (el-patch-swap (pop-to-buffer-same-window "*ielm*")
                       (progn (split-window)
                              (pop-to-buffer "*ielm*")))
        (when old-point (push-mark old-point))))

Here is the stack trace
Debugger entered--Lisp error: (error "Unregistered definition type ‘defalias’")
  signal(error ("Unregistered definition type ‘defalias’"))
  error("Unregistered definition type `%S'" defalias)
  #f(compiled-function (definition &optional docstring-note) "Evaluate DEFINITION without updating `load-history'.\nDEFINITION should be an unquoted list beginning with `defun',\n`defmacro', `define-minor-mode', etc. DOCSTRING-NOTE, if given,\nis a sentence to put in brackets at the end of the docstring." #<bytecode 0xbe7bd1>)((defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point))))))) "This function was patched by `el-patch'.")
  (el-patch--stealthy-eval (defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point))))))) "This function was patched by `el-patch'.")
  (progn (puthash 'defalias '(defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point))))))) (or (gethash ''ielm el-patch--patches) (puthash ''ielm (make-hash-table :test (function equal)) el-patch--patches))) (el-patch--stealthy-eval (defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point))))))) "This function was patched by `el-patch'."))
  (el-patch--definition (defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point))))))))
  (closure (bootstrap-version t) nil (el-patch--definition (defalias 'ielm (function (lambda nil "Interactively evaluate Emacs Lisp expressions.\nSwitches to the buffer `*ielm*', or creates it if it does not exist.\nSee `inferior-emacs-lisp-mode' for details." (interactive) (let (old-point) (if (comint-check-proc "*ielm*") nil (save-current-buffer (set-buffer (get-buffer-create "*ielm*")) (if (= 0 (buffer-size)) nil (setq old-point (point))) (inferior-emacs-lisp-mode))) (error "Can't use `el-patch-swap' outside of an `el-patch'") (if old-point (progn (push-mark old-point)))))))))()
  eval-after-load-helper("/usr/intel/pkgs/emacs/26.1/share/emacs/26.1/lisp/ielm.elc")
  run-hook-with-args(eval-after-load-helper "/usr/intel/pkgs/emacs/26.1/share/emacs/26.1/lisp/ielm.elc")
  do-after-load-evaluation("/usr/intel/pkgs/emacs/26.1/share/emacs/26.1/lisp/ielm.elc")
  autoload-do-load((autoload "ielm" 1234208 t nil) ielm)
  command-execute(ielm)

This works if I evaluate it in *scratch*, and also appears to expand to different code than appears in your stack trace if I byte-compile it.
Are you perhaps byte-compiling your code without having el-patch loaded at byte-compilation time?

looks like you are correct. I can eval in the scratch buffer and it works. I missed your clear instructions about this in the README :worried:


Algo medium 1

Solved issue #304
In Language - C++
updated README file and have proper comments in the code

Please place problems under Algorithms/Bit Manipulation/. Create the folder.

changes done please have a look


Hide App Entries

It shows a lot of my none VR Steam apps in the list, so it would be good to manually hide apps from the list (removing would add it again on the next scan).

Just use the filtering bar at the top to either hide non-open-vr detected games(button labeled Open VR) or filter by search text.


Rename bundling to batching

Note: tests will not pass until GAX 0.5.0 is released

Coverage increased (+0.004%) to 81.486% when pulling e4c5b332dd9cf26d811728496719ebf0d3276e19 on michaelbausor:bundling-batching into e9c05a5a9aed5103076e2e2d6d24f59f48a90ef3 on GoogleCloudPlatform:master.

@pongad 0.5.0 released and Travis passed, PTAL

LGTM


DRILL-6467: Percentage usage of memory is reported as zero by the WebUI

The memory reported as a percentage is incorrectly reported as 0%, irrespective of the actual usage.

This is because of a snippet in the Javascript that computes the percentage:
      //Compute Usage
      function computeMemUsage(used, max) {
        let percent = 0;
        if ( max > 0) {
          let percent = Math.round((100 * used / max), 2);
        }
        let usage   =  bytesInGB(used, 2) + "GB (" + Math.max(0, percent) + "% of "+ bytesInGB(max, 2) +"GB)";
        return usage;
      }

Turns out, the let keyword creates a new percent variable within the scope of the if (max > 0) { .. } block, so the original variable never got updated. The fix was to simply remove the let preceding the percentage computation.

Verified with screenshot

+1 LGTM


Testing when using the 'cache' middleware is difficult due to missing execution context

When utilizing the cache middleware it assumes that the context and caches will be present.
https://github.com/honojs/hono/blob/main/src/middleware/cache/index.ts#L18
It might be helpful if this was a no-op when used in environments that don't have access to the cache API? Otherwise, it becomes difficult to run any unit tests against the API without a workaround.
The discussion here provides a helpful utility method. If cache can't be a no-op in test environments, then perhaps this utility could be fleshed out to provide a testing helper that Hono would provide to handle this situation in a more official way.
https://github.com/honojs/hono/issues/678#issuecomment-1364578058
I extended it a little bit so I could extract it and use it across the test suite by passing in the Hono app object.
/**
 * A helper function to easily make GET requests against
 * the hono router with a dummy ExecutionContext. This is needed
 * because the 'cache' middleware requires an ExecutionContext
 * to be present, which is not present in the unit tests. This
 * function will create a dummy ExecutionContext and pass it to
 * the app.fetch() function. Use this for GET requests instead of
 * 'await app.request('http://localhost/')' in unit tests.
 * @param app The hono app
 * @param url The URL to fetch
 * @param environment The environment to pass to the app
 * @param mockContext The mock context to pass to the app
 * @returns The response
 * @see: https://github.com/honojs/hono/issues/678#issuecomment-1364578058
 * */
export function get(
  app: Hono<{ Bindings: Bindings }>,
  url: string | URL,
  environment?: any,
  mockContext?: ExecutionContext,
) {
  const request = new Request(url)
  mockContext ??= {
    passThroughOnException: () => {},
    waitUntil: () => {},
  }
  return app.fetch(request, environment, mockContext)
}

Thanks for guidance on a better way to handle this if there is one.

Hi @grempe !
Very good point of view, good suggestion!
The app.request is a helper to make testing easier, I think we can add the feature you suggest:
https://github.com/honojs/hono/blob/64956cb57ded4f8b7833afd9a9059e6dac3bfaac/src/hono.ts#L287-L299
It has not been a PR yet, but this might be a good way that we write it like below:
  request = async (
    input: Request | string | URL,
    requestInit?: RequestInit,
    env?: {},
    executionCxt?: ExecutionContext
  ) => {
    executionCxt ??= {
      passThroughOnException: () => {},
      waitUntil: () => {},
    }
    if (input instanceof Request) {
      if (requestInit !== undefined) {
        input = new Request(input, requestInit)
      }
      return await this.fetch(input, env, executionCxt)
    }
    input = input.toString()
    const path = /^https?:\/\//.test(input) ? input : `http://localhost${mergePath('/', input)}`
    const req = new Request(path, requestInit)
    return await this.fetch(req, env, executionCxt)
  }
}

Hi @bdsoha
While it refactored but, you can still you these methods:
const app = new Hono()
const res = await app.request('/')

// Or

const app = new Hono()
const req = new Request('/')
const res = await app.fetch(req, { key:'val', executionContext })

@yusukebe Thanks for the quick response.
I was reffering to something a little bit more involved.
How would you go about testing the routes below (the BEARER_TOKEN is not mockable):
const app = new Hono()

app.use('*', bearerAuth({ token: env('BEARER_TOKEN') }))

You should use the following approach:
app.use('*', (ctx, next) => {
    return bearerAuth({ token: ctx.env.BEARER_TOKEN })(ctx, next);
});

Currently, this is the only method to handle values like ctx.env.xxx in middlewares such as bearerAuth and basicAuth.

We can close this issue. Thanks.


Feat:Apply kubernetes to your app

Describe the feature
As your app is dockerize then it is best to do kubernetes in your app which make your app also good in devops field some benefits of kubernetes are mention below -
Benefits of kubernetes:

It helps in deploying your app locally and on internet
It helps in load balancing the many user
it helps in auto healing the damaged pods
Also it helps in changing the code when your app is live

Add ScreenShots
no screenshot needed
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

@hereisSwapnil please assign me this issue i want to work on this issue


Player Controls on IMA ad Player

Hi,
Is there a way to implement standard player controls (play/pause, mute/unmute, elapsed time) on the adPlayer?
Is it a setting in your project or an ima setting?
Or do we have to roll our own?
If the answer is roll our own, I'm happy to contribute it back to the open source project.
Thanks!

Hi @bcorvino. The short answer is: roll your own :)
We intentionally wanted to keep this library as low-level and as small as possible because we think that building a video-player user interface highly depends on individual needs and you often need to connect the UI to other parts of your environment (error handling, custom advertisment, custom animations/transitions, end-cards, ...) in order to fully control every part of the UI/UX.
At glomex we implemented a separate UI as overlay above the video-tag / IMA ad layer completely outside this library because we had to fulfill custom needs. If you want you can create a separate project that uses vast-ima-player as dependency but we don't want to maintain a separate UI stack.
To completely hide the Google IMA overlays you can do the following:
const adsRenderingSettings = new ima.AdsRenderingSettings();
adsRenderingSettings.uiElements = [];
const playerOptions = new PlayerOptions();
playerOptions.clickTrackingElement = adElementToRenderImaOverlayIn;

const player = new Player(
  ima, yourVideoElement, adElementToRenderImaOverlayIn,
  adsRenderingSettings, playerOptions
);

In case you want a more full fledged player with IMA integration I would suggest to have a look at https://github.com/openplayerjs/openplayerjs.

Hi,
Thanks for your reply. I'll look into rolling my own and I understand the reasoning.  I have previously implemented openplayerjs and have contributed to their ima integration, but I'm looking for something with a smaller footprint at this point, which is why your IMA library is so useful for us.

Glad I was able to help.


Bug: using a resolved Layout inside a strongly typed TemplateBase throws an ArgumentException

I have two razor views: Content.cshtml & Layout.cshtml.
I configured the TemplateService with a resolver that resolves the _Layout (which is set to "Layout.cshtml").
When I parse Content.cshtml while having the TemplateService configured to use a strongly typed TemplateBase<>, an exception is thrown from the CompilerServiceBase class in the method BuildTypeName:
"The template type is a generic defintion, and no model type has been supplied.".
The model type has indeed not been specified, since the Resolve method was called from the Resolver delegate without passing a model:
new DelegateTemplateResolver(x => _templateProvider.LoadTemplate(x)).
In summary: parsing a view (using a strongly typed TemplateBase) that has its _Layout property set to another view causes an ArgumentExeption: "The template type is a generic defintion, and no model type has been supplied.".

I've added a new method to TemplateBase called ResolveLayout, this grabs the layout template.When we override this in TemplateBase<T>, we pass in the model type that we are resolving. This allows the model to be passed from the child template to the layout template.

I'll likely push this next version to Nuget as v3.0.3beta


Update functions-overview.md

Changed the link to serverless landing page to the latest one

@intrepidsoldier : Thanks for your contribution! The author, @mattchenderson, has been notified to review your proposed change.

@intrepidsoldier good catch! Thanks for the PR!
#sign-off


Confusing error if your password is incorrect

This tool is awesome, but it took me a long time to figure out I was entering the wrong password.
If you enter a wrong password you get:
$ aws-azure-login
? Username<EMAIL_ADDRESS>? Password: **************
We don't recognize this user ID or password

If you enter a previously-used but no longer valid password:
$ aws-azure-login
? Username<EMAIL_ADDRESS>? Password: **************
Did you change your password recently?

I had no idea in the latter case that the program had failed. aws s3 ls would just say Unable to locate credentials. You can configure credentials by running "aws configure".
It would be super helpful if the program would say explicitly "Authentication failed" as well as exit with a non-zero exit code.
Thanks!

Sure. Easy enough. The app was simply returning the error message exactly as it was in Azure. I just published v0.3.1 that prefixes those errors with "Login failed" to make it clear. I also added a non-zero exit code.

Thank you! :D


Add Google Compute Platform Packer template

This commit adds a first basic version of a GCP Packer template to
deploy cOS or cOS derivatives systems into Google Cloud Platform
using a cOS Vanilla image as the bootstrap platform.
Fixes #380
Signed-off-by: David Cassany<EMAIL_ADDRESS>

maybe we could also add a small subsection on the docs on how to run the template with packer?

maybe we could also add a small subsection on the docs on how to run the template with packer?

Yes we can do that, I was about to start adding a small article about it. However the problem here is that the images are not public, so the instructions will require manually committing the vanilla image to your project first.


about vue pages directory structure

https://swdevlab.com/147

Application Structure LIFT Principle ( from angular)  https://angular.io/guide/styleguide#lift
Locate code quickly,
Identify the code at a glance,
keep the Flattest structure you can,
and Try to be DRY.
Folders-by-feature structure

components :  contains Vue.js components used on different pages or parts of your application. You can import these components from pages, layouts, and other components.
views or pages : contains Vue.js components that it registers as routes.
public : contains files that likely won't change, such as favicon, robots.txt, sitemap, or company logos.

template icon images..

use directory
A) flat : keep the folder hierarchy as flat as possible , redundancy of keywords in filenames/directory
B) group by domain : separate module(==domain)  in case of considering microfrontend
tests/unit tests/e2e or component와 같은 위치
links
https://dev.to/vcpablo/vuejs-one-more-way-of-structuring-your-project-13mj -> vscode 및 template setting
https://docs.vuestorefront.io/v2/getting-started/project-structure.html
https://markus.oberlehner.net/blog/vue-project-directory-structure-keep-it-flat-or-group-by-domain/
https://velog.io/@cindy-choi/VUE-우아한-프로젝트-구조-짜기
https://vueschool.io/articles/vuejs-tutorials/how-to-structure-a-large-scale-vue-js-application/

view에는 router로 노출되는 화면 ( 해당 화면 전용 component는?? ) => 그래도 comp에 넣어야 재사용 가능성이 높??
directory는 feature 기준


Value of type '[UICollectionViewCell]' has no member 'compactMap'

The newest version get error in the method below.
visibleCellsValue of type '[UICollectionViewCell]' has no member 'compactMap'
// Call this method in `scrollViewDidScroll(_:)`.
    public func animateVisibleCells() {
        guard let model = animationModel, model.isEnabled else { return }

        visibleCells
            .compactMap { $0 as? GeminiCell }
            .forEach { [weak self] cell in
                self?.animateCell(cell)
            }
    }

@Benyi-Peng
If your swift version is less than 4.1, please update Swift version to 4.1 or higher.


Ability to use brotli instead of gzip

I will release a new version with this feature soon

Released in v1.1.0

Thank you very much!


Bug: Spell Advantage talent not functioning

The talent "Spell Advantage" is not functional, the following issues are observed:

The check on Row 260 in PlayerSheetSD.mjs is containing a typo
When importing a spell even after fixing typo in 1, it modifies the talent inside the compendium, so if multiple spell advantages are added, the system won't prompt the user for what spell to pick.

I suggest we rework the Spell Advantage check somehow. It uses system.bonuses.advantage as effect key, and the "REPLACEME" check, this is not a great solution. I think adding a new bonus called spellAdvantages and combine the system.bonuses.advantage & system.bonuses.spellAdvantages lists would be a better suited way.

Appears to be working as-is:

Can you confirm this is still an issue?

What should be the "Effect Value" when replacing the REPLACEME?  I am not prompted when I add the talent to a character sheet that already has spells learned.

What should be the "Effect Value" when replacing the REPLACEME? I am not prompted when I add the talent to a character sheet that already has spells learned.

It should be the slugified version of the spell name, you can look at the Magic Missile Advantage talent for an example, and you can get foundry to show you what that should be by opening the console and typing:
"<Spell Name>".slugify()

Just replace <Spell Name> with the full name of the spell.

What should be the "Effect Value" when replacing the REPLACEME? I am not prompted when I add the talent to a character sheet that already has spells learned.

It should be the slugified version of the spell name, you can look at the Magic Missile Advantage talent for an example, and you can get foundry to show you what that should be by opening the console and typing:
"<Spell Name>".slugify()

Just replace <Spell Name> with the full name of the spell.

Using the slugify worked like a charm, thanks!
I still, however, am not prompted to select a spell when I drag "Spellcasting Advantage" to a character sheet with existing spells.


Move buildable module test to a module test

Move test out of add-to-app test since the add-to-app project is already materialized.

Does module_test_ios run anywhere? I don't even see a integration_tests-macos shard.

Guess not.
https://github.com/flutter/flutter/blob/master/.cirrus.yml#L501
Can we diagnose the flakiness?  Or make this the only test that runs in a new integration_tests-macos shard?  Or was module_test_ios itself the cause of the flakiness?
I'm afraid this will atrophy again if it's not running on any CI system.

T.T
https://github.com/flutter/flutter/issues/36120

Gonna rerun this on head to make sure this doesn't flake on cirrus

These mac tests take forever to schedule. But didn't flake on reruns. Merging.


Preliminary docs

Working version of documentation, but lacking the automation / workflow situation that would ideally exist!

By the way, this Latex-y stuff in the rs.extrapolate docstring isn't getting rendered in the HTML. I assume there's a way to convince sphinx to render it here; I'm not sure how you would do it without changing how the command-line version looks?
https://github.com/rs-station/rs-booster/blob/a9b93dd2aae86c4400d9862440ae1260f0158449/rsbooster/esf/extrapolate.py#L10
It ends up looking like this, which is a little silly (though also not completely unreadable):

I just remembered that this exists! I think only remaining task is to give this repo a version of something like this:
https://github.com/rs-station/reciprocalspaceship/blob/main/.github/workflows/documentation.yml
Because of how CLI things are exported, I think the right approach here is for anyone adding a new function to just also add it manually to the appropriate place in the docs. Perhaps it could be possible to go through the set of entry points listed in setup.py and make sure they're all mentioned in the docs? But that's probably overkill.

The workflow would update the docs for existing utilities, if there were changes to the docstrings or arguments or whatnot.

I think that's a fine requirement for now -- better to have something.
We can copy over and modify that documentation.yml workflow. We'll also need to set up a gh-pages branch with the documentation build that we use to support the hosting -- that's ultimately how it works on reciprocalspaceship

I think I've done this all properly; I'm going to merge this in so that I can test the workflow. The only change to the actual code base was a restructuring of how the parse_args() function calls work, and I tested locally that those still work.


events.js:62 Uncaught Error: Uncaught, unspecified "error" event. (Authentication error)

Hello.
I am using React Node.js webpack and socket.io + socket.io-stream. And I am new to this.
I like a lot socket.io-stream because it is easy to use and I all the time get good results. But I do have a bug now.
I have the following code :
import React, { Component} from 'react'
import PropTypes from 'prop-types'
import CustomBannerDropZone from '../../components/tool/BannerDropZone.jsx'

/*
this. socket = io.connect('https://localhost:3000', {
  query: {token: Auth.getToken()}

var socket = io.connect('https://localhost:3000', {
  query: {token: Auth.getToken()}
})
*/
const ss = require('socket.io-stream')

class BannerDropZone extends React.Component {
  constructor (props, context) {
    super(props, context)
    this.maxSize = props.maxSize ? props.maxSize : 2097152
    this.maxWidth = props.maxWidth ? props.maxWidth : 3000
    this.maxHeight = props.maxHeight ? props.maxHeight : 3000
    this.text = props.text ? props.text : `Drop image here. Max ${this.maxSize} and ${this.maxWidth}px by ${this.maxHeight}px`
    this.state = {
      file: null
    }

    this.onDrop = this.onDrop.bind(this)
    this.save = this.save.bind(this)

    ss(this.context.socket).on('file-uploaded', function (data, file) {
      console.log('upload the file')
      this.state.file = file
    })

  }

I have a middleware to check the socket user with JWT, and it is working good for socket.io.
io-auth-check.js
const jwt = require('jsonwebtoken')
const User = require('mongoose').model('User')
const config = require('../../config')

/**
 *  The Auth Checker middleware function.
 */
module.exports = (socket, next) => {
  if (socket.handshake.query && socket.handshake.query.token) {
    jwt.verify(socket.handshake.query.token, config.jwtSecret, (err, decoded) => {
      // the 401 code is for unauthorized status
      if (err)
      {
console.log(err)
        return next(new Error('Authentication error'))
      }

      const userId = decoded.sub

      socket.decoded = decoded
      // check if a user exists
      return User.findById(userId, (userErr, user) => {
        if (userErr || !user) {
          return next(new Error('Authentication error , cannot find the user'))
        }
        console.log(user.familly_name + ' is connected')
        console.log('token thing works fine')
        socket.user = user
        return next()
      })
    })
  }
  next(new Error('Authentication error'))
}

index.js
module.exports = (io) => {

  var mongoose = require('mongoose')
  var ss = require('socket.io-stream')
  var ent = require('ent') // Permet de bloquer les caractères HTML (sécurité équivalente à htmlentities en PHP)
  var Grid = require('gridfs-stream')
  Grid.mongo = mongoose.mongo
  var gfs
  const University = require('mongoose').model('University')

  var ioAuthCheck = require('../middleware/io-auth-check')

  mongoose.connection.once('open', function () {
    gfs = Grid(mongoose.connection.db)
  })

  // Note sure about this

  io.use(ioAuthCheck)
    .on('connection', function (socket) {

The problem is that I got the error specified in the title:
Uncaught Error: Uncaught, unspecified "error" event.  So it is related to it. I need my middleware . What do you think I could do to resolve this issue ? Is there anything I did wrong ?
Best regards,
Arn

Hei. Okay it is weird, but to upload a file, I need to push mu button  two times, or write into the chat I put on the same page. It looks like I am missing a next() or something . I don't know. I keep trying to figure out.


Save closed/closed_by references

It would be nice to record linkages between issues, particularly the relationship between a pull request and the issue that it closes.
The graphql interface makes it a little hard to extract these, so this is non-trivial.  They appear as a CrossReferencedEvent in the timelineItems field of issues and pull requests with a willCloseTarget attribute.  The event list can be filtered based on the type, so it's not likely to be a huge addition to the load.  Note that events should be immutable, so updating this can use skip or after fairly reliably.
Originally https://github.com/martinthomson/i-d-template/issues/227

Mostly noting for myself, we want to capture timelineItems of type CROSS_REFERENCED_EVENT since the last successful update, keeping a list of those where willCloseTarget is true and the source/target is the PR/issue in question.
Probably worth collapsing this to a list of PRs which would have closed a given issue or PR, plus a list of issues/PRs closed by each PR.


chore(test-data): create product presets for GoodStore data (101-118)

This PR creates product presets 101-118 for our GoodStore dataset. Most of it was brought in from this PR and massaged, with tests added.
Notably, product descriptions were brought into ProductDraft.description rather than as an attribute in the ProductVariantDraft.

Presets based on the latest translations from: https://github.com/commercetools/test-data/pull/347


Pipe schedule reporting

The pipe schedule for headers in the physical trough model are currently reported via a notification as text. The values should be reported in the data tables as output that can be processed numerically. Report header diameters, runner diameter(s), and runner length(s) as output. These should be present in both SDKTool and in SAM.

Moving this issue to a private fork instead.


New rule: same line or newline for @else statements

via https://github.com/brigade/scss-lint/blob/master/lib/scss_lint/linter/README.md#elseplacement
newline:
@if {
  ...
}
@else {
  ...
}

same line:
@if {
  ...
} @else {
  ...
}

Wow, we still don't have it :) Thanks.

Yeah, definitely should have this.

Hmm, seems this rule won't be that easy.
Firstly, to be able to control @else placement at all, a user would need to set up ignore options for block-closing-brace-newline-after like so: ignoreAtRules: ["if", "else"]. I would allow this rule to take effect, but would lead to:
@if ($f == 1) {
 ...
} @else {} a { display: block; }

(notice the a { display: block; }). To prevent that we'll have to control how the closing brace of the last @else in a row behaves. The options I see:

Somehow read the block-closing-brace-newline-after's config if present and apply it, or
Use our own option, specific to this rule, something like

"at-else-newline-before": [
  "always", {
    "lastClosingBraceNewlineAfter": "always"
  }
]

Secondly, the space before @else. block-closing-brace-space-after doesn't give any viable option, so we'll have to control it. The question is, should it be an option to this rule, or a standalone rule? at-else-space-before soulds stylelint-ish, but the whole rule for a single statement... I don't know, doesn't sound well.
And all that said, should this rule still be at-else-newline-before or at-else-behavior?
Any thoughts?

Hmm, seems this rule won't be that easy.
Firstly, to be able to control @else placement at all, a user would need to set up ignore options for block-closing-brace-newline-after like so: ignoreAtRules: ["if", "else"]. I would allow this rule to take effect, but would lead to:
@if ($f == 1) {
 ...
} @else {} a { display: block; }

(notice the a { display: block; }). To prevent that we'll have to control how the closing brace of the last @else in a row behaves. The options I see:

Somehow read the block-closing-brace-newline-after's config if present and apply it, or
Use our own option, specific to this rule, something like

"at-else-newline-before": [
  "always", {
    "lastClosingBraceNewlineAfter": "always"
  }
]

Secondly, the space before @else. block-closing-brace-space-after doesn't give any viable option, so we'll have to control it. The question is, should it be an option to this rule, or a standalone rule? at-else-space-before soulds stylelint-ish, but the whole rule for a single statement... I don't know, doesn't sound well.
And all that said, should this rule still be at-else-newline-before or at-else-behavior?
Any thoughts? @kristerkari @jeddy3 @ntwb

Yeah, so basically if a user needs standard behavior for if/else, they'll just stick to the core stylelint rules, otherwise theys specify them as ignored in at-rule-empty-line-before and block-closing-brace-newline-after and use our custom rules.
Ok then, let's rock. Thanks for the advice @jeddy3

Will be published with the next minor.

Available in 1.4.1


where is the code that is responsible for filtering records by organization for frontend.

oro platform is a multiple organization solution,  for frontend, one organization can't see records from another organization, for the backend, when we call isGranted('VIEW', $object)，it might be denied  by organization check, but for frontend, we may not have code check permission,   let's assume a customer try to access product which is not in his organization,    where is the source code for this feature?

Hi @videni ,
What do you mean by the frontend? we have it in OroCommerce, but not in the plain platform.

oro platform is a multiple organization solution

Not exactly, oro platform supports only a single organization. To have multiorganization support you have to use an Enterprise Edition of OroCrm or OroCommerce.

@anyt , I mean OroCommerce frontend. I am using Oro technologies to build  a multiple organization based  project, I am not using OroCommerce,  or OroCRM, just some technologies that is useful for my customization.  it seems some code are not open sourced.

enable features for specific organization. a organization can only use features he owned. both backend and frontend.

and this issue.

multiple organization management.

Organization-specific product features are available only in OroCommerce Enterprise Edition. If you are an Enterprise Edition customer or a partner - please use the support portal to submit your request.


Option to switch to Fauxpilot "python-backend" by making "model" configurable.

In the newer fauxpilot there is also a "py-model", next to "fastertransformer" backend, which enables deployment on low-resource devices (using int8 / float16 support etc.)
To use it, "py-model" would need to be configurable.
See in:
https://github.com/Venthe/vscode-fauxpilot/blob/e35c57f6ec86f1b8536c4c6775247ff68ecb42ac/src/FauxpilotCompletionProvider.ts#L70-L71
this could be changed to:
return this.openai.createCompletion({
            model: workspace.getConfiguration('fauxpilot').get("model"),
            ....

And make it configurable, e.g. here: https://github.com/Venthe/vscode-fauxpilot/blob/546b0a023935bea90a1156a3a2b79bf2b98871d7/package.json#L62-L64

Hello; sorry for the delay. Github hasn't sent me any notifications...
done as of ba9f034 and released as 1.1.0. Thanks!


How should OpenSearch allow for extensions to provide authentication?

Today there are HTTPAuthenticator.java and AuthenticationBackend.java which are extensible through the security plugin for OpenSearch.  There are existing implementations for internal user storage, kerberos, saml, ldap, and jwt exchange,   The dependency on the Security plugin interfaces does not seem like the correct long term solution for extensions that want to provide authentication.
As many customers have existing Identity Providers (IdP) they can leverage how should we support these with extensions.  Alternatively, should these be supported in another way perhaps built into OpenSearch?

Closing this issue as it is being tracked by https://github.com/opensearch-project/security/issues/1895 and https://github.com/opensearch-project/OpenSearch/issues/3846


Various improvements to REST

Includes:

A few minor bug fixes, cleanup, and doc fixes
Addition of proper OPTIONS handing
Richer implementation of CORS

The biggest update is to CORS. Previously, it was a very blunt all-or-nothing approach. The previous approach was appropriate for a public API, but not for anything that requires actual validation of the origin. This implementation stays with the spirit of simplicity (from the user's perspective) of being able to simply either annotate the related REST method, or implement a method for dynamic processing. I believe it should be basically compliant with the CORS spec.

Closing this PR as it applies to the old (pre v7) enroute.


Fill out memoryapi

Needs #466 first.

Test are failing with:

Doc-tests winapi
error: An unknown error occurred

They pass on my machine, though. Hmmm...

You have functions in memoryapi which come from a different library than kernel32. Specifically MapViewOfFileNuma2 which comes from one of onecore/onecoreuap/mincore/mmos. In Rust 1.6 inline functions, such as MapViewOfFile2, are not lazily instantiated and ld fails to strip unreferenced functions so it fails to link. I'm not entirely sure why the doc test fails on current Rust but my guess is that it depends on a symbol which only exists on a newer version of Windows than Appveyor has.

Doc tests failing because of https://github.com/rust-lang/rust/issues/44487

@retep998 This good to merge now?


Exclude binary sensors in default config

#646

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.112%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
411

Relevant Lines:
431

💛  - Coveralls


Creating a Baseline profile in OMEVVP

Requirement Breakdown
Details

Objective
Baseline Profile enables user to capture the baseline configuration for system configuration, firmware, or driver versions and maintain the desired state for clusters by identifying the drift against the baseline.

Authentication/Authorization
Authenticate using vCenter credentials (Basic Authorization) and "x_omivv-api-vcenter-identifier" (UUID of the vCenter) as a mandatory header.

List of the tasks in the workflow (in   order)
Ensure that the vCenter user credentials and the corresponding vCenter UUID are accepted.Comply with any input validation (see below)Invoke request to create a baseline profilePoll until the baseline profile is createdReturn baseline profile object

Module type: Library and/or executable
Both

Input and format
Accept the following input propertiesgroupIDsbaselineProfileNamefirmware repo iddriver repo iddriftSchedulemondaytuesdaywednesdaythursdayfridaysaturdaytimesundayAccept the following input parameter - vCenter uuid

Expected output and format   Export required
Add log message at various execution steps if provided else output to console. Export is not required.

Concurrency requirement.
None

Execution model: synchronous or   asynchronous
Synchronous

Applicable timeouts and retries
Attempt creating the baseline profile upto 3 times only when the failure is on account of a network timeout. On any other types of error for instance, providing invalid input parameters, no retry should be attempted.

Expected error handing
Handle all the network and non network related errors and log them in a user friendly way.

Expected domain specific validation
As specified above

https://github.com/dell/omivv/pull/39


Mirror teaching

This feature will be helping academy to use our application to teach there students Quran.
basically whatever teacher (host) does on their screen, it will reflect same changes on all the devices for all the users who are connected with the teacher.
ex:

if he play one word, it will play same word for all the students.
if he opens another surah, same surah automatically will be open for all the students
....

@hqaweb can use this feature for their academy and anyone else too insha'Allah.
[Note]: This feature should only be introduce or start working on, once issue #1 and #15 is completely done, even for word by word audio.  Then this feature becomes more useful.

@iBasit @hqaweb we can use this https://togetherjs.com/ .

togetherjs is mobile / tablet ready? I doubt it.

@iBasit it does work on mobile/ tablet devices as long as it supports webrtc, which I believe all modern browsers do support it (chrome/firefox).


MDV Wi-Fi Controller K86EB (0) does not work out

HA版本
2024.09.1
集成版本
0.5.7
之前可正常使用的集成版本
0.3.22
设备类型及型号
MDV Wi-Fi Controller K86EB (0)
使用的App
美的美居
问题详细描述
I just switched from the integration from georgezhao2010, and I found my three MDV Wi-Fi Controller K86EB (0)s does NOT work with the new one.  Maybe my devices are a little bit old,  and I can NOT scan any information with msmart-ng, either
The logs
msmart-ng query <IP_ADDRESS> --auto
INFO:msmart.cli:Discovering <IP_ADDRESS> on local network.
INFO:msmart.cloud:Using Midea cloud server: https://mp-prod.appsmb.com (China: False).
INFO:msmart.lan:Creating new connection to <IP_ADDRESS>:6444.
INFO:msmart.lan:Authenticating with <IP_ADDRESS>:6444.
INFO:msmart.lan:Authenticating with <IP_ADDRESS>:6444.
INFO:msmart.lan:Authentication with <IP_ADDRESS>:6444 successful. Expiration: 2024-09-08T20:50:30+00:00, Local key: 7d87a4cf5645bb7d57e248d7629694eb30aac952bb5db133e6a2123a191dacd8
ERROR:msmart.discover:Device class Device has not implemented refresh().
ERROR:msmart.cli:Device is not supported.

Hi @SikaiGGMU , any update from your side ?

python3 -m midealocal.cli discover -d --host <IP_ADDRESS>
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/local/lib/python3.11/dist-packages/midealocal/cli.py", line 24, in
from midealocal.device import (
File "/usr/local/lib/python3.11/dist-packages/midealocal/device.py", line 11, in
from typing_extensions import deprecated
ModuleNotFoundError: No module named 'typing_extensions'

Which version of the library are you using ?

@SikaiGGMU you can install midea_ac_lan in your HA device, once it done, you can discovery your device via web UI.
if there is still error exist, you can enable debug log via readme document and upload the full debug log to us.
if there is no any response for a long time, we will conside to close it as no error exist now.

Which version of the library are you using ?

I am using debian 12, and I keep updating my system.

Which version of the library are you using ?

I am using debian 12, and I keep updating my system.

could you help to answer our question ?
we don't care about your OS or update.
currently, you are using our midea_ac_lan integration, and you have reported a bug with it.
unfortunely, you didn't provide any error info, also not provided any debug log.
so, please back to your issue and this midea_ac_lan.
we have post the solution for you.
if you still think you want to fix error, please provide all the details with the issue template.
I'm sorry, we don't want to watste time with unnecessary  info.

Which version of the library are you using ?

I am using debian 12, and I keep updating my system.

could you help to answer our question ? we don't care about your OS or update.
currently, you are using our midea_ac_lan integration, and you have reported a bug with it. unfortunely, you didn't provide any error info, also not provided any debug log. so, please back to your issue and this midea_ac_lan.
we have post the solution for you. if you still think you want to fix error, please provide all the details with the issue template. I'm sorry, we don't want to waste time with unnecessary info.

I think the version I am using is clearly stated in the bug report (之前可正常使用的集成版本
0.3.22).

Which version of the library are you using ?

I am using debian 12, and I keep updating my system.

could you help to answer our question ? we don't care about your OS or update.
currently, you are using our midea_ac_lan integration, and you have reported a bug with it. unfortunely, you didn't provide any error info, also not provided any debug log. so, please back to your issue and this midea_ac_lan.
we have post the solution for you. if you still think you want to fix error, please provide all the details with the issue template. I'm sorry, we don't want to waste time with unnecessary info.

I think the version I am using is clearly stated in the stanza of "之前可正常使用的集成版本" of the bug report  (之前可正常使用的集成版本).
0.3.22).

I am afraid it would be hard for me to frequently switch between 0.5.x and 0.3.22, since I kind of "lost" my device in the 0.5.x version in the early try, and I HAD to restore my entire HA in order to get my device back.

I am afraid it would be hard for me to frequently switch between 0.5.x and 0.3.22, since I kind of "lost" my device in the 0.5.x version in the early try, and I HAD to restore my entire HA in order to get my device back.

what's your expected result for this issue?  I don't understand it.
we just need: what's the error and what's the detail.
if not, I'm sorry, no on can help with you for this issue.

I am afraid it would be hard for me to frequently switch between 0.5.x and 0.3.22, since I kind of "lost" my device in the 0.5.x version in the early try, and I HAD to restore my entire HA in order to get my device back.

what's your expected result for this issue? I don't understand it.
we just need: what's the error and what's the detail.
if not, I'm sorry, no on can help with you for this issue.

I was just elucidating the fact. Apparently, this new fork is not backwards compatible, and an art project is supposed to be backwards compatible. Also, I can live with the old version.
Lastly, still need to compliment, great work!

@SikaiGGMU  I can understand what you said.
unfortunely, it's no possible, it's not control by us, HA also not support it with some version changes(I'm not mean all the HA version upgrade, only some important changes that not backwards compatible)
not only for us, like apple iOS, you also can't support downgrade to old version, why ? as your config have upgrade to new version, only new version know the old format. unfortunely, new version don't know which old version you will downgrade to......
so I will consider there is no any info can be provide by this issue, and I will close it.
sorry.


fix broken download(url, path; headers) method

This method was broken because of a trivial typo: , versus ; in
the method signature, which escaped notice because the tests were not
sufficiently thorough. I could just fix the typo and add some more
tests, but since (a) this is exactly the kind of thing ArgTools is for
and (b) the Tar stdlib already depends on ArgTools, we might as well
just use it and use its test utilities for more thorough testing.

Codecov Report

Merging #26 into master will increase coverage by 15.37%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master      #26       +/-   ##
===========================================
+ Coverage   81.43%   96.81%   +15.37%
===========================================
  Files           5        5
  Lines         264      220       -44
===========================================
- Hits          215      213        -2
+ Misses         49        7       -42

Impacted Files
Coverage Δ

src/Downloads.jl
97.36% <100.00%> (+12.58%)
:arrow_up:

src/Curl/Multi.jl
98.61% <0.00%> (+12.02%)
:arrow_up:

src/Curl/Easy.jl
94.66% <0.00%> (+13.05%)
:arrow_up:

src/Curl/utils.jl
96.77% <0.00%> (+25.34%)
:arrow_up:

src/Curl/Curl.jl
100.00% <0.00%> (+42.85%)
: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 9e60335...7d3e4b1. Read the comment docs.


Create contact one step

[ ]  Does the code work?
[ ]  Are functions, methods, and variables adequately named?
[ ]  Any test on the new function?
[ ]  Is it well tested? It should pass all jest tests.
[ ]  Is the code clear and easy to understand?
[ ]  Does it meet the team guidelines and style guides?
[ ]  Is there any duplicated code?
[ ]  Is documentation on functions, methods, classes, contexts, and behaviours adequate?
[ ]  Are there better or simpler solutions?
[ ]  Is there any performance issue?

adding new middleware function that let front able to create contact with photo in one step


Synchronize Electronic Locations from Figgy

Coverage remained the same at 100.0% when pulling e5e4111dd05199da4aaf916a843c0f609203ec77 on 856_sync into 0a1c7d31713cdd585a75974839a8312175af00a7 on master.


Throws an error on third toggle

Extension
https://www.raycast.com/SebDanielsson/background-sounds
Description
I works when I toggle on, then off, but it fails and throws an error on the third toggle:
Error: Command failed with exit code 1: osascript
Background sound is on
Background sounds turned off
757:788: execution error: No matching processes belonging to you were found (1)

Background sound is on
Background sounds turned off
O9:run-applescript.js:38:21

---
35:         timedOut,
36:         command: "osascript",
37:         options,
38:         parentError: new Error(),
39:     });
40: }
41: exports.runAppleScript = runAppleScript;
---

https://github.com/raycast/extensions/assets/56486004/002ccfa4-6fa0-489c-ba2b-01473bbd7719
Steps To Reproduce

Toggle Background Sounds in Raycast
Do this 3 times
Receive error

Current Behaviour
Not working after 3 toggles. Then have to manually turn Background Sounds on/off in System Settings for it to work again.
Expected Behaviour
To be able to toggle on and off unlimited

Raycast 1.71.4
Sonoma 14.4.1

@pernielsentikaer did you try to toggle the sound on and off three times or more during testing? I can't reproduce on my end.

I can't reproduce it here, toggled 10+ times in a row without any issues
macOS 14.4.1 (23E224)
Raycast 1.72.0

Tried updating to Raycast 1.72.1, and uninstall then re-install the extension. No luck so far.
One thing I noticed is that the extension is not able to (at least not visually) toggle the Bakcground Sounds switch. Whenever I flip the switch after the error, I'm able to use the extension for a few runs again.

I think it's a UI thing.
I tried the following:

Open settings and see the Background Sounds switch set to off
Run the toggle command (The switch will still show that it's off)
Close settings and reopen (The switch will indicate that the sound is on)

If you're aware of a better way of changing macOS System Settings I'd be glad to try it out and update the extension.


[runtime][hip] The driver does not manage its devices properly in a multi-device context

There are a number of HIP functions that assume a selected device for the current thread and they operate on this device. For example hipModuleLoadDataEx.
We need to set the correct HIP device during IREE HAL HIP calls. The correct behavior should be that the HAL restores the selected HIP device before returning control to the caller. From a user's point of view the IREE HAL should not change the selected device unexpectedly.

This was/is an issue in CUDA as well and the last time a fix was attempted it ended in sadness. In CUDA changing the device would flush it and also synchronize, leading to switches taking up to 10ms to full seconds depending on whether there was any work in-flight. HIP may be better but I'm doubtful given that it's mostly a flaw with the design of the API they inherited.
During initialization (module loading/etc) this isn't a critical issue but is important when managing execution. Most real CUDA multi-device usage will take the model of one OS thread per device that has its respective device always set and then managing per-device submissions via those threads. We already have the pending action queue and could just lean on this: during normal execution all queue work should happen via the action queue thread and since each device has its own thread it's naturally always set appropriately. If we wanted faster startup we could move module loading to the action queue as well and that would allow multiple devices to initialize modules at the same time.
The big thing to work is that any operation we can avoid needing to make a TLS-dependent HIP API call on the "main thread" (whatever arbitrary thread the user is calling IREE on and thus coming in through the IREE HAL APIs on) should either use cached information from startup (for queries/etc), the action queue, or be explicitly OK with potentially blocking behavior (which is ideally nothing, but ok to work to that point).

@AWoloszyn, you mentioned that you wanted to refactor the HIP runtime and possibly to merge the common logic of the action queue between the CUDA and HIP drivers.
I was wonder if it makes sense to do first the refactoring and then to focus on this issue.

Good point - if we use the queue for doing submissions then having that be common would also solve the CUDA bugs we have (or at least fix most of the issues and leave just a few whack-a-mole ones).

Good point - we should pool all of those we can anyway and only submit to the queue (or force a blocking switch) when the pool needs to grow. Async allocs also require some work but it's not too different than what we need to do on other backends and we may be able to share things there (I've got a WIP PR for doing async allocs on CPU where we don't need to actually reserve memory at the HAL API time and instead can put it in the queue). The good news is all this can happen incrementally so long as we know where we're going (and get the queue commoned and generalized) - so long as we can get some real async traces from real programs and catch where we hit the major blocking ops we can burn them down.

Oh, for module loading we really need to fix the compiler to link executables together - ideally we should only have one HAL executable per device (though there may be more) and embedded within that we'll have multiple HIP/CUDA modules (or a library, etc) - that makes offloading to a worker thread even less costly as we'd only be sending one request for compilation to the worker thread instead of one per dispatch as we would be today.

It turned out that acquiring the information of what CUDA/HIP API functions require the current device to be set is not as straight forward as reading the doc. Even the CUDA doc is missing this information on a lot of function. I am working this out through experimentation now.
Regardless of what are the per-function requirements, HIP must have at least as relaxed requirements as CUDA does. My assumption is that if this is not the case, hipifying will be not straight-forward. We can focus on maintaining a unified implementation as much as possible. This may be a pessimization for HIP if it has less strict requirements for some functions. Then we may end up going through the device worker thread unnecessarily adding extra latency. For example I have checked that launching a kernel in HIP does not require the current thread device to be the same as the one associated with the stream we are launching on. According to the CUDA C++ Programming Guide in CUDA you can't launch kernels on other than the current device.
We would like to schedule functions on the device thread with coarse granularity and make as few round trips to the device thread and back as possible. I think in a lot of cases the hand-off to the device thread would happen right after the IREE HAL API vtable dispatch. Some of them make multiple CUDA/HIP API calls to complete.

I decided to not do guess work and raised questions for both HIP and CUDA. Even if calls right now don't fail they may start failing in subsequent releases.