AArch64 assembly pack: authenticate return addresses.

ARMv8.3 adds pointer authentication extension, which in this case allows
to ensure that, when offloaded to stack, return address is same at return
as at entry to the subroutine. The new instructions are nops on processors
that don't implement the extension, so that the vetification is backward
compatible.

Merged to master
9a18aae5f21efc59da8b697ad67d5d37b95ab322 AArch64 assembly pack: authenticate return addresses.

I'm thinking this should be cherry-picked to 1.1.1.  What say you, @kroeckx, @dot-asm?

This PR is impossible to read. Did people really check that every digit in each .inst line is exactly right? Given that this is PerlAsm, it would be better to nice to see the PerlAsm machinery used to make this easier to read.

Well, what can I say...  after years of exposure, I implicitly trust @dot-asm's knowledge and attention to detail.  But, since you asked, I went finding https://static.docs.arm.com/ddi0596/a/DDI_0596_ARM_a64_instruction_set_architecture.pdf, and this is what it tells me:
PACIASP: 1101 0101 0000 0011 0010 0011 0011 1111
AUTIASP: 1101 0101 0000 0011 0010 0011 1011 1111
In hex, that's D503233F and D50323BF, which are the two instruction numbers that are added.  So yeah, the comments on those lines are correct.

Regarding the PerlAsm machinery, it's different for different architectures.  Some architectures have make enormous use of the AUTOLOAD feature, while others are more direct assembler with just a little bit of translation wrapping.  It depends on when the particular architecture support started, and how different ideas affected this over time.  Gotta remember that we're talking 20+ years, and a lot happened over time.
Of course, one might want to argue that some of the architectures should be rewritten for better consistency, but well, that's a huge effort, and not top priority.

What I mean is that in text like D503233F there could very easily be a typo that we wouldn't notice. In C code we'd generally not accept repeating a constant's value over and over like this; we'd insist on using a symbolic name of some sort. IMO it would be better if the assembly code used symbol names in the same way.

The ARM perlasm driver is one of the newer ones that looks like a translate filter. It should certainly be possible to implement encoders for those two instructions. The x86_64 driver is of a similar style and does much more complex encoding.

(And, of course, it's possible for an old-style perlasm driver like 32-bit x86 to polyfill instructions too. The fact that the machinery is different for different architectures is orthogonal to this question.)

The reason for why it's encoded directly is that so far intention with ARM modules was to not require arm-xlate.pl. I mean if there is arm-xlate.pl, then it's called, and if there is none, then just go ahead emitting code unfiltered. Naturally without arm-xlate.pl you can't generate code for iOS (or Windows), only Linux, but majority [who would be interested to reuse code elsewhere] is not interested in anything else anyway. Which is the "circular" reason for making arm-xlate.pl optional... Of course, you can say "reconsider"... Shall we say more people ask, more likely it happens...

Meanwhile, I made an executive decision to cherry-pick to 1.1.1 as well, under the assumption that if 1.1.1 is built on a newer version ARM machine, there may be trouble without this.
2cf7fd698ec1375421f91338ff8a44e7da5238b6 AArch64 assembly pack: authenticate return addresses.

Regarding direct encoding of some instructions vs symbolic encoding, I suggest someone raise an issue.  Maybe I'm dreaming this up, but I vaguely recall having seen similar techniques being used in other assembler modules.


Setup travis builds for castxml epic version 1

Due to the introduction of the new xml format version in castxml, which can be enabled by using the --castxml-output=1 flag, the buildbots need to be upgraded.
For this we need:

New castxml binaries for OS X, Linux and Windows.
Make all the castxml tests run twice on travis and appveyor: once with and without the new flag. The builds will run twice as long, but this is still acceptable (around 5 to 6 min).

@thewtex Would you have time to build new CastXML binaries? There is nothing urgent but ITK could also benefit from the upgrade. No real new features for ITK, but there were some small patches lately.
I was also thinking if we should use circle/travis to get the binaries built, but I guess you have some setup locally at Kitware for building this.

@iMichka CastXML builds are currently configured here:
https://github.com/thewtex/CastXMLSuperbuild
It would be nice to move this to the CastXML or gccxml GitHub organizations. It currently has a Linux build on CircleCI, and I just grab the artifact and upload it. It would be nice to have Travis and Appveyor although the LLVM build time might be a challenge -- I have not tried.
It will be at least a couple of weeks before I can get to the updates.

Thanks Matt. No rush. I have a local build, so I can continue playing around the time being. Adding the new feature will take some time anyway.
I am +1 on moving this project. It would better fit under the CastXML organisation.
For travis, we could use their mac builds, and the llvm bottled by homebrew. That should be quite easy to do and no llvm will need to be done.
For the windows build, it may be more tricky.

Closing here. Tests are running with both the old and new castxml versions.
@thewtex Thanks for building new releases and adding them to ITK too. I was able to build the linux binaries using your docker (before you built them for ITK), it worked pretty well.

:+1:


:+1: Add send keys helper

keymap is a helper that send key sequences synchronously.
Example:
import { Denops } from "../mod.ts";
import * as fn from "../function/mod.ts";
import { send } from "./keymap.ts";
import { exprQuote as q } from "./expr_string.ts";

export async function main(denops: Denops): Promise<void> {
  denops.dispatcher = {
    send: async (): Promise<void> => {
      // Let's say the current buffer is "foo".
      await send(denops, "bar");
      // The buffer has been changed!
      // "foobar"
      console.log(await fn.getline(denops, "."));

      // Send special keys.
      await send(denops, [
        q`${"\\<BS>".repeat(6)}`,
        "baz",
      ]);
      // "baz"
      console.log(await fn.getline(denops, "."));

      // Send remaped keys.
      await send(denops, { keys: q`\<C-l>`, remap: true });
      // "bazsend"
      console.log(await fn.getline(denops, "."));
    },
  };
  await denops.cmd(`inoremap <C-k> <Cmd>call denops#notify('${denops.name}', 'send', [])<CR>`);
  await denops.cmd(`inoremap <C-l> send`);
}

Summary by CodeRabbit

New Features

Introduced a new key mapping utility with synchronous key sequence sending, including support for special and remapped keys.

Tests

Added comprehensive tests for the new key mapping functionality, ensuring reliability and correctness of the feature.

Documentation

Updated documentation to include details on the new key mapping types and utility functions.

@coderabbitai review


Add project_name for goreleaser

When CI is upgraded to goreleaser v1.21, our publish steps fail as the project_name could not be formulated by GoReleaser. This PR explicitly sets the project_name.
Note, for faster feedback loop, this PR should be merged first and a follow-up PR in pu/ci-mgmt will be created.
I've also triggered the CI workflow for this commit to test that it works and it is passing: https://github.com/pulumi/pulumi-gcp/actions/runs/6313530404/job/17142821989
Fixes: #1217

Guess we're updating ci-mgmt afterward.


Private instructions on Events not rendered using Markdown

Describe the bug
The private instructions on events are not rendered using Markdown, as far as I can tell, or they don't match the formatting of the input.
To Reproduce

Create an event.
Add private instructions with line spaces and more.
See the published page.

Expected behavior
It should use Markdown, I believe? Or a WISYWIG.
Screenshots

Desktop (please complete the following information):

OS: OSX
Browser: Firefox
Version: 99.0

Triage Template (core team only)
This template is for members of the team to triage for prioritisation. For more guidance see https://www.loom.com/share/369ab467fbc64dec848085d38ff57ca0:
P1 high frequency, high impact
P2 low frequency, high impact
P3 high frequency, low impact
P4 low frequency, low impact
Examples of high impact - a problem affects users during an essential process (expenses and payments > onboarding and registration > contributing) with no workaround.
High frequency - >10% of users affected (measured as a proportion of total potential users for this case).

From what I can see in the code, I don't think this field has ever been treated as something else as simple text (no HTML, no markdown). Did something in the interface made you think otherwise, or is this a feature request?

Right!
Something that made me think it wasn't text was that it supported newlines in the UI, but it doesn't support them in rendering. Perhaps a good halfway point would be to maintain newlines entered in the field in the display?

Right!
Something that made me think it wasn't text was that it supported newlines in the UI, but it doesn't support them in rendering. Perhaps a good halfway point would be to maintain newlines entered in the field in the display?

Absolutely, if it has new lines in the input we must make sure that they're preserved in the frontend and in the email (ticket confirmed)

Yep.
Might be worth splitting this into two issues - that newlines aren't preserved I interpret as a bug. Having Markdown enabled is more of a feature request, and may be an issue for email rendering and security, I think.

Yep.
Might be worth splitting this into two issues - that newlines aren't preserved I interpret as a bug. Having Markdown enabled is more of a feature request, and may be an issue for email rendering and security, I think.

Indeed. For consistency, I'd argue that the feature request should be about having rich text for this field - not markdown - with the WYSIWYG editor that we use in other places. We moved away from markdown a while back because many of our users are non-technical and don't know about this format.

Rich text sounds good to me. I've renamed. Would you prefer I re-add the bug label, or make this one about having a WISYWIG?

Rich text sounds good to me. I've renamed. Would you prefer I re-add the bug label, or make this one about having a WISYWIG?

Both work, as you prefer :-)

I've received more feedback on this from attendees of the recent @Open-Source-Collective call. The private instructions which included Zoom instructions was not easy for users to navigate via email.


Can't connect from Android app

Can't connect to server from android app
Environment Information

Device Name:Xperia5Ⅳ
OS Version:Android13
Mattermost App Version:2.4.0
Mattermost Server Version:7.10.2

Hi @YusukeMasuda36, what error are you seeing?

Thank you @amyblais
Fixed by restarting the server.


Smartcard logon support

Does this client support smartcard logon to remote servers?

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

ID: acc42a8f-2623-4352-7cc4-70f0f61e9d89
Version Independent ID: 97d8b54b-5e7d-098b-4fb7-e8f6e0b30389
Content: Get started with the Windows Store client
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/windows.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @lizap
Microsoft Alias: elizapo

Hello @paroola. GitHub issues for this repo are for reporting problems with our documentation.  Please open a support ticket or post your question on Microsoft Q&A.


Loading .env file from within hubot

Hubot currently uses environment variables to configure the hubot instance.  bootstrap files also show the ability to load from .env.  Example:
# Load environment specific environment variables
if [ -f .env ]; then
  source .env
fi

This works as long as the .env file has export in front of all the variables.
export HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx
Common node.js practice is to use modules like dotenv or node-env-file to load variables from .env in the format
HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx
But that format does not work with the source .env method above.
Adding node-env-file to bin/hubot would resolve this issue and be compatible with current functionality
env      = require 'node-env-file'
env('.env', {verbose: false, raise: false})

This will

only load items in .ssh that do not have export in front of them ( so will not conflict with existing .env files being sourced )
not overwrite any environment variables that are already populated via the environment

Tests
Gets read
.env
HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx

Results
# bin/hubot -a slack
[Mon Mar 21 2016 10:00:41 GMT-0700 (PDT)] INFO Connecting...
[Mon Mar 21 2016 10:00:42 GMT-0700 (PDT)] INFO Logged in as hubot of xxxxx, but not yet connected
[Mon Mar 21 2016 10:00:43 GMT-0700 (PDT)] INFO Slack client now connected

Not read if export
.env
export HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx

Results
# bin/hubot -a slack
[Mon Mar 21 2016 10:03:00 GMT-0700 (PDT)] ERROR No services token provided to Hubot

Will not overwrite
bin/hubot
export HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx
exec node_modules/.bin/hubot --name "hubot" --alias "!"  "$@"

.env
HUBOT_SLACK_TOKEN=this-is-a-bad-token

Results
# bin/hubot -a slack
HUBOT_SLACK_TOKEN
[Mon Mar 21 2016 09:54:08 GMT-0700 (PDT)] INFO Connecting...
[Mon Mar 21 2016 09:54:10 GMT-0700 (PDT)] INFO Logged in as hubot of xxxxxx, but not yet connected
[Mon Mar 21 2016 09:54:10 GMT-0700 (PDT)] INFO Slack client now connected

Works if .env is not present and no error messages
bin/hubot
export HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx
exec node_modules/.bin/hubot --name "hubot" --alias "!"  "$@"

Results
# ls -l .env
ls: .env: No such file or directory
# bin/hubot -a slack
[Mon Mar 21 2016 10:08:07 GMT-0700 (PDT)] INFO Connecting...
[Mon Mar 21 2016 10:08:09 GMT-0700 (PDT)] INFO Logged in as hubot of xxxxxx, but not yet connected
[Mon Mar 21 2016 10:08:09 GMT-0700 (PDT)] INFO Slack client now connected

Hi.
I'm facing a "ERROR No services token provided to Hubot" error while running Hubot on my Windows machine.
I've tried including both of the following (separately) in the bin\hubot file:
export HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx
HUBOT_SLACK_TOKEN=xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxx
A few days ago, using the first version got it working. But now it does not work anymore.
Things I did: installed yo, installed generator-hubot, ran yo hubot, added the above line to bin\hubot, then tried running ".\bin\hubot -a slack"
Any help would be appreciated. Thank you.

Hi.
I fixed it.
For anybody who's fixing the same problem:
Open up PowerShell and set environment variables like so:
[Environment]::SetEnvironmentVariable("HUBOT_ADAPTER", "slack", "Machine")
[Environment]::SetEnvironmentVariable("HUBOT_SLACK_TOKEN", "xoxb-xxx-xxx"", "Machine")
Did the job.


Add license

I am trying to evaluate for testing. Can you please add the license to this project?

OK. I will add the license soon.


Remove hipchat integration

Hipchat is being discontinued from Feb 15th, 2019 and is acquired by Slack.
https://www.cnet.com/news/slack-is-buying-rival-hipchat-only-to-kill-it-off/

Looks good to me. Thanks :100: :+1:


Fix component registration

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

// @leecalcote

Thank you. FYI - https://github.com/meshery/meshery-nginx-sm/commit/094c8edbbb142aefb6484a5bc4a7e16946fd15dc


Migrating RNRF v3 to RNRF v4

I am using airbnb google-maps in my project & it act as a base component of my app in v3 of RNRF I have used nested Scene code below & it was working fine .While upgrading to V4 it is not working can anyone here help me out .how to do it ?
<Drawer
        ref={ref => {
          this._drawer = ref;
        }}
        type="overlay"
        content={<SideBar navigator={this._navigator} />}
      >
        <StatusBar backgroundColor={statusBarColor} />
        <RouterWithRedux>
          <Scene key="root" hideNavBar>

            <Scene
              key="StartupService"
              component={StartupService}
              hideNavBar
              initial={this.props.JwtAccessToken}
            />

            <Scene key="rootView" component={RootView}>
              <Scene key="home"  component={Home} />
              <Scene key="confirm" component={Confirm} />
              <Scene key="Booked" component={Booked} />
            </Scene>

            <Scene key="sideBar" component={SideBar} />
            <Scene key="history" component={History} />
          </Scene>
        </RouterWithRedux>
      </Drawer>

here the rootView contain the map & the other component are screen on top of rootView
how to do that in V4

Please check docs/examples, there are some breaking changes.

@aksonov  i am not able to figureOut any work around .
As the rootView contain react-native-maps that is common in the other screen (home, confirm & booked) . any lead will be appreciated
v3.38 is laggy with RN V48.x thats why i need to upgrade the RNRF version .


Update comment for validator keys 5 to 7

This is to match the new keys in #1248 .

That doesn't sound right. Are you sure the issue wasn't on the infra side ?

That doesn't sound right. Are you sure the issue wasn't on the infra side ?

This is the comments inside the WK key pairs file. Looks like I did not update the comments there on the last update to a few keys.

That doesn't sound right. Are you sure the issue wasn't on the infra side ?

This is the comments inside the WK key pairs file. Looks like I did not update the comments there on the last update to a few keys.

Oh there is more though. Now I am also not sure. Will take a look.

After a discussion with @hewison-chris , the keys in the agora side are correct. The keys in the infrastructure have to be updated.


Update

I have a problem:
When I update list I do that
public void update(List<?> newData)  {
    notifyParentItemRangeRemoved(0, oldData.size());
    oldData.clear();
    oldData.addAll(newData);
    notifyParentItemRangeInserted(0, newData.size());
}

But when I do it I have flicker.
Can you help me and say the right way do data update ?
If I no use
notifyParentItemRangeRemoved(0, oldData.size());
I did not have flicker, but I have duplication

Just clear the list first. Add the new data and call notifydatasetchanged. Giv me a feedback if it works.

@pasha656 another option is to use [swapAdapter](https://developer.android.com/reference/android/support/v7/widget/RecyclerView.html#swapAdapter(android.support.v7.widget.RecyclerView.Adapter, boolean))
The best option is currently not available but being tracked in #89


Disable jvm dns cache in java11 in dockerfile-dev

We install java11 in dev image but didn't disable jvm dns cache for it. This PR fixes this.

why needs to disable?

@LuQQiu  It's for the HA in k8s. With the cache on, clients can't find the correct master address if the cluster elects a new master. The original PR that added this line is: https://github.com/Alluxio/alluxio/pull/9452

alluxio-bot, merge this please

alluxio-bot, merge this please


Command not interpolate user variables

Hi,
I've trying to use host-command integrated with user variables directly on attribute command, as below:
  provisioners: [
    {
      "type":   "host-command",
      "commands": [
        "ansible-playbook -i ansible/providers/aws/plugins/ec2.py --private-key={{ user `aws_source_ssh_key_path` }} --user={{ user `aws_source_ssh_user` }} -e app_hosts=packer_ami_build"
      ]
    }
  ]

But it fails:
$ packer validate -var aws_source_key_path=<a path> -var aws_source_ssh_user=<a user>  recipe.json

* Error processing commands[0]: template: tpl0:1:74: executing "tpl0" at <user `aws_source_ssh...>: error calling user: unknown user var: aws_source_ssh_key_path
Something failed while executing. Check your recipe and run again.

All variables are not recognized by Packer.
Thank you!

Hi! Thanks for bringing this up. I may have to take some time to investigate this, if it's alright. I cannot recall off the top of my head, but I think the packer shell provisioner (which this plugin is largely based off of) doesn't treat shell commands as configuration templates, so the interpolation might not work. I'll do some tinkering with this to see if it's possible to support that behavior.


Upgraded react to 0.14.3

also add production globals to webpack config to reduce bundle size by 10%, not bad!

This seems to work just fine:


How to know next major and minor versions of a vulnerable dependancy?

I am using dependancy-scan cli to scan a war for vulnerabilities. When we are working with maven plugin I am able to see the available versions for all dependancies but cli is not producing the file containing available versions, Next Major and Minor versions etc.. Could somebody help me in this issue?

The file containing the available versions is not from the dependency-check plugin. That is generated by the versions:dependency-updates-report.
Just using the CLI - I don't know of an automated way to get the next major/minor versions available.


Convert truncated quote currency value to float for marketBuy

Description
Convert truncated quote currency value to float for marketBuy
Fixes #248
Type of change
Please make your selection.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change requires a new dependency
[ ] Code Maintainability / comments
[ ] Code Refactoring / future-proofing

How Has This Been Tested?
Manual runs.
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added pytest unit tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Wouldn't be better to just remove the truncate ?
If the bot wants to buy BTC, the precision should be more than 2.

Wouldn't be better to just remove the truncate ?
If the bot wants to buy BTC, the precision should be more than 2.

I'd say yes, but I don't know enough. I'd be fine with it, let's wait for @whittlem - for some reason, truncate() was and is there, the problem is it used to return float when called like this, now it doesn't. Therefore, yes, I'd say it's safe to remove, but I don't know for sure.

Hi guys, do you know when this broken? Just to know which version isn't affected.


Endpoint for doing liveness probes

For our deployment strategy, it would be benefitial  to have an unencrypted endpoint for doing liveness proves.

Is this issue still valid? Or have you handled it already somehow?

Closing this one due to no feedback.


Replace to use org.messaginghub:pooled-jms in JMS Pooled Kamelet

Well io.quarkiverse.messaginghub:quarkus-pooled-jms is a extension for quarkus but here in this kamelet I think only  org.messaginghub:pooled-jms is needed for pooledFactoryBean.

I don't remember the reason but please test the update through camel-jbamg

Hmm, can you provide the command I need to test by camel-jbang?

I meant to say if you can test the kamelet with camel-jbang or what you're using

Yeah, I run a jbang example from https://github.com/apache/camel-kamelets-examples/tree/main/jbang/timer-activemq-artemis. But how to use the 4.8.0-SNAPSHOT of org.apache.camel.kamelets:camel-kamelet ?
jbang -Dcamel.jbang.version=4.8.0-SNAPSHOT camel@apache/camel run artemis-log.camel.yaml --kamelets-version=4.8.0-SNAPSHOT

[jbang] [WARN] Detected missing or out-of-date dependencies in cache.
[jbang] Resolving dependencies...
[jbang]    org.apache.camel:camel-bom:4.8.0-SNAPSHOT@pom
[jbang]    org.apache.camel:camel-jbang-core:4.8.0-SNAPSHOT
[jbang]    org.apache.camel.kamelets:camel-kamelets:4.7.0
[jbang] Dependencies resolved
...

@davsclaus @oscerd it's still 4.7.0 even I add  --kamelets-version=4.8.0-SNAPSHOT. any hint?

kamelets JAR is loaded by jbang, so you cannot use --kamelets-version.
Use -Dcamel-kamelets.version=xxx or better just edit the .java file in your ~/.jbang cache folder

Thanks a lot @davsclaus - Now I can run the example perfectly with the jbang -Dcamel-kamelets.version=4.8.0-SNAPSHOT

You can also use --local-kamelet-dir param

Thanks @oscerd - yeah, it works with --local-kamelet-dir as well.

Just curious, is it possible to use different artifacts based on runtime in kamelet?
I'm asking because if we run this kamelt in a quarkus runtime, by adding quarkus-pooled-jms and quarkua-artemis, there is also no need to create a pooledFactoryBean.

No, it's not possible, but you can create your own Kamelet and use that directly. The aim of Kamelets is creating a building block to make possible for end-users to create their own catalog.

Hmm, get it. Is there any label can be used to mark it only used in a specific runtime?


No background when pointer is selected

Codecov Report

Merging #563 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #563   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         945    945
=====================================
  Hits          945    945

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 5101c1a...57821aa. Read the comment docs.

Thanks for the pull request. However, I don't understand what it does... Can you provide a description and a demo?


VoTT is deprecated

Model Builder is currently still in preview, which is why the documentation is most likely not yet complete.
However, this documentation uses the VoTT software, which can be downloaded from GitHub. However, the repo and this software are outdated and archived. What @wbreza announced.
Since Model Builder is a new product, it would be nice if outdated examples are not used before the release.
Is there no alternative to this program that proves the same utility?

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

ID: 63a4f3b7-a2a6-760a-534b-22788ba77b5c
Version Independent ID: 1bee7901-164f-d9a7-9e7b-fd0ba55ad42e
Content: Tutorial: Detect objects in images with Model Builder - ML.NET
Content Source: docs/machine-learning/tutorials/object-detection-model-builder.md
Product: dotnet-ml
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

Hi @21r8390
Thanks for your questions.

Model Builder is currently still in preview, which is why the documentation is most likely not yet complete.

Would you be able to add more details on what's missing from the documentation?

Is there no alternative to this program that proves the same utility?

Although we are aware that VoTT is archived and no longer actively maintained, for the Model Builder use case, the existing functionality makes the process of labeling / tagging images easier while offering a diverse set of export formats. That being said, we're open to feedback to understand whether the current solution is either not solving your problems or getting in the way. Is there any specific functionality currently missing from your workflow that VoTT doesn't address?

Thank you for the reply.

Would you be able to add more details on what's missing from the documentation?

I personally find that the documentation is complete and very well written. However, the documentation states that Model Builder is currently in preview, so I wanted to note that.
VoTT fulfills all the tasks and requirements needed for this tutorial and beyond. However, from the user / beginner point of view, it is unpleasant to be greeted with the message that the product is archived.
It would be more pleasant if this message would not come or some hint with explanation is in the doc. This way people would know that the program still has all the functions and can be safely used.

Is there something else that is a good replacement of VoTT that is currently actively maintained and improved for such things? It feels strange to follow and use VoTT if it's archived.

@luisquintanilla I agree with the comments above.  I am just getting started with some Vision AI through the ML.NET package and also found references to VOTT.  If the tool is no longer being maintained (including security fixes as one fork is attempting to do) it will be a challenge to communicate to my corporate security team that this tool is ok to use.
Further, with each passing day, the fact that this tool is not being maintained means that critical updates just to keep it running as dependencies change won't be occurring.
This solution (https://github.com/SysCV/nutsh) looks like an excellent replacement tool from the perspective of quickly developing custom datasets, however, this tool is not yet supported on Windows.
It is quite clear to me that for the further development and support of custom Vision AI solutions using the Microsoft and Azure tool suite will require either endorsement and support of some other tool, or reconsideration of the non-supported situation with VOTT.
Thanks for letting us bend your ear a bit. :-)

Great ear bending as above, and it seems no response for 10 months? I have been using ML.NET now on many projects and before I was doing my image detection without any transfer learning using object categorisation that worked really well, but my new use case requires very fine identification of objects in images so I think I need object detection. VoTT looks like a great tool, it seems that Microsoft has decided that this tool is too good to be just free, as has happened a lot in the past unfortunately, LightSwitch, ISpy etc, but I really love how you have embraced open source Azure Functions, but again as serverless is only still a very small part of the web still again that seems like a strategic direction. So can the managers have a rethink, or are you just planning an even better tool and my suspicions are completely off track!!


Create a non-interactive (ni) flag

This is quite niche, but will be very useful for headless and on-boot execution.

Added in https://github.com/gstavrinos/ros-ez/pull/40/commits/fc9c0c439b4131afae4ee02517c8ac7f2fa9b598


etcd go client when get recursive return nothing

go client get method
func (k *httpKeysAPI) Get(ctx context.Context, key string, opts *GetOptions) (*Response, error) {
	act := &getAction{
		Prefix: k.prefix,
		Key:    key,
	}

	if opts != nil {
		act.Recursive = opts.Recursive
		act.Sorted = opts.Sort
		act.Quorum = opts.Quorum
	}

	resp, body, err := k.client.Do(ctx, act)
	if err != nil {
		return nil, err
	}

	return unmarshalHTTPResponse(resp.StatusCode, resp.Header, body)
}

returns empty string on the Value when use on recursive directories

@tweakmy
It works for me. etcdctl uses the same API, and I set the Recursive true.
./etcdctl set /a/b "Goodbye world"

./etcdctl get /a/b
Goodbye world

What is your use case?
If you want to list sub-directories recursively, you can do:
https://github.com/coreos/etcd/tree/master/etcdctl#listing-a-directory
Thanks,

I would like grab all values in the subdirectory
./etcdctl set /a/b "a sub b"
./etcdctl set /a/c "a sub c"
ideally should give
./etcdctl get --recursive /a
/a/b/ "a sub b"
/a/c/ "a sub c"
etcdctl get does not support recursive at the moment
NAME:
   ./bin/etcdctl get - retrieve the value of a key

USAGE:
   ./bin/etcdctl get [command options] <key>

OPTIONS:
   --sort	returns result in sorted order
   --quorum	require quorum for get request

However the curl implementation and response is what I am expecting
{"action":"get","node":{"dir":true,"nodes":[{"key":"/static","dir":true,"nodes":[{"key":"/static/binary","dir":true,"nodes":[{"key":"/static/binary/grp1obj2","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/0","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/0/value","value":"1","modifiedIndex":439,"createdIndex":439},{"key":"/static/binary/grp1obj2/0/eventVariantion","value":"22","modifiedIndex":440,"createdIndex":440}],"modifiedIndex":423,"createdIndex":423},{"key":"/static/binary/grp1obj2/1","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/1/value","value":"1","modifiedIndex":441,"createdIndex":441},{"key":"/static/binary/grp1obj2/1/eventVariantion","value":"22","modifiedIndex":442,"createdIndex":442}],"modifiedIndex":426,"createdIndex":426},{"key":"/static/binary/grp1obj2/2","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/2/value","value":"1","modifiedIndex":443,"createdIndex":443},{"key":"/static/binary/grp1obj2/2/eventVariantion","value":"22","modifiedIndex":444,"createdIndex":444}],"modifiedIndex":429,"createdIndex":429},{"key":"/static/binary/grp1obj2/3","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/3/eventVariantion","value":"22","modifiedIndex":446,"createdIndex":446},{"key":"/static/binary/grp1obj2/3/value","value":"1","modifiedIndex":445,"createdIndex":445}],"modifiedIndex":432,"createdIndex":432},{"key":"/static/binary/grp1obj2/4","dir":true,"nodes":[{"key":"/static/binary/grp1obj2/4/value","value":"1","modifiedIndex":447,"createdIndex":447},{"key":"/static/binary/grp1obj2/4/eventVariantion","value":"22","modifiedIndex":448,"createdIndex":448}],"modifiedIndex":435,"createdIndex":435}],"modifiedIndex":423,"createdIndex":423}],"modifiedIndex":423,"createdIndex":423}],"modifiedIndex":423,"createdIndex":423}]}}

It is only how it should be presented in the keyapi and how I could use it programmatically. Of course, I could implement it myself but because the getoptions supports recursive, I thought I just everyone know.

--recursive flag  and  ls command will output all keys and values for a given path:
    --recursive  returns all values for key and child keys

@tweakmy I think you are close. If you want to do programmatically, you can do the same thing as
https://github.com/coreos/etcd/blob/master/etcdctl/command/ls_command.go#L40-L58.
And if you want to use etcdctl, you should use ls command.

./bin/etcdctl ls --recursive /static
/static/binary
/static/binary/grp1obj2
/static/binary/grp1obj2/0
/static/binary/grp1obj2/0/value
/static/binary/grp1obj2/0/eventVariantion
/static/binary/grp1obj2/1
/static/binary/grp1obj2/1/eventVariantion
/static/binary/grp1obj2/1/value
/static/binary/grp1obj2/2
/static/binary/grp1obj2/2/value
/static/binary/grp1obj2/2/eventVariantion
/static/binary/grp1obj2/3
/static/binary/grp1obj2/3/value
/static/binary/grp1obj2/3/eventVariantion
/static/binary/grp1obj2/4
/static/binary/grp1obj2/4/value
/static/binary/grp1obj2/4/eventVariantion

I can confirm it only gives me the key
./bin/etcdctl get /static/binary/grp1obj2/0/value
1

I do need key and value because at a periodic time, I would like to 'get' key-value set

@tweakmy ls only lists the names. If you want the key-value listed at the same time, you have to use etcd/client. As @gyuho said, etcd/client should just work.

@tweakmy If you try etcd/client and it does not work for you, please reopen this. Thanks!

Thanks @gyuho


Get Python 3 tests running on Travis-CI (They pass locally)

Travis-CI does not have python 3 enabled.
If we can fix or work round this then Python 3 bindings can be tested by amending the run_tests script.

closed by PR #68


SLIM-898 bundle request for get profile generic data

This pull request makes the build fail.

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

All is well.


Fixed hyperlinks in Windows section of README

The links were written for Markdown but the document is RST.

Coverage remained the same at 82.494% when pulling 283ff083b21011bff8508ca1c34d6423f82fccc6 on readme-syntax-fix into a3cf1bb07985d008235dcfb9dde9cdb8bb89d78e on master.

Coverage remained the same at 82.494% when pulling 283ff083b21011bff8508ca1c34d6423f82fccc6 on readme-syntax-fix into a3cf1bb07985d008235dcfb9dde9cdb8bb89d78e on master.


Add Match method to Type interface

This PR is on top of #52 . So only last commit is to be reviewed. Once #52 is merged, I will rebase this PR
Added MatchWithNullability and MatchWithoutNullability methods on type interface. This method returns true if argument "t" is type compatible with this type otherwise it returns false
These two APIs are necessary considering Match behavior will differ based on function's nullability handling (MIRROR, DECLARED_OUTPUT, DISCRETE).
Nullability "MIRROR" and "DECLARED_OUTPUT" requires MatchWithoutNullability
Nullability "DISCRETE" will require MatchWithNullability
In follow up PR I will add Match method on FunctionVariant interface

Using reflect.TypeFor requires updating the module to go1.22 instead of go1.21, that's why the linter is failing most likely

I will un-draft once #52 is merged and is rebased for this PR


CSS rendered differently in production and development mode

When I send emails in development mode, the css is rendered perfectly in gmail.But, when I send the same email in production mode, the CSS gets broken in couple of places. I even tried rake:assets:precompile before sending the email. Stylesheet has been included in the HEAD section of mailer as <%= stylesheet_link_tag 'email/my_css' %> Is it a problem with a premailer or something that is to be configuerd for production mode. Am I missing something ?

So I use this gem for quite a while now and I have some issue that related. In email that I sent, I included image and sets its height in scss file. In development, everything great, image rendered with correct height. But in production, I can't get it right. I try resetting the app, the background job. I can't pinpoint the issue. Any suggestion?

Hard to understand without code. Mind showing some?

I have this image inside my email html

    <%= image_tag 'logo-light.png', height: '45' %>

Here's the style for those element
table.body-wrap .container .header{
  margin-bottom:10px;
  background: #1C788E;
  height: 75px;
  width:100%;
  border-radius: 1px;
}

table.body-wrap .container .header img{
  height: 45px;
  vertical-align: middle;
  padding: 15px 0;

  border-top-left-radius: 5px;
  border-top-right-radius: 5px;
}

This is the rendered element in development using mailer preview

And this is rendered element in production
<img src="https://ci5.googleusercontent.com/proxy/zqB3SKzsMQPGmc0MPF3jUby1LidTw5hkNhxpaqSuxXeO8ejHtHrbIivJoZZGYxCEYuTI_gYXXRbFN2rsv78w6DizJyVqCm38nOdlrTLWxa5an4GDgACzY8aTFJbKJF_PXs6LgMevH7WhlCNFjqHOdvfQN4gFrDEVRt2LMQQKx9yY=s0-d-e1-ft#https://www.handl.in/assets/logo-light-753ab2cd9b99ecc1d3b24005fba3f3aa1e85a5e5e5b1820fd93a336d12702d93.png" alt="Logo light" style="border-top-left-radius:5px;border-top-right-radius:5px;color:#fff;font-family:'Bariol','Open Sans','Helvetica Neue','Helvetica',Helvetica,Arial,sans-serif;font-size:100%;min-height:45px;line-height:1.5em;margin:0;padding:15px 0;text-align:center;vertical-align:middle">

The difference between the rendered element in development and production is the height. In dev, the height properly set to 45px, but in production somehow the style become min-height:45px;. Notice that in the image_tag code I gave the height property but still no luck.

What versions are you using in development and in production? AFAIK, premailer has no notion of rails envs.

I'm using premailer-rails 1.9.0 and premailer 1.8.6

I'm sorry, but I don't know why this would be happening. Maybe have a look at how premailer works and ask there. This gem, premailer-rails, only loads CSS and passes it to premailer. Either it's premailer that is doing something or it's your CSS that is somehow different in dev and production.

I am getting this error in production even after precompiling.  My stylesheet file is email.scss.  It works great in development.  Seems related to the OP.
Premailer::Rails::CSSHelper::FileNotFound: File with URL "/stylesheets/email.css" could not be loaded by any strategy.


[WIP] Add Elyra image to jupyter stacks

The Elyra image will use the minimal-notebook image as a base and deploy
it's suite of JupyterLab extensions on top as well as create a default metadata
instance to the default Kubeflow installation on the same cluster.

@vpavlin - do official images need to be in quay.io or can they reside in any container registry?


translation comment

想关关不掉的流
想干干不过的人
想忍忍不了的痛
想去不敢去的地方

Hi,
I'm sorry I don't speak Chinese, I don't believe this add's any value so I'm closing this :)

PR with a single white space + 1 contribution

Looks like the beginning of a spam account.

I think it might be a translation of the XML doc in there. Looks like either something went horribly wrong when translating it to Chinese, or Google Translate did a horrible job translating it back to English, cause it's way off the original :stuck_out_tongue_closed_eyes:

To close the unclosable stream..
To fight the unbeatable foe..
To bear with unbearable sorrow..
To run where the brave dare not go..


Value of type 'MTIRenderPipelineKernel' has no member 'apply'

import MetalPetal successful but it shows Value of type 'MTIRenderPipelineKernel' has no member 'apply'

@gmehedi Hi, did you find a fix for this?

If you installed using Cocoa Pods, to fix this issue, add this to your Podfile:
pod 'MetalPetal/Swift'


added Young Lu (me!) to Contributors.md

this is my first "contribution;" hopefully there will be more to come :)

Hi  @young-lu, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


new lesson: space-complexity

⭐ Request Type
I want to add information in space-complexity.md
Structure:

Concept
Need & Application
Calculation of space complexity
Explanation about calculation using examples
Space complexities of common algorithms

💻 Location
Location is at
section: 7
lesson: C
order: 7C
filename: space-complexity.md
❌ Additional Info
No response

I will like to work on this issue.


Add a parallel solver

Closes #9

Codecov Report

Merging #12 (85ecb10) into master (ff1d8ae) will increase coverage by 0.36%.
The diff coverage is 93.03%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   83.78%   84.14%   +0.36%
==========================================
  Files          24       25       +1
  Lines        1486     1564      +78
==========================================
+ Hits         1245     1316      +71
- Misses        241      248       +7

Impacted Files
Coverage Δ

upf/parallel.py
80.00% <80.00%> (ø)

upf/factory.py
86.27% <90.90%> (+10.51%)
:arrow_up:

upf/shortcuts.py
72.30% <100.00%> (ø)

upf/solver.py
70.00% <100.00%> (+7.50%)
:arrow_up:

upf/test/test_planner.py
99.50% <100.00%> (+0.04%)
:arrow_up:

upf/test/test_validator.py
98.43% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add ExceptionType member to Exceptions for Get-Error

PR Summary
For Get-Error cmdlet, if the object (or nested object) is an Exception, we add an ExceptionType property that has the full type name.  The Exception type is useful information and this change doesn't require the user to explore the error object to get it.
Example:
PS> 1/0
RuntimeException: Attempted to divide by zero.
PS> gerr

Exception             :
    ExceptionType  : System.Management.Automation.RuntimeException
    ErrorRecord    :
        Exception             :
            ExceptionType : System.Management.Automation.ParentContainsErrorRecordException
            Message       : Attempted to divide by zero.
            HResult       : -2146233087
        CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
        FullyQualifiedErrorId : RuntimeException
        InvocationInfo        :
            ScriptLineNumber : 1
            OffsetInLine     : 1
            HistoryId        : -1
            Line             : 1/0
            PositionMessage  : At line:1 char:1
                               + 1/0
                               + ~~~
            CommandOrigin    : Internal
        ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
    TargetSite     :
        Name          : Divide
        DeclaringType : System.Management.Automation.IntOps
        MemberType    : Method
        Module        : System.Management.Automation.dll
    StackTrace     :
   at System.Management.Automation.IntOps.Divide(Int32 lhs, Int32 rhs) in /Users/steve/repos/PowerShell/src/System.Management.Automation/engine/runtime/Operations/NumericOps.cs:line 61
   at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
   at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame) in /Users/steve/repos/PowerShell/src/System.Management.Automation/engine/interpreter/DynamicInstructions.Generated.cs:line 166
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) in /Users/steve/repos/PowerShell/src/System.Management.Automation/engine/interpreter/ControlFlowInstructions.cs:line 357
    Message        : Attempted to divide by zero.
    Data           : System.Collections.ListDictionaryInternal
    InnerException :
        ExceptionType : System.DivideByZeroException
        Message       : Attempted to divide by zero.
        HResult       : -2147352558
    Source         : System.Management.Automation
    HResult        : -2146233087
CategoryInfo          : NotSpecified: (:) [], RuntimeException
FullyQualifiedErrorId : RuntimeException
InvocationInfo        :
    ScriptLineNumber : 1
    OffsetInLine     : 1
    HistoryId        : -1
    Line             : 1/0
    PositionMessage  : At line:1 char:1
                       + 1/0
                       + ~~~
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan Please remind me in 1 hour

@TravisEz13, this is the reminder you requested 1 hour ago

@PoshChan Please remind me in 1 hour

@TravisEz13, this is the reminder you requested 1 hour ago

changed property name from ExceptionType to just Type based on @mklement0's feedback

@PoshChan please retry windows

CodeFactor issue is by-design

@SteveL-MSFT, successfully started retry of PowerShell-CI-Windows


Unauthenticated email from DOMAIN.COM is not accepted

Hello all,
I am using PRTG to monitor the SMTP roundtrip (it is sending to a Gmail account which replies back).
PRTG is relaying the emails to Postal which delivers the emails into the world.
Many times my emails are getting blocked by Gmail with below error message.
Why is is that most of the times the emails are being delivered but many times this error is generated?
All the external IPs being used by Postal are allowed in my DNS records.
550-5.7.1 Unauthenticated email from **domain**.com is not accepted due to domain's 550-5.7.1 DMARC policy. Please contact the administrator of **domain**.com domain if 550-5.7.1 this was a legitimate mail. Please visit 550-5.7.1 https://support.google.com/mail/answer/2451690 to learn about the 550 5.7.1 DMARC initiative. i2si1363996wrs.325 - gsmtp

What is the from domain when gmail sees that email? Does it have a DMARC policy on it that needs expanding to include your Postal server?

Hello,
The from is always the same<EMAIL_ADDRESS>It has a DMARC policy which includes postal allready in the spf records.

Below a Google report with the fails.
`

-
-<report_metadata>
<org_name>google.com</org_name>
<EMAIL_ADDRESS><extra_contact_info>https://support.google.com/a/answer/2466580</extra_contact_info>
<report_id>11888836422482274127</report_id>
-<date_range>
1572048000
1572134399
</date_range>
</report_metadata>
-<policy_published>
domain.com
r
r
reject
reject
100
</policy_published>
-
-
<source_ip><IP_ADDRESS></source_ip>
14
-<policy_evaluated>
none
pass
fail
</policy_evaluated>

-
<header_from>domain.com</header_from>

-<auth_results>
-
domain.com
pass
postal-fjFaAL

-
rp.postal.domain.com
softfail

</auth_results>

-
-
<source_ip><IP_ADDRESS></source_ip>
13
-<policy_evaluated>
none
pass
fail
</policy_evaluated>

-
<header_from>domain.com</header_from>

-<auth_results>
-
domain.com
pass
postal-fjFaAL

-
rp.postal.domain.com
softfail

</auth_results>

-
-
<source_ip><IP_ADDRESS></source_ip>
2
-<policy_evaluated>
reject
fail
fail
</policy_evaluated>

-
<header_from>domain.com</header_from>

-<auth_results>
-
rp.postal.domain.com
fail
postal

-
rp.postal.domain.com
softfail

</auth_results>

`

You'll note that the return path domain is present in the report, is that part of the DMARC policy too?
(P.S. You should use three backticks to enclose multi line comments in GitHub)

Looks like it's solved now by expanding the SPF records.


Add pac4j-config module and ConfigPropertiesFactory

CAS offers the capability to configure some common clients via properties -> https://github.com/Jasig/cas/blob/master/cas-server-support-pac4j/src/main/java/org/jasig/cas/support/pac4j/Pac4jConfiguration.java#L31
Knox integration requires the same capability, so it's necessary to have it in a ConfigPropertiesFactory created in a new pac4j-config module.

PR: https://github.com/pac4j/pac4j/pull/358


Error generating on windows, doesn't implement Debug

error[E0277]: `[u8; 40]` doesn't implement `std::fmt::Debug`
     --> C:\git\rust\xplm-sys\target\debug\build\xplm-sys-2d2d1c6f68d72b6b\out/bindgen.rs:59717:5
      |
59717 |     pub __bindgen_padding_0: [u8; 40usize],
      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `[u8; 40]` cannot be formatted using `{:?}` because it doesn't implement `std::fmt::Debug`
      |
      = help: the trait `std::fmt::Debug` is not implemented for `[u8; 40]`
      = note: required because of the requirements on the impl of `std::fmt::Debug` for `&[u8; 40]`
      = note: required for the cast to the object type `dyn std::fmt::Debug`

I get the following error trying to generate the bindings on Windows 10 with Clang 7.0 installed

I've also encountered a similar issue to this, along with some others. This is the culprit:
#[repr(C)]
#[derive(Debug, Copy)]
pub struct tagMONITORINFOEXA {
    pub __bindgen_padding_0: [u8; 40usize],
    pub szDevice: [CHAR; 32usize],
    pub __bindgen_align: [u32; 0usize],
}

The pregenerated branch has that change. If that works on Windows as far as you can tell, I'll publish it as a new version.

This worked for me, thank you. :+1:

Version 0.4.0, just released, has the definitions generated in advance. That should eliminate most of the bindgen-running problems, hopefully without creating any problems when compiling plugins.


Support buildTarget/run

Allows running of main methods using buildTarget/run BSP request
Supports scala-main-class RunParamsDataKind as there is no jvm specific data type.
Caveats...

StdIn - not connected since run/readStdin not supported - need to upgrade BSP to 2.2
StdOut - sent as log message since run/printStdout not supported - need to upgrade BSP to 2.2
StdErr - sent as log message since run/printStderr not supported - need to upgrade BSP to 2.2
Env vars are not passed -  need to upgrade BSP to 2.2

Looks like a lot of features are missing before upgrading to 2.2
Is the code change big for upgrading the BSP to 2.2? If not, maybe we can upgrade first.

Is the code change big for upgrading the BSP to 2.2? If not, maybe we can upgrade first.

I don't think there's much difference.  I'll submit a PR


Go build

Build image with go

I have read the CLA Document and I hereby sign the CLA

@NickChoiRBX Do you know why the CLA is failing?

@austinmacrbx Looks like npd config build is spitting a lot of information while it's building the image.
root@vagrant:~# npd config build --image npd-detector:1.0.9 --root-dir /home/vagrant/go/src/github.com/nomad-health-checks
{"stream":"Step 1/3 : FROM ubuntu:20.04"}
{"stream":"\n"}
{"status":"Pulling from library/ubuntu","id":"20.04"}
{"status":"Pulling fs layer","progressDetail":{},"id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":294128,"total":28565863},"progress":"[\u003e                                                  ]  294.1kB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":2062777,"total":28565863},"progress":"[===\u003e                                               ]  2.063MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":4401593,"total":28565863},"progress":"[=======\u003e                                           ]  4.402MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":7334329,"total":28565863},"progress":"[============\u003e                                      ]  7.334MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":9988537,"total":28565863},"progress":"[=================\u003e                                 ]  9.989MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":14088633,"total":28565863},"progress":"[========================\u003e                          ]  14.09MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":17025465,"total":28565863},"progress":"[=============================\u003e                     ]  17.03MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":20838841,"total":28565863},"progress":"[====================================\u003e              ]  20.84MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":24672697,"total":28565863},"progress":"[===========================================\u003e       ]  24.67MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Downloading","progressDetail":{"current":27601337,"total":28565863},"progress":"[================================================\u003e  ]   27.6MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Verifying Checksum","progressDetail":{},"id":"a31c7b29f4ad"}
{"status":"Download complete","progressDetail":{},"id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":294912,"total":28565863},"progress":"[\u003e                                                  ]  294.9kB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":3833856,"total":28565863},"progress":"[======\u003e                                            ]  3.834MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":7667712,"total":28565863},"progress":"[=============\u003e                                     ]  7.668MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":10616832,"total":28565863},"progress":"[==================\u003e                                ]  10.62MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":14450688,"total":28565863},"progress":"[=========================\u003e                         ]  14.45MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":18874368,"total":28565863},"progress":"[=================================\u003e                 ]  18.87MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":22708224,"total":28565863},"progress":"[=======================================\u003e           ]  22.71MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":24477696,"total":28565863},"progress":"[==========================================\u003e        ]  24.48MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":27426816,"total":28565863},"progress":"[================================================\u003e  ]  27.43MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Extracting","progressDetail":{"current":28565863,"total":28565863},"progress":"[==================================================\u003e]  28.57MB/28.57MB","id":"a31c7b29f4ad"}
{"status":"Pull complete","progressDetail":{},"id":"a31c7b29f4ad"}
{"status":"Digest: sha256:b3e2e47d016c08b3396b5ebe06ab0b711c34e7f37b98c9d37abe794b71cea0a2"}
{"status":"Status: Downloaded newer image for ubuntu:20.04"}
{"stream":" ---\u003e c29284518f49\n"}
{"stream":"Step 2/3 : COPY ./nnpd.tar /tmp/nnpd.tar"}
{"stream":"\n"}
{"stream":" ---\u003e da07fc4c9e\n"}
{"stream":"Step 3/3 : ENTRYPOINT tar -xvf /tmp/nnpd.tar -C /alloc \u003e/dev/null 2\u003e\u00261"}
{"stream":"\n"}
{"stream":" ---\u003e Running in 8e3bf98aef1b\n"}
{"stream":"Removing intermediate container 8e3bf98aef1b\n"}
{"stream":" ---\u003e 7d2eaa33b2b7\n"}
{"aux":{"ID":"sha256:7d2eaa33b2b72714e7e5d0c3bcd89e760c1cef4d61e07f63fa6e67a753b0eec4"}}
{"stream":"Successfully built 7d2eaa33b2b7\n"}
{"stream":"Successfully tagged npd-detector:1.0.9\n"}
npd: building docker image        2s [================================================] 100%
npd-detector:1.0.9 build successfully.

We don't need all of this. We just need to show the progress bar (The way it was before).
npd: building docker image        2s [================================================] 100%
npd-detector:1.0.9 build successfully.

Can you check if this can be suppressed?

Yep lemme do that

Adding @cliffchapmanrbx, in case he knows why the CLA bot is failing.

Adding @cliffchapmanrbx, in case he knows why the CLA bot is failing.

As the CLA bot commented the commits in this repo aren't associated with a current GitHub account. @austinmacrbx needs to associate the email used to create those commits with the account being used to comment on this PR.

Adding @cliffchapmanrbx, in case he knows why the CLA bot is failing.

As the CLA bot commented the commits in this repo aren't associated with a current GitHub account. @austinmacrbx needs to associate the email used to create those commits with the account being used to comment on this PR.

Aah I see! Thanks.


bugfix #5 - image does not reload after image source property change

You can do this by using replace method. Check this, I think it'll solve your problem
https://github.com/Agontuk/vue-cropperjs/blob/master/example/src/App.vue#L45

tnx... this would solve my issue


Remove src directory and already-bundled dependencies from published package

We currently include the src directory in the published artifact, resulting in an extra 2.6 MB on disk.
Additionally, although we bundle the application into wrangler-dist/cli.js, we publish package.json still declaring dependencies on those bundled libraries, resulting in an additional 32 MB of packages getting installed even though they've already been included in the bundle.
In order to minimize installation time of wrangler, we should consider removing src from the published artifact and either moving bundled dependencies to devDependencies or publishing with a stripped down package.json that only includes within dependencies any externalized modules. This becomes more important as we start depending on larger external modules (e.g. workerd) and need to keep time-to-install within reasonable bounds.

On further inspection, it turns out we mostly already do only include externalized dependencies within our dependencies array. The only bundled dependencies we're unnecessarily installing seem to be nanoid and xxhash-wasm, which we should still move into devDependencies, though doing so will net us far less savings than I was hoping for (~250 KB on disk).
On the bright side, we're already doing the right thing, so GO TEAM! 🥳
Sorry for the false alarm, and h/t @petebacondarwin for calling attention to the quick savings we could gain by removing src.

I think xxhash-wasm is still needed as a dependency for now. It is used to create a hash key for "Workers Sites" uploads. But once we move over to Pages based asset uploads, this can go.

oh, good to know! I just meant xxhash-wasm is currently bundled, not externalized, so we can move it over to devDependencies.

Thanks @1000hz for enlightening me about how xxhash-wasm has the WASM module inlined in the JS module! So indeed it is already bundled.

If we ship the JS API and want to provide declarationMaps, we'd probably want to include the src directory in the published package.
I'm a pretty big +1 to doing this! It can make using a package so much easier.


Flutter beta 0.5.1 does not upgrade to Flutter Release Preview 1 on macOS 10.13.5

The Medium article at https://medium.com/flutter-io/flutter-release-preview-1-943a9b6ee65a?linkId=53249457, "Announcing Flutter Release Preview 1", says:
How do you upgrade to Flutter Release Preview 1? If you’re on the beta channel already, it just takes one command:
$ flutter upgrade
This does not work.

My understanding is that is the release preview version. It came out around a day before the article did and if you check the download links in the installation guide, they point to that version.

@MaikuB is right, the current beta is the Release Preview 1.

@MaikuB mai  you mean beta 0.5.1  is the release preview version?

Yes that was confirmed by @zoechi as well. in fact if you look at the install guides for downloading the Flutter SDK zip file then you'll see it's 0.5.1

Hey sorry for follow up question, is there no upgrade after beta 0.5.1? It seems the last update was 3 months ago? Or should I move to a different branch?
Hope someone can clarify thanks!

@allandaleho 0.5.1 seems still to be the latest beta channel version. You could switch to dev channel until a new beta is released. I don't know what blocks a new beta release.


Add basic video edition capabilities

Hi,
As discussed over Discord, It would be nice to have basic video edition capabilities such as rotating a video.

@alexandrefresnais concatenating videos is coming in 0.0.18. We can quickly add a lot of video editing capabilities, but they will all run server-side for now. We will then try to bring these back to run on-device later, given the difficulty of support for some of these operations across different platforms.

@alexandrefresnais we've decided not to go ahead with implementing editing functions in VideoKit because of how open-ended these editing functions can be. And composing different edits will also take a lot of processing time, as compared to having a single function that performs all the required operations.
Instead, I recommend using our Function platform to write editing functions in Python (e.g. using ffmpeg) then using these functions from your Unity app. Feel free to follow up for more info on doing this.


Thread safety for changing values of keys already in ordered_map

Hi!
I'm using this project's ordered_map. The values under the keys can change, but after the map is first populated, the keys always remain the same. In that situation, in a multithreaded program, is it safe to overwrite the value under one key from thread 1 while accessing another key from thread 2?
I took a look at https://tessil.github.io/ordered-map/classtsl_1_1ordered__map.html#details

insert, emplace, emplace_hint, operator[]: when a std::vector is used as ValueTypeContainer and if size() < capacity(), only end(). Otherwise all the iterators are invalidated if an insert occurs.

From that quote, is it correct that simply changing the value under one key isn't an "insertion" (as defined in something like cplusplus docs for std::unordered_map: adding a new element to the map) and therefore even an ordered_map using std::deque isn't invalidating its iterators (and therefore, can access values under other keys from another thread safely)?
If my understanding is correct and you think it makes sense, I could try my hand at updating the docs to make them clearer on this point.
Cheers!

@Tessil ping :)

Hi @ericonr
Sorry for the delay. Yes, your understanding is right.
Using insert or emplace on an existing key will not modify the map and as long as both threads are not trying to read and update the value of the same key, everything should be thread safe.

Sorry for the delay. Yes, your understanding is right.

No worries, I know how easily things can slip up :) And that's great to know!

The documentation could effectively be updated to make the distinction between an actual insert and an insert call with an existing key (which will just return an iterator to the existing element similarly to find).

I will try and find the time to make a PR, then :)


Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes

Output of helm version:
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.17.13"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.6+k3s1", GitCommit:"a8e0c66d1a90a2bbc4ffa975129ca35756cc7c14", GitTreeState:"clean", BuildDate:"2022-09-28T16:52:07Z", GoVersion:"go1.18.6", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.6+k3s1", GitCommit:"a8e0c66d1a90a2bbc4ffa975129ca35756cc7c14", GitTreeState:"clean", BuildDate:"2022-09-28T16:52:07Z", GoVersion:"go1.18.6", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
native ， k3s

I suspect the presence of the build version is confusion the semver comparison (ie. the +k3s1 part of the version string)

Source: https://github.com/helm/helm/blob/49819b4ef782e80b0c7f78c30bd76b51ebb56dc8/pkg/action/action.go#L116
Notably, it seems that caps.KubeVersion is empty

This is retrieved by client-go:
https://github.com/kubernetes/client-go/blob/1ac8d459351e21458fd1041f41e43403eadcbdba/discovery/discovery_client.go#L566-L578
Is k3s not providing the /version api?

Trying to install on pi cluster and getting very similar error:
pi@blade1:~/longhorn_test $ helm install rancher rancher-stable/rancher \

--namespace cattle-system
--set hostname=rancher.mydomain.com
--set bootstrapPassword=admin
Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.25.6+k3s1
pi@blade1:~/longhorn_test $

@dstewen 1.25.6 is not less than 1.25.0. Fun fact, 1.25.0 is also greater than 1.25.0-0 as the -0 makes it a pre-release.

I'm using a Cloud-Init version of Ubuntu 22.04 in some Proxmox virtual machines which now delivers Kubernetes 1.26.1 version. How could I use Rancher in a production environment with those version discrepancies? I mean... should I use another cloud-init distro for safely run Rancher or something?

If the chart you're using has a restriction stating that the kubernetes version must be < 1.25.0-0, then you'll need a chart upgrade. Check with your chart publisher.

If the chart you're using has a restriction stating that the kubernetes version must be < 1.25.0-0, then you'll need a chart upgrade. Check with your chart publisher.

I'm using this chart. As far as I understand this is the "official" Rancher chart, isn't it? It's also indicated on Rancher docs. Should I use another chart?

If the chart you're using has a restriction stating that the kubernetes version must be < 1.25.0-0, then you'll need a chart upgrade. Check with your chart publisher.

My bad! I thought I'm in the Rancher repo! Sorry!

No worries. We've all been there. Should I close this then?

First time successfully installed a Kubenetes installation it took like 10 VM's to get it working but i did it!!! I used MicroK8s on Ubuntu Server and got Remote access working for Dashboard and installed cert-manager and I'm at the final command to install Rancher and I get "Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.26.1". Is it something that could be worked around or is there no "fix" for this yet?


Execute Docker API/CLI commands against multiple containers

Rancher UI already supports limited capabilities of being able to execute commands against multiple containers (i.e run, stop, state change commands) but does not support this via API/CLI.
Rancher should support CLI/API capability to do a best effort execution of Docker commands (run, exec, etc.) against multiple containers.  It can support executing (exact or reg exp match):

by host
by cluster
by name
by label
by multiple container IDs
by service (once Service Discovery feature has been implemented)

+1

+1
Even just making it possible to execute a single command via the API would make the rancher-compose equivalent of docker-compose exec feasible.


custom render text input

Thanks for the PR! The custom renderTextInput prop will land in the v2 release soon.

Merged it in master :).


Unknown encoding name - utf8

Hi,
I'm getting a strange error when I try and access a div element on a webpage (I've tried different elements.. same issue). Error is below:
from /usr/local/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node.rb:631:in serialize' 	from /usr/local/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node.rb:790:in to_format'
from /usr/local/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node.rb:646:in to_html' 	from /usr/local/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/lib/nokogiri/xml/node.rb:517:in to_s'
from /Users/maxfarrar/Dropbox/Programming/Ruby/generalScraper.rb:13:in puts' 	from /Users/maxfarrar/Dropbox/Programming/Ruby/generalScraper.rb:13:in puts'
from /Users/maxfarrar/Dropbox/Programming/Ruby/generalScraper.rb:13:in `scrape'

I think the problem is that "utf8" is not a valid encoding, it needs to be "utf-8" (with the dash).
> "foo".force_encoding("utf-8")
# => "foo"

> "foo".force_encoding("utf8")
ArgumentError: unknown encoding name - utf8

Is it possible that the webpage you're parsing uses "utf8" instead of "utf-8" somewhere (maybe in its Content-Type header or meta charset tag)?

There's not enough information here to diagnose the issue. Please reopen with more information if you're still experiencing issues.


enable slack notification on kcp o cmd

Implement kcp-cli orchestration sends Slack info message to multiple channels
when its merged the slack-api-url in kcp-dev.yaml should change to:

slack-api-url: ["https://hooks.***", "https://hooks.***"]

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: lauraanddola:x: lauraanddolayYou have signed the CLA already but the status is still pending? Let us recheck it.


Cursor position always show at the start when add new mentions into textfield

Hi, your package is awesome. Android works perfectly but in IOS, it doesn't work as expected
https://user-images.githubusercontent.com/34902237/106765508-72e3d600-666b-11eb-8059-baa0ea28b0d7.mov

@Barry0501 why was this issue closed without PR merged? Do you know a way to solve it? I am experiencing same issue.

@dmba Yeah I figured out how to solve it. Let me create PR for this issue

@Barry0501 awesome, thank you


IDS/IPS rule download, use content-disposition and support overlays

when downloading rules, use content-disposition if found in the reponse headers.
If target filenames overlap, use the last found (descending filename)
improve logging, add http response code in log

https://github.com/opnsense/core/commit/534c918a4efaa39868d5242349d6cfe669d07608

to test:
opnsense-patch 534c918  416b05a  b38a76a


update readme

[x] Top-level README “Table of Contents” is updated
[x] Feature tasks for this challenge are completed
[x] Unit tests written and passing

[x] {1,2,3,99,4,10,11}; - Expected outcome
[x] {1,2,3,99,4,10,10}; - Expected failure
[x] Edge Case (if applicable/obvious)

[x] README for this challenge is complete

[x] Summary, Description, Approach & Efficiency, Solution
[x] Link to code
[x] Picture of whiteboard


Unexpected token, expected "{"

Summary
Got build error after installed the package and run pod install in the app on xCode:
SyntaxError: ${PROJEcT}/node_modules/react-native/index.js: Unexpected token, expected "{"

I already try during almost 5 hours to find a way, but I'm not an expert using xCode. When I removed the package my project build correctly. I don't know if I'm doing something wrong
Reproducible sample code
And here is my babel.config.js:

module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
  plugins: [
    [
      'module-resolver',
      {
        root: ['.'],
        alias: {
          components: './src/components',
          store: './src/store',
          config: './src/config',
        },
      },
    ],
    [
      'const-enum',
      {
        transform: 'constObject',
      },
    ],
  ],
};

Here is my Podfile:
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '13.0'

target 'LifeLine' do
  config = use_native_modules!

  use_react_native!(
    :path => config[:reactNativePath],
    # to enable hermes on iOS, change `false` to `true` and then install pods
    :hermes_enabled => false
  )

  # Required to display the google map by package react-native-maps
  rn_maps_path = '../node_modules/react-native-maps'
  pod 'react-native-google-maps', :path => rn_maps_path

  target 'LifeLineTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable the next line.
  use_flipper!()

  post_install do |installer|
    react_native_post_install(installer)
  end
end

### Steps to reproduce

Install react-native-maps & pod install then try to run the project on a real device

### Expected result

Build successfully

### Actual result

SyntaxError: ${PROJEcT}/node_modules/react-native/index.js: Unexpected token, expected "{"

### React Native Maps Version

1.3.2

### What platforms are you seeing the problem on?

iOS (Google Maps)

### React Native Version

0.67.2

### What version of Expo are you using?

Not using Expo

### Device(s)

Iphone 13

### Additional information

_No response_

react-native/index.js isn't modified by react-native-maps in any way. If you still experience this, you'd probably have to provide a minimal reproducible example in a repo.


updated commit reference for v6.0.0 changelog #5204

updated CHANGELOG.md file for v6.0.0 release, due to this 5204
Commits refered from this link
https://github.com/angular/protractor/commits/master

I signed it!

Thank you so much. I generated these off of the selenium4 branch and did a release for 6 beta. During the release I moved these changes to the master branch and I guess the commit hash changed. Thank you for finding this and thank you for this PR.

Squash merging this. The CircleCI and travis issues have nothing to do with the markdown file.


fix: request camera permission only after screen transition is complete

Details

This PR fixes an issue where screen transition animation was getting interrupted by camera permission dialog causing the animation to stop in between.
Fixed Issues

$ https://github.com/Expensify/App/issues/36551
PROPOSAL: https://github.com/Expensify/App/issues/36551#issuecomment-1945132640
Tests

Reinstall the app on a native device
Log in for the first time
Tap on FAB -> Request money -> Scan
Verify that the screen transition animation is smooth and not interrupted in middle by camera permission dialog

[x] Verify that no errors appear in the JS console

Offline tests

Reinstall the app on a native device
Log in for the first time
Go Offline
Tap on FAB -> Request money -> Scan
Verify that the screen transition animation is smooth and not interrupted in middle by camera permission dialog

QA Steps

Reinstall the app on a native device
Log in for the first time
Tap on FAB -> Request money -> Scan
Verify that the screen transition animation is smooth and not interrupted in middle by camera permission dialog

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/6880914/fe0e7c6a-3831-4a94-8051-ecf7229f90ae

Android: mWeb Chrome

https://github.com/Expensify/App/assets/6880914/fba13c10-de24-4480-9750-ecb0fd9de228

iOS: Native

https://github.com/Expensify/App/assets/6880914/39c1ab94-f717-4048-a56e-12c416960a71

iOS: mWeb Safari

https://github.com/Expensify/App/assets/6880914/837a8eeb-4120-4cf0-88f9-6d85b5c22f3c

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/6880914/666cdd21-2571-4117-b0a4-74c38b1c7c59

MacOS: Desktop

https://github.com/Expensify/App/assets/6880914/eb2ad51a-27e0-4138-be5b-08d8d39bca08

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

tests passed

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.4.55-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.4.55-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.4.55-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Feat:

Describe the feature
Adding different modes
Add ScreenShots
I would like to add different modes for kids and light and dark themes and make it responsive
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

acha


DNN-7278: keep checkpoint data if exception throw.

@zyhfish see the comment in the JIRA - rather than re-opening a closed/regressed issue we need a new issue to track this change


Fix a minor bug preventing immediate resync when new ENI is created

This commit returns the correct instance mutation status in
handleIPAllocation() and also avoids unnecessary invocation of
resyncTrigger when there's an error in MaintainIPPool.
Previously, on ENI creation resync was being scheduled but was
not triggered immediately.

Fixed in https://github.com/cilium/cilium/pull/20609


Add an Object.groupBy TypeScript goody

An Object.groupBy method is being added to JavaScript, but for now this is not available on LeetCode, since it requires Node 21, whereas LeetCode uses Node 20.
We'd like to get access to this function sooner, so let's create our own version!
This issue involves adding another directory within workspaces/adventure-pack/goodies/typescript, named Object.groupBy, with an index.ts for the implementation and an index.test.ts for a test. You can use the Map.groupBy added by #358 for inspiration, this should be very similar.
Note: after adding or updating a goody you will need to run yarn package-goodies:test -u to refresh the snapshot tests.
Please comment with any questions.

@miorel Quick question would this issue be the same as #108

Not exactly. This one is about replicating the built-in function Object.groupBy, #108 would be about adding a method to iterators.


Error code AADB2C99001 not in the error code list

[Enter feedback here]
I encountered an error code not in your list- AADB2C99001
Below is more details on the error. Some of the error is policy specific (using b2c custom policies) but having something in the documentation about the existence of this code would be helpful.
AADB2C99001 This+user+already+exists%2c+and+profile+%27Step-57-AAD-Fed-Link-Federated-Account%27+does+not+allow+the+same+user+to+be+created+again.

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

ID: fd9c64ff-5065-9a2b-4965-c48685482fe1
Version Independent ID: 3ff9871f-d28d-b752-750e-1142556ec8cb
Content: Error code reference - Azure AD B2C
Content Source: articles/active-directory-b2c/error-codes.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@frankdrewes
Thanks for your feedback! We will investigate and update as appropriate.

@frankdrewes
Thank you for your feedback and patience.  We're collecting all the information required to resolve this issue.

Hi, what was the outcome here? AADB2C99001 is still not listed, though I see references to it in our codebase and in official Microsoft example code.
https://github.com/Azure-Samples/active-directory-b2c-advanced-policies/blob/e4b6c895f6769344ed5868c74ee5db6762cf7e7f/wingtipgamesb2c/src/WingTipGamesWebApplication/Startup.cs#L464

As far as I can see, this commit was made to fix this issue, but refers to a different error code to what was requested in this ticket
https://github.com/MicrosoftDocs/azure-docs/commit/99f3213327996c5141d4c2152c63c1059fc7050e
AADB2C99001 (this ticket)
AADB2C90001 (added in commit)

@yoelhor @kengaderdus please can you reopen this?

Please reopen. The error code is still not in the documentation. The correct error code is AADB2C99001. A sample scenario is if a sign up user flow is executed, social login is attempted for a user that is already in the directory.
Error message is: AADB2C99001: You are already registered, please press the back button and sign in instead.

Please reopen. The error code AADB2C99001 is incorrectly listed as AADB2C900011 (2nd digit should be 9 instead of 0)

I don’t think anyone is checking comments here so probably worth opening a new issue and referencing this one.
I has opened this which iirc was related, though it was closed without change
https://github.com/MicrosoftDocs/azure-docs/issues/116527