Can't compile example

I tried compiling the async_client example.
First I had to add the feature esp-hal-embassy to get it to get through the rust compile, worth adding in the docs.
But then, it link, I got this error which looks like its about the missing binary, the instructions in the README state the binaries come with mbedtls, where do I get them and how should I user them for the examples to compile?
/Users/my_user/.rustup/toolchains/esp/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/../lib/gcc/xtensa-esp-elf/13.2.0/../../../../xtensa-esp-elf/bin/ld: /Users/my_user/OpenSourceProj/esp-mbedtls/target/xtensa-esp32s3-none-elf/release/build/esp-mbedtls-sys-3b3c6bc69fe592d1/out/libmbedcrypto.a(bignum.c.obj):(.literal+0xd0): undefined reference to `mbedtls_mpi_exp_mod'
          /Users/my_user/.rustup/toolchains/esp/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/../lib/gcc/xtensa-esp-elf/13.2.0/../../../../xtensa-esp-elf/bin/ld: /Users/my_user/OpenSourceProj/esp-mbedtls/target/xtensa-esp32s3-none-elf/release/build/esp-mbedtls-sys-3b3c6bc69fe592d1/out/libmbedcrypto.a(rsa.c.obj):(.literal+0x34): undefined reference to `mbedtls_mpi_exp_mod'
          collect2: error: ld returned 1 exit status

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-lib)

Had a mistake in the command line, seem to compile now, closing


Stop flags with optional arg eating following flags.

Hi all,
I don't know if this should be part of #5338, #8656 or #11136, and I see a PR in #9909, so it's possible there's some overlap. What I do know is that I had an itch to scratch because my CLI app has defined within it several flags with optional arguments that would then eat following arguments if not provided a value.
All existing specs pass on my machine.
Let me know if there's anything untoward.
Regards,
iain

Btw, the check that is failing is a formatting check in the spec file. Running crystal tool format --check spec/std/option_parser_spec.cr gives me "formatting './spec/std/option_parser_spec.cr' produced changes". I've no idea what that means, any guidance on using that tool would be welcome.
Regards,
iain

Hi @yb66
We have a code formatter in place, and all code in this repository must follow that format.
You can run:
crystal tool format spec/std/option_parser_spec.cr

that will change the file to follow that format. Then commit and push those changes. Thank you!

Thanks @asterite, I see it's already in the guide, I missed that, sorry. I'm installing the hook now!
Regards,
iain

The PR should have a clear description of the proposed change. Only after looking into the code, I realized what it is about.

My apologies.

But it is not a generic solution. For example, it can't tell an optional value from a positional argument.

I think this comes down to our needs here. You're looking to improve the language/tools as a whole long term and without needing to return to things. I want that too but I also have a need for this specific fix right now, so that's the focus of this patch. I haven't looked at OptionParser as a whole.
Regards,
iain

Related: #11546 will make optional flags skip any subsequent argument, not just flags.


Correct the incorrect label in kubectl command for inspecting Leases for kube-apiserver

This fixes #41881
Corrected the incorrect(old) label in kubectl command for inspecting Leases for kube-apiserver.

Hi @tengqm,
Can you please review this?

/lgtm

Hi @sftim, can you please merge this?

/approve


Move cli tools to ha-mqtt-discoverable-cli

Per #18, move the cli tools into a different module, ha-mqtt-discoverable so python programs that only use the API don't also install all of our cli tools.

Sure you don't want to keep a single package? (I am thinking in term of ease of maintenance and keeping everything in check under the same code structure).
I have been playing a bit with defining the CLI as a Python extra, obtaining this: https://github.com/mion00/ha-mqtt-discovery/tree/feat/typer_boilerplate (ignore the entities.py, it's just some boilerplate code to get going).
Typer is not pulled by doing poetry install, so consumers of the library won't have it in their dependencies.
It must be asked for by using poetry install --extras cli.

Maybe I'm reading this wrong, but doesn't that only affect the dependencies of the module? It won't install Typer unless you do poetry install --extras cli, but that doesn't stop the entrypoint scripts from being created during a pip install, it keeps them from working because the proper dependencies weren't installed.
Moving the cli stuff to a separate package keeps them from getting installed at all by a pip install ha-mqtt-discoverable so that people only interested in using the module won't have the CLI tools pollute their disk.
If there's a clean way to keep both modules in the same repo I'd prefer to do that, but I don't see a way to have the cli tools currently defined in the [tool.poetry.scripts] section only get installed when the cli extra gets installed.
I'd be happy to be wrong though.

From what I learned the scripts section cannot be made conditional.
The way httpx handles it is that they always install the script entrypoint, and in that script they check if the cli dependencies are installed, otherwise they error out.

Closed by https://github.com/unixorn/ha-mqtt-discoverable-cli/pull/2


Get General Help

bot anti-nuke won't work... i tried nuking my testing server if the anti-nuke is working but it's not.
console won't show any error tho, I waited for 5 minutes and the whole server nuked like a thousand pings but it wont kick/activate the anti nuke.
i used the suggested antinuke settings

pinging a ton is raiding
nuking is:
deleting channels
deleting roles
creating channels
creating roles
adding other bots
etc. etc,


Allow writing JSON reporter to write directly to file

Description of the Change
Add feature for reporterOption in JSON reporter to output directly to file system. Method is similar to how xunit is implemented
Alternate Designs
It would be simple to write the JSON to the stdout and then just pipe that into a file. However when using certain tools like mocha-multi-reporters there is no way around writing JSON and the spec reporter to the stdout. Furthermore, with bash and jq JSON is a great way to parse the results while still allowing for human readable output with spec.
Why should this be in core?
There are so many different JSON reporters but non are managed and they all fall through. This is a simple fix that would be a great feature that will help many
Benefits
The ability to write JSON files of your output thereby making analyzation of your tests easier to parse
Possible Drawbacks
None that I can think of right now (happy to hear if someone has some ideas)
Applicable issues
This is an enhancement (minor release) I think

Coverage increased (+0.02%) to 90.009% when pulling e4ce8076c77f8c8b527629bed909c5cb75baa508 on mkamioner:master into f71f3472d1049737ce0e2d2131753b468d45c66a on mochajs:master.

Thanks.  I'm not convinced Mocha needs this feature, since you can pipe to a file, like you mentioned.
If we do want to be able to write directly to a file (and I'm not sure how necessary that is for the userbase, because pipes), I'd rather make it happen in the general case by swapping the output stream, instead of a reporter-by-reporter basis.
Please don't let this discourage you from contributing to Mocha!  There are plenty of issues labeled help wanted that we could use help with.

Guess I wasted my time doing basically the same enhancement, except I threw out the existing "json.spec.js" and based my tests on revamped version of XUnit's spec (which did stream checking). I have a use case for our project  (which programmatically uses Mocha under the covers for RAML-based test automation) referenced in this issue (for one). If someone adds console.log() statements to his hook files, but specifies (for example) the Mocha json reporter -- assertions will fail due to crossing of the streams and Abao can't salvage Mocha's output. I was actually rather stunned that file output was ONLY available for XUnit reporter -- IMO, output should be trivially redirectable (-o | --output) without having to convert individual reporters as such or involve command shell piping.

@boneskull BTW, had two questions left after doing my enhancement -- could you shed some light on them?

These two lines. First binds and assigns to a variable. But why is the expectation seemingly referring to result of its invocation.
https://github.com/mochajs/mocha/blob/d3d7799fbb298148b8adc73a3d5bdc989ff8f1cc/test/reporters/xunit.spec.js#L41-L42

GH-237
https://github.com/mochajs/mocha/blob/d3d7799fbb298148b8adc73a3d5bdc989ff8f1cc/lib/reporters/xunit.js#L17-L28
https://github.com/mochajs/mocha/blob/d3d7799fbb298148b8adc73a3d5bdc989ff8f1cc/lib/reporters/base.js#L21-L33

If these variables were exported from Base, would the individual reporters need to have same code repeated?

XUnit.bind() returns a function, and that function is then run, and we assert it throws.
I don't think that repetition is necessary.

Not having a way to redirect the json output to a file can be an issue when launched within a test suite:
nyc mocha --recursive --exit --timeout=10000 -r ./node_modules/ts-node/register src/**/*.spec.ts -R json
As it will collide with nyc output and others. We could argue that we could do two runs: one for coverage and one for unit test result but it is overkilled no?
Am I missing something obvious?

@boneskull Is it possible to remove the "extra" stuff that comes out when piping? For example, when I run something like:
npx cypress run --headless --reporter json > results.json
My results.json file comes out like this:

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:    3.8.3                                                                              │
  │ Browser:    Electron 78 (headless)                                                             │
  │ Specs:      1 found (test.spec.js)                                                             │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  test.spec.js                                                                    (1 of 1)
{
  "stats": {
    "suites": 1,
    "tests": 12,
    "passes": 11,
    "pending": 0,
    "failures": 1,
    "start": "2020-05-06T02:31:09.690Z",
    "end": "2020-05-06T02:31:14.497Z",
    "duration": 4807
  },
 ..... removed for brevity ...

Obviously this isn't a valid JSON file because of the initial output. Is it possible to get rid of that and just pipe the JSON result?

that output is from cypress not mocha

Oh, shoot. My apologies!

regarding nyc output, you could suppress that instead and write to file. not ideal...
this being said I would support adding the ability to swap the output stream (generally just process.stdout) in mocha, but it should be generic and applicable to all reporters. someone would need to send that PR though
this would allow these sorts of situations—mocha combined with other tools—to work together more nicely.
implementation would just be something like a “default” stream for each reporter—probably in the Base reporter—which can be swapped out via reporter options.


Fix typo

a -> an

@changeworld : Thanks for your contribution! The author, @swhite-msft, has been notified to review your proposed change.

Verified editorial correction.


Swift Package Manager 5.3 support: Swift and Objective-C library

Updated the SPM Support.
Support for Objective-C library as SPM.

@MatthewYork Any chance this could be merged so your library works with SPM again? 🙂

Sure would be nice if it would get merged so I could use SWP!

Agreed, I was just looking migrating to SPM for this and sadly with the current release it is not possible.


[BUG] Sway/Workspaces - One workspace not following format: "{icon} {name}"

Workspace 6:notes is not inheriting the format for workspaces.
Workspace Config:

Waybar:

I've tried some steps to fix this but nothing has worked so far:

Sway Reload
Exit and Restart Sway
killall -SIGUSR2 waybar
reboot

Waybar 0.9.13
Sway 1.7

I experimented further and this seems like an issue with Font-Awesome.
Using a different icon for "6:notes" moved the icon into the correct position.

Changing it back to the original icon causes the same issue.


nvim-cmp not working at all

Hello,
I've been trying to setup nvim-cmp all day now but I can't get it to work,
I first tried to do everything listed in the readme but it didn't work.
I then tried to follow this tutorial from nvim-lspconfig but that also did not work.
I get no errors whatsoever, I have nvim-cmp & cmp-buffer installed through packer. But since I have no error messages, I have no idea on where to even begin at fixing it.
This is the repo where all my config files are if you want to take a look. all lsp related config is in the lua/dev/lsp.lua file.
Thank you for your time

I think this requires further debugging. Glancing at your config you are using onmifunc which might conflict (but lsp completions should be working with it). You can make sure its running setup by using something like print('running cmp setup').

The file is definitely loading, I have all the nvim-lspconfig diagnostics working. It's just that the completion never pops up or shows no sign of life. So when I had a print statement in the lsp.lua file, all seem file, printing the local cmp variable also seem to return a valid address. After that, I have no idea what to do

I think you should create the minimal vimrc to reproduce the problem.

I've made a minimal repro here which only has 3 plugins installed, nvim-lspconfig, nvim-cmp and cmp-buffer. The completion still does not appear. So my problem is either in my lsp setup, or something else, i'm not too sure. I have a correct neovim verison (v0.5.0-dev+1375-gca802046b). So i'm a bit lost.

Well...  You should create one minimal vimrc without packer.
OK.  I will create the minimal.

Wow.  My minimal vimrc does not work...
if &compatible
  set nocompatible
endif

set runtimepath+=~/src/nvim-cmp
set runtimepath+=~/src/cmp-buffer

lua <<EOF
  local cmp = require'cmp'.setup()

  cmp.setup {
    -- You can set mappings if you want
    mapping = {
      ['<C-p>'] = cmp.mapping.select_prev_item(),
      ['<C-n>'] = cmp.mapping.select_next_item(),
      ['<C-d>'] = cmp.mapping.scroll_docs(-4),
      ['<C-f>'] = cmp.mapping.scroll_docs(4),
      ['<C-Space>'] = cmp.mapping.complete(),
      ['<C-e>'] = cmp.mapping.close(),
      ['<CR>'] = cmp.mapping.confirm({
        behavior = cmp.ConfirmBehavior.Insert,
        select = true,
      })
    },

    -- You should specify your *installed* sources.
    sources = {
      { name = 'buffer' },
    },
  }
EOF

@hrsh7th Can you provide the minimal vimrc for me?

I've added the minimal vimrc. https://github.com/hrsh7th/nvim-cmp/blob/main/utils/vimrc.vim
@Wmbat This minimal vimrc allows you to complete neovim/lspconfig. Please looking into it.

Ok, I setup neovim with the minimal vimrc you linked. but the completion still doesn't work. The LSP does work though. I tried both CCLS & Clangd and both LSP provided me with errors (on code with syntax errors).
It has to be a problem on my side, as it works for everyone else, but I have no idea what it is

@Wmbat I think your config didn't install cmp-nvim-lsp.
https://github.com/Wmbat/nvim-config/blob/main/lua/plugins.lua#L47

My config did not, but I copied your minimal vimrc and it also didn't work there. @hrsh7th

Hm... I'm getting it to work with the following configuration now...
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/vim-vsnip'
Plug 'neovim/nvim-lspconfig'
call plug#end()
PlugInstall | quit

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  snippet = {
    expand = function(args)
      vim.fn['vsnip#anonymous'](args.body)
    end
  },

  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = {
    { name = "nvim_lsp" },
    { name = "buffer" },
  },
}
EOF

lua << EOF
local capabilities = require('cmp_nvim_lsp').update_capabilities(vim.lsp.protocol.make_client_capabilities())

require'lspconfig'.clangd.setup {
  capabilities = capabilities,
}
EOF

Yeah, I have the exact same code right now and it does not work. Which is why i'm really confused about what is not working

OOHHH, I think i have it fixed, It seems like the completion does not working with neovim v0.5.0-dev+1375-gca802046b. I've fully removed it and installed neovim v0.5.0 and it works. That's a really weird bug.
It also worked with neovim v0.6.0-dev+198-g81f4de08b. I think the version I had predates the 0.5 release

For LSP debugging, You can set vim.lsp.set_log_level("debug") and then ~/.cache/nvim/lsp.log will be wrote all LSP payloads.

Hm....! I have not idea for it. 😭

Yeah, it's a bit weird. I'm not sure why it didn't work for that version

Setup lazy loading packer. Working perfectly fine. Please welcome to use it as a POC
https://gist.github.com/horseinthesky/26d813d2974b27b5d142bb8a412d2ba3


Caching updates

What's New?

Fix a bug where farm designer would download the same icon more than once. (memoize HTTP requests)

Coverage increased (+0.01%) to 77.594% when pulling 9ece0718e3ecda98e88a14b8ce9c0e51aa11ece4 on RickCarlino:regimen_item_constraint into cccb1a765dddeda4a0526a6d4e7c285d6ba9b280 on FarmBot:master.


After adding an altLabel, the vocabulary in SKOSMOS fails to load.

After adding the alternative label property to the term, the vocabulary cannot be loaded in SKOSMOS. There is an error message: 'Top hierarchy cannot be loaded'.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

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

Smartphone (please complete the following information):

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

Additional context
Add any other context about the problem here.

I could not reproduce the problem, on my side it worked for a general term. Could you provide more details? E.g. a screenshot of the filled "adding property popup" and how the terms looks like after adding the altLabel property (and breaking skosmos) would be great!

Investigation showed that the problem was that the altLabel was set to URI which does not work. It has always to be string. Close this issue, broader context can be found in #229


npmjs.org site point to wrong github url

When I go to https://www.npmjs.com/package/express
and then follow the link for the Github repo.. it takes me to https://github.com/expressjs/express  instead of this repo url of https://github.com/strongloop/express

It may be wrong, but the URL sounds about right to me.


If image has no extension not reconized as image

When i paste in an image in the href without an image extension, like this for example: https://picsum.photos/1200/700/?image=40
The lightbox will be opened as a iFrame and i get (except for Chrome) unexpected styling results.

If i put in an image with an extension, like this for example: https://media.architecturaldigest.com/photos/59b04f5ddd88d32f9bd9c633/master/pass/AJN_HW_Abu_Dhabi_Louvre_04 © TDIC, Architect Ateliers Jean Nouvel.jpg
It works great in all browsers and the lightbox is not in a iFrame.

You can add data-glightbox="type: image" to your a tag so glightbox knows it's an image.


Revert "xorg.xorgserver: 1.20.13 -> 21.1.3"

This reverts commit<PHONE_NUMBER>a2c5c6bf6775ee2f90c4eca0e39223.
Fixes #170856: issues of some users.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

According to testing on the issue, reverting the driver bumps from PR #153994 isn't needed to fix the issues.  (There are no newer releases for -ati and -nouveau.)
However, there's a newer release of xorg-server-1.20.14, but the affected people haven't tested it (yet), so I can't be confident that it didn't backport the regression.  (There is some modesetting change.)   You can try https://github.com/vcunat/nixpkgs/commits/p/xorg-server_bump

We've been using 21.1.3 for a very long time and I don't recall people reporting problems, so I'd hope it would be OK even without doing more testing beforehand.

However, there's a newer release of xorg-server-1.20.14, but the affected people haven't tested it (yet), so I can't be confident that it didn't backport the regression. (There is some modesetting change.) You can try https://github.com/vcunat/nixpkgs/commits/p/xorg-server_bump

Can confirm reverting to xorg-server-1.20.14 is solving the issue for me.

With the amounts of rebuilds we should target staging-next at least.

I assume .14 will be preferable to .13, so I added that here now, but more testing would still be nice.

I just switched to this branch, and I can confirm that this still works, whereas the latest nixos-unstable still triggers the issue for me. Thanks!

I think we have enough feedback to stage this at least for unstable.

I think we have enough feedback to stage this at least for unstable.

I am suffering this issue too. Can I know how to apply this PR to configuration.nix? I'm new into NixOS and it's hard to know what I have to change.
I did
...
let
  staging = import
    (builtins.fetchTarball https://github.com/nixos/nixpkgs/tarball/staging-next)
    { config.allowUnfree = true; };
in

But I'm not sure what I have to change the next since I enabled xserver by services.xserver.enable = true;. I added staging.xorg.xorgserver into environment.systemPackages but Nix didn't build the correct version.

It's relatively easy to use a different nixpkgs version (for everything), e.g.:
$ nixos-rebuild -I nixpkgs=https://github.com/nixos/nixpkgs/archive/staging-next.tar.gz switch

It's relatively easy to use a different nixpkgs version (for everything), e.g.:
$ nixos-rebuild -I nixpkgs=https://github.com/nixos/nixpkgs/archive/staging-next.tar.gz switch

Thanks for your answer. Is there a good way to apply only for the related xserver package? I found it takes a lot of time to build the packages without cache.

The very easiest way I know is to check out nixpkgs of whatever version you want, cherry-pick this pair of commits, and use the above syntax with a local directory instead of URL.
Almost all packages should be in cache: https://hydra.nixos.org/jobset/nixpkgs/staging-next


do not set window.jQuery except for global file

fixes #187

Can a test be added for this?

@chasenlehara maybe.  I'll see what I can do.

@chasenlehara https://github.com/bitovi/funcunit/pull/197/commits/4fc59a588b21da398764b491f6d5d95267138358


Split into multiple functionalities to compensate for lack of APN lookup

This includes:

Add XML parser for address endpoint
Add interface though client with address endpoint to allow address_key to be retrieved
Allow property lookup via address_key over apn/fips
Add relevant tests for new functionalities
Add fixtures for new tests being mocked

Looks good :+1: awesome work!

Once you're ready feel free to merge and I'll release to rubygems @jonahoffline


Search - Grouped expenses show User submits to User instead of to Workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.5-4
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Launch New Expensify app.
Create a new workspace.
Go to workspace chat.
Submit two expenses.
Go to Search.
Go to Shared (important).

Expected Result:
The grouped expenses will show that user submits to the workspace.
Actual Result:
The grouped expenses shows that user submits to the same user.
On web layout, it displays correctly, which is user submits to the workspace.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/487d3cb7-b702-4783-ad54-6f9807b429fa

View all open jobs on GitHub

@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

We think this issue might be related to the #collect project.

Production

@luacmartins - Just wanted to confirm that the expected steps are correct on this one: we want to show the user or workspace being submitted to on the grouped UI?

We should be showing the workspace as submitted to

I'm pretty sure this comes from this PR. @c3024 @brunovjk could you please take a look?

transactionItem has a reportType field to check if the transaction is an expense. reportItem does not have it. I think ideally backend should send reportType for reportItem as well.
We can just use type of one of the transactions' reportType also to check if it is an expense report without any changes on backend.

@c3024 @luacmartins - Should we revert the PR and make the changes to the backend and update the original PR?

I have some draft PRs up, I'll finish them once I'm done with a call. Meanwhile, we can demote this to NAB since part of the fix is in Auth.

@alexpensify for clarify, there's no payment due on this issue. It'll be handled in https://github.com/Expensify/App/issues/44093

Noted, thank you for that update!

Hello @luacmartins :D I was about to fill out the BugZero Checklist, I'm confused, does this issue count as a regression for this PR? Thanks.

I don't think so, they had different root causes.

[x]  [@brunovjk] The PR that introduced the bug has been identified. Link to the PR: N/A
[x]  [@brunovjk] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x]  [@brunovjk] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x]  [@brunovjk] Determine if we should create a regression test for this bug. Yes
[x]  [@brunovjk] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. * Since there's no payment due on this issue. It'll be handled in 44093, the regression test can be the same.

Based on this update: https://github.com/Expensify/App/issues/45013#issuecomment-2228931662, there is no required payment action. Closing!


Update remove-license-from-shared-mailbox.md

Updated the document to reflect that no  EXchange online Plan 2 is required if assigning M365 for defender.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8657

@SKjerland Please merge this PR. Thanks


Possible new issue template improvements

@emackey brought up VS Code's way of doing it and it's pretty nice, especially since it will help direct people to the forum:
https://github.com/Microsoft/vscode/issues/new/choose
Implementation here:
https://github.com/Microsoft/vscode/tree/master/.github/ISSUE_TEMPLATE

Oh that is awesome.

@OmarShehata perhaps a good one for you once the glTF extensions and clipping planes converge?

That's really cool! @pjcozzi  Yeah I can propose something and see what people think.


Datasets for other PLs

Hi. The dataset you guys made is great. However, since Python3, C, and C++ are also widely used in CS assignments, do you guys have any plans to make datasets for these languages as well?

Yes, we plan to do similar thing for Python next year. The project is slightly delayed due to pandemic. I will keep you posted. In case it is urgent, you can translate the Java data set to other programming languages. You can push the translated data set here also if you want. I am happy to merge it with mine.


mu: 1.4.12 -> 1.4.13

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/djcb/mu/releases.
meta.description for mu is: "A collection of utilties for indexing and searching Maildirs"
meta.homepage for mu is: "https://www.djcbsoftware.nl/code/mu/"
meta.changelog for mu is: "https://github.com/djcb/mu/releases/tag/1.4.13"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.4.13 with grep in /nix/store/smvl7fzbj2x98d659si485p9knf1k0gn-mu-1.4.13

directory tree listing: https://gist.github.com/be9d968a4a42db840383c1da101b3b88

du listing: https://gist.github.com/c0aadb1908bece34fbd412bd65e32213

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
mu

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/smvl7fzbj2x98d659si485p9knf1k0gn-mu-1.4.13 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/smvl7fzbj2x98d659si485p9knf1k0gn-mu-1.4.13
ls -la /nix/store/smvl7fzbj2x98d659si485p9knf1k0gn-mu-1.4.13/bin

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

1 package built:

mu

Maintainer pings
cc @antono @peterhoeg for testing.

Works for me!


[refactor] #3526: Allow only a fixed set of signature verification conditions

Description
Instead of allowing arbitrary iroha expressions in SignatureVerificationCondition, allow only a fixed set of verification conditions
Linked issue
Closes #3526

Checklist

[x] Decide on the set of signature check conditions we want to allow
[x] Add unit tests
[x] Implement without using expressions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

119 of 129 (92.25%)  changed or added relevant lines in 5 files are covered.
5730 unchanged lines in 99 files lost coverage.
Overall coverage decreased (-1.2%) to 58.221%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client_cli/src/main.rs
0
3
0.0%

data_model/src/account.rs
108
115
93.91%

Files with Coverage Reduction
New Missed Lines
%

cli/src/main.rs
1
0.0%

cli/src/torii/pagination.rs
1
98.9%

config/base/src/runtime_upgrades.rs
1
51.72%

config/src/torii.rs
1
96.67%

core/src/smartcontracts/isi/block.rs
1
87.5%

crypto/src/merkle.rs
1
96.23%

data_model/derive/src/partially_tagged.rs
1
99.67%

data_model/src/domain.rs
1
47.37%

logger/src/lib.rs
1
95.15%

config/src/lib.rs
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-1.2%

Covered Lines:
21369

Relevant Lines:
36703

💛  - Coveralls


fix(OHIFv2):Fix a dependency issue on windows caused by node-gyp

The node-gyp version used by the docz installed for OHIFv2 is very old
and is incompatible with some recent python updates and other packaging
issues.  Just force a node-gyp newer version to be used.  No functional
changes.

Going to just let the e2e commit cover this one as it seems to take a bunch of overlapping files.


Attachment - Drag and drop of application files throws wrong error message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login with any account.
Choose any report, choose an Application file (Steam, slack,
Notice that the validation message says: "Attachment size must be greater than 240 bytes" even the size of attachment is 6MB.

Expected Result:
The attachment modal should show correct message.
Actual Result:
The attachment modal show incorrect message.
Workaround:
Move the validation fileExtension on to the top of isValidFile inside AttachmentModal
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] MacOS / Chrome  and Win chrome

Version Number: 1.2.42-1
Reproducible in staging?: y
Reproducible in production?: y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/209005262-abd82e65-0e22-4df6-9ace-eee36f4357ca.mov
https://user-images.githubusercontent.com/43996225/209005283-bb40ca8c-5103-4106-b8af-848b4cbcfef0.mp4
Expensify/Expensify Issue URL:
Issue reported by:  @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1671512078960629
View all open jobs on GitHub

Will take a look at this one.

Are we sure this is replicable?

@muttmuure Yeah, it's replicable when drag and dropping, not when using the attachment picker:
https://user-images.githubusercontent.com/4741899/211430291-54699d5a-1d41-4cd0-92a9-89e479d75a12.mp4

Although I think this is just related to the OS's file provided when dragging and dropping vs using the image picker, since both flows hit the same logic: https://github.com/Expensify/App/blob/4e915a957e343b30e6a233d80735fe70a42037a4/src/components/AttachmentModal.js#L150-L185
I think a simple solution would be just to check for file type first in this method, since that would give us some consistency when we can't control what receive from the OS/browser (unless we can?)

I have a question, if my solution (Posted in Workaround of this issue) is also the solution that contributor used to fix this bug, should I rewarded? @yuwenmemon  😂

@muttmuure can you issue payment and complete the regression test steps today? Also address @hungvu193 's question above.  If needed, post in #contributor-plus to discuss, thanks.

Will get to this today - I have a lot of other issues to get through but I will make sure this is done before I log off.

OK getting to this now

Posted a buddy check here https://expensify.slack.com/archives/C01SKUP7QR0/p1674236286387249

I've invited @hungvu193 but @Santhosh-Sellavel isn't showing under our company hires

You're both invited to apply for the job. Thanks!

Applied for the job!

Everyone is paid. Great hustle everybody.


Fix wrong sender when send slack webhook

Fix #7265

CI fail seems unrelated but maybe you can restart it.

Codecov Report

Merging #7918 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #7918      +/-   ##
==========================================
+ Coverage   41.43%   41.43%   +<.01%
==========================================
  Files         478      478
  Lines       63943    63943
==========================================
+ Hits        26492    26496       +4
+ Misses      34000    33996       -4
  Partials     3451     3451

Impacted Files
Coverage Δ

models/release.go
52.94% <100%> (ø)
:arrow_up:

models/repo_list.go
73.09% <0%> (+1.01%)
:arrow_up:

modules/log/event.go
65.64% <0%> (+1.02%)
:arrow_up:

Continue to review full report at Codecov.

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

First PR merged by me 🎉
Please send backport.


issue with open files

running bin/benchpark setup while packages.yaml is opened in vim results in problems for ramble -P -D ...
==> Error: 'utf-8' codec can't decode byte 0xb3 in position 17: invalid start byte

It seems that some vim temp files are used in the background. When I close the file and run ramble -P -D ... again i get a new error pointing to some .swp file from vim:
==> Error: [Errno 2] No such file or directory: '/vol0005/mdt3/data/ra000020/u10016/benchpark/test.gnu/amg2023/openmp/RCCS-Fugaku-Fujitsu-A64FX-TofuD/workspace/configs/auxiliary_software_files/.packages.yaml.swp'

@jdomke The bin/benchmark setup step creates a symlink to all the config files including configs/RCCS-Fugaku-Fujitsu-A64FX-TofuD/auxiliary_software_files/.packges.yaml.swp (which will be present is the packages.yaml is opened in vim).
If between bin/benchmark setup and ramble -P -D ..., the vim temp file gets deleted, we get the
No such file or directory error.
The workaround is to remove the symlink /vol0005/mdt3/data/ra000020/u10016/benchpark/test.gnu/amg2023/openmp/RCCS-Fugaku-Fujitsu-A64FX-TofuD/workspace/configs/auxiliary_software_files/.packages.yaml.swp
@pearce8 @scheibelp We should exclude non-config files from symlink creation in bin/benchmark setup


papers: Make thumbnailer file point to absolute path

Description of changes
Allows use with nautilus(bubblewrap) even if installed in home.packages
Things done

Built on platform(s)

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

[x] Tested basic functionality of all binary files (usually in ./result/bin/)

[x] Fits CONTRIBUTING.md.

Yeah, that would be great!

Is there anything missing here or does it usually take some time for it to get merged?

Sorry, was waiting for CI and then forgotten about it.

Manual pull request?

Yes, manual pull request will be needed.


[e2e test] Test mask rom bootstrap properties

Check that the Mask ROM enters bootstrap mode.
The the jedec ID of the Mask ROM in bootstrap mode.
The the SFDP of the Mask ROM in bootstrap mode.

Signed-off-by: Chris Frantz<EMAIL_ADDRESS>

This is still a bit of a work in progress.
This covers mask_rom_e2e_bootstrap_success and mask_rom_e2e_bootstrap_config.  I combined these cases into one test program because the second one is trivial after entering bootstrap mode.
We need to decide on some standard things to print for each test case and write the infrastructure to do it.  Things like:
starting test_bootstrap_entry...
test_bootstrap_entry PASSED.

or

starting test_jedec_id...
test_jedec_id FAILED


Fixes friend declaration tag mismatch

InstanceBase is a struct, but declared as class.
./servers/visual/rasterizer.h:116:10: warning: class 'InstanceBase' was previously declared as a struct; this is valid, but may result in linker errors under the Microsoft C++ ABI
      [-Wmismatched-tags]
                friend class InstanceBase;
                       ^
./servers/visual/rasterizer.h:106:9: note: previous use is here
        struct InstanceBase;
               ^

Thanks!


Replace defences in urban_centres with utils.defence functions.

Description of the Feature to be Added
Some defences in the urban_centres module should be replaced with  utils.defence functions.
(OPTIONAL) Suggested Implementations
Additional context

Would you say this is a copy of #160 @SergioRec ?

Sorry, didn't see you had created an issue already. Closing as duplicate.


Lookup for non-existent records has different behavior for online and offline tables

MobileServiceTable.lookup() fails if the record does not exist
MobileServiceSyncTable.lookup() returns undefined if the record does not exist

https://github.com/Azure/azure-mobile-apps-js-client/pull/150 closes https://github.com/Azure/azure-mobile-apps-js-client/issues/140


build: don't compile classes for /es build

/es build output classes are compiled, so when someone want's to use webpack to bundle/chunk for evergreen browsers he has to explicitly include WC es5-shim polyfill.
Is there any particular reason why we ship es/ this way ? I think it should be consumer responsibility to compile what he imports ( for both tree shaking and compile output )
TL;DR:
es/ should include similar output like esnext/ except for relative paths to preact and .js suffixes in imports

Oh I completely missed "new Readme"

If you want to deliver native classes, you can configure Webpack to pull in a version of Skate that's been transpiled to the latest ES specification. More about this approach is detailed in this blog post.

I don't like that explicit churn within webpack config but I guess that's best we can get as of today. Maybe some tiny function as npm module could be neat so users don't have to go through that article ceremony everytime ? Just thinking out loud here :)
anyway Closing

I've since updated the 5.x build. It's now a bit more clear. It has specific babel configs for both es and esnext, where esnext is untranspiled classes and es is only import / export + es5.

esnext is untranspiled everything not just classes right ?

It will transpile everything to es2015. So you can use es2016 and es2017 and have a consistent target.

yup, basically allows running skate + html-lit without ZERO build step

Yeah, but I need to work out if I broke web compat imports in #1189 :p.

whoops! :D


Issue with updateOAuthApp() method in org.wso2.carbon.analytics.idp.client.external.dao.OAuthAppDAO.java  class

Description:
In updateOAuthApp() method in org.wso2.carbon.analytics.idp.client.external.dao.OAuthAppDAO.java class, there is a problem set arguments for the following SQL query.
 ps.setString(1, oAuthApplicationInfo.getClientId());
            ps.setString(2, oAuthApplicationInfo.getClientSecret());
            byte[] encrypt = this.secretRepository.encrypt(oAuthApplicationInfo.getClientSecret().getBytes("UTF-8"));                                                                                ps.setBytes(3, encrypt);

It should be corrected as below.
ps.setString(1, oAuthApplicationInfo.getClientId());
          byte[] encrypt = this.secretRepository.encrypt(oAuthApplicationInfo.getClientSecret().getBytes("UTF-8"));
          ps.setBytes(2, encrypt);
          ps.setString(3, oAuthApplicationInfo.getClientName());

Version/4.3.0
Priority/High
Severity/Major
type/Bug

Fixed by https://github.com/wso2/carbon-analytics-common/pull/653


Getting feedback but cannot control the devices

I inserted the ip and the port then added the configuration of the device (relay switch) i am getting feedback but when i turn it on it turns back to off and doesn't  turn the light on or off its not sending the change of state but i am getting the realtime feedback correct

Hello,please i added the ip and port and the configuration i am not getting feedback can somebody helps me please

This is happening to me too, it was working correctly

Hello, for me it didn't work yet please can you send me the your
coniguration for the very first time when it was working like a snapshot
On Fri, 7 Jul 2023, 15:21 Moises Ortiz, @.***> wrote:

This is happening to me too, it was working correctly
—
Reply to this email directly, view it on GitHub
https://github.com/eyesoft/home_assistant_buspro/issues/2#issuecomment-1625574478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3W7M5WG6X6HYC23DOQYMW3XPASQXANCNFSM6AAAAAAT7WE45A
.
You are receiving this because you commented.Message ID:
@.***>

I managed to solve it
for some reason my Module changed of IP without notice (I thought I reserved the IP in DHCP but not)
I set a static IP and fixed the IP in the configuration in HAS.
If the Host is wrong on HASS you will only be able to track the status of the devices but you wont be able to change the state (turn on or off the lights for example)
In home assistant add HDL host, in this case <IP_ADDRESS> and the port that appears there 6000, modify configuration.yml
for example this is mine
`# HDL
light:

platform: buspro
running_time: 0
devices:
#Cuarto Moises
1.1.1:
name: Lampara Moises
dimmable: true
1.1.3:
name: Luz Moises
dimmable: true
#Garaje
1.9.12:
name: Luz Garaje
dimmable: false
binary_sensor:
platform: buspro
devices:
address: 1.152
name: Sensor PA
type: motion
device_class: motion`

Hopefully it works for you

Thank you but  i did the same thing i am able the status but cannot operate
.Please do i name like this: name:"moises" or
On Fri, 7 Jul 2023, 22:41 Moises Ortiz, @.***> wrote:

I managed to solve it
for some reason my Module changed of IP without notice (I thought I
reserved the IP in DHCP but not)
I set a static IP and fixed the IP in the configuration in HAS.
If the Host is wrong on HASS you will only be able to track the status of
the devices but you wont be able to change the state (turn on or off the
lights for example)
In home assistant add HDL host, in this case <IP_ADDRESS> and the port
that appears there 6000, modify configuration.yml
for example this is mine
`# HDL
light:

platform: buspro
running_time: 0
devices:
#Cuarto Moises
1.1.1:
name: Lampara Moises
dimmable: true
1.1.3:
name: Luz Moises
dimmable: true
#Garaje
1.9.12:
name: Luz Garaje
dimmable: false
binary_sensor:
platform: buspro
devices:
address: 1.152
name: Sensor PA
type: motion
device_class: motion`

[image: image]
https://user-images.githubusercontent.com/5110242/251873892-e748a002-246b-414f-8f06-b78b6f58758f.png
[image: image]
https://user-images.githubusercontent.com/5110242/251873983-04abd127-c708-4255-94ff-caa61ab32691.png
[image: image]
https://user-images.githubusercontent.com/5110242/251874016-8570a582-7cf7-4377-8f13-3a19e44ddd5f.png
Hopefully it works for you
—
Reply to this email directly, view it on GitHub
https://github.com/eyesoft/home_assistant_buspro/issues/2#issuecomment-1626330280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3W7M5SOLNDK65QEWQUIIB3XPCF73ANCNFSM6AAAAAAT7WE45A
.
You are receiving this because you commented.Message ID:
@.***>

Thank you but i did the same thing i am able the status but cannot operate .Please do i name like this: name:"moises" or
…
On Fri, 7 Jul 2023, 22:41 Moises Ortiz, @.> wrote: I managed to solve it for some reason my Module changed of IP without notice (I thought I reserved the IP in DHCP but not) I set a static IP and fixed the IP in the configuration in HAS. If the Host is wrong on HASS you will only be able to track the status of the devices but you wont be able to change the state (turn on or off the lights for example) In home assistant add HDL host, in this case <IP_ADDRESS> and the port that appears there 6000, modify configuration.yml for example this is mine # HDL light: - platform: buspro running_time: 0 devices: #Cuarto Moises 1.1.1: name: Lampara Moises dimmable: true 1.1.3: name: Luz Moises dimmable: true #Garaje 1.9.12: name: Luz Garaje dimmable: false binary_sensor: platform: buspro devices: address: 1.152 name: Sensor PA type: motion device_class: motion [image: image] https://user-images.githubusercontent.com/5110242/251873892-e748a002-246b-414f-8f06-b78b6f58758f.png [image: image] https://user-images.githubusercontent.com/5110242/251873983-04abd127-c708-4255-94ff-caa61ab32691.png [image: image] https://user-images.githubusercontent.com/5110242/251874016-8570a582-7cf7-4377-8f13-3a19e44ddd5f.png Hopefully it works for you — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3W7M5SOLNDK65QEWQUIIB3XPCF73ANCNFSM6AAAAAAT7WE45A . You are receiving this because you commented.Message ID: @.>

Hello.
Im facing this issue. Controlling the HDL show status on Homeassistant. But i cant seem to be able to control from Homeassistant.
Anything i can do?

This happened to me , my HDL host address was wrong changed it , restarted has and worked again

Okay i did that and now all is working great!
Perfect!


The following property in '/SettingsJson/Inputs/0' isn't supported: FileInput.

Describe the bug
A clear and concise description of what the bug is.
Not understanding why I am receiving an issue upon deploying from the CDK due to the key FileInput in my settingsJson config.
To Reproduce
Steps to reproduce the behavior.
Example JSON:
settingsJson:
{
        "Inputs": [
          {
            "TimecodeSource": "ZEROBASED",
            "VideoSelector": {},
            "AudioSelectors": {
              "Audio Selector 1": {
                "DefaultSelection": "DEFAULT",
                "SelectorType": "TRACK",
                "Tracks": [1]
              }
            },
            "FileInput": "s3://{inputBucket}/{key}.flac",
          }
        ],

Expected behavior
A clear and concise description of what you expected to happen.
I would expect FileInput to be recognized given that the console uses it to create jobs
Please complete the following information about the solution:

[ ] Version: [e.g. v1.0.0]
[ ] Region: [e.g. us-east-1]
[ ] Was the solution modified from the version published on this repository?
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[ ] Have you checked your service quotas for the sevices this solution uses?
[ ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.
This output was given to me by the console; however it will not deploy:
{
    "Inputs": [
      {
        "TimecodeSource": "ZEROBASED",
        "VideoSelector": {},
        "AudioSelectors": {
          "Audio Selector 1": {
            "DefaultSelection": "DEFAULT",
            "SelectorType": "TRACK",
            "Tracks": [
              1
            ]
          }
        },
        "FileInput": "s3://{inputBucket}/{key}.mp3"
      },
      {
        "TimecodeSource": "ZEROBASED",
        "VideoSelector": {},
        "AudioSelectors": {
          "Audio Selector 1": {
            "DefaultSelection": "DEFAULT",
            "SelectorType": "TRACK",
            "Tracks": [
              1
            ]
          }
        },
        "FileInput": "s3://{inputBucket}/{key}.flac"
      }
    ],
    "OutputGroups": [
      {
        "Name": "File Group",
        "OutputGroupSettings": {
          "Type": "FILE_GROUP_SETTINGS",
          "FileGroupSettings": {
            "Destination": "REDACTED"
          }
        },
        "Outputs": [
          {
            "AudioDescriptions": [
              {
                "CodecSettings": {
                  "Codec": "MP3",
                  "Mp3Settings": {
                    "RateControlMode": "CBR",
                    "SampleRate": 44100,
                    "Bitrate": 128000
                  }
                },
                "AudioSourceName": "Audio Selector 1"
              }
            ],
            "ContainerSettings": {
              "Container": "RAW"
            },
            "NameModifier": "full-128",
            "Extension": "mp3"
          }
        ],
        "CustomName": "MP3 128 Kbps"
      },
      {
        "Name": "File Group",
        "OutputGroupSettings": {
          "Type": "FILE_GROUP_SETTINGS",
          "FileGroupSettings": {
            "Destination": "REDACTED"
          }
        },
        "Outputs": [
          {
            "AudioDescriptions": [
              {
                "CodecSettings": {
                  "Codec": "MP3",
                  "Mp3Settings": {
                    "RateControlMode": "CBR",
                    "SampleRate": 44100
                  }
                },
                "AudioSourceName": "Audio Selector 1"
              }
            ],
            "ContainerSettings": {
              "Container": "RAW"
            },
            "NameModifier": "full-192",
            "Extension": "mp3"
          }
        ],
        "CustomName": "MP3 192 Kbps"
      },
      {
        "Name": "File Group",
        "OutputGroupSettings": {
          "Type": "FILE_GROUP_SETTINGS",
          "FileGroupSettings": {
            "Destination": "REDACTED"
          }
        },
        "Outputs": [
          {
            "AudioDescriptions": [
              {
                "CodecSettings": {
                  "Codec": "AAC",
                  "AacSettings": {
                    "Bitrate": 32000,
                    "CodingMode": "CODING_MODE_2_0",
                    "SampleRate": 44100,
                    "CodecProfile": "HEV1"
                  }
                },
                "AudioSourceName": "Audio Selector 1"
              }
            ],
            "ContainerSettings": {
              "Container": "MP4",
              "Mp4Settings": {}
            },
            "NameModifier": "full-32",
            "Extension": "mp4"
          }
        ],
        "CustomName": "MP4 32 Kbps"
      },
      {
        "Name": "File Group",
        "OutputGroupSettings": {
          "Type": "FILE_GROUP_SETTINGS",
          "FileGroupSettings": {
            "Destination": "REDACTED"
          }
        },
        "Outputs": [
          {
            "AudioDescriptions": [
              {
                "CodecSettings": {
                  "Codec": "AAC",
                  "AacSettings": {
                    "Bitrate": 192000,
                    "CodingMode": "CODING_MODE_2_0",
                    "SampleRate": 44100
                  }
                },
                "AudioSourceName": "Audio Selector 1"
              }
            ],
            "ContainerSettings": {
              "Container": "MP4",
              "Mp4Settings": {}
            },
            "NameModifier": "full-192",
            "Extension": "mp4"
          }
        ],
        "CustomName": "MP4 192 Kbps"
      },
      {
        "Name": "File Group",
        "OutputGroupSettings": {
          "Type": "FILE_GROUP_SETTINGS",
          "FileGroupSettings": {
            "Destination": "REDACTED"
          }
        },
        "Outputs": [
          {
            "AudioDescriptions": [
              {
                "CodecSettings": {
                  "Codec": "AAC",
                  "AacSettings": {
                    "Bitrate": 64000,
                    "CodingMode": "CODING_MODE_2_0",
                    "SampleRate": 44100,
                    "CodecProfile": "HEV1"
                  }
                },
                "AudioSourceName": "Audio Selector 1"
              }
            ],
            "ContainerSettings": {
              "Container": "MP4",
              "Mp4Settings": {}
            },
            "NameModifier": "full-64",
            "Extension": "mp4"
          }
        ],
        "CustomName": "MP4 64 Kbps"
      }
    ],
    "TimecodeConfig": {
      "Source": "ZEROBASED"
    }
  }

Thanks for your feedback. We are currently reviewing this with our engineering team.


Add run command to CLI

Adds run command to CLI

if no path is sent, it runs the current project's main (like build, but also running the binary)
if a path is sent, it builds and runs that concrete file in single file mode.

Adds an example project, can be used to test the run command in project mode.

Example usage:
cargo run -- run examples/fib_if.con
# or
concrete run examples/fib_if.con

tip: to install the binary, run:
cargo install --path crates/concrete

Codecov Report
Attention: Patch coverage is 0% with 137 lines in your changes are missing coverage. Please review.

Project coverage is 57.74%. Comparing base (53cddd9) to head (5573d2c).
Report is 13 commits behind head on main.

Files
Patch %
Lines

crates/concrete_driver/src/lib.rs
0.00%
137 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
+ Coverage   57.35%   57.74%   +0.38%
==========================================
  Files          34       34
  Lines        3956     3992      +36
==========================================
+ Hits         2269     2305      +36
  Misses       1687     1687

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


New version: EFF.Certbot version 1.25.0

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 454
Microsoft Reviewers: Open in CodeFlow

/azp run


More sample compressions

🚀 🚀 Pull Request
https://activeloop.atlassian.net/browse/AL-1189
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes
Add bmp and gif

i saw you snuck sample.__array__ in there, nice lil surprise


ReadSettings / autoProcess reformat

The options in the MP4 section have gotten rather long and cumbersome, would like to break that apart into more sections (video, audio, subtitle, etc)
Would also like to overhaul readSettings.py to include more dedicated standardized parsing methods
Ideally would do this in a way that would migrate old configs over to not break anyone's setup

https://github.com/mdhiggins/sickbeard_mp4_automator/tree/settings
This branch contains the settings overhaul, appreciate any testing

@RandomNinjaAtk @stevemk14ebr @JySzE
Name dropping a few of the recently active people on here to see if I can get some testers before I merge this back to the main branch. If you can, make sure it migrates all your settings appropriately

Pulled the trigger as my prelim tests looked good, closing for now

Okay so a few things I noticed:
Some values I had set to nothing were then changed to a value of "0" and one was changed to 0 when it was actually "5.1"
Original:
"video-bitrate = "
"video-max-width = "
"h264-max-level = 5.1"
"max-audio-channels = "
"ignore-truehd = False"
"convert-mp4 = True" < this is completely missing from the reformatting version.
Reformatted:
"bitrate = 0"
"max-width = 0"
"max-level = 0"
"max-channels = 0"
"ignore-truehd = " < no value on reformat when original was "False"
You can see if I missed anymore issues here:
Here is my original INI file:  original.autoProcess.txt
Here is the reformatted INI file: reformatted.autoProcess.txt
Side note:
Also another thought so every time you run the script it doesn't check the ENTIRE ini file for formatting is to do versioning of the ini file so lets say this INI file would be labeled somehow as "Version 1".
If the script reads that its Version 1 and that matches the current commits version, it wont attempt to reformat the entire thing every time it runs, and next commit if you change or add something to the ini file you just change the version numbering and it will check versioning. (if this is an issue at all).

Dang closed 13 seconds before I posted.  I was too slow 😆

I appreciate you getting back to me still!
I rewrote how all the options are parsed because the old method was kind of sloppy and all over the place and I really wanted to clean that up but in a way that wouldn't screw up people's confgs
For some of the settings now 0 is treated like None and I'm using stricter variable types so that's why you're seeing the 0 in lots of stuff. Behavior should still be the same its just the script filling in things
I fixed the level not migrating correctly, had to do with me tagging it as an int instead of float
It only does the migration if it detects the old version of the file so should only run once. It doesn't actually read the entire file it just looks to see if the old "MP4' section is present indicated the old format. I thought about versioning but with versioning I would still need to have all the old code to interpret the other format which wasn't the goal.
the ignore-truehd setting also was reworking. Instead of being a boolean value like before its not an array of extensions. So you could still ignore-truehd for say, MP4 files without having to ignore it for other formats. More flexible this way. If it was set to false before having it blank is the same equivalent
078c7eb47481ca7e05613e3cb9a535f865cddc7f

Excellent news, tested again and everything seems to be working great.
We appreciate all the hard work.


New version: Yarn.Yarn version 1.22.19

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Yarn
Yarn

Version
1.22.19
1.22.19

Publisher
Yarn Contributors
Yarn Contributors

ProductCode
{C719DC4C-8FB0-4BB1-B622-A165776D8AF8}
{C719DC4C-8FB0-4BB1-B622-A165776D8AF8}

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1493
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

Running winget install --manifest D:\TRANSFER\2eaf3f15-a9d0-ec11-b701-0022484bf065\Manifest.yaml --accept-package-agreements
End winget install --manifest D:\TRANSFER\2eaf3f15-a9d0-ec11-b701-0022484bf065\Manifest.yaml --accept-package-agreements
The FileSystemWatcher has detected an error System.IO.ErrorEventArgs
The file system watcher experienced an internal buffer overflow: Too many changes at once in directory:C:\.
Launching executable file: C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.

An excerpt from the log file. Was Windows Update running at the same time as the install?

@wingetbot waivers Add Validation-Executable-Error