Get-RubrikVM inconsistent results

Current Behavior:
Get-RubrikVM -name “XXX” doesn’t return all values yet if i issue
Get-RubrikVM -name “XXX” | Get-RubrikVM I get additional data?
Specifically the first call doesn’t return the blackout window, whereas the second call piped through the first call does
blackoutWindows : @{globalBlackoutWindows=System.Object[]; snappableBlackoutWindows=System.Object[]}
Paste the verbose output from the command here

Expected Behavior:
Same output for Get-RubrikVM and Get-RubrikVM -Id
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.
Get-RubrikVM -name “XXX” doesn’t return all values yet if i issue
Get-RubrikVM -name “XXX” | Get-RubrikVM I get additional data?
Context:
On the API side of things, will rework Get-RubrikVM to give consistent results regardless of parameter set used.

Closed in #264


Missing some iOS icons

Noticed we are still missing icons for iOS.
On XCode if I inspect the assets, I can find these missing ones (more details below):

Location:
-src-cordova/platform/ios/AppName/Images.xcassets/AppIcon.appiconset
Files I took from this folder:
missing icons.zip

I'm not sure if these are the icons you are looking for...
Should I also search inside my src-cordova/res/ folder?

Thanks! That's perfect.

Btw i’m using cordova with ios5
Dont know if the version is important ^^


Host Name Cannot Be User-Defined

It seems that there is a bug in the javax.jmdns.impl.HostInfo class and its newHostInfo(InetAddress address, JmDNSImpl dns, String jmdnsName) method. In my project it is mandatory to export a gateway as mDNS device with host name using the following pattern:
Miele-.local.
So we are using the following code for the creation of the JmDNS instance for exporting the Gateway:
jmDNS = JmDNS.create(InetAddress.getLocalHost(), hostName);
where the hostName is created according the pattern described above. Using the library the Gateway was always exported with the Host name of the box but not the one which is passed as parameter. I found something which looks like a bug in the newHostInfo method. Here is the original source:
public static HostInfo newHostInfo(InetAddress address, JmDNSImpl dns, String jmdnsName) {
    HostInfo localhost = null;
    String aName = (jmdnsName != null ? jmdnsName : "");
    InetAddress addr = address;
    try {
        if (addr == null) {
            String ip = System.getProperty("net.mdns.interface");
            if (ip != null) {
                addr = InetAddress.getByName(ip);
            } else {
                addr = InetAddress.getLocalHost();
                if (addr.isLoopbackAddress()) {
                    // Find local address that isn't a loopback address
                    InetAddress[] addresses = NetworkTopologyDiscovery.Factory.getInstance().getInetAddresses();
                    if (addresses.length > 0) {
                        addr = addresses[0];
                    }
                }
            }
            if (addr.isLoopbackAddress()) {
                logger.warn("Could not find any address beside the loopback.");
            }
        }
        if (aName.length() == 0) {
            aName = addr.getHostName();
        }
        if (aName.contains("in-addr.arpa") || (aName.equals(addr.getHostAddress()))) {
            aName = ((jmdnsName != null) && (jmdnsName.length() > 0) ? jmdnsName : addr.getHostAddress());
        }
    } catch (final IOException e) {
        logger.warn("Could not intialize the host network interface on " + address + "because of an error: " + e.getMessage(), e);
        // This is only used for running unit test on Debian / Ubuntu
        addr = loopbackAddress();
        aName = ((jmdnsName != null) && (jmdnsName.length() > 0) ? jmdnsName : "computer");
    }
    // A host name with "." is illegal. so strip off everything and append .local.
    // We also need to be carefull that the .local may already be there
    int index = aName.indexOf(".local");
    if (index > 0) {
        aName = aName.substring(0, index);
    }
    aName = aName.replaceAll("[:%\\.]", "-");
    aName += ".local.";
    localhost = new HostInfo(addr, aName, dns);
    return localhost;
}

and here is the fix which we've done:
public static HostInfo newHostInfo(InetAddress address, JmDNSImpl dns, String jmdnsName) {
    HostInfo localhost = null;
    String aName = (jmdnsName != null ? jmdnsName : "");
    InetAddress addr = address;
    try {
        if (addr == null) {
            String ip = System.getProperty("net.mdns.interface");
            if (ip != null) {
                addr = InetAddress.getByName(ip);
            } else {
                addr = InetAddress.getLocalHost();
                if (addr.isLoopbackAddress()) {
                    // Find local address that isn't a loopback address
                    InetAddress[] addresses = NetworkTopologyDiscovery.Factory.getInstance().getInetAddresses();
                    if (addresses.length > 0) {
                        addr = addresses[0];
                    }
                }
            }
            if (addr.isLoopbackAddress()) {
                logger.warn("Could not find any address beside the loopback.");
            }
        }
        if (aName.length() == 0) {
            aName = addr.getHostName();
        }
        if (aName.contains("in-addr.arpa") || (aName.equals(addr.getHostName()))) {
            aName = ((jmdnsName != null) && (jmdnsName.length() > 0) ? jmdnsName : addr.getHostAddress());
        }
    } catch (final IOException e) {
        logger.warn("Could not intialize the host network interface on " + address + "because of an error: " + e.getMessage(), e);
        // This is only used for running unit test on Debian / Ubuntu
        addr = loopbackAddress();
        aName = ((jmdnsName != null) && (jmdnsName.length() > 0) ? jmdnsName : "computer");
    }
    // A host name with "." is illegal. so strip off everything and append .local.
    // We also need to be carefull that the .local may already be there
    int index = aName.indexOf(".local");
    if (index > 0) {
        aName = aName.substring(0, index);
    }
    aName = aName.replaceAll("[:%\\.]", "-");
    aName += ".local.";
    localhost = new HostInfo(addr, aName, dns);
    return localhost;
}

Using this fix now my gateway is always exported using the pattern I want to use. I'd like to ask you to check whether this is really a bug or I'm not using the correct methods.

Hi @danieljanev,
Sorry for coming back so late on this.
Before merging, I tried to dive into the code to understand the change - which I actually fail to do.
I have written this test:
    @Test
    public void testNewHostInfo() throws IOException {
        String mDNSName = "Miele-.local.";
        JmDNS jmdns = JmDNS.create(InetAddress.getLocalHost(), mDNSName);
        assertEquals(jmdns.getHostName(), mDNSName);
    }

which is green, even without your change. So what exactly is the problem you are trying to address? Would be great if you could add an according unit test to your PR, which is red on the current code and becomes green with your changes.

Hi @kaikreuzer
The main problem is that the mDNS device is exported in the network using the host name of the machine but not the specified one. E.g. on QIVICON box the name is QIVICON.local. but not Miele-1234567890.local.

How to capture this in a test? Even if I do
        String mDNSName = "Miele-.local.";
        JmDNS jmdns = JmDNS.create(InetAddress.getByName("<IP_ADDRESS>"), mDNSName);
        assertEquals(jmdns.getHostName(), mDNSName);

        jmdns = JmDNS.create(InetAddress.getByName("<IP_ADDRESS>"), null);
        assertEquals(jmdns.getHostName(), "localhost.local.");

everything is green. And it shows that the "name" parameter is clearly taken into account, even if a hostname for the ip address can be resolved.

I'm not sure we can check it with a test. We found this problem using the JmDNS browser :(

Well, if you claim that the change in HostInfo fixes a bug, you should be able to specify which input to this method results in which wrong output.

@danieljanev Any success in your further analysis? If not, I would suggest to close this PR for the moment.

@kaikreuzer I'll try create a test till the end of the week. Too busy with some internal product work these days ...

I plan to do a new JmDNS patch release on Thursday - so if you want this in, better do it mid than end of the week ;-) Otherwise, we will schedule it for the next one.

@danieljanev What is the status on this? Are you still convinced that there is a bug in the code? If so, let us address this as I plan to do a new patch release soon!

@danieljanev Would be great if you could briefly comment!

Agree with issue starter.
You can see that Service name equals to the target name. "SlavkaAndroid._airplay._tcp.local:" to the "target SlavkaAndroid.local" what is not good.
SlavkaAndroid._airplay._tcp.local: type SRV, class IN, cache flush, priority 0, weight 0, port 7000, target SlavkaAndroid.local
    Service: SlavkaAndroid
    Protocol: _airplay
    Name: _tcp.local
    Type: SRV (Server Selection) (33)
    .000 0000 0000 0001 = Class: IN (0x0001)
    1... .... .... .... = Cache flush: True
    Time to live: 3599
    Data length: 22
    Priority: 0
    Weight: 0
    Port: 7000
    Target: SlavkaAndroid.local

We have to get something like:
SlavkaDesktop._airplay._tcp.local: type SRV, class IN, cache flush, priority 0, weight 0, port 7000, target DESKTOP-1UVTC9H.local
            Service: SlavkaDesktop
            Protocol: _airplay
            Name: _tcp.local
            Type: SRV (Server Selection) (33)
            .000 0000 0000 0001 = Class: IN (0x0001)
            1... .... .... .... = Cache flush: True
            Time to live: 120
            Data length: 24
            Priority: 0
            Weight: 0
            Port: 7000
            Target: DESKTOP-1UVTC9H.local

I`m sure you can see the difference. Big problem for me as for now.
Thanks

We made an investigation on this issue. Tests and code analysis show, that the existing code is complete correct in regard of this issue.
Additionally, the proposed change does not change anything in this situation, because the effected if-clause is not executed anyway if using a custom name, not without the change and not with the change.

Thanks @sobimibos, this was also the result of my analysis, see above.
@danieljanev & @LionisIAm It would be hugely helpful if you could come up with a test case that clearly shows your issue and which can prove that the suggested change fixes it. I think you agree that by looking at the change, it simply does not seem to make any kind of sense.

As there is no feedback since summer 2016, I am closing this PR now.
Once you have figured out a test case and can explain the suggested change, feel free to re-open it.


Added Authentication

Test Instructions

Open https://deploy-preview-21--create-app.netlify.app/
Should see a login form
Log in using your door43 credentials
refresh the page, the login should persist
Open the menu drawer by clicking the hamburger icon
Log out by clicking the logout button at the bottom of the drawer menu
Should render the login screen

This change is

@mannycolon In testing, if I do not check "keep me logged in" when logging in, that refreshing the page takes me back to login screen. Is this the expected behavior?

@mannycolon In testing, if I do not check "keep me logged in" when logging in, that refreshing the page takes me back to login screen. Is this the expected behavior?


eco-ci-output.txt is empty for GitLab pipeline

Hi guys, I'm trying to measure a GitLab job like this, but the resulting eco-ci-output.txt is empty.
image: ubuntu:22.04

services:
  - openjdk:11-jre-buster

include:
  remote: 'https://raw.githubusercontent.com/green-coding-berlin/eco-ci-energy-estimation/main/eco-ci-gitlab.yml'

stages:
  - build

build:
  stage: build
  script:
    - apt-get update
    - apt-get install default-jdk -y
    - export ECO_CI_LABEL="build"
    - !reference [.initialize_energy_estimator, script]
    - !reference [.start_measurement, script]
    - chmod +x ./gradlew
    - ./gradlew check assemble
    - !reference [.get_measurement, script]
    - !reference [.display_results, script]
  artifacts:
    paths:
      - eco-ci-output.txt

Here's the console output:
...
$ echo 'running eco-ci start script' # collapsed multi-line command
running eco-ci start script
⚠ Unknown model model name	: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
model name	: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
model name	: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
model name	: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz for estimation, running default ...
$ chmod +x ./gradlew
$ ./gradlew check assemble
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :compileJava
> Task :processResources
> Task :classes
> Task :bootJarMainClassName
> Task :bootJar
> Task :jar
> Task :compileTestJava
> Task :processTestResources
> Task :testClasses
> Task :test
> Task :check
> Task :assemble
BUILD SUCCESSFUL in 2m 37s
8 actionable tasks: 8 executed
$ echo 'running eco-ci measure script'
running eco-ci measure script
$ repo=$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME # collapsed multi-line command
38.38 32.23 17.45 8.14 8.12 12.92 4.24 5.53 5.53 11.05 10.00 4.96 12.04 30.50 54.75 58.46 60.90 58.75 81.42 59.45 64.65 60.15 62.53 61.90 62.56 48.48 38.89 40.70 72.50 50.51 40.46 99.50 99.50 58.19 57.89 61.10 62.96 81.27 81.30 58.69 71.54 67.34 69.00 72.39 35.13 27.66 21.88 24.23 14.73 10.31 9.14 17.01 13.40 13.33 19.49 53.52 53.79 53.02 52.76 53.88 52.63 52.90 53.16 48.74 60.45 73.30 65.49 74.00 84.38 70.28 92.11 90.50 87.68 89.90 88.35 88.24 90.45 90.00 86.40 88.80 84.74 86.22 87.82 83.59 66.67 50.89 46.08 40.61 53.03 53.25 51.13 48.36 55.42 43.25 50.00 44.16 57.18 78.48 67.17 78.59 56.96 52.79 74.25 65.91 76.59 77.27 62.53 61.21 60.86 64.82 72.98 67.34 63.61 60.00 61.15 61.77 66.08 94.71 76.32 60.45 56.53 70.43 67.51 61.27 65.49 62.28 70.85 64.91 60.05 61.46 57.68 78.50 71.07 73.37 74.37 59.19 61.65 86.65 70.85 84.79 97.24 82.78 82.16 62.03 56.64 59.75 61.62 54.27 83.17 73.05 60.10 79.35 37.75 0.00 8.50 1.25 36.00
$ echo 'running eco-ci display script'
running eco-ci display script
$ FORMAT_CLR="\e[44m" && TXT_CLEAR="\e[0m" # collapsed multi-line command
cat: /tmp/eco-ci/output-short.txt: No such file or directory
$ echo -e "$FORMAT_CLR$(cat /tmp/eco-ci/output.txt)$TXT_CLEAR"
$ cp /tmp/eco-ci/output.txt ./eco-ci-output.txt
section_end:1689932512:step_script
section_start:1689932512:archive_cache
Saving cache for successful job
Creating cache default...
WARNING: /tmp/eco-ci/venv/: no matching files
Archive is up to date!
Created cache
section_end:1689932512:archive_cache
section_start:1689932512:upload_artifacts_on_success
Uploading artifacts for successful job
Uploading artifacts...
eco-ci-output.txt: found 1 matching files and directories
Uploading artifacts as "archive" to coordinator... ok
section_end:1689932513:upload_artifacts_on_success
section_start:1689932513:cleanup_file_variables
Cleaning up file based variables
section_end:1689932514:cleanup_file_variables
Job succeeded

Hey @NatalieZava , nice that you are trying out the Eco-CI to measure your pipelines!
What I see in the debug is that the CPU is not found, which is suprising as we are currently not aware that Gitlab Shared runners are using different CPUs than the AMD Epyc ones.
=> Are you running on Gitlab shared runners or in a self hosted instance?

@dan-mm Could you look into the error that /tmp/eco-ci/output-short.txt does not exist and thus 'eco-ci-output.txt' cannot be popuplated?

Hi @dan-mm and @ArneTR - Thanks! It's working now 🤩

Hey @NatalieZava : Do you still have a reply for us if you are using a shared runner or a self-hosted one?
We have never seen this line before and are curious where the unknown CPU is coming from:
Unknown model model name	: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz


Implement edge-to-edge on branch main

Please add a scroll bar to the app so that it can be used in landscape mode. Otherwise, the app is not usable.

Not related to this PR.
Readme has TODO, could you please remove them?


Define order for packageid: query results for FindPackagesById hijack

Today, the order is defined by downloads then doc ID.
Related:
https://github.com/NuGet/NuGetGallery/issues/5431

The root cause is that gallery specifies a document ordering for FindPackagesById hijacks that has an unpredictable order for documents with the same ID. The hijack passes sortBy=relevance which is an unmapped sort by mode. Therefore, search service falls back to the default sort by mode, which is by Lucene query score (which is essentially our notion of relevance).
For packages with the same ID, it is very likely that many of the versions have similar metadata. Therefore, Lucene assigns the same score. In the NLog case, there were only two distinct scores assigned to the 27 versions we tested. Therefore, within the two score groupings, the order of the documents was defined by their Lucene document ID.
The Lucene document ID is an incrementing integer generated by Lucene when a document is added to the index. When a package's unlist status changes or if the package is reflowed, catalog2lucene performs an update on the document, which in Lucene is actually a delete then add. Therefore, the document ID for that package changes due to user or admin action.
Additionally, when an index is rebuilt, many if not all of the document IDs will change, since the order in which they were added to the index is based off of database (db2lucene) instead of catalog.
In other words, this problem happens any time we do an index rebuild. The degree of impact is based off of how recently we have done an index rebuild and how many old packages have been reflowed, relisted, or unlisted. If a package ID has had no new versions published since the last index rebuild and no catalog items have been produced, the relative ordering of the versions will remain constant.

My proposed fix is to change the sortBy that gallery passes to search service during a hijack. The sort should have the following principles:

Defined by some document field, not document ID. This means the sort will remain consistent from one index rebuild to the next.
Monotonically increasing. Having new documents appear in the middle of the order means that paging performed as that document is added will miss the new document. New documents should appear at the end of the results.
Immutable per version. An existing package should not be able to move to the edit of the list due to some user or ops action.

There are four supported sortBy modes today (excluded the default relevance sort).
https://github.com/NuGet/NuGet.Services.Metadata/blob/25b24c93fc6bfd88511cd8d6cc65a41cf8a32d9d/src/NuGet.Indexing/GalleryServiceImpl.cs#L124-L129
published is not appropriate since unlisted packages all have the same published date: year 1900 (except for https://github.com/NuGet/NuGetGallery/issues/5435).
title-asc and title-desc are not appropriate since a lot of packages all have the same title.
lastEdited is not appropriate since it is not immutable per version. Also, last edited resolution is day so order is defined by document ID if two packages were edited on the same the day.
Therefore, I propose introducing a new sortBy which is created and based off of the packages created date. Note that this isn't perfectly monotonically increasing but it should be Close Enough™. Note that package key has the same following caveats as created and therefore doesn't help us.

Hard delete then recreate will cause a change, breaking principle number 3.
Async validation means packages come in out of order, breaking principle number 2.
DB commits of new packages do not necessarily get commits in the same order they are started, also breaking principle number 2.

tl;dr: the best I think we can do is by making FindPackagesById() ask for results sorted by package created date, which requires a new document field CreatedDate and a new sort field.


[Windows] Vitest can not run in folders that are symlinked

Describe the bug
I have symlinked a folder on Windows 11. When running vitest it tells me the file does not exist and gives out the "canonical" path to the file - however this path is absolutely correct and the file exist.
When I run vitest directly in the "canonical" path it works as expected.

Reproduction
This seems to be an issue with resolving directories in NTFS, I don't know how to set up a reproducible environment that is running Windows 11.

Have a machine running Windows 10 / 11 with NTFS file system
Create Folder A and set up a basic vitest project with one test
Run vitest
Everything should be fine here
Go one folder up and create a symlink to Folder A and call it Folder B
mklink /D "Folder B" "Folder A" (Keep in mind that mklink works the other way around than you are used to with ln -s)
Go into Folder B
You should see the files of Folder A, however your path shows Folder B
Run vitest
You will see an error that C:\YourPath\Folder A\yourFile.js can not be found although it is there and you are in Folder B

System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (12) x64 AMD Ryzen 5 5600G with Radeon Graphics
    Memory: 5.60 GB / 15.89 GB
  Binaries:
    Node: 20.6.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.2215.0), Chromium (116.0.1938.69)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @vitejs/plugin-react: ^4.0.4 => 4.0.4
    vite: ^4.4.9 => 4.4.9
    vitest: ^0.34.4 => 0.34.4

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

BTW I'm getting similar errors when running vite server in dev mode:
When I start vite in the symlinked directory I am getting the error:

as if the file was never transpiled.
When I run the command in the canonical folder the error does not happen and the app renders as expected.

Maybe it thinks it's outside of root? If you disable server.fs.strict, will it work?

WOW! Yes that works.
I added
server: {
		fs: {
			strict: false,
		},
	},

OK I fiddled around a little bit more and went with the following instead:
		fs: {
			allow: [__dirname],
		},

which seems redundant but gets the job done

So I assume something like searchForWorkspaceRoot(process.cwd()) is built in as default setting.
What we could do is to check if searchForWorkspaceRoot(process.cwd()) !== __dirname and then also add __dirname to the allowlist.
I guess I would either hook in here: https://github.com/vitejs/vite/blob/c7969597caba80cf5d3348cba9f18ad9d14e9295/packages/vite/src/node/config.ts#L499
or here: https://github.com/vitejs/vite/blob/c7969597caba80cf5d3348cba9f18ad9d14e9295/packages/vite/src/node/server/index.ts#L801
🤔
I would be very happy to submit a PR if you think it makes sense.
Cheers! 👋🏻

I guess I would either hook in here

Actually, we already override it:
https://github.com/vitest-dev/vitest/blob/b75f91d26529d7c6a09bd1d9149e8672c5de978e/packages/vitest/src/node/plugins/utils.ts#L102
But we use root for not, not process.cwd() (which can be system root in docker for example)

Yeah but do I understand it correctly that when the config file is empty we fall back to process.cwd()? And apparently when you are in a symlinked folder on windows it seems like that process.cwd() and __dirname (given __dirname = path.dirname(fileURLToPath(import.meta.url));) return different paths while on UNIX~oid systems they are the same. 🤔
// test-paths.mjs
import path from 'node:path';
import process from 'node:process';
import {fileURLToPath} from 'node:url';

const __dirname = path.dirname(fileURLToPath(import.meta.url));
const processCWD = process.cwd();

console.log('__dirname', __dirname);
console.log('processCWD', processCWD);

So maybe we just need to change it to use __dirname instead of process.cwd() and it will work for all 🤔

__dirname would be the Vitest dist folder though.


Anvil hardcoded chain id when loading genesis

The chain id can be apart of the genesis.json. When parsing the genesis file, anvil sets the default config (chain id == 1), then loads in the file and overwrites the config with the information present in the file.
If the chain id is not apart of that file, then the chain id remains 1, regardless of the --chain-id flag. This presents a problem as we use the flag to set chain id for the chain.
This breaks tests that assert the chain id and will also break transactions that sign over the expected chain id as well.
Reference:
https://github.com/alloy-rs/alloy/blob/902d847c023d9d96d63b753028731261e0871d34/crates/genesis/src/lib.rs#L526
https://github.com/foundry-rs/foundry/blob/72e44fb87c38b2acfa2b0b136fc1bc833f71e674/crates/anvil/src/config.rs#L935

Fixed with generated genesis files


[WebAPI] Make the test suites support Ostro IoT platform on Crosswalk 22 branch

Make the test suites support Ostro IoT platform
Cherry-pick from the master branch.

LGTM


Error about missing file/directory when trying to use

Entirely possible that there's something wrong that I'm doing (not very proficient with GH Actions 😅), but hoping to get some clues about how to address the issue I'm running into...
I'm getting this error when trying to run this action:
Error: ENOENT: no such file or directory, lstat '/opt/hostedtoolcache/ndk/r24/x64/*'

Here's the relevant configuration:
steps:
  - uses: actions/checkout@v4

  - name: Setup NDK
    uses: nttld/setup-ndk@v1
    id: setup_ndk
    with:
      ndk-version: r24 # https://github.com/android/ndk/wiki/Unsupported-Downloads#r24
      local-cache: true

Additional context:

The workflow runs on ubuntu-latest
The workflow uses a matrix configuration

Removed the local-cache option and that seemed to fix it. Would love to get a better understanding of why if possible. I think using the local cache makes sense for my usage (correct me if I'm mistaken), so would be ideal to have it enabled
Otherwise, please feel free to close

My bad, accidentally broke local-cache with 1.4.0. Should be fixed now.


Script doesn't work by default

When using the script it should work by default. Right now I get:
error: Package bitwise v0.1.0 (file:///home/travis/build/gnzlbg/bitwise) does not have these features: unstable
If I comment out the following line:
 - TRAVIS_CARGO_NIGHTLY_FEATURE=nightly

and
error: Package bitwise v0.1.0 (file:///home/travis/build/gnzlbg/bitwise) does not have these features: nightly
if I leave it on.
One solution is to set that line to the empty string
- TRAVIS_CARGO_NIGHTLY_FEATURE=""

but that should be made more obvious. IMO it would be better if the default would be for repos without nightly features to compile as is on nightly, and if some repos need unstable or nightly features the script should explain how to do that, and provide the lines commented out so that just un-commenting them works:
 #- TRAVIS_CARGO_NIGHTLY_FEATURE=nightly
 #- TRAVIS_CARGO_NIGHTLY_FEATURE=unstable

Could probably use cargo metadata for this:
cargo metadata | jq ".packages[0].features"


Is AzureServiceTokenProvider.GetAccessTokenAsync() thread safe?

This is important information to know, I don't want to "new" a AzureServiceTokenProvider on every page request instead would rather hold onto a static instance of one.

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

ID: 315e6bfa-53fd-2ee1-bbda-64204283c6a2
Version Independent ID: cc17a1df-33ce-e6ba-bad9-052010244bff
Content: Service-to-service authentication to Azure Key Vault using .NET
Content Source: articles/key-vault/service-to-service-authentication.md
Service: key-vault
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

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

@MikeGriffinReborn I am checking on this and update you on my findings.

@MikeGriffinReborn The Version 1.3.1 of AppAuthentication library is where a lock is made when a token is not found in the cache to retrieve a valid one. The cache itself is thread safe.

@MikeGriffinReborn We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Write Report on OpenSSF Best Practices Badge program

Status of the projects, for those that have gaps, explanation of them and next steps
Breakdown of what work was done by the project and what work was done by Jordan
Recommendations and analysis of gaps (e.g. single contributor project)
Analysis of the project state (are things better than we thought they were)

Audience For Report

Internal - OpenJS projects, STF
External - Developers using OpenJS projects

I've got a draft here: https://hackmd.io/AlRL1qlMQ8e_cI1oNWZu5w thoughts and comments welcome!


Fixes scroll position reset when pokemon details is opened - (issue - #70)

Closing, conflict with mobile iOS scroll


Fix tracking branches in dynamic repositories

When running GitVersion with a dynamic repository using a new branch it cannot find a remote tracking branch. I dug a bit deeper and found that in GitHelper.CreateMissingLocalBranchesFromRemoteTrackingOnes the remoteTrackingReference is a DirectReference, but I think it should be a SymbolicReference for this to work.
I'm not sure how to fix this as I'm not familiar with LibGit2Sharp. Any advice?

Is this still happening on the V3 beta branch, or is this only on v2?

I tried this on master (97dade8), which is ahead of 3.0.0-Beta3

Just to confirm, the 3.0.0 release hasn't been merged yet:
https://github.com/ParticularLabs/GitVersion/tree/release/3.0.0
Can you try on this?

Sorry, I don't understand, running git merge-base master release/3.0.0 outputs 24fa6b5 which is essentially release/3.0.0, so what do you mean by it hasn't been merged yet?

To the best of my knowledge, although I hadn't checked, the beta code hasn't been merged to master, but I could be wrong.  @JakeGinnivan could confirm.
You could well be right, and I am just a little behind :smile_cat:

Yeah, GitHub also says that release/3.0.0 is 0 commits ahead of master and 4 commits behind it :-)

Sorry for confusion, I am just using release branch for releasing betas. Am keeping master in sync/ahead
Sent from my Windows Phone

From: Johannes<EMAIL_ADDRESS>Sent: 15/06/2015 09:54
To<EMAIL_ADDRESS>Subject: Re: [GitVersion] Fix tracking branches in dynamic repositories (#464)
I tried this on master (97dade8https://github.com/ParticularLabs/GitVersion/commit/97dade82877fae86d6f0f106bc21aae9fa06d32c), which is ahead of 3.0.0-Beta3
—
Reply to this email directly or view it on GitHubhttps://github.com/ParticularLabs/GitVersion/pull/464#issuecomment-111983608.

Ping @nulltoken, thoughts on the libgit2sharp question?

I dug a bit deeper and found that in GitHelper.CreateMissingLocalBranchesFromRemoteTrackingOnes the remoteTrackingReference is a DirectReference, but I think it should be a SymbolicReference for this to work.

@JakeGinnivan Thanks for the ping!
@eggapauli Could you please elaborate further regarding what makes you think that?

I was wrong. I think the problem was that a local ref was added, but it wasn't set up to track the remote ref.
I tried to do this in the second commit. Again, I'm not familiar with libgit2sharp and found your answer on how to update a branch to track a remote one.


Fix various minor HTML and React component issues

This PR fixes a few minor issues across the site:

[x] Fixed og:image path on blog pages
[x] Added missing and resolved duplicate key props to mapped React components. See React's docs for more info.
[x] Fixed many prop type issues
[x] Fixed invalid HTML nesting errors. Various issues such as nesting a <p> in a <p>, or a <p> in a <div>, or an <a> in an <a> were throwing errors and can cause issues with browsers.

Note: it looks like gatsby-plugin-image and MDX are having some issues as gatsby images (which are wrapped in a <div>) are being wrapped in a <p> tag. We'll need to fix separately.

@MrPowers could you please review when you get the chance?  Thanks!


Documentation on how to contribute to the platform

User Story
We need some documentation on how to contribute to the platform and our modules, best practices, testing etc.
User Type(s)
MP Users and engineers
Value
Allow people to contribute and add value to the platform.
Assumptions / Hypothesis / Questions / Unknowns
Setting guidelines for repository contributors

We'll use CONTRIBUTING.md as the location to store this information
We'll add a page to our user-guide to briefly detail this approach

Definition of done

[ ] readme has been updated
[ ] user docs have been updated
[ ] another team member has reviewed
[ ] tests are green
[ ] UR test OR added to continual research plan

Reference
How to write good user stories

@davidkelliott should the file be contributors.md or contributing.md (as suggested in the github documentation)? I've named it contributors,md but it can easily be changed.

Go with CONTRIBUTING.md - I'll update the story.

Most of the documentation I've written appears to relate to how people should code etc. rather than specifically relating to contributors. I need to look at it again and, maybe, rewrite it so it's just contributor related rather than aimed at general coders. Will be looking at this with David S today.
May be a major update later today.

Steve and I rewrote the document. I raised a new PR here: https://github.com/ministryofjustice/modernisation-platform/pull/4125

After many discussions a rewrite was suggested as the documentation I had written was too "everyday" user based not specifically related to contributors. This has now been approved in https://github.com/ministryofjustice/modernisation-platform/pull/4125 and merged into main. Complete!


Istio manual protocol selection configuration is getting ignored

Bug description
We are working on configuring to support HTTPS support for our product. The flow we have is, Browser -> Istio -> NGNIX. We ran into to issues with the “Automatic Protocol Selection” of Istio, i.e., selecting HTTP 2.0 (which is resulting in failure in the upstream at NGNIX).
To resolve this issue, we are attempting to configure HTTP 1.1 (for switching to, “Manual Protocol Selection”).
Istio documentation referred: https://istio.io/v1.4/docs/ops/configuration/traffic-management/protocol-selection/
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[X] Developer Infrastructure
Expected behavior

Protocol selected should change to HTTP 1.1, instead of HTTP 2.0 sent by the browser.

Steps to reproduce the bug

Configure manual protocol selection, to select HTTP as following:
Here’s the configuration done:
ports:
number: 443
name: http
protocol: HTTPS
tls:
mode: SIMPLE
privateKey: /etc/istio/ingressgateway-certs/tls.key
serverCertificate: /etc/istio/ingressgateway-certs/tls.crt

However, this configuration is getting ignored and protocol of HTTP 2.0 is still being selected
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
Istio 1.4.1
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

I tried to look at this, but I don't have my ingress set up for HTTPS.
What I did was install Istio, and the Httpbin sample.  Then from my laptop I did curl -v <myip>/anything --http2-prior-knowledge.  The httpbin pod's Envoy logged
[2020-10-01T14:01:03.037Z] "GET /anything HTTP/1.1" 200 - "-" 0 754 2 2 "<IP_ADDRESS>" "curl/7.64.1" "02a96643-35da-44c0-9566-719d7f9fde19" "<IP_ADDRESS>" "<IP_ADDRESS>:80" inbound|8000|http|httpbin.default.svc.cluster.local <IP_ADDRESS>:39502 <IP_ADDRESS>:80 <IP_ADDRESS>:0 outbound_.8000_._.httpbin.default.svc.cluster.local default

However, I am using Istio pre-1.8 (master).  I see you are using Istio 1.4.  Can someone try this with HTTPS and Istio 1.4?

You have configured the port of the Gateway. This is for inbound traffic. The outbound traffic is determined byt the port name on nginx

This appears to be user error, not a bug. I recommend taking a look at https://preliminary.istio.io/latest/docs/ops/configuration/traffic-management/tls-configuration/


Bitbucket similar issue feature

Preparing review...

PR Analysis

🎯 Main theme: Adding a feature to find similar issues in Bitbucket repositories.
📝 PR summary: This PR extends the functionality of the existing 'Find Similar Issue' feature to support Bitbucket repositories. It modifies the BitbucketProvider and GithubProvider classes to handle Bitbucket issues and adds new methods for issue handling. It also updates the PRSimilarIssue class to support Bitbucket issues.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 4, because the PR involves changes in multiple files and adds significant new functionality. Understanding the context and implications of these changes requires a good understanding of the existing codebase.
🔒 Security concerns: Yes, because the PR code handles bearer tokens in a potentially insecure way. The tokens are stored in headers, which could expose them to potential security risks.

PR Feedback

💡 General suggestions: The PR introduces a significant new feature and modifies multiple files. It would be beneficial to include tests to ensure the new functionality works as expected and does not break existing features. Also, consider handling exceptions more gracefully, providing more informative error messages to help with debugging.

 🤖 Code feedback:

relevant file: pr_agent/git_providers/bitbucket_provider.py
suggestion: Consider using a more secure method for handling bearer tokens. Storing tokens in headers can expose them to potential security risks. [important]
relevant line: '+        s.headers["Authorization"] = f"Bearer {bearer}"'

relevant file: pr_agent/git_providers/bitbucket_provider.py
suggestion: Avoid hardcoding URLs. Consider storing them in a configuration file or as constants at the top of your file. This would make your code easier to maintain and update. [medium]
relevant line: '+        url = f"https://api.bitbucket.org/2.0/repositories/{workspace_slug}/{repo_name}/issues/{original_issue_number}/comments"'

relevant file: pr_agent/git_providers/github_provider.py
suggestion: Avoid using bare 'except' statements. It's better to catch specific exceptions that you expect might be raised in the try block. This way, you won't accidentally catch an exception that wasn't caused by the code in the try block. [important]
relevant line: '+        except:'

relevant file: pr_agent/tools/pr_similar_issue.py
suggestion: Avoid using magic numbers. Consider defining a constant for '10' to make the code more readable and easier to maintain. [medium]
relevant line: '+                        if num_words_comment < 10 or not isinstance(comment_body, str):'

Preparing review...

Persistent review updated to latest commit https://github.com/akkiaws/akkipr/commit/fa41ff57369d064c895d74428a851e80e45baaaf

Questions to better understand the PR:

It seems like you have added a similar issue feature for both GitHub and Bitbucket. Can you confirm if this feature is now fully functional for both platforms?
The PR includes changes to the BitbucketProvider and GithubProvider classes. Are these changes only related to the similar issue feature, or do they also affect other functionalities of these classes?
Could you explain the logic behind the _parse_issue_url method in the BitbucketProvider class? It seems to be extracting the workspace_slug, repo_slug, and issue_number from the issue URL. How does this contribute to the overall functionality of the similar issue feature?

Please respond to the questions above in the following format:

/answer

...
...
...

reflect

Preparing questions...

Questions to better understand the PR:

I see that you have added a feature to find similar issues for both Github and Bitbucket. Does this feature work for both public and private repositories in both platforms?
In the BitbucketProvider class, you have added a new method _parse_issue_url. Does this method handle all possible Bitbucket issue URL formats?
Could you explain the logic behind the get_issue_numbers_from_list method in both the GithubProvider and BitbucketProvider classes? It seems to be converting a string to a list and then returning the first element. What is the expected format of the input string and why is only the first element returned?

Please respond to the questions above in the following format:

/answer

...
...
...


Updates chalk to 1.0.0.

Updates Chalk to latest version, 1.0.0. See the releasenotes for the changes.
This is the first major version, and the API can now be considered stable.
This commit and PR is auto-generated. Please merge with care. My apologies if it's undesirable.
Made with ♥ by Sindre, Joshua, and all our wonderful contributors.

Unless you feel like sending this to the major-v2 branch, I'll be doing this manually when I get to updating my dependencies. Thanks for the heads-up!


ForEach-Object -Parallel does not accept a scriptblock variable containing a $using

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
After upgrading to PS 7.2 from PS 7.1.5 I am not able to pass a scriptblock variable containing a $using anymore. This works fine in PS 7.1.5
Expected behavior
Using PS 7.1.5

PS>$data = 'hi'
PS>$script = [scriptblock]::Create('Write-Host $using:data')
PS>1..2 | ForEach-Object -Parallel $script
hi
hi

Actual behavior
Using PS 7.2.0

PS>$data = 'hi'
PS>$script = [scriptblock]::Create('Write-Host $using:data')
PS>1..2 | ForEach-Object -Parallel $script
InvalidOperation: A Using variable cannot be retrieved. A Using variable can be used only with Invoke-Command, Start-Job, or InlineScript in the script workflow. When it is used with Invoke-Command, the Using variable is valid only if the script block is invoked on a remote computer.
InvalidOperation: A Using variable cannot be retrieved. A Using variable can be used only with Invoke-Command, Start-Job, or InlineScript in the script workflow. When it is used with Invoke-Command, the Using variable is valid only if the script block is invoked on a remote computer.

Error details
Exception             :
    Type        : System.Management.Automation.RuntimeException
    ErrorRecord :
        Exception             :
            Type    : System.Management.Automation.ParentContainsErrorRecordException
            Message : A Using variable cannot be retrieved. A Using variable can be used only with Invoke-Command,
Start-Job, or InlineScript in the script workflow. When it is used with Invoke-Command, the Using variable is valid
only if the script block is invoked on a remote computer.
            HResult : -2146233087
        CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRecordException
        FullyQualifiedErrorId : UsingWithoutInvokeCommand
        InvocationInfo        :
            ScriptLineNumber : 1
            OffsetInLine     : 1
            HistoryId        : -1
            Line             : Write-Host $using:data
            PositionMessage  : At line:1 char:1
                               + Write-Host $using:data
                               + ~~~~~~~~~~~~~~~~~~~~~~
            CommandOrigin    : Internal
        ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
    TargetSite  :
        Name          : GetUsingValue
        DeclaringType : System.Management.Automation.VariableOps, System.Management.Automation, Version=<IP_ADDRESS>0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35
        MemberType    : Method
        Module        : System.Management.Automation.dll
    Message     : A Using variable cannot be retrieved. A Using variable can be used only with Invoke-Command,
Start-Job, or InlineScript in the script workflow. When it is used with Invoke-Command, the Using variable is valid
only if the script block is invoked on a remote computer.
    Data        : System.Collections.ListDictionaryInternal
    Source      : System.Management.Automation
    HResult     : -2146233087
    StackTrace  :
   at System.Management.Automation.VariableOps.GetUsingValue(MutableTuple tuple, String usingExpressionKey, Int32
index, ExecutionContext context)
   at System.Management.Automation.Interpreter.FuncCallInstruction`5.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
CategoryInfo          : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : UsingWithoutInvokeCommand
InvocationInfo        :
    ScriptLineNumber : 1
    OffsetInLine     : 1
    HistoryId        : -1
    Line             : Write-Host $using:data
    PositionMessage  : At line:1 char:1
                       + Write-Host $using:data
                       + ~~~~~~~~~~~~~~~~~~~~~~
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1

Environment data
Name                           Value
----                           -----
PSVersion                      7.2.0
PSEdition                      Core
GitCommitId                    7.2.0
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

Dup #12378


thumb slider freezes or touches at outside of round slider thumb control automatically

Hey,
Could you please give me a hint how to fix following problem:
when tap on the slider thump it freezes and doesn't move or seems like thumb control is not on the round thumb itself, because it slides to the side
thanks

Hey @alexgofman, can you give more details please, if you can upload a video it will be super, thanks a lot

Hey @alexgofman, I will close the ticket for now. If you get the chance to look into this issue further, you can always respond to reopen the ticket


systemd could not find the requested service "'carbon-cache'" on CentOS7

RUNNING HANDLER [nsg.graphite : restart carbon-cache] **************************
fatal: [IP]: FAILED! => {"changed": false, "failed": true, "msg": "systemd could not find the requested service \"'carbon-cache'\": "}

sudo service carbon-cache restart works, but the systemd fails

@030 with distribution and version?

[user@host1 ~]$ cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)


Requests to servers using letsencrypt's new root certificate fail verifiction

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.60.2
OS Version: macOS 11.5.2

Steps to Reproduce:
Add a request to a server using a new certificate to the plugin initialization
await axios.get('https://letsencrypt.org').catch(e => console.error(e))

GET https://letsencrypt.org
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5
Error: certificate has expired
	at TLSSocket.onConnectSecure (_tls_wrap.js:1497:34)
	at TLSSocket.emit (events.js:315:20)
	at TLSSocket._finishInit (_tls_wrap.js:932:8)
	at TLSWrap.onhandshakedone (_tls_wrap.js:706:12)
	at TLSWrap.callbackTrampoline (internal/async_hooks.js:131:14)
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5

This might be related
https://github.com/electron/electron/pull/31213

Likely the same issue: https://github.com/microsoft/vscode/issues/134245

For those who use GOT this may be a temporary solution, until the VSCode update comes out: https://github.com/sindresorhus/got/issues/1148

Same issue here with an extension that I have for private use. The request now fails indicating the certificate is expired, even though the certificate was renewed today and is valid for another 3 months. It started happening this afternoon after DST Root CA X3 expired.
The certificate shows as valid when browsing with Chrome, Firefox, Edge or on a smartphone.
The following error is thrown in the VS Code developer tools menu:
stack trace: Error: certificate has expired at TLSSocket.onConnectSecure (_tls_wrap.js:1497:34) at TLSSocket.emit (events.js:315:20) at TLSSocket.EventEmitter.emit (domain.js:467:12) at TLSSocket._finishInit (_tls_wrap.js:932:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)

This is caused by https://github.com/electron/electron/issues/31212 in Electron.
As a workaround, you can set the "preferred chain" option on the server side to prefer the ISRG root. This fixed the issue for me and I can confirm my VSCode/Atom extensions work as before after the change. See more details in this comment: https://github.com/electron/electron/issues/31212#issuecomment-931610222
There are also other workarounds listed in the original issue comments.

@deepak1556 is it planned to backport the release to the previous versions (before the upcoming September release) to prevent extensions from breaking on older VS Code versions? When is September release due?

The current fix is targeted for the September release which is due sometime next week. I will see if we can also make a recovery release for the current stable.

If anyone is using cert-manager on kubernetes, you can update your Issuer manifest to use the preferredChain to fix this issue server side.
https://cert-manager.io/docs/configuration/acme/#use-an-alternative-certificate-chain
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: letsencrypt
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    preferredChain: "ISRG Root X1"

You then need to reissue your certificates. This can be done with the plugin they provide or just delete the associated secret. You may then need to restart your ingress so that it picks up the new certificate.

Thanks @pbstriker38 that worked!

This issue reoccurred in version 1.62.1.


Ditch "do-not-reply" email address if in use

https://www.sendwithus.com/resources/guide
^ Fantastic write up on doing email as a startup.
http://hn.premii.com/#/comments/10420878
^ Discussion
No rush on this but lets move away from no-reply.

@sirtastic :

What do you want the address to be?
The emailer appears to be not working, and I can't find the credentials for our mail server. What are they? I need:
username
pw
port number
mail server's address (is it smtp.1and1.com)

@entrity

<EMAIL_ADDRESS>(created and forwarding to quinesquines AT gmail.com + my personal email)

User name - (The e-mail address that you set up and that you want to use.)
Password - (emailed to you)
Incoming Server - imap.1and1.com
Incoming port (SSL must be activated) - 993
Outgoing server (SMTP) - smtp.1and1.com
Outgoing port (TLS must be activated) - 587
Outgoing server requires authentication - Yes


compare machinedeployment vs machinepool

in preparation for an upcoming KaaS-Sync let's create a comparison about Pros and Cons of using machinepools vs. machinedeployments.

Current working document:
https://docs.google.com/document/d/1eK9zDB9ip7xUpqRKmLbemkPQPJoDdUulL0x3bRl1VOc/edit#

for now in CAPZ we switch back to machineDeployments (https://github.com/giantswarm/roadmap/issues/1897)
The general issue regarding machinePools vs. machineDeployments is tracked in https://github.com/giantswarm/giantswarm/issues/25395


Stop relying on the input .zap file in Matter test codegen.

To keep backwards compat with old Matter revisions, we require explicit includeAllClusters=true in the templates to get the new behavior.

Codecov Report

Merging #1035 (78f6547) into master (4e0ae8c) will decrease coverage by 0.01%.
The diff coverage is 72.72%.

@@            Coverage Diff             @@
##           master    #1035      +/-   ##
==========================================
- Coverage   67.04%   67.03%   -0.01%
==========================================
  Files         157      157
  Lines       17198    17202       +4
  Branches     3756     3760       +4
==========================================
+ Hits        11531    11532       +1
- Misses       5667     5670       +3

Impacted Files
Coverage Δ

.../app/zap-templates/common/ClusterTestGeneration.js
15.26% <33.33%> (-0.05%)
:arrow_down:

.../matter/app/zap-templates/common/ClustersHelper.js
87.20% <83.33%> (-0.15%)
:arrow_down:

...tes/common/simulated-clusters/SimulatedClusters.js
74.00% <100.00%> (ø)

Assuming these changes are just for backwards compatibility and not being used by any of our latest application templates.

Our latest application templates would be setting includeAllClusters=true.  The support for includeAllClusters=false (or unset) is for backwards compat.


Use Kubernetes annotations

New command-line argument --k8sEnrichment to enable the Kubernetes-Enrichment plugin
Interpreting Kubernetes annotations

sematext.com/logs-token, send pod logs to a specific Sematext Logs Token
sematext.com/logs-enabled, enable/disable pod logs.
sematext.com/logs-remove-fields, list of fields removed from pod logs

Update container.image.name with value from pod.spec.container.image.name
Bugfix: Docker engine in k8s reports sha256:ID as image name, while the Kubernetes API
provides the correct image name
Other changes:

Update kubernetes-events plugin to latest k8s API client
Update Redis logs pattern
Minor bug fixes:

Catch file not found error when loading pattern files,
Parser: Fix issue finding patterns for a source

Is everything backwards compatible?
Do we have a ticket for /docs for this?

Is everything backwards compatible?
Do we have a ticket for /docs for this?

ping @megastef

Is everything backwards compatible?
Yes. Docker labels and env vars will still work. Plus new k8s annotations.
Field value in container.image.name will change - but this is a bug fix as docker reports sha256:ID as image.name insted of the real image name that we take now from k8s API.
Do we have a ticket for /docs for this?
I've just created SC-5813 ticket.


Returning flat interactive surface

Hi all,
I am quite new to Makie.jl and its features and I was trying to get to know the interactive layoutables for, for example, a surface plot:

fig = Figure(resolution = (900,900))

lsgrid = labelslidergrid!(
    fig,
    ["Frequency", "Amplitude"],
    [1:0.1:3, 1:0.1:3];
    formats = [x -> "$(round(x, digits = 1))"],
    width = 350,
    tellheight = false)

fig[1,2] = lsgrid.layout

ax = Axis(fig[1, 1])

x = (-2:0.01:2).* π
y = x

sliderobservables = [s.value for s in lsgrid.sliders]

fun = lift(sliderobservables...) do slvalues...
    [slvalues[2]*sin.(slvalues[1]*xs)*cos.(slvalues[1]*ys) for xs in x, ys in y]
end

surface!(x,y,fun)

fig

However, the graph provided is completely flat, resembling a contour. I have tried adding zlims! unsuccessfully though. What is it that I am missing? Thanks in advance!

Replace Axis with LScene. Axis is 2D only, so you're seeing an orthographic projection of the surface from the top. LScene is the current way to include a normal Scene which by default uses a 3D projection, in a layout.

That's what I was looking for. Thanks!


Allow excluding exception messages from ExceptionTelemetry

It would be nice to have the ability to exclude exception messages from the telemetry, as the messages could contain PII.

Thanks for feedback! This feature is partially blocked on this one: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/498 Once the exception model will be exposed - you'd be able to override all fields in telemetry processor.
We will schedule those issues together


Allow negative contrast values in the editor theme settings

master version of #48540.
When using a negative contrast value, the base color will be lightened to create the derivative colors instead of being darkened.
This can lead to better-looking themes, especially for light themes.
I also fixed the default theme contrast value not matching the new default.
See https://github.com/godotengine/godot/issues/48477#issuecomment-834343944.
Preview
Light theme

Custom theme based on Light theme with base color set to #ddd and contrast to -0.08

Thanks!

PS: It would be interesting to see whether we should change the Light theme preset to use a negative contrast. Any opinions?

Might be worth a try, but needs feedback from Light theme users (I tend to stick with the default so Dark theme).


utilise crypto compare

@ashachaf I've messaged you a new secret key we need to add.

@ashachaf has this been added or access granted to us devs for making this happen? Or still waiting on access to the Bancor key?

@ashachaf still in waiting, did we have a pre-existing key?

shared the key privately.


Update to OpenCV 3 maybe?

Basically i get the following error:
`conversion.cpp: In member function ‘cv::Mat NDArrayConverter::toMat(const PyObject*)’:
conversion.cpp:202:11: error: ‘class cv::Mat’ has no member named ‘refcount’
m.refcount = refcountFromPyObject(o);
^
conversion.cpp: In member function ‘PyObject* NDArrayConverter::toNDArray(const cv::Mat&)’:
conversion.cpp:223:12: error: ‘class cv::Mat’ has no member named ‘refcount’
if(!p->refcount || p->allocator != &g_numpyAllocator)
^
conversion.cpp:230:36: error: ‘class cv::Mat’ has no member named ‘refcount’
return pyObjectFromRefcount(p->refcount);
`
Which is caused for the absence of refcount which needs an update to OpenCV 3.0

Hey, thanks for the report! I do not have too much time at hand to work on the upgrade, but will try to hack on it when I do. Of course I will appreciate ideas (or patches!).


Use the Submodules Alternative tool

Description
With the Submodules Alternative tool, anyone can easily clone the submodules without having to install Git or run any extra commands.
PanqKart already uses Submodules Alternative and it has been working very well. The tool is still WIP and might have a few bugs, but with the proper configuration, it should work completely fine.
Let me know your thoughts. Thanks! 🙂

Obsolete due to https://github.com/minetest-mods/castle/commit/a35e564b81739c02bc5e418b5a14940bd9739638.


Add started timestamp to organization form

Scope of changes
This adds a "started" timestamp to the organization form. The point of this is to be able to determine from the backend if the user has started filling out a form (in other words, they have saved it at least once from the UI). Once use case of this is the Attention endpoint which can check this field to determine if it should return the "start your registration" message.
SC-7760
Type of change

[ ] bug fix
[x] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
When a user saves an organization form, the Attention endpoint will no longer return the "start registration" message.
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[x]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] The assumption is that a user has not started the form until they hit "save" and the form successfully goes to the backend. Is this the right semantic?
[ ] When we save the form in the backend, what should we do if the form is empty? Currently we interpret this as a "delete" request and the started timestamp does not get populated.

Codecov Report

Merging #681 (0dd992c) into main (dcdc91a) will decrease coverage by 7.31%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #681      +/-   ##
==========================================
- Coverage   45.40%   38.08%   -7.32%
==========================================
  Files         575      155     -420
  Lines       17090     2434   -14656
  Branches     1245      618     -627
==========================================
- Hits         7759      927    -6832
+ Misses       8151     1330    -6821
+ Partials     1180      177    -1003

Impacted Files
Coverage Δ

...ules/dashboard/certificate/lib/validationSchema.ts

...mponents/MissingRequire/MissingRequire.stories.tsx

web/gds-user-ui/src/utils/axios.ts

...r-ui/src/components/CollaboratorsSection/index.tsx

...ts/CertificateReview/TrisaImplementationReview.tsx

web/gds-user-ui/src/application/config/index.ts

web/gds-user-ui/src/hoc/withReduxContext.tsx

...src/components/ContactForm/ContactForm.stories.tsx

web/gds-user-ui/src/locales/zh/messages.js

...github.com/trisacrypto/directory/pkg/utils/gzip.go

... and 410 more

Continue to review full report at Codecov.

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


Refactor: Indexer Performance Improvements

Refactors the Indexer backfilling process for faster/bulk database insertions and parallel log fetching. No new features are added, this is purely a refactor and the logs not yet added to the database still need to be implemented.
I believe this completes #8

Sweet could you merge? I don't have permissions


Support HHVM. See if CURLOPT_PROTOCOLS is defined before using it and other HHVM errors.

This constant is not available on hhvm at this time. It causes test fails in other projects. I am aware that Guzzle allows failures for HHVM at this time but this check fixes it.
I am not sure if this could be a security issue. If the constant is not available, the feature is not available in curl and it wouldn't make any difference.
Lastly, FYI: HHVM has added this constant in an upcoming release as seen here: https://github.com/facebook/hhvm/blob/20287e468c5727578af55690b48099f1c09d55fd/NEWS#L87. It is not in any release yet AFAICT.

The error fixed in https://github.com/guzzle/guzzle/commit/690f7af914953830bcc8da997b2e4089c97deac9 is best explained with this eval: http://3v4l.org/1LTC3. I am not sure if this counts as a bug in HHVM, or just a discrepancy. I fixed the bug in the commit though.

@mtdowling Any suggestions or help here would be greatly appreciated. Thanks!

You can probably remove composer self-update from the travis file.

The file permissions on CurlFactory.php shouldn't have changed.

@GrahamCampbell, I would be happy to remove composer self-update. I was just wondering if it is relevant here and does it make sense to be a separate PR?
I will fix the file permissions. That was a mistake.

IMO, you should allow failures on HHVM again until the Pool tests are fixed (unless you plan to fix them here before the merge, but I would like to see a version where the CURLOPT_PROTOCOLS issue is fixed)

This PR seems more or less ready to be merged, but I think HHVM should be allowed to fail until all of the tests pass. That could be a separate set of PRs though. I'd like this PR to be in the next Guzzle release.

Sorry for the delay on this. I had a busy weekend. I have pushed changes to allow failures on HHVM. I am looking forward to see this get in.

Merged. Thanks! We can do more HHVM work in other PRs.


Bottom Sheet recomposes entire content If its slightly dragged without fully dismissing

In the Adaptive Bottom Sheet specifically the iOS implementation, placing any content inside the sheet causes the content to recompose if I slightly drag the sheet downwards and let it snap back to its original height without dismissing it. What I did exactly was I used the Adaptive Bottom Sheet in my iOS module and placed a WebView inside it [also from calf]. dragging the sheet and letting it go back to its original height recomposes the webview inside which causes my webview to reload.
Here's a small code snippet:
AdaptiveBottomSheet(
                    onDismissRequest = {  },
                    adaptiveSheetState =
                        rememberAdaptiveSheetState(),
                ) {
                    WebView(
                        state = state,
                    )
                }

update: this issue arises due to jetbrains compose version 1.6.0. older versions do not have this bug. any plans to address the issue?

Hi
Thanks for reporting this issue.
I will check it out.

Can you try with the latest version 0.5.3, it should be fixed now.


output image in pdf file ?

is there a way to output (convert) an image in PDF File using this library (  it's supported in Imagick  ) ?

Hello! Thanks for interest in Glide. Unfortunately this isn't supported by Glide, as it falls pretty far outside of the scope of this project. I'd recommend using Imagick, or some other tool more geared to PDF generation. Sorry I cannot be more helpful.

thank you ,
i am using Imagick now and it work's :+1:


A page which is not an OCaml doc gets autoconverted to the new Reason doc stylesheet

When I go to the URL: https://www.tjson.org/spec/, the extension automatically swaps the stylesheet and detects the page to be an OCaml doc page.
This is a false positive.

Thanks for the report - this passes the check here because this page uses the same rel syntax with Chapter and Contents. I think Chapter and Contents can be removed - but I'll check with my test pages to be sure.
https://github.com/rickyvetter/reason-tools/blob/master/src/AutoConversionPrompt.js#L31

Fixed in d1df6e8


"Delete" of bogus commits looks like a successful no-op rather than an error

Repro is with Zed commit 4600f3e. I bumped into it while reviewing the latest Zed lake API doc examples.
Starting with an empty lake, I create a pool and load some data.

Having first bumped into this in the API context, I now realize that using the actual zed command sees much the same;
$ zed -use inventory delete 27aaaaaaaaaaaaaaaaaaaaaaaaa
292bGDsBPGoeDvgaI0gfS54KcXr delete committed

Verified in Zed commit 5b12013.
Now instead of the no-op and additional entry in the zed log, our attempts to delete bogus commits result in HTTP 404 errors.
$ zed -version
Version: v1.2.0-69-g5b12013f

$ curl http://localhost:9867/version
{"version":"v1.2.0-69-g5b12013f"}

"Data deletion" request:
$ curl -i -X POST \
      -H 'Accept: application/json' \
      -H 'Content-Type: application/json' \
      -d '{"object_ids": ["27aaaaaaaaaaaaaaaaaaaaaaaaa", "27bbbbbbbbbbbbbbbbbbbbbbbbb"]}' \
      http://localhost:9867/pool/inventory/branch/main/delete

Response:
HTTP/1.1 404 Not Found
Content-Type: application/json
Vary: Origin
X-Request-Id: 2Fgnf0Ql9lW9KlsqcPIGkqqA7jD
Date: Tue, 04 Oct 2022 22:31:33 GMT
Content-Length: 109

{"type":"Error","kind":"item does not exist","error":"27aaaaaaaaaaaaaaaaaaaaaaaaa: commit object not found"}

Zed log:
$ zed log
commit 2FgndcMIvfdMS24Y0yj5oKxmlID (HEAD -> main)
Author:
Date:   2022-10-04T22:31:22Z

    loaded 1 data object

    2FgndaBl6ds5II7QZpB5h1ewpuJ 3 records in 108 data bytes

The same using the zed command:
$ zed -use inventory delete 27aaaaaaaaaaaaaaaaaaaaaaaaa
status code 404: 27aaaaaaaaaaaaaaaaaaaaaaaaa: commit object not found

Thanks @nwt!


Lost scheduler/Broker

When the slave machine running the scheduler is taken out of the cluster or stops responding. The scheduler is not restarted by marathon and it hangs indefinitely.  Attaching image. Destroy /scale up down does not work as well.

When the slave machine running broker is taken out of the cluster or stops responding. I see Broker Lost message but it's not scheduled in another machine or stopped. scheduler still shows broker is active

Regarding point 2. The designed behavior is in case of broker failure (which actually is modelled) try to reuse same slave node during configurable period of time (--stickyness-period option). After that time is passed Scheduler would restart broker on any matched node. You can find more information here: https://github.com/mesos/kafka/#failed-broker-recovery

Regarding point 1. Described case is 99% not related to kafka mesos, but is related to Marathon / app configuration. Could you please post your app configuration here?

One more comment about point 1 - I was just able to run a scheduler on a slave and then tried 2 options:

shutdown that slave machine completely: Mesos/Marathon noticed the slave went down, healthchecks weren't passing and after ~3-5 minutes tasks/instances count went to 0/1. After I spinned up that machine again Marathon was able to recover (reschedule) the task in another 3-5 minutes.

turn off networking on the slave machine (via ifconfig eth1 down): again Mesos/Marathon noticed the slave went down, the healthchecks weren't passing, but the scheduler was still running on that slave. After I enabled the networking back Marathon was able to recover the scheduler (not sure though did it kill the previous one and started a new instance or recovered the old one).

Can you please post the json you feed to marathon so we can try/figure out more things? Thanks!

Sorry looks like I missed all these updates. I went ahead and restart all masters and all marathon and everything came back and scheduler started appearing without me adding scheduler again. Looks to me as marathon issue


[Bug]: Clicking outside on the canvas/ Query pane the bottom panel must close

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When the user clicks on the canvas or on the query pane it is observed that panel does not close
Steps To Reproduce

Navigate to API pane
Add the API with error
Run the API
Ensure he bottom panel is open
Click outside the panel

Observe that the panel does not close
Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
DP

@prapullac are you referring to the debugger pane? could you elaborate why the pane should close on canvas clicks? cc: @parth-appsmith


Windows - AttributeError: 'CustomVisionPredictionClient' object has no attribute 'classify_image'

fixed after jupyter notebook restart in 1.0.0


Improve implementation to convert stargz TOC into RAFS fs

Improve implementation to convert stargz TOC into RAFS fs.

LGTM.


Topics should be able to be created just by clicking in a "new tab" or pressing a +

Currently to create a topic a user has to click the "+" on the right of the workspace/topic view then select "Create a new Topic" there is also an option to "open an existing topic" that does not do anything. (While I think it was intended to find topics in other workspaces that you might want to associate with the current workspace, I don't think this is an implementation of that use case that makes sense).
So:

Remove the options for topics from the right "+" (for now leave the resource options, but I will be creating a separate ticket to have them done differently as well.
The "open an existing topic" option will just go away for now.
If you put your mouse anywhere in the area to the right of existing tabs a "phantom" tab should appear under the mouse and if you click a topic will be created and you will be editing the topic name by creating the name of the tab.
Also there should be "+" option just to the right of the last existing topic tab and clicking on it will have the same effect as #3 above

This is complete


PackStreamWriter cannot write DateTime's

When trying to save an object with a DateTime in it, I receive the following error
Neo4j.Driver.V1.ProtocolException : Cannot understand value with type System.DateTime

Hi @rdehuyss,
This driver only supports Cypher types.
Therefore this error is a expected behaviour. In order to save Date type, you probably want to convert it to a supported Cypher type before passing it to the driver.
Zhen

Temporal type support added in this driver since https://github.com/neo4j/neo4j-dotnet-driver/pull/281
Please follow on news about Neo4j 3.4 releases and 1.6 driver releases where DateTime parameter type support would become available in Cypher.


Run isort to reorder imports

As generated by isort .
@kuberti, @guberti this is step one of switching to Black style.

isort is a tool that reorders your import statements in the Python-preferred way. Pylint will check if imports are in the wrong order, so this is putting them in the right order.
See https://github.com/PyCQA/isort for details.

Gotcha, understood. What's the reason for this though? Just overall neatness?

Yep - neatness and removal of unused imports, mainly. Otherwise as code changes you can end up with a lot of stale imports.


A question in state_distribution.cc

so in this for loop
https://github.com/deepmind/open_spiel/blob/c1fbaca644aaf6c7dd82eea4f62cccd9f6469a5d/open_spiel/algorithms/state_distribution.cc#L226
Is there a particular reason that it is written as a for loop? Can't it be just checking whether my_infostate_str is in infostate_action_map, and if it is then directly extract the corresponding action from the map and add the new (state, prob) to the queue?

Hi @rezunli96,
Hmm.. I don't see why you would have to iterate over your actions unless this code was trying to support the case of imperfect recall where the player forgets their own past actions. I believe we might have used it in that settings, but even if we did, it's not well-documented because the header says it assumes perfect recall: https://github.com/deepmind/open_spiel/blob/c1fbaca644aaf6c7dd82eea4f62cccd9f6469a5d/open_spiel/algorithms/state_distribution.h#L31
Tagging @finbarrtimbers: do we have an explanation for this?


Feature/newstarter

Test the CI

Seems that CI steps are passing - I would suggest we merge this to main, and then all thats left to do is somehow test the CI flow introduced by https://github.com/zenml-io/zenml/pull/2157


Future data?

Hi,
do you think it's possible to fetch future data from Vattenfall and display it somehow in Grafana?

We do have a whole day's worth of data and you an set a time range in Grafana to be in the future. From a display perspective I suppose it's possible. But future data doesn't really map to what Prometheus is doing, that's always past-up-to-now. We'd have to fake some kind of time series as being in the past and dealing with the scrape interval too.
There is the Grafana JSON plugin https://grafana.com/grafana/plugins/simpod-json-datasource/ which might be usable for this purpose instead. We could add a separate endpoint to this exporter exposing future data in this format and hope that's graphable.

FYI, I've made another tool to export the data into InfluxDB and show it as future forecast  - https://github.com/rvoitenko/vattenfall-to-influxdb

I ended up adding this in 3fd00ecbb143264400f373fbbc9a2b08cb11f696. Now you can graph it in Grafana directly without needing to ingest the data somewhere else too.

it's a great feature!
However, I have a small issue with it, when I run the command with specific region, for example:
vattenfall  -output.http=":9000" -region SN3
It does not honor region parameter and display all regions(SN1-SN3) informations at /forecast.
It make it little bit difficult to make graph in Grafana only for single region, at least I don't know how.
Do you know what can be the issue?

Oh yeah, sorry. It takes it as a URL parameter, you can set a Parameter of region and then SN3 and it'll limit. But that's silly actually, I should be reusing the region that folks are already passing in. Let me go in and fix that.

Here we go:<PHONE_NUMBER>f0b88afb063df7dd1de36d1abda3aa. v0.3.2 is getting built right now.

works like a charm, thanks!


[Looking for feedback] Make m_params private

I'd suggest that we make m_params private, as it is very easy to use it wrongly.
There were quite a few cases already where someone used the m_params directly (and in most cases introducing bugs while doing so).
In this PR I've built a simple trick to emulate privacy in GLSL.
If you actually prefer accessing m_params directly, instead of using the serialize/deserialize functions, we could alternatively just remove the serialization system. (I'd like your thoughts on this!)
Although I personally think writing trapezoid.m_widthB is better than cutout.m_params[1] for multiple reasons.
(In the second commit I've implemented a simple boundingBox function for the cutout that is needed for MarchingCubes.cpp)
This PR intentionally doesn't compile yet, due to some uses of m_params that now fail to compile due to it being private.
What are your thoughts?

Sounds like a good idea to me.


Classification Banners

Ticket #4086  was closed prematurely. The suggestion that 2.6 will solve the problem is inaccurate as 2.6.0 is currently not stable, and a stable release is required for the environment it is going into. This will need to be corrected in the latest stable (2.5.9 currently). Classification banners must work on all UI pages for specific environments, which it currently does not.

The issue is fixed in 2.6.0, at some point a 2.6 build will be the next stable. There are no plans to back port banner changes to 2.5.x.


Using Jil with ASP.NET Core 6

Has anyone had any success in using Jil as the primary JSON formatter in ASP.NET Core 6? There are plenty of examples of how to switch between JSON.NET and System.Text, but I haven't seen anything about how to swap in another library.
I am working on an API where the requests can get pretty large - 20MB, and JSON.NET is currently taking so long to deserialise those requests that the load balancer is timing out the connection; and we're looking to handle larger and larger payloads as we go on. From what I've been able to benchmark, Jil looks like it should be able to process my data in half the time that JSON.NET does, and with fewer demands on the resources of my containers.

I have finished a simple Jil Formatters for Asp.net Core; feel free to try it: https://github.com/PicoHex/Zaaby/blob/master/src/Server/Formatters/Zaaby.AspNetCore.Formatters.Jil/README.md


Add support for BranchListOptions

Add support for BranchListOptions for RepositoriesService.ListBranches.
ref. https://developer.github.com/v3/repos/branches/#list-branches

This branch failed to pass CI because of Go 1.13.
Could anyone fix the CI settings?

Thanks for your review!

Thank you, @gauntface!
Merging.


West build command execution takes more time or fails sometimes

Describe the bug
When executing the west build command as shown in the attached image, the build process stops at random command.
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using?  -  Windows
What have you tried to diagnose or workaround this issue? - None
Is this a regression? If yes, have you been able to "git bisect" it to a Zephyr 3.1.0 SDK 0.14.2
specific commit?
...

To Reproduce
Steps to reproduce the behavior:

Use west build -b nucleo_f429zi -p
See error

Expected behavior
After executing the build command the execution should not pause for long time and should not hang.
Impact
It is annoying to wait for long time after code is done and we are building the code.
Logs and console output
Refer locations where the build execution took a long pause or hanged. But the location is random.

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows) - Windows
Toolchain (e.g Zephyr SDK, ...) - Zephyr 3.1.0 SDK 0.14.2
Commit SHA or Version used Zephyr 3.1.0 SDK 0.14.2

Just one update:
We have same observation for SDK 0.15.2
Additional context
Add any other context that could be relevant to your issue, such as pin setting,
target configuration, ...

@mbolivar-nordic  FYI

@SadanandPenore-eaton Can you please revise the title?

I think same issue is observed in 3.2 as well.. One thing to note that when we used to have arm embedded tool chain, it was not seen but as soon as we switched to zephyr sdk, we started seeing this issue randomly( not always).. some time it just hangs for 4-5 minutes without generating any new logs and we need to terminate the current process and re-start.
Is there a possibility that some antivirus/firewall could be playing the role? Have you or zephyr community came across any such observation where Corporate policy was restricting the zephyr tools and executables and some exceptions were required to mitigate. As we don't know, in which area such exception could be applied, therefore we are trying to gather as much information as possible.

@prayassamriya and me are in same team. Also refer the additional comments from prayas.
The issue is also reproduced on 3.2.
I had already mentioned it for SDK 0.15.2 which uses 3.2.

It would be good to know if any recent release is working for you. If not, then it does indeed strongly point to an environment issue on your end since nobody else has reported this issue. Antivirus is a good guess, but it's impossible to say from the outside.

Reassigning to @nordicjm since this seems like a build system issue.

@SadanandPenore-eaton @prayassamriya can you confirm this is still an issue for you?

Run the configure commands using cmake instead of west and include the --trace argument to see where it is going wrong. When it goes wrong, what process executable is "stuck", what is the CPU utilisation of that process?

Is there a possibility that some antivirus/firewall could be playing the role?

It could be an antivirus, what system is being used on these systems?

we don't know how to run it without west. for example what will be equivalent of "west build  -b nucleo_f429zi -p"

cd <app_folder>
mkdir build
cd build
cmake -GNinja -DBOARD=nucleo_f429zi --trace ..

@prayassamriya do you have any feedback on this?

I tried this ninja command. It did not stuck anywhere.
Finished the whole process in one minute.
For the same folder structure west is taking 5 and half minutes to complete. ( If it did not stuck anywhere )

Sounds like a west issue, assigning to @mbolivar-nordic

In the screenshots showing a hung process, west build is just waiting for the cmake subprocess to finish. It isn't doing anything else. So none of this makes any sense to me, unfortunately.
zcmake.py lines 62-64:
    log.dbg('Running CMake:', quote_sh_list(cmd), level=log.VERBOSE_NORMAL)
    p = subprocess.Popen(cmd, **kwargs)
    out, _ = p.communicate()

you can see this if you run in verbose mode:
$ west -vvv build --cmake-only samples/hello_world
[...]
Running CMake: /usr/bin/cmake -DWEST_PYTHON=/home/mbolivar/.virtualenvs/west-dev/bin/python -B/home/mbolivar/zp/zephyr/build -GNinja -DBOARD=nrf52dk_nrf52832 -S/home/mbolivar/zp/zephyr/samples/hello_world
Loading Zephyr default modules (Zephyr base).
-- Application: /home/mbolivar/zp/zephyr/samples/hello_world
[...]

It seems very unlikely that the standard library's subprocess module is not working as documented, so I still have trouble believing this is a problem in west build.
It seems far more likely to me to be a problem in either the environment calling west build, or some specific command run by cmake in the build system.
@SadanandPenore-eaton if you want me to try to diagnose further, I'm going to need more detailed information in the form of west -vvv build ... -- --trace-expand output for a situation where the process hangs. For example, if you can get it to happen with the hello_world sample on the qemu_cortex_m3 board, then the complete output from this command would be useful:
$ west -vvv build -b qemu_cortex_m3 samples/hello_world/ -- --trace-expand

Please paste the complete output somewhere like a github gist:

use copy/paste; do not post a picture of a screenshot
paste the command's entire output, not just the parts that seem most relevant to you

Thanks!

Closing due to inactivity, let us know if this is still an issue.

An update on this:
The issue came out to be .cache folder which gets created inside zephyr folder for toolchain testing capability. We had the patch for zephyr. To apply the patch, we needed to revert the zephyr repo using git clean command and as a consequence it was removing the .cache folder as well. so every time we apply the patch, it was taking significant time and just hang for 4-5 minutes to generate zephyr/.cache data


playground precommit move to selfhosted and update

In #32740 I saw that the playground precommit is failing with the canceled message. This is probably due to OOM but the runner is github hosted so Im unable to confirm. I tested it on a self hosted runnner and it works
This PR will:

Move the job to self hosted runner
Update the workflow file
Allow to invoke the job using comments

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Thanks for noticing and fixing this! I likely would've banged my head on this for a while


Update instruction in the README

I was thrown off by instructions from an earlier version that talked about /account/settings/social/associate/complete/github/, and the current wording didn't make clear to me that this has changed. Hopefully this does to others :)
Also add a line about GITHUB_ORGANIZATION

Codecov Report

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

@@         Coverage Diff          @@
##           master   #17   +/-   ##
====================================
  Coverage      49%   49%
====================================
  Files           9     9
  Lines         200   200
====================================
  Hits           98    98
  Misses        102   102

Continue to review full report at Codecov.

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

I'm not sure how this is really any different. Appears to me its just adding "for example", and makes the formatting less structured around it.

It changes the wording from "use the field as the sentry setting" to "use the sentry setting as the field value", which makes quite a lot of difference :)


Use of Wildcards in Search Criteria

Description
Allow the use of wildcards when defining search criteria to encompass multiple devices.
Use Case
For getModel, instead of typing getModel === 'iPhone X' || getModel === 'iPhone XR' || getModel === 'iPhone XS' || getModel === 'iPhone XS Max' can it be something like getModel === 'iPhone X'* where the asterisk (*) is the wildcard?

Hi and thank you for the proposal, but this really doesn't fall into this library scope, which is extracting data from the device and handing it back to you.
Your use case could be implemented using a regular expression in your app:
if (device.getModel().match(/iPhone X.*/) {
   // special treatment
}


Improve grammar (KR), update as upstream

Improve grammar several files in ko translations
Update as upstream
Fix some typos in ko translations

Thanks!


module 'signal' has no attribute 'SIGALRM'

Hey guys, Me again, I was finally able to get pycurl working by uninstalling and reinstalling it so thanks for that! I was able to log in and connect to Overdrive/Libby however I was experiencing issues similar to those described in #23
I downloaded the new 1.04 release and now I'm experiencing a new error and seem unable to run the program.
I have copied/pasted what happens down below, If you guys have any advice please let me know, I'm watching some tutorials for Python on YouTube but I still don't understand much of it lol.
PS C:\Users\Owner\Downloads\libbyfetch-1.0.4> python3 libbyfetch.py
Initializing webdriver.
An error occurred for an unknown cause.
Exception type:  <class 'AttributeError'>
Message: module 'signal' has no attribute 'SIGALRM'
Traceback (most recent call last):
File "C:\Users\Owner\Downloads\libbyfetch-1.0.4\libbyfetch.py", line 489, in startup
return initialize_driver()
File "C:\Users\Owner\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.13_qbz5n2kfra8p0\LocalCache\local-packages\Python313\site-packages\timeout_decorator\timeout_decorator.py", line 75, in new_function
old = signal.signal(signal.SIGALRM, handler)
^^^^^^^^^^^^^^
AttributeError: module 'signal' has no attribute 'SIGALRM'. Did you mean: 'SIGABRT'?
PS C:\Users\Owner\Downloads\libbyfetch-1.0.4>

@OGQueenie Glad you got pycurl working!  I think the error you are now observing was reported in issue #21.  There is a fix in the current version of libbyfetch.py found in the main branch of the repository.  Please download just that single source file from the main branch and see if that works for you.   Let me know if the error persists.

Thank you! That seems to have fixed this issue but now I am receiving the same "Page says: An error was encountered while opening this audiobook." that the other users have reported when trying to download a book, Hopefully you can get that part sorted soon