Add support for API version 2021-06-30-preview

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

API changes have been detected in Azure.DigitalTwins.Core. You can review API changes here
API changes
+             V2021_06_30_Preview = 2,
-         public DigitalTwinsClientOptions(ServiceVersion version = V2020_10_31);
+         public DigitalTwinsClientOptions(ServiceVersion version = V2021_06_30_Preview);
+         [JsonPropertyName("sourceTime")]
+         public DateTimeOffset? SourceTime { get; set; }
+         public const string MetadataPropertySourceTime = "sourceTime";


fix(docs): use sh instead of bash with busybox

create examples/work-avoidance.yaml
echo pod occur error:
Error: failed to find name in PATH: exec: "bash": executable file not found in $PATH

Motivation
use sh instead of bash
Modifications

Verification

Were there any other uses of bash you could find?

I checked all the busybox examples, and only found this one using bash. others all use sh or directly use command (echo, true, mkdir etc)

Answering my own question, did a search and the rest uses other images. Some of them do use argosay though, which is slated for removal as well, so those will need to be careful around


Add tex/latex discovery plugin

Add a discovery plugin to find files of the type used for Latex.

This was added to tdenewiler/statick-tex#1.


⚠ RPC server - Conflux has degraded performance

In f319bf3, RPC server - Conflux ($CONFLUX_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Conflux performance has improved in db1eae3 after 8 minutes.


[BUG]  tag is not taken into account when using rowspan

Prerequisites

[x] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[x] Checked that your issue isn't already filed.
[x] Checked if no PR was submitted that fixes this problem.

Versions

PHP version:

PHP 7.3.4 (cli) (built: Apr  2 2019 21:57:22) ( NTS MSVC15 (Visual C++ 2017) x64 ) Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.4, Copyright (c) 1998-2018 Zend Technologies

Laravel version:

Laravel Framework 5.8.22

Package version: 3.1.13

Description
Trying to style a Spreadsheet from the blade view yields inconsistent results.
The rowspan and colspan attributes for  and  tags work out of the box.
Using either  or  tags also work but combining them does not.
Steps to Reproduce

Run php artisan make:export TestExport
Swap FromCollection concern with FromView and implement.

# app\Exports\TestExport.php
<?php

namespace App\Exports;

use Illuminate\Contracts\View\View;
use Maatwebsite\Excel\Concerns\FromView;

class testExport implements FromView
{
    /**
    * @return \Illuminate\Contracts\View\View
    */
    public function view(): View
    {
        return view('test_view');
    }
}

Create test_view.blade.php file in resources/views/ directory. A simple example will do.

1

2

3

4       1234
5       Letters
6

7

8       qwer
9       asdf
10      zxcv
11

12

13

14

15      1234-1
16      qwer-1
17      asdf-1
18      zxcv-1
19

20

21

Make a route to export the spreadsheet.

# routes/web.php
Route::get('test', function () {
  return Excel::download(new App\Exports\TestExport, 'test.xlsx');
});

Expected behavior:
The cells in the resulting spreadsheet should be boldened like their HTML equivalent.

1234
Letters

qwer
asdf
zxcv

1234-1
qwer-1
asdf-1
zxcv-1

Actual behavior:
Not every cell is styled correctly

Excel

Google-Spreadsheet
Additional Information
Upon further testing, this only appears to be the case if the cell ends up after a rowspanned cell, meaning everything works correctly if lines 4 and 5 are swapped in the view file.

Hey @ipontt the view parsing is not part of this package, but is done by the parent package PhpSpreadsheet. We have no control of how  and  are being parsed. You can find there code here: https://github.com/PHPOffice/PhpSpreadsheet/blob/master/src/PhpSpreadsheet/Reader/Html.php

I tried to debug the issue and reached that same file. However, I do not understand much how the switch works in some cases.
In the end I gave up and just used style arrays in an afterSheet method. It looks bloated and I originally hoped to let the view be responsible for its own styling but to put it simply, PhpSpreadsheet is very inconsistent with this.


Fix windows can not recognize the tag version when publishing

Github Action Log
Release url
The screenshot is as follows, the windows version number is normal.

Thanks @Tlntin !

Would you happen to know how I might be able to run the newest workflow manually without publishing another release? I made a release last night but the windows version failed to upload and I am trying to get the windows binary uploaded by attempting to manually trigger the workflow.


[Hardware] AXI write converter broken when slices depth > 0

seems it also applies to the read converter


Browser hangs and disconnects when testing against a url that contains a symbol and while using an experimental proxyless mode

What is your Scenario?
I am running a simple test against a url which contains a question mark and I am using the --experimental-proxyless parameter. The test hangs and browser disconnects in this case.
What is the Current behavior?
Upon running the test with experimental proxyless mode, the page loads but then the browser hangs and eventually disconnects.
Upon running the test without the experimental proxyless mode, the test succeeds each time.
What is the Expected behavior?
The expected behavior would be for the browser to not hang and then disconnect when running a test against a url that contains a symbol and while using proxyless mode
What is your public website URL? (or attach your complete example)
https://www.chegg.com/auth?login
What is your TestCafe test code?
fixture`Login page test`.meta({ fixtureID: 'f-0001', author: 'GDG', app: '' });

test.meta({
  priority: 'p1',
  testID: 't-0001',
  testType: 'Smoke',
  testRailCaseId: '267753',
})(
  'Login page test',
  async (t) => {
    await t.navigateTo(`https://www.chegg.com/auth?login`);
  }
);

Your complete configuration file
No response
Your complete test report
ERROR The Chrome 109.0.5414.74 / Linux 0.0 browser disconnected. If you did not close the browser yourself, browser performance or network issues may be at fault.
Type "testcafe -h" for help.
error Command failed with exit code 1.
Screenshots
No response
Steps to Reproduce
Steps 4 and 5 highlight the issue. The other steps are shows for comparison that urls that do not contains symbols appear to be working fine

Testcafe version should be 2.2
Run the sample code without the --experimental-proxyless option
Test passes as expected
Run the sample code with --experimental-proxyless option
Test hangs and eventually the browser disconnects
Run the sample code with --experimental-proxyless but adjust the url to not contain the question mark (https://www.chegg.com)
Test passes as expected

TestCafe version
2.2.0
Node.js version
14.20.1
Command-line arguments
yarn testcafe chrome testcafe/tests/sampleTest.ts --experimental-proxyless
or
yarn testcafe chrome testcafe/tests/sampleTest.ts --experimental-proxyless -L
Browser name(s) and version(s)
Version 109.0.5414.87 (Official Build) (x86_64)
Platform(s) and version(s)
No response
Other
No response

Hello,
I did not manage to reproduce TestCafe hanging using your test code, however I get a JavaScript error when running TestCafe with the experimental-proxyless flag.
Uncaught ReferenceError: __set$ is not defined           No stack trace available
I just checked this usage scenario in v2.3.0-rc.1 and it works as expected there. Would you please check this on your side and let us know if this issue is reproducible in v2.3.0-rc.1 on your side?

@Artem-Babich Hello, thanks for replying back to me.
I wasn't able to check because I ran into an issue during installing version 2.3.0-rc.1
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 16". Got "14.20.1" error Found incompatible module.
Does the upcoming version 2.3 mean that users will have to switch to node version >=16?

Hello @ayemelyanenko-chegg,
Officially, NodeJS 14 maintenance will end on April 30, 2023. However, we had to update babel-plugin-module-resolver to v5 due to a vulnerability: babel-plugin-module-resolver#441. This version only supports NodeJS version >=16.
So, yes, we are ending support for NodeJS 14 in v2.3.0.
By the way, we already released v2.3.0-rc.2, which includes some fixes. Please check if the test hanging issue is reproducible in this version and let me know your results.

Hello @Artem-Babich, it's odd but I installed the recommended RC version to my repo (using yarn)
My package.json has the below version
"testcafe": "2.3.0-rc.2"
I also updated my node version to 18.13.0 which is the latest recommended stable version. I tried node 16.16.0 as well just in case.
I am trying to run my sample code with --experimental-proxyless and node 18.13.0 (also tried with 16.16.0) and the Chrome browser 109.0.5414.87 (Official Build) (x86_64) just sits at about:blank and doesn't open the page at all. When I run without experimental proxyless option, the test runs fine on either node version.
Here are the command lines with --experimental-proxyless and without. Also attaching videos of how it looks like:
yarn testcafe chrome testcafe/tests/sampleTest.ts --experimental-proxyless -L
Video of above command run:
https://recordit.co/6rC1U4KF7Y
yarn testcafe chrome testcafe/tests/sampleTest.ts  -L
Video of above command run:
https://recordit.co/GDzS5wXUyG

Hello,
Thank you for the clarification and video. I'm happy to hear that the issue is resolved in newer versions. Regarding our proxyless mode, it is still experimental, but we are actively working on it to improve user experience. Would you please send us a simple working project so we can reproduce this issue locally and fix it in a proxyless mode?

Thank you @Artem-Babich. I'm going to close this issue for now and pull in latest version of TestCafe into my repository and run with experimental proxyless and a newer version of node. If I still see this issue, I will try to get it to reproduce it in a simple project and will reopen this issue.


Add a license to the repository

I recently came across your project Grover-database-in-python-Qiskit and I noticed that the repository github.com/jesusmontera/Grover-database-in-python-Qiskit currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

MIT license so can modify or use free.

Thanks!


tryParse could be nullable?

I have an issue with this code:
Map<String, String> map = {};
map['hello'] = '123';
int? something = int.tryParse(map['hello']); // uh oh!

tryParse accepts a non-null string. Therefore, I need to use map['hello']! but if hello doesn't exist, it gets even more verbose.
if (map['hello'] != null) {
    int? something = int.tryParse(map['hello']!);
    if (something != null) {
        doWhatIWant();
    } else {
       doSomethingElse();
   }
} else {
    doSomethingElse();
}

If tryParse propagated null, this wouldn't be needed.
My dream is still having String.toInt() one day, so that '123'.toInt() would be possible. In this nullable case, map['hello']?.toInt() could be used.

There are no plans to change int.tryParse to accept a null argument.
It can't use a null for anything, and the caller is perfectly capable of detecting whether the argument it's null or not before calling. Allowing a null in a place where it's not needed can hide issues where something is accidentally null or nullable.
If you want to treat null the same as an invalid string, all you need to do is int.tryParse(map['hello'] ?? ''), then tryParse will return null.


TrustCenter links don't redirect to language specific urls

Describe the bug
Any links to https://www.microsoft.com/trustcenter/ and below without the language identifer en-us do not seem to work.
I realize this isn't a docs site page, but is linked to quite a bit from the docs, and is likely easier for you to address internally.
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-ca/azure/analysis-services/analysis-services-overview
Click on "Microsoft Trust Center"
The page loads https://www.microsoft.com/trustcenter/Security/AzureSecurity
Manually add en-us/ after microsoft.com/ to be forwarded to https://www.microsoft.com/en-us/trustcenter/security/azure-security

Expected behavior
Language detection to work
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Close as transferring the issue to Azure team


Icons in Automatic Jupyter Notebooks

When icons are included in the text of the tutorial, there is an error with generated Jupyter Notebook which says: "The editor could not be opened due to an unexpected error: Unexpected token f in JSON at position XXXX".  I tested out that it's due to the icon symbols, so just wanted to point that out and save people's time on debugging :)

Thanks @wee-snufkin !


Remove unused "fs" require

The import is currently unused, so it can safely be removed.
It has also caused problems for us in an environment where we are unable to use the fs package.

Closing this to clean up my open PRs. Feel free to reopen this if you still want to merge.


ERROR: This application requieres one of the following version of .NET Framework

he system give me the next message:
This application requieres one of the following version of .NET Framework:
.NET Framework, Version 4.7.2
Do you want to install this .NETFramework version now?
I select Yes,  and the system tells me: This Operating System does not support .Net Framework 4.7.2.
This is the windows version: Microsoft Windows [Version 10.0.10240].  64 bits In Spanish and Office 365 ProPlus both in Spanish
try disabling .NET from the windows features and install a previus version of .NET or a previus version of Ootd (32 bits too) and it didn't work.
I really try differents option and really like your program, please help me.
I would greatly appreciate your help

Try this pre-release and let me know if it works: https://github.com/mscrivo/OotD/releases/download/3.99.83/ootd-<IP_ADDRESS>.exe


FirebaseUI v2.0.1 requires unavailable Firebase/Play Services Version

Trying to compile
compile 'com.firebaseui:firebase-ui-auth:2.0.1'
in app gradle file returns:
Error:Failed to resolve: com.google.firebase:firebase-auth:11.0.1
Looks like firebase 11.0.1 isn't still available, I just find 11.0.0.

@FranSalguero you have to update 'Google Repository' in your SDK manager.  11.0.1 was released last week.


Update UserGuide to eliminate any trace of AB3

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (6e78be2) compared to base (2f5ae9e).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #57   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Idea: Meta Resources

Should Waffles have meta-resources that abstract underlying resources?
For example, right now Waffles only has the apt resource to install packages. If a yum resource is created, should the user have to create separate roles for apt and yum-based nodes? Or should they be able to have a single node that uses a package resource and Waffles will intelligently determine whether to use apt or yum?

You could do both; make seperate resources for package managers and add the most basic functionality to a package resource, that uses whatever package manager is on the system (or is the default for the Linux flavour it is running on). The code should easily be reusable.


spec-reporter prints retries

PR Checklist

[x] Addresses an existing open issue: fixes #5014
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview

I've implemented a function called logRetries() which displays the number of the current retry along with the total number of retries, provided that the total number of retries is greater than zero. This output is formatted below the test title and highlighted in yellow as requested for ecosystem consistency. I would greatly appreciate any feedback on this addition!
Example:

coverage: 94.346% (+0.01%) from 94.335%
when pulling b5d4d68a2899d7ab54b63541828f9d64764c7353 on CheadleCheadle:spec-reporter-retries
into b88978deb3c12f9b95502828f6ac29ebe8be85ef on mochajs:master.

👋 Ping @CheadleCheadle, is this still something you have energy & time for?

Closing out to free up the backing issue. @CheadleCheadle if you end up seeing this and having time again, no worries, feel free to re-open the PR or send a new one.
If anybody else sees this message and there isn't a new PR, feel free to send one yourself. Just make sure to add a co-author attribution if it takes code from this PR.
Cheers all! 🤎


Cant work with cordova android

On android platform with  cordova app, if user scroll from bottom to top, only touch start and only 1 touch move event is called, no touch end is fired.
This causes pull state is stuck at 'pulling' event and it doesnt work until user tap once on screen again to trigger touch end event

This issue might be related to how Cordova handles touch events, and as ptr.js is focused on the web platform and it's working correctly, you might need to debug the differences between Cordova and a browser on how touch events are handled.


Utility Meter component "jumps" in values. Mostly after a reboot of hass...

Home Assistant release with the issue:

Currently 0.91.3, but as far as I know this bug was already in the version where the utility meter was introduced (0.87).
Last working Home Assistant release (if known):
Unknown.
Operating environment (Hass.io/Docker/Windows/etc.):

Docker environment. Managed with Portainer.
Component/platform:

https://www.home-assistant.io/components/utility_meter/
Description of problem:
This server is monitored using a z-wave component (greenwave). Average consumption is around 22W, meaning a daily consumption of around 0.56kWh.
Normal / Expected graph for daily usage (picture from Grafana):

A small jump as seen from hass itself, dated feb 17, 2019:

The next overview shows the Utility values, daily, weekly and monthly (picture from Grafana).
On the left you see the normal pattern, on the right the abnormal pattern.

Small jumps in values
Extremely large jumps in values

Daily usage jumps from 0.xkWh to 120000kWh !!

Daily usage with two "jumps" in values.

Left circle: From 0.54 to 1.30
Right circle: From 0.28 to 1.87

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# As of hass 0.87, Utility Meter does exist
utility_meter:
  domiduca_energy_daily:
    source: sensor.greenwave_powernode_6_port_energy
    cycle: daily
  domiduca_energy_weekly:
    source: sensor.greenwave_powernode_6_port_energy
    cycle: weekly
  domiduca_energy_monthly:
    source: sensor.greenwave_powernode_6_port_energy
    cycle: monthly
  domiduca_energy_yearly:
    source: sensor.greenwave_powernode_6_port_energy
    cycle: yearly

Traceback (if applicable):
None available.
The jumps sometimes seem to happen during/after a reboot of hass.

Additional information:
This bug renders the utility sensor useless, as I can't correct the data anymore.
Furthermore, I had alarms on the daily values to warn that something is wrong with the server. This bug makes this automated monitoring useless too!
@dgomes as requested in the architecture thread!

What integration is greenwave_powernode_6_port_energy ?

Using built in z-wave integration of hass.

Can I assume the Z-Wave sensor provides kWh values and resets it self every day ?

Nope. It keeps on counting as you can see in the below graph:

OK I just spotted the issue.
You see 3/27 ~12h00 in your last comment ? that "error" matches the utility_meter "jump"
At that time your reading was less then the previous value... since the utility meter calculates differences between two readings that must have created an overflow in the diff.

Might that happen during restart/upgrade of hass? That either hass recieves or remembers an older value, or that z-wave sends an older value???

I don't have z-wave, so I'm not really into the z-wave implementation...
But something odd is coming from that sensor :(

But can it be fixed in the utility sensor? At least a check on a diff overflow??

I would probably query influxdb directly and understand from the raw values (no mean, no max) what is happening in the time frame close to the jump.

I will check the data. I think Grafana supports a table which just would display the stored values without any interpretation...

Hello, this is my first comment on the forum.
I'm using Hass.io 0.94.1 with the following components:

utility_meter
zwave

I'm facing a similar problem monitoring a z-wave component (Qubino Smart Meter) through an utility meter. This is the utility_meter configuration, nothing special:
daily_energy:
  source: sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy
  cycle: daily

It worked well until a restart caused by a blackout. After the blackout I verified energy value to jump from 30.7 to 23.1 and back to 30.7 causing the utility meter to jump accordingly.
Here are some DB events regarding the energy sensor entity, the state value goes from 30.7 to 23.1 and back to 30.7:
{"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "old_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "30.7", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "power_consumption": 114.6, "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:03.226419+00:00", "last_updated": "2019-06-11T14:44:03.226419+00:00", "context": {"id": "6b1fe1b26d964953afaedda4bfcf1209", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "30.7", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "power_consumption": 112.8, "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:03.371526+00:00", "last_updated": "2019-06-11T14:44:03.371526+00:00", "context": {"id": "86a392d5e2484af2824bd81ad653ef6a", "parent_id": null, "user_id": null}}}
{"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "old_state": null, "new_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "23.1", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:55.507010+00:00", "last_updated": "2019-06-11T14:44:55.507010+00:00", "context": {"id": "e54619ba19b34a7c94a4f4af68b59fed", "parent_id": null, "user_id": null}}}
{"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "old_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "23.1", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:55.507010+00:00", "last_updated": "2019-06-11T14:44:55.507010+00:00", "context": {"id": "e54619ba19b34a7c94a4f4af68b59fed", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "23.1", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "power_consumption": 162.0, "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:55.685113+00:00", "last_updated": "2019-06-11T14:44:55.685113+00:00", "context": {"id": "ccd0f3c2aaa0456b867c90d38c42f5da", "parent_id": null, "user_id": null}}}
{"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "old_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "23.1", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "power_consumption": 162.0, "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:55.685113+00:00", "last_updated": "2019-06-11T14:44:55.685113+00:00", "context": {"id": "ccd0f3c2aaa0456b867c90d38c42f5da", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.qubino_goap_zmnhtdx_smart_meter_s4_s5_s6_energy", "state": "30.7", "attributes": {"node_id": 5, "value_index": 0, "value_instance": 1, "value_id": "72057594126827522", "power_consumption": 162.0, "unit_of_measurement": "kWh", "friendly_name": "Qubino (Goap) ZMNHTDx Smart meter S4 S5 S6 Energy"}, "last_changed": "2019-06-11T14:44:57.821284+00:00", "last_updated": "2019-06-11T14:44:57.821284+00:00", "context": {"id": "2a31aa99da9e4ffa8300f92051eda9c8", "parent_id": null, "user_id": null}}}
this was really strange but confirm that it's not an issue regarding the utility meter (IMHO). So I checked the OZW log. The first poll response from the node was 30.7 after the restart.
2019-06-11 14:44:57.634 Info, Node005, Received Meter report from node 5: Energy=30.7kWh
From where was read the 23.1 value that caused the jump?
Let's check the Z-Wave XML configuration of the node:
<Node id="5" name="" location="" basic="4" generic="49" specific="3" roletype="5"
 devicetype="5888" nodetype="0" type="Whole Home Meter Simple" listening="true"
 frequentListening="false" beaming="true" routing="true" max_baud_rate="40000"
 version="4" query_stage="Complete">
 <Manufacturer id="159" name="Qubino (Goap)">
  <Product type="7" id="52" name="ZMNHTDx Smart meter S4 S5 S6" />
 </Manufacturer>
 <CommandClasses>
  <CommandClass id="50" name="COMMAND_CLASS_METER" version="4" request_flags="2"
   innif="true">
   <Instance index="1" />
   <Value type="decimal" genre="user" instance="1" index="0" label="Energy"
    units="kWh" read_only="true" write_only="false" verify_changes="false"
    poll_intensity="0" min="0" max="0" value="23.1" />

please note the value="23.1" on the last line.
Could it be that the first value of the z-wave entity is read from the XML configuration after a power outage (or an update) ?
@rytilahti : IMHO it's a zwave issue.
Hope this helps.


Fix "concatenate nil value" error

If options is nil the script fails with a attempt to concatenate local 'options' (a nil value) when trying to construct the the second argument for iif.
This change fixes this. But since I'm not a LUA guy there may be better ways to fix this?

Ouch, unit test fail!
Nice catch, thanks for this.
It's possible to do this in one line with and and or, but I think this approach is more readable anyway.


tag releases

Hi,
could you please tag releases on supermarket also on github? It's a bit hard to debug without…
Thanks!

Done!


bluebird is needed in prod

Fixes #4
once the babel target moves to nodejs 8.x.x (where async/await syntax is available),
bluebird can be removed altogether

@IanSavchenko github protip (which i discovered yesterday) - an issue can be closed also via keywords in the PR description, not just in the commit message. This is useful because by default the owner of a repo can edit other people's PRs and just add these keywords.


Raw files

FileSystemApi needs to support reading and writing "raw" files.
When writing, AddFileOptions.RawLeaves is set.

Raw

ipfs add --raw-leaves hello.txt

zb2rhj7crUKTQYRGCRATFaQ6YFLTde2YzdqbbhAASkL9uRDXn hello.txt

Note that the CID is v1 with a content type of "raw".

Implemented


Update host for Hesan.He3 1.3.23

#163422

Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels - Intentionally didn't update manifest version

https://github.com/microsoft/winget-pkgs/issues/142854


Is it possible to implement a real Stream?

To make a non-panicking collect, with the actual code I have to do something like
async fn query<T: FromRow, E: From<FromRowError> + From<Error>>(conn: &mut Conn, query: &str) -> Result<Vec<T>, E> {
  conn.query_iter(query).await?
    .try_collect::<T>().await?
    .into_iter().collect::<Result<Vec<T>, E>>()
}

(this is only for example purposes, could contains errors)
This means allocating the entire resultset even if every single row is an error, or having to implement a wrapper to use next() as a Stream...
Wouldn't be possible, for example, to add an impl of futures_core::Stream that is the same used by tokio-stream and it seems to be a standard de-facto?
If you prefer, under a feature, so it wouldn't be default for everyone.
I can do the PR if you want

Hi.

To make a non-panicking collect, with the actual code I have to do something like... This means allocating the entire resultset even if every single row is an error

You meant that you want to stop on the first row that isn't convertible to T? If yes, then the QueryResult::reduce will do this for you in the most effective manner, because mysql protocol requires you to consume the whole QueryResult:
async fn query<T, E>(conn: &mut Conn, query: &str) -> Result<Vec<T>, E>
where
    T: FromRow,
    E: From<FromRowError> + From<Error>,
{
    let mut done = false;
    conn.query_iter(query).await?
        .reduce(Ok(Vec::new()), |mut result, row: Row| {
            match result {
                Ok(mut acc) => {
                    match from_row_opt::<T>(row) {
                        Ok(x) => {
                            acc.push(x);
                            Ok(acc)
                        }
                        Err(e) => Err(e.into())
                    }
                },
                err => err,
            }
        }).await
}

(this is only for example purposes, could contains errors)

Wouldn't be possible, for example, to add an impl of futures_core::Stream that is the same used by tokio-stream and it seems to be a standard de-facto?

This would be great.
You should note, however, that this may be tricky, because you should cover multi-result set case. This means that:

QueryResult is the stream of streams
2-nd level streams have Rows of different shapes so you'd better to use the Row type as an Item,
It's better to make result set metadata accessible through both 1-st and 2-nd level streams,
You have to consume 2-nd level stream before calling next on the 1-st level stream, so (i) 2-nd should borrow 1-st, (ii) 1-st should consume unconsumed 2-nd at call to 1-st's next.

Ok, this makes everything complicated, I wasn't taking multiple resultsets in consideration...
But, as far as I can see, in the actual architecture it's always next() to return every resultset rows, putting a None at the end of every resultset as a separator.
I can see the stream-of-streams, but it's more like a single stream that changes datatype on the run, because streams aren't concurrent but sequential.
Correct me if I'm wrong, but this kind of behaviour is easily solved by an enum that impl FromRow and uses the data to discriminate between variants, but it's something the user has to write, not the crate itself...

My proposal for a Stream impl is here, based on a solution by @dodomorandi: https://github.com/nappa85/mysql-stream/blob/master/src/lib.rs
There are both stream and stream_and_drop methods, mimic the style of QueryResult methods.

Great!. I'll look into it.

Hello, any news about the subject?
Also a "your code is bad and you should feel bad" is accepted

@nappa85, your proposal was really helpful, thanks!
Published as v0.28.1.

Great to hear that, good work!
Il sab 18 set 2021, 14:06 Anatoly I @.***> ha scritto:

@nappa85 https://github.com/nappa85, your proposal was really helpful,
thanks!
Published as v0.28.1
https://github.com/blackbeam/mysql_async/releases/tag/v0.28.1.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/blackbeam/mysql_async/issues/166#issuecomment-922266811,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXINNEUC5R4ESZWWY4HJLUCR6FLANCNFSM5BI4EEBA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


encounter some problems on train.py

The error is as followed ，did i miss any step？
********** Tensor Shape ************
video_feat_fw:
(?, ?, 500)
video_feat_bw:
(?, ?, 500)
proposal_fw:
(?, ?, 120)
proposal_bw:
(?, ?, 120)
proposal_weight:
(120, 2)
Evaluating the initialized model ...
vid: v_uqiMw7tQ1Cc
feature_len: 26
Evaluating batch: #0
Traceback (most recent call last):
File "E:/pythonCode/DenseVideoCaptioning-master/train.py", line 547, in
train(options)
File "E:/pythonCode/DenseVideoCaptioning-master/train.py", line 392, in train
val_loss, val_proposal_loss, val_caption_loss = evaluation(options, data_provision, sess, inputs, t_loss_list)
File "E:/pythonCode/DenseVideoCaptioning-master/train.py", line 49, in evaluation
feed_dict=feed_dict[0:120][:])
TypeError: unhashable type

This line of code: feed_dict=feed_dict[0:120][:]) is not the original code. Have you modified the code? "feed_dict" is a dictionary type. Please double check your modification.

Thanks for your timely reply


AtomicBuffer strict-aliasing violations (undefined behavior)

Some methods in the AtomicBuffer class such as overlayStruct(), putInt64() and getInt32() violate C++ strict-aliasing rules and thus yield undefined behavior (UB) because an underlying uint8_t array is accessed through unrelated and incompatible pointer types:
https://github.com/real-logic/aeron/blob/dd302d5a243870657f8fa1917d0d157605e4ab0f/aeron-client/src/main/cpp/concurrent/AtomicBuffer.h#L189-L220
Also, defining the field m_buffer as std::uint8_t*, cf.
https://github.com/real-logic/aeron/blob/dd302d5a243870657f8fa1917d0d157605e4ab0f/aeron-client/src/main/cpp/concurrent/AtomicBuffer.h#L475
in such a low level buffer class invites more UB because the C++ standard doesn't allow extra aliasing for uint8_t pointers.
This contrasts unsigned char, char or std::byte pointers for which the C++ specifies special aliasing rules.
Thus, for such a buffer class it's usually advantageous to use - say - unsigned char pointers internally to eliminate UB.
Sure, currently, in most environments uint8_t is simply typedeffed to unsigned char.
However, one can't rely on that this is everywhere the case and that no implementation ever changes that typedef.
For example, there are people who use uin8_t for intended use cases and who complain to compiler developers
about missed optimization opportunities in their uint8_t array code, when uint8_t is typedeffed to unsigned char,
because of possible aliasing to all other types that is then allowed.

I'm thus wondering:

Does aeron require users to compile everything with -fno-strict-aliasing?
Is the aeron team interested in eliminiting such undefined behavior?

On all of the platforms that we test on uint8_t is currently typedef'd unsigned char.  As you say that can be relied upon, so I've added a static_assert to verify that these are the same times.  Therefore the compilation will break on any platform on which this is not supported.  While it would be safer to change the internal representation to unsigned char this would mean that the passed in parameters would also need to change or perform some sort of byte by byte copy.  As this is designed so that is does not own the underlying buffer this creates some awkward ownership issues or would require cascading this change out to all use of this class, which would potentially break a lot of customer code.


ENH: allow matplotlib colormaps as pal

Allow matplotlib colormaps to be used directly as pal. Closes #9
@ljwolf Note that tests are apparently broken due to changes in Pysal. We may use geopandas naturalearth_lowres as a test data instead. That way you don't need whole PySAL to be installed. I have just mimicked your tests, so there is no real check that color is correctly assigned.

Yeah, tests will need to be updated. Happy to remove the testing dependency on pysal, but if it gets integrated into splot, we'll have the core (and thus the example datasets) anyway. Will rewrite tests in a forthcoming roadmap.


amount of documents =/= amount of users

hi.
i have a project where 10 people have access to. however after a while there were 2.5k documents inside the collection it needs.
and after refreshing they just keep on coming. did i do something wrong in my code?
var store = new MongoDBStore({
    uri: process.env.MONGO_URL,
    collection: 'v2Sessions'
  });

app.use(session({
    name: "Auth",
    secret: process.env.SESSION_SECRET_KEY,
    resave: true,
    saveUninitialized: true,
    cookie: {
        maxage: 86400000
    },
    store: store
}));

kind regards
milan

@wfjake is right, a session isn't one-to-one to a user. And refreshing the page would create a new session if saveUninitialized: true is set.


Open VR controllers do not raise some UnityEditor.XR.Node events

Overview
Some UnityEditor.XR.Node events do not get raised properly.
When turning a controller off, the tracking lost and node removed events do not get raised by the editor.
Steps to reproduce
Add the following to the Unity Interaction Events region in OpenVRDeviceManger.cs

        #region Unity InteractionManager Events

        private void InputTracking_nodeAdded(XRNodeState nodeState)
        {
            if (IsNodeTypeSupported(nodeState))
            {
                Debug.Log("Node added:" + nodeState.nodeType);
                GetOrAddController(nodeState);
            }
        }

        private void InputTracking_trackingAcquired(XRNodeState nodeState)
        {
            if (IsNodeTypeSupported(nodeState))
            {
                if (activeControllers.ContainsKey(nodeState.nodeType))
                {
                    Debug.Log("Tracking acquired:" + nodeState.nodeType);
                    var controller = GetOrAddController(nodeState);
                    InputSystem?.RaiseSourceDetected(controller?.InputSource, controller);
                }
            }
        }

        private void InputTracking_trackingLost(XRNodeState nodeState)
        {
            if (IsNodeTypeSupported(nodeState))
            {
                Debug.Log("Tracking lost:" + nodeState.nodeType);
                var controller = GetOrAddController(nodeState);
                InputSystem?.RaiseSourceLost(controller?.InputSource, controller);
            }
        }

        private void InputTracking_nodeRemoved(XRNodeState nodeState)
        {
            Debug.Log("node removed:" + nodeState.nodeType);
            activeControllers.Remove(nodeState.nodeType);
        }

        #endregion Unity InteractionManager Events

Start editor with open vr settings.
Turn controllers on, then off.
Unity Editor Version
2018.1.9f1
Mixed Reality Toolkit Release Version
vNEXT Alpha

I can repro this with Vive as well, on 2018.1.9f1. Might not be WinMR-specific.

Ok, so possibly an issue in the editor. What about an actual build?
And for Alpha, is this really an issue? SO long as controllers are detected and work.
We do need to look for better "non Unity" methods of getting controller data

What about an actual build?

Same thing.

And for Alpha, is this really an issue? SO long as controllers are detected and work.

Agreed, cleaning up the controller model / source lost seems to be the only issue.


Explore using CMIP & constantish NDVI for making env forecasts

[ ] Look into getting and merging in CMIP data
[ ] Explore fixing NDVI in environmental models

For CMIP data we have a few choices to make.
-How far out to go. CMIP5 goes to 2099
-Which scenario to use. They have different outputs for RCP 2.6, 4.5, 6.0, and 8.5. 8.5 is the worst case scenario.
-Dealing with ensembles. There are 10-20 different model outputs from various institution around the world, each with 1-5 runs based on slightly different initial conditions.

I think for time period 2050 sounds like a reasonable number. anything beyond that will probably be terrible because we can't predict observers or ndvi.
for the ensembles the most straightforward way would be to average everything together to give our own models just a single set of bioclim vars to work with.

@sdtaylor - those both sound good to me. As for the RCP choice, I don't have any strong feelings, but I think picking one of the middle two values seems reasonable as a middle of the road estimate.

What are our current thoughts about fixing NDVI?

I think just the average value since the year 2000 or so.

To clarify, does that mean the following?
"During training, use the value for that year. Forecasts will be based on the average value from the last X years of the training set"

Yes, but maybe:
"For the forecasted years 2014-2050 we used near surface temperature and precipitation data from CMIP5 RCP6.0 models to calculate the bioclim variables. NDVI values were the site level mean from the years 2000-2013, and the observer was set as the last known observer at the site."

Ah, so this is just post-2013. Got it.
It might make more sense to make predictions based on the median observer. I don't think we really want to assume zero observer turnover between now and 2050.

On Jun 12, 2017, at 11:47 AM, Shawn<EMAIL_ADDRESS>wrote:
Yes, but maybe:
"For the forecasted years 2014-2050 we used near surface temperature and precipitation data from CMIP5 RCP6.0 models to calculate the bioclim variables. NDVI values were the site level mean from the years 2000-2013, and the observer was set as the last known observer at the site."
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/weecology/bbs-forecasting/issues/110#issuecomment-307830836, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzdCZPZo1mxzwwHhFOVN6bmUJWWxFwoks5sDV2jgaJpZM4NYSmM.

who would the median observer be?

It's what you get when you set the observer bias to zero
Dave

On Jun 12, 2017, at 11:53, Shawn<EMAIL_ADDRESS>wrote:
who would the median observer be?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, that sounds good.

Update on CMIP data. I think this is the best source for CMIP5 data for us. This group does downscaling to 12x12km from the original 0.5 deg data and distributes only the variables hydrologists (and ecologists) care about, surface precip and temperature. I'm currently working on getting the 17 models aggregated to 1 as well as to the 40x40km resolution we're using.

I'm going to make it so the cmip data is accessed via get_bioclim_data(source='cmip5'), while get_bioclim_data() defaults to the original prism data so nothing gets broken. Will probably add 1 more function called get_future_env_data() to aggregate other things for 2017+ forecasts.

There is some overlap in the prism/cmip5 data so I can do some quick comparisons. These are the raw climate variables, each point is a single site/month. The temperature is really good. Precip is really variable in reanalysis data like this so it's probably the best we a hope for.

And of the bioclim variables. each point is a site/year. The funky ones have precip incorporated somehow.

Really interesting, the biased bioclim variables in particular. Thanks for doing this check. I definitely think there's a really interesting project or two to be done looking at integrating uncertainty in the future climate predictions into these kinds of forecasts

There is an updated sqlite file on the T drive for using the updates in #128

Thanks @sdtaylor! I think I'll wait to re-run everything until the NDVI is also available, so that I can fit & predict to 2050 in one go.

@davharris, cmip5 bioclim forecasts and the NDVI averages is now included in #129, let me know if that works for you. I'm not sure to incorporate the median observer into it.

Awesome. I can deal with the observer stuff.  Thanks!

On Jun 18, 2017, at 4:41 PM, Shawn<EMAIL_ADDRESS>wrote:
@davharris https://github.com/davharris, cmip5 bioclim forecasts and the NDVI averages is now included in #129 https://github.com/weecology/bbs-forecasting/pull/129, let me know if that works for you. I'm not sure to incorporate the median observer into it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/weecology/bbs-forecasting/issues/110#issuecomment-309301563, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzdCa_964lYkOQNkDcvyeOD9a7QwVuvks5sFYt9gaJpZM4NYSmM.

I think this is solved in #129. Nice work @sdtaylor!


feat: allow using sharded repodata

Enables sharded repodata for specific channels.
Add:
[repodata-config."https://prefix.dev/conda-forge"]
disable-sharded = false

To your global config to not disable sharded repodata. The double negation is there because in the future we might want to enable sharded repodata by default.
This PR is in draft because https://github.com/conda/rattler/pull/910 needs to be merged first.
@ruben-arts is there a good place to add this to the documentation?

The documentation can go here: https://pixi.sh/latest/reference/pixi_configuration/

When I enable all logic I get an error on the normal conda-forge. I think rattler should just skip this and try the next option.
config.toml:
[repodata-config]
disable-jlap = false
disable-bzip2 = false
disable-zstd = false
disable-sharded = false

❯ pixi exec cowpy
ERROR error=could not find subdir 'noarch' in channel 'https://conda.anaconda.org/conda-forge/'
  × failed to get repodata
  ├─▶ could not find subdir 'noarch' in channel 'https://conda.anaconda.org/conda-forge/'
  ╰─▶ HTTP status client error (404 Not Found) for url (https://conda.anaconda.org/conda-forge/noarch/repodata_shards.msgpack.zst)

I would like to add this test, but currently the default and per_channel aren't merged.
#[test]
  fn test_repodata_config() {
      let toml = r#"
          [repodata-config]
          disable-jlap = true
          disable-bzip2 = true
          disable-zstd = true
          disable-sharded = true

          [repodata-config."https://prefix.dev/conda-forge"]
          disable-jlap = false
          disable-bzip2 = false
          disable-zstd = false
          disable-sharded = false

          [repodata-config."https://conda.anaconda.org/conda-forge"]
          disable-jlap = false
          disable-bzip2 = false
          disable-zstd = false
      "#;
      let (config, _) = Config::from_toml(toml).unwrap();
      let repodata_config = config.repodata_config();
      assert_eq!(repodata_config.default.disable_jlap, Some(true));
      assert_eq!(repodata_config.default.disable_bzip2, Some(true));
      assert_eq!(repodata_config.default.disable_zstd, Some(true));
      assert_eq!(repodata_config.default.disable_sharded, Some(true));

      let per_channel = repodata_config.clone().per_channel;
      assert_eq!(per_channel.len(), 2);

      let prefix_config = per_channel.get(&Url::from_str("https://prefix.dev/conda-forge").unwrap()).unwrap();
      assert_eq!(prefix_config.disable_jlap, Some(false));
      assert_eq!(prefix_config.disable_bzip2, Some(false));
      assert_eq!(prefix_config.disable_zstd, Some(false));
      assert_eq!(prefix_config.disable_sharded, Some(false));

      let anaconda_config = per_channel.get(&Url::from_str("https://conda.anaconda.org/conda-forge").unwrap()).unwrap();
      assert_eq!(anaconda_config.disable_jlap, Some(false));
      assert_eq!(anaconda_config.disable_bzip2, Some(false));
      assert_eq!(anaconda_config.disable_zstd, Some(false));
      // TODO: disable-sharded is not set so default should be used
      // assert_eq!(anaconda_config.disable_sharded, Some(true));
  }

So a user can't do this right now and expect repodata-config to be used by default for the prefix channel:
[repodata-config."https://prefix.dev/conda-forge"]
disable-sharded = true

[repodata-config]
disable-jlap = true
disable-bzip2 = false
disable-zstd = true
disable-sharded = false

I like the added config flexibility. I think I would really like it if we also support setting things based on the "prefix" of the URL, so that you can configure it for a wider set of channels. E.g. adding the option to set
[repodata-config."https://prefix.dev/"]
disable-sharded = false

for all channels on prefix.dev – this is also how the mirror config works :)

@ruben-arts @wolfv all your concerns should be addressed now. Could you take another look?

Btw @ruben-arts I changed your code. Instead of merging after deserialization its merged when passing to rattler. I think the datastructure in the config should be kept as close to the source as possible.


allow passing a schema version to NewID()

Closes #15

Closing per earlier discussion, will follow up with branch-based approach


Allow only specific methods with DynamicModelViewSet

Sometimes views allow certain methods and not others.  You can whitelist the ones you want in DRF with, for instance:
class MyView(
        mixins.UpdateModelMixin,
        viewsets.GenericViewSet):

instead of using ModelViewSet which incorporates all actions.
How would you replicate this with a DynamicViewSet?

You can use this mixin to accomplish the same thing.

@aleontiev thanks for responding.  I saw that in looking through the code, but there's a bunch of code directly on DynamicModelViewSet which I'd be losing out on -- I didn't study what was in there, but figured I'd be losing something...


Apple ARM Processors Require Rosetta 2 to Build for gRPC Build Tools Support

I don't think this repository can be build on MacOs / Apple Sillicon

NO GOAL: depends on Rosetta
GOAL: Having the tooling "just works"

$ git clone https://github.com/dotnet/eShop

$ dotnet tool restore
# this repo is missing dotnet tool manifest for ef
$ dotnet new tool-manifest
$ dotnet tool install dotnet-ef
$ git add ./.config
$ git commit -m "Add required file for dotnet tool to avoid relying on a global computer state"

$ sudo dotnet workload restore
# dotnet workload is still bugged and require sudo on non-windows
# https://github.com/dotnet/sdk/issues/18585

$ dotnet restore eShop.Web.slnf
$ dotnet build eShop.Web.slnf
# should work

Current Result:
This repo depends on a package that is yet to be Apple ARM compliant:
dotnet build eShop.Web.slnf
MSBuild version 17.8.3+195e7f5a3 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.

  Restore operation started

  4 libraries restored in 0,07 seconds

  EventBus -> ~/dev/github/eshop/src/EventBus/bin/Debug/net8.0/EventBus.dll
  Ordering.Domain -> ~/dev/github/eshop/src/Ordering.Domain/bin/Debug/net8.0/Ordering.Domain.dll
  eShop.ServiceDefaults -> ~/dev/github/eshop/src/eShop.ServiceDefaults/bin/Debug/net8.0/eShop.ServiceDefaults.dll
  WebAppComponents -> ~/dev/github/eshop/src/WebAppComponents/bin/Debug/net8.0/WebAppComponents.dll
  IntegrationEventLogEF -> ~/dev/github/eshop/src/IntegrationEventLogEF/bin/Debug/net8.0/IntegrationEventLogEF.dll
  Mobile.Bff.Shopping -> ~/dev/github/eshop/src/Mobile.Bff.Shopping/bin/Debug/net8.0/Mobile.Bff.Shopping.dll
  Ordering.Infrastructure -> ~/dev/github/eshop/src/Ordering.Infrastructure/bin/Debug/net8.0/Ordering.Infrastructure.dll
  EventBusRabbitMQ -> ~/dev/github/eshop/src/EventBusRabbitMQ/bin/Debug/net8.0/EventBusRabbitMQ.dll
  WebhookClient -> ~/dev/github/eshop/src/WebhookClient/bin/Debug/net8.0/WebhookClient.dll
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003: The specified task executable "~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc" could not be run. System.ComponentModel.Win32Exception (86): An error occurred trying to start process '~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc' with working directory '~/dev/github/eshop/src/Basket.API'. Bad CPU type in executable [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003: The specified task executable "~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc" could not be run. System.ComponentModel.Win32Exception (86): An error occurred trying to start process '~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc' with working directory '~/dev/github/eshop/src/WebApp'. Bad CPU type in executable [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [~/dev/github/eshop/src/WebApp/WebApp.csproj]
  Identity.API -> ~/dev/github/eshop/src/Identity.API/bin/Debug/net8.0/Identity.API.dll
  PaymentProcessor -> ~/dev/github/eshop/src/PaymentProcessor/bin/Debug/net8.0/PaymentProcessor.dll
  OrderProcessor -> ~/dev/github/eshop/src/OrderProcessor/bin/Debug/net8.0/OrderProcessor.dll
  Webhooks.API -> ~/dev/github/eshop/src/Webhooks.API/bin/Debug/net8.0/Webhooks.API.dll
  Ordering.API -> ~/dev/github/eshop/src/Ordering.API/bin/Debug/net8.0/Ordering.API.dll
  Catalog.API -> ~/dev/github/eshop/src/Catalog.API/bin/Debug/net8.0/Catalog.API.dll
  Ordering.UnitTests -> ~/dev/github/eshop/tests/Ordering.UnitTests/bin/Debug/net8.0/Ordering.UnitTests.dll
  Catalog.FunctionalTests -> ~/dev/github/eshop/tests/Catalog.FunctionalTests/bin/Debug/net8.0/Catalog.FunctionalTests.dll
  Ordering.FunctionalTests -> ~/dev/github/eshop/tests/Ordering.FunctionalTests/bin/Debug/net8.0/Ordering.FunctionalTests.dll

Build FAILED.

~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003: The specified task executable "~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc" could not be run. System.ComponentModel.Win32Exception (86): An error occurred trying to start process '~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc' with working directory '~/dev/github/eshop/src/Basket.API'. Bad CPU type in executable [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [~/dev/github/eshop/src/Basket.API/Basket.API.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003: The specified task executable "~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc" could not be run. System.ComponentModel.Win32Exception (86): An error occurred trying to start process '~/.nuget/packages/grpc.tools/2.59.0/tools/macosx_x64/protoc' with working directory '~/dev/github/eshop/src/WebApp'. Bad CPU type in executable [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands) [~/dev/github/eshop/src/WebApp/WebApp.csproj]
~/.nuget/packages/grpc.tools/2.59.0/build/_protobuf/Google.Protobuf.Tools.targets(291,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute() [~/dev/github/eshop/src/WebApp/WebApp.csproj]
    0 Warning(s)
    2 Error(s)

Time Elapsed 00:00:02.14

Grpc.Tools only ship for macos x64 apparently, until Google actually update their package for Apple Silicon, should this repo offer an alternative way of using GRPC like for example protobuff-net ?

It's not a priority for us to avoid using Rosetta in our build process. But if you determine that the above tool works we'd be happy to consider a PR that uses it.

Hey,
not sure what's the status, I'm running (aka building) this on Apple's Ms processor no problem (the dev certificate for Aspire was a tricky one, otherwise works).

I have updated instructions in this PR: https://github.com/dotnet/eShop/pull/353
If you are running preview 7 you will need to checkout aspire-preview7 branch

can you re-open that issue @jamesmontemagno ?
The link PR just changed a few line on a README
current status: this repo won't build on Apple Silicon
the issue that the MSFT / Grpc implementation is not usable on MacOs
Unless the repo change to protobuf-net.GRPC or so that does not rely on Google protoc, this issue should stay open

@tebeco I am on an Apple M1 and was able to get it to run. Let's re-open it, but update the title with more information about the specific issue. As is, the directions build and run the project out of the box, but may need to document the grpc items.

I want to clarify here that you have Rosetta turned off? That is the main issue here?

Yep it's because you previously installed Rosetta 2
And it probably is silently depending on Rosetta 2 for running protoc
i don't think requiring Rosetta 2 on apple silicon for dotnet core should be a pre requisite for XPlat runtime/tooling
as far as i recall google tooling is nearly always ultra late to the game when it's for compatibility with technology that isn't theirs
so the short term here would be to find a way to either commit the generated code or moving out of the google tooling that is not compliant

Thanks for the information here. I will adjust and update the title of this issue.
Since this is a requirement of the library and it is an open ticket, I will document Rosetta 2 is required when running on Apple Silicon.

I will document Rosetta 2 is required when running on Apple Silicon.

I think depending on Rosetta 2 being mandatory for MacOS sort of means that the tooling is not XPlat yet, am I wrong ?

I'll reiterate what @mikekistler said above:

It's not a priority for us to avoid using Rosetta in our build process.

The fact that this sample happens to use tooling as part of the build process that isn't native arm64 isn't super interesting IMO. It affects neither the performance/functionality of the sample nor the educational value. Moreover, adding extra logic or committing generated code as you suggested above might actually lead to more confusion--keep in mind that this sample app is supposed to reflect best practices for how to do things. Having Rosetta disabled seems to be very uncommon (as one data point, you're the only person who has reported this, despite there being many devs trying this sample on macOS).
Consider chiming in on the grpc issue to voice support for the arm64 versions of the tools.

@JamesNK Is this something we can raise again on the gRPC tooling side? https://github.com/grpc/grpc/issues/25755

I'll reiterate what @mikekistler said above:

It's not a priority for us to avoid using Rosetta in our build process.

The fact that this sample happens to use tooling as part of the build process that isn't native arm64 isn't super interesting IMO. It affects neither the performance/functionality of the sample nor the educational value. Moreover, adding extra logic or committing generated code as you suggested above might actually lead to more confusion--keep in mind that this sample app is supposed to reflect best practices for how to do things. Having Rosetta disabled seems to be very uncommon (as one data point, you're the only person who has reported this, despite there being many devs trying this sample on macOS).
Consider chiming in on the grpc issue to voice support for the arm64 versions of the tools.

I understand what you're saying but it's not constructive from either side. The issue is existing since 2021, and this is not the first gRPC where we're saying multi-year delay reactivity from Google (just re-iterating)
My previous post added 2 possibles solutions, the first one would be to keep the repo as/is BUT add Condition within MSBuild to avoid running protoc as part of the build ... and get these file pre-generated / added to the repo for MacOs, that's all
Is it something that the MSFT GRPC tools for AspNetcore support ? the Opt-In running protoc and instead use specific C# file mapped

I'm afraid doing something non-standard here for this case isn't a priority for us in this sample application, for the reasons I mentioned above. If there was widespread demand for this, we may consider doing something but as it stands this isn't something we want to address.

@JamesNK Is this something we can raise again on the gRPC tooling side? grpc/grpc#25755

This should probably be done regardless of the presence of Rosetta 2 or not on devices.

heads up for @adityamandaleeka @jamesmontemagno @mikekistler
Latest MacOs Sonoma 14.5 broke a part of Rosetta 2 BTW
So even with the pre-requisite of Rosetta 2 this is not a reliable solution
https://www.reddit.com/r/docker/comments/1czh2wz/failed_to_start_emulated_container_on_sonoma_145/
https://forums.developer.apple.com/forums/thread/755840

I'm on Sonoma 14.5 and just checked that the non-native protoc executable used in this project works fine. The sample is able to build and run successfully.

you're right this part wasn't broken by the update, but relying on it seems unreliable as a peer dependency


What's the meaning of such bug logs?

roi logic is not implemented

https://github.com/ENOT-AutoDL/onnx2torch/pull/67
Feel free to open it again or create a new one if you have further questions.


Create Dockerfile

docker build -t bucketsnoop .
docker run -it -p 9000:9000 bucketsnoop
Will require Client to be able to change IP to submit to.

Cheers! Will merge once I've finished the settings section in the client


How to find the mount point on node for a dynamic PVC?

PVC is created by specify a glusterfs storage class. Is there a way to find out where is the mount point on the node?

It is not mounted until a pod uses it in its volume list. When kubelet starts the pod, it will mount the Gluster volume on the host where the pod is going to run. Once the pod exists, the volume is unmounted again.
See the Persistent Volumes concept for more details.

The path where OpenShift mounts the Gluster Volume on the host is something like this:
/var/lib/origin/openshift.local.volumes/pods/1eebe57d-b81e-11e8-8379-525400a4b9f3/volumes/kubernetes.io~glusterfs/db

The UUID is the pod:metadata:uuid from the running pod. The /db at the end is the spec:volumes:glusterfs:name.
For Kubernetes it is something very similar.
Alternatively you can manually mount the volume on one of the hosts. Get the PV for the PVC that holds the data, and inspect it. The spec:glusterfs:path is the name of the Gluster volume, and the spec:glusterfs:endpoints point you to the Endpoint object with the servernames (but you can use any Gluster server).

@shaozi have your questions been answered? If so, please close this issue. Thanks!

I end up with create a new pod to access the PVC.

@nixpanic  @shaozi
Related question - Does the PV always talk to the gluster node on the same host or can it talk to a remote gluster node? Let's say there are 3 gluster nodes/endpoints running provided in the gluster service, which of them does my pod talk to? Is it based on the same host, or it picks the one with the lowest latency?

Replication in Gluster (AFR) is done client side (mounted PVC), so the client talks to all Gluster servers that participate in the Gluster Volume (PV consisting out of bricks).


feat(pop-api): add call filter

Adds an allowed list call filter to chain extension.
pallet-contracts's CallFilter is not being used because it will allowb contracts to directly use call_runtime. Once the pop api pallet is introduced, the call filter should be implemented there.
There is a new example contract for testing purposes that tests that the call filter works.

It would be good to set the same filter for pallet-contracts in general ?
In case some contracts decide to not use pop-api to call the runtime.

We do not want to expose call_runtime directly because then we may break contracts with runtime upgrades. If we were to utilize the CallFilter in pallet-contracts, we would have to ONLY allow calls going into the Pop API pallet. Then we can filter a second layer in to ensure the next call is allowed


Implement TAU-based invulnerability logic

Overhauls the invuln module with a rewrite into typescript, and a total rewrite of TAU-based invuln logic.
New non-legacy logs should now, with config where required, be significantly more accurate.
TODO

[x] changelog entry


crash occur when catching advertise

sometime, panic occur in  func (a *Advertisement) unmarshall(b []byte)

sorry.
I made a pull request by mistake.
Please ignore it.


Revisit choke group with CC mapping

Hi,
Last time I check the choke group with the same number, it still has issue (which i think Paul had fixed in some last build), but now seems trouble again.
The issue is, when mapping the region using CC (common use for hihat mapping to CC 4 for play with e-drums kit), which the openness degree mapped to a same key and across different CC level. With the last fix (same group/off_by number don't choke), however when using CC-mapped like this, it should be choke.
I attach a test file for quick check :
choke_cc_check.zip

Hi @kinwie ! I'll check it out. Does sforzando handles it properly for me to compare?

Maybe try the PR above? What I put is more than the CC switch, it's going to choke the region if it is disabled by any mean (CC, keyswitch, ...). Maybe that is too much but it seemed to match what is expected more or less: if a region is currently disabled, it should be considered in "another choke group" regardless of the conditions.

I'll change it to only CC though, after thinking about it.

thanks @paulfd for  looking into this. Where to download the new setup btw?

If you go to https://github.com/sfztools/sfizz/actions, you have the list of CI runs. If you click on the last one related to the pull request, it will load up the summary, and there you have the artifacts to download.
The direct link for this one is https://github.com/sfztools/sfizz/actions/runs/1456579150.

Yes, I got it. Tested and the choke works just fine now with the CC. Thanks for this, I feel relieved :)
I just wish this can become the "Native SFZ choke behavior" since it's what Rene's original design and perfected in sfizz!
Anyway, everytime I click something on the UI, e.g. moving the CC 4 knob, it crashed VstHost (32-bit, vst3), also SaviHost. It's a random crash and just because when clicking on the UI. Maybe @jpcima knows something about it?

Maybe it's me, I changed many things in the UI recently. I'll put up another issue for it.

Thanks for the report, as always !

Yes, I got it. Tested and the choke works just fine now with the CC. Thanks for this, I feel relieved :) I just wish this can become the "Native SFZ choke behavior" since it's what Rene's original design and perfected in sfizz!

Good thing is we have a nice test coverage for all these cases so it should keep getting better.


Add TLA+ syntax highlighting to the manual

Add TLA+ syntax highlighting to the manual:

Provide a rudimentary TLA+ language lib for highlight.js (the library used by mdBook): 20c1b06c1ad943571bd292d3faffa1227f1a79d0
Hook up the library in our mdBook config. This requires a bit of wiring in 764fce74cccd86a41087623702fb4849a70f29c4
Building the language lib is a bit finicky, so I'm including a minified CDN build of the language lib in 7d8542729734521ec6da87698283c8ffbe671067

This should also make it work OOTB for the published manual at https://apalache.informal.systems/docs/.

[ ] ~Tests added for any new code~
[ ] ~Ran make fmt-fix (or had formatting run automatically on all files edited)~
[x] Documentation added for any new functionality
[x] Entries added to ./unreleased/ for any new functionality

Codecov Report

Merging #1972 (764fce7) into unstable (f0327a9) will increase coverage by 0.60%.
The diff coverage is n/a.

:exclamation: Current head 764fce7 differs from pull request most recent head 03cd2fc. Consider uploading reports for the commit 03cd2fc to get more accurate results

@@             Coverage Diff              @@
##           unstable    #1972      +/-   ##
============================================
+ Coverage     77.14%   77.74%   +0.60%
============================================
  Files           415      415
  Lines         12714    12749      +35
  Branches        573      565       -8
============================================
+ Hits           9808     9912     +104
+ Misses         2906     2837      -69

Impacted Files
Coverage Δ

...t/forsyte/apalache/shai/TransExplorerService.scala
88.88% <0.00%> (-11.12%)
:arrow_down:

...he/io/annotations/parser/CommentPreprocessor.scala
97.80% <0.00%> (+1.09%)
:arrow_up:

...n/scala/at/forsyte/apalache/io/OutputManager.scala
15.38% <0.00%> (+1.53%)
:arrow_up:

...ala/at/forsyte/apalache/tla/imp/SanyImporter.scala
85.93% <0.00%> (+3.12%)
:arrow_up:

...main/scala/at/forsyte/apalache/tla/imp/utils.scala
5.26% <0.00%> (+5.26%)
:arrow_up:

...a/typecomp/signatures/ApalacheOperSignatures.scala
100.00% <0.00%> (+11.76%)
:arrow_up:

...ache/tla/typecomp/subbuilder/ApalacheBuilder.scala
100.00% <0.00%> (+27.27%)
:arrow_up:

...he/tla/typecomp/unsafe/UnsafeApalacheBuilder.scala
100.00% <0.00%> (+30.00%)
:arrow_up:

.../scala/at/forsyte/apalache/infra/passes/Pass.scala
100.00% <0.00%> (+50.00%)
:arrow_up:

...a/at/forsyte/apalache/infra/ExceptionAdapter.scala
50.00% <0.00%> (+50.00%)
:arrow_up:

... and 10 more

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 f0327a9...03cd2fc. Read the comment docs.


Landing zone template can't be run in China Azure

In China Azure, select "deploy a customer template" and then "Azure Landing Zone" and fill in with the required info. And then select "Review + create". Then following issue pops up:
{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The template variable 'azPrivateDnsPolicyAssignment' is not valid: The language expression property 'https://management.chinacloudapi.cn' doesn't exist, available properties are 'https://management.azure.com/, https://management.usgovcloudapi.net'.. Please see https://aka.ms/arm-template-expressions for usage details.'."}

Hi @zhouease,
Thanks for the issue. Unfortunately, the portal experience is not supported for Azure China.
Please deploy via https://github.com/Azure/Enterprise-Scale/blob/main/eslzArm/README-AzureChina.md
Or consider ALZ-Bicep - https://aka.ms/alz-bicep


Generate a docs website

Automatically generate and deploy a website for the docs when we push code to master & dev

✅ Docs generator
✅ CI/CD configured
⚠ Just waiting on the repository admin to set the GitHub Pages source branch to gh-pages


Documentation update after moving HTTP to Sender module

Hello Rollbar team,
I am just new using Rollbar (specially on vanilla Java). I had to integrate you lib with a logger and, therefore, use what you say 'Custom usage'. I saw myself trying to sent a Payload p.send() unsuccessfully. After some digging into your code I realized that you moved HTTP to sender module. Thus, sending a Payload changed slightly.
Since documentation wasn't updated accordingly, I decided to send you guys a PR approaching it. I thing this is useful for developers to be updated.

This threw me off too. Thank you @xeviknal


Check document access before showing users

#4

Current coverage is 94.29% (diff: 88.23%)

Merging #19 into master will decrease coverage by 0.11%

@@             master        #19   diff @@
==========================================
  Files            55         56     +1
  Lines          1143       1156    +13
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1079       1090    +11
- Misses           64         66     +2
  Partials          0          0

Powered by Codecov. Last update 4d6c79f...69123a0


project delete throws error if a linked component is deleted

/kind bug

What versions of software are you using?
Operating System:
supported
Output of odo version:
master
How did you run odo exactly?
$ odo create nodejs frontend --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/ --project test123
$ odo create java:8 backend --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/openjdk/ --project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/openjdk/

$ odo link backend --component frontend --project test123 --port 8080 --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/openjdk/ --wait

$ odo component delete backend --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/openjdk/

$ odo project delete test123
This project contains the following applications, which will be deleted
Application app
 ✗  secrets "backend-app-8080" not found

Actual behavior
$ odo project delete test123 -f
This project contains the following applications, which will be deleted
Application app
 ✗  secrets "backend-app-8080" not found

Expected behavior
Project delete should not throw error
Any logs, error output, etc?

/close
duplication of https://github.com/openshift/odo/issues/2355


Alert does not display if the first character of the message is a quote.

This fails:
note := gosxnotifier.NewNotification("\"Welcome\" was updated.")
....
err := note.Push();
....

You can use strconv.QuoteToASCII link.
message := strconv.QuoteToASCII("\"Welcome\" was updated.")
note := gosxnotifier.NewNotification(message)
....
err := note.Push();
....


remove from List of Addnodes

Please remove the following hosts from the "List of Addnodes"
https://github.com/gridcoin-community/Gridcoin-Wiki/wiki/List-of-Addnodes
de.gridcoin.pl
no.gridcoin.pl
uk.gridcoin.pl
I will not maintain them anymore.
Regards,
Artur Pedziwilk

Done


Error message  'deploymentName' exceeds maximum length of '64'.

Describe the bug
I've created 2 new Policy Sets in a new branch and after the PR the AzOps Push pipeline starts in Azure DevOps. The deployments stops with the following error:
Write-AzOpsLog: /var/lib/app/entrypoint.ps1:105
Line |
 105 |              Write-AzOpsLog -Level Error -Topic "entrypoint" -Message  …
     |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | [14:15:32.8192] (entrypoint) [14:15:32.8103]
     | (New-AzOpsDeployment) Template Validation Failed
     | 'deploymentName' exceeds maximum length of '64'.

##[error]Bash exited with code '1'.

what is the name of file and what resource is it deploying?

Hi Uday,
The names of the files are;

Microsoft.Authorization_policySetDefinitions-Demo-Azure-Container-Registry-A.parameters.json
Microsoft.Authorization_policySetDefinitions-Demo-Azure-Container-Registry-S.parameters.json

It's deploying a Policy Initiative on the Top Management Group scope.
{
  "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {
    "input": {
      "value": {
        "Name": "Demo-ACR-A",
        "PolicySetDefinitionId": "/providers/Microsoft.Management/managementGroups/ES/providers/Microsoft.Authorization/policySetDefinitions/Demo-ACR-A",
        "Properties": {
          "Description": "This Policy Set bundles all Policy Definitions for the Azure Container Registry Service with regard to the Advanced Controls.",
          "DisplayName": "Demo-ACR-A",
          "Parameters": {},
          "PolicyDefinitionGroups": null,
          "PolicyDefinitions": [
            {
              "policyDefinitionReferenceId": "6159304146578410160",
              "policyDefinitionId": "/providers/Microsoft.Management/managementGroups/es/providers/Microsoft.Authorization/policyDefinitions/DEMO-ACR-AdminUser",
              "parameters": {
                "effect": {
                  "value": "Deny"
                }
              }
            },
            {
              "policyDefinitionReferenceId": "17900905191361092817",
              "policyDefinitionId": "/providers/Microsoft.Management/managementGroups/es/providers/Microsoft.Authorization/policyDefinitions/DEMO-ACR-SKUSetting",
              "parameters": {
                "allowedAzureContainerRegistrySKU": {
                  "value": "Premium"
                },
                "effect": {
                  "value": "Deny"
                }
              }
            },
            {
              "policyDefinitionReferenceId": "7378665652881350983",
              "policyDefinitionId": "/providers/Microsoft.Management/managementGroups/es/providers/Microsoft.Authorization/policyDefinitions/DEMO-ACR-FirewallDeploy",
              "parameters": {
                "effect": {
                  "value": "Append"
                }
              }
            },
            {
              "policyDefinitionReferenceId": "5371675718443658518",
              "policyDefinitionId": "/providers/Microsoft.Management/managementGroups/es/providers/Microsoft.Authorization/policyDefinitions/DEMO-ACR-FirewallChange",
              "parameters": {
                "effect": {
                  "value": "Deny"
                },
                "allowedAddressRanges": {
                  "value": [
                    "<IP_ADDRESS>",
                    "<IP_ADDRESS>/27"
                  ]
                }
              }
            },
            {
              "policyDefinitionReferenceId": "943646168861518825",
              "policyDefinitionId": "/providers/Microsoft.Management/managementGroups/es/providers/Microsoft.Authorization/policyDefinitions/Deploy-Diagnostics-ACR",
              "parameters": {
                "logAnalytics": {
                  "value": "/subscriptions/a0633a75-0fad-4e44-8d77-9ebd184ed938/resourcegroups/es-mgmt/providers/microsoft.operationalinsights/workspaces/es-la-a0633a75-0fad-4e44-8d77-9ebd184ed938"
                }
              }
            },
            {
              "policyDefinitionReferenceId": "3397024401318903222",
              "policyDefinitionId": "/providers/Microsoft.Authorization/policyDefinitions/5f0f936f-2f01-4bf5-b6be-d423792fa562",
              "parameters": {
                "effect": {
                  "value": "AuditIfNotExists"
                }
              }
            },
            {
              "policyDefinitionReferenceId": "1976285719169009144",
              "policyDefinitionId": "/providers/Microsoft.Authorization/policyDefinitions/c25d9a16-bc35-4e15-a7e5-9db606bf9ed4",
              "parameters": {
                "effect": {
                  "value": "AuditIfNotExists"
                }
              }
            }
          ]
        },
        "ResourceId": "/providers/Microsoft.Management/managementGroups/ES/providers/Microsoft.Authorization/policySetDefinitions/Demo-ACR-A",
        "ResourceName": "Demo-ACR-A",
        "ResourceType": "Microsoft.Authorization/policySetDefinitions",
        "SubscriptionId": null
      }
    }
  }
}

can you please try cloning this repo and retry?
https://github.com/Azure/AzOps-Accelerator

Any updates on this?

@stefanstranger - I'm going to close this issue, please re-open this if you're still experiencing this behavior with the new AzOps implementation.

Hi Lyon,
Everything is working correctly with the new AzOps-Accelerator solution.
Thanks.
Stefan


Open comments section in new tab

Hi, can we get a feature to be able to automatically open posts and comments section in a new tab?
There's already an option to open all external links in a new tab, but that doesn't work for internal links, like text posts and comments
Thank you!

Sounds like a good idea, will look into it.


[BUG] DlTable - unit test fails randomly

@fadiDL @guyDataloop see here - the test fails, then runs just fine on the 2nd attempt with no code changes.

and again - but this time it is a different test

feels like this happens more often now


operator: do not reconcile all IOPs if REVISION env is set to blank

Please provide a description of this PR:
Currently operator which has REVISION env set to "" or unset tries to reconcile IOPs of all revisions. Thus there is no easy way to allow migration from a default install of istio to a revisioned install without changing REVISION to be default at multiple IOPs to avoid this behavior. However that introduces multiple changes needed in the environment and possibly restarting all gateways deployments since now the IOPs are expected to have the revision as well.
With this PR the intent to only reconcile a non revisioned IOP (blank revision) and not others is honored when REVISION env is present but blank. If env is not set, the behavior remains same.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @kanurag94. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test

/retest

/retest all

@tanujd11: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test bookinfo-build
/test gencheck
/test integ-ambient
/test integ-basic-arm64
/test integ-cni
/test integ-distroless
/test integ-ds
/test integ-helm
/test integ-ipv6
/test integ-operator-controller
/test integ-pilot
/test integ-pilot-istiodremote
/test integ-pilot-istiodremote-mc
/test integ-pilot-multicluster
/test integ-security
/test integ-security-istiodremote
/test integ-security-multicluster
/test integ-telemetry
/test integ-telemetry-discovery
/test integ-telemetry-istiodremote
/test integ-telemetry-mc
/test lint
/test macbuildcheck
/test release-notes
/test release-test
/test unit-tests
/test unit-tests-arm64

The following commands are available to trigger optional jobs:

/test benchmark
/test experimental-tracing
/test integ-ambient-calico
/test integ-assertion

Use /test all to run the following jobs that were automatically triggered:

gencheck_istio
integ-ambient_istio
integ-basic-arm64_istio
integ-cni_istio
integ-distroless_istio
integ-ds_istio
integ-helm_istio
integ-ipv6_istio
integ-operator-controller_istio
integ-pilot-istiodremote-mc_istio
integ-pilot-istiodremote_istio
integ-pilot-multicluster_istio
integ-pilot_istio
integ-security-istiodremote_istio
integ-security-multicluster_istio
integ-security_istio
integ-telemetry-discovery_istio
integ-telemetry-istiodremote_istio
integ-telemetry-mc_istio
integ-telemetry_istio
lint_istio
macbuildcheck_istio
release-notes_istio
release-test_istio
unit-tests-arm64_istio
unit-tests_istio

In response to this:

/retest all

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/test all

@kanurag94: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
e299942864f5f875ddab1a60a9b695013d98650e
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@howardjohn @hanxiaop gentle ping

Gentle ping @hanxiaop


ME conduit incorrectly reporting "number installed" on ME network

Here I have a screen shot example of the problem, under the floor there are about 80 ME conduits and 60 ME dense conduits.
However the ME network is reporting numbers incorrectly. As you will see in the screenshot this network believes there are 37,000 Dense ME conduit installed and doesn't even see the ME conduit.
(however the line connected by ME conduit is still functioning)
As you will also see the Network truly believes that 37k dense conduit is truly installed and the energy usage reflects that.
Screenshot: http://i.imgur.com/jVA6lyL.png

This has been fixed for the next version


Does sealpir support multi-core computing？

I found the following information in your paper “We run the PIR servers on H16 instances (16-core 3.6 GHz Intel Xeon E5-2667 and 112 GB RAM), and clients on F16s instances (16-core, 2.4 GHz Intel Xeon E5-2673 and 32 GB RAM), all running Ubuntu 16.04.”. It seems that sealpir support multi-core parallel computing. But when I run main.cpp, I only use one cpu core.

We only use 1 CPU in all of the experiments in the paper.


Add Devise and Authentication

Hello Reviewer! 👋🏾

In this pull request, me and @brainskev  did the following things :

Here is a concise list of tasks we have completed :-

Remove current_user method in ApplicationController. Devise will provided us with one.
Install and setup Devise.
Add a new route for /users/sign_up.
Add a new view for /users/sign_up.
Add a new controller action for users#new.
Add a new model for User.
Add a migration to create the users table.
Add a password_confirmation field to the users table.
Configure Devise to use the users table.
Add a new route for /users/sign_in.
Add a new view for /users/sign_in.
Add a new controller action for users#login.
Configure Devise to send a confirmation email to new users.
Add a new route for /users/password/reset.
Add a new view for /users/password/reset.
Add a new controller action for users#reset_password.
Modify the views in Devise for registration and login to match the wireframes from the Sneak Peek and use custom styling.

@Whoistolu Thanks.


DPF-Post Refactoring

Project: DPF Refactoring
Aim
Simple, and intuitive, yet powerful, easy-to-use entry level library wrapping calls to the PyDPF-Core library.
Requirements

Simple: Mostly focused on exposing data and current post-processing operations. No complicated heavy data manipulation.

Intuitive: Similar to other Python libraries (numpy, pandas, pyvista), flat APIs.

Powerful: Using PyDPF-Core under the hood. Everything is just exposing PyDPF-Core operators/functions.

Easy-to-use: No more than three lines to retrieve/plot data.

Features

Rely mainly on kwargs arguments, which will just apply Simulation class methods (PyDPF-Core operators under the hood).

Approach to general structural

from ansys.dpf import post

# Loading structural analysis
simulation = post.load_simulation("myfile.rst")

Fields of Simulation object.
>>> dir(simulation)
- Results (wrapper of results container)
- Geometry
- Mesh (Wrapper of dpf mesh)
- Boundary_conditions
- Structural/Fluids/Explicit #(Specific for each physics/solver?)

API Pseudo-code
Retrieving data object
>>> simulation.results.elemental_stress(
    time_steps=[1, 3],
    entity="elemental", # default
    )
DataObject
-------------
Elemental Stress Results
Applied to:
- Time steps: 1, 3

Retrieving numpy ndarrays
>>> # Getting array data
>>> arr = simulation.results.elemental_stress(
    time_steps=[1, 2],
    entity="nodes", # default
    named_selection="my_cm_selec"
    ).to_array()
array([
    [0.1, 0.2, 0.2, 0.3, 0.2, 0.4],
    [0.2, 0.1, -0.2, 0.3, 0.1, 0.2]
    [0.5, 0.2, 0.4, -0.1, 0.1, 0.35]
    ....]
    )

Retrieving pandas Dataframes
Where:

ids = nodes/elements ids
columns = stress component values

>>> df = simulation.results.elemental_stress(
    time_steps=[1, 2],
    entity="nodes", # default
    components= ["XX", "YY"],
    named_selection="my_cm_selec"
    ).to_dataframe()

      XX    YY
1    0.1  -1.3
2    0.2   2.4
...

Retrieving DPF operators
fc = simulation.results.elemental_stress(
    time_steps=[1, 2],
    entity="nodes", # default
    named_selection="my_cm_selec",
    return_op=True
    )

Retrieving plotter objects
pl = simulation.results.elemental_stress(
    time_steps=[0],
    entity="elements",
    named_selection= "my_cm_selection"
).plot(
    colormap="viridis",
    return_plotter=True
)

Applying selections
from ansys.dpf.post import select

# Two approaches
## Function based
selection = select(
    simulation,
    entity="nodes"
)  # Does not change 'simulation' state

## Method based
simulation.apply_selection(
    entity="nodes",
) # Remains applied in 'simulation' until cleared/deactivated

# You can reselect (applying selections to selections)
selection = selection.apply(nodes=[1,20])

simulation.results.nodal_displacements(
    selection=selection
    ).plot()

Worflow
Selection - @cbellot000

Time
Spatial (mesh, parts)
Qualifiers

Result - @PProfizi

Location (Elemental/Nodal/ElementalNodal)
Result (displacements/stresses/...)
Component ("X", "Y", ...)

Output - @MaxJPRey

DataObject (with helpers: .min(), .max(), etc)

Array
Plot
Dataframe

The use of the word Simulation instead of Solution was apparently not done on purpose but actually could be an interesting choice.

The use of the word Simulation instead of Solution was apparently not done on purpose but actually could be an interesting choice.

#Serendipity


Inconsistency between @dataclass and BaseModel

Bug
For bugs/questions:

OS: OSX
Python version: 3.7.2
Pydantic version: 0.23

There seems to be an inconsistency between using dataclasses or BaseModel whereas a dataclass raises a TypeError but BaseModel raises a pydantic ValidationError that you are expecting.
from pydantic.dataclasses import dataclass

@dataclass
class User:
    id: int

user = User()
TypeError: __init__() missing 1 required positional argument: 'id'

Same with BaseModel
from pydantic import BaseModel

class User(BaseModel):
    id: int

user = User()
pydantic.error_wrappers.ValidationError: 1 validation error
id
  field required (type=value_error.missing)

I'm afraid that's just a fundamental difference between them.
Unless someone else has am idea I don't, I don't think this is fixable.

@samuelcolvin thank you for the response and the library

No problem, thanks for using it.