Dynamic imports from CDN

Hello. Experiencing problems attempting dynamic imports from CDN. Doing something wrong?
Using in index.js,
    await Promise.all([
        import("https://..."),
        import("https://..."), ...
    ]);

With cdnjs.cloudflare URLs, it gives

Access to XMLHttpRequest at 'https://cdnjs.cloudflare.com/ajax/libs/...min.js' from origin 'http://<IP_ADDRESS>:8000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

OPTIONS 405 in the Network tab

Cloudflare has an example on how to simulate the OPTIONS method response via a service worker, but doing so didn't help.
With jsDelivr URLs, it gives

Access to fetch at 'https://cdn.jsdelivr.net/npm/...min.js' from origin 'http://<IP_ADDRESS>:8000' has been blocked by CORS policy: Request header field x-requested-with is not allowed by Access-Control-Allow-Headers in preflight response.

OPTIONS 200 in the Network tab

The errors occur for every import that I use. Everything works if imported via a script tag inside index.html.
However, it all does work when using unpkg URLs.
Except a specific library I load, that has this init code
...else if (typeof module === 'object' && module.exports) {
    // Node/CommonJS
    module.exports = factory(require('jquery'), global, global.document);
  } else ...

and it alone gives

Uncaught ReferenceError: require is not defined
at eval (eval at evaluateModule (app.js:), :)
at eval (eval at evaluateModule (app.js:), :)
at evaluateModule (app.js:)
at app.js:
at XMLHttpRequest.request.onreadystatechange (app.js:)

No, I tried adding shimming for jquery and it does not help.
Even with this one import commented out, it still does not work exactly like it does with script tag imports. Global objects that some libs define are missing when they are imported dynamically.
For clarity, what I want is a lean index.html with no script tags except the one for index.js. Index.js is to load my application after awaiting on imports of all of its dependencies from CDN.
A separate question: how do I unload a module when no longer needed to free up memory?
Thanks. Hoping too for SRI to be implemented in the next version.

@hollowcat the problem with dynamic import from CDN is that we don't know which object is exposed and how it is exposed. Anyway, I am working on a brand new v4 version which should address code splitting properly.

Do you think we can just insert it to the head ? And resolve once loaded ?

I'm not qualified to provide technical suggestions, but my use case is with Lit-element (former Polymer, a.k.a. web components) + Redux + Redux-saga, as well as legacy jQuery code. My app's lean loader is to lazy-load code for components, sagas and store-related definitions, with the root component then assembling everything via dependency injection. Dynamic loading of CDN dependencies isn't critical, but nice for consistency.
Insert a CDN-sourced script tag to the head, with an onload event that resolves the import promise, like in here ? Why not, and perhaps would bypass the aforementioned XHR CORS problem. No idea about exposed objects because I am not clear how module systems work.

@hollowcat can you please confirm if the issue still occurs with<EMAIL_ADDRESS>Also see here for info on major changes

@charsleysa
I've just updated to next.401 and modified my fuse.js as written (replaced output with bundles as an argument to runDev, no other changes from this example).
It does compile, but gives TypeError: Object.assign(...) is not a function when opened in the browser, generated at the point of first import of LitElement. My config has the dependencies: { include: [ 'tslib' ] } line, my tsconfig.js has importHelpers: true, and it previously worked.
So I can't report on the CDN imports issue until I figure out how to just make it work again.

Could you reproduce it ?

You don't need to add tslib anymore btw, we don't use Typescript anymore

With only this code in my entrypoint index.ts,
(async () => {
    await import("https://unpkg.com/redux@4.0.1/dist/redux.min.js"); // works in 164
    await import("https://cdn.jsdelivr.net/npm/redux@4.0.1/dist/redux.min.js");
    await import("https://cdnjs.cloudflare.com/ajax/libs/redux/4.0.1/redux.min.js");
})();

next.164 throws as described initially, while next.403 just throws Uncaught (in promise) Error: Module<EMAIL_ADDRESS>was not found any way.
Does the shift to another parser affect compatibility with Lit-element which expects TS?
How to fix the Object.assign is not a function errors?

Are you using IE7 or something? Can you add a polyfill ?
Also did you previously use any ts transformers ? Cuz the latest version requires custom transformers, we are trying to cover the most popular cases but it will take time.
As for dynamic cdn imports I will add the support for that soon enough

Using latest FF and Chrome, no transformers or Babel, adding the polyfill from here did not help.
The Object.assign issue first appears with fusebox version alpha.269; version alpha.267 and some before it throw a different error, File.js does not provide a module; versions between that and next.164 generate bundles with various syntax errors.

@hollowcat I've been able to successfully run the fuse-box react example project v4 branch.
The only changes required were:

delete the package-lock.json file
update fuse.ts as the watch option has been renamed to watcher
update package.json and change fuse-box to 4.0.0-next.403

If you are still having issues running that project please open a new issue as this issue will be specifically for dynamic url imports.

Closed due to inactivity.


opentrons_24_tuberack_nest_* definitions are wrong

Overview
The opentrons_24_tuberack_nest_1.5ml_screwcap labware appears to have a problem with both its x-spacing and y-spacing.
The tip will correctly be positioned in A1. However, in D6, the position is noticeably off. Very sloppily measuring with calipers, I'd say the tip is 2 mm too close to the front of the robot and 3 mm too far to the left.
The same tube rack with different tubes, opentrons_24_tuberack_eppendorf_2ml_safelock_snapcap, does not have this issue.
Reproducing
This is an APIv2 demo script, but the issue applies equally to APIv1. I ran this without any labware calibration.
from opentrons import protocol_api

metadata = {
    'protocolName': 'Tube rack offset test',
    'author': 'Max Marrone',
}

def run(protocol: protocol_api.ProtocolContext):
    tip_rack = protocol.load_labware('opentrons_96_tiprack_300ul', '1')
    tube_rack_1 = protocol.load_labware('opentrons_24_tuberack_nest_1.5ml_screwcap', '7') # Shows problem.
    tube_rack_2 = protocol.load_labware('opentrons_24_tuberack_eppendorf_2ml_safelock_snapcap', '8') # Does not show problem.

    pipette = protocol.load_instrument('p300_single', 'left', tip_racks=[tip_rack])

    pipette.pick_up_tip()

    for tube_rack in [tube_rack_1, tube_rack_2]:
        pipette.move_to(tube_rack.well("A1").top())
        context.comment("Should be centered in A1.")
        context.pause()
        pipette.move_to(tube_rack.well("D6").top())
        context.comment("Should be centered in D6.")
        context.pause()

Other notes

I haven't tested to see if the height of the labware is correct.
I haven't tested any of the other opentrons_24_tuberack_* labware.

I just did some additional investigation. It looks like all 24 tuberack NEST definitions added by #3916 were generated with their X and Y spacing swapped. This is easily noticeable from looking at the numbers on the labware library; I don't know how we missed this
Moving forward:

I'm going to add an automatic test to ensure X + Y consistency among our modular tuberack definitions
We will ensure that 100% of labware definitions merged have first and last wells tested

This has been the procedure in a lot of cases but clearly we didn't codify it hard enough


Feature request: Databindable read-only properties on Node

It would be really good to be able to databind to the absolute screenspace position of a node post layout, for instance to be able to draw lines between elements. Is it a horrible no-no to have readonly general properties like these?

Absolute screenspace is an issue since it's very costly to determine when it updates. It involves a world transform listener. We have these, but they have a cost across all nodes in the app. I'm not really in favour of exposing this functionality too much to the user level due to this.
If you can give some clearer use-cases though I can probalby some up with functions that would help in the more limited situation. You usually don't wan't screen space, but some limited local space.


[Text Translation] Updating to latest TypeSpec

Updated names of properties according to the GA review comments.
Update GetLanguages to GetSupportedLanguages.
Allow to create TextTranslationClien without any credentials to support Text Translation scenario.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.Translation.Text


model.edge.add() starts with existing edges starts with edge_id=1, causing unique validation error

Below an example on how I add new edges using the add-API in current main (pulled 06-09-2024). Adding edges will add edge_id=1, going up one int every time I edge. Problem is, edge_id 0 till 1956 are already used causing a unique validation error on the edge_id column while writing

Fixed in #1818


Create DockerHub repository

I created a repository here: https://hub.docker.com/repository/docker/fairsoftware/fairtally


Unexpected crash when copying files from a window with a preview pane

Microsoft PowerToys version
0.55.2
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce
I was using CTRL-C to copy some file from a Windows Explorer window that has a file preview enabled.  I'm not sure if I didn't hit CTRL-C exactly right but I got a Microsoft.NET Unhandled Exception Error:
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.PowerToys.PreviewHandler.Monaco.MonacoPreviewHandlerControl.<>c__DisplayClass6_1`1.<b__3>d.MoveNext()
--- End of stack trace from previous location ---
at System.Threading.Tasks.Task.<>c.b__140_0(Object state)
ExceptionError.txt
PowerToysReport_2022-02-16-15-00-17.zip

✔ Expected Behavior
No crash when using CTRL-C after highlighting files :-)
❌ Actual Behavior
Crash when trying to copy.  Might have not had my finger exactly on the C key
Other Software
No response

Crash when trying to copy. Might have not had my finger exactly on the C key

cc: @Aaron-Junker
Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software..

Duplicate of #16081


Design distributed cache

Watch this https://www.youtube.com/watch?v=iuqZvajTOyA&ab_channel=SystemDesignInterview, and get it merged into https://github.com/danniel1205/tech-notes/tree/master/system-design/topics/caching

Done

2668e354b4b8e48dfe1315b6dbbba427de0a8d4c


Unexpected crash with exit code 1 when creating the PipelineLayout object

Working code produces the following output, which is correct and expected:
https://hastebin.com/lebivamugo
While when I uncomment a function, the program hangs on the last line of output and after about a minute unexpectedly exits with exit code 1. Output log:
https://hastebin.com/cuxececayi
The program hangs after printing out
ObjectTracker information: OBJ[0x1e] : CREATE PipelineLayout object 0x15
and exits before getting to printing out
ObjectTracker information: OBJ[0x1f] : CREATE Pipeline object 0x16

Did you try enabling the validation layers, in case it reports something?
The most probable causes are a hardware limit that is not respected (vulkano doesn't check that yet), or a driver bug.

Yes, I am enabling the validation layers, it just crashes without reporting anything. https://github.com/Limeth/vulkanscratch/blob/master/src/main.rs#L125

For the record I tried running your code and got a stack overflow inside std::ptr::write when writing the data to upload to the immutable buffer.

That's odd, I don't know what to make of that. Another hardware limitation, I guess.

Does it happen right after ObjectTracker information: OBJ[0x1e] : CREATE PipelineLayout object 0x15, or do you think it's another issue?

Maybe it's a legitimate stack overflow because there's too much data on the stack?

ObjectTracker information: OBJ_STAT Destroy CommandPool obj 0x9 (10 total objs remain & 0 CommandPool objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x6 (9 total objs remain & 5 Buffer objs).
ObjectTracker information: OBJ[0xf] : CREATE Buffer object 0xa
ObjectTracker information: OBJ[0x10] : CREATE ShaderModule object 0xb
ObjectTracker information: OBJ[0x11] : CREATE DescriptorSetLayout object 0xc
ObjectTracker information: OBJ[0x12] : CREATE PipelineLayout object 0xd
Driver error: Compute info
(0) : fatal error C9999: *** exception during compilation ***
ParameterValidation warning: vkCreateComputePipelines: returned VK_ERROR_INVALID_SHADER_NV, indicating that one or more shaders failed to compile or link
thread 'main' panicked at 'Vulkan function returned VK_ERROR_INVALID_SHADER_NV', C:\Users\Pierre.cargo\git\checkouts\vulkano-cb672043253a6e8d\c40954c\vulkano\src\lib.rs:23
3:39
note: Run with RUST_BACKTRACE=1 for a backtrace.
ObjectTracker information: OBJ_STAT Destroy PipelineLayout obj 0xd (12 total objs remain & 0 PipelineLayout objs).
ObjectTracker information: OBJ_STAT Destroy DescriptorSetLayout obj 0xc (11 total objs remain & 0 DescriptorSetLayout objs).
ObjectTracker information: OBJ_STAT Destroy ShaderModule obj 0xb (10 total objs remain & 0 ShaderModule objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0xa (9 total objs remain & 5 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x8 (8 total objs remain & 4 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x5 (7 total objs remain & 3 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x4 (6 total objs remain & 2 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x3 (5 total objs remain & 1 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy Buffer obj 0x1 (4 total objs remain & 0 Buffer objs).
ObjectTracker information: OBJ_STAT Destroy DeviceMemory obj 0x7 (3 total objs remain & 1 DeviceMemory objs).
ObjectTracker information: OBJ_STAT Destroy DeviceMemory obj 0x2 (2 total objs remain & 0 DeviceMemory objs).
ObjectTracker information: OBJ_STAT Destroy Device obj 0x269847a0020 (1 total objs remain & 0 Device objs).
ObjectTracker information: OBJ_STAT Destroy Queue obj 0x26983f2f150 (0 total objs remain & 0 Queue objs).
loader debug: Unloading layer library C:\WINDOWS\system32.\nvoglv64.dll
loader debug: Unloading layer library D:\Logiciels\VulkanSDK\<IP_ADDRESS>\Bin.\VkLayer_threading.dll
loader debug: Unloading layer library D:\Logiciels\VulkanSDK\<IP_ADDRESS>\Bin.\VkLayer_parameter_validation.dll
loader debug: Unloading layer library D:\Logiciels\VulkanSDK\<IP_ADDRESS>\Bin.\VkLayer_object_tracker.dll
loader debug: Unloading layer library D:\Logiciels\VulkanSDK\<IP_ADDRESS>\Bin.\VkLayer_core_validation.dll
loader debug: Unloading layer library D:\Logiciels\VulkanSDK\<IP_ADDRESS>\Bin.\VkLayer_unique_objects.dll
error: process didn't exit successfully: target\debug\vulkanscratch.exe (exit code: 101)

The interesting part is unfortunately not helpful:

(0) : fatal error C9999: *** exception during compilation ***

I guess your best bet is to report this to nVidia: https://devtalk.nvidia.com/default/board/166/vulkan/

Will do, thank you.


The last two sentences are unclear

Hello,
The last two sentences are unclear and seem to be out of order.
"If the target network chosen is the failover vnet” and 2nd point to say “If the target network chosen is different from the failover vnet but has the same subnet range as failover vnet”
Can we update this to make this statement more clear?

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

ID: dbc136fa-e90c-108a-fada-68e8621e6b3e
Version Independent ID: 605b1a94-8bef-f7f3-5eaa-ec8b5bb8fc4a
Content: Map virtual networks between two Azure regions in Azure Site Recovery
Content Source: articles/site-recovery/azure-to-azure-network-mapping.md
Service: site-recovery
GitHub Login: @mayurigupta13
Microsoft Alias: mayg

@mikedeatworld Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Last two lines are appended by mistake. They are part of the table and explained in details. Thank you for the feedback.
#please-close


Fixes nemofw doc links

PR is for review, but afterwards, the git tag named v0.3.0.trtllm will need to be updated

closing since the r0.3.0.trtllm tag is updated


[image_picker] Implement getMedia for picking videos and images simultaneously on iOS.

This PR implements the getMedia method added to the platform interface in #4675 on iOS, allowing users to pick both images and videos from the gallery simultaneously. It superses #4676 and will remain in draft mode until the changes to the platform interface have been merged and published, so that this PR may be updated.
As of right now, this PR still lacks some tests which I will provide later.
Relevant issue:

flutter/flutter#89159

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@BeMacized Is this still on your radar?

@BeMacized is this still on your radar?
See also: https://github.com/flutter/plugins/pull/5979

Oops, I see I already asked that once. I'm going to close this PR for now to get it off our review queue, but please don't hesitate to submit a new PR if you have the time to get back to it. In the meantime I'll mention this PR on the issue so that anyone else who wants to pick it up can do so. Thanks again for your contribution!


Error in production, but not in local

When I try to publish my site in production, I get this error:
str_starts_with(): Argument #1 ($haystack) must be of type string, bool given
from this file, line 51:
/site/plugins/kirby-vite/packages/kirby-vite/Vite.php
 if (str_starts_with($fullPath, $rootPath)) {
    return ltrim(substr($fullPath, strlen($rootPath)), DIRECTORY_SEPARATOR);
  }

Any idea what it could be?

Can you share your setup with a minimal repository?
There used to be a similar issue but I forgot what caused it 🙈

Ah I found it: maybe issue #40 can help you

Thanks for taking a look. I realised the website is looking for /site/config/vite.config.php but that file is in the .gitignore. And the error I posted above is caused when I stop ignoring that file and pushing it to the server. I also realised I can't use Node on my remote server, so no npm install available there. I guess that's the problem? If so, any idea how to bypass it?

The file is git ignored by purpose, because it its auto-generated by the kirby-vite plugin. (I don't like to comit any files that are auto-generated or installed, like node_modules and composer's vendor) because you can recrate these files any time, so there is no need for them to end up in version control like git. But of course you have to upload the file.
I don't know how you deploy, but if you use git, you have to run npm install, npm run build and composer install on the server. If you can't use node then yes, you have to remove the auto-generated files from .gitignore. For simple website I also use a cheap shared hosting webspace without node and to deploy these website I use rsync or lftp. This way I still can ignore all auto-generated files from git, but I upload them to the server never the less. I also made a simple tool to help with lftp: very-simple-deploy, I you have ssh access you could also use rploy. Here is an example setup of how I use my lftp tool with Kirby and Vite :)

amazing, many thanks for your reply!

fantastic, thanks a lot for your work!


Custom Commands: If statements breaking

Problem with if statements
Steps to reproduce:
Not really known
Example:
{{if ne (len .Args) 3}}
	You must enter **2** numbers to roll!
{{else}}
	{{$a := toInt64 (index .Args 1)}}
	{{$b := toInt64 (index .Args 2)}}
	{{if eq $a $b}}
		The numbers **cannot be equal**, or the values are not valid!
	{{else if or (gt $a 99) (gt $b 99) }}
		The numbers **cannot be greater than 99**!
	{{else}}
		{{if gt ($a) ($b)}}
			{{$c := randInt $a $b}}
		{{else if lt ($a) ($b)}}
			{{$c := randInt $b $a}}
		{{end}}
		**{{.User.Username}}**, you have rolled a {{$c}}.
	{{end}}
{{end}}

Expected output:

Command running correctly and getting the roll output.

Actual output:

No output, and $c is not defined.

What could the problem caused by:
Maybe the method the bot is using to convert the custom commands is not expecting these type of statements.
Hope we'll get a fix and it won't take too long or too much to fix it!
Thanks for all!

Not a issue, remove please.

Yes, indeed, figured out that {{end}} clears the variable out of the memory

(I like necroposting) @casKd-dev close this tbh

Close #221

Close #221


[Feature] dbt-Bigquery retry for DML job BQ API errors (503 errors, etc. )

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Background
Currently, dbt-bigquery profile.yml has two configurations: Timeouts and Retries
We at Semios have been using dbt extensively to run high-frequency data pipelines on BigQuery (some of them run every 10 minutes). Because of the strict SLA requirement, we require more granular control on BigQuery timeout and retry mechanism to minimize the intermittent query failures and its impact to our pipeline.
We found that the existing configs are not enough to mitigate all intermittent query failures. for example, the Deadline of 120.0s exceeded 503 errors raised by BigQuery JobInsert API that occurred from time to time and impacted several dbt-BigQuery users in the dbt community.
We would like to suggest a more comprehensive BigQuery retry config to minimize all these errors.
Technical Context
Before I propose the suggestion, let me explain how BigQuery query works and how we would like to retry.
How BigQuery query works in dbt
at the core, BigQuery query is made by two steps in dbt
    def _query_and_results(self, client, sql, conn, job_params, timeout=None):
        """Query the client and wait for results."""
        # Cannot reuse job_config if destination is set and ddl is used
        job_config = google.cloud.bigquery.QueryJobConfig(**job_params)    # <--- Step 1
        query_job = client.query(sql, job_config=job_config)               # <--- Step 2
        iterator = query_job.result(timeout=timeout)
        return query_job, iterator

In the first step, client.query() submits a query to BQ JobInsert API server, when succeeded, BQ server creates a new BigQuery query job, and return the query job id back to the client as part ofquery_job object. This step shall be very quick, normally under a few seconds. however, in some rare cases, it would take much longer and might even up to 4 minutes according to the BigQuery engineering team.
In the 2nd step, query_job.result() await for the BigQuery executing (running) the query and return the results back to the client as an iterator. depending on the complexity of the query, this step could takes long, from tens of seconds to tens of minutes.
how dbt currently retries BigQuery queries
Currently, The dbt retry config is used to set the retries of the overall _query_and_results. the dbt timeout config is used only to control step 2, query_job.result(timeout=timeout). These configs make sense on its own.
However, you might notice that there is no control over the timeout of query() in step 1, other than relying on its [default value] (https://github.com/googleapis/python-bigquery/blob/1762e5bd98ab089abf65a0d146234c77217b8dbe/google/cloud/bigquery/client.py#L3193).  When BQ JobInsert API sharding cluster is unstable. it could take up to 4 minutes to create the query job id in some rare cases. Because the query() had a client-side [default deadline of 120s](DEFAULT_RETRY = retry.Retry(predicate=_should_retry)), the client quits at 120s while server side is still waiting for the job creation. That's why several dbt community members had experienced the [Deadline of 120.0s exceeded errors (https://getdbt.slack.com/archives/C99SNSRTK/p1627926805026400).
BQ team has since patched the query() to make a client-side [default deadline of 10 mins](DEFAULT_RETRY = retry.Retry(predicate=_should_retry, deadline=600.0). It means by default, query() could take up to 4 minutes to make one attempt to create a new job id. If it fails, the client-side could have up to 10 minutes to retry. This would work fine for users who don't have stringent timing requirements. They won't mind waiting for 10 minutes to create a new BQ job ID and then waiting for another 10 minutes to get the result.
Unfortunately, it doesn't work for us. In situations like this, we would rather fail faster and try again. It shall not take more than 30 seconds to create a new job id. if it takes too long, we would rather let the query() timeout and fail, so that we could retry it again.
the Proposed Solution
In order to gain fine control of the timeout mechanism of step 1 and step 2, we would like to propose the following 4 dbt configs
job_creation_timeout_seconds     # specific for initiate BQ job, to control the timeout of step 1, query()
job_execution_timeout_seconds    # specific for awaiting job result, to control the timeout of step 2, result()

job_retry_deadline_seconds       # to control the overal query, retry_deadline of _query_and_results()
job_retries                      # to control the overall query, retries of _query_and_results()

For example, we could set the configs below to fail faster on the step of BQ job creation, while allowing queries with long-running results.
job_creation_timeout_seconds=30
job_execution_timeout_seconds=1200
job_retry_deadline_seconds=1500
job_retries=3

These settings would allow us to control the timeout behaviors of step 1 and step 2 on their own, hence maximizing our chances to mitigate different kinds of intermittent errors.
NOTE:
job_execution_timeout_seconds is the renaming of the current timeout config.
job_retries is the renaming of the current retries config.
Describe alternatives you've considered
Currently, we have to override the dbt-core code to allow the query() to fail faster and retry, and to mitigate the 503 error.
Who will this benefit?
the dbt-bigquery users who would need more fine control of BigQuery query behaviors
Are you interested in contributing this feature?
yes
Anything else?
this issue has been discussed by several dbt community members in slack
https://getdbt.slack.com/archives/C99SNSRTK/p1627926805026400

@jtcohen6,
thank you. your suggestions sound good.
Just a note,  we need to also make sure we use google-bigquery version 2.26 or above to make this work.

I will take the first stab at this issue.

hello @jtcohen6,
I submit the first draft of the PR. I am going to add some tests later. It's my first time contributing. I appreciate any feedback and suggestions for the next step.


[Feature]: Ordering of results should not be biased towards mappings

Similar Issues

[X] Before filing, I have searched for similar issues.

Description
Sharing the following example (where I have typed comm and wanted to find :Comment):

Mappings take priority over Commands, even though I would argue the 4th result may actually be the best result. For my current usage (everything is a command now) I actually search for the command itself rather than the command description.
Interested to get your thoughts on this.

So, the issue isn't necessarily that it's biased towards mapping, it's that when using vim.ui.select() we don't have much/any control over the sort order, other than the initial sort order (before you've typed any query).
Technically those first 3 items would have the same matching score, since you typed comm and they all contain comm, though in different locations.
The only way to fix this would be with user config, providing a custom sorter, e.g. if you're using dressing.nvim, providing a custom sorter to dressing.nvim.
See: #64
I'm not sure how exactly the sorter would be implemented, I haven't looked at that issue in a while, but I can try to take another look soon.
The solution will essentially be for legendary.nvim to provide some sort of generic sorting function which can then be used in user config to provide custom sorters to your chosen vim.ui.select() implementer (e.g. dressing.nvim).

See also: https://github.com/stevearc/dressing.nvim/issues/22

Maybe it would be worth just creating a first-class Telescope picker, since I'm guessing that's what the vast majority of users use. That way we'd have more fine-grained control over how it works with Telescope.

Copying some context from #64, the original idea there was also to make it so that user-defined items appear before built-in items.


Don't show not-allowed cursor on valid drop targets.

This is a fix proposal for my issue #28.

Thanks!


for the blind who made the map

for your kind information whoever made that map. look for the world map again , you cut the Jammu and Kashmir from the India map and included it to Pakistan and China. please do correct it

This is a geopolitical issue[1] MapSCII as an OSM[2] client can't address.
Additionally, MapSCII currently uses the latest available, outdated OSM2Vectortiles world tileset until an envisioned adaption to its successor OpenMapTiles is achieved.
[1] https://www.swp-berlin.org/publications/products/comments/2020C52_Kashmir.pdf
[2] https://www.openstreetmap.org/


new image for community curation feed

To rotate with the word cloud
in the drop box, called "papers curated"

I've added that image to the main page.

It was a 'colour pop' to give a bit of definition when embedded in the white page, but you can remove it it looks rubbish!

It would have been better if it was closer to the graph colour, but it was a 'default slide format in google slides...

I made a new one with the green not so garish

It looks like this after scaling:

I think it would work OK as a 'teaser' bet maybe we need to make the complete graph available via a link?
https://curation.pombase.org/pombe/stats/annotation

I'll also redo the key  so it's  larger and in the body of the graph....the "key" is key.....
I'll also replace the years by 5 year interval markers...

I think it would work OK as a 'teaser' bet maybe we need to make the complete graph available via a link?

Easy enough to do.  Where should the link go?  We could make the image a link.

I've updated the image and set modified the config so that the images don't rotate.
It will be visible tomorrow.

It will be visible tomorrow.

The new image is available now.  I think I might have cropped it too much.  Let me know what you think.

Is it possible to only have one image in the rotation, but the archive to still be visible (in this instance, but we might   sometimes want to phase out  older front page images but still keep them in the archive....

phase out older front page images but still keep them in the archive....

We could do but I think having an archive of images would be strange as the context would be missing.  Unless we put a column of images on the left or right of this page?: https://www.pombase.org/reference_list/community

we could label them  there was a batch at the top under "current rotation"
and then  the rest under "archive" ?
I think it would be nice to see the old ones , or those which are not currently rotating. If we have a focus on a particular thing (like community curation), we might want to 'freeze' an image on the front page for a week......


Add an option to download the third party addons

Useless since ppl are going to fork this and integrate their own marketplace!


Imagefactory: TinMan

Added ability to pass in overrides for oz configurations in the
format of a json/dict string. Example:

--parameter oz_overrides "{'libvirt': {'memory': 4096, 'image_type': 'kvm', 'cpus': 2}}"
Added python-simplejson Requires to imagefactory-plugins.spec.in
imgfac/FactoryUtils.py

Added the check_qcow_size function into this common place.

imagefactory_plugins/vSphere/vSphere.py

Now checks if "input" image is raw or qcow; if qcow2, it
converts to raw and passes the new raw image as the input
for the vSphere conversion

imagefactory_plugins/OpenStack/OpenStack.py

Remove the check_qcow_size def, added import

imagefactory_plugins/ovfcommon/ovfcommon.py

Remove the check_qcow_size def, added import

Committed in a modified form in 0a728a6281714ead9548834f8803eaf36b831d9f
Closing


azurite 3.12.0: No connection could be made because the target machine actively refused it (<IP_ADDRESS>:50210)

Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
3.12.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v12.16.2
What problem was encountered?
We use azurite in our unit tests, after updating to 3.12.0 tests started to fail with this error:
Error Message:
System.AggregateException : Retry failed after 6 tries. (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)) (No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210))
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> Azure.RequestFailedException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
----> System.Net.Http.HttpRequestException : No connection could be made because the target machine actively refused it. (<IP_ADDRESS>:50210)
----> System.Net.Sockets.SocketException : No connection could be made because the target machine actively refused it.
Steps to reproduce the issue?

upgrade to 3.12.0
run tests

Have you found a mitigation/solution?
Pin version to 3.11.0

Hi,
I notice that you are trying to connect to a non-standard tcp port:
<IP_ADDRESS>:50210

Could you perhaps share a little more information about how your tests are configured?
Thanks!

We start Azurite from C# using the following parameters <azurite> --oauth basic -l <tempdirectory> --blobPort 0 --queuePort 0 --cert cert.pem --key cert.pem --skipApiVersionCheck. If I remember correctly this will make Azurite pick the next free port. Our tests can run in parallel so we can have multiple Azurite processes running side by side each on a separate set of ports and using a separate temp directory.

As the latest release includes table API, you might need to add --tablePort 0 to your configuration, as otherwise multiple instances of Azurite will conflict.

Thanks @edwin-huber , adding --tablePort 0 fixed it.


Extract image retrieval logic from collection slide creation function

Obtaining the correct image blob to add into a slide is currently handled by the slide creation function. It should be separated to reduce complexity.

Moved to Facades for now


new code updated on kubeless-ui  doesn't take effect

got this bug when try to change existing code on kubeless-ui.
For example:

create a new python2.7 function on kubeless-ui.
it will automatically generate a simple "hello world" code.
now if I change this code, to make it say "hello 123", and save it, then click on "run function", it will still show result "hello world".

Although I can see function got changed if I do "kubectl get function -o yaml", the result has no changes at all.
the result only changes when I manually delete function pod, which will trigger a recreation of that pod. I think this is due to recreation of a function pod reloads function scripts.
suggestions: automatically kill old pod if user changes and saves a script on kubeless-ui

Indeed, the checksum is not properly updated so it doesn't trigger the rolling update.

Should be fixed with #61 . Let us know if you find any other issue!


how to make a preview editor permanent w/o editing or mouse?

VSCode Version: Code 1.3.1 (e6b4afa53e9c0f54edef1673de9001e9f0f547ae, 2016-07-12T13:31:10.994Z)
OS Version: Darwin x64 15.5.0

Go to File opens a preview editor per default, which is fine, but, how do I keep a tab open without having to double click it, edit its content or move it to another group?
Maybe it's a good idea to have:

a command to make a preview editor permanent
some modifier key for the Go to File dialogue to switch the default open mode (e.g. shift+enter to open permanently when workbench.editor.enablePreviewFromQuickOpen is true and vice versa).

Ok, just found out that there's workbench.action.keepEditor already bound to cmd+k enter.
Closing this.


Improvement/add weak crypto

Adds reporting for weak crypto (per BOD 18-01)

Tested by myself and @jsf9k


why  duplicate order id - can match, but can not place

Hi,  i have a question that whey duplicate order id - can match, but can not place?
In my mind, duplicate order id neither can mach nor can place

Hi
Beacuse unique orderId should be assigned externally, it should never happen.
It just a performance tradeoff here - why check order uniquness if it is not really needed unless we actually want to place order into the order book.


✨ Implement a scoped committer

Summary
This is useful when trying to commit changes and patch a resource that is scoped.
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>Related issue(s)
Fixes #

/retest-required


10/25 Publish

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/overview/azure/activedirectory.md
:white_check_mark:Succeeded
View

api/overview/azure/appservice.md
:white_check_mark:Succeeded
View

api/overview/azure/billing.md
:white_check_mark:Succeeded
View

api/overview/azure/cdn.md
:white_check_mark:Succeeded
View

api/overview/azure/cosmosdb.md
:white_check_mark:Succeeded
View

api/overview/azure/data-lake-analytics.md
:white_check_mark:Succeeded
View

api/overview/azure/data-lake-store.md
:white_check_mark:Succeeded
View

api/overview/azure/mysql.md
:white_check_mark:Succeeded
View

api/overview/azure/postgresql.md
:white_check_mark:Succeeded
View

api/overview/azure/recovery-services.md
:white_check_mark:Succeeded
View

api/overview/azure/redis-cache.md
:white_check_mark:Succeeded
View

api/overview/azure/resource-manager.md
:white_check_mark:Succeeded
View

api/overview/azure/search.md
:white_check_mark:Succeeded
View

api/overview/azure/service-bus-relay.md
:white_check_mark:Succeeded
View

api/overview/azure/service-fabric.md
:white_check_mark:Succeeded
View

api/overview/azure/sql.md
:white_check_mark:Succeeded
View

api/overview/azure/storage.md
:white_check_mark:Succeeded
View

api/overview/azure/traffic-manager.md
:white_check_mark:Succeeded
View

api/overview/azure/virtualmachines.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/TOC.yml
:white_check_mark:Succeeded
View

docs-ref-conceptual/dotnet-quickstart-vs.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/dotnet-sdk-azure-authenticate.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/dotnet-sdk-azure-get-started.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/dotnet-sdk-azure-sample-readme.md
:white_check_mark:Succeeded
View

docs-ref-conceptual/index.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


refer to remote to seed volume

it should be possible to declaratively define a defined starting point for a volume, which dm would pull on demand
in docker compose (volume options) and kube yaml (PVC volume options?), e.g. initialVolumePull
this could be in the form dothub.com/username/dot[@branch[:commit]] or something similar

relates: https://github.com/dotmesh-io/dm-linuxkit
could be named "from" instead of "seed"?

Rather than having it as a volume opt, it may or may not be desirable to copy the docker image semantics, where the remote could be encoded in the name of the image

What would that look like, practically? How is it different from dothub.com/username/dot[@branch[:commit]]?

"origin" and "source" are good words, too.
@deitch : The syntax is up for debate, but perhaps whereas:
docker run -v myapp.mysql:/var/lib/mysql ...

which would start off with a blank filesystem if myapp.mysql didn't already exist, we'd have:
docker run -v myapp$hub/production@branch.mysql:/var/lib/mysql ...

...to clone production from the pre-configured remote hub if myapp doesn't exist, then mount subdot mysql from branch branch.

@alaric-datamesh that all makes sense. How is it different than the original proposal?

The original proposal was that we provided a "docker volume option", which I don't know the syntax for.
In either case, the convention we have with Kubernetes is to use PVC annotations like dotmeshNamespace - we'd just add another, perhaps dotmeshSeed set to something like hub/production; or dotmeshSeedRemote set to hub and dotmeshSeedDot set to production.

From a usage perspective, would be really helpful if, before we actually implement, we could write up here how it would be consumed, i.e. sample config files for docker and/or kube (and possibly dm cli), so we can understand the customer usage implications.
Thanks for the patience explaining @alaric-datamesh !

This depends on server side remotes, as does https://github.com/dotmesh-io/dotmesh/issues/370
When we start working on either of these, let's break that out into a separate issue and track it as a dependency.

Closing until we decide to do it as a roadmap item: https://github.com/dotmesh-io/roadmap/issues/40

Re-open as we need to do it for https://github.com/dotmesh-io/frontend-ng/issues/108


Fix the vocab layout sidebar running away

Concept editor sidebar tends to run away below on small screens. This can confuse users, fix it in place with CSS even if it means side scrolling.
For bonus an animated popout sidebar could be ideal for mobile UX, but sidescrolling is still better.

Closing, fixed. Open a different issue to support animated popout sidebar on mobile


use v3 namespaces api

The pr uses the new api/automation-hub/pulp/api/v3/pulp_ansible/namespaces/ in place of the old /api/automation-hub/_ui/v1/namespaces/ one.
Unfortunately, though the api at http://localhost:5001/api/automation-hub/pulp/api/v3/pulp_ansible/namespaces/ works fine, the UI is having trouble reading it.
I am using:
https://github.com/ansible/galaxy_ng/pull/1705
https://github.com/pulp/pulp_ansible/pull/1437
Thanks for a quick review:)

Looks similar to https://github.com/ansible/ansible-ui/pull/657 .. did you want to close this one or are they complementary?

@himdel yeah I guess I can close this one... I'm breaking it into smaller chunks in separate prs.


Final renaming

Functions:
calculateLoglikFromVariables -> logLikehood
calculatePerplexityWithResampling -> resamplePerplexity
calculatePerplexity -> perplexity
Variables in returned from factorizeMatrix:
cell.states -> cell
cell.population.states -> cell.population
gene.states -> module
sample.states -> sample

Fixed in #346


Remove an unused variable

@jvoisin Thank you for your patience! 🙏🏼
It‘s been a while since I had free time to focus more on Nord, and my open source projects in general, and invest time in this issue due to work-life balance.
I recently published the first “Northern Post — The state and roadmap of Nord“ announcement which includes all details about the plans and future of the Nord project, including the goal of catching up with the backlog. This issue is part of the backlog and therefore I want to triage and process it to get one step closer to a “clean state“. Read the announcement about reaching the “clean“ contribution triage state in Nord‘s discussions for more details about the goal.
Therefore it has been added to the queue in the central and single-source-of-truth project board that is also described in more detail in the roadmap announcement.

@jvoisin Thanks for your contribution 🚀
The pull request has been added to the queue and the review will be planned for the next iterations!


Prefer Northstar ID whenever possible and cover some bases, huzzah!

What's this PR do?
This PR does a few updates to fix up an issue occurring on Staging. It defaults to referring to the Northstar ID for a user when working with their record in Phoenix and when querying Northstar for more information on them. (see background context below!)
How should this be reviewed?
tell us, how can we review, to test that this works
Any background context you want to provide?
When using OpenID to register as a new user via Northstar, Northstar creates a new record in its system and then passes the information over to Phoenix to then create a new Drupal user in its system and associating the NS ID created on the Northstar side. However, we don't then go back and tell Northstar what the drupal_id for this new user is, which means that all the functions that later go grab Northstar info for this user, and ask to find the user using their drupal_id will return null because that id was never passed into the NS system.
Relevant tickets
Fixes # https://github.com/DoSomething/northstar/issues/458
Checklist

[ ] Tested on staging.
[ ] Pinged a PM if this is a larger PR that would benefit from some additional testing love

@DFurnes @angaither
cc: @jessleenyc

 Users registered via OpenID Connect flow do not have drupal_id set on their Northstar profile.


Missing toml in asset_stats

Code: XIM
Issuing  Account: GBZ35ZJRIKJGYH5PBKLKOZ5L6EXCNTO7BKIL7DAVVDFQ2ODJEEHHJXIM
There is a home domain in the accounts table but no toml in the asset_stats table.

As far as remember /assets endpoint (and home_domain) is updated when there's an operation involving the asset in the network. Updating it one account changes is not there yet: https://github.com/stellar/go/blob/master/services/horizon/internal/ingest/asset_stat.go#L43.
In short: send any operation that involves the asset (payment, offer, etc.) and it will update.

Do you mean execute an operation involving the asset from the issuing account or just in general?  XIM has had  many ops executed after the home domain was  changed:  https://stellar.expert/explorer/public/asset/XIM-GBZ35ZJRIKJGYH5PBKLKOZ5L6EXCNTO7BKIL7DAVVDFQ2ODJEEHHJXIM

I think this can be caused by https://github.com/stellar/go/pull/436 which is now blocked by https://github.com/stellar/go/issues/445 (and a fix for this: https://github.com/stellar/go/pull/446). I think this will be merged today and we will test it in testnet and master, then release a patch horizon build.

Hello istrau2
Did you manage to resolve this issue as I'm having the same????
some help would much be appreciated
thanks

The fix has been just deployed to horizon.stellar.org. Please check if it works after submitting a transaction involving the asset (it triggers stats update).

@bartek we run our own horizon. What do we have to do?

@bartekn Where can I find instructions on upgrading to the latest horizon?

A new Horizon version that includes a fix for this issue has been released: https://github.com/stellar/go/releases/tag/horizon-v0.13.0 Please read release notes carefully.


update go.mod to v46, add groups.

1. Overview
update cosmos-sdk to v0.46.9
should I update sdk version to v3?

Sorry, reviewed wrong set of changes, also not sure why it appears in my review queue. Will wait till this is marked as ready.

@xlab actually awaiting decision to ever support v46 :P , from me it is actually ready, I am using this branch as of now for pstake version update.


driver/gpio.h: No such file or directory

Hi!
I run idf.py build and get such error
hackwatch/components/twatch-lib/drivers/i2c.c:3:10: fatal error: driver/gpio.h: No such file or directory
    3 | #include "driver/gpio.h"
      |          ^~~~~~~~~~~~~~~
compilation terminated.
[2/71] Performing build step for 'bootloader'
[1/1] cd /home/reinethernal/firmware/hackw2/hackwatch/build/bootloader/esp-idf/esptool_py && /home/reinethernal/.espressif/python_env/idf5.0_py3.10_env/bin/python /home/reinethernal/esp/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x1000 /home/reinethernal/firmware/hackw2/hackwatch/build/bootloader/bootloader.bin
Bootloader binary size 0x6610 bytes. 0x9f0 bytes (9%) free.
ninja: build stopped: subcommand failed.
ninja failed with exit code 1
root@re:/home/reinethernal/firmware/hackw2/hackwatch#

I got the same issue with the current version :
esp/hackwatch/components/twatch-lib/inc/drivers/axp20x.h:47:10: fatal error: driver/gpio.h: No such file or directory
47 | #include "driver/gpio.h"
|          ^~~~~~~~~~~~~~~
compilation terminated.

Hi, currently the compilation does not work with the latest version of ESP-IDF, you have to use the commit 01d014c42def8d0c19e1ce55c07de6761e092ffa .

It looks like I made a bad choice to move from ESP-IDF version 4.4.2 to 5.0-dev, so I rolled back the code to version 4.4.2 in order to fix everything. Code should compile fine and without errors/warning with ESP-IDF 4.4.2 (latest stable).

Issue fixed, closing it.


Remove Ferdi string from default user agent

Description

It seems that most websites don't like the additional Ferdi/<version> Electron/<version> string in the user agent used by Ferdi. I propose that we remove this, to mimic what Chrome would send to websites.
This would remove the need to make recipe-specific hacks to the user agent such as in Gmail - https://github.com/getferdi/recipes/blob/1498743f99625b574b51cee061a70bf271da93b7/uncompressed/gmail/index.js#L9
Motivation and Context

Fixes https://github.com/getferdi/ferdi/issues/788 and fixes https://github.com/getferdi/ferdi/issues/790
Screenshots

Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

@vantezzen - imo, this is a breaking change - and afaik, has a bigger impact both on the number of users of Ferdi and the number of services affected per user. Can #551 be reverted and fixed in a different manner?

@vraravam I think this is more reverting of an unneeded breaking change. We constantly need to remove the changes from #551 from individual recipes as many services (like all Google Services and WhatsApp) don't work with such a "special" user agent.
Currently, we need to add the header modification code to all those recipes individually, which will be hard to maintain for future changes in Ferdi.
The number of services who actually profit from knowing that the client is Ferdi is very small, so I think it's probably better to just disable it by default and having an option to enable it for individual services.
Additionally, this change shouldn't have any breaking change for most of our users as changing the user agent of a browser is a normal change that also happens between updates of your normal browser.

This PR does not work with the 5.6.0-rc1 anymore. I pulled it in, but now neither WhatsApp, but also Slack stopped working.
So I have to choose either WhatsApp working or Slack working ...

@norbusan Thank you for reporting on this. Could you please further explain what you mean with "This PR does not work with the 5.6.0-rc1 anymore"? There is currently no 5.6.0-rc1 (there isn't even an active 5.6.0-beta.1 yet) and we haven't merged this PR either.

@vantezzen Sorry for the mix up, I meant 5.6.0-beta.1 of course. I build myself from git and added these changes myself, because before (the last package I used was some nightly...) adding this patch did make WhatsApp work again, and everything else also worked. Now, adding these changes to 5.6.0-beta.1 (tag in git) I see browser rejections in Slack.

Let's address regressions at the recipes level for now if any.
Making user agents strings available via the UI at the service settings level would come handy by now.


fix: remove legacy version of metrics-server due to vulnerability

What type of PR is this?
Removing legacy version of Metrics-server due to CVE

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

already dropped? no diff after rebase :D

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 61.973%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
2544

Relevant Lines:
4105

💛  - Coveralls


graph-node: Remove ports 8030 and 8040

Can you explain exactly why those ports should be removed from there?

Someone from community suggested me for the PR

https://discord.com/channels/438038660412342282/791444347823980604/976514563384164442

Hey @thisisommore!  I'll close this.


Simplify the font families

h1 {
  font-family: heading;
}

body {
  font-family: body;
}

code {
  font-family: monospaced;
}

https://github.com/ConciseCSS/concisecss/issues/1


the training log files

Hi, can you provide me with the training log files for the second stage of transfusion_nusc_voxel_LC and MSMDFusion_nusc_voxel_LC for my reference? Thank you!

I can not find the relevant training logs. You can provide intermediate results and I can help you to check them.

Thank you for your assistance!
I'm currently working on reproducing TransFusion. After training for 20 epochs on LiDAR, I obtained results with mAP: 0.6463 and NDS: 0.6979, which are close to the original TransFusion-L.
However, when I continued training for 6 epochs for fusion, the first epoch yielded very low results with mAP: 0.3156 and NDS: 0.2860. Is this normal?

I would like to know where the initialization weights for the 2D model come from. Have you retrained the 2D model?

It is not normal in my memory. The performance will not decrease dramatically in the second training stage. Please refer to here for the pretrained 2D backbone.

您好，您能否提供 transfusion_nusc_voxel_LC 和 MSMDFusion_nusc_voxel_LC 第二阶段的训练日志文件供我参考？谢谢！

您好，请问您这里训练第二阶段时的显卡和显存是多少呢？我这里使用了4090，显示显存不够，然后又更换成了A800,还是显存不够，我不知道是我哪里设置错误还是模型确实需要这么大的显存，您能帮我解答一下吗，谢谢。

I can not find the relevant training logs. You can provide intermediate results and I can help you to check them.

您好，请问您训练第二阶段的模型时，显卡的显存是多少呢？我这里A800 还是显示显存不够。


Initialisation does not work for me

Hi,
following configuration:

NodeRed on Raspberry PI (native) - no local browser
installed apfelstrudel today (no other alexa stuff on the same system)
create a configuration for amazon.de

Deployed , open browser from my win PC and sccessfully logged into amazon:
"Amazon Alexa Cookie successfully retrieved. You can close the browser."
but the nodes on NodeRed still shows 'uninitialized'
Thanks
J.

tried the same with a local windows installation - target address now <IP_ADDRESS>:3456 - but same result.
Is there any option to trace how the code generate/save the cookie ?
Thanks
Joerg

I can see the following debug log entries:
25 Nov 13:47:17 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Get pushed activities ... 1 entries in queue (already running: false)
25 Nov 13:47:17 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No authentication check needed (time elapsed 17962)
25 Nov 13:47:17 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Sending Request with {"host":"www.amazon.de","path":"/alexa-privacy/apd/rvh/customer-history-records?startTime=1700830037990&endTime=1701002837990&recordType=VOICE_HISTORY&maxRecordSize=3","method":"GET","timeout":10000,"headers":{}}
25 Nov 13:47:18 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Response: {"customerHistoryRecords":[],"encodedRequestToken":null,"noDataFoundWithinTimeLimit":false,"lastRecordTimestamp":null,"voiceProfileAssociatedWithPerson":false}
25 Nov 13:47:18 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity data []
25 Nov 13:47:18 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity for device G091ET10110404FA not found
25 Nov 13:47:18 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No activities from stored 1 entries found in queue (0)
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Get pushed activities ... 1 entries in queue (already running: false)
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No authentication check needed (time elapsed 20697)
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Sending Request with {"host":"www.amazon.de","path":"/alexa-privacy/apd/rvh/customer-history-records?startTime=1700830040725&endTime=1701002840725&recordType=VOICE_HISTORY&maxRecordSize=3","method":"GET","timeout":10000,"headers":{}}
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Response: {"customerHistoryRecords":[],"encodedRequestToken":null,"noDataFoundWithinTimeLimit":false,"lastRecordTimestamp":null,"voiceProfileAssociatedWithPerson":false}
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity data []
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity for device G091ET10110404FA not found
25 Nov 13:47:20 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No activities from stored 1 entries found in queue (1)
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Get pushed activities ... 1 entries in queue (already running: false)
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No authentication check needed (time elapsed 23391)
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Sending Request with {"host":"www.amazon.de","path":"/alexa-privacy/apd/rvh/customer-history-records?startTime=1700830043419&endTime=1701002843419&recordType=VOICE_HISTORY&maxRecordSize=3","method":"GET","timeout":10000,"headers":{}}
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Response: {"customerHistoryRecords":[],"encodedRequestToken":null,"noDataFoundWithinTimeLimit":false,"lastRecordTimestamp":null,"voiceProfileAssociatedWithPerson":false}
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity data []
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Activity for device G091ET10110404FA not found
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: No activities from stored 1 entries found in queue (2)
25 Nov 13:47:23 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote: Reset expected activities
25 Nov 13:49:26 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote HTTP2-PUSH: Send Ping
25 Nov 13:49:46 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote HTTP2-PUSH: Send Ping
25 Nov 13:50:00 - [debug] [alexa-remote-account:AlexaWin] Alexa-Remote HTTP2-PUSH: Send Ping
25 Nov 13:50:33 - [error] [alexa-remote-routine:ee983c40f64386d9] Account not initialised!

the same; no working,

Same here.
First I tried with a dockered version of Node-RED (running under IOTstack) and managed to open port 3456. Then I was unsure about the file the persisted data is written into (File Path parameter) but I think I got it right. Just to be sure I also used a non-dockered instance running on a RasPi. I can see that the file is read because JSON errors are shown if there is file content that is not conforming to JSON syntax.
I always get the success page after login (without as well as with 2FA) but no cookie information.
The procedure described in get_cookie.md does not work because the URL alexa.amazon.com always tells me how to open the mobile Alexa app. No radio stations to be played.
I also tried to copy the cookie information from another Amazon session and use it with the "Auth Method" parameter set to "Cookie", but the module keeps logging "please open :3456" which is strange because that method is not active then.
There is no documentation about the JSON structure in the "File Path" JSON file, and I cannot simply paste the cookie string into that file.

Same here. Use Proxmox server with Debian instance where node-red is running on a docker container.
No cookie or cookie file saved on the system...
URL alexa.amazon.de shows always the info: use the Alexa mobile app...
Please help ...

Same today, i debug it and i see some trouble in initExt method from lib/alexa-remote-ext.js
const value = await new Promise((resolve, reject) => this.init(config, (err, val) => {
	if (err) {
		// proxy status message is not the final callback call
		// it is also not an actual error
		// so we filter it out and report it our own way
		const begin = `You can try to get the cookie manually by opening http://`;
		const end = `/ with your browser.`;
		const beginIdx = err.message.indexOf(begin);
		const endIdx = err.message.indexOf(end);

		if (beginIdx !== -1 && endIdx !== -1) {
			const url = err.message.substring(begin.length, endIdx);
			proxyActiveCallback(url);
		}
		else {
			//reject(err);
		}
	}
	else {
		resolve(this.cookieData);
	}
}));

this.init callback is called twice, but promise is registered only one time.
The first time reject is call to update node status in nodered ui to say: please connect to amazon on http://localhost:3456.
Then after connection this.init is called a second time, but promise is already consumed in error, so nothing happen.
To test theory i comment the reject (so node message is broken) but promise can be triggered without error and code continue, my nodes are ready and i can make alexa speak but It seems cookie is not saved to flow context and not save to file.
@DanPatten i see you do some things on it, have you an idea to fix it in a better way ?

Ok i made a pull request with the right fix: https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/pull/166

made an update to my node-red installation and restarted node-red.
If I open http://:3456 it shows the following screen:


Unit test failure - test_post_submit

The following test_post_submit unit test fails on the master branch:
======================================================================
FAIL: test_post_submit (app.tests.SubmitNewLicenseViewsTestCase)
POST Request for submit a new license
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/spdx-online-tools/spdx-online-tools/src/app/tests.py", line 1229, in test_post_submit
    self.assertEqual(resp.status_code,200)
AssertionError: 500 != 200

@goneall I'm getting a different error in my machine.

FYI, All the test cases that are failing are the once that were skipped because they require github credentials which is why these tests were not tested. I will take a look at it.

FYI, All the test cases that are failing are the once that were skipped because they require github credentials which is why these tests were not tested. I will take a look at it.

I added the credentials to Git a couple weeks back - this may have exposed an issue that was introduced some time ago.  The errors are coming from the automated Git actions on checkin.
@Ugtan Thanks for looking into the issue.

How i can contribute
please guide me
I like to solve this problem

Hi @goneall can you clarify the difference between test_post_submit and test_submit_new_license

@BanulaKumarage Probably a better question for @rtgdk - I'm not as familiar with the unit test code

Hi @goneall I made a pr to fix this issue. Can you review it?

@BanulaKumarage test_submit_new_license is the test for get request on submit-new-license page while test_post_submit tests the post request. Both of them have different functionalities

get -> retrivies page and check the form is displayed with correct values
post -> checks with correct data license is submitted successfully

Thank you @rtgdk. I got the idea

@rtgdk - what is the status of this?


host: Add vertical resizing in left code mode column

This extends ResizablePanelGroup with an orientation property that allows either horizontally- or vertically-resizing panels. This is accomplished by extracting private getters that derive dimensional property names from @orientation, like clientWidth vs clientHeight as clientLengthProperty, which allows the geometric calculations to be dimension-agnostic. width is broadly renamed to length. Other renamings follow a pattern of leftEl/rightEl to firstEl/secondEl.

There’s also a reverseCollapse property that works best with a two-panel setup like exists in the leftmost column; the default is to collapse edge panels inward, but in a two-panel setup you might want to collapse end-ward instead of beginning-ward.
Known limitations

The original implementation used HTML element ids to connect the group and panels, which limited it to one resizable panel per page. This adds @orientation to the ids which means there can now be one group per orientation on the page only. I haven’t opened an issue about this because it might be fine, although it did prevent me from adding a third example on the usage page to demonstrate vertical orientation separately from reverseCollapse. One way to fix this would be to use guidFor, or when the panels register themselves with the parent the parent could store their elements directly instead of using querySelector.

The reverseCollapse handle points correctly before collapsing but not after. Recorded as 6167.

I fixed something similar to this when resizing the left column but it remains when resizing the entire window. This doesn’t happen with the horizontally-resizing panels for unknown-to-me-reasons, is it because the vertically-resizing ones are nested? Recorded as 6168.

Is it possible to reuse the resizable-panel-group component? I believe we could enhance it by incorporating a direction parameter, which would allow us to determine whether the panel can be expanded vertically or horizontally.

yes, that’s what I’m doing

When the left column is snapped closed, there is a random triangle hanging out, presumably from the otherwise hidden vertical resize handle:

When the left column is snapped closed, there is a random triangle hanging out, presumably from the otherwise hidden vertical resize handle:

nice catch, thanks. Maybe this won’t be too hard to fix (hide the handle if the opposite-orientation length is 0) but I’ll open another issue for it.


Post markers should close the current popup when selected

Related issue: https://github.com/angular-ui/angular-google-maps/issues/434

Neverwoods
Margrietlaan 10
Willemstad, Curaçao
T (+599 9) 522 9996
W http://www.neverwoods.com
"we create the future"
On Sun, Feb 1, 2015 at 4:51 AM, Keith D. Moore<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/trendicity/trendicity/issues/47.

Modified the behavior so this is no longer an issue.


windows_certificate_binding is ignoring store_name attribute

This fixes issues as reported in #298 where the store_name of windows_certificate_binding is ignored and always uses MY regardless of attribute value.

:+1:

:+1:


fix overriding of headers when using deprecated body setters

fixes https://github.com/Azure/azure-sdk-for-python/issues/33751

API change check
API changes are not detected in this pull request.

/azp run python - communication - ci


fix: reduce through2 usage

This is the part where I admit to not understanding how the other stream fix y'all landed works, or if this would be subject to the same kind of problem.  I do know that the last 2 usages of through2 in the codebase cause sample test failures if you swap them out with PassThrough.  Can I ask you both to poke holes in this?

The default through.objseems equivalent to pass through. The other usages are nested streams to allow for retry. The other fix was due to one stream ending, but not unpiping causing write after end errors.
https://github.com/googleapis/nodejs-bigtable/blob/master/src/table.ts#L689
The instances in table.ts likely need to replace the usage with
stream.Transform(writableObjectMode: true, transform: (chunk, encoding, callback) => {
  // bespoke transform
});


Depth Gradient Derivation

Hello, thank you for the great work and congratulations on your paper acceptance!
I was wondering how you derived the gradient for the depth from the camera plane. In particular this part:
        // the w must be equal to 1 for view^T * [x,y,z,1]
	float3 m_view = transformPoint4x3(m, view);

	// Compute loss gradient w.r.t. 3D means due to gradients of depth
	// from rendering procedure
	glm::vec3 dL_dmean2;
	float mul3 = view[2] * m.x + view[6] * m.y + view[10] * m.z + view[14];
	dL_dmean2.x = (view[2] - view[3] * mul3) * dL_ddepth[idx];
	dL_dmean2.y = (view[6] - view[7] * mul3) * dL_ddepth[idx];
	dL_dmean2.z = (view[10] - view[11] * mul3) * dL_ddepth[idx];

	// That's the third part of the mean gradient.
	dL_dmeans[idx] += dL_dmean2;

Per my understanding, the depth that is calculated in the forward pass is simply the p_view.z that is calculated in
in_frustum(idx, orig_points, viewmatrix, projmatrix, prefiltered, p_view)

In this method (contained in auxiliary.h) the world-space 3D coordinate undergoes a rigid transform to the view space 3D coordinate. In that case, wouldn't the gradient just be the coefficients that map the world-space x,y,z to the view z-coordinate in the view matrix? Like:
//aggregate depth gradients
	dL_dmean2.x = view[2] * dL_ddepth[idx];
	dL_dmean2.y = view[6] * dL_ddepth[idx];
	dL_dmean2.z = view[10] * dL_ddepth[idx];

Is there something I'm missing here? I'm simply trying to reverse engineer whatever happened in the forward pass. Your help is much appreciated!

Hi, thanks for your interest.
Actually, in Deformable-GS, we only used the main branch of depth-diff-gaussian-rasterization, meaning we only have a forward pass for depth.
Interestingly, in our experiments, depth supervision actually led to negative optimization. In more general experiments with vanilla 3D-GS, we also found that improvements in 3D-GS geometry did not lead to an enhancement in rendering quality.


Add missing TransactionOperation fields

Fields gateway_configuration and gateway_configuration_id were present in API response but missing in class definition.

Thanks for the active feedback! This change was introduced into the master branch, and is available in versions >= 6.15.1


New version: alesimula.wsa_pacman version 1.3.5

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

@OfficialEsco This is an internal failure. An upstream team sent us an unexpected value that we attempted to parse into an enumeration which failed. We are currently working on a fix for this. We will also build measures to help avoid this in the future.

@wingetbot run


Add CLI-3-MAIN chinese version

fixed #3

Please change the filename, no need to add the suffix for now.


kytea: 0.4.6 -> 0.4.7; source was still pointing to version 0.4.6

Motivation for this change
Source was pointing to 0.4.6 even though version stated 0.4.7
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks!


Integrate client into loadgen

Instead of having standalone executable client.py (or C++ version, see #112) that runs arbitrary workload, we could integrate the client into loadgen itself. This would simplify running the power measurement on the SUT side, and allow us to measure in more environments, e.g. mobile.
We considered this option in the past (2020-12-11), but decided to postpone it after round 1.0. Probably should be done in the inference repo.
Estimate time of implementation: 3-4 weeks.

[ ] Analyze loadgen codebase to understand what is the best way of integration
[ ] Create minimal working prototype that can connect to the server
[ ] Integrate all necessary features

I would like to propose that we only take this on,  if any other higher priority issues are resolved and if we can fix this by v1.1 freeze date.


Add command to deploy Lambda + API Gateway

To make it easy to setup and convenient, a command to deploy the Lambda and setup API gateway would be nice.

This will be done via Apex. It should basically be all set with the following commands (though I might add a script to simplify - combining the apex commands and adding a prompt for AWS account ID, DynamoDB table name for the config, API name, stage, etc.).
apex infra apply -var 'aws_account_id=XXXXX'
apex deploy

Allow this from the CLI using discfg api deploy or something like that...Because there could be an api run as well for running an API server on the current machine. api remote api serverless api lambda ? Anyway, since someone could get the binary without the source of course, it should fetch the data from the apex directory and deploy.
So this would also mean the command would need to get Terraform and Apex too...
Alternatively, it could all be done with Terraform and zip files could be put in the distribution. Have to think about the best UX on this one.

I think the Terraform can be dramatically simplified now that AWS API Gateway has a pass through ANY request method. Though it will work today as set up.
Getting this to work from the binary is going to require a bit of work and will ultimately bloat the binary too. The reason is because it would need to bundle all of the compiled apex functions ready to go and also the apex deploy functionality.
Might need to revisit this or even avoid using apex for something more simplistic.

This will be handled by #26


SpanMarker support to the estimator tool

As per accelerate output:
ValueError: Library `span-marker` is not supported yet, please open an issue on GitHub for us to add support.
https://github.com/tomaarsen/SpanMarkerNER

Can you give us a full trace please? What were you trying to do? What was the code you were running?

I ran the following command from the shell:
accelerate estimate-memory stefan-it/span-marker-gelectra-large-germeval14 --dtypes float32
Full trace:
  _torch_pytree._register_pytree_node(
/Users/user/anaconda3/envs/ner2/lib/python3.11/site-packages/transformers/utils/generic.py:309: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _torch_pytree._register_pytree_node(
Traceback (most recent call last):
  File "/Users/user/anaconda3/envs/ner2/bin/accelerate", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/user/anaconda3/envs/ner2/lib/python3.11/site-packages/accelerate/commands/accelerate_cli.py", line 47, in main
    args.func(args)
  File "/Users/user/anaconda3/envs/ner2/lib/python3.11/site-packages/accelerate/commands/estimate.py", line 250, in estimate_command
    data = gather_data(args)
           ^^^^^^^^^^^^^^^^^
  File "/Users/user/anaconda3/envs/ner2/lib/python3.11/site-packages/accelerate/commands/estimate.py", line 217, in gather_data
    model = create_empty_model(
            ^^^^^^^^^^^^^^^^^^^
  File "/Users/user/anaconda3/envs/ner2/lib/python3.11/site-packages/accelerate/commands/estimate.py", line 133, in create_empty_model
    raise ValueError(
ValueError: Library `span-marker` is not supported yet, please open an issue on GitHub for us to add support.```

If a contributor would like to implement this that is most welcome, however we only guarantee support for libraries inside the Hugging Face suite


Library doesn't work without jcenter()

The classes are not identified if I remove  jcenter() repositories. Please support maven

Migrated to https://github.com/CanHub/Android-Image-Cropper


CalTRACK Issue: Improve handling of buildings with weather-energy misalignments

Prerequisites

[x] Are you opening this issue in the correct repository (caltrack/grid/seat)?
[x] Did you perform a search of previous Github issues to check if this issue has been previously considered?

Article reference number in CalTRACK documentation (optional): 3.3.1 (?)
(Also, see original issue #111, closed during CalTRACK transition from OEE to EM2.)
Description
Background
Buildings have different thermal characteristics which can create a delay between outdoor temperature changes and the resulting heating and cooling energy loads. For example, an uninsulated wood home from the 1950’s will respond very differently to a winter cold snap than a new highly insulated straw-bale home with high thermal mass. The heater will turn on almost immediately in the former, but may not respond for several days in the latter. As a result, increased HVAC energy use may lag temperature changes by several days. While these lags are most apparent during extreme temperature swings, they are caused by fixed building characteristics and the same delay occurs with every outdoor temperature change, no matter how small.
Likewise, the opposite can occur, if buildings incorporate automated pre-cooling or pre-heating strategies. In these cases – which we expect to become more common in the future as we shift to TOU rates -- the associated increase in HVAC energy consumption may precede a change in temperature. Examples:

Since 1991 PG&E’s Pacific Energy Center can consume more electricity the day before a very hot day by making and storing ice in the basement, which is then used to cool the building in following days.
Stanford's new SESI facility represents an extreme case: they can start chilling water up to 7 days (!) before a heat wave.

Issue
Current CalTRACK methods look for correlations between weather and energy use on a day by day basis (i.e., Tuesday’s outside temperature is only compared to Tuesday’s energy use). As such, any significant delay between cause and effect will obfuscate the true amount of energy correlated with weather, and regression results will be inaccurate. This type of model error is indicated in the chart below as either type 1 or type 2: individual [daily] energy data points used during the regression analysis are being placed incorrectly -- the temperature or energy values for the data points are not including physical effects from different days.

Validation
There are at least two issues to validate: (1) the building behavior and (2) the potential impact on NMEC results.
(1) Regarding the building behavior:
HEA confirmed this issue with a variety of building science experts including Gil Masters at Stanford. But this group likes data, so we recently ran a simple test to try to directly measure this “lag”.
Test methodology:

Use hourly natural gas data from 29 gas-heated homes in SoCalGas territory.
Find all “cold snap” dates, defined as the first day when the local weather average temperature dropped by 5 degrees (F) compared to a 5-day rolling average. Weather data came from the KONT weather station very near these homes.
Exclude those dates with any similar cold snaps within five days before or after.
For each home, determine the maximum gas use within 5 days after the cold snap date. Record the difference in hours between cold snap date and the timestamp of the observed maximum gas use.

Results:

We identified 28 such cold snaps between October of 2015 and last week.
The median lag across all homes was 41 hours, with an average standard deviation of 31 hours.

Nearly two days! This is longer than we expected and the variation is quite high, so hopefully someone can run a better analysis, perhaps using regressions with varying offsets. But we believe even this simplistic analysis demonstrates the presence of meaningful delays.
(2) Regarding the impact on NMEC results:
HEA’s internal analysis produces significantly lower CVRMSE values than CalTRACK (see table in Issue #103). In other posts we've documented a number of issues we believe contribute to these improved results, but we have not been able to quantify the impact of each issue independently. The test results described above, if accurate, indicates that many more homes than [we] expected have significant delays between weather and energy use. If this is the case, the delay would undoubtedly impact CalTRACK's existing day-by-day weather-energy correlations, making this issue a significant opportunity to lower CVRSME values, reduce model bias, or both.
Requested CalTRACK change
Investigate and characterize the effectiveness of methods to improve handling of timing differences between weather changes and associated energy use in different building types.
There are probably many ways to address this issue. HEA correlates a single day’s temperature with a moving 5-day average of energy use covering two prior days and two days post. We implemented this in 2011 after finding that it significantly improved regression results for many homes, with no noticeable degradation of existing “good” regression results for others (HEA testing methods were documented in #109).
Proposed test methodology

Identify a test sample of appropriate buildings that demonstrate delayed response to weather spikes, together with others which do not (to use as a control group).
Run current methods on these homes and record "before" results.
Adjust daily methods to take these energy-weather misalignments into account.
Rerun with the updated data, and compare "after" results.

Acceptance Criteria
Monthly bias and CVRMSE values should be improved in most cases, and never made worse.

Notes from working group meeting on 10/23/19:

Ethan asked if this was similar to Normal Year Savings being discussed in the GRID working group. Steve responded that he didn't think so, since actual weather data is being used in this case.
Ethan asked if a moving average might also dilute or degrade the correlation between weather and energy use for buildings that do not demonstrate a delay. Steve responded that HEA did not see any noticeable degradations, but saw significant improvements across many homes.
Jon noted the impact of this type of change should be fairly easy to test.

I having a hard time thinking through what the consequences are of using a 5-day rolling average temperature are, but it seems like they could be significant and not always for the best. I think the usual way that temperature response delays are modeled using hourly data is by using lagged temperature variables. I could imagine a similar method for use with daily data. However, I expect the optimal lag length may vary considerably depending on how extreme the outdoor temperatures are and how quickly changes occur. Not sure how that is typically handled.


Remove default_pass_manager_simulation in favor of level 1 default

Summary
Follow up to #2672

This is out of WIP

I tried to remove the change in test/python/basicaer/test_unitary_simulator.py in df45973, since it seems unrelated to this PR:
However, it's not passing, so I reverted it in 3a9084b. It probably needs adjustment. Is there any way to adjust this test minimally?

No this change is needed because the global phase must be ignored in the comparison of unitaries.


Bump build number, update URL and add patch to build with METIS 5.1.1

Checklist

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

Based on coin-or/coinbrew#47 (comment) probably we should pass -fallow-argument-mismatch somewhere.

See also https://github.com/conda-forge/scalapack-feedstock/pull/30#issuecomment-1061196317 .

Some macos builds fail with:
Error: Type mismatch in argument ‘s’ at (1); passed INTEGER(4) to LOGICAL(4)
mpi.f:575:72:

  575 |          CALL MUMPS_COPY_LOGICAL( SENDBUF, RECVBUF, CNT )
      |                                                                        1
Error: Type mismatch in argument ‘r’ at (1); passed INTEGER(4) to LOGICAL(4)
mpi.f:577:72:

  577 |          CALL MUMPS_COPY_REAL( SENDBUF, RECVBUF, CNT )
      |                                                                        1
Error: Type mismatch in argument ‘s’ at (1); passed INTEGER(4) to REAL(4)
mpi.f:577:72:

  577 |          CALL MUMPS_COPY_REAL( SENDBUF, RECVBUF, CNT )
      |                                                                        1
Error: Type mismatch in argument ‘r’ at (1); passed INTEGER(4) to REAL(4)
mpi.f:580:72:

  580 |          CALL MUMPS_COPY_DOUBLE_PRECISION( SENDBUF, RECVBUF, CNT )
      |                                                                        1
Error: Type mismatch in argument ‘s’ at (1); passed INTEGER(4) to REAL(8)
mpi.f:580:72:

  580 |          CALL MUMPS_COPY_DOUBLE_PRECISION( SENDBUF, RECVBUF, CNT )
      |                                                                        1
Error: Type mismatch in argument ‘r’ at (1); passed INTEGER(4) to REAL(8)
mpi.f:582:72:

Based on coin-or/coinbrew#47 (comment) probably we should pass -fallow-argument-mismatch somewhere.

The osx-64 fortran compiler is gfortran 12, while in the latest build was gfortran 9, that is the reason why we now need the workaround also for osx-64 .

Title says draft, but it's all looking okay to me, now. LMK when you think this is ready.

It is not, basically mumps hardcode some indeces that changed between metis 5.1.0 and 5.1.1 and so at runtime in some cases it would crash, see https://github.com/KarypisLab/METIS/issues/71#issuecomment-1696082046 . I wanted to see if there was something in mumps recipe itself that could capture this, but unfortunatly that is not the case.

@conda-forge-admin, please rerender

If anyone has any idea of a test we could add here to fail as python -c "import kwant; kwant.test()" fails, it would be great.

At the moment the build is failing as on linux-ppc64le there is not metis 5.1.1 build, see https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4857#issuecomment-1699470569 for the full context.

At the moment the build is failing as on linux-ppc64le there is not metis 5.1.1 build, see conda-forge/conda-forge-pinning-feedstock#4857 (comment) for the full context.

This was fixed by https://github.com/conda-forge/metis-feedstock/pull/40 , the PR should now be ready.

@conda-forge-admin, please rerender

The PR is ready for review @conda-forge/mumps

The PR is ready for review @conda-forge/mumps

It would be great to merge this, so we can unblock https://github.com/conda-forge/mumps-feedstock/pull/89, thanks!

@conda-forge-admin, please rerender


Fix actions

1. Why is this change necessary?
2. What does this change do, exactly?
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

 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: shyim:x: pantrtxpYou have signed the CLA already but the status is still pending? Let us recheck it.


use ipython-contrib gitter badge, rather than the @epifanio one

whoops, wrong repo branch! See #630


[BUG] Slack invite link no longer works.

What is the bug?
https://opensearch.slack.com/join/shared_invite/zt-2bh052go7-1s_~5G1_alt9aLPmoRAINQ#/shared-invite/error no longer provides an invite for the slack workspace.
How can one reproduce the bug?
Try receiving an invite link

@rjsadow Thanks for reporting this- did you get the link from this page https://opensearch.org/slack.html or was there another location?

@opensearch-project/admin Can you please transfer this to the project-website project?
Looks like join-slack-button needs to be regenerated impacted code: https://github.com/opensearch-project/project-website/blob/7f7d17ac4a78af7ee64101efe5cff9e352cd97fd/_includes/redesign_buttons.html#L172


docker missing arches

looking at https://linbreux.github.io/wikmd/installation/docker.html
it says "Docker files are available for arm, arm64 and amd64."
however if you look at: https://hub.docker.com/r/linbreux/wikmd/tags
only amd64 is listed.
and when trying to use the docker compose example you will see the error "exec format error" in logs when attempting to start the container on an arm64 system.

Cool work!!, but would be awesome to have arm arch images


Update README.md

Fixing some of the generated commands to be more accurate

i dunno i think we may need to put this through a few rounds of QA