Test full .NET Framework class lib using Sdk style csproj

Hello,
Thanks for the project, I tested it out on a .net standard 2.0 class lib and it worked great out of the box.
I was wondering if my unique scenario is potentially supported.
I have converted my .NET framework class libraries, which target .NET 4.6.1 to use the Sdk .csproj format.
Example
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net461</TargetFramework>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <Optimize>false</Optimize>
    <OutputPath>bin\Debug\</OutputPath>
    <DefineConstants>DEBUG;TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <DebugType>pdbonly</DebugType>
    <Optimize>true</Optimize>
    <OutputPath>bin\Release\</OutputPath>
    <DefineConstants>TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" Version="9.0.1" />
    <PackageReference Include="RestSharp" Version="106.1.0" />
  </ItemGroup>
  <ItemGroup>
    <Reference Include="System.Configuration" />
    <Reference Include="System.Web" />
    <Reference Include="System.Data.DataSetExtensions" />
    <Reference Include="Microsoft.CSharp" />
    <Reference Include="System.Net.Http" />
  </ItemGroup>
</Project>

So this project uses PackageReference, targets .net 4.6.1 and builds / runs just fine.
I reference it in my Test project which uses the traditional csproj and doesn't use PackageReference.
When I run the tests (using xUnit) in Visual Studio 2017 or at the command line using dotnet test the tests are run and the results are displayed.
Example
$ dotnet test
Build started, please wait...
Build completed.

Test run for D:\dev\company\company\Company.Tests\bin\Debug\Company.Tests.dll(.NETFramework,Version=v4.6.1)
Microsoft (R) Test Execution Command Line Tool Version 15.7.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

Total tests: 7. Passed: 7. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 1.2361 Seconds

When I run $ dotnet test //p:CollectCoverage=true //p:CoverletOutputFormat=opencover (// escapes / in git bash) I get this response.
Starting test execution, please wait...
[xUnit.net 00:00:00.2213043] Skipping: Company.Tests (could not find dependent assembly 'xunit.core, Version=2.0.0')
No test is available in D:\dev\company\company\Company.Tests\bin\Debug\Company.Tests.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

More can be read about using the Sdk project format with .NET full framework
https://natemcmaster.com/blog/2017/03/09/vs2015-to-vs2017-upgrade/
https://github.com/hvanbakel/CsprojToVs2017
https://github.com/dotnet/project-system/blob/master/docs/opening-with-new-project-system.md

Also having issues with a .Net Core application targeting net461, though in my case all tests run and complete successfully but no code coverage is calculated.
Starting test execution, please wait...

Total tests: 77. Passed: 77. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 1.4099 Minutes

Calculating coverage result...
  Generating report 'D:\...\coverage.json'

+--------+--------+--------+--------+
| Module | Line   | Branch | Method |
+--------+--------+--------+--------+

Hi @RockfordSP and @sgwatgit at this moment Coverlet has been tested with only .NET Core applications that target netcoreapp and netstandard. It should work with the full .NET framework with only minor adjustments but it's currently not on my immediate radar

@tonerdo - I assume it is still the case that .net framework is still not supported?

@jessekingf the latest release now does


add docs for notification api routes

add docs for retrieving solutions with no comments and feedbacks marked "unread"

@bermannoah 👍


PR for v0.3.1 and release

Codecov Report

Merging #21 into master will decrease coverage by 1.53%.
The diff coverage is 63.07%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   69.92%   68.39%   -1.54%
==========================================
  Files          15       15
  Lines         798      889      +91
==========================================
+ Hits          558      608      +50
- Misses        240      281      +41

Impacted Files
Coverage Δ

tooldog/analyse/container.py
41.02% <ø> (ø)
:arrow_up:

tooldog/analyse/language_analyzer.py
26% <0%> (-5.71%)
:arrow_down:

tooldog/analyse/code_collector.py
36.73% <0%> (ø)
:arrow_up:

tooldog/analyse/tool_analyzer.py
27.9% <0%> (ø)
:arrow_up:

tooldog/main.py
45.18% <62.5%> (-2.03%)
:arrow_down:

tooldog/annotate/cwl.py
81.69% <71.42%> (-4.59%)
:arrow_down:

tooldog/biotool_model.py
92.3% <71.42%> (-7.7%)
:arrow_down:

tooldog/annotate/galaxy.py
88.28% <78.57%> (-6.34%)
:arrow_down:

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 088fc20...2c68ef4. Read the comment docs.


python3Packages.more-itertools: 8.8.0 -> 8.10.0

Motivation for this change
Noticed update. This is a large rebuild, >10k packages.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build python38Packages.pytest python39Packages.pytest

I have a feeling that the cause for the rebuild explosion is purely down to is being a pytest dependency, and for me all combinations of python 3.8/3.9 pytest_4/pytest_5/pytest_6 build (on a cherry-pick back to master`) on macos 10.15 and nixos x86_64.

@risicle makes sense, good spot.


I am able to initalized the Datadog but unable to send any events or logs (Android iOS)

W/Datadog ( 3737): The Datadog library has already been initialized.
W/Datadog ( 3737): RumMonitor has already been registered
W/Datadog ( 3737): A RUM event was detected, but no view is active. To track views automatically, try calling the DatadogConfig.Builder.useViewTrackingStrategy() method.
W/Datadog ( 3737): You can also track views manually using the RumMonitor.startView() and RumMonitor.stopView() methods.
@tshedor  Please Help in bypassing or help in understanding whats the issue
And i tried to change my environment and i get one more from datadog log
Unable to send batch [510 bytes] (LogsOkHttpUploader) because your token is invalid. Make sure that the provided token still exists.+ flutter datadog**

Hi @maheshmaersk thanks for using datadog_flutter.
I think this line explains it: Unable to send batch [510 bytes] (LogsOkHttpUploader) because your token is invalid. Make sure that the provided token still exists.+ flutter datadog**
Please check out Datadog's docs for generating a client token. Don't use the client token generated when create a RUM application; only use the application ID generated.

Hello @tshedor We are using the application ID Generated but there seems this issue of clientId being a mandatory Parameter
await DatadogFlutter.initialize(
clientToken: Platform.isIOS
? Constants.DATADOG_CLIENT_IOS_TOKEN
: Constants.DATADOG_CLIENT_ANDROID_TOKEN,
environment: 'preprod',
androidRumApplicationId: Constants.ANDROID_RUM_APPLICATION_ID,
iosRumApplicationId: Constants.IOS_RUM_APPLICATION_ID,
serviceName: 'Project Name'),
trackingConsent: TrackingConsent.granted,
);
and we are using the right client token and Rum ID

@maheshmaersk you should not need two different client tokens between the platforms; there should only be one client token. I don't follow the clientId as a mandatory parameter; there is no parameter with this name.

Hello @tshedor,
Thank you so much on the clientToken currently we are able to see this over the console of Flutter IDE
V/Datadog ( 2683): Batch [527 bytes] sent successfully (LogsOkHttpUploader).
W/Datadog ( 2683): A RUM event was detected, but no view is active. To track views automatically, try calling the DatadogConfig.Builder.useViewTrackingStrategy() method.
W/Datadog ( 2683): You can also track views manually using the RumMonitor.startView() and RumMonitor.stopView() methods.
But still we are not seeing any logs in the Dashboard Panel is there something which has been missed

@maheshmaersk I'd encourage you to double check your Datadog configuration, your app code, or reach out to<EMAIL_ADDRESS>. The example app uploads logs successfully.


Fix 4 flaky tests in TestGenerateJsonSchema

Tests testSinglePropertyDependency, testMultiplePropertyDependencies, testSchemaPropertyDependency, and testSchemaPropertyDependencies were flaky because the mapper doesn't always write a string in deterministic order and the order of 5 properties in properties was nondeterministic. I configured the mapper so that it will always return fields in the schema in alphabetical order. I also set the order in which property 1-5 should be returned.

Thanks!


fix: small UI fix

fix: small UI fix

Thanks for the PR @OlegYak.
Before we get this in, can you please provide more details and potentially screenshots of the issue that this is fixing?

Closing this PR as it's stale and it has no context on what it is fixing. @OlegYak please reopen when you get back to us with more details


🤖 Add authors and contributors to Practice Exercises

If you got tagged in this PR, it is because you are being credited for work you've done in the past on Exercism here, and we want to ensure you don't miss out on the recognition you deserve 🙂

With v3, we've introduced the idea of exercise authors and contributors. This information is stored in the exercises' .meta/config.json files (see the docs).
Concept Exercises, which are all new, already contain authors and contributors. Practice Exercises though are missing this information. In this PR, we attempt to populate the authors and contributors of Practice Exercises based on their commit history.
Maintainer TODO list
These are the things you, the maintainers, should do:

[ ] Check the authors and contributors, adding/removing users where the data is missing or incorrect
[ ] Double-check any renamed Practice Exercises
[ ] Check for Practice Exercises with missing authors, which are most likely due to the author not being on GitHub anymore
[ ] Add additional authors if you know that a Practice Exercise has actually been created by more than one author

For clarity, authors should be the people who originally created the exercise on this track. Contributors should be people who have substantially contributed to that exercise. PRs for typos or multiple-exercise PRs do not automatically mean someone should be considered a contributor to that exercise. Those non-exercise-specific contributions will get recognition through Exercism's reputation system in v3.
If you find something needs updating, just push a new commit to this PR.
Automatic Merging
We will automatically merge this PR before we launch v3, but will give the maximum time we can to maintainers to review it first.

The rest of this issue explains how this PR has been generated. You do not need to read it.
Algorithm
We start out by looking at the current Practice Exercises. For each Practice Exercise, we'll look at the commit history of its files to see which commits touched that Practice Exercise. How renames are handled is discussed in the "Renames" section later in this document.
Any commit that we can associate with a Practice Exercise is used to determine authorship/contributorship. Here is how we assign authorship/contributorship:
Authors

Find the Git commit author of the oldest commit linked to that Practice Exercise.
Find the GitHub username for the Git commit author of that commit
Add the GitHub username of the Git commit author to the authors key in the .meta/config.json file

Contributors

Find the Git commit authors and any co-authors of all but the oldest commit linked to that Practice Exercise. If there is only one commit, there won't be any contributors.
Exclude the Git commit author and any co-authors of the oldest commit from the list of Git commit authors (an author is not also a contributor)
Find the GitHub usernames for the Git commit authors and any co-authors of those commits
Add the GitHub usernames of the Git commit authors and any co-authors to the contributor key in the .meta/config.json file

We're using the GitHub GraphQL API to find the username of a commit author and any co-authors. In some cases though, a username cannot be found for a commit (e.g. due to the user account no longer existing), in which case we'll skip the commit.
Renames
There are a small number of Practice Exercises that might have been renamed at some point. You can ask Git to "follow" a file over its renames using git log --follow <file>, which will also return commits made before renames. Unfortunately, Git does not store renames, it just stores the contents of the renamed files and tries to guess if a file was renamed by looking at its contents. This can (and will) lead to false positives, where Git will think a file has been renamed whereas it hasn't. As we don't want to have incorrect authors/contributors for exercises, we're ignoring renames. The only exception to this are known exercise renames:

bracket-push was renamed to matching-brackets
retree was renamed to satellite
resistor-colors was renamed to resistor-color-duo
kindergarden-garden was renamed to kindergarten-garden

If you know of a rename of a Practice Exercise, please check to see if its authors and contributors are correctly set.
Exclusions
There are some commits that we skip over, which thus don't influence the authors/contributors list:

Commits authored by dependabot[bot], dependabot-preview[bot] or github-actions[bot]
Bulk update PRs made by ErikSchierboom or kytrinx to update the track

Tracking
https://github.com/exercism/v3-launch/issues/24

cc @amscotti, @arthurchipdean, @arueckauer, @brettsantore, @camilopayan, @codedge, @DerTee, @dkinzer, @Dog, @dstockto, @duffn, @ecrmnn, @ErikSchierboom, @G-Rath, @Hrumpa, @jeslopcru, @joseph-walker, @jrdnull, @karptonite, @kenden, @kip-13, @kk-r, @kunicmarko20, @kytrinyx, @lafent, @leNEKO, @Leprechaunz, @LucasThompson, @marvinrabe, @masters3d, @MatheusNaldi, @MichaelBunker, @mikeSimonson, @mk-mxp, @neenjaw, @nhoag, @petemcfarlane, @peteraba, @Pierre-Vdsp, @pmatseykanets, @pminten, @rossbearman, @schorsch3000, @Scientifica96, @TFarla, @tstirrat15, @woylie, @yisraeldov, @zembrowski as you are referenced in this PR

remaining configlet issues to be fixed in #380.
I'm going to merge it before it gets out of sync again with the repo.  It's been here for quite a while without people citing a need for it to be updated, probably good to go now


Slightly inaccurate when integrating over floor/ceil.

I'm not sure if this is a known limitation or something that should be an issue. I suspect it applies to all step-wise functions but I haven't checked.
>> ∫ (0, 1, ⌈x⌉, dx)
0.9995833333

This should be 1 exactly, but I suspect that the code falls back to numerical integration in these cases.
More examples:
>> ∫ (1/10000, 1, ⌈x⌉, dx)
0.9999 # correct
>> ∫ (1/100000, 1, ⌈x⌉, dx)
1  # should be 0.99999
>> ∫ (1/1000000, 1, ⌈x⌉, dx)
1 # should be 0.999999
>> ∫ (1/10000000, 1, ⌈x⌉, dx)
1.0004165666   # over one? should be 0.9999999

Well, integration will often not be perfectly accurate, since functions can really vary a lot. Sometimes it's spot on, sometimes it's not. in this case, it looks like it's related to floating point numbers not being perfectly accurate, since it gets less accurate when you have numbers like 1/100000. This is the kind of thing I'm interested in making more accurate though, so this is a great example! It appears to be just slightly better (for me at least) on the desktop version, that is better at dealing with very large/very small numbers. Eventually, I'd like this to be the case for the web version as well, but the language it's written in (Rust) seems to lack a mature library for this.

Makes sense, thank you for the quick reply! Please feel free to close this issue if it is not useful to you to have it open. :)

Hi, I encountered the same result just like this one
Given
∫(-2,2,(√(4-x^2))*(1/2+x^3*cos(x/2))dx)
We suppose to get the result pi, which is 3.1415926535897
However, I got 3.1415340713 using Kalk
Is there something that can be improved in the future?
Many thanks.

Hi, I encountered the same result just like this one
Given
∫(-2,2,(√(4-x^2))*(1/2+x^3*cos(x/2))dx)
We suppose to get the result pi, which is 3.1415926535897
However, I got 3.1415340713 using Kalk
Is there something that can be improved in the future?
Many thanks.

Ah. Well, when it comes to more "complicated" ones like this, it may be difficult to get more accuracy. It can always be tweaked though, and maybe made more flexible. I'll look into it!

∫ (1/10000000, 1, ⌈x⌉, dx)
1.0004165666   # over one? should be 0.9999999

I can't reproduce this, it says ≈ 1 for me.
I think a good solution to this problem would be to add an optional parameter for the integrate function to set the accuracy.


Requesters can withdraw excess funds

As a requester with budgets (analyst and reviewer ptokens) for my challenges, I want to be able to withdraw left over funds, so that I don't lose access to tokens
@masonchain please build out this ticket for @sebruiz 🙏

I believe you have this covered here #815


Fixed Makefile and debian skeleton control scripts

This includes builder executable paths fixes and debian skeleton control scripts like postinst, preinst etc.

Closing this PR as it is merged with previous unwanted PRs.


“reverse” setting of ZWO EAF driver not inherited

When I use 2 telescope setups with EAFs, one with “reverse” set and one with “reverse” unset, I have to correct the “reverse” setting manually in the original ZWO driver, as it is not saved in the Virtual Driver. I’m using N.I.N.A. with 2 different profiles, and it would be great if the “reverse” setting was saved in the NINA profiles as part of the Virtual Focuser’s settings.
Regards, Bernd

Hi @limburg11 , thank you for reporting this issue! The reverse setting you are referring to, is it a checkbox in the EAF driver options dialog? If so, I don't understand how that would even work, even without this virtual focuser driver in the middle. There is no "reverse" property in the IFocuserV3 ASCOM interface. The virtual focuser driver simply forwards the position that the application (NINA in your case) wants the focuser to move to. Can you share a few screenshots? Maybe I am missing something obvious. Also, are you saying that what you are doing works fine if you don't use the virtual focuser driver? Thanks!

Hi Julien, yes, the reverse setting is a checkbox in the EAF driver options dialog, see attached image:

But you are completely right, this checkbox must be set within this dialog and nowhere else. The problem was that this dialog didn't distinguish between my different EAFs because they all had the same name ("EAF(EAF)"). But this name can be edited, and now each of my motors has a unique name and the setup dialog assigns the individual setting to the correct device.
So, all is working perfectly without the need for any change in the Virtual Focuser.
Thanks, Bernd

Awesome, thank you for confirming!


Change __resource to fxmanifest

I changed the __resource to fxmanifest to add the ability for natives from latest resource manifest

LGTM, thanks for the PR.


feat: Read config and custom rules from git repository folder

Is your feature request related to a problem? Please describe.
We want to keep all custom rules and conf in one place for easy management. We have terraform configurations in different repositories every time we need to pull configs from shared repo to scan with custom rules and configs
Describe the solution you'd like
Add possibility to set git url as config file and config folder location.

Hey @armanbaghajyan  - this has been added in #1774 and #1776
the custom-check-url and config-file-url arguments expect the path to a json or yaml file.
Hopefully this will be released today


Incorrectly says someone signed

I suppose the best way to show you what's going on is to show you what I'm seeing
The pull request https://github.com/octgn/OCTGN/pull/1433
and then the CLA https://www.clahub.com/agreements/octgn/OCTGN
So that user has never signed the CLA, and it says that he did.

Production says the user signed the agreement on 5/19/2015 so I'm going to close this since this is no longer a usable test case that I can investigate. If it happens again please feel free to open a new bug with a live test case like you did with this one.


flexget --help requires a config file to exist

Might be related with #1537.
Expected behaviour:
$ flexget --help
usage: flexget [-V] [--test] [-c CONFIG] [--logfile LOGFILE]
               [--loglevel LEVEL] [--bugreport] [--profile [OUTFILE]] [--cron]
… (rest of the argparse help text) …

Actual behaviour:
$ flexget --help
2019-09-23 20:50 CRITICAL manager                       Failed to find configuration file config.yml
2019-09-23 20:50 INFO     manager                       Tried to read from: /tmp, /home/zopieux/.flexget, /home/zopieux/.config/flexget
Could not instantiate manager: No configuration file found.

I understand that I need to create a config file, but a program --help should not be stateful or reyling on the presence of a file to work. That's what most people run to start using a program.
Additional information:

FlexGet version: FlexGet-2.21.19-py2.py3-none-any.whl
Python version: 3.7
Installation method: venv, pip

@Zopieux you are absolutely right. Unfortunately our architecture is build in a way which does not make this easy.
(Manager is created by passing in a configuration file, and is responsible for loading plugins which then register arguments via events).

Could we create some sort of null configuration object to satisfy the dependency?

Indeed, that might be the easiest way around this


Unify presubmit CI and nightly CI

Prerequisites: move all jobs to the sitrep system, so that each job in the unified workflow can generate its individual status badge.
#229
#237
#238


Do not issue 'Warning prefer-interpolation' until nested interpolations are not supported

Bicep version
Bicep CLI version 0.19.5 (87ca110fc0)
Describe the bug
I prefer interpolation over concat() myself but there are situations when I need to concatenate strings inside a string interpolation.
In this case I do not wish to get the below warning:
Warning prefer-interpolation: Use string interpolation instead of the concat function. [https://aka.ms/bicep/linter/prefer-interpolation]
To Reproduce
Example bicep code:
var aksNodeResourceGroupName = '${length(resourceGroup().name) > 76 ? concat(substring(resourceGroup().name, 0, 63), sys.uniqueString(resourceGroup().id)) : resourceGroup().name}-aks'

Additional context
I'm not saying we need nested interpolation but the above warning is certainly anoying.

I feel like below is a cleaner way to do this?
var aksRG= length(resourceGroup().name) > 76 ? '${substring(resourceGroup().name, 0, 63)}${sys.uniqueString(resourceGroup().id)}' : '${resourceGroup().name}-aks'

Are you specifically against that syntax ?

You are right, it looks cleaner to me as well.
Thanks for the tip.


Basic IPv6 Support

This adds the most basic IPv6 support
This is a non-default feature. ("ipv6")
Currently it just creates a link-local address which is used. No DAD is done to detect address conflicts right now. SLAAC / Dhcpv6 is not implemented
Easiest way to test this:
In one of the example folders execute this cargo run --example static_ip --release --features "embedded-svc,wifi,ipv6"
See the link-local address logged at INFO level.
You should be able to ping that address or connect via a browser (with a URL similar to http://[fe80::36b4:72ff:fe4c:4410]:8080/)
The feature also activates Ipv6 support in embassy-net but it seems there is currently no way to set the v6 IP / route there?
Things to be done in future (not part of this PR)

SLAAC or DhcpV6 support
Find out how to use IPv6 with embassy-net

Probably SLAAC and DhcpV6 are impossible to implement since smoltcp currently doesn't support multicast for anything but IPv4
However, I was able to not only commission a Matter device but also to control it in Google Home with this ( https://github.com/bjoernQ/matter-rs-experiment/tree/ipv6 )

By the way, what about IPv6 makes the matter demo work?

The problem was that Google Home does the commissioning part fine on v4 but after that it only wants to talk v6. The spec leaves this a bit open so v4 might work with some vendors (and with the official CHIP tool it does) but for some vendors it won't work on v4. The fact that commissioning went through made me believe that everything should also work on v4 so it took me a bit too long to realize that 🤷♂


Subscriptions get shared between clients

Subscribe filters don't work properly when 2 different clients subscribing to the same object but with different filters. For example Client A runs:
const query = gql`subscription {
  books(query: "author.name = 'Ernest Cline'") {
    lastReadDatetime
  }
}`
client.subscribe({ query }).subscribe({
  next: data => {
    console.log(data)
  },
  error: err => {
    console.log(err);
  }
})

Works great with only Client A running the code; however, when Client B runs
const query = gql`subscription {
  books(query: "author.name = 'Charles Dickens'") {
    lastReadDatetime
  }
}`
client.subscribe({ query }).subscribe({
  next: data => {
    console.log(data)
  },
  error: err => {
    console.log(err);
  }
})

Both clients subscribe to both filters, switching between them for every update.

I'd like to follow up on this issue

@LucidComplex , it doesn't look like you shared any kind of error message or the exact behavior you're seeing.  I just see two code snippets

@mgeerling There is no error message. I believe I've clearly described the behavior that is occurring. The subscriptions are being shared. That is, when you subscribe to 2 different things, such as subscribing to 2 different authors, both observers receive update for both authors -- even updates not intended for them.

I tried what you said, and indeed the issue didn't occur. However, I created 2 clients by copying the directory and running both of them at the same time. I set one of the client to subscribe to Nissans, and the other to Hondas, and the issue occurred there.

Thanks. With the new instructions, I was able to reproduce it and we'll have a fix shortly.


Fix validation for dataclasses subclassing from parametrized generics

Alternative to https://github.com/pydantic/pydantic/pull/10696
Fix #10689
TODO: still needs more thorough testing, but just wanted to get this up before I forgot what was going on over the weekend.

Going to wait on this for for v2.11 where we're going to do this right and fully support nested generic dcs.

Closing for now, will use as a ref for picking this up in v2.11


Difference of results based on the computer ?

I tested my ft_printf with the iMacs at 42, 100% with both francinette and francinette --strict but on my M2 Macbook, many KOs and some Abort and Segfault.
Is this normal ? I haven't tested my GNL at school but it says KO on a lot of tests on my macbook for now. I will try my code tomorrow at school. (I hope to get better results there :D)
Thank you !

Probably because of the different architecture's of the machines (M2 vs Intel CPU).
Don't know how to fix it tho...

Hey,
Yes, on the ARM silicon weird things happen, and because I don't have access to one, I don't know how I could try to find out what is going wrong.

I presume that the safer way would be to add "-arch x86_64" to all Makefiles when compiling the codes, to force to the 42 architecture.

How do you do it in the makefile?

CFLAGS		= -Wall -Wextra -Werror -arch x86_64


refactor(start_planner): refactor debug and safety check logic

Description
This commit refactors the start_planner module in several ways:

The verbose parameter is removed from the YAML configuration file and replaced with a print_debug_info parameter under a new debug section.
A new function, initVariables(), is introduced to initialize member variables, which is called during processOnEntry() and processOnExit().
The function isBackwardDrivingComplete() is renamed to hasFinishedBackwardDriving() to better reflect its purpose. It also includes additional debug prints.
A new function, checkCollisionWithDynamicObjects(), is introduced to encapsulate the logic for checking collisions with dynamic objects.
The function isExecutionReady() is modified to use the new checkCollisionWithDynamicObjects() function.
The function resetStatus() is simplified by directly assigning an empty PullOutStatus object to status_.
The function updatePullOutStatus() now uses the new hasFinishedBackwardDriving() function.
The logging of pull out status is now controlled by the new print_debug_info parameter rather than the removed verbose parameter.

These changes improve the clarity of the code and make it easier to control debug output.

Tests performed

[ ] PASS TIERIV INTERNAL SCENARIOS

[ ] release scenarios
[ ] future scenarios

Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

      path_safety_check:
        # EgoPredictedPath
          acceleration: 1.0
          max_velocity: 1.0

this parameters is updated in processing, so is not parameters.
void updatePathProperty(
  std::shared_ptr<EgoPredictedPathParams> & ego_predicted_path_params,
  const std::pair<double, double> & pairs_terminal_velocity_and_accel)
{
  // If acceleration is close to 0, the ego predicted path will be too short, so a minimum value is
  // necessary to ensure a reasonable path length.
  // TODO(Sugahara): define them as parameter
  const double min_accel_for_ego_predicted_path = 1.0;
  const double acceleration =
    std::max(pairs_terminal_velocity_and_accel.second, min_accel_for_ego_predicted_path);

  ego_predicted_path_params->max_velocity = pairs_terminal_velocity_and_accel.first;
  ego_predicted_path_params->acceleration = acceleration;
}

@kosuke55
I believe I've addressed all the changes, could you please confirm if everything is okay?


This doesn't help with a Public Group site where can I find that one?

Site groups doesn't cover the Public Group sites?

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

ID: d167a987-f36a-d526-063a-9316470a2194
Version Independent ID: 14a80401-d388-6890-74e8-ba920a20960f
Content: Manage SharePoint Online site groups with Office 365 PowerShell
Content Source: Enterprise/powershell/manage-sharepoint-site-groups-with-powershell.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@officedocsbot assign @mypil

@anyITsolution - Thank you for submitting feedback.
I will get this issue over to the Enterprise writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Dear @anyITsolution ,
could you please clarify, what do you mean by "Public Group site"? are you talking about Office 365 Groups? And which action do you want to perform using PowerShell?
Thank you

We would like to know if there is a switch to limit who can email from the
O365 public group.
So far looks like anyone can even if they havent join or arent members of
the public site.
Thanks!
On Tue, Aug 20, 2019 at 6:58 AM MaratMussabekov<EMAIL_ADDRESS>wrote:

Dear @anyITsolution https://github.com/anyITsolution ,
could you please clarify, what do you mean by "Public Group site"? are you
talking about Office 365 Groups? And which action do you want to perform
using PowerShell?
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-Enterprise/issues/498?email_source=notifications&email_token=ALONBMKSCXOUKEUAUWXOT3DQFPE4LA5CNFSM4IMM4RJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4V4MXA#issuecomment-522962524,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALONBMMFIMSJZFLWPNYZJWTQFPE4LANCNFSM4IMM4RJA
.

@anyITsolution I am looking into this. I will post when I have more information. Thanks.

hello @anyITsolution ,
no, not everyone can send emails from public group, only delegates can.
I would recommend to check who has "send as" permission for that group
Thank you

No it doesn’t
Bit i believe i found a work around in those exchange online permissions to
delegate who can send and maintain a list of members updated for it
manually not what i was looking for but looks like its the only option or
change it to private.
On Mon, Aug 26, 2019 at 11:04 AM Joe Davies<EMAIL_ADDRESS>wrote:

@anyITsolution https://github.com/anyITsolution Does Marat's post
address your question? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-Enterprise/issues/498?email_source=notifications&email_token=ALONBMNXOVWBO44CBTDQ5KLQGPWI7A5CNFSM4IMM4RJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EUY7Y#issuecomment-524897407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALONBMMQ3FXTDSQDBPO6QBLQGPWI7ANCNFSM4IMM4RJA
.


Add loader

It takes some time to load collection, and sometimes I'm confused where my collections have gone, so I guess the loader would be helpful

Hey @ungarson - thanks for reporting this and suggesting this.
We're hoping to avoid the need to load specifically via a button with changes to indexing that will speed things up tremendously. Linked relevant development work for now via the issue.

tzkt merged in 0.7.0 with dramatic performance improvements - going to close this for now unless we continue to find problems in the future with fetching data.


container create --secrets to set environment variables does not work

Describe the bug
When trying to set a secret environment variable for a container instance by using az cli switch "--secret mysecret=verysecret", an error message appears:
"Please specify --secrets --secrets-mount-path to enable secrets volume mount."
Secret environment variable does not have anything to do with a secret mount.
If a mount name is specified the command runs, but no environment variable is set
To Reproduce
Try to set a secret environment variable:
az container create --secret mysecret=verysecret ...  (plus other required parameters...)
Expected behavior
A container being create with a secret variable.
Environment showing the variable when checked:

az container show --resource-group myRG --name securetest --query 'containers[].environmentVariables`

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Python 3.6.1
pip install
az --version
azure-cli (2.0.38)
acr (2.0.27)
acs (2.1.1)
advisor (0.5.1)
ams (0.1.1)
appservice (0.1.35)
backup (1.1.1)
batch (3.2.4)
batchai (0.3.0)
billing (0.1.8)
cdn (0.0.14)
cloud (2.0.14)
cognitiveservices (0.1.13)
command-modules-nspkg (2.0.1)
configure (2.0.16)
consumption (0.3.1)
container (0.1.24)
core (2.0.38)
cosmosdb (0.1.21)
dla (0.1.0)
dls (0.0.22)
dms (0.0.1)
eventgrid (0.1.12)
eventhubs (0.1.3)
extension (0.0.15)
feedback (2.1.2)
find (0.2.10)
interactive (0.3.23)
iot (0.1.21)
keyvault (2.0.22)
lab (0.0.22)
maps (0.2.0)
monitor (0.1.7)
network (2.1.4)
nspkg (3.0.2)
policyinsights (0.1.0)
profile (2.0.26)
rdbms (0.2.4)
redis (0.2.13)
reservations (0.2.0)
resource (2.0.31)
role (2.0.26)
servicebus (0.1.2)
servicefabric (0.0.12)
sql (2.0.27)
storage (2.0.35)
vm (2.0.34)
Additional context
Add any other context about the problem here.

@samkreter Which release will this be part of? Could you please link to the Issue that implements this feature so that I can follow it?


New Feature: Validate Input Based on OpenAPI Definition

Input validation is one of the key components for creating secure software, yet one of those things that can take quite a bit of time to do properly/maintain. With Azure Functions support for the OpenAPI/Swagger definitions; it would be great if those could be utilized to validate the incoming input without any further code being required to be written.
I imagine this being done with two toggles within the Platform Features.
1st Toggle: Enable validation against OpenAPI File: (On/Off)
2nd Toggle: Behavior when validation fails: (Log/Block)
If validation is enabled and the behavior is log, then any failures of the OpenAPI specifications will be logged to a file so they can be looked at.
If validation is enabled and the behavior is to block, then any failures of the OpenAPI specifications would return a "400 Bad Request" response.
This would mean that all you need to do to have incoming requests be validated is define an OpenAPI file, and enable the validation. You now know the schema of anything that hits your function.

Makes sense as a feature request.


Retrieve data from lambda

I need to store some API keys somewhere and reading around I found that obfuscation is a bad idea, then I came up with:
https://docs.amplify.aws/cli/function/secrets/
which I'm not entirely sure if it's the best solution, for example in my app I need the api key from a third party and then I'm attaching it to a URL, not sure how secure is the above secret url function for this ...
Can someone point out if this is the right approach for this use case and if so how can I retrieve the value from the lambda function into my ios app?
Thanks

Hi @afern247, you can execute a lambda from AWS AppSync or API Gateway. For AppSync, you can have a lambda data resolver. Amplify CLI provides a way to get these provisioned as well, such as using the @function directive. Once you have a secure API, you can use library to make requests to the API by setting the up the endpoint in amplifyconfiguration.json https://docs.amplify.aws/lib/graphqlapi/existing-resources/q/platform/ios/ . If you have any questions about the CLI doc you linked, feel free to check existing issues or open one over in the CLI repro https://github.com/aws-amplify/amplify-cli


Update upstream for Node 18 compatibility

Motivation

We're updating Yarn to the latest version so that we can use the new package cache feature. In order to do so, each package must be buildable on our machines. This PR simply updates our upstream version so that we can build this package on our M1 based MacBooks
Note: I originally tried to update to v6.31.1, but Sequelize added support for OracleDB in v6.22.0, which doesn't have any ARM binaries, and therefore refuses to build on my machine. There's most likely a way around this (as installing the upstream package works fine), but I'm unsure what that workaround is

Changes

Update upstream for Node 18 compatibility

Hard reset wanderlog branch to v6.21.6 tag
Cherry picked Tuyet's commit for index hints (no merge conflicts)
Updated eslint-plugin-jsdoc for compatibility with Node 18

Testing
None yet.

2 recommendations - let's actually figure out what's wrong with the upgrade to 6.31.1, and also do a rebase!

We'll eventually need to upgrade to 6.31.1 anyways, so I recommend that we try to resolve the issues now rather than pushing it down the road
Currently, this PR merges in commits from sequelize into the wanderlog branch. Instead, I recommend just doing a rebase of the wanderlog branch instead of doing it this way. I realize this makes it hard to submit a PR, but you can just submit an empty PR or add a Notion doc


About Real_FITS.py

Dear authors,
Thanks for your wonderful work FITS and releasing the codes!
I'm trying to use the Real_FITS.py for training on NVIDIA 4090 GPU. However, seems like the model in this file cannot be directly used by replacing the model name in the scripts. This is because this file is not included in exp_main_F.py.
Moreover, the Real_FITS.py itself is not very complete. For example, self.output_len in Line 70 is missing in the _init_ function of this class.
Could you please make the training of Real_FITS.py feasible by completing some missing details?
Thanks for your time!

Sure, I will check!
btw, can you run with the above fix you mentioned?

Hi, the code have been updated and validated! Please check!

Sure, I will check!
btw, is it working with the above fix you mentioned?

Yes, it works with the mentioned fix.
Thank you for your really quick response!!!
I have no more questions. And I really like your new paper which is a very innovative new setting.
Warm regards!

Thanks for your support and recognition!
I will close this issue if no more questions. Please feel free to reopen it.
Please feel free to reach out if you want some further discussion.


file: afterword/pythia

@brian-rose @jukent Pangeo and OpenEO have teamed up to run a tutorial for BiDs. We are spolighting Pangeo resources, I'm wondered if there's an updated version of Project Pythia. We have an old one used for 2022 FOSS4G, see here.
Thank you!

Thanks @acocac ! That resource looks great, except the slides say our Cookbooks are "Coming Soon." There are now several Cookbooks available. I can get you some updated slides - or just link to our project here - https://projectpythia.org/
What would be the most helpful for you?

@jukent thanks for validating the content of Project Pythia. We successfully delivered the training with OpenEO last week. We can update the resources for future visitors if relevant. I think if you have an up-to-date slides would be very beneficial for coming trainings we'll get involved in 2024.
We'll make sure to validate any future Project Pythia content with a longer period of notice.


Replace if with guard clause

Regression tests are here: https://github.com/elixir-lang/ecto/blob/v2.0.0-rc.5/test/ecto/type_test.exs#L100:L102

What's the regression, shouldn't those tests return :error?

@ericmj I guess my comment was confusing :) there're no regressions; and if they were, they would have been caught by the tests that I mentioned above, it's a pure refactoring. In fact, cast is already with the similar structure: https://github.com/elixir-lang/ecto/blob/v2.0.0-rc.5/lib/ecto/type.ex#L522

Okay, that makes sense.


Clone Hero Update

I'm just informing that Clone Hero just got a huge update yesterday to v25.1 and i'd be interested to see if Aurora support can be updated and re implemented as it no longer functions
Thank you
Aurora Version:
V0.7.0rc2
Previously an Issue?
No

Can confirm it doesn't work.


plutus playground

I don't suppose we got anywhere with getting rid of the big string literal contract? From a purely selfish point of view - as soon as this is merged then I am on the hook for not breaking it instead of you, and I am not keen on having to edit that constantly :p

Sorry @michaelpj not a priority at the moment

Okay, I'm going to merge this soonish barring any objections.

gulp


K8SPS-93: Don't run multiple backups on the same pod

https://jira.percona.com/browse/K8SPS-93
During backup, operator searches replica pods that are not running backup until it finds it. Otherwise, it sleeps for 10 seconds and searches again. If there are no free pods after the second search, multiply sleeping time by 2 (up to 10 minutes)

Test name
Status

auto-config
passed

init-deploy
passed

demand-backup
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

config
passed

scaling
passed

sidecars
passed

limits
passed

users
passed

We run 12 out of 12

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/e6dff6ca2c71b5393bd127f372b535ab5e25d9c8
image: perconalab/percona-server-mysql-operator:PR-170-e6dff6c

Test name
Status

auto-config
passed

demand-backup
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

config
passed

service-per-pod
passed

scaling
passed

sidecars
passed

limits
passed

users
passed

We run 12 out of 12

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/67be2f3478fe8b6f91dc8e9d11af77f89682375d
image: perconalab/percona-server-mysql-operator:PR-170-67be2f3

Test name
Status

auto-config
passed

init-deploy
passed

demand-backup
failed

gr-init-deploy
passed

monitoring
passed

config
passed

scaling
passed

semi-sync
passed

users
passed

service-per-pod
passed

sidecars
passed

limits
passed

We run 12 out of 12

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/d49a543e823dd447f88e1846e1f70851cd3c1e69
image: perconalab/percona-server-mysql-operator:PR-170-d49a543

Test name
Status

auto-config
passed

demand-backup
failed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

config
passed

service-per-pod
passed

scaling
passed

sidecars
passed

limits
passed

users
passed

We run 12 out of 12

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/4f7eed10fa6fe401d00ff7928e9decf9c795188b
image: perconalab/percona-server-mysql-operator:PR-170-4f7eed1

Test name
Status

auto-config
passed

config
passed

demand-backup
failed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

sidecars
passed

limits
passed

scaling
passed

users
passed

We run 12 out of 12

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/4f7eed10fa6fe401d00ff7928e9decf9c795188b
image: perconalab/percona-server-mysql-operator:PR-170-4f7eed1

@pooknull please fix shellcheck warnings

@inelpandzic what do you see in the logs? from what I understand by reading the code excess backups should sleep and retry until pod becomes available. am I right @pooknull ?

@inelpandzic what do you see in the logs? from what I understand by reading the code excess backups should sleep and retry until pod becomes available. am I right @pooknull ?

Yes, yes, I can see that in the code as well, but I expected not to see them like in the running state. But maybe my expectation was wrong.

Test name
Status

We run 0 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/02e37cca62a20e677977a2022e629966a2f72b84
image: perconalab/percona-server-mysql-operator:PR-170-02e37cc

Test name
Status

demand-backup
passed

auto-config
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

config
passed

sidecars
passed

limits
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 13 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/ca9ea8c0b7bfa6b31a2c53aaa7d06c81585edc23
image: perconalab/percona-server-mysql-operator:PR-170-ca9ea8c

Test name
Status

demand-backup
passed

auto-config
passed

init-deploy
passed

config
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

sidecars
passed

limits
passed

scaling
passed

tls-cert-manager
passed

users
passed

We run 13 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/9ce2831bdfaa2604c5aa9cc5eb8b44856fe75792
image: perconalab/percona-server-mysql-operator:PR-170-9ce2831

Test name
Status

demand-backup
passed

auto-config
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

config
passed

sidecars
passed

limits
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 13 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/03099cff2436d7ec91585207a4480729a2f184df
image: perconalab/percona-server-mysql-operator:PR-170-03099cf

Test name
Status

init-deploy
passed

auto-config
passed

demand-backup
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

scaling
passed

service-per-pod
passed

users
passed

sidecars
passed

limits
passed

tls-cert-manager
passed

config
passed

We run 13 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/bef3ca3146161be4afd6da711a43f9386cc277ad
image: perconalab/percona-server-mysql-operator:PR-170-bef3ca3

Test name
Status

demand-backup
passed

auto-config
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

sidecars
passed

limits
passed

scaling
passed

tls-cert-manager
passed

users
passed

config
passed

We run 13 out of 13

commit: https://github.com/percona/percona-server-mysql-operator/pull/170/commits/80696d6e55bb8e31e1483fad23726403929868a6
image: perconalab/percona-server-mysql-operator:PR-170-80696d6


Trouble Connecting Turtlebot4 to Institutional Wi-Fi Network.

I'm working with a Turtlebot4 running Galactic Distro and using a Create3 base with firmware G.5.3. My goal is to connect the Turtlebot4 to my institutional Wi-Fi network named "RedRover". I'm attempting this connection using Discovery Server Mode, so I don't have to directly connect the Create3 to RedRover.
The problem arises when I execute the command sudo wifi.sh -s 'RedRover' -p '' -r 'US' && sudo reboot. This command successfully changes my IP address to a 10.X.X.X subnet. However, despite this, I'm unable to ping or access the Turtlebot4 when connected to RedRover. Interestingly, it remains accessible when connected to my personal Wi-Fi network (TP-Link_DXX_5G). The robot's RPI was connected to this previously.
Additional steps I've taken include providing the Raspberry Pi's MAC address to my institution to allow network access. Despite this, the connectivity issue persists on the RedRover network.
I'm seeking advice on how to resolve this connectivity issue. Are there specific settings or considerations for connecting a Turtlebot4 to an institutional network like RedRover? Any insights or suggestions would be greatly appreciated.

Hello Tauhid,
Thank you for opening up this issue. I have a question regarding your personal network TP-Link_DXX_5G, is the network password protected or does it also use no password? If connecting to RedRover, try running the command without the -p flag: sudo wifi.sh -s 'RedRover' -p '' -r 'US' && sudo reboot and see if the TB4 is able to connect to the network in this manner.
Looking forward to hearing from you soon.

@smatar22, TP-Link_DXX_5G has its own password. My robot was previously connected to TP-Link_DXX_5G. But I tried to switch my TB4 to 'RedRover'.
I have already tried this: sudo wifi.sh -s 'RedRover' -p '' -r 'US' && sudo reboot. I saw the IP address of TB4 changes to something from 192.168.X.X to something 10.X.X.X. But I cannot ping the TB4 from RedRover, I can ping the robot when I'm connected to TP-Link_DXX_5G this router. Although my robot is showing inside it is connected to something name RedRover (by ssh to TB4).

@smatar22 , No, after connecting the TB4 to Redrover, is the address: <IP_ADDRESS> and one of the laptop's ip address is <IP_ADDRESS>. I can ssh with that laptop. Another laptop's IP address is different doesn't match last two numbers. I cannot ping TB4 with that laptop. Thanks for the information. I'll talk to the IT team. We are planning to put 6-8 TB4s under our institutional wifi network. I hope it will work.

Hello Tauhid,
From the description it appears that due to the laptop being on a different subnet, it is unable to communicate with the TB4 team. If possible, try changing the adapter settings for the laptop with the different IP address to something in line with the format 10.52.16.X and see if it is now able to ssh and ping the Turtlebot.
In terms of the command, if the original command works, then there is no need to try with the new command.
Looking forward to hearing from you soon.

@smatar22 , Thank you so much. It worked after talking to our institutional IT folks. I'll work on other TB4s. Thank you for the constant support. I'm closing this for now. If I face any problem regarding other TB4s. I'll open the issue again.


[CVE-2022-23852] of underlying libexpat

The underlying version of libexpat packaged in node-expat is most likely vulnerable to the vulnerability documented for libexpat < 2.4.4

https://nvd.nist.gov/vuln/detail/CVE-2022-23852
https://github.com/libexpat/libexpat/pull/550

Using an OS with package management, I've always wondered why we vendored libexpat.

Using an OS with package management, I've always wondered why we vendored libexpat.

If only all OSes brought libs like that ... but wait - we might even get fewer security fixes for older devices where nobody updates the OS :D

Please note that Expat 2.4.5 with more security fixes has been released by now.

Are there any plans to upgrade the bundled libexpat version to latest?


Fixing disappearance of requirements after adapter init

Description of the issue
In the case in which tags are missing, after initing the adapter, the model_tags parameter  is defaulted to None.
When running gov.get_evidence_requirements, the chain of calls is:

tags = self.get_model_info()["tags"]
self._get_model_info

Here since "tags" is in model (value = None), model.get("tags", {}) simply returns the None rather then defaulting to {}.
So when check_subset is run in get_evidence_requirements, no matches are found.
Solutions
Either of these fixes it:

Enforcing default behavior for None model_info (this is the change I have made)
Enforcing empty dictionary as default at Adapter init:

def __init__(
        self,
        governance: Governance,
        model_name: str,
        model_tags: Optional[dict] ={}, # Changed here!
        model_version: Optional[str] = None,
        assessment_dataset_name: str = None,
   ):

@esherman-credo let me know which one you think it's best.

I think you should fix the Adapter init. model_tags should be a dictionary, however you shouldn't make a dictionary a default argument. You should add a line that is like:
model_tags = model_tags | {}


⚠ Bofrost.de has degraded performance

In 0669a6d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: Bofrost.de performance has improved in 3443916 after 8 minutes.


Fix curl commands escape double quotes

Why:
Closes #21146

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Thanks for the contribution @alexandrosyiangou! I'll get this triaged for review. ✨

Thank you for contributing, @alexandrosyiangou! ✨
Since this is a duplicate of https://github.com/github/docs/pull/21133, I am going to close this one out.
Let us know if/when you find any other issues or improvements you'd like to make to our documentation. We'd love to loop your contributions in!
If you're interested in picking up a project as part of Hacktoberfest, check out the pumpkin-spice label 🎃


Expand component metadata templating docs

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Read the contribution guide
[x] Commands include options for Linux, MacOS, and Windows within codetabs
[x] New file and folder names are globally unique
[x] Page references use shortcodes instead of markdown or URL links
[x] Images use HTML style and have alternative text
[x] Places where multiple code/command options are given have codetabs

Description

Describe templating possibilities for metadata values. Before, only {uuid} and {podName} were described. Now, {namespace} and {appID} are noted as additional possibilities.
Link to metadata docs in kafka components, and provide an example for consumerGroups.
Issue reference
Linked to https://github.com/dapr/dapr/pull/5752

Recreate of https://github.com/dapr/docs/pull/3062. Messed up the sign-offs there.
@msfussel @yaron2 Can you add this to v1.10 milestone again, and the old PR be closed? My apologies.

@VerstraeteBert could you point this PR to the v1.10 branch?

Good to go @hhunter-ms

@VerstraeteBert could you pull in the latest from v1.10? I fixed that broken link


Boss suggestion 6

$BOSS
Arena
Arena has several $smallareas, possibly marked with circles with $smallobjects in their middles.
Boss
$BOSS is a big monster in the middle of the arena. $BOSS attacks in melee and has $targetedspell which is cast on the furthest hero within $range. $BOSS uses both modes of attack with no restraint. $BOSS walks rather slowly.
Phase 1 (100-70% HP)
$BOSS uses the following abilities:
$ability1: $BOSS throws $bigprojectile in an upward arc, so it will land in an indicated $bigarea. It deals physical damage to units in $bigarea and spawn up to two $minions in $bigarea. Each unit hit will reduce the number of $minions spawned by one.
$minions have enough HP, attack speed and damage to ultimately deal more damage before being killed than the projectile does on impact. $minions also have a large collision box.
$ability1 has a $long interval between casts.
Phase 2 (70-40% HP)
$ability1 $bigprojectile will now spawn up to three $minions.
$BOSS gains the following ability:
$ability2: $BOSS teleports to the center of the arena and charges a spell for several seconds, gaining additional damage reduction. $BOSS does not attack, move or cast $targetedspell when charging, but it can't be interrupted. Every unit that's not $minion or $BOSS becomes marked with $red or $blue. (Stand-in visual effect: Morph.) Two random $smallareas begin emitting $verticalbeams, one $blue and one $red.
Upon finishing channeling, $BOSS causes $hugeexplosion which hits everything in the arena and deals $superhigh magic damage to each colour-marked unit not standing in the same-coloured $verticalbeam. $verticalbeams then disappear.
$ability2 is cast in the middle of the interval between casts of $ability1, so the two alternate with no reduction of frequency of $ability1.
Phase 3 (40-0% HP)
$ability1 $bigprojectile will now spawn up to five $minions.
$BOSS gains the following ability:
$ability3: $BOSS launches $bouncyprojectile at a random hero. $bouncyprojectile deals $moderate magic damage and applies $debuff after damaging. $debuff increases damage of $bouncyprojectile $several times and makes it pure damage. $bouncyprojectile does not travel very fast. It can bounce to $minions if no other units are in $bounceradius, dealing no damage. It has $kindahigh limit on bounces. (12?)
$ability3 is cast 1 second after $bigprojectile lands or $hugeexplosion happens.
Strategy
Blocking $minion spawns by intercepting $bigprojectile is optimal. Not getting hit by $hugeexplosion by standing in the right $verticalbeam is optimal. In both cases there is enough time to reasonably run to the right location assuming roughly centralized positioning. When more $minions spawn from phase 2 onward, killing them when waiting for $hugeexplosion is preferable over attacking $BOSS due to damage reduction during charging.
Both of these abilities require units to bunch up in a location. Due to $ability3, splitting up afterwards is optimal.
$BOSS is tanked by two players, one standing further than others to take $targetedspell and one tanking the melee attacks. It is possible to kite $BOSS instead of tanking melee hits, but it makes positioning of the $targetedspell tank difficult and might make reacting to $abilities difficult.

Thank you for the post. I have a question: should we really strive to have one of the two be optimal? It feels to me like having them have each their benefits and disadvantages would be best - it creates more strategic possibilities.
As it regards the minions' damage, given that they help bounce the spell, and mean wasting damage to get rid of, I am unsure they need to be more damaging the projectile, even if we intend tanking the projectile to be optimal.


Stop using deprecated Omnitruck URL

Fixes issue #48 by using the Omnitruck metadata-server endpoint rather than the deprecated download-server endpoint, as suggested in #52.

Hello,
More information is coming - but I'm closing this for the same reason I stated here: https://github.com/opscode-cookbooks/chef-server/issues/52#issuecomment-75202308


Force on some TypeScript options at the loader

We force some on in tsconfig.json but the user could always overwrite them after boot. We need to prevent this to stop obscure bugs.

This is corrupt and has taken my privacy away


Some runes use more than 8bytes and is rendered with a space after

Try typing æøå into the editor.

Weird, this should be accounted for. I remember specifically implementing support for some weird unicode characters and chinese characters. We will have to look into it! Thanks :smile:

Try inserting them into a line with text and press left and right arrow.

Just looked into this and i guess i don't really have that commit :confused: I think for the cursor placement something like this should work. In util.go:
 func GetCursorVisualX(x int, line string) int {
-	r := []rune(line)
-	if x > len(r) {
-		x = len(r) - 1
+	if x > len(line) {
+		x = len(line) - 1
 	}

-	return ByteWidth(string(r[:x]), tabSize)
+	return ByteWidth(string(line[:x]), tabSize)
 }

As for full unicode support (fullwidth characters and such) view.go needs a bigger rewrite. tcell has a nice example of how unicode could be handled if anyone wants to give it as stab. Here's the link https://github.com/gdamore/tcell/blob/master/_demos/unicode.go
Right now we naively expect that 1 character = 1 rune but some runes are combination runes. See signature of tcell's SetContent, we have to use the combc argument.

Thanks a lot, this solves my issue at least, and probably for most other western characters like ß and ö.

You wanna do it @jantb? Othetwisw i'll do it later in the week i think :smile:

sure, np


Illegal file name in distributed version of Complex library

Reported by stefanv on 11 Jul 2016 18:15 UTC
The distributed version of the Complex library comes with a file, Resources/help/Complex.'<>'.html, which is illegal in Windows. As such, MSL 3.2.2 can't be properly installed under Windows.

Migrated-From: https://trac.modelica.org/Modelica/ticket/2025

Comment by beutlich on 12 Jul 2016 12:43 UTC
Duplicate of #2024.

Comment by stefanv on 12 Jul 2016 13:35 UTC
Sorry, I never saw 2024, I guess because it went to map-lib only.

Modified by dietmarw on 13 Jul 2016 14:51 UTC

Modified by beutlich on 14 Jul 2016 12:15 UTC


firebase_remote_config: internal remote config fetch error

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Remote Config
Which platforms are affected?
iOS
Description
Issue Summary:
We are encountering a FirebaseException when calling the await remoteConfig.fetchAndActivate(); method within our Flutter app using the firebase_remote_config plugin (version 4.3.8). The exception details are as follows:
Code Snippet:
try {
  await remoteConfig.fetchAndActivate();
} on FirebaseException catch (e) {
    debugPrint('FirebaseException Caught:');
    debugPrint('Error Code: ${e.code}');
    debugPrint('Message: ${e.message}');
    debugPrint('Plugin: ${e.plugin}');
    debugPrint('Full Exception: $e');
    debugPrint('StackTrace: ${e.stackTrace}');
} catch (e) {
    debugPrint("FAIL" + e.toString());
}

Error Logs:
flutter: FirebaseException Caught:
flutter: Error Code: internal
flutter: Message: cancelled
flutter: Plugin: firebase_remote_config
flutter: Full Exception: [firebase_remote_config/internal] cancelled
flutter: StackTrace: null

For Reference (Screenshot when debugging):

Issue Details
Upon investigating the issue, I noticed that a similar problem was previously reported and resolved in Issue #6196. In that case, the error code returned was 999, and a fix was implemented here, which retries the fetchAndActivate call if the error code is 999.
This fix is also present in the version (4.3.8) of the firebase_remote_config plugin that we are using. However, the issue we are encountering now returns a different error code (internal instead of 999), which causes the retry logic to be bypassed, and thus the fix does not work in our case.
Specifically, the retry logic checks if the error code is 999:
if (error.code == 999 && _fetchAndActivateRetry == false) {
  _fetchAndActivateRetry = true;
  [self fetchAndActivate:arguments withMethodCallResult:result];
} else {
  result.error(nil, nil, nil, error);
}

Since our error code is internal, this condition fails, and the retry logic is not triggered.
Request for Fix
Could you please look into this issue and consider updating the logic to account for error codes like internal or other potential error codes? Currently, the fix only handles the specific case for error code 999, but our issue seems to fall under a broader category of errors.
It would be helpful if the retry logic could be extended to handle internal or similar errors to prevent these fetch requests from being cancelled and allow the operation to complete successfully.
Flutter Doctor for reference:
[✓] Flutter (Channel stable, 3.7.12, on macOS 15.0.1 24A348 darwin-arm64, locale en-PH)
    • Flutter version 3.7.12 on channel stable at /Users/haritha/fvm/versions/3.7.12
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (1 year, 6 months ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/haritha/Library/Android/sdk
    • Platform android-34, build-tools 33.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] VS Code (version 1.94.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • iPhone (mobile) • 00008130-######### • ios          • iOS 18.0.1 22A3370
    • macOS (desktop)         • macos                     • darwin-arm64 • macOS 15.0.1 ###### darwin-arm64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Reproducing the issue

Prerequisites:

Flutter version: 3.24.3
firebase_remote_config plugin version: 4.3.8
Firebase project is properly configured in the Flutter app (ensure the necessary Firebase setup is complete).

Steps to Reproduce:

Set up a Flutter app with the firebase_remote_config plugin.
Initialize Firebase and call await remoteConfig.fetchAndActivate(); method in your app.
Wrap the method call inside a try-catch block that captures FirebaseException (as shown in the code snippet above).
Run the app and observe the logs or behavior when the fetchAndActivate method is invoked.

Expected Outcome:

The fetchAndActivate method should successfully fetch the remote configuration and activate it without any errors.

Actual Outcome:

The method throws a FirebaseException with the following details:

Error Code: internal
Message: cancelled
Plugin: firebase_remote_config

No retry logic is triggered due to the error code being internal rather than 999.

Firebase Core version
2.24.2
Flutter Version
3.24.3
Relevant Log Output
flutter: FirebaseException Caught:
    flutter: Error Code: internal
    flutter: Message: cancelled
    flutter: Plugin: firebase_remote_config
    flutter: Full Exception: [firebase_remote_config/internal] cancelled
    flutter: StackTrace: null

Flutter dependencies

Expand Flutter dependencies snippet

  firebase_core: ^2.14.0
  firebase_remote_config: ^4.3.8

Additional context and comments
No response

Hi @HarithaMadhushanka , thanks for the report. I'm unable to reproduce this issue on the latest version of firebase_remote_config: 5.1.3. Can you update your version and try again?

I am using the firebase_remote_config version 4.3.8 in my mobile app. Unfortunately, I cannot upgrade my Flutter SDK version beyond 3.0.0 due to other plugins in my application that depend on a Flutter SDK version between ">=2.16.1 <3.0.0" (as specified in the pubspec.yaml).
However, I will try upgrading my firebase_remote_config version to 5.0.2 and see if that resolves the issue.
Upon reviewing the source code of the latest version (5.1.3), I noticed that the fetchAndActivate method has not changed compared to the version 4.3.8 code. However, I did notice some other differences in the FLTFirebaseRemoteConfigPlugin.m file.
I will add my update in this thread if version 5.0.2 resolves this issue. Thanks!


[C++] Compute: Why here arrow::compute has MetaFunction

Describe the usage question you have. Please include as many useful details as  possible.
In arrow compute, MetaFunction means some "sepcial function", which "dispatch implementation to other impl. And the introduced pr is here: https://github.com/apache/arrow/commit/199d089e6343df1a1aa95f75b9e99e05a2702257
However, some function like "CAST" also has correspond kernel, and it just works like a normal function. Besides, why should it has a MetaFunction rather rathan a function with some "Match Any" Kernels?
Component(s)
C++

In arrow compute, MetaFunction means some "sepcial function", which "dispatch implementation to other impl. And the introduced pr is here: 199d089

As I understand it, a meta function gives you a structural way to bypass all the routines to actually invoke a regular function: executor creation, dispatching (kernel lookup), initialization, etc. So it's suitable for things like checking input "shape" and dispatch to concrete overloads (CC/CA/AC/etc.), or any other thing that you feel best to implement a function without using kernels.

However, some function like "CAST" also has correspond kernel, and it just works like a normal function.

IIUC, cast, as a meta function, has no kernel. What you saw might be subclasses of
https://github.com/apache/arrow/blob/383ffe06075c5b66e2c7a37bfaf91a84aeb453d2/cpp/src/arrow/compute/cast_internal.h#L35
What is a arguably strange though, is that these concrete cast_xxx functions are not registered in the global function registry. Instead, cast meta function manages them using an internal registry-like structure:
https://github.com/apache/arrow/blob/383ffe06075c5b66e2c7a37bfaf91a84aeb453d2/cpp/src/arrow/compute/cast.cc#L49

Besides, why should it has a MetaFunction rather rathan a function with some "Match Any" Kernels?

Well, I would say that probably is technically doable. I think people just chose one.

I understand MetaFunction is "tiny function without kernel and not evolved in scalar eval", however, "cast" seems to be a special case, which also has kernel as internal implementation and would be bound in scalar eval. I don't know why it's design like that


Max zoom out to world border

Hi.
I'm using your pack and it works fine.
Can you edit your pack set to a max zoom out to the world border?
It will better work for all display.
I want set the map to a max size as self as world borders height.
eg.
The world border is XY blocks.
So, if I load an dynmap, it should better to the map in max-with and then the user can fade in (zoom in).

Maybe with a div or js to handle automate the max zoom out.
The green frame is the max zoom out and the orange arrows are the fade in (zoom in).
The picture above is set to extrazoomout: 5
If I set extrazoomout: 4 it looks so. picture below.

But I didn't find a correct form factor to set between.
Concretely, I want set the max zoom out to world border's bottom and top line.
**max-height:100% or any js format will fixing all displays **

+1

Hi @JLyne
Have you got read this issue?


prepatch versioning does not work

I created a new prepatch version by using
npm run release prepatch.
A version 0.0.7-0 was created [OK]
Afterwards I did some changes and ran the command
npm run release prepatch
again. A version 0.0.8-0 was created [NOK], I expected a version 0.0.7-1
{
  _: [ 'prepatch' ],
  dry: true,
  all: true,
  '$0'<EMAIL_ADDRESS>}
Your branch has uncommitted changes that will be included in the release commit!
Consider adding them to a separate commit first.

bumping version 0.0.7-0 to prepatch version 0.0.8-0

dry run: not updating package files
dry run: I would execute this:
  npm install
  git add -A -- ":(exclude).commitmessage"
  git commit -F ".commitmessage"
  git tag v0.0.8-0
  git push
  git push --tags

done!

That is correct. If you look at the documentation, it clearly states:

Like patch, but to provide test versions before the final release. WARNING: Using this multiple times increases the patch version each time.

If you want to increase the suffix, you need to use prerelease, see https://github.com/AlCalzone/release-script#command-line


spring boot runtime/version fields not added

Issue
Component.yaml is populated correctly using ap4k 0.3.2 but the following spring boot fields are missing fields : runtime: spring-boot and version: 2.1.2.RELEASE.
I'm pretty sure that we added them within the ap4k-spring-boot dependency ...
What is generated
apiVersion: "v1"
kind: "List"
items:
- apiVersion: "component.k8s.io/v1alpha1"
 kind: "Component"
 metadata:
  name: "cool-demo"
 spec:
  deploymentMode: "innerloop"
  exposeService: false

Should be
apiVersion: "v1"
kind: "List"
items:
- apiVersion: "component.k8s.io/v1alpha1"
 kind: "Component"
 metadata:
  name: "cool-demo"
 spec:
  runtime: spring-boot
  version: 2.1.2.RELEASE
  deploymentMode: "innerloop"
  exposeService: false

Do you plan to release 0.3.3 to be able to test this fix or do we have to build master to test it ? @iocanel


Bluetooth: Host-based Privacy: RPA rotation changes

This PR attempts to improve Host-based Privacy in the Bluetooth subsystem.
Rationale:

Synchronizing RPA rotations between multiple advertising sets (prevention from identity bridging).
Synchronization of advertising payload and RPA rotation for each advertising set (advertising payloads containing random value compromise privacy if the random part does not change in sync with the RPA).
Possibility to delay the rotation on each RPA timeout (seed used to generate the next value of rotating payload cannot be updated).
Redefining RPA rotation periods in runtime (possibility to randomize RPA timeout improves privacy).

See the code example below for a demonstration of how to use the new API:
#define RPA_TIMEOUT_AVERAGE (15 * SEC_PER_MIN)
#define RPA_TIMEOUT_OFFSET_MAX (1 * SEC_PER_MIN)

static uint16_t app_rpa_timeout_randomize(void)
{
   int err;
   int8_t rand;
   uint16_t rpa_timeout = RPA_TIMEOUT_AVERAGE;

   err = sys_csrand_get(&rand, sizeof(rand));
   if (!err) {
   	int16_t rand_timeout_diff;

   	rand_timeout_diff = (((int)(RPA_TIMEOUT_OFFSET_MAX * MSEC_PER_SEC)) / INT8_MAX);
   	rand_timeout_diff *= rand;
   	rand_timeout_diff /= ((int) MSEC_PER_SEC);

   	rpa_timeout += rand_timeout_diff;
   } else {
   	LOG_WRN("Cannot get random RPA timeout (err: %d). Used fixed value", err);
   }

   return rpa_timeout;
}

static bool app_rpa_timed_out(struct bt_le_ext_adv *adv)
{
   int err;
   uint16_t next_rpa_timeout;

   LOG_INF("RPA timed out");

   /* Randomize the next RPA timeout. */
   next_rpa_timeout = app_rpa_timeout_randomize();

   err = bt_le_set_rpa_timeout(next_rpa_timeout);
   if (err) {
   	LOG_ERR("bt_le_set_rpa_timeout failed: %d", err);
   } else {
   	LOG_INF("Setting RPA timeout to %d [s]", next_rpa_timeout);
   }

   /* Update the advertising payload in sync with RPA timeout. */
   err = bt_le_ext_adv_set_data(adv, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
   if (err) {
   	LOG_ERR("Cannot set advertising data (err: %d)", err);
   	return false;
   }

   return true;
}

@Thalley, I addressed most of your comments

Rebased to address non-related CI failures. I have only addressed the https://github.com/zephyrproject-rtos/zephyr/pull/47260#discussion_r915234873 during this rebase

Rebased to address non-related CI failures. I have only addressed the #47260 (comment) during this rebase

Looks like the documentation build was cancelled - Reran the CI action :)

Rebased to address non-related CI failures. I have only addressed the #47260 (comment) during this rebase

Looks like the documentation build was cancelled - Reran the CI action :)

Thanks. The CI is green now :)

@jilu-ot please review

I pushed another small update that addresses the change discussed in the https://github.com/zephyrproject-rtos/zephyr/pull/47260#discussion_r916768318 review discussion (callback name change to rpa_expired). Apart from that, I rebased my commits on top of the main Zephyr branch.
I believe that we have reached a consensus on all ongoing review discussions.
I will start my vacation next week and will be away for the next two weeks (10-24.07). If any review comments appear during my absence, I will be happy to resolve them once I am back.
We still might be able to finalize this PR by the end of this week, but I don't want to rush it.


Update .clang-format

I agree with the access modifier indentation change. For namespaces, where are those used in Charm++? I'm always used to seeing them unindented in Charm++ adjacent projects, but I'm not familiar with them too much in Charm++ itself. Also, does clang format touch .ci files at all?
You also mentioned in core that brace spacing was possibly inconsistent, but didn't change it here.

I agree with the access modifier indentation change. For namespaces, where are those used in Charm++? I'm always used to seeing them unindented in Charm++ adjacent projects, but I'm not familiar with them too much in Charm++ itself. Also, does clang format touch .ci files at all?
You also mentioned in core that brace spacing was possibly inconsistent, but didn't change it here.

They're used sporadically in Charm++; changing them to indented is mostly personal preference, but I think that's contrary to the prevailing style in Charm++ and most other places, so I'll remove that from the patch for now.
I didn't change the brace style because we've already explicitly changed it from Attach to Allman here: https://charm.cs.illinois.edu/gerrit/c/charm/+/4309. I'm in favor of Allman, but most of the code in the codebase I've seen is closer to Attach.

The access modifier change essentially changes from this:
class Example
{
 public:
  void example() {}
}

to this:
class Example
{
public:
  void example() {}
}

(note that public is preceded by a space in the first example and is not in the second)

I agree with the access modifier indentation change. For namespaces, where are those used in Charm++? I'm always used to seeing them unindented in Charm++ adjacent projects, but I'm not familiar with them too much in Charm++ itself. Also, does clang format touch .ci files at all?
You also mentioned in core that brace spacing was possibly inconsistent, but didn't change it here.

They're used sporadically in Charm++; changing them to indented is mostly personal preference, but I think that's contrary to the prevailing style in Charm++ and most other places, so I'll remove that from the patch for now.
I didn't change the brace style because we've already explicitly changed it from Attach to Allman here: https://charm.cs.illinois.edu/gerrit/c/charm/+/4309. I'm in favor of Allman, but most of the code in the codebase I've seen is closer to Attach.

Ah yeah, I'm much more partial to Attach, and I thought that's what we used tbh. Most of the actually formatted code I run into uses Attach, so I've been matching that, and even updating some unformatted code to that here and there in PRs that touched that code.


refactor: routing fixes and cleanup

Try out this version of the Hiro Wallet - download extension builds.

This PR fixes a couple of minor bugs reported with testing the routing refactor changes.
*I also moved the new BuyButton into its own file instead of co-locating it with the SendButton.
cc/ @kyranjamie @beguene

Found an issue testing this tonight with the Unlock route b/w the two view modes, so will continue working on it tomorrow.

This PR will conflict with this one https://github.com/hirosystems/stacks-wallet-web/pull/2054

I wonder if we could come up with a consistent pattern for how we handle situations such as the natigate useEffects in both onboarding.tsx and save-secret-key.tsx. These are conditions for whether or not the a given users is allowed to see the view. Could this instead be its own route guard?

I was thinking about this a bit more swimming this morning (haha). The route guards really doesn't work with the ext popup bc of how the VaultLoader sets the state of the wallet. I am wondering if I should revert this PR back to just fixing the send form route and use the conditional index, but then try to address the conditional routing logic in the Layout/Container route which will wrap everything? It might work better than using the AccountGate that currently only works with the full page view. I do think there is too much being handled in components useEffect which could later be difficult for new devs to understand.

@kyranjamie it seems to work pretty well to put this in the app-routes:
if (
    pathname !== RouteUrls.RequestDiagnostics &&
    pathname !== RouteUrls.Onboarding &&
    pathname !== RouteUrls.Home &&
    !wallet
  )
    return <></>;

Do you have a problem with this instead of using useEffect?

No, I reckon this is better than a useEffect 👍🏼
Ideally we'd show some sort of loading spinner, rather than just blank screen.
Is there a cleaner way to know if the background script has updated the state in the react app? if (!wallet.isReady) return ... would be better if it's easy to infer this.

Is there a cleaner way to know if the background script has updated the state in the react app? if (!wallet.isReady) return ... would be better if it's easy to infer this.

Yep, I'll change to loading spinner (was just testing). I agree on that. I'll look at adding this. Maybe when we look at refactoring the Vault this can be looked at again and simplified further.

Yep, for sure. I'm looking into the vault stuff atm for Ledger support (persisting public key)

This isn't perfect, but going to merge it into dev so I can continue implementing the Layout/Container route that actually might solve some of the view sync issues a bit better rather than using useEffect. Using the loading spinner and returning early did not end up working consistently.


Support for Crystal 0.31.0

For run spec with Crystal 0.31.0 will fail on CentOS 6 or Fedora 22.

We may fix for SEGV in Spec.build


Concerto 1.0 generates identifiers even when they should be user-provided

Description
I think this should be a bug? I thought user-declared identifiers (with identified by XXX) were now meant to be provided by the user -- and distinguished from system generated identifiers (with identified).
But Concerto 1.0.0-alpha.2 generates user-declared identifiers. For instance:
Model
namespace org.test

concept C identified by id {
	o String name
	o String id
}

Data
{
    "$class": "org.test.C",
    "name": "John"
}

Validates as:
zsh-5.8$ concerto validate --ctoFiles test6.cto --sample test6.json
10:49:53 AM - INFO:
{
  "$class": "org.test.C",
  "name": "John",
  "id": "e55698df-2218-40ee-bcf9-13e6bfb38958"
}

I'm unclear if that is the intended behaviour though.

That's a bug imo - id is declared as an identifier and identifiers are never optional.

That's a bug imo - id is declared as an identifier and identifiers are never optional.

That makes sense to me too!
I think the issue here is that id is automatically generated (so it behaves is if it had a default generated value, even when not optional).

Addressed in #246:
zsh-5.8$ more test.cto
namespace org.test

concept C identified by id {
        o String name
        o String id
}
zsh-5.8$ more test.json
{
    "$class": "org.test.C",
    "name": "John"
}
zsh-5.8$ ./index.js validate --model test.cto --input test.json
2:16:00 PM - INFO: Input is invalid
2:16:00 PM - ERROR: Invalid or missing identifier for Type C in namespace org.test
zsh-5.8$ ./index.js validate --model test.cto --input test.json --functional
2:16:01 PM - INFO: Input is invalid
2:16:01 PM - ERROR: Instance org.test.C#undefined has an empty identifier.


Support Agilent Masshunter DAD format

This requires handling two files ("SD" header file and "SP" data file) for input (same as #12).
Existing implementation here:
https://github.com/bovee/Aston/blob/master/aston/tracefile/agilent_uv.py#L221

Just wanted to put in a vote for this converter. I would be very happy to be able to read these types of files into R!!!

With the new filename params from #24 , I added support for this in 1942eee438815c5f310ce0eeb2acafb5fd176e65.

Awesome!!! thank you so much


Feature/onnx export quant avg pool

Add new CustomOp that corresponds to Brevitas QuantAvgPool2d and testing export and execution of that node.

@auphelia can you have a look at the failed tests here? One of them is the newly-added QuantAvgPool2d export (unsure if this is related to the already-known failures that you discussed with Alessandro already), but the other one occurs during test_end2end_cnv_w1a1. The second one may be related to the sanitize_quant_tensor functionality, or the change in behavior in InferDataTypes in this branch.


Cleanup workaround

Based in #1, this PR decompose the different workarounds by components.

I think this is would be a good direction but it makes it hard for me to review. If we want to refactor the code, can we separate the refactor from the KSPWorkaround being added?


Compatilibity with Expo SDK 51

Description
Compatility errors when upgrading to the new version of expo sdk
CodeSandbox/Snack link
No response
Steps to reproduce

Create a project with npm create gluestack
Select expo router v3
upgrade to the sdk because that's a requirement for emulating on Expo Go App
npm install expo@latest
npx expo install --fix
See the errors

gluestack-ui Version
latest
Platform

[X] Expo
[ ] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
I have a project built with nativebase, and i am having the same issue, so i tried to upgrade the ui library to gluestack, but there is also compatibility errors, because of the new sdk by expo.

Where are you upgrading from? This issue might be related: https://github.com/gluestack/gluestack-ui/issues/1669

I have the same problem and I think its due to the react native svg dependency:

What version are you upgrading from? This issue might be related: #1669

Upgrading from the SDK 49

Yep, I get compat issues too when trying to add gluestack to an existing expo project @51.0.9

I tried  upgrading react to 18.3.1 but that caused other issues with expo

i have the same issue ,anyone found resolution to this ?


Base64 decoding not working correctly

What version of Go are you using (go version)?

$ go version
go version go1.16.4 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
windows/amd64

What did you do?

https://play.golang.org/p/EHg3FJ57PEt
What did you expect to see?
{"dn":"AUTO_permtstadm13","tgt":"TGT-1534-KkhuPbAqgrGsMPcFFKc0oGcEjW7gO4qtcRGLguUf2HxYD2wSBj-cas","uid":"AUTO_permtstadm13","un":"AUTO_permtstadm13}
What did you see instead?
{"dn":"AUTO_permtstadm13","tgt":"TGT-1534-KkhuPbAqgrGsMPcFFKc0oGcEjW7gO4qtcRGLguUf2HxYD2wSBj-cas","uid":"AUTO_permtstadm13","un":"AUTO_permtstadm13
See the missing '}' at the end
The actual base64 decoded value has  a '}' at the end
The actual (expected) decoded value can be verified from any of the online decoders like https://codebeautify.org/base64-decode

b, _ := base64.URLEncoding.DecodeString(

Don't ignore errors:

illegal base64 data at input byte 196

URLEncoding needs padding. Add a = at the end of your string and it'll work. As documented:

RawURLEncoding is the unpadded alternate base64 encoding defined in RFC 4648. It is typically used in URLs and file names. This is the same as URLEncoding but omits padding characters.

You want to use RawURLEncoding if your input has no padding.


Fix test on 32-bit targets

Fixes rdar://106707727

@swift-ci Please smoke test

(smoke testing because apparently we're not testing 32-bit targets in CI anymore anyway)

I accidentally included a second test case that I've been working on.

@swift-ci Please smoke test

@swift-ci Please smoke test macOS


Allow to be registered as panel or tab

Some Storybook addons like addon-notes can be registered as a panel (appear below the story, current behaviour of this addon) or as a tab (appear alongside 'Canvas', 'Docs' etc.). Can this addon also support registration as a tab?
References:

Getting Started for addon-docs
Tab registration
Panel registration

#47 (v5.3.0-beta)


Fix server crash on sending non-valid schema to /validate endpoint

Describe the bug
Sending file with non-valid schema name to /validate-endpoint crashes server and returns 500.
To Reproduce
Steps to reproduce the behaviour:

Send form to validate-endpoint with non-valid schema name.
Server crashes

Expected behavior
Expected server to respond with clear message about wrong schema name.
Stacktrace
While testing submission in frontend, I managed to send request to /validate with schema type null and file being null. This resulted following stacktrace:
metadata_submitter_backend_dev | [2020-07-10 13:01:37][server][1 MainProcess][INFO    ](L:40) init: Server configurations and routes loaded
metadata_submitter_database_dev | 2020-07-10T13:01:38.000+0000 I  SHARDING [ftdc] Marking collection local.oplog.rs as collection version: <unsharded>
metadata_submitter_backend_dev | [2020-07-10 13:01:55][aiohttp.server][1 MainProcess][ERROR   ](L:355) log_exception: Error handling request
metadata_submitter_backend_dev | Traceback (most recent call last):
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 1506, in open_local_file
metadata_submitter_backend_dev |     stats = os.stat(localfile)
metadata_submitter_backend_dev | FileNotFoundError: [Errno 2] No such file or directory: '/usr/src/app/null'
metadata_submitter_backend_dev |
metadata_submitter_backend_dev | During handling of the above exception, another exception occurred:
metadata_submitter_backend_dev |
metadata_submitter_backend_dev | Traceback (most recent call last):
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
metadata_submitter_backend_dev |     resp = await task
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
metadata_submitter_backend_dev |     resp = await handler(request)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
metadata_submitter_backend_dev |     return await handler(request)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/metadata_backend/api/middlewares.py", line 29, in http_error_handler
metadata_submitter_backend_dev |     response = await handler(req)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/metadata_backend/api/handlers.py", line 183, in validate
metadata_submitter_backend_dev |     schema.validate(xml_content)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/xmlschema/validators/schema.py", line 1305, in validate
metadata_submitter_backend_dev |     for error in self.iter_errors(source, path, schema_path, use_defaults, namespaces):
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/xmlschema/validators/schema.py", line 1334, in iter_errors
metadata_submitter_backend_dev |     source = XMLResource(source, defuse=self.defuse, timeout=self.timeout, lazy=False)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/xmlschema/resources.py", line 342, in __init__
metadata_submitter_backend_dev |     self.source = source
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/xmlschema/resources.py", line 359, in __setattr__
metadata_submitter_backend_dev |     self._root, self._text, self._url = self._fromsource(value)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/site-packages/xmlschema/resources.py", line 418, in _fromsource
metadata_submitter_backend_dev |     with urlopen(url, timeout=self.timeout) as resource:
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 222, in urlopen
metadata_submitter_backend_dev |     return opener.open(url, data, timeout)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 525, in open
metadata_submitter_backend_dev |     response = self._open(req, data)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 543, in _open
metadata_submitter_backend_dev |     '_open', req)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
metadata_submitter_backend_dev |     result = func(*args)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 1484, in file_open
metadata_submitter_backend_dev |     return self.open_local_file(req)
metadata_submitter_backend_dev |   File "/usr/local/lib/python3.7/urllib/request.py", line 1523, in open_local_file
metadata_submitter_backend_dev |     raise URLError(exp)
metadata_submitter_backend_dev | urllib.error.URLError: <urlopen error [Errno 2] No such file or directory: '/usr/src/app/null'>

Additional context
Clearly backend doesn't check if schema type exists, so check for this can be added first (see other methods in handlers for example). However, this sort of error where schma doesn't exist should be catched and SchemaNotFoundExpection should be raised. That raising needs to be debugged as well.

@otahontas I cannot replicate on branch develop :thinking: with Postman.
some js code of my request:
var request = require('request');
var options = {
  'method': 'POST',
  'url': 'localhost:5430/validate',
  'headers': {
    'Accept': '*/*'
  },
  formData: {
    'null': 'null'
  }
};
request(options, function (error, response) {
  if (error) throw new Error(error);
  console.log(response.body);
});

maybe doing something wrong ?

ok ...this is what replicates it:
var request = require('request');
var fs = require('fs');
var options = {
  'method': 'POST',
  'url': 'localhost:5430/validate',
  'headers': {
    'Accept': '*/*'
  },
  formData: {
    'study': {
      'value': fs.createReadStream('/path/to/file'),
      'options': {
        'filename': 'filename'
        'contentType': null
      }
    }
  }
};
request(options, function (error, response) {
  if (error) throw new Error(error);
  console.log(response.body);
});


modules, mountinfo: check scanner.Err after scanner.Scan

Check for any non-EOF errors after scanner.Scan.

test-me-please

Coverage increased (+0.02%) to 45.526% when pulling 617dd127e98543fbb3f780003df4402c881c8e5e on pr/tklauser/scanner-err into 7c023b53832de6c6e6fb825d5c678925e34b27ef on master.

test-me-please

test-me-please


The DNS-SD Resolve callback logic must be executed in the Matter task context

Problem
In the current implementation of a Matter node running over Thread a successful DNS-SD resolution can result in CASE session establishment code to be executed in the Thread task context (see attached stack trace). This is problematic as the Tread task is not generally expected to have sufficient stack to handle Matter processing. Another issue is that this may result in a semaphore block during an attempt to send a Thread message from the context of receiving a Thread message.
More info in this discussion thread: https://csamembers.slack.com/archives/G014G30SVV0/p1640643472300200
Proposed Solution
The Matter processing resulting from OnDnsResolveResult
(and probably other DNS-SD events) must be handed off to the Matter processing context.
Stack:

Always reproductible on NXP platform. Also left a comment in the Slack thread.