Make Response.IsError functional for clients

Missed this in the last IsError PR.  Fixes https://github.com/azure/azure-sdk-for-net/issues/24225
As long as Response.IsError lives in Azure.Core.Experimental, we'll need to add the ResponsePropertiesPolicy to LLC clients' pipelines in their constructors, as we're doing here.  When this functionality moves into Azure.Core, we can add this to PipelineBuilder.

Test?

Test?

CanGetOutputModelOnSuccessCodeAsync was failing before this fix with the following exception:
Message:
System.InvalidOperationException : IsError was not set on the response. Please ensure the pipeline includes ResponsePropertiesPolicy.

Do we have a test for the error scenario?

Do we have a test for the error scenario?

CannotGetOutputModelOnFailureCodeAsync is intended to do this, but is there a case you're thinking of that's not covered here?  Happy to add...

That test throws inside the client. Do we have one that throws in the cast operator?


PhantomJS crashing while running gulp-uncss task

PhantomJS is crashing everytime i run gulp-uncss task. How to optimise uncss to reduce memory usage?(I am running it on VM  with 3.5GB and 2 Core)

What OS? I'm running vanilla uncss on a Lubuntu VM with ~750MB & 1 core.

How many CSS files are you passing through your gulp-uncss task? It may unfortunately try to run them in parallel and blow through your memory usage. FWIW, using the postcss version of uncss should fix this (if you are willing to use postcss), since I serialize execution in that pipeline.
(I never felt comfortable doing that on raw uncss and slowing things down, but perhaps we should. Check "serializedQueue" in uncss.js for where this is done.)

@Ajeetlakhani Is this still an issue for you?

@mikelambert Should this be closed?

I guess technically we should be supporting parallel execution requests of phantomjs by the same method I implemented it for postcss plugin (by serializing it). I was scared to do drastic changes at the time since I was new to the project, but given the support load and lack of other maintainer improvements, probably should be willing to make this trade-off...you interested? ;)

Don't know when I'll get time, collaborating at mde/ejs keeps me quite busy. Perhaps add the enhancement label and rename to something more descriptive of the task to be done (or open a new issue)?
If I get time, I'll let everyone know I'm working on it.

@mikelambert Would serializing PhantomJS requests also fix #136?

Grunt has a workaround fix, but gulp does not. Fixing this issue would also fix #136 and allow grunt-uncss to remove their hack.
I have https://github.com/giakki/uncss/pull/249 which I believe should fix this, and passes all tests, but I haven't tested it in a proper parallelized environment. @Ajeetlakhani , are you interested in testing my pull request to see if it fixes your issue?


[material-ui][ListItemSecondaryAction] Deprecate ListItemSecondaryAction component

We intended to deprecate ListItemSecondaryAction in v5 in favor of the secondaryAction prop in ListItem, but we forgot to do it officially. Now, we can't remove it in v6. This PR adds a new entry deprecation entry in the docs to deprecate ListItemSecondaryAction officially in v6.  See https://github.com/mui/material-ui/pull/26446 for context.
Preview link: https://deploy-preview-42251--material-ui.netlify.app/material-ui/migration/migrating-from-deprecated-apis/#listitemsecondaryaction

I tried to mark ListItemSecondaryAction as @deprecated using JSDoc but it was picked up as the component description in the docs. Is there a way to mark components as @deprecated in the code?

Other deprecated components like Hidden aren't marked either.

I don't have answers for all questions but:

Is a codemod provided in these scenarios?

We can read the user's implementation and try to apply the changes accordingly, but if it would be too difficult to know the correct replacement, then it's better not to have a codemod. If that's the case, we should explain in detail how to adapt.

As of today, there's no way of displaying a component as deprecated in the API pages e.g. Hidden is marked as deprecated in the usage page but not the API page.

We could implement this capability, what do you think @alexfauquette @danilo-leal?

Should we remove ListItemSecondaryAction from the list of APIs in the Lists docs page?

Yes

The rendering part you're looking to modify is here:
https://github.com/mui/material-ui/blob/df6516ea9bd7a1377c59dda667ee907838c9bbf1/docs/src/modules/components/ApiPage.js#L251-L261
The description is generated here: https://github.com/mui/material-ui/blob/df6516ea9bd7a1377c59dda667ee907838c9bbf1/packages/api-docs-builder/ApiBuilders/ComponentApiBuilder.ts#L459

We have a specific rule to validate that every public component is included in at least one docs md page. Removing ListItemSecondaryAction from the Lists page results in this error while building the docs:

Could we add a "skip" list so we can skip some of them?

Could we add a "skip" list so we can skip some of them?

Another option could be to keep it in the APIs but indicate it is deprecated

I think we should look into being able to mark components as @deprecated in JSDoc without it ending up in the component docs description so we can:

Automatically display a deprecation callout in the usage and API pages.
Remove the entry (or display as deprecated) in the related APIs list.
Make any other automation we can think of.

Also, consumers would see components as deprecated in their IDE, which is not the case at the moment afaik.
But probably in another PR.

I opened a draft PR with a potential approach we could use to treat JSDoc comments as the source of truth for deprecations: https://github.com/mui/material-ui/pull/42280


[rstream]  in the web worker scope

worker.js (esm) esbuild
import { fromIterable, trace } from<EMAIL_ADDRESS>
self.onmessage = function ({data}){
  fromIterable([1,3]).subscribe(trace('worker'))
}

|>  unhandled error: undefined

I don't know enough about your project setup, but I've not once run into any issues with using any of the packages in a worker. There's no reliance on any globals, so my guess this is a config issue with esbuild (sorry, no 1st hand experience with it, only via Vite). Can you please put up a small project somewhere for debugging/reproduction?

test project
created a test project
plz help solve the problem

@bit-app-3000 After a lot of digging, I found that esbuild does not support standard ESM import.meta look ups. This hasn't anything to do directly with thi.ng/rstream, but is required by the widely used assert() function of thi.ng/errors. To have esbuild deal with import.meta properly, we can write a little build plugin:
Plugin:
// plugin-import-meta-env.js

import { readFileSync } from "fs";

export default (prefixes = []) => ({
    name: "import.meta.env",
    setup({ onLoad }) {
        // only collect & expose selected (deemed safe!) env vars
        const env = { MODE: process.env.NODE_ENV };
        if (prefixes.length) {
            for (let k of Object.keys(process.env)) {
                if (prefixes.some((prefix) => k.startsWith(prefix))) {
                    env[k] = process.env[k];
                }
            }
        }
        const envFmt = `(${JSON.stringify(env)})`;
        // plugin hook (only apply to JS/TS files)
        onLoad({ filter: /\.[jt]sx?$/, namespace: "file" }, (args) => {
            const code = readFileSync(args.path, "utf8").replace(
                /\bimport\.meta\.env\b/g,
                envFmt
            );
            return { contents: code };
        });
    },
});

Then use a esbuild build script:
import { build } from "esbuild";
import pluginImportMetaEnv from "./plugin-import-meta-env.js";

await build({
    entryPoints: ["src/app.js", "src/store.js"],
    bundle: true,
    minify: true,
    outdir: "build",
    // can skip the looking for custom UMBRELLA prefix if you're just after using default behavior
    plugins: [pluginImportMetaEnv(["UMBRELLA_"])],
});

...and build via: node build.js
I've pushed some new releases (incl. the above linked commits), so also make sure to update your dependencies, just in case...

thx for the help
found another workaround

--define:import.meta.env={}

тут могуть бути підводні каміння?

Cool. Good to know...


Audio checklist problem

Hi,
Audiochecklist is not showing up in Lua, Macro.
I think i installed al the files and Sop in the correct folders.
Can you help please?
Kind regards,
Gilbert.

Hi Gilbert,
can you take a screenshot of the content of the folder <X-Plane>\Resources\plugins\FlyWithLua\Scripts\ and <X-Plane>\Resources\plugins\FlyWithLua\Modules and upload them here, so that I can see what is in there?

[image: image.png][image: 56408d3e-a6b6-4be9-b664-a1789ca7c3a4.png][image:
image.png][image: image.png]
Patrick,
Thanks for your reply.
Strange thing is that I have in the resources map a plugging map, but
inside the plugins map which is above the resources map there is another
plugin map.
I already deleted that plugin map, but no results.
When I started x plane 11, there was nothing in the plugins, no LUA, no
other addons like for example better pushbak, x camera etc.....
Sorry sending you my problems,
Kind regards,
Gilbert.
Op do 31 mrt. 2022 om 19:49 schreef Patrick Lang @.***>:

Hi Gilbert,
can you take a screenshot of the content of the folder
\Resources\plugins\FlyWithLua\Scripts\ and
\Resources\plugins\FlyWithLua\Modules and upload them here, so
that I can see what is in there?
—
Reply to this email directly, view it on GitHub
https://github.com/patrickl92/AudioChecklist/issues/14#issuecomment-1084921681,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASBN4K4DIUG533JNNZV4QULVCXQTBANCNFSM5SDJTCGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Patrick,
the problem is solved, I deleted the resources map, and let x plane build a
new one.
Reinstalled FLY WITH LUA,
Thanks,
Gilbert.
Op do 31 mrt. 2022 om 19:49 schreef Patrick Lang @.***>:

Hi Gilbert,
can you take a screenshot of the content of the folder
\Resources\plugins\FlyWithLua\Scripts\ and
\Resources\plugins\FlyWithLua\Modules and upload them here, so
that I can see what is in there?
—
Reply to this email directly, view it on GitHub
https://github.com/patrickl92/AudioChecklist/issues/14#issuecomment-1084921681,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASBN4K4DIUG533JNNZV4QULVCXQTBANCNFSM5SDJTCGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

[image: image.png][image: image.png][image: image.png]
Patrick,
These are the prints of the audi checklist in Lua,
In plugins , Lua, Macros. I still can't see my audio checklist.
Kind regards,
Gilbert.
Op vr 1 apr. 2022 om 00:00 schreef gilbert Goossens @.***>:

Hi Patrick,
the problem is solved, I deleted the resources map, and let x plane build
a new one.
Reinstalled FLY WITH LUA,
Thanks,
Gilbert.
Op do 31 mrt. 2022 om 19:49 schreef Patrick Lang @.***

:

Hi Gilbert,
can you take a screenshot of the content of the folder
\Resources\plugins\FlyWithLua\Scripts\ and
\Resources\plugins\FlyWithLua\Modules and upload them here, so
that I can see what is in there?
—
Reply to this email directly, view it on GitHub
https://github.com/patrickl92/AudioChecklist/issues/14#issuecomment-1084921681,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASBN4K4DIUG533JNNZV4QULVCXQTBANCNFSM5SDJTCGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Gilbert, I can't see you images. Please open this link and post the images there: https://github.com/patrickl92/AudioChecklist/issues/14

Hi Patrick,
I solved the problem.
Thank you for youre reply.
Kind regards,
Gilbert.
Op di 5 apr. 2022 10:04 schreef Patrick Lang @.***>:

Hi Gilbert, I can't see you images. Please open this link and post the
images there: #14 https://github.com/patrickl92/AudioChecklist/issues/14
—
Reply to this email directly, view it on GitHub
https://github.com/patrickl92/AudioChecklist/issues/14#issuecomment-1088394417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASBN4KZWS2QKPBVVLHD5BH3VDPX2PANCNFSM5SDJTCGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix UI Bug - Hide Empty Box Until Check Button Is Clicked

Description:
Fixed a UI bug where an empty box was displayed upon page load. This could be misleading or confusing for users. With this fix:
The box is now hidden when the page is loaded.
The box becomes visible only when the "Check!" button is clicked.
Screenshots:
Before:

After:

Would appreciate feedback and further suggestions if any!

tested. it looks nicer indeed. thank you for your effort @arashjafari


WIP: Travis code format investigation (resolves #201)

This does nothing, ignore it for now.  It's just allowing me to test things on travis until I find what's broken.

Interestingly, this did fix the issue in this case, as I suspected it had something to do with the way we're doing git clones and comparing cross-repo.  Not sure it's a permanent fix though (i.e. guaranteed to work in all cases).

Hrm, ok this commit appears to help it out better (ensuring we have the script before running it).  I think there are some states on travis that are more or less likely to fail, depending on what happened before it.


Internet Explorer browser support

Added support for Internet Explorer and other browsers when using the new "browser" platform in Cordova 4.
Chrome, Safari, and Firefox were already supported, but when using IE or any other browser an error would occur because the user agent string wasn't recognized.
I added specific logic to parse Internet Explorer's user agent string.  Note that IE 11's user agent string doesn't include "MSIE", so I search for "Trident" as well.
I also fixed the bug that was causing an error if the user agent wasn't recognized, so if a browser other than Chrome, Safari, Firefox, or IE is used, the plugin will still work.  It just won't have the device.model or device.version set.

What is the planned release date for this fix?  cordova plugin add org.apache.cordova.device still gets the version without the fix, so it still doesn't work in IE.


Build(deps): Bump xml-formatter from 3.3.2 to 3.4.1 (#4935)

Pull request opened by the merge tool on behalf of #4935

Merged in 45b7a5ae8172e2c38a4e8c034e02df55f1f51818


problem retrieving table data

Hi Dmitry,
I have this code:
import sqlalchemy as db
engine = db.create_engine("iris://kutac:pwd@localhost:51774/USER")
connection = engine.connect()
metadata = db.MetaData()
city = db.Table('demo.citytable', metadata, autoload=True, autoload_with=engine)
print(city.columns.keys())
---- where demo.citytable is a simple IRIS table:
Class Demo.CityTable Extends %Persistent
{
Property Name As %String [ SqlColumnNumber = 2 ];
Property City As %String [ SqlColumnNumber = 6 ];
Property Age As %Integer [ SqlColumnNumber = 3 ];
Property Friends As %Integer [ SqlColumnNumber = 4 ];
Property Cash As %Numeric(SCALE = 2) [ SqlColumnNumber = 5 ];
--- runnning the code result in error below:
PS C:\WORK\Projects\Python\sql-alchemy> & C:/Users/kutac/AppData/Local/Programs/Python/Python310/python.exe c:/WORK/Projects/Python/sql-alchemy/sqldemo.py
Traceback (most recent call last):
File "c:\WORK\Projects\Python\sql-alchemy\sqldemo.py", line 11, in
city = db.Table('demo.citytable', metadata, autoload=True, autoload_with=engine)
File "", line 2, in new
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\util\deprecations.py", line 309, in warned
return fn(*args, **kwargs)
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\sql\schema.py", line 616, in new
with util.safe_reraise():
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\util\langhelpers.py", line 70, in exit
compat.raise_(
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\util\compat.py", line 208, in raise_
raise exception
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\sql\schema.py", line 612, in new
table._init(name, metadata, *args, **kw)
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\sql\schema.py", line 687, in _init
self._autoload(
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\sql\schema.py", line 722, in _autoload
conn_insp.reflect_table(
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\engine\reflection.py", line 774, in reflect_table
for col_d in self.get_columns(
File "C:\Users\kutac\AppData\Local\Programs\Python\Python310\lib\site-packages\sqlalchemy\engine\reflection.py", line 500, in get_columns
for col_def in col_defs:
TypeError: 'NoneType' object is not iterable
any idea?

Hi, thanks for report,
yep, I see the issue, in my part and I fix it
but, you have issue as well
The correct code should be
city = db.Table('CityTable', metadata, schema='Demo', autoload=True, autoload_with=engine)

Schema name, has to be passed separately

ok, thanks Dmitry.

with you proposed change, I was able to retrieve data from the table as well. closing this issue.


I frequently have to sign in

Describe the bug
Since maybe few months back, I need to re-sign in very often. Previously I never had to do that. I don't know when/why it happens.
Expected behavior
To never resign on single machine when token is valid.
Desktop (please complete the following information):

VS Code Version 1.50.1
GistPad Version 0.1.12

Hey! I actually just rewrote auth and published it a couple of days ago. So if you updated to the latest version, you would have been asked to sign in again, but the frequent sign outs should be fixed. So I'm going to close this for now, since this issue should be resolved. Please re-open it if you see this issue again, after using the new extension version for a few days. Thanks!


Feature request: Auto generate app.listen port

We know, when we create a react application then, it automatically creates a port and runs the application to this port.
In the case when we create an express server then we provide a custom port like this
app.listen(3000)

I face some issues when I use a custom port number.
It's possible to generate a port automatically?
Example: 1st time my application run on 3000 number port but when 3000 number port is busy then it's run on 3001 number port automatically (Like react application generate auto port).

Hi @jinnatul . The .listen method comes from Node.js: https://nodejs.org/dist/latest-v15.x/docs/api/http.html#http_server_listen
You can provide no port number and Node.js will pick an unused port number to listen on.


catalyst support?

I have a app that runs on iOS, iPadOS and macOS, but this pod doesn't build on macOS.
Can you guys update this pod to support Catalyst?
Thanks in advance

Yes, we're looking into supporting Catalyst, but there are some issues to get there at the moment. Since we're doing fat library - Catalyst uses it's own version of x86_64 architecture and we can't include it, because we already included x86_64 for iOS Simulator. We can't compile it in x86_64h because Socket.io library uses libz that is not compiled for this architecture. And finally we can't use new XCFramework, because we want to support Xcode 10. We will switch to XCFramework as soon as Xcode 10 will be outdated.
We can offer you an option to compile version of our sdk specially for Catalyst, but it won't contain architecture for ios Simulator and you need to contact our support in order to ask for it.
PS. This is and old SDK. You can find latest version here: https://github.com/helpcrunch/helpcrunchsdk-ios/

Thanks for the info @Fishkiller, but it sounds above my head to compile myself. Is there an easy way to exclude this pod from macos builds of my app? I want to use the pod on iOS but not on macOS, but I can't build at all if I include your pod. Thanks again

No problem, in this case I recommend you to look into platform section in podfile. You defer which pods to install for which platform. https://guides.cocoapods.org/syntax/podfile.html#platform
You might need to create two targets: for iOS and MacOS


Theano Version Issues Between Exoplanet 0.4.4 and Celerite2

Describe the bug
The exoplanet software, when conda installed, automatically adds the package theano-pymc, which seems to conflict with my installed version of theano. When I have, without exoplanet, theano version 1.0.5 installed on my computer, the command
from celerite2.theano import  terms
executes normally. After a conda installation of exoplanet version 0.4.4, theano-pymc version 1.1.5 is automatically installed. Then, the command
from celerite2.theano import terms
ends in an attribute error, I have attached a picture. This is all done on a freshly created conda environment, with minimal packages installed. My advisor has also been able to recreate this problem on a completely separate machine.
To Reproduce
It is not necessary to create a fresh environment, but that has the best hopes for reproduction:
conda create -n myenv python
Then install any files one needs, I prefer using Jupyter Notebook, and so I run
pip install notebook
Install celerite2 and theano:
conda install -c conda-forge theano python -m pip install -U celerite2
Then running the following command in either a jupyter notebook or any short python script should terminate successfully:
from celerite2.theano import terms
Next, installing any version of exoplanet seems to override this. I did it with the latest version:
conda install -c conda-forge exoplanet
Now when I run the command
from celerite2.theano import terms
The code ends in an Attribute error, a picture of which is attached.

Expected behavior
I expect the command
from celerite2.theano import terms
To execute without error.
Your setup (please complete the following information):

Version of exoplanet: 0.4.4 (though I have tried multiple versions)
Operating system: macOS Catalina 10.15.7
Python version & installation method (pip, conda, etc.): Python version 3.7.10 (though I have tried multiple version)

Additional context
With this setup, I have installed and successfully run Celerite2 tutorials, provided they do not use the directory celerite.theano.
Additionally, I have run exactly copied exoplanet tutorials. Those that do not use celerite2 run to accurate completion. Those that use celerite2 end in failure.

I've moved this to celerite2 because the initial issue is a celerite2 issue not an exoplanet issue.
@LucaNap: I'm sorry that you're having trouble with this, but I'm certainly not forcing you to use anything! I'm working on fixing this issue (that was only opened 2 weeks ago), but this project has a lot of dependencies that have been breaking like crazy recently and I'm just one person doing what I can so please have some patience.

@dfm sorry I did not mean to disrespect you.. I guess this shows that english is not my first language! Thanks for your work

@LucaNap: Thanks for your response and no hard feelings! I'm hoping to have an updated release in the next day or two (see #29).

Thanks for reporting this issue @ceyrox. I have been encountering similar problems with:
from celerite2.theano import terms
My PhD at the European Southern Observatory focuses on stellar activity filtering using Gaussian Processes towards exoplanet detection and characterisation. So celerite2 + PyMC3 should be perfect for that work.
Please @dfm let us know when you pushed a compatible version of celerite2 with exoplanet 0.4.4 and its latest dependencies.
P.S.: Cheers to the developer team of celerite2 and exoplanet, great work! 👌

I've just updated celerite2 and exoplanet on PyPI so
python -m pip install -U celerite2 exoplanet

should deliver versions that are all compatible. You might want to make sure that the theano and theano-pymc packages are uninstalled first because there are issues with colliding namespaces between those two packages.
I'm going to close this issue for now, but please comment if you continue having these issues and I can reopen as needed!


OSError on Vault PKI relation created event

Describe the bug
OSError on Vault PKI relation created event.
To Reproduce
Follow the How-to Use Vault as an intermediate CA  guide:

juju config vault common_name=mydomain.com
juju deploy self-signed-certificates
juju integrate vault:tls-certificates-pki self-signed-certificates
juju deploy tls-certificates-requirer --config common_name=demo.mydomain.com
juju integrate tls-certificates-requirer vault:vault-pki

Expected behavior
No error
Logs
Model  Controller          Cloud/Region        Version  SLA          Timestamp
lev    microk8s-localhost  microk8s/localhost  3.4.0    unsupported  07:34:01-04:00

App                        Version  Status   Scale  Charm                      Channel    Rev  Address         Exposed  Message
self-signed-certificates            active       1  self-signed-certificates   stable      72  <IP_ADDRESS>   no
tls-certificates-requirer           active       1  tls-certificates-requirer  stable      59  <IP_ADDRESS>  no       Certificate request is sent
vault-k8s                           waiting      1  vault-k8s                  1.15/edge  201  <IP_ADDRESS>  no       installing agent

Unit                          Workload  Agent  Address      Ports  Message
self-signed-certificates/0*   active    idle   <IP_ADDRESS>
tls-certificates-requirer/0*  active    idle   <IP_ADDRESS>         Certificate request is sent
vault-k8s/0*                  error     idle   <IP_ADDRESS>         hook failed: "vault-pki-relation-created"

Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/./src/charm.py", line 1355, in <module>
    main(VaultCharm)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/main.py", line 544, in main
    manager.run()
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/main.py", line 520, in run
    self._emit()
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/main.py", line 511, in _emit
    ops.charm._evaluate_status(self.charm)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/charm.py", line 1228, in _evaluate_status
    charm.on.collect_unit_status.emit()
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/framework.py", line 352, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/framework.py", line 851, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/ops/framework.py", line 941, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/./src/charm.py", line 212, in _on_collect_status
    if not vault.is_api_available():
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/lib/charms/vault_k8s/v0/vault_client.py", line 128, in is_api_available
    self._client.sys.read_health_status(standby_ok=True)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/hvac/api/system_backend/health.py", line 68, in read_health_status
    return self._adapter.head(
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/hvac/adapters.py", line 211, in head
    return self.request("head", url, **kwargs)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/hvac/adapters.py", line 408, in request
    response = super().request(*args, **kwargs)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/hvac/adapters.py", line 367, in request
    response = self.session.request(
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/requests/adapters.py", line 458, in send
    self.cert_verify(conn, request.url, verify, cert)
  File "/var/lib/juju/agents/unit-vault-k8s-0/charm/venv/requests/adapters.py", line 261, in cert_verify
    raise OSError(
OSError: Could not find a suitable TLS CA certificate bundle, invalid path: /var/lib/juju/storage/certs/0/ca.pem

Environment

Charm / library version (if relevant):1.15/edge (rev. 201)
Juju version (output from juju --version): 3.4.0
Cloud Environment: MicroK8s
Kubernetes version (output from kubectl version --short): 1.29-strict/stable

This usually happens when the certs storage is not attached to the unit yet. I'm taking a look.


Failed to create connection to server 'PicoTorrent' on topic 'ApplicationOptions': a client's attempt to establish a conversation has failed.

This problem appears sometimes when I try to open PicoTorrent on Windows 10

I have the same error every time I change settings and PicoTorrent asks to restart

Same issue here


Does the /consumption/summary/ endpoint return real time data?

Hi there, just wondering if the /consumption/summary/ endpoint return real time data or how much of a delay is there?
In other words can I get data for the current day or can I only get data for the previous day after passing midnight?
Thanks!

Hey Dixon - great question. The electricity consumption data comes from the metering providers (not Electric Kiwi) and it's a delayed service. The consumption data is made available via the API endpoints, /consumption/summary/ and /consumption/averages/ as soon as we receive it. Generally, reads arrive between 48-72 hours behind real-time as a rule of thumb.
I hope this helps. Cheers.

Thanks, ah this won't work for me then. I'm thinking to build a function that runs just before midnight and checks the current day's consumption and set the HOP to the hour with most consumption.

There are alternative third party hardware solutions to obtain real time consumption data which you can still achieve the same outcome. Sounds like a great project - let us know how you go!
I will look to process your API request shortly so you have access to the sandbox environment to play with our API.
Cheers, Matt


Pup 5545 rubocop by default

Hey @ghoneycutt, it looks like the Rubocop check is now failing in Travis, could you take a quick look and see what's going on there?

Hi @HAIL9000
Seems that the rubocop testing for puppet itself is using an older version and was attempting to read the .rubocop.yml file in the skeleton. I added a commit which tells the rubocop for the puppet project to ignore files in the puppet skeleton itself.
https://github.com/puppetlabs/puppet/pull/4463/files#diff-11a0d7906801d9dea0eccb85667ad811R15

Don't merge yet.. I found some more additions to the configuration while testing another module that contained custom facts. I'll also need to run this over a module with custom types and providers to ensure it isn't suggesting changes for things that are common place in the community.

Ping @andersonmills

Needs a rebase :(

Hey @ghoneycutt, do you have some time to give this a quick rebase? Looks like there are merge conflicts

Hey @ghoneycutt could you rebase? @andersonmills can you follow up and either merge when the changes become available or close if there is no activity?

CLA signed by all contributors.

@joshcooper @hail9000
Rebased

I've opened a rebased PR at https://github.com/puppetlabs/puppet/pull/4936 for @andersonmills to test. If it looks good we'll merge it, otherwise might have more requests for work.

Closed in deference to #4936


Improve Styling for Sankey Diagram

Added gradient for top and bottom section
Center the sankey on mount
Z index

Please fix conflicts


Add cheatsheet to website

[ ] Add cheatsheet to website
[ ] Link to cheatsheet from docs?
[ ] Change web version of cheatsheet to look different somehow

this would be great as "cursorless cheatsheet" isnt working for me
("cursorless docs" and "help" are though)

@asg0451 worth filing a bug if "cursorless cheatsheet" isn't working for you.  Are you running it with VSCode focused?
Keep in mind that the cheatsheet on the website won't be tailored to your customisations, unlike the one that you get from the "cursorless cheatsheet" voice command

done ty https://github.com/cursorless-dev/cursorless/issues/969


ExposedSecretReport target attribute is always empty

What steps did you take and what happened:
The target attribute of found secrets in ExposedSecretReport is always empty, although when reviewing the same report produced by trivy cli (using trivy i --security-checks secret -f json <image>) the target is specified:
Output from trivy cli:
  "Results": [
    {
      "Target": "/etc/apt/s3auth.conf",
      "Class": "secret",
      "Secrets": [
        {
          "RuleID": "aws-access-key-id",
          "Category": "AWS",
          "Severity": "CRITICAL",
          "Title": "AWS Access Key ID",

ExposedSecretReport of same image:
  secrets:
  - category: AWS
    match: AccessKeyId = ********************
    ruleID: aws-access-key-id
    severity: CRITICAL
    target: ""
    title: AWS Access Key ID

What did you expect to happen:
Was expecting to see the value of target to be populated with the path of the file where the secret material was identified.
Anything else you would like to add:
N/A
Environment:

Trivy-Operator version (use trivy-operator version): 0.10.2
Kubernetes version (use kubectl version): 1.24.9
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): N/A

I think the issue is that the operator assumes that Target is part of the Secerts object elements, as defined here: https://github.com/aquasecurity/trivy-operator/blob/bc2ae293b8e11eacaefc445278b471176253ecf2/pkg/plugins/trivy/model.go#L46
However, looking at a JSON report from trivy cli, the Target is an attribute of the Results object elements:
  "Results": [
    {
      "Target": "/etc/apt/s3auth.conf",
      "Class": "secret",
      "Secrets": [
        {
          "RuleID": "aws-access-key-id",
          "Category": "AWS",
          "Severity": "CRITICAL",
          "Title": "AWS Access Key ID",

so when the report is being populated here: https://github.com/aquasecurity/trivy-operator/blob/bc2ae293b8e11eacaefc445278b471176253ecf2/pkg/plugins/trivy/plugin.go#L1936
it never gets a value.

Hey @chen-keinan 👋🏼 hope you'd have a sec to take a look at #993, I believe it addresses this issue.


adding option to read transform from dictin memory

Codecov Report

Merging #25 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #25   +/-   ##
========================================
  Coverage    72.28%   72.28%
========================================
  Files           11       11
  Lines          837      837
========================================
  Hits           605      605
  Misses         232      232

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 b9b5869...0f37df0. Read the comment docs.


Convenience method to set all the dotstars to the same color

Hello, I don't know how to get past the build docs failure. Any advice greatly appreciated.

Hi, this function is already built into the dotstars object. So to set them all to 0x00FF00 for instance, you can actually just call:
from adafruit_funhouse import peripherals

peripherals = Peripherals()
peripherals.dotstars.fill(0x00FF00)

Thanks for adding this, but I'm going to close this because it adds duplicate functionality and these libraries are pretty close to pushing the memory limit over the line.

Thanks for the update. I'll have a go submitting a different PR to add the dotstar attribute to the Sphinx docs if that's OK.

Yep, thank you.


[WIP] Expose GPIO

@MGBla could you test this on a real hardware?

@MGBla could you test this on a real hardware?

That would be great. Because I am having really bad time testing it on the docker simulation.

Replaced by #66


Memory leak

Hello,
QAVSubtitleFrame::QAVSubtitleFrame()
: QAVStreamFrame(*new QAVSubtitleFramePrivate)
{
Q_D(QAVSubtitleFrame);
d->subtitle.reset(new AVSubtitle, subtitle_free);
memset(d->subtitle.data(), 0, sizeof(*d->subtitle.data()));
}
Asan tell me -  new AVSubtitle  - not free
Propousal:
static void subtitle_free(AVSubtitle *subtitle)
{
avsubtitle_free(subtitle);
delete subtitle;
}
Leak very fast, ~8Gb around 2 minutes
Thanks

thanks, looks something wrong with
https://github.com/valbok/QtAVPlayer/blob/master/src/QtAVPlayer/qavsubtitleframe.cpp#L37

https://github.com/valbok/QtAVPlayer/pull/479

thanks,
looks delete subtitle; is missing, right.
Could you please add MR and will be merged you as author? Also did you try ASAN with that fix?

Hi!
Sorry for the long time answer - a lot of work and little time :)
I do not claim authorship, thank you for making the merge yourself.
You have a good project, I wanted to help.
Yes, after this correction the asan says that everything is fine.
Well, at least not bad ).
There are still leaks, but they are minor and, in my opinion, not worth attention.
At least for now.
Thank you for your work and project.
I was glad to help.


shortcut to SSL, anyone?

since this is a private gitlab on a publicly hosted machine (out on AWS) I want SSL out of the box, so I thought I'd go with a module that will use Let's Encrypt to create my certificates. however there's a chicken and egg here - nginx won't run till I create the certs and the certs can't be created without a working webserver (that will also serve files from the disk), so unless I'm missing something...?
in order to automate this, I'd have to patch this module and make a PR. I'll happily do it on a less busy week. for now I'd love it if there's a shortcut solution that I'm missing (or I'll just manually bootstrap the first cert and fix this in June)
Thanks in advance!

This will be fixed in an upcoming Gitlab Omnibus release and then also supported by the Puppet module. You can track progress here (see comments for some hints how to do it atm) : https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1096


Incorrect website grizzly install command

According to https://www.weld.rs/grizzly/ the command to get started is $ pip install grizzly however this doesn't seem to be correct. The grizzly package on PyPi is some sort of USB driver.
I believe the documentation should be: pip install pygrizzly but that is failing for me, too

@gnmerritt were you able to fix it? I'm having the same issue. I installed using pip install pygrizzly. However, when I try to import I'm getting NameError: name 'WeldInt16' is not defined

Ah, this version of Grizzly is outdated/not supported. We’ve been working
on a ground up rewrite that isn’t published on PyPi yet, but you can
install it from source here:
https://github.com/weld-project/weld/tree/master/weld-python
I’ll post an update on this issue when this is released/published!
On Sat, May 2, 2020 at 9:21 PM Supun Abeysinghe<EMAIL_ADDRESS>wrote:

@gnmerritt https://github.com/gnmerritt were you able to fix it? I'm
having the same issue. I installed using pip install pygrizzly. However,
when I try to import I'm getting NameError: name 'WeldInt16' is not
defined
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weld-project/weld/issues/503#issuecomment-623051851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKMEY5J7NYLXBRROR4SVU3RPTWM7ANCNFSM4LEMPWLA
.

--
Shoumik

@sppalkia Where can I find a working version of Grizzly? I tried installing the python package in weld-python directory, but it seems like it only includes the python weld APIs, but not Grizzly. (I tried doing import weld.grizzly, it says no module found)
Should I use the old python/pyweld, python/grizzly, ..etc project? If so, what version of the release would you recommend?


Breakpoints should be faster

This does the following:

Expressions are filtered so that we don't evaluate parts of the tree that don't matter
We allow breakpoints to be set from more positions

the biggest perf issue is that we typecheck the whole thing before we check breakpoints.


windows 7 (maybe windows xp) support

From what i've been seeing it's mostly a matter of adding a few dlls. Need to investigate should be possible.

Let's use "Platform testing" for that


caravel-redesign-2: Missing mag/mgmt_core_wrapper.mag

The caravel-redesign-2 branch is missing mag/mgmt_core_wrapper.mag.
The actual layout in this file is irrelevant because make ship/truck adds a GDS_FILE property.

the mgmt_core_wrapper is flattened inside the caravel_core

@d-m-bailey The only required macro to be loaded from the caravel_mgmt_soc_litex repo is the RAM128. should its views be added to the caravel-redesign-2 branch?

So with mgmt_core_wrapper flattened, caravel_core.mag directly loads mgmt_core_wrappers subcells RAM128, etc. However, RAM128.mag is not on the path, so magic throws an error.
File ../mag/RAM128.mag couldn't be read

Do you want to change the Makefile to load caravel_core instead of mgmt_core_wrapper and set a GDS_FILE for caravel_core instead?

@passant5 I'm not even going to try suggest a simple solution to this because it may be a much deeper issue.
It seems to me that previously hard macro mgmt_core_wrapper is now being used as a soft macro where only the verilog from the repo is relevant. Maybe the hard sub macro RAM128 is also needed from the repo.
There's also this message in regards to the simple_por.
Duplicate cell in caravel_core:  Instance of cell simple_por is from path ../mag but cell was previously read from ../maglef.
Cell name conflict:  Renaming original cell to simple_por#0.
Warning:  Renaming read-only cell "simple_por"
Read-only status will be revoked and GDS file pointer removed.

The GDS file pointer removed is alarming.
@RTimothyEdwards help. Who do we need to bring into this?

@d-m-bailey make ship is not updated. The hierarchy changed quit a bit, and this target is only used for tapeout, so it is usually the last thing that gets updated after we review the hierarchy. This hierarchy is similar to the one in gf180mcu so I recommend you take a look at the target here.

@marwaneltoukhy :  Mitch is trying to run LVS on a full chip design so it is critical that make ship should keep tracking the actual layout changes.  It is not some detail to be left until the end.

@d-m-bailey :  The purpose of the sleight-of-hand around the simple POR is that the top level assembly uses cif *hier write disable to avoid the considerably large overhead to resolve hierarchical issues in the GDS that aren't needed for properly designed standard cells and I/O cells, all of which correctly abut without modifications.  But that gets disabled universally, so any circuits that require hierarchical processing, like the simple_por, may end up with DRC errors due to the failure to patch up layers through the cell hierarchy.  So the simple_por is (supposed to be) using the abstract view, which will get replaced verbatim with the pre-built simple_por.gds, which has already been put through hierarchical processing.
If the view is switched from "maglef" to "mag", then there is some risk of DRC errors being introduced into the design due to the failure to do hierarchical processing.
Maybe I should implement a different behavior in magic;  I could use a property tag to force a cell to use hierarchical GDS processing;  essentially override cif *hier write disable on a local level.  That would avoid needing to deal with the abstract view.

@RTimothyEdwards Thanks for the explanation. Just wanted to be sure that people are aware the current make ship/truck won't work with caravel-redesign-2. I'll try again once the Makefile is updated.

I can update it, but I'll need @jeffdi and @RTimothyEdwards approval and review as the tapeout process heavily depends on it.

@d-m-bailey fixed in PR #422


ion-Input clearIcon only aprearing when used in conjunction with ion-item

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When using  WITHOUT a wrapping  the clear-input button does not appear when typing.
Expected behavior:
Using the ion-input on it's own will work. Sometimes you might want the function of the ion-input without the styling of the ion-item
Steps to reproduce:
http://plnkr.co/edit/sobZUdUpMH3aPYIauqub?p=preview

Hello, thanks for using Ionic! At this time it is a requirement for ion-input to be a child of ion-item as ion-input inherits alot of styles (including for the clear button) from ion-item. Because of this, I am going to consider this a feature request and move this over to our internal feature request tracking repo. When we have evaluated and started working on this feature, I will move this back to the main repo here.

This issue was moved to ionic-team/ionic-feature-requests#264

thnx for opening the feature request. Is there any way to get feedback on the progress of these matters? (this is no biggy ,was just wondering :-))


Minor Improvements

Add final to variable
Remove Unused import
Use Standard Charset object
Use computeIfAbsent
Replace 'StringBuffer' with  'StringBuilder'

Hi @garydgregory
I agree that I should have checked if the binaries was broken. My mistake by not running mvn clean install japicmp:cmp
I've execute  japicmp:cmp and i notice that  are several error, including the two of the UPPERCASE that you comment.
What do you think we should do? we solve all the error of CheckStyle in this PR  or do we create a new one?

Hi @garydgregory
I agree that I should have checked if the binaries was broken. My mistake by not running mvn clean install japicmp:cmp
I've execute  japicmp:cmp and i notice that  are several error, including the two of the UPPERCASE that you comment.
What do you think we should do? we solve all the error of CheckStyle in this PR  or do we create a new one?

I would just fix checkstyle issues in your PR, not everywhere.

I would just fix checkstyle issues in your PR, not everywhere.

I would just fix checkstyle issues in your PR, not everywhere.

Great. Fix it

I would just fix checkstyle issues in your PR, not everywhere.

Great. Fix it

HI @garydgregory
I think everything would be solved by now.
Regards

HI @garydgregory
I think everything would be solved by now.
Regards


Turn off on press functionality to close menu

Is there anyway i can turn off the functionality that closes the menu when you press anywhere within the content?

No


wrong docstring output encoding

From @IgorNovozhilov on March 23, 2017 20:49
Environment data
VS Code version:  1.11.0-insider
Python Extension version:  0.6.0
Python Version: 3.3.5
OS and version: win7-pro
Actual behavior

Expected  behavior

Steps to reproduce:

write "ru" docstring
hovered methods

It's a heisenbug... The text with the wrong encoding appears not on every hover. He occasionally appears when auto-save file, even when editing parcels not related to the method or docstring.
A similar problem: https://github.com/DonJayamanne/pythonVSCode/issues/372
Settings
Your settings.json:  no
Logs
no
Output from Console window (Help->Developer Tools menu)
no
Copied from original issue: DonJayamanne/pythonVSCode#844

Closing in favor of #96


Clearer doc on how to use .simulate()

I actually spent a good while on this. I'm using MaterialUI and those components don't have onClick props, they use onTouchTap and all sorts of custom events of the sort to handle touch and clicks.
It was not clear that .simulate() actually called the prop itself and did not cause a "real" event to be sent to the component, so I was trying to .simulate('click'). With no success obviously.
I'm not sure if there's a specific PR policy for this repo, but I figured I'd try my hand at clarifying .simulate()'s documentation.

I like the idea of this PR, but I think the example is wrong. React doesn't seem to support onTouchTap simulation:
TypeError: ReactWrapper::simulate() event 'touchTap' does not exist
    at ReactWrapper.<anonymous> (packages/modules.js?hash=b053b68f533e45d134e516cff9d658226e7fa66b:25409:19)
    at ReactWrapper.single (packages/modules.js?hash=b053b68f533e45d134e516cff9d658226e7fa66b:25975:19)
    at ReactWrapper.simulate (packages/modules.js?hash=b053b68f533e45d134e516cff9d658226e7fa66b:25405:14)
    at Context.<anonymous> (app/app.js?hash=48ae892390da5ada9154e1bedf99219291ef4069:875:49)
    at callFn (packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3227:21)
    at Test.Runnable.run (packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3220:7)
    at Runner.runTest (packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3688:10)
    at packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3799:12
    at next (packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3608:14)
    at packages/practicalmeteor_mocha.js?hash=489e07e2e98906b5ed07059bc93d8f53fe79c00b:3618:7

https://facebook.github.io/react/docs/events.html#touch-events

@joncursi this PR is targeting ShallowWrapper docs while your error is within the ReactWrapper (mount).

I'm just suggesting a different event be used in the example rather than touchTap which has known compatibility issues inside of React. Might make more sense that way.

Like @blainekasten suggested, I removed the part where I mention Material-UI. I hope it will still be clear enough.

I think this may need some updates for when https://github.com/airbnb/enzyme/pull/368 gets merged.

@Aweary i'm not following that PR very closely. But does it change it so it's not calling the prop anymore? If not, I don't think it hurts to merge doc PR's. They can always be updated later easily.

@blainekasten it's still calling the prop like before but now it simulates event propagation and calls that prop with an event-like object, so the result of calling simulate is more in line with the result of dispatching an actual event.

It may introduce deprecations related to calling custom events, which would be something we'd also want to document.

If it's still calling the prop. Then his doc suggestions are correct, and might need updating later. I say this is good to merged as is and we can update later. Then @gCardinal can get on the contributor list at least :)
LGTM

Yeah you're right, they are still technically correct (just potentially incomplete pending that PR) so I'm good with merging and updating later 😄

Well, I guess it's possible to future-proof how I wrote it. What about:

Be aware that .simulate() uses the component's props to simulate the event, meaning .simulate('click') will call whatever function is bound to your component's onClick prop and .simulate('touch') would call the onTouch prop.

I think it reflects well the current behavior and will still apply when that PR gets merged. What do you think?

@gCardinal I think what you have now is fine, I don't think we've decided on what exactly the future behavior is going to be 🙂

@gCardinal can you update your PR with the master branch? I think we can merge after that.

I had never use Github's "auto fork feature-thingy" when simply editing .MD files before, so I'm not sure I merged properly, but it seems alright. Let me know if there's a problem with it.

Looks good! Thanks @gCardinal


Don't re-open editor when switching side-bar tabs

Start with an open project but no open files. If I click a file in Explorer to open it, then close the editor, the file will remain selected in Explorer (that's fine).
Then if I switch to another tab, like Extensions, and switch back to Explorer, it will re-open the selected file.
This seems wrong; it should leave the editor closed.

I can not reproduce this. Can you reproduce using vscode insiders?
https://code.visualstudio.com/insiders/
if yes, can you please attach a short video / gif demontrating this?

I can reproduce it with my insiders version:
VS Code version: Code - Insiders 1.25.0-insider (b7e6e04666ca8dde560b69081c43365dce77d12a, 2018-06-22T05:17:08.689Z)
OS version: Windows_NT x64 10.0.17134

When I saw the op says

then close the editor, the file will remain selected in Explorer

I realize they have "explorer.autoReveal": false in their settings.
Steps:

Close all files
Open a file from explorer
Close it
Hide sidebar
Click the explorer icon to open the sidebar

And the selected file is opened again.

@jacobweber thanks, I also see this behavior it was just not clear from your original comment.
However this behavior is designed and we do it explicitly here
I feel like this is user preference and we would add an option to disable this only if more users complained.
@bpasero can also share why he originaly did this.

Thanks @yume-chan — you're right that I do have "explorer.autoReveal": false. Maybe it would make sense to disable this behavior if that setting is false? It seems to only make sense when it's true.

More complaints:

https://stackoverflow.com/questions/50181866/prevent-vscode-from-re-opening-selected-file-when-switching-back-to-explorer

https://github.com/microsoft/vscode/issues/75181


Release maps from the reference simulation tool

Run the tool with the reference design configuration for all channels with:

tensor to scalar ratio r = 0
1e-3

Release to the collaboration

The two cases for r should be 0 & 3e-3
J

On Mar 10, 2020, at 10:58, Andrea Zonca<EMAIL_ADDRESS>wrote:

Run the tool with the reference design configuration for all channels with:
tensor to scalar ratio r = 0
1e-3
Release to the collaboration
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@keskitalo do you think we are going to get realization 0 of the atmosphere for all channels sometimes before this Sunday? if so I'll wait and will run maps and do slides based on the full run, otherwise I'll just do an example run with a few channels.

@zonca realization 0 without a doubt, but hopefully all 8 realizations. I was almost done with the caching when I learned that the reported focal plane radii in the hardware configuration are underestimated. As a result, the simulated atmosphere does not span enough of a volume to fit the lines-of-sight. I'm caching the atmosphere again...

@keskitalo I wanted to pick 4 channels (1 per telescope per site) from the atmosphere outputs that you generated.
But I noticed now you deleted them from:
`/global/cscratch1/sd/keskital/s4sim/reference_tool/out/00000000`

I assume they were broken.
Fortunately I have 1 channel that I saved on my VM and I will use that single SAT channel to demo the tool, even if broken, it will do for now.
 Sorry for the delay.
-R

@zonca the first realization is in place for all tubes.

thanks @keskitalo, I am running them through

ok, I got the reference design with r=3e-3,
https://132-249-238-90.compute.cloud.sdsc.edu/output//reference-design-r-3e-3/
next r=0.

ok, r=0 is at https://132-249-238-90.compute.cloud.sdsc.edu/output/reference-design-r-0/
next week I'll do:

[ ] cross-checks, plots
[ ] add documentation about these
[ ] copy to NERSC
[ ] announce a proper release

@keskitalo @jdborrill
ok, I don't have the CMB ready, so can't do the full release but it seems like noise is priority.
So I ran noise+atmosphere only.
Maps are ready, I would like to announce release tomorrow or monday.
Here the documentation:
https://github.com/CMB-S4/s4mapbasedsims/tree/master/202004_reference_design
I think we need more docs about noise and atmosphere in the design tool (see #5), then I can summarize in the map release docs.
please send some feedback.

Hi Andrea,
Before we release more widely we should get Colin's validation.
Thanks,
Julian
On Thu, Apr 23, 2020 at 9:49 PM Andrea Zonca<EMAIL_ADDRESS>wrote:

@keskitalo https://github.com/keskitalo @jdborrill
https://github.com/jdborrill
ok, I don't have the CMB ready, so can't do the full release but it seems
like noise is priority.
So I ran noise+atmosphere only.
Maps are ready, I would like to announce release tomorrow or monday.
Here the documentation:
https://github.com/CMB-S4/s4mapbasedsims/tree/master/202004_reference_design
I think we need more docs about noise and atmosphere in the design tool
(see #5 https://github.com/CMB-S4/s4_design_sim_tool/issues/5), then I
can summarize in the map release docs.
please send some feedback.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-618799654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4LSQIF4YKRTDMFATN3CLROEK4VANCNFSM4LFES6WA
.

I am making a check of the white noise level in the maps, using the sensitivity from the table in the DRS.

So for LFL1 I took 383 microKsqrt(s).
I made the calculation and it is way off.

I'm sure I messed up some factor, @keskitalo @cbischoff, would you like to crosscheck my notebook at:
https://gist.github.com/zonca/5d48c8c80ea0a84b01fe66019b96a946

one issue is that high noise ell is dominated by the atmosphere.
So if I do the same exercise for the input maps at 10 days, and I take instead the NET from s4sim of 177 instead of 383 (see https://github.com/CMB-S4/s4sim/issues/7). I get:

From the map C_ell = 1.36e-15, from the NET C_ell = 9.76e-16
next I'll compute the total power spectrum from the input maps and compare with the output to check if the scaling makes sense.

ok, I made a full comparison including also the atmosphere:

Do you think it looks reasonable?
see the full notebook at https://gist.github.com/zonca/1914abdc08ee1ce00c719fc3aa5f94c7

Which spectrum is this? TT, EE, BB? If it is a polarization spectrum, then the atmospheric noise is extremely pessimistic. See this figure, for example -- BB noise spectrum from ACTpol 2yr result gets to ~1e-16 K^2 at ell~500, which is more than an order of magnitude better than the orange curve.
I'm worried about the assumption that atmospheric noise doesn't integrate down with number of detectors, only with integration time. By this assumption, there is some maximum number of detectors and beyond that number it is pointless to continue scaling up your instrument. Looking at this figure, it seems like the LAT has exceeded this maximum number of detectors by a factor of 1e7 at ell~100 and by a factor of 100 at ell~1000.
Also, why does the output map power (green curve) greatly exceed the sum of input atmosphere and input noise for ell > 500? Is there some sort of aliasing going on?

@cbischoff This must be temperature. Without gain and bandpass mismatch, the simulation does not have a mechanism to convert atmosphere-based temperature fluctuations into polarization.
Exactly how we choose to scale the atmospheric noise by detector count is open for discussion. We know that it is very correlated between detectors and won't scale as instrumental noise but beyond that things get complicated. Since the atmospheric noise in polarization is due to detector mismatch, it does help to have many detectors, provided that the mismatch between them is random and not systematic.
Thanks for pointing out the ell > 500 excess. I'm going to see if we can make the spectra align by masking out the poorly sampled edge pixels. If that does not work, we can try using PolSpice instead of anafast to appropriately weight the map according to noise level.

I should also point out that the spectrum above is for the Chile SAT LF1 case. The fraction of uniformly-weighted sky is 69%.

Doesn't your atmospheric noise model actually calculate lines of sight through some 3d Kolmogorov distribution? If so, then don't the detectors naturally show partial, but not complete, correlation? Or does the scaling come in because you do the atmospheric sim for just a small number of detectors? (how many?)

The correlations between detectors within a tube are simulated and accounted for. We only simulate one tube on each telescope. Since the footprint of the tubes on each telescope perfectly overlap, we decided to approximate that the additional tubes on the telescope do not average down the atmosphere. Separate telescopes are treated as independent.
In real life, there probably is some, scale dependent suppression of atmosphere from having more than one tube on the same telescope. We just don't have good models for this yet.

Since the footprint of the tubes on each telescope perfectly overlap, we decided to approximate that the additional tubes on the telescope do not average down the atmosphere.

I'm not sure what this means. Within an individual telescope, the different tubes are both physically and angularly separated. So, depending on where the ray bundles from the individual detectors start expanding, the different tubes might see very different atmosphere.
--
Tom Crawford
University of Chicago
Department of Astronomy & Astrophysics
773-702-1564

On Apr 27, 2020, at 11:23 AM, Reijo Keskitalo<EMAIL_ADDRESS>wrote:
The correlations between detectors within a tube are simulated and accounted for. We only simulate one tube on each telescope. Since the footprint of the tubes on each telescope perfectly overlap, we decided to approximate that the additional tubes on the telescope do not average down the atmosphere. Separate telescopes are treated as independent.
In real life, there probably is some, scale dependent suppression of atmosphere from having more than one tube on the same telescope. We just don't have good models for this yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620090462, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5DQRYCNZINPQAS7V44Z2DROWWQLANCNFSM4LFES6WA.

Thanks @tcrawfor . Indeed, this point remains unsettled. In the current model, the majority of the atmospheric power comes from 100m-sized correlated structures a kilometer away from the telescope.  I would expect a high degree of correlation between detectors looking at the same location on the celestial sphere, even if they were on different but adjacent optics tubes. As I said, there will probably be some scale-dependent suppression but we don't have reliable simulations for that yet.

But the different tubes in a single telescope are not looking at the same location on the celestial sphere. In a given instant, the sky is imaged onto the focal plane, and the physically separated tubes necessarily intercept different portions of that image.
--
Tom Crawford
University of Chicago
Department of Astronomy & Astrophysics
773-702-1564

On Apr 27, 2020, at 11:53 AM, Reijo Keskitalo<EMAIL_ADDRESS>wrote:
Thanks @tcrawfor https://github.com/tcrawfor . Indeed, this point remains unsettled. In the current model, the majority of the atmospheric power comes from 100m-sized correlated structures a kilometer away from the telescope. I would expect a high degree of correlation between detectors looking at the same location on the celestial sphere, even if they were on different but adjacent optics tubes. As I said, there will probably be some scale-dependent suppression but we don't have reliable simulations for that yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620106546, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5DQR4CNONCAXAANASYR4TROWZ7PANCNFSM4LFES6WA.

That seems like a semantic issue. If the FOV overlap then they, by definition, converge at infinity. The question seems to be if the modest separation of the tubes at the telescope is enough to decorrelate the observations.
I sent a question to the SAT group for another opinion.  I am out of my depth here and my naive thinking is probably less than helpful.

No, this is my fault. I had not read carefully enough, and I was thinking of LAT configuration, in which the different optics tubes in a single telescope can (by definition) not see the same sky.
--
Tom Crawford
University of Chicago
Department of Astronomy & Astrophysics
773-702-1564

On Apr 27, 2020, at 12:15 PM, Reijo Keskitalo<EMAIL_ADDRESS>wrote:
That seems like a semantic issue. If the FOV overlap then they, by definition, converge at infinity. The question seems to be if the modest separation of the tubes at the telescope is enough to decorrelate the observations.
I sent a question to the SAT group for another opinion. I am out of my depth here and my naive thinking is probably less than helpful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620118668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5DQRYXACV5UGWJ5OJVVY3ROW4UHANCNFSM4LFES6WA.

That certainly explains some of the confusion. It still remains that our model of not weighting down the atmosphere by the number of tubes is pessimistic. I am curious to hear from the SAT experts just how pessimistic they find it.

Although we're using this approach (which I thought we'd discussed and
agreed on the DM telecon) for both LATs and SATs, no?
Julian
On Mon, Apr 27, 2020 at 10:17 AM tcrawfor<EMAIL_ADDRESS>wrote:

No, this is my fault. I had not read carefully enough, and I was thinking
of LAT configuration, in which the different optics tubes in a single
telescope can (by definition) not see the same sky.
--
Tom Crawford
University of Chicago
Department of Astronomy & Astrophysics
773-702-1564

On Apr 27, 2020, at 12:15 PM, Reijo Keskitalo<EMAIL_ADDRESS>wrote:
That seems like a semantic issue. If the FOV overlap then they, by
definition, converge at infinity. The question seems to be if the modest
separation of the tubes at the telescope is enough to decorrelate the
observations.
I sent a question to the SAT group for another opinion. I am out of my
depth here and my naive thinking is probably less than helpful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <
https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620118668>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AC5DQRYXACV5UGWJ5OJVVY3ROW4UHANCNFSM4LFES6WA
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620119659,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4LSRSRECHZS3OUN24UPDROW43JANCNFSM4LFES6WA
.

Yes, the LAT tubes are also treated as perfectly correlated but for a very different reason. The FOV of the entire LAT focalplane is so small that the majority of atmospheric fluctuations are extremely correlated across all detectors.
Since the LAT FOVs do not overlap, we could just simulate all tubes and get realistic suppression from more tubes. From looking at ACT and SPT data, I really would not expect much improvement over the current model.  The angular scale of the atmospheric fluctuations is about the size of the LAT FOV.

The LAT FOV is 8 degrees in diameter, right? Are you finding nearly perfect correlation all the way across the SPT-3G focal plane? I thought we could detect decorrelation even across the ~1 degree SPT-SZ focal plane, but I can't back that up with hard numbers.
--
Tom Crawford
University of Chicago
Department of Astronomy & Astrophysics
773-702-1564

On Apr 27, 2020, at 12:34 PM, Reijo Keskitalo<EMAIL_ADDRESS>wrote:
Yes, the LAT tubes are also treated as perfectly correlated but for a very different reason. The FOV of the entire LAT focalplane is so small that the majority of atmospheric fluctuations are extremely correlated across all detectors.
Since the LAT FOVs do not overlap, we could just simulate all tubes and get realistic suppression from more tubes. From looking at ACT and SPT data, I really would not expect much improvement over the current model. The angular scale of the atmospheric fluctuations is about the size of the LAT FOV.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/CMB-S4/s4_design_sim_tool/issues/2#issuecomment-620128241, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5DQR4M4NUI3PWPIFSY4X3ROW63BANCNFSM4LFES6WA.

I found a bug in the scaling of the noise, I'm rerunning some maps to make a comparison, I'll open a new issue when I have results. Let's dedicate this issue to scaling of the atmosphere.

@tcrawfor excellent point. The correlation functions on https://cmb-s4.org/wiki/index.php/Atmospheric_calibration_with_SPT certainly show a modest dependence between correlation strength and separation on the focalplane. And that is only considering separations of less than 2 degrees. Tubes across the CMB-S4 LAT will be more separated and less correlated than our pessimistic model here.

@keskitalo do you recommend we change anything in the scaling of the atmosphere for the next run (in #13)?

@zonca Excellent question! We could decide to adjust the per-tube scaling to better match the map-based SAT simulations. However, there has been little focus on the SAT temperature sims. Much more critical would be to include some amount of detector mismatch and then scale the resulting polarized atmosphere. I propose we enable 1% gain mismatch in the sims, keep the tube scaling factors for now. If the resulting BB noise ends up grossly higher than the map-based sims we can revisit the per-tube scaling.

ok, agreed


Filter conditions on the same column overwrite each other

Bug report
Describe the bug
If multiple filters are provided for a particular column, only the last filter is applied in the query. All the previous ones are overwritten. This happens here in the FilterBuilder implementation (for all operators).
If we take a look at the other Supabase PostgREST implementations, they append additional filters instead (eg. here in postgrest-dart, here in postgREST-js).
To Reproduce
// Table has a column 'year' with values 2020, 2022, 2024.

client.From("mytable").Select("*", "exact", false).gte("year", 2023).lte("year", 2024).Execute()

// Results include 2020, 2022, 2024. Expected only 2024.

Expected behavior
Multiple filters for a given column should all be applied.
System information

Version of postgrest-go: 0.0.11
Version of go: 1.22.2

This was also reported in supabase-go: https://github.com/supabase-community/supabase-go/issues/13


Fix incorrect start after SDL crash

PR Changes:

Fix incorrect start after SDL crash

Related: APPLINK-27204

Please review: @anosach-luxoft , @LuxoftAKutsan , @orhan-mehmedov, @dtrunov

Reviewed

@OHerasym Reviewed.

Reviewed

@OHerasym Reviewed


[MODEL] Add "suggest" method to get response suggest

I would like to use suggest of Elasticsearch response.
But Elasticsearch::Model::Response::Response class hasn't the method. That's why I added it.
I have already signed the CLA.

I think it makes sense. Can we also have integration tests for the feature, and update to the example application HTML template (in a separate commit?)

Some tests on Travis are failing, do they run locally for you?

I fixed it.

I'm sorry for such a long delay, I've tweaked the code a bit and merged it! Thanks!


Fix the semicolon semantics for indexes while respecting other bug fix.

resolves #85
docs dbt-labs/docs.getdbt.com/#
Problem

Reprex now added as test and replicated locally!
@mikealfare shared this lovely context, re the comment linked in the issue ticket (here). We removed a ; at the postgres__get_create_index_sql macro to solve a different problem sending up empty queries when getting this merged:

We do not appear to be updating cache for MV functionality like drops, renames, adds which is causing catalog mismatch errors in runs especially between MV's that are dependent on each other

This however was incomplete as a solution because we needed to only leave off the last ; from various index create/alter statements.
Solution

Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[X] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

FYI @VersusFacit - We need to backport this fix for inclusion in v1.7.x + v1.8.x, because this was a regression introduced in v1.7.14. I don't believe we have the backport workflow set up in this repo yet, so we either need to backport manually or set up that workflow.


Replace ScatterNNlib with NNlib

The functionality of scatter and gather has been migrated to NNlib and NNlibCUDA.

It seems many tests have been removed, why?
Also, since the new scatter has different argument ordering, next release should be marked as breaking

There are two categories of tests are removed:

GATConv layer: tests are removed due to the introduction of number of node/edge check for FeaturedGraph in GraphSignals v0.2 series. Current tests will break the check due to the implementation of GATConv. GATConv has multiple head design, but the GATConv output mix the number of edges and heads together. Thus, GATConv need a new implementation to separate heads and number of edges.
Another test is message-passing network for CUDA: message-passing network has an operation of scalar indexing over a cuarray. Currently, new version of CUDA forbidden the use of scalar indexing, which breaks the tests. Message-passing need a new implementation for indexing vertecies or edges, maybe a cuda kernel.


Extend loop unrolling with one more loop case

This patch extends loop unroller to also handle this case:
      \|/
   +- HEAD<---+
   |   |      |
   |  MID     |
   |   |      |
   +->LATCH --+
       |
      exit

It corresponds to a do-while loop with one if inside.
The patch achieves this by adding the AdvancedUnroller class. There are some redundancies with the Unroller class. It would probably be nice to get rid of these redundancies by maybe creating a class hierarchy and moving some parts of unrollers to an abstract class in the future.
Here's a testcase to show off this patch:
int src()
{
    int x = 0;
    int i = 0;
    do
    {
        if (i % 2 == 0)
            x += 1;
        i += 1;
    } while (i < 10);
    return x;
}

int tgt()
{
    return 6;
}

With this patch applied, running smtgcc-check-refine on this code produces this:
testsmt3.c: In function ‘tgt’:
testsmt3.c:14:5: note: Transformation is not correct (retval)
src retval: #x00000005
tgt retval: #x00000006
   14 | int tgt()
      |

Without the patch, smtgcc gives up on the loop.

Thanks!
I have started a test where I compile all C and C++ files in the GCC test suite with the -O3 optimization level. It has found one problem so far: gcc/gcc/testsuite/c-c++-common/analyzer/infinite-recursion-pr108935-1.c fails an assert.

I have tested by compiling all C and C++ files in the GCC test suite with pysmtg-tv.so on X86_64, GCC trunk compiled a week ago (9d1bf1d0b7a14ef741e967e0ab3ead35ec8e5f4e), and the -O3 optimization flag. This found two issues...
Assertion
Several tests fail the assertion at lib/loop_unroll.cpp:613:
cc1: lib/loop_unroll.cpp:613: void smtgcc::{anonymous}::AdvancedUnroller::unroll(): Assertion `inst->nof_args == 0' failed.

One example of this is testsuite/c-c++-common/analyzer/infinite-recursion-pr108935-1.c:
typedef struct {
    unsigned idx;
    int vals[512];
} foo_t;

int ended(foo_t* f) {
    return f->idx >= 512;
}
unsigned foo(foo_t* f) {
    if (ended(f)) {
        return f->idx;
    }
    do {
        f->idx++;
    } while(!ended(f) && !f->vals[f->idx]);
    return foo(f); /* { dg-bogus "infinite recursion" } */
}

Miscompiled IR
pysmtg-tv.so claims that testsuite/gcc.dg/pr57233.c is miscompiled, but the GIMPLE looks correct to me, so I guess the unroller is doing something bad with the IR.
The detected issue is that the memory is not correct for
pr57233.c.146t.walloca2 -> pr57233.c.147t.pre

Below is a slightly simplified reproducer (where I have changed the types to unsigned char in order to make the checking faster)
unsigned char
r (void)
{
  static unsigned char x = 0xdeadbeefU;
  static unsigned char y = 0x12347654U;
  static unsigned char z = 0x1a2b3c4dU;
  static unsigned char w = 0x87654321U;
  unsigned char t = x ^ (x << 11);
  x = y;
  y = z;
  z = w;
  w = w ^ (w >> 19) ^ t ^ (t >> 8);
  return w;
}

void
init (unsigned char *p, int count, int mod)
{
  int i;
  for (i = 0; i < count; i++)
    {
      unsigned char v = r ();
      if (mod)
	v = (v % 31) + 1;
      p[i] = v;
    }
}

I'll have a look at these two bugs and (hopefully) report back with a fix.

I wasn't successful in fixing the second bug but I at least produced this reduced testcase while trying to (i used C-Vise):
init_count;
*init_p;
init() {
  int i = 0;
  for (; i < init_count; i++) {
    static w;
    w = w ^ 5;
    init_p[i] = 1;
  }
}

The reduced test case shows the issue even without your change! That is, it is a bug in smtgcc. I'm investigating...

Nice! I'm glad that I helped discover a bug and that the bugs in my PR are sorted out. I've squashed the commits as requested.


Allow passing custom tls.Config to the Config

Coverage remained the same at 35.784% when pulling 3239a61b71bf10f74401778f2cab5a52fc03665f on georgijd:f-add-support-for-tlsconfig into 5b9dc74d49a8646b548518001669e8d406173b7e on MatthewHartstonge:master.

Hello Georgi!
First off, thank you for your contribution! I appreciate it 👌
I’ll have a proper look into these PRs first thing tomorrow morning NZST and get back to you/merge them in!
Thanks!


🔊 added debug logs

Codecov Report

Merging #48 (30690b9) into main (7b108df) will increase coverage by 0.94%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
+ Coverage   73.75%   74.69%   +0.94%
==========================================
  Files           2        2
  Lines          80       83       +3
==========================================
+ Hits           59       62       +3
  Misses         21       21

Impacted Files
Coverage Δ

iamlistening/__init__.py
100.00% <100.00%> (ø)

iamlistening/main.py
73.75% <100.00%> (+1.02%)
:arrow_up:


⚠ Mobitopup has degraded performance

In 7ef642d, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 11378 ms

Resolved: Mobitopup performance has improved in 0355d5e.