generate the tracking results and plots

Thank you for contributing! Do you keep looping when you finally generate the tracking results and plots? Or is something wrong with me somewhere else?

You're welcome, and thank you for your interest in it!
The scripts to generate tracking results loop over different confidence thresholds and the available weights, which takes a while, but you should be able to see progress in the console and evaluation_results folder. Is that what you're experiencing, or is a different part looping and getting stuck?

Thanks for the reply! This is the case in my evaluation_results folder and I don't know where to find the problem?

Thanks for the reply! This is the case in my evaluation_results folder and I don't know where to find the problem?

I don't seem to have spent enough time generating enough txt results, does this file contain files that can directly specify weights and data to generate trace results? I don't seem to see any description in either the code or the paper. Looking forward to hearing from you!

I think the issue is an invalid file path. Tracking_results.sh works in two main steps. The first is to generate the tracking outputs with track.py. Then the tracking outputs are compared with the ground truth (MOT-ASTERS/train/MOT-ASTERS-0X/gt) using the motmetrics Python package to compute the metrics.
I forgot to specify where to put the inference videos, so for simplicity, I added them directly to this repo with the last push. Running the shell script should now find the videos to generate the tracking outputs correctly, and then compute the MOT metrics.
Hopefully, this helps fix the issue. Let me know if you need any more assistance!

别客气！
我认为问题是无效的文件路径。Tracking_results.sh主要分为两个步骤。第一种是用 track.py 生成跟踪输出。然后，使用 motmetrics Python 包将跟踪输出与地面实况 （MOT-ASTERS/train/MOT-ASTERS-0X/gt） 进行比较，以计算指标。
我忘了指定将推理视频放在哪里，所以为了简单起见，我在最后一次推送时将它们直接添加到这个存储库中。现在，运行 shell 脚本应该会找到视频以正确生成跟踪输出，然后计算 MOT 指标。
希望这有助于解决问题。如果您需要更多帮助，请告诉我！

Thank you for the recovery, about the video question I have finished generating the video using the images in the dataset, the previous problem may be that there is not enough time to iterate through all the results generated, if I want to directly use your model and weights to detect a new video, what should I do?

I want to use your model to track different video objects with different weights, so as to achieve a similar effect in your paper. If you can, please have a relevant explanation.

You can use this line to run inference with your desired parameters
python examples/track.py --save-mot --yolo-model "$model_weight" --source "inference/videos/${video}" --name "exp_${model_name}_video${video%.*}_conf_gun${conf_gun}_conf${conf}" --device 0 --conf_gun "$conf_gun" --conf "$conf" --project Tracking_Outputs --tracking-method deepocsort_confirm
For example,
python examples/track.py --save-mot --yolo-model "yolov8n_AugCTextured_CMasked_Real_S.pt" --source "inference/videos/example.mp4" --name "test" --device 0 --conf_gun 0.8 --conf 0.6 --project Tracking_Outputs --tracking-method deepocsort_confirm
Would detect and track shooters using gun confirmation in the example.mp4 video. If you want to also save the video output with bounding boxes, you can add --save and if you want to see the video with bounding boxes as it's running, you can add --show
If you want to compute the metrics, you will need to label the video(s) using a tool like cvat (https://github.com/opencv/cvat) to have the ground truth, which can be a tedious process.
If you want to detect and track objects other than shooters, https://github.com/mikel-brostrom/yolo_tracking would probably be better suited for the task. It's the project I built upon to add the confirmation step to track ID initialization. Alternatively, using custom weights and changing --tracking-method to just deepocsort in this repo should work the same.
Also, just to be clear, I manually added the red arrows in the tracking image to represent the time component of tracking. The video output just has the bounding boxes with ID and confidence.
Hopefully this helps, let me know if you have any more questions!

Thank you for your answer, I have solved the problem of reasoning, after filtering out the 11 weights you bolded in your paper, I reasoned about the same video, and I think that yolov8n_AugCTextured_CMasked_Real_S(The missed detection rate is low), yolov8n_AugCTextured_CMasked_Real_M, and yolov8n_AugCTextured_CMasked_Real_S (Low false detection rate)have the best effect, and finally I have the problem that the guns mentioned in your paper are difficult to detect, and maybe adding some fires generated when bullets are fired may be helpful for gun detection, I wish you all the best in your work!

 That's an interesting idea, although one thing to consider is that detecting the gun when it's already being fired is probably later than ideal. Nonetheless, having higher confidence in gun detection would still be good. I considered adding more annotated guns to the real data from existing gun datasets, but class imbalance might become a concern. Thank you!


82 add tests for check binding

Added the XSL ruleset explicitly to the testbed, I think it was pulling in the parent ruleset before (the stage already existed).


Automated cherry pick of #6052: host fix cmt bound, minor fix

Cherry pick of #6052 on release/3.2.
#6052: host fix cmt bound, minor fix

Codecov Report

Merging #6053 into release/3.2 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.2    #6053      +/-   ##
===============================================
- Coverage         7.02%    7.02%   -0.01%
===============================================
  Files              644      644
  Lines           110421   110425       +4
===============================================
  Hits              7756     7756
- Misses          102066   102070       +4
  Partials           599      599

Flag
Coverage Δ

#aFlag
7.02% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/caller.go
25.43% <0.00%> (ø)

pkg/cloudcommon/db/standalone.go
1.68% <0.00%> (-0.03%)
:arrow_down:

pkg/compute/models/hosts.go
0.31% <0.00%> (ø)

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 aab70ad...6b4c215. Read the comment docs.


Debugger won't start/launch after build fails.

Run or press F5 to debug the C# project.
A build error dialog pops up asking you to click on any of the following: Debug Anyway, Cancel, or Show Errors.
Click Cancel.
Correct the failing code.
Run or press F5 again to debug.
Issue: Debugger won't launch. Does not even trigger the build.

Expected  behavior
Should be able to build & debug after build errors.
Actual behavior

Issue: Debugger won't launch. Not even triggering the build.

Also, the errors in the Problems panel won't go away even though the errors were already fixed.

@dbaeumer @rchande Does this sound like a VS Code issue? Or does the language service side of the extension have something to do in this scenario?

Here is what I see:

new dotnet project created with dotnet new console
opened in VS Code
insert an error (change WriteLine to Writeline)
press F5
you get

which IMO is correct since there is a build error

fix the error
press F5
I can successfully debug

If you don't have auto save on please ensure that after fixing the error you save. Otherwise the error will not go away.

@gregg-miskelly can you provide steps where the F5 fails even after fixing the error.

@gregg-miskelly I did notice another problem. The task you run is using the $mscompile problem matcher. This matcher assumes absolute path names for the files. However the dotnet build command issues relative paths. This can be fixed using the following takss.json config:
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build",
            "command": "dotnet",
            "type": "process",
            "args": [
                "build",
                "${workspaceFolder}/dotnet.csproj"
            ],
            "problemMatcher": {
                "base": "$msCompile",
                "fileLocation": "relative"
            }
        }
    ]
}

However this still double the errors (you see two for program.cs). This can be avoided if you use the same owner as you use for the diagnostics created by the extension itself.
And you should start thinking about using the new task API to provide these tasks instead of writing a tasks.json file. For a do please see: https://code.visualstudio.com/docs/extensions/example-tasks
Please ping if you have questions.

@whizkidwwe1217 are you able to repo this problem for a basic app? Or is this something specific to a project?
@DustinCampbell @rchande in the task.json that we generate, do you think we should be setting an option to dotnet build to have it generate full paths in diagnostic messages? (at least I thought there was an option for this, though I am not sure what it is) Or should we set "fileLocation": "relative"? Do you know how to fix the 'owner' problem that Dirk mentioned?

@gregg-miskelly Yes, I was able to reproduce this problem consistently. I even created a new project fresh from start (e.g. dotnet new webapi),, and I always get same issue. I tried your suggestion but got the same result.

@gregg-miskelly  @DustinCampbell  @rchande Do you think this is a Visual Code issue? It doesn't seem to be a problem in Visual Code Insider builds.

@whizkidwwe1217 I followed exactly your steps using that latest stable release of VS Code and it works for me. @gregg-miskelly can you reproduce this?

I've experienced the exact same thing. I have an issue open with vscode, and they want to see the conclusion of this. @whizkidwwe1217's comment about it working in Insiders led me to investigate something. I tested this in Insiders, but I used Settings Sync to restore all the same extensions I had for my .NET Core development. So, I was experiencing the same issue as I was in the stable release. Others not seeing the issue at all and seeing it go away with a presumably fresh clean Insiders version lead me to believe that it could be a bad interaction between extensions.
I disabled all extensions except for the C# extension, which is required to run the build. I enabled extensions one at a time based on which seemed most likely to be involved and retested. If I didn't see the issue, I disabled the extension I just re-enabled and tried the next one.
My testing revealed that VS Live Share seems to be the problematic extension here. Having only it and the C# extension enabled causes this issue. And back in my primary dev environment, disabling only it resolved the issue for me.

I also tried to disable Live Share in stable build but I haven't thought of it as the issue because I didn't keep an eye on it. After that, I couldn't reproduce the issue. The fact that it worked when I tested it in insider build, which doesn't have Live Share installed, maybe you're right that the  Live Share is indeed causing the build not to work. But I have to confirm this with my other machine. I'll put a comment here after my investigation.

I also had the same experience as @Blackbaud-MitchellThomas. I found that when I disabled all the extensions (apart from the C# extension) I was able to Debug as expected. I then enabled only the C# and VS Live Share code extension and the problem occured. It does feel like the issue is with the VS Live Share extension.

My teammates have confirmed this as well.

This is a known problem being tracked on the live share team. We are planning on releasing a workaround on the short term. The root problem is the use of a vscode debugger API that has limitations for our scenario and so cause problems when proxing a debug session and the builds fail. We have a long term solution that will resolve the root problem by using a different architecture that will be much more robust. Apologize, and as soon as we have the fix one our team members will report.

Thanks @rodrigovaras  I just tested in my other machine and I can also confirm that Live Share is the main culprit.


DataTable control

Will DataTable provide an easy way of displaying a pandas.DataFrame?

I'm pretty sure it will!
It's going to be a general-purpose control for displaying grid data, but then we could do a number of extensions/adapters on Python side to make it more handy with different formats/libs. The same is applicable to charts as well.
I'm going to work on DataTable and Charts next week. This week I'm finishing Authentication. Thanks for your patience!

Expect DataTable control

@FeodorFitsner Any news on this?  I saw a commit related to DataTable but nothing in the documentation yet.

It's been documented here: https://flet.dev/docs/controls/datatable


How to add my API?

Sorry to ask this, but can someone tell me exactly where to place my API token?
Thanks

Sorry that was tricky. Thanks for following up after you figured it out.
I updated the README to make this a bit more clear: https://github.com/zeke/inpainter/commit/95f8f7a1de19322ab657d44a14496d920da636fe

Thank you so much for the clarification, it all work great!


Add a tuto about sparse monge displacements

This adds a tuto demoing sparse monge displacements with mixed costs.

Codecov Report

Merging #374 (7425fbc) into main (31df701) will decrease coverage by 0.71%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files

@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
- Coverage   88.43%   87.73%   -0.71%
==========================================
  Files          51       52       +1
  Lines        5605     5650      +45
  Branches      836      573     -263
==========================================
  Hits         4957     4957
- Misses        529      568      +39
- Partials      119      125       +6

see 3 files with indirect coverage changes

All your comments have been taken into account. WDYT now?

There's a small typo in the notebook, that's why linter fails. After addressing the last few of my comments, we can merge!


Move the src directory to sumatra

Move the src directory to sumatra to adhere to Python canonical naming patterns. This relates to installation issues with python setup.py develop and pip install -e hg+https://bitbucket.org/apdavison/sumatra#egg=Sumatra. See
 https://groups.google.com/d/msg/sumatra-users/n7AIqk0VvqE/KEoC_Ft8N5sJ

and
 https://groups.google.com/d/msg/sumatra-users/xnCAtoI3P-8/50yPisSDUAYJ

Imported from Bitbucket issue 179,  created by wd15 on 05-16-2013 at 13:42, last modified: 05-21-2013 at 09:21

Implemented in r732, r733, r734 (I was tired, that's why it took three commits instead of one!)
Trac comment by apdavison on 05-21-2013 at 09:21


Several updates to the RDS tutorial

Issue #, if available: N/A
Description of changes:
These updates include:

Fixing the examples for specifying paths with FieldExport
Switching default instance type to db.t4g.micro
Updating controller version to v0.0.24

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Minecraft 1.16 version?

I agree it should have one

I agree it should have one

I agree it should have one

https://github.com/LucilleTea/cadmium-fabric/releases

I agree it should have one

https://github.com/LucilleTea/cadmium-fabric/releases


[postgres] creates pod that gets stuck with "chown: changing ownership of ‘/var/lib/postgresql/data/pgdata’: Invalid argument"

BUG REPORT
Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.5.1", GitCommit:"7cf31e8d9a026287041bae077b09165be247ae66", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.5.1", GitCommit:"7cf31e8d9a026287041bae077b09165be247ae66", GitTreeState:"clean"}

Kubernetes:
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.3", GitCommit:"2c2fe6e8278a5db2d15a013987b53968c743f2a1", GitTreeState:"clean", BuildDate:"2017-08-03T07:00:21Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.3", GitCommit:"2c2fe6e8278a5db2d15a013987b53968c743f2a1", GitTreeState:"clean", BuildDate:"2017-08-03T06:43:48Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
postgres (and also gitlab, where I saw it first).
What happened:
After installing & creating a PV for the postgres pod, once it connects its PVC to the PV, the pod falls into a crash loop, with kubectl logs -f <podname> returning just:
chown: changing ownership of ‘/var/lib/postgresql/data/pgdata’: Invalid argument
Literally nothing else is printed - no history up to that message, nothing.
What you expected to happen:
A working pod is installed.
How to reproduce it (as minimally and precisely as possible):
Just install postgres or gitlab.
Anything else we need to know:

I'm seeing the same thing with my pod (not postgres), what was your solution?

Facing same issue. It takes minutes to run simple chown command. Any fixes?

I also face this problme when I deploy postgres use nfs as the storage class provisioner,my storage backend is truenas。I solve it by
setting truenas For no_root_squash, use -maproot="root":"wheel",then all fine.so I think is the permits cause.


Spotify authentication in MA addon

What version of Music Assistant has the issue?
2.2.1
What version of the Home Assistant Integration have you got installed?
2024.8.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
When authenticating with spotify, the callback times out. The issue is caused because the callback is trying to use the internal IP address of homeassistant even when trying to authenticate remotely. Not sure if there is a way to fix this by using the homeassistant public url?
How to reproduce
Try to access Music Assistant from a different network using the public url of your homeassistant, then try to authenticate with spotify, it will fail after a while with a timeout. The only thing that gave me a clue was the browser window that opened to authenticate spotify eventually timed out stating it got no response from https://192.168.XX.XX.......
Then tried to authenticate locally on the same network as my homeassistant install and it completed successfully.
Music Providers
Spotify
Player Providers
No players are affected
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.8.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

No sorry. We are in the process of updating the docs. You must do this locally and not be behind a VPN


Upgrade and pin mattes/migrate to the v3.0.0 tag

Signed-off-by: Ashwini Oruganti<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "upgrade-migrate" git@github.com:ashfall/notary.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354133312
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

LGTM!  Thanks for fixing this!!


Use eslint

Start using eslint, in order to enforce code standards and help in eliminate errors.
NOTE: We should agree on these rules before merging.

Nevermind, I just realized the project uses the JavaScript Standard Style linter.


paddingIndex documentation for TransposedConv2D

Also I'd like to ask if I could start an Issue stating that we support NCWH format for layers as well, is it a wise idea to do that? or should we wait for all layers to be added first and then go onto this idea

Thank you for the contribution!
Speaking of working on NCWH format, let's start with a design document. How do you feel about putting together a writeup on what this work will entail, and then discussing that at one of the future open design meetings?


curl: add hyper support

Closes https://github.com/NixOS/nixpkgs/issues/357409

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] 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

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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.

Curl has officially removed hyper support: https://daniel.haxx.se/blog/2024/12/21/dropping-hyper/


Remove some asserts in libfuncs

Codecov Report
Attention: Patch coverage is 22.22222% with 7 lines in your changes missing coverage. Please review.

Project coverage is 82.91%. Comparing base (16715e5) to head (07173fc).

Files with missing lines
Patch %
Lines

src/libfuncs/bounded_int.rs
22.22%
7 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #921   +/-   ##
=======================================
  Coverage   82.91%   82.91%
=======================================
  Files         120      120
  Lines       34362    34362
=======================================
  Hits        28490    28490
  Misses       5872     5872

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Pre-rendering all pages at once with Adapter Static can exceed node memory limit

Describe the bug
Note: I'm describing this as a "bug" rather than a "feature request" as it seems to not have been an issue in earlier versions of Adapter Static.
When pre-rendering my Svelte Kit app with ~300 fairly data-heavy pages, I am hitting the default 2GB memory limit in Node.
The reason for hitting this limit seems to be that the pre-rendered pages are getting stored in memory until ALL of them have been generated, and then are getting written to disk. Previous versions of Adapter Static seemed to write the pages to disk one-by-one, thus not causing this issue. I tend to believe that this previous "streaming" approach is more robust as it doesn't limit the size of sites that can be statically generated with Svelte Kit.
Reproduction
Build a Svelte Kit app with a lot of pages.
Logs
<--- Last few GCs --->

[18376:0000021C00E58240]   114602 ms: Scavenge (reduce) 2042.8 (2083.6) -> 2042.3 (2083.6) MB, 18.1 / 0.0 ms  (average mu = 0.128, current mu = 0.097) allocation failure
[18376:0000021C00E58240]   114620 ms: Scavenge (reduce) 2043.0 (2083.6) -> 2042.6 (2084.1) MB, 7.6 / 0.0 ms  (average mu = 0.128, current mu = 0.097) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF68DA2013F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+112495
 2: 00007FF68D9AF396 DSA_meth_get_flags+65526
 3: 00007FF68D9B024D node::OnFatalError+301
 4: 00007FF68E2E19EE v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF68E2CBECD v8::SharedArrayBuffer::Externalize+781
 7: 00007FF68E17C2C9 v8::internal::Heap::PublishPendingAllocations+1129
 8: 00007FF68E17929A v8::internal::Heap::PageFlagsAreConsistent+2842
 9: 00007FF68E16BF19 v8::internal::Heap::CollectGarbage+2137
10: 00007FF68E16A0D0 v8::internal::Heap::AllocateExternalBackingStore+2000
11: 00007FF68E18EA06 v8::internal::Factory::NewFillerObject+214
12: 00007FF68DEC1CD5 v8::internal::DateCache::Weekday+1797
13: 00007FF68E36F3E1 v8::internal::SetupIsolateDelegate::SetupHeap+494417
14: 00007FF68E3015A1 v8::internal::SetupIsolateDelegate::SetupHeap+44305
15: 0000021C0359EF49

System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz
    Memory: 2.02 GB / 7.72 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (102.0.1245.33)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @sveltejs/adapter-static: next => 1.0.0-next.34
    @sveltejs/kit: next => 1.0.0-next.350
    svelte: ^3.34.0 => 3.46.4

Severity
serious, but I can work around it
Additional Information
I can work around this for my present project by setting a higher memory limit in Node, but can imagine that it will fail entirely for very large projects (eg. 1,000s, 10,000s or 100,000s of pages).

I'm afraid we're going to need a repro for this. Pages aren't stored in memory, they're written to disk as they're ready, and the default config.kit.prerender.concurrency (which dictates how many pages can be prerendered at once) is 1. Perhaps there's something else going on here?

I think two weeks is long enough to wait for a repro. OP, if you are still experiencing a bug, please create a repro and open a new issue. Thanks!

I've got unintentional repro:
git clone https://github.com/i-s-compat-table/i.s.compat.table.git repro &&
  git checkout 12fdd14 &&
  cd repro/website &&
  pnpm i &&
  pnpm build

When I run the failing build, I see memory usage creep up while ~11 of processes like
node<EMAIL_ADDRESS>\
  ./svelte-kit/output/client/ \
  ./.svelte-kit/generated/prerender.json \
  ./.svelte-kit/output/server/manifest.js \
  true

run. I double-checked that setting config.kit.prerender.concurrency did not affect the memory consumption.
system info

  System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
    Memory: 29.00 GB / 31.29 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.n/bin/node
    Yarn: 1.22.11 - ~/.n/bin/yarn
    npm: 8.11.0 - ~/.n/bin/npm
  Browsers:
    Firefox: 103.0
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.64
    @sveltejs/adapter-static: 1.0.0-next.39 => 1.0.0-next.39
    @sveltejs/kit: next => 1.0.0-next.405
    svelte: ^3.44.0 => 3.49.0
    vite: ^3.0.0 => 3.0.0


FIX for XHTML Documents

in XHTML Documents getElementsByTagName is Case-Sensitive and XHTML
allows only lower Case Tag-Names

Great find - hope this can get merged soon


Look into casing issues with HoneySQL

Casing issues with HoneySQL:
https://github.com/seancorfield/honeysql/issues/386

I'm tracking general DDL (column specification) issues around casing in https://github.com/seancorfield/honeysql/issues/439


fix: shifted hidden column are causing problems

closes #404
Prerequisites:

[x] Branch is up-to-date with the branch to be merged with, i.e. develop
[x] Build is successful
[x] Code is cleaned up and formatted
[x] Tested with Firefox ESR, latest Firefox, latest Chrome, Edge 18

Summary
fixes #404 where hidden columns are causing shifting errors

the question is what should happen with a column that is by default hidden? Should the user be able to add it at all? I changed the logic such that the user cannot add a hidden description.

IMO there are two options:

Columns are hidden everywhere and cannot be added or used (current status with your last commit)
Columns are hidden in the ranking by default (similar to initialRanking: falsein TDP), but can be added by the user (previous status)

I'd argue that option 1 does not make a lot of sense, because the column could be filtered out from the dataset before passing it to LineUp or one could simply not create a LineUp column for this data column. In both cases we would have the same result that the column is not available or visible in the UI.
Option 2 is probably prefered, because it gives users the option to add the column later on demand. In my opinion the previous state was fine, the only thing missing was the filter in the side panel when adding a hidden column to the ranking (see my last comment).

Option 2 is probably prefered, because it gives users the option to add the column later on demand. In my opinion the previous state was fine, the only thing missing was the filter in the side panel when adding a hidden column to the ranking (see my last comment).

why adding a column to the (initial) ranking and mark it as hidden? Why cannot you just use the builder to build a ranking which doesn't include this column ?

I think we are still not on the same page and there are two points, we should discuss:

Define which columns should be available in the add column dialog
Define which columns should be shown/hidden in the (initial) ranking

I thought the first one is automatically done by adding the dataset to the builder (e.g., LineUpJS.builder(arr)) or registering it to the data provider. If a developer wants to make certain columns unavailable the properties must be filtered out before passing arr to the builder.
As for the second point, I agree with your suggestion to exclude the column from the builder and also thought that this should do the trick. Take for example the visibility.html demo with the removed cat column builder:
.column(LineUpJS.buildStringColumn('d').label('Label').alignment('right').width(100))
// .column(LineUpJS.buildCategoricalColumn('cat', cats).color('green').hidden())
.column(LineUpJS.buildCategoricalColumn('cat2', cats).color('blue'))
.column(LineUpJS.buildNumberColumn('a', [0, 10]).color('blue'));

The cat column is not visible in the ranking, but also not available in the add column dialog:

What is the setup to hide a column in the (initial) ranking, but let the user add it on demand?

What is the setup to hide a column in the (initial) ranking, but let the user add it on demand?

the builder automatically calls .defaultRanking() when no explicit ranking is defined. e.g. take a look at builder2.html. You can create your own rankings easily and define which columns you wanna include. The .defaultRanking() will include all columns by default
const builder = LineUpJS.builder(arr);

// manually define columns
builder
  .sidePanel(true, true)
  .column(LineUpJS.buildStringColumn('d').label('Label').alignment('right').width(100))
  .column(LineUpJS.buildCategoricalColumn('cat', cats).color('green'))
  .column(LineUpJS.buildCategoricalColumn('cat2', cats).color('blue'))
  .column(LineUpJS.buildNumberColumn('a', [0, 10]).color('blue'));

const ranking = LineUpJS.buildRanking()
  .supportTypes()
  .column('d')
  .column('cat')
  .column('a')
  .groupBy('cat')
  .sortBy('a', 'desc')

builder.ranking(ranking);

const lineup = builder.build(document.body);

as far as I remember: The use case for the hidden flag of columns is quite rare. You want a column part of the ranking which is not visible to the user. For example when you wanna control a column from the outside which sole purpose is to control the ranking with no user interaction.


API endpoint issue.

I have installed cf-cli, BOSH CLI v2 and VirtualBox in my computer. My aim is to build a private cloud and push an app to cloud using Cloud Foundry but its asking for an API endpoint. Kindly help me in setting up the cloud environment using BOSH and VirtualBox and then push an app using cf.
What I feel is there's an issue regarding the connection between my computer and VM created in VirtualBox. But I'm not sure.

@spunky11 wihtout a more concrete error message its hard to help. i would recommend following http://bosh.io/docs/bosh-lite to get a feel for it and then extending it to cf.

@cppforlife
I have completed all the steps given in the doc i.e. installation of bosh-lite and zookeeper deployment (even the smoke test was successful); but I really do not have an idea as to how to set up the cloud environment with the help of BOSH and VirtualBox.

I have completed all the steps given in the doc i.e. installation of bosh-lite and zookeeper deployment (even the smoke test was successful)

http://bosh.io/docs/bosh-lite#install step 7 specifies how to add route from your machine so that you can access IPs where (zookeeper or other software can run). hoping @dsabeti can point to bosh-lite cf installation guide.

@spunky11, you can follow these directions to deploy Cloud Foundry to bosh-lite. You'll probably want to start at step 4, since the first few steps have to do with setting up a bosh-lite on a public cloud like AWS or GCP, and you're using you're local VirtualBox instead.

Closing - thanks @dsabeti for the assist. Feel free to follow up if you are continuing to see issues around the routing to VMs.


racket: unbreak on darwin

Description of changes
Closes #240085.
Things done

Built on platform(s)

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

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

[ ] 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/)
23.11 Release Notes (or backporting 23.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.

@ofborg build racket racket.passthru.tests

Result of nixpkgs-review pr 240096 run on aarch64-darwin 1

2 packages built:

racket
racket-minimal


[BIGTABLE] Insert callback called multiple times if err

Environment details

OS: macOS Sierra 10.12.11
Node.js version: 6.9.1
npm version: 3.10.8
google-cloud-node version: "@google-cloud/bigtable": "^0.6.0"

Steps to reproduce
I use "insert" function to insert an array of 2 entries, for the example I force error with "wrong" timestamp (yes timestamp defined in milliseconds is invalid...)
let i = 0;
const INSTANCE_NAME = 'myInstance';

require('@google-cloud/bigtable')().instance(INSTANCE_NAME).table('test').insert([{
  key: 'alincoln',
  data: {
    follows: {
      gwashington: {
        value: 1,
        timestamp:<PHONE_NUMBER>949 // Invalid timestamp (note<PHONE_NUMBER> in seconds is OK,<PHONE_NUMBER>949000 in microseconds is OK)
      }
    }
  }
},{
  key: 'alincoln',
  data: {
    follows: {
      helloworld: {
        value: 1,
        timestamp:<PHONE_NUMBER>949 // Invalid timestamp (note<PHONE_NUMBER> in seconds is OK,<PHONE_NUMBER>949000 in microseconds is OK)
      }
    }
  }
}], err => {
  i++;
  console.log('--');
  console.log(`CALLBACK ${i}`);
  if (err) console.error(err.message);
  console.log('--');
});

/*
--
CALLBACK 1
--
--
CALLBACK 2
Error in field 'entries' : Error in element #0 : Error in field 'Mutation list' : Error in element #0 : Timestamp granularity mismatch. Expected a multiple of 1000 (millisecond granularity), but got<PHONE_NUMBER>949.
--
*/

In source file "table.js" I just add some logs to find source of error, callback is called multiple times, first time with end event, and last with error event
If I use promise syntax I just never see that an error occurred because promise is resolved with end event without error
// table.js - line 868
this.requestStream(grpcOpts, reqOpts)
  .on('error', (err) => {
    console.log('event:error', err); // LAST_LOG: event:error { Error: Error in field 'entries' : Error in element #0 : Error in field 'Mutation list' : Error in element #0 : Timestamp granularity mismatch. Expected a multiple of 1000 (millisecond granularity), but got<PHONE_NUMBER>949.
    callback(err);
  })
  .on('data', function (obj) {
    obj.entries.forEach(function (entry) {
      // Mutation was successful.
      if (entry.status.code === 0) {
        return;
      }

      var status = common.GrpcService.decorateStatus_(entry.status);
      status.entry = entries[entry.index];

      mutationErrors.push(status);
    });
  })
  .on('end', function () {
    var err = null;

    if (mutationErrors.length > 0) {
      err = new common.util.PartialFailureError({
        errors: mutationErrors
      });
    }

    console.log('event:end', err); // FIRST_LOG: event:end null
    callback(err);
  });

Thanks for reporting, we'll put out a patch soon.

Fix sent in #1847.

The fix turned out to be incorrect and the issue persists.

It looks like the gRPC stream emits both metadata and error, which triggers two event handlers that retry-request is listening for to decide if it should retry the request: https://github.com/stephenplusplus/retry-request/blob/85ee18dfc48e3bff174a4711440f55ed4748dc0f/index.js#L83-L84
metadata is what we've been using to say "nothing obvious went wrong with the request", but it looks like we're going to need to beef up that logic, since an error can still emerge.
A solution is to wait after receiving the metadata event before giving retry-request the all clear, but it would introduce an undesirable delay at the start of each request. That would look like:
  var waitForErrorTimeout;

  var retryOpts = {
    retries: this.maxRetries,
    objectMode: objectMode,
    shouldRetryFn: GrpcService.shouldRetryRequest_,

    request: function() {
      return service[protoOpts.method](reqOpts, self.grpcMetadata, grpcOpts)
        .on('metadata', function() {
          // retry-request requires a server response before it starts emitting
          // data. The closest mechanism grpc provides is a metadata event, but
          // this does not provide any kind of response status. So we're faking
          // it here with code `0` which translates to HTTP 200.
          //
          // https://github.com/GoogleCloudPlatform/google-cloud-node/pull/1444#discussion_r71812636
          var self = this;
          waitForErrorTimeout = setTimeout(function() {
            var grcpStatus = GrpcService.decorateStatus_({ code: 0 });
            self.emit('response', grcpStatus);
          }, 1000);
        });
    }
  };

  return retryRequest(null, retryOpts)
    .on('error', function(err) {
      clearTimeout(waitForErrorTimeout);

      var grpcError = GrpcService.decorateError_(err);
      stream.destroy(grpcError || err);
    })
    .pipe(stream);

@callmehiphop any other ideas on how we can handle this?

@stephenplusplus I'm not too sure, maybe some one on the gRPC side of things would have insight to help us.
/cc @murgatroid99

I think it's worth clarifying what those emitted events mean. The "metadata" event is emitted unconditionally at the beginning of any call that the server accepts and starts handling, whether or not the call eventually succeeds. "error" is emitted if the call fails in any way.
There is also the "status" event, which is emitted unconditionally when the call finishes, with a code indicating success or failure. You could do something like
call.on('status', function(status) {
  if (status.code == grpc.status.OK) {
    self.emit(response);
  }
});

Receiving an OK status code should be mutually exclusive with seeing an "error" event.

@murgatroid99 thank you for the explanation. After digging in further, it looks like the gRPC stream will emit both an error and an end event. While the stream is technically "ended" after an error occurs-- maybe more accurately, "closed"-- the end event should not be emitted.
require('fs')
  .createReadStream('non-existent-file')
  .on('error', function(err) { console.log('emitted') })
  .on('end', function() { console.log('not emitted') })
  .on('data', function() {}) // to drain the data

require('request')
  .get('http://www.non-exitent-url.com')
  .on('error', function(err) { console.log('emitted') })
  .on('end', function() { console.log('not emitted') })
  .on('data', function() {}) // to drain the data

This is the root of our problem when trying to use retry-request. It's expecting the stream to either emit error or end, but not both. The stream will emit end first, then error.
I haven't looked deeply into the implementation in gRPC, but making a generalization; if this is the process:

allow the stream the user is holding to complete its lifecycle
do some post-processing
emit status
if there was an error, emit error

Consider using an intermediary stream, such as a through stream or a Transform stream, then registering a prefinish event handler to cork() the stream while you do the post processing. If after determining there was no error, you can call uncork() on the through stream, which will allow the end event to fire.

Posted to a new issue in the gRPC repo: https://github.com/grpc/grpc/issues/8954

Going to close this and follow over on https://github.com/grpc/grpc/issues/8954 for developments.


fixes #231: generate strings with fewer escape sequences by default

Fixes #231. Many more characters are now represented literally instead of by their unicode escapes by default. /cc @vkz

From my side, this looks very nice to me.

@michaelficarra thank you very much!
спасибо! :)


Emulator - Azure sign in does not let me sign in under a new tenant

Version
4.0.0-preview
Describe the bug
I signed in the Emulator with my Microsoft org id, signed out, then closed the Emulator. When I reopen the Emulator again and sign in as a different, non-Microsoft id, I get an error.
To Reproduce
Steps to reproduce the behavior:

Sign in to Emulator with a Microsoft id.
Sign out.
Close Emulator.
Open Emulator and sign in with a different Azure account. See the error messages below.

Screenshots

[bug]

The original report is a bit misleading, I don't think it is to do with signing out and the signing in with a different id.  I think the problem is that the emulator is somehow hard coded to authenticate microsoft.com ids against the Microsoft tenant/AD only, and doesn't work with personal ids.  When I try to log in with an outlook.com id (which is associated with Azure) I get the same error:

Microsoft
Sign in
Sorry, but we’re having trouble signing you in.
AADSTS50020: User account<EMAIL_ADDRESS>from identity provider 'live.com' does not exist in tenant 'Microsoft' and cannot access the application '4f28e5eb-6b7f-49e6-ac0e-f992b622da57' in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.
©2018 Microsoft Terms of use Privacy & cookies
Request Id: ed68caaa-b337-45e2-ba32-efee14985f00
Correlation Id: 29db409d-27be-4bed-93ce-afb9f798a131
Timestamp: 2018-11-15T16:06:38Z

Having looked at the code, I think the cause may be this application id in azureAuthWorkflowService.ts, line 40:
const clientId = '4f28e5eb-6b7f-49e6-ac0e-f992b622da57';
I presume that is registered on Microsoft's own AD and thus not available to users on a different AD (or personal LIve IDs etc).

I registered a "Bot Emulator" app on my own AD, gave it the right redirect URI and Windows Azure Service Management API permission and changed the clientId in azureAuthWorkflowService.ts to the new app ID, and I could then log in.  So perhaps that clientId needs to be configurable in settings?

I'm getting this too - I can't actually use the emulator to log in to either my corp Azure subscription or my MSDN subscription because of it, which renders the services pane completely useless.
Any idea on why this is this way and when it will get fixed?

This should be resolved now. If you are still seeing an error, please reopen this issue or feel free to create a new one.


All emails going to gmail spam folder

Hi guys,
Great plugin. My issue is that all my emails are going to gmails spam folder. I have had to create a hardcoded subject and create a filter in gmail to stop it going to spam.
Have you guys experienced this before? Gmails spam message is 'Why is this message in Spam? It's similar to messages that were detected by our spam filters'. Is there a setup for fromEmail and subject etc that you know of that stops it going to spam? My sender name is the same as domain name so I know it's not that issue.
Thanks!

There are some good tips here for ensuring reliable email delivery: https://blog.codinghorror.com/so-youd-like-to-send-some-email-through-code/


Add bower support ?

Hello,
It could be great if this library can be loaded using bower
What do you think ?

Duplicate of #1


[Feature Request] Sub categories

It would be nice to have sub categories. I am wanting to have a structure that goes like:

life

task

projects

project one

task

a more better idea to just add recursive categories so it's more universal :)


Use switch statements

In torchaudio's libsox bindings (I/O and sox effects), there are couple of locations where different operation is applied based on Tensor's dtype.
Currently the code uses caffe2::TypeMeta type to check the dtype, such as the following example;
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/effects_chain.cpp#L83-L107
For this kind of execution flow, using switch statement makes the code cleaner. caffe2::TypeMeta is not an integral type so switch statement is not applicable. Converting it to c10::ScalarType make s it possible to use switch statement. For the above case, the resulting code looks like the following.
  switch (tensor_.dtype().toScalarType()) {
  case c10::ScalarType::Float: {
    auto ptr = tensor_.data_ptr<float_t>();
    for (size_t i = 0; i < *osamp; ++i) {
      obuf[i] = SOX_FLOAT_32BIT_TO_SAMPLE(ptr[i], effp->clips);
    }
    break;
  }
  case c10::ScalarType::Int: {
    auto ptr = tensor_.data_ptr<int32_t>();
    for (size_t i = 0; i < *osamp; ++i) {
      obuf[i] = SOX_SIGNED_32BIT_TO_SAMPLE(ptr[i], effp->clips);
    }
    break;
  }
  case c10::ScalarType::Short: {
    auto ptr = tensor_.data_ptr<int16_t>();
    for (size_t i = 0; i < *osamp; ++i) {
      obuf[i] = SOX_SIGNED_16BIT_TO_SAMPLE(ptr[i], effp->clips);
    }
    break;
  }
  case c10::ScalarType::Byte: {
    auto ptr = tensor_.data_ptr<uint8_t>();
    for (size_t i = 0; i < *osamp; ++i) {
      obuf[i] = SOX_UNSIGNED_8BIT_TO_SAMPLE(ptr[i], effp->clips);
    }
    break;
  }
  default:
    throw std::runtime_error("Unexpected dtype.");
  }

We would like to apply the same pattern to all the usage of caffe2::TypeMeta. The following is the list of such usage.
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L105-L110
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L219-L226
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L389-L397
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L423-L444
Steps

Replace the if ~ else if ~ else statements listed above with switch statement on c10::ScalarType. Use toScalarType() method to convert caffe2::TypeMeta to c10::ScalarType.

Building and testing locally

Follow the CONTRIBUTING guide to set up development environment.
Build and run test with;

BUILD_SOX=1 python setup.py develop && (cd test && pytest torchaudio_unittest/backend/sox_io -v --ff )

All the test should pass.

I can work on this.

@prabhat00155
Thanks, let me know if you need help.

Is there any point in modifying this: https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L105-L110

Is there any advantage of modifying this?
https://github.com/pytorch/audio/blob/05bff83fdec3e8f70f80bf7a1b89951bf7050114/torchaudio/csrc/sox/utils.cpp#L105-L110

Not much from practical view point. It's more cosmetic.

Well, there should be a tiny performance improvement because ScalarType is backed by integral type. But that will be negligible improvement.


Better experience for replacing folders in web upload

This PR fixes #99074

Thanks, this is a good fix I think. Pushed a few fixes on top.


issue/367 add changelog for id_attribute called id

Description
Adds a changelog entry saying that in a future release it will not be possible anymore to use an id_attribute called id
closes https://github.com/inmanta/pytest-inmanta/issues/367
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in ff8db9422466dcbccb073342856c85f6a164fe57

Processing #5868.


Non blocking recv

This change allows ws.recv() to be non-bocking. It will return empty string when there current is no data.
This way your main loop can call recv inside of it and do other things while there isn't data actively coming in.
This PR contains the change from #7 as well. I could separate them if that would be best.

You can rebase on main, by removing the extra_headers commit from this one.
The current idea with the library though is that the blocking behavior has to be set by the user code, or application-level library, catching OSError on its side. See here in the OBS client library (which could be updated to use errno).
https://github.com/Neradoc/websockets-for-circuitpython/blob/4f45b58313057df5e7d55035c3b0d703988a2891/examples/obs_remote_demo/obsws.py#L65-L79
So we can't force or assume in the code that the timeout is set to 0.
I'm not sure what EAGAIN is used for in general though, if it's always and only raised when the timeout is 0 and there's no data, we could still implement your change to read_frame(). Or maybe move it to recv().
But I don't know if using a 0 timeout works well, which is probably why I don't use it in my OBS code.
Isn't there a risk that each call to read() would raise an EAGAIN exception then ? Are we sure that all the bytes of a websocket frame will be received together so that when the first read() succeeds, all the other ones do ? Or should they have retries and manage the actual user-set timeout at a higher level rather than at the internal socket level ?
I vaguely remember trying things where the timeout is set to 0 before looking for the first 2 bytes, then set back to its past value if it succeeds, and I probably gave up after having issues, a long time ago.

I didn't know about EAGAIN either, but found information in this answer: https://stackoverflow.com/a/4058377/507810  which also links back to some older documentation here: https://web.archive.org/web/20130508062559/http://www.wlug.org.nz/EAGAIN
I do think it should be a configurable option rather than hardcoded to zero, I stuffed it there mostly as a quick proof of concept.
Having timeout 0 seems to be working fine for my use case. I've been using the modified version of the library for a few days during development and haven't had any issues with only receiving partial data from a recv(). using it like this:
_data = self.ws.recv()
if _data:
    self._info_log(f"Received Data: {_data}")
    # do more stuff with _data ...

It does mean that we're calling read() over and over and it's constantly raising that EAGAIN message. But it handles it gracefully and ends up returning None if there is no data. I'm receiving JSON via this mechanism and have not had any issues with receiving partial data or not being able to parse the data that I've received, though I have done mostly only rudimentary testing, and am not really sending that much information through the websocket at this point. It's pretty much just opening and waiting for incoming messages and printing them, all of the messages that are being sent are manual so I've clicked the button a handful of times only.
I don't know for certain that it's guaranteed to receive the full message, but anecdotally it seems like it does.
I'll try to get some more thorough testing setup and perhaps submit example scripts for server and client that illustrate how it's working. I will also get the branch sorted out. I'll try getting it working back into this PR, but if I mangle the branch locally I may make a new one from a clean branch.

Have you tried doing it like that, without changes to the library ?
self.ws.settimeout(0)
try:
    data = self.ws.recv()
except OSError as err:
    if err.errno == errno.EAGAIN:
        data = b""
    else:
        raise

Thank you!
Doing it that way does seem to work for me after a quick test. I'll to some more thorough testing next week, but after this test I don't see any reason to believe it will end up requiring any change to the library. Closing this now and I'll start using the currently released version in my project.


New worker architecture

Added package structure and interface for new architecture supporting several
implementations for calling worker scripts.

@johnduro I have created an interface intended to support different ways to execute worker scripts. Do you thing you can work with that for #65. Please also have a look at https://github.com/corvus-ch/rabbitmq-cli-consumer/wiki/Architecture.

@corvus-ch I looked at the architecture and i think i can work with it. I have to take a little time to discover the interfaces in go.
How do you think we should do ? You merge the interface + the exec worker refactored and then i'll implement the fast-cgi one ?

How do you think we should do ? You merge the interface + the exec worker refactored and then i'll implement the fast-cgi one ?

@johnduro You can start with FastCGI as soon as the interface is merged. Waiting for me to merge the refactored exec worker probably will make things for you a lot easier since you have some place to look for inspiration. Your decision.

@corvus-ch i think i'll wait for the worker merge as i'm going in holliday soon and i won't be able to do anything while this period


Enable container as task type

Need to add a new task type called "container".
This new task type does not have magnus installed as part of the container, so all implementations should find ways to interact only via file mounts.

Released as 0.43.0


JOpenCageComponents should contain unmapped objects of a _type key and _category

See the image below:

Right now fields like _category and in this case "leisure" are not mapped to the JOpenCageResponse:

I think that for that those fields or any other key of _type  should be included for the easier manipulation of the formatted string in the response.
Currently the raw JSON object in the response contains all the vital components for the custom formation of the string, but the JOpenCageComponents does not contain, for example, a field "leisure" IF there is a "_type" : "leisure" , so that field cannot be mapped from JSON to the JOpenCageResponse.
Here is the example :
"coordinates": [
16.407438398213937,
48.172555994664336
]
formatted = “FC Mariahilf, Leberstraße 84, 1110 Wien, Österreich”
We want to, for example, be able to remove “FC Mariahilf”. So I think that if we could add a HashMap field "unmappedFields" for all the dynamic fields that are currently not being mapped to the JOpenCageComponents response, which adds a tad more flexibility to the code..

Since I am not allowed to push the changes to create a PR, here is a solution:
Just add these lines of code in JOpenCageComponents
`    Map<String, Object> unmappedFields = new LinkedHashMap<>();
@JsonAnySetter
void setUnmappedFields(String key, Object value) {
    unmappedFields.put(key, value);
}
public Map<String, Object> getUnmappedFields() { return unmappedFields; }`

Hi,
I checked the docs for creating PRs and it is missing one part, that I though is obvious.
You have to clone the this repo.
I will add it to the README.
BR

https://github.com/moberwasserlechner/jopencage#contribute


Improve error handling for feed test

When creating a feed and running the first test need to ensure we are returning the most comprehensive and error message possible

Added here: https://github.com/JohnGUnderwood/atlas-news-search/commit/d703e0d6387e0b9e0bf6ba13242331dff4fc024a


/en-US/docs/Learn/CSS/Building_blocks/Organizing

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

There is a broken link on
/en-US/docs/Learn/CSS/Building_blocks/Organizing
In the section "Compiling component stylesheets" there is a link to
You can see how one developer approaches the problem in this blog post (https://www.lauraleeflores.com/blog/how-to-organize-your-css-files) which leads to an 404 error page

Ah yes, that article no longer seems to exist. That's a shame.
I couldn't really find an appropriate equivalent, so I've just removed it, and added a bit more information on Sass partials.
Thanks for reporting it!


Ability to use --no-verify as default and have it as an option in dialog

In #110452 it was requested to have --no-verify as a default configurable setting. The issue was closed, because it was misread.
It would be very useful to have this as a configurable default VSCode setting, that you can enable because on some codebases I want to ignore the pre-commit step as:

it's either very slow to execute
or I want to bypass the commit name linter
or the step is failing due to setup issues

Additional enhancement:
It would also be very useful if in the below dialog, it had an option Commit (No Verify) that you could use to re-do the commit without verification. This is a common action to take next, and would bypass the need to go into context menus.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Errors using ChatGPT

Trying to listen to a stream from GPT, I can see the data being printed out, but my listeners never fire.
flutter: FormatException: Unexpected character (at character 1)
flutter: data: {"id":"chatcmpl-72CZsAqYS71OoS3bA3uGmCjkkScEO","object":"chat.complet...
flutter: ^
flutter:
flutter: data: {"id":"chatcmpl-72CZsAqYS71OoS3bA3uGmCjkkScEO","object":"chat.completion.chunk","created":1680759360,"model":"gpt-3.5-turbo-0301","choices":[{"delta":{"role":"assistant"},"index":0,"finish_reason":null}]}
flutter:
flutter: data: {"id":"chatcmpl-72CZsAqYS71OoS3bA3uGmCjkkScEO","object":"chat.completion.

Usage example:
var url = Uri.https('api.openai.com', '/v1/chat/completions');
    final headers = {'Content-Type': 'application/json', 'Authorization': 'Bearer $k'};
    final response = await http.post(
      url,
      headers: headers,
      body: json.encode({
        'stream': true,
        'model': 'gpt-3.5-turbo',
        'messages': messages.map((e) {
          var role = e.chatMessageType == ChatMessageType.user ? 'user' : 'assistant';
          if (e.chatMessageType == ChatMessageType.system) role = 'system';
          return {'role': role, 'content': e.text};
        }).toList(),
        'temperature': temperature ?? .7,
        'max_tokens': 2000,
        'top_p': 1,
        'frequency_penalty': 1.0,
        'presence_penalty': 1.0,
      }),
    );
    final _listener = SSEClient.subscribeToSSE(
      url: 'https://api.openai.com/v1/chat/completions',
      header: headers,
    ).listen((event) {
      print(event);
    });

I believe this is because POST is not used, so no body content can be set.

Hi @esDotDev.
The issue is that the package doesn't support post at them moment. I'll add that in today and create a new release.
Thanks

Hi, any luck with this? Is there anything I can do to help?

Hi @esDotDev. Sorry for the delay. I am almost done
Will create a hotfix in a couple of hours

Great, ty!


feat: Allow unsafeSsl for artemis connections

Add unsafeSsl option (like the prometheus scaler) to allow self-signed certificates.
Checklist

[x] When introducing a new scaler, I agree with the scaling governance policy
[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) -> https://github.com/kedacore/keda-docs/pull/1042
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #

Relates to #

/run-e2e artemis*

/run-e2e artemis*

Does unsafeSsl make sense once the customCA is merged?

Closing as customCA can solve the issue


fix: SignUp Issue

What
For Incorrect Email there was long html response which has been fixed in this PR

Looks good, thanks @Akashsri3bi
Edit:
It does but what is missed is the analyzer. You have to also commit the pubspec.yaml and pubspec.lock

Sure @M123-dev !

Looks good to me too !

Thanks !!


Documentation is outdated

All of the documentation refers to an old version of Twitter's interface that no longer is available. Setting this up requires alot of guessing about proper inputs.

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

ID: c3c91b46-f547-f01a-b44b-2f0da184eed8
Version Independent ID: e4d3f56c-0349-55f5-8c50-17b2b4b3dbf8
Content: Set up a connector to archive Twitter data - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/archive-twitter-data-with-sample-connector.md
Service: o365-seccomp
GitHub Login: @v-tophillips
Microsoft Alias: v-tophillips

@v-tophillips Please help us in resolving this issue. Thanks

@eliebermangwm Thanks for your feedback! New issues and pull requests for this content are closed while we update this content to support upcoming feature improvements.


Support for other hashing functions?

Is this on the roadmap? I'm concerned about the security of SHA1 against GPU attacks.

Could you describe your concern with SHA1 as it is used in this library in more detail?
Attacks against hash functions are not representative of their security as part of message authentication.  https://en.wikipedia.org/wiki/Hash-based_message_authentication_code#Security
You can subclass or assign to override default_digest_method if this is a concern for you.

See #80, I'm upgrading this to SHA-512 after more discussion.


[SPARK-17866][SPARK-17867][SQL] Fix Dataset.dropduplicates

What changes were proposed in this pull request?
Two issues regarding Dataset.dropduplicates:

Dataset.dropDuplicates should consider the columns with same column name
We find and get the first resolved attribute from output with the given column name in Dataset.dropDuplicates. When we have the more than one columns with the same name. Other columns are put into aggregation columns, instead of grouping columns.

Dataset.dropDuplicates should not change the output of child plan
We create new Alias with new exprId in Dataset.dropDuplicates now. However it causes problem when we want to select the columns as follows:
 val ds = Seq(("a", 1), ("a", 2), ("b", 1), ("a", 1)).toDS()
 // ds("_2") will cause analysis exception
 ds.dropDuplicates("_1").select(ds("_1").as[String], ds("_2").as[Int])

Because the two issues are both related to Dataset.dropduplicates and the code changes are not big, so submitting them together as one PR.
How was this patch tested?
Jenkins tests.

Test build #66724 has started for PR 15427 at commit dd6405c.

Test build #66724 has finished for PR 15427 at commit dd6405c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66724/
Test PASSed.

cc @cloud-fan @hvanhovell

Test build #66790 has started for PR 15427 at commit 81339dc.

Test build #66790 has finished for PR 15427 at commit 81339dc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66790/
Test PASSed.

Merged build finished. Test PASSed.

My thoughts:

Dataset.dropDuplicates() should drop duplicates for all columns, the current implementation is wrong, this PR fixed it.
Dataset.dropDuplicates(col: String) should drop the first column matching the given name, or all matched columns? Dataset.drop(col: String) also drops all matched columns, the new behaviour seems reasonable. But we should be very careful, as this is a breaking change. cc @rxin

Dataset.dropDuplicates() should definitely drop duplicates for all columns.

Dataset.dropDuplicates(col: String) should also drop duplicates for all columns matching the name.

LGTM, merging to master!

Thanks for review! @rxin @cloud-fan


Need an example that uses the scope parameter

I cannot figure out how to format the scope parameter to List configurations.  I've tried without any URL Encoding (scope=22e89a89-a207-4e3d-81cb-e364225db1e6:refs/heads/master), and I have tried with URL encoding (scope=22e89a89-a207-4e3d-81cb-e364225db1e6%3Arefs%2Fheads%2Fmaster), I've tried wildcards, and I always get a JSON object with "count": 0.  If I don't use the scope parameter at all, I get the whole list of policy configurations.  The documentation seems so straight forward.... but it doesn't work!  It'd be nice to have an example because I'm sure I'm just doing something wrong.

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

ID: d635175e-8ab5-dd18-2b4a-18587075cab6
Version Independent ID: dffee946-f65f-2b4c-bacf-0e42f3392398
Content: Configurations (VSTS Policy)
Content Source: docs-ref-autogen/4.1/policy/Configurations.yml
Product: devops
GitHub Login: @wnjenkin
Microsoft Alias: whjenkin

This parameter is actually a very confusing legacy implementation. We do not recommend you use it, as it will probably not do what you want (as you are discovering 😄) but we keep it for legacy support purposes. If you look at this policy API you can query for all policies on a given ref/repository.

Is the preview git/policy API working? I tried querying it with no parameters and get an empty result returned: {"count":0,"value":[]}
I know that project has policies and am able to pull policies using the policy/configurations api. I posted on this on Stack if you could shed some light: https://stackoverflow.com/questions/53709421/azure-devops-git-policy-configurations-api-broken

@hross for visibility

@jdholbrook81 I will get in touch on the stack overflow thread. The blank git/policy and policy endpoints are returning policies for me. I'll get some more info from you over there.

@jdholbrook81 The policy and git/policy APIs work fine with no query parameters from what I can tell. I am going to need some more specific info. Email me at<EMAIL_ADDRESS>and I can follow up.


Unable to build with private registry that allows only https

With our private registry that only allows https access I can not build the container with the fabric8 maven plugin. Manual executing of docker build works just fine.
The error message is that the maven plugin for some reason tries to access the registry for my base image with http. Is there a configuration to skip this API check?
[INFO] DOCKER> [docker-registry.cp.creditreform.de/ask/ask-ims:2.1.0-SNAPSHOT] "ask-ims": Created docker-build.tar in 64 milliseconds [ERROR] DOCKER> Unable to build image [docker-registry.cp.creditreform.de/ask/ask-ims:2.1.0-SNAPSHOT] : Get http://registry.docker.ecofis.de/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)  [Get http://registry.docker.ecofis.de/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers) ]
Info

f-m-p version : 0.21.0
Maven version (mvn -v) : 3.3.3

Posted in wrong project, was docker-maven-plugin


BMI Calculator is done

Issue No. #72
Email id used to regsiter for VSoc'24<EMAIL_ADDRESS>Description
This is  a BMI Calculator which is been Build using HTML,CSS,JS
Type of PR

[ ] Feature enhancement

Screenshots / Videos (if applicable)
https://github.com/dhairyagothi/50_days_50_web_project/assets/140420819/a671af1e-a5b3-4d56-ad1d-71bb36c89836
Checklist

[ X] I have performed a self-review of my code.
[ ] I have read and followed the Contribution Guidelines.
[X ] I have tested the changes thoroughly before submitting this pull request.
[ X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have followed the code style guidelines of this project.
[X ] I have checked for any existing open issues that my pull request may address.
[ ] I have ensured that my changes do not break any existing functionality.
[X ] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[ ] I have read the resources for guidance listed below.
[ ] I have followed security best practices in my code changes.

check in issue by entering [X] in boxes
Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the Easy label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to Medium. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Easy:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Medium:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Hard:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!
](https://www.linkedin.com/in/monishr608/)

change name
merge main branch tere are conflicts


[Feature] jsx outline filter nodes

Why
With UI lib like mui, the component tree is very deep. It would be very useful if the outline can filter out component nodes for clean structure.

do you want a setting to remove specific outline items by regexp? eg /^[A-Z]/
anyway I really do suggest splitting the component tree into smaller components (we have our code action Extract to JSX btw for this) or at least extracting specific JSX tree parts into variables in the same component.


Cloning into 'sm-3Dcontinous' Fatal

Hi, there is an error when I trying to run your code, the error message is:

I can find the sm-3Dcontinous on your github

Hi,
I accidentally linked the wrong repo, sorry.
try this command instead.
git clone git@github.com:paul0noah/sm-3dcouple.git

Hi, I accidentally linked the wrong repo, sorry. try this command instead. git clone git@github.com:paul0noah/spider-match.git

thanks very for your help, I have already install the env. unfortunatly, when I run the spidermatch_example.py, I got the error:

I changed the core area size to unlimited, but the problem is still there

the error is caused by this line: smm = ShapeMatchModelDijkstra(vy, ey, vx, ex, edge_costs.T, True, False, False)

Hey @paul0noah , do you have any solutions/updates for the above issue on "segment fault(core dumped)"?

Hey @Reginald-L , you can use this conda install -c conda-forge libstdcxx-ng for opening the visualisation window. I hope this

@Reginald-L, did the solution of @kulendu work for you?

Closing due to inactivity


Patches table not being populated

When I process a nessus file, it seems as though the "patches" table does not get populated. As a result the ms_patch_summary template produces a blank report.

This should be fixed in v1.4.9


Features in .csproj are ignored.

I am trying to use the "Flow-Analysis"  which should be added to a .csproj like this
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.1</TargetFramework>
    <Features>Flow-Analysis</Features>
  </PropertyGroup>

However when I try to use your library like this:
AnalyzerManager manager = new AnalyzerManager();
 ProjectAnalyzer analyzer = manager.GetProject(@"path/to/my/project.csproj");
AdhocWorkspace workspace = analyzer.GetWorkspace();
var project = workspace.CurrentSolution.Projects.First();
System.Console.WriteLine(project.ParseOptions.Features.Count);

The output will be 0, the feature is not added to my project.
Some features like the ControlFlowGraph need those to be used
Ex: http://source.roslyn.io/#Microsoft.CodeAnalysis/Operations/ControlFlowGraph.cs line 74
if (!operation.Syntax.SyntaxTree.Options.Features.ContainsKey("flow-analysis"))
{
    throw new InvalidOperationException(CodeAnalysisResources.FlowAnalysisFeatureDisabled);
}

I just published Buildalyzer 2.0 which runs MSBuild out-of-process (as opposed to the old way of running it via MSBuild APIs). In general, if you can build it Buildalyzer should now be able to build it. Given how drastically different this new technique is, I'm closing all existing bug reports.
Please try the new version and if you're still having problems, please open a new issue.


GPL v3 License violation

This is great work, no doubt.
However, it cannot be released under C0, because it contains the init_module string from LMFAO https://github.com/esoteric-programmer/LMFAO
Well, I may have tolerated that, but I'm a little disappointed that the C0 is more show than real since neither the source code nor the entire tool chain were released or named. Even in the write-up, the use of LMFAO is not named at all. If you don't want to put your into GPL v3 (including a release of your source codes), please contact me to discuss the usage of the init_module.

@esoteric-programmer
Interesting. When I was tinkering with your code, I didn't exactly realize that grafting the string would be a license violation. Thanks for the heads up, I will contact you as soon as possible.


2023-24 reporting

Planned Date
Action
Done and notes
Completed Date

22nd April
ARC sends over previous year's school template for the RRED team to update to the current year
✅
22nd April

1st July
RRED team sends over school template for current year
✅
1st July

1st - 5th July
ARC checks access for 2023-24 RRED project
✅

22st July
Study closes
✅

29th July
ARC receive dispatch list from RRED
✅
29th July

29th July
ARC downloads 2022-23 and 2023-24 years from redcap
✅
26th July

30th July - 2nd August
ARC run wide to long conversion (may need to use the alias file from the previous year), send masterfile and any issues files over to RRED
✅
30th July

5th - 9th August
RRED team resolves any issues found with schools
✅

5th - 9th August
ARC reruns redcap extract and then ask RRED team to check masterfile for any required manual edits
✅

12th - 15th August
ARC resolves any issues in generating reports, email UAT combined report to RRED team
✅
8th August

12th - 15th August
Katie emails indvidual reports to their own email address to ensure setup is working
✅

19th August
email individual reports to<EMAIL_ADDRESS>✅

30th August
RRED team tests the dispatch list for emails working
✅

10th September
reports signed off by RRED, email to schools
✅
10th Sept

10th September
ARC to archive masterfile and dispatch list on R drive
✅
11th Sept

Closing as all completed 🎉


 All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

/opt/conda/lib/python3.9/site-packages/scipy/__init__.py:146: UserWarning: A NumPy version >=1.16.5 and <1.23.0 is required for this version of SciPy (detected version 1.26.4
  warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}"
[2024-08-02 10:10:26,735] [INFO] [real_accelerator.py:161:get_accelerator] Setting ds_accelerator to cuda (auto detect)
Traceback (most recent call last):
  File "/opt/openfold/run_pretrained_openfold.py", line 498, in <module>
    main(args)
  File "/opt/openfold/run_pretrained_openfold.py", line 288, in main
    for model, output_directory in model_generator:
  File "/opt/openfold/openfold/utils/script_utils.py", line 97, in load_models_from_command_line
    d = torch.load(ckpt_path)
  File "/opt/conda/lib/python3.9/site-packages/torch/serialization.py", line 705, in load
    with _open_zipfile_reader(opened_file) as opened_zipfile:
  File "/opt/conda/lib/python3.9/site-packages/torch/serialization.py", line 242, in __init__
    super(_open_zipfile_reader, self).__init__(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: Expected hasRecord("version") to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)

Hi, thanks for your interest in OpenFold.
To make predictions using alphafold weights, please specify the parameter path with the flag jax_param_path instead of openfold_checkpoint_path


Structural suggestion SDG12.6

SDG: 12
Target & Phrase: 12.6 phrase 1
Suggestion: Can drop "OR ("energy efficien*" NEAR/5 ("housing" OR "building$" OR "construction$")) " as efficien* is included as a standalone term
Reason: Simplification

I also wonder if it would more consistent to use the whole SCP string here (as used in phrase 1) - or at least it maybe needs some documentation as to why these specific terms are included while others from SCP are not?

Add "corporate" as a synonym for companies (currently only "corporation" is included). Consider also terms which could go with sector (e.g. industrial, commercial, logistics sector)


Move the topBar below the navigation bar avoid the app got rejected b…

because of a status bar overlay (for violating 10.1/10.3).

This won't make it in that form.. we could possibly add it as a style setting or something. But even then we should not use magic numbers (44.0).


Bad error message and script for gogh.sh

I had a lot of trouble using Gogh for Mac OS using iterm2. I kept getting the error message below. I think it should be more descriptive to help people use Gogh properly.
Unsupported terminal!

Supported terminals:
   mintty and deriviates
   guake
   iTerm2
   elementary terminal (pantheon/elementary)
   mate-terminal
   gnome-terminal
   tilix
   xfce4-terminal

If you believe you have recieved this message in error,
try manually setting `TERMINAL', hint: ps -h -o comm -p $PPID

I tried setting the TERMINAL env value to iTerm2 and other variants and it still would show that message each time I tried rerunning the script.
Similarly I tried running ps -h -o comm -p $PPID and kept getting the output COMM\nlogin which was related at all to the terminal type.
I eventually had to go trough through the script and see that the the $TERM_PROGRAM env is used to set the tone $TERMINAL. The value of this on my machine was 'iTerm.app' and when I set the TERMINAL env to that value it finally worked.
The error message should list add iTerm.app as a supported terminal option instead of the iTerm2 and it should also tell people to trying check the value of $TERM_PROGRAM.
Even better the gogh.sh should be able to detect the terminal type with my machine and setup.

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on for so long, then it seems no one has the time to implement this.
Please reopen if you still encounter this issue with the latest version.
Thank you!

I would consider reopening this issue, if possible.
I can't seem to get it working on macOS Big Sur 11.6, and I am getting the same error as in the report above.
TERMINAL is unset and TERM_PROGRAM returns AppleTerminal.
Unlike in the above report, setting TERM_PROGRAM to iTerm.app just throws a new error:
No application knows how to open URL file:///Users/<obfuscated>/Monokai%20Dark.itermcolors (Error Domain=NSOSStatusErrorDomain Code=-10814 "kLSApplicationNotFoundErr: E.g. no application claims the file" UserInfo={_LSLine=1479, _LSFunction=runEvaluator}).

Thanks!

I also have the same problem as @vmdumitrache
@Mgldvd Please reopen.

Same problem on Mac OS 12.2 default terminal. No matter what I try (creating a "Default" profile or running as sudo) I get "Unsupported terminal".

Same problem on Mac OS 12.2 default terminal.
Default terminal is using xterm-256color which does support colors however it is not supported by Gogh.

@denniskb can you create a separate issue for xterm-256color support.

@alexwolf22 I am unable replicate this issue. What version of macOS and iTerm2 (echo $TERM_PROGRAM_VERSION) are you using? What does env output for TERM, LC_TERMINAL and COLORTERM?
@vmdumitrache TERM_PROGRAM is the application itself it's not the terminal per se. Could you provide the values of above variables?

For the original issue OP:
the error message has been updated in #442 to include the  iTerm.app string for use with TERMINAL=iTerm.app
To the others:
Do your issues are still happening with the latest version of Gogh and with TERMINAL=iTerm.app?

TERMINAL=iTerm.app working on Mac OS Sonoma and iTerm2.


Occasional input errors when running goto within Windows cmd.exe

Problem
On a very rare ocassion if start goto in cmd.exe and connect to a remote machine it may omit first keyboard symbol when typing ssh password, so you will need to type your password again. To reproduce:

Run cmd.exe;
Start goto and make sure you have at least 2 hosts;
Press up and down buttons;
Press Enter to connect to a selected host.

When you type your password (for a ssh key or for the host iteself) first time it won't be accepted.
Workaround
Run gg using powershell until this is resolved:

Right mouse on gg.exe, select "Send to Desktop" in order to create a shortcut;
Open the shortcut properties and update the target field: powershell.exe Start-Process 'C:\your_path_to\gg.exe' (make sure you use single quotes).

Filed a bug in bubbletea library project. This library is used to run external processes in goto.

I suspect that windows antivirus could be a contributing factor into this problem. Unfortunately this issue is very sporadic, which makes it hard to allocate. Clearly this has something to do with the parallel goroutine which bubbletea runs to to poll the input stream.

No longer reproducible after bubbleteat upgrade. Closing.


Allow super admins to destroy team memberships

https://trello.com/c/3yPlxHcR/43-allow-superadmins-to-remove-team-members

Clicking on the "Back to list" link takes me to "/memberships" route which doesn't actually contain a list of users - it looks like this:

Same thing happens when the "Save" button after change a permission for a user - it takes me to "/memberships/updated/permissions" route, which doesn't contains a list of users. It looks like this:

I'm not sure whether this is intentional though.

@robinmitra I think these are valid bugs, I'm not sure they were introduced in this PR though.

@robinmitra looking at the update action for memberships the redirect is fixed https://github.com/alphagov/govwifi-admin/blob/master/app/controllers/memberships_controller.rb#L10 to a specific path. I think this should be addressed in subsequent work.


Resume Template

A resume building template , simple and clean site.

Assign me in this issue.

I have made a resume template. Please assign me this issue.

@1ananya3 issue assigned to you.

I want to work on this under GSSOC2022. Can you assign it to me.

@1ananya3 you have already made 2-3 issues and haven't completed a single one, so I m assigning this issue to @adityabhatia17. Complete it asap!

On Sat, 12 Mar, 2022, 4:23 pm Kumari Astha Rani, @.***>
wrote:

@1ananya3 https://github.com/1ananya3 you have already made 2-3 issues
and haven't completed a single one, so I m assigning this issue to
@adityabhatia17 https://github.com/adityabhatia17. Complete it asap!
—
Reply to this email directly, view it on GitHub
https://github.com/arpit456jain/Cool-Front-End-Templates/issues/237#issuecomment-1065861584,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWQOODNFJSQ73IQN64BYUYDU7RZTVANCNFSM5PVCHFPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Is it completed? If not, reopen this issue when PR is ready


Viewer performance regressions

Seeing some viewer slowdowns in the new version, especially for larger structures. Will run a profiler on the Python side soon to see if there's an obvious culprit. Here are the serious issues:

Drawing large structures freezes the browser for as long as 30 seconds before loading (using chrome at least) - the old version renders in about 2-3 seconds:

m = mdt.from_pdb('1kbu')
mol = mdt.build_assembly(m, 1)
viewer = mol.draw(display=True)

In the above structure, clicking on an atom makes my browser freeze for about 10 seconds before the selection is rendered and the text box appears (<<1 second before merge):

Trajectory animations take a really long time to appear - and can actually crash the browser. This one (following on the previous example) freezes for about 3 minutes, then crashes my browser:

rotation = mdt.Trajectory(mol)
rotation.new_frame()
for i in xrange(20):
    mol.rotate(20.0 * u.degrees, [1,0,0])
    rotation.new_frame()
rotation.draw()

Trajectory animations take a really long time to appear. They also appear to lag behind the slider by a few seconds. Following on the previous example:

mol = mdt.build_dna_helix('ACTGCGTA')
rotation = mdt.Trajectory(mol)
rotation.new_frame()
for i in xrange(20):
    mol.rotate(20.0 * u.degrees, [1,0,0])
    rotation.new_frame()
rotation.draw()

Previous behavior: Viewer appears in 3-4 seconds. There's actually still a UI lag, but not as bad, even for larger molecules:

@avirshup I think I improved everything mentioned, should be at least as fast as before now...  Can you try it out and let me know what you think when you get a chance?  Two PRs:
https://github.com/Autodesk/molecule-3d-for-react/pull/9
https://github.com/Autodesk/notebook-molecular-visualization/pull/27

For my later reference:
I tried this, and initially couldn't get it to work, mostly because I wasn't smart enough to pull the companion PRs from the javascript libraries :(
With @justinmc's help, here's how I got it working:
git clone https://github.com/Autodesk/molecule-2d-for-react
git clone https://github.com/Autodesk/molecule-3d-for-react
cd /path/to/molecule-3d-for-react
git fetch
git checkout 3d-perf
git pull origin 3d-perf
npm run build
npm link
cd /path/to/notebook-molecular-visualization/js
npm link molecule-3d-for-react
cd ../
python setup.py jsdeps

Fixed with: https://github.com/Autodesk/notebook-molecular-visualization/pull/27


Update stuck at 69%

The update mechanism stops at 69%:

Maybe its a glitch somewhere, it counts:
33%, 43%, 33%, 41%,53%,64%, 69%

I am trying to figure that out myself.  I ended up re-installing on my computer, but I will keep an eye on it with new releases.

This appears to be fixed with the latest releases


Add bounding volume to eye dome lighting full screen command

If a command without a bounding volume is added to the command list the near/far will be set to the maximum possible range (1.0 to 500000000.0) and all four frustums will be rendered when log depth is disabled. This behavior makes sense because if you don't know where a draw command is you don't have enough information to contrain the near/far range. It's not good for performance though, which is why every draw command that CesiumJS pushes to a command list has a bounding volume.
There's one exception though: EyeDomeLighting pushes a viewport quad command which doesn't have a bounding volume. We would expect the scene to render with 4 frustums but this actually doesn't happen because EDL also pushes a clear command and this causes undefBV in createPotentiallyVisibleSet to be reset back to false. Basically the two bugs cancel each other out.
So the two fixes are:

In createPotentiallyVisibleSet: undefBV = !(command instanceof ClearCommand); should instead be undefBV = undefBV || !(command instanceof ClearCommand);
EDL sets the bounding volume of the draw command using the tileset's bounding sphere.

This fix doesn't have to be mentioned in CHANGES.md because the bugs were cancelling each other out before and there wasn't a noticeable problem.
@likangning93 can you review? There's way more text here than actual lines of code changed.

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks @lilleyse!


Update the donate buttons

Remove paypal and flatr.
Have a single button that will link to https://psfmember.org/civicrm/contribute/transact/?reset=1&id=44

In the future, we will also have GitHub Sponsor... so maybe we can add the second button to GitHub ... and a link to Tidelift... but for now, we should update the single button ASAP


modern-report-umfds:0.1.1

I am submitting

[ ] a new package
[x] an update for a package

Description: In this update, users can now set a custom image on the cover page of the report, providing more flexibility for personalization. We also fixed issues with the conditional display of the abstract and bibliography page, ensuring they only appear when relevant content is present. Additionally, the styling of headings has been updated to appear in bold, with added spacing below each heading to improve readability and the overall document structure.

Approved, those fixes are needed to make the template usable :^)

Thanks for the update, and sorry for the bot being so insistent. :sweat_smile:


Create  a Small Timer Toggle for the Timers Plugin

Create "small" timer and subsequent classes for UI

I think this would be better solved by overlay resizing and/or something at the infobox level to render them like this.

But the infobox level has no knowledge of what type of info box it is


Get vim-rooter to detect git worktree

Hi there,
I need to work on several branches of the same git repo at once. I have several branches checked out as worktrees in different directory. Unfortunately, it seems vim-rooter will set the cwd to the original checkout of the repo if I start vim in one of these worktree. Is there a way to configure it so that it sets the cwd to the root of the worktree instead?

Does adding !.git/worktrees to your g:rooter_patterns help?
let g:rooter_patterns=["!.git/worktrees", ".git"]

(From #110.)

Thanks so much for the quick response (and also the great tool!). Upon further inspection it might be an issue with fugitive. I noticed that during a cherry pick, on conflicts, the git status wasn't showing correctly in the fugitive git window. I thought it was related to rooter setting the wrong project directory but I'll have to look more into it.

You could uninstall vim-rooter and see if the problem is still there.  Or vice versa – uninstall fugitive.


chef-server-ctl user-create throws error if email address has a . in it

That's a legit email address, per the RFC if memory serves. Also the error message is nonsensical:
chef-server-ctl user-create foo John Q Public<EMAIL_ADDRESS>some_password*
ERROR: Conflict
Response: User 'foo' already exists
The user doesn't actually exist. If I give it a more normal-looking<EMAIL_ADDRESS>email address things work fine.

Hm, no, it's weirder than that... my own personal address<EMAIL_ADDRESS>also breaks it, but<EMAIL_ADDRESS>does not. Other variations of email addresses fail or succeed in a pattern I can't quite explain.

Hm, no, it's weirder than that... my own personal address<EMAIL_ADDRESS>also breaks it, but<EMAIL_ADDRESS>does not. Other variations of email addresses fail or succeed in a pattern I can't quite explain.

This is a critical bug for our project, rendering our chef-based tool undeployable for the typical user emails we see.

@rpattcorner @jstrange Apologies that you haven't gotten a response on this yet.  I'll be looking at this today and let you know what I find.  If you have time, I'd love if someone with a reproduction case of this could send me<EMAIL_ADDRESS>the contents of the /var/log/opscode/oc_erchef/ directory after the failure.

@rpattcorner @jstange A quick follow up.  In the cases you found, are you certain their are no other users with the given email address in the system.  The email address must be unique as well as the username.  Unfortunately, it appears the error message returned does not give you an indication that it is actually the error message that is failing:
vagrant@private-chef:~$ sudo chef-server-ctl user-create foo John Q Public<EMAIL_ADDRESS>some_password
-----BEGIN RSA PRIVATE KEY-----
[...SNIP...]
vagrant@private-chef:~$ sudo chef-server-ctl user-create foobar John Q Public<EMAIL_ADDRESS>some_password
ERROR: Conflict
Response: User 'foobar' already exists

Note that I don't have a user foobar in the system, but because the email address conflicts, I get the "Conflict" error message.

That explanation sounds like what I've been seeing. Definitely warrants a better error message...
What's the reasoning behind enforcing uniqueness with email addresses? It seems like a standard use case to have an admin identity that might conceivable be the same person as a regular user, strictly for management tasks. Also multiple users for the same person across orgs, though there are probably better ways to accomplish the latter.

@jstange The uniqueness constraint for email addresses was originally put in place for Hosted Chef where password reset (and perhaps other items) are tied to email addresses:
https://www.chef.io/account/password_resets/new
The same user account can be associated with multiple organizations, so normal users typically don't need more than one account; however, there are other use cases where it would be nice to use the same address for multiple accounts.
I'll open a new bug for the error message and then close this one out.

Roger that. We can work around for now by aiming our generic admin user at a local machine address or something. Thanks!

Closing in favor of: https://github.com/opscode/chef-server/issues/59

you may created the org-username my mistake, but every problem  has some solution.
sudo -s
chef-server-ctl org-delete learndevops        # learndevops is my org-name you may have different


Investigate Hashicorp usage

Goal
With the change of Hashicorp license, verify our dependency on their projects
CNCF resources
https://github.com/cncf/foundation/issues/617

cert-manager

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
lifecycle

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
metrics

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
scheduler

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>

Keptn v1 ticket: https://github.com/keptn/keptn/issues/9732