Bump DC/OS Diagnostics

High-level description
What features does this change enable? What bugs does this change fix?
Fixes https://jira.mesosphere.com/browse/COPS-5509
Corresponding DC/OS tickets (required)

COPS-5509 DC/OS Diagnostics Bundle Download fails via Master Load Balancer

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review @janisz @br-lewis @drewvanstone


ARM support

Building on ARM fails:
error[E0433]: failed to resolve: could not find `x86_64` in `arch`
  --> /home/xazax/.cargo/registry/src/index.crates.io-6f17d22bba15001f/number-theory-0.0.23/src/arithmetic/inlineops.rs:70:26
   |
70 |     unsafe { core::arch::x86_64::_addcarry_u64(carry, x, y, output) }
   |                          ^^^^^^ could not find `x86_64` in `arch`

error[E0433]: failed to resolve: could not find `x86_64` in `arch`
  --> /home/xazax/.cargo/registry/src/index.crates.io-6f17d22bba15001f/number-theory-0.0.23/src/arithmetic/inlineops.rs:75:26
   |
75 |     unsafe { core::arch::x86_64::_subborrow_u64(carry, x, y, output) }
   |                          ^^^^^^ could not find `x86_64` in `arch`

Extended to support ARM, albeit with likely suboptimal algorithm.

Thanks! I have this a try and got some compilation errors:
error[E0308]: mismatched types
  --> /home/xazax/.cargo/registry/src/index.crates.io-6f17d22bba15001f/number-theory-0.0.24/src/arithmetic/inlineops.rs:92:50
   |
92 |           let (flag,interim) = x.overflowing_sub(carry);
   |                                  --------------- ^^^^^ expected `u64`, found `u8`
   |                                  |
   |                                  arguments to this method are incorrect
   |
note: method defined here
  --> /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/num/mod.rs:1167:5
   = note: this error originates in the macro `uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
help: you can convert a `u8` to a `u64`
   |
92 |           let (flag,interim) = x.overflowing_sub(carry.into());
   |                                                       +++++++

error[E0599]: no method named `overflowing_sub` found for type `bool` in the current scope
  --> /home/xazax/.cargo/registry/src/index.crates.io-6f17d22bba15001f/number-theory-0.0.24/src/arithmetic/inlineops.rs:93:37
   |
93 |           let (flag2,res) = interim.overflowing_sub(y);
   |                                     ^^^^^^^^^^^^^^^ method not found in `bool`

error[E0308]: mismatched types
  --> /home/xazax/.cargo/registry/src/index.crates.io-6f17d22bba15001f/number-theory-0.0.24/src/arithmetic/inlineops.rs:95:14
   |
95 |           if flag || flag2{
   |              ^^^^ expected `bool`, found `u64`

@JASory I opened a PR to fix the compilation errors here: https://github.com/JASory/ENT/pull/7


Use system version of libfmt instead of rosfmt vendored one on ROS 1

Including this package on a ROS Noetic setup where other packages use system libfmt-dev causes xqms/rosfmt#12 to break them.
We're dropping mqtt from our setup for different reasons, so this isn't exhaustively tested. But in case it helps, these changes drop rosfmt in favor of system libfmt-dev and the package still builds on Noetic, which is the only version this is released into. A simple test run of the nodelet also seems to format error messages just fine.

Great, thanks!


Fixed import statements in home page code engine example

In the engine example at the home page, the import statement is wrong.
It shows from sourced.spark import API as Engine instead of  the correct statement from sourced.engine import Engine.
I'm not sure it these are the files to fix it, I guess so. If they aren't let me know and I'll be happy to change the right files.

merged by https://github.com/src-d/landing/pull/210


Run AdvDupe_FinishPasting for normal Duplicator

AdvDupe_FinishPasting is a hook that both advduplicator and advdupe2
call once the contraption has finished pasting. It's useful for E2s, as
running on "if (first() | duped())" means that it can run before your
contraption is only partially pasted. This means that for E2s that are
expecting to be pasted as part of a large contraption, it's only really
possible to use one of the non-standard duplicator tools, for
dupefinished()'s sake.
This patches the duplicator module to also call AdvDupe_FinishPasting
when it's done. It passes all the same data as advdupe2 does, which
means that it should be compatible with anything that's out there in the
wild.
The way the code is written also allows for the duplicator module
functions to start taking extra parameters and returning extra values
without breaking the code.
Fixes #1407. Closes #1515.

I've tested this (so blame me if it's broken!)


refactor collections

Refactor collections to reduce the APIs exposure and usage difficulty

@corazawaf/core-developers please your comments before continuing this PR!

Moving this to v4


added libalglib-dev

Please add debian and fedora entries as well.
Thanks!

can you use the suffix -devel for the fedora entry so that they all use the development version of the package ? (like in libann-dev below) thanks

Oh, sorry.


Player jumps to end of video when video source chnaged

Current Behavior:
Player jumps to end of video when source changed
Expected Behavior:
Player starts from 00:00
Steps To Reproduce:

Go to https://stackblitz.com/edit/vidstack-examples-iqz5p6?file=src%2FPlayer.vue
Run play
Click "change"

Environment:

Framework: Vue
OS: Ubuntu 22.04
Browser: Electron / Firefox (I think other too)

It's because you're switching the source to a live stream.


refactor(test): enable travis builds to conduct integration tests

rename test classes to Maven expected format
add logging configuration for testing
update provided test scenes/controls to match ones stored in the Interactive Studio
fix service provider tests failing
enable travis to do automated integration tests using environment variables

@pahimar,
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


DMPTool by the Numbers displaying incorrect number for Participating Orgs

I just noticed that the DMPTool by the numbers section on the home page has 408 participating institutions now. Last I looked it was around 270ish. I assume this is b/c of the ROR integration db changes?
I checked the Participating Institutions list and it looks like some of those listed should not actually be managed accounts, though it is hard to say for sure without seeing the old version. Some examples of orgs I don't think have managed accounts:
Bishop Ascendant Inc. (bishopascendant.com)
Arukah Institute of Healing (arukahinstitute.org)
JoJo Cups

updated the records in the database. Looks like one of my manual cleanup scripts after the upgrade incorrectly defined them as "managed".


NoneType object has no attribute groups

Hi!
I have a problem with creating record files with your create_pet_tf_record.py version.  When I call:
python object_detection/dataset_tools/create_pet_tf_record.py --label_map_path=object_detection/data/label.pbtxt --data_dir=pwd --output_dir=pwd``
it returns me this error:
File "object_detection/dataset_tools/create_pet_tf_record.py", line 204, in
tf.app.run()
File "/Users/user/tensorflow/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "object_detection/dataset_tools/create_pet_tf_record.py", line 199, in main
image_dir, train_examples)
File "object_detection/dataset_tools/create_pet_tf_record.py", line 168, in create_tf_record
tf_example = dict_to_tf_example(data, label_map_dict, image_dir)
File "object_detection/dataset_tools/create_pet_tf_record.py", line 112, in dict_to_tf_example
class_name = get_class_name_from_filename(data['filename'])
File "object_detection/dataset_tools/create_pet_tf_record.py", line 57, in get_class_name_from_filename
return match.groups()[0]
AttributeError: 'NoneType' object has no attribute 'groups'
Can anyone know the solution of this problem?

Solved problem. Reason was wrong picture names. Different than in map.pbtxt.

Hi..I'm facing the same issue...can you share me your working map.pbtxt..thanks

Same issue, please explain more about 'map.pbtxt'. thanks.

Hello, what about 2 classes? how should the images be named?

Faced same issue.
File "object_detection/dataset_tools/create_pet_tf_record.py", line 69,
in get_class_name_from_filename return match.groups()[0]
AttributeError: 'NoneType' object has no attribute 'groups'
Because of these lines in file create_pet_tf_record.py:
match = re.match(r'([A-Za-z_]+)(_[0-9]+\.jpg)', file_name, re.I)
return match.groups()[0]
Just changed filenames from *.jpeg -> *.jpg and it helped.

how should the image name be changed if there are 2 classes?

or maybe change
match = re.match(r'([A-Za-z_]+)(_[0-9]+\.jpg)', file_name, re.I) to
match = re.match(r'([A-Za-z]+)([0-9]+\.jpg)', file_name, re.I)


Set x margin for flowchart in CLI

The x margin on a flowchart is much larger than the y margin. The CLI provides a way to set the margins for sequence and gantt diagrams, but not for flow diagrams (as far as I can tell).
Is it possible to set the x margin for a flowchart using the current CLI?

Not currently. Will try to align how the various diagrams work in the CLI. Will take a w hile though as I am currently working focused on Class Diagrams. Will set this as help wanted as it would be great if someone looked at it.

Given how long ago this issue's activity died out, I'm closing it.
This allows us to maintain a fresh list of issues the community is interested in.
Feel free to create a new issue, if necessary.


Working with USB epson printer TM-T88V

Does this library suport USB connected printers? I'm trying to get the paper sensor status from a TM-T88V printer, can I do this with this library?

Good afternoon!
Yes, the library works great with USB-connected printers as long as you are using the virtual com port drivers provided by Epson.
I have updated the Readme with a USB Usage Guide, please review it and if you run into any issues, let me know on this issue and I'll update the guide.

Also, printer statuses are implemented in 2 ways, one is to read status as needed, but if you have an Epson, you can enable Automatic Status Back, and you can hook up an event every time a status changes (for example as paper starts and stops feeding, or runs out of paper, or door is open, etc. you will get a callback on your event with properties on what changed).  The included support app shows off the status changes and what data is in them.

@juanMorenoDev pinging to make sure you see this update.  I'm closing this issue but please let me know if you give it a try.

Yes! Thank you very much for your quick response, I test it and works fine!


Cannot use Chrome DevTools to debug a Tabris.js app

Problem description
When using latest Chrome (83.0.4103.61) and Tabris.js (3.5.0) and trying to connect the debugger to a running Tabris.js app as described in the documentation:

To connect the Chrome DevTools to a Tabris.js app on the default port 9090, the following URL should be entered:
devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=<device-ip>:9090
(https://docs.tabris.com/latest/debug.html)
Exchange  with the IP of your Android device.

... Chrome shows an empty page instead of the inspector UI. Following error is output to the console:
Uncaught (in promise) TypeError: Cannot assign to read only property 'length' of object '#<Storage>'
    at SettingsStorage.setPreference [as _setCallback] (host.js:106)
    at SettingsStorage.set (common.js:330)
    at VersionController._migrateSettingsFromLocalStorage (common.js:429)
    at VersionController._updateVersionFrom11To12 (common.js:396)
    at VersionController.updateVersion (common.js:366)
    at MainImpl._createSettings (main.js:37)
    at MainImpl._gotPreferences (main.js:34)
    at InspectorFrontendHostStub.getPreferences (host.js:105)
    at MainImpl._loaded (main.js:32)

Environment

Tabris.js version: 3.5.0
Device: ASUS X01BDA
OS: Android 9

Thanks for bringing it up. It works as expected in VSC and WebStorm. The chrome devtools have been teste as well. We will look into it.

Workaround: in chrome developer console goto Application, right click on local storage and clear.

The workaround is valid 👍


Web Error

I can't use my flutter project on web but I used to the same project. On chrome it shows these errors;

Hi @BeratTezer
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Changed FileLoggerAdapterSpec to fail gracefully on Windows

Running tests on Windows caused this error:
B:\Projects\Parse Server\parse-server\spec\FileLoggerAdapter.spec.js:38
        expect(results[0].message).toEqual('testing info logs');
                         ^

TypeError: Cannot read property 'message' of undefined
    at B:\Projects\Parse Server\parse-server\spec\FileLoggerAdapter.spec.js:38:26
    at ParsePromise.<anonymous> (B:\Projects\Parse Server\parse-server\src\Adapters\Logger\FileLoggerAdapter.js:9:17440)
    at ParsePromise.wrappedResolvedCallback (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:139:41)
    at ParsePromise.resolve (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:72:36)
    at resolveOne (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:471:29)
    at ParsePromise.object.then.errors.(anonymous function) (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:480:13)
    at ParsePromise.wrappedResolvedCallback (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:139:41)
    at ParsePromise.resolve (B:\Projects\Parse Server\parse-server\node_modules\parse\lib\node\ParsePromise.js:72:36)
    at ReadFileContext.callback (B:\Projects\Parse Server\parse-server\src\Adapters\Logger\FileLoggerAdapter.js:9:16189)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:303:13)

Rest of the tests could not be run as the test runner would break here. This change adds a check to fail when the FileLoggerAdapter returns an empty array from here: https://github.com/ParsePlatform/parse-server/blob/master/src/Adapters/Logger/FileLoggerAdapter.js#L191
Regarding the cause of the error itself, it is due to different filename separators in *nix and Windows. The FileLoggerAdapter would not save logs (have not tested this). This is a separate issue and should also be fixed.

Current coverage is 90.56%

Merging #946 into master will decrease coverage by -0.79% as of 3e5542e

@@            master    #946   diff @@
======================================
  Files           73      73
  Stmts         4324    4324
  Branches       863     863
  Methods          0       0
======================================
- Hit           3950    3916    -34
  Partial         10      10
- Missed         364     398    +34

Review entire Coverage Diff as of 3e5542e

Powered by Codecov. Updated on successful CI builds.

This is really bad to change the spec to accommodate the problem you're facing. please propose a PR that solved the problem instead of hiding it.

The problem i am facing is that the test runner breaks while running tests on Windows. This is solely concerned with how this spec is written. If there is something wrong in the code, the appropriate tests should fail. Bugs in the code should not make the entire test suite unusable.

please propose a PR that solved the problem instead of hiding it.

I agree that there exists a bug in the code that needs to be fixed, and I hope someone from the community comes up with a fix. This does not hide the bug, rather it highlights it by making this test fail. This change improves the spec by catching a failure it did not before. It makes the test fail where it should.

You can propose the fix, to build paths that are functional in windows use
path.resolve and path.separator this should be a 1-2 liner, and I can merge it as soon as you propose it :)

@flovilmart I'm trying your fix although it does not work. Will make a new PR if I can get it working


[19.07] luci-app-ksmbd: support new UCI option, update for 3.2.1 version

support new UCI option "allow_legacy_protocols"
update for 3.2.1 version (usmbd -> ksmbd.mountd)

Depends on: openwrt/packages#11297

Please rebase your changes

Please rebase your changes

done... i really suck at those rebases lol

@Andy2244 sorry but that is because of the translations.
Could you also please do a separate commit for uci option add and api change?

Could you also please do a separate commit for uci option add and api change?

done


Integrate Google Maps/Waze traffic

To be notified of an exceptional event leading to congestion or just to precise trip computation time and choose the timely shortest one. Just an open-source Google Maps/Waze implementation would already be nice.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. For example:
I'm always frustrated when [...]
Describe the ideal solution
A clear and concise description of what you want to see in Organic Maps.
Describe alternatives you have considered

How do you solve this issue now with Organic Maps or other apps?
Attach any examples, screenshots, or screen recordings from other apps that help us to better understand the idea.

Additional context
Add any other context or screenshots about the feature request here.

See Waze_traffic and Waze_traffic/issues/13.

Related to Benjamin-Loison/android/issues/28, to potentially vocally state I am going to be notified of such rare event.


Move to sample attester rather than offline_fs_kbc for nontee tests

We should stop thinking about the offline_fs_kbc as our non-tee KBC. Instead we should use the cc_kbc with the sample attester for this. The offline_fs_kbc is a KBC for platforms that protect the rootfs with encryption, but it isn't ideal for testing. I have mentioned this before, but here I will list the reasons more clearly.
Why?
First, the offline_fs_kbc makes it tricky for new users to test out encrypted images. If someone comes to the project without hardware, they will use the nontee runtime class. Currently the only way for them to use their own encrypted image with that runtime class is to modify the rootfs. This is not approachable for new users.
Here  is an example thread where a new user tried to follow the quickstart guide, which explains how to provision resources via the KBS. Since they were using the nontee runtime class, this didn't work. With the sample attester, the flow for provisioning resources for TDX/SNP would be the same as for the non-tee runtime class.
As a side note, in the past we tried to get around a similar issue by creating the ssh-demo CRD. By switching to the sample attester, we can probably get rid of this.
Second, the offline_fs_kbc does not test the attestation code path at all. Currently our testing of the attestation code path is extremely spotty. In fact the KBS isn't explicitly referenced anywhere in the Kata or operator CI. The TDX CI does cover it, but this is up to the configuration of the CI node, which is behind a firewall. It would be better to have this crucial aspect of the project covered more directly by our CI. Of course the sample attester does not constitute a rigorous attestation, but it does trigger the complete attestation codepath from AA->KBS->AS and back.
Third, it could be misleading to expose flows that store secrets in the rootfs. Besides s390x, none of our platforms support encrypted root disks, so we risk confusing people when we write tests that do exactly that. Of course this is a less concrete concern than the previous two, but I think it's still significant.
Fourth, the offline_fs_kbc might not be compatible with advanced features of the CDH. As of today I think the CDH (like the online_sev_kbc does work with all of the new features that have been added to the CDH, but as we continue to add more advanced features, that might no longer be the case. If we want to test all these features in the non-tee CI, we'll probably need to use some kind of online KBC like the sample one.
How?
So how/when would we make the switch? I think writing tests for Kata main could be the right time. If we switch to the sample attester, provisioning resource for SNP/TDX and nontee would be very similar. I think this can help us writing the tests. Of course the s390x tests will still need to modify the initrd.
We can potentially keep the offline_fs_kbc in the rootfs for the nontee runtime class in case people do want to modify the initrd. With this approach we could potentially continue to support the existing approach as well as the sample attester in the nontee runtime class.
I am creating this issue today so that I can reference it in some small fixes to various components, but I am planning to pursue this more directly as well.
@ChengyuZhu6 @lindayu17 I am tagging you because you were working on some features for Kata that might involve attestation. Please ignore this entire post if it is not helpful, but if you have been wondering about how to setup tests that involve provisioning things via attestation, this might be useful. Basically I think you can write tests for the nontee runtime class by using the sample-kbc (which is included in the AA by default). Then we can add platform-specific tests as a second step.
@stevenhorsman @wainersm @fidencio @jepio @portersrc

Hey Tobin,
I'm not against us switching to sample_kbc if that makes more sense and is easier for users to set up for the non-TEE tests and just keep the offline_fs_kbc for the s390x tests, there are a couple of things I'd like your thoughts on, that could be done potentially as part of this wider issue, or done beforehand to prep for the kata-containers main testing:

This is almost certainly just a me issue, but do we have any documentation for how to use sample_kbc yet? I've had a look around and can't find anything, but am probably looking in the wrong place. Note, this isn't a reason to not switch over as our offline_fs_kbc docs are probably not perfect either, but we have some and I know how to use them and we have a fair few examples of usages to copy, whereas I've not needed to play with sample_kbc, so it would be good to see how straight forward it is to set-up and integrate into the kata tests
In image-rs I think that all of the current integration tests: https://github.com/confidential-containers/guest-components/tree/main/image-rs/tests use the offline_fs_kbc, so do you think we should add sample_kbc support there first to test it before it gets included in kata, or is it not straight-forward to get set-up in that sort of environment.

Thanks!
PS: I guess another thing to note (which again isn't a blocker), is that switching over to sample-kbc is likely to take a little bit more time, so might cause a slight delay to 0.9 features getting merged to main, but if we think this is the correct approach then I think it's worth any costs, but we'll want to decide sooner rather than later

This is almost certainly just a me issue, but do we have any documentation for how to use sample_kbc yet?

Not really. I am doing some legwork to make sure it actually works and I can add some docs as part of that.

In image-rs I think that all of the current integration tests: https://github.com/confidential-containers/guest-components/tree/main/image-rs/tests use the offline_fs_kbc, so do you think we should add sample_kbc support there first to test it before it gets included in kata, or is it not straight-forward to get set-up in that sort of environment.

I think it's fine to stick with the current approach for the image-rs integration tests. No need to go through the whole KBS roundtrip for that.

I guess another thing to note (which again isn't a blocker), is that switching over to sample-kbc is likely to take a little bit more time, so might cause a slight delay to 0.9 features getting merged to main, but if we think this is the correct approach then I think it's worth any costs, but we'll want to decide sooner rather than later

I am hoping that this will make things easier for v0.9.0 but if it turns out to be a big can of worms we can just stick with the current approach.

Btw when I first wrote this I used the wrong term. We don't want the sample_kbc, we want the cc_kbc with the sample attester.

I think this is a good idea mostly for reasons 1 and 2 (better for first-time users; and exercises attestation code path for testing). With respect to this:

We can potentially keep the offline_fs_kbc in the rootfs for the nontee runtime class in case people do want to modify the initrd....
-- yes, I think it's better to keep that support there.

Ok, I think I have wrapped up the underlying work required to easily use the sample attester (https://github.com/confidential-containers/guest-components/pull/425 https://github.com/confidential-containers/guest-components/pull/426 https://github.com/confidential-containers/kbs/pull/283)
Now when we build the guest components, we can simply do make build TEE_PLATFORM=none and only the sample attester will be enabled.
For the KBS, it's pretty to deploy with docker compose. There is a guide for this here. I will summarize here as well.
Set up keys for the cluster.
openssl genpkey -algorithm ed25519 > kbs/config/private.key
openssl pkey -in kbs/config/private.key -pubout -out kbs/config/public.pub

Run cluster
docker compose up

Build the client tool and provision a resource with something like
 ./kbs-client --url http://<IP_ADDRESS>:8080 config --auth-private-key ../../kbs/config/private.key  set-resource --path my_repo/resource_type/123abc --resource-file test_resource

By default the KBS will reject sample evidence, so you might also want to set a more permissive resource policy.
./kbs-client --url http://<IP_ADDRESS>:8080 config --auth-private-key ../../kbs/config/private.key  set-resource-policy --policy-file allow_all.rego

You can also set a policy that will require a particular launch measurement.

Hi @fitzthum !
This sounds as a good idea.
Now that we have some code to install KBS for testing on Kata main and PR 8870 is in advanced state; I thought in start looking at porting the encryption tests.
Do you know if we can use the existing encrypted images?

Good question. Maybe we should actually make another issue for the encryted tests. Otherwise this one can probably be closed.
Regarding the images, we have these ones that should work. The singed images are broken and need to be regenerated but the encrypted ones are good.
That said, I think we should consider making new images for the encrypted image tests where the encrypted image does not have identical content to the unencrypted image. There are some weird quirks with container caching that can cause confusion if you have an encrypted image and an unencrypted one that are identical. Under normal circumstances we should not hit these issues, but to be totally foolproof if might be good to have the encrypted image contain a file that says ENCRYPTED and for the test to check that this exists after decrypting the image.


NLog WebService target creates too many connections

NLog version: 4.7.6
Platform: .Net Core 3.1
I have a .NET Core 3.1 service which make use of NLog. Here is my NLog.config code:
<?xml version="1.0" ?>
<nlog autoReload="true"
      xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <targets>
    <target name="AsyncInformation" xsi:type="AsyncWrapper">
      <target type="WebService"
                  name="ws"
                  url="https://log-api.com/log/v1"
                  protocol="JsonPost">
        <parameter name="">
          <layout xsi:type="newrelic-jsonlayout">
            <attribute name="time" layout="${date}" />
            <attribute name="level" layout="${level:upperCase=true}"/>
            <attribute name="message" layout="${message}" />
            <attribute name="host" layout="${machinename}" />
            <attribute name="ActivityId" layout="${activityId}" />
            <attribute name="processId" layout="${processId}" />
            <attribute name="threadid" layout="${threadid}" />
            <attribute name="event-properties" >
              <layout type="JsonLayout" includeAllProperties="true" maxRecursionLimit="0" escapeForwardSlash="true" />
            </attribute>
            <attribute name="exception" layout="${exception}" />
            <attribute name="traceId" layout="${var:traceId}" />
          </layout>
        </parameter>
        <header name="X-License-Key" layout="${environment:LICENSE_KEY}"/>
      </target>
    </target>
  </targets>
  <rules>
    <logger name="*" minlevel="Information" maxlevel="Error" writeTo="AsyncInformation"/>
  </rules>
</nlog>

My service is hosted in Azure and I can see that code is running and I can see also the logs arrive into in my API. Service performance been hit and the CPU usage is very high (most of the time 100%), I have noticed that our open connections have been increased from 700 to 2,000 (which is the maximum amount of allowed connections) which I believe is the source of the performance issue.
I tried to get into NLog source code and noticed that WebService target (which I use) is using HttpWebRequest which I believe is the reason for these huge amount of connections that being opened because the connection is not persistence. I wonder if there is an option use the WebService target but with reusing the connections by keeping the connections alive?
Or there is an option to use HttpClient instead of HttpWebRequest in the WebService target?
Any help would be great.

See also: https://stackoverflow.com/q/67803384/193178

Closing this as an "external" issue in NetCoreApp31, that has been fixed with Net50. See also: https://github.com/dotnet/corefx/pull/41462
Alternative you could try out https://github.com/DarekDan/NLog.Targets.HTTP


Live Demo website down

https://templates.mudblazor.com/ doesn't seem to be working anymore.

Has been down from a few days

Is this still alive ?

 There will come a replacement soon

You are doing a good job!

Hi! any news about this?

Hmmm

Prob late feburary.


sell channels using trade secret

The other PR is on paid-services repo:
https://github.com/alexbosworth/paid-services/pull/7
files changed:
bos

merged, but it had to be rebased so github wont' auto close it


Feature request: SneakyThrows Quick Fix

Short description
Would love there to be a quick fix that adds an @SneakyThrows annotation to a method when code in there throws a checked Exception.
Expected behavior
Alt-Enter on problem code that throws an exception should have an Add @SneakyThrows menu item that adds the annotation to fix the problem.

Should be available in the next version of plugin (0.28)


Roll Flutter Engine from 2b353ae90731 to 51928f24d501 (2 revisions)

https://github.com/flutter/engine/compare/2b353ae90731...51928f24d501
2023-06-05<EMAIL_ADDRESS>Use the arm64 dsymutil on Mac M1 machines (flutter/engine#42533)
2023-06-05<EMAIL_ADDRESS>Roll Skia from a226cfbd6cc7 to 7db361be474b (14 revisions) (flutter/engine#42578)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jonahwilliams@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Lazy loaded data does not display

Hi,
I tried to lazy load with table.
Here is my Html code.
<generic-table #myTable [gtSettings]="configObject.settings" [gtFields]="configObject.fields" [gtData]="configObject.data" (gtEvent)="trigger($event)" [gtInfo]="configObject.info" [gtOptions]="{stack:false, highlightSearch:true, lazyLoad:true, rowSelection:true}"></generic-table>

<gt-pagination [genericTable]="myTable" [gtClasses]="'pagination-sm'"></gt-pagination>

public trigger = function($event){
    console.log("EVENT",event)
    console.log("pageCurrent",$event.value.pageCurrent,$event.value.recordLength)
    switch ($event.name){
        case 'gt-page-changed-lazy':
            this.getData($event.value.pageCurrent , $event.value.recordLength);
            break;
        case 'gt-sorting-applied':
            console.log($event.value);
            break;
        default:
            console.log($event);
            break;
    }
  };

getData = function(pageCurrent, recordLength){

    this.userService.getUsers(this.at).subscribe(users => {
      var TotalRecords=users.length;
      this.userService.getUsersLimit(pageCurrent, recordLength).subscribe(users=>{
        this.users = users;
        this.userService.getRoles(this.at).subscribe(roles => {
          var roles = roles;
          for(var i in this.users) {
            if(this.users[i].APART_ID === this.aid) {
              var rolename = roles.filter(role => role.ROLE_ID === this.users[i].ROLE_ID);
              this.configObject.data.push({
                 // id:users[i].id,
                  name: this.users[i].FIRST_NAME + " " + this.users[i].LAST_NAME,
                  role: rolename[0].ROLE_NAME,
                  email: this.users[i].EMAIL,
                  mobile: this.users[i].MOBILE1,
              })

              this.configObject.info = <GtInformation>{
                      pageNext: 2,
                      pageCurrent: 1,
                      pagePrevious: null,
                      recordLength: 5,
                      recordsAfterFilter: TotalRecords, // server need to return total number of records, ie. 1000 in you case
                      recordsAfterSearch: TotalRecords, // server need to return total number of records, ie. 1000 in you case
                      recordsAll: TotalRecords, // server need to return total number of records, ie. 1000 in you case

                  }
              console.log("info",this.configObject.info);
              console.log("///",this.configObject.data)
             // this.configObject.info.searchTerms = 'al';
            }
          }
        })
      })
  })

    console.log("this///",this.configObject);
  }

Here is my output

I display only 5 records.When i click next page display another record.I have totally 11 records.
First display 5 records work fine.When i click another page records are retrieved but not display.why?
Then if i go to previous page I got this err
ERROR RangeError: Maximum call stack size exceeded
How can fix it?
Kindly advice me,
Thanks

Well I’m just browsing through your code now on my phone and it looks like you’re making the client a bit too smart and putting a lot of logic in the client that should probably be on your server, like filtering.
If you look at this example (look at the network traffic and the data returned by the server). You shouldn’t push the new data to the record set client side either, just set data to whatever is returned by the server. If you enable caching for lazy loading generic table will handle the rest and persist the data for you.

Hi,
I try to search table.But all data is loaded.why?
Here is my code.
 <input type="text" class="form-control" id="Weight" #search (keyup)="myTable.gtSearch(search.value)" placeholder="Search">
 <generic-table #myTable [gtSettings]="configObject.settings" [gtFields]="configObject.fields" [gtData]="configObject.data" (gtEvent)="trigger($event)" [gtInfo]="configObject.info" [gtOptions]="{lazyLoad:true, highlightSearch:true, rowSelection:true}"></generic-table>

Kindly advice me ,
Thanks


Cross-compile on Linux, target i686-pc-windows-gnu fails.

Compiling a program that uses Tracy and works on Linux.
Trying a compile with target cargo build --target i686-pc-windows-gnu. Compile time errors.
Looks like a missing dependency at the C++ level, or wrong version, or something like that.
System doing the compile is 20.04 LTS.
Program being compiled is "Rend3": Location: https://github.com/BVE-Reborn/rend3
The following warnings were emitted during compilation:

warning: In file included from tracy/client/TracyProfiler.hpp:17,
warning:                  from tracy/client/TracyScoped.hpp:11,
warning:                  from tracy/client/TracyProfiler.cpp:71,
warning:                  from tracy/TracyClient.cpp:23:
warning: tracy/client/../common/TracyMutex.hpp:19:25: error: ‘mutex’ in namespace ‘std’ does not name a type
warning:    19 | using TracyMutex = std::mutex;
warning:       |                         ^~~~~
warning: tracy/client/../common/TracyMutex.hpp:16:1: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
warning:    15 | #include <mutex>
warning:   +++ |+#include <mutex>
warning:    16 |
warning: In file included from tracy/client/TracyScoped.hpp:11,
warning:                  from tracy/client/TracyProfiler.cpp:71,
warning:                  from tracy/TracyClient.cpp:23:
warning: tracy/client/TracyProfiler.hpp:795:5: error: ‘TracyMutex’ does not name a type
warning:   795 |     TracyMutex m_serialLock;
warning:       |     ^~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:799:5: error: ‘TracyMutex’ does not name a type
warning:   799 |     TracyMutex m_fiLock;
warning:       |     ^~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static tracy::QueueItem* tracy::Profiler::QueueSerial()’:
warning: tracy/client/TracyProfiler.hpp:170:11: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   170 |         p.m_serialLock.lock();
warning:       |           ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static tracy::QueueItem* tracy::Profiler::QueueSerialCallstack(void*)’:
warning: tracy/client/TracyProfiler.hpp:177:11: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   177 |         p.m_serialLock.lock();
warning:       |           ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::QueueSerialFinish()’:
warning: tracy/client/TracyProfiler.hpp:186:11: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   186 |         p.m_serialLock.unlock();
warning:       |           ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::SendFrameImage(const void*, uint16_t, uint16_t, uint8_t, bool)’:
warning: tracy/client/TracyProfiler.hpp:226:18: error: ‘class tracy::Profiler’ has no member named ‘m_fiLock’; did you mean ‘m_sock’?
warning:   226 |         profiler.m_fiLock.lock();
warning:       |                  ^~~~~~~~
warning:       |                  m_sock
warning: tracy/client/TracyProfiler.hpp:234:18: error: ‘class tracy::Profiler’ has no member named ‘m_fiLock’; did you mean ‘m_sock’?
warning:   234 |         profiler.m_fiLock.unlock();
warning:       |                  ^~~~~~~~
warning:       |                  m_sock
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemAlloc(const void*, size_t, bool)’:
warning: tracy/client/TracyProfiler.hpp:398:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   398 |         GetProfiler().m_serialLock.lock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:400:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   400 |         GetProfiler().m_serialLock.unlock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemFree(const void*, bool)’:
warning: tracy/client/TracyProfiler.hpp:411:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   411 |         GetProfiler().m_serialLock.lock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:413:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   413 |         GetProfiler().m_serialLock.unlock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemAllocCallstack(const void*, size_t, int, bool)’:
warning: tracy/client/TracyProfiler.hpp:429:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   429 |         profiler.m_serialLock.lock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:432:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   432 |         profiler.m_serialLock.unlock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemFreeCallstack(const void*, int, bool)’:
warning: tracy/client/TracyProfiler.hpp:451:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   451 |         profiler.m_serialLock.lock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:454:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   454 |         profiler.m_serialLock.unlock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemAllocNamed(const void*, size_t, bool, const char*)’:
warning: tracy/client/TracyProfiler.hpp:468:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   468 |         GetProfiler().m_serialLock.lock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:471:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   471 |         GetProfiler().m_serialLock.unlock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemFreeNamed(const void*, bool, const char*)’:
warning: tracy/client/TracyProfiler.hpp:482:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   482 |         GetProfiler().m_serialLock.lock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:485:23: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   485 |         GetProfiler().m_serialLock.unlock();
warning:       |                       ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemAllocCallstackNamed(const void*, size_t, int, bool, const char*)’:
warning: tracy/client/TracyProfiler.hpp:501:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   501 |         profiler.m_serialLock.lock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:505:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   505 |         profiler.m_serialLock.unlock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp: In static member function ‘static void tracy::Profiler::MemFreeCallstackNamed(const void*, int, bool, const char*)’:
warning: tracy/client/TracyProfiler.hpp:524:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   524 |         profiler.m_serialLock.lock();
warning:       |                  ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.hpp:528:18: error: ‘class tracy::Profiler’ has no member named ‘m_serialLock’
warning:   528 |         profiler.m_serialLock.unlock();
warning:       |                  ^~~~~~~~~~~~
warning: In file included from tracy/TracyClient.cpp:23:
warning: tracy/client/TracyProfiler.cpp: At global scope:
warning: tracy/client/TracyProfiler.cpp:141:10: error: ‘once_flag’ in namespace ‘std’ does not name a type
warning:   141 |     std::once_flag once_flag;
warning:       |          ^~~~~~~~~
warning: In file included from tracy/TracyClient.cpp:23:
warning: tracy/client/TracyProfiler.cpp:99:1: note: ‘std::once_flag’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
warning:    98 | #  include <lmcons.h>
warning:   +++ |+#include <mutex>
warning:    99 | extern "C" typedef LONG (WINAPI *t_RtlGetVersion)( PRTL_OSVERSIONINFOW );
warning: In file included from tracy/TracyClient.cpp:23:
warning: tracy/client/TracyProfiler.cpp: In constructor ‘tracy::RPMallocInit::RPMallocInit()’:
warning: tracy/client/TracyProfiler.cpp:154:14: error: ‘call_once’ is not a member of ‘std’
warning:   154 |         std::call_once( once_flag, InitOnceCallback );
warning:       |              ^~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:154:25: error: ‘once_flag’ was not declared in this scope
warning:   154 |         std::call_once( once_flag, InitOnceCallback );
warning:       |                         ^~~~~~~~~
warning: In file included from tracy/TracyClient.cpp:23:
warning: tracy/client/TracyProfiler.cpp: In function ‘const char* tracy::GetHostInfo()’:
warning: tracy/client/TracyProfiler.cpp:531:50: error: ‘std::thread’ has not been declared
warning:   531 |     ptr += sprintf( ptr, "CPU cores: %i\n", std::thread::hardware_concurrency() );
warning:       |                                                  ^~~~~~
warning: tracy/client/TracyProfiler.cpp: In function ‘LONG tracy::CrashFilter(PEXCEPTION_POINTERS)’:
warning: tracy/client/TracyProfiler.cpp:702:10: error: ‘std::this_thread’ has not been declared
warning:   702 |     std::this_thread::sleep_for( std::chrono::milliseconds( 500 ) );
warning:       |          ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:704:58: error: ‘std::this_thread’ has not been declared
warning:   704 |     while( !GetProfiler().HasShutdownFinished() ) { std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) ); };
warning:       |                                                          ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::SpawnWorkerThreads()’:
warning: tracy/client/TracyProfiler.cpp:1271:14: error: ‘std::this_thread’ has not been declared
warning:  1271 |         std::this_thread::sleep_for( std::chrono::milliseconds( 1 ) );
warning:       |              ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::Worker()’:
warning: tracy/client/TracyProfiler.cpp:1372:70: error: ‘std::this_thread’ has not been declared
warning:  1372 |     while( m_timeBegin.load( std::memory_order_relaxed ) == 0 ) std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                                                                      ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:1492:18: error: ‘std::this_thread’ has not been declared
warning:  1492 |             std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                  ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:1682:26: error: ‘std::this_thread’ has not been declared
warning:  1682 |                     std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                          ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:1815:18: error: ‘std::this_thread’ has not been declared
warning:  1815 |             std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                  ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::CompressWorker()’:
warning: tracy/client/TracyProfiler.cpp:1826:70: error: ‘std::this_thread’ has not been declared
warning:  1826 |     while( m_timeBegin.load( std::memory_order_relaxed ) == 0 ) std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                                                                      ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:1834:21: error: ‘m_fiLock’ was not declared in this scope; did you mean ‘m_sock’?
warning:  1834 |             while( !m_fiLock.try_lock() )
warning:       |                     ^~~~~~~~
warning:       |                     m_sock
warning: tracy/client/TracyProfiler.cpp:1845:17: error: ‘m_fiLock’ was not declared in this scope; did you mean ‘m_sock’?
warning:  1845 |                 m_fiLock.unlock();
warning:       |                 ^~~~~~~~
warning:       |                 m_sock
warning: tracy/client/TracyProfiler.cpp:1878:18: error: ‘std::this_thread’ has not been declared
warning:  1878 |             std::this_thread::sleep_for( std::chrono::milliseconds( 20 ) );
warning:       |                  ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::ClearSerial()’:
warning: tracy/client/TracyProfiler.cpp:1980:13: error: ‘m_serialLock’ was not declared in this scope
warning:  1980 |     while( !m_serialLock.try_lock() )
warning:       |             ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:1992:9: error: ‘m_serialLock’ was not declared in this scope
warning:  1992 |         m_serialLock.unlock();
warning:       |         ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘tracy::Profiler::DequeueStatus tracy::Profiler::DequeueSerial()’:
warning: tracy/client/TracyProfiler.cpp:2283:17: error: ‘m_serialLock’ was not declared in this scope
warning:  2283 |         while( !m_serialLock.try_lock() )
warning:       |                 ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:2294:13: error: ‘m_serialLock’ was not declared in this scope
warning:  2294 |             m_serialLock.unlock();
warning:       |             ^~~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::HandleDisconnect()’:
warning: tracy/client/TracyProfiler.cpp:2808:22: error: ‘std::this_thread’ has not been declared
warning:  2808 |                 std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                      ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp:2837:18: error: ‘std::this_thread’ has not been declared
warning:  2837 |             std::this_thread::sleep_for( std::chrono::milliseconds( 10 ) );
warning:       |                  ^~~~~~~~~~~
warning: tracy/client/TracyProfiler.cpp: In member function ‘void tracy::Profiler::CalibrateTimer()’:
warning: tracy/client/TracyProfiler.cpp:2849:10: error: ‘std::this_thread’ has not been declared
warning:  2849 |     std::this_thread::sleep_for( std::chrono::milliseconds( 200 ) );
warning:       |          ^~~~~~~~~~~
warning: In file included from tracy/TracyClient.cpp:26:
warning: tracy/client/TracySysTrace.cpp: In function ‘bool tracy::SysTraceStart(int64_t&)’:
warning: tracy/client/TracySysTrace.cpp:396:37: error: ‘TraceSetInformation’ was not declared in this scope; did you mean ‘HeapSetInformation’?
warning:   396 |         const auto intervalStatus = TraceSetInformation( 0, TraceSampledProfileIntervalInfo, &interval, sizeof( interval ) );
warning:       |                                     ^~~~~~~~~~~~~~~~~~~
warning:       |                                     HeapSetInformation
warning: tracy/client/TracySysTrace.cpp:422:35: error: ‘std::thread’ has not been declared
warning:   422 |     s_prop->MinimumBuffers = std::thread::hardware_concurrency() * 4;
warning:       |                                   ^~~~~~
warning: tracy/client/TracySysTrace.cpp:423:35: error: ‘std::thread’ has not been declared
warning:   423 |     s_prop->MaximumBuffers = std::thread::hardware_concurrency() * 6;
warning:       |                                   ^~~~~~
warning: tracy/client/TracySysTrace.cpp:453:34: error: ‘TraceSetInformation’ was not declared in this scope; did you mean ‘HeapSetInformation’?
warning:   453 |         const auto stackStatus = TraceSetInformation( s_traceHandle, TraceStackTracingInfo, &stackId, sizeof( stackId ) );
warning:       |                                  ^~~~~~~~~~~~~~~~~~~
warning:       |                                  HeapSetInformation
warning: tracy/client/TracySysTrace.cpp: In function ‘void tracy::SysTraceSendExternalName(uint64_t)’:
warning: tracy/client/TracySysTrace.cpp:536:26: error: ‘GetProcessIdOfThread’ was not declared in this scope
warning:   536 |         const auto pid = GetProcessIdOfThread( hnd );
warning:       |                          ^~~~~~~~~~~~~~~~~~~~
warning: In file included from tracy/TracyClient.cpp:27:
warning: tracy/common/TracySocket.cpp: In member function ‘int tracy::Socket::Recv(void*, int, int)’:
warning: tracy/common/TracySocket.cpp:342:19: error: aggregate ‘tracy::Socket::Recv(void*, int, int)::pollfd fd’ has incomplete type and cannot be defined
warning:   342 |     struct pollfd fd;
warning:       |                   ^~
warning: tracy/common/TracySocket.cpp:344:17: error: ‘POLLIN’ was not declared in this scope
warning:   344 |     fd.events = POLLIN;
warning:       |                 ^~~~~~
warning: tracy/common/TracySocket.cpp:23:16: error: ‘WSAPoll’ was not declared in this scope
warning:    23 | #  define poll WSAPoll
warning:       |                ^~~~~~~
warning: tracy/common/TracySocket.cpp:346:9: note: in expansion of macro ‘poll’
warning:   346 |     if( poll( &fd, 1, timeout ) > 0 )
warning:       |         ^~~~
warning: tracy/common/TracySocket.cpp: In member function ‘bool tracy::Socket::HasData()’:
warning: tracy/common/TracySocket.cpp:425:19: error: aggregate ‘tracy::Socket::HasData()::pollfd fd’ has incomplete type and cannot be defined
warning:   425 |     struct pollfd fd;
warning:       |                   ^~
warning: tracy/common/TracySocket.cpp:427:17: error: ‘POLLIN’ was not declared in this scope
warning:   427 |     fd.events = POLLIN;
warning:       |                 ^~~~~~
warning: tracy/common/TracySocket.cpp:23:16: error: ‘WSAPoll’ was not declared in this scope
warning:    23 | #  define poll WSAPoll
warning:       |                ^~~~~~~
warning: tracy/common/TracySocket.cpp:429:12: note: in expansion of macro ‘poll’
warning:   429 |     return poll( &fd, 1, 0 ) > 0;
warning:       |            ^~~~
warning: tracy/common/TracySocket.cpp: In member function ‘tracy::Socket* tracy::ListenSocket::Accept()’:
warning: tracy/common/TracySocket.cpp:515:19: error: aggregate ‘tracy::ListenSocket::Accept()::pollfd fd’ has incomplete type and cannot be defined
warning:   515 |     struct pollfd fd;
warning:       |                   ^~
warning: tracy/common/TracySocket.cpp:517:17: error: ‘POLLIN’ was not declared in this scope
warning:   517 |     fd.events = POLLIN;
warning:       |                 ^~~~~~
warning: tracy/common/TracySocket.cpp:23:16: error: ‘WSAPoll’ was not declared in this scope
warning:    23 | #  define poll WSAPoll
warning:       |                ^~~~~~~
warning: tracy/common/TracySocket.cpp:519:9: note: in expansion of macro ‘poll’
warning:   519 |     if( poll( &fd, 1, 10 ) > 0 )
warning:       |         ^~~~
warning: tracy/common/TracySocket.cpp: In member function ‘bool tracy::UdpBroadcast::Open(const char*, uint16_t)’:
warning: tracy/common/TracySocket.cpp:607:5: error: ‘inet_pton’ was not declared in this scope; did you mean ‘inet_ntoa’?
warning:   607 |     inet_pton( AF_INET, addr, &m_addr );
warning:       |     ^~~~~~~~~
warning:       |     inet_ntoa
warning: tracy/common/TracySocket.cpp: In member function ‘void tracy::IpAddress::Set(const sockaddr&)’:
warning: tracy/common/TracySocket.cpp:651:5: error: ‘inet_ntop’ was not declared in this scope; did you mean ‘inet_ntoa’?
warning:   651 |     inet_ntop( AF_INET, &ai->sin_addr, m_text, 17 );
warning:       |     ^~~~~~~~~
warning:       |     inet_ntoa
warning: tracy/common/TracySocket.cpp: In member function ‘const char* tracy::UdpListen::Read(size_t&, tracy::IpAddress&, int)’:
warning: tracy/common/TracySocket.cpp:736:19: error: aggregate ‘tracy::UdpListen::Read(size_t&, tracy::IpAddress&, int)::pollfd fd’ has incomplete type and cannot be defined
warning:   736 |     struct pollfd fd;
warning:       |                   ^~
warning: tracy/common/TracySocket.cpp:738:17: error: ‘POLLIN’ was not declared in this scope
warning:   738 |     fd.events = POLLIN;
warning:       |                 ^~~~~~
warning: tracy/common/TracySocket.cpp:23:16: error: ‘WSAPoll’ was not declared in this scope
warning:    23 | #  define poll WSAPoll
warning:       |                ^~~~~~~
warning: tracy/common/TracySocket.cpp:739:9: note: in expansion of macro ‘poll’
warning:   739 |     if( poll( &fd, 1, timeout ) <= 0 ) return nullptr;
warning:       |         ^~~~
warning: tracy/common/TracySocket.cpp: In member function ‘int tracy::Socket::Recv(void*, int, int)’:
warning: tracy/common/TracySocket.cpp:354:1: warning: control reaches end of non-void function [-Wreturn-type]
warning:   354 | }
warning:       | ^
warning: tracy/common/TracySocket.cpp: In member function ‘tracy::Socket* tracy::ListenSocket::Accept()’:
warning: tracy/common/TracySocket.cpp:537:1: warning: control reaches end of non-void function [-Wreturn-type]
warning:   537 | }
warning:       | ^

error: failed to run custom build command for `tracy-client-sys v0.16.0`

You should provide the entire output (i.e. include the environment variables etc. that come after the output you pasted.)
That said, you should confirm if your toolchain is able to build the upstream Tracy project at all. I myself find issues like EVENT_FILTER_EVENT_ID being absent from my mingw toolchain.

tracybuildbuild.txt
Entire output from compile.
This is with
rustc --version
rustc 1.59.0 (9d1b2106e 2022-02-23)

I know, mingw is a problem. i686-pc-windows-gnu is supposed to be a Rust "tier I target", so it's supposed to "just work". If something is missing from the Rust tool chain, that's a problem with the toolchain and should be reported.
The first error reported, with "", is interesting. That's a known error in other packages.. It's enough of a known error that rustc has a special message for it.
warning: tracy/client/../common/TracyMutex.hpp:19:25: error: ‘mutex’ in namespace ‘std’ does not name a type
warning:    19 | using TracyMutex = std::mutex;
warning:       |                         ^~~~~
warning: tracy/client/../common/TracyMutex.hpp:16:1: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
warning:    15 | #include <mutex>
warning:   +++ |+#include <mutex>
warning:    16 |

But what rustc is suggesting, adding "#include <mutex>", seems to have already been done. So this may be a newer problem in the same area. If you can confirm that i686-pc-windows-gnu toolchain is broken here, this can be passed over to that group as a bug. The mingw environment I'm using is whatever shipped with Rust.
This looks like some kind of version problem.
Is there something else you would like me to build, as a test?

Thank you for the full log.

I know, mingw is a problem. i686-pc-windows-gnu is supposed to be a Rust "tier I target", so it's supposed to "just work". If something is missing from the Rust tool chain, that's a problem with the toolchain and should be reported.
The first error reported, with "<mutex>", is interesting. That's a known error in other packages.. It's enough of a known error that rustc has a special message for it.

i686-pc-windows-gnu is indeed a T1 target, but that is only as far as Rust code is concerned. In this case the diagnostics in question come from a C++ toolchain that you have installed on your system (i686-w64-mingw32-g++) and which this crate invokes here to build a part of an upstream project implemented in C++. In that sense, the Rust toolchain and its tier levels are pretty much uninvolved here.
Unfortunately, I haven't much in terms of suggestions of what could be going wrong with the <mutex> include here. My only guess is that you may be missing some package on your system that would provide the header in question. I can't really say much else, as I'm unable to reproduce this specific problem locally. Though, as I mentioned earlier, I hit other issues building the Tracy code, even with a much more recent version of the mingw toolchain, so even if you resolve a problem with the mutex include, you won't be able to build this project using the -gnu target.

Possibly related: https://github.com/microsoft/STL/issues/980

Does not seem to be a problem with current versions as of this date.


[WIP] RE-1617 Require maas

recheck_xenial_no_artifacts_swift_deploy

Closing for now -- it seems like there's too much risk introduced by this change when the system we're trying to swap out isn't even used. Separate discussions will be raised to figure out if any integration between rpc-openstack and rpc-maas should in fact exist.


feat: DIA-1511: Support data batch context for autorefinement

fix /improve-prompt request to not require a jobid, as a job has not yet been created

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

Project coverage is 66.41%. Comparing base (cd98c73) to head (70c9e63).
Report is 3 commits behind head on master.

Files with missing lines
Patch %
Lines

adala/skills/collection/prompt_improvement.py
57.14%
3 Missing :warning:

adala/agents/base.py
0.00%
2 Missing :warning:

adala/skills/_base.py
60.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #232   +/-   ##
=======================================
  Coverage   66.41%   66.41%
=======================================
  Files          46       46
  Lines        2230     2230
=======================================
  Hits         1481     1481
  Misses        749      749

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

Does this PR introduce any functional changes or is it only about reformatting and renaming?

the only functional change is this

fix /improve-prompt request to not require a jobid, as a job has not yet been created

which I assume was a bug, unless it's to support some future pathway what I didn't know about

Approved as far as these changes being fine, but to be clear: do we just not actually need any substantive changes (aside from not requiring the job_id) to support this?

Approved as far as these changes being fine, but to be clear: do we just not actually need any substantive changes (aside from not requiring the job_id) to support this?

That's right. It's a bit hard to follow all the plumbing, but the PromptImprovementSkill is currently implemented as an AnalysisSkill: DataFrame -> Record, where all other inputs go in the static instructions field and the GT data batch is the DataFrame. This needs some rethinking in the future if we want the ability to input multiple kinds of example data, such as with and without GT, or positive (correct) vs negative (incorrect) examples. Especially since we don't actually want anything implemented in the AnalysisSkill (just batching, afaik), But that's what we have for now.

Approved as far as these changes being fine, but to be clear: do we just not actually need any substantive changes (aside from not requiring the job_id) to support this?

That's right. It's a bit hard to follow all the plumbing, but the PromptImprovementSkill is currently implemented as an AnalysisSkill: DataFrame -> Record, where all other inputs go in the static instructions field and the GT data batch is the DataFrame. This needs some rethinking in the future if we want the ability to input multiple kinds of example data, such as with and without GT, or positive (correct) vs negative (incorrect) examples. Especially since we don't actually want anything implemented in the AnalysisSkill (just batching, afaik), But that's what we have for now.


feature: outline provide in VS Code

Just a nice-to-have, but a really useful one: we should provide an outline view in the VS Code extension.

Totally not obvious from the user's perspective, but this is actually a dupe of #271, since in-document symbol navigation is powered off the same LSP call that produces the document outline.

Oh, neat. Closing this in favor of that!

❤🙏

❤🙏


Bunch of minor fixes.

@jlouis Happy to fix any problems shown up by the addition of the .travis.yml file.

The build passed on travis : https://travis-ci.org/erikd/combinatorrent/builds/189689605

Welcome fellow Necromancer!
I see you have decided to reanimate this corpse which has been lying dormant in a Nordic Tomb for far too long. Beware, the corpse has rotted a bit since the last commits and its motor skills might be worse than a Clay Golem.
I'm happy to share the secret scrolls with you, as your runes looks good. Accept my sincerest gratitude for your work.
If you manage to successfully reanimate the zombie, I'd be happy to know if it can still fight. Try giving it a Sword of Torrent +1 and an Ubuntu shield (brown or lilac). Should you wish to pursue the deeper arts of making the zombie into a wight, or strip it of its bones for a bone-dragon, please let me know.


[MM-43075] Channel Info RHS: shortcut

Summary
Add a shortcut to toggle channel info RHS: CTRL(or cmd)+shift+I
Ticket Link
https://mattermost.atlassian.net/browse/MM-43075
Related Pull Requests
N/A
Screenshots

Release Note
NONE

Looks good @JulienTant!
+1 for the toggle
I'll test and pass it once that's in place.

/e2e-tests

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/183094

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/183156

@JulienTant I took a second pass with this yesterday and found some issues that I'd missed the first time around when testing only on my Mac.
The biggest one is that Ctrl+Shift+I is the default shortcut for opening the Developer Tools on Chrome on Windows.

As such using those keys would toggle that open and closed some of the time while opening and closing the info at other times.
Also, while testing on a Windows 10 PC the Ctrl+. only worked if you press the dot on the number pad as it ignored the one on the main keyboard. On Windows 7 (using a different PC) it worked as expected but then would only work to expand (Ctrl+shift+.) when using the one on the main keyboard (and not the number pad one).
Meanwhile on both macOS and Windows (7 & 10) when you use Ctrl/CMD+. it tosses up two identical 400 errors each time you use it which might be an issue?

The biggest one is that Ctrl+Shift+I is the default shortcut for opening the Developer Tools on Chrome on Windows. As such using those keys would toggle that open and closed some of the time while opening and closing the info at other times.

I can't seem to be able to reproduce the issue. There are conditions for it to show tho: you have to be in a channel (or gm/dm) for the shortcut to be registered, it won't work on the login page, or in boards, .... If you have a way to make it fail for sure feel free to tell me. Gentle ping to @matthewbirtch for the shortcut: maybe the CTRL+SHIFT+I shortcut will end up being annoying for devs who want to display the dev console.

Meanwhile on both macOS and Windows (7 & 10) when you use Ctrl/CMD+. it tosses up two identical 400 errors each time you use it which might be an issue?

It looks like I forgot to register the Channel Info RHS as the previously opened panel, I'll push a fix for this!

Also, while testing on a Windows 10 PC the Ctrl+. only worked if you press the dot on the number pad as it ignored the one on the main keyboard. On Windows 7 (using a different PC) it worked as expected but then would only work to expand (Ctrl+shift+.) when using the one on the main keyboard (and not the number pad one).

Is it possible to make a ticket for the webapp/channels team?

Meanwhile on both macOS and Windows (7 & 10) when you use Ctrl/CMD+. it tosses up two identical 400 errors each time you use it which might be an issue?

Fixed after the last push: after opening the channel info RHS, CTRL+. will now close and reopen the channel info rhs.

@JulienTant The 400 error is no longer there so that's all set. 👍🏻
I tested further using Windows 11 on my Mac (with Parallels) and it worked as expected (including when using an external keyboard with number keys). The only problem being that it wouldn't open the dev tools on Chrome which only matters to devs, QA and a few others. I couldn't get it to trigger the dev tools except when I was on Playbooks or Boards which is expected.

@stevemudie are we ok to merge this then?

@stevemudie are we ok to merge this then?

@JulienTant I'm fine with it but the only reason I was holding off was to see what @matthewbirtch had to say about the Windows Chrome conflict. As a guess he's out today.

The biggest one is that Ctrl+Shift+I is the default shortcut for opening the Developer Tools on Chrome on Windows. As such using those keys would toggle that open and closed some of the time while opening and closing the info at other times.

I can't seem to be able to reproduce the issue. There are conditions for it to show tho: you have to be in a channel (or gm/dm) for the shortcut to be registered, it won't work on the login page, or in boards, .... If you have a way to make it fail for sure feel free to tell me. Gentle ping to @matthewbirtch for the shortcut: maybe the CTRL+SHIFT+I shortcut will end up being annoying for devs who want to display the dev console.

Ya, that's a pretty big conflict. I guess I missed that. We should definitely find an alternative for the windows shortcut. What about Cltr Alt I?

I changed  Shift to Alt 👍🏻

/e2e-test

The command /e2e-test requires all PR checks to pass.

/e2e-test


Services: first build: abs added

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:13: invalid_url: ftp://anduin.linuxfromscratch.org/BLFS/popt/popt-1.16.tar.gz : No connection adapters were found for 'ftp://anduin.linuxfromscratch.org/BLFS/popt/popt-1.16.tar.gz'
ERROR: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:20: patch_must_be_in_build: patch must be in build when source/patches is set.
WARNING: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
ERROR: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:45: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:45: missing_description: The recipe is missing a description
ERROR: /tmp/abs_83n42mqeqi/clone/recipe/meta.yaml:45: missing_doc_url: The recipe is missing a doc_url
Errors were found


Perform frontend and backend testing

Parent Issues: #66 and #61
Hours: 6

[x] Front-end testing assigned to: @rekandiah
[x] Back-end testing assigned to: @coreylevine

Testing is completed. It successfully passes on Travis.

Hours worked: 8

Hours spent:10


Update README.md

We should update the README#Configuration.
In my case i had to explicitally require 'rspec-sidekiq' in the spec_helper to avoid the following error:
NameError:
  uninitialized constant RSpec::Sidekiq

Coverage remained the same at 79.501% when pulling 11ebc330052d4e4a7d1e3af1ce0a166b13d92d02 on nic-lan:patch-1 into 2cd15b0fe2b172243e8002c4aefa39696c42d52f on philostler:develop.


Arrangement customization of the contents of the left side-navigation bar in the Chimoney documentation. ('CHIMONEY API contents ' can start from the top  followed by 'CHIMONEY API DOCS' )

The contents of 'CHIMONEY API' , that is Introduction, Getting started with Chimoney API etc. will give a better look to the website if they start from top in the side-navigation bar followed by 'CHIMONEY API DOCS and its content: Account, Info etc.'
This issue is like a recommendation to developers.

@phyleria assign this task to me. Wanna give it a try.

Feedback


Intermittent Decryption Failure (1/1000+ so far), reproduced once

Problem:
I'm using eccrypto in both browser & node in a system and am observing a decryption failure.  In the browser I'm encountering this error with specific data (so far this has been replicated once in about 1000+ uses
decryption-problem.zip
):
"Uncaught Error: The error you provided does not contain a stack trace."
When I move the same data and use case to node, I get the following error:
Failed with error: Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
    at Decipheriv.final (internal/crypto/cipher.js:183:29)
    at aes256CbcDecrypt (/Users/.../node_modules/eccrypto/index.js:61:28)
    at /Users/.../node_modules/eccrypto/index.js:256:66
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async tryDecrypting (/Users/.../index.js:44:18) {
  library: 'digital envelope routines',
  function: 'EVP_DecryptFinal_ex',
  reason: 'bad decrypt',
  code: 'ERR_OSSL_EVP_BAD_DECRYPT'
}

The associated private key was created using the eccrypto library on a browser, here is what that code looks like:
    const priKey = eccrypto.generatePrivate()
    const pubKey = eccrypto.getPublic(priKey)

This works most of the time (i.e. upwards of 1/1000), however I'd like to understand this particular failure as this rate of failure is still too high.
One important note is that private keys are being encrypted/decrypted on an HSM and stored in binary on a DB. Also the cipher text object is being stored in binary on a DB.  We could change that to base 64 and possibly look at applying ECC or other techniques to ensure data integrity, but it's not clear to me that is the issue.
I've attached an example node project with the failing data (key and ciphertext).  To run it:

unzip
npm install
node index.js

decryption-problem.zip

Note:  the 1000+ figure is when encryption/decryption cycles were both browser based.  The figure is lower (~100) now that encryption is server side and decryption remains on a browser.

After trying to decrypt with a different library based  loosely on this one (https://github.com/tibetty/ecies-lite#readme), I get the following error which I believe is telling me the mac is incorrect:
Failed with error: Error: Corrupted Ecies-lite body: unmatched authentication code
at Object.exports.decrypt (/Users/.../node_modules/ecies-lite/index.js:78:19)
at tryEciesLite (/Users/.../index.js:60:34)
at main (/Users/.../index.js:70:9)
at Object. (/Users/.../index.js:74:1)
at Module._compile (internal/modules/cjs/loader.js:945:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:962:10)
at Module.load (internal/modules/cjs/loader.js:798:32)
at Function.Module._load (internal/modules/cjs/loader.js:711:12)
at Function.Module.runMain (internal/modules/cjs/loader.js:1014:10)
at internal/main/run_main_module.js:17:11

So far, I've managed to trace this to an environment problem between two machines--on one machine the encrypt function creates something that can be decrypted. On the other machine, the cipher text cannot be decrypted.  Comparing package-lock.json and the captured output of npm install is fruitless unfortunately.
If anyone has any suggestions on a way to meaningfully compare the the library in the two environments, please do let me know.

Sorry for the late reply, I'm not sure the difference between the machines, if you can provide more info it would be helpful. Closing for now, please re-open if you still need help.


chore(main): release 0.26.1

:robot: I have created a release beep boop
0.26.1 (2023-06-08)
Bug Fixes

bb start with todo template (11579bd)
sync issue and typo on bb connect (4d0fafc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/appblocks-hub/BB-CLI/releases/tag/v0.26.1 :sunflower:


Move search app out of renderer into shared process or extension host

We need to remove node dependencies of the renderer for our sandbox effort. Search is currently a process that is triggered from the renderer (via vs/workbench/services/search/electron-browser/searchService et al). Going forward, we should move this into one of the processes that is allowed to execute node:

shared process
extension host

Filing this to get a discussion starting how to tackle this. With terminals moved, @Tyriar and @meganrogge have demonstrated that the shared process is a viable host for native processes and the patterns used for terminals can be applied to this one as well.
https://github.com/microsoft/vscode/issues/116337 has a diagram for how the shared process today is being used as host for privileged processes.

It has been the plan for awhile to move this to the EH. I can't find the old discussion about the architecture and the possible perf issues of running search in the EH, but I think this has been proved in Remote, and we can revisit this. @jrieken @kieferrm

I verified the search.forceSearchProcess setting. It needs a restart and we do not tell the user, but my understanding is this setting goes away in October anyway.


Restore [Fact] and [Theory] attributes

removed in 310ab25

I missed these removals in the PR...

:shipit:

0ec2a31


classify XML files with .ncl extension as XML

Description
When NCL support was added (see #2440), XML files with .ncl extension were classified as Text. This PR moves them to XML adding a simple heuristic.
Tested on https://gist.github.com/pchaigno/2478bc86dd831382bfba by @pchaigno and, at least for the files that still exist today, this seems to be working correctly.
XML files with .ncl extensions were being classified as text.
Checklist:

[x] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:
[x] I have included a change to the heuristics to distinguish my language from others using the same extension.

:+1: Done.


fix double free & enhence p2p failover

What this PR does / why we need it:
Before this change:

if p2pConfig().enable() == true, then srcfs will equal remote_fs, which leads to double free.
if check_accelerate_url failed, it doesn't use any cache, this will cause all data to back to the source, resulting in reduced efficiency.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Please check the following list:

[x]  Does the affected code have corresponding tests, e.g. unit test, E2E test?
[x]  Does this change require a documentation update?
[x]  Does this introduce breaking changes that would require an announcement or bumping the major version?
[x]  Do all new files have an appropriate license header?

LGTM..
maybe 'do_failover' should be renamed..


Want to maintain the repository

Do you have any experience of maintaining any Open source projects?

Good to hear about your professional career 👍
But I wanted to know about Open source contributions.

Not contributed much to widely known open source repositories, only some open source post-quantum cryptography project on github.


General Data Protection Regulation

Devise inevitable asks one user to invite another (invitee). Given the invitee hasn't consented to giving their email (or name) I wounded if you or anyone else has an opinion on if storing the users email is in breach of General Data Protection Regulation (GDPR) use of Personal Data.  If yes (or even maybe) then it might make sense to add something to the Readme warning others about this.

I like the idea of having the email be a parameter in the invitation link. It would allow you to delete it from the database. I think with gdpr having a separate table is going to help people feel more comfortable with it. Personally I would just create a chron job for deleting emails. I haven't read anything that says how long you can store it for. I plan to store the invitation email for a while so I can send out follow ups automatically in the event that they haven't responded in a week. I still plan to delete the email after a month which sounds like it would still be complying with the "rule".

@Willardgmoore I'm far from an expert but I think if the user hasn't consented to their email being stored (which given someone else is inviting them is almost certainly the case) then it would be breaking GDPR.

Consent cannot be implied and must always be given through an opt-in, a declaration or an active motion, so that there is no misunderstanding that the data subject has consented to the particular processing.


[SMALLFIX] Java 5 migrartion: replace for with foreach in alluxio.cli.fs.command.CheckConsistencyCommand#checkConsistency

[SMALLFIX] Java 5 migrartion: replace for with foreach in alluxio.cli.fs.command.CheckConsistencyCommand#checkConsistency

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/Alluxio-Pull-Request-Builder/653/
Test PASSed.


basePath component missing in the API swagger file

Description:
when we create an API from the API publisher, and retrieve its swagger file, the basePath component is missing
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This issue is cannot be reproducible in the latest pack


Convert to TypeScript and add public types

There have been a few issues related to TypeScript types (#13, #72), updating the source code to TypeScript would make future changes easier and give consumers better type support.

So admittedly I am a TS amateur.  I was just playing around with things and I did get it to config a bit easier if I added index.d.ts directly to the node_modules/cypress-image-snapshot/ with
import 'cypress';

declare global {
  namespace Cypress {
    interface Chainable {
      matchImageSnapshot: (options?: any) => void;
    }
  }
}

That removed the need to include a custom types file and include that in my tsconfig.json file for the cypress tests and or using
/// <reference types="../types/cypress-image-snapshot/" />

in the spec file to reference the type file manually.  I then can use the import statement in my support/index.ts like so
import 'cypress-image-snapshot/command'

Obviously hacking a node_modules folder is a no no but I thought that might be a way to go.  I have seen a few other plugins use this sort of pattern and thought I would give it a shot.

Yep that makes sense!  So if we add an index.d.ts to the root of cypress-image-snapshot and publish to NPM again, everyone will receive types without having to touch their node_modules directly.
I think what would be even better is if we rewrite to use TypeScript and then generate index.d.ts from our source, similar to how Formik does.
But creating types manually is definitely useful if we want to start there.

Im pretty new to typescript but would like to have a go at this issue if it is ok?

@makeupsomething for sure give it a shot!  I'm happy to review any PRs.

import "cypress";
import { MatchImageSnapshotOptions } from "jest-image-snapshot";

declare global {
    namespace Cypress {
        interface Chainable {
            matchImageSnapshot: (
                options?:
                    | string
                    | (Partial<
                          MatchImageSnapshotOptions & Loggable & Timeoutable & ScreenshotOptions
                      >),
            ) => void;
        }
    }
}

Just based on what I understood from the readme, just a good stop gap for now.

So admittedly I am a TS amateur. I was just playing around with things and I did get it to config a bit easier if I added index.d.ts directly to the node_modules/cypress-image-snapshot/ with
import 'cypress';

declare global {
  namespace Cypress {
    interface Chainable {
      matchImageSnapshot: (options?: any) => void;
    }
  }
}

Obviously hacking a node_modules folder is a no no but I thought that might be a way to go though im not sure how much different it is from having a custom types folder somewhere else. I have seen a few other plugins use this sort of pattern and thought I would give it a shot.

Adding index.d.ts as you said still gives me error in the .ts spec file-
Property 'matchImageSnapshot' does not exist on type 'Chainable<undefined>'.

Any solution? How to use this plugin with typescript?

I shifted to Percy. They have a free version as well and much smoother. Had no luck here.

I went ahead and added typings for folks to use: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/41222
Now, all you need to do is yarn add @types/cypress-image-snapshot -D for this plugin to work with TypeScript!

I still cannot get this to work with typescript.  I followed instructions on the main page
But get an error
Property 'matchImageSnapshot' does not exist on type 'cy & EventEmitter'.ts(2339)
I tried adding types @types/cypress-image-snapshot as suggested in one of the other thread but still cannot get it to work.
I changed the test file from .ts to .js to get it to run but then get the following error
cy.task('Matching image snapshot') failed with the following error:

The task 'Matching image snapshot' was not handled in the plugins file. The following tasks are registered: resetCoverage, combineCoverage, coverageReport

Any pointers?

@Keysox For some reason, even after installing the types, matchImageSnapshot property seems to be missing :(


refactor(kernelspecs): tear out createAJAXSettings

Similar to #22

Forgot to note that these are BREAKING CHANGES. On purpose, to export less.

Current coverage is 100% (diff: 100%)

Merging #24 into master will not change coverage

@@           master   #24   diff @@
===================================
  Files           6     6
  Lines          60    58     -2
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
- Hits           60    58     -2
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update df4efbe...2c311bd

After we finish trimming we should make a 2.0.0 release.

Hmmm, I'm tempted to get the terminals endpoint in before we do 2.0.0


[NEW] GreHack 2023

Name: GreHack
Website: https://grehack.fr
Date: 17 november 2023
Location: Grenoble, France
Twitter/Mastodon Handle: @GrehackConf
Free: N

Thanks!


Get underlying exception object on pos-catch middleware

Given a serverless configuration like:
provider:
  name: aws
  runtime: nodejs18.x
  stage: ${opt:stage, 'local'}
  region: us-east-1
middleware:
   pos:
     - catch: handlers/middleware/error.handler
plugins:
  - serverless-middleware

How can I get the error object thrown by the caller handler?
Looking at the generated code in .middleware folder I see this:
return Promise.resolve().then(wrappedHandler(handler.bind(auth_exports))).then(wrappedHandler(handler2.bind(profile_id_exports))).then(wrappedHandler(handler3.bind(list_exports))).catch(wrappedHandler(handler4.bind(error_exports)));

The .catch  method is there but I am not sure how to get hold of the actual error object in the error handler function.

Hi @obaqueiro ,
That middleware block should be inside a custom block:
provider:
   name: aws
   runtime: nodejs18.x
   stage: ${opt:stage, 'local'}
   region: us-east-1

custom:
   middleware:
      pos:
         - catch: handlers/middleware/error.handler

plugins:
   - serverless-middleware

Although that's not really the problem since you are getting the middleware correctly chained in the final handler.
To get the result from a previous middleware (either successful result or error), you can access context.prev in the middleware.

Closing since there was no response.


Stack overflow when trying to identify leave-one-out-connected set

Dear developers,
First of all, thank you for supplying the great BipartitePandas and PyTwoWay packages.
I have an issue identifying the leave-one-out-connected set using BipartitePandas.
Everything works well on small simulated and test data. However, if I apply the data cleaning to real admin data (>21 Mio. worker-year obs.), Python crashes. The error I get is ‘Windows fatal exception: stack overflow’. A window pops up saying “Python has stopped working” and the Python kernel in Spyder restarts.
The server I use runs on a Windows 64-bit OS. It has got a 2.1 GHz processor and 256GB RAM. Python uses only about 10GB RAM at max while my program is running. The Python version installed on this server is 3.8.8 and BipartitePandas is version 1.0.35.
I tried increasing both the stack size and recursion depth (see code in txt file). This did not resolve the problem though.
I would be grateful if you have any idea what may cause the stack overflow and how to fix it. Please find my code and associated output from the Spyder console below. (I redacted some paths from these files for security reasons.)
Best
Martin
22_8_22_bp_tw_code.txt
output_console.txt

Hi Martin,
Here's what I figured out:
-The issue is being caused by a particular method (.bridges()) from the package igraph, which is used for estimating the articulation points of the graph. Luckily .bridges() is used only for collapsed format data.
-Taking advantage of the fact that the leave-one-out code doesn't rely on this method for long format data, if you estimate the leave-out-match set, but specify collapse_at_connectedness_measure=False, then collapse after, it may work. When I tried it on my computer, this worked with large datasets I simulated that wouldn't work with collapse_at_connectedness_measure=True.
Please let me know if this works for you!
Best,
Adam

Hi Adam,
Thank you so much for your quick help. The method that you suggested solved the issue. My program just finished without any errors.
Best
Martin


BAU: return error for invalid excel submission

Adds a new SheetCheck to return useful error message if admin sheet not present for specified fund.

[x] Unit tests and other appropriate tests added or updated
[ ] README and other documentation has been updated / added (if needed)
[x] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

This does look to work nicely - the error message may be too long though. Might be one to get some quick content design on - when on the page it looks a bit overwhelming

I will leave that to you though and not block on this - as even with this error it's much better than just a 500. Could be one we tweak as a followup (or not 🤷)

I got this from design, but will doublecheck with them

Nice 👍  If content/design are happy with that error message then I'm happy enough with the code side of it.
I guess this might break down if we add more funds - at the moment I guess we're just saying that Pathfinders has a sheet called x, and Towns Funds called y, and they are exclusively owned by the fund. That's fine for now as long as we really do move away from spreadsheets for future funds 🤞

Nice 👍 If content/design are happy with that error message then I'm happy enough with the code side of it.
I guess this might break down if we add more funds - at the moment I guess we're just saying that Pathfinders has a sheet called x, and Towns Funds called y, and they are exclusively owned by the fund. That's fine for now as long as we really do move away from spreadsheets for future funds 🤞

This check is really only for TF vs. other funds as all other funds should now use the same sheet, and a separate fund check should catch this one. Only an issue with TF because the different tab names were causing a KeyError.


Update Polars guide with latest SQL improvements

@ritchie46 @alexander-beedie
here is the PR updating the Polars guide with the latest improvements on SQL (https://github.com/pola-rs/polars/pull/8749)
any thoughts?

Looking like a nice improvement! (Just read through the diff).
Though I would like to register my objections about anyone over 30 being thrown into the "old people" table 🤣  "...table called older_people based on a SELECT statement that selects all rows from the my_table DataFrame where the age column is greater than 30."

@alexander-beedie I didn't even notice that as it was already there. I have been old for some time based on that table
I can change it to wiser_people if that's better :)

I have been old for some time based on that table

You & me both then...😆

Thanks a lot @lucazanna 🙌

@ritchie46 if you are ok with it, I will prepare next a section on the Polars CLI

@ritchie46 if you are ok with it, I will prepare next a section on the Polars CLI

Please.. :)


eas-cli not working on Bitbucket Pipelines

Build/Submit details page URL
No response
Summary
My Pipeline runs the following command:
npx eas update --platform=all --auto --branch=develop
But it does not seem to work which seems weird because another pipeline works with eas build and that does work.
Is eas update even available for CI usage?
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 12.5
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.2/bin/yarn
npm: 8.17.0 - ~/.nvm/versions/node/v16.13.2/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 14.0/14A309 - /usr/bin/xcodebuild
npmPackages:
expo: ^46.0.10 => 46.0.13
react: 18.0.0 => 18.0.0
react-dom: 18.0.0 => 18.0.0
react-native: 0.69.5 => 0.69.5
react-native-web: ~0.18.7 => 0.18.9
npmGlobalPackages:
eas-cli: 2.1.0
expo-cli: 6.0.5
Expo Workflow: managed
Error output
ERR! could not determine executable to run
Reproducible demo or steps to reproduce from a blank project
Not available.

it should have been npx eas-cli


Missing Checkbox PropertyFilter + can't set property name

Hi,
I found that the checkbox entry was missing in notion.api.v1.model.common. Adding
@SerializedName("checkbox") Checkbox("checkbox");

should solve this part of the issue.
Also I can't found how to set the name of the property :
My checkbox is called Done in notion
if i managed to make the following code where i can't set the property name
println(notionClient.queryDatabase(databaseId = database_id, filter = PropertyFilter(PropertyType.Checkbox (Missing as of now), checkbox = CheckboxFilter("true"))))

I end wit this error ; notion.api.v1.exception.NotionAPIError: Got an error from Notion (status: 400, code: validation_error, message: Could not find property with name or id: checkbox)
I suppose it take the property type as name
Additionnal thing but not important :
CheckboxFilter equals take a String => Shouldn't it be a bool ?
Thanks
Denis

Thanks! Fixed

The fix is included in v0.1.15

Does this add the ability to set the property name?

@DenisD3D Thanks for your reply. As the unit tests use "title" for it, the tests haven't detect my mistakes on the property type 🤦 I just released v0.1.16 including the fix for it (the jar files will be available in the Maven Central repos soon).


Bootstrap and sass

Seems correct. You have added the links in your index.html , made a build and watch command in the package.json.