feat: mapper supports returning array of events

Modification to the appendAction function to facilitate returning either an object or array of objects in the custom mapper.

Thanks for this. I may add a test case before cutting a build but this looks great @meatwallace.

a build with this fix would be great!

@gsdean Coming tonight. Sorry for the wait.


fix(ui): center failed payment error modal dialog

Motivation and Context:
Fix #3183
How Has This Been Tested?
Manually
Screenshots (if appropriate):

Checklist:

[x] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 22.783% when pulling b08353c116779019752207fab16e3a20cb569608 on bolatovumar:fix-3183 into d800a0199012af00675bb4bb71a8d672370d6569 on LN-Zap:master.


Ability to turn off "Show Branch" tooltip in terminal

I like to copy the current git branch name by double clicking it in my integrated terminal. However, gitlens is creating a tooltip on the branch name on hover which breaks my double click selection.

Where is this code coming from? Is it possible to turn this off?

@tgreen7 Unfortunately there isn't a way to turn this off currently, but I will add a setting.
Although, the terminal links shouldn't break any existing behavior -- could you provide more details on how it is breaking your workflow?

@eamodio It just blocks the double click selection. When you double click the mouse on text it will select the whole word. But the tooltip blocks the click.

@tgreen7 Hrm, I can't reproduce that, might be OS specific? But even if I could repo, this would be a bug in VS Code itself as the VS Code terminal links API shouldn't cause the impact you are experiencing. Can you open an issue on the VS Code repo so it can get fixed there?

There is now a new gitlens.terminalLinks.enabled setting to control whether terminal links are enabled.
Can you please verify this fix in tomorrow's insiders edition?
You can install the insiders edition from here. Be sure to disable/uninstall the stable version of GitLens first.

Perfect. Looks good!


-g cannot detect .mk

(Original issue 923 created by leesei on 2013-11-07T07:36:24.990802+00:00)
pygmentize -g Android.mk incorrectly highlights the make file
pygmentize -l make Android.mk does a better job

(Original issue 923 last updated on 2014-01-10T09:52:14.448353+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by birkenfeld on 2014-01-09T18:04:09.182630+00:00)
which lexer does it recognize? can you attach the Android.mk file?

(Original comment by leesei on 2014-01-10T04:27:04.826114+00:00)
I guess it's shell or no lexer, how to output the guessed lexer?
Here's the Android.mk I tested:
# Copyright 2007 The Android Open Source Project
#
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)

LOCAL_SRC_FILES := $(call all-subdir-java-files)
LOCAL_MODULE := pm
include $(BUILD_JAVA_LIBRARY)

include $(CLEAR_VARS)
ALL_PREBUILT += $(TARGET_OUT)/bin/pm
$(TARGET_OUT)/bin/pm : $(LOCAL_PATH)/pm | $(ACP)
        $(transform-prebuilt-to-target)

(Original comment by leesei on 2014-01-10T04:32:22.871721+00:00)
Screenshots for pygmentize output

(Original comment by birkenfeld on 2014-01-10T09:41:54.704682+00:00)
Closes #923: remove blanket nonzero analyse_text returns, and add an analyse_text for Makefile lexer
→ <>

(Original comment by birkenfeld on 2014-01-10T09:41:56.906125+00:00)
Thanks, that should now be working as intended.


Nonce doesn't change per request in production build

Hi,
I've added a CSP but I'm having an issue with nonces not changing for a production deployment.
Running npm run dev the nonce changes per request.

Running npm run build , the nonce doesn't change. It's always this:

This happens in my local environment build and in production build which is Cloudflare Pages.
I tried a couple of versions both having the same result:
nuxt-security: 2.0.0-rc.9
nuxt-security: v2.0.0
nuxt: 3.12.3
The CSP I'm using is the same as listed on the FAQ page for Cloudflare config (https://nuxt-security.vercel.app/documentation/advanced/faq)
Is this a known issue and maybe I've missed a configuration?

This is strange
It looks like node:crypto is not working correctly here. There is a Cloudflare setting for this, so it could explain the issue.
But the very strange part is that you said this happens in your local environment build. Not normal at all.
How to you build locally?

Hi @vejja,
Thanks for the quick response.
I just run npm run build.
Then preview the build with npx wrangler pages dev dist/
If there is something I can do in Cloudflare to get node:crypto working then that would be great.

https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/
I think they say you need the nodejs_compat_v2 flag

No luck unfortunately.
I tried both nodejs_compat and nodejs_compat_v2 with a compatibility date of 2024-09-23 or later but the nonce is still the same.

Locally, what if you npm run build and then node .output/server/index.mjs?
Do you have a nonce?

node .output/server/index.mjs gives output Listening http://[::]:3000
Do I need to configure a host IP somehow?

Just open Chrome on localhost:3000

Yeah I tried that and strangely I'm seeing a really old version of the website that appears to not have nuxt-security at all on http://localhost:3000/.
No idea how that can happen. npm run dev / build is showing the latest version which is a relief.

wow this is becoming really tough to debug 😂

do you have PWA?
do you have a zombie process listening on port :3000?
rm -rf node_modules
npm install
give us your wrangler.toml
give us your nuxt.config.ts

No PWA
No zombie process (restarted machine)
Deleted node_modules and reinstalled

nuxt.config.ts
> // https://nuxt.com/docs/api/configuration/nuxt-config
> export default defineNuxtConfig({
>   app: {
>     head: {
>       charset: 'utf-8',
>       viewport: 'width=device-width, initial-scale=1',
>     },
>   },
>
>   debug: false,
>
>   devtools: {
>     enabled: false
>   },
>
>   gtag: {
>     id: '',
>     // loadingStrategy: 'async'
>   },
>
>   image: {
>   },
>
>   nitro: {
>     preset: "cloudflare-pages",
>   },
>
>   modules: [
>     "@nuxtjs/sitemap",
>     "nitro-cloudflare-dev",
>     "@nuxtjs/robots",
>     ["nuxt-gtag", { enabled: process.env.NODE_ENV === 'production' }],
>     "@nuxt/image",
>     "nuxt-security"
>   ],
>
>   pages: true,
>
>   routeRules: {
>     // Don't add any /secret/** URLs to the sitemap.xml E.g
>     // '/secret/**': { robots: false },
>   },
>
>   runtimeConfig: {
>     // The private keys which are only available within server-side
>     myPrivateKey: 42,
>     // Keys within public, will be also exposed to the client-side
>     public: {
>       gtagId: '',
>       pageSize: 20,
>     }
>   },
>
>   security: {
>     headers: {
>       // crossOriginEmbedderPolicy: process.env.NODE_ENV === 'development' ? 'unsafe-none' : 'require-corp',
>       crossOriginEmbedderPolicy: 'unsafe-none',
>       contentSecurityPolicy: {
>         'img-src': ["'self'", 'data:'],
>         'script-src': [
>           "'self'",
>           'https:',
>           "'unsafe-inline'",
>           "'strict-dynamic'",
>           "'nonce-{{nonce}}'",
>           "'unsafe-eval'"
>         ]
>       },
>     },
>   },
>
>   site: {
>     defaultLocale: 'en', // not needed if you have @nuxtjs/i18n installed
>   },
>
>   sitemap: {
>     credits: false,
>     exclude: [
>       '/secret/**'
>     ],
>     sitemaps: {
>       pages: {
>         includeAppSources: true
>       }
>     }
>   },
>
>   ssr: true,
>
>   compatibilityDate: "2024-07-03"
> })

wrangler.toml
#:schema node_modules/wrangler/config-schema.json
name = ""
compatibility_date = "2024-09-24"
pages_build_output_dir = "./dist"
compatibility_flags = [ "nodejs_compat_v2" ]

# Bind a D1 database. D1 is Cloudflare’s native serverless SQL database.
# Docs: https://developers.cloudflare.com/pages/functions/bindings/#d1-databases
[[d1_databases]]
binding = "DB"
database_name = ""
database_id = ""

Thanks for all the help so far.

ok, remove nitro: preset from nuxt.config.ts, then npm run build then node ./output/server/index.mjs
open in Chrome, can you see the nonce ?

Yes! That worked. I can see a nonce now.
What are the ramifications of removing the nitro preset?
Is that required for Cloudflare Pages module "nitro-cloudflare-dev"?

What are the ramifications of removing the nitro preset?

I'm not 100% sure myself 😉
I'm just checking that everything works correctly in the local build, which is the case.
I'm not a Cloudflare expert, so I don't have a good knowledge of their terminology - but here is the basic stuff you need to know:

nonce require SSR
SSR requires a physical runtime (infrastructure) and an executable
the executable (aka Nitro) is provided by Nuxt when you do npm run build
Cloudflare has the infrastructure on Cloudflare Workers
Nitro has presets for Cloudflare Workers to be able to run the Nitro executable
Cloudflare Workers only support node:crypto with the special flag

I have no first-hand knowledge of how to make this whole stack run on Cloudflare, but my 2 cents are 'cloudflare_pages' probably stands for 'a CDN that can only deliver static files with no runtime' while 'cloudflare_module' probably means 'a full runtime environment that is able to run the Nitro executable'.
That's why I asked you to remove the nitro preset...
Now for better advice you should look here and here.
The first one is Nuxt's method to export its stack into Cloudflare. The second one is Cloudflare's method to import the Nuxt stack. Either one should work.

Thank you for your kind words @brewaa !
I'm actually concerned that under some kind of obscure combination of modules and deployment presets, we allow a static bogus nonce value to be generated. This would in fact be a breach of the RFC.
I did have a deeper look in the meantime and I would greatly appreciate if you could try the following:

Reset nitro.preset to cloudflare_pages (your initial value)
Remove the 'nitro-cloudflare-dev' entry in modules (I think this one is messing up with something)
Make sure your wrangler.toml has the right compat flags (as in your example above)
Build with npm run build (your initial value)
Deploy with npx wrangler pages deploy dist/ (don't use 'dev' but 'deploy' instead)

Would be extremely interested in knowing if it works 🙏🏻

Hi @brewaa
Can you let me know if you managed to make it work?

Hi @vejja,
Sorry I hadn't got back to this yet.
I'll create a new repo to test this now.

The nonces are still changing correctly in local dev environment. npm run dev
Do you want access to the repository?

Yes that would be great

I’m proposing a change that would supposedly avoid this whole nodejs_compat issue, but some real-life testing would be great.
If you can test the branch locally and confirm whether it works that would be super helpful !
Cheers

@brewaa Thanks for the repo link
I wasn't able to find the appropriate configuration for Cloudflare but I'm no expert so maybe I'm missing something.
However I used your repo to test the changes introduced by PR #547 and I can confirm it now works on Cloudflare, the nonce is there as expected.
You should be able to use it as soon as we release v2.1.0
@Baroshem: With this change, Cloudflare users don't need to think about setting a nodejs_compat flag anymore, which I think is much safer. Most people are unaware of the subtleties of API availability and compatibility issues between Node and Workers, so it's better if Nuxt-Security can work out-of-box in all deployment environments.

Sorry @vejja.
I'm getting:
'nuxt-module-build' is not recognized as an internal or external command
What do I need to install?

did you yarn first?
Alternatively you can also use npm install and npm run prepack if you prefer

Ahh yes. Thanks. No I didn't yarn first.
I've deleted everything and started again.
Yarn'd first then did yarn prepack
Receiving error:
failed to resolve "extends":"./.nuxt/tsconfig.json" in C:\Repo\nuxt-security\tsconfig.json
I can't see a .nuxt folder in the nuxt-security repo.
If this is just me, understandable if this is not worth pursuing, I don't want to take up too much of your time. I'm really happy with the effort you've put in so far and I'd be happy to wait to the 2.1.0 release. Thanks for your help.

sorry it's me, I think you probably need to yarn dev:prepare before prepacking to generate the tsconfig stubs

YES!!!
That worked @vejja !!
You are the best!
I can confirm nonces are working in Cloudflare with chore/2.1.0.
https://nuxt-security-test.pages.dev/

Awesome, let's plan to release 2.1.0 with this change then! :)
Thanks for the amazing work @vejja !

@pi0 I'm flagging you here on this thread as I think we might have uncovered an edge case here  - we would need your advice.
OP is deploying on Cloudflare using preset cloudflare-pages, and discovers that the crypto functions are not working.
Our module uses node:crypto under the hood, but Node APIs are not available in Cloudflare Workers, unless the nodejs_compat flag is set on Cloudflare. So we tell Cloudflare users to set that flag.
But it doesn't work...
I looked at the nitro server code generated by npm run build and it looks like all the node:crypto API calls are replaced by empty statements with a comment that the API is unsupported.
In other words, it looks like the nitro bundler detects that Node is not supported in Workers, and discards the Node API calls. Which prevents us from using legit Node API calls within Workers where the Node API was enabled manually.
I might be completely wrong, but from the surface of it, it looks like an unjs/unbuild issue. Leaving it up to you here.
FYI we are circumventing the issue by moving our codebase to never use the Node APIs in nitro, which solves the issue on our end from a functional perspective.


[BACK-2984] Resolve dependabot issues

Fix dependencies issues and vulnerabilities
Use modern version of yarn
Update Dockerfile
Update .travis.yml
Update .gitgnore and .dockerignore
Update .nvmrc
Add .yarnrc.yml
Add .snyk
Use Node v20.8.0
https://tidepool.atlassian.net/browse/BACK-2984

Thanks, yes, that's intentional. Once it is tested I'll move it to 1.7.3, release a new version, and pick up that change in the export repo.

/deploy qa2


uboot: allow bigger kernels to boot on raspberry pi

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Can you change the title and commit message to something like uboot: allow bigger kernels to boot on raspberry pies

sure!

Can you change the title and commit message to something like uboot: allow bigger kernels to boot on raspberry pies

sure!

Sorry for being at risk of abusing your care for the commons, but I'm trying to use this PR as an overlay, but I seem unable to get it to work...
I tried setting it buildUboot and what not...
Is there an easy way I'm just not seeing?

Sorry for being at risk of abusing your care for the commons, but I'm trying to use this PR as an overlay, but I seem unable to get it to work...
I tried setting it buildUboot and what not...
Is there an easy way I'm just not seeing?

Sorry for being at risk of abusing your care for the commons, but I'm trying to use this PR as an overlay and I seem unable to get it to work...
I tried setting it buildUboot and what not...
Is there an easy way I'm just not seeing?

Try this:
final: prev: {
  ubootRaspberryPi3_64bit = prev.ubootRaspberryPi3_64bit.overrideAttrs (o: { patches = [ ../pkgs/misc/uboot/0001-configs-rpi-allow-for-bigger-kernels.patch ]; });
}

Sorry for being at risk of abusing your care for the commons, but I'm trying to use this PR as an overlay and I seem unable to get it to work...
I tried setting it buildUboot and what not...
Is there an easy way I'm just not seeing?

Try this:
final: prev: {
  ubootRaspberryPi3_64bit = prev.ubootRaspberryPi3_64bit.overrideAttrs (o: { patches = [ ../pkgs/misc/uboot/0001-configs-rpi-allow-for-bigger-kernels.patch ]; });
}

Hi!
Nice work, may I ask you to also send this upstream? We've had a good success story with @lopsided98 for rockchip boards in the past:

<EMAIL_ADDRESS>
(Though you'll also have to fix the comments if you send upstream.)

Hi!
Nice work, may I ask you to also send this upstream? We've had a good success story with @lopsided98 for rockchip boards in the past:

<EMAIL_ADDRESS>
(Though you'll also have to fix the comments if you send upstream.)

I will try to send it upstream in the next few hours, although I'm not entirely sure if they'll accept it. After all where is the limit for kernel size? It will just keep getting bigger and bigger and the values will not be enough in a year.

I will try to send it upstream in the next few hours, although I'm not entirely sure if they'll accept it. After all where is the limit for kernel size? It will just keep getting bigger and bigger and the values will not be enough in a year.

I submitted a similar patch for the RockPro64 and they accepted it, although I don't remember how much I increased it by.

I submitted a similar patch for the RockPro64 and they accepted it, although I don't remember how much I increased it by.

They are understanding of "mainline defconfig Linux". They know it exists, and gets bigger.
Just to re-iterate, here is the patch @lopsided98 contributed, if you want to see the reception:

<EMAIL_ADDRESS>
(Though it was reviewed by the Rockchip... maintainer? )

They are understanding of "mainline defconfig Linux". They know it exists, and gets bigger.
Just to re-iterate, here is the patch @lopsided98 contributed, if you want to see the reception:

<EMAIL_ADDRESS>
(Though it was reviewed by the Rockchip... maintainer? )

Meh, all of us didni't actually test it and the patch I committed was for 2021.01 and doesn't apply to 2020.10. I will fix it later.

Meh, all of us didni't actually test it and the patch I committed was for 2021.01 and doesn't apply to 2020.10. I will fix it later.


Tables do not work properly with > 2 editors on one page

With >2 editors on one page, they throw errors in the console when hovering over them with a mouse. Might be fixed in next lexical version, which contains major refactors?
Seems to be a lexical bug: https://github.com/facebook/lexical/issues/4157

Would you recommend using the experimental table instead? Or is there a risk it will be dropped or dramatically changed in the future?

Would you recommend using the experimental table instead? Or is there a risk it will be dropped or dramatically changed in the future?

Honestly not sure - that one is mostly mirrored from the lexical playground.
The standard table has been receiving some more updates recently, e.g. background color for cells. However on the other hand, the standard one is based on a deprecated node type, while the experimental is not.
Might be worth asking the lexical team (eg on discord) to know about what their plan / goal is with the experimental table!

Ok, thanks for the quick response.


Implement functions library

Optimize scripts by compiling them into functions.
https://community.bistudio.com/wiki/Arma_3:_Functions_Library
https://www.ofpec.com/forum/index.php?topic=32468.0

#12 Should resolve this issue.


Avoid running data migration on incorrect databases

Problem
When running Django with multiple databases, ./manage.py migrate --database other fails because none of the Axes migrations run, but the data migration does run, and fails because the tables don't exist.
Solution
Early exit if the migrations are being run on a database where Axes doesn't exist.

Good catch, thank you for the PR 👍


model.hasRelationship

Hello,
I need to check if a model had a certain relationship to another, like, a lot. It would be handy to add a function, for example: 'hasRelationship' to the model's instance:
user.hasRelationship({alias:'LikesMovie', where:{id:movie.id}});
As you noticed, this is based on the relateTo(...) pattern, which I like and use a lot.
Thanks for considering.
p.s.
This lib works so well for me. won't get enough to appreciate your work!.

I'm glad that you like Neogma, and that it suits you well!
Thanks for submitting this, it's another great improvement! I'll implement it when I find some time in the following weeks.

@tejo-ak I'm considering the following, which has more uses:
const relationships = await user.getRelationships({
    alias: 'LikesMovie',
    targetWhere: { id: movie.id },
    limit: 1,
    relationshipWhere: { since: 2021 }
});

console.log(relationships[0].target.name); // "John Wick"
console.log(relationships[0].relationship.since); // 2021
console.log(!!relationships.length); // true

All params except for alias are optional.
Using limit, you can improve its performance if you just want to see if the relationship just exists.
Do you think it's simple enough for your case, or should I create a dedicated hasRelationship method?

Hello,
Yes, this approach works in my use thanks.
In which version will this api available?
Thanks again.

I ended up adding a findRelationships Model static (and an Instance method as a wrapper).
Docs.
Deployed in 1.9.0.


PARQUET-793: Do not return incorrect statistics

Weird test failure:
18: *** error: can'unsigned short allocate region
18: *** set signed char breakpoint in malloc_error_break to debug```

Otherwise LGTM.

Thanks for the reviews.

@wesm can you merge this patch too if you have no comments? Thanks.


[WSL2] Issues with running LXD (system containers)

This is basically a follow up from: https://github.com/microsoft/WSL/issues/4158
After doing sudo lxd init and accepting all defaults I run in to the issue
$ sudo service lxd start
Starting Container hypervisor based on LXC: ip6tables: No chain/target/match by that name.

Even if I uninstall by sudo apt remove --purge lxd, then install LXD again with sudo apt install lxd I will run in to this issue. Running init results in the following error:
$ sudo lxd init
error: Unable to talk to LXD: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: no such file or directory

Notes:
This guy (https://wsl.dev/wsl2-lxd-funtoo/) seems to have the lxd network interface already, dont know what is up with that?
I plan to follow @simos post after this is cleared https://blog.simos.info/how-to-run-lxd-containers-in-wsl2/

My guess is that some lxd config is not removed when uninstalling

Can you reproduce this on Ubuntu 18.04 or 20.04? LXD in 16.04 is ancient.
Here is a video of Nuno's LXD workflow, BTW: https://www.youtube.com/watch?v=DULAocJuo_g

@sirredbeard I have it working on Ubuntu 18.04!

Closing remarks (mostly to self) there's probably "something" to the OP. I mean, Xenial is "ancient", but it also isn't like lxd didn't work back in the day. That said, the probability of anyone drilling down hovers around zero in this issue context. I've seen some (utterly unproven) evidence something strange is going on with ipv6 that has the potential to trip upstream (userspace) assumptions when manipulating iptables, but finger pointing (scare quote) "WSL" versus chalking tag linux-behavior is not trivial ref #767.


Feature/rename career information to career stage

Feat: Header menu item text changes, renamed Career information to Career stage

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Lesson 6: Brownie Fund Me - Fail in Compiling

FundMe.sol
// SPDX-License-Identifier: MIT

// Smart contract that lets anyone deposit ETH into the contract
// Only the owner of the contract can withdraw the ETH
pragma solidity ^0.6.6;

// Get the latest ETH/USD price from chainlink price feed
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
contract FundMe {
    // safe math library check uint256 for integer overflows
    using SafeMathChainlink for uint256;

    //mapping to store which address depositeded how much ETH
    mapping(address => uint256) public addressToAmountFunded;
    // array of addresses who deposited
    address[] public funders;
    //address of the owner (who deployed the contract)
    address public owner;

    // the first person to deploy the contract is
    // the owner
    constructor() public {
        owner = msg.sender;
    }

    function fund() public payable {
        // 18 digit number to be compared with donated amount
        uint256 minimumUSD = 50 * 10**18;
        //is the donated amount less than 50USD?
        require(
            getConversionRate(msg.value) >= minimumUSD,
            "You need to spend more ETH!"
        );
        //if not, add to mapping and funders array
        addressToAmountFunded[msg.sender] += msg.value;
        funders.push(msg.sender);
    }

    //function to get the version of the chainlink pricefeed
    function getVersion() public view returns (uint256) {
        AggregatorV3Interface priceFeed = AggregatorV3Interface(
            0x8A753747A1Fa494EC906cE90E9f37563A8AF630e
        );
        return priceFeed.version();
    }

    function getPrice() public view returns (uint256) {
        AggregatorV3Interface priceFeed = AggregatorV3Interface(
            0x8A753747A1Fa494EC906cE90E9f37563A8AF630e
        );
        (, int256 answer, , , ) = priceFeed.latestRoundData();
        // ETH/USD rate in 18 digit
        return uint256(answer *<PHONE_NUMBER>0);
    }

    //<PHONE_NUMBER>
    function getConversionRate(uint256 ethAmount)
        public
        view
        returns (uint256)
    {
        uint256 ethPrice = getPrice();
        uint256 ethAmountInUsd = (ethPrice * ethAmount) /<PHONE_NUMBER>000000000;
        // the actual ETH/USD conversation rate, after adjusting the extra 0s.
        return ethAmountInUsd;
    }

    //modifier: https://medium.com/coinmonks/solidity-tutorial-all-about-modifiers-a86cf81c14cb
    modifier onlyOwner() {
        //is the message sender owner of the contract?
        require(msg.sender == owner);

        _;
    }

    // onlyOwner modifer will first check the condition inside it
    // and
    // if true, withdraw function will be executed
    function withdraw() public payable onlyOwner {
        // If you are using version eight (v0.8) of chainlink aggregator interface,
        // you will need to change the code below to
        // payable(msg.sender).transfer(address(this).balance);
        msg.sender.transfer(address(this).balance);

        //iterate through all the mappings and make them 0
        //since all the deposited amount has been withdrawn
        for (
            uint256 funderIndex = 0;
            funderIndex < funders.length;
            funderIndex++
        ) {
            address funder = funders[funderIndex];
            addressToAmountFunded[funder] = 0;
        }
        //funders array will be initialized to 0
        funders = new address[](0);
    }
}

brownie-config.yaml
dependencies:
   # - <organisation/repo>@<version>
   -<EMAIL_ADDRESS>compiler:
  solc:
    remappings:
    - '<EMAIL_ADDRESS>
terminal:
XXX % brownie compile
Brownie v1.18.1 - Python development framework for Ethereum

Compiling contracts...
  Solc version: 0.6.12
  Optimizer: Enabled  Runs: 200
  EVM Version: Istanbul
CompilerError: solc returned the following errors:

contracts/FundMe.sol:8:1: ParserError: Source<EMAIL_ADDRESS>not found: File outside of allowed directories.
import<EMAIL_ADDRESS>^--------------------------------------------------------------------------^

contracts/FundMe.sol:9:1: ParserError: Source<EMAIL_ADDRESS>not found: File outside of allowed directories.
import<EMAIL_ADDRESS>^------------------------------------------------------------------^

Can you check the spacing in the below code:
remappings:
- '<EMAIL_ADDRESS>
TAB is needed as below:
remappings:
    - '<EMAIL_ADDRESS>
I do not see that in your code:

I am having the same issue, @kelhkc, did you ever figure it out?


Update main.css

Cleaned up the CSS code by removing duplicated selectors and consolidating common styles.
Fixed the formatting by using consistent indentation and spacing. Added comments to sections of the code for better readability and understanding.
Improved the code structure for easier maintenance and future updates.

problem I'm familiar with how it is and don't have time to test that you haven't broken something, so I'm punting on this for now, thanks anyway.


refactor: allow false value for MEMBERS_WORLD

It was quite confusing that you had to either go for true or not set

.env files are parsed as strings, so =false is 'false' and becomes truthy in that ternary condition.
console.log('false' ? 1 : 0);
Maybe just compare to process.env.MEMBERS_WORLD === 'true'?

changes pushed


Syslog logging

Discussed in https://github.com/lora-aprs/LoRa_APRS_iGate/discussions/146

Originally posted by oh2lak January 22, 2022
We are to use the TTGO ethernet boards to build our LoRa-APRS infrastructure for digi's and igates and thus the serial logging feature is not enough. Could a syslog logging feature be implemented to be able to do remote logging?
Looks like there is a suitable Arduino syslog library available ( https://github.com/arcao/Syslog ) which could do the job. I'm not a programmer but I'm tempted to fork the project and try on my own with learning by error.
@peterus Could you consider adding this to the igate code if I fail miserably?
Thanks for a great project and code!
Erik OH2LAK

closed with #167 and #166


Milestone B basics

I would propose to merge this in development when the tests pass, even whilst the feature is not 100% complete yet.
@JeroenStravers1 can continue with his extra endpoint based on this GraphQL infrastructure.

Hi @moretea, is there an individual issue this can be connected to? For overview's sake I would like to smash the commits to one.

@moretea, o, and please let me know when the tests do pass and can be merged :-)


Branchify and move to dynamic images

Hi @mmitche, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@dotnet-bot test ci please


[bugfix] set_tags call in BaseObject.clone_tags used incorrect signature

This is a bugfix to BaseObject.clone_tags.
set_tags was called incorrectly from clone_tags without the kwargs symbol.

@fkiraly the checks are still running, but the update looks pretty clear cut for unpacking the dictionary correctly. I'll approve once it is done.
Minor suggestion (and probably not really worth the CI running again!), but when if tag_names is None is True it seems like you could just do update_dict = tags_est and in the "else" portion, you could probably just go straight to the dictionary comprehension instead of looping to filter the tag_names then looping the ones that survived the filtering.
        if tag_names is None:
            update_dict = tags_est # tag_names = tags_est.keys()
        else:
            # if tag_set is passed, intersect keys with tags in estimator
            if not isinstance(tag_names, list):
                tag_names = [tag_names]
            update_dict = {key: tags_est[key] for key in tag_names if key in tags_est.keys()}
            # tag_names = [key for key in tag_names if key in tags_est.keys()]

        # update_dict = {key: tags_est[key] for key in tag_names}


fix: use blob digest as cleanup and cache key for refs in registry pr…

…oxy mode

Please sign your commit.


[Feature Request]: Increase watermark coverage to fill page

Feature Description
When using the watermark function as default (45° watermark) the lower rightcorner of the page is untouched by the watermark.
It would need some extra lines to be filled completely.
Why is this feature valuable?
Watermark should be able to be on the full size of the page
Suggested Implementation
option 1 : Compute the right amount of line, not based only on page height like now, but incorporating the angle. Probably nee a trigonometry calculation to compute the "extra height".
option 2 : Add an extra field to the existing watermark generator for line counts. When empty (default) use the existing computation, when filed, use the amount specified.
Additional Information
Seem to happend only on long watermark string, when it don't have the oportunity to "repeat"
No Duplicate of the Feature

[X] I have verified that there are no existing features requests similar to my request.

to fix your trouble check this solution click
maybe this will solve your problem.

Hi, I can work on this.

Lovely, great work !


How to add a country?

I have Prism running locally, for a demo, I'm looking at adding Kenya, how can I do that? Is there any script that helps configure the different files?
Can I add a layer that pulls a GeoJSON file from an API that contains points?

Hi @jeremi, we'd be happy to help you add Kenya!
Unfortunately we don't have a script at the moment have been doing this manually:

copy the folder of an existing country in src/config and public/data and rename them as kenya
import and add kenya in /src/config/index.ts
update the boundary files and update layers.json accordingly
adapt the prism.json and layers.json to suit your needs. In particular, adapt the map bounding box for Kenya

Yes, you should be able to pull geojson file that contain points. Maybe not out of the box but you can look at how things work for point_data layers as well as the cdi layers.


Shouldn't RandomReverse be applied to both im and gt?

Motivation for the feature

From the doc:

It is suggested that RandomReverse is applied to im only. But if it was the case, the GT would not match. So, shouldn't we suggest by default to apply this transformation to both the image and the ground truth? Unless I am missing something.

Yes, you're right! It has to be applied to both image and GT. For example, the config file of the previous version of the mp2rage model applies it to both im and gt. Even for our ongoing centerline detection models, we are applying it for both images.

OK, so in this case why don't we simply get rid of the 'applied_to', which introduces confusion and could lead to improper usage?

Yes, I think that's a fair point! Conventionally, the user is left to specify which image is the transformation is applied to (this is also the case for Monai's transformations). I thought of adding a recommendation in the docs to apply it to both, but I think it's better to do it ourselves as you suggest. The confusion is indeed real and it would be better to not burden users with one more option among a million others!


Test is failed with Ruby 2.5+

massign structure has been changed.

$ bundle exec rspec

(snip)

Finished in 0.0096 seconds
47 examples, 11 failures

Failed examples:

rspec ./spec/ruby-hl-lvar_spec.rb:26 # RubyHlLvar::Extractor#extract with simple mass assignment should == [["a", 1, 0], ["b", 1, 3], ["c", 1, 6]]
rspec ./spec/ruby-hl-lvar_spec.rb:32 # RubyHlLvar::Extractor#extract complex mass assignment should == [["a", 1, 0], ["b", 1, 4], ["c", 1, 7]]
rspec ./spec/ruby-hl-lvar_spec.rb:33 # RubyHlLvar::Extractor#extract complex mass assignment should == [["a", 1, 0], ["b", 1, 4]]
rspec ./spec/ruby-hl-lvar_spec.rb:34 # RubyHlLvar::Extractor#extract complex mass assignment should == [["a", 1, 1], ["b", 1, 4]]
rspec ./spec/ruby-hl-lvar_spec.rb:35 # RubyHlLvar::Extractor#extract complex mass assignment should == [["a", 1, 0], ["b", 1, 4], ["c", 1, 7]]
rspec ./spec/ruby-hl-lvar_spec.rb:41 # RubyHlLvar::Extractor#extract lhs of assignment should == [["a", 1, 0], ["a", 2, 1], ["b", 2, 4], ["a", 2, 9]]
rspec ./spec/ruby-hl-lvar_spec.rb:45 # RubyHlLvar::Extractor#extract with complex mass assignment should == [["a", 1, 1], ["b", 1, 5], ["c", 1, 8], ["d", 1, 13]]
rspec ./spec/ruby-hl-lvar_spec.rb:61 # RubyHlLvar::Extractor#extract complex block args should == [["a", 1, 7], ["b", 1, 10], ["c", 1, 12]]
rspec ./spec/ruby-hl-lvar_spec.rb:67 # RubyHlLvar::Extractor#extract array should == [["a", 1, 0], ["b", 1, 2], ["a", 2, 1], ["b", 2, 3]]
rspec ./spec/ruby-hl-lvar_spec.rb:126 # RubyHlLvar::Extractor#extract field mass assignment should == [["z", 1, 5]]
rspec ./spec/ruby-hl-lvar_spec.rb:144 # RubyHlLvar::Extractor#extract for params should == [["x", 1, 5], ["y", 1, 9], ["z", 1, 12]]

$ docker run -it --rm rubylang/all-ruby env ALL_RUBY_SINCE=ruby-2.4 ./all-ruby -rpp -rripper -e 'pp Ripper.sexp("a,b=1,2")'
ruby-2.4.0          [:program,
                     [[:massign,
                       [[:@ident, "a", [1, 0]], [:@ident, "b", [1, 2]]],
                       [:mrhs_new_from_args, [[:@int, "1", [1, 4]]], [:@int, "2", [1, 6]]]]]]
...
ruby-2.4.9          [:program,
                     [[:massign,
                       [[:@ident, "a", [1, 0]], [:@ident, "b", [1, 2]]],
                       [:mrhs_new_from_args, [[:@int, "1", [1, 4]]], [:@int, "2", [1, 6]]]]]]
ruby-2.5.0-preview1 [:program,
                     [[:massign,
                       [[:var_field, [:@ident, "a", [1, 0]]],
                        [:var_field, [:@ident, "b", [1, 2]]]],
                       [:mrhs_new_from_args, [[:@int, "1", [1, 4]]], [:@int, "2", [1, 6]]]]]]
...
ruby-2.7.0-preview1 [:program,
                     [[:massign,
                       [[:var_field, [:@ident, "a", [1, 0]]],
                        [:var_field, [:@ident, "b", [1, 2]]]],
                       [:mrhs_new_from_args, [[:@int, "1", [1, 4]]], [:@int, "2", [1, 6]]]]]]

I resolved this issue by #23.


Dynamic forms not staying on same page after submission

I've left the redirect URL blank for each of my dynamic forms, and made sure that the workflows do not contain a redirect on form submission. However on form submission the user is redirected to the homepage with the Show Notification message appearing there. I expected that the same page (containing the form) would reload with the Show Notification message appearing.

You can work around this by using the Request token in the redirect URL field.

Is this similar to the behavior I raised an issue about here https://github.com/OrchardCMS/Orchard/issues/5765?

Should be fixed with #5765 in 1.9.2


Write expected outcomes

Expected outcomes (e.g., publications, white papers, open access databases, etc).

Arena's initial draft and my first suggested revisions have been pushed 😄

The essential seems there! However, I'm not sure if it's useful to write an R package since we'll only do data analyses. We won't implement a new set of methods or functions that others can use (unless I misunderstood the objective of the working group). Should we also say something about recommending a set of actions to protect raptor populations in the prairies? Or perhaps a map of the areas where raptor populations are the most vulnerable / a map of where they are expected to be in the future could be an interesting outcome as well.

I like your idea to add a set of recommended actions/guidelines for protecting raptors! And the maps you suggest would also be excellent.


I'm getting this error when trying to ping an ES server

The error is: the client noticed that the server is not a supported distribution of Elasticsearchmake[1]
I'm using github.com/elastic/go-elasticsearch/v7 v7.15.0 with go1.16
The ES server info is:
"version" : {
    "number" : "7.10.2",
    "build_flavor" : "oss",
    "build_type" : "tar",
    "build_hash" : "unknown",
    "build_date" : "2021-05-21T20:25:46.519671Z",
    "build_snapshot" : false,
    "lucene_version" : "8.7.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },

This is explained in the compatibility matrix in the readme:
Language clients are forward compatible; meaning that clients support communicating with greater or equal minor versions of Elasticsearch. Elasticsearch language clients are only backwards compatible with default distributions and without guarantees made.
Hence, the 7.15 client is not compatible with the oss distribution version 7.10.2.
You can still use the version v7.10.0 of this client for full compatibility!


Add supabase storage support

Supabase is an open source Firebase alternative providing all the backend features you need to build a product.

https://supabase.com/docs/guides/storage
https://supabase.github.io/storage-api/

I am sort of interested and want to have a look at this, you can assign this to me 😆

I am sort of interested and want to have a look at this, you can assign this to me laughing

Thanks a lot! Have fun in that. Supabase is super cool!

Thanks a lot! Have fun in that. Supabase is super cool!

I am sure it will be fun! But since I am not that familiar with storage systems, this may take a while lol

But since I am not that familiar with storage systems, this may take a while lol

Take you time and have fun!

Thanks to @Ji-Xinyou, we have support it.


Resolve announceip

ptarmd --announce_ip enable name.

#1485

#1484

we'd like to resolve from ptarmcli.


feat(check): Allow to only check trees+packs for given snapshots

see #251
depends on https://github.com/rustic-rs/rustic_core/pull/262

Unblocked after merging #1282


Force tooltip direction regardless of whether space is sufficient

Hello and thanks for your amazing work!
Is it possible to add an option / prop that disables the automatic behavior which determines the tooltip direction based on remaining space?
Thanks in advance!

@bsidelinger912 Thank you very much! Works great :)


Could not find tools.jar

Hi,
I'm currently trying to run an Android project  width React Native. However, when I try so, I get this error :
:react-native-vector-icons:compileReleaseJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vector-icons:compileReleaseJavaWithJavac'.
> Could not find tools.jar

But I can't see where it comes from...
Here's my java version :
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)

Any ideas ?

Hey @enguerranws, You probably don't need to integrate react-native-vector-icons further than just copying the fonts.

Hi, @oblador and thank you for your quick answer.
We're 2 to work on this project, so I don't know why we use that package (well, I can guess why :)), but what in this error makes you think that we only needs the fonts instead the whole package ?

You only need to integrate the java parts when you need to use the icons as PNGs and in most use cases you don't.
Your error Could not find tools.jar is most likely not connected to this library but your env setup, try googling it.

So, I try to fix my Android / Java env to solve this. I was using Homebrew android-sdk, I tried a fresh reinstall of android-sdk (manual install). Here's what I get :
/Users/enguerran/Sites/lab/ebayfetcherapp/node_modules/react-native-vector-icons/android/src/main/java/com/oblador/vectoricons/VectorIconsPackage.java:21: illegal start of type
    List<NativeModule> modules = new ArrayList<>();
                                               ^
1 error
:react-native-vector-icons:compileReleaseJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vector-icons:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

I'm pretty sure that comes from my env and I'm not familiar with Java, but it seems like something's going wrong, isn't it ?

Sorry I don't have time nor the knowledge to support your Java installation. Ask your colleague or refer the the react native manual.

I got the same issue. I'm sure Java SDK wa installed and correct system environment setting. I can run-android before install react-native-vector-icons
here is my error log:
:react-native-vector-icons:compileReleaseJavaWithJavac - is not incremental (e.g. outputs have changed, no previous execution, etc.).
:react-native-vector-icons:compileReleaseJavaWithJavac FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-vector-icons:compileReleaseJavaWithJavac'.

Could not find tools.jar. Please check that C:\Program Files (x86)\Java\jre1.8.0_101 contains a valid JDK installation.

Java version
D:\Projects\SMP\SMP-Android\SaigonMeditation>java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) Client VM (build 25.101-b13, mixed mode)

Sometimes you need to re-install java and everything will work just great.

I have the same problem. But 3-4 months ago it worked ok, and as I remember I didn't do anything with my project since then...

I had same problem. My java path was wrong.
Previously i was using '/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java'
I changed to '~/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java'
Now issue is solved for me.


Regenerate protos with new protoc version

Closed in favor of https://github.com/dart-lang/dart-pad/pull/2618


GIF images cannot move of version 4.1.2

version: 4.1.2
UIImageView *image = [[UIImageView alloc]initWithFrame:CGRectMake(50, 0, 50, 50)];
[image sd_setImageWithURL:[NSURL URLWithString:@"http://qq.yh31.com/tp/zjbq/201711142021166458.gif"]];

The gif image can be displayed but can't move

find reason：

Starting with the 4.0 version, we rely on FLAnimatedImage to take care of our animated images.
If you use cocoapods, add pod 'SDWebImage/GIF' to your podfile.> 8
To use it, simply make sure you use FLAnimatedImageView instead of UIImageView.
Note: there is a backwards compatible feature, so if you are still trying to load a GIF into a UIImageView, it will only show the 1st frame as a static image.
Important: FLAnimatedImage only works on the iOS platform. For OS X, use NSImageView with animates set to YES to show the entire animated images and NO to only show the 1st frame. For all the other platforms (tvOS, watchOS) we will fallback to the backwards compatibility feature described above


cloudbuild trigger example not working - schema correct ?

Example seen here : https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/blob/master/dm/templates/cloudbuild/examples/cloudbuild_trigger.yaml
When running, 2 error messages that the schema is not matching

Additional properties are not allowed ('branchName' was unexpected) at ['triggerTemplate']
Additional properties are not allowed ('buildTemplate' was unexpected)

gcloud deployment-manager deployments update test-deployment --config=cloudbuild_trigger.yaml
The fingerprint of the deployment is BX7Pi_Hx1Q1mSLyZENJkSw==
Waiting for update [operation-1583859384742-5a083000072ae-37b7726c-725af8b2]...failed.
ERROR: (gcloud.deployment-manager.deployments.update) Error in Operation [operation-1583859384742-5a083000072ae-37b7726c-725af8b2]: errors:
- code: MANIFEST_EXPANSION_USER_ERROR
  location: /deployments/firebase-tools-cloudbuilder/manifests/manifest-1583859384940
  message: |-
    Manifest expansion encountered the following errors: Invalid properties for 'trigger.py':
    Additional properties are not allowed ('branchName' was unexpected) at ['triggerTemplate']
    Additional properties are not allowed ('buildTemplate' was unexpected)
     Resource: mybuildtrigger Resource: config

is this syntax supported ? the interpretation seems to fail.
branchName is not accepted as parameter to triggerTemplate.
...
properties:
  triggerTemplate:
    type: object
    additionalProperties: false
    properties:
      revision:
        type: string
        oneOf:
          - "$ref": "#/definitions/branchName"
          - "$ref": "#/definitions/tagName"
          - "$ref": "#/definitions/commitSha"

definitions:
  commitSha:
    type: string
    description: Explicit commit SHA to build.
  branchName:
    type: string
    description: The name of the branch to build.
  tagName:
    type: string
    description: The name of the tag to build.
...


No network with pi3

Hello,
I am trying to get network on my Raspberry Pi3.
ip link returns "lo" and "eth0" (where is wlan0 ?)
but ifup returns
ifup eth0
ifup: can't open '/etc/network/interface': No such file or directory

Also, before the boot I get "No ethernet found" and the ethernet LED are off until the linux boot.
Did a miss something in the configuration ?

Wifi isn't working here either. I added linux-firmware-bcm43430 to IMAGE_INSTALL_append.

It does work with the right firmware added. This layer come with some images for testing. The key thing is https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-core/packagegroups/packagegroup-rpi-test.bb#L31 .

@agherzan can you tell me which layers I should add in my local.conf?
Because I'm not getting it to work, whatever I try.

Thanks, already found kernel-modules in rpi-hwup-image so building that now. linux-firmware-bcm43430 was already in there. Will let you know.

But generally use the test image. And start from there when investigating support issues.


FormSection propType doesn't allow React 16 Fragment

Are you submitting a bug report or a feature request?
Bug report
What is the current behavior?
FormSection prop type doesn't allow React 16 Fragment
What is the expected behavior?
FormSection prop type allows React 16 Fragment to be used (PropTypes.node)
Sandbox Link
https://codesandbox.io/s/l6nx50r3m
Open the console
What's your environment?
React 16.2.0
Redux form 7.2.3
Workaround
Wrap Fragment in a Stateless Functional Component
(Everything works, it just adds a console warning)

Thanks for the report! Issue up for grabs, shouldn't be difficult to fix.

@shulcsm it would definitely break many people's code.

Fix released in v7.4.0.


Random error when trying to launch

This shows up when I try to launch it. I have updated pythong and installed via git.
https://i.imgur.com/P1bspzF.png

Hi, do you have srtuped config?
Start bot like this "Python3 autofishbot.py nameofyourconfig"

same error

Python 3.10.6 (or above required), you are using 3.8.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4175

Questions ?
Please refer to the Backport tool documentation


fix local state uts

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

pkg/engine/states/local
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Coverage increased (+0.04%) to 72.68% when pulling 8373e0afccbad237e661f3f6c0288ba427aad313 on SparkYuan:fix_uts into 5dc798c0f6939586daa3bff738d48c5dd58b38bb on KusionStack:main.


chore: update data

seems we also need a translation for the new fish specie 鰯

missed that one, now update again

Thanks!


New package: mhogomchungu.media-downloader version 5.1.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #182133

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manually validated in Windows Sandbox instance.

[!NOTE]
Close with reason: Duplicated.

Related #182138


reports for deterministic fx show event summary statistics table

for example

Added a comment in the problematic code that references this issue and will try to summarize the cause here.
The issue here was not detectable when using the core cli to generate reports. The core library's helper functions take the API Response's object_pairs that look something like this:
"object_pairs": [
{
"aggregate": "0f59de55-2f0e-436a-8ea9-fb197b396fd3",
"cost": null,
"forecast": "c1058bd0-c3da-4141-92c6-496be27f264d",
"forecast_type": "forecast",
"observation": "5bf24aaf-36fe-45d8-956d-da6551803aa4",
"reference_forecast": null,
"uncertainty": null
}
],

And fill in forecast/observation/aggregate with the appropriate datamodel objects using the helper here: https://github.com/SolarArbiter/solarforecastarbiter-core/blob/fa8fb9961e8135c52395dd138061aaedf6915e76/solarforecastarbiter/io/api.py#L1063
Since the raw_report field of a completed report object already includes this metadata in the Report.raw_report.processed_forecasts_observations[<index>].forecast/observation.original, the dashboard avoids loading this a second time by setting Report.report_parameters.object_pairs to an empty list before instantiating a Report object for use with the solarforecastarbiter.reports.template.py functions.
The code as written functioned in core with the aid of the above mentioned helper, but when passed an empty list the all(x.forecast is datamodel.EventForecast for x in report_parameters.object_pairs) test always returned true. The fix implemented is to use the original forecast from the processed pairs, since they should always exist for a completed report that is being rendered.


chore(main): release 1.2.2

:robot: I have created a release beep boop
1.2.2 (2024-06-19)
Bug Fixes

release please deprecation (#25) (2fc4da5)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.2
:sunflower:


Contributing to: us-md-anne_arundel.json

Adding/Updating us-md-anne_arundel.json

I think the "type": "ESRI" is throwing it off. Can you change that?

:ok_hand:


HTTP Client improvements, DNS Client rework, RFC 6335

For some reason the the callback delegate the HTTP Client sometimes ended up as nullptr. Maybe due to new delegate implementation. Seems to be fixed by using spec::dynamic. If anyone can explain why, please do :D
TCP and UDP are now using dynamic (ephemeral) ports in the range described by IANA in RFC 6335. In other words, the outgoing ports are now in range of 49152 - 65534.
Improved the DNS Client by adding timeout on resolve requests (5s default). It now also reuses one UDP socket. Also added transaction ID matching on incoming responses.
Also a fix for #1073 sneaked in before I noticed #1074 - please merge that one first (when sorted).

Thanks for the review @RostakaGmfun, much appreciated!


[index/build] Upstream indexing while building changes

This patch upstreams previously AppleInternal changes for
indexing while building.

@swift-ci Please test


[22.11] freshrss: add patch for CVE-2023-22481

Description of changes
https://nvd.nist.gov/vuln/detail/CVE-2023-22481
Addressed in unstable with bump to 1.21.0, but that adds some new features and removes support for some php versions so better not to risk breakages.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] 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/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 225416 run on x86_64-linux 1

1 package built:

freshrss


Test PR

Test pr to check pr labeler

@tusharnankani i want to check a github action can u approve the review

Cool it is working


Add collected memory usage to metrics

Initiates a collection of memory usage metrics roughly every 30 seconds, which are also logged.
In passing, fixes a bug where twice as many events as should be were counted.

bors r+


Bug: Copy File from TeamViewer doesn't copy File Creation date attribute

What feature or improvement do you think would benefit Files?
When copying a file from a remote TeamViewer session the file creation time is not copied across (whereas it is with copy & paste into Windows File Explorer). I suspect Modified and Accessed are similarly ignored. Having these file attributes maintained is very helpful and ideally Files would behave in the same way as Windows File Explorer.
Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.2792
Comments
No response

Thanks for the report.


Update to rust master: fixed array length fixes + lib stabilizations

Thanks for the PR. I ended up fixing this w/ the newer breaking changes as well 00198f1488dfcfd9a60abfe0cb0ce0b437b69d78


feat(azure): added support to azure functions http trigger

Description of change
Close the issue #3.

Pull-Request Checklist

[x] Code is up-to-date with the main branch
[x] npm run lint passes with this change
[x] npm run test passes with this change
[x] This pull request links relevant issues as Fixes #0000
[x] There are new or updated unit tests validating the change
[x] Added documentation inside www/docs/main folder.
[x] Included new files inside index.doc.ts.
[x] The new commits follow conventions outlined in the conventional commit spec

Codecov Report

Merging #31 (828eac5) into main (43e2f20) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #31   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           36        37    +1
  Lines          849       935   +86
  Branches       194       219   +25
=========================================
+ Hits           849       935   +86

Impacted Files
Coverage Δ

src/adapters/azure/http-trigger-v4.adapter.ts
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


GSM 03.48

Is it possible to send GSM 03.48 message using jsmpp

Yes, I also maintain the GSM 03.48 library (https://github.com/opentelecoms-org/gsm0348). The binary messages generated with this library needs to be send with DCS F6 and PID 7F to reach the SIM via an envelope.

I'm looking at how I can send OTA-update on a SIM as SMS and the automatically updates are installed

First you need to construct the binary message. For GSM 03.48 encrypted messages to update the SIM filesystem, or to send messages to open channels for HTTPS, you can use the library at https://github.com/opentelecoms-org/gsm0348, which by coincidence I also maintain. For SIM related SMS, use DCS 0xF6 and PID 0x7F.

Can I modify or attach an algorithm to monitor the operations of the SIM card? Thanks a lot for the feedback!


MH Replay support?

Since Mega Hack Replay is literally built-in megahack v7 which most people have, I think it will make sense to add support for it's macros in future.

here is a version that has support
https://github.com/Ploosho/zcb-2.0/releases/tag/v1.3.1-zbot-mhr

This feature is in development, thanks!

use zcb 3: https://github.com/zeozeozeo/zcb3/releases/


Intermittent error (happened once):  "Failed to fork: Invalid argument"

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

A brief description

This is more of an incident report than a bug report because I haven't been able to reproduce it.  Filing it mostly as an FYI / in case it sounds familiar, or in case someone else hits this and has more details.  The command worked fine on a retry and hasn't happened again since, so this is not at all a blocker for me.
I was compiling a large C/C++ codebase in DrvFs.  Many invocations of the compiler; not much else going on.  I had ccache (apt install ccache) in front of the compiler.

Expected results

Compilation should succeed.

Actual results (with terminal output if applicable)

One of the files failed to compile with:
ccache: error: Failed to fork: Invalid argument

When I retried, it built fine.  I have not been able to reproduce this since.  I have never seen this failure mode on Linux.

Your Windows build number

15042
See our contributing instructions for assistance.

I realize that this is probably not actionable.  Feel free to close it as such if you'd like.

Thanks for the report!  Closing this out per the comment above and we can take a closer look if this starts hitting more often.

Adding more comments on #2469 (i.e. moving thread there :)


Add SubmissionDate to download's SubmissionRef section

Ticket:
https://dluhcdigital.atlassian.net/browse/FPASF-588
Description:
This is the first step of the work in the ticket, to add "SubmissionDate" to the "SubmissionRef" section of the data extract.
Screenshot:

Have chased TF again to understand if this will break them

@sc15zs - TF team confirmed this is OK to merge in :)


add upgrade strategy

As discussed with @regisss, adding --upgrade-strategy eager so that the latest subpackages are installed.
With pip install --upgrade optimum[intel]  the latest optimum version will be downloaded but not the latest version of optimum-intel

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

If you have time, you can add entries for Furiosa in both tables, otherwise we'll do it in another PR 🙂

Good point,  will do it right now !


Add all official azure domains

Searching for "list of azure domains" gives this list, and the list is not complete. E.g. "azureml.net" is missing, and probably others as well. It would be usefull for our security-departments domain-whitelisting to have a list of Microsoft azure domains.

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

ID: 790ff17b-0306-897d-f0df-59dd92441426
Version Independent ID: 6bfac7c1-8909-73f9-4212-26cc7ffaaa81
Content: Reference list of Azure domains
Content Source: articles/security/fundamentals/azure-domains.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @memildin
Microsoft Alias: memildin

@epa095 Thank you for catching this. We have engaged the content team to review and update as needed.

@memildin Could you please review this one?

Hi @epa095, thanks for the feedback and for taking the time to help us improve the docs.
The title of the page says it's not comprehensive and the first line of the text says it's a partial list. The purpose of this reference page was to provide a good springboard for identifying the Azure domains in use and the REST API endpoints. An exhaustive list would be constantly in flux, as Azure services are added/decommissioned and it's not our intention at this time to provide such a list here.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close

I agree that the page sais that the list is partial:-) This issue is not about how the article is missleading (it is not), is about how it would be better if the list was complete. And yes, that list of domains would be constaintly in flux, but I belive in you! In fact, I firmly belive that Microsoft is the company best suited to maintain this list!


Add anisotropic filtering to GLES2 backend

Fixes issue #45641
I made this change by copying the relevant code from the GLES3 backend to the GLES2 backend. In so doing, I noticed a strange line, line 8358 of rasterizer_storage_gles3.cpp:
config.use_anisotropic_filter = config.extensions.has("rendering/quality/filters/anisotropic_filter_level");
The strange thing about it is, as far as I can tell, this variable soon gets overwritten without having been used. Still, I copied this line even though I'm not sure it has any effect.
(EDIT: I have discussed this line with other devs and removed it from the GLES2 backend. It's still in the GLES3 backend, though.)
(EDIT: It's gone from both backends now.)

Looks fine to me although I haven't tested. Great first PR. :+1:
Seeing the duplication in texture_set_data and texture_set_flags reminded me I noticed a lot of code duplication here when converting this for Godot 4.0. In there I used a separate function to do all the common stuff between the two functions. It should be fine to leave like this though in 3.2.

Looks good to me! I'll let @clayjohn do the final review.
As a tip for future PRs, you might want to make them from a dedicated branch instead of your 3.2 branch, so that you can easily create new branches for new PRs even before the first one is merged.

I'd like to do some testing on Android and HTML5 before this is merged, just in case :slightly_smiling_face:

Thanks!


add gemmx prameter support

In this PR, we add the parameter support for gemmx. More specifically, we:

set the gemmx pe array size, meshRow, tileSize, and meshCol as configurable parameters in the cfg file. Now we can set these parameters to different values, but please take care to modify the streamer parameters too! Just so you know, the transpose extension only works for 512 data width for readers.
Note: the pipelined SIMD only works for meshRow * meshCol = 64 cases so if you set pe array size that doesn't have 64 output, please take care to set with_pipeline = false.
modify software test and datagen.py to accommodate arbitrary pe array size. Now only fixed the matmul test. Conv test modification will be done later.
relevant modification in snax-gen.py. The format tool did some format, so it looks like many changes but only very minimal changes actually.

Would it be more useful though that there is a default setting for the GeMM config?

I don't know. Maybe it's better to ensure that people explicitly set the PE size?

I don't know. Maybe it's better to ensure that people explicitly set the PE size?
The streamer parameters should be matched with the PE array size

I'm not too picky so okay haha. Maybe we can add somekind of documentation on our documentation page for this 😄

I don't know. Maybe it's better to ensure that people explicitly set the PE size?
The streamer parameters should be matched with the PE array size

I'm not too picky so okay haha. Maybe we can add somekind of documentation on our documentation page for this 😄

We can!

For this specific PR though:

Just so you know, the transpose extension only works for 512 data width for readers.

Note: the pipelined SIMD only works for meshRow * meshCol = 64 cases so if you set pe array size that doesn't have 64 output, please take care to set with_pipeline = false.

Can you please please please verify this somewhere in software instead of just this comment

I verified locally. Later relevant documentation will be added to push a warning on this.

Who sets TRANSPOSE_EXTENSION_ENABLE in the software makefile? Is there an automatic way this is set?

The streamer header file gen will set it if a transpose extension is instantiated.


Improve book structure

One thing that is currently not optimal with the book structure is that h3 (###) headings in chapter top documents are not listed in the table of content (sidebar). They are when used in a section.
One option is to move these chapter top documents within the chapter directorey. So instead of having
01-introduction
 |-01-about.md
 |-02-licensing.md
01-introduction.md

We could do
01-introduction
 |-00-index.md
 |-01-about.md
 |-02-licensing.md

Clicking on introduction would show the content of 00-index.md and subsections would be listed underneath. This would also facilitate the navigation in the book files. However, it would work only - as things stand - if 00-index.md has a title to show as section in the navigation. For most chapter, it would be 'Introduction'. Since we don't want
Introduction
  Introduction

for the first chapter, we could rename one of the two "About this book". Any thoughts?

I like the idea of all content being included in the folder, rather than a top-level file and then the rest in the folder.

Chapter top documents are now 00-index.md files with an additional chapter-title key.


[dv/otp_ctrl] Update testplan for V2 review

This PR updates the otp_ctrl's testplan for V2 review.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

Thanks Sri for all the suggestions! I updated this PR accordingly and fixes the inconsistency in the previous version.


Error in neural network compiler computing minimum sequence length for the model

❓Question
add network input to output, then get this warning, why and how to avoid it?
1/25: Converting Node Type Conv
2/25: Converting Node Type Relu
3/25: Converting Node Type Conv
4/25: Converting Node Type Conv
5/25: Converting Node Type Relu
6/25: Converting Node Type Conv
7/25: Converting Node Type Conv
8/25: Converting Node Type Add
9/25: Converting Node Type Conv
10/25: Converting Node Type Conv
11/25: Converting Node Type Relu
12/25: Converting Node Type Conv
13/25: Converting Node Type Conv
14/25: Converting Node Type Add
15/25: Converting Node Type Conv
16/25: Converting Node Type Reshape
17/25: Converting Node Type Transpose
18/25: Converting Node Type Reshape
19/25: Converting Node Type Transpose
20/25: Converting Node Type Reshape
21/25: Converting Node Type PRelu
22/25: Converting Node Type Conv
23/25: Converting Node Type Upsample
24/25: Converting Node Type Add
25/25: Converting Node Type Relu
Translation to CoreML spec completed. Now compiling the CoreML model.  /python2.7/site-packages/coremltools/models/model.py:111: RuntimeWarning: You will not be able to run predict() on this Core ML model. Underlying exception message was: Error compiling model: "compiler error:  Error in neural network compiler computing minimum sequence length for the model.".
RuntimeWarning)
Model Compilation done.

Hi @Penelope1003 ,
Did you manage to solve this issue?


Another Starfield interface

Adding another Starfield interface inspired by their HUD compass.

People really like starfield, this looks slick!

Great job!! Please make a version for Kraken elite. Fonts are super small)


Create new pull request template

We will eventually want to support different types of Pull requests (issues, docs, etc.) and GitHub supports a Template directory where many templates can be used for different kinds of PR's and can have different automation flows with query parameters.  This will be a useful starting point as we build out more automation (@ostephens docs effort) and expand our contributors.
Details here:

https://help.github.com/en/github/building-a-strong-community/about-issue-and-pull-request-templates
https://help.github.com/en/github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters

+1 for encouraging to link to the relevant issue. Let's keep this template minimal, we don't want to deter people from submitting PRs either :)

@wetneb That was the idea... minimal.  For Docs, or in the Docs repo, once we have something or other...then certainly the templates needed there could be different.  For us on OpenRefine trunk, what I have proposed here is all we need for now.


Does this work in windows?

I don't have windows to test.

Yes windows is supported: https://github.com/ErikDubbelboer/node-sleep/blob/master/sleep.cc#L11


Jakarta.validation API 3.0.1 is backward incompatible

The API contains OSGi header Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=9.0))", unlike the 3.0.0 API.
This requirement for JDK 9 is a backward-incompatible change that should not be introduced in a service release of the API.

according to https://jakarta.ee/specifications/bean-validation/3.0/ it shall support JDK 1.8

Hey there,
Can you make sure this PR https://github.com/eclipse-ee4j/beanvalidation-api/pull/177 fixes the issue for you?

looks good to me, thank you.


Remove save alert on Routing Group page

What is the motivation for adding/enhancing this feature?

When saving changes for a Routing Group, the user does not ned to be prompted again to confirm their save.

Enhancement changes verified and working fine in release v1.1.0.
Hence, closing it.
https://jam.dev/c/7c7d66c1-df68-45fd-91e2-01cf0bdacff0


Add option to include ValidationContext secrets

Currently, only TLSCertificates can be specified in the secrets section of EnvoyConfig, it would be great if also CertificateValidationContext secret were allowed.
The absence of this feature means that dynamic mTLS (with custom CA for validation) doesn't currently work

/kind feature

Example of defining a CA within a type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret proto:
resources:
  - "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"
    name: validation_context_sds
    validation_context:
      trusted_ca:
        filename: /certs/cacert.pem

which is slightly different from how a certificate is defined:
resources:
  - "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"
    name: tls_sds
    tls_certificate:
      certificate_chain:
        filename: /certs/sds_cert.pem
      private_key:
        filename: /certs/sds_key.pem

Right now only the second type is generated, to add support for the first type there are a couple of options:

Just add a "type" field to the secret resources in the EnvoyConfig to generate a secret of the "CA type"
Add a generic mechanism to generate secrets for envoy sds, where you provide a template that fetches the secret values from a generic k8s Secret. There are more types of secrets in envoy's sds protocol that certificate and ca, and this mechanism would cover them all.

Also a combination of both options would be good, option 1 for easy CA managemenr for validation contexts, and option 2 for a generic mechanism that potentially cover other uses of sds.

Example of defining a CA within a type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret proto:
resources:
  - "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"
    name: validation_context_sds
    validation_context:
      trusted_ca:
        filename: /certs/cacert.pem

which is slightly different from how a certificate is defined:
resources:
  - "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret"
    name: tls_sds
    tls_certificate:
      certificate_chain:
        filename: /certs/sds_cert.pem
      private_key:
        filename: /certs/sds_key.pem

Right now only the second type is generated, to add support for the first type there are a couple of options:

Just add a "type" field to the secret resources in the EnvoyConfig to generate a secret of the "CA type"
Add a generic mechanism to generate secrets for envoy sds, where you provide a template that fetches the secret values from a generic k8s Secret. There are more types of secrets in envoy's sds protocol that certificate and ca, and this mechanism would cover them all.

Also a combination of both options would be good, option 1 for easy CA managemenr for validation contexts, and option 2 for a generic mechanism that potentially cover other uses of sds.

Example usage:
apiVersion: marin3r.3scale.net/v1alpha1
kind: EnvoyConfig
metadata:
  name: config
  namespace: test
spec:
  nodeID: proxy
  resources:
    - type: secret
      generateFromTlsSecret: ca
      blueprint: validationContext


⚠ ClamAV has degraded performance

In 5fcce0e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 198 ms

Resolved: ClamAV performance has improved in 7f9ce20.


Question : Is there a way to convert markdown text to plain text

One method is to convert it to HTML and then parse it to extract plain text . I was wondering if there is direct way to do it

Why should you want to convert Markdown to Plain text? It already is, isn't it?

Markdown: something *bold* and _underlined_
Text: something bold and underlined


Added link to PEP-8

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

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

Thank you for your contribution.  At this time we have decided not to merge your pull request.  We welcome future pull requests from you.
Reason: A previous pull request added a similar link.  Please ensure you update your repo to the latest version of the freeCodeCamp/master branch before submitting future PRs.
Happy Coding!


[scalardb-cluster] Add startup probe in ScalarDB Cluster chart

This PR adds Startup Probe in the ScalarDB Cluster chart.
Sometimes, ScalarDB Cluster takes a bit long time to start and return Ready state (i.e., SERVING in gRPC health check). However the initialDelaySeconds of Readiness/Liveness Probe is fixed value. In other words, if it takes over 60sec to start process, the pod will be killed by Kubernetes and there is a possibility that the CrashLoopBackOff.
To avoid this issue, we can use Startup Probe instead of initialDelaySeconds. This is a better way in the Kubernetes environment to handle health checking when that pod starting process.
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
We can run the health check before Readiness/Liveness Probe starts when the pod starting process by using Startup Probe. After only Startup Probe succeeded, Kubernetes runs Readiness/Liveness Probe. So, we can avoid unexpected pod killing by Liveness Probe even if ScalarDB Cluster take a bit long time to starts (I set the timeout 300sec by default).
Please take a look!

According to the discussion and investigation result in the following comment, I removed readinessProbe.
https://github.com/scalar-labs/helm-charts/pull/220#discussion_r1197511801


[1.12.2] Crash upon loading the game

Issue description:
Crashing during game load up, NPE
What happens:
When starting the game, it crashes with a NPE from RS EnergyCapability
What you expected to happen:
For the game to load so i could play it lulz
Steps to reproduce:

Install Forge
Install RS
Start game

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>57
Refined Storage: 1.5.32

Does this issue occur on a server? Untested, mainly a solo player
If a (crash)log is relevant for this issue, link it here:
crash-2018-04-15_01.13.44-client.txt
2018-04-15-1.log.gz

Downgrade Forge

@raoulvdberge could you please specify which version you recommend? It would greatly appreciated.

@hron84 i downgraded to Forge: <IP_ADDRESS>53 and that seems to work fine, no crashing

@ApexModder thanks, I'll check it tonight


pass text editor to completion support

I don't like this solution too much because of casts to Cell everywhere. And I am not sure about text CellPropertySpecs location.
I am going to get rig of CompletionSupport.INITIAL_TEXT_PROVIDER if EDITOR spec is accepted.

Commit looks good except that TextCell implements TextEditorCell. We shouldn't break layered architecture which we have.


Date format not the same in all views.

When setting the preferred date format in the account settings, this format is used in the logbook overview, but not when entering new QSOs (e.g. in Live-QSO).
The preferred date format should be used everywhere.
Wavelog V1.6.1

I agree that the date format should be used everywhere. It's not so easy to do in the QSO entry page.
An attempt was made in Cloudlog a few years back, but it turned out that the date was not saved correctly in the database with certain formats.
Perhaps @T012m3n7oR would be up for giving it a go in Wavelog?

A suggestion for a potential fix that would be a breaking change.  Note: I haven't looked at the source code at all so this might not be a solution at all.
Always store the date in the db in a std format and transform that on the client side or when communicating with third party api's to the preferred format.
M7 SPK - just taking a look at the software and saw the open issues tagged help wanted.


Support for GPO, OU and container harvesting

Now Bloodhound.py can collect GPO, OU and containers.

There are probably some minor adjustments to be made, but the core is there!

hey, would love to merge this but this repo requires signed commits to merge. Could you re-submit the PR with signed commits? (either set up GPG or make the changes in the github editor)


Fix no value found

Fix for #10
I used @fuero's PR for unit tests (#9), so we should merge that first, then this PR would change the tests to account for this new behaviour fix.
So, this is technically a breaking change, as it changes the fail behaviour when a key is not found. Since this module hasn't hit a major version yet, semantically it's fine but it would be nice to add a note! 👍

#7 is a better implementation IMO


the user p2p cert information

the user p2p cert is not in the current user store, and it's valid only for 1 hour.
The information in the doc is not correct.

@shanjin90 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

I confirmed from lab and logs.:

the cert is not in current user store;
it valids for 1 hour

@MicrosoftGuyJFlo
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

Resolved by PG in referenced PR #please-close


Missing quotations in Index

Thanks this was merged in https://github.com/nicolaiarocci/cerberus/commit/c251f766904d5801081ea93cd8d1570153551723


Improvment : add .265 .h265 .hevc .hvc files reconized by the source file browser please

Last thing i will bother you with ( I really hope ) :
When selecting a file as source StaxRip recognize and filter automatically a bunch of file formats as seen here :

Will it be possible to add also the following ones to the list please :
.265
.h265
.hevc
.hvc
If you wonder about .hvc one it's the extension mp4box uses when it extracts a hevc stream from a mp4 using his own demuxing option, a mp4 containing x265 video stream will have the video track extracted as .hvc
Not a big deal but it will spare the need to switch to " all files (*)" and it's always better to have less files displayed as been filtered with the first option
Thank you very much.

Thanks for reporting, it's fixed in the next build.

Just saw they were added on last version, thanks a lot Stax


Vue's Devtool still show up after NODE_ENV set to production in 2.x

Vue.js version
2.0.0-rc.8
The devtool is hidden correctly in 1.0.28 but still appear when using 2.0.0-rc.8
What is Expected?
Vue's devtool doesn't show up anymore in chrome's dev console
What is actually happening?
Vue's devtool still show up in chrome's dev console

Please make sure to read the Issue Reporting Guidelines before opening new issues. The issue list only accepts bug reports and feature requests. Questions should be posted to the Gitter chat room,  forum or StackOverflow. Thanks.

That's not enough, the variable need to be replaced on the code. Check the templates for help about how to setup that: https://github.com/vuejs-templates/webpack


undefined reference to 'Bockchain::Blockchain()'

ide used : codeblocks

how to recover this issue

@sourajeetmohanty  Have you tried "g++" compiler instead of "gcc". For example, g++ -std=c++11 main.cpp Block.cpp Blockchain.cpp sha256.cpp -o TestChain?
I also don't see entire error message. It would be helpful if you paste entire error message instead of screenshot.


Updated test-resources to add eventhubs host name

Updated test-resources.json to export FQDN for eventhubs instance.
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

Does this need to be merged before the release today, or can it happen after?

This blocks our CI pipeline from running. We can't release without the CI pipeline running.


MINOR: update README with how to run code coverage on module. add reportCoverage at subProject level

@ijuma

@guozhangwang


star-citizen 1.6.10 -> 2.0.3

Bump star-citizen to 2.0.3
Bump winetricks to git versions
Add options enableGameScope gameScopeArgs

Placing this as draft, submitting a PR to nixpkgs for proton-ge-9-12 which would change things for this package as well.

Considering bumping this to 2.0 launcher, proton-ge-12 has the powershell fixes. latest git for winetricks has it as well.
@fufexan do you have any opinions on adding winetricks-git to this repo?

No objections, feel free.

proton-ge-bin update is now in nixpkgs-unstable
this PR is not ready to be merged until #201 is in

Confirmed game is running as expected.

Oops, looks like npins is conflicting.

Launcher has been bumped to 2.0.5 and wine has been updated from wine-ge to latest wine stable.


fix: check db and indices for canonical block

Fixes #2689
Previously we were only checking the indices when determining whether or not a block is already canonical in make_canonical. Calls to engine_forkchoiceUpdated for historical blocks would return SYNCING because the block would not be found in memory, and the call to is_block_hash_canonical would only check the canonical blocks tracked in memory.
This introduces a new method is_block_hash_canonical on the blockchain tree, which also checks the db if it cannot find the canonical block in memory.

Codecov Report

Merging #2702 (fa19326) into main (c441170) will decrease coverage by 53.78%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2702       +/-   ##
===========================================
- Coverage   71.36%   17.58%   -53.78%
===========================================
  Files         502      503        +1
  Lines       65065    65088       +23
===========================================
- Hits        46435    11448    -34987
- Misses      18630    53640    +35010

Flag
Coverage Δ

integration-tests
17.58% <0.00%> (-0.03%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/blockchain-tree/src/blockchain_tree.rs
0.00% <0.00%> (-85.10%)
:arrow_down:

... and 356 files with indirect coverage changes

need to fix tests

Why does this test expect Syncing if the block is known and valid?
https://github.com/paradigmxyz/reth/blob/ca6724f1069a034f1e5f87dbfdc0ac5518c121cf/crates/consensus/beacon/src/engine/mod.rs#L1246-L1261


karma helm chart - new v0.116 released

Hello,
https://github.com/prymitive/karma
https://github.com/prymitive/karma/releases/tag/v0.116

Sorry, I haven't answered here.
It is simple: PR accepted! ;)


failed migrations should cause deployment to stop

see this issue: #251
it has a situations where there are errors in deploy log, but deployment continued
it's very important to ensure that deployment stops on any error
you can see how server is setup in this document: https://github.com/Midburn/Spark/blob/master/docs/development/devops.md

@johnyzed can you help with this?

is @johnyzed working on it? if not, please remove him from assignees and add the up-for-grabs label

@OriHoch I am working on it. To be honest i already fixed it in my fork (https://github.com/johnyzed/Spark/commit/0f520f0d4b18c68b85fefd5f9dbee010e2226620), I just want to discuss with the guys on wednesday about a more generic solution, so I wanted to wait before submiting my PR

@johnyzed  - better to open a pull request and prefix the title with [WIP] - so we know not to merge it
WIP = work in progress

@johnyzed Done?


Dynamic libraries do not support arm64

ld: warning: ignoring file /Users/myself/Downloads/flutter_barcode_sdk-main/macos/lib/libDynamsoftBarcodeReader.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:
"OBJC_CLASS$_DynamsoftBarcodeReader", referenced from:
objc-class-ref in FlutterBarcodeSdkPlugin.o
"OBJC_CLASS$_iTextResult", referenced from:
objc-class-ref in FlutterBarcodeSdkPlugin.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **

arm64 will still give an error：
ld: warning: directory not found for option '-L/Users/myself/Downloads/flutter_barcode_sdk-main/example/macos/../../macos/libs'
dyld[86770]: Library not loaded: @loader_path/libDynamsoftBarcodeReader.dylib
Referenced from:  /Users/myself/Downloads/flutter_barcode_sdk-main/example/build/macos/Build/Products/Debug/flutter_barcode_sdk_example.app/Contents/MacOS/flutter_barcode_sdk_example
Reason: tried: '/Users/myself/Downloads/flutter_barcode_sdk-main/example/build/macos/Build/Products/Debug/flutter_barcode_sdk_example.app/Contents/MacOS/libDynamsoftBarcodeReader.dylib' (no such file), '/usr/local/lib/libDynamsoftBarcodeReader.dylib' (no such file), '/usr/lib/libDynamsoftBarcodeReader.dylib' (no such file, not in dyld cache)
Error waiting for a debug connection: The log reader stopped unexpectedly, or never started.
Error launching application on macOS.

@sliderss currently, the mac dylib only supports x86_64

@sliderss here are the arm64 dylibs
Mac_Arm64.zip

@sliderss  I apologize for the inconvenience, but according to the package publishing policy, a package must be smaller than 100 MB after gzip compression. The use of universal dylib files would exceed this size limit for my package. Thank you for your understanding.

@yushulx thank you.

what should we do with this zip file ?

@TamirlanBir extract the dylib files from the zip file and overwrite the dylib files in https://github.com/yushulx/flutter_barcode_sdk/tree/main/macos/lib

The latest v2.2.5 has replaced x86_64 libs with arm64 libs in macOS plugin.

@TamirlanBir @sliderss Please try v2.2.5.


Add ability to manually set token if running in docker/without GUI

I had to start Python and import the set_token function manually without this change, this makes it a bit easier

I would try mounting the token file into the container as a volume

Yeah, I would either mount as a volume or write the file manually. Not sure how this is easier than writing the file.


Fetching stories from an RSS feed not working.

Hello @rahulbot  @dsjen  @pypt
We have been trying to pull stories from this RSS feed and also for this (I picked the RSS data from an active rss feed that has been fetched from another site so I'm sure it works if pulled from that website.).
Is there something that we are missing in order to be able to fetch stories off an rss feed URL?
There aren't any errors that we can find to attach here.
The only interesting thing that happens is a new RSS feed gets created and it also gets marked Disabled automatically as shown below

The only thing weird in that screenshot is the URL - it has the package names prepended to the URL. Did you add those or is there some bug in the system that added them?

The system automatically added them.


BF(dependencies)| Bump text_unidecode version

1.2 -> 1.3

Fixes #82

Please issue PR to the staging branch ...

@un33k is it ok like this ?

Thank you for your contribution. I will publish this on the next release cycle. Soon.

Please upgrade to https://github.com/un33k/python-slugify/tree/3.0.4


Failing to deploy on PHP 5.6

Currently getting following error:
Generating optimized autoload files
PHP Parse error:  syntax error, unexpected '[', expecting ')' in /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/react/promise/src/functions.php on line 68
PHP Stack trace:
PHP   1. {main}() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/artisan:0
PHP   2. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/artisan:16
PHP   3. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/bootstrap/autoload.php:17
PHP   4. ComposerAutoloaderInit4d73418afec9fbbb9e59fdeb8b7d28a8::getLoader() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/autoload.php:7
PHP   5. composerRequire4d73418afec9fbbb9e59fdeb8b7d28a8() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/composer/autoload_real.php:49
PHP   6. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/composer/autoload_real.php:58
Script php artisan optimize handling the post-install-cmd event returned with an error

  [RuntimeException]
  Error Output: PHP Parse error:  syntax error, unexpected '[', expecting ')' in /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/react/promise/src/functions.ph
  p on line 68
  PHP Stack trace:
  PHP   1. {main}() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/artisan:0
  PHP   2. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/artisan:16
  PHP   3. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/bootstrap/autoload.php:17
  PHP   4. ComposerAutoloaderInit4d73418afec9fbbb9e59fdeb8b7d28a8::getLoader() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/autoload.php:7
  PHP   5. composerRequire4d73418afec9fbbb9e59fdeb8b7d28a8() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/composer/autoload_real.php:49
  PHP   6. require() /var/lib/openshift/550b92394382ec66d0000177/app-root/runtime/repo/web/vendor/composer/autoload_real.php:58

Tested with react/promise 2.2/2.1 & php 5.6.4

What's your setup? I'm running PHP 5.6.0 and it's working fine. Since it's react that seems to be causing the error, I'd suggest it's your environment.

After a few more looks, problem solved,
The installation was done on Redhat Openshift with a custom php. On a closer look at composer.json, composer tries to run the system-installed php which does not work with Cachet.
Manually modifying the commands to reflect the proper php binary fixes things. Is there some way I can reference the proper php binary without having to break upgrades?
Thanks for your help :)


German language: Section sign missing

On German computer keyboards the section sign "§" can be typed using Shift+3 so it is easily writable. In AnySoftKeyboard with German language layout I cannot see how to write this sign at all. I tried all buttons in all keyboard-views by long pressing on them. Inside the Android standard AOSP keyboard the section sign can be typed by long pressing on the pilcrow (¶). I think the section sign was simply forgotten.

@Flnch which German language pack are you using?

@menny I'm not exactly sure what you intend with language pack, "Deutsch breit +"?

I guess, what I'm asking is where did you download the pack from? Can you
share a link?
On Wed, Feb 28, 2018, 2:45 PM Flnch<EMAIL_ADDRESS>wrote:

@menny https://github.com/menny I'm not exactly sure what you intend
with language pack, "Deutsch breit +"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AnySoftKeyboard/LanguagePack/issues/117#issuecomment-369359795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdX-FHaSW7T0jXT--HXjxFvEzjaCtMxks5tZazigaJpZM4Rdn7t
.

Oh okay. I downloaded it from F-Droid. The link is https://f-droid.org/app/com.anysoftkeyboard.languagepack.german

Hi. While at it, I have exactly the same issue with Czech layout (also from F-Droid). On S, it includes the German ẞ (not needed in Czech) but not § which we use in every law (sometimes needed very much).

Hey, i'm also affected. Is there any fix for this issue?