[GH-15803] fix: migrate this.ref.dotMenu to React.createRef

Summary

Migrate this.refs.dotMenu to React.createRef
Ticket Link

Jira ticket: https://mattermost.atlassian.net/browse/MM-29314
Fixes https://github.com/mattermost/mattermost-server/issues/15803
Related Pull Requests

None
Screenshots

None

Hello @jufab,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

/update-branch

No Problem.
It's done in this commit.

/update-branch

In test queue.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

Thanks for your contribution, @jufab! QA has been busy with hacktoberfest, but will get to your PR soon!

/update-branch

hi @jufab sorry it is taking so long, I'm afraid there is a ton of contributions in hacktoberfest and it takes longer than usual. Unfortunately this also meant that we now have a conflict in your contribution, can you fix it so the process can continue?

@Willyfrog No problem, I understand!
It's done 😉

Removing setup cloud server label for maintenance purposes. Feel free to reapply if needed :)

Hey all, I will remove the tag Setup Cloud Test Server for maintenance reasons. Feel free to re-add it when you need it. Thank you

/update-branch

Error trying to update the PR.
Please do it manually.

@Willyfrog are you okay if I assign to you to help with merging?

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

seems like auto-merge is not working :/


Switch docs to suggest 'test' path instead of 'tests'.

Just noticed that basically all of ROS upstream uses a test dir, but this doc suggests tests, which has led to an inconsistency in our internal packages, with some following the documented example and others following upstream.
Note that this change is also consistent with the generated CMakeLists.txt template:
https://github.com/ros-infrastructure/catkin_pkg/blob/e4b9bcd884b5f7fb9e6ddcfaa976aa3c72c22654/src/catkin_pkg/templates/CMakeLists.txt.in#L192-L193

Thanks for the path. Singular makes indeed more sense.


wat: noticed breaking changes in bump from version 1.0.71 to 1.0.72

This is mostly just an FYI, but in the clarity-wasm team, we noticed that when our wat crate upgraded from 1.0.71 to 1.0.72, WAT code that was previously compiling just fine started reporting errors. The two cases that showed up were

if expressions without a then (these seemed to be optional before)
Use of i32.wrap_i64 on the result of select was okay before, but now we needed to move the i32.wrap_i64 onto each of the expressions instead

These changes are totally reasonable, but it would be great if this kind of change triggered at least a minor version bump and not just a patch bump.

Thanks for the report! These are indeed intended changes:

https://github.com/bytecodealliance/wasm-tools/issues/1164 was handled in https://github.com/bytecodealliance/wasm-tools/pull/1184
https://github.com/bytecodealliance/wasm-tools/issues/1213 was fixed in https://github.com/bytecodealliance/wasm-tools/pull/1215

I've written down a bit about stability a long time ago, but that's albeit in a pretty obscure location and not prominently written.
That being said it's intentional that major version bumps are not used to communicate breaking changes to the text format. Such changes are theoretically, and practically so far, pretty rare. If you need any help updating I can try to help out though

Got it - make sense. Thanks for the quick response and the offer for help! We're in good shape now.


v-memo doesn't work with v-if

Vue version
3.2.38
Link to minimal reproduction
https://sfc.vuejs.org/#eNp9UEtuwjAQvcrUG4ogcVU2FQ0RPUfdRTATkoI/sp2wiHL3jpMU0VRiN+/N+4ymYx/Wpm2DbMsyL11tA3gMjc2FrpU1LkAHDkvooXRGwYKki3ehhZZGe9JW5gq7qHgOrsHlLy9No8O0eFmSIeNjOuUSCKjspQhICCDzttDQJnW5EywGCkZIoTKEP4ekL8HyrhvGvqcoMuQweA9NCEbDXl5qeZ781Ps05uSyKvQJhzMzPmrHzrlvyF6tomWcbnLqyfjtYLZm418SVdj02xtNn+tipJgWXrAtDEzk6F8RC1aFYP2W80bb8ymVRvE97bijslphcjRqv0lf080bP9Y+3PMpepUcnLl6dNQo2PounBPZoksc6iM6dA/LZto/hbPdv9LY2Qvds/4HLEzDqw==
Steps to reproduce

click the button "count++"
click the button "change show"
click the button "change show"
click the button "count++"

What is expected?

the count display in the  will increase
the  will remove
the  will show
the count display in the  will increase

What is actually happening?

the count display in the  will increase
the  will remove
the  will show
the count display in the  will NOT increase

System Info
window 10
vue 3.2.38

Any additional comments?
No response

for now, v-memo does not work with v-show and v-if.

workaround: use v-show instead.
  {{count}}


Update quickstart-create-access-environments.md

Removed unnecessary element in command

Learn Build status updates of commit 91498dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/deployment-environments/quickstart-create-access-environments.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@RoseHJM,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for your contribution @wi5nia, we appreciate you helping to improve the documentation!
#sign-off


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/486 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 5bb8de7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Ignore commented out tests

At the moment, tasty-discover ignores tests that have been commented out using --, e.g.:
-- test_Repro :: TestTree
-- test_Repro =
--   testCase do
--      ...

However, if I comment out the test using {- -}, tasty-discover will still find the test, include it in the tree, but then fail to compile:
{-

test_Repro :: TestTree
test_Repro =
  testCase do
     ...

-}

/home/dc/dev/demo/test/Tree.hs:91:34: error:
    Not in scope: ‘Demo.test_Repro’
    Module ‘Demo’ does not export ‘test_Repro’.

This seems to stem from the fact that tasty-discover simply reads the entire file and looks for lines starting with one of the supported prefixes (e.g. test_).
Another manifestation of this issue is when a test is wrapped in a CPP-style #if. For example, a test might not work on Windows, so a user might wrap it in #if !defined(mingw32_HOST_OS).
A more robust solution might be to use ghc-lib-parser or ghc-exactprint to parse the file and then extract top-level definitions that start with one of the supported prefixes.
I'd be willing to submit a PR, if the maintainers agree with the change.

Sorry, for getting back to you late.  Yes.  I accept PRs.  😁


RadSideDrawer seperation

I have successfully implemented RadSideDrawer into my app. However, currently, I am implementing it on every HTML view separately. I have 5 pages, they all have the full RadSideDrawer code in the view and component.
Is there a way of segregating this so I don't have to copy and paste the code onto every new page I create?
Thanks

Yes there is, I followed this article, and could do it without any issues
https://codedump.io/share/S9LgvPW6tgA8/1/nativescript---make-telerik-sidedrawer-in-all-views


Should pass route optional args too

Should be able to handle this:
get '/foo', :agent => /Songbird (\d\.\d)[\d\/]*?/ do
  "You're using Songbird version #{params['agent'][0]}"
end

closed in #5


is_ prefix?

Hi, first of thank you for the great library.  I have a question, so I know the lib generates things like User.male from gender_cd.  Would it be possible/easy to make it so it adds helpers like User.is_male? ?
Many thanks

Hi, glad you find simple_enum useful :)
It is possible to provide a prefix, or disable the generation of any shortcut methods:
# option 1, using :prefix => true
as_enum :gender, [:male, :female], :prefix => true

# allows to do:
user.gender_male?
user.gender_female!

as an alternative a custom string can be passed in as prefix
# option 2, using custom prefix e.g. "is"
as_enum :gender, [:male, :female], :prefix => "is"

# then use as
user.is_male?
user.is_female!

Personally I would not recommend to use a prefix like is and rather stick with a something like gender.

@lwe Works like a charm.... thank you for adding that in :)

you're welcome :)


[PDI-7538] S3 Input/Output Steps does not respect IAM security rules

In the use case where a user only has permissions on a single bucket and lacks permissions to list all existing buckets the S3 CSV input step would fail to read the specified file.
While it isn't possible to browse and select the bucket that contains the file to read, the user must be able to type the bucket name and even the filename to process.
Because of this, we can't use the listBuckets() method and then filter the results and instead should use the doesBucketExistV2( bucketName ) method.
@pentaho/tatooine and @rmansoor, please review and merge.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/s3csvinput/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/s3csvinput/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/s3csvinput/core/src/main/java/org/pentaho/di/trans/steps/s3csvinput/S3ObjectsProvider.java
  plugins/s3csvinput/core/src/test/java/org/pentaho/di/trans/steps/s3csvinput/S3ObjectsProviderTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.trans.steps.s3csvinput.S3ObjectsProvider

Instruction Change: -0.3% :small_red_triangle_down:


Organize documentation resources

thanks i agree that's much better, just need to fix the tests.

thank you ben!

thanks @jaroslawmalekcodete for fixing the tests for me!


Added Deserialize and compatible Serialize

To transport SOAP objects over other transport mechanisms,
such as oslo.messaging, we need a representation,
which allows us to reconstruct (de-serialize) the
serialized object. This is commonly a dict, as done in
the pre-existing serialize_object function.
This change improves the function by:

Not serializing empty defaults making the result
less verbose
Serialize the type by adding the "class" field to
the dict, in cases of fields being of derived types
of the default

For compatibility reasons, the latter is only active
when opting-in.
Additionally, the deserialize_object has been added,
which takes the dict generated by serialize_object
and creates a SOAP object out of it
Change-Id: Ie76b1e6940b5022563ce91d5692df589573704d0

Essentially what we already have in Nova.
https://github.com/sapcc/nova/blob/stable/rocky-m3/nova/virt/vmwareapi/vim_util.py#L153-L238


Remove don't work with custom template

If I try to remove an item in custom template, it doesn't work.
(It is also the case in the demo.)

True, that's a little outdates, I will update it :) (it will also need some tweak in the code as I need to pass the index to the template context)

@sancaruso try this:
        <template let-item="item">

                    {{ item.value }}

        </template>

Notice the inclusion of input.items.indexOf(item)

Thanks @tonysparks, that should be good as well. I'll add index to the template context to ease this soon :)

The new version adds index as a variable in the template's context :)


Trivial auto-generated theorems and tooling to compute transitive reductions/closures

This change includes ~15 thousand theorems, that prove a total of 4.2 million total derived implications (~20% of the total, e.g. 4694 ^ 2). I include scripts to calculate the transitive reduction and closure of a set of implications, to help future devs similarly submit minimal changes.

Note that there is also equational_theories/SimpleRewrites/src/find_redundant.py for transitive reduction

I mentioned it on Zulip, but it should also go here, one thing I did not do here, is delete other theorems subsumed by these implications, e.g. in Subgraph.lean or other auto-generated implications. Should I? I'm not sure if that's kosher or desirable. Input is welcome.

Note that there is also equational_theories/SimpleRewrites/src/find_redundant.py for transitive reduction

I am trying to run it for my base set of implications (1 million) and it hasn't finished after 5 minutes. (My script is also pretty slow tbf, it takes just under a minute.) I had to optimize my script so that it finished relatively quickly by performing condensing/uncondensing that I don't see here?

I mentioned it on Zulip, but it should also go here, one thing I did not do here, is delete other theorems subsumed by these implications, e.g. in Subgraph.lean or other auto-generated implications. Should I? I'm not sure if that's kosher or desirable. Input is welcome.

e.g. this change subsumes Generated/Singleton.lean, but not Generated/Constant.lean or SimpleRewrites. In Subgraph.lean, it subsumes 43/46 implications.

Thanks!  I just added a chapter to the blueprint at https://github.com/teorth/equational_theories/blob/main/blueprint/src/chapter/trivial_auto.tex , if at some point you could describe your methodology and compare the data set with other generated sets, that would be great.


Sync SharePoint Columns to SharePoint Folders

Show and Sync SharePoint Columns for folders that have been synced with SharePoint.

Thanks for the feedback. Please make a new issue following the issue templates.


Adding a few lines to frontend .gitignore files.

This PR just adds a couple of quality of life improvements for frontend development, by adding three lines to each of the relevant .gitignore files.

Having '/generated' as well as '/generated/' lets you use a symlink to your nix store (or whatever) instead of a directory with a copy of the generated PureScript.
91394e9 changed the setup from Yarn to NPM. Adding '/yarn.lock' (and restoring '/yarn-error.log') lets you carry on using Yarn locally if you want to. Then everybody's happy. 😄

These folders all look pretty generic - I think we could probably stuff most of this into the root gitignore with some wildcard patterns and get rid of the duplication? e.g. put **/node_modules/ in the root .gitignore.

These folders all look pretty generic - I think we could probably stuff most of this into the root gitignore with some wildcard patterns and get rid of the duplication? e.g. put **/node_modules/ in the root .gitignore.

Good point @michaelpj. Does anyone know if any of these aren't generic? I'd be tempted to just put them all in the root .gitignore and be done with it. Similarly, I've just noticed the root .gitignore file includes marlowe-playground-server/playground.yaml, but plutus-playground-client/playground.yaml is included in the plutus-playground-client/.gitignore file instead.

Good point @michaelpj. Does anyone know if any of these aren't generic? I'd be tempted to just put them all in the root .gitignore and be done with it. Similarly, I've just noticed the root .gitignore file includes marlowe-playground-server/playground.yaml, but plutus-playground-client/playground.yaml is included in the plutus-playground-client/.gitignore file instead.

Similarly, I've just noticed the root .gitignore file includes marlowe-playground-server/playground.yaml, but plutus-playground-client/playground.yaml is included in the plutus-playground-client/.gitignore file instead.

Seems like an argument for consolidating it!
I can see the argument for directory-specific gitignore files if it's really stuff that's only specific to that folder, otherwise you get lots of sections in the root gitignore. But in this case the ability to generalize seems nice.

Similarly, I've just noticed the root .gitignore file includes marlowe-playground-server/playground.yaml, but plutus-playground-client/playground.yaml is included in the plutus-playground-client/.gitignore file instead.

Seems like an argument for consolidating it!
I can see the argument for directory-specific gitignore files if it's really stuff that's only specific to that folder, otherwise you get lots of sections in the root gitignore. But in this case the ability to generalize seems nice.

Let me know what you all think of this then please. There appeared to be a few redundancies once I started looking.

Let me know what you all think of this then please. There appeared to be a few redundancies once I started looking.

Let me know what you all think of this then please. There appeared to be a few redundancies once I started looking.

Let me know what you all think of this then please. There appeared to be a few redundancies once I started looking.

I think until things get out of hand, a single gitignore makes more sense

I think until things get out of hand, a single gitignore makes more sense

Does someone know how to get this past CI? I'm afraid I don't. It's complaining that the .gitignore files I've removed don't exist.

Does someone know how to get this past CI? I'm afraid I don't. It's complaining that the .gitignore files I've removed don't exist.

Ah, I think this was @gilligan trying to be smart and selectively filter the sources per-directory. I think we should just pass the filtered source in, tbh. Give me a sec and I'll take a look.

Ah, I think this was @gilligan trying to be smart and selectively filter the sources per-directory. I think we should just pass the filtered source in, tbh. Give me a sec and I'll take a look.

Hm, not quite as obvious as I'd hoped. Still thinking.

Hm, not quite as obvious as I'd hoped. Still thinking.

nix-gitignore doesn't read .gitignores in parent directories.
Passing in a filtered source for the root and then extending the path to get a subdirectory doesn't seem to work.
hercules-ci/gitignore.nix does read gitignores in parent directories, but it slows down our eval atm (I already tried it in https://github.com/input-output-hk/plutus/pull/2512)

I'm having another look at gitignore.nix, in the mean time I suggest just putting the directory-specific ones back to unblock this.

nix-gitignore doesn't read .gitignores in parent directories.
Passing in a filtered source for the root and then extending the path to get a subdirectory doesn't seem to work.
hercules-ci/gitignore.nix does read gitignores in parent directories, but it slows down our eval atm (I already tried it in https://github.com/input-output-hk/plutus/pull/2512)

I'm having another look at gitignore.nix, in the mean time I suggest just putting the directory-specific ones back to unblock this.

Ok, thanks Michael. I'll do that for now, and if you think of something on the CI issue we can remove them later.

Ok, thanks Michael. I'll do that for now, and if you think of something on the CI issue we can remove them later.


My custom osiris randomly crashing

my custom version of osiris randomly crashing my game
but i dont know why.
I'm using Win10, 720x480 res (because my computer is super potato)
and my source code is here
What i changed on original osiris:

Add no zoom Khajiitos's work
Add this, but only bullet tracer beam & draw multipoints
some crashing bug fix & remove anti-aim & rename some features but only gui showing (not function name)

is there incorrect code?

my custom version of osiris randomly crashing my game
but i dont know why.
I'm using Win10, 720x480 res (because my computer is super potato)
and my source code is here
What i changed on original osiris:

Add no zoom Khajiitos's work
Add this, but only bullet tracer beam & draw multipoints
some crashing bug fix & remove anti-aim & rename some features but only gui showing (not function name)

is there incorrect code?

Some peoples have problems with bullet tracer, idk why.

lol i just changed my game resolution, and it fixed. XDD


Reduce padding buffer size in cbc mode

Description
Hello,
I am currently in the process of including mbedtls into a really small embedded system. As I was looking to reduce my memory footprint, I noticed that there is some optimisations possibles in the way CBC padding is allocated and exploited.
I understand that TLS allowes CBC padding up to 256 bytes per message, but currently mbedtls only pad to round to the next block instead :

branch baremetal
v2.18
v2.24.0

However, the size allocated to accommodate the padding is still set to 256 bytes, in and out ( branch baremetal ).
This pull request contains two commits :

The first one only decrease the buffer size of outgoing messages to 16, which I believe is the biggest block size currently in use. I noticed that some blocksize are #define as constant, but not all of them so that's why I didn't use one of them. I believe this modification doesn't alter the ABI, as it is strictly internal.
The second one introduce the configuration option MBEDTLS_SSL_CONF_PADDING_IN allowing one to set the buffer size of ingoing messages to a custom value. It is however not TLS compliant, so be careful to be in control of both ends if you want to change it.

Status
I tested both of these modifications with success on my little system. It allowed me to reduce my memory footprint by almost 500 bytes, which is about 20% of reduction ! But as my understanding of the codebase is far from perfect, all comments are welcomed, I might have missed something.
Additional comments
My commits are not signed-of as the contributing guidelines mandate, but I am happy to wave all my right on this work to anyone if this is necessary :)
Thank you,
G4E.

Hi G4E,
Do you really need CBC? CBC in TLS is somewhat deprecated due to several attacks such as Lucky Thirteen. Using modern cipher suites based on GCM or CCM is more secure, and is likely to save both memory and code size. Between GCM and CCM, CCM tends to be preferred in the embedded world because it requires less code size. They're close on performance, with a slight win for GCM unless you have AES acceleration but no GCM-specific acceleration in which case CCM wins. (There's also Chacha/poly, which is faster if you don't have AES acceleration, but it's less widely supported in TLS 1.2.)
If we accept this patch, we'd need to carefully review the security implications. The countermeasures against Lucky Thirteen are somewhat delicate and I wouldn't swear that they work with a different value of the maximum padding.
In addition:

We need signed-off-by lines in the patch. Sorry, otherwise we don't have permission to use your code.
The patch would need to pass CI. Several jobs are failing.
The new configuration option must be declared and documented in config.h. (That's one of the CI failures.)
There should be a test component in tests/scripts/all.sh that exercises the new option.

L502568B-en_US

Hello Gilles,
Thank you very much for your very detailed answered. You are absolutely right, we don't require AES-CBC. We chose AES-CCM8 for our main cipher suite, but we wanted to include AES-CBC as a backup. The problem is when a cipher suite with CBC is enabled, and therefore CIPHER_CBC, the 256 bytes are allocated in the in/out buffer no matter the cipher suite actually in use.
The best way to handle that would be to dynamically allocate the buffer to match the cipher suite in use, but from what I saw the buffer is allocated before the cipher suite negotiation.
I can rework the pull request, add the missing tests and the documentation if you think it would be an useful addition to the library.
For the failing tests, they were already failing before my modifications on my end ?
I'll make a diff of the tests before/after to be sure.
Thanks,
G4E.

My personal opinion is that this is a high-risk, low-reward feature. It's high-risk because it may have subtle security implications due to the interaction with Lucky 13 countermeasures, and low-reward because new designs should not use CBC ciphersuites. This doesn't mean that we'd reject this feature, just that we're likely to give it low priority, and that it needs special attention during review.
I just realized that you're submitting this PR to the baremetal branch. I'm a gatekeeper for Mbed TLS's “main” branch but not for the baremetal branch. The gatekeepers for baremetal may have a different opinion.
The CI failure in check_names is because MBEDTLS_SSL_CONF_PADDING_IN isn't declared in config.h. I don't know about the other failure on Travis: that other failure didn't happen on Jenkins.

I am closing this pull request because the baremetal branch is no longer maintained in this repository. If it is still relevant, please open a new pull request in https://github.com/PelionIoT/pelion-crypto .


Internet explorer

Hi,
Thank you for coding such a great gantt charting tool!
Is there any way of / or a fix for it working on Internet explorer?
Nick

Any ideas?

Hi,
Wanted to post an update for others that may be wanting / needing Frappe gantt to work in Internet explorer 9 to 11.
We used the babeljs polyfill script to resolve the issue.
https://babeljs.io/docs/usage/polyfill/
This now fully works as before and also on the above version of IE 9.
Hope this help.
Nick

@nickwilliams999 - were you able to get the custom_popup_html to bind & fire in IE 11? If so I'd love to know how. I have the chart rendering just fine in IE, and the popups work for me in Opera and Chrome, but not IE.

Hi Bryan-c-oconnell,
We ended up not using the custom_popup_html as we made the whole of the gantt chart read-only.

Drat! Ok, thanks for the reply. I definitely need the popups ...

Let me know if you have any luck with it bryan-c-oconnell

@nickwilliams999 Good to hear that it worked for you!
Unfortunately, I don't plan to support IE, so if you have found methods to make it work, please add it to the readme and send a PR 😄


Add driver flag to precompile Swift-compatible explicit Clang modules.

Some additional context/discussion can be found in this Swift Forums thread.
This change adds two flags to the Swift driver:

-emit-pcm, which takes as input a module map and generates an explicit precompiled module using a Clang compiler instance from Swift's ClangImporter.
-dump-pcm, which takes as input a .pcm file generated by the Swift compiler (either by -emit-pcm, or one from the implicit module cache) and prints info about it as a debugging aid (equivalent to clang -module-file-info)

Such a .pcm file can be passed to swiftc using -Xcc -fmodule-file=path/to/module.pcm and imported like any other C/Objective-C module.
Example usage
swiftc -emit-pcm -module-name TheNameOfAModuleInTheModuleMap \
  -target arm64-apple-ios11.0.0 \
  -o MyModule.pcm \
  -Xcc -DADDITIONAL_CLANG_FLAGS \
  path/to/module.modulemap

swiftc -dump-pcm MyModule.pcm

Motivation
When distributing Swift builds consisting of large numbers of Objective-C and Swift modules remotely with build systems like Bazel, we can't rely on the implicit module cache to reduce repeated work—the cache won't be the same from machine to machine, and it's not possible to share it because absolute paths to the workspaces will be different (and those paths are written into the modules).
This means that each swiftc job's ClangImporter must redo the work of parsing the C/Objective-C headers used by a Swift module, which greatly slows down our remote builds. For dependency graphs with large amounts of Objective-C, we a significant amount of time reported by the compiler spent in Name Binding, and file system traces indicate that much of that is processing headers.
Instead, we'd like to explicitly precompile those C modules and propagate the .pcm artifacts as part of the build graph, thus doing the work only once. Since precompiled modules are not binary-compatible across different versions of Clang or across invocations where the non-benign invocation options differ, the only stable way to make a .pcm that is compatible with Swift is to extend swiftc to have its own ClangImporter instance do it.

cc @DougGregor, could you add assign a reviewer to this please? Thanks!

This seems to be working for some basic modules (like the ones in the test case in the PR), but I'm seeing some odd behavior (an assertion failure) when I try to build and then consume explicit modules for some of the Apple SDK system frameworks/modules. (We need to turn on -fno-implicit-modules so that the module cache doesn't affect the content of the modules, meaning tht even the system frameworks have to be explicit.)
In order to do this, I have the following modules that I build explicitly with -emit-pcm invocations:

_Builtin_stddef_max_align_t (defined in <clang-resource-dir>/include/module.modulemap)
Darwin (defined in $SDKROOT/usr/include/module.modulemap, depends on [_Builtin_stddef_max_align_t])
ObjectiveC (defined in $SDKROOT/usr/include/objc/module.modulemap, depends on [_Builtin_stddef_max_align_t, Darwin])
os_object (defined in $SDKROOT/usr/include/module.modulemap, depends on [_Builtin_stddef_max_align_t, Darwin, ObjectiveC])
Dispatch (defined in $SDKROOT/usr/include/dispatch/module.modulemap, depends on [_Builtin_stddef_max_align_t, Darwin, ObjectiveC, os_object])

Building Dispatch is where things go south. I pass all the dependencies to using swiftc -emit-pcm -Xcc -fmodule-file=/path/to/module.pcm, and I get a crash like this:
Assertion failed: (D == Ptr && "Didn't find this decl on its identifier's chain!"), function RemoveDecl, file /REDACTED/Swift/llvm/tools/clang/lib/Sema/IdentifierResolver.cpp, line 221.

0  swift                    0x00000001116fc655 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1  swift                    0x00000001116fb945 llvm::sys::RunSignalHandlers() + 85
2  swift                    0x00000001116fcc38 SignalHandler(int) + 264
3  libsystem_platform.dylib 0x00007fff6f68eb5d _sigtramp + 29
4  swift                    0x00000001139ec06d cmark_strbuf__initbuf + 126920
5  libsystem_c.dylib        0x00007fff6f5486a6 abort + 127
6  libsystem_c.dylib        0x00007fff6f51120d basename_r + 0
7  swift                    0x0000000112476bb3 clang::IdentifierResolver::RemoveDecl(clang::NamedDecl*) (.cold.5) + 35
8  swift                    0x0000000110a6bc08 clang::IdentifierResolver::RemoveDecl(clang::NamedDecl*) + 232
9  swift                    0x000000011093de90 clang::ASTReader::pushExternalDeclIntoScope(clang::NamedDecl*, clang::DeclarationName) + 160
10 swift                    0x000000011093dc08 clang::ASTReader::InitializeSema(clang::Sema&) + 280
11 swift                    0x0000000110a9e595 clang::Sema::Initialize() + 85
12 swift                    0x00000001108cde55 clang::Parser::Initialize() + 4421
13 swift                    0x0000000110832f6d clang::ParseAST(clang::Sema&, bool, bool) + 381
14 swift                    0x00000001106da74e clang::FrontendAction::Execute() + 78
15 swift                    0x0000000110696c31 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) + 1473
16 swift                    0x000000010e9d11b0 swift::ClangImporter::emitPrecompiledModule(llvm::StringRef, llvm::StringRef, llvm::StringRef) + 1280
17 swift                    0x000000010defd669 performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&, swift::FrontendObserver*, swift::UnifiedStatsReporter*) + 1785
18 swift                    0x000000010defbfa2 swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 2978
19 swift                    0x000000010dea6388 main + 696
20 libdyld.dylib            0x00007fff6f4a33d5 start + 1
21 libdyld.dylib            0x000000000000001d start +<PHONE_NUMBER>

I threw some D->dump() calls inside RemoveDecl and saw some stuff about "undeserialized declarations", but I don't really have any idea what that means.
Then, I noticed the differing semantics of -fmodule-file=MODULE_NAME=path vs. -fmodule-file=path and decided to try the former form instead, and that succeeded (at least, it didn't crash).
This behavior happened both at HEAD, and in the 5.1 branch. I didn't observe it in an older prototype that I've been experimenting with internally, where I'm using sources that date back to sometime in June (I'll have to fish out more specific timestamps).
I don't think what I'm seeing is related to my PR specifically, but it's something I'd like to figure out before we're able to make real use of this. Is the behavior I'm observing (especially the difference between -fmodule-file forms) expected?

Following up to my previous comment, I observe the same behavior if I build and consume the same explicit modules using the standalone clang binary built from apple/llvm-project: crash when using -fmodule-file=path, success when using -fmodule-file=module_name=path, but not from clang distributed with Xcode 11.
So, at least the issue appears to be unrelated to this PR or to Swift/ClangImporter. I'll see if I can get the same behavior on upstream clang next.

Thanks Doug! If there's nothing else blocking, can you kick off the tests and merge if successful? I don't have permissions to do so.

@swift-ci please test


PackedByteArray.data corrupts if the PackedByteArray object goes out of scope earlier

Describe the bug
accessing data from
auto data = FileAccess.getFileAsBytes(path).data;
writeln(data[0 .. 1000]); // <-- potentially corrupt memory

breaks because it accesses corrupt / freed memory, since the PackedByteArray is destructed immediately on this call.
To access it correctly you need to do:
auto bytes = FileAccess.getFileAsBytes(path);
auto data = bytes.data;
writeln(data[0 .. 1000]);

the PackedByteArray object returned by FileAccess.getFileAsBytes(path) needs to stay alive as long as the .data pointer/buffer that you can read off it.
Expected behavior
A compiler error should occur when attempting to outlive variables (e.g. using dip1000 / return/scope attributes)
Plaform (please complete the following information):

OS: ArchLinux
Build target: Desktop Linux

fixed if caller is @safe now (even if the library isn't really usable with @safe code yet)


Android adaptive icons is cropped

Godot version:
3.3.2
OS/device including version:
Android 10 / Honor 9x
Issue description:
I tried various ways of getting the launcher icon to display right, but nothing seems to be working.
This is the icon I want to set:

I configured the icon and separated foreground background into own pngs and configured it in the export options.
But no matter what I do, the icon always looks like this in my launcher:

The workaround described here (https://godotengine.org/qa/60477/godot-3-2-android-exported-icon-is-cropped) by JordanMotta is also not working for me, as it produces the following error during export:

Execution failed for task ':processReleaseManifest'.

Manifest merger failed : Attribute application@icon value=(@mipmap/icon) from AndroidManifest.xml:31:210-244
is also present at AndroidManifest.xml:31:210-244 value=(@mipmap/icon_launch).
Suggestion: add 'tools:replace="android:icon"' to  element at AndroidManifest.xml:16:5-25:19 to override.

Adding tools:replace="android:icon didn't do the trick sadly, same error
It was working for me using another app in Godot 3.2
Steps to reproduce:

Configure an Icon for android export

https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive
https://medium.com/google-design/designing-adaptive-icons-515af294c783
you need to make the penguin image much smaller.
here are several templates.
https://developer.android.com/google-play/resources/icon-design-specifications#download_design_templates_resources

Closing per @volzhs's comment.


chore: configure Metro to consume source directly

This will allow developers to modify the TypeScript code and see changes without having to run tsc --watch separately.

cc @chiaramooney @Titozzz

@chiaramooney or @Titozzz, can you merge this whenever you're ready? Thanks ❤


refactor and tidy dds::participant some more

Codecov Report

Merging #164 (11d6153) into master (c873705) will increase coverage by 0.03%.
The diff coverage is 0.00%.

:exclamation: Current head 11d6153 differs from pull request most recent head 59e2c14. Consider uploading reports for the commit 59e2c14 to get more accurate results

@@            Coverage Diff             @@
##           master     #164      +/-   ##
==========================================
+ Coverage   70.47%   70.50%   +0.03%
==========================================
  Files          88       88
  Lines        8006     8002       -4
==========================================
  Hits         5642     5642
+ Misses       2364     2360       -4

Impacted Files
Coverage Δ

src/dds/participant.rs
77.12% <0.00%> (+0.81%)
:arrow_up:

Continue to review full report at Codecov.

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


Updated the Design Section in DG

updated the design section in DG
Resolve #293

Codecov Report

Merging #294 (0f0c0b0) into master (79a8da4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #294   +/-   ##
=========================================
  Coverage     83.88%   83.88%
  Complexity     1126     1126
=========================================
  Files           125      125
  Lines          3028     3028
  Branches        410      410
=========================================
  Hits           2540     2540
  Misses          393      393
  Partials         95       95

Continue to review full report at Codecov.

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


docs: Update hermes.md gradle.properties folder

fix wrong folder to gradle.properties

Thanks for the fix @ParagonVirtuoso
Can I ask you to accept the CLA so we can merge this?
Also could you backport this to the 0.71 docs?

Good morning @cortinico , I accepted the CLA but I'm waiting for verification again or validation.

CLA is good now 👍 could you apply the same change to the 0.71 docs?


ci: Bazel builds use .cloudcxxrc

Sometimes we want to run the build scripts on our workstations, but we are only interested in storage, or pubsub, or spanner. We can do this for CMake-builds using .cloudcxxrc and the development.sh build. With this change any Bazel-based build can be configured to compile a subset of the targets.

This change is

Observation: I think all integration tests will run:

Yes.  I fixed that.  Now it skips (maybe) a few more tests than it should, but all the important ones are included.

Yes. I fixed that.

Nice, thanks.


Core

Pull Request Test Coverage Report for Build 25

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.612%

Totals

Change from base Build 22:
0.0%

Covered Lines:
122

Relevant Lines:
143

💛  - Coveralls


WHAMR!: sep_reverb_noisy 1dB lower than the reported performance

❓ Questions and Help
What is your question?
Hi,
I am trying task of both separation and denoise on WHAMR!, but my SI-SDR is about 3.94dB, 1dB lower than that in README.
Could you please upload the log so that I can check this by myself ?
Thanks a lot !

Can you add you're training config please? I'll look for the log today.

Thanks ! This is my config:
data:
mode: min
nondefault_nsrc: null
sample_rate: 8000
task: sep_reverb_noisy
train dir: data/wav8k/min/tr
valid dir: data/wav8k/min/cv
filterbank:
kernel size: 40
n_filters: 512
stride: 20
main_args:
exp_dir: exp/train_tasnet_sep_reverb_noisy_8kmin_db50b168
help: null
masknet:
dropout: 0.3
n_layers: 4
n_src: 2
n_units: 600
optim:
lr: 0.001
optimizer: adam
weight_decay: 1.0e-05
training:
batch size: 32
early_stoping: true
epochs: 200
half_lr: true
num_workers: 16
My final loss is about -3.98 (SI-SNR)

Here are the log files : logs.tar.gz
Here is the conf
data:
  mode: min
  nondefault_nsrc: null
  sample_rate: 8000
  task: sep_reverb_noisy
  train_dir: data/wav8k/min/tr
  valid_dir: data/wav8k/min/cv
filterbank:
  kernel_size: 40
  n_filters: 512
  stride: 20
main_args:
  exp_dir: exp/train_tasnet_sep_reverb_noisy_plain_pl0.6/
  gpus: '-1'
  help: null
masknet:
  dropout: 0.3
  n_layers: 4
  n_src: 2
  n_units: 600
optim:
  lr: 0.001
  optimizer: adam
  weight_decay: 1.0e-05
positional arguments: {}
training:
  batch_size: 32
  early_stop: true
  epochs: 200
  half_lr: true
  num_workers: 4

In pytorch lightning 0.6.0, early stopping was broken so training didn't stop and the performance improved. Could you also try without early stopping to see if this is better please?
I need to make the patience higher IMO

The log is similar with mine. I think I can reproduce the results with more training epochs.
Thanks for your patience !

Could you share your log here please? I'm curious when the early stopping happens

Sure. I will download the log from the lab tomorrow

Sorry for late reply. This is my log.
train_tasnet_sep_reverb_noisy_8kmin_db50b168.tar.gz


File Paths on non windows platforms

fix up path generation on non windows platforms for modelgen.

Thanks a lot!


legal: understand to what extent we are affected by GDPR

Tracking issue. Even if we get minimal user details as a result of OAuth auth, we are likely to fall under GDPR. Understand what we need to do here pre-release.

Making this one of the first things we do post go-live.


Garbage collector problem

Garbage collector cannot delete textures from gpu memory when using this extension!
Is this a bug or is it normal?
If this is normal, can't the problem be fixed using WeakRef?

You arguably should not be counting on garbage collection for WebGL. As is says in the MDN article for WeakRef

Avoid where possible
Correct use of WeakRef takes careful thought, and it's best avoided if possible. It's also important to avoid relying on any specific behaviors not guaranteed by the specification. When, how, and whether garbage collection occurs is down to the implementation of any given JavaScript engine. Any behavior you observe in one engine may be different in another engine, in another version of the same engine, or even in a slightly different situation with the same version of the same engine. Garbage collection is a hard problem that JavaScript engine implementers are constantly refining and improving their solutions to.
Here are some specific points that the authors of the WeakRef proposal included in its explainer document:

Garbage collectors are complicated. If an application or library depends on GC cleaning up a WeakRef or calling a finalizer [cleanup callback] in a timely, predictable manner, it's likely to be disappointed: the cleanup may happen much later than expected, or not at all. Sources of variability include:

One object might be garbage-collected much sooner than another object, even if they become unreachable at the same time, e.g., due to generational collection.
Garbage collection work can be split up over time using incremental and concurrent techniques.
Various runtime heuristics can be used to balance memory usage, responsiveness.
The JavaScript engine may hold references to things which look like they are unreachable (e.g., in closures, or inline caches).
Different JavaScript engines may do these things differently, or the same engine may change its algorithms across versions.
Complex factors may lead to objects being held alive for unexpected amounts of time, such as use with certain APIs.

On top of all those reasons it's even worse with WebGL. AFAIK no JavaScript engine has any idea of the memory used by WebGL resources. In other words, Assume you have 150meg free of VRAM. If you allocate a 100meg texture, from JavaScript's POV all you've done is allocate a few bytes to track the the WebGL resource. The JavaScript engine has no idea of the 100meg if you've allocated in VRAM. If you then lose the reference and immediately allocate another 100meg texture the JavaScript engine has no idea it should stop the world and delete your unreferenced 100meg texture so that there's room to allocate a new one. Instead you'll likely just get an OUT_OF_MEMORY error from WebGL or you'll lose the WebGL context. Conversely if you gl.deleteTexture the texture it should work you'd have memory to allocate the new texture.
I really don't want to encourage bad practices via this library. This library requires you to delete your WebGL objects which is the right thing to do and it will report resource counts encouraging you to manually delete the objects.

Just as a test I wrote some code that allocated a 4Meg WebGL texture and watched for it to be garbage collected using WeakRef. On Safari it was collected 4 seconds later. On Firefox and Chrome it was never collected (well, I stopped waiting after 2 minutes). Note: I was not allocating more things, well, expect a new Promise and a new setTimeout event, both of which are allocations.
As another test I tried creating a Canvas and waiting to see when it was collected. On Safari it was collected in ~4 seconds. On Firefox ~9. On Chrome it was ~32 seconds. In this case, every second I created a new canvas and inserted in into the body of the document.
When I removed the creation of another canvas every second it was ~4 seconds on Safari, ~9 on Firefox, stop waiting after 8 minutes in Chrome
Anyway, this is just all evidence of the warnings above.

Also, just for fun, I tried implementing it. I couldn't get Chrome nor Firefox to garbage collect WebGL objects so there's no way to test 😅
But, also, unless there's some other way to implement it I don't know, I'm required to keep an array of all WeakRefs to every object and scan it (slow) because you don't get directly told when an object is collected, you can just check if it was. So, when someone calls ext.getMemoryInfo() then inside that
// pseudo code
for(const [ref, id] of arrayOfRefsToAllWebGLObjects) {
  if (!ref.deref()) {
    // This object was GCed. Remove its memory
    // Example: 1024x1024xRGBA texture is 4meg so lower the memory usage by 4meg
    // and remove it from the arrayOfRefsToAllWebGLObjects
  }
}

Maybe that's okay. It's just slow for a large project to go over that array. I guess if you're not calling ext.getMemoryInfo often it doesn't matter.
One more issue is that in order to work, webgl-memory would have to start tracking all attachments (see README on the fact that it doesn't). The reason is the browser can GC a WebGLBuffer, WebGLTexture, or WebGLRenderbuffer object but WebGL can still reference that object if it's attached to some other object. For example a buffer referenced in a vertex array or a texture referenced in a framebuffer
Here's an example (only works in Safari)
https://jsgist.org/?src=baa6464cd855205b42d7c24409f72475
The WebGLBuffer for the triangle is GCed but the triangle is still taking memory and still usable because it was attached to vertex array object. In order for WebGL-Memory to handle that it would require expanding it to track the state of all attachments and only record the freeing of the memory when the object is GCed by GL.
That's not to say it shouldn't be done. It's just more work than I'm willing to do at the moment.


[BUG] Network Service Mesh (NSM) example is not working

Describe the bug
NSM example is not working when cnf_setup is called. I see there few issues.

It is failing on:
Helm install error: Chart.yaml file is missing

I think that this issue is caused by incorrect release_name in cnf-testsuite.yml. Where is something weird:
release_name: nsm --set insecure=true.
I tried it to run it with just release_name: nsm and then new issues popped up.

Issues after fixed incorrect release_name and rerun of cnf_setup:

Helm installation failed
        Helm install error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1", unable to recognize "": no matches for kind  `"MutatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"]``
Which I think is caused by using a newer version of Kubernetes. But I tested it with v1.23.13, which is not one of the recent ones. So I suggest updating this nsm example to be able to work with newer versions of Kubernetes
To Reproduce
./cnf-testsuite cnf_setup cnf-config=example-cnfs/nsm/cnf-testsuite.yml
Expected behavior
CNF setup should pass without issues and nsm cnf has to be in running state.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.13", GitCommit:"592eca05be27f7d927d0b25cbb4241d75a9574bf", GitTreeState:"clean", BuildDate:"2022-10-12T10:57:16Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.13", GitCommit:"592eca05be27f7d927d0b25cbb4241d75a9574bf", GitTreeState:"clean", BuildDate:"2022-10-12T10:50:48Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
How will this be tested? aka Acceptance Criteria (optional)
Create new nsm cnf with cnf_setup command and it has to pass and correctly create new cnf.

I tried to create this nsm cnf on older kubernetes (v1.21.14) and with fixed that release_name and I had green results:


the keys is wrong

i also put the right key but incorrect

Not sure I understand but if this is still an issue, feel free to re-open.


Uploading very large unpublished sumstats dataset

Helen had contact with authors of an unpublished dataset and we had offered to upload it for them when the submission interface was ready. There are over 3000 files, I think around 1.5TB of data. Curators are not able to handle this volume of data, so we need another solution.
Data is here: https://open.win.ox.ac.uk/ukbiobank/big40/

This info from the website
3,935 files, one file per trait, containing: chr rsid pos a1 a2 beta se pval(-log10). The beta coefficient is in the direction of a2.
The download for trait 1 is:    release2/stats/0001.txt.gz
@

It looks like the files need to be formatted en masse, which is something that I can do/advise how to do with the new formatter. pvalues will need to be converted from -log - I will need to add an option to the formatter to enable this. Genome assembly appears to be GRCh37, but please confirm.
chr rsid pos a1 a2 beta se pval(-log10)
01 rs367896724 10177 A AC -0.001157 0.014236 0.029085
01 rs201106462 10352 T TA -0.0020071 0.014645 0.050126
01 rs534229142 10511 G A -0.08748 0.19528 0.18431
01 1:10616_CCGCCGTTGCAAAGGCGCGCCG_C 10616 CCGCCGTTGCAAAGGCGCGCCG C 0.073579 0.091994 0.37282
01 rs575272151 11008 C G -0.033773 0.024695 0.76589
01 rs544419019 11012 C G -0.033773 0.024695 0.76589
01 rs540538026 13110 G A 0.058805 0.033066 1.1229
01 rs62635286 13116 T G 0.014839 0.019169 0.35765
01 rs62028691 13118 A G 0.014839 0.019169 0.35765

Yes, GRCh37/hg19, and A2 effect allele

Completed submission template is here: GWASCatalog_template-BIG40.xlsx

After formatting the above looks like this:
chromosome	variant_id	base_pair_location	other_allele	effect_allele	beta	standard_error	neg_log10_p_value	odds_ratio	ci_lower	ci_upper	effect_allele_frequency	p_value
1	rs367896724	10177	A	AC	-0.001157	0.014236	0.029085	NA	NA	NA	NA	0.9352226147136065
1	rs201106462	10352	T	TA	-0.0020071	0.014645	0.050126	NA	NA	NA	NA	0.8909924008180644
1	rs534229142	10511	G	A	-0.08748	0.19528	0.18431	NA	NA	NA	NA	0.654169060596548
1	NA	10616	CCGCCGTTGCAAAGGCGCGCCG	C	0.073579	0.091994	0.37282	NA	NA	NA	NA	0.4238185877576885
1	rs575272151	11008	C	G	-0.033773	0.024695	0.76589	NA	NA	NA	NA	0.17143914810708835
1	rs544419019	11012	C	G	-0.033773	0.024695	0.76589	NA	NA	NA	NA	0.17143914810708835
1	rs540538026	13110	G	A	0.058805	0.033066	1.1229	NA	NA	NA	NA	0.07535290502354003
1	rs62635286	13116	T	G	0.014839	0.019169	0.35765	NA	NA	NA	NA	0.4388842542088914
1	rs62028691	13118	A	G	0.014839	0.019169	0.35765	NA	NA	NA	NA	0.4388842542088914

Please can you confirm this is correct and I will apply to all

@jdhayhurst formatting looks good to me

formatted, submitted and released on FTP


Nostrconnect uri timeout

i'm trying to follow the example in crates/nostr-signer/examples/nostr-connect-signer.rs and it does not work when using the nostrconnect uri
It hangs in this line
https://github.com/rust-nostr/nostr/blob/3d9ebbbe7fdf2fb27990b3ff83353f40c311027e/crates/nostr-sdk/examples/nostr-connect.rs#L28
You can scan the qrcode using amber if you have an android phone
Amber sends the ack response but this library never receives it
Using the bunker uri it works fine

Thanks, I'm going to investigate

I'm the original complainer 😂. I have a couple of tools where I try to use the nostrconnect URIs, so if you need help testing a fix LMK!

Should be fixed now. Let me know if you have issues

@greenart7c3 I tried with Amber and "ACK" message is now handled, but Amber crashes after successful connection :(

It closes the app when you accept an event so you dont need to go back to the app you are using

It closes the app when you accept an event so you dont need to go back to the app you are using

Ah ok. Weird, the connection success but Amber not receive the requests from the client. I thought was crashing and for this reason not replying. The p tag in the event is correct and the event is sent to the right relay.

Are you in the latest stable or the beta release? i think its the problem i solved in the beta release

Are you in the latest stable or the beta release? i think its the problem i solved in the beta release

I'm on v1.0.9

I can confirm everything is working now, thanks everyone!

Are you in the latest stable or the beta release? i think its the problem i solved in the beta release

Solved by changing the notification type from "Push notification" to "Direct connection".

Just published the patch for nostr-signer (v0.32.1):
cargo update -p nostr-signer

Just published the patch for nostr-signer (v0.32.1):
cargo update -p nostr-signer

Thanks already bumped. Damn, this was fast!


Update openedx/frontend-app-discussions to use the new combination of paragon+platform+build

https://github.com/openedx/frontend-app-discussions/pull/724
https://github.com/openedx/frontend-app-discussions/pull/723
https://github.com/openedx/frontend-app-discussions/pull/707


Folder Structuring

While seeing the repository I noticed that the structure of this folder is very bad and has to be improved.
The new structure of the folder:
Moksh
|
+-- Images
|  |
|  +-- All the images
|
+-- Sounds
|  |
|  +-- All the sounds
|
|
+-- CSS
|  |
|   +-- Contain all the CSS files
|
+-- HTML
|   |
|    +-- Container all the HTML Files
|
+-- Index.html
|
+-- Contributing.md file
Note: I would like to work on this issue. And I will make sure that all the internal links work correctly.

I am working on it


Added  html questions

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it.
We already a few similar questions on the alt attribute in both the accessibility and HTML quizzes so at this time we will not be accepting any more.
But we do encourage you to contribute in the future. 👍


Ieee802154 layer adaptation

The layer should have a function used something like State = Mod:init(Params) and all further call should look like State2 = Mod:fun(State, ...)

Could there be multiple mac layers ? Do they have to be restarted independently from the ieee802154 module ? I think I would rather have the Mac layer not be a process for now. And if it was it could probably just be linked to the ieeee802154 process ? In any case, network_sup sounds too generic a name for this.

the stop callback to be called terminate

For the stop/terminate of the gen_mac_layer I followed the same architecture as gen_server. stop is in the module and terminate is the callback


MumbleClient.users() not returning users online

MumbleClient#users() doesn't return the list of users currently online, rather all users that have been on the server when the client has been connected regardless if the user is offline or online.

Maybe add a MumbleClient.usersOnline() and MumbleClient.usersOffline() method as well as a property "online" to the user objects instead of changing the behaviour of this method?

Maybe add a MumbleClient.usersOnline() and MumbleClient.usersOffline() method as well as a property "online" to the user objects instead of changing the behaviour of this method?

Yes, this seems like the best solution instead of making breaking changes.

In terms of keeping the API clean and logical, I wouldn't consider this breaking change. The session IDs, etc. are wrong anyway for disconnected users. If the application needs to keep track of all the possible users, they should persist them somewhere.
.. and how did I miss the original issue posted October 18th? This completely went past me. Sorry for that!

(I'd be okay with usersOnline() and usersOffline() if users() returned -all- the registered users from the server. Even the ones who haven't logged on at all.)
Returning users the client has seen is just iffy.
(On the other hand: While fixing this, I think we should also include a method to retrieve all registered users in case the bot account has necessary permissions for that.)

While fixing this, I think we should also include a method to retrieve all registered users in case the bot account has necessary permissions for that.

Does a user require a special permission to view all registered users? I'm not seeing any ACL for that:

Not sure about that. Could be everyone can see them.

Hm, I went on a random server and I couldn't access registered users.

Could be the 'register user' permission affects it.


Make compute configurable

allow option to configure compute

Proposal: Instead of making AML compute configurable, I suggest removing it from this module all together. It is unlikely that any associated compute (AML compute instance, AML compute cluster, AKS, other, etc.) will be provisioned simultaneously with the workspace - even if the same person is provisioning both.
We will need to revisit what AML compute should look like in an AVM module or modules at a later date.
// @Nepomuceno @shanepeckham @vyta


Either a v4 tag or branch should be created or the README should be updated

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the issue has not already been raised

Issue
The README says to use @v4, but this does not exist.
jobs:
  ci:
    uses: fastify/workflows/.github/workflows/plugins-ci.yml@v4

See this failing run on fastify-flash for reference
https://github.com/fastify/fastify-flash/actions/runs/7835351308/workflow
Check failure on line 20 in .github/workflows/ci.yml

GitHub Actions
/ .github/workflows/ci.yml
Invalid workflow file
error parsing called workflow
".github/workflows/ci.yml"
-> "fastify/workflows/.github/workflows/plugins-ci.yml@v4"
: failed to fetch workflow: reference to workflow should be either a valid branch, tag, or commit

Thanks for the context @gurgunday. Would a PR to make the README reflect that be welcome?

Time is better spent getting Fastify v5 ready and shipped, and/or fixing the dependabot problem. It should not automatically update workflows with new major versions of this workflow.


The code block of the official website tutorial did not match the curly braces properly

It looked uncomfortable all night:<

send a PR?


fix: Closes #182 - update to mf_getuniquelibref.sas

Please consider this as a non-breaking replacement of the existing macro, although I'd be happy to learn how best to proceed when a breaking change cannot be avoided.

A breaking change would normally result in a new major version number.  Where a breaking change is avoidable but results in deprecated components (like this one), we mark it in the README and make the cleanup in the next (unavoidable) breaking change.
I've done the above and also added tests for this macro (plus some additional checks, such as whether the prefix is a valid name)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Broken link detection reports valid links inside parens

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
We have a changelog.md file as part of the markdown content, and it gets flagged as having wrong links for PRs. Those links are inside parens, and the mechanism detects them as wrong because of the trailing paren, thinking it is a part of the link.
Reproducible demo
No response
Steps to reproduce
Add this into a markdown file rendered via docusaurus and enable link checking
- Add user.updateLimits ([#595](https://github.com/apify/apify-client-js/pull/595)) ([bf97c0f](https://github.com/apify/apify-client-js/commit/bf97c0f5bf8d0cbd8decb60382f0605243b00dd5)) by [@MFori](https://github.com/MFori), closes [#329](https://github.com/apify/apify-client-js/issues/329)

Expected behavior
Links can be wrapped in parens and wont trigger this validation.
Actual behavior
Such links result in broken builds:
[ERROR] Error: Unable to build website for locale en.
    at tryToBuildLocale (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:78:15)
    at async /Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
    ... 4 lines matching cause stack trace ...
    at async file:///Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
  [cause]: Error: Docusaurus found broken links!

  Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
  Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

  It looks like some of the broken links we found appear in many pages of your site.
  Maybe those broken links appear on all pages through your site layout?
  We recommend that you check your theme configuration for such links (particularly, theme navbar and footer).
  Frequent broken links are linking to:
  - %5B#595%5D(https://github.com/apify/apify-client-js/pull/595)
  - %5B#602%5D(https://github.com/apify/apify-client-js/pull/602)
  - %5B#604%5D(https://github.com/apify/apify-client-js/pull/604)

  Exhaustive list of all broken links found:
  - Broken link on source page path = /api/client/js/docs/2.6/changelog:
     -> linking to %5B#595%5D(https://github.com/apify/apify-client-js/pull/595) (resolved as: /api/client/js/docs/2.6/%5B#595%5D(https://github.com/apify/apify-client-js/pull/595))
     -> linking to %5B#602%5D(https://github.com/apify/apify-client-js/pull/602) (resolved as: /api/client/js/docs/2.6/%5B#602%5D(https://github.com/apify/apify-client-js/pull/602))
     -> linking to %5B#604%5D(https://github.com/apify/apify-client-js/pull/604) (resolved as: /api/client/js/docs/2.6/%5B#604%5D(https://github.com/apify/apify-client-js/pull/604))
  - Broken link on source page path = /api/client/js/docs/2.7/changelog:
     -> linking to %5B#595%5D(https://github.com/apify/apify-client-js/pull/595) (resolved as: /api/client/js/docs/2.7/%5B#595%5D(https://github.com/apify/apify-client-js/pull/595))
     -> linking to %5B#602%5D(https://github.com/apify/apify-client-js/pull/602) (resolved as: /api/client/js/docs/2.7/%5B#602%5D(https://github.com/apify/apify-client-js/pull/602))
     -> linking to %5B#604%5D(https://github.com/apify/apify-client-js/pull/604) (resolved as: /api/client/js/docs/2.7/%5B#604%5D(https://github.com/apify/apify-client-js/pull/604))
  - Broken link on source page path = /api/client/js/docs/2.8/changelog:
     -> linking to %5B#595%5D(https://github.com/apify/apify-client-js/pull/595) (resolved as: /api/client/js/docs/2.8/%5B#595%5D(https://github.com/apify/apify-client-js/pull/595))
     -> linking to %5B#602%5D(https://github.com/apify/apify-client-js/pull/602) (resolved as: /api/client/js/docs/2.8/%5B#602%5D(https://github.com/apify/apify-client-js/pull/602))
     -> linking to %5B#604%5D(https://github.com/apify/apify-client-js/pull/604) (resolved as: /api/client/js/docs/2.8/%5B#604%5D(https://github.com/apify/apify-client-js/pull/604))
  - Broken link on source page path = /api/client/js/docs/next/changelog:
     -> linking to %5B#595%5D(https://github.com/apify/apify-client-js/pull/595) (resolved as: /api/client/js/docs/next/%5B#595%5D(https://github.com/apify/apify-client-js/pull/595))
     -> linking to %5B#602%5D(https://github.com/apify/apify-client-js/pull/602) (resolved as: /api/client/js/docs/next/%5B#602%5D(https://github.com/apify/apify-client-js/pull/602))
     -> linking to %5B#604%5D(https://github.com/apify/apify-client-js/pull/604) (resolved as: /api/client/js/docs/next/%5B#604%5D(https://github.com/apify/apify-client-js/pull/604))
  - Broken link on source page path = /api/client/js/docs/changelog:
     -> linking to %5B#595%5D(https://github.com/apify/apify-client-js/pull/595) (resolved as: /api/client/js/docs/%5B#595%5D(https://github.com/apify/apify-client-js/pull/595))
     -> linking to %5B#602%5D(https://github.com/apify/apify-client-js/pull/602) (resolved as: /api/client/js/docs/%5B#602%5D(https://github.com/apify/apify-client-js/pull/602))
     -> linking to %5B#604%5D(https://github.com/apify/apify-client-js/pull/604) (resolved as: /api/client/js/docs/%5B#604%5D(https://github.com/apify/apify-client-js/pull/604))

      at throwError (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/logger/lib/logger.js:80:11)
      at reportBrokenLinks (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/server/brokenLinks.js:250:47)
      at handleBrokenLinks (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/server/brokenLinks.js:282:5)
      at executeBrokenLinksCheck (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:91:47)
      at /Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:70:67
      at Object.async (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/logger/lib/perfLogger.js:42:47)
      at buildLocale (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:70:31)
      at async runBuildLocaleTask (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:93:5)
      at async /Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:74:13
      at async tryToBuildLocale (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:70:9)
      at async /Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
      at async mapAsyncSequential (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24)
      at async Command.build (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/build/build.js:33:5)
      at async Promise.all (index 0)
      at async runCLI (/Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/lib/commands/cli.js:56:5)
      at async file:///Users/adamek/htdocs/apify/apify-client-js/website/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3
}
[INFO] Docusaurus version: 3.6.3
Node version: v22.12.0

Your environment
Here is a failed job in our CI, it uses older docusaurus and node versions, but I've tried it locally with node 22.12 and docusaurus 3.6.3, with the same outcome.
https://github.com/apify/apify-client-js/actions/runs/12069278020/job/33656193940
Self-service

[ ] I'd be willing to fix this bug myself.

I tried a minimal repro of your problem and couldn't get Docusaurus to fail https://stackblitz.com/edit/github-upgr1x?file=docs%2Fintro.md,docusaurus.config.js
It's been a long time since I've done this so there may be something I'm missing ?

This is a bug in @apify/docusaurus-plugin-typedoc-api
Your generated changelog files contain syntax such as:
- Add user.updateLimits ([#595]([#595](https://github.com/apify/apify-client-js/pull/595))) ([bf97c0f](https://github.com/apify/apify-client-js/commit/bf97c0f5bf8d0cbd8decb60382f0605243b00dd5)) by [@MFori](https://github.com/MFori)

which is wrong and different from what you expected/provided:
- Add user.updateLimits ([#595](https://github.com/apify/apify-client-js/pull/595)) ([bf97c0f](https://github.com/apify/apify-client-js/commit/bf97c0f5bf8d0cbd8decb60382f0605243b00dd5)) by [@MFori](https://github.com/MFori)

You can see for yourself the result in the MDX playground:


Support gradle's verification-metadata.xml?

Hi. It looks like osv-scanner only checks for gradle.lockfile and friends, not verification-metadata.xml (Gradle dependency verification), which is the only "lockfile"-like thing we have for gradle.
We currently use another tool for scanning our gradle dependency tree against NVD, and that tool works with the files we have. We would like to migrate to osv-scanner if possible. Is there any reason osv-scanner does not parse this file, or is it simply because it has not been added yet?
We currently use the following tool to scan our gradle dependency tree against NVD: https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html.
Current results:
$ osv-scanner scan --lockfile android/gradle/verification-metadata.xml
could not determine extractor for /home/foobarbaz/android/gradle/verification-metadata.xml

Thanks for the request!  we simply have not added support for this yet.
@G-Rath is this something we can put on your plate?

@faern would it be possible for you to provide a couple of examples of this file, for building test fixtures? All good if not, it'd just save me some searching if you can🙂

Here is our own lockfile, I can start by linking that. I'll see if I can find more examples later: https://github.com/mullvad/mullvadvpn-app/blob/main/android/gradle/verification-metadata.xml

This would be a great addition to the tool!
Here's another one used by the official F-Droid Android Client app that also includes signature checks:
https://gitlab.com/fdroid/fdroidclient/-/blob/master/gradle/verification-metadata.xml

Thanks all for the samples! I'll start digging and post back here if I have any questions :)


Support duration in cache configuration

The default duration is null which will cache forever, which is the current behavior.

Thanks!


Output gPlayerInfo via console

output of LVL, XP and estimate of games, minutes and hours needed to lvl up.

i never encountered a boss battle.. what would the score be in that case?


branches in .git/logs/refs/heads are not checked, but do show up as branches in git-branch

I have an (old) git repo that has a branch that is not in .git/refs/heads but in .git/logs/refs/heads. It shows up as a normal branch in git branch and also when doing git for-each-ref --format '%(refname:short)' refs/heads/. Maybe we should replace the for REF_HEAD in $(cd $GIT_DIR/refs/heads with the git for-each-ref command? (I'd be happy to provide a PR)

Just checked with another repo that I've had on my laptop for a few years now. It contains files in logs/refs/heads that are not in refs/heads and do show up in git branch. Files that appear in both directories and also files that appear in logs/refs/heads that are in refs/heads and that do not show up in git branch. Apperently the logic is not trivial.


Find my mouse - shake mouse trigger on touch input

Microsoft PowerToys version
0.56.1
Running as admin

[ ] Yes

Area(s) with issue?
Mouse Utilities
Steps to reproduce
When I use the touch screen while having "Maus schütteln" enabled it will trigger the event.
Surface Pro (5th. Generation) 16GB
✔ Expected Behavior
Nothing
❌ Actual Behavior
It triggered the event
Other Software
No response

It makes sense to try and make it ignore touch screens. Need to see if this can be detected.

I was about to open a similar issue, for me this just happened when my Surface Pen was at the top window bar of open windows (it didn't actually touch the screen)
Now that I've tried it, I noticed that it is also happening when trying to move a window with my finger.

Just making some notes here.
It should be possible to find the source of the input.
https://docs.microsoft.com/en-us/windows/win32/api/winuser/ne-winuser-input_message_device_type
I'm assuming the TOUCH and PEN input types can be ignored.

TOUCH input would be in an upcoming utility: "Find my finger"

While at this point we didn't prevent touch inputs from actually "finding my mouse", on 0.56.2 we added a sensitivity control in settings so it shouldn't activate as easily as before.
Could you please verify if this issue is fixed for you?
/needinfo

It seems to be fixed now!
With my current settings (minimum-distance=1500) I have to try really hard to trigger it with my pen, and with minimum distance set to 1, it doesn't trigger instantly like before, not from "natural hand jiggling" (also not when using my finger to move windows)

Thanks for the feedback. I expect this to have been fixed in https://github.com/microsoft/PowerToys/pull/16756 for the case where it was really causing issues.


Check if event is part of a synced project before sending it to the processor

The leecher is receiving all events that happen on Aquarium. Some of them might not be inside a synced project.
To avoid unnecessary event to process, we can check if the event is part of a synced project by using the event.get_context() un the callback function:
https://github.com/ynput/ayon-aquarium/blob/ea0e891187e601675408219b7ae54157701666b3/services/leecher/leecher/leecher.py#L31-L50
Here is a not tested example:
context = event.get_context()
project = context["project"]
if project is not None and project.data.ayonProjectName is not None:
    # Process the event

this is implemented as part of https://github.com/ynput/ayon-aquarium/pull/8


Update Orchard Core packages to 1.6.0

https://github.com/OrchardCMS/OrchardCore/releases/tag/v1.6.0

thanks @agriffard wasn't able to test it, so waited till I could work on 1.8.0.


chore(ci): workaround semantic-release/npm rate limits

Resolves: https://github.com/janus-idp/backstage-plugins/issues/521
Instead of release toolkit migration, which didn't yield sufficient results, I've tried working around the semantic-release issues instead.
This PR applies https://github.com/semrel-extra/npm workaround to the mysterious NPM rate limits.. Let's see if it helps.

Self merging this to resolve releasing issues.


Low speed of training widerface by ssd300 using dist_train.sh

Before training the model, it takes long long time, as well as validation. It is longer than single GPU. The utilization rate of cpu and gpu is low. I do not know what's the problem.
mmcv=0.6.2 installed by pip;
and mmdetection=2.21；
pytorch=1.4.0 + cu100

It takes longer when samples_per_gpu or workers_per_gpu is large. For SSD, it is 8*3.

@xvjiarui ,but if I set 8*3, the gpu-util is low.

Waiting for fork process.

16cores + 2* titanxp，samples=32, workers=8,  waiting 5 min, and training 6 min, does it normal？

I am not sure if your hard drive will slow it down.
More workers will load more images, and each worker has its own coco annotation copy.
I suggest you validate less frequently and use fewer workers. You may try how many workers will be the best trade-off between GPU utilization and waiting time.


Cnsrc dev

Hongji will do this. @JiJiJiang.

New scheduler can also be verified on the voxceleb dataset, could you try when you have time?

Hongji will do this @JiJiJiang.


manifest: update catalyst-api version commit

For staging, this include:

unrevert of commits after the multistream rollback
transcode,video: Add support for copying HLS input segments (https://github.com/livepeer/catalyst-api/pull/1261[)](https://github.com/livepeer/catalyst-api/commit/c31e2b5549402e88a1daf067e7f391a35d2bc956)
access-control: use whole acReq payload as cacheKey (https://github.com/livepeer/catalyst-api/pull/1267[)](https://github.com/livepeer/catalyst-api/commit/cb6dce39167a66c2b31cf7cb7307a9d85c65173a)

I've seen this test failure be flaky in the past, should be ok to merge https://github.com/livepeer/catalyst/actions/runs/9500437849/job/26183495484?pr=973

I think I am unable to merge this without everything being green, can you do that?


Expand getArgsData from Issue #1 so it can grab Node CLI args if no "?" querystring

Expand getArgsData (from Issue #1) so it can run standalone in Node and/or via foo.test.js
Once completed, try a variety of test runners: Mocha/Chai and Jest and Jasmine and even whew.js :-)

Expand getArgsData (from Issue Parse querystring args - auto-calc if "?" anything #1) so it can run standalone in Node and/or via foo.test.js

-Partially completed via fd9e44d (the foo.test.js part, not the parse-Node-args part).

TBH should probably delay the "playing around" with the variety of test runners for now - should focus on AWS exercise!


Running multiple pairs in 4.x?

Is it still possible under 4.x, for example both BTC-USD and ETH-USD?

Yes, just start new traders with a different pair as an argument.
In the docker-compose.yml (in case you use docker) you can even re-use the zenbot_server image.

Although it's possible, I would not really recommend multiple pairs on the same exchange and same currency. Your profit calculations will be off, and the bot won't be able to execute signals when it needs to - the 2 processes will conflict at some point. And the sim doesn't accept 2 pairs, so there's no way to model what happens to your profit margin.

I'm curious about this too.  I have it running with two pairs, and set the buy % to 70% of available balance so there's usually some amount available when one currency or the other wants to trade.  It's far from ideal though.  What I'd really like is to be able to block off some amount of the balance as only tradeable on one currency or another.  Sort of like a separate account.  I'm not sure what that would take though.

Sort of like a separate account. I'm not sure what that would take though.

I thought about that too, maybe a setting where it will use Math.min(balance, some_amount) as the balance, instead of the full balance.

I thought about that too, maybe a setting where it will use Math.min(balance, some_amount) as the balance, instead of the full balance.

I second that. I usually allocate 40-40 split between the 2 coins and hold 20% cash for manual trades.

This is still an interesting feature guys :)

Suggestion for the logic.
If I have 100€ on my account, I would like bot1 to start with 50€ max, bot2 to start with 25€.
Then they can only play with their own gains or loss. Bot1 made 20€ profit so it's trading up to 70€, bot2 made 20€ loss so it's trading with 5€

I'd be happy with simply being able to set a max amount. I restart the bots often enough to redistribute the profits for trading.

@timstoop Do you have a program that automatically restarts your bots at some point?

No, but I manually run the backtester every day or so to tweak for the best settings.

Will this issue be solved. I too have the same problem. If I have €500 on GDAX balance and I want bot 1 to use only €300 of that balance.
I tried using the options --currency_capital and giving it my limit. But when the trade is executed the full balance is used rather that the one specified.
Would be nice to have this option.


ActiveDirectory / LDAP integration

Should be able to:

Choose AD/LDAP as the authentication source (instead of GitHub) and configure relevant settings (host, port, service account, etc)
Decide who can log in

"unrestricted" mode: allow any valid AD user in
"restricted" mode: allow only whitelisted users and members of whitelisted groups

Create environments with LDAP users & groups as projectMembers

Thanks. Can't wait to test.

Basic use case Happy flow is now supported.
Login with username password. Ldap config now exists.
This Issue cannot be resolved until #1497 is finished.

Adding Cattle Identity API and adding capability to configure.

Complete integration with UI + write design spec.

Ldap Authentication Integration
Purpose: To be able to authenticate to rancher using ldap credentials. Add users to the site based on their ldap username or groups.
Add users to a project based on their ldap user or groups.
After configuring ldap you are able to login to rancher using ldap username and password. Then you use rancher the same
as normal except that when creating projects you use ldap users and groups not github users ors or teams.

In order to configure ldap you must specify the following:

accessMode  (restricted or unrestricted)
domain (domain with in ldap to use. ex ad.example.com)
loginDomain

default domain to login using
ex User1 becomes loginDomain\User
ex foo\User1 stays foo\User1

port (port ldap is listening on. defaults to 389)
server (server ip or domain that rancher can use to connect.)
tls (Use tls or not. (Tls not tested / implemented yet.))
serviceAccountPassword (password for the service account that has readonly access to all of ldap (All of ldap that you may need access too for authentication.))
serviceAccountUsername (username for the service account, same account as above)
searchFieldUser (Field used on ldap object to search for a user defaults to sAMAccountName)

Subject to change

https://github.com/rancher/rancher/wiki/Ldap-Auth-Configuration.

Hi,
May I know to which docker image tag that this changes commit to? I'm using latest one apparently it's using v0.30.0 tag.

@MhdAli this feature hasn't landed in a release yet. We'll update this issue when it does. Sorry for the confusing statements.
Here's the relevant PR:
https://github.com/rancher/cattle/pull/703

Search for Groups.


SCIP build successful but scip not available

I just built SCIPOpt suite with cmake3 and when I run make check, I get 100% successful build. The installation path is default /usr/local, and I have done export SCIPOPTDIR=/usr/local. But when I try to launch the Scip command using scip, I get bash: scip: command not found
I'm on Centos 7.
Am I missing something here?

Different Linux distributions use different default paths for binaries/executables. It can be that in Centos /usr/local is not in the PATH. If it isn't you should either add it or use another installation directory. CMake cannot detect this automatically, it seems.

I am closing this due to inactivity.


Update free-courses-en.md

What does this PR do?
Add resource(s) | Remove resource(s) | Add inf | Improve repo
For resources
Description
Why is this valuable (or not)?
I have taken this course.
How do we know it's really free?
edX courses are for free and self paced.
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Hello @sohansai, I've followed all the contribution guidelines and crafted a flawless pull request.

Hi @sohansai, I have made the required changes.
Regards

Hi @sohansai . I have made the required changes, kindly mention if more have to be made.
Regards


Crash: C# Arrays Passed as a Parameter

Describe the bug
When a C# array is passed as a parameter to a Swift method, a crash occurs with no error or logs produced.
To Reproduce
C# Script
GodotObject singleton = ClassDB.Instantiate("CoolObject")
string[] myStringArr = new string[] { "noice", "ok" };
singleton.Call("printCoolWords", myStringArr);

Swift Script
// Class: CoolObject
@Callable
public func printCoolWords(coolWords:[String]) {
  for coolWord in coolWords {
    GD.print(coolWord)
  }
}

Expected behavior
Any variant compatible type should be able to be passed as a parameter, per the documentation.
OS: tested on macOS, and iOS.
Additional context
There is a work around to use arrays provided by Godot.Collections. So, one could use:
Godot.Collections.Array<string> myStringArr = new();
myStringArr.Add("noice");
myStringArr.Add("ok");

While this makes the plugin functional, it certainly isn't ideal as Godot.Collections should be avoided in C# as it requires some potentially expensive marshaling.

I suspect the reason is that the above should probably be coolWords: GArray or coolWords: VariantCollection<GString>

There is no automatic conversion to a Swift array from a GArray or a variant collection, worth exploring as a new feature.

We should have the Callable macro catch this particular case '[String]' and point the user on the right direction, not a bug in the binding itself, but would reduce the agony for users.

That's also a possibility, I will try to see if we can do that.


Create Post “2022-10-29-sudah-kenal-computer-vision-belum-berikut-ini-penjelasan-secara-singkat-dan-mudah-dipahami-1”

Automatically generated by Netlify CMS

👷 Deploy Preview for mystifying-heyrovsky-e13280 processing.

Name
Link

🔨 Latest commit
8cecf2fe8074ac024dd9629dfc2a7b4676975ac0

🔍 Latest deploy log
https://app.netlify.com/sites/mystifying-heyrovsky-e13280/deploys/635cbe2be9a4b50008e83cb2


Texture Issue when next to stairs

Found an issue when placing a stair next to a windowlogged stair facing a different direction.  the face of the stair disappears.

which version of windowlogging are you running? i thought i fixed that a while ago...

windowlogging-mc1.16.3_v0.0.4

I can't reproduce this, i couldn't reproduce in 0.0.4, and i can't in 0.0.5. Might this be optifine?

I don't have optifine but I got another texture bug related to the mod
(using windowlogging-mc1.18.1_v0.0.8 in allthemods7)
Mostly iron bars, their textures started to spread out. It took me a while wondering what was happening, and noticed that the textures started to get worst as I progressed with my decorations.
I did pretty much check that it was this mod causing the issue. By simply removing the mod while in another world.
Early on

Later pixels raised by a few notches up and down.

@HopsandBarley
It might help if you told what resource pack/materials you are using as well, seems like this is not normal minecraft glass to me. (Can see the designs on the back of the block).


Fab Button Functionality

Add Fab Button in View and onClick event handle check stock is present in Database or not, If yes show toast Stock already in Database, If not make Request to Yahoo REST API and fetch Stock.

Looks good Fab Button Looking good in View. Now Need to Add Click Event.
Before making Click event, Stock have to save in Database.
Let's Make Database Functionality.


Steps fail due to linker error

No matter what I do, I'll keep getting "LNK1104 - cannot open file 'etc.lib'". Because there will be no ".lib" file, the project only creates ".dll".
I'd be very glad if anyone could clarify why would I need a static library to be linked anyway, as the whole point of creating a dll is to use the dll itself.

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

ID: 08c574a2-cef0-ab13-7375-55851f966ef6
Version Independent ID: fe3421c7-e9f4-4986-589f-fadaedce583e
Content: Walkthrough: Create and use your own Dynamic Link Library (C++)
Content Source: docs/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

I've found the reason my project didn't export the ".lib" file, and for the record for those who might run into the same problem, take a look at this discussion here on stack overflow :
https://stackoverflow.com/questions/3950509/build-succeeded-but-no-lib-file-gets-created

@theparham
Did you have trouble with this particular walkthrough, or were you looking for a solution to this issue in some project of your own? Is there a particular part of this document that you looked at for this information, and were either confused by, or the information wasn't there? I'm trying to figure out if there's something here that needs to be addressed.

@corob-msft
Short answers would be no, yes, and yes :)
I wasn't following exactly the walk through, I already had a concept in mind and was trying to fix the DLL linking problem, in which case this walk through came up first in the search.
I skim read the walk through to see if I can figure out what's wrong in my setup, and I saw no clue due to the basic fact that I was trying to export a simple template class to start with, and according to the mentioned stack overflow discussion it was both the wrong mindset and the different way msvc compiler handles template classes in dynamic link libraries, resulting in the absence of the ".lib" file on debug which would break the chain! (Jesus that was an extra long sentence!!!)
I'd be very happy if I could notice this data here (where everyone would probably attend to know the basic facts about creating DLLs) rather than spending half a day trying to search for an answer that fits my problem by chance. Something like a callout just to mention that there is a reason this walk through is only exporting functions could've save that half a day for me if it helps ;) :)
Thanks for the deep instructions by the way, it sure must've took a lot of effort. I do appreciate it :)

I'd also add this ancient yet very useful page for those who might need some clarifying on why my mindset would be wrong, again for the record:
https://www.codeproject.com/Articles/28969/HowTo-Export-C-classes-from-a-DLL

Added a paragraph about our rationale for choosing a C-style interface. It seems related.


Fix CBMC proofs for socket

This PR fixes the build issues and proof failures for the Socket related CBMC proofs post the IPv6 changes.
Test Steps
cd test/cbmc/proofs/
python run-cbmc-proofs.py

Related Issue
Failing CBMC proofs
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run uncrustify


Configure jspreadsheet dropdown with single-click

Dear Team,
I get number of questions from users that ask if the dropdown jexcel/jspreadsheet could be configured with single click instead of double-click? Any chance this can be achieved?
Thanks and regards

Hi,
you can use event onselection
var MyTable = jspreadsheet(DOMElement, {
    onselection: function(el, x1, y1, x2, y2, origin) {
        // check if it is one cell, and if is column C with dropdown
       if(x1 == x2 && y1 == y2 && y1 == 2) {
              jexcel.current.openEditor(jexcel.current.records[y1][x1], false);
       }
   },
});


feat: self-disable if detected Node.js runtime version is too old

This change prevents @instana packages from loading in (and thereby crashing)
Node.js processes that run on an unsupported, outdated Node.js version.
refs 80206

Super sweet!


Both sites that have the "freeze extension" button are blocked

I don't know if there are mirror sites that might be unblocked, or if it just won't work.

It's not my responsibility to host mirror sites. You can always fork this repo and host it somewhere else.


Automatically resolves wifi info so no Tessel is fetched

Grunt is still not passing this and I'm not sure why. But it will take care of the previous issue we were seeing with Travis because the getWifiInfo was not stubbed so it was attempting to fetch a real Tessel.
@rwaldron or @MrNice could you look at this Grunt test? I can't figure out what the issue might be. It looks like if you comment out the getWifiInfo stub, it passes (except you'd get the same getDeviceList error on Travis if you pushed it.

Will close this and open on master.


fix: lets try new boot image

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test gsm

kube
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test gsm

kube
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test kube

vault
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test gsm

kube
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test kube

vault
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
6d10dd4b16924d8b933f57c22367b6b60c910706
link
/test kube

vault
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test vault

gsm
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jstrachan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test vault

gsm
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test gsm

kube
eaf34a18afdc8359a71209f6fad9d3f4aefb72ee
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Jack connect config

Second attempt... Fixed formatting.
Add option to allow baresip not to make jack connections once the call is up and running.  My use case is radio broadcasting where the routing will be switched by the playout system.

Thanks!


Improve (or just check) that tutorial with "search on AWS S3" shows how to set correctly the AWS env

For example, we can make sure that AWS S3 is reachable from the instance by using the AWS CLI to:

check the bucket existence
make a put / delete a file to ensure everything is working well

Closed via 2f514ebca5bb4e979356b0b76426c51ae7b3ab0a.