[Storage] ConnectionString requires EndpointSuffix

I am trying to use the Blob connection string sample:
https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/storage/storage-blob/samples/v12/typescript/src/connectionStringAuth.ts
With the first example shown in the Storage Connection String docs:
DefaultEndpointsProtocol=https;AccountName=myAccountName;AccountKey=myAccountKey

https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#configure-a-connection-string-for-an-azure-storage-account
It fails with this error:
Error: Invalid EndpointSuffix in the provided Connection String

It works if I add the default EndpointSuffix:
DefaultEndpointsProtocol=https;AccountName=myAccountName;AccountKey=myAccountKey;EndpointSuffix=core.windows.net

But I do not believe the EndpointSuffix is required in most other languages.

/cc @jeremymeng any thoughts on this one?

Looks that instead of throwing error, we could use a default value of "core.windows.net"?
https://github.com/Azure/azure-sdk-for-js/blob/f5de1196170c647e9dc9bef0833640b7bb5572e7/sdk/storage/storage-blob/src/utils/utils.common.ts#L208-L212

I agree. We should have a default endpoint value. I'll fix it.

I would like to note that this is also an issue in the data-tables SDK, See line 46 in https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/tables/data-tables/src/utils/accountConnectionString.ts
    if (!endpointSuffix) {
      throw new Error("Invalid EndpointSuffix in the provided Connection String");
    }


how-to-attend-stream: Copy accessibility notes from CR workshop pages

Mostly the same as what the workshop pages had, but it's relevant to
other courses so copied here.
Review: worth a read, I probably have forgotten some things, too.

Thanks!


[MM-T2086] Cypress test for changing password and checking email and timestamp

Summary

Cypress test for MM-T2086:
Check that password setting (in profile settings) shows password was updated at current time.
Additionally, check that an email notification about the password update is received.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/18818

Hello @Borknab,
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.

/release-note-none

Triggering e2e testing with options:
<nil>

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

/e2e-test

Triggering e2e testing with options:
<nil>

A pipeline with the same environment variables is already running.
Please cancel it first with /e2e-cancel, or specify different environment variables.

@josephbaylon @furqanmlk nice! Thanks guys, glad to contribute!

Hello everyone! Why is the PR still not merged? Is there anything else I need to do?

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!

@furqanmlk @josephbaylon Hello guys! I received a notification that the PR got stale, though I don't understand why the PR has not been merged yet? Is there anything else I need to address?

@Borknab I've notified Furqan about this PR. As a side note, after you make the requested changes, please hit the re-request review to the person you wanted another review from so that he/she is notified. Otherwise, it may go off radar.
Thanks for notifying us directly though.


OSS-Fuzz: infinite loop in spirv-opt, in DeadBranchElimPass::FindFirstExitFromSelectionMerge.

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=38172&q=spirv-tools&can=2&sort=summary
The function keeps considering the cycle:
-> 55 -> 56 -> 60 -> 61 -> 55 -> 56 -> 60 -> 61 ...
@s-perron would you be able to take a look?

I believe this is an invalid test case because the cfg is not structured.  I have attached a visual representation of the cfg.  Notice the branch from block 61 to block 55.  That branch is not part of the loop with loop header block 55.  In order to reach block 61 from 55, you have to go through the merge block for the loop, block 56.
@alan-baker Do you agree that this is something that the validator is missing?

I agree this seems wrong. I'll take a look.

The validator isn't able to perform much validation for unreachable blocks. 61 -> 55 looks like an invalid back edge, but the traversal in the validator doesn't qualify it as such because 61 is unreachable.

Aside: I think there's a strong case for arguing that structurally unreachable blocks should not be allowed at all, or that anything goes in such blocks with respect to control flow. (See here for what I mean by "structurally unreachable").

Right I missed that 61 is unreachable.  However, it is the merge block for the infinite loop, which places it outside of the construct.  If this is not something that the validator can fix, I can fix dead branch elimination.  Dead branch elimination should also delete the branch in block 61 so later passes do not have to worry about it.

This is being caught as invalid now. I believe structural dominance fixed it.


Metrics for raw/trim coverage

It would be nice to compute a new metric for the trim algorithm and/or analysis of the raw datasets: the raw coverage. The raw coverage is the total number of bases contained in the reads divided by the genome length. We can allow the computation of this by an input of the FASTA genome or the genome length as parameter, or provide the number of bases present in the raw reads vs. trim reads to see how much we lose.

Changed to beta, because it could be implemented directly in the new tool for trimming.

The new tool have a histogram of read lengths before/after trimming. This could be used to compute the raw/trim coverage if a reference genome is provided. Moved to version 1 to decide if we really need that or its enough with the histograms.

Lack of interest for this from the original user who requested it (it was enough with the provided histogram). Closing.


Added travis.yml

Your CONTRIBUTING.md states that you are looking for a third-party service to run your tests on.  You can log in using your github account and add your repository. Every time you push a new commit or someone submits a pull request, travis will build the commit and notify you if it failed. You can learn more about travis here.
This PR adds a .travis.yml so that travis knows how to run your tests. It currently tests clang 3.4 and g++ 4.8. For an example how this might look see https://travis-ci.org/UnrealQuester/better-enums/builds/68665505

I had considered Travis and decided not to use it for now. The incremental benefit from testing on two Unix compilers (rather than one) is much less than from testing on both MSVC and a Unix compiler (rather than only one of those). This change may help people developing on MSVC the most, but there are more immediate challenges with MSVC, such as running cl.exe from the command line. So, this change could be nice for the time being, but I would prefer something more conclusive.
Perhaps Visual Studio Online can help with MSVC testing, and then we can use Travis for Unix testing. I spent some time looking into that setup, but ultimately wrote CONTRIBUTING.md instead :)
I don't have enough experience to know this: is it relatively easy to get Travis to test on more than one version each of clang and gcc?

This should be trivial to accomplish. If you are fine with using travis I could write up a matrix for all compiler versions mentioned in test.py.
For windows there is appveyor, but I remember that being a pain to set up.

I don't remember why I rejected AppVeyor before. The reason may since have become moot. I'm looking at it again now.
Getting automated builds on MSVC is a high priority compared to clang/gcc, so I think the best thing to do is for me to focus on setting up AppVeyor. If, after that, it looks straightforward to also build with clang and gcc in AppVeyor's Windows environment (as weird as that sounds), then I will opt for that. Otherwise, we should extend this travis.yml to build on more gcc and clang versions, and use both AppVeyor and Travis.
My reasoning is that a typical developer on a Unix-like system is probably using something like gcc 4.9 or clang 3.6 locally. In my experience, the behavior of recent versions of gcc and clang is mostly equivalent for the features enum.h uses, so running an automated test is unlikely to reveal anything – the exceptions to this are gcc before 4.7, so those are the most useful to include in travis.yml. On the other hand, testing the code on MSVC is quite likely to reveal problems. The converse doesn't hold. Code written to compile on MSVC is pretty likely to work on gcc/clang. In short, MSVC is the main problem compiler, followed by old gcc.

While working on a version with all compilers installed I noticed that g++-3.4 is in that list. This compiler version is pretty old. So old in fact, that it is not even in any package repository available for ubuntu precise. As a result, I have been unable to install it. Would you mind if I removed this compiler version from test.py?

I think you mean g++ 4.3. I prefer you not remove any of the compilers covered by test.py --all, but either I or you can add an option such as test.py --travis, or the like.
test.py --all is really only for me to run. It covers the compilers that I have access to and decided to test on, for the sake of thoroughness. I never intended it for general usage either by users or CI services. If I limit test.py --all to only what Travis/AppVeyor support, I give up decision making on supported compilers to Travis/AppVeyor/the Ubuntu maintainers, which I am not willing to do. Consider the following paragraph.
What it's looking like now is that CI services will cover a bunch of gcc and clang versions (Travis), and only some recent versions of MSVC (AppVeyor). If AppVeyor still supports even VS2013, they don't make it obvious. Since I want to cover more than what AppVeyor seems to support, I will need to keep test.py --all for my own use even after we set up CI. CI with AppVeyor and Travis will only be a useful approximation to whether a commit okay – the final say will be after I (or someone with too many compilers) is able to confirm with test.py --all.
I am testing out AppVeyor now, by the way.

Will try to get a build matrix running on travis with as many compilers as I can.
Appveyor images do have VS2013 installed. I can confirm that Windows Server 2012 R2 does.

Cool, thanks, and thanks!

Quick update: The build matrix currently looks like this.
Just need to add some options to test.py for the older compiler versions.

Thanks. I see that you are not using test.py's internal "matrix", which is the same conclusion I am coming to with AppVeyor. I think it's time to reengineer test.py slightly. I'm creating a simple "driver" module in Python that knows how to start each compiler that Better Enums positively claims to compile on, in each supported configuration for that compiler. That should make it easier to break up test.py --all into multiple independent calls to test.py, one per CI build matrix row. It should also help to run locally with the right options for whatever compiler the developer is using.

This looks like a use case for CMake, actually. We can check if a compiler supports a specific flag with CHECK_CXX_COMPILER_FLAG and starting with 3.1 we can also check for specific features. This way we don't have do update the list for every compiler. There are also script out there for cmake < 3.1 that do this. The only problem would be testing multiple compilers in one go. We would have to write a script that calls cmake for every version.
For now, I could just add options to test.py for modern_gnu, gnu_re_constexpr and gnu_pre_enum_class and configure in travis what compiler needs what flag.

I actually started on that at some point after I sent the last message. I uploaded the CMake branch, in the interest of coordination. It's still very basic. You can see the diff here: https://github.com/aantron/better-enums/compare/cmake
I'm a CMake newb, as in this is the first time I use it, so don't hesitate to give any advice if you have experience.
Also, I checked out options for building on multiple clang/gcc versions in AppVeyor yesterday, and decided that it's easier to just use Travis side-by-side.

The current matrix looks like this. The clang builds fail because they have a test case which compiles with c++98. enum.h uses char32_t and char16_t if clang >= 2.9. But as these types are a c++11 extension and clang is compiling these with c++98 it (correctly) fails to build.
g++ only passes these tests because it also checks for GXX_EXPERIMENTAL_CXX0X and __cplusplus.

Going to take a look at the CMake branch now.
Not sure how much of cxxtestgen we need for this. This might be straightforward with FindCxxTest.cmake.
Globbing files is potentially dangerous. CMake finds all files matching the glob and creates a solution/makefile/whatever for them. If the list of files change, cmake has to be re-run.
If you manually add the files, you just have to re-run make.
But using CMake is a good idea. We can generate native VS .sln files and run them.

I am aware of the danger of globbing, but I am not aware of a good way to do this automatically. I'd rather not resort to generating CMakeLists.txt. That's a little ridiculous :)
As for the clang issue, the feature detection code is indeed apparently wrong. My local clang accepts char16_t and char32_t in C++98 mode, however. Quite interesting. Anyway, I am checking what __cplusplus is defined as in versions of clang where C++11 support was experimental, and then making a patch.

Since I'm having trouble reproducing the problem with the compilers I already have installed, can you give this a try in Travis? https://github.com/aantron/better-enums/compare/clang-char-types
This check might miss some old clang versions that took the -std=c++0x flag, if they still defined __cplusplus as 199711, but I don't have any such compilers handy, and I am not currently aiming to support them either.

You can check the status of the new build with your fix here.

Cool, watching it.
In the interest of me not wasting your time by us working on the same thing, I suggest we do this:

I get testing working with CMake and make sure it's suitable for local builds on my machines and in AppVeyor. This should be done by the end of today (my time), maybe tomorrow.
It should then be straightforward to adapt the testing scripts to Travis.

We will have one build matrix row per combination of compiler/configuration.

Sounds good. We will see how big the build matrix gets for travis. While travis does not have a upper limit in total build time and size, the huge delay between single builds blows up the total build time. The current build was created on hour ago and only completed 4 out of 11 builds. We might want to have one row per compiler and iterate over all possible combinations in the build script.

I am also reconsidering one row per combination for another reason, which is it might be a good idea to give developers the ability to test all configurations on their compiler locally. Perhaps it won't be fast enough to use while first implementing a change, but these tests can be run before submitting a pull request. Once we have this ability, it will be easy to trigger it in Travis/AppVeyor, and we can have one matrix row per compiler.

Ok, the changes are in master now. You can see the AppVeyor build status here.
It should now be possible to test in Travis by running make COMPILER=[compiler] unix in directory test/. The time utility is no longer necessary, as timing tests are not done automatically. There is one build matrix row per compiler. The Makefile will try all configurations. Configurations not supported by a particular compiler are "vacuous" successes. CxxTest is still required.

Rebased my work on top of master und currently running the tests.

You may want to also try make default-all. I'm guessing CMake will detect the compiler you are installing. make COMPILER=c++ unix looks a little funny :) The point of that target is to select a compiler when the CMake default isn't the right choice.
Also, some upcoming nits:

Do you need ppa:dhart/ppa? It looks like you were using that to get CxxTest, but you are currently cloning it from GitHub.
I'm assuming you will eventually flatten these into one commit. For consistency, please add a period to the commit message.

After this goes in, I will commit an updated CONTRIBUTING.md and CONTRIBUTORS.

I'm seeing this in the Travis testing output: /bin/sh: 6: 0: not found. Try incorporating this fix. If it works, I will commit it to master. I'm having a small amount of trouble reproducing the problem, since apparently my sh is a symlink for bash.

Fix added.
PPA removed.
Changed the compiler to $COMPILER. I need to specify the compiler because the travis image already contains a c++ compiler and I need to make sure CMake picks our compiler.

All tests passed for the latest build. Is there anything else you would like me to add?

Looks good :) Ready for the squashed & rebased patch.

@aantron done.

In as 1769fbb6b797bda62a53d867661845ebfb2eb7d6 and will close when Travis tests pass. Thanks!


GL.createCapabilities: add way to exclude arbitrary extensions

Description
Proposal in the title. The current way of achieving this basically involves adding your own logic after checking each specific extension flag on GLCapabilities, which is relatively brittle (e.g. when you aren't the only client of the GL and want full application testing), and not easily extended.
I believe this should generally work with regard to LWJGL itself, since extensions are by design optional features.

An easy way to control extension use for the sake of external tools, e.g. NVIDIA Nsight, which fails with use of extensions like NV_command_list and NV_fill_rectangle.
A way for users to disable extensions, either for troubleshooting purposes or as a workaround for application and driver bugs.

Solutions
Probably the easiest way would be to add a parameter to GLCapabilities createCapabilities(boolean forwardCompatible) called Set<String> excludedExtensions that is simply subtracted from the set reported by the driver just before passing them into GLCapabilities. Then it would be up to the developer to decide how best to inject them.
An alternative approach would be to read a comma-delimited list from a System.getProperty, which has the advantage of allowing user control without requiring thought or effort from developers. This may not be a universally desired feature, however. Applications that don't actually check for extensions could be broken, but the responsibility would clearly rest with the user in this case, imo. The downside is it wouldn't be programmatically controllable without manipulating System properties and doing String processing.
Problems
It's possible that a driver reports an extension that implies the driver cannot be used as though the extension didn't exist. I'm not intimate enough with every extension to know, but they commonly change language in the spec, which I could see having this effect (possibly unintentionally.) However, this sounds like a violation of the entire concept of extensions.
Conclusion
Hopefully this wasn't too formal, I just wanted to be thorough in making a suggestion. It's possible there's a better method of achieving this, in which case, do let me know.
Thanks for reading!

Excellent! Thanks for your hard work!


Webview on many android devices is super pixelated after upgrading to 3.27

Steps to reproduce

Upgrade to 3.27
Run a flutter webview app on a Samsung a50
It's pixelated

Expected results
The expected result is for the webview to not be pixelated.
Actual results
The webview is pixelated.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

@Codewealth
I see that you have commented in this issue. Are you seeing this without any changes in resolution and by default if running the example app ?

@Codewealth I see that you have commented in this issue. Are you seeing this without any changes in resolution and by default if running the example app ?

Yes, this issue is happening on the default settings of the android devices we have. We have not changed any settings and in find, some of the devices don't have settings for resolution. This issue actually is related to the link you posted. This issue was introduced in 3.24, we just didn't notice it as we didn't update to 3.24 but rather to 3.27.

Thanks for the update. Using the plugin example app with below dependency versions and running on S10+ device (Android 12) on latest stable (3.27.1) version and latest master, I do see the pixelated webview as shown below:

This didn't occur in previous stable (3.24.4).
The issue looks similar to https://github.com/flutter/flutter/issues/159688 but in that issue, the OP says, the pixelated behavior occurs after changing resolution on specific device.
I will keep the issue open as regression and for team's tracking.
  webview_flutter: ^4.10.0
  webview_flutter_android: ^4.2.0

I will close this as duplicate of https://github.com/flutter/flutter/issues/159688 and based on https://github.com/flutter/flutter/issues/159688#issuecomment-2549755637


fontWeight should allow numbers

See https://github.com/DefinitelyTyped/DefinitelyTyped/pull/23808#discussion_r169737635. The schema currently only allows strings.

FWIW, this is not an oversight. The schema and docs type fontWeight as a string intentionally. The parameter does not accept arbitrary numbers, nor should it. CSS allows specific numbers: 100, 200, up to 900. (See https://developer.mozilla.org/en-US/docs/Web/CSS/font-weight) Perhaps this could be an enum instead?

It also doesn’t accept arbitrary strings, though.
JSON Schema supports min, max, and multiple of but also enums. Both are more accurate than only allowing strings.

See my last comment above :)

Fixed in<EMAIL_ADDRESS>onwards. We now use an enum for all legal values of fontWeight, including both strings and numbers.


Deprecate the non-benchmarking uses of TickDuration in std.datetime.

This gets us another step closer to being able to deprecate TickDuration.

:white_check_mark:

I wonder if I should invoke a variant of Cunningham's Law: Merge this pull request in order to summon other reviewers.

Looks good except for one potential problem.
Moving from templated to non-templated methods without const parameters could break currently compiling code. Should this be considered?

Moving from templated to non-templated methods without const parameters could break currently compiling code. Should this be considered?

I'm not aware of any potential code breakage here and don't know what you're referring to. Previously, the functions in question were templated but only accepted Duration and TickDuration. Now, they're separate functions which explicitly accept Duration and TickDuration. That shouldn't break anything. It's true that when I originally did std.datetime, I mistakenly used in on a bunch of parameters, because I didn't understand it properly at the time, and I did not put in on the now non-templated functions, but the constness of the parameters shouldn't matter at all, and scope currently does nothing for these types. The function arguments are taken by value, and they're value types, so they're copied. Their constness is irrelevant to the caller.
So, what are you seeing that I'm missing? Or did you think that more types than Duration and TickDuration were accepted previously?

Your point about function args being by-value and being copied was something I had forgotten.
:+1:

Auto-merge toggled on


Update ghost to 1.0.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

The install fails now. I see the name of the app inside the .zip file has changed.

Thank you for noticing. Care submitting another PR with a fix?

yes, but i'm not sure what's going wrong, seems to be something with the zip file name and the name of the app. Also, the folder /usr/local/Caskroom/ghost is not created

There is a just a need to change line app "ghost-#{version}-SIGNED/Ghost.app" to app 'Ghost.app'.

Yes i've noticed, but even after changing that it fails... I assume I can run brew cask install ghost while editing the file to see if it works? Or do I need another workflow for this to test?

I keep getting
==> Verifying checksum for Cask ghost
Error: It seems the App source is not there: '/usr/local/Caskroom/ghost/1.0.0/ghost-1.0.0/Ghost.app'

and when i look in /usr/local/Caskroom/ there is indeed no ghost folder

You can run brew cask install on a local file that has been changed inside a current directory:
brew cask install ghost.rb

In this way, the modified cask file will be used.

Thanks! will try that

Fixed in #26700


briefcase package, error in windows, the build work, the app open but cant compile anithing.

(wunjo) PS H:\ia\wunjo.wladradchenko.ru-main\portable> briefcase package

** WARNING: No signing identity provided                               **

Briefcase will not sign the app. To provide a signing identity,
use the `--identity` option; or, to explicitly disable signing,
use `--adhoc-sign`.

[wunjo] Building MSI...
Compiling application manifest...
Compiling... done
Compiling application installer...
wunjo.wxs
wunjo-manifest.wxs
Compiling... done
Linking application installer...
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(7199) : warning LGHT1076 : ICE60: The file filF5E8DB8E4102951E3A509A6C325A79BA is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(7205) : warning LGHT1076 : ICE60: The file fil27F48996A851EEF3E69C743F02E20EC6 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(7211) : warning LGHT1076 : ICE60: The file fil84A5823952D12DBE3E58C5D215A6794B is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(7217) : warning LGHT1076 : ICE60: The file fil5F37FC6ED022340FBD6A66A552B5794D is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16983) : warning LGHT1076 : ICE60: The file filFA56B82AFD7E905E82BCC5549B58ACF5 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16986) : warning LGHT1076 : ICE60: The file fil1257BC7A45E9CCB44B5D58901B791E38 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16989) : warning LGHT1076 : ICE60: The file filFB1DEC1BC03800BCDBA8458D29D25DBD is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16992) : warning LGHT1076 : ICE60: The file fil4C4AE428D50598D6F28EEEFE74EBEFE1 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16995) : warning LGHT1076 : ICE60: The file fil639BB5793B86E2E02E52710602CC01EF is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(16998) : warning LGHT1076 : ICE60: The file fil7780A2CB4076B3C896045F19A87F400A is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17001) : warning LGHT1076 : ICE60: The file fil0C34475C8EF86122A73F3C3099D638E8 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17004) : warning LGHT1076 : ICE60: The file fil9B0C46927834A29B63685B46CCB9A5E4 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17007) : warning LGHT1076 : ICE60: The file fil40BA84BE3C99CF9874E590294E2929E7 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17010) : warning LGHT1076 : ICE60: The file fil209FAA2C5F012FD2DB9DEC3BF8F0001A is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17013) : warning LGHT1076 : ICE60: The file fil0B5B172BE478D66250D56ECA4D7D6FA3 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17016) : warning LGHT1076 : ICE60: The file filFD150E313DC40C5B46A8AF6222C4FC7A is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17019) : warning LGHT1076 : ICE60: The file fil1E5D34E22EA1D3FCE9A39C2B8BB435DF is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17022) : warning LGHT1076 : ICE60: The file filB5183121DCDD8DAC62871760FD7C1067 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17025) : warning LGHT1076 : ICE60: The file fil844C26D7E6C2CA410C89170A7F93476B is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17028) : warning LGHT1076 : ICE60: The file fil2DE1D004C173118DE042B0C259AA725E is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17031) : warning LGHT1076 : ICE60: The file filF9E7BF2B7E5B778DA311E58F09B9DA25 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17034) : warning LGHT1076 : ICE60: The file fil607120AB67899383769523711DB907C8 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17037) : warning LGHT1076 : ICE60: The file filCA8A5F8BA260A9C59BAEF6655CC45D04 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17040) : warning LGHT1076 : ICE60: The file fil001DA59D301F6A5E1881AFEE273D843A is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17043) : warning LGHT1076 : ICE60: The file filDCF180F036CC702E2F2F7EE4B3B566A1 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17052) : warning LGHT1076 : ICE60: The file fil7CFE43D0BE49FD060CBD1D46F0392078 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17055) : warning LGHT1076 : ICE60: The file fil250D619EC793734ACD252F8FD938470A is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17058) : warning LGHT1076 : ICE60: The file filF60DD131E7DE28A714BA64AE899BE919 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17061) : warning LGHT1076 : ICE60: The file fil3EFBA07AC3672BFBBB3D1E3580D0980C is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17064) : warning LGHT1076 : ICE60: The file fil712C897C067DDF03B95DA2C512903DFB is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17067) : warning LGHT1076 : ICE60: The file fil1700653885C516498B262C27DEA65153 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17070) : warning LGHT1076 : ICE60: The file fil3F240E1AA70835D2046F421BBE05B764 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17073) : warning LGHT1076 : ICE60: The file fil0F6E3CA59997F63AEEF9516DB50E9762 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17076) : warning LGHT1076 : ICE60: The file fil0038C5C2406506395965003D4F99DD14 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17079) : warning LGHT1076 : ICE60: The file filD2599584109A7FEDED1DD8510DD031A7 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17082) : warning LGHT1076 : ICE60: The file fil56FE8AACE2B03C50C184FA3C917ECF14 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17085) : warning LGHT1076 : ICE60: The file filAC3CE1EFC7FC38692594AA6D4893F70B is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17088) : warning LGHT1076 : ICE60: The file fil30F0C5EF90EA412C864433EB4209BA14 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17091) : warning LGHT1076 : ICE60: The file fil495B071AD61B20AD457E5005D6E22364 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17094) : warning LGHT1076 : ICE60: The file fil27228CA6FF465C5E37A2B50300613E54 is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17097) : warning LGHT1076 : ICE60: The file fil8E4FADCC47EA4D581CADBF1034E01FED is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
H:\ia\wunjo.wladradchenko.ru-main\portable\build\wunjo\windows\app\wunjo-manifest.wxs(17100) : warning LGHT1076 : ICE60: The file filB8BBB096C9D7AA5E3F4A44245E1D354B is not a Font, and its version is not a companion file reference. It should have a language specified in the Language column.
Linking... done
[wunjo] Packaged dist\Wunjo Wladradchenko AI-1.4.0.msi
(wunjo) PS H:\ia\wunjo.wladradchenko.ru-main\portable>

ah! i find Wunjo Wladradchenko AI-1.4.0.msi in dist folder, installing :D

dont work :/
The part that speaks does not work for me either, it asks me to create the folder and download a json?
or does the json have to download something else?
Yes, I can take a face, mark the area of the face, choose an audio, but he always tells me that he doesn't see the face or things like that.
try to use installer stable but it gives me python error.
Traceback (most recent call last):
File "\app\wunjo_main_.py", line 1, in
from wunjo.app import main
File "\app\wunjo\app.py", line 3, in
import torch
File "\app_packages\torch_init_.py", line 17, in
import ctypes
File "", line 259, in load_module
File "ctypes_init_.py", line 7, in
ImportError: Module use of python310.dll conflicts with this version of Python.
im supous the python 3.10,

Hello, zephirusgit,
It seems you're encountering an issue with the Windows installer creation via the Briefcase package. Since Briefcase is a third-party library, it would be more appropriate to raise this issue in their official repository.
You could consider pinning your Briefcase version to 0.3.14 as a workaround. The issue may be version-specific.
Regarding your query about setting up deepfake, I've recently updated our documentation. You can find a manual setup guide here. Additionally, we have a Windows installation video tutorial available here (I will record this video on English after version 1.5).
I've also resolved some path-related issues specific to Windows in our upcoming 1.5 update. Though it's still in development, you may find it helpful to switch to the v1.5 branch, where bug fixes are actively being rolled out.

Additionally, I would like add information what I use in project a Python 3.10.12

By the way, I would like to note that briefcase package creates an installer. However, when you did a briefcase build. In the build folder, you will already find a ready-made application that you can use as a ready-made application.

2023-09-05 10:36:51.181 | INFO     | speech.tts.synthesizer:_load_text_handler:353 - Loading text handler
2023-09-05 10:36:55.257 | INFO     | speech.tts.synthesizer:module_from_config:322 - Loading tacotron2 module
2023-09-05 10:36:56.249 | INFO     | speech.tts.synthesizer:module_from_config:322 - Loading waveglow module
2023-09-05 10:37:01.342 | INFO     | speech.tts.synthesizer:load_user_dict:267 - User dictionary has been loaded
2023-09-05 10:37:01.342 | INFO     | speech.tts.synthesizer:init:62 - Synthesizer Russian man is ready
New voice models added
2023-09-05 10:37:01.342 | INFO     | speech.tts.synthesizer:text_to_audio_gen:114 - ╨┐╤А╨╕╨▓╨╡╤В ╨┤╤А╤Г╨│
ERROR:root:

Resource punkt not found.
Please use the NLTK Downloader to obtain the resource:

import nltk
nltk.download('punkt')

import nltk
import ssl
try:
_create_unverified_https_context = ssl._create_unverified_context
except AttributeError:
pass
else:
ssl._create_default_https_context = _create_unverified_https_context
nltk.download()

import nltk import ssl
try: _create_unverified_https_context = ssl._create_unverified_context except AttributeError: pass else: ssl._create_default_https_context = _create_unverified_https_context
nltk.download()

From the provided information, it looks like you encountered a problem related to missing resources for the Natural Language Toolkit (NLTK). Specifically, the 'punkt' tokenizer models. Becuase of nltk.download('punkt') used urlib to download file.
However, in some environments, downloading resources directly using the nltk.download() function can encounter SSL certification issues.
Your solution aims to disable SSL certificate verification, allowing NLTK's downloader to retrieve data without encountering SSL issues.
Here's what you should consider:

Disabling SSL verification can have security implications.

If you decide to implement this workaround, make sure it's conditional, will be more clear approach to allow users to choose whether they want to disable SSL checks or not.

Thank you what you noted what users can encountered. I have changed the code in branch https://github.com/wladradchenko/wunjo.wladradchenko.ru/tree/v1.5.1 and the soon it will be in main. I used custom download function with requests without default approach of NLTK.  If you encounter bugs in v1.5.1 feel free to contact.


Suggestion for 'details' popup window

It's beyond belief that Amazon's web team hardcodes pixel widths here in 2020.
I've resisted the urge to show a 'before' picture for confidentiality but can do so if reached at the obvious gmail address.  Now that I've dug unto the CSS, I understand why the popups for item details are unreadable on mobile. :-(
As a developer myself, I know that what you really want is a PR that you can just click 'merge and close', but I also know that you're likely to debate how and where to best integrate this and that since this is essentially a one-liner, I hope you can easily copy-and-paste this into the official release without such back-and-forth. (Which I will do if that's really needed.)
The simple addition of
.a-popover {
width:90%;
}
to the bottom of my stylebot makes "See details" actually look reasonable for any width that I can resize my browser to on a 27" display. Notably, the "narrow" sizes don't simply break and if I could do this on mobile chrome, I wouldn't have to the screen sideways to read the 'Details' pop-up (Hard to believe their developers never tested on a mobile device. Sigh).
OK, I started with a one-liner, but then I looked carefully at the rest of that dialogue. This disease runs deep, but I lack the CSS mojo to "fix" it. Their developers were completely too clever with jquery (OMG, it's 2010!) instead of just making a stinking .flex layout and letting that right hand column grow-and-flow.
id="vvp-product-details-info-container"
Is the right hand column in a flex that's effectively the image on the left  and the name, vendor, and (artificially truncated) description. It's insane on a modern screen to limit that to an expander of 150px and force a 'more' but that's where we are. It also holds the drop-downs for any options like color or size.
We would like a-popover-inner to be able to use all that massive whitespace that's before back/request buttons, but from the factional pixel notation, we assume that Javacript is strategically lying to the layout engine about the wanted height of that div.
vvp-product-description-expander seems to be the center of the storm. It's artifically capped at 150px (ugh, more hard-coded nonsense) and relies on Javascript (aui-da-a-expander-toggle?) to knock it back to data-a-expander-collapsed-height when minimized. Change either of the and the layout falls over. I didn't chase it up into the (surely obfuscated) Javascript.
It seems that the ...expander relies on ...expander-toggle() to resize vvp-product-description-expander and thus, vvp-product-details-info-container to include the expansion PLUS vvp-product-details-modal--variations-container (which it seems to forget - or at least lose) and it's thus hidden and worse, without a scrollbar which we can fix with an overflow. I'd like to lose the paginator and just rely on scrolling when needed. The descriptions are rarely THAT long, thought mobile might pick other chocies. (That are still > 150px on a modern screen.)
So I guess please accept my one line change and I'll just write off a few hours of programmer loss trying to make it look sensible. It's goofy looking, but it's at least readable now, so it's hard to take that as total defeat.
It's, of course, your choice whether to close issue when when the original fix is applied or to keep it open and pursue aliminating thta paginator together.
Thank you for making this and keeping it awesome!

I don't understand the issue sorry. A screenshot might help.
I also have a 27 inch monitor

@robertlipe mobile has special styles designed for it. You can't use the desktop ones hehe. You can find android and ios variations here on the repo as well.
Are you using on a third of the screen or something on desktop? For me it shows fully even when using half monitor


Rewrite the export script in Python

Feature request

Current Behavior

The script is written in Bash.
Expected Behavior

The scripts following scripts must be rewritten in Python:

40-export-export_connectivity.sh

The export must implement the logic to support multiple export formats. The first 2 options required are local export and S2 export.
The export MUST NOT use uuids, but instead must use Calver to identify the different BNA run results.

The new export command should provide the ability to write the result files in

a custom directory
in a directory following calver for the naming scheme

The calver scheme is  based and inspired by the BNA mechanics standards: <country>/<state or province or region or country>/<city>/YY.M[.Micro]
Examples:

USA/TX/Austin/23.8
USA/TX/Austin/23.12.2
Spain/Valencia/Valencia/23.8


2019?

hi folks!
will there be a 2019 edition?

Hi, thanks for reaching out.
We have been asked this question or similar to it before and unfortunately the answer is no, there will not be JSConf Iceland 2019.
If you're wondering how soon will the next be? The answer is nothing has been decided.

ah. too bad. thanks for the response!


Branding settings can be enabled on Professional edition

Bug Report
System Information

Ubuntu 18.04 LTS
v2.0.3, built 22/07/2020 12:17
Mainline

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
Branding settings are functional on AMP Professional Edition, despite the edition comparison page specifying that the custom branding feature is limited to Network Standard edition and above
Reproduction
Create a new instance using a professional license and turn on the "Display Branding" option.

Fixed as of 2.0.5


Disable propagateCreateError by default

The attribute propagateCreateError should be set to false by default to prevent unexpected Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? error.
Explanation:
The propagateCreateError is set to true by default in Knex and throws a TimeoutError if the first create connection to the database fails, preventing tarn (the connection pool manager) from re-connecting automatically.
The solution is to set propagateCreateError to false thus enabling knex to automatically reconnect on create connection failure, instead of throwing the error, and only throwing it when the acquireTimeoutMillis has passed, as defined by tarn
Related issues:
#1381 #1382 #1655 #2445 https://github.com/strapi/strapi/issues/2790 #1875 #1909 #2302 #2141 #1264

Propagating the error is the correct and intentional functionality. If you think there is a problem, please add bug report with reproduction case.


Add an eslint step to the code coverage GitHub Action

Codecov Report

Merging #16 (8e72a66) into main (f9f31ee) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 8e72a66 differs from pull request most recent head 2721783. Consider uploading reports for the commit 2721783 to get more accurate results

@@            Coverage Diff            @@
##              main       #16   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          229       229
  Branches        25        25
=========================================
  Hits           229       229

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 f9f31ee...2721783. Read the comment docs.


doc is not removed from db on model.destroy

Hi,
I don't know how to debug this : a destroyed model seems to persist in xapian db.
Destroy is effective in db : DELETE FROM models WHERE id=123;
After deletion, a search in xapian finds model id 123, and of course leads to Error, coulldn't find model with id=123.
Using rails 3.1, ActiveRecord, behaviour seen in development mode.
Thks
PS: in Readme, seems that
blueprint.base_query Person.includes(:addresses)
should be corrected into
blueprint.base_query { |c| c.includes(:addresses) }
if I undestood correctly the warning.

Hi
The destroy problem is fixed in 1.2.4, which I released 2 days go. Please try the newest release and let me know if it is working for you. Thanks for the Readme correction.

Hi,
Thks for your quick reply.
I'm sorry but 1.2.4 doesn't solve the problem for my Model.destroy.
I made a mistake :
blueprint.base_query { |c| c.includes(:addresses) }
doesn't work, I needed to correct this into
blueprint.base_query { |c| Person.includes(:addresses) }.


Can't run multiple EE on same cluster

I'd expect that I can run the EE twice in different namespaces on the same cluster.  But when I try that, I get this error in the edge-endpoint pod:
  Warning  FailedScheduling  3m5s  default-scheduler  0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

Manual workaround is to create a second PV and PVC like this:
apiVersion: v1
kind: PersistentVolume
metadata:
  name: edge-endpoint-pv2
spec:
  capacity:
    storage: 2Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  storageClassName: local-sc
  hostPath:
    path: /opt/groundlight/edge2


Added new guidance page for setting up personal cluster (ADA) with R/…

…RStudio. Renamed previous guidance page to databricks_rstudio_sql_warehouse.
Overview of changes
Additional guidance instructing analysts how to setup an ODBC connection to a personal cluster in ADA. Updated existing guidance filename to make it more specific
Why are these changes being made?
Previous guidance only provided instruction on how to connect to a SQL warehouse in DataBricks.
Detailed description of changes
A duplicated guidance page with the instructions amended to relate to personal clusters in DataBricks, as opposed to SQL warehouses. An additional screenshot has been added to the images directory.
In addition the links to the existing and new guidance pages have been amended and added.
Issue ticket number/s and link
Not applicable.
Checklist before requesting a review

[Y] I have checked the contributing guidelines
[Y] I have checked for and linked any relevant issues that this may resolve
[Y] I have checked that these changes build locally
[Y] I understand that if merged into main, these changes will be publicly available

 Review analysts guide PR for Nick T

 Nick T analysts guide PR


Unexpected keyword argument 'ape', 'use_checkpoint'

I tried to do the inference test with the command
python tools/test.py ./configs/swin/mask_rcnn_swin_tiny_patch4_window7_mstrain_480-800_adamw_3x_coco.py ./checkpoints/mask_rcnn_swin_tiny_patch4_window7.pth --eval bbox segm
But I always got the following Traceback as below.
loading annotations into memory...
Done (t=0.29s)
creating index...
index created!
Traceback (most recent call last):
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 52, in build_from_cfg
    return obj_cls(**args)
TypeError: __init__() got an unexpected keyword argument 'ape'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 52, in build_from_cfg
    return obj_cls(**args)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmdet/models/detectors/mask_rcnn.py", line 27, in __init__
    init_cfg=init_cfg)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmdet/models/detectors/two_stage.py", line 32, in __init__
    self.backbone = build_backbone(backbone)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmdet/models/builder.py", line 20, in build_backbone
    return BACKBONES.build(cfg)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 212, in build
    return self.build_func(*args, **kwargs, registry=self)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 27, in build_model_from_cfg
    return build_from_cfg(cfg, registry, default_args)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 55, in build_from_cfg
    raise type(e)(f'{obj_cls.__name__}: {e}')
TypeError: SwinTransformer: __init__() got an unexpected keyword argument 'ape'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "tools/test.py", line 220, in <module>
    main()
  File "tools/test.py", line 173, in main
    model = build_detector(cfg.model, test_cfg=cfg.get('test_cfg'))
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmdet/models/builder.py", line 59, in build_detector
    cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 212, in build
    return self.build_func(*args, **kwargs, registry=self)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 27, in build_model_from_cfg
    return build_from_cfg(cfg, registry, default_args)
  File "/home/wma/anaconda3/envs/openmmlab/lib/python3.7/site-packages/mmcv/utils/registry.py", line 55, in build_from_cfg
    raise type(e)(f'{obj_cls.__name__}: {e}')
TypeError: MaskRCNN: SwinTransformer: __init__() got an unexpected keyword argument 'ape'

I think the problems come from the mismatch of the keyword definition between the mmcv, mmdet packages and the configuration files. There are at least "embed_dim", "ape", and "use_checkpoint" that can not be recognized by the two packages above. It is easy to figure the "embed_dim" out which should be "embed_dims". But what about the other two?
Please provide me with some possible solutions to this problem.
Thank you!

Nope, I have not figured it out although I tried to install the latest mmcv, mmdet packages. Please share any idea or solution if possible.

Hi, I have solved the problem by run python setup.py develop in Swin-Transformer-Object-Detection folder, you can refer to here. But I still meet some strange situation here, please give me any suggestion.

@wenchima It doesn't work for me either. First, it happened with embed_dim, which I changed to embed_dims. Now the keyword ape has a problem. I tried to delete the ape parameter from the config file, then it threw an error for the use_checkpoint parameter.

well,  you solved it or not finally ? can you  share the solution experience?

The swin_transformer backbone in this program has a few differences between the one in mmdetection so you cannot just use the config file in this program.

I am getting the same error regarding ape are we suppose to use the MMDet repo? They don't have the updated configs and they have a different format.


FIle name?

In the C++/winrt example of a simple POST of binary data, there is no file name, so it's not clear to me where this sample data is going  - isn't it necessary to specify a destination for the data? How would one add a path to this example, so that the data being POSTed replaces the contents of a specified file at the server? Thanks.

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

ID: 1ab6b70c-a112-963b-3951-b4fa958694a9
Version Independent ID: a7d8ff19-bda3-0889-2051-6627e5d4b16b
Content: HttpClient - Windows UWP applications
Content Source: windows-apps-src/networking/httpclient.md
Product: uwp
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Talking to someone about this I've come to understand that the script receiving the query will do the work of creating the file, etc. - so all I need is a standard way to specify that path in the header for this content. Perhaps there is no way to do that with HttpBufferContent.

I've updated the code here (should be live today or tomorrow). And I've added more thoughts (related to this question) to the other issue (https://github.com/MicrosoftDocs/winrt-api/issues/907). But, yeah, it probably boils down to how you specify that filename directive, and what path (if any) is meant to go in there.


ieee802154: csma-ca: random backoff factor looks wrong

This was posted on the user mailing list [1] and didn't have any response yet. Maybe it gets more exposure here.
The calculation for the random backoff factor looks wrong:
https://github.com/zephyrproject-rtos/zephyr/blob/e1b772479b12ccf31b3ec8e3c5b43d1644038535/subsys/net/ip/l2/ieee802154/ieee802154_radio_csma_ca.c#L44
This generates either a power-of-two number or zero for bo_n, because it only overlaps a single bit with the random number. The overlap is very rare and results in the backoff time being zero most of the time, if I'm not completely mistaken.
The standard defines the value to be random between zero and 2^be-1. The implementation should be:
u8_t bo_n = sys_rand32_get() & ((1 << be) - 1);

Has anyone had experience with this? I noticed this going over the implementation.
I want someone to confirm or discuss this before I open a pull request.
Kind regards,
Franco
[1] https://lists.zephyrproject.org/g/users/message/878

Sounds like a trivial bug, just send a PR directly.


Missing info about required netcoredeps folder for self contained exe on Linux

I wish publishing a self contained exe was easy for Linux.  However this page doesn't mention that the developer needs to download specific libraries for each Linux distro they need to support and place them in a sub directory called netcoredeps.  This can be quite challenging and Microsoft offers no tool to do this easily.
I build a docker image for each distro to download packages, extract the libraries, and place them in a flat directory and export each docker image.  Later I import these docker images to copy the correct set of files for the Linux distro into the netcoredeps directory of the app.
This works great for all but one distribution.  CentOS7.8.2003.  after installing my web app, I run it, and I get an error saying it found the fx.so (don't remember the exact name) , but it can't find a Linux prerequisite.  It doesn't tell me the missing prerequisite.
Now I can't release our app as self contained for this latest version of centos7 -- 7.8.2003 -- because of this problem.
This documentation needs to be updated and Microsoft needs to make it easier to gather these third party libraries for self contained exes.  Or customers don't have their machines connected to the internet.  We need this to work.
Thank you.

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

ID: 85eba478-0374-bb9b-8fa7-d5cf7d520603
Version Independent ID: 89967250-8c3b-1999-078f-94ad7518ed49
Content: Application publishing - .NET Core
Content Source: docs/core/deploying/index.md
Product: dotnet-core
GitHub Login: @adegeo
Microsoft Alias: adegeo

Tagging @rbhanda @leecow for comment
This is definitely a gap. Thank you for bringing this up. The self-contained section should be expanded to explain this scenario.
I don't know if this helps, browsing through it I don't think it will, but I'll at least link to it: https://github.com/dotnet/core/blob/master/Documentation/self-contained-linux-apps.md


Fix relativize_url for pretty permalinks

I found your pull-request yesterday and really liked it (https://github.com/jekyll/jekyll/pull/6362). Unfortunately it was not successful because of the issue with the permalink: pretty setting, which would have been easy to solve and due to the missing willingness to accept the use case.
However, for the reference, I want to link my fix here.

Yep. Nice fix. :+1:

BTW, leave a comment explaining this on the original ticket. If enough people express their desire to get this fixed, maybe the maintainers will wake up :-)

Actually I found out, that the dir is not set for posts, so this one will not work for posts. I have fixed it in https://github.com/jekyll/jekyll/pull/8519


pull request for e2e test at 01/16/2017 20:15:09

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


Documentation of what appears in Cheat Sheet

I generate an empty cheat sheet at the moment. From the docs I can't see what should go into the cheat sheet. I think, looking at the code, it is only functions from prioritized files? Is this correct? Can the explanation be added to the documentation?

Sorry.  The CheatSheet is built up from all the Usage: lines for each module, function, and the names of each constant.
I'll add this into the docs.


Replace signatory with ed25519-dalek and k256 crates

Native support for the signature traits used by the signatory* was recently added to ed25519-dalek in v1.0.0-pre.4, and the k256 crate recently added a native pure Rust implementation of ECDSA/secp256k1.
Together these changes eliminate the need for the signatory* wrapper crates. Additionally, k256 eliminates the need for the rust-secp256k1 C-based library, which has been problematic with e.g. WASM (#391).
This commit eliminates all signatory dependencies and uses ed25519-dalek and k256 directly instead. Both of these were already dependencies, so it's not adding any additional dependencies, but instead removes several of them.

The clippy failures seem unrelated?

@liamsi @xla hopefully I've addressed all of the line notes.
The major remaining concern to me is the point decompression-related issues. I'll try to verify the behaviors on both Rust and Go, as if there's an actual discrepancy there that sounds potentially consensus-critical.

@liamsi @xla hopefully I've addressed all of the line notes.
The major remaining concern to me is the point decompression-related issues. I'll try to verify the behaviors on both Rust and Go, as if there's an actual discrepancy there that sounds potentially consensus-critical.

Yeah, it's a bit weird as the go library also does point decompression as far as I remember. And the test vectors surely were generated using the go implementation (I wish we documented how exactly these were generated). I guess as long as we can "roundtrip" pubkeys between the go and rust implementation we should be fine.
A while ago @valardragon suggested to cache these decompressions and add a verification method directly on the uncompressed pk as an optimization: https://github.com/tendermint/tendermint/issues/1784. But as far as I know this never materialized.

Actually, we did document were these test-vectors are coming from, besides, how the raw bytes came about:
https://github.com/informalsystems/tendermint-rs/blob/48a11d1aea190a3f9eaa8582c37b82e1395d5858/tendermint/src/amino_types/ed25519.rs#L106-L110
Note that the go code does not do any checks on these bytes but I would be surprised that the existing test-vectors were not generated from a priv-key. In that case the pubkey should have been compressed, as this is called while generating a key(pair): https://github.com/golang/crypto/blob/123391ffb6de907695e1066dc40c1ff09322aeb6/ed25519/internal/edwards25519/edwards25519.go#L708
My suggestion is to generate a fresh key pair in go and use this as a new test-vector (maybe this is what you did anyways?) and verify everything works as expected.

https://github.com/informalsystems/tendermint-rs/pull/522/files#r472102039
The bytes that were used were not generated using github.com/tendermint/tendermint/crypto/ed25519.ed25519.GenPrivKey()
This is not a compatibility issue!

@xla looks like this is blocked on your suggested changes, but I think they've all been done.
Any ideas on the clippy error? Will it block merging?

After some investigation the clippy error seems to be related to the enum variants the PublicKey type wraps.
Specifically the VerificationError::InvalidSignature variant stores the entire Validator struct, which I guess is now large enough to push it over the clippy size limit.


Unity Ripper Error Issue Extacting the avater VRChat

 **i do have Issue  Problem when i Extract the avatars from VRChat game order to using it inside Unity matter so how i can fix that problem  i don't know how to ? what is best  Solutions i have ?
 with Unity Ripper how to Fix this issue Error problems ?  i need it Please   Thank you im looking for Solution
if you know how to fix it Please contact with me in my Discord :(Darkhal#0550) ido appreciate you for help and support **

uTinyRipper has been abandoned, but you can try my AssetRipper fork. In the event that AssetRipper encounters issues while ripping your files, feel free to post an issue on that repository.
AssetRipper is actively being developed with the intent to recover games as best as possible. Weekly releases are normally on Sunday or Monday. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
If you like the work I've done and want to see it continue, please consider sponsoring me. It really does help with development. These are some of the notable things I've implemented since taking over development:

2020+ support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements
Support for all asset types

Sponsorship Links:

GitHub Sponsors
Patreon
Paypal

can you Describe me how it works ? with VRChat avatar please ?

I don't teach people how to use AssetRipper. However, I am open to hearing feedback on its user interface and usability. If you have specific questions, I may answer them.


Overriding top-level security with a empty operation level security array

The OAS specifies the operation level security object as follows:
A declaration of which security mechanisms can be used for this operation. The list of values includes alternative security requirement objects that can be used. Only one of the security requirement objects need to be satisfied to authorize a request. This definition overrides any declared top-level security. To remove a top-level security declaration, an empty array can be used.
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#fixed-fields-8
The overriding with a empty array seems to be a problem when creating the OpenApiDocument from a Swagger 2.0 / OAS string as it gets deserialized into a empty list thus removing the information that the operation should override the security defined on the top level.
Example of operation level security that does not override the top-level one:
"security": []
Example that does override it but does not follow the spec
"security": [{}]

I've just stumbled upon this bug too, and it affected me because I wanted to be able to define a single route without security.
Looking at the source here, I can see the problem

OpenApiOperation.Security is initialized as an empty List.  Would there be any harm if it was initialized as null?  I guess this would be a problem as soon as someone wants to do Security.Add() without realising it hadn't been initialized.
OpenApiOperation.SerializeAsV3 uses WriteOptionalCollection for the Security property, which ignores any null or empty lists.  We need an alternative method which ignores null objects, but writes empty lists - I'm not sure if one exists.

I've tried a variety of workarounds, but none have worked for me yet.  I think I'm going to have to override the SwaggerMiddleware, and specifically replace
"security": [           null         ]
with
`"security": [
    ]`

before sending the JSON response.

This is one of those "it's not actually a bug" but it confuses enough people that it warrants adding support for the empty array.  See #521 for a long conversation about it.
But just to clarify, adding an array that contains an empty object is the correct way to be explicit about an operation allowing anonymous access.   An empty array simply says nothing about the security requirements of the operation.   However, we can assume that if you are not telling a consumer anything about the security requirements, then you probably should allow anonymous access.

I'm going to close this as by design.  I don't want to get in a place where sometimes, not describing behaviour means something and sometimes it doesn't.  An empty array is equivalent to not including the security property.  i.e. it tells you nothing about the security of the API.  An array with an item that contains an empty security requirement is explicitly saying anonymous access is allowed.  It does not say you cannot call the API with an authentication header.
OpenAPI has a philosophy that it describes what is possible, without saying what is not possible.  This was an explicit decision.


[suggestion] Docker image release with log level for metric_namer

First of all, thank you for all your work @DirectXMan12, it's really useful.
I have notice that the currently tagged docker image (v0.2.1) has a very verbose output, which in our case generated an immense amount of logs to the point of being dangerous (filling up the logging server, which has a lot of space).
Of course we can workaround this issue by renaming your latest image (or build our own) and tag it in our registry, however I think this would be nice to have a tagged image which this behaviour, so that people are not encouraged to use latest tag (which also caused more serious problems to us in the past, with the breaking changes).
Do you think it would be possible to release more frequently, especially when there are significant improvements like the logging level for metric_namer.go?
Thanks in advance!

Yeah, I'll tag a release.

https://github.com/DirectXMan12/k8s-prometheus-adapter/releases/tag/v0.2.2


RemovedInDjango21Warning

RemovedInDjango21Warning: Add the renderer argument to the render() method of <class 'smart_selects.widgets.ChainedSelect'>. It will be mandatory in Django 2.1. [boundfield.py:36]
Changes need to be made here:
https://github.com/digi604/django-smart-selects/blob/master/smart_selects/widgets.py#L217
And here:
https://github.com/digi604/django-smart-selects/blob/master/smart_selects/widgets.py#L83
Here is an example of how to make the change:
https://github.com/adilkhash/django-wysiwyg-redactor/commit/b2c4ca33909ced447f3c1ee9bd01dab14d3a5ac2
@PetrDlouhy

Hi @timthelion, tried with latest 2.0 and did not see the warning. Tried with 2.1 and it worked. Can you please add more information to this issue?

@timthelion this has been fixed in https://github.com/jazzband/django-smart-selects/commit/6c00a6b54aeabce771218c07006cca156b3b06e2


Feature for V2: Dropping HTTP, using plain TCP.

For now interaction between tumbler and client are using HTTP and JSON.
This has several issue:

Fingerprinting at HTTP Level (if multiple implementation)
Fingerprinting at JSON level (if multiple implementation)
Inefficient use of bandwidth

This is not a big deal for now as tumblebit has only one implementation, but this is something that should be done in V2 once it get stable and used.

Concept ack.
Notes:

while inefficient bandwidth use is not a problem at tumblebit, http/1.1 also not inefficient, only when there are many many rounds of requests in row. But http/2.0 fixes that.
We could explore I2P or Tor hidden services.

However it also obsolates all 3 proxy types. Therefore if we can all agree on this goes into v2 I am not interested pushing the PR https://github.com/NTumbleBit/NTumbleBit/pull/79 anymore.

it does not obsolete Socks proxy.

Indeed, not necessarily. My PR is still relevant then.

Done, now TumbleBit does not use HTTP, nor JSON for server transfer.


How To track Clicked Child on React App

Hi bumbeishvili, Thank you for your great work , i have couple questions
How can i able to track current child dom ref inside chart that being clicked , i need to mount a tooltip when a child is being clicked , using React app.
Currently , I am able to handle rendered component based on click state, but not able to track clicked child dom reference

You can access this in the nodeUpdate  which is a wrapper g element of single node and you can access any element after it
chart.nodeUpdate(function(d){
   const elem = d3.select(this).select('.customElementClass').node()
})


Acid missing as Koffling's fast attack in pokemon.json

Description of the issue
As stated in the title, Acid is missing as one of Koffling's fast attacks in pokemon.json. Although Acid has become a legacy move now for Koffling, it should NOT be removed from the JSON file.
Relevant section in pokemon.json
{
    "Number": "109",
    "Name": "Koffing",
    "Classification": "DataNotInGameMaster",
    "Type I": [
      "Poison"
    ],
    "Weaknesses": [
      "DataNotInGameMaster"
    ],
    "Fast Attack(s)": [
      "Tackle",
      "Infestation"
    ],
    "Weight": "1 kg",
    "Height": "0,6 m",
    "Candy": {
      "Name": "Koffing candies",
      "FamilyID": 109
    },
    "Next Evolution Requirements": {
      "Amount": 50,
      "Family": 109,
      "Name": "Koffing candies"
    },
    "Next evolution(s)": [
      {
        "Number": "110",
        "Name": "Weezing"
      }
    ],
    "Special Attack(s)": [
      "Sludge",
      "Sludge Bomb",
      "Dark Pulse"
    ],
    "BaseAttack": 119,
    "BaseDefense": 164,
    "BaseStamina": 80,
    "CaptureRate": 0.5,
    "FleeRate": 0.1,
    "BuddyDistanceNeeded": 3
  }

Output when issue occurred
[2017-03-05 08:09:23] [MoveToFort] [INFO] Moving towards pokestop Coral Gazebo - 0.14km
[2017-03-05 08:09:25] [   Pokemon] [ERROR] Unexpected moveset [Acid, Dark Pulse] for #109 Koffing, please update info in pokemon.json and create issue/PR
[2017-03-05 08:09:25] [   Pokemon] [ERROR] Unexpected moveset [Acid, Dark Pulse] for #109 Koffing, please update info in pokemon.json and create issue/PR
[2017-03-05 08:09:28] [MoveToFort] [INFO] Moving towards pokestop Coral Gazebo - 0.12km

Other Information
OS:
Ubuntu 16.04.1 LTS 64-bit
Branch:
dev
Git Commit:
720c90a3962783e871896618e2353995cf6f94e9
Python Version:
Python 2.7.12

Issued Merged


Tracking what's new in MSIX and what's supported in Win10/11

There are some broken links resulting in 404s here:
Defer registration flag
Force provisioning
There may be others.
Also there are many other new features I'm interested in tracking that are not in this table (listed below along with the supported OS according to the page):

Flexible Virtualization

Windows 10 21H1
https://docs.microsoft.com/en-us/windows/msix/desktop/flexible-virtualization

Start Menu Groups

Windows 10 Dev Ring 20257
https://docs.microsoft.com/en-us/windows/msix/packaging-tool/create-start-group

Legacy Context Menu Support

Windows 11 Insider Preview 22000
https://docs.microsoft.com/en-us/windows/msix/packaging-tool/support-legacy-context-menus

Shared Package Container

Windows 10 Insider Preview 21354
https://docs.microsoft.com/en-us/windows/msix/manage/shared-package-container

Mutable Package Directories

Windows 11
https://docs.microsoft.com/en-us/windows/msix/manage/create-directory

MSIX Persistent Identity

Windows 11 Insider Preview 22000
https://docs.microsoft.com/en-us/windows/msix/package/persistent-identity

Shared Package Container is in the table with support listed for Windows 11 21H2, but the page for that feature only mentions Windows 10 Insider Preview. I am therefore unsure about whether or not these other preview features have yet finally made it into production!
It would be great to see these other features added to the support matrix, highlighting which features are still in preview.
It would also be nice to have a "What's new in MSIX" page listing these to help us keep track of the latest additions!

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

ID: 95b83f04-01b6-c494-1e2a-dcddecaa7dc8
Version Independent ID: 758db7a1-fd48-56fc-1e82-0fbd7ad3f7dc
Content: Supported platforms - MSIX
Content Source: msix-src/supported-platforms.md
Product: msix
GitHub Login: @dianmsft
Microsoft Alias: diahar

Thank you for your comment @DanGough. I also saw the post on tech community and appreciate the feedback. We will get to updating the docs accordingly.
As for what's new in MSIX, this blog is where we update the community: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog/label-name/MSIX


Cannot compute fid for a generator, using images in fdir2.

This code is from fid.py line 459-470.
elif gen is not None:
    if not verbose:
        print(f"compute FID of a model with {dataset_name}-{dataset_res} statistics")
    score = fid_model(gen, dataset_name, dataset_res, dataset_split,
            model=feat_model, z_dim=z_dim, num_gen=num_gen,
            mode=mode, num_workers=num_workers, batch_size=batch_size,
            device=device, verbose=verbose)
    return score

# compute fid for a generator, using images in fdir2
elif gen is not None and fdir2 is not None:

There is no way we enter the last elif, so I can't compare my generator with images in fdir2. Is this intentional?

Hi,
Thank you for pointing this out!
I have addressed in the new release of the library.
Regards,
Gaurav


Increment version for communication releases

Increment package version after release of Azure.Communication.Email

API change check
API changes are not detected in this pull request.


Fixing image for black background theme I#3215

Fixing Image for #3215
This substitute PR #3382
Copy review @nenonix @JohanFreelancer9 is required on this one guys. Thank you in advance!

@dstrome PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@j0rt3g4 - please re-submit the graphic change without the owner or video link changes. thanks.


Fix travis scripts, error in javadoc, and StandardCharsets which cannot be used on java1.6

Please use separate PRs for different fixes