TS Server fatal error:  Debug Failure. False expression.

Issue Type: Bug
❗❗❗ Please fill in the sections below to help us diagnose the issue ❗❗❗
TypeScript Version: 4.6.3
Steps to reproduce crash

Use search and compare tree with 200 files
Compare files
Open some files

TS Server Log
❗Server logging disabled. To help us fix crashes like this, please enable logging by setting:
"typescript.tsserver.log": "verbose"

After enabling this setting, future crash reports will include the server log.
TS Server Error Stack
Server: semantic
Error: Debug Failure. False expression.
    at _loop_2 (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:169026:34)
    at ProjectService.assignOrphanScriptInfoToInferredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:169034:25)
    at ProjectService.assignProjectToOpenedScriptInfo (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:170700:26)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:170974:97
    at Object.flatMap (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:508:25)
    at ProjectService.applyChangesInOpenFiles (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:170974:41)
    at Session.handlers.ts.Map.ts.getEntries._a.<computed> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:172133:46)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:174069:88
    at IpcIOSession.Session.executeWithRequestId (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:174060:28)
    at IpcIOSession.Session.executeCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:174069:33)
    at IpcIOSession.Session.onMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:174095:35)
    at process.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:176730:31)
    at process.emit (node:events:390:28)
    at emit (node:internal/child_process:917:12)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:49:37.118Z)
OS version: Darwin arm64 21.4.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (4.59GB free)

Process Argv
--crash-reporter-id c0903e5b-9907-4c1a-8c69-fa0bfc3f4b9b

Screen Reader
no

VM
0%

Extensions (44)

Extension
Author (truncated)
Version

Bookmarks
ale
13.2.4

cucumberautocomplete
ale
2.15.2

ng-template
Ang
13.3.0

atlascode
atl
2.10.11

vscode-eslint
dba
2.2.2

gitlens
eam
12.0.5

vscode-html-css
ecm
1.11.0

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.24

prettier-vscode
esb
9.5.0

php-intellisense
fel
2.3.14

vscode-jest-runner
fir
0.4.48

auto-rename-tag
for
0.1.10

remotehub
Git
0.30.0

todo-tree
Gru
0.0.215

name-that-color
gui
0.1.6

batch-rename-extension
Jan
0.0.5

vscode-peacock
joh
4.0.1

vscode-colorize
kam
0.11.1

vscode-gutter-preview
kis
0.30.0

HTMLHint
mka
0.10.0

vscode-scss
mrm
0.10.0

remote-repositories
ms-
0.4.0

vscode-typescript-tslint-plugin
ms-
1.3.4

vsliveshare
ms-
1.0.5449

vsliveshare-audio
ms-
0.1.91

vsliveshare-pack
ms-
0.4.0

angular-console
nrw
17.15.0

vscode-nunjucks-formatter
oki
0.1.3

vscode-yaml
red
1.6.0

nunjucks
ron
0.3.1

vs-code-prettier-eslint
rve
3.1.0

angular-follow-selector
san
1.2.0

markdown-preview-enhanced
shd
0.6.2

sonarlint-vscode
Son
3.4.0

autoimport
ste
1.5.4

code-spell-checker
str
2.1.11

code-spell-checker-dutch
str
0.3.0

tabnine-vscode
Tab
3.5.42

highlight-matching-tag
vin
0.10.1

vscodeintellicode
Vis
1.2.18

quokka-vscode
Wal
1.0.455

twig
wha
1.0.2

html-css-class-completion
Zig
1.20.0

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30466689
pynewfile477:30463512

Thanks. Moving upstream so the TS team can investigate the perf issue

Thanks to you too Matt!

Op 7 apr. 2022 om 23:06 heeft Matt Bierner @.***> het volgende geschreven:

Thanks. Moving upstream so the TS team can investigate the perf issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

That's a weird type indeed 😂 but the call stack actually doesn't seem related to that - this is basically in the code that takes the set of open files and projects and determines which file belongs to which project. If you can find a way to reproduce that reliably, we'd want to fix it.

Hehe, I know 😆. But I really like the new possibilities! I'll enable the more complex types in a few weeks and will let you know if I have more info.

After upgrading to TypeScript 4.7.4 and Angular 14.0.5, I get similar issues. The compiler just hangs after saving the TypeScript file. Maybe it is an Angular or Webpack issue, I don't know and can't provide more information other than the previous types. Sorry! 😔


[Bug]: Duplicate names for sections in property pane of RTE widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
In a RTE widget there are two sections in the Property pane named Styles. Ideally one of them (which deals with label styling) should be named as Label Styles.

Steps To Reproduce

D&D a RTE widget.
Go to the property pane.

Public Sample App
No response
Version
Cloud

@keyurparalkar please add your RTE pr to this once you fix this issue

This issue has been fixed. Now we see Label Styles & Styles as two different sections in the property pane.

Moving it to Done.


refactor(iroh): remove the addr arg from start

Description
Removes the add from the start args as discussed internally. Reason for this is that it's currently not used. In reality, the port was not used. If we do add this back, most likely we want to also use the address to allow ipv6 listening nodes. In the spirit of removing code we opt for letting the code reflect how it's actually used in the moment
Notes & open questions
na
Change checklist

[ ] Self-review.
[ ] Documentation updates if relevant.
[ ] Tests if relevant.

/netsim branch arqu/drop_addr

This is the custom run: https://github.com/n0-computer/iroh/actions/runs/6974445664/job/18980130821
If it passes we should merge https://github.com/n0-computer/chuck/pull/47 and then this PR

Can you rebase on top of https://github.com/n0-computer/iroh/pull/1834?

rebased @Arqu but netsim is still unhappy

/netsim branch arqu/drop_addr

Ugh so a couple clarifications:

the CI PR I did doesn't work for summoning netsim-CI till it's merged into main

I merged that and we need to rebase this from main

Once rebased the CI will still be red on the PR but then we can check against the netsim tests with /netsim branch arqu/drop_addr

If all is good we merge the netsim PR and then your PR

To make life easier I'll check manually we can merge my PR and then your PR and be done with it, but I just want to test that the "invoke netsim from a fork" workflow works.

Can confirm it works in a manual test with netsim. Will just wait it out to test the comment based CI to see if it works. Can then proceed to merge stuff.

/netsim branch arqu/drop_addr


Check datamap headers prior to processing with datamap

The user needs to be reminded what the required headers are, or we may opt to have optional headers - for example "type" should be optional.

Improvements made in https://github.com/hammerheadlemon/bcompiler-engine/commit/c4da3d5476361b98d96e5e889645194de078bc92. Tested in suite, need to also include adapter exception handling, to pass the user nice messages.

Datamaps are now checked. Concluded in https://github.com/hammerheadlemon/bcompiler-engine/commit/2346525bb6f7c8d0ca1f0335f2c16512a4e14de4.


Multiple logins from the same computer blocked by Facebook.

Unable to login to more than 10 accounts from the same computer. Facebook forces you to change your password. Any solutions?
Login here to understand the error.
It's a service that lets you send messages from your pebble watch.

If this is consistent and repros in the browser, there's not much we can do about it on the api end unfortunately.

Same with me, Facebook IP bans. Change the IP and it should be fine. Sometimes anyway, I currently run from an AWS server so I made a new server and put it on that it didn't have the block message at first but a few days it did. May be due to the location as well, but I'm not entially aure.

@Schmavery I'll try to reproduce it on a browser.
@bobland1 Yeah, eventually, it will block new sign-ins. Thinking of using Tor-Requests in the library instead, so that it will keep cycling ip addresses.  Also looking into whether facebook drops these security measures when 2-factor login is enabled. In that case I can ask my users to just enable 2-factor.

Have you found out is 2F helps?

No.

Something that I found is that if you just keep trying to login, it will eventually let you in. Maybe after 20 tries but it still lets you in.

Our goal isn't to circumvent facebook rate-limiting/abuse prevention strategies. This api logs in as a user account and is treated as such by facebook's backend.


cli: add priority fee arg for idl commands

add priority fees to idl command so init/upgrade work during network congestion

Duplicate of https://github.com/coral-xyz/anchor/pull/2845


pls solve

undefined property: Maatwebsite\Excel\Excel::$firstRowAsLabel

I also get the same error in laravel 4.2.
ErrorException (E_UNKNOWN)
Undefined property: Maatwebsite\Excel\Collections\RowCollection::$rate_center
Could you help please!

Different issue. This means you have to loop one time more, so you get CellCollectiom as object. On that collection it's possible to get the rate_center.

Thanks,
Already I solved.


custom optimizer is not used in trainer.py

If you define a custom optimizer in a training_config to use it with the Trainer class, the optimizer is never used since  Adam is hardcoded as an optimizer. https://github.com/Hironsan/anago/blob/master/anago/trainer.py#L38

Same issue with  lr_decay and clip_gradients. I would suggest using only optimizer as parameter the same way keras handles it

In anaGo 1.0.0, this problem is solved.
Thanks!
Example:
model = anago.Sequence(optimizer='rmsprop')
model.fit(x_train, y_train)


Can't run electron on Flynn - /dev/shm: No such file or directory

I can't get electron to un on Flynn, when I try to I get the error in the following gist:
https://gist.github.com/kevinob11/4b8d1737d0b926e92ab83c4968d2741d#file-error-txt-L1
To repro the error I created https://github.com/praece/flynn-electron-nightmare-test, which includes nightmarejs, electron-prebuilt and xvfb. After creating the release I test by getting shell access using flynn run sh then entering the following commands:
$ Xvfb -ac -screen scrn 1280x2000x24 :9.0 &
$ export DISPLAY=:9.0
$ ELECTRON_ENABLE_LOGGING=true node_modules/electron-prebuilt/dist/electron

This appears to work fine when run in today's stable release that uses libcontainer instead of libvirt-lxc.

Great, we're going to spin a new cluster, migrate and test asap!

Fixed! Thanks!


Remove flag --no-dry-run for arduino-cli >= 0.14.0

Highlights from CHANGELOG.md

See CHANGELOG.md for more

@hel06492, Thank you for this PR. Could you give us a bit of background on why it is desirable or what problem it solves? Next, why tie it to an arduino_ci version? If it is desirable, why not have it take effect immediately? Presumably people using the old version will already have the legacy behavior. Thanks!

@jgfoster The --dry-run flag was removed from version 0.14.0 and as for version 0.19.0 arduino-cli no longer accepts the flag. It fails with the following error. I can't find the changelog, only a forum post about the change.
Compiling Blink.ino for arduino:avr:mega:cpu=atmega2560...
Last command:  $  /usr/bin/arduino-cli --format json compile --fqbn arduino:avr:mega:cpu=atmega2560 --warnings all --dry-run /home/salaryman/Arduino/trial.errors/Blink/examples/Blink/Blink.ino
Error: unknown flag: --dry-run

The version check is for older versions which might give unexpected behavior without the --dry-run flag.
Please let me know if there are more things I need to fix/add for this pull request. Thanks.

@hel06492, I think some of my confusion is that the change refers to arduino_ci (Continuous Integration) while it appears that it should refer to arduino_cli (Command Line Interface). Could you update the title and other text in the PR and comments in the code to make that clarification? Thanks!

Hi @jgfoster @ianfixes
Thanks for the suggestions. I've made changes according to those feedbacks.

@hel06492 Have you selected "allow edits from maintainers" on your PR?  I can probably take care of the remaining issues.

@ianfixes yes, it's already checked

@ianfixes, I'm going through the open PRs and wonder if this can be merged. Thanks!

I've merged this with a larger body of work in #334 -- thanks!

This has merged as part of #334 and was released in v1.4.0


Simplify quadilateral_area + better doc

I changed to human numbering 1, 2, 3,...
I think the formula a1 + a2 + a3 + a4 is exact so no need to update that. I did update the docs a bit to be truthful to what quadrilateral_area does. Have a look @ashjbarnes, thanks!

Together with #65 this PR resolves #39.

Looks good thanks Navid! Yeah this function is one I borrowed and was really opaque earlier


Rule 942151 has false positive on "left"

Description
This is very similar to #3721. The word "left" can trigger false positives. An example is "Take a left (1 mile)".
How to reproduce the misbehavior (-> curl call)
curl -i -H "x-format-output: txt-matched-rules" https://sandbox.coreruleset.org/?test=Take+a+left+(1+mile)

HTTP/1.1 403 Forbidden
Date: Wed, 26 Jun 2024 12:48:44 GMT
Content-Type: text/plain; charset=iso-8859-1
Transfer-Encoding: chunked
Connection: keep-alive
X-Unique-ID: ZnwOLKE6cEZzRGum1iCCDgAAAEE
x-backend: apache-nightly
x-crs-last-commit: none

942151 PL1 SQL Injection Attack: SQL function name detected
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=5-0-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=5, XSS=0, RFI=0, LFI=0, RCE=0, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)

Your Environment

CRS version (e.g., v3.3.4):  4.3.0
Paranoia level setting (e.g. PL1): PL1

Confirmation
[X] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

Thank you for the report.
We don't think this false positive is very common (like in #3721).
I would say it's best to tune this in your configuration with:
SecRuleUpdateTargetById 942151 !ARGS:test

@ssigwart let us know the above provided solution fixed your. I'll wait a few days before closing this issue.

@Xhoenix, I didn't use that suggestion because the false positive could appear on a large number of fields and it was also too broad of an exclusion. I did find a way to work around it though.

@ssigwart If your consider your problem resolved, then you can close this issue.

Sure. I'll close it. I do feel like this is a false positive that could be fairly common for other people, but it's not affecting me anymore since I have rules to work around it.


support window is now only two releases

Support window is actually two release not three
/assign @upodroid @krsna-m

Linter issue fixed in - https://github.com/knative/toolbox/pull/26

/override "style / Golang / Auto-format and Check"


Adx 723 validation workflow

This PR significantly improves the validation UI ready for the 22 Estimates.

Nicer badges that give clearer information
Animated throbber in the badge for those jobs still running.
Asynchronous update of badges if the validation job is incomplete at the point of loading the page. based on 5s polling of the api.
Clear link to the view the validation report "View Error Report" if validation errors or fails.
Auto open all error details in the report so that they are not hidden.
Clearer layout of validation badges in pages.

The approach I've taken here is to amend the existing implementation rather than redesign (it would definitely benefit from a redesign!) Validation doesn't have any JS tests in place.  I have updated the python tests that are affected by this commit, though they are currently skipped due to a CKAN2.9 oddity.

Could you have a look at the github actions py tests and either fix them or mark failing test @pytest.mark.skip(reason="no way of currently testing this")?

@tomeksabala Tests are sorted and passing for this PR.


GD crashes when I open the level edit

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
Geode Version
v2.0.0-beta.25
Mods Installed
geode.loader v2.0.0-beta25, geode.texture-loader v1.5.0, prevter.openhack v2.3.0
Steps to Reproduce

When i play a level, i press esc key
then i  click into the level edit
The game crashes

Crash Report
[2024-05-07_12-20-21.log](https://github.com/geode-sdk/geode/fi
Geode 2024-03-27 12.54.47.log
les/15234142/2024-05-07_12-20-21.log)
Additional Information
this is likely caused by some mods but i dont know

I am having the exact same problem, here is my crash issue: https://github.com/geode-sdk/geode/issues/763

turn off no wave trail pulse

stale, reopen if needed


Red Flash Animation

Current Behavior
In 1.19.4, the red flash animation broke due to EntityEffect.HURT breaking in code.
Expected Behavior
Entity should flash red when damaged
Steps To Reproduce

Damage an entity

Version and Log
Going to break my own rules here...
Anything else?
https://github.com/PaperMC/Paper/pull/9037

https://hub.spigotmc.org/stash/projects/SPIGOT/repos/bukkit/pull-requests/858/overview
I made a PR with spigot to get this issue fixed

PR is implemented in Spigot, and is working in 1.20.1+


Using GitHub Actions to Auto-Deploy Docs

The point of this PR is to ensure that we are always auto-deploying the latest docs to our public website.  And GitHub Pages makes this doable. Please see the new docs.yaml to see how I did this.
I also added a new tox -e docs that people can use to build the docs, and ensure that they have the right version of Sphinx and everything else to make that happen.  (Because Sphinx has some versioning issues.)
The bottom line is the docs now build and work. Though they still throw a bunch of warnings and even a couple errors, but I figure we make it work first, then clean it up.
Please note that I tested if this auto-deploy works a bunch of times, and it seems to.  See the example here.

UPDATE: I have added the ACCESS_TOKEN to the TerraPower GitHub organization.  I believe this is sufficient to allow this PR to work.
Full Disclosure, I did a lot of testing to make sure it would work. But I now realize that I wasn't testing inside an organization. I don't see any reason that should matter.

Can we not dry run the action from a branch? You should have permissions to push to a feature branch on the honest-to-goodness terrapower/armi repo

Can we not dry run the action from a branch? You should have permissions to push to a feature branch on the honest-to-goodness terrapower/armi repo

Ah, I have permissions now! Yeah, I can give that a try.
I did a dozen dry runs on my own copies of these repos, so it's not untested. But I can test and see if the tokens work differently in an org, sure.

@youngmit  I have confirmation that the deploy system works.  I made a copy of this PR's branch into the OG TerraPower ARMI repo and GitHub Actions auto-deployed the docs.
Look here:  https://terrapower.github.io/armi/user/user_install.html#prerequisites
And notice that it says:

You must have the following installed before proceeding:

But it used to say:

You must have the following before proceeding:

The word "installed" is added in this PR, as a proof-of-concept.


Add Prometheus pull consumer support for custom endpoint /mgmt/tm/sys/ha-status

Add Prometheus pull consumer support for custom endpoint /mgmt/tm/sys/ha-status
In TMOS there is a useful API endpoint /mgmt/tm/sys/ha-status that reports when any critical services are experiencing an issue. The API endpoint reports No when services are healthy and yes when an issue is experienced.
Currently, the Prometheus pull consumer is not able to include these metrics when added as a custom endpoint.
Describe the solution you'd like
When API endpoint /mgmt/tm/sys/ha-status is added as a custom endpoints definition, have TS scrape the endpoint /mgmt/tm/sys/ha-status and report either a failure 0 or 1 for each critical service that is being monitored.
 A product in maintenance mode continues to receive support and ensures its stability with regular critical fixes and security updates. This maintenance approach helps maintain the longevity and reliability of the product for the long term. Enhancement requests for this product will be evaluated on an individual basis, taking into consideration their overall impact and alignment with our business objectives. Only those with a strong case for improvement will be considered for implementation. There is no plan to deprecate this product. If you have a business case for this, please let me know and I will let you know how to contact us. Thank you


Document cluster's kubeconfig location and name

In the documentation in README.md there's no mention where the cluster's kubeconfig is located or how to retrieve it. Presently, It happens to be in the cluster's directory under the name admin.conf.

PR https://github.com/SUSE/skuba/pull/938 merged, ready to stage


Change event dot position

Is there anyway I can change the event dot position.

Use calendarView.appearance.eventOffset to change the event dot position


Migration to Flex Clusters

Hi there.
In the last weeks MongoDB started to inform customers about changes to the types of clusters they offer.

Active M2, M5, and Serverless clusters will be automatically migrated to a Flex cluster, beginning January 2025 for M2/M5 and March 2025 for Serverless. MongoDB has planned this to be a seamless transition with an emphasis on:
Zero impact on your operations
No changes to your connection strings or application code
Seamless transition to a flexible, tiered pricing model (see pricing details above)

and

Customers can use existing programmatic methods to create M2, M5 and Serverless tier clusters until January 2025. However, the behavior of these programmatic methods is scheduled to change in January 2025 as set forth below:
M2/M5 APIs will create Flex clusters instead of M2 or M5 clusters.
Serverless instances APIs will create Flex clusters instead of Serverless instances
Please note that these programmatic methods will be EOL’d in January 2026.

Here is a link to the documentation for IaC tools: https://www.mongodb.com/docs/atlas/flex-migration/ which also states:

API endpoints for Serverless Instances will begin managing Flex clusters in January of 2025. You can continue managing your existing Serverless instances using these APIs. Existing Serverless instances will be migrated to Free clusters, Flex clusters, or Dedicated clusters, according to your usage, after March 2025

I am using a Serverless Instance via pulumi-mongodbatlas => https://www.pulumi.com/registry/packages/mongodbatlas/api-docs/serverlessinstance/
Looking at the docs I mentioned, I already wonder: Serverless Instances get migrated in March 2025 but the API Endpoints start managing Flex Clusters in January 2025. What happens if I do a deployment in February 2025?
Are there any plans on how these changes will be implemented in this package (e.g. will there still be the same ServerlessInstance that does the correct calls to generate a flex cluster or will this be a breaking change)? Will there be a guide on how to migrate? Can this be handled by pulumi without a complete redeployment (which would be "the horror")?
Thanks in advance.

@hffmnn this provider bridges the upstream Terraform provider. The Mongo team is busy implementing support for Flex clusters:
https://github.com/search?q=repo%3Amongodb%2Fterraform-provider-mongodbatlas+flex&type=pullrequests
Looking at the merge date of these pull requests, these didn't make it in the latest release of their provider. Once the Mongo team creates a new release, the Pulumi team can update this provider too.


Using this within Angular

Has anyone been able to integrate this within their angular7 web app?
I was able to import and link everything, but the panzoom button is not appearing for me.
I've done something like the following in one component:
import cytoscapePanzoom from "cytoscape-panzoom";
import * as $ from "jquery/dist/jquery.min.js";

...

cytoscapePanzoom(cytoscape, $);
cy.panzoom(defaults); // defaults from the README

I added the css files (font-awesome and cytoscape-panzoom ones) within the index.html
Is there something else I'm missing?

were you able to get this working?

No solution at the moment

Hi, I've successfully integrated cytoscape-panzoom in an Angular (v.11/12) application.
The steps to make it works are:

declare the variable require, which is a function, to import the plugin via CommonJS

declare var require: any

this function is provided by webpack which is built-in in Angular;

require cytoscape-panzoom in your component

const cytoscapePanzoom = require('cytoscape-panzoom');

at this point the plugin works, but it doesn't see its CSS. This can be solved by exposing the .css files in angular.json

  "styles": [
              "src/styles.css",
              "./node_modules/cytoscape-panzoom/font-awesome-4.0.3/css/font-awesome.min.css",
              "./node_modules/cytoscape-panzoom/cytoscape.js-panzoom.css"
            ],

the remaining configuration (like registering the plugin) is the same.

For any doubt I created a simple repository in my GitHub:
cytoscape-panzoom-in-angular

Result

Hi, I've successfully integrated cytoscape-panzoom in an Angular (v.11/12) application.
The steps to make it works are:

declare the variable require, which is a function, to import the plugin via CommonJS

declare var require: any

this function is provided by webpack which is built-in in Angular;

require cytoscape-panzoom in your component

const cytoscapePanzoom = require('cytoscape-panzoom');

at this point the plugin works, but it doesn't see its CSS. This can be solved by exposing the .css files in angular.json

  "styles": [
              "src/styles.css",
              "./node_modules/cytoscape-panzoom/font-awesome-4.0.3/css/font-awesome.min.css",
              "./node_modules/cytoscape-panzoom/cytoscape.js-panzoom.css"
            ],

the remaining configuration (like registering the plugin) is the same.

For any doubt I created a simple repository in my GitHub:
cytoscape-panzoom-in-angular
Result

Why use require in frontend code? I can confirm this package does not work by the way "Import"


Consider removing the Task.usesService requirement

As stated in issue #22888, Gradle is requiring that if a task uses a build service, then users must declare an association between the two via the Task.usesService API (or the @ServiceReference annotation).
This requires a lot of work for the users, so it would be helpful to offer some explanations on why this is necessary, for example:

What is the impact on correctness and performance between declaring Task.usesService/@ServiceReference and not declaring it (other than the current failure from Gradle)?
Can Gradle fulfill this requirement automatically for the users? For example, after Gradle finishes a task's configuration, it can check all the task's properties to see if any properties are RegisteredBuildServiceProvider, and if so, automatically calls Task.usesService directly without requiring the users to do it. Note that in this way, Task.usesService is entirely an internal Gradle concept, and users don't need to know about it.

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

We can relax the explicit declaration requirement for services that do not limit the usages.

Thanks, that would be great. That would make it easy for users to meet the requirement, with or without help from Gradle.

For 8.12, we are actually disabling the deprecation warning altogether: https://github.com/gradle/gradle/pull/31419
Some reasons: we are lacking mechanisms for declaring service usage for things other than tasks, and we do not enforce max parallel usage at configuration time (which can now be parallel via org.gradle.configuration-cache.parallel).


Use typed-rest-client 1.0.7 to allow toolLib.downloadTool to work with redirects.

Background
While trying to download a tools exe from Github releases using toolLib.downloadTool I got the following error: UnhandledPromiseRejectionWarning: Error: Unexpected HTTP response: 302. Github was redirecting met to an AWS blob which seems perfectly fine to me but toolLib.downloadTool only accepts HTTP 200.
Change
I updated typed-rest-client to 1.0.7 to allow toolLib.downloadTool to work with HTTP redirects.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: sanderaernouts sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@sanderaernouts Thanks for taking the time to do a PR, we appreciate it! This module relies on the typed-rest-client which we also own. We recently made changes here to have that client handle redirects. It's a lower level client that should have that responsibility. I think if we simply update this module to point to the latest typed-rest-client it should resolve your issue.
Since you already started working on this and investigating do you want to give that a try and see if it works?

@stephenmichaelf  sure thing. I updated typed-rest-client to 1.0.7 and added some test using https://httpbin.org to test the redirect status codes work with downloadTool.

@stephenmichaelf sure thing. I updated typed-rest-client to 1.0.7 and added some tests to verify the redirect status codes work with downloadTool. I did not change the statuscode back to statuscode == 200 because there are other 2xx status codes that indicate success.

Thanks for taking the time to make these adjustments, it is much appreciated.
LGTM.
@bryanmacfarlane if you agree I am fine merging this.

Bump @bryanmacfarlane.

Thanks!

I will release after lunch :)

I published 0.5.1

Thanks!


feat: (IAC-1386) EncryptAtHost changes for NIST

Changes:
This PR adds EncryptAtHost requirements in the VMs and AKS nodes.

Virtual machines and virtual machine scale sets should have encryption at host enabled.
Temp disks and cache for agent node pools in AKS clusters should be encrypted at host.

This is an optional features, to enable encryption at host for nodes and VMs you would set the following variables:

Name
Description
Type
Default

enable_vm_host_encryption
Setting this variable enables all of the disks (including the temp disk) attached to this Virtual Machine be encrypted by enabling Encryption at Host. This setting applies to both Jump and NFS VM.
bool
false

vm_disk_encryption_set_id
The ID of the Disk Encryption Set which should be used to Encrypt this OS Disk. This setting applies to both Jump and NFS VM.
string
null

aks_cluster_enable_host_encryption
Enables host encryption on all the nodes in the Node Pool.
bool
false

aks_node_disk_encryption_set_id
The ID of the Disk Encryption Set which should be used for the Nodes and Volumes. Changing this forces a new resource to be created.
string
null

By default, when using AKS, OS and data disks use server-side encryption with platform-managed keys. The caches for these disks are encrypted at rest with platform-managed keys. You can specify your own managed keys following Bring your own keys (BYOK) with Azure disks in Azure Kubernetes Service. The caches for these disks are also encrypted using the key you specify.
When using customer-managed-keys, ensure you have the proper AKS credentials. The managed identity needs to have contributor access to the resource group where the diskencryptionset is deployed. Otherwise, you'll get an error suggesting that the managed identity does not have permissions.
Also, make sure the VNet of your deployment has access to the Key Vault which has the diskencryptionset.
Note: Adding the subnet service endpoints makes the process smooth.
Tests:

Scenario
Description
Order Cadence
Verification

1
Defaults, no changes
Fast 2020
Transparent to user, no changes

2
Set enable_vm_host_encryption = true, aks_cluster_enable_host_encryption = true
fast:2020
Encryption at host enabled with platform-managed keys on VM and nodes in nodepools

3
Set enable_vm_host_encryption = true, vm_disk_encryption_set_id = "<disk_encryption_set_id>", aks_cluster_enable_host_encryption = true, aks_node_disk_encryption_set_id = "<disk_encryption_set_id>"
fast:2020
Encryption at host enabled with customer-managed keys on VM and nodes in nodepools

Are these breaking changes? I see where we are adding items into the node pool definitions and how the vms are being created as well.

No not breaking change. The default values are set for the variables as false and null, which guards this. So it doesn't affect the existing user.


Add the sender email and add a suitable subject

Adding the sender mail in nodemailer function to<EMAIL_ADDRESS>and adding relevant subject.

Hey, when I upstream the master branch, the utils folder doesn't contain email,js file in which I have to update changes. How to resolve this?

Try pulling once. I don't see a reason why it doesn't contain the email.js file else.

Complete it fast , I have another job for you.

I will complete it by tomorrow evening. Thanks for the patience.


Make plugin compatible with Matomo 4

Hi, hope you are doing well!
Matomo 4 is progressing steadily and it would be great if this plugin was also available for it.
Migrating the plugin should be pretty simple as there were not many breaking changes.
You can find the migration guide here: https://developer.matomo.org/guides/migrate-matomo-3-to-4
It boils down to:

update your dev environment to 4.x-dev
update your plugin.json (new major version of the plugin and require >=4.0.0-b1,<5.0.0-b1)
check that everything still works fine
commit this to a new branch (e.g. 4.x-dev) and make this branch the default in the github settings
tag and push a new release to publish it to the marketplace

If you later fix a bug and also want to backport it to the 3.x plugin, you can cherry-pick the commit to the old branch, release a new version (lower than the one for 4.x) and publish it and 3.x users should get this update.
If you have questions about anything, just ask me!

@Findus23 I've just published 2.0.0 version with >= 7.2.5 for PHP and >= 4.0.0-b1 for Matomo. Feel free to test it out, everything should work fine.

Hi,
Many thanks for the update. It seems to be visible on the Marketplace.


Improve search engine

Search songs by matching artists, works, tags
Use mini language to specify search field.
ex:
artist:<artist name>
work:<work name> (alternative: <work_type>:<work name>)
title:<song title>
#<tag>

Partial matching by default, switch to strict matching with quotes
ex:
artist:"<artist name>"

Search query without keywords searches in any fields

Maybe use (shlex)[https://pymotw.com/2/shlex/] more intensively.

Alternative work search not implemented.
Done in 2684ade3f52808f65e91c2de439328efbf94d64c 6e608941e717275624367b2e53ad27d3529f0130
ec48cefcd03e33247b4720f6a3a433cebbda8e5a.


401 unauthorized for “/.auth/login/aad/callback” with external tenant

Describe the bug

We get a 401 unauthorised page after successfully(?) logging in with an account of an external tenant in our web app. We get it on the “/.auth/login/aad/callback” redirect. It does correctly work with ourselves as a tenant.
To Reproduce
Steps to reproduce the behavior (see below for set-up that works):

The external organization registers an app registration with user.read() rights, id_tokens, creates a secret and sends us the application ID, tenant ID and secret value.
The external organization adds our domain and our domain + “/.auth/login/aad/callback” as web redirect URIs.
In our static web app azure configuration we set the AZURE_CLIENT_ID value and the AZURE_CLIENT_SECRET value to the one given by the external organization

"auth": {
   "identityProviders": {
     "azureActiveDirectory": {
       "registration": {
         "openIdIssuer": "https://login.microsoftonline.com/{EXTERNAL_ORGANIZATION_TENANT_ID}/v2.0",
         "clientIdSettingName": "AZURE_CLIENT_ID",
         "clientSecretSettingName": "AZURE_CLIENT_SECRET"
       }
     }
   }
 },

After a user (from the external organisation) logs in he gets redirected to the “/.auth/login/aad/callback” he sees a “401 Unauthorized” microsoft page.

Expected behavior

We have a static web app hosted on azure
We have implemented custom authentication
We want a single tenant to be able to log in
When we test this with ourselves as single tenant we set the staticwebapp.config.json as:

"auth": {
   "identityProviders": {
     "azureActiveDirectory": {
       "registration": {
         "openIdIssuer": "https://login.microsoftonline.com/{OUR_TENANT_ID}/v2.0",
         "clientIdSettingName": "AZURE_CLIENT_ID",
         "clientSecretSettingName": "AZURE_CLIENT_SECRET"
       }
     }
   }
 },

We create an app subscription with id_tokens enabled and the microsoft graph user.read() rights enabled.
We create a secret in the app subscription and copy the secret VALUE and the app subscription APP ID
In the static web app configuration we define 2 variables named “AZURE_CLIENT_ID” and “AZURE_CLIENT_SECRET”, we give these the values of the secret and the app id.
We add our website name and our website name + “/.auth/login/aad/callback” as Web redirect URIs.
After doing this we can successfully log in on the front end, and this login is restricted to ourselves as a tenant.
When using '/.auth/me' authInfo.clientPrincipal we can verify that the user was correctly logged in

Screenshots

Device info (if applicable):

All devices

Additional context
Replicating the problem for our organisation (our own tenant and application id):
We are able to replicate the problem in our organisation when in the static web app configuration we intentionally set a wrong AZURE_CLIENT_SECRET secret value. This had led us to double check and reset the secret value with the external organization but this did not help.

I personally encountered the 401 response when using https://login.microsoftonline.com/organizations/v2.0. Swapping organizations out for an explicit tenant guid worked. This didn't solve my issue because I need users from different tenants to be able to sign in. So I tried common instead, which works without producing a 401 callback response.


core-app-api: fix and release accidental createApp type breakage

The only change in this release is a fix for the accidental breakage of the createApp from @backstage/core-app-api. The  previous release brought in the deprecation of createApp from @backstage/core-app-api in favor of the one from @backstage/app-defaults. The intention was to keep the existing deprecated function intact, but it mistakenly received changes to both the parameters and return type which have now been reverted.

In case anyone encounters this and is looking for an immediate fix, the more proper long-term one is to move over to importing createApp from @backstage/app-defaults. This is just to make sure bumping core-app-api doesn't result in type errors

Ah nice, yeah that loiks better.
Maybe document the command / process used for posterity?

@freben Can walk through it perhaps, but essentially it's

Run yarn release
Only commit the stuff that you want in the release

It's 2 that's a bit tricky to document x)


[Bug] Storage shows 100% used

https://pastebin.com/axeA8CTN - yarn output
compose config
dash:
image: mauricenino/dashdot:latest
restart: unless-stopped
privileged: true
ports:
- 8086:3001
environment:
- DASHDOT_ENABLE_CPU_TEMPS = true
- DASHDOT_SHOW_HOST = true
- DASHDOT_ENABLE_STORAGE_SPLIT_VIEW = true
- DASHDOT_ALWAYS_SHOW_PERCENTAGES = true
volumes:
- /etc/os-release:/etc/os-release:ro
- /proc/1/ns/net:/mnt/host_ns_net:ro
- /mnt:/mnt/host_mnt:ro
- /media:/mnt/host_media:ro
I've tried removing the last two lines separately but it still doesn't work. Removing media, shows the bpool drive as free.  ADding it back shows it 100 used
https://i.imgur.com/Z4qNDeI.png
I only have 1 drive on the host and it's using zfs.

https://i.imgur.com/GT5k232.png
without those two volumes this is what  see

🎉 This issue has been resolved in version 4.0.0
Please check the changelog for more details.


TableView.ScreenToCell returns rows passed the end of the table

For example the following code example (see below).  Workaround is to apply this check in user code i.e.  && clicked.Value.Y < tv.Table.Rows.Count.

tv.MouseClick += (e)=>
{
    if(e.MouseEvent.Flags == MouseFlags.Button3Clicked)
    {
        var clicked = tv.ScreenToCell(e.MouseEvent.X,e.MouseEvent.Y);
        if(clicked.HasValue)
        {
            MessageBox.Query("Right Click",$"You clicked {clicked.Value.X},{clicked.Value.Y}","Ok");
        }
    }
};

Ok looks like it is already fixed in https://github.com/tznind/gui.cs/commit/965255b1a751034b7690fb1d994c8388b752c28c#diff-cabc06df9590a035dadf256277de6facda529d77c24898509033704c9f32c43bR1041-R1043
Which was merged in https://github.com/gui-cs/Terminal.Gui/pull/2239 (3 months ago)
I must have been running an old code base when I encountered this bug.


Added Less support.

Choose in wizard between Sass and Less support for stylesheet mangement. (2nd try)

Hard fight. Spend more time struggling with git itself than with the code. But this is my learn curve. :-)

As expected bootstrap 4 went with sass.


.json  extension should not be mandatory at export operation

fixed with https://github.com/jrichardsz-software-architect-tools/stressify/pull/14


ASAlaunch fails in nanoserver

Describe the bug
Running ASALaunch.bat on a Windows nanoserver 1809 (using the container version) does not
trigger any collectors.
To Reproduce
Steps to reproduce the behavior:

Create a dotnet core 2.2 nanoserver container and start a command prompt using:

docker run -it -u ContainerAdministrator mcr.microsoft.com/dotnet/core/sdk:2.2-nanoserver-1809 cmd

On the command prompt, execute the following to download ASA:

curl -o ./asa.zip -OL -G https://github.com/microsoft/AttackSurfaceAnalyzer/releases/download/v2.0.154%2B303aa9fef5/AsaCli-win-2.0.154.zip

Create a directory to unzip

mkdir app
cd app

Unzip

tar -xvf ../asa.zip
cd AsaCli-win-2.0.154

Run ASA

AsaLaunch.bat collect -all

Observe that nothing happens. Process terminates immediately

Expected behavior
ASA will start the collection process
System Configuration (please complete the following information):

OS: Windows
OS Version: Windows 10 1809
Application Version: -2.0.154
CLI or GUI: CLI

Additional Context
Add any other context about the problem here.

Reopening after editing the docker run command to specify a dotnet core 2.2 base image

Are you having issues running the exe directly?  You don't need to use the script.

I tried running the exe directly and the same happens, it terminates immediately

Thanks.  We did not test on nanoserver so I suspect as is it something basic isn't supported. I will keep this on the list to investigate.

Sounds great, thanks Gabe!

This now works for me with the following steps. Note that User, Service and Firewall collectors don't work on Server Core, it appears the WMI mechanisms we're using aren't supported.  Also, I've identified a bug in the registry collector so it will also currently crash (once #299 is fixed you'll be able to run "Cclfpr" to collect the most amount of data, or alternately just use -a and have the incompatible collectors ignored).
docker run -it -u ContainerAdministrator mcr.microsoft.com/dotnet/core/sdk:3.0-nanoserver-1903 cmd
curl -o ./asa.zip -OL -G https://github.com/microsoft/AttackSurfaceAnalyzer/releases/download/v2.1.28-beta%2B7e04a764f9/Asa-win-2.1.28-beta.zip
mkdir app
cd app
tar -xvf ../asa.zip
cd Asa-win-2.1.28-beta
AsaLaunch.bat collect -Cclfp


make check on OpenBSD fails (15/140)

=======================================
   fwup 0.17.0: tests/test-suite.log
=======================================

# TOTAL: 140
# PASS:  125
# SKIP:  0
# XFAIL: 0
# FAIL:  15
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: 038_write_15M
===================

|                                    | 1% (0.20 / 15.00) MBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-038_write_15M.test'
FAIL 038_write_15M.test (exit status: 134)

FAIL: 039_upgrade
=================

|=================================== | 99% (152.56 / 152.56) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-039_upgrade.test'
FAIL 039_upgrade.test (exit status: 134)

FAIL: 045_legacy_require_partition1
===================================

|=================================== | 99% (152.56 / 152.56) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-045_legacy_require_partition1.test'
FAIL 045_legacy_require_partition1.test (exit status: 134)

FAIL: 052_file_concatenation
============================

|==============================      | 85% (130.70 / 152.05) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-052_file_concatenation.test'
FAIL 052_file_concatenation.test (exit status: 134)

FAIL: 073_multistep_fat
=======================

|                                    | 1% (0.15 / 15.16) MBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-073_multistep_fat.test'
FAIL 073_multistep_fat.test (exit status: 134)

FAIL: 074_fat_cache_fail
========================

|=========                           | 25% (1.18 / 4.58) MBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-074_fat_cache_fail.test'
FAIL 074_fat_cache_fail.test (exit status: 134)

FAIL: 075_big_fat_fs
====================

|=                                   | 4% (0.66 / 15.00) MBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-075_big_fat_fs.test'
FAIL 075_big_fat_fs.test (exit status: 134)

FAIL: 082_uboot_upgrade
=======================

|=================================== | 99% (152.56 / 152.56) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-082_uboot_upgrade.test'
FAIL 082_uboot_upgrade.test (exit status: 134)

FAIL: 085_raw_memset
====================

|=================================== | 99% (259.58 / 262.14) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-085_raw_memset.test'
FAIL 085_raw_memset.test (exit status: 134)

FAIL: 095_sparse_apply
======================

fwup: Unsigned archive '/home/niko/tmp/fwup/tests/work-095_sparse_apply.test/fwup.fw' is not corrupt.
/home/niko/tmp/fwup/tests
fwup: Unsigned archive '/home/niko/tmp/fwup/tests/work-095_sparse_apply.test/new.fw' is not corrupt.
|=================================== | 99% (7.17 / 7.17) KBpthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
|====================================| 100% (7.17 / 7.17) KB
Success!
Elapsed time: 0.003s
|===                                 | 9% (0.84 / 9.24) MBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-095_sparse_apply.test'
FAIL 095_sparse_apply.test (exit status: 134)

FAIL: 109_includes
==================

|===============================     | 87% (130.70 / 150.00) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-109_includes.test'
FAIL 109_includes.test (exit status: 134)

FAIL: 110_compression_level
===========================

|=========                           | 26% (128.78 / 493.57) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-110_compression_level.test'
FAIL 110_compression_level.test (exit status: 134)

FAIL: 111_streaming_exit_fast
=============================

./111_streaming_exit_fast.test[27]: timeout: not found

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-111_streaming_exit_fast.test'
FAIL 111_streaming_exit_fast.test (exit status: 127)

FAIL: 125_trimmed_upgrade
=========================

|=================================== | 99% (152.57 / 152.57) KBAbort trap (core dumped)

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-125_trimmed_upgrade.test'
FAIL 125_trimmed_upgrade.test (exit status: 134)

FAIL: 131_raw_key
=================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
43+0 records in
43+0 records out
43 bytes transferred in 0.000 secs (394495 bytes/sec)
86+0 records in
86+0 records out
86 bytes transferred in 0.000 secs (601399 bytes/sec)
/home/niko/tmp/fwup/tests
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
fwup: Signed archive '/home/niko/tmp/fwup/tests/work-131_raw_key.test/fwup.fw' is not corrupt. Pass a public key to verify the signature.
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
pthread_mutex_destroy on mutex with waiters!
fwup: Error reading or decoding public key from file '/home/niko/tmp/fwup/tests/work-131_raw_key.test/fwup-key.pub.unpadded'

Test failed!

Leaving test work files in '/home/niko/tmp/fwup/tests/work-131_raw_key.test'
FAIL 131_raw_key.test (exit status: 1)

What version of OpenBSD are you running? I don't regularly run OpenBSD, so if there's anything else I should know to reproduce these issues, could you let me know that as well.
Also, if you happen to know whether there's an OpenBSD CI server that I can use to automate testing of fwup I would most appreciate it.
As a final note, if you're just creating .fw files on OpenBSD, you should be fine even with those test failures. The failures all look like they're verifying the more rarely used features.

Ok, I went through and fixed all of the OpenBSD failures. This was unbelievably helpful as it pointed out several subtle, but legit issues. Thanks for bringing this to my attention!


Add Sandcastle example for new Montreal Point Cloud ion asset

This adds a Sandcastle example exploring the new ion asset we just added, the Montreal Point Cloud:
http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/montreal-sandcastle/Apps/Sandcastle/index.html?src=Montreal Point Cloud.html&label=ion Assets
It has some nice stored views but also a little system for exploring the classification. I think this acts as a nice template we can easily re-use for any new point clouds that come with classification information (or any new ion assets in general to share stored views of it).

Thanks for the pull request @OmarShehata!

: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.

@hpinkos this is ready. I don't think the AppVeyer build failure is relevant tot his PR. It builds and deploys fine on Travis.


SEC New Fair Access Limit

First of all, thanks a million for this great downloader! And, I would like to ask, how can we integrate the new SEC user agent requirement to the code? Thank you for your time!

Hey Kedimamasi,
I have updated the code to hate the option to customize request-headers, however I am still getting 'Your Request Originates from an Undeclared Automated Tool' from SEC.
Personally, I would say this code this deprecated and I would advise against using it as it need a lot of polishing but rather use the SEC API instead: https://www.sec.gov/edgar/sec-api-documentation, it is more efficient and flexible. I just don't have the time to work out it.
thanks!


Configure Github Actions

https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow#

https://github.com/actions/upload-artifact


[WIP] Use the same registration order inside the packs register API as we do in st2-register-content

This pull request fixes pack register API endpoint to register different resource type in the exact same order as we do in st2-register-content.
Not registering it in the same order could cause different issue:

Output which it not consistent with st2-register-content. This could be confusing because both scripts fail on failure on default, but they could fail with a different error in case a different resource is used (e.g. one fails with an error inside action metadata first and other fails with an error inside rule)
Rules could get registered before sensors / triggers which would cause an error (trigger doesn't exist)

This addresses an issue indirectly reported in https://gist.github.com/lakshmi-kannan/6493c0d303df0622145730cf6b8e2b22. @lakshmi-kannan reported an issue, but it looks like a problem lied elsewhere (it was an "old" bug unrelated to my changes) which is nevertheless still a good catch :+1:
TODO

[ ] Tests

While working on this I encountered another "issue" - well, it's not an issue because the same behavior exists in register content and it has been then since the begining, but it's something we might need to document or similar.
Right now, we only register "dependent" resources when registering actions and rules - we also register runners when user requests to register actions and we register rule types when user requests to register rules.
Keep in mind that this only applies when user requests to register a single resource type.
Another thing we could do (but it's debatable and maybe current behavior is fine since it has been like that from the beginning) - when user requests to register just rules we could potentially also register other dependent types - notably sensors and triggers.
Imo though, this is not the best behavior, especially because sensors also contain actual sensors in additional to triggers.

Current coverage is 77.46% (diff: 100%)

Merging #3108 into master will increase coverage by 0.10%

@@             master      #3108   diff @@
==========================================
  Files           430        430
  Lines         22144      22145     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          17130      17154    +24
+ Misses         5014       4991    -23
  Partials          0          0

Diff Coverage
File Path

•••••••••• 100%
st2api/st2api/controllers/v1/packs.py

Powered by Codecov. Last update d878a62...35e9fe9

For other supposed bug (not a bug, same behavior existed since the beginning), please refer to the comment here - https://gist.github.com/lakshmi-kannan/6493c0d303df0622145730cf6b8e2b22

The reason why pack.install doesn't fail, but pack register and st2ctl reload --register-all do is because packs.register action only registers actions, aliases and sensors by default (see packs.load action metadata). It has been like that since the beginning and nothing has changed and exact same behavior existed before the packs API change.

So until we decide how to proceed there is nothing for me to do with regard to that - one option would be to update packs.load to register all resource types, but again, this is a "breaking" change since it changes an old default behavior so probably not a good idea to do it in v2.1.1.

Note: This only applies if pack github is not already installed, if it's installed this error won't appear of course.


Improve readme

This explains how the build should be set up to actually use this rule
as a source generator.

Needs adjusting after publishing


I see this error       TypeError: unsupported file type: undefined (file: undefined), after 11 -> 12 migration, can you help me?

How did you solve this?

This worked for me:
In next.config.js:
const withImages = require("next-images");

module.exports = withImages({
  images: {
    disableStaticImages: true,
  },
});

And then, in the images I had with src={StaticImage.src}, I changed them to src={StaticImage}.
Then, I also had a vscode warning about static images types, which I solved with this.


Windows 10 creators update

Since I installed the windows 10 creators update the miner keeps hanging at i  12:40:12|stratum  Received new job #ab1eaf5d.
Is there a way to get more details about the issue? I also notice there is no activity on my GPU.
Please let me know how I can provide additional details to make this miner work again on Windows 10 Creators update.

It seems that it is mining on my onboard graphics card since the update (at least it tries to do so, but it freezes). How can I make sure the right graphics card is used for the mining?


cant open file gyb.py

extracted gyb on mac to a sub-folder in the home directory and when i try to run the python3 gyb.py --email<EMAIL_ADDRESS>--action estimate it gives this error /usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python: can't open file 'gyb.py': [Errno 2] No such file or directory
in the gyb folder extracted there is only a gyb executable, cant see any gyb.py in it.
i installed the  gyb-1.33-macos-x86_64-MacOS10.14.4.tar.xz on my mac running 10.15.2

This is the expected behavior. Just execute gyb binary and don't worry about Python, it's built-in to that gyb binary. If you want to use your own Python download the src archive instead of the MacOS binary.

thanks.
for the benefit of newbies: to execute the gyb binary from terminal run this command ./gyb --email<EMAIL_ADDRESS>--action estimate


De-duplicate common service specs, fix chef-vault data bag item test fixture

Many integration test suites contained a duplicate copy of the dependency_spec.rb specs. I have moved this into test/integration/helpers/serverspec/service_dependency_spec.rb, added test/integration/helpers/serverspec/spec_helper.rb and updated the remaining suite-specific specs to include these.
I've also attempted to fix failures seen in #401 by removing the encrypted_data key and empty string value from test/integration/vault/data_bags/sensu/config.json. @martinisoft can you comment on the change here? It's unclear to me why this one liner was added in bbc973b94a49c383b34f2726c78fc8d202999a28 but it seems to be the source of failures now.

LGTM


Add Telink dependencies to vscode Docker image

Problem
https://github.com/project-chip/connectedhomeip/issues/8843
Change overview
Add Telink dependencies to Dockerfile of vscode
Testing
Manually:

Build docker image
Run docker image
Check if following command able to build examples for all platforms:
$ ./scripts/build/build_examples.py --platform all build

/gcbrun


Sort out various etcd make targets

There are a number of make targets that should be removed:
run-etcd-st....  possibly others
Need to check that run-etcd and run-etcd-host are correct too

This should include standardizing all of our make targets across all the repos and updating them to deploy v3.


Declare working dependency version with go.mod

Some sort of incompatibility was introduced between moq and whatever version of golang.org/x/tools/go/packages I happened to have in my $GOPATH that resulted in moq failing with odd errors (see #98).
I was able to fix this by updating my copy of the dependency to the current version, though it took a bit for me to think to do that. Adding a go.mod file will ensure that builds of mod are done against a working version of golang.org/x/tools/go/packages, especially in Go 1.13+ which will have modules on by default.
Resolves #98.

Ideally, should this change be merged, the resultant commit would be tagged with a version tag like v1.0.0.

What's blocking this at the moment?

Thank you @tylerchr for the PR but I had to make a few more changes to migrate to Go modules and did so in #135.


Error: "Specified method is not supported" in VS 2017

I have an Asp.Net Core project referencing my own lib, which is dependent on another library. I have all 3 projects opened in one solution, referencing the dependencies via NuGet. When I try to switch from NuGet to Project reference, I get the following error:
"Specified method is not supported."
Please let me know what I am missing.
Thanks.

NuGetReferenceSwitcher does not work with the new csproj format (i.e. PackageReference tags). It only works with the old full .NET Framework projects... I'm working on new tools to support .net standard and .net core

See https://github.com/RSuter/DNT


Put route labels above map labels

Since they're off by default, make them visible most often if turned on

It already isn't below any other layers


Added password-generator to js-projects

Here is the password generator project

Useful app @IbrahimOlayinka .

@namangupta1399 @jomefavourite please check this project out.
The functionality .....

@namangupta1399 thank you


python: engine implementation

Description:
All header changes in this PR come from https://github.com/envoyproxy/envoy-mobile/pull/1217, that should be reviewed and merged first.
This PR implements all of the engine-related classes, like Engine and EngineBuilder.
Risk Level: Low
Testing: N/A, will follow up when everything is finished with e2e testing + unit testing in Python and/or C++
Docs Changes: N/A
Release Notes: N/A

Waiting on this to be updated with executor change.

Waiting on this to be updated with executor change.

Should be ready for review now. I changed it to no longer depend on the executor, but because there's no trampoline class any longer we have to explicitly take the GIL when we execute the callback since it's coming from another thread. That's just represented in the same ..._shim function pattern I had in the headers defn.

Should be ready for review now. I changed it to no longer depend on the executor, but because there's no trampoline class any longer we have to explicitly take the GIL when we execute the callback since it's coming from another thread. That's just represented in the same ..._shim function pattern I had in the headers defn.

rebased onto main bc of BUILD problem

rebased onto main bc of BUILD problem

Once BUILD conflicts are resolved, I can merge this.

Once BUILD conflicts are resolved, I can merge this.


ORDER BY results in empty results, cmd query tool

What version of Genji are you using?

$ genji version
Genji v0.14.0
Genji CLI v0.14.0

Same behaviour with Boltdb/Badgerdb. To be clear, this is only in the genji cmd tool; I'm not seeing issues using the Genji API.
What did you do?
Using the command line query tool:
Example data:

select * from person limit 1;
{
"sid": "af879a5vfpdad6wd",
"firstname": "Bolt0",
"lastname": "Smith",
"primaryemail"<EMAIL_ADDRESS>}

Example query without ORDER BY
genji> select sid, firstname from person  limit 5;
{
"sid": "af879a5vfpdad6wd",
"firstname": "Bolt0"
}
{
"sid": "af879a5vfpdad6we",
"firstname": "Bolt1"
}
{
"sid": "af879a5vftdad6wf",
"firstname": "Bolt2"
}
What did you expect to see?
5 documents, ordered ASC or DESC
What did you see instead?
FAILing query - it doesn't matter what field or direction the order by is issued, always empty N results.
genji> select sid, firstname from person ORDER BY  sid limit 5;
{}
{}
{}
{}
{}

Thanks for reporting, I managed to reproduce it. I'll investigate and release a fix soon

This has been fixed by v0.14.1, you can run:
go get github.com/genjidb/genji@latest
go install github.com/genjidb/genji/cmd/genji@latest


When my code is formatted, some single quotes are canceled.

like this

The Images are not working. :)

@daidaishuo please provide steps to reproduce. Best is a GitHub repository we can clone that demos the problem.

@daidaishuo I'm guessing you are using prettier-vscode extension that formats your code to double quotes? If that's the case you can set prettier.singleQuote to true.
If that's not the case, feel free to do Help -> Report issues from VS Code to create a new issue with reproduce steps.


Data Preprocessing

The data scientists at BigMart have collected 2013 sales data for 1559 products across 10 stores in different cities. Also, certain attributes of each product and store have been defined. The aim of this data science project is to build a predictive model and find out the sales of each product at a particular store. Using this model. BigMart will try to understand the properties of products and stores which play a key tole in increasing sales The data has missing values as some stores do not report all the data due to technical glitches, Hence, it will be required to treat them accordingly


[FEATURE] Restore integration test stability

Requirements
Changes to flagd's sync mechanisms have caused the integration tests to become unstable. Investigate & eliminate points of instability.

The problem is that the tests replace the contents of the flag configuration file with the amended configuration (to test that cache has been invalidated). In doing this, flagd receives the change event, pulls the contents of the file, sees that the file is empty (it hasn't been written to yet), interprets this as an empty state and invalidates all of the cache. Then the configuration gets written to the file and flagd interprets the event correctly.
Potential solutions:

Rerun tests on failure (slow)
Retry retrieval if file is empty
Run the tests against the flagd binary directly (it seems that the slowness of the write/retrieval comes from the mounting of the file to the docker volume)


[data_loader] Optionally also propagate set_epoch to batch sampler

What does this PR do?
When training with the transformers Trainer or related (Sentence Transformers, SpanMarker, SetFit, etc.), set_epoch is called on the dataloader. This is propagated down to the dataloader.batch_sampler.sampler if that has a set_epoch , but not to dataloader.batch_sampler.
This prevents epoch-specific generator seeding in custom batch samplers, such as the ones that are common in Sentence Transformers: https://sbert.net/docs/package_reference/sentence_transformer/sampler.html
See also https://github.com/UKPLab/sentence-transformers/issues/3069 by @antigregory which showed that set_epoch in my Batch Samplers is not called like I expected them to be.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
@muellerzr (p.s. get better soon!)

Tom Aarsen

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Can you confirm it fixes your issue?

It does indeed. I think I can write a test to go alongside this PR.

Tom Aarsen

This test roughly mirrors my use case and should act as an effective test to make sure ST should work. Feel free to update it if e.g. you don't normally use Accelerator in the data_loader tests.

Tom Aarsen


Reinstall WSL Arch Linux

How do I reinstall WSL Arch Linux? Is there such a possibility?

yes, it's possible.
run arch.exe clean and arch.exe install.
this will remove all archwsl data and install from scratch.

yes, it's possible. run arch.exe clean and arch.exe install. this will remove all archwsl data and install from scratch.

ty so much.


Add deploy start & success notifications & multiple slack channel support

Summary

Add deploy start notification #3
Update readme with info for newer versions of Trellis + variable name updates
Add git username #4
Add a link to the deployed site env. URL
Add a link to the deployed commit on GitHub for quick lookup (if using GitHub, otherwise show git sha as before)
Simplify message into a single line for quick scanning (after a couple deploys the longform messages cause quite a bit of scrolling)
Ignore errors, so deployments do not fail #8
Multiple Slack channels/organisations support - #9

Preview

Awesome idea!

@TangRufus I've updated this a little further as Slack now doesn't allow one webhook to post to multiple channels, at least when creating a new App. My changes allow a channel to be notified per site, per environment, as well as notifying multiple channels per deploy (Mike's change). I've also moved the slack deploy token to vault. There's a PR up for @mike-sheppard here (#3) - I figured it was best to merge into his changes first but I can PR direct if that's easier.
Feedback welcome from all 👍

@dalepgrant I'd definitely prefer merging the work from you and @mike-sheppard in one to simplify tagging the next release - so hopefully we can move forward with that.

@codepuncher happy to help, let me know if you need anything more from me.
Same to you @mike-sheppard 👍

@dalepgrant I can see that you've submitted a PR here, so I guess we'll just wait to hear back from @mike-sheppard

Sure thing, that should be sorted now 👍🏻

Cheers, @mike-sheppard. I'll try and get this tested this week. Thanks again for the PR!

Hey @codepuncher any issues during testing? Let me know if I can do anything to get this merged in.
Nice one!
Mike


What to do with species aggregate

There are three taxa defined with rank "species aggregate":

Callitriche obtusangula/platycarpa (160 observations)
Nasturtium officinale/microphyllum (2 observations)
Nitella flexilis/opaca (2 observations)

Possible solutions:

do not map them
include them at genus level (e.g.  "Nitella flexilis/opaca" becomes "Nitella")
use the first taxon (e.g. "Nitella flexilis/opaca becomes "Nitella flexilis")

I would not map them as they are because the rank "species aggregate" doesn't exist and the double taxon will never be recognized by the GBIF taxonomic backbone.

Please include them and use taxonRank speciesAggregate (available on https://rs.gbif.org/vocabulary/gbif/rank_2015-04-24.xml). For waarnemingen.be we use the taxonRank multispecies for these, which is not a correct use. I'm curious to see how speciesAggregate will be handled by GBIF.

Thanks @peterdesmet. However, I cannot find clear instructions on how to write such species. From your link I read:

An aggregate may be denoted by a group name interpolated in parentheses.

But I do not understand how to do it.  Something like this?
Callitriche obtusangula/platycarpa -> Callitriche (obtusangula,platycarpa)

I would leave those names as is for now. It's an interesting question on how to write these though (and with what rank), maybe good to ask in GBIF portal-feedback

Thanks @peterdesmet. Issue posted: https://github.com/gbif/portal-feedback/issues/4014


Can't find Xbox Wireless Controller via bluetooth

Hi,
I'm trying to setup Xbox Wireless controller via bluetooth. But when I search, it doesn't find it. Updated the controller to the latest firmware via Windows. Not sure how to debug this, any ideas?

If you're using secure boot make sure you've enrolled our signing key, the Xbox driver necessary can't load otherwise.

just did it by extracting the keys from windows registry (there is an archlinux documentation about it). Now it pairs and connects but steam doesn't detect it.

Make sure you're in the input group, if not add yourself to it.
Let me know if that fixes it for you and I'll automate this step in future releases.

thank you @KyleGospo yeah it fixed it.

https://github.com/ublue-os/bazzite/commit/b57ff42462eafffefc6b6a5a82123a0af7d8e736


[Warning] -Wparentheses on line 555 on single_include

The following warning appears (I am using Clang 6.0):
/home/travis/build/KratosMultiphysics/Kratos/external_libraries/json/json.hpp:19250:15:   required from here
/home/travis/build/KratosMultiphysics/Kratos/external_libraries/json/json.hpp:555:45: warning: suggest parentheses around ‘&&’ within ‘||’ [-Wparentheses]
         std::is_constructible<typename ConstructibleObjectType::key_type,
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         typename object_t::key_type>::value and
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
         std::is_same<typename object_t::mapped_type,

The line on the code is:
https://github.com/nlohmann/json/blob/f102df3cba1036d81ef5f344ebabe5cefa797cc9/single_include/nlohmann/json.hpp#L555
Thank you very much

Thanks for reporting! I already fixed this two branches that should be merged soon. I'll leave this issue open until the fix reached the develop branch.

Thanks

Before fixing it - @theodelrieu - is
    static constexpr bool value =
        std::is_constructible<typename ConstructibleObjectType::key_type,
        typename object_t::key_type>::value and
        std::is_same<typename object_t::mapped_type,
        typename ConstructibleObjectType::mapped_type>::value or
        (has_from_json<BasicJsonType,
         typename ConstructibleObjectType::mapped_type>::value or
         has_non_default_from_json <
         BasicJsonType,
         typename ConstructibleObjectType::mapped_type >::value);

correct and only needs parentheses?

Hurray, thanks a lot


Command with no output and a non-zero exit code breaks terminal tab.

Windows 10: 1903, 1803
WSL Distros: Ubuntu, Artix
Shells: fish, bash
Extraterm 0.46
A command with no output and a non-zero exit code replaces the line where the command was typed with a frame. The content in the tab stops responding to input. Nothing can be typed or displayed, and right click doesn't open up the context menu. Attempting to blindly type commands does not seem to actually do anything if checking for processes in another tab. Removing the frame works, but the tab remains unresponsive to other input.
Edit: This still happens when there is output from the command (either stdout/stderr). After the command with the non-zero exit code, pressing enter on an empty line produces the error. If other commands are typed after the non-zero command, the shell keeps working.
Extraterm 0.45
The frame is displayed, and pressing enter on an empty line frames the empty line itself instead of just printing the next empty prompt in the shell. The tab still functions otherwise.
Screenshot from 0.46:

Screenshot from 0.45:

I'm not super familiar with the code, but I finally got around to running it from source. I've narrowed down the breaking issue. Here's where the isEmpty check is failing for me. For some reason my empty command has a range.end.row value of -1.
For example purposes only (since I gave no thought as to what else it could impact), I threw in a quick check to see where that would get me. The terminal no longer breaks completely, and it's back to showing a bunch of empty frames when I press enter (since the return code is still 1) like in version 0.45.
src/TerminalDocument.ts:
const isEmpty = range.start.row === range.end.row && range.start.column === range.end.column;
const shouldBeEmpty = range.start.row === -1 || range.start.column === -1 || range.end.row === -1 || range.end.column === -1;
if ((newText.length === 0 && isEmpty) || shouldBeEmpty) {

I haven't quite narrowed down the repeating, empty frames when pressing enter after the last command exited non-zero, but I'm thinking it will be around here.
src/render_process/Terminal.ts:1155
if (returnCode === "0" && ! this._commandNeedsFrame(this._lastCommandLine, moveTextLines.length)) {

After running a successful command, pressing enter goes to a new line, keeping the previous line, but when the last command was non-zero, it removes it and tries to frame it, even when there's no command, output, or status code. There should be some condition to skip this and other areas to get an empty command to behave the same as it does when the last exit code was zero.
src/render_process/Terminal.ts:1172 (removes the empty command from the screen)
this._lastCommandTerminalViewer.deleteLines(this._lastCommandTerminalLine);
this._lastCommandTerminalViewer = null;

So far, this has been the simplest solution that resolves most of the issues I've been having.
I'm still having framing issues after running the clear command, but overall my terminal is much more reliable. I haven't yet tried running the Extraterm tests with my changes.
--- a/extraterm/src/render_process/Terminal.ts
+++ b/extraterm/src/render_process/Terminal.ts
@@ -1152,7 +1152,9 @@ export class EtTerminal extends ThemeableElementBase implements AcceptsKeybindin
       }

       let moveTextLines = this._lastCommandTerminalViewer.getTerminalLinesToEnd(this._lastCommandTerminalLine);
-      if (returnCode === "0" && ! this._commandNeedsFrame(this._lastCommandLine, moveTextLines.length)) {
+      // TODO: Add settings to always frame zero and/or non-zero returnCode.
+      //       Until then, respect framing rules on all return codes.
+      if (! this._commandNeedsFrame(this._lastCommandLine, moveTextLines.length)) {
         // No need to frame anything.
         this._lastCommandLine = null;
         this._lastCommandTerminalViewer = null;
@@ -1169,7 +1171,10 @@ export class EtTerminal extends ThemeableElementBase implements AcceptsKeybindin
       this._disconnectActiveTerminalViewer();

       // Extract the output of the failed command.
-      this._lastCommandTerminalViewer.deleteLines(this._lastCommandTerminalLine);
+      if (moveTextLines.length > 0) {
+        // Only delete lines of output, not the command itself.
+        this._lastCommandTerminalViewer.deleteLines(this._lastCommandTerminalLine);
+      }
       this._lastCommandTerminalViewer = null;

       // Append our new embedded viewer.
@@ -1187,7 +1192,7 @@ export class EtTerminal extends ThemeableElementBase implements AcceptsKeybindin
       outputTerminalViewer.setReturnCode(returnCode);
       outputTerminalViewer.setCommandLine(this._lastCommandLine);
       outputTerminalViewer.setUseVPad(false);
-      if (moveTextLines !== null) {
+      if (moveTextLines.length > 0) {
         outputTerminalViewer.setTerminalLines(moveTextLines);
       }
       outputTerminalViewer.setEditable(true);

I would imagine it would be good to have an option to select if good/bad commands always get framed. For example: if someone wanted to easily notice failed commands, always frame non-zero. In that case, ignoring the returnCode for empty commands would keep it from being too obnoxious.

I just want to add a couple of observations after using 0.46 with my modifications. This is while framing commands if output is longer than 1 line. Side note, that setting seems to frame commands if output is >= 1 line.
After running the clear command, my commands don't get framed initially, but after running additional commands with enough output to fill the screen, commands start being framed again. When my commands are being framed, reset doesn't clear the screen. It just goes to the next line like a command without output would. But, when I've got the framing issue after running clear, reset causes the clear command's full screen of blank output to display in a frame, then subsequent commands are framed successfully.
In fish, running a for loop to echo 1 through 5, with each number on a new line and a sleep after the echo, the output is displayed in-line as if it isn't going to be framed. It then gets removed and framed when the command finishes. On bash, 1-4 display in-line without a frame, then a frame is displayed containing only the number 5, with the previous non-framed lines still displayed. If you take away the sleep, fish frames all the output and bash doesn't display a frame. I first noticed this type of behavior running ssh-copy-id. Unlike the for loop with echo, both fish and bash display the ssh-copy-id output without a frame, then the text is removed and all output displays in one frame.
These were the commands I used:
for i in (seq 1 5); echo $i; sleep 1; end
for i in (seq 1 5); echo $i; end

for i in $(seq 1 5); do echo $i; sleep 1; done
for i in $(seq 1 5); do echo $i; done

This issue is now at the top of my TODO list. thanks for the patience @Kynolin
One comment so far:

I haven't quite narrowed down the repeating, empty frames when pressing enter after the last command exited non-zero,

This sounds like a really one know bug/limitation. If I remember correctly, the shell integration will report a non-zero result each time you hit enter on an empty command line after a command failed. Each CR looks like a command which failed. This might be shell specific too. It's a separate (but related) issue than the main problem here.

@Kynolin

I would imagine it would be good to have an option to select if good/bad commands always get framed.

At the moment I think it should always frame failed commands, reason being that failed commands is typically infrequent and if it does happen it is something which should get the users attention (with a big red frame).

This sounds like a really one know bug/limitation. If I remember correctly, the shell integration will report a non-zero result each time you hit enter on an empty command line after a command failed. Each CR looks like a command which failed. This might be shell specific too. It's a separate (but related) issue than the main problem here.

That's the behavior I get on both bash/fish. Pressing enter on an empty line uses the same exit code as the last command.

At the moment I think it should always frame failed commands, reason being that failed commands is typically infrequent and if it does happen it is something which should get the users attention (with a big red frame).

That's how I prefer it too, minus pressing enter on an empty line (or a line containing nothing but whitespace) and getting a bunch of empty red frames. I figured I'd at least mention having the option.
I've still been using my modified version since I apparently have a habit of pressing enter more than I realized, so no rush on my account. Besides the slightly odd behavior of when output gets converted to frames, it's been working well enough to get by without breaking tabs accidentally.

The crashing bug is fixed in 0.47.0. Thanks. I understand the other problems better now and can attempt a solution.

Awesome, thanks! Seems to be working as expected so far. Would you prefer that I close this issue and create a new one referencing the unexpected framing behavior I noticed? Or, is there another issue already?
Fish seems pretty good but still has issues framing after the clear command, until output has filled the screen. Bash is a little worse still.
This gets framed in bash.
echo -e "1\n2\n3\n4\n5"

This does not get framed. Each line also has a very small delay in being displayed, so you can actually see each individual line be rendered one at a time. I was using frame output if longer than 3 lines. If I change it back to 1, only the line containing 5 gets framed.
for i in $(seq 1 5); do echo $i; done

@Kynolin  yes, please make a new issue. It helps keep things a bit more organised and there is less chance of things falling through the cracks.

Sounds good. I've created #229 for the unexpected framing behavior.


Haskell Extension Pack does not work without additional steps

I'm looking to create further PRs for the Haskell Feature, but before I do I want to check that I'm on the right path.
Is editing the install.sh and devcontainer-feature.json files directly in this repo the right approach? I observed a conversation about cookie cutter and generating these files, but I'm not sure I'm following the vision for the future.
I'm new to Haskell and learning a little bit of it through Exercism. I want to try it out in a container in VS Code using what appear to be the most popular plug-ins, the Haskell Extension Pack. Does it fit with the design goals for this repo for me to add steps and change defaults so that the base Haskell Feature supports the following scenario?

Open a fresh directory with a simple "Hello World" Haskell program in VS Code.
Execute the Add Dev Container Configuration Files command
Choose Ubuntu with the default jammy version.
Add the Haskell Feature listed.
Select Reopen in Container.
Find the "Haskell Extension Pack" extension and choose to Install it in the Dev Container.
Open the HelloWorld.hs file and benefit from the extensions without further action needed.

At present, when I complete the steps above, I see a prompt to download hls-<IP_ADDRESS> and also that hlint cannot be found.

Agreeing to install HLS results in further errors because of version mismatches.

I didn't save my steps, but I got everything working previously and believe I can set up the Haskell Feature to run these extensions out of the box.
@danielbraun89, before I do so: is that a desirable set of changes? If it affects your answer, I'm also planning to do something similar for additional languages that have Exercism tracks (such as Clojure, Elixir, and Scala).

Thanks, I'll take a look. I will say this, though: I wasn't looking to add docs but to modify the Feature so that the VS Code extensions work out of the box.
I'm really interested in the Features because I've found myself taking two or three Dockerfiles and copy-pasting from them to create the Dockerfile I want. Even in my current use-case, however, I'd like to create a custom Dev Container for running VS Code that has git and my Exercism CLI installed and configured (once for all languages/tracks) and then adds a specific language Feature depending on which track I open.
I'll see if I can just open a PR to make clear what I'm thinking since it at least sounds like my effort won't be wasted.

I wasn't looking to add docs but to modify the Feature so that the VS Code extensions work out of the box.

@DaneWeber Sorry for the misunderstanding on my part 😬. That sounds like a good idea, though 👍!

It doesn't seem like the CLI respects TERM=dumb, 2> stderr.log or > stdout.log. Even with all those, it still outputs a mess. But! The good thing is that it doesn't "clear the screen" like the TTY terminal does. Thus, this works:
devcontainer features test -f jest 2> stderr.log

It shows something like this:
[1 ms] @devcontainers/cli 0.25.2. Node.js v16.18.1. linux 5.4.0-1094-azure x64.
[484 ms] Start: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-codespace/container-features/0.25.2-1670050215072 --build-arg _DEV_CONTAINERS_BASE_IMAGE=ubuntu:focal --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-1670050214548-6a9d9fccd3ecec4aec72582743637f90-features -f /tmp/devcontainercli-codespace/container-features/0.25.2-1670050215072/Dockerfile.extended /tmp/devcontainercli-codespace/empty-folder
[+] Building 0.0s (0/0)
[+] Building 0.1s (1/2)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 998B                                       0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 0.2s (2/2)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 998B                                       0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
[+] Building 0.4s (2/3)
 => [internal] load build definition from Dockerfile.extended              0.1s
 => => transferring dockerfile: 998B                                       0.0s
 => [internal] load .dockerignore                                          0.1s
 => => transferring context: 2B                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1.4               0.1s

Which, yes, is a mess; but it DOES contain all the info! It's just messed up with some blue coloring prefix characters.


The Wiki wrongly mentions that the version on Kali is deprecated

Hello, I've been reading the Wiki https://wiki.porchetta.industries/getting-started/installation/installation-on-unix#apt-package-kali-linux-only and it says:

APT package Kali Linux only
Not recommanded as the version on Kali is deprecated

May I kindly ask you to remove this mention? In Kali Linux, like in most distros, the packages are updated by maintainers, according to the time available. Sometimes it's up-to-date, sometimes it's not. But a general statement like "version on Kali is deprecated" doesn't make any sense.
If you insist on such warning, it should apply to packages from distributions in general, not just Kali Linux. You could make a section "Install a package from your distribution", then mention that packages provided by the distributions might not always be up-to-date, then list all the distributions that provide a package for crackmapexec (like you already do).
If I look at https://repology.org/project/crackmapexec/versions, I can see that at the moment, Kali and Pentoo provide an up-to-date package, while BlackArch's package is slightly outdated.
If there's a Git repo for your wiki, I'll be happy to submit a MR, just let me know the URL of the Git repo.
Thanks in advance!

Hello, you right, I've updated the Wiki to put the warning on other distros.
The reason I put the warning is that distro cannot follow up with the release, I got issues that are already fixed in it's a time killer plus people complaining about your project about something already fixed is not great for the mental and for the image of the tool.
Regards

Hi @mpgn, and thanks for the quick reply.
I must say the change you made is a bit unfortunate. The wording "is deprecated" is misleading. The packages are not deprecated, neither in Kali, neither in any of the distributions that you list in the Wiki. It might be out of date at times, but that's very different from being deprecated. Apologizes if it was not clear in my first message.

What's your definition of 'deprecated' ?
Mine is that: the version is not supported anymore, no support will be provided for this version and running this version is not recommanded

Good question. For me, deprecated is something that is on the way out. If I want to drop a functionality in a library, I mark it as deprecated, and after some time (long enough), I will remove it. The purpose of deprecation is to announce that something will be removed.
But the point is that I can only deprecate the stuff that I develop myself, I can't deprecate stuff developed by other people. For example, if my program supports X, I can "deprecate support for X", that doesn't mean X is deprecated, it's only the support for X in my program that is deprecated. Hope it makes sense...
But to be back on the topic: if you don't want people to install CME from their distro, then you can just drop all the sections for Kali/BlackArch/Pentoo in the wiki? Why mention it in the first place? Optionally, leave a note such as "We do not recommend installing from the package manager because X or Y"...
I'm from the other side of things, I'm a Kali developer, and the advice we give is pretty much the opposite, we advise our users to always install via the package manager. And the reason we do so is pretty much the same reasons you invoked above: « issues that are already fixed and it's a time killer plus people complaining about your project about something already fixed is not great for the mental and for the image of the tool ». Exactly that :)

Hi, I can absolutely see both of your points, but is there maybe another way to solve it?
I agree with mpgn that it is really annoying to see the same tickets over and over again, because the bugfixes are not already pushed to the repositories. Is there maybe a way to automate the release?
For example as soon as mpgn releases a new binary (e.g. the latest bug fix with a point release) the binary gets uploaded to apt (or however it works).

I've updated the working to avoid the word "deprecated" :)

For example as soon as mpgn releases a new binary (e.g. the latest bug fix with a point release) the binary gets uploaded to apt (or however it works).

Well, if it was "automatable' it would be automatic already! Updating the apt packages is rather straightforward, but needs to be done by someone (ie. human being), in order to have a look at the changes, update dependencies if needed, and a whole bunch of other things. It might be that unit tests won't pass with the new version, so it will require time to investigate test failures and fix it. Sometimes it can be quick, sometimes not.
And in the end it's an issue of manpower, at Kali we're a small team and we maintain many packages. If a package doesn't get updated, it's because we're busy doing other things and we didn't have time to update it. If it really takes too long, that's fine to ping us via the bugtracker of course.

I've updated the working to avoid the word "deprecated" :)

@mpgn Thank you for the update. I noticed that the wording "the version on Kali" was copy/pasted as is, also for Pentoo and BlackArch. I would have said « Not recommended as the version might not be up-to-date » but anyway.
Thanks for your time on that! I'm closing the issue.

Updated


strip installer binary

reduce binary size by 20% by stripping dwarf debug symbols: from 44MiB to 34 on Macos
❯ du -h bin/installer
 44M	bin/installer
❯ git checkout -
Switched to branch 'raphael/strip_binary'
❯ invoke installer.build
❯ du -h bin/installer
 34M	bin/installer

/merge


Exposing new functions at the module level.

Exposing new functions at the module level.
Improving server_meets_version function to accept objects
Close #57

Codecov Report

Merging #58 (bf825aa) into main (6a677de) will decrease coverage by 1.28%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
- Coverage   96.87%   95.58%   -1.29%
==========================================
  Files           3        3
  Lines          64       68       +4
==========================================
+ Hits           62       65       +3
- Misses          2        3       +1

Impacted Files
Coverage Δ

src/ansys/tools/versioning/utils.py
98.18% <75.00%> (-1.82%)
:arrow_down:

src/ansys/tools/versioning/__init__.py
71.42% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Check in does not recognize replaced files

I have a build process that updates a database backup(.bak) that sits in my project. I was hoping to use the check-in task to check the file back into source control after an update but it seems that no changes get recognized.
It would be nice if there was a "force" option for replacing these kinds of files.

Have you tried using the tfvc add task for that?
I'd expect your .tfignore file is blocking the add action, it's probably best to add an exclusion for your database backup folder.
Just add a extra tf ignore file in that folder and add !*.bak

There was a bug introduced when using the latest agent version. I fixed that.


Motion Prediction Challenge Problem.

Hello, thank you for your contribution, I was going to participate in the motion prediction challenge, but when I was about to submit my results to the official website, I found that motion_submission.proto has disappeared, what format should I submit my results in now?

It looks like motion_submission.proto is still in the same place here: https://github.com/waymo-research/waymo-open-dataset/blob/master/src/waymo_open_dataset/protos/motion_submission.proto
The format should be the same.  Please let me know if you are still having trouble.


simpleListView

Description
Added Simple List View UI in UI designs folder
Fixes #6
https://user-images.githubusercontent.com/96647299/196957690-4be61358-0c09-4fcf-805e-1b426903cb3c.mp4

Congrats @Perumallpardhiv 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Add basic sensu_ctl resource with configure ability

Here's a start at a resource for handling sensuctl to satisfy #5 . Currently it can only install the cli and configure it to talk to a cluster.
Builds on changes already included in #7 so merge that first and I can rebase as needed.

looks pretty reasonable with a quick look through after the other PR merges we should rebase so I can more easily evaluate the changes in isolation and greater detail.

Now that #7 has merged please rebase

@majormoses rebased