Transfer learning process incorrect

As far as I can tell, during the transfer learning process, you're already trying to make the network classify the videos.
Instead, the 2D CNN should take 32 RGB frames from a video of a certain timestamp and the 3D CNN should take a video clip from the same timestamp. The network then should tell if the 32 frames and the video clip match. That way you can use a huge data set of unlabeled videos, because the label doesn't matter.
It shouldn't be too difficult to fix. The video generator could pick a random video with a random timestamp and extract 32 frames from it. Then it could either feed the same data to the 3D CNN with a label of '1', as the data is from the same video, or it could pick another video and feed that data to the 3D CNN with a label of '0'.

Thanks for correction, I have updated the development branch to do a quite similar thing. Just need to do a sanity check. I'll let you know once I check them on proper GPU machines.

I still don't understand how did the authors feed the 2D CNN 32 images while inputting a video clip to the 3D CNN at the same time.
2D input has the shape (224,224,3), but it has to take 32 images, so the shape then should be (32,224,224,3). The 3D CNN also takes the input shape of (32,224,224,3).
Is there a way to feed the 2D CNN 32 images one by one and only feed the 3D CNN one video clip in a single batch? If that's impossible, you'd have to replace the input layer of the 2D CNN to match the one of the 3D CNN.

@MartynasJanonis, I agree with you.
The input shape to 2D CNN is (?, 224, 224, 3) and 3D CNN is (?, 32, 256, 256, 3) where ? denotes batch-size. My initial approach was to make batch-size of 2D CNN 32 and 3D CNN 1. But that didn't work and raised an error:
All input arrays (x) should have same number of samples. Got array of shapes : [(32, 224, 224, 3), (1, 32, 256, 256, 3)]
One way to tackle this is using keras.layers.TimeDistributed on the input-layer of 2D CNN. I have to do further digging on this and then can I come with a solution. If you find any other way, please comment.


recOrder data schema

Fixes #371
This PR describes recOrder's current storage schema for discussion. Let's iterate on the schema here, then after this merges I will modify recOrder to match the schema.
Here's a list of the issues I think should be addressed together with my suggestions:

consistent numbering: I'll vote for the first BG to be BG_0 to match the snaps
consistent case: I'll vote for snake_case everywhere, so BG -> bg, recOrderPluginSnap -> recorder_plugin_snap and <acq_name_0>_RawPolDataSnap.zarr -> <acq_name_0>_data.zarr
simpler names: I'll vote for <acq_name_0>_recOrderPluginSnap -> <acq_name_0>_snap, and <acq_name_0>_RawPolDataSnap.zarr -> <acq_name_0>_raw_data.zarr
consistent path to raw data: we currently save polarization data to *_RawPolDataSnap and brightfield data to *_RawBFDataSnap. The channel names within these zarr stores describe the data within ('BF', 'State*'), so this data is redundant. (I'm flexible on this point, but if we prefer separate names then I think the names should appear one level up...as is they're hidden in the root directory).
consistent duplication of <acq_name>: I will vote for <acq_name_0>_RawPolDataSnap.zarr -> RawPolDataSnap.zarr, but I'm also fine with the alternative of prepending <acq_name_0> to the other files (reconstruction.zarr, transfer_function.zarr, etc)

Those are good suggestions @talonchandler . We can simplify the schema even further.

bg_<n>.zarr and <acq_name>_<n>.zarr can contain raw and reconstructed data as channels. We can even store the YAML configs inside the Zarr store and eliminate one hierarchy level.
The transfer functions can be stored as bg_<n>_tf.zarr or <acq_name>_<n>.zarr.

Thanks @mattersoflight. I've made edits on this PR for my best-effort attempt to simplify further.

bg_.zarr and <acq_name>_.zarr can contain raw and reconstructed data as channels...eliminate one hierarchy level.

This is a challenging change for a couple reasons:

recOrder's 2D reconstructions have different shapes for raw and reconstructed data, and IMO it would be confusing to mix 2D and 3D data in a single TCZYX array. We could think about adding them as different Arrays in the zarr store, but...
recOrder's current CLI operates on zarrs with regular PTCZYX shapes. Adding array support to recOrder's CLI is possible, but it leads to several non-obvious UI questions: how should I specify which Arrays are input and output (config file or CLI)?, what napari viewer should I use to visualize a multi-channel multi-array zarr store?

At the expense of the extra hierarchy level, I think the current design is working reasonably well so I will vote to stick with separate raw_data.zarr and reconstruction.zarr. Any thoughts @ziw-liu?

The calibration metadata, gui_state, and reconstruction_settings can be part of a single YML file, if that does not pose any challenges in workflow.

I think calibration metadata and reconstruction_settings need to stay separate for our workflows (also worthwhile considering an likely upcoming split of recOrder and a calibration plugin).
IMO gui_state has served its purpose as an interim reproducibility aid since we now have the reconstruction_settings. @ziw-liu let me know if you have any objection to me removing it.

recOrder's 2D reconstructions have different shapes for raw and reconstructed data, and IMO it would be confusing to mix 2D and 3D data in a single TCZYX array. We could think about adding them as different Arrays in the zarr store, but...

I agree that the main issue of having 2D reconstructions from 3D raw data in the same store is visualization. The napari-ome-zarr plugin doesn't support extra arrays other than resolution levels. And saving the 2D reconstruction as an extra channel with only Z=0 being filled would render as black for Z!=0, which is not entirely obvious or convenient.

IMO gui_state has served its purpose as an interim reproducibility aid since we now have reconstruction_settings.yml files. @ziw-liu let me know if you have any objection to me removing it.

It was introduced as a duct-tape fix so no objection in replacing it with a proper implementation!

At the expense of the extra hierarchy level, I think the current design is working reasonably well so I will vote to stick with separate raw_data.zarr and reconstruction.zarr.

Ah - a good point that reconstruction can be a different shape than raw_data. Makes sense to store raw_data.zarr and reconstruction.zarr  as separate stores.

I think calibration metadata and reconstruction_settings need to stay separate for our workflows (also worthwhile considering a likely upcoming split of recOrder and a calibration plugin).
If a CLI needs both config files, the information is best kept in the same files. If a CLI/UI needs just one of the two pieces of information, it can just read that field. The unused field is a 'read-only metadata'. We had too many config files (preprocessing, training, prediction) in microDL that all needed to be carried around. I am trying to prevent a similar outcome.

Is calibration metadata needed only for polarization-resolved acquisitions? If yes, it may make sense to keep the files separate. In that case, I would rename the file to polarization_calibration.txt

Is calibration metadata created only for polarization-resolved acquisitions? If yes, it may make sense to keep the files separate. In that case, I would rename the file to polarization_calibration.txt

That's correct. The calibration is only for polarization-resolved acquisitions, so I like this renaming. Changing.
The polarization_calibration.txt file is not used as an input for the reconstruction pipelines, so I think it's appropriate to keep polarization_calibration.txt in a separate file. The only field that is needed by the reconstruction is the swing, so that field appears in both polarization_calibration.txt and reconstruction_settings.yml.
Thanks!


Update HTTP getfile handler to pass along metadata

When testing:
$curl http://localhost:30652/v1/pfs/repos/test/commits/4cc12ebb8bd24a2d8909ce93878ab7c3/files/Makefile -H "Cookie: authn-token=abbazabbadoo"

I see (from some added instrumentation in auth.In2Out) the incoming context specified appropriately:
incoming context: context.Background.WithValue(metadata.mdIncomingKey{}, metadata.MD{"authn-token":[]string{"abbazabbadoo"}})

Also, a note ... for some reason hitting that URL from my browser doesn't work ... but substituting <IP_ADDRESS> for localhost works ... I think this is just a DNS issue / difference btw my browser and the shell.


Add optional processing of styles with Hugo Pipes

This bump the min version to .79 but could be lower once we discuss the scripts treatment @budparr
Fixes #379

We end up only bumping to 64.

We end up only bumping to 64.


Return a 0 temperature value when none is found

It's well documented that these TRVs will only return the current temperature
for a short time after the actuator has moved. This means that, usually, they will
not return the current temperature. Setting a non-value here causes errors in the logs
and for the TRV to not show on the dashboard at all.

Hi @phil-lavin,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Allow multiple edges with different type (catalog graph)

Hey, I just made a Pull Request!
I'm currently implementing a new plugin, which is highly requested from end users in our firm.
Additionally, I saw some issues here, which go into the same direction like #17996 or #18751
Here the first draft of my plugin code https://github.com/dweber019/backstage-plugins/tree/feat/relations/plugins/relations-backend
It works like intended and fits nicely our firms needs.
One thing I noticed, was that the catalog graph it not implemented with multiple edges in mind when the edges have the same source/from and target/to nodes but different relation types like (e.g. ownerBy, ledBy, applicationOwnerBy...).
What did I change.

The section in if (unidirectional) { will just add missing edges, if unidirectional is set to true, as with the implementation of this visitor pattern, we only visit nodes once and therefor are only picking up a relation once.
the const finalEdges = edges.reduce((previousEdges will merge relation types for edges so only edge remains per source and target. This change even seams to improve rendering performance when I tested this with a graph > 200 nodes.

Here some screenshots after the modification

Would highly appreciate if we can bring this feature to the graph and grateful for any input on optimising my changes.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@benjdlambert any chance to review there changes? would like to release the plugin, which needs this change to work properly 🙏
https://github.com/dweber019/backstage-plugins/tree/main/plugins/relations-backend

@dweber019 it needs a review from @backstage/catalog-maintainers before we can merge this. Pinging them internally too.

@benjdlambert rebased on the latest and fixed DCO.

nice thanks! sorry for the delay! :tada:

Awesome thx @benjdlambert


Behat with Firefox-node error, Could not open connection: Payload received from webdriver is valid but unexpected json: ..

I'm having an issue connecting behat with the docker selenium firefox node through grid. I keep getting a "Could not open connection: Payload received from webdriver is valid but unexpected json: ..."
If I watch the test, Firefox starts and freezes. It never loads any pages i'm directing it to and fails out on the first step "Given I am on "/" see below for actual error.
I am able to connect and run all my tests just fine with the chrome node but I'm running into some issues with my tests and wanted to double check with another browser to determine if it's a chromedriver issue or not.
I have opened a ticket at docker-selenium 665 and they requested I open one here also.
Any help or direction to get this solved would be greatly appreciated.
behat.yml
default:
  suites:
    default:
      contexts:
        - FeatureContext
        - Drupal\DrupalExtension\Context\DrupalContext
        - Drupal\DrupalExtension\Context\MinkContext
        - Drupal\DrupalExtension\Context\MessageContext
        - Drupal\DrupalExtension\Context\DrushContext
  extensions:
    Behat\MinkExtension:
      browser_name: 'firefox'
      javascript_session: selenium2
      goutte:
        guzzle_parameters:
          verify: false
      selenium2:
        wd_host: 'http://<IP_ADDRESS>:4444/wd/hub'
        capabilities:
          browserName: 'firefox'
          browserVersion: '*'
          marionette: true
      base_url: https://<IP_ADDRESS> #localhost
    Drupal\DrupalExtension:
      blackbox: ~
      api_driver: 'drupal'
      drush:
        root: '/var/www/vendor/drush/drush'
      drupal:
        drupal_root: '/var/www/web'

Meta -
Image(s):
selenium/hub
selenium/node-firefox-debug
Docker-Selenium Image Version(s):
latest
Docker Version:
17.12.0-ce
OS:
Ubuntu 16.04
-->
Expected Behavior -
For Firefox to open and run tests.
Actual Behavior -
@api @javascript
  Scenario: Test user login link while authenticated.                            # features/eva.feature:10
    Given I am on "/"                                                            # Drupal\DrupalExtension\Context\MinkContext::visit()
      Could not open connection: Payload received from webdriver is valid but unexpected json: {"value":{"sessionId":"34a26006-2510-4400-9e39-a8b74a655176","capabilities":{"moz:profile":"/tmp/rust_mozprofile.Xa1n21MpYjLo","rotatable":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"pageLoadStrategy":"normal","moz:headless":false,"moz:accessibilityChecks":false,"acceptInsecureCerts":false,"browserVersion":"57.0.4","platformVersion":"4.13.0-31-generic","moz:processID":319,"browserName":"firefox","platformName":"linux","moz:webdriverClick":false}}} (Behat\Mink\Exception\DriverException)
    And I am logged in as a user with the "Authenticated user" role on this site # FeatureContext::assertAuthenticatedByRoleOnThisSite()
    And I wait for 1 seconds                                                     # FeatureContext::iWaitForSeconds()
    Then the href of ".header-user a" should be "/user"                          # FeatureContext::theHrefShouldBe()

--- Failed scenarios:

    features/eva.feature:10

1 scenario (1 failed)
4 steps (1 failed, 3 skipped)

I was able to fix this issue by downgrading to an older version of firefox tag 2.53.0 which is selenium2 compatible. I guess compatibility with the newer version of firefox isn't working yet, but it's mostly working on newer versions of chrome which is why i was getting errors using firefox.
closing this for now.


Need correct link for "Azure Event Grid"

In the "Next Steps" section, the link to "Azure Event Grid" goes to the same link as "Azure Functions".

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

ID: de93e314-ae26-29c3-1594-377081ddb002
Version Independent ID: a65af49c-ba04-b76a-b510-a8646d5056e6
Content
Content Source
Service: service-bus-messaging

@ggailey777 @tdykstra @tfitzmac Can you please take a look?

Hey Patrick
Thanx for the feedback! We have assigned the issue to the authors to update as appropriate.


Radio Canada link doesn't match radiocanada extractor URL pattern

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[x] I've read about sharing account credentials and I'm willing to share it if required

Region
Canada
Provide a description that is worded well enough to be understood
I'm trying to download a documentary from radio-canada. I saw  that there was an extractor 1 but my URL doesn't match the pattern, falls back to the generic information extractor and ends with a yt_dlp.utils.UnsupportedError.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://ici.radio-canada.ca/tele/decouverte/site/episodes/786107/baie-james-hydroelectrique']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp (linux_exe)
[debug] Python 3.11.10 (CPython x86_64 64bit) - Linux-6.11.10-amd64-x86_64-with (OpenSSL 3.1.7 3 Sep 2024)
[debug] exe versions: rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.7.1, mutagen-1.47.0, requests-2.32.3, secretstorage-3.3.3, sqlite3-3.44.2, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[generic] Extracting URL: https://ici.radio-canada.ca/tele/decouverte/site/episodes/786107/baie-james-hydroelectrique
[generic] baie-james-hydroelectrique: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] baie-james-hydroelectrique: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://ici.radio-canada.ca/tele/decouverte/site/episodes/786107/baie-james-hydroelectrique
Traceback (most recent call last):
  File "yt_dlp/YoutubeDL.py", line 1624, in wrapper
  File "yt_dlp/YoutubeDL.py", line 1759, in __extract_info
  File "yt_dlp/extractor/common.py", line 742, in extract
  File "yt_dlp/extractor/generic.py", line 2553, in _real_extract
yt_dlp.utils.UnsupportedError: Unsupported URL: https://ici.radio-canada.ca/tele/decouverte/site/episodes/786107/baie-james-hydroelectrique

Duplicate of #6678


ValueError: vector

When attempting to load an ASE calculator for a particular water model, I get the following error:
In [1]: from pynep.calculate import NEP

In [2]: calc = NEP('nep.txt')
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-2-746ad733c731> in <module>
----> 1 calc = NEP('nep.txt')

~/anaconda3/lib/python3.8/site-packages/pynep/calculate.py in __init__(self, model_file, **kwargs)
     16     def __init__(self, model_file="nep.txt", **kwargs) -> None:
     17         Calculator.__init__(self, **kwargs)
---> 18         self.calc = NepCalculator(model_file)
     19         self.type_dict = {e: i for i, e in enumerate(self.calc.info["element_list"])}
     20

ValueError: vector::_M_default_append

The model was constructed with GPUMD 3.2, here is a snippet of how nep.in was parsed:
Input or default parameters:
    (input)   use NEP version 3.
    (input)   number of atom types = 2.
        (default) type 0 (H with Z = 1) has force weight of 1.
        (default) type 1 (O with Z = 8) has force weight of 1.
    (default) will not add the ZBL potential.
    (input)   radial cutoff = 4.3 A.
    (input)   angular cutoff = 3 A.
    (default) n_max_radial = 8.
    (default) n_max_angular = 6.
    (default) l_max_3body = 4, l_max_4body = 0.
    (default) number of neurons = 50.
    (default) lambda_1 = 0.02.
    (default) lambda_2 = 0.02.
    (default) lambda_e = 1.
    (default) lambda_f = 1.
    (default) lambda_v = 0.1.
    (default) force_delta = 0.
    (input)   batch size = 2264.
    (default) population size = 50.
    (input)   maximum number of generations = 20000.
Some calculated parameters:
    number of radial descriptor components = 9.
    number of angualr descriptor components = 28.
    total number of  descriptor components = 37.
    NN architecture = 37-50-1.
    number of NN parameters to be optimized = 1951.
    number of descriptor parameters to be optimized = 576.
    total number of parameters to be optimized = 2527.

To be sure, the calculator works for some other models, e.g. the PbTe example model in GPUMD/examples/nep_potentials/PbTe/train. I'm not sure what the difference is with this new model that I have?

Could you please provide the nep.txt or just the the first few lines if it's not convenient to upload?

Thank you, the basis_size line was indeed the missing link. I will update GPUMD on this machine. I will also try the larger cutoff, thank you for the suggestion.


No Response with error urllib3.connection.HTTPSConnection Failed to establish a new connection [Errno 11001] getaddrinfo failed

Package Name: azure-ai-formrecognizer
Package Version: 3.2.0
Operating System: windows
Python Version: 3.7

Describe the bug
I am using the SDK for getting predictions from invoices and receipt pre-build models. I create a exe of this python file using pyinstaller. initially it was running properly. but suddenly this is giving me below error.
No Response with error urllib3.connection.HTTPSConnection Failed to establish a new connection [Errno 11001] getaddrinfo failed
To Reproduce
Steps to reproduce the behavior:
1.
Expected behavior
This should return the expected output object.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
import argparse
import os
from azure.ai.formrecognizer import DocumentAnalysisClient
from azure.core.credentials import AzureKeyCredential
pstr_az_endpoint = r"https://xyz.cognitiveservices.azure.com/"
pstr_az_key = "xyz"
document_analysis_client = DocumentAnalysisClient(endpoint=pstr_az_endpoint, credential=AzureKeyCredential(pstr_az_key))
if __name__ == '__main__':
    # import ctypes
    parser = argparse.ArgumentParser(description='For testing purposes')
    parser.add_argument('-path', dest='path', type=str, default=None)
    parser.add_argument('-model', dest='model', type=str, default=None)
    args = parser.parse_args()
    if args.path:
           with open(args.path, "rb") as fileitem:
                lftr_file = fileitem.read()
                lbyte_file = bytearray(lftr_file)
                poller = document_analysis_client.begin_analyze_document(args.model, lbyte_file)
                print(poller.result())
    else:
        print(f"path is not specified")

Thanks for reaching out.
This error shows that you don't have a working network connection.
Please check your network setting.

/unresolved

now i am also getting
("('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))",)
its working fine when I make exe using below code
`import argparse
import os
from azure.ai.formrecognizer import DocumentAnalysisClient
from azure.core.credentials import AzureKeyCredential
pstr_az_endpoint = r"https://xyz.cognitiveservices.azure.com/"
pstr_az_key = "xyz"
document_analysis_client = DocumentAnalysisClient(endpoint=pstr_az_endpoint, credential=AzureKeyCredential(pstr_az_key))
if name == 'main':
# import ctypes
parser = argparse.ArgumentParser(description='For testing purposes)
parser.add_argument('-path', dest='path', type=str, default=None)
parser.add_argument('-model', dest='model', type=str, default=None)
args = parser.parse_args()
if args.path:
        with open(args.path, "rb") as fileitem:
            lftr_file = fileitem.read()
            lbyte_file = bytearray(lftr_file)
        poller = document_analysis_client.begin_analyze_document(args.model, lbyte_file)
        print(poller.result())

else:
    print(f"path is not specified")

`
but in production exe I am making a object of document_analysis_client and reusing it for every API call to that exe. cant figure out whats going wrong for once it worked fine but next call it gave the above error


Added mandatory models

Fixes this so that old verisons will have these

This PR handles issue #282 in pearai-app repository


net-mgmt/telegraf: Support InfluxDB v2 Output

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
[x] When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
I've recently upgraded to Influx v2.0.0-beta on my servers, but can't find an option to setup an influx 2 connection in the os-telegraf package.
Describe the solution you'd like
I'd like a checkbox, like the other ones for influx/prometheus/etc outputs, where we can fill in the following data:

Url - The URL where Influx v2 is hosted.
Token - The token with which to connect.
Organization - Influx v2 is multi-tenant, so we must specify an organization.
Bucket - Database name.

Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
Here's how the configuration should look like
[[outputs.influxdb_v2]]
    ## The URLs of the InfluxDB cluster nodes.
    ##
    ## Multiple URLs can be specified for a single cluster, only ONE of the
    ## urls will be written to each interval.
    ## urls exp: http://<IP_ADDRESS>:9999
    urls = ["http://my.host:9999"]

    ## Token for authentication.
    token = "<base64-encoded-string>"

    ## Organization is the name of the organization you wish to write to; must exist.
    organization = "<string>"

    ## Destination bucket to write into.
    bucket = "<string>"

Environment
OPNsense 20.1.7-amd64 on a virtual machine
os-telegraf 1.7.7

I'll try to spin up a development environment and add it myself, doesn't seem that hard.
Ill be taking notes from https://github.com/opnsense/plugins/pull/834

Yes, should be easy :)

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Discover and/or modify global.json

I’ve been bitten by global.json, not realising it was specified somewhere in the working directory hierarchy, so adding discoverability would be useful; i.e. a subcommand that enumerates all known config files and maybe goes into more detail showing their content.
Also, when tinkering with an open source project, I often take another approach, which is to edit any global.json to match what I have installed, since I prune my installed sdks to the minimum set required for the latest versions.

We have a pending feature that will enumerate directories in the same manner as the dotnet cli. More verbose output would be useful here.
From what I understand, at some point Microsoft will make it say we can say "at least this SDK version" in global.json, which will fully fix your second point, the problem with changing it manually is that you don't know if the OSS repo you are dealing with really needs that version, or just pinned a convenient version, or latest at that point in time.

From my experience it tends to be whatever version was available at that point in time. Besides, it’s easy to revert and install the original version if bumping it breaks something.

So would your suggestion be to allow for this tool to say "It looks like you have a later version of this SDK, use that instead of downloading the exact version?", and yes would rewrite the file to the nearest version that's higher and copy the old version to global.json.bak?
My current workflow for that sort of thing is:
rm global.json
dotnet new globaljson

which will default to the latest SDK you dotnet cli finds, but isn't as intelligent as what is described above.

That would be a great start - apply latest initially and add intelligence for better major.minor compatibility later.
If a global dotnet tool can have config then I’d add options around the above; e.g. don’t generate a backup file (when using source control).

Without wanting to alter the default behaviour of dotnet install-sdk, I suppose one option would be to have flag to allow you to apply a later version if you have it. But at this point I'd question whether it would be better off just deleting the global.json file as if someone isn't interested in using the version pinned then the file's existence is kinda redundant.

That's where I'm at with this one too, you typically want to do one of two things, ignore the project.json (then delete it), or adhere to it and acquire the necessary sdk, this tool helps with the latter.

@slang25 project.json? That's going back a bit! 😁

🤦♂


Support NodeJS 16 (latest LTS)

According to https://github.com/adobe/aio-cli-plugin-cloudmanager#requirements only Node 12 and 14 is supported. Since October Node 16 is the current LTS version though which should be supported (https://nodejs.org/en/about/releases/).

This depends on https://github.com/adobe/aio-cli/issues/324.

I've added node 16 to the build matrix (and had to adjust some dev dependencies) both for this project and @adobe/aio-lib-cloudmanager. But leaving this issue open for "real" support dependent upon aio-cli.

@justinedelson aio-cli supports node 14/16/18! What's the support for the cloud-manager plugin?

@patrickheinzelmann I no longer work at Adobe. I wouldn’t anticipate any issues on newer versions of node but am not in a position to update the CI matrix or even remove the blocked label from this issue.
I would suggest opening a support case.

I opened the ticket E-000955176 about this. It is really unfortunate that regular open source workflows (leveraging GH issues and providing PRs) do no longer seem to work for this and some other Adobe projects...

Ticket resulted in the following answer:

Unfortunately, these plugins are public and managed directly on their public GitHub pages, so I cannot provide an ETA for your request.

Seem that Adobe support seems to regret going open source for this plugin and aio cli in general. But as neither opening issues here nor opening support requests at Adobe seems to have any effect there seems to be kind of a limbo of this tool which is really sad.


Hygiene: fix 1687 filename case collisions & renormalize CRLF & LFS

This is the result of checking out on a case-sensitive filesystem and resolving all conflicts in case, then running git add --renormalize .. Binary files under deps/3rdparty have been reverted.

This change is

It'll be easier to review this in witespace-agnostic mode, here.

I'm a bit confused. Why are the reference images being moved (read renamed) to the actual data folder? Isn't this where the test's generated images go?

Good eye.

I've run the diff list through uniq -ic (which spits out a list of each line in a file prefixed by how many times it appears) and verified that each filename appears identical (case-insensitive) exactly twice -- that is to say, no files have moved to different folders this time.


react-router 0.13.2  Uncaught TypeError: Cannot call a class as a function

Hi
I'm getting an error when trying to render this simple page with react 0.13.0 and react-router 0.13.2.
var React = require('react');
var Router = require('react-router');
var Route = Router.Route;
var RouteHandler = Router.RouteHandler;

var App = React.createClass({
  render: function() {
    return (
      <div> </div>
    );
  }
});

var routes = (
  <Route handler={App} name="app" path="/">
  </Route>
);
Router.run(routes, function (Handler, state) {
  React.render(<Handler/>, document.getElementById('content'));
});

Chrome complains about the following line.
var _classCallCheck = function (instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } };

The page renders fine if I remove react-router. Any ideas of what could be wrong?

I have somehow made it work with 0.13.2. No idea what I did, it just suddenly stopped giving me the error. :confused:

Is there any chance you are using an old version of JSX transpiler that compiles <Handler /> into Handler() instead of the correct React.createElement(Handler)?

@paulmillr

React-router doesn't work at all currently.

Can you please give the exact steps or a sample project to reproduce?
RR 0.13.2 for me (I'm testing with React 0.13 and Babel).

Same problem with react-router 0.13.3 and react 0.13.2.

@gsanta What JSX transpiler are you using?

+1 using grunt-react

we're using CJSX compiler.

Us too.  Specifically in our test suite, we have a test context which handles each component.  In the example below, targetComponent can be any old React Class.  Problem seems to be isolated to TestLocation in our case.

// tests/TestContext.js
// used to bootstrap components that require flux
'use strict';

var Router = require('react-router'),
    Route = Router.Route,
    TestLocation = Router.TestLocation,
    FluxxorTestUtils = require('fluxxor-test-utils'),
    FluxConstructor = require('../../app/FluxConstructor.js');

var TestContext = {

    getRouterComponent: function(targetComponent, props) {
        var realFlux = FluxConstructor();
        var fakeFlux = FluxxorTestUtils.fakeFlux(realFlux);

        //check props and add flux
        if(typeof props === 'undefined'){
            props = {};
        }
        props.flux = fakeFlux;

        var component, mainComponent,
            routes = (
                <Route name="test" path="/" handler={targetComponent} />
            );

        //create router history
        TestLocation.history = ['/test'];

        //run router
        Router.run(routes, TestLocation, function (Handler) {

            //mainComponent = React.render(<Handler props={props} />, global.document.body);
            //component = TestUtils.findRenderedComponentWithType(mainComponent, targetComponent);

        });

        return {
            flux: fakeFlux,
            component: component,
            mainComponent: mainComponent,
            location: TestLocation
        };
    }
};

module.exports = TestContext;

Using
└──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Trace:
1) app/modules/HeaderNav.jsx renders the HeaderNav class:
TypeError: Cannot call a class as a function
at _classCallCheck (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/locations/TestLocation.js:3:106)
at Function.TestLocation (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/locations/TestLocation.js:17:5)
at Function.dispatchHandler (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:381:22)
at /Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:349:29
at /Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/Transition.js:69:9
at Function.Transition.to (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/Transition.js:72:15)
at /Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:348:22
at Function.Transition.from (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/Transition.js:51:15)
at Function.dispatch (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:345:20)
at Function.refresh (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:396:16)
at Function.run (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/createRouter.js:392:16)
at Object.runRouter [as run] (/Users/4m1r/xxxxxx/xxxxxx-web/node_modules/react-router/lib/runRouter.js:45:10)
at Object.getRouterComponent (/Users/4m1r/xxxxxx/xxxxxx-web/test/lib/TestContext.js:32:16)
at Context.<anonymous> (/Users/4m1r/xxxxxx/xxxxxx-web/test/app/modules/headerNav-test.js:26:62)
    at callFn (/usr/local/lib/node_modules/mocha/lib/runnable.js:266:21)
    at Test.Runnable.run (/usr/local/lib/node_modules/mocha/lib/runnable.js:259:7)
    at Runner.runTest (/usr/local/lib/node_modules/mocha/lib/runner.js:387:10)
    at /usr/local/lib/node_modules/mocha/lib/runner.js:470:12
    at next (/usr/local/lib/node_modules/mocha/lib/runner.js:312:14)
    at /usr/local/lib/node_modules/mocha/lib/runner.js:322:7
    at next (/usr/local/lib/node_modules/mocha/lib/runner.js:257:23)
    at /usr/local/lib/node_modules/mocha/lib/runner.js:284:7
    at done (/usr/local/lib/node_modules/mocha/lib/runnable.js:222:5)
    at callFn (/usr/local/lib/node_modules/mocha/lib/runnable.js:277:7)
    at Hook.Runnable.run (/usr/local/lib/node_modules/mocha/lib/runnable.js:259:7)
    at next (/usr/local/lib/node_modules/mocha/lib/runner.js:268:10)
    at Object._onImmediate (/usr/local/lib/node_modules/mocha/lib/runner.js:289:5)
    at processImmediate [as _immediateCallback] (timers.js:354:15)

@paulmillr Do you use coffee-react >=3.0?

To anybody having this problem: please, can you extract a reproducible example? It's hard to say what's going on because on my projects, and in examples, everything works fine. It's hard to guess by code snippets.

@adjavaherian
In your example, TestLocation is used incorrectly. It should be created individually for each test:
var location = new TestLocation([ '/test' ]);
Router.run(routes, location, function (Handler) {
  ...
});

It should not be used directly like in your example:
Router.run(routes, TestLocation, function (Handler) { // wrong

If the code that sets fields directly on TestLocation worked before, it was pure luck. It's true that the docs are lacking on it, please feel free to send a PR :-). Personally I think it might be better to export factories (createTestLocation and createStaticLocation) to prevent these kinds of mistakes. (cc @mjackson who's working on the new API)

Thanks @gaearon that helps, so I no longer get the class issue, but now I'm seeing a makeHref issue.
        var component, mainComponent,
            routes = (
                <Route name="test" path="/test" handler={targetComponent} />
            );

        //create router history
        var location = new TestLocation(['/test']);

        //run router
        Router.run(routes, location, function (Handler) {
            mainComponent = React.render(<Handler props={props} />, global.document.body);
            component = TestUtils.findRenderedComponentWithType(mainComponent, targetComponent);

        });

These warnings too
  app/modules/HeaderNav.jsx
Warning: Failed Context Types: Required context `router` was not specified in `Link`.
Warning: owner-based and parent-based contexts differ (values: `undefined` vs `function (props, context) {
      // This constructor is overridden by mocks. The argument is used
      // by mocks to assert on what gets mounted.

      if ("production" !== process.env.NODE_ENV) {
        ("production" !== process.env.NODE_ENV ? warning(
          this instanceof Constructor,
          'Something is calling a React component directly. Use a factory or ' +
          'JSX instead. See: http://fb.me/react-legacyfactory'
        ) : null);
      }

I haven't upgraded this to RR13 yet, but this repo shows the whole test suite I'm using.  If you wanna try forking that and upgrading it to 13.  https://github.com/adjavaherian/mocha-react

@adjavaherian
This guide describes the contextTypes problem you're having, as well as the solution to it.

I'm having this issue as well.
React.CreateElement has this line:
return type.apply(null, Array.prototype.slice.call(arguments, 1));
Where type is require('react-router').Route, or the following function:
function Route() {
    _classCallCheck(this, Route);
    if (_React$Component != null) {
      _React$Component.apply(this, arguments);
    }
  }

the context of this call is clearly null, which makes _classCallCheck(this, Route); throw.

React.CreateElement has this line:
return type.apply(null, Array.prototype.slice.call(arguments, 1));

As far as I can see React 0.13 doesn't contain such a line. On the other hand, React 0.12 contains it.
Which is why the current version of the router requires React 0.13. Are you sure you're using it?

That did it, thanks! Not sure why I had an older version.

If you have this issue you're either:

Using an old React version (must be >= 0.13)
Using an old JSX compiler (must be compatible with React >= 0.13)
Incorrectly using TestLocation (see the fix above)

I'm closing this issue.
If you have a reproducible example of this problem, please share it with us so we can take a look!

How can I figure out which jsx compiler version I am using ?
I have this issue reproduced right now.
My package.json dependency:
  "dependencies": {
    "express": "~3.3.4",
    "reactify": "~0.14.0",
    "react": "0.13",
    "parse": "*",
    "react-router": "0.13.3",
    "uglify-js": "~2.4.15"
  }

    var App = React.createClass({displayName: 'App',
      render: function() {
        return (
          React.DOM.div(null,
            NavigationBar(null),
            RouteHandler(null)
          )
        );
      }
    });

    var routes = (
      Route({name: "app", path: "/", handler: App},
        Route({name: "login", path: "/login", handler: LoginBox}), // ERROR
        Route({name: "signup", path: "/signup", handler: SignUpBox}),
        Route({name: "session", path: "/session", handler: EventBox}),
        DefaultRoute({handler: EventBox})
      )
    );

@toshi0383 You are using a very old version of reactify. Switch to 1.x and you'll be fine.

Thanks, it worked !

I ran into the same issue while working through a node server + react-router example. In that case, server.js was calling node-jsx.install(). I was running 0.2 of node-jsx (from the isomorphic-react example). Upgrading to 0.13.3 fixed the issue.
A generic tl;dr to this issue is "upgrade your jsx transpiler".


mopidy: add setuptools to propagatedBuildInputs

Motivation for this change
Mopidy fails to start with ImportError: No module named pkg_resources
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @fpletz

(was backported to 19.09 in https://github.com/nixos/nixpkgs/commit/5220486f44e483a76c7e83d18718cb88a69f611f)


Fix nil panic when configuration.toml can't be loaded.

Fix nil panic when configuration.toml can't be loaded.
Fixes #1814 (cherry-pick from fuji branch)
When configuration.toml can't be loaded, the
LoggingClient global variable isn't initialized,
causing main program to panic when it attempts
to log that configuration.toml can't be loaded.
This is a temporary workaround until security-proxy-setup
is migrated to the common bootstrap.
Duplicate of #2054 for master
Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>

recheck

recheck

Keep in mind this is a temporary workaround this is integrated with the common bootstrap.  The common bootstrap will handle setting up the logging object.

recheck

Codecov Report

Merging #2055 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2055      +/-   ##
==========================================
- Coverage   42.19%   42.18%   -0.01%
==========================================
  Files         184      184
  Lines       12027    12029       +2
==========================================
  Hits         5075     5075
- Misses       6655     6657       +2
  Partials      297      297

Impacted Files
Coverage Δ

internal/security/proxy/init.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Rename survey-url to schema-url

What is the context of this PR?
Renames instances of survey-url to schema-url
How to review
Check that you are able to launch a questionnaire using a schema_url.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Needs https://github.com/ONSdigital/ons-schema-definitions/pull/66


djinni on windows machine - Waiting for lock .ivy2.sbt.ivy.lock to be available.

Hi,
I got the above when running djinni on my windows machine.
Any help please,

Hi,
I managed to solve the issue by killing the processes that use the lock file.


interceptor return local json and cancel request if flag isOffline = true

Hi,
I`m trying to implement a interceptor, based on an "isOffline" flag, if is false it does the request to the actual url / if the flag is true, it doesn't do the request instead it returns the data from a local json.
What i can`t figure out is how do you cancel the request inside the interceptor and return the data from local json.
Thank you
Cheers

You could try with two interceptors. A request interceptor (on resolved) that returns a rejected promise (with a custom "offline error") and a response interceptor (on rejected) that returns a resolved promise with the offline data (when the error is an "offline error").


Audio Stops Working after few seconds of joining room

Describe the bug
I tried joining a room today and after a few seconds, the audio stopped. I tried reloading the page and after a few seconds, the audio stopped. I thought it might have something to do with that room, but when I went to a different room, the same error happened.
To Reproduce
Steps to reproduce the behavior:

Go to dogehouse dashboard
Click on any room
join and wait a few seconds
See error

Expected behavior
What I expected it to do is play the audio for that room.
What device are you on?
MacBook Pro 13" 2014
Additional context
OS: macOS 11.3
Browser: Brave Version 1.23.71 using Chromium: 90.0.4430.72

what is the error?

@benawad The problem has been fixed, though I don't know how it was fixed. The problem was that when I joined a room with my Bluetooth headset connected. The audio would stop working after a few seconds. I would reload the page and the bug would happen again. Though it is working now, and I don't know why. I will let you know if I find anything else.

Update, Audio only stops when I'm connected to my school's network, which is a problem with the school's network. Sorry for bothering you ben.


Voltage LSP Integrations

A few things to finish this off:

[x] https://github.com/MutinyWallet/mutiny-node/issues/363
[x] https://github.com/MutinyWallet/mutiny-node/issues/373
[x] Voltage CLN rebase on master: https://github.com/voltagecloud/lightning/tree/v23-05-voltage-staging
[ ] CLN to LND bug: https://github.com/ElementsProject/lightning/issues/6208
[ ] Voltage Deploys to mainnet

Blocked on any further integrations, but I worked around some of our troubles here: https://github.com/MutinyWallet/mutiny-node/pull/429
Also blocked on voltage deploying to mainnet, I think we did all we could with this ticket. No other client-related changes are expected.


Snapcraft Last updated

📋 Description
Snapcraft
Last updated | 21 June 2024
🔗 Data
IDK, however it is that the existing Snapcraft version badge works.
🎤 Motivation
It's like the other "Last Updated" badges.

Snapcraft exposes a released-at property.
I'd probably frame this one in terms of release date rather than "last update".
This is exposed at the track / risk level so would need those params like the snapcraft version badge.

@chris48s I'd like to work on this, how do I get started

There is a tutorial for adding new badges at https://github.com/badges/shields/blob/master/doc/TUTORIAL.md
The code for the existing snapcraft version badge is at https://github.com/badges/shields/tree/master/services/snapcraft
You might also find it useful to refer to the PR adding at that badge at https://github.com/badges/shields/pull/9976

Is this issue still open?

yep


fix(MetadataDiscovery): prevent "Cannot read property 'name' of undefined" from obscuring the fromWrongReference MetadataError

I haven't created a bug ticket for this, but I did explain the problem in this Slack thread.

Codecov Report

Merging #3085 (6476f99) into master (8da69d7) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #3085   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          193       193
  Lines        11881     11883    +2
  Branches      2742      2743    +1
=========================================
+ Hits         11881     11883    +2

Impacted Files
Coverage Δ

packages/core/src/metadata/MetadataDiscovery.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

@B4nan I made your suggested change.
I'm going to hold off on writing a test for this until I can fix my own bug.

this is coming from wrong decorator usage, right?

I'm still running into the underlying error. So I do not know where this is coming from. Which is a part of the reason why I'm not in a position to write a test.

Dropping this in hopes this could possibly reproduce the issue later:
import { Field, ObjectType } from '@nestjs/graphql';

import {
  Collection,
  Entity,
  IdentifiedReference,
  ManyToOne,
  OneToMany,
} from '@mikro-orm/core';

import { MyBaseEntity } from '@my/entities';

@ObjectType()
@Entity()
export class OpsManagerService extends MyBaseEntity <OpsManagerService> {
  @OneToMany({
    entity: () => OpsManagerEnvironmentService,
    mappedBy: 'opsManagerService',
  })
  public opsManagerEnvironmentServices = new Collection<OpsManagerEnvironmentService>(
    this
  );
}

@ObjectType()
@Entity()
export class OpsManagerEnvironmentService extends YellowBrimBaseEntity<OpsManagerEnvironmentService> {
  @ManyToOne({
    entity: () => OpsManagerService,
    eager: true,
    wrappedReference: true,
    inversedBy: 'opsManagerEnvironmentServices',
  })
  @Field(() => OpsManagerService, { nullable: false })
  opsManagerService: IdentifiedReference<OpsManagerService>;
}

Hmmm.... seems that Mikro has some inconsistencies with its path-to-class attribute. I'm console logging out everything that comes into the validate bidirectional functions, and I'm seeing two different path types:
One entity's path is the bundle: main.js
The other's path is a webpack path: webpack:/ops-manager/libs/domain/src/lib/ops-manager-environment-service/entities/ops-manager-environment-service.entity.ts

I was asking for a unit test case, not sure what that (very incomplete) entity definition should reproduce... Also hearing about webpack, the path to entity is irrelevant in there.
Let's merge, the change is definitely not problematic, it can't break anything, so I am fine merging without tests.

@B4nan I understood your request, but I didn't have time yesterday to task switch, as I am still attempting to debug the underlying error that I ran into. I'm only seeing it in production, and so I was just dropping notes above on what I think might be causing it.
Glad it was okay enough to merge.


WIP: e2e: run via go-run by default, GORUN_FIXTURE=0 for opt-out from Makefile

Blocked on https://github.com/golang/go/issues/40467.

Is it necessary or desirable long-term that our e2e suite be responsible for starting servers? vs requiring test servers be started before the test run, which presumably could use go run and maybe not run into this issue?


I cant load a weapon Mesh

Hey, I have a problem. I bought this plugin on roblox and I dont know how to use it. I watched tutorial by AlvonBlox from 2017 but everything is different now, is there any good tutorial for this?
Sincerely, Reiv21

you got scammed hard if you paid for this


Query data rework

Hi @sanderson , here's my initial rough draft. Can you let me know what needs to be fixed? Thanks so much!

I also think we need more context here.  Like at the bottom we had the InfluxQL paragraph which points folks off to the scheme exploration guide...  We need similar pointer for Flux... I think?

@timhallinflux -- I cut out some unnecessary details, but it's still about 50% InfluxQL example. The InfluxQL heading starts at line 53.

I also think we need more context here. Like at the bottom we had the InfluxQL paragraph which points folks off to the scheme exploration guide... We need similar pointer for Flux... I think?

@timhallinflux tim Added these in for both

ok. ship it.  We'll likely continue to iterate.


Uploading blob with container client fails with auth error but succeeds with blob client when using Azure CDN

Package Name: azure-storage-blob
Package Version: 12.9.0
Operating System: Windows 10
Python Version: 3.10.2

Describe the bug
I have an Azure Storage account that is configured with an Azure CDN. When using BlobServiceClient with the account URL set to an Azure CDN, uploading a file using the container client fails with an authentication error, while it succeeds when using a blob client.
Both succeed when the account URL is set to the actual Storage Account URL.
To Reproduce
Steps to reproduce the behavior:
from azure.storage.blob import BlobServiceClient

edge_url = 'https://edgeaccount.azureedge.net'
storage_url = 'https://account.blob.core.windows.net'
service = BlobServiceClient(account_url=edge_url, credential={'account_name': 'abc', 'account_key': 'xyz'})

blob_client = service.get_blob_client('container', 'blobname')
container_client = service.get_container_client('container')

with open("./testfile", "rb") as stream:
    # This succeeds
    blob_client.upload_blob(stream, overwrite=True)
    # This fails with authentication error
    container_client.upload_blob('blobname', stream, overwrite=True)

Authentication error
authenticationerrordetail:The MAC signature found in the HTTP request '5dC3N7RcRW9V...' is not the same as any computed signature. Server used following string to sign: 'PUT

1

application/octet-stream

x-ms-blob-type:BlockBlob
x-ms-client-request-id:xxxx
x-ms-date:Mon, 21 Feb 2022 07:34:35 GMT
x-ms-version:2020-10-02
Content: <?xml version="1.0" encoding="utf-8"?><Error>AuthenticationFailed<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed
correctly including the signature.
RequestId:xxx
Time:2022-02-21T07:34:35.1058206Z</Message><AuthenticationErrorDetail>The MAC signature found in the HTTP request '5dC3N7RcRW9V...' is not the same as any computed
signature. Server used following string to sign: 'PUT

Expected behavior
The container client should upload the blob successfully.

Hi @JeffreyCA, thanks for reporting this. We will look into it and get back to you.

Hi again @JeffreyCA, I have tried out your sample with an Azure CDN configured on a Storage Account and was not able to reproduce the auth error. Both the BlobClient and ContainerClient method worked as expected with no errors. I tried a couple different combinations of how the container was initially created, etc.
Is this a consistent or intermittent? Is there anything special (outside of default) configured on your Storage Account or CDN? I was testing with a pretty much default Storage Account and CDN configuration.
Could you share a recent request id from a failed request? I can look at it on the service side to see if that reveals anything. (The more recent, the better, since the service logs roll over fairly quickly, ~2 days)

Yes I managed to save one request: d81ed268-301e-0068-63f7-263995000000
Content: <?xml version="1.0" encoding="utf-8"?><Error>AuthenticationFailed<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
api_1          | RequestId:d81ed268-301e-0068-63f7-263995000000
api_1          | Time:2022-02-21T07:46:18.3875170Z</Message><AuthenticationErrorDetail>The MAC signature found in the HTTP request 'Ge9LF9U/IxrXWwnRDkxLL5+JCv/Sz2kGIbEmVG9SWR0=' is not the same as any computed signature. Server used following string to sign: 'PUT
api_1          |
api_1          |
api_1          | 109264
api_1          |
api_1          | application/octet-stream
api_1          |
api_1          |
api_1          |
api_1          |
api_1          |
api_1          |
api_1          | x-ms-blob-content-disposition:attachment
api_1          | x-ms-blob-content-type:audio/mpeg
api_1          | x-ms-blob-type:BlockBlob
api_1          | x-ms-client-request-id:5ab7e560-92ea-11ec-9174-0242ac120006
api_1          | x-ms-date:Mon, 21 Feb 2022 07:46:18 GMT
api_1          | x-ms-version:2020-10-02
api_1          | /spleeterweb/gpu/uploads/dd50891f-cd77-48f6-aef1-76f5d928cb20/a.mp3
api_1          | timeout:20'.</AuthenticationErrorDetail></Error>

Hi @JeffreyCA Jeffery, unfortunately the service logs for this request have rolled over (I did check soon after you provided it). Are you able to reproduce the issue again and provide another request id? Thanks

Hi @JeffreyCA Jeffery, unfortunately the service logs for this request have rolled over (I did check soon after you provided it). Are you able to reproduce the issue again and provide another request id? Thanks

No I'm not able to reproduce it anymore

@JeffreyCA so the issue is no longer happening and requests to the CDN endpoint are working as expected now?
If that is the case, I would probably say this was an intermittent issue with the service. Perhaps it took longer than expected for your CDN settings to take affect or there was a problem on the backend that got resolved.

Looks like this may have been a service issue that recovered. I'm going to close this but please feel free to re-open if this reoccurs. Thanks.


The overflow in  the viewport of report filters is fixed Issue#8929

Fixed https://github.com/wagtail/wagtail/issues/8929
Only changed file https://github.com/wagtail/wagtail/blob/main/client/scss/components/_filters.scss

https://user-images.githubusercontent.com/71623442/183364166-7ba4cdaf-5dde-438c-acf2-25033a3a3bfa.mp4
Preview of the output.

@PaarthAgarwal  have a look at this change in the context of investigating the form submission listing issue.

yep - the other thing that was needed was to go from sm to md breakpoint for the breakpoint where the content wraps into one column, there was no practical way it could all fit when the sidebar was expanded.
Thanks for your help on this!

@PaarthAgarwal  when you get a chance, please check out the latest main now and confirm there is no longer an issue with the form submission listings as discussed today.

@lb- any update on the PR https://github.com/wagtail/wagtail/pull/8960 ?

Not yet - only a mere human volunteer - will get to it when I get the chance :) otherwise another core team member will in due course.


Update irreps.py: New point group

I completed another point group (Ci).

Thanks. I merged it to the master branch. I don't have a test case for Ci. If you have it, to make it sure, please test the latest master branch of phonopy.

I have tested the latest master branch. It works as expected. I get the correct number of irreducible representations and also the correct labels for my example.

I see. Thanks.


Add huawei cloudeye exporter

Signed-off-by: zhongjun2<EMAIL_ADDRESS>

Thanks!
The metric name prefix should not be configurable, and I'd also advise against munging of label names.

Thanks brian-brazil!  " I'd also advise against munging of label names. " ----- Where I can find what label I can use, what label I can not use? Is there a link or something else?

I'm looking at https://github.com/huaweicloud/cloudeye-exporter/blob/master/collector/collector.go#L30
https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels are the docs, if there are invalid characters you'd usually change them to underscores.

Got it, thanks brian-brazil!


Upgrade to python 3.6

Upgrade to python 3.6

Codecov Report

Merging #195 into data-platform-upgrade will increase coverage by 0.00%.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##           data-platform-upgrade     #195   +/-   ##
======================================================
  Coverage                  68.62%   68.63%
======================================================
  Files                        143      143
  Lines                      11411    11411
======================================================
+ Hits                        7831     7832    +1
+ Misses                      3580     3579    -1

Impacted Files
Coverage Δ

airflow/models.py
85.98% <0.00%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

@astahlman @ArgentFalcon @youngyjd

👍 Well that was easy

Can we aim this at airflowinfra branch? I think that's the branch that airflowinfra uses.

@ArgentFalcon I think the plan is to upgrade the etl repo in place to PY3 without upgrading airflow versions. I believe airflowinfra is already on 3.6 based on https://github.com/lyft/incubator-airflow/blob/airflowinfra/.travis.yml#L29

Oh, I see, thanks for clairfying


Code Snippet Missing 'left' for Off-Canvas

Yo Rafi!
In the code snippet for the off-canvas panel and button, the IDs don't match. As a result, the button doesn't trigger the panel to slide. The panel ID is offCanvas and the button toggle is offCanvasLeft. See http://foundation.zurb.com/sites/docs/off-canvas.html#complete-example + Click Trigger section.
<3

@mandimey - would you like to submit a Pull Request to fix this?

Hi @mandimey would you have the time to provide a PR and need any assistance or can I provide a PR?

Closimg as this was fixed with https://github.com/zurb/foundation-sites/pull/10981


Introduce Async Appending Benchmark

Introduce Benchmarks for Async configured logging systems, like logback, log4j, logstash etc

Include coretto 17 System.Logger async


Endpoint remedy

In reference to issue #1027
Endpoints can be remediated or deleted individually or in bulk. Reports will now reflect differences between remediated and vulnerable endpoints by separating endpoints into different sections.
While tweaking reports, I followed advice given here and corrected the behavior of private notes. The notes section of a report will only appear if there is at least one public note. The section will not appear at all with exclusive private notes or no notes at all.

[x] Your code is flake8 compliant
[x] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[x] Model changes must include the necessary migrations in the dojo/dd_migrations folder.
[ ] Add applicable tests to the unit tests.

@aaronweaver  would you please provide feedback?


add Python support

cc @ingenieroariel
Add support for integration downstream Python applications.

This would be very useful for persisting the side effects of a JupyterLab notebook into a noise knowledge graph.


Update to pouchdb-utils and pouchdb-adapter-websql-core 6.1.1

fixed by https://github.com/nolanlawson/pouchdb-adapter-cordova-sqlite/pull/21


ClangImporter: Support for subclass existentials

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 5dba1e839c540db90d65089e10e2459d524e02f1
Test requested by - @slavapestov

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 5dba1e839c540db90d65089e10e2459d524e02f1
Test requested by - @slavapestov

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 5dba1e839c540db90d65089e10e2459d524e02f1
Test requested by - @slavapestov

@swift-ci Please clean test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - de67234c28359543c1f73ffc5f113cbaf030dcc2
Test requested by - @slavapestov

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - de67234c28359543c1f73ffc5f113cbaf030dcc2
Test requested by - @slavapestov

@swift-ci smoke test Linux

@aciidb0mb3r Can you take a look at the Linux test failure here? https://ci.swift.org/job/swift-PR-Linux/6876/consoleFull#-5114079ee1a197b-acac-4b17-83cf-a53b95139a76

Ah, that was a non-deterministic test. It was fixed by: https://github.com/apple/swift-package-manager/pull/1097

Thanks!


thunderbird-unwrapped: 115.7.0 -> 115.8.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for thunderbird-unwrapped is: A full-featured e-mail client
meta.homepage for thunderbird-unwrapped is: https://thunderbird.net/
meta.changelog for thunderbird-unwrapped is: https://www.thunderbird.net/en-US/thunderbird/115.8.0/releasenotes/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 115.8.0 with grep in /nix/store/51k39ksq4c9gqqlhgzbkfph9g92d5alc-thunderbird-unwrapped-115.8.0
found 115.8.0 in filename of file in /nix/store/51k39ksq4c9gqqlhgzbkfph9g92d5alc-thunderbird-unwrapped-115.8.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
thunderbird-unwrapped
thunderbirdPackages.thunderbird
thunderbirdPackages.thunderbird-115

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/51k39ksq4c9gqqlhgzbkfph9g92d5alc-thunderbird-unwrapped-115.8.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A thunderbird-unwrapped https://github.com/r-ryantm/nixpkgs/archive/33893ac9033f109effe7e2db8cb867295806d8b3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/33893ac9033f109effe7e2db8cb867295806d8b3#thunderbird-unwrapped

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/51k39ksq4c9gqqlhgzbkfph9g92d5alc-thunderbird-unwrapped-115.8.0
ls -la /nix/store/51k39ksq4c9gqqlhgzbkfph9g92d5alc-thunderbird-unwrapped-115.8.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

thunderbird
thunderbird-unwrapped

Maintainer pings
cc @edolstra @lovesegfault @nbp @vcunat for testing.

It works for me.  I think we can merge this to master fast.


Misleading Description for MvcHtmlString.Create()

The description of the function MvcHtmlString.Create() is misleading as it states that it:

Creates an HTML-encoded string using the specified text value.

But instead, it is decoding an already HTML-encoded string and if you pass an HTML string to it, it simply outputs its HTML.
For eg:
@MvcHtmlString.Create("i am <bold>")
will output an decoded HTML code:

I am Bold

and if we input an simple HTML string like:
@MvcHtmlString.Create("I am <b>bold</b>)
again it is written as a normal HTML code:

I am Bold

instead of i am <bold>
Please fix the description as it confuses to whoever is using it.

@vikscool Moved to that repo https://github.com/aspnet/ApiDocs/issues/127


feat(chat): Multiple chatting characters in order

If there were more than just 2 characters, we could do a lot more cool things:

Inner monologue could be formatted with its own unique prefix like the original paper did (https://innermonologue.github.io/).
Recurring context clues.
Narration.
Multiple characters, obviously.

Let's restrict this feature to a simple rotating order for now and make sure it can be changed with on the fly with a command.

Perhaps these lines should be optionally transient and disappear. This this feature could subsume #5.
This and some other things are blocked on real sxproto parsing, so I'll be prioritizing that in https://github.com/fildesh/fildesh/issues/135.

Let's just say these are all the confidant's line prefixes. I don't know if it's a good idea to bother making them optional or mutable during chat, so I won't.
((confidant_prefixes) "{{char}} thinks:" "{{char}}:")

I'm getting good results. Going to make the setting include the protagonist prefix too.
((chat_prefixes) "{{user}}:" "{{char}} feels:" "{{char}} wants:" "{{char}} plans:" "{{char}}:")

Needs an example and documentation.

I think this needs to be an array of messages instead. Something like:
((chat_prefixes)
 (() (key "{{user}}:"))
 (() (key "{{char}} goal:"))
 (() (key "{{char}}:")))

Or maybe we can just accept the current format of ((chat_prefixes) "{{user}}:" "{{char}} goal:" "{{char}}:") in the long term alongside the message-array one.

Here how about we split the difference. Let's use manyof syntax so the 2 work:
(((chat_prefixes))
 "{{user}}:"
 ((inner_monologue)
  (prefix "{{char}} goal:")
  (rollforget_keep_count 4)
  (repeat_window 0))
 "{{char}}":")

The 2-"person" mode (protagonist & confidant) now functions the same as the multiple character case.


Fixed Mixed Reality Toolkit service registration & unit tests

Overview
Fixed all unit tests and made sure we're registering the correct interfaces by adding a debug error check in MixedRealityToolkit registration
Changes

Fixes: #2972
Fixes: #2979

Going to close this until service serialization is fixed


Trap focus no longer loses focus when clicking on non-tabbable elements

Linked Issue
Fixed #1613
Description
Instead of adding event listeners to each child, I added 1 keydown listener to the dom, this prevents adding and removing listeners every time the targeted node has changes (observed by the MutationObserver). The main reason I did this is to add 1 more check after Shift + Tab and Tab have been checked: Now when both tab scenario's were falsy focusTrap will do 1 additional check to check wether the currently active element is not inside the targeted node, if not it will focus the first child inside the targeted node again. This utilizes document.activeElement which will return the current active element (like the name suggests). This way when a user clicks on an element that is not tabbable and hits tab after, it will first check if that element is part of our focusableChilds list, if not it will prevent the user from tabbing (e.preventDefault()) and instead focus the firstFocusableChild (determined by the MutationObserver).
Edit (Important note):
After discussing with @endigo9740 and @Mahmoud-zino we've decided to make the behaviour I implemented optional by user, this ensures modals can be focused without escape and forms can be escaped if the users wishes to. Because that would introduce a breaking change we've decided to, for the time being, allow a data-strict-focus attribute to be set on the node focus trap is applied to, it will look like:
<div use:focusTrap={true} data-focus-strict>

The focus trap action will respect this prop and focus strictly (no escape) if the attribute is set. This will be removed when Skeleton Version 2 hits and instead will be part of a parameter passed on to the focusTrap action. So it will convert from:
export function focusTrap(node: HTMLElement, enabled: boolean);

to:
export function focusTrap(node: HTMLElement, {enabled: boolean, strict?: boolean});

Read the discussion: https://discord.com/channels/1003691521280856084/1003699523522142399/1113897699687796848
Changsets
Changesets automate our changelog. If you modify files in /package/skeleton, run pnpm changeset, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[x] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[x] Ensure code linting is current - run pnpm format
[x] All test cases are passing - run pnpm test
[x] Includes a changeset (if relevant; see above)

@Hugos68 This looks like a pretty big rewrite of the action. I'm going to have to set aside some time to review in the near future. Unfortunately I can't provide an ETA, but this will be asap.
For now I'll ask @Mahmoud-zino to come in as a guest and peer review if/when he can. Just try to poke holes and highlight any obvious issues we might run into.
Thanks guys.

Ofcourse, I tried my best documenting the code why and when it would run, since I can understand rewrites like this coming from another person is sometimes hard to understand. No worries it's not a breaking bug, just a minor inconvenience thus no rush required.

@Hugos68 I know this is still marked in the draft state, but wanted to provide a couple bits of feedback early on:

You've moved focusableElementSelector, getFirstAndLastFocusableChild, and isFocusStrict outside the Action function. Given these are all related directly to the action I'd recommend we keep those embedded within the function. Treat it a bit like methods for a Class. Best to co-locate those.
As a stylistic choice we group "add listeners" statements near the bottom of the action, just above the return statement. This provides some consistency and makes it easy to scan and ensure every listeners added is removed in the destroy() method.
Do me a favor and add a comment near the top of the file that says "DEPRECATED: replace the enabled argument with {enabled: boolean, strict?: boolean} in v2." I'll be scanning the doc for references to  DEPRECATED when we make this change so this is just a helpful reminder. Technically it's not deprecated, just a temporary solution.

Given a couple folks have had their hands on this, some of this may not be from you - but if you don't mind helping us correct this while you're in progress please!

@Hugos68 I know this is still marked in the draft state, but wanted to provide a couple bits of feedback early on:
1. The `focusableElementSelector`, `getFirstAndLastFocusableChild`, and `isFocusStrict` constant and functions are outside the Action function. Given these are all related directly to the action I'd recommend we keep those embedded within the Action please. Treat these like properties and methods for a Class. Best to co-locate those.

2. As a stylistic choice we group `addEventListener()` statements near the bottom of the action, just above the `return` statement. This provides some consistency and makes it easy to scan and ensure every listener added is removed in the `destroy()` method.

3. Do me a favor and add a comment near the top of the file that says "DEPRECATED: replace the `enabled` argument with `{enabled: boolean, strict?: boolean}` in v2." I'll be scanning the doc for references to  `DEPRECATED` when we make this change so this is just a helpful reminder. Technically it's not deprecated, just a temporary solution.

Given a couple folks have had their hands on this, some of this may not be from you - but if you don't mind helping us correct this while you're in progress please!

I moved them outside because I am pretty sure they are being created now for every instance of focus trap whilst in reality is a function that can be used by any focus trap, I'll happily move it back though, that is just my way of doing stuff.

Sure thing, on it.

Will do 👍

Currently 2 elements that both have action: use:focusTrap={true} and attribute: data-focus-strict will break the tabbing ability of the user causing them to be stuck. To fix this issue (because it HAS to be fixed) I have 2 suggestions in mind:
Suggestion A:
We implement a Stack, this will basically ensure all elements on the current page, this will work like the following:
Element A with  action: use:focusTrap={true} and attribute: data-focus-strict gets added to the DOM the stack will then look like:
const stack = [A];

Then element B with  action: use:focusTrap={true} and attribute: data-focus-strict gets added to the DOM the stack will then look like:
const stack = [A, B];

Then whenever the isFocusStrict(); method gets called element B will take higher precedence over element A because it was added later to the stack, therefor only element B will be strictly focused. When one of these nodes are destroyed they are removed from the stack by calling the following method in the destroy function:
removeStrictlyElement()
Suggestion B:
We still implement the same stack like in suggestion A but instead of preferring one over another based on when they were added to the DOM we prefer one over another based on z-index, this will look something like this:
Element A with  action: use:focusTrap={true}, attribute: data-focus-strict and z-index: 10 gets added to the DOM the stack will then look like:
const stack = [A];

Then element B with action:use:focusTrap={true}, attribute: data-focus-strict and z-index: 5 gets added to the DOM the stack will then look like:
const stack = [A, B];

Then whenever the isFocusStrict(); method gets called element A will take higher precedence over element B because element A has a higher z-index value than element B so Element A will be strictly focused. Again when one of these nodes are destroyed they are removed from the stack by calling the following method in the destroy function:
removeStrictlyElement()
I'd love to hear feedback or other solutions 👍, FYI I've implemented A for now since it firstly came to mind and tabs are broken with the current PR.

@Hugos68 another suggestion to consider:
join all focusable elements from both focus traps (or all visible focus traps with data-focus-strict) in one array and handle them as one focus trap.

@Hugos68 another suggestion to consider: join all focusable elements from both focus traps (or all visible focus traps with data-focus-strict) in one array and handle them as one focus trap.
Lets say we have a modal with strict focus trap and another modal on top, how would that handle the focus trap in that scenario? Because we don't want the user to be able to tab behind the top modal, but from what I understand from your suggestion we basically combine both, but would that no cause the tab to go behind the modal in front?

yeah, you are correct on this one, I didn't though about two modals on top of each other but about a modal having a form inside it. there is a lot to consider here and a huge amount of edge cases to cover.

yeah, you are correct on this one, I didn't though about two modals on top of each other but about a modal having a form inside it. there is a lot to consider here and a huge amount of edge cases to cover.

I can't think of any other "normal" patterns then modal on modal, any other situation the developer shouldn't really use 2 focus traps on the same screen for the user to see, so I would say any other edge case is just a anti pattern created by the develepor.

Current bug/not desired behaviour: When 2 elements are created at the same time and one is a child of another so:
<div use:outer>
  <div use:inner>

  </div>
</div>

The inner action will fire first, this means using the stack the outer div will be the one who takes the strictly focus even though we (and most consumers) will want/expect inner to be focused strictly. This is because upon dom creation the most inner childs are created before their parents thus the action of inner will be triggered first. I'm not sure how to tackle this problem, suggestions are absolutely welcome.

@Hugos68
cause of behavior:

The order of execution of onMount and the initial afterUpdate is that children execute before their parent. This makes sense because conceptually each child needs to be mounted before the parent can complete its mount.

I agree with you, I think we should not handle this hell of edge cases, but display a clear and easy-to-see warning that the dev should only do this once in a visible area and that we are already using it in modals so no need to do it there.

@Hugos68 cause of behavior:

The order of execution of onMount and the initial afterUpdate is that children execute before their parent. This makes sense because conceptually each child needs to be mounted before the parent can complete its mount.

I agree with you, I think we should not handle this hell of edge cases, but display a clear and easy-to-see warning that the dev should only do this once in a visible area and that we are already using it in modals so no need to do it there.

I was thinking to completely remove the data-strict-focus thing and just leave the focus trap as is, less headache for maintainers and seems like all the other websites have the same "bug" so it's just how things work honestly

Yup sounds good, this PR doesn't have any value if the inert turns out anything like how we expect it to.

Cool, well again we can reference it and use it going forward. But I'm going to close it for now to help prune our PR pile a bit. Thanks Hugos!


[19.03 backport] For ipvlan tests check that the ipvlan module is enabled

backport of https://github.com/moby/moby/pull/39358 for 19.03

experimental:
00:25:34.590 Running /go/src/github.com/docker/docker/integration/network/ipvlan
00:25:35.198 INFO: Testing against a local daemon
00:25:35.198 === RUN   TestDockerNetworkIpvlanPersistance
00:25:35.218 --- SKIP: TestDockerNetworkIpvlanPersistance (0.02s)
00:25:35.219     ipvlan_test.go:27: !ipvlanKernelSupport(t): Kernel doesn't support ipvlan
00:25:35.219 === RUN   TestDockerNetworkIpvlan
00:25:35.220 --- SKIP: TestDockerNetworkIpvlan (0.00s)
00:25:35.220     ipvlan_test.go:55: !ipvlanKernelSupport(t): Kernel doesn't support ipvlan
00:25:35.221 PASS

janky:
00:27:20.107 Running /go/src/github.com/docker/docker/integration/network/ipvlan
00:27:20.136 INFO: Testing against a local daemon
00:27:20.137 testing: warning: no tests to run
00:27:20.137 PASS


Only one line displayed in dialog content (IE 11)

Hi,
there will only one line displayed in the dialog content, for example the confirm dialog of your documentation. (tested in IE 11)
Thank you

When this happens? Only for the confirm Dialog on the documentation?

The confirm and prompt dialog

Same with

As a quick workaround I suggest using css:
.md-dialog, .md-dialog-content, .md-dialog-actions {   background-color: white !important; }

To clarify, the background property of .md-dialog-content is quiet fuzzy to me. I don't get why there are so many values for just a white background ;), but the issue same to be related to those values.
linear-gradient(180deg,#fff 0,#fff 1px,transparent 0),linear-gradient(0deg,#fff 0,#fff 3px,transparent 0),linear-gradient(180deg,rgba(0,0,0,.12) 0,rgba(0,0,0,.12) 1px,transparent 0),linear-gradient(0deg,rgba(0,0,0,.2) 1px,rgba(0,0,0,.2) 2px,transparent 0)

This color is not for the background itself, but for the scroll border trick.

#184


BE-10: [API] Implementation of Logout Endpoint #199

What's up?
We should start implementing our API endpoints related to Registration/Login System. We'll be using Postman to test our endpoints and then provide the necessary details to the Frontend team via Google Docs.
To Do

[ ] Implement the API endpoint: http://{host}/api/v1/auth/register/
[ ] Document it in the Google Docs (created in BE-7 API Documentation with FE team  #193) in detail.
[ ] Write unit tests for the helper functions (if any)

Deadline
25.10.2022 @17.00
Additional Information
No response
Reviewers
@KarahanS

Implemented Logout API with know_views and documented it on the API documentation doc.
PR for the implementation is reviewed and merged.


Application deployed not accessible from browser

Following the instructions from https://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/blob/master/docs/guidance.md,  the bosh and cloud foundry deployment completed successfully. I was also able to push the sample application to the cloud foundry instance but unable to reach deployed application from the browser. cf app shows the app as running successfully.
What could cause this issue? Seems to be something to do with routes of the public IP.

Which domain name are you using in your cf manifest? If you are using Azure template to deploy your environment, you should access your application in your browser by this URL https://YOUR-APP-NAME.CF-PUBLIC-IP.xip.io

@AbelHu : Thank you, I used the azure template, so I have to use the IP, I didn't register a domain name. The documentation says http://game-2048.REPLACE_WITH_CLOUD_FOUNDRY_PUBLIC_IP.xip.io/  should work but it doesn't. The https:// link shows the cert warning but comes up.

Have you pushed the app game-2048?
You can type 'cf apps' to check the status of your app and find the URL to access.
You should ignore the cert warning and continue to access it in the browser.
Best Regards,
Abel HU
Sent from my iPhone
? 2016?4?22??21:44?Madhuri Gummalla <notifications<EMAIL_ADDRESS>???
@AbelHuhttps://github.com/AbelHu : Thank you, I used the azure template, so I have to use the IP, I didn't register a domain name. The documentation says http://game-2048.REPLACE_WITH_CLOUD_FOUNDRY_PUBLIC_IP.xip.io/https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgame-2048.REPLACE_WITH_CLOUD_FOUNDRY_PUBLIC_IP.xip.io%2F&data=01|01|Chou.Hu%40microsoft.com|984156c7b85544ddb9b708d36ab43029|72f988bf86f141af91ab2d7cd011db47|1&sdata=XAYFxZRTNdl67xfkBvdycRdu%2BlarPee%2Bop2Yq6KhcLM%3D should work but it doesn't. The https:// link shows the cert warning but comes up.

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/cloudfoundry-incubator/bosh-azure-cpi-release/issues/129#issuecomment-213433304

Yes app is deployed and cf apps shows the status as running. You can see it at https://game-2<IP_ADDRESS>.150.xip.io/

@madhurig After CF is deployed, you can use any other machine to deploy your apps.

@AbelHu thank you, I am able to access the cf deployment.


Crates.io not updated for more than a year

Hello,
The last crate version on crates.io is from more than a year ago. Some features, like map_with_owner, are missing. Can you update please ?
Thank you

Thanks, published as v0.4.1


fix(codegen): format new expession + import expression with the correct parentheses

Similar to #2330

Current dependencies on/for this PR:

main

PR #2346   👈

This stack of pull requests is managed by Graphite.


Don't apply default Select.filterFn in async mode

Fixes #2192

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

See ticket for details on replicating and how this manifested in FilterChooser.
Note that mobile Select does not support async, so N/A there.

@lbwexler I'm going to go ahead and merge this as I would like to get it into a snapshot for a client app release prior to additional QA next week. Of course please give a shout if anything looks off or in need of further investigation!

looks good

not critical, but had to look up my "order of precedence" to see that && has precedence over ||.  Might benefit from an explicit additional set of parenthesis, but this looks to be doing what you intend


Fix missing medium compatibility color

Closes #579. Decided to change med to medium to match low and high. Fully words == less ambiguity …generally.

Coverage remained the same at 99.81% when pulling d07a293e803af7ac9b56d5bbe5ade447e0ab491d on warpling:master into 393ecf15789d4faa835e80eb4880e146ff73a9ce on openfarmcc:master.


FAILED to initialize Bus

Same as issue #46
Launching LSS for 2nd time.
INFO config file detected path=/home/user/.config/Ledger Live/lss.json
FATAL Failed to initialize bus
error=failed to load wallet: -4: wallet file verification failed. Refusing to load database. Data file '/bitcoin/.bitcoin/satstack/wallet.dat' is already loaded

I have a similar issue on a new install.
lss.exe
←[90m[2021/04/22 - 19:39:56]←[0m ←[32m INFO←[0m Ledger SatStack (lss) v0.12.0                 ←[32march←[0m=windows amd64 ←[32mbuild←[0m= ←[32mcommit←[0m= ←[32mruntime←[0m=go1.15.5
←[90m[2021/04/22 - 19:39:56]←[0m ←[32m INFO←[0m Config file detected                          ←[32mpath←[0m=C:\Users\user/AppData/Roaming/Ledger Live/lss.json
←[90m[2021/04/22 - 19:39:56]←[0m ←[32m INFO←[0m Warming up...
←[90m[2021/04/22 - 19:39:56]←[0m ←[31mFATAL←[0m Failed to initialize Bus                      ←[31merror←[0m=failed to detect txindex: failed to get block

This can be 'fixed' by running bitcoin-cli unloadwallet satstack on the node running bitcoind.
Note: When bitcoind is still syncing / rescanning addresses for this wallet this may take a while to complete (and unload).

Hm, still needed to restart bitcoind to get it 'fixed' -.-

The unloadwallet command does not seem to work for me:
./bitcoin-cli unloadwallet "satstack"
error code: -18
error message:
Requested wallet does not exist or is not loaded

./bitcoin-cli unloadwallet satstack
error code: -18
error message:
Requested wallet does not exist or is not loaded

The unloadwallet command does not seem to work for me:
./bitcoin-cli unloadwallet "satstack"
error code: -18
error message:
Requested wallet does not exist or is not loaded

./bitcoin-cli unloadwallet satstack
error code: -18
error message:
Requested wallet does not exist or is not loaded

Same issue for me: Requested wallet does not exist or is not loaded.

This issue is not fixed as of 0.17.0
Instantly crashes on startup.
[2022/12/01 - 17:35:33]  INFO Ledger SatStack (lss) v0.16.1                 arch=windows amd64 build= commit= runtime=go1.17.13
[2022/12/01 - 17:35:33]  INFO Config file detected                          path=C:\Users/<>/Ledger Live/lss.json
[2022/12/01 - 17:35:33]  INFO Warming up...
[2022/12/01 - 17:35:36] FATAL Failed to initialize Bus                      error=failed to load wallet: -35: Wallet file verification failed. Refusing to load database. Data file '/bitcoin/.bitcoin/satstack/wallet.dat' is already loaded.

[process exited with code 1 (0x00000001)]

Seems that this issue is not fixed as of 0.17.0
Instantly crashes on startup.
[2022/12/01 - 17:35:33]  INFO Ledger SatStack (lss) v0.16.1                 arch=windows amd64 build= commit= runtime=go1.17.13
[2022/12/01 - 17:35:33]  INFO Config file detected                          path=C:\Users/<>/Ledger Live/lss.json
[2022/12/01 - 17:35:33]  INFO Warming up...
[2022/12/01 - 17:35:36] FATAL Failed to initialize Bus                      error=failed to load wallet: -35: Wallet file verification failed. Refusing to load database. Data file '/bitcoin/.bitcoin/satstack/wallet.dat' is already loaded.

[process exited with code 1 (0x00000001)]

Manually unloading the wallet worked for me, but is cumbersome since it requires opening a docker shell etc in my scenario
bitcoin-cli unloadwallet satstack

a node restart would also solve this usually

Sub-optimal to have to use CLI to restart the node if it's i.e. running on another host under docker. Couldn't we ask the user if they want to try unloading the wallet when this error appears?

Sub-optimal to have to use CLI to restart the node if it's i.e. running on another host under docker. Couldn't we ask the user if they want to try unloading the wallet when this error appears?
I also discovered lss --unload-wallet works so that functionality is already there, it seems

yes this is why we added the unload wallet

hello, this is my 2nd time reaching about 60% progress and me getting this error. any update on how to resolve?
i just created an account here, i am not technical at all so simple steps to resolve would be greatly appreciated.


Recurrent Convolution Model : how to get past the tensor dimension limit ?

Description
Hi,
With my company, Vitirover, we have a mower robot navigating on a vineyard. We trained some convolutional models for obstacle detection, and it is working great. The input is an image, and the output are classes of obstacles (or no obstacles)
However, our robot sometimes hits obstacles that are invisible now (not in the immediate detection field), but were visible a few seconds ago. So we would like to use a recurrent convolutional model to do this
My model input shape would be [ Sequence of images, Height, Width, Channels  ], which needs 4 dimensions.
But the documentation says Tensors are either 1-, 2-, or 3-dimensional.
So my questions are :

Is it possible that on the future, more than 3 dimensions could be allowed ? Is this a software limitation or a hardware one ?

Does the new append_recurrent_links utility help here by allowing us to input only one image at a time (only three dimensions) and saving the "state" part internally ? Even if theoretically the model itself would still be 4-dimensionnal ?

Does the dimension limitation apply only to inputs, or any tensor inside the edge tpu ?

Is there any known clever way to get around the problem ? For example, we could use three different model inputs for [red, green, blue], using the "saved" dimension for the "Sequence" part ?

Could it work by splitting our model into two model : the first one would take one image and outputs a flattened 1-D vector. The second one takes a sequence of these 1D vector, and outputs what we want ? Is this case, there would be a useless round-trip to and from the CPU.

Thanks a lot !
Click to expand!
Issue Type
Support, Feature Request
Operating System
Linux
Coral Device
USB Accelerator
Other Devices
No response
Programming Language
C++, Python 3.9
Relevant Log Output
No response

Hello @mathieugalle

Is it possible that on the future, more than 3 dimensions could be allowed ? Is this a software limitation or a hardware one ?

No, we aren't planning to support higher dimensions in future. For now this is a software limitation ( we may not disclose complete info about limitation)

Does the new append_recurrent_links utility help here by allowing us to input only one image at a time (only three dimensions) and saving the "state" part internally ? Even if theoretically the model itself would still be 4-dimensionnal ?

Yes, the model would be 4d if input is 3d. This can be applicable for 2d inputs, where model can be 3d.

Does the dimension limitation apply only to inputs, or any tensor inside the edge tpu ?

it applies to every tensor executable on edgetpu

Is there any known clever way to get around the problem ? For example, we could use three different model inputs for [red, green, blue], using the "saved" dimension for the "Sequence" part ?

Not exactly sure about work around can you try with gray scale images first.


⚠ Bofrost.be has degraded performance

In af37d69, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1655 ms

Resolved: Bofrost.be performance has improved in 8e76f1d after 6 minutes.