Add gulp targets, fix build for Windows on Arm.

This PR partially fixes #33620, #81854
This PR doesn't get us all the way there because of a problem with vscode-sqlite3. (Essentially, it doesn't build with right version of Visual Studio - 2017 or later is needed, the node-gyp config is slightly wrong and I don't have legal approval to fix it). Once that issue is fixed, you'll be able to do the following to build for Windows on Arm, assuming Node v12.13.1 and node-gyp 5.0.5:
set npm_config_arch=arm64
yarn install --force
yarn run gulp vscode-win32-arm64-archive

Make sure to set up an ARM64 cross-compilation terminal as documented in Electron's upstream instructions.
The result is a zip file which you can manually install and run on the device - seems to work well, built-in extensions like syntax highlighting, PowerShell prompt all seem to function, performance is good too.
PTAL and I'll try to fix any non-SQLite issues which come up. CC @deepak1556
Update: 2020-March-10: the revised SQlite3 module has been published.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: richard-townsend-arm sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@richard-townsend-arm  Don't forget to sign the CLA, that way it will get released :). I'm happy to help test this on my surface pro x.

OK, CLA is now signed. I meant to get another patchset out last week, but there've been a few last-minute issues before branching Chromium 80 / Electron 8 which have been consuming my attention. Hopefully get an update out in a few days time.

Change itself looks OK to me, but I think we need to validate the build once we ran it since these changes are all in build scripts. Unassigning myself from review.

OK. I'm unsure why the CI is failing to fetch all the deps (something to do with --frozen-lockfile?) There haven't been any changes to packages.json so I'm unsure why it's doing this...

Cool, looks like the CI has come back clean this time. Ready for review.

Hi guys, happy new year! Any review thoughts?

I'd love to see this merged in soon. I built from your branch last month and it has been running perfectly for me on my Surface Pro X @richard-townsend-arm .

Indeed do we have a date estimate for review @joaomoreno  / @deepak1556 ? It appears that @richard-townsend-arm has completed your changes.

I'm not authorized to merge this change atm.

It needs @joaomoreno to review it before you can merge.

So... any thoughts on getting this merged soon? Even if Microsoft does not plan to distribute it an official binary, it'd be useful for a lot of people (me included!)

So... any thoughts on getting this merged soon? Even if Microsoft does not plan to distribute it an official binary, it'd be useful for a lot of people (me included!)

Agreed. There's a lot of ARM64 Windows users that would greatly benefit from using this. I've even gone so much as compiling the .NET Core SDK and and ASP.NET Core Runtime for ARM64 and it works pretty nice with it (minus a few issues around launching the debugger). We're just looking to help out the community by having support on an architecture where the core build components are already supported on.

I noticed that in https://github.com/mapbox/node-sqlite3/pull/1242, the vscode-sqlite3 issue was fixed (but vscode needs to upgrade to that version).

CC'ing @bpasero (seems that you look after the sqlite3 dependency).

I think we can try to update to latest. If you make the PR, I can look into it. Note that we use a fork with some changes so they would have to go into our repo.

@bpasero: I think the npm.js package (https://www.npmjs.com/package/vscode-sqlite3) would need to be updated first, otherwise any CI attached would fail. If it is a fork, the relevant change could be incorporated safely by cherry-picking https://github.com/mapbox/node-sqlite3/pull/1242/commits/f2f3b7df1130e8129ab76ad9cf0904634ba7cf38, but it would still probably need at least a version bump.

@richard-townsend-arm oh nice, a cherry-pick would be good because that reduces the chances of breakage. I am happy to accept a PR there and publish a newer version.

OK, I'll need to check that this component is covered under our our existing legal approval to contribute to VsCode. Can you confirm that this is the place where the PR should be sent?

@richard-townsend-arm it should be https://github.com/microsoft/vscode-node-sqlite3

OK, so I don't have legal approval yet to contribute the backport. It's in progress (might take some time.)

Still having some issues with vscode-sqlite3: it looks like yarn install does not use the variables from the binary section of vscode-sqlite3's package.json, so you end up with an error like this:

gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info find Python using Python version 2.7.16 found at "C:\Python27\python.exe"
gyp info find VS using VS2017 (15.9.28307.812) found at:
gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community"
gyp info find VS run with --verbose for detailed information
gyp info spawn C:\Python27\python.exe
gyp info spawn args [
gyp info spawn args   'C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\rictow01\\vscode\\node_modules\\vscode-sqlite3\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\rictow01\\AppData\\Local\\node-gyp\\Cache\\7.1.11\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\rictow01\\AppData\\Local\\node-gyp\\Cache\\7.1.11',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\rictow01\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\7.1.11\\\\<(target_arch)\\\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=C:\\Users\\rictow01\\vscode\\node_modules\\vscode-sqlite3',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\Users\\rictow01\\vscode\\node_modules\\vscode-sqlite3\\build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp: Undefined variable module_path in binding.gyp while trying to load binding.gyp

Hopefully this is something that can be addressed by packing appropriately with node-pre-gyp.

OK, so the error turned out to be because the published package contains additional changes (including typescript definitions etc) from the source code that's in microsoft/vscode-node-sqlite3, so naively doing yarn link was not going to work. Hopefully open the pull request to backport the change tomorrow.

sqlite3 request opened: https://github.com/microsoft/vscode-node-sqlite3/pull/7 @bpasero

Thank you for continuing to put in work into this!!! :) Let me know if you have a way for me to buy you a coffee/beer.

Whilst testing the new sqlite3, it emerged that the previous way of building the remote extensions no longer works correctly, the latest update should fix it again.

Verified that the build works fine and was able to test on a local device. Thanks @richard-townsend-arm for all the work on this 👍

Published<EMAIL_ADDRESS>

Unsure as to why one of the checks has still not come back, but ready to review.

Would be great to have this merged. Is it just waiting for @joaomoreno to approve or were more changes requested? It looks like all the checks have passed at this point.

Would be great to have this merged. Is it just waiting for @joaomoreno to approve or were more changes requested? It looks like all the checks have passed at this point.

It's sad to think this is being blocked by internal politics at Microsoft.

Would be great to have this merged. Is it just waiting for @joaomoreno to approve or were more changes requested? It looks like all the checks have passed at this point.

It's sad to think this is being blocked by internal politics at Microsoft.

Internal politics? The PR is appropriately licensed, and if it works all that is left is to hit the merge button. It's not even that large of a code change. I'd be happy to click the merge button for someone else if they don't feel they can.

I hope @joaomoreno is alright 😕, hopefully they're just on vacation and not hit with the virus.

hello @joaomoreno !  It appears that you're back. Hopefully all is well. I understand that times have been rough for all and please take the time you need to recenter and breathe. Nobody is as productive as they would like during a pandemic.
If you find that you have the time it would mean a lot to us if you could merge even with an early access or alpha label that way people can use and install it but you don't have as much pressure to work tickets to resolve them, merely merging fixes as you can. Hopefully that could be a decent middle path that allows people to have an option. I personally have not been using my surface pro x as much as I would like in part because it has no native vscode. I really had expected Microsoft to have a unified approach but it appears they have left your team behind in resources. Sorry to hear about that, as I think Code is one of Microsoft's best products.

@voronoipotato, and everyone else: merging this PR does not mean, by all means, that we will start releasing VS Code for ARM. That is a whole different undertaking and requires proper planning and time allocation for our PM team, who is very much aware of the demand for VS Code on ARM for Windows.
This PR will simply enable you to build the Code OSS build for Windows ARM. You can already do that today, you don't need to wait for me:

Clone this repo
Checkout this PR
Build

I will look into merging the PR in April.

@voronoipotato, and everyone else: merging this PR does not mean, by all means, that we will start releasing VS Code for ARM. That is a whole different undertaking and requires proper planning and time and resource allocation for our PM team, who is very much aware of the demand for VS Code on ARM for Windows.
This PR will simply enable you to build the Code OSS build for Windows ARM. You can already do that today, you don't need to wait for me:

Clone this repo
Checkout this PR
Build

I will look into merging the PR in April.

Nevertheless, we appreciate you looking into this. It'll make it easier for those who wish to create automated Code OSS builds for WoA. After what I've tried to do personally with building some of the components for ARM64, I definitely understand the amount of roadblocks involved with enabling this to be a fully supported VS Code build. After .NET 5 is released, I know a few of those roadblocks will be fixed.
If testers, or ANY help is desired - the team definitely has a group of people they can call upon.
I ask that each of us awaiting this, continue to be patient and contribute any way we can.

May I ask, how is anybody testing this? With what hardware?

I've tested this compiling it from my ASUS NovaGo and most recently my Surface Pro X using the instructions above. I was able to compile a build from this PR while even merging master into it.
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: João Moreno<EMAIL_ADDRESS>Sent: Wednesday, April 8, 2020 8:01:19 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Jeremy Sinclair<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Add gulp targets, fix build for Windows on Arm. (#85326)
May I ask, how is anybody testing this? With what hardware?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode%2Fpull%2F85326%23issuecomment-610917179&data=02|01||be342319d2e34384e9b508d7dbb48cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637219440805126929&sdata=8J34yN2lUCK6PKWFOzqx9HrbyRH7dX9ULj128mD8ZTY%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA6URJPNA7XG4HZLKFYMDOTRLRRQ7ANCNFSM4JQGXUWQ&data=02|01||be342319d2e34384e9b508d7dbb48cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637219440805136926&sdata=aEGuSLMtTvUyg0kaLY47YFvRZb6NOAZ6jLcKsRNEINI%3D&reserved=0.

Surface Pro X here.
-------- Original message --------
From: Jeremy Sinclair<EMAIL_ADDRESS>Date: 8/4/20 10:05 pm (GMT+10:00)
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Hon Weng Chong<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Add gulp targets, fix build for Windows on Arm. (#85326)
I've tested this compiling it from my ASUS NovaGo and most recently my Surface Pro X using the instructions above. I was able to compile a build from this PR while even merging master into it.
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: João Moreno<EMAIL_ADDRESS>Sent: Wednesday, April 8, 2020 8:01:19 AM
To: microsoft/vscode<EMAIL_ADDRESS>Cc: Jeremy Sinclair<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/vscode] Add gulp targets, fix build for Windows on Arm. (#85326)
May I ask, how is anybody testing this? With what hardware?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode%2Fpull%2F85326%23issuecomment-610917179&data=02|01||be342319d2e34384e9b508d7dbb48cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637219440805126929&sdata=8J34yN2lUCK6PKWFOzqx9HrbyRH7dX9ULj128mD8ZTY%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA6URJPNA7XG4HZLKFYMDOTRLRRQ7ANCNFSM4JQGXUWQ&data=02|01||be342319d2e34384e9b508d7dbb48cee|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637219440805136926&sdata=aEGuSLMtTvUyg0kaLY47YFvRZb6NOAZ6jLcKsRNEINI%3D&reserved=0.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/pull/85326#issuecomment-610919062, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAC734VEOOTYUVMSAICUWVDRLRSB3ANCNFSM4JQGXUWQ.

Maybe Microsoft should send Surface Pro X's to the entire development team of VS code!

Got it. Let's see if I can get my hands on one of those.

There are quite a few options available for ARM64 based devices. For doing dev work I'd certainly limit the options to those with 8GiB RAM or more. Surface ProX is an obvious choice, especially to MS employees who can get them internally. But the Yoga C630 is an inexpensive candidate, being featured for sale in many stores, being previous generation.
Qualcomm 8cx based:

Surface ProX
Samsung Galaxy Book S

Qualcomm 850 based:

Samsung Galaxy Book 2
Lenovo Yoga C630 Snapdragon

Qualcomm 835 based:

Asus NovaGo
HP Envy x2 Snapdragon
Lenovo Miix 630

https://github.com/wixtoolset/issues/issues/5558
Looks like wix is ready to go for this too!

wixtoolset/issues#5558
Looks like wix is ready to go for this too!

Yup. Hopefully the 3.14 release comes soon. I was able to pull THIS off using the latest WiX dev release (with a bunch of horrible changes that I could never commit lol)
https://twitter.com/sinclairinat0r/status/1241059487139717121

This is now merged, so you should be able to compile VS Code for ARM.
There's a Surface Pro X on the way, so we'll be able to test this soon and evaluate having an official VS Code version.

Thank you so much Joao!!! This means so much to me, I really appreciate it. I think once you realize just how amazing it is to not worry about outlets on the go or lugging around a heavy machine you will also come to love the Surface Pro x, and now the battery footprint of VSCode is going to be so tiny! It really is night and day. Truly the killer app for the killer laptop.

Thank you very much for merging this and for working to implement full support for WOA! I've managed to transition almost all my development work to the Surface Pro X with the exception of remote WSL and C/CPP, and so I still keep the x86 binary around for that. Otherwise it works perfectly for most of the other interpreted languages 😊


LaplaceMulti() execution failed

Hello,
I'm trying to run the mainSift.cpp program on a Tesla M2090. First of all I had to change all of sim_35 occurences into sim_20 in CMakeLists.txt. After that, this message is returned during the execution of LaplaceMulti():
checkMsg() CUDA error: LaplaceMulti() execution failed
 in file </ghome/rzhengac/Downloads/CudaSift-Maxwell/cudaSiftH.cu>, line 324 : unknown error.

Why this happens?

Quite a lot has changed since compute capability 2.0, but I cannot see why if should fail in LaplaceMulti(). The latest version was adapted for Maxwell though and that is a later generation.


[type:feat]add rocketmq logging e2e test

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.90%. Comparing base (5d9fb45) to head (0977721).
Report is 8 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5439      +/-   ##
============================================
+ Coverage     60.85%   60.90%   +0.04%
- Complexity     8626     8653      +27
============================================
  Files          1263     1263
  Lines         38543    38575      +32
  Branches       3679     3682       +3
============================================
+ Hits          23456    23493      +37
+ Misses        12971    12961      -10
- Partials       2116     2121       +5

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


Upload nightly wheels to Scientific Python nightly channel

See https://github.com/scientific-python/upload-nightly-action/issues/63

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 88.076%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
2600

Relevant Lines:
2952

💛  - Coveralls

We are only going to see if this worked or not on main, so going to merge this to verify (happy to do any follow-ups!)


Have other marker instead of checkmark

A really great control. Thanks !
Something that could be improved:
A checkmark always implies that something is "OK".
If you have to answer "Is there something wrong ?" the checked box looks as if everything is fine.
I´d sugest to have a property e.g. "markerType" with an option to set it to e.g. "BEMMarkerTypeCheckmark" (default), "BEMMarkerTypeDiagonalCross" etc... with a corresponding symbol.
Optimum solution would be to have this customizable for selected and unselected state so the box would not be empty when deselected.
Any chance this gets implemented by a friendly soul ? ;-)

Hi @Oggerschummer,
This is a very good idea. One thing to keep in mind, is that all of the "markerTypes" need to support all of the animations.


Avast detects parser.php as an IDP.ALEXA.51 virus (on Windows)

The atom-autocomplete-php plugin version is 0.25.6
Avast version is 17.5.2303
Would be glad to help if anyone has an idea how to validate a false positive.
Thanks.

Hello,
I found you because i have the same issue on my router.php ? did you resolved it ? i hope so ^^
(sorry for my english i'm french)

Hello,
I found you because i have the same issue on my router.php ? did you resolved it ? i hope so ^^
(sorry for my english i'm french)

Hello,
Same issue here using Symfony 4.4.
router.php is blocked when starting the built-in server : php bin/console server:run

Hello,
I found you because i have the same issue on my router.php ? did you resolved it ? i hope so ^^
(sorry for my english i'm french)

Hello,
Same issue here using Symfony 4.4.
router.php is blocked when starting the built-in server : php bin/console server:run

Did you find a solution ?

Hello,
I have same issue on Symfony 4.4 with Windows 10 / Avast 20.1.2397 ?
@glen-rhodes @EmilieGithub @jubecl
Did you find a solution ?
Thank's


"Options" page to set scihub URL

Please redirect to my fork - I am willing to maintain it for the remainder of my PhD (~early 2024???).
Allows for end-users to update the scihub TLD url through the "options" page.
Extremely minimalist options page accessed by right clicking bird icon > "Options"

Instructions for manually installing this extension (copy-pasted from #6 )

It seems @0x01h is no longer maintaining this project.  Here are instructions to update the extension to this version.  It's very easy; I was hoping @0x01h would have stepped in but I guess that won't happen.
Download @lsterzinger 's version

On this page, click "Commits" right above my original comment, next to "Conversation" and "Checks"
On the right hand side of the page, click the little <> icon which has the mouseover text "browse the repository at this point in history"
Click the green "Code" dropdown towards the upper right of the screen and select "Download Zip"
Unzip the folder once it's done downloading.  I recommend placing this folder somewhere permanent (not in Downloads folder), because if it gets deleted, Chrome will not be able to find it anymore.

Install into Chrome

go to chrome://extensions
on the top right of the screen, toggle "Developer Mode" to ON.  You should now see "Load Unpacked" "Pack Extension" "Update" on the top left of the screen.
(optional) Remove the old Sci-Hub Now extension, so that you don't get confused which version is which (because this will install a new version but not replace the old one)
Click "Load Unpacked".  Select the unzipped folder.

That should be it and it should be working now with the new version (0.0.3).

Thanks bro, this is invalueable for my PhD (~2021) and my wife's PhD (~2023). I can't thank you enough!

Thanks @rwat1 - and thanks for letting me know.  I updated it on my fork's master branch.

Hi, Do you know how to implement it Firefox?
I have followed all the steps but it seems like in Firefox the manual installation works different,
Thanks in advance

Please refer to my fork
It's published to the official firefox store here
Alternatively, for a manual installation you can also click this link and it should install
Thanks! :)

Cool it worked for me directly by clicking the link!

Thanks a lot man you are a lifesaver 👍


Bump BT to version 2.5.0

Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Also

Add any other relevant change made on this PR.

Notes

Describe your changes

Tests Added / Updated?

YES or NO. If not, why?

Screenshots

Current dependencies on/for this PR:

main

PR #83   👈

This comment was auto-generated by Graphite.


Hi, is there any plans for support windows?

Describe the feature
Motivation
A clear and concise description of the motivation of the feature.
Ex1. It is inconvenient when [....].
Ex2. There is a recent paper [....], which is very helpful for [....].
Related resources
If there is an official code release or third-party implementations, please also provide the information here, which would be very helpful.
Additional context
Add any other context or screenshots about the feature request here.
If you would like to implement the feature and create a PR, please leave a comment here and that would be much appreciated.

We have no official plan to test it on windows since we do not have any windows servers, but community support is available and it should work well now.

@hellock I had followed the pull request of @wswday for building this repo on Windows but seems there's a bug.

#1088


Don’t overwrite layer checksum on push

After v1.8.3 layer checksum is used for image ID
validation. Rewriting the checksums on push would
mean that next pulls will get different image IDs if
compression returns a different blobsum
and pulls may fail if its detected that same
manifest digest can now point to new image ID.
Fixes #17178
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>cc @aaronlehmann

I think overwriting the checksum on push is the right thing to do, because we want the checksum file to reflect the latest checksum.
Maybe it would be better to relax the restriction that a manifest digest's mapping to an image ID can never be changed once it's set?

want the checksum file to reflect the latest checksum

That is true but then we would have to change the image ID that matches the checksum on disk as well and we don't have a good way to do that atm. The new checksum is not valid for the ID that is already on disk.

Maybe it would be better to relax the restriction that a manifest digest's mapping to an image ID can never be changed once it's set?

This isn't only about digest collision - you would still need to download the image again and get new IDs. I think its makes more sense to keep the checksums that we have validated instead of the generated ones.

My concern is that if we don't update the checksums when we push, docker push $repo && docker pull $repo will re-download layers and change the image ID. I think people will experience this frequently and it will cause major complaints.

@aaronlehmann 1) this will not happen on the images that user has built 2) it makes sure that if compression conflicts happen, you will not get IDs from another image but get the same IDs that the new users get for a fresh pull.
Storing multiple blobsums for image is not very hard. That would fix the digest conflict and pull after push. The images pulled the second time would still keep and ID that doesn't match the checksum.

I vote against storing multiple blobsums for an image. Based on a quick look at the code, storing multiple checksums in one file will break "push" if someone downgrades the client. And I really don't want to introduce a new file for this workaround, since all of this is being redone in 1.10 anyway.
As you say, rewriting the blobsum on push makes it inconsistent with the computed image ID, which causes a redownload anyway.
I think this PR is the least bad option until 1.10.
LGTM

Would be great to have a test case for this

@aaronlehmann When you say "downgrades a client", are you referring to engine here? If so, there hasn't ever been a guarantee that this will ever work.

So from what I understand:

Local digest either doesn't exist or is different on push
If not exist set the digest -> ok
Digest is different but exists -> pull will yield a new image

Why would the on-push digest be different from what's on disk?

The on-push digest may end up different because we don't store tar.gz files. The tar we produce may be different if the original one didn't use tarsplit, and the compression is not especially reproducable.

On Oct 20, 2015, at 11:59, Brian Goff<EMAIL_ADDRESS>wrote:
So from what I understand:
Local digest either doesn't exist or is different on push
If not exist set the digest -> ok
Digest is different but exists -> pull will yield a new image
Why would the on-push digest be different from what's on disk?
—
Reply to this email directly or view it on GitHub.

are you in consensus about the design can we move to code review

@aaronlehmann When you say "downgrades a client", are you referring to engine here? If so, there hasn't ever been a guarantee that this will ever work.

Yes, I was referring to engine.

are you in consensus about the design can we move to code review

Tonis and I agree about the proposed design. @cpuguy83, what do you think?

@tiborvass Testcase is a bit tricky because it needs 2 registries and pull by digest(if we don't go though trust). We also just can't use hub as one of the registries because we can't hardcode a digest from there. So this is possible with a new suite and some workarounds, but currently I don't even see a testcase for plain pull-by-digest.

I think it's ok.

LGTM


New top-level API SystemPackages

What this PR does / why we need it:
Provides more control over what's happen on machine in strict environments
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #654
new systemPackages configuration block

@xmudrii in follow-up PR I'm planning also to add systemPackages.configureProxy.

/retest

/lgtm


Failed to change reliability tier through azure portal but succeeded via Powershell

i have a cluster with 3 VMs and reliability tier, then i scaled up to 5 VMs and try to upgrade the tier to Silver.

However,  it returned  "Failed to save node type 'xxxx' for cluster 'yyy'. Error: There was an error processing your request. Try again in a few moments."  without detail information.
I waited for 4-5 hours, tried more than 10 times, still the same issue.
Then i turned to Powershell script, update-AzureRmServiceFabricReliability -ResourceGroupName 'xxxsfgroup' -Name 'yyy' -ReliabilityLevel Silver.
it works like charm.

I have this same issue - I have been running in Bronze with 3 VMs, and scaled up the VMSS to 5, ensuring all 5 nodes report healthy (including the SF extension).
When I go to change the durability tier to Silver, I get the same error:

Fabric Version: 7.1.456.9590


fix: les etab fermes ne sont plus listes-108

:tada: This PR is included in version 0.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


push ids are not stream ids

The stream id type is used to represent and validate push ids. On GOAWAY frames from the client, StreamId::is_push() is used to validate the push id. Based on my understanding of the RFC I believe this is incorrect (they are not related) and it leads to errors on client initiated shutdowns:
h3::Error { code: H3_ID_ERROR, reason: "non-push StreamId in a GoAway frame: client bidirectional stream 0" }

I can send a PR with the following changes:

add a PushId type
Either:

differentiate Frame::ServerGoaway(StreamId) and Frame::ClientGoaway(PushId)
introduce GoawayId with stream and push variants for Frame::Goaway(GoawayId)
use Frame::Goaway(u64) and convert to respective type as soon as possible after unpacking

Thanks for submitting this issue.
You are right. This does not look correct.
In my opinion your second suggestion with the GoawayId is the best.
Since server push is not fully implemented yet the server can not push. So the only valid push id for now is 0 right?

Since server push is not fully implemented yet the server can not push. So the only valid push id for now is 0 right?

Not quite. GOAWAY frames sent by the remote party have no upper bound on the push id they specify afaik. Specifying a larger one won't be meaningful in the absence of server pushes , but is valid.
I'll have a look at this and try to  send a PR asap.


Importing with unsaved Sketch file in background

When trying to import a saved, active file while having an unsaved document in the background, Sketch and Framer both throw errors and the import fails.

Not necessarily a big issue. But it should be possible to import a valid, saved and active document regardless of what documents you have opened in the background.

Can't reproduce here, is this still an issue, @benjaminnathan and @koenbok?

Yes this is actually a Sketch issue. Repro:

Make new document
Open existing document
Focus on new document
Minimize new document
Import in Framer

You now get a bunch of warnings. Apparently Sketch still thinks the minimized document is the frontmost one.

I think that's actually a new issue in Sketch (context.document points to the wrong thing under some circumstances, like following the steps you outlined) and is technically not related to save state. Anyway, we're about to fix it so those steps are really handy to reproduce the issue : )

This is fixed in Sketch 3.4.2 15853 (a beta is coming out shortly). I'll leave this open until you can confirm the fix : )

Ping @benjaminnathan and @koenbok: did you have a chance to try the latest Sketch beta? I'd love to confirm this issue has been fixed for good : )

I think I just saw this again :-/

Basically Sketch still seems confused if:

It's in the background OR
Some docs are minimized

: (


About the data you provide!

Your json file provides thetas, betas, smpl_joints, h36m_joints.
I calculated the smpl joints by thetas, betas and J_regressor(basicModel_neutral_lbs_10_207_0_v1.0.0.pkl), it is the same as the smpl_joints you provided.
smpl joints - smpl joints root coordinate (I calculated) = smpl_joints - smpl_joints root coordinate (You provide)
But, I calculated the h36m joints by thetas, betas and J_regressor_h36m(from J_regressor_h36m_correct.npy), it is different from the h36m_joints you provided.
h36m_joints - h36m_joints root coordinate (I calculated) ≠ h36m_joints - h36m_joints root coordinate (You provide)
Why?

Hi, it seems the J_regressor you used (J_regressor_h36m_correct.npy) is different from the one I used. I think it would cause some difference.


retrofit tests so that they work on Windows

added appveyor configuration (a Windows CI server).
hiredis is now installed as an optional dev dependency (since Windows machines have trouble building it with node-gyp).
auth-spec is now skipped if we fail to spawn a Redis (in our Windows CI we assume a Redis is provisioned by the CI environment, not that we can spawn it using a redis bin).
Windows tests run on an older Redis, I fixed up some of the tests that were conditional based on which Redis version was being used.
found a single test that behaves weirdly on Windows, and added a  TODO (relates to an error being returned even though the operation should simply be enqueued).

@blainsmith @BridgeAR any objections to landing this, it gets us up and running with Windows CI.

@bcoe do you have any idea why coveralls does not run?

I think this is ready to go out the door -- my only concern is the slight drop in test-coverage, but I think this is a rounding issue due to shuffling code around a bit, should come out in the wash when we land some of @BridgeAR's pulls that increase coverage.

This looks good on my end. I think we are safe and let the coverage come back up with the pending PRs.


[FR] Implement Support for WebSocket (R5)

Describe the issue
FHIR R5 (4.6) changed the behavior on how to subscribe to Websockets to listen to subscriptions.
As defined in http://build.fhir.org/subscription.html#websockets it is now a "2 Step" Process to receive messages.
While the first part - connecting to the general socket endpoint - seems to work, HAPI does not support to generate the subscription token by calling the $get-ws-binding-token operation.
Environment (please complete the following information):

HAPI FHIR Version: 5.5-PRE-7
OS: Ubuntu 20.04 / Docker
Browser: NA (Tested with Postman)

Additional context
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
Invalid request: The FHIR endpoint on this server does not know how to handle GET operation[Subscription/40364ab3-b9fe-40e6-bc7e-da856b3f833f/$get-ws-binding-token] with parameters [[]]
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "not-supported",
            "diagnostics": "Invalid request: The FHIR endpoint on this server does not know how to handle GET operation[Subscription/40364ab3-b9fe-40e6-bc7e-da856b3f833f/$get-ws-binding-token] with parameters [[]]"
        }
    ]
}

@tadgh As support for R5 is being released with the upcoming 6.6 can we expect the websockets to work or should I keep this ticket opened?

Heya, I would recommend just checking our and building rel_6_6 branch and finding out.
Sadly I personally have not been involved with the upgrade to R5 or with the websockets implementation. I would hazard that this has not been done yet with the conversion. @jamesagnew did this bump so he may know more, but I think this would be a separate change to our subscription processor. Likely this ticket is still valid.

Since we now support R5 though, this will likely be prioritized pretty quickly.

@tadgh is there any update on it?
Glad to close the ticket if it has been already implemented, however I didnt find anything in the changelog.


matplotlib throwing notebook inline error

I'm submitting a ...

[x] bug report
[ ] feature request

How do we replicate the issue?
By importing binary_visualize before matplotlib

import matplotlib.pyplot as plt
from fromscratchtoml.toolbox import binary_visualize
%matplotlib inline

Stacktrace (if any)

/home/mark/.local/lib/python2.7/site-packages/fromscratchtoml-0.0.2-py2.7.egg/fromscratchtoml/toolbox/__init__.py:11: UserWarning:
This call to matplotlib.use() has no effect because the backend has already
been chosen; matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
or matplotlib.backends is imported for the first time.

The backend was *originally* set to 'module://ipykernel.pylab.backend_inline' by the following code:
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/lib/python2.7/dist-packages/ipykernel_launcher.py", line 16, in <module>
    app.launch_new_instance()
  File "/usr/local/lib/python2.7/dist-packages/traitlets/config/application.py", line 658, in launch_instance
    app.start()
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/kernelapp.py", line 477, in start
    ioloop.IOLoop.instance().start()
  File "/usr/local/lib/python2.7/dist-packages/zmq/eventloop/ioloop.py", line 177, in start
    super(ZMQIOLoop, self).start()
  File "/usr/local/lib/python2.7/dist-packages/tornado/ioloop.py", line 888, in start
    handler_func(fd_obj, events)
  File "/usr/local/lib/python2.7/dist-packages/tornado/stack_context.py", line 277, in null_wrapper
    return fn(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/zmq/eventloop/zmqstream.py", line 440, in _handle_events
    self._handle_recv()
  File "/usr/local/lib/python2.7/dist-packages/zmq/eventloop/zmqstream.py", line 472, in _handle_recv
    self._run_callback(callback, msg)
  File "/usr/local/lib/python2.7/dist-packages/zmq/eventloop/zmqstream.py", line 414, in _run_callback
    callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/stack_context.py", line 277, in null_wrapper
    return fn(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/kernelbase.py", line 283, in dispatcher
    return self.dispatch_shell(stream, msg)
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/kernelbase.py", line 235, in dispatch_shell
    handler(stream, idents, msg)
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/kernelbase.py", line 399, in execute_request
    user_expressions, allow_stdin)
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/ipkernel.py", line 196, in do_execute
    res = shell.run_cell(code, store_history=store_history, silent=silent)
  File "/usr/local/lib/python2.7/dist-packages/ipykernel/zmqshell.py", line 533, in run_cell
    return super(ZMQInteractiveShell, self).run_cell(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2718, in run_cell
    interactivity=interactivity, compiler=compiler, result=result)
  File "/usr/local/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2822, in run_ast_nodes
    if self.run_code(code, result):
  File "/usr/local/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2882, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-1-0f9831bce6aa>", line 6, in <module>
    import matplotlib.pyplot as plt
  File "/usr/local/lib/python2.7/dist-packages/matplotlib-2.2.2-py2.7-linux-x86_64.egg/matplotlib/pyplot.py", line 71, in <module>
    from matplotlib.backends import pylab_setup
  File "/usr/local/lib/python2.7/dist-packages/matplotlib-2.2.2-py2.7-linux-x86_64.egg/matplotlib/backends/__init__.py", line 16, in <module>
    line for line in traceback.format_stack()

  matplotlib.use('agg')

Expected behavior (i.e. solution)
Anything but this.

I suggest using filterwarnings to remove the warning for now. But I believe the warning has something to do with conflicting backends for matplotlib.

filterwarnings suppresses the warning. Indeed it is a conflict with the backends. We need a workaround.


flake8 precommit from github

Fix #1206

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Updated to Swift 5 and DidScroll delegate added

Updated to Swift 5 and DidScroll delegate added

I have added one delegate from scrollView. Please accept the change

@bannzai Can you please check this merge request?


How to switch DEBUG = True/False on the fly in prod?

When prod breaks, how do I enable Django to temporarily show debugging data to help me troubleshoot when prod breaks?
I tried switching the DEBUG config environment variable in the Heroku Admin Dashboard from “False” to “True” (which had no effect).

This is just my guess, the application seem to be overriding the environment variable DEBUG in the settings file here. You could,

Test it out by printing the value of DEBUG config inside your running application.
Set DJANGO_DEBUG to True and verify it the INFO logs start appearing.

Hey @enoren5 brother

You can switch the DEBUG  on the fly using DJANGO_DEBUG config variable (as we have implemented a configuration as you know). Check Below screenshot from settings.py

@UmarGit: Yes, this is the DEBUG switch. But to make toggle it on/off, I need to manually make the change in settings.py, commit to master, and push to staging/prod. That is cumbersome to handle. Instead my initial question was how to keep DEBUG settings as they are, but be able to turn debugging on/off in prod without hard coding changes in settings.py.
alienware proposes one such solution by first checking the DEBUG config in prod (like with heroku-cli) with something like $ echo $DJANGO_DEBUG or $ echo $DEBUG and then using export to make the change. I haven't tested this yet, but I will at my next opportunity (which will be later this week).

@UmarGit: Yes, this is the DEBUG switch. But to make toggle it on/off, I need to manually make the change in settings.py, commit to master, and push to staging/prod. That is cumbersome to handle. Instead my initial question was how to keep DEBUG settings as they are, but be able to turn debugging on/off in prod without hard coding changes in settings.py.
alienware proposes one such solution by first checking the DEBUG config in prod (like with heroku-cli) with something like $ echo $DJANGO_DEBUG or $ echo $DEBUG and then using $ export DEBUG = True to make the change. I haven't tested this yet, but I will at my next opportunity (which will be later this week).

Yes @enoren5 brother, need to try your method

Then we will implement a switch to toggle it on the fly, If your hypothesis is true

The official Django docs specifically say to: "Never deploy a site into production with DEBUG turned on." (Citation). So that is the final word. Issue Closed.


Bug in ast/index_access.go

Context
Found a bug while trying to print an index access node in the AST.
source code: myArray[idx]
Expected: myArray[idx]
Actual: idx[myArray]
Problem
I think that the (i *IndexAccess) Parse method has a bug where the index and type expressions are swapped.
Currently:

i.IndexExpression -> ctx.Expression(0)
i.TypeExpression -> ctx.Expression(1)

Should be:

i.IndexExpression -> ctx.Expression(1)
i.TypeExpression -> ctx.Expression(0)

On a side note, I can't seem to label the issue due to lack of permissions 🫡

Wow missed this one out. Thank you! Going to fix it tomorrow

Alright @xianlinc it's resolved! Merging in soon the fix into the main. Thanks again for finding this out!


CAMEL-10397 SJMS - Raise an error against InOut+transacted producer a…

…s it causes a deadlock

Hold on one sec, I'd like to move that check from SjmsEndpoint.createProducer() to InOutProducer.doStart()

OK done.

@igarashitm Thanks for the contribution!
The PR has been merged. Can you close this?

Thanks! closing


[Open File] An editor opened by top menu cannot get a focus.

Select one of files.
Select File > Open File
--------> Selected file is opened.
---------> Problem : The opened file has no focus on it. Therefore, sub-menus of 'Edit' are disabled.

@JUHYUNCHOI : I solved this. thanks.


Certificate errors when connecting from mumble desktop

Hi all, sorry if this isn't the proper place to ask this but I'm having issues. I installed the container through docker compose and got nginx properly configured for it, and it passes certification in a web browser. AM I doing something wrong? I'm using the desktop version in the ubuntu repos if age of the package makes a difference

mumble use certificate for tls encryption, not for http packets.
The reverse nginx cannot forward UDP and TCP mumble protobuff packet. It's not web packet here.

How do I go about acquiring a cert for my server? do I do so from the shell within the docker container?

The server will automatically generate a certificate, if it doesn't have one yet

How do I go about acquiring a cert for my server? do I do so from the shell within the docker container?

The mumble documentation has instructions on how to set up letsencrypt...it's not a cakewalk but not insanely hard either.
Because we're in dockerland, I use SWAG (nginx and letsencrypt have a baby)...then mount the pem files from swag into the mumble container. The reason is if I use mumble.domain.com it's nice when the ssl cert matches and mumble clients don't get an error.  Otherwise, the default self-signed cert is just fine.

Hi,
I have the following problem. The docker mumble server is running and lokal network connections from mumble clients working as expected but our Firewall has deep ssl inspection enabled and every client who tried to connect from outside gets this error message:
Mar  2 10:52:38 mumble-srv 2023-03-02 09:52:38.447 SSL: OpenSSL version is 'OpenSSL 1.1.1f  31 Mar 2020'
Mar  2 10:52:38 mumble-srv 2023-03-02 09:52:38.448 Initializing settings from /data/mumble_server_config.ini (basepath /data)
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.105 MetaParams: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-SHA:AES128-SHA"
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.185 ServerDB: Opened SQLite database /data/mumble-server.sqlite
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.185 ServerDB: Using SQLite's default rollback journal.
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.188 MurmurIce: Endpoint "tcp -h <IP_ADDRESS> -p 6502 -t 60000" running
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.188 Murmur 1.4.287 running on Linux: Ubuntu 20.04.5 LTS [x64]: Booting servers
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.197 1 => Server listening on <IP_ADDRESS>:64738
Mar  2 10:52:39 mumble-srv 2023-03-02 09:52:39.829 1 => Not registering server as public
Mar  2 10:52:52 mumble-srv 2023-03-02 09:52:52.026 1 => <0:(-1)> New connection: xx.xxx.xx.xxx:65156
Mar  2 10:52:52 mumble-srv 2023-03-02 09:52:52.119 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0407E068:rsa routines:RSA_verify_PKCS1_PSS_mgf1:bad signature, error:1417B07B:SSL routines:tls_process_cert_verify:bad signature [13]
Mar  2 10:53:02 mumble-srv 2023-03-02 09:53:02.192 1 => <0:(-1)> New connection: xx.xxx.xx.xxx:65157
Mar  2 10:53:02 mumble-srv 2023-03-02 09:53:02.292 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0407E068:rsa routines:RSA_verify_PKCS1_PSS_mgf1:bad signature, error:1417B07B:SSL routines:tls_process_cert_verify:bad signature [13]
I tried to load our official wildcard certificate that fits to the docker host but mumble server cannot read it, no matter which format I try. I believe that mumble doesn't accept own certificates. who can help and what's the problem here ? Every settings that I change is done via enviroment settings like MUMBLE_CONFIG_sslCA= ......
Mar  2 10:58:02 mumble-srv Setting config "sslCA" to: '/media/docker/containers/mumble/data/star.test-cl.com.pem'
Mar  2 10:58:02 mumble-srv Setting config "sslCert" to: '/media/docker/containers/mumble/data/wildcard-bundle.test-cl.pem'
Mar  2 10:58:02 mumble-srv Setting config "logfile" to: '/var/log/docker/mumble-srv.log'
Mar  2 10:58:02 mumble-srv Setting config "certrequired" to: 'true'
Mar  2 10:58:02 mumble-srv Setting config "sslKey" to: '/media/docker/containers/mumble/data/wildcard.test-cl.com_2022.key'
Mar  2 10:58:02 mumble-srv ls: cannot access '/run/secrets': No such file or directory
Mar  2 10:58:02 mumble-srv Setting config "database" to: '/data/mumble-server.sqlite'
Mar  2 10:58:02 mumble-srv Setting config "ice" to: '"tcp -h <IP_ADDRESS> -p 6502"'
Mar  2 10:58:02 mumble-srv Setting config "port" to: '64738'
Mar  2 10:58:02 mumble-srv 2023-03-02 09:58:02.728 SSL: OpenSSL version is 'OpenSSL 1.1.1f  31 Mar 2020'
Mar  2 10:58:02 mumble-srv 2023-03-02 09:58:02.729 Initializing settings from /data/mumble_server_config.ini (basepath /data)
Mar  2 10:58:02 mumble-srv 2023-03-02 09:58:02.729 MetaParams: Failed to read /media/docker/containers/mumble/data/star.test-cl.com.pem
Mar  2 10:58:02 mumble-srv 2023-03-02 09:58:02.729 MetaParams: Failed to load SSL settings. See previous errors.
Regards,
Frank


Use cma plain client

Summary
Updating to new major version of CMA SDK and using the plain client. This causes a breaking change in case users consume the createManagementClient function.
@ruderngespra is there anything left in regards to documentation inside this repo?
Description

Motivation and Context

Todos

[x] Implemented feature
[ ] Feature with pending implementation

Screenshots (if appropriate):

@suevalov yes, I was surprised as well.


When clicking an emoji, it just pasted whatever's in the clipboard

On Kubuntu 14.04, installed both from source and from Debian package, both have the same effect. Choosing any emoji has the same effect as Ctrl+V, whatever was in the clipboard before is pasted to where the cursor is.

Pushed (hopefully) a fix just now, could you try the latest commit and see if it works?

Thanks for the quick response, unfortunately the problem still exists. Earlier, when I clicked an emoji, the text from the clipboard would appear immediately, now it seems there is a short delay. Also strangely when I try to add an emoji in a Firefox window, now nothing happens, while in any other program (GTK or QT) I get the clipboard content pasted. Earlier, Firefox functioned like any other program. See attached errors when starting the keyboard from the terminal. Lines 1-333 are printed at startup, lines 340 to 1003 are printed when I try to insert an emoji to a GTK application.
emoji-error.txt

Okay, this one is because emoji-keyboard requires python 3.5. Any chance you can get python 3.5 running and see if it solves the issues?

Did some testing and those should not be related to pasting emoji. In fact, everything except sorting of recent emoji should work on earlier versions of python.
Back to the pasting bug, added another timeout, can you try the latest commit?

Sorry, the problem persisted with the last commit with Python 3.4... I tried Python 3.5 briefly but there was some problem up the dependency tree (with gi), somehow pip didn't get a good version of it, so I was not able to test the emoji keyboard with it.

Hmm, I can't reproduce this at all. Anyway, made the timeouts ridiculous, could you try it again? If it doesn't work now I'm afraid I'm out of ideas.

It didn't solve the problem unfortunately. There is a ~3 second delay now between clicking an emoji and getting the clipboard's content pasted in the window. Maybe I'll give Python 3.5 another go later.

I tried Python 3.6; was not easy to figure out how to install the correct version of gi, but I did eventually. Unfortunately exactly the same as before 😞 there are no errors printed out at all.
Moreover, now the there seems to be some problem with the rendering, this is how it looks like on my screen:

Rendering's on gi and Gtk, I'm afraid there's nothing I can do about.
As for pasting, I'm downloading Kubuntu to see if it's something specific to your system or if it's just Gtk not playing nice with KDE.

Finally managed to reproduce this, not working on KDE at all. I'll try switching from Gtk to Xlib for clipboard access and see if that works.

Thanks :) Kubuntu 14.04 has some glitches with recent versions of Firefox seemingly due to the newer version of GTK, while Kubuntu 16.04 renders everything normally, maybe it's related to either the pasting bug or the bad rendering.

So finally got some testing done and I got bad news. Python-xlib doesn't play nice with KDE either, which leads me to believe there're some non-standard behaviors in KDE. One thing that immediately popped out was clipboard manager randomly taking over, but I guess there's more.
So in summary fixing this would require rewriting the app in qt and I have no desire or time to learn qt, sorry, marking this as won't fix.

I'm experiencing the same in i3 window manager. Can I suggest that you update the readme to indicate only GTK-based desktop environments are supported?

@sahmes , @billwanjohi Okay, I think I figured it out.  Note that at least under KDE you need python-xlib version 0.19 which is only available through pip, so update that as well. I also introduced a new bug somehow, where exiting through indicator menu doesn't work, but sending SIGTERM works properly. I'll have to figure this out later.

Yep, the clipboard problem is resolved on Kubuntu 14.04 using Python 3.6 and Xlib 0.19 🙂
The hideous SVG distortion is still there though 😞
I really couldn't figure out how to install a fresh gi; version 1.2 here (same thing I get via pip) is actually not compatible with python 3. When installing python3-gi via apt, it goes to the (default) Python 3.4 path in my system, I manually linked it into the dist-packages of 3.6 installation, it kinda works but may be the cause of the problem.
me@myserver:~$ python3.4 -c "import gi; print(gi.__version__)"
3.12.0

Where can I find the source for this "3.12" version? Maybe it's a completely different package?

@sahmes Good to hear it works!
As for the rendering glitches, I'm sorry, this is over my head. No idea where to even start with this.

@OzymandiasTheGreat rebuilding after your changes fixed my problems.


Fixing build on Linux

Using Dockerfile instead of dockerfile fixes following error on Linux machines:
9 errors occurred:
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/timescaledb/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/special/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/upper/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/generator/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/lower/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/load/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/digit/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/collector/Dockerfile: no such file or directory
	* unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/konrad/tech/opentelemetry-demo/grafana/Dockerfile: no such file or directory

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.kkonrad seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@kkonrad hey! Thanks for the bug fix. I'd really like to merge it but we need you to sign our contributor license agreement first. Would you be willing to do that?

Hey, I'm still working on getting approval for this - please give me 2 more days. Sorry for this situation ...

No problem, friend. Thanks for your contribution

It looks like for me getting approval to sign CLA will take so long that there is no point in keeping it open and potentially blocking others from fixing it. I'm really sorry for this situation

@kkonrad I totally understand. No worries. Thanks for the bug report and the attempt at fixing it!


fix #2215

New documentation looks like this:

This looks fine for version 1. I'd recommend changing "A lot of times a publication relies" to "Many publications rely". Do you need me to merge the PR?

That would be great! Thank you @adswafford

Thank you! .... Just realized that this was 3K 😮


Add an option follow to the joystick

This will make the joystick follow the finger/cursor when going farther than the back circle.
This way, it will allow to have a revert movement way faster and shorter than with a fixed joystick.

Hi @yoannmoinet , is this implemented?

No it's not.
I don't think this is needed or required by anyone after all.
Never saw any joystick implement this feature.
Do you need it? What would be your use-case?

Thanks @yoannmoinet , what I'm trying to achieve, that I think would improve the user experience, is the following:
Lets say the user takes the joystick and goes up surpassing the threshold with its finger because it wants go up very fast. Then, it want to decrease the velocity a little bit, and moves the finger slowly down but, as the finger is already out of the threshold, it is not going to do anything until it reaches the threshold.
So to avoid this what I would want is that the joystick would be responsive to the finger/mouse even if it is outside the threshold, because in a screen the user gets out of it many times wihtout noticing. One way to achieve this is by doing the joystick to follow your finger/mouse when you surpass the threshold.

Working on this myself currently. A good example of this type of feature can be found in the mobile game Brawl Stars. I saw a WIP implementation here, any interest in this picking back up?

It is being implemented in https://github.com/yoannmoinet/nipplejs/pull/160
And it looks promising, very close to be shipped.


Updated the math library to use inbuilt functions

This pull updates the Dome Math library to use the inbuilt functions for min, max and clamp., The changed functions are

Math.min (a, b)
Math.max(a, b)
Math.mid (a, b, c)

Also, a new function Math.clamp (number, min, max ) has been added which is a wrapper around the inbuilt Num.clamp function

The documentation for Math.clamp has been added.

Thank you so much!


Makefile error

Hi,
can you, somehow, help me with the installation of this useful tool?
I have successfully installed GOLANG and configured path variables like the tutorial stated but running Makefile returns an error at line 9: The system cannot find the file specified.
I'm not able to solve this issue because I'm not familiar with Makefiles and I'm not sure which file is missing.
Thank you in advance!

Specifically, here is an error on my end. Not sure if this is a mistake from Makefile or just my go path issue.
env CGO_ENABLED=0 env GOPATH=/Users/Oscar/binlog-parser/_vendor:/Users/Oscar/binlog-parser go install -ldflags '-s' zalora/binlog-parser/...
go: warning: "zalora/binlog-parser/..." matched no packages

I just ran into this problem, I was able to solve it with
go env -w GO111MODULE=off
Then make worked properly

@nathan-bowman I was able to solve this problem by the command you gave. Thanks!


[BUG REPORT]: rts-utils script error

When using the initialization script "rtsutils_init.py" I am getting this error on the first run, having copied and pasted the contents from the script provided at: https://github.com/USACE/rts-utils/wiki/Initialization-Script#rtsutils_initpy

Does anyone happen to know a fix for this?

Closing due to no response to suggested solution.


[release-1.17] Integration Test for Istio custom GRPC count metrics

This is an automated cherry-pick of #44231

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
4f8350856839fe3dd0acf24e8b9423ba68c95742
link
true
/test integ-security-multicluster

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 kubernetes/test-infra repository. I understand the commands that are listed here.


Jordajm/fractional schema tweaks

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:
Bug fixes and schema tweaks

Haven't confirmed this theory but I think what might be happening here is that we're creating too many listings/purchases during are tests, and that is causing the notifications tests to time out because there are too many things to load. (Issue is described here: https://github.com/OriginProtocol/origin-js/issues/245.)
Will investigate

Old theory appears to be incorrect. Fixed the test issue in https://github.com/OriginProtocol/origin-js/pull/273 but that doesn't fix these failures.


Teaching Git interactively in the browser

We want to eventually teach Git interactively in the browser. The best example I've found of doing this is this: https://github.com/pcottle/learnGitBranching
It's open source and runs completely client-side.

This something we could potentially fork and get working within the freeCodeCamp platform, though it would require heavy modification, since it's mostly using a modal-based lessons and a faked Git REPL.
Anyone interested in spiking on this?

Sorry - I created this on the entirely wrong repository accidentally. Please disregard.


Can't rename folder in FileSystem dock since Godot 3.3

Godot version:

OS/device including version:

Issue description:

Steps to reproduce:
Minimal reproduction project:

Godot 3.3中无法使用rename对文件夹进行重命名，但是对文件可以。对文件夹进行重命名时，系统报错为：file_exists()所选文件不存在。本人推测是将文件夹作为文件进行判断，我对Godot进行卸载重装，依然是这样。在3.2.3版本中没有出现这个错误

Translation via google translate:
"In Godot 3.3, rename cannot be used to rename folders, but files can be renamed. When renaming the folder, the system reports an error: The file selected by file_exists() does not exist. I guessed that the folder was judged as a file. I uninstalled and reinstalled Godot, and it was still the same. This error did not appear in version 3.2.3"

I can't reproduce the issue, renaming folders works fine here on Linux:
https://user-images.githubusercontent.com/4701338/116368898-170f9000-a809-11eb-9d36-4900b4e45327.mp4
Please give more details. What OS are you using? What are you doing exactly?

能提供一个可以复现这个问题的Godot工程（打成压缩包再拖进评论框就行）吗？还有，最好提供一些其它的信息，比如你的操作系统之类的（按照模板来填，查查你的问题上面那几个小标题什么意思）。另外，这个社区一般用英语交流，你可以先自己用谷歌翻译转成英语，这样也省得麻烦别人特地去转。
Can you provide a minimal reproduction project? And it's better to give more details about the issue, e.g. the OS you're using. In addition, English is mostly used for communication in this community. I suggest you translate your words into English by Google Translate first, saving some trouble for others.

Can't reproduce on windows 7 64 bit either. Godot 3.3 64bit(didn't try the mono version).

@yxl1779556215 Can you still reproduce this bug? You can also test this in Godot 3.3.1rc2 and see if you can reproduce the bug there.

@yxl1779556215你还能重现这个虫子吗？您也可以在Godot 3.3.1rc2中测试此，看看是否可以在那里重现该 bug。

Sorry, I don't know much about GitHub. I am using windows10 and godot version 3.3.2. This error still exists, please help me, thank you.

What the docs say about this method:

Error rename ( String from, String to )
Renames (move) the from file to the to destination. Both arguments should be paths to files, either relative or absolute. If the destination file exists and is not access-protected, it will be overwritten.
Returns one of the Error code constants (OK on success).

It can only be used to change files' name, so what you're experiencing is intended.

文档对此方法的看法：

错误重命名 （字符串从， 字符串到 ）
将文件重命名为到目的地。这两种参数都应是通往文件的路径，无论是相对的还是绝对的。如果目的地文件存在且未受访问保护，则将被覆盖。
返回错误代码常数之一（成功时确定）。

它只能用于更改文件的名称，因此您正在体验的内容是有意的。

Thank you for your answer, but in my version 3.2.3, this behavior is feasible.

@yxl1779556215 Just did some testing. Can confirm.

@yxl1779556215 Just did some testing. Can confirm that Directory.rename() in 3.3 and 3.4 can't rename folders while it can in 3.2.3. We should change the issue title.

Thank you very much for your reply. I don't know how the title got there. I don't know much about it. Is there a way to rename folders using scripts in Version 3.3.2?

@yxl1779556215 Sorry I couldn't think of a straightforward way to do it. If this change is not intended, I'll try to look into the issue.

The behaviour change of rename() was introduced by 11cbe99cccc2a493e14dfce674a70ad0190e2f61 to avoid renaming a non-existing file. Since a path is not a valid file, ERR_DOES_NOT_EXIST gets returned.

 11cbe99引入了行为更改，以避免重命名不存在的文件。由于路径不是有效的文件，将返回。rename()``ERR_DOES_NOT_EXIST

HMM... I don't understand it, but it looks like that's where the problem is. So, what do I need to learn if I want to get involved in developing Godot?

@yxl1779556215 You could check out this page first https://docs.godotengine.org/en/stable/community/contributing/ways_to_contribute.html. And this specific issue will be handled by @KoBeWi.

@yxl1779556215 You could check out this page first https://docs.godotengine.org/en/stable/community/contributing/ways_to_contribute.html. And this specific issue will be handled by @KoBeWi.

Thank you very much!

And this specific issue will be handled by @KoBeWi.

Even if an issue has someone assigned, you are free to make a PR, because there is no guarantee that it will be handled anytime soon.
Although in this case the fix was easy, so I could make a quick PR.


ReadOnlyConfiguration class is redundant

I think that ReadOnlyConfiguration class is redundant because it is just forwards all calls to IFieldConfiguration. I think we can delete it without problems, and just make IReadonlyFieldConfiguration a part of IFieldConfiguration. BTW as I see IReadonlyFieldConfiguration is used just for internal purposes, maybe it should be hidden as private? What do you think?

If you can do this without breaking the public API and without removing IReadonlyFieldConfiguration (it's important) then feel free to submit a PR - would gladly merge that. It's a bit of a pain we have to keep the other class up to date!

Closing this


API Updates

Master issue to track the updates that I would like to make to the Toolbox API

[ ] No longer automatically register event handlers
[ ] Make the cache name easier to configure
[ ] Simplify - regex vs. express-style is slightly confusing
[ ] Add ability to 'refresh' a cache

Nice touch
It's kind related, shouldn't sw-toolbox delete old cache names automatically? Look this print

Changed from 7 to 7.1 but the version 7 still there, and if I update to 7.2, 7.3 etc.. all the old version still there too.

Only the cache that starts with $$$toolbox-cache$$$... is managed by toolbox. If you have specified your own caches to use with some of the helpers then you will have to manage those caches yourselves. We just don't have any way to know which caches are supposed to be there and which can be deleted, especially since caches are shared across the whole origin while a SW is limited to a scope.

I'm going to argue that we should close this in favor of discussions like https://github.com/GoogleChrome/sw-helpers/issues/44


About support period of version 0.4.3

I am currently using version 0.4.3, it's works pretty well so far. Thanks for your hard work and sharing.
But now the latest version is 0.6.1, the API changes too. Should I update pushy from 0.4.3 to 0.6.1? Or can I still use the version 0.4.3 until further notice? Thanks.

I strongly recommend updating to the latest version. Support issues aside, it's using the vastly-improved, HTTP/2-based APNs protocol; that means connections are much more stable, and we actually know what happens to your push notifications after we send them.
We're not planning on supporting the 0.4 series, which is probably another good reason to upgrade. That said, short of an upstream change, there shouldn't be anything that would cause the 0.4 series to spontaneously stop working.


Mess with various controllers code.

Currently code for various controllers is spread out around whole codebase (replication controller in controller directory, node controller, route controller and service controller in cloud_provider, other controllers in other places). In addition naming is inconsistent, some of them are called XYZController, other XYZManager.
This is confusing (and can be annoying).
cc @wojtek-t @bgrant0607

I'm going to make naming uniform, and move all controllers that are 'real' controllers (i.e. are started in controller-manager) to controller directory.

Ref #4851

@mikedanese we already have controller/replication

All controllers are now in controller directory.


failure count is not increasing in junitfull report

Hi, i am getting junitfull report. but failure count is not increased as we have failure tag inside testcase.
Issue:
<testsuite id="2" hostname="https://hpe-cep--dcedevpiu..com" package="" name="dce-contacts/search/" tests="1" failures="0" errors="0" timestamp="2023-05-31T13:31:10.539" time="1.740">
<properties>
<property name="instance_url" value="https://hpe-cep--dcedevpiu.com"/>
<property name="nimbleToken" value=""/>
<property name="access_token" value=""/>
</properties>
<testcase classname=" / dce-contacts/search/" name="All Onboarded Email id Check (record,status,error code,record count):" time="1.740">
<failure type="AssertionError" message="expected 200 to deeply equal 201">
<![CDATA[ AssertionError: expected 200 to deeply equal 201 at Object.eval sandbox-script.js:1:3) ]]>
</failure>
</testcase>
</testsuite>

here <failure> tag is present inside <testcase> tag, but under <testsuite> tag "failures" count is showing as 0.
Expected: failures count should increase and show number of failed test cases.
Any suggestion on this issue??

Same for me! Our Pipelines in Azure are always Green because of this...(?)


Wrong documentation or argument order

Brief description of your issue
Actual command syntax does not reflect documentation.
Command help winget list --help shows:
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.

The list command displays the packages installed on the system, as well as whether an update is available. Additional options can be provided to filter the output, much like the search command.

usage: winget list [[-q] <query>] [<options>]

The following command aliases are available:
  ls

The following arguments are available:
  -q,--query                  The query used to search for a package

The following options are available:
  --id                        Filter results by id
  --name                      Filter results by name
  --moniker                   Filter results by moniker
  -s,--source                 Find package using the specified source
  --tag                       Filter results by tag
  --cmd,--command             Filter results by command
  -n,--count                  Show no more than specified number of results (between 1 and 1000)
  -e,--exact                  Find package using exact match
  --header                    Optional Windows-Package-Manager REST source HTTP header
  --accept-source-agreements  Accept all source agreements during source operations

More help can be found at: https://aka.ms/winget-command-list

Note the argument order: winget list [[-q] <query>] [<options>]
Using this command syntax, I get an error:
PS C:\> winget list Element.Element --id
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Argument value required, but none found : '--id'

Steps to reproduce
To show the help: winget list --help
Write a query according to the usage in the help: winget list Element.Element --id
Expected behavior
Proper results. For example:
Name    Id              Version Available Source
------------------------------------------------
Element Element.Element 1.11.5            winget
Element Element.Element 1.10.1  1.11.5    winget

Actual behavior
Error Argument value required, but none found : '--id'
Environment
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.978
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.2161.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

@JohnMcPMS any ideas on this one?

Do you have a suggestion on how the help could provide clarity?

Before I can make a suggestion, I need to have more information. How does --query works differently from --id, --name or --moniker.

This is similarly confusing:
PS C:\Users\rltas> winget list --name --exact "Windows Subsystem for Linux Preview"
No installed package found matching input criteria.

PS C:\Users\rltas> winget list --exact --name "Windows Subsystem for Linux Preview"
Name                                ID           Version  Quelle
------------------------------------------------------------------
Windows Subsystem for Linux Preview 9P9TQF7MRM4R <IP_ADDRESS> msstore


Parameter in addsale.php

Hi
In the file add_sale.php I can see  this lines
`

Buscar

`
and I can see you send a parameter to ajax.php
`<?php
// Auto suggetion
$html = '';
if(isset($_POST['product_name']) && strlen($_POST['product_name']))
{
$products = find_product_by_title($_POST['product_name']);
if($products){
foreach ($products as $product):
$html .= "
";
$html .= $product['name'];
$html .= "";
endforeach;
} else {
    $html .= '
';
    $html .= 'No encontrado';
    $html .= "
";

  }

  echo json_encode($html);

}
?>`
the problem is I want to change the parameter but I dont see the pamarameter called "product_name" from add_sale.php to ajax.php..can you explain me pleasee. I need this project for my school..=)
Wich is your logic, please let me know .
Is really interested your system.
Thanks

This function located in includes/sql.php
/--------------------------------------------------------------/
/* Function for Finding all product name
/* Request coming from ajax.php for auto suggest
/--------------------------------------------------------------/
function find_product_by_title($product_name){
global $db;
$p_name = remove_junk($db->escape($product_name));
$sql = "SELECT name FROM products WHERE name like '%$p_name%' LIMIT 5";
$result = find_by_sql($sql);
return $result;
}

Hi bro thank for your atenttion , I understant the fuction of the method
called " find_product_by_title" but  my dude is about how  the file
add_sale.php  sends the parameter  $_POST['product_name'] to ajax.php int
the next form  the parameter "product_name" doesn't exist. but this form
send ti ajax.php this parameter. I will put in red.

id="sug-form">*

*

*

       *

         <button type="submit" class="btn

btn-primary">Buscar*

       *

       <input type="text" id="sug_input" class="form-control"

name="title"  placeholder="Buscar por nombre de producto">*

*

*

*

*

*

<?php

// Auto suggetion*

$html = '';*

if(isset($_POST['product_name']) && strlen($_POST['product_name']))*

{*

$products = find_product_by_title($_POST['product_name']);*

if($products){*

   foreach ($products as $product):*

      $html .= "
";*

      $html .= $product['name'];*

      $html .= "
";*

    endforeach;*

 } else {*

   $html .= '
';*

   $html .= 'No encontrado';*

   $html .= "
";*

 }*

Help me please,
Thank.
2016-06-07 15:36 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
This function located in includes/sql.php
/--------------------------------------------------------------/
/* Function for Finding all product name
/* Request coming from ajax.php for auto suggest
/--------------------------------------------------------------/
function find_product_by_title($product_name){
global $db;
$p_name = remove_junk($db->escape($product_name));
$sql = "SELECT name FROM products WHERE name like '%$p_name%' LIMIT 5";
$result = find_by_sql($sql);
return $result;
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#issuecomment-224406100,
or mute the thread
https://github.com/notifications/unsubscribe/AEuDtawzTLV46VNzMHmvhfUiDHR5gVzJks5qJdZLgaJpZM4IwJ2n
.

i'm retrieving  data by jQuery, check out function.js  file.

Ok I understand, Thanks very much =)
2016-06-07 21:11 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
i'm retrieving data by jQuery, check out function.js file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#issuecomment-224468789,
or mute the thread
https://github.com/notifications/unsubscribe/AEuDtQjvxH84qwTEbAJvPXld2UaboEIJks5qJiS5gaJpZM4IwJ2n
.

No problem!

Hi , the really I staying many hours in this example because I need to
present this in my school this last week and please I need your help onlly
in this part becase I start to develop recently and I dont know javascript
in hight level.I need the next image in your source code.
[image: Imágenes integradas 1]
please help me only with this..
Thank you for your attention
Really thank you very much.
2016-06-07 23:12 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
No problem!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#issuecomment-224482657,
or mute the thread
https://github.com/notifications/unsubscribe/AEuDtUTbFf9l4VEW3u2vvrLeE-NjEAZsks5qJkFCgaJpZM4IwJ2n
.

Can you help me bro?..I need know if you can help me.
Thanks
2016-06-08 0:41 GMT-05:00 jeanfranco gutierrez <
<EMAIL_ADDRESS>
Hi , the really I staying many hours in this example because I need to
present this in my school this last week and please I need your help onlly
in this part becase I start to develop recently and I dont know javascript
in hight level.I need the next image in your source code.
[image: Imágenes integradas 1]
please help me only with this..
Thank you for your attention
Really thank you very much.
2016-06-07 23:12 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
No problem!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#issuecomment-224482657,
or mute the thread
https://github.com/notifications/unsubscribe/AEuDtUTbFf9l4VEW3u2vvrLeE-NjEAZsks5qJkFCgaJpZM4IwJ2n
.

Sure.
Siamon Hasan

On Jun 8, 2016, at 10:16 AM, gian123<EMAIL_ADDRESS>wrote:
Can you help me bro?..I need know if you can help me.
Thanks
2016-06-08 0:41 GMT-05:00 jeanfranco gutierrez <
<EMAIL_ADDRESS>
Hi , the really I staying many hours in this example because I need to
present this in my school this last week and please I need your help onlly
in this part becase I start to develop recently and I dont know javascript
in hight level.I need the next image in your source code.
[image: Imágenes integradas 1]
please help me only with this..
Thank you for your attention
Really thank you very much.
2016-06-07 23:12 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
No problem!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#issuecomment-224482657,
or mute the thread
https://github.com/notifications/unsubscribe/AEuDtUTbFf9l4VEW3u2vvrLeE-NjEAZsks5qJkFCgaJpZM4IwJ2n
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

you mean this code
`function suggetion() {

     $('#sug_input').keyup(function(e) {

         var formData = {
             'product_name' : $('input[name=title]').val()
         };

         if(formData['product_name'].length >= 1){

           // process the form
           $.ajax({
               type        : 'POST',
               url         : 'ajax.php',
               data        : formData,
               dataType    : 'son',

               encode      : true
           })
               .done(function(data) {
                   //console.log(data);
                   $('#result').html(data).fadeIn();
                   $('#result li').click(function() {

                     $('#sug_input').val($(this).text());
                     $('#result').fadeOut(500);

                   });

                   $("#sug_input").blur(function(){
                     $("#result").fadeOut(500);
                   });

               });

         } else {

           $("#result").hide();

         };

         e.preventDefault();
     });

 }`

Closet en tu culo
2016-10-13 12:48 GMT-05:00 Siamon Hasan<EMAIL_ADDRESS>
Closed #13
https://github.com/siamon123/warehouse-inventory-system/issues/13.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/siamon123/warehouse-inventory-system/issues/13#event-822869597,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuDtYJ14Q_vSLJcRjCNdms8zJcAv0nbks5qzm78gaJpZM4IwJ2n
.


NIFI-13495 Exclude FindBugs Annotations and Hibernate Annotations

Summary
NIFI-13495 Excludes FindBugs Annotations and Hibernate Annotations dependencies due to LGPL 2 licensing conflicts. Annotation libraries are not required at runtime and cannot be included in distributed components.
Additional changes include adding these dependencies to the list of banned dependencies to avoid future inclusion.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Closing due to incorrect Jira issue number.


145 refactor

Refactor the service into components.
The structure now is:
renku_notebooks/
├── __init__.py
├── api
│   ├── __init__.py
│   ├── auth.py
│   └── notebooks.py
├── config.py
├── util
│   ├── __init__.py
│   ├── _gitlab.py
│   ├── _jupyterhub.py
│   └── _kubernetes.py
└── wsgi.py

This PR also removes all of the UI code.

Sorry for being a bit late to the party. I've had a quick look at on Friday but didn't have my laptop with me to do a review. Looks good to me overall, definitely structured much more clearly! Just left 2-3 comments.

No problem, thanks for having a look. I'll quickly fix those later today.


Removed time_quantum query option

Related: https://github.com/pilosa/pilosa/pull/699

Coverage remained the same at 100.0% when pulling b429d6076f9f6a10938aedfc4cc222022b62ab3b on yuce:remove-query-option-timequantum into f2d4ffc8d6195193662890af91418171c0f5aa46 on pilosa:master.

Coverage remained the same at 100.0% when pulling 4ee23feefa52b8043261bcf7f50a7bccc43535e9 on yuce:remove-query-option-timequantum into f2d4ffc8d6195193662890af91418171c0f5aa46 on pilosa:master.


⚠ ClamAV has degraded performance

In 548039a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 462 ms

Resolved: ClamAV performance has improved in 892b1cc.


Copy files between containers of different storage accounts?

I have half a million files to copy from one storage account to another. None of your libraries are working and if they work they aren't reliable.
I tried..
Azure Storage Explorer: Whenever I start copy operation it copies some 10000 to 15000 files and closes the application saying "A problem caused Storage Explorer to stop working correctly. Storage Explorer can check for a solution and try to restart the program."
azure-cli: I don't see an option to copy from one storage account to another. All I see is copy between containers of same storage account.
AzCopy: I have read in the documentation that there is an option for copying between different storage accounts but it's only available for windows and I am not using one.
Point me in right direction if I am missing something or suggest me a sure shot option!

cc/ @troydai
@sriharshakappala we have replicated much of the AzCopy functionality in our Azure CLI 2.0 Preview (this repo). The command you would want to use is:
az storage file copy start-batch --source-account {source} --source-share {scont} --destination-share {dest} --account-name {dest account}
You may need additional parameters (i.e. credentials). If this doesn't work for you, that is valuable feedback!

@sriharshakappala could you give az storage file start-batch a try? Should you hit any issue, please leave comments to this issue?
I'll assign this issue to me for now and I'll close it in about a week. Thanks.

Cleaning u old issues, reopen if this is still active.

I'd like copy files from one share to another share but in different storage accounts. I used this
az storage file copy start-batch displays file with --dryrun but when i remove --dryrun, it gives me the following error:
Failed to copy file 0x0409.ini from share dlmrisklink18/DLM_Data_06142018 to file share dlmrisklink18. Please check if you have right permission to read source or set a correct sas token.


Log out

Task: Terminate session when user confirms log out and remains logged out when navigating website

The logout functionality is already being documented in THIS ISSUE.


Thread Safety?

Since this package is on PyPI and shows up in search engine results, I just wanted to point out that it does not appear to be threadsafe.
The global variable _last_v7_timestamp is getting modified but does not have a lock around it.

I am not a maintainer of this repository, but I have to ask: does thread safety matter for this project? This is a python library, so as far as I understand the global interrupt lock essentially prevents code from executing in parallel. Is that incorrect?

The GIL prevents true parallelism, but code execution can still start and stop anywhere.
The code in the uuid7() function, reproduced below, could have one thread reach the line nanoseconds = _last_v7_timestamp + 1 and pause and then another thread reach the same line, pause, and switch back to the first.
In that event, both threads could end up with the same timestamp and appear in the same order even though thread 1 came before thread 2.
This may seem contrived, but if you are making these uuid7() calls in tight loops on multiple threads it can happen. If clock precision on the OS does not reach the nanosecond level, this issue may occur more often.
If the UUIDs are out of order, it may break downstream code which tries to do basic duplicate checking by skipping UUIDs which are less than the last cached value from a given source system/process where it is assumed they will always be in lexicographic order.
def uuid7() -> UUID:
    global _last_v7_timestamp

    nanoseconds = time.time_ns()
    if _last_v7_timestamp is not None and nanoseconds <= _last_v7_timestamp:
        nanoseconds = _last_v7_timestamp + 1
    _last_v7_timestamp = nanoseconds

    ...code continues...

If you are using threads, you should use locks around uuid7() just like you would use with the official UUIDv1 implementation.

@oittaa you are right. i had not noticed that before. they are mutating global state in that module as well. i guess that makes sense to avoid the overhead of a lock unless you need it.


Fetched Data is not displayed except momentarily when the Command Dialog is about to be closed

I'm using a server action inside a command component to implement a search bar functionality. The search input is debounced and when the user stops typing, the server action is called to get the search data. The data is retrieved successfully but the result is not shown despite a correct state update. I have tried this functionality separately without involving a modal and it works.
`"use client";
import { SearchIcon } from "lucide-react";
import { useEffect, useState } from "react";
import {
CommandDialog,
CommandEmpty,
CommandGroup,
CommandInput,
CommandItem,
CommandList,
CommandSeparator,
CommandShortcut,
} from "@/components/ui/command";
import useDebounce from "@/hooks/useDebounce";
import filterProducts from "@/lib/actions/filterProducts";
import { Skeleton } from "../ui/skeleton";
import { cn } from "@/lib/utils";
export default function SearchBar() {
const [open, setOpen] = useState(false);
const [query, setQuery] = useState("");
const [products, setProducts] = useState();
const [isLoading, setLoading] = useState(false);
// const [isPending, startTransition] = useTransition();
const debouncedQuery = useDebounce(query);
console.log(open);
const fetchData = async (debouncedQuery) => {
setLoading(true);
try {
const data = await filterProducts(debouncedQuery);
console.log(data);
setProducts(data);
} catch (err) {
console.error(err);
} finally {
setLoading(false);
}
};
useEffect(() => {
if (query.length <= 0) {
setProducts(null);
return;
}
fetchData(debouncedQuery);
}, [debouncedQuery]);
return (

<SearchIcon className="h-[25px] w-[24px]" onClick={() => setOpen(true)} />
<CommandDialog
className="rounded-lg border"
open={open}
onOpenChange={(open) => {
setOpen(open);
if (!open) {
setQuery("");
}
}}
>

{isLoading ? (

) : (

{products?.map((product) => {
console.log("yo");
return (

{product.name}

);
})}

)}

);
}
`
screen-capture.webm

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

.


Make Flyout component slottable

From what I understand, it could be that the Flyout could other things then that SearchTrackers part. If so, I suggest taking a look at slots. This will allow you to keep the base FlyOut, but switch out the content of it without needed to rebuilt the entire flyout.
Originally posted by @BT-Creator in https://github.com/osoc22/project-track-trace/pull/50#discussion_r920126333

Done in #56


HV 6 Memory and performance improvements

https://hibernate.atlassian.net/browse/HV-1437
https://hibernate.atlassian.net/browse/HV-1438
https://hibernate.atlassian.net/browse/HV-1439
https://hibernate.atlassian.net/browse/HV-1441
https://hibernate.atlassian.net/browse/HV-1443

Note 1: CI fails because of https://github.com/beanvalidation/beanvalidation-tck/pull/149 .
Note 2: the order of the commits displayed below is not exactly the one I have in my branch - the order of the HV-1439 commits is more consistent in my branch.
It's a big one. I started working on the different subjects separately but as I touched the same code and had the same issues, I had to cherry-pick some of the commits in other branches and finally ended up joining the efforts in one branch. The commits are well isolated and should be easily understandable by reading the commit comment and the code.
HV-1438
There are several things here:

I removed completely the ObjectValueExtractor. It's not a good idea to rely on the extractor infrastructure to validate the annotated object itself. Funnily enough, removing it revealed a few issues (these are the commits before the "Remove the ObjectValueExtractor" commit);
Narrowing down the value extractors considered is a necessity as cascading is real slow now, mostly due to the calls to TypeVariableBindings. What I did work, but I think I found an issue in the TCK: https://github.com/beanvalidation/beanvalidation-tck/pull/149 .

HV-1437
These are memory footprint improvements. The idea was mostly to reduce the size of the metadata. The example reported by Stuart is kinda extreme: see https://github.com/keycloak/keycloak/blob/master/model/jpa/src/main/java/org/keycloak/models/jpa/entities/RealmEntity.java .
6.0 was already better than 5.x as I introduce the CollectionHelper.toImmutable* utilities: they trim down the empty and one element collections to the minimum but there was still some room for improvements.
All in all, we reduced the BeanMetaDataImpl of RealmEntity from ~177 kB in the original snapshot of Stuart (using 5.x) to ~60 kB (using this branch).
I'll post something on the list about some other things I'd like to discuss.
HV-1439
Benchmark improvements
The benchmarks were a bit painful to use when you wanted to compare closely 2 versions and switch from one to the other.
I pushed some clean ups to them.
I also removed the iterative benchmarks which were useless.
Some runtime performance improvements
Nothing big but a few things I noticed while benchmarking and it definitely improved the performances.
Quite a lot of parsing/metadata building improvements
The situation was quite bad here so I made quite a lot of improvements to reduce the startup cost of HV.
HV-1443
A small fix required by the other changes.

@gunnarmorling force pushed an update fixing your remarks.
I answered to the others, let me know if there's something else you want me to fix.

@gunnarmorling added 2 more commits to remove the metadata of the unconstrained methods (one is purely cosmetic).


Question about lovasz_hinge_loss

What's the purpose of act in https://github.com/yinghdb/EmbedMask/blob/3b4d9fb4e0b6112dc501708184ff684dfb45f3f0/fcos_core/layers/lovasz_hinge_loss.py#L64, i find there is no act in the original implementation of lovasz_hinge. Turning on it could cause nan in the training process, but turning off it the loss does not degrad. Do you have any idea about the nan problem, what might be the reason? Reducing the lr does not help.

Right. The original lovasz_hinge does not have the 'act' operation. But the input range of the original lovasz_hinge is (-inf, +inf). So I use the 'act' operation to range my input. And it brings 'nan' problem.
The 'nan' problem mainly come from the extreme value of the input, e.g., the original input which is very close to 0 will be come the nearly '-inf' after 'act'. In my later practice, I find it useful to eliminate these extreme values before 'act' like following, and it rarely affects the final results.
m = (input_flatten < 0.999999) * (input_flatten > 1e-9)
input_flatten = input_flatten[m]
target_flatten = target_flatten[m]
input_flatten = torch.log(input_flatten) - torch.log(1 - input_flatten)

I am struggling in improving the performance of EmbedMask, so I have not fixed the problems like this, sorry!

Thanks for your quick reply, i will try the solution. Hope to see the improvements of EmbedMask!

Right. The original lovasz_hinge does not have the 'act' operation. But the input range of the original lovasz_hinge is (-inf, +inf). So I use the 'act' operation to range my input. And it brings 'nan' problem.
The 'nan' problem mainly come from the extreme value of the input, e.g., the original input which is very close to 0 will be come the nearly '-inf' after 'act'. In my later practice, I find it useful to eliminate these extreme values before 'act' like following, and it rarely affects the final results.
m = (input_flatten < 0.999999) * (input_flatten > 1e-9)
input_flatten = input_flatten[m]
target_flatten = target_flatten[m]
input_flatten = torch.log(input_flatten) - torch.log(1 - input_flatten)

I am struggling in improving the performance of EmbedMask, so I have not fixed the problems like this, sorry!

I think it might be better to use torch.clamp().
if act:
    # map [0, 1] to [-inf, inf]

    # m = (input_flatten < 0.999999) * (input_flatten > 1e-9)
    # input_flatten = input_flatten[m]
    # target_flatten = target_flatten[m]

    MIN = 1e-6
    MAX = 1 - MIN

    torch.clamp(input=input_flatten,  min=MIN, max=MAX, out=input_flatten)
    torch.clamp(input=target_flatten, min=MIN, max=MAX, out=target_flatten)

    input_flatten = torch.log(input_flatten) - torch.log(1 - input_flatten) # prob to logits

Since m = (input_flatten < 0.999999) * (input_flatten > 1e-9)  reduces the number of samples & targets.