[SPARK-30895]:The behavior of CsvToStructs should not depend on SQLConf.get

What changes were proposed in this pull request?
In the PR, I add the nameOfCorruptRecord parameter to the CsvToStructs expression.
Why are the changes needed?
This allows to avoid the issue when the configuration change between different phases of planning, and this can silently break a query plan which can lead to crashes or data corruption.
Does this PR introduce any user-facing change?
No
How was this patch tested?
By CsvExpressionsSuite.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

cc @MaxGekk

Test build #118780 has started for PR 27663 at commit 17ce9b9.

Merged build finished. Test PASSed.

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

Test build #118780 has finished for PR 27663 at commit 17ce9b9.

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

Merged build finished. Test PASSed.

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

Test build #118845 has started for PR 27663 at commit b40cbc5.

Merged build finished. Test PASSed.

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

Test build #118845 has finished for PR 27663 at commit b40cbc5.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #118958 has started for PR 27663 at commit f4150c5.

Merged build finished. Test PASSed.

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

Test build #118958 has finished for PR 27663 at commit f4150c5.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #118976 has started for PR 27663 at commit 677c265.

Merged build finished. Test PASSed.

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

Test build #118976 has finished for PR 27663 at commit 677c265.

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

Merged build finished. Test PASSed.

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

Test build #119223 has started for PR 27663 at commit b8b77ba.

Merged build finished. Test PASSed.

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

Test build #119223 has finished for PR 27663 at commit b8b77ba.

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

Merged build finished. Test PASSed.

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

Closing this per the discussion in the JIRA


switch to true|false for protectionsState param

Reviewer:

Description:

Steps to test this PR:

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

Current dependencies on/for this PR:

main

PR #2326   👈

This stack of pull requests is managed by Graphite.


Correct await-ed inline snapshot indentation

Summary
When testing asynchronous code using .resolves/.rejects it is mandatory to await the expect. When combined with an inline snapshot, the snapshot is not indented correctly. It is aligned to the expect not the await.
Example
it('is a test', async () => {
  await expect(Promise.resolve({ a: 'a' })).resolves.toMatchInlineSnapshot();
});

Currently becomes:
it('is a test', async () => {
  await expect(Promise.resolve({ a: 'a' })).resolves.toMatchInlineSnapshot(`
          Object {
            "a": "a",
          }
        `);
});

After the change:
it('is a test', async () => {
  await expect(Promise.resolve({ a: 'a' })).resolves.toMatchInlineSnapshot(`
    Object {
      "a": "a",
    }
  `);
});

Test plan
See the unit test in packages/jest-snapshot/src/tests/InlineSnapshots.test.ts:633

https://github.com/facebook/jest/releases/tag/v28.1.3


First commit xiami-ble parser [WIP]

Work in progress.
First commit for the xiaomi-ble parser.
I copied the inkbird-ble parser and will change the parser later, this first commit it is to get all the side things working, like docs, packages

I'm going to move the name field per this comment here https://github.com/home-assistant/core/pull/75531#discussion_r926394972 but I don't think it will actually change the code for this as it will just be an underlying lib bump

ok, all the work on the parser and tests need to be done anyways, this PR is meant for setting stuff up and having a work environment.

I guess these failing test are not an issue, they fail on not being able to find xiaomi-ble pypi package, which is logic, as it isn't there yet.

poetry run pytest
That should pick them up

Can I merge the current PR, just to have a check that all side things are in place and working?. I will make an note that it is a non-functional version

Can I merge the current PR, just to have a check that all side things are in place and working?. I will make an note that it is a non-functional version

Go for it. It won't hurt anything. You'll need to publish it to PyPi manually once and then generate a token and put it in the release environment so it happens automatically on merge in the future


Office 365 Outlook incorrect OAuth redirect

Describe the Bug with repro steps
I've noticed an issue where in the new designer, the OAuth pop-up redirects to login.live.com which is the login page for personal Microsoft accounts, not work accounts. Thus it fails to recognize my email address.

Using the new designer add a Send Email (v2) action via the Office 365 Outlook connector
Try creating a connection
Sign-in pop-up redirect to login.live.com instead of login.microsoft.com

Note: I've had a couple others test this and it's not entirely reproducible. I'm not sure what the difference is, but at least one other person reports the same, albeit intermittent. Some days it works, others not.

If I use the fallback url, it redirects to login.microsoft.com as expected and I can successfully authenticate.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
n/a

Screenshots or Videos

Browser
Edge
Additional context
No response
AB#24810598

From what I can tell, we have two different outlook connectors for whatever reason, one is called Outlook.com and the other is Office 365 Outlook.  When trying to reproduce the issue, the Outlook.com connector always redirected to the login.live.com url, while the Office 365 Outlook connector always went to the proper login.microsoftonline.com url.  This is the same behavior I'm seeing in legacy designer.
Looking at the gif you posted, you are using the Outlook.com connector, @cmeadowstech can you try out the Office 365 Outlook connector instead and see if it works?

Hi @rllyy97, thanks for taking a look. I feel silly, it looks like you are right. I'm so used to searching 'Outlook' and choosing the first 'Send an Email (V2)' action I see that I hadn't even noticed there were two connectors. In the past the correct Office 365 Outlook always returned first so habit got the best of me.
Thanks again, I think we can close this.

@cmeadowstech No worries!  I was confused too when I was trying to investigate


Using "global" search with Leap disconnects neovim and vs code cursors?

When I have leap set up to search globally
vim.keymap.set('n', 's', function ()
  local focusable_windows_on_tabpage = vim.tbl_filter(
    function (win) return vim.api.nvim_win_get_config(win).focusable end,
    vim.api.nvim_tabpage_list_wins(0)
  )
  require('leap').leap { target_windows = focusable_windows_on_tabpage }
end)

I get labels from both open panes in VS Code

But if I type a label from the left pane (while my cursor is in the right one), I get some odd behavior. The line I intended to jump to is highlighted (see the def parse_args line on the left, the second function)

but the cursor remains on the right pane. While I'm in normal mode, all commands act as if my cursor is now in the left pane (e.g. I can move that highlighted line up or down, dd the line, etc). But if I enter insert mode, I'll be back where the red cursor is in the right pane.
Has anybody been able to get leap (or similar) to work for searching multiple windows? Or is an error here expected and this isn't supported?
(note for reproducibility: I can usually but not always get this behavior. The other outcome is that jumping to the other pane just fails. Also, if I jump back to the pane where the red cursor is, things are normal again)

for searching multiple windows?

Surprised that works at all, lol. Visual plugins are a best-effort thing for now.

Yeah, vscode-neovim does not support any multi-window actions.


openai.BadRequestError: Error code: 400 - Unrecognized request argument supplied: dataSources.

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
When I use chat.completions.create(), and give extra_body, encounter this error.
I've checked endpoint uri, key, ai search endpoint and key. Nothing wrong.
After I remove extra_body, it worked.
To Reproduce
client = AzureOpenAI(
azure_endpoint="",
api_key="",
azure_deployment="",
api_version="",
)
completion = client.chat.completions.create(
model=deployment,
messages=[
{
"role": "user",
"content": "What are my available health plans?",
},
],
extra_body={
"dataSources": [
{
"type": "AzureCognitiveSearch",
"parameters": {
"endpoint": os.environ["AZURE_AI_SEARCH_ENDPOINT"],
"key": os.environ["AZURE_AI_SEARCH_API_KEY"],
"indexName": os.environ["AZURE_AI_SEARCH_INDEX"]
}
}
]
}
)
Code snippets
No response
OS
windows
Python version
Python 3.11.5
Library version
openai v1.23.2

@DavidHWWang which API version are you targeting? The arguments you're supplying in the extra_body seem appropriate for the older preview version, but not newer versions of the API. I recommend updating to the latest GA version 2024-02-01 if possible which accepts the data sources in snake_case:

client = AzureOpenAI(
    azure_endpoint="",
    api_key="",
    azure_deployment="",
    api_version="2024-02-01",
)

completion = client.chat.completions.create(
    model=deployment,
    messages=messages,
    extra_body={
        "data_sources":[
            {
                "type": "azure_search",
                "parameters": {
                    "endpoint": os.environ["AZURE_AI_SEARCH_ENDPOINT"],
                    "index_name": os.environ["AZURE_AI_SEARCH_INDEX"],
                    "authentication": {
                        "type": "api_key",
                        "key": os.environ["AZURE_AI_SEARCH_API_KEY"],
                    }
                }
            }
        ],
    }
)


[Idea] write bad events

Bad events (error when processing), should be detected and written to an specific "table"

Fields:

Timestamp,
event a
error cause / stacktrace


Beautify the connection between nodes

In many node editor, the connections between nodes are mostly curves rather than straight lines
Visually, this can achieve better results. Can you consider using Bezier curves, etc. instead of the current straight line connection?
There are some examples:

Github workflow preview:

Bolt editor for Unity3D:

Node editor for Blender:

hi @mnixry, I see Vue is in your skills list. The line is defined here: https://github.com/remcoplasmeyer/flowy-vue/blob/master/src/components/FlowyNode.vue#L218
I'll gladly review a PR.


Images are cached twice by AFImageCache and NSURLCache.

Feel free to close this ticket. I was incorrect.
Thanks.

This is by design. AFImageCache is a in memory cache to aid in performance for scrolling views.


feat: add OpenTofu formatter

Adds tofu_fmt from OpenTofu. An alternative to terraform_fmt for those that have switched away from Terraform.

Thanks for the PR!


Delay getting correct leaf indices in nearest

Some indices may be in the heap only temporary, and not stay till the end. For those indices, there is no point in getting the correct leaf indices.

This does not currently show any difference in the performance. Still think it is a good thing to do.

All builds but HIP pass. HIP build was not started due to timeout (long queue). Good enough.


Scroll bar offset does not match cursor offset on Flutter Web

When dragging the scroll bar thumb on Flutter Web while the cursor is already moving, the scrollbar thumb offset won't match the expected offset.
Example code:
import 'package:flexible_scrollbar/flexible_scrollbar.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(App());
}

class App extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      debugShowCheckedModeBanner: false,
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: HomeScreen(),
    );
  }
}

class HomeScreen extends StatefulWidget {
  @override
  _HomeScreenState createState() => _HomeScreenState();
}

class _HomeScreenState extends State<HomeScreen> {
  final _scrollController = ScrollController();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: FlexibleScrollbar(
        controller: _scrollController,
        alwaysVisible: true,
        scrollThumbBuilder: (ScrollbarInfo info) {
          return Container(
            width: 50,
            height: info.thumbMainAxisSize,
            decoration: BoxDecoration(color: Colors.black),
          );
        },
        child: ListView(
          controller: _scrollController,
          children: List.generate(
            30,
            (index) {
              return ListTile(title: Text(index.toStringAsFixed(0)));
            },
          ),
        ),
      ),
    );
  }
}

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.1, on Microsoft Windows [Version    10.0.19045.4412], locale en-US)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Chrome - develop for the web
[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.4.3)
[✓] Android Studio (version 2020.3)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

flexible_scrollbar 0.1.3

https://github.com/ReliableCauliflower/flexible_scrollbar/assets/58010418/05c9e378-388a-4708-abdc-8f263a0d286e

From what I've been testing, adding
onPanDown: (details) {
  onScrollLineTapDown(
    TapDownDetails(
      globalPosition: details.globalPosition,
      localPosition: details.localPosition,
    ),
  );
},

to the GestureDetector seems to fix it.


Bug report: Function elink(url, [display]) is not working in  table view

What happened?
I tried to reproduce the simple example of elink() in the documentation, but could not get it to work.
The image "www.google.com" does not respond when clicked.

DQL
table elink("www.google.com") as Google from #test

JS
No response
Dataview Version
0.5.47
Obsidian Version
1.1.9
OS
MacOS

Hello,
sorry, I do not understand your bug report. Which image? You did not specify any image in your DQL. What is your expected behaviour?
Should your link do not show www.google.com but the text Google? You then need to specify it as the second argument of the function, just like in the docs: elink("www.google.com", "Google")

Thank you for your reply.
I am expecting "www.google.com" to work as a link.
When I click on it, nothing happens.
I changed the DQL as follows and still the same situation.
table elink("https://www.google.com") from #test

Hello again,
thanks alot for the clarification! I now can reproduce your problem. The documentation is falsy here. It needs to be prefixed with a http:// or https:// to work - the elink function only converts the element to a clickable link element (an a tag) and doesn't verify that it is an valid, callable URL. The example certainly needs to be reworked here. In fact if you do
table "www.google.com" as "Just Text", elink("https://www.google.com") as "elink" from #test

the "Just Text" variant works as expected.
I am suprised that your second example doesn't work for you, though. This works for me just fine.
I'll tag the issue as a documentation issue to clarify the effect and usage of elink and choose better examples.

I just tried again and my second example works as a link.
I have confirmed that your example works in my environment as well.
Thanks for solving my question!


JIB to.auth.password should be a Property, not a plain String

When JIB 2.7.0 gets released with to.auth.password a Property, clean the code that configures JIB.

Done: JIB 2.7.0 released, code cleaned up.


Can't install

root@retracker:~# go install 'github.com/vvampirius/retracker@latest'
# github.com/vvampirius/retracker
go/pkg/mod/github.com/vvampirius/retracker@v0.0.0-20240416120713-0b932dd2ecb3/receiverAnnounce.go:149:13: forward.Host undefined (type "github.com/vvampirius/retracker/common".Forward has no field or method Host)
go/pkg/mod/github.com/vvampirius/retracker@v0.0.0-20240416120713-0b932dd2ecb3/receiverAnnounce.go:150:23: forward.Host undefined (type "github.com/vvampirius/retracker/common".Forward has no field or method Host)

Try again please. It seems fixed.
% go install 'github.com/vvampirius/retracker@latest' go: downloading github.com/vvampirius/retracker v0.0.0-20241108170741-19ca869ddff5 go: downloading github.com/prometheus/client_golang v1.20.5 go: downloading gopkg.in/yaml.v2 v2.4.0 go: downloading github.com/vvampirius/retracker/bittorrent/tracker v0.0.0-20241018131108-6661250eb98b go: downloading github.com/vvampirius/retracker/common v0.0.0-20241018131108-6661250eb98b go: downloading github.com/vvampirius/retracker/bittorrent/common v0.0.0-20241018131108-6661250eb98b go: downloading github.com/vvampirius/retracker/bittorrent/response v0.0.0-20241018131108-6661250eb98b go: downloading github.com/zeebo/bencode v1.0.0 go: downloading github.com/prometheus/common v0.60.1 go: downloading github.com/klauspost/compress v1.17.11 go: downloading github.com/prometheus/client_model v0.6.1 go: downloading google.golang.org/protobuf v1.35.1 go: downloading github.com/cespare/xxhash/v2 v2.3.0 go: downloading github.com/prometheus/procfs v0.15.1 go: downloading github.com/beorn7/perks v1.0.1 go: downloading github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 go: downloading golang.org/x/sys v0.27.0


Handle qpy serialization across versions

Summary
Cherry picked from https://github.com/Qiskit/qiskit-ibm-runtime/pull/1377, credit to @mtreinish
We can remove the vendored version of QPY in this repo after a deprecation period
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-4 of 8 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall first build on qiskit-qpy-1.0 at 43.088%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/utils/json.py
4
8
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
43.1%

Covered Lines:
2902

Relevant Lines:
6735

💛  - Coveralls


[Bug Report][0.7.3]: Failure of build product compilation css

Steps to reproduce
example/react
// step 1
pnpm build

// step 2
pnpm preview

What is expected?
normal
What is actually happening?
Normal situation
pnpm start

Error situation
pnpm build

pnpm preview

System Info
windows 11

Any additional comments?
No response

This is caused by the wrong order of the css resource. It should be topo order but it's not for now. It's a bit complex, I will fix it later


Add --ie32 commandline option to webdriver_manager

Fixes #1297
The new option allows to download the 32-bit version of the IE driver on
a 64-bit system, as the 64-bit version has been broken for over a year
now (the sendKeys() function works very slowly on it).

CLA has been signed in the meantime

Commit author has been updated to match the CLA

@rogierschouten Have you tested it? I can't test it right now since I don't have a windows machine, but the code looks good. As soon as you can confirm that you tested it, and sign the CLA again, I'll pull it in.

I plan to test it at work next Monday, I can't do so now either. I'll let you know, thank you

Tested & working!

Thanks! Merged: https://github.com/angular/protractor/commit/c989a7eeed5a0a55d2fbd37dc7278a7967889852


xk6 failing to build due to missing 3rd party dependencies

I dont know if you manage these in grafana or k6, but this is happening since yesterday
❯ ./xk6 build
2022/09/28 09:39:40 [INFO] Temporary folder: /tmp/buildenv_2022-09-28-0939.48910491
2022/09/28 09:39:40 [INFO] Initializing Go module
2022/09/28 09:39:40 [INFO] exec (timeout=10s): /usr/bin/go mod init k6
go: creating new go.mod: module k6
2022/09/28 09:39:40 [INFO] Pinning versions
2022/09/28 09:39:40 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
go: warning: "all" matched no packages
2022/09/28 09:39:40 [INFO] Writing main module: /tmp/buildenv_2022-09-28-0939.48910491/main.go
2022/09/28 09:39:40 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
go: finding module for package go.k6.io/k6/cmd
go: found go.k6.io/k6/cmd in go.k6.io/k6 v0.40.0
go: finding module for package github.com/spf13/afero
go: finding module for package github.com/mailru/easyjson
go: finding module for package github.com/Soontao/goHttpDigestClient
go: finding module for package github.com/spf13/pflag
go: finding module for package github.com/davecgh/go-spew/spew
go: finding module for package github.com/oxtoacart/bpool
go: finding module for package github.com/go-sourcemap/sourcemap
go: finding module for package github.com/mailru/easyjson/jlexer
go: finding module for package gopkg.in/guregu/null.v3
go: finding module for package github.com/mailru/easyjson/jwriter
go: found github.com/spf13/afero in github.com/spf13/afero v1.9.2
go: found gopkg.in/guregu/null.v3 in gopkg.in/guregu/null.v3 v3.5.0
go: finding module for package github.com/spf13/pflag
go: finding module for package github.com/mailru/easyjson/jwriter
go: finding module for package github.com/mailru/easyjson/jlexer
go: finding module for package github.com/davecgh/go-spew/spew
go: finding module for package github.com/mailru/easyjson
go: finding module for package github.com/go-sourcemap/sourcemap
go: finding module for package github.com/oxtoacart/bpool
go: finding module for package github.com/Soontao/goHttpDigestClient
k6 imports
        go.k6.io/k6/cmd imports
        github.com/spf13/pflag: module github.com/spf13/pflag@latest found (v1.0.5), but does not contain package github.com/spf13/pflag
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/cloudapi imports
        github.com/mailru/easyjson: module github.com/mailru/easyjson@latest found (v0.7.7), but does not contain package github.com/mailru/easyjson
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/cloudapi imports
        github.com/mailru/easyjson/jlexer: module github.com/mailru/easyjson@latest found (v0.7.7), but does not contain package github.com/mailru/easyjson/jlexer
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/cloudapi imports
        github.com/mailru/easyjson/jwriter: module github.com/mailru/easyjson@latest found (v0.7.7), but does not contain package github.com/mailru/easyjson/jwriter
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/js imports
        github.com/oxtoacart/bpool: module github.com/oxtoacart/bpool@latest found (v0.0.0-20190530202638-03653db5a59c), but does not contain package github.com/oxtoacart/bpool
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/js imports
        go.k6.io/k6/js/compiler imports
        github.com/go-sourcemap/sourcemap: package github.com/go-sourcemap/sourcemap provided by github.com/go-sourcemap/sourcemap at latest version v2.1.3+incompatible but not at required version v2.1.4-0.20211119122758-180fcef48034+incompatible
k6 imports
        go.k6.io/k6/cmd imports
        go.k6.io/k6/output/cloud imports
        go.k6.io/k6/lib/netext/httpext imports
        github.com/Soontao/goHttpDigestClient: module github.com/Soontao/goHttpDigestClient@latest found (v0.0.0-20170320082612-6d28bb1415c5), but does not contain package github.com/Soontao/goHttpDigestClient
k6 imports
        go.k6.io/k6/cmd tested by
        go.k6.io/k6/cmd.test imports
        github.com/stretchr/testify/assert imports
        github.com/davecgh/go-spew/spew: module github.com/davecgh/go-spew@latest found (v1.1.1), but does not contain package github.com/davecgh/go-spew/spew
2022/09/28 09:39:42 [INFO] Cleaning up temporary folder: /tmp/buildenv_2022-09-28-0939.48910491
2022/09/28 09:39:42 [FATAL] exit status 1

Hi, thanks for reporting :bow:
This seems like something is wrong with your machine resolving the dependencies. I definitely can't reproduce it. Both with go1.18.6  and 1.19.1
Can you provide go env output? And maybe if you can think of anything that has changed since yesterday?
Also, xk6 build does not build in the local extension it just builds k6 which is likely not what you want :thinking: ?

Can you try to run go mod -cleancache ?

Note that support for modules is built into all the go commands,
not just 'go mod'. For example, day-to-day adding, removing, upgrading,
and downgrading of dependencies should be done using 'go get'.
See 'go help modules' for an overview of module functionality.

Usage:

        go mod <command> [arguments]

The commands are:

        download    download modules to local cache
        edit        edit go.mod from tools or scripts
        graph       print module requirement graph
        init        initialize new module in current directory
        tidy        add missing and remove unused modules
        vendor      make vendored copy of dependencies
        verify      verify dependencies have expected content
        why         explain why packages or modules are needed

Use "go help mod <command>" for more information about a command.

So I removed all caches and started from 0:
❯ sudo rm go -fr
❯ go install go.k6.io/xk6/cmd/xk6@latest
go: downloading go.k6.io/xk6 v0.7.0
go: downloading github.com/Masterminds/semver/v3 v3.1.1
❯ cd go/bin
❯ l
total 4.3M
drwxr-xr-x 2 agilob users 4.0K Sep 28 10:56 .
drwxr-xr-x 4 agilob users 4.0K Sep 28 10:56 ..
-rwxr-xr-x 1 agilob users 4.3M Sep 28 10:56 xk6
❯ ./xk6 build v0.40.0 --with github.com/tmieulet/xk6-cognito
2022/09/28 10:56:18 [INFO] Temporary folder: /tmp/buildenv_2022-09-28-1056.697840031
2022/09/28 10:56:18 [INFO] Initializing Go module
2022/09/28 10:56:18 [INFO] exec (timeout=10s): /usr/bin/go mod init k6
go: creating new go.mod: module k6
2022/09/28 10:56:18 [INFO] Pinning versions
2022/09/28 10:56:18 [INFO] exec (timeout=0s): /usr/bin/go mod edit -require github.com/tmieulet/xk6-cognito@latest
2022/09/28 10:56:18 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
go: downloading github.com/tmieulet/xk6-cognito v0.0.1
go: finding module for package go.k6.io/k6/js/modules
go: finding module for package github.com/aws/aws-sdk-go-v2/aws
go: finding module for package github.com/alexrudd/cognito-srp/v4
go: finding module for package github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider
go: finding module for package github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider/types
go: finding module for package github.com/aws/aws-sdk-go-v2/config
go: downloading github.com/alexrudd/cognito-srp v0.0.0-20190402174326-7bb6280c912c
go: downloading go.k6.io/k6 v0.40.0
go: downloading github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider v1.20.1
go: downloading github.com/aws/aws-sdk-go-v2/config v1.17.7
go: downloading github.com/alexrudd/cognito-srp/v4 v4.1.0
go: downloading github.com/aws/aws-sdk-go-v2 v1.16.16
go: found github.com/alexrudd/cognito-srp/v4 in github.com/alexrudd/cognito-srp/v4 v4.1.0
go: found github.com/aws/aws-sdk-go-v2/aws in github.com/aws/aws-sdk-go-v2 v1.16.16
go: found github.com/aws/aws-sdk-go-v2/config in github.com/aws/aws-sdk-go-v2/config v1.17.7
go: found github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider in github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider v1.20.1
go: found github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider/types in github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider v1.20.1
go: found go.k6.io/k6/js/modules in go.k6.io/k6 v0.40.0
go: downloading github.com/dop251/goja v0.0.0-20220815083517-0c74f9139fd6
go: downloading github.com/aws/smithy-go v1.13.3
go: downloading github.com/aws/aws-sdk-go-v2/credentials v1.12.20
go: downloading github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.12.17
go: downloading github.com/aws/aws-sdk-go-v2/internal/ini v1.3.24
go: downloading github.com/aws/aws-sdk-go-v2/service/sso v1.11.23
go: downloading github.com/aws/aws-sdk-go-v2/service/ssooidc v1.13.5
go: downloading github.com/aws/aws-sdk-go-v2/service/sts v1.16.19
go: downloading github.com/aws/aws-sdk-go-v2/internal/configsources v1.1.23
go: downloading github.com/google/go-cmp v0.5.8
go: downloading github.com/serenize/snaker v0.0.0-20201027110005-a7ad2135616e
go: downloading github.com/sirupsen/logrus v1.8.1
go: downloading github.com/stretchr/testify v1.8.0
go: downloading github.com/spf13/afero v1.1.2
go: downloading github.com/oxtoacart/bpool v0.0.0-20190530202638-03653db5a59c
go: downloading golang.org/x/time v0.0.0-20220609170525-579cf78fd858
go: downloading gopkg.in/guregu/null.v3 v3.3.0
go: downloading github.com/mstoykov/envconfig v1.4.1-0.20220114105314-765c6d8c76f1
go: downloading github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.4.17
go: downloading github.com/mailru/easyjson v0.7.7
go: downloading github.com/fatih/color v1.13.0
go: downloading github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.9.17
go: downloading github.com/dlclark/regexp2 v1.7.0
go: downloading golang.org/x/text v0.3.7
go: downloading gopkg.in/yaml.v2 v2.2.8
go: downloading github.com/andybalholm/brotli v1.0.4
go: downloading github.com/gorilla/websocket v1.5.0
go: downloading github.com/klauspost/compress v1.15.7
go: downloading github.com/mccutchen/go-httpbin v1.1.2-0.20190116014521-c5cb2f4802fa
go: downloading golang.org/x/net v0.0.0-20220630215102-69896b714898
go: downloading google.golang.org/grpc v1.47.0
go: downloading github.com/go-sourcemap/sourcemap v2.1.4-0.20211119122758-180fcef48034+incompatible
go: downloading github.com/davecgh/go-spew v1.1.1
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading gopkg.in/yaml.v3 v3.0.1
go: downloading golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a
go: downloading github.com/mattn/go-colorable v0.1.12
go: downloading github.com/mattn/go-isatty v0.0.14
go: downloading golang.org/x/crypto v0.0.0-20220622213112-05595931fe9d
go: downloading google.golang.org/protobuf v1.27.1
go: downloading google.golang.org/genproto v0.0.0-20210604141403-392c879c8b08
go: downloading github.com/golang/protobuf v1.5.2
go: downloading gopkg.in/yaml.v2 v2.4.0
go: finding module for package gopkg.in/guregu/null.v3
go: finding module for package github.com/onsi/ginkgo
go: finding module for package github.com/spf13/afero
go: finding module for package github.com/davecgh/go-spew/spew
go: finding module for package github.com/oxtoacart/bpool
go: finding module for package github.com/go-sourcemap/sourcemap
go: finding module for package github.com/mailru/easyjson/jwriter
go: finding module for package github.com/onsi/gomega
go: downloading github.com/onsi/ginkgo v1.16.5
go: downloading github.com/onsi/gomega v1.20.2
go: downloading gopkg.in/guregu/null.v3 v3.5.0
go: downloading github.com/spf13/afero v1.9.2
go: downloading github.com/go-sourcemap/sourcemap v2.1.3+incompatible
go: found github.com/spf13/afero in github.com/spf13/afero v1.9.2
go: found gopkg.in/guregu/null.v3 in gopkg.in/guregu/null.v3 v3.5.0
go: found github.com/onsi/ginkgo in github.com/onsi/ginkgo v1.16.5
go: found github.com/onsi/gomega in github.com/onsi/gomega v1.20.2
go: downloading golang.org/x/sys v0.0.0-20220722155257-8c9f86f7a55f
go: downloading github.com/nxadm/tail v1.4.8
go: downloading golang.org/x/net v0.0.0-20220722155237-a158d28d115b
go: downloading google.golang.org/protobuf v1.28.0
go: downloading gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7
go: downloading github.com/fsnotify/fsnotify v1.4.9
go: finding module for package github.com/davecgh/go-spew/spew
go: finding module for package github.com/mailru/easyjson/jwriter
go: finding module for package github.com/oxtoacart/bpool
go: finding module for package github.com/go-sourcemap/sourcemap
k6 imports
        github.com/tmieulet/xk6-cognito imports
        go.k6.io/k6/js/modules imports
        go.k6.io/k6/lib imports
        github.com/oxtoacart/bpool: module github.com/oxtoacart/bpool@latest found (v0.0.0-20190530202638-03653db5a59c), but does not contain package github.com/oxtoacart/bpool
k6 imports
        github.com/tmieulet/xk6-cognito imports
        go.k6.io/k6/js/modules imports
        github.com/dop251/goja imports
        github.com/dop251/goja/file imports
        github.com/go-sourcemap/sourcemap: package github.com/go-sourcemap/sourcemap provided by github.com/go-sourcemap/sourcemap at latest version v2.1.3+incompatible but not at required version v2.1.4-0.20211119122758-180fcef48034+incompatible
k6 imports
        github.com/tmieulet/xk6-cognito imports
        go.k6.io/k6/js/modules imports
        go.k6.io/k6/js/common imports
        go.k6.io/k6/metrics imports
        github.com/mailru/easyjson/jwriter: module github.com/mailru/easyjson@latest found (v0.7.7), but does not contain package github.com/mailru/easyjson/jwriter
k6 imports
        github.com/tmieulet/xk6-cognito imports
        go.k6.io/k6/js/modules imports
        go.k6.io/k6/js/common tested by
        go.k6.io/k6/js/common.test imports
        github.com/stretchr/testify/assert imports
        github.com/davecgh/go-spew/spew: module github.com/davecgh/go-spew@latest found (v1.1.1), but does not contain package github.com/davecgh/go-spew/spew
2022/09/28 10:57:47 [INFO] Cleaning up temporary folder: /tmp/buildenv_2022-09-28-1056.697840031
2022/09/28 10:57:47 [FATAL] exit status 1

:facepalm: I did write the commadn by hand and it  was go clean -modcache not how I slapped the words :facepalm:
I have now spend probably over 2 hours,  trying to reproduce this. Including on arch (I guess you are on it based on other threads) and I can not reproduce it this at all. I tried older version of xk6, different go versions - nothing.
I can tell you that the
go: finding module for package github.com/davecgh/go-spew/spew
go: finding module for package github.com/mailru/easyjson/jwriter
go: finding module for package github.com/oxtoacart/bpool
go: finding module for package github.com/go-sourcemap/sourcemap

Is at all not present in any of the outputs I had - the rest (up to that point) look similar apart from some lines being swapped - likely to go doing downloads in parallel.
Given that I have no way to reproduce it and that I have no other questions to try to tease this out I will have to wait for more info on how to reproduce it before I proceed.
Again this looks like some kind of go cache corruption, But what you did should've fixed that.
I guess you can try to git clone the extension and do go build . to see if that works :shrug:

I compiled it fine on mac :eyes: Has to be something local then. I'm closing this and will update if I fix it

Magically working today...
❯ ./xk6 build v0.40.0
2022/10/07 16:10:54 [INFO] Temporary folder: /tmp/buildenv_2022-10-07-1610.1139569771
2022/10/07 16:10:54 [INFO] Initializing Go module
2022/10/07 16:10:54 [INFO] exec (timeout=10s): /usr/bin/go mod init k6
go: creating new go.mod: module k6
2022/10/07 16:10:54 [INFO] Pinning versions
2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
go: warning: "all" matched no packages
2022/10/07 16:10:54 [INFO] Writing main module: /tmp/buildenv_2022-10-07-1610.1139569771/main.go
2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go mod edit -require<EMAIL_ADDRESS>2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
2022/10/07 16:10:54 [INFO] Build environment ready
2022/10/07 16:10:54 [INFO] Building k6
2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go mod tidy -compat=1.17
2022/10/07 16:10:54 [INFO] exec (timeout=0s): /usr/bin/go build -o /home/agilob/go/bin/k6 -ldflags -w -s -trimpath
2022/10/07 16:11:07 [INFO] Build complete: ./k6
2022/10/07 16:11:07 [INFO] Cleaning up temporary folder: /tmp/buildenv_2022-10-07-1610.1139569771

xk6 has now produced a new k6 binary which may be different than the command on your system path!
Be sure to run './k6 run <SCRIPT_NAME>' from the '/home/agilob/go/bin' directory.


Fix tiny typo in asserts/index.md

expectedEror → expectedError

Hm… ping @isaacs ? :smile:

thanks! pushed.


Daniel Widdis: Watch milf

Daniel Widdis requests the watch of the watch_keyword milf. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

milf has been seen in 6 true positives, 3 false positives, and 0 NAAs.

Approved by NobodyNada in Charcoal HQ


Avoid deadlock on data bigger than buffer by chunking

A deadlock occurs when the data to send is bigger than the available buffer. Chunking data removes this deadlock.

For tracking this is an alternative to https://github.com/ethereum/utp/pull/61

https://github.com/ethereum/utp/pull/65#discussion_r1208613588
This is why I made the PR for this solution https://github.com/ethereum/utp/pull/61 . Cause fixing the problem at a deeper level requires a refactor, unless you increase complexity. Which I guess is fine temporary.
The refactor would be something like combining pending_writes and send_buf into one, since having them both is quite redundant since we already have an outgoing buffer which is sent_packets.packets packets should be renamed to outgoing_buffer to better represent the reference implementations

If we choose your temporary solution over mine, you should add a TODO to this PR of.
// todo: combine pending_writes and send_buf, rename sent_packets.packets to sent_packets.outgoing_buffer


Revert "Automated Contour version update 1.14.0"

Reverts replicatedhq/kURL#1406

Closing. Tested an install and upgrade and seems to work fine.


As a logged-in user, I want to click on my profile to see and potentially edit my personal information to keep it up to date.

Acceptance Criteria:

[x] By clicking on my username, I can view all my information like username, password, points, email
[x] By clicking on an edit button within my user-profile, I want to be able to change my password and username
[x] After changing and saving the data, the new/changed data is displayed

Dev Tasks:

[x] sopra-fs23-group-10/sopra-fs23-group-10-client#29
[x] sopra-fs23-group-10/sopra-fs23-group-10-server#80

All dev tasks are completed and acceptance criterias are met. Issue is therefore closed.


[5.5] Let config get many keys at once.

Let config get many keys at once so that $values = Config::getMany(['foo', 'bar.baz']); is now possible.
A default value can also be set for each items to retrieve:
$values = Config::getMany(['foo' => 'default_value', 'bar.baz' => 123]);

If Config::get is called with $key as an array, Config::getMany will be used.

I don't understand why x.y returns an array, why does it not just return the y value like it would when using Config::get('x.y.')

You're totally right @taylorotwell , updated in https://github.com/laravel/framework/pull/19770/commits/f4f6a70840aafe1f580c40419926007882a6feba


Unfortunatly right now bots requires some files only respawn have,
as referenced in #3 pepole are working on seeing how thoses files are made for singleplayer and potentially making them for multiplayer. But that's gonna take time

alright, let me know how it goes.

I'll close this issue now since we don't have to files to make AI work and can't generate them unless we understand the format. Refer to issue #3 for updates


Error running the command

flick video -a start -p android
/usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/system.rb:7:in mkdir': No such file or directory @ dir_s_mkdir - /Users/saikrisv/.flick/<IP_ADDRESS>:5555 (Errno::ENOENT)        	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/system.rb:7:in setup_system_dir'
from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/android.rb:23:in create_flick_dirs'        	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/android.rb:15:in initialize'
from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/video.rb:15:in new'        	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/lib/flick/video.rb:15:in initialize'
from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/bin/flick:32:in new'        	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.2.3/bin/flick:32:in block (2 levels) in <top (required)>'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in call'        	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in run'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in run_active_command'        	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:68:in run!'
from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in run!'        	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/import.rb:5:in block in <top (required)>'

Hmm, I've pulled that version of the gem. Can you do a "gem install flick" and try again? You should get version 3.0 now. Thank you for reporting the problem.

@saikrishna321 did 0.3.0 fix this problem? I'm unable to reproduce the issue now.

@isonic1 i still the have issue with v 3.0.0
flick video -a start -p android -u 32085b6d8fdb71ff --trace
/usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/system.rb:7:in `mkdir': No such file or directory @ dir_s_mkdir - /Users/saikrisv/.flick/32085b6d8fdb71ff (Errno::ENOENT)
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/system.rb:7:in `setup_system_dir'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/android.rb:27:in `create_flick_dirs'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/android.rb:19:in `initialize'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/video.rb:15:in `new'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/lib/flick/video.rb:15:in `initialize'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/bin/flick:32:in `new'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.0/bin/flick:32:in `block (2 levels) in <top (required)>'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:68:in `run!'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/import.rb:5:in `block in <top (required)>'

Doh! I see the problem. Sorry about that. I'll fix it soon. Thank you @saikrishna321 for letting me know.

@isonic1 most welcome :) waiting for the fix. I basically want to use this plugin in my parallel appium framework. Please take a look
https://github.com/saikrishna321/AppiumTestDistribution

@saikrishna321 it's fixed now. I just pushed 0.3.1 and yanked 0.3.0. Please do a "gem update flick" to get the latest. I'm pretty sure it will work now. Thanks again! :)
Your Appium Test Distribution looks awesome! I'll definitely pass it on as reference for others wanting to do the same in java!

@isonic1 it started the recording, but stopping the recording i see MP4BOX stop unexpectedly,
~ ᐅ flick video -a start -p android -u 32085b6d8fdb71ff --trace
zsh: correct 'android' to '.android' [nyae]? n
Starting Recorder In Normal Mode.
Recorder will automatically stop after 180 seconds...
~ ᐅ flick video -a stop -p android -u 32085b6d8fdb71ff --trace
zsh: correct 'android' to '.android' [nyae]? n

Stopping Recorder!!!
[iso file] Incomplete box mdat
[iso file] Incomplete MDAT while file is not read-only
No suitable media tracks to cat in /Users/saikrisv/.flick/32085b6d8fdb71ff/video-single.mp4 - skipping
Saving to /Users/saikrisv/32085b6d8fdb71ff.mp4
/usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.1/lib/flick/video.rb:107:in `rename': No such file or directory @ rb_file_s_rename - (/Users/saikrisv/.flick/32085b6d8fdb71ff/32085b6d8fdb71ff.mp4, /Users/saikrisv/32085b6d8fdb71ff.mp4) (Errno::ENOENT)
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.1/lib/flick/video.rb:107:in `stop_record'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.1/lib/flick/video.rb:49:in `stop'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.1/lib/flick/video.rb:25:in `run'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/flick-0.3.1/bin/flick:32:in `block (2 levels) in <top (required)>'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:68:in `run!'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
       	from /usr/local/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/import.rb:5:in `block in <top (required)>'

@saikrishna321 hmm, that seems like a mp4box error. Did you install using homebrew? I would uninstall it and reinstall. Maybe also update brew if you didn't do that already.

@isonic1 yah i did install it by brew .. will give it a try again .. Is there any other medium i can chat on this? gitter , skype, slack or gtalk ?

@isonic1 got it working :) thanks a lot 👍 how can i extend the time from 180 seconds ?

sweet! Yeah, you can extend it by passing -e true in the start action. e.g. flick video -p android -a start -e true . Thank you again for reporting this. Proves how helpful tests can be, which I need to update them. :)

@isonic1 thanks for building flick 👍  very helpful


Add a .where class method

This implements a .where method for retrieving an array of static records. The
method accepts an array of ids and returns an array of records. Unlike the
.find record, if a record does not exist for a given id, an error is not
raised.

Closing in favour #16


Change font size?

Great project, thanks for your efforts. Does anyone know if it's possible to increase/decrease the font size?

Hi Samuel.
Check my issue: https://github.com/NielsLeenheer/EscPosEncoder/issues/46#issue-899084125.
There y show the raw() function commands you should use to increase the font size, but i dont know how to increase it in width and height at the same time.
Tell me if you know how! good luck

@SamuelMichelRiad  and @paluchi The only way I've found is to increase font size is:
.raw([[0x1b, 0x21, 0x10]])   // Double both height .raw([[0x1b, 0x21, 0x20]])   // Double both width .raw([[0x1b, 0x21, 0x30]])   // Double both height and width

@Kamaulan thx  you so much!
can i ask you how did you notice that [0x1b, 0x21, 0x30] would work?  whats 0x30 reffers to?

@SamuelMichelRiad and @paluchi The only way I've found is to increase font size is:
.raw([[0x1b, 0x21, 0x10]]) // Double both height
.raw([[0x1b, 0x21, 0x20]]) // Double both width
.raw([[0x1b, 0x21, 0x30]]) // Double both height and width

thx  you so much!
can i ask you how did you notice that [0x1b, 0x21, 0x30] would work?  whats 0x30 reffers to?

@KamauIan
thx you so much!
can i ask you how did you notice that [0x1b, 0x21, 0x30] would work? whats 0x30 reffers to?

@paluchi checkout these resources for more :
https://github.com/escpos/escpos/blob/master/lib/escpos.rb
https://escpos.readthedocs.io/en/latest/font_cmds.html#select-print-mode-1b-21-rel-phx

The upcoming 2.0 version of EscPosEncoder will support changing the width and height of the text:
encoder
   .width(3)
   .height(3)
   .text('This text is three times as large as normal')

@NielsLeenheer is there any size between hight(1). And hight(2) because hight (2) is little large.. please let me know is there any alternative solutions thanks


Log rotation only rotates gogs.log

Gogs version (or commit ref): <IP_ADDRESS>5
Git version: 2.9.2
Operating system: FreeBSD
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
Opening issue at the request of @Unknwon
With the following settings for log rotation only gogs.log gets rotated:
[log.file]
LOG_ROTATE      = true
DAILY_ROTATE    = true
MAX_DAYS        = 25

The http.log, update.log and xorm.log do not get rotated. This is problematic for me because we have a policy on log retention that I need to follow. What is the appropriate work around for this issue and/or can it be fixed relatively easy and soon?

Note: because rotate requires app running long enough, but processes to write other log files usually lives only for few seconds.

@Unknwon: I'm not sure if this is an appropriate place to put this but this is my opinion on how log rotation should work. Let me know your thoughts.
Logs should rotate on only one of either a daily basis, number of lines basis, or size basis. I don't believe they should rotate on multiple factors. For daily log rotation ALL Gogs logs should rotate at midnight. Ideally there would also be the option to compress rotated logs. And to take it a step further sometimes there is the option for a delayed compression of logs (meaning the previous log stays uncompressed until the next rotation).

@vroomanj yes, I think you're right, the currently log implementation is crap..

xorm.log is now the only file won't rotate.

For xorm.log, please follow https://github.com/gogits/gogs/issues/3183.


running with crash_safe=true is much slower

Mark reasons for process isolation

PyTorch JIT leak => OOM; https://github.com/pytorch/pytorch/issues/86537
Better oracle: crash & timeout;

crash_safe=True is now compatible with:

onnx-tvm
onnx-ort
onnx-trt
tflite

imcompatible with:

xla: reinitialization of cuda context; https://github.com/tensorflow/tensorflow/issues/57877
pytorch-jit (experimental): performance and randomized haulting;

required by:

pytorch-jit: to route the leak => OOM issue;

Now investigating pytorch compatibility.


Doc: tcpinfo plugin table formatting

Prechange, the rst table showed as unformatted "==="s
and run on sentences.

Cherry-picked to v9.0.x branch.
Cherry-picked to v9.1.x branch.


v2 tutorials?

Hello!
Thanks for your great material and tutorials.
Now that v1 seems EOL, and I heard about the "feature freeze" of the v2 version ... where can I find a list of all those tutorials & manuals that target v2 ?
E.g. this excellent workshop is still based on -b v1.0 https://substrate.dev/docs/en/tutorials/start-a-private-network-with-substrate#your-first-time
Secondly, for very basic experiments, would you recommend to I use this "Current Stable Version" Jan 6 pre-v2.0-3e65111  ?
Thank you very much!

P.S.: How about a flag on the top of every page of every manual - which signals for which version that page is suitable? Perhaps even until which future version it might be useful, i.e. "expiration date".

The private network tutorial you linked above has been updated. Here is the new version which works with pre-v2.0-3e65111 https://substrate.dev/docs/en/tutorials/start-a-private-network/
And yes, currently we are recommending building on 3e65111 for experimentation. That is the version that is currently best documented.
I'm sorry you've struggled with the versioning. It has been tough for us writing the docs too. The good news is that that will change soon as we are just starting to publish Substrate on crates.io and soon v2.0 proper will be out.
Please continue to reach out with questions and we will do our best to help.

Perfect. This time, I just asked before, to minimized the trouble. So ... all good.
Thanks a lot.  Have a great weekend.


Still able to view cached pages after logging out

I'm using barba with Wordpress. I'm having an issue where I log out of WP, but I can hit the back button and still see pages in cache.
My first thought was to reset Barba.BaseCache.data, but that neither Barba.BaseCache nor Barba.BaseCache.data seem to exist, despite what the documentation says.
Another thought was to set Barba.HistoryManager.history = [] but that doesn't do the trick either.
How can clear cache so I can disallow users from viewing pages through use of back button, after logging out of an application like WordPress?

Hello @PhillyWebGuy ,
Usually I disable barba.js navigation when logged as admin (so it doesn't interfere with wp admin bar).
Yes, actually Barba.BaseCache is not exposed, the jsdoc annotation is wrong and therefore the doc. (i'll fix it in the v2)
You can access the cache via Barba.Pjax.Cache.

Ok, I'll set Barba.Pjax.Cache = [] on logout and see what happens...

There is a reset method:
Barba.Pjax.Cache.reset()

Nothing actually appears in that array. And if I do reset() I am still unable to use the back button to navigate to pages.

I am still unable to use the back button to navigate to pages.

Hello @PhillyWebGuy , isn't that what you wanted?
To not allow people to see pages in the cache after the logged out.
Can you explain a bit better?

That was a type. The problem is that I reset() but I am still have to use back button. The data still seems to be cached. Not only that, it doesn't appear to be there in the first place when inspecting, so I can't verify it is gone, aside from the fact that I can still use back button.

@PhillyWebGuy the browser will always shows the back button, barba.js can't disallow that.
If you reset the cache, barba.js will just force a new xhr request for a page, that's it.
Hope it makes sense


Update imports of React headers for react-native 0.40 breaking change

React-Native 0.40 introduces a breaking change and imports now require the "React/" namespace (https://github.com/facebook/react-native/releases/tag/v0.40.0).
Per the suggestion in the commit where this change was made: https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d , this PR updates imports with the "React/" namespace and updates the header include path to use $(BUILT_PRODUCTS_DIR)/usr/local/include.
For my initial build following this change, I had to follow the instructions in the linked commit to add React as an explicit dependency in the scheme and disable "parallelize build". After the initial build I was able to remove the React dependency and rebuild without error.

Hello,
When will this be upgraded?
Thx !

@oney we need this PR merge soon as the latest version is breaking under current format.

This would also force everyone to upgrade RN 40 if they use this module but couldn't upgrade to RN 40 anytime soon.
If anyone has an idea that helps this process smooth, let me know.
may be temporary create a branch for RN < 40?

@zxcpoiu this is why we need to bump the version as well so people can choose. look at https://github.com/oney/react-native-webrtc/pull/192

I understand.
the pain is at:
from now on, we force everyone to stay webrtc 0.54.4 unless they upgrade to RN 0.40
but it seems the only way to go
thanks for this and sharing your experiences @Kenny-House

yep, and we should change the README to reflect that change.

Sure thing @zxcpoiu , thanks for your work this fantastic library.

@sagivo added into readme

A week has passed. Is there any new progress now?


Add support for conditional rendering to jsx-multiline-wrap

Main issue: https://github.com/yannickcr/eslint-plugin-react/issues/1282
I tried to make the fixer better so the output has the parens in the correct place. Probably, need to add a few more tests, but I think the current solution looks quite solid.
The rule is defaulted to false initially. If enabling it by default, a bigger version bump would be required?
See also some comments on another issue regarding jsx-multiline-wrap: https://github.com/yannickcr/eslint-plugin-react/issues/1207#issuecomment-313086986

FYI broken build doesn't seem to be related to this branch. Currently when I try to build master I get the same error messages, even though the latest build on travis for master was successful (21hrs ago: https://travis-ci.org/yannickcr/eslint-plugin-react/builds/250125668)

I know that it'd require a bigger version bump, but to me it'd make more sense to have all the rules enabled by default.
Also, while you're in there, feel like adding ternaries?

Enabling rules by default should wait for a separate semver-major PR, released after the non-major changes are released.

*** sits wriggling with excitement waiting for the merge ***

Sorry for the inconvenience; I've just merged a refactor to start using arrow functions. Would you mind rebasing?

Are there some problems regarding for this PR to be moved forward?
I'd like to take a further look at this rule because I currently joined a project where we use a lot of conditional rendering and eslint-plugin-react doesn't always fix things as I expect it to. 😄

Seems like this was added in another PR, hence closing.
To achieve this functionality, use the option: {logical: 'parens'} or {logical: 'parens-new-line'}.

@jseminck sorry about the conflict :-)


[managedEnvironments]: "identity" property missing in type definition

Resource Type
Microsoft.App/managedEnvironments
Api Version
2024-03-01
Issue Type
Missing property(s)
Other Notes
No response
Bicep Repro
resource environmentIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
  name: 'mgid-cae-identity-sample'
  location: 'westeurope'
}

resource cae 'Microsoft.App/managedEnvironments@2024-03-01' = {
  name: 'cae-identity-sample'
  location: 'westeurope'
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      '${environmentIdentity.id}': {}
    }
  }
  properties: {
    ...
  }
}

The identity assignment to the Container Apps Environment is giving me a warning which I have to disable with #disable-next-line BCP187:

The property "identity" does not exist in the resource or type definition, although it might still be valid.

Following the documentation (where it shows 2023-11-02-preview as latest, although I can deploy against version 2024-03-01 as in my sample) identity is available on the type and it does in fact deploy just fine.
Confirm

[X] I have read the troubleshooting guide and looked for duplicates.

Just wanted to chime in, because I think other fields are (probably?) missing as well:

properties.appInsightsConfiguration
properties.openTelemetryConfiguration


removing func ref

@MandiOhlinger,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/core/conversion-functoids.md
:warning:Warning
View
Details

biztalk/core/input-parameters-functoid-property.md
:warning:Warning
View
Details

biztalk/core/looping-functoid.md
:warning:Warning
View
Details

biztalk/core/mathematical-functoids.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/step-1-modify-the-vprev-biztalk-project-in-oracle-database.md
:warning:Warning
View
Details

biztalk/core/assert-functoid.md
:warning:Warning
View
Details

biztalk/core/how-to-add-assert-functoids-to-a-map.md
:warning:Warning
View
Details

biztalk/core/how-to-add-basic-functoids-to-a-map.md
:warning:Warning
View
Details

biztalk/core/how-to-add-looping-functoids-to-a-map.md
:warning:Warning
View
Details

biztalk/core/how-to-add-nil-value-functoids-to-a-map.md
:warning:Warning
View
Details

biztalk/core/how-to-insert-an-any-element-or-any-attribute-node.md
:warning:Warning
View
Details

biztalk/core/string-functoids.md
:warning:Warning
View
Details

biztalk/core/table-looping-and-table-extractor-functoids.md
:warning:Warning
View
Details

biztalk/core/table-looping-grid-functoid-property.md
:warning:Warning
View
Details

biztalk/core/database-functoids.md
:warning:Warning
View
Details

biztalk/core/date-and-time-functoids.md
:warning:Warning
View
Details

biztalk/core/nil-value-functoid.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-sql/receive-strongly-typed-polling-based-data-changed-messages-from-sql-in-biztalk.md
:warning:Warning
View
Details

biztalk/core/basic-functoids.md
:warning:Warning
View
Details

biztalk/core/creating-schemas-using-biztalk-editor.md
:warning:Warning
View
Details

biztalk/core/cumulative-functoids.md
:warning:Warning
View
Details

biztalk/core/logical-functoids.md
:warning:Warning
View
Details

biztalk/core/using-biztalk-mapper.md
:warning:Warning
View
Details

biztalk/core/using-functoids-to-create-more-complex-mappings.md
:warning:Warning
View
Details

biztalk/core/advanced-functoids.md
:warning:Warning
View
Details

biztalk/core/functoid-categories.md
:warning:Warning
View
Details

biztalk/core/functoid-input-parameters.md
:warning:Warning
View
Details

biztalk/core/general-troubleshooting-questions-and-answers.md
:warning:Warning
View
Details

biztalk/core/scientific-functoids.md
:warning:Warning
View
Details

biztalk/core/10-n-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/TOC.md
:white_check_mark:Succeeded

biztalk/core/absolute-value-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/add-days-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/addition-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/advanced-functoids-reference.md
:white_check_mark:Succeeded
View

biztalk/core/arc-tangent-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/ascii-to-character-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/assert-functoid-reference.md
:white_check_mark:Succeeded
View

biztalk/core/base-specified-logarithm-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-cross-reference-import-tool-btsxrefimport-exe.md
:white_check_mark:Succeeded

biztalk/core/character-to-ascii-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/common-logarithm-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/conversion-functoids-reference.md
:white_check_mark:Succeeded
View

biztalk/core/cosine-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-average-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-concatenate-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-functoids-reference.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-maximum-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-minimum-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-sum-functoid.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

biztalk/core/conversion-functoids.md

Line 32: [Warning] Invalid file link:(~/core/hexadecimal-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/octal-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/character-to-ascii-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/ascii-to-character-functoid.md).
Line 36: [Warning] Invalid file link:(~/core/conversion-functoids-reference.md).

biztalk/core/input-parameters-functoid-property.md

Line 42: [Warning] Invalid file link:(~/core/functoid-reference.md).

biztalk/core/looping-functoid.md

Line 100: [Warning] Invalid file link:(~/core/table-looping-functoid-reference.md).

biztalk/core/mathematical-functoids.md

Line 29: [Warning] Invalid file link:(~/core/subtraction-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/modulo-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/maximum-value-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/absolute-value-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/minimum-value-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/multiplication-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/square-root-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/addition-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/integer-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/round-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/division-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/mathematical-functoids-reference.md).

biztalk/adapters-and-accelerators/adapter-oracle-database/step-1-modify-the-vprev-biztalk-project-in-oracle-database.md

Line 93: [Warning] Invalid file link:(~/core/string-left-trim-functoid.md).

biztalk/core/assert-functoid.md

Line 23: [Warning] Invalid file link:(~/core/assert-functoid-reference.md).
Line 24: [Warning] Invalid file link:(~/core/logical-functoids-reference.md).

biztalk/core/how-to-add-assert-functoids-to-a-map.md

Line 49: [Warning] Invalid file link:(~/core/assert-functoid-reference.md).

biztalk/core/how-to-add-basic-functoids-to-a-map.md

Line 63: [Warning] Invalid file link:(~/core/functoid-reference.md).
Line 94: [Warning] Invalid file link:(~/core/conversion-functoids-reference.md).
Line 95: [Warning] Invalid file link:(~/core/cumulative-functoids-reference.md).
Line 96: [Warning] Invalid file link:(~/core/database-functoids-reference.md).
Line 97: [Warning] Invalid file link:(~/core/date-and-time-functoids-reference.md).
Line 98: [Warning] Invalid file link:(~/core/logical-functoids-reference.md).
Line 99: [Warning] Invalid file link:(~/core/mathematical-functoids-reference.md).
Line 100: [Warning] Invalid file link:(~/core/scientific-functoids-reference.md).
Line 101: [Warning] Invalid file link:(~/core/string-functoids-reference.md).

biztalk/core/how-to-add-looping-functoids-to-a-map.md

Line 56: [Warning] Invalid file link:(~/core/looping-functoid-reference.md).

biztalk/core/how-to-add-nil-value-functoids-to-a-map.md

Line 42: [Warning] Invalid file link:(~/core/nil-value-functoid-reference.md).

biztalk/core/how-to-insert-an-any-element-or-any-attribute-node.md

Line 30: [Warning] Invalid file link:(~/core/scripting-functoid-reference.md).
Line 30: [Warning] Invalid file link:(~/core/mass-copy-functoid-reference.md).

biztalk/core/string-functoids.md

Line 39: [Warning] Invalid file link:(~/core/string-concatenate-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-find-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-left-trim-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-right-trim-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-left-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/lowercase-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/uppercase-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-right-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/string-extract-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/size-functoid.md).
Line 43: [Warning] Invalid file link:(~/core/string-functoids-reference.md).

biztalk/core/table-looping-and-table-extractor-functoids.md

Line 29: [Warning] Invalid file link:(~/core/table-looping-functoid-reference.md).
Line 31: [Warning] Invalid file link:(~/core/table-extractor-functoid-reference.md).

biztalk/core/table-looping-grid-functoid-property.md

Line 37: [Warning] Invalid file link:(~/core/table-looping-functoid-reference.md).
Line 38: [Warning] Invalid file link:(~/core/table-extractor-functoid-reference.md).

biztalk/core/database-functoids.md

Line 63: [Warning] Invalid file link:(~/core/database-functoids-reference.md).
Line 97: [Warning] Invalid file link:(~/core/get-common-value-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/remove-application-id.md).
Line 97: [Warning] Invalid file link:(~/core/get-common-id-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/value-extractor-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/set-common-id-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/get-application-value-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/get-application-id-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/database-lookup-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/error-return-functoid.md).
Line 97: [Warning] Invalid file link:(~/core/format-message-functoid.md).
Line 101: [Warning] Invalid file link:(~/core/database-functoids-reference.md).

biztalk/core/date-and-time-functoids.md

Line 30: [Warning] Invalid file link:(~/core/add-days-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/date-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/date-and-time-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/time-functoid.md).

Line 125: [Warning] Invalid file link:(~/core/cumulative-average-functoid.md).
Line 125: [Warning] Invalid file link:(~/core/cumulative-sum-functoid.md).
Line 125: [Warning] Invalid file link:(~/core/cumulative-minimum-functoid.md).
Line 125: [Warning] Invalid file link:(~/core/cumulative-maximum-functoid.md).
Line 129: [Warning] Invalid file link:(~/core/cumulative-functoids-reference.md).

biztalk/core/logical-functoids.md

Line 60: [Warning] Invalid file link:(~/core/logical-string-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/less-than-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/equal-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-numeric-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-or-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/not-equal-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/less-than-or-equal-to-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/isnil-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-not-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-and-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/greater-than-or-equal-to-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/greater-than-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-date-functoid.md).
Line 60: [Warning] Invalid file link:(~/core/logical-existence-functoid.md).
Line 64: [Warning] Invalid file link:(~/core/logical-functoids-reference.md).

biztalk/core/using-biztalk-mapper.md

Line 64: [Warning] Invalid file link:(~/core/functoid-reference.md).

biztalk/core/using-functoids-to-create-more-complex-mappings.md

Line 24: [Warning] Invalid file link:(~/core/functoid-reference.md).

biztalk/core/advanced-functoids.md

Line 42: [Warning] Invalid file link:(~/core/scripting-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/value-mapping-flattening-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/looping-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/record-count-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/iteration-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/index-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/mass-copy-functoid-reference.md).
Line 42: [Warning] Invalid file link:(~/core/value-mapping-functoid-reference.md).

biztalk/core/functoid-categories.md

Line 25: [Warning] Invalid file link:(~/core/scripting-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/table-looping-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/nil-value-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/assert-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/value-mapping-flattening-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/looping-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/record-count-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/iteration-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/index-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/advanced-functoids-reference.md).
Line 25: [Warning] Invalid file link:(~/core/table-extractor-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/mass-copy-functoid-reference.md).
Line 25: [Warning] Invalid file link:(~/core/value-mapping-functoid-reference.md).
Line 26: [Warning] Invalid file link:(~/core/hexadecimal-functoid.md).
Line 26: [Warning] Invalid file link:(~/core/octal-functoid.md).
Line 26: [Warning] Invalid file link:(~/core/conversion-functoids-reference.md).
Line 26: [Warning] Invalid file link:(~/core/character-to-ascii-functoid.md).
Line 26: [Warning] Invalid file link:(~/core/ascii-to-character-functoid.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-concatenate-functoid.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-average-functoid.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-sum-functoid.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-minimum-functoid.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-functoids-reference.md).
Line 27: [Warning] Invalid file link:(~/core/cumulative-maximum-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/get-common-value-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/remove-application-id.md).
Line 28: [Warning] Invalid file link:(~/core/get-common-id-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/value-extractor-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/set-common-id-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/get-application-value-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/get-application-id-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/database-lookup-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/error-return-functoid.md).
Line 28: [Warning] Invalid file link:(~/core/database-functoids-reference.md).
Line 28: [Warning] Invalid file link:(~/core/format-message-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/add-days-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/date-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/date-and-time-functoids-reference.md).
Line 29: [Warning] Invalid file link:(~/core/date-and-time-functoid.md).
Line 29: [Warning] Invalid file link:(~/core/time-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-string-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/less-than-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/equal-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-numeric-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-or-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/not-equal-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/less-than-or-equal-to-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/isnil-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-functoids-reference.md).
Line 30: [Warning] Invalid file link:(~/core/logical-not-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-and-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/greater-than-or-equal-to-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/greater-than-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-date-functoid.md).
Line 30: [Warning] Invalid file link:(~/core/logical-existence-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/subtraction-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/modulo-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/maximum-value-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/absolute-value-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/minimum-value-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/multiplication-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/mathematical-functoids-reference.md).
Line 31: [Warning] Invalid file link:(~/core/square-root-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/addition-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/integer-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/round-functoid.md).
Line 31: [Warning] Invalid file link:(~/core/division-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/cosine-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/sine-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/common-logarithm-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/natural-logarithm-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/x-y-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/arc-tangent-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/10-n-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/tangent-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/scientific-functoids-reference.md).
Line 32: [Warning] Invalid file link:(~/core/natural-exponential-functoid.md).
Line 32: [Warning] Invalid file link:(~/core/base-specified-logarithm-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-concatenate-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-find-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-left-trim-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-right-trim-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-left-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/lowercase-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-functoids-reference.md).
Line 33: [Warning] Invalid file link:(~/core/uppercase-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-right-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/string-extract-functoid.md).
Line 33: [Warning] Invalid file link:(~/core/size-functoid.md).

biztalk/core/functoid-input-parameters.md

Line 33: [Warning] Invalid file link:(~/core/functoid-reference.md).

biztalk/core/general-troubleshooting-questions-and-answers.md

Line 47: [Warning] Invalid file link:(~/core/error-return-functoid.md).

biztalk/core/scientific-functoids.md

Line 35: [Warning] Invalid file link:(~/core/cosine-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/sine-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/common-logarithm-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/natural-logarithm-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/x-y-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/arc-tangent-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/10-n-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/tangent-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/natural-exponential-functoid.md).
Line 35: [Warning] Invalid file link:(~/core/base-specified-logarithm-functoid.md).
Line 39: [Warning] Invalid file link:(~/core/scientific-functoids-reference.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/core/database-functoids.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/step-1-modify-the-vprev-biztalk-project-in-oracle-database.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/receive-strongly-typed-polling-based-data-changed-messages-from-sql-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/core/10-n-functoid.md
:white_check_mark:Succeeded

biztalk/core/TOC.md
:white_check_mark:Succeeded

biztalk/core/absolute-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/add-days-functoid.md
:white_check_mark:Succeeded

biztalk/core/addition-functoid.md
:white_check_mark:Succeeded

biztalk/core/advanced-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/advanced-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/arc-tangent-functoid.md
:white_check_mark:Succeeded

biztalk/core/ascii-to-character-functoid.md
:white_check_mark:Succeeded

biztalk/core/assert-functoid-reference.md
:white_check_mark:Succeeded

biztalk/core/assert-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/base-specified-logarithm-functoid.md
:white_check_mark:Succeeded

biztalk/core/basic-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-cross-reference-import-tool-btsxrefimport-exe.md
:white_check_mark:Succeeded

biztalk/core/character-to-ascii-functoid.md
:white_check_mark:Succeeded

biztalk/core/common-logarithm-functoid.md
:white_check_mark:Succeeded

biztalk/core/conversion-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/conversion-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/cosine-functoid.md
:white_check_mark:Succeeded

biztalk/core/creating-schemas-using-biztalk-editor.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-average-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-concatenate-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/cumulative-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-maximum-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-minimum-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-sum-functoid.md
:white_check_mark:Succeeded

biztalk/core/database-functoids-reference.md
:white_check_mark:Succeeded
View

biztalk/core/database-lookup-functoid.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoid.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/date-functoid.md
:white_check_mark:Succeeded

biztalk/core/developers-reference.md
:white_check_mark:Succeeded
View

biztalk/core/division-functoid.md
:white_check_mark:Succeeded

biztalk/core/equal-functoid.md
:white_check_mark:Succeeded

biztalk/core/error-return-functoid.md
:white_check_mark:Succeeded

biztalk/core/format-message-functoid.md
:white_check_mark:Succeeded

biztalk/core/functoid-categories.md
:white_check_mark:Succeeded
View

biztalk/core/functoid-input-parameters.md
:white_check_mark:Succeeded
View

biztalk/core/functoid-reference.md
:white_check_mark:Succeeded

biztalk/core/general-troubleshooting-questions-and-answers.md
:white_check_mark:Succeeded
View

biztalk/core/get-application-id-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-application-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-common-id-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-common-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/greater-than-functoid.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

biztalk/core/database-functoids.md

Line 51: [Warning] Invalid file link:(~/core/database-functoids-reference.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/step-1-modify-the-vprev-biztalk-project-in-oracle-database.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sql/receive-strongly-typed-polling-based-data-changed-messages-from-sql-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/core/10-n-functoid.md
:white_check_mark:Succeeded

biztalk/core/TOC.md
:white_check_mark:Succeeded

biztalk/core/absolute-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/add-days-functoid.md
:white_check_mark:Succeeded

biztalk/core/addition-functoid.md
:white_check_mark:Succeeded

biztalk/core/advanced-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/advanced-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/arc-tangent-functoid.md
:white_check_mark:Succeeded

biztalk/core/ascii-to-character-functoid.md
:white_check_mark:Succeeded

biztalk/core/assert-functoid-reference.md
:white_check_mark:Succeeded

biztalk/core/assert-functoid.md
:white_check_mark:Succeeded
View

biztalk/core/base-specified-logarithm-functoid.md
:white_check_mark:Succeeded

biztalk/core/basic-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/biztalk-server-cross-reference-import-tool-btsxrefimport-exe.md
:white_check_mark:Succeeded

biztalk/core/character-to-ascii-functoid.md
:white_check_mark:Succeeded

biztalk/core/common-logarithm-functoid.md
:white_check_mark:Succeeded

biztalk/core/conversion-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/conversion-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/cosine-functoid.md
:white_check_mark:Succeeded

biztalk/core/creating-schemas-using-biztalk-editor.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-average-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-concatenate-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/cumulative-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/cumulative-maximum-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-minimum-functoid.md
:white_check_mark:Succeeded

biztalk/core/cumulative-sum-functoid.md
:white_check_mark:Succeeded

biztalk/core/database-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/database-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/database-lookup-functoid.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoid.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoids-reference.md
:white_check_mark:Succeeded

biztalk/core/date-and-time-functoids.md
:white_check_mark:Succeeded
View

biztalk/core/date-functoid.md
:white_check_mark:Succeeded

biztalk/core/developers-reference.md
:white_check_mark:Succeeded
View

biztalk/core/division-functoid.md
:white_check_mark:Succeeded

biztalk/core/equal-functoid.md
:white_check_mark:Succeeded

biztalk/core/error-return-functoid.md
:white_check_mark:Succeeded

biztalk/core/format-message-functoid.md
:white_check_mark:Succeeded

biztalk/core/functoid-categories.md
:white_check_mark:Succeeded
View

biztalk/core/functoid-input-parameters.md
:white_check_mark:Succeeded
View

biztalk/core/functoid-reference.md
:white_check_mark:Succeeded

biztalk/core/general-troubleshooting-questions-and-answers.md
:white_check_mark:Succeeded
View

biztalk/core/get-application-id-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-application-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-common-id-functoid.md
:white_check_mark:Succeeded

biztalk/core/get-common-value-functoid.md
:white_check_mark:Succeeded

biztalk/core/greater-than-functoid.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: add Data Processing and Data Visualization sections with relevant tools

Information

Name
Category

ETL
Data processing

Numpy
Data processing

Pandas
Data processing

Matplotlib
Data visualization

Chart.js
Data visualization

Description
Added Data processing and Data visualization sections.
Added ETL, Numpy and Pandas badges in Data processing.
Added Matplotlib and Chart.js badges in Data visualization.
Preview

Preview
Markdown Code

[![ETL](https://custom-icon-badges.demolab.com/badge/ETL-9370DB?logo=etl-logo&logoColor=fff)](#)

[![NumPy](https://custom-icon-badges.demolab.com/badge/NumPy-4DABCF?logo=numpy-icon&logoColor=fff)](#)

[![Pandas](https://custom-icon-badges.demolab.com/badge/Pandas-150458?logo=pandas&logoColor=fff)](#)

[![matplotlib](https://custom-icon-badges.demolab.com/badge/Matplotlib-71D291?logo=matplotlib-logo&logoColor=fff)](#)

[![Chart.js](h(https://custom-icon-badges.demolab.com/badge/Chart.js-FF6384?logo=chartdotjs&logoColor=fff)](#)

thanks @codecruz!

Thank you, @inttter, for reviewing, fixing, and merging the pull request! I really appreciate it. I'll be contributing more in the future!


Plz use branches :(

@redhann Might be a couple of bugs in data_handler.py, not sure though, should lmk what you think. If there are, should probably make a branch and PR.
c.execute("""CREATE TABLE IF NOT EXISTS info_db (time_ timestamp, title text, length real, link text, filepath text, thumnbnail text);""")
c.execute('''DELETE * FROM ht_db WHERE time_>=?;''',(timestamp))

Is ht_db supposed to be info_db here when deleting using timestamp?
Should time>=?; be time_<=?; as we're deleting the older timestamped rows
Also I think the c.execute argument should be a tuple, so shouldn't it be (timestamp,)

Additionally, it might be nice to have a check in insert_data so that we don't insert data if the link already exists in the db.
Last nitpick might be having timestamp as an argument instead of doing it when insert_data is called, though it probably doesn't matter too much.

yes oops
also yes oops
no, it's okay just needs to be a sequence. see https://docs.python.org/3/library/sqlite3.html

I don't want a timestamp argument but I see an argument for tracking the video's last updated info


SSIS and Replication Commands -- Remove SSIS Commands, Update SMO/Library Import and Messages

fixes #7553
Creating SSIS objects is unreliable and supporting it will require a ton of DLLs that will increase the size of dbatools. We can move these commands to a new module if we ever decide to create one.
RMO, so far, is still working.

All checks pass ✔


Deadlock in algorithm when using a custom security initializer

Actual Behavior
I was running constantly into a deadlock situation in which the algorithm just randomly stops running and hangs. And I managed to pinpoint it to the exact lines in the code.
Reproducing the Problem

Use a custom security initializer like this:

In your algorithm code access for instance the TotalPortfolioValue.

And now here is how it comes to a deadlock between the ResultThread and IsolatorThread:
ResultThread
For some reason even though the fee model is one of the predefined classes implemented in c#, it still goes through the PythonWrapper when calculating the fees and because of that it acquires the Python.GIL() mutex. The result thread updates the trade statistics and at some point requires the _totalPortfolioValueLock.

IsolatorThread
The IsolatorThread runs the algorithm code and if you access at some point TotalPortfolioValue or any other statistic, then it also needs the _totalPortfolioValueLock. And when the python code is called, it is of course also wrapped in the Python.GIL() lock.

This leads to a deadlock. And I don't know what is the best way to solve this. Maybe you have some thoughts.
Here is also the call stack when the deadlock happens:

System Information

I think it's independent from the system, but I'm running it on Ubuntu 22.04.2. And I've made sure to pull the latest master branch version.
Potential solution
If the fee model wouldn't go through the PythonWrapper, there wouldn't be a deadlock. This would work for cases in which the fee model is actually not in python, but for python custom fee model initializers this would need to be fixed differently.
Another solution would be to not include fees in the UnrealizedProfit calculation, which would then remove the dependency on any custom python code execution in the ResultThread as far as I understand.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

Thank you for the detail report @yuriyarabskyyPro! We will look into it 👍


Truncated commands in ConsoleHost_history.txt

ConsoleHost_history.txt collects commands issued in the console. However, Powershell core truncates commands to 215 characters.
The classic power shell (not core) saves full command line, so it is a regression.
I think that the previous version of PS core also saved more (but not sure about that and do not want to downgrade to verify).
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0 ```

/cc @daxian-dbw Is it PSReadline related?

I don't see the symptom. Can you provide a reproducible example?
Here's an example of a command that works fine across sessions; it outputs a 501-character string literal and reports its length:
(write-output 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxy').length

I cannot confirm directly this 215 characters truncation now; I just see it is truncated in the history file.
However I could provide this issue that is similar:
.\product\src\Run-Test2.ps1 -TargetHost api.redacted.net -TestName ScaleGoals.jmx -DurationInSeconds $(3600*27) -WorkerCount 25 -JMeterProperties "-GOveralGoalPercentage=100 -GSETUP_FILE=100-1k.json" -pfxCertificatePath D:\frome2e_smartspacese2ekeyvault-redacted-20200430.pfx -generateReportJMeterReport $false -collectLog $false

This does not show up in the history file at all, however this
.\product\src\Run-Test2.ps1 -TargetHost api.redacted.net -TestName ScaleGoals.jmx -DurationInSeconds $(3600*27) -WorkerCount 25 -JMeterProperties "-GOveralGoalPercentage=100 -GSETUP_FILE=100-1k.json" -pfxCertificatePath D:\from.pfx -generateReportJMeterReport $false -collectLog $false

is saved in the history file. The only difference is how long is the path to pfx file.
I did a few retries and only this change affects the the history update.
If I have repros of the truncation I will update the thread.

I do not observe the issue anymore after new updates