Error: No match was found for the specified search criteria and module name 'OpenSSHUtils'

The document references OpenSSHUtils as the tooling solution for deploying public keys to the server, but this tool is no longer available (it seems it has been deprecated). See: https://stackoverflow.com/questions/62873521/powershell-opensshutils
Please update these documents with new instructions for deploying public keys.

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

ID: 4c89b7b3-c05f-b517-6109-04e6a97195c3
Version Independent ID: 1e4b742e-d999-2c1e-a396-dc149f7ac76b
Content: OpenSSH key management for Windows
Content Source: WindowsServerDocs/administration/OpenSSH/OpenSSH_KeyManagement.md
Product: windows-server
Technology: administration
GitHub Login: @maertendMSFT
Microsoft Alias: damaerte

I know, it has taken a long time to get the documentation updated to match the current status. This has been reported before and also has at least 1 Pull Request to have the documentation updated accordingly, but it seems to take much more time than first anticipated.
Also, duplicate of the following list of issue tickets:

OpenSSHUtils is deprecated -- #3806 opened on Jan 28, 2020 by FizzBuzz791
PubKey Auth not working [solution] -- #3828 opened on Jan 31, 2020 by ackvf
Outdated instructions? -- #4023 by RussKeldorph was closed on Sep 2, 2020
OpenSSHUtils Not Needed -- #4345 opened on May 14, 2020 by gynnantonix
Unable to configure OpenSSH for public key auth following docs -- #4518 opened on Jun 20, 2020 by jaraco
Instructions provided ends with an error -- #4598 opened on Jun 28, 2020 by jyavenard
Out-of-date - OpenSSHUtils no longer available. -- #4622 opened on Jul 8, 2020 by Jammrock
More documentation required -- #4634 opened on Jul 11, 2020 by garylawuk
OpenSSHUtils install reference no longer valid -- #4690 opened on Aug 1, 2020 by wrjohnson
OpenSSHUtils got unlisted from the PowerShell gallery -- #4702 opened on Aug 5, 2020 by jagraveldinger
Does not list possible ssh commands -- #4726 opened on Aug 16, 2020 by morgzz
ssh-agent service not installed upon installation of OpenSSH Server or Client -- #4729 by ThatNerdyPikachu was closed on Oct 10, 2020
Nope. First example errors out. -- #4743 opened on Aug 22, 2020 by boomalator
Error when following instructions to install OpenSSHUtils -- #4770 opened on Aug 31, 2020 by c0f
OpenSSHUtils module does not exist -- #4787 opened on Sep 4, 2020 by oliversalzburg
Does not explain how to ensure keys get reloaded to agent on boot -- #4858 opened on Sep 30, 2020 by g24swint
Private keys from the ssh-agent can be accessed -- #4871 opened on Oct 2, 2020 by stefanfritsch
Install-Module OpenSSHUtils failure -- #4893 opened on Oct 8, 2020 by LeeJenkins
Does ssh-agent on windows have persistent storage of ssh keys? -- #4946 opened on Oct 27, 2020 by zaaj
OpenSSHTools doesn't exist anymore on powershell gallery -- #4948 opened on Oct 28, 2020 by JustinGrote
Clarification needed -- #5000 opened on Nov 10, 2020 by conyg
OpenSSHUtils has been delisted -- #5068 by esc was closed on Dec 1, 2020
Update suggestion of OpenSSHUtils -- #5080 by aamir0 was closed on Dec 4, 2020
These instructions do not work on Windows 10 20h2 -- #5138 opened on Dec 19, 2020 by mihai-preda
Out of date - Repair-AuthorizedKeyPermission -- #5395 opened 4 days ago by nekdima

See Pull Request update OpenSSH key management #4788 for a possible solution to your report.

Thanks for submitting this issue. I have reworked this document to remove or replace parts that are no longer relevant or correct based on this and several other issues raised for this page.
The changes should be visible in around 6-12 hours.
#please-close


FFHQ 256×256 and ImageNet 256×256 validation dataset

Dear Authors,
Thanks for your great work and for sharing your code!
I am currently working on reproducing the results, and I wanted to ask how you sampled the 100 images for evaluation (if possible, which specific samples were used) and how they were pre-processed to obtain the final 256x256 HR images for each dataset.
Thank you.

Hi @NebiyouTen,
I have just uploaded the names of the validation data at https://github.com/yuanzhi-zhu/DiffPIR/blob/main/testsets/ffhq_val_100/ffhq_val_100.txt and https://github.com/yuanzhi-zhu/DiffPIR/blob/main/testsets/imagenet_val_100/imagenet_val_100.txt.
You can download them from the corresponding 256*256 datasets.

Thank you.


MICS6814: read_nh3 and read_oxidising now call the correct get_raw_* functions

As per DrDozzy's comments on Discord, the MICS6814 breakout code uses 'get_raw_red' for both nh3 and oxidising readings too, rather than the correct ones.
Note: I don't actually have one of these breakouts, so my testing has been limited to 'does it still compile' :smile:

It's a testament to how completely opaque these gas values are that a mistake this blatant can survive for over a year :roll_eyes:  thank you for PR'ing a fix!


[GHSA-3rq8-h3gj-r5c6]  .NET Denial of Service Vulnerability

Updates

Affected products

Comments
There's a mismatch when comparing the list of packages in the description of this CVE.

Hi there @rbhanda! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


How to run the face detection/recognition on edge tpu device ?

Hi,
I followed the tutorial by Andrian and was able to generate the pickle file for the training face images I used. I would like to implement the model on edge tpu and use it. Can anyone please tell me how to proceed ?
Any help would be appreciated.
Thanks in advance.
Vismaya

Hi,
I've gotten face detection and recognition to work on Google Coral using tpu-, dlib- and openCV-based face detectors and dlib- and OpenCV-based facial embedders and an SVM-based face classifier. The detailed instructions on how to set this up can be found here (note that you don't need to follow all the steps outlined here if you are just interested in face detection / recognition). Please take a look at that and let me know if you have any questions.
Thanks.
Lindo

Closing due to inactivity.

Hi,
Sorry for the inactivity. Could you please reopen the issue ?
Thanks,
Vismaya

As you wish. Please let me know how I can help.

Hi,
Thanks a lot. Is it possible to do the face recognition module on edge tpu device without memory swap ? When I tried it last time, the system got crashed.

Do you mean the temporary swap sapce required to compile dlib and face_recognition on the coral board? Yes, you can cross compile those packages on another machine instead. But not sure what your problem is exactly. The swap space is temporary and after you are done compiling the packages you remove the swap. See the detailed instructions at https://github.com/goruck/edge-tpu-servers/blob/master/README.md. You can send me the commands you are using and the error and I will try to help further.

I just tried swaping for the installation of OpenCV, the board crashed and I lost all the data on the board. But I've compiled OpenCV now with swaping. So my question here is can we compile dlib and face_recognition without generating swap space. I've generated all the models including svm and xgboost. If everything goes well and fine how much time will it take for inference on the board ? and how do I find the accuracy and loss ?

The Coral Dev Board has a modest 8GB on-board eMMC. You need to insert a MicroSD card (at least 32 GB) into the Dev Board to have enough space to install the software. Are you using a MicroSD card?
As for your questions:

"can we compile dlib and face_recognition without generating swap space"
No. You will run out of ram and the compiler will crash.

"How do I test the models on desktop?"
See face-det-rec and in particular train.py.

"If everything goes well and fine how much time will it take for inference on the board" + "how do I find the accuracy and loss".
See this.

Thanks for the valuable information 👍


Allow to use custom serializaition in localStorageCache and sessionStorageCache

Hi! It would be super useful to have the ability to customize serialization used by cache adapters
Use case
We are using tRPC with superjson as a custom transformer.
This allows transparently pass Date fields between client and server
export const api = createTRPCProxyClient<AppRouter>({
    transformer: superjson,
})

Each query are wrapped in createQuery
export const listQuery = createQuery({
    handler: api.list.query
})

Then we are trying to cache listQuery
cache(listQuery, {
    adapter: localStorageCache(),
})

Everything is working great, except instead of Date type in cached response we are getting string (e.g. 2023-04-03T07:22:51.627Z), which is not the same response returned from a wrapped handler.

Hello! Sounds great, will be done in the next release 🫶

Done and will be released in #312


Update to fog 1.25 gem to support AWS4.

Firstly, this is an awesome gem.
For fog, see https://github.com/fog/fog/blob/master/CHANGELOG.md : version 1.25 is needed if you want to use the new locations like Frankfurt, as they ONLY support AWS v4 and up.
Locally I changed my gemfile.lock to test with the backup gem and a Frankfurt Amazon bucket. Everything works as expected.

this commit killed the ability to push to  radosgw from ceph
since the fog update i get the following error
2015/01/27 10:12:47][info] Storing 'backups/nova/data/2<IP_ADDRESS>.12.47/data.tar'...
[2015/01/27 10:12:47][info] CloudIO::Error: Retry #1 of 10
[2015/01/27 10:12:47][info]   Operation: PUT 'backups/nova/data/2<IP_ADDRESS>.12.47/data.tar'
[2015/01/27 10:12:47][info] --- Wrapped Exception ---
[2015/01/27 10:12:47][info] Excon::Errors::BadRequest: Expected(200) <=> Actual(400 Bad Request)
[2015/01/27 10:12:47][info] excon.error.response
[2015/01/27 10:12:47][info]   :body          => "<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error>InvalidArgument</Error>"
[2015/01/27 10:12:47][info]   :headers       => {
[2015/01/27 10:12:47][info]     "Accept-Ranges"  => "bytes"
[2015/01/27 10:12:47][info]     "Connection"     => "close"
[2015/01/27 10:12:47][info]     "Content-Length" => "81"
[2015/01/27 10:12:47][info]     "Content-Type"   => "application/xml"
[2015/01/27 10:12:47][info]     "Date"           => "Tue, 27 Jan 2015 10:12:47 GMT"
[2015/01/27 10:12:47][info]     "Server"         => "Apache/2.2.22 (Ubuntu)"
[2015/01/27 10:12:47][info]   }
[2015/01/27 10:12:47][info]   :local_address => "<IP_ADDRESS>"
[2015/01/27 10:12:47][info]   :local_port    => 52550
[2015/01/27 10:12:47][info]   :reason_phrase => "Bad Request"
[2015/01/27 10:12:47][info]   :remote_ip     => "<IP_ADDRESS>"
[2015/01/27 10:12:47][info]   :status        => 400

see
https://github.com/meskyanichi/backup/issues/474
https://github.com/meskyanichi/backup/pull/439

it seems this issue is fixed in https://github.com/fog/fog/pull/3303

@ramonskie so a update to v1.27.0 would fix it, right?
https://github.com/fog/fog/commit/f4a04fe7b8f9ccc03682aac0a6e6c625df8ffa20

yes this would fix my issue
because then we could use the option "aws_signature_version: 2"

@ramonskie can you use the branch update_fog_issue_616 and let me know if this fixes your config?

first had some troubles but noticed that the gemspec was not up to date yet (DOH)
but all in all when everything installed fine and i added
s3.fog_options = {:host=>"myhost", :scheme=>"http", :port=>80, :aws_signature_version=>2}

all worked as it should be :+1:
i think this would also be nice if someone can document this feature so you can also close
this feature request https://github.com/meskyanichi/backup-features/issues/20

@ramonskie new release 4.1.7 has an updated fog dependency, resolving your issue.


Probing always fails when HTTP fallback is disabled in config-network

When HTTP fallback is disabled probing will set an https scheme and a port of 443
https://github.com/knative-sandbox/net-contour/blob/50b263c04bb6ff46398f9a2baa06cd9f13cc0ba3/pkg/reconciler/contour/lister.go#L48-L52
Contour targets Pod IPs for probing which doesn't do TLS termination so the endpoints will never be ready.

/lifecycle frozen

/assign
I will work on this.

/unassign @nak3
/assign @kvmware

Note this issue changes slightly when https://github.com/knative-sandbox/net-contour/pull/610 lands
Since we'll want to configure the spec.HTTPOption now

When using kubectl apply -f https://github.com/knative/net-contour/releases/download/v0.25.0/contour.yaml and kubectl apply -f https://github.com/knative/net-contour/releases/download/v0.25.0/net-contour.yaml a service is created kn service create hello --image gcr.io/knative-samples/helloworld-go --port 8080 --env TARGET=New_World --revision-name=new_world which results in:
$ kubectl get ksvc
NAME    URL                                           LATESTCREATED   LATESTREADY   READY     REASON
hello   https://hello.default.<IP_ADDRESS>.sslip.io   hello-world     hello-world   Unknown   EndpointsNotReady

$ kubectl describe ksvc hello
...
Status:
  Address:
    URL:  http://hello.default.svc.cluster.local
  Conditions:
    Last Transition Time:        2021-09-23T19:05:43Z
    Status:                      True
    Type:                        ConfigurationsReady
    Last Transition Time:        2021-09-23T19:05:44Z
    Message:                     Waiting for Envoys to receive Endpoints data.
    Reason:                      EndpointsNotReady
    Status:                      Unknown
    Type:                        Ready
    Last Transition Time:        2021-09-23T19:05:44Z
    Message:                     Waiting for Envoys to receive Endpoints data.
    Reason:                      EndpointsNotReady
    Status:                      Unknown
    Type:                        RoutesReady
  Latest Created Revision Name:  hello-world
  Latest Ready Revision Name:    hello-world
  Observed Generation:           1
  Traffic:
    Latest Revision:  true
    Percent:          100
    Revision Name:    hello-world
  URL:                https://hello.default.<IP_ADDRESS>.sslip.io
...

Changing this to use kubectl apply -f https://github.com/knative/net-contour/releases/download/v0.26.0/contour.yaml and kubectl apply -f https://github.com/knative/net-contour/releases/download/v0.26.0/net-contour.yaml which includes the changes from #610 the result is thus:
$ kubectl get ksvc
NAME    URL                                           LATESTCREATED   LATESTREADY   READY     REASON
hello   https://hello.default.<IP_ADDRESS>.sslip.io   hello-world     hello-world   True

$ kubectl describe ksvc hello
...
Status:
  Address:
    URL:  http://hello.default.svc.cluster.local
  Conditions:
    Last Transition Time:        2021-09-23T19:05:43Z
    Status:                      True
    Type:                        ConfigurationsReady
    Last Transition Time:        2021-09-23T19:24:51Z
    Status:                      True
    Type:                        Ready
    Last Transition Time:        2021-09-23T19:24:51Z
    Status:                      True
    Type:                        RoutesReady
  Latest Created Revision Name:  hello-world
  Latest Ready Revision Name:    hello-world
  Observed Generation:           1
  Traffic:
    Latest Revision:  true
    Percent:          100
    Revision Name:    hello-world
  URL:                https://hello.default.<IP_ADDRESS>.sslip.io
...

$ curl https://hello.default.<IP_ADDRESS>.sslip.io
Hello World!

Yes, I believe https://github.com/knative-sandbox/net-contour/pull/610 solved this issue as well. @kvmware Thank you for the confirmation. And I'm sorry if you wanted to tackle this issue :cold_sweat:

/close
On Mon, Sep 27, 2021 at 05:31 Kenjiro Nakayama @.***>
wrote:

Yes, I believe #610
https://github.com/knative-sandbox/net-contour/pull/610 solved this
issue as well. @kvmware https://github.com/kvmware Thank you for the
confirmation. And I'm sorry if you wanted to tackle this issue 😰
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knative-sandbox/net-contour/issues/423#issuecomment-927692816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAERAWOQXJSRQCVSC5GBFDUEA2X5ANCNFSM4XPGGLHQ
.


sd-image: use parallel pbzip2 implementation

Motivation for this change
Using parallel bzip2 implementation is faster on multi-processor machines. I tried to compress a 2.7 GB aarch64 NixOS image with the following results:
bzip2

output size: 627353716 bytes
duration: 217 seconds

real	3m36.963s
user	3m35.370s
sys	0m1.552s

pbzip2 -p4:

output size: 632445704 bytes (increase of ~0.1%)
duration: 96 seconds (55% faster)

real	1m36.191s
user	6m11.421s
sys	0m8.036s

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Another option would be to use zstd for final compression of the image (zstd is already a dependency as it decompresses the rootfs image).

zstd -T4:

output size: 614908377 (decrease of 2%)
duration: 10 seconds (95% faster)

real	0m10.069s
user	0m36.025s
sys	0m1.431s

@prusnak Hi!
I agree that using bzip2 is counterproductive as it's extremely slow, especially on more constrained HW. I think pbzip is okay as a stop-gap, but just using zstd is a much better approach that will benefit even single-core systems.
FWIW: I've suggested in the past that we move all our compression to zstd as it has amazing ratio and speed.

I will gladly rework the PR to use zstd instead if that's what we really want.

IIRC the last time I tried to do this there was some discussion on whether or not the output format, in this case the compression algo, of a drv constituted a "public interface" or not; in which case changing it can't be done without further consideration as it breaks things.
IMO: The benefits are significant enough to be worth it, but it needs to be added to the release notes.

Okay, let's close this and pursue a bigger change (zstd) in another PR: https://github.com/NixOS/nixpkgs/pull/85947


highlight() adds newline to the end of a single line expression

(Original issue 1403 created by asmeurer on 2017-12-14T06:09:15.228801+00:00)
>>> highlight('1', Python3Lexer(), pygments.formatters.Terminal256Formatter())
'\x1b[38;5;241m1\x1b[39m\n'

It's a bit annoying that it adds a newline at the end when the input expression has no newlines.

This happens at the lexing stage, e.g.
import pygments
print(list(pygments.lex("1", pygments.lexers.PythonLexer())))

will give you:
[(Token.Literal.Number.Integer, '1'), (Token.Text.Whitespace, '\n')]

Thanks, I missed that.


feat: override subProject and defaultCompression with CLI

Related: #46

Codecov Report

Merging #78 (284b881) into master (4e9e223) will decrease coverage by 2.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
- Coverage   54.01%   51.82%   -2.20%
==========================================
  Files          51       16      -35
  Lines        1244      465     -779
  Branches      255       87     -168
==========================================
- Hits          672      241     -431
+ Misses        572      224     -348

Impacted Files
Coverage Δ

packages/bundlemon/src/cli/index.ts

packages/bundlemon/src/main/analyzer/pathUtils.ts

...es/bundlemon/src/main/utils/ci/providers/github.ts

...ges/bundlemon-markdown-output/src/markdownUtils.ts

packages/bundlemon-utils/src/diffReport/utils.ts

...ckages/bundlemon/src/main/utils/validationUtils.ts

packages/bundlemon/src/main/utils/ci/index.ts

...ackages/bundlemon/src/main/analyzer/getFileSize.ts

packages/bundlemon-markdown-output/src/index.ts

...kages/bundlemon/src/main/outputs/outputs/github.ts

... and 25 more

Continue to review full report at Codecov.

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


bug(hubble): signers are out of sync on some hubs

What is the bug?
Fid 6546 has a signer missing on a lot of hubs:
invalid signer: signer 0x9e49829443c9a11aeb283b06a773d206689978ff21cdbd3f2bbb2931c64f38b7 not found for fid 6546

Nemes has some additional fids where it's missing signers, e.g.
invalid signer: signer 0xd697997bfee1112f733cafc18251c09d324a085fceb9e17ccfef7bc52f6e3eaa not found for fid 762

How can it be reproduced? (optional)
Include steps, code samples, replits, screenshots and anything else that would be helpful to reproduce the problem.
Additional context (optional)
Add any other context about the problem here.

this is my FID. Happy to help triage as this appears to be blocking me in multiple places. pls DC @artlu.eth on Warpcast thank you 🙏


Preserve old version of releases manifest for backwards compatibility

Partially reverting #4777 to have both the older and newer formats of the releases manifest so as to maintain backwards compatibility when performing latest minor release upgrades.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


Snow Leopard-like release?

I'm seeing significant memory consumption pretty much every time I use the interactive window these days (even if it's just minor computations). Not sure when this started but judging by the amount of issues created in the past few months with "memory" in their title, it seems I'm not the only one experiencing this:

Lots of jedi subprocesses created until memory runs out #7144
restarting the Python Interactive kernel increases persistent memory usage #6975
https://github.com/microsoft/vscode-python/issues/6356
Remote Jupyter connection with long running command: Extension host terminated due to memory #6222
Extension host terminated unexpectedly: JavaScript heap out of memory #6001
python language server uses too much memory #5862

So I thought I'd throw the idea out there of doing a Snow Leopard-like release in the coming months that focuses on improving memory and CPU efficiency. Feel free to close if this is out of the question. In any case, thanks for providing such an awesome extension! 😄

Thanks for your suggestions.
Regarding the language server, we have been working for several months on improving CPU and memory footprint, so we are well aware of this.
Those Code Helper processes come from Visual Studio Code; they are likely not Python specific or related to the extension.
The interactive window does keep a second kernel around for fast restarts; that's something we may revisit.
I don't think there is anything new and specific in this issue that isn't captured elsewhere, so I'm closing it.


5.0 compatibility

Chrome

Firefox

Looks like the firefox slider in gradio core is bugged.
The slider color will change to be orange when this PR is released: https://github.com/gradio-app/gradio/pull/9481

Released in version 0.0.7


feat(web): pipeline event watchers

Add automatic pipeline triggers based on registry push events

Codecov Report
Attention: 111 lines in your changes are missing coverage. Please review.

Comparison is base (b16a13e) 18.22% compared to head (bf4b80e) 12.11%.

Files
Patch %
Lines

web/crux/src/app/pipeline/pipeline.dto.ts
0.00%
25 Missing :warning:

web/crux/src/domain/pipeline.ts
0.00%
23 Missing :warning:

web/crux/src/app/registry/registry.service.ts
0.00%
20 Missing :warning:

.../crux/src/app/pipeline/pipeline.http.controller.ts
0.00%
14 Missing :warning:

.../crux/src/app/registry/registry-client.provider.ts
0.00%
8 Missing :warning:

...rux/src/app/registry/registry-clients/v2-labels.ts
0.00%
6 Missing :warning:

...b/crux/src/services/domain.notification.service.ts
50.00%
5 Missing :warning:

web/crux/src/app/registry/registry.dto.ts
0.00%
3 Missing :warning:

web/crux/src/app/registry/registry.mapper.ts
25.00%
3 Missing :warning:

web/crux/src/app.module.ts
0.00%
1 Missing :warning:

... and 3 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #905      +/-   ##
===========================================
- Coverage    18.22%   12.11%   -6.12%
===========================================
  Files          344      272      -72
  Lines        17118     9488    -7630
  Branches      1006      998       -8
===========================================
- Hits          3120     1149    -1971
+ Misses       13810     8314    -5496
+ Partials       188       25     -163

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

crux build is failing

crux build is failing

Thanks! It was caused by the rebase. Now fixed.


Unity firebase messaging crashes

Hi everyone,
I used quick master example included in FCM docs as an example and i initialized FCM properly but when i build and run on android it crashes.Thanks

What is the crash that you see?  Could you share some logs?

We've reproduced a crash on iOS 10 and think we have a fix.  We'll be cutting a release soon and will keep you posted.

This should be resolved in version 1.1.1
https://firebase.google.com/support/release-notes/unity#1.1.1


Feature metadata loader

Follow up to https://github.com/CesiumGS/cesium/pull/9481
Adds a loader for the EXT_feature_metadata extension. GltfFeatureMetadataLoader loads textures, buffer views, and schemas from the cache but does not itself need to go in the cache, so there are no changes to ResourceCache and ResourceCacheKey.

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@ptrgags I added the additional test. Should be ready now.

looks good now, thanks @lilleyse!


feat: run scheduled tasks to sync shared resources from gateway

Resync the resources every 15 seconds minutes. Enabled only when DIRECT_SHARED_RESOURCE_MANAGEMENT_ENABLED is turned no. Need to configure the RESOURCE_SERVER's URL, SECRET_KEY, and RESOURCE_JWT_USER_ID before use.
AAP-23724: EDA: Schedule Sync Task
STEPS to prepare the dev environment:

start the gateway
find the jwt_user_id through API https://<gateway>/api/gateway/v1/users (for the first time)
find the ansible_id of user _system
create a secret_key on the gateway shell (inside the gateway container) (for the first time)
django-admin generate_service_secret eda
export the following ENVS and start eda-server:
EDA_RESOURCE_SERVER__URL=https://<gateway ip, not localhost>
EDA_RESOURCE_JWT_USER_ID=<ansible_id from step 2>
EDA_RESOURCE_SERVER__SECRET_KEY=<output from step 3>
There will be errors in the default worker logs. Proceed to step 5.
run service migrate data on the gateway shell (for the first time)
django-admin migrate_service_data --api-slug eda --username admin
Worker errors should go away.

Added

@bzwei could you extend the docstring here to document these new variables? They seem important enough to clarify them. https://github.com/ansible/eda-server/blob/main/src/aap_eda/settings/default.py#L14

@jamesmarshall24 @rooftopcellist This PR expects EDA_RESOURCE_SERVER__URL, EDA_RESOURCE_SERVER__SECRET_KEY , EDA_RESOURCE_SERVER__VALIDATE_HTTPS, EDA_RESOURCE_JWT_USER_ID, and optionally EDA_RESOURCE_SERVICE_PATH


Nithin/sdkupdates 2019 06 version

changes -
We have added optional fields for WebhookReceiver model in Swagger Spec. Updating the SDK to reflect the same.
incremented the version number .

Can one of the admins verify this patch?

@nithinpnp, could you share the swagger specs PR link related to this change?

/azp run net - mgmt - ci

@erich-wang . The instructions to follow link is broken , Could you please get the latest link ?

@nithinpnp , it is private repo and you should log in first. BTW, you should have joined Azure organization in github already, right? If not, please checkout https://repos.opensource.microsoft.com/.

@erich-wang  https://github.com/Azure/azure-rest-api-specs/pull/6218
this is the pull request for swagger spec that got approved.


build: assume a parallel tree layout for unified builds

Attempt to repair the build for the unified swift build.  This allows us
to build a single unified toolchain with swift support.  In this layout
assume that cmark and clang are peers of LLVM rather than located in
tools.  Doing so allows a uniform layout of the tree and a simpler
build approach.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@jrose-apple ... so, this actually is somewhat related.  This allows me to do a unified build, the difference is that the tree lives as a peer rather than inside of tools.  This allows building with -DLLVM_ENABLE_PROJECTS=cmark

Build failed
Swift Test Linux Platform
Git Sha - 16a4af0e5b1223ac197f7b2fa1f174db2d9cd3d4

When I build with Swift in llvm/tools, I also put CMark there. You can also have Swift and CMark as peers of LLVM in the directory structure and use -DLLVM_EXTERNAL_PROJECTS=swift;cmark -DLLVM_ENABLE_PROJECTS=clang;swift;cmark which leverages the LLVM mono-repo build system tooling.

@llvm-beanz - hmm, would this change then break that?  IIRC, the *_EXTERNAL_SOURCE_DIR are supposed to be setup

This change will break the workflow of nesting under llvm/tools because the LLVM_EXTERNAL_*_SOURCE_DIR variables aren't set in that case. Personally I don't care if we break that flow because the new mono-repo will make working with LLVM projects nested a thing of the past. As long as the LLVM_EXTERNAL_PROJECTS and LLVM_ENABLE_PROJECTS options work that is good enough.

@swift-ci please test Linux platform

Did I miss a warning email about this change? I've been using unified builds for a long time, and the error message if one tries to do it the old way (with clang/swift in the tools directory) isn't helpful.
Where are the directions for how to do it the new way?


Photos sync to Files but are unavailable as Album

I am trying to implement an auto-update gallery workflow for artists.
The idea is for an artist to snap a picture of their work with their phone, the app FolderSync automatically syncs the picture of the work to a pre-set public folder on Hubzilla, this folder should be available as an album for the new Portfolio widget, and the widget is included in the artist's gallery web page. Hey presto, the gallery web page shows a new work by the artist.
Photos sync to the correct public folder in Files, the public folder is visible under Photos, but no photos are visible there.
What is missing to make this work?

fixed in 988028577b19d2cf2825eec65e398d447d8d4056


[WIP] Use post_config.gypi to use shared libraries

Node can be compiled with external shared libraries;
in this case append their compile and linker flags last.

When is this a problem and why does it require a new file?

I try to make node-sass to compile in a situation when libuv is unbundled. I need to supply system include directory (in my case -I /usr/local/include) which make cause certain pollution. For example, I've had an older version of https://github.com/sass/libsass installed in /usr/local and after adding -I /usr/local/include compilation failed.
What I am trying to do is to tell https://github.com/sass/node-sass/pull/2070 to put libsass headers first and this patch is needed to make sure system include path goes last. So we get this order:
-I _added by the binary module_ -I _needed by node itself_
I do not see a way to tell gyp "add those directories at the end of the list". When not using "+" (prepend) qualifier it seems to merge directories in the order of include files.
I am experimenting here to make it work, this PR combined with  https://github.com/sass/node-sass/pull/2070 does the job.
There are may be better alternatives, like removing include_dirs altogether from addon.gypi and building the include_dirs list once into the config.gypi. I would like to also avoid eventuality to adjust binary modules' binding.gyp just for this reason. The problem is binding.gyp is the main file and I think it is processed at the end.

> node -p process.config
{ target_defaults:
   { cflags: [],
     default_configuration: 'Release',
     defines: [],
     include_dirs:
      [ '/usr/local/include',
        '/usr/local/include',
        '/usr/local/include' ],
     libraries:
      [ '-lz',
        '-L/usr/local/lib',
        '-luv',
        '-L/usr/local/lib',
        '-lcares',
        '-L/usr/local/lib',
        '-licui18n',
        '-licuuc',
        '-licudata' ] },
  variables:
   { asan: 0,
     coverage: false,
     debug_devtools: 'node',
     force_dynamic_crt: 0,
     host_arch: 'x64',
     icu_gyp_path: 'tools/icu/icu-system.gyp',
     icu_small: false,
     llvm_version: '3.4',
     node_byteorder: 'little',
     node_enable_d8: false,
     node_enable_v8_vtunejit: false,
     node_install_npm: false,
     node_module_version: 57,
     node_no_browser_globals: false,
     node_prefix: '/usr/local',
     node_release_urlbase: '',
     node_shared: false,
     node_shared_cares: true,
     node_shared_http_parser: false,
     node_shared_libuv: true,
     node_shared_openssl: false,
     node_shared_zlib: true,
     node_tag: '',
     node_use_bundled_v8: true,
     node_use_dtrace: false,
     node_use_etw: false,
     node_use_lttng: false,
     node_use_openssl: true,
     node_use_perfctr: false,
     node_use_v8_platform: true,
     node_without_node_options: false,
     openssl_fips: '',
     openssl_no_asm: 0,
     shlib_suffix: 'so.57',
     target_arch: 'x64',
     uv_parent_path: '/deps/uv/',
     uv_use_dtrace: false,
     v8_enable_gdbjit: 0,
     v8_enable_i18n_support: 1,
     v8_enable_inspector: 1,
     v8_no_strict_aliasing: 1,
     v8_optimized_debug: 0,
     v8_promise_internal_field_count: 1,
     v8_random_seed: 0,
     v8_trace_maps: 0,
     v8_use_snapshot: false,
     want_separate_host_toolset: 0,
     want_separate_host_toolset_mkpeephole: 0 } }

Here is what happens (building https://github.com/sass/node-sass/commit/4a0f3d028c81ab355b9d2b75b76da14e7bf13725 with https://github.com/nodejs/node-gyp/releases/tag/v3.6.2 when using node v8.2.1 from FreeBSD ports :
  c++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.5.0.beta.2"' -I/usr/local/include/node -I/usr/local/src -I/usr/local/deps/uv/include -I/usr/local/deps/v8/include -I../src/libsass/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++0x -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/values.o.d.raw   -c -o Release/obj.target/libsass/src/libsass/src/values.o ../src/libsass/src/values.cpp
  rm -f Release/obj.target/src/sass.a && ar crs Release/obj.target/src/sass.a Release/obj.target/libsass/src/libsass/src/ast.o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o Release/obj.target/libsass/src/libsass/src/base64vlq.o Release/obj.target/libsass/src/libsass/src/bind.o Release/obj.target/libsass/src/libsass/src/cencode.o Release/obj.target/libsass/src/libsass/src/check_nesting.o Release/obj.target/libsass/src/libsass/src/color_maps.o Release/obj.target/libsass/src/libsass/src/constants.o Release/obj.target/libsass/src/libsass/src/context.o Release/obj.target/libsass/src/libsass/src/cssize.o Release/obj.target/libsass/src/libsass/src/emitter.o Release/obj.target/libsass/src/libsass/src/environment.o Release/obj.target/libsass/src/libsass/src/error_handling.o Release/obj.target/libsass/src/libsass/src/eval.o Release/obj.target/libsass/src/libsass/src/expand.o Release/obj.target/libsass/src/libsass/src/extend.o Release/obj.target/libsass/src/libsass/src/file.o Release/obj.target/libsass/src/libsass/src/functions.o Release/obj.target/libsass/src/libsass/src/inspect.o Release/obj.target/libsass/src/libsass/src/json.o Release/obj.target/libsass/src/libsass/src/lexer.o Release/obj.target/libsass/src/libsass/src/listize.o Release/obj.target/libsass/src/libsass/src/memory/SharedPtr.o Release/obj.target/libsass/src/libsass/src/node.o Release/obj.target/libsass/src/libsass/src/output.o Release/obj.target/libsass/src/libsass/src/parser.o Release/obj.target/libsass/src/libsass/src/plugins.o Release/obj.target/libsass/src/libsass/src/position.o Release/obj.target/libsass/src/libsass/src/prelexer.o Release/obj.target/libsass/src/libsass/src/remove_placeholders.o Release/obj.target/libsass/src/libsass/src/sass.o Release/obj.target/libsass/src/libsass/src/sass2scss.o Release/obj.target/libsass/src/libsass/src/sass_context.o Release/obj.target/libsass/src/libsass/src/sass_functions.o Release/obj.target/libsass/src/libsass/src/sass_util.o Release/obj.target/libsass/src/libsass/src/sass_values.o Release/obj.target/libsass/src/libsass/src/source_map.o Release/obj.target/libsass/src/libsass/src/subset_map.o Release/obj.target/libsass/src/libsass/src/to_c.o Release/obj.target/libsass/src/libsass/src/to_value.o Release/obj.target/libsass/src/libsass/src/units.o Release/obj.target/libsass/src/libsass/src/utf8_string.o Release/obj.target/libsass/src/libsass/src/util.o Release/obj.target/libsass/src/libsass/src/values.o
  rm -rf "Release/sass.a" && cp -af "Release/obj.target/src/sass.a" "Release/sass.a"
  c++ '-DNODE_GYP_MODULE_NAME=binding' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' -I/usr/local/include/node -I/usr/local/src -I/usr/local/deps/uv/include -I/usr/local/deps/v8/include -I../node_modules/nan -I../src/libsass/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -fno-rtti -fno-exceptions -std=gnu++0x -std=c++0x -MMD -MF ./Release/.deps/Release/obj.target/binding/src/binding.o.d.raw   -c -o Release/obj.target/binding/src/binding.o ../src/binding.cpp
In file included from ../src/binding.cpp:1:
../node_modules/nan/nan.h:48:10: fatal error: 'uv.h' file not found
#include <uv.h>
         ^
1 error generated.
gmake: *** [binding.target.mk:115: Release/obj.target/binding/src/binding.o] Błąd 1

Bundled libsass C++ files get compiled but <uv.h> cannot be found when comping node binding file.

@bnoordhuis I need solution to this problem quite urgently, do you think this is a way to go forward? Can you (or anyone) think of better alternatives? (I agree that introduction of an extra file is a kind of overkill)

@saper do you want to continue pursuing this? if so, rebase to master and we'll try and get Ben back in here.

Yes, definitely, this is the #1 reason why plain compilation of binary extensions fails on FreeBSD - uv.h cannot be found.

@saper can you start considering how a test (or tests) for this might be constructed? There's a few more examples inside test/ these days that you could lean on.

While I can't review the proposed changes here, I want to voice my support for this in general because this is becoming a huge pain for addon developers.
Most recently the issue is that some OSes are still building node v17.x (which now bundles OpenSSL 3.x) against a shared OpenSSL 1.x. In this situation, when node-gyp builds, it downloads and builds against the bundled OpenSSL 3.x headers instead of the shared headers, which (depending on OpenSSL API changes) may still allow compilation to complete successfully but will end up causing runtime errors (e.g. due to missing symbols), which is more frustrating than not being able to compile at all because the user thinks the addon is going to work properly after installation.
Some example OSes that are currently doing this include: macOS (specifically homebrew), ArchLinux (and any of its derivatives -- e.g. Manjaro), and some other Linux distro (RH/CentOS-based?) I can't recall offhand right now.

Rebase, please?

At least if the OpenSSL subdirectory was in a separate directory (e.g. include/_openssl, which should never interfere with a #include <...>), addons could conditionally exclude that directory, which would allow shared OpenSSL headers to be used.

This is really bad, do you think node should bundle OpenSSL differently?


⚠ Boutique - Ascentia has degraded performance

In dc1391e, Boutique - Ascentia (https://store.ascentia.fr/) experienced degraded performance:

HTTP code: 200
Response time: 10509 ms

Resolved: Boutique - Ascentia performance has improved in 173cfc6 after 10 minutes.


Simplify some VolumeManager tooling

Replace getVolumeByPath(p).getFileSystem() with getFileSystemByPath(p)
(no caller used getVolumeByPath without immediately calling getFileSystem)
Remove redundant null checks for path argument by pushing down into
getFileSystemByPath method
Remove unneeded NonConfiguredVolume class and test
Remove unneeded (and unused) VolumeManager.getContentSummary
Rename create method with overwrite capability to make API more clear
Retain all exceptions when closing filesystems (as suppressed)
Simplify/shorten implementations for VolumeManagerImpl methods
Make VolumeManager AutoCloseable (it already had a close method)
Fix tests (ZooLockTest -> ZooLockIT, and numerous incorrect usages of
TemporaryFolder)

This is an incremental enhancement to a bunch of internal code related to VolumeManager.

I had a question about the use of TemporaryFolder class but it looks like the tests are passing in Travis so it must not be an issue.

Yes. All the ITs passed, too.


[FEATURE] Make viewmodel of phobos compatible with future (if it's even possible)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.

Use smallshield in future to lower the offhand

that just lowers his position LOL


Lacking documentation on Direct3DCreate9On12

Would it be possible to create an example app which is using the D3D9on12 layer end-to-end? For me IDirect3D9 gets created correctly by Direct3DCreate9On12 but when I call:
g_pD3D->CreateDevice(D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, _hWnd, 0, &g_d3dpp, &g_pd3dDevice);
it fails with HR = 0x8876086C (unable to detect a supported Graphics Card).
Thanks!

Sorry for the silence, we saw this, but haven't had a chance to put together samples. Hopefully we'll get to it eventually but I don't have a timeframe I can promise.

I can't even get Direct3DCreate9On12 to make a 9on12 device.  It ALWAYS creates a D3D9 one.  I have no idea why.
I have some test code like so...
`			IDirect3D9* d3d = nullptr;
IDirect3DDevice9On12* d3dtest = NULL;
D3D9ON12_ARGS dArgs;
		ZeroMemory(&dArgs, sizeof(D3D9ON12_ARGS));
		dArgs.Enable9On12 = TRUE;
		d3d = Direct3DCreate9On12(D3D_SDK_VERSION, &dArgs, 1);
		debug(L"d3d is %08X", d3d);
		debug(L"Query interface returned %08X", d3d->QueryInterface(IID_PPV_ARGS(&d3dtest)));
		debug(L"d3dtest is %08X", d3dtest);

`
Any ideas why this doesn't work?
I've also tried creating a D3D12 device first, which works, then adding it to the override list but still, I'm only getting a D3D9 device and queryinterface always returns no interface.
Do you HAVE to be running a Windows insider build for it to function?  I'm just trying to see performance on Windows 11.

Sorry for the silence, we saw this, but haven't had a chance to put together samples. Hopefully we'll get to it eventually but I don't have a timeframe I can promise.

I can't even get Direct3DCreate9On12 to make a 9on12 device. It ALWAYS creates a D3D9 one. I have no idea why.
I have some test code like so...
IDXGIAdapter1* TryD3D12()
{
	HRESULT hr;

	// -- Create the Device -- //

	IDXGIFactory4* dxgiFactory;
	hr = CreateDXGIFactory1(IID_PPV_ARGS(&dxgiFactory));
	if (FAILED(hr))
	{
		return NULL;
	}

	IDXGIAdapter1* adapter; // adapters are the graphics card (this includes the embedded graphics on the motherboard)

	int adapterIndex = 0; // we'll start looking for directx 12  compatible graphics devices starting at index 0

	// find first hardware gpu that supports d3d 12
	while (dxgiFactory->EnumAdapters1(adapterIndex, &adapter) != DXGI_ERROR_NOT_FOUND)
	{
		DXGI_ADAPTER_DESC1 desc;
		adapter->GetDesc1(&desc);

		if (desc.Flags & DXGI_ADAPTER_FLAG_SOFTWARE)
		{
			// we dont want a software device
			adapterIndex++; // add this line here. Its not currently in the downloadable project
			continue;
		}

		// we want a device that is compatible with direct3d 12 (feature level 11 or higher)
		hr = D3D12CreateDevice(adapter, D3D_FEATURE_LEVEL_11_0, _uuidof(ID3D12Device), nullptr);
		if (SUCCEEDED(hr))
		{
			debug(L"Adapter description: %s", desc.Description);
			debug(L"Adapter LUID: %llx", desc.AdapterLuid);
			return adapter;
		}

		adapterIndex++;
	}

	return NULL;
}

IDirect3D9* d3d = nullptr;

	{
			IDirect3DDevice9On12* d3dtest = NULL;
			D3D9ON12_ARGS dArgs;
			ID3D12Device* d3d12 = NULL;
			IDXGIAdapter1* adapter;

			if ((adapter = TryD3D12()) != NULL)
			{
				D3D12CreateDevice(adapter, D3D_FEATURE_LEVEL_11_0, IID_PPV_ARGS(&d3d12));
				LUID adapter_LUID = d3d12->GetAdapterLuid();
				ZeroMemory(&dArgs, sizeof(D3D9ON12_ARGS));
				dArgs.Enable9On12 = TRUE;
				dArgs.pD3D12Device = d3d12;
				d3d = Direct3DCreate9On12(D3D_SDK_VERSION, &dArgs, 1);
				debug(L"D3D12 memory address: %08X", d3d12);
				debug(L"D3D12 device LUID: %llx", adapter_LUID);
				debug(L"D3D9 memory address: %08X", d3d);
				debug(L"Query interface returned %08X", d3d->QueryInterface(IID_PPV_ARGS(&d3dtest)));
				debug(L"IDirect3DDevice9On12 interface memory address: %08X", d3dtest);

			}
	}

Log output is:
[08-16-2022, 06:49:19] Adapter description: NVIDIA GeForce RTX 3090
[08-16-2022, 06:49:19] Adapter LUID: 9fa8
[08-16-2022, 06:49:19] D3D12 memory address: 034B0348
[08-16-2022, 06:49:19] D3D12 device LUID: 9fa8
[08-16-2022, 06:49:19] D3D9 memory address: 054222E0
[08-16-2022, 06:49:19] Query interface returned 80004002
[08-16-2022, 06:49:19] IDirect3DDevice9On12 interface memory address: 00000000
I've even tried simplifying it like so:
ZeroMemory(&dArgs, sizeof(D3D9ON12_ARGS));
dArgs.Enable9On12 = TRUE;
d3d = Direct3DCreate9On12(D3D_SDK_VERSION, &dArgs, 1);
d3d->QueryInterface(IID_PPV_ARGS(&d3dtest))

.. But I still get E_NOINTERFACE. :(
Any ideas why this doesn't work?
Do you HAVE to be running a Windows insider build for it to function? I'm just trying to see performance on Windows 11.

Do you HAVE to be running a Windows insider build for it to function? I'm just trying to see performance on Windows 11.

Woops, I'm dumb, I needed to call QueryInterface on the IDirect3DDevice9 device and NOT the Direct3D9 interface.  HA!


hiro proto message reorder

Reorder .proto messages so that dependencies are higher in the file. This is needed for Unreal where you cannot forward-declare USTRUCT() types and the C++ compiler is single-pass.

@lugehorsam Sorry for the delay on this one. Can you rebase your pull request?


following() always returns objects of NoneType

django-activity-stream==0.5.1
What's going on here? Why does following() return NoneType objects?
>>> from actstream.actions import follow
>>> a = TRUser.objects.first()
>>> a
<TRUser: a>
>>> b = TRUser.objects.get(id=5)
>>> b
<TRUser: b>
>>> follow(b,a)
<Follow: f42b0d15-7a3f-473f-a4e6-aba8a1 -> a>
>>> followers(a)
[<User: f42b0d15-7a3f-473f-a4e6-aba8a1>]

Everything is fine up to this point. Then when I try following() I get:
>>> following(b)
[None]
>>> type(following(b)[0])
<type 'NoneType'>

I thought perhaps the issue was that TRUser is not a subclass of User, but I see the same behavior when I use a django User.

Probably got similar problem here #245


Dispose Hubs from ActivatorUtilities

We weren't disposing the hubs from Activator.CreateInstance<THub>() in a couple places
@moozzyk @anurse @davidfowl @mikaelm12 @muratg

Hi @BrennanConroy, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Add a test

Added a test

Next, this logic needs to move into a hub activator like component.


Pair dataset

Hi author, I wonder if there is any paired dataset for video background music generation?

To my knowledge, there is no such dataset.


Feature Request: add support for page.waitForSelectorAndEvaluate

In many cases, we wait for an element to be loaded to screen, and right after that we use something like page.$eval to get hold of that element / do something with it.
I think that a method like page.waitForSelectorAndEvaluate (not sure about the name) might be very useful. Its signature might be similar to page.$eval:
page.waitForSelectorAndEvaluate(selector, pageFunction[, ...args])

selector <[string]> A [selector] to query frame for
pageFunction <[function]> Function to be evaluated in browser context
...args <...[Serializable]|[JSHandle]> Arguments to pass to pageFunction
returns: <[Promise]<[Serializable]>> Promise which resolves to the return value of pageFunction

I didn't see many interest for the feature on the bugtracker, closing for now.


Decide on Tools to be Used in the Project

As we are working in a team, it is important that we standardize the tools that we use, so that any output we create is easily interchangeable between each other.
In general , following is a list of categories for which we should find tools for:

[ ] Code Quality
[ ] Time Tracking
[ ] Continuous Integration
[ ] Update Notifications
[ ] Versioning
[ ] Dependency Management
[ ] Documentation
[ ] Project Planning
[ ] Task Management
[ ] UML Editor
[ ] Mockup Editor
[ ] IDE
[ ] Intra-Team Communication

Please reply with possible candidates for each category, and we can decide upon the tool to be used by voting.

My candidates are as follows:

code quality: #3, and coding standards which depend on tech stack
Time tracking: toggle
CI: travis-ci.org, and maybe github webhooks for automatic deployments.
Dependency management: depends on tech stack
documentation: github wiki
Task management: github issues, milestones and projects sections?
IDE: depends on tech stack
Intra-team communication: for free talk, slack or gitter.

ZenHub for Task Management

We can use zenhub with harvest for tracking estimated and actual time. Easy to use and integrated with github.

Experience: we should never use GitHub wiki for project planning. Maintenance is a big issue.

ProjectLibre'mden bir kesit, hem planım hem de gannt chart'ımın birlikte bulunabilme şekli. Bana göre rahat ama bu konuda oylama mı yapsak?

I will update this comment to list the latest candidates before we vote

Code Quality - Codacy / Coveralls
Time Tracking - Toggl / Harvest
Continuous Integration - Travis CI / GitHub Webhooks
Update Notifications - E-mail/Slack
Versioning - GitHub / GitHub Desktop
Dependency Management - TBD
Documentation - MS Office/GitHub Wiki
Project Planning - MS Project / ProjectLibre
Task Management - GitHub Issues / ZenHub
UML editor - Visual Paradigm
**Mockup Editor - **
IDE - TBD
Intra-Team Communicaion - Slack / Whatsapp / Gitter

i think it would be better to find an online tool for project plan. i used ganttpro.com for the previous project but the downside is you dont get a lot of features in the free plan

actually, that's true. it would be nice if every tool is online, so that anyone can view and edit.

Built-in "Projects" tab for task management. Easy to follow board and panels.
"Balsamique Mockups" as a mockup editor.
GitHub "Wiki pages" for documentation purposes.
"Slack" for intra-team communication.

Time Tracking - Google Spreadsheets
Project Planning - MS Project / ProjectLibre / ganttpro.com
MS Project is the best, but too expensive and there is no student licencing is available.
ProjectLibre is good but not online option is available.
ganttPro looks fine I guess. Free plan is more than enough for us I think.
Task Management - GitHub Issues / ZenHub
I prefer to use gitHub's cards (The Project tab), unless zenhub provides extra cool features.
UML editor - Visual Paradigm
I like Visual Paradigm. But you need its application to use it.
Has anyone used the tool mentioned by Suzan: UMLet?
Mockup Editor
NinjaMock is free and good. If you have licence, balzamiq is fine also.
IDE - TBD
For compatibility issues, it is good practice for everyone to use the same IDE.
JetBrains's tools rock.
Intra-Team Communicaion - Slack / Whatsapp / Gitter
If there is another tool that is integrated with github better than slack, we can give it a try. Remember Suzan's mentioning IRC integration with github for documenting the meetings. Or we can try to find a better slack <-> github integration tool. There has been lots of good discussions and decision makings on Slack, it would be good if we can report them to github with a tool.
I've examined the Gitter a bit, this morning. It has integration wit gihub, but as far as I examined it is not more than notifications.

Required tools are decided upon. Closing this issue for now.


Removed nbinsDU and nbinsSS arguments from subroutine NIheterogenousChem

This PR addresses issue #171

Will need better fix later on.


Retry - Add stack trace to code recursively scheduling timers #325

Re-adding the reverted merge - Add stack trace to code recursively scheduling timers #325
I've cherry-picked commits made by @alistairjcbrown to re-file the original PR that was merged and then reverted due to some compatibility issues.

So this fails in IE 11, Safari 9, Firefox. This ties in with https://github.com/sinonjs/sinon/issues/2359 which is about which browsers we officially support and that our docs is out-of-sync. We have dropped IE 11 and Safari 9 in favor of evergreen browsers, so we could ignore them here as well, but it fails in Firefox, which we do support, and we need to handle that somehow.

IE11 and Safari has been dropped. Any chance of seeing if you can get this running in Firefox as well?

Yeah sure @fatso83, I don't know how to do it, but I would like to try! :)
I'm on it.

Thank you @fatso83 for helping out and explaining everything!

just copy-pasting the entire script

Do you mean this script:
"test-cloud": "mochify --wd --no-detect-globals --timeout=10000" that appears in package.json?
I'm just guessing because this script shows Unexpected HTTP status: 401 Unauthorized when running it, and because it's the only one that I could see using the .min-wd config file.

I was simply thinking that if you needed to test certain things in Firefox that failed in the Sauce Labs run you could just copy-paste the entire fake-timers.js script and just manually execute whatever failed in the test runs.
The test-cloud script returns 401 since you do not have credentials setup. I contacted you on Twitter to send you the credentials. You need $SAUCE_ACCESS_KEY  and $SAUCE_USERNAME in your environment. If you pass me an email (on my profile) you can get it right away.

I didn't understand the script way at first, so I decided to try the other way with the local wd.
I'm just a little slow on the take right now :)
If I wanna use the script in the console should I build it first?
And thank you for the email!! 🌼 and for all the help.

If I wanna use the script in the console should I build it first?

As the docs say, you can either build it or use Skypack. Since the latter assumes it's already on NPM, you need to build it for the browser:
npx browserify src/fake-timers-src.js -o lolex.js

If you want all tests in the browser:
npx browserify test/fake-timers-test.js -o tests.js

Hi @fatso83, thanks for explaining - I tried both:
npx browserify src/fake-timers-src.js -o lolex.js worked (I think), the second one threw an error.
I'm gonna try to debug the script, do you know how do I access createClock() and basically all the other methods? I've looked it up on the 'window' object after running the script, but I couldn't find it. I don't know the naming in which it was saved.

Hi @fatso83 (and @benjamingr ) :)
All the tests now pass, I just pushed the fix, when you're available please update me if everything is really ok.
Tons of RegExp lol my head is spiraling!

BTW, I'm trying to run npm run prettier:write and I don't know why it fails..

@itayperry I see why it fails! It's because we are kind of a unix shop, and I see the "C:\Projects\fake-timers" string indicating you are not in that camp 😄 So NPM will run its script in the default shell on your machine. The default shell on your machine is CMD.exe, which does not know the {js,css,ms} syntax at all. It thinks it is a verbatim string to match.
So ... either accept that you need to do a manual prettier --write */*.js (or whatever syntax works on Windows) OR check out WSL2, which works great (I am developing on Windows these days using mainly WSL2 to get all my Unix fixes covered). If you just check out the project on WSL2 it will "just work".

P.S. I have not checked out your code yet, but just a general thing: instead of trying to create One Regex To Rule Them All ™ , you can try to split it up into different "branches" and test something depending on what matches some substring. Just to get the complexity down.

The default shell on your machine is CMD.exe, which does not know the {js,css,ms} syntax at all. It thinks it is a verbatim string to match.

ohhh now I get it! thank you :) I've used the WSL2 once, I'll try and use it again after I finish this PR.

test something depending on what matches some substring. Just to get the complexity down.

I didn't think about it actually... RegExp can be quite intimidating sometimes for me.
For now, what I did was to add an if to check whether the env is Node.js

Update: now all the tests pass, which is wonderful :)
eslint yelled at me lol - it didn't work at all and I think it was updated or something so I tried npm install and now all hell broke loose.. I'm getting many warnings - even about code that's not in the PR.
I fixed the errors but there are still approximately 100 warnings.

Perhaps I should use something like this: /* istanbul ignore if */ ?

Does this mean it actually runs in Firefox?

@fatso83 Yes, it runs in Firefox, and from what I remember also Chrome :)

To me this sound like it's ready to merge :)

@fatso83 can you release this? 🙂 (I guess major after #385 etc)

Hi, @SimenB . Welcome back :smiley_cat:
I actually thought that both you and Benjamin both had NPM release rights. Could arrange for that, rather than having you wait for me.
Not totally sure if there is something else breaking worth thinking about ... not quite sure why #385 would be breaking though. We have targetted Evergreen browsers for some time, so if ES2015+ features have snuck in, that's to be expected. My memory is old and faded, though :shrug:

Ah, even better 😀

@SimenB I released it as v8.0.0 now, since I was a bit unsure about how the removal of TS bindings would affect current installs. Someone might see some things break, so better safe than sorry.

Thanks!

Bare hyggelig :norway:

Funka nesten 😀
There's a bug here, I'm seeing Cannot read property 'stack' of undefined - will dig into this and send a PR

amagad, should we mark v8 as deprecated and move the latest tag to v7.x?

Yeah, probably

Ah, you do have rights already.
$ npm show @sinonjs/fake-timers maintainers

```json
[
  'simenb<EMAIL_ADDRESS>  'mrgnrdrck<EMAIL_ADDRESS>  'fatso83<EMAIL_ADDRESS>  'mantoni<EMAIL_ADDRESS>  'cjohansen<EMAIL_ADDRESS>  'benjamin.gruenbaum<EMAIL_ADDRESS>]


(fix) Use isEqual comparison for isNewOptionSelected in Creatable.

Diandra and I have recently been experiencing weirdness with onCreateOption in react-select. This is prop you use when you want to create a new contact from the dropdown, rather than select an existing one. See the Loom here: https://www.loom.com/share/032f5cd3b0ea421398ce6e3d4aa9781b.
This is an open bug in react-select on 3.1.0, the version we’re running. This pull request copies an open pull request which fixes this issue on the main project.
The main project pull request has not received attention from the maintainer, so we made the decision to fork the project and fix it ourselves to unblock PCM.
Created this ticket to track follow up: https://warrenpay.atlassian.net/browse/FRON-2101.
I've set a reminder for myself to check the project every two weeks for updates.

Keeping branch around to use like we do with our fork of Cleave.js in package.json.


Is it possible to add freelancer scraping?

It'd be super useful being able to see freelancer experience, rates, etc to assess the market/competition as well as who to hire if an employer

Unfortunately, this is not possible. Upwork doesn't show this information, even if you are logged in. And as a client, you can only see information about the freelancers who applied to a job you posted, as far as I know.


this.fireUploadStart is NOT triggered in FileUploader.js -> FileUploader.prototype.upload = function()

OpenUI5 version: 1.28
Browser/version (+device/version): any
Any other tested browsers/devices(OK/FAIL): all failed
URL (minimal example if possible): n/a, the issue is in FileUploader.js
User/password (if required and possible - do not post any confidential information here): n/a
Steps to reproduce the problem:
When UploadCollection control and multiple files selection is used in version 1.28 then even BeforeUploadStarts is not triggered for each file.
The reason is the FileUploader,js does not fire even BeforeUploadStarts, please have a look here:
https://github.com/SAP/openui5/blob/rel-1.28/src/sap.ui.unified/src/sap/ui/unified/FileUploader.js
function :: this.fireUploadStart is triggered in FileUploader.js -> FileUploader.prototype.upload = function()
before block ::
aXhr[j].xhr.open("POST", this.getUploadUrl(), true);                             if (this.getHeaderParameters()) {                                 var oHeaderParams = this.getHeaderParameters();                                 for (var i = 0; i < oHeaderParams.length; i++) {                                     var sHeader = oHeaderParams[i].getName();                                     var sValue = oHeaderParams[i].getValue();                                     aXhr[j].xhr.setRequestHeader(sHeader, sValue);                                     aXhr[j].requestHeaders.push({name: sHeader, value: sValue});                                 }                             }
after block :: NULL
expected block :: (taken from release 1.30)
var sFilename = aFiles[j].name;                             var aRequestHeaders = this._aXhr[j].requestHeaders;                             this.fireUploadStart({                                 "fileName": sFilename,                                 "requestHeaders": aRequestHeaders                             });                             for (var i = 0; i < aRequestHeaders.length; i++) {                                 // Check if request is still open in case abort() was called.                                 if (this._aXhr[j].xhr.readyState === 0) {                                     break;                                 }                                 var sHeader = aRequestHeaders[i].name;                                 var sValue = aRequestHeaders[i].value;                                 this._aXhr[j].xhr.setRequestHeader(sHeader, sValue);                             }
We can also see that this part is covered in release 1.30 and higher.
What is the expected result?
Event this.fireUploadStart is triggered in FileUploader.js -> FileUploader.prototype.upload = function()
What happens instead?
Event this.fireUploadStart is NOT triggered in FileUploader.js -> FileUploader.prototype.upload = function(), so in case of multiple files upload all files have the same name as the first one, because there is no way to update file name in the request header parameters set
Any other information? (attach screenshot if possible)
Adjustments to control UploadCollection is currently made by us for Fiori application My Travel and Expenses (MTE).

Hi Siarhei,
when working for SAP, please report issues using the normal internal BCP system.
I have opened ticket<PHONE_NUMBER> there for this issue.
Regards
Andreas

Hi Andreas,
Thank you! I have used this thread this time because that is implementation related we are currently doing, but next time I will use BCP system.
Kind Regards,
Siarhei

Hi Siarhei,
the mentioned UploadStart event was introduced with 1.30 and is therefore not available with 1.28. Unfortunately it's not possible to introduce it in a compatible way by making a fix. The recommendation from my side would be to upgrade to SAP UI5 version 1.36 as a lot of fixes and features needed by the upload collection have been made since then.
Best regards
Stanley

Hello Stanley,
Thank you for your reply!
Actually, as it's been Go Live blocker for us, we've made a decision to go to 1.36, even that it pushed us to upgrade SAP_BASIS.
Kind Regards,
Siarhei

Closing, as this is not a bug, but a not-yet available featrue in an older version, which unfortunately cannot be downported. Sorry for the inconvenience.
Regards
Andreas

Hi Andreas,
I have encountered a peculiar problem. My Upload Collection is working perfectly fine when I upload a file the first time (Single File upload Multiple = false). But the next time I upload a different file then the fireUploadStart event throws the following error: File upload failed:
Cannot instantiate object: "new" is missing!. I am using SAPUI5 version 1.44.1.
Attaching screenshot for your reference.

I also faced this problem,when i was upload file.I want to get the file name before uplaod.but the fileuploader didn't trigger the function in the controller.so i don't konw how to solve the problem.


installations performed under dolmades debug flood the hosts menu with entries

when installers are being run in debug mode they will create menu entries in the users linux desktop.
not nice! I remember theres a wine setting which can suppress this behaviour...

solution: use this for dolmades debug :
WINEDLLOVERRIDES=winemenubuilder.exe=d wine setup.exe


failed in many know_people(1W<>)

face_recognition version:  unknow(the newest from apt install)
Python version: 3.5.2
Operating System: Ubuntu 16.04.6 LTS

Description
ps: there are 1w pictures in the  /home/ubuntu/face_pic/
a long time after i runned the command,this result was returned:
Traceback (most recent call last):
  File "/usr/local/bin/face_recognition", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.5/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.5/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/face_recognition/face_recognition_cli.py", line 102, in main
    known_names, known_face_encodings = scan_known_people(known_people_folder)
  File "/usr/local/lib/python3.5/dist-packages/face_recognition/face_recognition_cli.py", line 20, in scan_known_people
    img = face_recognition.load_image_file(file)
  File "/usr/local/lib/python3.5/dist-packages/face_recognition/api.py", line 85, in load_image_file
    im = im.convert(mode)
  File "/usr/local/lib/python3.5/dist-packages/PIL/Image.py", line 934, in convert
    self.load()
  File "/usr/local/lib/python3.5/dist-packages/PIL/ImageFile.py", line 249, in load
    "(%d bytes not processed)" % len(b)
OSError: image file is truncated (2 bytes not processed)

What I Did
run this command:
face_recognition --tolerance 0.42 /home/ubuntu/face_pic/ /home/ubuntu/604446db-52e3-4f30-b90f-89c86bb7dfe7

(no answer)