Walkie Talkie app does not exist.

I have found many references to this app.  It is not available when you search in the admin console or from teams itself.  About 80% of Teams tutorials and information does not work.  Really poor.  I want to switch to Teams phones, but you are missing so many basic features.  You need someone with logic working there.
[Enter feedback here]

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

ID: d91ddefc-3722-8bc2-bd9b-4a90ede28944
Version Independent ID: 35e56a9d-a01c-4126-3750-aae1ed984f55
Content: Walkie Talkie app in Microsoft Teams - Microsoft Teams
Content Source: Teams/walkie-talkie.md
Service: msteams
GitHub Login: @samanro
Microsoft Alias: samanro

Hi @jpeterson540 - I'm sorry to hear that you are frustrated with this documentation and Walkie Talkie. Some reasons you might not be able to find the app in Teams itself: it must be configured from the Teams Admin Center, and is only available on Android or iOS, not Desktop. There are also policies that control whether the app is available to users. I hope this helps.

Nope.   It is not in the teams admin center under manage apps.  We are Microsoft Business 365 Standard.  Running a Teams phone trial and  you forgot to consider a lot of basic things for phone systems.  Really poor.
Many Thanks,
JP
John Peterson AIA
DALGLIESH GILPIN PAXTON ARCHITECTS
206 Fifth Street NE
Charlottesville Virginia 22902
434 977 4480
dgparchitects.com
CHARLOTTESVILLE  BALTIMORE  URBANA
From: Samantha Robertson @.>
Sent: Tuesday, July 18, 2023 5:13 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: John Peterson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Walkie Talkie app does not exist. (Issue #10198)
Hi @jpeterson540https://github.com/jpeterson540 - I'm sorry to hear that you are frustrated with this documentation and Walkie Talkie. Some reasons you might not be able to find the app in Teams itself: it must be configured from the Teams Admin Center, and is only available on Android or iOS, not Desktop. There are also policies that control whether the app is available to users. I hope this helps.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/10198#issuecomment-1640999269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BA6Y3BXGZ6TMYOTWCE5WHY3XQ335NANCNFSM6AAAAAA2O6CP6I.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It looks like you are not the only one having trouble with the mobile Walkie Talkie app on Business Standard. Here's a Q&A thread - you can add your info here to see if there's an update or solution: https://learn.microsoft.com/en-us/answers/questions/765722/walkie-talkie-feature-cant-be-added-to-ms-teams

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

Did you read that article?  It provides no information, nor do the documents it links to.
Many Thanks,
JP
John Peterson AIA
DALGLIESH GILPIN PAXTON ARCHITECTS
206 Fifth Street NE
Charlottesville Virginia 22902
434 977 4480
dgparchitects.com
CHARLOTTESVILLE  BALTIMORE  URBANA
From: Samantha Robertson @.>
Sent: Tuesday, July 18, 2023 5:27 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: John Peterson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Walkie Talkie app does not exist. (Issue #10198)
It looks like you are not the only one having trouble with the mobile Walkie Talkie app on Business Standard. Here's a Q&A thread - you can add your info here to see if there's an update or solution: https://learn.microsoft.com/en-us/answers/questions/765722/walkie-talkie-feature-cant-be-added-to-ms-teams

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/10198#issuecomment-1641013487, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BA6Y3BTQEPHIQI2J7KUUH63XQ35SJANCNFSM6AAAAAA2O6CP6I.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

It was not resolved at all.  I was sent a different thread to read that had no information whatsoever about the issue.  I've come across a lot that doesn't work lately in tutorials and articles published by Microsoft.  I think you need help in quality control.  Also Teams phone just isn't cutting it.  Basic things any phone system needs is the ability to page someone, or everyone, and a decent screen to handle and transfer calls.  The person logged into the queue cannot see how many other calls are in the queue, they can't see which calls they have parked while they try to reach a Team member to see if they want to take a call.  Yes we have a real person that talks to callers and transfers calls to us after confirming we are able to speak at that time.  We are not always at our desks with the phone within reach.  Sometimes we are at another work area in our space, or conferring with a colleague.   Yes I realize things are changing and you think everyone always has there cell phone in their pocket.  They don't.
Many Thanks,
JP
John Peterson AIA
DALGLIESH GILPIN PAXTON ARCHITECTS
206 Fifth Street NE
Charlottesville Virginia 22902
434 977 4480
dgparchitects.com
CHARLOTTESVILLE  BALTIMORE  URBANA
From: Manuela Scanu @.>
Sent: Wednesday, July 19, 2023 12:32 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness @.>
Cc: John Peterson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Walkie Talkie app does not exist. (Issue #10198)
Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/10198#issuecomment-1641395310, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BA6Y3BRWXZXC6VU3CVLONFTXQ5PMJANCNFSM6AAAAAA2O6CP6I.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Created the first draft

@BenedictCDiscovery @foadsaliba All valid suggestions, but this time I do not have time to implement them. I have created this draft. You guys should discuss this and implement the changes.
Note: Please keep in consideration the current state DKids app regarding the new lines. I really like the number of new lines used. I like the fact that there is empty space and that help visually identify related blocks of code.


gmic-qt: refactor

bring uniformity to variants set
set sourceRoot
intern libsForQt5
migrate to by-name

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1515

Ofborg hasn't finished aarch64-darwin, but I tested it manually, so I'll go ahead and merge
Thanks!

With some luck, maybe we can delegate the next merges to the bots :)


Updated the Podfile to fix compatibility issue with CocoaPods 1.0

@MichaelCampbell this should fix the issues with the builds failing.

👍


Generalize the Chain Rule for Smart Cons

The chain rule for functions applies the function, otherwise it makes a Cons cell.
It would be nice if users could define custom chain rules.
( (App (: f (->(x y))) x) ... apply function ... )
custom chain rules go here
( (App l r) ... yield cons ... )

The syntax will become as per this thread.
https://github.com/andrew-johnson-4/-/issues/77


Nuxt Layers: pathPrefix: false prevents component imports when the application is extended

Environment
2 Nuxt Applications with same Environment:
nuxt: 3.14.1592
nitro: 2.10.4
Reproduction
Link: https://stackblitz.com/edit/nuxt-starter-tckmhw?file=base%2Fnuxt.config.ts
Steps:

cd layer
yarn or npm i
yarn dev or npm run dev

Describe the bug
When working with two Nuxt applications, one as a base and the other as a layer, there is an issue with component exports from the base application to the layer.
Here’s the scenario:

The base application contains components, which are intended to be imported and used in the layer application.
In the layer application, the base application is extended using the extend property in nuxt.config.ts.
The base application uses a nested component structure. To simplify usage, we disabled component name prefixes by setting pathPrefix: false in the nuxt.config.ts as per the official documentation.
After doing this, components from the base application are no longer exported to the layer application, making them inaccessible.

Conclusion: This behavior breaks the expected functionality where components from the base application should be seamlessly available in the layer application. It appears that the configuration in the base application's nuxt.config.ts is interfering with the component export mechanism.
And also this issue might not be limited to the pathPrefix setting. It could also occur if the base application has custom components property and with related configurations in it's nuxt.config.ts.
Logs
WARN  [Vue warn]: Failed to resolve component: TestInner
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
  at <App>
  at <NuxtRoot>

There is a concept of single-spa application (https://single-spa.js.org) that could be used to bundle the microservices. The reach of shared components is quite easy in this architecture as they serve as a microservice. On which nuxt version did the components from the base application still reach the layer application?

The ~ refers to the final project's source directory - not the layer, in this case.
If you want custom configuration only within the layer's components directories, you can do this by using an absolute path within the layer configuration file.
import { createResolver } from 'nuxt/kit'

const resolver = createResolver(import.meta.url)

export default defineNuxtConfig({
  components: [
    {
      path: resolver.resolve('./components'),
      pathPrefix: false,
    },
  ],
});


Properties not displaying when returning the entity type using JS on the components Autocomplete and Entity Picker

Description
Upon setting the entity type through JavaScript, users expect to be able to select display properties and properties for entity filtering seamlessly. However, the system fails to recognize the entity type set via JavaScript, resulting in the absence of available properties for selection. This issue affects both the Entity Picker and Autocomplete components
To Reproduce
Steps to reproduce the behavior:

Go to 'https://function-adminportal-test.shesha.dev/dynamic/Boxfusion.SheshaFunctionalTests.Common/twenty-three-details?id=9e58861b-2b22-48e9-a5ab-05fddd8cfe13'
Utilize JavaScript to dynamically set the entity type, such as return "Shesha.Core.Address". Attempt to select a display property for the entity type.
Try to select a property for entity filtering.

Actual behavior
When attempting to select a display property or a property for entity filtering after setting the entity type using JavaScript, no data is displayed. Despite configuring the entity type through JavaScript, the system fails to populate the available properties for display or filtering.
Expected behavior:
After setting the entity type using JavaScript, users should be able to select display properties and properties for entity filtering as usual. The system should recognize the entity type and provide a list of available properties for selection, allowing users to proceed with configuring the form without any issues.

Hey @nthangeniphumudzo, the issue persists. After returning the Entity Type "Boxfusion.SheshaFunctionalTests.Domain.Bank" using JS the Display Properties and the properties on the query builder are still empty upon clicking.  See the screenshot below

hi @Tshepiso-R @hlayisanimazuze @nthangeniphumudzo
This is definitely not a problem, but incorrect requirements.
A property configured via a JS does not have a specific value and can change while working with the form. Because of this, it is impossible to determine a specific value at a specific point in time.
For example, if EntityType has a JS like this -
return data.type === 1
    ? 'Shesha.Person'
    : data.type === 2
        ? 'Shesha.Member'
        : 'MyProject.Superman';

Properties from which class should be shown in the drop-down list?
In the designer mode we can't know which class will be used at a specific point in time
If such a feature is really needed and is not just a random test experiment, then real use cases and specific requirements should be described.
For example, "Display Property" should also become computable via JS...
The current Issue is meaningless, since explicitly specifying the entity type as text via JS is equivalent to selecting a value from a drop-down list and has no meaning. And if the JS contains a complex condition, then it is impossible to determine the entity type in the designer and PropertyAutocomplete will not work anyway.
It is possible to implement something like this, but it will definitely add additional load to the system, as it will require additional calculations of the model. This is why specific use cases are needed so that the implementation will optimal and generally makes sense.

Hey @AlexStepantsov, thanks for the clarity. I will close the issue.


Distant Galaxy builds Stars with Wrong name

Describe the bug
Stars are numbered wrong - when one disappears and the next spawns its usually numbered 249 or 248,  not like a running number.
To Reproduce
Start the Game and view the logfile in debug
(Both master and dev)
Expected behavior
The when 250 stars are build, the following new start should be numbered 251 etc.

I would take this one.


Aside from Kudu, what makes this project require CDH?

I think this project is a great idea! There are many simple, common ETL-like tasks, that you'd not want to write a complete Spark job for, but instead just configure what you want. Envelope seems to do just that.
It seems, however, that this should not be limited to clusters running CDH. I can imagine this running on Hortonworks or MapR clusters just fine, except for the Kudu parts, that is.
Care to comment?

I'm glad you think this project could be useful!
I don't see any fundamental reason why Envelope wouldn't work on other distributions as long as the versions of the dependencies were compatible with each other and with the cluster. The presence of the Kudu integration shouldn't break pipelines on clusters that don't have Kudu either, provided the pipeline doesn't try to access Kudu of course!

If you've got any more questions please drop a line on the Cloudera Community forum: http://community.cloudera.com/t5/Cloudera-Labs/bd-p/ClouderaLabs
Thanks!


Add the ability to track parameter values in the spec coverage file.

For large-scale testing, it is useful to have the specific values of
parameters fuzzed in the spec coverage file, in order to facilitate
root cause failure analysis.
This change adds an option to the compiler that produces a grammar which
contains the parameter names to track for every fuzzable value.
Testing:

manual testing
added/fixed engine tests to make sure new code path is exercised
Note: the payload body checker code is not modified in this change because
it does not require this feature.

Add documentation to spec coverage format.


Re-enable convenient FSDP configuration for wrapping and activation checkpointing

Description & Motivation
The pull request #18045 is about to change the way activation checkpointing gets configured in FSDP. Previously, https://github.com/Lightning-AI/lightning/issues/15825 enabled a convenient way to configure activation checkpointing without importing boilerplate code from PyTorch FSDP:
fabric = Fabric(strategy=FSDPStrategy(..., activation_checkpointing=MyTransformerBlock))

However, if #18045 it will now be necessary again to configure it like so:
from torch.distributed.fsdp.wrap import ModuleWrapPolicy

strategy = FSDPStrategy(activation_checkpointing_policy=ModuleWrapPolicy({MyTransformerBlock}))

or via a functional policy. This is now more boilerplate code than necessary, since Lightning could easily accept the class or list of classes directly and wrap it internally, which is what this issue proposes.
Pitch
Part 1
Allow passing the module classes to wrap directly to the argument:
strategy = FSDPStrategy(activation_checkpointing_policy=MyTransformerBlock)

Part 2
In addition,  #18045 also proposes to rename activation_checkpointing to activation_checkpointing_policy with the argument that the newly provided functionality is a policy and consistent with a similarly functioning argument auto_wrap_policy. Given my pitch above, and the fact that it is no longer necessary to explicitly construct a policy (it is optional), we could go for a simplified and convenient API like this:
strategy = FSDPStrategy(
    auto_wrap={MyTransformerBlock, ...}  # automatically converted to a policy under the hood
    activation_checkpointing_policy={MyTransformerBlock, ...}  # automatically converted to a policy under the hood
)

Alternatives
No response
Additional context
I strongly vote for this pitch because the purpose of Lightning is to make these tools accessible to as many users as possible, whether they are distributed training experts or not. Making complex features in PyTorch easily configurable is at the core of Lightning's philosophy :)
cc @borda @awaelchli @carmocca

I don't have a preference here. My only suggestion is that either both arguments are suffixed by _policy or none of them are.


DNN 7.2.1 not working with DNN Active Directory 6.00.06

I am trying to get ad auto sign in to work for our DNN intranet site. We are running DNN 7.2.1. Currently we have been using DNN Active Directory version 5.06, but I can't seem to get auto sign in to work after carefully following the instructions on the wiki and experimenting with different settings-. When I install the latest version of DNN Active Directory (i.e., 6.00.06) I receive the following error message after the installation: "Could not load type 'DotNetNuke.Entities.Users.IUserController' from assembly 'DotNetNuke, Version=<IP_ADDRESS>7, Culture=neutral, PublicKeyToken=null'." I have also tried installing DNN Active Directory 6.00.00, but I receive the same error. Any assistance would be appreciated. Thanks.

The issue I am having with DNN 7.2.1 and AD 5.06 is when I go to the web site I am being prompted for a username and a password in a browser dialog box (basic auth). None of the ad admin accounts seems to work for a successful login. When I click cancel on the dialog then I receive a 401.1 Unauthorized. Here some information from that screen:
'Requested URL': http:///DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx?portalid=0
Physical Path: \DesktopModules\AuthenticationServices\ActiveDirectory\WindowsSignin.aspx
Module: WindowsAuthenticationModule
Error Code: 0xc000006d

DNN doesn't cause the dialog box.  That usually is on the web server level.  Perhaps permissions on the windowssignin.aspx file?
I am busy with my "real" job right now but will get back to this project soon.  Hopefully I can give a more verbose answer at that time.

Thanks for the response. I have looked into permissions in IIS, and NTFS for the WindowsSignIn.aspx file, and made quite a few tweeks to no avail. I have had a couple other sets of eyes on this problem as well (including a network administrator) but they were not able to find the issue. I even installed DNN 9 with the latest AD module, but I am getting the same issue. Not sure what else I can try... If it helps I am running windows 7 with IIS version 7.5. I have not tried this on our servers because I wanted to have it work locally first.

Look in your web.config file and see if you can find this portion.  Should be at the bottom:
 <location path="DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx">     <!-- Disable Forms Authentication -->     <formsAuthenticationWrapper enabled="false" />     <system.webServer>       <security>         <!-- Enable IIS Windows authentication for the login page -->         <authentication>           <windowsAuthentication enabled="true" />           <anonymousAuthentication enabled="false" />         </authentication>       </security>     </system.webServer>   </location>
Does it match mine?

Yes. It appears that yours and mine are a match. Here is mine directly from the web.config:
  <location path="DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx">     <!-- Disable Forms Authentication -->     <formsAuthenticationWrapper enabled="false" />     <system.webServer>       <security>         <!-- Enable IIS Windows authentication for the login page -->         <authentication>           <windowsAuthentication enabled="true" />           <anonymousAuthentication enabled="false" />         </authentication>       </security>     </system.webServer>   </location>
Under System.web I also have this too (mentioning as I am unsure if that is correct, although, I have tried all variations that I can come up with):
    <!-- Forms or Windows authentication -->     <authentication mode="Forms">       <forms name=".DOTNETNUKE" protection="All" timeout="720" cookieless="UseCookies" />     </authentication>     <!--<identity impersonate="true" />     <authentication mode="Windows">     </authentication>-->

Should there be a code behind for the WindowsSignin.aspx in my project?

Interesting, because I don't see the code behind in the .zip file (i.e., ActiveDirectory_05.00.06_Install.zip). I downloaded this from here: https://github.com/DNNCommunity/DNN.ActiveDirectory/releases

The install package doesnt have source code.  You need to download the source package.

Just to confirm though, do I need the code behind to make the install package work?

No you do not need the code behind for installation.  All code behind compiles into a single dll file that is included in the install package.

The wiki has been updated to explain the problem with local server auto login.

The wiki has been updated to explain the problem with local server auto login.

FYI... I see you updated the wiki, but it doesn't contain a hyperlink to the article. I think the wiki is missing many hyperlinks. Could you just specify the full URL since hyperlinking isn't working?

I was able to spend some time working on the autologin feature. I have found a major problem on the Microsoft side. If you are browsing to a website on the local machine using a hostname other than the actual hostname then you will get the 401 and/or pop up box. Here is the workaround for this situation: https://support.microsoft.com/en-us/help/896861/you-receive-error-401-1-when-you-browse-a-web-site-that-uses-integrate
This problem should not present if you browse to a the site not on your local machine. Please report any results.

This fixed the problem! Thank you.

I am getting the same issue. Can you please explain how you resolved this.

I have updated the wiki.  Not sure why the link wasnt working.
@vamsisagi the link above and in the wiki explain how to work around the issu

@sawest I followed the steps and it worked in my local machine. When I am trying to do the same in production but didn't work. In production, I tried both methods that you have suggested.
Is there anything that I need to try.

Unfortunately if you indeed are experiencing the problem listed in this issue, I am rather limited on helping as it is outside the scope of this module.  The link above is about all I can do to help.  Post any fixes/research you can to help others.  If I run across any other fixes for this I will post as well.


network, masquerade: remove dummy

What this PR does / why we need it:
A linux bridge MAC is set to the lowest mac address of any of the
ports on it; the dummy is in place to help keep the mac address of
the bridge stable.
Since there's a single VM connected (hence a single tap) to the
bridge, the dummy is redundant (the pod lives as long as the VM).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @davidvossel
@vladikr / @davidvossel do you happen to have a better understanding that I about why this dummy is necessary ?
This is my best guess.

Since there's a single VM connected (hence a single tap) to the
bridge, the dummy is redundant (the pod lives as long as the VM).

What happens if the domain crashes/restarts? I know the tap device link will be "down" as there is no application connected to it, but will that have any special affect on the bridge?
Also, there is a stronger reasoning on why this can be removed: If the mac is set explicitly on the bridge, the mechanism of choosing the mac address per the 1st port attached is not in play anymore.

Since there's a single VM connected (hence a single tap) to the
bridge, the dummy is redundant (the pod lives as long as the VM).

What happens if the domain crashes/restarts? I know the tap device link will be "down" as there is no application connected to it, but will that have any special affect on the bridge?

If I just kill the qemu-kvm process the VMI goes into failed state, essentially makes the whole pod unusable (completed state).
If we restart the VMI (virsh reboot <domain name>), the bridge's addresses (mac + ips) are preserved, and the bridge stays UP.

Also, there is a stronger reasoning on why this can be removed: If the mac is set explicitly on the bridge, the mechanism of choosing the mac address per the 1st port attached is not in play anymore.

+1; I'll update the PRs description accordingly.

/approve

/test pull-kubevirt-unit-test
This flaked on me.

/retest
Guess I'm extremely unlucky; it failed again on the heartbeat unit test:
------------------------------
• Failure [1.513 seconds]
Heartbeat
pkg/virt-handler/heartbeat/heartbeat_test.go:26
  without deviceplugin and
  vendor/github.com/onsi/ginkgo/extensions/table/table.go:92
    becoming ready after a few probes, node should be set to unschedulable immediately and switch earlier than one minute [It]
    vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43

    Timed out after 1.000s.
    Expected
        <map[string]string | len:2>: {
            "cpumanager": "false",
            "kubevirt.io/schedulable": "false",
        }
    to have {key: value}
        <map[interface {}]interface {} | len:1>: {
            "kubevirt.io/schedulable": "true",
        }

    pkg/virt-handler/heartbeat/heartbeat_test.go:121
------------------------------
{"component":"","level":"info","msg":"Updating cluster config from KubeVirt to resource version 'sgjv7btdcj'","pos":"config-map.go:516","timestamp":"2021-06-01T16:21:40.827643Z"}

JUnit report was created: /tmp/cache/bazel/18316b1300bb8985bc913139d5cc6323/sandbox/linux-sandbox/4153/execroot/__main__/bazel-out/k8-fastbuild/testlogs/pkg/virt-handler/heartbeat/go_default_test/test.xml

Summarizing 1 Failure:

[Fail] Heartbeat without deviceplugin and [It] becoming ready after a few probes, node should be set to unschedulable immediately and switch earlier than one minute
pkg/virt-handler/heartbeat/heartbeat_test.go:121

Ran 8 of 8 Specs in 2.543 seconds
FAIL! -- 7 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestHeartbeat (2.54s)
FAIL


Default surface from template is created without blending points

Steps to reproduce

Start WebsiteEditor (branch develop), SignIn (branch develop)
Call http://localhost:8080/website/resetdata to load default mappings
Go to http://localhost:8080/signin/signinuser to generate the admin user and sign in
Go to http://localhost:8080/websiteeditor/surfacegroups
Create a new surface from the "Default" template
Click on "New default template" -> "Blending points"

Expected result
The new surface should have two blending points with the bottom one marked as default.
Actual result
The new surface has no blending points.
Technical information
Starcounter version <IP_ADDRESS>94

Closing as done.


Updated Ace used to version 1.2

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

What features are we picking up from this? Also, are you sure no apis changeD?

On Thu, Jul 23, 2015 at 10:00:21PM -0700, Alex Crichton wrote:

What features are we picking up from this? Also, are you sure no
apis changeD?

Something which would increase the value of this for me is a pointer
to the correct documentation.
For #143 I found enough documentation
to get the job done, but it described functions which are not in 1.1.9
so my PR is...  possibly not using Ace correctly.
--
Matthew
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.

Not sure how to quote users here but anyway ;)
The only thing I intended as an addition in updating to Ace 1.2 is the changed highlighting rules for Rust. I'm not sure what else that's changed is relevant to Playpen's use.
That said, I admit I haven't checked whether the merged changes have made it to version 1.2 or are bound to a later ver :/

I would hold off on this. That regex change messed up commenting highlighting in rustbyexample.com (see https://github.com/rust-lang/rust-by-example/issues/619). It was fixed in https://github.com/ajaxorg/ace/pull/2600 but until it makes it to a release rustbyexample is using a locally fixed version: https://github.com/rust-lang/rust-by-example/pull/620. Merging would probably force playpen to do something similar too.

Weird. The specific reason mentioned (that // is treated as an operator) wasn't in anything I'd changed (only operators I'd included in the regex where single-glyph and /\|\||&&|->|==/ and the assignment ones, only :/

Eh, the problem with this regex is it's kinda repetitive and a lot of it doesn't do anything helpful and isn't obvious:
 /[$]|->|--?|\+\+?|==?|<<=|>>=|[<>]=?|[&]{2}|[|]{2}|[$]|[|!&^*\-+%/]=?/

// This part has a few issues:
[|!&^*\-+%/]=?

1. `\-+` is a range starting with `\` and ending with `+` which probably wasn't
the intent. The class should be `[-|!&^*\+%/]` to avoid the range.
2.

The way you avoid this is with both positive and negative look-around assertions which most regex don't support (javascript only supports forward it seems). Look-around allows you to say "I'm looking for ++ which isn't either followed or preceded by a + but may be followed by a ?.

OK, sounds like we should hold off on merging for now according to @mdinger, so I'm going to close.


Add API docs where unmapped reads are discarded

See https://github.com/bigdatagenomics/adam/pull/2019 ; https://github.com/bigdatagenomics/adam/pull/2019#issuecomment-407142702

Closing as WontFix


Support generic tasks or improve documentation on why it's not possible (and perhaps suggest workarounds)

I was looking at #1837 which didn't really have a resolution, in my mind. So this feature request comes from a bit of ignorance as I don't know why this wouldn't be possible. The best work around for now seems to be to generate tasks using a macro.
What I basically want is the ability to hand a task any device like Spi, Pwm Uart, etc. It seems to me like the proc macro is making the function generic (on nightly) behind the scenes using RPIT, so some level of genericness seems possible at least? Based on the mentioned issue it seems like it was possible to bypass the macro check using TAIT in arguments to make it compile as well.
If there is a fundamental blocker I think it would be very helpful to have some documentation on how this can be worked around.
On a separate note, I've been trying out Embassy for a small project at work and it has been a breath of fresh air for embedded development. :+1:

I'm new to this project as well but I recently had the same thought (and would like to double check my reasoning!) so thought I'd share my understanding.
An async executor needs to be able to know about the tasks that it is responsible for polling. Additionally those tasks need somewhere to store their in-progress state. In embassy (on stable) the latter is achieved as follows -

An async function undergoes compiler magic to transform it into an unnamed type we'll call F, which implements Future. This type encompasses the in-progress state of the function and so its size depends directly on the types used by the function.
To use an async function with embassy, a task is created using the embassy_executor::task annotation macro. It's implementation wraps the annotated function in a new function (accepting the same arguments).
The wrapper function additionally declares a local static variable which is a reference TaskPoolRef to the TaskPool<F> for the original function.
When invoked the wrapper uses this reference to create a task by adding a closure, capturing the wrapped function and the invocation arguments, to the pool and returning a reference TaskRef (SpawnToken is a newtype wrapping a TaskRef for a few reasons inconsequential to this explanation).

The crux of the generics issue is that (source) -

A static item defined in a generic scope (for example in a blanket or default implementation) will result in exactly one static item being defined, as if the static definition was pulled out of the current scope into the module. There will not be one item per monomorphization.

The problematic code is happening across steps 3 & 4 above. Breaking it down -

The generically typed TaskPool<F> is lazily allocated on first access by TaskPoolRef using an Arena.
The allocation size if based on the inferred (i.e. _) type of F for this first (monomorhpized) instance.
Subsequent access to the TaskPool<F> is via TaskPoolRef which unsafely casts to the inferred type of F for this (monomorhpized) instance.

This works fine assuming there is only one F - the first (monomorhpized) instance is thereby guaranteed to be the only (monomorhpized) instance. Embassy enforces this invariant by preventing generic types (along with other checks e.g. no variadics).
If this invariant wasn't there, these different (monomorhpized) instances could potentially require different amounts of memory to store and/or be storing different types and/or in a different order. Thereby resulting in undefined behaviour after the unsafe cast.
On nightly, TAIT allows F to be named as Fut and used in a static type, thereby delegating responsibility for upholding the invariant to the compiler. This also eliminates the need for TaskPoolRef because TaskPool<F> can be statically defined as TaskPool<Fut>.
TLDR; with or without TAIT you somehow need to ensure there is a static TaskPool<F> for each F, meaning you need to define a task per F.
Here's an example of how this invariant could be lifted in a std context. However, applying that here would require some form of runtime allocation with the typical problems that would involve.
An outstanding question I had was - does nightly's use of TAIT allow the explicit generic check to be removed? Quickly butchering the macro code and hacking the tests suggests it should work although the error is obtuse so I can see the benefit of leaving it in place -
    #[task]
    async fn task1<T>(trace: T) where T: Tracer + 'static {
        trace.push("poll task1")
    }

error: type parameter `T` is part of concrete type but not used in parameter list for the `impl Trait` type alias
  --> tests/test.rs:65:5
   |
65 |     #[task]
   |     ^^^^^^^
   |
   = note: this error originates in the attribute macro `task` (in Nightly builds, run with -Z macro-backtrace for more info)

I'm new to the Rust, and stumbled at similar problem. I found out that passing impl with 'static often works.
Example GPIO task (with Flex that supports both reads and writes
async fn touch_task(
    mut flex:  Flex<'static, impl Pin + 'static>,
    ...
)

and PWM
async fn pwm_task(
    mut pwm: Pwm<'static, impl embassy_rp::pwm::Channel>,
    ...
) {
   ...
}

Interesting, I hadn't tried that. I think it's an embassy bug though.
Based on my reasoning above, I would expect that the block on generics is meant to extend to impl T. No matter whether it's qualified with 'static (I understand this to just disallow implementations that are or contain non-static references), nor its nested depth in the argument type (e.g. impl T, T<impl U>, etc.). However, I can't see any checks for it.
I think it's just happening to work in this case because the types implementing the Pin/Channel trait happen to have a compatible memory layout (read as - undefined behaviour). Or possibly you're only using a single implementation in your binary? Not sure...

oh yes this is definitely a bug!

I stumbled on this error which brought me here.
I have a task with this signature that I managed to get to compile:
pub async fn some_task (some_struct: SomeStruct<'static, &'static mut TcpSocket<'static>, 4096, 4096>)
Does this limitation mean that I need to duplicate myself the entire function's code for every TcpBuffer with different buffer sizes?
Is there any way to workaround that?

I use a non-task async function and wrap that in a tiny task, like this:
#[embassy_executor::task]
pub async fn some_task_0 (some_struct: SomeStruct<'static, &'static mut TcpSocket<'static>, 1024, 1024>) {
    some_task_inner(some_struct)
}

#[embassy_executor::task]
pub async fn some_task_1 (some_struct: SomeStruct<'static, &'static mut TcpSocket<'static>, 4096, 4096>) {
    some_task_inner(some_struct)
}

async fn some_task_inner<const A: usize, const B: usize> (some_struct: SomeStruct<'static, &'static mut TcpSocket<'static>, A, B>)

Thanks, that's simple.
Need to await the inner task inside the calling async fn, right?

Ah, you sure do, that's what I get for writing code in the github comment box.


Scale down API cluster as capacity not required

What is this PR trying to achieve?
A reasonable provision for the API cluster.

[ ] Run terraform apply.

Better – but now we’re wasting a lot of capacity.
CPU:
a pair of c4.xlarge     2 * (1024 * 4)   = 8192

API tasks               2 * (1024 + 128) = 2304
Loris tasks             2 * (1024 + 128) = 2304
-----------------------------------------------
Spare                  8192 - (2304 * 2) = 3584

Memory:
a pair of c4.xlarge     2 * (1024 * 8)   = 16384

API tasks               2 * (2048 + 128) =  4352
Loris tasks             2 * (2048 + 128) =  4352
------------------------------------------------
Spare                 16384 - (4352 * 2) =  7680

tl;dr: If we’re paying for c4.xlarges, we can afford to run another API and another Loris task without paying an extra cent – deploys might be a bit slower, but the majority of the time is spent not-deploying.


Can't run docker

2023-02-04 17:35:15 [2023-02-05 01:35:15 +0000] [1] [INFO] Starting gunicorn 20.1.0
2023-02-04 17:35:15 [2023-02-05 01:35:15 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:9000 (1)
2023-02-04 17:35:15 [2023-02-05 01:35:15 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
2023-02-04 17:35:15 [2023-02-05 01:35:15 +0000] [8] [INFO] Booting worker with pid: 8
2023-02-04 17:35:26 [2023-02-05 01:35:26 +0000] [8] [ERROR] Exception in worker process
2023-02-04 17:35:26 Traceback (most recent call last):
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 1348, in do_open
2023-02-04 17:35:26     h.request(req.get_method(), req.selector, req.data, headers,
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 1282, in request
2023-02-04 17:35:26     self._send_request(method, url, body, headers, encode_chunked)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 1328, in _send_request
2023-02-04 17:35:26     self.endheaders(body, encode_chunked=encode_chunked)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 1277, in endheaders
2023-02-04 17:35:26     self._send_output(message_body, encode_chunked=encode_chunked)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 1037, in _send_output
2023-02-04 17:35:26     self.send(msg)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 975, in send
2023-02-04 17:35:26     self.connect()
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 1447, in connect
2023-02-04 17:35:26     super().connect()
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/http/client.py", line 941, in connect
2023-02-04 17:35:26     self.sock = self._create_connection(
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/socket.py", line 824, in create_connection
2023-02-04 17:35:26     for res in getaddrinfo(host, port, 0, SOCK_STREAM):
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/socket.py", line 955, in getaddrinfo
2023-02-04 17:35:26     for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
2023-02-04 17:35:26 socket.gaierror: [Errno -3] Temporary failure in name resolution
2023-02-04 17:35:26
2023-02-04 17:35:26 During handling of the above exception, another exception occurred:
2023-02-04 17:35:26
2023-02-04 17:35:26 Traceback (most recent call last):
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
2023-02-04 17:35:26     worker.init_process()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/uvicorn/workers.py", line 66, in init_process
2023-02-04 17:35:26     super(UvicornWorker, self).init_process()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/workers/base.py", line 134, in init_process
2023-02-04 17:35:26     self.load_wsgi()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
2023-02-04 17:35:26     self.wsgi = self.app.wsgi()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/app/base.py", line 67, in wsgi
2023-02-04 17:35:26     self.callable = self.load()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
2023-02-04 17:35:26     return self.load_wsgiapp()
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
2023-02-04 17:35:26     return util.import_app(self.app_uri)
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/gunicorn/util.py", line 359, in import_app
2023-02-04 17:35:26     mod = importlib.import_module(module)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module
2023-02-04 17:35:26     return _bootstrap._gcd_import(name[level:], package, level)
2023-02-04 17:35:26   File "", line 1050, in _gcd_import
2023-02-04 17:35:26   File "", line 1027, in _find_and_load
2023-02-04 17:35:26   File "", line 1006, in _find_and_load_unlocked
2023-02-04 17:35:26   File "", line 688, in _load_unlocked
2023-02-04 17:35:26   File "", line 883, in exec_module
2023-02-04 17:35:26   File "", line 241, in _call_with_frames_removed
2023-02-04 17:35:26   File "/app/app/webservice.py", line 55, in
2023-02-04 17:35:26     model = whisper.load_model(model_name)
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/whisper/init.py", line 108, in load_model
2023-02-04 17:35:26     checkpoint_file = _download(_MODELS[name], download_root, in_memory)
2023-02-04 17:35:26   File "/app/.venv/lib/python3.10/site-packages/whisper/init.py", line 50, in _download
2023-02-04 17:35:26     with urllib.request.urlopen(url) as source, open(download_target, "wb") as output:
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 216, in urlopen
2023-02-04 17:35:26     return opener.open(url, data, timeout)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 519, in open
2023-02-04 17:35:26     response = self._open(req, data)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 536, in _open
2023-02-04 17:35:26     result = self._call_chain(self.handle_open, protocol, protocol +
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 496, in _call_chain
2023-02-04 17:35:26     result = func(*args)
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 1391, in https_open
2023-02-04 17:35:26     return self.do_open(http.client.HTTPSConnection, req,
2023-02-04 17:35:26   File "/usr/local/lib/python3.10/urllib/request.py", line 1351, in do_open
2023-02-04 17:35:26     raise URLError(err)
2023-02-04 17:35:26 urllib.error.URLError: <urlopen error [Errno -3] Temporary failure in name resolution>
2023-02-04 17:35:26 [2023-02-05 01:35:26 +0000] [8] [INFO] Worker exiting (pid: 8)
2023-02-04 17:35:26 [2023-02-05 01:35:26 +0000] [1] [INFO] Shutting down: Master
2023-02-04 17:35:26 [2023-02-05 01:35:26 +0000] [1] [INFO] Reason: Worker failed to boot.

Hello @DamonGuzman,
Could you please share your running environment and container details?

So I had this same issue. The issue was I have multiple network cards, one of which did not have internet access. For me the solution was to unplug that network card that did not have internet access and it ran fine. This may only be an issue for the first run since it looks like it downloads the model. @ahmetoner @DamonGuzman

@clintdavis77, Thanks for reporting your solution for offline usage.
@DamonGuzman If you want to use whisper completely offline, you should store models (download links) in a local directory and then you should mount this directory to container. Here is an example:
# via Docker run

docker run -d -p 9000:9000 -e ASR_MODEL=base -v /whisper-models-directory:/root/.cache/whisper onerahmet/openai-whisper-asr-webservice:latest

# in docker-compose.yml
volumes:
    - /whisper-models-directory:/root/.cache/whisper


Is it possible to use a custom trained checkpoint of MDM ?

I'd also be extremely curious about this.

Rename your checkpoint file to mdm_t2m.pth (human_ml3d dataset) or mdm_kit.pth (kitml dataset) and drop it into ckpts folder


remove project feature

test coverage:

Pull Request Test Coverage Report for Build 255270535

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.941%

Totals

Change from base Build 254847379:
0.0%

Covered Lines:
19145

Relevant Lines:
44848

💛  - Coveralls


Turtlbot3 + WebCam -> Gazebo

I have connected a webcam to my TB3 and I would like to experiment with it in the Gazebo simulator. I have set the TB3_MODEL and TURTLEBOT3_MODEL to waffle_pi and that seems to work fine. But now I am trying some simple scripts that use OpenCV to display the image in a window, and it displays the image for a few seconds in a cv2 namedWindow, but then the named window dies. I am looking for sample code for TB3 for this very simple example.

Sorry. We have not provide simple OpenCV example.
But tb3_autorace package is nice example for using OpenCV.
Futhermore, I attached below link for you.
http://wiki.ros.org/opencv3

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.


Kill container directly if timeout is 0.

Based on CRI Defination, timeout 0 means forcibly terminate the container immediately.
So skip graceful deletion when timeout is 0.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Apply LGTM based on https://github.com/kubernetes-incubator/cri-containerd/pull/75#pullrequestreview-43831790.

Offline discussed with @yujuhong, she's also ok with the change. Merge it.


Compiler panic when you modify the value of an element of a slice

Aim
We (https://github.com/FuzzingLabs) found that the compiler panics when you modify the value of an element of a slice
Expected Behavior
No panic should occur.
Bug
The compiler panics whenever you modify the value of an element of a slice. This issue doesn't depend on the size of the slice or the values used; it only happens with the slice type.
The compiler still panics if you modify the entire slice, but the error message is different.
The issue occurs with the latest compiler version on the master branch. The error message is as follows:
The application panicked (crashed).
Message:  Found unexpected tree combination during SSA: (Branch([Leaf(Mutable(Id(5), Numeric(Unsigned { bit_size: 64 }))), Leaf(Mutable(Id(6), Slice([Numeric(Signed { bit_size: 32 })])))]), Leaf(Array([Numeric(Signed { bit_size: 32 })], 1)))
Location: compiler/noirc_evaluator/src/ssa/ssa_gen/value.rs:152

The error message obtained with modification of the entire slice is as follows:
The application panicked (crashed).
Message:  internal error: entered unreachable code: assign: Expected lhs and rhs values to match but found Branch([Leaf(Mutable(Id(5), Numeric(Unsigned { bit_size: 64 }))), Leaf(Mutable(Id(6), Slice([Numeric(Signed { bit_size: 32 })])))]) and Leaf(Normal(Id(8)))
Location: compiler/noirc_evaluator/src/ssa/ssa_gen/context.rs:1035

To Reproduce
fn main() {
/* panic if you try to modify the value of an element of a slice */
let mut var: [i32] = [1];
var[0] = 3;

/* size or values doesn't matter */
let mut var: [i32] = [1, 2, 3, 4, 5, 99999999, 7, 8, 9];
var[5] = 6;

/* no panic with array */
let mut var: [i32; 1] = [1];
var[0] = 3;

/* another panic message appears when you modify the entire slice */
let mut var: [i32] = [1];
var = [3];
}

Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
None
Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

This is related to the array to slice coercion which is being used here. The [1] literal is now an array literal, not a slice literal which would be &[1]. When an array is assigned to a slice variable however, it is coerced via an implicit call to .as_slice(). Showing the monomorphized output of the first two lines confirms this:
fn main$f0() -> () {
    let var$0 = as_slice$as_slice([1]);
    var$l0[0] = 3
}

Curiously, adding an explicit .as_slice() seems to produce the same monomorphized IR but does not lead to a panic:
fn main() {
    let mut var: [i32] = [1].as_slice();
    var[0] = 3;

Produces the same:
fn main$f0() -> () {
    let var$0 = as_slice$as_slice([1]);
    var$l0[0] = 3
}

Using an explicit slice literal &[1] to begin with also fixes the issue, but we should fix the panic regardless. Perhaps the types used in the as_slice expression when it is auto-generated are incorrect.

I can't reproduce this issue. It might be that this issue existed in the old resolver and the elaborator doesn't have this bug.
I'm closing this, but @vezenovm feel free to open if it reproduces on your side.


Common storage backend for all migplans sharing a migstorage

This is intended enable performance gain of same image layers
referenced across multiple migplans

try to validate, don't see it not working. Will remove the WIP once I have tested it

\test

@alaypatel07 Added this as a perf/scale PR to the overall tracking issue https://github.com/konveyor/mig-controller/issues/597

@alaypatel07 is this PR ready for review or still WIP?

@djwhatle yes removed the WIP after testing. Tested +ve results for the three scenarios as follows:
A couple ways to test:
(assume migplanA:namespace1, migplanB:namespace2)
1. Open migplanA, migplanB, migrate migplanA, migrate migplanB
2. Open migplanA, migplanB, migrate migplanA, close migplanA, migrate migplanB
3. Open migplanA, migrate migplanA, close migplanA, repeat with B

1 shows that having multiple running registries pointing to the same storage is OK. 2 and 3 demonstrate that close plan cleanup doesn't interfere with other plans.


add back namespace APIs

Signed-off-by: Chengxuan Xing<EMAIL_ADDRESS>Adding back namespace methods for discovery

replaced by https://github.com/hyperledger/firefly-sdk-nodejs/pull/56 as I cannot push new commit to existing branch


As a curator I want access to the "status" attributes of my taxon name through the API  [was: API Query]

Can we pull the status of a taxon (nomen nudum/nomen dubium) using the api? We are not seeing where it is.

Good catch, TaxonNameRelationship and TaxonNameStatus are not exposed
@proceps @jlpereira I wonder if we create a unified status endpoint that includes both for a taxon name?  Would that be perhaps usable in the new taxon name interface as well?

we have method .combined_statuses which brings together list of statuses which come from both relationships and classifications. It could be exposed with an endpoint.

@jcabbott13 I suspect you want a human readable summary string?  Or will you compose the "status" from the raw data?

Yes…human readable string is preferred, but we can probably work with either.


Messages sent twice to Gitter while using integration tests

Cake.Issues.Recipe uses an integration test script which is called from AppVeyor. This results in messages being sent twice to Gitter for release builds: Once for the actual build and once for integration tests.

This was confirmed as working by @pascalberger


add hclfmt.nix

Mhm actually this seems to break:
[nix-shell:~/work/kuutamo/core]$ treefmt --fail-on-change
[INFO]: #hclfmt: 1 files processed in 3.33ms
[INFO]: #shell: 5 files processed in 122.72ms
[INFO]: #python: 17 files processed in 256.47ms

traversed 475 files
matched 386 files to formatters
left with 23 files after cache
of whom 1 files were re-formatted
all of this in 308ms

formatted files:
#hclfmt:
- /home/joerg/work/kuutamo/core/ops/modules/aws-backup/approle.tf
[ERR]: fail-on-change


Enum/Scalar Handlers

We should introduce a way of coercing enum values and custom scalar types. Since alumbra.spec 0.1.6 every leaf value contains a type annotation which can be used for coercion.
alumbra.claro already implements coercion for the base scalar types, as well as translation for enums from/to kebab-case and snake_case respectively. All that remains to be done is offering a way to attach custom coercers.

As of alumbra/claro@65defb4, the :scalars key can be passed to the executor to define encode and decode functions for custom scalars or enums.

Is there any documentation to achieve a custom scalar? I'm trying to create a custom Date scalar.

@mruzekw I extended the docstring for alumbra.core/handler today, so there you should find some information. I'm still working on actual guides and examples.
In short:
(alumbra.core/handler
  {:schema ...
   :query ...
   :scalars {"Date" {:encode format-date, :decode parse-date}})

I hope this helps!


bump feemarket in release branch

Upd dependency to 1.1.1

https://github.com/neutron-org/neutron-tests/actions/runs/10577845564
testrun


Unable to resolve nonexistent file ... javascript.code-snippets in SQL Editor

Azure Data Studio Version: Dev, Insiders
OS Version: Windows 11

When typing in query editor, it leads to below error in console log. Seems related with some builtin JS extension which is falsely activated in SQL Editor 🤔
[error] Error: Unable to read file 'c:\Users\~\Code\GitHub\azuredatastudio\extensions\javascript\snippets\javascript.code-snippets' (Error: Unable to resolve nonexistent file 'c:\Users\~\Code\GitHub\azuredatastudio\extensions\javascript\snippets\javascript.code-snippets')
    at new FileOperationError (vscode-file://vscode-app/c:/Users/~/Code/GitHub/azuredatastudio/out/vs/platform/files/common/files.js:426:13) [<root>]
    at FileService.restoreReadError (vscode-file://vscode-app/c:/Users/~/Code/GitHub/azuredatastudio/out/vs/platform/files/common/fileService.js:480:20) [<root>]
    at FileService.doReadFileStream (vscode-file://vscode-app/c:/Users/~/Code/GitHub/azuredatastudio/out/vs/platform/files/common/fileService.js:469:28) [<root>]
    at async FileService.doReadFile (vscode-file://vscode-app/c:/Users/~/Code/GitHub/azuredatastudio/out/vs/platform/files/common/fileService.js:397:28) [<root>] file:///c%3A/Users/~/Code/GitHub/azuredatastudio/extensions/javascript/snippets/javascript.code-snippets

This is happening for Notebooks too - @cheenamalhotra @kisantia were you going to look into this? Not sure what the user impact is, but it's filling up the console logs with a ton of stuff which isn't great.

Should hopefully be as simple as bringing over https://github.com/microsoft/vscode/blob/main/extensions/javascript/snippets/javascript.code-snippets

We're also missing https://github.com/microsoft/vscode/blob/release/1.82/extensions/javascript/syntaxes/Regular Expressions (JavaScript).tmLanguage file, is that something we should bring over too?

sure don't think it'll hurt to bring it over since that file was there in the previous ADS release.


SimpleMDE occurs an error to preview.

Describe the bug
SimpleMDE occurs an error to preview.
To Reproduce

Install Orchid as the very basic way.
Access /admin/example-editors page.
Input something on SimpleMDE, and press Toggle Preview.
Check the below error on the console of DevTools.

vendor.js?id=d8f40f248cc76311d0a5:2 Uncaught TypeError: o is not a function
    at Y.markdown (vendor.js?id=d8f40f248cc76311d0a5:2:1255267)
    at Object.Y.t.previewRender.t.previewRender (vendor.js?id=d8f40f248cc76311d0a5:2:1254253)
    at Object.j [as action] (vendor.js?id=d8f40f248cc76311d0a5:2:1247341)
    at HTMLAnchorElement.t.action.t.action.e.onclick (vendor.js?id=d8f40f248cc76311d0a5:2:1261640)

Expected behavior
It just need to show the preview of the markdown input.
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 97.0.4692.99

Additional context
I think this error is related with some wrong dependencies, because I can see the below messages, when I do npm audit.
# npm audit report

quill  <=1.3.7
Severity: moderate
Cross-site Scripting in quill - https://github.com/advisories/GHSA-4943-9vgg-gr5r
No fix available
node_modules/quill

simplemde  *
Severity: moderate
Moderate severity vulnerability that affects simplemde - https://github.com/advisories/GHSA-wg85-p6j7-gp3w
No fix available
node_modules/simplemde

2 moderate severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Can anyone help me to solve this issue?
Thank you for reading.

I confirm this issue. Preview has the same behavior.


Migration Guide v1 to v2

Any source or migration guide from v1 to v2?

hey @wongzigii
you may find this interesting:
https://docs.walletconnect.com/2.0/advanced/migrating-from-v1.0


Custom probability functions for service/interarrival times

Option to pass Ciw a function to sample from to obtain service / inter-arrival times

@sluenenglish you happy to do this?

Yes sure :+1:  will give it a go

:boom: :hatching_chick: :rooster: :toilet: :basketball: :art: :bento: :rocket:

Implemented with commit 012c60bb3cee688aa4496a62306ecea84c9673b4 :hatching_chick:


conda-build 3, remove clangdev runtime dependency

finish up #4

removes runtime dependency on clangdev
adds run_constrained to get compatibility constraints for users with conda >=4.4
pinning in conda_build_config.yaml
toolchain template variables

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


WW-4901 Decouples from URL.openConnection implementation of container

Changes Unknown when pulling 94758b699cfea1bb8bfba777dcc383b4dcd41436 on yasserzamani:WW-4901 into ** on apache:master**.

Changes Unknown when pulling d082aaca2a6d2d3a37b374ad34f4ea8d091d09f1 on yasserzamani:WW-4901 into ** on apache:master**.

Looks good to me, LGMT 👍


Global Data Flow: Control Flow Analysis

Global Data Flow currently has no support for control flow analysis. We should add that back in.

Thanks for your suggestion @JLLeitschuh, would you like this to be assigned to you? :)


Complete migration of code from Mifos IO for fims-web-app

Migrated the remaining commits from Mifos IO to Fineract CN.
@crain , @myrle-krantz , @awasum . Is there a reason why all was not migrated? Please advice so that I can close the PR if not correct.

I think you are right @kengneruphine .


feat(ui-ux): update sui backing address

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

Fixes #
Sample Links & Screenshots:

Link:

Desktop Screenshot

Mobile Screenshot

Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on multiple web browsers
[ ] Tested responsiveness (e.g, iPhone, iPad, Desktop)
[ ] No console errors
[ ] Unit tests*
[ ] Added e2e tests*

@chloezxyy can you update test case too proof-of-backing.spec.ts


Wrong wording in greek localization

In class CountrySelectorLocalizationEl and specifically in line 18 stands this: return 'Επιλέγω $country';. The correct one in Greek is "Επίλεξε" instead of "Επιλέγω".

Please submit a PR with the required changes

fixed in 1.0.8


nixos/tests/k3s: can't run tests: error: 'k3s_1_24' has been removed from nixpkgs as it has reached end of life

Describe the bug
❯ nix-build default.nix -A multi-node
error:
       … while evaluating the 'name' attribute of a derivation

         at «none»:0: (source not available)

       … while evaluating the attribute 'value'

         at /home/bbigras/src/nixpkgs/lib/modules.nix:809:9:

          808|     in warnDeprecation opt //
          809|       { value = builtins.addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          810|         inherit (res.defsFinal') highestPrio;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: 'k3s_1_24' has been removed from nixpkgs as it has reached end of life
❯ nix-build default.nix -A single-node
error:
       … while evaluating the 'name' attribute of a derivation

         at «none»:0: (source not available)

       … while evaluating the attribute 'value'

         at /home/bbigras/src/nixpkgs/lib/modules.nix:809:9:

          808|     in warnDeprecation opt //
          809|       { value = builtins.addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          810|         inherit (res.defsFinal') highestPrio;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: 'k3s_1_24' has been removed from nixpkgs as it has reached end of life

Steps To Reproduce
Steps to reproduce the behavior:

cd nixpkgs/nixos/tests/k3s
nix-build default.nix -A single-node or nix-build default.nix -A multi-node

Expected behavior
success
Screenshots
Additional context
Notify maintainers
@euank @mic92 @superherointj @yajo

Metadata

system: "x86_64-linux"
host os: Linux 6.8.2, NixOS, 24.05 (Uakari), 24.05.20240406.ff0dbd9
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.18.2
nixpkgs: not found

Add a :+1: reaction to issues you find important.

https://github.com/NixOS/nixpkgs/tree/master/pkgs/applications/networking/cluster/k3s

I was able to reproduce the problem you mention.
We don't have that problem because we run tests as:

nix build .#k3s.passthru.tests.single-node .#k3s.passthru.tests.multi-node .#k3s.passthru.tests.etcd

I suspect nix-build is using some extraneous old nixpkgs version that has k3s pointing out to k3s_1_24 still.
So you get this mismatch from your system and nixpkgs.

@bbigras Can I close this?

@bbigras Did you have any other fix in mind for this?


[Docs]: Pre-flight check page

Type
New content idea
What do you want to report?
We need a page describing pre-flight checks
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Overview > Expand a bit on what preflight check is - it's a job that runs before every pipeline in your org, if it fails pipeline won't start. Only have 1 warning.
Restricting who can start promotions > You can achieve the same result with Deployment Targets
Permissions required > Let's remove this section from the docs

Review links:

project: https://storage.googleapis.com/sem-docs/main/index.html#/docs/using-semaphore/projects%23preflight
organization: https://storage.googleapis.com/sem-docs/main/index.html#/docs/using-semaphore/org-preflight

Fixed on #148

Looks good 👍
Slight suggestion added: https://github.com/semaphoreci/semaphore/pull/148#discussion_r1713659386
Please close this ticket once reviewing the suggested change.


Green Uop unary check

#2787

linearizer should fallback to float32 for imagef https://github.com/tinygrad/tinygrad/actions/runs/7229870390/job/19701282549?pr=2787#step:14:302
skipping non-unary ops for now (still handling the dtypes in the uop function). To unblock binary ops, we need two things:

adding two bools (eg. CMPLT results) should autocast to int, then get rid of logic and in llvm: https://github.com/tinygrad/tinygrad/blob/master/tinygrad/renderer/llvmir.py#L17
https://github.com/tinygrad/tinygrad/actions/runs/7229870390/job/19701282273?pr=2787#step:14:2417
remove CMPLT f32() hack in webgpu
https://github.com/tinygrad/tinygrad/blob/master/tinygrad/renderer/cstyle.py#L340

cool! if you want you can do the unary and binary check. I am working on the where one https://github.com/chenyuxyz/tinygrad/pull/54

sg - do you think we can merge this one for unaries and I'll work on binary next? @chenyuxyz

gotta revert again - i'll figure out why

we should also add more fuzz / kernel search test to CI to increase kernel variety


File Disappearance

ADD ISSUE DESCRIPTION HERE
Version: 1.96.0
Commit: 138f619c86f1199955d53b4166bef66ef252935c
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Embedder: vscode.dev

When I logged into VSCode Edu as usual, my files weren't there

Can you use this flow to file an issue please:

That takes you to: https://aka.ms/vscedu/feedback
This is the repo for VS Code, not for EDU.

My mistake thank you for the clarification have a great rest of your week
On Fri, Dec 13, 2024, 1:16 PM Tyler James Leonhardt <
@.***> wrote:

Can you use this flow to file an issue please:
image.png (view on web)
https://github.com/user-attachments/assets/4150fa2d-7cfc-4876-8d8e-86afcaa689b5
That takes you to: https://aka.ms/vscedu/feedback
This is the repo for VS Code, not for EDU.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/236095#issuecomment-2542395077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNWAU7B4TKEICSILACQAZJD2FNFCDAVCNFSM6AAAAABTSU5HS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBSGM4TKMBXG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Feature request (Webhooks mgmt)

My body needs webhook managment on ORG and Site level (and alerting configuration) Since these always need to be changed by our team.

Hi @steinzi ,
Just to let you know v0.1.20 (and later) are providing Webhook management.


⚠ ClamAV has degraded performance

In 4233e6c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 127 ms

Resolved: ClamAV performance has improved in 0d06209.


Recommend functional service names

I will touch a very sensitive topic: service names. IMHO we should advise naming services that implement APIs to be with their name as close as possible to the API name itself.
I'm observing a high number of services with names that are more or less random (hero names, chemical elements, ...). Such names make it very difficult to understand the architecture of a system or even parts of it. It's also impossible to add such names to any kind of documentation or diagram.
A rule of thumb is to name the service with the root aggregate, entity or bounded context that's being managed by it. Examples:

Stock Location for managing Stock Locations,
Sales Order for managing Sales Orders,
Retail Catalog manages Retail Products (aggregate of product, price and stock data).
Fulfillment Order for managing Fulfillment Orders, Shipment Orders, Shipments (bounded context).

One can of course argue, that in different domains, an order means sth. different. However, prefixing the entities with the domain (bounded context) name is widely used: Purchase Order, Sales Order, Fulfillment Order, Shipment Order.
Technical services & abbreviations
Code names are widely used for technical services, appliances and libraries (Nakadi, buku, bubuku, spilo), which is perfectly fine in my point of view. Other examples exist though (Exception monitor, Deploy Control).
Smart abbreviations like Cuxy for CUstomer proXY should be allowed for technical components like caches, tools.
Suggestion for the guidelines
Service names (and thus their public URLs)

Must: Service name is closely related to the entities, aggregate or bounded context that they manage (i.e. Fulfillment Order, Sales Order, Stock Location).
Must: Use code names internally, don't expose them to clients.
Could: Use code names for technical infrastructure components (like Nakadi).

/cc: @codekultur @tfrauenstein

I guess this could go into the "Naming" section.

I think we should discuss this together with the naming of permissions-topic, as they might relate - both should be modelled around bounded context names IMHO.

@ePaul @codekultur @bocytko Hey, is this question still on the table ("open") or did you resolve it?

We are still discussing a coherent model for naming API hosts, permissions and event names based on Zalando's product structure and functional components. As we don't want to introduce a central API gateway, but use a DNS based approach (which is then coupled in some way to AWS accounts), this is a larger topic: We must find a solution that keeps those names resilient against organisational and technical changes. If you like to know more details of the current discussion, please let me know.

Guideline changes can be found here https://github.com/zalando/restful-api-guidelines/tree/new-naming-schema - should be merged after new naming schema is communicated.

Amazing to see this moving forward!

Thanks, Bartosz, for bringing this up.
Only yesterday, I realised that “Bankroll API” has nothing to do with money, or bankrolls, but serving product pictures.

asko

On 30 Aug 2016, at 14.57, bocytko<EMAIL_ADDRESS>wrote:
I will touch a very sensitive topic: service names. IMHO we should advise naming services that implement APIs to be with their name as close as possible to the API name itself.
I'm observing a high number of services with names that are more or less random (hero names, chemical elements, ...). Such names make it very difficult to understand the architecture of a system or even parts of it. It's also impossible to add such names to any kind of documentation or diagram.
A rule of thumb is to name the service with the root aggregate, entity or bounded context that's being managed by it. Examples:
Stock Location for managing Stock Locations,
Sales Order for managing Sales Orders,
Retail Catalog manages Retail Products (aggregate of product, price and stock data).
Fulfillment Order for managing Fulfillment Orders, Shipment Orders, Shipments (bounded context).
One can of course argue, that in different domains, an order means sth. different. However, prefixing the entities with the domain (bounded context) name is widely used: Purchase Order, Sales Order, Fulfillment Order, Shipment Order.
Technical services & abbreviations
Code names are widely used for technical services, appliances and libraries (Nakadi, buku, bubuku, spilo), which is perfectly fine in my point of view. Other examples exist though (Exception monitor, Deploy Control).
Smart abbreviations like Cuxy for CUstomer proXY should be allowed for technical components like caches, tools.
Suggestion for the guidelines
Service names (and thus their public URLs)
Must: Service name is closely related to the entities, aggregate or bounded context that they manage (i.e. Fulfillment Order, Sales Order, Stock Location).
Must: Use code names internally, don't expose them to clients.
Could: Use code names for technical infrastructure components (like Nakadi).
/cc: @codekultur https://github.com/codekultur @tfrauenstein https://github.com/tfrauenstein
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/zalando/restful-api-guidelines/issues/132, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPNRuRBE8wwN2o6YOX1Hm42gdKt4bhEks5qlBqcgaJpZM4JwcdW.


Gently notify user if pickle file is older than config file, and pickle requested.

This should be fixed.

Closing as its a stale merge.


Exposes lastEvaluatedKey in the scan client function

Overloads the scan client function with an extra parameter:
lastEvaluatedKey
It also returns a stream with a tuple of the lastEvaluatedKey and the rows.
This is useful to use when you want to checkpoint and in case of a failure while scanning restart on the lastEvaluatedKey
Pending:

[ ] Add tests for the scan API operations that lack tests

Thank you for the PR and sorry for late reply, I was completely offline for a long break. It would be great to have some tests for the new overloaded method as well.

Hope you had a nice break! One small comment for you to reply and I will add those tests after, depending on your response :)


Selecting all text causes it to go inside br

Selecting all text causes it to go inside br

Now applying style causes br to dissapear as of 6616da448224e0d392c96ac0fb13442baa65d3d2

Resolved by reverting back to whitespace as of 4c761119b2ed316dfa72ed6221159d2206332730


Adding automated test file modified times

Motivation and Context

Showing the time an assignment's automated test file was submitted in the test manager, so that users know when  test files were modified (similar to files submitted to an assignment)
Your Changes

Description:
I added a submitted_date key to the file_data hash rendered by populate_autotest_manager in automated_tests_controller.rb. I added a check to make sure the files being uploaded existed, since the tests do not create real files.
Type of change (select all that apply):

[x] New feature (non-breaking change which adds functionality)

Testing

I tested my changes in the UI, using multiple languages and time zones. I also ran rspec on automated_tests_controller_spec.
Questions and Comments (if applicable)

I still need to update this so that the time uploaded is in the correct time zone.
Checklist

[x] I have performed a self-review of my own code.
[x] I have fixed any Hound bot comments.
[x] I have verified that the TravisCI tests have passed.
[x] I have reviewed the test coverage changes reported on Coveralls.

Required documentation changes (if applicable)

@TheXanMan321 good work! I reviewed the coveralls check in this case, it's okay (I think it looks lower because this branch isn't up to date with master).


Track payments for dues or events

A payment can be associated with either an event (i.e. for a trip) or due(s) for a specific semester(s).
Users may enter cash or check transactions directly into the application. Card-present transactions will be routed through the Square Point of Sale application on the user's mobile device.
Self-service online payments can be implemented using the Square checkout page functionality to minimize the amount of UI work required here.

Split to #148, #149


Restore-DbaDatabase not working right

I am trying to restore database in SQL server 2016(I have got SSMS 17.9 installed) using dbatools version 0.9.773.
Environment variable i set to dabtools that has got SMO version 14.0...
I am getting below error
WARNING: [08:31:58][Restore-DbaDatabase] Failure | [A]Microsoft.SqlServer.Management.Smo.RelocateFile cannot be cast to [B]Microsoft.SqlServer.Management.Smo.RelocateFile. Type A originates from 'Microsoft.SqlS
erver.SmoExtended, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' in the context 'Default' at location 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoExtended\<IP_ADDRESS>__89845dcd8080cc
91\Microsoft.SqlServer.SmoExtended.dll'. Type B originates from 'Microsoft.SqlServer.SmoExtended, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91' in the context 'LoadFrom' at location 'C:
Program Files\WindowsPowerShell\Modules\dbatools\0.9.773\bin\smo\Microsoft.SqlServer.SmoExtended.dll'.
I tried to load SMO assembly manually in my script(below command) but no luck
[Reflection.Assembly]::Load("Microsoft.SqlServer.Smo, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=89845dcd8080cc91")
Not sure what I should do to by pass GAC assembly or get latest version that is 14.0...
Thanks for your work and support to the community.

PowerShell does not support loading multiple versions of assemblies in the same session. You will have to remove that from your script.
Our module loads SMO utilizing the version of SMO we package in our module.

hey @MuruArumugam , this is something we'd like to follow up on as we just updated our versions of SMO but we cannot accept this issue without the template info. Please recreate the issue with the requested information in the bug issue template https://github.com/sqlcollaborative/dbatools/issues/new?assignees=&labels=&template=Bug_Report.md&title=[Bug]


Samples do not work due to IIS InProcess

Since InProcess became the default mode many of the samples in this repo have stopped working with 500.0 - ANCM In-Process Handler Load Failure. Adding <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel> to their csproj makes them work again.
Some of these projects don't have a reference to Microsoft.AspNetCore.Server.IIS nor call UseIIS(), but adding those is not enough.
The NativeIISSample is the only one I've seen that still works and that's because it heavily customized the launch settings.
Ideally any customizations needed to make InProcess work in this repo would be consolidated to some shared source dependency we could reference from all of the samples.
@pakrym @jkotalik

Some reference samples:

Security.sln' CookieSample
Middleware.sln's SessionSample, StaticFileSample

When fixing up the dependencies most samples can move from individual references to pulling in the Microsoft.AspNetCore metapackage as there's no more repo layering to worry about. I've already done that for some of the Security samples.

Let's make the samples use out-of-proc because it's the simplest option.

Boooooooo!

I don't believe it would be much work at all. It should just be adding an additional props file to each sample.

@jkotalik - from my understanding during triage it was quite a bit more work to get the native assets to work as well. But either way, not as simple as using in-proc, and for no clear gain.


Work/1.0.0/room update

added room apis, room views, api tests
updated views

send to work/1.0.0/main


Cannot press Escape to cancel entering a command or search input.

When you press : to enter a command, or / or ? to enter a search input, you cannot press escape to cancel the operation. You must hit Enter to submit your input and get back to the normal viewing experience.
jless uses Rustyline for the readline-esque functionality. I'm unsure if this is simply something that's not supported by Rustyline, or if my input code is doing something weird to mask the escapes.

installed 0.7.1 today, using the ':' key to enter a command does not work at all (no response) on a larger file (~17M), and trying to search with / or ? quits outright. Is there a build I could try with debug output?


Add good full coverage beacon API tests

What is your question?
Current tests for the beacon API are of sub-optimal quality:

Very limited coverage
No assurance that all and future new endpoints are tested
Require import stubbing
Extensive use of brittle stubs: which require big diffs when modifying unrelated cost.

In my subjective opinion the current test suite has a very high cost of maintenance with very little return in ensuring the API is correct.
Proposed solution
Proper tests for a the beacon API should:

Have full coverage
Ensure programmatically that all endpoints current and future are tested
Be tested against a full BeaconChain instance without stubbing and with real data. We are already doing this for BeaconChain validation and such data is extremely fast to produce and to run tests against.

More disabled tests
https://github.com/ChainSafe/lodestar/blob/5d086b58a20f57c69f1d2cc90d5bf785f851f535/packages/lodestar/test/unit/api/impl/beacon/state/fork.test.ts#L9-L10
https://github.com/ChainSafe/lodestar/blob/5d086b58a20f57c69f1d2cc90d5bf785f851f535/packages/lodestar/test/unit/api/impl/beacon/pool/pool.test.ts#L25-L26

We now have oapi schema compliance tests that ensure validity of request/response data shapes and proper support of headers, status codes, etc. This is a good halfway solution.
Closing this for now


Functional programming guide

A bare-bones article on functional programming, ideally to be expanded on later.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Will do.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


refactor: signal handling functions when verbose is enabled

Motivation
Just a small code improvement to avoid headaches.
The verbose flag :point_down: was introduced by https://github.com/falcosecurity/falco/pull/2249 and that's fine.
https://github.com/falcosecurity/falco/blob/62abefddf69b12f49ecedac39c9cfd321cb739a3/userspace/falco/application.cpp#L101-L110
However, the verbose flag is not semantically connected to the reason the log message is saying.
Feature
Pass the reason message as an argument in order to make those functions completely generic.
Alternatives

Additional context
/assign @jasondellaluce
/milestone 0.34.0

/milestone 0.35.0


[mgmt] servicelinker release

https://github.com/Azure/sdk-release-request/issues/5549

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-servicelinker


fix(meta): use per table mce and safe epoch in metadata backup

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
After #17161, batch query over metadata backup won't work correctly, because it try_get_hummock_version (find a queryable backup) using global safe_epoch and MCE, while validate_safe_epoch using per table safe_epoch and MCE.
This PR fixes it by storing and using per table safe_epoch and MCE.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

FYI, I have to revert the adoption of the macro introduced in #17225 when restoring a backup, because insertion requires a specific order to satisfy foreign key constraints. @yezizp2012