Navigating "Back" into a page with lots of tiles is slow

Couldn't find the Desktop version of the ticket, so opening a new one.  It's been this way since 2020, so we can isolate this from the recent slowdown that we are seeing (although they all add up).
Issue
If you navigate back to a page with lots of claim tiles, it takes several seconds to load (proportional to number of tiles).
Reproduce:

Enter any category page
Scroll to 10+ or more pages
Click on a tile
Back -- the more tiles in the previous page, the more longer it takes.  Also more apparent in slower machines or mobile.

Causes

[ ] ClaimPreview and ClaimPreviewTile is just too complex with too many children.  Ligthouse complains about DOM size being too big.

Having many smaller components help in reusability, but most of them aren't being reused anyway.  One solution is to move the logic into util functions instead to lower the number of children for these 2 components.

[x] Each tile will look up 4 blocklists on every render

Alleviated through better memoization of the lookup + lighter URI parsing

[ ] Bad selectors

Even when these components aren't rendering, their select is calling a bunch of selectors that are still not memoized correctly. Also, each child of this component uses the same selectors, so the calculations are repeated many times due to the failed memo.

Explored solutions

Windowed scrolling (loading only a handful of tiles at a time)

Issues found at that time:

no robust 3rd party solution -- each have their quirks.  Might as well just roll our own.  Looked at react-virtualized,  react-window and a few smaller ones.
Our tiles have uneven height (e.g. different height for reposts).  This is a general crux for Windowed Scrolling.
Our homepage consists of different sections.  Hard to virtualize and maintain multiple sections in a window.

Alternative ideas:

Just show an auto-incrementing horizontal loading bar at the top when Back is clicked, and dismiss when page is rendered.

My previous attempts weren't successful ... the bar itself would not paint until the page is already loaded.


Fix Subscribe panic and add a test which would have caught it

Description
This PR creates a new test for the Subscribe endpoint as well as fixing a current bug which causes panics when that RPC is used.
Why is this needed
Fixes: #69
How Has This Been Tested?
~/Workspace/hegel % go test ./...
?   	github.com/tinkerbell/hegel/cmd/hegel	[no test files]
?   	github.com/tinkerbell/hegel/grpc/protos/hegel	[no test files]
ok  	github.com/tinkerbell/hegel/grpc-server	(cached)
?   	github.com/tinkerbell/hegel/hardware	[no test files]
?   	github.com/tinkerbell/hegel/hardware/mock	[no test files]
?   	github.com/tinkerbell/hegel/hegelc	[no test files]
ok  	github.com/tinkerbell/hegel/http-server	0.946s
?   	github.com/tinkerbell/hegel/metrics	[no test files]
?   	github.com/tinkerbell/hegel/xff	[no test files]
~/Workspace/hegel % git revert a1790b264f3e71ebf7070d27e41e2e8abfdfe49b
Auto-merging grpc-server/grpc_server.go
[nshalman/subscribe-fix-and-test 7fb47d7] Revert "subLock needs to be initialized"
 1 file changed, 2 deletions(-)
~/Workspace/hegel % go test ./...
?   	github.com/tinkerbell/hegel/cmd/hegel	[no test files]
?   	github.com/tinkerbell/hegel/grpc/protos/hegel	[no test files]
{"level":"info","ts":1641500023.904764,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
{"level":"info","ts":1641500023.905344,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
{"level":"info","ts":1641500023.9055989,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
{"level":"info","ts":1641500023.9056818,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
{"level":"info","ts":1641500023.9058208,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
{"level":"info","ts":1641500023.906524,"caller":"grpc-server/grpc_server.go:155","msg":"","service":"github.com/tinkerbell/hegel","pkg":"grpcserver","client":"<IP_ADDRESS>:80","op":"get"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x107525e]

<snip>

How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[x] added unit or e2e tests
[ ] provided instructions on how to upgrade

Thanks again to @mmlb for most of this test harness, and for the pointers for the further cleanup of the tests in https://github.com/tinkerbell/hegel/compare/669989512f74834d3a41cbcc271cf03cb152c630..f0ae94cd34199f0d1d1ce3c90e64dfb8ad9111a5

Thanks again to @mmlb for most of this test harness, and for the pointers for the further cleanup of the tests in 669989512f74834d3a41cbcc271cf03cb152c630..f0ae94cd34199f0d1d1ce3c90e64dfb8ad9111a5 (compare)

np. now that I look again the WaitGroup is probably unnecessary and I forgot to drop it

now that I look again the WaitGroup is probably unnecessary and I forgot to drop it

Good catch. I will clean that up.


1136 jsonapi factories

Context
Things to do before shipping this:

DRY doubles in the vacancy helper spec
Add request specs to replace the feature tests we removed

Changes proposed in this pull request
Guidance to review

Still left to do:

move spec that compares the generated jsonapi structure to the json structure currently in the test into a factory spec
share initialize_with with site_statuses, sites and other factories


fix: action description typo

Description
Typo fix
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for fixing this! But it looks like I can't merge unless all checks pass.

@alanzchen Can you please merge it?

Thanks for the correction 🙂


frontrun tx always reverts with ERC20: transfer amount exceeds balance

It seems that the contract always tries to send some amount of the non-weth token to the pair despite the contract having a balance of 0. What am I doing wrong?

Do you still have this issue? Can share more details?

Acc to this contract, the contract first takes the token, and then changes it to weth in frontrun, and in backrun it converts weth to token. So better way is to replace the token -> weth in frontSliceTxPayload and weth->token in backsliceTxPayload . Or you can do is to fund your sandwich contract with the token you want to swap with


use literal substitution instead of identifier

Related issue https://github.com/CartoDB/support/issues/2273
I made a quick test in one of the affected users database and the fix seems to work

Fine by me, but most likely the problem comes from double quoting, that is, changes in the parameter passed to the function (I can tell for sure this used to work ok under different conditions).

This is how it's being called from cartodb (which is the origin of the issue):
CDB_UserDataSize('#{self.database_schema}')

I did some manual tests and it seems to happen when the database_schema contains -. I'll try to add some tests to check that to the PR.


Move memo to RenderContext

This moves the memo function to RenderContext, where it will bind a Renderable to a single RenderContext. This ensures that it will only be rendered once and has symmetry with render.
This is a breaking change and bumps the version to 0.7.0.
(To resolve circular import issues, it also splits core.ts into node.ts and render.ts.)

Would you mind updating the rest of the docs to reflect this? For instance, https://docs.ai-jsx.com/guides/rules-of-jsx?_highlight=memo#memoization.


[BUG] Post View Modal Resize

Description
On resize (width), you cannot scroll on the post view modal and view the rest of the content.
Reproduction Steps
Minimize the width of the post-view modal page.

Resolved by #304


zk init error

zk init gives me error

thread 'main' panicked at 'Can't read .zbin bytecode at "/Users//Documents/Projects/zksync-era/etc/system-contracts/contracts/precompiles/artifacts/Keccak256.yul/Keccak256.yul.zbin": No such file or directory (os error 2)', core/lib/contracts/src/lib.rs:195:31

root cause in core/lib/types/src/system_contracts.rs
workaround https://github.com/bap2pecs/zksync-era/pull/1

this is actually due to the submodule not pointing to the latest one


Figure out how "video" type attachments are getting created - see Hylo Stewards projects stream

in filestack. maybe disabled now

solved for now it seems


Add Austin LeBel to Contributors list

Yay fun things and learning

Hi  @Slatefox, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Other sync options: Google Drive, Dropbox, Nextcloud (regular, non-WebDAV)?

Allowing for other sync options using OAuth2 to authenticate or with integrated account support on Android would be pretty nice.

Quick note: You can now specify a custom data directory under Android (https://github.com/redsolver/notable-mobile/commit/be5abfd5734592af13391fdce71cbc3564ce1b13), which allows to use basically any other external sync app.

Unfortunately this only works with apps like FolderSync, but not with apps like Google Drive (which does not use the physical filesystem).

I decided to drop support for syncing notes directly via the app in the new release, because it's very hard to implement it right and there are a lot better apps for it which primary feature is synchronisation. Maybe someday it will return, but for now I recommend using an external data directory and using a third-party sync app for Android like Syncthing or FolderSync for other cloud services.
Also, there are a lot of cloud services out there and I don't want to implement every single protocol or API they offer, because I think that's beyond the scope of this app when there are working alternatives.


Security Patch for nokogiri

NOTE Also, there is a concern with XML External Entity (XXE) Injection though there is no patch for it yet. https://app.snyk.io/vuln/SNYK-RUBY-NOKOGIRI-20299

It looks like the patch is updating your Gem files. It's putting the latest versions in which for nokogiri has a security patch.


Support reset positions

Fixed #13

Hi @qinmingyuan, thank you for getting this started for me. I've gone ahead and done a more comprehensive solution and encapsulated the logic in a new Healer class. It was also a good chance to tidy up the Advisory Lock code.
Let me know how it works for you :)


{{ .Release.* }} and {{ .Values.* }} not validated as correct when template is not in 'templates' directory

When using a template which is not directly under a directory named "templates" {{ .Release.* }} and {{ .Values.* }} are not validated as correct.

cc @andxu @testforstephen

It looks like the extension defines a 'helm-template' file type.  We can't distinguish this from the 'YAML' file type on file extension or first line alone, so we try to infer it from the templates file path.
As a workaround, could you try clicking on the file type 'YAML' on the status bar (towards the right hand end, next to the smiley face icon), and selecting 'helm-template' in the drop down?  Unfortunately this selection doesn't seem to persist, so it's not suitable as a long term fix...

A workaround that persists (but is a bit more effort):

Open your workspace settings (Ctrl+, or File > Preferences > Settings)
In the Workspace Settings tab, add the following entry:

    "files.associations": {
        "**/my-template1/*.yaml": "helm"
    }

Save the settings and re-open the template file.

Thanks @itowlson the workaround fixed my issues.


LOW: Make copy/paste work well

Great ideas from @gabi, going to work on defining a MVP once VIP scope is defined.

I'll dig into this next week, but jotting down ideas off the top of my head:

Formatting is broken when you copy/paste -- bold, italics, paragraph breaks, etc.
Ideal flow should be that you can copy/paste something from somewhere else into newdot, and maintain the formatting, and then copy/paste from newdot into somewhere else, and also maintain the formatting.

haven't gotten to this yet, i'm trying to #focus on #vip-split right now. let me know if this bumps up priority.

@arielgreen just putting this on your radar, though I'm not sure there is any immediate action to take.


mark-feed-read when filter is applied should only mark visible items read

Newsboat version (copy the output of newsboat -v or the first line of git show):
r2.21-362-g80f1
Steps to reproduce the issue:

Apply a filter by pressing F and type in title =~ "(string that's only in a subset of articles)"

Press A to mark all read.

Expected: only visible articles are read, similar to if one had used / (open-search) to do the filtering instead of a filter.
Actual: all articles in the feed are read.
My guess is this happens because / creates a temporary "feed" and marks it read, while filters work differently?  Anyway, seems like they should work the same, or perhaps a new mark-visible-read command could be added?

Reproduced on 8880ba431012964d62c8d798191995e53a58a99f, thanks for the report!

My guess is this happens because / creates a temporary "feed" and marks it read, while filters work differently?

Exactly. Filters are applied at "display" time, by filtering out the items that don't match: https://github.com/newsboat/newsboat/blob/8880ba431012964d62c8d798191995e53a58a99f/src/itemlistformaction.cpp#L916-L923

seems like they should work the same

Yes, I think the expected behaviour you describe is the correct one.


TE-3.6: ACK in the Presence of Other Routes

@azubaidhar to be assigned

Hi @azubaidhar can you let us know how the development is going?

Hi Darren,
Submitted code for TEC-3.6 merge blocked including CLA acceptance. Will work on fixing this,
https://github.com/openconfig/featureprofiles/pull/198
Thanks,
Abdul Zubaidhar .A
From: Darren Loher @.>
Date: Friday, 27 May 2022 at 11:43 PM
To: openconfig/featureprofiles @.>
Cc: Abdul Zubaidhar Abdulla @.>, Mention @.>
Subject: Re: [openconfig/featureprofiles] TE-3.6: ACK in the Presence of Other Routes (Issue #136)
[External Email. Be cautious of content]
Hi @azubaidharhttps://urldefense.com/v3/__https:/github.com/azubaidhar__;!!NEt6yMaO-gk!A2Fb4mgJ9evZ8Ww_pzG_NKqE6btl-STRDL8r9nBJLA4P_ghgLBDFgroo5cAziCYqkGnzQom16sidZOI867PGpojpzso$ can you let us know how the development is going?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/openconfig/featureprofiles/issues/136*issuecomment-1139908641__;Iw!!NEt6yMaO-gk!A2Fb4mgJ9evZ8Ww_pzG_NKqE6btl-STRDL8r9nBJLA4P_ghgLBDFgroo5cAziCYqkGnzQom16sidZOI867PG6Gl8BMc$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AYQGC76N4IGSBQGTN7LX64LVMEGDLANCNFSM5TEMIY2A__;!!NEt6yMaO-gk!A2Fb4mgJ9evZ8Ww_pzG_NKqE6btl-STRDL8r9nBJLA4P_ghgLBDFgroo5cAziCYqkGnzQom16sidZOI867PGHechtN8$.


Change Sickle main entry point to ts.SourceFile

ts.Program (the previous parameter) is a fully compiled program of
potentially multiple files, while ts.SourceFile is a single parsed file.
It appears from how we're using sickle that we want the latter, not the
former.
(It may be the case that we need a fully compiled program to get all the
references right, but for now this appears to work.)

If you add closes #13 to the commit message, github will autoclose that issue.


NonRoot: move session-mode files to /home/qemu

What this PR does / why we need it:
Before this, the bazel rules chowned /run to qemu:qemu, as a side-effect of chowning /run/var/lib/swtpm-localca.
That makes everything work nicely but it is less than ideal!
Chowning /run back to root and moving XDG_* to /home/qemu seems saner.
The alternative solution would have been to pre-create and chown more /run subdirectories,
but that won't work since swtpm_setup creates files at the root of XDG_RUNTIME_DIR (or another XDG_).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

The qemu user no longer owns /run

/cc @xpivarc

/retest

We could in the future want to run the launcher under random users. Why can't we keep the /var/run (Maybe use an Emptydir)?

We could in the future want to run the launcher under random users. Why can't we keep the /var/run (Maybe use an Emptydir)?

The directory doesn't have to be /home/qemu, it could be anything, like /nonroot or /var/run/nonroot, but we can't use just /var/run since we would have to allow anyone to write to it.
@xpivarc any specific location preference?

Switched to a cleaner approach there: https://github.com/kubevirt/kubevirt/pull/7713
Opened a separate PR to keep this intact in case there's any issue with the new approach.
Closing, at least for now.


add Dutch translation

Dutch translation

@Leecason Translation doesnt seem to have any mistakes. Could you please merge this?

@Leecason This is a translation created by and for the Dutch. Merging is much appreciated!

:tada: This PR is included in version 1.27.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Moving CloudStack to use v2 controller

Issue #, if available:

https://github.com/aws/eks-anywhere/issues/2929
https://github.com/aws/eks-anywhere/issues/2260

Description of changes:
In order to address the issue, it seemed like migrating the Cloudstack provider off the legacy controller was the best way to enable the proper creation of the ClusterSpec. I have done so, based off the VSphere provider's example and would like some early feedback on my approach, and to make sure I haven't missed anything obvious.
Testing (if applicable):
TBD
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Reopen if needed. Looks pretty dated and irrelevant at this point.


google-cloud-cpp: simplify excluded test list

Description of changes
The upstream project labels any test that requires contacting
Google Cloud Platform as an integration-test. It is easier to
skip the tests by label than explicitly listing each test.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

@dbolduc FYI

Just floating this idea, any chance this PR can include updating the SDK as well? Looking around here it seems that using the 'update.sh' file will help in updating this PR for updating the package. Package is 452.0.1 and current version is 466.0.0. Not sure of a way to update locally w/o using the official gcloud cli tool.

Thanks for the quick reviews and getting this merged.  I hope it will make it easier to upgrade this package from time to time.


Simplify travis

ARGH: push build failed. Will try rerunning... Perhaps an upgrade in some underlying numeric library?
diff -w -r -x .DS_Store fake-files/output/linnarsson/linnarsson.cells.json fake-files/output-expecte
141855c141855
<     6.33
---
>     6.32
194050c194050
<     6.33
---
>     6.32


Warnings on Arduino IDE

I am getting many warnings on arduino IDE.
warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
The small program below shows where these come from.
You can find one for instance on line 104 of the ArduinoSpotify.h file.
ArduinoSpotify(Client &client, char *clientId, char *clientSecret, char *refreshToken = "");
char *refreshToken = "" this part gives the warning as illustrated below
You can remove the warning by adding (char *) as shown below but not sure program then still works as intended
char refreshToken1 [] = "";            //Is Ok
char *refreshToken2 = (char *)"";      //Is OK
char *refreshToken3 = "";              // gives above warning
void setup() {
}
void loop() {
}

Updated, I no longer have any compiler warnings.

Thank you very much for fixing that.
I still get one warning.
getRefreshToken.ino: In function 'void handleCallback()':
getRefreshToken:118: error: invalid conversion from 'const char*' to 'char*' [-fpermissive]
refreshToken = spotify.requestAccessTokens((char*)code.c_str(), callbackURI);
                                             ^

Ok thanks I'll fix that when I'm working on it again. For now I think you
could just remove the cast to (char *) before code.c_str
On Fri 31 Jul 2020, 07:35 krulkip<EMAIL_ADDRESS>wrote:

Thank you very much for fixing that.
I still get one warning.
getRefreshToken.ino: In function 'void handleCallback()':
getRefreshToken:118: error: invalid conversion from 'const char*' to
'char*' [-fpermissive]
refreshToken = spotify.requestAccessTokens((char*)code.c_str(),
callbackURI);
                                         ^

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/witnessmenow/arduino-spotify-api/issues/7#issuecomment-666956034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL5PQVGEAY4J4ULPXXVUZLR6JQ27ANCNFSM4PM6YVZA
.

I forked your library and made the changes to fix this issue. Not tested it yet but it assembles without errors.

All working OK now. Tested both getrefreshtoken and getcurrentlyplaying.
Thank you so much. Super cool.


Allow specification of additional JAVA_ARGS

I just upgraded my jenkins module (from 1.4.0), and in upgrading things, ran into the fact that the Jenkins module now manages the INI settings in /etc/default/jenkins (in Debian). I had been setting a few options of my own with inifile, which Jenkins' management overwrote.
In the end I decided to solve it by implementing an option to specify additional JAVA_ARGS to the module. In doing so, I moved a little bit more of the logic into config.pp, in order to allow adding custom JAVA_ARGS.
I wasn't able to get a test environment up, so this PR is partially to get acceptance tests run as well.

Hmm, looks like some relevant tests did indeed fail - I'll take a look at those this week, and maybe take another run at getting my own test environment up and running.

I like this feature, and want to move away from the problems with config_hash/jenkins::sysconfig, but it is going to be tricky to get the implementation right.

Thanks for the feedback. As mentioned, this was my problemsolving for my own needs, and PR'd it to see if it was useful enough to round out with tests and closer attention. I'll address your comments and work on tests, thanks!
And yeah, any more substantial changes are going to be pretty tricky, so I think I can shape this up to be a reasonable solution within the existing setup.

Hi. Thanks for raising this PR, but I'm going to close it due to inactivity. Please reopen it if you're still interested in getting this merged.


[Enum Request] Table 99000770 "Manufacturing Comment Line" - "Table Name"

Hello,
Could you please change the type of this field to a extensible Enum in "Manufacturing Comment Line" table?
field(1; "Table Name"; Option)
{
   Caption = 'Table Name';
   OptionCaption = 'Work Center,Machine Center,Routing Header,Production BOM Header';
   OptionMembers = "Work Center","Machine Center","Routing Header","Production BOM Header";
}

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46015.

Hello @JesperSchulz ,
We didn't found yet in any versions of BC.
Could You tell when will arrive?
Thx for in advance.
BR,
Laszlo


Avoid sending async updates on config update

In https://github.com/atom/atom/commit/7a5d727e224a7a5fa9c45a1979bb1758c12d8b20 the 'set-user-settings' callback was changed so that it no longer returned the promise created by ConfigFile.update(). This meant that the logic in ApplicateDelegate.onDidChangeUserSetting() which uses .pendingSettingUpdateCount to avoid triggering in response to calls to
ApplicationDelegate.setUserSettings was no longer effective.
I noticed this when updating settings via the setting view. If you type at just the right (wrong?) cadence, you'll notice that your input can get updated with stale values.
Something like this:
You type            "a"      "b"            "c"
config.set          "a"      "ab"           "ac"
config.observe                        "a"         "ab"    "ac"
Input value         "a"      "ab"     "a"   "ac"  "ab"    "ac"

It's possible that this is the same as https://github.com/atom/settings-view/issues/1062
After this change typing in a settings input seems to behave as expected.

Thanks for the fix, @captbaritone!


[Feature] Gitlab integration

It would be awesome a Gitlab integration.

Hi @DanielRamosAcosta! This tool should work with any Git repository.
Personally, I don't work with Gitlab. Are you referring to a specific feature, such as GitHub Releases, to work in a similar fashion with Gitlab?

Yes, I was thinking about the Releases and assets upload.

Feel free to open a PR and explore this idea further. I'm interested as well.

I'll look into it, thanks!


Implement critical system log capture before and after upgrades

Is your feature request related to a problem? Please describe.
When upgrading PAN-OS on firewalls using the pan-os-upgrade utility, it is crucial to capture and analyze critical system logs before and after the upgrade process. These logs can provide valuable insights into the health and stability of the firewall, as well as help identify any potential issues or anomalies that may occur during or after the upgrade. Currently, the utility does not have a built-in mechanism to capture and store critical system logs, which may make it difficult to troubleshoot or investigate upgrade-related problems.
Describe the solution you'd like
Enhance the pan-os-upgrade utility to capture critical system logs on the firewalls before and after the upgrade process. The utility should:

Before initiating the upgrade, identify the critical system logs that need to be captured based on predefined criteria or user-specified configuration.
Execute the appropriate CLI commands (e.g., show log system) or API calls to retrieve the specified system logs from the firewall.
Store the captured logs in a structured format (e.g., JSON or XML) along with metadata such as the timestamp, device information, and log type.
Proceed with the normal upgrade process.
After the upgrade is completed and the firewall is back online, re-capture the same set of critical system logs from the upgraded firewall.
Store the post-upgrade logs in a similar structured format as the pre-upgrade logs.
Perform a comparison between the pre-upgrade and post-upgrade logs to identify any significant changes, error messages, or anomalies.
Generate a report or display the comparison results to the user, highlighting any potential issues or areas that require further investigation.
Provide an option to export or archive the captured logs for future reference or deeper analysis.

Describe alternatives you've considered
An alternative approach could be to rely on external log management solutions or SIEMs to capture and analyze the system logs. However, this would require additional integrations and may not provide a seamless experience within the pan-os-upgrade utility itself. Moreover, capturing logs directly through the utility ensures that the relevant logs are available even if external logging systems are not accessible or properly configured.
Additional context
Here are a few additional points to consider:

Allow users to customize the list of critical system logs to capture based on their specific requirements or organizational policies.
Handle scenarios where the log capture commands may fail or return unexpected output, and provide appropriate error handling and logging.
Implement log rotation or purging mechanisms to prevent excessive storage consumption, especially for large-scale deployments with multiple firewalls.
Provide guidelines and best practices on interpreting the log comparison results and identifying potential issues.
Consider integrating with external log analysis tools or machine learning algorithms to automatically detect anomalies or patterns in the captured logs.
Update the project's documentation to include information about this new feature, explaining how it helps monitor and troubleshoot the upgrade process through system log analysis.

By implementing this feature, the pan-os-upgrade utility will provide a comprehensive approach to capturing and analyzing critical system logs before and after the upgrade process. This will enable users to proactively identify and address any potential issues, ensure the stability and reliability of the upgraded firewalls, and facilitate effective troubleshooting and root cause analysis.

will revisit when time permits, closing for now


[BUG] Version Tree link is broken

6d939696cdcf998f3d02b4d3f522a176720394b4 changed release in the client options to prefer travisBuildNumber over gitReleaseName, and release is used in the client side code to construct a link to github.

Whoops, good spot.


Cannot load PlugIn DVTKitDFRSupport in Xcode >= 8.1 on macOS Sierra

Sierra 10.12.2 Beta (16C48b)
Xcode 8.1
Xcode 8.2 beta 2

Reproduce
I tried running build.sh framework test, but gave up after an hour of execution time.  I noticed some failures that appeared to be unrelated to this issue.
I updated the build.sh to only run the FBDeviceControl tests.
  114 function all_frameworks_test() {
  115 #  core_framework_test
  116 #  xctest_framework_test
  117 #  simulator_framework_test
  118   device_framework_test
  119 }
  120

$ ./build.sh framework test
Test Case '-[FBDeviceControlLinkerTests testLinksPrivateFrameworks]' started.
/Users/moody/git/calabash/FBSimulatorControl/FBDeviceControlTests/Integration/FBDeviceControlLinkerTests.m:35: error: -[FBDeviceControlLinkerTests testLinksPrivateFrameworks] : failed: caught "NSInternalInconsistencyException
", "Error getting value for key 'initializationClass' of extension 'Xcode.DVTKitDFRSupport.Initializer' in plug-in 'com.apple.dt.IDE.DVTKitDFRSupport'"

Expected
The tests to pass.
Notes
Not reproducible on El Cap or Xcode 8.0 - the DVTKitDFRSupport plug-in does not exist in the Contents/PlugIns directory.
Log
2016-11-18 11:13:43.309 iOSDeviceManager[23441:895900] [MT] DVTPlugInLoading: Failed to load code for plug-in com.apple.dt.IDE.DVTKitDFRSupport (/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin), error = Error
 Domain=NSCocoaErrorDomain Code=3587 "dlopen_preflight(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport): Library not loaded: @rpath/DFRSupportKit.framework/Versions/A/DFRSuppor
tKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle is damaged or missing necessary resources., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=/Xcode/8.1/Xcode.app/Contents/PlugIns
/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport, NSDebugDescription=dlopen_preflight(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport): Library not loaded: @rpath/DF
RSupportKit.framework/Versions/A/DFRSupportKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found, NSBundlePath=/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin, NSLocalizedDescription=The bundle “DVTKitDFRSupport” couldn’t be loaded because it is damaged or missing necessary reso
urces.}, dyldError = dlopen(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport, 0): Library not loaded: @rpath/DFRSupportKit.framework/Versions/A/DFRSupportKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found
2016-11-18 11:13:43.310 iOSDeviceManager[23441:895900] [MT] DVTPlugInExtensionFaulting: Failed to fire fault for extension Xcode.DVTKitDFRSupport.Initializer: Error Domain=DVTPlugInErrorDomain Code=2 "Loading a plug-in failed
." UserInfo={DVTPlugInIdentifierErrorKey=com.apple.dt.IDE.DVTKitDFRSupport, DVTPlugInExecutablePathErrorKey=/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport, NSLocalizedRecovery
Suggestion=The plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled., DVTPlugInDYLDErrorMessageErrorKey=dlopen(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/C
ontents/MacOS/DVTKitDFRSupport, 0): Library not loaded: @rpath/DFRSupportKit.framework/Versions/A/DFRSupportKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found, NSLocalizedDescription=Loading a plug-in failed., NSFilePath=/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin, NSLocalizedFailureReason=The plug-in “com.apple.dt.IDE.DVTKitDFRSupport
” at path “/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin” could not be loaded.  The plug-in or one of its prerequisite plug-ins may be missing or damaged., NSUnderlyingError=0x7f841b5f4540 {Error Domain=NSC
ocoaErrorDomain Code=3587 "dlopen_preflight(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport): Library not loaded: @rpath/DFRSupportKit.framework/Versions/A/DFRSupportKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found" UserInfo={NSLocalizedFailureReason=The bundle is damaged or missing necessary resources., NSLocalizedRecoverySuggestion=Try reinstalling the bundle., NSFilePath=/Xcode/8.1/Xcode.app/Contents/PlugIns
/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport, NSDebugDescription=dlopen_preflight(/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport): Library not loaded: @rpath/DF
RSupportKit.framework/Versions/A/DFRSupportKit
  Referenced from: /Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin/Contents/MacOS/DVTKitDFRSupport
  Reason: image not found, NSBundlePath=/Xcode/8.1/Xcode.app/Contents/PlugIns/DVTKitDFRSupport.ideplugin, NSLocalizedDescription=The bundle “DVTKitDFRSupport” couldn’t be loaded because it is damaged or missing necessary reso
urces.}}}
2016-11-18 11:13:43.319 iOSDeviceManager[23441:895900] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error getting value for key 'initializationClass' of extension 'Xcode.DVTKitDFR
Support.Initializer' in plug-in 'com.apple.dt.IDE.DVTKitDFRSupport''
*** First throw call stack:
(
        0   CoreFoundation                      0x00007fffca8f3e7b __exceptionPreprocess + 171
        1   libobjc.A.dylib                     0x00007fffdf4d7cad objc_exception_throw + 48
        2   DVTFoundation                       0x0000000111b45590 -[DVTExtension valueForKey:error:] + 0
        3   IDEFoundation                       0x00000001131b938d _IDEInitializeOnePlugInAndPrerequisites + 1138
        4   IDEFoundation                       0x00000001131b7c59 _IDEInitializePlugIns + 1481
        5   IDEFoundation                       0x00000001131b701f IDEInitialize + 8173
        6   IDEFoundation                       0x00000001131b87d0 +[IDEFoundationTestInitializer initializeTestabilityWithUI:error:] + 57
        7   FBDeviceControl                     0x000000010edee12c +[FBDeviceControlFrameworkLoader initializePrincipalClasses:error:] + 62
        8   FBDeviceControl                     0x000000010ededd47 +[FBDeviceControlFrameworkLoader loadXcodeFrameworks:error:] + 524
        9   FBDeviceControl                     0x000000010ededaad __59+[FBDeviceControlFrameworkLoader initializeXCodeFrameworks]_block_invoke + 82
        10  FBDeviceControl                     0x000000010ede8786 +[CalabashUtils doOnMain:] + 132
        11  FBDeviceControl                     0x000000010ededa55 +[FBDeviceControlFrameworkLoader initializeXCodeFrameworks] + 86
        12  FBDeviceControl                     0x000000010ede78c5 __33-[FBDeviceSet primeDeviceManager]_block_invoke_2 + 62
        13  libdispatch.dylib                   0x00007fffdfd850b8 _dispatch_client_callout + 8
        14  libdispatch.dylib                   0x00007fffdfd85075 dispatch_once_f + 38
        15  FBDeviceControl                     0x000000010ede7881 __33-[FBDeviceSet primeDeviceManager]_block_invoke + 110
        16  FBDeviceControl                     0x000000010ede8786 +[CalabashUtils doOnMain:] + 132
        17  FBDeviceControl                     0x000000010ede7802 -[FBDeviceSet primeDeviceManager] + 93
        18  FBDeviceControl                     0x000000010ede822f -[FBDeviceSet dvtDeviceWithUDID:] + 56
        19  FBDeviceControl                     0x000000010ede9049 -[FBDevice dvtDevice] + 104
        20  FBDeviceControl                     0x000000010edeb546 __63-[FBiOSDeviceOperator waitForDeviceToBecomeAvailableWithError:]_block_invoke + 56
        21  FBControlCore                       0x000000010ed3b22d -[FBRunLoopSpinner spinUntilTrue:error:] + 144
        22  FBDeviceControl                     0x000000010edeaf55 -[FBiOSDeviceOperator waitForDeviceToBecomeAvailableWithError:] + 248
        23  iOSDeviceManager                    0x000000010ec8f6cb +[PhysicalDevice deviceForID:codesigner:] + 264
        24  iOSDeviceManager                    0x000000010ec8ff2d +[PhysicalDevice appIsInstalled:deviceID:] + 70
        25  iOSDeviceManager                    0x000000010eca6ba9 +[Device appIsInstalled:deviceID:] + 110
        26  iOSDeviceManager                    0x000000010ec89a38 +[IsInstalledCommand execute:] + 144
        27  iOSDeviceManager                    0x000000010ecaae43 +[CLI process:] + 1142
        28  iOSDeviceManager                    0x000000010ec7f015 main + 121
        29  libdyld.dylib                       0x00007fffdfdbb255 start + 1
        30  ???                                 0x0000000000000006 0x0 + 6
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6

Workaround
If I add:
# FBWeakFramework+ApplePrivateFrameworks
+ (nonnull instancetype)DFRSupportKit
{
  return [FBWeakFramework<EMAIL_ADDRESS>}

+ (nonnull instancetype)DVTKit
{
  return [FBWeakFramework<EMAIL_ADDRESS>}

My test passes.
It seems like there needs to be a runtime check against macOS version and Xcode version.
Notes
I am seeing these messages in the console:
2016-11-18 12:22:36.803697 xctest[31857:947377] Pruning certificate chain to<PHONE_NUMBER>3709551615
2016-11-18 12:22:36.803783 xctest[31857:947377] Trying to add a bogus certificate
2016-11-18 12:22:36.803817 xctest[31857:947377] An error occured while inserting an untrusted certificate into the chain
2016-11-18 12:22:36.909307 xctest[31857:947377] Pruning certificate chain to<PHONE_NUMBER>3709551615
2016-11-18 12:22:36.909343 xctest[31857:947377] Trying to add a bogus certificate
2016-11-18 12:22:36.909356 xctest[31857:947377] An error occured while inserting an untrusted certificate into the chain

I'd need to check this out for the FBDeviceControl Frameworks, but yes it is more invasive in the sense that it loads Frameworks that are more core to the Xcode IDE. If there are some changes to the way that dyld works in Sierra, then we might have to change the Frameworks that are loaded and when on a newer version of Xcode 8.
In addition to the definition of those new Frameworks, did you add them to the list of Frameworks to be loaded?

Hey.  I found a way to reproduce and am working on a PR.

Awesome thanks @jmoody, if you could provide details on the differences between the macOS versions and Xcodes that would be awesome for future reference.

Updated with steps to reproduce.
@lawrencelomax Have you seen these certificate log messages before?

Yep I've seen the messages before, but I haven't dug into them yet.

Any thoughts about how to branch on the availability of the /Frameworks/DFRSupportKit.framework?
This framework exist only on macOS Sierra in Xcode >= 8.1.
Is there an existing strategy for runtime branching on macOS and Xcode version?
Maybe a simple fileExistsAtPath: check when creating the list of FBWeakFramework instances?

Branching on the macOS version at runtime is simple.
NSProcessInfo#isOperatingSystemAtLeastVersion:
I only know how to check the Xcode version at runtime by shelling out (with NSTask). :/

Xcode version can be found using FBControlCoreGlobalConfiguration.xcodeVersionNumber

Fixed.


Casting does not stop when deselecting Chromecast device

I am running in Windows 10, and am able to cast to one or more devices, as intended. But when I deselect a device in the tray menu, the sound stops for a few seconds and then starts up again, even though the device is shown as deselected in the tray menu. While this is happening, the Chromecast app on my phone confirms that the device stops casting briefly and then starts casting again.
This consistently happens. Anyone else having this problem?
Thanks,
Dennis

Same. Have spent way too much time & effort trying to get this app working reliably. I've now given up, there are just too many issues. Such a shame, I even bought a stack of chromecasts to get whole-house audio, it worked brilliantly when I first installed it.

Yes, I am having the same problem with Windows 10. Uncheck the device in the menu, the audio disconnects... wait for a few seconds, it re-connects again. I would be really interested to know if this gets fixed. Many thanks Acidhax.

Still an issue with latest release, I'm looking into it.


[TEST] Update action.yml

Describe your changes

This pull request does...

It solves...

It was tested with...

Fixes...

Checklist

[ ] I have performed a self-review of my code
[ ] The code has been tested locally and works as expected.
[ ] Changes have been documented (if applicable).

Hello World!

Hello World! markdown

Hello World \n\n
:sparckles: test\n\n
*123*

:bulb:
Detected 0 conflicts among them

:mag_right:
Spotted 0 similar hunk(s)

(More Info)
check_conflicts.sh DETAILS (TODO)
check_hunks.sh DETAILS (TODO)

:open_file_folder:
Found 2 contributors working on the same files

:bulb:
Detected 0 conflicts among them

:mag_right:
Spotted 0 similar hunk(s)

More Info
check_pulls.sh DETAILS (TODO)
check_conflicts.sh DETAILS (TODO)
check_hunks.sh DETAILS (TODO)

Checks
PR Tracker Status

:white_check_mark:
0 contributor(s) found working on the same file(s)

:white_check_mark:
0 conflict(s) detected among them

:white_check_mark:
0 similar hunk(s) spotted

Details

Note Last update at Thu, 04 May 2023 23:32:25 GMTLearn more about PR Tracker ↗

Checks
PR Tracker Status

:ballot_box_with_check:
2 contributor(s) found working on the same file(s)

:white_check_mark:
0 conflict(s) detected among them

:white_check_mark:
0 similar hunk(s) spotted

Details
Check Pulls
:ballot_box_with_check: Found other Pull Request(s) with the same file(s) being modified (TODO)

Note Last update at Thu, 04 May 2023 23:54:54 GMTLearn more about PR Tracker ↗


Add reference to groovy-extra-list-behaviour

Add reference to groovy-extra-list-behaviour

Merged. Thanks for PR


Add Linux kernel v6.10 operations

Sending of buffer (from ReadBufPool):
IORING_RECVSEND_BUNDLE in IORING_OP_SEND/IORING_OP_RECV:
https://github.com/torvalds/linux/commit/a05d1f625c7aa681d8816bc0f10089289ad07aad
https://github.com/torvalds/linux/commit/2f9c9515bdfde9e4df1f35782284074d3625ff8a
Inject error results to test error handling:
IORING_NOP_INJECT_RESULT:
https://github.com/torvalds/linux/commit/deb1e496a83557896fe0cca0b8af01c2a97c0dc6
IORING_CQE_F_SOCK_NONEMPTY for accept:
https://github.com/torvalds/linux/commit/ac287da2e0ea5be2523222981efec86f0ca977cd
IORING_ACCEPT_POLL_FIRST for accept:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d3da8e98592693811c14c31f05380f378411fea1
IORING_RECVSEND_BUNDLE with IORING_OP_RECV:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f9c9515bdfde9e4df1f35782284074d3625ff8a
IORING_RECVSEND_BUNDLE with IORING_OP_SEND:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a05d1f625c7aa681d8816bc0f10089289ad07aad
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac5f71a3d9d7eb540f6bf7e794eb4a3e4c3f11dd

v6.10 has now been released, so work can start on this.


Disable purchase requests for galleries with pre-qualification enabled

Example: https://www.artsy.net/artwork/damien-hirst-norleucine-2

this was fixed by https://github.com/artsy/metaphysics/pull/501, maybe it wasn't deployed yet at the time.


Tag stable version

Currently there is no stable version released even though the library feels stable.

I've noticed a problematic behaviour with a recursive, heavily nested schema I've been testing. I'd like to fix that before creating a tag. It should be done soon.

Do you think you could you send me the problematic schema?

I solved the problem with #14. The only thing that prevented me to create a tag is the remaining issues #6 and #11. I think I will give it a shot this weekend (I've been pretty busy these times).


Remove unused GitHub integration

These aren't used by any Agent, as far as I know.

There are also some leftovers in application.scss and application_helper.rb, but it probably does not hurt to keep them, :+1: either way.

I figured those would be useful if we do add it.


chore: bump ESLint dependencies

Mainly, bump ESLint to v7, which figures out extensions from overrides, so we no longer need to pass --ext. I disabled some errors while updating other ESLint dependencies.

ESLint v7 lints the configuration file now as well, that's why there are so many changes there.


Possible to get proper colors in compiler errors?

When using elm make on it's own, you get color highlighting which really helps you spot the differences in big type signatures. But with Webpack it's all white. I tried setting stats: {colors: true} in the Webpack dev server config, but all that did was change the errors to all red.

I did some investigation and it seems like it's node-elm-compiler that would have to change for this to work.
The problem is that when it runs the compiler with stdio : "pipe" then the colors are lost.
I actually got color output working by hacking node-elm-compiler so that if there's an error, then it reruns the compiler with  stdio : "inherit" :smile:

Seems to be a problem with node-elm-compiler https://github.com/rtfeldman/node-elm-compiler/issues/91.


v1.69 ui bg The editing area appears abruptly blank

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

VS Code Version:
OS Version:

Steps to Reproduce:

/duplicate https://github.com/microsoft/vscode/issues/152816

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


new feed debugging

I've successfully followed a few Chicago centric feeds, but appears none of them have populated stories onto activity pub.
The feeds are
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I've spot checked the blockclubchicago .RSS link, and it does seem like they're actually updating it.
Are there a list of steps I should take to debug these feeds -> activity pub posts?

i think i may be seeing this same problem. even with feeds that look to have been around for a while (like xkcd from the example). it seems like the account and profile is there, but zero posts.
this is what i see when i follow the xkcd one. note, however, it says "cancel follow". it appears that the follow is awaiting approval from the xkcd account.


Warn on unsaved changes does not always work

I was trying to debug why the feature to warn the user on unsaved changes:
https://github.com/ambuda-org/ambuda/blob/8abad24a803699c28c1d9c4a0d5f8c5187961e11/ambuda/static/js/proofer.js#L74-L81
does not work properly with my pending changes in #132 but found that it's not quite working consistently on current prod either.
To reproduce,

go to a proofing page e.g. https://ambuda.org/proofing/mdhuraavijym/120/
type some spaces in the textarea
reload page

It warns you sometimes, but not always.
I tried looking at this and this but nothing is clear to me yet.

I can reproduce the error. I'll prepare a fix.

For me, the following triggers:

type some text
click outside the textarea
refresh

And the following doesn't:

type some text
refresh without clicking outside of the text area.


lets have a mvn fabric8:import goal to make it easy to import projects into fabric8

which then creates the BuildConfig from the git repository of the local project. If there is no git repository then also create a new gogs repository and push the code there.
This goal should also prompt the user for user/password for https based git protocols; or SSH keypairs for git/ssh protocol so that we can pre-populate the secrets easily for reuse by the console

Is this specific to the fabric8 CD setup or could this be also used when f-m-p is used outside the context of fabric8 ?

it should work with vanilla openshift too really; one day when we've got ThirdPartyResources for kubernetes; it can support there too really

I mean because of

If there is no git repository then also create a new gogs repository and push the code there.

I thought Gogs is specific to our setup.

ah yeah. Over time I'd like to support other git providers really; but right now gogs is all we have

I mean, even if we support other Git providers, we assume that a Git service is running in Kubernetes / OpenShift with the proper secrets setups, which by default is probably not the case.

yeah - if there's no git service in the current namespace we should fail nicely with a tip on how the user can fix it

@rhuss BTW added a nicer warning if there's no gogs running:
[WARNING] F8> No running endpoints for service gogs in namespace. Please run the `gogs` or the `cd-pipeline` application in the fabric8 console!

@jstrachan so this goal really makes only sense when used together with CD ? (that was my initial question ;-) For any other user who (for what reason ever ;-) doesn't want to run the fabric8 infra, the goal is of no use ?
If so, we should document this and maybe call the goal 'cd-import' ?

its of use to anyone using OpenShift or fabric8 on kubernetes. Not sure CD is the right name; they are called Jobs in Jenkins and BuildConfigs in OpenShift - we tend to call them apps in fabric8, iPaaS and MBaaS ;)

a build may not have any CD; may not have any CI - could just be a build - so not totally sure of a better prefix really ;)

another word than import could be share - as the idea is to share the code/build with folks on the cluster?


Update homepage table instructions

Hi.
The table creation scripts on the doc specify the use of BLOB for snapshots and journal.
Mysql's default max size for BLOB is 65k. Mysql default is also to not enable strict mode. This mean that writing more than that as a blob truncates it "silently" (an alert should be raised, but nothing was in my logs, could be my configuration, unsure), failing on recovery.
Maybe add a caveat about using MEDIUMBLOB (50Mb max) upon planning to store a lot in a snapshot.

@Akrome Modified BLOB into LONGBLOB.
https://github.com/okumin/akka-persistence-sql-async/commit/1e72fb96d408838d71e8e38a14a855de19a13432
Thanks for your pointing.


Use resolved parent for resolving children in normalizer

A potential solution to #379 by not allowing an evicted version to have effect on selecting a version of its children.

If we think this is a good addition, I'm willing to add some unit tests!

Update: we consider to change to maven_install from rules_jvm_external for multiple reasons later. I'd need to put this work on hold until we figure that out, as my resources are currently very limited towards this project. Still the patch should work and give the same resolution as using maven_install with pinned version conflict resolution, so whoever needs it could use this version. If I can get more resources to it, I'll return to it, but I cannot guarantee that unfortunately at this time.

Thanks for the update.
BTW: maven_install seems like a good choice. I think the main benefit of Bazel-deps is that it has better scala support. For scala you don't want to run ijar in libraries that have macros or they will fail.
If you don't use scala or leverage any of the customization that Bazel-deps offers I think maven_install could be a fine choice.

As far as I know maven_install doesn't use ijar anymore but their own simplified import rule, exactly because Scala macros and some issues with Kotlin as well. But yeah, it'd be great to make maven_install use scala_import and version the artifacts automatically, but based on the conversations I've seen I don't see much willingness to go to that direction.

Update: for now we went with maven_install, which means that I won't be able to do any more progress on this PR in the foreseeable future. (We missed some of the Scala specifics that bazel-deps has but managed to work around those for ourselves for now.)


ENH: stats.describe: add axis tuple and masked array support, keepdims; fix nan_policy and edge cases

Reference issue
Toward gh-14651
What does this implement/fix?
Adds axis tuple support, masked array support, and keepdims parameter to describe. Fixes nan_policy implementation and edge cases.
Additional information
Need to add tests.
describe is unusual in that

the shape of the first element of the result, nobs, depends on the presence of NaNs to be omitted. nobs is a scalar if there are no NaNs omitted and an array if NaNs have been omitted. Apparently, there are no tests that complain if this behavior is not maintained.
It raises an error when the input is of zero size. This is not uncommon but causes some complications with nobs. It would be better if it were to just return nobs=0 and NaN for all the rest.
The second output, minmax, is a tuple containing two arrays, the minimum element and the maximum element. Ideally, these would just be two separate attributes of the result object. This is not too hard to handle.

Marking this as draft so we can decide whether we want to go through with this.

Because of the issues above, it would be better to come back to this later. Let's get through all the easy stuff, first.


Oil Pouring Engineers Assignment Bug

The AI does not properly man their no1 rallying point for oil engineers.
This is caused by the fact, that this specific engineer is the one who distributes the oil to the other engineers meaning he is stuck with the oil smelter.
To fix this bug we need to a) increase the number of engineers assigned to the oil smelter by 1 (from n to n+1) and b) reassign the engineers so that the first engineer has no assignment to a specific AIV oil spot or that he might be assigned to spot no0 if that doesn't cause other bugs while the next one is assigned to no1; no2 and so on.
The mechanic with a no0 spot might cause bugs and crashes in unlocked maps where it is possible to have the AI send an oil engineer to spot no1 correctly by simply selecting the engineer who is distributing the oil.

When working on a fix you might want to think about the following:
If the AI recruits and assigns several engineers simultaneously it is possible that a different engineer than the no1 arrives first at the oil smelter and therefore being stuck there. That means that even if there is a no0 engineer it would still be possible that another engineer gets stuck at the oil smelter while there is going to be a 10th oil engineer who doesn't know what to do with himself.


servicemanager is not available

When doing the initial install of pGina 3.0, I get the following error:
the servicemanager is not available.
This does not seem to affect the overall install and usability of the program, but it is an issue, none-the-less.

Thanks! This is fixed in a newer build of the code, not yet released though as its awaiting another fix or two.  Next beta build will have it.  As you indicate, it does not affect overall installation, so shouldn't prevent testing.


Update project to AndroidX

Is it possible to update the Android project to use the AndroidX libraries instead of the old support libraries like described here https://flutter.dev/docs/development/packages-and-plugins/androidx-compatibility#how-to-migrate-a-flutter-app-to-androidx ?
This would enable projects which are dependent on this one to migrate to AndroidX too (like ours :blush: )

@fezu54 I've just updated the package to AndroidX and made a pull request, give it a test and make sure it works for you -> #28


Missing Command Error

I'm using Visual Studio 2015 RC to a project in Cordova and decided to use the ContentSync plugin to sync my files. I made a compilation for Windows Phone (Universal) and when I try to use the plugin, it appears as return on error: Missing Command Error.
I tried to debug the Sync.cs but could not figure out something useful.
Anyone ever been in this situation?

Same error here. Did you resolve the issue?

Which version of windows you are trying ? 8 or 10 ?

@snehasis and @stefanoavancini I use Windows 8.1. I discover what is the problem. The phonegap-plugin-contentsync is not supported on Windows Universal Apps. Thanks for the answer. We will waiting a stable version to use on Windows Universal Apps.


[Docs Bug 🐞 report]: Repeated context in Event-Driven Architectures page

Describe the bug you found in AsyncAPI Docs.
This was accidentally repeated in " However, that's not always the case, as Martin Fowler explains in his talk "the many meanings of Event-Driven Architecture" "

How to reproduce the bug

Visit https://www.asyncapi.com/docs/getting-started/event-driven-architectures.
Scroll down until you found the section "Why "event-driven" and not "message-driven"?".
The position of the docs-bug at the end of the second paragraph and also the last paragraph.

Expected result
Only the one with a link to the youtube talk should remain, the other one needs to get deleted.
Attach any resources that can help us understand the issue.
Link to the highlight.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@luphieanza hey, there is a PR opened already that fixes it -> https://github.com/asyncapi/website/pull/686
let's keep this issue opened and once PR is merged, it will be closed automatically

Hi @derberg, I found this issue from @alequetzalli, She gives instructions to me for creating an issue of it and working on it, I don't know if there is any PR on it.

@luphieanza no worries. Sometimes it happens that some things are overlooked and people duplicate each other 👍🏼

Is this issue fixed ?

@darp99 It's still on the review phase for the PR.

This has been fixed and live for a while now:
https://www.asyncapi.com/docs/tutorials/getting-started/event-driven-architectures


Turn off logs

Edit: Is there a way to programatically disable logs from the runtime?

use env LOG_LEVEL=error

Sorry, I meant not from the CLI, but using the setup, setupWithServer functions 😅
Even though, that's a pretty good solution for now.

Right. We can add a log level parameter to be able to configure it.


Inconsistency in STAC.yaml and api-spec.md for search endpoint supported methods.

The STAC.yaml has been updated to reflect GET as an optional method for the /search endpoint but the api-spec.md seems to only show POST support?  I could just be misreading it but should this be updated to reflect the new optional GET method?

The whole section is a bit confusing, I think. The section title is "HTTP Request Methods and Content Types" but the text is basically only describing which content types are supported so I'd propose to change the title to "HTTP Content Types". The text just says that you can use some content types with POST /search, but it doesn't say it's not allowed to use GET. It just doesn't specify a content type for GET /search. Also, I think the chapter should be moved down a bit and be above "Filter Parameters and Fields". And then we should probably add a "Method(s)" column for the "... endpoints" sections. That should clarify it.

Hey @philvarner, I think you wrote the section "HTTP Request Methods and Content Types". I'm trying to understand the "HTTP Request Methods and Content Types" can you explain it? I don't get it. What POST endpoints is spoken about? What does the bullet point about GET tells me? I think we should clarify that section.

I'll take a look at it

@philvarner @joshfix @cholmes and others involved here: While working on PR #731 I realized that the API and README are diverging. The API clearly says:

This method [GET /search] is optional, but you MUST implement POST /search if you want to implement this method.

and

This method [POST /search] is mandatory to implement if GET /search is implemented.

I guess we should align the README or decide to define it differently also in the API spec.
My personal opinion is that the API spec should be left as is (/search is optional) and change the README accordingly. Reason as stated above is that implementing STAC API should also be possible if you don't expose items or don't want to implement search, but just allow browsing. I'd be fine to change "optional" to "recommended".
The issue regarding the search rel types is not really an issue, it's actually specified, but I clarified it with PR #731.


style(checkbox): update checkbox to sip-34 design

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
before

after

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Oh - side note - I noticed some rogue checkboxes in the "Filter Scope Modal" today that use a hard coded older theme color.

Codecov Report

Merging #10416 into master will increase coverage by 1.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10416      +/-   ##
==========================================
+ Coverage   70.80%   71.84%   +1.03%
==========================================
  Files         604      196     -408
  Lines       32426    21018   -11408
  Branches     3414        0    -3414
==========================================
- Hits        22960    15100    -7860
+ Misses       9354     5918    -3436
+ Partials      112        0     -112

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
71.84% <ø> (+1.45%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/connectors/druid/views.py
67.76% <0.00%> (-1.63%)
:arrow_down:

superset/utils/dict_import_export.py
54.23% <0.00%> (-1.58%)
:arrow_down:

superset/connectors/connector_registry.py
83.33% <0.00%> (-1.12%)
:arrow_down:

superset/models/slice.py
83.82% <0.00%> (-0.84%)
:arrow_down:

superset/utils/dashboard_import_export.py
60.00% <0.00%> (-0.72%)
:arrow_down:

superset/tasks/cache.py
73.52% <0.00%> (-0.39%)
:arrow_down:

superset/views/utils.py
83.85% <0.00%> (-0.28%)
:arrow_down:

superset/commands/utils.py
100.00% <0.00%> (ø)

superset/utils/import_datasource.py
100.00% <0.00%> (ø)

...hboard/components/gridComponents/new/NewColumn.jsx

... and 412 more

Continue to review full report at Codecov.

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


document formatter

I can't find a way to format the .pde files in VS Code... I get a message "There is no document formatter for 'pde'-files installed."
Is there a formatter available?

This just came up with #52
A code formattor is well out of the scope of this extension, and is clearly stated as such in the readme. I don't think making a processing specific formatter would make sense either. Not compared to extending support of an extension java formatter to also work in .pde files...

Still, I’ve found the extension works really well and I appreciate being able to use it.


Implicit extension API (i.e. HTTP client lib must be required before webmock) is confusing

Currently, WebMock decides to monkey patch (or not) the supported HTTP client libraries by detecting the presence or absence of the necessary constants.  This works, but it is a confusing, implicit API because it relies upon the require order.  If a project requires WebMock before the HTTP library, then the library will not be monkey patched by WebMock and it will not be able to stub requests made through it.  This is even more of a problem when using something like Bundler since Bundler will require your gems, and there isn't an explicit way to make it require things in a particular order.  I've had a couple VCR users open issues about how a particular HTTP library wasn't working with VCR and the problem was that they weren't requiring the HTTP library before VCR required WebMock.  Wycats has also blogged about the problems with this approach.
I'd like to suggest that WebMock should move away from this implicit API.  Instead, here's how I think it would ideally work:

WebMock would provide an explicit API like WebMock.stub_http_libs :net_http, :patron.
This would require the necessary WebMock monkey patches (each of which requires the necessary HTTP client gem) for the configured HTTP libraries; the various extension files would not all be required automatically, as they are now.
Switching directly to this API would essentially be a breaking change, so for now the existing way should continue to work with a deprecation.  The best way I can come up to do this is to add some code to WebMock.stub_request so that the first time it is called, it checks to see if any http libs have been configured, and if not, it prints a deprecation warning and calls WebMock.stub_http_libs with the libraries that have already been loaded based on the presence of the constant.  Whenever you release the next major release (WebMock 2.0.0) you could remove this deprecation code.

What do you think?

I believe this change broke my usage of WebMock + VCR for versions >= 1.7.  We record SOAP interactions.  With WebMock 1.6.4 we used this as our spec/support/vcr.rb (simplified):
This needs to be loaded before webmock is loaded, soap4r uses httpclient
require 'soap/streamHandler'
Configure VCR
VCR::Config.stub_with :webmock
Any way around this impasse?
Reference to my issue: https://github.com/myronmarston/vcr/issues/109

No idea why 1.7.0 would break it. If soap4r already loads httpclient, then this change shouldn't matter as webmock
would not load it twice.
If you discover any more details please let me know.


Cleanup of sections 1 and 3; moved diagnostics to section 3

Can you add nbreview?

Added.

Those three still seem to have invalid json.

Ugh, not sure how that happened. Fixed now.

:+1:


Use of Seeding

What is the purpose of seeding the database? Can the program function without it?

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

ID: a0a4022c-7ef1-3c30-4f9d-cf521a57a44a
Version Independent ID: a0b5e15c-d747-8710-95fb-a55c09861a1e
Content: Work with SQL in an ASP.NET Core MVC app
Content Source: aspnetcore/tutorials/first-mvc-app/working-with-sql.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.


kp_objectInits.sqf

contains helipads, add vn helipads line 35

nice find, I wasn't aware that was done there. thank you!


Adds unit tests for providers parse payload

everything in same files was getting difficult to navigate
so moved detect and parse payload to separate files
and
adds missing unit tests for providers
Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

yes please, more splitting and refactoring!
💯 🎯
feel free to merge it when CI is green and conflict resolved.

weird errors, let's retry


Fixes to bring support yaml in sync with Prime correct response payloads

Description
Found some broken things that needed to be fixed to make load testing prime workflow succeed.
Needed to bring mtoShipments and mtoAgent code in support.yaml up to date with prime.yaml (hate that this is necessary)
Basically copy pasted from prime to update the following:

Updated MTO Shipment support model/payload to match prime version
Updated MTO Agent yaml and model/payload funcs to match prime.yaml
Updated UpdatePostCounseling info to return entitlement, which was in the redoc but not being populated

Setup
Test the getMTOShipment, updateMTOAgent and UpdatePostCounseling endpoint to check that they work and return all info expected in the redoc.
References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 74b7522269aad83ebeb099c6b4f8949d24ffeb65


Please Add the manifest Link in below sample Table for Tab, Bot and Message Extension (ME) SSO sample

Please add the manifest Link for the below Code Sample Table

Sample name
Description
.NET
Node.js
Manifest

Tab SSO
Microsoft Teams sample app for tabs Azure AD SSO
View
View,Teams Toolkit

Tab, Bot and Message Extension (ME) SSO
This sample shows SSO for Tab, Bot and ME - search, action, linkunfurl.
View
View
View

Manifest link for sample: https://github.com/OfficeDev/Microsoft-Teams-Samples/blob/main/samples/app-sso/csharp/demo-manifest/App-SSO.zip
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 410609cf-c930-72de-319d-351212f71b8c
Version Independent ID: 410609cf-c930-72de-319d-351212f71b8c
Content: Code configuration for enabling SSO for tabs - Teams
Content Source: msteams-platform/tabs/how-to/authentication/tab-sso-code.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: surbhiguptaSample name	Description	.NET	Node.js
Tab SSO	Microsoft Teams sample app for tabs Azure AD SSO	View View,
Teams Toolkit
Tab, Bot and Message Extension (ME) SSO	This sample shows SSO for Tab, Bot and ME - search, action, linkunfurl.	View View

@surbhigupta12 - Could please help here to add the manifest link for Tab, Bot and Message Extension (ME) SSO sample.


Prepare release with Duncan

Repo is now public which is an requirement to release via pypi

Sent email to Duncan: "Ragsdale, Duncan"<EMAIL_ADDRESS>

Duncan has confirmed he has done it

Introducing now a branch "vX.Y.Z" (e.g. v0.0.1) will trigger a pypi release.

sorry, it has to be a tag :-)

We would be ready to release 0.0.1. But let's test that later


Nit use credentials

What?
As per the title.
Why?
https://github.com/kubeflow/pipelines/blob/ccc763fb718569a21b95a107ffe5beb023334742/sdk/python/kfp/_auth.py#L32
LOCAL_KFP_CREDENTIAL = os.path.expanduser('~/.config/kfp/credentials.json')

/assign @Bobgy @IronPan @neuromage @Ark-kun @numerology
PTAL 🔍
Thank you all

@subodh101 Hi, any update this?
cc @Bobgy (left comments above), @RFMVasconcelos

Thank you.
Closing it for now. I thought it was a nit.
/close


Deploy Checklist: New Expensify 2022-09-08

Release Version: 1.1.98-1
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/7846
[x] https://github.com/Expensify/App/pull/9441
[x] https://github.com/Expensify/App/pull/10455
[x] https://github.com/Expensify/App/pull/10488
[x] https://github.com/Expensify/App/pull/10557
[x] https://github.com/Expensify/App/pull/10659
[x] https://github.com/Expensify/App/pull/10668
[x] https://github.com/Expensify/App/pull/10669
[x] https://github.com/Expensify/App/pull/10723
[x] https://github.com/Expensify/App/pull/10742
[x] https://github.com/Expensify/App/pull/10769
[x] https://github.com/Expensify/App/pull/10804
[x] https://github.com/Expensify/App/pull/10810
[x] https://github.com/Expensify/App/pull/10812
[x] https://github.com/Expensify/App/pull/10834
[x] https://github.com/Expensify/App/pull/10837
[x] https://github.com/Expensify/App/pull/10839
[x] https://github.com/Expensify/App/pull/10841
[x] https://github.com/Expensify/App/pull/10844
[x] https://github.com/Expensify/App/pull/10856
[x] https://github.com/Expensify/App/pull/10867
[x] https://github.com/Expensify/App/pull/10908

Deploy Blockers:

[ ] https://github.com/Expensify/App/issues/10901

Deployer verifications:

[x] I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
[x] I checked Firebase Crashlytics and verified that this release does not introduce any new crashes.

cc @Expensify/applauseleads

:rocket: All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.1.98-0 :rocket:

Checking off #10867 as there's no testing required

@Julesssss Regression is almost completed.
PR https://github.com/Expensify/App/pull/10455 - We are not sure how to test this. Video and steps do not match. Need some help with this one.
PR https://github.com/Expensify/App/pull/10488#issuecomment-1240141936 - QA team is not able to test Wallet
PR https://github.com/Expensify/App/pull/10659 is failing https://github.com/Expensify/App/issues/9705. Since its in PROD. Checking off
PR https://github.com/Expensify/App/pull/10723 is failing  https://github.com/Expensify/App/issues/10897. Its not in PROD, but as a new feature. Are we ok to check off or this will be a blocker?
Finishing few TR steps as well. Will share final summary in a bit

PR https://github.com/Expensify/App/pull/10723 is failing https://github.com/Expensify/App/issues/10897. Its not in PROD, but as a new feature. Are we ok to check off or this will be a blocker?

Yes, looks like the issue is just with the offline part, wherein when coming back online the workspace disappears. Not deploy blocker worthy so I'll check it off.

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.98-1 :rocket:

@chiragsalian Regression is completed.

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.98-1 has been deployed to staging :tada:

Im checking https://github.com/Expensify/App/issues/10901, since we're trying to get https://github.com/Expensify/App/pull/10908 out the door soon as its affecting customers. https://github.com/Expensify/App/issues/10901 is also an edge case and I wasn't able to reproduce it.

:shipit:

Thanks @chiragsalian


Date Functions

Please clarify on the page whether the displayed date respects date localisation or whether only the rare US order (MM/DD/YYYY) is displayed

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

ID: bc130656-2e47-da15-cf41-40bc9661b592
Version Independent ID: 127c1432-3f3b-8056-4b25-6fd19be5e40f
Content: Text Features - Adaptive Cards
Content Source: AdaptiveCards/authoring-cards/text-features.md
Product: adaptive-cards
GitHub Login: @matthidinger
Microsoft Alias: mahiding

It appears to only do the US formatting and not respect the users local, we have this same issue


Update - Benefits of Agile

Update - Benefits of Agile

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #27719

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


document $*VM

including how to introspect its contents:
14:31 < lizmat> m: dd VM.^attributes>>.name   # [Coke]  ??
14:31 < camelia> rakudo-moar b703d6: OUTPUT«("\$!config", "\$!prefix",
                 "\$!precomp-ext", "\$!precomp-target", "\$!precomp-dir",
                 "\$!name", "\$!auth", "\$!version", "\$!signature",
                 "\$!desc")␤»

It is already mentioned here: http://doc.perl6.org/language/variables#Dynamic_variables

$*VM variable itself is already mentioned. Otherwise, this is a dup of https://github.com/perl6/doc/issues/503


Adding time to total-data.json and lap-data.json

Hi,
I added the time (or duration) parameter to the data files. I was not sure if this is a desirable feature for anyone else, however I needed this information for my research, and I thought it may be useful for other people too.
What prompted me to add the duration was the discrepancy I noticed between the duration calculated by EcoCI and the duration of the given step provided directly by the GitHub API. I am not sure if this is a big problem, but I wanted to leave this here as well in case it is an uncaught issue.

Uhh, this looks nice, ty!
We are actually not using that data export too often, so I have to loop Dan in to give it a review. Looks legit for me though on first glimpse.
@dan-mm Please give it a look and merge if ok

Hi @nstruharova - it looks good to me! I'll merge it in after tests.
Also I think I can shed some light on the time discrepancy - the timer in Eco-CI only starts its internal timer after the initial setup, so that overhead is not attributed to the user's workflow. Additionally, the timer is reset at the end of the make_measurement step, so similarly some of Eco-CI's functionality is similarly not attributed to the user's workflow (though, as I'm taking another look at the code to verify this, the actual model run does happen within the timer, so that will be a part of it). In general, our design philosophy was that Eco-CI's functionality itself should not be a part of the energy estimation.


string_view instead of string?

One problem with std::string_view is, it's not guaranteed to be a null-terminated string.
I would love to replace const std::string& with something like std::string_view, but I wouldn't recommend it.
We probably need something like zstring_view. Shouldn't be that hard to implement

Agreed, and because performance isn't the primary goal of this library, it may not be worth its adoption.


Bad Address Index

Godot version
v4.0.stable.official [92bee43ad]
System information
macOS 13.2.1 (22D68), Intel Intel(R) Iris(TM) Plus Graphics - Supported, Integrated Vulkan API 1.2.231 - Forward+
Issue description
Howdy 👋
I came across a weird error that I've narrowed down to:

Inherited scenes
Inherited class
Instantiation

When using a combination of those, I get:

Steps to reproduce
This is a very reduced version of a project I work on, so don't expect it to "make sense".
Since the code is so short, here's:
# base.gd
extends Node2D
func _ready(): add_child(preload("res://blue.tscn").instantiate())

# red.gd
extends Node
class_name Red
var something = 1

# blue.gd
extends Red
class_name Blue
func _ready(): get_parent().add_child(preload("res://green.tscn").instantiate())

# green.gd
extends Blue

In the same fashion, blue.tscn is inherited from red.tscn and green.tscn is inherited from blue.tscn.
When this code runs, it fails on var something = 1 with the error:

Maybe related to this?
https://github.com/godotengine/godot/blob/31eccb5501ddc92b4a17fd6ae33dca4ad217702c/modules/gdscript/gdscript_vm.cpp#L633
There are a few changes that prevent the code from failing:

remove/comment var something = 1
make Red and/or Blue and/or Green extends from ColorRect
remove green.gd script from the green.tscn scene

Minimal reproduction project
Archive.zip

There is a cycle between Blue and Green. The inheritance relationship of scenes is opposite to that of scripts.

Ah good catch, is this a case where a cycle should be detected and give a more meaningful message?

Would be great to have some more direction when attempting to fix such errors.
Currently refactoring a bit of my large project, now I'm dealing with this issue again and there's really not much to do except comment out sections of a large section of my codebase until I find the single line which is causing the issue.
Previously it was caused by referencing a class_name inside a function definition, but this time who knows 🤷

I went and wrote the following gist:
https://gist.github.com/tavurth/0d4c49a0a800cbc27f80c3a68f0c8ee7
Code is a bit messy as I was in a rush, but it works to detect such circular dependencies and can also output a graph of your project.
The class structure of my game:

The circular dependencies detected:

4.1 dev:

  scene/resources/resource_format_text.cpp:481 - res://green.tscn:6 - Parse Error:
  Failed loading resource: res://green.tscn. Make sure resources have been imported by opening the project in the editor at least once.
  scene/resources/packed_scene.cpp:90 - Condition "nc == 0" is true. Returning: nullptr

@dalexeev this is a different issue I'm pretty sure.
referenced non existent resource
Most likely means that your scene is missing, or corrupted in some other way?

I think the ResourceLoader now recognizes this cyclic dependency which is causing the scene to fail to load.

@dalexeev seems like you are running an example scene anyway? Perhaps you could post the zip here?

Currently, it's not possible to load cyclically scenes, ie. scenes with scripts that their definitions depend on the loading script.
Originally, I had intended to support this, but my PR couldn't be merged. See the discussion for more info.
https://github.com/godotengine/godot/pull/71004

Just in case it helps someone else:
I came across something that seems very similar to this bug. I had the same 'bad address index' error message.
Mine was related to type annotations: I couldn't have var b: B = null in class A, seemingly because in class B at some point I had var a2 = A2.new() with A2 a subclass of A, but Godot was fine with var b = null.
It was also related to loading scenes (of type A, or inheriting from A) in an autoload Foo, and my main scene was inheriting from B.
I fixed it in the autoload Foo, simply by transforming
var packed_scene = load("res://inherits_from_A.tscn")
into
@onready var packed_scene = load("res://inherits_from_A.tscn")
Seemingly, without the @onready, Godot tried to load the scene somewhat too early to handle the type reference of B in A (at least that's what I can only assume. Hope it helps!


All contributor bot additions

@all-contributors please add @ojasjain24  for code, doc, ideas, tests, mentoring, maintenance, projectManagement

@all-contributors please add @domesticmouse for code

@all-contributors please add @ojasjain24 for design

@all-contributors please remove @ojasjain24  for mentoring,


YoWASP yosys fails to generate SVG diagrams

Currently, YoWASP Yosys fails to generate SVG diagrams. However, the .dot file is created correctly in the output directory.
The problem seems to be related to dot execution:
3. Generating Graphviz representation of design.
Writing dot description to `yosys.dot'.
Dumping module ADDER to page 1.
Exec: dot -Tsvg 'yosys.dot' > 'yosys.svg.new' && mv 'yosys.svg.new' 'yosys.svg'

Steps to reproduce:
wget https://raw.githubusercontent.com/SymbiFlow/sphinxcontrib-verilog-diagrams/master/tests/verilog/adder.v
python3 -c "from yowasp_yosys import *; run_yosys(['-p', 'prep -top ADDER ; cd ADDER; ; show -format svg -prefix yosys', 'adder.v'])"

Comparison with standard Yosys:
wget https://raw.githubusercontent.com/SymbiFlow/sphinxcontrib-verilog-diagrams/master/tests/verilog/adder.v
yosys -p 'prep -top ADDER ; cd ADDER; ; show -format svg -prefix yosys' adder.v

Yeah, there needs to be a custom hostcall used to implement Yosys' exec_command. I had planned to implement it but other tasks were higher priority.

In the end I feel that this functionality is not important enough to warrant being implemented. Plus it would cause difficulty for the JavaScript port.


Feature Request: Autocapture Screenshots from Predefined Virtual Camera Poses

Summary
I'm writing to propose a new feature for the Rerun visualization tool: the ability to autocapture screenshots from fixed virtual camera poses for objects rendered in the 3D viewport (point clouds, 3d objects, etc.). This feature would significantly enhance our data visualization and debugging processes, especially in the context of machine learning model development and robotics.
Background
At our robotics company, we frequently work with multiple datasets to train and evaluate our machine learning models. Visualizing these datasets from various perspectives is crucial for in-depth analysis and effective debugging. Currently, Rerun allows us to visualize data on a per-need basis, but it lacks the capability to automatically capture and store visual snapshots from specific, predefined camera angles.
Feature Request
I would like to request the addition of an "Autocapture" functionality to Rerun. This feature should allow users to:

Define multiple virtual camera poses within the 3d viewport.
Automatically capture screenshots from these fixed camera poses.
Save these screenshots in a designated folder, with options to format file names for easy identification (e.g., dataset name, camera position, timestamp).

Use Case and Benefits
This feature would be immensely beneficial because it allows us to:

Enhanced Debugging: Quickly log visual data from multiple datasets and capture snapshots for thorough examination.
Consistent Visualization: Maintain uniformity in visual perspectives across different datasets and different model updates.
Efficient Documentation: Easily attach before-and-after snapshots to PRs (Pull Requests), which makes out development process far more effective and consistent over time.
Streamlined Workflow: Automate the visual logging process, akin to scripts that generate metrics over multiple datasets, saving time and effort, especially if we can run this for hundreds of datasets.

Conclusion
Implementing this feature would greatly streamline our workflow and enhance our ability to analyze and debug complex datasets in robotics and machine learning applications. We believe it would also be a valuable addition for the broader Rerun user community engaged in similar tasks.
Thank you for considering this feature request.

Hello @shalins. Thanks for your input. Your proposal is legitimate and in-line with our roadmap.
The screenshot feature exists already via the command line. You can use  rerun --screenshot-to /path/to/screenshot.png /path/to/file.rrd. It will however be of limited use until we build support for fine-grained control from code of the visualisation content (views, camera angles, etc.). It turns out that this is our next major focus over the coming weeks/months. We refer to this effort as "blueprint", and you can track progress with this label.

To add to what @abey79 wrote though, I don't think headless rendering / screenshots is on our near term roadmap unfortunately so you'd still have to do this on a machine with a screen.


Nice to have features like dragging the states from tree and dropping it in the string constant

I just imagine like... while I design my system using LV, I know to which states  I have to go. Instead of copying the states and pasting it, it would be nice if I can simply drag and drop the states from the tree to my string constant which has the list of states to go.

I have a POC for this feature.


[Snyk] Upgrade @fortawesome/vue-fontawesome from 3.0.0-5 to 3.0.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @fortawesome/vue-fontawesome from 3.0.0-5 to 3.0.3.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 4 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-01-24.

Release notes

Package name: @fortawesome/vue-fontawesome

3.0.3 - 2023-01-24Changed

NPM download @ fortawesome/vue-fontawesome-latest is now set to Vue 3; to download the Vue 2 package you will have to use @ fortawesome/vue-fontawesome-latest-2, which is described in our Vue setup docs
CI workflow updated for testing
README.md and package.json updated for new contributor

Added

Missing TypeScript animations added  (github issue #428)
Missing TypeScript sizes added (github issue #415)

3.0.2 - 2022-11-07Changed

Vue 3 Composition API TypeScript support (github issue #276)
Updated README.md with a spelling correction, linter fixes, and new contributor
Updated icon example in App.vue to use fixed-width rather than full-width

Added

Missing tests

3.0.1 - 2022-06-17Changed

README.md Documentation now points to https://fontawesome.com/docs/web/use-with/vue/

3.0.0 - 2022-06-07Added

New animations for bounce and shake
Feature to call icons using a string format

Fixed

Animations for beat, fade, beat-fade, flash, spin-pulse, and spin-reverse
Tee-shirt sizes to include 2xs, lg, xl, and 2xl
Flip animation when used by itself

3.0.0-5 - 2021-10-18Fixed

Include 1.3.0-beta versions in peer dependencies

    from @fortawesome/vue-fontawesome GitHub release notes

Commit messages

Package name: @fortawesome/vue-fontawesome

21f8f7d add contributor and fix spelling mistake (#430)
4241f0d Vue3 - update workflows ci (#377)
aed76ee add ts missing animations (#429)
94dade0 Add missing ts sizes (#427)
e97ee3f Release 3.0.2
4ec8d01 restore package-lock (#410)
0260208 fix: Type definitions for Vue 3 Composition API (#355)
49de51d Revert "Vue3 fix setup link (#409)"
33f2bc2 Vue3 fix setup link (#409)
bd84f81 Vue3 - add some missing tests (#398)
14d82b3 Bug fix: Vue 3.x documentation link is not working (temp fix) #389
06b4d62 Release 3.0.1
11d8a51 update vue3 readme doc (#376)
7464e8a Release 3.0.0
8634aed Vue3 add bounce shake tests (#366)
efe9812 Fix comments in code examples
7a4d865 Release 3.0.0-5

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Unit tests passed locally.


Provide a way for the user to change the grid size without recompiling

Does Fortran make this difficult by defaulting to fixed-size arrays?
I can imagine several ways to achieve this:

Find the dynamically-sized arrays feature (it must exist) and use it.  Are there any disadvantages to this?
Replace the compile-time constant sizes with compile-time constant maximum sizes, and only operate on the subsection of the array that the user actually asked for.  This wastes some amount of memory, but presumably not enough to be a problem; and requires recompilation to change the maximum, but that's presumably less onerous than having to recompile to change the resolution at all.

Regardless, we should make sure that we still have bounds checks for indexing those arrays, to the extent this is possible.

This would be a good feature.
The Fortran allocatable arrays feature (described here: http://www.pcc.qub.ac.uk/tec/courses/f90/stu-notes/F90_notesMIF_11.html) would let us do this. I think the only downside is the possibility of memory leaks.
I'm not sure about static arrays with some maximum size. Potential changes in grid size are likely to be very large - factors of ten or more.

How does the program's runtime and memory use scale with the grid size?  That may affect this decision, and in any case we should know, because we should document it for the users.  (Notably, what are the dimensions of that matrix that needs inverting?)

The memory usage scales quadratically in nx or ny - so doubling the grid resolution quadruples the memory requirement. The run time scales as the cube, since the time step has to be halved to maintain stability.
For the n-layer physics the performance may be slightly worse since the number of iterations for the matrix inversion to converge also scales with the grid. The size of the matrix that needs inverting is the size of the grid, so nx by ny.

Just to make sure I understand: memory use is O(nx ny layers), reduced-gravity run time is O(nx ny layers nt), (where nt should be O(nx + ny) to be stable), and the additional matrix being inverted for n-layer physics has O(nx ny) elements (not rows, which would presumably not fit into O(nx ny) memory)?

I'd say that nt should be O(max(nx, ny)), rather than the sum.
Otherwise, yes, that's all correct.

Well, O(max(x, y)) = O(x + y), because those two quantities cannot differ by more than a factor of two (assuming x, y > 0).


Migrated site to Material for MkDocs

Migrated the existing Reuse Standard to use Material for MkDocs. This provides a number of advantages:

Better and consistent site navigation.
Automatic display of the standard versions (based on Git branches), so people can view different versions of the standard.
Flow diagrams are now generated in code using Mermaid, which means it's easier to update them without having to edit images.

Added new GitHub Actions workflow that will build and deploy the site to GitHub Pages whenever it gets merged to the main branch. NOTE: currently GH Pages is set up to use the main branch for the site, but this will need to be changed to use the gh-pages branch instead (that's where the build action will push the built files).

All the content from the current standard has been copies across as-is, so no changes required to the version numbers.

@kim-reath Yes please!

@tomvanenckevort-hp cool I've just updated that to be gh-pages now:

@kim-reath I've just merged the PR and the build completed fine (all correct files are in the gh-pages branch). But the site now shows a 404.
Can you just double-check the settings are still as per your screenshot after the build was done?

@tomvanenckevort-hp it looked like the custom domain value had disappeared. I've added that back in and doesn't seem to be a 404 for me now.

@kim-reath All good now. Thanks!


Add SNMP topology probe

It's one way to retrieve fabric topology/metrics

I spike with safchain about this, it was be great to get SNMP capabilities added to skydive, to build typologies!

Anyone started work with this?


Implement resource details for DaemonSet

Is your feature request related to a problem? Please describe.
When fetching resources for a Module, some resources are supported to return details about a specific resource. For example, the endpoint for Deployments will return more information about pods and their statuses, and the endpoint for Services will return information about the ports.
If you want to fetch information about a Deployment form default namespace called demo-app you would call:
/resources?group=apps&version=v1&kind=Deployment&name=demo-app&namespace=default
The goal of the issue is to support DaemonSets on the same endpoint. The endpoint for fetching DaemonSet data would look like this: /resources?group=apps&version=v1&kind=DaemonSet&name=&namespace=
The handler function for the endpoint is here, and you will have to handle a new type here.
You can add data about pods and its status similar to what we are doing with Deployments.
Refer to this PR on adding new types https://github.com/cyclops-ui/cyclops/pull/259

This sounds interesting. Can I take this one ?

Hey @FengMeizuo, sure!

You can use the following template to create a DaemonSet:
repo: https://github.com/cyclops-ui/templates
path: demo
version: test-daemonset-endpoint