[breaking change] Remove dynamic type

Change Intent
Dart should remove the dynamic type for stricter type-safety, better performance and less support for bad practices.
Justification
The use of dynamic is a bad practice, often even referred to as such in the documentation:

"dynamic: Indicates that you want to disable static checking. Usually you should use Object or Object? instead." (https://dart.dev/language/built-in-types)
"Dynamic calls are treated slightly different in every runtime environment and compiler, but most production modes (and even some development modes) have both compile size and runtime performance penalties associated with dynamic calls." (https://dart.dev/tools/linter-rules/avoid_dynamic_calls)

However, there are ways to bypass dynamic calls and implicit casts for your own projects using lints (e.g. with strong-mode).
But this does not solve the problems that the support for dynamic has for the Dart language in general.
Firstly, it results in worse performance of the compiled code, since more inefficient runtime checks are required. (I'm not an expert on Dart compilers, so correct me if I'm wrong on this point).
Secondly, the support of dynamic prevents other features that many developers would like to use in a type-safe object-oriented language. For example, private, protected and public modifiers are not possible because they could not support dynamic types except through very inefficient runtime checks (#33383).
In general, Dart tries to be as type-safe as possible. But on the other hand there is this relict dynamic, which stands against it.
dynamic generally feels like a concession to JavaScript developers to get more of them to switch to Dart/Flutter. Developers who have moved from Java/Kotlin/Swift/C++,... are just disturbed by dynamic and it also doesn't bring any benefits except more opportunities to apply bad practices.
Impact
All code that currently uses dynamic would have to be changed to Object? or subtypes and implicit casts would be required. Also, method calls would no longer be possible without knowing the type of an object.
Mitigation
Since this would be a null-safety level change, it would have to be made optional at first and fully introduced with the next major release.

This is a language change request. Moving it to the language repository.


add support for tessellation shaders, if the necessary enums are available

Not super-pretty, but gets the job done.

Thansk for your work!


fix: template use with vault

copilot:all

Current dependencies on/for this PR:

main

PR #2962   👈

This comment was auto-generated by Graphite.


feat: add a helper function to get bot user credentials

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

Needs approval from an approver in each of these files:

OWNERS

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

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

Test name
Commit
Details
Rerun command

pr-build
cb4de4e38253bdc64a789873aa99ca8952243690
link
/test this

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

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

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


Add optional support to restore nuget packages recursively

Nuget packages in submodules are not restored before build.
I found a powershell line here, that when executed instead of "nuget package restore", properly restores the packages.  Using the standard nuget restore simply says "all packages already installed" and then the build obviously fails after that.
https://gist.github.com/jongalloway/cc6cb3885fe1777a05ac
get-childitem . -include *.sln -recurse | foreach ($_) { nuget restore $_.FullName -verbosity detailed}

A workaround is to set project hint paths in the submodule csproj file to use $(SolutionDir)\packages\foo\bar instead of packages\foo\bar. But this is not an option for everyone. Unless there is a specific downside to recursing the package restore command, I would think it's a more flexible option with less user headache.

Generally, the process that does the build knows nothing about submodules. It looks at all the files in the repository folder, regardless of whether they all came from one repo or multiple.
Submodule aside, if the default deployment script doesn't do what you want, you can switch to using a custom deployment script, which lets you run nuget in any way you want.

Thanks for the reply.  Kudu is using git in its deploy script is it not? Is it correct design to support git projects in the standard deploy script, but completely fail with those projects that employ the standard submodule pattern that many projects use?
I obviously can't force you to change your mind, but I think that your stance on this is a mistake which will ultimately hurt the quality of the product.  Is there any way this can be solved without expecting people to write their own custom scripts?

No, the deploy script is actually agnostic of git. The general high level flow is:

Do the git update (including submodules)
Run the deployment script, which works with whatever files end up in the repository folder (with git and submodules of no relevance at this point)

So I'm not sure what the issue is, but I'm fairly confident that it is not directly related to submodules. To see that, try creating a single repo containing the union of all your submodules. You'll likely see the same behavior.

Here is what the issue is:

Kudu calls git.exe submodule update --init --recursive and then submodules are updated.
At this point, the folder structure looks like:

mainsolution.sln
MainProject/MainProject.csproj
Submodule/Submodule.sln
Submodule/Submodule.csproj

The deploy script is run, which calls nuget package restore on mainsolution.sln via the below command

:: 1. Restore NuGet packages
IF /I "mainsolution.sln" NEQ "" (
call :ExecuteCmd "%NUGET_EXE%" restore "%DEPLOYMENT_SOURCE%\mainsolution.sln"
IF !ERRORLEVEL! NEQ 0 goto error
)
Right at this point when the NuGet packages are restored, the directory structure looks like this:
mainsolution.sln
packages/{all packages belonging to both main solution and submodule}
MainProject/MainProject.csproj
Submodule/Submodule.sln
Submodule/Submodule.csproj

The problem is that within submodule.csproj, BY DEFAULT references are relative to the csproj file and not the sln file.  At least this is true in the version of nuget I am using.  So compilation fails because ./Submodule/packages/whatever/whatever.dll is not found, but is instead placed in ./packages/whatever/whatever.dll.
The default deploy script doesn't know about git, but it could simply, for each .sln file which is not in the root directory, also execute the nuget package restore command for that respective folder.  An option to disable this behavior could be specified by the user so long as they are using the default deploy script.
It's not exactly the simplest of fixes but I feel like this is something that should be fixed, even if you don't have the resources to do it outside of a community-submitted patch.

If this is something that is deemed too kludgey for default behavior then perhaps having it as an advanced option disabled by default would be okay too. Just thinking out loud

First, we need to agree that the behavior you describe has nothing to do with submodules. You could have a regular plain repo that happens to have multiple solution files in various folders, and the same would apply.
I think the main danger with the recursive nuget approach is the possible perf issues. Some repos have 10000 folders with random stuff, and that directory walk could be slow.
The part I'm not clear about in your scenario: what specific project are you deploying? MainProject.csproj or Submodule.csproj? And are those two solutions in any way related, or are they each their own things?
Honestly, I don't think using a custom script is much of a burden for these more complex scenarios (I don't think this issue has come up before). You can very easily download the default scripts for your site (Tools menu in Kudu), modify a couple lines and get it in your repo. The default script only goes so far, and there are lots of reasons why people move to custom scripts. It's really a pretty simple thing that then gives you a ton more control over your deployment process.

To respond to the performance issues: There are a few options.  One of them is to have an option to specify recursive depth, with a default of one.  Or the behavior can be disabled.  Anyone who is the lead developer on a project with submodules, having a solution structure with that level of complexity, likely to understand how to use advanced options, but too busy to spare the time to build custom scripts just for this task.  As an accomplished architect, you may see batch scripts as a relatively simple thing.  But from my experience batch scripting is not as flexible of a tool as it was designed to be.  A lot of C# developers do not really do so well with batch scripting, myself included.  We can do it, but it is very time-consuming and headache-inducing.
Even if I could write a batch script, a lot of team managers do not like having scripts that only one person can understand or maintain, because it is a liability to the project (believe it or not, a lot of small software companies hire younger devs that do not have this background).  Or they don't like having to pull Bob off of project A and have him fix project B every time something needs to be updated or diagnosed with the custom build script.  So is this fine for one-man projects?  I say that it still isn't, because one-man projects are supposed to be small and simple, and Kudu from my understanding is supposed to make things less painful and more simple.  Submodules are no longer a fringe use case and are becoming a standard thing.
If the aforementioned edge case is not solvable with the options given, I imagine that another user will submit an issue here asking for help and then the issue can be dealt with as it arrives. Worst case scenario, they will have to have the behavior disabled and it will behave, for that user, as if we had done nothing here.  The standard, run of the mill use cases, will see that their nuget packages are no longer missing references.
I am deploying MainProject.sln. The two solutions, in my case, are related. And I even have my own workaround already done with.  But if Submodule.csproj were an open source project not under my control, my workaround would likely not work without a custom deploy script.
With that said, if you still think custom scripts are what is necessary, here is what I propose: The documentation should clearly explain the possibility of this issue occurring, and describe how to solve it by editing the build script (include the actual code). And explain the possible performance implications.

And yes to answer your question, I understand that this is not a problem unique to submodules, but submodules are the use case that virtually every instance of this problem will occur with in the real world.

To be clear, I'm not against targeting this scenario if the community has the drive to make something happen and sends a PR. That's how a lot of things get done in the OS world :)

Thank you!  Could the issue be re-opened in that case? :+1:

I changed the title to more precisely describe the need, and reactivated it.

Hi
Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained.
If the problem persists and is related to running on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


[COU] UI of fringe scenarios (Epic 1 & Epic 2)

To be discussed first.
"Cancel" button shall be in orange (see the Fig.2) OR be the same style/format as the other fringe scenarios (e.g., order cancelation, see Fig.3).
Fig.1

Fig.2

Fig.3

@Aris I propose to have the same format as Fig. 3

wrong delivery address modal should look like the cancel order modal. Please also change the color of action button (submit) [Confirm and Cancel Order] in our dark green

Cancel Order Modal is like that currently and wrong delivery address is like that:

which of them should we keep as design?

I guess the second @Mastaleru @klivit

The second one looks great for me
On Thu, 26 May 2022, 12:34 Aris, @.***> wrote:

I guess the second @Mastaleru https://github.com/Mastaleru @klivit
https://github.com/klivit
—
Reply to this email directly, view it on GitHub
https://github.com/PharmaLedger-IMI/csc-workspace-main/issues/697#issuecomment-1138345816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALGVSIH2G3CCHSRIFBIGWLVL5AQXANCNFSM5VEPWNCA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Use kubebuilder:pruning:PreserveUnknownFields

We worked around the config needing arbitrary yaml before Kubebuilder codegen supported it, but they got it merged almost a year ago. Let's switch to the standard way.
see https://github.com/kubernetes-sigs/controller-tools/pull/345

Fixed by #279


Fix typo for docs reference

Fix typo for docs reference from EXAMPLES to Examples and keep the same format among docker commands.
Signed-off-by: yuexiao-wang<EMAIL_ADDRESS>

LGTM, thanks!


Dropout Reconnect

Is there a correct way of doing Reconnection for Device disconnected while the app is running at the background?

+1


[User Story] -

As a [role]
I need [function]
So that [benefit]
Details and Assumptions

[document what you know]

Acceptance Criteria
Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

Update an account in the service


Building from source with CUDA PATH problem

Environment info
Operating System: Fedora 23
If installed from sources, provide the commit hash:
8e035ea
Steps to reproduce

../bazel/output/bazel --output_base=/projects/.cache build -c opt --config=cuda //tensorflow/tools/pip_package:build_pip_package --verbose_failures

What have you tried?

./configure on root directory
cuda_config.sh script
building without --config=cuda is successful.

Logs or other output that would be helpful
(If logs are large, please upload as attachment).
Output from build
http://pastebin.com/17BejSXD
I noticed that PATH in the log doesn't have the directory to libcudart.so.7.5, which is here:
/usr/local/cuda/lib64/
echo $LD_LIBRARY_PATH:
:/usr/local/cuda/lib64:/usr/local/cuda/lib:/usr/lib/nvidia:/usr/local/cuda/lib64:/usr/local/cuda/lib:/usr/lib/nvidia:/usr/local/cuda/lib64:/usr/local/cuda/lib:/usr/lib/nvidia
Pointers will be welcome.

changed the PATH and still have this problem.  Will make a new issue.


 I'd also like to get taxable / price set town plots done first as that's a major feature. Towny also has a bunch of stuff that Husk Towns does not like nations.

Taken from the Roadmap. Check for updates.
If anyone has any suggestions or ideas on how we should handle issues like the nation system import, please leave a comment in this ticket. This lets us compile everything, and hear feedback.
This issue is marked as postponed; this is not correct but it's priority is considered so low that postponed is the best gauge

**!DO NOT PROCEED INTO THIS OR MAKE ANY PULL REQUESTS WITHOUT DISCUSSING THIS! **
As towny contains features we do not, Discussion with our Users are first priority. If a Structure for a Migrator has not been approved then it's subsequent Pull Request will not be merged.
Think before you Code.
Thanks,
The Cruel Hearted Bastard who will put someones hard work to waste
because they didn't read this first -- Iotados


Crash with read-only root filesystem

Your environment

Secret Injector Version: 1.0.2

1Password CLI Version: N/A

Connect Server Version: N/A

Kubernetes Version: N/A
What happened?
It's good security practice to set security contexts, specifically readOnlyRootFilesystem. However, the container will crash instantly when enabled.
What did you expect to happen?
The container should run normally.
Steps to reproduce
Set the container security context option readOnlyRootFilesystem to true.
Notes & Logs
This is caused by glog's default behaviour of writing to a temporary file. It can be disabled with the logtostderr flag, but glog never has the chance to read this flag as flag.Parse is called after a glog log.

Hey @uhthomas! I'm having trouble validating the glog behaviour as the source of the issue. Could you provide the steps that you used to confirm that the PR solves the issue?

Closing this ticket as there was no response for a while. Feel free to re-open if the problem persists.
In the meantime, it was identified that the root cause of the issue you're facing is related to the fact that the CLI is trying to write in the /tmp and /op (or .op) directories. This is required by the CLI to properly handle authentication when using a service account with the CLI. The workaround that was found for the original issue is as follows:

Add the following snippet to the deployment in which the kubernetes-secrets-injector will inject secrets into:spec:
  volumes:
    - name: tmp
       mountPath: /tmp/
    - name: op
       mountPath: /.op/

Re-apply the new configuration (it might require a restart).

Once this is done, It should work as expected.

Hey @uhthomas! I'm having trouble validating the glog behaviour as the source of the issue. Could you provide the steps that you used to confirm that the PR solves the issue?

 It would be nice to merge this fix regardless of whether or not the rest of the app needs certain mounts. Let me know if you need help validating it.


elf2uf2-rs: 2.0.0 -> 2.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/elf2uf2-rs/versions.
meta.description for elf2uf2-rs is: Convert ELF files to UF2 for USB Flashing Bootloaders
meta.homepage for elf2uf2-rs is: https://github.com/JoNil/elf2uf2-rs
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.1.1 with grep in /nix/store/b1ik8z80mayf3bilhjh2d2cb8j06cc5d-elf2uf2-rs-2.1.1
found 2.1.1 in filename of file in /nix/store/b1ik8z80mayf3bilhjh2d2cb8j06cc5d-elf2uf2-rs-2.1.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

elf2uf2-rs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b1ik8z80mayf3bilhjh2d2cb8j06cc5d-elf2uf2-rs-2.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A elf2uf2-rs https://github.com/r-ryantm/nixpkgs/archive/98f3cf181bd62d49b7ec14be499b4a334871d4f5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/98f3cf181bd62d49b7ec14be499b4a334871d4f5#elf2uf2-rs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b1ik8z80mayf3bilhjh2d2cb8j06cc5d-elf2uf2-rs-2.1.1
ls -la /nix/store/b1ik8z80mayf3bilhjh2d2cb8j06cc5d-elf2uf2-rs-2.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

elf2uf2-rs

Maintainer pings
cc @polygon @moni-dz for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

hm, guess I'll do some cleaning up wrt the darwin frameworks

#361211


Prevent removal of embedded documents

This fixes a bug I introduced along with ODM support. Removing an entity that contains an embedded document will trigger a removal for that object as well, which then causes an error because embedded documents don't have an identifier.
The fix is simple; this PR also adds tests to ensure only one creation/update/deletion is triggered when writing documents that contain embed relationships.

Hi,
I ran the test locally and I got into this error:
1) Algolia\AlgoliaSearchBundle\Tests\AlgoliaSearch\ORM\AlgoliaIntegrationTest
Doctrine\ORM\Mapping\MappingException: Class "Algolia\AlgoliaSearchBundle\Tests\Entity\EmbeddedDocument" is not a valid entity or mapped super class. in /home/vagrant/AlgoliaSearchBundle/vendor/doctrine/orm/lib/Doctrine/ORM/Mapping/MappingException.php:346

Any idea? I pushed your branch the repo to see how it goes on Travis.

My IDE snuck in a strict type declaration which I forgot to remove. Since travis is running PHP 5.6 it didn't quite like it. I pushed a version without it - we'll see if it goes better this time.

I didn't seem to fix the issue. Have you run the test locally? They keep failing on my machine.

Yeah - I was only running the ODM test suite since I only modified those tests. I'll need to make some changes to the metadata loading to avoid the ORM tests trying to load mapping information for the embedded document.

@julienbourdeau Can you give it another shot? Should be fixed now - all tests stable on my machine.

Thank you :)


Z index for dropdown selector collide with modals

Summary
Fixing a z-index issue with dropdown selector and modal with z-index. Ideally we should use this property at input level, instead of form, but the fix it's much bigger and require more investigation, as the z index levels are complex to follow.
Ticket Link
https://mattermost.atlassian.net/browse/MM-47802
Screenshots
before

After

Release Note
NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.


allow global opsgenie api key

just like #897
closes #1173

@stuartnelson3 FWIW the docs counterpart is pending merge https://github.com/prometheus/docs/pull/955


Add warning diagnostic when trying to use if statement expression that always evaluates to true in Lua

Maybe i missed something in the documentation or issues, but i cannot find anything about the difference in falsy values. The most obvious one being "0", and the transpilation of this code:

As far as i can tell, this should not print the value because 0 is false in typescript. But it will print it, because 0 is true in lua!
Is this intended? Am i wrong and 0 is actually true in typescript as well? I am quite confused right now

You are right, this behavior differs between JS and Lua. To avoid it, I would recommend only using if with boolean or undefined expressions. See https://typescripttolua.github.io/docs/caveats#boolean-coercion for the corresponding documentation.

Oh sorry, i totally missed that part in the docs. Is this by design, or would you potentially be interested in a pull request to change this?

This is by design. Changing this behavior would involve injecting extra unexpected code into a lot of places, even though part of our users probably will not want or expect this. Simply changing conditions to be booleans with an explicit comparison is a simple and clear workaround, supported by for example eslint's strict-boolean-expression rule.

Thinking about this a bit more, I think we should probably make this a tstl warning if you try to do something that might yield unexpected results. I'm thinking we can add a warning "This will always evaluate as true" when the type of the expression in an if statement expression type cannot be false or undefined.

I think that a lot of TypeScript users use ESLint with the strict-boolean-expressions rule.
So, in your example:
let theNumber = 0;
if (theNumber) {} // Illegal!

This code would be illegal, and wouldn't pass the linter. It would force you to instead use:
let theNumber = 0;
if (theNumber === 0) {} // or "theNumber <= 0", depending on what exactly you want to do

The second code is much more sane, so I highly recommend using this rule.
Or, if you want an opinionated linter ruleset to get you off the ground running with TSTL, you can use my linter metapackage.

@Zamiell You are absolutely correct. I added the strict boolean expression rule after @Perryvw mentioned it here. It improves code clarity and i much prefer not relying on internal falsy-rules anyway. I will check out the linter metapackage you mentioned
@Perryvw Showing a warning in this case would be great, maybe including a link to the explanation in the docs, together with a hint to use the strict-boolean-expressions rule. Just to help other people like me which are unable to read the docs properly before using the project ;-)

Showing a warning in this case would be great, maybe including a link to the explanation in the docs, together with a hint to use the strict-boolean-expressions rule.

Yeah, that would be pretty nice if the TSTL vscode extension could do that.


Add a mocking framework to go along ztest

Origin
https://github.com/meekrosoft/fff
Purpose
Allows mocking C functions.
Mode of integration
Module: from my experience it would be easier to update the fork. The module name should simply be fff
Description
Zephyr is light on tests and while zmake provides a test framework it's difficult to do anything less than an integration test right now. FFF is a simple function mocking framework that involves just a single header. Having this would allow for much faster tests with less dependencies.
Dependencies
None
Revision
7e09f07e5b262b1cc826189dc5057379e40ce886
License
MIT

I should also add that the current mocking framework for Zephyr has 2 downsides:

Anyone moving into Zephyr has yet another learning curve. FFF is the framework used on Android and is very common.
Zephyr's mocking is "incomplete" still and under featured.

CONFIG_ZTEST_PARAMETER_COUNT is needed and limits arguments
It isn't possible to use the framework to check the history of arguments. For example in FFF it would be possible to mock a function that's called N times and then (after it was used) assert the arguments (it's possible that we only care that the last call had specific arguments).

As per the TSC discussion I've also removed the testcase.yaml filter and FFF does appear to be working on the ARM qemus


[BUG] Getting 403 error (50001 missing access code)

Describe the bug
For some reason there is a place where I get 403 error code when I try to use the tool. It works everywhere else, only fails here. If I search by hand and delete, works great. I mean, of course I have rights to remove my own posts. Tried picking a Range, tried without Range - no dice.
It's an NSFW marked private room so that could be an issue?
To Reproduce
Steps to reproduce the behavior:

Go to a private channel that's locked from public access (AND IS set to NSFW).
Click the usual (get auth, get author, get guild/channel)
Hit Start
See error

Screenshots / Logs
Error searching messages, API responded with status 403!
	{"message":"Missing Access","code":50001}

Affects (Add an X to items that apply)

[ ] DMs
[ ] DM Groups
[X] Channel
[X] Channel (NSFW)
[ ] Server (All Channels)
[ ] Other (explain)

System:

OS: Windows 10
Browser Chrome, Firefox

Ps.: Thank you for the continued work on this script, it's truly a superb tool.

Ah found the issue here, and I had to use the scripts linked in comments AND enable NSFW toggle: https://github.com/victornpb/deleteDiscordMessages/issues/27


Print over shared printer

Hi,
I'm trying to print over a shared printer in Windows, is this possible?
Could I print over \<IP_ADDRESS>\printer ?
I have:

[x ] searched open and closed issues for duplicates

Thank you

Hi @aljimgar .
Since v.3.0a5 python-escpos supports printing through the win32 print queue thanks to #320, so if your printer is properly configured in Windows, you can send the commands as a print job using the Win32Raw() printer connector of the printer module.

Hi @aljimgar .
Since v.3.0a5 python-escpos supports printing through the win32 print queue thanks to #320, so if your printer is properly configured in Windows, you can send the commands as a print job using the Win32Raw() printer connector of the printer module.


Updates for heading capitalization and other misc. edits

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/680477e8fed3eef6b09692ea83a2dd12da1604df/


Invariant Violation: requireNativeComponent: "RCT3DARModelView" was not found in the UIManager.

hi i am facing this issue in android.

Seems like you haven't properly linked the library? https://facebook.github.io/react-native/docs/linking-libraries-ios

so you are saying it will work in android also right??

Yes it will run on android

Thanks for the help will check what's wrong with the linking.

i am facing the same issue.. i have even linked it right. Please tell me how to fix it ?


Add Armeria backend server

Add ArmeriaServerBuilder that binds HttpRoutes with Armeria server.
Add ArmeriaHttp4sHandler that converts an Armeria request from and to http4s'
Add ArmeriaExmaple based on the http4s repo

@rossabaker It's ready to review. 😉

Link back: https://github.com/http4s/http4s/pull/3614

Thanks for reviewing! @rossabaker


[nextjs] useTheme replacement does not work

Search keywords
useTheme nextjs
Latest version

[X] I have tested the latest version

Steps to reproduce
use useTheme from ../zero-styled to let Pigment CSS process.
Current behavior
Got error at build time:

As I dug deeper, I found that Next.js wraps the component before passing to Pigment like the snippet below:
const Component = /*#__PURE__*/_s(React.forwardRef(_c = _s(function Component(inProps, ref) {
  _s();
  const props = useThemeProps({
    props: inProps,
    name: "MuiIconButton"
  });
  return …
}, "526RDEpO1CGEADq5vnCvoNyCejQ=", false, function () {
  return [useThemeProps, useTheme, useUtilityClasses];
})), "526RDEpO1CGEADq5vnCvoNyCejQ=", false, function () {
  return [useThemeProps, useTheme, useUtilityClasses];
});

Since Pigment replaces useTheme with a variable, I think that's why useTheme is no longer available when Next.js before building the page at the end.
Expected behavior
The page should be rendered without any error.
Context
I am trying to use useTheme processor in https://github.com/mui/material-ui/pull/42476
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

@brijeshb42 I believe that useTheme should be changed to createUseTheme (we can add internal_ prefix to it) and update the runtime createUseTheme:
// runtime createUseTheme
import theme from '@pigment-css/react/theme';

export default function createUseTheme() {
  return function useTheme() {
    return theme;
  }
}

So that Pigment does not replace the useTheme in the consumer codebase:
import { createUseTheme } from '../zero-styled';

const useTheme = createUseTheme();

function Component() {
  const theme = useTheme();
}

@siriwatknp Is there a PR/branch to test the useTheme changes in material-ui ? I wanted to test few approaches.

Is there a PR/branch to test the useTheme changes in material-ui ? I wanted to test few approaches

You can test it at https://github.com/mui/material-ui/pull/42476 using the apps/pigment-nextjs-app.
FYI, I tried with this but does not work too:
// mui-material/src/Tooltip
import { useTheme } from '../zero-styled';

const useLocalTheme = () => useTheme();

…

function Tooltip() {
  const theme = useLocalTheme();
}

Nextjs wraps the useLocalTheme with useTheme dependencies too and since useTheme is replaced by Pigment, Nextjs throw the same error.


update cosmos properties description

As title, acronyms like db should be all caps.

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


BN does not parse/detect doubles if the binary is an ARM binary

Hello,
What is the feature you'd like to have?
Binary ninja cannot detect/parse doubles in HLIL/PseudoC view if the binary is an ARM binary
Additional Information:
I want to report a decompilation incapability. I have realized this while solving a challenge from r0. Mirror download link
In this situation we have a 32 bit ARM binary. Anyone can run binary in Raspbian.
This binary has been initializing some doubles. Then uses them. I have realized that Binary Ninja HLIL and Pseudo C views cannot decompile the doubles in exact values:
Disassembly:
00008624  e13f8fe2   adr     r3, data_89b0
00008628  d020c3e1   ldrd    r2, r3, [r3]  {data_89b0}  {0x400921cac083126f}
0000862c  f4214be1   strd    r2, r3, [r11,  #-0x14] {var_18}
00008630  0e3d8fe2   adr     r3, data_89b8

Pseudo C
00008628      int32_t r2;
00008628      int32_t r3;
00008628      r3 = HIGHW(0x400921cac083126f);
00008628      r2 = LOWW(0x400921cac083126f);

Let's cross check this binary in IDA Pro:
Disassembly:
.text:00008624 ADR     R3, dword_89B0
.text:00008628 LDRD    R2, R3, [R3]
.text:0000862C STRD    R2, R3, [R11,#f1]
.text:00008630 ADR     R3, dword_89B8

Pseudo C
  double v20; // [sp+68h] [bp-1Ch]
  double v21; // [sp+70h] [bp-14h]
  int i; // [sp+7Ch] [bp-8h]

  v21 = 3.1415;
  v20 = 6.283;

BTW, I have extracted the pseudo c code and recompiled as x86, then check it through Binary Ninja:
Pseudo C
00001243      double var_58 = ((double)((long double)3.1415000000000002));
00001263      double var_48 = ((double)((long double)9.9000000000000004));
.
.
.
snip code
.
.
.
((long double)((double)((long double)6.2830000000000004)))

Final words
Binary Ninja have problems detecting/parsing doubles if the binary is an ARM binary, but can decompile/detect doubles if the binary is x86 binary

The relevant code in HLIL:
main:
   0 @ 00008628  int32_t r2
   1 @ 00008628  int32_t r3
   2 @ 00008628  r3:r2 = 0x400921cac083126f
   3 @ 0000862c  double var_18 = r3:r2
   4 @ 00008634  int32_t r2_1
   5 @ 00008634  int32_t r3_1
   6 @ 00008634  r3_1:r2_1 = 0x401921cac083126f
   7 @ 00008650  int32_t r2_2
   8 @ 00008650  int32_t r3_2
   9 @ 00008650  r3_2:r2_2 = 0x4023cccccccccccd
  10 @ 00008654  int64_t var_30 = r3_2:r2_2

I think the real problem is we do not support setting the type of sth like r3:r2. Otherwise, we should have displayed it correctly. @plafosse

The binary uploaded to GH:
548774e79cb74a656e8c75dc82cfa7fc.zip


Add missing 'logging' imports

Those imports were missing and lead to errors in case of other errors which should be logged but logging was not imported yet.

Yeah, even better this way. Thanks.


build: set up caretaker note label in merge script

Updates to the latest version of the dev-infra package, so
that we could leverage the new caretaker note label prompt.
The script will prompt/warn the caretaker if a note is
set up. This should help with raising awareness for
special attention required by the caretaker.

@devversion needs rebase

@mmalerba done!


Cleaned picks.csv formatting with the csv library

I described issue https://github.com/wayneweiqiang/PhaseNet/issues/9 a while ago and here is the PR with the fix. The fix is a two-part solution.
First, I open the picks.csv file in the write w mode with the csv.writer from the csv library and write the header row. The write w mode will overwrite any existing file with the same filename.
I then open picks.csv in the append a mode and write the results to picks.csv by looping through each batch. The results are converted from arrays to lists with the tolist() method which removes the excess white spaces. I then append the results to the csv with the writerow() method by passing the results in list format. This automatically delimits the csv columns into fname, itp, tp_prob, its, ts_prob and adresses any issues like overfull lines automatically (see issue https://github.com/wayneweiqiang/PhaseNet/issues/6).
I have tried and tested the method and it works as hoped. When reading the csv files with pandas, one should still note that the pandas.read_csv() method will default to reading all entries as strings. This is described fully in a stackoverflow post. An easy fix is using the literal_eval method from ast.
>>> from ast import literal_eval
>>> literal_eval('[1.23, 2.34]')
[1.23, 2.34]

Best,
Lenni

Here is an excel copy of an example output.
picks.xlsx


Template Strings ?

Is it possible to use template strings inside a blaze component, essentially eliminating the need for .html files ?
This is just a generate question as I have not tested whether or not it can be done.
something like.
MyComponent extends BlaseComponent {
        template: `

{{someVar}}

       `
}

Maybe, but not yet. This would require one to have a Spacebars compiler on the client, and while this is doable, often you do not want extra libraries on the client.


[now deploy] Check server.js file when detecting the platform version

Check server.js file when detecting the platform version

Build is failing:
Error: [tsl] ERROR in /home/circleci/repo/src/util/prefer-v2-deployment.ts(23,3)
      TS2339: Property 'hasServerfile' does not exist on type '{ hasDockerfile: boolean; pkg: CantParseJSONFile | Package | null; localConfig: Config | undefined; }'.

Codecov Report

Merging #2664 into canary will decrease coverage by 0.04%.
The diff coverage is 87.5%.

@@            Coverage Diff            @@
##           canary   #2664      +/-   ##
=========================================
- Coverage    8.07%   8.02%   -0.05%
=========================================
  Files         259     259
  Lines       10455   10420      -35
  Branches     1324    1323       -1
=========================================
- Hits          844     836       -8
+ Misses       9554    9527      -27
  Partials       57      57

Impacted Files
Coverage Δ

src/commands/deploy/index.js
0% <ø> (ø)
:arrow_up:

src/util/prefer-v2-deployment.ts
69.44% <87.5%> (+6.58%)
:arrow_up:

src/util/dev/yarn-installer.ts
37.28% <0%> (-0.81%)
:arrow_down:

src/util/dev/builder-cache.ts
39.48% <0%> (-0.42%)
:arrow_down:

src/util/dev/server.ts
11.52% <0%> (-0.25%)
:arrow_down:

src/util/dev/builder.ts
12.43% <0%> (+0.26%)
:arrow_up:

src/util/get-files.ts
87.07% <0%> (+0.81%)
:arrow_up:

src/util/output/create-output.ts
29.54% <0%> (+2.46%)
:arrow_up:

src/util/dev/router.ts
80.3% <0%> (+4.58%)
:arrow_up:

src/util/metrics.ts
68.18% <0%> (+6.64%)
:arrow_up:

... and 1 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 1b9c14b...35165d9. Read the comment docs.


Bump podspec to  '<IP_ADDRESS>'

The latest release is '<IP_ADDRESS>', however, in podspec the version is  '<IP_ADDRESS>', which is incorrect.
Please fix it.

Resolved with 0.4.0.


FLINK-23454 The upstream sends the buffer of the right size for unicast case

What is the purpose of the change
This PR implements the reaction on NewBufferSize. It changes the size of output buffers corresponded to the received information.
Brief change log

Added the support of changing the max capacity to BufferBuilder
Subpartition is able to notify the desirable buffer size for input buffer consumer.
Notifying the subpartitions about the new received buffer size.
*LocalInputChannel notifying the subpartition about the new buffer size directly. *
*ResultPartition changes the BufferBuilder size according to the desirable buffer size of each subpartition. *

Verifying this change

Added unit tests for each classes which behaviour was changed

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@pnowojski , tests finally are green. So please pay attention to the first(https://github.com/apache/flink/pull/16726/commits/62e69286ad4a4a2367bac131fed2cbe0b71337f5) and the last(https://github.com/apache/flink/pull/16726/commits/8b6e33923bfbb843e425dc87d65520e595c5fea8) commits which were changes recently. Also, benchmarks look good:

http://codespeed.dak8s.net:8080/job/flink-benchmark-request/410/
http://codespeed.dak8s.net:8080/job/flink-benchmark-request/429/


Vulnerability roundup 113: darkhttpd-1.13: 1 advisory [7.5]

search, files

[ ] CVE-2020-25691 CVSSv3=7.5 (nixos-21.11, nixos-unstable)

CVE details
CVE-2020-25691
A flaw was found in darkhttpd. Invalid error handling allows remote attackers to cause denial-of-service by accessing a file with a large modification date. The highest threat from this vulnerability is to system availability.

Scanned versions: nixos-21.11: a62ce97f92b; nixos-unstable: ff9efb0724d.
Cc @bobvanderlinden

Can't find any reference to this from upstream. Function mentioned in redhat issue doesn't appear to have been touched for 11 years.

Probably not much we can do here. Let's focus on things that are actually actionable.


crba is not working in c++, but works in python

Bug description
crba is not working in C++, but works in Python
Reproduction steps
C++ code:
#include <iostream>

#include "pinocchio/parsers/urdf.hpp"
#include "pinocchio/algorithm/contact-dynamics.hpp"

int main() {
    pinocchio::Model model;
    pinocchio::urdf::buildModel("./example.xml", model);
    pinocchio::Data data(model);

    auto q = Eigen::VectorXd::Zero(model.nq);
    std::cout << pinocchio::crba(model, data, q) << "\n";
    return 0;
}

Compiled by g++ -std=c++11 main.cpp -o main $(pkg-config --cflags --libs pinocchio)
Python code:
model = pin.buildModelFromUrdf('example.xml')
data = model.createData()
q = np.zeros(model.nq)
print(pin.crba(model, data, q))

Runned by python3.9 main.py
example.xml:
<robot name="manipulator">
  <link name="ground_frame">
    <origin xyz="0.0 0.0 0.0" rpy="0.0 0.0 0.0"/>
  </link>

  <joint name="joint_1" type="continuous">
    <origin xyz="0 0 0" rpy="0 0 0"/>-->
    <parent link="ground_frame"/>
    <child link="body_1"/>
    <axis xyz="0 0 1" />
  </joint>

  <joint name="joint_2" type="continuous">
    <origin xyz="0 0 1" rpy="0 0 0"/>-->
    <parent link="body_1"/>
    <child link="body_2"/>
    <axis xyz="1 0 0" />
  </joint>

  <link name="body_1">
    <inertial>
      <origin xyz="0 0 1" rpy="0 0 0"/>
      <mass value="1"/>
      <inertia ixx="1" ixy="0" ixz="0" iyy="1" iyz="0" izz="1" />
    </inertial>
  </link>

  <link name="body_2">
    <inertial>
      <origin xyz="0 1 0" rpy="0 0 0"/>
      <mass value="1"/>
      <inertia ixx="1" ixy="0" ixz="0" iyy="1" iyz="0" izz="1" />
    </inertial>
  </link>
</robot>

Running C++ version leads to:
main: /opt/openrobots/lib/pkgconfig/../../include/pinocchio/spatial/symmetric3.hpp:418: pinocchio::Symmetric3Tpl<Scalar, Options> pinocchio::Symmetric3Tpl<Scalar, Options>::rotate(const Eigen::MatrixBase<OtherDerived>&) const [with D = Eigen::Matrix<double, 3, 3>; _Scalar = double; int _Options = 0]: Assertion `isUnitary(R.transpose()*R) && "R is not a Unitary matrix"' failed.
Aborted (core dumped)

Running Python version:
[[2. 0.]
 [0. 2.]]

Additional info:
Pinocchio installed according to this
System

OS: Ubuntu 22.04.3 LTS
Pinocchio version: 2.6.20

@someilay : I can't test why your version is not working right now, but could you test your code with CMake instead of pkg-config ? We have an example here: https://github.com/stack-of-tasks/pinocchio-minimal

Oh, I guess it is "working" in python because the module is compiled in release mode.
What happen if you add -O2 to your compilation line ?

@nim65s. Thank you for response. With minimal CMake this code starts to work). Can you explain why manual compiled code fails?

Hello @someilay,
Thanks for the nice reproduction steps you have give. I have been able to reproduce your issue easily.
There is no issue with the compilation. When building with pkg-config you're not giving the -DNDEBUG flags and asserts are then activated.
It's a good thing, because the assert had detect that you give an unnormalized quaternion in the freeflyer.
If you change your code with the following code then the assert is not raised anymore:
#include <iostream>

#include "pinocchio/parsers/urdf.hpp"
#include "pinocchio/algorithm/contact-dynamics.hpp"
#include "pinocchio/algorithm/joint-configuration.hpp"

int main() {
    pinocchio::Model model;
    pinocchio::urdf::buildModel("./example.xml", model);
    pinocchio::Data data(model);

    auto q = pinocchio::neutral(model);
    std::cout << pinocchio::crba(model, data, q) << "\n";
    return 0;
}

Here, I just call pinocchio::neutral instead of Eigen::Zero to initialize q. This ensure an unit quaternion for the freeflyer joint.
I'm still available if you have anymore questions.

@jorisv. Thank you for clarifying the compilation process. However, I didn't get why such simple system needs quaternions. Moreover, suggested solution doesn't explain how to set manual configuration.

@someilay,
I check again your example and I answered too fast.
You don't have freeflyier joint (by default buildModel add a Fixed joint as robot base), but you have continuous joints.
Here the description of this joint in the URDF documentation:

a continuous hinge joint that rotates around the axis and has no upper and lower limits.

So... it seem to be a revolute joint without limits. But, it's a little more complicated than that. This kind of joint can be used to model wheel. Issue is the value of this joint, since it doesn't have limits, can reach a really high value.
So instead of using joint angle to model the joint configuration we use the cos(angle) and sin(angle) value.
The continuous joint can then rotate indefinitely without reaching infinity.
It's why the 0 configuration you give at the beginning wasn't working.
If you want to manually set the configuration you can just wrote:
Eigen::VectorXd q(4);
q << std::cos(angle1), std::sin(angle1), std::cos(angle2), std::sin(angle2);

Also, if you finally don't need continuous joints, you can use revolute joints.
q will then be a size 2 vector that will contains angle1 and angle2.

@jorisv, now it makes senses. Thank you


Expose deep links in the UI

For example, in https://sindresorhus.com/playground/KeyboardShortcuts_Name/, it would be nice when I hovered over init?(rawValue:), it would show a link icon and clicking it would give me a direct deep link to that method. Like with headers in GitHub readme's.

That's a great idea, @sindresorhus.
For posterity, here's a screenshot of how GitHub renders heading anchors:

Fixed by https://github.com/SwiftDocOrg/swift-doc/pull/275


Github 1544: build: Initial fixes for MinGW-w64 on Windows.

These are initial fixes for MSYS2 MinGW-w64 on Windows.
It should also build with GCC without problems, although I haven't tested that yet.
A lot of the tests are failing and some of the layer tests even segfault.
This is the output of the failing tests, but to debug it you would have to build them yourself, unless you don't mind me providing binaries.
https://gist.github.com/DragoonX6/d9a846a5a995df698bf787c0b82c8053
I've tried taking a look at the segfaulting test in a debugger, but I couldn't work out why this crashed.
The samples do actually work though.
Please review the code so we can pin down what's actually causing the tests to fail.

Updated with some more fixes to get it building again, and rebased to master. Please review.

The Travis-CI builds are still failing.  (I cleared the cache and restarted it to get around an apparent caching problem.)  It looks like the Linux builds are trying to use xcopy.  Please fix that.
Also, your 6f7c765 commit seems to introduce a lot of unneeded whitespace changes.  You might want to drop that commit and make another one without any unintended whitespace changes.

Looks like those whitespace changes slipped through unintendedly.
I'll get to it once I'm back from work.

@karl-lunarg Fixed the white space issue and fixed the build.
Appveyor build is still broken because of a bug in MSVC, which is an easy fix, but out of scope for this PR.

@karl-lunarg ping.

@karl-lunarg  is on travel.  He'll get to this as soon as he can.

Alright, do you have any idea when he's going to be back? I'll try to rebase with master often so I don't diverge too much.

I believe he'll be back either Thursday or Friday, but I don't know when he'll have a chance to get to this since he is actively working another project.

That's okay, the earliest I can probably do after Friday is Monday, so no rush.

The Appveyor problem needs to be fixed as well.

It's a bug with visual studio that's technically out of scope for this PR.
The bug is that VS thinks that _strdup is deprecated and that you should use _strdup, this warning is meant to fire for strdup instead.
I can fix it in this PR, but I think a separate PR would be more appropriate.
Also there's a caching problem with Appveyor, because if you look at the build log it's obviously failing, but because it's restoring the build from cache it appears to be working.

Updated to conform with the review.

Would porting the MASM code to YASM/NASM be a viable alternative? It does introduce an extra dependency, but having less code to maintain (in contrast to an extra GAS asm file) sounds like a plus.

I had though about using other assemblers back when we introduced this (NASM was the one I had in mind), but the main reason we didn't do it was because of the extra dependency. The other reason is that even with another assembler, writing cross platform assembly still isn't particularly easy. And there is a certain simplicity to just separating the code for the two platforms entirely.
So I think the answer is that while we could use NASM/YASM/whatever, we'd rather not switch to that, partly because of the dependency issue, and partly because we know that the current assemblers work fine for our needs. Also, while there's more code with the current setup, it's pretty low maintenance code (unless we try to port to other platforms) so maintenance hasn't been much of an issue.

I meant using NASM/YASM for Windows, not for both Windows and Linux. Basically we'd stay with 2 files, but just swap out the MASM assembler.

Well for Windows it really comes down to dependencies. The vast majority of people who work with our software on Windows are using Visual Studio. Consequently, it makes sense to default to the assembler that ships with Visual Studio. I'm just curious, what's your objection to Visual Studio? Is it because it's closed source or something?

My qualms with Visual Studio are mostly with the (un)install process, and the standard compliancy of the compiler. The install size is also somewhat of an issue, but it's not that big of an issue anymore.
My current code base depends on GNU ld, so it's a bit hard for me to switch until I either write a new CRT, or port an existing CRT that supports my use case, or modify all the external libraries I use.
I also chose for MinGW-w64 because porting my code from Linux to Windows was easier using that compiler, and it also generates slightly faster code. Apart from that, I'm really attached to clang as a compiler, so there's that too.
I get the argument about the dependency, but let's be honest, if I were to port the MASM code to GAS for MinGW-w64 builds (unlikely, since my asm knowledge is next to none), it would be largely unmaintained, since nobody else uses the setup or tests for it. I think porting the code to YASM/NASM would widen the Vulkan userbase, while keeping the burden on you lower.
I get that the most users use VS, but they also use the SDK instead of going through the whole process of compiling it from source. Having it work for MinGW-w64 would enable packagers and the MSYS2 project to release builds for their distributions, taking away the burden of packaging it for this setup from you guys.

I don't think that maintaining NASM code would be any easier than maintaining MASM code. It would make MinGW builds easier, but it would make Visual Studio builds harder. Also, while you're right that most Visual Studio users go through the SDK, it's still pretty common for people to get the code from the repo. Driver vendors often want to test with the latest code, and that's only in the repo. Also, if developers find a problem in the SDK, they'll sometimes move to the repo where we can get a fix more quickly. And in an open source project, there's always other random people using the repo for a number of reasons.
I'm also not really concerned about maintaining this assembly code (even if we have another platform), because the code actually does very little. It just unwraps one or two objects and calls down the loader's call chain. On top of that, this code is very unlikely to need to change, since it only depends on a couple of Vulkan conventions (the first argument has to be a dispatchable object). However, I'm busy enough that I don't have time to write this new code (actually, it's the testing that would really eat up time).
If you don't want to write up the assembly code for GAS/Windows, then I see two potential solutions. One is that we just use the C code that may or may not work, This isn't going to cause you problems unless you're writing new extensions. The other option is that there's an assembler called JWasm which claims to be MASM-compatible. I should warn you I know nothing about this assembler, but it seems like you may be able to use that to assemble to the MASM code. Personally, I think simply falling back on the C code seems like the best solution, but you seem like you're not crazy about that idea (though it is currently what we do with non-x86 builds).

It's not that I don't want to write the assembly code, it's that I lack the knowledge to.
I'm not sure how long it would take me to get the required knowledge for me to port it, but I doubt it's a short time frame.
I guess I can give JWasm a try, but I have a feeling it won't be that easy to get it in.

@lenny-lunarg, @DragoonX6, any updates here, or has this MR outlived its usefulness?

I don't have any updates here. Right now it looks like the PR would have to be brought up to date to merge it. I'd be willing to take a PR if it is brought up to master and if the assembly code is either updated for MinGW, or is removed from MinGW builds and replaced with the existing C code. I'm going to close this since it appears dead, but if @DragoonX6 wants to update this PR I can reopen it when that happens.

I sadly don't have the time to work on this in the near future. And if the PR were to be merged, the test failures would have to be addressed too.
Perhaps somebody else is willing to pick this up.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Lenny Komow<EMAIL_ADDRESS>Sent: Friday, December 15, 2017 9:48:49 PM
To: KhronosGroup/Vulkan-LoaderAndValidationLayers
Cc: DragoonX6; Mention
Subject: Re: [KhronosGroup/Vulkan-LoaderAndValidationLayers] Github 1544: build: Initial fixes for MinGW-w64 on Windows. (#1923)
Closed #1923https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/pull/1923.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/pull/1923#event-1390307963, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABilbww8BB0L-46dtzMHwz7w9NeWCNHKks5tAtswgaJpZM4OJqHE.


Is there a way to know when video has been created ?

Hello,
How can I know if the video finished creating ? I saw it took some time, that's fine, but can I know when it's done ?
Thank you for this amazing lib !
Yoann

Hello,
How can I know if the video finished creating ? I saw it took some time, that's fine, but can I know when it's done ?
Thank you for this amazing lib ! Yoann

I think you can search for a way to get it from the ffmpeg command.
Probably some usage of verbose to a file might be helpful here.
Feel free to share here if you find something interesting.


Fix #302: Handle paths to local jars in dependency declarations.

I've verified that this works with my packaging PR #364 , i.e. local jar dependencies are correctly added when creating a package in Gradle.  I can add tests for this as a separate, later PR (as it needs both this PR and #364 to be merged to be able to test both packaging and non-packaging scenarios).

Closing it as per discussion in https://github.com/holgerbrandl/kscript/issues/302.
Another solution is mentioned in this ticket, which IMHO would be a much better approach.


Harmonize issue labels

Summary
Use a consistent set of labels across repositories in this organisation.
Details
A bash script that creates/updates labels across select repositories
Motivation and Context
As discussed in last week's community meeting we want to establish a triage process for issues and pull requests. This is to lower the cognitive overhead for regular contributors.
For this purpose, a GitHub Projects Board has been created. We want to use a consistent set of labels (with identical colour and description) so that the board will be easier to read.
I've set up a temporary repository with these labels here.
Before this is rolled out we need to:

[ ] Manually rename existing labels
[ ] Remove remaining labels that are not in the proposed standard set

An exception will be made for the cucumber/cucumber monorepo, which needs additional tags to separate between modules and languages.

@cucumber/committers - any objections or suggestions before I start harmonising labels?

Awesome ! 👍

Looks good. Did we decide what to do with “discussions”?

Looks good. Did we decide what to do with “discussions”?

I think the new GitHub discussions look great, but I'm afraid it would cause too much fragmentation. We already have Slack, GitHub issues/PRs and the SmartBear Community.
Whenever people open an issue that looks like a question / discussion, I suggest we:

Tag it with ❓ question
Leave a canned comment (mine says Please use the [support](https://cucumber.io/tools/cucumber-open/support) forums for questions and discussions. We use GitHub issues to track bugs and contributions exclusively.)
Close the issue

(Just realised the support page still mentions the defunct google group - I've made a note to update that).

"Slow Burner" tag is used to prevent stalebot from closing the issue if inactive for too long.
In my opinion, "Slow Burner" is obfuscating the real intent of this tag. I suggest to rename "Slow Burner" tag to stalebot's default "pinned" which is more widely used and recognized.
Thoughts?

I like pinned (with a 🧷 ) - will go for that!

The Spring project has the waiting-for-feedback and feedback-provided labels. The waiting-for-feedback is a manual label with a @ mention and the feedback-provided is an automated label change.

It is pretty useful to filter the issues where someone provided the required information for an incomplete issue.
Also the Spring team uses the waiting-for-triage to filter incoming issues but I am not sure how useful that is.

I'd second the status and kind prefixes.

I agree various workflow labels are useful. I'll leave them out for this PR - we can add them later. I think there might be bots that can help us out with that.

I'm agnostic to the "what" but I do like the "why"

I have rolled out the harmonized tags to the most active repos. I've also filled up the new board according to the guidelines in the new TRIAGE.md document. In short, the issues in Next:

consists of a mix of languages
are a mix of PRs and bug issues
they are all "old" (following a FIFO pull policy)

/cc @aurelien-reeves


Initialization Issues

The variable used for the final process.chdir is startDir but the variable that was defined is startingDir. The concerning part is that this never complained before...but someone found it

Fixed with b19e373


add Dhgeqz and Dlapy3

Part of #1651.
Dhgeqz's eigenvalues do not seem to be a solution for the GNEP using input or resulting H and T matrices as far as I can tell. I'm guessing I need direct input from Dggbal? I've run comparisons of eigenvalues with reference and I'm getting identical up to tol=1e-14 results.
This is how I tried to test the solution no GNEP:
        // Compute right and left hand sides of
	//   H*x = lambda*T*x
	// Where lambda are the eigenvalues computed by Dhgeqz.
	lhs := blas64.Vector{N: n, Data: make([]float64, n), Inc: 1}
	rhs := blas64.Vector{N: n, Data: make([]float64, n), Inc: 1}
	x := blas64.Vector{
		N:    n,
		Data: randomSlice(n, rnd),
		Inc:  1,
	}
	blas64.Gemv(blas.NoTrans, 1, hCopy, x, 0, lhs)
	for i := 0; i < n; i++ {
		if alphar[i] == 0 && alphai[i] == 0 && beta[i] == 0 {
			continue // singular EV.
		}
		lambdar := alphar[i]
		lambdai := alphai[i]
		if beta[i] != 0 {
			lambdai /= beta[i]
			lambdar /= beta[i]
		}
		if lambdai != 0 {
			continue // Imag EV.
		}

		blas64.Gemv(blas.NoTrans, lambdar, tCopy, x, 0, rhs)
		if !floats.EqualApprox(lhs.Data, rhs.Data, tol) {
			t.Error("H*x != lambda*T*x", i, complex(lambdar, 0), lhs.Data, rhs.Data)
		}
       }

Codecov Report
Patch coverage: 78.48% and no project coverage change.

Comparison is base (93223b4) 74.00% compared to head (494271a) 74.01%.
Report is 12 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           master    #1897    +/-   ##
========================================
  Coverage   74.00%   74.01%
========================================
  Files         526      525     -1
  Lines       63210    63670   +460
========================================
+ Hits        46778    47123   +345
- Misses      13854    13966   +112
- Partials     2578     2581     +3

Files Changed
Coverage Δ

lapack/gonum/dhgeqz.go
78.44% <78.44%> (ø)

lapack/gonum/dlapy3.go
100.00% <100.00%> (ø)

... and 9 files with indirect coverage changes

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


Add Node SPR endpoint

Adds a text only API endpoint curl http://<IP_ADDRESS>:8080/api/codex/v1/spr to simplify curl commands.
Question, when node.discovery.dhtRecord.isSome is empty what should we do? I followed the debug info and return empty string 204 status code. Though perhaps it should be an error, maybe a 503?
Implements https://github.com/orgs/codex-storage/projects/3/views/9?pane=issue&itemId=57116903

I am not a fan of the "text endpoint" approach. IMHO we should soon show some love to the API by, for example, unifying all the endpoints to return the same content type (IMHO JSON).

This endpoint is primarily for simplifying the tutorials for how to run nodes, which is why I initially went with text. Though I'm not opposed to JSON, I'd like to get @benbierens feedback on that as well.

Regarding "what to do if no SPR is defined," it depends on whether it is a valid state. If I understand it correctly, it is not a valid state for the node to not have an SPR.

Ok that's what I was wondering. The only reason I could think would be while the DHT is initializing and perhaps the SPR wouldn't have been configured yet.

I am not a fan of the "text endpoint" approach. IMHO we should soon show some love to the API by, for example, unifying all the endpoints to return the same content type (IMHO JSON).

This endpoint is primarily for simplifying the tutorials for how to run nodes, which is why I initially went with text. Though I'm not opposed to JSON, I'd like to get @benbierens feedback on that as well.

I am also not a fan of a text endpoint and would prefer a JSON object. Still, in this case I think we should make an exception: If people start having fun with shell scripts and curl commands, having the node return a plain SPR that you can just throw in a var and use, is very handy. I'm sure JSON-parsing exists in shells on lots of platforms. But why make it more complicated?

Regarding "what to do if no SPR is defined," it depends on whether it is a valid state. If I understand it correctly, it is not a valid state for the node to not have an SPR.

Ok that's what I was wondering. The only reason I could think would be while the DHT is initializing and perhaps the SPR wouldn't have been configured yet.

Maybe during the earliest second, there is no SPR and returning and error code would be good, I think. 500? 503? I don't speak HTTP codes. Probably the one that means "Try again in a few seconds, please."

Ah, looks like I'll have to go back and sign my commits.

Oops, I forgot Content-Type http header is for the uploaded data, while Accept is the header for a client to specify their desired response type see MSDN.

Okay, fixed things and updated the twoclients docs. I'd appreciate if you guys could check the two client doc updates.
I also added a curl -X GET -H "Accept: text/plain" http://<IP_ADDRESS>:8081/api/codex/v1/peerid endpoint.

Ran the updated openapi.yaml through the dist-test code generator: Checks out. 👍

Wouldn't that suffice for your case @elcritch ? IMHO I would avoid information being duplicated between endpoints.

Normally I'd agree with you, but the debug/info endpoint is a debugging endpoint and these new endpoints are mainly to help simplify the guides. Also, I think it's info we should commit to offering them directly in the API rather in the debugging section since they're core to our current DHT.
Mainly these new endpoints make it simpler on parts of the user guides. You don't need a tool like jq to automate anything either. We discussed it in a client meeting and everyone seemed ok with adding the extra endpoints if it could simplify the guides.


Added the 1.22 docs

Issue #, if available:
Description of changes:

Added new doc for 1.22
Updated existing docs for 1.22
Fixed some incorrect project versions in some docs for other versions
Reformatted some markdown tables IntelliJ has been mad about for months and I was sick of seeing the warning for

/hold
Do not unhold unless you're 100% sure this is the right call (or until I do so myself)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/retest

/test eks-distro-docs-presubmit

/retest


Selection highlighting is one character off

Tmux 2.7
ZSH 5.5.2
Mac OS X 10.13.4
Alacritty @ 24e8a19

The letter 'c' is part of the selection (as desired) but is not highlighted.
(The error happens when selecting in the middle of a line too.)

Is your cursor on the c? it looks like it's highlighted properly but inverted.


DatArchive Persistence and Write Permissions

I ran this code in the Firefox:

const archive = await DatArchive.create({
      title:"Test",
    });

console.debug(archive);

Then I copied the URL from the console, and changed my code to:
const archive = await DatArchive.load("dat://f8c1bd14267d5783a06ed7ca9d255a6ca957b4be853ec415f77cda2ce4dda7ed");
await new Promise(resolve => setTimeout(resolve, 4000));
await archive.writeFile('/test.json', 'Hello World!');

and I get:
Error: Cannot write to this archive ; Not the owner
Here's a link to glitch:
https://glitch.com/edit/#!/ralphie-line

Thanks for the bug report and repro! I think it should be fixed in 0.3.4. https://github.com/datproject/sdk/releases/tag/v0.3.4
Also, you shouldn't need the delay anymore since I changed how it does the initial load.


Convert sample to use BackgroundService

Convert the BackgroundTasksSample-WebHost sample over to BackgroundService.

Requires commensurate changes to the topic's text.
Probably need to snapshot 2.0 code, since BackgroundService is new in 2.1.

See: https://github.com/aspnet/Docs/pull/7397

Yeah let me know what I need to do

Sure ...

In the snapshot folder for the WebHost version of the sample at ...

aspnetcore/fundamentals/host/hosted-services/samples-snapshot/2.x/BackgroundTasksSample-WebHost
... create a copy of the current QueuedHostedService.cs file ...
aspnetcore/fundamentals/host/hosted-services/samples/2.x/BackgroundTasksSample-WebHost/Services/QueuedHostedService.cs
... this will serve as a snapshot of the 2.0 version. We'll show it for now, since BackgroundService is only available for 2.1+.

Make the changes that you had over on #7397 to the file at ...

aspnetcore/fundamentals/host/hosted-services/samples/2.x/BackgroundTasksSample-WebHost/Services/QueuedHostedService.cs
... just as you did on your patch branch before.

In the topic, where the prior QueuedHostedService.cs was described for the 2.0 sample, you'll isolate existing text in a moniker range that will only show that text when the 2.0 version of the topic is loaded. When you provide alternate text that describes the BackgroundService version, that text will receive a moniker range for 2.1 or later. The links to the two sample files only differ by the word "snapshot" in a link segment. Here's an example ...

::: moniker range=">= aspnetcore-2.1"

Describe the new BackgroundService version here. To link to the 2.1 sample file, use this ...

[!code-csharp[](hosted-services/samples/2.x/BackgroundTasksSample-WebHost/Services/QueuedHostedService.cs?name=snippet1&highlight=30-31,35)]

::: moniker-end

::: moniker range="= aspnetcore-2.0"

Retain the current text from the topic for 2.0 readers. To link to the 2.0 sample file, use
the following (note "snapshot" in the path segment). You just need to re-target the
current link to the *samples-snapshot* folder ...

[!code-csharp[](hosted-services/samples-snapshot/2.x/BackgroundTasksSample-WebHost/Services/QueuedHostedService.cs?name=snippet1&highlight=30-31,35)]

::: moniker-end

The moniker ranges and build system will take care of the rest.
Note on sample links: You'll see we use snippets to isolate the code for the topic to display. You can highlight lines and ranges of lines as needed.
Since you'll be working with multiple files, I recommend forking/cloning the repo and creating/submitting the PR from your own branch. It's not strictly required. You can start with a "patch" branch, then set the repo to that branch and keep working on and committing additional files to the branch in the GH UI until the PR is ready. If you go that way tho, I recommend marking the title with "[WIP]" when you commit the first file on the patch PR to let us know you're still working on it.
Start your PR with the text Fixes #7638, and this issue will auto-close when the PR merges. I'll call for engineering review after you submit the PR. When they're done, we'll just touch up any MS style guidance issues.
MS style and grammar guidelines are at :point_right: https://docs.microsoft.com/style-guide/welcome/
... and if it isn't covered there, we go by the Chicago Manual of Style .... or we just make it up! :smile: lol We do have quite a few little rules and customs. Don't sweat it tho, we'll touch up little things at the end before merging.
Thanks for the help.

I've created a pull request for here https://github.com/aspnet/Docs/pull/7640


[ConvenienceService] [Data] /v1/provide-list-of-actual-device-equipment response needs to return all attributes marked as required

The service  /v1/provide-list-of-actual-device-equipment returns on data from the Cache, derived as follows:
ElasticSearch://control-construct={mountName}?fields=top-level-equipment;equipment(uuid;actual-equipment(manufactured-thing(equipment-type(type-name))))
I tried running a responseBody completeness test in the lab, where the responseBody is compared to the responseSchema.
The required property equipment-type-name of actual-equipment-list sometimes is missing, therefore the testcase fails (which is not actually an MWDI issue).
See example for mount-name: 513559991A

{
  "top-level-equipment": [
    "SLOT-1"
  ],
  "actual-equipment-list": [
    {
      "uuid": "RMM-1",
      "equipment-type-name": "Removable Memory Module"
    },
    {
      "uuid": "SFP-1.2",
      "equipment-type-name": "10GBASE_LR_LW"
    },
    {
      "uuid": "SFP-1.3",
      "equipment-type-name": "1000BASE_T"
    },
    {
      "uuid": "SFP-1.4"
    },
    {
      "uuid": "SLOT-1",
      "equipment-type-name": "MINI-LINK 6352 80/21H"
    }
  ]
}

For SFP-1.4 there is no equipment-type-name.
The OAS lists this attribute as required. As this is a convenience server and not a ressource path, MWDI should not just return what is see's in the cache 1:1. Instead MWDI implementation should be modified as follows:

return all attributes listed as required in the responseSchema
if found in the CC fill the attribute with the found value
if an attribute is missing in the CC, it will still be included, but with an empty string as value

(If required the description in the OAS could be extended to reflect that requirement more clearly (with own issue), this would be done with milestone v1.1.3_spec.)

Tested ok 1.1.2.c_impl
Example for mount-name: 513250009

Tested with latest  MWDI version 1.1.2.g_impl, Issue is no longer observed.
http://XXXXXX:XXXX/v1/provide-list-of-actual-device-equipment

{
  "top-level-equipment": [
    "SLOT-1"
  ],
  "actual-equipment-list": [
    {
      "uuid": "RMM-1",
      "equipment-type-name": "Removable Memory Module"
    },
    {
      "uuid": "SFP-1.2",
      "equipment-type-name": "10GBASE_LR_LW"
    },
    {
      "uuid": "SFP-1.3",
      "equipment-type-name": "1000BASE_T"
    },
    {
      "uuid": "SFP-1.4",
      "equipment-type-name": ""
    },
    {
      "uuid": "SLOT-1",
      "equipment-type-name": "MINI-LINK 6352 80/21H"
    }
  ]
}


Clarification note for picking hash vs append distribution

I'm capturing @umurc's note in the internal email thread (re: Hash vs append distribution) in this issue. @umurc brought this up as a semi-related issue as part of our discussion on #95.
Related to this thread but as a separate item, I'm noting the current explanation for append might also impact its usage: "Append distributed tables are best suited to append-only event data which arrives in a time-ordered series." --> users might relate to this and pick this method, without considering/being aware of its broader implications.

Closing this due to newly created #135 and our desire to promote the multi-tenant and analytics use cases.


Scope autocompletion problem

Posting this just to keep track on that annoying issue
The problem
Currently, using the "sass-in-rust" styling, like the following:
styly!(scope {
    .sel1.sel2 {}
});

One can't get proper scope:: autocompletion from rust-analyzer.
It seems to work with styly!(scope "path/to/file.scss") though.
The root of evil
While I was writing the parsing part of procmacro, I've noticed then styly! seems to receive nothing where brackets with the code should be, just like if I wrote bare styly!(scope );
Initially, the code which parses arbitrary style in brackets was:
// sabry_procmacro_impl/src/impls/mod.rs
// impl Parse for ArbitraryStyleBlock
// fn parse

let _s;
braced!(_s in input);
let stream = _s.parse::<TokenStream>()?;
let c = match stream.span().source_text() {
    Some(stx) => stx,
    // TODO: rust-analyzer does fall into this even if all is fine
    None => return Err(syn::Error::new(stream.span(), "Source code expected")),
};

And that was the cause of editor false-positive error "Source code expected".
Now it looks like this:
let _s;
braced!(_s in input);
let stream = _s.parse::<TokenStream>()?;

let c = match stream.span().source_text() {
    Some(stx) => stx,
    // TODO: rust-analyzer does fall into this even if all is fine
    None => "".to_string(), //return Err(syn::Error::new(stream.span(), "Source code expected")),
};

So i've just decided to treat None-ish tokenstream's source_text as empty sourcecode.
I'm completely unsure if that's the proper way to extract source code from the ParseBuffer.
I'm aware of the fact that we could just do the input.to_string() within the proc-macro itself, however that's not the case for sabry, as we do the scoping before CSS compilation and parsing the string again and again is a bad idea.
What to do next
It's very annoying not to have autocompletion for selectors, because the selector identifier in rusty scope doesn't always match the selector identifier in style code.
So I need to investigate -- why does it even happen with rust-analyzer, and why does it work as expected with rustc.

I'm pretty happy with this commit.
Now we have to write styles in-quotes though:
styly!(scope:sass {"
    .sel
        color: red
"});

We don't benefit from unquoted style code anyway, because syntax highlighting is messy - sass isn't rust.
This way, The sass-tabbed-syntax indentation problem is also partially resolved.
And I get an opportunity to implement rust identifier injection, by reserving unqouted sass syntax for the future.


Unknown source when downloading images from gelbooru user favorites

Bug description
Source is not found for images from gelbooru user favorites.
Steps to reproduce

Select "gelbooru" in "sources."
Search for a user's favorites (e.g. fav:727453).
Click on any image.
The new window says "Image not Found," and in the details tab, the source is simply "Unknown."

Expected behavior
The source should exist; additionally, the image's resolution is very low when downloaded, since it just uses the thumbnail (as I understand it).
Context
This problem only occurs when searching favorites pages--I didn't find a problem searching keywords.
Screenshots

System information
main.log
settings.txt

OS: Windows 10
Grabber version: 7.3.2

Add any other context about the bug report here.

Seems to be ok in nightly, seems to be related to #2235.
Yeah this is the html modification that gelbooru did some times ago, the fix should be up in version 7.3.3 as it is working now fine on nightly.
Duplicate of #2235

I am having the same issue with gelbooru favorites even after switching to the latest nightly release, it only finds the image thumbnails. Works perfectly fine for any other tags.

I also just tried a fresh install of the nightly version and couldn't seem to get it to work.


run golangci-lint error, msg="Parallel golangci-lint is running"

/home/faneluo/QQMail/gobackend/server/mmocadbinlogreader/binlog
Error while running tool: /data/go/bin/golangci-lint run --print-issued-lines=false level=error msg="Parallel golangci-lint is running"
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 6.1.7601
Remote OS version: Linux x64 3.10.107-1-tlinux2_kvm_guest-0049

I just started hitting this issue with golangci-lint v1.21.0 on the command line. No extensions or any options specified, just running golangci-lint run. It doesn't even print a help message if I pass -h to it.


Fixed missing required fields check using schema sync

error description in #1258 can mostly be fixed using --schema-sync, as it uses field-based matching. However it has a bug,  Some required fields were not checked while validation if it is not set in the data. This PR fixes it.
Added tests for two different use cases:

Validating resources using field-based matching. Data and schema are not aligned. No type-error and incorrect-label  errors occur as in positional matching while values are missing. Example of data:

required fields: id, name
data: "smith"

Only enforce required fields for missing data.

fixes #1258

Please make sure that all the checks pass. Please add here any additional information regarding this pull request. It's highly recommended that you link this PR to an issue (please create one if it doesn't exist for this PR)

@roll it is ready for review.


Don't rebuild tree when navigating to path

Closes #93829
Technically fixes #99760, but I have a simpler fix in mind for that issue.

Thanks!


Formatter: breaks single-element pattern

A case with single-element tuple pattern (e.g. (x,)) is broken into multiple lines:
match a:
    case (x,):
        pass

is formatted to
match f:
    case (
        x,
    ):
        pass

Would have expected the formatter leaving it alone like it does for (x,) = y (and like Black does).
Invocation
ruff format test.py
Version
ruff 0.0.291

Thanks! I consider that a bug too, since it deviates from our if (x,): handling.


Create report on test failure

I'm using the plugin for JUnit output for Jenkins integration and I wanted to generate the report even if a failure occured. Now the reporter generate only on success.
Making this I can visualize better the failure results without going directly to the logs.

please reopen with additional information


Add mocking for unit tests to work with travis

@ldunphy1 @iamemilio FYI

@jbernal0019 I saw you committed the travis file.

Yes, I have. The testing is at https://travis-ci.org/FNNDSC/openshiftmgr. It's failing right now.
FileNotFoundError: [Errno 2] No such file or directory: '/home/travis/.kube/config'


Stretched image in customOverlay layout.

My screen consists of 1/3 scan area and the rest is other layouts (buttons, images etc) i use the customOverlay property.Then, I start scanning but the scanning area seems to be stretched (in portait view) and a little bit "laggy". How i can fix this?

I am with the same issue. I have many barcodes in a paper and some times the code had read is one above or one below, not the barcode at center of screen. I tried to read the sources and I found nothing like to limit the area of scanner.

I have the exact same problem. I tries to play and tweak the returned CameraResolution at the CameraResolutionSelector, but in same devices (like Samsung Galaxy S7 edge) this tweak generates a "SetupCamera failed" error that comes with a black screen. I think that if this is a bug it should be fixed with high priority because we can't publish any app with stretched QR code scanner. If all the above are not bugs please provide us a working solution

I have the same issue. Its strange that only few people notice that, I installed in new empty project that lib and camera image stretched anyway. Can someone help me?

10/10 can confirm ugly stretched hands..
Image with camera app (OP 3T)

screenshot using my own app. Code below

using Android.App;
using Android.Widget;
using Android.OS;
using ZXing.Mobile;
using System;
using Android.Views;

namespace App1
{
    [Activity(Label = "App1", MainLauncher = true, Icon = "@drawable/icon")]
    public class MainActivity : Activity
    {
        protected override void OnCreate(Bundle bundle)
        {
            base.OnCreate(bundle);

            // Set our view from the "main" layout resource
             SetContentView (Resource.Layout.Main);

            MobileBarcodeScanner.Initialize(Application);

            var btn = FindViewById<Button>(Resource.Id.button1);
            btn.Click += async (sender, e) => {

                var scanner = new ZXing.Mobile.MobileBarcodeScanner();

                scanner.UseCustomOverlay = true;
                scanner.CustomOverlay = LayoutInflater.FromContext(this).Inflate(Resource.Layout.Test, null);;

                var result = await scanner.Scan();

                if (result != null)
                    Console.WriteLine("Scanned Barcode: " + result.Text);
            };

        }
    }
}

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:p1="http://schemas.android.com/apk/res/android"
    p1:orientation="vertical"
    p1:minWidth="25px"
    p1:minHeight="25px"
    p1:layout_width="match_parent"
    p1:layout_height="100dp"
    p1:id="@+id/linearLayout1" />

I'm also experiencing this with the Xamarin Forms version on my Samsung Galaxy S4 (Android 6) and S8 (Android 7). It's notably worse in landscape mode.

Any progress on this? I'm experiencing the same issue

Same here :(. Any ideas to solve this problem ?

Is this still not solved?!

https://msicc.net/how-to-avoid-a-distorted-android-camera-preview-with-zxing-net-mobile/


Not all transactions visible in Wallet

I have a strange problem on the Verge wallet. I have made two transactions (to the same address) only one is showing up. Blockchain gives the correct information.
Is this a know bug in the wallet? Please let me know if you need any information from my side.

no this isn't a known bug. do you have your wallet locked? it sounds like you've locked the wallet.

Thanks for your update. No wallet is not locked. Buy why is only one transaction visable (100xvg) and not two? https://verge-blockchain.info/address/DPoSh9cYxFaXVAYugZuSMCMdbTeSb5kXSG

Did you figure this out?

Yes I have find it! wallet.dat seems to be corrupted. I have deleted and import private keys using command line. After entering the command it takes forever (and your computer is taking off on the cpu load). But the most important I can access my balance againe.


Still Broken fonts

@Sterzz, @Snuffleupagus
Fonts are still broken:
https://github.com/mozilla/pdf.js/files/10083159/bug.pdf

Duplicate of #15738.

Please don't open yet another incomplete issue, since you've unfortunately not provided enough information to clearly explain the problem; please note e.g. https://github.com/mozilla/pdf.js/issues/15738#issuecomment-1326208230.


[Feature] Use RayService with existing RayCluster

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
When creating RayService, the new ray cluster will be created as specified in
rayClusterConfig:
  rayVersion: '2.7.0'
  ...

It would be great to be able to specify existing RayCluster.
Also it would be beneficial to have multiple RayService instances utilizing the same RayCluster.
Use case
This would lead to better separation of infrastructure(RayCluster) and apps(RayService).
And better resource utilization.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

This scene matches my needs, and I also want to make application as a k8s svc. it's there any roadmap.
@ericl @jianyuan @pcmoritz @tekumara

To achieve high availability for RayService, the RayCluster also needs to be configured correctly. For example, readiness/healthiness probes and an external Redis are required.


Add test for config cache defect related to system properties from included build

See #19184

@bot-gradle test and merge

OK, I've already triggered a build for you.


MAINT: Add missing imports in deprecated modules

See details at: https://github.com/scipy/scipy/issues/14360#issuecomment-980322121

Tracking the fixed modules:

[x] cluster
[x] constants
[x] fft
[x] fftpack
[x] integrate
[x] interpolate
[x] io (skipped io.byteordercodes since it should be io.matlab.byteordercodes(and that too is deprecated))
[x] linalg
[x] misc
[x] ndimage
[x] odr
[x] optimize
[x] signal
[x] sparse
[x] sparse.csgraph
[x] sparse.linalg
[x] spatial
[x] special
[x] stats

cc @rgommers

This all looks correct so far, thanks @Smit-create

On the current diff, I get the these results:
These files are not present in current API:
scipy.interpolate.interpnd_info
scipy.io.harwell_boeing.hb
scipy.signal.sigtools
scipy.sparse.generate_sparsetools
scipy.sparse.linalg.dsolve.linsolve
scipy.sparse.linalg.eigen.arpack
scipy.sparse.linalg.eigen.arpack.arpack
scipy.sparse.linalg.eigen.lobpcg
scipy.sparse.linalg.eigen.lobpcg.lobpcg
scipy.sparse.linalg.isolve.iterative
scipy.sparse.linalg.isolve.lgmres
scipy.sparse.linalg.isolve.lsmr
scipy.sparse.linalg.isolve.lsqr
scipy.sparse.linalg.isolve.minres
scipy.sparse.linalg.isolve.utils
----------------------------------
These files missed the imports:
File scipy.io:  ['byteordercodes']

File scipy.linalg.interpolative:  ['backend']

File scipy.signal:  ['sigtools']

File scipy.signal.fir_filter_design:  ['sigtools']

File scipy.sparse.linalg:  ['iterative', 'utils', 'linsolve', 'arpack']

File scipy.spatial.distance:  ['wminkowski']

About the missing files, scipy.sparse.*  and scipy.io.harwell_boeing.hb are due to entire directory rename changes. While scipy.interpolate.interpnd_info and scipy.signal.sigtools are private modules with all private functions.

>>> import scipy.interpolate.interpnd_info as sii
>>> dir(sii)
['Matrix', '__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__', '_estimate_gradients_2d_global', 'binomial', 'symbols']
>>> import scipy.signal.sigtools as sss
>>> dir(sss)
['__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__', '_convolve2d', '_correlateND', '_linear_filter', '_medfilt2d', '_order_filterND', '_remez']

About the missing imports in files:
(i) scipy.io:  ['byteordercodes']: It is because we have placed it as io.matlab.byteordercodes which is also deprecated.
(ii) scipy.linalg.interpolative:  ['backend']: It was as private import which was renamed to _backend.
(iii) scipy.signal:  ['sigtools'] and scipy.signal.fir_filter_design:  ['sigtools']: It is private module with all private functions. See above snippet
(iv) scipy.sparse.linalg:  ['iterative', 'utils', 'linsolve', 'arpack']: These came from isolve/dsolve/eigen submodules which were renamed and place under private submodules(ex: _eigen.arpack)
(v) scipy.spatial.distance:  ['wminkowski']: On master: https://github.com/scipy/scipy/blob/3f05efb9498e29f4e735aa7e0220139a8d8c8773/scipy/spatial/distance.pyi#L54-L55


fix "carousel and modal settings not respected"

I've tried to adjust the carousel interval but it remained the default from bootstrap.Carousel.Default.
setOptionsFromSettings() is using this.settings, but that has not yet been merged with options at that point.
Related to https://github.com/trvswgnr/bs5-lightbox/issues/46

Thank you!
May I ask for a release?
We went live in a project with that fix yesterday and it would be great if I could change the package that to a released version :)

@jonaseberle I updated the version and build yesterday, so the change is now live in version 1.8.3

I was confused because it has not shown up here https://github.com/trvswgnr/bs5-lightbox/tags yet. Maybe you forgot to push the tag?
On https://www.npmjs.com/package/bs5-lightbox it is fine. Thank you!


Added Source Tag in documentation

I have tried to add the feature which I mentioned in #30
Please review this pull request

Sir any updates

Hi @Lakshmikanth2001!
I'm sorry it's taken me so long to get back to you on this. I've been pretty preoccupied with crafting gifts for friends and family for the impending holiday season!
I took a look at the source, and I realized that you'd manually added links to the source code in GitHub in each of the functions. While this is very admirable work, I don't think it's very sustainable. With each new function, it will be necessary to not only remember to update the link, but also update all of the other links that may have been affected by the change in line numbers.
In short, I think that this will lead to ongoing headache for anyone involved.
I've done a little research, and found the standard Sphinx extension sphinx.ext.viewcode which is more along the lines of what I thought you'd originally intended in #30.
I'm declining this PR, and will add the extension in a small PR so that the updates should be brought in. Thank you again for pressing onward with this issue, it's a great improvement, and I appreciate your continued drive.

Thanks For this Feature
Actually, I have developed a python script that adds line numbers to each function doing it manually would take days
if name == "main":
function_url =  dict()
REMOTE_URL = "https://github.com/engineerjoe440/ElectricPy/blob/master/electricpy/"

#get only files electricpy directory
SOURCES = [file for file in os.listdir('electricpy') if os.path.isfile(os.path.join('electricpy', file))]

for source in SOURCES:
    with open(os.path.join(sys.path[0], f"electricpy\{source}"), "r") as code:
        # buid a regular expression for "def ()"

        code = code.readlines()

        blank_count = 0

        RE = re.compile(r'def (.*)\(')
        param_count = 0
        function_count = 0
        source_count = 0

        # iterate over the lines in the file
        for line_number, line in enumerate(code):
            # find all the functions
            function_name = RE.findall(line)

            try:
                if code[line_number+1].find("    Parameters") != -1:
                    line = add_source(list(function_url.values())[-1])
                    source_count += 3
                    continue
            except IndexError:
                pass

            if line.find("    Parameters") != -1:
                blank_count+=1
                param_count += 1

            # if there are any matches
            if function_name:

                # get the function name
                function_name = function_name[0]

                module = source.replace(".py", "")

                if correct_doc(function_name, module):

                    function_count+=1

                    function_url[function_name] = f"{REMOTE_URL}{source}#L{line_number+1+source_count}"

        logging.info(f"In {source} their are {function_count} functions with {param_count} parameters")
        logging.info(f"In {source} there are {blank_count} blank lines above parameters")


Support Windows

Blocked on https://github.com/astral-sh/uv/issues/1539

It looks like uv 0.1.6 contains a fix for windows paths.

I know, but note the CI is failing with https://github.com/astral-sh/uv/issues/1779... so we're not there yet...

I was able to run on Windows if install uv in test virtualenv.
It is suggestion for workaround, as installation of dependencies is much slower than venv create for big projects.


Add my duck

Description
Here my contribution to "The Duck Gallery".

Thank you for giving me an opportunity to contribute to your repo.
You must respect the following conditions

Your contribution must respect the code of conduct
It's your first PR to this repository
You have added your image of the duck downloaded from https://pimpmyduck.zenika.com
You have not changed the image of the duck
The image filename must be your GitHub username (ex: your-username.png)
You are using your own GitHub user and it's the same as the PR author
Into the contributors.js file, the message must be short and respect the code of conduct

If the PR doesn't respect those conditions, it will be closed

yeah i have fixed it now, check it now.
thank you

oh sorry, I removed the space now.


UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 18: ordinal not in range(128)

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: 2.7.5 and 3.6.8
pyodbc: 4.0.27
OS: Red Hat 4.8.5 - CentOS
DB: SQL Server.
driver: ODBC Driver 17 for SQL Server

Issue
I am receiving the following error:
UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 18: ordinal not in range(128)
I have tried:
cnxn.setencoding(str, 'utf-8')
cnxn.setencoding(unicode, 'utf-8')
# and
cnxn.setdecoding(pyodbc.SQL_CHAR, encoding='latin1', to=str)
cnxn.setencoding(str, encoding='latin1')
# also
cnxn.setdecoding(pyodbc.SQL_CHAR, encoding='utf-8')
cnxn.setdecoding(pyodbc.SQL_WCHAR, encoding='utf-8')
cnxn.setdecoding(pyodbc.SQL_WMETADATA, encoding='utf-8')
cnxn.setencoding(str, encoding='utf-8')
cnxn.setencoding(unicode, encoding='utf-8')

With no luck. Any advice on how to proceed?

I also just tried in Python 3. Same error. I'm going to try another driver version.

Tried using ODBC Driver 13 for SQL Server and ODBC Driver 17 for SQL Server both fail with the same error.

In Python 3 I have tried adding cnxn.setencoding('utf-8') to the connection factory.

I have also tried cnxn.setencoding(encoding='utf-8', ctype=pyodbc.{SQL_CHAR and SQL_WCHAR})

Do you have a repro script with the string that gives that error?

import pyodbc
server = 'xxxx'
database = 'xxx'
username = ''
password = r''
cnxn = pyodbc.connect('DRIVER={ODBC Driver 13 #or 17 for SQL Server};SERVER='+server+';DATABASE='+database+';UID='+username+';PWD='+ password)
cursor = cnxn.cursor()
for rows in cursor.execute('SELECT x, x, x FROM x.x.x').fetchall():
    for row in rows:
        print(row)

Pretty simple.

Resolved. The solution was in Python 3.
cnxn = pyodbc.connect()
cnxn.setencoding('utf-8')
cursor = cnxn.cursor()
for row in cursor.execute(xxx).fetchall():
    for column in row:
        col = column
        if isinstance(col, str):
            col = col.encode('utf-8')
        print(col)

what was the solution here ? I am also getting the same error...


Event callback if the plugin wasn't enabled, i.e IE browsers.

Do we have or can have a callback function when custom player is not added i.e in IE browsers?

Is this any use? https://github.com/Selz/plyr#checking-for-support

I know some browsers are not supported but the video should at least play with normal UI ... I ended up using this to make sure Youtube UI is there for video:
// Fallback if custom controls dont exist i.e IE
setTimeout(function () {
	if(!$('.plyr__controls').get(0)){

		$('.we-video iframe').each(function () {
			var src = $(this).attr('src');
			var src = src.split('?')[0];
			$(this).attr('src', src);
		});

		$('.we-video iframe').css({
			width: '100%',
			height: '100%'
		});
	}
}, 5000);