Issue #517: Test automation script for Component Role

Fixes #517
Description of the Solution
Validation script to test component role functionality
Suggested Reviewers
@j0hnL @lwilson

@all-contributors please add @VishnupriyaKrish for test, code


[Bug]: Caret Screenshot

Version
1.43.0
Steps to reproduce

Java 11 Maven project in IntelliJ IDEA 2024.1
Clone my repo: https://github.com/erdemgurell/Playwright_LearningProject.git
Go to src/test/java/LambdaTest/day4/Screenshots.java and run the file.

Expected behavior
Take a screenshot of the input element with the caret hidden and save it to a fil
Actual behavior
It gives this error:
com.microsoft.playwright.PlaywrightException: Error
message='caret: expected one of (hide|initial)
name='Error
stack='Error: caret: expected one of (hide|initial)
Additional context
I think it's about enums in ScreenshotCaret class
Environment

Operating System: [Windows 10]
Browser: [Chromium]
IDE: [IntelliJ IDEA 2024.1 (Community Edition)]
Java Version: [Java 11]
Playwright Version: [1.43.0]
Maven Version: [4.0.0]

I was not able to reproduce it. Can you run it from terminal and share your command if it fails there?

I don't know how to run it from terminal. What should I do?

Configure it to work with mvn test? I just want to rule out any potential issues related to us running it in different environments.

I figured out and here are the results:

Can you update you repository and provide instructions how to reproduce it? We can't debug screenshots.

I updated the repository and commented every step. Here are the reproduce steps:

Navigate to "https://www.lambdatest.com/selenium-playground/simple-form-demo"
Create a new instance of ScreenshotOptions
Create a Locator for the Single Input Field (my selector: "input#user-message")
Then used method: input.scrollIntoViewIfNeeded();
Click the input element
Take a screenshot of the input element with the caret hidden and save it to a file
Take a screenshot of the input element with the caret in its initial state and save it to a file

I was also not able to reproduce - my rough guess is that it might be related to the Java you are using. The ScreenshotCaret.HIDE enum value seems to not being able to get passed over correctly. Could you try on OpenJDK 21? Ideally we recommend Zulu.

Closing as part of the triage process since it seemed stale. Please create a new issue with a detailed reproducible or feature request if you still face issues.


Dynamic Height Width

How do we pass the Height width dynamically, currently it is statically defined ?

Hi, you can change the height and width with chart.width() and chart.height()
code pen example : https://codepen.io/mcaule/pen/oopYXw


Machine mac-4 lost connection from the external iPhone device.

Machine mac-4 lost connection from the external iPhone device.

The external connection has been restored by rebooting machine mac-4.


k8s version update for 2022 November patch release

for issues: https://github.com/rancher/rancher/issues/39369 and https://github.com/rancher/rancher/issues/39370

Actually, the failure is due to a couple of CVEs. It looks like all that's needed is to rebuild hyperkube-base image and start referencing it. See more info here - https://github.com/rancher/rancher/issues/39509.


Does not work with SDL

SDL does something strange where it replaces main() with its own main. I am not exactly sure how the catch define CATCH_CONFIG_MAIN works, but it messes with SDL's ability to capture keyboard input, I guess because it prevents SDL from taking control of main.

Defining my own main solved the issue.


Disqus export is invalid when posts are not published

I just noticed that disqus comment export xml file is invalid when the export is done by not selecting "publish all" check box.
This is because the xml needs the absolute url of the post, which is only available when the post is published.
So, there are two options to solve the problem:

make publishing compulsory if disqus export is selected
publish and then unpublish the post after the export has been done.

Which is better?

I think # 1 is easiest, if discuss export is selected we can auto select that and disable unselecting it


Add not_in generation constraint

We can exclude some expressions from the output by passing the not_in keyword parameter to the model call. This can be implemented with OpenAI by using the logit_bias argument.
We will need to find a smart way to make sure the constraint has not been violated while limiting the number of tokens consumed.

Superseded by #156


update luakit

Motivation for this change
Luakit is out of date. This PR fixes that
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hello, @enderger! Many thanks for your contribution!
Just a small correction: rewrite the commit in the form luakit: 2.1 -> 2.2.1.
(If I'm not wrong, you can use a mere git commit --amend to edit the commit message, and then git push -fvu it.)

The message should now be fixed, as a side note I am not the origional maintainer of the package, just a user who saw an out of date package. I may push some updates since they are inactive, but a new maintainer may be needed. I don't know how that works, just wanted to let you guys know.

OK. I will update it locally, then.


Scrollr inside a div

Hi there, i wonder if it is possible to use Scrollr just for a div and not the body, something like $('myElement').skrollr.init();
thanks.

+1 For this feature request.

Did anyone try the changes in IE 8 and more important on mobile? And "it seems to work" is not what I mean. For example APIs like setScrollTop should also work.

Why not just mark this feature in docs as experimental or IE9+ or even breaksSetScrollTop :) (or something similar)?

+1 for this feature,
since in some platforms like Microsoft SharePoint, disables the default scrolling behavior, and append the whole page content in a scrollable div.


merge (#1)

Update log from master

Update conversion from master

Update conversion from master

Update fiber from master

Add Boost Process to master

Update maintainer list.

Update container from master

Update container from master

Update python from master

Update quickbook from master

Update geometry from master

Update fiber from master

Update fiber from master

Update rational from master

Update context from master

Update build from master

Update align from master

Update align from master

Update align from master

Update fiber from master

Update unordered from master

Remove links to deleted tools modules

Singular 'library' when appropriate

Mustache is really terrible for this kind of thing.

Try to fix the python links in the getting started guide

Update process from master

Update context from master

Update context from master

Update context from master

Update build from master

Update filesystem from master

Update filesystem from master

Update utility from master

Update concept_check from master

Update context from master

Update fiber from master

Update fiber from master

Update build from master

Update geometry from master

Update context from master

Update intrusive from master

Update hana from master

Update geometry from master

Update fiber from master

Update fiber from master

Update move from master

Update multi_index from master

Update unordered from master

Added Stacktrace library

Update 4 submodules from master

Update atomic, dll, quickbook, signals2.

Bump to 1.65.0.

Update config from master

Update context from master

Update typeof from master

Update core, preprocessor from master

Update iterator from master

Update parameter from master

Update date_time, interval from master

Update smart_ptr from master

Update context from master

Update container, intrusive, move from master

Update quickbook from master

Update convert from master

Update uuid from master

Update core, smart_ptr from master

Update smart_ptr from master

Update tokenizer from master

Update smart_ptr from master

Update config from master

Update serialization from master

Update align from master

Update align from master

Update serialization from master

Update compute from master

Update exception from master

Added stacktrace folder

Remove changes to maintainers.txt

Update quickbook from master

Update quickbook from master

Update align from master

Update qvm from master

Update maintainer list.

Update stacktrace from master

Update quickbook from master

Update predef from master

Update config from master

Update metaparse from master

Update align, core from master

Don't use non-existent test projects.

Update context, coroutine2, fiber from master

Update core from master

Update context from master

Update config from master

Remove TR1 submodule.

Update utility from master

Update atomic from master

Update utility from master

Update core, smart_ptr from master

Update circular_buffer from master

Update smart_ptr from master

Update variant from master

Delete boost_tr1.html forwarding html file

The module has been deleted so the documentation is no longer generated.

Update context, coroutine2, fiber from master

Update assert from master

Update convert from master

Update build from master

Update context from master

Update convert from master

Update context from master

Update context, fiber from master

Update integer from master

Update context from master

Update context from master

Update fiber from master

Update context from master

Update context from master

Update assert from master

Update 3 submodules from master

Update functional, quickbook, unordered.

Update align from master

Update build from master

Update core from master

Update chrono from master

Update thread from master

Update context, coroutine2 from master

Update context from master

Update 3 submodules from master

Update date_time, dynamic_bitset, function.

Update algorithm from master

Update interval from master

Update test from master

Update context from master

Update assert from master

Update fiber from master

Update context, fiber from master

marked unusable toolsets for poly_collection

Add poly_collection submodule

Update maintainer list.

Update quickbook from master

Update fusion, phoenix from master

Update config from master

Update smart_ptr from master

Update system from master

Update boostdep, build from master

Update core from master

Update quickbook from master

Update date_time, tti from master

Update pool from master

Update poly_collection from master

Update poly_collection from master

Update context from master

Update program_options from master

Update boostdep from master

Update boostdep from master

added qcc unusable toolsets to poly_collection

Update links to std.dkuug.dk to www.open-std.org

list of excludedd compilers for boost.fiber

Try installing ghostscript on travis

Tests are failing on travis, it might be because of this:
/bin/sh: 2: gs: not found
...removing /home/travis/build/boostorg/build/boost/bin.v2/gs.check

So try installing ghostscript.

Update signals2 from master

Update conversion, lexical_cast from master

Update type_index from master

Update atomic from master

Fix autolink in boost-lib.

Update program_options from master

Update fiber from master

Update python from master

Update 4 submodules from master

Update container, interprocess, intrusive, move.

Update smart_ptr from master

Update gil from master

Update locale from master

Update maintainer list.

 We take pull requests into develop, and then after the tests have cycled, then we merge into master.
Second, this is a large patch, affecting 10s of libraries, but with no explanation. What are you trying to accomplish with this patch?


Remove 'fleshclam' command from Dockerfile

https://trello.com/c/2XWgdfo7/5-💥-make-setup-super-fast-and-easy
Previously we ran 'freshclam' to update virus definitions for Asset
Manager, but this takes a while a doesn't seem to have any impact on
the day-to-day tasks. This removes the command from the Dockerfile -
we may want to support updating virus definitions more regularly and
easily if this is a day-to-day concern.

@kevindew perhaps worth double-checking this is unnecessary now that you've got that final Asset Manager test working?

@benthorner asset manager will still be calling out to govuk_clamscan - but don't think there is any need for it to be up to date, unless Clam will moan if it gets too far out of date. Though given how it's built and docker layers there isn't anything to keep it up date, even with the freshclam command.
One option I recall that was being considered with end-to-end tests and might be better in a dev environment is to set govuk_clamscan to just return an exit code of 0 whatever the input. I have a feeling we have code for that somewhere but I can't remember where.

@kevindew I think it's here: https://github.com/alphagov/publishing-e2e-tests/blob/master/docker-compose.yml#L885. But I'm cautious about making the dev environment unrealistic in this way, although that's just my superficial opinion that a dev on Asset Manager would want to be working with a real virus scanner.

@kevindew I think it's here: https://github.com/alphagov/publishing-e2e-tests/blob/master/docker-compose.yml#L885. But I'm cautious about making the dev environment unrealistic in this way, although that's just my superficial opinion that a dev on Asset Manager would want to be working with a real virus scanner.

Yup, understandable - pros and cons either way.


Array size differs when explicitly declared

Godot version: 3.2.1 stable official
OS/device including version: Windows 10 updated on desktop
Issue description: Array size depends on how it's declared in very deceiving fashion
Steps to reproduce: `extends Node2D
const ARRAY_SIZE = 10
var array1 = [ARRAY_SIZE]
var array2 = []
func _ready():
for i in range(ARRAY_SIZE):
array1.append(i)
array2.append(i)
print("Array1 size is " + str(array1.size()))
print("Array2 size is " + str(array2.size()))
`
Output:
Array1 size is 11
Array2 size is 10
Minimal reproduction project:
ArraySizeProblem.zip

var array1 = [ARRAY_SIZE] creates array with ARRAY_SIZE element. var array2 = [] creates empty array. That's why for array1 it prints 11, and 10 for array2. That's wrong?

You can't declare array size in GDScript. Print the contents of the arrays instead of their size and it should clear the problem for you.


Added importer scripts for Accordion, marquee and icon-block

Importer script for Accordion block with class 'accordion'
Importer script for marquee block with id 'marquee'
Importer script for marquee block with id 'express'

I added some additional importer rules on top of this branch to avoid code conflicts: https://github.com/Deva309/cc/pull/1

@So1ene : do you have a source and target page on milo with imported blocks by any chance? This would help reviewers see the before and after. Thx

We are using different repo to track import script work.


Looking forward to sharing

Looking forward to sharing

Looking forward to sharing

Thx, sorry for the delay, I've got other priorities right now but will try to put it up!

@maxiaoliang1989120 All the code is finally there, along with some READMEs to explain a few things.
If you have any issues don't hesitate to ask!


Some tests on the VM fail now due to the size of output they generate

A recent change (Don't truncate command output in the test runner.) made it an error if a test creates
too much ouput.
The tests
language/unsorted/disassemble_test/0 TruncatedOutput (expected Pass)
language/unsorted/disassemble_test/0 TruncatedOutput (expected Pass)
language/unsorted/disassemble_test/1 TruncatedOutput (expected Pass)
language/unsorted/disassemble_test/1 TruncatedOutput (expected Pass)
language_2/unsorted/disassemble_test/0 TruncatedOutput (expected Pass)
language_2/unsorted/disassemble_test/1 TruncatedOutput (expected Pass)
standalone/typed_data_isolate_test/0 TruncatedOutput (expected Pass)
standalone/typed_data_isolate_test/0 TruncatedOutput (expected Pass)
standalone/typed_data_isolate_test/1 TruncatedOutput (expected Pass)
standalone/typed_data_isolate_test/1 TruncatedOutput (expected Pass)
standalone_2/typed_data_isolate_test/0 TruncatedOutput (expected Pass)
standalone_2/typed_data_isolate_test/1 TruncatedOutput (expected Pass)
vm/dart_2/disassemble_determinism_test TruncatedOutput (expected Pass)

are now failing on multiple configurations.

@munificent @whesse

I thought that I bumped the size up enough to handle dissassemble_test. I'm not sure how the bots didn't catch the other failures. I found the whole process of landing this CL really confusing. Everything was green on the SQ, so I submitted. Then I got a huge flurry of failure emails, but when I looked into them, it looks like all the failures had already been approved?
How were these tests passing before? Was the output getting truncated but the test just didn't care?
I'd like to re-propose my original solution which was to simply not truncate at all. Picking any arbitrary threshold is going to lead us to chase bugs like this forever.

The disassemble tests do not seem to care about the output itself, they were apparently written to ensure that the VM did not crash when disassembling the code. I will look at modifying the tests to not output the disassembly to stdout and instead redirect the output to /dev/null
The typed_data_isolate_test also seems to print the 'data' received and does not check correctness of the 'data' received, maybe this test needs to be modified to not print the 'data' to stdout and instead loop and check  correctness of 'data' received.

https://dart-review.googlesource.com/c/sdk/+/194884 has been submitted to account for the typed_data_isolate_test issues.

I will look at modifying the tests to not output the disassembly to stdout and instead redirect the output to /dev/null

That SGTM, thanks!


workflow is attempting to lint deleted files

hello! it's me again 😄
I'm getting a workflow error that says:
PR with files detected: someFile,anotherFile
##[error]Error: No files matching 'someFile' were found.
##[error]No files matching 'anotherFile' were found.

What settings are you using?

I agree that errorOnUnmatchedPattern defaulted to false should work.. the only setting we've toggled is reportWarnings 🤔

@bradennapier are you able to take a look? this issue is coming up quite often for us during things like refactoring. the only workaround to remove the failing check is to manually delete the Workflow results
I was originally going to suggest filtering the files fetched from the PR by checking file.status === 'deleted', but I don't think that is being return from the GraphQL request that is being made

@bradennapier are you able to take a look? this issue is coming up quite often for us during things like refactoring. the only workaround to remove the failing check is to manually delete the Workflow results
I was originally going to suggest filtering the files fetched from the PR by checking file.status === 'deleted', but I don't think that is being return from the GraphQL request that is being made

I was planning to look into this ASAP - that was my expected solution :-P

@imsteev see the PR #31 - mine works fine when I deleted src/quick.ts

@bradennapier our config file looks like:
module.exports = {
  extends: [
    'react-app',
    'prettier',
    'plugin:@typescript-eslint/recommended'
  ],
  plugins: ['react-hooks', 'mocha', 'i18next', '@typescript-eslint'],
  ignorePatterns: ['build/**'],
  rules: {
    ...
  },
  overrides: [
    {
      files: ['*.test.ts', '*.test.tsx', '*.spec.ts'],
      rules: {
        ...
      }
    }
  ]
};

and the debug output before running ESLint:
[ESLINT] Run With Configuration  {
  extensions: [ '.js', '.jsx', '.ts', '.tsx' ],
  ignore: true,
  useEslintrc: true,
  rulePaths: [],
  errorOnUnmatchedPattern: false,
  fix: false,
  configFile: undefined
}

Also - what version of eslint are you using? Looks like the errorOnUmatchedPattern was added in 6.8.0

oh wait this might be it... we're on 6.7.2

@bradennapier alright bumping the version of ESLint to latest works for me (meaning the workflow passed with a deleted file!)
the downside to this is that I have to add SKIP_PREFLIGHT_CHECK=true to ignore CRA's dependency check before a yarn start.

Cant you use yarn resolutions?

Ah yeah - quick google shows thats a pretty big overall annoyance people have ... not much can be done there there :-\   I could do a force yarn add on eslint after you checkout but that prob would have unwanted side effects :-)

You could add a command in the workflow right before the linting runs that updates eslint though --
name: "lint"
on:
  # by adding a schedule task to this workflow we will automatically
  # begin serializing read-only runs and handling them. The cron job
  # below is set to run every 15 minutes, GitHub will ignore anything
  # under 10 minutes and run every 10 minutes anyway.
  schedule:
    - cron: '*/15 * * * *'
  pull_request:
    types:
      - opened
      - synchronize
      - closed
jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Update eslint
      run: yarn add --dev<EMAIL_ADDRESS>      env:
        NODE_ENV: development
    - uses<EMAIL_ADDRESS>      with:
           reportWarnings: false

yeah any time i have to change a react-scripts dependencies, that SKIP_PREFLIGHT_CHECK flag is necessary. the workflow edit you mentioned seems promising, i didn't know you could add intermediate steps

Yep, you would actually want to do more than that, we skip installing your dependencies if we find node_modules exists when the action is called so you can also use that to cache your modules
https://github.com/bradennapier/eslint-plus-action/blob/1601d2e4f90de971fb03b2134f9c8d337f7ee195/.github/workflows/test.yml

@bradennapier thanks for this info. I think I have a solution that works, but it jumps through a lot of hoops just to get this Workflow to run.
I wonder if a long-term solution that supports backwards compatibility is to just filter out all the files in the PR/diff that are deleted, and not pass them to ESLint at all. Otherwise I think it'd be helpful to document that this action requires 6.8.0 and above for errorOnUnmatchedPattern

Yeah, the problem is that isn't very easy to do since we don't get that meta from graphql -- there was an important reason for the original dev using the graphql instead of the rest request but I can't remember what it was.
Happy to consider other options -- iterating all the changed files and checking if they exist doesn't seem ideal.


How can I add class-wise weight for multi-class focal loss?

I only find loss weight in config file, but it seems that is used to balance different loss?

Yes, you need to implement it by yourself if you would like the class-wise weights for focal loss.

Hi @hellock , does the focal loss of this repo support multi-class?


Producer can't produce messages with an old schema version.

Describe the bug
Producer can't produce messages with an old schema version.
To Reproduce
Steps to reproduce the behavior:

Use pulsar-admin to set-schema-autoupdate-strategy -c Backward public/default
Run following test case:

import org.apache.pulsar.client.api.PulsarClient;
import org.apache.pulsar.client.api.PulsarClientException;
import org.apache.pulsar.client.api.Schema;

public class SchemaTests {

    public static void main(String[] args) throws PulsarClientException {

        PulsarClient client = PulsarClient.builder().serviceUrl("pulsar://<IP_ADDRESS>:6650").build();
        client.newProducer(Schema.AVRO(UserV1.class)).topic("topic-1").create();
        client.newProducer(Schema.AVRO(UserV2.class)).topic("topic-1").create();
        client.newProducer(Schema.AVRO(UserV1.class)).topic("topic-1").create();

    }

    private static class UserV1 {

        private String username;
        private int age;

        public String getUsername() {
            return username;
        }

        public void setUsername(String username) {
            this.username = username;
        }

        public int getAge() {
            return age;
        }

        public void setAge(int age) {
            this.age = age;
        }
    }

    private static class UserV2 {

        public String getUsername() {
            return username;
        }

        public void setUsername(String username) {
            this.username = username;
        }

        private String username;

    }

}

Will produce the following error:
Exception in thread "main" org.apache.pulsar.client.api.PulsarClientException$IncompatibleSchemaException: org.apache.pulsar.broker.service.schema.exceptions.IncompatibleSchemaException: Incompatible schema used
	at org.apache.pulsar.client.api.PulsarClientException.unwrap(PulsarClientException.java:253)
	at org.apache.pulsar.client.impl.ProducerBuilderImpl.create(ProducerBuilderImpl.java:88)
	at org.apache.pulsar.issue.SchemaTests.main(SchemaTests.java:12)

Expected behavior
At producer side, producer can send messages using an old version schema.

@congbobo184 please take a look this issue.

would like to move this to 2.5.0

This has been addressed by #5227


G&F: Fix Mega Evolution validation again

This allows Pokemon that still share one type with the "God" after mega evolving to be on the team (i.e. Gyarados -> Mega Gyarados on Yveltal teams still should be legal, since Gyarados shares Flying and Mega Gyarados shares Dark).

@TheImmortal


Movies Secondary Category Not Firing

When selecting a Secondary category (i.e By Year) the job is not launching, and not firing.

This is now fixed as part of the migration to presenters.


Git doesn't update saved changes in git gui

VSCode Version: 1.49.3
OS Version: 10.15.7
Steps to Reproduce:
1.right click uncheck git source control
2. check it again to bring it back

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

I was able to get it back and working by switching to a new project then switching back.


Gzip fix

Based on the discussion with @paulbramsen in #74, I have split the PR so that we can benefit from the gzip changes without losing the authentication mechanism provided by AuthenticatedURL.
This also removes the thread local's (for the token and authenticatedurl) in favor of the approach used by SparkFSFetcher's readJsonNode function which creates a separate token every time the function is called. In our tests, this approach reduces the number of connections leaked.
This works on our production clusters (queue size is processed quickly), but still uses a large number of sockets and puts a fairly large (though more manageable) load on the JHS. @stiga-huang's solution in #67 will work around those issues, unless the community is interested in extending the pooling mechanism to handle auth. This PR is only for the existing fetcher if users can't migrate to the new fetcher in #67 that bypasses the JHS.
@paulbramsen mind giving this a review?
@akshayrai we discussed separating out #74 into a separate fetcher. Would you still recommend doing that with this patch as it is more of a minor improvement on the existing fetcher?
I think #74 can be closed at this point. Thanks!

@rsprabery , I would still push for a separate fetcher. Since a lot of people are already running the current fetcher in production, it would be good if we can provide them the flexibility to switch to the new fetcher and try it out.
Add deprecated tags to the old fetcher and include this as a new fetcher. After a few weeks we can completely remove the old fetcher.

@akshayrai @rsprabery or maybe put the gzip code behind a feature switch?

@paulbramsen , what do mean by a feature switch?

@akshayrai I meant some param in the fetcher conf.

@rsprabery, any update on this?

@akshayrai @paulbramsen Been busy with some other projects - I'm handing this over to @zero45.
We were debating whether the community needs this patch. We are currently using this internally, but will likely be moving over to @stiga-huang's patch in the near future after some testing. We may also look at submitting a gzip PR for the new fetcher. Just wanted to get those ideas out there for community feedback before we move forward with that.

We too are using @stiga-huang's patch.

@rsprabery @zero45, definitely. It would be good to include this fetcher along with the one contributed by @stiga-huang. Though we might switch over to the FS Fetcher, some people might still prefer using the GZIP fetcher. It will serve as an alternate source to fetch information.
We should start deprecating the old fetcher(without gzip) and that should leave us with two fetchers (Gzip and FS)

Hi @rsprabery @zero45 @paulbramsen, is this PR still relevant or should it be closed?

This could potentially still be useful if someone wanted to fix the merge conflicts since not everyone can use the filesystem fetcher.
@rsprabery does this work with Kerberos?

Hey @paulbramsen, @cwsteinbach -- We should close this PR. I made a comment in #73 pointing to a patch -> https://github.com/linkedin/dr-elephant/files/499499/dre_issue73.patch.txt.
The code here did not support Kerberos.

@paulbramsen This does not work with kerberos which was one of the reasons we never ported it over to its own fetcher.
If the community is still interested, we can talk to @zero45 and apply his patch to this PR. Because of the lack of kerberos I'd just suggest closing this.
Kerberos won't be easy to add in until the upstream (Hadoop) auth library supports pooling + gzip.

Thanks everyone. I am closing this PR.
@zero45, would it be possible for you to send a PR for the patch?


How long will the board update?

Hi, I have submitted a new result a week ago and successfully merged, but I notice that the result is not updated on the leadee board. So I want to know that how long will the board update? Thanks!

Hello,
Sincere apologies for the delay. The delay is due to pending automation of the leaderboard update. That was compounded by the fact that one of our team members who is working on the leaderboard migration had multiple deadlines last week and all of us have also been busy with the TREC Deep Learning Track. We will try to manually update the leaderboard soon. But in the meantime please feel free to use the evaluation results in your papers and presentations even if they are not on the official leaderboard yet.
We sincerely apologize for the inconvenience.
Best regards,
Bhaskar


No content in PDF in VS Code

Thank you for the repo.
I followed your README instruction.
I set up for my project, adding .devcontainer/devcontainer.json and .devcontainer/docker-compose.ym.
I open the command palette in Visual Studio Code (CTRL+SHIFT+P) and select Remote-Containers: Open Folder in Container... and chose my project directory.
I have Remote-Containers and LaTeX-Workshop installed.
I built and saved my tex doc it created a PDF but there is NO content.
My tex file:
\documentclass{article}
\begin{document}
An Example document.

Updating tex from VS Code.

\end{document}

Terminal output:

[WARNING] TZ environment variable not set, time might be wrong!
Docker socket not owned by group IDs 1000, 102 or 976, changing its group to 1000
Base version: alpine-2020-09-13T09:12:41Z-b015a59
Running as user vscode
VS code server 1.50.0
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied
Docker server  | client 19.03.12
Docker-Compose 1.26.2
TexLive release 2020
tlmgr version 55369 (2020-06-01 02:32:00 +0200)
Useful commands available:

Update LaTex packages: tlmgr update --all
Install a LaTex package:
tlmgr install packagename
texhash
Install an OS package: sudo apk add packagename
[powerlevel10k] fetching gitstatusd .. [ok]
/workspace ▓▒░

Do you have any ideas?

It works now.
I don't know why.
I changed the theme, open the PDF in a browser from LaTeX-Workshop.

@shinokada thanks for reporting the issue. I'll have a look if I can reproduce the issue. Also for the Docker socket error, do you mind running in the vscode terminal
ls -al /var/run/docker.sock

and send me the output? I'm curious why it cannot have access to the Docker socket, especially since I use this approach for a bunch of other development containers.
Thanks!

Here is the output:
 /workspace ▓▒░ ls -al /var/run/docker.sock
srwxr-xr-x    1 root     vscode           0 Oct 10 00:47 /var/run/docker.sock

Thanks for the output!
I believe this is using TexLive. Although funnily enough, I'm no Latex expert either.
Adding another one would not be trivial, but I'll try to move the container to use XeLaTex instead of TexLive & tlmgr, maybe their install/package manager is better than TexLive.0

I don't think you need to change it.
Why don't you add a section in the README about "How to change to another typesetting engine using Dockerfile".

Yes that's a good idea, let's keep the issue opened so I can get to it in the future.
I'll probably fix up the Docker build first and base it on debian instead of Alpine as tlmgr doesn't seem to support Alpine's musl anymore, so commands might be different once that's done.

I wonder how much the image size will increases if you use the debian instead of Alpine.

Suggestion for your repo structure:
Jupyter notebook repo has different images depends on users' needs.
I thought LaTeX is a similar situation. You may use LaTeX for essay, writing, thesis, etc.
So maybe you can have the existing repo as the base-latexcontainer, then we can create our stack and make a pull request to your repo.
Users can select one stack for their work.
What do you think?

Yes I can make different docker tags with different latex engines (from different Dockerfiles I would say).
Anyway, let me fix the existing texlive build first 😄 And debian would probably increase the image size by about 50MB with the packages installed, not a big deal either.

Build is fixed, I'll try to fix the several issues you're opened now.

I wonder how much the image size will increases if you use the debian instead of Alpine.

It was 393MB, it's now 485MB
If you don't mind, can you create another issue to use different typesetting engines please? So that I can close this issue and for clarity purposes. Thanks!
Also the docker error in the terminal should be fixed now.

See #5
You might want to docker pull qmcgaw/latexdevcontainer to get the newer version and then Rebuild and reopen container in the VScode command palette. I'll add some doc in the readme on how to update it too.


[BUG] disk monitor cannot recognize disks if disk paths are somehow changed after reboot

Describe the bug (🐛 if you encounter this issue)
When a block-type disk is added, a lvstore is created, and its UUID is stored in node.Status.DiskStatus. If the underlying storage of the disk is replaced, such as changing the disk path after a reboot, spdk_tgt fails to recognize it and attempts to create a new lvstore on the disk. This operation leads to contamination of the wrong disk's contents.
To resolve this problem, we can send the recorded disk UUID to the disk grpc service to assist in checking if the disk is the expected one.
To Reproduce
Steps to reproduce the behavior:
We can emulate the issue by the steps

Create a block-type disk test-block-1 on a node using a loop devicedd if=/dev/zero of=blockfile1 bs=1M count=5120 && sudo losetup /dev/loop0 blockfile1

Restart the node
Create a new file for the loop device (/dev/loop0)dd if=/dev/zero of=blockfile2 bs=1M count=5120 && sudo losetup /dev/loop0 blockfile2

The disk is added to the node, and the blockfile2 is contaminated.grep -nr test-block-1 blockfile2

Expected behavior
A clear and concise description of what you expected to happen.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version:
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
Add any other context about the problem here.

This should be fixed in 1.5.0 already, but it seems missing to validate by @longhorn/qa ?

Does this improvement try to solve this issue in https://github.com/longhorn/longhorn/issues/5827? If so, I can still observe this issue in master-head (longhorn-manager 77ed1a7) by the following steps:

Create nodes with machine type c5d.2xlarge, and complete and spdk setup
Originally, the nvme device is on /dev/nvme1n1, so we create the block type disk with path /dev/nvme1n1:

$ fdisk -l
Disk /dev/nvme0n1: 300 GiB,<PHONE_NUMBER>00 bytes, 629145600 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4B464A1A-ABA0-49AF-8065-3030FA493F67

Disk /dev/nvme1n1: 186.26 GiB,<PHONE_NUMBER>00 bytes, 390625000 sectors
Disk model: Amazon EC2 NVMe Instance Storage
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme2n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And everything works well, spdk volume can be created, workload works well too, data can be write into/read from the spdk volume through the workload
After reboot the node, the nvme device is changed to /dev/nvme2n1, and the block type disk we just created in step 2 becomes Unschedulable with size 0 / 0 Gi:

$ fdisk -l
Disk /dev/nvme2n1: 186.26 GiB,<PHONE_NUMBER>00 bytes, 390625000 sectors
Disk model: Amazon EC2 NVMe Instance Storage
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 300 GiB,<PHONE_NUMBER>00 bytes, 629145600 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4B464A1A-ABA0-49AF-8065-3030FA493F67

Disk /dev/nvme1n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

supportbundle_cfda4f6b-b95a-45db-9e96-9036892bb276_2023-07-17T09-35-48Z.zip

After reboot the node, the nvme device is changed to /dev/nvme2n1, and the block type disk we just created in step 2 becomes Unschedulable with size 0 / 0 Gi:

I think the fix here is to prevent the disk will not be initialized again after you update the disk with the new path. The fix is not to automatically correct the relationship between the new path of the block device and the Longhorn block disk.  @derekbit right?
I would be helpful to update the testing steps for QA.

Does this improvement try to solve this issue in #5827? If so, I can still observe this issue in master-head (longhorn-manager 77ed1a7) by the following steps:

Create nodes with machine type c5d.2xlarge, and complete and spdk setup
Originally, the nvme device is on /dev/nvme1n1, so we create the block type disk with path /dev/nvme1n1:

$ fdisk -l
Disk /dev/nvme0n1: 300 GiB,<PHONE_NUMBER>00 bytes, 629145600 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4B464A1A-ABA0-49AF-8065-3030FA493F67

Disk /dev/nvme1n1: 186.26 GiB,<PHONE_NUMBER>00 bytes, 390625000 sectors
Disk model: Amazon EC2 NVMe Instance Storage
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme2n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And everything works well, spdk volume can be created, workload works well too, data can be write into/read from the spdk volume through the workload
After reboot the node, the nvme device is changed to /dev/nvme2n1, and the block type disk we just created in step 2 becomes Unschedulable with size 0 / 0 Gi:

$ fdisk -l
Disk /dev/nvme2n1: 186.26 GiB,<PHONE_NUMBER>00 bytes, 390625000 sectors
Disk model: Amazon EC2 NVMe Instance Storage
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 300 GiB,<PHONE_NUMBER>00 bytes, 629145600 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4B464A1A-ABA0-49AF-8065-3030FA493F67

Disk /dev/nvme1n1: 160 GiB,<PHONE_NUMBER>40 bytes, 335544320 sectors
Disk model: Amazon Elastic Block Store
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

 supportbundle_cfda4f6b-b95a-45db-9e96-9036892bb276_2023-07-17T09-35-48Z.zip
cc @derekbit

Yes, this is expeceted.
The steps are updated in https://github.com/longhorn/longhorn/issues/6125#issuecomment-1591694243.

Verified passed on master-head (longhorn-manager 77ed1a7) and v1.5.x-head (longhorn-manager 910081c) following the test steps.


Update load-balancer-ipv6-internet-ps.md

Hi @stegag, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (stegag). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@stegag : Thanks for your contribution to the Azure documentation! The author, @sdwheeler, has been notified to review your proposed change.

@stegag - thanks for your feedback
#sign-off


Wrapped with a UMD pattern as commented in #66

This PR should not be merged yet. It is to be discussed whether the file matchMedia.addListener.js should also be wrapped in a UMD.

Is AMD worth supporting anymore? Is commonjs good enough?
Mostly asking because every bit counts with this script - often inlined in the html.

I'd rather prefer AMD over commonjs, especially on a browser environment. Speed and Inlining are arguments against the use of an async loader. But how would you provide matchMedia synchronously in an otherwise async environment?

@krnlde
We do not need wrapp a UMD pattern. It is already works.
require("matchMedia");
if (matchMedia('tv').matches) {
  // tv media type supported
}


Blank charts in falcosidekick-ui but falco is working (ARM64)

Describe the bug
The falcosidekick-ui is showing blank charts, I can see that in the top it is reporting the events though. Also, I can see that events are appearing in the Falco logs.
How to reproduce it
The installation command:
helm install falco falcosecurity/falco --namespace falco --create-na
mespace --values values.yaml

My values file:
driver:
  kind: ebpf

falcosidekick:
  enabled: true
  replicaCount: 1
  webui:
    enabled: true
    replicaCount: 1
    user: "REDACTED"
    ingress:
      enabled: true
      hosts:
      - host: falco.magi.lan
        paths:
        - path: /
      tls:
      - hosts:
        - falco.magi.lan

  config:
    customfields: "cluster:MAGI"

tolerations:
- effect: NoSchedule
  key: node-role.kubernetes.io/master
- effect: NoSchedule
  key: node-role.kubernetes.io/control-plane
- key: CriticalAddonsOnly
  operator: Exists
  effect: NoSchedule

Expected behaviour
The UI charts should be populated with falco events.
Screenshots

Environment

Falco version:
Falco version: 0.34.1 (aarch64)
System info:

{
  "machine": "aarch64",
  "nodename": "falco-6s564",
  "release": "6.1.19-v8+",
  "sysname": "Linux",
  "version": "#1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023"
}

Cloud provider or hardware configuration:
3 nodes K3S cluster, the nodes are raspberry pi 4 b with 4GB of RAM each.
OS:
Debian GNU/Linux 11 (raspbian bullseye)
Kernel:
Linux 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux
Installation method:
Falco Helm chart

What are the logs in Falcosidekick pods?

Thanks for the early response!
falco-falcosidekick pod:
2023/04/04 11:51:06 [INFO]  : Falco Sidekick version: 2.27.0
2023/04/04 11:51:06 [INFO]  : Enabled Outputs : [WebUI]
2023/04/04 11:51:06 [INFO]  : Falco Sidekick is up and listening on :2801
2023/04/04 11:52:39 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:06 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:08 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:23 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:24 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:25 [INFO]  : WebUI - Post OK (200)
2023/04/04 11:53:33 [INFO]  : WebUI - Post OK (200)

falco-falcosidekick-ui pod:
2023/04/04 11:51:30 [WARN] : Index does not exist
2023/04/04 11:51:30 [WARN] : Create Index
2023/04/04 11:51:30 [INFO] : Falcosidekick UI is listening on <IP_ADDRESS>:2802
2023/04/04 11:51:30 [INFO] : log level is info
2023/04/04 11:56:38 [INFO] : user 'admin' authenticated

falco-falcosidekick-ui-redis
9:C 04 Apr 2023 11:51:07.412 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9:C 04 Apr 2023 11:51:07.412 # Redis version=6.2.10, bits=64, commit=00000000, modified=0, pid=9, just started
9:C 04 Apr 2023 11:51:07.412 # Configuration loaded
9:M 04 Apr 2023 11:51:07.419 * monotonic clock: POSIX clock_gettime
9:M 04 Apr 2023 11:51:07.423 * Running mode=standalone, port=6379.
9:M 04 Apr 2023 11:51:07.423 # Server initialized
9:M 04 Apr 2023 11:51:07.462 * <search> Redis version found by RedisSearch : 6.2.10 - oss
9:M 04 Apr 2023 11:51:07.462 * <search> RediSearch version 2.6.5 (Git=HEAD-71bd22f3)
9:M 04 Apr 2023 11:51:07.462 * <search> Low level api version 1 initialized successfully
9:M 04 Apr 2023 11:51:07.462 * <search> concurrent writes: OFF, gc: ON, prefix min length: 2, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results:  10000, search pool size: 20, index pool size: 8,
9:M 04 Apr 2023 11:51:07.466 * <search> Initialized thread pool!
9:M 04 Apr 2023 11:51:07.466 * <search> Enabled diskless replication
9:M 04 Apr 2023 11:51:07.466 * <search> Enabled role change notification
9:M 04 Apr 2023 11:51:07.467 * Module 'search' loaded from /opt/redis-stack/lib/redisearch.so
9:M 04 Apr 2023 11:51:07.491 * <graph> Starting up RedisGraph version 2.10.8.
9:M 04 Apr 2023 11:51:07.510 * <graph> Thread pool created, using 4 threads.
9:M 04 Apr 2023 11:51:07.510 * <graph> Maximum number of OpenMP threads set to 4
9:M 04 Apr 2023 11:51:07.510 * Module 'graph' loaded from /opt/redis-stack/lib/redisgraph.so
9:M 04 Apr 2023 11:51:07.511 * <timeseries> RedisTimeSeries version 10805, git_sha=a7a296c8f3f6e312811032233a468d57d45957ca
9:M 04 Apr 2023 11:51:07.511 * <timeseries> Redis version found by RedisTimeSeries : 6.2.10 - oss
9:M 04 Apr 2023 11:51:07.511 * <timeseries> loaded default CHUNK_SIZE_BYTES policy: 4096
9:M 04 Apr 2023 11:51:07.511 * <timeseries> loaded server DUPLICATE_POLICY: block
9:M 04 Apr 2023 11:51:07.511 * <timeseries> Setting default series ENCODING to: compressed
9:M 04 Apr 2023 11:51:07.511 * <timeseries> Detected redis oss
9:M 04 Apr 2023 11:51:07.519 * <timeseries> Enabled diskless replication
9:M 04 Apr 2023 11:51:07.519 * Module 'timeseries' loaded from /opt/redis-stack/lib/redistimeseries.so
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> version: 20404 git sha: eb5eba8 branch: HEAD
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> Exported RedisJSON_V1 API
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> Exported RedisJSON_V2 API
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> Exported RedisJSON_V3 API
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> Enabled diskless replication
9:M 04 Apr 2023 11:51:07.520 * <ReJSON> Created new data type 'ReJSON-RL'
9:M 04 Apr 2023 11:51:07.520 * Module 'ReJSON' loaded from /opt/redis-stack/lib/rejson.so
9:M 04 Apr 2023 11:51:07.520 * <search> Acquired RedisJSON_V3 API
9:M 04 Apr 2023 11:51:07.520 * <graph> Acquired RedisJSON_V1 API
9:M 04 Apr 2023 11:51:07.524 * <bf> RedisBloom version 2.4.4 (Git=unknown)
9:M 04 Apr 2023 11:51:07.524 * Module 'bf' loaded from /opt/redis-stack/lib/redisbloom.so
9:M 04 Apr 2023 11:51:07.526 * Ready to accept connections
9:M 04 Apr 2023 11:56:08.003 * 100 changes in 300 seconds. Saving...
9:M 04 Apr 2023 11:56:08.005 * Background saving started by pid 35
35:C 04 Apr 2023 11:56:08.013 * DB saved on disk
35:C 04 Apr 2023 11:56:08.015 * RDB: 0 MB of memory used by copy-on-write
9:M 04 Apr 2023 11:56:08.106 * Background saving terminated with success

The console is empty sadly 😢

No request with 401 error?

I would like to say yes but no...:

Select 1Y for Since to see if it's not an issue with Dates please

Screenshots with the since filter set to 1Y:

This is a mystery, I don't understand what's happening :sob:

Yeah... it is really frustrating 😭

I never noticed a such strange behavior, are you available on kubernetes.slack.com #falco? It will be easier to help I think.

Nope, but I guess I can just create an account for it

For people facing the same issue, it is scoped to arm64 users.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale


How to define a default for a new theme colour?

I've added a new feature to my extension and want the user to be able to customise the colour. I figured it makes sense to have it in the workbench.colorCustomizations section, so planned to allow the user to do it like this:
"workbench.colorCustomizations": {
	"dart.closingLabels": "#ff0000"
},

Then in my code I'm doing this:
new vs.ThemeColor("dart.closingLabels")

This works fine, but I don't know how to set a default. Ideally I'd like to fall back to the tab.inactiveForeground colour (so that it has a reasonable default for any theme). However, I can't see a way to do this.
Is there a nice way to handle this? Or is the best thing just to look for workbench.colorCustomizations.dart.closingLabels in the settings and if it's not set, use the string  tab.inactiveForeground for the colour?

This seems to work; but feels a bit wonky:
vs.workspace.getConfiguration("workbench").get("colorCustomizations")["dart.closingLabels"]

We need a contribution point for user defined theme colors, this is #14309.
That way user colors can define default and can also be defined in themes.
I'll add that for August.


Dynamic record size tests fail sometimes

Problem:
From time to time we run into failures with dynamic record size tests.
https://travis-ci.org/awslabs/s2n/jobs/650075690?utm_medium=notification&utm_source=github_status
Running s2n dynamic record size tests

Cipher: AES128-SHA                   Vers: TLSv1.2  ... PASSED
Cipher: DHE-RSA-AES128-SHA           Vers: TLSv1.2  ... PASSED
Cipher: AES256-SHA                   Vers: TLSv1.2  ... PASSED
Cipher: DHE-RSA-AES256-SHA           Vers: TLSv1.2  ... PASSED
Cipher: AES128-SHA256                Vers: TLSv1.2  ... PASSED
Cipher: AES256-SHA256                Vers: TLSv1.2  ... PASSED
Cipher: DHE-RSA-AES128-SHA256        Vers: TLSv1.2  ... PASSED
Cipher: DHE-RSA-AES256-SHA256        Vers: TLSv1.2  ... FAILED
Makefile:52: recipe for target 'dynamic_record' failed
make[2]: *** [dynamic_record] Error 1
make[2]: Leaving directory '/home/travis/build/awslabs/s2n/tests/integration'
Makefile:39: recipe for target 'integration' failed
make[1]: *** [integration] Error 2
make[1]: Leaving directory '/home/travis/build/awslabs/s2n/tests'
Makefile:73: recipe for target 'integration' failed
make: *** [integration] Error 2
The command ".travis/s2n_travis_build.sh" exited with 2.
0.00s$ .travis/s2n_after_travis_build.sh

https://travis-ci.org/awslabs/s2n/jobs/649153883?utm_medium=notification&utm_source=github_status
Traceback (most recent call last):
  File "s2n_dynamic_record_size_test.py", line 293, in <module>
    sys.exit(main())
  File "s2n_dynamic_record_size_test.py", line 282, in main
    failed += test(host, port, test_ciphers, int(file_size / 2))
  File "s2n_dynamic_record_size_test.py", line 196, in test
    result = run_test(host, port, ssl_version, cipher, threshold)
  File "s2n_dynamic_record_size_test.py", line 179, in run_test
    failed += analyze_throughput_dump(out_array)
  File "s2n_dynamic_record_size_test.py", line 233, in analyze_throughput_dump
    output = array[i]
IndexError: list index out of range
Makefile:52: recipe for target 'dynamic_record' failed

Proposed Solution:
Investigate, fix.

Note this is the same error as above, but for a different test.
Cipher: ECDHE-RSA-AES256-GCM-SHA384  Vers: TLSv1.2  ... PASSED
Cipher: ECDHE-RSA-CHACHA20-POLY1305  Vers: TLSv1.2  ... PASSED
Traceback (most recent call last):
  File "s2n_dynamic_record_size_test.py", line 293, in <module>
    sys.exit(main())
  File "s2n_dynamic_record_size_test.py", line 282, in main
    failed += test(host, port, test_ciphers, int(file_size / 2))
  File "s2n_dynamic_record_size_test.py", line 196, in test
    result = run_test(host, port, ssl_version, cipher, threshold)
  File "s2n_dynamic_record_size_test.py", line 179, in run_test
    failed += analyze_throughput_dump(out_array)
  File "s2n_dynamic_record_size_test.py", line 233, in analyze_throughput_dump
    output = array[i]
IndexError: list index out of range
Makefile:52: recipe for target 'dynamic_record' failed

I've seen this pop up in another 2 builds, same error code. The cipher does not matter, the index error strikes at random.

Possibly I fixed this as part of https://github.com/awslabs/s2n/pull/1669 by removing a potential race condition. Since it was a transitory failure, I'm not sure how to verify other than waiting a while and checking that it doesn't happen again.

Nope, the above PR did not fix the flakiness. Still periodically failing :(

Still happening...from travis:
Cipher: ECDHE-RSA-AES256-GCM-SHA384  Vers: TLSv1.2  ... FAILED
Makefile:52: recipe for target 'dynamic_record' failed
make[2]: *** [dynamic_record] Error 1

Related to #1485. To test this in the new framework, we need to be able to send data over a connection.

The test was working when dynamic record size feature was launched. I think at certain point, we broke the test and did not fix it right away. It is probably related to send, cipher or record changes. The test basically verifies packet length from TCPDump output < mss when sent bytes < dynamic threshold and > 1500(default MTU) after that.
zz85 has made a change to print the tcpdump output when the test fails https://github.com/awslabs/s2n/pull/1717. According the error output https://travis-ci.org/github/awslabs/s2n/jobs/669839733, I think the problem is that we do not see a packet length > 1500 case here. We could look for more lines from output to see if we can find a packet whose length is greater thank 1500.

When you look at the output you can see, in the failing cases, that the last line of output is incomplete. This could be tcpdump getting killed before flushing the output buffer (although we use line buffering now). We could increase the sleep time, or wait for a properly sized packet in another thread.
My approach (rewriting the test) is based on the sleep() calls and the lack of process management. Getting the process management right will help address the same sleep patterns that exist in other tests as well.

When you look at the output you can see, in the failing cases, that the last line of output is incomplete. This could be tcpdump getting killed before flushing the output buffer (although we use line buffering now). We could increase the sleep time, or wait for a properly sized packet in another thread.
My approach (rewriting the test) is based on the sleep() calls and the lack of process management. Getting the process management right will help address the same sleep patterns that exist in other tests as well.

Cool. This should work, ping me if you need PR review for that :) Thanks !


feat: Initial Commit - Implement Changes

README
Please read the README before reviewing this PR!
A few notes on this initial commit:

For now, dist will be used for the action checkout until we build out a better ci process that both builds and publishes the release accordingly.
Our current CI only runs npm run all, which runs:

npm run test
npm run build
npm run format
npm run lint
npm run package

Jest tests will run via --runInBand until we verify workers/subprocess behave correctly in the CI environment
Before allowing additional Feature Requests/PRs/merges outside of enabling the core functionality, we need to ensure all logic behaves correctly amongst our internal services.
We will label the first release as a pre-release until engineering approves for official release.

Please fix these properties in package.json:
  "name": "typescript-action",
  "description": "TypeScript template action",
  "main": "lib/main.js",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/actions/typescript-action.git"
  },
  "keywords": [
    "actions",
    "node",
    "setup"
  ],
  "author": "",

Remove main and keywords?

It would be good to remove dist before the first release.
https://docs.github.com/en/actions/creating-actions/releasing-and-maintaining-actions

Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the main branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or shas, and you help ensure the security of third party pull requests by doing the build yourself during a release.

See https://github.com/github-developer/javascript-action/blob/main/.github/workflows/publish.yml

It would be good to remove dist before the first release.
https://docs.github.com/en/actions/creating-actions/releasing-and-maintaining-actions

Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the main branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or shas, and you help ensure the security of third party pull requests by doing the build yourself during a release.

See https://github.com/github-developer/javascript-action/blob/main/.github/workflows/publish.yml

Removed the dist directory and finalized publishing via the publish.yml workflow.
You can see it successfully packaging and working (via ncc and the JasonEtco/build-and-tag-action@v2) here: https://github.com/arivera-xealth/xealth-auto-cherry-pick/actions/runs/2746863392
Disregard the error The format of '' is not a valid email address with display name as I resolved that in the latest commit here.
We need to keep the main json key in package.json since JasonEtco/build-and-tag-action@v2 uses it for publishing (it uses that key as the target in build/packaging).

@joebowbeerxealth We'll need to create branch protection for all branches with the v prefix (what we'll be using for releases). So branches like v1.0.0, 2.0.0. That way only the publish action is able to compile and publish to those branches.


Don't include list of reference assemblies in blazor.boot.json for server-side apps

Is the file needed at all for server-side Blazor apps?

This was fixed in 0.8.0 (as in, we no longer have that file at all in server-side apps).


Update CCTP Lib dependency with static Bzip2 lib

This PR updates the CCTP Lib dependency to the latest version, that includes a small fix to statically link the Bzip2 library.
Such change is required to avoid errors when compiling Zend on systems on which Bzip2 is installed as shared library, since in that case Cargo uses the dynamic linking without providing the Bzip2 symbols.
Such update required also some small changes to make unit tests compatible with the new CCTP Lib.

This PR should be merged after

https://github.com/HorizenOfficial/zendoo-cctp-lib/pull/41
https://github.com/HorizenOfficial/zendoo-cctp-lib/pull/42

After having merged the CCTP Lib and releasing a new version, this branch should be changed accordingly to include the right version as dependency.

This PR should be put on hold since we discovered some weird behavior while developing the requested changes. In particular, we saw some tests in mcTest fail when using Darlin proving system (instead of Coboundary Marlin that is working as expected).
The changes contained in this PR are made to be compatible with the latest version of the CCTP Lib, that introduced a new way of handling the DLog keys: it's not possible to call init_dlog_keys() multiple times anymore, during the execution of the application it's only possible to call it once and then using trimmed keys whenever we want to generate or verify proofs with a smaller segment size.
On Zend, we rely on such mechanism because the main application always uses a segment size of 2^18 (and it's only used for verifying proofs since they are generated by Sidechains) but we needed to implemented fast Python tests to generate and verify proofs with a segment size of 2^9 (to make it faster).
With the old version of MC Crypto Lib (and of CCTP Lib) we used the special function init_dlog_keys_test_mode(max_segment_size, supported_segment_size) to initialize keys with a smaller supported segment size (2^9) to generate proofs that were compatible with the verification process of Zend main application (that uses 2^18 as a max segment size) .
Since such function is not available anymore, we can only generate keys using init_dlog_keys(segment_size) and relying on trimming the DLog keys when generating and verifying the proofs. So, basically, the current situation is:

Zend uses DLog keys with a segment size of 2^18 (for verification only, there is no need to generate proofs)
mcTestCall initializes DLog keys with a segment size of 2^9 and contextually generates the proving and verification keys with the same parameter
mcTestCall uses DLog keys with a segment size of 2^18 when generating and verifying proofs, but now uses an additional parameter segment_size when calling create_proof() and verify_proof() to trim the DLog keys

Everything is perfectly compatible when using Coboundary Marlin, but it immediately stops working for Darlin because it seems like we cannot use DLog keys of 2^9 segment size to generate the proving and verification keys and then use 2^18 when generating the proof (even though the keys get trimmed). This behavior must be analyzed carefully to avoid to introduce incompatibilities in Zendoo and eventually hidden hard forks. Moreover, it should be checked that the Sidechain SDK (which uses the updated version of CCTP Lib through the SC Crypto Lib) has not any inconsistency (it should be generally safe since it's not currently using Darlin).

Issues were addressed and are now part of https://github.com/HorizenOfficial/zendoo-mc-cryptolib/pull/60


Alerts in correlations

Description

Alerts in Correlations Feature

Issues Resolved
[988]

Testing
1).Create Correlation Rule with Alert Trigger
https://github.com/opensearch-project/security-analytics-dashboards-plugin/assets/69919272/a3a1f5ce-dd72-492a-8d0e-c25a079cd987
2). View Correlation Alerts and check Notifications
https://github.com/opensearch-project/security-analytics-dashboards-plugin/assets/69919272/60be0f6c-bbb0-49a4-a6b5-0eca801e9fa7
3). Error when correlation-rule is deleted
https://github.com/opensearch-project/security-analytics-dashboards-plugin/assets/69919272/5416c9c1-bffb-41eb-a2ea-ec28acee86d8
UX Review changes
After UX review changes incorporated

Alert Trigger Panel alignment

LogTypes added as a column while viewing Correlation Alerts

Create Correlation Rule

Experimental on the Correlations tab

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

CI tests passing in local:


Error when I use the override option

What happened?
Error message: Hasnayeen\Themes\Themes::make(): Return value must be of type Hasnayeen\Themes\Contracts\Theme, none returned
How to reproduce the bug
Set the "override" option to "true".
Package Version
latest
Filament Version
3.0.62
PHP Version
8.2.4
Laravel Version
10.25.1
Notes
I use this code:
ThemesPlugin::make()
    ->registerTheme(
        [
            MyTheme::getName() => MyTheme::class
        ],
        true,
    ),

Fixed by ac1ee2e


Make AnyArrayBuffer conform to Vector

There's plenty I'd like to improve in here, plenty to discuss, and plenty of tests to add, but I wanted to get this in front of @marcrasi  ASAP

I shall look later today! I'm working on a few urgent issues first, but I plan to get to this next.

@marcrasi This works for me with TOOLCHAINS=com.google.swift.20200826.  Is there any way we can upgrade the bots that are testing SwiftFusion?

@marcrasi This works for me with TOOLCHAINS=com.google.swift.20200826. Is there any way we can upgrade the bots that are testing SwiftFusion?

It's configured in https://github.com/borglab/SwiftFusion/blob/master/.github/workflows/ci.yml

Any ideas?  I'm stumped.

@marcrasi  We should move to a Linux-based CI I think, macOS env is not consistent on Actions...

Yeah, maybe the macos version is too old for the new Swift toolchain.

Sorry, the urgent stuff took up all my time today. I'll try again to look at this tomorrow :)

@marcrasi I think the bot needs the latest Xcode-beta installed (and xcode-select called to point at it).  Do you think you could set that up?

I searched around for github actions documentation and found this: https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md
Looks like we might be able to get xcode beta only a xcode-select. I'll try that and if it doesn't work I'll see if I can do something else that works.

It worked!!! 🎉


mobile page scroll problrm

use in mobile, if has too many items, to move page bottom item, the page scroll up  and cannot to drop bottom item
demo: http://jsbin.com/civesoj/edit?html,css,js,output

It has been solved , donot page scroll, it  part scroll is ok


UX: account deletion dialogue does not tell me which account I'm deleting

Describe the bug
I'm logged in to multiple accounts, through the account switcher feature. When deleting an account, the final "Delete account" dialogue does not tell me which account I'm deleting. When it comes time to click the final button, I have to put a lot of faith in past-me (a notorious dumbass) to have selected the right account at the first step.
The confirmation email also does not mention an account name.
To Reproduce
Go through the steps of deleting an account.
Expected behavior
As an example, if I go to delete a repo on github, it makes it very clear which repo I'm about to delete

Deleting things is always scary, and this gives me more peace of mind.
Details

Platform: desktop web

@DavidBuchanan314  does this ui change solves this issue CC @pfrazee

:+1:  Part way there, but there's a second screen after that (where you enter the confirmation code from the email - sorry I don't have a screenshot handy) that would also need changing (assuming that's a separate dialogue, maybe the component is reused)

@DavidBuchanan314  we need to show something like this there as well right on the confirmation code modal?

Yeah, this is what the final step looks like:


Is it possible to test for bimodality in scanpy?

Is there a way to test if particular genes of a single-cell-RNA-seq-dataset show bimodal distributions, in order to infer heterogeneity?
e.g. like in: https://www.nature.com/articles/nature13437

@Koncopd @ivirshup @flying-sheep @gokceneraslan Is there something in this direction implemented in scanpy? I would be happy to hear from you. If it exist already, I wouldn't have to implement it on my own :)

Hi @erikadudki,
Sorry for the slow replies to this post. There is no test implemented for bimodality in scanpy at the moment. For modeling you could look into diffxpy, where you may be able to fit a gaussian mixture model to do model selection. Otherwise I guess statsmodels is the way forward for this in python.

@erikadudki  If you are willing to dabble in R, the scDD package  seeks to address this problem specifically.  It may also be worth looking at for inspiration if you want to pursue your own implementation in python.


Feature request - multithreaded rendering

As part of migrating my project (a video player) from bgfx to sokol, it became apparent pretty quickly that I would need to figure out how to deal with sokol being designed for single threaded use with my application having a separate update and render thread.
So I wrote a proof-of-concept multithreaded rendering class, and adapted sokol_imgui.h to use this too.
I know @floooh mentioned in https://github.com/floooh/sokol/issues/403 about the possibility of a command queue so apart from making a FR for this, I thought I'd share my proof-of-concept code which is working well in my project. The code is not a complete working example, but it shows how it works, in case anyone is interested.
https://ovcollyer-colebrooke.synology.me:5001/d/f/584662710053025875
It's in C++ but maybe if you ever go down this route and produce some kind of sokol_cmdqueue.h it might be of some use.
Basic principle is that the application would create the window/device etc as usual in the main thread, but then create an update/game-logic thread which would create this renderer object. Thereafter, you would add commands to the renderer, and at the end, commit them. This would move them into the commit list, and the main/render thread would then call into the renderer object to execute the commands, with two semaphores used to coordinate things. This part is similar to bgfx.
To deal with things like creating/updating images, buffers, etc, a copy of the data has to be included in the queue system, but since these allocations would often be repeated every frame it caches these blocks and re-uses them, periodically flushing those that haven't been re-used for a while (1000ms).
It can almost certainly be optimised, and probably if @floooh wrote something like this in C it would be way more efficient, but thought I'd share it anyway.
In a proper implementation, maybe things like sokol_imgui, sokol_fontstash etc could have compile-time options to render to a queue, rather than directly otherwise all of that magic wouldn't be taken advantage of. Or some way of making the sg_xxxx() calls resolve to queue functions instead, somehow.
Anyway, I don't know if this is on the roadmap, but thought I'd share this anyway.

The same ideas i looked in rizz.
https://github.com/septag/rizz

So I refined/simplified the concept a little, and made a repo for it.
It no longer deals with copying the memory used for buffers, images etc, instead this is left to the caller to manage with a completion callback called when the memory is finished with. This is more flexible and efficient.
https://github.com/oviano/sokol-multithread

https://github.com/oviano/sokol-multithread

It is very interesting!
I'm having trouble using multithread with Sokol gfx in my project https://github.com/supernovaengine/supernova, but I think I'll use your solution.

https://github.com/oviano/sokol-multithread

It is very interesting! I'm having trouble using multithread with Sokol gfx in my project https://github.com/supernovaengine/supernova, but I think I'll use your solution.

How did you get on with this? The code might need tweaking to work with latest sokol_gfx.h.
Even if you don't use this code specifically, the concept has worked really well for me.

I did some tests and I think I understand now the reason of two semaphores. It is necessary to avoid two or more sequences of (step 3) before (step 6). With two semaphores you garantee the sequence (step 3), (step 6), (step 3), (step 6), etc.
Thanks, your contribuition help me a lot!!

I did some tests and I think I understand now the reason of two semaphores. It is necessary to avoid two or more sequences of (step 3) before (step 6). With two semaphores you garantee the sequence (step 3), (step 6), (step 3), (step 6), etc.
Thanks, your contribuition help me a lot!!

Nice one - your library looks pretty well featured!


panic when killing cluster out of range

Describe the bug
thread 'tokio-runtime-worker' panicked at 'range start index<PHONE_NUMBER>3709551612 out of range for slice of length 0', library/core/src/slice/index.rs:52:5
stack backtrace:

To Reproduce
CI https://github.com/singularity-data/risingwave/actions/runs/2214550489
Expected behavior
No panic when killing
Additional context
No backtrace for this panic, so I guess the issue might relate to something happening in drop functions?

18446744073709551612 =<PHONE_NUMBER>3709551616 - 4
So we are accessing -4?


Guide: how to update BFBridge

Make a new BFBridge release on Github
In camicroscope/image-decoders repository in install_bfbridge.sh, update the version number

moved to wiki


Product check: Improve retry mechanism

This ensures the product check is not flagged wrongfully as successful if the answer has not been properly validated.
The client will retry product check until success or error.

This ensures the product check is not flagged wrongfully as successful if the answer has not been properly validated.

@Anaethelion can you describe how this was happening before? This change seems complicated to me, and I don't understand why it's necessary.


Key 248 and other NoSymbol keys not working

Regression?
Yes
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 918d8340afd652b011b937d29d5eea0be08467f5  (flake.lock: update).
Date: Tue Jun 25 12:06:02 2024
Tag: v0.41.2, commits: 4886

flags: (if any)

System Information:
System name: Linux
Node name: Murmaider
Release: 6.6.35-2-lts
Version: #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 21:05:23 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [Geforce RTX 3070 Ti Laptop GPU] [10de:24a0] (rev a1) (prog-if 00 [VGA controller])
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev c7) (prog-if 00 [VGA controller])

os-release: NAME="EndeavourOS"
PRETTY_NAME="EndeavourOS"
ID="endeavouros"
ID_LIKE="arch"
BUILD_ID="2023.11.17"
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://endeavouros.com"
DOCUMENTATION_URL="https://discovery.endeavouros.com"
SUPPORT_URL="https://forum.endeavouros.com"
BUG_REPORT_URL="https://forum.endeavouros.com/c/general-system/endeavouros-installation"
PRIVACY_POLICY_URL="https://endeavouros.com/privacy-policy-2"
LOGO="endeavouros"

plugins:

Description
this setting bind = , 248, exec, grim -g "$(slurp)" does not work for some mysterious reason (it used to a few versions back so this is some kind of regression), changing the key to a different one works, and reading another key by it's keycode instead of keysym also works, so it's like Hyprland just really does not like this specific keycode.
wev and xev both display the key properly when it's pressed (it's FN+Print on my laptop) but Hyprland will not act on it.
This is on Hyprland 1.41.2-2
On an older version of Hyprland (forgot exactly, but it was new, 1.40 at oldest, possibly as recent as 1.41.1) I was also having an issue where when I pressed this same key, many other keybinds would fire off in hyprland (volume up/down, xf86launch, brightness...) before that version the key worked completely fine on Hyprland and i've been using it for months.
The same keybind also works fine on i3.
From wev:
[14:     wl_keyboard] key: serial: 36238; time: 19877312; key: 248; state: 1 (pressed)
                      sym: NoSymbol     (0), utf8: ''

My haphazard guess would be that this issue might have something to do with the keysym being NoSymbol.
How to reproduce
set bind = , 248, exec, grim -g "$(slurp)" and press that button.

have you tried code:248?

have you tried code:248?

Yeah, made no difference.

I have the same issue with a key after updating to 0.41.0:
bind = , code:197, workspace, e+1
[14:     wl_keyboard] key: serial: 6078; time: 1894859; key: 197; state: 1 (pressed)
                      sym: NoSymbol     (0), utf8: ''

I think the problem is that this key is 'NoSymbol' because as far as I've tested other keys have a symbol. Before it stopped working, sometimes after startup, this key triggered print, which I think was usually after a new update. I had to unbind and rebind print.

Similar problem? fcitx5 shortcut to switch input method sometimes no popup, log as follows.

can someone bisect this?

@vaxerski  I tried to bisect it but couldn't reproduce it in the debug version of the same installed version v0.41.2. I installed git version 4141e6755022edc19cd37cd7ad077a93b3bae5bd and I still have the issue. It's a pain to bisect if I have to install and restart every time.

such is life, but I don't have any way to test this so without a bisect you'll likely not get this fixed (unless you write a patch yourself)

such is life, but I don't have any way to test this so without a bisect you'll likely not get this fixed (unless you write a patch yourself)

Are you sure you don't have any nosymbol key on your keyboard?  Do you have an FN key on it? You can just try holding it and smashing random buttons till you find a nosymbol one.
Alternatively maybe you could use a keystroke generator, you know keycode 248 is one that generates the issue, so something like ydotool might be able to replicate this for you?

@vaxerski I just dug into the code and look what I found!!! Somehow when you install Hyprland, it only runs the following block:
https://github.com/hyprwm/Hyprland/blob/51ffd7fa6f186419276e5d3d5fe141a3fdb3c55c/src/managers/KeybindManager.cpp#L641-L666
[LOG] Key event: KEYCODE = 116, keysym = 65364, internalKeysym = 65364
[LOG] Handling keybind: modmask = 0, keycode = 116, keysym = 65364, keyName = , pressed = false
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] Key event: KEYCODE = 36, keysym = 65293, internalKeysym = 65293
[LOG] Handling keybind: modmask = 0, keycode = 36, keysym = 65293, keyName = , pressed = true
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] Window 62ddac6c1bd0 set title to cat $XDG_RUNTIME_DIR ~
[LOG] Searching for matching rules for Alacritty (title: cat $XDG_RUNTIME_DIR ~)
[LOG] Window rule opacity 0.90 0.90 -> class:Alacritty matched [Window 62ddac6c1bd0: title: "cat $XDG_RUNTIME_DIR ~"]
[LOG] cursorImage request: shape 9 -> text
[hc] getShapesC: found 1 images for text
[ERR] rbo: glCheckFramebufferStatus failed
[LOG] cursorImage request: shape 1 -> default
[hc] getShapesC: found 1 images for default
[ERR] [GLES] Error in call at<EMAIL_ADDRESS>0x502
[ERR] rbo: glCheckFramebufferStatus failed
[LOG] Key event: KEYCODE = 36, keysym = 65293, internalKeysym = 65293
[LOG] Handling keybind: modmask = 0, keycode = 36, keysym = 65293, keyName = , pressed = false
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!
[LOG] oMg such performance hit!!11!

and d1340bd1d8eedd274283e0cb2568a3ed67b58c81 is the reason why NoSymbol keys stopped working.

MRs welcome

Sorry, I'm not a C++/Linux programmer, giving you a hint was the only thing I could do.

@MrYuto does this patch.txt work?

@ikalco Yes, I don't see any issues

can confirm, it's fixed.


How to build this code on windows?

Hi. I need this code to be running on windows.
Would you kindly advise me how I can build on windows ?
Thanks.

Hey you can setup MediaPipe on windows and the rest should be the same
checkout - https://google.github.io/mediapipe/getting_started/install.html#installing-on-windows

On windows or intel machine, you can using openvino toolkit to optimize performace.
https://github.com/nguditi/OpenvinoGoogleMeetVirtualBackground


M1 芯片上无法打开BingGPT

下载的是Apple Silicon的版本，打开之后软件一片空白

Microsoft strengthened the server-side restrictions on IP yesterday. VPN is needed when launching the app if new Bing is not available in your area. You can exit VPN while chatting.

VPN已经开了，也还是显示空白界面。

2023年3月14日 11:29，DICE @.***> 写道：
Microsoft strengthened the server-side restrictions on IP yesterday. VPN is needed when launching the app if new Bing is not available in your area. You can exit VPN while chatting.
—
Reply to this email directly, view it on GitHub https://github.com/dice2o/BingGPT/issues/4#issuecomment-1467296694, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHT3JCDMUXBO2JPUQJQT26TW37QZXANCNFSM6AAAAAAVZ2OGTM.
You are receiving this because you authored the thread.

You can check if bing.com is included in the rules of your VPN. If not, you can use the global mode of your VPN.

Global mode is worked. Thank you!

2023年3月14日 11:44，DICE @.***> 写道：
You can check if bing.com is included in the rules of your VPN. If not, you can use the global mode of your VPN.
—
Reply to this email directly, view it on GitHub https://github.com/dice2o/BingGPT/issues/4#issuecomment-1467306006, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHT3JCD332P4J5VU2JURBWTW37SSPANCNFSM6AAAAAAVZ2OGTM.
You are receiving this because you authored the thread.

很有帮助，

Please can you use the English language ?

最新安装mac打开白屏什么都没有？

Please can you use the English language ?!!!

Hello sir, the MAC m1 chip has been installed, the VPN is enabled globally,
and the screen remains white when opened. Thanks[image: 截屏2023-09-20
00.16.30.png]
foxypiratecove37350 @.***> 于2023年9月17日周日 04:29写道：

Please can you use the English language ?!!!
—
Reply to this email directly, view it on GitHub
https://github.com/dice2o/BingGPT/issues/4#issuecomment-1722309724, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A6TFJMDRHVEP54MLBJSCMODX2YD2LANCNFSM6AAAAAAVZ2OGTM
.
You are receiving this because you commented.Message ID:
@.***>


app crash on iphone 6

opening again and again but not responding and crashing and don’t work.

Only for iPhone X

Hi @Phoenix100, maybe it's not clear, but this app only supports iPhone X.


When declining or merging, no message is sent to a channel about that event

I'm not sure what the Bitbucket equivalent is "closed" status on a PR. But neither decline or merge deliver an event

@DHaussermann, I agree that some events are very noisy and I will fix it, but when you merge a PR and you have the pull_reviews feature enabled, you should see a notification like this:

You didn't see anything like this?

@DHaussermann, I agree that some events are very noisy and I will fix it, but when you merge a PR and you have the pull_reviews feature enabled, you should see a notification like this:

You didn't see anything like this?


bugadd config for Cooldown Job

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.96 seconds
load time: 526 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230128084211_clickbench_pr_85484.html


[GRID] Make it possible to ellipsize long fields  and add a hover tooltip

Provide a general summary of the feature here
We would like it to be possible to ellipsize long fields, and display a hover tooltip with the content. The tooltip should only be shown when the content is ellipsized.
🤔 Expected Behavior?
Ellipsize content when that's preferred
😯 Current Behavior
You cannot ellipsize content. When the content is too long, the content will break into multiple lines.
💁 Possible Solution
No response
🔦 Context
Sometimes the content of a column is not important enough to have the need to be fully shown.
💻 Examples
No response
🧢 Your Product/Team
Magister

This looks like a duplicate of https://github.com/sl-design-system/components/issues/1436 ?

Duplicate


Had to pin dependencies to work with podman build

On the current master branch, before I could successfully getting podman build -t nostr-rs-relay .  to build I had to pin the following dependencies to work with rust 1.68.2:
cargo update -p anstyle-parse --precise 0.2.1
cargo update -p clap --precise 4.3.24
cargo update -p clap_lex --precise 0.5.0
cargo update -p anstyle --precise 1.0.2

Should I do a PR to add these cargo update commands or upgrade the version of rust in the Dockerfile ?

I think your issue is that you need to run podman build --pull -t nostr-rs-relay .; as that will retrieve the latest base image.  You are probably trying a build against an old container image that is using a pre-1.70.0 rustc.

I'm going to update the README to add the --pull flag; this should make it less likely others will run into the same issue.

Thanks! I confirmed your suggestion works for me, I did the below and my relay is up and running fine with no pinned dependencies.
podman build --pull -t nostr-rs-relay .
podman run -it -d --rm -p 8080:8080   --user=100:100   -v $(pwd)/data:/usr/src/app/db:Z   -v $(pwd)/config.toml:/usr/src/app/config.toml:ro,Z   --name nostr-relay nostr-rs-relay:latest


[Feature] Add metafield identifiers to be looked up by tax partner for querying

WHY are these changes introduced?
Add a new field that a tax_calculation extension can set called input.metafield_identifiers which is an object containing a namespace/key pair. The field is intended to be a metafield reference where the partner will store which metafields per merchant they want Shopify to query the value for come tax calculation time to passed back to the app.
Relies on https://github.com/Shopify/shopify/pull/456423 to complete.
WHAT is this pull request doing?
Adding a new tax_calculation extension field called input.metafield_identifiers which will store a namespace/key pair. The pair will be used by Shopify at tax calculation time to lookup metafield values to pass along to the tax partner app.
How to test your changes?

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

/shipit


Show privacy statement on first invocation of ‘az’ command

$ az

Welcome to Azure CLI!
---------------------
Use `az -h` to see available commands or go to https://aka.ms/cli.

Telemetry
---------
The Azure CLI collects usage data in order to improve your experience.
The data is anonymous and does not include commandline argument values.
The data is collected by Microsoft and shared with the community.

You can change your telemetry settings with `az configure`.

     /\
    /  \    _____   _ _ __ ___
   / /\ \  |_  / | | | \'__/ _ \
  / ____ \  / /| |_| | | |  __/
 /_/    \_\/___|\__,_|_|  \___|

Welcome to the cool new Azure CLI!

Here are the base commands:

    account   : Manage subscriptions.
    acr       : Manage Azure container registries.
    acs       : Manage Azure Container Services.
...

A config value is stored like so:
[core]
first_run = yes

cc: @twitchax


chore(lifecycle-operator): remove deprecated fields in KeptnTaskDefinition

Fixes: #3104
Depends on: https://github.com/keptn/lifecycle-toolkit/pull/3344

Did you confirm that https://keptn.sh/stable/docs/reference/crd-reference/taskdefinition/#differences-between-versions is still accurate?  It looks like we didn't tell them that function still actually worked in place of deno so maybe we don't need to say that function is shut down in v2.0?

Did you confirm that https://keptn.sh/stable/docs/reference/crd-reference/taskdefinition/#differences-between-versions is still accurate? It looks like we didn't tell them that function still actually worked in place of deno so maybe we don't need to say that function is shut down in v2.0?

Good point, looking at the page it states that function is deprecated already in 0.8.0 and will be dropped in future releases. I would say this is good enough here.


Cannot read properties of undefined (reading 'replace')

<EMAIL_ADDRESS>injecting env (0) from .env
<EMAIL_ADDRESS>injecting env (0) from .env
2024-07-11 11:08:27,751 ERROR 159528 [swagger-egg] Cannot read properties of undefined (reading 'replace')
2024-07-11 11:08:27,792 INFO 159528 [egg-sequelize](2ms) Executed (default): SELECT 1+1 AS result
2024-07-11 11:08:27,798 INFO 32160 [master] egg started on http://<IP_ADDRESS>:7001 (4578ms)
2024-07-11 11:11:10,935 INFO 32160 [master] master is killed by signal SIGINT, closing

运行中遇到了这个问题，应该怎么debug？

找到问题了，我晚点提个PR吧


Add -K|--skip-dependencies. Fix #49.

Fix #49.

I think the code looks good, and I tested it as far as seeing that the GUI checkbox looks to be working correctly. But I'm wondering if having it in the GUI is unnecessary? This isn't something that will be used in 95% of cases, right? I would vote for it to be a CLI-only option, but since the box is auto-checked unless the option is passed, I'm also okay with it staying in the GUI. I'll leave the final decision up to you.


Document Minimal Java requirements and enforce build requirement

This documents the minimal JDK version in the readme and stops
Maven if the wrong Java version is used.
Thanks to @mauricioaniche for alerting me of this.

Thanks for updating the README and adding the right settings in the pom file. This will be merged onto master


Implement fetch API

When we do this, we can update Babylon.js to use the fetch API instead of XMLHttpRequest. Perhaps even deprecate XMLHttpRequest in this repo.
Note that fetch polyfill with XMLHttpRequest does work.

Deprecating the old and replacing with modern API has my vote. Getting bundle sizes down, and eliminating mixed uses in client code would be the primary forces IMO


Serialization?

Great job with this library!
This is just what I need for an open source project I'm working on, but I need serialization support.
Do you have any plans for that or do you accept PRs?
Thanks

@Performador you write the code and I'll certainly take a look at the PR!
Ideally serialize to an storage abstraction, include units for to/from and aim for high coverage on the tests.
I'm travelling at the moment so may take longer to respond to messages.


Federate edge image list

Initial version for the parity between image builder and edge image list

FYI @mgold1234 @matoval @loadtheaccumulator This is the initial setup for the parity.
@croissanne The feature flag and layout approach is under the other pr's opened by Michal, please let us know if you need any changes on our side

/retest

@croissanne I've addressed some of your comments, and as @mgold1234 mentioned, the other layout changes are on ther pr.
Let us know the better way to proceed

Hmm, that still doesn't have the white background for the tab headers.
Also I think every PR should make sense and work  as a unit. So we can either rebase the other on top of this. Or we can merge them one by one, but both need to be green of course.

@mgold1234 lets rebase our prs and get in one then we can have the complete flow working.
@croissanne the tests that is broken is related to the tab changes we are looking to fix that based on the feature flag.

Closing this pr, once the changes were rebased on #1149


How do I create a desktop application on a Mac?

Hi,
I have created asp.net core 3.1 web application with simple login user functionality. Now I am trying to convert to a desktop application via Electron JS on a Mac machine, but I am getting problems on a build application.
I want to know how to create build via commands for a Mac machine.
I have tried with the solutions below, but no success:
Https://github.com/ElectronNET/Electron.NET#start-the-application
Https://github.com/ElectronNET/Electron.NET/issues/190
Thanks in advance.

Hello,
I have found the solution, I've created a build on the folder path through the terminal by using below commands :
dotnet tool install ElectronNET.CLI -g
electronize init
electronize start
electronize build /target win
Thanks & Regards
Ajay

Hello,
I have found the solution, I've created a build on the folder path through the terminal by using below commands :
dotnet tool install ElectronNET.CLI -g
electronize init
electronize start
electronize build /target win
Thanks & Regards
Ajay


Do we need widget merge_settings?

Why not just use the list of keys in the widget's config before we validate?
If we can do this, that will remove a bunch of lines of code.
If we figure that we do need them, incorporate them into the MPF-side processing of plugin player validation

computer says?
no


Include deps in src artifact hash

Drive-by comment: as you're building an understanding of what this code does, I would appreciate docstrings for any public functions (or all if you want to go so far) that do things that are less than painfully obvious.

I would hope that good docstrings would make the process of getting into this code faster.

@enocom the fn I changed was not public - but perhaps it needs a docstring, too. I'll come back to that.