smatch: move to by-name and modernize derivation

Description of changes

Removed with lib; (ref: https://github.com/NixOS/nixpkgs/issues/208242)
Formatted via nixfmt-rfc-style
Removed rec (ref: https://nix.dev/guides/best-practices#recursive-attribute-set-rec)
Moved pkgs/development/tools/analysis to pkgs/by-name

I also add myself to the maintainer list of this package, as it was empty.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Please split into move to pkgs/by-name, format and refactor. Git is unable to track moved files now.

@aleksaana Thanks for reviewing. Which should I split into two commits, or two pull-requests?

@aleksaana Thanks for reviewing. Which should I split into two commits, or two pull-requests?

Three commits. I asked to split because you edited too much that git doesn't recognize it as a moved file, but a separated one. (https://github.com/NixOS/nixpkgs/pull/343686/commits/55535d9e81ce1b04b08feb49df32ca8bb37c15e7) So someone browsing history will get lost.

@aleksaana Thanks for reviewing. Which should I split into two commits, or two pull-requests?

Three commits. I asked to split because you edited too much that git doesn't recognize it as a moved file, but a separated one. (https://github.com/NixOS/nixpkgs/pull/343686/commits/55535d9e81ce1b04b08feb49df32ca8bb37c15e7) So someone browsing history will get lost.

Understood the reason, I'll do it. Thank you for teaching me.

I split it into these commits.


FIX RealtimePlumber will never exit if push to deep Storage failed

Our HDFS namenode failure for some time occasionally, and I found that realtime peon nodes upload to HDFS failed and never exit. Looking into the RealtimePlumber code and I found that segment push failure will make the Sink never be removed from list, and the peon will be trapped into endless waiting. So a peon will never exit until you kill it manually. This is true for handoff time limit is not set and it is the default parameter.
This can be solved by tracking the state in Sink object and do re-uploading and re-publish in next retries.
I can work on this, any idea?  @fjy

@du00cs Nice find. I think your solution is valid

This is true for earlier production case, but I can not reproduce it. I notice that a commit of Himanshu fix that by dropping the failed segments. I will follow this in later days.

@du00cs, ah, yeah, if "emit" throws an exception then that is an issue with the emitter. Druid assumes that emitting will not throw exceptions, and extensions should assure that is the case by whatever means they choose.
It's a community extension (not maintained by core committers) but patches are definitely welcome if you can fix it yourself! Or you could try pinging people who have worked on it, check the commit history of the extension for details there. IIRC @b-slim was the main original author.

will take a look at it.

@du00cs what was the exception ? can you share the logs ?

@du00cs checkout this Fix https://github.com/druid-io/druid/pull/3441 assuming one of those exception was the issue.

@b-slim Thanks for quick fix, happy to see the changes.


improvement: Upgrade generatorInvocations, Jan 29

Test Suites: 2 failed, 15 passed, 17 total
Tests:       2 failed, 46 passed, 48 total
Snapshots:   29 passed, 29 total
Time:        127.778 s

@dsinghvi if I already ran yarn test -u and yarn test:ete -u, what else should I do to get tests passing?

closing in favor of https://github.com/fern-api/fern/pull/2867


[Addon istio]Modify the label of destinationrules

Signed-off-by: suwanliang_yewu<EMAIL_ADDRESS>
Description of your changes
modify the destinationrules's label app.oam.dev/revision to service.istio.io/canonical-name,because the lable app.oam.dev/revision belongs to deployment, the pod doesn't have the label.

How has this code been tested?
following istio

Checklist

I have:

[ ] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
[ ] New addon should be put in experimental.
[ ] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[ ] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[ ] An accessible icon url and source url defined in addon's metadata.yaml.
[ ] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[ ] Also provide an introduction in KubeVela documentation.
[ ] It's more likely to be accepted if useful examples provided in example dir.

Can you describe a bit how this label service.istio.io/canonical-name works?

Does it relate with https://github.com/kubevela/kubevela/issues/5148 ?

Can you describe a bit how this label service.istio.io/canonical-name works?

Can you describe a bit how this label service.istio.io/canonical-name works?

@wonderflow When a workload is injected into a sidecar, the corresponding  pod will label service.istio.io/canonical-name.The lable can be used to  distinguish between different versions in destinationrules.

Does it relate with kubevela/kubevela#5148 ?

yes

Can you describe a bit how this label service.istio.io/canonical-name works?

@wonderflow When a workload is injected into a sidecar, the corresponding pod will label service.istio.io/canonical-name.The lable can be used to distinguish between different versions in destinationrules.

Does the inject automatically done by istio?

yes


fix(combobox): Disabled Multi Combobox disables the buttons inside it

Issue: #1057
What I did

Fixed the Multi Combobox so that all interactive items inside it cannot be clicked when disabled
Screenshots (if appropriate):

Checklist

[X] changeset has been added
[X] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes
[X] I have added tests that prove my fix is effective or that my feature works

How to test

Confirm that multi comboboxes with selected items can't be deselected
Confirm the inverse state
Confirm the styles of the disabled, selected items
Confirm that when using isClearable, that button also cannot be clicked

🚤

Confirm that multi comboboxes with selected items can't be deselected ✅
Confirm the inverse state ✅
Confirm the styles of the disabled, selected items ✅
Confirm that when using isClearable, that button also cannot be clicked ✅

Tested in: https://next--upbeat-sinoussi-f675aa.netlify.app/api/combobox/
Everything looks good, however I noticed this padding being a little off, I don't know if it's technically a bug or we want to address this in the ticket, however:


Add simple troubleshooting for PoweBI and Analytics

Just a couple of common scenarios we see from time to time when customers are trying to use PowerBI and Analytics.

Hi @debugthings, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

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

Added section about using API per review.

@noamben Made updates per your suggestions

@noamben Thanks for the review. Merging this pull request. When you review pull requests in this repo, please sign off so that automation can add the appropriate label. Thanks.


Converting official checkpoints to the format used in this repo

Hello and thank you for this very useful implementation (I have managed to run it on Jetson devices, unlike the official implementation).
I have tried to use the official weights and configs for other models, provided here: https://github.com/ViTAE-Transformer/ViTPose, but I get some messages about key mismatch, such as
RuntimeError: Error(s) in loading state_dict for ViTPose:
	Unexpected key(s) in state_dict: "backbone.cls_token".

If you could provide info about the parameter names you used in your model, I think I might work to something similar to this conversion script: https://github.com/open-mmlab/mmsegmentation/issues/1473
Best

@Stack-it-up
Which model have you tried?

I have tried using the pre-trained models found in the official implementation, such as https://github.com/ViTAE-Transformer/ViTPose#results-from-this-repo-on-ms-coco-val-set-single-task-training :
in particular, I tried using the Small model (ViTPose-S aka ViTPose_small_coco_256x192) and the Base model with simple decoder (VitPose_base_simple_coco-256x192)

@Stack-it-up
Sorry, I haven't implement for ViTPose-S as well as all models with simple decoder.


pandoc: remove bit no longer needed

Motivation for this change
As comment indicates, 2.6 doesn't need this anymore :).
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Looks like postInstall can go too, looking at hackage-packages.nix. :)

@grahamcofborg eval

Look good? :)

cc #56180 .  Feel free to include this as part of that PR :).

Sorry, totally thought I merged this already. Done in aa88d65e28ad346d14854a8f0c6dfe1cd1fc9dd3


Allow stat var hierarchy to display checkbox instead of stat line charts

Stat var hierachy taking multiple places, which is the case for timeline, scatter plot.
Store stat var hierarchy type in context.
Check the stat var hierarchy type and render accordingly.

Thanks for review!


added f-strings to python-package/setup.py

One mistake below, everything else looks fine!

Could you please mention the line where the mistake is.

One mistake below, everything else looks fine!

Could you please mention the line where the mistake is.

it is right here: https://github.com/microsoft/LightGBM/pull/4145#discussion_r604399154

@NovusEdge

Could you please mention the line where the mistake is.

GitHub review comments are posted with a small visible piece of code. Most often, the last line of that codepiece is the line review comment is referring to.

Also, GitHub has recently introduced "Review suggestions". So that reviewers now can suggest code changes directly in the review comments:

Contributors, in case they are agree with a suggestion, are able to commit the suggested change directly in the browser by clicking "Commit suggestion" button or commit multiple suggestion at one time ("Add suggestion to batch" button).


 It just quits there's no db file created in sample_data

the repo comes with one already sample_data/labels.db. what do you mean no db file is created? did you delete the one that is already there?

@matpalm yes. I want to start fresh. See how things are happening one-by-one
Also I'm downloading your db from Kaggle. So I can try and learn entire thing. End to end. These concepts are very new for me


I Got this error This i missed any thing ?

root@Holfz:/usr/local/bin# youtube-dl https://www.youtube.com/watch?v=Ta-va7qfhnE
[youtube] Ta-va7qfhnE: Downloading webpage
[youtube] Ta-va7qfhnE: Downloading video info webpage
[youtube] Ta-va7qfhnE: Extracting video information
[youtube] Ta-va7qfhnE: Downloading js player vfl8jhACg
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1162, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1085, in _extract_signature_function
cache_res = res(test_string)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1138, in
return lambda s: initial_function([s])
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 254, in resf
res, abort = self.interpret_statement(stmt, local_vars)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 55, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/local/bin/youtube-dl/youtube_dl/jsinterp.py", line 211, in interpret_expression
raise ExtractorError('Unsupported JS expression %r' % expr)
ExtractorError: Unsupported JS expression u'oE"do"'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u'Unsupported JS expression u'oE"do"'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
root@Holfz:/usr/local/bin# ^C
root@Holfz:/usr/local/bin# pip3 install -U youtube-dl
-bash: pip3: command not found
root@bro-vm:/usr/local/bin# pip install -U youtube-dl
Requirement already up-to-date: youtube-dl in /usr/local/lib/python2.7/dist-packages
Cleaning up...

Please make it close. i Sloved

How have you solved it? I have the same problem.

I reinstall it. it work some video
I wait for this Issue too #13123

Reinstalling doesn't work? It's YouTube they changed something which has broken it and we have to wait for fix.

Yea. "Some" video it work for me

Update with pip and pip3 no success. Now trying with apt-get.

From what I understand, without physical code change nothing will work.

apt-get no success too.

We have to Wait For fix


Feature Request: Specify Branch for Dotfiles

I have many branches for my dotfiles and it would be nice to be able to specify which branch to use. On VSCode I have a workaround by add \\-b <BRANCH> before the repo address.

Looks like what you are proposing solves the issue, thanks! ❤


Add description in education section

Thesis title
Abstract (add a link to pdf?)
Supervisor with link
About awards

Add abstract (PDF)?

commit 4a137b39b770c394f0a97e10f5c8b96d38bbd36f


chore(main): release 0.4.4

:robot: I have created a release beep boop
0.4.4 (2024-08-20)
Documentation

Add new API documentation files (19fe2cc)
index docs page update with default readme file (eb6703b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.4.4
:sunflower:


Allow hashes to be escaped in headers

Adjust pattern to allow for escaped hashes, but take care to not treat
escaped escapes before hashes as escaped hashes. Closes #762.

Can you add a comment to the release notes?

Done


Some notices for the the newest version.

VERSION:

python 3.6.2+
mxnet-GPU 1.0.0+ or mxnet 1.0.0+

issues fixed:

if you get the ModuleNotFoundError: No module named 'common' ,it must be you should the newer mxnet version.It has got change in commonhere.Please change to from symbol.common import multi_layer_feature, multibox_layer in symbol_builder.py
Perhaps change xrange to range in python3.6+ version

Many Thanks!

zhreshold/mxnet-ssd works only with python2


ignore headers within code blocks

Hi,
Could the headers within code blocks be ignored? When I run doctoc on input below...
# hola
~~~
# adeu
~~~

... I get the following, I'd only like to have "hola" at the TOC
- [hola](#hola)
- [adeu](#adeu)

thanks

Yeah, that's an issue we've been aware of for some time. I wouldn't be surprised if #77 fixes it though.

Closed via #107.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 53 ms

Resolved: ClamAV performance has improved in 24444ea.


add weighted voting as a combination rule

At this time, the Combination class only accepts the combination rule as parameter.
We want a 'weighted' combination rule, in which one would also manually pass the
weights as parameters (either in the class constructor or in the 'combine' method)
and use those weights to perform the combination of classifiers predictions.

I'm on it


aws ecr scan fails with no error

Below is actions yaml. Attached is the log file.
logs_26538100467.zip
name: Build and run tests for dev

on:
  workflow_dispatch:
  push:
    branches:
      - 'feature/**'
      - 'develop'
    paths-ignore:
      - 'k8s/**'
      - '.github/**'

permissions:
  id-token: write
  contents: write
  checks: write
  issues: write
  packages: write
  pull-requests: write

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout sources
        uses: actions/checkout@v4

      - name: Configure qemu for multiarch builds
        uses: docker/setup-qemu-action@v2

      - name: Configure buildx
        uses: docker/setup-buildx-action@v2

      - uses: actions/setup-java@v4
        with:
          distribution: 'corretto'
          java-version: '21'
          cache: "gradle"

      - name: Setup Gradle
        uses: gradle/gradle-build-action@v3

      - name: Build with Gradle
        run: ./gradlew build

      - name: Configure AWS credentials
        id: creds
        uses: aws-actions/configure-aws-credentials@v1
        with:
          role-to-assume: ${{ vars.AWS_ROLE_TO_ASSUME_ECR_PUSH }}
          aws-region: ${{ vars.AWS_SECRETS_REGION }}
          output-credentials: true

      - name: Login to Amazon ECR
        id: login-ecr
        uses: aws-actions/amazon-ecr-login@v1

      - name: Build
        env:
          DOCKERFILE: "./Dockerfile.jvm"
          REGISTRY: ${{ steps.login-ecr.outputs.registry }}
          REPOSITORY: "ciam-sync-service"
          VERSION: "ciam-sync-service-${{ github.sha }}"
        run: docker buildx build --build-arg ENVIRONMENT=dev --platform linux/amd64,linux/arm64 -f $DOCKERFILE -t $REGISTRY/$REPOSITORY:dev-$VERSION .

      - name: Push
        env:
          DOCKERFILE: "./Dockerfile.jvm"
          REGISTRY: ${{ steps.login-ecr.outputs.registry }}
          REPOSITORY: "ciam-sync-service"
          VERSION: "ciam-sync-service-${{ github.sha }}"
        run: docker buildx build --build-arg ENVIRONMENT=dev --push --platform linux/amd64,linux/arm64 -f $DOCKERFILE -t $REGISTRY/$REPOSITORY:dev-$VERSION .

      - name: Scan image in a private registry
        uses<EMAIL_ADDRESS>        with:
          image-ref: '${{ steps.login-ecr.outputs.registry }}/ciam-sync-service:dev-ciam-sync-service-${{ github.sha }}'
          format: 'sarif'
          output: 'trivy-results.sarif'
        env:
          AWS_ACCESS_KEY_ID: ${{ steps.creds.outputs.aws-access-key-id }}
          AWS_SECRET_ACCESS_KEY: ${{ steps.creds.outputs.aws-secret-access-key }}
          AWS_DEFAULT_REGION:  ${{ vars.AWS_SECRETS_REGION }}

      - name: Upload Trivy scan results to GitHub Security tab
        uses: github/codeql-action/upload-sarif@v2
        with:
          sarif_file: 'trivy-results.sarif'

      - name: Get Image URI
        id: image
        env:
          REGISTRY: ${{ steps.login-ecr.outputs.registry }}
          REPOSITORY: "ciam-sync-service"
          VERSION: "ciam-sync-service-${{ github.sha }}"
        run: |
          IMAGE_ID=$REGISTRY/$REPOSITORY:dev-$VERSION
          echo "image_id=${IMAGE_ID}" >> "$GITHUB_OUTPUT"

      - name: Extract branch name
        shell: bash
        run: echo "branch=${GITHUB_HEAD_REF:-${GITHUB_REF#refs/heads/}}" >> $GITHUB_OUTPUT
        id: extract_branch

      - name: Update Image Version in the kubernetes yaml file
        uses: fjogeleit/yaml-update-action@main
        with:
          valueFile: 'k8s/dev/ciam-sync-service.yml'
          propertyPath: 'spec.template.spec.containers[0].image'
          value: ${{ steps.image.outputs.image_id }}
          repository: nuuday/ciam-sync-service
          branch: deployment/image-${{ github.sha }}
          commitChange: true
          createPR: true
          targetBranch: ${{ steps.extract_branch.outputs.branch }}
          masterBranchName: main
          force: true
          message: 'Update Image Version to ${{ steps.image.outputs.image_id }}'
          token: ${{ secrets.GITHUB_TOKEN }}

@simar7  Could you please assist here?

Hi @Poornachand200 !
Are you encountering a issue with the latest version of action (0.26)?


tidy up package.json w/ fixpack

npm doesn't allow for extra whitespace or any additional formatting in the package.json (it will strip it every single time you use --save with an npm command), so I removed it and sorted the package.json with fixpack.

Thanks for this!


Fix: print error code for nuvoton wifi ping failure

print error code for nuvoton wifi ping failure
Description
Wifi errors are not descriptive, we will print errors from Wifi Ping when they occur for better understanding of failures
Checklist:

[X] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

The branch need to rebase to top of master to pass the cypress64 build test.

/bot run checks


Latest update broke sound drivers.

Latest DS4 tanked my wireless headset as an output.  Can't run logitech software and Ds4 at the same time or I wont get audio.

You are posting in the VERY VERY old, no-longer-maintained DS4Windows repository (Jay2Kings).
Consider trying the vastly improved Ryochan7 fork of DS4Windows:
https://ryochan7.github.io/ds4windows-site/
And if you have any problems, don't back come here. Jay2Kings' repo is obsolete, no one will help you. Instead, post your problem on Ryochan7's issues board: https://github.com/Ryochan7/DS4Windows/issues

Sweet!  Thank you!
On Mon, May 18, 2020 at 8:04 AM Chris Ayala<EMAIL_ADDRESS>wrote:

You are posting in the VERY VERY old, no-longer-maintained DS4Windows
repository (Jay2Kings).
Consider trying the vastly improved Ryochan7 fork of DS4Windows:
https://ryochan7.github.io/ds4windows-site/
And if you have any problems, don't back come here. Jay2Kings' repo is
obsolete, no one will help you. Instead, post your problem on Ryochan7's
issues board: https://github.com/Ryochan7/DS4Windows/issues
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Jays2Kings/DS4Windows/issues/596#issuecomment-630168823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APQ55YF626DAU4UZBK36JIDRSEW6VANCNFSM4M5MMJRA
.


Could we use the grinder to get renewable sand?

Basically the title says it, but if we could use the grinder to break down stone or cobble into gravel and then sand would be a neat feature.

This is a solid suggestion. I have added recipes for gravel from cobblestone and sand from gravel, each requiring 200 MU (10 seconds of basic waterwheel power).


Xilinx vitis HW emulation exception caught error

I have been trying to solve this error for over a month but no results every time I run the HW  emu gives this error . the software emulation runs fine but don't know what's the problem with the hardware . the memory also is not that much allocated just a matrix of 32*32.
[XRT] WARNING: Profiling may contain incomplete information. Please ensure all OpenCL objects are released by your host code (e.g., clReleaseProgram()).
ERROR: [EMU 60-601]  Exception Caught - Failed with the command REMOVE operation at the Line Number: 1394
Makefile:135: recipe for target 'check' failed
make: *** [check] Error 1

@dheeraj141, Is it possible to share the code so that we can check the failure?
which Vitis & XRT are being used?
-Vishnu

It is the hbm bandwidth example but I modified the function performed by the kernel. The kernel is taking 32 inputs each input corresponding to a different bank and then performing a function on the inputs.
XRT Information
Version:        2.7.766
[0] 0000:05:00.1 xilinx_u280_xdma_201920_3(ID=0x5e278820) user(inst=128)

Hi @dheeraj141
As you modified the function performed by the kernel, it reports following errors in log:
[XRT] WARNING: Profiling may contain incomplete information. Please ensure all OpenCL objects are released by your host code (e.g., clReleaseProgram()).
ERROR: [EMU 60-601] Exception Caught - Failed with the command REMOVE operation at the Line Number: 1394
Makefile:135: recipe for target 'check' failed
make: *** [check] Error 1
Please do use Xilinx Forum for such queries:
https://forums.xilinx.com/t5/Vitis-Acceleration-SDAccel-SDSoC/bd-p/tools_v
Please use this Git Issues if you are facing any issue with any existing design without any change in example.
Thanks,
Vishnu

Closing as same discussion started in forum


Truncated float support for SAS Xport files

SAS xport files allow floats to be stored with fewer than 8 bytes, with implicit zeros in the high order bytes.  Currently we only handle full width (8 byte) floats.  This PR adds support for truncated floats.

seems reasonable. can you add a whats note in enhancements.

merged via https://github.com/pydata/pandas/commit/547750aa5ba5b4a1b5d0cde05cc21e588b30cc27
thanks!


oksh: init at 6.8.1

Motivation for this change
Init oksh at 6.8.1. Shell launches and works as expected, so does the man page.
Things done

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

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

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

Result of nixpkgs-review pr 105605 1

1 package built:

oksh

Result of nixpkgs-review pr 105605 1

1 package built:

oksh

Result of nixpkgs-review pr 105605 1

1 package built:

oksh

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/320

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/320

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 105605 run on x86_64-darwin 1

1 package built:

oksh

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 105605 run on x86_64-darwin 1

1 package built:

oksh

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 105605 run on x86_64-linux 1

1 package built:

oksh

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 105605 run on x86_64-linux 1

1 package built:

oksh


Fix concurrent directory creation

Description
Concurrent directory creation fails because we treat all failure cases as an exception. If the directory already exists, we can ignore that exception.
Motivation and Context
Fixes #3917
Replaces #3924
How Has This Been Tested?
Existing tests pass.
Type of Changes

Bug fix (non-breaking change which fixes an issue)

@jelovirt - I confirmed your revised fix on both my 12-core and 24-core machines.


Fixed feed-forward to consider steer_offset

This simple fix improves the PID response and tuning greatly, since Feed-Foward causes very undesirable results on cars that have significant steering offsets
Here is a video showing before / after adding the compensation.
https://www.youtube.com/watch?v=rMTGcqOx26s

makes sense. I guess the only uncertainty is about the sign. You sure about that? :)

btw, nice video

If the angle_offset were negative, would it add to feedforward (and is that desired)?

That's a really good question about the sign, which I spent quite a bit of time on.  I actually didn't submit the full fix that I had, since I was way less confident about it.
The fix started out as a -1 * steer_offset on the input parameter, then a + on the feedforward.  The result from that was very similar to what I submitted, but possibly better for Honda.  (since the steering torque value needs to be inverted in carcontroller.
However, the single change in the PR should not be platform specific at all, and I did test it with the fresh, clean build I created specifically for this PR.  The steering is so much better than I even hoped.

definitely no abs(). And yes, the sign is right. Few words about why this wasn't done before and why we are still on the fence about it: the angleOffset as defined here doesn't exactly represents the physical steering offset, it's just what is needed to drive centered and it is affected by many factors (model skews above all). We should develop a true steering angle offset calibrator.
Also, thinking a bit more about it, I wouldn't expect this change to have much of an effect: wouldn't the integral term of the controller just make up for the difference?

If the angle_offset were negative, would it add to feedforward (and is that desired)? Or do you always want to subtract abs(angle_offset)?

The reason to subtract the steer_offset is because it was first subtracted from the actual steer angle to calculate the desired delta angle, then it was added back to get the desires steering angle.  Therefore, the desired steering angle includes the steer_offset (error).
Since the feed-forward needs to be based on a real steering "center", the offset needs to be subtracted first

The particular issue I was getting from this was that the car was always oscillating some amount in the lane.  Depending on what stage of oscilation it was at on corner entry, it would make the turn well, or it would totally blow it.

uldn't expect this change to h

The problem is that the integral component gets consumed by this error, so it's not usable to do what it normally does.  The feed-forward and integral wind up working against each other (for evil), instead of contributing to a greater good.
Thankfully, it's really easy to do positive and negative testing on this change.  If you simply hard-code a +.5 to that line, and drive on a straight road for a bit, then compare the result to a -.5 on the same straight road, It will be obvious.

Another note about the calculated angle_offset ... I agree that the value calculated by OP isn't perfect.  It changes from day to day.  It's also different from the offset value that is calculated (and reported) by the Honda ECU.  However, the OP value on my car is 0.5 degrees, and the OEM calculated value is -0.7 degrees.  I believe the difference in polarity is due to the flipped polarity in Honda's logic.  Either way, there's a HUGE difference in feed-forward on a torque based system with 0.5-0.7 degrees of offset!  It would literally turn left briefly at the beginning of a right-hand curve!

I tested this in 2017 CR-V, I couldn't seem to realize a positive or negative effect. I'm wondering if the offset of @Gernby  EON is more drastic than mine and even though not exact for the full curve of feedforward is more perceivable with his mount. (my angle offset is about -0.23)

@Gernby
It's also different from the offset value that is calculated (and reported) by the Honda ECU <-- is the angle offset on CAN? There is something on the dbc, but I was under the impression it was something else.
Either way, there's a HUGE difference in feed-forward on a torque based system with 0.5-0.7 degrees of offset! It would literally turn left briefly at the beginning of a right-hand curve! <-- but again, the integrator makes up for it (unless your Ki is zero). So in the end you should not feel a difference.

I tested this in 2017 CR-V, I couldn't seem to realize a positive or negative effect. I'm wondering if the offset of @Gernby EON is more drastic than mine and even though not exact for the full curve of feedforward is more perceivable with his mount. (my angle offset is about -0.23)

I think it will be much less noticeable on a car with smaller offset, but also less noticeable on a CR-V, due to tires and suspension.  My Accord has dynamic dampers, 19" wheels, and low profile tires that make it very responsive to steering input.

@rbiasini Is steer_offset based on offset of steering controller and unrelated to potential roll in EON mount?

I spent a couple hours driving back and forth on a 3 lane S-curve that OP has never been able to handle in my car without me grabbing the wheel in 1-2 places in each direction (after MUCH tuning).  Here is a list of today's observations:

The integral does take care of the steer_offset issue when using the standard tuning parameters for the '18 Accord (relatively low feed-forward)
Something improved greatly somewhere in OP's steering logic over the past few months, since the clean branch I pulled yesterday handles this S-curves VASTLY better than ever before.  I don't think it would handle any of these turns without me grabbing the wheel when I got my EON a few months ago.
I was able to achieve somewhat better results by NOT clipping the steer command at +/- 0x1000.  It is necessary to keep 0x1000 as the multiplier (to preserve the tuning), but the upper and lower limits can be +/-0x7dff.
The saturation beep is annoying A-F

Here is a video I captured, which is at 2X speed.
https://www.youtube.com/watch?v=otHIoYRYMS0

Initial testing for me on Rx450hl was not good.
felt worse for me and it kept trying to turn when line was missing for a intersection.
Road that was good now openpilot was unusable. Version .5.5
Unless it needs to re tune and relearn the car might need more time driving ?

Thought I'd just chime in. Driving GM. QqI didnt notice any changes for the worse.  It actually seemed better for turns but not sure if it's just a placebo effect. As bugsy mentioned there were a few turns I'd usually have to grab the wheel where I didn't this time.  Before it seemed like it would correct too much on some turns. This was at hwy speeds. Will have to test more at city speeds and see as that's where i had most of my steering issues turning

My test was city to and back 5miles each way.
When comparing explorer data
Was 2x the disengages vs. prior days.
The steering reaction time was faster like a sport mode or something.
But again was too sensitive and small gaps of missing lane marking it wold try and turn right or left vs. stayed straight before.
So it could be a good find just might require tuning other parameters.

Chassdesk, I had the same issue but it was from feed forward being too high. Once I raised it too high it started steering really funny.  I brought it back down a bit and it was much smoother.  Not sure if that'll help

The feedback from everybody inspired me to do more focused testing on the impact of speed and slope on the effective 0 crossing (of torque).  What I found is that the true alignment offset does need to be accounted for, but it's more complicated than a simple subtraction.
After subtracting the offset, there needs to be a speed-based dead-zone applied only to feed-forward.  The impact of slope is much more significant at slow speeds, so the deadzone needs to be wide, but as speed increases, the dead-zone needs to shrink.
If I had time tonight, I would record a video of it "dialing itself in", but I need to focus on other things for a bit.  Here is a screen shot of the real-time scatter-plot I built today to show the torque-by-angle over time.  Note how well defined the X is as it moves away from center.  I actually think it would be very simple to auto-tune a look-up table for feed-forward that is angle AND speed based.


Automated Latest Dependency Updates

This is an auto-generated PR with latest dependency updates. Please do not delete the latest-dep-update branch because it's needed by the auto-dependency bot.

Did it not automerge?

@angela97lin was too quick with approving the merge after all CI passes (the workflow needs ~5 minutes after the CI passes).

Oops I completely forgot we had the fancy new automerge 🤦♀


Wrong css generation with libsass 3.6.3

Sassc generates from source approx. 70M large css regardless of light/dark version.
This probably related patterns issue described here:
https://github.com/sass/libsass/issues/3033
*:hover {
*:visited {
color: green;
}
}
button {
@extend *:hover;
}
Similar patterns can be found _common.scss
Cheers.

@cysp74 thanks for raising this - I'm not sure what I can do about it; 99% of the CSS used in this themes is just straight from GTK3. I actually just downgraded my libsass package to 3.5.? to avoid several other deprecation warnings and haven't had an issue since.

Perhaps prebuilt packages as releases? However this would increase maintenance activity on your side....

Thinking about it - I should just include the compiled .css files in the repo just like every other theme developer seems to do. It would be distro/package manager agnostic and would prevent compilation issues due to package updates. I'll see if I can push that up today.

I've included the compiled CSS that I get in the repo. It should now just be a case of symlinking the directories and re-opening gnome-tweaks to see the themes. Let me know if that's working for you.

Awesome, working as expected on my end, issue can closed, thanks. :)


[Feature] Dynamically baked static physics colliders based on visual mesh

Resolves https://github.com/CesiumGS/cesium-o3de/issues/26
This PR implements dynamic baking of static physics colliders based on the visual mesh of the currently loaded tiles.
This PR is developed extending upon https://github.com/CesiumGS/cesium-o3de/pull/45 and https://github.com/CesiumGS/cesium-o3de/pull/50 and has been tested with them, should however also work independently of them.
Edit: It should be noted, that the collider baking implemented here is executed in the main thread. This may introduce visible lag when loading very large tiles

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @lgleim!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.


FancyZones: Zones don't apper with Google Chrome Window [running as user]

ℹ Computer information

PowerToys version: v 0.25.0
PowerToy Utility: Fancy Zones
Running PowerToys as Admin:  🆗 normal behavior.
Windows build number: 1903 (Build 18362.1083)

📝 Provide detailed reproduction steps (if any)
Move with Hotkey and try to snap
✔ Expected result
Fancy Zones appear.
❌ Actual result
Fancy Zones dont appear

Can you try running it as admin?

As described above, running it as admin works as expected.

That's strange. Are you running Google Chrome as admin?

That's strange. Are you running Google Chrome as admin?

no, only tried to run PowerToys as Admin (and then it worked like before).

Well the docs says that FancyZones only requires admin to snap elevated windows: https://github.com/microsoft/PowerToys/wiki/PowerToys-and-running-as-Administrator#when-does-powertoys-need-this

/cc @enricogior

If it doesn't activate when PT is running as a user and it does activate when PR runs as admin, that is already the solution.

Closing issue as answered

just want to mention: i did a reboot and everything works like before.


Present SafariView on top most viewController

Hi,
There seems to be no available way of presenting the SafariView if another viewController is already being presented.
Is that wanted or will it be changed?
Cordially, Louis.

Hey @LouisBorlee:
Would love to hear your feedback on this conversation here:
https://github.com/SimplicityMobile/Simplicity/pull/10
I think we should definitely visit doing something like this; I'm just not too familiar with the edge cases around this at the moment.

Hey @LouisBorlee, I believe #22 should fix your concerns. It's now pushed under 2.0.1. Let me know if this does not!

Hi @edjiang,
Thank you for your reply and update.
Sadly, I'm using your Swift 2.3 branch and thus can't use your fix.
I'll try to see what I can do later for I haven't the time to do it so for now.
Have a nice day!

Ah kk. You could try modifying the dependency files and checking them in, as that branch will probably no longer be updated. Or, you can submit a PR to 2.3; it's like another 4 lines of code so should be fairly straightforward either way =]


Training with smaller batch sizes

Hi @antoine77340 ,
Thank you very much for publishing this great paper and code.
I'm wondering if you can share some insights regarding the effect of batch size on the results. Did you ever attempt to go below batch size 512? (e.g., 32/64/128?). While trying to reproduce the results, I wasn't able to get very far with batch size 64 (unfortunately, larger batch sizes are out of reach for me w.r.t compute).
Thanks!!
Amir

Hi!
Thank you for your comment.
I am not sure if we tried getting below batch size of 64.
But I can assume that the learning can be very difficult in that regime due to high noise in narration whereas batch size of 64 is usually fine with strong and clean supervision (like Kinetics).
Did you try putting a lower learning rate? I guess that would be important given that gradients would be very noisy with batch size of 64.

Thank you for the fast response! I've trained with 1e-3/1e-4 for around 4 days with batch size 64. I've tested the model on HMDB and I get an accuracy of around 20%. I agree that the gradients might be noisier (or have larger variance more precisely). However, the denominator in the MIL-NCE loss actually relies on the size of the batch to get more negative samples, so this is not just noisy gradients, the expectation over the loss with different batch sizes should be different. I'm wondering if that's the reason.

That's right, this also have an effect on the number of negative examples which has an importance.
We do have an ablation study in the original paper where we vary the number of negatives an we tried with 64.
The results are still quite good on HMDB (56% in accuracy).

Thank you for the helpful comments @antoine77340 !

the number of negatives an we tried with 64
@antoine77340 , in this setup, did you fine tune the representations or used fixed representations and just trained a linear classifier?

Hi!
i am sorry for this very late reply, this totally slipped by!
The representation was still learnt from scratch.


Support lifting from LiME dumps

LiME dumps is a damn simple format for memory dumps convenient for developers to write. May be useful for reversing of firmware of embedded devices. Some info though has to be provided off-band, as with other raw images.
Feel free to use my impl: https://github.com/KOLANICH/kaitai_struct_formats/blob/lime_avml_memory_dump/log/lime_avml_memory_dump.ksy .

https://github.com/KOLANICH/lime.py may be helpful


service client: avoid closing conn if it has been reset

When error happens, CallContext returns and the caller may cancel the context, which triggers sc.conn.Close() on nil. This prevents that from happening. I wanted to add test coverage but I couldn't find how to launch the goroslib-test-master container to pass the tests.

Codecov Report

Merging #103 (d5f03ce) into main (bc55e68) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #103      +/-   ##
==========================================
- Coverage   82.26%   82.24%   -0.02%
==========================================
  Files          46       46
  Lines        4432     4433       +1
==========================================
  Hits         3646     3646
+ Misses        574      572       -2
- Partials      212      215       +3

Impacted Files
Coverage Δ

serviceclient.go
63.71% <100.00%> (+0.32%)
:arrow_up:

simpleactionclient.go
60.62% <0.00%> (-1.58%)
:arrow_down:

actionserver.go
81.66% <0.00%> (-0.70%)
:arrow_down:

node.go
79.41% <0.00%> (-0.54%)
:arrow_down:

actionclient.go
57.56% <0.00%> (+1.14%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks for the fix but there's an issue: we can't read sc.conn inside a goroutine, since it is written inside another routine - this leads to a race condition:
go func() {
	select {
	case <-ctx.Done():
		if sc.conn != nil {
			sc.conn.Close()
		}

	case <-funcDone:
		return
	}
}()
...

/// race condition
sc.conn = nil

I fixed the issue in another way. Thanks again for reporting this.

Oops yeah you are absolutely right. Thanks for the prompt fix!


Error Installing appium_lib with Ruby v2.4.2 Due to JSON

Hello we're trying to install appium_lib v9.6.1 (bundle install) with Ruby v2.4.2-2 and we're getting an error with json v2.1.0 (and 1.8.7):
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory:
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/generator
C:/Ruby24-x64/bin/ruby.exe -r ./siteconf20171006-3700-aias1v.rb extconf.rb
creating Makefile

current directory:
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/generator
make "DESTDIR=" clean

current directory:
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/generator
make "DESTDIR="
generating generator-x64-mingw32.def
compiling generator.c
Makefile:241: recipe for target 'generator.o' failed
process_begin: CreateProcess(NULL, x86_64-w64-mingw32-gcc -I.
-IC:/Ruby24-x64/include/ruby-2.4.0/x64-mingw32
-I/C/Ruby24-x64/include/ruby-2.4.0/ruby/backward
-I/C/Ruby24-x64/include/ruby-2.4.0 -I. -DJSON_GENERATOR -D_FORTIFY_SOURCE=2
-D__USE_MINGW_ANSI_STDIO=1 -DFD_SETSIZE=2048 -D_WIN32_WINNT=0x0501
-D__MINGW_USE_VC2005_COMPAT -D_FILE_OFFSET_BITS=64 -march=x86-64 -mtune=generic
-O2 -pipe -o generator.o -c generator.c, ...) failed.
make (e=2): The system cannot find the file specified.

make: *** [generator.o] Error 2

make failed, exit code 2

Gem files will remain installed in
C:/Ruby24-x64/lib/ruby/gems/2.4.0/gems/json-2.1.0 for inspection.
Results logged to
C:/Ruby24-x64/lib/ruby/gems/2.4.0/extensions/x64-mingw32/2.4.0/json-2.1.0/gem_make.out

An error occurred while installing json (2.1.0), and Bundler cannot continue.
Make sure that `gem install json -v '2.1.0'` succeeds before bundling.

In Gemfile:
  appium_lib was resolved to 9.6.1, which depends on
    json

We've followed https://github.com/bundler/bundler/issues/4462 to no avail.
Right now we're using Ruby 2.3.3 and everything is running smoothly,

I don't think this issue relates to Bundler, are you able to install the json gem with gem install json -v '2.1.0'?

@colby-swandale I was thinking that as well, but I wanted to follow suit with #4462

#4462 isn't really a bundler issue either so we're not really able to help unless bundler is specifically the reason why the gem cannot be installed.

@PatrickDuncan Were you able to resolve your issue?

I will post it in the json repo. Thanks.


Making PermissionAdderTest run in PCT

In https://github.com/jenkinsci/bom/pull/359 the test from #23 fails when jth.jenkins-war.path is set to the megawar. Seems that SignupPage.submit quietly returns even when the signup in fact fails. Trying the page interactively showed that it would refuse to proceed unless you entered an email address. Making this change makes the test pass when jth.jenkins-war.path is set. The test utility predates the new signup page GUI but it is not clear that is relevant; I have not figured out what about the megawar (bundled JavaScript?) would change behavior here.

I have not figured out what about the megawar (bundled JavaScript?)

Presence of mailer plugin?

Oh, perhaps.

Hmm, apparently needs to catch ElementNotFoundException in case mailer is absent. On mobile, can try that on Monday.

https://github.com/jenkinsci/jenkins/blob/7aa52381f8d716f19ff71d7cf37970767ed5bbac/core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/_entryForm.jelly#L75 FTR

Now it failed in https://github.com/jenkinsci/matrix-auth-plugin/blob/df6f6491f1d9ddab40fd4476852d8c9940c5762f/src/test/java/com/cloudbees/hudson/plugins/folder/properties/AuthorizationMatrixPropertyTest.java#L111, rerunning.

Hmm, passed locally, not sure what that is about.


update no-string-refs.md?

No-string-refs.md makes the distinction between valid and invalid use of refs:
Invalid:
var Hello = React.createClass({
  componentDidMount: function() {
    var component = this.refs.hello;
    // ...do something with component
  },
  render: function() {
    return
Hello, world.
;
  }
});

Valid:
var Hello = React.createClass({
  componentDidMount: function() {
    var component = this.hello;
    // ...do something with component
  },
  render() {
    return
 this.hello = c}>Hello, world.
;
  }
});

However, the valid method described produces another warning "react/jsx-no-bind". No-string-refs.md may need to be updated so as to illustrate how to properly use refs without either warning?

Sorry I did not see this issue, so I am closing mine.


307/308 - Handle displaying images for non-image assets better

Helps resolve issues described in #307/#308 where image previews/thumbnails are broken for unsupported (by the browser)(sometimes image) file formats.
/cc @HitmanInWis

@HitmanInWis this look generally OK? I think ultimately we gotta fallback on the front-end, but its good to do some more checking on the backend as well.

Yes I agree with this @davidjgonzalez.  In my cursory testing it seems to be working well for the cases I outlined in #307 and #308

btw I think the fix is easy enough for the cart if following the same approach as search results:
Update
src/main/content/jcr_root/apps/asset-share-commons/components/modals/cart/_cq_dialog/.content.xml
+  <missing-image
            jcr:primaryType="nt:unstructured"
           sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"
           fieldLabel="Missing Image"
           fieldDescription="Image to use if no asset thumbnail can be found."
           filter="hierarchy"
           rootPath="/"
           name="./missingImage"/>

update:  src/main/content/jcr_root/apps/asset-share-commons/components/modals/cart/cart.html

+
-

@godanny86 I made an adjustment to SearchConfigImpl so its better at resolving the Search Config even outside of the Search page itself - and leverage the missing image from that, so authors don't have to configure it 2x.


Newsletter-57: translate into Chinese

translate "Lightning BOLTs" to "闪电网络规范"
modified all "Bitcoin Improvement Proposals(BIPs)" to "比特币改进提案（BIPs）" and removed those space on both sides


[webapi] Fix frame-src tests for CSP

Impacted TCs num(approved): New 0, Update 8, Delete 0
Unit test Platform: Crosswalk Project for Android 16.44.399.0
Unit test result summary: Pass 8, Fail 0, Blocked 0
https://crosswalk-project.org/jira/browse/XWALK-4924

Thanks, please apply to Crosswalk-15 branch too.


handling grpc._channel._MultiThreadedRendezvous

Hi Folks,
On a subscribe_stream call, we may receive the grpc._channel._MultiThreadedRendezvous exception.
It seems that for some reason, this is not caught by the script using pygnmi, but can be caught inside the enqueue_updates call, example:
            try:
                for update in subscription:
                    self._updates.put(update)
            except grpc.RpcError as e:
                print(f"{e = }")

I couldn't figure out why, so opening this case to see if we can fix this and close the channel when such error is seen, otherwise it can't be treated. Example of my code that never hits this exception:
    try:
        with gNMIclient(target=host, username=username, password=password, insecure=True, debug=True) as gc:
            telemetry_stream = gc.subscribe_stream(subscribe=subscriptionlist)
            for telemetry_entry in telemetry_stream:
                log.info(f"telemetry_entry={telemetry_entry}")
    except grpc.RpcError as rpc_error:
        print(f'RPC failed with code {rpc_error.code()}: {rpc_error}')

A simple way to hit this is by subscribing to a path that doesn't exist.

Seems like the issue is that subscribe_stream is running on its own thread.
I wonder if we instead use the concurrent.futures module with a future we'll be able to handle this better by capturing the thread's result.

Hey @brunoonovais ,
The idea of running subscribe_stream in a separate thread was done for a purpose of scalability to ensure that multiple threads can co-exist. We can try to look if there will be any benefits of changing the structure.
Best,
Anton

Sounds good, Anton! The point here is that if a subscription closes (i.e. a
process restarts or a box reload or any other issue), one can treat the
condition if the thread result is passed down. If not, what happens is that
the main script won't catch any exception, and basically get stuck.
On Sun, Nov 13, 2022 at 8:58 AM Anton Karneliuk @.***>
wrote:

Hey @brunoonovais https://github.com/brunoonovais ,
The idea of running subscribe_stream in a separate thread was done for a
purpose of scalability to ensure that multiple threads can co-exist. We can
try to look if there will be any benefits of changing the structure.
Best,
Anton
—
Reply to this email directly, view it on GitHub
https://github.com/akarneliuk/pygnmi/issues/104#issuecomment-1312737598,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKG3BBH2Y5DQ4T7OUFRGHOTWIDXZRANCNFSM6AAAAAAR4YTWEU
.
You are receiving this because you were mentioned.Message ID:
@.***>

I encountered a similar problem while using subscribe2. While it generally works well, we face issues with the session to the device, such as network problems, node reboot, or service interruptions, I am unable to receive errors through exceptions. The subscribe session stops sending updates and returns nothing, and I am unsure if there is another way to handle this. It would be helpful to have a method to check whether the grpc session to the device is still normal while receiving updates from the subscribe, or perhaps a way to reconnect the existing session again.

I'm encountering similar issue while trying to subscribe for the path greater than the limit
subscription_dict = {'subscription': [{'path': 'openconfig-interfaces:interfaces/', 'mode':'sample'}], 'mode': 'poll', 'encoding':'json'}
    subscription_ids = []
    for i in range(2):
        subscription_id = client.subscribe_poll(subscribe=subscription_dict)
        subscription_ids.append(subscription_id)
        time.sleep(2)

It's throwing me the below error but i'm unable to catch it
Exception in thread Thread-11:
Traceback (most recent call last):
  File "/usr/lib64/python3.6/threading.py", line 937, in _bootstrap_inner
    self.run()
  File "/usr/lib64/python3.6/threading.py", line 885, in run
    self._target(*self._args, **self._kwargs)
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/pygnmi/client.py", line 999, in enqueue_updates
    for update in subscription:
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/grpc/_channel.py", line 426, in __next__
    return self._next()
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/grpc/_channel.py", line 827, in _next
    raise self
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.RESOURCE_EXHAUSTED
        details = "gNMI: subscribe: exceeded the maximum number of streaming gRPCs per user: 1"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:xx.xx.xx.xx:57400 {created_time:"2023-11-17T17:28:33.376998151+05:30", grpc_status:8, grpc_message:"gNMI: subscribe: exceeded the maximum number of streaming gRPCs per user: 1"}"
>

Is there any fix?
We tried to catch the exception in enqueue_updates even then i'm unable to catch it
def enqueue_updates():
            stub = gNMIStub(channel)
            subscription = stub.Subscribe(_client_stream, metadata=metadata)
            for update in subscription:
                try:
                    self._updates.put(update)
                except Exception as error:
                    print(str(error))
                    raise Exception(error)

I'm encountering similar issue while trying to subscribe for the path greater than the limit
subscription_dict = {'subscription': [{'path': 'openconfig-interfaces:interfaces/', 'mode':'sample'}], 'mode': 'poll', 'encoding':'json'}
    subscription_ids = []
    for i in range(2):
        subscription_id = client.subscribe_poll(subscribe=subscription_dict)
        subscription_ids.append(subscription_id)
        time.sleep(2)

It's throwing me the below error but i'm unable to catch it
Exception in thread Thread-11:
Traceback (most recent call last):
  File "/usr/lib64/python3.6/threading.py", line 937, in _bootstrap_inner
    self.run()
  File "/usr/lib64/python3.6/threading.py", line 885, in run
    self._target(*self._args, **self._kwargs)
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/pygnmi/client.py", line 999, in enqueue_updates
    for update in subscription:
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/grpc/_channel.py", line 426, in __next__
    return self._next()
  File "/ws/sampsamp-bgl/venv/lib64/python3.6/site-packages/grpc/_channel.py", line 827, in _next
    raise self
grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.RESOURCE_EXHAUSTED
        details = "gNMI: subscribe: exceeded the maximum number of streaming gRPCs per user: 1"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:xx.xx.xx.xx:57400 {created_time:"2023-11-17T17:28:33.376998151+05:30", grpc_status:8, grpc_message:"gNMI: subscribe: exceeded the maximum number of streaming gRPCs per user: 1"}"
>

Is there any fix? We tried to catch the exception in enqueue_updates even then i'm unable to catch it
def enqueue_updates():
            stub = gNMIStub(channel)
            subscription = stub.Subscribe(_client_stream, metadata=metadata)
            for update in subscription:
                try:
                    self._updates.put(update)
                except Exception as error:
                    print(str(error))
                    raise Exception(error)

@akarneliuk Can you please help us with this? We are interested in capturing the error.


Support for 'gulp describe --dirty'

Seems like it should be reasonably easy.  Is describe something I should just use git.exec() for?   Or is it worth somehow wrapping describe like git.status()?

I'd suggest using git.exec unless there are formaters needed to parse the output

Thanks


[Change Case] ... Please add 'Sentence Case'

Extension
https://www.raycast.com/erics118/change-case
Description
Could you please add the option 'sentence case' to your app? That would be most welcome for me as a professional writer. For inspiration check the first option on this site: https://convertcase.net/
Who will benefit from this feature?
Writers and more in general people that, for instance, receive feedback from others in capitals and want to transform those texts to ordinary sentence case.
Anything else?
No response

Tx for the quick reply. You're right. Hadn't spotted that option yet.
But, either I'm using it wrong or Sentence Case doesn't work as expected.
Hopefully you or one of the makers won't mind checking.

Tx for the quick reply. You're right. Hadn't spotted that option yet.
But, either I'm using it wrong or Sentence Case doesn't work as expected.
Hopefully you or one of the makers won't mind checking.

No worries!
Yeah, after downloading this earlier, I've been trying to make the extension work, but it seems that there seems to be some sort of bug with the clipboard - I'll see if I can work out what's going wrong later 😄

Tx for the quick reply. You're right. Hadn't spotted that option yet.
But, either I'm using it wrong or Sentence Case doesn't work as expected.
Hopefully you or one of the makers won't mind checking.

Alright so after a little bit of digging, it seems that the library that this extension is using isn't doing the sentence case correctly:

When I think it should say:

The quick brown fox jumps over the lazy dog. Hello there!

--
I've also found the bug I was talking about ^, it seems that you have to "exit" and go back into the extension to put in new copied text.

@JoltCode for the needing to reopen the extension , see https://github.com/raycast/extensions/issues/9364 and the related issues/PRs
For the sentence case and title case not working too correctly, see https://github.com/raycast/extensions/issues/10594 Feel free to add docs clarifying the behavior, or a preference to lowercase the text before other transformations

@raycastbot close this issue


Git-lfs support missing

Agent version and platform
2.124.0
Windows
VSTS type and version
VisualStudio.com
What's not working?
git-lfs isn't installed with the agent, so a pulling from a repository enabled with lfs fails.
I had an older version of the agent running which used to work just fine with lfs, but I had to reinstall it. My builds started failing after the reinstall. I've worked around the problem by putting a copy of git-lfs into the /externals/git/cmd folder - git lfs now functions correctly.

@pete-thompson the agent has never packaged git-lfs with it. you always need to install git-lfs yourself.

Older versions of the agent included git-lfs - my build server was working fine until I had to uninstall/reinstall the agent at which point builds that relied on git-lfs failed. I hadn't installed git-lfs previously. Sadly I don't recall exactly which version I was using previously (it would have been installed early in 2017).

@pete-thompson - can you point me to the version that contained git-lfs?  We never did that.  But I would be interested in unzipping the version you're referring to and taking a look.  The releases tab has all the versions.


Consider more positive reactions in highest-rated-comment

Closes #2190
Test
From original to make sure it still works:
leafo/sticky-kit#201
facebook/react#13991
flutter/flutter#11609
MrMEEE/bumblebee-Old-and-abbandoned#123
Example of likes vs hearts + likes (also my project :smiley:)
https://github.com/microsoft/python-language-server/issues/19

Question, how come you swapped the default parameter for the null parameter and that or construct? I'm not too experienced with typescript but is there a difference?

(reactionBox = document) will set the type of reactionBox to Document but we need it to stay Element so the other calls will keep working.
Instead of changing the type of the parameter, I thought it would be easier to just make it optional and then handle its absence later in the code (reactionBox || document)

Ah I see, sorry about that, I didn't see the compile errors but since it still ran I thought it was fine. Too used to static languages 😄 I'll test this out today or tomorrow and merge, thanks for the explanation.

I'll wait for another day just to be safe if you want to do anything, but I tested it out on the example cases and it works fine.

I tested it as well and it seems to work correctly

Thanks @CTrando!


audit: prefer assert/refute_predicate over File.exist?

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

assert_predicate and refute_predicate fail in a much clearer way than File.exist? does, and we've slowly started switching them over but @ilovezfs suggested audit was the way to go for consistency, so, here's a PR for him.
Before:
Error: minisign: failed
<false> is not true.

After:
Error: minisign: failed
<#<Pathname:/tmp/minisign-test-20171005-74992-3xoky/minisignb.pub>>.exist? is true value expected but was
<false>

Thanks again @DomT4!

@DomT4 OK I think I got all of them:
https://github.com/Homebrew/homebrew-core/pull/19084
https://github.com/Homebrew/homebrew-core/pull/19086
https://github.com/Homebrew/homebrew-core/pull/19088
https://github.com/Homebrew/homebrew-core/pull/19089
https://github.com/Homebrew/homebrew-core/pull/19090
https://github.com/Homebrew/homebrew-core/pull/19091
https://github.com/Homebrew/homebrew-core/pull/19092
https://github.com/Homebrew/homebrew-core/pull/19093
https://github.com/Homebrew/homebrew-core/pull/19095
https://github.com/Homebrew/homebrew-core/pull/19096
https://github.com/Homebrew/homebrew-core/pull/19098

Thanks again @DomT4!

Thanks for merging ❤.

OK I think I got all of them:

Nice! Thanks for that. It was on my radar at some point but I'm certainly not complaining 😉. Appreciated!


feat: build docker images in CI

Hi, really like the project. I wanted to have docker images that were already pre-built to self-host. So, I got the project building in GitHub Container Registry & built automatically in CI.
Definitely some optimizations could be made to the Docker images to get this to work better though like:

We could leverage Docker multi-stage builds to reduce final image size
We could pick a better base image (seems like the current base image is bundling python? That doesn't seem neccessary & I could build it without it. I didn't include it in the PR because I wasn't totally sure if this was needed for a feature that I did not know about)
I found the build times to be extremely slow. I think it is because I'm doing a multiple architecture build but I actually checked and saw that yarn installs were a good chunk of the time. Could have a cache between them or honestly just switch from yarn since it is known to be slow at resolving. (I already added frozen-lockfiles which was a significant speedup)

One thing that I had to do though, we not modify the config file (since that is better handled by a volume) at build time to include the build time arg. So what I did was make env vars be a fallback for values that are actually specified in the config (so updating the config should always override an env var declarations)
You can see the docker images (and pull them if you like!) here:

https://github.com/nperez0111/Perplexica/pkgs/container/perplexica-app
https://github.com/nperez0111/Perplexica/pkgs/container/perplexica-backend

This looks like a professional enhancement to this lovely project. +1 for this

Hey @nperez0111, thanks for the PR! All of the changes looks good but I cannot merge the CI pipeline for the docker image building as if the config.toml file doesn't gets configured correctly, the page won't load and it would throw an error, some of the fields are still not present in the config menu to be configured from the frontend so that might cause an issue, we can implement the CI part later when these things are implemented.

Hi,
I found (here)[https://mariushosting.com/synology-install-searxng-with-portainer/] how to get searXNG running with Portainer. Now I would like to get Perplexica inside Portainer but is there a way to provide API keyes, searchXNG , Ollama URLs, port  via env rather than config.toml file.
Thank you for consideration.

Yea I think in general the maintainer is looking at how to store and configure these settings. I appreciate that it can be difficult since there are so many options to configure with: env vars, runtime values, config file, even the db could store settings.
I made some modifications to read from env vars since that is quite common in docker. But I'll let the maintainer cook on what he actually wants to build, support and maintain.

I've got a version of mine work.
https://github.com/rqi14/Perplexica-docker

@ItzCrazyKns I see you closed this, what you have right now works but what I had made here also supported multiple architectures, attestation and more advanced features than the docker image workflow you've just made. I'd suggest you to reconsider taking my PR


Possible to get Swift Package Manager support added?

We are transitioning away from CocoaPods to SPM – this feels like the 'modern' way of managing 3rd party dependencies on iOS.

Thanks for reaching out.
We are currently looking into extending our support for swift, but there's no immediate plans yet.
Please reach out to your Queue-it representative if you want to discuss anything further related to your implementation.


Develop

Resolved #5.

Coverage remained the same at 44.048% when pulling 003dfcd56fbad0151b04e59967eefcb917b3e891 on develop into 6af76d9aaf0963cc709e42a1b86fe0c3f920ffb6 on master.


Regarding mounting Azure Disk on multiple pods (containers)

Regarding mounting Azure Disk on multiple pods (containers)
"An Azure disk can only be mounted to a single pod at a time. If you need to share a persistent volume across multiple pods, use Azure Files."
I would say that statement/information is wrong.
You can mount a Azure Disk on more then one pod (container) at the time if they running on the same node.
I tested it and it to worked.
Can this be confirmed and the information changed accordingly.
E.g.
kubectl label nodes aks-nodepool1-xxxxxxxx-x azuredisk=disk-name
Add nodeSelector to your pod(s) config.
nodeSelector:
  azuredisk: disk-name

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

ID: 74be7378-92bc-0e59-0b70-c6b10e80d9b6
Version Independent ID: f7f1eeb3-efe7-86e2-1fd7-04341b2c77cc
Content: Create a static volume for pods in Azure Kubernetes Service (AKS)
Content Source: articles/aks/azure-disk-volume.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@caleno Thanks for the finding! I will check this out and let you know.

@caleno Although a single disk can be mounted to multiple pods on the same host, this really isn't something that should be done as the underlying filesystem isn't aware it's being shared for concurrent access like that. This behavior is the same as using a single virtual disk attached to multiple VMs - the filesystem on that disk isn't aware of the scenario, and there's potential for data loss if multiple locks are placed on the same files on that filesystem. It's not behavior unique to using Kubernetes or AKS. The correct, and supported, approach for concurrent access by multiple pods is Azure Files, which is a network-based file share designed for concurrent access.
@jakaruna-MSFT #please-close

@iainfoulds It's a perfectly valid scenario to mount a disk to multiple pods where each pod writes to it's own directory. This is a great way to give each POD their own persistent storage with high IOPS without wasting loads and loads of disk space (=money).
I would propose to document that it is possible to mount disk to multiple pods, and then explain as you did above what the issues with that are. I think we're all grown-up enough to then decide if we want to roll with it or not.

As it currently stands, the documentation is misleading. If there are data loss concerns, they should be stated explicitly instead of making people believe a disk cannot be shared by multiple pods while it, in fact, can.
@iainfoulds
Are the aforementioned data loss concerns still valid given each pod writes to a separate folder on the disk?

I've found myself in the situation of wanting to share the disk with multiple pods where each pod handles a different directory. The informationof the docs has made me loose a lot of hours trying to find a way to achieve the same behavior (in order to not have a ton of disks) in the same pod (multiple containers in a single pod, etc).
It would be really good if the documentation was clearer like @wyrade said


Don't identify call sites by the list of identifiers being defined.

Currently, we identify call sites by the names of the variables defined by the call.   This is
not quite right as apparently things like this make sense:
   () = f (17);

The idea here is that f contains some property that needs to be proved, but does not return
any interesting results.
With the current schema multiple calls like this would be confused, so we probably should just
make up proper (generated) names for each calls site.

Specifically, this refers to the renaming information computed by the inliner.


Please update the OCaml version

Hello everyone
I noticed that the ocaml version you are using is really old, the current version is 4.07
Could you please try and upgrade the version?

Please raise issues about the languages at the neighbour repo https://github.com/Codewars/codewars-runner-cli/issues ;-)

Moved to https://github.com/Codewars/codewars-runner-cli/issues/646


gridcharheight is sometimes calculated wrong

Sometimes the gridcharheight seems to be calculated wrong, with the result that the bottom row of a grid window is invisible. A rearrange event will result in the correct gridcharheight being calculated.
Video: https://youtu.be/GAGTW8BiOtE

Might be related to this? https://github.com/erkyrath/lectrote/issues/83

Sounds like it. I haven't seen it on Mac, anyhow.

Turns out it was happening on Mac, but the calculation error was too small to make a visible difference. And only happening on Lectrote.
I have added a font_load_delay option to cover this case.


Failed deployments not considered when patching resources

When running helm upgrade on an existing release, it appears that helm ignores state that was changed resulting in a failed release. This manifests itself in particular when we use the --wait flag and say that a developer bumps the version of their software component and at the same time want to activate a feature using a new environment variable, the deployment fails because of code issues and now the pod container has an environment variable set that is not tracked by helm.
Here is an example how to reproduce it with a simple helm chart:
chart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: app
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app
  template:
    metadata:
      labels:
        app: app
    spec:
      terminationGracePeriodSeconds: 0
      containers:
        - name: busybox
          image: busybox:latest
{{- if .Values.deploy1 }}
          command: ["/bin/sh", "-ec", "while :; do sleep 5; done"]
          env: []
{{- else if .Values.deploy2 }}
          command: ["false"]
          env:
            - name: UNWANTED_VAR
              value: foo
{{- else if .Values.deploy3 }}
          command: ["/bin/sh", "-ec", "while :; do sleep 5; done"]
          env:
            - name: WANTED_VAR
              value: bar
{{- end }}

First deploy the initial successful version with no environment variables:
$ helm upgrade --install --wait --set deploy1=true chart chart

Then deploy a crashing version with new environment variable:
$ helm upgrade --install --wait --set deploy2=true chart chart

Finally deploy a working version with another environment variable:
$ helm upgrade --install --wait --set deploy3=true chart chart

The result, where the expected output would be only the WANTED_VAR but now also contains the UNWANTED_VAR from the failed deployment:
$ kubectl get po -o json | jq '.items[0].spec.containers[0].env'
[
  {
    "name": "WANTED_VAR",
    "value": "bar"
  },
  {
    "name": "UNWANTED_VAR",
    "value": "foo"
  }
]

Output of helm version:
version.BuildInfo{Version:"v3.5.4", GitCommit:"1b5edb69df3d3a08df77c9902dc17af864ff05d1", GitTreeState:"clean", GoVersion:"go1.15.11"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-21T01:11:42Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Kubeadm

https://helm.sh/docs/faq/changes_since_helm2/#upgrades-where-live-state-has-changed explains some of this behavior in more depth, but I'll try to explain it further.
Helm attempts to upgrade your chart using the last known working release state. That way it has a "known working" state to compare against. It then compares the old state (in this case, the initial deploy), the target state (your last call to helm upgrade), and the live state for comparison. Helm takes all three into consideration to generate the patch.
Because the environment variable was introduced in a failing release, Helm assumes this variable was added out-of-band. And since "live state wins", Helm merges in the two environment variables to preserve changes made to the live state.
To fix this in the future, instead of "forging ahead" when you're in a known bad state, try calling helm rollback chart 1. That way the live state is in a known working state before you call helm upgrade. As a result, you should see the UNWANTED_VAR no longer present.
Hope this helps.

Thanks for the explanation. However for me I see an inconsistency in that the state of identical helm releases is stored differently if it was using the wait flag or not. If release 2 would have been applied without Helm --wait flag it would have been successful and stored with state "deployed" and considered when generating the patch for release 3. For me it would make sense to have a different state when release fails due to wait timeout and consider this state when generating patch for new release?

When we hit a timeout, Helm can no longer guarantee the release is in a consistent state. It would be way more dangerous to attempt to upgrade from an unknown state than a known one. So from Helm’s perspective there is no difference between a failed deployment and a failed deployment due to a timeout.
That’s why I would suggest using helm rollback if you enter a failed release due to a timeout - we’ve recommended this in the past and it (generally) results in a clean upgrade.

We will look into how we can introduce rollbacks in our ci/cd pipeline. I don't have anything else to add so closing this issue, thanks for the support!


Add regex for temperature

add regex in Wex.py
The code is really messed up. Sorry about that!

can you be more specific?

Can you add a detailed explanation, please?

@p-mayank   @Keshav-Agarwal  I'll add it in a few hours. Thanks for taking the interest!


Ensure DataFusion "works" with the "zip bomb" parquet file

Is your feature request related to a problem or challenge?
DuckDB wrote a description of how to compress 4PM of data into a small number of bytes:
https://duckdb.org/2024/03/26/42-parquet-a-zip-bomb-for-the-big-data-age
We should make sure DataFusion / arrow-rs does not explode on this file
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

@alamb  What should be the desired outcome? To be able to read it or to throw an error once we identify the parquet may be a "zip bomb". Can I work on this issue?

@alamb What should be the desired outcome? To be able to read it or to throw an error once we identify the parquet may be a "zip bomb". Can I work on this issue?

My desired behavior would be:

Running a query that actually reads the file (for example SELECT SUM(colum) FROM bomb does not result in an OOM / out of memory
The query can be cancelled (e.g. Ctrl-C / dropping the stream) correctly cleans up and stops decoding

@alamb  I did three test, the results:

The program I did for testing was running forever for this query in my computer, I did not experience OOM contrary the memory consumption was really small 15mb and the cpu consumption was high. I will attach a flame graph for this query.
Code:

fn main(){
    bomb_table();
}

#[tokio::main]
async fn bomb_table(){
    let ctx = SessionContext::new();
    ctx.register_parquet("bomb", "path/to/fortytwodotparquet/42.parquet", ParquetReadOptions::default().skip_metadata(false)).await.unwrap();
    let df = ctx.sql("select sum(b) from bomb").await.unwrap();
    df.show().await.unwrap();
}

Flame Graph of sum query:

I was able to successfully cancel the query and the resources in use where clean.
I run the following query SELECT * FROM bomb to bring everything into memory and the program was killed by OS when it reached the limits of my computer memory.

Flame Graph of * query:

Awesome -- thank you @brayanjuls  -- that is both great news and a great analysis. I think with that I would say this issue is complete. 🎩 👌


gPodder doesn't start

I get the following when trying to start gPodder.
[jei@GnosisNana ~]$ gpodder
1435177334.433182 [gpodder.sync] WARNING: Could not find eyed3.mp3
libva info: VA-API version 0.37.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
NOT SANDBOXED
libva info: VA-API version 0.37.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
[ERROR:flash/platform/pepper/common/pep_process.cpp(19)] CHECK(g_process_type == PROCESS_TYPE_UNKNOWN) failed
中止 (コアダンプ)

This is with freshplayerplugin 0.3.0-2 from AUR. This is output after uninstalling freshplayer:
[jei@GnosisNana ~]$ gpodder
1435177635.731032 [gpodder.sync] WARNING: Could not find eyed3.mp3
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (Arch Linux build 7.u79_2.5.5-1-x86_64)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

It works fine then. Now I build freshplayer myself from git, output is:
[jei@GnosisNana ~]$ gpodder
1435177736.881789 [gpodder.sync] WARNING: Could not find eyed3.mp3
NOT SANDBOXED
[fresh] [warning] NP_Initialize was called more than once
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (Arch Linux build 7.u79_2.5.5-1-x86_64)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

Also works now. So yes just wanted to let you know about this, seems this issue is fixed. But if gpodder starts not working again (it worked at some point in the past with freshplayerplugin installed) I will update this issue.

Yes, similar issue (also with Java and embedded browser engine) was fixed in 7243809dcbe8b2dac9695ee095367cc1ac2b40d4.

v0.3.1 was just released, so mentioned fix is already in.


Allow for bool inputs for loggers

MLFlowLogger takes in a log_system_metrics=<bool> parameter that we'd like to support.

going to merge directly into main instead https://github.com/mosaicml/llm-foundry/pull/897


Github secret is not working inside _config.yml

NOTE: Before you start, the following should be completed.

Read Wiki to understand the usage and the correct effect of functional design.
Make sure no similar issue(including closed ones) exists.
Try to find the answer on Jekyll Forum and StackOverflow.

Description

I have create secrete inside GitHub repo environment secret and pass the value like this
  giscus:
    repo: ${{ secrets.REPO }}
    repo_id: ${{ secrets.REPO_ID }}
    category: General
    category_id: ${{ secrets.CAT_ID }}
    mapping: pathname # optional, default to 'pathname'
    input_position: # optional, default to 'bottom'
    lang: # optional, default to the value of `site.lang`
    reactions_enabled: # optional, default to the value of `1`

Try to find the answer on Jekyll Forum and StackOverflow.

The internet is your friend.


Drop extra link to hosting a module

TBR: @agasparovic - this brings it in sync with master content.

@andresusanopinto LGTM


Datafile column labels

Hi thanks for making this project and dataset available.
I was wondering if you had the names of the columns for the unfiltered bboxes.txt files. It looks like there's some more information in the file that could be useful and I'd like to use it if possible.
Thanks!

Not sure why this was never answered. Sorry about that. Unfortunately we don't have that information readily available now.


postgres-xc fails to build

Message:
checking for dns_sd.h... no
configure: error: header file <dns_sd.h> is required for Bonjour

I've already got a fix for this; I'll submit it after the freeze is over.

This issue was moved to Linuxbrew/homebrew-core#127


Add build filters on org/cluster

Fix bug that did not pick up config changes in builds

[info] ScalaTest
[info] Run completed in 30 seconds, 949 milliseconds.
[info] Total number of tests run: 175
[info] Suites: completed 30, aborted 0
[info] Tests: succeeded 175, failed 0, canceled 0, ignored 2, pending 0
[info] All tests passed.
[info] Passed: Total 175, Failed 0, Errors 0, Passed 175, Ignored 2
[info] ScalaTest
[info] Run completed in 29 seconds, 906 milliseconds.
[info] Total number of tests run: 0
[info] Suites: completed 0, aborted 0
[info] Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
[info] No tests were executed.
[success] Total time: 34 s, completed Jan 2, 2020, 3:12:48 PM


Unable to convert existing base 64 (application/pdf type) string to jsPDF

Aim :
Add custom header and footer to base 64 pdf content.
content-type : application/pdf
Problem :
We tried various approaches to convert base 64 content to jsPDF but looks like jsPDF is expecting either an text, image or an html as input to create an pdf.
Is there any support which allows us to create an pdf with base 64 pdf content. (content-type : application/pdf).

jsPDF cannot read/modify existing PDF files.
Duplicate of #131.


react native 0.60 Please update the following components: TriggeringView

With the new versions of react native many methods become obsolete, do you plan to update the library?
Thank you!

news about that? thanks

@georgeMorales @robertobrogi I planned to update this lib in a few days

+1 for this!

has this issue been resolved i wanted to use it can you give me a alternative to react-native-image-header-scroll-view

@cristoferrao This is resolved ATM by introducing UNSAFE_ to componentWillMount and componentWillReceiveProps for now. If you pull the master with the latest commit, you won't encounter the warning message anymore.

thanks but the warning was removed when i removed the TriggeringView and made hide and that call from HeaderImageScrollView  using on scroll start those options

Seems that the version we get when using yarn or npm does not have the TriggeringView changes in it. Is there a way to fix that ?

@Spoutnik97 ping

Thanks for the update 🙂
If you have time you can make a pull request to update it, otherwise I try to do it this week

Done ✅ I updated the package. Please try v1.0.0 and report errors

@Spoutnik97 Sorry, didn't have time to create pull request.
Thanks! I'll try it out and report any bugs


If function defined in two lines (first line datatype and 2nd line function name) the sticky scroll sticks to first line i.e. datatype

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

VS Code Version: 1.70.2
OS Version: mac os 12.5.1

Steps to Reproduce:

define a function in two line 1st line datatype and 2nd line name followed by definition
e.g
void
foo() {
printf("hello");
}

sticky scroll sticks to first line i.e. void

/duplicate and already fixed in Insiders.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Run linter on JS file

Done.

I found this eslint-check for github status checks. I'm not sure if you had any in mind.
https://github.com/ninosaurus/eslint-check


Fix Path must be a string. Received null error

I believe this error is caused by this plugin. It happens when you open files in the Git view of the editor.

I confirm that, happens to me as well.

I also get this error, but for me it happens in all views of the editor.

Fixed in 2.1.1.
@jshamley It shouldn't happen in every view, only in the Git view. So if this release didn't fix it for you, make sure it's because of this extension by disabling all the others. If it still keeps showing, feel free to open a new issue. But I'm not sure if I will be able to solve it as it never happened to me in the Explorer view.

I am 2.2.0 now and get almost the same error when opening a git diff, but with undefined instead of null:

Path must be a string. Received undefined


refactor: replace rusqlite with sqlx

Unless the maximum number of connections is set to 1, SQLite throws an error stating that the "database is deadlocked."
Many values in mlua do not implement the Sync trait, making it difficult to integrate with axum.

Even though mlua provides async features, it has several types that don't fit in an async scenario, e.g., lua_State. I have tested it with axum and hyper, but with no success. Currently, it's impossible to use SQLx with Mlua, as it requires Mlua to be fully async.


Add a changelog

I was recently encountering an issue with fetchPolicy not being a valid option. I tried to work out why that might be by starting with the library changelog, in order to see when it was introduced. Unfortunately, there isn't a changelog for this project.
As it turns out, the option only exists in master and, correspondingly, the README only applies to master.

Hey there! We are indeed thinking in adding one with lerna and conventional commits, we already use this internally and works wonders

Cool. I'm unfamiliar with either of those tools. A simple text file indicating high level changes from release-to-release, along with release dates, would be perfectly fine. If you have a tool that simplifies it, even better.

closing in favor of #48

@fakenickels Thanks for addressing, but where can I find the changelog or release notes? I can't find a file with history information anywhere in the repo and the GitHub releases page has something for  2.0.0-beta.1, but there's been nine tagged releases since then without any indication of what's changed.

We don't have this for old releases, we'll introduce with the new system of packages management


APPS-362 - Implement manifest support

This PR adds the -useManifests compiler option, which causes workflows and applets to be generated with input and output parameters for manifest files. All job outputs are uploaded directly to the project in the .d folder.
Note: moving final outputs to the workflow output folder and deletion of intermediate files are not implemented in this PR.

@commandlinegirl integration tests are passing. Please review.


Use canonical dotnet project structure

Restructure repository contents to adhere to the example given in this gist, which seems to be a well known, widely used structure.

Hi, could I take this one?

For sure! I have assigned you the PR.

Done via #89


Help

Describe your problem here.

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
yes, i changed the song and the notes display

It says "Uncaught Error: Invalid char 91 at position 127". The game cannot read special characters like ñ or ć. You just need to replace it to fix the error.

i'm not very practical with these kinds of things, if i send the files to you can you help me fix it?
capaproject.json
capaproject-hard.json
events.json

I found a simple mistake happens to the best of us. In events.json, you are missing an open bracket on line 6. Hope this helps!
Also, if you don't already have it, I highly recommend downloading Visual Studio Code, as it highlights easily missed errors.


Remove compass importonce use fast blank

This PR uses the faster blank? from fast_blank instead of ActiveSupport's blank?, as the gem was already included but not being used. I also removed compass-import-once, which was not being used at all.
Please check it out, thanks!

I believe import-once is being used inside compass. It's auto-required by Bundler and does some caching magic

I think fast_blank is also auto-required by Bundler.


bug/docs: remove reference to page packs from CLI docs

The CLI docs make reference to page packs which appears to only be a supported feature for Skuid SFX per the documentation here.
References to page packs should be eliminated from skuid-cli docs since it only supports NLX per the this comment in #183.

Addressed in the same fix as this thread:
https://github.com/skuid/skuid-cli/issues/183#issuecomment-2307322348