Memory Usage problem

Hi @anands-repo,
I am running a whole genome variant calling for the HG002 sample from the Truth Challenge V2 with a 35x sample. I have specified 90 threads inside the docker container to be available for the script using this command
docker run --rm    -v "${HELLO_DIR}:/data"    -v "${BAM_DIR}:/data/bamdir"    -v "${REFERENCE_GENOME_DIR}:/data/ref/"    -v "${OUTPUT_DIR}:/data/workdir"    oddjobs/hello_deps python /data/python/call.py    --ibam "/data/bamdir/$(basename "${BAM_FILE}")"    --ref "/data/ref/hs37d5.fa"    --workdir "/data/workdir"    --network "/data/${MODEL_PATH}"    --num_threads ${NUM_THREADS}    --mapq_threshold 5
but I noticed that there was intensive memory usage to the extent that the device went out of memory. I had to run the container with limited memory using the flag -m 80g to restrict the device memory overconsumption by the script, but now the caller is stuck at 99% and is not proceeding. what do you suggest I do ?. I am running a benchmarking analysis with my setup, that has 96 threads and 125 GB of RAM and I have fixed the choice of 90 threads all over the other tools I benchmarking with

Hi,
Could you please try branch devel_bugfix? The new branch (repo) contains
several UX and error handling improvements, however it has a memory issue.
Functionally, both branches should be the same.
I never tried 90 parallel threads. If it still has memory issues, I would
recommend running at 16/32 threads, which is what I probably tried.
Please note that the VCF from devel_bugfix branch has some VCF header
issues. A small fix for the header is at the bottom of the Readme file.
I will revert the default branch in the repository to devel_bugfix as well.
Thanks,
Anand
On Fri, Apr 5, 2024 at 7:32 PM Mahmoud Bassyouni @.***>
wrote:

Hi @anands-repo https://github.com/anands-repo,
I am running a whole genome variant calling for the HG002 sample from the
Truth Challenge V2 with a 35x sample. I have specified 90 threads inside
the docker container to be available for the script using this command
docker run --rm -v "${HELLO_DIR}:/data" -v "${BAM_DIR}:/data/bamdir" -v
"${REFERENCE_GENOME_DIR}:/data/ref/" -v "${OUTPUT_DIR}:/data/workdir"
oddjobs/hello_deps python /data/python/call.py --ibam
"/data/bamdir/$(basename "${BAM_FILE}")" --ref "/data/ref/hs37d5.fa"
--workdir "/data/workdir" --network "/data/${MODEL_PATH}" --num_threads
${NUM_THREADS} --mapq_threshold 5
but I noticed that there were extensive memory usage to the extent that
the device went out of memory. I had to run the container with the limited
memory using the flag of -m 80g to restrict the device memory over
consumption by the script, but now the caller stuck at 99% and is not
proceeding. what do you suggest I Shall do ?. I am running a benchmarking
analysis with my setup that has 96 threads and 125g or RAM and I have fixed
the choice of 90 threads all over the other tools I benchmarking with
—
Reply to this email directly, view it on GitHub
https://github.com/anands-repo/hello/issues/12, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJJMQA3DZ2B2FY5S63VSILY35NDXAVCNFSM6AAAAABF2B5BS2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDSMBTGQZDKNY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,
I have tried the 16 threads and it went fine but used around a peak of 115-120g of RAM which was barely affordable from the devise. However I would use the devel_bugfix branch for these vcf header changes.
Thanks,
Mahmoud Bassyouni
On 8 Apr 2024, at 10:37 PM, anands-repo @.***> wrote:

Hi,
Could you please try branch devel_bugfix? The new branch (repo) contains
several UX and error handling improvements, however it has a memory issue.
Functionally, both branches should be the same.
I never tried 90 parallel threads. If it still has memory issues, I would
recommend running at 16/32 threads, which is what I probably tried.
Please note that the VCF from devel_bugfix branch has some VCF header
issues. A small fix for the header is at the bottom of the Readme file.
I will revert the default branch in the repository to devel_bugfix as well.
Thanks,
Anand
On Fri, Apr 5, 2024 at 7:32 PM Mahmoud Bassyouni @.***>
wrote:

Hi @anands-repo https://github.com/anands-repo,
I am running a whole genome variant calling for the HG002 sample from the
Truth Challenge V2 with a 35x sample. I have specified 90 threads inside
the docker container to be available for the script using this command
docker run --rm -v "${HELLO_DIR}:/data" -v "${BAM_DIR}:/data/bamdir" -v
"${REFERENCE_GENOME_DIR}:/data/ref/" -v "${OUTPUT_DIR}:/data/workdir"
oddjobs/hello_deps python /data/python/call.py --ibam
"/data/bamdir/$(basename "${BAM_FILE}")" --ref "/data/ref/hs37d5.fa"
--workdir "/data/workdir" --network "/data/${MODEL_PATH}" --num_threads
${NUM_THREADS} --mapq_threshold 5
but I noticed that there were extensive memory usage to the extent that
the device went out of memory. I had to run the container with the limited
memory using the flag of -m 80g to restrict the device memory over
consumption by the script, but now the caller stuck at 99% and is not
proceeding. what do you suggest I Shall do ?. I am running a benchmarking
analysis with my setup that has 96 threads and 125g or RAM and I have fixed
the choice of 90 threads all over the other tools I benchmarking with
—
Reply to this email directly, view it on GitHub
https://github.com/anands-repo/hello/issues/12, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJJMQA3DZ2B2FY5S63VSILY35NDXAVCNFSM6AAAAABF2B5BS2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDSMBTGQZDKNY
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/anands-repo/hello/issues/12#issuecomment-2043600468, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD64LANJYHIJESPPST2XZC3Y4L5XJAVCNFSM6AAAAABF2B5BS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGYYDANBWHA.
You are receiving this because you authored the thread.Message ID: @.***>


Fixup/cs/turn defines into enums

This allows for better type checking vs raw integers. Coming from C, hard type checks on enums is a real treat! Note the inclusion of default: cases where previously it was not handled.

@ClutchplateDude Don't merge yet please, I'd like to clean up the commit history

@ClutchplateDude Don't merge yet please, I'd like to clean up the commit history

I can squash and merge if you like,

@ClutchplateDude Don't merge yet please, I'd like to clean up the commit history

I can squash and merge if you like,

No I like to keep the changes in separate commits (esp for simple changes like this). Good to merge whenever :)


ARROW-2759: [Plasma] Export plasma notification socket

https://issues.apache.org/jira/browse/ARROW-2759

Ready to merge. @pcmoritz Can you review this PR?

Ready to merge. The test fail is not because of this PR.


Add rename-command config

@karelrooted And could you supplement some tcl tests

@karelrooted And could you supplement some tcl tests

add a rename one command test,  the current code base will not allow a multi rename-command directive,  so rename-two-command  testcase is not included


useSearchParams uses decoded URI

Describe the bug
The useSearchParams hook's setSearchParams will decode any given URL.
This means that the encoded versions of symbols like ? or # will be decoded upon usage.
Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-y1upyl?file=src/SearchParamIssue.tsx
Steps to Reproduce the Bug or Issue

Go to Stackblitz
Open the issue page
Spectate as the URL changes from %23world to #world

Expected behavior
Expected behavior would be:
Route: /search/0/%23world
setSearchParams( { p: "1" } );
Result: /search/0/%23world?p=1
Actual behavior is:
Route: /search/0/%23world
setSearchParams( { p: "1" } );
Result: /search/0/#world?p=1
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

I believe this was resolved from 0.6.0 onwards (late December).  Does upgrading resolve this for you?

Upgrading did solve my issue. I wonder why my 'npm outdated' didn't catch this one...  Whatever, thanks for the help!


Fix bash_completion double reading bug

$ # When first read, it is no ploblem.
$ . hub/etc/hub.bash_completion.sh
$ hub [tab][tab]
add                  describe             pull-request
alias                diff                 push
am                   difftool             rebase
:
$ # When read again, it is problem.
$ . hub/etc/hub.bash_completion.sh
$ hub [tab]-bash: __git_list_all_commands_without_hub_without_hub: command not found

This pull request correct the problem.

Thanks for the suggestion? But, when is bash completion script read twice?

I'm verry sorry. I found the problem in my bashrc.
I read a local copy of hub.bash_completion.sh, and one more it installed by brew too.

Ok, so if it was a problem with your bashrc, I'm going to close this out.


feat: Ability to Share Service Instances

Purpose
Users now have the flexibility to share their service instances across different environments by modifying the shared parameter within the Service Instance resource schema. This parameter can be adjusted during the instance creation or updated later as per the user's preference.
During both the creation and updating processes of the service instance resource, an extra call is made to the 'btp share' and 'btp unshare' APIs based on the value specified for the 'shared' parameter.
It's crucial for users to ensure that the instances they intend to share are associated with a service plan that supports sharing.
fix #437
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code via automated test

go test ./...

What to Check
Verify that the following are valid:

Automated tests are executed successfully

Other Information

Checklist for reviewer

The following organizational tasks must be completed before merging this PR:

[x] The PR is assigned to the Terraform project and a status is set (typically "in review").
[x] The PR has the matching labels assigned to it.
[x] The PR has a milestone assigned to it.
[x] If the PR closes an issue, the issue is referenced.
[x] Possible follow-up items are created and linked.

Inclusive Language Check failure is accepted as errors occur due to service responses we cannot influence

Sonar Cloud findings are acceptable


Refactor database update to not use a partial data object anymore

Refactor database update to not use a partial data object anymore, full room object will be overwritten instead. Also applied a few minor fixes.

can we update the board in mongoHistoryEndGame to the final masterboard as well by: gameHistory.board = room.masterBoard; So that the status on revealed is accurate.

Ya good idea

Maybe want to check if socket username === input username for join team and randomize team buttons too unless that will be fixed by other things.

I think now that we have the username stored to the socket, we don't need to pass it to any requests except when the user first chooses their username upon joining. Every other function after that can identify the user by their socket username.

I'll work on the username stuff in a separate PR.


Translation to german

Hey,
since I am native german  speaker I could add a german translation for the CyberPop website if that is something you want.

double


Fix dialogue variables not mimicking actual narrative variables

dialogue.variable_storage().variables() will also have declare'd variables as well now.

Eh will look into that test later. And possibly add my own regression one

Idea sounds sound to me. I'll check the PR in detail when you're done :)

Heh I found out why that test was erroring:
        .declare_variable(
            Declaration::new("$external_str", Type::String).with_default_value("Hello"),
        )
        .declare_variable(Declaration::new("$external_int", Type::Boolean).with_default_value(true)) // <--
        .declare_variable(Declaration::new("$external_bool", Type::Number).with_default_value(42)) // <--

I also added a test to validate declared vars are indeed visible ^^
Other CI failures I think are unrelated

@stargazing-dino hehe, that one seems sneaky

Hmm, I'm missing the "merge main branch into this branch" button here and your other PR. Could you merge main so that the CI will be fixed?

should be ready now

Thanks :)


2021 Launch

It's almost December and I have enough head space and free time to relaunch the project this year.
Any help would be appreciated, the majority of work involved is user support and marketing.
Launch tasks:

[x] Run rake task to check status of all existing projects (@andrew)
[x] Scale up heroku dynos (@andrew)
[x] Review current admins and contributors on GitHub (@andrew)
[x] Update sponsors
[x] Update sendgrid config
[x] Update and send November reminder email
[ ] Update featured projects
[ ] Triage existing issues
[ ] Tweet to thank each sponsor

Nice to see this return @andrew! Seems only fitting that it has a little spot on our /explore page 🙂

Published on GitHub's Twitter, Facebook and LinkedIn feeds too 🎉

Thanks so much @leereilly 🎅

Question, there's GitHub Discussions as well as Gitter, are both being used?
Spotted a few small things I can send a PR for on the site contents.

@andypiper said...
Question, there's GitHub Discussions as well as Gitter, are both being used?

GitHub Discussions have only been introduced this year, while GItter has been used in previous years.  I would suggest that we should continue to use Gitter for this year (the traffic there isn't particularly heavy), but begin encouraging people to use Discussions, and then stop using Gitter next year.
Thoughts?

Sounds reasonable. I can do a PR for the site content with relevant links, and will mention Discussions over on Gitter to encourage folks to check that channel out.

I found gitter could get a bit spammy in the past and i like the Discussions is a little more async which is good with everyone spread out in different timezones.


Update Operator API reference

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit ce16b3618da0a3a283da6c92e605cb56e738ff4f
https://deploy-preview-3683--calico.netlify.app

Deploy preview for calico ready!
Built with commit 4bb13c8900baa78e3a33aa2f5f216ed65fd1bfcf
https://deploy-preview-3683--calico.netlify.app


The takeScreenshot API did not achieve its intended effect

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I am developing an app for processing creative programming, and I want to use webview to take screenshots of content as a way to share my work. However, when I took the screenshots, they were ineffective and left blank
Expected Behavior
Can effectively capture screenshots of webview content
Steps with code example to reproduce

Steps with code example to reproduce
class TestScreenShot extends StatefulWidget {
  const TestScreenShot({super.key});

  @override
  State<TestScreenShot> createState() => _TestScreenShotState();
}

class _TestScreenShotState extends State<TestScreenShot> {
  InAppWebViewController? webViewController;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        actions: [
          TextButton(
              onPressed: () {
                webViewController?.takeScreenshot().then((screenshot) async {
                  if (screenshot == null || webViewController == null) {
                    print('data is empty');
                    return;
                  }
                  Directory tempDir = await getTemporaryDirectory();
                  File file = File('${tempDir.path}/screenshot.png');
                  print('path ' + file.path);
                  await file.writeAsBytes(screenshot);
                  showDialog(
                      context: context,
                      builder: (context) {
                        return AlertDialog(
                          content: Image.memory(screenshot),
                        );
                      });
                });
              },
              child: Text('screenShot')),
        ],
      ),
      body: InAppWebView(
        initialUrlRequest: URLRequest(
          url: WebUri("https://processing-30afc.web.app/p5Preview"),
        ),
        onProgressChanged: (InAppWebViewController controller, int progress) {
          if (progress == 100) {
            webViewController = controller;
          }
        },
      ),
    );
  }
}

Stacktrace/Logs

Did I save the image locally while running the screenshot? It was successful
path /data/user/0/com.code.art.show.processing/cache/screenshot.png

Flutter version
3.24.3
Operating System, Device-specific and/or Tool
android,ios,xcode
Plugin version
6.1.5
Additional information
No response
Self grab

[ ] I'm ready to work on this issue!

iOS is working for me. Instead, Android won't work with HTML canvas objects unfortunately.
On Android, you can try to use the controller.evaluateJavascript method and get the image data of the canvas using https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toDataURL javascript API.

Is it possible to use native APIs to take screenshots of your webview instead of finding ways to use JavaScript related APIs

As I said, Android won't work with HTML canvas objects.
I have tried but didn’t found any solution for it.
Android WebView native APIs works but except for canvas elements that remains white.
This is has something to do with the API itself or how the platform manages it.


swift-wala-translator-standalone not running on MacOS

The translator runs successfully but gives no output

@mmroz is that still the case? I thought you fixed that a while back.

Yeah this is closed!


Add DF post

:shipit:

The word "quite" is used 7 times in the blog post.
I think that this could be reduced :smiling_imp:
Great blog post, very interesting read, good pacing, good humor.
A++++ would read again.


Configurable distribution repository URL for Gradle wrapper download

Expected Behavior
I want to override the repository url for the gradle wrapper task with my custom repository URL, so that the wrapper config generated uses my mirror instead of the official distribution point.
wrapper {
  repositoryUrl = "https://my-private.mirror.org/gradle-distributions"
}

If I want to update gradle wrapper to a new version, I want the following command to use the repo I have specified above.
./gradlew wrapper --gradle-version 4.5

Current Behavior
I can only override the entire distributionUrl:
wrapper {
  distributionUrl = 'https://my-private.mirror.org/gradle-distributions/gradle-4.4.1-bin.zip'
}

This means I cannot upgrade my gradle wrapper config pointing to my custom site with the following command:
./gradlew wrapper --gradle-version 4.5

Context

I want to mirror gradle distributions in-house at our company to reduce outbound network traffic, but also make upgrading gradle wrapper as simple as if I were using services.gradle.org.

Steps to Reproduce (for bugs)

Your Environment

Build scan URL:

"gradle init" also destroys an existing url and enters an unreachable default URL in an enterprise setting.

Is there an example of the Provider infrastructure that would teach me how to add a system property such as gradle.wrapperRepository which, when set, would replace the hard code string value in DistributionLocator.java?

It looks like this was added in version 8.2: https://github.com/gradle/gradle/commit/a6313ff9592aed71bb34694a9f03e9d37dcdc777#diff-9b13417b3301e94644ac049b22a8a6b0056a6597d10167e756580c5ee5934c7e
You can now set this in your gradle.properties file in order to set the base url:
systemProp.org.gradle.internal.services.base.url=https\://my-artifactory-server.local/services-gradle-remote

The configured URL should proxy/mirror https://services.gradle.org. I'm sure the fact that the property is on an internal package means that it's not officially stable, but I'm happy to take it. It would be nice to stabilise this as a documented property!


Avoid using nixpkgs in overlay

This is just an idea to remove the dependency on nixpkgs and maybe solve the issues with glibc mentioned in #20  .
I didn't encounter any issues so far, but I don't have a lot of experience with this so maybe there are other issues.

Ah! I've been able to trigger a glibc recompilation too -_-
So it doesn't solve that!

Thanks.


fix: warning by gesture handler

Fixes: https://github.com/gunnartorfis/sonner-native/issues/44

Awesome, thanks for the contribution @matinzd! 👏


add now_or_never

this has stopped me from using futures-lite a couple of times now. incredibly useful function.

It currently exists as futures_lite::future::poll_once, although it's not a method like .now_or_never().

No, that's not the same. It requires you to construct a waker, and if you look at the futures NoopWaker it's about 200loc.

Oh, sorry, I didn't realize. But it can still be useful when you are already in an async context, which is often the case.


DocBlock Parsing Causes Failure to Build extension

Versions
Zephir: 0.9.11-534bd284df
Zephir-Parser: 1.0.3
Sample
https://github.com/ninjapanzer/zephir_docblock_parse_failure_example
Expected behavior
Docblocks like
/**
 * DocBlockFail
 *
 * @author Paul Scarrone<EMAIL_ADDRESS> */

Will be parsed as is into the translated C files
Actual behavior
$ sudo zephir build
Compiling...
Installing...
Zephir\CompilerException: Internal extension compilation failed. Check compile-errors.log for more information

With the actual error being:
/Users/paulscoder/personalrepos/docblockfail/ext/docblockfail/docblocktest.zep.c:20:4: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
 * DocBlockFail
   ^
/Users/paulscoder/personalrepos/docblockfail/ext/docblockfail/docblocktest.zep.c:20:16: error: expected ';' after top level declarator
 * DocBlockFail
               ^
               ;
1 warning and 1 error generated.
make: *** [docblockfail/docblocktest.lo] Error 1
/Users/paulscoder/personalrepos/docblockfail/ext/docblockfail/docblocktest.zep.c:20:4: warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
 * DocBlockFail
   ^
/Users/paulscoder/personalrepos/docblockfail/ext/docblockfail/docblocktest.zep.c:20:16: error: expected ';' after top level declarator
 * DocBlockFail
               ^
               ;
1 warning and 1 error generated.
make: *** [docblockfail/docblocktest.lo] Error 1

@ninjapanzer Could you please provide compiler version?

I'm closing this issue due to the lack of any reaction. I'll open it again if the need arises


add libopus-android-armv7 to opus

add libopus-android-armv7 to opus

Thank you for your contribution!
Please update https://github.com/pion/mediadevices/tree/master/dockerfiles and https://github.com/pion/mediadevices/blob/master/Makefile to make library building process reproducible.

This dockerfile is only useful to opus because openh264 must need NDK to build.

@at-wat I'm used v4 webrtc and update  v3 to v4 change too much files. so i close it.


controlProperties not supported

When parsing and writing a xlsm file containing a button to trigger a macro, the written xlsm file opens with an error basically saying that the file is corrupt.
I noticed that the [Content_Types].xml file was missing the following line:
<Override PartName="/xl/ctrlProps/ctrlProp1.xml" ContentType="application/vnd.ms-excel.controlproperties+xml"/>

I could fix this by adding the CONTENT_TYPE constant in storage.rb
  class ControlPropertiesFile < GenericStorageObject
    CONTENT_TYPE = 'application/vnd.ms-excel.controlproperties+xml'
    REL_TYPE     = 'http://schemas.openxmlformats.org/officeDocument/2006/relationships/ctrlProp'
  end

I assume that this was intentionally left out to not make it ms-excel specific, but maybe it could be an option...
BTW, cool gem!

Thanks! And no, it was not intentionally left out, it was just overlooked, and somewhat undertested as Excel has so many various features, and having everything work would be like re-writing the entire Excel!


⚠ Bofrost.be has degraded performance

In 6a57064, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2708 ms

Resolved: Bofrost.be performance has improved in 4874728.


Add MinIO recipe

I can't get it working to access MinIO console via subpath, e.g. https://omv7box.local:8443/minio, even when MINIO_BROWSER_REDIRECT_URL and MINIO_BROWSER_CONTENT_SECURITY_POLICY are set. Any help is welcome to get it running behind the Traefik reverse proxy.

looks like it is not supported by minio:
https://github.com/minio/minio/issues/5947#issuecomment-415342037


upstream: don't require source_address in upstream_bind_config

Signed-off-by: Greg Greenway<EMAIL_ADDRESS>
Commit Message: This allows setting socket options without specifying an address to bind for upstream connections.
Additional Description:
Risk Level: Low
Testing: Added unit tests. Interestingly, there were already other unit tests for this, which were generating invalid config by not setting the source_address, but the unit tests didn't go through proto validation so they worked.
Docs Changes: none
Release Notes: added
Platform Specific Features: none
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest


Userscript parser error

At this moment @resource row can't contain \t as separator, only space
Test source:
Bilibili Fixer - Perfect!.user.js.zip

core/pull-requests/1487


Content edit of css-tricks.md

There should be no change of meaning.

Changing "Framing Protections" to "XFO" in the table makes it inconstant with other pages such as https://xsleaks.dev/docs/attacks/xs-search/#defense and https://xsleaks.dev/docs/attacks/navigations/#defense

Fair enough.  I've added a link to "XFO" then, in case readers (like me) don't know the abbreviation.

"Pixel Perfect Timing Attacks with HTML5" link results in a 404.
Maybe https://www.youtube.com/watch?v=KcOQfYlyIqw or https://owasp.org/www-pdf-archive/HackPra_Allstars-Browser_Timing_Attacks_-_Paul_Stone.pdf
Not due to this change but may as well get fixed :)

Sounds like a good additional PR :)


fix(@schematics/angular): disable v10 side effect package.json migration

Please remove / disable this test:
https://github.com/angular/angular-cli/blob/88d0eaf885c6a055cf601b11c6190072031bf000/packages/schematics/angular/migrations/update-10/side-effects-package-json_spec.ts#L53-L58

Also merged to 10.0.x patch branch.


Cypress test. Login to task if logout from task.

Cypress test. Login to task if logout from task.
Add cssSelector for element.
Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage increased (+0.4%) to 62.198% when pulling 9d82bb43f1ab6872e3743362513f05233ef9e89b on DmitriyOparin:upstream/do/cypress_test_pr_2527_login_to_task_if_logout_from_task into 565020cce20c291843232e0c84b2dba4ac01a1c7 on openvinotoolkit:develop.


Exporter

Design and implement component that will take all data for a given collection and prepares yearly dumps and one full dump which we will offer for download from the Data access section
Dumps will be new line delimited files. One compiled release per one line so that user can process the file line by line.
Let's have two level directory structure

create one directory per one collection (data source)
and one subdirectory per each job for which we create the dumps.

full and annual dumps exporter implemented

done for now refactor and improvements will be needed when integration with flatten tool is agreed. But I'll start a new issue for this.


additional Arg to start tmux session directly without fuzzy finder window?

Hej! I've been using tms for quite awhile. But one feature that am missing/do not know how to execute is how to open a project given an arg- "path to dir" for making automated scripts. I guess one workaround would be to manually create a tmux session with the proper name? But if tms already does that then it seems like a "dirty fix". At a time my rust skills were beginner like, but now I might at least try to implement that additional argument for tms. Wanted to get insights from the dev himself on possible issues/ and or why it's not a feature of tms?

I hadn't implemented it because I didn't see a strong use case for it and It seemed like it would be a pain to enter manually.
What sort of scripts are you wanting to write?

It would indeed be inpractical to enter manually.
Lately I got tired of creating new project dirs and setup code git init etc. Like cargo has new command but say python does not. Am working in project structure dev/type/lang where type is e.g. personal or work & lang e.g. rust, python, C. Every single project has a specific structure license, .gitignore readme src tests etc. script that am building would wrap around other tools like cargo new, custom for python, custom for C.
So the idea is to have a cli script where user could pass in new --type personal --lang py project_name. And that would create project structure in the dir: dev/personal/python/project_name. Then if I could chain in tms then it would also start a new tmux session. This workflow is quite specific but i got tired of doing it all manually tbh.
As well as if tms would have that option I could create keyboard shortcuts for dwm to start/attach to frequently used projects.
I looked briefly around the source code and tbh I have not a clear plan on how this functionality could be implemented. As I said am still quite new to Rust.

This could also be done with vanilla tmux: tmux new-session -s $SESSION_NAME -c $PATH
Or if you only have the path, then tmux new-session -s $PATH -c $PATH

Hmm I don't think that tms would be a good fit for initializing projects. As an example I have a little bash script that I use to create new projects that creates the project and then opens the project using tmux directly.
I think tms is really more for opening and finding projects and some helpers with git and tmux.
I think the problem your describing would be more elegantly solved with a bash script

Tms in this scenario would not actually intiliase a project. It would simply start the session for the newly created project but within a script.
But I heard you all. Gonna add that step with vanilla tmux. Thought was that with tms it would simplify the process as only a single path would be passed to the tms- in the same way as you would chose a session with fuzzy finder but programatically. But if this functionality within tms would use more setup than using vanilla tmux commands then it's not worth the effort. Thanks 😄

Going to contribute as this is not a closed issue
This was also something I was looking for. I assumed that it would be a feature of this project as it's based on Primagens tmux-sessionizer and supported in that script.
I'm also jumping constantly between a few active projects and being able to wire them up as is done here in Primagens tmux.conf would be incredibly useful.
Thanks for everyone's work on this by the way. Aside from this small issues I've been enjoying it so far 🙂


Remove unused dependencies before saving cache

Every time cargo-cache falls back on an older cache, it may pull in cargo cache files that are no longer needed, e.g. for an older version of a dependency after a cargo update. The stale cargo cache files get mixed in with the fresh cargo cache files produced by cargo during the workflow job, which progressively balloons the cache size each time this happens (until the next Rust update comes along and all the caches automatically reset because they can't fall back).
Increasing cache size means increasing download and upload time, and quickly running out of the 10GB cache storage space provided by GitHub. A user would have to recognize that this issue is occurring and know to manually delete all the caches periodically to work around this.
This was mitigated for a particularly bad case in https://github.com/Leafwing-Studios/cargo-cache/issues/22, but the root cause has not yet been fixed.
The ideal solution would be to fall back on an older cache, run the workflow job, then delete any cargo cache files that went unused during the workflow job before saving the cache.
There's an unstable cargo feature that may help with this: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#manual-garbage-collection-with-cargo-clean.

I'm not sure if this can easily be integrated in this action.
Ideally, this would need to run in a post step, at the end of the workflow.
But the current composite action format we use doesn't allow to define custom post actions, AFAIK.
To support this we would probably need to implement a fully custom action, which would give us more flexibility, but also increase complexity (and make it harder to audit the action).
On the bright side: This feature doesn't require direct support from our action.
In theory you can manually configure a step at the end of your job to run this command, and it will reduce the cache size.
Perhaps we can prototype how this would influence the cache size in bevy_quickstart or some other repository :)

Hey, look! I can contribute to this conversation!
Today I've been working on cargo-sweep, an action that integrates with cargo-sweep. I've been using it to automatically delete files that haven't been accessed in the workflow.

Hey, look! I can contribute to this conversation!
Today I've been working on cargo-sweep, an action that integrates with cargo-sweep. I've been using it to automatically delete files that haven't been accessed in the workflow. It does exactly as @TimJentzsch mentioned, and is pretty effective from my testing.

This is interesting. Since it runs in a post step, we could integrage it directly into cargo-cache, probably with an option to disable it.
Still makes it difficult to audit (an additional action and a cargo binary), but might be worth it to make the caching more effective

I released cargo-cache as v1.0.0 and am willing to maintain it, would you all be interested in integrating it with this action?

I think it makes sense. i'd do it like this:

Opt-out in cargo-cache v3
Installs to separate directory (not target)
Installation saved in separate cache with its own cache key

Installs to separate directory (not target)

I'm good with all those points, but where do you suggest it be installed instead?

Installs to separate directory (not target)

I'm good with all those points, but where do you suggest it be installed instead?

Where exactly doesnt really matter, but it would enable use of a separate cache :)
Of course Im not sure how difficult it would be to generate the cache key for it to work correctly...

Maybe it can be an optional parameter to your action.
Also, isnt the default installation path somewhere in ~/.cargo? Maybe we can leverage that

Closed by #28.


Add a Gitter chat badge to README.md

OryxProject/oryx now has a Chat Room on Gitter
@smarthi has just created a chat room. You can visit it here: https://gitter.im/OryxProject/oryx.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Closing this PR, was a mistake


zsh install support

add path to .zprofile
add a test for zsh

Thanks for the PR, we should definitely start improving the experience for more different shells.
However, I think we should always add to .profile regardless, and also add to shell-specific files if we think that shell will be used. For zsh, a good heuristic might be whether ~/.zprofile already exists, or whether SHELL is set to zsh as you are checking here.

I like @Diggsey's suggestions here. In general, I think the surest way we're going to be able to reliably set PATH is by pessimistically configuring in multiple places on Unix.

I'll update soon, thanks.

@bors r+ Thanks!

:pushpin: Commit 9a9abe1 has been approved by Diggsey

:hourglass: Testing commit 9a9abe1 with merge 68848c9...

:sunny: Test successful - status-appveyor, status-travis
Approved by: Diggsey
Pushing 68848c986ea832e4ca43f153d959cc2345638792 to master...


How highlighting works?

I am unable to figure out how element highlighting is working. I commented out all implementation of HighlightPath() and NativeMethods.HighlightCachedUI(). Still, It's highlighting. Can anyone help me out here?

which version of WAD are you using can you share the code for highlighting.

Hi anunay1, Thanks for responding.
Although I found out how it's highlighting. It was getting highlighted from uixpathlib.dll. I was looking into the managed code eventually I found out

@luvukr Can you please share how did you manage to highlight the elements, as I am unable to do so, also it will be helpful for others.


Security -  Update pepkong plugin to support Keycloak

[ ] Rebuild schema
[ ] Extract token_endpoint from iss claim


Removing 'Options' from the 'ConfigureRouteOptions' extension method name.

https://github.com/aspnet/Mvc/issues/2169

:shipit: but check to see if MusicStore and other repos need to react to this and the MVC update

Hmmm, MusicStore doesn't seem to use it. Let me check other repos..

:shipit:


Prediction is from the untrained model

in the testing phase, run_bert currently loads the base model instead of the checkpoint. This line should be changed to
model = BertForMultiLable.from_pretrained(config['checkpoint_dir'], num_labels=len(label_list))
for testing.

Thank you @Josh1108  for pointing it out.
By default, it is set to run the test on the pre-trained model weighs. For checkpoints, it could be configured with "checkpoint_dir".
In the recent commit, an additional "test_path" argument is added to specify the weights for testing.


Please clarify github.com/gflags/python-gflags

I found what looks like an out-of-date version of this repository at github.com/gflags/python-gflags. That repository is linked to by https://code.google.com/archive/p/python-gflags/, so I thought it was the official repository for quite a while. If that repository is owned by the same people as this one, please consider either removing it from github (ideally) or adding a note to the README file there that this repository is kept up-to-date.
If possible, it would also be great to update https://code.google.com/archive/p/python-gflags/, but less important.

@noahl Can you please click "Close" on this issue?

Yes, I see the fix. Thank you!


Connection resiliency required when using Azure SQL database

Describe the bug
The CustomerSite (& AdminSite) is unable to recover from a transient failure when connecting to the backing Azure SQL database.
To Reproduce
Steps to reproduce the behavior:

Implement Azure Application Insights logging for the CustomerSite (and AdminSite)
...and wait until a transient failure eventually occurs.

Expected behavior
Microsoft.Data.SqlClient.SqlException should not occur due to transient (connection) failures (see log excerpt below).
RESOLUTION: Implement the fix recommended in Microsoft's Connection Resiliency article.
In the AdminSite/Startup.cs file, change the UseSqlServer() line of code from:
services.AddDbContext<SaasKitContext>(options => options.UseSqlServer(this.Configuration.GetConnectionString("DefaultConnection")));
...to:
services.AddDbContext<SaasKitContext>(options => options.UseSqlServer(this.Configuration.GetConnectionString("DefaultConnection"), providerOptions => providerOptions.EnableRetryOnFailure()));
In the CustomerSite/Startup.cs file, change the UseSqlServer() line of code from:
services.AddDbContext<SaasKitContext>(options => options.UseSqlServer(this.Configuration.GetConnectionString("DefaultConnection")));
...to:
services.AddDbContext<SaasKitContext>(options => options.UseSqlServer(this.Configuration.GetConnectionString("DefaultConnection"), providerOptions => providerOptions.EnableRetryOnFailure()));
In the MeteredTriggerJob/Program.cs file, change the UseSqlServer() line of code from:
.AddDbContext<SaasKitContext>(options => options.UseSqlServer(configuration.GetConnectionString("DefaultConnection")))
...to:
.AddDbContext<SaasKitContext>(options => options.UseSqlServer(configuration.GetConnectionString("DefaultConnection"), providerOptions => providerOptions.EnableRetryOnFailure()))
Screenshots
Application Insights log excerpt:
An exception occurred while iterating over the results of a query for context type 'Marketplace.SaaS.Accelerator.DataAccess.Context.SaasKitContext'.
System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure' to the 'UseSqlServer' call.
---> Microsoft.Data.SqlClient.SqlException (0x80131904): Database '<database-name>' on server '<sql-server-name>' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '<guid>'.

Environment (please complete the following information):

Are you using the CloudShell? No
If not using the CloudShell:

OS: Windows 11 Pro
PowerShell version: 5.1.22621.963
Modules installed: Azure Application Insights implemented with the SaaSAccelerator CustomerSite (also, the AdminSite)

Additional context
For additional context, see Microsoft's Connection Resiliency article.

@santhoshb-msft We seem to be experiencing the same and this is flagged in a review since the error message is leaking a lot of debug data. Is there a way in the Web App to disable the verbose error message that appears when there is an SQL issue (like 0x80131904).


Reorg packages

Bring a bit more order into the package hierarchy:

Object
OId Package
Suggested New Package

zcl_abapgit_login_manager
UTILS
HTTP

zcl_abapgit_url
UTILS
HTTP

zcl_abapgit_field_rules
OBJECTS
OBJECTS_RULES

zif_abapgit_field_rules
OBJECTS
OBJECTS_RULES

zcl_abapgit_adt_link
UTILS
OBJECTS_JUMP

zcl_abapgit_gui_jumper
OBJECTS_CORE
OBJECTS_JUMP

zif_abapgit_gui_jumper
UI
OBJECTS_JUMP

zcl_abapgit_exit
ROOT
EXIT

zif_abapgit_exit
ROOT
EXIT

zcl_abapgit_stage
ROOT
STAGE

zcl_abapgit_stage_logic
ROOT
STAGE

zif_abapgit_stage_logic
ROOT
STAGE

zcl_abapgit_merge
ROOT
STAGE

zif_abapgit_merge
ROOT
STAGE

zcl_abapgit_news
ROOT
UTILS

zcl_abapgit_version
ROOT
UTILS

some better org of UI package which has too many classes

👍

Imho:

zcl_abapgit_version is an util, it is not UI but actually a backend logic, doesn't touch user directly
EXIT :+1:
also news class is not UI either, it is parser. Maybe also an util ...
UI package - yeah ... certainly needs some order. Here are some thoughts

core is abapgit agnostic, and I'd suggest keeping it this way and actually change nothing there
then, based on core there are some high level components, which are rendering related, maybe I'd call it UI_LIB

ex_viewer, buttons, chunk_lib (OMG this also should be cleaned up... :), component, hotkey_ctl, all HTML* classes, log_viwer, maybe somethign else

then, there are routing stuff: UI_ROUTING ?

router and service classes

then obviously pages: UI_PAGES ?
then some classes will probably stay in the root, because they do not match the categories above: factory, injector, popups (?), passdialog, frontends services

something like this

#5945 for my comment

👍  for the UI changes. changed news + version to utils


Retrofill UA only if the user agent is Chrome

Actual Behavior
Several bots / spiders likely use Chromium based browsers for automated web requests. Such agents right now identify themselves by modifying the User-Agent header. When client hints are introduced and a client side JS adopts uach-retrofill the automated requests from such user agents will contain Chrome User-Agent instead of the UA string of the bot / spider.
Expected Behavior
Websites should continue to be able to identify bots using User-Agent even after using uach-retrofill.
Suggested Change
Verify that navigator.userAgent identifies itself as Chrome before filling navigator.userAgent with a string constructed from client hints.

This won't be bulletproof, because bots can be clever, but it does make sense at least until more browsers are shipping this API.

I was not thinking of malicious bots when referring to bots. I was referring to well behaved bots which identify themselves accurately by setting the User-Agent header.
https://www.iab.com/guidelines/iab-abc-international-spiders-bots-list/ provides the list of such bots.


Feature Request: Extend generate_tests method to support folder paths

The current generate_tests method in the UnitTestGenerator class only accepts a single file path. This request proposes extending the method to accept a folder path, allowing it to generate tests for all files within the directory.
Triage needed

Would love this feature, do you want to add it or I can do it?

I'll be happy to work on it

Okay, I should be available for the next few hours if you have any doubts!


[ADD] Kosovo

Hello,
I noticed the Kosovo was missing from the countries, so I added it, using https://emojipedia.org/flag-for-kosovo/ as a reference for the data.
Let me know if that's okay.
Thanks.

Missed the other PR, closing.


Small update to incorporate MN location

Just a small edit to get MN location to work for distributed cases

These changes were added to another pull request that was merged with dev/refactor today. #210


Usage with themes

Hi there, great plugin. Only issue I've run into is that I have to jump through a few hoops to get it to work with styled components themes since they require some type composition using the & operator. This means wrapping the ES6 string template in a function which seems to break the plugin's syntax highlighting.
Take the following example where Spinner gets syntax highlighting properly but Spinner2 does not:
import themed, { withProps, keyframes } from './themed-components';

interface IProps {
  active?: boolean;
}

// Any html styled components can go here
// Req'd due to:
const styled = {
  div: withProps<IProps>()(themed.div)
};

// take a type and a string, return a styled component

export const Rotate360 = keyframes`
  0% {
    transform: rotate(0deg);
  }

  100% {
    transform: rotate(360deg);
  }
`;

export const Spinner = styled.div`
  animation: ${Rotate360} 1.1s infinite linear;
  border-color: ${props => props.theme.color.blue400} ${props =>
  props.theme.color.blue400} ${props => props.theme.color.blue400} ${props =>
  props.theme.color.blue200};
  border-radius: 50%;
  border-style: solid;
  border-width: 1.1em;
  display: inline-block;
  font-size: 10px;
  height: 10em;
  margin: 60px auto;
  overflow: hidden;
  position: relative;
  text-indent: -9999px;
  transform: translateZ(0);
  width: 10em;
`;

export const Spinner2 = withProps<IProps>()(themed.div)`
animation: ${Rotate360} 1.1s infinite linear;
border-color: ${props => props.theme.color.blue400} ${props =>
props.theme.color.blue400} ${props => props.theme.color.blue400} ${props =>
props.theme.color.blue200};
border-radius: 50%;
border-style: solid;
border-width: 1.1em;
display: inline-block;
font-size: 10px;
height: 10em;
margin: 60px auto;
overflow: hidden;
position: relative;
text-indent: -9999px;
transform: translateZ(0);
width: 10em;
`;

themed-components looks like this:
import * as styledComponents from 'styled-components';

import { ThemedStyledComponentsModule } from 'styled-components';
import { ThemedStyledFunction } from 'styled-components';

import { ITheme } from './theme/standard';

function withProps<U>() {
    return <P,T,O>(
        fn: ThemedStyledFunction<P, T, O>
    ): ThemedStyledFunction<P & U, T, O & U> => fn
}

const {
  default: styled,
  css,
  injectGlobal,
  keyframes,
  ThemeProvider,
  withTheme,
} = styledComponents as ThemedStyledComponentsModule<ITheme>;

export {
  css,
  injectGlobal,
  keyframes,
  ThemeProvider,
  withProps,
  ITheme,
  withTheme,
};
export default styled;

Effectively I am just wrapping styled-components in themed-components so that I can provide a theme using ThemeProvider.  It actually works really well but there is one caveat, the vs code plugin requires that I have this broken out in my file because it seems not to like composition around the styled template tag:
const styled = {
  div: withProps<IProps>()(themed.div)
};

If I try to inline those lines in the string template like in Spinner2 then css formatting is gone. It seems like it really wants styled.div syntax right by the template syntax.

Yes it looks like even after configuring withProps as a valid tag, we do not show intellisense in the string:
{
    "compilerOptions": {
        "module": "commonjs",
        "target": "ES6",
        "plugins": [
            {"name": "typescript-styled-plugin", "tags": ["styled", "withProps"]}
        ]
    },
    "exclude": [
        "node_modules",
        "**/node_modules/*"
    ]
}

Fixed as part of #56 I believe. You still have to configure tags but intellisense should now work after that


Hristov & .60 changes - Hristov Rework, Part 2

About the PR

This PR focuses on a few different changes to Hristov that are intended to rework the weapon into a formidable sniper rifle, including object penetration and damage changes. This is part 2 of a two-part Hristov rework; part 1 #31626 focuses on extending the gun's range.
This PR implements the following:

The Hristov is now a wield-to-fire weapon.
While being wielded, the wielder gets a 75% speed penalty.
The Hristov takes 2.5 seconds to chamber a round; this delay is also applied when first wielding it.
.60 Anti-Materiel bullets now deal:

75 Piercing Damage
150 Structural Damage
60 Stamina Damage

.60 Anti-Materiel bullets now have the ability to penetrate structures, up to a threshold of 360 damage.

The way this is calculated is that the bullet checks the damage required to break the entity it has hit, and if the bullet has dealt a combined damage under the threshold and the bullet damage itself is enough to break the object, it will continue.
If an entity is missing the ability to take Structural damage, the bullet will stop. This keeps the bullet from penetrating mobs (it's far too powerful for that).

Why / Balance

The Hristov rework is split up in two parts as they implement different features and it would be fairly overwhelming to do both at once. The two parts are also fairly disconnected from each other codewise, so it's easier to implement.
The combined changes in this PR turns the Hristov into a powerful sniper that requires planning to use optimally. The requirement to wield and the long chamber time keeps its DPS down, and it becomes a poor choice for a run-and-gun situation due to the extreme movement speed slowdown. To balance this out the damage rewards landing your shots, and the gun gives you unique tools to let you do that.
The anti-materiel bullets are tweaked such that they are able to penetrate weak structural objects like windows and grilles, but stop at walls. Since fights in groups in long hallways aren't uncommon and damage dealt by the bullets is high, they've been made to not penetrate mobs, making them more effective at single-target elimination. As an added bonus for any entrepreneuring sniper it also features heavy stamina damage; the 60 stamina damage of the first shot is enough to allow a brief moment of slowdown that the sniper is able to capitalize in for one shot, and if hit again the target will be knocked down. The damage is tweaked such that an officer or Captain is able to take 3 hits before being crit, while an unarmored target takes only 2. While the burst damage is strong, the slow reload causes a Time-To-Crit that is comparable to the high-tier lasers such as the laser cannon or advanced laser pistol.
Please consider these changes in the context of Part 1 of the Hristov Rework as well, since the extended range is key to utilizing the Hristov effectively.
For comparison, here is how the new Hristov (12 TC purchase) stacks up against the C20-r (20 TC purchase), the Viper (3 TC purchase) and the Python (8 TC purchase):

Technical details

There are two main components to this PR:
The first is the new property in ProjectileComponent, PenetrationThreshold, which is used in ProjectileSystem to determine if a bullet should penetrate an entity or not.
The second is the SpeedModifiedOnWieldComponent, which is used in WieldableSystem to set the movement speed slowdown.
Media

Youtube video link:

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: .60 anti-materiel bullets now deal a lot more damage and are able to penetrate weak structures.
tweak: Hristov now requires wielding to fire, and slows you down considerably.

so based

Wait c20 is 20tc since when

It isn’t, just checked

Wait c20 is 20tc since when

Oop, miswrote.

holy based

No rework .60 ammo?

Can we make AP .60 rounds which can penetrate whole station like Immovable Rod or like AP rounds in SS13. That AP bullet must be deleted only if hit Human.


[DOC] Move forecasting notebooks

Reference Issues/PRs
part of https://github.com/aeon-toolkit/aeon/issues/507
What does this implement/fix? Explain your changes.
moves forecasting notebooks into their own dir, renames them to remove bizarre prefixes and adds an image for proabilistic. No content changed at all

May be other concerns by @ltsaprounis and @aiwalter, but i think the only potential issue with this move is that I cant see any change to the usage of the glocal_fc folder and some of the images. Either they are unused or the path to use them has not been updated.

How did Markus get pinged as a code owner 🤔

How did Markus get pinged as a code owner 🤔

codeowners I guess, will give it a tidy up soon

I'd not looked at the user guide at all, will update it now


Syz-manager panic after adding new IOCTL

I am seeing syz-manager panic immediately  while launching. I just added new IOCTL and followed procedure(syz-extract and make generate). which got success. and did a clean build.
https://android.googlesource.com/platform/hardware/qcom/msm8960/+/76de202d7eae6422d5bcba124734a96b8b6b1b01/original-kernel-headers/linux/msm_mdp.h#70
go version go1.8 linux/amd64
goroutine 1 [running]:
panic(0x12444c0, 0xc4204773b0)
/local/mnt/workspace2/go/src/runtime/panic.go:500 +0x1a1
github.com/google/syzkaller/sys.ForeachType.func1(0x0, 0x0)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:591
+0x284
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60d00, 0xc4202c9840)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:569
+0x53f
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60e00, 0xc420143620)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:578
+0x492
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60e80, 0xc4201497c0)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:586
+0x20b
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60e00, 0xc420153b60)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:578
+0x492
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60e80, 0xc4201496d0)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:586
+0x20b
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60e00, 0xc42015bbc0)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:578
+0x492
github.com/google/syzkaller/sys.ForeachType.func1(0x1a60d00, 0xc42020c740)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:569
+0x53f
github.com/google/syzkaller/sys.ForeachType(0xc42020a780, 0xc420117930)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:595
+0x12f
github.com/google/syzkaller/sys.resourceCtors(0xc4200187c0, 0x4, 0x4,
0xc4204aec00, 0xc42014a360, 0xc4201be301, 0xc4201baf10)
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:462
+0xf1
github.com/google/syzkaller/sys.initResources()
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:442
+0xbf
github.com/google/syzkaller/sys.init.1()
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/decl.go:610
+0x30
github.com/google/syzkaller/sys.init()
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/sys/sys_amd64.go:32382
+0xacb4a
github.com/google/syzkaller/prog.init()
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/prog/validation.go:227
+0x33
main.init()
/local/mnt/workspace2/syzkaller-02202017/src/github.com/google/syzkaller/syz-manager/persistent.go:134
+0xa3

Any pointers to fix the issue either from generating descriptions correctly or any missing step causing the issue.

Looking at the stack trace by itself I'm not sure what the problem might be.
You can try to minimize the descriptions you added until you figure out which part causes the crash. Maybe then you'll be able to understand what's wrong.
Or you can provide exact steps to reproduce the problem so we could take a look.

Here is the IOCTL descriptor http://dpaste.com/24JJ8JV
the panic is seen if i include 'MSMFB_MDP_PP'. Removing this is working fine.
The IOCTL information can be get from https://android.googlesource.com/platform/hardware/qcom/msm8960/+/76de202d7eae6422d5bcba124734a96b8b6b1b01/original-kernel-headers/linux/msm_mdp.h#70
Let me know any more information is needed.

Tried to apply descriptions from http://dpaste.com/24JJ8JV, but they don't compile:
struct 'mdp_pcc_cfg_data' is defined multiple times

Also please provide .const files generated by syz-extract.

@dvyukov for me its compiling without any issues, please find the const file http://dpaste.com/0QRMVCH

I also get multiple struct ... defined multiple times compilation errors.
When I remove the duplicate structs I get complains about these fields:
mdss_ad_init {
...
   color_corr_lut[int32, 33]
   i_control[int8, 2]
}

mdp_gamut_cfg_data {
...
    r_tbl ptr[int16, 8]
    g_tbl ptr[int16, 8]
    b_tbl ptr[int16, 8]
...
}

and a few about some missing structs.

I am not seeing any of these errors. It's getting compiled with out any errors. What could be the errors in these structures?

The syntax for fields is field_name field_type[specifiers] and for example color_corr_lut[int32, 33] doesn't match this.

@xairy Below is the actual structure, which i have modified for syzkaller descriptor http://dpaste.com/0NCCBPQ. can you tell where is the actual mistake .
struct mdss_ad_init { 	uint32_t asym_lut[33]; 	uint32_t color_corr_lut[33]; 	uint8_t i_control[2]; 	uint16_t black_lvl; 	uint16_t white_lvl; 	uint8_t var; 	uint8_t limit_ampl; 	uint8_t i_dither; 	uint8_t slope_max; 	uint8_t slope_min; 	uint8_t dither_ctl; 	uint8_t format; 	uint8_t auto_size; 	uint16_t frame_w; 	uint16_t frame_h; 	uint8_t logo_v; 	uint8_t logo_h; 	uint32_t alpha; 	uint32_t alpha_base; 	uint32_t al_thresh; 	uint32_t bl_lin_len; 	uint32_t bl_att_len; 	uint32_t *bl_lin; 	uint32_t *bl_lin_inv; 	uint32_t *bl_att_lut; };

for me it is not showing any errors with descriptors http://dpaste.com/0NCCBPQ, but panic is observed while launching syz-manager.
compilation log http://dpaste.com/0FSSQD4
can i know the steps what you are following?

I copied your descriptions into sys/sys.txt and tried to compile syzkaller and got those compilation errors.

can you try this http://dpaste.com/0NCCBPQ once. Also help me what is the issue with actual descriptor with the syzkaller descriptor
can you tell where is the actual mistake .
struct mdss_ad_init { uint32_t asym_lut[33]; uint32_t color_corr_lut[33]; uint8_t i_control[2]; uint16_t black_lvl; uint16_t white_lvl; uint8_t var; uint8_t limit_ampl; uint8_t i_dither; uint8_t slope_max; uint8_t slope_min; uint8_t dither_ctl; uint8_t format; uint8_t auto_size; uint16_t frame_w; uint16_t frame_h; uint8_t logo_v; uint8_t logo_h; uint32_t alpha; uint32_t alpha_base; uint32_t al_thresh; uint32_t bl_lin_len; uint32_t bl_att_len; uint32_t *bl_lin; uint32_t *bl_lin_inv; uint32_t *bl_att_lut; };

You have a typo here:
cfg_payload ptr[intour, mdp_hist_lut_data_v1_7, opt]

It should be ptr[inout, ....
Fixing that should get rid of the panic you get.
Syzkaller currently fails to detect that, I'll add a check.


Automatic publishing of ProGit book is not working.

Before migration from TravisCI to GitHub Actions each release of the ProGit book was published at git-scm.com/book/ including translations.
Now, this process seems to be broken - the new changes are not published.
Here is an example:
The PR is merged https://github.com/progit/progit2/pull/1759 and the new version of the book is released https://github.com/progit/progit2/releases/tag/2.1.346
It is expected that the changes will appear on the page http://git-scm.com/book/en/v2/Git-Branching-Branch-Management but nothing changed.

In fact, the publishing on git-scm.com web site has nothing to do with Github Actions. IIRC, this is a crontab job running each night on the dyno. @pedrorijo91 @ttaylorr could you check the status of the dyno cron scripts?

I think the cronjobs can't hit GitHub's API because the API token they have is an old one belonging to me, and is expired. Ideally there would be some token belonging to a bot account. Barring that, somebody more active should probably generate a token (with locked-down permissions!) and stick it in GITHUB_API_TOKEN in Heroku's config vars (under "Settings", though I think "heroku config" from the CLI can touch the same ones).

@pedrorijo91 do you have access to do this? Otherwise, I can take a look into it myself.

Done.

sorry @ttaylorr i've been out for the past week. i guess this will solve the heroku apps issue as well


Slider not visible in Textual Inversion Tab and not resizing

Thanks for this extension but I'm having an issue.
When I start my webui and go to view my extra networks, all cards are on their smallest size until I go to either of Hypernetworks, Checkpoints or Lora tab which will then resize the cards to the correct size (Load the saved value).
Additionally the slider is missing in the Textual Inversion Tab. If I change the slider size in other tabs that size will apply to the Textual Inversion tab.

Sorry, I missed this issue earlier. I just gave this a major update, so please do give it another try :)


add ability to perform unit tests

test/jest config is encapsulated behind this npm package

@balena-ci I self certify!


Add support for

Description
Zcash 2.0 fork on sapling mpc
Monthly blockreward decreas 5-50%

Name:

HD Derivation Scheme:

Symbol:
 https://github.com/bitzec/bitzec
http://explorer.bitzec.org
Documentation:

Reason: because bzc bitzec
The binary digit zero knowledge electronic currency   : )
Checklist
Finish check list here.

please check our requirements, it looks like bitzec is not even listed in CMC

Its on coinpaprika.com


[core] Fix @material-ui/lab homepage url

[ ] I have followed (at least) the PR section of the contributing guide.

I was browsing the NPM page and came across the broken link to the @material-ui/lab package url.

@francisrod01 Thank you!


jalali to  gregory

how i can convert jalali date to gregory ?

@benamm Sorry for the late response
First create a dayjs instance from jalali date:
const instance = dayjs(jalaliDateString, { jalali: true })

Then change its calendat to gregory:
const gregory = instance.calendar('gregory').locale('en')

@benamm Sorry for the late response
First create a dayjs instance from jalali date:
const instance = dayjs(jalaliDateString, { jalali: true })

Then change its calendat to gregory:
const gregory = instance.calendar('gregory').locale('en')

How to do vice versa?
I mean, Gregory to Khorshidi?

How to do vice versa?

const instance = dayjs(gregoryDateString)
const jalali = instance.calendar('jalali').locale('fa')


TST: Update lib/test_Repo.py for additional inputs (e.g. ./, special characters, ...)

It was noticed, that test_Repo.py is missing some tests we have in newer files, due to its being one of the oldest, so that these should be added soon. This should be seen as connected to #251 and #253, which are about modernizing our existing tests.
In PR #280 it was noticed that Repo.dirs should be tested to contain ./ (here: https://github.com/psyinfra/onyo/blob/main/tests/lib/test_Repo.py#L253). When this file gets modernized, these test-cases, as well as special characters and other common variants tested in the newer tests should be brought in, too.

The whole process of working with paths, special characters, and other things related was reworked.
Many tests were added or re-factored to aim at the underlying problems which lead to the creation of this issue. Therefore I consider this done, and will close this issue.